H3C Technologies H3C SecPath F5020 - Manual (Page 58)

49
Step Command Remarks
7. Assign the port or the range
of ports to the ND MAD
VLAN.
• Assign the port to the VLAN as an
access port:
port access vlan vlan-id
• Assign the port to the VLAN as a
trunk port:
port trunk permit vlan vlan-id
• Assign the port to the VLAN as a
hybrid port:
port hybrid vlan vlan-id { tagged |
untagged }
The link type of ND MAD ports
can be access, trunk, or hybrid.
The default link type of a port is
access.
8. Return to system view. quit N/A
9. Enter VLAN interface view.
interface vlan-interface
vlan-interface-id
N/A
10. Assign the interface an IP
address.
ipv6 address
{ ipv6-address/pre-length | ipv6
address pre-length }
By default, no IPv6 address is
assigned to any VLAN interface.
11. Enable ND MAD. mad nd enable By default, ND MAD is disabled.
Excluding a port from the shutdown action upon detection of multi-active collision
By default, all ports except the console and IRF physical interfaces shut down automatically when the IRF
fabric transits to the Recovery state.
You can exclude a network port from the shutdown action for management or other special purposes. For
example:
• Exclude a port from the shutdown action so you can Telnet to the port for managing the device.
• Exclude a VLAN interface and its Layer 2 ports from the shutdown action so you can log in through
the VLAN interface.
To configure a port to not shut down when the IRF fabric transits to the Recovery state:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure a network port to
not shut down when the IRF
fabric transits to the
Recovery state.
mad exclude interface interface-type
interface-number
By default, all network ports on a
Recovery-state IRF fabric are shut
down, except for the IRF physical
interfaces and console port.
Recovering an IRF fabric
After the failed IRF link between two split IRF fabrics is recovered, log in to the inactive IRF fabric, and use
the reboot command to reboot all its members. If the irf auto-merge enable command has been
configured, the inactive IRF member devices automatically reboot after the failed link is recovered. After
these member devices join the active IRF fabric as subordinates, IRF merge is complete, as shown
in Figure 16 .