- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
02-Ethernet link aggregation commands | 144.04 KB |
Ethernet link aggregation commands
display link-aggregation load-sharing mode
display link-aggregation member-port
display link-aggregation summary
display link-aggregation verbose
link-aggregation global load-sharing mode
link-aggregation lacp traffic-redirect-notification enable
link-aggregation load-sharing mode
link-aggregation load-sharing mode local-first
link-aggregation load-sharing mpls enhanced
link-aggregation port-priority
link-aggregation selected-port maximum
link-aggregation selected-port minimum
Ethernet link aggregation commands
bandwidth
Use bandwidth to set the expected bandwidth for an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth (in kbps) is the interface baud rate divided by 1000.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Layer 3 aggregate subinterface view
Predefined user roles
network-admin
mdc-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth is an informational parameter used only by higher-layer protocols for calculation. You cannot adjust the actual bandwidth of an interface by using this command.
Examples
# Set the expected bandwidth to 10000 kbps for Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] bandwidth 10000
default
Use default to restore the default settings for an aggregate interface.
Syntax
default
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Layer 3 aggregate subinterface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
|
CAUTION: The default command might interrupt ongoing network services. Make sure you are fully aware of the impacts of this command when you execute it on a live network. |
This command might fail to restore the default settings for some commands for reasons such as command dependencies and system restrictions. Use the display this command in interface view to identify these commands, and then use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to resolve the problem.
Examples
# Restore the default settings for Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] default
description
Use description to set a description for an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of an interface is interface-name Interface. For example, the default description of Route-Aggregation 1 is Route-Aggregation1 Interface.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Layer 3 aggregate subinterface view
Predefined user roles
network-admin
mdc-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 255 characters.
Examples
# Set the description to connect to the lab for Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] description connect to the lab
display interface
Use display interface to display aggregate interface information.
Syntax
display interface [ { bridge-aggregation | route-aggregation } [ interface-number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
bridge-aggregation: Specifies Layer 2 aggregate interfaces.
route-aggregation: Specifies Layer 3 aggregate interfaces.
interface-number: Specifies an existing aggregate interface number.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of each interface description.
down: Displays information about interfaces in down state and the causes for the down state. If you do not specify this keyword, the command displays information about interfaces in all states.
Usage guidelines
If you do not specify the bridge-aggregation and route-aggregation keywords, the command displays information about all interfaces.
If you specify one of the following keywords but do not specify an interface number, the command displays information about all aggregate interfaces of the specified type.
· bridge-aggregation
· route-aggregation
If you specify one of the following options, the command displays information about the specified aggregate interface.
· bridge-aggregation interface-number
· route-aggregation interface-number
Examples
# Display detailed information about Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> display interface route-aggregation 1
Route-Aggregation1
Current state: UP
Line protocol state: UP
Description: Route-Aggregation1 Interface
Bandwidth: 1000kbps
Maximum transmission unit: 1500
Internet protocol processing: disabled
IP packet frame type: PKTFMT_ETHNT_2, hardware address: 0000-0000-0000
IPv6 packet frame type: PKTFMT_ETHNT_2, hardware address: 0000-0000-0000
Port priority: 0
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Unknown-speed mode, unknown-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 drops
Output: 0 packets, 0 bytes, 0 drops
# Display brief information about Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> display interface route-aggregation 1 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
RAGG1 UP UP --
Table 1 Command output
Field |
Description |
Bridge-Aggregation1 |
Layer 2 aggregate interface name. |
Route-Aggregation1 |
Layer 3 aggregate interface name. |
Current state |
Layer 3 aggregate interface status: · DOWN (Administratively down)—The interface is administratively shut down with the shutdown command. · DOWN—The interface is administratively up but physically down (possibly because no physical link exists or the link has failed). · UP—The Ethernet interface is both administratively and physically up. |
IP packet frame type |
IPv4 packet frame format. The value PKTFMT_ETHNT_2 indicates that packets are encapsulated in Ethernet II format. |
Description |
Partial or complete interface description set by using the description command. · If you do not specify the description keyword in the display interface brief command, this field displays the first 27 characters of the description. · If you specify the description keyword in the display interface brief command, this field displays the complete description. |
Bandwidth |
Expected bandwidth of the interface. This field is not displayed when the bandwidth is 0 kbps. |
Output queue - Urgent queuing: Size/Length/Discards |
Information about the urgent output queue: · Size—Number of packets in the queue. · Length—Maximum number of packets that the queue can contain. · Discards—Number of dropped packets. |
Output queue - Protocol queuing: Size/Length/Discards |
Information about the protocol output queue: · Size—Number of packets in the queue. · Length—Maximum number of packets that the queue can contain. · Discards—Number of dropped packets. |
Output queue - FIFO queuing: Size/Length/Discards |
Information about the FIFO output queue: · Size—Number of packets in the queue. · Length—Maximum number of packets that the queue can contain. · Discards—Number of dropped packets. |
Unknown-speed mode, unknown-duplex mode |
The interface speed and duplex mode are unknown. |
Port link-type |
Port link type: · Access. · Trunk. · Hybrid. |
Tagged VLANs |
VLAN whose packets are sent out of this interface with a tag. |
Untagged VLANs |
VLAN whose packets are sent out of this interface without a tag. |
Last clearing of counters |
Time when the reset counters interface command was last used to clear the interface statistics. This field displays Never if the reset counters interface command has never been used on the interface since device startup. |
Last 300 seconds input/output rate |
Average input or output rate over the last 300 seconds. |
Input/Output (total) |
Statistics of all packets received or sent on the interface. |
Input/Output (normal) |
Statistics of all normal packets received or sent on the interface. |
Line protocol state |
Data link layer protocol state of the interface: · UP. · DOWN. |
Internet protocol processing |
IP packet processing. Disabled indicates that IP packets cannot be processed. For an interface configured with an IP address, this field changes to Internet Address is. |
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
Brief information on interfaces in bridge mode |
Brief information about Layer 2 interfaces. |
Link: ADM - administratively down; Stby - standby |
Link status: · ADM—The interface has been administratively shut down. To recover its physical layer state, use the undo shutdown command. · Stby—The interface is operating as a backup interface. |
If the speed of an interface is automatically negotiated, the speed attribute of the interface includes the autonegotiation flag (the letter a in parentheses). If an interface is configured to autonegotiate its speed but the autonegotiation has not started, its speed attribute is displayed as auto. |
|
Duplex: (a)/A - auto; H - half; F - full |
If the duplex mode of an interface is automatically negotiated, the duplex mode attribute of the interface includes the letter a in parentheses. H indicates the half duplex mode. F indicates the full duplex mode. If an interface is configured to autonegotiate its duplex mode but the autonegotiation has not started, its duplex mode attribute is displayed as A. |
Type: A - access; T - trunk; H - hybrid |
Port link type options for interfaces. |
Protocol: (s) – spoofing |
The protocol attribute includes the spoofing flag (the letter s in parentheses) when the following conditions exist: · The data link layer protocol state of an interface is shown as UP. · The link is an on-demand link or is not present. |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been administratively shut down. To bring up the interface, use the undo shutdown command. · Stby—The interface is operating as a backup interface. |
Speed |
Interface speed, in bps. |
Protocol |
Data link layer state of the interface: · UP—The data link layer of the interface is up. · DOWN—The data link layer of the interface is down. · UP(s)—The data link layer of the interface is shown as UP, but its link is an on-demand link or is not present. |
Cause |
Cause for the physical link state of an interface to be DOWN. |
display lacp system-id
Use display lacp system-id to display the local system ID.
Syntax
display lacp system-id
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Usage guidelines
You can use the lacp system-priority command to change the LACP priority of the local system. The LACP priority value is specified in decimal format in the lacp system-priority command. However, it is displayed in hexadecimal format in the output from the display lacp system-id command.
Examples
# Display the local system ID.
<Sysname> display lacp system-id
Actor System ID: 0x8000, 0000-fc00-6504
Table 2 Command output
Field |
Description |
Actor System ID: 0x8000, 0000-fc00-6504 |
Local system ID, which contains the system LACP priority (0x8000 in this sample output) and the system MAC address (0000-FC00-6504 in this sample output). |
lacp system-priority
display link-aggregation load-sharing mode
Use display link-aggregation load-sharing mode to display global or group-specific link-aggregation load sharing modes.
Syntax
display link-aggregation load-sharing mode [ interface [ { bridge-aggregation | route-aggregation } interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
bridge-aggregation: Specifies Layer 2 aggregate interfaces.
route-aggregation: Specifies Layer 3 aggregate interfaces.
interface-number: Specifies an existing aggregate interface number.
Usage guidelines
If you do not specify the interface keyword, the command displays the global link-aggregation load sharing modes.
If you specify the interface keyword but do not specify an interface, the command displays all group-specific load sharing modes.
The bridge-aggregation or route-aggregation keyword is available only when the corresponding aggregate interfaces exist on the device.
Examples
# Display the default global link-aggregation load sharing modes.
<Sysname> display link-aggregation load-sharing mode
Link-aggregation load-sharing mode:
Layer 3 traffic: destination-ip address source-ip address
Layer 4 traffic: destination-ip address source-ip address
# Display the default link-aggregation load sharing modes of Layer 3 aggregation group 10.
<Sysname> display link-aggregation load-sharing mode interface route-aggregation 10
Route-Aggregation10 load-sharing mode:
Layer 3 traffic: destination-ip address source-ip address
Layer 4 traffic: destination-ip address source-ip address
Table 3 Command output
Field |
Description |
Link-aggregation load-sharing mode |
Global link-aggregation load sharing mode. By default, this field displays the link-aggregation load sharing modes for Layer 3 and Layer 4 traffic. If you have set the global link-aggregation load sharing mode, this field displays the set mode. |
Route-Aggregation10 load-sharing mode |
Link-aggregation load sharing mode of Layer 3 aggregation group 10. By default, this field displays the global link-aggregation load sharing modes. If you have set a link-aggregation load sharing mode for this aggregation group, this field displays the set mode. |
Layer 3 traffic: destination-ip address source-ip address |
Default link-aggregation load sharing mode for Layer 3 traffic. In this sample output, Layer 3 traffic is load shared based on source and destination IP addresses. |
Layer 4 traffic: destination-ip address source-ip address |
Default link-aggregation load sharing mode for Layer 4 traffic. In this sample output, Layer 4 traffic is load shared based on source and destination IP addresses. |
display link-aggregation member-port
Use display link-aggregation member-port to display detailed link aggregation information for the specified member ports.
Syntax
display link-aggregation member-port [ interface-list ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-list: Specifies a list of link aggregation member ports, in the format interface-type interface-number [ to interface-type interface-number ]. The interface-type interface-number argument specifies an interface by its type and number.
Usage guidelines
A member port in a static aggregation group cannot obtain information about the peer group. For such member ports, the command displays the port number, port priority, and operational key of only the local end.
Examples
# Display detailed link aggregation information for GigabitEthernet 2/1/1, which is a member port of a static aggregation group.
<Sysname> display link-aggregation member-port gigabitethernet 2/1/1
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
GigabitEthernet2/1/1:
Aggregate Interface: Route-Aggregation1
Port Number: 1
Port Priority: 32768
Oper-Key: 1
# Display detailed link aggregation information for GigabitEthernet 2/1/2, which is a member port of a dynamic aggregation group.
<Sysname> display link-aggregation member-port gigabitethernet 2/1/2
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
GigabitEthernet2/1/2:
Aggregate Interface: Route-Aggregation10
Local:
Port Number: 2
Port Priority: 32768
Oper-Key: 2
Flag: {ACDEF}
Remote:
System ID: 0x8000, 000f-e267-6c6a
Port Number: 26
Port Priority: 32768
Oper-Key: 2
Flag: {ACDEF}
Received LACP Packets: 5 packet(s)
Illegal: 0 packet(s)
Sent LACP Packets: 7 packet(s)
Table 4 Command output
Field |
Description |
Flags |
LACP state flags. This field is one byte long, represented by ABCDEFGH from the least significant bit to the most significant bit. A letter appears when its bit is 1 and does not appear when its bit is 0. · A—Indicates whether LACP is active on the port. 1 indicates active. 0 indicates passive. · B—Indicates the LACP timeout interval. 1 indicates the short timeout interval. 0 indicates the long timeout interval. · C—Indicates whether the sending system considers that the link is aggregatable. 1 indicates yes. 0 indicates no. · D—Indicates whether the sending system considers that the link has been aggregated. 1 indicates yes. 0 indicates no. · E—Indicates whether the sending system considers that the link can collect frames. 1 indicates yes. 0 indicates no. · F—Indicates whether the sending system considers that the link can distribute frames. 1 indicates yes. 0 indicates no. · G—Indicates whether the RX state machine of the sending system is in default state. 1 indicates yes. 0 indicates no. · H—Indicates whether the RX state machine of the sending system is in expired state. 1 indicates yes. 0 indicates no. |
Aggregate Interface |
Aggregate interface to which the member port belongs. |
Local |
Information about the local end. |
Oper-key |
Operational key. |
Flag |
LACP protocol state flag. |
Remote |
Information about the peer end. |
System ID |
Peer system ID, containing the system LACP priority and the system MAC address. |
Received LACP Packets |
Total number of LACP packets received. |
Illegal |
Total number of illegal packets. |
Sent LACP Packets |
Total number of LACP packets sent. |
display link-aggregation summary
Use display link-aggregation summary to display brief information about all aggregation groups.
Syntax
display link-aggregation summary
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Usage guidelines
Static link aggregation groups cannot obtain information about the peer groups. As a result, the Partner ID field displays None or nothing for a static link aggregation group.
Examples
# Display brief information about all aggregation groups.
<Sysname> display link-aggregation summary
Aggregate Interface Type:
BAGG -- Bridge-Aggregation, BLAGG –- Blade-Aggregation, RAGG -- Route-Aggregation, SCH-B – Schannel-Bundle
Aggregation Mode: S -- Static, D -- Dynamic
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Actor System ID: 0x8000, 000f-e267-6c6a
AGG AGG Partner ID Selected Unselected Individual Share
Interface Mode Ports Ports Ports Type
--------------------------------------------------------------------------------
BLAGG1 S None 0 0 0 Shar
RAGG10 S None 1 0 0 NonS
BAGG20 D 0x8000,00e0-fcff-ff01 2 0 0 Shar
SCH-B1 S None 0 0 0 Shar
Table 5 Command output
Field |
Description |
Aggregate Interface Type |
Aggregate interface type: · BAGG—Layer 2. · RAGG—Layer 3. |
Aggregation Mode |
Aggregation group type: · S—Static. · D—Dynamic. |
Loadsharing Type |
Load sharing type: · Shar—Load-sharing. · NonS—Non-load-sharing. |
Actor System ID |
Local system ID, which contains the local system LACP priority and the local system MAC address. |
AGG Interface |
Type and number of the aggregate interface. |
AGG Mode |
Aggregation group type. |
Partner ID |
System ID of the peer system, which contains the peer system LACP priority and the peer system MAC address. |
Selected Ports |
Total number of Selected ports. |
Unselected Ports |
Total number of Unselected ports. |
Individual Ports |
Total number of Individual ports. |
Share Type |
Load sharing type. |
display link-aggregation verbose
Use display link-aggregation verbose to display detailed information about the aggregation groups that correspond to the specified aggregate interfaces.
Syntax
display link-aggregation verbose [ { bridge-aggregation | route-aggregation } [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
bridge-aggregation: Specifies Layer 2 aggregate interfaces.
route-aggregation: Specifies Layer 3 aggregate interfaces.
interface-number: Specifies an existing aggregate interface by its number.
Usage guidelines
If you specify one of the following keywords but do not specify an interface number, the command displays detailed information about all aggregation groups of the specified type:
· bridge-aggregation
· route-aggregation
If you do not specify an aggregate interface type, the command displays detailed information about all aggregation groups.
The bridge-aggregation or route-aggregation keyword is available only when the corresponding aggregate interfaces exist on the device.
Examples
# Display detailed information about Layer 3 aggregation group 10, which is a dynamic aggregation group.
<Sysname> display link-aggregation verbose route-aggregation 10
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected, I -- Individual
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregate Interface: Route-Aggregation10
Aggregation Mode: Dynamic
Loadsharing Type: Shar
System ID: 0x8000, 000f-e267-6c6a
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
GE2/1/1 S 32768 2 {ACDEF}
GE2/1/2 S 32768 2 {ACDEF}
GE2/1/3 S 32768 2 {AG}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
GE2/1/1 1 32768 2 0x8000, 000f-e267-57ad {ACDEF}
GE2/1/2 2 32768 2 0x8000, 000f-e267-57ad {ACDEF}
GE2/1/3 0 32768 0 0x8000, 0000-0000-0000 {DEF}
Table 6 Command output
Field |
Description |
Loadsharing Type |
Load sharing type: · Shar—Load-sharing. · NonS—Non-load-sharing. |
Port Status |
Port state: Selected, Unselected, or Individual. |
Flags |
LACP state flags. This field is one byte long, represented by ABCDEFGH from the least significant bit to the most significant bit. A letter appears when its bit is 1 and does not appear when its bit is 0. · A—Indicates whether LACP is active on the port. 1 indicates active. 0 indicates passive. · B—Indicates the LACP timeout interval. 1 indicates the short timeout interval. 0 indicates the long timeout interval. · C—Indicates whether the sending system considers that the link is aggregatable. 1 indicates yes. 0 indicates no. · D—Indicates whether the sending system considers that the link has been aggregated. 1 indicates yes. 0 indicates no. · E—Indicates whether the sending system considers that the link can collect frames. 1 indicates yes. 0 indicates no. · F—Indicates whether the sending system considers that the link can distribute frames. 1 indicates yes. 0 indicates no. · G—Indicates whether the RX state machine of the sending system is in default state. 1 indicates yes. 0 indicates no. · H—Indicates whether the RX state machine of the sending system is in expired state. 1 indicates yes. 0 indicates no. |
Aggregate Interface |
Name of the aggregate interface. |
Aggregation Mode |
Aggregation group type: · S—Static. · D—Dynamic. |
System ID |
Local system ID, containing the local system LACP priority and the local system MAC address. |
Local |
Information about the local end: · Port—Port type and number. · Status—Port state, which can be Selected, Unselected, or Individual. · Priority—Port priority. · Oper-Key—Operational key. · Flag—LACP state flag. NOTE: For static aggregation groups, the Flag field is not displayed. |
Remote |
Information about the peer end: · Actor—Type and number of the local port. · Partner—Index of the peer port. · Priority—Priority of the peer port. · Oper-Key—Operational key of the peer port. · System ID—System ID of the peer end. · Flag—LACP state flag of the peer end. |
interface bridge-aggregation
Use interface bridge-aggregation to create a Layer 2 aggregate interface and enter its view, or enter the view of an existing Layer 2 aggregate interface.
Use undo interface bridge-aggregation to delete a Layer 2 aggregate interface.
Syntax
interface bridge-aggregation interface-number
undo interface bridge-aggregation interface-number
Default
No Layer 2 aggregate interfaces exist.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
interface-number: Specifies a Layer 2 aggregate interface number. The value range for the interface-number argument is 1 to 128.
Usage guidelines
When you create a Layer 2 aggregate interface, the system automatically creates a Layer 2 aggregation group with the same number. The aggregation group operates in static aggregation mode by default.
Deleting a Layer 2 aggregate interface also deletes the Layer 2 aggregation group. At the same time, the member ports of the aggregation group, if any, leave the aggregation group.
Examples
# Create Layer 2 aggregate interface Bridge-Aggregation 1, and enter its view.
<Sysname> system-view
[Sysname] interface bridge-aggregation 1
[Sysname-Bridge-Aggregation1]
interface route-aggregation
Use interface route-aggregation to create a Layer 3 aggregate interface or subinterface and enter its view, or enter the view of an existing Layer 3 aggregate interface or subinterface.
Use undo interface route-aggregation to delete a Layer 3 aggregate interface or subinterface.
Syntax
interface route-aggregation { interface-number | interface-number.subnumber }
undo interface route-aggregation { interface-number | interface-number.subnumber }
Default
No Layer 3 aggregate interfaces or subinterfaces exist.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
interface-number: Specifies a Layer 3 aggregate interface number. The value range for the interface-number argument is 1 to 4096.
interface-number.subnumber: Specifies a subinterface of a Layer 3 aggregate interface. The interface-number argument specifies the main interface number. The subnumber argument specifies the subinterface number and is separated from the main interface number by a dot (.). The value range for the subnumber argument is 1 to 4094.
Usage guidelines
When you create a Layer 3 aggregate interface, the system automatically creates a Layer 3 aggregation group with the same number. The Layer 3 aggregation group operates in static aggregation mode by default.
Deleting a Layer 3 aggregate interface also deletes the Layer 3 aggregation group. At the same time, the member ports of the aggregation group, if any, leave the aggregation group.
Deleting a Layer 3 aggregate subinterface does not affect the state of the main interface and the corresponding aggregation group.
Examples
# Create Layer 3 aggregate interface Route-Aggregation 1 and enter its view.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1]
# Create Layer 3 aggregate subinterface Route-Aggregation 1.1 and enter its view.
<Sysname> system-view
[Sysname] interface route-aggregation 1.1
[Sysname-Route-Aggregation1.1]
lacp edge-port
Use lacp edge-port to configure an aggregate interface as an edge aggregate interface.
Use undo lacp edge-port to restore the default.
Syntax
lacp edge-port
undo lacp edge-port
Default
An aggregate interface does not operate as an edge aggregate interface.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
Use this command on the aggregate interface that connects the device to a server if dynamic link aggregation is configured only on the device. This feature improves link reliability by enabling all member ports of the aggregation group to forward packets.
This command takes effect only on an aggregate interface corresponding to a dynamic aggregation group.
Link-aggregation traffic redirection cannot operate correctly on an edge aggregate interface.
Examples
# Configure Layer 3 aggregate interface Route-Aggregation 1 as an edge aggregate interface.
<Sysname> System-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] lacp edge-port
lacp mode
Use lacp mode passive to configure LACP to operate in passive mode on a port.
Use undo lacp mode to restore the default.
Syntax
lacp mode passive
undo lacp mode
Default
LACP operates in active mode on a port.
Views
Layer 2 Ethernet interface view
Layer 3 Ethernet interface view
Layer 3 Ethernet subinterface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
When LACP is operating in passive mode on a local member port and its peer port, both ports cannot send LACPDUs. When LACP is operating in active mode on either end of a link, both ports can send LACPDUs.
This command takes effect only on member ports of dynamic aggregation groups.
Examples
# Configure LACP to operate in passive mode on GigabitEthernet 2/1/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 2/1/1
[Sysname-GigabitEthernet2/1/1] lacp mode passive
lacp period short
Use lacp period short to enable the short LACP timeout interval (3 seconds) on an interface.
Use undo lacp period to restore the default.
Syntax
lacp period short
undo lacp period
Default
An interface uses the long LACP timeout interval (90 seconds).
Views
Layer 3 Ethernet interface view
Layer 3 Ethernet subinterface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
To avoid traffic interruption during an ISSU, do not enable the short LACP timeout interval before performing the ISSU. For more information about ISSU, see Fundamentals Configuration Guide.
Examples
# Enable the short LACP timeout interval (3 seconds) on GigabitEthernet 2/1/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 2/1/1
[Sysname-GigabitEthernet2/1/1] lacp period short
lacp system-priority
Use lacp system-priority to set the system LACP priority.
Use undo lacp system-priority to restore the default.
Syntax
lacp system-priority priority
undo lacp system-priority
Default
The system LACP priority is 32768.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
priority: Specifies the system LACP priority in the range of 0 to 65535. The smaller the value, the higher the system LACP priority.
Examples
# Set the system LACP priority to 64.
<Sysname> system-view
[Sysname] lacp system-priority 64
Related commands
link-aggregation port-priority
link-aggregation bfd ipv4
Use link-aggregation bfd ipv4 to enable BFD for an aggregation group.
Use undo link-aggregation bfd to disable BFD for an aggregation group.
Syntax
link-aggregation bfd ipv4 source ip-address destination ip-address
undo link-aggregation bfd
Default
BFD is disabled for an aggregation group.
Views
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Parameters
source ip-address: Specifies the source IP address of BFD sessions.
destination ip-address: Specifies the destination IP address of BFD sessions.
Usage guidelines
An aggregation group does not support BFD if it contains interfaces on a FIP-600 module.
The source and destination IP addresses of BFD sessions must be unicast addresses. Make sure the source and destination IP addresses are consistent between the two ends of an aggregate link. For example, if you execute link-aggregation bfd ipv4 source 1.1.1.1 destination 2.2.2.2 at the local end, execute link-aggregation bfd ipv4 source 2.2.2.2 destination 1.1.1.1 at the peer end.
The BFD parameters configured on the aggregate interface take effect on all its member interfaces' BFD sessions. BFD sessions for link aggregation do not support the echo packet mode or the Demand mode. For more information about BFD, see High Availability Configuration Guide.
As a best practice, do not configure other features to collaborate with BFD on a BFD-enabled aggregate interface.
Make sure the number of member ports in a BFD-enabled aggregation group is less than or identical to the number of BFD sessions supported by the device. If the aggregation group contains more member ports than the supported sessions, some Selected ports might change to the Unselected state.
Examples
# Enable BFD for Layer 3 aggregation group 1, and specify the source and destination IP addresses as 1.1.1.1 and 2.2.2.2 for BFD sessions.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] link-aggregation bfd ipv4 source 1.1.1.1 destination 2.2.2.2
link-aggregation global load-sharing mode
Use link-aggregation global load-sharing mode to set the global link-aggregation load sharing mode.
Use undo link-aggregation global load-sharing mode to restore the default.
Syntax
link-aggregation global load-sharing mode { { destination-ip | destination-mac | destination-port | source-ip | source-mac | source-port } * | per-packet }
undo link-aggregation global load-sharing mode
Default
The device load shares traffic based on source and destination IP addresses.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
destination-ip: Distributes traffic based on destination IP addresses.
destination-mac: Distributes traffic based on destination MAC addresses.
destination-port: Distributes traffic based on destination ports.
source-ip: Distributes traffic based on source IP addresses.
source-mac: Distributes traffic based on source MAC addresses.
source-port: Distributes traffic based on source ports.
per-packet: Distributes traffic on a per-packet basis.
Usage guidelines
If you execute this command multiple times, the most recent configuration takes effect.
If an unsupported load sharing mode is set, an error prompt appears.
Examples
# Set the global load sharing mode to load share packets based on destination MAC addresses.
<Sysname> system-view
[Sysname] link-aggregation global load-sharing mode destination-mac
Related commands
link-aggregation load-sharing mode
link-aggregation ignore vlan
Use link-aggregation ignore vlan to configure a Layer 2 aggregate interface to ignore VLANs.
Use undo link-aggregation ignore vlan to remove ignored VLANs from a Layer 2 aggregate interface.
Syntax
link-aggregation ignore vlan vlan-id-list
undo link-aggregation ignore vlan vlan-id-list
Default
A Layer 2 aggregate interface does not ignore any VLANs. To become Selected, a member port must have the same VLAN permit state and tagging mode as the Layer 2 aggregate interface for all VLANs.
Views
Layer 2 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Parameters
vlan-id-list: Specifies a space-separated list of up to 10 VLAN items. Each item specifies a VLAN ID or a range of VLAN IDs in the form of vlan-id1 to vlan-id2. The value range for VLAN IDs is 1 to 4094. The value for vlan-id2 must be equal to or greater than the value for vlan-id1.
Usage guidelines
To ignore the VLAN permit state and tagging mode of a VLAN when choosing Selected ports, specify the VLAN as an ignored VLAN. A member port can become Selected even if it does not have the same VLAN permit or tagging mode as the Layer 2 aggregate interface for an ignored VLAN.
Examples
# Configure interface bridge-aggregation 1 to ignore VLAN 50.
<Sysname> system-view
[Sysname] interface bridge-aggregation 1
[Sysname-Bridge-Aggregation1] link-aggregation ignore vlan 50
link-aggregation lacp traffic-redirect-notification enable
Use link-aggregation lacp traffic-redirect-notification enable to enable link-aggregation traffic redirection.
Use undo link-aggregation lacp traffic-redirect-notification enable to disable link-aggregation traffic redirection.
Syntax
link-aggregation lacp traffic-redirect-notification enable
undo link-aggregation lacp traffic-redirect-notification enable
Default
Link-aggregation traffic redirection is disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
When you restart a card that contains Selected ports in a multimodule dynamic aggregation, this feature redirects the traffic on the ports to the remaining cards. Zero packet loss is guaranteed for known unicast traffic, but not for unknown unicast traffic. (In standalone mode.)
When you restart an IRF member device that contains Selected ports in a multichassis dynamic aggregation, this feature redirects the traffic on the ports to the remaining IRF member devices. When you restart a card that contains Selected ports in a multimodule dynamic aggregation, this feature redirects the traffic on the ports to the remaining cards. Zero packet loss is guaranteed for known unicast traffic, but not for unknown unicast traffic. (In IRF mode.)
Link-aggregation traffic redirection applies only to dynamic link aggregation groups.
To prevent traffic interruption, enable link-aggregation traffic redirection on devices at both ends of the aggregate link.
Do not enable both spanning tree and link-aggregation traffic redirection on a device. Otherwise, light packet loss might occur when a card or the device reboots.
Link-aggregation traffic redirection cannot operate correctly on an edge aggregate interface.
Examples
# Enable link-aggregation traffic redirection.
<Sysname> system-view
[Sysname] link-aggregation lacp traffic-redirect-notification enable
link-aggregation load-sharing mode
Use link-aggregation load-sharing mode to set the link-aggregation load sharing mode for an aggregation group.
Use undo link-aggregation load-sharing mode to restore the default.
Syntax
link-aggregation load-sharing mode { { destination-ip | destination-mac | destination-port | ip-protocol | mpls-label1 | mpls-label2 | mpls-label3 | source-ip | source-mac | source-port } * | bandwidth-usage | per-packet }
undo link-aggregation load-sharing mode
Default
The group-specific load sharing mode is the same as the global load sharing mode.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Parameters
destination-ip: Distributes traffic based on destination IP addresses.
destination-mac: Distributes traffic based on destination MAC addresses. This keyword is supported only by Layer 2 aggregate interfaces.
destination-port: Distributes traffic based on destination ports.
ip-protocol: Distributes traffic based on IP protocol types.
mpls-label1: Distributes MPLS traffic based on Layer 1 labels.
mpls-label2: Distributes MPLS traffic based on Layer 2 labels.
mpls-label3: Distributes MPLS traffic based on Layer 3 labels.
source-ip: Distributes traffic based on source IP addresses.
source-mac: Distributes traffic based on source MAC addresses. This keyword is supported only by Layer 2 aggregate interfaces.
source-port: Distributes traffic based on source ports.
bandwidth-usage: Distributes a data flow to the Selected port that has the lowest bandwidth usage when the first packet of that data flow arrives. In this mode, each flow is identified by an IP five-tuple (source and destination IP addresses, source and destination ports, and protocol). This keyword is supported only for aggregate interfaces that use member ports on a FIP-240, FIP-300, or FIP-310 module.
per-packet: Distributes traffic on a per-packet basis.
Usage guidelines
|
IMPORTANT: If you configure one aggregation group to load shard traffic based on bandwidth usage, any of the following operations might affect the traffic load sharing in the aggregation group: · Setting the global load sharing mode. · Setting the load sharing modes for other aggregation groups. Make sure you are fully aware of the impacts when you perform these operations. |
If you execute this command multiple times, the most recent configuration takes effect.
If you set an unsupported load sharing mode, you will receive an error message.
Examples
# Configure Layer 3 aggregation group 1 to load share packets based on destination IP addresses.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] link-aggregation load-sharing mode destination-ip
Related commands
link-aggregation global load-sharing mode
link-aggregation load-sharing mode local-first
Use link-aggregation load-sharing mode local-first to enable local-first load sharing for link aggregation.
Use undo link-aggregation load-sharing mode local-first to disable local-first load sharing for link aggregation.
Syntax
link-aggregation load-sharing mode local-first
undo link-aggregation load-sharing mode local-first
Default
Local-first load sharing is enabled for link aggregation.
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
After you disable local-first load sharing, the packets will be load shared among all Selected ports of the aggregate interface on all IRF member devices.
Examples
# Disable local-first load sharing for link aggregation.
<Sysname> system-view
[Sysname] undo link-aggregation load-sharing mode local-first
link-aggregation load-sharing mpls enhanced
Use link-aggregation load-sharing mpls enhanced to enable link-aggregation load sharing enhancement for MPLS packets.
Use undo link-aggregation load-sharing mpls enhanced to disable link-aggregation load sharing enhancement for MPLS packets.
Syntax
link-aggregation load-sharing mpls enhanced
undo link-aggregation load-sharing mpls enhanced
Default
Link-aggregation load sharing enhancement is disabled for MPLS packets.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
This command enables an aggregate interface to use IP five-tuple information for MPLS packet distribution. The IP five-tuple is the source IP address, source port number, destination IP address, destination port number, and protocol number.
Use this command only on the provider (P) device. For information about the P device, see MPLS L3VPN configuration in MPLS Configuration Guide.
Examples
# Enable link-aggregation load sharing enhancement for MPLS packets on Route-Aggregation 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] link-aggregation load-sharing mpls enhanced
link-aggregation mode
Use link-aggregation mode dynamic to configure an aggregation group to operate in dynamic aggregation mode and enable LACP.
Use undo link-aggregation mode to restore the default.
Syntax
link-aggregation mode dynamic
undo link-aggregation mode
Default
An aggregation group operates in static aggregation mode.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Examples
# Configure Layer 3 aggregation group 1 to operate in dynamic aggregation mode.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] link-aggregation mode dynamic
link-aggregation port-priority
Use link-aggregation port-priority to set the port priority of an interface.
Use undo link-aggregation port-priority to restore the default.
Syntax
link-aggregation port-priority priority
undo link-aggregation port-priority
Default
The port priority of an interface is 32768.
Views
Layer 2 Ethernet interface view
Layer 3 Ethernet interface view
Layer 3 Ethernet subinterface view
Predefined user roles
network-admin
mdc-admin
Parameters
priority: Specifies the port priority in the range of 0 to 65535. The smaller the value, the higher the port priority.
Examples
# Set the port priority to 64 for Layer 3 Ethernet interface GigabitEthernet 2/1/2.
<Sysname> system-view
[Sysname] interface gigabitethernet 2/1/2
[Sysname-GigabitEthernet2/1/2] link-aggregation port-priority 64
Related commands
lacp system-priority
link-aggregation selected-port maximum
Use link-aggregation selected-port maximum to set the maximum number of Selected ports allowed in an aggregation group.
Use undo link-aggregation selected-port maximum to restore the default.
Syntax
link-aggregation selected-port maximum max-number
undo link-aggregation selected-port maximum
Default
The maximum number of Selected ports allowed in an aggregation group depends on hardware limitation.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Parameters
max-number: Specifies the maximum number of Selected ports allowed in an aggregation group. The value range for this argument is 1 to 8.
Usage guidelines
Executing this command might cause some of the Selected ports in an aggregation group to become Unselected ports.
The maximum number of Selected ports allowed in the aggregation groups must be the same for the local and peer ends.
The maximum number of Selected ports allowed in an aggregation group is limited by one of the following values, whichever value is smaller:
· Maximum number set by using the link-aggregation selected-port maximum command.
· Hardware limitation.
You can implement backup between two ports by performing the following tasks:
· Assign two ports to an aggregation group.
· Configure 1 as the maximum number of Selected ports allowed in the aggregation group.
Then, only one Selected port is allowed in the aggregation group at any point in time, while the Unselected port acts as a backup port.
Examples
# Set the maximum number of Selected ports to 5 for Layer 3 aggregation group 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] link-aggregation selected-port maximum 5
Related commands
link-aggregation selected-port minimum
link-aggregation selected-port minimum
Use link-aggregation selected-port minimum to set the minimum number of Selected ports in an aggregation group.
Use undo link-aggregation selected-port minimum to restore the default.
Syntax
link-aggregation selected-port minimum min-number
undo link-aggregation selected-port minimum
Default
The minimum number of Selected ports in an aggregation group is not specified.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Parameters
min-number: Specifies the minimum number of Selected ports in an aggregation group required to bring up the aggregate interface. The value range for this argument is 1 to 8.
Usage guidelines
Executing this command might cause all member ports in the aggregation group to become Unselected ports.
The minimum number of Selected ports allowed in the aggregation groups must be the same for the local and peer ends.
Examples
# Set the minimum number of Selected ports to 3 for Layer 3 aggregation group 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] link-aggregation selected-port minimum 3
Related commands
link-aggregation selected-port maximum
mtu
Use mtu to set the MTU for a Layer 3 aggregate interface or subinterface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU for Layer 3 aggregate interfaces and subinterfaces is 1500 bytes.
Views
Layer 3 aggregate interface view
Layer 3 aggregate subinterface view
Predefined user roles
network-admin
mdc-admin
Parameters
size: Specifies the MTU in bytes. The value range for this argument is 46 to 9600.
Examples
# Set the MTU to 1430 bytes for Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] mtu 1430
display interface
port link-aggregation group
Use port link-aggregation group to assign an interface or subinterface to an aggregation group.
Use undo port link-aggregation group to remove an interface or subinterface from an aggregation group.
Syntax
port link-aggregation group group-id
undo port link-aggregation group
Default
An interface or subinterface does not belong to an aggregation group.
Views
Layer 2 Ethernet interface view
Layer 3 Ethernet interface view
Layer 3 Ethernet subinterface view
Predefined user roles
network-admin
mdc-admin
Parameters
group-id: Specifies an existing aggregation group by its aggregate interface number.
Usage guidelines
An interface or subinterface can belong to only one aggregation group.
· If the aggregation group is for a Layer 2 aggregate interface, the member interfaces must be Layer 2 Ethernet interfaces.
· If the aggregation group is for a Layer 3 aggregate interface, the member interfaces must be Layer 3 Ethernet interfaces or subinterfaces, but not both.
If you are assigning a Layer 3 Ethernet interface to an aggregation group, make sure it does not have subinterfaces. You cannot create subinterfaces on a Layer 3 Ethernet interface after it is assigned to an aggregation group.
If you are assigning a Layer 3 Ethernet subinterface to an aggregation group, follow these restrictions and guidelines:
· You cannot assign Layer 3 Ethernet subinterfaces on a FIP-600 module to a aggregation group.
· Configure VLAN termination before you assign the subinterface to the aggregation group. You cannot modify the VLAN termination configuration after the subinterface is assigned to an aggregation group. The following are VLAN termination commands you might use:
¡ vlan-type dot1q default
¡ vlan-type dot1q untagged
¡ vlan-type dot1q vid
¡ vlan-type dot1q vid second-dot1q
For information about the VLAN termination commands, see "VLAN termination commands."
· All Layer 3 Ethernet subinterfaces in an aggregation group must have the same VLAN termination configuration.
· If you are assigning a subinterface to a dynamic aggregation group, specify only the outer VLAN ID when you use the vlan-type dot1q vid vlan-id-list [ loose ] command on that subinterface.
For a Layer 3 aggregate interface, aggregate subinterfaces and Layer 3 subinterfaces cannot coexist.
· You cannot create aggregate subinterfaces on a Layer 3 aggregate interface if its aggregation group contains Layer 3 Ethernet subinterfaces.
· You cannot assign Layer 3 Ethernet subinterfaces to an aggregation group if its aggregate interface has aggregate subinterfaces.
Examples
# Assign Layer 2 Ethernet interface GigabitEthernet 2/1/1 to Layer 2 aggregation group 1.
<Sysname> system-view
[Sysname] interface gigabitethernet 2/1/1
[Sysname-GigabitEthernet2/1/1] port link-aggregation group 1
# Assign Layer 3 Ethernet interface GigabitEthernet 2/1/2 to Layer 3 aggregation group 2.
<Sysname> system-view
[Sysname] interface gigabitethernet 2/1/2
[Sysname-GigabitEthernet2/1/2] port link-aggregation group 2
reset counters interface
Use reset counters interface to clear statistics for the specified aggregate interfaces.
Syntax
reset counters interface [ { bridge-aggregation | route-aggregation } [ interface-number ] ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
bridge-aggregation: Specifies Layer 2 aggregate interfaces.
route-aggregation: Specifies Layer 3 aggregate interfaces.
interface-number: Specifies an existing aggregate interface number.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
If you do not specify any parameters, the command clears statistics for all interfaces in the system.
If you specify only one of the following keywords, the command clears statistics for all aggregate interfaces of the specified type:
· bridge-aggregation
· route-aggregation
If you specify one of the following options, the command clears statistics for the specified aggregate interface.
· bridge-aggregation interface-number
· route-aggregation interface-number
The bridge-aggregation or route-aggregation keyword is available only when the corresponding aggregate interfaces exist on the device.
Examples
# Clear statistics for Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> reset counters interface route-aggregation 1
reset lacp statistics
Use reset lacp statistics to clear LACP statistics for the specified link aggregation member ports.
Syntax
reset lacp statistics [ interface interface-list ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
interface interface-list: Specifies a list of link aggregation member ports, in the format interface-type interface-number [ to interface-type interface-number ]. The interface-type interface-number argument specifies an interface by its type and number. If you do not specify any member ports, the command clears LACP statistics for all member ports.
Examples
# Clear LACP statistics for all link aggregation member ports.
<Sysname> reset lacp statistics
display link-aggregation member-port
service
Use service to specify a primary traffic processing slot for an interface.
Use undo service to restore the default.
Syntax
In standalone mode:
service slot slot-number
undo service slot
In IRF mode:
service chassis chassis-number slot slot-number
undo service chassis
Default
No primary traffic processing slot is specified for an interface.
Views
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Parameters
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Usage guidelines
Specify a traffic processing slot for all traffic on a Layer 3 aggregate interface to be processed on the same slot. If the aggregate interface contains subinterfaces, traffic on the subinterfaces is not processed on the specified slot.
For high availability, you can specify one primary and one backup traffic processing slot by using the service command and the service standby command, respectively.
To avoid processing slot switchover, specify the primary slot before specifying the backup slot. If you specify the backup slot before specifying the primary slot, traffic is switched over to the primary slot immediately after you specify the primary slot.
If you specify both primary and backup slots for an interface, traffic on that interface is processed as follows:
· The backup slot takes over when the primary slot becomes unavailable. The backup slot continues to process traffic for the interface after the primary slot becomes available again. The switchover will not occur until the backup slot becomes unavailable.
· When no specified traffic processing slots are available, the traffic is processed on the slot at which it arrives. Then, the processing slot that first becomes available again takes over.
If you do not specify a primary or a backup traffic processing slot for an interface, traffic on that interface is processed on the slot at which the traffic arrives.
Examples
# Specify a primary traffic processing slot for Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] service slot 2
Related commands
service standby
service standby
Use service standby to specify a backup traffic processing slot for an interface.
Use undo service standby to restore the default.
Syntax
In standalone mode:
service standby slot slot-number
undo service standby slot
In IRF mode:
service standby chassis chassis-number slot slot-number
undo service standby chassis
Default
No backup traffic processing slot is specified for an interface.
Views
Layer 3 aggregate interface view
Predefined user roles
network-admin
mdc-admin
Parameters
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Usage guidelines
Specify a traffic processing slot for all traffic on a Layer 3 aggregate interface to be processed on the same slot. If the aggregate interface contains subinterfaces, traffic on the subinterfaces is not processed on the specified slot.
For high availability, you can specify one primary and one backup traffic processing slot by using the service command and the service standby command, respectively.
To avoid processing slot switchover, specify the primary slot before specifying the backup slot. If you specify the backup slot before specifying the primary slot, traffic is switched over to the primary slot immediately after you specify the primary slot.
If you specify both primary and backup slots for an interface, traffic on that interface is processed as follows:
· The backup slot takes over when the primary slot becomes unavailable. The backup slot continues to process traffic for the interface after the primary slot becomes available again. The switchover will not occur until the backup slot becomes unavailable.
· When no specified traffic processing slots are available, the traffic is processed on the slot at which it arrives. Then, the processing slot that first becomes available again takes over.
If you do not specify a primary or a backup traffic processing slot for an interface, traffic on that interface is processed on the slot at which the traffic arrives.
Examples
# Specify a primary and a backup traffic processing slots for Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] service slot 2
[Sysname-Route-Aggregation1] service standby slot 3
Related commands
service
shutdown
Use shutdown to shut down an aggregate interface or subinterface.
Use undo shutdown to bring up an aggregate interface or subinterface.
Syntax
shutdown
undo shutdown
Default
All aggregate interfaces are administratively up. An aggregate subinterface is up if the main aggregate interface is up.
Views
Layer 2 aggregate interface view
Layer 3 aggregate interface view
Layer 3 aggregate subinterface view
Predefined user roles
network-admin
mdc-admin
Examples
# Bring up Layer 3 aggregate interface Route-Aggregation 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] undo shutdown