02-Virtual Technologies Command Reference

HomeSupportSwitchesH3C S7500E Switch SeriesReference GuidesCommand ReferencesH3C S7500E Command References-R752X-6W10002-Virtual Technologies Command Reference
01-IRF commands
Title Size Download
01-IRF commands 193.24 KB

IRF commands

All IRF commands are available only on the default MDC, except for the commands in Table 1.

Table 1 IRF commands available on both default and non-default MDCs

Command category

Commands

Display commands

display irf link

MAD commands

mad arp enable

mad enable

mad nd enable

mad exclude interface

 

For more information about MDCs, see Virtual Technologies Configuration Guide.

chassis convert mode irf

Use chassis convert mode irf to enable IRF mode.

Use undo chassis convert mode to restore the default.

Syntax

chassis convert mode irf

undo chassis convert mode

Default

The device operates in standalone mode.

Views

System view

Predefined user roles

network-admin

Usage guidelines

To set up an IRF fabric, place all member devices in IRF mode after you configure member IDs, priorities, and IRF port settings for the member devices. In standalone mode, a device cannot form an IRF fabric with other devices.

The device automatically reboots for the mode change to take effect. During the reboot, you may choose to have the system automatically convert the startup configuration file. Automatic configuration conversion prevents slot- or interface-related settings from becoming invalid. For example, the system adds member ID information to interface numbers and file paths in IRF mode.

IRF generates packets on a device in IRF mode even if the device does not form an IRF fabric with any other devices. To conserve system resources, set a device to standalone mode after removing it from an IRF fabric.

Examples

# Enable IRF mode.

<Sysname> system-view

[Sysname] chassis convert mode irf

The device will switch to IRF mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y

Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

Saving the converted configuration file to the main board succeeded.

Slot 1:

 Saving the converted configuration file succeeded.

 Now rebooting, please wait...

# Restore standalone mode.

<Sysname> system-view

[Sysname] undo chassis convert mode

The device will switch to stand-alone mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y

Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in stand-alone mode? [Y/N]:y

Now rebooting, please wait...

Saving the converted configuration file to the main board succeeded.

Chassis 2 Slot 1:

Saving the converted configuration file succeeded.

Now rebooting, please wait...

display irf

Use display irf to display IRF fabric information.

Syntax

display irf

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display IRF fabric information.

<Sysname> display irf

MemberID  Slot  Role   Priority  CPU-Mac         Description

 *+1      0     Master 1         0210-fc03-0007  -----

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

 

 * indicates the device is the master.

 + indicates the device through which the user logs in.

 

 The Bridge MAC of the IRF is: 3ce5-a6b8-3800

 Auto upgrade                : yes

 Mac persistent              : always

 Domain ID                   : 0

 Auto merge                  : no

 IRF mode                    : normal

Table 2 Command output

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.

Slot

MPU slot number.

Role

Role of the MPU in the IRF fabric:

·     Standby—Standby MPU for the global active MPU.

·     Master—Global active MPU.

·     Loading—Standby MPU for the global active MPU. The standby MPU is loading software images.

Priority

IRF member priority.

CPU-MAC

MAC address of the CPU on the MPU.

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.

Auto merge

State of the auto-merge feature:

·     yes—Enabled.

·     no—Disabled.

IRF mode

IRF mode:

·     enhanced.

·     light.

·     normal.

 

Related commands

display irf configuration

display irf topology

display irf configuration

Use display irf configuration to display basic IRF settings for each member device.

Syntax

display irf configuration

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# (In standalone mode.) Display the basic IRF settings of the device.

<Sysname> display irf configuration

 MemberID Priority IRF-Port1                   IRF-Port2

 1        1        disable                     disable

# (In IRF mode.) Display basic IRF settings for all members.

<Sysname> display irf configuration

 MemberID  NewID  IRF-Port1                     IRF-Port2

  1        1      Ten-GigabitEthernet1/1/0/1    disable

                  Ten-GigabitEthernet1/1/0/2

  2        2      disable                       Ten-GigabitEthernet2/1/0/1

                                                Ten-GigabitEthernet2/1/0/2

Table 3 Command output

Field

Description

MemberID

Current member ID of the device.

Priority

Member priority.

This field is available when the device is operating in standalone mode.

NewID

Member ID assigned to the device. This member ID takes effect at reboot.

This field is available when the device is operating in IRF mode.

IRF-Port1

Physical interfaces bound to IRF-port 1.

This field displays disable if no physical interfaces are bound to the IRF port.

IRF-Port2

Physical interfaces bound to IRF-port 2.

This field displays disable if no physical interfaces are bound to the IRF port.

 

Related commands

display irf

display irf topology

display irf link

Use display irf link to display IRF link information.

Syntax

display irf link

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display IRF link information.

<Sysname> display irf link

Member 1

 IRF Port    Interface                           Status

 1           disable                             --

 2           Ten-GigabitEthernet1/3/0/1(MDC1)    UP

             Ten-GigabitEthernet1/5/0/1(MDC2)    ADM

             Ten-GigabitEthernet1/6/0/1(MDC3)    DOWN

Member 2(IRF-Link-Down: MDC2, MDC3)

 IRF Port    Interface                           Status

 1           Ten-GigabitEthernet2/3/0/1(MDC1)    UP

             Ten-GigabitEthernet2/5/0/1(MDC2)    DOWN

             Ten-GigabitEthernet2/6/0/1(MDC3)    ADM

 2           disable                             --

# Display IRF link information.

<Sysname> display irf link

Member 1

 IRF Port    Interface                           Status

 1           disable                             --

 2           Ten-GigabitEthernet1/3/0/1(MDC1)    UP

             Ten-GigabitEthernet1/5/0/1(MDC2)    ADM

             Ten-GigabitEthernet1/6/0/1(MDC3)    DOWN

Member 2

 IRF Port    Interface                           Status

 1           Ten-GigabitEthernet2/3/0/1(MDC1)    UP

             Ten-GigabitEthernet2/5/0/1(MDC2)    DOWN

             Ten-GigabitEthernet2/6/0/1(MDC3)    ADM

 2           disable                             --

Table 4 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, and their respective MDCs. 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—Interface module that hosts the interface is not present.

 

display irf topology

