13-High Availability Command Reference

HomeSupportRoutersH3C SR8800-F Router SeriesReference GuidesCommand ReferencesH3C SR8800-F Routers Command Reference-R8530Pxx-6W10113-High Availability Command Reference
08-VSRP commands
Title Size Download
08-VSRP commands 294.59 KB

VSRP commands

VSRP basic commands

backup id

Use backup id to specify a backup ID for a VSRP instance.

Use undo backup id to restore the default.

Syntax

backup id backup-id peer peer-name

undo backup id

Default

A VSRP instance has no backup ID.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

backup-id: Specifies a VSRP instance by its backup ID in the range of 1 to 2048.

peer-name: Specifies a VSRP group by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

A VSRP instance can be associated with only one VSRP group. The backup ID uniquely identifies a VSRP instance in a VSRP group.

You must specify the same backup ID for a VSRP instance on both devices in a VSRP group.

When you specify a backup ID for a VSRP instance, make sure the following conditions are met:

·     The associated VSRP group already exists.

·     The backup ID is unique in the VSRP group.

To specify a new backup ID for a VSRP instance, first execute the undo form of the command to remove the existing backup ID setting.

Examples

# Specify the backup ID of VSRP instance aaa as 5 in VSRP group pname.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] backup id 5 peer pname

backup mode

Use backup mode to set the backup mode for a VSRP instance.

Use undo backup mode to restore the default.

Syntax

backup mode { hot [ dual-active ] | warm }

undo backup mode

Default

A VSRP instance operates in hot backup mode.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

hot: Specifies hot backup mode.

dual-active: Specifies dual-active hot backup mode. To specify single-active hot backup mode, do not specify this keyword together with the hot keyword. The dual-active keyword is supported only in the VSRP and S-Trunk collaboration network. Do not configure this keyword in other networks.

warm: Specifies warm backup mode.

Usage guidelines

In hot backup mode, the backup device issues backup information to the data plane immediately upon receiving the information from the master. This allows the VSRP instance to perform a fast master and backup switchover to enable the backup to forward packets when the master fails. VSRP provides the following hot backup modes:

·     Dual-active hot backup mode—Both the master and backup devices are active to load share traffic.

·     Single-active hot backup mode—The master device is active to process service traffic, and the backup device takes over when the master device fails.

In warm backup mode, the backup device does not issue received backup information to the data plane immediately. When the master fails and a switchover occurs, the backup begins to set backup information to the data plane. As a result, the switchover takes longer in warm backup mode than in hot backup mode.

Examples

# Set VSRP instance aaa to operate in warm backup mode.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] backup mode warm

backup route-advertise

Use backup route-advertise to enable route advertisement for the backup.

Use undo backup route-advertise to restore the default.

Syntax

backup route-advertise [ master-cost master-cost backup-cost backup-cost ]

undo backup route-advertise

Default

Route advertisement is enabled only for the master.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

master-cost master-cost: Specifies the route cost for the master, in the range of 0 to 4261412863. The default route cost is 10. The master's route cost must be lower than the backup's route cost.

backup-cost backup-cost: Specifies the route cost for the backup, in the range of 1 to 4261412864. The default route cost is 20.

Usage guidelines

An IPoE or PPPoE network requires an address pool to be created on the master and backup of a VSRP instance and route advertisement for subnets of the address pool. By default, only the master advertises the subnet routes, and network devices reach terminal users only through the master. If the master fails or is disconnected, communication with the terminal users is interrupted before the backup takes over.

This command enables the backup to advertise subnet routes for the address pool to reduce the service outage. After you configure this command, the network devices have two routes to reach a terminal user, and the route advertised by the master has a smaller route cost. When both the master and the backup are available, the network devices access terminal users through the master. When the master becomes unavailable, the network devices look up the routing table and use the routes advertised by the backup to reach terminal users.

With route advertisement enabled, the backup can advertise subnet routes for both IPv4 and IPv6 address pools, and subnet routes for PPP IPv6 address pools.

Examples

# Enable route advertisement for the backup of VSRP instance aaa. Set the route costs for the master and the back to 20 and 30, respectively.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] backup route-advertise master-cost 20 backup-cost 30

bind s-trunk

Use bind s-trunk to bind a VSRP instance to a smart trunk member interface.

Use undo bind s-trunk to restore the default.

Syntax

bind s-trunk s-trunk-id interface route-aggregation interface-number

undo bind s-trunk

Default

A VSRP instance is not bound to any smart trunk member interface.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

s-trunk-id: Specifies a smart trunk ID. The value range for this argument is 1 to 65535.

interface route-aggregation interface-number: Specifies a Layer 3 aggregate interface in the smart trunk by its interface number.

Usage guidelines

A VSRP instance is bound to a smart trunk to determine the device role (master or backup) in the VSRP instance. You can bind a VSRP instance to only one smart trunk.

A VSRP instance is in initialized state in one of the following conditions:

·     The Layer 3 aggregate interface bound to the VSRP instance is not in the specified smart trunk.

·     The specified smart trunk does not exist.

If you execute the following commands multiple times for a VSRP instance, the most recent configuration takes effect:

·     bind interface

·     bind s-trunk

·     bind vrrp ipv6 vrid

·     bind vrrp vrid

Examples

# Bind VSRP instance aaa to Route-Aggregation 1 in smart trunk 1.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] bind s-trunk 1 interface route-aggregation 1

Related commands

bind interface

bind vrrp ipv6 vrid

bind vrrp vrid

bind vrrp ipv6 vrid

Use bind vrrp ipv6 vrid to bind a VSRP instance to an IPv6 VRRP group.

Use undo bind vrrp ipv6 to restore the default.

Syntax

bind vrrp ipv6 vrid virtual-router-id interface interface-type interface-number

undo bind vrrp ipv6

Default

A VSRP instance is not bound to any IPv6 VRRP group.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

virtual-router-id: Specifies an IPv6 VRRP group by its virtual router ID in the range of 1 to 255.

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

Usage guidelines

A VSRP instance is bound to an IPv6 VRRP group to determine the device role (master or backup) in a VSRP group.

You can bind a VSRP instance to only one IPv6 VRRP group. The IPv6 VRRP group can be on any interface.

If you execute the bind vrrp vrid and bind vrrp ipv6 vrid commands multiple times for a VSRP instance, the most recent configuration takes effect.

Examples

# Bind VSRP instance aaa to IPv6 VRRP group 2 on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] bind vrrp ipv6 vrid 2 interface ten-gigabitethernet 3/1/1

Related commands

bind vrrp vrid

bind vrrp vrid

Use bind vrrp vrid to bind a VSRP instance to an IPv4 VRRP group.

Use undo bind vrrp to restore the default.

Syntax

bind vrrp vrid virtual-router-id interface interface-type interface-number

undo bind vrrp

Default

A VSRP instance is not bound to any IPv4 VRRP group.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

virtual-router-id: Specifies an IPv4 VRRP group by its virtual router ID in the range of 1 to 255.

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

Usage guidelines

A VSRP instance is bound to an IPv4 VRRP group to determine the device role (master or backup) in a VSRP group.

You can bind a VSRP instance to only one IPv4 VRRP group. The IPv4 VRRP group can be on any interface.

