Network Configuration - 800xa 5.1 FP4
As part of our network switch upgrade we are having problems with secondary network.
We have isolated and checked each individual cable on both primary and secondary switch the cables are landed in the right place.
Now what we observed is, all the computers are showing a connectivity on primary network with "domain.local" name on it but the secondary shows "unspecified network" (RNRP shows connectivity down).
When we unplug the cable or disable the primary adapter, the secondary network get connected and shows "domain.local" but no connectivity.
On the other hand plugging the cable back or enabling the primary adapter after identifying it shows "unspecified network", then i have to disable the secondary adapter to get connectivity on the primary.
Any valuable suggestion would be appreciated.
Voted best answer
Disconnecting the cable or disabling the network adapters will give you different results.If you disconnected primary network work connection, 800xA communication will switch to back up network connection. The system would work normally.If you disabled the primary network adapter for the node, the network redundancy would not worked. This is design.So if you want to test the redundancy then only disconnect the cable.
Please provide more information like the addressing schemes used is it implicit or explicit addressing?
If you are using managed switches it is worth checking
1)IGMP Snooping must be disabled.
2)If Spanning Tree (STP/RSTP) is enabled, check if it's really needed and if there's any other option available then disable it.
3)If the actual configuration is not a ring the ring redundancy protocol (Spanning Tree or HIPERRING), ring redudancy operation should be disabled to allow regular use of the ports otherwise reserved for the ring.
As a general recommendation do the following
1)If Receive side scaling is enabled in the netwrok adapters please disable them.
2)Check the binding order and see if the order is set as per recommendation.
3)If there are unused network adapters then please disable them.
4)Register the connection on DNS is checked for both the primary and the secondary network.
Do not use disable adapter to test RNRP; RNRP can not handle if primary interface is lost.
-> pull cable (or use "Disconnect" in VMware).
If RNRP shows no connection on secondary LAN; have you tried pinging over it (with primary network cable disconnected)?
If you can't ping another computer over the secondary LAN, it can not be properly setup.
If ping other via secondary work, but not RNRP - verify that IGMP is "OFF". Both Cisco and Westermo switches comes with IGMP "ON" by factory default. In Cisco, you need to disable IGMP using the Cisco Network Assistant tool as the built-in web interface does not show nor allow changing of IGMP settings.
I believe the "domain.local" lights up if Windows detect a domain controller on that LAN.
At this stage; I think all evidence points to a non-operational secondary LAN.
About problems with getting primary interface up after having secondary up (but not operational) - what network adapter and driver are you using?
If you use VMware/ESX you should select the E1000 network driver as we have seen issues with RNRP and the other VMware drivers (VMXNETx).