Leland reported the following error when querying OSA card via OSA/SF .
> IOAK881E Image D UA 15 had an OSA OAT reject code of E00A
According IBM doc :
>> E00A An IP address was received by the OSA port that duplicates an IP
address being used by another IP connection in the IP network. Change one
of the IP addresses in the network.
So it looks as an IP address duplication . It is probably the VIPA address.
Infact, according qetharp reply, the VIPA address is defined to both OSA
cards.
Now the question is: How Linux manges VIPA takeover ? I don't know. But I
remember how it should work for OS/390.
In OS/390 A TCPIP stack with two OSA card on the same LAN and a PLAN
network (VIPA same network address as interface network addresses) make the
following action :
- activate the first interface and send out a gratious ARP to advertize
its' IP address (interface)
- define the first interface as in charge of VIPA address (VIPA arp
responsible) ; informs OSA card of the VIPA address.
- activate the other card : send gratious ARP ;
- receive gratious ARP of the secondth interface from the first interface ,
so understands that the interface is on the same LAN as the first, and
decides to not propagate VIPA address on that interface .
- If the first interface goes down, TCPIP stack move the arp
responsibility for VIPA to the other interface.
In other words only a single OSA card has to be in charge of VIPA at the
same time.
Perhaps some guy can confirm and/or add something about how LINUX manages
VIPA takeover. It is not clear why sometime it works, sometime it
doesn't.
OSA query reporting registered addresses could be useful .
Franco Mignogna INTERNET : franco_mignogna@
it.ibm.com
