![]() Such misconfiguration is known to cause loops in the network that lead to an ARP broadcast storm that is then detected by the network switch and as a result, the switch port gets disabled. To verify, run the following on both VIOs: When creating an SEA in failover (auto or sharing) mode without a properly configured control channel adapter, this can lead to a network storm. The PVID must be a "unique" PVID that is NOT in use. ![]() ![]() If answer is YES, ensure the control channel adapter specified during SEA creation (mkvdev) on both VIOS is using the same "Port VLAN ID" (PVID). To check, run: ' lsdev -dev SEA_ent# -attr netaddr' Note: If the Shared Ethernet Adapter in question is a "Simplified SEA failover" setup (no dedicated control channel adapter is being used), so this does NOT apply.See "Diagnosing the problem" for more details. When using a dedicated control channel adapter and the Shared Ethernet Adapters are created using a control channel adapter with a different PVID, such misconfiguration can lead to a network storm. The Shared Ethernet Adapter may be misconfigured.If the Shared Ethernet Adapter netaddr attribute has an IP address to ping, ensure the IP is valid and pingable. The Shared Ethernet Adapter cannot ping the specified remote host-IP address to ping ( netaddr)-to inform the backup Shared Ethernet Adapter that it needs to become active.The link status went down for the underlying physical adapter.The most common causes for a Shared Ethernet Adapter to be in limbo state include (but are not limited to) the following:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |