However, if I manually source the ping it works fine: community string is like a preshared password which must be configured on both the ASA and the. ASA(config) snmp-server host interfacename ipaddress community community string Where interface name is the ASA interface through which the NMS can be reached, and ip address is the NMS address. The main difference between the other ASAs is that with the 5505 you have 10 ports.

Latest operation start time: 09:25:08.110 EST Fri Dec 20 2019 Step2: Identify the NMS host that can connect to the ASA for SNMP management. Below is an example of a basic configuration for an ASA 5505 Firewall. Latest RTT (milliseconds): NoConnection/Busy/Timeout Number of Octets Used by this Entry: 2056 Unfortuntately, I'm getting timeouts as if traffic is not making it: Sla monitor schedule 20 life forever start-time now Type echo protocol ipIcmpEcho 192.168.72.254 interface inside What if we want to monitor a destination which is reachable through a Site to Site VPN? I have configured it by using the inside interface to source it, but unfortunately this is not working. Guys - In those configuration examples, we are basically monitoring a destination in the Public Internet and using the outside interface to source it.

Cisco asa 5505 configuration example