Unbrowse has 3 ways to receive traps. Each of these are called providers. Here is a quick tip of how and when to use each of these.
The normal UDP socket.
- Listen on a specific port only
- Traps must be sent to the machine running Unbrowse
- Cannot have any process other than Unbrowse listening for traps
- Best option if Unbrowse is the primary trap receiver
Windows Raw Sockets.
- Listens for traps using Windows Raw sockets.
- Listens on all ports.
- Can have other processes listening for traps on the same port.
- Reliable on XP and Vista Home versions. Not so reliable on Vista Enterprise.
- May result in ICMP Destination Unreachable if Unbrowse is the main trap receiver
- Use this provider only if you want Unbrowse to receive traps on a system already running another trap reciever or for debugging
Winpcap.
- Listens for traps using the Winpcap packet capture library.
- You can get Winpcap from
Winpcap download
- Listens on all ports.
- Works reliably on all platforms (XP and Vista)
- May result in ICMP Destination Unreachable if Unbrowse is the main trap receiver
- Use this when deploying Unbrowse as a passive trap receiver. You can log all traps even those sent to other systems by using port mirroring
.
You can select a provider from the above 3 options via Tools > Customize > Trap Console > Preferred Provider.
The currently active provider is shown at the bottom of the trap console.
Hope this tip helps uses of Unbrowse SNMP with their trap monitoring needs.
--
Unleash Networks