Use display irf topology to display IRF fabric topology information.

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

 1          DOWN        ---           UP          2            000f-cbb8-1a82

 2          UP          1             DIS         ---          000f-cbb8-1a82

Table 5 Command output

Field

Description

IRF-Port1

Information about IRF-port 1, including its link state and neighbor.

IRF-Port2

Information about IRF-port 2, including its link state and neighbor.

MemberID

IRF member ID.

Link

Link state of the IRF port:

·     UP—The IRF link is up.

·     DOWN—The IRF link is down because the port has no physical link or has not been activated by the irf-port-configuration active command.

·     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.

This field displays three hyphens (---) if no device is connected to the port.

Belong To

IRF fabric that has the device, represented by the CPU MAC address of the master in the IRF fabric.

 

Related commands

display irf

display irf configuration

display irf-port load-sharing mode

Use display irf-port load-sharing mode to display IRF link load sharing mode.

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: packet type-based sharing

Layer 3 traffic: packet type-based sharing

Layer 4 traffic: packet type-based sharing

# Display the global load sharing mode for IRF links. In this example, because a global load sharing mode has been configured, the configured mode applies.

<Sysname> display irf-port load-sharing mode

irf-port Load-Sharing Mode:

destination-mac address  source-mac address

# 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: packet type-based sharing

Layer 3 traffic: packet type-based sharing

Layer 4 traffic: packet type-based sharing

# Display the load sharing mode of IRF-port 1/1 after a load sharing mode is configured on the port.

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

irf-port1/1 Load-Sharing Mode:

  destination-mac address  source-mac address

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

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

irf-port1/1 Load-Sharing Mode:

destination-ip address   source-ip address

 

irf-port1/2 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

Table 6 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: packet type-based sharing

Default load sharing mode for traffic that has no IP header. The default link load sharing mode differs by service modules. For information about the default link load sharing modes of different service modules, see device management in Fundamentals Configuration Guide.

Layer 3 traffic: packet type-based sharing

Default load sharing mode for non-TCP/-UDP IP packets. The default link load sharing mode differs by service modules. For information about the default link load sharing modes of different service modules, see device management in Fundamentals Configuration Guide.

Layer 4 traffic: packet type-based sharing

Default load sharing mode for TCP/UDP packets. The default link load sharing mode differs by service modules. For information about the default link load sharing modes of different service modules, see device management in Fundamentals Configuration Guide.

 

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 enabled.

MAD ND enabled.

MAD LACP disabled.

MAD BFD disabled.

# Display detailed MAD information.

<Sysname> display mad verbose

Multi-active recovery state: No

Excluded ports(user-configured):

  Vlan-interface999

Excluded ports(system-configured):

  Ten-GigabitEthernet1/3/0/25

  Ten-GigabitEthernet1/3/0/26

  Ten-GigabitEthernet2/3/0/27

  Ten-GigabitEthernet2/3/0/28

MAD ARP disabled.

MAD ND disabled.

MAD LACP enabled interface: Bridge-Aggregation 1

  MAD status                 : Normal

  Member ID       Port                             MAD status

  1               Ten-GigabitEthernet1/3/0/1       Normal

  2               Ten-GigabitEthernet2/3/0/1       Normal

MAD BFD enabled interface: VLAN-interface 3

  MAD status                 : Normal

  Member ID   MAD IP address       Neighbor    MAD status

  1           192.168.1.1/24       2           Normal

  2           192.168.1.2/24       1           Normal

Table 7 Command output

Field

Description

MAD ARP enabled.

Status of ARP MAD.

This field displays MAD ARP disabled if ARP MAD is disabled.

MAD ND enabled.

Status of ND MAD.

This field displays MAD ND disabled if ND MAD is disabled.

MAD LACP enabled.

Status of LACP MAD.

This field displays MAD LACP disabled if LACP MAD is disabled.

MAD BFD enabled.

Status of BFD MAD.

This field displays MAD BFD disabled if BFD MAD is disabled.

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 network ports and interfaces in the fabric except for the following ports and interfaces:

¡     IRF physical interfaces.

¡     Ports and interfaces configured to not shut down.

·     No—The IRF fabric is not in Recovery state. It is active and can forward traffic.

Excluded ports(user-configured)

Ports and interfaces manually configured to not shut down when the IRF fabric transits to the Recovery state.

Excluded ports(system-configured)

Ports and interfaces set to not shut down by default when the IRF fabric transits to the Recovery state. These ports and interfaces are not user configurable.

MAD status

MAD operating status:

·     Normal—The MAD mechanism is operating correctly.

·     Faulty—The MAD mechanism is not operating correctly. Check the interface or port for connectivity or configuration problems. For example, verify that all member devices have member ports used for LACP MAD.

·     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.

 

easy-irf

Use easy-irf to bulk-configure basic IRF settings for an IRF member device.

Syntax

easy-irf [ member member-id [ renumber new-member-id ] domain domain-id [ priority priority ] [ irf-port1 interface-list1 ] [ irf-port2 interface-list2 ] ]

Views

System view

Predefined user roles

network-admin

Parameters

member member-id: Specifies the member ID of a member device. The value range for the member ID is 1 to 4.

renumber new-member-id: Specifies a new member ID for the device. The value range for the member ID is 1 to 4. The member device automatically reboots for the new member ID to take effect. If you do not specify this option, the command does not change the member ID.

domain domain-id: Specifies an IRF domain ID in the range of 0 to 4294967295. Assign the same domain ID to all devices you are adding to the same IRF fabric.

priority priority: Specifies an IRF 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.

irf-port1 interface-list1: Specifies a space-separated list of up to 16 interface items. Each interface item specifies one interface in the interface-type interface-number form. The interfaces are bound to IRF-port 1.

irf-port2 interface-list2: Specifies a space-separated list of up to 16 interface items. Each interface item specifies one interface in the interface-type interface-number form. The interfaces are bound to IRF-port 2. A physical interface can be bound to only one IRF port.

Usage guidelines

This command is supported only in IRF mode.

This command bulk-configures basic IRF settings for a member device, including the member ID, domain ID, priority, and IRF port bindings.

The easy IRF feature provides the following configuration methods:

·     Interactive method—Enter the easy-irf command without parameters. The system will guide you to set the parameters step by step.

