Isl does not come up on some ports – Brocade Network OS Administrator’s Guide v4.1.1 User Manual
Page 685
1. Check for db packet capture. Below are the commands to enable and view a capture.
db 8/0/1 rte enable capture all
db 8/0/1 rte start capture
db 8/0/1 rte show capture
After the start capture command, the system sends a stream and performs show capture. This
displays most of the capture information:
a)
It shows all the fields resolved — whether it is trap, drop, or fwd.
b)
It shows the packet itself.
c)
It shows the Routing Engine (RTE) Layer 2 history, as in the result of the Layer 2 table hit or
miss.
d)
It shows the RTE Layer 3 history, as in the result of the Layer 3 table hit or miss. If Layer 2
table has a success and Layer 3 table failed, then check for routing issues.
For example, in the entry for trap (Ping to box), the Routed fields should display Ipv4Rtd
and the entries hit. For a TRAP hit, it should display trapen:1 (Bit set to 1 to indicate
packet is trapped).
e)
Packet Capture displays the last four packets, Make sure those are the fwd packets (for
example, check for SA DA MAC, pkttyp:0806).
db 8/0/1 rte enable capture all
db 8/0/1 rte start capture
db 8/0/1 rte show capture
f)
If the FWD and packets are not being forwarded, then it is an ASIC problem. If it is a DROP,
proceed to the next step.
2. If result is DROP:
a)
Execute the show ip route command. If the route is not present, then it is an RTM issue.
b)
Execute the show arp command. If ARP is not resolved for the corresponding next hop,
then it is an ARP issue. If it is VLAN along with ARP, MAC should be resolved. If MAC is not
resolved then it is an L2SYS issue.
c)
If step 2b passes, enter the debug show ip lpm command to display the routes in
hardware, and verify that the corresponding destination ARP address is present. If it is not
present, then it is an L3FWD issue. Collect the information from debug show ip lpm ,
attach the file /tmp/fib_wlv_ioctl, along with supportSave data and contact support.
Specify that it failed in this step.
Refer also to
Gathering troubleshooting information
on page 667, which provides
information about Network OS supportSave files.
d)
If step 2c passes and traffic is still dropping, then it is an ASIC issue.
NOTE
For additional information about packet capture, refer to
Using the packet capture utility
page 723.
ISL does not come up on some ports
The failure of an Inter-SwitchLink (ISL) between two switches in a VCS Fabric cluster can occur for
various reasons:
• The ISL configuration is disabled. Refer to
on page 686.
• The ISL is segmented. Refer to
on page 686.
• VCS Fabric mode is not enabled on one of the switches. Refer to
Verifying VCS Fabric configuration
on page 687.
• Different VCS IDs on each of the switches. Refer to
Verifying VCS Fabric configuration and RBridge
on page 687.
ISL does not come up on some ports
Network OS Administrator’s Guide
685
53-1003225-04