Internal System configuration during startup
Parsed from file POLYCOM-RMX-MIB.mib
Module: POLYCOM-RMX-MIB
Vendor: Polycom, Inc.
Module: POLYCOM-RMX-MIB
[Automatically extracted from oidview.com]
rmxStartupConditionConfigurationAlarmClear NOTIFICATION-TYPE OBJECTS { rmxAlarmDescription , rmxActiveAlarmDateAndTime, rmxActiveAlarmIndex , rmxActiveAlarmListName , rmxActiveAlarmRmxStatus } STATUS current DESCRIPTION "Internal System configuration during startup" ::= { rmxTraps 15017 }
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15001 | rmxNoLicensingAlarmClear | 0 | 0 | License not found |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15002 | rmxNoMeetingRoomAlarmClear | 0 | 0 | Resource process did not receive the Meeting Room list during startup. |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15003 | rmxNoIpServiceParamsAlarmClear | 0 | 0 | No IP Network Services defined |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15004 | rmxTaskTerminatedAlarmClear | 0 | 0 | Task terminated |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15005 | rmxCfgChangedAlarmClear | 0 | 0 | System Configuration modified |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15006 | rmxCfgInvalidAlarmClear | 0 | 0 | Invalid System Configuration |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15007 | rmxDebugModeAlarmClear | 0 | 0 | DEBUG mode enabled |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15008 | rmxLowProcessMemoryAlertAlarmClear | 0 | 0 | Low Processing Memory |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15009 | rmxLowSystemMemoryAlertAlarmClear | 0 | 0 | Low system Memory |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15010 | rmxSystemCpuUsageAlertAlarmClear | 0 | 0 | High system CPU usage |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15011 | rmxTestErrorAlarmClear | 0 | 0 | Used for testing the Active Alarms mechanism |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15012 | rmxSipSecuredCommunicationFailedAlarmClear | 0 | 0 | Secured SIP communication failed |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15013 | rmxBadFileAlarmClear | 0 | 0 | File error |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15014 | rmxHighCpuUsageProcessAlertAlarmClear | 0 | 0 | High CPU utilization |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15016 | rmxIdleDeadlineReachedAlarmClear | 0 | 0 | Process idle |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15018 | rmxRestoringDefaultFactoryAlarmClear | 0 | 0 | Restoring Factory Defaults. Default system settings will be restored once Reset is completed |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15019 | rmxIpVersionChangedAlarmClear | 0 | 0 | IP Version has been changed |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15050 | rmxNoServiceFoundInDbAlarmClear | 0 | 0 | IP Network Service not found |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15052 | rmxNoConnectionWithCsAlarmClear | 0 | 0 | No response from Central Signaling |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15053 | rmxCsComponentFatalAlarmClear | 0 | 0 | Central signaling component failure |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15054 | rmxCsNotConfiguredAlarmClear | 0 | 0 | Missing Central Signaling configuration |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15055 | rmxCsServiceStateFailAlarmClear | 0 | 0 | Central Signaling indicating Faulty status |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15056 | rmxCsStartupFailedAlarmClear | 0 | 0 | Central Signaling startup failure |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15058 | rmxDuplicateIpCsMngmntAlarmClear | 0 | 0 | IP addresses of Signaling Host and Control Unit are the same |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15059 | rmxIpServiceDeletedAlarmClear | 0 | 0 | IP Network Service deleted |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15060 | rmxIpServiceChangedAlarmClear | 0 | 0 | IP Network Service configuration modified |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15061 | rmxCsRecoveryStatusAlarmClear | 0 | 0 | Central Signaling indicating Recovery status |
| 1.3.6.1.4.1.13885.9.1.1.2.2.0.15062 | rmxExternalAlertCsAlarmClear | 0 | 0 | Alarm generated by a Central Signaling component |
| ... | ||||