Change IP address successfully, but SNMP says no!!!

[absinthium]

Hi all,

I have a problem that has occurred on every CS1KS/M rls 4.5+ (SSC, pure TDM)

I change the IP addresses for active and inactive ELNK fine.
Can ping, can Rlogin, all good....

Then configure SNMP traps. Alarms trigger traps correctly, I can receive them fine, but the trap states that it's source is the old IP address!

The only way I have figured out how to resolve this is by INI each switch!! I have 11 more to do and really don't want to INI all of them (rule of averages).

Has anybody seen this before, and more importantly, does anybody have any suggestions on how fix it?

I am threatening to edit the net files in PDT...

 

[bigindian65]

what is wrong with the INI, it isn't taboo.

Mato' Was'aka

 

[absinthium]

What's wrong is that I don't want to do it to every single one every time. Have to schedule after hours INI and not forgetting the fact that 1 in x will go tits up.

I forgot to mention that I am doing these remotely!!

 

[Avaya911PLM]

Did you try an EDD on the switches? I know new destinations do not go into effect until you EDD

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcast

 

[allenmac]

I believe Fletch is correct. You must EDD the switch for the changes to be updated in SNMP.

 

[absinthium]

I have done an EDD after configuration. When you stat host in 117 i can see where the old IP address is coming from as it is still in the active host table, even if it is preceded with a -- for no active ID.

So far only an INI has successfully cleaned this table and the SNMP trap source field.

 

[MagnaRGP]

How about LD 117 Update DBS?

 

[absinthium]

Update DBS has no effect either. I don't think there is any way of escaping an INI