I am installing an E4C with the new 5899 1GB 4-port Ethernet Adapters.
IBM documentation from 30th May 2012 states latest support for this adapter is in VIOS 188.8.131.52, but when is that available?
184.108.40.206 is not listed in Fix Central
Background to my question:
The config includes dual-VIOS with SEA Failover.
When I test the failover, it all looks as it should in both VIOS from entstat -all ent10 |grep Active but the packets are lost. This is whether I use VLAN tagging or not.
Any help is gratefully appreciated.
bsewen 01000023VV1 Post
Re: VIOS 220.127.116.11 availability2012-07-27T14:36:10ZThis is the accepted answer. This is the accepted answer.We are seeing the exact same thing with the exact same configuration. When we test failover both fall off the network. We have swapped cables, changed trunk priorities, rebuilt them from scratch and everything else you can think of and the problem persists.
Re: VIOS 18.104.22.168 availability2012-07-29T13:24:10ZThis is the accepted answer. This is the accepted answer.Update: Called IBM to report 5899 issue. It's a known problem that SEA failover won't work. A driver issue in AIX / VIOS.
They are coding an efix for it before 22.214.171.124 is released.
JCBAS 0600023XU01 Post
Re: VIOS 126.96.36.199 availability2012-08-01T19:10:01ZThis is the accepted answer. This is the accepted answer.Hello, trying the same configuration . I've installed VIOS 188.8.131.52 from media but the Driver for 5899 was not found in it.
What version have you got ?
I want to update to FP25 to see if driver is inside but with the media bug and the need to install fix IV07822.
But with no network , i don't know how to do .
An idea please ?
Re: VIOS 184.108.40.206 availability2012-08-01T20:16:53ZThis is the accepted answer. This is the accepted answer.The driver for the 5899 can be found in the AIX 6.1TL 7 SP4 media.
But I haven't tried to install it on a 220.127.116.11 level.
I was lucky that I had a preload 18.104.22.168 which included the driver. I then used alt_root_vg to install my second VIOS.
When I spoke to IBM I got the impression that even the shipped driver is the wrong one despite its correct description.
Sorry this is not much help.
I can't wait for this fix !