cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
392
Views
0
Helpful
4
Replies

Unusual behavior on 2nd port of 2 port MC T3 card.

p-blake
Level 1
Level 1

I am having an odd problem. I have a 2 port MC-T2 card installed in a 7206VXR in slot 5. Port 5/0 is behaving as expected. We are bring up a new Channelizes DS3 on port 5/1 and I am getting behavior that generated the output below when I issue the "show controller T3 5/1" command. The controller shows DOWN while the T1 channels on the controller show UP/UP. any thoughts?

T3 5/1 is down. Hardware is 2CT3 single wide port adapter

CT3 H/W Version : 0.2.2, CT3 ROM Version : 1.0, CT3 F/W Version : 2.5.1

FREEDM version: 1, reset 0 resurrect 0

Applique type is Channelized T3

No alarms detected.

FEAC code received: No code is being received

Framing is M23, Line Code is B3ZS, Clock Source is Line

Rx-error throttling on T1's ENABLED

Rx throttle total 0, equipment customer loopback

Data in current interval (2 seconds elapsed):

0 Line Code Violations, 0 P-bit Coding Violation

0 C-bit Coding Violation, 0 P-bit Err Secs

0 P-bit Severely Err Secs, 0 Severely Err Framing Secs

0 Unavailable Secs, 0 Line Errored Secs

0 C-bit Errored Secs, 0 C-bit Severely Errored Secs

T1 1 is up

timeslots: 1-24

FDL per AT&T 54016 spec.

No alarms detected.

Framing is ESF, Clock Source is Internal

Data in current interval (82 seconds elapsed):

0 Line Code Violations, 581 Path Code Violations

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

3 Errored Secs, 0 Bursty Err Secs, 3 Severely Err Secs

0 Unavail Secs, 0 Stuffed Secs

T1 2 is up

timeslots: 1-24

FDL per AT&T 54016 spec.

No alarms detected.

Framing is ESF, Clock Source is Internal

Data in current interval (83 seconds elapsed):

0 Line Code Violations, 581 Path Code Violations

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

2 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs

0 Unavail Secs, 0 Stuffed Secs

Thanks..

4 Replies 4

paolo bevilacqua
Hall of Fame
Hall of Fame

Why you blame the port?

Do you have evidence that the circuit is working on a different port ?

I am scheduling to move the circuit to another T3 port, that is currently working, to see if the behavior follows. Thanks for the input.

Giuseppe Larosa
Hall of Fame
Hall of Fame

Hello Paul,

I see

>> FEAC code received: No code is being received

this may be related to the fact second T3 is considered down

Hope to help

Giuseppe

That in itself is normal, no loop code is being received.

All appears normal, but maybe telco has not completed their mux configuration.

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:

Review Cisco Networking products for a $25 gift card