what command can i used to verify the ppp encapsulation in the space provided below
PPP Commands
This module provides command line interface (CLI) commands for configuring Indicate-to-Point Protocol (PPP) on the Cisco CRS Router Cisco NCS 6000 Series Router .
To use commands of this module, you must be in a user grouping associated with a job grouping that includes appropriate task IDs. If the user grouping assignment is preventing you from using whatever command, contact your AAA administrator for assistance.
Point-to-Point Protocol (PPP) is an encapsulation scheme that can exist used on Packet-over-SONET (POS) and serial interfaces. PPP is a standard protocol used to ship data over synchronous series links. PPP also provides a Link Control Protocol (LCP) for negotiating properties of the link. LCP uses echo requests and responses to monitor the continuing availability of the link.
PPP provides the following Network Control Protocols (NCPs) for negotiating properties of information protocols that will run on the link:
- Cisco Discovery Protocol Control Protocol (CDPCP) to negotiate CDP properties
- IP Command Protocol (IPCP) to negotiate IP backdrop
- IP Version half-dozen Control Protocol (IPv6CP) to negotiate IPv6 properties
- Multiprotocol Label Switching Command Protocol (MPLSCP) to negotiate MPLS backdrop
- Open Arrangement Interconnection Control Protocol (OSICP) to negotiate OSI properties
clear ppp sso state
To clear the replicated Inter-Chassis Stateful Switchover (ICSSO) states for the specified standby interface or for all interfaces on the specified node, use the clear ppp sso state command in EXEC style XR EXEC way .
clear ppp sso land {interface interface-path-id | all} location node-id
Syntax Clarification
| interface interface-path-id | Physical interface or virtual interface.
For more than information about the syntax for the router, apply the question mark ( ? ) online help part. | ||
| all location node-id | Specifies the full qualified path of a specific node in the format rack/slot/module. |
Command Default
No default behavior or values
Command Modes
EXEC mode XR EXEC mode
Command History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release 5.0.0 | This control was introduced. |
Usage Guidelines
This command sets the PPP sessions in the Standby-Upwardly land to the Standby-Down country. All replicated information received from the peer is purged, and SSRP Asking messages are re-sent to the peer.
Task ID
| Job ID | Operations |
|---|---|
| ppp | execute |
Examples
The post-obit example shows how to clear the replicated ICSSO states for the specified standby interface:
RP/0/RP0 /CPU0:router # clear ppp sso country interface 0/1/0/1 The following example shows how to articulate the replicated Inter-Chassis Stateful Switchover (ICSSO) states for all interfaces on the specified node:
RP/0/RP0 /CPU0:router # articulate ppp sso state all location 1/0/one clear ppp statistics
To articulate all Signal-to-Point Protocol (PPP) statistics for a PPP interface, use the articulate ppp statistics command in EXEC style XR EXEC mode .
clear ppp statistics interface interface-path-id
Syntax Description
| interface interface-path-id | Concrete interface or virtual interface.
For more information about the syntax for the router, employ the question mark ( ? ) online help function. |
Command Default
No default behavior or values
Control Modes
EXEC mode XR EXEC mode
Control History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
No specific guidelines touch on the employ of this command.
Job ID
| Task ID | Operations |
|---|---|
| ppp | execute |
Examples
The following example shows how to clear PPP statistics for a PPP interface:
RP/0/RP0 /CPU0:router # articulate ppp statistics interface 0/ane/0/1 encapsulation ppp
To enable encapsulation for communication with routers or bridges using the Point-to-Point Protocol (PPP), apply the encapsulation ppp control in interface configuration mode. To disable PPP encapsulation, use the no form of this command.
encapsulation ppp
Syntax Description
This command has no keywords or arguments.
Command Default
PPP encapsulation is disabled.
Control Modes
Interface configuration
Control History
| Release | Modification |
|---|---|
| Release two.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
Utilize the encapsulation ppp control to enable PPP encapsulation on an interface.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
| interface | read, write |
Examples
The following example shows how to set PPP encapsulation on interface POS 0/1/0/ane:
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/1/0/i RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router # interface serial 0/0/1/2/4:iii RP/0/RP0 /CPU0:router # encapsulation ppp grouping
To create a Session Country Redundancy Protocol (SSRP) group and associate information technology with a profile, utilize the group command in Global Configuration mode XR Config style . To remove this group, use the no form of this command.
group group-id profile profile_name [default]
Syntax Description
| group-id | SSRP group identifier. The range is 1 to 65535. |
| profile profile_name | Profile to associate with this group. |
| default | Associates the group to the default contour. |
Control Default
No default behavior or values
Command Modes
Global Configuration mode XR Config mode
Command History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
Any interfaces on this card can exist configured to employ this grouping. The group number must be unique beyond the router.
Task ID
| Job ID | Operations |
|---|---|
| ppp | read, write |
Examples
The post-obit instance shows how to create an SSRP grouping:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# ssrp location 0/1/cpu0 RP/0/RP0 /CPU0:router (config-ssrp-node)# group 1 profile default multi-router aps
To configure Multi-Router Automatic Protection Switching (MR-APS) and enter APS redundancy configuration mode, employ the multi-router aps command in redundancy configuration style. To deactivate Multi-Router Automatic Protection Switching (MR-APS), utilize the no form of this command.
multi-router aps
Syntax Clarification
This control has no keywords or arguments.
Control Default
No default behavior or values
Control Modes
Back-up configuration
Command History
| Release | Modification |
|---|---|
| Release three.9.0 | This command was introduced. |
Usage Guidelines
No specific guidelines impact the employ of this control.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read |
Examples
The post-obit example shows how to
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# redundancy RP/0/RP0 /CPU0:router (config-back-up)# multi-router aps RP/0/RP0 /CPU0:router (config-redundancy-aps) peer ipv4 accost
To configure the IPv4 address for a Session State Back-up Protocol (SSRP) peer, use the peer ipv4 address control in SSRP configuration mode. To remove the address, utilise the no form of this command.
peer ipv4 address ip-address
Syntax Description
| ip-accost | IP accost of the peer interface whose states will be replicated past SSRP. |
Command Default
No default beliefs or values
Command Modes
SSRP configuration
Command History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release five.0.0 | This command was introduced. |
Usage Guidelines
No specific guidelines touch on the use of this command.
Task ID
| Chore ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following instance shows how to configure the IPv4 address for a Session State Redundancy Protocol (SSRP) peer:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# ssrp profile Profile_1 RP/0/RP0 /CPU0:router (config-ssrp)# peer ipv4 address 10.ten.x.x ppp authentication (BNG)
To enable Challenge Handshake Authentication Protocol (CHAP), MS-CHAP, or Password Authentication Protocol (PAP), and to specify the lodge in which CHAP, MS-CHAP, and PAP authentication is selected on the interface, utilize the ppp authentication command in an appropriate configuration style. To disable PPP authentication, use the no form of this control.
ppp authentication protocol [protocol [protocol] ] {list-name | default}
Syntax Description
| protocol | Proper noun of the authentication protocol used for PPP hallmark. See Table 1 for the appropriate keyword. Y'all may select one, 2, or all three protocols, in whatever order. |
| list-name | (Optional) Used with authentication, authorization, and bookkeeping (AAA). Name of a list of methods of authentication to use. If no list proper noun is specified, the system uses the default. The list is created with the aaa hallmark ppp command. |
| default | (Optional) Specifies the name of the listing of methods created with the aaa hallmark ppp control. |
Command Default
PPP authentication is not enabled.
Command Modes
Interface configuration
Dynamic template configuration
Command History
| Release | Modification |
|---|---|
| Release 2.0 | This control was introduced. |
| Release 3.ii | This command was corrected to include the possibility of specifying iii protocols simultaneously. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
When you enable CHAP or PAP authentication (or both), the local router requires the remote device to prove its identity earlier allowing data traffic to flow. PAP authentication requires the remote device to send a proper noun and a password, which is checked against a matching entry in the local username database or in the remote security server database. CHAP authentication sends a challenge bulletin to the remote device. The remote device encrypts the challenge value with a shared clandestine and returns the encrypted value and its name to the local router in a response bulletin. The local router attempts to lucifer the remote device's proper noun with an associated underground stored in the local username or remote security server database; information technology uses the stored hugger-mugger to encrypt the original challenge and verify that the encrypted values match.
You lot can enable CHAP, MS-CHAP, or PAP in any order. If you enable all iii methods, the first method specified is requested during link negotiation. If the peer suggests using the 2nd method, or refuses the first method, the second method is tried. Some remote devices support simply one method. Base the order in which you specify methods on the remote device's ability to correctly negotiate the appropriate method, and on the level of data line security y'all require. PAP usernames and passwords are sent as clear text strings, which tin be intercepted and reused.
To enter the dynamic template configuration mode, run dynamic-template control in the Global Configuration mode XR Config manner .
 Annotation | If you use a list-proper noun value that was not configured with the aaa authentication ppp command, then authentication does not complete successfully and the line does non come up up. |
