NAS M2250 console inop after 1 month of in service

[ledfordb]

OK,
I read this site a great deal but have really never had the cause to post a question but here is my virgin plunge.

I have a client with (2) Option 11C's that are networked across PRI-TIE circuits. About 2 months ago, I went to the locations and added an M2250 console on the far side of the network (Site B) in addition to the existing console at Site A. Nortel assisted me in setting up the NAS functionality, as well as the D-Channel alterations.

The site has been in service for well over a month utilizing the NAS service as it was described. About a week ago, I received a call from Site B informing me that the console was locked up, Hold key showing an indicator beside it and calls routing into the CP system due to the situation. Site A is only sometimes manned and normally calls go across to the Site B console.

I called in and stat'd the console and it appeared in an idle condition. However, calls coming into the systems were being treated with Nite Service routing. I disabled the console and reenabled....physically removed and replaced for testing....and even as of yesterday changed the line card for giggles....same situation.

ETAS called into the switchs, both sitting at Rel 3.0 and informed me that my dependancy list neede to be upgraded because it was a year old. The engineer said that this was wh the console was locked and stated software patch would "most likely" remedy the situation.

Has anyone been in this situation before? John P, who I like to think of as the Nortel Guru, have you seen this before? Does anyone have any idea if the DEP will cure this?
I have the patchs and have scheduled their installation but it just bothers me that it worked like a dream for a month. I can't say that I will be a happy telephone jock if I install these and the console remains dead.....

Sorry for being so long winded but I am at a loss for a solution and decided to lay it all out for the regulars on here. Many times I have come to this forum and found my answers without even posting and the script files are the greatest. Thanks in advance for your suggestions and advice, it is greatly appreciated.

In closing, my hats' off to the "Knowers of Nortel" here at this place......keep it ringing!




J. Baron Ledford LVCU
Senior Project Engineer
Nu-Vision Technologies LLC
Georgia Offices

 

[johnpoole]

thanks for the mention but a lot of us have been around a while... nortel can't swear that the patch will cure the problem.. it is to isolated and not a problem you can duplicate... they can look at pointers and history plus other switch history and make an educated guess.. the console locked up once? that could have been someone shorting the wronge pair, the operator going into nights due to a new headset without hitting rls.. those types of things never leave an audut trail... i'm on rls 3 with a networks site but do not have a console on the far end... the good thing is the nite treatment worked, when one locks and callers get dead air.. it hurts worse..


tow things i would do.. clean up your switches.. remove everything that is not used.. make sure your as built matches your actual sets... do not remove ld 30 from drol and make sure drol is loaded.. then dial in once a day and look at the history files as well as ld 117 prt sel 500.. clear any bugs/errors etc... if you keep your switches clean that will keep you employeed.. in my case for almost 40 years

john poole
bellsouth business
columbia,sc

 

[ledfordb]

John,
Thanks for the info, somehow I knew that you would be one of the first to reply. Here is the kicker, the console is and has been locked up entirely. It has not been in service since it initially locked up. I guess I could out and rebuild to see if that restores it to service.

Some days you're the windshield and some days you're the bug....

Should have more info after this weekend, got a patch to install. Thanks so much for your insight, it is so greatly appreciated!

Baron

J. Baron Ledford LVCU
Senior Project Engineer
Nu-Vision Technologies LLC
Georgia Offices

 

[johnpoole]

if it has never been up then i would suspect the wireing or the console itself.. when i have that kind of a problem i move the 2250 to the frame and connect just the 2 tn's to the 1st two pair... that removes the possiblity of a layer one problem

john poole
bellsouth business
columbia,sc

 

[ledfordb]

John,
The console was in place and had been working for well over a month before the failure occured, that is what strikes me as strange.

Just now we started the PEP installation and now it shows that file P18006D5 is corrupted and cannot be written to the directory on the PCMCIA drive. I have Nortel slated for a callback.

Jeez, will it never end? I'll let you know more if you like, as I progress. Thanks again for your time!

Baron

J. Baron Ledford LVCU
Senior Project Engineer
Nu-Vision Technologies LLC
Georgia Offices