Reth interface commands -- bandwidth

Use bandwidth to set the expected bandwidth for a Reth interface.

Use undo bandwidth to restore the default.

Syntax

bandwidth bandwidth-value

undo bandwidth

Default

The expected bandwidth is 10000 kbps for a Reth interface.

Views

Reth interface 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 50 kbps for Reth 1.

<Sysname> system-view

[Sysname] interface reth 1

[Sysname-Reth1] bandwidth 50

Reth interface commands -- default

Use default to restore the default settings for a Reth interface.

Syntax

default

Views

Reth interface 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.

To resolve this problem:

1. Use the display this command in interface view to identify these commands.

2. Use their undo forms or follow the command reference to restore their default settings.

3. If the restoration attempt still fails, follow the error message instructions to resolve the problem.

Examples

# Restore the default settings for Reth 1.

<Sysname> system-view

[Sysname] interface reth 1

[Sysname-Reth1] default

Reth interface commands -- description

Use description to configure the description of an interface.

Use undo description to restore the default.

Syntax

description text

undo description

Default

The description of a Reth interface is interface-name plus Interface (for example, Reth1 Interface).

Views

Reth interface view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Examples

# Configure the description of Reth 1 as master-interface.

<Sysname> system-view

[Sysname] interface reth 1

[Sysname-Reth1] description master-interface

Reth interface commands -- display interface reth

Use display interface reth to display Reth interface information.

Syntax

