WIC2T interface problems

westwoodwestwood Member Posts: 5 ■□□□□□□□□□
Hey guys,

So I finally got my lab setup, only to find that one interface on my WIC2T is causing me problems.

I am using a back to back connection with HDLC.

The configuration thus is fairly simple, and I have verified it works on my other interface(s).

The problem interface (s0/0) on my 1760 router seems to never come up and I get "Serial0/0 is down, line protocol is down".

When I tested the same WIC on my 2610XM I am able to get "Serial0/0 is up, line protocol is down" with the line protocol flapping up and down over and over again.

From what I have read, this is likely caused by a physical hardware problem, but I thought I would post on here to see if anyone has anymore ideas or troubleshooting advice.

Thanks all!

Comments

  • lantechlantech Member Posts: 329
    What are the configurations on the interfaces for your routers?
    2012 Certification Goals

    CCENT: 04/16/2012
    CCNA: TBD
  • westwoodwestwood Member Posts: 5 ■□□□□□□□□□
    R2: (problem interface)

    r2#sh ru
    ....
    interface Serial0/0
    ip address 192.168.1.19 255.255.255.0
    ....


    r2>sh int s0/0
    Serial0/0 is down, line protocol is down
    Hardware is PowerQUICC Serial
    Internet address is 192.168.1.19/24
    MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation HDLC, loopback not set
    .....


    r2>sh controllers s0/0
    Interface Serial0/0
    Hardware is PowerQUICC MPC860
    DTE Unknown (13) TX and RX clocks detected.
    idb at 0x81577B98, driver data structure at 0x81556FF0
    ...


    R3
    r3#sh ru
    ....
    interface Serial1/0
    ip address 192.168.1.15 255.255.255.0
    clockrate 64000



    r3#sh int s1/0
    Serial1/0 is up, line protocol is down
    Hardware is PowerQUICC Serial
    Internet address is 192.168.1.15/24
    MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation HDLC, loopback not set
    Keepalive set (10 sec)
    ....


    r3#sh controllers s1/0
    Interface Serial1/0
    Hardware is PowerQUICC MPC860
    DCE V.35, clock rate 64000
    ....
  • SteveO86SteveO86 Member Posts: 1,423
    westwood wrote: »
    R2: (problem interface)


    r2>sh controllers s0/0
    Interface Serial0/0
    Hardware is PowerQUICC MPC860
    DTE Unknown (13) TX and RX clocks detected.
    idb at 0x81577B98, driver data structure at 0x81556FF0
    ...


    r3#sh controllers s1/0
    Interface Serial1/0
    Hardware is PowerQUICC MPC860
    DCE V.35, clock rate 64000
    ....

    R2 is seeing the clocking form R3, but R2's DTE is showing unknown, does this cable work with other WICs? Might want to check for the sh controller output on R2 for aborts/errors, looks to be hardware issue.


    I actually spent an hour last night troubleshooting one of my own WIC-2T's. I moved my WIC-2T to multiple routers, multiple cables, multiple encapsulation, and my interface consistantly flaps up/down
    My Networking blog
    Latest blog post: Let's review EIGRP Named Mode
    Currently Studying: CCNP: Wireless - IUWMS
  • westwoodwestwood Member Posts: 5 ■□□□□□□□□□
    SteveO86 wrote: »
    R2 is seeing the clocking form R3, but R2's DTE is showing unknown, does this cable work with other WICs? Might want to check for the sh controller output on R2 for aborts/errors, looks to be hardware issue.

    The cable seems to be fine because it works with other interfaces and other cards with the same configuration.
    SteveO86 wrote: »
    I actually spent an hour last night troubleshooting one of my own WIC-2T's. I moved my WIC-2T to multiple routers, multiple cables, multiple encapsulation, and my interface consistantly flaps up/down

    This is the exact type of testing I have been doing as well.
  • Ltat42aLtat42a Member Posts: 587 ■■■□□□□□□□
Sign In or Register to comment.