1-17
User Guide for Cisco Unified Service Monitor
OL-9351-01
Chapter1 Using Cisco Unified Service Monitor
Generating a Cisco1040 Unreachable Trap
You can use the data for further analysis or you can turn archiving off. (Service Monitor does not send
the archived data to other applications.) Tabl e 1-1 lists the format for call metrics data files.
Note Call metrics data files remain on disk for 30 days. Service Monitor deletes them thereafter. If you would
like to save these files, you must back them up using whatever method your normally use to back up your
disk. For more information, see Managing Service Monitor Data, page 2-1.
Generating a Cisco 1040 Unreachable Trap
When a Service Monitor stops receiving keepalives from a Cisco 1040 that is registered to it, the Service
Monitor generates a Cisco 1040 Unreachable SNMP trap. The Service Monitor sends this trap to up to
four recipients. For more information, see Setting Up Service Monitor, page 1-3 and MIBs Used and
SNMP Traps Generated, page A-1.
Note If you configure Operations Manager to receive traps from Service Monitor, the Cisco 1040 Unreachable
trap is displayed on the Alerts and Events monitoring dashboard under the unidentified trap device type.
Table1-1 Service Monitor Archived Call Metrics Data Format
Description Value
Cisco 1040 Sensor ID A Cisco 1040 Sensor ID consists of a letter and a 3-digit
number, for example: A100
Time stamp Date and time
Flag indicating actual or sampled data 0: Actual
1: Sampled
Source device IP address IPv4 address, for example:
172.020.119.043
Destination device IP address IPv4 address, for example:
172.020.119.025
Codec of call data record 2: G711Alaw 64k
6: G722 64k
9: G7231
10: G728
11: G729
Calculated MOS score 2-digit number with an implied decimal point between the
first and second digit
Primary cause of call degradation J: Jitter
P: Packet Loss
Actual packet loss in the previous minute <numeric value>
Actual jitter, in milliseconds, in the
previous minute
<numeric value>