62
Troubleshooting flowchart
Figure 20 Troubleshooting IRF split
Solution
To resolve the issue:
1.
Verify that the IRF physical interfaces are operating correctly:
a.
Execute the
display trapbuffer
command or view system logs to check for physical
IRF link down events that occurred around the split time.
b.
If the split followed an IRF link down event, execute the
display interface
command to
check port statistics for CRC errors.
c.
If transceiver modules and fibers are used, execute the
display transceiver
diagnosis
command. Make sure the transmit and receive power has not exceeded the
power specifications of the fiber module.
d.
Remove hardware issues that might cause recurring IRF split events:
e.
Execute the
display version
command to identify the uptime of MPUs and interface
modules that have IRF links.
f.
Compare the uptime of MPUs and interface modules to determine whether a member
chassis or interface module had rebooted before the IRF split.
g.
If the IRF split is caused by a member chassis or interface module reboot, use the methods
described in "
" to resolve the issue.
2.
If the issue persists, contact H3C Support.
BFD MAD failure
Symptom
BFD MAD fails to detect an IRF split event. Two IRF fabrics are operating with the same Layer 3
settings, including the same IP address.
End
IRF split
Contact the support
Member chassis or module that
has IRF links rebooted?
Identify the cause and
resolve the issue
Yes
No
Resolved?
No
Yes
IRF physical interfaces down?
Identify the cause and
resolve the issue
Yes
No
Resolved?
No
Yes
