Table of Contents

Related Documents

14-CP-UP connection management commands

Title	Size	Download
14-CP-UP connection management commands	184.01 KB

CP-UP connection management commands

On a CUPS network, this device acts only as a UP. When executing operation commands in this chapter (except the display commands and the snmp-agent trap enable protocol-tunnel command), follow these restrictions and guidelines:

· If a command is tagged with (UPs), this command can be executed only on a UP. Before executing this command on a UP, make sure you are fully aware of the impact of this command on the current network and prevent configuration errors from causing network failures.

· If a command does not have any tag, this command can be executed only on a CP by default. To execute this command on a UP, do that under the guidance of professionals, make sure you are fully aware of the impact of this command on the current network, and prevent configuration errors from causing network failures.

Control channel commands

bfd enable (CUSP agent view)

Use bfd enable to enable BFD for CUSP on a CUSP agent.

Use undo bfd enable to disable BFD for CUPS on a CUSP agent.

Syntax

bfd enable [ template template-name ]

undo bfd enable

Default

BFD is disabled for CUSP.

Views

CUSP agent view

Predefined user roles

network-admin

Parameters

template template-name: Specifies a BFD template by its name , a case-sensitive string of 1 to 63 characters. If you do not specify a BFD template, this command references the default BFD session parameters. To view the BFD session information, execute the display bfd session command.

Usage guidelines

With BFD enabled for CUPS on a CUSP agent, BFD sessions will be set up for new CUSP connections to fast detect CUSP connection faults. A BFD template is used for flexibly configuring BFD session parameters. For more information about BFD templates, see BFD in High Availability Configuration Guide.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Enable BFD for CUPS on CUSP agent up1, and specify BFD template cusp-bfd. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1] bfd enable template cusp-bfd

controller address

Use controller address to specify the CUSP controller IP address for a CUSP agent.

Use undo controller address to delete the CUSP controller IP address for a CUSP agent.

Syntax

controller address { ipv4-address | ipv6 ipv6-address }

undo controller address { ipv4-address | ipv6 ipv6-address }

Default

No CUSP controller IP address is specified for a CUSP agent.

Views

CUSP agent view

Parameters

ipv4-address: Specifies a CUSP controller IPv4 address.

ipv6-address: Specifies a CUSP controller IPv6 address.

Predefined user roles

network-admin

Usage guidelines

Make sure the IP address configured by using this command is the same as that configured by using the listening-ip command on the CUSP controller.

You can execute this command multiple times to specify multiple CUSP controller IP addresses for a CUSP agent.

Examples

# Remotely specify CUSP controller IP address 3.1.1.2 for CUSP agent up1. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1] controller address 3.1.1.2

cusp agent

Use cusp agent to create a CUSP agent and enter its view, or enter the view of an existing CUSP agent.

Use undo cusp agent to delete a CUSP agent.

Syntax

cusp agent agent-name

undo cusp agent agent-name

Default

No CUSP agent exists.

Views

System view (UPs)

Predefined user roles

network-admin

Parameters

agent-name: Specifies a CUSP agent name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

Only one CUSP agent can be created on a UP. To modify the name of a CUSP agent, first delete the CUSP agent.

Examples

# Create CUSP agent up1 and enter its view. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1]

disconnection entry-aging (CUSP agent view)

Use disconnection entry-aging to configure the CUSP entry aging time of a CUSP agent after the CUSP connection is disconnected.

Use undo disconnection entry-aging to restore the default.

Syntax

disconnection entry-aging aging-time

undo disconnection entry-aging

Default

The CUSP entries of a CUSP agent do not age out after the CUSP connection is disconnected.

Views

CUSP agent view

Predefined user roles

network-admin

Parameters

aging-time: Specifies the aging time in the range of 5 to 1440 minutes.

Usage guidelines

After a CUSP connection is disconnected, if the connection is still disconnected when the CUSP entry aging time expires, the CUSP entries will be deleted. CUSP entries include user entries of UCM and route entries that the DHCP server deploys to the UPs through the control channel. For more information about UCM, see BRAS Services Configuration Guide.

When you configure this feature, follow these restrictions and guidelines:

