Debugging an Interface

When a fault occurs on an interface, you can run the following debugging commands in the user view to view the debugging information, locate the fault, and analyze the cause.

Context

Debugging affects the performance of the system. So, after debugging, run the undo debugging all command to disable it immediately.

When a fault occurs on an interface, run the following debugging commands in the user view to locate the fault.

Procedure

Run the debugging ethernet packet [ arp | error | ip | ipv6 | isis ] [ verbose ] [ interface interface-type interface-number ] in the user view to debug the Ethernet interface.
Run the debugging ethernet packet process [ interface interface-type interface-number ] in the user view to debug the related process after Ethernet packets are received.
Run the debugging ethernet packet mac { dest_mac dest-mac | src_mac src_mac } in the user view to debug the Ethernet interface based on the MAC address.
Run the debugging trunk error [ slot slot-number ] command in the user view to enable debugging for errors on Eth-Trunk interfaces.
Run the debugging trunk event [ slot slot-number ] command in the user view to enable debugging for events on Eth-Trunk interfaces.
Run the debugging trunk msg [ slot slot-number ] command in the user view to enable debugging for Eth-Trunk packets.
Run the debugging trunk state-machine [ slot slot-number ] command in the user view to enable debugging for the Eth-Trunk state machine.
Run the debugging trunk updown [ slot slot-number ] command in the user view to enable debugging for Up/Down events of LAGs.