I am trying to configure the sending of basic snmp traps on a FWSM running 3.2(1) to ServersAlive and have had some success.
Purely for testing purposes, I am able to get alerted on sending snmp requests to the FWSM with bad authentication.
According to "Cisco ASA, PIX, and FWSM Firewall Handbook, Second Edition" Hucaby et al. the FWSM,PIX etc sends OID's depending on product.
For example, FWSM in single-congle context mode sends 188.8.131.52.184.108.40.206.522.
I have this configured as my enterprise OID on ServersAlive NMS but have no specific OID 'leaf-node'.
When I send a snmpget to the FWSM with a bad community string, I get an alert, as desired.
Can someone tell me where specific OID's come into play with FWSM's? For example, how is the entire OID constructed if it wnats to send a warm/cold start trap?
Any help appreciated.
snmp-server host VLAN205_NMS 10.0.0.1 trap community testsnmp
snmp-server enable traps