Figure 3-12 Clearing Mad Fault (Clearing Isf Link Fault) - Raisecom ISCOM2600G-HI (A) Series Configuration Manual

Raisecom
ISCOM2600G-HI (A) Series Configuration Guide
To make a VLAN interface in a Recovery ISF continue to receive and send packets
(such as using the VLAN interface for remote login), configure the VLAN interface
and its corresponding Layer 2 Ethernet interface as reserved interfaces.
Clearing MAD fault
When an ISF link is faulty, the ISF splits into two ISFs, and thus multi-active conflict occurs.
When the ISF system detects multi-active conflict, these two conflicting ISFs will elect as
below:
Step 1 Compare the number of member devices in these two ISFs. The ISF with more member
devices will win and resume working. The loser ISF transits to Recovery status, in which it
fails to forward service packets.
Step 2 If these two ISFs have the same number of member devices, the ISF system will compare the
member ID of the master device. The ISF with the master device of a greater member ID will
win and resume working. The loser ISF transits to Recovery status, in which it fails to
forward service packets.
In this case, you can clear the ISF link fault to resume the ISF system (devices will
automatically try to clear the ISF link fault. If failed, it needs manual restoration).
After the ISF link fault is cleared, the Active ISF and the Recovery ISF will merge into an ISF.
The ISF system prompts you to restart the Recovery ISF. After the Recovery ISF is restarted,
its services interfaces forcibly shut down will be restored to the actual physical status, and the
ISF system will resume. As shown in Figure 3-12, if you restart the Active ISF, the two ISFs
will merge into one. Then, you need to use the mad restore command to restore services
interfaces, which are forcibly shut down, in the Recovery ISF to the actual physical status,
and the ISF system will resume.

Figure 3-12 Clearing MAD fault (clearing ISF link fault)

As shown in Figure 3-13, if the Active ISF (ISF 1) becomes faulty (device fault or
uplink/downlink fault) before the MAD fault is cleared, you can use the mad restore
command on the Recovery ISF (ISF 2) to restore it and make it replace ISF 1. Then, clear the
fault of the link between ISF 1 and ISF 2. Then, these two ISFs merge and the ISF system is
restored.
Raisecom Proprietary and Confidential
Copyright © Raisecom Technology Co., Ltd.
3 ISF
176