Fibre Channel (SAN)

Reply
N/A
Posts: 1
Registered: ‎07-17-2009

libipadm error: client connect failed

I'm new to Brocade communities.  So, forgive me if I'm posting this in the wrong area.

We have two 48000 directors acting as core switches in our environment.  I have started receiving some unusual errors/information when connecting to them via telnet, their health status in SAN Health or clicking on the "Status" button in the admin GUI.  Below are examples of each.  I'm hoping someone has seen this before or has some knowledge of what is going on.  Any help would be appreciated.

Health status of directors reports “N/A” in SAN Health Report.

Reports healthy in directors’ admin GUI under “Switch Information” tab.

When clicking on “Status”, receive the following information.

Director A - when clicking on Status

Error

Mon Jan 10 2011 22:47:57 GMT

Internal API (FW) error

Director B - when clicking on Status

Error

Mon Jan 10 2011 23:24:28 GMT

Internal API (FW) error

Information displays properly when clickin on the following.

                Temp

                Power

                Fan

                HA

Received the following errors when connecting via Hyperterminal.

I receive the following information on both directors when connecting via telnet.  The same error occurred on the othe director only it was for CP0.

Fabric OS (cp1)

libipadm error: client connect failed /tmp/ipadm-g-login-3622-7d12f6be509ba1

ipadm do_backtrace connect failed pid 3622, name login

/fabos/lib/libipadm.so.1.0

/fabos/lib/libipadm.so.1.0

/fabos/lib/libipadm.so.1.0(ipAdmLocalAddrIdGet+0x4c)

/lib/security/pam_fabos.so

/lib/security/pam_fabos.so(pam_sm_authenticate+0x25c)

/lib/libpam.so

/lib/libpam.so(_pam_dispatch+0x2b0)

/lib/libpam.so(pam_authenticate+0x90)

/bin/login

/lib/libc.so.6

/lib/libc.so.6

Fabos Version 5.3.0

Thanks,

Tim

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook