All MIBs › ERICSSON-ROUTER-IETF-ENTITY-CAP
Organization: Ericsson AB.
Last Updated: 2015-01-14
Category: Standard: IETF, Vendor: Ericsson
Description: Declares Ericsson router agent capabilities for the IETF Entity MIB (RFC 4133).
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 ERICSSON-ROUTER-IETF-ENTITY-CAP?
ERICSSON-ROUTER-IETF-ENTITY-CAP is an Ericsson AGENT-CAPABILITIES MIB that declares how Ericsson router platforms implement the standards-track IETF ENTITY-MIB (RFC 4133), which models physical component inventory (chassis, slots, cards, ports). Rather than defining new managed objects, it lists a series of AGENT-CAPABILITIES statements (eriRouterIetfEntityCap1 through eriRouterIetfEntityCap5), each tied to a specific PRODUCT-RELEASE string (e.g. AOS 5.0.X.X, SEOS 2.0, SEOS 6.2.X for the SmartEdge family, SEOS 6.3.X for SM, SEOS 11.1.x for the Smart Service Router family) and declaring which ENTITY-MIB groups that release SUPPORTS — entityPhysicalGroup, entityGeneralGroup, entityNotificationsGroup, and later entityMappingGroup. The most recent capability statement also documents two VARIATIONs marking entLPPhysicalIndex and entPhysicalChildIndex as not-implemented, telling management systems not to expect those columns. It depends entirely on the base ENTITY-MIB it profiles and on ERICSSON-ROUTER-SMI for its registration point, and is deployed alongside SNMP agents on Ericsson SmartEdge/SM/SSR router platforms to describe their entity-inventory support, per the ERICSSON-ROUTER-IETF-ENTITY-CAP MIB.
IPNetwork Monitor allows you to monitor SNMP objects defined in ERICSSON-ROUTER-IETF-ENTITY-CAP. 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
- Ericsson SmartEdge (MSER), SM, and Smart Service Router (SSR) router families
Monitoring Examples
A network management system reads eriRouterIetfEntityCap5's SUPPORTS clause before polling a Smart Service Router's ENTITY-MIB to know it should expect entityMappingGroup objects but should not query entLPPhysicalIndex or entPhysicalChildIndex, since those are marked not-implemented; polling those unsupported columns anyway would return noSuchObject rather than useful inventory data, a sign the management tool needs to consult the capabilities statement.
What Can Be Monitored
- ENTITY-MIB group support declarations per firmware release
- physical entity group implementation status
- entity notification group implementation status
- entity mapping group implementation status
- unimplemented object variations (entLPPhysicalIndex, entPhysicalChildIndex)
Imported Objects
From ERICSSON-ROUTER-SMI
| eriRouterCapabilities | OBJECT-IDENTITY |
From SNMPv2-CONF
| AGENT-CAPABILITIES |
From SNMPv2-SMI
| MODULE-IDENTITY |
OIDs
RFC description
Ericsson router agent capabilities for ENTITY-MIB implementation on SmartEdge, Metro Ethernet, and Smart Service Router platforms.
Start monitoring Ericsson SmartEdge/SM/SSR platform (Redback Networks heritage) (ENTITY-MIB conformance, RFC 4133) 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.