Session | Name of the logical interface on
which the session is running. | All levels |
Type | Session type: PPP. | All levels |
Phase | PPP process phase: Authenticate, Pending, Establish, LCP, Network, Disabled, and Tunneled. | All levels |
Session flags | Special conditions present in the
session: Bundled, TCC, No-keepalives, Looped, Monitored, and NCP-only. | All levels |
protocol State | Protocol state information. See
specific protocol state fields for information. | None specified |
AUTHENTICATION | Challenge-Handshake Authentication
Protocol (CHAP) authentication state information or Password Authentication
Protocol (PAP) state information. See the Authentication
field description for further information. | None specified |
Keepalive settings | Keepalive settings for the PPP sessions on the L2TP network
server (LNS). LNS based PPP sessions are supported only on service
interfaces (si). - Interval—Time in seconds between successive
keepalive requests.
Keepalive aging timeout is calculated as a product of the interval and Down-count values. If the keepalive aging
timeout is greater than 180 seconds, the keepalive packets are handled
by the Routing Engine. If the aging timeout is less than or equal
to 180 seconds, the packets are handled by the Packet Forwarding Engine. - Up-count—The number of keepalive packets
a destination must receive to change a link’s status from down
to up.
- Down-count—The number of keepalive packets
a destination must fail to receive before the network takes down a
link.
| extensive |
RE Keepalive statistics | Keepalive statistics for the packets handled by the Routing
Engine. - LCP echo req Tx—LCP echo requests sent
from the Routing Engine.
- LCP echo req Rx—LCP echo requests received
at the Routing Engine.
- LCP echo rep Tx—LCP echo responses sent
from the Routing Engine.
- LCP echo rep Rx—LCP echo responses received
at the Routing Engine.
- LCP echo req timeout—Number of keepalive
packets where the keepalive aging timer has expired.
- LCP Rx echo req Magic Num Failures—LCP
echo requests where the magic numbers shared between the PPP peers
during LCP negotiation did not match.
- LCP Rx echo rep Magic Num Failures—LCP
echo responses where the magic numbers shared between the PPP peers
during LCP negotiation did not match.
| extensive |
LCP | LCP information: - State—LCP protocol state (all platforms
except M120 and M320 routers):
- Ack-rcvd—A Configure-Request has been sent
and a Configure-Ack has been received.
- Ack-sent—A Configure-Request and a Configure-Ack
have both been sent, but a Configure-Ack has not yet been received.
- Closed—Link is not available for traffic.
- Opened—Link is administratively available
for traffic.
- Req-sent—An attempt has been made to configure
the connection.
- State—LCP protocol state (M120 and M320
routers):
- Ack-rcvd—A Configure-Request has been sent
and a Configure-Ack has been received.
- Ack-sent—A Configure-Request and a Configure-Ack
have both been sent, but a Configure-Ack has not yet been received.
- Closed—Link is available (up), but no Open
has occurred.
- Closing—A Terminate-Request has been sent
but a Terminate-Ack has not yet been received.
- Opened—Link is administratively available
for traffic. A Configure-Ack has been both sent and received.
- Req-sent—An attempt has been made to configure
the connection. A Configure-Request has been sent but a Configure-Ack
has not yet been received.
- Starting—An administrative Open has been
initiated, but the lower layer is still unavailable (Down).
- Stopped—The system is waiting for a Down
event after the This-Layer-Finished action, or after sending a Terminate-Ack.
- Stopping—A Terminate-Request has been sent
but a Terminate-Ack has not yet been received.
- Last started—LCP state start time.
- Last completed—LCP state completion time.
| extensive |
| | - Negotiated options:
- ACFC—Address and-Control Field Compression.
A configuration option that provides a method to negotiate the compression
of the Data Link Layer Address and Control fields.
- Asynchronous map—Asynchronous control character
map. A configuration option used on asynchronous links such as telephone
lines to identify control characters that must be replaced by a two-character
sequence to prevent them from being interpreted by equipment used
to establish the link.
- Authentication protocol—Protocol used for
authentication. This option provides a method to negotiate the use
of a specific protocol for authentication. It requires a peer to authenticate
itself before allowing network-layer protocol packets to be exchanged.
By default, authentication is not required.
- Authentication algorithm—Type of authentication
algorithm. The Message Digest algorithm (MD5) is the only algorithm
supported.
- Endpoint discriminator class—For multilink
PPP (MLPPP), a configuration option that identifies the system transmitting
the packet. This option advises a system that the peer on this link
could be the same as the peer on another existing link.
- Magic number—A configuration option that
provides a method to detect looped-back links and other data-link
layer anomalies. By default, the magic number is not negotiated.
- MRU—Maximum receive unit. A configuration
option that may be sent to inform the peer that the implementation
can receive larger packets, or to request that the peer send smaller
packets. The default value is 1500 octets.
- MRRU—For multilink PPP, the maximum receive
reconstructed unit. A configuration option that specifies the maximum
number of octets in the Information fields of reassembled packets.
- Multilink header suspendable classes—For
MLPPP, an LCP option that advises the peer that the implementation
wishes to receive fragments with a format given by the code number,
with the maximum number of suspendable classes given.
- Multilink header format classes—For MLPPP,
an LCP option that advises the peer that the implementation wishes
to receive fragments with a format given by the code number.
- PFC—Protocol-Field-Compression. A configuration
option that provides a method to negotiate the compression of the
PPP Protocol field.
- short sequence—For MLPPP, an option that
advises the peer that the implementation wishes to receive fragments
with short, 12-bit sequence numbers.
| |
Authentication | CHAP or PAP authentication state
information. For CHAP authentication: - Chap-ans-rcvd—Packet was sent from the
peer, indicating that the peer received the Chap-resp-sent packet.
- Chap-ans-sent—Packet was sent from the
authenticator, indicating that the authenticator received the peer's Chap-resp-rcvd packet.
- Chap-chal-rcvd—Challenge packet has been
received by the peer.
- Chap-chal-sent—Challenge packet has been
sent by the authenticator to begin the CHAP protocol or has been transmitted
at any time during the Network-Layer Protocol (NCP) phase to ensure
that the connection has not been altered.
- Chap-resp-rcvd—CHAP response packet has
been received by the authenticator.
- Chap-resp-sent—CHAP response packet has
been sent to the authenticator.
- Closed—Link is not available for authentication.
- Failure—Authenticator compares the response
value in the response packet from the peer with its own response value,
but the value does not match. Authentication fails.
- Success—Authenticator compares the response
value in the response packet from the peer with its own response value,
and the value matches. Authentication is successful.
For PAP authentication: - Pap-resp-sent—PAP response sent to peer
(ACK/NACK)t.
- Pap-req-rcvd—PAP request packet received
from peer.
- Pap-resp-rcvd—PAP response received from
the peer (ACK/NACK).
- Pap-req-sent—PAP request packet sent to
the peer.
- Closed—Link is not available for authentication.
- Failure—Authenticator compares the response
value in the response packet from the peer with its own response value,
but the value does not match. Authentication fails.
- Success—Authenticator compares the response
value in the response packet from the peer with its own response value,
and the value matches. Authentication is successful.
| None specified |
IPCP | Internet Protocol Control Protocol
(IPCP) information. - State—(All platforms except M120 and M320
routers) One of the following values:
- Ack-rcvd—A Configure-Request has been sent
and a Configure-Ack has been received.
- Ack-sent—A Configure-Request and a Configure-Ack
have both been sent, but a Configure-Ack has not yet been received.
- Closed—Link is not available for traffic.
- Opened—Link is administratively available
for traffic.
- Req-sent—An attempt has been made to configure
the connection.
- State—(M120 and M320 routers) One of the
following values:
- Ack-rcvd—A Configure-Request has been sent
and a Configure-Ack has been received.
- Ack-sent—A Configure-Request and a Configure-Ack
have both been sent, but a Configure-Ack has not yet been received.
- Closed—Link is available (up), but no Open
has occurred.
- Closing—A Terminate-Request has been sent
but a Terminate-Ack has not yet been received.
- Opened—Link is administratively available
for traffic. A Configure-Ack has been both sent and received.
- Req-sent—An attempt has been made to configure
the connection. A Configure-Request has been sent but a Configure-Ack
has not yet been received.
- Starting—An administrative Open has been
initiated, but the lower layer is still unavailable (Down).
- Stopped—The system is waiting for a Down
event after the This-Layer-Finished action, or after sending a Terminate-Ack.
- Stopping—A Terminate-Request has been sent
but a Terminate-Ack has not yet been received.
- Last started—IPCP state start time.
- Last completed—IPCP state authentication
completion time.
- Negotiated options:
- compression protocol—Negotiate the use
of a specific compression protocol. By default, compression is not
enabled.
- local address—Desired local address of
the sender of a Configure-Request. If all four octets are set to zero,
the peer provides the IP address.
- primary DNS server—Negotiate with the remote
peer to select the address of the primary DNS server to be used on
the local end of the link.
- primary WINS server—Negotiate with the
remote peer to select the address of the primary WINS server to be
used on the local end of the link.
- remote address—IP address of the remote
end of the link in dotted quad notation.
- secondary DNS server—Negotiate with the
remote peer to select the address of the secondary DNS server to be
used on the local end of the link.
- secondary WINS server—Negotiate with the
remote peer to select the address of the secondary WINS server to
be used on the local end of the link.
| extensive |
IPV6CP | Internet Protocol version 6 Control
Protocol (IPV6CP) information. - State—(All platforms except M120 and M320
routers) One of the following values:
- Ack-rcvd—A Configure-Request has been sent
and a Configure-Ack has been received.
- Ack-sent—A Configure-Request and a Configure-Ack
have both been sent, but a Configure-Ack has not yet been received.
- Closed—Link is not available for traffic.
- Opened—Link is administratively available
for traffic.
- Req-sent—An attempt has been made to configure
the connection.
- State—(M120 and M320 routers) One of the
following values:
- Ack-rcvd—A Configure-Request has been sent
and a Configure-Ack has been received.
- Ack-sent—A Configure-Request and a Configure-Ack
have both been sent, but a Configure-Ack has not yet been received.
- Closed—Link is available (up), but no Open
has occurred.
- Closing—A Terminate-Request has been sent
but a Terminate-Ack has not yet been received.
- Opened—Link is administratively available
for traffic. A Configure-Ack has been both sent and received.
- Req-sent—An attempt has been made to configure
the connection. A Configure-Request has been sent but a Configure-Ack
has not yet been received.
- Starting—An administrative Open has been
initiated, but the lower layer is still unavailable (Down).
- Stopped—The system is waiting for a Down
event after the This-Layer-Finished action, or after sending a Terminate-Ack.
- Stopping—A Terminate-Request has been sent
but a Terminate-Ack has not yet been received.
- Last started—IPV6CP state start time.
- Last completed—IPV6CP state authentication
completion time.
- Negotiated options:
- local interface identifier—Desired local
address of the sender of a Configure-Request. If all four octets are
set to zero, the peer provides the IP address.
- remote interface identifier—IP address
of the remote end of the link in dotted quad notation.
| extensive |
OSINLCP State | OSI Network Layer Control Protocol
(OSINLCP) protocol state information (all platforms except M120 and
M320 routers): - State:
- Ack-rcvd—Configure-Request has been sent
and Configure-Ack has been received.
- Ack-sent—Configure-Request and Configure-Ack
have both been sent, but Configure-Ack has not yet been received.
- Closed—Link is not available for traffic.
- Opened—Link is administratively available
for traffic.
- Req-sent—Attempt has been made to configure
the connection.
- Last started—OSINLCP state start time.
- Last completed—OSINCLP state completion
time.
| extensive |
TAGCP | TAGCP information. - State—(All platforms except M120 and M320
routers) One of the following values:
- Ack-rcvd—A Configure-Request has been sent
and a Configure-Ack has been received.
- Ack-sent—A Configure-Request and a Configure-Ack
have both been sent, but a Configure-Ack has not yet been received.
- Closed—Link is not available for traffic.
- Opened—Link is administratively available
for traffic.
- Req-sent—An attempt has been made to configure
the connection.
- State—(M120 and M320 routers) One of the
following values:
- Ack-rcvd—A Configure-Request has been sent
and a Configure-Ack has been received.
- Ack-sent—A Configure-Request and a Configure-Ack
have both been sent, but a Configure-Ack has not yet been received.
- Closed—Link is available (up), but no Open
has occurred.
- Closing—A Terminate-Request has been sent
but a Terminate-Ack has not yet been received.
- Opened—Link is administratively available
for traffic. A Configure-Ack has been both sent and received.
- Req-sent—An attempt has been made to configure
the connection. A Configure-Request has been sent but a Configure-Ack
has not yet been received.
- Starting—An administrative Open has been
initiated, but the lower layer is still unavailable (Down).
- Stopped—The system is waiting for a Down
event after the This-Layer-Finished action, or after sending a Terminate-Ack.
- Stopping—A Terminate-Request has been sent
but a Terminate-Ack has not yet been received.
- Last started—TAGCP state start time.
- Last completed—TAGCP state authentication
completion time.
| extensive none |
