Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Carrier

Status
Not open for further replies.

new2nortel2

Technical User
Apr 28, 2014
42
US
Hi all,

Need some help. I'm a little new to the Option 81 and have some time of MAC experience... there is a copper Remote Carrier not working... I just want to confirm the best method of troubleshooting and resetting the Controller card on the superloop... thank you for any & all help

 
... so now the terminal screen is printing out BUG4216 and listing all the ports on a specific card:

BUG4216 : 20 0 4 x etc...

what does this mean?

Thank you
 
Just to clarify - this is a full copper carrier remote? not a mini carrier remote or a fiber carrier remote, or a multi-ipe carrier remote? there are a lot of flavors.

Usually they all pretty much self recover - if there is a good path/carrier. Are you using a straight copper link under the max distance?

Is it T1/E1 based? if so, is it private or going through a telco carrier? If so, is the T1/E1 working properly?

Do you know what loop it is? can you stat the loop? disable/enable the loop?
If nothing is working at the other end, you could always disable, jack and re-rack the local carrier card, and then re-enable. you could also do this at the remote end.


30n30w
 
Hi 30n30w, thank you for your response... this is a full copper carrier remote connected to the main site via T1... I inherited the site and do not have specifics on the type of T1 yet. I've opened a TT w/carrier for mulitlateral approach and waiting to hear back although I don't think its a Carrier issue since the CSU/DSU at the host is fine...

I understand your comment: "Usually they all pretty much self recover - if there is a good path/carrier" because this is usually the case when errors come through but this time it hasn't...

I know what the remote loop is but don't know what the local loop is - this is the exact guidance I was hoping to get:

How can I find the corresponding local loop to the remote carrier loop?
How can I disable/enable the loops so I can reseat the card?

I see a local Local Carrier I/F card at the host with a Enb/Dis switch on the top of it with an Amber Maint LED - is it safe to assume that this is the card? if so, can I use the switch to enable disable or should I 1st do this via CLI?

Thank you again

 
the consecutive BUG4216 messages stopped...

CRI3301 SUPC 20 EXTERNAL ALARM 1 CLEARED

CRI3301 SUPC 20 EXTERNAL ALARM 2 CLEARED

CRI3320 SUPC 20 EXTERNAL ALARM ?? SET

(maybe this was caused by the Carrier testing... )
 
So if you know what the remote loop number is, that should also be your local interface card loop.
THIS IS ASSUMING IT'S a carrier remote (network shelf card clot) and not a mini-carrier remote (ipe shelf card slot)

If a known phone hanging off the far end is 20 0 X X then it's loop 20 - the following is at your own risk of course :)

Chances are this is a telco carrier issue - or it could be a CSU problem at the far end - have you been able to physically verify that the CSU is normal at the far end?


Stat 20 - should show you:

REQ: stat 20
SUPER LOOP
000 DSBL 000 BUSY

or some combo of the above numbers

if nothing is functional at the other end, once you determine your loop number for this carrier remote, you could disable it and re-enable it. If some phones are working, disabling the loop will kill 'em

I always disable in software before using the dis/enl switch on the card....
(assuming it's loop 20)
REQ: disl 20
ground yourself on the switch cabinet
Move the switch to dis
carefully unlatch the card, drawing it part way out,
then gently re-seat it and relatch
move the switch to enl
Req: enll 20

again, free advice is worth what you pay for it. use at your own risk!
good luck!
30n30w


 
I haven't visited the remote side yet... but will in a bit - thank you for the free advice - very appreciated. I skimmed the Remote manual (thankfully left on site) while waiting for your reply and came across the page that describes what you just answered with... I requested a stat 20 from LD 20 & LD 32 and both printed:

STAT 20
SUPER LOOP
CARR CALS TTSA NND SPARED?
0 0 21/21 NO N/A
1 3 0/21 YES N/A
2 3 0/21 YES N/A

... this is different from you showed above - where you using a different LD? just being cautious

 
... the Local Carrier I/F card is sitting on a Network Shelf 1/1 SLP slot 9 ...

should I expect the Carrier I/F LEDs to deactivate once the DISL command is entered?
 
so I STAT 20 after DISL 20 and it came back with:

DSBL RESPONDING


should I wait for a confirmation message that the card is disabled before proceeding with manual part or is this enough confirmation?

Thank you!
 
you can probably go ahead with the manual part -

the reason the responses are different is I don't have an actual carrier remote installed; yours is configured and probably a different version of software. Mine is a multi-IPE remote that uses the standard SUPL card.

30n30w
 
OK, so the DISL, reseat, ENLL was completed and the STAT shows the Carrier to be OK... I went to site and noticed that all the line cards including the Remote I/F card had red LED's... how do these get enabled (or re-enabled) after the work at the host is completed?

Thank you
 
Have you done the DSXP and the XPCT commands from the PBX in LD 32. This will test the remote card. The only thing you can do at the far end is connect to the MMI terminal and there is a series of tests you can run there. Easy thing to do is get a T-1 loopback plug and see if these carrier alarms go away. It almost sounds like there is a loop up in the circuit. Have you had the telco test it or do you have a t-berd? In the Remote Services guide there is a whole troubleshooting section for the carrier remote.
 
if all the cards on the remote shelf are showing red; (if it were me), I would just kill power to the shelf and turn it back on...the controller should download and reset all the cards. Assuming the link is good...
30n30w
 
Thank you for the comment kcflhrc... the DSXP 20, XPCT 20, & ENXP 20 (found this in the Remote Services guide) are helpful... I also found XNTT and XPCT commands <-- are these needed?
 
XNTT is a self test of the local card and XPCT is a self test of the remote card. If the remote card is not responding then the XPCT is useless.
 
kcflhrc: thank you for the .pdf (easier to search through) - would you happen to have other Option81 .pdfs? also thank you for clarifying the XNTT & XPCT

30n30w: I've done the same in a few other occasions (pwer cycle) and did it hear also, but it didn't clear the cards

... I think ENXP did it! (does this command reset the controller as well as request a fresh download?)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top