IP SLA
IP SLAs with SNMP traps
(1)
<< Settings >>
ip sla reaction-configuration
<< debug snmp packet & console messages >>
*Mar 1 01:40:49.727: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:40:49.727: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 1
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 0A 07 07
rttMonCtrlOperConnectionLostOccurred.1 = 1
*Mar 1 01:40:49.743: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:40:49.743: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 5
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 0A 07 07
rttMonCtrl.19.1.2.1 = 8
rttMonCtrl.19.1.10.1 = 1
rttMonCtrl.19.1.9.1 = 1
rttMonCtrl.19.1.5.1 = 0
rttMonCtrl.19.1.6.1 = 0
SW2#
rttMonEchoAdminEntry.33.1 = 00 00 00 00
*Mar 1 01:40:49.979: SNMP: Packet sent via UDP to 10.10.128.130
*Mar 1 01:40:50.235: SNMP: Packet sent via UDP to 10.10.128.130
(2)
<< Settings >>
ip sla reaction-configuration
snmp-server enable traps ipsla
<< debug snmp packet & console messages >>
*Mar 1 01:37:34.715: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:37:34.719: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 1
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 0A 07 07
rttMonCtrlOperConnectionLostOccurred.1 = 1
*Mar 1 01:37:34.731: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:37:34.731: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 5
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 0A 07 07
rttMonCtrl.19.1.2.1 = 8
rttMonCtrl.19.1.10.1 = 1
rttMonCtrl.19.1.9.1 = 1
rttMonCtrl.19.1.5.1 = 0
rttMonCtrl.19.1.6.1 = 0
rttMonEchoAdminEntry.33.1 = 00 00 00 00
*Mar 1 01:37:34.971: SNMP: Packet sent via UDP to 10.10.128.130
*Mar 1 01:37:35.227: SNMP: Packet sent via UDP to 10.10.128.130
<< Comparison & Result >>
snmp packets are same as condition (1).
(3)
<< Settings >>
ip sla reaction-configuration
ip sla logging traps
<< debug snmp packet & console messages >>
*Mar 1 01:45:04.687: %RTT-4-OPER_CLOSS: condition occurred, entry number = 1
*Mar 1 01:45:04.703: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:45:04.703: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 1
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 0A 07 07
rttMonCtrlOperConnectionLostOccurred.1 = 1
*Mar 1 01:45:04.719: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:45:04.719: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 5
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 0A 07 07
rttMonCtrl.19.1.2.1 = 8
rttMonCtrl.19.1.10.1 = 1
rttMonCtrl.19.1.9.1 = 1
rttMonCtrl.19.1.5.1 = 0
rttMonCtrl.19.1.6.1 = 0
rttMonEchoAdminEntry.33.1 = 00 00 00 00
*Mar 1 01:45:04.739: %RTT-3-IPSLATHRESHOLD: IP SLAs(1): Threshold Occurred for connectionLoss
SW2#
*Mar 1 01:45:04.955: SNMP: Packet sent via UDP to 10.10.128.130
*Mar 1 01:45:05.211: SNMP: Packet sent via UDP to 10.10.128.130
<< Comparison & Result >>
new 2 messages appear
*Mar 1 01:45:04.687: %RTT-4-OPER_CLOSS: condition occurred, entry number = 1
*Mar 1 01:45:04.739: %RTT-3-IPSLATHRESHOLD: IP SLAs(1): Threshold Occurred for connectionLoss
when it's recovered
*Mar 1 01:49:04.687: %RTT-4-OPER_CLOSS: condition cleared, entry number = 1
*Mar 1 01:49:04.735: %RTT-3-IPSLATHRESHOLD: IP SLAs(1): Threshold Cleared for connectionLoss
(4)
<< Settings >>
ip sla reaction-configuration
snmp-server enable traps syslog
<< debug snmp packet & console messages >>
same as condition (2)
<< Comparison & Result >>
same as condition (2)
(5)
<< Settings >>
ip sla reaction-configuration
ip sla logging traps
snmp-server enable traps syslog
** All of 3 commands above are required.
<< debug snmp packet & console messages >>
*Mar 1 01:55:04.687: %RTT-4-OPER_CLOSS: condition occurred, entry number = 1
*Mar 1 01:55:04.723: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:55:04.727: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 1
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 0A 07 07
rttMonCtrlOperConnectionLostOccurred.1 = 1
*Mar 1 01:55:04.747: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:55:04.747: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 5
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 0A 07 07
rttMonCtrl.19.1.2.1 = 8
rttMonCtrl.19.1.10.1 = 1
rttMonCtrl.19.1.9.1 = 1
rttMonCtrl.19.1.5.1 = 0
rttMonCtrl.19.1.6.1 = 0
rttMonEchoAdminEntry.33.1 = 00 00 00 00
*Mar 1 01:55:04.767: %RTT-3-IPSLATHRESHOLD: IP SLAs(1): Threshold Occurred for connectionLoss
*Mar 1 01:55:04.775: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:55:04.775: SNMP: V1 Trap, ent ciscoSyslogMIB.2, addr 10.10.128.129, gentrap 6, spectrap 1
clogHistoryEntry.2.15 = RTT
clogHistoryEntry.3.15 = 5
clogHistoryEntry.4.15 = OPER_CLOSS
clogHistoryEntry.5.15 = condition occurred, entry number = 1
clogHistoryEntry.6.15 = 690469
*Mar 1 01:55:04.791: SNMP: Queuing packet to 10.10.128.130
*Mar 1 01:55:04.791: SNMP: V1 Trap, ent ciscoSyslogMIB.2, addr 10.10.128.129, gentrap 6, spectrap 1
clogHistoryEntry.2.16 = RTT
clogHistoryEntry.3.16 = 4
clogHistoryEntry.4.16 = IPSLATHRESHOLD
clogHistoryEntry.5.16 = IP SLAs(1): Threshold Occurred for connectionLoss
clogHistoryEntry.6.16 = 690476
*Mar 1 01:55:04.979: SNMP: Packet sent via UDP to 10.10.128.130
*Mar 1 01:55:05.235: SNMP: Packet sent via UDP to 10.10.128.130
*Mar 1 01:55:05.491: SNMP: Packet sent via UDP to 10.10.128.130
*Mar 1 01:55:05.747: SNMP: Packet sent via UDP to 10.10.128.130
<< Comparison & Result >>
Configuration below at SW2 is required.
## SW2 (Trap sendor) ##
ip sla logging traps
ip sla 1
tcp-connect 10.10.7.7 5000 source-ip 10.10.8.8
tos 96
timeout 1000
threshold 3000
frequency 15
ip sla reaction-configuration 1 react connectionLoss threshold-type consecutive 1 action-type trapOnly
ip sla schedule 1 start-time now
snmp-server enable traps syslog
snmp-server host 10.10.128.130 public
## SW1 (Trap Receiver) ##
ip sla responder
ip sla responder tcp-connect ipaddress 10.10.7.7 port 5000
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home