Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1247
Views
0
Helpful
2
Replies

Channelized E1 is flapping fequently

smily_guy40
Level 1
Level 1

‎02-27-2012 01:44 AM - edited ‎03-04-2019 03:26 PM

Hi,

I am getting issue with channelized E1 that it is flapping very frequently, below is the log kindly suggest.

E1 1/0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
  Module type is Channelized E1/T1 PRI
  Version info Firmware: 0000001D, FPGA: 0
  Hardware revision is 0.0         , Software revision is 29
  Protocol revision is 1
  number of CLI resets is 0
    receive remote alarm  :    0,
    transmit remote alarm :    0,
    receive AIS alarm     :    0,
    transmit AIS alarm    :    0,
    loss of frame         :    0,
    loss of signal        :    0,
    Loopback test         :    0,
    transmit AIS in TS 16 :    0,
    receive LOMF alarm    :    0,
    transmit LOMF alarm   :    0,
  MIB data updated every 10 seconds.
  Data in current interval (507 seconds elapsed):
     0 Line Code Violations, 508 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, 499 Unavail Secs

Feb 27 08:48:25.311: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (10 SES)

Feb 27 08:48:26.852: %LINK-5-CHANGED: Interface Serial1/0:0, changed state to reset

Feb 27 08:48:26.864: %LINK-5-CHANGED: Interface Serial1/0:1, changed state to reset

Feb 27 08:48:26.880: %LINK-5-CHANGED: Interface Serial1/0:2, changed state to reset

Feb 27 08:48:26.896: %LINK-5-CHANGED: Interface Serial1/0:3, changed state to reset

Feb 27 08:48:26.912: %LINK-5-CHANGED: Interface Serial1/0:4, changed state to reset

Feb 27 08:48:26.928: %LINK-5-CHANGED: Interface Serial1/0:5, changed state to reset

Feb 27 08:48:26.944: %LINK-5-CHANGED: Interface Serial1/0:6, changed state to reset

Feb 27 08:48:26.956: %LINK-5-CHANGED: Interface Serial1/0:7, changed state to reset

Feb 27 08:48:26.956: %OSPF-5-ADJCHG: Process 1501, Nbr 10.5.200.2 on Serial1/0:7 from FULL to DOWN,

Neighbor Down: Interface down or detached

Feb 27 08:48:26.972: %LINK-5-CHANGED: Interface Serial1/0:8, changed state to reset

Feb 27 08:48:26.988: %LINK-5-CHANGED: Interface Serial1/0:9, changed state to reset

Feb 27 08:48:27.004: %LINK-5-CHANGED: Interface Serial1/0:10, changed state to reset

Feb 27 08:48:27.020: %LINK-5-CHANGED: Interface Serial1/0:11, changed state to reset

Feb 27 08:48:27.036: %LINK-5-CHANGED: Interface Serial1/0:12, changed state to reset

Feb 27 08:48:27.048: %LINK-5-CHANGED: Interface Serial1/0:13, changed state to reset

Feb 27 08:48:27.064: %LINK-5-CHANGED: Interface Serial1/0:15, changed state to reset

Feb 27 08:48:27.080: %LINK-5-CHANGED: Interface Serial1/0:16, changed state to reset

Feb 27 08:48:27.104: %LINK-5-CHANGED: Interface Serial1/0:17, changed state to reset

Feb 27 08:48:27.112: %LINK-5-CHANGED: Interface Serial1/0:18, changed state to reset

Feb 27 08:48:27.124: %LINK-5-CHANGED: Interface Serial1/0:19, changed state to reset

Feb 27 08:48:27.140: %LINK-5-CHANGED: Interface Serial1/0:20, changed state to reset

Feb 27 08:48:27.156: %LINK-5-CHANGED: Interface Serial1/0:21, changed state to reset

Feb 27 08:48:27.172: %LINK-5-CHANGED: Interface Serial1/0:22, changed state to reset

Feb 27 08:48:27.188: %LINK-5-CHANGED: Interface Serial1/0:23, changed state to reset

Feb 27 08:48:27.204: %LINK-5-CHANGED: Interface Serial1/0:24, changed state to reset

Feb 27 08:48:27.216: %LINK-5-CHANGED: Interface Serial1/0:25, changed state to reset

Feb 27 08:48:27.232: %LINK-5-CHANGED: Interface Serial1/0:26, changed state to reset

Feb 27 08:48:27.248: %LINK-5-CHANGED: Interface Serial1/0:27, changed state to reset

