Monitor table examples

If you are going to change any of the monitor table object values for an existing table entry or row, you must take the row out of service to make the changes. To do this, set the value of slapm2PRMonRowStatus to 2. After your changes are made, set the row status to a value of 1 to put it back in service.

The following examples show how to create monitor table entries to monitor.

This example assumes SNMP version 1 security and no SNMPD.CONF file.
1. Enable traps. The snmptrap.dest file should contain the IP address and protocol of an entity to receive traps:
```
/etc/snmptrap.dest   contains: 9.67.191.5        UDP
/etc/pw.src          contains: public 0.0.0.0    0.0.0.0
```
  In this example, use the osnmp command running in the background to receive traps:
```
osnmp trap > /tmp/trap.output &
```
2. Change status to notInService:
```
osnmp set slapm2PRMonRowStatus.index 2
```
3. Enable monitoring for slapm2PolicyRuleMonNotOkay and slapm2PolicyRuleMonOkay (traps):
```
osnmp set slapm2PRMonTrapEnable.index 1
```
4. If wanted, change default thresholds:
  - TCP round trip, where l is the lower boundary and h is the upper boundary:
```
osnmp set slapm2PRMonTcpRttDelayLow.index l
osnmp set slapm2PRMonTcpRttDelayHigh.index h
```
  - TCP retransmit ratio, where l is the lower boundary and h is the upper boundary:
```
osnmp set slapm2PRMonTcpReXmitDelayLow.index l
osnmp set slapm2PRMonTcpReXmitDelayHigh.index h
```
  - Accept Queue delay ratio, where l is the lower boundary and h is the upper boundary:
```
osnmp set slapm2PRMonAcceptQDelayLow.index l
osnmp set slapm2PRMonAcceptQDelayHigh.index h
```
5. Make row active:
```
osnmp set slapm2PRMonRowStatus.index 1
```
Evaluate the following fields to determine why the slapm2PolicyRuleMonNotOkay trap was generated:
- If the maxTcpRttDelayExceeded bit in the previous slapm2PRMonStatus is off, indicating below the high threshold, and the bit in the current slapm2PRMonStatus is on, indicating above the high threshold, this indicates that at the end of this monitor interval this is a rising quantity and the threshold has exceeded its high threshold. Evaluate the slapm2PRMonTcpRTTCurrentDelay to determine the average round-trip time over the most recent interval for all outgoing TCP packets affected by this policy rule.
- If the maxTcpReXmitRatioExceeded bit in the previous slapm2PRMonStatus is off, indicating below the high threshold, and the bit in the current slapm2PRMonStatus is on, indicating above the high threshold, this indicates that at the end of this monitor interval this is a rising quantity and the threshold has exceeded its high threshold. Evaluate the slapm2PRMonTcpCurrentTcpReXmit to determine the TCP retransmit ratio over the most recent interval for all outgoing TCP packets affected by this policy rule.
- If the maxAcceptQueueDelayExceeded bit in the previous slapm2PRMonStatus is off, indicating below the high threshold, and the bit in the current slapm2PRMonStatus is on, indicating above the high threshold, this indicates that at the end of this monitor interval this is a rising quantity and the threshold has exceeded its high threshold. Evaluate the slapm2PRMonAcceptQCurrentDelay to determine the smoothed average accept queue delay over the most recent interval for all flows affected by this policy rule.
Evaluate the following fields to determine why the slapm2PolicyRuleMonOkay trap was generated:
- If the maxTcpRttDelayExceeded bit in the previous slapm2PRMonStatus is on, indicating above the low threshold, and the bit in the current slapm2PRMonStatus is off, indicating below the low threshold, this indicates that at the end of this monitor interval this is a falling quantity and the threshold has fallen below its low threshold. Evaluate the slapm2PRMonTcpRTTCurrentDelay to determine the average round-trip time over the most recent interval for all outgoing TCP packets affected by this policy rule.
- If the maxTcpReXmitRatioExceeded bit in the previous slapm2PRMonStatus is on, indicating above the low threshold, and the bit in the current slapm2PRMonStatus is off, indicating below the low threshold, this indicates that at the end of this monitor interval this is a falling quantity and the threshold has fallen below its low threshold. Evaluate the slapm2PRMonTcpCurrentTcpReXmit to determine the TCP retransmit ratio over the most recent interval for all outgoing TCP packets affected by this policy rule.
- If the maxAcceptQueueDelayExceeded bit in the previous slapm2PRMonStatus is on, indicating above the low threshold, and the bit in the current slapm2PRMonStatus is off, indicating below the low threshold, this indicates that at the end of this monitor interval this is a falling quantity and the threshold has fallen below its low threshold. Evaluate the slapm2PRMonAcceptQCurrentDelay to determine the smoothed average accept queue delay over the most recent interval for all flows affected by this policy rule.