To display PPP state information for an interface, use the show ppp interfaces command in EXEC mode.
show ppp interfaces [brief | detail] {all | type interface-path-id | location node-id}
Syntax Description
brief
|
(Optional)
Displays brief output for all interfaces on the router, for a specific POS
interface instance, or for all interfaces on a specific node.
|
detail
|
(Optional)
Displays detailed output for all interfaces on the router, for a specific
interface instance, or for all interfaces on a specific node.
|
type
|
Interface
type. For more information, use the question mark (?) online help function.
|
interface-path-id
|
Physical
interface or virtual interface.
Note
|
Use the
show
interfaces command to see a list of all interfaces
currently configured on the router.
|
For more
information about the syntax for the router, use the question mark (? ) online help function.
|
all
|
(Optional)
Displays detailed PPP information for all nodes.
|
location
node-id
|
(Optional)
Displays detailed PPP information for the designated node. The
node-id
argument is entered in the
rack/slot/module notation.
|
Command Default
No default behavior
or values
Command History
Release
|
Modification
|
Release 3.9.0
|
This command was introduced.
|
Release 4.2.0
|
This
command was supported in the dynamic template configuration mode for BNG.
|
Release 5.3.2
|
The command was modified to include a new output display field, SRG-state , as part of geo redundancy support for PPPoE sessions in BNG router.
|
Usage Guidelines
There are seven
possible PPP states applicable for either the Link Control Protocol (LCP) or
the Network Control Protocol (NCP).
The command output
displays a summary of the interface as it is in the PPP Interface Descriptor
Block (IDB). The output includes the following information (where applicable):
- Interface state
- Line protocol state
- Link Control Protocol (LCP)
state
- Network Control Protocol
(NCP) state
- Multilink PPP state
- Multilink PPP configuration
- Keepalive configuration
- Authentication
configuration
- Negotiated MRUs
- Negotiated IP addresses
This command can
display information for a single interface, all interfaces on a specified node,
or all interfaces on the router.
Multilink PPP and POS are not supported for BNG Geo Redundancy.
Task ID
Task ID
|
Operations
|
ppp
|
read
|
Examples
This example shows
how to display PPP state information for a POS interface:
RP/0/RSP0/CPU0:router# show ppp interface POS 0/2/0/3
POS0/2/0/3 is up, line protocol is up
LCP: Open
Keepalives enabled (10 sec)
Local MRU: 4470 bytes
Peer MRU: 4470 bytes
Authentication
Of Us: CHAP (Completed as 'test-user')
Of Peer: PAP (Completed as 'peer-user')
CDPCP: Listen
IPCP: Open
Local IPv4 address: 55.0.0.1
Peer IPv4 address: 55.0.0.2
Peer DNS Primary: 55.0.0.254
Peer DNS Secondary: 155.0.0.254
IPV6CP: Open
Local IPv6 address: fe80::3531:35ff:fe55:5747/128
Peer IPv6 address: fe80::3531:35ff:fe55:4213/128
MPLSCP: Stopped
This example shows
how to display PPP state information for a POS interface that is running as a
Layer 2 attachment circuit:
RP/0/0/CPU0:# show ppp interface POS0/2/0/2
POS0/2/0/2 is up, line protocol is up
LCP: Open
Running as L2 AC
This example shows
how to display PPP state information for a multilink interface:
RP/0/RSP0/CPU0:router:# show ppp interface Multilink 0/3/0/0/100
Multilink0/3/0/0/100 is up, line protocol is down
LCP: Open
SSO-State: Standby-Up
Keepalives disabled
IPCP: Open
SSO-State: Standby-Up
Local IPv4 address: 100.0.0.1
Peer IPv4 address: 100.0.0.2
IPV6CP: Open
Local IPv6 address: fe80::3531:35ff:fe55:4600/128
Peer IPv6 address: fe80::3531:35ff:fe55:3215/128
Multilink
Local MRRU: 1500 bytes
Peer MRRU: 1500 bytes
Local Endpoint Discriminator: 1234567812345678
Peer Endpoint Discriminator: 1111222233334444
MCMP classes: Local 4, Remote 2
Member links: 2 active, 6 inactive (min-active 2)
- Serial0/3/1/3/1 ACTIVE
- Serial0/3/1/3/2 ACTIVE
- Serial0/3/1/3/3 INACTIVE : LCP not negotiated
- Serial0/3/1/3/4 INACTIVE : Mismatching peer endpoint
- Serial0/3/1/3/5 INACTIVE : Mismatching peer auth name
- Serial0/3/1/3/6 INACTIVE : MRRU option rejected by Peer
- Serial0/3/1/3/7 INACTIVE : Mismatching local MCMP classes
- Serial0/3/1/3/8 INACTIVE : MCMP option rejected by peer
This example shows
how to display PPP state information for a serial interface:
RP/0/RSP0/CPU0:router# show ppp interface Serial 0/3/1/3/1
Serial0/3/1/3/1 is down, line protocol is down
LCP: Open
SSO-State: Standby-Up
Keepalives enabled (10 sec)
Local MRU: 1500 bytes
Peer MRU: 1500 bytes
Local Bundle MRRU: 1500 bytes
Peer Bundle MRRU: 1500 bytes
Local Endpoint Discriminator: 1234567812345678
Peer Endpoint Discriminator: 1111222233334444
Local MCMP Classes: Not negotiated
Remote MCMP Classes: Not negotiated
Authentication
Of Us: CHAP (Completed as 'test-user')
Of Peer: PAP (Completed as 'peer-user')
Multilink
Multilink group id: 100
Member status: ACTIVE
This is a sample output of the show ppp interfaces command in the BNG router, having subscriber redundancy group (SRG) in geo redundancy enabled for PPPoE sessions:
RP/0/RSP0/CPU0:router# show ppp interfaces
Bundle-Ether2.1.pppoe16534 is down, line protocol is up
SRG Role: Slave
LCP: Open
Keepalives enabled (60 sec, retry count 5)
Local MRU: 1492 bytes
Peer MRU: 65531 bytes
Authentication
Of Peer: PAP (Completed as user1@domain.com)
Of Us: <None>
IPCP: Open
Local IPv4 address: 12.16.0.1
Peer IPv4 address: 12.0.250.23
IPv6CP: Initial
Local IPv6 address: fe80::
Peer IPv6 address: fe80::
Table 2. show ppp
interfaces Field Descriptions
Field
|
Description
|
Ack-Rcvd
|
Configuration acknowledgemt was received; waiting for peer to
send configuration request.
|
Ack-Sent
|
Configuration acknowledgemt was sent; waiting for peer to
respond to configuration request.
|
Authentication
|
Type of
user authentication configured on the local equipment and on the peer
equipment. Possible PPP authentication protocols are Challenge Handshake
Authentication Protocol (CHAP), MS-CHAP, and Password Authentication Protocol
(PAP).
|
Closed
|
Lower
layer is up, but this layer is not required.
|
Closing
|
Shutting
down due to local change.
|
Initial
|
Connection
is idle.
|
IPCP
|
IP Control
Protocol (IPCP) state. The seven possible states that may be displayed are as
follows:
- Initial—Lower layer is
unavailable (Down), and no Open has occurred. The Restart timer is not running
in the Initial state.
- Starting—An administrative
Open has been initiated, but the lower layer is still unavailable (Down). The
Restart timer is not running in the Starting state. When the lower layer
becomes available (Up), a Configure-Request is sent.
- Closed— IPCP is not
currently trying to negotiate.
- Stopped—A Terminate-Request
has been sent and the Restart timer is running, but a Terminate-Ack has not yet
been received.
- Closing—A Terminate-Request
has been sent and the Restart timer is running, but a Terminate-Ack has not yet
been received. Upon reception of a Terminate-Ack, the Closed state is entered.
Upon the expiration of the Restart timer, a new Terminate-Request is
transmitted, and the Restart timer is restarted. After the Restart timer has
expired Max-Terminate times, the Closed state is entered.
- Stopping—A
Terminate-Request has been sent and the Restart timer is running, but a
IPCP-Ack has not yet been received. Req-Sent.
- ACKsent—IPCP has received a
request and has replied to it.
- ACKrcvd—IPCP has received a
reply to a request it sent.
- Open—IPCP is functioning
properly.
|
Keepalive
|
Keepalive
setting and interval in seconds for echo request packets.
|
LCP
|
Indicates
the current state of LCP. The state of the LCP will report the following
states:
- Initial—Lower layer is
unavailable (Down), and no Open has occurred. The Restart timer is not running
in the Initial state.
- Starting—An administrative
Open has been initiated, but the lower layer is still unavailable (Down). The
Restart timer is not running in the Starting state. When the lower layer
becomes available (Up), a Configure-Request is sent.
- Closed— LCP is not
currently trying to negotiate.
- Stopped—A Terminate-Request
has been sent and the Restart timer is running, but a Terminate-Ack has not yet
been received.
- Closing—A Terminate-Request
has been sent and the Restart timer is running, but a Terminate-Ack has not yet
been received. Upon reception of a Terminate-Ack, the Closed state is entered.
Upon the expiration of the Restart timer, a new Terminate-Request is
transmitted, and the Restart timer is restarted. After the Restart timer has
expired Max-Terminate times, the Closed state is entered.
- Stopping—A
Terminate-Request has been sent and the Restart timer is running, but a
Terminate-Ack has not yet been received. Req-Sent.
- ACKsent—LCP has received a
request and has replied to it.
- ACKrcvd—LCP has received a
reply to a request it sent.
- Open—LCP is functioning
properly
|
Local IPv4
address
|
IPv4
address for the local interface.
|
Local MRU
|
Maximum
receive unit. The maximum size of the information transported, in bytes, in the
PPP packet received by the local equipment.
|
Open
|
Connection
open.
|
OSICP
|
Open
System Interconnection Control Protocol (OSICP) state. The possible states that
may be displayed are as follows:
- Initial—Lower layer is
unavailable (Down), and no Open has occurred. The Restart timer is not running
in the Initial state.
- Starting—An administrative
Open has been initiated, but the lower layer is still unavailable (Down). The
Restart timer is not running in the Starting state. When the lower layer
becomes available (Up), a Configure-Request is sent.
- Closed— OSICP is not
currently trying to negotiate.
- Stopped—A Terminate-Request
has been sent and the Restart timer is running, but a Terminate-Ack has not yet
been received.
- Closing—A Terminate-Request
has been sent and the Restart timer is running, but a Terminate-Ack has not yet
been received. Upon reception of a Terminate-Ack, the Closed state is entered.
Upon the expiration of the Restart timer, a new Terminate-Request is
transmitted, and the Restart timer is restarted. After the Restart timer has
expired Max-Terminate times, the Closed state is entered.
- Stopping—A
Terminate-Request has been sent and the Restart timer is running, but a
Terminate-Ack has not yet been received. Req-Sent.
- ACKsent—OSICP has received
a request and has replied to it.
- ACKrcvd—OSICP has received
a reply to a request it sent.
- Open—OSICP is functioning
properly.
|
Peer IPv4
address
|
IPv4
address for the peer equipment.
|
Peer MRU
|
Maximum
receive unit. The maximum size of the information transported, in bytes, in the
PPP packet received by the peer equipment.
|
Req-Sent
|
Configuration request was sent; waiting for peer to respond.
|
Starting
|
This layer
is required, but lower layer is down.
|
Stopped
|
Listening
for a configuration request.
|
Stopping
|
Shutting
down as a result of interactions with peer.
|