· To prevent UP reboot from aging out and deleting CUSP entries, make sure the aging time set by using this command is longer than the sum of the UP reboot duration and the delay configured by using the first-connection-delay command.

· As a best practice, configure the same CUSP entry aging time on the CUSP controller and CUSP agent.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the CUSP entry aging time to 120 minutes on the CUSP agent after the CUSP connection is disconnected. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1] disconnection entry-aging 120

Related commands

first-connection-delay

display cusp agent (UPs)

Use display cusp agent to display the connection information of a CUSP agent.

Syntax

display cusp agent [ controller address { ipv4-address | ipv6 ipv6-address } ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

controller address: Specifies a controller connected to a CUSP agent. If you do not specify a CUSP controller, this command displays information about all controllers connected to a CUSP agent.

ipv4-address: Specifies a CUSP controller IPv4 address.

ipv6-address: Specifies a CUSP controller IPv6 address.

Usage guidelines

This command is supported only on UPs.

Examples

# Display the connection information of a CUSP agent.

<Sysname> display cusp agent

Agent name : up1

Vendor ID : 25506

CUSP version : 2

Agent IP : 1.1.1.1

VPN instance : --

SSL policy : --

BFD state : Disable

BFD template : --

Echo interval : 30s

Echo timeout threshold : 4

Keychain name : --

Disconnection entry aging time : Not aging

First connection delay time : Not delayed

Controller information:

Vendor ID : 25506

Control tunnel state : Active

Controller IP : 2.2.2.2

Connection state : Established

Packets sent : 11137

Packets received : 7993

Table 1 Command output

Field	Description
Agent name	CUSP agent name.
Vendor ID	Vendor ID.
CUSP version	CUSP protocol version.
Agent IP	IPv4 or IPv6 address of a CUSP agent. To configure a CUSP agent IP address, use the local-address command. If no CUSP agent IP address is configured, this field displays two hyphens (--).
VPN instance	VPN instance where the CUSP agent resides. If no VPN instance is configured for the CUSP agent, this field displays two hyphens (--).
SSL policy	Name of the SSL client policy associated with the CUSP connection. If no SSL client policy is associated, this field displays two hyphens (--).
BFD state	State of BFD for CUSP: · Enable. · Disable.
BFD template	Name of the BFD templates associated with the CUSP connection. If no BFD template is associated, this field displays two hyphens (--).
Echo interval	Interval at which the CUSP agent sends heartbeat detection packets, in seconds.
Echo timeout threshold	Threshold for the CUSP agent heartbeat detection timeout occurrences.
Keychain name	Security authentication keychain name specified for the CUSP connection. This field displays two hyphens (--) if no keychain name is configured.
Disconnection entry aging time	CUSP entry aging time (in minutes) after the CUSP connection is disconnected. This field displays Not aging if the entries do not age out.
First connection delay time	Delay time (in minutes) after which the CUSP agent sets up the CUSP connection for the first time after the UP is rebooted. This field displays Not delayed if the first connection setup is not delayed.
Controller information	CUSP controller information.
Control tunnel state	State of the control channel between the CP where the CUSP controller resides and the UP where the CUSP agent resides. Possible values are: · Active. · Inactive.
Controller IP	CUSP controller IP address.
Connection state	State of the connection between the CUSP controller and the CUSP agent. Possible values are: · Idle—The connection is not set up. · Established.
Packets sent	Number of packets that the CUSP agent has sent to the CUSP controller.
Packets received	Number of packets that the CUSP agent has received from the CUSP controller.

‌

echo-request (CUSP agent view)

Use echo-request to configure the heartbeat detection parameters for a CUSP agent.

Use undo echo-request to restore the default.

Syntax

echo-request { interval interval | threshold threshold }

undo echo-request { interval | threshold }

Default

The heartbeat detection packet interval is 30 seconds, and the threshold for the heartbeat detection timeout occurrences is 4 on a CUSP agent.

Views

CUSP agent view

Predefined user roles

network-admin

Parameters

interval: Specifies the interval at which the CUSP agent sends heartbeat detection packets, in the range of 0 to 120 seconds. The value 0 indicates no heartbeat detection packets are sent.

threshold: Specifies the threshold for the CUSP agent heartbeat detection timeout occurrences, in the range of 4 to 10.

Usage guidelines

A CUSP agent sends an Echo Request (heartbeat detection packet) to the connected CUSP controller at the specified interval. If the CUSP agent continuously fails to receive replies from the controller for threshold times, the CUSP agent disconnects from the CUSP controller.

The CUSP connection keepalive timer is the minimum of the following two values:

· Keepalive timer of the TCP connection carrying the CUSP connection, which is fixed at 30 seconds.

· Heartbeat detection timeout timer of the CUSP connection (interval × threshold).

Examples

# Configure the threshold as 5 for the heartbeat detection timeout occurrences for CUSP agent up1. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1] echo-request threshold 5

first-connection-delay

Use first-connection-delay to configure the delay after which a CUSP agent sets up a CUSP connection for the first time after a UP is rebooted.

Use undo first-connection-delay to restore the default.

Syntax

first-connection-delay delay-time

undo first-connection-delay

Default

A CUSP agent immediately tries to set up a CUSP connection after a UP is rebooted.

Views

CUSP agent view

Predefined user roles

network-admin

Parameters

aging-time: Specifies the first CUSP connection setup delay time in the range of 1 to 60 minutes.

Usage guidelines

After a UP is rebooted, if a CUSP connection is set up before the CGN module enters the normal state, service data might have errors. To resolve this issue, you can configure the CUSP agent to delay setting up the first CUSP connection. Make sure the delay is longer than the time taken by the CGN module to enter the normal state after device reboot. To view the module state, use the display device command.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Configure CUSP agent up1 to set up the first CUSP connection 30 minutes of delay after the UP is rebooted. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1] first-connection-delay 30

