2610 WIC-2T connection problems

So I got my 2610s, and I got 1 WIC-2T right now, I bought some crossover DB60 to smart serial connector. The DB60 ends are going to my 2501's.

I have tried countless configurations to get these links up, changing the DCE side and so forth, and they wont come up. I found a command on the 2610 S0/X interfaces called physical-layer sync. I applied that command and the smart serial ends came up in loopback, int up, line prot down. The 2501's show no connection at all.

ANything special I need to do since the WIC is Asynch/synch and I just need it to be synch? Im not sure if I have a bad WIC or bad cables (both?) otherwise, I am leaning towards the WIC as the idiot I bought the wic from on ebay has never heard of static bag, and shipped it UPS (United package smashers

).

I hope not, if so these will be the second time I got burned on ebay this month, I bought a 2924 EN and it came DOA, but at least the seller is working with me for a refund.

Find more posts tagged with

Comments

forbesl

johnnynodough wrote:

So I got my 2610s, and I got 1 WIC-2T right now, I bought some crossover DB60 to smart serial connector. The DB60 ends are going to my 2501's.

I have tried countless configurations to get these links up, changing the DCE side and so forth, and they wont come up. I found a command on the 2610 S0/X interfaces called physical-layer sync. I applied that command and the smart serial ends came up in loopback, int up, line prot down. The 2501's show no connection at all.

ANything special I need to do since the WIC is Asynch/synch and I just need it to be synch? Im not sure if I have a bad WIC or bad cables (both?) otherwise, I am leaning towards the WIC as the idiot I bought the wic from on ebay has never heard of static bag, and shipped it UPS (United package smashers ).

I hope not, if so these will be the second time I got burned on ebay this month, I bought a 2924 EN and it came DOA, but at least the seller is working with me for a refund.

Did you check the hardware/software advisor at CCO to ensure your IOS supports WIC-2T?

2lazybutsmart

forbsel, where in CCO do u get this information?

btw, jhonny, have u double checked ur Keepalives? I had some nasty problems with the WIC-2T (yes, I have one on the 2620XM) a few weeks back and I figured out someone played with the Keepalives. It was giving me that up,down on the DCE and down,down on the DTE.

forbesl

2lazybutsmart wrote:

forbsel, where in CCO do u get this information?

http://tools.cisco.com/Support/Fusion/FusionHome.do

You must have the right account privileges to access this..

johnnynodough

Hmmm, it is being detected by the IOS I currently have, but I didnt check the compatibility. Ill do that now.

wildfire

I had real problems with wic-2t and wic-2a/s on a 2612 and 3620, I couldnt get the interface to come up, and when I did show diag it said unknown serial port, put it into a 1720 and it came up straight away. #

I also found that smart serial to db-60 cross overs are a bit hit and miss, the smart serial will work the a slight touch and its gone! you said you changed the dce? the DCE will only be on on end either the smart end or the db60 end you cant change this. What clock rate are you using? I found clock rate 64000 works but anything else has problems.

why dont you post your configs. post your sh runn, show diag, sh contro s?? try doing a shutdown, the loop the no shutthen no loop.

ANything special I need to do since the WIC is Asynch/synch and I just need it to be synch? Im not sure if I have a bad WIC or bad cables (both?) otherwise, I am leaning towards the WIC as the idiot I bought the wic from on ebay has never heard of static bag, and shipped it UPS (United package smashers ).

You said it came up in loopback, this normally suggests you hardware is ok

johnnynodough

According to the comptibility matrix, all versions of IOS are compatible with the WIC-2T whne it is in the onboard slots, any slots in NM's needs IOS Cisco IOS versions 12.0(7)XK, 12.1(1)T, 12.2, 12.2T. Im at 12.3. Just for giggles Im am downloading 12.2T just to see what happens.

johnnynodough

show ver from 2610 that currently hosts module

R5_2610_A#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-I-M), Version 12.3(15), RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Tue 24-May-05 14:01 by ssearch
Image text-base: 0x80008098, data-base: 0x80CD8A7C

ROM: System Bootstrap, Version 12.2(10r)1, RELEASE SOFTWARE (fc1)
ROM: C2600 Software (C2600-I-M), Version 12.3(15), RELEASE SOFTWARE (fc3)

