At 08:02 PM 12/12/97 -0500, you wrote:
>
>There is recorded this:
>
> 3 carrier transitions
>
>full sh int:
>
> MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 4/255
> Encapsulation HDLC, loopback not set, keepalive set (10 sec)
> Last input 00:00:00, output 00:00:02, output hang never
> Last clearing of "show interface" counters never
> Input queue: 0/75/0 (size/max/drops); Total output drops: 0
> Queueing strategy: weighted fair
> Output queue: 0/64/0 (size/threshold/drops)
> Conversations 0/18 (active/max active)
> Reserved Conversations 0/0 (allocated/max allocated)
> 5 minute input rate 100000 bits/sec, 22 packets/sec
> 5 minute output rate 27000 bits/sec, 14 packets/sec
> 4733911 packets input, 2193128614 bytes, 0 no buffer
> Received 18210 broadcasts, 0 runts, 0 giants
> 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 3 abort
> 10236341 packets output, 2891963796 bytes, 0 underruns
> 0 output errors, 0 collisions, 0 interface resets
> 0 output buffer failures, 289806 output buffers swapped out
>->> 3 carrier transitions
> RTS up, CTS up, DTR up, DCD up, DSR up
>
>
>Whats a "carrier transition" ?
>
>
A carrier transition indicates when the cicuit signalling fails. For
example, this could be indicated when in interface shows 'Serial0/0 is down,
line protocol is down'. However, if the circuit were still up, but the line
protocol(PPP,HDLC,FR) were down you could see the following and not have a
'carrier transition' 'Serial0/0 is up, line protocol is down'.
I did not see the beginning of this thread, so I do not have enough info to
go on, but there could be several issues depending on the chassis, IOS,
processor load, and density of the circuits supported ... among others.
So, if after upgrading your IOS rev(as you mention earlier) you continue to
have difficulty; I might recommend contacting TAC and submitting a 'show
tech' output for them.
al
>On Fri, 12 Dec 1997, Luke Parrish wrote:
>
>> when you do a 'sh int s2/5', are you seeing any interface resets?
>>
>>
>> At 04:16 PM 12/12/97 -0500, you wrote:
>> >
>> >Seeing a lot of line protocol bounces on T1's in log files:
>> >
>> >For example:
>> >
>> >Dec 10 02:48:27 e1-1.baltimore.mae-east.clark.net 111498:
>> >%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/5, changed state
>> >to down
>> >Dec 10 02:48:27 e1-1.baltimore.mae-east.clark.net 111499:
>> >%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/5, changed state
>> >to up
>> >
>> >
>> >
>> >
>> >Bounces up and down in < 1 second - logs only show it for one end of the
>> >T1 not the other.
>> >
>> >Not sure if this is real, false positives, etc..
>> >
>> >Anyone seen this before?
>> >
>> > Stb
>> >
>> >
>> >
>> >
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>> * Luke Parrish * Email lparrish@iamerica.net *
>> * LDS-iAmerica, ISP * Email luke@ciscokid.iamerica.net *
>> * Network Engineer * Phone 1-800-789-6062 x3010 *
>> * AS 4958 * http://cust.iamerica.net/lparrish *
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>> * I love the Internet, and you should too. *
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>
>
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:14 EDT