All MIBs › POLYCOM-RMX-MIB
Organization: Polycom Ltd.
Last Updated: 2007-03-14
Category: Video Conferencing
Description: Tracks conference room utilization, media port availability, and active conference statistics for Polycom RMX media servers.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is POLYCOM-RMX-MIB?
POLYCOM-RMX-MIB is a vendor-specific MIB for Polycom's RMX series Multipoint Control Unit (MCU) media servers, used for video/audio conferencing bridging. It exposes objects for current system status, active alarms (description, timestamp, index, and associated status), and general/event configuration parameters for the conferencing platform. Its primary monitoring use is tracking device operational/fault status through rmxCurrentStatus and the active alarm objects, which surface hardware or service faults on the MCU such as port exhaustion or hardware errors, functioning much like a fault/traps subsystem for the conferencing server. It is a self-contained Polycom-proprietary MIB registered under the NSD Products enterprise branch, without notable reliance on external standard MIBs. It is typically deployed in enterprise or service-provider video conferencing environments to monitor the health and utilization of RMX MCU conference bridges. Network engineers evaluating or troubleshooting this functionality can download the POLYCOM-RMX-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in POLYCOM-RMX-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Polycom RMX series MCU (video/audio conferencing media server)
Monitoring Examples
An operator would poll rmxCurrentStatus to get the overall health state of the RMX MCU, and watch rmxActiveAlarmDescription alongside rmxActiveAlarmDateAndTime and rmxActiveAlarmIndex to see what specific fault conditions are currently active, such as a media port or hardware failure. The rmxActiveAlarmRmxStatus and rmxActiveAlarmListName provide additional context on how an alarm affects overall device status. A growing number of entries in the active alarm list combined with a degraded rmxCurrentStatus would signal that the conference bridge is approaching capacity or experiencing hardware issues that could disrupt active conferences.
What Can Be Monitored
- overall system status
- active alarm description and timestamp
- active alarm index and list name
- alarm-associated device status
This MIB depends on
Related MIBs
Imported Objects
From RFC-1215
| TRAP-TYPE |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 | |
| enterprises |
From SNMPv2-TC
| DateAndTime | |
| TEXTUAL-CONVENTION |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| 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 | |||
| RMX 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 | |||
| OCT rmxAlarmDescription | 1.3.6.1.4.1.13885.9.1.1.2.1.1 | OCTET STRING | accessible-for-notify | Active alarm description |
| DAT rmxActiveAlarmDateAndTime | 1.3.6.1.4.1.13885.9.1.1.2.1.2 | DateAndTime | accessible-for-notify | Active alarm date and time |
| U32 rmxActiveAlarmIndex | 1.3.6.1.4.1.13885.9.1.1.2.1.3 | Unsigned32 | accessible-for-notify | Active alarm table unique index number |
| OCT rmxActiveAlarmListName | 1.3.6.1.4.1.13885.9.1.1.2.1.4 | OCTET STRING | accessible-for-notify | The alarmListName value of this entery. |
| RMX rmxActiveAlarmRmxStatus | 1.3.6.1.4.1.13885.9.1.1.2.1.5 | RmxStatus | accessible-for-notify | 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 | |||
| NTF rmxNoLicensingAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5001 | License not found | ||
| NTF 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. | ||
| NTF rmxNoIpServiceParamsAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5003 | No IP Network Services defined | ||
| NTF rmxTaskTerminatedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5004 | Task terminated | ||
| NTF rmxCfgChangedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5005 | System Configuration modified | ||
| NTF rmxCfgInvalidAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5006 | Invalid System Configuration | ||
| NTF rmxDebugModeAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5007 | DEBUG mode enabled | ||
| NTF rmxLowProcessMemoryAlertAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5008 | Low Processing Memory | ||
| NTF rmxLowSystemMemoryAlertAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5009 | Low system Memory | ||
| NTF rmxSystemCpuUsageAlertAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5010 | High system CPU usage | ||
| NTF rmxTestErrorAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5011 | Used for testing the Active Alarms mechanism | ||
| NTF rmxSipSecuredCommunicationFailedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5012 | Secured SIP communication failed | ||
| NTF rmxBadFileAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5013 | File error | ||
| NTF rmxHighCpuUsageProcessAlertAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5014 | High CPU utilization | ||
| NTF rmxIdleDeadlineReachedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5016 | Process idle | ||
| NTF rmxStartupConditionConfigurationAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5017 | Internal System configuration during startup | ||
| NTF 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 | ||
| NTF rmxIpVersionChangedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5019 | IP Version has been changed | ||
| NTF rmxNoServiceFoundInDbAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5050 | IP Network Service not found | ||
| NTF rmxNoConnectionWithCsAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5052 | No response from Central Signaling | ||
| NTF rmxCsComponentFatalAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5053 | Central signaling component failure | ||
| NTF rmxCsNotConfiguredAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5054 | Missing Central Signaling configuration | ||
| NTF rmxCsServiceStateFailAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5055 | Central Signaling indicating Faulty status | ||
| NTF rmxCsStartupFailedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5056 | Central Signaling startup failure | ||
| NTF 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 | ||
| NTF rmxIpServiceDeletedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5059 | IP Network Service deleted | ||
| NTF rmxIpServiceChangedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5060 | IP Network Service configuration modified | ||
| NTF rmxCsRecoveryStatusAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5061 | Central Signaling indicating Recovery status | ||
| NTF rmxExternalAlertCsAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5062 | Alarm generated by a Central Signaling component | ||
| NTF rmxProductActivationFailureAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5100 | Product activation failure | ||
| NTF rmxNoManagementIpInterfaceAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5101 | Management Network not configured | ||
| NTF rmxNoTimeConfigurationAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5102 | Error reading MCU time | ||
| NTF rmxMplStartupFailureAuthenticationNotReceivedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5103 | MPL startup failure. Authentication not received. | ||
| NTF rmxMplStartupFailureMngmntIpCnfgNotReceivedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5104 | MPL startup failure. Management Network configuration not received. | ||
| NTF rmxNoDnsConfigurationAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5105 | DNS not configured in IP Network Service | ||
| NTF rmxDnsRegistraionFailedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5106 | Failed to register with DNS server | ||
| NTF rmxFailedToOpenApacheConfigurationFileAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5107 | Failed to open Apache server configuration file | ||
| NTF rmxFailedToSaveApacheConfigurationFileAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5108 | Failed to save Apache server configuration file | ||
| NTF rmxPatchedVersionAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5109 | The software contains patch(es) | ||
| NTF rmxPrivateVersionAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5110 | A private version is loaded | ||
| NTF rmxNtpSyncFailureAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5111 | NTP synchronization failure | ||
| NTF rmxIllegalTimeAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5112 | Invalid date and time | ||
| NTF rmxExternalNtpServersFailureAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5113 | External NTP servers failure | ||
| NTF rmxRunningVersionMismatchesCurrentVersionAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5114 | Fallback version is being used | ||
| NTF rmxIdeNotInDmaModeAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5115 | DMA not supported by IDE device | ||
| NTF rmxBadEthernetSettingsAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5116 | Incorrect Ethernet Settings | ||
| NTF rmxSmartReportErrorsOnHdAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5117 | Smart Report found errors on hard disk | ||
| NTF rmxIllegalMcuVersionAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5118 | Invalid MCU Version | ||
| NTF rmxDebugCfgExistAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5119 | DEBUG mode flags in use | ||
| NTF rmxInstallingNewVersionAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5120 | Version upgrade is in progress | ||
| NTF rmxSshEnabledAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5121 | SSH is enabled | ||
| NTF rmxFailedToValidateCertificateAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5122 | Security mode failed. Error in certificate file. | ||
| NTF rmxCertificateExpiredAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5123 | Security mode failed. Certificate has expired. | ||
| NTF 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. | ||
| NTF rmxCertificateNotValidYetAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5125 | Security mode failed. Certificate not yet valid. | ||
| NTF rmxCertificateGoingToBeExpiredAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5126 | Security mode failed. Certificate is about to expire. | ||
| NTF rmxProductTypeMismatchAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5127 | Product Type mismatch. System is restarting. | ||
| NTF rmxUnknownCpuSlotIdAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5128 | CPU slot ID not identified | ||
| NTF rmxNoFipsTestResultFromEncryptionkeyserverAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5129 | FIPS 140 test result not received | ||
| NTF rmxFipsFailureWithinEncryptionkeyserverAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5130 | FIPS 140 failure | ||
| NTF 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. | ||
| NTF rmxBackupOfCdrFilesIsRequiredAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5140 | Backup of CDR files is required | ||
| NTF rmxNoMusicSourceAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5150 | Music file error | ||
| NTF rmxSwitchNotLoadedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5151 | SWITCH not responding | ||
| NTF rmxNoIsdnServiceParamsAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5152 | No ISDN/PSTN Network Services defined | ||
| NTF rmxModuleDoesNotExistAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5153 | Card not found | ||
| NTF 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 | ||
| NTF rmxExternalAlertEmbAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5155 | Alarm generated by an internal component | ||
| NTF rmxVersionInstallProgressAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5156 | Software upgrade in component | ||
| NTF rmxVersionIpmcInstallProgressAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5157 | IPMC software upgrade in component | ||
| NTF rmxVoltageProblemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5200 | Voltage problem | ||
| NTF rmxTemperatureMajorProblemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5201 | Temperature Level Major | ||
| NTF rmxTemperatureCriticalProblemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5202 | Temperature Level Critical | ||
| NTF rmxFailureProblemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5203 | Card failure | ||
| NTF rmxPowerOffProblemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5204 | Power off | ||
| NTF rmxOtherProblemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5205 | Unspecified problem | ||
| NTF rmxNoConnectionWithCardAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5206 | Card not responding | ||
| NTF rmxUnitNotRespondingAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5207 | Unit not responding | ||
| NTF rmxMediaIpConfigurationFailureAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5208 | Failed to configure the Media card IP address | ||
| NTF rmxCardFolderMountingFailedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5209 | Failed to mount Card folder | ||
| NTF rmxCardStartupFailureAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5211 | Could not complete MPM Card startup procedure | ||
| NTF rmxRtmIsdnStartupFailureAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5212 | Could not complete RTM ISDN Card startup procedure | ||
| NTF rmxRtmIsdnStartupProblemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5213 | RTM ISDN card startup procedure error | ||
| NTF rmxNoConnectionWithRtmIsdnAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5214 | No response from RTM ISDN card | ||
| NTF rmxRedAlarmAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5215 | Red Alarm | ||
| NTF rmxYellowAlarmAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5216 | Yellow Alarm | ||
| NTF rmxDChannelNotEstablishedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5217 | D channel cannot be established | ||
| NTF rmxCardsConfigEventAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5218 | Card configuration event | ||
| NTF rmxCardsWrongFileModeAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5219 | Cards wrong file's mode | ||
| NTF rmxCardsFlashAccessProblemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5220 | Card failed to switch to Enhanced Security Mode | ||
| NTF 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 | ||
| NTF rmxNoLanConnectionAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5222 | No LAN connection | ||
| NTF rmxCanNotEstablishConnectionWithSipRegistrarAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5300 | Failed to connect to SIP registrar | ||
| NTF rmxSipRegistrationLimitReachedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5301 | SIP registrations limit reached | ||
| NTF rmxFailedToAccessDnsServerAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5350 | Failed to access DNS server | ||
| NTF rmxNoIndDnsSuccessAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5351 | DNS configuration error | ||
| NTF rmxFailedToInitFileSystemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5400 | Failed to initialize the file system | ||
| NTF rmxBadFileSystemAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5401 | The Log file system is disabled | ||
| NTF rmxBadHardDiskAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5402 | Hard disk error | ||
| NTF rmxBackupOfLogFilesIsRequiredAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5403 | Backup of log files is required | ||
| NTF rmxBackupOfAuditFilesIsRequiredAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5430 | Backup of audit files is required | ||
| NTF rmxFailedToFillActionRedirectionAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5450 | Action redirection failure | ||
| NTF rmxFailedConfigUserListInLinuxAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5500 | Failed to configure the Users list in Linux | ||
| NTF rmxInsufficientResourcesAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5550 | Insufficient resources | ||
| NTF rmxPortConfigurationChangedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5551 | Port configuration was modified | ||
| NTF rmxNoUtilizableUnitForAudioControllerAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5552 | No usable unit for audio controller | ||
| NTF rmxAllocationModeChangedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5553 | Allocation mode was modified | ||
| NTF rmxProcessTerminatedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5601 | Process terminated | ||
| NTF rmxResetMcuByTerminalAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5602 | Terminal initiated MCU reset | ||
| NTF rmxResetMcuByOperatorAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5603 | User initiated MCU reset | ||
| NTF rmxResetMcuInternalAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5604 | Internal MCU reset | ||
| NTF rmxResetMcuAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5605 | MCU reset | ||
| NTF rmxResetMcuDiagnosticsAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5606 | MCU Reset to enable Diagnostics mode | ||
| NTF rmxProcessStartupFailedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5607 | Startup process failure | ||
| NTF rmxSystemInSafeModeAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5608 | Automatic reset is unavailable in Safe Mode | ||
| NTF rmxGuiSystemConfigIsIllegalAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5609 | GUI System configuration file is invalid xml file | ||
| NTF rmxFileSystemFailedToScanAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5650 | File system scan failure | ||
| NTF rmxFileSystemOverflowAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5651 | File system space shortage | ||
| NTF rmxHardDiskFailureAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5652 | Hard disk error | ||
| NTF rmxCpuIpcmSoftwareIsNotUpdatedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5690 | CPU IPMC software was not updated. | ||
| NTF rmxNewVersionInstalledAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5700 | A new version was installed. Reset the system. | ||
| NTF rmxNewActivationKeyLoadedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5701 | A new activation key was loaded. Reset the system. | ||
| NTF rmxInsufficientUdpPortsAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5751 | Insufficient UDP Ports | ||
| NTF rmxUsersListCorruptedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5800 | Failed to open Users list file | ||
| NTF 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. | ||
| NTF 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 | ||
| NTF rmxIsdnServicesConfigurationChangedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5900 | ISDN/PSTN Network Services configuration changed | ||
| NTF 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 | ||
| NTF rmxNoRtmIsdnCardAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5902 | RTM ISDN card not found | ||
| NTF rmxNoClockSourceAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5903 | No clock source | ||
| NTF rmxSingleClockSourceAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5904 | Single clock source | ||
| NTF rmxGkmngrAvfWrongMcuConfigAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5950 | MCU is not configured for AVF gatekeeper mode | ||
| NTF rmxGateKeeperErrorAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.5951 | Gatekeeper failure | ||
| NTF rmxCanNotEstablishConnectionWithApplicationServerAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6000 | Failed to connect to application server | ||
| NTF rmxSystemConfigurationAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6001 | Configuration of external database did not complete. | ||
| NTF rmxExternalDbCertificateErrorAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6002 | Error in external database certificate | ||
| NTF rmxIvrServiceListMissingDefaultServiceAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6050 | No default IVR Service in IVR Services list | ||
| NTF rmxCanNotCreateDefaultProfileAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6051 | Failed to create Default Profile | ||
| NTF 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. | ||
| NTF rmxFailedToConnectRecordingLinkAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6053 | Failed to connect to recording device | ||
| NTF rmxRecordingLinkDisconnecedUnexpectedlyAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6054 | Recording device has disconnected unexpectedly | ||
| NTF rmxSystemBasedModeNotIntializedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6055 | Failed to initialize system base mode | ||
| NTF rmxConfEncryptionErrorAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6056 | Conference Encryption Error | ||
| NTF rmxSnmpAgentInitFailedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6100 | Failure in initialization of SNMP agent. | ||
| NTF rmxRestoreSucceededAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6200 | Restore Succeeded | ||
| NTF rmxRestoreFailedAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.6201 | Restore Failed | ||
| NTF rmxEncryptionServerErrorAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.7010 | Encryption Server Error. Failed to generate the encryption key | ||
| NTF rmxExchangeServerConnectionErrorAlarmFault | 1.3.6.1.4.1.13885.9.1.1.2.2.0.7050 | Unable to connect to Exchange Server. | ||
| NTF rmxNoLicensingAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15001 | License not found | ||
| NTF 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. | ||
| NTF rmxNoIpServiceParamsAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15003 | No IP Network Services defined | ||
| NTF rmxTaskTerminatedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15004 | Task terminated | ||
| NTF rmxCfgChangedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15005 | System Configuration modified | ||
| NTF rmxCfgInvalidAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15006 | Invalid System Configuration | ||
| NTF rmxDebugModeAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15007 | DEBUG mode enabled | ||
| NTF rmxLowProcessMemoryAlertAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15008 | Low Processing Memory | ||
| NTF rmxLowSystemMemoryAlertAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15009 | Low system Memory | ||
| NTF rmxSystemCpuUsageAlertAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15010 | High system CPU usage | ||
| NTF rmxTestErrorAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15011 | Used for testing the Active Alarms mechanism | ||
| NTF rmxSipSecuredCommunicationFailedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15012 | Secured SIP communication failed | ||
| NTF rmxBadFileAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15013 | File error | ||
| NTF rmxHighCpuUsageProcessAlertAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15014 | High CPU utilization | ||
| NTF rmxIdleDeadlineReachedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15016 | Process idle | ||
| NTF rmxStartupConditionConfigurationAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15017 | Internal System configuration during startup | ||
| NTF 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 | ||
| NTF rmxIpVersionChangedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15019 | IP Version has been changed | ||
| NTF rmxNoServiceFoundInDbAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15050 | IP Network Service not found | ||
| NTF rmxNoConnectionWithCsAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15052 | No response from Central Signaling | ||
| NTF rmxCsComponentFatalAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15053 | Central signaling component failure | ||
| NTF rmxCsNotConfiguredAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15054 | Missing Central Signaling configuration | ||
| NTF rmxCsServiceStateFailAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15055 | Central Signaling indicating Faulty status | ||
| NTF rmxCsStartupFailedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15056 | Central Signaling startup failure | ||
| NTF 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 | ||
| NTF rmxIpServiceDeletedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15059 | IP Network Service deleted | ||
| NTF rmxIpServiceChangedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15060 | IP Network Service configuration modified | ||
| NTF rmxCsRecoveryStatusAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15061 | Central Signaling indicating Recovery status | ||
| NTF rmxExternalAlertCsAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15062 | Alarm generated by a Central Signaling component | ||
| NTF rmxProductActivationFailureAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15100 | Product activation failure | ||
| NTF rmxNoManagementIpInterfaceAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15101 | Management Network not configured | ||
| NTF rmxNoTimeConfigurationAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15102 | Error reading MCU time | ||
| NTF rmxMplStartupFailureAuthenticationNotReceivedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15103 | MPL startup failure. Authentication not received. | ||
| NTF rmxMplStartupFailureMngmntIpCnfgNotReceivedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15104 | MPL startup failure. Management Network configuration not received. | ||
| NTF rmxNoDnsConfigurationAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15105 | DNS not configured in IP Network Service | ||
| NTF rmxDnsRegistraionFailedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15106 | Failed to register with DNS server | ||
| NTF rmxFailedToOpenApacheConfigurationFileAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15107 | Failed to open Apache server configuration file | ||
| NTF rmxFailedToSaveApacheConfigurationFileAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15108 | Failed to save Apache server configuration file | ||
| NTF rmxPatchedVersionAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15109 | The software contains patch(es) | ||
| NTF rmxPrivateVersionAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15110 | A private version is loaded | ||
| NTF rmxNtpSyncFailureAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15111 | NTP synchronization failure | ||
| NTF rmxIllegalTimeAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15112 | Invalid date and time | ||
| NTF rmxExternalNtpServersFailureAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15113 | External NTP servers failure | ||
| NTF rmxRunningVersionMismatchesCurrentVersionAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15114 | Fallback version is being used | ||
| NTF rmxIdeNotInDmaModeAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15115 | DMA not supported by IDE device | ||
| NTF rmxBadEthernetSettingsAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15116 | Incorrect Ethernet Settings | ||
| NTF rmxSmartReportErrorsOnHdAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15117 | Smart Report found errors on hard disk | ||
| NTF rmxIllegalMcuVersionAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15118 | Invalid MCU Version | ||
| NTF rmxDebugCfgExistAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15119 | DEBUG mode flags in use | ||
| NTF rmxInstallingNewVersionAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15120 | Version upgrade is in progress | ||
| NTF rmxSshEnabledAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15121 | SSH is enabled | ||
| NTF rmxFailedToValidateCertificateAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15122 | Security mode failed. Error in certificate file. | ||
| NTF rmxCertificateExpiredAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15123 | Security mode failed. Certificate has expired. | ||
| NTF 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. | ||
| NTF rmxCertificateNotValidYetAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15125 | Security mode failed. Certificate not yet valid. | ||
| NTF rmxCertificateGoingToBeExpiredAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15126 | Security mode failed. Certificate is about to expire. | ||
| NTF rmxProductTypeMismatchAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15127 | Product Type mismatch. System is restarting. | ||
| NTF rmxUnknownCpuSlotIdAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15128 | CPU slot ID not identified | ||
| NTF rmxNoFipsTestResultFromEncryptionkeyserverAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15129 | FIPS 140 test result not received | ||
| NTF rmxFipsFailureWithinEncryptionkeyserverAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15130 | FIPS 140 failure | ||
| NTF 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. | ||
| NTF rmxBackupOfCdrFilesIsRequiredAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15140 | Backup of CDR files is required | ||
| NTF rmxNoMusicSourceAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15150 | Music file error | ||
| NTF rmxSwitchNotLoadedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15151 | SWITCH not responding | ||
| NTF rmxNoIsdnServiceParamsAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15152 | No ISDN/PSTN Network Services defined | ||
| NTF rmxModuleDoesNotExistAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15153 | Card not found | ||
| NTF 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 | ||
| NTF rmxExternalAlertEmbAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15155 | Alarm generated by an internal component | ||
| NTF rmxVersionInstallProgressAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15156 | Software upgrade in component | ||
| NTF rmxVersionIpmcInstallProgressAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15157 | IPMC software upgrade in component | ||
| NTF rmxVoltageProblemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15200 | Voltage problem | ||
| NTF rmxTemperatureMajorProblemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15201 | Temperature Level Major | ||
| NTF rmxTemperatureCriticalProblemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15202 | Temperature Level Critical | ||
| NTF rmxFailureProblemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15203 | Card failure | ||
| NTF rmxPowerOffProblemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15204 | Power off | ||
| NTF rmxOtherProblemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15205 | Unspecified problem | ||
| NTF rmxNoConnectionWithCardAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15206 | Card not responding | ||
| NTF rmxUnitNotRespondingAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15207 | Unit not responding | ||
| NTF rmxMediaIpConfigurationFailureAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15208 | Failed to configure the Media card IP address | ||
| NTF rmxCardFolderMountingFailedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15209 | Failed to mount Card folder | ||
| NTF rmxCardStartupFailureAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15211 | Could not complete MPM Card startup procedure | ||
| NTF rmxRtmIsdnStartupFailureAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15212 | Could not complete RTM ISDN Card startup procedure | ||
| NTF rmxRtmIsdnStartupProblemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15213 | RTM ISDN card startup procedure error | ||
| NTF rmxNoConnectionWithRtmIsdnAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15214 | No response from RTM ISDN card | ||
| NTF rmxRedAlarmAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15215 | Red Alarm | ||
| NTF rmxYellowAlarmAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15216 | Yellow Alarm | ||
| NTF rmxDChannelNotEstablishedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15217 | D channel cannot be established | ||
| NTF rmxCardsConfigEventAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15218 | Card configuration event | ||
| NTF rmxCardsWrongFileModeAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15219 | Cards wrong file's mode | ||
| NTF rmxCardsFlashAccessProblemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15220 | Card failed to switch to Enhanced Security Mode | ||
| NTF 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 | ||
| NTF rmxNoLanConnectionAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15222 | No LAN connection | ||
| NTF rmxCanNotEstablishConnectionWithSipRegistrarAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15300 | Failed to connect to SIP registrar | ||
| NTF rmxSipRegistrationLimitReachedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15301 | SIP registrations limit reached | ||
| NTF rmxFailedToAccessDnsServerAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15350 | Failed to access DNS server | ||
| NTF rmxNoIndDnsSuccessAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15351 | DNS configuration error | ||
| NTF rmxFailedToInitFileSystemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15400 | Failed to initialize the file system | ||
| NTF rmxBadFileSystemAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15401 | The Log file system is disabled | ||
| NTF rmxBadHardDiskAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15402 | Hard disk error | ||
| NTF rmxBackupOfLogFilesIsRequiredAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15403 | Backup of log files is required | ||
| NTF rmxBackupOfAuditFilesIsRequiredAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15430 | Backup of audit files is required | ||
| NTF rmxFailedToFillActionRedirectionAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15450 | Action redirection failure | ||
| NTF rmxFailedConfigUserListInLinuxAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15500 | Failed to configure the Users list in Linux | ||
| NTF rmxInsufficientResourcesAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15550 | Insufficient resources | ||
| NTF rmxPortConfigurationChangedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15551 | Port configuration was modified | ||
| NTF rmxNoUtilizableUnitForAudioControllerAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15552 | No usable unit for audio controller | ||
| NTF rmxAllocationModeChangedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15553 | Allocation mode was modified | ||
| NTF rmxProcessTerminatedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15601 | Process terminated | ||
| NTF rmxResetMcuByTerminalAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15602 | Terminal initiated MCU reset | ||
| NTF rmxResetMcuByOperatorAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15603 | User initiated MCU reset | ||
| NTF rmxResetMcuInternalAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15604 | Internal MCU reset | ||
| NTF rmxResetMcuAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15605 | MCU reset | ||
| NTF rmxResetMcuDiagnosticsAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15606 | MCU Reset to enable Diagnostics mode | ||
| NTF rmxProcessStartupFailedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15607 | Startup process failure | ||
| NTF rmxSystemInSafeModeAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15608 | Automatic reset is unavailable in Safe Mode | ||
| NTF rmxGuiSystemConfigIsIllegalAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15609 | GUI System configuration file is invalid xml file | ||
| NTF rmxFileSystemFailedToScanAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15650 | File system scan failure | ||
| NTF rmxFileSystemOverflowAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15651 | File system space shortage | ||
| NTF rmxHardDiskFailureAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15652 | Hard disk error | ||
| NTF rmxCpuIpcmSoftwareIsNotUpdatedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15690 | CPU IPMC software was not updated. | ||
| NTF rmxNewVersionInstalledAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15700 | A new version was installed. Reset the system. | ||
| NTF rmxNewActivationKeyLoadedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15701 | A new activation key was loaded. Reset the system. | ||
| NTF rmxInsufficientUdpPortsAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15751 | Insufficient UDP Ports | ||
| NTF rmxUsersListCorruptedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15800 | Failed to open Users list file | ||
| NTF 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. | ||
| NTF 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 | ||
| NTF rmxIsdnServicesConfigurationChangedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15900 | ISDN/PSTN Network Services configuration changed | ||
| NTF 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 | ||
| NTF rmxNoRtmIsdnCardAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15902 | RTM ISDN card not found | ||
| NTF rmxNoClockSourceAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15903 | No clock source | ||
| NTF rmxSingleClockSourceAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15904 | Single clock source | ||
| NTF rmxGkmngrAvfWrongMcuConfigAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15950 | MCU is not configured for AVF gatekeeper mode | ||
| NTF rmxGateKeeperErrorAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.15951 | Gatekeeper failure | ||
| NTF rmxCanNotEstablishConnectionWithApplicationServerAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16000 | Failed to connect to application server | ||
| NTF rmxSystemConfigurationAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16001 | Configuration of external database did not complete. | ||
| NTF rmxExternalDbCertificateErrorAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16002 | Error in external database certificate | ||
| NTF rmxIvrServiceListMissingDefaultServiceAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16050 | No default IVR Service in IVR Services list | ||
| NTF rmxCanNotCreateDefaultProfileAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16051 | Failed to create Default Profile | ||
| NTF 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. | ||
| NTF rmxFailedToConnectRecordingLinkAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16053 | Failed to connect to recording device | ||
| NTF rmxRecordingLinkDisconnecedUnexpectedlyAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16054 | Recording device has disconnected unexpectedly | ||
| NTF rmxSystemBasedModeNotIntializedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16055 | Failed to initialize system base mode | ||
| NTF rmxConfEncryptionErrorAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16056 | Conference Encryption Error | ||
| NTF rmxSnmpAgentInitFailedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16100 | Failure in initialization of SNMP agent. | ||
| NTF rmxRestoreSucceededAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16200 | Restore Succeeded | ||
| NTF rmxRestoreFailedAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.16201 | Restore Failed | ||
| NTF rmxEncryptionServerErrorAlarmClear | 1.3.6.1.4.1.13885.9.1.1.2.2.0.17010 | Encryption Server Error. Failed to generate the encryption key | ||
| NTF 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 |
RFC description
Monitors Polycom RMX media server conference room utilization, media port availability, and active conference statistics.
Start monitoring Polycom RMX series MCU (video/audio conferencing media server) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.