Increasing Bandwidth
Troubleshooting Multilinks
2-16
2004.07.26 02:14:37 PPP.NEGOTIATION —-->>>>
:
PPPrx[t1 1/1] LCP: Conf-Req
MAGIC(c0b82465) MRRU(1500) ED(3:0000000c045b)
PPPtx[t1 1/1] LCP: Conf-Ack
MAGIC(c0b82465) MRRU(1500) ED(3:0000000c045b)
PPPrx[t1 2/1] LCP: Conf-Req
MAGIC(c0b130b4) MRRU(1500) ED(3:0000000c045b)
PPPtx[t1 2/1] LCP: Conf-Ack
MAGIC(c0b130b4) MRRU(1500) ED(3:0000000c045b)
2004.07.26 02:14:37 PPP.NEGOTIATION t1 1/1: LCP up
:
2004.05.26 02:14:37 PPP.NEGOTIATION PPPFSM: layer up, Protocol=c021
:
2004.07.26 02:14:37 PPP.NEGOTIATION t1 2/1: LCP up
2004.07.26 02:14:37 PPP.NEGOTIATION Links bundled
:
2004.07.26 02:21:15 PPP.NEGOTIATION PPPFSM: layer up, Protocol=8021
2004.07.26 02:21:15 PPP.NEGOTIATION IPCP up
2004.07.26 02:21:16 INTERFACE_STATUS.ppp 1 changed state to up
Figure 2-5. MLPPP Debug Messages
ED
Next, look for messages dealing with the ED option. The ED option identifies
the device transmitting the packet and allows the receiving peer to recognize
that frame fragments received on different carrier lines belong together. The
ED should be the same for each line in the bundle. For example, in Figure 2-5
the ED for the T1 1/1 interface and the T1 2/1 interface are the same.
Troubleshooting MLFR
To view debug messages for MLFR, enter the following command from the
enable mode context:
ProCurve# debug frame-relay multilink
MLFR periodically sends hellos to the remote endpoint. The local interface
should receive a hello ACK in reply. The Frame Relay interface should send a
hello for each carrier line. (See Figure 2-6.) If the interface is not sending hellos
for one of the carrier lines, then that line is down.
ID=133 Len=29 ACCM(00000000)
ID=133 Len=29 ACCM(00000000)
ID=11 Len=29 ACCM(00000000)
ID=11 Len=29 ACCM(00000000)
Multilink
support
T1 1/1 and T1
2/1 are the
same link
Need help?
Do you have a question about the 7102dl - ProCurve Secure Router and is the answer not in the manual?
Questions and answers