Feb 27 08:48:27.264: %LINK-5-CHANGED: Interface Serial1/0:28, changed state to reset

Feb 27 08:48:27.280: %LINK-5-CHANGED: Interface Serial1/0:29, changed state to reset

Feb 27 08:48:27.296: %LINK-5-CHANGED: Interface Serial1/0:30, changed state to reset

Feb 27 08:48:27.956: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:7, changed state to d

own

Feb 27 08:48:34.768: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Feb 27 08:48:35.908: %LINK-3-UPDOWN: Interface Serial1/0:27, changed state to up

Feb 27 08:48:38.908: %LINK-3-UPDOWN: Interface Serial1/0:0, changed state to up

Feb 27 08:48:41.908: %LINK-3-UPDOWN: Interface Serial1/0:1, changed state to up

Feb 27 08:48:44.908: %LINK-3-UPDOWN: Interface Serial1/0:2, changed state to up

Feb 27 08:48:44.924: %OSPF-5-ADJCHG: Process 1501, Nbr 10.5.200.2 on Serial1/0:7 from LOADING to FUL

L, Loading Done

Feb 27 08:48:47.908: %LINK-3-UPDOWN: Interface Serial1/0:3, changed state to up Feb 27 08:48:25.311: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (10 SES)
Feb 27 08:48:26.852: %LINK-5-CHANGED: Interface Serial1/0:0, changed state to reset
Feb 27 08:48:26.864: %LINK-5-CHANGED: Interface Serial1/0:1, changed state to reset
Feb 27 08:48:26.880: %LINK-5-CHANGED: Interface Serial1/0:2, changed state to reset
Feb 27 08:48:26.896: %LINK-5-CHANGED: Interface Serial1/0:3, changed state to reset
Feb 27 08:48:26.912: %LINK-5-CHANGED: Interface Serial1/0:4, changed state to reset
Feb 27 08:48:26.928: %LINK-5-CHANGED: Interface Serial1/0:5, changed state to reset
Feb 27 08:48:26.944: %LINK-5-CHANGED: Interface Serial1/0:6, changed state to reset
Feb 27 08:48:26.956: %LINK-5-CHANGED: Interface Serial1/0:7, changed state to reset
Feb 27 08:48:26.956: %OSPF-5-ADJCHG: Process 1501, Nbr 10.5.200.2 on Serial1/0:7 from FULL to DOWN,
Neighbor Down: Interface down or detached
Feb 27 08:48:26.972: %LINK-5-CHANGED: Interface Serial1/0:8, changed state to reset
Feb 27 08:48:26.988: %LINK-5-CHANGED: Interface Serial1/0:9, changed state to reset
Feb 27 08:48:27.004: %LINK-5-CHANGED: Interface Serial1/0:10, changed state to reset
Feb 27 08:48:27.020: %LINK-5-CHANGED: Interface Serial1/0:11, changed state to reset
Feb 27 08:48:27.036: %LINK-5-CHANGED: Interface Serial1/0:12, changed state to reset
Feb 27 08:48:27.048: %LINK-5-CHANGED: Interface Serial1/0:13, changed state to reset
Feb 27 08:48:27.064: %LINK-5-CHANGED: Interface Serial1/0:15, changed state to reset
Feb 27 08:48:27.080: %LINK-5-CHANGED: Interface Serial1/0:16, changed state to reset
Feb 27 08:48:27.104: %LINK-5-CHANGED: Interface Serial1/0:17, changed state to reset
Feb 27 08:48:27.112: %LINK-5-CHANGED: Interface Serial1/0:18, changed state to reset
Feb 27 08:48:27.124: %LINK-5-CHANGED: Interface Serial1/0:19, changed state to reset
Feb 27 08:48:27.140: %LINK-5-CHANGED: Interface Serial1/0:20, changed state to reset
Feb 27 08:48:27.156: %LINK-5-CHANGED: Interface Serial1/0:21, changed state to reset
Feb 27 08:48:27.172: %LINK-5-CHANGED: Interface Serial1/0:22, changed state to reset
Feb 27 08:48:27.188: %LINK-5-CHANGED: Interface Serial1/0:23, changed state to reset
Feb 27 08:48:27.204: %LINK-5-CHANGED: Interface Serial1/0:24, changed state to reset
Feb 27 08:48:27.216: %LINK-5-CHANGED: Interface Serial1/0:25, changed state to reset
Feb 27 08:48:27.232: %LINK-5-CHANGED: Interface Serial1/0:26, changed state to reset
Feb 27 08:48:27.248: %LINK-5-CHANGED: Interface Serial1/0:27, changed state to reset
Feb 27 08:48:27.264: %LINK-5-CHANGED: Interface Serial1/0:28, changed state to reset
Feb 27 08:48:27.280: %LINK-5-CHANGED: Interface Serial1/0:29, changed state to reset
Feb 27 08:48:27.296: %LINK-5-CHANGED: Interface Serial1/0:30, changed state to reset
Feb 27 08:48:27.956: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:7, changed state to d
own
Feb 27 08:48:34.768: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up
Feb 27 08:48:35.908: %LINK-3-UPDOWN: Interface Serial1/0:27, changed state to up
Feb 27 08:48:38.908: %LINK-3-UPDOWN: Interface Serial1/0:0, changed state to up
Feb 27 08:48:41.908: %LINK-3-UPDOWN: Interface Serial1/0:1, changed state to up
Feb 27 08:48:44.908: %LINK-3-UPDOWN: Interface Serial1/0:2, changed state to up
Feb 27 08:48:44.924: %OSPF-5-ADJCHG: Process 1501, Nbr 10.5.200.2 on Serial1/0:7 from LOADING to FUL
L, Loading Done
Feb 27 08:48:47.908: %LINK-3-UPDOWN: Interface Serial1/0:3, changed state to up

