- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
01-Text | 1.77 MB |
Contents
ppp compression iphc rtp-connections
ppp compression iphc tcp-connections
remote address dhcp client-identifier
display interface virtual-access
display interface virtual-template
reset counters interface mp-group
reset counters interface virtual-access
display pppoe-server session packet
display pppoe-server session summary
display pppoe-server throttled-mac
pppoe-server access-line-id bas-info
pppoe-server access-line-id circuit-id parse-mode
pppoe-server access-line-id circuit-id trans-format
pppoe-server access-line-id content
pppoe-server access-line-id remote-id trans-format
pppoe-server access-line-id trust
pppoe-server session-limit per-mac
pppoe-server session-limit per-vlan
pppoe-server session-limit total
pppoe-server tag ppp-max-payload
pppoe-server virtual-template va-pool
display pppoe-client session packet
display pppoe-client session summary
reset pppoe-client session packet
display l2tp session temporary
ppp user accept-format imsi-sn split
ppp user attach-format imsi-sn split
reset counters interface virtual-ppp
isdn progress-to-alerting enable
display interface virtual-ethernet
reset counters interface virtual-ethernet
3G/4G modem management commands
reset counters controller cellular
3G modem-specific management commands
4G modem-specific management commands
fr compression iphc rtp-connections
fr compression iphc tcp-connections
fr ipv6 ind solicitation retrans-timer
Multilink Frame Relay commands
PPP and MP commands
This feature is supported only on Layer 2 Ethernet ports on the following modules:
· AM.
· AS.
· ASE.
· BS.
· CE3.
· CPOS.
· E1.
· E1-F.
· POS.
· SAE.
· T1.
· T1-F.
Commands and descriptions for centralized devices apply to the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR2600-6-X1/2600-10-X1.
· MSR 2630.
· MSR3600-28/3600-51.
· MSR3600-28-SI/3600-51-SI.
· MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC.
· MSR 3610/3620/3620-DP/3640/3660.
· MSR810-LM-GL/810-W-LM-GL/830-6EI-GL/830-10EI-GL/830-6HI-GL/830-10HI-GL/2600-6-X1-GL/3600-28-SI-GL.
Commands and descriptions for distributed devices apply to the following routers:
· MSR5620.
· MSR 5660.
· MSR 5680.
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
PPP commands
display ip pool
Use display ip pool to display PPP address pools.
Syntax
display ip pool [ pool-name ] [ group group-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
pool-name: Specifies a PPP address pool by its name, a case-sensitive string of 1 to 31 characters.
group group-name: Displays PPP address pools in a group specified by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
If you do not specify any parameters, the command displays brief information about all PPP address pools.
If you specify an address pool, the command displays detailed information about the specified PPP address pool.
Examples
# Display brief information about all PPP address pools.
<Sysname> display ip pool
Group name: a
Pool name Start IP address End IP address Free In use
aaa1 1.1.1.1 1.1.1.5 5 0
aaa2 1.1.1.6 1.1.1.10 5 0
Group name: b
Pool name Start IP address End IP address Free In use
bbb 1.1.2.1 1.1.2.5 4 1
2.2.2.1 2.2.2.5 5 0
# Display brief information about the PPP address pools in group a.
<Sysname> display ip pool group a
Group name: a
Pool name Start IP address End IP address Free In use
aaa1 1.1.1.1 1.1.1.5 5 0
aaa2 1.1.1.6 1.1.1.10 5 0
# Display detailed information about PPP address pool bbb.
<Sysname> display ip pool bbb
Group name: b
Pool name Start IP address End IP address Free In use
bbb 1.1.2.1 1.1.2.5 4 1
2.2.2.1 2.2.2.5 5 0
In use IP addresses:
IP address Interface
1.1.2.1 POS2/2/0
Table 1 Command output
Field |
Description |
Free |
Number of free IP addresses. |
In use |
Number of IP addresses that have been assigned. |
In use IP addresses |
Information about the IP addresses that have been assigned. |
Interface |
Local interface that requests the IP address for the peer interface. |
Related commands
ip pool
display ppp access-user
Use display ppp access-user to display PPP user information.
Syntax
display ppp access-user { interface interface-type interface-number [ count ] | ip-address ipv4-address | ipv6-address ipv6-address | username user-name | user-type { lac | lns | pppoa | pppoe } [ count ] }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Displays brief information about PPP users on the specified interface.
count: Displays the total number of PPP users that match the specified criteria.
ip-address ipv4-address: Displays detailed information about the PPP user specified by its IPv4 address.
ipv6-address ipv6-address: Displays detailed information about the PPP user specified by its IPv6 address.
username user-name: Displays detailed information about the PPP user specified by its username, a case-sensitive string of 1 to 80 characters.
user-type: Displays brief information about online users of the specified type.
lac: Displays brief information about L2TP users for an LAC.
lns: Displays brief information about L2TP users for an LNS.
pppoa: Displays brief information about PPPoA users.
pppoe: Displays brief information about PPPoE users.
Usage guidelines
Brief information about a PPP user includes the following:
· Brief name of the VA interface.
· Username.
· MAC address.
· IPv4 address, IPv6 address, or IPv6 prefix of the PPP user.
Detailed information about a PPP user includes the following:
· Brief name of the VA interface.
· User ID.
· Username.
· Authentication information.
· Uplink and downlink traffic.
· Access start time of the PPP user.
Examples
# Display brief information about PPP users on GigabitEthernet 1/0/1.
<Sysname> display ppp access-user interface gigabitethernet 1/0/1
Interface Username MAC address IP address IPv6 address IPv6 PDPrefix
VA0 user1@h3c 0001-0101-9101 192.168.100.173 - -
VA1 user2@h3c 0001-0101-9101 192.168.80.173 2000::1 -
# Display the total number of PPP users on GigabitEthernet 1/0/1.
<Sysname> display ppp access-user interface gigabitethernet 1/0/1 count
Total users: 2
Table 2 Command output
Field |
Description |
Interface |
Name of the VA interface corresponding to the user. |
Username of the user. A hyphen (-) means that the user does not need authentication. |
|
MAC address |
MAC address of the user. A hyphen (-) means that the user is not a PPPoE user. |
IP address |
IP address of the user. A hyphen (-) means that no IP address is assigned to the user. |
IPv6 address |
IPv6 address of the user. A hyphen (-) means that no IPv6 address is assigned to the user. |
IPv6 PDPrefix |
IPv6 prefix of the user. A hyphen (-) means that no IPv6 prefix is assigned to the user. |
Total users |
Total number of PPP users. |
# Display detailed information about the PPP user whose IP address is 50.50.50.3.
<Sysname> display ppp access-user ip-address 50.50.50.3
Basic:
Interface: VA0
User ID: 0x28000002
Username: user1@hrss
Domain: hrss
Access interface: RAGG2
Service-VLAN/Customer-VLAN: -/-
MAC address: 0000-0000-0001
IP address: 50.50.50.3
IPv6 address: -
IPv6 PD prefix: -
VPN instance: 123
Access type: PPPoE
Authentication type: CHAP
AAA:
Authentication state: Authenticated
Authorization state: Authorized
Realtime accounting switch: Open
Realtime accounting interval: 60s
Login time: 2013-1-19 2:42:3:358
Accounting start time: 2013-1-19 2:42:3:382
Accounting state: Accounting
Online time(hh:mm:ss): 0:7:34
Idle cut: 0 sec 0 byte
Session timeout: 12000s
Time remained: 8000s
Byte remained: 20971520 bytes
Redirect WebURL: http://6.6.6.6
ACL&QoS:
User profile: profile123 (active)
User group profile: -
Inbound CAR: CIR 64000bps PIR 640000bps CBS 500bit
Outbound CAR: CIR 64000bps PIR 640000bps CBS 500bit
NAT:
Global IP address: 111.8.0.200
Port block: 28744-28748
Flow Statistic:
IPv4 uplink packets/bytes: 7/546
IPv4 downlink packets/bytes: 0/0
IPv6 uplink packets/bytes: 0/0
IPv6 downlink packets/bytes: 0/0
ITA:
Level-1 uplink packets/bytes: 100/128000
downlink packets/bytes: 200/256000
Level-2 uplink packets/bytes: 100/128000
downlink packets/bytes: 200/256000
Table 3 Command output
Field |
Description |
Basic |
Basic information. |
Interface |
Brief name of the VA interface that corresponds to the user. |
Username |
Username of the user. A hyphen (-) means that the user does not need authentication. |
Domain |
ISP domain name for authentication. A hyphen (-) means that no ISP domain is specified for authentication. |
Access interface |
Name of the access interface of the user. |
Service-VLAN/Customer-VLAN |
Service provider VLAN and customer VLAN information of the user. A hyphen (-) means that no VLAN information is available. |
IP address |
IP address of the user. A hyphen (-) means that no IP address is assigned to the user. |
IPv6 address |
IPv6 address of the user. A hyphen (-) means that no IPv6 address is assigned to the user. |
IPv6 PD prefix |
Delegated IPv6 prefix of the user. A hyphen (-) means that no delegated IPv6 prefix is assigned to the user. |
VPN instance |
VPN instance to which the user belongs. A hyphen (-) means that the user is not bound to any VPN instance. |
Access type |
Access type of the user: · PPPoE. · PPPoA. · L2TP. |
Authentication type |
Authentication type of the user: · PAP. · CHAP. · MS-CHAP. · MS-CHAP-V2. |
Authentication state |
Authentication state of the user: · Idle—The user has not been authenticated. · Authenticating—The user is being authenticated. · Authenticated—The user has been authenticated. |
Authorization state |
Authorization state of the user: · Idle—The user has not been authorized. · Authorizing—The user is being authorized. · Authorized—The user has been authorized. |
Realtime accounting switch |
· Open—The switch is on. · Closed—The switch is off. |
Realtime accounting interval |
Realtime accounting interval in seconds. A hyphen (-) means that no real-time accounting interval is authorized. |
Login time |
Time when the user accessed the device through PPP. |
Accounting start time |
Time when accounting started. A hyphen (-) means that no accounting is performed on the user. |
Online time(hh:mm:ss) |
Online duration of the current login. |
Accounting state |
Accounting state of the user: · Accounting—Accounting is on. · Stop—Accounting stops. |
Idle cut |
Traffic threshold for logging off the user in idle state. If the traffic is less than the threshold within the specified period, the user is forcibly logged off. |
Session timeout |
Authorization time for the user, in seconds. A hyphen (-) means that no authorization time is specified for the user. |
Time remained |
Remaining time for the user to stay online, in seconds. A hyphen (-) means that no authorization time is specified for the user. |
Byte remained |
Remaining traffic for the user. A hyphen (-) means that no authorization traffic is specified for the user. |
Redirect WebURL |
Redirect Web URL address for the user. A hyphen (-) means that no redirect Web URL address is specified for the user. |
User profile |
Name of the authorized user profile. The hyphen (-) means that no user profile is authorized. The user profile has two states: · active—The authorized user profile is successfully issued. · inactive—The authorized user profile fails to be issued. |
User group profile |
Name of the authorized user group profile. The hyphen (-) means that no user group profile is authorized. The user group profile has two states: · active—The authorized user group profile is successfully issued. · inactive—The authorized user group profile fails to be issued. |
Inbound CAR |
Authorized inbound CARs, which contain the CIR and the PIR in bps and the CBS in bits. |
Outbound CAR |
Authorized outbound CARs, which contain the CIR and the PIR in bps and the CBS in bits. |
Global IP address |
Global IP address of the user. This field is displayed if NAT444 is used. For information about NAT444, see Layer 3—IP Services Configuration Guide. |
Port block |
Port block of the user, from the start port to the end port. This field is displayed if NAT444 is used. |
IPv4 uplink packets/bytes |
Number of packets and bytes for IPv4 uplink traffic. |
IPv4 downlink packets/bytes |
Number of packets and bytes for IPv4 downlink traffic. |
IPv6 uplink packets/bytes |
Number of packets and bytes for IPv6 uplink traffic. |
IPv6 downlink packets/bytes |
Number of packets and bytes for IPv6 downlink traffic. |
ITA |
ITA statistics. ITA statistics are displayed after ITA is enabled. If the traffic-separate enable command is configured, ITA statistics are not included in flow statistics. For information about ITA and the traffic-separate enable command, see Security Configuration Guide. |
Level-n uplink packets/bytes downlink packets/bytes |
Number of packets and bytes for uplink traffic at accounting level n. The value for n depends on the traffic level command, and its value range is 1 to 8. |
Related commands
reset ppp access-user
display ppp compression iphc
Use display ppp compression iphc to display IP header compression (IPHC) statistics.
Syntax
display ppp compression iphc { rtp | tcp } [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
rtp: Displays IPHC RTP header compression statistics.
tcp: Displays IPHC TCP header compression statistics.
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify this option, the command displays IPHC statistics on all interfaces.
Usage guidelines
When IPHC applies to an MP link:
· If an MP template is used, such as a VT interface or a dialer interface, the associated VA interface performs IPHC. You can view the compression information on the VA interface.
· If an MP-group interface is used, the MP-group interface performs IPHC. You can view the compression information on the MP-group interface.
When IPHC applies to a normal PPP link, the physical interface performs IPHC. You can view the compression information on the physical interface.
Examples
# Display IPHC RTP header compression statistics.
<Sysname> display ppp compression iphc rtp
----------------------Slot1----------------------
Interface: Virtual-Access0
Received:
Compressed/Error/Total: 0/0/0 packets
Sent:
Compressed/Total: 0/0 packets
Sent/Saved/Total: 0/0/0 bytes
Packet-based compression ratio: 0%
Byte-based compression ratio: 0%
Connections:
Rx/Tx: 16/16
Five-Minute-Miss: 0 (Misses/5Mins)
Max-Miss: 0
# Display IPHC TCP header compression statistics.
<Sysname>display ppp compression iphc tcp
----------------------Slot1----------------------
Interface: Virtual-Access0
Received:
Compressed/Error/Total: 0/0/0 packets
Sent:
Compressed/Total: 0/0 packets
Sent/Saved/Total: 0/0/0 bytes
Packet-based compression ratio: 0%
Byte-based compression ratio: 0%
Connections:
Rx/Tx: 16/16
Five-Minute-Miss: 0 (Misses/5Mins)
Max-Miss: 0
Table 4 Command output
Field |
Description |
Received: Compressed/Error/Total |
Statistics for received packets: · Compressed—Number of compressed packets. · Error—Number of error packets. · Total—Total number of received packets. |
Sent: Compressed/Total Sent/Saved/Total Packet-based compression ratio Byte-based compression ratio |
Statistics for sent packets: · Compressed—Number of compressed packets. · Total—Total number of sent packets. · Sent—Bytes of sent packets. · Saved—Bytes of saved packets. · Total—Total bytes to be sent if packets are not compressed. · Packet-based compression ratio—Ratio of compressed packets to the total sent packets. · Byte-based compression ratio—Ratio of saved bytes to the total sent bytes. |
Connections: Rx/Tx Five-Minute-Miss Max-Miss |
Number of connections. · Rx—Number of connections that the receiver can decompress. · Tx—Number of connections that the sender can compress. · Five-Minute-Miss—Number of search failures within the last 5 minutes. · Max-Miss—Maximum number of search failures within 5 minutes. |
Related commands
ppp compression iphc enable
reset ppp compression iphc
ip address ppp-negotiate
Use ip address ppp-negotiate to enable IP address negotiation on an interface, so that the interface can accept the IP address allocated by the server.
Use undo ip address ppp-negotiate to restore the default.
Syntax
ip address ppp-negotiate
undo ip address ppp-negotiate
Default
IP address negotiation is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
If you execute the ip address ppp-negotiate and ip address commands multiple times, the most recent configuration takes effect.
Examples
# Enable IP address negotiation on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ip address ppp-negotiate
ip address (Layer 3—IP Services Command Reference)
remote address
ip pool
Use ip pool to configure a PPP address pool.
Use undo ip pool to remove a PPP address pool or an IP address range of the PPP address pool.
Syntax
ip pool pool-name start-ip-address [ end-ip-address ] [ group group-name ]
undo ip pool pool-name [ start-ip-address [ end-ip-address ] ]
Default
No PPP address pool is configured.
Views
System view
Predefined user roles
network-admin
Parameters
pool-name: Specifies a name for the PPP address pool to be created, a case-sensitive string of 1 to 31 characters.
start-ip-address [ end-ip-address ]: Specifies an IP address range. If you do not specify the end-ip-address argument, the PPP address pool has only the start IP address.
group group-name: Specifies a group by its name to which the PPP address pool belongs. The group name is a case-sensitive string of 1 to 31 characters. If you do not specify this option, the group name is default (the default group).
Usage guidelines
The system supports multiple address spaces that each correspond to a VPN instance. The same IP addresses can exist in different address spaces.
Each address space is represented by a group. One group can contain multiple PPP address pools, but one PPP address pool can belong to only one group.
One PPP address pool can contain multiple IP address ranges. You can execute this command multiple times to specify multiple IP address ranges for a PPP address pool. A PPP address pool can contain a maximum of 65535 IP addresses, and so can an IP address range.
IP address ranges in different groups can be overlapping, but those in the same group cannot.
Changes to a PPP address pool do not affect assigned IP addresses. For example, if you delete a PPP address pool from which an IP address has been assigned, the IP address can still be used.
When assigning IP address to users through a PPP address pool, make sure the PPP address pool excludes the gateway IP address of the PPP address pool.
Examples
# Configure PPP address pool aaa that contains IP addresses 129.102.0.1 through 129.102.0.10 for group a.
<Sysname> system-view
[Sysname] ip pool aaa 129.102.0.1 129.102.0.10 group a
Related commands
display ip pool
ip pool gateway
Use ip pool gateway to configure a gateway address for a PPP address pool.
Use undo ip pool gateway to remove the gateway address for the specified PPP address pool.
Syntax
ip pool pool-name gateway ip-address [ vpn-instance vpn-instance-name ]
undo ip pool pool-name gateway
Default
A PPP address pool is not configured with a gateway address.
Views
System view
Predefined user roles
network-admin
Parameters
pool-name: Specifies an existing PPP address pool by its name, a case-sensitive string of 1 to 31 characters.
ip-address: Specifies a gateway address for the PPP address pool.
vpn-instance vpn-instance-name: Specifies an existing MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the specified gateway belongs to the public network.
Usage guidelines
The IP pool gateway setting takes precedence over the DHCP pool gateway setting.
An interface on a BRAS must have an IP address before it can assign an IP address from a PPP or DHCP address pool to a client. This command enables interfaces that have no IP address to use a gateway address for IPCP negotiation and address allocation.
When you configure a gateway address for a PPP address pool, follow these restrictions and guidelines:
· If you also specify an IP address for an interface, the interface uses its own IP address to perform IPCP negotiation.
· You can specify only one gateway address for a PPP address pool. Different PPP address pools must have different gateway addresses (different combinations of ip-address and vpn-instance-name).
· You can specify any gateway address for a PPP address pool.
Examples
# Specify gateway address 1.1.1.1 and VPN instance test for PPP address pool aaa.
<Sysname> system-view
[Sysname] ip pool aaa gateway 1.1.1.1 vpn-instance test
Related commands
ip pool
link-protocol ppp
Use link-protocol ppp to enable PPP encapsulation on an interface.
Syntax
link-protocol ppp
Default
PPP encapsulation is enabled on all interfaces except Ethernet, VLAN, and ATM interfaces.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable PPP encapsulation on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol ppp
nas-port-type
Use nas-port-type to configure the nas-port-type attribute on a VT interface.
Use undo nas-port-type to restore the default.
Syntax
nas-port-type { 802.11 | adsl-cap | adsl-dmt | async | cable | ethernet | g.3-fax | hdlc | idsl | isdn-async-v110 | isdn-async-v120 | isdn-sync | piafs | sdsl | sync | virtual | wireless-other | x.25 | x.75 | xdsl }
undo nas-port-type
Default
The nas-port-type attribute is determined by the service type and link type of the PPP user, as shown in Table 5.
Table 5 Default nas-port-type attribute
Service type |
Link type |
Nas-port-type attribute |
PPPoE |
Layer 3 virtual Ethernet interface |
xdsl |
Other interfaces |
ethernet |
|
PPPoA |
Any |
xdsl |
L2TP |
Any |
virtual |
Views
VT interface view
Predefined user roles
network-admin
Parameters
802.11: Specifies IEEE 802.11. The code value is 19.
adsl-cap: Specifies asymmetric DSL, Carrierless Amplitude Phase. The code value is 12.
adsl-dmt: Specifies asymmetric DSL, Discrete Multi-Tone. The code value is 13.
async: Specifies async. The code value is 0.
cable: Specifies cable. The code value is 17.
ethernet: Specifies Ethernet. The code value is 15.
g.3-fax: Specifies G.3 Fax. The code value is 10.
hdlc: Specifies HDLC Clear Channel. The code value is 7.
idsl: Specifies ISDN Digital Subscriber Line. The code value is 14.
isdn-async-v110: Specifies ISDN Async V.110. The code value is 4.
isdn-async-v120: Specifies ISDN Async V.120. The code value is 3.
isdn-sync: Specifies ISDN Sync. The code value is 2.
piafs: Specifies PHS Internet Access Forum Standard. The code value is 6.
sdsl: Specifies symmetric DSL. The code value is 11.
sync: Specifies sync. The code value is 1.
virtual: Specifies virtual. The code value is 5.
wireless-other: Specifies wireless–other. The code value is 18.
x.25: Specifies X.25. The code value is 8.
x.75: Specifies X.75. The code value is 9.
xdsl: Specifies Digital Subscriber Line of unknown type. The code value is 16.
Usage guidelines
The nas-port-type attribute is used for RADIUS authentication and accounting. For more information about the nas-port-type attribute, see RFC 2865.
Examples
# Set the nas-port-type attribute to sync for Virtual-Template 1.
<Sysname> system-view
[Sysname] interface virtual-template 1
[Sysname-Virtual-Template1] nas-port-type sync
ppp accm
Use ppp accm to set the ACCM value sent to the peer on an interface.
Use undo ppp accm to restore the default.
Syntax
ppp accm hex-number
undo ppp accm
Default
The ACCM value sent to the peer is 0x000A0000 on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
hex-number: Specifies an ACCM value in hexadecimal format, in the range of 0 to 0xFFFFFFFF.
Usage guidelines
ACCM negotiation only applies to asynchronous links.
Examples
# Set the ACCM value sent to the peer to 0x01010101 on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp accm 01010101
ppp account-statistics enable
Use ppp account-statistics enable to enable PPP accounting on an interface.
Use undo ppp account-statistics enable to disable PPP accounting on an interface.
Syntax
ppp account-statistics enable [ acl { acl-number | name acl-name } ]
undo ppp account-statistics enable
Default
PPP accounting is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
acl: Specifies an ACL to match traffic. If no ACL is specified, the device generates statistics for all PPP traffic.
acl-number: Specifies an ACL by its number in the range of 2000 to 3999, where:
· 2000 to 2999 are numbers for basic IPv4 and IPv6 ACLs.
· 3000 to 3999 are numbers for advanced IPv4 and IPv6 ACLs.
If the specified ACL number corresponds to an IPv4 ACL and an IPv6 ACL, both ACLs take effect.
name acl-name: Specifies an ACL by its name, a case-insensitive string of 1 to 63 characters that start with an alphabetical character. To avoid confusion, do not use all as an ACL name.
Examples
# Enable PPP accounting on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp account-statistics enable
ppp acfc local-request
Use ppp acfc local-request to configure an interface to send ACFC requests by including the ACFC option in outbound LCP negotiation requests.
Use undo ppp acfc local-request to restore the default.
Syntax
ppp acfc local-request
undo ppp acfc local-request
Default
An interface does not include the ACFC option in outbound LCP negotiation requests.
Views
Interface view
Predefined user roles
network-admin
Examples
# Configure Serial 2/1/0 to send ACFC requests to the peer in PPP negotiation.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp acfc local-request
ppp acfc remote-reject
Use ppp acfc remote-reject to configure an interface to reject ACFC requests received from the remote peer.
Use undo ppp acfc remote-reject to restore the default.
Syntax
ppp acfc remote-reject
undo ppp acfc remote-reject
Default
An interface accepts ACFC requests received from the remote peer, and it performs ACFC on frames sent to the peer.
Views
Interface view
Predefined user roles
network-admin
Examples
# Configure Serial 2/1/0 to reject ACFC requests received from the remote peer.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp acfc remote-reject
ppp authentication-mode
Use ppp authentication-mode to configure PPP authentication on an interface.
Use undo ppp authentication-mode to restore the default.
Syntax
ppp authentication-mode { chap | ms-chap | ms-chap-v2 | pap } * [ [ call-in ] domain { isp-name | default enable isp-name } ]
undo ppp authentication-mode
Default
PPP authentication is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
chap: Uses CHAP authentication.
ms-chap: Uses MS-CHAP authentication.
ms-chap-v2: Uses MS-CHAP-V2 authentication.
pap: Uses PAP authentication.
call-in: Authenticates the call-in users only. This keyword can be configured when the local end acts as the receiving end of DDR calls. For more information about DDR, see Layer 2—WAN Access Configuration Guide.
domain isp-name: Specifies the ISP domain name for authentication, a case-insensitive string of 1 to 255 characters.
default enable isp-name: Specifies the default ISP domain name for authentication, a case-insensitive string of 1 to 255 characters.
Usage guidelines
PPP authentication includes the following categories:
· PAP—Two-way handshake authentication. The password is in plain text or cipher text.
· CHAP—Three-way handshake authentication. The password is in plain text or cipher text.
· MS-CHAP—Three-way handshake authentication. The password is in cipher text.
· MS-CHAP-V2—Three-way handshake authentication. The password is in cipher text.
You can configure multiple authentication modes.
In any PPP authentication mode, AAA determines whether a user can pass the authentication through a local authentication database or an AAA server. For more information about AAA authentication, see Security Configuration Guide.
If you configure the ppp authentication-mode command with the domain keyword specified, you must perform the following tasks:
· Use the specified ISP domain to authenticate the peer.
· Use a PPP address pool associated with this ISP domain for address allocation (if necessary).
You can use the display domain command to display the domain configuration.
The system can obtain ISP domains through multiple ways during user authentication. The system chooses one of the following ISP domains for authentication in descending priority order:
· ISP domain specified by the domain isp-name option. Use a PPP address pool associated with this ISP domain for address allocation (if necessary). You can use the display domain command to display the domain configuration.
· ISP domain contained in the username. If the ISP domain does not exist on the local device, the user's access request is denied.
· ISP domain specified by the default enable isp-name option.
· Default ISP domain in the system. You can use the domain default command to configure the default ISP domain. If no default ISP domain is configured, the default ISP domain (system) is used.
For authentication on a dialup interface, configure authentication on both the physical interface and the dialer interface. When a physical interface receives a DDR call request, it first initiates PPP negotiation and authenticates the dial-in user. Then it passes the call to the upper layer protocol.
Examples
# Configure Serial 2/1/0 to authenticate the peer by using PAP.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp authentication-mode pap
# Configure Serial 2/1/0 to authenticate the peer by using PAP, CHAP, and MS-CHAP.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp authentication-mode pap chap ms-chap
domain default (Security Command Reference)
local-user (Security Command Reference)
ppp chap password
ppp chap user
ppp pap local-user
ppp chap password
Use ppp chap password to set the password for CHAP authentication on an interface.
Use undo ppp chap password to restore the default.
Syntax
ppp chap password { cipher | simple } string
undo ppp chap password
Default
No password is set for CHAP authentication on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the password. Its plaintext form is a case-sensitive string of 1 to 255 characters. Its encrypted form is a case-sensitive string of 1 to 97 characters.
Examples
# Set the password for CHAP authentication to plaintext password sysname on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp chap password simple sysname
ppp authentication-mode chap
ppp chap user
Use ppp chap user to set the username for CHAP authentication on an interface.
Use undo ppp chap user to restore the default.
Syntax
ppp chap user username
undo ppp chap user
Default
The username for CHAP authentication is null on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
username: Specifies the username for CHAP authentication, a case-sensitive string of 1 to 80 characters. The username is sent to the peer for the local device to be authenticated.
Usage guidelines
To pass CHAP authentication, the username/password of one side must be the local username/password on the peer.
Examples
# Set the username for CHAP authentication to Root on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp chap user Root
ppp authentication-mode chap
ppp compression iphc enable
Use ppp compression iphc enable to enable IPHC on an interface.
Use undo ppp compression iphc enable to disable IPHC on an interface.
Syntax
ppp compression iphc enable [ nonstandard ]
undo ppp compression iphc enable
Default
IPHC is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
nonstandard: Specifies the nonstandard encapsulation format. If you do not specify this keyword, packets are encapsulated in standard format. You must specify this keyword when the device communicates with a non-H3C device. If you specify this keyword, this command enables RTP header compression.
Usage guidelines
IPHC includes RTP header compression and TCP header compression.
Enabling or disabling IPHC enables or disables both RTP header compression and TCP header compression.
To use IPHC, you must enable it on both sides of a PPP link.
When you enable IPHC on a VT, dialer, or ISDN interface, the setting does not immediately take effect. For the setting to take effect, execute the shutdown and then undo shutdown commands on the interface or its bound physical interface.
Examples
# Enable IPHC on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp compression iphc enable
ppp compression iphc rtp-connections
Use ppp compression iphc rtp-connections to set the maximum number of connections for which an interface can perform RTP header compression.
Use undo ppp compression iphc rtp-connections to restore the default.
Syntax
ppp compression iphc tcp-connections number
undo ppp compression iphc tcp-connections
Default
An interface can perform RTP header compression for a maximum of 16 connections.
Views
Interface view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of connections for which an interface can perform RTP header compression. The value range for this argument is 3 to 1000:
· When the number argument is set to a value less than or equal to 256, packets are compressed in the format of COMPRESSED RTP 8.
· When the number argument is set to a value greater than 256, packets are compressed in the format of COMPRESSED RTP 16.
Usage guidelines
RTP is a connection-oriented protocol. An interface can accommodate multiple RTP connections.
RTP header compression occupies memory resources for maintaining connection information. This command can limit memory resources used by compression. For example, if you set the limit to 3, RTP header compression only applies to a maximum of three RTP connections.
After you execute this command, you must shut down and then bring up the interface to make the command take effect.
You can configure this command only when IPHC is enabled. The configuration is removed after IPHC is disabled.
Examples
# Set the maximum number of connections for which Serial 2/1/0 can perform RTP header compression to 10.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp compression iphc enable
[Sysname-Serial2/1/0] ppp compression iphc rtp-connections 10
Related commands
ppp compression iphc tcp-connections
Use ppp compression iphc tcp-connections to set the maximum number of connections for which an interface can perform TCP header compression.
Use undo ppp compression iphc tcp-connections to restore the default.
Syntax
ppp compression iphc tcp-connections number
undo ppp compression iphc tcp-connections
Default
An interface can perform TCP header compression for a maximum of 16 connections.
Views
Interface view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of connections for which an interface can perform TCP header compression. The value range for this argument is 3 to 256.
Usage guidelines
TCP is a connection-oriented protocol. A link can accommodate multiple TCP connections.
TCP header compression occupies memory resources for maintaining connection information. This command can limit memory resources used by compression. For example, if you set the limit to 3, TCP header compression only applies to a maximum of three TCP connections.
After you execute this command, you must shut down and then bring up the interface to make the command take effect.
You can configure this command only when IPHC is enabled and packets are encapsulated in standard format. The configuration is removed after IPHC is disabled or packets are encapsulated in nonstandard format.
Examples
# Set the maximum number of connections for which Serial 2/1/0 can perform TCP header compression to 10.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp compression iphc enable
[Sysname-Serial2/1/0] ppp compression iphc tcp-connections 10
Related commands
ppp compression iphc enable
ppp ipcp dns
Use ppp ipcp dns to configure the primary and secondary DNS server IP addresses to be allocated in PPP negotiation on an interface.
Use undo ppp ipcp dns to delete the primary and secondary DNS server IP addresses to be allocated in PPP negotiation on an interface.
Syntax
ppp ipcp dns primary-dns-address [ secondary-dns-address ]
undo ppp ipcp dns primary-dns-address [ secondary-dns-address ]
Default
The DNS server IP addresses to be allocated in PPP negotiation are not configured on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
primary-dns-address: Specifies a primary DNS server IP address.
secondary-dns-address: Specifies a secondary DNS server IP address.
Usage guidelines
A device can assign DNS server IP addresses to its peer during PPP negotiation when the peer initiates requests.
To check the allocated DNS server IP addresses, execute the winipcfg or ipconfig /all command on the host.
Examples
# Set the primary and secondary DNS server IP addresses to 100.1.1.1 and 100.1.1.2 for the peer on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp ipcp dns 100.1.1.1 100.1.1.2
ppp ipcp dns admit-any
Use ppp ipcp dns admit-any to configure an interface to accept the DNS server IP addresses assigned by the peer even though it does not request DNS server IP addresses from the peer.
Use undo ppp ipcp dns admit-any to restore the default.
Syntax
ppp ipcp dns admit-any
undo ppp ipcp dns admit-any
Default
An interface does not accept the DNS server IP addresses assigned by the peer if it does not request DNS server IP addresses from the peer.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
You can configure an interface to accept the DNS server IP addresses assigned by the peer, through which domain names can be resolved for the device.
Typically, the server assigns a DNS server address to a client in PPP negotiation only when the client is configured with the ppp ipcp dns request command. Some servers, however, forcibly assign DNS server addresses to clients. You must configure the ppp ipcp dns admit-any command on the client devices to accept the DNS server addresses.
Examples
# Configure Serial 2/1/0 to accept DNS server IP addresses allocated by the peer.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp ipcp dns admit-any
Related commands
ppp ipcp dns request
ppp ipcp dns request
Use ppp ipcp dns request to enable an interface to actively request the DNS server IP address from its peer.
Use undo ppp ipcp dns request to restore the default.
Syntax
ppp ipcp dns request
undo ppp ipcp dns request
Default
An interface does not actively request the DNS server IP address from its peer.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
If a device is connected to a provider's access server through a PPP link, you can use this command. Then, the device can obtain the specified DNS server IP address from the access server during IPCP negotiation.
You can check the DNS server IP addresses by displaying information about the interface.
Examples
# Enable Serial 2/1/0 to actively request the DNS server IP address from its peer.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp ipcp dns request
ppp ipcp remote-address match
Use ppp ipcp remote-address match to enable the IP segment match feature for PPP IPCP negotiation on an interface.
Use undo ppp ipcp remote-address match to restore the default.
Syntax
ppp ipcp remote-address match
undo ppp ipcp remote-address match
Default
The IP segment match feature is disabled for PPP IPCP negotiation on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command enables the local interface to check whether its IP address and the IP address of the remote interface are in the same network segment. If they are not, IPCP negotiation fails.
Examples
# Enable the IP segment match feature on Virtual-Template 1.
<Sysname> system-view
[Sysname] interface virtual-template 1
[Sysname-Virtual-Template1] ppp ipcp remote-address match
ppp ip-pool route
Use ppp ip-pool route to configure a PPP address pool route.
Use undo ppp ip-pool route to remove a PPP address pool route.
Syntax
ppp ip-pool route ip-address { mask-length | mask } [ vpn-instance vpn-instance-name ]
undo ppp ip-pool route ip-address { mask-length | mask } [ vpn-instance vpn-instance-name ]
Default
No PPP address pool route is configured.
Views
System view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the destination IP address of the PPP address pool route, in dotted decimal notation.
mask-length: Specifies a mask length for the IP address, in the range of 0 to 32.
mask: Specifies a mask for the IP address, in dotted decimal notation.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the PPP address pool route applies to the public network.
Usage guidelines
The BRAS uses PPP address pool routes to control downlink traffic forwarding.
After you configure a PPP address pool route, the BRAS generates a static blackhole route destined for the specified network. All traffic matching the blackhole route is discarded. When a legal user logs in, the BRAS adds a host route destined for the specified network. In addition, the BRAS uses a dynamic routing protocol to redistribute the PPP address pool route to the upstream device.
Figure 1 Network diagram for the PPP address pool route
Make sure the destination network of the PPP address pool route includes the PPP address pool. You can execute this command multiple times to configure multiple PPP address pool routes.
Examples
# Configure the PPP address pool route as 2.2.2.2/24.
<Sysname> system-view
[Sysname] ppp ip-pool route 2.2.2.2 24
ppp lcp delay
Use ppp lcp delay to set the LCP negotiation delay timer.
Use undo ppp lcp delay to restore the default.
Syntax
ppp lcp delay milliseconds
undo ppp lcp delay
Default
PPP starts LCP negotiation immediately after the physical layer comes up.
Views
Interface view
Predefined user roles
network-admin
Parameters
milliseconds: Specifies the LCP negotiation delay timer in the range of 1 to 10000 milliseconds.
Usage guidelines
If two ends of a PPP link vary greatly in the LCP negotiation packet processing rate, configure this command on the end with a higher processing rate. The LCP negotiation delay timer prevents frequent LCP negotiation packet retransmissions. After the physical layer comes up, PPP starts LCP negotiation when the delay timer expires. If PPP receives LCP negotiation packets before the delay timer expires, it starts LCP negotiation immediately.
Examples
# Set the LCP negotiation delayer timer to 130 milliseconds.
<Sysname> system-view
[Sysname] interface virtual-template 1
[Sysname-Virtual-Template1] ppp lcp delay 130
ppp lqm
Use ppp lqm to enable PPP link quality Monitoring (LQM) on an interface.
Use undo ppp lqm to disable PPP LQM on an interface.
Syntax
ppp lqm close-percentage close-percentage [ resume-percentage resume-percentage ]
undo ppp lqm
Default
PPP LQM is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
close-percentage close-percentage: Specifies the PPP LQM close percentage in the range of 0 to 100.
resume-percentage resume-percentage: Specifies the PPP LQM resume percentage in the range of 0 to 100. The resume percentage must be greater than or equal to the close percentage. The default resume percentage is equal to the close percentage.
Usage guidelines
If you enable PPP LQM on both sides of a PPP link, make sure both sides have the same PPP LQM settings. Typically, there is no need to enable PPP LQM on both sides of a PPP link.
As a best practice, do not enable PPP LQM on a DDR dial-up link because DDR tears the link down when the link is closed by LQM. Then LQM cannot send LQR packets to resume the link.
Examples
# Enable PPP LQM on Serial 2/1/0, and set the PPP LQM close percentage to 90 and resume percentage to 95.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp lqm close-percentage 90 resume-percentage 95
ppp lqm lcp-echo
Use ppp lqm lcp-echo to configure an interface to periodically send LCP echo packets when LQM detects a low quality link.
Use undo ppp lqm lcp-echo to restore the default.
Syntax
ppp lqm lcp-echo [ packet size ] [ interval interval ]
undo ppp lqm lcp-echo
Default
An interface does not send LCP echo packets when LQM detects a low quality link.
Views
Interface view
Predefined user roles
network-admin
Parameters
packet size: Specifies the size added for the LCP echo packet, in the range of 128 to 1500 bytes.
interval interval: Specifies the interval for sending LCP echo packets, in the range of 1 to 10 seconds.
Usage guidelines
This feature can avoid PPP link flapping caused by loss of large LCP packets.
Examples
# Configure Serial2/1/0 to send a LCP echo packet every 1 second. The LCP echo packet is 1400 bytes larger than the original length.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp lqm lcp-echo packet 1400 interval 1
ppp pap local-user
Use ppp pap local-user to set the local username and password for PAP authentication on an interface.
Use undo ppp pap local-user to restore the default.
Syntax
ppp pap local-user username password { cipher | simple } string
undo ppp pap local-user
Default
The local username and password for PAP authentication are blank on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
username: Specifies the username of the local device for PAP authentication, a case-sensitive string of 1 to 80 characters.
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the password. Its plaintext form is a case-sensitive string of 1 to 255 characters. Its encrypted form is a case-sensitive string of 1 to 373 characters.
Usage guidelines
For the local device to pass PAP authentication on the peer, make sure the username and password configured for the local device are also configured on the peer. You can configure the peer's username and password by using the local-user username and password { cipher | simple } string commands, respectively.
Examples
# Set the local username and password for PAP authentication to user1 and plaintext pass1 on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp pap local-user user1 password simple pass1
local-user (Security Command Reference)
password (Security Command Reference)
ppp pfc local-request
Use ppp pfc local-request to configure an interface to send PFC requests by including the PFC option in outbound LCP negotiation requests.
Use undo ppp pfc local to restore the default.
Syntax
ppp pfc local-request
undo ppp pfc local-request
Default
An interface does not include the PFC option in outbound LCP negotiation requests.
Views
Interface view
Predefined user roles
network-admin
Examples
# Configure Serial 2/1/0 to send PFC requests during PPP negotiation.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp pfc local-request
ppp pfc remote-reject
Use ppp pfc remote-reject to configure an interface to reject PFC requests received from the remote peer.
Use undo ppp pfc remote to restore the default.
Syntax
ppp pfc remote-reject
undo ppp pfc remote-reject
Default
An interface accepts PFC requests received from the remote peer, and it performs PFC on frames sent to the peer.
Views
Interface view
Predefined user roles
network-admin
Examples
# Configure Serial 2/1/0 to reject PFC requests received from the remote peer.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp pfc remote-reject
ppp timer negotiate
Use ppp timer negotiate to set the PPP negotiation timeout time on an interface.
Use undo ppp timer negotiate to restore the default.
Syntax
ppp timer negotiate seconds
undo ppp timer negotiate
Default
The PPP negotiation timeout time is 3 seconds on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the negotiation timeout time in the range of 1 to 10 seconds.
Usage guidelines
In PPP negotiation, if the local device receives no response from the peer during the timeout time after it sends a packet, the local device sends the last packet again.
Examples
# Set the PPP negotiation timeout time to 5 seconds on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp timer negotiate 5
remote address
Use remote address to configure an interface to assign an IP address to the client.
Use undo remote address to restore the default.
Syntax
remote address { ip-address | pool pool-name }
undo remote address
Default
An interface does not assign an IP address to the client.
Views
Interface view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the IP address to be assigned to the client.
pool pool-name: Specifies a PPP or DHCP address pool by its name from which an IP address is assigned to the client. The pool name is a case-sensitive string of 1 to 31 characters.
Usage guidelines
This command can be used when the local interface is configured with an IP address, but the peer has no IP address. To enable the peer to accept the IP address assigned by the local interface (server), you must configure the ip address ppp-negotiate command on the peer to make the peer act as a client.
This command enables the local interface to forcibly assign an IP address to the peer. If the peer is not configured with the ip address ppp-negotiate command but configured with an IP address, the peer will not accept the assigned IP address. This results in an IPCP negotiation failure.
PPP supports IP address assignment from a PPP or DHCP address pool, but the PPP address pool takes precedence over the DHCP address pool. For example, if you use a pool name that identifies both a PPP address pool and a DHCP address pool, the system uses only the PPP address pool for address assignment.
To make the configuration of the remote address command take effect, configure this command before the ip address command, which triggers IPCP negotiation. If you configure the remote address command after the ip address command, the server assigns an IP address to the client during the next IPCP negotiation.
After you use the remote address command to assign an IP address to the client, you can configure the remote address command again or the undo remote address command for the peer. However, the new configuration does not take effect until the next IPCP negotiation.
Examples
# Specify the IP address to be assigned to the client as 10.0.0.1 on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] remote address 10.0.0.1
# Configure Serial 2/1/0 to assign an IP address from address pool aaa to the client.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] remote address pool aaa
Related commands
ip address ppp-negotiate
ip pool
remote address dhcp client-identifier
Use remote address dhcp client-identifier username to use the PPP usernames as the DHCP client IDs.
Use undo remote address dhcp client-identifier to restore the default.
Syntax
remote address dhcp client-identifier username
undo remote address dhcp client-identifier
Default
The PPP usernames are not used as the DHCP client IDs.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command uses PPP usernames as DHCP client IDs for DHCP pool address assignment. The DHCP pool can be an AAA-authorized address pool or an address pool configured by using the remote address command.
Configure this command when different users use different PPP usernames to come online and PPP usernames are required to be used as DHCP client IDs.
Examples
# Use the PPP usernames as the DHCP client IDs on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] remote address dhcp client-identifier username
reset ppp compression iphc
Use reset ppp compression iphc to clear IPHC statistics.
Syntax
reset ppp compression iphc [ rtp | tcp ] [ interface interface-type interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
rtp: Clears IPHC RTP header compression statistics.
tcp: Clears IPHC TCP header compression statistics.
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify this option, the command clears IPHC statistics on all interfaces.
Usage guidelines
If neither rtp nor tcp is specified, this command clears both RTP header compression and TCP header compression statistics.
Examples
# Clear IPHC statistics on all interfaces.
<Sysname> reset ppp compression iphc
Related commands
display ppp compression iphc
timer-hold
Use timer-hold to set the keepalive interval on an interface.
Use undo timer-hold to restore the default.
Syntax
timer-hold seconds
undo timer-hold
Default
The keepalive interval is 10 seconds on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval for sending keepalive packets, in the range of 0 to 32767 seconds. The value 0 disables keepalive packet sending. In this case, the interface can respond to keepalive packets from the peer.
Usage guidelines
An interface sends keepalive packets at keepalive intervals to detect the availability of the peer. If the interface receives no response to keepalive packets when the keepalive retry limit is reached, it considers the link faulty and reports a link layer down event.
To set the keepalive retry limit, use the timer-hold retry command.
On a slow link, increase the keepalive interval to prevent false shutdown of the interface. This situation might occur when keepalive packets are delayed because a large packet is being transmitted on the link.
Examples
# Set the keepalive interval to 20 seconds on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] timer-hold 20
Related commands
timer-hold retry
timer-hold retry
Use timer-hold retry to set the keepalive retry limit on an interface.
Use undo timer-hold retry to restore the default.
Syntax
timer-hold retry retries
undo timer-hold retry
Default
The keepalive retry limit is 5 on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
retries: Specifies the maximum number of keepalive attempts in the range of 1 to 255.
Usage guidelines
An interface sends keepalive packets at keepalive intervals to detect the availability of the peer. If the interface receives no response to keepalive packets when the keepalive retry limit is reached, it considers the link faulty and reports a link layer down event.
To set the keepalive interval, use the timer-hold command.
On a slow link, increase the keepalive retry limit to prevent false shutdown of the interface. This situation might occur when keepalive packets are delayed because a large packet is being transmitted on the link.
Examples
# Set the keepalive retry limit to 10 for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] timer-hold retry 10
Related commands
timer-hold
reset ppp access-user
Use reset ppp access-user to log off a PPP user.
Syntax
reset ppp access-user { ip-address ipv4-address [ vpn-instance ipv4-vpn-instance-name ] | ipv6-address ipv6-address [ vpn-instance ipv6-vpn-instance-name ] | username user-name }
Views
User view
Predefined user roles
network-admin
Parameters
ip-address ipv4-address: Specifies a PPP user by its IPv4 address.
ipv6-address ipv6-address: Specifies a PPP user by its IPv6 address.
vpn-instance ipv4-vpn-instance-name: Specifies a PPP user by the VPN to which the user belongs. The ipv4-vpn-instance-name argument specifies the name of the IPv4 MPLS L3VPN instance, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the specified user belongs to the public network.
vpn-instance ipv6-vpn-instance-name: Specifies a PPP user by the VPN to which the user belongs. The ipv6-vpn-instance-name argument specifies the name of the IPv6 MPLS L3VPN instance, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the specified user belongs to the public network.
username user-name: Specifies a PPP user by username, a case-sensitive string of 1 to 80 characters.
Usage guidelines
This command takes effect only on the current login for a PPP user. The user can come online after it is logged off.
Examples
# Log off the PPP user at 192.168.100.2.
<Sysname> reset ppp access-user ip-address 192.168.100.2
Related commands
display ppp access-user
MP 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
MP-group interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth of an interface affects the link costs in OSPF, OSPFv3, and IS-IS. For more information, see Layer 3—IP Routing 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
# Set the expected bandwidth of MP-group 2/0/0 to 1000 kbps.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] bandwidth 1000
default
Use default to restore the default settings for a VT or MP-group interface.
Syntax
default
Views
VT interface view
MP-group 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
# Restore the default settings of MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-Mp-group2/0/0] default
description
Use description to set the description for a VT or MP-group interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description for a VT or MP-group interface is interface name Interface (for example, Virtual-Template1 Interface or MP-group2/0/0 Interface).
Views
VT interface view
MP-group 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
# Set the description for MP-group 2/0/0 to mpgroup-interface.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] description mpgroup-interface
display interface mp-group
Use display interface mp-group to display information about a specified MP-group interface or all MP-group interfaces.
Syntax
display interface [ mp-group [ interface-number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-number: Specifies an existing MP-group interface by its number in the range of 0 to 1023. (Centralized devices in standalone mode.)
interface-number: Specifies an existing MP-group interface by its number in the format of X/Y/Z. X represents the slot number of the physical interface, in the range of 0 to 2. The value of Y is fixed at 0. Z represents the number of the MP-group interface, in the range of 0 to 1023. (Distributed devices in standalone mode.)
interface-number: Specifies an existing MP-group interface by its number in the format of X/Y/Z. X represents the member ID of the IRF member device to which the physical interface belongs, in the range of 1 to 2. The value of Y is fixed at 0. Z represents the number of the MP-group interface, in the range of 0 to 1023. (Centralized devices in IRF mode.)
interface-number: Specifies an existing MP-group interface by its number in the format of R/X/Y/Z. R represents the member ID of the IRF member device to which the physical interface belongs, in the range of 1 to 2. X represents the slot number of the physical interface, in the range of 0 to 2. The value of Y is fixed at 0. Z represents the number of the MP-group interface, in the range of 0 to 1023. (Distributed devices in IRF mode.)
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface description. If you do not specify this keyword, the command displays only the first 27 characters of the interface description if the description contains more than 27 characters.
down: Displays information about interfaces in physically down state and the causes. If you do not specify this keyword, the command displays information about all interfaces.
Usage guidelines
If you do not specify the mp-group keyword, the command displays information about all interfaces on the device.
If you specify the mp-group keyword without the interface-number argument, the command displays information about all existing MP-group interfaces.
Examples
# Display detailed information about MP-group 2/0/0.
<Sysname> display interface mp-group 2/0/0
MP-group2/0/0
Current state: DOWN
Line protocol state: DOWN
Description: MP-group2/0/0 Interface
Bandwidth: 2048kbps
Maximum transmission unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet address: 192.168.1.200/24 (primary)
Link layer protocol: PPP
LCP: initial
Physical: MP, baudrate: 2048000 bps
Output queue - Urgent queuing: Size/Length/Discards 0/1024/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 drops
Output: 0 packets, 0 bytes, 0 drops
# Display brief information about MP-group 2/0/0.
<Sysname> display interface mp-group 12 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
MP2/0/0 DOWN DOWN --
# Display brief information about the MP-group interfaces in physically down state and the causes.
<Sysname> display interface mp-group brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
MP2/0/0 ADM Administratively
MP2/0/1 DOWN Not connected
Field |
Description |
Current state |
Physical and administrative states of the interface: · DOWN (Administratively)—The interface was administratively shut down with the shutdown command. · DOWN—The interface is administratively up but physically down (possibly because no physical link is present or the link is faulty). · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer state: UP or DOWN. |
Description |
Interface description. |
Bandwidth |
Expected bandwidth of the interface. |
Hold timer |
Interval at which the interface sends keepalive packets. |
retry times |
Keepalive retry limit. The interface determines that its peer has been down if it does not receive a keepalive response when the keepalive retry limit is reached. |
Internet protocol processing |
The interface cannot process IP packets currently. |
Internet address: 192.168.1.200/24 (primary) |
Primary IP address of the interface. |
LCP initial |
LCP negotiation is complete. |
Physical |
Physical type of the interface. |
baudrate |
Baud rate of the interface. |
Output queue - Urgent queuing: Size/Length/Discards 0/1024/0 Output queue - Protocol queuing: Size/Length/Discards 0/500/0 Output queue - FIFO queuing: Size/Length/Discards 0/75/0 |
Traffic statistics of the interface output queues. |
Last clearing of counters: Never |
Last time when statistics on the interface were cleared. Never indicates that statistics on the interface were never cleared. |
Last 300 seconds input rate: 0 bytes/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 packets/sec |
Average rate of input packets and output packets in the last 300 seconds. |
Input: 0 packets, 0 bytes, 0 drops |
Total number of inbound packets of the interface (in the number of packets and in bytes), and the number of dropped incoming packets. |
Output: 0 packets, 0 bytes, 0 drops |
Total number of outbound packets of the interface (in the number of packets and in bytes), and the number of dropped outgoing packets. |
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
Link: ADM - administratively down; Stby - standby |
Link status: · ADM—The interface has been administratively shut down. To recover its physical state, execute the undo shutdown command. · Stby—The interface is operating as a backup interface. To see the primary interface, use the display interface-backup state command in High Availability Command Reference. |
Protocol: (s) - spoofing |
Indicates the line protocol is UP, but the physical link is an on-demand link or is not present. |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been administratively shut down. To recover its physical state, use the undo shutdown command. · Stby—The interface is a backup interface. |
Protocol |
Line protocol state: · UP—The line protocol is up. · DOWN—The line protocol is down. · UP(s)—The line protocol is up, but the physical link is an on-demand link or is not present. |
Primary IP |
Primary IP address of the interface. |
Description |
Interface description configured by using the description command. If you do not specify the description keyword, the display interface brief command displays a maximum of 27 characters of the description. If you specify the description keyword, the command displays the complete description. |
Cause |
Causes for the physical state of the interface to be Down: · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). · Administratively—The interface was shut down with the shutdown command. To restore the physical state of the interface, use the undo shutdown command. |
Related commands
reset counters interface mp-group
display interface virtual-access
Use display interface virtual-access to display information about VA interfaces.
Syntax
display interface [ virtual-access [ interface-number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-number: Specifies a VA interface by its number.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays interface description information. This keyword does not apply to VA interfaces because VA interfaces do not support description configuration.
down: Displays information about interfaces in physically down state and the causes. If you do not specify this keyword, the command displays information about all interfaces.
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
MSR810-LM-GL |
Yes |
MSR810-W-LM-GL |
Yes |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR2600-6-X1-GL |
Yes |
MSR3600-28-SI-GL |
Yes |
If you do not specify the virtual-access keyword, the command displays information about all interfaces on the device.
If you specify the virtual-access keyword without the interface-number argument, the command displays information about all VA interfaces.
Examples
# Display information about Virtual-Access 1.
<Sysname> display interface virtual-access 1
Virtual-Access1
Current state: UP
Line protocol state: UP
Description: Virtual-Access1 Interface
Bandwidth: 1920kbps
Maximum transmission unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet address: 122.1.1.1/24 (primary)
Link layer protocol: PPP
LCP: opened, MP: opened, IPCP: opened
Physical: MP, baudrate: 1920000 bps
Main interface: Virtual-Template1
Output queue - Urgent queuing: Size/Length/Discards 0/1024/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 2 packets, 24 bytes, 0 drops
Output: 2 packets, 24 bytes, 0 drops
# Display brief information about Virtual-Access 1.
<Sysname> display interface virtual-access 1 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
VA1 DOWN DOWN --
# Display brief information about VA interfaces in physically down state and the causes.
<Sysname> display interface virtual-access brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
VA1 DOWN Not connected
Table 7 Command output
Field |
Description |
Current state |
Physical and administrative states of the interface: · DOWN—The interface is administratively up but physically down. · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer state: UP or DOWN. |
Description |
Interface description. |
Bandwidth |
Expected bandwidth of the interface. |
Hold timer |
Interval at which the interface sends keepalive packets. |
retry times |
Keepalive retry limit. The interface determines that its peer has been down if it does not receive a keepalive response when the keepalive retry limit is reached. |
Internet protocol processing: Disabled |
The interface cannot process IP packets currently. |
Internet address: 122.1.1.1/24 (primary) |
Primary IP address of the interface. |
LCP: opened, MP: opened, IPCP: opened |
The PPP connection has been successfully established. |
Physical |
Physical type of the interface. |
Main interface |
VT interface associated with the VA interface. |
Output queue - Urgent queuing: Size/Length/Discards 0/1024/0 Output queue - Protocol queuing: Size/Length/Discards 0/500/0 Output queue - FIFO queuing: Size/Length/Discards 0/75/0 |
Traffic statistics of the interface output queues. |
Last clearing of counters: Never |
Last time when statistics on the interface were cleared. Never indicates that statistics on the interface were never cleared. |
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec |
Average rate of input packets and output packets in the last 300 seconds. |
Input: 2 packets, 24 bytes, 0 drops |
Total number of inbound packets of the interface (in the number of packets and in bytes), and the number of packets dropped among the inbound packets. |
Output: 2 packets, 24 bytes, 0 drops |
Total number of outbound packets of the interface (in the number of packets and in bytes), and the number of packets dropped among the outbound packets. |
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
Link: ADM - administratively down; Stby - standby |
Link status: · ADM—The interface has been administratively shut down. To recover its physical state, execute the undo shutdown command. · Stby—The interface is a backup interface. To see the primary interface, use the display interface-backup state command in High Availability Command Reference. |
Protocol: (s) - spoofing |
Indicates the line protocol is UP, but the physical link is an on-demand link or is not present. |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. |
Protocol |
Line protocol state: · UP—The line protocol is up. · DOWN—The line protocol is down. · UP(s)—The line protocol is up, but the physical link is an on-demand link or is not present. |
Primary IP |
Primary IP address of the interface. |
Description |
Interface description configured by using the description command. This field does not apply to VA interfaces because VA interfaces do not support description configuration. |
Cause |
Cause for the physical state of the interface to be Down. Not connected indicates no physical link exists (possibly because the network cable is disconnected or faulty). |
Related commands
reset counters interface virtual-access
display interface virtual-template
Use display interface virtual-template to display information about VT interfaces.
Syntax
display interface [ virtual-template [ interface-number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-number: Specifies an existing VT interface by its number.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface description. If you do not specify this keyword, the command displays only the first 27 characters of the interface description if the description contains more than 27 characters.
down: Displays information about interfaces in physically down state and the causes. If you do not specify this keyword, the command displays information about all interfaces.
Usage guidelines
If you do not specify the virtual-template keyword, the command displays information about all interfaces on the device.
If you specify the virtual-template keyword without the interface-number argument, the command displays information about all existing VT interfaces.
Examples
# Display detailed information about Virtual-Template 1.
<Sysname> display interface virtual-template 1
Virtual-Template1
Current state: DOWN
Line protocol state: DOWN
Description: Virtual-Template1 Interface
Bandwidth: 100000kbps
Maximum transmission unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet address: 192.168.1.200/24 (primary)
Link layer protocol: PPP
LCP: initial
Physical: None, baudrate: 100000000 bps
Output queue - Urgent queuing: Size/Length/Discards 0/1024/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
# Display brief information about Virtual-Template 1.
<Sysname> display interface virtual-template 1 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
VT1 DOWN DOWN --
# Display brief information about the VT interfaces in physically down state and the causes.
<Sysname> display interface Virtual-Template brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
VT0 DOWN Not connected
VT12 DOWN Not connected
VT1023 DOWN Not connected
Table 8 Command output
Field |
Description |
Current state |
Physical state of the interface. This field for a VT interface can only be DOWN. |
Line protocol state |
Data link layer state. This field for a VT interface can only be DOWN. |
Description |
Interface description. |
Bandwidth |
Expected bandwidth of the interface. |
Hold timer |
Interval at which the interface sends keepalive packets. |
retry times |
Keepalive retry limit. The interface determines that its peer has been down if it does not receive a keepalive response when the keepalive retry limit is reached. |
Internet protocol processing: Disabled |
The interface cannot process IP packets currently. |
Internet address: 192.168.1.200/24 (primary) |
Primary IP address of the interface. |
LCP initial |
LCP initialization is complete. |
Physical |
Physical type of the interface. |
Output queue - Urgent queuing: Size/Length/Discards 0/1024/0) Output queue - Protocol queuing: Size/Length/Discards 0/500/0) Output queue - FIFO queuing: Size/Length/Discards 0/75/0) |
Traffic statistics of the interface output queues. |
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
Link: ADM - administratively down; Stby - standby |
Link status: · ADM—The interface has been administratively shut down. To recover its physical state, use the undo shutdown command. · Stby—The interface is operating as a backup interface. To see the primary interface, use the display interface-backup state command in High Availability Command Reference. |
Protocol: (s) - spoofing |
Indicates the line protocol is UP, but the physical link is an on-demand link or is not present. |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface. This field for a VT interface can only be DOWN. |
Protocol |
Line protocol state of the interface. This field for a VT interface can only be DOWN. |
Primary IP |
Primary IP address of the interface. |
Description |
Interface description configured by using the description command. If you do not specify the description keyword, the display interface brief command displays a maximum of 27 characters of the description. If you specify the description keyword, the command displays the complete description. |
Cause |
Causes for the physical state of the interface to be Down. Not connected indicates no physical link exists (possibly because the network cable is disconnected or faulty). |
display ppp mp
Use display ppp mp to display MP information for MP-group interfaces.
Syntax
display ppp mp [ interface interface-type interface-number ]
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its number. If you do not specify this option, the command displays MP information for all interfaces.
Examples
# Display MP information. (MP is configured through an MP-group interface.)
<Sysname> display ppp mp
Template: MP-group2/0/0
max-bind: 20, fragment: enabled, min-fragment: 128
Master link: MP-group2/0/0, Active members: 2, Bundle Multilink
Peer's endPoint descriptor: MP-group2/0/0
Sequence format: short (rcv)/long (sent)
Bundle Up Time: 2012/11/05 07:29:33:612
0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved
Sequence: 0 (rcv)/0 (sent)
Active member channels: 2 members
Serial2/1/0:15 Up-Time: 2012/11/05 07:29:33:613
Serial2/1/0:16 Up-Time: 2012/11/05 07:30:10:945
Inactive member channels: 2 members
Serial2/1/0:17
Serial2/1/0:18
Field |
Description |
max-bind |
Maximum number of links that can be bound. |
fragment |
Indicates whether MP fragmentation is enabled or disabled. |
min-fragment |
Minimum size of an MP fragment. |
Sequence format: short (rcv)/long (sent) |
Sequence number header format of MP. The short sequence number format is used in the incoming direction, and the long sequence number format is used in the outgoing direction. |
reordered |
Number of reassembled packets. |
unassigned |
Number of packets waiting for being reassembled. |
interleaved |
Number of interleaved fragments. LFI breaks larger packets into fragments and interleaves the fragments between smaller packets for transmission. |
Sequence: 0 (rcv)/0 (sent) |
Received sequence number/sent sequence number. |
Up-Time |
Uptime of a member channel. |
interface mp-group
Use interface mp-group to create an MP-group interface and enter its view, or enter the view of an existing MP-group interface.
Use undo interface mp-group to remove an MP-group interface.
Syntax
interface mp-group mp-number
undo interface mp-group mp-number
Default
No MP-group interfaces exists.
Views
System view
Predefined user roles
network-admin
Parameters
mp-number: Specifies an existing MP-group interface by its number in the range of 0 to 1023. (Centralized devices in standalone mode.)
mp-number: Specifies an existing MP-group interface by its number in the format of X/Y/Z. X represents the slot number of the physical interface, in the range of 0 to 2. The value of Y is fixed at 0. Z represents the number of the MP-group interface, in the range of 0 to 1023. (Distributed devices in standalone mode.)
mp-number: Specifies an existing MP-group interface by its number in the format of X/Y/Z. X represents the member ID of the IRF member device to which the physical interface belongs, in the range of 1 to 2. The value of Y is fixed at 0. Z represents the number of the MP-group interface, in the range of 0 to 1023. (Centralized devices in IRF mode.)
mp-number: Specifies an existing MP-group interface by its number in the format of R/X/Y/Z. R represents the member ID of the IRF member device to which the physical interface belongs, in the range of 1 to 2. X represents the slot number of the physical interface, in the range of 0 to 2. The value of Y is fixed at 0. Z represents the number of the MP-group interface, in the range of 0 to 1023. (Distributed devices in IRF mode.)
Usage guidelines
You must use the interface mp-group command together with the ppp mp mp-group command. You can execute the two commands in either order.
Examples
# Create interface MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0]
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 following matrix shows the value ranges for the number argument:
Hardware |
Value range |
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
0 to 1023 |
MSR2600-6-X1/2600-10-X1 |
0 to 1023 |
MSR 2630 |
0 to 1023 |
MSR3600-28/3600-51 |
0 to 1023 |
0 to 1023 |
|
MSR 3610 |
0 to 1023 |
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
0 to 2047 |
MSR 3620/3620-DP/3640/3660 |
0 to 2047 |
MSR5620/5660/5680 |
0 to 4095 |
Hardware |
Value range |
MSR810-LM-GL |
0 to 1023 |
MSR810-W-LM-GL |
0 to 1023 |
MSR830-6EI-GL |
0 to 1023 |
MSR830-10EI-GL |
0 to 1023 |
MSR830-6HI-GL |
0 to 1023 |
MSR830-10HI-GL |
0 to 1023 |
MSR2600-6-X1-GL |
0 to 1023 |
MSR3600-28-SI-GL |
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] 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 size of an interface is 1500 bytes.
Views
VT interface view
MP-group interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU size in the range of 128 to 1500 bytes.
Usage guidelines
The MTU size setting of an interface affects the fragmentation and reassembly of IP packets on that interface.
For the configured MTU size to take effect, you must execute the shutdown command and then the undo shutdown command on the interface.
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
# Set the MTU size of MP-group 2/0/0 to 1200 bytes.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] mtu 1200
ppp mp
Use ppp mp to enable MP for an interface.
Use undo ppp mp to disable MP on an interface.
Syntax
ppp mp
undo ppp mp
Default
An interface is enabled with PPP.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
To obtain more bandwidth, you can bind multiple PPP links to form a logical MP interface.
Examples
# Enable MP for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp mp
ppp mp binding-mode
Use ppp mp binding-mode to set the MP binding mode on an interface.
Use undo ppp mp binding-mode to restore the default.
Syntax
ppp mp binding-mode { authentication | both | descriptor }
undo ppp mp binding-mode
Default
Both the username and the descriptor are used for MP binding on an interface.
Views
VT interface view
Dialer interface view
Predefined user roles
network-admin
Parameters
authentication: Uses the username for MP binding.
both: Uses both the username and the endpoint descriptor for MP binding.
descriptor: Uses the endpoint descriptor for MP binding.
Usage guidelines
The username is obtained from the peer during PAP, CHAP, MS-CHAP, or MS-CHAP-V2 authentication. The endpoint descriptor, which uniquely identifies a device, is obtained from the peer during LCP negotiation. Based on the username or endpoint descriptor, the system can locate the corresponding VT interface and create an MP bundle according to the template.
The descriptor mode cannot differentiate users. To bind users to different bundles, use the both mode.
The authentication mode cannot differentiate peer devices. When multiple peer devices exist, use the both mode.
Examples
# Specify Virtual-Template 1 to use the username for MP binding.
<Sysname> system-view
[Sysname] interface virtual-template1
[Sysname-Virtual-Template1] ppp mp binding-mode authentication
ppp mp endpoint
Use ppp mp endpoint to set the endpoint option.
Use undo ppp mp endpoint to restore the default.
Syntax
ppp mp endpoint endpoint
undo ppp mp endpoint
Default
The endpoint option carries the device name on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
endpoint: Specifies the content of the endpoint option, a case-sensitive string of 1 to 20 characters.
Usage guidelines
The endpoint option (terminal descriptor) is negotiated during MP LCP negotiation.
When MP is configured by using a VT interface, an MP endpoint bases its link binding decisions on the remote endpoint descriptors, and assigns the links that receive the same endpoint descriptor to the same bundle. To avoid incorrect link binding on a VT interface, make sure the link descriptors used by different devices are unique. You must reconfigure an endpoint descriptor for a device if the default endpoint descriptor (device name) cannot uniquely identify the MP bundle at the remote end.
When MP is configured by using an MP-group interface, the negotiating endpoints do not base their binding decisions on the endpoint descriptor. By default, the endpoint descriptor of an interface in an MP-group is the MP-group interface name. If you configure an endpoint descriptor for the interface, the configured MP endpoint descriptor takes effect.
If the endpoint descriptor exceeds 20 bytes, the first 20 bytes are taken as the endpoint descriptor.
Examples
# Configure the endpoint descriptor of Serial 2/1/0 as 123456.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp mp endpoint 123456
ppp mp fragment disable
Use ppp mp fragment disable to disable MP fragmentation on an interface.
Use undo ppp mp fragment disable to enable MP fragmentation on an interface.
Syntax
ppp mp fragment disable
undo ppp mp fragment disable
Default
MP fragmentation is enabled on an interface.
Views
VT interface view
Dialer interface view
MP-group interface view
Predefined user roles
network-admin
Usage guidelines
If the peer device does not support fragment reassembly, you must configure the ppp mp fragment disable command to disable MP fragmentation on the local device. This enables the two devices to communicate. After that, outgoing packets are not fragmented, but they still carry an MP sequence number and fragment tag.
After you configure the ppp mp fragment disable command on an interface, the settings configured with the ppp mp lfi enable and ppp mp min-fragment commands do not take effect on the interface.
Examples
# Disable MP fragmentation on MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] ppp mp fragment disable
Related commands
ppp mp lfi enable
ppp mp min-fragment
ppp mp lfi delay-per-frag
Use ppp mp lfi delay-per-frag to set the maximum LFI fragment transmission delay on an interface.
Use undo ppp mp lfi delay-per-frag to restore the default.
Syntax
ppp mp lfi delay-per-frag time
undo ppp mp lfi delay-per-frag
Default
The maximum LFI fragment transmission delay is 10 ms on an interface.
Views
VT interface view
Dialer interface view
MP-group interface view
Predefined user roles
network-admin
Parameters
time: Specifies the maximum LFI fragment transmission delay, in the range of 1 to 1000 ms.
Examples
# Set the maximum LFI fragment transmission delay to 20 ms on MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] ppp mp lfi delay-per-frag 20
Related commands
ppp mp lfi enable
ppp mp lfi size-per-frag
ppp mp lfi enable
Use ppp mp lfi enable to enable LFI on an interface.
Use undo ppp mp lfi to disable LFI on an interface.
Syntax
ppp mp lfi enable
undo ppp mp lfi enable
Default
LFI is disabled on an interface.
Views
VT interface view
Dialer interface view
MP-group interface view
Predefined user roles
network-admin
Usage guidelines
Disabling LFI also removes the user-configured settings of the maximum LFI fragment transmission delay and size.
Examples
# Enable LFI on MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] ppp mp lfi enable
ppp mp lfi delay-per-frag
ppp mp lfi size-per-frag
ppp mp lfi size-per-frag
Use ppp mp lfi size-per-frag to set the maximum LFI fragment size (in bytes) on an interface.
Use undo ppp mp lfi size-per-frag to restore the default.
Syntax
ppp mp lfi size-per-frag size
undo ppp mp lfi size-per-frag
Default
On an interface, the maximum LFI fragment size is derived from this formula: (Expected bandwidth of the interface x Maximum LFI fragment transmission delay)/8.
Views
VT interface view
Dialer interface view
MP-group interface view
Predefined user roles
network-admin
Parameters
size: Specifies the maximum LFI fragment size in the range of 40 to 1500 bytes.
Usage guidelines
When LFI is enabled and both this command and the ppp mp lfi delay-per-frag command are configured, the maximum LFI fragment size is the value configured with the ppp mp lfi size-per-frag command.
Examples
# Set the maximum LFI fragment size to 80 bytes on MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] ppp mp lfi size-per-frag 80
Related commands
ppp mp lfi enable
ppp mp lfi delay-per-frag
ppp mp max-bind
Use ppp mp max-bind to set the maximum number of PPP links in an MP bundle on an interface.
Use undo ppp mp max-bind to restore the default.
Syntax
ppp mp max-bind max-bind-num
undo ppp mp max-bind
Default
The maximum number of PPP links in an MP bundle is 16 on an interface.
Views
VT interface view
Dialer interface view
MP-group interface view
Predefined user roles
network-admin
Parameters
max-bind-num: Specifies the maximum number of PPP links in an MP bundle, in the range of 1 to 128.
Usage guidelines
IMPORTANT: Use the default setting in most situations. Inappropriate use of this command can cause PPP performance degradation. Make sure you understand the impact of this command on your network before you use it. |
Set the maximum number of PPP links in an MP bundle to be greater than the actual number of bound links. Otherwise, MP binding fails.
The maximum number of PPP links configured for an MP bundle takes effect immediately. If the configured maximum number is smaller than the number of existing PPP links, the existing links are not affected.
Examples
# Set the maximum number of PPP links in an MP bundle to 12 on MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] ppp mp max-bind 12
ppp mp min-bind
Use ppp mp min-bind to set the minimum number of PPP links in an MP bundle on a dialer interface.
Use undo ppp mp min-bind to restore the default.
Syntax
ppp mp min-bind min-bind-num
undo ppp mp min-bind
Default
On a dialer interface, the minimum number of PPP links in an MP bundle is 0, which means that MP dial-up relies on traffic detection.
Views
Dialer interface view
Predefined user roles
network-admin
Parameters
min-bind-num: Specifies the minimum number of PPP links in an MP bundle, in the range of 0 to 128.
Usage guidelines
This command specifies the minimum number of PPP links in a MP bundle to ensure the minimum bandwidth for the service.
When the minimum number of PPP links is set to a non-zero value, subsequent MP dial-up operations will not depend on traffic detection, but existing dial-up connections will be removed upon timeout.
The min-bind-num argument cannot be greater than the maximum number set with the ppp mp max-bind command.
Examples
# Set the minimum number of PPP links in an MP bundle to 4 on Dialer 0.
<Sysname> system-view
[Sysname] interface dialer 0
[Sysname-Dialer0] ppp mp min-bind 4
Related commands
ppp mp max-bind
ppp mp min-fragment
Use ppp mp min-fragment to set the minimum MP packet fragmentation size on an interface.
Use undo ppp mp min-fragment to restore the default.
Syntax
ppp mp min-fragment size
undo ppp mp min-fragment
Default
The minimum MP packet fragmentation size is 128 bytes on an interface.
Views
VT interface view
Dialer interface view
MP-group interface view
Predefined user roles
network-admin
Parameters
size: Specifies the minimum MP packet fragmentation size in the range of 128 to 1500 bytes. Outgoing MP packets less than the minimum value will not be fragmented, and those greater than or equal to the minimum value will be fragmented.
Examples
# Set the minimum MP packet fragmentation size to 500 bytes on MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] ppp mp min-fragment 500
ppp mp mp-group
Use ppp mp mp-group to assign an interface to an MP group, and enable MP for the interface.
Use undo ppp mp to restore the default.
Syntax
ppp mp mp-group mp-number
undo ppp mp
Default
An interface is enabled with PPP.
Views
Interface view
Predefined user roles
network-admin
Parameters
mp-number: Specifies an MP-group interface by its number.
Usage guidelines
This command should be used with the interface mp-group command. You can create an MP group interface and then assign an interface to the MP group. You can also assign an interface to an MP group and then create the MP group.
Examples
# Assign Serial 2/1/0 to MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp mp mp-group 2/0/0
Related commands
interface mp-group
ppp mp short-sequence
Use ppp mp short-sequence to trigger MP short sequence number header format negotiation on an interface. After the negotiation succeeds, the local end receives packets with short sequence numbers.
Use undo ppp mp short-sequence to restore the default.
Syntax
ppp mp short-sequence
undo ppp mp short-sequence
Default
The long sequence number header format is used on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command applies to the incoming direction only. To enable the local end to transmit packets with short sequence numbers, configure this command on the remote end.
The sequence number format (long or short) of an MP bundle depends on the configuration of the first channel joining the MP bundle.
To negotiate the use of short sequence numbers on a dialer MP bundle, configure the command on the dialer interfaces and the ISDN D channels. To negotiate the use of short sequence numbers on a common MP bundle, use the command on all its channels. The command will cause PPP re-negotiation.
Examples
# Configure the short sequence number header format of MP in the incoming direction of Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp mp mp-group 2/0/0
[Sysname-Serial2/1/0] ppp mp short-sequence
ppp mp sort-buffer-size
Use ppp mp sort-buffer-size to set the MP sort buffer size factor on an interface.
Use undo ppp mp sort-buffer-size to restore the default.
Syntax
ppp mp sort-buffer-size size
undo ppp mp sort-buffer-size
Default
The MP sort buffer size factor is 1 on an interface.
Views
VT interface view
Dialer interface view
MP-group interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MP sort buffer size factor in the range of 1 to 64.
Usage guidelines
The MP sort buffer size = the number of channels in the current MP bundle × size. You can use the display ppp mp command to view the number of member channels in an MP bundle. If the calculated MP sort buffer size is 20, the MP sort buffer can sort 20 packets.
When MP is used, the received packets might be out of order. The sort buffer is used to re-sort packets. A large sort buffer results in better re-sorting but increases delay. For voice packets, the transmission delay should be minimized.
Examples
# Set the MP sort buffer size factor to 64 on MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] ppp mp sort-buffer-size 64
ppp mp timer lost-fragment
Use ppp mp timer lost-fragment to set the timer for MP to wait for the expected fragments on an interface.
Use undo ppp mp timer lost-fragment to restore the default.
Syntax
ppp mp timer lost-fragment seconds
undo ppp mp timer lost-fragment
Default
The timer for MP to wait for the expected fragments is 30 seconds on an interface.
Views
VT interface view
Dialer interface view
MP-group interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the timer for MP to wait for the expected fragment, in the range of 1 to 255 seconds.
Usage guidelines
A receiving end puts the received fragments in the buffer and reassembles them when it receives all the packet's fragments. You can configure a timer for MP to wait for the expected fragments. When the receiving end receives the first fragment of a packet, it starts the timer. When the timer expires, the system checks whether or not all fragments have arrived. If they have all arrived, the system reassembles the fragments. If they have not all arrived, the system discards all received fragments to release the buffer space.
Examples
# Set the timer for MP to wait for the expected fragment to 20 seconds on MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] ppp mp timer lost-fragment 20
ppp mp user
Use ppp mp user to associate a username with a VT interface.
Use undo ppp mp user to remove the association.
Syntax
ppp mp user username bind virtual-template number
undo ppp mp user username
Default
No username is associated with a VT interface.
Views
System view
Predefined user roles
network-admin
Parameters
username: Specifies a username, a case-sensitive string of 1 to 80 characters.
bind virtual-template number: Specifies a VT interface by its number.
The following matrix shows the value ranges for the number argument:
Hardware |
Value range |
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
0 to 1023 |
MSR2600-6-X1/2600-10-X1 |
0 to 1023 |
MSR 2630 |
0 to 1023 |
MSR3600-28/3600-51 |
0 to 1023 |
MSR3600-28-SI/3600-51-SI |
0 to 1023 |
MSR 3610 |
0 to 1023 |
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
0 to 2047 |
MSR 3620/3620-DP/3640/3660 |
0 to 2047 |
MSR5620/5660/5680 |
0 to 4095 |
Hardware |
Value range |
MSR810-LM-GL |
0 to 1023 |
MSR810-W-LM-GL |
0 to 1023 |
MSR830-6EI-GL |
0 to 1023 |
MSR830-10EI-GL |
0 to 1023 |
MSR830-6HI-GL |
0 to 1023 |
MSR830-10HI-GL |
0 to 1023 |
MSR2600-6-X1-GL |
0 to 1023 |
MSR3600-28-SI-GL |
0 to 1023 |
Usage guidelines
This command associates a username with a VT interface. After the user passes authentication, the system uses the settings on the VT interface to create an MP bundle and a VA interface to transmit data.
You can configure the following parameters for a VT interface:
· Local IP address and the peer IP address (or address pool).
· ppp mp-commands.
Examples
# Associate username user 1 with Virtual-Template 1, and set the IP address of the VT interface to 202.38.60.1/24.
<Sysname> system-view
[Sysname] ppp mp user user1 bind virtual-template 1
[Sysname] interface virtual-template 1
[Sysname-Virtual-Template1] ip address 202.38.60.1 255.255.255.0
Related commands
ppp mp
ppp mp virtual-template
Use ppp mp virtual-template to bind an interface to a VT interface and enable MP for the interface.
Use undo ppp mp to restore the default.
Syntax
ppp mp virtual-template number
undo ppp mp
Default
An interface is enabled with PPP.
Views
Interface view
Predefined user roles
network-admin
Parameters
number: Specifies a VT interface by its number.
The following matrix shows the value ranges for the number argument:
Hardware |
Value range |
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
0 to 1023 |
MSR2600-6-X1/2600-10-X1 |
0 to 1023 |
MSR 2630 |
0 to 1023 |
MSR3600-28/3600-51 |
0 to 1023 |
MSR3600-28-SI/3600-51-SI |
0 to 1023 |
MSR 3610 |
0 to 1023 |
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
0 to 2047 |
MSR 3620/3620-DP/3640/3660 |
0 to 2047 |
MSR5620/5660/5680 |
0 to 4095 |
Hardware |
Value range |
MSR810-LM-GL |
0 to 1023 |
MSR810-W-LM-GL |
0 to 1023 |
MSR830-6EI-GL |
0 to 1023 |
MSR830-10EI-GL |
0 to 1023 |
MSR830-6HI-GL |
0 to 1023 |
MSR830-10HI-GL |
0 to 1023 |
MSR2600-6-X1-GL |
0 to 1023 |
MSR3600-28-SI-GL |
0 to 1023 |
Usage guidelines
After you bind an interface to a VT interface, you can optionally enable PAP, CHAP, MS-CHAP, or MS-CHAP-V2 authentication.
The interfaces bound to the same VT interface are bound together. The ppp mp virtual-template command and the ppp mp command are mutually exclusive.
Examples
# Bind Serial 2/1/0 to Virtual-Template 1, and enable MP for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp mp virtual-template 1
Related commands
ppp mp
reset counters interface mp-group
Use reset counters interface mp-group to clear statistics on MP-group interfaces.
Syntax
reset counters interface [ mp-group [ interface-number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
mp-group: Clears traffic statistics on MP-group interfaces.
interface-number: Specifies an existing MP-group interface by its number.
Usage guidelines
Before collecting traffic statistics regularly on an MP-group interface, clear the existing statistics.
If you do not specify the mp-group keyword, the command clears statistics on all interfaces.
If you specify the mp-group keyword without the interface-number argument, the command clears statistics on all MP-group interfaces.
If you specify both mp-group and interface-number, the command clears statistics on the specified MP-group interface.
Examples
# Clear the statistics of MP-group 2/0/0
<Sysname> reset counters interface mp-group 2/0/0
Related commands
display interface mp-group
reset counters interface virtual-access
Use reset counters interface virtual-access to clear statistics on VA interfaces.
Syntax
reset counters interface [ virtual-access [ interface-number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
virtual-access: Clears statistics on VA interfaces.
interface-number: Specifies an existing VA interface by its number.
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
MSR810-LM-GL |
Yes |
MSR810-W-LM-GL |
Yes |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR2600-6-X1-GL |
Yes |
MSR3600-28-SI-GL |
Yes |
Before collecting traffic statistics regularly on a VA interface, clear the existing statistics.
If you do not specify the virtual-access keyword, the command clears statistics on all interfaces.
If you specify the virtual-access keyword without the interface-number argument, the command clears statistics on all VA interfaces.
If you specify both virtual-access and interface-number, the command clears statistics on the specified VA interface.
Examples
# Clear statistics on Virtual-Access 10.
<Sysname> reset counters interface virtual-access 10
Related commands
display interface virtual-access
service
Use service to specify a primary traffic processing slot for an interface.
Use undo service to restore the default.
Distributed devices in standalone mode/centralized devices in IRF mode:
service slot slot-number
undo service slot
Distributed devices in IRF mode:
service chassis chassis-number slot slot-number
undo service chassis
Default
No primary traffic processing slot is specified for an interface.
Views
VT interface view
Default command level
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
Hardware |
Command compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR2600-6-X1-GL |
No |
MSR3600-28-SI-GL |
No |
This command is supported on distributed devices and IRF-capable centralized devices.
Specify traffic processing slots if a feature requires that all traffic on a VA 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
# (Distributed devices in standalone mode.) Specify slot 2 as the primary traffic processing slot for VA interfaces on Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] service slot 2
# (Centralized devices in IRF mode.) Specify slot 2 as the primary traffic processing slot for VA interfaces on Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] service slot 2
# (Distributed devices in IRF mode.) Specify slot 2 as the primary traffic processing slot for VA interfaces on Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] service chassis 2 slot 2
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
Distributed devices in standalone mode/centralized devices in IRF mode:
service standby slot slot-number
undo service standby slot
Distributed devices in IRF mode:
service standby chassis chassis-number slot slot-number
undo service standby chassis
Default
No backup traffic processing slot is specified for an interface.
Views
VT interface view
Default command level
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
Hardware |
Command compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR2600-6-X1-GL |
No |
MSR3600-28-SI-GL |
No |
This command is supported on distributed devices and IRF-capable centralized devices.
Specify traffic processing slots if a feature requires that all traffic on a VA 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
# (Distributed devices in standalone mode.) Specify slot 2 as the primary traffic processing slot for the VA interfaces on Virtual-Template 10. Specify slot 3 as the backup traffic processing slot for the VA interfaces on Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] service slot 2
[Sysname-Virtual-Template10] service standby slot 3
# (Centralized devices in IRF mode.) Specify slot 2 as the primary traffic processing slot for the VA interfaces on Virtual-Template 10. Specify slot 3 as the backup traffic processing slot for the VA interfaces on Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] service slot 2
[Sysname-Virtual-Template10] service standby slot 3
# (Distributed devices in RF mode.) Specify slot 2 on IRF member device 2 as the primary traffic processing slot for the VA interfaces on Virtual-Template 10. Specify slot 3 on IRF member device 2 as the backup traffic processing slot for the VA interfaces on Virtual-Template 10.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] service chassis 2 slot 2
[Sysname-Virtual-Template10] service standby chassis 2 slot 3
Related commands
service
shutdown
Use shutdown to shut down an MP-group interface.
Use undo shutdown to bring up an MP-group interface.
Syntax
shutdown
undo shutdown
Default
An MP-group interface is up.
Views
MP-group interface view
Predefined user roles
network-admin
Examples
# Shut down MP-group 2/0/0.
<Sysname> system-view
[Sysname] interface mp-group 2/0/0
[Sysname-MP-group2/0/0] shutdown
PPPoE commands
Commands and descriptions for centralized devices apply to the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR2600-6-X1/2600-10-X1.
· MSR 2630.
· MSR3600-28/3600-51.
· MSR3600-28-SI/3600-51-SI.
· MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC.
· MSR 3610/3620/3620-DP/3640/3660.
· MSR810-LM-GL/810-W-LM-GL/830-6EI-GL/830-10EI-GL/830-6HI-GL/830-10HI-GL/2600-6-X1-GL/3600-28-SI-GL.
Commands and descriptions for distributed devices apply to the following routers:
· MSR5620.
· MSR 5660.
· MSR 5680.
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
The device does not support this feature in IRF mode.
The following matrix shows the feature and hardware compatibility:
Hardware |
PPPoE compatibility |
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK |
Yes |
MSR810-LMS/810-LUS |
Yes for only PPPoE client |
MSR2600-6-X1/2600-10-X1 |
Yes |
MSR 2630 |
Yes |
MSR3600-28/3600-51 |
Yes |
MSR3600-28-SI/3600-51-SI |
No |
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
MSR5620/5660/5680 |
Yes |
Hardware |
PPPoE compatibility |
MSR810-LM-GL |
Yes |
MSR810-W-LM-GL |
Yes |
MSR830-6EI-GL |
Yes |
MSR830-10EI-GL |
Yes |
MSR830-6HI-GL |
Yes |
MSR830-10HI-GL |
Yes |
MSR2600-6-X1-GL |
Yes |
MSR3600-28-SI-GL |
No |
PPPoE server commands
display pppoe-server session packet
Use display pppoe-server session packet to display packet statistics for PPPoE sessions.
Syntax
Centralized devices in standalone mode:
display pppoe-server session packet [ interface interface-type interface-number ]
Distributed devices in standalone mode:
display pppoe-server session packet { slot slot-number | interface interface-type interface-number }
Views
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface for centralized devices in standalone mode, the command displays packet statistics for PPPoE sessions on all interfaces.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command displays packet statistics for PPPoE sessions on all cards. (Distributed devices in standalone mode.)
# Display packet statistics for PPPoE sessions on GigabitEthernet 1/0/1.
<Sysname> display pppoe-server session packet interface gigabitethernet 1/0/1
Total PPPoE sessions: 2
Ethernet interface: GE1/0/1 Session ID: 1
InPackets: 37 OutPackets: 38
InBytes: 390 OutBytes: 406
InDrops: 0 OutDrops: 0
Ethernet interface: GE1/0/1 Session ID: 2
InPackets: 67 OutPackets: 48
InBytes: 490 OutBytes: 806
InDrops: 1 OutDrops: 2
Table 10 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
Centralized devices in standalone mode:
display pppoe-server session summary [ interface interface-type interface-number ]
Distributed devices in standalone mode:
display pppoe-server session summary { slot slot-number | interface interface-type interface-number }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface for centralized devices in standalone mode, the command displays summary PPPoE session information for all interfaces.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command displays summary PPPoE session information for all cards. (Distributed devices in standalone mode.)
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 GigabitEthernet 1/0/1.
<Sysname> display pppoe-server session summary interface gigabitethernet 1/0/1
Total PPPoE sessions: 2
Ethernet interface: GE1/0/1 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: GE1/0/1 Session ID: 2
PPP interface: VA2 State: OPEN
Remote MAC:00e0-1600-7200 Local MAC: 00e0-1400-7400
Service VLAN: 2 Customer VLAN: 155
# (Centralized devices in standalone mode.) Display summary PPPoE session information on all interfaces.
<Sysname> display pppoe-server session summary
Total PPPoE sessions: 2
Local PPPoE sessions: 2
Ethernet interface: GE1/0/2 Session ID: 1
PPP interface: VA1 State: OPEN
Remote MAC: 0000-0000-0005 Local MAC: 0000-5e00-0101
Service VLAN: N/A Customer VLAN: N/A
Ethernet interface: RAGG1 Session ID: 1
PPP interface: VA0 State: OPEN
Remote MAC: 0050-56c0-0005 Local MAC: 0000-5e00-0102
Service VLAN: N/A Customer VLAN: N/A
# (Distributed devices in standalone mode.) Display summary PPPoE session information on the MPU in slot 0.
<Sysname> display pppoe-server session summary slot 0
Total PPPoE sessions on slot 0: 1
Local PPPoE sessions on slot 0: 0
Ethernet interface: RAGG1 Session ID: 1
PPP interface: VA0 State: OPEN
Remote MAC: 0050-56c0-0005 Local MAC: 0000-5e00-0102
Service VLAN: N/A Customer VLAN: N/A
# (Distributed devices in standalone mode.) Display summary PPPoE session information on the interface card in slot 2.
<Sysname> display pppoe-server session summary slot 2
Total PPPoE sessions on slot 2: 2
Local PPPoE sessions on slot 2: 1
Ethernet interface: GE2/0/2 Session ID: 1
PPP interface: VA1 State: OPEN
Remote MAC: 0000-0000-0005 Local MAC: 0000-5e00-0101
Service VLAN: N/A Customer VLAN: N/A
Ethernet interface: RAGG1 Session ID: 1
PPP interface: VA0 State: OPEN
Remote MAC: 0050-56c0-0005 Local MAC: 0000-5e00-0102
Service VLAN: N/A Customer VLAN: N/A
Table 11 Command output
Field |
Description |
Total PPPoE sessions |
Total number of PPPoE sessions on physical interfaces and logical interfaces (centralized devices in standalone mode). |
Local PPPoE sessions |
Total number of PPPoE sessions on physical interfaces (centralized devices in standalone mode). When an interface is specified, this field is not displayed. |
Total PPPoE sessions on slot slot-number |
Total number of PPPoE sessions (distributed devices in standalone mode). When the slot slot-number option is specified, both PPPoE sessions on the local card's physical interfaces and global PPPoE sessions are displayed. |
Local PPPoE sessions on slot slot-number |
Total number of PPPoE sessions on the local card's physical interfaces (distributed devices in standalone mode). 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
Centralized devices in standalone mode:
display pppoe-server throttled-mac [ interface interface-type interface-number ]
Distributed devices in standalone mode:
display pppoe-server throttled-mac { slot slot-number | interface interface-type interface-number }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface for centralized devices in standalone mode,, the command displays information about blocked users on all interfaces.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command displays information about blocked users on all cards. (Distributed devices in standalone mode.)
Examples
# Display information about blocked users on GigabitEthernet 1/0/1.
<Sysname> display pppoe-server throttled-mac interface gigabitethernet 1/0/1
Total 3 client MACs:
Interface Remote MAC Start time Remaining time(s)
GE1/0/1 00e0-1500-4100 2010-12-01,12:10:30 55
GE1/0/1 00e0-1500-4000 2010-12-01,12:10:40 65
GE1/0/1 00e0-1500-3300 2010-12-01,12:10:50 75
Table 12 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
network-operator
Examples
# (Centralized devices in standalone mode.) Display information about VA pools.
<Sysname> display pppoe-server va-pool
VT interface Size Unused/State
Virtual-Template1 1000 900
Virtual-Template2 1000 Creating
# (Distributed devices in standalone mode.) Display information about VA pools.
<Sysname> display pppoe-server va-pool
Location VT interface Size Unused/State
Virtual-Template1 1000 900
1/* Virtual-Template2 1000 1000
Table 13 Command output
Field |
Description |
Location |
Card and CPU where the VA pool resides. This field is not displayed for centralized devices. 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
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
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface 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 GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server access-delay 100
pppoe-server access-line-id bas-info
Use pppoe-server access-line-id bas-info to configure the NAS-Port-ID attribute to automatically include BAS information on an interface.
Use undo pppoe-server access-line-id bas-info to restore the default.
Syntax
pppoe-server access-line-id bas-info [ cn-163 ]
undo pppoe-server access-line-id bas-info
Default
The NAS-Port-ID attribute does not automatically include BAS information on an interface.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Parameters
cn-163: Specifies the China-Telecom 163 format for the BAS information. If you do not specify this keyword, BAS information in the China-Telecom format is included.
Usage guidelines
The bas-info formats include China Telecom and China Telecom 163.
The BAS information in the China Telecom format is {atm|eth|trunk} NAS_slot/NAS_subslot/NAS_port:XPI.XCI, which represents information about the user access interface on the BRAS.
· When ATM/DSL is used, XPI.XCI represents VPI/VCI information.
· When Ethernet/DSL is used, XPI.XCI represents VLAN information.
For example, eth 1/0/1:4096.2345 includes the following information about the user access interface on the BRAS:
· The type of the interface is Ethernet interface.
· The interface is located at slot 1, subslot 0, and port 1.
· The outer VLAN ID is 4096 (which means invalid VLAN), and the inner VLAN ID is 2345.
Table 14 shows the China-Telecom 163 format, where:
· NAS_slot, NAS_subslot, and NAS_port refer to the numbering information of the PPPoE access interface on the BAS device.
· vpi and vci refer to VPI and VCI information.
· vlanid and vlanid2 refer to inner VLAN and outer VLAN, respectively. Value for the vlanid of the primary interface is fixed at 0.
Table 14 BAS information in China-Telecom 163 format
Interface type |
Format |
ATM interface |
slot=NAS_slot;subslot=NAS_subslot;port=NAS_port;vpi=XPI;vci=XCI; |
Primary interface or interface that does not carry inner VLAN or outer VLAN information. |
slot=NAS_slot;subslot=NAS_subslot;port=NAS_port;vlanid=VLAN id; |
Interface that carries inner VLAN and outer VLAN information. |
slot=NAS_slot;subslot=NAS_subslot;port=NAS_port;vlanid=VLAN id;vlanid2=VLAN id2; |
This command determines the content of the NAS-Port-ID attribute that the PPPoE server delivers to the RADIUS server.
· If the cn-163 keyword is specified, the PPPoE server automatically inserts the corresponding BAS information before the parsed circuit-id. Then it sends the combination of the bas-info and circuit-id as the NAS-Port-ID attribute to the RADIUS server.
· If the cn-163 keyword is not specified, the PPPoE server creates a new circuit-id in China-Telecom format. Then it sends the new circuit-id as the NAS-Port-ID attribute to the RADIUS server. The new circuit-id contains the corresponding BAS information and the DSLAM user access information in the original circuit-id.
If this command is not executed, the NAS-Port-ID attribute that the PPPoE server delivers to the RADIUS server is determined by the pppoe-server access-line-id content command.
The RADIUS server cannot correctly parse a NAS-Port-ID attribute that includes the remote-id and BAS information. When you configure this command together with the pppoe-server access-line-id trust command, make sure the NAS-Port-ID attribute sent to the RADIUS sever does not include the remote-id.
Examples
# Configure the NAS-Port-ID attribute to automatically include BAS information on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server access-line-id bas-info
Related commands
pppoe-server access-line-id circuit-id parse-mode
pppoe-server access-line-id content
pppoe-server access-line-id trust
pppoe-server access-line-id circuit-id parse-mode
Use pppoe-server access-line-id circuit-id parse-mode to configure the format that an interface uses to parse the circuit-id in the access line ID.
Use undo pppoe-server access-line-id circuit-id parse-mode to restore the default.
Syntax
pppoe-server access-line-id circuit-id parse-mode { cn-telecom | tr-101 }
undo pppoe-server access-line-id circuit-id parse-mode
Default
An interface uses the TR-101 format to parse the circuit-id.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Parameters
cn-telecom: Specifies China Telecom format.
tr-101: Specifies TR-101 format.
Usage guidelines
The circuit-id formats include TR-101 and China Telecom.
The TR-101 format is Access-Node-Identifier atm slot/port:vpi.vci for ATM/DSL, and is Access-Node-Identifier eth slot/port[:vlan-id] for Ethernet/DSL. The entire ID refers to the user access information on the DSLAM, where
· Access-Node-Identifier refers to the identifier of the DSLAM.
· The remainder refers to information about the user access interface on the DSLAM.
The China Telecom format is AccessNodeIdentifier/ANI_rack/ANI_frame/ANI_slot/ANI_subslot/ANI_port[:ANI_XPI.ANI_XCI], which represents user access information on the DSLAM, including DSLAM identifier and user access interface.
For example, guangzhou001/1/31/63/31/127 includes the following user access information on the DSLAM:
· The identifier of the access node DSLAM is guangzhou001.
· The rack number of the DSLAM is 1.
· The user access interface is located at frame 31, slot 63, subslot 31, and port 127.
Examples
# Configure GigabitEthernet 1/0/1 to use China Telecom format to parse the circuit-id.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server access-line-id circuit-id parse-mode cn-telecom
Related commands
pppoe-server access-line-id circuit-id trans-format
pppoe-server access-line-id circuit-id trans-format
Use pppoe-server access-line-id circuit-id trans-format to configure the transmission format for the circuit-id in access line ID on an interface.
Use undo pppoe-server access-line-id circuit-id trans-format to restore the default.
Syntax
pppoe-server access-line-id circuit-id trans-format { ascii | hex }
undo pppoe-server access-line-id circuit-id trans-format
Default
The transmission format for the circuit-id in access line ID is a string of characters on an interface.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Parameters
ascii: Specifies the character string format. For example, the circuit-id 00010002 is transmitted in the form of 01 08 30 30 30 31 30 30 30 32.
hex: Specifies the hexadecimal format. For example, the circuit-id 00010002 is transmitted in the form of 01 04 00 01 00 02.
Examples
# Configure GigabitEthernet 1/0/1 to use the hexadecimal format to transmit the circuit-id.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server access-line-id circuit-id trans-format hex
pppoe-server access-line-id content
Use pppoe-server access-line-id content to configure the content of the NAS-Port-ID attribute delivered to the RADIUS server on an interface.
Use undo pppoe-server access-line-id content to restore the default.
Syntax
pppoe-server access-line-id content { all [ separator ] | circuit-id | remote-id }
undo pppoe-server access-line-id content
Default
The NAS-Port-ID attribute contains only the circuit-id on an interface.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Parameters
all: Sends both the circuit-id and remote-id.
separator: Specifies a separator that is one character long. By default, the value is a blank space. The circuit-id and remote-id are connected by the separator.
circuit-id: Sends only the circuit-id.
remote-id: Sends only the remote-id.
Usage guidelines
The PPPoE server on a BAS device uses the RADIUS NAS-Port-ID attribute to send the access line ID received from a DSLAM device to the RADIUS server. The access line ID contains the circuit-id and remote-id. The RADIUS server compares the received NAS-Port-ID attribute with the local line ID information to verify the location of the user.
For more information about the circuit-id, see the pppoe-server access-line-id circuit-id parse-mode command.
For more information about the remote-id, see pppoe-server access-line-id remote-id trans-format the command.
Do not use a character that exists in the circuit-id or remote-id as the separator. Otherwise, the RADIUS server might fail to parse the ID information.
This command determines the content of the NAS-Port-ID attribute only when the pppoe-server access-line-id bas-info command is not configured. Otherwise, the pppoe-server access-line-id bas-info command determines the content of the NAS-Port-ID attribute.
Examples
# Configure GigabitEthernet 1/0/1 to deliver only the circuit-id to the RADIUS server.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server access-line-id content circuit-id
Related commands
pppoe-server access-line-id bas-info
pppoe-server access-line-id circuit-id parse-mode
pppoe-server access-line-id remote-id trans-format
pppoe-server access-line-id remote-id trans-format
Use pppoe-server access-line-id remote-id trans-format to configure the transmission format for the remote-id in the access line ID on an interface.
Use undo pppoe-server access-line-id remote-id trans-format to restore the default.
Syntax
pppoe-server access-line-id remote-id trans-format { ascii | hex }
undo pppoe-server access-line-id remote-id trans-format
Default
The transmission format for the remote-id is a string of characters on an interface.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Parameters
ascii: Specifies the character string format.
hex: Specifies the hexadecimal format.
Usage guidelines
The remote-id is the system MAC address of a PPPoE relay device (for example, DSLAM). It can be transmitted in character strings or hexadecimal format.
Examples
# Configure GigabitEthernet 1/0/1 to use the hexadecimal format to transmit the remote-id.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server access-line-id remote-id trans-format hex
pppoe-server access-line-id trust
Use pppoe-server access-line-id trust to configure the PPPoE server to trust the access line ID in received packets on an interface.
Use undo pppoe-server access-line-id trust to restore the default.
Syntax
pppoe-server access-line-id trust
undo pppoe-server access-line-id trust
Default
The PPPoE server does not trust the access line ID in received packets on an interface.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Usage guidelines
This command enables the PPPoE server to parse the circuit-id and remote-id in a received packet, and creates a new circuit-id and remote-id. If the PPPoE server fails to parse the circuit-id or remote-id in a PADR packet, it discards the packet and does not return a PADS packet.
If this command is not executed, the PPPoE server does not parse the circuit-id and remote-id in a received packet. The contents of both the new circuit-id and the remote-id are null.
Examples
# Configure GigabitEthernet 1/0/1 to trust the access line ID in received packets.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server access-line-id trust
Related commands
pppoe-server access-line-id circuit-id parse-mode
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
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Parameters
virtual template number: Specifies a VT interface by its number.
The following matrix shows the value ranges for the number argument:
Hardware |
Value range |
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
0 to 1023 |
MSR2600-6-X1/2600-10-X1 |
0 to 1023 |
MSR 2630 |
0 to 1023 |
MSR3600-28/3600-51 |
0 to 1023 |
MSR3600-28-SI/3600-51-SI |
0 to 1023 |
MSR 3610 |
0 to 1023 |
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
0 to 2047 |
MSR 3620/3620-DP/3640/3660 |
0 to 2047 |
MSR5620/5660/5680 |
0 to 4095 |
Hardware |
Value range |
MSR810-LM-GL |
0 to 1023 |
MSR810-W-LM-GL |
0 to 1023 |
MSR830-6EI-GL |
0 to 1023 |
MSR830-10EI-GL |
0 to 1023 |
MSR830-6HI-GL |
0 to 1023 |
MSR830-10HI-GL |
0 to 1023 |
MSR2600-6-X1-GL |
0 to 1023 |
MSR3600-28-SI-GL |
0 to 1023 |
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 GigabitEthernet 1/0/1 and bind the interface to Virtual-Template 1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] 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
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface 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 card. (Distributed devices in standalone.)
· Limit on a device. (Centralized devices in standalone mode.)
New maximum number settings only apply to subsequently established PPPoE sessions.
Examples
# Set the maximum number of PPPoE sessions on GigabitEthernet 1/0/1 to 50.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] 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
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface 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 card. (Distributed devices in standalone.)
· Limit on a device. (Centralized devices in standalone mode.)
New maximum number settings only apply to subsequently established PPPoE sessions.
Examples
# Set the maximum number of PPPoE sessions for a user on GigabitEthernet 1/0/1 to 50.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] 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
Layer 3 Ethernet subinterface view
Layer 3 virtual Ethernet subinterface view
Layer 3 aggregate subinterface view
L3VE subinterface view
EFM subinterface 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 card. (Distributed devices in standalone.)
· Limit on a device. (Centralized devices in standalone mode.)
New maximum number settings only apply to subsequently established PPPoE sessions.
Examples
# Set the maximum number of PPPoE sessions for a VLAN on GigabitEthernet 1/0/1.1 to 50.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1.1
[Sysname-GigabitEthernet1/0/1.1] 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 session-limit total
Use pppoe-server session-limit total to set the maximum number of PPPoE sessions on a device.
Use undo pppoe-server session-limit total to restore the default.
Syntax
Centralized devices in standalone mode:
pppoe-server session-limit total number
undo pppoe-server session-limit total
Distributed devices in standalone mode:
pppoe-server session-limit slot slot-number total number
undo pppoe-server session-limit slot slot-number total
Default
The number of PPPoE sessions on a device is not limited. (Centralized devices in standalone mode.)
The number of PPPoE sessions on a card is not limited. (Distributed devices in standalone.)
Views
System view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of PPPoE sessions on a device, in the range of 1 to 65534.
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
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 card. (Distributed devices in standalone.)
· Limit on a device. (Centralized devices in standalone mode.)
New maximum number settings only apply to subsequently established PPPoE sessions.
Examples
# (Centralized devices in standalone mode.) Set the maximum number of PPPoE sessions on a device to 3000.
<Sysname> system-view
[Sysname] pppoe-server session-limit total 3000
# (Distributed devices in standalone mode.) Set the maximum number of PPPoE sessions on card 3 to 1500.
<Sysname> system-view
[Sysname] pppoe-server session-limit slot 3 total 1500
Related commands
pppoe-server session-limit
pppoe-server session-limit per-mac
pppoe-server session-limit per-vlan
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
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface 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 PPPoE clients on H3C devices cannot identify PPPoE servers 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 GigabitEthernet 1/0/1 as pppoes.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] 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
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface 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 GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] 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
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface 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 GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server tag service-name pppoes
pppoe-server throttle per-mac
Use pppoe-server throttle per-mac to set the PPPoE access limit on an interface.
Use undo pppoe-server throttle per-mac to restore the default.
Syntax
pppoe-server throttle per-mac session-requests session-request-period blocking-period
undo pppoe-server throttle per-mac
Default
The PPPoE access rate is not limited on an interface.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
L3VE interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Parameters
session-requests: Specifies the maximum number of PPPoE session requests from a user within the monitoring time. The value range is 1 to 100000.
session-request-period: Specifies the monitoring time in the range of 1 to 3600 seconds.
blocking-period: Specifies the blocking time in the range of 1 to 3600 seconds.
Usage guidelines
This command limits the rate at which a user (identified by MAC address) can create PPPoE sessions on an interface. If the number of PPPoE requests within the monitoring time exceeds the configured threshold, the device discards the excessive requests, and outputs log messages. If the blocking time is set to 0, the device does not block any requests, and it only outputs log messages.
The device uses a monitoring table and a blocking table to control PPP access rates.
· Monitoring table—Stores a maximum of 8000 monitoring entries. Each entry records the number of PPPoE sessions created by a user within the monitoring time. When the monitoring entries reach the maximum, the system stops monitoring and blocking session requests from new users. The aging time of monitoring entries is determined by the session-request-period argument. When the timer expires, the system starts a new round of monitoring for the user.
· Blocking table—Stores a maximum of 8000 blocking entries. The system creates a blocking entry if the access rate of a user reaches the threshold, and blocks requests from that user. When the blocking entries reach the maximum, the system stops blocking session requests from new users and it only outputs log messages. The aging time of the blocking entries is determined by the blocking-period argument. When the timer expires, the system starts a new round of monitoring for the user.
If the access rate setting is changed, the system removes all monitoring and blocking entries, and uses the new settings to limit PPPoE access rates.
Examples
# Limit the rate at which a user can create PPPoE sessions on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server throttle per-mac 100 100 5
Related commands
display pppoe-server throttled-mac
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
Centralized devices in standalone mode:
pppoe-server virtual-template template-number va-pool va-volume
undo pppoe-server virtual-template template-number va-pool
Distributed devices in standalone mode:
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.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, a global VA pool is created. (Distributed devices in standalone mode.)
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 places the interface back to the VA pool when the user goes offline. When the 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 come online or go 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
PPPoE client commands
dialer diagnose
Use dialer diagnose to configure DDR to operate in diagnostic mode.
Use undo dialer diagnose to restore the default.
Syntax
dialer diagnose [ interval interval ]
undo dialer diagnose
Default
DDR operates in non-diagnostic mode.
Views
Dialer interface view
Predefined user roles
network-admin
Parameters
interval: Specifies the diagnostic interval in the range of 5 to 65535 seconds. The default is 120 seconds.
Usage guidelines
This command takes effect only when a dialer interface is used with PPPoE client applications.
In diagnostic mode, the device performs the following operations:
· Dials a PPPoE connection immediately after the device configurations are complete.
· Automatically terminates the connection.
· Starts the auto-dial timer after a configurable diagnostic interval.
· Redials a connection when the auto-dial timer expires.
By establishing and terminating PPPoE sessions periodically, you can monitor the operating status of the PPPoE link.
In diagnostic mode, the link idle-timeout timer is ignored.
Examples
# Configure Dialer 1 to operate in diagnostic mode, with a diagnostic interval of 300 seconds.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] dialer diagnose interval 300
Related commands
dialer timer autodial
dialer timer idle
display pppoe-client session packet
Use display pppoe-client session packet to display the protocol packet statistics for a PPPoE session.
Syntax
display pppoe-client session packet [ dial-bundle-number number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
dial-bundle-number number: Specifies the dialer bundle number corresponding to a PPPoE session, in the range of 0 to 1023. If you do not specify this option, the command displays the protocol packet statistics for all PPPoE sessions.
Usage guidelines
To display the data packet statistics for a PPPoE session, use the display interface virtual-access command to display information about the specified VA interface.
Examples
# Display the protocol packet statistics for all PPPoE sessions.
<Sysname> display pppoe-client session packet
Bundle: 1 Interface: GE1/0/1
InPackets: 19 OutPackets: 19
InBytes: 816 OutBytes: 816
InDrops: 0 OutDrops: 0
Bundle: 2 Interface: GE1/0/1
InPackets: 18 OutPackets: 18
InBytes: 730 OutBytes: 730
InDrops: 0 OutDrops: 0
Table 15 Command output
Field |
Description |
Bundle |
Dialer bundle to which a PPPoE session belongs. |
Interface |
Ethernet interface where the PPPoE session is present. |
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
reset pppoe-client session packet
display pppoe-client session summary
Use display pppoe-client session summary to display summary PPPoE session information.
Syntax
display pppoe-client session summary [ dial-bundle-number number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
dial-bundle-number number: Specifies the dialer bundle number corresponding to a PPPoE session, in the range of 0 to 1023. If you do not specify this option, the command displays summary information for all PPPoE sessions.
Examples
# Display summary information for all PPPoE sessions.
<Sysname> display pppoe-client session summary
Bundle ID Interface VA RemoteMAC LocalMAC State
1 1 GE1/0/1 VA0 00e0-1400-4300 00e0-1500-4100 SESSION
2 1 GE1/0/2 VA1 00e0-1500-4300 00e0-1600-4100 SESSION
Table 16 Command output
Field |
Description |
Bundle |
Dialer bundle to which the PPPoE session belongs. |
Interface |
Ethernet interface where the PPPoE session is present. |
VA |
Virtual access interface created for the PPPoE session. |
RemoteMAC |
MAC address of the remote end. |
LocalMAC |
MAC address of the local end. |
State |
PPPoE session state: · IDLE—Initialization state. · PADI SENT—A PPPoE Active Discovery Initiation (PADI) packet has been sent, and a PPPoE Active Discovery Offer (PADO) packet is being expected. · PADR SENT—A PPPoE Active Discovery Request (PADR) packet has been sent, and a PPPoE Active Discovery Session-confirmation (PADS) packet is being expected. · SESSION—The PPPoE session has been successfully established. |
pppoe-client
Use pppoe-client to establish a PPPoE session and specify the dialer bundle corresponding to the session.
Use undo pppoe-client to remove a PPPoE session.
Syntax
pppoe-client dial-bundle-number number [ no-hostuniq ]
undo pppoe-client dial-bundle-number number
Default
No PPPoE session is established.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
Predefined user roles
network-admin
Parameters
dial-bundle-number number: Specifies the dialer bundle number corresponding to a PPPoE session, in the range of 0 to 1023. A dialer bundle number uniquely identifies a PPPoE session. It can also be used as a PPPoE session ID.
no-hostuniq: Configures the client not to carry the Host-Uniq field in discovery packets. If you do not specify this keyword, the client carries the Host-Unique field. The Host-Unique field uniquely identifies a PPPoE client when an interface is configured with multiple PPPoE sessions. When the PPPoE server receives a packet with this field, it must include this field unmodified in the response packet. The device identifies the PPPoE client where the response packet belongs based on the Host-Unique field in the response packet.
Examples
# Establish a PPPoE session on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-client dial-bundle-number 1
# Establish a PPPoE session on Virtual-Ethernet 0.
<Sysname> system-view
[Sysname] interface virtual-ethernet 0
[Sysname-Virtual-Ethernet0] pppoe-client dial-bundle-number 1
# Establish a PPPoE session on VLAN-Interface 1.
<Sysname> system-view
[Sysname] interface vlan-interface 1
[Sysname-Vlan-interface1] pppoe-client dial-bundle-number 1
reset pppoe-client
Use reset pppoe-client to reset a PPPoE session corresponding to a dialer bundle.
Syntax
reset pppoe-client { all | dial-bundle-number number }
Views
User view
Predefined user roles
network-admin
Parameters
all: Resets all the PPPoE sessions.
dial-bundle-number number: Specifies a dialer bundle by its number in the range of 0 to 1023.
Usage guidelines
A PPPoE session in permanent mode and terminated by this command will be established again when the auto dial timer expires.
A PPPoE session in on-demand mode and terminated by this command will be established again only when there is a need for data transmission.
Examples
# Reset all PPPoE sessions.
<Sysname> reset pppoe-client all
Related commands
dialer timer autodial
reset pppoe-client session packet
Use reset pppoe-client session packet to reset the protocol packet statistics for a PPPoE session.
Syntax
reset pppoe-client session packet [ dial-bundle-number number ]
Views
User view
Predefined user roles
network-admin
Parameters
dial-bundle-number number: Specifies the dialer bundle number corresponding to a PPPoE session, in the range of 0 to 1023. If you do not specify this option, the command resets the protocol packet statistics for all PPPoE sessions.
Examples
# Reset the protocol packet statistics for all PPPoE sessions.
<Sysname> reset pppoe-client session packet
Related commands
display pppoe-client session packet
L2TP commands
The device does not support this feature in IRF mode.
The LNS mode is not supported on MSR810-LMS and MSR810-LUS routers.
allow l2tp
Use allow l2tp to configure an L2TP network server (LNS) to accept Layer 2 Tunneling Protocol (L2TP) tunneling requests from an L2TP access concentrator (LAC), and to specify a VT interface for tunnel setup.
Use undo allow to restore the default.
Syntax
allow l2tp virtual-template virtual-template-number [ remote remote-name ]
Default
An LNS denies L2TP tunneling requests from any LACs.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
The following matrix shows the value ranges for the virtual-template-number argument:
Hardware |
Value range |
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
0 to 1023 |
MSR2600-6-X1/2600-10-X1 |
0 to 1023 |
MSR 2630 |
0 to 1023 |
MSR3600-28/3600-51 |
0 to 1023 |
MSR3600-28-SI/3600-51-SI |
0 to 1023 |
MSR 3610 |
0 to 1023 |
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
0 to 2047 |
MSR 3620/3620-DP/3640/3660 |
0 to 2047 |
MSR5620/5660/5680 |
0 to 4095 |
Hardware |
Value range |
MSR810-LM-GL |
0 to 1023 |
MSR810-W-LM-GL |
0 to 1023 |
MSR830-6EI-GL |
0 to 1023 |
MSR830-10EI-GL |
0 to 1023 |
MSR830-6HI-GL |
0 to 1023 |
MSR830-10HI-GL |
0 to 1023 |
MSR2600-6-X1-GL |
0 to 1023 |
MSR3600-28-SI-GL |
0 to 1023 |
remote remote-name: Specifies the name of the tunnel peer (LAC) initiating tunneling requests, a case-sensitive string of 1 to 31 characters.
Usage guidelines
The allow l2tp command is available only on L2TP groups in LNS mode.
Make sure the specified name of the tunnel peer is consistent with the local name configured on the LAC.
If you execute this command multiple times for an L2TP group, the most recent configuration takes effect.
For L2TP group 1, if you do not specify the remote remote-name option, an LNS accepts tunneling requests from any LACs. In this case, L2TP group 1 acts as the default L2TP group. For L2TP groups other than L2TP group 1, the remote remote-name option must be configured.
The allow l2tp command is available only on LNSs.
· When an LAC that initiates a tunneling request is the tunnel peer configured in an L2TP group, the LNS uses the tunnel parameters configured in this group for tunnel setup.
· When the LAC is not the tunnel peer configured in any L2TP group, the LNS performs one of the following operations:
¡ Uses the tunnel parameters for the default L2TP group if it exists.
¡ Fails to set up a tunnel with the LAC if the default L2TP group does not exist.
As a best practice, configure a default L2TP group on the LNS in the following cases:
· LACs (such as hosts with Windows 2000 Beta 2 installed) include blank local names in their tunneling requests.
· The LNS sets up tunnels with multiple LACs by using the same tunnel parameters.
Examples
# Specify L2TP group 1 as the default L2TP group, and specify Virtual-Template 1 for tunnel setup. For L2TP group 2, configure the LNS to accept the L2TP tunneling request initiated by the peer (LAC) named aaa, and specify Virtual-Template 2 for tunnel setup.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lns
[Sysname-l2tp1] allow l2tp virtual-template 1
[Sysname-l2tp1] quit
[Sysname] l2tp-group 2 mode lns
[Sysname-l2tp2] allow l2tp virtual-template 2 remote aaa
tunnel name
bandwidth
Use bandwidth to set the expected bandwidth for an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth (in kbps) is interface baudrate divided by 1000.
Views
Virtual PPP interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth of an interface affects the link costs in OSPF, OSPFv3, and IS-IS. For more information, see Layer 3—IP Routing Configuration Guide.
Examples
# Set the expected bandwidth of Virtual-PPP 10 to 100 kbps.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] bandwidth 100
default
Use default to restore the default settings for a virtual PPP interface.
Syntax
default
Views
Virtual PPP 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 when you execute it on a live network. |
This command might fail to restore the default settings for some commands for reasons such as command dependencies 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 for Virtual-PPP 10.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] default
description
Use description to set the description for a virtual PPP interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of an interface is the interface-name plus Interface. For example, the default description of Virtual-PPP254 is Virtual-PPP254 Interface.
Views
Virtual PPP 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 of Virtual-PPP 10 to virtual-interface.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] description virtual-interface
display interface virtual-ppp
Use display interface virtual-ppp to display information about virtual PPP interfaces.
Syntax
display interface [ virtual-ppp [ interface-number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-number: Specifies an existing virtual PPP interface by its number in the range of 0 to 255.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of each interface description.
down: Displays information about the interfaces in physically down state and the causes. If you do not specify this keyword, the command displays information about all interfaces.
Usage guidelines
If you do not specify the virtual-ppp keyword, this command displays information about all interfaces.
If you specify the virtual-ppp keyword but you do not specify an interface, this command displays information about all virtual PPP interfaces.
Examples
# Display detailed information about Virtual-PPP 10.
<Sysname> display interface virtual-ppp 10
Virtual-PPP10
Current state: Administratively DOWN
Line protocol state: DOWN
Description: Virtual-PPP10 Interface
Bandwidth: 100000kbps
Maximum transmission unit:1500
Hold timer: 10 seconds, retry times: 5
Internet address: 10.1.1.1/24 (primary)
Link layer protocol: PPP
LCP: initial
Physical: L2TP, baudrate: 100000000 bps
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 154 packets, 1880 bytes, 0 drops
Output: 155 packets, 1875 bytes, 0 drops
Table 17 Command output
Field |
Description |
Current state |
Physical state and administrative state of the virtual PPP interface: · Administratively DOWN—The interface is administratively shut down by using the shutdown command. · DOWN—The interface is administratively up but physically down. · UP—The interface is up both administratively and physically. |
Line protocol state |
Link layer protocol state of the virtual PPP interface: · UP—The interface is up at the data link layer. · UP (spoofing)—The link layer protocol of an interface is UP, but its link is an on-demand link or not present at all. · DOWN—The interface is down at the data link layer. |
Bandwidth |
Intended bandwidth of the interface. |
Hold timer |
Interval in seconds for the interface to send keepalive packets. |
retry times |
Keepalive retry limit. The interface determines that its peer has been down if it does not receive a keepalive response when the keepalive retry limit is reached. |
Internet Address |
IP address of the interface: · Internet protocol processing: disabled—No IP address is configured, and the interface cannot process IP packets. · primary—The IP address is the primary one of the interface. |
Link layer protocol |
Link layer protocol of the interface: PPP. |
Physical |
Physical type of the interface: L2TP. |
baudrate |
Baud rate of the interface. |
Last clearing of counters |
Time when the reset counters interface command was last used to clear the interface statistics. This field displays Never if the reset counters interface command has never been used on the interface since device startup. |
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec |
Average rate of inbound traffic in the last 300 seconds. |
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec |
Average rate of outbound traffic in the last 300 seconds. |
Input: 154 packets, 1880 bytes, 0 drops |
Total number of inbound packets, total number of inbound bytes, and total number of dropped inbound packets. |
Output: 155 packets, 1875 bytes, 0 drops |
Total number of outbound packets, total number of outbound bytes, and total number of dropped outbound packets. |
# Display summary information about Virtual-PPP 10.
<Sysname> display interface virtual-ppp 10 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
VPPP10 ADM DOWN 10.0.0.1
# Display information about the virtual PPP interfaces in physically down state and the causes.
<Sysname> display interface virtual-ppp brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
VPPP9 ADM Administratively
VPPP10 ADM Administratively
VPPP12 ADM Administratively
# Display summary information about Virtual-PPP 10, including the complete interface description.
<Sysname> display inter Virtual-PPP 10 brief description
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
VPPP10 ADM DOWN 10.0.0.1
Table 18 Command output
Field |
Description |
Brief information on interfaces in route mode |
Summary information about Layer 3 interfaces. |
Link: ADM - administratively down; Stby - standby |
Link status: · ADM—The interface has been shut down by the network administrator. To recover its physical layer state, execute the undo shutdown command. · Stby—The interface is a backup interface. To see the primary interface, use the display interface-backup state command described in High Availability Command Reference. |
Protocol: (s) - spoofing |
The link layer protocol of an interface is UP, but its link is an on-demand link or not present at all. The protocol state of null or loopback interfaces might include the spoofing flag. |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been administratively shut down. To recover its physical state, execute the undo shutdown command. · Stby—The interface is a backup interface. |
Protocol |
Link layer protocol state of the interface: · UP. · DOWN. · UP (s)—The link of the interface is an on-demand link or not present at all. This state applies to null and loopback interfaces. |
Description |
Partial or complete interface description set by using the description command: · If you do not specify the description keyword for the display interface brief command, this field displays only the first 27 characters of the interface description. · If you specify the description keyword for the display interface brief command, this field displays the complete interface description. |
Cause |
Causes for the physical state of the interface to be Down: · Not connected—No physical connection exists (possibly because the L2TP negotiation fails or insufficient configuration exists to trigger L2TP negotiation). · Administratively—The interface was shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. |
display l2tp session
Use display l2tp session to display information about L2TP sessions.
Syntax
display l2tp session [ statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
statistics: Displays statistics for L2TP sessions.
Examples
# Display statistics for L2TP sessions.
<Sysname> display l2tp session statistics
Total number of sessions: 1
# Display information about L2TP sessions.
<Sysname> display l2tp session
LocalSID RemoteSID LocalTID State
89 36245 10878 Established
Table 19 Command output
Field |
Description |
LocalSID |
Local session ID. |
RemoteSID |
Remote session ID. |
LocalTID |
Local tunnel ID. |
State |
Session state: · Idle. · Wait-tunnel—Waits for the tunnel to be established. · Wait-reply—Waits for an Incoming-Call-Reply (ICRP) message indicating the call is accepted. · Wait-connect—Waits for an Incoming-Call-Connected (ICCN) message. · Established. |
display l2tp session temporary
Use display l2tp session temporary to display information about temporary L2TP sessions.
Syntax
display l2tp session temporary
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display information about temporary L2TP sessions.
<Sysname> display l2tp session temporary
Total number of temporary sessions: 6
LocalSID RemoteSID LocalTID State
2298 0 19699 Wait-tunnel
42805 0 19699 Wait-tunnel
17777 0 19699 Wait-tunnel
58284 0 19699 Wait-tunnel
33256 0 19699 Wait-tunnel
8228 0 19699 Wait-tunnel
Table 20 Command output
Field |
Description |
LocalSID |
Local session ID. |
RemoteSID |
Remote session ID. |
LocalTID |
Local tunnel ID. |
State |
Session state: · Idle. · Wait-tunnel—Waits for the tunnel to be established. · Wait-reply—Waits for an ICRP message. · Wait-connect—Waits for an ICCN message. |
display l2tp tunnel
Use display l2tp tunnel to display information about L2TP tunnels.
Syntax
display l2tp tunnel [ statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
statistics: Displays statistics for L2TP tunnels.
Examples
# Display statistics for L2TP tunnels.
<Sysname> display l2tp tunnel statistics
Total number of tunnels: 1
# Display information about L2TP tunnels.
<Sysname> display l2tp tunnel
LocalTID RemoteTID State Sessions RemoteAddress RemotePort RemoteName
10878 21 Established 1 20.1.1.2 1701 lns
Table 21 Command output
Field |
Description |
LocalTID |
Local tunnel ID. |
RemoteTID |
Remote tunnel ID. |
State |
Tunnel state: · Idle. · Wait-reply. · Wait-connect. · Established. · Stopping. |
Sessions |
Number of sessions within 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
display l2tp va-pool
Use display l2tp va-pool to display information about L2TP VA pools.
Syntax
display l2tp va-pool
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display information about L2TP VA pools.
<Sysname> display l2tp va-pool
VT interface Size Unused State
Virtual-Template1 1000 900 Normal
Table 22 Command output
Field |
Description |
VT interface |
VT interface that uses the VA pool. |
Size |
VA pool capacity set for L2TP users. |
Unused |
VA pool capacity available for L2TP users. |
State |
Current state of the VA pool: · Creating—The VA pool is being created. · Destroying—The VA pool is being removed. · Normal—The VA pool has been created. |
Related commands
l2tp virtual-template va-pool
interface virtual-ppp
Use interface virtual-ppp to create a virtual PPP interface and enter its view, or enter the view of an existing virtual PPP interface.
Use undo interface virtual-ppp to delete a virtual PPP interface.
Syntax
interface virtual-ppp interface-number
undo interface virtual-ppp interface-number
Default
No virtual PPP interface exists.
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a virtual PPP interface by its number in the range of 0 to 255.
Usage guidelines
A virtual PPP interface is required on the LAC for establishing an LAC-auto-initiated L2TP tunnel.
Examples
# Create Virtual-PPP 10 and enter its view.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
ip dscp
Use ip dscp to set the DSCP value of L2TP packets.
Use undo ip dscp to restore the default.
Syntax
ip dscp dscp-value
undo ip dscp
Default
The DSCP value of L2TP packets is 0.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
dscp-value: Specifies the DSCP value of L2TP packets, in the range of 0 to 63.
Usage guidelines
The DSCP field is the first 6 bits of the IP ToS byte. This field marks the priority of IP packets for forwarding. This command sets the DSCP value for the IP packet when L2TP encapsulates a PPP frame into an IP packet.
Examples
# Set the DSCP value of L2TP packets to 50.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] ip dscp 50
l2tp enable
Use l2tp enable to enable L2TP.
Use undo l2tp enable to disable L2TP.
Syntax
l2tp enable
undo l2tp enable
Default
L2TP is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
For L2TP configurations to take effect, you must enable L2TP.
Examples
# Enable L2TP.
<Sysname> system-view
[Sysname] l2tp enable
l2tp tsa-id
Use l2tp tsa-id to set the TSA ID for the L2TP tunnel switching (LTS) device and enable L2TP loop detection on the LTS device.
Use undo l2tp tsa-id to restore the default.
Syntax
l2tp tsa-id tsa-id
undo l2tp tsa-id
Default
The TSA ID of the LTS device is not set, and L2TP loop detection is disabled on the LTS device.
Views
System view
Predefined user roles
network-admin
Parameters
tsa-id: Specifies a TSA ID that uniquely identifies the LTS device. This argument is a case-sensitive string of 1 to 64 characters.
Usage guidelines
The LTS device compares the configured TSA ID with each TSA ID Attribute Value Pair (AVP) in a received ICRQ packet for loop detection.
· If a match is found, a loop exists. The LTS immediately tears down the session.
· If no match is found, the LTS performs the following operations:
a. Encapsulates the configured TSA ID into a new TSA ID AVP.
b. Appends the new TSA ID AVP to the packet.
c. Sends the packet to the next hop LTS.
To avoid loop detection errors, make sure the TSA ID of each LTS device is unique.
Examples
# Set the TSA ID of the LTS device to lts0, and enable L2TP loop detection on the LTS device.
<Sysname> system-view
[Sysname] l2tp tsa-id lts0
l2tp virtual-template va-pool
Use l2tp virtual-template va-pool to create a VA pool.
Use undo l2tp virtual-template va-pool to delete a VA pool.
Syntax
l2tp virtual-template template-number va-pool va-volume
undo l2tp virtual-template template-number va-pool
Default
No VA pool exists.
Views
System view
Predefined user roles
network-admin
Parameters
virtual-template template-number: Specifies an existing VT interface by its number 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.
Usage guidelines
The LNS creates a VA interface for an L2TP session to exchange packets with the LAC, and it deletes the VA interface when the user goes offline. Creating and deleting VA interfaces take time. If a large number of users are coming online or going offline, the performance of L2TP connection establishment and termination will be degraded.
You can configure a VA pool to improve the performance. A VA pool contains a group of VA interfaces. The LNS selects a VA interface from the pool for a requesting user and places the interface back to the VA pool when the user goes offline. This mechanism speeds up the establishment and termination of L2TP connections. When a VA pool is exhausted, the system still creates a VA interface for an L2TP connection and deletes it when the user goes offline.
When you configure a VA pool, follow these guidelines:
· A VT interface can be associated with only one VA pool. To change the capacity of a VA pool, delete the previous configuration, and reconfigure the VA pool.
· Creating or deleting a VA pool takes time. During the process of creating or deleting a VA pool, users can come online or go offline, but the VA pool does not take effect.
· The system might create a VA pool that contains VA interfaces less than the specified number because of insufficient resources. In this case, you can use the display l2tp va-pool command to view the number of available VA interfaces and current state of the VA pool.
· Create a VA pool with an appropriate capacity, because a VA pool occupies much system memory.
· 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 for Virtual-template 2.
<Sysname> system-view
[Sysname] l2tp virtual-template 2 va-pool 1000
Related commands
display l2tp va-pool
l2tp-auto-client
Use l2tp-auto-client to trigger an LAC to automatically establish an L2TP tunnel.
Use undo l2tp-auto-client to delete the automatically established L2TP tunnel.
Syntax
l2tp-auto-client l2tp-group group-number
undo l2tp-auto-client
Default
An LAC does not automatically establish an L2TP tunnel.
Views
Virtual PPP interface view
Predefined user roles
network-admin
Parameters
l2tp-group group-number: Specifies an L2TP group by its number in the range of 1 to 65535. The LAC uses tunnel parameters of the L2TP group to establish the tunnel.
Usage guidelines
The L2TP group specified must be an existing one in LAC mode.
An L2TP tunnel automatically established in LAC-auto-initiated mode exists until you delete the tunnel by using the undo l2tp-auto-client or undo l2tp-group group-number command.
Examples
# Trigger the LAC to automatically establish an L2TP tunnel by using the tunnel parameters of L2TP group 10.
<Sysname> system-view
[Sysname] interface virtual-ppp 1
[Sysname-Virtual-PPP1] l2tp-auto-client l2tp-group 10
Related commands
l2tp-group
l2tp-group
Use l2tp-group to create an L2TP group and enter its view, or enter the view of an existing L2TP group.
Use undo l2tp-group to delete an L2TP group.
Syntax
l2tp-group group-number [ mode { lac | lns } ]
undo l2tp-group group-number
Default
No L2TP group exists.
Views
System view
Predefined user roles
network-admin
Parameters
group-number: Specifies an L2TP group by its number in the range of 1 to 65535.
mode: Specifies a mode for the L2TP group.
lac: Specifies the LAC mode.
lns: Specifies the LNS mode.
Usage guidelines
To create a new L2TP group, you must specify the mode keyword. To enter the view of an existing L2TP group, you do not need to specify this keyword.
In L2TP group view, you can configure L2TP tunnel parameters, such as tunnel authentication and flow control.
A device can have L2TP groups in both LAC and LNS modes at the same time.
Examples
# Create L2TP group 2 in LAC mode, and enter its view.
<Sysname> system-view
[Sysname] l2tp-group 2 mode lac
[Sysname-l2tp2]
Related commands
allow l2tp
lns-ip
user
lns-ip
Use lns-ip to specify LNS IP addresses on an LAC.
Use undo lns-ip to remove the specified LNS IP addresses on an LAC.
Syntax
lns-ip { ip-address }&<1-5>
undo lns-ip
Default
No LNS IP addresses are specified on an LAC.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
{ ip-address }&<1-5>: Specifies LNS IP addresses. &<1-5> indicates that you can enter a maximum of five IP addresses.
Usage guidelines
The LAC initiates an L2TP tunneling request to its specified LNSs consecutively in their configuration order until it receives an acknowledgment from an LNS. The LNS then becomes the tunnel peer.
The lns-ip command is available only on L2TP groups in LAC mode.
If you execute this command multiple times for an L2TP group, the most recent configuration takes effect.
Examples
# Specify the LNS IP address as 202.1.1.1.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] lns-ip 202.1.1.1
mandatory-chap
Use mandatory-chap to force the LNS to perform CHAP authentication for users.
Use undo mandatory-chap to restore the default.
Syntax
mandatory-chap
undo mandatory-chap
Default
An LNS does not perform CHAP authentication for users.
Views
L2TP group view
Predefined user roles
network-admin
Usage guidelines
The LNS uses the LAC as an authentication proxy. The LAC sends the LNS all user authentication information from users and the authentication method configured on the LAC itself. The LNS then checks the user validity according to the received information and the locally configured authentication method.
When mandatory CHAP authentication is configured, a user who depends on an LAC to initiate tunneling requests is authenticated by both the LAC and the LNS for increased security. Some users might not support the authentication on the LNS. In this situation, do not configure this command, because CHAP authentication on the LNS will fail.
This command is available only on L2TP groups in LNS mode.
This command takes effect only on NAS-initiated L2TP tunnels.
The mandatory-lcp command takes precedence over this command. If both commands are configured for an L2TP group, the LNS performs LCP renegotiation with the user.
Examples
# Force the LNS to perform CHAP authentication for users.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lns
[Sysname-l2tp1] mandatory-chap
mandatory-lcp
mandatory-lcp
Use mandatory-lcp to force an LNS to perform LCP negotiation with users.
Use undo mandatory-lcp to restore the default.
Syntax
mandatory-lcp
undo mandatory-lcp
Default
An LNS does not perform LCP negotiation with users.
Views
L2TP group view
Predefined user roles
network-admin
Usage guidelines
By default, to establish a NAS-initiated tunnel, the user performs LCP negotiation with the LAC. If the negotiation succeeds, the LAC initiates a tunneling request and sends the negotiation results (including authentication information) to the LNS. Then, the LNS determines whether the user is valid based on the information received instead of performing LCP renegotiation with the user.
If you do not expect the LNS to accept LCP negotiation parameters, configure this command to perform an LCP negotiation between the LNS and the user. In this case, the information sent by the LAC will be ignored.
Some users might not support LCP negotiation. In this case, do not configure this command because LCP negotiation will fail.
This command is available only on L2TP groups in LNS mode.
This command takes effect only on NAS-initiated L2TP tunnels.
This command takes precedence over the mandatory-chap command. If both commands are configured for an L2TP group, the LNS performs LCP negotiation with the user.
Examples
# Force an LNS to perform LCP negotiation with users.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lns
[Sysname-l2tp1] mandatory-lcp
Related commands
mandatory-chap
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 size of a virtual PPP interface is 1500 bytes.
Views
Virtual PPP interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU size in the range of 128 to 1500 bytes.
Usage guidelines
The MTU size of an interface affects the fragmentation and reassembly of IP packets on the interface.
For the configured MTU size to take effect, you must execute the shutdown command and then the undo shutdown command on the interface.
Examples
# Set the MTU size of Virtual-PPP 10 to 1400 bytes.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] mtu 1400
ppp access-control enable
Use ppp access-control enable to enable L2TP-based EAD.
Use undo ppp access-control enable to disable L2TP-based EAD.
Syntax
ppp access-control enable
undo ppp access-control enable
Default
L2TP-based EAD is disabled.
Views
VT interface view
Predefined user roles
network-admin
Usage guidelines
This command does not apply to PPP sessions that already exist on the VT interface. It only applies to newly created PPP sessions on the VT interface.
Different ACLs can be used for different users if the VT interface is used as the access interface for the LNS.
L2TP-based EAD enables the LNS to transparently pass CAMS/IMC packets to the iNode client to inform the client of EAD server information, such as the IP address.
Examples
# Enable L2TP-based EAD.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] ppp access-control enable
ppp lcp imsi accept
Use ppp lcp imsi accept to enable the client/LAC to accept the IMSI binding authentication requests from the LNS.
Use undo ppp lcp imsi accept to restore the default.
Syntax
ppp lcp imsi accept
undo ppp lcp imsi accept
Default
The client/LAC declines the IMSI binding authentication requests from the LNS.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable the client to accept the IMSI binding authentication requests from the LNS.
<Sysname> system-view
[Sysname] interface serial 2/1/0:0
[Sysname-Serial2/1/0:0] ppp lcp imsi accept
# Enable the LAC to accept the IMSI binding authentication requests from the LNS.
<Sysname> system-view
[Sysname] interface virtual-ppp 1
[Sysname-Virtual-PPP1] ppp lcp imsi accept
Related commands
ppp lcp imsi request
ppp lcp imsi string
ppp lcp imsi request
Use ppp lcp imsi request to enable the LNS to initiate IMSI binding authentication requests.
Use undo ppp lcp imsi request to restore the default.
Syntax
ppp lcp imsi request
undo ppp lcp imsi request
Default
The LNS does not initiate IMSI binding authentication requests.
Views
VT interface view
Predefined user roles
network-admin
Examples
# Enable the LNS to initiate IMSI binding authentication requests.
<Sysname> system-view
[Sysname] interface virtual-template 1
[Sysname-Virtual-Template1] ppp lcp imsi request
Related commands
ppp lcp imsi accept
ppp lcp imsi string
ppp lcp imsi string
Use ppp lcp imsi string to configure the IMSI information on the client/LAC.
Use undo ppp lcp imsi string to restore the default.
Syntax
ppp lcp imsi string imsi-info
undo ppp lcp imsi string
Default
The client/LAC automatically obtains the IMSI information from its SIM card.
Views
Interface view
Predefined user roles
network-admin
Parameters
imsi-info: Configures the IMSI information, a case-sensitive string of 1 to 31 characters.
Examples
# Configure the IMSI information as imsi1 on the client.
<Sysname> system-view
[Sysname] interface serial 2/1/0:0
[Sysname-Serial2/1/0:0] ppp lcp imsi string imsi1
# Configure the IMSI information as imsi1 on the LAC.
<Sysname> system-view
[Sysname] interface virtual-ppp 1
[Sysname-Virtual-PPP1] ppp lcp imsi string imsi1
Related commands
ppp lcp imsi accept
ppp lcp imsi request
ppp lcp sn accept
Use ppp lcp sn accept to enable the client/LAC to accept the SN binding authentication requests from the LNS.
Use undo ppp lcp sn accept to restore the default.
Syntax
ppp lcp sn accept
undo ppp lcp sn accept
Default
The client/LAC declines the SN binding authentication requests from the LNS.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable the client to accept the SN binding authentication requests from the LNS.
<Sysname> system-view
[Sysname] interface serial 2/1/0:0
[Sysname-Serial2/1/0:0] ppp lcp sn accept
# Enable the LAC to accept the SN binding authentication requests from the LNS.
<Sysname> system-view
[Sysname] interface virtual-ppp 1
[Sysname-Virtual-PPP1] ppp lcp sn accept
Related commands
ppp lcp sn request
ppp lcp sn string
ppp lcp sn request
Use ppp lcp sn request to enable the LNS to initiate SN binding authentication requests.
Use undo ppp lcp sn request to restore the default.
Syntax
ppp lcp sn request
undo ppp lcp sn request
Default
The LNS does not initiate SN binding authentication requests.
Views
VT interface view
Predefined user roles
network-admin
Examples
# Enable the LNS to initiate SN binding authentication requests.
<Sysname> system-view
[Sysname] interface virtual-template 1
[Sysname-Virtual-Template1] ppp lcp sn request
Related commands
ppp lcp sn accept
ppp lcp sn string
ppp lcp sn string
Use ppp lcp sn string to configure the SN information on the client/LAC.
Use undo ppp lcp sn string to restore the default.
Syntax
ppp lcp sn string sn-info
undo ppp lcp sn string
Default
The client/LAC automatically obtains the SN information from its SIM card.
Views
Interface view
Predefined user roles
network-admin
Parameters
sn-info: Configures the SN information, a case-sensitive string of 1 to 31 characters.
Examples
# Configure the SN information as sn1 on the client.
<Sysname> system-view
[Sysname] interface serial 2/1/0:0
[Sysname-Serial2/1/0:0] ppp lcp sn string sn1
# Configure the SN information as sn1 on the LAC.
<Sysname> system-view
[Sysname] interface virtual-ppp 1
[Sysname-Virtual-PPP1] ppp lcp sn string sn1
Related commands
ppp lcp sn accept
ppp lcp sn request
ppp user accept-format imsi-sn split
Use ppp user accept-format imsi-sn split to configure the separator for the received authentication information.
Use undo ppp user accept-format to restore the default.
Syntax
ppp user accept-format imsi-sn split splitchart
undo ppp user accept-format
Default
No separator is configured for the received authentication information.
Views
VT interface view
Predefined user roles
network-admin
Parameters
splitchart: Specifies the separator. The separator contains one character, and it can be a letter, digit, or sign such as the percent sign (%), pound sign (#), and at sign (@).
Usage guidelines
By default, the authentication information contains only the client username. If you include the IMSI or SN information in the authentication information, you must configure the separator to separate different types of information. For example, if you specify the at sign (@) as the separator, the information imsiinfo@sninfo@username will be split into imsiinfo, sninfo, and username.
If no IMSI/SN information is received from the peer during the authentication process, the IMSI/SN information split from the received authentication information is used.
Examples
# Configure the pound sign (#) as the separator for the authentication information.
<Sysname> system-view
[Sysname] interface virtual-template 1
[Sysname-Virtual-Template1] ppp user accept-format imsi-sn split #
Related commands
ppp user attach-format imsi-sn split
ppp user replace
ppp user attach-format imsi-sn split
Use ppp user attach-format imsi-sn split to configure the separator for the sent authentication information.
Use undo ppp user attach-format to restore the default.
Syntax
ppp user attach-format imsi-sn split splitchart
undo ppp user attach-format
Default
No separator is configured for the sent authentication information.
Views
Interface view
Predefined user roles
network-admin
Parameters
splitchart: Specifies the separator. The separator contains one character, and it can be a letter, digit, or sign such as the percent sign (%), pound sign (#), and at sign (@).
Usage guidelines
By default, the authentication information contains only the client username. If you include the IMSI or SN information in the authentication information, you must configure the separator to separate different types of information. For example, if you specify the at sign (@) as the separator, authentication information will be sent in the format of imsiinfo@sninfo@username.
Examples
# Configure the pound sign (#) as the separator for the sent authentication information on the client.
<Sysname> system-view
[Sysname] interface serial 2/1/0:0
[Sysname-Serial2/1/0:0] ppp user attach-format imsi-sn split #
# Configure the pound sign (#) as the separator for the sent authentication information on the LAC.
<Sysname> system-view
[Sysname] interface virtual-ppp 1
[Sysname-Virtual-PPP1] ppp user attach-format imsi-sn split #
Related commands
ppp user accept-format imsi-sn split
ppp user replace
ppp user replace
Use ppp user replace to replace the client username with the IMSI or SN information for authentication.
Use undo ppp user replace to restore the default.
Syntax
ppp user replace { imsi | sn }
undo ppp user replace
Default
The client username is used for authentication.
Views
VT interface view
Predefined user roles
network-admin
Parameters
imsi: Specifies IMSI information.
sn: Specifies SN information.
Examples
# Replace the client username with the IMSI information for authentication.
<Sysname> system-view
[Sysname] interface virtual-template 1
[Sysname-Virtual-Template1] ppp user replace imsi
Related commands
ppp user accept-format imsi-sn split
ppp user attach-format imsi-sn split
reset counters interface virtual-ppp
Use reset counters interface virtual-ppp to clear the statistics for virtual PPP interfaces.
Syntax
reset counters interface [ virtual-ppp [ interface-number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a virtual PPP interface by its number in the range of 0 to 255.
Usage guidelines
Use this command to clear history statistics if you want to collect traffic statistics for a specific time period.
If you specify neither virtual-ppp nor interface-number, this command clears the statistics for all interfaces.
If you specify virtual-ppp but not interface-number, this command clears the statistics for all virtual PPP interfaces.
If you specify both virtual-ppp and interface-number, this command clears the statistics for the specified virtual PPP interface.
Examples
# Clear the statistics for Virtual-PPP 10.
<Sysname> reset counters interface virtual-ppp 10
reset l2tp tunnel
Use reset l2tp tunnel to disconnect tunnels and all sessions within the tunnels.
Syntax
reset l2tp tunnel { id tunnel-id | name remote-name }
Views
User view
Predefined user roles
network-admin
Parameters
id tunnel-id: Specifies a tunnel by its local ID in the range of 1 to 65535.
name remote-name: Specifies L2TP tunnels by the tunnel peer name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
When the number of user connections is 0 or a network fault occurs, you can disconnect the L2TP tunnel by using this command on either the LAC or LNS. After the tunnel is disconnected, all sessions within it are disconnected.
If you specify a tunnel peer name, all tunnels with the tunnel peer name will be disconnected. If no tunnel with the tunnel peer name exists, nothing happens.
A tunnel disconnected by force can be re-established when a client makes a call.
Examples
# Disconnect all tunnels with the tunnel peer name of aaa.
<Sysname> reset l2tp tunnel name aaa
display l2tp tunnel
service
Use service to specify a primary traffic processing slot for an interface.
Use undo service to restore the default.
Syntax
Distributed devices in standalone mode:
service slot slot-number
undo service slot
Default
No primary traffic processing slot is specified for an interface.
Views
Virtual PPP interface view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
Hardware |
Command compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR2600-6-X1-GL |
No |
MSR3600-28-SI-GL |
No |
This command affects only L2TP data messages. The control messages are always processed on the active MPU.
Specify traffic processing slots if a feature requires that all traffic on a virtual PPP 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
# (Distributed devices in standalone mode.) Specify slot 2 as the primary traffic processing slot for Virtual-PPP 10.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] service slot 2
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
Distributed devices in standalone mode:
service standby slot slot-number
undo service standby slot
Default
No backup traffic processing slot is specified for an interface.
Views
Virtual PPP interface view
Default command level
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
Hardware |
Command compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR2600-6-X1-GL |
No |
MSR3600-28-SI-GL |
No |
This command affects only L2TP data messages. The control messages are always processed on the active MPU.
Specify traffic processing slots if a feature requires that all traffic on a virtual PPP 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
# (Distributed devices in standalone mode.) Specify slot 2 as the primary traffic processing slot for Virtual-PPP 10. Specify slot 3 as the backup traffic processing slot for Virtual-PPP 10.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] service slot 2
[Sysname-Virtual-PPP10] service standby slot 3
Related commands
service
shutdown
Use shutdown to shut down a virtual PPP interface.
Use undo shutdown to bring up a virtual PPP interface.
Syntax
shutdown
undo shutdown
Default
A virtual PPP interface is up.
Views
Virtual PPP interface view
Predefined user roles
network-admin
Examples
# Shut down Virtual-PPP 10.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] shutdown
source-ip
Use source-ip to configure the source IP address of L2TP tunnel packets.
Use undo source-ip to restore the default.
Syntax
source-ip ip-address
undo source-ip
Default
The source IP address of L2TP tunnel packets is the IP address of the egress interface.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the source IP address of L2TP tunnel packets.
Usage guidelines
This command is available only on an L2TP group in LAC mode.
As a best practice to ensure high availability, use the IP address of a loopback interface as the source IP address of L2TP tunnel packets.
Examples
# Configure the source IP address of L2TP tunnel packets as 2.2.2.2.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] source-ip 2.2.2.2
timer-hold
Use timer-hold to set the keepalive interval.
Use undo timer-hold to restore the default.
Syntax
timer-hold seconds
undo timer-hold
Default
The keepalive interval is 10 seconds.
Views
Virtual PPP interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval at which the LAC or the LNS sends keepalive packets, in the range of 0 to 32767 seconds.
Usage guidelines
A virtual PPP interface sends keepalive packets at keepalive intervals to detect the availability of the peer. If the interface fails to receive keepalive packets when the keepalive retry limit is reached, it considers the link faulty and reports a link layer down event.
To set the keepalive retry limit, use the timer-hold retry command.
On a slow link, increase the keepalive interval to prevent false shutdown of the interface. This situation might occur when keepalive packets are delayed because a large packet is being transmitted on the link.
Examples
# Set the keepalive interval to 20 seconds for Virtual-PPP 10.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] timer-hold 20
Related commands
timer-hold retry
timer-hold retry
Use timer-hold retry to set the keepalive retry limit.
Use undo timer-hold retry to restore the default.
Syntax
timer-hold retry retries
undo timer-hold retry
Default
The keepalive retry limit is 5.
Views
Virtual PPP interface view
Predefined user roles
network-admin
Parameters
retries: Specifies the maximum number of keepalive attempts in the range of 1 to 255.
Usage guidelines
A virtual PPP interface sends keepalive packets at keepalive intervals to detect the availability of the peer. If the interface fails to receive keepalive packets when the keepalive retry limit is reached, it considers the link faulty and reports a link layer down event.
To set the keepalive interval, use the timer-hold command.
On a slow link, increase the keepalive retry limit to prevent false shutdown of the interface. This situation might occur when keepalive packets are delayed because a large packet is being transmitted on the link.
Examples
# Set the keepalive retry limit to 10 for Virtual-PPP 10.
<Sysname> system-view
[Sysname] interface virtual-ppp 10
[Sysname-Virtual-PPP10] timer-hold retry 10
Related commands
timer-hold
tunnel authentication
Use tunnel authentication to enable L2TP tunnel authentication.
Use undo tunnel authentication to disable L2TP tunnel authentication.
Syntax
tunnel authentication
undo tunnel authentication
Default
L2TP tunnel authentication is enabled.
Views
L2TP group view
Predefined user roles
network-admin
Usage guidelines
Tunnel authentication prevents the local end from establishing L2TP tunnels with illegal remote ends.
You can enable tunnel authentication on both sides or either side.
To ensure a successful tunnel establishment when tunnel authentication is enabled on both sides or either side, set the same non-null key on the LAC and the LNS. To set the tunnel authentication key, use the tunnel password command.
When neither side is enabled with tunnel authentication, the key settings of the LAC and the LNS do not affect the tunnel establishment.
For tunnel security, enable tunnel authentication.
Examples
# Enable L2TP tunnel authentication.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lns
[Sysname-l2tp1] tunnel authentication
Related commands
tunnel password
tunnel avp-hidden
Use tunnel avp-hidden to enable transferring AVP data in hidden mode.
Use undo tunnel avp-hidden to restore the default.
Syntax
tunnel avp-hidden
undo tunnel avp-hidden
Default
AVP data is transferred over the tunnel in plaintext mode.
Views
L2TP group view
Predefined user roles
network-admin
Usage guidelines
L2TP uses AVPs to transmit tunnel negotiation parameters, session negotiation parameters, and user authentication information. This feature can hide sensitive AVP data, such as user passwords. This feature encrypts AVP data with the key configured by using the tunnel password command before transmission.
The tunnel avp-hidden command can be configured for L2TP groups in both LAC and LNS modes. However, it does not take effect on L2TP groups in LNS mode.
For this command to take effect, you must enable tunnel authentication by using the tunnel authentication command.
Examples
# Enable transferring AVP data in hidden mode.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] tunnel avp-hidden
Related commands
tunnel authentication
tunnel password
tunnel flow-control
Use tunnel flow-control to enable L2TP session flow control.
Use undo tunnel flow-control to disable L2TP session flow control.
Syntax
tunnel flow-control
undo tunnel flow-control
Default
L2TP session flow control is disabled.
Views
L2TP group view
Predefined user roles
network-admin
Usage guidelines
This feature adds sequence numbers to transmitted packets and uses them to reorder packets arriving out of order and to detect lost packets.
This feature takes effect on both sent and received L2TP data messages. The L2TP sessions support this feature if either the LAC or LNS is enabled with this feature.
When the device acts as an LAC, a change in the flow control status on the LNS causes the same change in the flow control status of L2TP sessions. When the device acts as an LNS, a change in the flow control status on the LAC does not affect the flow control status of L2TP sessions.
Examples
# Enable L2TP session flow control.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] tunnel flow-control
tunnel name
Use tunnel name to specify the local tunnel name.
Use undo tunnel name to restore the default.
Syntax
tunnel name name
undo tunnel name
Default
The local tunnel name is the device name. For more information about the device name, see Fundamentals Configuration Guide.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
name: Specifies the local tunnel name, a case-sensitive string of 1 to 31 characters.
Examples
# Specify the local tunnel name as itsme.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lns
[Sysname-l2tp1] tunnel name itsme
Related commands
sysname (Fundamentals Command Reference)
tunnel password
Use tunnel password to configure the key for tunnel authentication.
Use undo tunnel password to restore the default.
Syntax
tunnel password { cipher | simple } string
undo tunnel password
Default
No key is configured for tunnel authentication.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the password. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 1 to 53 characters.
Usage guidelines
For this command to take effect, you must enable tunnel authentication by using the tunnel authentication command.
For the tunnel authentication key change to take effect, change the tunnel authentication key before tunnel negotiation is performed.
Examples
# Configure the key for tunnel authentication to a plaintext key yougotit.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] tunnel password simple yougotit
Related commands
tunnel authentication
tunnel timer hello
Use tunnel timer hello to set the Hello interval.
Use undo tunnel timer hello to restore the default.
Syntax
tunnel timer hello hello-interval
undo tunnel timer hello
Default
The Hello interval is 60 seconds.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
hello-interval: Specifies the interval at which the LAC or the LNS sends Hello packets, in the range of 60 to 1000 seconds.
Usage guidelines
When no packet is transmitted between the LAC and LNS, Hello packets are sent at the set interval. This prevents the L2TP tunnels and sessions from being removed due to timeouts.
You can set different Hello intervals for the LNS and LAC.
Examples
# Set the Hello interval to 90 seconds.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] tunnel timer hello 90
tunnel window send
Use tunnel window send to set the sending window size for an L2TP tunnel.
Use undo tunnel window send to restore the default.
Syntax
tunnel window send size
undo tunnel window send
Default
The sending window size for an L2TP tunnel is 0, which means using the value of the receiving window size carried in messages sent by the peer end in the tunnel establishment process.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
size: Specifies the sending window size for an L2TP tunnel, in the range of 0 to 1024. It is the maximum number of packets the device can send to a peer end when the device receives no response from the peer end. If the messages from the peer end carry no receiving window size in the tunnel establishment process, the sending window size for the device is 4.
Usage guidelines
The packet processing capability of a peer end might mismatch the receiving window size of the peer end in some networks. For example, the actual packet processing capability of the peer end is 10, but the receiving window size of the peer end is 20. To ensure stable L2TP services, you can adjust the sending window size for the device to match the actual packet processing capability of the peer end.
The sending window size set in L2TP group view is obtained in the L2TP tunnel establishment process.
· If the sending window size is 0, the device uses the default sending window size.
· If the sending window size is not 0, the device uses the specified value as the sending window size.
Changing the sending window size after an L2TP tunnel is established does not affect the established L2TP tunnel.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the sending window size for L2TP group 1 to 128.
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] tunnel window send 128
user
Use user to configure the condition for the LAC to initiate tunneling requests.
Use undo user to restore the default.
Syntax
user { domain domain-name | fullusername user-name }
undo user
Default
No condition is configured for the LAC to initiate tunneling requests.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
domain domain-name: Configures the LAC to initiate tunneling requests to the LNS when the domain name of a user matches a configured domain name. The domain-name argument represents the domain name of the user and is an case-sensitive string of 1 to 255 characters.
fullusername user-name: Configures the LAC to initiate tunneling requests to the LNS when the username of a user matches a configured full username. The domain-name argument represents the username of the user and is a case-sensitive string of 1 to 255 characters.
Usage guidelines
This command is available only on L2TP groups in LAC mode.
If you execute this command multiple times for an L2TP group, the most recent configuration takes effect.
Examples
# Configure the LAC to initiate tunneling requests to the LNS when the username of the user is [email protected].
<Sysname> system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] user fullusername [email protected]
vpn-instance
Use vpn-instance to assign a tunnel peer to a VPN.
Use undo vpn-instance to restore the default.
Syntax
vpn-instance vpn-instance-name
undo vpn-instance
Default
A tunnel peer belongs to the public network.
Views
L2TP group view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies a VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
This command enables the device to transmit L2TP control messages and data messages in the specified VPN by searching the routing table in that VPN.
When one L2TP endpoint is in a VPN, assign the peer endpoint to the VPN for correct packet forwarding between the two endpoints.
The tunnel peer and the physical port connecting to the tunnel peer should belong to the same VPN. The VPN to which this physical port belongs is configured by using the ip binding vpn-instance command.
The specified VPN must already exist.
Examples
# Assign the tunnel peer to VPN vpn1.
<Sysname>system-view
[Sysname] l2tp-group 1 mode lac
[Sysname-l2tp1] vpn-instance vpn1
Related commands
ip vpn-instance (MPLS Command Reference)
ip binding vpn-instance (MPLS Command Reference)
HDLC commands
This feature is supported only on Layer 2 Ethernet ports on the following modules:
· CE3.
· CPOS.
· CT3.
· E1.
· E1-F.
· POS.
· SAE.
· T1.
· T1-F.
Commands and descriptions for centralized devices apply to the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR2600-6-X1/2600-10-X1.
· MSR 2630.
· MSR3600-28/3600-51.
· MSR3600-28-SI/3600-51-SI.
· MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC.
· MSR 3610/3620/3620-DP/3640/3660.
· MSR810-LM-GL/810-W-LM-GL/830-6EI-GL/830-10EI-GL/830-6HI-GL/830-10HI-GL/2600-6-X1-GL/3600-28-SI-GL.
Commands and descriptions for distributed devices apply to the following routers:
· MSR5620.
· MSR 5660.
· MSR 5680.
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
link-protocol hdlc
Use link-protocol hdlc to enable HDLC encapsulation on an interface.
Syntax
link-protocol hdlc
Default
PPP encapsulation is enabled on an interface.
Views
POS interface view
Serial interface view
Predefined user roles
network-admin
Usage guidelines
HDLC can transport the network layer protocols, such as IP and IPv6.
Examples
# Enable HDLC encapsulation on interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol hdlc
timer-hold
Use timer-hold to set the keepalive interval.
Use undo timer-hold to restore the default.
Syntax
timer-hold seconds
undo timer-hold
Default
The keepalive interval is 10 seconds.
Views
POS interface view
Serial interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the keepalive interval, in the range 0 to 32767 seconds.
Usage guidelines
An HDLC-enabled interface can regularly check link status by sending keepalives to the peer at the keepalive interval at the link layer. A keepalive carries the local sender sequence number and the last received sequence number of the peer.
After sending a keepalive, an interface increments the sender sequence number by 1 in the next keepalive when the following conditions exist:
· The interface receives a response within the keepalive interval.
· The response carries the sender sequence number in the sent keepalive.
After sending a keepalive, if the interface does not receive a response within the keepalive interval, it resends the keepalive with an unchanged sequence number. When the keepalive retry limit is reached, the interface considers the link faulty and reports a link layer down event.
Link status check is disabled if you set the keepalive interval to 0.
As a best practice, set the same keepalive interval for the two ends of a link.
If the network has a long delay or is experiencing congestion, you can increase the keepalive interval to prevent the link from being closed.
Examples
# Set the keepalive interval to 100 seconds on interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-serial2/1/0] timer-hold 100
Related commands
timer-hold retry
timer-hold retry
Use timer-hold retry to set the keepalive retry limit.
Use undo timer-hold retry to restore the default.
Syntax
Default
The keepalive retry limit is 5.
Views
POS interface view
Serial interface view
Pre-defined user roles
Parameters
retries: Specifies the keepalive retry limit, in the range of 1 to 255.
Usage guidelines
An HDLC-enabled interface can regularly check link status by sending keepalives to the peer at the keepalive interval at the link layer. A keepalive carries the local sender sequence number and the last received sequence number of the peer.
After sending a keepalive, an interface increments the sender sequence number by 1 in the next keepalive when the following conditions exist:
· The interface receives a response within the keepalive interval.
· The response carries the sender sequence number in the sent keepalive.
After sending a keepalive, if the interface does not receive a response within the keepalive interval, it resends the keepalive with an unchanged sequence number. When the keepalive retry limit is reached, the interface considers the link faulty and reports a link layer down event.
If the network has a long delay or is experiencing congestion, you can increase the keepalive retry limit to prevent the link from being closed.
Examples
# Set the keepalive retry limit to 10 on Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] timer-hold retry 10
Related commands
HDLC link bundling 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
HDLC link bundle interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth of an interface affects the link costs in OSPF, OSPFv3, and IS-IS. For more information, see Layer 3—IP Routing Configuration Guide.
Examples
# Set the expected bandwidth to 1000 kbps for HDLC link bundle interface 1.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] bandwidth 1000
bundle id
Use bundle id to assign an interface to an HDLC link bundle.
Use undo bundle id to restore the default.
Syntax
bundle id bundle-id
undo bundle id
Default
An interface is not assigned to any HDLC link bundle.
Views
POS interface view
Serial interface view
Predefined user roles
network-admin
Parameters
bundle-id: Specifies an HDLC link bundle by its number in the range of 1 to 10.
Usage guidelines
An interface can be the member of only one HDLC link bundle. To move an interface from one HDLC link bundle to another HDLC link bundle, remove the interface from the current HDLC link bundle first.
You must enable HDLC encapsulation on an interface to be assigned to an HDLC link bundle. You cannot change the link layer protocol encapsulation of an HDLC link bundle member interface.
You can assign interfaces to an HDLC link bundle before you create the HDLC link bundle.
Examples
# Assign POS 2/2/0 to HDLC link bundle 1.
<Sysname> system-view
[Sysname] interface pos 2/2/0
[Sysname-Pos2/2/0] bundle id 1
bundle load-balance
Use bundle load-balance to set the load balancing mode for an HDLC link bundle interface.
Use undo bundle load-balance to restore the default.
bundle load-balance { per-flow | per-packet }
Per-packet load balancing is used.
HDLC link bundle interface view
network-admin
per-flow: Specifies per-flow load balancing.
per-packet: Specifies per-packet load balancing.
The following load balancing modes are available:
¡ For IPv4 and IPv6 packets, the match criteria include source IP address and destination IP address.
¡ For MPLS packets, the match criteria are MPLS labels.
# Set per-flow load balancing mode for HDLC link bundle interface 1.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] bundle load-balance per-flow
bundle max-active links
Use bundle max-active links to set the maximum number of Selected interfaces allowed in an HDLC link bundle.
Use undo bundle max-active links to restore the default.
Syntax
bundle max-active links number
undo bundle max-active links
Default
The maximum number of Selected interfaces allowed in an HDLC link bundle is the maximum number of Selected interfaces supported by the device.
Views
HDLC link bundle interface view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of Selected interfaces allowed in an HDLC link bundle. The value range for this argument is 1 to 16.
Usage guidelines
The value specified by using this command cannot be smaller than the value specified by using the bundle min-active links command.
Use the bundle max-active links command together with the bundle member-priority command to make sure both ends of a link always have the same Selected status. The communication fails when one end is Selected but the other end is Unselected.
Examples
# Set the maximum number of Selected interfaces allowed in HDLC link bundle 1 to 8.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] bundle max-active links 8
Related commands
bundle member-priority
bundle min-active links
bundle member-priority
Use bundle member-priority to set the bundling priority value for an HDLC-enabled interface.
Use undo bundle member-priority to restore the default.
Syntax
bundle member-priority priority
undo bundle member-priority
Default
The bundling priority value of an HDLC-enabled interface is 32768.
Views
POS interface view
Serial interface view
Predefined user roles
network-admin
Parameters
priority: Specifies the bundling priority value of an HDLC-enabled interface. The value range for this argument is 1 to 65535. A higher priority value means a lower bundling priority.
Examples
# Set the bundling priority value to 1 for HDLC-enabled interface POS 2/2/0.
<Sysname> system-view
[Sysname] interface pos 2/2/0
[Sysname-Pos2/2/0] bundle member-priority 1
bundle min-active bandwidth
Use bundle min-active bandwidth to set the minimum bandwidth required for bringing up an HDLC link bundle interface.
Use undo bundle min-active bandwidth to restore the default.
Syntax
bundle min-active bandwidth bandwidth
undo bundle min-active bandwidth
Default
The minimum bandwidth required for bringing up an HDLC link bundle is not set.
Views
HDLC link bundle interface view
Predefined user roles
network-admin
Parameters
bandwidth: Specifies the minimum bandwidth (in kbps) required for bringing up an HDLC link bundle interface. The value range for this argument is 64 to 1342177280.
Examples
# Set the minimum bandwidth required for bringing up HDLC link bundle 1 to 1000 kbps.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] bundle min-active bandwidth 1000
bundle min-active links
Use bundle min-active links to set the minimum number of Selected interfaces required for bringing up an HDLC link bundle interface.
Use undo bundle min-active links to restore the default.
Syntax
bundle min-active links number
undo bundle min-active links
Default
The minimum number of Selected interfaces required for bringing up an HDLC link bundle is not set.
Views
HDLC link bundle interface view
Predefined user roles
network-admin
Parameters
number: Specifies the minimum number of Selected interfaces required for bringing up an HDLC link bundle interface. The value range for this argument is 1 to 16.
Usage guidelines
The value specified by using this command cannot be greater than the value specified by using the bundle max-active links command.
Examples
# Set the minimum number of Selected interfaces required for bringing up HDLC link bundle 1 to 5.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] bundle min-active links 5
Related commands
bundle max-active links
default
Use default to restore the default settings for an HDLC link bundle interface.
Syntax
default
Views
HDLC link bundle 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 when you use 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, and then use their undo forms 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 for HDLC link bundle interface 1.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] default
description
Use description to set the description of an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of an interface is the interface name followed by the Interface string, for example, Hdlc-bundle1 Interface.
HDLC link bundle interface view
Predefined user roles
network-admin
Parameters
text: Specifies an interface description, a case-sensitive string of 1 to 255 characters.
Examples
# Set the description of HDLC link bundle interface 1 to HDLC-bundle interface.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] description HDLC-bundle interface
display bundle hdlc-bundle
Use display bundle hdlc-bundle to display information about an HDLC link bundle.
Syntax
Centralized devices in standalone mode:
display bundle hdlc-bundle [ bundle-id ]
Distributed devices in standalone mode/centralized devices in IRF mode:
display bundle hdlc-bundle [ bundle-id ] slot slot-number
Distributed devices in IRF mode:
display bundle hdlc-bundle [ bundle-id ] chassis chassis-number slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
bundle-id: Specifies an HDLC link bundle by its number. If this argument is not specified, this command displays information for all HDLC link bundles.
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)
Usage guidelines
The HDLC link bundle information displayed for the active MPU includes information about all member interfaces.
The information displayed for the standby MPUs or any other interface card includes only information about Selected interfaces.
Examples
# (Centralized devices in standalone mode.) Display information about HDLC link bundle 1 on the active MPU.
<Sysname> display bundle hdlc-bundle 1
Bundle: HDLC-bundle1
max-active links: 2, min-active links: 2, min-active bandwidth: 1000000 kbps
Selected members: 2, Total bandwidth: 311040 kbps
Member State Bandwidth(kbps) Priority
Pos2/1 Selected 155520 1
Pos2/2 Selected 155520 2
Pos2/4 Ready 155520 32768
Pos2/3 Ready 155520 65535
Pos2/5 Ready 155520 32768
Pos2/6 Ready 155520 32768
# (Distributed devices in standalone mode.) Display information about HDLC link bundle 1 on the interface card in slot 2.
<Sysname> display bundle hdlc-bundle 1 slot 2
Bundle: HDLC-bundle1, slot 2
max-active links: 2, min-active links: 2, min-active bandwidth: 1000000 kbps
Selected members: 2, Total bandwidth: 311040 kbps
Member State Bandwidth(kbps) Priority
Pos2/1 Selected 155520 1
Pos2/2 Selected 155520 2
# (Centralized devices in IRF mode.) Display information about HDLC link bundle interface 1 on IRF member device 1.
<Sysname> display bundle hdlc-bundle 1 slot 1
Bundle: HDLC-bundle1, slot 1
max-active links: 2, min-active links: 2, min-active bandwidth: 1000000 kbps
Selected members: 2, Total bandwidth: 311040 kbps
Member State Bandwidth(kbps) Priority
Pos2/1 Selected 155520 1
Pos2/2 Selected 155520 2
# (Distributed devices in IRF mode.) Display information about HDLC link bundle 1 on the interface card in slot 2 of IRF member device 1.
<Sysname> display bundle hdlc-bundle 1 chassis 1 slot 2
Bundle: HDLC-bundle1, chassis 1, slot 2
max-active links: 2, min-active links: 2, min-active bandwidth: 1000000 kbps
Selected members: 2, Total bandwidth: 311040 kbps
Member State Bandwidth(kbps) Priority
Pos2/1 Selected 155520 1
Pos2/2 Selected 155520 2
Table 23 Command output
Field |
Description |
Bundle |
Name of the HDLC link bundle. |
chassis |
ID of the IRF member device for which HDLC link bundling information is displayed. |
slot |
Slot number of the interface card for which HDLC link bundling information is displayed. (Distributed devices in standalone mode.) ID of the IRF member device for which HDLC link bundling information is displayed. (Centralized devices in IRF mode.) |
max-active links |
Maximum number of Selected interfaces allowed in the HDLC link bundle interface. This field will not be displayed if you have not set the limit. |
min-active links |
Minimum number of Selected interfaces required for bringing up the HDLC link bundle interface. This field will not be displayed if you have not set the limit. |
min-active bandwidth |
Minimum bandwidth required for bringing up the HDLC link bundle interface. This field will not be displayed if you have not set the limit. |
Selected members |
Current number of Selected interfaces. |
Total bandwidth |
Total bandwidth of all the Selected interfaces in the HDLC link bundle. |
Member |
Name of a member interface. |
State of a member interface: · Selected—On an interface card, only information about Selected interfaces is displayed. · Ready. · Negotiated. · Initial. |
|
Bandwidth(kbps) |
Bandwidth (in kbps) of a member interface. |
Priority |
Bundling priority of a member interface. |
display interface hdlc-bundle
Use display interface hdlc-bundle to display information about an HDLC link bundle interface.
Syntax
display interface [ hdlc-bundle [ bundle-id ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
bundle-id: Specifies an HDLC link bundle interface by its number.
brief: Displays brief interface information. If you do not specify this keyword, this command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of each interface description.
down: Displays information about interfaces in DOWN state and the link down causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Usage guidelines
If you do not specify the hdlc-bundle keyword, this command displays information about all interfaces.
If you specify the hdlc-bundle keyword without any HDLC link bundle interface number, this command displays information about all HDLC link bundle interfaces.
Examples
# Display detailed information about HDLC link bundle interface 1.
<Sysname> display interface hdlc-bundle 1
HDLC-bundle1
Current state: UP
Line protocol state: UP
Description: HDLC-bundle1 Interface
Bandwidth: 128kbps
Maximum Transmit Unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet address: 1.1.1.1/24 (primary)
Link layer protocol: HDLC
Physical: HDLC-BUNDLE, baudrate: 128000 bps
Port priority: 0
Output queue - Urgent queuing: Size/Length/Discards 0/1024/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 32 packets, 1842 bytes, 0 drops
Output: 27 packets, 1512 bytes, 0 drops
# Display brief information about HDLC link bundle interface 1.
<Sysname> display interface hdlc-bundle 1 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
HDLC-B1 UP UP 1.1.1.2
# Display information about all HDLC link bundle interfaces in down state and the link down reasons.
<Sysname> display interface hdlc-bundle brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
HDLC-B2 ADM Administratively
Table 24 Command output
Field |
Description |
Current state |
Physical state and administrative state of the HDLC link bundle interface: · DOWN (Administratively)—The interface is shut down by using the shutdown command (the interface is administratively down). · DOWN—The interface is administratively up but physically down. · UP—The interface is up both administratively and physically. |
Line protocol state |
Link layer protocol state of the HDLC link bundle interface: · DOWN—The link layer protocol of the interface is down, typically because the HDLC link bundle interface does not have any Selected interface. · UP—The link layer protocol of the interface is up. |
Description |
Description of the HDLC link bundle interface. |
Bandwidth |
Expected bandwidth of the HDLC link bundle interface. |
Maximum Transmit Unit |
MTU on the HDLC link bundle interface. |
Hold timer |
Keepalive transmission interval of the interface. This field is ineffective for an HDLC link bundle interface because an HDLC link bundle interface does not transmit keepalives. |
Retry times |
Keepalive retry limit. This field is ineffective for an HDLC link bundle interface because an HDLC link bundle interface does not transmit keepalives. |
Internet address: 1.1.1.1/24 (primary) |
IP address of the HDLC link bundle interface. If no IP address is configured for the interface, this field is replaced with Internet protocol processing: disabled. |
Link layer protocol |
Link layer protocol encapsulation on the HDLC link bundle interface. |
Physical |
Physical type of the HDLC link bundle interface. |
Baudrate |
Baudrate of the HDLC link bundle interface. |
Output queue - Urgent queuing: Size/Length/Discards 0/1024/0 Output queue - Protocol queuing: Size/Length/Discards 0/500/0 Output queue - FIFO queuing: Size/Length/Discards 0/75/0 |
Traffic statistics for each output queue on the HDLC link bundle interface, including: · The number of packets in the queue (the queue size). · The maximum number of packets that the queue can hold (queue length). · The number of dropped packets. The output queues on the HDLC link bundle interface include the following types: · Urgent queue. · Protocol queue. · FIFO queue. |
Last clearing of counters |
Time when the reset counters interface command was last used to clear the interface statistics. This field displays Never if the reset counters interface command has never been used on the interface since device startup. |
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec |
Average incoming and outgoing traffic rates on the interface in the last 300 seconds. |
Input: 32 packets, 1842 bytes, 0 drops |
Incoming traffic size in packets and bytes and the number of dropped incoming packets on the interface. |
Outgoing traffic size in packets and bytes and the number of dropped outgoing packets on the interface. |
|
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
Link: ADM - administratively down; Stby - standby |
Link status: · ADM—The interface has been administratively shut down. To recover its physical state, perform the undo shutdown command. · Stby—The interface is operating as a backup interface. To see the primary interface, use the display interface-backup state command. |
Protocol: (s) – spoofing |
If the data link layer protocol state of an interface is shown as UP, but its link is an on-demand link or not present at all, the protocol attribute includes the spoofing flag (an s in parentheses). |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is up. · ADM—The interface has been administratively shut down. To bring up the interface, perform the undo shutdown command. |
Protocol |
Date link layer protocol state of the interface: · UP—The data link layer protocol state of the interface is up. · DOWN—The data link layer protocol state of the interface is down. · UP(s)—The data link layer protocol state of the interface is shown as UP, but its link is an on-demand link or not present at all. |
Primary IP |
Primary IP address of the interface. Two hyphens (--) indicate that no primary IP address is configured for the interface. |
Description |
Partial or complete interface description configured by using the description command: · If the description keyword is not specified for the display interface brief command, this field displays only the first 27 characters of the interface description. · If the description keyword is specified for the display interface brief command, this field displays the complete interface description. |
Cause |
Reason why a physical link is down. If the port has been shut down by using the shutdown command, this field displays Administratively. To restore the physical state of the interface, use the undo shutdown command. |
Related commands
interface hdlc-bundle
Use interface hdlc-bundle to create an HDLC link bundle interface and enter its view, or enter the view of an existing HDLC link bundle interface.
Use undo interface hdlc-bundle to delete an HDLC link bundle interface.
Syntax
interface hdlc-bundle bundle-id
undo interface hdlc-bundle bundle-id
Default
No HDLC link bundle interface exists.
Views
System view
Predefined user roles
network-admin
Parameters
bundle-id: Specifies an HDLC link bundle interface by its number in the range of 1 to 10.
Examples
# Create HDLC link bundle interface 1 and enter its view.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1]
mtu
Use mtu to set the MTU size for an HDLC link bundle interface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU size of an HDLC link bundle interface is 1500 bytes.
Views
HDLC link bundle interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU in bytes for an HDLC link bundle interface, in the range of 46 to 1560.
Usage guidelines
The MTU size of an interface affects IP packet fragmentation and reassembly on the interface.
To make the MTU configuration take effect on an interface, you must re-enable the interface by using the shutdown command and the undo shutdown command.
Examples
# Set the MTU size of HDLC link bundle interface 1 to 1430 bytes.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] mtu 1430
reset counters interface
Use reset counters interface to clear the statistics of an HDLC link bundle interface.
Syntax
reset counters interface [ hdlc-bundle [ bundle-id ] ]
Views
User view
Predefined user roles
network-admin
Parameters
bundle-id: Specifies an HDLC link bundle interface by its number in the range of 1 to 10.
Usage guidelines
Before collecting traffic statistics within a period of time on an interface, you must clear the existing statistics.
If you do not specify hdlc-bundle, this command clears the statistics of all interfaces.
If you specify hdlc-bundle but not bundle-id, this command clears the statistics of all HDLC link bundle interfaces.
If you specify both hdlc-bundle and bundle-id, this command clears the statistics of the specified HDLC link bundle interface.
Examples
# Clear the statistics of HDLC link bundle interface 1.
<Sysname> reset counters interface hdlc-bundle 1
service
Use service to specify a primary traffic processing slot for an interface.
Use undo service to restore the default.
Syntax
Distributed devices in standalone mode/centralized devices in IRF mode:
service slot slot-number
undo service slot
Distributed devices in IRF mode:
service chassis chassis-number slot slot-number
undo service chassis
Default
No primary traffic processing slot is specified for an interface.
Views
HDLC link bundle interface view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device. The slot-number argument represents its IRF member ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument refers to the ID of the IRF member device. The slot-number argument refers to the number of the slot where the card resides. (Distributed devices in IRF mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
No |
||
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
This command is supported on distributed devices and IRF-capable centralized devices.
Specify traffic processing slots if a feature requires that all traffic on an HDLC link bundle 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
# (Distributed devices in standalone mode.) Specify a primary traffic processing slot for HDLC link bundle interface 1.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] service slot 1
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
Distributed devices in standalone mode/centralized devices in IRF mode:
service standby slot slot-number
undo service standby slot
Distributed devices in IRF mode:
service standby chassis chassis-number slot slot-number
undo service standby chassis
Default
No backup traffic processing slot is specified for an interface.
Views
HDLC link bundle interface view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device. The slot-number argument represents its IRF member ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument refers to the ID of the IRF member device. The slot-number argument refers to the number of the slot where the card resides. (Distributed devices in IRF mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
This command is supported on distributed devices and IRF-capable centralized devices.
Specify traffic processing slots if a feature requires that all traffic on an HDLC link bundle 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
# (Distributed devices in standalone mode.) Specify a primary traffic processing slot and a backup traffic processing slot for HDLC link bundle interface 1.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname--HDLC-bundle1] service slot 2
[Sysname- HDLC-bundle1] service standby slot 3
Related commands
service
shutdown
Use shutdown to shut down an HDLC link bundle interface.
Use undo shutdown to bring up an HDLC link bundle interface.
Syntax
shutdown
undo shutdown
Default
An HDLC link bundle interface is up.
Views
HDLC link bundle interface view
Predefined user roles
network-admin
Usage guidelines
When an HDLC link bundle interface is brought up, the state of each member interface is re-determined.
When an HDLC link bundle interface is shut down, the state of each Selected interface is placed into the Negotiated state.
Examples
# Shut down HDLC link bundle interface 1.
<Sysname> system-view
[Sysname] interface hdlc-bundle 1
[Sysname-HDLC-bundle1] shutdown
ISDN commands
This feature is supported only on routers installed with the BS, E1, or T1 interface modules.
Before you can use a CE1/PRI or CT1/PRI interface to provide ISDN PRI services, you must use the pri-set command to bundle timeslots into channel sets on the interface. For each PRI set, the system creates a serial interface automatically. To configure ISDN settings for a PRI set, you must enter the view of this serial interface.
For more information about timeslot bundling, see the WAN interface section in Interface Configuration Guide.
display isdn active-channel
Use display isdn active-channel to display information about successful calls on ISDN interfaces.
Syntax
display isdn active-channel [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an ISDN BRI or PRI interface by its type and number. If you do not specify an interface, the command displays information about successful calls for all ISDN interfaces.
Examples
# Display information about successful Q.931 calls on BRI 2/4/0.
<Sysname> display isdn active-channel interface bri 2/4/0
Bri 2/4/0
Channel Info: B1
Call Property: Analog
Call Type: Out
Calling Number: 1111
Calling Subaddress:
Called Number: 2222
Called Subaddress:
Start Time: 13-03-14 15:22:26
Time Used: 00:01:10
# Display information about successful Q.931 calls on PRI interface Serial 2/3/0:15.
<Sysname> display isdn active-channel interface serial 2/3/0:15
Serial2/3/0:15
Serial2/3/0:15
Channel Info: B2
Call Property: Digital
Call Type: Out
Calling Number: 8306001
Calling Subaddress:
Called Number: 8306002
Called Subaddress:
Start Time: 13-02-14 12:22:26
Time Used: 00:11:20
Field |
Description |
Channel Info |
B-channel for the call. |
Call Property |
Call property: · Digital. · Analog. |
Call Type |
Call type: · Incoming call. · Outgoing call. In ISDN, "incoming" and "outgoing" describe a call as viewed by the user side of the interface. |
Start Time |
Time when the call was established. |
Time Used |
Duration of the connection since the call was established. |
display isdn call-info
Use display isdn call-info to display information about calls on ISDN interfaces.
Syntax
display isdn call-info [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an ISDN BRI or PRI interface by its type and number. If you do not specify an interface, the command displays call information for all ISDN interfaces.
Usage guidelines
The command displays information about each ISDN layer, including Q.921, Q.931, and CC. When a call setup fails, you can use the command to identify the layer that caused the failure.
Examples
# Display call information for BRI 2/4/0.
<Sysname> display isdn call-info interface bri 2/4/0
Bri2/4/0(User-side): ACTIVE
Link Layer 1: TEI = 65, State = MULTIPLE_FRAME_ESTABLISHED
Link Layer 2: TEI = NONE, State = TEI_UNASSIGNED
Link Layer 3: TEI = NONE, State = TEI_UNASSIGNED
Link Layer 4: TEI = NONE, State = TEI_UNASSIGNED
Link Layer 5: TEI = NONE, State = TEI_UNASSIGNED
Link Layer 6: TEI = NONE, State = TEI_UNASSIGNED
Link Layer 7: TEI = NONE, State = TEI_UNASSIGNED
Link Layer 8: TEI = NONE, State = TEI_UNASSIGNED
Network Layer: 1 connections
Connection 1:
CallID: 0x0001, State: ACTIVE, CES: 1, Channel: 0x00000001
TEI: 65
Calling_Num[:Sub]: 2014:1325
Called_Num[:Sub]: 50401:24136
# Display call information for PRI interface Serial 2/3/0:15.
<Sysname> display isdn call-info interface serial 2/3/0:15
Serial2/3/0:15(User-side):
Link Layer 1: TEI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Network Layer: 1 connections
Connection 1:
CallID: 0x0000ffff, State: ACTIVE, CES: 1, Channel: 0x00200000
TEI: 0
Calling_Num[:Sub]: 8306001
Called_Num[:Sub]: 8305001
Table 26 Command output
Field |
Description |
Bri2/4/0(User-side): ACTIVE |
Physical layer activation state of the interface: · ACTIVE—The physical layer is active. · DEACTIVE—The physical layer is inactive. The command displays the physical layer activation state only for BRI interfaces. The physical layer of a BRI interface is activated only when it receives an activation request from Q.931. However, the physical layer of a PRI interface does not require an activation request. It becomes active when the physical link comes up. The ISDN role of the interface is bracketed. |
Link Layer |
Data link connections on the ISDN interface. ISDN establishes a connection for each terminal and uses a TEI to identify each connection. A BRI interface can have eight connections, but a PRI interface can have only one connection. |
TEI |
Terminal endpoint identifier that identifies an end-user terminal such as an ISDN phone. TEIs are assigned by the network side. |
State |
Data link layer state: · TEI_UNASSIGNED—No TEI is assigned to the data link connection. · ASSIGN_AWAITING_TEI—The data link layer is waiting for TEI assignment. · ESTABLISH_AWAITING_TEI—The data link layer is waiting for TEI assignment and multiple-frame establishment. · TEI_ASSIGNED—A TEI has been assigned to the data link connection. · AWAITING_ESTABLISHMENT—The data link layer is waiting for multiple-frame establishment. · MULTIPLE_FRAME_ESTABLISHED—The multiple-frame operation is successful. The Send Sequence Number and the Receive Sequence Number for Q.921 frames are synchronized. · TIMER_RECOVER—On timer expiration, the data link layer is attempting to recover the link. · AWAITING_RELEASE—The data link layer is waiting for the multiple-frame operation to be released. · TEI_ASSIGNED_EXT1—The data link layer receives a deactivation instruction from the physical layer when the data link connection is present. · TEI_ASSIGNED_EXT2—The data link layer receives a multiple-frame operation request for a new call. |
Network Layer: 1 connections |
A Q.931 network layer connection is present on the interface. |
CallID |
Index of the call at the CC layer. |
State |
Layer 3 call control state: · NULL—Initial state. No call exists. · CALL_INITIATED—The user has initiated a call establishment, but the network has not answered yet. · OVERLAP_SENDING—Q.931 sends called number information in overlap mode. In this mode, called number information can be absent or incomplete in the outgoing SETUP messages. · OUTGOING_CALL_PROCEEDING—The user has sent all information required for call establishment. This state is available for outgoing calls. · CALL_DELIVERED—The network side has initiated remote user alerting, but it has not answered the call yet. This state is available for outgoing calls. · CALL_PRESENT—The user has received a call establishment request from the network, but it has not responded yet. This state is available for incoming calls. · CALL_RECEIVED—The user has indicated alerting for a call, but it has not answered the call yet. This state is available for incoming calls. · CONNECT_REQUEST—The user has answered the call, but the network has not awarded the call yet. This state is available for incoming calls. · INCOMING_CALL_PROCEEDING—The user has received all information necessary for call setup. This state is available for incoming calls. · ACTIVE—For an incoming call, this state indicates that the network has awarded the call. For an outgoing call, this state indicates that the remote user has answered the call. · DISCONNECT_REQUEST—The user has requested the network to clear the end-to-end connection. · DISCONNECT_INDICATION—The user received an instruction to disconnect the call because the network has disconnected the end-to-end connection. · SUSPEND_REQUEST—The user has requested the network to suspend the call. · RESUME_REQUEST—The user has requested the network to resume the suspended call. · RELEASE_REQUEST—The user has requested the network to release the call. · OVERLAP_RECEIVING—Q.931 receives called-number information in overlap mode. |
CES |
Connection endpoint suffix used between Q.931 and Q.921 to identify a call connection. |
Channel |
Bitmap of the ISDN B-channel for the call. Each bit in the bitmap represents a B channel. If a bit is set to 1, the B channel is used. |
Calling_Num[:Sub] |
Calling number and calling subaddress. |
Called_Num[:Sub] |
Called number and called subaddress. |
display isdn call-record
Use display isdn call-record to display the history records for ISDN calls.
Syntax
display isdn call-record [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an ISDN BRI or PRI interface by its type and number. If you do not specify an interface, the command displays call history records for all ISDN interfaces.
Usage guidelines
The command displays the most recent 100 history records for successful ISDN calls.
Examples
# Display ISDN call history records.
<Sysname> display isdn call-record
Type Caller Called Start time End time Duration(s)
Out - 232303 13-03-20 14:10:12 - 273
In - 262609 13-03-20 14:04:50 13-03-20 14:08:54 244
Out - 232303 13-03-20 14:00:47 13-03-20 14:04:07 200
In 232303 262609 13-03-20 13:48:15 13-03-20 13:49:06 51
Out 262609 232303 13-03-20 13:46:39 13-03-20 13:47:31 52
Table 27 Command output
Field |
Description |
Type |
Call type: · In—Incoming call. · Out—Outgoing call. In ISDN, "incoming" and "outgoing" describe a call as viewed by the user side of the interface. |
Caller |
Calling number. |
Called |
Called number. |
Start time |
Time when the call was established. |
End time |
Time when the call was terminated. |
Duration |
Duration (in seconds) of the connection since the call was established. |
display isdn parameters
Use display isdn parameters to display ISDN Layer 2 and Layer 3 parameters.
Syntax
display isdn parameters { protocol | interface interface-type interface-number }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
protocol: Specifies an ISDN protocol. Available options include 5ess, ansi, at&t, dss1, etsi, ni, ni2, ntt, and qsig. If you specify a protocol, the command displays the default parameters for the protocol.
interface interface-type interface-number: Specifies an ISDN BRI or PRI interface by its type and number. If you specify an interface, the command displays the ISDN Layer 2 and Layer 3 parameters for the specified interface.
Examples
# Display the default DSS1 parameters.
<Sysname> display isdn parameters dss1
DSS1 ISDN Layer 2 system parameters:
T200(sec) T201(sec) T202(sec) T203(sec) N200 K(BRI) K(PRI)
1 1 2 10 3 1 7
DSS1 ISDN Layer 3 system timers(default values):
Timer Value(sec)
T301 240
T302 15
T303 4
T304 30
T305 30
T308 4
T309 90
T310 40
T313 4
T322 4
# Display the ISDN parameters for PRI interface Serial 2/3/0:15.
<Sysname> display isdn parameters interface serial 2/3/0:15
Serial2/3/0:15(Network-side):
QSIG ISDN Layer 2 system parameters:
T200(sec) T201(sec) T202(sec) T203(sec) N200 K(PRI)
1 1 2 10 3 7
QSIG ISDN Layer 3 system timers:
Timer Value(sec)
T301 35
T302 37
T303 8
T304 50
T305 20
T308 3
T309 130
T310 130
T313 6
T322 8
Field |
Description |
T200(sec) |
Q.921 T200 timer sets the retransmission interval (in seconds). |
T201(sec) |
Q.921 T201 timer sets the minimum interval (in seconds) between the retransmissions of a TEI Identity check message. |
T202(sec) |
Q.921 T202 timer sets the minimum interval (in seconds) between transmissions of TEI Identity request messages. |
T203(sec) |
Q.921 T203 timer sets the maximum amount of time that the data link can be idle. |
N200 |
Q.921 N200 counter sets the maximum number of retransmissions. |
K(BRI) |
Maximum number of unacknowledged frames (sliding window size) on the ISDN BRI interface. |
K(PRI) |
Maximum number of unacknowledged frames (sliding window size) on the ISDN PRI interface. |
display isdn spid
Use display isdn spid to display SPID information for NI-enabled BRI interfaces.
Syntax
display isdn spid [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies a BRI interface that runs the NI protocol. If you do not specify an interface, the command displays SPID information for all NI-enabled BRI interfaces.
Examples
# Display SPID information for NI-enabled interface BRI 2/4/0 (the SPID type is AUTO).
<Sysname> display isdn spid interface bri 2/4/0
Interface Bri2/4/0:
SPID Type: AUTO
SPID B1:
SPID Num: 235
Neg State: SPID_UNASSIGNED
Init State: INIT_NULL
SPID B2:
SPID Num: 326
Neg State: SPID_UNASSIGNED
Init State: INIT_NULL
SPID timer: 30 seconds
SPID resend: 1 times
# Display SPID information for NI-enabled interface BRI 2/4/0 (the SPID type is STATIC).
<Sysname> display isdn spid interface bri 2/4/0
Interface Bri2/4/0:
SPID Type: STATIC
SPID B1:
SPID Num: 134
LDN: 3251
Init State: INIT_NULL
SPID B2:
SPID Num: 257
LDN: 3657
Init State: INIT_NULL
SPID timer: 30 seconds
SPID resend: 1 times
# Display SPID information on NI-enabled interface BRI 2/4/0 (the SPID type is NIT).
<Sysname> display isdn spid interface bri 2/4/0
Interface Bri2/4/0:
SPID Type: NIT
Table 29 Command output
Field |
Description |
SPID Type |
SPID assignment type: · NIT—Not initial terminal mode. You must enable NIT mode on the BRI interface if the NI-type service provider switch does not support SPID negotiation. · STATIC—Static SPID assignment. You must manually configure the SPIDs assigned by the service provider on the BRI interface. · AUTO—Dynamic SPID assignment. The interface obtains SPIDs dynamically from the service provider switch. |
SPID B1 |
SPID information for the B1 channel on the BRI interface. |
SPID B2 |
SPID information for the B2 channel on the BRI interface. |
SPID Num |
SPID value. It is manually configured or dynamically obtained from the service provider, depending on the SPID assignment type. |
LDN |
Local dialing number. You must configure an LDN depending on the service provider requirement. |
Neg State |
SPID negotiation state: · SPID_UNASSIGNED—The SPID is not assigned, or the SPID assignment has failed. · ASSIGN_AWAITING_SPID—The user terminal has initiated an auto-SPID request and is waiting for SPID assignment. · SPID_ASSIGNED—The user terminal has selected one SPID from the SPID options provided by the network. · ASSIGN_AWAITING_CALL_CLEAR—The B-channel transits to this state if a call is present when it receives an Auto-SPID request. |
Init State |
Layer 3 initialization state for the SPID: · INIT_NULL—No Layer 3 initialization has occurred. · INIT_IND—The service provider switch starts Layer 3 initialization. · INIT_PROCEEDING—Layer 3 is initializing. · INIT_END—Layer 3 initialization is finished successfully. · INIT_AWAITING_CALL_CLEAR—The B-channel transits to this state if a call is present when Q.931 receives a Layer 3 initialization request. |
SPID timer |
TSPID timer. This timer sets the maximum interval that ISDN waits for a response after it sends an INFORMATION message. To configure this timer, use the isdn spid timer command. |
SPID resend |
Maximum number of INFORMATION retransmissions. To configure this counter, use the isdn spid resend command. |
isdn bch-local-manage
Use isdn bch-local-manage to enable an ISDN interface to select ISDN B-channels for calls.
Use undo isdn bch-local-manage to restore the default.
Syntax
isdn bch-local-manage [ exclusive ]
undo isdn bch-local-manage
Default
B-channel selection is disabled on ISDN interfaces. The service provider switch selects B-channels for calls.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
exclusive: Specifies exclusive B-channel selection. If you do not specify this keyword, the command enables non-exclusive B-channel selection.
Usage guidelines
Typically, B-channel selection is done by the service provider switch. To improve call establishment efficiency and reduce call losses on ISDN lines, you can enable the ISDN interface to select B-channels for calls. This is particularly true for PRI ISDN lines.
· If non-exclusive B-channel selection is enabled, the interface selects a preferred B-channel for a call. However, it will use the B-channel selected by the peer end when a selection conflict occurs.
· If exclusive B-channel selection is enabled, the interface selects a preferred B-channel for a call. It does not accept the B-channel selected by the peer end when a selection conflict occurs.
IMPORTANT: Configure exclusive B-channel selection only when the interface is in network mode. In user mode, exclusive B-channel selection will cause a call establishment failure when a B-channel selection conflict occurs. |
Examples
# Enable non-exclusive B-channel selection on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn bch-local-manage
isdn bch-select-way
Use isdn bch-select-way to set a B-channel selection method.
Use undo isdn bch-select-way to restore the default.
Syntax
isdn bch-select-way { ascending | descending }
undo isdn bch-select-way
Default
The device selects B channels in ascending order of channel IDs.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
ascending: Selects ISDN B channels in ascending order of channel IDs.
descending: Selects ISDN B channels in descending order of channel IDs.
Usage guidelines
If the interface is operating in user mode, this command takes effect only when the isdn bch-local-manage command is configured.
Examples
# Set the B channel selection method to descending order on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn bch-select-way descending
Related commands
isdn bch-local-manage
isdn bri-slipwnd-size
Use isdn bri-slipwnd-size to set the sliding window size on an ISDN BRI interface.
Use undo isdn bri-slipwnd-size to restore the default.
Syntax
isdn bri-slipwnd-size window-size
undo isdn bri-slipwnd-size
Default
The sliding window size is 1 on an ISDN BRI interface.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
window-size: Specifies a sliding window size in the range of 1 to 7.
Usage guidelines
Q.921 sends frames in order of their sequence numbers and requires an acknowledgment of each transmitted frame. The sliding window mechanism enables Q.921 to send multiple continuous frames without waiting for the acknowledgment of the previous frame. The sliding window size sets the maximum number of unacknowledged frames. You can tune the size depending on the link status to maximize the throughput.
When sending a frame, Q.921 checks the number of unacknowledged frames. Suppose V(A) is the sequence number of the previous acknowledged frame, V(S) is the sequence number of the frame to be sent, and k is the sliding window size. If V(A) + k = V(S), the system stops sending frames.
Examples
# Set the sliding window size to 7 on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn bri-slipwnd-size 7
Related commands
isdn pri-slipwnd-size
isdn caller-number
Use isdn caller-number to configure calling number verification for incoming calls.
Use undo isdn caller-number to restore the default.
Syntax
isdn caller-number caller-number
undo isdn caller-number
Default
An ISDN interface accepts calls from any calling numbers.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
caller-number: Specifies an acceptable calling number, a case-insensitive string of 1 to 24 characters.
Usage guidelines
Calling number verification enables an ISDN interface to accept calls only from a specific calling party.
Call setup will fail in the following situations:
· The calling number in the incoming SETUP message is not configured on the ISDN interface.
· The incoming SETUP message does not include a calling number.
Examples
# Configure BRI 2/4/0 to accept incoming calls only from the calling number 400.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn caller-number 400
Related commands
isdn calling
isdn calling
Use isdn calling to configure ISDN calling number identification.
Use undo isdn calling to restore the default.
Syntax
isdn calling calling-number
undo isdn calling
Default
ISDN interfaces do not send a calling number in outgoing SETUP messages for any services except voice services.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
calling-number: Specifies a calling number, a case-insensitive string of 1 to 24 characters.
Usage guidelines
ISDN calling number identification enables an ISDN interface to include the call number of a calling party in the outgoing call SETUP messages. The calling number information can be used for different purposes. For example, the service provider can use this information to identify the pricing scheme for the calling party. The called party can use this information to verify the origin of calls.
For the called party to receive the calling number, the connected service provider switch must support transmitting calling numbers.
As a best practice, do not configure the calling number to be sent for voice services.
Examples
# Configure BRI 2/4/0 to include 8060170 as the calling number in outgoing SETUP messages.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn calling 8060170
Related commands
display isdn call-info
isdn caller-number
isdn carry calling-name
Use isdn carry calling-name to configure ISDN to include the calling-name field in outgoing packets on an ISDN interface.
Use undo isdn carry calling-name to restore the default.
Syntax
isdn carry calling-name
undo isdn carry calling-name
Default
ISDN does not include the calling-name field in outgoing packets on an ISDN interface.
Views
ISDN interface view
Predefined user roles
network-admin
Usage guidelines
The command enables a called party to identify the name of a calling party attached to the interface.
You can execute the command only when no call is present on the ISDN interface.
Examples
# Configure ISDN to include the calling-name field in outgoing packets on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn carry calling-name
Related commands
isdn carry connected-name
isdn carry connected-name
Use isdn carry connected-name to configure ISDN to include the connected-name field in outgoing packets on an ISDN interface.
Use undo isdn carry connected-name to restore the default.
Syntax
isdn carry connected-name
undo isdn carry connected-name
Default
ISDN does not include the connected-name field in outgoing packets.
Views
ISDN interface view
Predefined user roles
network-admin
Usage guidelines
The command enables a calling party to identify the name of a called party attached to the interface.
You can execute the command only when no call is present on the ISDN interface.
Examples
# Configure ISDN to include the connected-name field in outgoing packets on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn carry connected-name
Related commands
isdn carry calling-name
isdn check-called-number
Use isdn check-called-number to configure called-number verification for incoming calls on an ISDN interface.
Use undo isdn check-called-number to remove an acceptable called number.
Syntax
isdn check-called-number check-index called-party-number
undo isdn check-called-number check-index
Default
ISDN does not check the called number or subaddress in incoming SETUP messages.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
check-index: Specifies a called-number verification index in the range of 1 to 3.
called-party-number: Specifies an acceptable called number. You can include a colon-separated subaddress when you specify the called number, for example, 66668888:13525. The value must be a case-sensitive string of 1 to 40 characters.
Usage guidelines
Called-number verification enables an ISDN interface to accept only calls placed to specific called numbers. You can configure the ISDN interface to verify only the called number or both the called number and the called subaddress. The ISDN interface will accept a call only if the called-number information matches one entry in the list of acceptable called numbers.
Examples
# Add 66668888:13525 to the list of acceptable called-numbers on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn check-called-number 1 66668888:13525
isdn crlength
Use isdn crlength to set the length of the call reference for calls placed on an ISDN interface.
Use undo isdn crlength to restore the default.
Syntax
isdn crlength call-reference-length
undo isdn crlength
Default
The call reference length is 2 bytes for CE1/PRI and CT1/PRI interfaces and 1 byte for BRI interfaces.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
call-reference-length: Specifies an ISDN call reference length, in bytes. Available values include 1 and 2.
Usage guidelines
Call reference is a sequence number that identifies a call. A call reference can be reused after it is released when its associated call is released.
When the router is connected to a peer device that cannot recognize the call reference length, you must configure the router with the same call reference length as the peer device.
You can configure the command only when no calls are present on the ISDN interface.
Examples
# Set the call reference length to 1 byte on PRI interface Serial 2/3/0:15.
<Sysname> system-view
[Sysname] interface serial 2/3/0:15
[Sysname-Serial2/3/0:15] isdn crlength 1
isdn ignore connect-ack
Use isdn ignore connect-ack to enable ISDN to enter the ACTIVE state without an acknowledgment after it sends or receives a CONNECT request.
Use undo isdn ignore connect-ack to disable ISDN to enter the ACTIVE state without an acknowledgment after it sends or receives a CONNECT request.
Syntax
isdn ignore connect-ack [ incoming | outgoing ]
undo isdn ignore connect-ack [ incoming | outgoing ]
Default
After sending a CONNECT request, ISDN waits for a CONNECT ACK before it changes to the ACTIVE state for traffic transmission.
After receiving a CONNECT request, ISDN sends a CONNECT ACK and changes to the ACTIVE state.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
incoming: Specifies the incoming CONNECT ACK.
outgoing: Specifies the outgoing CONNECT ACK.
Usage guidelines
The setting for the command must be consistent with the setting on the service provider switch.
· If the service provider switch does not send CONNECT ACK, configure the isdn ignore connect-ack incoming command. After sending a CONNECT message, ISDN changes to the ACTIVE state without waiting for an acknowledgment.
· If the service provider switch does not receive CONNECT ACK, configure the isdn ignore connect-ack outgoing command. After receiving a CONNECT message, ISDN changes to the ACTIVE state without sending an acknowledgment.
You can configure the command only when no calls are present on the ISDN interface.
Examples
# On BRI 2/4/0, enable ISDN to change to the ACTIVE state after it sends a CONNECT request without waiting for a CONNECT ACK.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn ignore connect-ack incoming
# On BRI 2/4/0, enable ISDN to change to the ACTIVE state after it receives a CONNECT request without sending a CONNECT ACK.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn ignore connect-ack outgoing
isdn ignore hlc
Use isdn ignore hlc to exclude the HLC information element from the outgoing SETUP message.
Use undo isdn ignore hlc to restore the default.
Syntax
isdn ignore hlc
undo isdn ignore hlc
Default
All ISDN protocols except 5ESS and QSIG include the HLC information element in the SETUP message.
Views
ISDN interface view
Predefined user roles
network-admin
Usage guidelines
The high layer compatibility (HLC) element provides high layer compatibility check information for the called party. The called party will reject the call setup request if it detects an incompatibility.
For a successful call setup, make sure the ISDN interface uses the same HLC setting as the service provider switch.
You can execute the command only when no call is present on the ISDN interface.
Examples
# Exclude the HLC information element from the outgoing SETUP message on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn ignore hlc
isdn ignore llc
Use isdn ignore llc to exclude the LLC information element from the outgoing SETUP message.
Use undo isdn ignore llc to restore the default.
Syntax
isdn ignore llc
undo isdn ignore llc
Default
All ISDN protocols except 5ESS and QSIG include the LLC information element in the SETUP message.
Views
ISDN interface view
Predefined user roles
network-admin
Usage guidelines
The lower layer compatibility (LLC) element provides low layer compatibility check information for the called party. The called party will reject the call setup request if it detects an incompatibility.
For a successful call setup, make sure the ISDN interface uses the same LLC setting as the service provider switch.
You can execute the command only when no call is present on the ISDN interface.
Examples
# Exclude the LLC information element from the outgoing SETUP message on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn ignore llc
isdn ignore sending-complete
Use isdn ignore sending-complete to exclude or ignore the sending complete indication for call setup.
Use undo isdn ignore sending-complete to restore the default.
Syntax
isdn ignore sending-complete [ incoming | outgoing ]
undo isdn ignore sending-complete [ incoming | outgoing ]
Default
The device checks incoming SETUP messages for the sending complete indication.
The device includes a sending complete indication in outgoing SETUP messages.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
incoming: Ignores the sending complete indication in the incoming SETUP message.
outgoing: Excludes the sending complete indication from the outgoing SETUP message.
Usage guidelines
A sending complete indication in the SETUP message indicates the completion of information sending or receiving.
If you do not specify a call direction, the command takes effect on both incoming and outgoing ISDN calls.
The command takes effect only when the ISDN protocol is DSS1, QSIG, or ETSI. For a successful call setup, you must use the same sending complete indication setting as the service provider switch.
You can execute the command only when no call is present on the ISDN interface.
Examples
# Ignore the sending complete indication in the incoming SETUP message on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn ignore sending-complete incoming
# Exclude the sending complete indication in the outgoing SETUP message on BRI 2/4/0.
[Sysname-Bri2/4/0] isdn ignore sending-complete outgoing
isdn protocol-type
isdn l3-timer
Use isdn l3-timer to set an ISDN L3 timer.
Use undo isdn l3-timer to restore the default.
Syntax
isdn l3-timer timer-name time-interval
undo isdn l3-timer { timer-name | all }
Default
Table 30 lists the default L3 timer settings for DSS1. For the default L3 timer values for other ISDN protocols, use the display isdn parameters command.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
timer-name: Specifies an ISDN L3 timer name.
time-interval: Specifies a timer value.
all: Restores the default values of all ISDN L3 timers.
Keyword for the timer-name argument |
Timer name |
Value range (in seconds) |
Default (in seconds) |
t301 |
T301 |
30 to 1200 |
240 |
t302 |
T302 |
1 to 60 |
15 |
t303 |
T303 |
2 to 10 |
4 |
t304 |
T304 |
10 to 60 |
30 |
t305 |
T305 |
4 to 30 |
30 |
t308 |
T308 |
2 to 10 |
4 |
t309 |
T309 |
1 to 240 |
90 |
t310 |
T310 |
10 to 240 |
40 |
t313 |
T313 |
2 to 10 |
4 |
t322 |
T322 |
2 to 10 |
4 |
Usage guidelines
T302 and T304 are timers for overlap sending. They are not available in overlap sending-incapable ISDN protocols, including AT&T, NTT, NI2, and 5ESS.
Examples
# Set the T301 timer to 160 seconds on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn l3-timer t301 160
Related commands
display isdn parameters
isdn overlap-sending
isdn leased-line
Use isdn leased-line [ B1 | B2 | 128 ] to configure the leased line service for an ISDN BRI interface.
Use undo isdn leased-line [ B1 | B2 | 128 ] to remove the leased line configuration for an ISDN BRI interface.
Syntax
isdn leased-line [ B1 | B2 | 128 ]
undo isdn leased-line [ B1 | B2 | 128 ]
Default
The leased line service is not configured for an ISDN BRI interface.
Views
ISDN BRI interface view
Predefined user roles
network-admin
network-operator
Parameters
B1: Uses channel B1 as a 64-kbps leased line.
B2: Uses channel B2 as a 64-kbps leased line.
128: Combines channels B1 and B2 into a 128-kbps leased line.
Usage guidelines
The isdn leased-line command without any keywords configures both the B1 and B2 channels as 64-kbps leased lines.
The undo isdn leased-line command without any keywords removes both 64-kbps leased lines from the specified BRI interface.
You can directly switch an ISDN BRI interface from 64-kbps leased line service to 128-kbps leased line service, or vice versa.
This command is not available on BSV interfaces.
Examples
# Combine channels B1 and B2 on BRI 2/1 to provide a 128 kbps leased line.
<Sysname> system-view
[Sysname] interface bri 2/1
[Sysname-Bri2/1] isdn leased-line 128
isdn link-mode p2p
Use isdn link-mode p2p to configure a BRI interface to operate in point-to-point mode.
Use undo isdn link-mode to restore the default.
Syntax
isdn link-mode p2p
undo isdn link-mode
Default
A BRI interface operates in point-to-multipoint mode.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Usage guidelines
The data link type of an ISDN BRI interface can be one of the following:
· point-to-point—The BRI interface can be connected only to one terminal device.
· point-to-multipoint—The BRI interface can be connected to multiple terminal devices.
Set the data link type of an ISDN BRI interface to be the same as its connected service provider switch.
If the isdn two-tei command is configured, the data link of the BRI interface must be point-to-multipoint.
You cannot change an ISDN BRI interface's data link type when a call is present.
Examples
# Configure BRI 2/4/0 to operate in point-to-point mode.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn link-mode p2p
Related commands
isdn two-tei
isdn number-property
Use isdn number-property to set the number type and numbering plan identification for calling or called numbers in incoming or outgoing ISDN calls.
Use undo isdn number-property to restore the default.
Syntax
isdn number-property number-property [ calling | called ] [ in | out ]
undo isdn number-property [ calling | called ] [ in | out ]
Default
The system automatically selects a number type and numbering plan appropriate to the upper-layer service.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
number-property: Specifies the type and numbering identification plan of ISDN numbers, a hexadecimal string in the range of 0 to 7F. In binary form, the string contains 8 bits:
· Bits 1 through 4 represent the numbering identification plan.
· Bits 5 through 7 represent type of the number.
· Bit 8 is reserved for extension.
Table 31 through Table 36 show the ISDN number type and numbering plan identification bitmaps for different ISDN protocols.
calling: Specifies calling numbers.
called: Specifies called numbers.
in: Specifies incoming ISDN calls.
out: Specifies outgoing ISDN calls.
Table 31 ISDN number type and numbering plan identification bitmap for AT&T
Ext |
Type of number |
Numbering plan identification |
Information element |
Type of number |
Numbering plan identification |
||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
|
|
|
|
|
|
0 |
0 |
0 |
0 |
Calling party number |
N/A |
Unknown |
|
|
|
|
|
0 |
0 |
0 |
1 |
Calling party number |
N/A |
ISDN/telephony numbering plan (Recommendation E.164) |
|
|
|
|
|
0 |
0 |
1 |
1 |
Calling party number |
N/A |
Data numbering plan (Recommendation X.121) |
|
|
|
|
|
0 |
1 |
0 |
0 |
Calling party number |
N/A |
Telex numbering plan (Recommendation F.69) |
|
|
|
|
|
1 |
0 |
0 |
0 |
Calling party number |
N/A |
National standard numbering plan |
|
|
|
|
|
1 |
0 |
0 |
1 |
Calling party number |
N/A |
Private numbering plan |
|
|
|
|
|
1 |
1 |
1 |
1 |
Calling party number |
N/A |
Reserved for extension |
|
Table 32 ISDN number type and numbering plan identification bitmap for ANSI, ETSI, DSS1, and NTT
Ext |
Type of number |
Numbering plan identification |
Information element |
Type of number |
Numbering plan identification |
|||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
|
||
|
|
|
|
0 |
0 |
0 |
0 |
Calling party number Called party number |
N/A |
Unknown |
||
|
|
|
|
0 |
0 |
0 |
1 |
Calling party number Called party number |
N/A |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
|
|
|
0 |
0 |
1 |
1 |
Calling party number Called party number |
N/A |
Data numbering plan (Recommendation X.121) |
||
|
|
|
|
0 |
1 |
0 |
0 |
Calling party number Called party number |
N/A |
Telex numbering plan (Recommendation F.69) |
||
|
|
|
|
1 |
0 |
0 |
0 |
Calling party number Called party number |
N/A |
National standard numbering plan |
||
|
|
|
|
1 |
0 |
0 |
1 |
Calling party number Called party number |
N/A |
Private numbering plan |
||
|
|
|
|
1 |
1 |
1 |
1 |
Calling party number Called party number |
N/A |
Reserved for extension |
||
Table 33 ISDN number type and numbering plan identification bitmap for NI
Ext |
Type of number |
Numbering plan identification |
Information element |
Type of number |
Numbering plan identification |
|||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
|
||
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Called party number |
Unknown |
Unknown |
||
|
0 |
0 |
0 |
0 |
0 |
0 |
1 |
Calling party number |
Unknown |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
0 |
0 |
0 |
0 |
0 |
1 |
1 |
Calling party number |
Unknown |
Data numbering plan (Recommendation X.121) |
||
|
0 |
0 |
0 |
0 |
1 |
0 |
0 |
Calling party number |
Unknown |
Telex numbering plan (Recommendation F.69) |
||
|
0 |
0 |
0 |
1 |
0 |
0 |
0 |
Calling party number |
Unknown |
National standard numbering plan |
||
|
0 |
0 |
0 |
1 |
0 |
0 |
1 |
Calling party number |
Unknown |
Private numbering plan |
||
|
0 |
0 |
0 |
1 |
1 |
1 |
1 |
Calling party number |
Unknown |
Reserved for extension |
||
|
0 |
1 |
0 |
0 |
0 |
0 |
1 |
Called party number |
National number |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
0 |
1 |
1 |
1 |
0 |
0 |
1 |
Called party number |
Network specific number |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
1 |
0 |
0 |
0 |
0 |
0 |
1 |
Called party number |
Unknown |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
1 |
1 |
0 |
1 |
0 |
0 |
1 |
Called party number |
Abbreviated number |
Private numbering plan |
||
Table 34 ISDN number type and numbering plan identification bitmap for NI2
Ext |
Type of number |
Numbering plan identification |
Information element |
Type of number |
Numbering plan identification |
|||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
|
||
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Calling party number |
Unknown |
Unknown |
||
|
0 |
0 |
1 |
0 |
0 |
0 |
1 |
Calling party number |
International number |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
0 |
1 |
0 |
0 |
0 |
0 |
1 |
Calling party number |
National number |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
1 |
0 |
0 |
0 |
0 |
0 |
1 |
Calling party number |
Subscriber number |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
0 |
0 |
1 |
0 |
0 |
1 |
1 |
Calling party number |
International number |
Data numbering plan (Recommendation X.121) |
||
|
1 |
0 |
0 |
1 |
0 |
0 |
1 |
Calling party number |
Subscriber number |
Private numbering plan |
||
|
1 |
1 |
0 |
1 |
0 |
0 |
1 |
Calling party number |
Abbreviated number |
Private numbering plan |
||
Table 35 ISDN number type and numbering plan identification bitmap for 5ESS
Ext |
Type of number |
Numbering plan identification |
Information element |
Type of number |
Numbering plan identification |
|||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
|
||
|
0 |
0 |
0 |
|
|
|
|
Calling party number Called party number |
Unknown |
N/A |
||
|
0 |
0 |
1 |
|
|
|
|
Calling party number Called party number |
International number |
N/A |
||
|
0 |
1 |
0 |
|
|
|
|
Calling party number Called party number |
National number |
N/A |
||
|
0 |
1 |
1 |
|
|
|
|
Calling party number Called party number |
Network specific number |
N/A |
||
|
1 |
0 |
0 |
|
|
|
|
Calling party number Called party number |
Subscriber number |
N/A |
||
|
|
|
|
0 |
0 |
0 |
0 |
Calling party number Called party number |
N/A |
Unknown |
||
|
|
|
|
0 |
0 |
0 |
1 |
Calling party number Called party number |
N/A |
ISDN/telephony numbering plan (Recommendation E.164) |
||
|
|
|
|
0 |
0 |
1 |
0 |
Calling party number Called party number |
N/A |
Private numbering plan |
||
|
|
|
|
1 |
0 |
0 |
1 |
Calling party number Called party number |
N/A |
Unknown |
||
Table 36 ISDN number type and numbering plan identification bitmap for QSIG
Ext |
Type of number |
Numbering plan identification |
Information element |
Type of number |
Numbering plan identification |
||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
|
|||
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Calling party number Called party number |
Unknown |
Unknown |
|||
|
0 |
0 |
0 |
0 |
0 |
0 |
1 |
Calling party number Called party number |
Unknown |
ISDN/telephony numbering plan (Recommendation E.164) |
|||
|
0 |
0 |
1 |
0 |
0 |
0 |
1 |
Calling party number Called party number |
International number |
ISDN/telephony numbering plan (Recommendation E.164) |
|||
|
0 |
1 |
0 |
0 |
0 |
0 |
1 |
Calling party number Called party number |
National number |
ISDN/telephony numbering plan (Recommendation E.164) |
|||
|
1 |
0 |
0 |
0 |
0 |
0 |
1 |
Calling party number Called party number |
Network specific number |
ISDN/telephony numbering plan (Recommendation E.164) |
|||
|
0 |
0 |
0 |
1 |
0 |
0 |
1 |
Calling party number Called party number |
Unknown |
Private numbering plan |
|||
|
0 |
0 |
1 |
1 |
0 |
0 |
1 |
Calling party number Called party number |
International number |
Level 2 regional number in private numbering plan |
|||
|
0 |
1 |
0 |
1 |
0 |
0 |
1 |
Calling party number Called party number |
National number |
Private numbering plan |
|||
|
0 |
1 |
1 |
1 |
0 |
0 |
1 |
Calling party number Called party number |
Network specific number |
Private numbering plan |
|||
|
1 |
0 |
0 |
1 |
0 |
0 |
1 |
Calling party number Called party number |
Subscriber number |
Private numbering plan |
|||
Examples
# Set the type of number and numbering plan identification both to unknown for the calling numbers in incoming ISDN calls on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn number-property 0 calling in
# Set the type of number and numbering plan identification both to unknown for the called numbers in outgoing ISDN calls on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn number-property 0 called out
isdn overlap-sending
Use isdn overlap-sending to enable overlap sending on an ISDN interface for called numbers.
Use undo isdn overlap-sending to restore the default.
Syntax
isdn overlap-sending [ digits ]
undo isdn overlap-sending
Default
En-bloc sending is enabled for called numbers. In the SETUP message, ISDN includes all information required by the network to process the call.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
digits: Specifies the maximum number of digits that can be sent in each SETUP message. The value range is 1 to 15, and the default is 10.
Usage guidelines
In overlap mode, called number information is absent or incomplete in each outgoing SETUP message.
Overlap sending is not available in ANSI, DSS1, ETSI, NI, or QSIG.
You can execute the command only when no call is present on the ISDN interface.
Examples
# Enable overlap sending on BRI 2/4/0, and configure the interface to send a maximum of 12 called-number digits in each SETUP message.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn overlap-sending 12
isdn pri-slipwnd-size
Use isdn pri-slipwnd-size to set the sliding window size on an ISDN PRI interface.
Use undo isdn pri-slipwnd-size to restore the default.
Syntax
isdn pri-slipwnd-size window-size
undo isdn pri-slipwnd-size
Default
The sliding window size is 7 on ISDN PRI interfaces.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
window-size: Specifies a sliding window size in the range of 5 to 64.
Usage guidelines
Q.921 sends frames in order of their sequence numbers and requires an acknowledgment of each transmitted frame. To improve transmission efficiency, Q.921 does not wait for a transmitted frame to be acknowledged before it sends the next frame. Instead, it uses a sliding window mechanism for transmission.
The sliding window mechanism enables Q.921 to send multiple continuous frames without waiting for the acknowledgment of the previous frame. The sliding window size sets the maximum number of unacknowledged frames. You can tune the size depending on the link status to maximize the throughput.
When sending a frame, Q.921 checks the number of unacknowledged frames. Suppose V(A) is the sequence number of the previous acknowledged frame, V(S) is the sequence number of the frame to be sent, and k is the sliding window size. If V(A) + k = V(S), the system stops sending frames.
Examples
# Set the sliding window size to 10 on ISDN PRI interface Serial 2/3/0:15.
<Sysname> system-view
[Sysname] controller e1 2/3/0
[Sysname-E1 2/3/0] using ce1
[Sysname-E1 2/3/0] pri-set
[Sysname-E1 2/3/0] quit
[Sysname] interface serial 2/3/0:15
[Sysname-Serial2/3/0:15] isdn pri-slipwnd-size 10
Related commands
isdn bri-slipwnd-size
isdn progress-indicator
Use isdn progress-indicator to set the progress description in the progress indicator information element of ISDN signaling messages.
Use undo isdn progress-indicator to restore the default.
Syntax
isdn progress-indicator indicator
undo isdn progress-indicator
Default
ISDN uses the progress description assigned by the upper-layer voice service.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
indicator: Specifies one of the progress descriptions in Table 37.
Table 37 Progress descriptions
Value |
Description |
1 |
Call is not an end-to-end ISDN call. Further call progress information might be available in-band. |
2 |
Destination address is non-ISDN. |
3 |
Origination address is non-ISDN. |
4 |
Call has returned to the ISDN network. |
5 |
Interworking has occurred and has resulted in a telecommunication service change. For example, the ISDN network changes to the VoIP network. |
8 |
Signals of other protocols than ISDN are present on the D channel. |
Usage guidelines
The progress indicator information element describes an event that has occurred during the life of the call.
You only need to set the progress description manually only if you are required by the service provider to do so for compatibility.
Examples
# Set the progress description code to 8 on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn progress-indicator 8
isdn progress-to-alerting enable
Use isdn progress-to-alerting enable to enable an ISDN interface to interpret the PROGRESS message as the ALERTING message.
Use undo isdn progress-to-alerting enable to disable an ISDN interface from interpreting the PROGRESS message as the ALERTING message.
Syntax
isdn progress-to-alerting enable
undo isdn progress-to-alerting enable
Default
The progress message is not interpreted as the ALERTING message.
Views
ISDN interface view
Predefined user roles
network-admin
Usage guidelines
Typically, ISDN devices use the ALERTING message to indicate that called user alerting has been initiated. To work with ISDN devices that use the PROGRESS message to convey this information, you must configure the command.
Examples
# Interpret the PROGRESS message as the ALERTING message on ISDN PRI interface Serial 2/3/0:15.
<Sysname> system-view
[Sysname] interface serial 2/3/0:15
[Sysname-Serial2/3/0:15] isdn progress-to-alerting enable
isdn protocol-mode
Use isdn protocol-mode to configure the ISDN functionality of an ISDN interface.
Use undo isdn protocol-mode to restore the default.
Syntax
isdn protocol-mode { network | user }
undo isdn protocol-mode
Default
An ISDN interface provides the ISDN user-side functionality.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
network: Specifies the network-side functionality.
user: Specifies the user-side functionality.
Usage guidelines
An ISDN interface can provide the ISDN user-side or network-side functionality. For two ISDN devices to communicate with each other, you must configure one end as the network side and configure the other end as the user side.
Typically, an ISDN interface is operating on the user side. However, when a BRI interface on a BSV card is connected directly to an ISDN phone, you must configure the BRI interface as the network side.
You must configure the ISDN interface as the user side in the following situations:
· The BRI interface for data services must operate on the user side.
· ANSI, AT&T, ETSI, NI, or NTT is configured.
You cannot configure the command when a call is present on the ISDN interface.
Examples
# Configure BRI 2/4/0 as the network side.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn protocol-mode network
isdn protocol-type
Use isdn protocol-type to configure the ISDN switch type on an ISDN interface.
Use undo isdn protocol-type to restore the default.
Syntax
isdn protocol-type protocol
undo isdn protocol-type
Default
The ISDN switch type is DSS1 for both BRI and PRI.
Views
ISDN interface view
Predefined user roles
network-admin
Parameters
protocol: Specifies an ISDN switch type. Available options include 5ess, ansi, at&t, dss1, etsi, ni, ni2, ntt, and qsig. To specify ANSI, AT&T, ETSI, NI, or NTT, make sure the interface is operating on the user side.
Usage guidelines
You can configure the command only when no call is present on the ISDN interface.
ISDN service providers in different countries implement variants of ISDN to provide varied ISDN services. When you configure an ISDN interface, you must set the switch type on the interface to be the same as the service provider switch type.
Table 38 shows the ISDN switch types available on an ISDN interface.
Table 38 ISDN switch type and ISDN interface compatibility matrix
Switch type |
BRI |
CT1/PRI |
CE1/PRI |
ANSI |
Yes |
Yes |
No |
AT&T |
No |
Yes |
No |
5ESS |
No |
Yes |
No |
DSS1 |
Yes |
Yes |
Yes |
ETSI |
Yes |
Yes |
Yes |
NI |
Yes |
No |
No |
NI2 |
No |
Yes |
No |
QSIG |
No |
Yes |
Yes |
NTT |
Yes |
Yes |
No |
|
NOTE: The device provides full support for DSS1. For any other variants of ISDN, the device only provides the basic call functionality. |
Examples
# Set the ISDN switch type to ETSI on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn protocol-type etsi
# Set the ISDN switch type to 5ESS on ISDN PRI interface Serial 2/3/0:23.
<Sysname> system-view
[Sysname] interface serial 2/3/0:23
[Sysname-Serial2/3/0:23] isdn protocol-type 5ess
Related commands
isdn protocol-mode
isdn q921-permanent
Use isdn q921-permanent to enable permanent Q.921 link connectivity on a BRI interface.
Use undo isdn q921-permanent to disable permanent Q.921 link connectivity on a BRI interface.
Syntax
isdn q921-permanent
undo isdn q921-permanent
Default
Permanent Q.921 link connectivity is disabled on ISDN BRI interfaces.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Usage guidelines
You can enable permanent Q.921 link connectivity only on user-side ISDN BRI interfaces.
When this feature is enabled, the ISDN BRI interface establishes and maintains permanent data link connections automatically, regardless of whether or not a call is present. If the isdn two-tei command is also configured, the ISDN BRI interface establishes and maintains two permanent data link connections.
When this feature is disabled, the ISDN BRI interface transits to the multiframe established state only when a call is present. In multiframe established state, the interface disconnects the Q.921 link if no Q.931 call is present when the T325 timer expires.
To ensure successful call setup when ISDN NI is used, you must enable permanent Q.921 link connectivity.
Examples
# Enable permanent Q.921 link connectivity on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn q921-permanent
Related commands
isdn protocol-mode
isdn two-tei
isdn spid auto-trigger
Use isdn spid auto-trigger to initiate a SPID negotiation on an NI-enabled BRI interface.
Syntax
isdn spid auto-trigger
Default
The NI-enabled BRI interface initiates a SPID negotiation when it receives a call request.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Usage guidelines
The command is available only on NI-enabled BRI interfaces.
When the BRI interface uses dynamic SPID negotiation, you can initiate a SPID negotiation for testing purposes or after an automatic dynamic SPID negotiation fails. If NIT mode is enabled or static SPIDs are configured, you cannot initiate a SPID negotiation on the interface.
You can configure the command only when no call or SPID negotiation is present on the BRI interface.
Examples
# Initiate a SPID negotiation on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn spid auto-trigger
isdn spid nit
Use isdn spid nit to enable Not Initial Terminal (NIT) mode on an NI-enabled BRI interface.
Use undo isdn spid nit to restore the default.
Syntax
isdn spid nit
undo isdn spid nit
Default
NIT mode is disabled. NI-enabled BRI interfaces perform dynamic SPID negotiation.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Usage guidelines
The command is available only on NI-enabled BRI interfaces.
Typically, an NI-enabled BRI interface must pass SPID negotiation or initiation before it can place a call.
You must enable Not Initial Terminal (NIT) mode on the BRI interface if the NI-type service provider switch does not support SPID negotiation.
You can configure the command only when no call or SPID negotiation is present on the BRI interface.
Examples
# Enable NIT mode on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn spid nit
Related commands
display isdn spid
isdn spid resend
Use isdn spid resend to set the maximum number of INFORMATION message retransmissions for SPID negotiation or initialization on an NI-enabled BRI interface.
Use undo isdn spid resend to restore the default.
Syntax
isdn spid resend times
undo isdn spid resend
Default
The number of INFORMATION message retransmission attempts is 1.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Parameters
times: Specifies the maximum number of INFORMATION message retransmissions, in the range of 1 to 255.
Usage guidelines
The command is available only on NI-enabled BRI interfaces.
An NI-enabled BRI interface sends SPID information in the Q.931 INFORMATION message during SPID negotiation and Layer 3 initialization.
The TSPID timer sets the maximum interval that ISDN waits for a response after it sends an INFORMATION message. The timer starts when the device initiates an SPID negotiation or Layer 3 initialization.
The interface retransmits the INFORMATION message if it has not received a response from the service provider switch before the TSPID timer expires. This process continues until the interface receives a response or the maximum number of INFORMATION retransmissions is reached.
You cannot execute the command when a SPID negotiation is present on the interface.
Examples
# Set the maximum number of INFORMATION message retransmissions to 5 on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn spid resend 5
Related commands
isdn spid timer
isdn spid service
Use isdn spid service to specify services subscribed to by the device on an NI-enabled BRI interface.
Use undo isdn spid service to specify any service types.
Syntax
isdn spid service [ audio | data | speech ]
undo isdn spid service
Default
During a dynamic SPID negotiation, the device chooses the SPID that includes both speech and data services.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Parameters
audio: Specifies the audio service.
data: Specifies the data service.
speech: Specifies the speech service.
Usage guidelines
The command is available only on NI-enabled BRI interfaces.
You can repeat the command to specify multiple services. To specify all the services, execute the command without specifying any services.
If dynamic SPID negotiation is used, the service provider switch sends available SPIDs to the device. The device selects the SPID that best suits its service configuration. For example, if you specify the data service, the device preferentially selects the SPID that includes only the data service. If you specify the audio and data services, the device preferentially selects the SPID that includes both services.
For the device to accept a SPID that includes any service types, use the undo form of the command.
You cannot execute the command when a SPID negotiation is present on the interface.
Examples
# Specify the audio service on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn service audio
isdn spid timer
Use isdn spid timer to set the TSPID timer on an NI-enabled BRI interface.
Use undo isdn spid timer to restore the default.
Syntax
isdn spid timer seconds
undo isdn spid timer
Default
The TSPID timer on an NI-enabled BRI interface is 30 seconds.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Parameters
seconds: Sets the TSPID timer in the range of 1 to 255 seconds.
Usage guidelines
The command is available only on NI-enabled BRI interfaces. You cannot configure the command when a SPID negotiation is present on the interface.
An NI-enabled BRI interface sends SPID information in Q.931 INFORMATION messages during SPID negotiation and Layer 3 initialization.
The TSPID timer sets the maximum interval that ISDN waits for a response after it sends an INFORMATION message. The timer starts when the device initiates a SPID negotiation or Layer 3 initialization.
The interface retransmits the INFORMATION message if it has not received a response from the service provider switch before the TSPID timer expires. This process continues until the interface receives a response or the maximum number of INFORMATION retransmissions is reached.
Examples
# Set the TSPID timer to 50 seconds on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn spid timer 50
Related commands
isdn spid resend
isdn spid1
Use isdn spid1 to assign a SPID to the B1 channel on an NI-enabled BRI interface.
Use undo isdn spid1 to restore the default.
Syntax
isdn spid1 spid [ ldn ]
undo isdn spid1
Default
No SPID or LDN is configured for the B1 channel on an NI-enabled BRI interface.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Parameters
spid: Sets a SPID, a string of 1 to 20 digits.
ldn: Sets a local dialing number, a string of 1 to 30 digits.
Usage guidelines
The command is available only on NI-enabled BRI interfaces.
When you use the command, follow these guidelines:
· Make sure the configured SPID is the same as the SPID assigned by the service provider.
· Configure an LDN depending on the service provider requirement. If an LDN is configured, the setting for the isdn calling command becomes invalid.
· You cannot configure a SPID in the following situations:
¡ A call is present.
¡ A SPID negotiation is present.
Examples
# Assign a SPID of 012345 and an LDN of 54321 to the B1 channel on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn spid1 012345 54321
Related commands
isdn calling
isdn spid2
isdn spid2
Use isdn spid2 to assign a SPID to the B2 channel on an NI-enabled BRI interface.
Use undo isdn spid2 to restore the default.
Syntax
isdn spid2 spid [ ldn ]
undo isdn spid2
Default
No SPID or LDN is configured for the B2 channel on an NI-enabled BRI interface.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Parameters
spid: Sets a SPID, a string of 1 to 20 digits.
ldn: Sets a local dialing number, a string of 1 to 30 digits.
Usage guidelines
The command is available only on NI-enabled BRI interfaces.
When you use the command, follow these guidelines:
· Make sure the configured SPID is the same as the SPID assigned by the service provider.
· Configure an LDN depending on the service provider requirement. If an LDN is configured, the setting for the isdn calling command becomes invalid.
· You cannot configure a SPID in the following situations:
¡ A call is present.
¡ A SPID negotiation is present.
Examples
# Assign a SPID of 012345 and an LDN of 54321 to the B2 channel on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn spid2 012345 54321
Related commands
isdn calling
isdn spid1
isdn two-tei
Use isdn two-tei to configure a BRI interface to request a TEI for each B channel.
Use undo isdn two-tei to restore the default.
Syntax
isdn two-tei
undo isdn two-tei
Default
All B-channels on a BRI interface use the same TEI.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Usage guidelines
Terminal endpoint identifiers (TEIs) are assigned by the service provider to identify terminal devices. A TEI identifies one terminal device on a point-to-point link and identifies more than one terminal device on a point-to-multipoint link.
Typically, service provider switches assign one TEI for both B-channels on a BRI interface. If the service provider switch requires the B-channels to use different TEIs, you must configure the BRI interface to request a TEI from the switch before the interface can establish a call on a B-channel. If per-channel TEI assignment is not configured, only one B-channel can be brought up. For example, you must configure per-channel TEI assignment when a BRI interface is connected to an ISDN NI compliant DMS-100 switch in North America.
You cannot configure per-channel TEI assignment in the following situations:
· The BRI interface's data link type is point-to-point.
· A call is present on the interface.
Examples
# Enable per-channel TEI assignment on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Router-Bri2/4/0] isdn two-tei
Related commands
isdn link-mode p2p
permanent-active
Use permanent-active to enable persistent Layer 1 activation on a BRI interface.
Use undo permanent-active to disable persistent Layer 1 activation on a BRI interface.
Syntax
permanent-active
undo permanent-active
Default
Persistent Layer 1 activation is disabled on a BRI interface.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Usage guidelines
Persistent Layer 1 activation is available only on network-side BRI interfaces.
For energy efficiency, a network-side ISDN interface typically deactivates the physical layer when the data link layer connection is disconnected. To maintain physical layer connectivity when the data link connection is lost, enable persistent Layer 1 activation. This feature prevents Q.921 from sending deactivation requests to the physical layer.
Persistent Layer 1 activation can only maintain the active state of the physical layer. It does not activate the physical layer if you enable it when the physical layer is inactive. In contrast, Q.921 attempts to set up data link connections if you enable permanent Q.921 link connectivity when no data link connections are present.
|
NOTE: Only BRI interfaces on the BSV module can operate on the network side. |
Examples
# Enable persistent Layer 1 activation on BRI 2/4/0, a network-side BRI interface.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn protocol-mode network
[Sysname-Bri2/4/0] permanent-active
Related commands
isdn q921-permanent
power-source
Use power-source to enable a BRI interface to supply line power to the terminal equipment.
Use undo power-source to disable a BRI interface from supplying line power to the terminal equipment.
Syntax
power-source
undo power-source
Default
A BRI interface does not supply line power to the terminal equipment.
Views
ISDN BRI interface view
Predefined user roles
network-admin
Usage guidelines
You can configure only network-side BRI interfaces to supply line power to the terminal equipment.
Only ISDN BRI interfaces on the BSV module can operate on the network side.
You can configure the command only when no call is present.
Examples
# Configure BRI 2/4/0 to supply line power to the terminal equipment.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] isdn protocol-mode network
[Sysname-Bri2/4/0] power-source
Related commands
isdn protocol-mode
ATM commands
ATM is supported only by MSR routers installed with an ATM-OC3, ADSL2+, G.shdsl, or G.shdsl.Bis interface module.
ATM is not supported on the MSR3600-28-SI/3600-51-SI routers.
bandwidth
Use bandwidth to configure the expected bandwidth for an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth (in kbps) is the interface baud rate divided by 1000.
Views
VE interface view
VE subinterface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth of an interface affects the link costs of IS-IS, OSPF, and OSPFv3. For more information, see Layer 3—IP Routing Configuration Guides.
Examples
# Set the expected bandwidth of Virtual-Ethernet 2/4/1 to 50 kbps.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1
[Sysname-Virtual-Ethernet2/4/1] bandwidth 50
broadcast
Use broadcast to enable the broadcast attribute for a PVC or PVC-group.
Use undo broadcast to disable the broadcast attribute for a PVC or PVC-group.
Syntax
broadcast
undo broadcast
Default
The broadcast attribute is disabled.
Views
PVC view
PVC-group view
Predefined user roles
network-admin
Usage guidelines
On an ATM interface, multicast or broadcast packets are sent through all PVCs or PVC-groups with the broadcast attribute enabled.
You must configure this command on a PVC or PVC-group where broadcast or multicast packets must be sent. For example, to establish PIM neighbors between two routers on an ATM link through exchanging IP multicast packets, you must enable the broadcast attribute for PVCs on the ATM interfaces of both ends on the link.
This command is not applicable to PVCs in a PVC-group.
Examples
# Enable the broadcast attribute for PVC 0/100.
<Sysname> system-view
[Sysname] interface atm 2/4/1.1
[Sysname-ATM2/4/1.1] pvc 0/100
[Sysname-ATM2/4/1.1-pvc-0/100] broadcast
default
Use default to restore the default settings for an interface.
Syntax
default
Views
VE interface view
VE subinterface 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 impacts of this command when you use 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, and then use their undo forms 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 VE interface Virtual-Ethernet 2/4/1.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1
[Sysname-Virtual-Ethernet2/4/1] default
description
Use description to configure the description for an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description for an interface is interface name Interface, for example, Virtual-Ethernet 2/4/1 Interface.
Views
VE interface view
VE subinterface 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 VE interface Virtual-Ethernet 2/4/1 to Virtual-Ethernet.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1
[Sysname-Virtual-Ethernet2/4/1] description Virtual-Ethernet
display atm map-info
Use display atm map-info to display mapping information about PVCs or PVC-groups.
Syntax
display atm map-info [ interface interface-type { interface-number | interface-number.subnumber } [ pvc { pvc-name | vpi/vci } | pvc-group group-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type { interface-number | interface-number.subnumber }: Specifies an interface by its type and number. Both ATM interfaces and ATM subinterfaces are supported.
pvc: Displays mapping information for a PVC.
pvc-name: Specifies a PVC by its name, a case-sensitive string of 1 to 15 characters excluding slashes (/) and hyphens (-). For example, neither 1/20 nor a-b is a valid PVC name.
vpi/vci: Specifies a PVC by its VPI and VCI values. The value range for the vpi argument is 0 to 255. The value range for the vci argument varies by interface type. For more information, see Table 46. The values of the vpi and vci arguments cannot be 0 at the same time. As a best practice, do not use VCI values 0 through 31 because they are reserved for special purposes.
pvc-group group-number: Specifies a PVC-group by its number in the range of 1 to 128.
Usage guidelines
If you do not specify an ATM interface, this command displays mapping information for all PVCs and PVC-groups on all ATM interfaces.
If you specify an ATM interface but do not specify a PVC or PVC-group, this command displays mapping information for all PVCs and PVC-groups on the specified ATM interface.
If you specify an ATM interface and a PVC or PVC-group, this command displays mapping information for the specified PVC or PVC-group.
Examples
# Display mapping information for all PVCs and PVC-groups on all ATM interfaces.
<Sysname> display atm map-info
ATM2/4/0
PVC 1/32:
Protocol: PPP, Interface: Virtual-Template10, State: UP
Protocol: IP, IP address: 100.11.1.1, State: UP
PVC-group 1:
Protocol: IP InARP, IP address: 100.22.22.2, Interval: 2 minutes, State: UP
Protocol: ETH, Interface: Virtual-Ethernet2/4/0, State: UP
ATM2/4/1
PVC 2/32:
Protocol: IP InARP, IP address: no IP address, Interval: 3 minutes, State: UP
Field |
Description |
ATM2/4/0 |
Interface name. |
PVC 1/32 |
VPI/VCI pair of the PVC. |
PVC-group 1 |
PVC-group name. |
Protocol |
Upper-layer protocol running on the PVC or PVC-group: PPP—PPP protocol. IP—IP protocol. IP InARP—IP InARP protocol. ETH—Ethernet protocol. |
State |
Mapping state: · UP—In PPP and IP (including InARP) mappings, it means that the PVC or PVC-group is up. In Ethernet mapping, it means that the PVC or PVC-group and the VE interface are up. · DOWN—In PPP and IP (including InARP) mappings, it means that the PVC or PVC-group is down. In Ethernet mapping, it means that either the PVC (PVC-group) or the VE interface is down, or both the PVC (PVC-group) and the VE interface are down. |
Interval |
Interval (in minutes) at which InARP packets are sent. |
Interface |
VE interface that carries PPPoA or EoA. |
display atm pvc-group
Use display atm pvc-group to display PVC-group information.
Syntax
display atm pvc-group [ interface interface-type { interface-number | interface-number.subnumber } [ pvc-group group-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type { interface-number | interface-number.subnumber }: Specifies an interface by its type and number. Both ATM interfaces and ATM subinterfaces are supported.
pvc-group group-number: Specifies a PVC-group by its number in the range of 1 to 128.
Usage guidelines
If you do not specify an ATM interface, this command displays brief information about all PVC-groups on all ATM interfaces.
If you specify an ATM interface but do not specify a PVC-group, this command displays brief information about all PVC-groups on the specified ATM interface.
If you specify an ATM interface and a PVC-group, this command displays detailed information about the specified PVC-group.
Examples
# Display brief information about all PVC-groups on all ATM interfaces.
<Sysname> display atm pvc-group
ATM2/4/0, State UP
PVC-group: 1
Encapsulation: SNAP, Protocol: IP
VPI/VCI PVC name Precedence State
1/32 aa Default UP
2/32 N/A 2-3 UP
3/32 N/A 5 UP
PVC-group: 3
Encapsulation: SNAP, Protocol: IP
VPI/VCI PVC name Precedence State
3/64 bb 4 UP
4/64 N/A Default UP
ATM2/4/1, State UP
PVC-group: 1
Encapsulation: SNAP, Protocol: IP
VPI/VCI PVC name Precedence State
1/32 aa Default UP
Table 40 Command output
Field |
Description |
ATM2/4/0, State UP |
Name of the interface to which the PVC-groups belong, and the physical and administrative states of the interface. State of an interface (not a subinterface): · UP—The interface is both physically and administratively up. · DOWN—The interface is in either of the following states: ¡ The interface is administratively up but physically down (probably because no physical link is available or the link has failed). ¡ The interface is administratively down (shut down by using the shutdown command). State of a subinterface: · UP—The interface is administratively up. The parent interface is both physically and administratively up. · DOWN—The interface or its parent interface was shut down by using the shutdown command, or the parent interface is physically down. |
Encapsulation |
AAL5 encapsulation type of the PVC-group. It can only be SNAP, which is the Logical Link Control (LLC)/Subnet Access Protocol (SNAP) encapsulation type. |
Protocol |
Upper-layer protocol running on the PVC-group: · PPP—PPP protocol. · IP—IP protocol. · ETH—Ethernet protocol. · None—No protocol is configured. |
PVC name |
PVC name. N/A means no PVC name. |
Precedence |
Priority of the IP packets carried by the PVC in the PVC-group: · Default—Default PVC. IP packets without a priority configured are transmitted through the default PVC. · a-b—Lowest and highest priorities of the IP packets carried by the PVC. The value range for a and b is 0 to 7. a is smaller than b. · c—Priority of the IP packets carried by the PVC, in the range of 0 to 7. · -—No priority is configured for IP packets carried by the PVC. |
State |
PVC state: · UP—The following states are up: ¡ State of the ATM interface to which the PVC belongs. ¡ Shutdown state. ¡ OAM state. · DOWN—One or more of the following states is down: ¡ State of the ATM interface to which the PVC belongs. ¡ Shutdown state. ¡ OAM state. |
# Display detailed information about the specified PVC-group.
<Sysname> display atm pvc-group interface atm 2/4/0 pvc-group 1
ATM2/4/0, PVC-group: 1
Encapsulation: SNAP, Protocol: None
PVC VPI/VCI: 0/34
Precedence: default
Service-type: CBR, Output-pcr: 200 kbps, CDVT: 500 us
Transmit-Priority: 0
OAM loopback interval: 0 sec(disabled), OAM loopback retry interval: 1 sec
OAM loopback retry count (up/down): 3/5
OAM AIS-RDI count (up/down): 3/1
Interface State: UP, OAM State: UP, PVC State: UP
Input: 0 packets, 0 bytes, 0 errors
Output: 0 packets, 0 bytes, 0 errors
Output queue: (Urgent queuing : Size/Length/Discards) 0/100/0
Output queue: (Protocol queuing : Size/Length/Discards) 0/500/0
Output queue: (FIFO queuing : Size/Length/Discards) 0/75/0
OAM cells received: 42
F5 Loopback: 0, F5 AIS: 42, F5 RDI: 0
OAM cells sent: 0
F5 Loopback: 0
OAM cell drops: 0
PVC VPI/VCI: 0/35
Precedence: -
Service-type: UBR, Output-pcr: 200 kbps
Transmit-Priority: 0
OAM loopback interval: 0 sec(disabled), OAM loopback retry interval: 1 sec
OAM loopback retry count (up/down): 3/5
OAM AIS-RDI count (up/down): 3/1
Interface State: UP, OAM State: UP, PVC State: UP
Input: 0 packets, 0 bytes, 0 errors
Output: 0 packets, 0 bytes, 0 errors
Output queue: (Urgent queuing : Size/Length/Discards) 0/100/0
Output queue: (Protocol queuing : Size/Length/Discards) 0/500/0
Output queue: (FIFO queuing : Size/Length/Discards) 0/75/0
OAM cells received: 42
F5 Loopback: 0, F5 AIS: 42, F5 RDI: 0
OAM cells sent: 0
F5 Loopback: 0
OAM cell drops: 0
Table 41 Command output
Field |
Description |
Encapsulation |
AAL5 encapsulation type of the PVC-group. It can only be SNAP, which is the LLC/SNAP encapsulation type. |
Protocol |
Upper-layer protocol running on the PVC-group: · PPP—PPP protocol. · IP—IP protocol. · ETH—Ethernet protocol. · None—No protocol is configured. |
Precedence |
Priority of the IP packets carried by the PVC in the PVC-group: · Default—Default PVC. IP packets without a priority configured are transmitted through the default PVC. · a-b—Lowest and highest priorities of the IP packets carried by the PVC. The value range for a and b is 0 to 7. a is smaller than b. · c—Priority of the IP packets carried by the PVC, in the range of 0 to 7. · -—No priority is configured for IP packets carried by the PVC. |
Service-type |
Service type: · CBR—Constant bit rate. · UBR—Unspecified bit rate. · VBR-NRT—Variable bit rate-non real time. · VBR-RT—Variable bit rate-real time. |
Output-pcr |
Peak output rate of ATM cells. |
CDVT |
Cell delay variation tolerance in microseconds. |
Transmit-Priority |
Transmission priority. |
OAM loopback interval |
Interval (in seconds) at which OAM F5 Loopback cells are sent. |
OAM loopback retry interval |
Interval (in seconds) at which OAM F5 Loopback retransmission detection cells are sent. |
OAM loopback retry count (up/down) |
Number of cells that are detected as up and down in OAM detection. |
OAM AIS-RDI count (up/down) |
Number of seconds that are detected as up in OAM AIS-RDI detection. Number of cells that are detected as down in OAM AIS-RDI detection. |
Interface State |
Name of the interface to which the PVC belongs, and the physical and administrative states of the interface. State of an interface (not a subinterface): · UP—The interface is both physically and administratively up. · DOWN—The interface is in either of the following states: ¡ The interface is administratively up and physically down (probably because no physical link is available or the link has failed). ¡ The interface is administratively down (shut down by using the shutdown command). State of a subinterface: · UP—The interface is administratively up. The parent interface is both physically and administratively up. · DOWN—The interface or its parent interface was shut down by using the shutdown command, or the parent interface is physically down. |
OAM State |
OAM protocol state: UP or DOWN. |
PVC State |
PVC state: · UP—The following states are up: ¡ State of the ATM interface to which the PVC belongs. ¡ Shutdown state. ¡ OAM state. · DOWN—One or more of the following states is down: ¡ State of the ATM interface to which the PVC belongs. ¡ Shutdown state. ¡ OAM state. |
Input: 0 packets, 0 bytes, 0 errors |
Counts of received packets, bytes, and packet errors. |
Output: 0 packets, 0 bytes, 0 errors |
Counts of transmitted packets, bytes, and packet errors. |
Output queue |
QoS packet output queue information of the PVC. |
OAM cells received |
Number of received OAM cells. |
F5 Loopback |
Number of received F5 Loopback cells. |
F5 AIS |
Number of received AIS cells. If the AIS alarm state is not supported, this command displays only the number of AIS cells, rather than the AIS alarm state in the OAM AIS State field. |
F5 RDI |
Number of received RDI cells. If the RDI alarm state is not supported, this command displays only the number of RDI cells, rather than the RDI alarm state in the OAM RDI State field. |
OAM cells sent |
Number of transmitted OAM cells. |
F5 Loopback |
Number of transmitted F5 Loopback cells. |
OAM cell drops |
Number of dropped OAM cells. |
display atm pvc-info
Use display atm pvc-info to display PVC information.
Syntax
display atm pvc-info [ interface interface-type { interface-number | interface-number.subnumber } [ pvc { pvc-name | vpi/vci } ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type { interface-number | interface-number.subnumber }: Specifies an interface by its type and number. Both ATM interfaces and ATM subinterfaces are supported.
pvc: Displays information about a PVC.
pvc-name: Specifies a PVC by its name, a case-sensitive string of 1 to 15 characters, excluding slashes (/) and hyphens (-). For example, neither 1/20 nor a-b is a valid PVC name.
vpi/vci: Specifies a PVC by its VPI and VCI values. The value range for the vpi argument is 0 to 255. The value range for the vci argument varies by interface type. For more information, see Table 46. The values of the vpi and vci arguments cannot be 0 at the same time. As a best practice, do not use VCI values 0 through 31 because they are reserved for special purposes.
Usage guidelines
If you do not specify an ATM interface, this command displays brief information about all PVCs on all ATM interfaces.
If you specify an ATM interface but do not specify a PVC, this command displays brief information about all PVCs on the specified ATM interface.
If you specify an ATM interface and a PVC, this command displays detailed information about the specified PVC.
Examples
# Display brief information about all PVCs on all ATM interfaces.
<Sysname> display atm pvc-info
VPI/VCI State PVC name Encap Protocol Interface
1/32 UP aa SNAP IP ATM2/4/0
1/33 UP Sysname MUX None ATM2/4/0
1/55 UP datacomm SNAP PPP ATM2/4/0.1
2/66 UP N/A SNAP IP ATM2/4/0.4
2/101 UP beijing SNAP ETH ATM2/4/0.2
Table 42 Command output
Description |
|
State |
PVC state: · UP—The following states are up: ¡ State of the ATM interface to which the PVC belongs. ¡ Shutdown state. ¡ OAM state. · DOWN—One or more of the following states is down: ¡ State of the ATM interface to which the PVC belongs. ¡ Shutdown state. ¡ OAM state. |
PVC name |
PVC name. N/A means no PVC name. |
Encap |
AAL5 encapsulation type of the PVC: · SNAP—LLC/SNAP encapsulation. · NLPID—RFC1490 encapsulation. · MUX—MUX multiplexing encapsulation. |
Protocol |
Upper-layer protocol running on the PVC: · PPP—PPP protocol. · IP—IP protocol. · ETH—Ethernet protocol. · None—No protocol is configured. |
Interface |
Name of the interface to which the PVC belongs. |
# Display detailed information about the specified PVC.
<Sysname> display atm pvc-info interface atm 2/4/1 pvc 1/100
ATM2/4/1, VPI: 1, VCI: 100
Encapsulation: SNAP, Protocol: IP
Service-type: UBR, Output-pcr: 200 kbps
Transmit-Priority: 0
OAM loopback interval: 0 sec(disabled), OAM loopback retry interval: 1 sec
OAM loopback retry count (up/down): 3/5
OAM AIS-RDI count (up/down): 3/1
Interface State: UP, OAM State: UP, PVC State: UP
Input: 0 packets, 0 bytes, 0 errors
Output: 0 packets, 0 bytes, 0 errors
Output queue: (Urgent queuing : Size/Length/Discards) 0/100/0
Output queue: (Protocol queuing : Size/Length/Discards) 0/500/0
Output queue: (FIFO queuing : Size/Length/Discards) 0/75/0
OAM cells received: 42
F5 Loopback: 0, F5 AIS: 42, F5 RDI: 0
OAM cells sent: 0
F5 Loopback: 0
OAM cell drops: 0
Table 43 Command output
Field |
Description |
ATM2/4/1 |
Name of the interface to which the PVC belongs. |
Encapsulation |
AAL5 encapsulation type of the PVC: · SNAP—LLC/SNAP encapsulation. · NLPID—RFC1490 encapsulation. · MUX—MUX multiplexing encapsulation. |
Protocol |
Upper-layer protocol running on the PVC: · PPP—PPP protocol. · IP—IP protocol. · ETH—Ethernet protocol. · None—No protocol is configured. |
Service-type |
Services type: CBR, UBR, VBR-NRT, or VBR-RT. |
Output-pcr |
Peak output rate of ATM cells. |
OAM loopback interval |
Interval at which OAM F5 Loopback cells are sent. |
OAM loopback retry interval |
Interval at which OAM F5 Loopback retransmission detection cells are sent. |
OAM loopback retry count (up/down) |
Number of cells that are detected as up and down in OAM detection. |
OAM AIS-RDI count (up/down) |
Number of seconds that are detected as up in OAM AIS-RDI detection. Number of cells that are detected as down in OAM AIS-RDI detection. |
Interface State |
Name of the interface to which the PVC belongs, and the physical and administrative states of the interface. State of an interface (not a subinterface): · UP—The interface is both physically and administratively up. · DOWN—The interface is in either of the following states: ¡ The interface is administratively up and physically down (probably because no physical link is available or the link has failed). ¡ The interface is administratively down (shut down by using the shutdown command). State of a subinterface: · UP—The interface is administratively up. The parent interface is both physically and administratively up. · DOWN—The interface or its parent interface was shut down by using the shutdown command, or the parent interface is physically down. |
OAM State |
OAM protocol state: UP or DOWN. |
PVC State |
PVC state: · UP—The following states are up: ¡ State of the ATM interface to which the PVC belongs. ¡ Shutdown state. ¡ OAM state. · DOWN—One or more of the following states is down: ¡ State of the ATM interface to which the PVC belongs. ¡ Shutdown state. ¡ OAM state. |
Input: 0 packets, 0 bytes, 0 errors |
Counts of received packets, bytes, and packet errors. |
Output: 0 packets, 0 bytes, 0 errors |
Counts of transmitted packets, bytes, and packet errors. |
Output queue |
QoS packet output queue information of the PVC. |
OAM cells received |
Counts of received OAM cells. |
F5 Loopback |
Counts of received F5 Loopback cells. |
F5 AIS |
Number of received AIS cells. If the AIS alarm state is not supported, this command displays only the number of AIS cells, rather than the AIS alarm state in the OAM AIS State field. |
F5 RDI |
Number of received RDI cells. If the RDI alarm state is not supported, this command displays only the number of RDI cells, rather than the RDI alarm state in the OAM RDI State field. |
OAM cells sent |
Number of transmitted OAM cells. |
F5 Loopback |
Number of transmitted F5 Loopback cells. |
OAM cell drops |
Number of dropped OAM cells. |
display interface virtual-ethernet
Use display interface virtual-ethernet to display VE interface information.
Syntax
display interface [ virtual-ethernet [ interface-number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-number: Specifies a VE interface by its number.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays information about interfaces in physically down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Usage guidelines
If you do not specify the virtual-ethernet keyword, this command displays information about all interfaces on the device.
If you specify the virtual-ethernet keyword but do not specify the interface-number argument, this command displays information about all existing VE interfaces.
Examples
# Display detailed information about VE interface Virtual-Ethernet 2/4/1.
<Sysname> display interface virtual-ethernet 2/4/1
Virtual-Ethernet2/4/1
Current state: UP
Line protocol state: UP
Description: Virtual-Ethernet2/4/1 Interface
Bandwidth: 20000kbps
Maximum Transmit Unit: 1500
Internet protocol processing: disabled
IP Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 00e0-fc0d-9485
IPv6 Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 00e0-fc0d-9485
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 drops
Output: 0 packets, 0 bytes, 0 drops
# Display brief information about VE interface Virtual-Ethernet 2/4/1.
<Sysname> display interface virtual-ethernet 2/4/1 brief
Brief information on interface(s) under route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Main IP Description
VE1 DOWN DOWN --
# Display information about all VE interfaces in physically down state and the causes.
<Sysname> display interface virtual-ethernet brief down
Brief information on interface(s) under bridge mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
VE2/4/1 DOWN Not connected
Table 44 Command output
Field |
Description |
Current state |
Physical state of the interface: · Administratively DOWN—The interface was shut down by using the shutdown command. · DOWN—The interface is administratively up but physically down (probably because no physical link is available or the link has failed). · UP—The interface is both administratively and physically up. |
Line protocol state |
Link layer protocol state of the interface: UP or DOWN. |
Internet protocol processing |
Internet protocol processing state of the interface. |
IP Packet Frame Type |
Encapsulation format for IPv4 packets. PKTFMT_ETHNT_2 stands for Ethernet II frame format. |
IPv6 Packet Frame Type |
Encapsulation format for IPv6 packets. |
Hardware Address |
MAC address of the interface. |
Last clearing of counters: Never |
Time when the reset counters interface command was last used to clear the interface statistics. Never indicates the reset counters interface command has never been used on the interface after the device has started up. |
Last 300 seconds input rate |
Average packet input rate over the last 300 seconds. |
Last 300 seconds output rate |
Average packet output rate over the last 300 seconds. |
Input |
Input packet statistics: · packets—Number of packets. · bytes—Total bytes. · drops—Number of dropped packets. |
Output |
Output packet statistics: · packets—Number of packets. · bytes—Total bytes. · drops—Number of dropped packets. |
Brief information on interface(s) under route mode |
Brief information about the Layer 3 interface. |
Link: ADM - administratively down; Stby - standby |
Link layer state of the interface: · ADM—The interface was shut down by the network administrator. To recover its physical layer state, use the undo shutdown command. · Stby—The interface is a standby interface. You can use the display interface-backup state command to check the corresponding primary interface. |
Protocol: (s) - spoofing |
If the protocol attribute of an interface includes the spoofing flag (an s in parentheses), the data link layer protocol state of the interface is shown as UP, but its link is an on-demand link or not present at all. |
Interface |
Abbreviation of the interface name. |
Link |
Physical connection state of the interface: · UP—The interface is physically up. · ADM—The interface was shut down manually. You can bring up the interface by using the undo shutdown command. · Stby—The interface is a standby interface. |
Protocol |
Data link layer protocol state: · UP—The data link layer is up. · DOWN—The data link layer is down. · UP(s)—The data link layer protocol state of the interface is up, but its link is an on-demand link or not present at all. |
Main IP |
Primary IP address of the interface. |
Description |
Description for the interface configured with command description. The display interface brief command displays the first 27 characters when you do not specify the description keyword. It displays the entire description when you specify the description keyword. |
Cause |
Cause for a down physical link: · Administratively—The link was shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—No physical connection exists (probably due to network cable failures). |
encapsulation
Use encapsulation to configure the ATM AAL5 encapsulation type for a PVC or PVC-group.
Use undo encapsulation to restore the default.
Syntax
encapsulation { aal5mux | aal5nlpid | aal5snap }
undo encapsulation
Default
The ATM AAL5 encapsulation type is aal5snap.
Views
PVC view
PVC-group view
Predefined user roles
network-admin
Parameters
aal5mux: Specifies the MUX multiplexing encapsulation type.
aal5nlpid: Specifies the RFC1490 encapsulation type.
aal5snap: Specifies the LLC/SNAP encapsulation type.
Usage guidelines
Different encapsulation types support different mappings:
· aal5snap encapsulation supports IPoA, IPoEoA, PPPoA, and PPPoEoA mappings.
· aal5mux encapsulation supports IPoA, IPoEoA, PPPoA, and PPPoEoA mappings, but can only support one protocol at a time.
· aal5nlpid encapsulation supports only IPoA mappings.
Follow these guidelines when you configure the ATM AAL5 encapsulation type:
· Devices on the two ends must be configured with the same ATM AAL5 encapsulation types.
· Only aal5snap supports InARP. You cannot configure InARP when aal5mux or aal5nlpid is used.
· Although a PVC or PVC-group can carry multiple protocols, a specific encapsulation type might not support some of the applications (such as IPoA, IPoEoA, PPPoA, and PPPoEoA). In such cases, the system displays error prompts.
· When you change the encapsulation type for a PVC or PVC-group, and the mappings that you have configured conflict with the new encapsulation type, the PVC or PVC-group deletes the configurations of all conflicting mappings.
· This command is not applicable to PVCs in a PVC-group.
Examples
# Set the AAL5 encapsulation for PVC 1/32 on interface ATM 2/4/0 to aal5snap.
<Sysname>system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc 1/32
[Sysname-ATM2/4/0-pvc-1/32] encapsulation aal5snap
interface virtual-ethernet
Use interface virtual-ethernet to create a VE interface or VE subinterface and enter its view, or enter the view of an existing VE interface or VE subinterface.
Use undo interface virtual-ethernet to remove a VE interface or subinterface.
Syntax
interface virtual-ethernet { interface-number | interface-number.subnumber }
undo interface virtual-ethernet { interface-number | interface-number.subnumber }
Default
No VE interface or VE subinterfaces exist.
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a VE interface by its number.
interface-number.subnumber: Specifies a VE subinterface by its number. The interface-number argument represents the number of the VE interface. The subnumber argument represents the number of the subinterface.
Usage guidelines
The baud rate of the VE interface is 10000000 bps.
Examples
# Create VE interface Virtual-Ethernet 2/4/1 and enter its view.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1
[Sysname-Virtual-Ethernet2/4/1]
# Create VE subinterface Virtual-Ethernet 2/4/1.1 and enter its view.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1.1
[Sysname-Virtual-Ethernet2/4/1.1]
mac-address
Use mac-address to specify the MAC address for a VE interface.
Use undo mac-address to restore the default.
Syntax
mac-address mac-address
undo mac-address
Default
The MAC address of the VE interface is the bridge MAC address of the device.
Views
VE interface view
Predefined user roles
network-admin
Parameters
mac-address: Specifies the MAC address in the format of H-H-H.
Usage guidelines
A VE interface uses the bridge MAC address of the device as its MAC address. As a result, all VE interfaces share the same MAC address. You must use the mac-address command to specify a MAC address for each VE interface in the following condition:
· The VE interfaces are connected to a DHCP server through different PVCs.
· The VE interfaces need to obtain IP addresses from the DHCP server through static allocation.
Examples
# Set the MAC address of VE interface Virtual-Ethernet 2/4/1 to 0001-0001-0001.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1
[Sysname-Virtual-Ethernet2/4/1] mac-address 1-1-1
map bridge
Use map bridge to create an IPoEoA mapping or PPPoEoA mapping for a PVC or PVC-group.
Use undo map bridge to delete the mapping.
Syntax
map bridge virtual-ethernet interface-number
undo map bridge
Default
No IPoEoA mappings or PPPoEoA mappings exist.
Views
PVC view
PVC-group view
Predefined user roles
network-admin
Parameters
virtual-ethernet interface-number: Specifies a VE interface by its number. The interface must have already been created.
Usage guidelines
aal5snap and aal5mux encapsulations support IPoEoA and PPPoEoA mappings.
You can create a maximum of 512 mappings on a VE interface.
A PVC or PVC-group can be mapped to only one VE interface.
A VE interface can only be bound to the PVC or PVC-group on the same interface card. Before you bind a VE interface, check its interface number to make sure the VE interface is on the same card as the ATM interface to which the PVC or PVC-group belongs.
This command is not applicable to PVCs in a PVC-group.
Before you configure IPoEoA or PPPoEoA, you must specify a VE interface.
Examples
The following example demonstrates a complete process of IPoEoA configuration.
# Create VE interface Virtual-Ethernet 2/4/1.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1
# Set the IP address of the VE interface to 10.1.1.1/16.
[Sysname-Virtual-Ethernet2/4/1] ip address 10.1.1.1 255.255.0.0
[Sysname-Virtual-Ethernet2/4/1] quit
# Create PVC 1/102 on the ATM interface ATM 2/4/0.
[Sysname] interface atm 2/4/0
# Create an IPoEoA mapping using the created VE interface in PVC view.
[Sysname-ATM2/4/0-pvc-1/102] map bridge virtual-ethernet 2/4/1
Related commands
encapsulation
map ip
Use map ip to create an IPoA mapping for a PVC or PVC-group.
Use undo map ip to delete the mapping.
Syntax
map ip { ip-address | default | inarp [ minutes ] }
undo map ip [ ip-address | default | inarp ]
Default
No IPoA mappings for a PVC or PVC group exist.
Views
PVC view
PVC-group view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the remote IP address mapped to the PVC or PVC-group.
default: Sets the default PVC mapping. If no PVC mapping can be found for the next hop address of a packet, the packet is sent through the default PVC or PVC-group.
inarp: Enables InARP on the PVC.
minutes: Specifies the interval for sending InARP packets, in the range of 1 to 600 minutes. The default is 15 minutes.
Usage guidelines
All encapsulations support IPoA. Only aal5snap supports InARP. You cannot configure InARP when aal5mux or aal5nlpid is used.
A PVC or PVC-group can be configured with multiple IP address mappings, including static IP address mapping, default mapping, and InARP mapping.
Different PVCs or PVC-groups on the same interface cannot be mapped to the same IP address.
The PVCs or PVC-groups on the same interface can be configured with only one default mapping.
If you do not specify any arguments or keywords, the undo map ip command deletes all static IP address mappings, default mappings, and InARP mappings on the PVC or PVC-group.
This command is not applicable to PVCs in a PVC-group.
Examples
# Create a static IP address mapping on PVC 1/32, and set the IP address of the remote end to 61.123.30.169.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc 1/32
[Sysname-ATM2/4/0-pvc-1/32] map ip 61.123.30.169
# Enable InARP mapping on PVC 1/33, and set the InARP packet sending interval to 10 minutes.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc 1/33
[Sysname-ATM2/4/0-pvc-1/33] map ip inarp 10
# Delete all IP address mappings on PVC 1/33.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc 1/33
[Sysname-ATM2/4/0-pvc-1/33] undo map ip
Related commands
encapsulation
map ppp
Use map ppp to create a PPPoA mapping for a PVC or PVC-group.
Use undo map ppp to delete the PPPoA mapping.
Syntax
map ppp virtual-template vt-number
undo map ppp
Default
No PPPoA mappings for a PVC or PVC group exist.
Views
PVC view
PVC-group view
Predefined user roles
network-admin
Parameters
vt-number: Specifies the number of the VT interface corresponding to a PPPoA mapping. The VT interface must have already been created.
Usage guidelines
aal5snap and aal5mux encapsulations support PPPoA mapping.
A PVC or PVC-group can be mapped to only one VT interface.
This command is not applicable to PVCs in a PVC-group.
Examples
The following example demonstrates a complete process of PPPoA configuration.
# Create a VT interface Virtual-Template 10, and configure an IP address for it.
<Sysname> system-view
[Sysname] interface virtual-template 10
[Sysname-Virtual-Template10] ip address 202.38.160.1 255.255.255.0
[Sysname-Virtual-Template10] quit
# Create PVC 1/101 on interface ATM 2/4/0.
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc 1/101
# Create a PPPoA mapping using the created VT interface.
[Sysname-ATM2/4/0-pvc-1/101] map ppp virtual-template 10
Related commands
encapsulation
mtu
Use mtu to configure the MTU for an ATM interface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU of an ATM interface is 1500 bytes.
Views
VE interface view
VE subinterface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU in the range of 46 to 1500 bytes.
Usage guidelines
The MTU setting can affect IP packet fragmentation and reassembly on the interface.
To validate the MTU setting for an interface, execute the shutdown command and then the undo shutdown command on the interface.
Examples
# Set the MTU for the interface VE 1 to 200 bytes.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1
[Sysname- Virtual-Ethernet2/4/1] mtu 200
oam ais-rdi
Use oam ais-rdi to configure the parameters related to AIS/RDI alarm cell detection.
Use undo oam ais-rdi to restore the default.
Syntax
oam ais-rdi up up-seconds down down-seconds
undo oam ais-rdi
Default
A PVC comes up if no AIS/RDI alarm cells are received in the last three seconds, and it goes down if it receives successive AIS/RDI alarm cells in one second.
Views
PVC view
PVC view in a PVC-group
Predefined user roles
network-admin
Parameters
up up-seconds: Specifies the time (in seconds) within which the PVC comes up if no AIS/RDI alarm cells are received. The value range for the up-seconds argument is 3 to 60 seconds.
down down-seconds: Specifies the time (in seconds) within which the PVC goes down if it receives successive AIS/RDI alarm cells. The value range for the down-seconds argument is 1 to 60 seconds.
Usage guidelines
The system uses a 1-second timer to detect AIS/RDI alarm cells.
· A PVC goes down if it receives successive AIS/RDI alarm cells in the time period specified by the down-seconds argument.
· A PVC comes up if no AIS/RDI alarm cells are received in the time period specified by the up-seconds argument.
Examples
# Configure the AIS/RDI alarm detection parameters for PVC 1/32, setting up-seconds to 5 and down-seconds to 5.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc 1/32
[Sysname-ATM2/4/0-pvc-1/32] oam ais-rdi up 5 down 5
# Configure the AIS/RDI alarm detection parameters for PVC 1/33 of PVC-group 2, setting up-seconds to 5 and down-seconds to 5.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 2
[Sysname-ATM2/4/0-pvc-group-2] pvc 1/33
[Sysname-ATM2/4/0-pvc-group-2-pvc-1/33] oam ais-rdi up 5 down 5
oam loopback
Use oam loopback to enable OAM F5 Loopback cell transmission and retransmission detection and modify related parameters.
Use undo oam loopback to disable OAM F5 Loopback cell transmission and retransmission detection.
Syntax
oam loopback interval [ up up-count down down-count retry retries ]
undo oam loopback
Default
OAM F5 Loopback cell transmission is disabled. Responses are sent if OAM F5 Loopback cells are received.
Views
PVC view
PVC view in a PVC-group
Predefined user roles
network-admin
Parameters
interval: Specifies the interval for sending OAM F5 Loopback cells, in the range of 1 to 600 seconds.
up up-count: Specifies the number of successive OAM F5 Loopback cells received before the PVC comes up. The value range for the up-count argument is 1 to 600, and the default is 3.
down down-count: Specifies the number of successive OAM F5 Loopback cells not received before the PVC goes down. The value range for the down-count argument is 1 to 600, and the default is 5.
retry retries: Specifies the interval for sending retransmission detection cells before PVC state change. The value range for the retries argument is 1 to 1000 seconds, and the default is 1 second.
Usage guidelines
After you enable OAM F5 Loopback cell transmission and retransmission detection on a PVC, the PVC sends OAM F5 Loopback cells at the interval specified by the interval argument. If the PVC receives no responses after a time period specified by the retries argument, it immediately sends OAM F5 Loopback cells again.
The PVC state is updated during the OAM F5 Loopback cell transmission and retransmission detection process.
· If the PVC is down, it comes up when the number of successive OAM F5 Loopback cells received reaches the value specified by the up-count argument.
· If the PVC is up, it goes down when the number of successive OAM F5 Loopback cells not received reaches the value specified by the down-count argument.
Examples
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc 1/32
[Sysname-ATM2/4/0-pvc-1/32] oam loopback 12 up 4 down 4 retry 1
# Enable OAM F5 Loopback detection on PVC 1/33 of PVC-group 2, and set the interval, up-count, down-count, and retries arguments to 12, 4, 3, and 2, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 2
[Sysname-ATM2/4/0-pvc-group-2] pvc 1/33
[Sysname-ATM2/4/0-pvc-group-2-pvc-1/33] oam loopback 12 up 4 down 3 retry 2
oam ping
Use oam ping to send OAM F5 end-to-end cells through the specified PVC on the specified ATM interface to check the link state.
Syntax
oam ping interface interface-type { interface-number | interface-number.subnumber } pvc { pvc-name | vpi/vci } [ number timeout ]
Views
Any view
Predefined user roles
network-admin
Parameters
interface interface-type { interface-number | interface-number.subnumber }: Specifies an interface by its type and number. Both ATM interfaces and ATM subinterfaces are supported.
pvc: Sends OAM F5 end-to-end cells through the specified PVC.
pvc-name: Specifies a PVC by its name, a case-sensitive string of 1 to 15 characters, excluding slashes (/) and hyphens (-). For example, neither 1/20 nor a-b is a valid PVC name.
vpi/vci: Specifies a PVC by its VPI and VCI values. The value range for the vpi argument is 0 to 255. The value range for the vci argument varies by interface type. For more information, see Table 46. The values of the vpi and vci arguments cannot be 0 at the same time. As a best practice, do not use VCI values 0 through 31 because they are reserved for special purposes.
number: Specifies the number of OAM F5 end-to-end cells to be transmitted, in the range of 1 to 1000. The default is 5.
timeout: Specifies the OAM F5 end-to-end response timeout period in the range of 1 to 30 seconds. The default is 2 seconds.
Usage guidelines
Use this command to send OAM F5 end-to-end cells through the specified PVC on the specified ATM interface, and check the link state according to the response condition.
After you configure the oam ping command, the system sends an OAM F5 end-to-end cell. If the system receives a response within the time specified by the timeout argument, it immediately sends another OAM F5 end-to-end cell. If the system does not receive a response within the time specified by the timeout argument, the system sends an OAM F5 end-to-end cell again. In an oam ping process, the number of OAM F5 end-to-end cells transmitted is specified by the number argument. If no response is received, a link failure or link congestion might occur.
Examples
# Check the link state of PVC 1/32 on the interface ATM 2/4/0 by sending three cells and setting the timeout period to 1 second.
<Sysname> oam ping interface atm 2/4/0 pvc 1/32 3 1
PING interface ATM2/4/0 pvc 1/32 with 3 of 53 bytes of oam F5 end-to-end cell(s),
timeout is 1 second(s), press CTRL_C to break
Receive reply from pvc 1/32: time=1 ms
Receive reply from pvc 1/32: time=1 ms
Receive reply from pvc 1/32: time=1 ms
oam ping statistics:
Cells: Sent = 3, Received = 3, Lost = 0 (0.00% loss)
# Check the link state of PVC 5/100 on the interface ATM 2/4/0 by sending three cells and setting the timeout period to 1 second.
<Sysname> oam ping interface atm 2/4/0 pvc 5/100 3 1
PING interface ATM2/4/0 pvc 5/100 with 3 of 53 bytes of oam F5 end-to-end cell(s),
timeout is 1 second(s), press CTRL_C to break
Request time out!
Request time out!
Request time out!
oam ping statistics:
Cells: Sent = 3, Received = 0, Lost = 3 (100.00% loss)
Table 45 Command output
Field |
Description |
PING interface ATM2/4/0 pvc 1/32 |
Check if the link of PVC 1/32 on ATM 2/4/0 is available. |
53 bytes |
Number of bytes in each cell. |
timeout is 1 second(s) |
Response timeout period. |
Receive reply from pvc 1/32: time=1 ms |
A response is received within the specified time. |
Request time out |
No response is received within the specified timeout period. |
Sent = 3 |
Number of transmitted cells. |
Received = 0 |
Number of received responses. |
Lost = 3(100.00% loss) |
Cell loss rate (percentage of the number of unresponded cells to the total number of cells transmitted). |
precedence
Use precedence to configure the priority of IP packets carried by the PVC of a PVC-group.
Use undo precedence to restore the default.
Syntax
precedence { min-number [ to max-number ] | default }
undo precedence
Default
No priority is configured for IP packets.
Views
PVC view in a PVC-group
Predefined user roles
network-admin
Parameters
min-number: Specifies the lowest priority of IP packets carried by the PVC, in the range of 0 to 7.
max-number: Specifies the highest priority of IP packets carried by the PVC, in the range of 0 to 7. The max value must be equal to or larger than the min value.
default: Specifies the PVC as the default PVC. IP packets with priorities not specified for any PVC are sent through the default PVC.
Usage guidelines
This command is applicable only to the PVCs in a PVC-group.
If no default PVC exists in a PVC group, IP packets with priorities not specified for any PVC are distributed across all PVCs that are not configured with priorities on a per-packet basis.
If no PVC is specified as the default PVC and all PVCs are configured with transmission priorities, IP packets with priorities not specified for any PVC are dropped.
This command cannot change the priority of an IP packet.
Examples
# Configure PVC aa with a VPI/VCI value of 1/32 to carry IP packets with priorities from 0 to 3.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1] pvc aa 1/32
[Sysname-ATM2/4/0-pvc-group-1-pvc-aa-1/32] precedence 0 to 3
pvc
In ATM interface view or ATM subinterface view:
Use pvc to create a PVC and enter its view, or enter the view of an existing PVC.
Use undo pvc to delete the specified PVC.
In PVC-group view:
Use pvc to create a PVC for a PVC group and enter PVC view, or enter the view of an existing PVC.
Use undo pvc to remove the specified PVC from a PVC-group and delete the PVC.
Syntax
pvc { pvc-name [ vpi/vci ] | vpi/vci }
undo pvc { pvc-name | vpi/vci }
Default
No PVCs exist.
Views
ATM interface view
ATM subinterface view
PVC-group view
Predefined user roles
network-admin
Parameters
pvc-name: Specifies a PVC by its name, a case-sensitive string of 1 to 15 characters, excluding slashes (/) and hyphens (-). For example, neither 1/20 nor a-b is a valid PVC name.
vpi/vci: Specifies a PVC by its VPI and VCI values. The value range for the vpi argument is 0 to 255. The value range for the vci argument varies by interface type. For more information, see Table 46. The values of the vpi and vci arguments cannot be 0 at the same time. As a best practice, do not use VCI values 0 through 31 because they are reserved for special purposes.
Table 46 VCI value ranges for different interface types
Interface type |
VCI value range |
ATM ADSL2+ |
0 to 255 |
ATM SHDSL_4WIRE |
0 to 255 |
ATM SHDSL_8WIRE_BIS |
0 to 255 |
ATM OC-3c/STM-1 |
0 to 1023 |
ATM subinterface |
Same as that of the ATM interface to which the ATM subinterface belongs. |
PVC-group |
Same as that of the ATM interface to which the PVC-group belongs. |
Usage guidelines
When you create a PVC, you must specify the VPI/VCI value for it. The VPI/VCI value of a PVC is unique on an interface (including interface, subinterface, and PVC-group).
If you have specified the PVC name when creating the PVC, you can enter the PVC view by using the pvc pvc-name [ vpi/vci ] command, and delete the PVC by using the undo pvc pvc-name [ vpi/vci ] or undo pvc vpi/vci command.
You can configure only one PVC on an ATM P2P subinterface.
You can create a maximum of eight PVCs in a PVC-group.
You cannot delete a PVC from a PVC-group in ATM interface view or ATM subinterface view.
Examples
# Create a PVC named aa on the interface ATM 2/4/0, and set its VPI/VCI value to 1/101.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-aa-1/101]
# Create a PVC named bb for PVC-group 1, and set its VPI/VCI value to 1/102.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1] pvc bb 1/102
[Sysname-ATM2/4/0-pvc-group-1-pvc-bb-1/102]
Related commands
display atm pvc-info
pvc-group
pvc-group
Use pvc-group to create a PVC-group and enter its view, or enter the view of an existing PVC-group.
Use undo pvc-group to delete the specified PVC-group.
Syntax
pvc-group group-number
undo pvc-group group-number
Default
No PVC-groups exist.
Views
ATM interface view
ATM subinterface view
Predefined user roles
network-admin
Parameters
group-number: Specifies a PVC-group by its number in the range of 1 to 128.
Usage guidelines
A PVC-group can share traffic load among PVCs in it by transmitting IP packets of different priorities through different PVCs.
You can configure the priority of IP packets carried by each PVC. IP packets are transmitted through the PVC corresponding to the priority of the IP packets.
· If no corresponding PVC is found, the IP packets are transmitted through the default PVC.
· If no default PVC is configured, the IP packets are distributed across the PVCs that are not configured with priorities on a per-packet basis.
· If all PVCs are configured with priorities, the IP packets are dropped.
Data packets that are not IP packets are distributed across all PVCs in the PVC-group on a per-packet basis.
All PVCs in a PVC-group obtain the encapsulation type and protocol type from the PVC-group.
A PVC belongs to one PVC-group.
This command is applicable to ATM P2MP subinterfaces, but not to ATM P2P subinterfaces.
The number of a PVC-group is unique on an interface (including interface and subinterface).
Examples
# Create a PVC-group numbered 1.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1]
Related commands
display atm pvc-group
remark atm-clp
Use remark atm-clp to re-mark the cell loss priority (CLP) flag value of ATM cells.
Use undo remark atm-clp to restore the default.
Syntax
remark [ green | red | yellow ] atm-clp atm-clp-value
undo remark [ green | red | yellow ] atm-clp
Default
The CLP flag value of ATM cells is not re-marked.
Views
Traffic behavior view
Predefined user roles
network-admin
Parameters
green: Re-marks the CLP flag value of a green packet.
red: Re-marks the CLP flag value of a red packet.
yellow: Re-marks the CLP flag value of a yellow packet.
atm-clp-value: Sets the CLP flag value to 0 or 1. The cells with a CLP flag value of 1 are dropped first when network congestion occurs.
Usage guidelines
This command is applicable only to outbound PVCs.
Examples
# Set the CLP flag value of ATM cells to 1.
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] remark atm-clp 1
reset atm interface
Use reset atm interface to clear PVC statistics.
Syntax
reset atm interface [ interface-type { interface-number | interface-number.subnumber } ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-type { interface-number | interface-number.subnumber }: Clears statistics about all PVCs (including PVCs on the interface and PVCs of the PVC-groups) for the specified interface. Both ATM interfaces and ATM subinterfaces are supported. If you do not specify an interface, this command clears statistics about all PVCs for all interfaces.
Usage guidelines
This command clears statistics only about PVCs. To clear statistics about interfaces, use the reset counters interface command.
Examples
# Clear statistics about all PVCs for the interface ATM 2/4/0.
<Sysname> reset atm interface atm 2/4/0
reset counters interface virtual-ethernet
Use reset counters interface virtual-ethernet to clear VE interface statistics.
Syntax
reset counters interface [ virtual-ethernet [ interface-number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
virtual-ethernet: Clears the statistics for a VE interface.
interface-number: Specifies a VE interface by its number.
Usage guidelines
Before you collect traffic statistics within a specific time period on an interface, clear the existing statistics for the interface.
If you do not specify the virtual-ethernet keyword, this command clears statistics for all interfaces.
If you specify the virtual-ethernet keyword but do not specify the interface-number argument, this command clears statistics for all VE interfaces.
If you specify both the virtual-ethernet keyword and the interface-number argument, this command clears statistics for the specified VE interface.
Examples
# Clear statistics for the interface Virtual-Ethernet 2/4/1.
<Sysname> reset counters interface virtual-ethernet2/4/1
service cbr
Use service cbr to set the PVC service type to CBR and set the related parameters.
Use undo service to restore the default.
Syntax
service cbr output-pcr [ cdvt cdvt_value ]
undo service
Default
The service type of a PVC is UBR. The peak output rate of ATM cells equals the maximum bandwidth of the interface to which the PVC belongs.
Views
PVC view
PVC view in a PVC-group
Predefined user roles
network-admin
Parameters
output-pcr: Specifies the peak output rate of ATM cells in kbps. Table 47 shows the value ranges for the output-pcr argument on different interfaces.
Table 47 Peak output rate value ranges
Interface type |
Peak output rate value range |
ATM ADSL2+ |
64 to 640 |
ATM SHDSL_4WIRE |
128 to 4624 |
ATM SHDSL_8WIRE_BIS |
256 to 22784 |
ATM OC-3c/STM-1 |
64 to 155000 |
ATM subinterface |
Same as that of the ATM interface to which the ATM subinterface belongs. |
PVC-group |
Same as that of the ATM interface to which the PVC-group belongs. |
cdvt cdvt_value: Specifies the cell delay variation tolerance in the range of 0 to 10000 μs. The default is 500 μs, which means that the maximum cell delay is 500 μs.
Usage guidelines
When the peak output rate is exceeded, the system allocates caches based on the specified CDVT value to ensure service stability. A smaller CDVT value requires more hardware resources and is harder to configure. If the configuration fails, the following message appears: "Failed to set service parameter. Please adjust cdvt value." In this situation, configure a larger CDVT value.
You can use this command as well as the service ubr, service vbr-nrt, and service vbr-rt commands to set the service type and parameters of a PVC. If you execute this command multiple times, the most recent configuration takes effect.
Each PVC occupies a separate bandwidth. As a best practice, configure PVCs requiring more bandwidths first.
Examples
# Create a PVC named aa on the interface ATM 2/4/0, and set the VPI/VCI, service type, output-pcr, and cdvt_value to 1/101, CBR, 50000, and 1000, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-aa-1/101] service cbr 50000 cdvt 1000
# Create a PVC named aa in PVC-group 1, and set the VPI/VCI, service type, output-pcr, and cdvt_value to 1/101, CBR, 50000, and 1000, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-group-1-pvc-aa-1/101] service cbr 50000 cdvt 1000
Related commands
service ubr
service vbr-nrt
service vbr-rt
service ubr
Use service ubr to set the PVC service type to UBR and set the related parameters.
Use undo service to restore the default.
Syntax
service ubr output-pcr
undo service
Default
The service type of a PVC is UBR. The peak output rate of ATM cells equals the maximum bandwidth of the interface to which the PVC belongs.
Views
PVC view
PVC view in a PVC-group
Predefined user roles
network-admin
Parameters
output-pcr: Specifies the peak output rate of ATM cells in kbps. For more information about the value range, see Table 47.
Usage guidelines
You can use this command as well as the service cbr, service vbr-nrt, and service vbr-rt commands to set the service type and parameters of a PVC. If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Create a PVC named aa on the interface ATM 2/4/0, and set the VPI/VCI, service type, and output-pcr to 1/101, UBR, and 100000, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-aa-1/101] service ubr 100000
# Create a PVC named aa in PVC-group 1, and set the VPI/VCI, service type, and output-pcr to 1/101, UBR, and 100000, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-group-1-pvc-aa-1/101] service ubr 100000
Related commands
service cbr
service vbr-nrt
service vbr-rt
service vbr-nrt
Use service vbr-nrt to set the PVC service type to VBR-NRT and set the related parameters.
Use undo service to restore the default.
Syntax
service vbr-nrt output-pcr output-scr output-mbs
undo service
Default
The service type of a PVC is UBR. The peak output rate of ATM cells equals the maximum bandwidth of the interface to which the PVC belongs.
Views
PVC view
PVC view in a PVC-group
Predefined user roles
network-admin
Parameters
output-pcr: Specifies the peak output rate of ATM cells in kbps. For more information about the value range, see Table 47.
output-scr: Specifies the sustainable output rate of ATM cells in kbps. Its value ranges are the same as those of the output-pcr argument, and its value is equal to or smaller than the value of the output-pcr argument.
output-mbs: Specifies the maximum burst size for ATM cells (maximum number of ATM cells that the output interface can cache). The value range for this argument is 1 to 512.
Usage guidelines
You can use this command as well as the service cbr, service ubr, and service vbr-rt commands to set the service type and parameters of a PVC. If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Create a PVC named aa on the interface ATM 2/4/0, and set the VPI/VCI, service type, output-pcr, output-scr, and output-mbs to 1/101, VBR-NRT, 100000, 50000, and 320, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-aa-1/101] service vbr-nrt 100000 50000 320
# Create a PVC named aa in PVC-group 1, and set the VPI/VCI, service type, output-pcr, output-scr, and output-mbs to 1/101, VBR-NRT, 100000, 50000, and 320, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-group-1-pvc-aa-1/101] service vbr-nrt 100000 50000 320
Related commands
service cbr
service ubr
service vbr-rt
service vbr-rt
Use service vbr-rt to set the PVC service type to VBR-RT and set the related parameters.
Use undo service to restore the default.
Syntax
service vbr-rt output-pcr output-scr output-mbs
undo service
Default
The service type of a PVC is UBR. The peak output rate of ATM cells equals the maximum bandwidth of the interface to which the PVC belongs.
Views
PVC view
PVC view in a PVC-group
Predefined user roles
network-admin
Parameters
output-pcr: Specifies the peak output rate of ATM cells in kbps. For more information about the value range, see Table 47.
output-scr: Specifies the sustainable output rate of ATM cells in kbps. Its value ranges are the same as those of the output-pcr argument, and its value is equal to or smaller than the value of the output-pcr argument.
output-mbs: Specifies the maximum burst size of ATM cells (maximum number of ATM cells that the output interface can cache). The value range for this argument is 1 to 512.
Usage guidelines
You can use this command as well as the service cbr, service ubr, and service vbr-nrt commands to set the service type and parameters of a PVC. If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Create a PVC named aa on the interface ATM 2/4/0, and set the VPI/VCI, service type, output-pcr, output-scr, and output-mbs to 1/101, VBR-RT, 100000, 50000, and 320, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-aa-1/101] service vbr-rt 100000 50000 320
# Create a PVC named aa in PVC-group 1, and set the VPI/VCI, service type, output-pcr, output-scr, and output-mbs to 1/101, VBR-RT, 100000, 50000, and 320, respectively.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-group-1-pvc-aa-1/101] service vbr-rt 100000 50000 320
service cbr
service ubr
service vbr-nrt
shutdown
Use shutdown to shut down an interface.
Use undo shutdown to bring up an interface.
Syntax
shutdown
undo shutdown
Default
An interface is up.
Views
VE interface view
VE subinterface view
Predefined user roles
network-admin
Examples
# Shut down the VE interface Virtual-Ethernet 2/4/1.
<Sysname> system-view
[Sysname] interface virtual-ethernet 2/4/1
[Sysname-Virtual-Ethernet2/4/1] shutdown
shutdown
Use shutdown to shut down a PVC.
Use undo shutdown to bring up a PVC.
Syntax
shutdown
undo shutdown
Default
A PVC is up.
Views
PVC view
PVC view in a PVC-group
Predefined user roles
network-admin
Examples
# Bring up PVC 0/100 on the ATM interface ATM 2/4/0.1.
<Sysname> system-view
[Sysname] interface Atm 2/4/0.1
[Sysname-ATM2/4/0.1] pvc 0/100
[Sysname-ATM2/4/0.1-pvc-0/100] undo shutdown
# Bring up PVC 1/101 in PVC-group 1.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-group-1-pvc-aa-1/101] undo shutdown
transmit-priority
Use transmit-priority to configure the transmission priority for a PVC associated with the UBR, VBR-NRT, or VBR-RT service.
Use undo transmit-priority to restore the default.
Syntax
transmit-priority priority
undo transmit-priority
Default
The transmission priorities of the UBR service, VBR-NRT service, and VBR-RT service are 0, 5, and 8, respectively.
Views
PVC view
PVC view in a PVC-group
Predefined user roles
network-admin
Parameters
priority: Specifies the transmission priority in the range of 0 to 9. A higher value indicates a higher priority. Priorities 0 to 4 are for the UBR service, 5 to 7 are for the VBR-NRT service, and 8 to 9 are for the VBR-RT service.
Usage guidelines
PVCs with higher priorities occupy more bandwidths. PVCs with the same priority occupy the same bandwidth.
If you change the service type of a PVC, the transmission priority of the PVC is restored to the default.
Examples
# Set the transmission priority for PVC 1/32 of ATM 2/4/0 to 3.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc 1/32
[Sysname-ATM2/4/0-pvc-1/32] transmit-priority 3
# Set the transmission priority for PVC 1/101 in PVC-group 1 to 4.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] pvc-group 1
[Sysname-ATM2/4/0-pvc-group-1] pvc aa 1/101
[Sysname-ATM2/4/0-pvc-group-1-pvc-aa-1/101] transmit-priority 4
vp limit
Use vp limit to configure parameters for VP policing.
Use undo vp limit to restore the default.
Syntax
vp limit vpi scr
undo vp limit vpi
Default
VP policing is disabled.
Views
ATM interface view
Predefined user roles
network-admin
Parameters
vpi: Specifies the VPI value in the range of 0 to 255.
scr: Specifies the sustainable cell rate in kbps. For more information about the value range, see Table 47.
Usage guidelines
A VP is the collection of all PVCs with the same VPI value. VP policing is used to manage the maximum bandwidth of the VP, and monitor the traffic of the inbound and outbound directions of the VP on a physical interface. When the maximum transmission rate of the VP exceeds the specified value, the exceeded flows are dropped.
When VP policing is applied, the parameters of PVC are still valid. Packets can be transmitted or received only when the parameters of PVC and VP policing are met. In calculating the traffic, the LLC/SNAP, MUX, and NLPID headers are included, but the ATM cell header is not included.
Examples
# Set the flow of the VP with VPI value 1 to 2 Mbps.
<Sysname> system-view
[Sysname] interface atm 2/4/0
[Sysname-ATM2/4/0] vp limit 1 2000
service cbr
service ubr
service vbr-nrt
service vbr-rt
Modem management commands
This feature is supported only on the following interface modules and interfaces:
· AM interface modules.
· ASE interface modules.
· AUX interfaces.
· SAE interface modules that are operating in asynchronous mode.
country-code
Use country-code to set the modem country code on an AM interface.
Use undo country-code to restore the default.
Syntax
country-code area-name
undo country-code
Default
The country code is united-states.
Views
AM interface view
Predefined user roles
network-admin
Parameters
area-name: Specifies a country code. The following are available country codes:
australia |
france |
korea |
russia |
austria |
germany |
luxembourg |
singapore |
belgium |
greece |
malaysia |
southafrica |
brazil |
hongkong |
mexico |
spain |
bulgaria |
hungary |
netherlands |
sweden |
canada |
india |
new-zealand |
switzerland |
china |
ireland |
norway |
taiwan |
czechoslovakia |
israel |
philippines |
united-kingdom |
denmark |
italy |
poland |
united-states |
finland |
japan |
portugal |
|
Usage guidelines
CAUTION: Executing this command disconnects the modem connection that has been established on the interface. |
Modem encoding format varies by countries. Use this command to set the modem encoding format for a country.
Examples
# Set the country code to china on AM interface 2/4/0.
<Sysname> system-view
[Sysname] interface analogmodem 2/4/0
[Sysname-Analogmodem2/4/0] country-code china
modem answer-timer
Use modem answer-timer to set a dial-up connection timer.
Use undo modem answer-timer to restore the default.
Syntax
modem answer-timer time
undo modem answer-timer
Default
The dial-up connection timer is 60 seconds.
Views
User line view
Predefined user roles
network-admin
Parameters
time: Sets the dial-up connection timer in the range of 1 to 65535, in seconds.
Usage guidelines
When the timer expires, the modem disconnects the call.
· If the modem is on the calling party side, the timer starts when the modem starts to dial.
· If the modem is on the called party side, the timer starts when the modem goes off hook.
This command is available on the following user lines:
· TTY lines for the following interfaces:
¡ AM interface
¡ Asynchronous serial interface
¡ Asynchronous/synchronous serial interface operating in asynchronous mode
· AUX line
This command is not available on the console or VTY lines.
To display the user line for an interface, use the display line command.
Examples
# Set the dial-up connection timer to 50 seconds.
<Sysname> system-view
[Sysname] line aux 0
[Sysname-line-aux0] modem answer-timer 50
modem auto-answer
Use modem auto-answer to enable auto-answer mode.
Use undo modem auto-answer to restore the default.
Syntax
modem auto-answer
undo modem auto-answer
Default
Auto-answer mode is disabled. The modem answers a call only when it receives the AT command from the router.
Views
User line view
Predefined user roles
network-admin
Usage guidelines
To ensure correct operation of the modem, set the auto-answer mode on the user line to be the same as the modem.
· Enable auto-answer mode if the modem is in auto-answer mode (the AA LED of the modem lights up). This setting prevents the router from issuing a duplicate answer command after the modem answers a call.
· Disable auto-answer mode if the modem is not in auto-answer mode.
This command is available on the following user lines:
· TTY lines for the following interfaces:
¡ AM interface
¡ Asynchronous serial interface
¡ Asynchronous/synchronous serial interface operating in asynchronous mode
· AUX line
This command is not available on the console or VTY lines.
To display the user line for an interface, use the display line command.
Examples
# Enable auto-answer mode on TTY 1.
<Sysname> system-view
[Sysname] line tty 1
[Sysname-line-tty1] modem auto-answer
Related commands
modem caller-number resolve
modem callback
Use modem callback to enable callback.
Use undo modem callback to disable callback.
Syntax
modem callback
undo modem callback
Default
Callback is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
The callback function enables a modem to disconnect an incoming call and call back the calling party upon request.
Examples
# Enable the callback function.
<Sysname> system-view
[Sysname] modem callback
modem caller-number resolve
Use modem caller-number resolve to enable the modem to obtain the call numbers of calling terminals.
Use undo modem caller-number resolve to disable the modem from obtaining the call number of calling terminals.
Syntax
modem caller-number resolve [ ata-waiting-time time ]
undo modem caller-number resolve
Default
The modem does not obtain caller numbers when it accepts calls from terminals.
Views
User line view
Predefined user roles
network-admin
Parameters
ata-waiting-time time: Specifies the maximum amount of time that the modem waits for a calling terminal to send the call number. The value range for the time argument is 10 to 10000, in milliseconds. The default value is 1000. When this timer expires, the modem does not receive the call number of the terminal. Increase the timer value on a slow link for the router to obtain caller numbers successfully.
Usage guidelines
CAUTION: Executing this command disconnects the modem connection that has been established on the user line. |
This command is for point of sale (POS) terminal access services. It is available only on TTY lines for AM interfaces.
Configure this command if a bank front end processor requires the router to send the call numbers of POS terminals for acknowledgment before it accepts data from the terminals.
For more information about POS terminal access services and caller number sending, see Terminal Access Configuration Guide.
Examples
# Enable the modem to obtain caller numbers on TTY 81, and set the caller number waiting timer to 10 seconds.
<Sysname> system-view
[Sysname] line tty 81
[Sysname-line-tty81] modem caller-number resolve ata-waiting-time 10000
Related commands
modem auto-answer
modem enable
Use modem enable to enable the modem to answer incoming calls, initiate outgoing calls, or both.
Use undo modem enable to disable the modem from answering incoming calls and initiating outgoing calls .
Syntax
modem enable { both | call-in | call-out }
undo modem enable
Default
The modem is disabled from answering incoming calls and initiating outgoing calls.
Views
User line view
Predefined user roles
network-admin
Parameters
both: Enables the modem to answer incoming calls and initiate outgoing calls.
call-in: Enables the modem to answer incoming calls.
call-out: Enables the modem to initiate outgoing calls.
Usage guidelines
CAUTION: Executing this command disconnects the modem connection that has been established on the user line. |
This command is available on the following user lines:
· TTY lines for the following interfaces:
¡ AM interface
¡ Asynchronous serial interface
¡ Asynchronous/synchronous serial interface operating in asynchronous mode
· AUX line
This command is not available on the console or VTY lines.
Examples
# On user line TTY 1, enable the modem to answer incoming calls.
<Sysname> system-view
[Sysname] line tty 1
[Sysname-line-tty1] modem enable call-in
sendat
Use sendat to issue an AT command to a modem.
Syntax
sendat at-string
Views
Interface view
Predefined user roles
network-admin
Parameters
at-string: Specifies an AT command, a case-insensitive string of 1 to 300 characters. The router automatically converts lowercase characters to uppercase when it sends the command to the modem. Enter the AT prefix before all commands except A/ (Repeat Last Command) and +++ (Escape code). For more information about AT commands that begin with AT, see Table 48.
Usage guidelines
CAUTION: This command changes the modem operating state. Incorrect use of this command can cause problems such as dial-up failure. When you use this command, make sure you understand the impact of this command. |
This command is available on the following interfaces:
· Asynchronous serial interface
· Asynchronous/synchronous serial interface in asynchronous mode
· AM interface
· AUX interface
To send AT commands to a modem, you must first place the modem in AT command mode. To confirm that you can send AT commands, enter sendat at. The modem will return OK or 0 if it is ready to accept AT commands.
One sendat command can issue one AT command. To send multiple AT commands to a modem, you must repeat the sendat command.
This command does not verify the validity of AT commands. To verify the AT command execution result, enable modem debugging on the interface. To view the AT commands sent to the modem, issue the E1 command to the modem.
Table 48 describes commonly used AT commands. Support for AT commands varies by modems.
Table 48 AT commands in common use
Command |
Description |
A |
Forces the modem to go off-hook in answer mode. If a call is coming in, the modem will try to answer it without waiting for the ringtone. This command is useful when manual answer mode is used. |
Bn |
Sets the modulation protocol preference. Available options: · B0—Selects the ITU V.22 mode. The transmission speed is 1200 bps. · B1—Selects the Bell 212 mode. The default transmission speed is 1200 bps. · B2/B3—Cancels the ITU V.23 backward channel. · B15—Selects the ITU V.21 mode. The transmission speed is 300 bps. · B16—Selects the 103J mode. The transmission speed is 300 bps. This setting is the default for Compaq Presario 192-VS and Compaq Presario 288-VS modems. |
Dn |
Dials a telephone number. The n argument represents the dial string. In pulse dialing mode, the modem ignores nonnumeric characters. |
En |
Controls echo of commands to the configuration terminal. Available options: · E0—Disables echo of commands to the configuration terminal. · E1—Enables echo of commands to the configuration terminal. This option is the default. |
Hn |
Sets the method to terminate a call. Available options: · H0—Forces modem on-hook to hang up the line (the default). · H1—Forces modem off-hook to answer or dial. |
In |
Displays modem information and results of checksum tests on firmware. Available options: · I0/I3—Displays the default transmission speed and controller firmware version. · I1—Runs a checksum on the ROM and displays the result. · I2—Runs a checksum on the ROM and displays the checksum status: ¡ OK—The checksum is correct. ¡ ERROR—The checksum is incorrect. · I4—Displays the hardware version of the data pump. · I5—Displays the product code, software version, hardware version, and country code. · I9—Displays the country code. |
Ln |
Sets the speaker loudness for fax and data communication. Available options: · L0/L1—Low volume. · L2—Medium volume (the default). · L3—High volume. |
Mn |
Sets the speaker mode for fax and data communication. Available options: · M0—Speaker is always off. · M1—Speaker is on until the carrier is detected. This option is the default. · M2—Speaker is on when the modem is off-hook. · M3—Speaker is on after a dial until the carrier is detected. |
Nn |
Sets the modulation negotiation mode for the modem to establish a connection with a remote modem operating at a different speed. Available options: · N0—Forces the modem to connect at the speed specified in the S37 register and the ATBn command. · N1—Enables the modem to start connecting at the speed specified in the S37 register and ATBn command. However, the speed may drop during the negotiation. This option is the default. |
On |
Forces the modem to return to data mode. Available options: · O0—Returns to data mode. · O1—Initiates an equalizer retrain sequence before returning to data mode. · O3—Negotiates the transmission speed before returning to data mode. After you use the +++ command to place the command in command mode, you can use an ATOn command to change the modem to data mode. |
Qn |
Enables or disables the modem to send result and status codes to the configuration terminal. Available options: · Q0—The modem sends result and status codes. This option is the default. · Q1—The modem does not send result and status codes. |
Sr=n |
Sets the contents of S register r to value n. · Value range for the r argument—0 to 27, 29, 31 to 33, 35, 37, and 89. · Value range for the n argument—0 to 255. |
T |
Sets tone dialing (the default). This command can also be used as a dialing modifier. |
P |
Sets pulse dialing. After you execute this command, the modem performs pulse dialing for all calls until you execute the T command. The P command can also be used as a dialing modifier. |
Vn |
Specifies the result code format. Available options: · V0—Sends numeric result codes. · V1—Sends text-form result codes (the default). |
Examples
# On Async 2/4/0, instruct the modem to dial 169.
<Sysname> system-view
[Sysname] interface async 2/4/0
[Sysname-Async2/4/0] sendat ATD169
# On Serial 2/1/0, instruct the modem to dial 169.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] physical-mode async
[Sysname-Serial2/1/0] sendat ATD169
3G/4G modem management commands
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
4G modems are not supported on the following routers:
· MSR830-6EI-GL
· MSR830-10EI-GL
· MSR830-6HI-GL
· MSR830-10HI-GL
Common management commands
controller cellular
Use controller cellular to enter cellular interface view.
Syntax
controller cellular cellular-number
Views
System view
Predefined user roles
network-admin
Parameters
cellular-number: Specifies a cellular interface by its number.
Examples
# Enter Cellular 2/4/0 interface view.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular 2/4/0]
description
Use description to set a description for a cellular interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description for a cellular interface is in the interface name Interface format, for example, Cellular 2/4/0 Interface.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
text: Sets an interface description, a case-sensitive string of 1 to 255 characters.
Examples
# Set the description to Cellular-intf for Cellular 2/4/0.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] description Cellular-intf
display cellular
Use display cellular to display call connection information for a 3G/4G modem.
Syntax
display cellular [ interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-number: Specifies a cellular interface by its number. If you do not specify a cellular interface, call connection information for all cellular interfaces with 3G/4G modems installed is displayed.
Usage guidelines
The command output might vary by modem manufacturers.
Examples
# Display call connection information for Cellular 2/4/0 (WCDMA network).
<Sysname> display cellular 2/4/0
Cellular2/4/0:
Hardware Information:
Model: E176G
Modem Firmware Version: 11.604.09.00.00
Hardware Version: CD25TCPU
International Mobile Subscriber Identity (IMSI): 460029010431055
International Mobile Equipment Identity (IMEI): 353871020138548
Factory Serial Number (FSN): DK9RAA1871500602
Modem Status: Online
Profile Information:
Profile 1: Active
PDP Type: IPv4, Header Compression: Off
Data Compression: Off
Access Point Name (APN): 001
Packet Session Status: Inactive
Modem Setup Information:
Diagnostics Monitor: Close
Network Information:
Current Service Status: Service available
Current Service: Combined
Packet Service: Attached
Packet Session Status: Inactive
Current Roaming Status: Roaming
Network Selection Mode: Manual
Network Connection Mode: WCDMA precedence
Current Network Connection: HSDPA and HSUPA
Mobile Country Code (MCC): 460
Mobile Network Code (MNC): 00
Location Area Code (LAC): 4318
Cell ID: 25381
Radio Information:
Current Band: ANY
Current RSSI: -51 dBm
Modem Security Information:
PIN Verification: Disabled
PIN Status: Ready
Number of Retries remaining: 3
SIM Status: OK
Table 49 Command output
Field |
Description |
Model |
Modem name. |
International Mobile Subscriber Identity (IMSI) |
IMSI string of the SIM card. |
International Mobile Equipment Identity (IMEI) |
IMEI serial number of the modem. |
Factory Serial Number (FSN) |
FSN of the modem. |
Modem Status |
Status of the modem: · Online—The modem is powered on. · Offline—The modem is powered off or in low power mode. The cellular interface is not available. |
Profile Information |
Profile settings for the modem. |
Profile 1 |
PDP status of the modem: · Active—The profile is already configured. · Undefined—The profile is not configured. |
PDP Type |
PDP type, displayed only when Profile 1 is Active: · IPv4. · IPv6. · PPP (transparent transmission). |
Header Compression |
PDP header compression status: · On. · Off. |
Data Compression |
PDP data compression status: · On. · Off. |
Packet Session Status |
PDP status: · Active—The modem is transmitting data through PPP. · Inactive—The modem is physically down. |
Diagnostics Monitor |
Diagnostic and monitoring (DM) status: · Open—DM is enabled. · Close—DM is disabled. |
Current Service Status |
Service status of the modem: · Service available—The modem is providing services correctly. · Emergency—The modem is providing limited services. The cellular interface is not available. · No service—The modem cannot provide services. The cellular interface is not available. · Low power—The modem is in low power mode. The cellular interface is not available. |
Current Service |
Current service type: · Circuit-switched—For the CS domain only. · Packet-switched—For the PS domain only. · Combined—For both the CS and PS domains. · Invalid—Invalid service. |
Packet Service |
PS domain attach/detach status of the modem: · Detached—The cellular interface is not available. · Attached—The cellular interface is available. |
Current Roaming Status |
Roaming status: · Roaming. · Home. |
Network Selection Mode |
Network selection mode: · Manual. · Automatic. |
Network Connection Mode |
Network connection mode: · WCDMA only—Connected to the WCDMA network only. · WCDMA precedence—Connected to the WCDMA network with preference. · GSM only—Connected to the GSM network only. · GSM precedence—Connected to the GSM network with preference. |
Current Network Connection |
Current network: · No Service. · GSM. · GPRS. · EDGE. · WCDMA. · HSDPA. · HSUPA. · HSDPA and HSUPA. · HSPA+. · Unknown. |
Mobile Country Code (MCC) |
The MCC is displayed if the modem has found a mobile network. |
Mobile Network Code (MNC) |
The MNC is displayed if the modem is successfully registered with a mobile network. |
Location Area Code (LAC) |
The LAC is displayed if the modem is successfully registered with a mobile network. |
Cell ID |
The Cell ID is displayed if the modem is successfully registered with a mobile network. |
Current Band |
Current band selection mode: · GSM. · WCDMA. · ANY. · AUTO. |
Current RSSI |
Current RSSI: · An RSSI value in the range of –110 dBm to –51 dBm. · Unknown—No signal. The cellular interface is unavailable. |
PIN Verification |
PIN authentication status: · Disabled. · Enabled. |
PIN Status |
PIN status: · Ready—The SIM card is ready. · PIN Requirement—Requires you to execute the pin verify command to enter the PIN for PIN verification. · PUK Requirement—Requires you to execute the pin unlock command to unlock the SIM or UIM card. |
Number of Retries remaining |
Remaining retries available for entering the PIN or PUK. |
SIM Status |
SIM card status: · OK—The SIM card is normal. · Network Reject—The SIM card is denied access to the network. The cellular interface is not available. · Not Insert—The SIM card is absent. The cellular interface is not available. |
# Display call connection information for Cellular 2/4/0 (TD-SCDMA network).
<Sysname> display cellular 2/4/0
Cellular2/4/0:
Hardware Information:
Model: ET128
Modem Firmware Version: 11.101.01.08.00
Hardware Version: CS31TCPU
International Mobile Subscriber Identity (IMSI): 460079011105842
International Mobile Equipment Identity (IMEI): 860039002369111
Factory Serial Number (FSN): GQ4CAB1942911350
Modem Status: Online
Profile Information:
Profile 1: Active
PDP Type: IPv4
Header Compression: Off
Data Compression: Off
Access Point Name (APN): cmnet
Packet Session Status: Active
Network Information:
Current Service Status: Service available
Network Selection Mode: Automatic
Network Connection Mode: TD-SCDMA precedence
Current Network Connection: HSDPA
Mobile Network Name: CHINA MOBILE
Downstream Bandwidth: 2800000 bps
Radio Information:
Current RSSI: -75 dBm
Modem Security Information:
PIN Verification: Disabled
PIN Status: Ready
Number of Retries remaining: 3
SIM Status: OK
Table 50 Command output
Field |
Description |
Model |
Modem name. |
International Mobile Subscriber Identity (IMSI) |
IMSI string of the SIM card. |
International Mobile Equipment Identity (IMEI) |
IMEI serial number of the modem. |
Factory Serial Number (FSN) |
FSN of the modem. |
Modem Status |
Status of the modem: · Online—The modem is powered on. · Offline—The modem is powered off or in low power mode. The cellular interface is not available. |
Profile Information |
Profile settings for the modem. |
Profile 1 |
PDP status of the modem: · Active—The profile is already configured. · Undefined—The profile is not configured. |
PDP Type |
PDP type, displayed only when Profile 1 is Active: · IPv4. · IPv6. · PPP (transparent transmission). |
Header Compression |
PDP header compression status: · On. · Off. |
Data Compression |
PDP data compression status: · On. · Off. |
Packet Session Status |
PDP status: · Active—The modem is transmitting data through PPP. · Inactive—The modem is physically down. |
Current Service Status |
Service status of the modem: · Service available—The modem is providing services correctly. · Emergency—The modem is providing limited services. The cellular interface is not available. · No service—The modem cannot provide services. The cellular interface is not available. · Low power—The modem is in low power mode. The cellular interface is not available. |
Network Selection Mode |
Network selection mode: · Manual. · Automatic. |
Network Connection Mode |
Network connection mode: · WCDMA only—Connected to the WCDMA network only. · WCDMA precedence—Connected to the WCDMA network with preference. · GSM only—Connected to the GSM network only. · GSM precedence—Connected to the GSM network with preference. |
Current Network Connection |
Current network: · No Service. · GSM. · GPRS. · EDGE. · TD-SCDMA. · HSDPA. · Unknown. |
Downstream Bandwidth |
Downstream bandwidth, in bps. |
Radio Information |
Radio communication information. |
Current RSSI |
Current RSSI: · An RSSI value in the range of –110 dBm and –51 dBm. · Unknown—No signal. The cellular interface is unavailable. |
PIN Verification |
PIN authentication status: · Disabled. · Enabled. |
PIN Status |
PIN status: · Ready—The SIM card is ready. · PIN Requirement—Requires you to execute the pin verify command to enter the PIN for PIN verification. · PUK Requirement—Requires you to execute the pin unlock command to unlock the SIM or UIM card. |
Number of Retries remaining |
Remaining retries available for entering the PIN or PUK. |
SIM Status |
SIM card status: · OK—The SIM card is normal. · Network Reject—The SIM card is denied access to the network. The cellular interface is not available. · Not Insert—The SIM card is absent. The cellular interface is not available. |
# Display call connection information for Cellular 2/4/0 (CDMA network).
<Sysname> display cellular 2/4/0
Cellular2/4/0:
Hardware Information:
Model: EC169
Manufacturer: HUAWEI TECHNOLOGIES CO.
Modem Firmware Version: 11.002.03.01.45
Hardware Version: CE62TCPUVer A
Electronic Serial Number (ESN): c1836f2d
Preferred Roaming List (PRL) Version: 0
International Mobile Subscriber Identity (IMSI): 460036101433925
Modem Status: Online
Network Information:
Current Service Status: Service available
Current Roaming Status: Home
Network Connection Mode: Manual
Current Network Connection: 1xRTT/EVDO HYBRID
Downstream Bandwidth: 3100000 bps
Radio Information:
Current RSSI(1xRTT): -93 dBm
Current RSSI(EVDO): -75 dBm
Current Voltage: 3336 mV
Modem Security Information:
PIN Verification: Disabled
PIN Status: Ready
Number of Retries remaining: 3
UIM Status: OK
Table 51 Command output
Field |
Description |
Model |
Modem name. |
International Mobile Subscriber Identity (IMSI) |
IMSI string of the UIM card. |
Modem Status |
Status of the modem: · Online—The modem is powered on. · Offline—The modem is powered off or in low power mode. The cellular interface is not available. |
Current Service Status |
Service status of the modem: · Service available—The modem is providing services correctly. · Emergency—The modem is providing limited services. The cellular interface is not available. · No service—The modem cannot provide services. The cellular interface is not available. · Low power—The modem is in low power mode. The cellular interface is not available. |
Current Roaming Status |
Roaming status: · Roaming. · Home. |
Network Selection Mode |
Network selection mode · Manual. · Automatic. |
Current Network Connection |
Current network: · No Service. · 1xRTT/EVDO HYBRID. · EVDO. · 1xRTT. · Unknown. |
Downstream Bandwidth |
Downstream bandwidth, in bps. |
Radio Information |
Radio communication information. |
Current RSSI (1xRTT) |
Current RSSI of 1xRTT: · An RSSI value in the range of –125 dBm to –75 dBm. · Unknown—No signal. |
Current RSSI (EVDO) |
Current RSSI of EVDO: · An RSSI value in the ranges of –120 dBm to –60 dBm. · Unknown—No signal. |
Current Voltage |
Current voltage of the UIM card, in mV. |
PIN Verification |
PIN authentication status: · Disabled. · Enabled. |
PIN Status |
PIN status: · Ready—The UIM card is ready. · PIN Requirement—Requires you to execute the pin verify command to enter the PIN for PIN verification. · PUK Requirement—Requires you to execute the pin unlock command to unlock the SIM or UIM card. |
Number of Retries remaining |
Remaining retries available for entering the PIN or PUK. |
UIM Status |
UIM card status: · OK—The UIM card is normal. · Network Reject—The UIM card is denied access to the network. The cellular interface is not available. · Not Insert—The UIM card is absent. The cellular interface is not available. |
# Display the call connection information for Cellular 0/0 (LTE network).
<Sysname> display cellular 0/0
Cellular0/0:
Hardware Information:
Model: MC7750
Manufacturer: Sierra Wireless, Incorporated
Modem Firmware Version: SWI9600M_03.05.10.06
Hardware Version: 10
International Mobile Equipment Identity (IMEI): 990000560327506
Modem Status: Online
Profile Information:
Profile index: 1
PDP Type: IPv4
Header Compression: Off
Data Compression: Off
Access Point Name (APN): vzwinternet
Network Information:
Current Service Status: Service available
Current Roaming Status: Roaming
Current Data Bearer Technology: Unknown
Network Selection Mode: Manual
Mobile Country Code (MCC): 460
Mobile Network Code (MNC): 00
Location Area Code (LAC): 4318
Cell ID: 25381
Radio Information:
Technology Preference: LTE only
Technology Selected: LTE
LTE related info:
Current RSSI: -79 dBm
Current RSRQ: -9 dB
Current RSRP: -106 dBm
Current SNR: 5 dB
Tx Power: -3276 dBm
Modem Security Information:
PIN Verification: Disabled
PIN Status: Ready
SIM Status: OK
ICCID: 89860113811003195000
Table 52 Command output
Field |
Description |
Model |
Modem name. |
International Mobile Equipment Identity (IMEI) |
IMEI serial number of the modem. |
Modem Status |
Status of the modem: · Online—The modem is powered on. · Offline—The modem is powered off or in lower power mode. The cellular interface is unavailable. |
Profile Information |
Profile settings for the 4G modem. |
Index of the profile for modem. |
|
PDP Type |
PDP type, displayed only when Profile 1 is Active: · IPv4. · IPv6. · PPP (transparent transmission). |
Header Compression |
PDP header compression status · On. · Off. |
Data Compression |
PDP data compression status: · On. · Off. |
Current Service Status |
Service status of the modem: · Limited—The modem is not in the coverage of the selected network. The cellular interface is not available. · Service available—The modem is providing services correctly. · Emergency—The modem is providing limited services. The cellular interface is not available. · No service—The modem cannot provide services. The cellular interface is not available. · Low power—The modem is in low power mode. The cellular interface is not available. |
Current Roaming Status |
Roaming status: · Roaming. · Home. |
Current data carrier technology: · CDMA2000 1X. · CDMA2000 HRPD (1xEV-DO RevA). · Unknown. |
|
Network Selection Mode |
Network selection mode · Manual. · Automatic. |
Mobile Country Code (MCC) |
The MCC is displayed if the modem has found the network. |
Mobile Network Code (MNC) |
The MNC is displayed if the modem is successfully registered with a mobile network. |
Location Area Code (LAC) |
The LAC is displayed if the modem is successfully registered with a mobile network. |
Cell ID |
The Cell ID is displayed if the modem is successfully registered with a mobile network. |
Radio Information |
Radio communication information. |
Technology Preference |
Network connecting preference: · AUTO—Connects to a network automatically. · GSM only—Connects to a GSM network only. · GSM precedence—Connects to a GSM network with preference. · WCDMA only—Connects to a WCDMA network only. · WCDMA precedence—Connects to a WCDMA network with preference. · TD-SCDMA only—Connects to a TD-SCDMA network only. · TD-SCDMA precedence—Connects to a TD-SCDMA network with preference. · EVDO—Connects to a CDMA-EVDO network only. · 1x RTT—Connects to a CDMA-1x RTT network only. · 1xRTT/EVDO HYBRID—Connects to the CDMA-EVDO and CDMA-1x RTT hybrid networks only. · LTE only—Connects to an LTE network only. |
Current network: · GSM—Has connected to a GSM network. · WCDMA—Has connected to a WCDMA network. · TD-SCDMA—Has connected to a TD-SCDMA network. · EVDO—Has connected to a CDMA-EVDO network. · 1Xrtt—Has connected to a CDMA-1x RTT network. · 1xRTT/EVDO HYBRID—Has connected to the CDMA-EVDO and CDMA-1x RTT networks. · LTE—Has connected to an LTE network. |
|
Information about the LTE network. |
|
Current RSSI |
Current RSSI: · An RSSI value in the range of –110 dBm and –51 dBm. · Unknown—No signal. The cellular interface is unavailable. |
Reference Signal Received Quality. |
|
Reference Signal Receiving Power. |
|
Signal to noise ratio. |
|
Transmitting power. |
|
Information about modem security. |
|
PIN Verification |
PIN authentication status: · Disabled. · Enabled. · Unknown. |
PIN Status |
PIN status: · Ready—The SIM card is ready. · PIN Requirement—Requires you to execute the pin verify command to enter the PIN for PIN verification. · PUK Requirement—Requires you to execute the pin unlock command to unlock the SIM or UIM card. |
SIM Status |
SIM card status: · OK—The SIM card is normal. · Network Reject—The SIM card is denied access to the network. The cellular interface is not available. · Not Insert—The SIM card is absent. The cellular interface is not available. · Not Initialized—The SIM card status cannot be identified. |
ICCID |
ID of the SIM card, displayed only when the SIM card status is OK. |
Related commands
mode
pin modify
pin unlock
pin verification enable
pin verify
plmn select
profile create
display controller cellular
Use display controller cellular to display information about a cellular interface.
Syntax
display controller [ cellular [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-number: Specifies a cellular interface by its number.
Usage guidelines
If you do not specify the cellular keyword, the command displays information about all interfaces of the device.
If you specify the cellular keyword but not specify the interface-number argument, the command displays information about existing cellular interfaces.
Hot swapping a USB 3G/4G modem clears the cellular interface statistics.
Examples
# Display information about Cellular 2/4/0.
<Sysname> display controller cellular 2/4/0
Cellular2/4/0
Current state: UP
Description: Cellular2/4/0 Interface
Modem status: Present
DM port status: Disabled
Capability:
1 Control channel, 1 PPP channel
Control channel 0 traffic statistics:
TX: 0 packets, 0 errors
RX: 0 packets, 0 errors
PPP channel 0 traffic statistics:
TX: 0 packets, 0 errors
RX: 0 packets, 0 errors
Table 53 Command output
Field |
Description |
Cellular2/4/0 Current state |
Status of the interface: · DOWN(Administratively)—The interface has been administratively shut down by using the shutdown command. · DOWN—The interface is administratively up but its physical state is down, possibly because of a connection or link failure. · UP—The administrative and physical states of the interface are both up. |
Description |
Description of the interface. |
Modem status |
Status of the USB 3G/4G modem: · Present—The modem is present. · Absent—The modem is absent. |
DM port status |
DM status: · Enabled. · Disabled. |
Capability: 1 Control channel, 1 PPP channel |
Type and number of channels the cellular interface supports: · 1 Control channel—Supports one control channel. · 1 PPP channel—Supports one asynchronous serial subchannel. · 1 ETH channel—Supports one Ethernet subchannel. |
Control channel 0 traffic statistics: TX: 0 packets, 0 errors RX: 0 packets, 0 errors |
Control channel statistics: · TX: 0 packets, 0 errors—Number of packets and number of error packets sent through the control channel. · RX: 0 packets, 0 errors—Number of packets and number of error packets received through the control channel. |
PPP channel 0 traffic statistics TX: 0 packets, 0 errors RX: 0 packets, 0 errors |
PPP channel statistics: · TX: 0 packets, 0 errors—Number of packets and number of error packets sent through the PPP channel. · RX: 0 packets, 0 errors—Number of packets and number of error packets received through the PPP channel. |
ETH channel 0 traffic statistics TX: 0 packets, 0 errors RX: 0 packets, 0 errors |
Ethernet channel statistics: · TX: 0 packets, 0 errors—Number of packets and number of error packets sent through the Ethernet channel. · RX: 0 packets, 0 errors—Number of packets and number of error packets received through the Ethernet channel. |
Related commands
reset counters controller cellular
dm-port open
Use dm-port open to enable diagnostic and monitoring (DM) on a 3G/4G modem.
Use undo dm-port open to disable DM on a 3G/4G modem.
Syntax
dm-port open
undo dm-port open
Default
The default setting for this command depends on the modem model.
Views
Cellular interface view
Predefined user roles
network-admin
Usage guidelines
This command is supported only on SIC-3G modems and 4G modems.
Enabling DM on a 3G/4G modem allows third-party debugging tools to diagnose and monitor the 3G/4G modem through cellular interface debugging output.
For more information about DM, see related 3G/4G modem user manuals.
Examples
# Enable DM on a 3G/4G modem.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] dm-port open
mode
Use mode to specify network services for a 3G/4G modem.
Syntax
Default
The default setting for this command depends on the modem model.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
1xrtt: Connects to a CDMA-1x RTT network only.
auto: Connects to a network automatically.
evdo: Connects to a CDMA-EVDO network only.
gsm: Connects to a GSM network only.
gsm-preference: Connects to a GSM network with preference.
hybrid: Connects to the CDMA-EVDO and CDMA-1xRTT networks only.
lte: Connects to an LTE network only.
td: Connects to a TD-SCDMA network only.
td-preference: Connects to a TD-SCDMA network with preference.
wcdma: Connects to a WCDMA network only.
wcdma-preference: Connects to a WCDMA network with preference.
Usage guidelines
The available parameters depend on the modem model.
Examples
# Specify the LTE service for the 4G modem.
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] mode lte
modem reboot
Use modem reboot to reboot a 3G/4G modem.
Syntax
modem reboot
Views
Cellular interface view
Predefined user roles
network-admin
Usage guidelines
A 3G/4G modem module can automatically detect running errors and reboot. If the 3G/4G modem fails to reboot by itself, you can use this command to reboot it.
Examples
# Manually reboot the 3G/4G modem.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] modem reboot
modem response
Use modem response to set a 3G/4G modem response timer and a consecutive response failure threshold for auto recovery.
Use undo modem response to restore the default.
Syntax
modem response timer time auto-recovery threshold
undo modem response
Default
The response timer is 10 seconds and the consecutive response failure threshold is 3.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
timer time: Sets the response timer, in the range of 1 to 300, in seconds.
auto-recovery threshold: Specifies the consecutive response failure threshold for auto recovery. The value range for the threshold argument is 0 to 10. To disable auto recovery, set the value to 0.
Usage guidelines
A 3G/4G modem might malfunction in an unstable 3G/4G network or when the application environment changes. During a malfunction, the modem cannot respond to the device's requests or configuration commands. If the device does not receive any responses from the 3G/4G modem within the timer, a response failure occurs. When the number of consecutive response failures reaches the threshold, the device restarts the 3G/4G modem automatically. This releases the user from manually rebooting the modem.
The device does not restart the 3G/4G modem when the 3G/4G modem has not made a successful dialup since the last restart. This restriction avoids repeated restarts of the 3G/4G modem when there are configuration errors.
Examples
# Set the response timer to 20 seconds and the consecutive response failure threshold for auto recovery to 4.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] modem response timer 20 auto-recovery 4
pin modify
Use pin modify to modify the PIN of a SIM/UIM card.
Syntax
pin modify current-pin new-pin
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
current-pin: Specifies the current PIN of the SIM/UIM card, a string of 4 to 8 digits.
new-pin: Specifies the new PIN, a string of 4 to 8 digits.
Usage guidelines
The new PIN is saved on the SIM/UIM card.
If PIN verification is enabled, execute the pin verify command to save the new PIN on the device after the PIN is modified.
Failure to modify the PIN in a maximum number of attempts locks the SIM/UIM card. The maximum number of attempts depend on the 3G/4G modem model. To unlock the card, execute the pin unlock command.
For some 3G/4G modems, you can modify their PINs only when the 3G/4G modems pass the PIN authentication.
Examples
# Modify the PIN of a SIM/UIM card.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] pin modify 1234 4321
PIN will be changed to “4321”. Continue? [Y/N]:y
PIN has been changed successfully.
Related commands
pin unlock
pin verification enable
pin verify
pin unlock
Use pin unlock to specify the Personal Unlock Code (PUK) to unlock a SIM/UIM card.
Syntax
pin unlock puk new-pin
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
puk: Specifies the PUK of the SIM/UIM card, a string of 4 to 8 digits. The PUK code of a SIM/UIM card is provided by the network service provider.
new-pin: Specifies the new PIN, a string of 4 to 8 digits.
Usage guidelines
A SIM/UIM card will be locked in the following circumstances:
· Consecutive PIN modification failures.
· Consecutive failures for enabling or disabling PIN authentication.
· Consecutive PIN authentication failures.
If the SIM/UIM card is locked, the 3G modem cannot be used. To unlock the card, you can use the pin unlock command. The new PIN is saved on the SIM/UIM card.
If PIN verification is enabled, use the pin verify command to save the new PIN on the device after the SIM/UIM card is unlocked.
If you consecutively fail to unlock a card by using the PUK, the card will be locked permanently. To unlock a permanently locked card, contact the service provider of the card.
Examples
# Use the PUK to unlock a SIM/UIM card.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] pin unlock 87654321 1234
PIN will be unlocked and changed to “1234”. Continue? [Y/N]:y
PIN has been unlocked and changed successfully.
Related commands
pin modify
pin verification enable
pin verification enable
Use pin verification enable to enable PIN verification for a 3G/4G modem.
Use undo pin verification enable to disable PIN verification for a 3G/4G modem.
Syntax
pin verification enable [ pin ]
undo pin verification enable [ pin ]
Default
The default setting for this command depends on the modem model.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
pin: Specifies the PIN of the SIM/UIM card, a string of 4 to 8 digits.
Usage guidelines
If PIN verification is enabled, PIN verification is performed after you perform any of the following tasks:
· Install a 3G/4G modem.
· Reboot the device.
· Execute the modem reboot command to reboot a 3G/4G modem.
· Hot swap a USB 3G/4G modem.
· Cold boot the device where a SIC-3G/4G modem is installed.
To perform PIN verification, you also need to execute the pin verify command to save the PIN of the SIM/UIM card on the device. After the PIN is saved on the device, the PIN is used for verification automatically when required.
You might be required to provide the current PIN when you enable or disable PIN verification. This requirement depends on the 3G/4G modem model.
For some 3G/4G modems, you can disable PIN verification only when the 3G/4G modems pass PIN authentication.
Consecutive failures for enabling or disabling PIN verification lock a SIM/UIM card. To unlock the card, execute the pin unlock command.
Examples
# Enable PIN authentication.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] pin verification enable 1234
Related commands
pin unlock
pin verify
pin verify
Use pin verify to specify the PIN of a SIM/UIM card on a 3G/4G modem.
Use undo pin verify to restore the default.
Syntax
pin verify { cipher | simple } string
undo pin verify
Default
No PIN is specified for a SIM/UIM card.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
cipher ciphered-pin: Specifies a PIN in encrypted form.
simple pin: Specifies a PIN in plaintext form. For security purposes, the PIN specified in plaintext form will be stored in encrypted form.
string: Specifies the PIN. Its plaintext form is 4 to 8 digits long. Its encrypted form is a string of 37 to 41 characters.
Usage guidelines
This command saves the PIN of the SIM/UIM card on the device. The PIN is used for verifying the 3G/4G modem when PIN verification is performed. You can execute this command before or after you enable PIN verification.
Consecutive PIN verification failures might lock a SIM/UIM card. To unlock the card, execute the pin unlock command.
Examples
# Specify the plaintext form PIN 1234 for the SIM/UIM card.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] pin verify simple 1234
Related commands
pin unlock
pin verification enable
plmn search
Use plmn search to search for available mobile networks.
Syntax
plmn search
Views
Cellular interface view
Predefined user roles
network-admin
Usage guidelines
Before you use a 3G/4G modem to access a mobile network, use the plmn search command to search a PLMN for available mobile networks. The search takes a few minutes. After the search is complete, the CLI displays the available mobile networks. Some 3G/4G modems automatically access an available network. You can also specify a mobile network for the 3G/4G modem from the available mobile networks.
Examples
# Search for mobile networks on Cellular 2/4/0.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] plmn search
PLMN search done.
Available PLMNs:
PLMN No. MCC MNC Status Type
01 460 00 Current GSM
02 460 00 Available UTRAN
03 460 01 Forbidden GSM
Table 54 Command output
Field |
Description |
PLMN No |
PLMN number. |
MCC |
Mobile Country Code. |
MNC |
Mobile Network Code: · 00, 02, and 07—China Mobile. · 01—China Unicom. · 03—China Telecom. |
Status |
Status of the mobile network: · Current. · Available. · Forbidden. |
Type |
Type of the mobile network. |
Related commands
display cellular
plmn select
plmn select
Use plmn select to configure the mobile network selection mode.
Syntax
plmn select { auto | manual mcc mnc }
Default
The default setting for this command depends on the modem model.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
auto: Specifies the auto selection mode. The 3G modem automatically selects a mobile network.
manual: Specifies the manual selection mode.
mcc: Specifies the mobile country code (MCC) in the range of 0 to 65535.
mnc: Specifies the mobile network code (MNC) in the range of 0 to 65535.
Usage guidelines
For manual selection, you can first use the plmn search command to obtain the MCC and MNC of a mobile network.
Examples
# Manually specify a mobile network.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] plmn select manual 65524 65524
Related commands
display cellular
plmn search
reset counters controller cellular
Use reset counters controller cellular to clear statistics for a cellular interface.
Syntax
reset counters controller cellular [ interface-number ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a cellular interface by its number. If you do not specify this argument, this command clears statistics for all cellular interfaces.
Usage guidelines
To collect traffic statistics on an interface during a period of time, first use the reset counters controller cellular command to clear the existing statistics on the interface.
Examples
# Clear statistics for Cellular 2/4/0.
<Sysname> reset counters controller cellular 2/4/0
Related commands
display controller cellular
rssi
Use rssi to set the RSSI thresholds for a 3G/4G modem.
Use undo rssi to restore the default.
Syntax
rssi { 1xrtt | evdo | gsm | lte } { low lowthreshold | medium mediumthreshold } *
undo rssi { 1xrtt | evdo | gsm | lte } [ low | medium ]
Default
The lower and upper RSSI thresholds for a 3G/4G modem are –150 dBm and 0 dBm, respectively.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
1xrtt: Specifies the 1xRTT mode.
evdo: Specifies the EVDO mode.
gsm: Specifies the GSM mode.
lte: Specifies the LTE mode.
low lowthreshold: Specifies the lower RSSI threshold value in the range of 0 to 150, which represents a lower RSSI threshold in the range of –150 dBm to 0 dBm. The value of lowthreshold cannot be smaller than the value of mediumthreshold because the system automatically adds a negative sign to the RSSI thresholds.
medium mediumthreshold: Specifies the upper RSSI threshold value in the range of 0 to 150, which represents an upper RSSI threshold in the range of –150 dBm to 0 dBm.
Usage guidelines
The device performs the following operations based on the actual RSSI of the 3G/4G modem:
· Sends a trap that indicates high RSSI when the RSSI exceeds the upper threshold.
· Sends a trap that indicates normal RSSI when the RSSI is between the lower threshold and upper threshold (included).
· Sends a trap that indicates low RSSI when the RSSI drops to or below the lower threshold.
· Sends a trap that indicates low RSSI every 10 minutes when the RSSI remains equal to or smaller than the lower threshold.
To view the RSSI change information for a 3G/4G modem, use the display cellular command.
Examples
# Set the lower threshold for a 3G/4G modem in GSM mode to –110 dBm.
<Sysname> system-view
[Sysname] controller cellular 0/0
[Sysname-Cellular0/0] rssi gsm low 110
sendat
Use sendat to issue a configuration directive to a 3G/4G modem.
Syntax
sendat at-string
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
at-string: Specifies a configuration directive string, a string of 1 to 300 characters. This argument can be an AT directive (containing +++, A/, or be any string beginning with AT) or a CNS directive. For more information about AT directives, see the sendat command in Layer 2—WAN Access Command References. Table 55 describes the CNS directive samples.
Table 55 CNS directive description
Directive |
Description |
CNSn |
Controls the CNS heartbeat debugging switch. · n = 00000500000000000000—Enables CNS heartbeat debugging. · n = 00000800000000000000—Disables CNS heartbeat debugging. |
Usage guidelines
The sendat command does not verify the configuration directive. Each time it issues one configuration directive to the 3G/4G modem, lowercase characters are automatically converted to uppercase characters.
One sendat command issues one configuration directive. To issue multiple configuration directives to a modem, you must repeat the sendat command.
Configuration directives might cause malfunction of a 3G/4G modem. When you issue a configuration directive to the modem, make sure you understand the impact on the 3G/4G modem.
Examples
# Issue the ATD169 directive to the 3G/4G modem to call number 169.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] sendat ATD169
# Issue the cns00000500000000000000 directive to the 3G/4G modem to enable CNS heartbeat debugging.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] sendat cns00000500000000000000
shutdown
Use shutdown to shut down a cellular interface.
Use undo shutdown to bring up a cellular interface.
Syntax
shutdown
undo shutdown
Default
The cellular interface is up.
Views
Cellular interface view
Predefined user roles
network-admin
Examples
# Shut down Cellular 2/4/0.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] shutdown
sim backup enable track
Use sim backup enable track to associate 3G/4G link backup with a track entry.
Use undo sim backup enable to restore the default.
Syntax
sim backup enable track entry-number
undo sim backup
Default
3G/4G link backup is not associated with a track entry.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
entry-number: Specifies a track entry by its ID in the range of 1 to 1024.
Usage guidelines
IMPORTANT: This command is supported only on MSR810-LMS/810-LUS routers and routers installed with SIC-4G-CNDE interface modules. |
This command uses a track entry to monitor the status of the primary 3G/4G link. When the track entry state changes from Positive to Negative, the secondary 3G/4G link takes over. For information about track entries, see track configuration in High Availability Configuration Guide.
You can associate only one track entry with a 3G/4G link. If you execute this command multiple times, the most recent configuration takes effect.
The 3G/4G link backup and track entry association takes effect only after the track entry is created.
Examples
# Associate Cellular 1/0 with track entry 1.
<sysname> system
[system] controller cellular 1/0
[system-Cellular1/0] sim backup enable track 1
Related commands
sim switch-back enable
sim switch-to
sim switch-back enable
Use sim switch-back enable to enable automatic switchback to the primary SIM card.
Use undo sim switch-back enable to disable automatic switchback to the primary SIM card.
Syntax
sim switch-back enable [ wait-time time ]
undo sim switch-back enable
Default
Automatic switchback to the primary SIM card is disabled.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
time: Specifies the length of time for using the secondary SIM card. The value is in the range of 1 to 65535, in minutes. The default value is 60. After the time expires, the device automatically switches back to the primary SIM card.
Usage guidelines
IMPORTANT: This command is supported only on MSR810-LMS/810-LUS routers and routers installed with SIC-4G-CNDE interface modules. |
This command allows the device to automatically switch back to the primary SIM card after the specified length of time of using the secondary SIM card. To avoid frequent primary/secondary switchovers, make sure the link of the primary SIM card can recover after the specified length of time.
Examples
# Enable the device to automatically switch back to the primary SIM card after 100 minutes of using the secondary SIM card.
<Sysname> system-view
[Sysname] controller cellular 1/0
[Sysname-Cellular1/0] sim switch-back enable wait-time 100
sim switch-to
Use sim switch-to to specify the primary or secondary SIM card.
Syntax
sim switch-to card-number
Default
The primary SIM card is used.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
card-number: Specifies a SIM card by its slot number. The value is 0 or 1. 0 represents the primary SIM card. 1 represents the secondary SIM card.
Usage guidelines
CAUTION: This command might cause traffic interruption. Be aware of the impact of this command before executing it. |
IMPORTANT: This command is supported only on MSR810-LMS/810-LUS routers and routers installed with SIC-4G-CNDE interface modules. |
On a device that uses dual SIM card, you can execute this command to specify the use of the secondary SIM card when one of the following problems occurs:
· The 3G/4G link signals of the primary SIM card are weak.
· The service provider network that the primary SIM card connects to is unavailable.
· The primary SIM card has failed.
If the problems of the primary SIM card are resolved, you can use this command to specify the use of the primary SIM card.
Examples
# Specify the secondary SIM card for the device.
<Sysname> system-view
[Sysname] controller cellular 1/0
[Sysname-Cellular1/0] sim switch-to 1
trust-imsi
Use trust-imsi to configure a trusted IMSI.
Use undo trust-imsi to remove a trusted IMSI.
Syntax
trust-imsi string-imsi
undo trust-imsi [ string-imsi ]
Default
No trusted IMSI is configured.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
string-imsi: Specifies an IMSI. The string-imsi argument is a case-insensitive string of 1 to 31 characters.
Usage guidelines
For a successful dialup, configure the IMSI of the SIM card as a trusted IMSI.
You can configure a maximum of 16 trusted IMSIs.
Examples
# Configure trusted IMSI hccc123456789 for Cellular 0/0.
<Sysname> system-view
[Sysname] controller cellular 0/0
[Sysname-Cellular0/0] trust-imsi hccc123456789
3G modem-specific management commands
gsm band
Use gsm band to specify a GSM frequency band.
Use undo gsm band to restore the default.
Syntax
gsm band { egsm900 | gsm450 | gsm480 | gsm750 | gsm850 | gsm1800 | gsm1900 | pgsm900 | rsgm900 }
undo gsm band
Default
No GSM band is specified.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
egsm900: Specifies the E-GSM 900 MHz band.
gsm450: Specifies the GSM 450 MHz band.
gsm480: Specifies the GSM 480 MHz band
gsm750: Specifies the GSM 750 MHz band.
gsm850: Specifies the GSM 850 MHz band.
gsm1800: Specifies the GSM 1800 MHz band.
gsm1900: Specifies the GSM 1900 MHz band.
pgsm900: Specifies the P-GSM 900 MHz band.
rgsm900: Specifies the GSM-R 900 MHz band.
Usage guidelines
IMPORTANT: This command is supported only by Sierra MC7354 (ATT version) and MC7304 4G modules. |
Multiple frequency bands are available for accessing the GSM network. When the network environment changes, the 3G/4G modem might change the working band automatically to adapt to the change. To avoid link instability caused by frequency changes, you can specify a GSM frequency band for the 3G/4G modem.
Examples
# Specify the GSM 1800 MHz band for the 3G/4G modem.
<Sysname> system-view
[Sysname] controller cellular 0/0
[Sysname-Cellular0/0] gsm band gsm1800
Related commands
lte band
wcdma band
profile create
Use profile create to create a profile for a 3G modem.
Syntax
profile create profile-number { dynamic | static apn } authentication-mode { none | { chap | pap } user username [ password password ] }
Default
The default setting for this command depends on the 3G modem model.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
profile-number: Specifies a profile number. The value range varies by modem model.
dynamic: Uses an access point automatically assigned by the service provider.
static apn: Specifies the access point provided by the service provider. It is a string of 1 to 100 characters. Whether the string is case-sensitive varies by service provider.
authentication-mode: Specifies the authentication mode, which can be none, pap, or chap.
none: Performs no authentication.
chap: Specifies CHAP authentication.
pap: Specifies PAP authentication.
user username: Specifies the username provided by the service provider. It is a case-sensitive string of 1 to 32 characters.
password password: Specifies the authentication password provided by the service provider. It is a case-sensitive string of 1 to 32 characters.
Usage guidelines
If you specify chap or pap, make sure the authentication settings are identical to those assigned by the service provider.
Examples
# Create a profile for Cellular 2/4/0. Specify the profile number as 1 and the access point name as cmnet, and specify the PAP authentication mode.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] profile create 1 static cmnet authentication-mode pap user abc password abc
Related commands
display cellular
profile delete
profile delete
Use profile delete to delete a profile for a 3G modem.
Syntax
profile delete profile-number
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
profile-number: Specifies a profile by its number. The value range varies by modem model.
Examples
# Delete profile 1 for Cellular 2/4/0.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] profile delete 1
Related commands
display cellular
profile create
profile main
Use profile main to specify the primary and backup profiles for 3G modem dialup.
Use undo profile main to restore the default.
Syntax
profile main main-profile-number backup backup-profile-number
undo profile main
Default
Profile 1 is used for 3G modem dialup.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
main main-profile-number: Specifies the primary profile by its number. The value range varies by the modem model.
backup backup-profile-number: Specifies the backup profile by its number. The value range varies by modem model.
Usage guidelines
The primary profile always has priority over the backup profile. For each dialup connection establishment, the 3G modem uses the backup profile only when it has failed to dial up using the primary profile.
You must configure the same user name and password for the primary and backup profiles.
This command takes effect only on dialup connections initiated after the command is configured. It does not take effect on a dialup connection that has been established.
Examples
# Specify the profiles numbered 1 and 2 as the primary and backup profiles, respectively.
<sysname>system-view
[sysname]interface Cellular 2/4/0
[sysname-Cellular2/4/0]profile main 1 backup 2
serial-set
Use serial-set to channelize a cellular interface into a synchronous/asynchronous serial interface.
Use undo serial-set to delete a synchronous/asynchronous serial interface channelized from a cellular interface.
Syntax
serial-set set-number
undo serial-set set-number
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
set-number: Specifies the serial interface number.
Usage guidelines
The command names the serial interface as serial cellular-number:set-number.
Examples
# Channelize Cellular 2/4/0 into a serial interface.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] serial-set 0
wcdma band
Use wcdma band to specify a WCDMA frequency band.
Use undo wcdma band to restore the default.
Syntax
wcdma band { wcdma800 | wcdma850 | wcdma900 | wcdma1700ip | wcdma1700us | wcdma1800 | wcdma1900 | wcdma2100 | wcdma2600 }
undo wcdma band
Default
No WCDMA band is specified.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
wcdma800: Specifies the WCDMA 800 MHz band.
wcdma850: Specifies the WCDMA 850 MHz band.
wcdma900: Specifies the WCDMA 900 MHz band.
wcdma1700jp: Specifies the Japan WCDMA 1700 MHz band.
wcdma1700us: Specifies the US WCDMA 1700 MHz band.
wcdma1800: Specifies the WCDMA 1800 MHz band.
wcdma1900: Specifies the WCDMA 1900 MHz band.
wcdma2100: Specifies the WCDMA 2100 MHz band.
wcdma2600: Specifies the WCDMA 2600 MHz band.
Usage guidelines
IMPORTANT: This command is supported only by Sierra MC7354 (ATT version) and MC7304 4G modules. |
Multiple frequency bands are available for accessing the WCDMA network. When the network environment changes, the 3G/4G modem might change the working band automatically to adapt to the change. To avoid link instability caused by frequency changes, you can specify a WCDMA frequency band for the 3G/4G modem.
Examples
# Specify the WCDMA 1700 MHz band for the 3G/4G modem.
<Sysname> system-view
[Sysname] controller cellular 0/0
[Sysname-Cellular0/0] wcdma band wcdma1700
Related commands
gsm band
lte band
4G modem-specific management commands
apn
Use apn to create an access point name (APN) for a 4G modem.
Use undo apn to remove an APN.
Syntax
apn { dynamic | static apn }
undo apn
Default
No APN is specified for a 4G modem.
Views
4G modem profile view
Predefined user roles
network-admin
Parameters
dynamic: Uses an APN automatically assigned by the service provider.
static apn: Specifies the APN provided by the service provider. The apn argument is a string of 1 to 100 characters. Whether the string is case-sensitive varies by service providers.
Examples
# Specify APN apn1 for 4G modem profile test.
<Sysname> system-view
[Sysname] apn-profile test
[Sysname-apn-profile-test] apn static apn1
Related commands
apn-profile
apn-profile
Use apn-profile to create a 4G modem profile.
Use undo apn-profile to remove a 4G modem profile.
Syntax
apn-profile profile-name
undo apn-profile profile-name
Default
No 4G modem profiles exist.
Views
System view
Predefined user roles
network-admin
Parameters
profile-name: Specifies a 4G modem profile name.
Usage guidelines
A 4G modem profile takes effect only when you associate the profile with a 4G interface. To remove a 4G modem profile, you must first remove the association between the profile and the 4G interface.
Examples
# Create 4G modem profile test.
<Sysname> system-view
[Sysname] apn-profile test
Related commands
apn-profile apply
apn-profile apply
Use apn-profile apply to specify a 4G modem profile for an interface.
Use undo apn-profile apply to restore the default.
Syntax
apn-profile apply profile-name [ backup profile-name ]
undo apn-profile apply
Default
No 4G modem profiles are specified for an interface.
Views
Eth-channel interface view
Predefined user roles
network-admin
Parameters
profile-name: Specifies a primary 4G modem profile name.
backup profile-name: Specifies a backup 4G modem profile name.
Usage guidelines
After you specify a 4G modem profile for a 4G modem, the 4G modem uses the settings in the profile to negotiate with the service provider's device.
The primary profile always has priority over the backup profile. For each dialup connection establishment, the 4G modem uses the backup profile only when it has failed to dial up using the primary profile.
This command takes effect only on dialup connections initiated after the command is configured. It does not take effect on a dialup connection that has been established.
Examples
# Specify primary 4G modem profile test and backup 4G modem profile bktest for Eth-channel interface 2/4/0:0.
<Sysname> system-view
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0] apn-profile apply test backup bktest
Related commands
apn-profile
attach-format imsi-sn split
Use attach-format imsi-sn split to specify a separator for the IMSI/SN binding authentication information.
Use undo attach-format imsi-sn split to restore the default.
Syntax
attach-format imsi-sn split splitchart
undo attach-format imsi-sn split
Default
No separator is specified for the IMSI/SN binding authentication information.
Views
4G modem profile view
Predefined user roles
network-admin
Parameters
split splitchart: Specifies a separator. It can be a letter, a digit, or a sign such as a percent sign (%) or a pound sign (#).
Usage guidelines
If IMSI/SN binding authentication is enabled, the IMSI/SN information is included in the authentication information in addition to the username. You need to configure a separator to separate different types of information. For example, if you specify the separator as #, the authentication information will be sent in the imsiinfo#sninfo#username format.
Examples
# Configure the pound sign (#) as the separator for the IMSI/SN binding authentication information.
<Sysname> system-view
[Sysname] apn-profile test
[Sysname-apn-profile-test] attach-format imsi-sn split #
Related commands
apn-profile
authentication-mode
Use authentication-mode to specify an authentication mode.
Use undo authentication-mode to restore the default.
Syntax
authentication-mode { pap | chap| pap-chap } user user-name password { cipher | simple } string
undo authentication-mode
Default
No authentication mode is specified.
Views
4G modem profile view
Predefined user roles
network-admin
Parameters
chap: Specifies CHAP authentication.
pap: Specifies PAP authentication.
pap-chap: Specifies CHAP or PAP authentication.
user username: Specifies the username for authentication, a case-sensitive string of 1 to 80 characters.
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the password. Its plaintext form is a case-sensitive string of 1 to 32 characters. Its encrypted form is a case-sensitive string of 1 to 73 characters
Examples
# Specify the CHAP authentication mode for 4G modem profile test. Specify the username as user1 and the password as 123456.
<Sysname> system-view
[Sysname] apn-profile test
[Sysname-apn-profile-test] authentication-mode chap user user1 password simple 123456
Related commands
apn-profile
bandwidth
Use bandwidth to configure the expected bandwidth for an Eth-channel 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
Eth-channel interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth for an interface affects the link costs in OSPF, OSPFv3, and IS-IS. For more information, see Layer 3—IP Routing Configuration Guide.
Examples
# Set the expected bandwidth for Eth-channel 2/4/0:0 to 1000 kbps.
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0] bandwidth 1000
default
Use default to restore the default settings for an Eth-channel interface.
Syntax
default
Views
Eth-channel 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 and system restrictions. Use the display this command in interface view to identify these commands. Then, use their undo forms or follow the command reference to individually restore their default settings. If your restoration attempt fails, follow the error message instructions to resolve the problem.
Examples
# Restore the default settings for Eth-channel 2/4/0:0.
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0] default
description
Use description to set a description for an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description for an interface is in the interface name Interface format, for example, Echannel 2/4/0:0 Interface.
Views
Eth-channel interface view
Predefined user roles
network-admin
Parameters
text: Sets an interface description, a case-sensitive string of 1 to 255 characters.
Usage guidelines
Configure a description for an interface for easy identification and management purposes.
You can use the display interface command to view the description for an interface.
Examples
# Set the description for Eth-channel 2/4/0:0 to Echannel-interface.
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0] description Echannel-interface
display interface eth-channel
Use display interface eth-channel to display information about the specified or all Eth-channel interfaces.
Syntax
display interface [ eth-channel [ channel-id ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
channel-id: Specifies an Eth-channel interface by its number.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays information about interfaces in down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Usage guidelines
If the eth-channel keyword is not specified, the command displays information about all interfaces on the device.
If the eth-channel keyword is specified but the channel-id argument is not specified, the command displays information about all Eth-channel interfaces.
Examples
# Display detailed information about Eth-channel 2/4/0:0.
<Sysname> display interface eth-channel 2/4/0:0
Echannel2/4/0:0
Current state: DOWN
Line protocol state: DOWN
Description: Echannel2/4/0:0 Interface
Bandwidth: 100000kbps
Maximum Transmit Unit: 1500
Internet protocol processing: disabled
IP Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 000c-2963-b75d
IPv6 Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 000c-2963-b75d
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last link flapping: Never
Last clearing of counters: Never
Last 300 seconds input rate 0.00 bytes/sec, 0.00 packets/sec
Last 300 seconds output rate 0.00 bytes/sec, 0.00 packets/sec
Input: 0 packets, 0 bytes, 0 buffers
Output:0 packets, 0 bytes
# Display brief information about Eth-channel 2/4/0:0.
<Sysname> display interface eth-channel 2/4/0:0 brief
Brief information on interface(s) under route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Main IP Description
Echannel2/4/0:0 UP UP(s) 192.168.80.239
# Display information about all Eth-channel interfaces in down state and the causes.
<Sysname> display interface eth-channel brief down
Brief information on interface(s) under route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
Echannel2/4/0:0 ADM Administratively
Table 56 Command output
Field |
Description |
Current state |
Physical and administrative state of the Eth-channel interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up but physically down because no physical link is present or the link has failed. · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer protocol state of the interface: · UP. · DOWN. · UP(spoofing)—The data link layer protocol state of the interface is up but the link is an on-demand link or not present at all. |
Description |
Description for the interface. |
Bandwidth |
Expected bandwidth of the interface. |
Maximum Transmit Unit |
MTU of the interface. |
Internet protocol processing: disabled |
IP packet processing is disabled. |
Primary IP address of the interface, which is assigned automatically by the service provider. |
|
IP Packet Frame Type |
IPv4 packet framing format. |
Hardware Address |
MAC address of the interface. |
IPv6 Packet Frame Type |
IPv6 packet framing format. |
Packet statistics for urgent queuing in the output queue of the interface: · Size—Current number of packets in the queue. · Length—Maximum number of packets that can stay in the queue. · Discards—Number of dropped packets. |
|
Packet statistics for protocol queuing in the output queue of the interface: · Size—Current number of packets in the queue. · Length—Maximum number of packets that can stay in the queue. · Discards—Number of dropped packets. |
|
Packet statistics for FIFO queuing in the output queue of the interface: · Size—Current number of packets in the queue. · Length—Maximum number of packets that can stay in the queue. · Discards—Number of dropped packets. |
|
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
|
Last clearing of counters |
Time when statistics on the logical interface were last cleared by using the reset counters interface command. If the statistics of the interface have never been cleared by using the reset counters interface command since the device started, this field displays Never. |
Average input rate during the last 300 seconds: · bytes/sec—Average number of received bytes per second. · bits/sec—Average number of received bits per second. · packets/sec—Average number of received packets per second. |
|
Average output rate over the last 300 seconds: · bytes/sec—Average number of sent bytes per second. · bits/sec—Average number of sent bits per second. · packets/sec—Average number of sent packets per second. |
|
Incoming packet statistics: · 0 packets—Packet number. · 0 bytes—Packet size in bytes. · 0 buffers—Number of buffered units. |
|
Output: 0 packets, 0 bytes |
Outgoing packet statistics: · 0 packets—Packet number. · 0 bytes—Packet size in bytes. |
Brief information about Layer 3 interfaces. |
|
Link: ADM - administratively down; Stby - standby |
Explains the Link field values: · ADM—The interface has been shut down by the network administrator. To recover its physical layer state, execute the undo shutdown command. · Stby—The interface is a standby interface. To view the primary interface information, execute the display interface-backup state command. |
Protocol: (s) - spoofing |
Explains the Protocol field value. (s) represents spoofing. If the data link layer protocol of an interface is up but its link is an on-demand link or not present at all, the Protocol field displays UP(s). |
Interface |
Interface name. |
Link |
Physical state of the interface: · UP—The interface is up. · DOWN—The interface is physically down. · ADM—The interface has been administratively shut down. To recover its physical state, execute the undo shutdown command. · Stby—The interface is a standby interface. |
Protocol |
Data link layer protocol state of the interface: · UP. · DOWN. · UP(s)—The data link layer protocol state of the interface is up but the link is an on-demand link or not present at all. |
Main IP |
Main IP address of the interface. |
Interface description configured by using the description command. If the description keyword is not specified in the display interface brief command, the Description field displays the first 27 characters of the interface description. If the description keyword is specified in the display interface brief command, this field displays the complete interface description. |
|
Cause of the interface down event. If the interface has been shut down by using the shutdown command, this field displays Administratively. To restore the physical state of the interface, execute the undo shutdown command. |
eth-channel
Use eth-channel to channelize a cellular interface into an Eth-channel interface.
Use undo eth-channel to remove the Eth-channel interface channelized from a cellular interface.
Syntax
undo eth-channel channel-number
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
channel-number: Specifies an Eth-channel interface by its number.
Usage guidelines
This command names the Eth-channel interface channelized from a cellular interface as eth-channel cellular-number:channel-number.
Examples
# Channelize Cellular 2/4/0 into an Eth-channel interface.
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] eth-channel 0
imsi bind
Use imsi bind to bind the IMSI on the SIM card to an interface.
Use undo imsi bind to restore the default.
Syntax
imsi bind interface-type interface-number
undo imsi bind
Default
The IMSI on the SIM card is not bound to any interface.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number. In the current software version, the IMSI on the SIM card can only be bound to an L2TP virtual PPP interface.
Usage guidelines
IMPORTANT: This command is not available for distributed devices and IRF devices. |
The device must support PPP LCP negotiation of the IMSI/SI when it acts as a LAC to access the LNS in LAC-auto-initiated mode. After you bind the IMSI on the SIM card to a virtual PPP interface, the packets sent by the device carry the IMSI.
Examples
# Bind the IMSI on the SIM card to Virtual-PPP 1.
<Sysname> system-view
[Sysname] controller Cellular 0/0
[Sysname-Cellular0/0] imsi bind virtual-ppp 1
interface eth-channel
Use interface eth-channel to enter Eth-channel interface view.
Syntax
interface eth-channel interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies an Eth-channel interface by its number.
Examples
# Enter Eth-channel 2/4/0:0 interface view.
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0]
ip address cellular-alloc
Use ip address cellular-alloc to enable an Eth-channel interface to obtain an IP address by using the modem-manufacturer's proprietary protocol.
Use undo ip address cellular-alloc to restore the default.
Syntax
undo ip address cellular-alloc
Default
An Eth-channel interface does not obtain an IP address by using the modem-manufacturer's proprietary protocol.
Views
Eth-channel interface view
Predefined user roles
network-admin
Usage guidelines
To enable an interface to obtain an IP address from the modem by using the modem-manufacturer's proprietary protocol, use the ip address cellular-alloc command.
To enable an interface to obtain an IP address from the modem by using DHCP, use the ip address dhcp-alloc command.
The IP address of the modem is automatically allocated by the service provider.
Examples
# Channelize Cellular 2/4/0 into an Eth-channel interface. Enable the Eth-channel interface to obtain an IP address by using the modem-manufacturer's proprietary protocol.
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] eth-channel 0
[Sysname-Cellular2/4/0] quit
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0] ip address cellular-alloc
ipv6 address cellular-alloc
ipv6 address cellular-alloc
Use ipv6 address cellular-alloc to enable an interface to obtain an IPv6 address by using the modem-manufacturer's proprietary protocol.
Use undo ipv6 address cellular-alloc to restore the default.
Syntax
ipv6 address cellular-alloc
undo ipv6 address cellular-alloc
Default
An interface does not obtain an IPv6 address by using the modem-manufacturer's proprietary protocol.
Views
Eth-channel interface view
Predefined user roles
network-admin
Usage guidelines
This command enables an interface to obtain an IPv6 address from the modem by using the modem-manufacturer's proprietary protocol, use the ipv6 address cellular-alloc command.
To enable an interface to obtain an IP address from the modem by using DHCP, use the ipv6 address dhcp-alloc command.
The IPv6 address of a modem is automatically allocated by the service provider.
Examples
# Channelize Cellular 2/4/0 into an Eth-channel interface. Enable the Eth-channel interface to obtain an IPv6 address by using the modem-manufacturer's proprietary protocol.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Cellular2/4/0] eth-channel 0
[Sysname-Cellular2/4/0] quit
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0] ipv6 address cellular-alloc
Related commands
ip address cellular-alloc
lte band
Use lte band to specify a band for a 4G modem.
Use undo lte band to restore the default.
Syntax
lte band band-number
undo lte band
Default
The default setting for this command varies by 4G modem model.
Views
Cellular interface view
Predefined user roles
network-admin
Parameters
band-number: Specifies a band for a 4G modem. The available bands vary by modem model.
Usage guidelines
IMPORTANT: This command is supported only by the following 4G modems: · Sierra MC7354 and MC7304. · Long Sung U8300C, U8300W, and U8300. · WNC DM11-2. |
Examples
# Specify band 3 for Cellular 2/4/0.
<Sysname> system-view
[Sysname] controller cellular 2/4/0
[Sysname-Controller-Cellular2/4/0]lte band 3
Related commands
gsm band
wcdma band
mtu
Use mtu to set the maximum transmission unit (MTU) for an interface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU of an interface is 1500 bytes.
Views
Eth-channel interface view
Predefined user roles
network-admin
Parameters
size: Sets the MTU in the range of 128 to 2000, in bytes.
Examples
# Set the MTU for Eth-channel 2/4/0:0 to 1430 bytes.
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0] mtu 1430
pdp-type
Use pdp-type to specify the PDP data carrying protocol.
Use undo pdp-type to restore the default.
Syntax
pdp-type { ipv4 | ipv6 | ipv4v6 }
undo pdp-type
Default
The PDP data carrying protocol is IPv4 and IPv6.
Views
Apn-profile view
Predefined user roles
network-admin
Parameters
ipv4: Specifies the IPv4 protocol.
ipv6: Specifies the IPv6 protocol.
ipv4v6: Specifies the IPv4 and IPv6 protocols.
Examples
# Specify the PDP data carrying protocol as IPv4.
<Sysname> system-view
[Sysname] apn-profile 1
[Sysname-apn-profile-1] pdp-type ipv4
reset counters interface
Use reset counters interface to clear the statistics on the specified or all Eth-channel interfaces.
Syntax
reset counters interface [ eth-channel [ channel-id ] ]
Views
User view
Predefined user roles
network-admin
Parameters
eth-channel: Specifies Eth-channel interfaces.
channel-id: Specifies an Eth-channel interface by its number.
Usage guidelines
Use this command to clear history statistics if you want to collect traffic statistics for a specific period.
· If you do not specify an interface type, the command clears statistics on all interfaces.
· If you specify the eth-channel keyword without specifying the channel ID, the command clears statistics on all Eth-channel interfaces.
· If you specify both the eth-channel keyword and the channel ID, the command clears statistics on the specified Eth-channel interface.
Examples
# Clear the statistics on Eth-channel 2/4/0:0.
<Sysname> reset counters interface eth-channel 2/4/0:0
shutdown
Use shutdown to shut down an Eth-channel interface.
Use undo shutdown to bring up an Eth-channel interface.
Syntax
shutdown
undo shutdown
Default
An Eth-channel interface is up.
Views
Eth-channel interface view
Predefined user roles
network-admin
Examples
# Shut down Eth-channel 2/4/0:0.
[Sysname] interface eth-channel 2/4/0:0
[Sysname-Eth-channel2/4/0:0] shutdown
DDR commands
Commands and descriptions for centralized devices apply to the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR2600-6-X1/2600-10-X1.
· MSR 2630.
· MSR3600-28/3600-51.
· MSR3600-28-SI/3600-51-SI.
· MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC.
MSR 3610/3620/3620-DP/3640/3660.
· MSR/810-LM-GL/810-W-LM-GL/830-6EI-GL/830-10EI-GL/830-6HI-GL/830-10HI-GL/2600-6-X1-GL/3600-28-SI-GL.
Commands and descriptions for distributed devices apply to the following routers:
· MSR5620.
· MSR 5660.
· MSR 5680.
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
MSR3600-28-SI and MSR3600-51-SI routers do not support DDR commands.
bandwidth
Use bandwidth to set the expected bandwidth for a dialer 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
Dialer interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth of an interface affects the link costs in OSPF, OSPFv3, and IS-IS. For more information, see Layer 3—IP Routing Configuration Guide.
Examples
# Set the expected bandwidth of Dialer 1 to 100 kbps.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] bandwidth 100
default
Use default to restore the default settings for a dialer interface.
Syntax
default
Views
Dialer 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 when you execute it on a live network. |
This command might fail to restore the default settings for some commands for reasons such as command dependencies or system restrictions. Use the display this command in interface view to identify these commands, and then use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to resolve the problem.
Examples
# Restore the default settings for Dialer 1.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] default
description
Use description to set a description for a dialer interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of a dialer interface is interface-name Interface, for example, Dialer1 Interface.
Views
Dialer 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 of Dialer 1 to dialer-intf.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] description dialer-intf
dialer bundle enable
Use dialer bundle enable to enable bundle DDR on a dialer interface.
Use undo dialer bundle enable to disable bundle DDR on a dialer interface.
Syntax
dialer bundle enable
undo dialer bundle enable
Default
Bundle DDR is disabled on a dialer interface.
Views
Dialer interface view
Predefined user roles
network-admin
Usage guidelines
DDR includes traditional DDR and bundle DDR.
Before using bundle DDR, use this command to enable bundle DDR on a dialer interface. Then assign physical interfaces to the corresponding dialer bundle by using the dialer bundle-member command. To enable bundle DDR to receive calls, configure the dialer peer-name command on the dialer interface.
After you configure this command on a dialer interface already enabled with traditional DDR, the system clears the original traditional DDR settings.
The undo dialer bundle enable command clears all bundle DDR settings on the dialer interface.
Examples
# Enable bundle DDR on Dialer 1.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] dialer bundle enable
dialer bundle-member
dialer circular enable
dialer peer-name
dialer bundle-member
Use dialer bundle-member to assign a physical interface to a dialer bundle in bundle DDR.
Use undo dialer bundle-member to remove a physical interface from a dialer bundle in bundle DDR.
Syntax
dialer bundle-member number [ priority priority ]
undo dialer bundle-member number
Default
A physical interface does not belong to any dialer bundle in bundle DDR.
Views
Physical interface view
Predefined user roles
network-admin
Parameters
number: Specifies a dialer bundle by its number, which must be the same as the dialer interface number.
priority priority: Specifies the priority of the physical interface in the dialer bundle, in the range of 1 to 255. The default priority is 1. The greater the number, the higher the priority. Each time a call is placed, the highest-priority physical interface available is selected. If multiple physical interfaces with the highest priority are available, these interfaces are selected in a round-robin manner.
Usage guidelines
A physical interface can belong to multiple dialer bundles. You can configure this command multiple times to assign a physical interface to different dialer bundles.
When the specified dialer interface does not exist, this command creates one and enables bundle DDR on it.
Examples
# Assign BRI 2/4/0 to Dialer bundle 1 and Dialer bundle 2, with a priority of 50 in both dialer bundles.
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] dialer bundle-member 1 priority 50
[Sysname-Bri2/4/0] dialer bundle-member 2 priority 50
dialer bundle enable
interface dialer
dialer callback-center
Use dialer callback-center to configure the PPP callback reference.
Use undo dialer callback-center to restore the default.
Syntax
dialer callback-center [ dial-number | user ] *
undo dialer callback-center
Default
No PPP callback reference is configured.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
dial-number: Uses the callback number configured in the authorization-attribute callback-number command in local user view to place return calls.
user: Uses the dial string configured in the dialer route command to place return calls.
Usage guidelines
This command is mandatory on the PPP callback server.
If both the dial-number and user keywords are specified, the device attempts to place return calls by using the dial string determined by the first keyword entered. If the attempt fails, the device places return calls by using the dial string determined by the second keyword entered.
If the command is configured with neither keyword, it has the same effect as the dialer callback-center user dial-number command.
Examples
# Specify the device as the PPP callback server, and set the callback reference to user mode.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp callback server
[Sysname-Serial2/1/0] dialer callback-center user
[Sysname-Serial2/1/0] dialer route ip 1.1.1.2 dial-number 8810052 user Sysnameb
# Specify the device as the PPP callback server, and set the callback reference to dial number mode.
<Sysname> system-view
[Sysname] local-user usera
[Sysname-luser-usera] password simple usera
[Sysname-luser-usera] service-type ppp
[Sysname-luser-usera] authorization-attribute callback-number 8810048
[Sysname-luser-usera] quit
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp callback server
[Sysname-Serial2/1/0] dialer callback-center dial-number
ppp callback
dialer call-in
Use dialer call-in to configure a dialup interface to accept incoming calls from an ISDN calling number or enable callback for the ISDN calling number.
Use undo dialer call-in to restore the default.
Syntax
dialer call-in remote-number [ callback ]
undo dialer call-in remote-number [ callback ]
Default
Calls from all ISDN calling numbers are accepted, and callback is not initiated.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
remote-number: Specifies an ISDN calling number, a case-insensitive string of 1 to 30 characters. The asterisk (*) is allowed as a wildcard that matches any character.
callback: Enables callback for the specified ISDN calling number.
Usage guidelines
A dialup interface screens an incoming call by comparing the calling number with the numbers configured in the dialer call-in command. If the remote SPCS does not provide the calling number, the call is dropped directly.
On a dialup interface configured with the dialer call-in callback command, you must configure the dialer route or dialer number command. The dial-number configured in the dialer route or dialer number command must be the same as the remote-number configured in the dialer call-in callback command.
Examples
# Configure BRI 2/4/0 to place return calls for ISDN calling number 8810152.
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] dialer route ip 100.1.1.2 dial-number 8810152
[Sysname-Bri2/4/0] dialer call-in 8810152 callback
dialer callback-center
dialer circular enable
Use dialer circular enable to enable traditional DDR on a dialup interface.
Use undo circular bundle enable to disable traditional DDR on a dialup interface.
Syntax
dialer circular enable
undo dialer circular enable
Default
Traditional DDR is disabled on a dialup interface.
Views
Dialup interface view
Predefined user roles
network-admin
Usage guidelines
DDR includes traditional DDR and bundle DDR.
Before using traditional DDR, you must use this command to enable traditional DDR on the dialup interface.
If you configure this command on a dialup interface already enabled with bundle DDR, the system clears the original bundle DDR settings.
The undo dialer circular enable command clears all DDR settings on the dialup interface.
Examples
# Enable traditional DDR on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer circular enable
Related commands
dialer bundle enable
dialer circular-group
dialer circular-group
Use dialer circular-group to assign a physical interface to a dialer circular group in traditional DDR.
Use undo dialer circular-group to restore the default.
Syntax
dialer circular-group number
undo dialer circular-group
Default
A physical interface does not belong to any dialer circular group in traditional DDR.
Views
Physical interface view
Predefined user roles
network-admin
Parameters
number: Specifies a dialer circular group by its number, which must be the same as the one defined in the interface dialer command.
Usage guidelines
In traditional DDR, you can assign a physical interface to a dialer interface by assigning it to the dialer circular group associated with the dialer interface. A physical interface can belong to only one dialer circular group, but a dialer circular group can contain multiple physical interfaces. When placing a call on a dialer circular group, DDR selects the physical interface with the highest priority.
When the dialer interface does not exist, this command creates one and enables traditional DDR on it.
Examples
# Assign interfaces Serial 2/1/0 and Serial 2/1/1 to dialer circular group 1.
[Sysname] interface dialer 1
[Sysname-Dialer1] quit
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer circular-group 1
[Sysname-Serial2/1/0] quit
[Sysname] interface serial 2/1/1
[Sysname-Serial2/1/1] dialer circular-group 1
dialer circular enable
dialer priority
interface dialer
dialer disconnect
Use dialer disconnect to disconnect dialup links on an interface.
Syntax
dialer disconnect [ 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, this command disconnects dialup links on all interfaces.
Examples
# Disconnect dialup links on Dialer 0.
<Sysname> dialer disconnect interface dialer0
dialer flow-interval
Use dialer flow-interval to set the interval for DDR to collect traffic statistics.
Use undo dialer flow-interval to restore the default.
Syntax
dialer flow-interval interval
undo dialer flow-interval
Default
The interval for DDR to collect traffic statistics is 20 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Specifies the interval for DDR to collect traffic statistics, in the range of 1 to 1500 seconds.
Usage guidelines
DDR provides traffic statistics for dialup links at the user-configured interval.
Examples
# Set the interval for DDR to collect traffic statistics to 3 seconds.
<Sysname> system-view
[Sysname] dialer flow-interval 3
dialer threshold
dialer number
Use dialer number to configure a dial string for placing calls to a single remote site.
Use undo dialer number to restore the default.
Syntax
dialer number dial-number [ autodial ]
undo dialer number
Default
No dial string is configured for calling the remote site.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
dial-number: Specifies a dial string for calling a remote site, a case-insensitive string of 1 to 30 characters.
autodial: Enables the interface to automatically dial the remote site by using the specified dial string at specified intervals. The interval is set in the dialer timer autodial command and defaults to 300 seconds.
Usage guidelines
You must configure this command when the dialer or physical interface is the calling party.
In traditional DDR, you can also use the dialer route command to configure multiple destination addresses or dial strings for a dialer interface.
In bundle DDR, you can only use the dialer number command to configure one dial string for each dialer interface. This is because associations between dialer interfaces and call destination address are one-to-one.
Examples
# Set the dial string for placing calls to 11111 on Dialer 1.
[Sysname] interface dialer 1
[Sysname-Dialer1] dialer number 11111
dialer route
dialer timer autodial
dialer peer-name
Use dialer peer-name to specify the host name of the remote device for authenticating incoming calls.
Use undo dialer peer-name to remove the specified host name.
Syntax
dialer peer-name username
undo dialer peer-name [ username ]
Default
No host name of the remote device is specified for authenticating incoming calls.
Views
Dialer interface view
Predefined user roles
network-admin
Parameters
username: Specifies the host name of the remote device, a case-insensitive string of 1 to 80 characters.
Usage guidelines
The local device matches the peer names obtained in PPP authentication with the host names configured by this command to determine which dialer interface receives which call.
This command takes effect only on bundle DDR dialer interfaces. You can configure a maximum number of 255 host names for a dialer interface. This enables one dialer interface to receive calls from multiple physical interfaces.
If a bundle DDR dialer interface is not configured with any host name, this interface can place calls but cannot receive calls.
Examples
# Specify the host name of the remote device for Dialer 1 to routerb.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] dialer peer-name routerb
dialer priority
Use dialer priority to assign a priority to a physical interface in a dialer circular group.
Use undo dialer priority to restore the default.
Syntax
dialer priority priority
undo dialer priority
Default
The priority of a physical interface in a dialer circular group is 1.
Views
Physical interface view
Predefined user roles
network-admin
Parameters
priority: Specifies the priority of the physical interface in a dialer circular group, in the range of 1 to 127. The larger the value, the higher the priority.
Usage guidelines
This command sets the order in which the available physical interfaces in a dialer circular group are used. Each time a call is placed, the highest-priority physical interface available is selected. If multiple physical interfaces with the highest priority are available, these interfaces are selected in a round-robin manner.
Examples
# Set the priority of Serial 2/1/0 in dialer circular group 1 to 5.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer circular-group 1
[Sysname-Serial2/1/0] dialer priority 5
dialer circular-group
dialer queue-length
Use dialer queue-length to set the number of packets that can be buffered on a dialup interface.
Use undo dialer queue-length to restore the default.
Syntax
dialer queue-length packets
undo dialer queue-length
Default
No packets are buffered on a dialup interface.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
packets: Specifies the number of packets that can be buffered on the interface, in the range of 1 to 100.
Usage guidelines
If no connection is available when a dialup interface without a buffer queue receives a packet, the interface drops the packet. Configured with a buffer queue, the dialup interface buffers the packet until a connection is available for packet sending.
Examples
# Set the number of packets that can be buffered to 10 on Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer queue-length 10
dialer route
Use dialer route to configure a dialup interface to place calls to a remote site or receive calls from it.
Use undo dialer route to remove the configuration.
Syntax
dialer route ip next-hop-address [ mask network-mask-length ] [ vpn-instance vpn-instance-name ] [ dial-number number [ autodial | interface interface-type interface-number ] * ] [ broadcast | user hostname ] *
undo dialer route protocol next-hop-address [ mask network-mask-length ] [ vpn-instance vpn-instance-name ] [ dial-number number ]
Default
No dial string is configured.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
ip: Specifies IP as the network layer protocol.
next-hop-address: Specifies the IP address of the remote site.
mask network-mask-length: Specifies a mask length for the remote IP address, in the range of 0 to 32. If no mask length is specified, a 32-bit mask applies. Setting the next-hop-address argument to 0.0.0.0 and the network-mask-length argument to 0 indicates any remote IP address.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
dial-number number: Specifies the dial string for calling the remote site, a case-insensitive string of 1 to 30 characters. If no dial string is specified, the interface can only receive calls.
autodial: Enables the interface to automatically dial the specified dial string at specified intervals. The interval is set in the dialer timer autodial command and defaults to 300 seconds.
interface interface-type interface-number: Specifies a physical interface by its type and number. When multiple physical interfaces are assigned to a dialer interface and their dialup links are connected to different SPCSs, you must associate each dial string with one physical interface. This configuration is intended for dialer interfaces in traditional DDR only.
broadcast: Enables broadcast packets to pass through the dialup link.
user hostname: Specifies a host name of the remote device, a case-insensitive string of 1 to 80 characters used to authenticate incoming calls.
Usage guidelines
To enable DDR to originate calls, you must configure the dial-number number option. Otherwise, DDR can only receive calls.
If you specify the number argument in the dialer route command, you must also include the number argument when using the undo dialer route command to remove the dial string.
To use the user keyword, you must configure PPP authentication. DDR accepts a call only when the host name obtained through PPP authentication is the same as the remote username configured by using this command.
You can configure a dialup interface to place calls to or receive calls from multiple remote sites. You can also configure multiple dial strings for one destination address for backup purposes.
Examples
# Specify a dial string of 888066 for packets destined to network 192.168.1.0/24.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer route ip 192.168.1.0 mask dial-number 24 888066
# Specify a dial string of 888065 for packets destined to host address 191.168.1.1.
[Sysname-Serial2/1/0] dialer route ip 191.168.1.1 dial-number 888065
dialer timer autodial
dialer threshold
Use dialer threshold to set the traffic threshold for a dialer interface.
Use undo dialer threshold to restore the default.
Syntax
dialer threshold traffic-percentage [ in | in-out | out ]
undo dialer threshold
Default
The traffic threshold is not set for a dialer interface.
Views
Dialer interface view
Predefined user roles
network-admin
Parameters
traffic-percentage: Specifies the traffic threshold as a percentage of aggregate link bandwidth, in the range of 0 to 99.
in: Calculates the actual load on incoming traffic only.
in-out: Calculates the actual load on incoming traffic or outgoing traffic, whichever is greater.
out: Calculates the actual load on outgoing traffic only.
Usage guidelines
To ensure appropriate traffic distribution on DDR links, DDR brings up links in an MP bundle until either of the following conditions is met:
· The upper limit of links is reached.
· The percentage of traffic to the bandwidth of all activated links is equal to or lower than the traffic threshold.
To ensure the DDR link efficiency, DDR shuts down links in an MP bundle until either of the following conditions is met:
· The lower limit of links is reached.
· The percentage of traffic to the bandwidth of (n-1) activated links is equal to or higher than the traffic threshold.
For more information about the upper limit and lower limit of links, see Layer 2—WAN Access Configuration Guide.
If you set the traffic threshold to 0, DDR brings up all available links when triggered by auto-dial or packets. In addition, DDR does not disconnect these links based on the link idle-timeout timer.
This command must be used with the ppp mp command. To implement MP with DDR, you must use dialer interfaces.
DDR collects traffic statistics at the interval set by using the dialer flow-interval command.
Examples
# Set the traffic threshold on Dialer1 to 80%.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] dialer threshold 80
dialer flow-interval
dialer timer idle
ppp mp (Layer 2—WAN Access Command Reference)
dialer timer autodial
Use dialer timer autodial to set the auto-dial timer.
Use undo dialer timer autodial to restore the default.
Syntax
dialer timer autodial autodial-interval
undo dialer timer autodial
Default
The auto-dial timer is 300 seconds.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
autodial-interval: Specifies the interval between auto-dial attempts, in the range of 1 to 604800 seconds.
Usage guidelines
This command takes effect only when the autodial keyword is specified in the dialer number or dialer route command. DDR automatically dials the dial string at the specified interval until a connection is established. In the auto-dial method, dial attempts are not traffic triggered. Once a connection is established, it will not disconnect based on the idle timer mechanism.
Examples
# Set the auto-dial timer to 60 seconds on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer timer autodial 60
dialer number
dialer route
dialer timer compete
Use dialer timer compete to set the compete-idle timer.
Use undo dialer timer compete to restore the default.
Syntax
dialer timer compete compete-idle
undo dialer timer compete
Default
The compete-idle timer is 20 seconds.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
compete-idle: Specifies the idle time when contention occurs, in the range of 0 to 65535 seconds.
Usage guidelines
The idle-timeout timer starts when a link is established. If all physical interfaces are in use when DDR places a new call, contention occurs. DDR starts the compete-idle timer to replace the idle-timeout timer. When the compete-idle timer expires, DDR disconnects the idle links.
Examples
# Set the compete-idle timer to 10 seconds on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer timer compete 10
dialer timer enable
Use dialer timer enable to set the link holddown timer.
Use undo dialer timer enable to restore the default.
Syntax
dialer timer enable interval
undo dialer timer enable
Default
The link holddown timer is 5 seconds.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
interval: Specifies the holddown timer value in the range of 5 to 65535 seconds.
Usage guidelines
The holddown timer starts when a link is disconnected. A call attempt to bring up this link can be made only after the timer expires. This is to prevent a remote SPCS from being overloaded.
To leave enough time for callback, set the holddown timer on the client 10 or more seconds longer than that on the server. As a best practice, set the link holddown timer to 5 seconds (the default) on the server, and 15 seconds on the client.
Examples
# Set the link holddown timer to 15 seconds for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer timer enable 15
dialer timer idle
Use dialer timer idle to set the link idle-timeout timer.
Use undo dialer timer idle to restore the default.
Syntax
dialer timer idle idle [ in | in-out ]
undo dialer timer idle
Default
The link idle-timeout timer is 120 seconds, and only outgoing interesting packets reset this timer.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
idle: Specifies the link idle-timeout timer value in the range of 0 to 65535 seconds.
in: Allows only incoming interesting packets to reset the timer.
in-out: Allows both incoming and outgoing interesting packets to reset the timer.
Usage guidelines
The link idle-timeout timer starts when a link is established. If no interesting packets arrive before the timer expires, DDR disconnects the link.
If you do not specify the in or in-out keyword, only outgoing interesting packets reset the timer.
If the timer is set to 0, DDR will never disconnect the link. For a PPPoE client application, if the timer is set to 0, a dialup connection is created automatically and remains active permanently.
Examples
# Set the link idle-timeout timer to 50 seconds on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer timer idle 50
dialer timer wait-carrier
Use dialer timer wait-carrier to set the wait-carrier timer.
Use undo dialer timer wait-carrier to restore the default.
Syntax
dialer timer wait-carrier wait-carrier
undo dialer timer wait-carrier
Default
The wait-carrier timer is 60 seconds.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
wait-carrier: Specifies the wait-carrier timer value in the range of 0 to 65535 seconds.
Usage guidelines
The wait-carrier timer limits the amount of time that DDR waits for a connection to be established for a call. The wait-carrier timer starts when a call is placed. If the connection is not established before the timer expires, DDR terminates the call.
Examples
# Set the wait-carrier timer to 100 seconds on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer timer wait-carrier 100
dialer timer warmup
Use dialer timer warmup to set the warm-up timer for dynamic route backup.
Use undo dialer timer warmup to restore the default.
Syntax
dialer timer warmup delay
undo dialer timer warmup
Default
The warm-up timer for dynamic route backup is 30 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
delay: Specifies the warm-up timer value for dynamic route backup, in the range of 0 to 65535 seconds.
Usage guidelines
The warm-up timer introduces a delay for the dynamic route backup feature to operate after a system startup. Set this delay to prevent unnecessary link switchover at startup.
Interfaces cannot come up until the device recovers the configuration during a reboot.
Without a warm-up delay, the dynamic route backup feature dials the secondary link immediately after it detects that the primary interface is down. When the primary interface comes up, the feature dials the primary link. The secondary link, if dialed up successfully, is brought down shortly after it came up.
With a warm-up delay, the dynamic route backup feature does not dial the secondary link until it detects that the primary interface is down when the delay expires.
Examples
# Set the warm-up timer to 20 seconds for dynamic route backup.
<Sysname> system-view
[Sysname] dialer timer warmup 20
dialer-group
Use dialer-group to assign a dialup interface to a dialer group.
Use undo dialer-group to restore the default.
Syntax
dialer-group group-number
undo dialer-group
Default
A dialup interface does not belong to any dialer group.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
group-number: Specifies a dialer group by its number in the range of 1 to 255. Before the assignment, you must create the dialer group by using the dialer-group rule command.
Usage guidelines
A dialup interface can belong to only one dialer group. If you configure this command multiple times, the most recent configuration takes effect.
You must configure this command for DDR to send packets.
Examples
# Assign Serial 2/1/0 to dialer group 1.
<Sysname> system-view
[Sysname] dialer-group 1 rule ip acl 3101
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer-group 1
dialer-group rule
dialer-group rule
Use dialer-group rule to create a dialer group and configure a dial rule for it.
Use undo dialer-group rule to delete a dialer group.
Syntax
dialer-group group-number rule { ip | ipv6 } { deny | permit | acl { acl-number | name acl-name } }
undo dialer-group group-number rule [ ip | ipv6 ]
Default
No dialer group exists.
Views
System view
Predefined user roles
network-admin
Parameters
group-number: Specifies the number of the dialer group to be created, in the range of 1 to 255.
ip: Specifies the IPv4 protocol.
ipv6: Specifies the IPv6 protocol.
deny: Denies packets of the specified protocol.
permit: Permits packets of the specified protocol.
acl acl-number: Specifies an ACL by its number in the range of 2000 to 3999.
name acl-name: Specifies an ACL by its name.
Usage guidelines
A dial rule determines when an interface initiates DDR calls. You need to configure dial rules only on the initiator of DDR calls.
You can configure a dial rule to match only IP packets or use an ACL to match packets.
Permitted protocol packets or packets that match a permit statement of an ACL are interesting packets. When receiving an interesting packet, DDR performs one of the following operations:
· Sends it out and resets the idle-timeout timer if a link is present.
· Originates a new call to establish a link if no link is present.
Denied protocol packets or packets that match a deny statement of an ACL are uninteresting packets. When receiving an uninteresting packet, DDR performs one of the following operations:
· Sends it out without resetting the idle-timeout timer if a link is present.
· Drops it if no link is present.
For DDR to forward packets correctly, you must configure a dial rule and associate it with the dialup interface by using the dialer-group command.
Examples
# Create dialer group 1 and configure DDR to place calls for IPv4 packets. Associate Serial 2/1/0 with dialer group 1.
<Sysname> system-view
[Sysname] dialer-group 1 rule ip permit
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer-group 1
# Create dialer group 1 and configure DDR to place calls for IPv6 packets. Associate Serial 2/1/0 with dialer group 1.
<Sysname> system-view
[Sysname] dialer-group 1 rule ipv6 permit
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] dialer-group 1
Related commands
dialer-group
display dialer
Use display dialer to display the DDR information for an interface.
Syntax
display dialer [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the DDR information for all interfaces.
Examples
# Display the DDR information for all interfaces.
<Sysname> display dialer
Dialer0:
Dialer Route:
NextHop: 111.111.111.111 Dialer number: 123456789012345678901234567890
NextHop: 222.222.222.222 Dialer number: 123456789012345678901234567890
Dialer number:
Dialer Timers(in seconds):
Auto-dial: 300 Compete: 20 Enable: 5
Idle: 120 Wait-for-Carrier: 60
Total Channels: 1
Free Channels: 1
Table 57 Command output
Field |
Description |
Dialer0 |
Dialup interface: dialer or physical. |
Dialer Route: NextHop: 111.111.111.111 Dialer number: 123456789012345678901234567890 |
Remote IP address and dial string set by using the dialer route command. |
Dialer number |
Dial string for a remote IP address. |
Dialer Timers(in seconds): Auto-dial: 300 Compete: 20 Enable: 5 Idle: 120 Wait-for-Carrier: 60 |
DDR timers in seconds: · Auto-dial—Auto-dial timer set by the dialer timer autodial command. · Compete—Compete-idle timer set by the dialer timer compete command. · Enable—Link holddown timer set by the dialer timer enable command. · Idle—Link idle-timeout timer set by the dialer timer idle command. · Wait-for-Carrier—Wait-carrier timer set by the dialer timer wait-carrier command. |
Total Channels |
Total number of physical interfaces on the interface. For an ISDN interface, it refers to the number of B channels. |
Free Channels |
Number of free channels. |
display interface dialer
Use display interface dialer to display information about a dialer interface.
Syntax
display interface [ dialer [ interface-number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-number: Specifies a dialer interface by its number.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of each interface description.
down: Displays information about interfaces in physically down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Usage guidelines
If you do not specify the dialer keyword, this command displays information about all interfaces on the device.
If you specify the dialer keyword, this command displays information about all dialer interfaces.
Examples
# Display detailed information about Dialer 1.
<Sysname> display interface dialer 1
Dialer1
Current state: UP
Line protocol state: UP (spoofing)
Description: Dialer1 Interface
Bandwidth: 64kbps
Maximum Transmit Unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet protocol processing: disabled
Link layer protocol: PPP
LCP: initial
Physical: Dialer, baudrate: 64000 bps
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 dropped
Output: 0 packets, 0 bytes, 0 dropped
# Display brief information about Dialer 1.
<Sysname> display interface dialer 1 brief
Brief information on interface(s) under route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Main IP Description
Dia1 UP UP(s) --
# Display brief information about all dialer interfaces in physically Down state.
<Sysname> display interface dialer brief down
Brief information on interface(s) under route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
Dia1 ADM Administratively
Table 58 Command output
Field |
Description |
Dialer1 Current state |
Physical state of the dialer interface: · UP—The dialer interface is physically up. · DOWN (Administratively)—The dialer interface was shut down by using the shutdown command. To re-enable it, you must execute the undo shutdown command. |
Line protocol state |
Data link layer protocol state of the dialer interface: UP or DOWN. |
Description |
Interface description. |
Bandwidth |
Expected bandwidth of the interface. |
Maximum Transmit Unit |
MTU of the dialer interface. |
Internet protocol processing |
Network layer protocol state of the dialer interface. |
Hold timer |
Interval for sending keepalive packets. |
retry times |
Maximum number of keepalive retransmission attempts. A link is removed after the maximum number of retransmission attempts is reached. |
LCP: initial |
LCP initialization is complete. |
Physical |
Physical interface type. |
Output queue - Urgent queuing: Size/Length/Discards |
Statistics on the packets in the urgent output queue. |
Output queue - Protocol queuing: Size/Length/Discards |
Statistics on the packets in the protocol output queue. |
Output queue - FIFO queuing: Size/Length/Discards |
Statistics on the packets in the FIFO output queue. |
Last clearing of counters: Never |
Time when the reset counters interface command was last used to clear the interface statistics. This field displays Never if the reset counters interface command has never been used on the interface since device startup. |
Last 300 seconds input rate |
Input interface data rate during the latest 300 seconds. |
Last 300 seconds output rate |
Output interface data rate during the latest 300 seconds. |
Input: 0 packets, 0 bytes, 0 dropped |
Statistics on the packets reaching the interface. |
Output: 0 packets, 0 bytes, 0 dropped |
Statistics on the packets sent through the interface. |
Brief information on interface(s) under route mode: |
Brief information about Layer 3 interfaces. |
Link: ADM - administratively down; Stby - standby |
Link status: · ADM—The interface has been administratively shut down. To recover its physical state, execute the undo shutdown command. · Stby—The interface is operating as a standby interface. To display the active interface, use the display interface-backup state command (High Availability Command Reference). |
Protocol: (s) - spoofing |
If the data link layer protocol state of an interface is shown as UP, but its link is an on-demand link or not present at all, its protocol attribute includes the spoofing flag (an s in parentheses). |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is up. · ADM—The interface has been administratively shut down. To bring up the interface, execute the undo shutdown command. · Stby—The interface is operating as a standby interface. |
Protocol |
Data link layer protocol state of the dialer interface: · UP. · DOWN. · UP(s)—The interface is up, but its link is an on-demand link or not present at all. |
Main IP |
Primary IP address of the interface. |
Description |
Description of the interface. |
Cause |
Reason why a physical link is down. If the port has been shut down by using the shutdown command, this field displays Administratively. To restore the physical state of the interface, use the undo shutdown command. Not connected indicates no physical connection due to absence or failure of a network cable. |
Related commands
reset counters interface
interface dialer
Use interface dialer to create a dialer interface and enter its view, or enter the view of an existing dialer interface.
Use undo interface dialer to delete a dialer interface.
Syntax
interface dialer number
undo interface dialer number
Default
No dialer interface exists.
Views
System view
Predefined user roles
network-admin
Parameters
number: Specifies the number of the dialer interface, in the range of 0 to 1023.
Usage guidelines
A dialer interface has a fixed baud rate of 64000 bps.
Examples
# Create Dialer 1.
<Sysname> system-view
[Sysname] interface dialer 1
mtu
Use mtu to set the maximum transmission unit (MTU) of a dialer interface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU of dialer interfaces is 1500 bytes.
Views
Dialer interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU in the range of 128 to 1500 bytes.
Usage guidelines
The MTU setting of a dialer interface affects the fragmentation and reassembly of IP packets.
Examples
# Set the MTU of Dialer 1 to 1200 bytes.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] mtu 1200
ppp callback
Use ppp callback to enable an interface to initiate or accept callback requests as the callback client or server.
Use undo ppp callback to disable an interface from initiating or accepting callback requests.
Syntax
ppp callback { client | server }
undo ppp callback { client | server }
Default
Callback requests are not initiated or accepted.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
client: Enables the interface to initiate callback requests as the callback client.
server: Enables the interface to accept callback requests as the callback server.
Usage guidelines
The callback client first originates a call, and the server decides whether to place a return call. If a return call is needed, the callback server disconnects the call and originates a return call according to the username or callback number.
PPP callback saves costs when the call rates in two directions are different.
Examples
# Enable Serial 2/1/0 to accept callback requests as the callback server.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] ppp callback server
ppp callback ntstring
Use ppp callback ntstring to specify a dial string for a Windows server to call back.
Use undo ppp callback ntstring to restore the default.
Syntax
ppp callback ntstring dial-number
undo ppp callback ntstring
Default
No callback dial string is specified.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
dial-number: Specifies the dial string, a case-sensitive string of 1 to 64 characters.
Usage guidelines
Configure this command on the callback client if the Windows server requires PPP callback clients to send callback numbers.
Examples
# Specify a dial string of 1234567 for the Windows server to call back.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] ppp callback ntstring 1234567
reset counters interface
Use reset counters interface to clear the statistics of a dialer interface.
Syntax
reset counters interface [ dialer [ interface-number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
dialer: Specifies dialer interfaces.
interface-number: Specifies a dialer interface by its number.
Usage guidelines
Use this command to clear history statistics if you want to collect traffic statistics for a specific time period.
If you do not specify the dialer keyword, this command clears statistics for all interfaces.
If you specify the dialer keyword, this command clears statistics for all dialer interfaces.
If you specify a dialer interface, this command clears statistics for the specified dialer interface.
Examples
# Clear the statistics of Dialer 1.
<Sysname> reset counters interface dialer 1
Related commands
display interface dialer
service
Use service to specify a primary traffic processing slot for an interface.
Use undo service to restore the default.
Syntax
Distributed devices in standalone mode/centralized devices in IRF mode:
service slot slot-number
undo service slot
Distributed devices in IRF mode:
service chassis chassis-number slot slot-number
undo service chassis
Default
No primary traffic processing slot is specified for an interface
Views
Dialer interface view
Default command level
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
Hardware |
Command compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR2600-6-X1-GL |
No |
MSR3600-28-SI-GL |
No |
This command is supported on distributed devices and IRF-capable centralized devices.
Specify traffic processing slots if a feature requires that all traffic on a dialer 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
# (Distributed devices in standalone mode.) Specify a primary traffic processing slot for Dialer 1.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] service slot 2
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
Distributed devices in standalone mode/centralized devices in IRF mode:
service standby slot slot-number
undo service standby slot
Distributed devices in IRF mode:
service standby chassis chassis-number slot slot-number
undo service standby chassis
Default
No backup traffic processing slot is specified for an interface
Views
Dialer interface view
Default command level
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
Hardware |
Command compatibility |
MSR810-LM-GL |
No |
MSR810-W-LM-GL |
No |
MSR830-6EI-GL |
No |
MSR830-10EI-GL |
No |
MSR830-6HI-GL |
No |
MSR830-10HI-GL |
No |
MSR2600-6-X1-GL |
No |
MSR3600-28-SI-GL |
No |
This command is supported on distributed devices and IRF-capable centralized devices.
Specify traffic processing slots if a feature requires that all traffic on a dialer 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
# (Distributed devices in standalone mode.) Specify a primary traffic processing slot and a backup traffic processing slot for Dialer 1.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] service slot 2
[Sysname- Dialer1] service standby slot 3
Related commands
service
shutdown
Use shutdown to shut down a dialer interface.
Use undo shutdown to bring up a dialer interface.
Syntax
shutdown
undo shutdown
Default
A dialer interface is up.
Views
Dialer interface view
Predefined user roles
network-admin
Examples
# Shut down Dialer 1.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] shutdown
standby routing-group
Use standby routing-group to assign a dialup interface to a dynamic route backup group.
Use undo standby routing-group to remove a dialup interface from a dynamic route backup group.
Syntax
standby routing-group group-number
undo standby routing-group group-number
Default
A dialup interface is not assigned to any dynamic route backup group.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
group-number: Specifies a dynamic route backup group by its number in the range of 1 to 255.
Usage guidelines
Before assigning a dialup interface to a dynamic route backup group, make sure DDR is enabled on the interface.
A dialup interface can be assigned to multiple dynamic route backup groups.
Examples
# Assign dialup interface BRI 2/4/0 to dynamic route backup group 1.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] standby routing-group 1
standby routing-group rule
Use standby routing-group rule to create a dynamic route backup group or add a network to be monitored to the group.
Use undo standby routing-group rule to delete a dynamic route backup group or remove a monitored network from the group.
Syntax
standby routing-group group-number rule ip ip-address { mask | mask-length } [ vpn-instance vpn-instance-name ]
undo standby routing-group group-number rule [ ip ip-address { mask | mask-length } ] [ vpn-instance vpn-instance-name ]
Default
No dynamic route backup group exists.
Views
System view
Predefined user roles
network-admin
Parameters
group-number: Specifies the number of the dynamic route backup group, in the range of 1 to 255.
ip ip-address: Specifies the IP address of the network to be monitored.
mask: Specifies the network mask.
mask-length: Specifies the network mask length in the range of 0 to 32.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
You can add a maximum of 255 monitored networks to a dynamic route backup group. DDR determines that the primary link is disconnected only when there are no valid routes to any of the networks monitored by the dynamic route backup group.
Examples
# Create dynamic route backup group 1 to monitor routes to the networks 20.0.0.0/8 and 30.0.0.0/8.
<Sysname> system-view
[Sysname] standby routing-group 1 rule ip 20.0.0.1 255.0.0.0
[Sysname] standby routing-group 1 rule ip 30.0.0.1 255.0.0.0
standby timer routing-disable
Use standby timer routing-disable to set the secondary link disconnection delay.
Use undo standby timer routing-disable to restore the default.
Syntax
standby timer routing-disable delay
undo standby timer routing-disable
Default
The secondary link disconnection delay is 20 seconds.
Views
Dialup interface view
Predefined user roles
network-admin
Parameters
delay: Specifies the secondary link disconnection delay in the range of 0 to 65535 seconds.
Examples
# Set the secondary link disconnection delay to 5 seconds on BRI 2/4/0.
<Sysname> system-view
[Sysname] interface bri 2/4/0
[Sysname-Bri2/4/0] standby timer routing-disable 5
timer-hold
Use timer-hold to set the keepalive interval.
Use undo timer-hold to restore the default.
Syntax
timer-hold seconds
undo timer-hold
Default
The keepalive interval is 10 seconds.
Views
Dialer interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval for sending keepalive packets, in the range of 0 to 32767 seconds. The value 0 disables keepalive packet sending.
Usage guidelines
On an interface encapsulated with PPP, the data link layer sends keepalive packets at keepalive intervals to detect the availability of the remote end. The data link layer determines that the peer end is down if it has not received any keepalive messages when the keepalive retry limit is reached. The data link layer then reports the link down event to the upper-layer protocols.
To set the keepalive retry limit, use the timer-hold retry command.
On a slow link, increase the keepalive interval to prevent false shutdown of the interface. This situation might occur when keepalive packets are delayed because a large packet is being transmitted on the link.
Examples
# Set the keepalive interval to 1000 seconds on Dialer 1.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] timer-hold 1000
Related commands
timer-hold retry
timer-hold retry
Use timer-hold retry to set the keepalive retry limit.
Use undo timer-hold retry to restore the default.
Syntax
timer-hold retry retries
undo timer-hold retry
Default
The keepalive retry limit is 5.
Views
Dialer interface view
Predefined user roles
network-admin
Parameters
retries: Specifies the maximum number of keepalive retransmission attempts, in the range of 1 to 255.
Usage guidelines
The interface determines that the remote end is down if it has not received a keepalive response when the keepalive retry limit is reached.
On a slow link, increase the keepalive retry limit to prevent false shutdown of the interface. This situation might occur when keepalive packets are delayed because a large packet is being transmitted on the link.
Examples
# Set the keepalive retry limit to 10 on Dialer 1.
<Sysname> system-view
[Sysname] interface dialer 1
[Sysname-Dialer1] timer-hold retry 10
Related commands
timer-hold
Frame Relay commands
This feature is supported only on Layer 2 Ethernet ports on the following modules:
· CE3/CT3.
· E1/T1.
· E1-F/T1-F.
· POS/CPOS.
· SAE.
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
· MSR810-LM-GL/810-W-LM-GL/830-6EI-GL/830-10EI-GL/830-6HI-GL/830-10HI-GL.
broadcast
Use broadcast to allow broadcast packets on a virtual circuit (VC).
Use undo broadcast to forbid broadcast packets on a VC.
Syntax
broadcast
Broadcast packets are forbidden on static VCs and allowed on dynamic VCs.
Views
Frame Relay virtual circuit view
network-admin
Configure this command if a static VC needs to allow broadcast or multicast packets.
When a VC allows broadcast packets, the broadcast or multicast packets on the Frame Relay interface of the VC are also transmitted on the VC.
Examples
# Allow broadcast packets on the VC identified by DLCI 200.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr dlci 200
[Sysname-Serial2/1/0-fr-dlci-200] broadcast
display fr compression iphc
Use display fr compression iphc to display statistics for Frame Relay IPHC.
Syntax
display fr compression iphc { rtp | tcp } [ interface interface-type interface-number [ dlci dlci-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
rtp: Displays statistics for RTP header compression.
tcp: Displays statistics for TCP header compression.
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays IPHC statistics for the main interface and its subinterfaces. If you specify a subinterface, this command displays IPHC statistics for the subinterface. If you do not specify an interface, this command displays IPHC statistics for all interfaces.
dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007.
· If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not display IPHC statistics for the VC.
· If you specify a subinterface and a VC that is not on the subinterface, this command does not display IPHC statistics for the VC.
· If you specify only an interface, this command displays IPHC statistics for all VCs on the interface.
Usage guidelines
Frame Relay IPHC statistics are displayed on a per-VC basis. An interface (main interface or subinterface) can have one or more VCs.
Examples
# Display RTP header compression statistics for the VC with DLCI 17 on interface Serial 2/1/0.
<Sysname> display fr compression iphc rtp interface serial 2/1/0 dlci 17
DLCI: 17, Serial2/1/0
Received:
Compressed/Error/Total: 0/0/0 packets
Sent:
Compressed/Total: 0/0 packets
Sent/Saved/Total: 0/0/0 bytes
Packet-based compression ratio: 0%
Byte-based compression ratio: 0%
Connections:
Rx/Tx: 16/16
Five-Minute-Miss: 0 (Misses/5Mins)
Max-Miss: 0
# Display TCP header compression statistics for interface Serial 2/1/0.
<Sysname> display fr compression iphc tcp interface serial 2/1/0
DLCI: 16, Serial2/1/0
Received:
Compressed/Error/Total: 0/0/0 packets
Sent:
Compressed/Total: 0/0 packets
Sent/Saved/Total: 0/0/0 bytes
Packet-based compression ratio: 0%
Byte-based compression ratio: 0%
Connections:
Rx/Tx: 16/16
Five-Minute-Miss: 0 (Misses/5Mins)
Max-Miss: 0
DLCI: 17, Serial2/1/0
Received:
Compressed/Error/Total: 0/0/0 packets
Sent:
Compressed/Total: 0/0 packets
Sent/Saved/Total: 0/0/0 bytes
Packet-based compression ratio: 0%
Byte-based compression ratio: 0%
Connections:
Rx/Tx: 16/16
Five-Minute-Miss: 0 (Misses/5Mins)
Max-Miss: 0
Table 59 Command output
Field |
Description |
Statistics on received packets: · Compressed—Number of compressed packets. · Error—Number of error packets. · Total—Total number of packets. |
|
Statistics on sent packets: · Compressed—Number of compressed packets. · Total—Total number of packets. · Sent—Actual number of bytes sent. · Saved—Number of bytes reduced due to the compression. · Total—Number of bytes that need to be sent if no compression is performed. · Packet-based compression ratio—Ratio of compressed packets to the total number of packets (Compressed/Total x 100%). · Byte-based compression ratio—Ratio of saved bytes to the total number of bytes (Saved/Total x 100%). |
|
Statistics on sent packets: · Rx—Maximum number of decompression connections when the device acts as the receiving end. · Tx—Maximum number of compression connections when the device acts as the transmitting end. · Five-Minute-Miss—Number of times an entry failed to be found over the most recent 5 minutes. · Max-Miss—Maximum number of times an entry failed to be found. |
Related commands
fr compression iphc enable
reset fr compression iphc
display fr compression stac
Use display fr compression stac to display statistics for Frame Relay STAC compression.
Syntax
display fr compression stac [ interface interface-type interface-number [ dlci dlci-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays STAC compression statistics for the main interface and its subinterfaces. If you specify a subinterface, this command displays STAC compression statistics for the subinterface. If you do not specify an interface, this command displays STAC compression statistics for all interfaces.
dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007.
· If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not display STAC compression statistics for the VC.
· If you specify a subinterface and a VC that is not on the subinterface, this command does not display STAC compression statistics for the VC.
· If you specify only an interface, this command displays STAC compression statistics for all VCs on the interface.
Usage guidelines
Frame Relay STAC compression statistics are displayed on a per-VC basis. An interface (main interface or subinterface) can have one or more VCs.
Examples
# Display Frame Relay STAC compression statistics for all interfaces.
<Sysname> display fr compression stac
Serial2/1/0
DLCI: 22
Uncompressed bytes sent/received: 0/0
Compressed bytes sent/received: 0/0
1 min avg ratio output/input: 0.000/0.000
5 min avg ratio output/input: 0.000/0.000
Table 60 Command output
Field |
Description |
Uncompressed bytes sent/received |
Number of sent/received bytes before compression. |
Compressed bytes sent/received |
Number of bytes sent/received after compression. |
1 min avg ratio output/input |
Average ratio of bytes after compression to bytes before compression for every second over the last 1 minute (sent/received). |
5 min avg ratio output/input |
Average ratio of bytes after compression to bytes before compression for every minute over the last 5 minutes (sent/received). |
display fr fragment
Use display fr fragment to display statistics for Frame Relay FRF.12 fragmentation.
Syntax
display fr fragment [ interface interface-type interface-number [ dlci dlci-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays FRF.12 fragmentation statistics for the main interface and its subinterfaces. If you specify a subinterface, this command displays FRF.12 fragmentation statistics for the subinterface. If you do not specify an interface, this command displays FRF.12 fragmentation statistics for all interfaces.
dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007.
· If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not display FRF.12 fragmentation statistics for the VC.
· If you specify a subinterface and a VC that is not on the subinterface, this command does not display FRF.12 fragmentation compression statistics for the VC.
· If you specify only an interface, this command displays FRF.12 fragmentation statistics for all VCs on the interface.
Examples
# Display Frame Relay FRF.12 fragmentation statistics for all interfaces.
<Sysname> display fr fragment
Interface Serial2/1/0:
DLCI Interface Type Size (byte) In/Out/Dropped
200 Serial2/1/0 FRF12(end-to-end) 80 0/0/0
# Display FRF.12 fragmentation statistics for the VC with DLCI 200 on interface Serial 2/1/0.
<Sysname> display fr fragment interface serial2/1/0 dlci 200
Type: FRF12(end-to-end)
Size: 80 bytes
Pre-fragment:
Output: 0 packets, 0 bytes
Fragmented:
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
Assembled:
Input: 0 packets, 0 bytes
Dropped:
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
Out-of-sequence packets: 0
Table 61 Command output
Field |
Description |
Size (byte) |
Fragment size in bytes. |
In/Out/Dropped |
Numbers of fragments received/sent/dropped. |
Size |
Fragment size in bytes. |
Pre-fragment |
Number of packets to be fragmented. |
Fragmented |
Number of fragments. |
Assembled |
Number of fragments reassembled. |
Dropped |
Number of fragments dropped. |
Out-of-sequence packets |
Number of out-of-sequence fragments. |
Output: 0 packets, 0 bytes |
Number of packets or fragments sent, and number of bytes sent. |
Input: 0 packets, 0 bytes |
Number of fragments received, and number of bytes received. |
display fr inarp
Use display fr inarp to display statistics for Frame Relay InARP packets.
Syntax
display fr inarp [ interface interface-type interface-number ]
Views
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays statistics for the main interface and its subinterfaces. If you specify a subinterface, this command displays statistics for the subinterface. If you do not specify an interface, this command displays statistics for all interfaces.
Usage guidelines
You can determine whether Frame Relay InARP is operating correctly based on the output from this command.
Examples
# Display statistics for Frame Relay InARP packets.
Frame relay InARP statistics for interface Serial2/1/0 (DTE)
Recvd InARP request Sent InARP reply Sent InARP request Recvd InARP reply
0 0 1 1
Table 62 Command output
Field |
Description |
Recvd InARP request |
Number of received InARP requests. |
Sent InARP reply |
Number of sent InARP replies. |
Sent InARP request |
Number of sent InARP requests. |
Recvd InARP reply |
Number of received InARP replies. |
fr inarp
display fr ipv6 map
Use display fr ipv6 map to display Frame Relay IPv6 address mapping.
Syntax
display fr ipv6 map [ static | dynamic ] [ interface interface-type interface-number [ dlci dlci-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
static: Specifies static address mapping.
dynamic: Specifies dynamic address mapping.
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays IPv6 address mapping for the main interface and its subinterfaces. If you specify a subinterface, this command displays IPv6 address mapping for the subinterface. If you do not specify an interface, this command displays IPv6 address mapping for all interfaces.
dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007.
· If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not display IPv6 address mapping for the VC.
· If you specify a subinterface and a VC that is not on the subinterface, this command does not display IPv6 address mapping for the VC.
· If you specify only an interface, this command displays IPv6 address mapping for all VCs on the interface.
Usage guidelines
If you do not specify the static or dynamic keyword, this command displays both static and dynamic address mapping.
Examples
# Display Frame Relay IPv6 address mapping.
<Sysname> display fr ipv6 map
Map statistics for interface Serial2/1/0 (DTE)
DLCI: 100 IPv6 IND: FE80::56FF:FE00:0 Interface: Serial2/1/0
Create time: 2014/10/11 09:57:28 Status: Active
Encapsulation: IETF Broadcast
DLCI: 100 IPv6 IND: 10::1 Interface: Serial2/1/0
Create time: 2014/10/11 09:57:28 Status: Active
Encapsulation: IETF Broadcast
DLCI: 100 IPv6: 10::3 Interface: Serial2/1/0
Create time: 2014/10/11 09:57:28 Status: Active
Encapsulation: IETF Broadcast
Table 63 Command output
Field |
Description |
Map Statistics for interface Serial2/1/0 (DTE) |
IPv6 address-to-DLCI maps for Serial 2/1/0 (a DTE interface). |
DLCI: 100 |
VC identified by the DLCI number. |
IPv6 IND 10::1 |
Address map established with the peer IPv6 address 10::1 through IND. If IND is absent, the address map is manually configured. |
Interface: Serial2/1/0 |
Interface where the VC was created. |
Create time: 2014/10/11 09:57:28 |
Time when the address map was created. |
Status: Active |
Status of the address map: Active or Inactive. |
Encapsulation: IETF |
Encapsulation type for the VC: IETF or Nonstandard. |
Broadcast |
Broadcast packets are allowed on the VC. |
display fr lmi
Use display fr lmi to display LMI information.
Syntax
display fr lmi [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies a main interface by its type and number. If you do not specify an interface, this command displays LMI information for all main interfaces.
Usage guidelines
The LMI protocol sends status enquiry messages and status messages for maintaining Frame Relay links. The output from the command helps you diagnose faults.
Examples
# Display LMI information for all interfaces.
Frame relay LMI information for interface Serial2/1/0 (DTE, Q933)
T391DTE: 10 seconds, N391DTE: 6, N392DTE: 3, N393DTE: 4
Sent status enquiry: 96, Received status: 85
Status timeout: 3, Discarded messages: 3
Frame relay LMI information for interface Serial2/1/0 (DCE, Q933)
T392DCE: 15 seconds, N392DCE: 3, N393DCE: 4
Received status enquiry: 0, Sent status: 0
Status enquiry timeout: 0, Discarded messages: 0
Table 64 Command output
Field |
Description |
Frame relay LMI information for interface Serial2/1/0 (DTE, Q933) |
Serial 2/1/0 (a Frame Relay interface) is a DTE interface that complies with Q.933 Annex A. |
T391DTE: 10 seconds, N391DTE: 6, N392DTE: 3, N393DTE: 4 |
DTE-side T391 timer (in seconds) configured by using the timer-hold command, N391 counter, N392 counter, and N393 counter. |
Sent status enquiry: 96, Received status: 85 |
Number of status enquiry messages sent out of the interface and number of status messages received on the interface. |
Status timeout: 3, Discarded messages: 3 |
Number of status messages that timed out and number of discarded messages. |
Frame relay LMI information for interface Serial2/1/0 (DCE, Q933) |
Serial 2/1/0 (a Frame Relay interface) is a DCE interface that complies with Q.933 Annex A. |
T392DCE: 15 seconds, N392DCE: 3, N393DCE: 4 |
DCE-side T392, N392, and N393 values. |
Received status enquiry: 0, Sent status: 0 |
Number of status enquiry messages received on the interface and number of status messages sent out of the interface. |
Status enquiry timeout: 0, Discarded messages : 0 |
Number of status enquiry messages that timed out and number of discarded messages. |
Related commands
display fr map
Use display fr map to display Frame Relay address mapping.
Syntax
display fr map [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main or subinterface. If you specify a main interface, this command displays information for the main interface and its subinterfaces. If you specify a subinterface, this command displays information for the subinterface. If you do not specify an interface, this command displays information for all interfaces.
Usage guidelines
Based on the output from this command, you can determine whether the static address-to-DLCI maps are correct and whether dynamic address mapping is operating correctly.
Examples
# Display Frame Relay address mapping for all interfaces.
Map information for interface Serial2/1/0 (DTE)
DLCI: 100, IP InARP 100.100.1.1, Serial2/1/0
Creation time: 2012/10/21 14:48:44, Status: Active
DLCI: 200, IP InARP 100.100.1.1, Serial2/1/0
Creation time: 2012/10/21 14:34:42, Status: Active
DLCI: 300, IP 1.1.1.1, Serial2/1/0
Creation time: 2012/10/21 15:03:35, Status: Active
Table 65 Command output
Field |
Description |
Map information for interface Serial2/1/0 (DTE) |
Frame Relay address mapping for DTE interface Serial 2/1/0. |
DLCI: 100, IP InARP 100.100.1.1, Serial2/1/0 |
The VC identified by DLCI 100 is mapped to the peer IP address 100.100.1.1 through InARP. The VC is configured on the interface Serial 2/1/0. If the InARP keyword is not displayed, the address-to-DLCI map is a static map manually configured. |
Creation time: 2012/10/21 14:48:44 |
Time when the map was created. |
State of the address-to-DLCI map: · Active. · Inactive. The state of an address-to-DLCI map is the same as the state of the mapped VC. |
fr inarp
fr map ip
display fr pvc
Use display fr pvc to display information on Frame Relay PVCs and statistics about sent and received data.
Syntax
display fr pvc [ interface interface-type interface-number ] [ dlci dlci-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command displays information for the main interface and its subinterfaces. If you specify a subinterface, this command displays information for the subinterface. If you do not specify an interface, this command displays information for all interfaces.
dlci dlci-number: Specifies a PVC by its DLCI in the range of 16 to 1007. If you specify a PVC, this command displays detailed information about the PVC. If you do not specify a PVC, this command displays brief information about PVCs. In addition to the brief information, the detailed information includes Frame Relay traffic management information.
Examples
# Display brief information on all Frame Relay PVCs and statistics about sent and received data.
PVC information for interface Serial2/1/0 (DTE, physically up)
DLCI: 100 Type: Dynamic Interface: Serial2/1/0
Encapsulation: IETF Broadcast
Creation time: 2012/04/01 23:55:39 Status: Active
Input: 0 packets, 0 bytes, 0 dropped
Output: 0 packets, 0 bytes, 0 dropped
DLCI: 102 Type: Static Interface: Serial2/1/0.1
Encapsulation: Nonstandard
Creation time: 2012/04/01 23:56:14 Status: Active
Input: 0 packets, 0 bytes, 0 dropped
Output: 0 packets, 0 bytes, 0 dropped
# Display detailed information on the PVC identified by DLCI 100 and statistics about data sent and received on the PVC.
<Sysname> display fr pvc dlci 100
PVC information for interface Serial2/1/0 (DTE, physically up)
DLCI: 100 Type: Dynamic Interface: Serial2/1/0
Encapsulation: IETF Broadcast
Creation time: 2012/04/01 23:55:39 Status: Active
Input: 0 packets, 0 bytes, 0 dropped
Output: 0 packets, 0 bytes, 0 dropped
DE list: 3 DE set packets: 0
Traffic policing: Active
CIR ALLOW: 56000 bps CBS: 56000 bits EBS: 56000 bits
Input: 0 packets, 0 bytes, 0 dropped, 0 set DE packets
Traffic shaping: Inactive
CIR ALLOW: 56000 bps CIR: 56000 bps
CBS: 56000 bits EBS: 56000 bits
Current CIR: 56000 bps
Output: 0 packets, 0 bytes, 0 dropped packets
Delayed: 0 packets, 0 bytes
Output queue: (Urgent queuing: Size/Length/Discards) 0/100/0
Output queue: (Protocol queuing: Size/Length/Discards) 0/500/0
Output queue: (FIFO queuing: Size/Length/Discards) 0/75/0
Table 66 Command output
Field |
Description |
PVC information for interface Serial2/1/0 (DTE, physically up) |
Information about PVCs on the Frame Relay interface Serial 2/1/0. The interface is a DTE interface and is physically up. The interface types include: · DTE. · DCE. The physical states include: · physically up. · physically down. |
DLCI: 100, Type: Dynamic, Interface: Serial2/1/0 |
The type of the PVC identified by DLCI 100 is Dynamic. It is created on interface Serial 2/1/0. The PVC types include: · Dynamic—The PVC is dynamically learned through LMI. · Static—The PVC is statically configured by using the fr map ip or fr dlci command. |
The encapsulation type of the PVC is IETF. The PVC allows broadcast packets. The encapsulation types include: · IETF. · Nonstandard. |
|
Time when the PVC was created and the state of the PVC, which can be Active or Inactive. |
|
Number of received packets, number of received bytes, and number of dropped packets. |
|
Number of sent packets, number of sent bytes, and number of dropped packets. |
|
DE list number and number of packets with the DE bit set. |
|
Status of traffic policing: · Active. · Inactive. |
|
Number of received packets, number of received bytes, number of dropped packets, and number of packets with the DE bit set. |
|
Status of traffic shaping: · Active. · Inactive. |
|
Number of sent packets, number of sent bytes, and number of dropped packets after traffic shaping is enabled. |
|
Number of outgoing packets delayed and number of outgoing bytes delayed. |
broadcast
fr dlci
fr encapsulation
fr interface-type
fr map ip
reset fr pvc
fr compression iphc enable
Use fr compression iphc enable to enable Frame Relay IPHC on a Frame Relay interface or VC.
Use undo fr compression iphc enable to disable Frame Relay IPHC on a Frame Relay interface or VC.
Syntax
fr compression iphc enable [ nonstandard ]
undo fr compression iphc enable
Default
Frame Relay IPHC is disabled.
Views
Interface view
Frame Relay virtual circuit view
Predefined user roles
network-admin
Parameters
nonstandard: Specifies the nonstandard encapsulation type. Specify this keyword when the device is interoperating with third-party devices. This keyword supports RTP header compression (but not TCP header compression).
Usage guidelines
IPHC includes the following types:
· RTP header compression—Compresses the IP/UDP/RTP header in packets.
· TCP header compression—Compresses the TCP/IP header in packets.
Enabling/disabling IPHC enables/disables both RTP header compression and TCP header compression.
To make IPHC take effect on a link, you must enable Frame Relay IPHC on both ends of the link.
You can configure Frame Relay IPHC on either an interface or VC. The setting on an interface takes effect on all VCs of the interface. The setting on a VC takes effect only on the VC. When the interface setting is different from the VC setting, the VC setting takes effect.
When the encapsulation type is IETF, IPHC negotiation is triggered after you enable IPHC. IPHC takes effect only if IPHC negotiation succeeds.
When the encapsulation type is nonstandard, IPHC takes effect without negotiation. In this case, the encapsulation type must be nonstandard on both ends of the link.
Compression does not stop after you disable IPHC. To stop compression on an interface or PVC, you must also execute the shutdown/undo shutdown command sequence on the interface or PVC.
Examples
# Enable Frame Relay IPHC on interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr compression iphc enable
# Enable Frame Relay IPHC on the VC with DLCI 100 on interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr dlci 100
[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc enable
Related commands
fr encapsulation
fr compression iphc rtp-connections
Use fr compression iphc rtp-connections to set the maximum number of RTP header-compression connections allowed on a Frame Relay interface or VC.
Use undo fr compression iphc rtp-connections to restore the default.
Syntax
fr compression iphc rtp-connections number
undo fr compression iphc rtp-connections
Default
The maximum number of RTP header-compression connections is 16.
Views
Interface view
Frame Relay virtual circuit view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of RTP header-compression connections allowed, in the range of 3 to 1000. When this argument is less than or equal to 256, packets are compressed in COMPRESSED_RTP_8 format. When this argument is greater than 256, packets are compressed in COMPRESSED_RTP_16 format.
Usage guidelines
RTP is a connection-oriented protocol and can carry many RTP connections on one link. The compression algorithm maintains information for each RTP header-compression connection. To save memory resources, you can use this command to specify the maximum number of RTP header-compression connections allowed. For example, if you specify the maximum number as 3, packets of the fourth RTP connection are not compressed.
The maximum number of RTP header-compression connections configured on an interface is inherited by all VCs of the interface. If you set a different maximum number on a VC of the interface, the setting on the VC takes effect.
You can configure this command on an interface or PVC only after you enable IPHC on the interface or PVC. The configuration takes effect on an interface or PVC after you execute the shutdown/undo shutdown command sequence on the interface or PVC. After you disable IPHC, the configuration is deleted.
Examples
# Set the maximum number of RTP header-compression connections to 200 for interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr compression iphc enable
[Sysname-Serial2/1/0] fr compression iphc rtp-connections 200
# Set the maximum number of RTP header-compression connections to 200 for the VC with DLCI 100 on interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr dlci 100
[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc enable
[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc rtp-connections 200
Related commands
fr compression iphc enable
fr compression iphc tcp-connections
Use fr compression iphc tcp-connections to set the maximum number of TCP header-compression connections allowed on a Frame Relay interface or VC.
Use undo fr compression iphc tcp-connections to restore the default.
Syntax
fr compression iphc tcp-connections number
undo fr compression iphc tcp-connections
Default
The maximum number of TCP header-compression connections is 16.
Views
Interface view
Frame Relay virtual circuit view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of TCP header-compression connections allowed, in the range of 3 to 256.
Usage guidelines
TCP is a connection-oriented protocol and can carry many TCP connections on one link. The compression algorithm maintains information for each TCP header-compression connection. To save memory resources, you can use this command to specify the maximum number of TCP header-compression connections allowed. For example, if you specify the maximum number as 3, packets of the fourth TCP connection are not compressed.
The maximum number of TCP header-compression connections configured on an interface is inherited by all VCs of the interface. If you set a different maximum number on a VC of the interface, the setting on the VC takes effect.
You can configure this command on an interface or PVC only after you enable IPHC without specifying the nonstandard keyword on the interface or PVC. The configuration takes effect on an interface or PVC after you execute the shutdown/undo shutdown command sequence on the interface or PVC. After you disable IPHC or re-enable IPHC with the nonstandard keyword, the configuration is deleted.
Examples
# Set the maximum number of TCP header-compression connections to 200 for interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr compression iphc enable
[Sysname-Serial2/1/0] fr compression iphc tcp-connections 200
# Set the maximum number of TCP header-compression connections to 200 for the VC with DLCI 100 on interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr dlci 100
[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc enable
[Sysname-fr-dlci-Serial2/1/0-100] fr compression iphc tcp-connections 200
Related commands
fr compression iphc enable
fr compression stac enable
Use fr compression stac enable to enable Frame Relay STAC compression on a Frame Relay VC.
Use undo fr compression stac enable to disable Frame Relay STAC compression on a Frame Relay VC.
Syntax
fr compression stac enable
undo fr compression stac enable
Default
Frame Relay STAC compression is disabled on a Frame Relay VC.
Views
Frame Relay virtual circuit view
Predefined user roles
network-admin
Usage guidelines
To make STAC compression take effect on a PVC, you must enable STAC compression on both ends of the PVC.
STAC compression works only when the encapsulation type is IETF on both ends of a PVC. If the encapsulation type is not IETF when you enable STAC compression, the system automatically changes the encapsulation type to IETF.
Frame Relay IPHC and STAC compression are mutually exclusive.
Examples
# Enable Frame Relay STAC compression on the VC with DLCI 100 on interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr dlci 100
[Sysname-Serial2/1/0-fr-dlci-100]fr compression stac enable
fr dlci
Use fr dlci to create a VC and enter its view, or enter the view of an existing VC.
Use undo fr dlci to delete a VC.
Syntax
fr dlci dlci-number
undo fr dlci [ dlci-number ]
Default
No VCs exist.
Views
Interface view (main interface or subinterface view)
Predefined user roles
network-admin
Parameters
dlci-number: Specifies a VC by its DLCI in the range 16 to 1007. DLCIs 0 through 15 and 1008 through 1023 are reserved.
Usage guidelines
The undo form of this command deletes all VCs if you do not specify the dlci-number argument.
The DLCI of a VC must be unique on a main interface and all its subinterfaces.
On a main DCE interface or subinterface, you must manually create VCs.
On a main DTE interface, the device can automatically create VCs according to the settings received from the DCE side. If you create VCs manually, make sure the DLCIs of the VCs are the same as those used on the DCE side.
On a DTE subinterface, you must manually create VCs.
During LMI negotiation, the VC information of a DCE interface is transmitted. When too many VCs are configured on a DCE interface, the negotiation packet carrying the PVC information might exceed the maximum frame length allowed on the interface. In this case, the LMI negotiation fails.
Examples
# Create a VC with DLCI 100 on Frame Relay interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr dlci 100
[Sysname-Serial2/1/0-fr-dlci-100]
fr encapsulation
Use fr encapsulation to configure the encapsulation type for a Frame Relay interface or VC.
Use undo fr encapsulation to restore the default.
Syntax
fr encapsulation { ietf | nonstandard }
Frame Relay virtual circuit view
network-admin
Ietf: Specifies the IETF encapsulation type.
nonstandard: Specifies the nonstandard encapsulation type.
The Frame Relay encapsulation types include:
· IETF—The IETF encapsulation type conforms to RFC 1490.
· Nonstandard—The nonstandard encapsulation type is compatible with dedicated encapsulation types of mainstream routers.
If a VC is enabled with STAC compression, its encapsulation type can only be IETF.
When a Frame Relay interface is configured with an encapsulation type:
· The interface sends packets encapsulated in this type.
· The interface can recognize packets encapsulated in either type.
For the local end and the peer to communicate:
· If the peer can recognize packets in either type, you can set different encapsulation types on the two ends.
· If the peer cannot recognize packets in either type,, you must set the same encapsulation type on the two ends.
By default, a VC uses the encapsulation type configured on its Frame Relay interface. The encapsulation type configured for a VC takes precedence over the encapsulation type configured on its Frame Relay interface.
Examples
# Enable Frame Relay encapsulation on Serial 2/1/0, and set the encapsulation type to nonstandard.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr encapsulation nonstandard
# Set the Frame Relay encapsulation type to IETF on the VC with DLCI 200.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr dlci 200
[Sysname-Serial2/1/0-fr-dlci-200] fr encapsulation ietf
fr fragment enable
Use fr fragment enable to enable Frame Relay FRF.12 fragmentation on a Frame Relay interface.
Use undo fr fragment enable to disable Frame Relay FRF.12 fragmentation on a Frame Relay interface.
Syntax
fr fragment enable
undo fr fragment enable
Default
Frame Relay FRF.12 fragmentation is disabled on a Frame Relay interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command enables FRF.12 fragmentation on all PVCs of an interface and its subinterfaces.
FRF.12 fragmentation enabled by using this command is end-to-end type.
This command and the fr traffic-shaping command are mutually exclusive on an interface. For more information about Frame Relay traffic shaping, see ACL and QoS Configuration Guide.
Examples
# Enable Frame Relay FRF.12 fragmentation on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr fragment enable
fr fragment size
Use fr fragment size to set the fragment size allowed on a Frame Relay interface.
Use undo fr fragment size to restore the default.
Syntax
fr fragment size size
undo fr fragment size
Default
The fragment size allowed on a Frame Relay interface is 45 bytes.
Views
Interface view
Predefined user roles
network-admin
Parameters
size: Specifies the fragment size in the range of 16 to 1600 bytes.
Examples
# Set the fragment size to 300 bytes on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr fragment size 300
fr inarp
Use fr inarp to enable Frame Relay InARP on a Frame Relay interface.
Use undo fr inarp to disable Frame Relay InARP on a Frame Relay interface.
Syntax
fr inarp ip [ dlci-number ]
undo fr inarp ip [ dlci-number ]
Default
Frame Relay InARP is enabled on a Frame Relay interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
ip: Performs inverse address resolution for IPv4 addresses.
dlci-number: Specifies a VC by its DLCI number. The value range for this argument is 16 to 1007. If you do not specify a VC, all VCs on the interface and on all its subinterfaces are specified.
Usage guidelines
When Frame Relay sends data over an interface, the peer IP addresses must be mapped to the local DLCIs. The address-to-DLCI mapping can be configured automatically through InARP or manually.
If you enable or disable InARP on a Frame Relay interface without specifying a VC, InARP is enabled or disabled on the following VCs:
· All VCs on the Frame Relay interface.
· All VCs on each subinterface of the Frame Relay interface.
Examples
# Enable InARP on all VCs of the Frame Relay interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr inarp ip
Related commands
display fr inarp
fr inarp interval
fr inarp interval
Use fr inarp interval to set the InARP request interval during an InARP learning process.
Use undo fr inarp interval to restore the default.
fr inarp interval interval
The InARP request interval during an InARP learning process is 60 seconds.
network-admin
The InARP request interval takes effect only when InARP is enabled.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr inarp interval 15
Related commands
fr interface-type
Use fr interface-type to set the type of a Frame Relay interface.
Use undo fr interface-type to restore the default.
Syntax
fr interface-type { dce | dte }
undo fr interface-type
Default
The type of a Frame Relay interface is DTE.
Views
Interface view
Predefined user roles
network-admin
Parameters
dce: Specifies DCE.
dte: Specifies DTE.
Examples
# Set the type of the Frame Relay interface Serial 2/1/0 to DCE.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr interface-type dce
fr ipv6 ind
Use fr ipv6 ind to enable IND for dynamic address mapping on a Frame Relay interface.
Use undo fr ipv6 ind to disable IND for dynamic address mapping on a Frame Relay interface.
Syntax
fr ipv6 ind [ dlci-number ]
undo fr ipv6 ind [ dlci-number ]
Default
IND is disabled on a Frame Relay interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
dlci-number: Specifies a VC by its DLCI number in the range of 16 to 1007. If you do not specify a VC, all VCs on the interface and on all its subinterfaces are specified.
Usage guidelines
IND automatically creates IPv6 address-to-DLCI maps on an interface.
If you enable or disable IND on a Frame Relay interface without specifying a VC, IND is enabled or disabled on the following VCs:
· All VCs on the Frame Relay interface.
· All VCs on each subinterface of the Frame Relay interface.
Examples
# Enable IND for all VCs on interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr ipv6 ind
fr lmi n391dte
Use fr lmi n391dte to set the DTE-side N391 counter.
Use undo fr lmi n391dte to restore the default.
Syntax
fr lmi n391dte n391-value
undo fr lmi n391dte
Default
The DTE-side N391 counter is 6.
Views
Interface view
Predefined user roles
network-admin
Parameters
n391-value: Sets the DTE-side N391 counter in the range of 1 to 255.
Usage guidelines
This command is available on DTE interfaces.
A DTE sends status enquiry messages at an interval set by the T391 timer to a DCE. The status enquiry messages include link integrity verification enquiry messages and full status enquiry messages. The ratio of sent link integrity verification enquiry messages to sent full status enquiry messages is (N391–1):1.
Examples
# Set the type of Frame Relay interface Serial 2/1/0 to DTE. Set the N391 counter to 10.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dte
[Sysname-Serial2/1/0] fr lmi n391dte 10
fr lmi n392dce
Use fr lmi n392dce to set the DCE-side N392 counter.
Use undo fr lmi n392dce to restore the default.
Syntax
fr lmi n392dce n392-value
undo fr lmi n392dce
Default
The DCE-side N392 counter is 3.
Views
Interface view
Predefined user roles
network-admin
Parameters
n392-value: Sets the DCE-side N392 counter in the range of 1 to 10.
Usage guidelines
This command is available on DCE interfaces.
A DCE requires a DTE to send a status enquiry message at an interval set by the T392 timer. If the DCE has not received a status enquiry message when the T392 timer expires, the error counter on the DCE increments by one.
The N392 counter sets an error threshold for the total number of monitored events set by the N393 counter. If the number of errors during N393 events reaches N392, the DCE considers the physical link and all VCs unavailable and will not use them to forward packets.
N392 must be less than N393 on the DCE side.
Examples
# Set the type of Frame Relay interface Serial 2/1/0 to DCE. Set N392 to 5 and N393 to 6.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dce
[Sysname-Serial2/1/0] fr lmi n392dce 5
[Sysname-Serial2/1/0] fr lmi n393dce 6
fr lmi n392dte
Use fr lmi n392dte to set the DTE-side N392 counter.
Use undo fr lmi n392dte to restore the default.
Syntax
fr lmi n392dte n392-value
undo fr lmi n392dte
Default
The DTE-side N392 counter is 3.
Views
Interface view
Predefined user roles
network-admin
Parameters
n392-value: Sets the DTE-side N392 counter in the range of 1 to 10.
Usage guidelines
This command is available on DTE interfaces.
A DTE sends a status enquiry message at an interval to a DCE to request the link status. When the DCE receives a status enquiry message, the DCE immediately sends a status message. If the DTE has not received the status message when the T391 timer expires, the error counter on the DTE increments by one.
The N392 counter sets an error threshold for the total number of monitored events set by the N393 counter. If the number of errors during N393 events reaches N392, the DTE considers the physical link and all VCs unavailable and will not use them to forward packets.
N392 must be less than N393 on the DTE side.
Examples
# Set the type of Frame Relay interface Serial 2/1/0 to DTE. Set N392 to 5 and N393 to 6.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dte
[Sysname-Serial2/1/0] fr lmi n392dte 5
[Sysname-Serial2/1/0] fr lmi n393dte 6
fr lmi n393dce
Use fr lmi n393dce to set the DCE-side N393 counter.
Use undo fr lmi n393dce to restore the default.
Syntax
fr lmi n393dce n393-value
undo fr lmi n393dce
Default
The DCE-side N393 counter is 4.
Views
Interface view
Predefined user roles
network-admin
Parameters
n393-value: Sets the DCE-side N393 counter in the range of 1 to 10.
Usage guidelines
This command is available on DCE interfaces.
A DCE requires a DTE to send a status enquiry message at an interval set by the T392 timer. If the DCE has not received the status enquiry message when the T392 timer expires, the error counter on the DCE increments by one.
The N392 counter sets an error threshold for the total number of monitored events set by the N393 counter. If the number of errors during N393 events reaches N392, the DCE considers the physical link and all VCs unavailable and will not use them to forward packets.
N392 must be less than N393 on the DCE side.
Examples
# Set the type of Frame Relay interface Serial 2/1/0 to DCE. Set N392 to 5 and N393 to 6.
<Sysname> system-view
[Sysname] interface serial2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dce
[Sysname-Serial2/1/0] fr lmi n392dce 5
[Sysname-Serial2/1/0] fr lmi n393dce 6
fr lmi n393dte
Use fr lmi n393dte to set the DTE-side N393 counter.
Use undo fr lmi n393dte to restore the default.
Syntax
fr lmi n393dte n393-value
undo fr lmi n393dte
Default
The DTE-side N393 counter is 4.
Views
Interface view
Predefined user roles
network-admin
Parameters
n393-value: Sets the DTE-side N393 counter in the range of 1 to 10.
Usage guidelines
This command is available on DTE interfaces.
A DTE sends status enquiry messages at an interval to a DCE to request the link status. When the DCE receives a status enquiry message, the DCE immediately sends a status message. If the DTE has not received the status message when the T391 timer expires, the error counter on the DTE increments by one.
The N392 counter sets an error threshold for the total number of monitored events set by the N393 counter. If the number of errors during N393 events reaches N392, the DTE considers the physical link and all VCs unavailable and will not use them to forward packets.
N392 must be less than N393 on the DTE side.
Examples
# Set the type of Frame Relay interface Serial 2/1/0 to DTE. Set N392 to 5 and N393 to 6.
<Sysname> system-view
[Sysname] interface serial2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dte
[Sysname-Serial2/1/0] fr lmi n392dte 5
[Sysname-Serial2/1/0] fr lmi n393dte 6
fr lmi t392dce
Use fr lmi t392dce to set the DCE-side T392 timer.
Use undo fr lmi t392dce to restore the default.
Syntax
fr lmi t392dce t392-value
undo fr lmi t392dce
Default
The DCE-side T392 timer is 15 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
t392-value: Sets the DCE-side T392 timer in the range of 5 to 30 seconds.
Usage guidelines
This command is available on DCE interfaces.
The DCE-side T392 timer defines the longest period that a DCE can wait for a status enquiry message.
The DCE-side T392 timer must be greater than the DTE-side T391 timer set by using the timer-hold command.
Examples
# Set the type of Frame Relay interface Serial 2/1/0 to DCE. Set the T392 timer to 10 seconds.
<Sysname> system-view
[Sysname] interface serial2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dce
[Sysname-Serial2/1/0] fr lmi t392dce 10
fr lmi type
Use fr lmi type to configure the Frame Relay LMI protocol type.
Use undo fr lmi type to restore the default.
Syntax
fr lmi type { ansi | nonstandard | q933a }
undo fr lmi type
Default
The Frame Relay LMI protocol type is q933a.
Views
Interface view
Predefined user roles
network-admin
Parameters
ansi: Specifies the standard LMI protocol defined in ANSI T1.617 Annex D.
nonstandard: Specifies the nonstandard compatible LMI protocol.
q933a: Specifies the standard LMI protocol defined in Q.933 Annex A.
Usage guidelines
The LMI protocol maintains the Frame Relay PVC table. It can perform the following operations:
· Notifies the addition of a PVC.
· Detects the deletion of a PVC.
· Monitors PVC status changes.
· Verifies link integrity.
The system usually supports the following LMI protocols:
· ITU-T Q.933 Annex A.
· ANSI T1.617 Annex D.
· Nonstandard compatible LMI protocol.
Examples
# Configure the Frame Relay LMI type as nonstandard compatible protocol on Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr lmi type nonstandard
fr map
Use fr map to create a static address-to-DLCI map.
Use undo fr map to delete a static address-to-DLCI map.
Syntax
fr map ip { ip-address | default } dlci-number
fr map ipv6 { ipv6-address | default } dlci-number
undo fr map ip { ip-address | default } dlci-number
undo fr map ipv6 { ipv6-address | default } dlci-number
No static address-to-DLCI maps exist.
Views
Interface view (main interface view or P2MP subinterface view)
Predefined user roles
network-admin
Parameters
ip-address: Specifies the peer IPv4 address.
ipv6-address: Specifies the peer IPv6 address.
default: Creates a default address-to-DLCI map.
dlci-number: Specifies the local VC by its DLCI in the range of 16 to 1007. DLCIs 0 through 5 and 1008 through 1023 are reserved.
Usage guidelines
An address-to-DLCI map can be created automatically by using InARP or IND, or created manually.
· InARP or IND is suitable for a complex network where the peer devices also support InARP or IND.
· As a best practice, create address-to-DLCI maps manually when the number of peer hosts is small or when default routes exist.
The IPv4 or IPv6 address in an address-to-DLCI map must be a valid unicast IPv4 or IPv6 address.
When the VC specified in this command does not exist, the VC is automatically created.
Up to one default address-to-DLCI map can be configured on one interface.
Only one address-to-DLCI map can be configured for one IPv4 or IPv6 address on one interface.
Examples
# Create a static address-to-DLCI map on interface Serial 2/1/0 to map the VC with DLCI 50 to the peer IP address 202.38.163.252.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] fr map ip 202.38.163.252 50
Related commands
display fr map
fr ipv6 ind holdtime
Use fr ipv6 ind holdtime to set the IND request interval during the IND learning process.
Use undo fr ipv6 ind holdtime to restore the default.
Syntax
fr ipv6 ind holdtime seconds
undo fr ipv6 ind holdtime
Default
The IND request interval during the IND learning process is 30 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the IND request interval in the range of 10 to 120 seconds.
Usage guidelines
This command takes effect only when IND is enabled.
Examples
# Set the type of the Frame Relay interface Serial 2/1/0 to DTE, and set the IND request interval to 15 seconds for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dte
[Sysname-Serial2/1/0] ipv6 ind holdtime 15
fr ipv6 ind solicitation retrans-timer
Use fr ipv6 ind solicitation retrans-timer to set the interval between IND requests that are sent continuously.
Use undo fr ipv6 ind solicitation retrans-timer to restore the default.
Syntax
fr ipv6 ind solicitation retrans-timer seconds
undo fr ipv6 ind solicitation retrans-timer
Default
The interval between IND requests that are sent continuously is 1 second.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval between IND requests that are sent continuously, in the range of 1 to 5 seconds.
Usage guidelines
An interface that fails to receive IND responses within the IND request interval continuously sends IND requests up to three times at the interval set by using this command.
Examples
# Set the type of the Frame Relay interface Serial 2/1/0 to DTE, and set the interval between continuous IND requests to 2 seconds for Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dte
[Sysname-Serial2/1/0] ipv6 ind solicitation retrans-timer 2
link-protocol fr
Use link-protocol fr to enable Frame Relay encapsulation on an interface.
Use undo link-protocol to restore the default.
Syntax
undo link-protocol
Default
PPP encapsulation is enabled on all interfaces except Ethernet interfaces, VLAN interfaces, and ATM interfaces.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable Frame Relay encapsulation on interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
reset fr compression iphc
Use reset fr compression iphc to clear Frame Relay IPHC statistics.
Syntax
reset fr compression iphc { rtp | tcp } [ interface interface-type interface-number ] [ dlci dlci-number ]
Views
User view
Predefined user roles
network-admin
Parameters
rtp: Clears RTP header compression statistics.
tcp: Clears TCP header compression statistics.
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command clears IPHC statistics for all interfaces.
dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007. Before you specify a VC, you must specify an interface. If you do not specify a VC, this command clears IPHC statistics for all VCs on an interface.
Examples
# Clear IPHC statistics for all interfaces.
<Sysname> reset fr compression iphc
Related commands
display fr compression iphc
reset fr inarp
Use reset fr inarp to clear dynamic address-to-DLCI maps established by InARP.
Syntax
reset fr inarp [ interface interface-type interface-number [ dlci dlci-number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command clears information for the main interface and its subinterfaces. If you specify a subinterface, this command clears information for the subinterface. If you do not specify an interface, this command clears information for all interfaces.
dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007. DLCIs 0 through 15 and 1008 through 1023 are reserved. If you specify a VC, this command clears the dynamic address-to-DLCI map of the VC.
Usage guidelines
In some situations, for example, when the network topology changes, the dynamic address-to-DLCI maps will become invalid. Before dynamic address-to-DLCI maps are established again, clear all dynamic address-to-DLCI maps.
Examples
# Clear all dynamic IPv4 address-to-DLCI maps.
<Sysname> reset fr inarp
fr inarp
reset fr ipv6 ind
Use reset fr ipv6 ind to clear dynamic IPv6 address-to-DLCI maps.
Syntax
reset fr ipv6 ind [ interface interface-type interface-number [ dlci dlci-number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface.
· If you specify a main interface, this command clears information for the main interface and its subinterfaces.
· If you specify a subinterface, this command clears information for the subinterface.
· If you do not specify an interface, this command clears information for all interfaces.
dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007. DLCIs 0 through 15 and 1008 through 1023 are reserved.
· If you specify a main interface and a VC that is not on the main interface or any of its subinterfaces, this command does not clear IPv6 address mapping for the VC.
· If you specify a subinterface and a VC that is not on the subinterface, this command does not clear IPv6 address mapping for the VC.
· If you specify only an interface, this command clears IPv6 address mapping for all VCs on the interface.
Examples
# Clear all dynamic IPv6 address-to-DLCI maps.
<Sysname> reset fr ipv6 ind
reset fr pvc
Use reset fr pvc to clear statistics for PVCs.
Syntax
reset fr pvc [ interface interface-type interface-number [ dlci dlci-number ] ]
Views
User view
Predefined user roles
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. It can be a main interface or subinterface. If you specify a main interface, this command clears statistics for the main interface and its subinterfaces. If you specify a subinterface, this command clears statistics for the subinterface. If you do not specify an interface, this command clears statistics for all interfaces.
dlci dlci-number: Specifies a VC by its DLCI in the range of 16 to 1007. DLCIs 0 through 15 and 1008 through 1023 are reserved.
Examples
# Clear statistics for all PVCs on Serial 2/1/0.
<Sysname> reset fr pvc interface serial 2/1/0
snmp-agent trap enable fr
Use snmp-agent trap enable fr to enable SNMP notifications for Frame Relay.
Use undo snmp-agent trap enable fr to disable SNMP notifications for Frame Relay.
Syntax
snmp-agent trap enable fr
undo snmp-agent trap enable fr
Default
SNMP notifications are disabled for Frame Relay.
Views
System view
Predefined user roles
network-admin
Examples
# Disable SNMP notifications for Frame Relay.
<Sysname> system-view
[Sysname] undo snmp-agent trap enable fr
timer-hold
Use timer-hold to set the DTE-side T391 timer.
Use undo timer-hold to restore the default.
Syntax
timer-hold seconds
undo timer-hold
Default
The DTE-side T391 timer is 10 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the DTE-side T391 timer in the range of 0 to 32767 seconds. The value 0 indicates that the LMI protocol is disabled.
Usage guidelines
This command is available on DTE interfaces.
The DTE-side T391 timer defines the interval at which the DTE sends status enquiry messages.
The DTE-side T391 timer must be smaller than the DCE-side T392 timer.
Examples
# Set the type of Frame Relay interface Serial 2/1/0 to DTE. Set the T391 timer to 15 seconds.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol fr
[Sysname-Serial2/1/0] fr interface-type dte
[Sysname-Serial2/1/0] timer-hold 15
Multilink Frame Relay commands
This feature is supported only on Layer 2 Ethernet ports on the following modules:
· CE3.
· CPOS.
· CT3.
· E1.
· E1-F.
· POS.
· SAE.
· T1.
· T1-F.
bandwidth
Use bandwidth to set the expected bandwidth for an MFR interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth (in kbps) for an MFR interface is the interface baud rate divided by 1000.
Views
MFR interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth is an informational parameter used only by higher-layer protocols for calculation. You cannot adjust the actual bandwidth of an interface by using this command.
Examples
# Set the expected bandwidth to 1000 kbps for interface MFR 0/0/2.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] bandwidth 1000
default
Use default to restore the default settings for an MFR interface.
Syntax
default
Views
MFR 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 when you execute it on a live network. |
This command might fail to restore the default settings for some commands for reasons such as command dependencies or system restrictions. Use the display this command in interface view to identify these commands. Then use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to resolve the problem.
Examples
# Restore the default settings for interface MFR 0/0/2.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] default
description
Use description to set a description for an MFR interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of an MFR interface is interface name Interface, for example, MFR0/0/2 Interface.
Views
MFR interface view
Predefined user roles
network-admin
Parameters
text: Specifies an interface description, a case-sensitive string of 1 to 255 characters.
Examples
# Set the description to mfr0/0/2-interface for interface MFR 0/0/2.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] description mfr0/0/2-interface
display interface mfr
Use display interface mfr to display MFR interface information.
Syntax
display interface [ mfr [ interface-number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
mfr [ interface-number ]: Specifies MFR interfaces. If you do not specify the mfr keyword, this command displays information about all interfaces supported by the device. If you specify the mfr keyword but not the interface-number argument, this command displays information about all MFR interfaces.
brief: Displays brief information about interfaces. If you do not specify this keyword, the command displays detailed information about interfaces.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of each interface description.
down: Displays information about the interfaces in physically down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display detailed information about interface MFR 0/0/2.
<Sysname> display interface mfr 0/0/2
MFR0/0/2
Current state: DOWN
Line protocol state: DOWN
Description: MFR0/0/2 Interface
Maximum Transmit Unit: 1500
Hold timer: 10 seconds, retry times: 5
Internet protocol processing: Disabled
Link layer protocol is FR IETF
LMI DLCI is 0, LMI type is Q.933a, frame relay DTE
LMI status enquiry sent 0, LMI status received 0
LMI status timeout 0, LMI message discarded 0
Physical: MFR
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 dropps
Output: 0 packets, 0 bytes, 0 dropps
Table 67 Command output
Field |
Description |
Current state |
Physical state and administrative state of the MFR interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer state of the interface: · UP—The data link layer protocol is up. · DOWN—The data link layer protocol is down. |
Description |
Description of the MFR interface. |
Bandwidth |
Expected bandwidth of the MFR interface. |
Maximum Transmit Unit |
MTU of the MFR interface. |
Interval for the MFR interface to send keepalive messages. |
|
retry times |
Number of times that the interface sends a keepalive message. |
Internet protocol processing |
IP packet processing capability: · Enabled—The MFR interface can process IP packets. · Disabled—The MFR interface cannot process IP packets. |
Encapsulation type of the MFR interface: · IETF. · Nonstandard. |
|
DLCI number used by LMI, LMI type, and port type. Q.933a LMI and ANSI LMI use DLCI 0, and nonstandard LMI uses DLCI 1023. |
|
Number of sent status enquiry messages and number of received status messages. |
|
Number of status messages that timed out and number of discarded messages. |
|
Physical type of the interface. |
|
Output queue - Urgent queuing: Size/Length/Discards 0/100/0 Output queue - Protocol queuing: Size/Length/Discards 0/500/0 |
Statistics on the packets of the following interface output queues: · Urgent queue. · Protocol queue. · FIFO queue. |
Time when the interface statistics were last cleared. Never indicates that the interface statistics have never been cleared since device startup. |
|
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec |
Average input rate of the MFR interface in the last 5 minutes. Average output rate of the MFR interface in the last 5 minutes. |
Number of incoming packets, number of incoming bytes, and number of incoming packets discarded. |
|
Number of outgoing packets, number of outgoing bytes, and number of outgoing packets discarded. |
# Display brief information about interface MFR 0/0/2.
<Sysname> display interface mfr 0/0/2 brief
Brief information on interface(s) under route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Main IP Description
MFR0/0/2 DOWN DOWN --
# Display brief information about the MFR interfaces in physically down state.
<Sysname> display interface mfr brief down
Brief information on interface(s) under route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
MFR0/0/2 ADM Administratively
Table 68 Command output
Field |
Description |
Brief information about Layer 3 interfaces. |
|
Interface |
Interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface. |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces. |
|
Partial or complete interface description set by using the description command: · If you do not specify the description keyword for the display interface brief command, this field displays only the first 27 characters of the interface description. · If you specify the description keyword for the display interface brief command, this field displays the complete interface description. |
|
Cause |
Causes for the physical link state of an interface to be DOWN: · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. |
Related commands
display mfr
Use display mfr to display information about MFR bundles and bundle links.
Syntax
display mfr [ interface interface-type interface-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. The specified interface must be a main interface (MFR interface or physical interface).
verbose: Displays detailed information, including the number of control messages sent and received. If you do not specify this keyword, the command displays only configuration and status information.
Usage guidelines
If you specify an MFR interface without the verbose keyword, this command displays the configuration and status information for the specified bundle and all its bundle links.
If you specify a physical interface without the verbose keyword, this command displays the configuration and status information for the specified bundle link and its bundle.
If you specify an MFR interface with the verbose keyword, this command displays detailed information about the specified n MFR interface and all its bundle links.
If you specify a physical interface with the verbose keyword, this command displays detailed information about the specified bundle link and its bundle.
Examples
# Display the configuration and status information for all MFR bundles and bundle links.
Bundle interface: MFR0/0/2 Bundle state: Up Bundle class: A
Bundle name: MFR1 Peer bundle name: MFR2
Fragment: Enabled MFR bundle fragment size: 222 bytes
Original packets assembled/fragmented (input/output): 0/0
Dropped fragments (input/output): 0/0
Unassigned fragments: 0
Bundle links:
Serial2/1/0 Physical state: Up Link state: Up Link name: Serial2/1/0
Table 69 Command output
Field |
Description |
Operating state of the MFR interface: · Up—The interface is physically up. · Down—The interface is physically down. · Administratively down—The interface is administratively down. |
|
Bandwidth class, which is fixed at class A. A class A bundle is brought up when one or more bundle links come up. The bundle goes down when the last bundle link is down. |
|
Indicates whether fragmentation is enabled. |
|
Maximum fragment size allowed for bundle links. |
|
Number of assembled packets on the bundle interface and number of unfragmented packets before being sent by the MFR interface. |
|
Number of incoming/outgoing packets dropped on the MFR interface. |
|
Number of fragments that have not been assembled. |
|
Serial2/1/0 Physical state: Up Link state: Up Link name: Serial2/1/0 |
Information about a bundle link: · Physical layer state: ¡ Up. ¡ Down. ¡ Administratively down. · Link layer state: ¡ Add sent—The interface sent an Add_link message and started connection establishment. ¡ Ack rx—The interface received an Add_link acknowledgement and is expecting an Add_link message from the peer. ¡ Add rx—The interface received an Add_link message and is expecting an Add_link acknowledgement from the peer. ¡ Up—The bundle link was successfully negotiated, and the interface can send frames. ¡ Idle—The bundle link was removed. ¡ Down—The bundle link was physically down. ¡ Down idle—The bundle link was physically down and removed. · The bundle link name is the name of the physical interface by default. |
# Display detailed information about all MFR bundles and bundle links.
Bundle interface: MFR0/0/2 Bundle state: Up Bundle class: A
Bundle name: MFR1 Peer bundle name: MFR2
Fragment: Enabled MFR bundle fragment size: 222 bytes
Original packets assembled/fragmented (input/output): 0/0
Dropped fragments (input/output): 0/0
Unassigned fragments: 0
Bundle links:
Serial2/1/0
Link name: Serial2/1/0 Peer link name: Serial2/1/0
Physical state: Up Link state: Up Cause code: None
Timer: ACK 4 seconds Hello 10 seconds
Retry: Max 2 Current 0
Bundle link negotiation statistics:
Hello (Tx/Rx): 10/10 packets
Hello_ack (Tx/Rx): 10/10 packets
Add_link (Tx/Rx): 4/2 packets
Add_link_ack (Tx/Rx): 2/1 packets
Add_link_rej (Tx/Rx): 0/0 packets
Remove_link (Tx/Rx): 0/0 packets
Remove_link_ack (Tx/Rx): 0/0 packets
Packets dropped (input/output): 0/0
Bundle link fragment statistics:
MFR fragments(input/output): 0/0
Table 70 Command output
Field |
Description |
Physical state |
Operating state of the physical interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · Administratively down—The interface has been administratively shut down. |
Link state |
Operating state of the link protocol on the bundle link: · Add sent—The interface sent an Add_link message and started connection establishment. · Ack rx—The interface received an Add_link acknowledgement and is expecting an Add_link message from the peer. · Add rx—The interface received an Add_link message and is expecting an Add_link acknowledgement from the peer. · Up—The bundle link was successfully negotiated, and the interface can send frames. · Idle—The bundle link was removed. · Down—The bundle link was physically down. · Down idle—The bundle link was physically down and removed. |
Cause code for a bundle link state: · None—Initial state. · Ack timer expired—The ACK timer expires. · Bundle link idle—The bundle link is not operational. · Inconsistent bundle—Possible configuration mismatch detected. · Loopback detected—The bundle link has detected a potential loopback condition. · Unexpected add_link—An ADD_LINK message was received when the bundle link was in up state. · Other—Generic failure cause described by text in diagnostic element. |
|
Timer: Ack |
Amount of time for which the bundle link waits for a hello or Add_link acknowledgement before retransmitting a hello message or an Add_link message (for initial synchronization). |
Hello |
Interval for the bundle link to send hello messages. |
Retry: Max |
Maximum number of times that the bundle link can retransmit a hello or Add_link message before receiving a hello or Add_link acknowledgement. |
Current |
Number of retries that have been made. |
Number of hello messages sent/received. |
|
Number of hello acknowledgements sent/received. |
|
Number of Add_link acknowledgements sent/received. An Add_link acknowledgement notifies the peer that the local end received an Add_link message. |
|
Number of Add_link reject messages sent/received. An Add_link_rej message notifies the peer that the local end rejected an Add_link message. |
|
Number of Remove_link messages sent/received. A Remove_link message notifies that the local end is removing a bundle link from the bundle. |
|
Number of Remove_link acknowledgements sent/received. A Remove_link acknowledgement notifies the peer that the local end received a Remove_link message. |
|
Number of incoming/outgoing packets dropped. |
|
Number of fragments sent/received by the bundle link. |
Related commands
fr mfr
Use fr mfr to bind a physical interface to an MFR interface.
Use undo fr mfr to remove all physical interfaces from an MFR interface.
Syntax
fr mfr mfr interface-number
undo fr mfr
Default
A physical interface is not bound to any MFR interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
interface-number: Specifies an MFR interface by its number in the range of 0 to 1023.
Usage guidelines
Before configuring this command, make sure the physical interface is enabled with MFR encapsulation. A maximum of 16 physical interfaces can be bound to an MFR interface.
You can bind a physical interface to a nonexistent MFR interface. However, the binding takes effect only when the MFR interface is created. When a physical interface is removed from an MFR interface, MFR settings on the physical interface are not deleted.
To remove a physical interface from an MFR interface, you can also configure a different encapsulation type from MFR by using the link-protocol command.
After MFR encapsulation is enabled on a physical interface, the interface cannot be configured with any FR-related commands except MFR commands. In addition, the queuing type on the interface can be configured only as FIFO. If the interface uses another queuing type before you enable MFR encapsulation, the interface is forced to use FIFO after you enable MFR encapsulation.
Make sure a physical interface is on the same card as the MFR interface to which the interface is to be bound.
Examples
# Enable MFR encapsulation on Serial 2/1/0, and bind it to interface MFR 0/0/2.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol mfr
[Sysname-Serial2/1/0] fr mfr mfr 0/0/2
Related commands
link-protocol mfr
interface mfr
Use interface mfr to create an MFR interface or subinterface and enter its view, or enter the view of an existing MFR interface or subinterface.
Use undo interface mfr to delete an MFR interface or subinterface.
Syntax
interface mfr { interface-number | interface-number.subnumber [ p2mp | p2p ] }
undo interface mfr { interface-number | interface-number.subnumber }
Default
No MFR interface or subinterfaces exist.
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a number for the MFR interface.
interface-number.subnumber: Specifies a number for the MFR subinterface. The interface-number argument represents the number of the main MFR interface. The subnumber argument represents the number of the MFR subinterface. The value range for the subnumber argument is 0 to 1023.
p2mp: Specifies an MFR subinterface as a point-to-multipoint subinterface. By default, an MFR subinterface is a point-to-multipoint subinterface.
p2p: Specifies an MFR subinterface as a point-to-point subinterface.
Usage guidelines
Before creating an MFR subinterface, make sure the main MFR interface already exists.
An MFR interface is physically up when a minimum of one of its physical interfaces is up. An MFR interface is physically down when its last physical interface is down. The link layer state of an MFR interface is negotiated by using LMI messages.
Examples
# Create interface MFR 0/0/2, and create a point-to-multipoint subinterface.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] quit
[Sysname] interface mfr 0/0/2.1
[Sysname-MFR0/0/2.1]
link-protocol mfr
Use link-protocol mfr to enable MFR encapsulation on an interface.
Use undo link-protocol to restore the default.
Syntax
link-protocol mfr
undo link-protocol
Default
PPP encapsulation is enabled on all interfaces except Ethernet interfaces, VLAN interfaces, and ATM interfaces.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable MFR encapsulation on interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol mfr
Related commands
fr mfr
mfr bundle-name
Use mfr bundle-name to set a bundle name.
Use undo mfr bundle-name to restore the default.
Syntax
mfr bundle-name name
undo mfr bundle-name
Default
The bundle name is represented by MFR plus the bundle number, for example, MFR0/0/2.
Views
MFR interface view
Predefined user roles
network-admin
Parameters
name: Specifies a bundle name, a case-sensitive string of 1 to 49 characters.
Usage guidelines
You cannot set a bundle name as a string in the form of MFR + number.
Each MFR bundle has a bundle name, and the peer device can identify an MFR bundle by using the bundle name. Bundle names at the two ends of a bundle can be different. Bundle names must be unique on the same device.
The bundle names at both ends are used during the bundle link negotiation phase. After changing the bundle name of an MFR interface, you must execute the shutdown and undo shutdown commands on the interface to make the new bundle name take effect.
Examples
# Set the bundle name to bundle1 for interface MFR 0/0/2.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] mfr bundle-name bundle1
Related commands
display mfr
mfr fragment enable
Use mfr fragment enable to enable fragmentation on an MFR interface.
Use undo mfr fragment enable to disable fragmentation on an MFR interface.
Syntax
mfr fragment enable
undo mfr fragment enable
Default
Fragmentation is disabled on an MFR interface.
Views
MFR interface view
Predefined user roles
network-admin
Usage guidelines
With fragmentation enabled, an MFR interface fragments packets larger than the set fragment size and sends the fragments over bundle links in a round robin manner. The receiving end reassembles the fragments.
Examples
# Enable fragmentation on interface MFR 0/0/2.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] mfr fragment enable
Related commands
display mfr
mfr fragment size
Use mfr fragment size to set the maximum fragment size allowed on an MFR interface.
Use undo mfr fragment size to restore the default.
Syntax
mfr fragment size size
undo mfr fragment size
Default
The maximum fragment size allowed on an MFR interface is 300 bytes.
Views
MFR interface view
Predefined user roles
network-admin
Parameters
size: Specifies the fragment size in the range of 60 to 1500 bytes.
Usage guidelines
With fragmentation enabled, an MFR interface fragments packets larger than the set fragment size and sends the fragments over bundle links in a round robin manner. This reduces the transmission delay of real-time packets.
Examples
# Set the maximum fragment size allowed on interface MFR 0/0/2 to 70 bytes.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] mfr fragment-size 70
Related commands
display mfr
mfr timer lost-fragment
Use mfr timer lost-fragment to set the amount of time that an MFR interface waits for an expected fragment.
Use undo mfr timer lost-fragment to restore the default.
Syntax
mfr timer lost-fragment seconds
undo mfr timer lost-fragment
Default
An MFR interface waits for an expected fragment for 30 seconds before it declares the fragment lost.
Views
MFR interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies a value for the wait timer, in the range of 1 to 255 seconds.
Usage guidelines
The receiving end buffers the fragments of a packet before receiving all fragments of the packet. If any fragments are missing, the received fragments stay in the buffer. This processing wastes buffer resources.
The wait timer starts when the receiving end receives the first fragment of a packet. When the wait timer expires, the receiving end checks whether all fragments are received. If not all fragments are received, the receiving end discards all received fragments of the packet to release buffer resources.
Examples
# Set the wait time to 20 seconds for interface MFR 0/0/2.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] mfr timer lost-fragment 20
Related commands
mfr fragment enable
mfr link-name
Use mfr link-name to set the bundle link name for a Frame Relay interface.
Use undo mfr link-name to restore the default.
Syntax
mfr link-name name
undo mfr link-name
Default
The bundle link name is the name of the physical interface, for example, Serial 2/1/0.
Views
Frame Relay interface view
Predefined user roles
network-admin
Parameters
name: Specifies the bundle link name, a case-sensitive string of 1 to 49 characters.
Usage guidelines
Use link-protocol mfr to enable MFR encapsulation on a Frame Relay interface before configuring the mfr link-name command on the interface.
The bundle link name identifies the bundle link to the peer device and enables the local device to determine which bundle links are bound to which bundles. The bundle link names in a bundle must be unique on the same device. The local and peer bundle link names can be different.
The local and peer bundle link names are used during the bundle link negotiation phase. After changing the bundle link name on an interface, you must execute the shutdown and undo shutdown commands on the interface to make the new bundle link name take effect.
Examples
# Set the bundle link name to bl1 for interface Serial 2/1/0.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol mfr
[Sysname-Serial2/1/0] mfr link-name bl1
Related commands
link-protocol mfr
mfr retry
Use mfr retry to set the maximum number of times that a bundle link can resend a hello message when waiting for a hello acknowledgement.
Use undo mfr retry to restore the default.
Syntax
mfr retry retries
undo mfr retry
Default
The maximum number of retries is 2.
Views
Frame Relay interface view
Predefined user roles
network-admin
Parameters
retries: Specifies the maximum number of retries, in the range 1 to 5.
Usage guidelines
A bundle link maintains link status by periodically sending hello messages to its peer end. If the bundle link sends a hello message but does not receive a hello acknowledgement, it will resend the hello message. If the bundle link still receives no acknowledgements after the maximum number of retries is reached, the system determines that the line protocol on the bundle link is down.
Before configuring this command, make sure you have used the link-protocol mfr command to enable MFR encapsulation on the Frame Relay interface.
Examples
# Set the maximum number of retries to 3 for interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol mfr
[Sysname-Serial2/1/0] mfr retry 3
Related commands
link-protocol mfr
mfr timer ack
mfr timer hello
mfr timer ack
Use mfr timer ack to set the amount of time that a bundle link waits for a hello acknowledgment before resending the hello message.
Use undo mfr timer ack to restore the default.
Syntax
mfr timer ack seconds
undo mfr timer ack
Default
The wait time for a hello acknowledgment is 4 seconds.
Views
Frame Relay interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the wait time in the range 1 to 10 seconds.
Usage guidelines
A bundle link maintains link status by periodically sending hello messages to its peer end. If the bundle link sends a hello message but does not receive a hello acknowledgement, it will resend the hello message. If the bundle link still receives no acknowledgements after the maximum number of retries is reached, the system determines that the line protocol on the bundle link is down.
Before configuring this command, make sure you have used the link-protocol mfr command to enable MFR encapsulation on the Frame Relay interface.
Examples
# Set the wait time to 6 seconds for interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol mfr
[Sysname-Serial2/1/0] mfr timer ack 6
link-protocol mfr
mfr timer hello
mfr retry
mfr timer hello
Use mfr timer hello to set the interval at which a bundle link sends hello messages.
Use undo mfr timer hello to restore the default.
Syntax
mfr timer hello seconds
undo mfr timer hello
Default
A bundle link sends hello messages at the interval of 10 seconds.
Views
Frame Relay interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval in the range 1 to 180 seconds.
Usage guidelines
Before configuring this command, make sure you have used the link-protocol fr mfr command to enable MFR encapsulation on the Frame Relay interface.
Examples
# Configure interface Serial 2/1/0 to send a hello message every 15 seconds.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] link-protocol mfr
[Sysname-Serial2/1/0] mfr timer hello 15
Related commands
link-protocol mfr
mfr retry
mfr timer ack
mfr window-size
Use mfr window-size to set the maximum number of fragments that can be held by the window used in the sliding window algorithm when an MFR interface reassembles received fragments.
Use undo mfr window-size to restore the default.
Syntax
mfr window-size number
undo mfr window-size
Default
The sliding window size is the number of physical interfaces in an MFR bundle.
Views
MFR interface view
Predefined user roles
network-admin
Parameters
number: Specifies the sliding window size in the range 1 to 16.
Examples
# Set the sliding window size to 8 for interface MFR 0/0/2.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] mfr window-size 8
Related commands
fr mfr
reset counters interface
Use reset counters interface to clear statistics for MFR interfaces.
Syntax
reset counters interface [ mfr [ interface-number | interface-number.subnumber ] ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-number: Specifies an MFR interface by its number.
interface-number.subnumber: Specifies a number for the MFR subinterface. The interface-number argument represents the number of the main MFR interface. The subnumber argument represents the number of the MFR subinterface. The value range for the subnumber argument is 0 to 1023.
Usage guidelines
Use this command to clear history statistics before you collect traffic statistics for a time period.
· If you do not specify the mfr keyword, this command clears statistics for all interfaces.
· If you specify the mfr keyword but without the interface-number or interface-number.subnumber argument, this command clears statistics for all MFR interfaces or subinterfaces.
Examples
# Clear statistics for interface MFR 0/0/2.
<Sysname> reset counters interface mfr 0/0/2
shutdown
Use shutdown to shut down an MFR interface.
Use undo shutdown to restore the default.
Syntax
shutdown
undo shutdown
Default
An MFR interface is up.
Views
MFR interface view
Predefined user roles
network-admin
Examples
# Shut down interface MFR 0/0/2.
<Sysname> system-view
[Sysname] interface mfr 0/0/2
[Sysname-MFR0/0/2] shutdown
allow l2tp,96
apn,271
apn-profile,271
apn-profile apply,272
attach-format imsi-sn split,273
authentication-mode,273
bandwidth,286
bandwidth,97
bandwidth,274
bandwidth,195
bandwidth,353
bandwidth,34
bandwidth,138
broadcast,195
broadcast,319
bundle id,138
bundle load-balance,139
bundle max-active links,140
bundle member-priority,140
bundle min-active bandwidth,141
bundle min-active links,141
controller cellular,239
country-code,231
default,196
default,142
default,35
default,98
default,287
default,275
default,353
description,354
description,275
description,287
description,239
description,197
description,143
description,35
description,98
dialer bundle enable,288
dialer bundle-member,288
dialer callback-center,289
dialer call-in,290
dialer circular enable,291
dialer circular-group,292
dialer diagnose,90
dialer disconnect,293
dialer flow-interval,293
dialer number,294
dialer peer-name,295
dialer priority,295
dialer queue-length,296
dialer route,297
dialer threshold,298
dialer timer autodial,299
dialer timer compete,300
dialer timer enable,300
dialer timer idle,301
dialer timer wait-carrier,302
dialer timer warmup,302
dialer-group,303
dialer-group rule,304
display atm map-info,197
display atm pvc-group,199
display atm pvc-info,203
display bundle hdlc-bundle,143
display cellular,240
display controller cellular,251
display dialer,305
display fr compression iphc,319
display fr compression stac,322
display fr fragment,323
display fr inarp,324
display fr ipv6 map,325
display fr lmi,326
display fr map,328
display fr pvc,329
display interface dialer,306
display interface eth-channel,276
display interface hdlc-bundle,145
display interface mfr,355
display interface mp-group,36
display interface virtual-access,39
display interface virtual-ethernet,206
display interface virtual-ppp,99
display interface virtual-template,42
display ip pool,1
display isdn active-channel,155
display isdn call-info,156
display isdn call-record,159
display isdn parameters,160
display isdn spid,161
display l2tp session,102
display l2tp session temporary,103
display l2tp tunnel,104
display l2tp va-pool,105
display mfr,358
display ppp access-user,3
display ppp compression iphc,8
display ppp mp,44
display pppoe-client session packet,91
display pppoe-client session summary,92
display pppoe-server session packet,66
display pppoe-server session summary,68
display pppoe-server throttled-mac,70
display pppoe-server va-pool,71
dm-port open,252
encapsulation,209
eth-channel,279
fr compression iphc enable,331
fr compression iphc rtp-connections,332
fr compression iphc tcp-connections,333
fr compression stac enable,335
fr dlci,335
fr encapsulation,336
fr fragment enable,337
fr fragment size,338
fr inarp,338
fr inarp interval,339
fr interface-type,340
fr ipv6 ind,340
fr ipv6 ind holdtime,347
fr ipv6 ind solicitation retrans-timer,348
fr lmi n391dte,341
fr lmi n392dce,342
fr lmi n392dte,342
fr lmi n393dce,343
fr lmi n393dte,344
fr lmi t392dce,345
fr lmi type,346
fr map,346
fr mfr,361
gsm band,266
imsi bind,280
interface dialer,309
interface eth-channel,281
interface hdlc-bundle,149
interface mfr,362
interface mp-group,45
interface virtual-ethernet,210
interface virtual-ppp,105
interface virtual-template,46
ip address cellular-alloc,281
ip address ppp-negotiate,9
ip dscp,106
ip pool,10
ip pool gateway,11
ipv6 address cellular-alloc,282
isdn bch-local-manage,163
isdn bch-select-way,164
isdn bri-slipwnd-size,165
isdn caller-number,166
isdn calling,166
isdn carry calling-name,167
isdn carry connected-name,168
isdn check-called-number,168
isdn crlength,169
isdn ignore connect-ack,170
isdn ignore hlc,171
isdn ignore llc,171
isdn ignore sending-complete,172
isdn l3-timer,173
isdn leased-line,174
isdn link-mode p2p,175
isdn number-property,175
isdn overlap-sending,180
isdn pri-slipwnd-size,181
isdn progress-indicator,182
isdn progress-to-alerting enable,183
isdn protocol-mode,183
isdn protocol-type,184
isdn q921-permanent,185
isdn spid auto-trigger,186
isdn spid nit,187
isdn spid resend,187
isdn spid service,188
isdn spid timer,189
isdn spid1,190
isdn spid2,191
isdn two-tei,191
l2tp enable,106
l2tp tsa-id,107
l2tp virtual-template va-pool,108
l2tp-auto-client,109
l2tp-group,109
link-protocol fr,349
link-protocol hdlc,134
link-protocol mfr,363
link-protocol ppp,12
lns-ip,110
lte band,283
mac-address,210
mandatory-chap,111
mandatory-lcp,112
map bridge,211
map ip,212
map ppp,213
mfr bundle-name,363
mfr fragment enable,364
mfr fragment size,365
mfr link-name,366
mfr retry,367
mfr timer ack,368
mfr timer hello,369
mfr timer lost-fragment,365
mfr window-size,369
mode,253
modem answer-timer,232
modem auto-answer,233
modem callback,233
modem caller-number resolve,234
modem enable,235
modem reboot,254
modem response,254
mtu,113
mtu,149
mtu,283
mtu,309
mtu,47
mtu,214
nas-port-type,12
oam ais-rdi,215
oam loopback,216
oam ping,217
pdp-type,284
permanent-active,192
pin modify,255
pin unlock,256
pin verification enable,257
pin verify,258
plmn search,258
plmn select,259
power-source,193
ppp access-control enable,113
ppp accm,14
ppp account-statistics enable,14
ppp acfc local-request,15
ppp acfc remote-reject,15
ppp authentication-mode,16
ppp callback,310
ppp callback ntstring,311
ppp chap password,17
ppp chap user,18
ppp compression iphc enable,19
ppp compression iphc rtp-connections,20
ppp compression iphc tcp-connections,20
ppp ipcp dns,21
ppp ipcp dns admit-any,22
ppp ipcp dns request,23
ppp ipcp remote-address match,23
ppp ip-pool route,24
ppp lcp delay,25
ppp lcp echo mru verify,72
ppp lcp imsi accept,114
ppp lcp imsi request,114
ppp lcp imsi string,115
ppp lcp sn accept,116
ppp lcp sn request,116
ppp lcp sn string,117
ppp lqm,25
ppp lqm lcp-echo,26
ppp mp,48
ppp mp binding-mode,48
ppp mp endpoint,49
ppp mp fragment disable,50
ppp mp lfi delay-per-frag,51
ppp mp lfi enable,51
ppp mp lfi size-per-frag,52
ppp mp max-bind,53
ppp mp min-bind,54
ppp mp min-fragment,54
ppp mp mp-group,55
ppp mp short-sequence,56
ppp mp sort-buffer-size,56
ppp mp timer lost-fragment,57
ppp mp user,58
ppp mp virtual-template,59
ppp pap local-user,27
ppp pfc local-request,28
ppp pfc remote-reject,28
ppp timer negotiate,29
ppp user accept-format imsi-sn split,118
ppp user attach-format imsi-sn split,118
ppp user replace,119
pppoe-client,93
pppoe-server access-delay,73
pppoe-server access-line-id bas-info,73
pppoe-server access-line-id circuit-id parse-mode,75
pppoe-server access-line-id circuit-id trans-format,76
pppoe-server access-line-id content,77
pppoe-server access-line-id remote-id trans-format,78
pppoe-server access-line-id trust,79
pppoe-server bind,80
pppoe-server session-limit,81
pppoe-server session-limit per-mac,82
pppoe-server session-limit per-vlan,83
pppoe-server session-limit total,84
pppoe-server tag ac-name,85
pppoe-server tag ppp-max-payload,85
pppoe-server tag service-name,86
pppoe-server throttle per-mac,87
pppoe-server virtual-template va-pool,89
precedence,218
profile create,267
profile delete,268
profile main,268
pvc,219
pvc-group,220
remark atm-clp,221
remote address,29
remote address dhcp client-identifier,30
reset atm interface,222
reset counters controller cellular,260
reset counters interface,311
reset counters interface,150
reset counters interface,284
reset counters interface,370
reset counters interface mp-group,60
reset counters interface virtual-access,61
reset counters interface virtual-ethernet,223
reset counters interface virtual-ppp,120
reset fr compression iphc,349
reset fr inarp,350
reset fr ipv6 ind,350
reset fr pvc,351
reset l2tp tunnel,120
reset ppp access-user,33
reset ppp compression iphc,31
reset pppoe-client,94
reset pppoe-client session packet,95
reset pppoe-server,90
rssi,261
sendat,236
sendat,262
serial-set,269
service,121
service,61
service,150
service,312
service cbr,223
service standby,152
service standby,313
service standby,63
service standby,122
service ubr,225
service vbr-nrt,226
service vbr-rt,227
shutdown,228
shutdown,315
shutdown,285
shutdown,228
shutdown,370
shutdown,262
shutdown,153
shutdown,124
shutdown,65
sim backup enable track,263
sim switch-back enable,264
sim switch-to,265
snmp-agent trap enable fr,351
source-ip,124
standby routing-group,315
standby routing-group rule,316
standby timer routing-disable,317
timer-hold,317
timer-hold,352
timer-hold,135
timer-hold,32
timer-hold,125
timer-hold retry,32
timer-hold retry,136
timer-hold retry,126
timer-hold retry,318
transmit-priority,229
trust-imsi,265
tunnel authentication,126
tunnel avp-hidden,127
tunnel flow-control,128
tunnel name,128
tunnel password,129
tunnel timer hello,130
tunnel window send,130
user,131
vp limit,230
vpn-instance,132
wcdma band,270