Please help regarding these outputs....

salmanzaheer · ‎07-18-2012

Hi Frnd,

Pls help me regarding below output --

volkswagen_aurangabad2_in_mpls#sh int s0/0/1:0

Serial0/0/1:0 is up, line protocol is up

Hardware is GT96K Serial

Description: * Connected to PE4-PNQ-AP Serial4/0/18:0 *

MTU 1500 bytes, BW 1984 Kbit, DLY 20000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation FRAME-RELAY IETF, loopback not set

Bundle Link of bundle MFR997

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 1w0d

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 30

Queueing strategy: fifo

Output queue: 0/5 (size/max)

5 minute input rate 0 bits/sec, 1 packets/sec

5 minute output rate 0 bits/sec, 1 packets/sec

4674537 packets input, 2589523774 bytes, 0 no buffer

Received 0 broadcasts, 9 runts, 0 giants, 0 throttles

865 input errors, 865 CRC, 144 frame, 4 overrun, 0 ignored, 135 abort

3926773 packets output, 1304942401 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

4 carrier transitions <<<<<<<<<<<<<<<<<<<<<<<<wats the mean of this or carier transition

Timeslot(s) Used:1-31, SCC: 1, Transmitter delay is 0 flags

and also check below logs for controllers--

Jul 14 05:44:46.659 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface MFR997, changed state to up

Jul 14 05:44:47.907 CEST: %BGP-5-ADJCHANGE: neighbor 212.21.217.140 Up

Jul 14 05:44:54.371 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to up

Jul 14 05:44:54.375 CEST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is ON

Jul 14 05:44:56.979 CEST: %BGP-5-ADJCHANGE: neighbor 62.134.22.34 Up

Jul 14 07:19:05.740 CEST: %HSRP-6-STATECHANGE: GigabitEthernet0/0 Grp 0 state Active -> Speak

Jul 14 11:58:15.472 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (RAI detected) <<<<<<<<<

Jul 14 11:58:16.472 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up

Jul 14 11:58:56.221 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/1, changed state to down (LOF detected) <<<<<<<<<<

Jul 14 11:58:56.473 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (AIS detected)<<<<<<<<

Jul 14 11:58:58.221 CEST: %LINK-3-UPDOWN: Interface Serial0/0/1:0, changed state to down

Jul 14 11:58:58.473 CEST: %LINK-3-UPDOWN: Interface Serial0/0/0:0, changed state to down

Jul 14 11:58:58.477 CEST: %LINK-3-UPDOWN: Interface MFR997, changed state to down

Jul 14 11:58:59.221 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:0, changed state to down

Jul 14 11:58:59.473 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:0, changed state to down

Jul 14 11:58:59.477 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface MFR997, changed state to down

Jul 14 11:59:04.222 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/1, changed state to up

Jul 14 11:59:04.474 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up

Jul 14 11:59:06.222 CEST: %LINK-3-UPDOWN: Interface Serial0/0/1:0, changed state to up

Jul 14 11:59:06.474 CEST: %LINK-3-UPDOWN: Interface Serial0/0/0:0, changed state to up

Jul 14 11:59:15.170 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to down

Jul 14 11:59:15.174 CEST: %BGP-5-ADJCHANGE: neighbor 62.134.22.34 Down Interface flap

Jul 14 11:59:20.234 CEST: %LINK-3-UPDOWN: Interface MFR997, changed state to up

Jul 14 11:59:21.226 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:0, changed state to up

Jul 14 11:59:21.234 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface MFR997, changed state to up

Jul 14 11:59:21.466 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:0, changed state to up

Jul 14 11:59:45.171 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to up

Jul 14 11:59:47.215 CEST: %BGP-5-ADJCHANGE: neighbor 62.134.22.34 Up

Jul 14 14:14:46.502 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)<<<<<<<<<<

Jul 14 14:14:47.502 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up

Jul 15 17:14:38.954 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to down

Jul 15 17:14:38.958 CEST: %BGP-5-ADJCHANGE: neighbor 62.134.22.34 Down Interface flap

Jul 15 17:15:08.955 CEST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF

Jul 15 17:25:48.977 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to up

Jul 15 17:25:48.981 CEST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is ON

Jul 15 17:26:09.498 CEST: %BGP-5-ADJCHANGE: neighbor 62.134.22.34 Up

Jul 15 17:38:09.002 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to down

Jul 15 17:38:09.006 CEST: %BGP-5-ADJCHANGE: neighbor 62.134.22.34 Down Interface flap

Jul 15 17:38:29.003 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to up

Jul 15 17:39:02.476 CEST: %BGP-5-ADJCHANGE: neighbor 62.134.22.34 Up

Jul 16 19:47:10.653 CEST: %SYS-5-CONFIG_I: Configured from console by voyence on vty0 (195.182.112.252)

Jul 17 11:24:15.308 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (RAI detected) <<<<<<<<<<

Jul 17 11:24:16.308 CEST: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up

And also check the below controller status....

volkswagen_aurangabad2_in_mpls#sh controller e1

E1 0/0/0 is up.

Applique type is Channelized E1 - balanced

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20040802, FPGA: 13, spm_count = 0

Framing is CRC4, Line Code is HDB3, Clock Source is Line Independent. <<<<<<<<<<<<samething here....

CRC Threshold is 320. Reported from firmware is 320.

Data in current interval (255 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

Total Data (last 24 hours)

0 Line Code Violations, 6 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

E1 0/0/1 is up.

Applique type is Channelized E1 - balanced

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20040802, FPGA: 13, spm_count = 0

Framing is CRC4, Line Code is HDB3, Clock Source is Line Independent. <<<<<<<<<<<<clock source is set to line independent

CRC Threshold is 320. Reported from firmware is 320.

Data in current interval (256 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

Total Data (last 24 hours)

0 Line Code Violations, 16 Path Code Violations,

0 Slip Secs, 1 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,

0 Errored Secs, 0 Bursty Err Secs, 1 Severely Err Secs, 0 Unavail Secs

volkswagen_aurangabad2_in_mpls#

vmiller · ‎07-30-2012

You have layer 1 issues on E1 0/0/1. looks like some los of framing

ontroller E1 0/0/0, changed state to down (LOF detected)

Time to get the carrier involved.

darren.g · ‎07-30-2012

You are receiving link errors from the communications service - AIS is Alarm Indication Signal, LOF is Loss Of Framing and RAI is Remote Alarm Indication - in short, your link is having issues, and you need to talk to your telco/carrier to get it investigated.

Cheers.