SNMP Breaks After Upgrade

john.fleming · ‎04-20-2005

I have run into a situation, we just upgraded to version 7.50.004 of WebNS, and SNMP traps no longer can get to the destination address.

I did a sniffer capture, and the traps are being sent from the VLAN 1 IP address, even though we have a source specified as a different VLAN interface. Has anyone else run into this situation?

Does anyone know a fix?

John Fleming

Gilles Dufour · ‎04-21-2005

I can reproduce the same problem and I think I could find where in the code the problem is.

Could you just let me know what version you were running previously so I can verify my idea.

Thanks,

Gilles.

Gilles Dufour · ‎04-21-2005

John,

actually the behavior is correct.

You can't set the source ip of the ip packet.

All you can do is change the sourceip of the Agent specified in the snmptrap.

you can see it if you do

CSS11503(config)# snmp trap-source ?

egress-port Use the Egress Port IP in the Agent-Address field

management Use the Management Port IP in the Agent-Address field

specified Specify IP to use in the Agent-Address field

If you want the CSS to use a different vlan and a different ip you need to configure a static route pointing trough the correct vlan.

This behavior has always been like this.

Regards,

Gilles.

john.fleming · ‎04-21-2005

Gilles,

Thanks for your reply. My previous version was 7.30.106. Actually 2 of them were still running 7.20.

Thing is the default route for all the VLANS in the CSS's is the PIX, and the PIX knows the route to the Openview Box. So any additional Static routes would still be to the same PIX interface.

I am not sure how that will help.

Here is what my SNMP setup looks like:

snmp trap-type enterprise

snmp community ***** read-only

snmp community ***** read-write

snmp community squash read-only

snmp trap-type enterprise service-transition

snmp trap-type enterprise reload

snmp trap-source specified 10.0.50.2

snmp trap-host 10.0.10.69 *****

snmp name "YBKOPCSS11503_1"

The specified source is VLAN400, but the traps are being generated from the ip address assigned to Vlan1.

John