Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 06-PPPoE commands | 173.48 KB |
Contents
display pppoe-server packet statistics
display pppoe-server session packet
display pppoe-server session summary
display pppoe-server throttled-mac
pppoe-server session-limit per-mac
pppoe-server session-limit per-vlan
pppoe-server tag ppp-max-payload
pppoe-server virtual-template va-pool
reset pppoe-server packet statistics
PPPoE commands
PPPoE server commands
bandwidth
Use bandwidth to set the expected bandwidth of an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth (in kbps) is the interface baud rate divided by 1000.
Views
VT interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 800000000 kbps.
Usage guidelines
The expected bandwidth of an interface affects the link costs in OSPF. For more information, see Network Connectivity Configuration Guide.
Examples
# Set the expected bandwidth of Virtual-Template 10 to 1000 kbps.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] bandwidth 1000
default
Use default to restore the default settings for a VT interface.
Syntax
default
Views
VT interface view
Predefined user roles
network-admin
Usage guidelines
|
|
CAUTION: The default command might interrupt ongoing network services. Make sure you are fully aware of the impact of this command before using it on a live network. |
This command might fail to restore the default settings for some commands for reasons such as command dependencies or system restrictions. Use the display this command in interface view to identify these commands. Use the undo forms of these commands or follow the command reference to individually restore their default settings. If your restoration attempt still fails, follow the error message instructions to resolve the problem.
Examples
# Restore the default settings of Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] default
description
Use description to configure the description of an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description for a VT interface is interface name Interface (for example, Virtual-Template1 Interface).
Views
VT interface view
Predefined user roles
network-admin
Parameters
text: Specifies the interface description, a case-sensitive string of 1 to 255 characters.
Examples
# Set the description for Virtual-Template 10 to virtual-interface.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] description virtual-interface
display pppoe-server packet statistics
Use display pppoe-server packet statistics to display PPPoE server negotiation packet statistics.
Syntax
display pppoe-server packet statistics [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a cloud cluster member device by its member ID. If you do not specify a member device, this command displays PPPoE server negotiation packet statistics for all cloud cluster member devices.
Examples
# Display PPPoE server negotiation packet statistics for the specified slot.
<Sysname> display pppoe-server packet statistics slot 2
PPPoE Server packet statistics in slot 2:
RECV_PADI_PKT : 10 DISCARD_PADI_PKT : 0
SEND_PADO_PKT : 10
RECV_PADR_PKT : 10 DISCARD_PADR_PKT : 0
SEND_PADS_PKT : 10
RECV_PADT_PKT : 9 DISCARD_PADT_PKT : 0
SEND_PADT_PKT : 9
Table 1 Command output
|
Field |
Description |
|
RECV_PADI_PKT |
Number of received PADI packets. |
|
DISCARD_PADI_PKT |
Number of discarded PADI packets. |
|
SEND_PADO_PKT |
Number of sent PADO packets. |
|
RECV_PADR_PKT |
Number of received PADR packets. |
|
DISCARD_PADR_PKT |
Number of discarded PADR packets. |
|
SEND_PADS_PKT |
Number of sent PADS packets. |
|
RECV_PADT_PKT |
Number of received PADT packets. |
|
DISCARD_PADT_PKT |
Number of discarded PADT packets. |
|
SEND_PADT_PKT |
Number of sent PADT packets. |
Related commands
reset pppoe-server packet statistics
display pppoe-server session packet
Use display pppoe-server session packet to display packet statistics for PPPoE sessions.
Syntax
display pppoe-server session packet { slot slot-number | interface interface-type interface-number }
Views
Predefined user roles
network-admin
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface for centralized devices, the command displays packet statistics for PPPoE sessions on all interfaces.
slot slot-number: Specifies a cloud cluster member device by its member ID. If you do not specify a member device, the command displays packet statistics for PPPoE sessions on all member devices.
# Display packet statistics for PPPoE sessions on VLAN-interface 1.
<Sysname> display pppoe-server session packet interface vlan-interface 1
Total PPPoE sessions on slot 3: 1
Ethernet interface: Vlan1
Session ID: 1
InPackets: 40
OutPackets: 58
InBytes: 690
OutBytes: 506
InDrops: 3
OutDrops: 1
Total PPPoE sessions on slot 4: 2
Ethernet interface: Vlan1
Session ID: 1
InPackets: 43
OutPackets: 59
InBytes: 790
OutBytes: 576
InDrops: 2
OutDrops: 1
Ethernet interface: Vlan1
Session ID: 2
InPackets: 35
OutPackets: 36
InBytes: 370
OutBytes: 386
InDrops: 0
OutDrops: 0
Table 2 Command output
|
Field |
Description |
|
Ethernet interface |
Interface where the PPPoE session is present. |
|
Session ID |
PPPoE session ID. |
|
InPackets |
Number of packets received. |
|
OutPackets |
Number of packets transmitted. |
|
InBytes |
Number of bytes received. |
|
OutBytes |
Number of bytes transmitted. |
|
InDrops |
Number of discarded incoming packets. |
|
OutDrops |
Number of discarded outgoing packets. |
Related commands
display interface virtual-access
display pppoe-server session summary
Use display pppoe-server session summary to display summary PPPoE session information.
Syntax
display pppoe-server session summary { slot slot-number | interface interface-type interface-number }
Views
Any view
Predefined user roles
network-admin
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface for centralized devices, the command displays summary PPPoE session information for all interfaces.
slot slot-number: Specifies a cloud cluster member device by its member ID. If you do not specify a member device, the command displays summary PPPoE session information for all member devices.
Usage guidelines
Summary PPPoE session information on a physical interface can be displayed only on the card where the interface resides. Summary PPPoE session information on a logical interface can be displayed on all cards.
Examples
# Display summary PPPoE session information on VLAN-interface 1.
<Sysname> display pppoe-server session summary interface vlan-interface 1
Total PPPoE sessions on slot 1: 1
Ethernet interface: Vlan1
Session ID: 1
PPP interface: VA1
State: PADR_RCVD
Remote MAC: 00e0-1500-7100
Local MAC: 00e0-1400-7300
Service VLAN: N/A
Customer VLAN: N/A
Total PPPoE sessions on slot 2: 2
Ethernet interface: Vlan1
Session ID: 1
PPP interface: VA1
State: PADR_RCVD
Remote MAC: 00e0-1500-7100
Local MAC: 00e0-1400-7300
Service VLAN: N/A
Customer VLAN: N/A
Ethernet interface: Vlan1
Session ID: 2
PPP interface: VA2
State: OPEN
Remote MAC: 00e0-1500-7100
Local MAC: 00e0-1400-7400
Service VLAN: 2
Customer VLAN: 1
Table 3 Command output
|
Field |
Description |
|
Total PPPoE sessions |
Total number of PPPoE sessions on physical interfaces and logical interfaces. |
|
Local PPPoE sessions |
Total number of PPPoE sessions on physical interfaces. When an interface is specified, this field is not displayed. |
|
Ethernet interface |
Interface where the PPPoE session is present. |
|
Session ID |
PPPoE session ID. |
|
PPP interface |
Virtual access interface created for the PPPoE session. |
|
State |
PPPoE session state: · PADR RCVD—The PPPoE session is being negotiated. · Open—The PPPoE session has been successfully established. |
|
RemoteMAC |
MAC address of the remote end. |
|
LocalMAC |
MAC address of the local end. |
|
Service VLAN |
Service provider VLAN. N/A means no service provider VLAN is available. |
|
Customer VLAN |
Customer VLAN. N/A means no customer VLAN is available. |
display pppoe-server throttled-mac
Use display pppoe-server throttled-mac to display information about blocked users.
Syntax
display pppoe-server throttled-mac { slot slot-number | interface interface-type interface-number }
Views
Any view
Predefined user roles
network-admin
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, the command displays information about blocked users on all interfaces.
slot slot-number: Specifies a cloud cluster member device by its member ID. If you do not specify a member device, the command displays information about blocked users on all member devices.
Examples
# Display information about blocked users on VLAN-interface 1.
<Sysname> display pppoe-server throttled-mac interface vlan-interface 1
Total 1 client MACs in slot 1:
Interface Remote MAC Start time Remaining time(s)
Vlan1 00e0-1500-4100 2019-12-01,12:10:30 55
Total 2 client MACs in slot 2:
Interface Remote MAC Start time Remaining time(s)
Vlan1 00e0-1500-6300 2019-12-01,12:10:30 55
Vlan1 00e0-1500-6000 2019-12-01,12:10:40 65
Vlan1 00e0-1500-6300 2019-12-01,12:10:50 75
Table 4 Command output
|
Field |
Description |
|
Interface |
Interface at which the user is blocked. |
|
Remote MAC |
MAC address of the user. |
|
Start time |
Time to start blocking users. |
|
Remaining time(s) |
Time left for blocking users, in seconds. |
Related commands
pppoe-server throttle per-mac
display pppoe-server va-pool
Use display pppoe-server va-pool to display information about VA pools.
Syntax
display pppoe-server va-pool
Views
Any view
Predefined user roles
network-admin
Examples
# Display information about VA pools.
Location VT interface Size Unused/State
1/* Virtual-Template1 1000 900
- Virtual-Template2 1000 0
Table 5 Command output
|
Field |
Description |
|
Location |
Cloud cluster member device, card, and CPU where the VA pool resides. When the field displays a hyphen (-), it indicates a global VA pool. If the device cannot display the CPU, an asterisks (*) is displayed, for example, 1/0/*. |
|
VT interface |
Virtual-Template interface that uses the VA pool. |
|
Unused/State |
VA pool capacity available for PPP users/current state of the VA pool. · Creating—The VA pool is being created. · Destroying—The VA pool is being removed. |
Related commands
pppoe-server virtual-template va-pool
interface virtual-template
Use interface virtual-template to create a VT interface and enter its view, or enter the view of an existing VT interface.
Use undo interface virtual-template to remove a VT interface.
Syntax
interface virtual-template number
undo interface virtual-template number
Default
No VT interfaces exist.
Views
System view
Predefined user roles
network-admin
Parameters
number: Specifies a VT interface by its number. The value range for this argument is 0 to 1023.
Usage guidelines
To remove a VT interface, make sure all the corresponding VA interfaces are removed and the VT interface is not in use.
Examples
# Create interface Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10]
mtu
Use mtu to set the MTU size of an interface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU of an interface is 1500 bytes.
Views
VT interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU size. The value range is 128 to 1500.
Usage guidelines
The MTU size setting of an interface affects the fragmentation and reassembly of IP packets on that interface.
To make the mtu command take effect on an interface, you must re-enable the interface by using the shutdown command and then the undo shutdown command.
Examples
# Set the MTU size of Virtual-Template 10 to 1400 bytes.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] mtu 1400
ppp lcp echo mru verify
Use ppp lcp echo mru verify to enable maximum receive unit (MRU) verification for PPPoE on a VT interface.
Use undo ppp lcp echo mru verify to disable MRU verification for PPPoE.
Syntax
ppp lcp echo mru verify [minimum value ]
undo ppp lcp echo mru verify
Default
MRU verification for PPPoE is disabled on a VT interface.
Views
VT interface view
Predefined user roles
network-admin
Parameters
minimum value: Specifies the minimum MRU in the range of 64 to 1500 bytes.
Usage guidelines
To support an MTU larger than 1492, PPPoE adds the PPP-Max-Payload option during PPPoE negotiation. This option identifies the MTU for the current PPPoE session. If the MTU is larger than 1492, PPP uses the MTU as the MRU during LCP negotiation, and reports the MTU after negotiation.
MRU verification prevents the negotiated MRU from exceeding the receiving and sending capabilities of the interface. If the negotiated MRU is larger than 1492, the PPPoE server sends an echo request that has the same size as the negotiated MRU. If the PPPoE server receives a reply, it uses the MRU as the MTU. If the PPPoE server fails to receive a reply, the following situations occur:
· If the minimum MRU is configured, the PPPoE server sends a packet that has the same size as the minimum MRU.
· If the minimum MRU is not configured, the PPPoE server sends a packet that has the same size as the negotiated MRU.
If the second verification still fails, the PPPoE server tears down the link.
NCP negotiation starts after the MRU verification succeeds.
Examples
# Enable MRU verification for PPPoE and set the minimum MRU to 1200 bytes on Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] ppp lcp echo mru verify minimum 1200
pppoe-server access-delay
Use pppoe-server access-delay to set the response delay time on an interface.
Use undo pppoe-server access-delay to restore the default.
Syntax
pppoe-server access-delay delay-time
undo pppoe-server access-delay
Default
No response delay time is set on an interface.
Views
VLAN interface view
Predefined user roles
network-admin
Parameters
delay-time: Specifies the response delay time, in the range of 10 to 25500 milliseconds.
Usage guidelines
The system responds to the first packet of a PPP connection on the interface after the configured delay time elapses.
Examples
# Set the response delay time to 100 milliseconds on VLAN-interface 10.
<Sysname> system-view
[Sysname] interface Vlan-interface 10
[Sysname-Vlan-interface10] pppoe-server access-delay 100
pppoe-server bind
Use pppoe-server bind to enable the PPPoE server on an interface and bind the interface to a VT interface.
Use undo pppoe-server bind to disable the PPPoE server on an interface.
Syntax
pppoe-server bind virtual-template number
undo pppoe-server bind
Default
The PPPoE server is disabled on an interface.
Views
VLAN interface view
Predefined user roles
network-admin
Parameters
virtual template number: Specifies a VT interface by its number. The value range for the number argument varies by device model.
Usage guidelines
A PPPoE server-enabled interface can be bound to a nonexistent VT interface.
If the interface has been bound to a VT interface, you cannot use this command to bind the interface to another VT interface. To do that, disable the PPPoE server on the interface first.
If both the PPPoE client and PPPoE server are enabled on an interface, the PPPoE client feature does not take effect.
Examples
# Enable the PPPoE server on VLAN-interface 10 and bind the interface to Virtual-Template 1.
<Sysname> system-view
[Sysname] interface Vlan-interface 10
[Sysname-Vlan-interface10] pppoe-server bind virtual-template 1
pppoe-server session-limit
Use pppoe-server session-limit to set the maximum number of PPPoE sessions on an interface.
Use undo pppoe-server session-limit to restore the default.
Syntax
pppoe-server session-limit number
undo pppoe-server session-limit
Default
The number of PPPoE sessions on an interface is not limited.
Views
VLAN interface view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of PPPoE sessions on an interface, in the range of 1 to 65534.
Usage guidelines
PPPoE can establish a session when none of the following limits are reached:
· Limit for a user on an interface.
· Limit for a VLAN on an interface.
· Limit on an interface.
· Limit on a cloud cluster member device.
New maximum number settings only apply to subsequently established PPPoE sessions.
Examples
# Set the maximum number of PPPoE sessions on VLAN-interface 10 to 50.
<Sysname> system-view
[Sysname] interface Vlan-interface 10
[Sysname-Vlan-interface10] pppoe-server session-limit 50
Related commands
pppoe-server session-limit per-mac
pppoe-server session-limit per-vlan
pppoe-server session-limit total
pppoe-server session-limit per-mac
Use pppoe-server session-limit per-mac to set the maximum number of PPPoE sessions for a user on an interface.
Use undo pppoe-server session-limit per-mac to restore the default.
Syntax
pppoe-server session-limit per-mac number
undo pppoe-server session-limit per-mac
Default
A user can create a maximum of 100 PPPoE sessions on an interface.
Views
VLAN interface view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of PPPoE sessions for a user, in the range of 1 to 65534.
Usage guidelines
A user is identified by a MAC address.
PPPoE can establish a session when none of the following limits are reached:
· Limit for a user on an interface.
· Limit for a VLAN on an interface.
· Limit on an interface.
· Limit on a cloud cluster member device.
New maximum number settings only apply to subsequently established PPPoE sessions.
Examples
# Set the maximum number of PPPoE sessions for a user on VLAN-interface 10 to 50.
<Sysname> system-view
[Sysname] interface Vlan-interface 10
[Sysname-Vlan-interface10] pppoe-server session-limit per-mac 50
Related commands
pppoe-server session-limit
pppoe-server session-limit per-vlan
pppoe-server session-limit total
pppoe-server session-limit per-vlan
Use pppoe-server session-limit per-vlan to set the maximum number of PPPoE sessions for a VLAN on an interface.
Use undo pppoe-server session-limit per-vlan to restore the default.
Syntax
pppoe-server session-limit per-vlan number
undo pppoe-server session-limit per-vlan
Default
The number of PPPoE sessions for a VLAN on an interface is not limited.
Views
VLAN interface view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of PPPoE sessions for a VLAN, in the range of 1 to 65534.
Usage guidelines
PPPoE can establish a session when none of the following limits are reached:
· Limit for a user on an interface.
· Limit for a VLAN on an interface.
· Limit on an interface.
· Limit on a device.
New maximum number settings only apply to subsequently established PPPoE sessions.
Examples
# Set the maximum number of PPPoE sessions for a VLAN on VLAN-interface 10 to 50.
<Sysname> system-view
[Sysname] interface Vlan-interface 10
[Sysname-Vlan-interface10] pppoe-server session-limit per-vlan 50
Related commands
pppoe-server sessions limit
pppoe-server sessions limit per-mac
pppoe-server sessions limit total
pppoe-server tag ac-name
Use pppoe-server tag ac-name to set the access concentrator (AC) name for the PPPoE server on an interface.
Use undo pppoe-server tag ac-name to restore the default.
Syntax
pppoe-server tag ac-name name
undo pppoe-server tag ac-name
Default
The AC name for the PPPoE server is the device name on an interface.
Views
VLAN interface view
Predefined user roles
network-admin
Parameters
name: Specifies an AC name, a case-sensitive string of 1 to 64 characters.
Usage guidelines
The PPPoE server sends its AC name in PADO packets. PPPoE clients choose a PPPoE server by AC name.
The device does not support an AC name comprised of all blank spaces.
Examples
# Specify the AC name for the PPPoE server on VLAN-interface 10 as pppoes.
<Sysname> system-view
[Sysname] interface Vlan-interface 10
[Sysname-Vlan-interface10] pppoe-server tag ac-name pppoes
pppoe-server tag ppp-max-payload
Use pppoe-server tag ppp-max-payload to enable the PPPoE server to support the ppp-max-payload tag and set a range for the tag on an interface.
Use undo pppoe-server tag ppp-max-payload to restore the default.
Syntax
pppoe-server tag ppp-max-payload [ minimum min-number maximum max-number ]
undo pppoe-server tag ppp-max-payload
Default
The PPPoE server does not support ppp-max-payload tag on an interface. The PPPoE server ignores the ppp-max-payload tag in PADI or PADS packets from clients, and returns a PADO or PADS packets without the ppp-max-payload tag.
Views
VLAN interface view
Predefined user roles
network-admin
Parameters
minimum min-number: Specifies the minimum value for the PPP maximum payload, in the range of 64 to 4470 bytes. The default value is 1492 bytes.
maximum max-number: Specifies the maximum value for the PPP maximum payload, in the range of 64 to 4470 bytes. The default value is 1500 bytes. The max-number argument must be equal or greater than the min-number argument.
Usage guidelines
This command enables the PPPoE server to forward large PPP packets with a payload larger than 1492 bytes and reduces fragmentation. If the ppp-max-payload tag sent by the PPPoE client is within the tag range, the PPPoE server returns a PADO or PADS packet that includes the tag. If not, the PPPoE server considers the received packets invalid, and it does not return a PADO or PADS packet.
The jumboframe enable command can change the size of jumbo frames supported by the interface. The maximum size of the jumbo frames configured by the jumboframe enable command should be larger than the maximum value configured by the pppoe-server tag ppp-max-payload command.
Examples
# Enable the PPPoE server to support the ppp-max-payload tag and set the value for the PPP maximum payload to be in the range of 1494 to 1580 bytes on VLAN-interface 10.
<Sysname> system-view
[Sysname] interface Vlan-interface 10
[Sysname-Vlan-interface10] pppoe-server tag ppp-max-payload minimum 1494 maximum 1508
Related commands
jumboframe enable (Interface Command References)
pppoe-server tag service-name
Use pppoe-server tag service-name to set a service name for a PPPoE server on an interface.
Use undo pppoe-server tag service-name to restore the default.
Syntax
pppoe-server tag service-name name
undo pppoe-server tag service-name
Default
A PPPoE server does not have a service name.
Views
VLAN interface view
Predefined user roles
network-admin
Parameters
name: Specifies a service name, a case-sensitive string of 1 to 64 characters.
Usage guidelines
Service names identify the traffic destined for PPPoE servers when multiple PPPoE servers are providing services on the network. A PPPoE client establishes a session with the target PPPoE server by using the following process:
1. The client broadcasts a PADI packet.
2. The server compares its service name with the service-name tag field of the PADI packet. The server sends a PADO packet to the client if either of the following conditions exists:
¡ The field matches the service name.
¡ No service name is configured.
3. The client sends a PADR packet to the server.
4. The server compares its service name with the service-name tag field of the PADR packet. The server sends a PADS packet and sets up a session with the client if either of the following conditions exists:
¡ The field matches the service name.
¡ No service name is configured.
Examples
# Set the service name to pppoes for the PPPoE server on VLAN-interface 10.
<Sysname> system-view
[Sysname] interface Vlan-interface 10
[Sysname-Vlan-interface10] pppoe-server tag service-name pppoes
pppoe-server virtual-template va-pool
Use pppoe-server virtual-template va-pool to configure a VA pool.
Use undo pppoe-server virtual-template va-pool to remove a VA pool.
Syntax
pppoe-server virtual-template template-number [ slot slot-number ] va-pool va-volume
undo pppoe-server virtual-template template-number [ slot slot-number ] va-pool
Default
No VA pool is configured.
Views
System view
Predefined user roles
network-admin
Parameters
virtual-template template-number: Specifies an existing VT interface to use the VA pool.
va-pool va-volume: Specifies the maximum number of VA interfaces contained in the VA pool, in the range of 1 to 65534. The actual maximum value varies by device model.
slot slot-number: Specifies a cloud cluster member device by its cloud cluster member ID. If you do not specify a member device, a global VA pool is created.
Usage guidelines
The PPPoE server creates a VA interface for a PPPoE session to transmit packets between PPPoE and PPP, and removes the VA interface when the user goes offline. Creating and removing VA interfaces take time.
You can configure VA pools to improve the performance of PPPoE session establishment and termination. A VA pool contains a group of automatically numbered VA interfaces. The PPPoE server selects a VA interface from the pool for a requesting user and release the VA interface when the user goes offline. When a VA pool is exhausted, the system creates VA interfaces for new PPPoE sessions, and removes those VA interfaces when the users go offline.
On a VT interface, you can create one global VA pool and one regional VA pool per member device for interfaces bound with the VT interface.
· The global VA pool contains VA interfaces for logical interfaces that might span multiple devices, such as Ethernet aggregate interfaces.
· The regional VA pool contains VA interfaces for interfaces that do not span multiple devices, such as Ethernet interfaces.
When you configure a VA pool, follow these guidelines:
· To change the capacity of a VA pool, you must delete the previous configuration, and reconfigure the VA pool.
· Creating or removing a VA pool takes time. During the process of creating or removing a VA pool, users can go online or offline, but the VA pool does not take effect.
· If the system fails to create a VA pool because of insufficient resources, you can view the available resources by using the display pppoe-server va-pool command.
· VA pools are memory intensive. Set their capacity depending on your network requirements.
· Deleting a VA pool does not log off the users who are using VA interfaces in the VA pool.
Examples
# Create a VA pool with a capacity of 1000 VA interfaces on Virtual-Template 2.
<Sysname> system-view
[Sysname] pppoe-server virtual-template 2 va-pool 1000
Related commands
display pppoe-server va-pool
reset pppoe-server
Use reset pppoe-server to clear PPPoE sessions on the PPPoE server.
Syntax
reset pppoe-server { all | interface interface-type interface-number | virtual-template number }
Views
User view
Predefined user roles
network-admin
Parameters
all: Clears all PPPoE sessions.
interface interface-type interface-number: Specifies an interface by its type and number.
virtual-template number: Specifies a VT interface by its number.
Examples
# Clear established sessions on Virtual-template 1 on the PPPoE server.
<Sysname> reset pppoe-server virtual-template 1
reset pppoe-server packet statistics
Use reset pppoe-server packet statistics to clear PPPoE server negotiation packet statistics.
Syntax
reset pppoe-server packet statistics [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a cloud cluster member device by its member ID. If you do not specify a member device, this command clears PPPoE server negotiation packet statistics for all cloud cluster member devices.
Examples
# Clear PPPoE server negotiation packet statistics for the specified slot.
<Sysname> reset pppoe-server packet statistics slot 2
Related commands
display pppoe-server packet statistics
service
Use service to specify a primary traffic processing slot for an interface.
Use undo service to restore the default.
Syntax
service slot slot-number
undo service slot
Default
No primary traffic processing slot is specified for an interface.
Views
VT interface view
Default command level
network-admin
Parameters
slot slot-number: Specifies a cloud cluster member device by its member ID.
Usage guidelines
This command is supported on distributed devices and cloud cluster-capable centralized devices.
Specify traffic processing slots if a feature requires that all traffic on a VT interface be processed on the same slot.
For high availability, you can specify one primary and one backup traffic processing slot by using the service command and the service standby command, respectively.
To avoid processing slot switchover, specify the primary slot before specifying the backup slot. If you specify the backup slot before specifying the primary slot, traffic is switched over to the primary slot immediately after you specify the primary slot.
If you specify both primary and backup slots for an interface, traffic on that interface is processed as follows:
· The backup slot takes over when the primary slot becomes unavailable. The backup slot continues to process traffic for the interface after the primary slot becomes available again. The switchover will not occur until the backup slot becomes unavailable.
· When no specified traffic processing slots are available, the traffic is processed on the slot at which it arrives. Then, the processing slot that first becomes available again takes over.
If you do not specify a primary or a backup traffic processing slot for an interface, traffic on that interface is processed on the slot at which the traffic arrives.
Examples
# Specify slot 2 as the primary traffic processing slot for Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] service slot 2
Related commands
service standby
service standby
Use service standby to specify a backup traffic processing slot for an interface.
Use undo service standby to restore the default.
Syntax
service standby slot slot-number
undo service standby slot
Default
No backup traffic processing slot is specified for an interface.
Views
VT interface view
Default command level
network-admin
Parameters
slot slot-number: Specifies a cloud cluster member device by its member ID.
Usage guidelines
This command is supported on distributed devices and cloud cluster-capable centralized devices.
Specify traffic processing slots if a feature requires that all traffic on a VT interface be processed on the same slot.
For high availability, you can specify one primary and one backup traffic processing slot by using the service command and the service standby command, respectively.
To avoid processing slot switchover, specify the primary slot before specifying the backup slot. If you specify the backup slot before specifying the primary slot, traffic is switched over to the primary slot immediately after you specify the primary slot.
If you specify both primary and backup slots for an interface, traffic on that interface is processed as follows:
· The backup slot takes over when the primary slot becomes unavailable. The backup slot continues to process traffic for the interface after the primary slot becomes available again. The switchover will not occur until the backup slot becomes unavailable.
· When no specified traffic processing slots are available, the traffic is processed on the slot at which it arrives. Then, the processing slot that first becomes available again takes over.
If you do not specify a primary or a backup traffic processing slot for an interface, traffic on that interface is processed on the slot at which the traffic arrives.
Examples
# Specify slot 2 as the primary traffic processing slot for Virtual-Template 10. Specify slot 3 as the backup traffic processing slot for Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] service slot 2
[Sysname-Virtual-Template10] service standby slot 3
Related commands
service
