NAM changing DN 1

[mroberts]

Hi guys,
I have a customer who installed their fiber NAM last year and during the year the NAM has spontaneously changed it's identifying DN (F985)three times. This, of course, messes up their FNA settings. Have any of you seen the NAM do this and can we stop it?
Thanks
MRoberts

 

[DueE]

I've not heard of that before but you might check to see if "set relocation" is Y, if so change to N.
DueE

 

[schlum]

Never seen that one before, but could they possibly be changing the slot on the expansion card where the NAM is connected, maybe when they try to add another module? This would cause your problem if set relocate was set to no.

Schlum

 

[Guest_imported]

I have seen the fibre nam change its dn only when going through a ds30 ( 8x24 ksu > ds30 > fibre nam ) adaptor along with other numerous problems with the ds30 adaptor.

 

[Arr]

I havn't had any real trouble with the DS30 Stn adapter and a DR5 8X24.

There might be a hard drive problem, and there might be a ram problem and there might be a fibre connector that doesn't make good contact.

Try defaulting the NAM if it not too big a deal.

Sometimes the lack of sufficient RAM might cause too much file swapping.
What is the traffic like - is the NAM near its limmits?

PhM

 

[mroberts]

This NAM 4.0 is connected to an OX32 4.0 via a DS30 Fiber cable to a 6port exp. card in slot 3. It hasn't moved from slot 3 or the port on the card. The NAM isn't in a high traffic situation and only has about 25 mailboxes so it isn't using a crude load of memory either. Other than it changing it's F985 identifying DN, it is working perfectly.

 

[jerryreeve]

I did have one case where the DN's changed back do default on me, I had a 0x32 with NAM 0x16 and ASM, it only happened once and I think that the change occured during a power failure to the KSU, the change back to default numbering kept the line and trunk assignments as well as call forwarding info but when I changed the DN back the line and trunk assignments and forwarding info stayed with the port. I just figured it was a one time fluke and hoped it never happened again, Put an UPS on it and alls well. JerryReeve
Communications Systems Int'l
com-sys.com

 

[mikescience]

I have seem this many times on copper and a couple times on fiber. For whatever reason the lead dn port is not seen by the NAM and the NAM goes to the next DN. Once, it was a bad fiber spool. The other time was unresolved. Make sure that all of your channels are seen under F915.
Mikescience