How to check Ethernet Channel link failure

Ethernet Channel protocol is a link aggregation protocol developed by Cisco, which can bind multiple physical Ethernet links into a logical link, which can increase transmission bandwidth and improve link redundancy through multiple port bindings. Currently VNX supports the Ethernet channel protocol, where all ports are connected to the switch using the same IP and MAC address, and EtherChannel can bind 2, 4, or 8 Ethernet ports at the same time.

When using EtherChannel on Vnx, you can arrange the error according to the following ideas:

Step one: Check the physical port assigned to EtherChannel.

$ server_sysconfig server_2-virtual

server_2:

Virtual Devices:

Trk0_ec Devices=cge2 Cge3

FSN failsafe NIC Devices:

TRK trunking Devices:trk0_ec

Step Two: Verify the port Duplex and speed settings.

$ server_sysconfig Server_2-pci

SERVER_2:PCI DEVICES:

Slot:1

Emulex LP9000 Fibre Channel Controller

0:fcp-0 irq:23 addr:10000000c92b5a10

1:fcp-1 irq:24 Addr:10000000c92b5a11

Slot:2

Emulex LP9000 Fibre Channel Controller

0:fcp-2 irq:22 addr:10000000c92b514e

Slot:4

Intel 10/100/1k Ethernet Controller

0:CGE0 irq:18

Speed=auto Duplex=auto rxflowctl=disable txflowctl=disable

1:cge1 irq:19

Speed=auto Duplex=auto rxflowctl=disable txflowctl=disable

2:cge2 irq:20

Speed=auto Duplex=auto rxflowctl=disable txflowctl=disable

3:cge3 irq:21

Speed=auto Duplex=auto rxflowctl=disable txflowctl=disable

Slot:5

Alteon Tigon-2 Gigabit Ethernet Controller

0:ace0 irq:25

Linkneg=enable rxflowctl=disable txflowctl=disable

0:ace0 irq:25

Linkneg=enable rxflowctl=disable txflowctl=disable

Step three: Check the connectivity of the physical link.

$server _netstat Server_x–i | -A | -S | -R

Note:-A displays all IP, ICMP, TCP, and UDP port status

-I shows all physical port rollup status

-S shows all protocol statistics

-R Display Routing table

Step four: Check the ARP table.

$ server_arp Server_2-all

server_2:

172.24.102.254 at 0:D0:3:F9:37:FC

172.24.102.20 at 0:d0:b7:82:98:e0

172.24.102.24 at 0:50:56:8e:1d:5

128.221.253.100 at 0:4:23:a7:b1:35

Step five: Examine the routing table to verify the gateway and routing conditions.

$ Server_route Server_2-list

server_2:

NET 128.221.253.0 128.221.253.2 255.255.255.0 el31

NET 128.221.252.0 128.221.252.2 255.255.255.0 el30

NET 172.24.102.0 172.24.102.238 255.255.255.0 cge0

Host 127.0.0.1 127.0.0.1 255.255.255.255 loop

Step Six: Verify that the IP address, subnet mask, broadcast is correct.

$ server_ifconfig Server_2-all

server_2:

Loop Protocol=ip Device=loop

inet=127.0.0.1 netmask=255.0.0.0 broadcast=127.255.255.255

556 Command line Interface Reference for File 7.0

The server Commands

Up, loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0 netname=localhost

CGE0 Protocol=ip DEVICE=CGE0

inet=172.24.102.238 netmask=255.255.255.0 broadcast=172.24.102.255

Up, Ethernet, mtu=1500, vlan=0, macaddr=0:60:16:4:29:87

El31 Protocol=ip Device=cge6

inet=128.221.253.2 netmask=255.255.255.0 broadcast=128.221.253.255

Up, Ethernet, mtu=1500, vlan=0, Macaddr=0:60:16:4:11:a6 netname=localhost

El30 Protocol=ip device=fxp0

inet=128.221.252.2 netmask=255.255.255.0 broadcast=128.221.252.255

Up, Ethernet, mtu=1500, vlan=0, Macaddr=8:0:1b:43:7e:b8 netname=localhost

Step Seven: Check the data Mover log to confirm the presence of Port Up/down.

$server _log server_x | egrep TRK

Step eight: Use ping to verify physical connectivity.

$ server_ping server_2 172.24.102.2

server_2:172.24.102.2 is alive, Time= 0 ms

Step Nine: View the port using the load balancing method, MAC address, TCP, or IP?

Server_sysconfig Server_2-v-I. fsn_test

server_2:

FSN Fsn_test:link is up * * *

active=cge-2-1 primary=cge-2-1 standby=cge-2-0

By using the steps above, you can identify the cause of the Ethernet channel link failure and then fix it.