NTRB21AB Can't Get MSDL to Enable 4

[bfuller83]

I have a NTRB21AB installed in an option 11 and when I stat msdl 9 I get:

.stat msdl 9
MSDL 9: MAN DSBL
DCH 9 DIS PORT 1
.

So naturally I do a:

enl msdl 9

and it returns:

DOWNLOADING BASE
REASON: NONE ON CARD

OVL021 IDLE

SDL100 BUSY
........................
TIM000 11:50 20/7/2012 CPU 0

SDL000 MSDL 9 , VERSION 73 , MAINT MODE.

And eventually:
.
MSDL011
No response received to the enable card command

If I do a enl msdl 9 again I get a:

MSDL016
Failed enable attempt. If this message is not accompanied by any other
error message, the card may be in the process of performing self-tests
or the self-tests may have already failed.
Wait a few minutes, then execute the self-tests with the SLFT MSDL x
command. If self-tests pass, try to enable the card again.
Severity: Critical

so I run the slft and it posts results:

slft msdl 9
..............................
..............................
..............................
..............................
..............................
..............................
..............................
..............................
........
SELFTESTS PASSED
CARDID = NTRB21AB 01 NNTM5009PC10

and the cycle repets iself. I have attempted enl msdl 9 fdl with the same results. Any suggestions?

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

 

[StanleySteamer]

BARS/NARS uses the route number not the ACOD.
You will need to change all RLB's in LD 86 that reference the original copper route number. Otherwise your calls will continue to use the old route.

 

[bfuller83]

That seemed to work great...So I changed all the RLI's that pointed at the copper rdb 0 to 9 and it appears that my local calling is working great now! So the flow of things is this as I understand it:

NPA matches and sends it to a RLI that tells it what trunk to go out and adds and / or removes digits as needed for those trunks. How does it get to the NPA? Everything is working now I believe I appreciate all the help!!


Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

 

[StanleySteamer]

Nobody explains it better than GHTROUT

http://www.ghtrout.com/bars/index.html

 

[bfuller83]

ahha!! Thanks! So because we are using bars/rli/lcr then the acod on the route group really dosn't do anything except provide a direct access to bypass bars. Cool thanks again!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

 

[StanleySteamer]

ACOD also comes into play with CDR.
Most CDR software applications need to know the ACOD for all the trunk routes because it shows up in the CDR record.