Dynamic node stops responding in NPM

Confused.... I added a node as a dynamic IP address and used the FQDN and it worked. I was able to poll it and get SNMP off of it.

When they rolled the node and the IP address changed it showed down in Orion. I opened up system manager and looked and it still had the old IP (greyed out) so I tried to poll it - no go. I tried to rediscover it - no go.

What is funny is that I can drop down to the Orion server comamnd prompt and ping the device succesfully by FQDN and it resolves the IP - just not in Orion.

Why can't Orion do this? What am I missing?

Find more posts tagged with

fqdn

dynamic_ip

Accepted answers

All comments

Karlo.Zatylny

We had a bug with the dynamic ip addresses that was fixed in 9.5. Have you upgraded to 9.5 SP2?

Thanks

FormerMember

Nope. We are waiting until the dust storm settles with 9.5. I have read and heard way too many horror stories with this version and mgmt will not allow me to cut over until they can be assured they will not be blind.

Is there a work around for this outside of upgrading?

Karlo.Zatylny

Hi,

Actually, one thing to check is if the Caption and HostName (DNS) of the Node are the same. They should be in order to work properly without the fix. Then just restart the NetPerfMon service. Let me know if this works for you.

Thanks

david.templeton

Using 9.5.1 here and having the same sort of problem.

I set the Caption and DNS to the FQDN, then restarted the NetPerfMon service. After a while, the DNS changes to the FQDN of the NPM server, and the IP address changes to the server's IP.

Thanks,

Dave