keychain-authentication (CUSP agent view)

Use keychain-authentication to specify a CUSP agent to use keychain authentication for setting up a CUSP connection.

Use undo keychain-authentication to restore the default.

Syntax

keychain-authentication keychain-name

undo keychain-authentication

Default

Keychain authentication is not used by a CUSP agent for setting up a CUSP connection.

Views

CUSP agent view

Predefined user roles

network-admin

Parameters

keychain-name: Specifies a keychain name, a case-sensitive string of 1 to 63 characters.

Usage guidelines

You can configure keychain authentication to improve the CUSP connection security. For two ends to set up CUSP connections normally, configure keychain authentication on both the CUSP controller and CUSP agent, and make sure the keychains used by both ends meet the following conditions:

· The key ID used at a time must be the same. The key ID is specified by using the key command.

· Keys with the same ID use the same authentication algorithm and authentication key, which are configured by using the authentication-algorithm and key-string commands, respectively.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Remotely specify keychain authentication with username abc for CUSP agent up1 to set up a CUSP connection. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1] keychain-authentication abc

Related commands

authentication-algorithm (Security Command Reference)

key (Security Command Reference)

keychain (Security Command Reference)

key-string (Security Command Reference)

local-address

Use local-address to specify the local IP address for a CUSP agent.

Use undo local-address to delete the local IP address configuration from a CUSP agent.

Syntax

local-address { ipv4-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ]

undo local-address

Default

No local IP address is specified for a CUSP agent.

Views

CUSP agent view

Predefined user roles

network-admin

Parameters

ipv4-address: Specifies an IPv4 address as the local IP address.

ipv6-address: Specifies an IPv6 address as the local IP address.

vpn-instance vpn-instance-name: Specifies the VPN instance to which a CUSP agent belongs. The vpn-instance-name argument specifies an MPLS L3VPN name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the CUSP agent belongs to the public network.

Usage guidelines

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Configure the local IP address as 3.1.1.1 for CUSP agent up1. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1] local-address 3.1.1.1

reset cusp agent statistics (UPs)

Use reset cusp agent statistics to clear the packet statistics of a CUSP agent.

Syntax

reset cusp agent statistics [ controller address { ipv4-address | ipv6 ipv6-address } ]

Views

User view

Predefined user roles

network-admin

Parameters

ipv4-address: Specifies a CUSP controller IPv4 address.