·     Non-interactive method—Enter the easy-irf command with parameters.

As a best practice, use the interactive method if you are new to IRF.

If you execute this command multiple times, the following settings take effect:

·     The most recent settings for the member ID, domain ID, and priority.

·     IRF port bindings added through executions of the command. You can bind a maximum of 16 physical interfaces to an IRF port.

When you specify physical interfaces for an IRF port, you must follow the IRF port binding requirements in Virtual Technologies Configuration Guide.

If you specify physical interfaces by using the interactive method, you must also follow these restrictions and guidelines:

·     Do not enter spaces between the interface type and interface number.

·     Use a comma (,) to separate two physical interfaces. No spaces are allowed between interfaces.

To remove an IRF physical interface from an IRF port, you must use the undo port group interface command in IRF port view.

Examples

# Bulk-configure basic IRF settings by using the non-interactive method. Change the member ID from 1 to 2, set the domain ID to 10, configure the member priority as 10, and bind Ten-GigabitEthernet 1/1/0/21 through Ten-GigabitEthernet 1/1/0/24 to IRF-port 1.

<Sysname> system-view

[Sysname] easy-irf member 1 renumber 2 domain 10 priority 10 irf-port1 ten-gigabitethernet 1/1/0/21 ten-gigabitethernet 1/1/0/22 ten-gigabitethernet 1/1/0/23 ten-gigabitethernet 1/1/0/24

*****************************************************************************

                  Configuration summary for member 1

IRF new member ID: 2

IRF domain ID    : 10

IRF priority     : 10

IRF-port 1       : Ten-GigabitEthernet1/1/0/21, Ten-GigabitEthernet1/1/0/22

                   Ten-GigabitEthernet1/1/0/23, Ten-GigabitEthernet1/1/0/24

IRF-port 2       : Disabled

*****************************************************************************

Are you sure to use these settings to set up IRF? [Y/N] y

Starting to configure IRF...

Configuration succeeded.

The device will reboot for the new member ID to take effect. Continue? [Y/N] y

# Bulk-configure basic IRF settings by using the interactive method. Change the member ID from 1 to 2, set the domain ID to 10, configure the member priority as 10, and bind Ten-GigabitEthernet 1/1/0/21 through Ten-GigabitEthernet 1/1/0/24 to IRF-port 1.

<Sysname> system-view

[Sysname] easy-irf

*****************************************************************************

Welcome to use easy IRF.

To skip the current step, enter a dot sign (.).

To return to the previous step, enter a minus sign (-).

To use the default value (enclosed in []) for each parameter, press Enter withou

t entering a value.

To quit the setup procedure, press CTRL+C.

*****************************************************************************

Select a member by its ID <1> [1]:1

Specify a new member ID <1~4> [1]: 2

Specify a domain ID <0~4294967295> [0]: 10

Specify a priority <1~32> [1]: 10

Specify IRF-port 1 bindings (a physical interface or a comma-separated physical

interface list)[Disabled]: ten-gigabitethernet1/1/0/21,ten-gigabitethernet1/1/0/22,ten-gigabitethernet1/1/0/23,ten-gigabitethernet1/1/0/24

Specify IRF-port 2 bindings (a physical interface or a comma-separated physical

interface list)[Disabled]:

*****************************************************************************

                  Configuration summary for member 1

IRF new member ID: 2

IRF domain ID    : 10

IRF priority     : 10

IRF-port 1       : Ten-GigabitEthernet1/1/0/21, Ten-GigabitEthernet1/1/0/22

                   Ten-GigabitEthernet1/1/0/23, Ten-GigabitEthernet1/1/0/24

IRF-port 2       : Disabled

*****************************************************************************

Are you sure to use these settings to set up IRF? [Y/N] y

Starting to configure IRF...

Configuration succeeded.

The device will reboot for the new member ID to take effect. Continue? [Y/N] y

irf auto-merge enable

Use irf auto-merge enable to enable IRF auto-merge.

Use undo irf auto-merge enable to disable IRF auto-merge.

Syntax

irf auto-merge enable

undo irf auto-merge enable

Default

IRF auto-merge is enabled. The IRF fabric that has failed in the master election reboots automatically to complete the IRF fabric merge.

Views

System view

Predefined user roles

network-admin

Usage guidelines

If the IRF auto-merge feature is disabled, you must follow the system instructions to manually reboot member devices in the IRF fabric that fails master election.

For a successful merge, make sure IRF auto-merge is enabled on the IRF fabrics that are merging.

This command is supported only in IRF mode. When you change the operating mode from IRF to standalone, the setting for this command is lost, regardless of whether you have saved the configuration. To disable IRF auto-merge after you change the operating mode from standalone to IRF, use the undo form of this command.

IRF auto-merge takes effect on merges caused by the following events:

·     The IRF link recovers from a link failure.

·     The IRF physical interfaces of the member devices are connected after the interfaces are bound to IRF ports.

The feature does not take effect on a merge that occurs in the following conditions:

·     You bind a physical interface to an IRF port.

·     The interface has been connected to the peer IRF physical interface before the binding operation.

Examples

# Enable IRF auto-merge.

<Sysname> system-view

[Sysname] irf auto-merge enable

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

Software auto-update is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is supported only in IRF mode. When you change the operating mode from IRF to standalone, the setting for this command is lost, regardless of whether you have saved the configuration. To disable software auto-update after you change the operating mode from standalone to IRF, use the undo form of this command.

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

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

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 the IRF fabric.

Use undo irf domain to restore the default.

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

This command is supported only in IRF mode. When you change the operating mode from IRF to standalone, the IRF domain setting is lost, regardless of whether you have saved the configuration.

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.

In an MDC environment, the irf domain command is available only on the default MDC. The mad enable, mad arp enable, and mad nd enable commands are available on all MDCs. If you change the IRF domain ID in one MDC, the IRF domain IDs in all other MDCs change automatically.

Examples

# Set the IRF domain ID to 10.

<Sysname> system-view

[Sysname] irf domain 10

irf isolate member

Use irf isolate member to isolate an unused IRF member ID.

Use undo irf isolate member to remove the isolation setting for an IRF member ID.

Syntax

irf isolate member member-id

undo irf isolate member member-id

