CM-ENTITY-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsCM-ENTITY-MIB

Organization: ADVA Optical Networking SE

Last Updated: 2021-01-27

Category: Optical and WDM

Description: Provides vendor-specific extensions to the standard ENTITY-MIB for ADVA FSP150CM/CC optical transport product lines, describing physical and logical entities.

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 CM-ENTITY-MIB?

CM-ENTITY-MIB is ADVA's vendor-specific extension to the standard ENTITY-MIB (RFC 2737), tailored for the F3 (FSP150CM/CC) product line of optical transport/carrier Ethernet devices. It exposes a network-element inventory table describing each managed element's name, type, contact, physical location, and free-text description, along with objects tracking whether a discovered element has been accepted into management and what provisioning action applies to it. This makes it primarily an inventory/asset and provisioning-status MIB: it helps confirm which optical transport network elements are known to the management system, where they are located, and whether they've been formally accepted, which is a form of software/management-state monitoring for the device fleet. As an explicit extension of the standard ENTITY-MIB, it depends on and complements that IETF standard's physical-entity model. It is used in service-provider optical/carrier Ethernet transport networks built on ADVA FSP150CM/CC hardware, and an operator loading this module in a CM-ENTITY-MIB MIB Browser session sees the networkElementTable alongside the acceptance and provisioning objects, giving immediate visibility into which nodes are under management.

IPNetwork Monitor allows you to monitor SNMP objects defined in CM-ENTITY-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

  • ADVA FSP150CM optical transport switch
  • ADVA FSP150CC optical transport switch

Monitoring Examples

An operator queries networkElementTable to list managed network elements by neName and neType, and uses neLocation/neContact for asset tracking across a metro optical network. The neAccepted and neProvAction objects indicate whether a newly discovered FSP150 element has been approved into management or is still pending action, which an operator checks when auditing which optical transport nodes are fully under management control after a network expansion.

What Can Be Monitored

  • network element name and type
  • network element location and contact info
  • element management-acceptance status
  • element provisioning action state
Imported Objects

From ADVA-MIB

fsp150cmOBJECT-IDENTITY

From CM-COMMON-MIB

AdminState
CmPmIntervalType
OperationalState
RestartType
SecondaryState
TDMFrequencySourceType
UsbOperationalMode
VlanId

From CM-SYSTEM-MIB

CmAutoProvMode

From ENTITY-MIB

PhysicalIndex

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DateAndTime
DisplayString
RowStatus
StorageType
TEXTUAL-CONVENTION
TruthValue
VariablePointer

How to Use in IPNetwork Monitor

Example using f3StorageDeviceWearoutLevel OID:

Select an ADVA FSP150CM optical transport switch as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type f3StorageDeviceWearoutLevel into the Find box to locate it in the OID tree, then select it and click OK. It reports the wear-out level of the server card's internal SSD. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the wear-out level exceeds 80%, giving you time to plan a card replacement before the SSD reaches end of life. Click Finish to create the monitor; you can adjust any parameter later.

See also: psuOutputVoltage, psuTemperature

OIDs

FAQ

How does CM-ENTITY-MIB help track ADVA FSP150CM/CC network elements under management?
It exposes a network-element inventory table with each element's name, type, contact, physical location, and description, plus objects showing whether a discovered element has been accepted into management, giving an operator immediate visibility into which optical transport nodes are known and managed.

What would I check in CM-ENTITY-MIB if a newly installed FSP150 element isn't showing up as managed?
You'd check the element's management-acceptance status and provisioning-action objects in the network element table -- if the element hasn't been marked as accepted, that explains why it isn't fully under management even though it's been discovered.

RFC description

ADVA vendor-specific extension to ENTITY-MIB (RFC 2737) providing entity management for F3 FSP150CM/CC optical networking product lines.

Start monitoring ADVA/Ceragon FSP150 CM/CC (F3) microwave & Carrier Ethernet transport platform 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.

Download CM-ENTITY-MIB