orus
asked on
VWIC-2MFT-T1 question
Is it possible for a VWIC-2MFT-T1(3640), to connect to a WIC-1DSU-T1 (2621xm)? This is a lab setup and the routers are interconnected via a homemade t1 crossover.
k. Serial interface is up, but line protocol is down. Cable definitely works, tried it on other routers.
Both routers' clock source is line
2621xm is defining clock rate
framing is esf
line code bz8
Is this a compatibility issue
k. Serial interface is up, but line protocol is down. Cable definitely works, tried it on other routers.
Both routers' clock source is line
2621xm is defining clock rate
framing is esf
line code bz8
Is this a compatibility issue
ASKER
You are right, I see lots of slips on the 3640 with the dual card. So what do I need to do to resolve? . I think the 3640 only supports using one interface of the two port cards (limitation I believe I read about). Anyway, the 3640's config is in the code snippet below, with some sh commands. Here is the 2621xm config (single wic t1):
interface Serial0/0
description ***Connected to SL PE's s0/0:1 interface***
ip address 112.1.1.1 255.255.255.252
encapsulation ppp
tag-switching ip
service-module t1 clock source internal
service-module t1 timeslots 24
I have attached the 3640s config in the snippet here
interface Serial0/0
description ***Connected to SL PE's s0/0:1 interface***
ip address 112.1.1.1 255.255.255.252
encapsulation ppp
tag-switching ip
service-module t1 clock source internal
service-module t1 timeslots 24
I have attached the 3640s config in the snippet here
!
controller T1 0/0
framing esf
linecode b8zs
channel-group 1 timeslots 24
!
controller T1 0/1
framing sf
linecode ami
!
!
!
!
!
sl-mpls-pe#sh int s0/0:1
Serial0/0:1 is up, line protocol is down
Hardware is QUICC Serial
Internet address is 112.1.1.2/30
MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Listen, loopback not set
Keepalive set (10 sec)
Last input never, output 00:00:17, output hang never
Last clearing of "show interface" counters 02:04:21
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 42 kilobits/sec
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, 187 giants, 0 throttles
242 input errors, 8 CRC, 84 frame, 0 overrun, 0 ignored, 150 abort
1490 packets output, 20860 bytes, 0 underruns
0 output errors, 0 collisions, 398 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Timeslot(s) Used:24, SCC: 0, Transmitter delay is 0 flags
sl-mpls-pe#
sl-mpls-pe#sh controller t1 0/0
T1 0/0 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info Firmware: 20051006, FPGA: 20, spm_count = 0
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
Data in current interval (579 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
531 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
531 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 1:
0 Line Code Violations, 0 Path Code Violations
900 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 2:
0 Line Code Violations, 0 Path Code Violations
900 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 3:
0 Line Code Violations, 0 Path Code Violations
900 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 4:
0 Line Code Violations, 0 Path Code Violations
900 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 5:
0 Line Code Violations, 0 Path Code Violations
900 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 6:
0 Line Code Violations, 0 Path Code Violations
900 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 7:
0 Line Code Violations, 0 Path Code Violations
900 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 8:
0 Line Code Violations, 0 Path Code Violations
900 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 9:
0 Line Code Violations, 0 Path Code Violations
138 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
138 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 72 Unavail Secs
Data in Interval 10:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 11:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 12:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 13:
1 Line Code Violations, 3047 Path Code Violations
1 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
1 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs, 6 Unavail Secs
Data in Interval 14:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 15:
0 Line Code Violations, 978 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 541 Unavail Secs
Data in Interval 16:
114 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
Data in Interval 17:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
Total Data (last 17 15 minute intervals):
115 Line Code Violations, 4025 Path Code Violations,
7339 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins,
7339 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs, 2419 Unavail Secs
sl-mpls-pe#
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I dont have the "clock source primary" option. Its free-running, internal or line
Note: The 2-port E1 Multiflex Trunk VWICs has only one shared clocking domain between the two E1 controllers. So, if both E1 controllers are configured to derive clocking from the line, the clock references received must be synchronous. Otherwise, timing slips will occur on at least one of the controllers. If the clocking sources are pleisochronous and one controller is configured for "clock source line primary" and the other for "clock source line", it is likely the second controller will exhibit controlled slips in the output of the "show controllers E1" command. This behaviour is a hardware limitation of the 2-port E1 Multiflex Trunk VWIC product and is by design. However, independent clocking sources can be supported on the 2-port T1/E1 VWIC2 product when both controllers are used for data-only purposes.
http://www.cisco.com/en/US/products/hw/routers/ps274/products_tech_note09186a00800b6e0f.shtml