display interface [ reth [ interface-number ] ] [ brief [ description | down ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

reth [ interface-number ]: Specifies Reth interfaces. The interface-number argument specifies an existing Reth interface by its number. If you do not specify the reth keyword, the command displays information about all interfaces. If you specify the reth keyword without the interface-number argument, the command displays information about all Reth interfaces.

brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.

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.

description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of each interface description.

Examples

# Display detailed information about Reth 1.

<Sysname> display interface reth 1

Reth1

Current state: UP

Line protocol state: UP

Description: Reth1 Interface

Bandwidth: 10000kbps

Maximum transmission unit: 1500

Internet protocol processing: Disabled

IP packet frame type: Ethernet II, hardware address: 0cda-41b5-cf30

IPv6 packet frame type: Ethernet II, hardware address: 0cda-41b5-cf30

Physical: Reth, baudrate: 10000000 bps

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

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

Table 1 Command output

Field | Description
Current state | Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. A Reth interface is both administratively and physically up when a minimum of one member interface is administratively and physically up.
Line protocol state | Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · DOWN—The data link layer protocol is down.
Description | Description of the interface.
Bandwidth | Expected bandwidth of the interface.
Maximum transmission unit | MTU of the interface.
Internet protocol processing: Disabled | The interface is not assigned an IP address and cannot process IP packets.
Internet Address | IP address of the interface. The primary attribute indicates that the address is the primary IP address.
IP packet frame type | IPv4 packet framing format.
hardware address | MAC address of the interface.
IPv6 packet frame type | IPv6 packet framing format.
Physical | Interface type.
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.
Last clearing of counters | Last time when the reset counters interface command was used to clear the interface statistics. If the reset counters interface command has never been used on the interface since the device startup, this field displays Never.
Last 300 second input: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 second output: 0 bytes/sec, 0 bits/sec, 0 packets/sec | Average incoming and outgoing traffic rate for the last 300 seconds.
Input: 0 packets, 0 bytes, 0 drops | Incoming traffic statistics on the interface: · Number of packets. · Number of bytes. · Number of dropped packets due to insufficient receive buffer.
Output: 0 packets, 0 bytes, 0 drops | Outgoing traffic statistics on the interface: · Number of packets. · Number of bytes. · Number of dropped packets due to insufficient send buffer.
Brief information on interfaces in route mode | Brief information about Layer 3 interfaces.
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 shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command.
Protocol | Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag.
Primary IP | Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address.
Description | Description of the interface.

# Display brief information about Reth 1.

<Sysname> display interface reth 1 brief

Brief information on interfaces in route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface Link Protocol Primary IP Description

Reth1 DOWN DOWN --

# Display the causes for the down state of Reth 1.

<Sysname> display interface reth 1 brief down

Brief information on interfaces in route mode:

Link: ADM - administratively down; Stby - standby

Interface Link Cause

Reth1 DOWN Not connected

Table 2 Command output

Field | Description
Brief information on interfaces in route mode: | Brief information about Layer 3 interfaces.
Interface | 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 shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command.
Protocol | Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces.
Primary IP | Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address.
Description | Description of the interface.
Cause | Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty).

Reth interface commands -- display reth interface

Use display reth interface to display information about the member interfaces of a Reth interface.

Syntax

display reth interface reth interface-number

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

reth interface-number: Specifies a Reth interface by its number. The value range for the interface-number argument varies by device model.

Examples

# (Centralized IRF devices.) Display information about the member interfaces of Reth 1.

<Sysname> display reth interface reth 1

Reth1 :

Redundancy group : aaa

Member Physical status Forwarding status Presence status

GE1/0/1 UP Active Normal

GE1/0/2 UP Inactive Normal

# (Distributed devices in IRF mode.) Display information about the member interfaces of Reth 1.

<Sysname> display reth interface reth 1

Reth1 :

Redundancy group : aaa

Member Physical status Forwarding status Presence status

GE1/1/0/1 UP Active Normal

GE1/1/0/2 UP Inactive Normal

Table 3 Command output

Field | Description
Redundancy group | The redundancy group to which the Reth interface belongs. If the Reth interface is not in any redundancy group, this field displays N/A.
Member | Name of the member interface.
Physical status | Physical status of the member interface: · Down (redundancy down)—The interface has been shut down by the Reth module. · Down—The interface is administratively up but physically down possibly because no physical link is present or the link has failed. · UP—The interface is both administratively and physically up.
Forwarding status | Forwarding status of the member interface: · Active—The member interface can forward packets. · Inactive—The member interface cannot forward packets.
Presence status | Status of the member interface: · Normal—The member interface exists. · Absent—The member interface does not exist.

Reth interface commands -- interface reth

Use interface reth to create a Reth interface and enter its view, or enter the view of an existing Reth interface.

Use undo interface reth to delete a Reth interface.

Syntax

interface reth interface-number

undo interface reth interface-number

Default

No Reth interfaces exist.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

interface-number: Specifies a Reth interface by its number. The value range for this argument varies by device model.

Usage guidelines

A Reth interface is a virtual Layer 3 interface that uses two member interfaces to ensure link availability.

You cannot delete a Reth interface if it has member interfaces.

Examples

# Create Reth 1 and enter its view.

<Sysname> system-view

[Sysname] interface reth 1

[Sysname-Reth1]

Reth interface commands -- member interface

Use member interface to assign a member interface to a Reth interface.

Use undo member interface to remove a member interface from a Reth interface.

Syntax

member interface interface-type interface-number priority priority

undo member interface interface-type interface-number

Default

A Reth interface does not have member interfaces.

Views

Reth interface view

Predefined user roles

network-admin

mdc-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number.

The interface can be any of the following interfaces and their subinterfaces:

· Layer 3 Ethernet interfaces.

· Layer 3 aggregate interfaces.

· EFM interfaces

priority: Specifies an interface priority in the range of 1 to 255. The higher the value, the higher the interface priority.

Usage guidelines

You can assign a maximum of two member interfaces to a Reth interface. An interface can belong to only one Reth interface.

As a best practice, assign interfaces of the same type and same speed to a Reth interface.

When the two member interfaces of a Reth interface are up, the system chooses the interface with the higher priority as the active interface to forward packet. The interface with the lower priority is inactive and cannot forward packets.

Do not specify a Reth interface as the outgoing interface in IPv6 static neighbor entries if its member interfaces contain subinterfaces. For more information about IPv6 static neighbor entries, see Layer 3—IP Services Configuration Guide.

Examples

# (Centralized IRF devices.) Assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to Reth 1, and set their priority to 100 and 50, respectively.

<Sysname> system-view

[Sysname] interface reth 1

[Sysname-Reth1] member interface gigabitethernet 1/0/1 priority 100

[Sysname-Reth1] member interface gigabitethernet 1/0/2 priority 50

# (Distributed devices in IRF mode.) Assign GigabitEthernet 1/1/0/1 and GigabitEthernet 1/1/0/2 to Reth 1, and set their priority to 100 and 50, respectively.

<Sysname> system-view

[Sysname] interface reth 1

[Sysname-Reth1] member interface gigabitethernet 1/1/0/1 priority 100

[Sysname-Reth1] member interface gigabitethernet 1/1/0/2 priority 50

Reth interface commands -- mtu

Use mtu to set the MTU of a Reth interface.

Use undo mtu to restore the default.

Syntax

mtu size

undo mtu

Default

The MTU is 1500 bytes for a Reth interface.

Views

Reth interface view

Predefined user roles

network-admin

mdc-admin

Parameters

size: Specifies the MTU in bytes. The value range for this argument varies by device model.

Usage guidelines

The MTU size of a Reth interface affects the fragmentation and reassembly of IP packets on the interface.

For the configured MTU size to take effect, execute the shutdown command, and then the undo shutdown command on the interface.

Examples

# Set the MTU to 200 bytes for Reth 1.

<Sysname> system-view

[Sysname] interface reth 1

[Sysname-Reth1] mtu 200

Reth interface commands -- reset counters interface reth

Use reset counters interface reth to clear statistics for Reth interfaces.

Syntax

reset counters interface [ reth [ interface-number ] ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

reth [ interface-number ]: Specifies Reth interfaces. The interface-number argument specifies an existing Reth interface by its number. If you do not specify the reth keyword, the command clears statistics for all interfaces. If you specify the reth keyword without the interface-number argument, the command clears statistics for all Reth interfaces.

Usage guidelines

Use this command to clear history statistics before you collect traffic statistics for a time period.

Examples

# Clear statistics for Reth 1.

<Sysname> reset counters interface reth 1

Reth interface commands -- shutdown

Use shutdown to shut down a Reth interface.

Use undo shutdown to bring up a Reth interface.

Syntax

shutdown

undo shutdown

Default

The default for this command varies by device model.

Views

Reth interface view

Predefined user roles

network-admin

mdc-admin

Examples

# Shut down Reth 1.

<Sysname> system-view

[Sysname] interface reth 1

[Sysname-Reth1] shutdown

Redundancy group commands -- bind chassis

Use bind chassis to bind a redundancy group node to an IRF member device.

Use undo bind chassis to remove the binding between a redundancy group node and an IRF member device.

Syntax

bind chassis chassis-number

undo bind chassis

Default

A redundancy group node is not bound to an IRF member device.

Views

Redundancy group node view

Predefined user roles

network-admin

mdc-admin

Parameters

chassis-number: Specifies an IRF member device by its member ID.

Usage guidelines

You can create only one-to-one bindings between redundancy group nodes and IRF member devices.

The node in a binding can use interfaces of the bound IRF member device as members. Member interfaces on one node of a redundancy group back up the member interfaces on the other node.

You cannot change the binding for a node if the node has member interfaces.

Examples

# Bind node 1 in redundancy group aaa to IRF member device 3.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] node 1

[Sysname-redundancy-group-aaa-node1] bind chassis 3

Redundancy group commands -- bind slot

Use bind slot to bind a redundancy group node to an IRF member device.

Use undo bind slot to remove the binding between a redundancy group node and an IRF member device.

Syntax

bind slot slot-number

undo bind slot

Default

A redundancy group node is not bound to an IRF member device.

Views

Redundancy group node view

Predefined user roles

network-admin

mdc-admin

Parameters

slot-number: Specifies an IRF member device by its member ID.

Usage guidelines

You can create only one-to-one bindings between redundancy group nodes and IRF member devices.

The node in a binding can use interfaces of the bound IRF member device as members. Member interfaces on one node of a redundancy group back up the member interfaces on the other node.

You cannot change the binding for a node if the node has member interfaces.

Examples

# Bind node 1 in redundancy group aaa to IRF member device 1.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] node 1

[Sysname-redundancy-group-aaa-node1] bind slot 1

Redundancy group commands -- display redundancy group

Use display redundancy group to display redundancy group information.

Syntax

display redundancy group [ group-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

group-name: Specifies a redundancy group by its name, a case-sensitive string of 1 to 15 characters. If you do not specify a redundancy group, this command displays information about all redundancy groups.

Examples

# (Centralized IRF devices.) Display information about redundancy group aaa.

<Sysname> display redundancy group aaa

Redundancy group aaa (ID 1):

Node ID Slot Priority Status Track weight

1 Slot1 100 Secondary -255

2 Slot2 99 Primary 255

Preempt delay time remained : 0 min

Preempt delay timer setting : 1 min

Remaining hold-down time : 0 sec

Hold-down timer setting : 300 sec

Manual switchover request : No

Member interfaces:

Reth1 Reth2

Member failover groups:

Node 1:

Node member Physical status

GE1/0/2 DOWN

GE1/0/4 DOWN(redundancy down)

Track info:

Track Status Reduced weight Interface

1 Negative 255 GE1/0/2(Fault)

2 Negative 255 GE1/0/4

Node 2:

Node member Physical status

GE2/0/2 UP

GE2/0/4 UP

Track info:

Track Status Reduced weight Interface

3 Positive 55 GE2/0/2

4 Positive 55 GE2/0/4

# (Distributed devices in IRF mode.) Display information about the redundancy group aaa.

<Sysname> display redundancy group aaa

Redundancy group aaa (ID 1):

Node ID Chassis Priority Status Track weight

1 Chassis1 100 Secondary -255

2 Chassis2 99 Primary 255

Preempt delay time remained : 0 min

Preempt delay timer setting : 1 min

Remaining hold-down time : 0 sec

Hold-down timer setting : 300 sec

Manual switchover request : No

Member interfaces:

Reth1 Reth2

Member failover groups:

groupa

groupabc

Node 1:

Node member Physical status

GE1/1/0/2 DOWN

GE1/1/0/4 DOWN(redundancy down)

Track info:

Track Status Reduced weight Interface

1 Negative 255 GE1/1/0/2(Fault)

2 Negative 255 GE1/1/0/4

Node 2:

Node member Physical status

GE2/1/0/2 UP

GE2/1/0/4 UP

Track info:

Track Status Reduced weight Interface

3 Positive 55 GE2/1/0/2

4 Positive 55 GE2/1/0/4

Table 4 Command output

Field | Description
Priority | Priority of the node.
Status | Node status: · Primary—The primary node. It can forward packets. · Secondary—The secondary node. When the high-priority node acts as the secondary node, all its member interfaces are shut down by the Reth module and cannot forward packets. When the low-priority node acts as the secondary node, all its member interfaces can forward packets.
Track weight | Weight of the node.
Preempt delay time remained | Remaining preemption delay time in minutes.
Preempt delay timer setting | Configured preemption delay timer in minutes.
Remaining hold-down time | Remaining hold down time in seconds.
Hold-down timer setting | Configured hold down timer in seconds.
Manual switchover request | Manual switchover request: · Yes—A request is issued. · No—No request is issued.
Member interfaces | Reth interfaces in the redundancy group.
Member failover groups | Failover groups in the redundancy group.
Node 1 | Detailed information about the redundancy group node.
Node member | Member interfaces on the redundancy group node.
Physical status | Physical status of the member interfaces on the node: · Down (redundancy down)—The interface is shut down by the Reth module. · Down—The interface is administratively up but physically down possibly because no physical link is present or the link has failed. · UP—The interface is both administratively and physically up.
Track info | Information about the track entries associated with the node.
Track | Track entry number.
Status | Track entry status.
Reduced weight | Weight decrement rate of the node.
Interface | The interface excluded from the shutdown action by the Reth module. If the interface has failed, this field displays Fault. If the interface is not present, this field displays Absent.

Redundancy group commands -- hold-down-interval

Use hold-down-interval to set the hold down timer for a redundancy group.

Use undo hold-down-interval to restore the default.

Syntax

hold-down-interval second

undo hold-down-interval

Default

The hold down timer is 1 second for a redundancy group.

Views

Redundancy group view

Predefined user roles

network-admin

mdc-admin

Parameters

second: Specifies the hold down timer in the range of 0 to 1800 seconds.

Usage guidelines

Set the hold down timer to prevent frequent switchovers. The hold down timer specifies the minimum interval between two switchovers. This timer starts when a switchover is finished. The redundancy group can perform another switchover only after the hold down timer expires.

Examples

# Set the hold down timer to 300 seconds for redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] hold-down-interval 300

Redundancy group commands -- member failover group

Use member failover group to assign a failover group to a redundancy group.

Use undo member failover group to remove a failover group from a redundancy group.

Syntax

member failover group group-name

undo member failover group group-name

Default

A redundancy group does not contain failover groups.

Views

Redundancy group view

Predefined user roles

network-admin

mdc-admin

Parameters

group-name: Specifies an existing failover group by its name, a case-sensitive string of 1 to 63 characters.

Usage guidelines

You can assign a failover group to only one redundancy group.

A redundancy group can contain a maximum of 32 failover groups.

Examples

# Assign failover group bb to redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] member failover group bb

Redundancy group commands -- member interface

Use member interface to assign a Reth interface to a redundancy group.

Use undo member interface to remove a Reth interface from a redundancy group.

Syntax

member interface reth interface-number

undo member interface reth interface-number

Default

A redundancy group does not contain Reth interfaces.

Views

Redundancy group view

Predefined user roles

network-admin

mdc-admin

Parameters

reth interface-number: Specifies an existing Reth interface by its number. The value range for the interface-number argument varies by device model.

Usage guidelines

You can assign a Reth interface to only one redundancy group.

A redundancy group can contain a maximum of 32 Reth interfaces.

Examples

# Assign Reth 1 to redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] member interface reth 1

Redundancy group commands -- node

Use node to create a redundancy group node and enter its view, or enter the view of an existing redundancy group node.

Use undo node to remove a redundancy group node.

Syntax

node node-id

undo node node-id

Default

No redundancy group nodes exist.

Views

Redundancy group view

Predefined user roles

network-admin

mdc-admin

Parameters

node-id: Specifies a redundancy group node ID in the range of 1 to 2.

Usage guidelines

You can create a maximum of two nodes for a redundancy group. One is the primary node, and the other is the secondary node.

Before you delete a redundancy group node, you must remove the binding between the node and its IRF member device.

Examples

# Create node 1 for redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] node 1

Related commands

bind chassis

bind slot

Redundancy group commands -- node-member interface

Use node-member interface to assign a physical Ethernet interface to a redundancy group node.

Use undo node-member interface to remove a physical Ethernet interface from a redundancy group node.

Syntax

node-member interface interface-type interface-number

undo node-member interface interface-type interface-number

Default

A redundancy group node does not have member interfaces.

Views

Redundancy group node view

Predefined user roles

network-admin

mdc-admin

Parameters

interface-type interface-number: Specifies a physical interface by its type and number. The interface must belong to the IRF member device that is bound to the node.

Usage guidelines

Before you assign physical Ethernet interfaces to a redundancy group node, you must use the bind chassis or bind slot command to bind the node to an IRF member device.

The physical Ethernet interfaces cannot be members of Reth interfaces.

An interface can be assigned to only one redundancy group node.

Examples

# (Centralized IRF devices.) Assign GigabitEthernet 1/0/1 to node 1 of redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] node 1

[Sysname-redundancy-group-aaa-node1]node-member interface gigabitethernet 1/0/1

# (Distributed devices in IRF mode.) Assign GigabitEthernet 1/1/0/1 to node 1 of redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] node 1

[Sysname-redundancy-group-aaa-node1]node-member interface gigabitethernet 1/1/0/1

Related commands

bind chassis

bind slot

Redundancy group commands -- preempt-delay

Use preempt-delay to set the preemption delay timer for a redundancy group.

Use undo preempt-delay to restore the default.

Syntax

preempt-delay min

undo preempt-delay

Default

The preemption delay timer is 1 minute for a redundancy group.

Views

Redundancy group view

Predefined user roles

network-admin

mdc-admin

Parameters

min: Specifies the preemption delay timer in the range of 0 to 12 minutes. If you set this timer to 0 seconds, automatic switchover is disabled.

Usage guidelines

The preemption delay timer specifies the delay before a switchover to the high-priority node occurs after the switchover is triggered. The delay allows the system to process events (such as interface state changes) required for the switchover.

Examples

# Set the preemption delay timer to 2 minutes for redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] preempt-delay 2

Redundancy group commands -- priority

Use priority to set the priority of a redundancy group node.

Use undo priority to restore the default.

Syntax

priority priority

undo priority

Default

The priority of a redundancy group node is 1.

Views

Redundancy group node view

Predefined user roles

network-admin

mdc-admin

Parameters

priority: Specifies the priority in the range of 1 to 255. The higher the value, the higher the priority.

Usage guidelines

By default, the high-priority node is the primary node, and the low-priority node is the secondary node. If both nodes have the same priority, the lower-numbered node is the primary node.

Examples

# Set the priority to 3 for node 1 of redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] node 1

[Sysname-redundancy-group-aaa-node1] priority 3

Redundancy group commands -- redundancy group

Use redundancy group to create a redundancy group and enter its view, or enter the view of an existing redundancy group.

Use undo redundancy group to remove a redundancy group.

Syntax

redundancy group group-name

undo redundancy group group-name

Default

No redundancy groups exist.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

group-name: Specifies a redundancy group name, a case-sensitive string of 1 to 15 characters.

Usage guidelines

You can create a maximum of 255 redundancy groups.

Before you delete a redundancy group, make sure all its Reth interfaces, nodes, and failover groups are removed.

Examples

# Create redundancy group aaa and enter its view.

<Sysname> system-view

[Sysname] redundancy group aaa

Redundancy group commands -- snmp-agent trap enable rddc

Use snmp-agent trap enable rddc to enable SNMP notifications for redundancy groups.

Use undo snmp-agent trap enable rddc to disable SNMP notifications for redundancy groups.

Syntax

snmp-agent trap enable rddc

undo snmp-agent trap enable rddc

Default

SNMP notifications are enabled for redundancy groups.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This command enables SNMP notifications for the following events:

· A manual switchover is performed.

· An interface goes down.

· A faulty interface is recovered.

For redundancy group event notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.

Examples

# Enable SNMP notifications for redundancy groups.

<Sysname> system-view

[Sysname] snmp-agent trap enable rddc

Redundancy group commands -- switchover request

Use switchover request to request a switchover to the low-priority node.

Syntax

switchover request

Views

Redundancy group view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Use this command to request a switchover to the low-priority node when both of the redundancy group nodes are operating correctly. This command can be used in scenarios where component replacement is required for the high-priority node.

Examples

# Request a switchover to the low-priority node for redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] switchover request

Related commands

switchover reset

Redundancy group commands -- switchover reset

Use switchover reset to request a switchover to the high-priority node.

Syntax

switchover reset

Views

Redundancy group view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Use this command to request a switchover to the high-priority node when both of the redundancy group nodes are operating correctly.

Examples

# Request a switchover to the high-priority node for redundancy group aaa.

<Sysname> system-view

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] switchover reset

Related commands

switchover request

Redundancy group commands -- track

Use track to associate a track entry with a redundancy group node.

Use undo track to remove the association between a track entry and a redundancy group node.

Syntax

track track-entry-number [ reduced weight-reduced ] [ interface interface-type interface-number ]

undo track track-entry-number

Default

A redundancy group node is not associated with track entries.

Views

Redundancy group node view

Predefined user roles

network-admin

mdc-admin

Parameters

track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.

reduced weight-reduced: Specifies the weight decrement rate in the range of 1 to 255. The default is 255.

interface interface-type interface-number: Specifies an interface by its type and number. The interface will be excluded from the shutdown action by the Reth module. If you do not specify this option, no interface is excluded from the shutdown action by the Reth module. You must specify the tracked interface for this option if the interface has one of the following roles:

· Member of the redundancy group.

· Member of a Reth interface in the redundancy group.

Usage guidelines

You can associate a maximum of 64 track entries with a redundancy group node.

As a best practice, associate a redundancy group node with an existing track entry. If the track entry does not exist, a switchover might occur.

Do not exclude a subinterface from the shutdown action if both the subinterface and its main interface have one of the following roles on the high-priority node:

· Member of the redundancy group.

· Member of a Reth interface in the redundancy group.

When the Reth module shuts down the main interface, the subinterface is also shut down. The shutdown subinterface cannot recover automatically to trigger an automatic switchover.

Examples

# (Centralized IRF devices.) Associate track entries 1 and 2 with redundancy group node 1. Exclude GigabitEthernet 1/0/1 and GigabitEthernet 2/0/1 from the shutdown action by the Reth module.

<Sysname> system-view

[Sysname] track 1 interface gigabitethernet 1/0/1

[Sysname] track 2 interface gigabitethernet 2/0/1

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] node 1

[Sysname-redundancy-group-aaa-node1] track 1 reduced 50 interface gigabitethernet 1/0/1

[Sysname-redundancy-group-aaa-node1] track 2 reduced 50 interface gigabitethernet 2/0/1

# (Distributed devices in IRF mode.) Associate track entries 1 and 2 with redundancy group node 1. Exclude GigabitEthernet 1/1/0/1 and GigabitEthernet 2/1/0/1 from the shutdown action by the Reth module.

<Sysname> system-view

[Sysname] track 1 interface gigabitethernet 1/1/0/1

[Sysname] track 2 interface gigabitethernet 2/1/0/1

[Sysname] redundancy group aaa

[Sysname-redundancy-group-aaa] node 1

[Sysname-redundancy-group-aaa-node1] track 1 reduced 50 interface gigabitethernet 1/1/0/1

[Sysname-redundancy-group-aaa-node1] track 2 reduced 50 interface gigabitethernet 2/1/0/1