ipv6-address: Specifies a CUSP controller IPv6 address.

If you do not specify an IP address, this command clears packet statistics of all CUSP connections of a CUSP agent.

Usage guidelines

This command is supported only on UPs.

Examples

# Clear the packet statistics of a CUSP agent.

<Sysname> reset cusp agent statistics

snmp-agent trap enable cusp-agent (UPs)

Use snmp-agent trap enable cusp-agent to enable SNMP notifications for the CUSP agent module.

Use undo snmp-agent trap enable cusp-agent to disable SNMP notifications for the CUSP agent module.

Syntax

snmp-agent trap enable cusp-agent [ connect-state ]

undo snmp-agent trap enable cusp-agent [ connect-state ]

Default

SNMP notifications are enabled for a CUSP agent.

Views

System view

Predefined user roles

network-admin

Parameters

connect-state: Enables SNMP notifications for the CUSP connection state changes. If you do not specify this option, this command enables all types of SNMP notifications for the CUSP agent module.

Usage guidelines

With SNMP notifications enabled for the CUSP agent module, this module can generate alarms to report important events of this module. The generated alarms are sent to the SNMP module of the device. You can specify how the alarms are output through setting the alarm output parameters in SNMP. For more information about alarms, see SNMP configuration in Network Management and Monitoring Guide.

This command is supported only on UPs.

Examples

# Enable SNMP notifications for the CUSP agent module.

<Sysname> system-view

[Sysname] snmp-agent trap enable cusp-agent

ssl-client-policy

Use ssl-client-policy to specify the SSL client policy for a CUSP agent to set up a CUSP connection.

Use undo ssl-client-policy to restore the default.

Syntax

ssl-client-policy policy-name

undo ssl-client-policy

Default

No SSL client policy is specified for a CUSP agent to set up a CUSP connection.

Views

CUSP agent view

Predefined user roles

network-admin

Parameters

policy-name: Specifies an SSL client policy by its name, a case-insensitive string of 1 to 31 characters.

Usage guidelines

With this feature configured on a CUSP agent, the CUSP agent uses the SSL parameters in the SSL client policy for setting up a CUSP connection to secure the connection. For more information about SSL client policies, see SSL configuration in Security Configuration Guide.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Specify SSL client policy cusp-policy for CUSP agent up1 to set up a CUSP connection. (UPs.)

<Sysname> system-view

[Sysname] cusp agent up1

[Sysname-cusp-agent-up1] ssl-client-policy cusp-policy

Related commands

ssl client-policy (Security Command Reference)

Protocol channel commands

cp-management (UPs)

The cp-management command configuration on an interface indicates that the interface is remotely managed by a CP.

Syntax

cp-management

Default

No interface on a UP is remotely managed by a CP.

Views

Interface view

Predefined user roles

network-admin

Usage guidelines

In a CUPS network, a CP can remotely manage interfaces on UPs. When a remote interface is created on the CP, the cp-management command configuration is automatically generated on the UP interface managed by the remote interface.

The cp-management command configuration is automatically generated on the UP interface managed by the remote interface, and cannot be manually executed.

After the control channel to a UP is disconnected, you can execute the reset cp configuration command on the UP. Then, these UP interfaces are not remotely managed by the CP.

When a remote interface on the CP is mapped to a UP interface, you cannot execute the reset cp configuration command on the UP.

If the cp-management command configuration exists on the UP interface managed by the remote interface, you cannot perform the following tasks on the UP interface. To perform these tasks on the interface, first disconnect the control channel between the CP and UP and execute the reset cp configuration command on the UP.

· Deleting an interface

· Switching the interface mode between bridge and route

· Splitting an interface

· Switching the interface type by using the port-type command

· Assigning an interface to an aggregation group

· Assigning an interface to a redundancy group

cu-agent

Use cu-agent to create a CU agent and enter its view.

Use undo cu-agent to delete a CU agent and all configuration in the view of the CU agent.

Syntax

cu-agent

undo cu-agent

Default

A CU agent does not exist.

Views

System view (UPs)

Predefined user roles

network-admin

Usage guidelines

