POLYCOM-RMX-MIB: View SNMP OID List / Download MIB

VENDOR: POLYCOM


 Home MIB: POLYCOM-RMX-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 polycom 1.3.6.1.4.1.13885
This is RMX MCU MIB
             nsdProducts 1.3.6.1.4.1.13885.9
                 rmx 1.3.6.1.4.1.13885.9.1
                     rmxMib1 1.3.6.1.4.1.13885.9.1.1
                         rmxMib1General 1.3.6.1.4.1.13885.9.1.1.1
                             rmxCurrentStatus 1.3.6.1.4.1.13885.9.1.1.1.1 rmxstatus read-only
MCU current status
                         rmxMib1Events 1.3.6.1.4.1.13885.9.1.1.2
                             rmxMib1EventsParams 1.3.6.1.4.1.13885.9.1.1.2.1
                                 rmxAlarmDescription 1.3.6.1.4.1.13885.9.1.1.2.1.1 octet string no-access
Active alarm description
                                 rmxActiveAlarmDateAndTime 1.3.6.1.4.1.13885.9.1.1.2.1.2 dateandtime no-access
Active alarm date and time
                                 rmxActiveAlarmIndex 1.3.6.1.4.1.13885.9.1.1.2.1.3 unsigned32 no-access
Active alarm table unique index number
                                 rmxActiveAlarmListName 1.3.6.1.4.1.13885.9.1.1.2.1.4 octet string no-access
The alarmListName value of this entery.
                                 rmxActiveAlarmRmxStatus 1.3.6.1.4.1.13885.9.1.1.2.1.5 rmxstatus no-access
The current status of the RMX
                             rmxNotify 1.3.6.1.4.1.13885.9.1.1.2.2
                                 rmxTraps 1.3.6.1.4.1.13885.9.1.1.2.2.0
                                     rmxNoLicensingAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5001
License not found
                                     rmxNoMeetingRoomAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5002
Resource process did not receive the Meeting Room list during startup.
                                     rmxNoIpServiceParamsAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5003
No IP Network Services defined
                                     rmxTaskTerminatedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5004
Task terminated
                                     rmxCfgChangedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5005
System Configuration modified
                                     rmxCfgInvalidAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5006
Invalid System Configuration
                                     rmxDebugModeAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5007
DEBUG mode enabled
                                     rmxLowProcessMemoryAlertAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5008
Low Processing Memory
                                     rmxLowSystemMemoryAlertAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5009
Low system Memory
                                     rmxSystemCpuUsageAlertAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5010
High system CPU usage
                                     rmxTestErrorAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5011
Used for testing the Active Alarms mechanism
                                     rmxSipSecuredCommunicationFailedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5012
Secured SIP communication failed
                                     rmxBadFileAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5013
File error
                                     rmxHighCpuUsageProcessAlertAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5014
High CPU utilization
                                     rmxIdleDeadlineReachedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5016
Process idle
                                     rmxStartupConditionConfigurationAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5017
Internal System configuration during startup
                                     rmxRestoringDefaultFactoryAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5018
Restoring Factory Defaults. Default system settings will be restored once Reset is completed
                                     rmxIpVersionChangedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5019
IP Version has been changed
                                     rmxNoServiceFoundInDbAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5050
IP Network Service not found
                                     rmxNoConnectionWithCsAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5052
No response from Central Signaling
                                     rmxCsComponentFatalAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5053
Central signaling component failure
                                     rmxCsNotConfiguredAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5054
Missing Central Signaling configuration
                                     rmxCsServiceStateFailAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5055
Central Signaling indicating Faulty status
                                     rmxCsStartupFailedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5056
Central Signaling startup failure
                                     rmxDuplicateIpCsMngmntAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5058
IP addresses of Signaling Host and Control Unit are the same
                                     rmxIpServiceDeletedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5059
IP Network Service deleted
                                     rmxIpServiceChangedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5060
IP Network Service configuration modified
                                     rmxCsRecoveryStatusAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5061
