SNMP Traps use the CSS boot (management) IP

[dcayer]

We run WebNS 5.00b37 on 8 CSS' managed in-band with management interfaces disabled and boot-config IP left to the default value of 1.1.1.1.

Traps received on our SNMP trap collector show the CSS boot-config IP as the trap source. This makes the SNMP trap logs somewhat useless, since all traps apear to originate from the same 1.1.1.1 device. I thought of changing the boot-config IP to a valid (routable) IP, which would basically act as a loopback IP. Would this work? I also found references to WebNS 5.03, which now has a "snmp trap source" command to apparently fix my problem. This version also now has TACACS capabilities. Unfortunately, I cannot find this version on the Cisco software centre. Any idea where it is kept?

[tirawlins]

See if you can get to it here:

http://www.cisco.com/cgi-bin/tablebuild.pl/webns-maint

[dcayer]

I tried; the latest version listed is ap0500063.adi.gz (V5.0B63).

I'm looking for V5.03B15.

[dcayer]

Oops... found it under teh feature release link:

- 5.03b15 is a feature release (http://www.cisco.com/cgi-bin/Software/Tablebuild/doftp.pl?ftpfile=cisco/content-delivery/webns/feature-rel/ap0503015.adi.gz&swtype=FCS&software_products_url=%2Fcgi-bin%2Ftablebuild.pl%2Fwebns-feature&isChild=&appName=)

Thanks.