43
Solution
To resolve the issue:
1.
Verify that the IRF physical interfaces are operating correctly:
a.
Execute the
display logbuffer
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.
2.
Remove hardware issues that might cause recurring IRF split events:
a.
Execute the
display version
command to identify the uptime of IRF member devices.
b.
Compare the uptime of IRF member devices to determine whether a member device had
rebooted before the IRF split.
c.
If the IRF split is caused by a device reboot, perform one of the following tasks:
−
If the split is caused by a device reboot, use the methods described in "
" to resolve the issue.
−
If the reboot is caused by power failures, use the methods described in "
" to resolve the issue.
3.
If the issue persists, execute the
display diagnostic-information
command and collect
the device diagnostic information, and then send the information to 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
configurations, including the same IP address.