Central Signaling indicating Recovery status
                                     rmxExternalAlertCsAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5062
Alarm generated by a Central Signaling component
                                     rmxProductActivationFailureAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5100
Product activation failure
                                     rmxNoManagementIpInterfaceAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5101
Management Network not configured
                                     rmxNoTimeConfigurationAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5102
Error reading MCU time
                                     rmxMplStartupFailureAuthenticationNotReceivedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5103
MPL startup failure. Authentication not received.
                                     rmxMplStartupFailureMngmntIpCnfgNotReceivedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5104
MPL startup failure. Management Network configuration not received.
                                     rmxNoDnsConfigurationAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5105
DNS not configured in IP Network Service
                                     rmxDnsRegistraionFailedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5106
Failed to register with DNS server
                                     rmxFailedToOpenApacheConfigurationFileAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5107
Failed to open Apache server configuration file
                                     rmxFailedToSaveApacheConfigurationFileAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5108
Failed to save Apache server configuration file
                                     rmxPatchedVersionAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5109
The software contains patch(es)
                                     rmxPrivateVersionAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5110
A private version is loaded
                                     rmxNtpSyncFailureAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5111
NTP synchronization failure
                                     rmxIllegalTimeAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5112
Invalid date and time
                                     rmxExternalNtpServersFailureAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5113
External NTP servers failure
                                     rmxRunningVersionMismatchesCurrentVersionAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5114
Fallback version is being used
                                     rmxIdeNotInDmaModeAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5115
DMA not supported by IDE device
                                     rmxBadEthernetSettingsAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5116
Incorrect Ethernet Settings
                                     rmxSmartReportErrorsOnHdAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5117
Smart Report found errors on hard disk
                                     rmxIllegalMcuVersionAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5118
Invalid MCU Version
                                     rmxDebugCfgExistAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5119
DEBUG mode flags in use
                                     rmxInstallingNewVersionAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5120
Version upgrade is in progress
                                     rmxSshEnabledAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5121
SSH is enabled
                                     rmxFailedToValidateCertificateAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5122
Security mode failed. Error in certificate file.
                                     rmxCertificateExpiredAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5123
Security mode failed. Certificate has expired.
                                     rmxCertificateCommonNameErrorAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5124
Security mode failed. Certificate host name does not match the RMX host name.
                                     rmxCertificateNotValidYetAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5125
Security mode failed. Certificate not yet valid.
                                     rmxCertificateGoingToBeExpiredAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5126
Security mode failed. Certificate is about to expire.
                                     rmxProductTypeMismatchAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5127
Product Type mismatch. System is restarting.
                                     rmxUnknownCpuSlotIdAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5128
CPU slot ID not identified
                                     rmxNoFipsTestResultFromEncryptionkeyserverAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5129
FIPS 140 test result not received
                                     rmxFipsFailureWithinEncryptionkeyserverAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5130
FIPS 140 failure
                                     rmxHttpsDisabledInJitcAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5131
The system has been configured for JITC mode, but communication is not secured until a TLS certificate is installed and the MCU is set to Secured communication.
                                     rmxBackupOfCdrFilesIsRequiredAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5140
Backup of CDR files is required
                                     rmxNoMusicSourceAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5150
Music file error
                                     rmxSwitchNotLoadedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5151
SWITCH not responding
                                     rmxNoIsdnServiceParamsAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5152
No ISDN/PSTN Network Services defined
                                     rmxModuleDoesNotExistAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5153
Card not found
                                     rmxNoDefaultIsdnServiceAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5154
No default ISDN/PSTN Network Service defined in ISDN/PSTN Network Services list
                                     rmxExternalAlertEmbAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5155
Alarm generated by an internal component
                                     rmxVersionInstallProgressAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5156
Software upgrade in component
                                     rmxVersionIpmcInstallProgressAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5157
IPMC software upgrade in component
                                     rmxVoltageProblemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5200
Voltage problem
                                     rmxTemperatureMajorProblemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5201