If you execute the bind vrrp vrid and bind vrrp ipv6 vrid commands multiple times for a VSRP instance, the most recent configuration takes effect.

Examples

# Bind VSRP instance aaa to IPv4 VRRP group 2 on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] bind vrrp vrid 2 interface ten-gigabitethernet 3/1/1

Related commands

bind vrrp vrid

display vsrp instance

Use display vsrp instance to display VSRP instance information.

Syntax

display vsrp instance [ instance-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VSRP instance, this command displays information about all VSRP instances.

Examples

# Display information about VSRP instance aaa.

<Sysname> display vsrp instance aaa

VSRP instance name: aaa

 VSRP peer name: pname1

 Backup ID: 10

 Bound VRID: VRRP VRID 1   Interface: Ten-GigabitEthernet3/1/1

 Instance status: Master

 Local status: Master

 Peer status: Backup

 Backup mode: Warm

 Traffic backup interval: 10(minutes)

 Traffic backup threshold: 50(MB)

 NAS IP: 10.0.0.1

 NAS port: Ten-GigabitEthernet3/1/2

 NAS ID: h3c

 Route advertisement: Master and backup

 Master cost: 20

 Backup cost: 30

# Display information about all VSRP instances.

<Sysname> display vsrp instance

VSRP instance name: aaa

 VSRP peer name: pname1

 Backup ID: 10

 Bound VRID: VRRP VRID 1   Interface: Ten-GigabitEthernet3/1/1

 Instance status : Master

 Local status: Master

 Peer status: Backup

 Backup mode: Warm

 Traffic backup interval: 10(minutes)

 Traffic backup threshold: 50(MB)

 NAS IP: 10.0.0.1

 NAS port: Ten-GigabitEthernet3/1/2

 NAS ID: h3c

 Route advertisement: Master only

VSRP instance name: bbb

 VSRP peer name: pname2

 Backup ID: 10

 Bound S-Trunk ID: 1   Interface: Router-Aggregation1

 Instance status : Master

 Local status: Master

 Peer status: Backup

 Backup mode: Warm

 Traffic backup interval: 5(minutes)

 Traffic backup threshold: 100(MB)

 NAS IP: 10.0.0.2

 NAS port: Ten-GigabitEthernet3/1/4

 NAS ID: h3c

 Route advertisement: Master and backup

 Master cost: 20

 Backup cost: 30

Table 1 Command output

Field

Description

VSRP peer name

Name of a VSRP group associated with the VSRP instance.

Bound VRID   Interface:

Number of the VRRP group bound to the VSRP instance and the interface that hosts the VSRP instance. This field is displayed if the VSRP instance is bound to a VRRP group.

Bound S-Trunk ID:   Interface:

Smart trunk ID and smart trunk member interface bound to the VSRP instance. This field is displayed if the VSRP instance is bound to a smart trunk member interface.

Instance status

VSRP instance state:

·     Master—The device acts as the master in the VSRP instance.

·     Backup—The device acts as the backup in the VSRP instance.

·     Down—The device is not running in the VSRP instance.

Local status

Local device state:

·     Master—The local device is acting as the master.

·     Backup—The local device is acting as the backup.

·     Init—The local device is in initialized state.

·     Down—The state of the local device is unknown.

Peer status

Peer state:

·     Master—The peer is acting as the master.

·     Backup—The peer is acting as the backup.

·     Init—The peer is in initialized state.

·     Down—The state of the peer is unknown.

Backup mode

VSRP instance backup mode:

·     Dual-active—Dual-active hot backup mode.

·     Hot—Single-active hot backup mode.

·     Warm—Warm backup mode.

Traffic backup threshold

Traffic threshold that triggers a traffic backup.

NAS IP

Logical NAS IP address.

NAS port

Logical NAS port.

NAS ID

Logical host name.

Route advertisement

Route advertisement state:

·     Master and backup—Both the master and the backup advertise subnet routes for address pools.

·     Master only—Only the master advertises subnet routes for address pools.

Master cost

Route cost for the master. This field is displayed only when the value of the Route advertisement field is Master and backup.

Backup cost

Route cost for the backup. This field is displayed only when the value of the Route advertisement field is Master and backup.

 

display vsrp peer

Use display vsrp peer to display VSRP group information.

Syntax

display vsrp peer [ peer-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Examples

# Display information about VSRP group pname.

<Sysname> display vsrp peer pname

VSRP peer name: pname

 TCP status: Connected

 Peer IP: 11.0.0.3

 Local IP: 10.0.0.3

 Port: 6000

 Track ID: 5

 Track status: Positive

# Display information about all VSRP groups.

<Sysname> display vsrp peer

VSRP peer name: pname1

 TCP status: Connected

 Peer IP: 11.0.0.3

 Local IP: 10.0.0.3

 Port: 6000

 Track ID: 5

 Track status: Positive

VSRP peer name: pname2

 TCP status: Disconnected

 Peer IP: 10.0.0.2

 Local IP: 11.0.0.2

 Port: 5000

 Track ID: 5

 Track status: Negative

Table 2 Command output

Field

Description

VSRP peer name

Name of a VSRP group.

TCP status

TCP control channel state: Connected or Disconnected.

Peer IP

Peer IP address for VSRP channels.

Local IP

Local IP address for VSRP channels.

Port

Port number for the TCP control channel.

Track ID

ID of the track entry associated with the VSRP group.

Track status

Track entry state:

·     Positive.

·     NotReady.

·     Negative.

 

ipv6 virtual-address

Use ipv6 virtual-address to specify a virtual IPv6 address for an interface that is associated with a VSRP instance.

Use undo ipv6 virtual-address to restore the default.

Syntax

ipv6 virtual-address ipv6-address vsrp vsrp-instance

undo ipv6 virtual-address

Default

No virtual IPv6 address is configured.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Layer 3 FlexE interface view

VLAN interface view

Predefined user roles

network-admin

Parameters

ipv6-address: Specifies a virtual IPv6 address. The virtual IPv6 address must be a link local address that can be used as the gateway address by hosts in a LAN.

vsrp vsrp-instance: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

Use this command when you enable VSRP for IPv6 IPoE or DHCPv6 services on an interface. For VSRP to operate correctly, specify the same VSRP instance in this command and in the ipv6 subscriber vsrp-instance or the ipv6 dhcp vsrp-instance command. If different VSRP instances are specified, the hosts in the LAN cannot access the Internet after a master and backup switchover.

For the original link local address of the device to take effect, do not use this command when VSRP is disabled for IPv6 IPoE or DHCPv6 on the interface.

To enable VSRP to operate correctly, do not use this command on the same interface where a VRRP group is configured.

Examples

# Specify virtual IPv6 address fe80::10 for Ten-GigabitEthernet 3/1/1 that is associated with VSRP instance aaa.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] ipv6 virtual-address fe80::10 vsrp aaa

nas

Use nas to configure NAS parameters.

Use undo nas to remove the NAS parameters.

Syntax

nas { id host-name | ip ip-address | port interface-type interface-number }

undo nas [ id | ip | port ]

Default

No NAS parameters are configured.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

id host-name: Specifies a logical host name, a case-insensitive string of 1 to 127 characters.

ip ip-address: Specifies a logical unicast IP address. The IP address cannot be all zeros or a loopback address.

port interface-type interface-number: Specifies a logical interface by its type and number. It must be a Layer 3 Ethernet interface. The logical interface can be an interface that does not belong to the device. Make sure the logical interface number contains three segments in interface-type A/B/C format.

Usage guidelines

This command specifies NAS parameters for outgoing packets. This command enables devices in a VSRP group to share parameters when the devices have the following settings:

·     The same NAS-IP-address, NAS-Port, and host name in packets sent to the RADIUS server.

·     The same Option 82 in packets sent to the DHCP server.

In this way, the VSRP group is not required to be authenticated again after a master and backup switchover.

Examples

# Specify the logical IP address as 2.2.2.2.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] nas ip 2.2.2.2

# Specify the logical interface as Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] nas port ten-gigabitethernet 3/1/1

# Specify the logical host name as bbb.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] nas id bbb

peer

Use peer to configure the TCP parameters for establishing VSRP channels to the peer.

Use undo peer to delete the VSRP channels to the peer.

Syntax

peer [ ipv6 ] peer-ip-address local local-ip-address [ port port-id ]

undo peer

Default

No VSRP channels are established to the peer.

Views

VSRP peer view

Predefined user roles

network-admin

Parameters

ipv6: Specifies IPv6 addresses. To specify IPv4 addresses, do not specify this keyword.

peer-ip-address: Specifies the IPv4 address of the peer.

local local-ip-address: Specifies the IPv4 address of the local device.

port port-id: Specifies the TCP port number for establishing the control channel. The value range is 1024 to 65535 and the default is 60032. The specified port number cannot be one that is in use. To view the TCP port numbers in use, execute the display [ ipv6 ] tcp command.

Usage guidelines

You must specify different unicast IP addresses for the peer device and the local device in a VSRP group. The IP addresses cannot be all zeros or loopback addresses.

If you have multiple VSRP groups, make sure their IP address pairs are unique.

You cannot configure both IPv4 and IPv6 VSRP channels for the same VSRP peer. To change the TCP parameters for VSRP channel establishment, first execute the undo form of the command to remove the existing VSRP channels.

Examples

# Specify channel establishment parameters for VSRP group pname. Set the local IPv4 address to 11.0.0.2, the peer IPv4 address to 10.0.0.1, and the TCP port number for the control channel to 7000.

<Sysname> system-view

[Sysname] vsrp peer pname

[Sysname-vsrp-peer-pname] peer 10.0.0.1 local 11.0.0.2 port 7000

snmp-agent trap enable vsrp

Use snmp-agent trap enable vsrp to enable SNMP notifications for VSRP.

Use undo snmp-agent trap enable vsrp to disable SNMP notifications for VSRP.

Syntax

snmp-agent trap enable vsrp

undo snmp-agent trap enable vsrp

Default

SNMP notifications are enabled for VSRP.

Views

System view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

If SNMP notifications are enabled for VSRP, a notification is sent to the SNMP module after an important event occurs, such as VSRP connection setup, abnormal VSRP connection, or VSRP instance status switchover.

Operating mechanism

For SNMP notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see Network Management and Monitoring Configuration Guide.

Examples

# Enable SNMP notifications for VSRP.

<Sysname> system-view

[Sysname] snmp-agent trap enable vsrp

Related commands

display snmp-agent trap-list (Network Management and Monitoring Command Reference)

track

Use track to associate a VSRP group with a track entry.

Use undo track to restore the default.

Syntax

track track-entry-number

undo track

Default

A VSRP group is not associated with any track entry.

Views

VSRP peer view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

By default, a VSRP group can detect the state of the failover link based only on the state of the TCP control channel.

You can associate a VSRP group with a track entry to identify the state of the failover link.

·     When the track entry is in Positive or NotReady state, a device in the VSRP group attempts to establish a TCP control channel to the peer.

·     When the track entry changes to Negative state, the device terminates the TCP control channel.

A VSRP group takes effect only when a TCP control channel is established.

For more information about track entries, see High Availability Configuration Guide.

Examples

# Associate VSRP group pname with track entry 10.

<Sysname> system-view

[Sysname] vsrp peer pname

[Sysname-vsrp-peer-pname] track 10

traffic backup

Use traffic backup to set a traffic backup interval or a traffic threshold that triggers a traffic backup.

Use undo traffic backup to remove the specified traffic backup interval or traffic threshold settings.

Syntax

traffic backup { interval interval-value | threshold threshold-value } *

undo traffic backup [ interval | threshold ]

Default

A VSRP instance backs up traffic at an interval of 10 minutes or when the traffic reaches 50 MB.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

interval interval-value: Specifies a traffic backup interval in the range of 0 to 1440 minutes.

threshold threshold-value: Specifies a traffic threshold that triggers a traffic backup. The value range for the threshold-value argument is 0 to 100000 MB.

Usage guidelines

A VSRP instance backs up service data at the specified interval or when the specified traffic threshold is reached.

If traffic is not required to be backed up, set both the interval-value argument and the threshold-value argument to 0.

Examples

# Configure VSRP instance aaa to back up traffic every 50 minutes.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] traffic backup interval 50

# Configure VSRP instance aaa to back up traffic when the traffic reaches 200 MB.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] traffic backup threshold 200

# Set the traffic backup interval and the traffic threshold to the default value for VSRP instance aaa.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa] undo traffic backup

vsrp instance (system view)

Use vsrp instance to create a VSRP instance and enter its view, or enter the view of an existing VSRP instance.

Use undo vsrp instance to remove a VSRP instance.

Syntax

vsrp instance instance-name

undo vsrp instance instance-name

Default

No VSRP instances exist.

Views

System view

Predefined user roles

network-admin

Parameters

instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

A VSRP instance is associated with a service module. To enable a VSRP instance to function, you must configure the following items for the VSRP instance:

·     A VSRP group.

·     A bound VRRP group.

·     The backup mode.

·     The traffic backup interval or traffic threshold.

Examples

# Create a VSRP instance named aaa, and enter VSRP instance view.

<Sysname> system-view

[Sysname] vsrp instance aaa

[Sysname-vsrp-instance-aaa]

vsrp log enable

Use vsrp log enable to enable VSRP logging.

Use undo vsrp log enable to disable VSRP logging.

Syntax

vsrp log enable

undo vsrp log enable

Default

VSRP logging is disabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

If logging is enabled for VSRP, a log messages generated after an important event occurs, such as VSRP connection setup, abnormal VSRP connection, or VSRP instance status switchover.

Operating mechanism

The VSRP logging feature sends log messages to the information center. The information center can then output log messages from different source modules to different destinations. For more information about information center, see Network Management and Monitoring Configuration Guide.

Examples

# Enable VSRP logging.

<Sysname> system-view

[Sysname] vsrp log enable

Related commands

info-center enable (Network Management and Monitoring Command Reference)

vsrp peer

Use vsrp peer to create a VSRP group and enter VSRP peer view, or enter the VSRP peer view of an existing VSRP group.

Use undo vsrp peer to remove a VSRP group.

Syntax

vsrp peer peer-name

undo vsrp peer peer-name

Default

No VSRP groups exist.

Views

System view

Predefined user roles

network-admin

Parameters

peer-name: Specifies a VSRP group by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

You can create a maximum of 64 VSRP groups on the device.

If a VSRP instance exists on a VSRP group, you must use the undo backup id command to remove that VSRP instance before you can remove the VSRP group.

Examples

# Create a VSRP group named pname and enter VSRP peer view.

<Sysname> system-view

[Sysname] vsrp peer pname

[Sysname-vsrp-peer-pname]

Protection tunnel commands

protect lsp-tunnel for-all-instance

Use protect lsp-tunnel for-all-instance to specify the destination address of LSP protection tunnels.

Use undo protect lsp-tunnel for-all-instance to delete the destination address of LSP protection tunnels.

Syntax

protect lsp-tunnel for-all-instance peer-ip ip-address [ tunnel-policy policy-name ]

undo protect lsp-tunnel for-all-instance peer-ip

Default

No LSP protection tunnel destination address is configured.

Views

VSRP peer view

Predefined user roles

network-admin

Parameters

peer-ip ip-address: Specifies a tunnel destination address.

tunnel-policy tunnel-policy-name: Specifies a tunnel policy name, a case-sensitive string of 1 to 126 characters. If you do not specify a tunnel policy, the default tunnel policy is applied to the LSP protection tunnels.

Usage guidelines

To ensure service continuity when the access-side link of the master fails, the master forwards the traffic sent from the external network to users towards the backup over an LSP protection tunnel. The backup then forwards the traffic to the destination.

The master and the backup set up LSP protection tunnels for the public instance and each VPN instance. The LSP protection tunnel for the public instance is set up after you finish LSP protection tunnel configuration, while the LSP protection tunnel for a VPN instance is set up on demand.

Examples

# Specify the destination address of LSP protection tunnels as 1.1.1.1 in VSRP peer view of VSRP group 1.

<Sysname> system-view

[Sysname] vsrp peer 1

[Sysname-vsrp-peer-1] protect lsp-tunnel for-all-instance peer-ip 1.1.1.1

protect srv6-tunnel for-all-instance

Use protect srv6-tunnel for-all-instance to specify a locator for SRv6 protection tunnels.

Use undo protect srv6-tunnel for-all-instance to restore the default.

Syntax

protect srv6-tunnel for-all-instance locator locator-name

undo protect srv6-tunnel for-all-instance locator

Default

No SRv6 protection tunnels exist.

Views

VSRP peer view

Predefined user roles

network-admin

Parameters

locator locator-name: Specifies a locator by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

To ensure service continuity when the access-side link of the master fails, the master forwards the traffic sent from the external network to users towards the backup over an SRv6 protection tunnel. The backup then forwards the traffic to the destination.

The master and the backup set up SRv6 protection tunnels for the public instance and each VPN instance. The SRv6 protection tunnel for the public instance is set up after you finish SRv6 protection tunnel configuration, while the SRv6 protection tunnel for a VPN instance is set up on demand.

Examples

# Specify the locator for SRv6 protection tunnels as a in VSRP peer view of VSRP group 1.

<Sysname> system-view

[Sysname] vsrp peer 1

[Sysname-vsrp-peer-1] protect srv6-tunnel for-all-instance locator a

Related commands

locator (Segment Routing Command Reference)

BRAS VSRP commands (IPoE/PPPoE)

bras vsrp-instance

Use bras vsrp-instance to associate an BRAS service-enabled interface with a VSRP instance.

Use undo bras vsrp-instance to restore the default.

Syntax

bras vsrp-instance vsrp-instance-name

undo bras vsrp-instance

Default

An BRAS service-enabled interface is not associated with a VSRP instance.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

This command applies only to IPoE and PPPoE.

After you execute this command, the associated VSRP instance backs up BRAS user session information in real time through the data channel between the master and the backup.

You can specify a nonexistent VSRP instance in this command, but this command takes effect only after the specified VSRP instance is created.

An interface can be associated with only one VSRP instance. You can associate subinterfaces of an interface with the same VSRP instance.

To associate an interface with a VSRP instance that has been associated with another interface, remove the original association of the VSRP instance first.

On an interface, executing this command or its undo form causes all online IPoE and PPPoE clients to go offline.

To modify the VSRP instance association of an interface, first use the undo bras vsrp-instance command to remove the existing VSRP instance association.

Examples

# Associate BRAS service-enabled interface Ten-GigabitEthernet 3/1/1 with VSRP instance vsrp1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] bras vsrp-instance vsrp1

Related commands

bras vsrp-port

bras vsrp-port

Use bras vsrp-port to specify a TCP port number for VSRP to establish data channels for BRAS services.

Use undo bras vsrp-port to restore the default.

Syntax

bras vsrp-port port-number

undo bras vsrp-port

Default

TCP port number 60045 is used to establish the data channels for BRAS user session backup.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535. The TCP port cannot be used by other services or be a well-known port.

Usage guidelines

This command applies only to IPoE and PPPoE.

To back up the BRAS user sessions on an interface, the master must establish a TCP data channel with the backup. You can use this command to change the TCP port number for establishing the data channel.

Examples

# Specify TCP port 20000 for VSRP to establish data channels for BRAS services.

<Sysname> system-view

[Sysname] bras vsrp-port 20000

Related commands

bras vsrp-instance

L2TP VSRP commands

display l2tp tunnel vsrp

Use display l2tp tunnel vsrp to display information about the L2TP tunnels backed up by VSRP instances.

Syntax

display l2tp tunnel vsrp [ vsrp-instance-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VSRP instance, this command displays L2TP tunnel information backed up by all VSRP instances.

Examples

# Display information about the L2TP tunnels backed up by VSRP instance abc.

<Sysname> display l2tp tunnel vsrp abc

VSRP instance state: Master

Total synchronized L2TP tunnels: 1

LocalTID RemoteTID State        Sessions RemoteAddress   RemotePort RemoteName

15418    47605     Established  1        1.1.2.2         1701       LNS

Table 3 Command output

Field

Description

VSRP instance name

Name of the VSRP instance that backs up the L2TP tunnel.

VSRP instance state

VSRP instance state:

·     Master—The device acts as the master in the VSRP instance. The command displays L2TP tunnel information synchronized to the backup.

·     Backup—The device acts as the backup in the VSRP instance. The command displays L2TP tunnel information synchronized from the master.

·     Down—The device is not running. The device has no L2TP tunnel information synchronized by the VSRP instance. This field displays Down in either of the following situations:

¡     The associated VRRP group is in Initialize state.

¡     The VSRP instance does not exist or is not correctly configured on the device.

Total synchronized L2TP tunnels

Number of synchronized L2TP tunnels.

LocalTID

Local tunnel ID.

RemoteTID

Remote tunnel ID.

State

Tunnel state:

·     Idle.

·     Wait-reply—The tunnel is waiting for SCCRP messages.

·     Established.

·     Stopping—The tunnel is being disconnected.

Sessions

Number of sessions on the tunnel.

RemoteAddress

IP address of the peer.

RemotePort

UDP port number of the peer.

RemoteName

Name of the tunnel peer.

 

Related commands

reset l2tp tunnel (BRAS Service Command Reference)

l2tp tunnel-id

Use l2tp tunnel-id to specify an L2TP tunnel ID range.

Use undo l2tp tunnel-id to restore the default.

Syntax

l2tp tunnel-id low-id high-id

undo l2tp tunnel-id

Default

The L2TP tunnel ID is in the range of 1 to 65535.

Views

System view

Predefined user roles

network-admin

Parameters

low-id: Specifies the lower limit of the L2TP tunnel ID. The value range is 1 to 65535.

high-id: Specifies the upper limit of the L2TP tunnel ID. The value range is 1 to 65535. The upper limit must be greater than or equal to the lower limit.

Usage guidelines

To avoid tunnel ID conflicts after a master/backup switchover, you must specify different L2TP tunnel ID ranges on the peer LACs in the following scenario:

You assign the peer LACs to two VSRP instances with their roles exchanged for load sharing purposes. For example, use LAC 1 as the master and LAC 2 as the backup in VSRP instance 1. Use LAC 2 as the master and LAC 1 as the backup in VSRP instance 2.

You cannot change the L2TP tunnel ID range for an LAC when it has an L2TP tunnel.

Examples

# Specify a L2TP tunnel ID range from 20 to 100 on the LAC.

<Sysname> system-view

[Sysname] l2tp tunnel-id 20 100

l2tp vsrp-port

Use l2tp vsrp-port to specify a TCP port number for VSRP to establish data channels for L2TP services.

Use undo l2tp vsrp-port to restore the default.

Syntax

l2tp vsrp-port port-number

undo l2tp vsrp-port

Default

TCP port 60036 is used to establish the data channels for L2TP service backup.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535. The TCP port cannot be used by other services or be a well-known port.

Usage guidelines

To back up a L2TP service, the master must establish a TCP data channel with the backup. You can use this command to change the TCP port number for establishing the data channel.

You must specify the same TCP port number on the master and the backup in a VSRP instance. Otherwise, the data channel cannot be established.

Examples

# Specify TCP port 20000 for VSRP to establish data channels for L2TP service backup.

<Sysname> system-view

[Sysname] l2tp vsrp-port 20000

tunnel vsrp source-ip

Use tunnel vsrp source-ip to specify a source address for an L2TP tunnel when VSRP is enabled for L2TP. This address is used as the source IP address of tunneled packets.

Use undo tunnel vsrp source-ip to restore the default.

Syntax

tunnel vsrp source-ip ip-address

undo tunnel vsrp source-ip

Default

The L2TP tunnel source address is the IP address of the tunnel interface.

Views

L2TP group view

Predefined user roles

network-admin

Parameters

ip-address: Specifies a source address for the L2TP tunnel when VSRP is enabled for L2TP. The tunnel source address can only be the loopback interface address with a 32-bit mask or an IP address that does not exist on the network.

Usage guidelines

You must use this command to specify the same L2TP tunnel source address on the master and backup LACs. The master LAC automatically generates a static route to the source address with the loopback interface as the output interface.

After a master and backup switchover, the original master deletes the static route and uses a dynamic routing protocol to advertise the route deletion. Meanwhile, the new master generates a static route to the tunnel source address and uses a dynamic routing protocol to advertise the route. In this way, the traffic from the LNS can be automatically switched to the new master LAC. The LNS considers that the original L2TP tunnel remains established.

When you specify the source address for an L2TP tunnel, follow these restrictions and guidelines:

·     As a best practice, specify different L2TP tunnel source addresses for L2TP tunnels in different L2TP groups.

·     To specify an L2TP tunnel source address, you must first associate the L2TP group with a VSRP instance.

·     You cannot change or remove the specified tunnel source address for the existing L2TP tunnel in an L2TP group.

·     When you enable VSRP for L2TP services, the tunnel source address specified by the tunnel vsrp source-ip command rather than that specified by the source-ip command takes effect. If you configure the source-ip command but not the tunnel vsrp source-ip command, VSRP for L2TP cannot operate correctly.

Examples

# Specify the source address for the L2TP tunnel in L2TP group 1 as 2.2.2.2.

<Sysname> system-view

[Sysname] l2tp-group 1 mode lac

[Sysname-l2tp1] tunnel vsrp source-ip 2.2.2.2

Related commands

source-ip (BRAS Service Command Reference)

vsrp-instance (L2TP group view)

Use vsrp-instance to associate an L2TP group with a VSRP instance.

Use undo vsrp-instance to remove the VSRP instance association.

Syntax

vsrp-instance vsrp-instance-name

undo vsrp-instance

Default

An L2TP group is not associated with a VSRP instance.

Views

L2TP group view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

To back up L2TP services, you must associate an L2TP group with a VSRP instance. Then, the master LAC backs up information about the L2TP group to the backup LAC in real time over the VSRP data channel. In some situations, such as a device reboot, the backup LAC also requests L2TP group information from the master LAC over the VSRP data channel.

You must associate the peer L2TP groups on the master and backup LACs with the same VSRP instance.

Using this command removes the existing L2TP tunnel in the L2TP group.

You cannot change or remove the association between an L2TP group and a VSRP instance when an L2TP tunnel exists in the L2TP group.

Examples

# Associate L2TP group 1 in LAC mode with VSRP instance abc.

<Sysname> system-view

[Sysname] l2tp-group 1 mode lac

[Sysname-l2tp1] vsrp-instance abc

ARP VSRP commands

arp vsrp-instance

Use arp vsrp-instance to associate ARP with a VSRP instance on an interface.

Use undo arp vsrp-instance to restore the default.

Syntax

arp vsrp-instance vsrp-instance-name [ apply sub-interface ]

undo arp vsrp-instance

Default

ARP is not associated with any VSRP instance on an interface.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Layer 3 FlexE interface view

L3VE interface view

L3VE subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

apply sub-interface: Associates the specified VSRP instance with ARP on all subinterfaces that do not have a VSRP instance association. If you do not specify the apply sub-interface keyword, this command does not associate the VSRP instance with the subinterfaces of the specified interface. This keyword is supported only by main interfaces.

Usage guidelines

This command enables the master to back up the ARP entries of the interface to the backup in real time through the data channel of VSRP. When the master fails or its links fail, the backup can take over to forward traffic immediately without traffic loss.

On an interface, the time taken to create or remove a VSRP instance association for ARP increases with the number of entries to synchronize. You cannot execute this command again before the creation or removal operation is complete.

To modify the VSRP instance association for ARP on an interface, first remove the existing association.

Examples

# Associate ARP with VSRP instance vsrp 1 on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] arp vsrp-instance vsrp1

Related commands

arp vsrp-port

arp vsrp-port

Use arp vsrp-port to specify a TCP port number for VSRP to establish data channels for ARP service backup.

Use undo arp vsrp-port to restore the default.

Syntax

arp vsrp-port port-number

undo arp vsrp-port

Default

TCP port 60043 is used to establish data channels for ARP service backup.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535. The specified port number cannot be used by other services or be a well-known port.

Usage guidelines

To back up ARP entries, the master must establish a TCP data channel with the backup. You can use this command to change the TCP port number for establishing the data channel.

Examples

# Specify TCP port 20000 for VSRP to establish data channels for ARP service backup.

<Sysname> system-view

[Sysname] arp vsrp-port 20000

Related commands

arp vsrp-instance

ND VSRP commands

ipv6 nd vsrp-instance

Use ipv6 nd vsrp-instance to associate ND with a VSRP instance on an interface.

Use undo ipv6 nd vsrp-instance to restore the default.

Syntax

ipv6 nd vsrp-instance vsrp-instance-name [ apply sub-interface ]

undo ipv6 nd vsrp-instance

Default

ND is not associated with any VSRP instance on an interface.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Layer 3 FlexE interface view

L3VE interface view

L3VE subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

apply sub-interface: Associates the specified VSRP instance with ND on all subinterfaces that do not have a VSRP instance association. If you do not specify the apply sub-interface keyword, this command does not associate the VSRP instance with the subinterfaces of the specified interface. This keyword is supported only by main interfaces.

Usage guidelines

This command enables the master to back up the ND entries of the interface to the backup in real time through the data channel of VSRP. When the master fails or its links fail, the backup can take over to forward traffic immediately without traffic loss.

On an interface, the time taken to create or remove a VSRP instance association for ND increases with the number of entries to synchronize. You cannot execute this command again before the creation or removal operation is complete.

To modify the VSRP instance association for ND on an interface, first remove the existing association.

Examples

# Associate ND with VSRP instance vsrp 1 on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] ipv6 nd vsrp-instance vsrp1

Related commands

ipv6 nd vsrp-port

ipv6 nd vsrp-port

Use ipv6 nd vsrp-port to specify a TCP port number for VSRP to establish data channels for ND service backup.

Use undo ipv6 nd vsrp-port to restore the default.

Syntax

ipv6 nd vsrp-port port-number

undo ipv6 nd vsrp-port

Default

TCP port 60044 is used to establish data channels for ND service backup.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535. The specified port number cannot be used by other services or be a well-known port.

Usage guidelines

To back up ND entries, the master must establish a TCP data channel with the backup. You can use this command to change the TCP port number for establishing the data channel.

Examples

# Specify TCP port 20000 for VSRP to establish data channels for ND service backup.

<Sysname> system-view

[Sysname] ipv6 nd vsrp-port 20000

Related commands

ipv6 nd vsrp-instance

DHCP VSRP commands

dhcp relay vsrp-instance

Use dhcp relay vsrp-instance to associate a client-side interface on a DHCPv4 relay agent with a VSRP instance.

Use undo dhcp relay vsrp-instance to remove the VSRP instance association.

Syntax

dhcp relay vsrp-instance vsrp-instance-name

undo dhcp relay vsrp-instance

Default

The client-side interfaces on the DHCPv4 relay agent are not associated with VSRP instances.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

You can specify a nonexistent VSRP instance for this command, but this command takes effect only after the VSRP instance is created.

You can associate an interface or subinterface with only one VSRP instance.

You can associate a VSRP instance with one interface or multiple subinterfaces on the same interface.

If a DHCP relay agent is configured, and PPPoE users and IPoE users share an address pool, you can associate a VSRP instance with one of the following interface combinations:

·     A VT interface and a non-VT interface.

·     A VT interface and multiple subinterfaces of a non-VT interface.

Examples

# Associate Ten-GigabitEthernet 3/1/1 with VSRP instance a.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] dhcp relay vsrp-instance a

dhcp vsrp port

Use dhcp vsrp port to specify a TCP port number for VSRP to establish data channels for DHCPv4 server or relay agent service backup.

Use undo dhcp vsrp port to restore the default.

Syntax

dhcp vsrp port port-number

undo dhcp vsrp port

Default

TCP port 60037 is used to establish data channels for DHCPv4 server or relay agent service backup.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535. The specified port number cannot be used by other services or be a well-known port.

Usage guidelines

To back up data for a IPv4 address pool, the master DHCPv4 server must establish a TCP data channel with the backup DHCPv4 server.

To back up DHCPv4 relay agent data for a client-side interface, the master DHCPv4 relay agent must establish a TCP data channel with the backup DHCPv4 relay agent.

You can use this command to change the TCP port number for establishing the data channel.

Examples

# Specify TCP port 30000 for VSRP to establish data channels for DHCPv4 server or relay agent service backup.

<Sysname> system-view

[Sysname] dhcp vsrp port 30000

dhcp vsrp-instance

Use dhcp vsrp-instance to associate a client-side interface on the DHCPv4 server with a VSRP instance.

Use undo dhcp vsrp-instance to remove the VSRP instance association.

Syntax

dhcp vsrp-instance vsrp-instance-name

undo dhcp vsrp-instance

Default

The client-side interfaces on the DHCPv4 server are not associated with VSRP instances..

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

You can specify a nonexistent VSRP instance for this command, but this command takes effect only after the VSRP instance is created.

Use this command on the master and backup DHCPv4 servers to match their interfaces that connect to the same client.

You can associate an interface or subinterface with only one VSRP instance.

You can associate a VSRP instance with one interface or multiple subinterfaces on the same interface.

If a VSRP instance has been associated with one interface, you must remove the VSRP instance from that interface before you can specify it on another interface.

Examples

# Associate Ten-GigabitEthernet 3/1/1 with VSRP instance vsrp1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] dhcp vsrp-instance vsrp1

ipv6 dhcp relay vsrp-instance

Use ipv6 dhcp relay vsrp-instance to associate a client-side interface on the DHCPv6 relay agent with a VSRP instance.

Use undo ipv6 dhcp relay vsrp-instance to remove the VSRP instance association.

Syntax

ipv6 dhcp relay vsrp-instance vsrp-instance-name

undo ipv6 dhcp relay vsrp-instance

Default

The client-side interfaces on the DHCPv6 relay agent are not associated with VSRP instances.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

You can specify a nonexistent VSRP instance for this command, but this command takes effect only after the VSRP instance is created.

You can associate an interface or subinterface with only one VSRP instance.

You can associate a VSRP instance with one interface or multiple subinterfaces on the same interface.

If a DHCP relay agent is configured, and PPPoE users and IPoE users share an address pool, you can associate a VSRP instance with one of the following interface combinations:

·     A VT interface and a non-VT interface.

·     A VT interface and multiple subinterfaces of a non-VT interface.

Examples

# Associate Ten-GigabitEthernet 3/1/1 with VSRP instance a.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] ipv6 dhcp relay vsrp-instance a

ipv6 dhcp vsrp port

Use ipv6 dhcp vsrp port to specify a TCP port number for VSRP to establish data channels for DHCPv6 server or relay agent service backup.

Use undo ipv6 dhcp vsrp port to restore the default.

Syntax

ipv6 dhcp vsrp port port-number

undo ipv6 dhcp vsrp port

Default

TCP port 60039 is used to establish data channels for DHCPv6 server or relay agent service backup.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535. The specified port number cannot be used by other services or be a well-known port.

Usage guidelines

To back up data for a IPv6 address pool, the master DHCPv6 server must establish a TCP data channel with the backup DHCPv6 server.

To back up DHCPv6 relay agent data for a client-side interface, the master DHCPv6 relay agent must establish a TCP data channel with the backup DHCPv6 relay agent. You can use this command to change the TCP port number for establishing the data channel.

Examples

# Specify TCP port 30000 for VSRP to establish data channels for DHCPv6 server or relay agent service backup.

<Sysname> system-view

[Sysname] ipv6 dhcp vsrp port 30000

ipv6 dhcp vsrp-instance

Use ipv6 dhcp vsrp-instance to associate a client-side interface on the DHCPv6 server with a VSRP instance.

Use undo ipv6 dhcp vsrp-instance to remove the VSRP instance association.

Syntax

ipv6 dhcp vsrp-instance vsrp-instance-name

undo ipv6 dhcp vsrp-instance

Default

The client-side interfaces on the DHCPv6 server are not associated with VSRP instances..

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

You can specify a nonexistent VSRP instance for this command, but this command takes effect only after the VSRP instance is created.

Use this command on the master and backup DHCPv6 servers to match their interfaces that connect to the same client.

You can associate an interface or subinterface with only one VSRP instance.

You can associate a VSRP instance with one interface or multiple subinterfaces on the same interface.

If a VSRP instance has been associated with one interface, you must remove the VSRP instance from that interface before you can specify it on another interface.

Examples

# Associate Ten-GigabitEthernet 3/1/1 with VSRP instance vsrp1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] ipv6 dhcp vsrp-instance vsrp1

virtual-duid

Use virtual-duid to generate a virtual DUID for a DHCPv6 server.

Use undo virtual-duid to restore the default.

Syntax

virtual-duid { enterprise-number enterprise-number identifier identifier | hardware-type hardware-type address address }

undo virtual-duid

Default

No virtual DUID is specified for a DHCPv6 server. The DHCPv6 server uses its real DUID.

Views

IPv6 address pool view

Predefined user role

network-admin

Parameters

enterprise-number enterprise-number: Specifies a registered private enterprise number. The value range for the enterprise-number argument is 0 to 4294967295.

identifier identifier: Specifies a device identifier in hexadecimal format. The number of hexadecimal digits must be an even number between 2 and 128.

hardware-type hardware-type: Specifies the hardware type, a number in the range of 0 to 65535.

address address: Specifies a link layer address in hexadecimal format. The number of hexadecimal digits must be an even number between 2 to 128.

Usage guidelines

By default, the master and backup DHCPv6 servers use their respective real DUIDs for DHCP communication. For DHCPv6 clients to correctly renew leases or release IPv6 addresses after a switchover, use this command to generate the same virtual DUID for the master and the backup.

Examples

# Configure IPv6 address pool pool1 to use the virtual DUID generated based on enterprise number 1 and identifier 1234.

<Sysname> system-view

[Sysname] ipv6 pool pool1

[Sysname-ipv6-pool-pool1] virtual-duid enterprise-number 1 identifier 1234

vsrp-instance (IPv4/IPv6 address pool view)

Use vsrp-instance to associate an IPv4 or IPv6 address pool with a VSRP instance.

Use undo vsrp-instance to remove the VSRP instance association.

Syntax

vsrp-instance vsrp-instance-name

undo vsrp-instance

Default

An IPv4 or IPv6 address pool is not associated with any VSRP instance.

Views

IPv4 or IPv6 address pool view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

When you execute this command, the master and backup DHCPv4 or DHCPv6 servers establish a data channel to back up address pool data.

You can specify a nonexistent VSRP instance, but this command takes effect only when the specified VSRP instance exists.

Examples

# Associate IPv4 address pool p1 with VSRP instance vsrp1.

<Sysname> system-view

[Sysname] ip pool p1

[Sysname-ip-pool-p1] vsrp-instance vsrp1

# Associate IPv6 address pool p1 with VSRP instance vsrp1.

<Sysname> system-view

[Sysname] ipv6 pool p1

[Sysname-ipv6-pool-p1] vsrp-instance vsrp1

IGMP VSRP commands

igmp vsrp-instance

Use igmp vsrp-instance to associate an IGMP-enabled interface with a VSRP instance.

Use undo igmp vsrp-instance to remove the VSRP instance association.

Syntax

igmp vsrp-instance vsrp-instance-name

undo igmp vsrp-instance

Default

An IGMP-enabled interface is not associated with a VSRP instance.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

You can specify a nonexistent VSRP instance for this command, but this command takes effect only after the VSRP instance is created.

You can associate an interface or subinterface with only one VSRP instance.

You can associate a VSRP instance with one interface or multiple subinterfaces on the same interface.

If a VSRP instance has been associated with one interface, you must remove the VSRP instance from that interface before you can specify it on another interface.

Removing or configuring a VSRP instance association will cause the removal of multicast group information for offline users.

Examples

# Associate Ten-GigabitEthernet 3/1/1 with VSRP instance vsrp1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] igmp vsrp-instance vsrp1

igmp vsrp-load-balance

Use igmp vsrp-load-balance to enable VSRP load sharing on an IGMP-enabled interface.

Use undo igmp vsrp-load-balance to restore the default.

Syntax

igmp vsrp-load-balance [ no-restore | restore-delay delay-time ]

undo igmp vsrp-load-balance

Default

VSRP load sharing is disabled on an IGMP-enabled interface. Only the master device forwards multicast traffic.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

no-restore: Disables multicast traffic fallback upon recovery of the failed peer device. If you specify this option, the local device will continue forwarding all multicast traffic after the peer device recovers from failure.

restore-delay delay-time: Sets the delay in seconds for switching multicast traffic to the local device after it recovers from failure. The value range for the delay-time argument is 1 to 65535, and the default value is 180.

Usage guidelines

In a VSRP group, the master device by default forwards all multicast traffic. After you enable VSRP load sharing, the master and backup devices forward multicast traffic for odd multicast group addresses and even multicast group addresses, respectively.

If you do not specify any parameters, the multicast traffic fallback delay is set to the default value. After recovering from failure, the local device must wait 180 seconds before it can forward multicast traffic.

You must configure the same VSRP load sharing settings on the two member devices in the same VSRP group.

If you configure VSRP load sharing on a subinterface, follow these restrictions:

·     Make sure the subinterface and its main interface are associated with the same VSRP instance.

·     Configure VSRP load sharing on the main interface. Otherwise, VSRP load sharing does not take effect on the subinterface.

If the member devices in a VSRP group fail simultaneously, the member device that first recovers forwards all multicast traffic. When the other member device also recovers, it loads share multicast traffic immediately, whether you enable VSRP load sharing or not. In this situation, transient multicast traffic loss will occur.

In a VSRP group, if a non-direct uplink fails on a member device, the other member device forwards all multicast traffic. When the non-direct uplink recovers, the downstream VSRP member device loads share multicast traffic immediately, whether you enable VSRP load sharing or not. In this situation, transient multicast traffic loss will occur.

When you set the multicast traffic fallback delay, follow these restrictions and guidelines:

·     To prevent absence of multicast forwarding entries from causing multicast traffic loss, increase this delay.

·     To prevent a recovered member device from being idle, decrease this delay.

·     Make sure this delay is longer than the maximum response time for IGMP general queries (configurable with the igmp max-response-time command).

·     If you do not set the maximum response time for IGMP general queries, set this delay to be longer than 60 seconds.

During multicast traffic fallback, multicast traffic loss or duplication might occur. In an environment that requires high availability of multicast services, disable multicast traffic fallback.

Examples

# Enable VSRP load sharing on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] igmp vsrp-load-balance

Related commands

display igmp interface

igmp vsrp-port

Use igmp vsrp-port to specify a TCP port number for VSRP to establish data channels for IGMP service backup.

Use undo igmp vsrp-port to restore the default.

Syntax

igmp vsrp-port port-number

undo igmp vsrp-port

Default

TCP port 60041 is used to establish data channels for IGMP service backup.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535. The specified port number cannot be used by other services or be a well-known port.

Usage guidelines

To establish a data channel for an IGMP service successfully, you must specify the same TCP port number on the master and backup devices.

Examples

# Specify TCP port 20000 for VSRP to establish data channels for IGMP service backup.

<Sysname> system-view

[Sysname] igmp vsrp-port 20000

igmp vsrp-sync enable

Use igmp vsrp-sync enable to enable IGMP data synchronization on an IGMP-enabled interface.

Use undo igmp vsrp-sync enable to disable IGMP data synchronization on an IGMP-enabled interface.

Syntax

igmp vsrp-sync enable

undo igmp vsrp-sync enable

Default

IGMP data synchronization is enabled on an IGMP-enabled interface.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Usage guidelines

Enable IGMP data synchronization if you are not sure whether the master and the backup can both receive IGMP packets.

Disable IGMP data synchronization if the master and the backup can both receive IGMP packets. For example, you can disable IGMP data synchronization if you have not configured IPoE, PPP, or portal authentication for multicast users.

The synchronized IGMP data will age out after you disable IGMP data synchronization.

Examples

# Disable IGMP data synchronization on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] undo igmp vsrp-sync enable

MLD VSRP commands

mld vsrp-instance

Use mld vsrp-instance to associate an MLD-enabled interface with a VSRP instance.

Use undo mld vsrp-instance to restore the default.

Syntax

mld vsrp-instance vsrp-instance-name

undo mld vsrp-instance

Default

An MLD-enabled interface is not associated with a VSRP instance.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

vsrp-instance-name: Specifies a VSRP instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

You can specify a nonexistent VSRP instance for this command, but this command takes effect only after the VSRP instance is created.

You can associate an interface or subinterface with only one VSRP instance.

You can associate a VSRP instance with one interface or multiple subinterfaces on the same interface.

If a VSRP instance has been associated with one interface, you must remove the VSRP instance from that interface before you can specify it on another interface.

Removing or configuring a VSRP instance association will cause the removal of IPv6 multicast group information for offline users.

Examples

# Associate Ten-GigabitEthernet 3/1/1 with VSRP instance vsrp1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] mld vsrp-instance vsrp1

mld vsrp-load-balance

Use mld vsrp-load-balance to enable VSRP load sharing on an MLD-enabled interface.

Use undo mld vsrp-load-balance to restore the default.

Syntax

mld vsrp-load-balance [ no-restore | restore-delay delay-time ]

undo mld vsrp-load-balance

Default

VSRP load sharing is disabled on an MLD-enabled interface. Only the master device forwards multicast traffic.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Parameters

no-restore: Disables multicast traffic fallback upon recovery of the failed peer device. If you specify this option, the local device will continue forwarding all multicast traffic after the peer device recovers from failure.

restore-delay delay-time: Sets the delay in seconds for switching multicast traffic to the local device after it recovers from failure. The value range for the delay-time argument is 1 to 65535, and the default value is 180.

Usage guidelines

In a VSRP group, the master device by default forwards all multicast traffic. After you enable VSRP load sharing, the master and backup devices forward multicast traffic for odd multicast group addresses and even multicast group addresses, respectively.

If you do not specify any parameters, the multicast traffic fallback delay is set to the default value. After recovering from failure, the local device must wait 180 seconds before it can forward multicast traffic.

You must configure the same VSRP load sharing settings on the two member devices in the same VSRP group.

If you configure VSRP load sharing on a subinterface, follow these restrictions:

·     Make sure the subinterface and its main interface are associated with the same VSRP instance.

·     Configure VSRP load sharing on the main interface. Otherwise, VSRP load sharing does not take effect on the subinterface.

If the member devices in a VSRP group fail simultaneously, the member device that first recovers forwards all multicast traffic. When the other member device also recovers, it loads share multicast traffic immediately, whether you enable VSRP load sharing or not. In this situation, transient multicast traffic loss will occur.

In a VSRP group, if a non-direct uplink fails on a member device, the other member device forwards all multicast traffic. When the non-direct uplink recovers, the downstream VSRP member device loads share multicast traffic immediately, whether you enable VSRP load sharing or not. In this situation, transient multicast traffic loss will occur.

When you set the multicast traffic fallback delay, follow these restrictions and guidelines:

·     To prevent absence of multicast forwarding entries from causing multicast traffic loss, increase this delay.

·     To prevent a recovered member device from being idle, decrease this delay.

·     Make sure this delay is longer than the maximum response time for MLD general queries (configurable with the mld max-response-time command).

·     If you do not set the maximum response time for MLD general queries, set this delay to be longer than 60 seconds.

During multicast traffic fallback, multicast traffic loss or duplication might occur. In an environment that requires high availability of multicast services, disable multicast traffic fallback.

Examples

# Enable VSRP load sharing on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] mld vsrp-load-balance

Related commands

display mld interface

mld vsrp-port

Use mld vsrp-port to specify a TCP port number for VSRP to establish data channels for MLD service backup.

Use undo mld vsrp-port to restore the default.

Syntax

mld vsrp-port port-number

undo mld vsrp-port

Default

TCP port 60042 is used to establish data channels for MLD service backup.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535. The specified port number cannot be used by other services or be a well-known port.

Usage guidelines

To establish a data channel for an MLD service successfully, you must specify the same TCP port number on the master and backup devices.

Examples

# Specify TCP port 20000 for VSRP to establish data channels for MLD service backup.

<Sysname> system-view

[Sysname] mld vsrp-port 20000

mld vsrp-sync enable

Use mld vsrp-sync enable to enable MLD data synchronization on an MLD-enabled interface.

Use undo mld vsrp-sync enable to disable MLD data synchronization on an MLD-enabled interface.

Syntax

mld vsrp-sync enable

undo mld vsrp-sync enable

Default

MLD data synchronization is enabled on an MLD-enabled interface.

Views

Layer 3 Ethernet interface view

Layer 3 Ethernet subinterface view

Layer 3 aggregate interface view

Layer 3 aggregate subinterface view

Predefined user roles

network-admin

Usage guidelines

Enable MLD data synchronization if you are not sure whether the master and the backup can both receive MLD packets.

Disable MLD data synchronization if the master and the backup can both receive IGMP packets. For example, you can disable IGMP data synchronization if you have not configured IPoE, PPP, or portal authentication for multicast users.

The synchronized IGMP data will age out after you disable IGMP data synchronization.

Examples

# Disable MLD data synchronization on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] undo MLD vsrp-sync enable

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