Default

No IRF member IDs are isolated.

Views

System view

Predefined user roles

network-admin

Parameters

member-id: Specifies an IRF member ID. Available values are IDs that have not been assigned.

Usage guidelines

This command is supported only in IRF mode.

CRC errors or traffic storms occur if an IRF member device tags inter-chassis packets with a valid unused member ID. This issue is typically caused by poor-quality fiber modules, fibers, or cables on IRF links.

To avoid CRC errors or traffic storms, isolate the unused member IDs in the valid member ID range. When an unused member ID is isolated, the member devices will drop all packets that are tagged with the member ID.

Before you assign an isolated member ID to a new member device, you must remove the isolation setting for the member ID by using the undo irf isolate member command.

Examples

# Isolate IRF member ID 3.

<Sysname> system-view

[Sysname] irf isolate member 3

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 delay time 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.

Usage guidelines

This command is supported only in IRF mode. When you change the operating mode from IRF to standalone, the command configuration is lost, regardless of whether you have saved the configuration.

Make sure the IRF link down report delay 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 fast 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

Use irf mac-address to specify a MAC address as the IRF bridge MAC address.

Use undo irf mac-address to restore the default.

Syntax

irf mac-address mac-address

undo irf mac-address

Default

An IRF fabric uses the bridge MAC address of the master device as the IRF bridge MAC address.

Views

System view

Predefined user roles

network-admin

Parameters

mac-address: Specifies a MAC address in the format of H-H-H. The MAC address cannot be the all-zero or all-F MAC address, or a multicast MAC address. You can omit the consecutive zeros at the beginning of each segment. For example, you can enter f-e2-1 for 000f-00e2-0001.

Usage guidelines

CAUTION

CAUTION:

IRF bridge MAC address change causes transient traffic disruption.

 

You can specify the bridge MAC address of an existing IRF fabric for a new IRF fabric to replace the existing IRF fabric with transient packet loss.

This command is supported only in IRF mode.

When you change the operating mode from IRF to standalone, the IRF bridge MAC address configuration is lost, regardless of whether you have saved the configuration.

On a switched LAN, the IRF bridge MAC address must be unique.

After you specify an IRF bridge MAC address, the IRF fabric always uses the specified address as the IRF bridge MAC address.

When IRF fabrics merge, IRF ignores the IRF bridge MAC address and only checks the bridge MAC address of each member device in the IRF fabrics. IRF merge fails if any two member devices have the same bridge MAC address.

After IRF fabrics merge, the merged IRF fabric uses the bridge MAC address of the merging IRF fabric that won the master election as the IRF bridge MAC address.

If an IRF fabric splits after you configure the IRF bridge MAC address, both the split IRF fabrics use the configured bridge MAC address as the IRF bridge MAC address.

Examples

# Configure the IRF fabric to use c4ca-d9e0-8c3c as the IRF bridge MAC address.

<Sysname> system-view

[Sysname] irf mac-address c4ca-d9e0-8c3c

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

The IRF bridge MAC address 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 the fabric.

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

Usage guidelines

This command is supported only in IRF mode. When you change the operating mode from IRF to standalone, the bridge MAC persistence setting is lost, regardless of whether you have saved the configuration.

If the undo form of this command is configured, bridge MAC address of the current master replaces the original IRF bridge MAC as soon as the original address owner leaves.

This command does not take effect if the IRF bridge MAC address is configured by using the irf mac-address mac-address command.

If ARP MAD or ND MAD is used with the spanning tree feature, you must configure IRF bridge MAC persistence by using the undo irf mac-address persistent command. Do not specify a MAC address as the IRF bridge MAC address.

If the IRF fabric has cross-member aggregate links, do not use the undo irf mac-address persistent command to avoid unnecessary traffic disruption.

By default, an IRF fabric uses the bridge MAC address of the master device as its bridge MAC address.

On a switched LAN, the IRF bridge MAC address must be unique for correct traffic transmission.

When IRF fabrics merge, IRF ignores the IRF bridge MAC address and only checks the bridge MAC address of each member device in the IRF fabrics. IRF merge fails if any two member devices have the same bridge MAC address.

Examples

# Enable the IRF bridge MAC address to persist forever.

<Sysname> system-view

[Sysname] irf mac-address persistent always

irf member

Use irf member to assign a member ID to the device in standalone mode.

Use undo irf member to restore the default.

Syntax

irf member member-id

undo irf member

Default

The member ID is 1.

Views

System view

Predefined user roles

network-admin

Parameters

member-id: Assigns an IRF member ID to the device. The value range for this argument is 1 to 4.

Usage guidelines

Assign an IRF member ID to a device before enabling IRF mode. The member ID takes effect after IRF mode is enabled. This member ID must be unique among all IRF member devices.

To change the member ID of a device in IRF mode, use the irf member renumber command.

Examples

# (In standalone mode.) Assign member ID 2 to the device.

<Sysname> system-view

[Sysname] irf member 2

Related commands

irf member renumber

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.

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

Usage guidelines

This command is supported only in IRF mode. When you change the operating mode from IRF to standalone, the IRF member description is lost, regardless of whether you have saved the configuration.

Examples

# Configure the description as F1Num001 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. The value range for IRF member IDs is 1 to 4.

priority: Sets 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

This command is supported only in IRF mode. To assign an IRF priority to a device in standalone mode, use the irf priority command.

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

Related commands

irf priority

irf member renumber

Use irf member renumber to change the member ID of an IRF member 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 device uses the member ID that is set in standalone mode.

Views

System view

Predefined user roles

network-admin

Parameters

member-id: Specifies the ID of an IRF member. The value range for IRF member IDs is 1 to 4.

new-member-id: Assigns a new ID to the IRF member. The value range for IRF member IDs is 1 to 4.

Usage guidelines

CAUTION

CAUTION:

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.

 

To have the new ID take effect, you must reboot the IRF member. To cancel the member ID change before you reboot the member device, use the undo irf member renumber command. In the command, set the new member ID to be the same as the old member ID.

When adding a device into an IRF fabric, you must assign a unique IRF member ID to the device. If its IRF member ID has been used in the IRF fabric, the device cannot join the IRF fabric.

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.

To set the member ID of a device in standalone mode, use the irf member command.

