SNMP Traps and DNS resolving

[Antony]

I'd like to know if i can monitor for snmp traps a netbios name, instead of an ip address. This can be done for snmp get checking.
I 'd rather get in the notification email not the ip address of the monitored device, but its netbios name.

I have setup a hosts file which i use for this. So, this way when i setup a snmp get check for ip 192.168.1.1, i get an email that says "Host device1 interface is down" instead of "Host 192.168.1.1 interface is down".

Can i do this for snmp traps as well? If not, will this feature be added soon? Is there a way to resolve the ip into a netbios name (for snmp traps notification)?

Thanks alot!

[KS-Soft]

H'm, its complicated. Unlike SNMP Get requests, HostMonitor handles SNMP Trap messages in real time. If 20 messages comes at the same second, HostMonitor cannot spend much time to resolve IP address. Processing should be as quick as possible...
I have added request into "to do" list, but I don't know when it can be implemented.

Regards
Alex

[sneader]

Hi Alex,

I would REALLY like to see this as an option, also.

I get a lot of messages like:

Subject: 172.23.25.40 Link Down (3.0)

Then I have to go to a spreadsheet and find that IP, and figure out what device that was.

I would much prefer to create a Host File on my machine, which would do a reverse DNS lookup, so that instead I would get:

Subject: LA-Cisco3550 172.23.25.40 Link Down (3.0)

(or something like that -- the concept is that I would know the name and location of that switch, in addition to its IP)

I understand the problem you have, if a lot of traps are coming in at once, we can't take time to do lookups. I am not sure how you could handle this... maybe it is an option for the users to decide, like this:

__ Do Reverse DNS Lookup on SNMP Traps (Warning, this may cause some SNMP trap messages to be lost if many traps are received simultaneously!!)

i.e. give us the option, but warn us about the problem.

Here, we don't seem to have more than 1 event per second, if that, so I would rather have usable Trap messages vs. the potential chance I may lose a Trap.

Thanks for listening... (and maybe there is a better way to achieve the solution)

- Scott

[KS-Soft]

May be its good idea to use local file (by HostMonitor). This way you may specify host name or some useful information, like "192.168.5.47 old server on 1st floor, ph 206-555-7777".
Yes, you are right. Its not necessary for other test methods, but it would be really good option for SNMP Trap" test...
Ok, I increased priority of this task

Regards
Alex

[sneader]

Alex, I can tell you we will have a PARTY here in our office, when you implement this feature! The local file is a great idea... I do not need it to be a DNS file. Whatever works best for you.

Thank you !!!!!!!

- Scott

[AntonyP]

Alex, I can tell you we will have a PARTY here in our office, when you implement this feature! The local file is a great idea... I do not need it to be a DNS file. Whatever works best for you.

Thank you !!!!!!!

- Scott

Local file is fine by me as well

[KS-Soft]

Ok, may be in next version (6.20)...

Regards
Alex

[KS-Soft]

Done, version 6.20 Beta available at http://www.ks-soft.net/hostmon.eng/downpage.htm
Now you may specify host names and/or host descriptions in HostInfo.LST file and use %TrapHostInfo% macro variable in actions triggered by SNMP Trap test method. Sample HostInfo.LST file included in the package

Regards
Alex

[AntonyP]

Thank you!!

[sneader]

Done, version 6.20 Beta available at http://www.ks-soft.net/hostmon.eng/downpage.htm
Now you may specify host names and/or host descriptions in HostInfo.LST file and use %TrapHostInfo% macro variable in actions triggered by SNMP Trap test method. Sample HostInfo.LST file included in the package

Regards
Alex

Alex, this works GREAT !!!!!!!!!!!!!!!! We are THRILLED with this. Thank you, Thank you, Thank you !!!!!!!!!!

- Scott

[KS-Soft]

You are welcome

Regards
Alex