Cisco IP SLA Monitor
Subscribe

From OpenNMS

Jump to: navigation, search

Contents

Monitoring Cisco IP SLA

This plugin can be used to monitor IP SLA configurations on your Cisco devices. There is a second Cisco_IP_SLA_Support in OpenNMS which collects the performance data from IP SLA setups for visualization, threshold checking, and Top-N reporting. In contrast to this performance data collection support, this method implements the monitoring based on a service.

This monitor supports the following SNMP OIDS from CISCO-RTT-MON-MIB: 

  RTT_ADMIN_TAG_OID = .1.3.6.1.4.1.9.9.42.1.2.1.1.3
  RTT_OPER_STATE_OID = .1.3.6.1.4.1.9.9.42.1.2.9.1.10
  RTT_LATEST_OPERSENSE_OID = .1.3.6.1.4.1.9.9.42.1.2.10.1.2
  RTT_ADMIN_THRESH_OID = .1.3.6.1.4.1.9.9.42.1.2.1.1.5
  RTT_ADMIN_TYPE_OID = .1.3.6.1.4.1.9.9.42.1.2.1.1.4
  RTT_LATEST_OID = .1.3.6.1.4.1.9.9.42.1.2.10.1.1

Configure tests on your Cisco equipment

In this example we configure a IP SLA entry to monitor Googles website with HTTP GET. We use 4.4.4.4 as our DNS-Server, if this server is not working for you, just take someone from your ISP. In our example our SLA says we should reach Googles website within 200ms. To tell some other admin fellows, this monitor is used for monitoring, I set the owner to OpenNMS. The tag is used to identify the entry for monitoring. 

ip sla monitor 1
 type http operation get url http://www.google.de name-server 4.4.4.4
 timeout 3000
 threshold 200
 owner OpenNMS
 tag Google Website
ip sla monitor schedule 3 life forever start-time now

In the second example we configure a simple IP SLA to monitor an IP-address with a simple ping, in this example the IP from www.opennms.org is used. Like the example above we have a threshold and a timeout. 

ip sla 1
 icmp-echo 216.216.217.254
 timeout 3000
 threshold 150
 owner OpenNMS
 tag OpenNMS Host
ip sla schedule 1 life forever start-time now

Hint: It´s not possible to reconfigure a IP SLA entry. If you would like change parameters, you have to delete the whole configuration and reconfigure it with your new parameters. Backup your Cisco configuration manually or take a look at RANCID.

Configure OpenNMS for automatic detection

If you have meshed networks like MPLS or whatever, it can be interesting to monitor the same targets from different locations. In this case you can roll-out a lot of similar IP SLA setups maybe with different thresholds or timeouts on your Cisco equipment. The magic of capsd make the job and help during the roll-out. First we configure in capsd-configuration.xml the following new plugins 

<protocol-plugin protocol="IP-SLA-WEB-Google"
  class-name="org.opennms.netmgt.capsd.plugins.CiscoIpSlaPlugin" scan="on">
    <property key="timeout" value="2000" />
    <property key="admin-tag" value="Google Website" />
    <property key="retry" value="1" />
</protocol-plugin>
<protocol-plugin protocol="IP-SLA-PING-OpenNMS"
  class-name="org.opennms.netmgt.capsd.plugins.CiscoIpSlaPlugin" scan="on">
    <property key="timeout" value="2000" />
    <property key="admin-tag" value="OpenNMS Host" />
    <property key="retry" value="1" />
</protocol-plugin>

The service is on each Cisco equipment detected, if a IP SLA with tag "Google Website" is configured.

Configure OpenNMS to monitor IP SLA

There two options to monitor the IP SLA. You can monitor the generic availability with monitoring the timeout. If you set ignore-thresh to true the service goes down if the timeout is reached, else the service goes down if the threshold is exceeded. 

<service name="IP-SLA-WEB-Google" interval="300000"
  user-defined="false" status="on">
    <parameter key="retry" value="2" />
    <parameter key="timeout" value="3000" />
    <parameter key="admin-tag" value="Google Website" />
    <parameter key="ignore-thresh" value="false" />
</service>
<service name="IP-SLA-PING-OpenNMS" interval="300000"
  user-defined="false" status="on">
    <parameter key="retry" value="2" />
    <parameter key="timeout" value="3000" />
    <parameter key="admin-tag" value="OpenNMS Host" />
    <parameter key="ignore-thresh" value="false" />
</service>
<monitor service="IP-SLA-WEB-Google" class-name="org.opennms.netmgt.poller.monitors.CiscoIpSlaMonitor" />
<monitor service="IP-SLA-PING-OpenNMS" class-name="org.opennms.netmgt.poller.monitors.CiscoIpSlaMonitor" />

Version History/Availability

Retrieved from "http://www.opennms.org/wiki/Cisco_IP_SLA_Monitor"