Platform Considerations; Module Requirements - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - LINK LAYER CONFIGURATION GUIDE 2010-10-13 Configuration Manual

Platform Considerations

Module Requirements

Copyright © 2010, Juniper Networks, Inc.
NOTE: Even though the ppp peer-ip-address-optional command is
configured, on receiving a NAK from the server, if the client sends an IPCP
confReq message with specific IP address, IPCP is terminated after a
maximum of five attempts.
When the IPCP negotiation succeeds by configuring the ppp peer-ip-address-optional
command, the server does not have the client IP address. An IP address from RADIUS or
from the local pool is allocated to the client and the route towards this is added on the
server even though the client is not assigned with this address. If you want the server to
have the route to the client-requested IP address, use the framed-route RADIUS attribute
or configure statics routes. The client adds or configures static routes towards the server
for proper forwarding.
You can configure PPP interfaces on the following E Series Broadband Services Routers:
E120 router
E320 router
ERX1440 router
ERX1410 router
ERX710 router
ERX705 router
ERX310 router
For information about the modules that support PPP interfaces on ERX14xx models,
ERX7xx models, and the ERX310 router:
See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
See ERX Module Guide, Appendix A, Module Protocol Support for information about the
modules that support PPP.
For information about the modules that support PPP interfaces on the E120 and E320
routers:
See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module
specifications.
See E120 and E320 Module Guide, Appendix A, IOA Protocol Support for information
about the modules that support PPP.
Chapter 8: Configuring Point-to-Point Protocol
269