Before my time slot ended, I decided to give it one more shot, but this time on routers R7 and R8. It was a straight copy/paste of the other routers, except that the interface was se0/0/0 instead of se0/2/0.
R7# interface Multilink1 ip address 150.20.25.5 255.255.255.0 ppp multilink ppp multilink group 1 ! interface Serial0/0/0 no ip address encapsulation frame-relay no keepalive clock rate 2000000 frame-relay interface-dlci 205 ppp Virtual-Template1 frame-relay interface-dlci 222 ppp Virtual-Template1 frame-relay interface-dlci 502 ppp Virtual-Template1 frame-relay interface-dlci 555 ppp Virtual-Template1 ! interface Virtual-Template1 no ip address ppp multilink ppp multilink group 1 ! R8# interface Multilink1 ip address 150.20.25.2 255.255.255.0 ppp multilink ppp multilink group 1 ! interface Serial0/0/0 no ip address encapsulation frame-relay no keepalive frame-relay interface-dlci 205 ppp Virtual-Template1 frame-relay interface-dlci 222 ppp Virtual-Template1 frame-relay interface-dlci 502 ppp Virtual-Template1 frame-relay interface-dlci 555 ppp Virtual-Template1 ! interface Virtual-Template1 no ip address ppp multilink ppp multilink group 1 ! *Dec 2 16:32:22.395: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down *Dec 2 16:32:22.987: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up *Dec 2 16:32:22.991: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up *Dec 2 16:32:22.991: %LINK-3-UPDOWN: Interface Virtual-Access4, changed state to up *Dec 2 16:32:22.991: %LINK-3-UPDOWN: Interface Virtual-Access5, changed state to up *Dec 2 16:32:23.003: %FR-3-MLPOFR_ERROR: MLPoFR not configured properly on Link Virtual-Access1 Bundle Multilink1 :Frame Relay traffic shaping must be enabled *Dec 2 16:32:23.007: %FR-3-MLPOFR_ERROR: MLPoFR not configured properly on Link Virtual-Access3 Bundle Multilink1 :Frame Relay traffic shaping must be enabled R8(config-if)# *Dec 2 16:32:23.011: %FR-3-MLPOFR_ERROR: MLPoFR not configured properly on Link Virtual-Access4 Bundle Multilink1 :Frame Relay traffic shaping must be enabled *Dec 2 16:32:23.011: %FR-3-MLPOFR_ERROR: MLPoFR not configured properly on Link Virtual-Access5 Bundle Multilink1 :Frame Relay traffic shaping must be enabled *Dec 2 16:32:23.015: %LINK-3-UPDOWN: Interface Multilink1, changed state to up R8(config-if)# *Dec 2 16:32:24.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up *Dec 2 16:32:24.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up *Dec 2 16:32:24.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access4, changed state to up *Dec 2 16:32:24.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access5, changed state to up *Dec 2 16:32:24.015: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up R8(config-if)# R8(config-if)# R8(config-if)# R8(config-if)# R8(config-if)#do ping 150.20.25.5 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 150.20.25.5, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms R8(config-if)# Magically life seemed to be good. So what might have been the difference between the two pairs of routers? When doing a show interface on routers 7 and 8, both were DTE, both had a clock rate command, and neither had the frame-relay switching command applied. This to me seems to be the same as routers R2 and R5 when I first started this configuration. Do you think it would be possible there is a hardware issue on the serial interface going from R2 to R5 (R&S POD 111)? Also, thanks to all who have been helping to give input on this issue for me. On Thu, Dec 5, 2013 at 10:11 AM, rauenpc . <[email protected]> wrote: > I'm in the same boat as you Gbenga... I can make it work in GNS3 without > any issue. Not so much with the lab equipment. > > > On Thu, Dec 5, 2013 at 10:01 AM, Gbenga Olubisi > <[email protected]>wrote: > >> Hi rauenpc, >> >> just done this in GNS3 and it works. >> >> R5 >> === >> >> ! >> frame-relay switching >> ! >> ! >> interface Serial0/0 >> no ip address >> encapsulation frame-relay >> serial restart-delay 0 >> clock rate 2016000 >> frame-relay interface-dlci 205 ppp Virtual-Template1 >> frame-relay interface-dlci 222 ppp Virtual-Template1 >> frame-relay intf-type dce >> ! >> interface Multilink1 >> ip address 150.20.25.5 255.255.255.0 >> ppp multilink >> ppp multilink group 1 >> ! >> ! >> interface Virtual-Template1 >> no ip address >> ppp multilink >> ppp multilink group 1 >> ! >> >> >> R2 >> == >> ! >> interface Serial0/0 >> no ip address >> encapsulation frame-relay >> serial restart-delay 0 >> clock rate 2016000 >> frame-relay interface-dlci 205 ppp Virtual-Template1 >> frame-relay interface-dlci 222 ppp Virtual-Template1 >> ! >> interface Multilink1 >> ip address 150.20.25.2 255.255.255.0 >> ppp multilink >> ppp multilink group 1 >> ! >> interface Virtual-Template1 >> no ip address >> ppp multilink >> ppp multilink group 1 >> ! >> >> >> R5#ping 150.20.25.2 >> >> Type escape sequence to abort. >> Sending 5, 100-byte ICMP Echos to 150.20.25.2, timeout is 2 seconds: >> !!!!! >> Success rate is 100 percent (5/5), round-trip min/avg/max = 20/31/48 ms >> R2#ping 150.20.25.5 >> >> Type escape sequence to abort. >> Sending 5, 100-byte ICMP Echos to 150.20.25.5, timeout is 2 seconds: >> !!!!! >> Success rate is 100 percent (5/5), round-trip min/avg/max = 20/30/44 ms >> >> >> >> >> >> >> >> >> On Thu, Dec 5, 2013 at 3:55 PM, rauenpc . <[email protected]> wrote: >> >>> If it makes any difference, I applied the same commands to a couple >>> routers in GNS3, and everything worked like a charm so the multilink, >>> virtual-template, and frame-relay related commands under the serial >>> interface seem to be all in order. >>> >>> I also added the commands suggested by Gbenga, but the situation is the >>> same, with the exception that se0/2/0 now shows as being DCE when doing a >>> show interface. >>> >>> >>> On Thu, Dec 5, 2013 at 9:44 AM, Gbenga Olubisi <[email protected] >>> > wrote: >>> >>>> You need to configure frame-relay switching in the global config of one >>>> of the switches e.g R5 >>>> Also configure the serial on that same switch as DCE ---> frame-relay >>>> intf-type dce >>>> >>>> >>>> On Thu, Dec 5, 2013 at 3:36 PM, rauenpc . <[email protected]> wrote: >>>> >>>>> They are both DTE, and if I try to remove the clock rate command on >>>>> either >>>>> side it does nothing. >>>>> >>>>> R5(config-if)#do show int se0/2/0 >>>>> Serial0/2/0 is up, line protocol is up >>>>> Hardware is GT96K Serial >>>>> MTU 1500 bytes, BW 1544 Kbit/sec, DLY 20000 usec, >>>>> reliability 255/255, txload 1/255, rxload 1/255 >>>>> Encapsulation FRAME-RELAY, loopback not set >>>>> Keepalive not set >>>>> CRC checking enabled >>>>> LMI DLCI 1023 LMI type is CISCO frame relay DTE >>>>> FR SVC disabled, LAPF state down >>>>> Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface >>>>> broadcasts 0 >>>>> Last input 01:08:19, output 00:00:10, output hang never >>>>> Last clearing of "show interface" counters 01:08:16 >>>>> Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 >>>>> Queueing strategy: weighted fair >>>>> Output queue: 0/1000/64/0 (size/max total/threshold/drops) >>>>> Conversations 0/1/256 (active/max active/max total) >>>>> Reserved Conversations 0/0 (allocated/max allocated) >>>>> Available Bandwidth 1158 kilobits/sec >>>>> 5 minute input rate 0 bits/sec, 1 packets/sec >>>>> 5 minute output rate 0 bits/sec, 1 packets/sec >>>>> 6560 packets input, 134480 bytes, 0 no buffer >>>>> Received 0 broadcasts, 0 runts, 0 giants, 0 throttles >>>>> 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort >>>>> 6560 packets output, 134480 bytes, 0 underruns >>>>> 0 output errors, 0 collisions, 2 interface resets >>>>> 0 unknown protocol drops >>>>> 0 output buffer failures, 0 output buffers swapped out >>>>> 0 carrier transitions >>>>> DCD=up DSR=up DTR=up RTS=up CTS=up >>>>> >>>>> R5(config-if)# >>>>> R5(config-if)#do show run int se0/2/0 >>>>> Building configuration... >>>>> >>>>> Current configuration : 321 bytes >>>>> ! >>>>> interface Serial0/2/0 >>>>> no ip address >>>>> encapsulation frame-relay >>>>> no keepalive >>>>> clock rate 2000000 >>>>> frame-relay interface-dlci 205 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 222 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 502 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 555 ppp Virtual-Template1 >>>>> end >>>>> >>>>> R5(config-if)#int se0/2/0 >>>>> R5(config-if)#no clock rate 2000000 >>>>> R5(config-if)#do show run int se0/2/0 >>>>> Building configuration... >>>>> >>>>> Current configuration : 321 bytes >>>>> ! >>>>> interface Serial0/2/0 >>>>> no ip address >>>>> encapsulation frame-relay >>>>> no keepalive >>>>> clock rate 2000000 >>>>> frame-relay interface-dlci 205 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 222 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 502 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 555 ppp Virtual-Template1 >>>>> end >>>>> >>>>> R5(config-if)# >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> R2#show int se0/2/0 >>>>> Serial0/2/0 is up, line protocol is up >>>>> Hardware is GT96K Serial >>>>> MTU 1500 bytes, BW 1544 Kbit/sec, DLY 20000 usec, >>>>> reliability 255/255, txload 1/255, rxload 1/255 >>>>> Encapsulation FRAME-RELAY, loopback not set >>>>> Keepalive not set >>>>> CRC checking enabled >>>>> LMI DLCI 1023 LMI type is CISCO frame relay DTE >>>>> FR SVC disabled, LAPF state down >>>>> Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface >>>>> broadcasts 0 >>>>> Last input 01:08:44, output 00:00:31, output hang never >>>>> Last clearing of "show interface" counters 01:08:42 >>>>> Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 >>>>> Queueing strategy: weighted fair >>>>> Output queue: 0/1000/64/0 (size/max total/threshold/drops) >>>>> Conversations 0/1/256 (active/max active/max total) >>>>> Reserved Conversations 0/0 (allocated/max allocated) >>>>> Available Bandwidth 1158 kilobits/sec >>>>> 5 minute input rate 0 bits/sec, 0 packets/sec >>>>> 5 minute output rate 0 bits/sec, 0 packets/sec >>>>> 6560 packets input, 134480 bytes, 0 no buffer >>>>> Received 0 broadcasts, 0 runts, 0 giants, 0 throttles >>>>> 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort >>>>> 6568 packets output, 134644 bytes, 0 underruns >>>>> 0 output errors, 0 collisions, 2 interface resets >>>>> 0 unknown protocol drops >>>>> 0 output buffer failures, 0 output buffers swapped out >>>>> 10 carrier transitions >>>>> DCD=up DSR=up DTR=up RTS=up CTS=up >>>>> >>>>> R2# >>>>> >>>>> R2(config-if)#do show run int se0/2/0 >>>>> Building configuration... >>>>> >>>>> Current configuration : 321 bytes >>>>> ! >>>>> interface Serial0/2/0 >>>>> no ip address >>>>> encapsulation frame-relay >>>>> no keepalive >>>>> clock rate 2000000 >>>>> frame-relay interface-dlci 205 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 222 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 502 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 555 ppp Virtual-Template1 >>>>> end >>>>> >>>>> R2(config-if)#no clock rate 2000000 >>>>> R2(config-if)#do sh run int se0/2/0 >>>>> Building configuration... >>>>> >>>>> Current configuration : 321 bytes >>>>> ! >>>>> interface Serial0/2/0 >>>>> no ip address >>>>> encapsulation frame-relay >>>>> no keepalive >>>>> clock rate 2000000 >>>>> frame-relay interface-dlci 205 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 222 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 502 ppp Virtual-Template1 >>>>> frame-relay interface-dlci 555 ppp Virtual-Template1 >>>>> end >>>>> >>>>> R2(config-if)# >>>>> >>>>> >>>>> On Thu, Dec 5, 2013 at 9:20 AM, Danny Alvarez Uribe < >>>>> [email protected]>wrote: >>>>> >>>>> > Thanks man. Then perhaps it's because the clock rate statement is >>>>> > configured on both ends? Can you post the '"show interface" from >>>>> each side? >>>>> > >>>>> > >>>>> > On Thu, Dec 5, 2013 at 9:09 AM, rauenpc . <[email protected]> wrote: >>>>> > >>>>> >> Being PPPoFR, the serial link needs to remain with encapsulation >>>>> >> frame-relay. The only way to configure "ppp multilink group 1" >>>>> would be to >>>>> >> first set the encapsulation to ppp on the serial interface. >>>>> >> >>>>> >> >>>>> >> On Thu, Dec 5, 2013 at 8:59 AM, Danny Alvarez Uribe < >>>>> [email protected]>wrote: >>>>> >> >>>>> >>> Shouldn't Serial0/2/0 also be on ppp multilink group 1 ? >>>>> >>> >>>>> >>> - Danny >>>>> >>> >>>>> >> >>>>> >> >>>>> > >>>>> _______________________________________________ >>>>> Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos >>>>> :: >>>>> >>>>> iPexpert on YouTube: www.youtube.com/ipexpertinc >>>>> >>>> >>>> >>> >> > _______________________________________________ Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos :: iPexpert on YouTube: www.youtube.com/ipexpertinc