Temperature Level Major
                                     rmxTemperatureCriticalProblemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5202
Temperature Level Critical
                                     rmxFailureProblemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5203
Card failure
                                     rmxPowerOffProblemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5204
Power off
                                     rmxOtherProblemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5205
Unspecified problem
                                     rmxNoConnectionWithCardAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5206
Card not responding
                                     rmxUnitNotRespondingAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5207
Unit not responding
                                     rmxMediaIpConfigurationFailureAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5208
Failed to configure the Media card IP address
                                     rmxCardFolderMountingFailedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5209
Failed to mount Card folder
                                     rmxCardStartupFailureAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5211
Could not complete MPM Card startup procedure
                                     rmxRtmIsdnStartupFailureAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5212
Could not complete RTM ISDN Card startup procedure
                                     rmxRtmIsdnStartupProblemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5213
RTM ISDN card startup procedure error
                                     rmxNoConnectionWithRtmIsdnAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5214
No response from RTM ISDN card
                                     rmxRedAlarmAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5215
Red Alarm
                                     rmxYellowAlarmAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5216
Yellow Alarm
                                     rmxDChannelNotEstablishedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5217
D channel cannot be established
                                     rmxCardsConfigEventAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5218
Card configuration event
                                     rmxCardsWrongFileModeAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5219
Cards wrong file's mode
                                     rmxCardsFlashAccessProblemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5220
Card failed to switch to Enhanced Security Mode
                                     rmxRtmLanOrIsdnMissingAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5221
No RTM-LAN or RTM-ISDN installed. One of these cards must be installed in the RMX 4000
                                     rmxNoLanConnectionAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5222
No LAN connection
                                     rmxCanNotEstablishConnectionWithSipRegistrarAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5300
Failed to connect to SIP registrar
                                     rmxSipRegistrationLimitReachedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5301
SIP registrations limit reached
                                     rmxFailedToAccessDnsServerAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5350
Failed to access DNS server
                                     rmxNoIndDnsSuccessAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5351
DNS configuration error
                                     rmxFailedToInitFileSystemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5400
Failed to initialize the file system
                                     rmxBadFileSystemAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5401
The Log file system is disabled
                                     rmxBadHardDiskAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5402
Hard disk error
                                     rmxBackupOfLogFilesIsRequiredAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5403
Backup of log files is required
                                     rmxBackupOfAuditFilesIsRequiredAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5430
Backup of audit files is required
                                     rmxFailedToFillActionRedirectionAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5450
Action redirection failure
                                     rmxFailedConfigUserListInLinuxAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5500
Failed to configure the Users list in Linux
                                     rmxInsufficientResourcesAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5550
Insufficient resources
                                     rmxPortConfigurationChangedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5551
Port configuration was modified
                                     rmxNoUtilizableUnitForAudioControllerAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5552
No usable unit for audio controller
                                     rmxAllocationModeChangedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5553
Allocation mode was modified
                                     rmxProcessTerminatedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5601
Process terminated
                                     rmxResetMcuByTerminalAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5602
Terminal initiated MCU reset
                                     rmxResetMcuByOperatorAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5603
User initiated MCU reset
                                     rmxResetMcuInternalAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5604
Internal MCU reset
                                     rmxResetMcuAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5605
MCU reset
                                     rmxResetMcuDiagnosticsAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5606
MCU Reset to enable Diagnostics mode
                                     rmxProcessStartupFailedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5607
Startup process failure
                                     rmxSystemInSafeModeAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5608
Automatic reset is unavailable in Safe Mode
                                     rmxGuiSystemConfigIsIllegalAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5609
GUI System configuration file is invalid xml file
                                     rmxFileSystemFailedToScanAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5650
File system scan failure
                                     rmxFileSystemOverflowAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5651
File system space shortage
                                     rmxHardDiskFailureAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5652
Hard disk error
                                     rmxCpuIpcmSoftwareIsNotUpdatedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5690
