https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651210#M6160 Every day...hundreds of our machines shut down when workers go home. Can the "DISCOVERY" events for END NODE UNREACHABLE be turned off?<BR /><BR />What is the benefit for monitoring end nodes in PCM?<BR /> Mon, 17 Oct 2005 16:56:22 GMT Preston Gallwas 2005-10-17T16:56:22Z https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651210#M6160 Every day...hundreds of our machines shut down when workers go home. Can the "DISCOVERY" events for END NODE UNREACHABLE be turned off?<BR /><BR />What is the benefit for monitoring end nodes in PCM?<BR /> Mon, 17 Oct 2005 16:56:22 GMT https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651210#M6160 Preston Gallwas 2005-10-17T16:56:22Z https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651211#M6161 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. Mon, 17 Oct 2005 21:01:40 GMT https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651211#M6161 Les Ligetfalvy 2005-10-17T21:01:40Z https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651212#M6162 Will excluding them from PCM 2.0+ prevent us from doing a find end-node or node-to-node search?<BR /><BR /> Tue, 18 Oct 2005 10:23:06 GMT https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651212#M6162 Preston Gallwas 2005-10-18T10:23:06Z https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651213#M6163 Ive excluded them and are still receiving events...<BR /><BR />arg<BR /> Tue, 18 Oct 2005 13:11:40 GMT https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651213#M6163 Preston Gallwas 2005-10-18T13:11:40Z https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651214#M6164 Preston,<BR /><BR />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.<BR /><BR />Excluding the end-nodes from Discovery will not affect Find Node or Node-to-Node path trace.<BR /><BR />Hope this helps.<BR />Thanks for your input.<BR />Ted Tue, 18 Oct 2005 14:07:38 GMT https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651214#M6164 Ted Nguyen 2005-10-18T14:07:38Z https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651215#M6165 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<BR /><BR />Thanks...a ...patch..for...removing/excluding those events would be...fantastic ;)<BR /> Tue, 18 Oct 2005 14:48:32 GMT https://community.hpe.com/t5/switches-hubs-and-modems/disabling-quot-end-node-unreachable-quot-events/m-p/3651215#M6165 Preston Gallwas 2005-10-18T14:48:32Z