Mismatched WAN Encapsulations
If you accept a point-to-point articulation but the encapsulations aren’t the same, the articulation will never
come up. Figure 11.5 shows one articulation with PPP and one with HDLC.
FIGURE 1 1 . 5 Mismatched WAN encapsulations
Look at router Pod1R1 in this output:
Pod1R1#sh int s0/0
Serial0/0 is up, band agreement is down
Hardware is PowerQUICC Serial
Internet abode is 10.0.1.1/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 254/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
LCP REQsent
Closed: IPCP, CDPCP
The consecutive interface is down, and LCP is sending requests but will never accept any responses
because router Pod1R2 is application the HDLC encapsulation. To fix this problem, you would
have to go to router Pod1R2 and configure the PPP encapsulation on the consecutive interface. One
more thing—even admitting the usernames are configured and they’re wrong, it doesn’t matter
because the command ppp affidavit buck isn’t acclimated beneath the consecutive interface configuration
and the username command isn’t accordant in this example.