Indeterminate Alarms

Mitel Performance Analytics has some common indeterminate alarms that are easy to resolve. These alarms typically occur in the following situations:

A new device has been configured in Mitel Performance Analytics but has not yet been connected to it, either directly or using a Probe.

There is a network communications failure between the device and Mitel Performance Analytics. This may be due to an authentication error, a local network problem, or an internet connectivity issue.

The Probe responsible for reporting the status of the device has failed to communicate with Mitel Performance Analytics. In this case, all of the devices that are monitored by this Probe are placed into the indeterminate state.

Licensing issues.

During initial setup and configuration of Mitel Performance Analytics, many indeterminate alarms will be raised. To hide them, click the Indeterminate Alarms filter button on the bar located above the Alarm Panel, as shown in the figure below.

The following table contains a list of the most common indeterminate alarms, along with suggestions and links to help topics to assist you in resolving the alarm.

Alarm	Resolution
Invalid AXI credentials	Re-enter the AXI Credentials for the Mitel DIP DECT OMM device. Refer to "Configuring Mitel Performance Analytics for Mitel SIP DECT OMM".
MarWatch Probe (###.###.###.###) is not set as SNMP Trap destination	Ensure the device has SNMP configured to same port on which the probe receives SNMP packets. Refer to "Receipt of SNMP Traps".
Message Print connection failure	Detailed MiVoice Office 250 alarm information is available in the MiVoice Office user documenation: https://www.mitel.com/document-center/business-phone-systems/mivoice-office-250/mivoice-office-250.
MiCollabAM: Required Service not Found: OneBox DAL Server	Restart critical services. If the mentioned server is not present, double check the device configuration in Mitel Performance Analytics.
MiVoice Business Trap Forwarding table full. Cannot add Probe IP address as SNMP Trap destination	Check the SNMP Trap Recipient list for the MiVoice Business device and remove any depreciated entries. See one of: • "MiVoice Business SNMP Configuration For MiVB Before 9.0". • "MiVoice Business SNMP Configuration For MiVB and MiVB EX Version 9.0 and Later".
New device, information not yet available	Mitel Performance Analytics has not yet collected information from the device. This alarm only appears on newly created devices.
No probe configured	Ensure that a probe has been assigned this device. On the dashboard for the device in question, select System Administration > <Device_Name> Settings and select the probe to use. Refer to the device specific configuration help topics under "Configuring Mitel Performance Analytics Devices",
No SSH Credentials set for this device: cannot connect to device via SSH.	Refer to the device specific configuration help topics under "Configuring Mitel Performance Analytics Devices" to configure SSH for the specific device. NOTE: If the alarm is on a MiVoice Business device that has been upgraded to version 9, it may be that the MSL password has not been set. See "Configuring Mitel Performance Analytics for MiVoice Business " for details.
Probe has not yet connected	When a device is created or edited, it can take up to 15 minutes for the configuration changes to propagate to the Probe.
Probe not reporting	The Probe assigned to this device has not checked in to the Mitel Performance Analytics server for some time. The probe may be powered off or blocked by network issues.
SMDR connection failure	Ensure SMDR Collection is configured correctly. Refer to the following topics: • "SMDR Collection" • "MiVoice Business SMDR Collection", • "MiVoice Office 250 Device Configuration" • "Avaya IP Office Device Configuration".
SNMP unreachable	The Probe is unable to communicate with the device. Ensure that SNMP has been configured properly both on the device and in Mitel Performance Analytics. Refer to the device specific SNMP configuration help topics under "Configuring Mitel Performance Analytics Devices". See also "SNMP Configuration".
SSH time out occurred when trying to connect	The device may be offline, or a firewall may be blocking SSH connections.
This Device is in maintenance mode.	If the maintenance is scheduled, wait until the maintenance period is complete. If the maintenance was manually set and subsequently forgotten, you can take the device out of maintenance mode by deselecting the maintenance mode option on the devices settings page (System Administration > <Device_Name> Settings). Refer to "Viewing Devices in Maintenance Mode".
Traffic Report Options set incorrectly.	Double check the traffic report options configuration. Refer to "MiVoice Business Digital Trunk and SIP Trunk Utilization Monitoring Configuration".
Unable to connect to device via MiXML	Ensure the MiXML username and password have been configured correctly for the device. Refer to one of the following: • "Configuring Mitel Performance Analytics for MiVoice Business ". • "MiVoice Border Gateway Voice Quality Configuration for MBG before 9.0".
Unlicensed Capability: FeatureName	Check to see which licenses are installed and which ones may have expired using the Licensing Queries available from the Network Data menu. Also see "Mitel Performance Analytics Licensing".
Voice Quality Monitoring is not enabled.	Ensure that Voice Quality Monitoring is properly configured for the device. Refer to the following topics: • "MiVoice Business Voice Quality Configuration". • "MiVoice Border Gateway Voice Quality Configuration for MBG before 9.0". • "MiVoice Border Gateway Voice Quality Configuration for MBG 9.0 and Later".
Unable to acknowledge emergency call on MiVB. Check SNMP Community string.	For emergency response monitoring, ensure the Community String is configured the same on the device and Mitel Performance Analytics. Refer to one of the following topics: • "Configuring Mitel Performance Analytics for MiVoice Business ". • "Configuring Mitel Performance Analytics for MiVoice Business ".
Incorrect OMM platform was selected in Device Settings.	SIP DECT OMM devices support two platform types: Linux and RFP. Double check the device settings to ensure the correct platform is configured. Refer to "Configuring Mitel Performance Analytics for Mitel SIP DECT OMM".