Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Monitor Cisco ASA VPN Tunnel

Monitor Cisco ASA VPN Tunnel

Table of contents

Overview

This article describes how to monitor Cisco ASA VPN tunnels by monitoring a secondary variable from the Cisco MIB trees and using this information to infer the status of the tunnel.

Monitoring of the UP/Down status of a Cisco ASA VPN tunnel is not as straight forward as a regular physical or VLAN interface. This is because VPN tunnels fall outside the scope of  RFC 1213 MIB's ifTabletree.

Environment

  • All NPM versions
  • Cisco ASA VPN/IPSEC

Steps

  1. Configure a Universal Device Poller for monitoring of a your required MIB. Refer to Monitoring MIBs with Universal Device Pollers.
  2. Configure the custom MIB to point to the cikeGlobalActiveTunnels oid : 1.3.6.1.4.1.9.9.171.1.2.1.1, this gives you the number of IPSec Tunnels or you can use the “ciscoIpSecFlowMonitorMIB" “1.3.6.1.4.1.9.9.171 which is one that has been recommended by CISCO.
  • The OID used in Step 2 is one of many options that could be used to monitor depending on what specific information you require but for the purposes of this example it is deemed most suitable for monitoring of active VPNs.
  • One other option is to configure the IP SLA Monitor to each tunnel endpoint and use the inherit trap capabilities of IPSLA to monitor tunnel failures.

 

Last modified
07:34, 20 Jul 2017

Tags

Classifications

Public