All MIBs › CRMMISC-MIB
Category: Network Monitoring (RMON)
Description: Provides miscellaneous CRM traffic management system objects for general configuration and status monitoring.
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 CRMMISC-MIB?
CRMMISC-MIB is a vendor MIB providing miscellaneous configuration and status objects for a CRM traffic management system, based on its file-backup and package-memory object naming it appears to belong to telecom/traffic-management shelf equipment (CRM likely denoting a carrier/traffic-management platform rather than customer-relationship software). It exposes a file backup table tracking backup file types, target hard drive/module, backup status, and file names, alongside package memory objects that map memory addresses to specific shelf, package, and processor indices. Its monitoring value centers on software/configuration status: crmFileBupStatus reveals whether a configuration or firmware backup completed successfully or failed, which is important before a shelf reboot or upgrade, while the package memory objects support diagnosing which processor/module owns a given memory region during fault investigation. It sits under the standard org/dod/internet enterprise arborescence with no other apparent standard-MIB dependency called out in the object set. It would be deployed on carrier-grade traffic management or switching shelf equipment where configuration backups and per-processor memory tracking are part of routine operations. Network engineers evaluating or troubleshooting this functionality can download the CRMMISC-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in CRMMISC-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
- NTT BA3000 ATM switch — identified via enterprise OID 210 (NTT), matching the confirmed attribution of the sibling CRMSVC-MIB module in the same private-enterprise family (file backup/package memory objects)
Monitoring Examples
An administrator would walk crmFileBupTable/crmFileBupEntry to check crmFileBupStatus for each configured backup job, confirming crmFileBupName completed writing to the target crmFileBupWriteHd/crmFileBupWriteMod without error. A backup status stuck in a failed or in-progress state would indicate a storage or module problem needing attention before a planned upgrade. The crmPkgMem objects (crmPkgMemShelfIndex, crmPkgMemPkgIndex, crmPkgMemProcessorIndex, crmPkgMemAddress) would be consulted during a fault investigation to map a reported memory address back to a specific processor card in a specific shelf slot.
What Can Be Monitored
- configuration/file backup status
- backup job file type and destination
- package/processor memory address mapping
Imported Objects
From IF-MIB
| InterfaceIndex |
From RFC-1212
| OBJECT-TYPE |
From RFC1155-SMI
| Counter | |
| IpAddress |
From RFC1213-MIB
| DisplayString | |
| ifIndex | |
| mib-2 |
From SNMPv2-TC
| RowStatus | |
| TimeStamp |
OIDs
RFC description
Miscellaneous management objects for BA3000 carrier relay systems including file backup and memory control.
Start monitoring NTT BA3000 ATM switch 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.