R5_2610_A uptime is 8 minutes
System returned to ROM by power-on
System image file is "flash:c2600-i-mz.123-15.bin"

cisco 2610 (MPC860) processor (revision 0x203) with 28672K/4096K bytes of memory
.
Processor board ID JAD044400T6 (3725282439)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
1 Ethernet/IEEE 802.3 interface(s)
2 Serial(sync/async) network interface(s)
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

R5_2610_A#

The running Config

R5_2610_A#sh run
Building configuration...

Current configuration : 513 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R5_2610_A
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
ip subnet-zero
ip cef
!
!
!
!
!
!
!
interface Ethernet0/0
no ip address
shutdown
half-duplex
!
interface Serial0/0
ip address 1.1.1.1 255.255.255.0
encapsulation ppp
no fair-queue
!
interface Serial0/1
no ip address
shutdown
!
ip http server
ip classless
!
!
!
line con 0
line aux 0
line vty 0 4
!
!
end

R5_2610_A#

Show controller

R5_2610_A#show contr s0/0
Interface Serial0/0
Hardware is PowerQUICC MPC860
DTE Unknown (13) clocks stopped.
idb at 0x815829C8, driver data structure at 0x8158A75C
SCC Registers:
General [GSMR]=0x2:0x00000030, Protocol-specific [PSMR]=0x8
Events [SCCE]=0x0000, Mask [SCCM]=0x001F, Status [SCCS]=0x02
Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E
Interrupt Registers:
Config [CICR]=0x00367F80, Pending [CIPR]=0x00008006
Mask [CIMR]=0x40204000, In-srv [CISR]=0x00000000
Command register [CR]=0x600
Port A [PADIR]=0x1000, [PAPAR]=0xFFFF
[PAODR]=0x0000, [PADAT]=0xE6FE
Port B [PBDIR]=0x09C0F, [PBPAR]=0x0000E
[PBODR]=0x00000, [PBDAT]=0x3E77D
Port C [PCDIR]=0x00C, [PCPAR]=0x000
[PCSO]=0x820, [PCDAT]=0xFC0, [PCINT]=0x00F
Receive Ring
rmd(680126B0): status 9000 length 60C address 1C54F44
rmd(680126B

: status 9000 length 60C address 1C548C4
rmd(680126C0): status 9000 length 60C address 1C54244
rmd(680126C

: status 9000 length 60C address 1C53BC4
rmd(680126D0): status 9000 length 60C address 1C53544
rmd(680126D

: status 9000 length 60C address 1C52EC4
rmd(680126E0): status 9000 length 60C address 1C52844
rmd(680126E

: status 9000 length 60C address 1C521C4
rmd(680126F0): status 9000 length 60C address 1C51B44
rmd(680126F

: status 9000 length 60C address 1C514C4
rmd(68012700): status 9000 length 60C address 1C50E44
rmd(6801270

: status 9000 length 60C address 1C507C4
rmd(68012710): status 9000 length 60C address 1C50144
rmd(6801271

: status 9000 length 60C address 1C4FAC4
rmd(68012720): status 9000 length 60C address 1C4F444
rmd(6801272

: status 9000 length 60C address 1C4EDC4
rmd(68012730): status 9000 length 60C address 1C4E744
rmd(6801273

: status 9000 length 60C address 1C4E0C4
rmd(68012740): status 9000 length 60C address 1C4DA44
rmd(6801274

: status 9000 length 60C address 1C4D3C4
rmd(68012750): status 9000 length 60C address 1C4CD44
rmd(6801275

: status 9000 length 60C address 1C4C6C4
rmd(68012760): status 9000 length 60C address 1C4C044
rmd(6801276

: status B000 length 60C address 1C4B9C4
Transmit Ring
tmd(68012770): status 0 length E address 0
tmd(6801277

: status 0 length E address 0
tmd(68012780): status 0 length E address 0
tmd(6801278

: status 0 length E address 0
tmd(68012790): status 0 length E address 0
tmd(6801279

: status 0 length E address 0
tmd(680127A0): status 0 length E address 0
tmd(680127A

: status 0 length E address 0
tmd(680127B0): status 0 length E address 0
tmd(680127B

: status 0 length E address 0
tmd(680127C0): status 0 length 0 address 0
tmd(680127C

: status 0 length 0 address 0
tmd(680127D0): status 0 length 0 address 0
tmd(680127D

: status 0 length 0 address 0
tmd(680127E0): status 0 length 0 address 0
tmd(680127E

: status 2000 length 0 address 0

tx_limited=0(16)

SCC GENERAL PARAMETER RAM (at 0x68013C00)
Rx BD Base [RBASE]=0x26B0, Fn Code [RFCR]=0x18
Tx BD Base [TBASE]=0x2770, Fn Code [TFCR]=0x18
Max Rx Buff Len [MRBLR]=1548
Rx State [RSTATE]=0x0, BD Ptr [RBPTR]=0x26B0
Tx State [TSTATE]=0x0, BD Ptr [TBPTR]=0x2770

SCC HDLC PARAMETER RAM (at 0x68013C3

CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8
Errors: CRC [CRCEC]=0, Aborts [ABTSC]=0, Discards [DISFC]=0
Nonmatch Addr Cntr [NMARC]=0
Retry Count [RETRC]=0
Max Frame Length [MFLR]=1524
Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=0
User-defined Address 0000/0000/0000/0000
User-defined Address Mask 0x0000

buffer size 1524

PowerQUICC SCC specific errors:
0 input aborts on receiving flag sequence
0 throttles, 0 enables
0 overruns
0 transmitter underruns
0 transmitter CTS losts
0 aborted short frames

Show interface

R5_2610_A#sh int s0/0
Serial0/0 is up, line protocol is down
Hardware is PowerQUICC Serial
Internet address is 1.1.1.1/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP REQsent, loopback not set
Keepalive set (10 sec)
Last input never, output 00:04:03, output hang never
Last clearing of "show interface" counters 00:04:42
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 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
53 packets output, 742 bytes, 0 underruns
0 output errors, 0 collisions, 14 interface resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up

[/b]

johnnynodough

Now the 2501 end is just as it should be, no clock rate, encap ppp , ip is 1.1.1.2/24 (even though at this point its a moot point since I cant get a layer 1 link) and its status is down and down.

johnnynodough

It doesnt show the clock rate even though I set it. I think I have a bad wic.

johnnynodough

Here is the show diag, i just tried monkying around with loop/no loop and shut/no shut with no change. It only loops when I apply the physical-layer-link sync command.

R5_2610_A#show diag 0
Slot 0:
C2610 1E Mainboard Port adapter, 3 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 2.3
PCB Serial Number : JAD044400T6 (3725282439)
Part Number : 73-2839-13
RMA History : 00
RMA Number : 0-0-0-0
Board Revision : C0
Deviation Number : 0-0
Product (FRU) Number : C2610 - 1E
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 00 91 41 02 03 C1 18 4A 41 44 30 34 34
0x10: 34 30 30 54 36 20 28 33 37 32 35 32 38 32 34 33
0x20: 39 29 82 49 0B 17 0D 04 00 81 00 00 00 00 42 43
0x30: 30 80 00 00 00 00 FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

WIC Slot 0:
Serial 2T (12in1)
Hardware revision 1.0 Board revision B0
Serial number 14844465 Part number 800-03181-01
FRU Part Number WIC-2T=

Test history 0x0 RMA number 00-00-00
Connector type PCI
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 12 01 00 00 E2 82 31 50 0C 6D 01 00 00 00 00
0x30: 58 00 00 00 99 06 30 00 FF FF FF FF FF FF FF FF

R5_2610_A#

johnnynodough

Im starting to think these WICs are more trouble than they are worth, I just bought a WIC 1T, well see what happens with that. If I still have problems I will just go with a NM-4A/S, but I really wanted to put a NM-4E in these guys, but I guess I will just do that with the 3620, at least I can get FE modules for it

wildfire

Thats wierd because

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

this means as you say your layer one singnalling is up and the interface it up, just line protocol down it normally either a clock or encapsulation issue, try using the default encap, so "no ecnapsulation ppp"

Its strange how it wont take you clock rate command in, try removing the cable then putting the command in both routers then reinsert the cable.

johnnynodough

assigning the clock rate without the cable connected worked, it shows the clock rate in the running config now, but still no connection.

johnnynodough

AFter I changed back to HDLC the clock rate magically dissapeared from the running config. This sucks.

wildfire

what IOS are you running, that happend to me on an early release development of 12.1 when I went from ppp to hdlc it lost the command.

I take it not you have gone to hdlc it wont take the command? try taking the cable of, assing the clock rate, save config, reload, then no shut then put the cable on.

johnnynodough

Its 12.3 and I rolled back to 12.2T to check, but no change. I am getting a V.35 DCE to smart serial cable and will hook that up to a V.35 to DB60 DTE cable and see what happens. They are both Cisco made so I will trust the results more than these cross over cables. I have a WIC-1T coming but I realized that it has a DB60 connector, so that wont help me troubleshoot the cable.

johnnynodough

OK, got my hands on a Cisco made V.35 to SS DTE cable today, linked it to a Cisco V.35 to DB 60 DCE cable. Very interesting results.

On S0/0, I can get a link light, I can get the int up, cant get LP up at all, no activity whatsoever on the router on the other end. HDLC or PPP. Same as using the DB60/SS crossover cable.

Now on S0/1. I get the link light again, and I can get the int and LP up as before, but on the 2501, I get a link this time, I get the int up, and the link light goes totally ape$hit! When using PPP i can debug PPP events and LCP is trying like a mad fool to setup the link, but nigh a reply from the WIC2T. I switch to HDLC and the link light still goes nuts, but nothing tangible to debug.

So this leads me to 2 conclusions, the WIC is for definetely bad, and at least one of the cross over cables are bad.

Im done with these WIC-2T;s, and I am done buying cisco gear from people that havent sold it before. I lucked out with this one though, the seller already refunded me so this sucker is going out tomorrow.

I just hope this didnt fry the serial port on my 2501

Yankee

I have a couple hundred WIC-2Ts in the production network in a variety of platforms and they have never been an issue. Maybe a couple have had a problem over the years but I wouldn't give up on them

Yankee

2lazybutsmart

Yankee wrote:

I have a couple hundred WIC-2Ts in the production network

200 serial links??? now isn't that some real production environment.

get any sleep?

2lbs.

johnnynodough

Got my NM-4A today, slapped it in, connected everything up, no problemo. I just wish I didnt have to take up a whole module expansion slot for serial connections since there arent ethernet WICs available for the 2600's. WIC1T should be here next week for the other 2610.

BTW, my record for buying functional back to back DB60 cables is 100% 5/5 have worked.

heathric

interface FastEthernet0/0
description **** Connection to ETH WHATEVER *****
ip address 1.1.1.1 255.255.255.0
no cdp enable
NO SHUT
!
interface Serial0/0/0
no ip address
encapsulation frame-relay IETF
frame-relay lmi-type ansi
load-interval 30
NO SHUT
!
interface Serial0/0/0.888 point-to-point
description ****NMO TO WHATEVER****
ip address 2.2.2.2 255.255.255.252
ip ospf authentication-key 999
ip ospf mtu-ignore
no cdp enable
frame-relay interface-dlci 999
NO SHUT
!
router ospf 200
router-id 1.1.1.1
log-adjacency-changes
area 10.10.10.10 authentication message-digest
timers throttle spf 2000 3000 3000
network 1.1.1.1 0.0.0.0 area 10.10.10.10
network 2.2.2.2 0.0.0.3 area 10.10.10.10
maximum-paths 2
!

keenon

i should have jumped in on this earlier the wic2t will not work unless there is a fast ethernet port on the device.. i learned this the hard way

if possible get a 2620 it will work just fine

EdTheLad

keenon wrote:

i should have jumped in on this earlier the wic2t will not work unless there is a fast ethernet port on the device.. i learned this the hard way

if possible get a 2620 it will work just fine

I have 4 2610's here with WIC-2Ts in all, they work fine for me.

wildfire

Ive just checked again, it works in my 2612, but not my 2610, it also wont work on my NM's on my 3600's.

http://www.cisco.com/warp/public/107/wic-2t.shtml