You can send traps to multiple destinations but if the destinations are on
the same node, then Netview's control desk will display duplicates of each
trap received. Of course sending duplicate traps means the UDP packet
traffic is doubled and might lead to congestion on the network .
Incidentally, the SNMP protocol explicitly uses the connectless UDP because
the philosophy was to minimize management traffic so as not to interfere
with data traffic on the network. Moreover, this is why the SNMP
philosophy calls for polling devices to ensure their status, which netmon
In fact, when you think about a "route failure", then the device that is
broken causing the route failure is highlighted in NetView as "DOWN" and
all devices downstream are also considered "DOWN". In this case it is the
device that caused the route failure that needs to be fixed, not the remote
device that may also be originating a trap. When the broken device is
fixed, then netmon polls everything downstream for a status update anyway.
Moreover, depending on your network topology, the more remote the network
device that breaks is from the NetView server, the less chance you will
have of dropping other traps.