CPU IPMC software was not updated.
                                     rmxNewVersionInstalledAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5700
A new version was installed. Reset the system.
                                     rmxNewActivationKeyLoadedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5701
A new activation key was loaded. Reset the system.
                                     rmxInsufficientUdpPortsAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5751
Insufficient UDP Ports
                                     rmxUsersListCorruptedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5800
Failed to open Users list file
                                     rmxDefaultUserExistsAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5801
Polycom default User exists. For security reasons, it is recommended to delete this User and create your own User.
                                     rmxSupportOperatorIllegalInFederalModeAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5802
User Name SUPPORT cannot be used in Enhanced Security Mode
                                     rmxIsdnServicesConfigurationChangedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5900
ISDN/PSTN Network Services configuration changed
                                     rmxNoIsdnPstnLicensingAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5901
No License for ISDN/PSTN. Please activate the RTM ISDN card through Polycom website
                                     rmxNoRtmIsdnCardAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5902
RTM ISDN card not found
                                     rmxNoClockSourceAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5903
No clock source
                                     rmxSingleClockSourceAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5904
Single clock source
                                     rmxGkmngrAvfWrongMcuConfigAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5950
MCU is not configured for AVF gatekeeper mode
                                     rmxGateKeeperErrorAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.5951
Gatekeeper failure
                                     rmxCanNotEstablishConnectionWithApplicationServerAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6000
Failed to connect to application server
                                     rmxSystemConfigurationAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6001
Configuration of external database did not complete.
                                     rmxExternalDbCertificateErrorAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6002
Error in external database certificate
                                     rmxIvrServiceListMissingDefaultServiceAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6050
No default IVR Service in IVR Services list
                                     rmxCanNotCreateDefaultProfileAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6051
Failed to create Default Profile
                                     rmxNoReadMrDbReqRecievedFromRsrcAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6052
Resource process failed to request the Meeting Room list during startup.
                                     rmxFailedToConnectRecordingLinkAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6053
Failed to connect to recording device
                                     rmxRecordingLinkDisconnecedUnexpectedlyAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6054
Recording device has disconnected unexpectedly
                                     rmxSystemBasedModeNotIntializedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6055
Failed to initialize system base mode
                                     rmxConfEncryptionErrorAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6056
Conference Encryption Error
                                     rmxSnmpAgentInitFailedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6100
Failure in initialization of SNMP agent.
                                     rmxRestoreSucceededAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6200
Restore Succeeded
                                     rmxRestoreFailedAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.6201
Restore Failed
                                     rmxEncryptionServerErrorAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.7010
Encryption Server Error. Failed to generate the encryption key
                                     rmxExchangeServerConnectionErrorAlarmFault 1.3.6.1.4.1.13885.9.1.1.2.2.0.7050
Unable to connect to Exchange Server.
                                     rmxNoLicensingAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15001
License not found
                                     rmxNoMeetingRoomAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15002
Resource process did not receive the Meeting Room list during startup.
                                     rmxNoIpServiceParamsAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15003
No IP Network Services defined
                                     rmxTaskTerminatedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15004
Task terminated
                                     rmxCfgChangedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15005
System Configuration modified
                                     rmxCfgInvalidAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15006
Invalid System Configuration
                                     rmxDebugModeAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15007
DEBUG mode enabled
                                     rmxLowProcessMemoryAlertAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15008
Low Processing Memory
                                     rmxLowSystemMemoryAlertAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15009
Low system Memory
                                     rmxSystemCpuUsageAlertAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15010
High system CPU usage
                                     rmxTestErrorAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15011
Used for testing the Active Alarms mechanism
                                     rmxSipSecuredCommunicationFailedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15012
Secured SIP communication failed
                                     rmxBadFileAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15013
File error
                                     rmxHighCpuUsageProcessAlertAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15014
High CPU utilization
                                     rmxIdleDeadlineReachedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15016
Process idle
                                     rmxStartupConditionConfigurationAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15017
