Switches, Hubs, and Modems
1753726 Members
4899 Online
108799 Solutions
New Discussion юеВ

Re: Disabling "end node unreachable" events?

 
Preston Gallwas
Valued Contributor

Disabling "end node unreachable" events?

Every day...hundreds of our machines shut down when workers go home. Can the "DISCOVERY" events for END NODE UNREACHABLE be turned off?

What is the benefit for monitoring end nodes in PCM?
5 REPLIES 5
Les Ligetfalvy
Esteemed Contributor

Re: Disabling "end node unreachable" events?

Yes, it is very annoying. I have been blocking them from discovery as quickly as they get discovered. The discovery should have and IP range exclusion.
Preston Gallwas
Valued Contributor

Re: Disabling "end node unreachable" events?

Will excluding them from PCM 2.0+ prevent us from doing a find end-node or node-to-node search?

Preston Gallwas
Valued Contributor

Re: Disabling "end node unreachable" events?

Ive excluded them and are still receiving events...

arg
Ted Nguyen
Advisor

Re: Disabling "end node unreachable" events?

Preston,

Good point. Currently, there isn't an easy way to turn off "DISCOVER" events for end nodes. You'll need to restrict the Discovery's subnet ranges to exclude these end-node ip addresses and delete all end nodes that have already been discovered. Since end-nodes are discovered using the default SNMP read community configured in PCM, you can change this default SNMP read community name in PCM and also delete the end-nodes from PCM, but this will require you to configue all new switches that will be added to the network with the new community name since Discovery uses the default community name configured in PCM to discover new devices. We'll look into this issue.

Excluding the end-nodes from Discovery will not affect Find Node or Node-to-Node path trace.

Hope this helps.
Thanks for your input.
Ted
Preston Gallwas
Valued Contributor

Re: Disabling "end node unreachable" events?

Oy. We can't exclude the ranges, due to the fact that all switches we have are DHCP save the stack commanders at each location, which are static

Thanks...a ...patch..for...removing/excluding those events would be...fantastic ;)