HP ProCurve Secure 7000dl Series Basic Management And Configuration Manual page 311

ppp 2 is DOWN
Configuration:
Keep-alive is set (10 sec.)
No multilink
MTU = 1500
No authentication
IP is configured
15.1.1.1 255.0.0.0
Link thru ser 2/1 is DOWN; LCP state is INITIAL
Receive: bytes=0, pkts=0, errors=0
Transmit: bytes=0, pkts=0, errors=0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
Bundle information
Queueing method: weighted fair
HDLC driver does not support quality-of-service, or is not cross-connected
Output queue: 0/0/-1512133286/64/0 (size/highest/max total/threshold/drops)
Conversations
Available Bandwidth 0 kilobits/sec
Figure 6-21. show interface ppp <number>
If the PPP interface is down, you should recheck the configuration to see if
there are any errors. (See Figure 6-21.) You should also ensure that you have
bound the physical interface to the PPP interface. If you have entered a bind
command, it should be displayed when you enter show running-config
interface ppp <number> from the enable mode context.
You should then determine if all steps for establishing a PPP session were
completed successfully. The output for the show interface ppp command
provides basic information about different PPP protocols, and you can use
this information to determine if these PPP protocols were exchanged. If you
want more detailed information to troubleshoot the PPP session, you can use
debug commands, which are explained later in this section.
LCP State. When you enter show interfaces ppp command, the status
report will indicate whether the LCP state is opened, initial, or starting.
Configuring the Data Link Layer Protocol for E1, T1, and Serial Interfaces
0/0/0 (active/max active/max total)
If the LCP is opened, the ProCurve Secure Router was able to exchange
LCP packets with its peer.
If the LCP is in the initial state, the ProCurve Secure Router has not yet
succeeded in establishing a link with the peer.
If the LCP state is starting, the PPP interface is attempting to reopen a link
that has been lost.
Troubleshooting Logical Interfaces
6-59