Internal System configuration during startup
                                     rmxRestoringDefaultFactoryAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15018
Restoring Factory Defaults. Default system settings will be restored once Reset is completed
                                     rmxIpVersionChangedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15019
IP Version has been changed
                                     rmxNoServiceFoundInDbAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15050
IP Network Service not found
                                     rmxNoConnectionWithCsAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15052
No response from Central Signaling
                                     rmxCsComponentFatalAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15053
Central signaling component failure
                                     rmxCsNotConfiguredAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15054
Missing Central Signaling configuration
                                     rmxCsServiceStateFailAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15055
Central Signaling indicating Faulty status
                                     rmxCsStartupFailedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15056
Central Signaling startup failure
                                     rmxDuplicateIpCsMngmntAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15058
IP addresses of Signaling Host and Control Unit are the same
                                     rmxIpServiceDeletedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15059
IP Network Service deleted
                                     rmxIpServiceChangedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15060
IP Network Service configuration modified
                                     rmxCsRecoveryStatusAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15061
Central Signaling indicating Recovery status
                                     rmxExternalAlertCsAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15062
Alarm generated by a Central Signaling component
                                     rmxProductActivationFailureAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15100
Product activation failure
                                     rmxNoManagementIpInterfaceAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15101
Management Network not configured
                                     rmxNoTimeConfigurationAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15102
Error reading MCU time
                                     rmxMplStartupFailureAuthenticationNotReceivedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15103
MPL startup failure. Authentication not received.
                                     rmxMplStartupFailureMngmntIpCnfgNotReceivedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15104
MPL startup failure. Management Network configuration not received.
                                     rmxNoDnsConfigurationAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15105
DNS not configured in IP Network Service
                                     rmxDnsRegistraionFailedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15106
Failed to register with DNS server
                                     rmxFailedToOpenApacheConfigurationFileAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15107
Failed to open Apache server configuration file
                                     rmxFailedToSaveApacheConfigurationFileAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15108
Failed to save Apache server configuration file
                                     rmxPatchedVersionAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15109
The software contains patch(es)
                                     rmxPrivateVersionAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15110
A private version is loaded
                                     rmxNtpSyncFailureAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15111
NTP synchronization failure
                                     rmxIllegalTimeAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15112
Invalid date and time
                                     rmxExternalNtpServersFailureAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15113
External NTP servers failure
                                     rmxRunningVersionMismatchesCurrentVersionAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15114
Fallback version is being used
                                     rmxIdeNotInDmaModeAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15115
DMA not supported by IDE device
                                     rmxBadEthernetSettingsAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15116
Incorrect Ethernet Settings
                                     rmxSmartReportErrorsOnHdAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15117
Smart Report found errors on hard disk
                                     rmxIllegalMcuVersionAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15118
Invalid MCU Version
                                     rmxDebugCfgExistAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15119
DEBUG mode flags in use
                                     rmxInstallingNewVersionAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15120
Version upgrade is in progress
                                     rmxSshEnabledAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15121
SSH is enabled
                                     rmxFailedToValidateCertificateAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15122
Security mode failed. Error in certificate file.
                                     rmxCertificateExpiredAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15123
Security mode failed. Certificate has expired.
                                     rmxCertificateCommonNameErrorAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15124
Security mode failed. Certificate host name does not match the RMX host name.
                                     rmxCertificateNotValidYetAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15125
Security mode failed. Certificate not yet valid.
                                     rmxCertificateGoingToBeExpiredAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15126
Security mode failed. Certificate is about to expire.
                                     rmxProductTypeMismatchAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15127
Product Type mismatch. System is restarting.
                                     rmxUnknownCpuSlotIdAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15128
CPU slot ID not identified
                                     rmxNoFipsTestResultFromEncryptionkeyserverAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15129
FIPS 140 test result not received
                                     rmxFipsFailureWithinEncryptionkeyserverAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15130
FIPS 140 failure
                                     rmxHttpsDisabledInJitcAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15131