Labels:
0 Helpful
2 Replies 2

nisagar
Level 1
Level 1

‎02-27-2012 06:57 AM

Hi,

Can you look at "508 Path Code Violations" ? This can be an telco issue as Path code voilation's generally occur due to an physcial connectivity problem or framing.

Ensure the framing format configured on the  port matches the framig format of the line. Look for Framing is  {crc4|no-crc4} in the show controller e1 output.

If Path Code Violations keep increasing, contact your Service  Provider to check the E1 line as Path Code Violations can also be caused  by physical line problems.

Regards

Nitin

0 Helpful

smily_guy40
Level 1
Level 1
In response to nisagar

‎02-27-2012 10:54 PM

Hi Nitin,

Thanks for your support!

There is no framing issue with the E1 as "NO-CRC4" configured for E1 and same is for line but per your next suggestion to check the physical line we are going to check it with the service provider.

Below is the latest snapshot of controller in which some new errors detected like Severely Err Secs, so kindly go through the below log and suggest the possible cause.

E1 1/0 is up.

  Applique type is Channelized E1 - balanced

  No alarms detected.

  alarm-trigger is not set

  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.

  Module type is Channelized E1/T1 PRI

  Version info Firmware: 0000001D, FPGA: 0

  Hardware revision is 0.0         , Software revision is 29

  Protocol revision is 1

  number of CLI resets is 0

    receive remote alarm  :    0,

    transmit remote alarm :    0,

    receive AIS alarm     :    0,

    transmit AIS alarm    :    0,

    loss of frame         :    1,

    loss of signal        :    0,

    Loopback test         :    0,

    transmit AIS in TS 16 :    0,

    receive LOMF alarm    :    0,

    transmit LOMF alarm   :    0,

  MIB data updated every 10 seconds.

  Data in current interval (225 seconds elapsed):

     0 Line Code Violations, 116 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, 219 Unavail Secs

  Total Data (last 64 15 minute intervals):

     0 Line Code Violations, 33122 Path Code Violations,

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

     1359 Errored Secs, 0 Bursty Err Secs, 1357 Severely Err Secs, 48010 Unavail Secs

E1 1/1 is up.

  Applique type is Channelized E1 - balanced

  No alarms detected.

  alarm-trigger is not set

  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.

  Module type is Channelized E1/T1 PRI

  Version info Firmware: 0000001D, FPGA: 0

  Hardware revision is 0.0         , Software revision is 29

  Protocol revision is 1

  number of CLI resets is 0

    receive remote alarm  :    1,

    transmit remote alarm :    0,

    receive AIS alarm     :    5,

    transmit AIS alarm    :    0,

    loss of frame         :    6,

    loss of signal        :    0,

    Loopback test         :    0,

    transmit AIS in TS 16 :    0,

    receive LOMF alarm    :    0,

    transmit LOMF alarm   :    0,

  MIB data updated every 10 seconds.

  Data in current interval (229 seconds elapsed):

     0 Line Code Violations, 72 Path Code Violations

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

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

  Total Data (last 64 15 minute intervals):

     2 Line Code Violations, 43331 Path Code Violations,

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

     7838 Errored Secs, 0 Bursty Err Secs, 7039 Severely Err Secs, 2225 Unavail Secs

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card