Examples

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

<Sysname> display irf

[Sysname] irf member 1 renumber 2

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 1 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 1 renumber 2 command, the device member ID changes to 2 at system reboot. Using undo irf member 1 renumber cannot restore the member ID to 1. You must use the irf member 2 renumber 1 command to reconfigure the member ID.

Related commands

irf member

irf priority

Use irf priority to assign an IRF member priority to a device in standalone mode.

Use undo irf priority to restore the default.

Syntax

irf priority priority

undo irf priority

Default

The IRF member priority is 1.

Views

System view

Predefined user roles

network-admin

Parameters

priority: Specifies an IRF member priority value 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 member priority configured in standalone mode takes effect after you enable IRF mode.

To change the member priority of a device in IRF mode, use the irf member priority command. The new priority setting takes effect at the next master election, but it does not trigger a master election.

Examples

# (In standalone mode.) Assign IRF member priority 32 to the device.

[Sysname] system-view

[Sysname] irf priority 32

Related commands

irf member priority

irf-port

Use irf-port to enter IRF port view.

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

Syntax

In standalone mode:

irf-port irf-port-number

undo irf-port irf-port-number

In IRF mode:

irf-port member-id/irf-port-number

undo irf-port member-id/irf-port-number

Views

System view

Predefined user roles

network-admin

Parameters

member-id: Specifies an IRF member device by its member ID.

irf-port-number: Specifies an IRF port on the member device. The irf-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.

Examples

# (In standalone mode.) Enter IRF-port 1 view.

<Sysname> system-view

[Sysname] irf-port 1

[Sysname-irf-port1]

# (In IRF mode.) Enter IRF-port 2/1 view.

<Sysname> system-view

[Sysname] irf-port 2/1

[Sysname-irf-port2/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 default IRF link load sharing mode differs by service modules. For information about the default link load sharing modes of different service modules, see device management in Fundamentals Configuration Guide.

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.

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

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 default IRF link load sharing mode differs by service modules. For information about the default link load sharing modes of different service modules, see device management in Fundamentals Configuration Guide.

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.

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 ports.

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 when the port is in DIS state:

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

<Sysname> system-view

[Sysname] interface ten-gigabitEthernet 1/1/0/27

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

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

[Sysname] irf-port 1/2

[Sysname-irf-port1/2] port group interface Ten-GigabitEthernet 1/1/0/27

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/0/27

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

[Sysname-Ten-GigabitEthernet1/1/0/27] 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.

Chassis 1 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

mdc-admin

Usage guidelines

Do not configure ARP MAD together with LACP MAD, because they handle collisions differently.

Do not configure ARP MAD together with BFD MAD. ARP MAD requires the spanning tree feature, but BFD MAD is mutually exclusive with the spanning tree feature. At the same time, ARP MAD handles collisions differently than BFD MAD.

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.

 

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

 

Category

Restrictions and guidelines

Management Ethernet ports for ARP MAD

Connect the management Ethernet ports on each member device to the common Ethernet ports on the intermediate device.

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.

 

When you use the mad arp 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.

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.

You can execute the mad arp enable command on any MDCs. If you change the IRF domain ID in one MDC, the new IRF domain ID takes effect immediately on all MDCs.

Examples

# Enable ARP MAD on VLAN-interface 3.

<Sysname> system-view

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] mad arp 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 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

VLAN interface view

Management Ethernet interface view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Do not configure BFD MAD together with ARP MAD or ND MAD. BFD MAD is mutually exclusive with the spanning tree feature, but ARP MAD and ND MAD require the spanning tree feature. At the same time, BFD MAD handles collisions differently than ARP MAD and ND MAD.

When you configure BFD MAD that uses common Ethernet ports, 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, perform the following tasks on both the IRF fabric and the intermediate device:

¡     Create a VLAN and VLAN interface for BFD MAD.

¡     Assign the ports of BFD MAD links to the BFD MAD VLAN.

·     Make sure the IRF fabrics on the network use different BFD MAD VLANs.

·     Make sure the BFD MAD VLAN contains only ports on the BFD MAD links. Exclude a port from the BFD MAD VLAN if the port is not on the BFD MAD link. For example, if you have assigned the port to all VLANs by using the port trunk permit vlan all command, use the undo port trunk permit command to exclude the port from the BFD MAD VLAN.

BFD MAD VLAN and feature compatibility

Do not use the BFD MAD VLAN for any purposes 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.

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.

 

When you configure BFD MAD that uses management Ethernet ports, follow these restrictions and guidelines:

 

Category

Restrictions and guidelines

Management Ethernet ports for BFD MAD

Connect the management Ethernet ports on each member device to the common Ethernet ports on the intermediate device. To avoid BFD MAD failure caused by an active/standby MPU switchover, connect the management Ethernet port on each MPU to the intermediate device.

BFD MAD VLAN

·     On the intermediate device, 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 management Ethernet ports to the VLAN.

·     Make sure the IRF fabrics on the network use different BFD MAD VLANs.

·     Make sure the BFD MAD VLAN on the intermediate device contains only ports on the BFD MAD links.

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.

 

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

mdc-admin

Usage guidelines

LACP MAD handles collisions differently than ARP MAD and ND MAD. To avoid conflicts, do not enable LACP MAD together with ARP MAD and ND MAD on an IRF fabric.

LACP MAD requires an H3C device that supports extended LACPDUs to act as the intermediate device. 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.

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.

You can execute the mad enable command on any MDCs. If you change the IRF domain ID in one MDC, the new IRF domain ID takes effect immediately on all MDCs.

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.

Related commands

irf domain

mad exclude interface

Use mad exclude interface to exclude a network port or interface 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 configure the IRF fabric to shut down a network port or interface when it transits to the Recovery state upon detection of a multi-active collision.

Syntax

mad exclude interface interface-type interface-number

undo mad exclude interface interface-type interface-number

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

If a port or interface must be kept in up state for special purposes such as Telnet connection, exclude the port or interface from the shutdown action. As a best practice to avoid incorrect traffic forwarding, do not exclude any ports or interfaces except for the ports used for Telnet.

Do not exclude the following ports and interfaces from the shutdown action:

·     Aggregate interfaces used for MAD and their member ports.

