From: Lillemor Hamnqvist (lillemor@hamnqvist.org)
Date: Tue Feb 04 2003 - 22:55:13 GMT-3
Changing the framing on the remote side from non-crc4 to crc4 (to match the
local ISP) solved the problem.
-----Original Message-----
From: Tim Fletcher [mailto:tim@fletchmail.net]
Sent: Thursday, January 30, 2003 4:29 PM
To: Lillemor Hamnqvist
Subject: RE: T1 installation, 3660, VWIC-2MFT-T1-D1
As I've said before, I don't know anything about E1s, but I would be
suspicious of the "speed 64". It wasn't all that long ago that a 64K
channel on a T1 was the exception. I have no idea whether E1s support 64K
channels or not. Even if they do, there may be a link in the middle
somewhere that doesn't.
I'm pretty sure if you change to AMI you will also have to change to 56K.
If I recall correctly, with AMI you need the signalling bits to maintain 1s
density, hence only 56K. It's been a while, so I may be wrong about this.
-Tim Fletcher
At 03:13 PM 1/30/2003 -0500, you wrote:
>I have pointed out the 'path code violation' to the provider but they can
>not see any problem on there side. That is why we are changing the line
code
>to AMI so that it is matching both side.
>The strange thing is that the loopback tests works, I ping and see the
>counters on the remote side increasing. But the without the loop the
>keepalive is not going over.
>
>-----Original Message-----
>From: Tim Fletcher [mailto:tim@fletchmail.net]
>Sent: Thursday, January 30, 2003 2:59 PM
>To: Chuck Church; Lillemor Hamnqvist; ccielab@groupstudy.com
>Subject: Re: T1 installation, 3660, VWIC-2MFT-T1-D1
>
>
>If you look back at the original email, the config shows only channels 1-8
>in use, so there shouldn't be a problem mapping 8 T1 channels to 8 E1
>channels. I never touched an E1 before either, but since you can't get a T1
>in Europe and you can't an E1 in North America, and there are probably
>thousands of trans Atlantic data circuits I figure it's been done before.
>
>If you look at the sh contr t1 there are several errors. The counts are
>low, so they may just be the result of the controller synching up. Do a
>clear counters and check it again in 5 or 10 minutes.
>
>What's the config on the other side look like?
>
>-Tim Fletcher
>
>At 02:03 PM 1/30/2003 -0500, Chuck Church wrote:
> >I've never touched an E1 before, but it seems to me that if the T1 side
is
> >using channels 1-24, you'd want the E1 side to only use those as well,
> >right? I don't see how any 'mapping' function could magically create a
>half
> >megabit from thin air. Can you tell the E1 side to use only 1-24?
> >
> >Chuck Church
> >CCIE #8776, MCNE, MCSE
> >
> >
> >----- Original Message -----
> >From: "Lillemor Hamnqvist" <lillemor@hamnqvist.org>
> >To: <ccielab@groupstudy.com>
> >Sent: Thursday, January 30, 2003 11:15 AM
> >Subject: RE: T1 installation, 3660, VWIC-2MFT-T1-D1
> >
> >
> > > Its an international line. The Carrier is taking care of the mapping
>from
> >T1
> > > to E1(at least they are claiming that).
> > > When I do loop tests I see the counter on the remote router
increasing.
>So
> > > the ping packets arrives. But when I remote the loopback, the link
> >protocol
> > > do not get any keepalive from remote side and link goes down.
Something
>is
> > > not matching. Could it be the E1-T1 mapping ?
> > >
> > > -----Original Message-----
> > > From: Paul Lalonde [mailto:plalonde2@cogeco.ca]
> > > Sent: Thursday, January 30, 2003 11:12 AM
> > > To: Lillemor Hamnqvist; ccielab@groupstudy.com
> > > Subject: Re: T1 installation, 3660, VWIC-2MFT-T1-D1
> > >
> > >
> > > Are you connecting T1 to E1???
> > >
> > > Different framing, different linecoding... isn't that apples to
>oranges???
> > >
> > > Anyone?
> > >
> > > Paul
> > > ----- Original Message -----
> > > From: "Lillemor Hamnqvist" <lillemor@hamnqvist.org>
> > > To: <ccielab@groupstudy.com>
> > > Sent: Thursday, January 30, 2003 10:52 AM
> > > Subject: Re: T1 installation, 3660, VWIC-2MFT-T1-D1
> > >
> > >
> > > > SRS#
> > > > SRS#sh int s2/0:0
> > > > Serial2/0:0 is up, line protocol is down
> > > > Hardware is DSX1
> > > > Internet address is 10.1.1.2/24
> > > > MTU 1500 bytes, BW 512 Kbit, DLY 20000 usec,
> > > > reliability 255/255, txload 1/255, rxload 1/255
> > > > Encapsulation HDLC, loopback not set
> > > > Keepalive set (10 sec)
> > > > Last input 00:01:05, output 00:00:05, output hang never
> > > > Last clearing of "show interface" counters 00:12:05
> > > > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output
drops:
> >127
> > > > 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 384 kilobits/sec
> > > > 5 minute input rate 0 bits/sec, 0 packets/sec
> > > > 5 minute output rate 0 bits/sec, 0 packets/sec
> > > > 159 packets input, 472277 bytes, 0 no buffer
> > > > Received 178 broadcasts, 0 runts, 0 giants, 0 throttles
> > > > 0 input errors, 6 CRC, 0 frame, 0 overrun, 0 ignored, 1 abort
> > > > 164 packets output, 125726 bytes, 0 underruns
> > > > 0 output errors, 0 collisions, 2 interface resets
> > > > 0 output buffer failures, 0 output buffers swapped out
> > > > 11 carrier transitions
> > > > SRS#sh cont e1
> > > > E1 2/0 is up.
> > > > Applique type is Channelized E1 - balanced
> > > > No alarms detected.
> > > > alarm-trigger is not set
> > > > Version info Firmware: 20001015, FPGA: 15
> > > > Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
> > > > Data in current interval (759 seconds elapsed):
> > > > 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
> > > > SRS#sh
> > > > callpmr#sh cont t1 1/0
> > > > T1 1/0 is up.
> > > > Applique type is Channelized T1
> > > > Cablelength is long gain36 0db
> > > > Description: ATT International T1
> > > > No alarms detected.
> > > > alarm-trigger is not set
> > > > Version info Firmware: 20001015, FPGA: 15
> > > > Framing is ESF, Line Code is B8ZS, Clock Source is Line.
> > > > Data in current interval (796 seconds elapsed):
> > > > 1 Line Code Violations, 24 Path Code Violations
> > > > 1 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
> > > > 0 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs, 0
Unavail
> > > Secs
> > > > callpmr#
> > > > callpmr#sh int s1/0:0
> > > > Serial1/0:0 is up, line protocol is down
> > > > Hardware is DSX1
> > > > Internet address is 10.1.1.1/24
> > > > MTU 1500 bytes, BW 512 Kbit, DLY 20000 usec,
> > > > reliability 255/255, txload 1/255, rxload 1/255
> > > > Encapsulation HDLC, loopback not set
> > > > Keepalive set (10 sec)
> > > > Last input 00:03:23, output 00:00:03, output hang never
> > > > Last clearing of "show interface" counters 00:14:14
> > > > 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 384 kilobits/sec
> > > > 5 minute input rate 0 bits/sec, 0 packets/sec
> > > > 5 minute output rate 0 bits/sec, 0 packets/sec
> > > > 237 packets input, 352509 bytes, 0 no buffer
> > > > Received 176 broadcasts, 0 runts, 0 giants, 0 throttles
> > > > 0 input errors, 18 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
> > > > 258 packets output, 134430 bytes, 0 underruns
> > > > 0 output errors, 0 collisions, 4 interface resets
> > > > 0 output buffer failures, 0 output buffers swapped out
> > > > 1 carrier transitions
> > > > callpmr#
> > > > -----Original Message-----
> > > > From: Chuck Church [mailto:ccie8776@rochester.rr.com]
> > > > Sent: Thursday, January 30, 2003 10:27 AM
> > > > To: Lillemor Hamnqvist; ccielab@groupstudy.com
> > > > Subject: Re: Re: T1 installation, 3660, VWIC-2MFT-T1-D1
> > > >
> > > >
> > > > Send us your:
> > > > 'sh run int x' where x is the interface the T1 is using, such as
>s1,
> > > etc.
> > > > 'sh int x'
> > > > 'sh service-m x'
> > > >
> > > > from both routers.
> > > >
> > > > Chuck Church
> > > > CCIE #8776, MCNE, MCSE
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Lillemor Hamnqvist" <lillemor@hamnqvist.org>
> > > > To: <ccielab@groupstudy.com>
> > > > Sent: Thursday, January 30, 2003 8:43 AM
> > > > Subject: RE: Re: T1 installation, 3660, VWIC-2MFT-T1-D1
> > > >
> > > >
> > > > > HI again,
> > > > > Any more suggestion way a serial interface is not coming up in
>up-up.
> > > What
> > > > > debug command could help me. I'm stuck ... The control T1 shows
up,
>no
> > > > > alarms.
> > > > > Thank you,
> > > > > /lillemor
> > > > >
> > > > > -----Original Message-----
> > > > > From: bobdu11@cox.net [mailto:bobdu11@cox.net]
> > > > > Sent: Tuesday, January 28, 2003 1:30 PM
> > > > > To: Chuck Church; Lillemor Hamnqvist; ccielab@groupstudy.com
> > > > > Subject: Re: Re: T1 installation, 3660, VWIC-2MFT-T1-D1
> > > > >
> > > > >
> > > > >
> > > > > > Check your pinouts in the Smartjack. I had that happen to me
> >before,
> > > > the
> > > > > pins were reversed from the way they were supposed to be. Even
>though
> > > > Loops
> > > > > from the smartjack back to the Carrier were good, the circuit
would
> > > still
> > > > > not come up when connected end to end. This of course is if your
> >serial
> > > > > line is showing dwn/dwn when connected. If it's showing up/down
>then
> > > > you've
> > > > > got configuration issues....Bob
> > > > >
> > > > >
> > > > > > From: "Chuck Church" <ccie8776@rochester.rr.com>
> > > > > > Date: 2003/01/28 Tue AM 09:41:22 EST
> > > > > > To: "Lillemor Hamnqvist" <lillemor@hamnqvist.org>,
> > > > > <ccielab@groupstudy.com>
> > > > > > Subject: Re: T1 installation, 3660, VWIC-2MFT-T1-D1
> > > > > >
> > > > > > Fillmore,
> > > > > >
> > > > > > If you're seeing the interface as up/down, then it's the
layer
>2
> > > > > > protocol that's having trouble negotiating. Is the remote end
>also
> > > set
> > > > as
> > > > > > HDLC? Is it a Cisco? Are the channels really 64kb? Did you
try
> >56?
> > > > > Since
> > > > > > it's a fractional T1, usually the provider will provide the
> >clocking,
> > > so
> > > > > > that should be ok. What did 'sh service-module' show you? (I'm
>not
> > > > sure
> > > > > if
> > > > > > that card supports that command though, I've never used one).
>HTH.
> > > > > >
> > > > > > Chuck Church
> > > > > > CCIE #8776, MCNE, MCSE
> > > > > >
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Lillemor Hamnqvist" <lillemor@hamnqvist.org>
> > > > > > To: <ccielab@groupstudy.com>
> > > > > > Sent: Tuesday, January 28, 2003 8:48 AM
> > > > > > Subject: OT : T1 installation, 3660, VWIC-2MFT-T1-D1
> > > > > >
> > > > > >
> > > > > > > Anyone out there that can help me with an installation of a T1
>in
> >a
> > > > 3660
> > > > > > > with a VWIC-2mft-t1-d1 card, version 12.1-5.yd6
> > > > > > > The T1 up (control T1), no alarms, no fame error. But the
serial
> > > > > interface
> > > > > > > does not come up-up. We have done loopback test and I can loop
>to
> > > the
> > > > > > remote
> > > > > > > router and vs. We have done loopback test with Telco provider,
> > > putting
> > > > > > loops
> > > > > > > in the middle and we can see that. But the serial line does
not
> >come
> > > > up
> > > > > > when
> > > > > > > the line is normalized, all loop taken down. Any suggestions ?
> > > > > > > !
> > > > > > > controller T1 1/0
> > > > > > > framing esf
> > > > > > > linecode b8zs
> > > > > > > channel-group 0 timeslots 1-8 speed 64
> > > > > > > description ATT International 512k
> > > > > > > !
> > > > > > > !
> > > > > > > interface Serial1/0:0
> > > > > > > ip address 10.1.1.1 255.255.255.0
> > > > > > > !
> > > > > > >
> > > > > > > Thank you,
> > > > > > > /lillemor
> > > > > > > .
> > > > > > .
> > > > > .
> > > > .
> > > .
> >.
>.
.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:09 GMT-3