Table ane lists the protocols used to negotiate PPP authentication.
| Protocol | Description |
|---|---|
| chap | Enables CHAP on an interface. |
| ms-chap | Enables Microsoft's version of CHAP (MS-CHAP) on an interface. |
| pap | Enables PAP on an interface. |
Enabling or disabling PPP authentication does non affect the power of the local router to authenticate itself to the remote device.
MS-CHAP is the Microsoft version of CHAP. Similar the standard version of CHAP, MS-CHAP is used for PPP hallmark. In this example, authentication occurs between a personal computer using Microsoft Windows NT or Microsoft Windows 95 and a Cisco router or admission server interim as a network access server.
Enabling or disabling PPP authentication does not affect the local router authenticating itself to the remote device.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/4/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp authentication chap MIS-access RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# dynamic-template type ppp p1 RP/0/RP0 /CPU0:router (config-dynamic-template-type)# ppp hallmark chap ms-chap pap ppp chap password
To enable a router calling a collection of routers to configure a common Claiming Handshake Authentication Protocol (CHAP) secret password, use the ppp chap password control in interface configuration style. To disable the countersign, use the no grade of this command.
ppp chap password [articulate | encrypted] countersign
Syntax Description
| clear | (Optional) Specifies the cleartext encryption parameter for the password. |
| encrypted | (Optional) Indicates that the countersign is already encrypted. |
| password | Cleartext or already-encrypted password. |
Command Default
The password is disabled.
Command Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release 2.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
The ppp chap password command is sent in CHAP responses and is used by the peer to authenticate the local router. This does not affect local authentication of the peer. This command is useful for routers that practise not support this command (such every bit routers running older Cisco IOS XR images).
The CHAP secret countersign is used by the routers in response to challenges from an unknown peer.
Task ID
| Chore ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
In this example, a password (xxxx) is entered as a cleartext password:
RP/0/RP0 /CPU0:router (config-if)# ppp chap password xxxx When the password is displayed (as shown in the following instance, using the prove running-config control), the password xxxx appears as 030752180500:
RP/0/RP0 /CPU0:router (config)# testify running-config interface POS one/0/1/0 interface POS0/1/four/2 description Continued to P1 POS 0/1/4/3 ipv4 accost 10.12.32.ii 255.255.255.0 encapsulation ppp ppp authentication chap pap ppp chap password encrypted 030752180500 On subsequent logins, inbound whatsoever of the three following commands would have the same upshot of making xxxx the password for remote CHAP authentication:
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 1/0/1/0 RP/0/RP0 /CPU0:router (config-if)# ppp chap countersign xxxx RP/0/RP0 /CPU0:router (config-if)# ppp chap password articulate xxxx RP/0/RP0 /CPU0:router (config-if)# ppp chap password encrypted 1514190900 ppp chap refuse
To refuse Challenge Handshake Authentication Protocol (CHAP) hallmark from peers requesting it, apply the ppp chap reject control in interface configuration fashion. To allow CHAP authentication, utilise the no class of this control.
ppp chap refuse
Syntax Description
This command has no keywords or arguments.
Command Default
CHAP hallmark is disabled.
Command Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release ii.0 | This command was introduced. |
| Release 5.0.0 | This control was introduced. |
Usage Guidelines
The ppp chap refuse command specifies that CHAP authentication is disabled for all calls, significant that all attempts past the peer to force the user to authenticate using CHAP are refused.
If outbound Countersign Authentication Protocol (PAP) has been configured (using the ppp authentication command), PAP is suggested as the authentication method in the refusal packet.
Task ID
| Chore ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
The following example shows how to specify POS interface 0/3/0/1 and disable CHAP authentication from occurring if a peer calls in requesting CHAP authentication. The method of encapsulation on the interface is PPP.
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/3/0/ane RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp chap refuse ppp ipcp dns
To configure the chief and secondary Domain Proper name Arrangement (DNS) IP addresses for the Internet Protocol Control Protocol (IPCP), use the ppp ipcp dns control in interface configuration mode. To remove the addresses, utilise the no class of this command.
ppp ipcp dns primary-ip-address [sec-ip-address]
Syntax Description
| primary-ip-address | Primary DNS IP address, in the format A.B.C.D. |
| sec-ip-accost | Secondary DNS IP address, in the format W.X.Y.Z. |
Command Default
No default behavior or values
Command Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release 3.nine.0 | This control was introduced. |
| Release 5.0.0 | This control was introduced. |
Usage Guidelines
No specific guidelines bear upon the use of this control.
Chore ID
| Job ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following example shows how to configure the primary and secondary DNS IP addresses for Net Protocol Command Protocol (IPCP):
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# interface serial 0/1/0/1 RP/0/RP0 /CPU0:router (config-if)# ppp ipcp dns ten.ten.x.ten 10.10.x.11 ppp ipcp neighbor-route disable
To disable installation of a route to the peer address negotiated by Net Protocol Control Protocol (IPCP), use the ppp ipcp neighbor-route disable command in interface configuration style. To re-enable installation of a route to the peer address negotiated past IPCP, utilize the no class of this command.
ppp ipcp neighbor-route disable
Syntax Description
This control has no keywords or arguments.
Command Default
No default behavior or values
Command Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release 5.0.0 | This control was introduced. |
Usage Guidelines
No specific guidelines touch on the utilise of this command.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following instance shows how to disable installation of a road to the peer address negotiated past IPCP:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# interface serial 0/ane/0/1 RP/0/RP0 /CPU0:router (config-if)# ppp ipcp neighbour-route disable ppp ipcp peer-address default
To specify the default IPv4 accost that is assigned to the peer past the Internet Protocol Command Protocol (IPCP), utilize the ppp ipcp peer-address default command in interface configuration mode. To remove the address, utilise the no form of this control.
ppp ipcp peer-address default ip-address
Syntax Description
| ip-address | Specifies the IP address for the peer node. |
Control Default
No default behavior or values
Control Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
No specific guidelines affect the use of this command.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following example shows how to specify the default IPv4 address that is assigned to the peer by IPCP.
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# interface series 0/ane/0/ane RP/0/RP0 /CPU0:router (config-if)# ppp ipcp peer-address default 10.10.x.10 ppp max-bad-auth (BNG)
To configure a PPP interface non to reset itself immediately after an authentication failure only instead to allow a specified number of authentication retries, apply the ppp max-bad-auth control in the appropriate configuration mode. To reset to the default of immediate reset, use the no form of this command.
ppp max-bad-auth retries
Syntax Clarification
| retries | Number of retries later on which the interface is to reset itself. Range is from 0 to 10. Default is 0 retries. |
Command Default
retries : 0
Command Modes
Interface configuration
Dynamic template configuration
Command History
| Release | Modification |
|---|---|
| Release 2.0 | This control was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
The ppp max-bad-auth command applies to whatever interface on which PPP encapsulation is enabled.
To enter the dynamic template configuration fashion, run dynamic-template control in the Global Configuration mode XR Config mode .
Chore ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/3/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp hallmark chap RP/0/RP0 /CPU0:router (config-if)# ppp max-bad-auth 3 RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# dynamic-template type ppp p1 RP/0/RP0 /CPU0:router (config-dynamic-template-blazon)# ppp max-configure 5 ppp max-configure (BNG)
To specify the maximum number of configure requests to attempt (without response) before stopping the requests, use the ppp max-configure command in an appropriate configuration mode. To disable the maximum number of configure requests and return to the default, use the no form of this control.
ppp max-configure retries
Syntax Description
| retries | Maximum number of retries. Range is 4 through xx. Default is ten. |
Control Default
retries : 10
Command Modes
Interface configuration
Dynamic template configuration
Command History
| Release | Modification |
|---|---|
| Release 2.0 | This command was introduced. |
| Release five.0.0 | This control was introduced. |
Usage Guidelines
Utilise the ppp max-configure command to specify how many times an attempt is made to establish a Link Control Protocol (LCP) session between two peers for a particular interface. If a configure asking message receives a reply earlier the maximum number of configure requests are sent, further configure requests are abandoned.
To enter the dynamic template configuration way, run dynamic-template control in the Global Configuration mode XR Config mode .
Job ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/3/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp max-configure 4 RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# dynamic-template type ppp p1 RP/0/RP0 /CPU0:router (config-dynamic-template-type)# ppp ipcp ppp max-failure (BNG)
To configure the maximum number of sequent Configure Negative Acknowledgments (CONFNAKs) to permit before terminating a negotiation, use the ppp max-failure command in an appropriate configuration mode. To disable the maximum number of CONFNAKs and return to the default, use the no class of this command.
ppp max-failure retries
Syntax Description
| retries | Maximum number of CONFNAKs to permit earlier terminating a negotiation. Range is from ii to ten. Default is 5. |
Command Default
retries : 5
Command Modes
Interface configuration
Dynamic template configuration
Command History
| Release | Modification |
|---|---|
| Release 2.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
To enter the dynamic template configuration mode, run dynamic-template command in the
Global Configuration mode.
Task ID
| Job ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/3/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp max-failure 3 RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# dynamic-template blazon ppp p1 RP/0/RP0 /CPU0:router (config-dynamic-template-type)# ppp max-failure four ppp max-terminate
To configure the maximum number of finish requests (TermReqs) to send without answer before closing down the Link Control Protocol (LCP) or Network Control Protocol (NCP), utilize the ppp max-cease command in interface configuration mode. To disable the maximum number of TermReqs and return to the default, apply the no form of this command.
ppp max-end number
Syntax Description
| number | Maximum number of TermReqs to ship without reply earlier endmost down the LCP or NCP. Range is from 2 to 10. Default is two. |
Control Default
number : ii
Command Modes
Interface configuration
Control History
| Release | Modification |
|---|---|
| Release two.0 | This control was introduced. |
| Release five.0.0 | This command was introduced. |
Usage Guidelines
No specific guidelines impact the utilize of this control.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
In the post-obit example, a maximum of v TermReqs are specified to be sent before terminating and closing LCP or NCP:
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/3/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp max-terminate five ppp ms-chap hostname
To configure the hostname for MS-CHAP hallmark on an interface, use the ppp ms-chap hostname command in interface configuration fashion. To remove the hostname, use the no form of this command.
ppp ms-chap hostname hostname
Syntax Description
| hostname | Specifies the hostname for MS-CHAP authentication. |
Command Default
No default beliefs or values
Command Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release 3.ix.0 | This control was introduced. |
| Release 5.0.0 | This control was introduced. |
Usage Guidelines
No specific guidelines touch the use of this command.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
The following example shows how to configure the hostname for MS-CHAP authentication on an interface:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# interface serial 0/1/0/1 RP/0/RP0 /CPU0:router (config-if)# ppp ms-chap hostname Host_1 ppp ms-chap password
To configure a mutual Microsoft Challenge Handshake Authentication (MS-CHAP) secret password, use the ppp ms-chap password command in interface configuration style. To disable the countersign, use the no course of this command.
ppp ms-chap password [clear | encrypted] password
Syntax Description
| clear | (Optional) Specifies the cleartext encryption parameter for the countersign. |
| encrypted | (Optional) Indicates that the password is already encrypted. |
| password | Cleartext or already-encrypted password. |
Command Default
The password is disabled.
Command Modes
Interface configuration
Control History
| Release | Modification |
|---|---|
| Release 3.three.0 | This command was introduced. |
| Release v.0.0 | This command was introduced. |
Usage Guidelines
The ppp ms-chap countersign command is sent in CHAP responses and is used by the peer to authenticate the local router. This does not affect local authentication of the peer. The ppp ms-chap password command is useful for routers that do non support this control (such as routers running older software images).
The MS-CHAP cloak-and-dagger password is used past the routers in response to challenges from an unknown peer.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following instance shows how to enter a password (xxxx) every bit a cleartext password:
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/iii/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp ms-chap countersign clear xxxx ppp ms-chap refuse
To refuse Microsoft Challenge Handshake Authentication Protocol (MS-CHAP) authentication from peers requesting it, use the ppp ms-chap reject control in interface configuration mode. To allow MS-CHAP authentication, use the no form of this command.
ppp ms-chap refuse
Syntax Clarification
This command has no keywords or arguments.
Command Default
MS-CHAP hallmark is disabled.
Control Modes
Interface configuration
Control History
| Release | Modification |
|---|---|
| Release three.3.0 | This command was introduced. |
| Release v.0.0 | This command was introduced. |
Usage Guidelines
The ppp ms-chap turn down control specifies that MS-CHAP authentication is disabled for all calls, meaning that all attempts by the peer to forcefulness the user to authenticate using MS-CHAP are refused.
If outbound Countersign Hallmark Protocol (PAP) has been configured (using the ppp authentication command), PAP is suggested as the authentication method in the refusal packet.
Task ID
| Chore ID | Operations |
|---|---|
| ppp | read, write |
Examples
This example shows how to specify POS interface 0/3/0/1 and disable MS-CHAP authentication from occurring if a peer calls in requesting MS-CHAP authentication. The method of encapsulation on the interface is PPP.
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/3/0/i RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp ms-chap decline ppp multilink multiclass
To enable multiclass multilink PPP, use the ppp multilink multiclass command in interface configuration mode. To disable multiclass multilink PPP, employ the no form of this command.
ppp multilink multiclass
Syntax Description
This command has no keywords or arguments.
Control Default
No default behavior or values
Command Modes
Interface configuration
Control History
| Release | Modification |
|---|---|
| Release 3.nine.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
No specific guidelines impact the use of this control.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following example shows how to enable multiclass multilink PPP:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# interface Multilink 0/1/0/0/1 RP/0/RP0 /CPU0:router (config-if)# ppp multilink multiclass ppp multilink multiclass local
To configure the initial number and maximum number of Multiclass Multilink PPP (MCMP) receive classes in a Conf-Request sent from a local host to its peer, use the ppp multilink multiclass local command in interface configuration manner. To remove these settings, use the no course of this command.
ppp multilink multiclass local initial init-number maximum max-number
Syntax Description
| initial init-number | Specifies the initial number of receive classes in the Conf-Request. The range is one to 16. |
| maximum max-number | Specifies the maximum number of receive classes in the Conf-Request. The range is 1 to 16. |
Command Default
When MCMP is enabled, the default initial value is 2 and the default maximum value is 4.
Command Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release three.nine.0 | This control was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
The maximum number of receive classes configures the number of transmission classes on the local host.
Chore ID
| Chore ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following instance shows how to configure the initial number and maximum number of Multiclass Multilink PPP (MCMP) receive classes in a Conf-Request sent from a local host to its peer:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# interface Multilink 0/1/0/0/1 RP/0/RP0 /CPU0:router (config-if)# ppp multilink multiclass local initial ane maximum 16 ppp multilink multiclass remote utilize
To configure the minimum number of Multiclass Multilink PPP (MCMP) receive classes that a local host will have from its peer in a Conf-Asking, employ the ppp multilink multiclass control in interface configuration mode. To remove this setting, use the no course of this command.
ppp multilink multiclass remote apply min-number
Syntax Description
| min-number | Specifies the minimum number of receive classes in the Conf-Asking. The range is 1 to xvi. |
Command Default
The default is 2 if MCMP is enabled.
Control Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release five.0.0 | This command was introduced. |
Usage Guidelines
This command is used to coerce the peer to take a minimum number of MCMP classes. If the peer does non accept the minimum number of MCMP classes specified by this command, the local router will not bring up the PPP link.
Job ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following example shows how to employ the ppp multilink multicast remove apply command.
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# interface Multilink 0/1/0/0/one RP/0/RP0 /CPU0:router (config-if)# ppp multilink multiclass remote employ xvi ppp pap refuse
To refuse Password Authentication Protocol (PAP) authentication from peers requesting information technology, utilize the ppp pap refuse control in interface configuration mode. To let PAP hallmark, use the no form of this command.
ppp pap decline
Syntax Clarification
This command has no keywords or arguments.
Control Default
PAP hallmark is disabled.
Control Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release ii.0 | This command was introduced. |
| Release five.0.0 | This command was introduced. |
Usage Guidelines
The ppp pap turn down command specifies that PAP authentication is disabled for all calls, meaning that all attempts by the peer to strength the user to authenticate using PAP are refused.
If outbound Challenge Handshake Hallmark Protocol (CHAP) has been configured (using the ppp authentication command), CHAP is suggested equally the hallmark method in the refusal packet.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
The following example shows how to specify POS 0/3/0/1 using PPP encapsulation on the interface. This example shows PAP authentication being specified as disabled if a peer calls in requesting PAP authentication.
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/3/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp pap turn down ppp pap sent-username countersign
To enable remote Password Authentication Protocol (PAP) support for an interface, and to use the values specified for username and password in the PAP hallmark request, employ the ppp pap sent-username password command in interface configuration manner. To disable remote PAP back up, use the no form of this command.
ppp pap sent-username username password [articulate | encrypted] password
Syntax Description
| username | Username sent in the PAP hallmark request. |
| clear | (Optional) Specifies the cleartext encryption parameter for the password. |
| encrypted | (Optional) Indicates that the countersign is already encrypted. |
| password | Cleartext or already-encrypted password. |
Command Default
Remote PAP support is disabled.
Control Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release 2.0 | This control was introduced. |
| Release v.0.0 | This control was introduced. |
Usage Guidelines
Use the ppp pap sent-username password control to enable remote PAP support (for example, to respond to the peer'south request to authenticate with PAP) and to specify the parameters to exist used when sending the PAP authentication request.
Yous must configure the ppp pap sent-username password command for each interface.
Task ID
| Job ID | Operations |
|---|---|
| ppp | read, write |
| aaa | read, write |
Examples
In the following example, a password is entered equally a cleartext countersign, xxxx:
RP/0/RP0 /CPU0:router (config-if)# ppp pap sent-username xxxx countersign notified When the password is displayed (as shown in the post-obit instance, using the show running-config command), the password notified appears every bit 05080F1C2243:
RP/0/RP0 /CPU0:router (config-if)# bear witness running-config interface POS0/1/0/0 clarification Continued to P1 POS 0/1/4/ii ipv4 accost ten.12.32.2 255.255.255.0 encapsulation ppp ppp pap sent-username P2 password encrypted 05080F1C2243 On subsequent logins, entering whatever of the 3 following commands would take the aforementioned effect of making xxxx the password for remote PAP authentication:
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/1/0/0 RP/0/RP0 /CPU0:router (config-if)# ppp pap sent-username xxxx password notified RP/0/RP0 /CPU0:router (config-if)# ppp pap sent-username xxxx password clear notified RP/0/RP0 /CPU0:router (config-if)# ppp pap sent-username xxxx encrypted 1514190900 ppp timeout hallmark
To set PPP hallmark timeout parameters, apply the ppp timeout authentication command in interface configuration mode. To reset the default value, employ the no form of this control.
ppp timeout authentication seconds
Syntax Description
| seconds | Maximum time, in seconds, to wait for a response to an authentication bundle. Range is from 3 to xxx seconds. Default is 10 seconds. |
Control Default
seconds : 10
Command Modes
Interface configuration
Command History
| Release | Modification |
|---|---|
| Release 2.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
The default authentication time is 10 seconds, which should allow fourth dimension for a remote router to authenticate and authorize the connectedness and provide a response. However, it is as well possible that it will take much less time than 10 seconds. In such cases, utilise the ppp timeout authentication control to lower the timeout period to amend connection times in the consequence that an hallmark response is lost.
| Note | The timeout affects connection times but if packets are lost. |
| Note | Although lowering the authentication timeout is beneficial if packets are lost, sending authentication requests faster than the peer can handle them results in churn and a slower connexion time. |
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
In the following example, PPP timeout authentication is set to 20 seconds:
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/3/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp timeout authentication xx ppp timeout retry
To gear up PPP timeout retry parameters, use the ppp timeout retry command in interface configuration mode. To reset the time value, use the no form of this control.
ppp timeout retry seconds
Syntax Description
| seconds | Maximum time, in seconds, to wait for a response during PPP negotiation. Range is from 1 to 10 seconds. Default is three seconds. |
Command Default
seconds : iii
Control Modes
Interface configuration
Control History
| Release | Modification |
|---|---|
| Release two.0 | This command was introduced. |
| Release five.0.0 | This command was introduced. |
Usage Guidelines
The ppp timeout retry command is useful for setting a maximum amount of time PPP should wait for a response to whatsoever control packet it sends.
Chore ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following case shows the retry timer being set to 8 seconds:
RP/0/RP0 /CPU0:router # configure RP/0/RP0 /CPU0:router (config)# interface POS 0/iii/0/1 RP/0/RP0 /CPU0:router (config-if)# encapsulation ppp RP/0/RP0 /CPU0:router (config-if)# ppp timeout retry viii redundancy
To enter the back-up configuration mode to configure Multi-Router Automatic Protection Switching (MR-APS), employ the redundancy control in Global Configuration fashion XR Config way .
redundancy
Syntax Description
This command has no keywords or arguments.
Command Default
No default beliefs or values
Control Modes
Global Configuration style XR Config fashion
Command History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
Usage Guidelines
No specific guidelines impact the use of this command.
Task ID
| Chore ID | Operations |
|---|---|
| ppp | read |
Examples
The following example shows how to enter the redundancy configuration way:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# back-up RP/0/RP0 /CPU0:router (config-back-up)# security ttl
To specify that the time-to-live (TTL) value in the IP header of the package is used to validate that a packet is from the expected source, use the security ttl command in SSRP configuration mode. To remove the TTL requirement, employ the no grade of this command.
security ttl max-hops number
Syntax Description
| max-hops number | Maximum number of hops between the peer routers. |
Control Default
The max-hops default is 255.
Command Modes
SSRP configuration
Command History
| Release | Modification |
|---|---|
| Release three.ix.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
If max-hops is not specified, the TTL value must be 255 for a package to exist accustomed.
Task ID
| Task ID | Operations |
|---|---|
| ppp | read, write |
Examples
The following case shows how to specify that the time-to-alive (TTL) value in the IP header of a packet is used to validate that the packet is from the expected source:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# ssrp contour Profile_1 RP/0/RP0 /CPU0:router (config-ssrp)# peer ipv4 address ten.10.10.ten RP/0/RP0 /CPU0:router (config-ssrp)# security ttl max-hops number 50 evidence ppp interfaces (BNG)
To display PPP state data for an interface, use the evidence ppp interfaces control in EXEC mode XR EXEC mode .
show ppp interfaces [brief | detail] {all | type interface-path-id | location node-id}
Syntax Clarification
| 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. | ||
| particular | (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 than data, utilise the question mark (?) online aid function. | ||
| interface-path-id | Concrete interface or virtual interface.
For more than information well-nigh the syntax for the router, use the question mark ( ? ) online aid function. | ||
| all | (Optional) Displays detailed PPP information for all nodes. | ||
| location node-id | (Optional) Displays detailed PPP data for the designated node. The node-id argument is entered in the rack/slot/module annotation. |
Command Default
No default behavior or values
Command Modes
EXEC mode XR EXEC style
Command History
| Release | Modification |
|---|---|
| Release 2.0 | This command was introduced. |
| Release 3.9.0 | For ICSSO, when SSRP is configured, the evidence ppp interfaces control displays the SSO-State for LCP, IPCP, and hallmark layers. |
| Release 4.2.0 | This control was supported in the dynamic template configuration mode for BNG. |
| Release five.0.0 | This command was introduced. |
| Release 5.three.2 | The control was modified to include a new output display field, SRG-state , every bit 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 Cake (IDB). The output includes the following information (where applicable):
- Interface land
- Line protocol land
- Link Control Protocol (LCP) state
- Network Control Protocol (NCP) land
- Multilink PPP state
- Multilink PPP configuration
- Keepalive configuration
- Hallmark configuration
- Negotiated MRUs
- Negotiated IP addresses
This command tin can brandish information for a unmarried interface, all interfaces on a specified node, or all interfaces on the router.
Job ID
| Task ID | Operations |
|---|---|
| ppp | read |
Examples
This example shows how to display PPP state data for a POS interface:
RP/0/RP0 /CPU0:router # evidence ppp interface POS 0/two/0/3 POS0/2/0/3 is upwards, line protocol is up LCP: Open Keepalives enabled (ten 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: Heed IPCP: Open Local IPv4 address: 55.0.0.one Peer IPv4 accost: 55.0.0.ii 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 accost: fe80::3531:35ff:fe55:4213/128 MPLSCP: Stopped This example shows how to brandish PPP state information for a POS interface that is running every bit a Layer ii attachment circuit:
RP/0/0/CPU0:# show ppp interface POS0/ii/0/2 POS0/2/0/ii is up, line protocol is up LCP: Open Running every bit L2 AC This example shows how to display PPP state information for a multilink interface:
RP/0/RP0 /CPU0:router :# show ppp interface Multilink 0/three/0/0/100 Multilink0/iii/0/0/100 is up, line protocol is down LCP: Open up SSO-Land: Standby-Up Keepalives disabled IPCP: Open SSO-Land: Standby-Up Local IPv4 address: 100.0.0.1 Peer IPv4 accost: 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 Fellow member links: ii active, half-dozen inactive (min-active 2) - Serial0/3/one/3/1 ACTIVE - Serial0/3/1/three/two Active - Serial0/iii/1/3/3 INACTIVE : LCP not negotiated - Serial0/3/ane/3/4 INACTIVE : Mismatching peer endpoint - Serial0/3/one/three/5 INACTIVE : Mismatching peer auth name - Serial0/3/one/three/6 INACTIVE : MRRU selection rejected by Peer - Serial0/3/1/3/7 INACTIVE : Mismatching local MCMP classes - Serial0/3/ane/3/8 INACTIVE : MCMP option rejected by peer This case shows how to brandish PPP state information for a serial interface:
RP/0/RP0 /CPU0:router # testify ppp interface Serial 0/3/i/3/ane Serial0/3/1/iii/1 is down, line protocol is down LCP: Open SSO-State: Standby-Up Keepalives enabled (ten 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: Non negotiated Remote MCMP Classes: Not negotiated Authentication Of Us: CHAP (Completed as 'test-user') Of Peer: PAP (Completed equally 'peer-user') Multilink Multilink grouping id: 100 Member status: Active | Field | Description |
|---|---|
| Ack-Rcvd | Configuration acknowledgemt was received; waiting for peer to send configuration asking. |
| 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 hallmark protocols are Challenge Handshake Hallmark Protocol (CHAP), MS-CHAP, and Password Authentication Protocol (PAP). |
| Closed | Lower layer is up, simply this layer is not required. |
| Endmost | Shutting down due to local change. |
| Initial | Connection is idle. |
| IPCP | IP Command Protocol (IPCP) state. The seven possible states that may be displayed are equally follows:
|
| Keepalive | Keepalive setting and interval in seconds for echo request packets. |
| LCP | Indicates the electric current state of LCP. The state of the LCP will report the following states:
|
| Local IPv4 accost | IPv4 address for the local interface. |
| Local MRU | Maximum receive unit. The maximum size of the data transported, in bytes, in the PPP parcel received past the local equipment. |
| Open | Connection open up. |
| OSICP | Open System Interconnection Control Protocol (OSICP) state. The possible states that may exist displayed are equally follows:
|
| 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 bundle received by the peer equipment. |
| Req-Sent | Configuration request was sent; waiting for peer to respond. |
| Starting | This layer is required, only lower layer is down. |
| Stopped | Listening for a configuration asking. |
| Stopping | Shutting down as a event of interactions with peer. |
show ppp sso alerts
To brandish all Inter-Chassis Stateful Switchover (ICSSO) alerts that have occurred, use the show ppp sso alerts control in EXEC mode XR EXEC mode .
show ppp sso alerts location node-id
Syntax Description
| location node-id | Specifies the full qualified path of a specific node in the format rack/slot/module. |
Command Default
No default behavior or values
Control Modes
EXEC mode XR EXEC fashion
Control History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
This control displays the following information for alerts that accept prevented a standby session from beingness brought to the Standby-Up state using replicated data.
- The interfaces on which the alerts have occurred
- The layer in which the error has occurred
- A curt description of the error
| Note | Only 1 fault is reported for each layer for each interface. The error displayed is the near recent error that has occurred. |
Task ID
| Task ID | Operations |
|---|---|
| ppp | read |
Examples
The following example shows how to display all ICSSO alerts that have occurred:
RP/0/RP0 /CPU0:router # testify ppp sso errors location 0/three/cpu0 Intf Layer SSO Proper name with error Error ---------------------------------------------------------------------------- Mu0/three/0/0/100 IPCP Unsupported IPCP choice 0x07 Se0/3/one/3/1:0 LCP Unacceptable value for LCP MRU selection Se0/iii/one/3/2:0 of-us-auth Incorrect Authentication protocol, CHAP Se0/3/one/iii/3:0 of-peer-auth Invalid CHAP Authentication options Se0/3/one/3/four:0 LCP Inconsistent LCP MRRU options prove ppp sso land
To display the Inter-Chassis Stateful Switchover (ICSSO) states of a Point-to-Bespeak Protocol (PPP) session running under a particular Multi-Router Automatic Protection Switching (MR-APS) group, utilise the show ppp sso state command in EXEC mode XR EXEC mode .
prove ppp sso state group grouping-id location node-id
Syntax Description
| group group-id | Specifies the redundancy group number. The range is 1 to 32. |
| location node-id | Specifies the full qualified path of a specific node in the format rack/slot/module. |
Command Default
If group is non specified, states are displayed for all redundancy groups.
Command Modes
EXEC mode XR EXEC mode
Control History
| Release | Modification |
|---|---|
| Release 3.9.0 | This command was introduced. |
| Release 5.0.0 | This control was introduced. |
Usage Guidelines
This command shows united states of these session layers:
- LCP
- of-us authentication
- of-peer authentication
- IPCP
| Note | When an interface is in Standby mode, it is ready to forward traffic immediately later a switchover, if all the session layers, including IPCP, are in the S-Negd country. |
Task ID
| Task ID | Operations |
|---|---|
| ppp | read |
Examples
The following example shows how to display the ICSSO states for PPP running under a redundancy group:
RP/0/RP0 /CPU0:router # show ppp sso country location 0/3/cpu0 Not-Ready : The session is not yet fix to run as Active or Standby S-UnNegd : In Standby mode, no replication country received yet A-Downwardly : In Agile fashion, lower layer non however upwards Deact'ing : Session was Active, now going Standby A-UnNegd : In Active mode, non fully negotiated all the same S-Negd : In Standby mode, replication state received and pre-programmed Act'ing : Session was Standby and pre-programmed, now going Agile A-Negd : In Active way, fully negotiated and up - : This layer non running SSO-Group 1 | of-us of-peer Sess-ID Ifname | LCP auth auth IPCP --------------------------------+------------------------------------------- one Multilink0/3/0/0/100 : Due south-Negd S-Negd S-Negd S-Negd 2 Multilink0/3/0/0/101 : South-UnNegd S-UnNegd S-UnNegd Non-Fix 3 Serial0/3/ane/3/1 : Due south-Negd Due south-Negd S-Negd - four Serial0/3/1/three/2 : A-Negd A-Negd A-Negd A-UnNegd v Serial0/3/1/3/3 : A-Down Non-Ready Non-Ready - vi Serial0/3/1/3/4 : A-Up A-Upwards A-Up A-Up SSO-Group 1 | of-us of-peer Sess-ID Ifname | LCP auth auth IPCP --------------------------------+------------------------------------------- 1 Multilink0/3/0/0/102 : S-Negd Due south-Negd S-Negd S-Negd 2 Serial0/three/1/3/5 : S-Negd Southward-Negd Due south-Negd - three Serial0/3/ane/three/half dozen : A-Negd A-Negd A-Negd A-UnNegd show ppp sso summary
To display the number of sessions in each Inter-Chassis Stateful Switchover (ICSSO) country for each session layer, use the show ppp sso summary command in EXEC way XR EXEC mode .
show ppp sso summary location node-id
Syntax Clarification
| location node-id | Specifies the full qualified path of a specific node in the format rack/slot/module. |
Control Default
No default behavior or values
Command Modes
EXEC way XR EXEC way
Command History
| Release | Modification |
|---|---|
| Release iii.9.0 | This command was introduced. |
| Release five.0.0 | This command was introduced. |
Usage Guidelines
This control displays information for these session layers:
- LCP
- of-usa
- of-peer authentication
- IPCP
| Note | Only sessions with Session State Redundancy Protocol (SSRP) configured are displayed. |
Chore ID
| Chore ID | Operations |
|---|---|
| ppp | read |
Examples
This example shows how to display the number of sessions in each ICSSO state for each session layer.
RP/0/RP0 /CPU0:router # show ppp sso summary location 0/3/cpu0 Not-Ready : The session is not even so prepare to run as Active or Standby Stby-UnNegd : In Standby mode, no replication land received yet Act-Down : In Agile mode, lower layer not withal up Deactivating : Session was Active, now going Standby Act-UnNegd : In Active manner, not fully negotiated yet Stby-Negd : In Standby mode, replication state received and pre-programmed Activating : Session was Standby and pre-programmed, at present going Active Act-Negd : In Active mode, fully negotiated and up - : This layer non running Not- Stby- Human activity- Deactiv- Act- Stby- Activ- Human activity Layer | Total Ready UnNegd Downwardly ating UnNegd Negd ating Negd -------------+------- ------ ------ ------ ------ ------ ------ ------ ----- LCP | 20 2 5 0 0 3 6 0 4 of-usa-auth | 20 10 two 0 0 1 iv 0 iii of-peer-auth | 20 10 3 0 0 2 3 0 two IPCP | 10 ane 2 1 0 3 two 0 1 ssrp group
To attach an Session State Redundancy Protocol (SSRP) group on an interface, employ the ssrp grouping command in interface configuration mode. To remove the SSRP group from the interface, use the no form of this command.
ssrp group grouping-number id id-number ppp
Syntax Description
| grouping-number | SSRP group number. The range is 1 to 65535. |
| id id-number | SSRP identifier number. The range is 1 to 4294967295. |
| ppp | Specifies betoken-to-point protocol. |
Command Default
No default beliefs or values
Command Modes
Interface configuration
Control History
| Release | Modification |
|---|---|
| Release three.9.0 | This command was introduced. |
| Release 5.0.0 | This control was introduced. |
Usage Guidelines
The grouping must exist configured first on a specific location (linecard) then assigned to the interface. The redundancy ID must be unique within the grouping. This command specifies a list the protocols that the group can replicate. Currently only PPP is supported.
Task ID
| Chore ID | Operations |
|---|---|
| ppp | read, write |
Examples
The post-obit instance shows how to
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# interface Multilink 0/1/0/0/1 RP/0/RP0 /CPU0:router (config-if)# ssrp group 1 id 1 ppp ssrp location
To specify the node on which to create a Session State Redundancy Protocol (SSRP) grouping and enter the SSRP node configuration mode, utilize the ssrp location command in Global Configuration mode XR Config mode .
ssrp location node_id
Syntax Description
| node_id | Specifies the full qualified path of a specific node in the format rack/slot/module. |
Control Default
No default behavior or values
Command Modes
Global Configuration mode XR Config way
Command History
| Release | Modification |
|---|---|
| Release iii.9.0 | This command was introduced. |
| Release five.0.0 | This control was introduced. |
Usage Guidelines
The location specifies the bill of fare on which an SSRP group is created.
Task ID
| Chore ID | Operations |
|---|---|
| ppp | read, write |
Examples
This instance shows how to create an SSRP group on a specified node for employ by whatever interface on the card:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# ssrp location 0/one/cpu0 RP/0/RP0 /CPU0:router (config-ssrp-node)# ssrp profile
To configure a Session Land Redundancy Protocol (SSRP) contour and enter the SSRP configuration mode, use the ssrp profile control in Global Configuration mode XR Config fashion . To remove the contour, apply the no form of this command.
ssrp profile profile-proper noun
Syntax Description
| profile-name | Proper noun of this SSRP profile. |
Command Default
No default behavior or values
Command Modes
Global Configuration mode XR Config mode
Command History
| Release | Modification |
|---|---|
| Release three.9.0 | This control was introduced. |
| Release 5.0.0 | This command was introduced. |
Usage Guidelines
A Session Country Redundancy Protocol (SSRP) contour allows the same SSRP configuration to be shared across multiple groups. The same profile can be attached to multiple groups across the router. The group must exist configured earlier the interface that uses the group can be configured. The group number is used in the TCP port number then, the group number must exist unique across the router.
Chore ID
| Chore ID | Operations |
|---|---|
| ppp | read, write |
Examples
This example shows how to configure an SSRP profile:
RP/0/RP0 /CPU0:router # config RP/0/RP0 /CPU0:router (config)# ssrp profile Profile_1 RP/0/RP0 /CPU0:router (config-ssrp)# Source: https://www.cisco.com/c/en/us/td/docs/routers/ncs6000/software/interfaces/command/reference/b-interfaces-cr-ncs6k/b_interfaces_cr50ncs_chapter_01000.html
0 Response to "what command can i used to verify the ppp encapsulation in the space provided below"
Post a Comment