·     VLAN interfaces used for MAD and the Ethernet ports in the VLANs.

·     Management Ethernet ports used for MAD.

The ports and interfaces that have been 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 and interfaces.

Examples

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

<Sysname> system-view

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

Related commands

mad restore

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

VLAN interface view

Management Ethernet interface view

Predefined user roles

network-admin

mdc-admin

Parameters

ip-address: Specifies an IP address in dotted decimal notation.

mask: Specifies a subnet mask in decimal dotted notation.

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

member member-id: Specifies the ID of an IRF member.

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.

Do not configure a MAD IP address by using the ip address command or configure a VRRP virtual address on the BFD MAD-enabled port or interface.

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

·     If 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

mdc-admin

Usage guidelines

Do not configure ND MAD together with LACP MAD, because they handle collisions differently.

Do not configure ND MAD together with BFD MAD. ND MAD requires the spanning tree feature, but BFD MAD is mutually exclusive with the spanning tree feature. At the same time, ND MAD handles collisions differently than BFD MAD.

Do not configure ND MAD on VLAN-interface 1.

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.

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.

You can execute the mad nd enable command on any MDCs. If you change the IRF domain ID in one MDC, the new IRF domain ID takes effect immediately on all MDCs.

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 to 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. If you specify an MDC, this command binds physical interfaces on the MDC to an IRF port. If you do not specify an MDC, this command binds physical interfaces on the default MDC to an IRF port.

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.

enhanced: Sets the binding mode to enhanced.

extended: Sets the binding mode to extended. This mode is not supported by the IRF physical interfaces on MPUs and SA interface modules. If the extended mode is used, an IRF fabric can contain a maximum of two chassis.

Usage guidelines

Execute this command multiple times to bind multiple physical interfaces to an IRF port. You can bind a maximum of 16 physical interfaces to an IRF port.

The MDC settings might lose effect after the device reboots to join an IRF fabric. As a best practice, create MDCs and bind the physical interfaces on non-default MDCs to an IRF port only after the IRF fabric is formed. For more information about MDCs, see Virtual Technologies Configuration Guide.

In IRF mode, 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. In standalone mode, the shutdown and undo shutdown operations are not required.

Make sure the IRF physical interfaces of an IRF port use the same binding mode. In IRF mode, IRF physical interfaces of an IRF port cannot be configured to use different binding modes. In standalone mode, you can configure the IRF physical interfaces of an IRF port to use different binding modes. However, only one binding mode takes effect after the operating mode changes from standalone to IRF. The binding mode of the first IRF physical interface in the configuration file has the highest priority.

The system does not dynamically remove IRF port bindings when IRF links are lost, for example, because an interface module 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

# (In standalone mode.) Bind Ten-GigabitEthernet 1/0/1 to IRF-port 1.

<Sysname> system-view

[Sysname] irf-port 1

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

# (In IRF mode.) Bind Ten-GigabitEthernet 1/1/0/1 to IRF-port 1/1 on IRF member 1.

<Sysname> system-view

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

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

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

[Sysname] irf-port 1/1

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

[Sysname-irf-port1/1] quit

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

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

Related commands

irf-port


IRF 3 commands

associate

Use associate to assign a virtual chassis number to a tier-1 PEX.

Use undo associate to remove the virtual chassis number of a tier-1 PEX.

Syntax

associate associated-id

undo associate

Default

A tier-1 PEX is not assigned a virtual chassis number.

Views

PEX port view

Predefined user roles

network-admin

mdc-admin

Parameters

associated-id: Specifies a virtual chassis number. The value range for this argument is 100 to 159. If S5130-EI PEXs exist, the value range changes to 100 to 129.

Usage guidelines

A tier-1 PEX is directly connected to the parent fabric. You must assign a unique virtual chassis number to each tier-1 PEX.

You cannot change the chassis number of a tier-1 PEX while it is starting up.

An operating tier-1 PEX will reboot if you change or remove its chassis number.

If you execute this command multiple times on a PEX port, the most recent configuration takes effect.

Examples

# Assign virtual chassis 100 to the tier-1 PEX attached to PEX port 2.

<Sysname> system-view

[Sysname] pex-port 2

[Sysname-pex-port2] associate 100

Related commands

display pex-port

associate order

Use associate order to assign a virtual chassis number to a tier-2 PEX.

Use undo associate order to remove the virtual chassis number of a tier-2 PEX.

Syntax

associate order associate-id

undo associate order associate-id

Default

A tier-2 PEX is not assigned a virtual chassis number.

Views

PEX port view

Predefined user roles

network-admin

mdc-admin

Parameters

associated-id: Specifies a virtual chassis number for the tier-2 PEX. The value range for this argument is 1 to 159. If S5130-EI PEXs exist, the value range changes to 1 to 129.

Usage guidelines

Use this command in conjunction with the associate command to set up a two-tier PEX stack.

A tier-2 PEX is directly connected to a tier-1 PEX. On the PEX port for a tier-1 PEX, you can assign a virtual chassis number only to its directly connected tier-2 PEX.

For example, the physical topology of a PEX stack is PEX port 1---PEX 100---PEX 101---PEX 102---PEX 103---(PEX port 2). To configure this PEX stack, you must perform the following tasks:

·     On PEX port 1, execute the associate 100 command and the associate order 101 command.

·     On PEX port 2, execute the associate 103 command and the associate order 102 command.

If a tier-2 PEX is directly connected to two tier-1 PEXs as in a three-member PEX stack, you can make the assignment for the tier-2 PEX on either of their PEX ports.

You must make sure the virtual chassis number assigned to a tier-2 PEX is unique.

To change the assigned number, you must first remove the old number.

You cannot change the virtual chassis number of a tier-2 PEX while it is starting up.

An operating tier-2 PEX will reboot if you change or remove its virtual chassis number.

Examples

# Assign virtual chassis number 101 to the tier-2 PEX attached to PEX port 1.

<Sysname> system-view

[Sysname] pex-port 1

[Sysname-pex-port1] associate order 101

Related commands

associate

pex-port

pex-port-group

description

Use description to configure the description of a PEX port or PEX port group.

Use undo description to restore the default.

Syntax

description text

undo description

Default

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

