Field	Description
MemberID	IRF member ID: · ID of the master is prefixed with an asterisk (*) sign. · ID of the device where you are logged in is prefixed with a plus (+) sign.
Role	Role of the member device in the IRF fabric: · Standby—Subordinate device. · Master—Master device. · Loading—The device is loading software images.
Priority	IRF member priority.
CPU-Mac	MAC address of the CPU on the device.
Description	Description you have configured for the member device. · If no description is configured, this field displays a dashed line (---). · If the description exceeds the maximum number of characters that can be displayed, an ellipsis (…) is displayed in place of the exceeding text. To display the complete description, use the display current-configuration command.
Auto upgrade	Status of the software auto-update feature: · yes—Enabled. · no—Disabled.
Mac persistent	IRF bridge MAC persistence setting: · 6 min—Bridge MAC address of the IRF fabric remains unchanged for 6 minutes after the address owner leaves. · always—Bridge MAC address of the IRF fabric does not change after the address owner leaves. · no—Bridge MAC address of the current master replaces the original bridge MAC address as soon as the owner of the original address leaves.
IRF mode	IRF mode setting. · enhance—The IRF fabric operates in enhanced IRF mode. · normal—The IRF fabric operates in normal IRF mode. In this mode, IRF 3 is not supported.

Use display irf configuration to display basic IRF settings, including each member's current member ID, new member ID, and physical interfaces bound to the IRF ports. The new member IDs take effect at reboot.

Syntax

display irf configuration

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display all members' basic IRF settings.

<Sysname> display irf configuration

MemberID NewID IRF-Port1 IRF-Port2

1 1 Ten-GigabitEthernet1/1/1 disable

Ten-GigabitEthernet1/1/2

2 2 disable Ten-GigabitEthernet2/1/1

Ten-GigabitEthernet2/1/2

Table 2 Command output

Field	Description
MemberID	Current member ID of the device.
NewID	Member ID assigned to the device. This member ID takes effect at reboot.
IRF-Port1	Physical interfaces bound to IRF-port 1. The bindings take effect at reboot. This field displays disable if no physical interfaces are bound to the IRF port.
IRF-Port2	Physical interfaces bound to IRF-port 2. The bindings take effect at reboot. This field displays disable if no physical interfaces are bound to the IRF port.

display irf link

Use display irf link to display IRF link information, including IRF ports, IRF physical interfaces, and IRF link status.

Syntax

display irf link

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display IRF link information.

<Sysname> display irf link

Member 1

IRF Port Interface Status

1 disable --

2 Ten-GigabitEthernet1/1/1 UP

Ten-GigabitEthernet1/2/1 ADM

Ten-GigabitEthernet1/3/1 DOWN

Member 2

IRF Port Interface Status

1 Ten-GigabitEthernet2/1/1 UP

Ten-GigabitEthernet2/2/1 DOWN

Ten-GigabitEthernet2/3/1 ADM

2 disable --

Table 3 Command output

Field	Description
Member ID	IRF member ID.
IRF Port	IRF port number: · 1—IRF-port 1. · 2—IRF-port 2.
Interface	Physical interfaces bound to the IRF port. This field displays disable if no physical interfaces have been bound to the IRF port.
Status	Link state of the IRF physical interface: · UP—The link is up. · DOWN—The link is down. · ADM—The interface has been manually shut down by using the shutdown command. · ABSENT—The interface does not exist.

display irf topology

Use display irf topology to display IRF fabric topology information, including the member IDs, IRF port state, adjacencies of IRF ports, and CPU MAC address of the master.

Syntax

display irf topology

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display the IRF fabric topology.

<Sysname> display irf topology

Topology Info

-------------------------------------------------------------------------

IRF-Port1 IRF-Port2

MemberID Link neighbor Link neighbor Belong To

3 DIS --- DOWN --- 00e0-fc0f-8c08

Table 4 Command output

Field	Description
IRF-Port 1	Information about IRF-port 1, including its link state and neighbor.
IRF-Port 2	Information about IRF-port 2, including its link state and neighbor.
Link	Link state of the IRF port: · UP—The IRF link is up. · DOWN—The IRF link is down. · DIS—No physical interfaces have been bound to the IRF port. · TIMEOUT—IRF hello interval has timed out. · ISOLATE—The device is isolated from the IRF fabric. This issue might be caused by the following reasons: ¡ The IRF fabric does not support the device model. ¡ The maximum number of member devices has exceeded the upper limit.
neighbor	IRF member ID of the device connected to the IRF port. If no device is connected to the IRF port, this field displays three hyphens (---).
Belong To	IRF fabric that has the device, represented by the CPU MAC address of the master in the IRF fabric.

display irf-port load-sharing mode

Use display irf-port load-sharing mode to display load sharing mode for IRF links.

Syntax

