Troubleshooting
Use the pppPacket log to diagnose problems on your PPP interfaces. On dynamic PPP interfaces, you can use the ppp log command within the profile, as described in Chapter 15, Configuring Dynamic Interfaces.
log severity debug pppPacket
- Use to configure a trace log file for a PPP interface.
- Specify one of the following interface types and an interface specifier. For example, specify slot/port:channel/subchannel for a serial POS PPP interface.
- You also configure logging to direct the output to a specific destination. For information, see JUNOSe System Event Logging Reference Guide, Chapter 1, System Logging Overview.
- Example
host1(config-if)#log severity debug pppPacket serial 0/0:1/1
DEBUG 01/01/1970 00:16:58 pppPacket (1000001,*): interface:0/0:1/11/0:1,
time: 0.00, tx lcp confReq, id = 226, length = 19, mru = 32759,
authentication = chap MD5,magicNumber = 0x5387f9a2
DEBUG 01/01/1970 00:16:58 pppPacket (1000001,*): interface: 0/0:1/11/0:1,
time: 0.01, rx lcp confReq, id = 156, length = 18, mru = 32759,
magicNumber = 0x2d8eac91, pfc, acfc
DEBUG 01/01/1970 00:16:58 pppPacket (1000001,*): interface: 0/0:1/11/0:1,
time: 0.01, tx lcp confAck, id = 156, length = 18, mru = 32759,
magicNumber = 0x2d8eac91, pfc, acfc
ppp log
- Use to enable PPP packet or state machine logging on any dynamic interface that uses the profile being configured. Specify one of the following keywords:
host1(config-profile)#ppp log pppPacket
NOTE: This command is equivalent to the log severity debug pppPacket and log severity debug pppStateMachine commands.
