Troubleshooting Mlppp; Mrru - HP ProCurve Secure Router 7203 dl Advanced Management And Configuration Manual

View the Frame Relay interface and verify that its signaling type matches that
of your service provider. You can enter show interface fr <subinterface
number> to view a subinterface (the PVC endpoint) and check DLCIs and the
PVC state. If the Frame Relay interface is down, you probably have a problem
with the signaling type or role.
If the Frame Relay interface is up but a PVC is inactive or deleted, you probably
have a problem with the DLCI.
Also check the TDM channels configured for the physical interface. Even
though mismatched channels is a Physical Layer problem, it sometimes does
not manifest itself until peers attempt to establish a link.
For more information about troubleshooting Frame Relay, see the Basic
Management and Configuration Guide, Chapter 6: Configuring the Data
Link Layer Protocol for E1, T1, and Serial Interfaces.

Troubleshooting MLPPP

The most important consideration for troubleshooting MLPPP is determining
whether the peer supports it. To determine this, view PPP debug messages:
ProCurve# debug ppp negotiation
As you examine the output, look for the following two fields in the negotiation
events:

MRRU

ED
MRRU
An MRRU field automatically signals MLPPP support. In Figure 2-5, the router
receives a message with an MRRU option, which indicates that the peer
supports MLPPP.
If the peer at the other end of the link rejects this option, the ProCurve Secure
Router will terminate the link because it assumes its peer cannot support
MLPPP.
Increasing Bandwidth
Troubleshooting Multilinks
2-15