This command is supported only when the device is operating in standard mode. For more information about the system operating mode, see device management configuration in Fundamentals Configuration Guide.

In CU agent view on a CP in the CUPS scenario, you can execute the commands available in CU agent view on a UP and deploy these commands to the UP.

When you execute the undo cu-agent command, the CU agent view and configuration in the view are deleted on the CP, as well as the configuration in CU agent view on the UP.

Examples

# Create a CU agent and enter its view. (UPs.)

<Sysname> system-view

[Sysname] cu-agent

[Sysname-cu-agent]

display protocol-tunnel packet statistics (UPs)

Use display protocol-tunnel packet statistics to display the packet statistics of protocol channels.

Syntax

display protocol-tunnel packet statistics [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays entries for the active MPU.

Usage guidelines

In the CUPS scenario, the CP and a UP needs to set up a protocol channel to exchange protocol packets. During the protocol packet exchange between the CP and UP, the device will record the protocol packet statistics in the memory, which facilitates troubleshooting when a failure occurs. To view statistics of protocol packets between the CP and the UP, use this command.

Examples

# View the packet statistics of the protocol channel between slot 3 of the UP and the CP.

<Sysname> display protocol-tunnel packet statistics slot 3

Input packet statistics:

Total: 2000

PPPoE PADI and PADO: 1000

Other PPPoE: 1000

DHCP DISCOVER and OFFER: 0

Other DHCP: 0

DHCPv6: 0

ND: 0

L2TP: 0

ARP: 0

IPv4 data miss: 0

IPv6 data miss: 0

Ethernet: 0

IPv4: 0

IPv6: 0

Drop: 0

Output packet statistics:

Total: 2000

PPPoE PADI and PADO: 0

Other PPPoE: 2000

DHCP DISCOVER and OFFER: 0

Other DHCP: 0

DHCPv6: 0

ND: 0

L2TP: 0

ARP: 0

IPv4 data miss: 0

IPv6 data miss: 0

Ethernet: 0

IPv4: 0

IPv6: 0

Drop: 0

Table 2 Command output

Field	Description
Input packet statistics	Inbound protocol packet statistics of a protocol tunnel.
Output packet statistics	Outbound protocol packet statistics of a protocol tunnel.
Total	Total number of packets.
PPPoE PADI and PADO	PPPoE PADI and PADO packets.
Other PPPoE	Protocol packets except PADI and PADO packets, including PADR, PADS, and PADT packets.
DHCP DISCOVER and OFFER	DHCP Discover and Offer packets.
Other DHCP	DHCPv4 protocol packets except DHCP Discover and Offer packets.
DHCPv6	DHCPv6 protocol packets.
ND	IPv6 ND protocol packets.
L2TP	L2TP protocol packets.
ARP	ARP protocol packets that the device sends to users.
IPv4 data miss	ARP and other IPv4 packets that the users send to the device for triggering user access.
IPv6 data miss	Other IPv6 packets that the users send to the device for triggering user access.
Ethernet	Others packets that the device sends to users.
IPv4	IPv4 packets in the protocol channel.
IPv6	IPv6 packets in the protocol channel.
Drop	Dropped packets.

‌

Related commands

reset protocol-tunnel packet statistics

display protocol-tunnel verbose (UPs)

Use display protocol-tunnel verbose to display detailed information about the protocol channel between a UP and a CP on the UP.

Syntax

display protocol-tunnel verbose

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

Examples

# Display detailed information about the protocol channel between the UP and a CP on the UP.

<Sysname> display protocol-tunnel verbose

Protocol tunnel:

VXLAN ID: 100

Source IPv4/IPv6 address: 1.1.1.1

Destination IPv4/IPv6 address: 10.1.2.3

VPN instance: abc

State: UP

Active: Yes

Protocol tunnel:

VXLAN ID: 200

Source IPv4/IPv6 address: 1.1.1.1

Destination IPv4/IPv6 address: 10.1.2.4

State: UP

Active: Yes

Table 3 Command output

Field	Description
Protocol tunnel	Protocol channel information.
VXLAN ID	VXLAN ID of the protocol channel.
Source IPv4/IPv6 address	Source IPv4/IPv6 address of the protocol channel.
Destination IPv4/IPv6 address	Destination IPv4/IPv6 address of the protocol channel.
VPN instance	VPN instance associated with the protocol channel. This field is not displayed when the VPN instance is not configured.
State	Protocol channel connection status: · DOWN. · UP.
Active	Protocol channel activation status: · No—The protocol channel is not activated. · Yes—The protocol channel is activated.

‌

protocol-tunnel (CU agent view)

Use protocol-tunnel to configure the parameters for the protocol channel between a CP and a UP.

Use undo protocol-tunnel to delete the protocol channel between a CP and a UP.

Syntax

protocol-tunnel vxlan vxlan-id source { ipv4-address | ipv6 ipv6-address } destination { ipv4-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ]

undo protocol-tunnel vxlan vxlan-id source { ipv4-address | ipv6 ipv6-address } destination { ipv4-address | ipv6 ipv6-address }

Default

No protocol channel exists between a CP and a UP.

Views

CU agent view

Predefined user roles

network-admin

Parameters

vxlan vxlan-id: Specifies the VXLAN ID that a UP uses to set up a protocol channel to a CP. The value range for the vxlan-id argument is 1 to 16777215.

source: Specifies the source IP address used by a UP for setting up a protocol channel to a CP.

destination: Specifies the destination IP address used by a UP for setting up a protocol channel to a CP.

ipv4-address: Specifies an IPv4 UP IP address. This address cannot be an all-zeros, all-ones, class-D, class-E, or loopback address.

ipv6 ipv6-address: Specifies an IPv6 UP IP address. This address must be a unicast address and cannot be a loopback or link-local address. If you do not specify this option, an IPv4 UP IP address is specified.

vpn-instance vpn-instance-name: Specifies a VPN instance by its name, a case-sensitive string of 1 to 31 characters. The VPN instance is associated with the interface connecting a UP to a CP. If you do not specify this option, the interface connecting a UP to a CP belongs to the public network.

Usage guidelines

A VXLAN tunnel is set up between a UP and a CP and used as the protocol channel for exchanging protocol packets, such as ARP, IP, and DHCP protocol packets.

When you execute this command, make sure the source IP specified is the destination IP of the protocol channel on the CP, and the destination IP specified is the source IP of the protocol channel on the CP.

The VXLAN tunnels on a CP and UP pair must have the same VXLAN ID.

A CP can be configured with up to two protocol channels, which are typically used in the CPDR scenario.

If you execute this command multiple times with the same VXLAN ID, source IP address, and destination IP address, the most recent configuration takes effect.

Different UPs correspond to different VXLAN tunnels. The source IP address and destination IP address of each VXLAN tunnel must be unique. That is, a source IP address and destination IP address pair corresponds to a unique VXLAN ID.

Examples

# In CU agent view, configure parameters for the protocol channel between a UP and a CP, with VXLAN ID 10, source IP 1.1.1.1, and destination IP 2.2.2.2. (UPs.)

<Sysname> system-view

[Sysname] cu-agent

[Sysname-cu-agent] protocol-tunnel vxlan 10 source 1.1.1.1 destination 2.2.2.2

reset cp configuration (UPs)

Use reset cp configuration to clear all configuration that a CP deploys to a UP.

Syntax

reset cp configuration

Views

User view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

When the connection between a CP and a UP is normal, executing this command will clear the cp-management and protocol-tunnel configuration deployed by the CP to the UP and disconnect the CP and UP. As a result, users cannot come online.

When a UP is permanently disconnected from its CP and not managed by the CP any more, use this command to clear all configuration that the CP has deployed to the UP. After executing this command, manually disconnect the NETCONF session between the CP and UP. Otherwise, when the CP reconnects to the UP, the NETCONF session between the CP and UP cannot be re-connected. As a result, the CP cannot deploy configuration to the UP, and the CP cannot manage the UP.

When a CP and a UP are properly connected, to clear all configuration that the CP deploys to the UP, you must first delete all remote interfaces on the CP.

Examples

# Clear all configuration that a CP deploys to a UP.

<Sysname> reset cp configuration

reset protocol-tunnel packet statistics (UPs)

Use reset protocol-tunnel packet statistics to clear the packet statistics of protocol channels.

Syntax

reset protocol-tunnel packet statistics [ slot slot-number ]

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command clears entries for the active MPU.

Usage guidelines

In the CUPS scenario, during protocol packet exchange between a CP and a UP, the device will record the protocol packet statistics in the memory, which facilitates troubleshooting when a failure occurs. To prevent the history packet statistics from affecting troubleshooting, first use this command on the UP to clear the packet statistics of protocol channels, and then use the display protocol-tunnel packet statistics to display the new packet statistics of protocol channels.

A CP and a UP collect packet statistics separately. Using this command on the UP to clear the packet statistics protocol channel between the CP and the UP does not affect the packet statistics of protocol channels on the CP.

Examples

# Clear the packet statistics of all protocol channels.

<Sysname> reset protocol-tunnel packet statistics

Related commands

display protocol-tunnel packet statistics

snmp-agent trap enable protocol-tunnel

Use snmp-agent trap enable protocol-tunnel to enable SNMP notifications for CP-UP protocol tunnels.

Use undo snmp-agent trap enable protocol-tunnel to disable SNMP notifications for CP-UP protocol tunnels.

Syntax

snmp-agent trap enable protocol-tunnel

undo snmp-agent trap enable protocol-tunnel

Default

SNMP notifications are disabled for CP-UP protocol tunnels.

Views

System view

Predefined user roles

network-admin

Usage guidelines

With this feature enabled on a device, alarms are generated when the protocol tunnel states change. The generated alarms are sent to the SNMP module of the device. You can specify how the alarms are output through setting the alarm output parameters in SNMP.

For more information about alarms, see SNMP configuration in Network Management and Monitoring Guide.

Examples

# Enable SNMP notifications for CP-UP protocol tunnels.

<Sysname> system-view

[Sysname] snmp-agent trap enable protocol-tunnel

sub-interface inherit-main (UPs)

Use sub-interface inherit-main to configure subinterfaces managed by a main interface on the CP not to report state information

Use undo sub-interface inherit-main to restore the default.

Syntax

sub-interface inherit-main

undo sub-interface inherit-main

Default

Subinterfaces managed by a main interface on the CP report state information.

Views

System view

Predefined user roles

network-admin

Usage guidelines

By default, the state of a remote subinterface is reported by a UP to the CP through CUSP channels. On CPs of some vendors, the state of remote subinterfaces is inherited from their main interfaces, the CPs do not receive subinterface state information reported by UPs, and UPs do not report subinterface state information. When you interoperate with CPs of these vendors, for compatibility with the subinterface state information processing method, execute this command on the UP to disable the UP from reporting remote subinterface state information.

Execute this command on both a CP and its UPs. If you execute this command on a CP, you must also execute this command on its UPs, and vice versa. Asymmetric configuration of this command might cause the subinterface state information reported by UPs to be lost. As a result, the remote subinterface state on the CP is incorrect.

After you execute this command, as a best practice, do not modify the subinterface state information on a UP. Otherwise, the subinterface resources might be inconsistent on the CP and its UPs.

If this feature is also configured on a CP, when you execute the undo sub-interface inherit-main command, first execute this command on the CP, and then execute this command on the UP. Otherwise, the subinterface resources might be inconsistent on the CP and its UPs.

Examples

# Disable subinterfaces managed by a CP from reporting state information.

<Sysname> system-view

[Sysname] sub-interface inherit-main

17-BRAS Services Command Reference

disconnection entry-aging (CUSP agent view)

display cusp agent (UPs)

echo-request (CUSP agent view)

keychain-authentication (CUSP agent view)

reset cusp agent statistics (UPs)

snmp-agent trap enable cusp-agent (UPs)

cp-management (UPs)

display protocol-tunnel packet statistics (UPs)

display protocol-tunnel verbose (UPs)

protocol-tunnel (CU agent view)

reset cp configuration (UPs)

reset protocol-tunnel packet statistics (UPs)

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

Company Information

News & Events

Contact Us