H3C Technologies H3C S7500E Series Switches - Manual (Page 24)

1-17
To do… Use the command… Remarks
the BFD MAD
detection
Hybrid port port hybrid vlan vlan-id
according to the port type.
BFD MAD detection has no
requirement on the link type of
the detection port, and you do
not need to modify the current
link type.
By default, the port is an access
port.
Return to system view quit —
Enter VLAN interface view
interface vlan-interface
interface-number
—
Enable BFD MAD mad bfd enable
Required
Disabled by default.
Configure a MAD IP address for
the VLAN interface on the
specified member mad ip address ip-address { mask |
mask-length } chassis
chassis-number
Required
By default, no MAD IP address is
configured for any interface.
If there is an intermediate device in a BFD-MAD enabled IRF virtual device, to ensure that the BFD
packets can be transmitted among members normally, you also need to add the port that connects to
the BFD MAD detection link on the intermediate device into the VLAN used for the detection.
z You are not allowed to configure other services on a Layer 3 interface with BFD MAD enabled.
z A VLAN interface enabled with BFD MAC detection and the interfaces of this VLAN do not support
any Layer 2 and Layer 3 protocol applications, including ARP and LACP.
z You cannot enable BFD MAD detection on VLAN interface 1.
z The MAD function is mutually exclusive with VPN; therefore, Layer 3 interfaces with BFD MAD
enabled cannot be bound with VPN.
z A MAD IP address and a common IP address are not mutually interfered; they can coexist: the
MAD IP address automatically becomes the slave address after being configured, and the common
IP address becomes the primary address.
z If an IRF virtual device configured with the BFD MAD function is divided into two IRF virtual devices,
routing collision information (for example, %May 5 16:15:47:733 2010 H3C
ARP/3/ROUTECONFLICT:Chassis=2-Slot=5;Route conflict found, IP:192.168.2.1,
VrfIndex:0)may be generated because the new IRF virtual devices still keep the forwarding entries
with the destination being the original master device. This collision information does not affect the
device forwarding and automatically stops to be generated with the aging of the forwarding entries.
Enabling LACP MAD detection
1) LACP MAD detection mechanism