The description of a PEX port group uses the pex-port-group group-id format (for example, pex-port-group 0002).

Views

PEX port view

PEX port group view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Examples

# Configure the description as connettodep2 for PEX port 2.

<Sysname> system-view

[Sysname] pex-port 2

[Sysname-pex-port2] description connecttodep2

# Configure the description as PEXStackA for PEX port group 2.

<Sysname> system-view

[Sysname] pex-port-group 1

[Sysname-pex-port-group-1] description PEXStackA

Related commands

display pex-port

display pex working-mode

Use display pex working-mode to display the operating mode settings for PEXs.

Syntax

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

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

all: Specifies all PEXs.

chassis chassis-number slot slot-number1 [ to slot-number2 ]: Specifies a PEX or a range of PEXs.

·     chassis chassis-number: Specifies a virtual chassis number.

·     slot slot-number1: Specifies a PEX in the virtual chassis.

·     to slot-number2: Specifies a range of PEXs in the virtual chassis. 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.

Usage guidelines

This command is supported only in IRF mode.

Examples

# Display the operating mode settings for all PEXs.

<Sysname> display pex working-mode all

PEX device mode Configuration:

  Switch mode at startup:

    None

  PEX mode at startup:

    Chassis 101 slots 0

Table 8 Command output

Field

Description

PEX device mode Configuration

Displays the operating mode settings for PEXs.

Switch mode at startup

Displays PEXs that will operate in switch mode after a reboot.

PEX mode at startup

Displays PEXs that will operate in PEX mode after a reboot.

 

display pex-port

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

pex-port-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 2:

  Description: pex-port 0002

  Group: 2

  Associated chassis numbers: 1

    Chassis            PEX status

    *100               Online

     101               Online

 

PEX port 3:

  Description: pex-port 0003

  Group: 2

  Associated chassis numbers: 1

    Chassis            PEX status

    *103               Online

     102               Online

# Display detailed information about all PEX ports.

<Sysname> display pex-port verbose

PEX port 2:

  Description: pex-port 0002

  Group: 2

  Associated chassis numbers: 1

    Chassis            PEX status

    *100               Online

     101               Online

  Member interfaces: 3

    Member interface    Status          Peer interface

    XGE1/1/0/2          Forwarding      PEX100/0/0/51

    XGE1/1/0/3          Forwarding      PEX100/0/0/52

    XGE1/1/0/4          Blocked         --

Table 9 Command output

Field

Description

Description

PEX port description.

Group

PEX port group to which the PEX port is assigned.

This field is displayed if the PEX port is connected to a PEX stack.

Associated chassis numbers

Number of virtual chassis assigned to PEXs on the PEX port.

Chassis

Virtual chassis number of a PEX attached to the PEX port. The virtual chassis number of the tier-1 PEX is prefixed with an asterisk (*).

This field displays No associated ID if no virtual chassis numbers have been assigned on the PEX port.

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 that are assigned to the PEX port.

Member interface

Physical interface 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 interfaces.

No physical interfaces have been assigned to the PEX port.

 

display pex-port topology

Use display pex-port topology to display PEX topology information.

Syntax

display pex-port [ pex-port-id ] topology

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

pex-port-id: Specifies a PEX port by its ID. The value range is the PEX port IDs used on the device. If you do not specify a PEX port ID, this command displays PEX topology information for all existing PEX ports.

Examples

# Display PEX topology information for PEX port 1.

<Sysname> display pex-port 1 topology

PEX port 1:

PEX            Neighbors       Local interfaces     Peer interfaces

Chassis 100    PEX port 1      PEX100/0/0/26        XGE1/0/0/5

               Chassis 101     PEX100/0/0/27        PEX101/0/0/27

Chassis 101    Chassis 100     PEX101/0/0/27        PEX100/0/0/27

               Chassis 102     PEX101/0/0/28        PEX102/0/0/28

Chassis 102    Chassis 101     PEX102/0/0/28        PEX101/0/0/28

               PEX port 2      PEX102/0/0/27        XGE1/0/0/6

Table 10 Command output

Field

Description

PEX

Virtual chassis number of a PEX.

Neighbors

Virtual chassis number of each neighbor device. This field displays the PEX port ID if the neighbor device is a parent device.

Local interfaces

Local interface that connects to a neighbor device.

Peer interfaces

Interface that connects the neighbor device to the local interface.

 

irf mode

Use irf mode to configure the IRF mode.

Use undo irf mode to remove the IRF mode configuration.

Syntax

irf mode { enhanced | light | normal }

undo irf mode { enhanced | light }

Default

The IRF mode is normal.

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. This mode supports a maximum of 60 PEXs. If S5130-EI PEXs exist, this mode supports a maximum of 30 PEXs.

light: Specifies light IRF mode. In this mode, the device can operate as a parent device in an IRF 3 system. This mode supports a maximum of 30 PEXs. You must set the IRF operating mode to light when using PEX stack access.

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

This command is supported only in IRF mode. The command setting takes effect on all IRF member devices in an IRF fabric.

For a success IRF merge, make sure all IRF member devices operate in the same IRF mode.

Make sure no non-default MDCs are created when you set the IRF mode to enhanced or light. The irf mode { enhanced | light } command and the mdc command are mutually exclusive.

For the mode change to take effect, save the configuration and reboot the device.

Examples

# Set the IRF mode to enhanced.

<Sysname> system-view

[Sysname] irf mode enhanced

member pex-port

Use member pex-port to assign a PEX port to a PEX port group.

Use undo member pex-port to remove a PEX port from a PEX port group.

Syntax

member pex-port pex-port-id

undo member pex-port pex-port-id

Default

A PEX port group does not contain PEX ports.

Views

PEX port group view

Predefined user roles

network-admin

mdc-admin

Parameters

pex-port-id: Specifies a PEX port by its ID. The value range for the port number is 1 to 120.

Usage guidelines

To set up a PEX stack, you must assign all its PEX ports to the same PEX port group. For example, the physical topology of a PEX stack is (PEX port 1)—PEX 100—PEX 101—PEX 102—PEX 103—(PEX port 2). To set up the PEX stack, you must assign PEX port 1 and PEX port 2 to the same PEX port group.

Examples

# Assign PEX port 1 and PEX port 2 to PEX port group 1.