The system has been configured for JITC mode, but communication is not secured until a TLS certificate is installed and the MCU is set to Secured communication.
                                     rmxBackupOfCdrFilesIsRequiredAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15140
Backup of CDR files is required
                                     rmxNoMusicSourceAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15150
Music file error
                                     rmxSwitchNotLoadedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15151
SWITCH not responding
                                     rmxNoIsdnServiceParamsAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15152
No ISDN/PSTN Network Services defined
                                     rmxModuleDoesNotExistAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15153
Card not found
                                     rmxNoDefaultIsdnServiceAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15154
No default ISDN/PSTN Network Service defined in ISDN/PSTN Network Services list
                                     rmxExternalAlertEmbAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15155
Alarm generated by an internal component
                                     rmxVersionInstallProgressAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15156
Software upgrade in component
                                     rmxVersionIpmcInstallProgressAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15157
IPMC software upgrade in component
                                     rmxVoltageProblemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15200
Voltage problem
                                     rmxTemperatureMajorProblemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15201
Temperature Level Major
                                     rmxTemperatureCriticalProblemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15202
Temperature Level Critical
                                     rmxFailureProblemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15203
Card failure
                                     rmxPowerOffProblemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15204
Power off
                                     rmxOtherProblemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15205
Unspecified problem
                                     rmxNoConnectionWithCardAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15206
Card not responding
                                     rmxUnitNotRespondingAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15207
Unit not responding
                                     rmxMediaIpConfigurationFailureAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15208
Failed to configure the Media card IP address
                                     rmxCardFolderMountingFailedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15209
Failed to mount Card folder
                                     rmxCardStartupFailureAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15211
Could not complete MPM Card startup procedure
                                     rmxRtmIsdnStartupFailureAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15212
Could not complete RTM ISDN Card startup procedure
                                     rmxRtmIsdnStartupProblemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15213
RTM ISDN card startup procedure error
                                     rmxNoConnectionWithRtmIsdnAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15214
No response from RTM ISDN card
                                     rmxRedAlarmAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15215
Red Alarm
                                     rmxYellowAlarmAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15216
Yellow Alarm
                                     rmxDChannelNotEstablishedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15217
D channel cannot be established
                                     rmxCardsConfigEventAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15218
Card configuration event
                                     rmxCardsWrongFileModeAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15219
Cards wrong file's mode
                                     rmxCardsFlashAccessProblemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15220
Card failed to switch to Enhanced Security Mode
                                     rmxRtmLanOrIsdnMissingAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15221
No RTM-LAN or RTM-ISDN installed. One of these cards must be installed in the RMX 4000
                                     rmxNoLanConnectionAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15222
No LAN connection
                                     rmxCanNotEstablishConnectionWithSipRegistrarAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15300
Failed to connect to SIP registrar
                                     rmxSipRegistrationLimitReachedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15301
SIP registrations limit reached
                                     rmxFailedToAccessDnsServerAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15350
Failed to access DNS server
                                     rmxNoIndDnsSuccessAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15351
DNS configuration error
                                     rmxFailedToInitFileSystemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15400
Failed to initialize the file system
                                     rmxBadFileSystemAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15401
The Log file system is disabled
                                     rmxBadHardDiskAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15402
Hard disk error
                                     rmxBackupOfLogFilesIsRequiredAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15403
Backup of log files is required
                                     rmxBackupOfAuditFilesIsRequiredAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15430
Backup of audit files is required
                                     rmxFailedToFillActionRedirectionAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15450
Action redirection failure
                                     rmxFailedConfigUserListInLinuxAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15500
Failed to configure the Users list in Linux
                                     rmxInsufficientResourcesAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15550
Insufficient resources
                                     rmxPortConfigurationChangedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15551
Port configuration was modified
                                     rmxNoUtilizableUnitForAudioControllerAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15552
No usable unit for audio controller
                                     rmxAllocationModeChangedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15553
Allocation mode was modified
                                     rmxProcessTerminatedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15601
