This chapter describes how to con\ufb01gure the Point-to-Point Protocol (PPP) and Multilink PPP features that can be con\ufb01gured on the serial interfaces on a Cisco Optical Networking System (ONS) 15304. Before con\ufb01guring the synchronous serial interfaces, be sure the VC-12 Time Division Multiplexing (TDM) channels are drop-terminated and the DS-1 framers con\ufb01gured.
This chapter covers only the most common con\ufb01guration options as used within the
Cisco ONS 15304 application. For a complete description of the PPP commands in this
chapter, refer to the \u201cMedia-Independent PPP and Multilink PPP Commands\u201d chapter of
theDial Solutions Command Reference. To locate documentation of other commands that
appear in this chapter, use the command reference master index or search online.
interfaces operate at the \ufb01xed E1 rate of 2 Mbps. PPP is used when a link consists of a single synchronous serial channel. For higher-rate services (nxE1), Multilink-PPP is used to bond the individual serial channels together and provide the view of a single, integrated,
PPP, described in RFC 1661, encapsulates network layer protocol information over
point-to-point links. The current implementation of PPP supports option 3, authentication
using CHAP or PAP, option 4, Link Quality Monitoring, and option 5, Magic Number
Magic Number support is available on all serial interfaces. PPP always attempts to
negotiate for Magic Numbers, which are used to detect looped-back lines. Depending on
how thedown-when-looped command is con\ufb01gured, the router might shut down a link if
it detects a loop.
The software provides the Challenge Handshake Authentication Protocol (CHAP) and
Password Authentication Protocol (PAP) on serial interfaces running PPP encapsulation.
For detailed information about authentication, see theSecurity Con\ufb01guration Guide.
In the current Cisco ONS 15304 implementation, Multilink-PPP packet fragmentation is
not currently supported. Disabling fragmentation helps preserve packet processing
\u2022Enable CHAP or PAP Authentication
\u2022Enable Link Quality Monitoring (LQM)
\u2022Disable or Reenable Peer Neighbor Routes
\u2022Con\ufb01gure PPP Half-Bridging
\u2022Con\ufb01gure Multilink PPP
\u2022Monitor and Maintain PPP and MLP Interfaces
With this authentication information, if the router or access server receives another packet
for a destination to which it is already connected, it does not place an additional call.
However, if the router or access server is using rotaries, it sends the packet out the correct
CHAP and PAP were originally speci\ufb01ed in RFC 1334, and CHAP is updated in RFC 1994. These protocols are supported on synchronous and asynchronous serial interfaces. When using CHAP or PAP authentication, each router or access server identi\ufb01es itself by aname. This identi\ufb01cation process prevents a router from placing another call to a router to which it is already connected, and also prevents unauthorized access.
Access control using CHAP or PAP is available on all serial interfaces that use PPP
encapsulation. The authentication feature reduces the risk of security violations on your
router or access server. You can con\ufb01gure either CHAP or PAP for the interface.
Now bringing you back...
Does that email address look wrong? Try again with a different email.