<Sysname> system-view

[Sysname] pex-port group 1

[Sysname-pex-port-group-1] member pex-port 1

[Sysname-pex-port-group-1] member pex-port 2

Related commands

associate order

pex-port

pex-port-group

pex working-mode

Use pex working-mode to change the operating mode of PEXs to switch mode.

Use undo pex working-mode to restore the default.

Syntax

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

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

Default

PEXs in the IRF 3 system operate in PEX mode.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

switch: Specifies the switch mode.

all: Specifies all PEXs.

chassis chassis-number slot slot-number1 [ to slot-number2 ]: Specifies a PEX or a range of PEXs.

·     chassis chassis-number: Specifies a virtual chassis number.

·     slot slot-number1: Specifies a PEX in the virtual chassis.

·     to slot-number2: Specifies a range of PEXs in the virtual chassis. 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.

Usage guidelines

This command is supported only in IRF mode.

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 switch mode setting, you must execute the undo form of the command. The undo configuration takes effect after the PEXs reboot.

If a specified PEX is not in the IRF 3 system when you change its mode, the mode change does not take effect. To change the operating mode of the PEX after it joins the IRF 3 system, you must execute this command again.

Examples

# Change the PEX in virtual chassis 100 to switch mode.

<Sysname> system-view

[Sysname] pex working-mode switch chassis 100 slot 0

Are you sure you want to force a change to switch mode? In forced switch mode, the device can't change to PEX mode automatically. [Y/N]: y

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

Related commands

display pex working-mode

pex-port

Use pex-port to create a PEX port and enter its view, or enter the view of an existing PEX port.

Use undo pex-port to delete a PEX port.

Syntax

pex-port pex-port-id

undo pex-port pex-port-id

Default

No PEX ports exist.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

pex-port-id: Specifies a PEX port number. The value range for the port number is 1 to 120.

Usage guidelines

PEX ports are logical ports for managing PEXs.

Each PEX must be assigned to a PEX port. 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 PEXs to reboot.

Examples

# Create PEX port 2.

<Sysname> system-view

[Sysname] pex-port 2

[Sysname-pex-port2]

Related commands

display pex-port

pex-port global load-sharing mode

Use pex-port global load-sharing mode to set the global load sharing mode for PEX links.

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

Syntax

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

undo pex-port global load-sharing mode

Default

The default PEX link load sharing mode differs by service modules. For information about the default link load sharing mode, see device management in Fundamentals Configuration Guide.

Views

System view

Predefined user roles

network-admin

mdc-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.

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

The global PEX link load sharing mode applies to all PEX ports on the parent 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 a PEX port in PEX port view by using the pex-port load-sharing mode command.

A PEX 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 PEX link load sharing mode to distribute traffic based on destination MAC address.

<Sysname> system-view

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

Related commands

pex-port load-sharing mode

pex-port load-sharing mode

Use pex-port load-sharing mode to configure a port-specific 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 default PEX link load sharing mode differs by service modules. For information about the default link load sharing modes of different service modules, see device management in Fundamentals Configuration Guide.

Views

PEX port view

Predefined user roles

network-admin

mdc-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.

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 a port-specific 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 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 a PEX port, the most recent configuration takes effect.

A PEX 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 PEX port 1 to distribute traffic based on destination MAC address.

<Sysname> system-view

[Sysname] pex-port 1

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

Related commands

pex-port global load-sharing mode

pex-port-group

Use pex-port-group to create a PEX port group and enter its view, or enter the view of an existing PEX port group.

Use undo pex-port-group to delete a PEX port group.

Syntax

pex-port-group group-id

undo pex-port-group group-id

Default

No PEX port groups exist.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

group-id: Specifies a PEX port group ID. The value range for the port group number is 1 to 60.

Examples

# Create PEX port group 1, and assign PEX port 1 and PEX port 2 to the PEX port group.

<Sysname> system-view

[Sysname] pex-port-group 1

[Sysname-pex-port-group-1] member pex-port 1

[Sysname-pex-port-group-1] member pex-port 2

Related commands

member pex-port

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

mdc-admin

Parameters

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.

Usage guidelines

Execute this command multiple times to bind multiple physical interfaces to a PEX port. You can bind a maximum of six physical interfaces to a PEX port. 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.

The SFP+ ports on the LSQM1TGS12EC0 module are grouped by port number in order, starting from 1. Each group contains four ports.

The SFP+ ports on the LSQM2TGS16SF0 module are divided into the following groups:

·     Ports 1, 2, 15, and 16.

·     Ports 3 through 5.

·     Ports 6 through 8.

·     Ports 9 through 11.

·     Ports 12 through 14.

When you use the SFP+ ports in a group for PEX links, follow these restrictions and guidelines:

·     You must use all or none of the SFP+ ports for PEX links. The SFP+ ports can be assigned to different PEX ports.

·     You must shut down all the SFP+ ports in a group before you can assign or remove any of the ports to or from a PEX port. To bring up the SFP+ ports after the assignment or removal is complete, execute the undo shutdown command.

·     To shut down or bring up any SFP+ ports in a group, you must make sure all the SFP+ ports in the group have been assigned to or removed from PEX ports.

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

·     The interface is removed from the PEX port.

·     The interface goes down.

For more information about IRF physical interface requirements, see Virtual Technologies Configuration Guide.

Examples

# Assign physical interface Ten-GigabitEthernet 1/0/1 to PEX port 3.

<Sysname> system-view

[Sysname] pex-port 3

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

# Assign physical interface Ten-GigabitEthernet 1/0/6 to PEX port 4. In this example, Ten-GigabitEthernet 1/0/5 to Ten-GigabitEthernet1/0/8 are in the same port group.

<Sysname> system-view

[Sysname] interface range name pex interface ten-gigabitethernet 1/0/5 to ten-gigabitethernet 1/0/8

[Sysname-if-range-pex] shutdown

[Sysname-if-range-pex] quit

[Sysname] pex-port 4

[Sysname-pex-port4] port group interface ten-gigabitethernet 1/0/6

[Sysname-pex-port4] quit

[Sysname] interface range name pex

[Sysname-if-range-pex] undo shutdown

[Sysname-if-range-pex] quit

Related commands

display pex-port

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网