02-12-2016 04:25 AM
I have 2005-B16 Ala 200E IBM San Switch.
I upgarded it from 5.1.0b to 5.2.3 and after reboot i can see i lot partial FOS command fucntionalities.
I kept upgrading until 6.2.2g as a last Release for this device Model Type 34 = 2005-B16 = 200E kind.
Now my Problem is whenever i try to run "ipAddrSet" / ipaddrshow etc i end up with following error..
libipadm error: client connect failed /tmp/ipadm-g-ipaddrshow-1851-fae2eebbc5
ipadm do_backtrace connect failed pid 1851, name ipaddrshow
libipadm error: client connect failed /tmp/ipadm-g-ipaddrset-1881-10ab65bdec0
ipadm do_backtrace connect failed pid 1881, name ipaddrset
ipAdmLocalAddrIdGet() returned 21
I tried a lot by checking..
#ldd + ldconfig and i end up like this..
Lets Check Libraries.....
fsw02:root> ls -lrt /fabos/lib/libipadm.so.1*
-rwxr-xr-x 1 root sys 47488 Feb 2 2015 /fabos/lib/libipadm.so.1.0*
fsw02:root> ls -lrt /lib/libc.so.6*
lrwxrwxrwx 1 root sys 13 Dec 15 13:05 /lib/libc.so.6 -> libc-2.3.6.so*
fsw02:root> find / -name "libc-2.3.6.so*"
fsw02:root> ls -lrt /mnt/lib/libc-2.3.6.so
-rwxr-xr-x 1 root sys 1312032 Jan 12 13:08 /mnt/lib/libc-2.3.6.so
I can see this all commands at last Point to -----> ipAddr ... see Below..
fsw02:root> ls -lrt ipAddr
-rwsr-xr-x 1 root sys 35288 Feb 2 2015 ipAddr*
fsw02:root> ls -lrt ipAddrSet
ls: ipAddrSet: No such file or directory
fsw02:root> ls -lrt ipaddrset
lrwxrwxrwx 1 root admin 6 Nov 6 17:49 ipaddrset -> ipAddr*
fsw02:root> ls -lrt ipaddrshow
lrwxrwxrwx 1 root user 6 Nov 6 17:49 ipaddrshow -> ipAddr*
When i check LIBRARIES are OKAY.
When i check all /etc/ld.so.conf is also pointing OK.
Kindly help me to solve this problem as i spent huge time troubleshoting it and i always end up with this freaking errors..
Any suggestions .. Do i need to downupgarde and go back to 5.1.0b OR 5.1.1 and see if it solves the Problem ???
Please Please suggest..
attacehed = support logs..
03-03-2016 10:14 AM - edited 05-06-2016 06:18 AM
We have passed this information along to our support group in hopes they can assist you. You should have received an email requesting more information. You can either respond here or via email. If the issue is resolved we will make sure to post the solution in the community to assist other members.
You can find more information about the Brocade Community / TAC program by clicking the image below.
03-03-2016 10:17 PM
Hello Dennis Smith,
Thanks for your email and reply.
I replyed on email to support group / support team.
Let's see how it goes ahead.
Looking forward to have support on this issue.
03-03-2016 10:53 PM
do you follow from FOS 5.3.2 the correct upgrade procedure path ?
FOS v6.0.0c -> FOS v6.1.2c -> FOS v6.2.2g
Upgrading to Fabric OS v6.0.0 is only allowed from Fabric OS v5.3.x and not from 5.2 as you mention in the Threads
03-03-2016 11:07 PM
Thanks for your valuable comment.
Here is the PATH we followed..
5.1.0b -->5.2.3-->5.3.2c --> 6.0.1a ---> 6.1.2c --> 6.2.2f
what i observed is port 5.2.3 when switch rebooted it went into this lib errors and i lost partial FOS fucntionality.
Now i can not set any more ip address along with few more commands / binaries are not working they all results me in lib erros.
Do you see an option that i should roll back / downgrade and reach to 5.1.0b and will that bring me back to working state my main aim is to change IP address of this switch ?
At Frabric level i can see all my ports are ONLINE and WWN / WWNP etc are discovered well ( using serial console i am accessing this switch now a days ).
Kindly suggest How we can recover this situation ?
Thanks & Regards,
03-03-2016 11:41 PM
i've my doubt with a downgrade from current 6.2 to 5.1, and to be honestly I don't want to assist to a such procedure, because you can get a risk that the switch get corrupted.
Theoretically, such a downgrade is supported, but I would suggestat this point to wait answer from Support.
can you tell me please follow:
what is the exact in MB zipped package file from FOS 5.2.3 ? and where you download the package ?
I ask because it was different package in the past for download available.
Another question, as fair as i remember, in old FOS 5.x - but I don't remember the exact release - , before upgrade to 5.2 or 5.3 aptpolicy must disable, otherwise the Upgrade failed.
do you have aptpolicy enabled ?
03-04-2016 12:54 AM
PFA screenshots of various upgrade packages from my loca FTP Server.
6.2.2f and 6.2.2g is downloaded from Brocade and rest all are downloaded by IBM for us last year.
I have my IBM Account using that i am redirected to Brocade site and i was able to download 6.2.2f + 6.2.2g.
Package Size = 269MB for v5.2.3 zip.
I read about this policy routing aptpolicy etc which was disbaled at my end not only on this switch but i have still other switches in v5.3.2 successfully upgarded until 6.2.2f/g.
What i saw in output of "firmwaredownloadstatus" after upgrade to 5.2.3 ( from 5.1.0b ) both memory area were showing 5.2.3
but i lost fos fucntionality , even after loosing FOS fucntionality i moved ahead with with next upgrade and finished until 6.2.2f.
today switch is in 6.2.2f in production system with those errors.
I can not keep them running like this for longer ( with FOS functionality lost ) .
Attached few screenshots and supportshow output ( of same switch removed from production for troubleshooting purpose ).
03-04-2016 07:29 AM
the FOS package show ok.
--->>>I can not keep them running like this for longer
if you have a active maintenance contract, can open a call with the support.
03-07-2016 10:05 AM
Hello, I'm representing IBM Storage Support.
In order to provide you the appropriate support, you need to open a PMR, so we can now the details of your Storage enviroment.
You can check toll-free number for your country on this link: http://www.ibm.com/planetwide/index.html#region