Process terminated
                                     rmxResetMcuByTerminalAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15602
Terminal initiated MCU reset
                                     rmxResetMcuByOperatorAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15603
User initiated MCU reset
                                     rmxResetMcuInternalAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15604
Internal MCU reset
                                     rmxResetMcuAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15605
MCU reset
                                     rmxResetMcuDiagnosticsAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15606
MCU Reset to enable Diagnostics mode
                                     rmxProcessStartupFailedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15607
Startup process failure
                                     rmxSystemInSafeModeAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15608
Automatic reset is unavailable in Safe Mode
                                     rmxGuiSystemConfigIsIllegalAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15609
GUI System configuration file is invalid xml file
                                     rmxFileSystemFailedToScanAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15650
File system scan failure
                                     rmxFileSystemOverflowAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15651
File system space shortage
                                     rmxHardDiskFailureAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15652
Hard disk error
                                     rmxCpuIpcmSoftwareIsNotUpdatedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15690
CPU IPMC software was not updated.
                                     rmxNewVersionInstalledAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15700
A new version was installed. Reset the system.
                                     rmxNewActivationKeyLoadedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15701
A new activation key was loaded. Reset the system.
                                     rmxInsufficientUdpPortsAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15751
Insufficient UDP Ports
                                     rmxUsersListCorruptedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15800
Failed to open Users list file
                                     rmxDefaultUserExistsAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15801
Polycom default User exists. For security reasons, it is recommended to delete this User and create your own User.
                                     rmxSupportOperatorIllegalInFederalModeAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15802
User Name SUPPORT cannot be used in Enhanced Security Mode
                                     rmxIsdnServicesConfigurationChangedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15900
ISDN/PSTN Network Services configuration changed
                                     rmxNoIsdnPstnLicensingAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15901
No License for ISDN/PSTN. Please activate the RTM ISDN card through Polycom website
                                     rmxNoRtmIsdnCardAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15902
RTM ISDN card not found
                                     rmxNoClockSourceAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15903
No clock source
                                     rmxSingleClockSourceAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15904
Single clock source
                                     rmxGkmngrAvfWrongMcuConfigAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15950
MCU is not configured for AVF gatekeeper mode
                                     rmxGateKeeperErrorAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.15951
Gatekeeper failure
                                     rmxCanNotEstablishConnectionWithApplicationServerAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16000
Failed to connect to application server
                                     rmxSystemConfigurationAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16001
Configuration of external database did not complete.
                                     rmxExternalDbCertificateErrorAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16002
Error in external database certificate
                                     rmxIvrServiceListMissingDefaultServiceAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16050
No default IVR Service in IVR Services list
                                     rmxCanNotCreateDefaultProfileAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16051
Failed to create Default Profile
                                     rmxNoReadMrDbReqRecievedFromRsrcAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16052
Resource process failed to request the Meeting Room list during startup.
                                     rmxFailedToConnectRecordingLinkAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16053
Failed to connect to recording device
                                     rmxRecordingLinkDisconnecedUnexpectedlyAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16054
Recording device has disconnected unexpectedly
                                     rmxSystemBasedModeNotIntializedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16055
Failed to initialize system base mode
                                     rmxConfEncryptionErrorAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16056
Conference Encryption Error
                                     rmxSnmpAgentInitFailedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16100
Failure in initialization of SNMP agent.
                                     rmxRestoreSucceededAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16200
Restore Succeeded
                                     rmxRestoreFailedAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.16201
Restore Failed
                                     rmxEncryptionServerErrorAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.17010
Encryption Server Error. Failed to generate the encryption key
                                     rmxExchangeServerConnectionErrorAlarmClear 1.3.6.1.4.1.13885.9.1.1.2.2.0.17050
Unable to connect to Exchange Server.
                     rmxProducts 1.3.6.1.4.1.13885.9.1.10
                           rmx2000 1.3.6.1.4.1.13885.9.1.10.1
                           rmx4000 1.3.6.1.4.1.13885.9.1.10.2