INFORMATION
MiContact Center includes an SNMP agent that enables you to monitor MiContact Center alarms through an SNMP manager. MiContact Center SNMP agent integrates with the Windows SNMP service and requires that a Windows SNMP Service be added and configured on the Enterprise Server.
The MiContact Center SNMP agent is primarily configured for traps only, but also responds to Get-request messages for trap messages.
SNMP Agent provides information on nine categories of alarms:
- General Category Alarm
- Data Collection Alarms
- Server Resource Alarm
- Communication Alarm
- License Violation Alarm
- IVR Alarm
- Reporting Alarm
- Performance Alarm
- Configuration Alarm
The value reported for each alarm category is the highest severity of alarm currently triggered in that category.
CONFIGURING WINDOWS SNMP SERVICE
MiContact Center and Business Reporter requires the use of the Windows SNMP service for the MiContact Center SNMP agent.
The following procedures outlines how to:
- Install the Windows SNMP services (Windows Server 2008 R2 and Windows Server 2012 and 2012 R2)
- Configure Windows SNMP service for the SNMP agent
To install the Windows SNMP services (Windows Server 2008 R2)
- Start the Server Manager.
- Under Features Summary, click Add Features.
- The Add Features Wizard opens.
- SNMP Services
- SNMP Service
- SNMP WMI Provider
To install the Windows SNMP services (Windows Server 2012 and 2012 R2)
- Start the Server Manager.
- Click Manage =>Add Roles and Features.
- The Add Roles and Features Wizard opens.
- SNMP Service
- SNMP WMI Provider
To configure Windows SNMP service for the SNMP agent
- If you do not have SNMP Service installed on your server, install it using the Add/Remove Program, Add Features, or Add roles and features function of your Window server.
- After the installation has completed, navigate to Services.
- Right-click on SNMP and select Properties.
- Select the Traps tab.
- Under Community name, type a community name, such as Public, and click Add to list.
- Under Trap destinations:, click Add.
- Under Host name, IP or UPX address:, type the destination for MiContact Center SNMP Agent traps.
- Click Add.
- Select the Security tab.
- Click Add.
- In the Community rights drop-down list, select READ WRITE.
- Under Community name:, type Public.
- Select the Log On tab.
- Under Log on as:, select Local System Account.
- Click OK.
- NOTE: After setting up your SNMP Agent, it is recommended you test it using an appropriate tool to confirm that it has been configured correctly.
SNMP MIB SUMMARY
Table 1 and Table 2 summarize object information from the MIB. The MIB is located in <drive>/CCM/Services/MaintenanceAlarmDispatcher/Snmp.
Table 1: prairieFyre sub-tree
Object Type | Object Identifier |
enterpriseAlarms | prairieFyre 1 |
enterpriseAlarms | prairieFyre 2 |
enterpriseAlarms | prairieFyre 3 |
Object Type | Syntax Integer | Max Access | Description | Object Identifier |
manufacturer | manufacturer | read-only | Mitel Networks Contact Center Suite | enterpriseAlarms 1 |
overridingSystemAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | This is the cumulative total of all reporting active alarms and should be viewed as the overriding alarm state that the Mitel suite is now reporting. | enterpriseAlarms 2 |
generalCatagoryAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | When a software entity raises an alarm not covered in the following list then it is categorized as a general alarm. | enterpriseAlarms 3 |
dataCollectionAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | One of the Media Controller Data Link Connections within the Mitel Enterprise is offline. This could be a connection to a PBX or an email server or some other controller of a media transaction that is configured to be connected to the Mitel suite. | enterpriseAlarms 4 |
serverResourceAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | One or more software services in the Mitel suite is reporting an unusual consumption of computer resources. This may a result of an exceptionally high CPU consumption or running low on physical memory, for example. This may require a service restart to resolve. | enterpriseAlarms 5 |
communicationsAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | One or more service endpoints is reporting an error in its control channel with an associated endpoint. This may be a socket or WCF channel or may be an MSMQ error that is preventing normal process flow in the Mitel software suite. | enterpriseAlarms 6 |
licenseViolationAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | The prairieFyre Enterprise Licensing Manager is reporting that the installation is violating or has attempted to exceed enforced license limits for their installation. This may be configuring the YSE services for features or capacity they have not purchased. | enterpriseAlarms 7 |
ivrAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | The Routing services for IVR Routing are reporting an alarm, which may be due to media ports being out of service or an inability to load a workflow. | enterpriseAlarms 8 |
reportingAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | The reporting engine is reporting an error that implies it cannot generate a requested report due to a system inoperability error. This may be a corrupt report template or could be a transaction error on the retrieval of SQL data to fill the report. | enterpriseAlarms 9 |
performanceAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | One or more of the service endpoints in the Mitel suite is reporting an overload condition. | |
configurationAlarm | unknownAlarm(0) noAlarm(1) minorAlarm(2) majorAlarm(3) criticalAlarm(4) | read-only | One or more of the service endpoints in the Mitel suite is reporting an error when loading configuration data. |
APPLIES TO
MiCC Version 6.0.2.3 and newer
Keywords: SNMP agent alarms enable enabling