NIM-2MFT-T1/E1 not showing up as serial interfaces for MPLS - Page 2

Travis-Fleming · ‎10-17-2019

Hello. We have an ISR 4331/K9 with voice and security license on them.

A show inventory shows our NIM card installed:

"NAME: "NIM subslot 0/2", DESCR: "NIM-2MFT-T1/E1 - T1/E1 Serial Module"
PID: NIM-2MFT-T1/E1 , VID: V05 , SN: FOC23354FUE"

I've configured the controllers as T1 as below from show controllers t1 command. However when I do a show ip int brief, I"m not seeing the serial interfaces as I would expect to configure the MPLS T1's? We will have 2 1.5 T1's setup in a multilink fashion.

What am I missing here? They don't have cables plugged in as I'm staging them at our HQ then shipping onsite to another state.

Router(config)#do sh controllers t1
T1 0/2/0 is down
Applique type is Channelized T1
Cablelength is long gain36 0db
Transmitter is sending remote alarm.
Receiver has loss of signal.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Failure LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (3 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, 3 Unavail Secs
Total Data (last 1 15 minute intervals):
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, 900 Unavail Secs
T1 0/2/1 is down
Applique type is Channelized T1
Cablelength is long gain36 0db
Transmitter is sending remote alarm.
Receiver has loss of signal.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Failure LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (2 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, 2 Unavail Secs
Total Data (last 1 15 minute intervals):
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, 900 Unavail Secs

Travis-Fleming · ‎10-21-2019

Morning, it still did not work.

Should I just open a TAC case maybe? I do have another card new in the box, so maybe the card is bad? The amber light is still solid on them, but the green light is solid on the EN light, so the card is enabled and working. I just still can't get the 1 T1 port to light up my NIC on my directly connected laptop.

Current controller configs:

wt-latx-mpls-rt01#sh run | sec controller
controller T1 0/2/0
threshold sd-ber 6
threshold sf-ber 3
framing esf
linecode b8zs
cablelength short 110
channel-group 1 timeslots 1
controller T1 0/2/1
threshold sd-ber 6
threshold sf-ber 3
framing esf
linecode b8zs
cablelength short 110
channel-group 1 timeslots 1

Georg Pauwen · ‎10-21-2019

Hello,

actually, I would try and upgrade to the recommended release Fuji-16.9.4 MD first. The 'threshold' lines are a bug, and there might be others.

Travis-Fleming · ‎10-21-2019

Unfortunitly that did not work either. I'm running Fuji 16.9.4 now. The AL lights on the NIM-2MFT-T1/E1 card are still a solid amber light. The EN light is solid Green. It did remove the lines you talked about on the controllers however. Current config:

wt-latx-mpls-rt01#sh run | section controller
controller T1 0/2/0
framing esf
linecode b8zs
cablelength short 110
channel-group 1 timeslots 1
controller T1 0/2/1
framing esf
linecode b8zs
cablelength short 110
channel-group 1 timeslots 1

wt-latx-mpls-rt01#sh run int multilink1
Building configuration...

Current configuration : 138 bytes
!
interface Multilink1
ip address x.x.x.x 255.255.255.252
ppp multilink
ppp multilink links minimum 1
ppp multilink interleave
ppp multilink group 1
end

Is there a log file that will tell me why the card is in error state?

Georg Pauwen · ‎10-21-2019

Hello,

annoying. I remember there was something particular about these cards, I am trying to figure out what it was.

If you take the channel-group off the interfaces, does that change anything, that is, do the individual cards have the same remote alarm ?

Travis-Fleming · ‎10-21-2019

I did try that, same error still occurs.

I did open a TAC case as well just now.

Georg Pauwen · ‎10-21-2019

Hello,

of course it is always possible that the cards are faulty. Very curious to know what TAC says...

Travis-Fleming · ‎10-21-2019

Our TAC coverage doesn't start until Nov 1 so they won't help, which is okay in our time frame.

On a complete side note I did plug in a loopback and the light went green! Any thing I can do from that aspect to test it to be sure it will work? Forgot about the old loopback ethernet plug until a bit ago. Here is what I get when I do a show controller t1 now with a single loopback in:

wt-latx-mpls-rt01#sh controller t1
T1 0/2/0 is up
Applique type is Channelized T1
Cablelength is short 110
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (69 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 1 15 minute intervals):
5384 Line Code Violations, 8 Path Code Violations,
0 Slip Secs, 1 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,
3 Errored Secs, 3 Bursty Err Secs, 0 Severely Err Secs, 21 Unavail Secs
T1 0/2/1 is down
Applique type is Channelized T1
Cablelength is short 110
Transmitter is sending remote alarm.
Receiver has loss of signal.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Failure LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (68 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, 68 Unavail Secs
Total Data (last 1 15 minute intervals):
5306 Line Code Violations, 2 Path Code Violations,
0 Slip Secs, 1 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 872 Unavail Secs

Travis-Fleming · ‎10-21-2019

Our TAC coverage doesn't start until Nov 1 so they won't help, which is okay in our time frame.

On a complete side note I did plug in a loopback and the light went green! Any thing I can do from that aspect to test it to be sure it will work? Forgot about the old loopback ethernet plug until a bit ago. Here is what I get when I do a show controller t1 now with a single loopback in:

wt-latx-mpls-rt01#sh controller t1
T1 0/2/0 is up
Applique type is Channelized T1
Cablelength is short 110
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (69 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 1 15 minute intervals):
5384 Line Code Violations, 8 Path Code Violations,
0 Slip Secs, 1 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,
3 Errored Secs, 3 Bursty Err Secs, 0 Severely Err Secs, 21 Unavail Secs
T1 0/2/1 is down
Applique type is Channelized T1
Cablelength is short 110
Transmitter is sending remote alarm.
Receiver has loss of signal.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Failure LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (68 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, 68 Unavail Secs
Total Data (last 1 15 minute intervals):
5306 Line Code Violations, 2 Path Code Violations,
0 Slip Secs, 1 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 872 Unavail Secs

Georg Pauwen · ‎10-21-2019

Hello,

if the loopback brings up the interface, the card is pretty much for sure ok. How much contact did you actually have with the ISP ? I would call them and ask them to check their side. The 'remote alarm' pointed to their side from the beginning.

Travis-Fleming · ‎10-21-2019

I do apologize George,

The new router is being staged at our HQ office, then shipped across the country to another state to be put in place. We don't have an MPLS here to test, so I was trying to do as much prep-work as I could before shipping out. It's our first experience with a 4300 series router with a T1 card. All our other bonded T1 solutions are with a 2911. I was trying to hook a laptop up to the interface, and I mistakenly thought it would make the interface go live, but I guess that is not the case. However testing with the loopback I believe I have it setup correctly now.

Georg Pauwen · ‎10-21-2019

Hello,

in order for the interface to go up you would need some sort of DSLAM, which I don't think you have just sitting there...:)

I think your interfaces are fine, the loopback test went well.

Travis-Fleming · ‎10-21-2019

Yep! Thank you so much for going on this journey with me!