Documentation: Openscape Voice V6 Interface Manual
Documentation: Openscape Voice V6 Interface Manual
OpenScape Voice V6
Interface Manual
Volume 3, SNMP Interface and MIB Description
A31003-H8060-T103-1-7618
History of Changes 0
Contents 0
History of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 Supported and Unsupported MIBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1 Supported MIBS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.1 OpenScape Voice MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.2 SNMPv2 MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2 Unsupported MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Gathering MIBs Using Supported Compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.1 Standard RFC MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.2 Compilation Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.3 SNMP Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.4 Procedures for Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3 Event and Alarm Management MIBS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1 Event Management MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.1 Event Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.1.1 Last Event Sequence Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.1.2 Generic Trap OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.1.3 Event Descriptor Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.1.4 Filtered Event Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.1.5 Event Filter Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2 Alarm Management MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.1 Alarm Object Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.2 Active Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2.2.1 Correlation Trap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4 External Message Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.1 Message Flows Between the NOC and OpenScape Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2 Additional Message Flow Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.3 Managing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.1 Alarm Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.1.1 Alarm Clearance via Correlation Trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.1.2 Alarm Clearance via Trap with Clear Severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.1.3 Manual Alarm Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.2 Alarm Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.2.1 Lost Trap Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.2.2 Periodic Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.3 Alarm Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5 SNMP Trap Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.1 Object Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.1.1 hiQAccountMgmtFaultMgt (221). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.1.2 hiQAucUscFaultMgmt (182) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.1.3 hiQAudFaultMgmt (102) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.1.4 hiQCacFaultMgt (231) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
List of Tables 0
List of Figures 0
1 Introduction
This chapter lists the SNMP Traps generated by the OpenScape Voice system
and received by the OpenScape Voice Assistant. The system generates traps to
alert management stations that failure events have been detected or cleared. The
OpenScape Voice supports the SNMP v2 trap format.
Note: For alarm descriptions and repair notes, refer to the OpenScape Voice
Service Handbook (SHB).
A fault is a condition in the system, detected by the system, where the system
does not behave as specified. All the faults are predefined by the system and can
not be changed.
• Faults with severity minor, major, critical are stored in the alarm database
• Faults with severity warning, minor, major, critical and fault clearance events
are reported with SNMP traps
If, for any reason, forwarding of faults from OpenScape Voice to a surveillance
system (like Assistant) is not possible, the faults can be read from the OSV
database via SNMP, CLI or reading a file with a list of active alarms.
1. Shows how many times an alarm has been triggered since the last acknowledge action.
• SNMPv2-SMI
• SNMPv2-TC
• SNMPv2-CONF
• SNMPv2-MIB
• INET-ADDRESS-MIB
• TCP-MIB
• UDP-MIB
• IANAifType-MIB
• IF-MIB
• IP-MIB
These MIBs are acquired from the compiler. In case they are not provided,
download them from the following directory in the OpenScape Voice system or
any Linux Machine with Net-SNMP installed:
/usr/share/snmp/mibs/
1. SNMPv2-SMI
2. SNMPv2-TC
3. SNMPv2-CONF
4. SNMPv2-MIB
5. INET-ADDRESS-MIB
6. TCP-MIB
7. UDP-MIB
8. IANAifType-MIB
9. IF-MIB
10. IP-MIB
11. RtpAdm.mib
12. RtpAdmEventMgmt.mib
13. RtpAdmAlarmMgmt.mib
14. surpassRtp.mib
15. surpassRtpAdmin.mib
16. surpassRtpProducts.mib
17. hiq8000Admin.mib
18. hiqTrap.mib
19. hiqFeatLic.mib
20. us_srxSip.mib
21. us_srxUce.mib
22. us_srxService.mib
23. us_srxMgcp.mib
Siemens Enterprise Communications does not guarantee that the MIBs provided
will collect, or gather, with other compilers without errors and/or warnings.
• Event Management
• Alarm Management
• Traps (rtpEvtTraps)
rtpEvtTable 1.3.6.1.4.1.4329.2.1.2.1.1.1
Aggregate not-accessible
rtpEvtTableEntry 1.3.6.1.4.1.4329.2.1.2.1.1.1.1
Aggregate not-accessible
Table 4 defines the variable binding object list of every reported event. All are
read only.
The following OID can be used to retrieve the sequence number of the last trap
that was reported to all "generic" destinations configured in the SNMP master
agent. If event filters are being used to route traps to specific management
systems, then the sequence number may be different for each system. Refer to
Section 3.1.1.5, “Event Filter Table”, on page 26 for more information.
rtpEvtLastEventSequenceNumber 1.3.6.1.4.1.4329.2.1.2.1.1.2
Unsigned32 read-only
Used only by RTP, the following OIDs represent the generic trap IDs for alarm
traps generated by RTP that do not have a specific OID configured for a given
Event Set-Event ID.
rtpEvtTrapCritical 1.3.6.1.4.1.4329.2.1.2.1.1.3.1
nonLeaf
rtpEvtTrapMajor 1.3.6.1.4.1.4329.2.1.2.1.1.3.2
nonLeaf
rtpEvtTrapMinor 1.3.6.1.4.1.4329.2.1.2.1.1.3.3
nonLeaf
rtpEvtTrapWarning 1.3.6.1.4.1.4329.2.1.2.1.1.3.4
nonLeaf
rtpEvtTrapInformation 1.3.6.1.4.1.4329.2.1.2.1.1.3.5
nonLeaf
rtpEvtTrapClear 1.3.6.1.4.1.4329.2.1.2.1.1.3.6
nonLeaf
rtpEvtTrapUnknown 1.3.6.1.4.1.4329.2.1.2.1.1.3.7
nonLeaf
Each trap, generic or specific, provides the following object list. Refer to Table 4
for details.
rtpEvtSequenceNumberIndex=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.1
rtpEvtCurrId=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.2
rtpEvtSet=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.3
rtpEvtNum=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.4
rtpEvtSeverity=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.5
rtpEvtEventTime=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.6
rtpEvtReportingObject=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.7
rtpEvtFaultyObject=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.8
rtpEvtEndkey=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.9
rtpEvtFormatText=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.10
rtpEvtParameters=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.11
rtpEvtAlarmType=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.12
rtpEvtShortText=1.3.6.1.4.1.4329.2.1.2.1.1.1.1.13
rtpEvtFilterLastTransId=1.3.6.1.4.1.4329.2.1.2.1.1.9.1.5
The rtpEvtDescriptorTable is a table that contains the severity and alarm type
(summary category) for each Event Set-Event ID. These are configured in the
*.eds files. Refer to Table 5 for details.
rtpEvtDescriptorTable 1.3.6.1.4.1.4329.2.1.2.1.1.5
Aggregate not-accessible
rtpEvtDescriptorTableEntry 1.3.6.1.4.1.4329.2.1.2.1.1.5.1
Aggregate not-accessible
Table 5 defines the variable binding object list of the Event Descriptor Table. All
objects are read only.
The rtpEvtFilteredEventTable is a table that contains details of the alarms that are
sent to management systems configured in the Event Filter Table and is indexed
by the IP address of the management system. Refer to Table 6 for details.
rtpEvtFilteredEventTable 1.3.6.1.4.1.4329.2.1.2.1.1.8
Aggregate not-accessible
rtpEvtFilteredEventEntry 1.3.6.1.4.1.4329.2.1.2.1.1.8.1
Aggregate not-accessible
Table 6 defines the variable binding object list of the Filtered Event Table (Fet).
All objects are read only.
rtpEvtFilterTable 1.3.6.1.4.1.4329.2.1.2.1.1.9
Aggregate not-accessible
rtpEvtFilterEntry 1.3.6.1.4.1.4329.2.1.2.1.1.9.1
Aggregate not-accessible
Table 7 defines the variable binding object list of the Event Filter Table. All objects
are read only, unless noted.
rtpArmAlarmObjectTable 1.3.6.1.4.1.4329.2.1.2.2.1.1
Aggregate not-accessible
rtpArmAlarmObjectEntry 1.3.6.1.4.1.4329.2.1.2.2.1.1.1
Aggregate not-accessible
Table 8 defines the variable binding object list of the Alarm Object Table. All
objects are read only, unless noted.
rtpArmAlarmTable 1.3.6.1.4.1.4329.2.1.2.2.1.2
Aggregate not-accessible
rtpArmAlarmEntry 1.3.6.1.4.1.4329.2.1.2.2.1.2.1
Aggregate not-accessible
Table 9 defines the variable binding object list of the Active Alarm Table. All
objects are read only, unless noted.
rtpArmCorrIdTrap 1.3.6.1.4.1.4329.2.1.2.2.1.3
nonLeaf
Table 10 defines the variable binding object list of the Correlation Trap Table. All
objects are read only.
There are, however, other methods to achieve the same end result, so possible
flows for other surveillance systems are shown in Section 4.2, “Additional
Message Flow Diagrams”, on page 34.
A surveillance system can perform its own alarm correlation by associating clear
traps with related alarm traps. Typically, but not always, the faultyObject trap
variable contains a string that is useful in identifying a specific object or collection
of objects.
In order to clear alarms in the OpenScape Voice system, the sequence depicted
in Figure 3 on page 32 is required.
• Periodic audit
While there is a trap sequence number mechanism provided for lost trap
detection, it cannot be totally relied upon. If the last trap that was sent by the
OpenScape Voice system was lost, the surveillance system does not detect the
lost trap until some point in time that OpenScape Voice sends yet another alarm
trap. To avoid this issue, the surveillance system periodically retrieves the value
of rtpEvtFilterLastTransId for a specified IP address.
Another consideration with this method is that if alarms are manually cleared in
OpenScape Voice via one surveillance system, other surveillance systems
monitoring the same OpenScape Voice will not detect the clearing of that alarm
since no trap is sent as a result.
A simple solution that the NOC uses is to poll for active alarms at startup and
periodically audit the active alarms in OpenScape Voice against the active alarm
list maintained by the NOC. This method is simple and reliable, however, if there
are a large number of alarms present, excessive resources might be used during
the audit, when compared with the lost trap detection, that simply detects a break
in trap sequence numbers. Refer to Figure 7 on page 35.
alarm summary for communication alarms would indicate so. The process of
retrieving alarm summary information is shown in Figure 8 on page 36.
For more information on the RTP event records, refer to Section 3.1.1, “Event
Table”, on page 19.
– The last two numbers of the trap OID are 221.1, where the 221 represents
the rtpEvtSet and the 1 represents the rtpEvtNum.
Note: The largest event set is 255 and the largest event number is 32767. For the
event set, 1 through 175 are reserved for use by RTP; 176 and above are for
applications.
The sections below outline the SNMP trap name, its object identifier (OID),
corresponding alarm name, severity of the trap, as well as the trap name that can
clear the alarm.
Table 20 outlines the SNMP traps that are reported when software processes fail.
It is recommended that the OpenScape Voice surveillance Operations Support
System (OSS) logs these events and informs the craft about an unusual number
of occurrences. For example, more than five in one hour and/or more than one
per day for more than seven days.
Note: In general, warning traps are not stored in the OpenScape Voice alarm
database and, therefore, there is no alarm correlation trap when the faulty
condition is cleared (most likely by a successful process restart).
Failed software processes restart automatically, which are reported with one or
more of the following clearance traps outlined in Table 21.
Table 30 outlines the SNMP traps that are associated with the Threshold
Crossing Alarm (TCA) Faults.
• MGCP
• UCE
• Services
• SNMP V2 MIBs
• IF-MIB II
• IP-MIB II
• TCP - MIB II
• UDP - MIB II
• SNMP - MIB II
• UCD-SNMP-MIB
The following sections outlines the details and information regarding each MIBs’
reporting counters/measurements. The Object Identifier (OID) is provided for
each measurement/count. Refer to Section 5.1, “Object Identifier”, on page 40 for
more information.
These statistics include User Agent (UA) Client, User Agent (UA) Server, and
Proxy. Table 36 outlines the available SNMP SIP performance statistics and
measurement parameters.
This value identifies the count of INVITE messages sent from the SIP Client.
This value identifies the 4xx-6xx for SUBSCRIBE messages received by the
SIP Client. Possible errors are Client, Server, or Global.
This value identifies the 100 TRYING messages received by the SIP Client.
The request has been received and continues to process the request.
This value identifies the INFO messages (DTMF digits) sent by the SIP
Client.
This value identifies the 180 RINGING messages received by the SIP Client.
The request has been received and continues to process.
This value identifies the 200 OK for INFO messages received by the SIP
Client. The INFO was successfully received, understood, and accepted
This value identifies the 200 OK for INVITE messages received by the SIP
Client. The action was successfully received, understood, and accepted.
This value identifies the 301 (Moved Permanently) messages received by the
SIP Client (i.e., redirected).
This value identifies the REFER messages received by the SIP Server.
This value identifies the 302 (Moved Temporarily) messages received by the
SIP Client (i.e., redirected).
This value identifies the 202 ACCEPTED messages sent by the SIP Server.
The REFER was successfully received, understood, and accepted.
This value identifies the Ack for INVITE messages sent by the SIP Client.
Acknowledgement (handshake) is done and a call is going to be setup.
This value identifies the 4xx-6xx for REFER messages sent by the SIP
Server. Possible errors are Client, Server, or Global
This value identifies the Ack For ERROR messages sent by the SIP Client.
Acknowledgement (handshake) is done and a call is going to be setup.
This value identifies the NOTIFY messages received by the SIP Server.
There has been a service session status change.
This value identifies the ERROR messages received by the SIP Client.
Possible errors are Client, Server, or Global.
This value identifies the 200OK for NOTIFY messages sent by the SIP
Server. There has been a service session status change. The action was
successfully received, understood, and accepted.
This value identifies the BYE messages Sent by the SIP Client.
This value identifies the 4xx-6xx for NOTIFY messages sent by the SIP
Server.
This value identifies the BYE messages received by the SIP Server.
This value identifies the SUBSCRIBE messages received by the SIP Server.
This value identifies the CANCEL messages sent by the SIP Client.
This value identifies the 200OK for SUBSCRIBE messages sent by the SIP
Server. The action was successfully received, understood, and accepted.
This value identifies the 200 OK for CANCEL messages received by the SIP
Client. The action was successfully received, understood, and accepted.
This value identifies the 4xx-6xx for SUBSCRIBE messages sent by the SIP
Server.
This value identifies the INFO messages (DTMF digits) received by the SIP
Server.
This value identifies the 200OK for INFO messages Sent by the SIP Server.
This value identifies the 200 OK for REGISTER messages sent by the SIP
Server. The action was successfully received, understood, and accepted.
This value identifies the rest of supported 1xx messages received. The
request has been received and continues to process.
This value identifies the rest of supported 2xx messages received. The action
was successfully received, understood, and accepted.
This value identifies the rest of supported 4xx messages received. Client
Error -- the request contains bad syntax or cannot be fulfilled at this server.
This value identifies the rest of supported 5xx messages received. Server
Error -- the server failed to fulfill an apparently valid request.
This value identifies the rest of supported 6xx messages received. Global
Failure -- the request cannot be fulfilled at any server.
This value identifies the rest of supported 1xx messages sent. The request
has been received and continuing to process.
This value identifies the rest of supported 2xx messages sent. The action
was successfully received, understood, and accepted.
This value identifies the rest of supported 3xx messages sent. Redirection:
further action needs to be taken in order to complete the request.
This value identifies the rest of supported 4xx messages sent. Client Error:
the request contains bad syntax or cannot be fulfilled at this server.
This value identifies the rest of supported 5xx messages sent. Server Error:
the server failed to fulfill an apparently valid request.
This value identifies the rest of supported 6xx messages sent. Global Failure:
the request cannot be fulfilled at any server.
This value identifies the REGISTER messages received by the SIP Server.
This value identifies the 100 TRYING messages sent by the SIP Server. The
request has been received and continues to process.
This value identifies the 180 RINGING messages sent by the SIP Server.
Provisional: request received, continuing to process the request.
This value identifies the 200 OKs for INVITE messages sent by the SIP
Server. The action was successfully received, understood, and accepted.
This value identifies the INVITE messages received by the SIP Server.
This value identifies the ERROR messages Sent by the SIP Server. Possible
errors are Client, Server, or Global.
This value identifies the 200 OKs received for PRACK messages.
The action was successfully received, understood, and accepted.
This value identifies the Ack for ERROR messages received by the SIP
Server. Handshake is complete.
This value identifies the 200 OKs received for UPDATE messages. The
action was successfully received, understood, and accepted.
This value identifies the 200 OKs for BYE messages sent by the SIP Server.
The action was successfully received, understood, and accepted.
This value identifies the 200 OKs sent for PRACK messages. The action was
successfully received, understood, and accepted.
This value identifies the 200 OK for BYE messages received by the SIP
Client.
This value identifies the 200 OKs sent for Update messages. The action was
successfully received, understood, and accepted.
This value identifies the 200 OKs for CANCEL messages sent by the SIP
Server. The action was successfully received, understood, and accepted.
This value identifies the CANCEL messages Received by the SIP Server.
This value identifies the NOTIFY messages sent by the SIP Client. There has
been a service session status change.
This value identifies the 487 (Connection Terminated) messages sent by the
SIP Server. Client Error: the request contains bad syntax or cannot be fulfilled
at this server.
This value identifies the 200 OKs for NOTIFY messages received by the SIP
Client. Service Session Status Change
The NOTIFY was successfully received, understood, and accepted.
This value identifies the ACK for CANCEL messages received by the SIP
Server. Handshake is complete and a call is going to be setup.
This value identifies the 4xx-6xx for NOTIFY messages received by the SIP
Client. Service Session Status Change. Possible errors are Client, Server, or
Global.
This value identifies the REFER messages sent by the SIP Client.
This value identifies the SUBSCRIBE messages sent by the SIP Client.
This value identifies the 202 ACCEPTED messages received by the SIP
Client. The REFER was successfully received, understood, and accepted.
This value identifies the 200 OKs for SUBSCRIBE messages received by the
SIP Client. The SUBSCRIBE was successfully received, understood, and
accepted.
This value identifies the 4xx-6xx for REFER messages received by the SIP
Client. Possible errors are Client, Server, or Global.
This object refers to the counter of total NOTIFY REQUEST messages sent.
This object refers to the counter of total AUDIT ENDPOINT messages sent.
This object refers to the counter of total AUDIT CONNECTION messages sent.
This object refers to the counter of total ENDPOINT CONFIG messages sent.
This object refers to the counter of MTA Transient Errors with ranges from 400-
499.
This object refers to the counter of MGCP return code 500: The transaction
could not be executed, because the endpoint is unknown.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 501:The transaction
could not be executed, because the endpoint is not ready. This includes the
case where the endpoint is out-of-service.
This object refers to the counter of MGCP return code 502: The transaction
could not be executed because the endpoint does not have sufficient resources
(permanent condition).
This object refers to the counter of MGCP return code 503: Wildcard too
complicated.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 504: Unknown or
unsupported command.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 505: Unsupported
RemoteConnectionDescriptor.
This should be used when one or more mandatory parameters or values in the
RemoteConnectionDescriptor is not supported.
This object refers to the counter of MGCP return code 506: Unable to satisfy
both LocalConnectionOptions and RemoteConnectionDescriptor.
This should be used when the LocalConnectionOptions and
RemoteConnectionDescriptor contain one or more mandatory parameters or
values that conflict with each other and/or cannot be supported at the same time
(except for codec negotiation failure - see error code 534).
This object refers to the counter of MGCP return code 508: Unknown or
unsupported quarantine handling.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 509: Error in
RemoteConnectionDescriptor. This should be used when there is a syntax or
semantic error in the RemoteConnectionDescriptor."
This object refers to the counter of MGCP return code 510: The transaction
could not be executed, because some unspecified protocol error was detected.
There has been a provisioning mismatch.
Automatic recovery from such an error will be very difficult; therefore, this code
should only be used as a last resort.
This object refers to the counter of MGCP return code 511:The transaction could
not be executed because the command contained an unrecognized extension.
There has been a provisioning mismatch.
This code should be used for unsupported critical parameter extensions.
This object refers to the counter of MGCP return code 512: The transaction
could not be executed because the gateway is not equipped to detect one of the
requested events.
This object refers to the counter of MGCP return code 513: The transaction
could not be executed, because the gateway is not equipped to generate one of
the requested signals.
This object refers to the counter of MGCP return code 514: The transaction
could not be executed because the gateway cannot send the specified
announcement. There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 515: The transaction
refers to an incorrect connection-id (may have been already deleted).
There has been a state mismatch.
This object refers to the counter of MGCP return code 516: The transaction
refers to an unknown caller-id, or the caller-id supplied is incorrect.
There has been a state mismatch.
This object refers to the counter of MGCP return code 517: Unsupported or
invalid mode. There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 518: Unsupported or
unknown package.
There has been a provisioning mismatch.
It is recommended to include a PackageList parameter with the list of supported
packages in the response, especially if the response is generated by the Call
Agent.
This object refers to the counter of MGCP return code 519: Endpoint does not
have a digit map.
There has been a state mismatch.
This object refers to the counter of MGCP return code 520: The transaction
could not be executed because the endpoint is 'restarting'.
There has been a failure in service.
In most cases this would be a transient error, in which case, error code 405
should be used instead. The error code is only included here for backwards
compatibility.
This object refers to the counter of MGCP return code 521: Endpoint redirected
to another Call Agent.
The associated redirection behavior is only well-defined when this response is
issued for a RestartInProgress command.
This object refers to the counter of MGCP return code 522: No such event or
signal. There has been a provisioning mismatch.
The request referred to an event or signal that is not defined in the relevant
package (which could be the default package).
This object refers to the counter of MGCP return code 523: Unknown action or
illegal combination of actions.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 524: Internal
inconsistency in LocalConnectionOptions.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 525: Unknown extension
in LocalConnectionOptions.
There has been a provisioning mismatch.
This code should be used for unsupported mandatory vendor extensions.
This object refers to the counter of MGCP return code 526: Insufficient
bandwidth.
There has been a provisioning mismatch.
In cases where this is a transient error, error code 404 should be used instead.
This object refers to the counter of MGCP return code 527: Missing
RemoteConnectionDescriptor. Remote Descriptor Error, or State MisMatch
This object refers to the counter of MGCP return code 528: Incompatible
protocol version.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 529: Internal hardware
failure.
There has been a service failure.
This object refers to the counter of MGCP return code 530: CAS signaling
protocol error.
Table 37 MGCP Signaling Manager Performance Counters (Sheet 11 of 14)
This object refers to the counter of MGCP return code 531: Failure of a grouping
of trunks (e.g., facility failure).
There has been a service failure.
This object refers to the counter of MGCP return code 532: Unsupported
value(s) in LocalConnectionOptions.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 533: Response too large.
Likely to occur only in the case of an audit
This object refers to the counter of MGCP return code 534: Codec negotiation
failure.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 535: Packetization period
not supported.
Normally this error should not be generated
This object refers to the counter of MGCP return code 536: Unknown or
unsupported RestartMethod.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 537: Unknown or
unsupported digit map extension.
There has been a provisioning mismatch.
This object refers to the counter of MGCP return code 538: Event/signal
parameter error.
Response valid for NotificationRequest
This object refers to the counter of MGCP return code 539: Invalid or
unsupported command parameter.
There has been a provisioning mismatch.
This code should only be used when the parameter is neither a package nor a
vendor extension parameter.
This object refers to the counter of MGCP return code 540: Per endpoint
connection limit exceeded.
State Mismatch
This object refers to the counter of MGCP return code 541: Invalid or
unsupported LocalConnectionOptions.
There has been a provisioning mismatch.
This code SHOULD only be used when the LocalConnectionOptions is neither
a package nor a vendor extension LocalConnectionOptions.
This object refers to the total number of calls reaching address completion.
This object refers to the total number of abort calls caused by unavailable
resources.
This object refers to the total number of abort calls caused by no route availabe.
This object refers to the total number of abort calls caused by no trunk available.
Table 38 UCE Performance Measurement Parameters (Sheet 2 of 4)
This object refers to the total number of abort calls caused by gateway
resources unavailable.
This object refers to the total number of abort calls caused by codec unavailable.
This object refers to the total number of abort calls caused by authorization
failure.
This object refers to the total number of abort calls because of other misc error.
This object refers to the total number of times a subscriber of the feature
attempts to activate call forwarding. An activation attempt is defined as dialing
the activation code plus a complete legitimate telephone number.
This object refers to the total number of times a subscriber of the feature
attempts to activate call forwarding but dials a non-allowed number.
This object refers to the total number of times call forwarding occurs for the Call
Forwarding Variable Feature.
This object refers to the total number of times call forwarding occurs for the Call
Forwarding Busy feature.
This object refers to the total number of times Call Forwarding occurs for the Call
Forwarding No Reply feature.
This object refers to the total number of times the Call Forwarding Access Code
is dialed.
This object refers to the total number of times the Call Forwarding Feature is
activated to a remote DN.
This object refers to the total number of forwardings that occur due to the Call
Forwarding feature.
This object refers to the total number of forwarding attempts that fail.
This object refers to the total number of times calls are 'offered' to be forwarded
to the RCF remote DN. Before forwarding a call to the RCF remote DN, a check
is made to see if the customer-specified limit of simultaneous calls has been
reached. If this limit has been reached, the calling party shall be given busy tone
from the base switching office.
This object refers to the total number of times calls are forwarded to the RCF
remote DN.
This object refers to the total number of times the calling parties are given busy
tone from the base switching office in response to exceeding the customer-
specified limit of simultaneous calls.
This object refers to the total number of times the Selective Call Forwarding
Screen Editing Service is accessed.
This object refers to the total number of forwardings that occur due to the
Selective Call Forwarding feature.
This object refers to the total number of times the Selective Call Forwarding
feature activates the Remote DN.
This object refers to the total number of times a customer could not activate SCF
due to unavailable resources on the OpenScape Voice system.
This object refers to the total number of times a customer's call is forwarded to
Voice Mail.
This object refers to the total number of times a calling party's directory number
is delivered to a subscriber with the Calling Number Delivery Service.
This object refers to the total number of times a Private Number indication is
delivered to a subscriber with the Calling Number Delivery Service.
This object refers to the total number of times the Calling Number Delivery
(CND) feature is activated by a subscriber with the Usage Sensitive version of
the feature.
This object refers to the total number of times the Calling Number Delivery
feature is deactivated by a subscriber with the Usage Sensitive version of the
feature.
This object refers to the total number of times a calling party's name is delivered
to a subscriber with the Calling Name Delivery Service.
This object refers to the total number of times an Anonymous Name indication
is delivered to a subscriber with the Calling Name Delivery Service.
This object refers to the total number of times an out of area/unavailable name
indication is delivered to a subscriber with the Calling Name Delivery Service.
This object refers to the total number of times a TCAP Name Query is sent to
the SCP.
This object refers to the total number of timeouts that occured while the SRX
was waiting for the response from the SCP for a Calling Name Query.
This object refers to the total number of times the Calling Number Delivery
Blocking feature was activated due to subscriber dialing the Service Access
Code for the feature.
This object refers to the total number of times the Calling Number Delivery
Blocking feature Activation made the DN public.
This object refers to the total number of times the Calling Number Delivery
Blocking feature Activation made the DN private.
This object refers to the total number of times the Calling Name Delivery
Blocking feature was activated due to subscriber dialing the Service Access
Code for the feature.
This object refers to the total number of times the Calling Identity Delivery and
Suppression's (CIDS) Delivery Feature was activated due to subscriber dialing
the Service Access Code for the feature.
This object refers to the total number of times the Calling Identity Delivery and
Suppression's (CIDS) Suppression Feature was activated due to subscriber
dialing the Service Access Code for the feature.
This object refers to the total number of times the ACR feature was activated
due to subscriber dialing the Service Access Code for the feature.
This object refers to the total number of times the ACR feature was deactivated
due to subscriber dialing the Service Access Code for the feature.
This object refers to the total number of times a customer could not activate
ACR due to unavailable resources on the SRX.
This object refers to the total number of times a customer could not deactivate
ACR due to unavailable resources on the SRX.
This object refers to the total number of times a call was routed to the ACR
Denial Announcement.
This object refers to the total number of times the ACR Denial Announcement
facility is unavailable.
This object refers to the total number of times the ACR Activation Confirmation
Announcement facility is unavailable.
This object refers to the total number of times the ACR Deactivation
Confirmation Announcement facility is unavailable.
This object refers to the total number of times Enhanced Anonymous Call
Rejection (EACR) is not activated due to unavailability of resources.
This object refers to the total number of times Enhanced Anonymous Call
Rejection (EACR) is not deactivated because of unavailability of resources.
This object refers to the total number of times the EACR Activation Confirmation
Announcement facility is unavailable.
This object refers to the total number of times the EACR Deactivation
Confirmation Announcement facility is unavailable.
This object refers to the total number of times the EACR feature was activated
due to subscriber dialing the Service Access Code for the feature.
This object refers to the total number of times the EACR feature was deactivated
due to subscriber dialing the Service Access Code for the feature.
This object refers to the total number of times that customers place calls to a
repertory of frequently called numbers by dialing a 1-digit speed calling code.
Eight numbers(2 through 9) can be placed in the list for non-business group
users and six numbers (2 through 7) for Business Group customers.
This object refers to the total number of times that customers place calls to a
repertory of 30 frequently called numbers by dialing the 2-digit speed calling
code (20 through 49).
This object refers to the total number of times that Customer-Changeable Speed
Calling (CCSC) customers successfully dial a change speed calling list access
code and a new telephone number to assign their own speed calling codes
directly and immediately from their own telephone. The CCSC feature is
available for 1-digit and/or 2-digit speed calling list owners.
This object specifies the peg counts of attempts to invoke Screen List Editing as
a result of dialing the access code. The Service is responsible in incrementing
this count.
This object provides overflow counts of the number of customers denied access
to Screen List Editing as a result of unavailable resources. The Service is
responsible in incrementing this count.
This object refers to the total number of hourly peg counts and usage counts
with a usage-scan rate of 1 per 10 seconds for SCA screening list editing and
for attempts to invoke control procedures as a result of dialing an SCA service
access code. These counts should be available per hour on an individual SPCS
basis.
This object refers to the total number of hourly peg counts of unaccepted calls.
These counts should be available per hour on an individual SPCS basis.
This object refers to the total number of hourly peg counts of all calls checked
against the screening list of a customer with SCA active. These counts should
be available per hour on an individual SPCS basis.
This object refers to the total number of calls on which a caller successfully
entered a PIN. These counts should be available hourly on a per-SPCS and a
per-line basis.
This object refers to the total number of calls on which a caller unsuccessfully
attempted PIN entry. These counts should be available hourly on a per-SPCS
and a per-line basis.
This object refers to the total number of overflow counts for the number of
customers denied access to SCA because of unavailable Stored Program
Control Switch (SPCS) resources. These counts should be available on an
individual SPCS basis.
This object refers to the total number of overflow counts for the number of
unaccepted calls. These counts should be available on an individual SPCS
basis.
This object refers to the total number of overflow counts for the SPCS and/or
any circuits used to provide SCA control procedures. These counts should be
available on an individual SPCS basis.
This object refers to the hourly peg counts and usage counts with a usage scan
rate of 1 per 10 seconds for Selective Call Rejection (SCR) screen editing and
for attempts to invoke control procedures as a result of dialing the SCR service
success code.
This object refers to the hourly peg counts of all calls screened for a customer
with Selective Call Rejection (SCR) active.
This object refers to the overflow counts for the number of customers denied
access to Selective Call Rejection (SCR) because of unavailable system
resources.
This object refers to the overflow counts for the number of rejected calls
because of denied access to Selective Call Rejection (SCR).
This object refers to the overflow counts for the system and/or any circuits used
to provide Selective Call Rejection (SCR) control procedures.
This object refers to the number of times the subscriber accesses the service by
dialing the service access code.
This object refers to the number of times a call trace is attempted after a
subscriber accesses the service.
This object refers to the number of call trace records successfully written to file.
This object refers to the number of times that the service cannot be successfully
completed after subscriber access.
This object refers to the number of times the subscriber accesses the service,
but the service cannot proceed due to an invalid or missing calling DN in the
subscriber's incoming memory slot (ie, the calling party number of the last
received call is invalid or unavailable).
This object refers to the number of times the subscribers attempt to use
Malicious Call Trace, but are denied access.
This object refers to the number of times that the subscriber dialed the MCT
access code, but did not proceed with the activation.
This object refers to the number of call trace records successfully written to file
when malicious call trace method 'after a call' is activated. This counter applies
to both ANSI and ITU.
This object refers to the number of call trace records successfully written to file
when malicious call trace method 'during a call' is activated. This counter
applies to both ANSI and ITU.
This object refers to the number of call trace records successfully written to file
when malicious call trace method 'Not-Answered calls' is activated. This counter
applies to both ANSI and ITU.
This object refers to the number of call trace records successfully written to file
when malicious call trace method 'Upon an answer' is activated. This counter
applies to both ANSI and ITU.
This object refers to the number of call trace records successfully written to file
when malicious call trace method 'Upon alerting' is activated. This counter
applies to both ANSI and ITU.
This object refers to the number of times TWC service customers attempt to add
on a thid party. The count indicates the customer involved in a stable talking
connection has flashed and dialed a complete set of digits that are valid for
calling.
This object refers to the number of times successful Three Way Calling is
formed by a customer with TWC service.
This object refers to the number of times ICD service customers attempt to
connect an incomming intercom call.
This object refers to the number of successful times an incomming Intercom Call
is formed by a customer with ICD service.
This object refers to the number of times ICD service customers attempt to
connect an outgoing intercom call.
This object refers to the number of successful times an outgoing Intercom Call
is formed by a customer with ICD service.
This object refers to the number of times Voice Mail service customers trigger
Message Waiting Indication.
This object refers to the number of times Voice Mail service customers trigger
the removal of Message Waiting Indication.
This object refers to the number of times TCAP Message Waiting Indicator
queries are successfully sent.
This object refers to the number of times TCAP Message Waiting Indicator
queries are unsuccessfully sent. .
This object refers to the number of times TCAP Message Waiting Indicator
queries are successfully received.
This object refers to the number of times TCAP Message Waiting Indicator
queries are unsuccessfully received.
This object refers to the number of times TCAP Message Waiting Indicator
queries fail.
This object refers to the number of times the E164 number provided to identify
the receiving user is not a valid number (Operate).
This object refers to the number of times the E164 number provided to identify
the receiving user is not a valid number (Remove).
This object refers to the number of times the resources required to perform
adequately the MWI supplementary service are not available (Operate).
This object refers to the number of times the resources required to perform
adequately the MWI supplementary service are not available (Remove).
This object refers to the number of times the received E164 number identifying
the controlling user is a non authorized number (in case of registration
subscription option applies) or an invalid number (Operate).
This object refers to the number of times the received E164 number identifying
the controlling user is a non authorized number (in case of registration
subscription option applies) or an invalid number (Remove).
This object refers to the number of times the MWI supplementary service has
not been subscribed to by the receiving user (Operate).
This object refers to the number of times the MWI supplementary service has
not been subscribed to by the receiving user (Remove).
This object refers to the number of times indication is not delivered by the
access signaling system (Operate).
This object refers to the number of times indication is not delivered by the
access signaling system (Remove).
This object refers to the number of times the receiving user's network cannot
handle any further controlling users.
This error value is used when the maximum number of activations for the
receiving user has been reached and a further activation has been requested.
This object refers to the number of times an error response indicating that the
Receiving user is not subscribed, is sent by the system in response to a
received MWI Set operation.
This object refers to the number of times an error responce indicating that the
Receiving user is not subscribed, is sent by the system in response to a
received MWI Reset operation.
This object refers to the number of times an error response indicating that
Indication is Not Delivered, is sent by the system in response to a received MWI
Set operation.
This object refers to the number of times an error response indicating that
Indication is Not Delivered, is sent by the system in response to a received MWI
Reset operation.
This object refers to the total number of successful activations of the Do Not
Disturb service.
This object refers to the total number of unsuccessful activations of the Do Not
Disturb service.
This object refers to the total number of successful deactivations of the Do Not
Disturb service.
The average usage within one hour. License Manager will take snapshots of
current usage counter every 5 minutes and get the average of the values during
an hour.
The maximum average usage within one hour, during a 24 hour period.
6.2.1 IF-MIB II
Table 52 describes the IF-MIB II performance statistics and measurement
parameters.
OID - 1.3.6.1.2.1.2.2.1.13
OID - 1.3.6.1.2.1.2.2.1.14
OID - 1.3.6.1.2.1.2.2.1.15
OID - 1.3.6.1.2.1.2.2.1.16
OID - 1.3.6.1.2.1.2.2.1.17
OID - 1.3.6.1.2.1.2.2.1.19
OID - 1.3.6.1.2.1.2.2.1.20
OID - 1.3.6.1.2.1.31.1.1.1.2
OID - 1.3.6.1.2.1.31.1.1.1.3
OID - 1.3.6.1.2.1.31.1.1.1.4
OID - 1.3.6.1.2.1.31.1.1.1.5
OID - 1.3.6.1.2.1.31.1.1.1.6
OID - 1.3.6.1.2.1.31.1.1.1.7
OID - 1.3.6.1.2.1.31.1.1.1.8
OID - 1.3.6.1.2.1.31.1.1.1.9
OID - 1.3.6.1.2.1.31.1.1.1.10
OID - 1.3.6.1.2.1.31.1.1.1.11
OID - 1.3.6.1.2.1.31.1.1.1.12
OID - 1.3.6.1.2.1.31.1.1.1.13
6.2.2 IP-MIB II
Table 53 describes the IP-MIB II performance statistics and measurement
parameters.
OID - 1.3.6.1.2.1.5.29.1.2
OID - 1.3.6.1.2.1.5.29.1.3
OID - 1.3.6.1.2.1.5.29.1.4
OID - 1.3.6.1.2.1.5.29.1.5
OID - 1.3.6.1.2.1.5.30.1.2
OID - 1.3.6.1.2.1.5.30.1.3
OID - 1.3.6.1.2.1.4.31.1.1.3
OID - 1.3.6.1.2.1.4.31.1.1.4
OID - 1.3.6.1.2.1.4.31.1.1.5
OID - 1.3.6.1.2.1.4.31.1.1.6
OID - 1.3.6.1.2.1.4.31.1.1.7
OID - 1.3.6.1.2.1.4.31.1.1.8
OID - 1.3.6.1.2.1.4.31.1.1.9
OID - 1.3.6.1.2.1.4.31.1.1.10
OID - 1.3.6.1.2.1.4.31.1.1.11
OID - 1.3.6.1.2.1.4.31.1.1.12
OID - 1.3.6.1.2.1.4.31.1.1.13
OID - 1.3.6.1.2.1.4.31.1.1.14
OID - 1.3.6.1.2.1.4.31.1.1.15
OID - 1.3.6.1.2.1.4.31.1.1.16
OID - 1.3.6.1.2.1.4.31.1.1.17
OID - 1.3.6.1.2.1.4.31.1.1.18
OID - 1.3.6.1.2.1.4.31.1.1.19
OID - 1.3.6.1.2.1.4.31.1.1.20
OID - 1.3.6.1.2.1.4.31.1.1.21
OID - 1.3.6.1.2.1.4.31.1.1.22
OID - 1.3.6.1.2.1.4.31.1.1.23
OID - 1.3.6.1.2.1.4.31.1.1.24
OID - 1.3.6.1.2.1.4.31.1.1.25
OID - 1.3.6.1.2.1.4.31.1.1.26
OID - 1.3.6.1.2.1.4.31.1.1.27
OID - 1.3.6.1.2.1.4.31.1.1.28
OID - 1.3.6.1.2.1.4.31.1.1.29
OID - 1.3.6.1.2.1.4.31.1.1.30
OID - 1.3.6.1.2.1.4.31.1.1.31
OID - 1.3.6.1.2.1.4.31.1.1.32
OID - 1.3.6.1.2.1.4.31.1.1.33
OID - 1.3.6.1.2.1.4.31.1.1.34
OID - 1.3.6.1.2.1.4.31.1.1.35
OID - 1.3.6.1.2.1.4.31.1.1.36
OID - 1.3.6.1.2.1.4.31.1.1.37
OID - 1.3.6.1.2.1.4.31.1.1.38
OID - 1.3.6.1.2.1.4.31.1.1.39
OID - 1.3.6.1.2.1.4.31.1.1.40
OID - 1.3.6.1.2.1.4.31.1.1.41
OID - 1.3.6.1.2.1.4.31.1.1.42
OID - 1.3.6.1.2.1.4.31.1.1.43
OID - 1.3.6.1.2.1.4.31.1.1.44
OID - 1.3.6.1.2.1.4.31.1.1.45
OID - 1.3.6.1.2.1.4.31.3.1.3
OID - 1.3.6.1.2.1.4.31.3.1.4
OID - 1.3.6.1.2.1.4.31.3.1.5
OID - 1.3.6.1.2.1.4.31.3.1.6
OID - 1.3.6.1.2.1.4.31.3.1.7
OID - 1.3.6.1.2.1.4.31.3.1.8
OID - 1.3.6.1.2.1.4.31.3.1.9
OID - 1.3.6.1.2.1.4.31.3.1.10
OID - 1.3.6.1.2.1.4.31.3.1.11
OID - 1.3.6.1.2.1.4.31.3.1.12
OID - 1.3.6.1.2.1.4.31.3.1.13
OID - 1.3.6.1.2.1.4.31.3.1.14
OID - 1.3.6.1.2.1.4.31.3.1.15
OID - 1.3.6.1.2.1.4.31.3.1.16
OID - 1.3.6.1.2.1.4.31.3.1.17
OID - 1.3.6.1.2.1.4.31.3.1.18
OID - 1.3.6.1.2.1.4.31.3.1.19
OID - 1.3.6.1.2.1.4.31.3.1.20
OID - 1.3.6.1.2.1.4.31.3.1.21
OID - 1.3.6.1.2.1.4.31.3.1.23
OID - 1.3.6.1.2.1.4.31.3.1.24
OID - 1.3.6.1.2.1.4.31.3.1.25
OID - 1.3.6.1.2.1.4.31.3.1.26
OID - 1.3.6.1.2.1.4.31.3.1.27
OID - 1.3.6.1.2.1.4.31.3.1.28
OID - 1.3.6.1.2.1.4.31.3.1.29
OID - 1.3.6.1.2.1.4.31.3.1.30
OID - 1.3.6.1.2.1.4.31.3.1.31
OID - 1.3.6.1.2.1.4.31.3.1.32
OID - 1.3.6.1.2.1.4.31.3.1.33
OID - 1.3.6.1.2.1.4.31.3.1.34
OID - 1.3.6.1.2.1.4.31.3.1.35
OID - 1.3.6.1.2.1.4.31.3.1.36
OID - 1.3.6.1.2.1.4.31.3.1.37
OID - 1.3.6.1.2.1.4.31.3.1.38
OID - 1.3.6.1.2.1.4.31.3.1.39
OID - 1.3.6.1.2.1.4.31.3.1.40
OID - 1.3.6.1.2.1.4.31.3.1.41
OID - 1.3.6.1.2.1.4.31.3.1.42
OID - 1.3.6.1.2.1.4.31.3.1.43
OID - 1.3.6.1.2.1.4.31.3.1.44
OID - 1.3.6.1.2.1.4.31.3.1.45
OID - 1.3.6.1.2.1.6.5
OID - 1.3.6.1.2.1.6.6
OID - 1.3.6.1.2.1.6.7
OID - 1.3.6.1.2.1.6.8
OID - 1.3.6.1.2.1.6.9
OID - 1.3.6.1.2.1.6.10
OID - 1.3.6.1.2.1.6.17
OID - 1.3.6.1.2.1.6.11
OID - 1.3.6.1.2.1.6.18
OID - 1.3.6.1.2.1.6.12
OID - 1.3.6.1.2.1.6.14
OID - 1.3.6.1.2.1.6.15
OID - 1.3.6.1.2.1.7.1
OID - 1.3.6.1.2.1.7.8
OID - 1.3.6.1.2.1.7.2
OID - 1.3.6.1.2.1.7.3
OID - 1.3.6.1.2.1.7.4
OID - 1.3.6.1.2.1.7.9
OID - 1.3.6.1.2.1.11.1
OID - 1.3.6.1.2.1.11.3
OID - 1.3.6.1.2.1.11.4
OID - 1.3.6.1.2.1.11.5
OID - 1.3.6.1.2.1.11.6
OID - 1.3.6.1.2.1.11.31
OID - 1.3.6.1.2.1.11.31
OID - 1.3.6.1.2.1.11.32
6.2.6 UCD-SNMP-MIB
OpenScape Voice Memory, IO and CPU measurements are available via the
UCD-SNMP-MIB and Host-Resources MIB.
Note: Please note that Siemens Enterprise Communications does not control the
SW supporting these MIBs. Some of the information may not be supported by a
particular HW platform.
Note: There is only a single average counter and not one for each CPU. The
number is in clock ticks so the interpreting software at a surveillance OSS will
have to poll and create an average over time. The formula for a percentage is:
Idle CPU = (idle2 - idle1)*100/((idle2 - idle1)+(user2 - user1)+(nice2 -
nice1)+(system2 - system1))
+--systemStats
| +-- ssIndex
| +-- ssErrorName
| +-- ssSwapIn
| +-- ssSwapOut
| +-- ssIOSent
| +-- ssIOReceive
| +-- ssSysInterrupts
| +-- ssSysContext
| +-- ssCpuUser
| +-- ssCpuSystem
| +-- ssCpuIdle
| +-- ssCpuRawUser
| +-- ssCpuRawNice
| +-- ssCpuRawSystem
| +-- ssCpuRawIdle
| +-- ssCpuRawWait
| +-- ssCpuRawKernel
| +-- ssCpuRawInterrupt
| +-- ssIORawSent(
| +-- ssIORawReceived
| +-- ssRawInterrupts
| +-- ssRawContexts
| +-- ssCpuRawSoftIRQ
| +-- ssRawSwapIn
| +-- ssRawSwapOut
|
+--memory
+-- memIndex
+-- memErrorName
+-- memTotalSwap
+-- memAvailSwap
+-- memTotalReal
+-- memAvailReal
+-- memTotalSwapTXT
+-- memAvailSwapTXT
+-- memTotalRealTXT
+-- memAvailRealTXT
+-- memTotalFree
+-- memMinimumSwap
+-- memShared
+-- memBuffer
+-- memCached
+-- memSwapError
+-- memSwapErrorMsg
UCD-SNMP-MIB::memSwapErrorMsg.0 = STRING:
UCD-SNMP-MIB::laIndex.1 = INTEGER: 1
UCD-SNMP-MIB::laIndex.2 = INTEGER: 2
UCD-SNMP-MIB::laIndex.3 = INTEGER: 3
UCD-SNMP-MIB::laNames.1 = STRING: Load-1
UCD-SNMP-MIB::laNames.2 = STRING: Load-5
UCD-SNMP-MIB::laNames.3 = STRING: Load-15
UCD-SNMP-MIB::laLoad.1 = STRING: 13.01
UCD-SNMP-MIB::laLoad.2 = STRING: 13.05
UCD-SNMP-MIB::laLoad.3 = STRING: 13.00
UCD-SNMP-MIB::laConfig.1 = STRING: 12.00
UCD-SNMP-MIB::laConfig.2 = STRING: 12.00
UCD-SNMP-MIB::laConfig.3 = STRING: 12.00
UCD-SNMP-MIB::laLoadInt.1 = INTEGER: 1301
UCD-SNMP-MIB::laLoadInt.2 = INTEGER: 1305
UCD-SNMP-MIB::laLoadInt.3 = INTEGER: 1300
UCD-SNMP-MIB::laLoadFloat.1 = Opaque: Float: 13.010000
UCD-SNMP-MIB::laLoadFloat.2 = Opaque: Float: 13.050000
UCD-SNMP-MIB::laLoadFloat.3 = Opaque: Float: 13.000000
UCD-SNMP-MIB::laErrorFlag.1 = INTEGER: error(1)
UCD-SNMP-MIB::laErrorFlag.2 = INTEGER: error(1)
UCD-SNMP-MIB::laErrorFlag.3 = INTEGER: error(1)
UCD-SNMP-MIB::laErrMessage.1 = STRING: 1 min Load Average too
high (= 13.01)
UCD-SNMP-MIB::laErrMessage.2 = STRING: 5 min Load Average too
high (= 13.05)
UCD-SNMP-MIB::laErrMessage.3 = STRING: 15 min Load Average too
high (= 13.00)
UCD-SNMP-MIB::ssIndex.0 = INTEGER: 1
UCD-SNMP-MIB::ssErrorName.0 = STRING: systemStats
UCD-SNMP-MIB::ssSwapIn.0 = INTEGER: 0 kB
UCD-SNMP-MIB::ssSwapOut.0 = INTEGER: 0 kB
UCD-SNMP-MIB::ssIOSent.0 = INTEGER: 85 blocks/s
UCD-SNMP-MIB::ssIOReceive.0 = INTEGER: 0 blocks/s
UCD-SNMP-MIB::ssSysInterrupts.0 = INTEGER: 326 interrupts/s
UCD-SNMP-MIB::ssSysContext.0 = INTEGER: 2214 switches/s
UCD-SNMP-MIB::ssCpuUser.0 = INTEGER: 5
UCD-SNMP-MIB::ssCpuSystem.0 = INTEGER: 0
UCD-SNMP-MIB::ssCpuIdle.0 = INTEGER: 93
UCD-SNMP-MIB::ssCpuRawUser.0 = Counter32: 9615391
UCD-DISKIO-MIB::diskIOIndex.26 = INTEGER: 26
UCD-DISKIO-MIB::diskIOIndex.27 = INTEGER: 27
UCD-DISKIO-MIB::diskIOIndex.28 = INTEGER: 28
UCD-DISKIO-MIB::diskIOIndex.29 = INTEGER: 29
UCD-DISKIO-MIB::diskIOIndex.30 = INTEGER: 30
UCD-DISKIO-MIB::diskIOIndex.31 = INTEGER: 31
UCD-DISKIO-MIB::diskIOIndex.32 = INTEGER: 32
UCD-DISKIO-MIB::diskIOIndex.33 = INTEGER: 33
UCD-DISKIO-MIB::diskIOIndex.34 = INTEGER: 34
UCD-DISKIO-MIB::diskIOIndex.35 = INTEGER: 35
UCD-DISKIO-MIB::diskIOIndex.36 = INTEGER: 36
UCD-DISKIO-MIB::diskIOIndex.37 = INTEGER: 37
UCD-DISKIO-MIB::diskIOIndex.38 = INTEGER: 38
UCD-DISKIO-MIB::diskIOIndex.39 = INTEGER: 39
UCD-DISKIO-MIB::diskIOIndex.40 = INTEGER: 40
UCD-DISKIO-MIB::diskIOIndex.41 = INTEGER: 41
UCD-DISKIO-MIB::diskIOIndex.42 = INTEGER: 42
UCD-DISKIO-MIB::diskIOIndex.43 = INTEGER: 43
UCD-DISKIO-MIB::diskIOIndex.44 = INTEGER: 44
UCD-DISKIO-MIB::diskIOIndex.45 = INTEGER: 45
UCD-DISKIO-MIB::diskIOIndex.46 = INTEGER: 46
UCD-DISKIO-MIB::diskIODevice.1 = STRING: ram0
UCD-DISKIO-MIB::diskIODevice.2 = STRING: ram1
UCD-DISKIO-MIB::diskIODevice.3 = STRING: ram2
UCD-DISKIO-MIB::diskIODevice.4 = STRING: ram3
UCD-DISKIO-MIB::diskIODevice.5 = STRING: ram4
UCD-DISKIO-MIB::diskIODevice.6 = STRING: ram5
UCD-DISKIO-MIB::diskIODevice.7 = STRING: ram6
UCD-DISKIO-MIB::diskIODevice.8 = STRING: ram7
UCD-DISKIO-MIB::diskIODevice.9 = STRING: ram8
UCD-DISKIO-MIB::diskIODevice.10 = STRING: ram9
UCD-DISKIO-MIB::diskIODevice.11 = STRING: ram10
UCD-DISKIO-MIB::diskIODevice.12 = STRING: ram11
UCD-DISKIO-MIB::diskIODevice.13 = STRING: ram12
UCD-DISKIO-MIB::diskIODevice.14 = STRING: ram13
UCD-DISKIO-MIB::diskIODevice.15 = STRING: ram14
UCD-DISKIO-MIB::diskIODevice.16 = STRING: ram15
UCD-DISKIO-MIB::diskIODevice.17 = STRING: sr0
UCD-DISKIO-MIB::diskIODevice.18 = STRING: sda
UCD-DISKIO-MIB::diskIONRead.12 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.13 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.14 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.15 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.16 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.17 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.18 = Counter32: 1992004096
UCD-DISKIO-MIB::diskIONRead.19 = Counter32: 206336
UCD-DISKIO-MIB::diskIONRead.20 = Counter32: 910244864
UCD-DISKIO-MIB::diskIONRead.21 = Counter32: 1572864
UCD-DISKIO-MIB::diskIONRead.22 = Counter32: 3072
UCD-DISKIO-MIB::diskIONRead.23 = Counter32: 414607872
UCD-DISKIO-MIB::diskIONRead.24 = Counter32: 1318912
UCD-DISKIO-MIB::diskIONRead.25 = Counter32: 12714496
UCD-DISKIO-MIB::diskIONRead.26 = Counter32: 4743680
UCD-DISKIO-MIB::diskIONRead.27 = Counter32: 159392256
UCD-DISKIO-MIB::diskIONRead.28 = Counter32: 3940864
UCD-DISKIO-MIB::diskIONRead.29 = Counter32: 3342848
UCD-DISKIO-MIB::diskIONRead.30 = Counter32: 283406848
UCD-DISKIO-MIB::diskIONRead.31 = Counter32: 1110528
UCD-DISKIO-MIB::diskIONRead.32 = Counter32: 2757120
UCD-DISKIO-MIB::diskIONRead.33 = Counter32: 192178688
UCD-DISKIO-MIB::diskIONRead.34 = Counter32: 499712
UCD-DISKIO-MIB::diskIONRead.35 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.36 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.37 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.38 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.39 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.40 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.41 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.42 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.43 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.44 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.45 = Counter32: 0
UCD-DISKIO-MIB::diskIONRead.46 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.1 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.2 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.3 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.4 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.5 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.6 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.7 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.8 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.9 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.10 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.11 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.12 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.13 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.14 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.15 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.16 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.17 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.18 = Counter32: 2247980032
UCD-DISKIO-MIB::diskIONWritten.19 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.20 = Counter32: 4134790144
UCD-DISKIO-MIB::diskIONWritten.21 = Counter32: 131072
UCD-DISKIO-MIB::diskIONWritten.22 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.23 = Counter32: 1793713152
UCD-DISKIO-MIB::diskIONWritten.24 = Counter32: 3458048
UCD-DISKIO-MIB::diskIONWritten.25 = Counter32: 87937024
UCD-DISKIO-MIB::diskIONWritten.26 = Counter32: 798013440
UCD-DISKIO-MIB::diskIONWritten.27 = Counter32: 792976384
UCD-DISKIO-MIB::diskIONWritten.28 = Counter32: 34331136
UCD-DISKIO-MIB::diskIONWritten.29 = Counter32: 133648896
UCD-DISKIO-MIB::diskIONWritten.30 = Counter32: 3508507648
UCD-DISKIO-MIB::diskIONWritten.31 = Counter32: 202240
UCD-DISKIO-MIB::diskIONWritten.32 = Counter32: 305664
UCD-DISKIO-MIB::diskIONWritten.33 = Counter32: 1417307136
UCD-DISKIO-MIB::diskIONWritten.34 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.35 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.36 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.37 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.38 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.39 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.40 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.41 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.42 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.43 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.44 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.45 = Counter32: 0
UCD-DISKIO-MIB::diskIONWritten.46 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.1 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.2 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.3 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.4 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.5 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.6 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.7 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.8 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.9 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.10 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.11 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.12 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.13 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.14 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.15 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.16 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.17 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.18 = Counter32: 95442
UCD-DISKIO-MIB::diskIOReads.19 = Counter32: 214
UCD-DISKIO-MIB::diskIOReads.20 = Counter32: 63964
UCD-DISKIO-MIB::diskIOReads.21 = Counter32: 1396
UCD-DISKIO-MIB::diskIOReads.22 = Counter32: 3
UCD-DISKIO-MIB::diskIOReads.23 = Counter32: 24159
UCD-DISKIO-MIB::diskIOReads.24 = Counter32: 712
UCD-DISKIO-MIB::diskIOReads.25 = Counter32: 6151
UCD-DISKIO-MIB::diskIOReads.26 = Counter32: 8740
UCD-DISKIO-MIB::diskIOReads.27 = Counter32: 25357
UCD-DISKIO-MIB::diskIOReads.28 = Counter32: 6413
UCD-DISKIO-MIB::diskIOReads.29 = Counter32: 5808
UCD-DISKIO-MIB::diskIOReads.30 = Counter32: 41102
UCD-DISKIO-MIB::diskIOReads.31 = Counter32: 1756
UCD-DISKIO-MIB::diskIOReads.32 = Counter32: 4853
UCD-DISKIO-MIB::diskIOReads.33 = Counter32: 78431
UCD-DISKIO-MIB::diskIOReads.34 = Counter32: 45
UCD-DISKIO-MIB::diskIOReads.35 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.36 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.37 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.38 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.39 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.40 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.41 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.42 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.43 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.44 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.45 = Counter32: 0
UCD-DISKIO-MIB::diskIOReads.46 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.1 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.2 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.3 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.4 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.5 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.6 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.7 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.8 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.9 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.10 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.11 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.12 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.13 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.14 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.15 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.16 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.17 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.18 = Counter32: 2747399
UCD-DISKIO-MIB::diskIOWrites.19 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.20 = Counter32: 3106950
UCD-DISKIO-MIB::diskIOWrites.21 = Counter32: 68
UCD-DISKIO-MIB::diskIOWrites.22 = Counter32: 0
UCD-DISKIO-MIB::diskIOWrites.23 = Counter32: 439607
UCD-DISKIO-MIB::diskIOWrites.24 = Counter32: 869
UCD-DISKIO-MIB::diskIOWrites.25 = Counter32: 21672
UCD-DISKIO-MIB::diskIOWrites.26 = Counter32: 195202
UCD-DISKIO-MIB::diskIOWrites.27 = Counter32: 1242466
UCD-DISKIO-MIB::diskIOWrites.28 = Counter32: 9723
UCD-DISKIO-MIB::diskIOWrites.29 = Counter32: 32770
This chapter assumes the user knows how to use and access the RTP CLI. For
information on either of these topics, refer to the OpenScape Voice Configuration
Manual: Volume 3, Configuration and Administration Using CLI Application-level
Management book.
1. From the Main Menu (shown below), at the Selection prompt, enter the
following menu selection: 2 (Fault Management).
Main Menu:
Configuration Management.......................1
Fault Management...............................2
Performance Management.........................3
Security Management............................4
System Management..............................5
Application-level Management...................6
Open Logfile............................93
Show Callback Output....................94
Wait for Callbacks......................95
Change Password.........................96
New Login...............................97
Expert Mode.............................98
Exit....................................99
Selection: 2
2. From the Fault Management (shown below), at the Selection prompt, enter
the following menu selection: 1 (Events).
Fault Management:
Events.........................................1
Alarms.........................................2
Trace..........................................3
Audit..........................................4
Recovery.......................................5
Return..................................99
Selection: 1
3. From the Events menu (shown below), at the Selection prompt, enter the
following menu selection: 14 (createSnmpEventFilter).
Events (methods):
registerForEvents..............................1
unregisterForEvents............................2
reRegisterForEvents............................3
recoverEvents..................................4
getEventSets...................................5
getEventBasicDescriptions......................6
getFullEventDescription........................7
modifyEventParameters..........................8
getEventEscalationFilters......................9
addEventEscalationFilter......................10
removeEventEscalationFilter...................11
removeEvents..................................12
getLatestEventSequenceNumber..................13
createSnmpEventFilter.........................14
modifySnmpEventFilter.........................15
removeSnmpEventFilter.........................16
getSnmpEventFilters...........................17
getCriticalEventDescriptions..................18
addCriticalEvent..............................19
removeCriticalEvent...........................20
ipAddr:
severities[0] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 1
severities[1] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 2
8. The following is displayed; enter 3.
severities[2] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 3
9. The following is displayed; enter 4.
severities[3] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 4
severities[3] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 6
11. The following is displayed; press Enter.
severities[3] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>:
snmpVersion <EVT_SNMP_TRAP_V1: 1,
EVT_SNMP_TRAP_V2c: 2,
EVT_SNMP_TRAP_V3: 3>: 2
1. From the Main Menu (shown below), at the Selection prompt, enter the
following menu selection: 2 (Fault Management).
Main Menu:
Configuration Management.......................1
Fault Management...............................2
Performance Management.........................3
Security Management............................4
System Management..............................5
Application-level Management...................6
Open Logfile............................93
Show Callback Output....................94
Wait for Callbacks......................95
Change Password.........................96
New Login...............................97
Expert Mode.............................98
Exit....................................99
Selection: 2
2. From the Fault Management (shown below), at the Selection prompt, enter
the following menu selection: 1 (Events).
Fault Management:
Events.........................................1
Alarms.........................................2
Trace..........................................3
Audit..........................................4
Recovery.......................................5
Return..................................99
Selection: 1
3. From the Events menu (shown below), at the Selection prompt, enter the
following menu selection: 15 (modifySnmpEventFilter).
Events (methods):
registerForEvents..............................1
unregisterForEvents............................2
reRegisterForEvents............................3
recoverEvents..................................4
getEventSets...................................5
getEventBasicDescriptions......................6
getFullEventDescription........................7
modifyEventParameters..........................8
getEventEscalationFilters......................9
addEventEscalationFilter......................10
removeEventEscalationFilter...................11
removeEvents..................................12
getLatestEventSequenceNumber..................13
createSnmpEventFilter.........................14
modifySnmpEventFilter.........................15
removeSnmpEventFilter.........................16
getSnmpEventFilters...........................17
getCriticalEventDescriptions..................18
addCriticalEvent..............................19
removeCriticalEvent...........................20
ipAddr:
severities[0] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 1
severities[1] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 2
8. The following is displayed; enter 3.
severities[2] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 3
9. The following is displayed; enter 4.
severities[3] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 4
severities[3] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>: 6
11. The following is displayed; press Enter.
severities[3] <EVT_SEV_CRITICAL: 1,
EVT_SEV_MAJOR: 2,
EVT_SEV_MINOR: 3,
EVT_SEV_WARNING: 4,
EVT_SEV_INFORMATION: 5,
EVT_SEV_CLEAR: 6,
end: <Return>>:
snmpVersion <EVT_SNMP_TRAP_V1: 1,
EVT_SNMP_TRAP_V2c: 2,
EVT_SNMP_TRAP_V3: 3>: 2
trapDestPort <(1..32767)> (default: -1):
1. From the Main Menu (shown below), at the Selection prompt, enter the
following menu selection: 2 (Fault Management).
Main Menu:
Configuration Management.......................1
Fault Management...............................2
Performance Management.........................3
Security Management............................4
System Management..............................5
Application-level Management...................6
Open Logfile............................93
Show Callback Output....................94
Wait for Callbacks......................95
Change Password.........................96
New Login...............................97
Expert Mode.............................98
Exit....................................99
Selection: 2
2. From the Fault Management (shown below), at the Selection prompt, enter
the following menu selection: 1 (Events).
Fault Management:
Events.........................................1
Alarms.........................................2
Trace..........................................3
Audit..........................................4
Recovery.......................................5
Return..................................99
Selection: 1
3. From the Events menu (shown below), at the Selection prompt, enter the
following menu selection: 16 (removeSnmpEventFilter).
Events (methods):
registerForEvents..............................1
unregisterForEvents............................2
reRegisterForEvents............................3
recoverEvents..................................4
getEventSets...................................5
getEventBasicDescriptions......................6
getFullEventDescription........................7
modifyEventParameters..........................8
getEventEscalationFilters......................9
addEventEscalationFilter......................10
removeEventEscalationFilter...................11
removeEvents..................................12
getLatestEventSequenceNumber..................13
createSnmpEventFilter.........................14
modifySnmpEventFilter.........................15
removeSnmpEventFilter.........................16
getSnmpEventFilters...........................17
getCriticalEventDescriptions..................18
addCriticalEvent..............................19
removeCriticalEvent...........................20
ipAddr: 172.20.1.100
1. From the Main Menu (shown below), at the Selection prompt, enter the
following menu selection: 2 (Fault Management).
Main Menu:
Configuration Management.......................1
Fault Management...............................2
Performance Management.........................3
Security Management............................4
System Management..............................5
Application-level Management...................6
Open Logfile............................93
Show Callback Output....................94
Wait for Callbacks......................95
Change Password.........................96
New Login...............................97
Expert Mode.............................98
Exit....................................99
Selection: 2
2. From the Fault Management (shown below), at the Selection prompt, enter
the following menu selection: 1 (Events).
Fault Management:
Events.........................................1
Alarms.........................................2
Trace..........................................3
Audit..........................................4
Recovery.......................................5
Return..................................99
Selection: 1
3. From the Events menu (shown below), at the Selection prompt, enter the
following menu selection: 17 (getSnmpEventFilter).
Events (methods):
registerForEvents..............................1
unregisterForEvents............................2
reRegisterForEvents............................3
recoverEvents..................................4
getEventSets...................................5
getEventBasicDescriptions......................6
getFullEventDescription........................7
modifyEventParameters..........................8
getEventEscalationFilters......................9
addEventEscalationFilter......................10
removeEventEscalationFilter...................11
removeEvents..................................12
getLatestEventSequenceNumber..................13
createSnmpEventFilter.........................14
modifySnmpEventFilter.........................15
removeSnmpEventFilter.........................16
getSnmpEventFilters...........................17
getCriticalEventDescriptions..................18
addCriticalEvent..............................19
removeCriticalEvent...........................20
Ok.
{
(de.siemens.icp.rtp.eventMgmt.SnmpEventFilterInfo@1cffeb4)
ipAddr: 10.22.100.100
eventSets:
severityLevels: 1 2 3 4 6
snmpVersion: 2
lastTransId: 0
trapDestPort: -1
}
{
(de.siemens.icp.rtp.eventMgmt.SnmpEventFilterInfo@5b0668)
ipAddr: 10.22.100.105
eventSets:
severityLevels: 1 2 3 4 6
snmpVersion: 2
lastTransId: 0
trapDestPort: 162
}
{ (de.siemens.icp.rtp.eventMgmt.SnmpEventFilterInfo@1d5a0)
ipAddr: 10.22.140.240
eventSets:
severityLevels: 1 2 3 4 6
snmpVersion: 2
lastTransId: 0
trapDestPort: 162
}
{
(de.siemens.icp.rtp.eventMgmt.SnmpEventFilterInfo@701a27)
ipAddr: 10.22.21.40
eventSets:
severityLevels: 1 2 3 4 6
snmpVersion: 2
lastTransId: 0
trapDestPort: 162
}
7.5 Troubleshooting
Attention: For help with expert mode commands or RTP CLI Application-level
commands, refer to the OpenScape Voice Configuration Manual: Volume 3,
Config and Admin Using CLI Application-level Mgmt book.
1. Login as root and type the following commands to test the alarm.
su - srx
../SendAlarm 217 1 fo1 fo2 fo3 "Test Alarm"
A trap is sent to the configured trap destinations. Additionally, the active alarm is
shown in the active alarm table and can be verified by displaying the alarms via
the RTP CLI. In this particular example, there would be a critical alarm with the
short text:
"FaultyObject = fo1/fo2/fo3: Loss of communication".
2. Clear the alarm via the command:
SendAlarm 217 4 fo1 fo2 fo3 "Test Alarm"
3. A clear trap and correlation trap must be sent to the trap destinations.
Attention: Checking the node.cfg file is generally used before system installation
to set up the trap destinations.
Index Z hiQAudFileSystemBelowMin2Trap 42
hiQAudFileSystemBelowMin3Trap 42
hiQAudFileSystemBelowMin4Trap 42
hiQAuditStartingTrap 42
hiQAudOSProcInstanceNotRunningTrap 45
B hiQAudOSProcNotRunningTrap 45
backward compatibility 14 hiQAudProcessNotRunningMajorTrap 45
hiQAudProcessNotRunningMinorTrap 45
C hiQAudProcessRunningTrap 52
change an SNMP trap destination 155 hiQAudProcHeapAboveCritThld 43
compile order 17 hiQAudProcHeapAboveMajorThld 43
create an SNMP trap destination 152 hiQAudProcHeapAboveMinorThld 44
hiQAudProcHeapSizeChanged1Trap 44
D hiQAudProcHeapSizeChanged2Trap 44
delete an SNMP trap destination 158 hiQAudProcHeapSizeChanged3Trap 44
display an SNMP trap destination 160 hiQAudProcHeapSizeChanged4Trap 44
E hiQAudProcHeapSizeOkTrap 44
hiQAudProcNotRunningCriticalTrap 45
Emmanate 16
hiQAudProcRunningTrap 45
G hiQAudProcStackAboveCritThld 44
get an SNMP trap destination 160 hiQAudProcStackAboveMajorThld 44
hiQAudProcStackAboveMinorThld 44
H hiQAudProcStackSizeChanged1Trap 44
hiPathSIPCounterAboveHighThld 54 hiQAudProcStackSizeChanged2Trap 44
hiPathSIPCounterAboveLowThld 54 hiQAudProcStackSizeChanged3Trap 44
hiPathSIPCounterBelowThld 54 hiQAudProcStackSizeChanged4Trap 44
hiQAccountDeletedTrap 41 hiQAudProcStackSizeOkTrap 45
hiQAccountDisabledTrap 41 hiQAudSemUtilAboveCritThld 46
hiQAccountInactiveTrap 41 hiQAudSemUtilAboveMajorThld 46
hiQAucUscFileSeqNumberErrorTrap 42 hiQAudSemUtilAboveMinorThld 46
hiQAucUscLocalSecStorageOk 42 hiQAudSemUtilBelowThreshTrap 46
hiQAucUscPriStorNotPossibleTrap 41 hiQAudSemUtilChangedTrap 46
hiQAucUscPriStorOKTrap 41 hiQAudSemUtilTrap 46
hiQAucUscSecStorNotPossibleTrap 42 hiQAudShMemUtilBelowThreshTrap 46
hiQAucUscServerTxCdrTrap 41 hiQAudShMemUtilChangedTrap 46
hiQAudAvailDiskSpBelowCritThld 42 hiQAudShMemUtilTooAboveCritThld 46
hiQAudAvailDiskSpBelowMajorThld 42 hiQAudShMemUtilTooAboveMajorThld 46
hiQAudAvailDiskSpBelowMinorThld 42 hiQAudShMemUtilTooAboveMinorThld 46
hiQAudCPUUtilAboveCritThld 45 hiQAudShMemUtilTrap 46
hiQAudCPUUtilAboveMajorThld 45 hiQAudSwapSpaceAboveCritThld 45
hiQAudCPUUtilAboveMinorThld 45 hiQAudSwapSpaceAboveMajorThld 45
hiQAudCPUUtilBelowThreshTrap 45 hiQAudSwapSpaceAboveMinorThld 45
hiQAudCPUUtilChangedTrap 45 hiQAudSwapUtilBelowThreshTrap 46
hiQAudCPUUtilTrap 45 hiQAudSwapUtilChangedTrap 46
hiQAudFileGroupSizeChanged1Trap 43 hiQAudSwapUtilTrap 46
hiQAudFileGroupSizeChanged2Trap 43 hiQCacHighThreshTrap 47
hiQAudFileGroupSizeChanged3Trap 43 hiQCacLowThreshTrap 47
hiQAudFileGroupSizeChanged4Trap 43 hiQCritOperationModeStateChange 49
hiQAudFileGrpAboveCritThld 43 hiqFeatLicTrunkAverageUsage 119
hiQAudFileGrpBelowThreshTrap 43 hiqFeatLicTrunkMaxAverageUsage 119
hiQAudFileSystemAboveMinTrap 43 hiQFileGrpAboveMajorThld 43
hiQAudFileSystemBelowMin1Trap 42 hiQFileGrpAboveMinorThld 43
hiQGlobalCommsEstablishedTrap 48 hiQNmProcessRestartShortTimeTrap 51
hiQGlobalCommsOperational 49 hiQNmQueueAllocErrorTrap 51
hiQGlobalCriticalLossOfCommsTrap 48 hiQNmQueueCorruptedTrap 51
hiQGlobalDegradedCommsTrap 49 hiQNmResizeGlobalProcTblTrap 51
hiQGlobalFuncAvailTrap 48 hiQNormalOperationMode 49
hiQGlobalFuncUnavailTrap 48 hiQOperationModeStateChange 49
hiQGlobalMajorLossOfCommsTrap 48 hiQOvlCongLevelChangeTrap 53
hiQGlobalMinorLossOfCommsTrap 48 hiQOvlCongLevelToCL0Trap 53
hiQGlobalMsgQueueAboveHighThld 48 hiQOvlCongLevelToCL1Trap 53
hiQGlobalMsgQueueAboveLowThld 49 hiQOvlCongLevelToCL2Trap 53
hiQGlobalMsgQueueAboveMedThld 48 hiQOvlCongLevelToCL3Trap 53
hiQGlobalMsgQueueBelowThld 49 hiQResourceHIghLimitExceeded 49
hiQGlobalProcAbnormalTermTrap 48 hiQResourceMediumLimitExceeded 49
hiQGlobalProcAliasGrpAvail 48 hiQSbcAlarmTrap 53
hiQGlobalProcessAliasGrpUnavail 48 hiQSbcClearTrap 53
hiQGlobalProcessInitActiveTrap 48, 52 hiQSbcSevereAlarmTrap 53
hiQGlobalProcessPartialInitFailTrap 48 hiQSbcTrap 53
hiQGlobalProcSevereInitFailTrap 48 hiQSbcVerySevereAlarmTrap 53
hiQGlobalResourceExceedLimitTrap 48 hiQSecurityFirewallTrigClearTrap 54
hiQGlobalResourceWithinLimitTrap 48 hiQSecurityFirewallTrigTrap 54
hiQGlobalSevereDegradedCommsTrap 49 hiQSevereHardwareTrap 49
hiQGlobalVerySevereDegradedComms 49 hiQSmdiREcvIPAddrPortError 62
hiQHardwareFailureTrap 49 hiQSmdiRecvIPAddrPortOk 62
hiQHardwareInServiceTrap 50 hiQSnmRebootForSubsystemTrap 55
hiQImportantFuncUnavailTrap 48 hiQSnmRtpNodeDownTrap 55
hiQLicenseCountMismatchTrap 50 hiQSnmRtpNodeDownWasUpTrap 55
hiQLicenseCountOkTrap 50 hiQSnmRtpNodeUpTrap 55
hiQLicenseCountSyncTrap 50 hiQSnmRtpNodeUpWasDownTrap 55
hiQLicenseRestoreTrap 50 hiQSnmRtpRestartforSubsystemTrap 54
hiQLicenseSessionCountOkTrap 50 hiQSnmSpecialActScrExecTrap 55
hiQLicenseSessionsTrap 50 hiQSnmSpecialActScrSuccessTrap 55
hiQLicensesExceededTrap 50 hiQSnmStartupFailedTrap 55
hiQMajorOperationModeStateChange 49 hiQSnmStartupSuccessTrap 55
hiQMinorOperationModeStateChange 49 hiQSnmSubsysAdmInterventionTrap 54
hiQNmAliasMembersExceededTrap 51 hiQSnmSubsysAlreadyRunningTrap 54
hiQNmAliasTableLenExceededTrap 51 hiQSnmSubsysRestartSuccessTrap 55
hiQNmDbMaxProcGrpExceededTrap 50 hiQSnmSubsystemStartErrorTrap 54
hiQNmDbTableNotClosedTrap 51 hiQSnmSystemSwitchOffTrap 55
hiQNmDbTableNotOpenedTrap 51 hiQSolidBackupFailedTrap 57
hiQNmDbUnreachable1Trap 50 hiQSolidBothHSBDbPrimaryTrap 57
hiQNmDbUnreachable2Trap 51 hiQSolidCreateNewDbFailedTrap 56
hiQNmDiagnosticErrorTrap 51 hiQSolidDatabaseStartedTrap 56
hiQNmNodeDownMsgErrorTrap 51 hiQSolidDbBrokenCopyTrap 57
hiQNmNodeMgrSignalRestartTrap 51 hiQSolidDbConvertedTrap 56
hiQNmNodeMgrStartingTrap 51, 52 hiQSolidDbDoesNotExistsTrap 56
hiQNmNodeShutdownTrap 51 hiQSolidDbIndexErrorTrap 56
hiQNmProcessCoreCreatedTrap 51 hiQSolidDbIndexTestSuccessTrap 56
hiQNmProcessExecvErrorTrap 51 hiQSolidDbOpenFailureTrap 56
hiQNmProcessExitedwithCodeTrap 51, 52 hiQSolidDbOpeningProblemTrap 57
hiQNmProcessHealthChkTimeoutTrap 51 hiQSolidDbServerCorruptTrap 57
hiQNmProcessInitCompleteTrap 50, 52 hiQSolidDbTstConnectFailureTrap 56
hiQNmProcessReadyTimeoutTrap 51 hiQSolidDbTstOpenFailureTrap 56
hiQSolidFatalErrSrvNotStartTrap 56 hiQTcaL4ProcessingTrap 59
hiQSolidFatalErrSrvShutdownTrap 56 hiQTcaL4SecurityTrap 59
hiQSolidFlowEngineIntErrorTrap 56 hiQTcaL4ServiceTrap 59
hiQSolidHSBSwitchPrimErrTrap 57 hiQTestCallGeneratorNotOkTrap 60
hiQSolidHSBSwitchSecErrTrap 57 hiQTestCallGeneratorOkTrap 60
hiQSolidLocalDbServerCorruptTrap 57 hiQTestCallGeneratorProvErrTrap 60
hiQSolidNewConnsAllowedTrap 56 hiQTestCallGenNotOkNodeRestart 60
hiQSolidNewDbNotCreatedTrap 56 hiQTestCallGenNotOkProcRestart 60
hiQSolidNoNewConnsAllowedTrap 56 hiQTestCallGenOverloadDetTrap 60
hiQSolidOldDbVersionTrap 56 hiQTicCopyToTicketPoolFailed 57
hiQSolidServerStartFailedTrap 56 hiQTicDiskFullTicketPoolFailed 57
hiQSolidShutdownTrap 56 hiQTicPoolDiskDevNotAccessible 57
hiQSolidStartedHSBPrimaryTrap 57 hiQUCEServicesRegisteringTrap 60
hiQSolidStartedHSBSecondaryTrap 57 hiQUCEServicesRegistrationFailedTrap 60
hiQSolidTableConvertedTrap 57 hiQVeryImportantFuncUnavailTrap 48
hiQSolidTooManyClientsTrap 56 hiQVerySevereHardwareFailureTrap 49
hiQSubMgmtRemoveResourceError 55
hiQSubMgmtRemoveResourceSuccess 55 I
hiQTcaClearedTrap 60 icmpMsgStatsInPkts 124
hiQTcaL1CommunicationTrap 58 icmpMsgStatsOutPkts 124
hiQTcaL1DatabaseTrap 59 icmpStatsInErrors 123
hiQTcaL1EnvironmentTrap 58 icmpStatsInMsgs 123
hiQTcaL1EquipmentTrap 58 icmpStatsOutErrors 124
hiQTcaL1IndicationTrap 59 icmpStatsOutMsgs 123
hiQTcaL1MibTrap 59 ifHCInBroadcastPkts 122
hiQTcaL1ProcessingTrap 58 ifHCInMulticastPkts 122
hiQTcaL1SecurityTrap 59 ifHCInOctets 122
hiQTcaL1ServiceTrap 58 ifHCInUcastPkts 122
hiQTcaL2CommunicationTrap 58 ifHCOutBroadcastPkts 123
hiQTcaL2DatabaseTrap 59 ifHCOutMulticastPkts 123
hiQTcaL2EnvironmentTrap 58 ifHCOutOctets 122
hiQTcaL2EquipmentTrap 58 ifHCOutUcastPkts 123
hiQTcaL2IndicationTrap 59 ifInBroadcastPkts 121
hiQTcaL2MibTrap 59 ifInDiscards 120
hiQTcaL2ProcessingTrap 58 ifInErrors 120
hiQTcaL2SecurityTrap 59 ifInMulticastPkts 121
hiQTcaL2ServiceTrap 58 ifInOctets 120
hiQTcaL3CommunicationTrap 58 ifInUcastPkts 120
hiQTcaL3DatabaseTrap 59 ifInUnknownProtos 120
hiQTcaL3EnvironmentTrap 58 ifOperStatus 120
hiQTcaL3EquipmentTrap 58 ifOutBroadcastPkts 122
hiQTcaL3IndicationTrap 59 ifOutDiscards 121
hiQTcaL3MibTrap 59 ifOutErrors 121
hiQTcaL3ProcessingCriticalTrap 58 ifOutMulticastPkts 122
hiQTcaL3SecurityTrap 59 ifOutOctets 121
hiQTcaL3ServiceTrap 58 ifOutUcastPkts 121
hiQTcaL4CommunicationTrap 59 ipIfStatsHCInBcastPkts 135
hiQTcaL4DatabaseTrap 59 ipIfStatsHCInDelivers 132
hiQTcaL4EnvironmentTrap 59 ipIfStatsHCInForwDatagrams 131
hiQTcaL4EquipmentTrap 59 ipIfStatsHCInMcastOctets 135
hiQTcaL4IndicationTrap 59 ipIfStatsHCInMcastPkts 134
hiQTcaL4MibTrap 59 ipIfStatsHCInOctets 130
69 usSrxSipPerfUASSnt4xx6xxRefer 66
usSrxSipPerf2xxMsgRcvByClient 69 usSrxSipPerfUASSnt4xx6xxSubs 68
usSrxSipPerf2xxMsgSentByServer 70 usSrxSipPrackMsgRcvByClient 72
usSrxSipPerf301MsgsRcvdByClient 65 usSrxSipPrackMsgSentByServer 73
usSrxSipPerf302MsgsRcvdByClient 65 usSrxSipUpdateMsgRcvByClient 72
usSrxSipPerf3xxMsgRcvByClient 69 usSrxSipUpdateMsgSentByServer 73
usSrxSipPerf3xxMsgSentByServer 71 usSrxUceAbortForAuthFailCounter 93
usSrxSipPerf487MsgsRcvdByClient 68 usSrxUceAbortForCodecUnavailableCounter 93
usSrxSipPerf487MsgsSentByServer 75 usSrxUceAbortForGatewayResourceUnavailable-
usSrxSipPerf4xxMsgRcvByClient 70 Counter 93
usSrxSipPerf4xxMsgSentByServer 71 usSrxUceAbortForMiscErrorCounter 93
usSrxSipPerf5xxMsgRcvByClient 70 usSrxUceAbortForNoRouteAvailableCounter 92
usSrxSipPerf5xxMsgSentByServer 71 usSrxUceAbortForNoTrunkAvailableCounter 92
usSrxSipPerf6xxMsgRcvByClient 70 usSrxUceAbortForUnavailableResourcesCounter 92
usSrxSipPerf6xxMsgSentByServer 71 usSrxUceBackwardReleaseCounter 92
usSrxSipPerfAckforCancelMsgsRecdByServer 76 usSrxUceCallsReachAddrCompleteCounter 92
usSrxSipPerfAckForCancelMsgsSentByClient 68 usSrxUceCallsReachAnswerCounter 92
usSrxSipPerfAckForErrorMsgsRecdByServer 74 usSrxUceForwardReleaseCounter 91
usSrxSipPerfAckForErrorMsgsSentByClient 66 usSrxUceIncomingHalfCallsCounter 91
usSrxSipPerfAckforInviteMsgsRecdByServer 72 usSrxUceOutgoingHalfCallsCounter 91
usSrxSipPerfAckForInviteMsgsSentByClient 66 usSrxUceSipToMgcpCounter 93
usSrxSipPerfByeMsgsRecdByServer 67 usSrxUceSipToSipCounter 94
usSrxSipPerfByeMsgsSentByClient 67 usSrxUceTermToTreatmentCounter 93
usSrxSipPerfCancelMsgsRecdByServer 75 usSrxUceTotalReleaseCounter 92
usSrxSipPerfCancelMsgsSentByClient 67
usSrxSipPerfErrorMsgsRcvdByClient 66 Z
usSrxSipPerfErrorMsgsSentByServer 73 Zenoss 16
usSrxSipPerfInviteMsgsRecdByServer 73
usSrxSipPerfInviteMsgsSentByClient 64
usSrxSipPerfNoSupportRcvByClient 72
usSrxSipPerfRegisterMsgsReceivedByServer 71
usSrxSipPerfUACRcv200OKInfo 64
usSrxSipPerfUACRcv200OKNotify 75
usSrxSipPerfUACRcv200OKSubs 76
usSrxSipPerfUACRcv202Accepted 76
usSrxSipPerfUACRcv300Multiple 65
usSrxSipPerfUACRcv4xx6xxNotify 76
usSrxSipPerfUACRcv4xx6xxRefer 77
usSrxSipPerfUACRcv4xx6xxSubs 64
usSrxSipPerfUACSntInfo 64
usSrxSipPerfUACSntNotify 75
usSrxSipPerfUACSntRefer 76
usSrxSipPerfUACSntSubscribe 76
usSrxSipPerfUASRcvInfo 68
usSrxSipPerfUASRcvNotify 66
usSrxSipPerfUASRcvRefer 65
usSrxSipPerfUASRcvSubscribe 67
usSrxSipPerfUASSnt200OKInfo 69
usSrxSipPerfUASSnt200OKNotify 67
usSrxSipPerfUASSnt200OKSubs 68
usSrxSipPerfUASSnt202Accepted 65
usSrxSipPerfUASSnt4xx6xxNotify 67