Configuring IPSLA via SNMP RW (Set)

rwandreas · ‎03-31-2011

Anyone have an example of configuring IPSLA, specifically path-echo, via SNMP rather than CLI. Would like to have IPSLA triggered by NMS as result of application alerts.

Thx

Nael Mohammad · ‎04-01-2011

You will need to use the CISCO-RTTMON-MIB which can be viewed here http://www.cisco.com/go/mibs. Depending on your goals, you will need to identify which OID to use. The whitepaper about IP SLA under "Creating Operations with the RTTMON MIB" should give you a starting point for which OID's to use. And keep in mind, most NMS such as LMS and Orion have the ability to configure IP SLA from the respective programs.

http://www.cisco.com/en/US/technologies/tk648/tk362/tk920/technologies_white_paper09186a00802d5efe.html

rwandreas · ‎04-01-2011

Thanks for your assistance:

This is the target device: Cisco IOS Software, 1841 Software (C1841-ADVIPSERVICESK9-M), Version 12.4(24)T3

Copying and pasting from the referenced IPSLA Whitepaper for Path Echo operation:

rttMonCtrlAdminStatus. -Integer 4 \

rttMonCtrlAdminRttType. -Integer 2 \

rttMonEchoAdminProtocol. -Integer 2 \

rttMonEchoAdminTargetAddress. -OctetString "05 00 00 02" \

rttMonScheduleAdminRttStartTime. -TimeTicks 1 \

rttMonScheduleAdminConceptRowAgeout. -Integer 0

Substituted appropriate to arrive at:

snmpset -v 2c -c Q845q8st 10.252.28.122 rttMonCtrlAdminStatus.555 -Integer 4 \
rttMonCtrlAdminRttType.555 -Integer 2 \
rttMonEchoAdminProtocol.555 -Integer 2 \
rttMonEchoAdminTargetAddress.555 -OctetString "05 00 00 02" \
rttMonScheduleAdminRttStartTime.555 -TimeTicks 1 \
rttMonScheduleAdminConceptRowAgeout.555 -Integer 0

[randreas@localhost ~]$ snmpset -v 2c -c Q845q8st 10.252.28.122 rttMonCtrlAdminStatus.555 -Integer 4 \
> rttMonCtrlAdminRttType.555 -Integer 2 \
> rttMonEchoAdminProtocol.555 -Integer 2 \
> rttMonEchoAdminTargetAddress.555 -OctetString "05 00 00 02" \
> rttMonScheduleAdminRttStartTime.555 -TimeTicks 1 \
> rttMonScheduleAdminConceptRowAgeout.555 -Integer 0
rttMonCtrlAdminStatus.555: Bad object type: -

Doesn't like the "-"

[randreas@localhost ~]$ snmpset -v 2c -c Q845q8st 10.252.28.122 rttMonCtrlAdminStatus.555 Integer 4 \
> rttMonCtrlAdminRttType.555 Integer 2 \
> rttMonEchoAdminProtocol.555 Integer 2 \
> rttMonEchoAdminTargetAddress.555 OctetString "05 00 00 02" \
> rttMonScheduleAdminRttStartTime.555 TimeTicks 1 \
> rttMonScheduleAdminConceptRowAgeout.555 Integer 0
rttMonEchoAdminTargetAddress.555: Bad object type: O

Doesn't like the OctetString object type for Target Address. Didn't like Hex-STRING either. Only thing that it would accept was "I"

[randreas@localhost ~]$ snmpset -v 2c -c Q845q8st 10.252.28.122 rttMonCtrlAdminStatus.555 Integer 4 \
> rttMonCtrlAdminRttType.555 Integer 2 \
> rttMonEchoAdminProtocol.555 Integer 2 \
> rttMonEchoAdminTargetAddress.555 i "5.0.0.2" \
> rttMonScheduleAdminRttStartTime.555 TimeTicks 1 \
> rttMonScheduleAdminConceptRowAgeout.555 Integer 0
rttMonScheduleAdminRttStartTime.555: Bad object type: T

TimeTicks not valid object type. Again only I was accepted:

[randreas@localhost ~]$ snmpset -v 2c -c Q845q8st 10.252.28.122 rttMonCtrlAdminStatus.555 Integer 4 \
> rttMonCtrlAdminRttType.555 Integer 2 \
> rttMonEchoAdminProtocol.555 Integer 2 \
> rttMonEchoAdminTargetAddress.555 i "5.0.0.2" \
> rttMonScheduleAdminRttStartTime.555 i 1 \
> rttMonScheduleAdminConceptRowAgeout.555 Integer 0
rttMonCtrlAdminStatus.555: Unknown Object Identifier (Sub-id not found: (top) -> rttMonCtrlAdminStatus)
rttMonCtrlAdminRttType.555: Unknown Object Identifier (Sub-id not found: (top) -> rttMonCtrlAdminRttType)
rttMonEchoAdminProtocol.555: Unknown Object Identifier (Sub-id not found: (top) -> rttMonEchoAdminProtocol)
rttMonEchoAdminTargetAddress.555: Unknown Object Identifier (Sub-id not found: (top) -> rttMonEchoAdminTargetAddress)
rttMonScheduleAdminRttStartTime.555: Unknown Object Identifier (Sub-id not found: (top) -> rttMonScheduleAdminRttStartTime)
rttMonScheduleAdminConceptRowAgeout.555: Unknown Object Identifier (Sub-id not found: (top) -> rttMonScheduleAdminConceptRowAgeout)

Beyond my understanding what these messages mean

Nael Mohammad · ‎04-08-2011

What kind of NMS are you using? It would be easier to configure this using the application. The values provided will only work after IP SLA has already been configured on the device itself.

rwandreas · ‎04-11-2011

We use CA Spectrum and OpenNMS - http://www.opennms.org/wiki/Main_Page, neither of which have built-in support for IPSLA.

We run IPSLA UDP Jitter probes which are configured to send alerts to Spectrum and OpenNMS on loss. OpenNMS or Spectrum would then via SNMP configure PathEcho. OpenNMS would poll RTTMON MIB to get hops/interfaces and then poll MIB2 and other stats looking for router and interface errors/exceptions on the path. Would prefer to use RFC 2925 for SNMP definition of traceroute, but Cisco chose not to implement (Juniper did!).

Not sure what you mean that IPSLA already configured on the device. We used Sev1 to configure the initial IPSLA probes, the ones mentioned above which send alerts to OpenNMS. There was no IPSLA configured on the router and Sev1 had no problem defining and scheduling UDP Jitter and HTTP Get operations. Sev1 unfortunately has no capability as a trap receiver or we would use it to dynamically generate the PathEcho.