8 Replies Latest reply: Dec 27, 2011 4:45 AM by Ryanlk18 RSS

    OSPF Adjacency problem

    Mike Jamrog

      Has anyone seen anything like this before.

       

      Dec 15 18:37:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

      Dec 15 18:37:11: %OSPF-5-ADJCHG: Process 1, Nbr 10.1.1.1 on Serial0/1/0:0 from DOWN to INIT, Received Hello

      Dec 15 18:38:11: %OSPF-5-ADJCHG: Process 1, Nbr 10.1.1.1 on Serial0/1/0:0 from INIT to DOWN, Neighbor Down: Dead timer expired

      Dec 15 18:38:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down

      Dec 15 18:38:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

      Dec 15 18:38:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down

      Dec 15 18:38:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

      Dec 15 18:39:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down

      Dec 15 18:39:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

      Dec 15 18:39:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down

      Dec 15 18:39:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

      Dec 15 18:40:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down

      Dec 15 18:40:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

      Dec 15 18:40:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down

      Dec 15 18:40:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

      Dec 15 18:41:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down

      Dec 15 18:41:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

      Dec 15 18:41:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down

      Dec 15 18:41:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up

       

       

      These are logs from a Cisco 3925 IRS router.  Sitting at the other end is a Cisco 2611XM connected via a T1.

       

      I have't ran a debug ip ospf adjancency yet, because I have to wait until after hours.

       

      What I am doing is migrating the 2611XM off from a Cisco 3660 to a Cisco 3925.

       

      I have checked all the common things.  Correct subnet/masks, correct hello and dead timers.

        • 1. Re: OSPF Adjacency problem
          Vijay Swaminathan

          Hi Mike,

           

          Looks like you have a problem in forming OSPF neighborship.

           

          You are not receiving hello packets from the neighboring router.

           

          Can you pls share the configuration of your current and the remote router? That will help us in troubleshooting your problem

           

          -Vijay

          • 2. Re: OSPF Adjacency problem
            Scott Morris - CCDE/4xCCIE/2xJNCIE

            It's every 20 seconds down and up in 10 seconds, and it's a serial thing.

             

            You have a keepalive mismatch on your serial link....  OSPF isn't getting a chance yet.

             

            Scott

            • 3. Re: OSPF Adjacency problem
              Mike Jamrog

              I have checked all the serial links.

               

              The link on the new 3925:

              3925-1#show interfaces serial 0/1/0:0

              Serial0/1/0:0 is down, line protocol is down

                Hardware is DSX1

                Description: Midland to 555 Wackerly

                Internet address is 10.128.255.13/30

                MTU 1500 bytes, BW 1536 Kbit/sec, DLY 20000 usec,

                   reliability 252/255, txload 1/255, rxload 1/255

                Encapsulation HDLC, crc 16, loopback not set

                Keepalive set (10 sec)

                Last input 5d21h, output 5d21h, output hang never

                Last clearing of "show interface" counters never

                Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 9

                Queueing strategy: Class-based queueing

                Output queue: 0/1000/0 (size/max total/drops)

                5 minute input rate 0 bits/sec, 0 packets/sec

                5 minute output rate 0 bits/sec, 0 packets/sec

                   38 packets input, 2302 bytes, 0 no buffer

                   Received 35 broadcasts (0 IP multicasts)

                   0 runts, 1 giants, 0 throttles

                   3 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

                   89 packets output, 12964 bytes, 0 underruns

                   0 output errors, 0 collisions, 11 interface resets

                   0 unknown protocol drops

                   0 output buffer failures, 0 output buffers swapped out

                   2 carrier transitions

               

              The other end of the of the 3925 which is the 2611XM:

              2611XM#show interface s0/0

              Serial0/0 is up, line protocol is up

                Hardware is PQUICC with Fractional T1 CSU/DSU

                Description: 555 to Midland1

                Internet address is 10.128.255.14/30

                MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

                   reliability 255/255, txload 3/255, rxload 2/255

                Encapsulation HDLC, loopback not set

                Keepalive set (10 sec)

                Last input 00:00:00, output 00:00:00, output hang never

                Last clearing of "show interface" counters never

                Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 12086

                Queueing strategy: weighted fair

                Output queue: 0/1000/64/12086 (size/max total/threshold/drops)

                   Conversations  0/62/256 (active/max active/max total)

                   Reserved Conversations 1/1 (allocated/max allocated)

                   Available Bandwidth 646 kilobits/sec

                5 minute input rate 15000 bits/sec, 18 packets/sec

                5 minute output rate 20000 bits/sec, 21 packets/sec

                   10399082 packets input, 2440290477 bytes, 0 no buffer

                   Received 59578 broadcasts, 0 runts, 0 giants, 0 throttles

                   3 input errors, 2 CRC, 1 frame, 0 overrun, 0 ignored, 0 abort

                   12516047 packets output, 3469474287 bytes, 0 underruns

                   0 output errors, 0 collisions, 2 interface resets

                   0 output buffer failures, 0 output buffers swapped out

                   1 carrier transitions

                   DCD=up  DSR=up  DTR=up  RTS=up  CTS=up

               

               

              And even the old 3660 which is currently up and running with the 2611XM:

              3660-1#show interface serial 4/0

              Serial4/0 is up, line protocol is up

                Hardware is DSCC4 with integrated T1 CSU/DSU

                Description: Midland to 555

                Internet address is 10.128.255.13/30

                MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

                   reliability 255/255, txload 3/255, rxload 3/255

                Encapsulation HDLC, loopback not set

                Keepalive set (10 sec)

                Last input 00:00:02, output 00:00:00, output hang never

                Last clearing of "show interface" counters never

                Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 66511

                Queueing strategy: Class-based queueing

                Output queue: 0/1000/64/66484 (size/max total/threshold/drops)

                   Conversations  0/67/256 (active/max active/max total)

                   Reserved Conversations 1/1 (allocated/max allocated)

                   Available Bandwidth 646 kilobits/sec

                5 minute input rate 20000 bits/sec, 20 packets/sec

                5 minute output rate 19000 bits/sec, 17 packets/sec

                   69859922 packets input, 2193968122 bytes, 0 no buffer

                   Received 311455 broadcasts, 0 runts, 29 giants, 0 throttles

                   333 input errors, 47 CRC, 285 frame, 0 overrun, 0 ignored, 1 abort

                   57104026 packets output, 864454910 bytes, 0 underruns

                   0 output errors, 0 collisions, 58 interface resets

                   0 output buffer failures, 0 output buffers swapped out

                   9 carrier transitions

                   DCD=up  DSR=up  DTR=up  RTS=up  CTS=up

               

               

              The serial keepalives are all set to 10 seconds.

              • 4. Re: OSPF Adjacency problem
                Brian

                This is not an OSPF problem, but a serial connection problem.  Take a look at the output of your "sh int s0/1/0:0" command on the 3925.

                 

                3925-1#show interfaces serial 0/1/0:0
                Serial0/1/0:0 is down, line protocol is down

                 

                it is showing as "Down/Down".  I would check the configuration of the T1 controller on the 3925 as well as a possible cabling problem.  Do you have the correct pin out for the T1 cable on the 3925 side?  Did you configure the T1 controller with the correct framing, line code, number of channels and clocking?

                 

                Can you provide the output of the "sh run" command for each router.

                 

                Brian

                • 5. Re: OSPF Adjacency problem
                  Mike Jamrog

                  The reason this is down, is because I don't have the link on the 3925.  Since an adjacency could not be formed, I put the link back on the 3660.  So, yes I know the link is down, its supposed to be.

                   

                  Thanks

                  • 6. Re: OSPF Adjacency problem
                    Brian

                    Ok, this was not clear from your previous posts.  So, when you had the 3925 connected to the 2611XM via the T1, what was the state of the interfaces?  Can you provide the configuration for the 2611Xm and 3925 regarding the T1 controller and serial interfaces.  Thanks.

                     

                    Brian

                     

                    • 7. Re: OSPF Adjacency problem
                      Scott Morris - CCDE/4xCCIE/2xJNCIE

                      You also have some CRC and framing errors which may account for your interface resets...

                       

                      Strange that it's on the timeline noted above, but may just be coincidence!

                       

                      But it's a physical problem someplace.

                       

                      Scott

                      • 8. Re: OSPF Adjacency problem
                        Ryanlk18

                        I have a similar problem.  I have a 3662 router with a T1CSU module that goes to a T1 line to a 3640 with the same module.  When I upgraded the 3662 to a 3845 with the 8CE1T1 PRI module, my serial interface drops randomly.

                         

                        The drops do not occur at a given interval and my interface runs clean until the it drops and then I take input and CRC errors.  I'm going tomorrow to the remote location to swap back to the 3662 to see if the problem clears up, but I'm at a loss.

                         

                        The Telco came out and looked at the line and said they were running clean.  They were running dirty at first, but they swapped pairs on the T1 and then said it was clean.

                         

                        Mike, did you ever get this figured out?