Table of Contents
Advertisement
Raisecom
ISCOM2600G-HI (A) Series Configuration Guide
member devices receiving the message, according to the local ISF topology information table,
will determine whether member device A is the master or slave device.
The status of an ISF interface depends on that of the bound ISF physical interface.
When all ISF physical interfaces become Down, the ISF interface will be Down.
3.2.5 MAD
Multi-Active Detection (MAD) is a detection and processing mechanism. When an ISF link is
faulty, the ISF will be split to two new ISFs which have the same IP address and thus conflict
with each other and amplify the fault. Thus, a mechanism is required to improve system
availability when ISF split occurs. MAD can detect whether there are multiple ISFs on the
network, take actions accordingly to minimize impact of ISF split on services, and enable the
ISF at the master device side before ISF split to work properly. MAD has the following
functions:
3.3 Establishing ISF environment
3.3.1 Establishment flow
Figure 3-8 shows the flow for establishing the ISF environment. We recommend planning the
ISF topology and then installing devices to facilitate physical connection of cables in the ISF.
If member device A is the master device, its leave triggers role election and then its
neighbor devices will update local ISF topology.
If member device A is the slave device, its neighbor devices will update local ISF
topology to guarantee rapid convergence of ISF topology.
Detect ISF split: use Bidirectional Forwarding Detection (BFD) to detect whether there
are multiple ISFs on the network.
Eliminate conflict: after ISF split occurs, the original ISF can detect other ISFs in Active
status (indicating the ISF is working). This function allows the ISF with the minimum
unit ID of the master device to continue to work while converting other ISFs to Recovery
status (indicating the ISF is disabled) and shuts down all physical interfaces except the
reserved interface in the Recovery ISFs to prevent these ISFs from forwarding packets.
Clear MAD faults: when an ISF link is faulty, the ISF will be split to two new ISFs. In
this case, you can clear the fault by resuming the faulty link to merge two conflicting
ISFs to one. If a Recovery ISF becomes faulty before an existing MAD fault is cleared,
you must resume the faulty ISF and faulty link to merge two conflicting ISFs to one. If
the Active ISF becomes faulty before an existing MAD fault is cleared, you can use
command lines to enable the Recovery ISF to replace the original ISF to minimize
impact on services, and then clear the existing MAD fault.
Raisecom Proprietary and Confidential
Copyright © Raisecom Technology Co., Ltd.
3 ISF
161
Advertisement
Table of Contents