display irf-port load-sharing mode [ irf-port [ member-id/irf-port-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

irf-port: Displays IRF port-specific load sharing modes. If you do not specify this keyword, the command displays the global load sharing mode for IRF links.

member-id/irf-port-number: Specifies an IRF port number. The member-id argument represents an IRF member ID. The irf-port-number argument represents the index number (1 or 2) of the IRF port on the member device. If you do not specify the member-id and irf-port-number arguments, this command displays the load sharing mode used on each IRF port in the IRF fabric. If no IRF ports are in up state, this command displays No IRF link exists.

Examples

# Display the global load sharing mode for IRF links. In this example, because no user-defined global load sharing mode has been configured, the default global load sharing mode applies.

<Sysname> display irf-port load-sharing mode

irf-port Load-Sharing Mode:

Layer 2 traffic: destination-mac address source-mac address

Layer 3 traffic: destination-ip address source-ip address

Layer 4 traffic: destination-port source-port

# Display the load sharing mode of IRF-port 1/1. In this example, because neither port-specific load sharing mode nor user-defined global load sharing mode has been configured, the default global load sharing mode applies.

<Sysname> display irf-port load-sharing mode irf-port 1/1

irf-port1/1 Load-Sharing Mode:

Layer 2 traffic: destination-mac address, source-mac address

Layer 3 traffic: destination-ip address, source-ip address

Layer 4 traffic: destination-port, source-port

# Display the load sharing mode used on each IRF port.

<Sysname> display irf-port load-sharing mode irf-port

irf-port 1/1 Load-Sharing Mode:

destination-mac address

Table 5 Command output

Field	Description
irf-port Load-Sharing Mode	Global load sharing mode for IRF links: · If no global IRF link load sharing mode has been configured, the default global load sharing mode applies. · If a user-defined global load sharing mode has been configured, the configured mode applies.
irf-port1/1 Load-Sharing Mode	Link load sharing mode of IRF-port 1/1: · If you have not configured a port-specific load sharing mode, the global IRF link load sharing mode applies. · If you have configured a port-specific load sharing mode, the configured mode applies.
Layer 2 traffic: destination-mac address source-mac address	Default load sharing mode for traffic that has no IP header. By default, this type of traffic is distributed based on source and destination MAC addresses.
Layer 3 traffic: destination-ip address source-ip address	Default load sharing mode for non-TCP/-UDP IP packets. By default, this type of traffic is distributed based on source and destination IP addresses.
Layer 4 traffic: destination-port source-port	Default load sharing mode for TCP/UDP packets. By default, this type of traffic is distributed based on source and destination port numbers.
destination-mac address	Configured load sharing mode of IRF-port 1/1. Packets are distributed based on their destination MAC addresses.

display mad

Use display mad to display MAD status and settings.

Syntax

display mad [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

verbose: Displays detailed MAD information. If you do not specify this keyword, the command only displays whether a MAD mechanism is enabled or disabled.

Examples

# Display brief MAD information.

<Sysname> display mad

MAD ARP disabled.

MAD ND disabled.

MAD LACP disabled.

MAD BFD disabled.

# Display detailed MAD information.

<Sysname> display mad verbose

Multi-active recovery state: No

Excluded ports (user-configured):

Excluded ports (system-configured):

FortyGigE4/2/26

FortyGigE6/2/26

Pex103/0/51

Pex103/0/52

Ten-GigabitEthernet4/1/1

Ten-GigabitEthernet4/1/24

Ten-GigabitEthernet6/1/1

MAD ARP disabled.

MAD ND disabled.

MAD LACP disabled.

MAD BFD disabled.

Table 6 Command output

Field	Description
Multi-active recovery state	Whether the IRF fabric is in Recovery state. · Yes—The IRF fabric is in Recovery state. When MAD detects that an IRF fabric has split into multiple IRF fabrics, it allows one fabric to forward traffic. All the other IRF fabrics are set to the Recovery state. In Recovery state, MAD shuts down all physical ports in the fabric except for the IRF physical interfaces and ports configured to not shut down. · No—The IRF fabric is not in Recovery state. The fabric is active and can forward traffic.
Excluded ports (user-configured)	Ports manually configured to not shut down when the IRF fabric transits to the Recovery state.
Excluded ports (system-configured)	Ports set to not shut down by default when the IRF fabric transits to the Recovery state.
MAD status	MAD link status: · Normal—The MAD link is operating correctly. · Faulty—The MAD link is faulty. Check the interface or port for connectivity or configuration problems. · N/A—MAD link status cannot be detected. This field always displays N/A if BFD MAD is enabled on a management Ethernet port.
Member ID	IRF member ID of the local device.
Port	Member ports of the aggregate interface used for LACP MAD.
Neighbor	IRF member ID of the neighbor member device.

irf auto-update enable

Use irf auto-update enable to enable the software auto-update feature.

Use undo irf auto-update enable to disable the software auto-update feature.

Syntax

irf auto-update enable

undo irf auto-update enable

Default

The software auto-update feature is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command automatically propagates the current software images of the master device in the IRF fabric to any devices you are adding to the IRF fabric.

To ensure a successful software update, verify that the new device you are adding to the IRF fabric has sufficient storage space for the new software images. If sufficient storage space is not available, the device automatically deletes the current software images. If the reclaimed space is still insufficient, the device cannot complete the auto-update. You must reboot the device, and then access the BootWare menus to delete files.

You must manually update the new device with the software images running on the IRF fabric if software auto-update is disabled.

Examples

# Enable the software auto-update feature.

<Sysname> system-view

[Sysname] irf auto-update enable

irf domain

Use irf domain to assign a domain ID to an IRF fabric.

Use undo irf domain to restore the default IRF domain setting.

Syntax

irf domain domain-id

undo irf domain

Default

The IRF domain ID is 0.

Views

System view

Predefined user roles

network-admin

Parameters

domain-id: Specifies a domain ID for the IRF fabric. The value range is 0 to 4294967295.

Usage guidelines

One IRF fabric forms one IRF domain. IRF uses IRF domain IDs to uniquely identify IRF fabrics and prevent IRF fabrics from interfering with one another.

If one IRF fabric uses another IRF fabric as the intermediate device for LACP MAD, ARP MAD or ND MAD, you must assign the two IRF fabrics different domain IDs for correct split detection. False detection causes IRF split.

An IRF fabric has only one IRF domain ID. You can change the IRF domain ID by using the following commands: irf domain, mad enable, mad arp enable, or mad nd enable. The IRF domain IDs configured by using these commands overwrite each other.

Examples

# Set the IRF domain ID to 30.

<Sysname> system-view

[Sysname] irf domain 30

irf link-delay

Use irf link-delay to set a delay for the IRF ports to report a link down event.

Use undo irf link-delay to restore the default.

Syntax

irf link-delay interval

undo irf link-delay

Default

The IRF link down event report delay is 1 second.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Sets the IRF link down report delay in the range of 0 to 10000 milliseconds. If the interval is set to 0, link down events are reported without any delay. The greater the interval, the slower the service recovery.

Usage guidelines

If the CFD or BFD feature is used in the IRF fabric, make sure the delay interval is shorter than the maximum CCM lifetime and BFD session lifetime. For more information about CFD and BFD, see High Availability Configuration Guide.

As a best practice, set the delay to 0 seconds in the following situations:

· The IRF fabric requires a quick master/subordinate or IRF link switchover.

· The BFD, BFD MAD, GR, or RRPP feature is used.

Examples

# Set the IRF link down report delay to 300 milliseconds.

<Sysname> system-view

[Sysname] irf link-delay 300

irf mac-address persistent

Use irf mac-address persistent to configure IRF bridge MAC persistence.

Use undo irf mac-address persistent to enable the IRF fabric to change its bridge MAC address as soon as the address owner leaves.

Syntax

irf mac-address persistent { always | timer }

undo irf mac-address persistent

Default

Bridge MAC address of the IRF fabric does not change after the address owner leaves.

Views

System view

Predefined user roles

network-admin

Parameters

always: Enables the IRF bridge MAC address to be permanent. The IRF bridge MAC address does not change after the address owner leaves.

timer: Enables the IRF bridge MAC address to remain unchanged for 6 minutes after the address owner leaves. If the address owner rejoins the IRF fabric within the time limit, the IRF bridge MAC address does not change. If the address owner does not rejoin within the time limit, the IRF fabric uses the bridge MAC address of the current master as the bridge MAC address.

Usage guidelines

IRF bridge MAC persistence specifies the amount of time an IRF fabric can continue using a bridge MAC address as its bridge MAC address after the address owner leaves.

To prevent traffic interruption, follow these restrictions and guidelines:

· If ARP MAD or ND MAD is used, execute the undo irf mac-address persistent command to disable IRF bridge MAC persistence.

· If TRILL is configured, configure the irf mac-address persistent always command to disable IRF bridge MAC change. The persistence setting ensures that other devices in the TRILL network can maintain correct network topology after the address owner leaves.

If two IRF fabrics have the same bridge MAC address, they cannot merge.

Examples

# Enable the IRF bridge MAC address to be permanent.

<Sysname> system-view

[Sysname] irf mac-address persistent always

irf member description

Use irf member description to configure a description for an IRF member device.

Use undo irf member description to restore the default.

Syntax

irf member member-id description text

undo irf member member-id description

Default

No description is configured for an IRF member device.

Views

System view

Predefined user roles

network-admin

Parameters

member-id: Specifies the ID of an IRF member device, in the range of 1 to 10.

text: Configures a description, a string of 1 to 127 characters.

Usage guidelines

Configure a description to describe the location or purpose of a member device.

Examples

# Configure a description for IRF member 1.

<Sysname> system-view

[Sysname] irf member 1 description F1Num001

irf member priority

Use irf member priority to change the priority of an IRF member device.

Use undo irf member priority to restore the default.

Syntax

irf member member-id priority priority

undo irf member member-id priority

Default

The IRF member priority is 1.

Views

System view

Predefined user roles

network-admin

Parameters

member-id: Specifies an IRF member ID in the range of 1 to 10.

priority: Sets a priority in the range of 1 to 32. The greater the priority value, the higher the priority. A member with higher priority is more likely to be the master.

Usage guidelines

The new priority setting takes effect at the next master election, but it does not trigger a master election.

Examples

# Set the priority of IRF member 2 to 32.

<Sysname> system-view

[Sysname] irf member 2 priority 32

irf member renumber

Use irf member renumber to change the IRF member ID of a device.

Use undo irf member renumber to restore the previous IRF member ID of the device.

Syntax

irf member member-id renumber new-member-id

undo irf member member-id renumber

Default

The IRF member ID is 1.

Views

System view

Predefined user roles

network-admin

Parameters

member-id: Specifies the ID of an IRF member device, in the range of 1 to 10.

new-member-id: Assigns a new ID to the IRF member device, in the range of 1 to 10.

Usage guidelines

CAUTION:

An IRF member ID change can invalidate member ID-related settings, including interface and file path settings, and cause data loss. Make sure you fully understand its impact on your live network.

The new IRF member ID, including the one set by using the undo irf member renumber command, takes effect after you reboot the member device.

Interchanging member IDs between IRF member devices might cause undesirable configuration changes and data loss. For example, the IRF member IDs of Device A and Device B are 2 and 3, respectively. After you interchange their member IDs, their port settings also interchange.

Examples

# Change the member ID of an IRF member from 2 to 4.

<Sysname> system-view

[Sysname] irf member 2 renumber 4

Renumbering the member ID may result in configuration change or loss. Continue?[Y/N]y

# Before rebooting the device, cancel the change in the preceding example.

[Sysname] undo irf member 2 renumber

Renumbering the member ID may result in configuration change or loss. Continue?[Y/N]y

If you reboot the device after executing the irf member 2 renumber 4 command, the device member ID changes to 4 at system reboot. Using undo irf member 2 renumber cannot restore the member ID to 2.

irf-port

Use irf-port to enter IRF port view.

Use undo irf-port to removing all port bindings on an IRF port.

Syntax

irf-port member-id/port-number

undo irf-port member-id/port-number

Views

System view

Predefined user roles

network-admin

Parameters

member-id/port-number: Specifies an IRF port on an IRF member device. The member-id argument represents the ID of the IRF member device. The port-number argument represents the IRF port index and must be 1 or 2.

Usage guidelines

To bind physical interfaces to an IRF port, you must enter IRF port view.

Before you remove all port bindings on an IRF port, shut down all its physical interfaces.

Examples

# Enter the view of IRF-port 1 on member 1.

<Sysname> system-view

[Sysname] irf-port 1/1

Related commands

port group interface

irf-port global load-sharing mode

Use irf-port global load-sharing mode to set the global load sharing mode for IRF links.

Use undo irf-port global load-sharing mode to restore the default.

Syntax

irf-port global load-sharing mode { destination-ip | destination-mac | ingress-port | source-ip | source-mac } *

undo irf-port global load-sharing mode

Default

The following are criteria for distributing different types of packets across IRF links:

· TCP/UDP packets—Source and destination TCP/UDP port numbers.

· Non-TCP/-UDP IP packets—Source and destination IP addresses.

· Non-IP packets (packets without an IP header)—Source and destination MAC addresses.

Views

System view

Predefined user roles

network-admin

Parameters

destination-ip: Distributes traffic across IRF member links based on destination IP address.

destination-mac: Distributes packets across IRF member links based on destination MAC address.

ingress-port: Distributes packets across IRF member links based on incoming port. This keyword is not supported in the current software version.

source-ip: Distributes packets across IRF member links based on source IP address.

source-mac: Distributes packets across IRF member links based on source MAC address.

Usage guidelines

The global IRF link load sharing mode applies to all IRF ports in the IRF fabric. You can configure the sharing mode to include a combination of multiple criteria for making traffic distribution decisions. If your device does not support a criterion combination, the system displays an error message.

If you configure the global load sharing mode multiple times, the most recent configuration takes effect.

You can also configure a port-specific load sharing mode for an IRF port in IRF port view by using the irf-port load-sharing mode command.

An IRF port preferentially uses the port-specific load sharing mode. If no port-specific load sharing mode is available, the port uses the global load sharing mode.

Examples

# Configure the global IRF link load sharing mode to distribute traffic based on destination MAC address.

<Sysname> system-view

[Sysname] irf-port global load-sharing mode destination-mac

Related commands

irf-port load-sharing mode

Use irf-port load-sharing mode to configure a port-specific load sharing mode for an IRF port to distribute traffic across its physical links.

Use undo irf-port load-sharing mode to restore the default.

Syntax

irf-port load-sharing mode { destination-ip | destination-mac | ingress-port | source-ip | source-mac } *

undo irf-port load-sharing mode

Default

The following are criteria for distributing different types of packets across IRF links:

· TCP/UDP packets—Source and destination TCP/UDP port numbers.

· Non-TCP/-UDP IP packets—Source and destination IP addresses.

· Non-IP packets (packets without an IP header)—Source and destination MAC addresses.

Views

IRF port view

Predefined user roles

network-admin

Parameters

destination-ip: Distributes traffic across IRF member links based on destination IP address.

destination-mac: Distributes packets across IRF member links based on destination MAC address.

ingress-port: Distributes packets across IRF member links based on incoming port. This keyword is not supported in the current software version.

source-ip: Distributes packets across IRF member links based on source IP address.

source-mac: Distributes packets across IRF member links based on source MAC address.

Usage guidelines

To successfully configure a port-specific load sharing mode for an IRF port, make sure you have bound a minimum of one physical interface to the IRF port.

You can configure an IRF port-specific load sharing mode to include a combination of multiple criteria for making traffic distribution decisions. If your device does not support a criterion combination, the system displays an error message.

If you configure the port-specific load sharing mode multiple times on an IRF port, the most recent configuration takes effect.

An IRF port preferentially uses the port-specific load sharing mode. If no port-specific load sharing mode is available, the port uses the global load sharing mode.

Examples

# Configure a port-specific load sharing mode for IRF-port 1/1 to distribute traffic based on destination MAC address.

<Sysname> system-view

[Sysname] irf-port 1/1

[Sysname-irf-port1/1] irf-port load-sharing mode destination-mac

Related commands

irf-port global load-sharing mode

irf-port-configuration active

Use irf-port-configuration active to activate IRF port settings.

Syntax

irf-port-configuration active

Views

System view

Predefined user roles

network-admin

Usage guidelines

After connecting the physical interfaces between two devices and binding them to the correct IRF ports, you must use this command to activate the settings on the IRF ports. This command merges the two devices into one IRF fabric.

The system activates the IRF port settings automatically in the following situations:

· The configuration file that the device starts with contains IRF port bindings.

· You are binding physical interfaces to an IRF port after an IRF fabric is formed.

Examples

To configure and activate IRF-port 1/2:

# Bind Ten-GigabitEthernet 1/1/7 to IRF-port 1/2.

<Sysname> system-view

[Sysname] interface ten-gigabitEthernet 1/1/7

[Sysname-Ten-GigabitEthernet1/1/7] shutdown

[Sysname-Ten-GigabitEthernet1/1/7] quit

[Sysname] irf-port 1/2

[Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/1/7

You must perform the following tasks for a successful IRF setup:

Save the configuration after completing IRF configuration.

Execute the "irf-port-configuration active" command to activate the IRF ports.

[Sysname-irf-port1/2] quit

[Sysname] interface ten-gigabitEthernet 1/1/7

[Sysname-Ten-GigabitEthernet1/1/7] undo shutdown

[Sysname-Ten-GigabitEthernet1/1/7] quit

# Save the configuration so the IRF port settings can take effect after the device reboots.

[Sysname] save

The current configuration will be written to the device. Are you sure? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait............................

Saved the current configuration to mainboard device successfully.

Slot 1:

Save next configuration file successfully.

Configuration is saved to device successfully.

# Activate the IRF port settings.

[Sysname] irf-port-configuration active

mad arp enable

Use mad arp enable to enable ARP MAD.

Use undo mad arp enable to disable ARP MAD.

Syntax

mad arp enable

undo mad arp enable

Default

ARP MAD is disabled.

Views

Management Ethernet interface view, VLAN interface view

Predefined user roles

network-admin

Usage guidelines

ARP MAD detects multi-active collisions by using extended ARP packets.

You can use ARP MAD with ND MAD, but not with LACP MAD or BFD MAD.

· ARP MAD handles collisions differently than LACP MAD.

· ARP MAD requires the spanning tree feature, but BFD MAD is exclusive with the spanning tree feature.

When you configure ARP MAD that uses common Ethernet ports, follow these restrictions and guidelines:

Category	Restrictions and guidelines
ARP MAD VLAN	· Do not enable ARP MAD on VLAN-interface 1. · If you are using an intermediate device, perform the following tasks on both the IRF fabric and the intermediate device: ¡ Create a VLAN and VLAN interface for ARP MAD. ¡ Assign the ports of ARP MAD links to the ARP MAD VLAN. · As a best practice, do not use the ARP MAD VLAN for any other purposes.
ARP MAD and feature configuration	If an intermediate device is used, make sure the following requirements are met: · Run the spanning tree feature between the IRF fabric and the intermediate device to ensure that there is only one ARP MAD link in forwarding state. For more information about the spanning tree feature and its configuration, see Layer 2—LAN Switching Configuration Guide. · Enable the IRF fabric to change its bridge MAC address as soon as the address owner leaves. · If the intermediate device is also an IRF fabric, assign the two IRF fabrics different domain IDs for correct split detection.

Category	Restrictions and guidelines
Ports on the intermediate device for ARP MAD	Use common Ethernet ports on the intermediate device to connect the management Ethernet ports on the IRF fabric.
ARP MAD VLAN	On the intermediate device, create a VLAN for ARP MAD, and assign the ports used for ARP MAD to the VLAN. On the IRF fabric, you do not need to assign the management Ethernet ports to the VLAN.
ARP MAD and feature configuration	· Enable the IRF fabric to change its bridge MAC address as soon as the address owner leaves. · If the intermediate device is also an IRF fabric, assign the two IRF fabrics different domain IDs for correct split detection.

mad bfd enable

Use mad bfd enable to enable BFD MAD.

Use undo mad bfd enable to disable BFD MAD.

Syntax

mad bfd enable

undo mad bfd enable

Default

BFD MAD is disabled.

Views

Management Ethernet interface view, VLAN interface view

Predefined user roles

network-admin

Usage guidelines

BFD MAD uses the BFD protocol to detect multi-active collisions. This MAD mechanism can work with or without intermediate devices.

You cannot use BFD MAD with LACP MAD, ARP MAD, or ND MAD.

· BFD MAD handles collisions differently than LACP MAD.

· BFD MAD is exclusive with the spanning tree feature, but ARP MAD and ND MAD require the spanning tree feature.

When you configure BFD MAD on a VLAN interface, follow these guidelines:

Category	Restrictions and guidelines
BFD MAD VLAN	· Do not enable BFD MAD on VLAN-interface 1. · If you are using an intermediate device, create the VLAN and VLAN interface on both the IRF fabric and the intermediate device. Assign the ports of BFD MAD links to the BFD MAD VLAN on both the IRF fabric and the intermediate device. · Make sure the IRF fabrics on the network use different BFD MAD VLANs.
BFD MAD VLAN and feature compatibility	Do not use the BFD MAD VLAN for any purpose other than configuring BFD MAD. · Configure only the mad bfd enable and mad ip address commands on the BFD MAD-enabled VLAN interface. If you configure other features, both BFD MAD and other features on the interface might run incorrectly. · Disable the spanning tree feature on any Layer 2 Ethernet ports in the BFD MAD VLAN. The MAD feature is mutually exclusive with the spanning tree feature. · Do not bind a BFD MAD-enabled VLAN interface to a VPN instance. The MAD feature is mutually exclusive with VPN.
MAD IP address	· To avoid problems, only use the mad ip address command to configure IP addresses on the BFD MAD-enabled VLAN interface. Do not configure an IP address by using the ip address command or configure a VRRP virtual address on the BFD MAD-enabled VLAN interface. · Make sure all the MAD IP addresses are on the same subnet. · MAD IP addresses must be unique among all IP addresses on the IRF fabric.
BFD MAD and IRF link down report delay restrictions	Set the IRF link down report delay to 0 seconds to avoid unnecessary recalculations.

When you use BFD MAD on management Ethernet ports, follow these restrictions and guidelines:

Category	Restrictions and guidelines
Ports on the intermediate device for BFD MAD	If you are using an intermediate device, use common Ethernet ports on the intermediate device to set up BFD MAD links.
BFD MAD VLAN	· On the intermediate device (if any), create a VLAN for BFD MAD, and assign the ports used for BFD MAD to the VLAN. On the IRF fabric, you do not need to assign the BFD MAD-enabled management Ethernet ports to the VLAN. · As a best practice, do not configure other features on the VLAN used for BFD MAD for successful detection. · Make sure the IRF fabrics on the network use different BFD MAD VLANs.
BFD MAD-enabled management Ethernet port and feature compatibility	Do not bind a BFD MAD-enabled management Ethernet port to a VPN instance. The MAD feature is mutually exclusive with VPN.
MAD IP address	· Use the mad ip address command instead of the ip address command to configure MAD IP addresses on the BFD MAD-enabled management Ethernet ports. · Make sure all the MAD IP addresses are on the same subnet. · MAD IP addresses must be unique among all IP addresses on the IRF fabric.
BFD MAD and IRF link down report delay restrictions	Set the IRF link down report delay to 0 seconds to avoid unnecessary recalculations.

Examples

# Enable BFD MAD on VLAN-interface 3.

<Sysname> system-view

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] mad bfd enable

mad enable

Use mad enable to enable LACP MAD.

Use undo mad enable to disable LACP MAD.

Syntax

mad enable

undo mad enable

Default

LACP MAD is disabled.

Views

Aggregate interface view

Predefined user roles

network-admin

Usage guidelines

LACP MAD uses extended LACP packets to detect multi-active collisions. This MAD mechanism requires an intermediate H3C device that supports extended LACPDUs.

LACP MAD handles collisions differently than BFD MAD, ARP MAD, and ND MAD. To avoid conflicts, do not enable LACP MAD together with any of those mechanisms in an IRF fabric.

You must set up a dynamic link aggregation group that spans all IRF member devices between the IRF fabric and the intermediate device. To enable dynamic link aggregation, configure the link-aggregation mode dynamic command on the aggregate interface.

If one IRF fabric uses another IRF fabric as the intermediate device for LACP MAD, you must assign the two IRF fabrics different domain IDs for correct split detection. False detection causes IRF split.

When you use the mad enable command, the system prompts you to enter a domain ID. If you do not want to change the current domain ID, press enter at the prompt.

NOTE:

Examples

# Enable LACP MAD on Bridge-Aggregation 1, a Layer 2 dynamic aggregate interface.

<Sysname> system-view

[Sysname] interface bridge-aggregation 1

[Sysname-Bridge-Aggregation1] link-aggregation mode dynamic

[Sysname-Bridge-Aggregation1] mad enable

You need to assign a domain ID (range: 0-4294967295)

[Current domain is: 0]: 1

The assigned domain ID is: 1

MAD LACP only enable on dynamic aggregation interface.

# Enable LACP MAD on Route-Aggregation 1, a Layer 3 dynamic aggregate interface.

<Sysname> system-view

[Sysname] interface route-aggregation 1

[Sysname-Route-Aggregation1] link-aggregation mode dynamic

[Sysname-Route-Aggregation1] mad enable

You need to assign a domain ID (range: 0-4294967295)

[Current domain is: 0]: 1

The assigned domain ID is: 1

MAD LACP only enable on dynamic aggregation interface.

mad exclude interface

Use mad exclude interface to exclude a physical network port from being shut down when the IRF fabric transits to the Recovery state upon detection of a multi-active collision.

Use undo mad exclude interface to restore the default MAD action on a physical network port.

Syntax

mad exclude interface interface-type interface-number

undo mad exclude interface interface-type interface-number

Default

All physical network ports but the IRF physical interfaces and console port shut down when the IRF fabric transits to the Recovery state.

Views

System view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies a port by its type and number.

Usage guidelines

MAD action is not configurable for IRF physical interfaces.

When MAD detects a multi-active collision, it sets all IRF fabrics except one to the Recovery state. The fabric that is not placed in Recovery state can continue to forward traffic. The Recovery-state IRF fabrics are inactive. MAD shuts down all their physical ports except the IRF physical interfaces and the ports manually configured to not shut down.

If a port must be kept in up state for special purposes such as Telnet connection, exclude the port from the shutdown action. As a best practice to avoid incorrect traffic forwarding, do not exclude any ports except for the ports used for Telnet and MAD. However, do not exclude the VLAN interface of BFD MAD and its Layer 2 member ports from being shut down.

The ports that have shut down by MAD come up when the member devices reboot to join the recovered IRF fabric. If auto recovery fails because the current master fails or any other exception occurs, use the mad restore command to manually recover the member devices and bring up the ports.

Examples

# Exclude Ten-GigabitEthernet 1/1/1 from being shut down when the MAD status transits to Recovery.

<Sysname> system-view

[Sysname] mad exclude interface ten-gigabitethernet 1/1/1

mad ip address

Use mad ip address to assign a MAD IP address to an IRF member device for BFD MAD.

Use undo mad ip address to delete the MAD IP address for an IRF member device.

Syntax

mad ip address ip-address { mask | mask-length } member member-id

undo mad ip address ip-address { mask | mask-length } member member-id

Default

No MAD IP address is configured for an IRF member device.

Views

Management Ethernet interface view, VLAN interface view

Predefined user roles

network-admin

Parameters

ip-address: Specifies an IP address in dotted decimal notation. This IP address is bound to an IRF member for BFD detection and is called a MAD IP address.

mask: Specifies a subnet mask in dotted decimal notation.

mask-length: Specifies a subnet mask in length, in the range of 0 to 32.

member member-id: Specifies an IRF member ID.

Usage guidelines

To use BFD MAD, configure a MAD IP address for each IRF member. Make sure all the MAD IP addresses are on the same subnet and are unique among all IP addresses on the IRF fabric.

To avoid problems, only use the mad ip address command to configure MAD IP addresses. Do not configure a MAD IP address by using the ip address command or configure a VRRP virtual address.

The master attempts to establish BFD sessions with other members by using its MAD IP address as the source IP address.

· When the IRF fabric is integrated, only the MAD IP address of the master takes effect. The master cannot establish a BFD session with any other member. If you execute the display bfd session command, the state of the BFD sessions is Down.

· When the IRF fabric splits, the IP addresses of the masters in the partitioned IRF fabrics take effect. The masters can establish a BFD session. If you execute the display bfd session command, the state of the BFD session between the two devices is Up.

Examples

# Assign a MAD IP address to IRF member 1 on VLAN-interface 3.

<Sysname> system-view

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] mad ip address 192.168.0.1 255.255.255.0 member 1

# Assign a MAD IP address to IRF member 2 on VLAN-interface 3.

[Sysname-Vlan-interface3] mad ip address 192.168.0.2 255.255.255.0 member 2

Related commands

mad bfd enable

mad nd enable

Use mad nd enable to enable ND MAD.

Use undo mad nd enable to disable ND MAD.

Syntax

mad nd enable

undo mad nd enable

Default

ND MAD is disabled.

Views

VLAN interface view

Predefined user roles

network-admin

Usage guidelines

ND MAD uses extended NS packets of the IPv6 ND protocol to detect multi-active collisions.

You can use ND MAD with ARP MAD, but not with LACP MAD or BFD MAD.

· ND MAD handles collisions differently than LACP MAD.

· ND MAD requires the spanning tree feature, but BFD MAD is exclusive with the spanning tree feature.

Do not configure ND MAD on VLAN-interface 1.

You can set up ND MAD links between neighbor IRF member devices, or between each IRF member device and an intermediate device.

If one IRF fabric uses another IRF fabric as the intermediate device for ND MAD, you must assign the two IRF fabrics different domain IDs for correct split detection. False detection causes IRF split.

When you use the mad nd enable command, the system prompts you to enter a domain ID. If you do not want to change the current domain ID, press enter at the prompt.

NOTE:

Examples

# Enable ND MAD on VLAN-interface 3.

<Sysname> system-view

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] mad nd enable

You need to assign a domain ID (range: 0-4294967295)

[Current domain is: 0]: 1

The assigned domain ID is: 1

Related commands

irf domain

mad restore

Use mad restore to restore the normal MAD state of the IRF fabric in Recovery state.

Syntax

mad restore

Views

System view

Predefined user roles

network-admin

Usage guidelines

If the active IRF fabric has failed to work before the IRF split problem is fixed, use this command to restore an IRF fabric in Recovery state. The recovered IRF fabric will take over the active IRF fabric role.

Examples

# Restore the normal MAD state of the IRF fabric in Recovery state.

<Sysname> system-view

[Sysname] mad restore

This command will restore the device from multi-active conflict state. Continue? [Y/N]:Y

Restoring from multi-active conflict state, please wait...

port group interface

Use port group interface to bind a physical interface to an IRF port.

Use undo port group interface to remove the binding of a physical interface and an IRF port.

Syntax

port group [ mdc mdc-name ] interface interface-type interface-number [ mode { enhanced | extended } ]

undo port group [ mdc mdc-name ] interface interface-name

Default

No physical interfaces are bound to an IRF port.

Views

IRF port view

Predefined user roles

network-admin

Parameters

mdc mdc-name: Specifies an MDC name, a case-sensitive string of 1 to 15 characters. This option is not supported in the current software version.

interface-type interface-number: Specifies a physical interface by its type and number.

interface-name: Specifies a physical interface in the interface-typeinterface-number format. No space is allowed between the interface-type and interface-number arguments.

mode: Specifies a binding mode for the IRF physical interface. If you do not specify this keyword, the command binds the physical interface to an IRF port in enhanced mode.

· enhanced: Sets the binding mode to enhanced.

· extended: Sets the binding mode to extended. Specify this binding mode if optical transmission devices are deployed on the IRF link. This keyword is not supported in the current software version.

Usage guidelines

Use the shutdown command to shut down a physical interface before you bind it to or remove it from an IRF port. To bring up the physical interface after a binding or binding removal operation, use the undo shutdown command.

Repeat the port group interface command to bind a maximum of eight physical interfaces to an IRF port for link redundancy.

The binding mode takes effect only after the IRF binding takes effect.

The system does not dynamically remove IRF port bindings when IRF links are lost, for example, because an expansion interface card is removed. To remove IRF port bindings, you must use the undo port group interface command.

For more information about IRF port binding requirements, see Virtual Technologies Configuration Guide.

Examples

# Bind Ten-GigabitEthernet 1/1/1 to IRF-port 1 of member 1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/1/1

[Sysname-Ten-GigabitEthernet1/1/1] shutdown

[Sysname-Ten-GigabitEthernet1/1/1] quit

[Sysname] irf-port 1/1

[Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/1/1

You must perform the following tasks for a successful IRF setup:

Save the configuration after completing IRF configuration.

Execute the "irf-port-configuration active" command to activate the IRF ports.

[Sysname-irf-port1/1] quit

[Sysname] interface ten-gigabitethernet 1/1/1

[Sysname-Ten-GigabitEthernet1/1/1] undo shutdown

Related commands

irf-port

IRF 3 commands

For information about displaying and specifying PEX startup software images, see software upgrade in Fundamentals Command Reference.

associate

Use associate to assign a virtual slot number to a PEX.

Use undo associate to remove the virtual slot number assignment for a PEX.

Syntax

associate slot-number

undo associate

Default

A PEX is not assigned a virtual slot number.

Views

PEX port view

Predefined user roles

network-admin

Parameters

slot-number: Specifies a virtual slot number in the range of 100 to 219.

Usage guidelines

You must assign a unique virtual slot number to each PEX.

You cannot change the slot number of a PEX while it is starting up.

An operating PEX will reboot if you change or remove its slot number.

Examples

# Assign slot number 100 to the PEX attached to PEX port 2.

<Sysname> system-view

[Sysname] pex-port 2

[Sysname-pex-port2] associate 100

description

Use description to configure a description for a PEX port.

Use undo description to restore the default description.

Syntax

description text

undo description

Default

PEX port description uses the pex-port pex-number format (for example, pex-port 0002).

Views

PEX port view

Predefined user roles

network-admin

Parameters

text: Configures a description, a case-sensitive string of 1 to 79 characters.

Examples

# Configure a description for PEX port 2.

<Sysname> system-view

[Sysname] pex-port 2

[Sysname-pex-port2] description connecttodep2

display pex working-mode

Use display pex working-mode to display the operating mode configuration of PEXs in the IRF 3 system.

Syntax

display pex working-mode { all | slot slot-number1 [ to slot-number2 ] }

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

all: Specifies all PEXs.

slot slot-number1: Specifies a PEX by its virtual slot number.

slot slot-number1 to slot-number2: Specifies a range of PEXs. The slot-number1 argument represents the start PEX slot number. The slot-number2 argument represents the end PEX slot number. The value for the slot-number2 argument must be greater than or equal to the value for the slot-number1 argument.

Examples

# Display the operating mode configuration of all PEXs.

<Sysname> display pex working-mode all

PEX device mode Configuration:

Switch mode at startup:

None

PEX mode at startup:

Slots 129

Table 7 Command output

Field	Description
PEX device mode Configuration	Displays the operating mode configuration for PEXs.
Switch mode at startup	Displays the virtual slot number information for PEXs that will operate in switch mode after a reboot.
PEX mode at startup	Displays the virtual slot number information for PEXs that will operate in PEX mode after a reboot.
Slots 129	PEX in slot 129.

display pex-port

Use display pex-port to display information about PEX ports.

Syntax

display pex-port [ pex-id ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

pex-id: Specifies the port number of a PEX port. If you do not specify a PEX port, the command displays information about all PEX ports.

verbose: Displays detailed information about PEX ports. If you do not specify this keyword, the command displays brief information about PEX ports.

Examples

# Display brief information about all PEX ports.

<Sysname> display pex-port

PEX port 1:

Description: pex-port 0001

Associated slot numbers: 1

Slot PEX status

*100 Online

PEX port 2:

Description: pex-port 0002

Associated slot numbers: 1

Slot PEX status

*101 Online

# Display detailed information about all PEX ports. In this example, PEX ports have member physical interfaces.

<Sysname> display pex-port verbose

PEX port 1:

Description: pex-port 0001

Associated slot numbers: 1

Slot PEX status

*100 Online

Member interfaces: 2

Member interface Status Peer interface

XGE1/2/1 Forwarding PEX100/0/27

XGE10/1/1 Down --

PEX port 2:

Description: pex-port 0002

Associated slot numbers: 1

Slot PEX status

*101 Online

Member interfaces: 3

Member interface Status Peer interface

XGE1/2/2 Forwarding PEX105/0/51

XGE9/2/2 Forwarding PEX105/0/52

XGE10/1/2 Down --

Table 8 Command output

Field	Description
Description	PEX port description.
Associated slot numbers	Number of virtual slot numbers for the PEX port.
Slot	Virtual slot number for the PEX port. If no virtual slot number is associated with the PEX port, this field displays No associated ID. The asterisk (*) indicates that the PEX is directly connected to the parent fabric.
PEX status	PEX status: · Online—The PEX is online. · Offline—The PEX is offline. · Loading—The PEX is starting up.
Member interfaces	Number of PEX physical interfaces assigned to the PEX port on the parent fabric.
Member interface	Physical interfaces assigned to the PEX port on the parent fabric.
Status	PEX link status: · Forwarding—The PEX link is operating correctly and can forward data traffic. · Down—The PEX link is disconnected and cannot forward any packets. · Blocked—The PEX link cannot forward any packets except for IRF 3 packets.
Peer interface	PEX physical interface on the PEX. This field displays two hyphens (--) if the system cannot obtain the interface name.
No member interface.	No physical interfaces have been assigned to the PEX port.

irf mode

Use irf mode to configure the IRF mode.

Use undo irf mode to restore the default.

Syntax

irf mode { enhanced | normal }

undo irf mode enhanced

Default

The device operates in normal IRF mode to provide IRF capability.

Views

System view

Predefined user roles

network-admin

Parameters

enhanced: Specifies enhanced IRF mode. In this mode, the device can operate as a parent device in an IRF 3 system.

normal: Specifies normal IRF mode. In this mode, IRF 3 capability is disabled. The device can only form an independent IRF fabric with other devices.

Usage guidelines

For a device to operate as a parent device, you must enable its IRF 3 capability by setting the IRF mode to enhanced. An IRF 3 system can contain a maximum of 2 parent devices and a maximum of 30 PEXs.

For the mode change to take effect, you must reboot the device.

Examples

# Enable enhanced IRF mode.

<Sysname> system-view

[Sysname] irf mode enhanced

Do you want to change the IRF capability? [Y/N]:y

IRF capability changed. For the setting to take effect, save the configuration,

and then reboot the device.

pex working-mode

Use pex working-mode to set the operating mode of PEXs.

Use undo pex working-mode to restore the default.

Syntax

pex working-mode switch { all | slot slot-number1 [ to slot-number2 ] }

undo pex working-mode { all | slot slot-number1 [ to slot-number2 ] }

Views

System view

Predefined user roles

network-admin

Parameters

switch: Specifies the switch operating mode. In this mode, the specified devices operate independently. It is not part of an IRF 3 system, whether or not it has connections to the parent fabric.

all: Specifies all PEXs.

slot slot-number1: Specifies a PEX by its virtual slot number.

Usage guidelines

This command does not change the current operating mode of specified PEXs. For the mode change to take effect, you must reboot the PEXs. After the PEXs reboot, you must save the configuration for the configuration to survive a reboot.

To cancel the mode change configuration, use the undo form of this command before you reboot the device. However, the undo command takes effect after the PEXs reboot.

Examples

# Set the operating mode to switch for the PEX in virtual slot 100.

<Sysname> system-view

[Sysname] pex working-mode switch slot 100

Are you sure you want to force a change to switch mode?[Y/N]: y

If you want to change PEX device to switch mode, you must reboot the device.

[Sysname] quit

<Sysname> reboot slot 100

pex-port

Use pex-port to create a PEX port and enter PEX port view. If the port has been created, the command only places you in PEX port view.

Use undo pex-port to delete a PEX port.

Syntax

pex-port pex-id

undo pex-port pex-id

Default

No PEX ports exist.

Views

System view

Predefined user roles

network-admin

Parameters

pex-id: Specifies a PEX port number in the range of 1 to 120.

Usage guidelines

For each PEX, you must create a unique PEX port on the parent fabric. All PEX settings for a PEX are configured on its PEX port.

Before you delete a PEX port, check its state. If the PEX port is in Online state, the delete operation will cause the attached PEX to reboot.

Examples

# Create PEX port 2.

<Sysname> system-view

[Sysname] pex-port 2

[Sysname-pex-port2]

pex-port load-sharing mode

Use pex-port load-sharing mode to configure the PEX link load sharing mode for a PEX port to distribute traffic across its physical links.

Use undo pex-port load-sharing mode to restore the default.

Syntax

pex-port load-sharing mode { destination-ip | destination-mac | ingress-port | source-ip | source-mac } *

undo pex-port load-sharing mode

Default

The following are criteria for distributing different types of packets across PEX links:

· TCP/UDP packets—Source and destination TCP/UDP port numbers.

· Non-TCP/-UDP IP packets—Source and destination IP addresses.

· Non-IP packets (packets without an IP header)—Source and destination MAC addresses.

Views

PEX port view

Predefined user roles

network-admin

Parameters

destination-ip: Distributes traffic across PEX member links based on destination IP address.

destination-mac: Distributes packets across PEX member links based on destination MAC address.

ingress-port: Distributes packets across PEX member links based on incoming port. This keyword is not supported in the current software version.

source-ip: Distributes packets across PEX member links based on source IP address.

source-mac: Distributes packets across PEX member links based on source MAC address.

Usage guidelines

To successfully configure the PEX link load sharing mode for a PEX port, make sure you have bound a minimum of one physical interface to the PEX port.

You can configure a PEX link load sharing mode to include a combination of multiple criteria for making traffic distribution decisions. If your device does not support a criterion combination, the system displays an error message.

If you configure the PEX link load sharing mode multiple times on a PEX port, the most recent configuration takes effect.

Examples

# Configure a PEX link load sharing mode for PEX port 1 to distribute traffic based on destination MAC addresses.

<Sysname> system-view

[Sysname] pex-port 1

[Sysname-pex-port1] pex-port load-sharing mode destination-mac

port group interface

Use port group interface to assign a physical interface to a PEX port on the parent fabric.

Use undo port group interface to remove a physical interface from a PEX port.

Syntax

port group interface interface-type interface-number

undo port group interface interface-name

Default

No physical interfaces are assigned to a PEX port.

Views

PEX port view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies a physical interface by its type and number. Available interfaces include SFP+ and QSFP+ ports.

interface-name: Specifies a physical interface in the interface-typeinterface-number format. No space is allowed between the interface-type and interface-number arguments.

Usage guidelines

You can assign a maximum of six physical interfaces to the PEX port for a PEX. The physical interfaces are aggregated automatically for backup and load balancing. The default configuration is automatically restored on the interfaces after the assignment.

You must connect a PEX port's all physical interfaces to the same PEX.

If a physical interface has been assigned to a PEX port, you cannot assign the interface to any other PEX port.

Make sure the PEX physical interfaces at the two ends of a PEX link are at the same rate.

A PEX port must have a minimum of one physical interface in Forwarding state for its PEX to communicate with the parent device correctly. If a PEX port has only one physical interface in Forwarding state, the PEX will reboot when any of the following events occur:

· The interface is removed from the PEX port.

· The interface goes down.

Examples

# Assign the physical interfaces Ten-GigabitEthernet 1/2/1 through Ten-GigabitEthernet 1/2/4 to PEX port 3.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 1/2/1 to ten-gigabitethernet 1/2/4

[Sysname-if-range] shutdown

[Sysname] pex-port 3

[Sysname-pex-port3] port group interface ten-gigabitethernet 1/2/1

[Sysname-pex-port3] port group interface ten-gigabitethernet 1/2/2

[Sysname-pex-port3] port group interface ten-gigabitethernet 1/2/3

[Sysname-pex-port3] port group interface ten-gigabitethernet 1/2/4

[Sysname-pex-port3] quit

[Sysname] interface range ten-gigabitethernet 1/2/1 to ten-gigabitethernet 1/2/4

[Sysname-if-range] undo shutdown

02-Virtual Technologies Command Reference

IRF commands

display irf-port load-sharing mode

display mad

irf auto-update enable

irf domain

irf member description

irf-port

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us