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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NAM 'remembering' old DN ports 3

Status
Not open for further replies.

AlquestTech

Technical User
Jan 29, 2003
295
US
I could not find a thread about this, if there was one I apologize.
One of my techs is having a problem on a MICS where he has changed the DN of a port but the NAM seems not to be aware of it.
I'll make up two numbers for ease of explanation, as follows:

He changed extension 4177 to extension 2132 and 2132 to extension 4177.
The NAM allows him to build a mailbox for extension 2132, but every time he tries to build one for 4177, he gets as far as COS and then it says "mailbox cannot be created" and kicks him out of admin.

To complicate matters, every time he tries to call through the Auto Attendant, if he dial 4177 it transfers him to station 2132, (the old port for 4177).
He even tried changing 4177 to ext. 5177 yet when he dials 4177 in the Auto Attendant, it still transfers him to 2132.

Anyone know how I can fix this?

I have run into this problem before but and have worked around it by using totally new/different ports and numbers.
Unfortunately, that is not an option this time.

Would restarting the NAM clear this problem?
Does anyone know what causes this problem so we can avoid it in the future?

Thanks for any help.
 
try turning autoset off if its on then reboot the whole system first bring up ksu then nam

Pat Guido
NEXTIRAONE
Pat.guido@nextiraone.com

Formerly Nextira, formerly Williams Communications, formerly Wiltel, formerly Nortel networks, formerly Northern Telecom, formerly, Nynex meridian systems formerly Northern Telecom.

 
I'm sorry.. I am not familiar with the term autoset.You are not referring to set relocation are you?
 
Yeah... Set relocation is not enabled.
I will have him try the power up tomorrow.
 
Everything I've ever seen says the NAM has to be rebooted after making the change you describe above. You do not need to reboot the KSU.

These days, I just move the cross connects, and I don't have this problem.
 
I agree, That was my original suggestion but for whatever reason, my guy says he cannot so I'll try your suggestion. Thanks.
 
That fixed the problem Thanks.
Also to get it out of the tree he had to disable the tree and then reenable it. (FYI)

Thanks again for your help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top