All MIBs › H3C-IPRAN-DCN-MIB
Organization: Hangzhou H3C Tech. Co., Ltd.
Last Updated: 2013-07-24
Category: Vendor: H3C/HH3C
Description: H3C MIB for IP RAN Data Communication Network (DCN) managing OAM channels in mobile backhaul networks.
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 H3C-IPRAN-DCN-MIB?
H3C-IPRAN-DCN-MIB is an H3C (Chinese networking vendor) MIB for managing the Data Communication Network (DCN) used in IP RAN (mobile backhaul) deployments, providing mechanisms to monitor network elements (NEs) across the IPRAN DCN. It exposes tables identifying each network element by ID, IP address/type, and mask, along with metric and device-type information used for topology and reachability tracking of NEs within the DCN OAM channel. Its monitoring value lies in confirming that each network element in the backhaul network is reachable and correctly identified, effectively tracking connectivity/management-plane health across the mobile backhaul infrastructure rather than exposing per-chassis hardware sensors directly. It is specific to H3C's IPRAN product architecture and works alongside standard IP/routing MIBs for underlying reachability. It is deployed by mobile operators using H3C equipment for IP RAN mobile backhaul transport, where H3C-IPRAN-DCN-MIB SNMP monitoring tracks network element reachability across the dedicated DCN OAM channel.
IPNetwork Monitor allows you to monitor SNMP objects defined in H3C-IPRAN-DCN-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
- H3C IP RAN network element (mobile backhaul equipment)
Monitoring Examples
An administrator would walk h3cIpRanDcnNeInfoTable/h3cIpRanDcnNeInfoEntry, checking h3cIpRanDcnNeInfoNeId against h3cIpRanDcnNeInfoNeIp and h3cIpRanDcnNeInfoDeviceType to build an inventory of network elements reachable via the DCN channel, while h3cIpRanDcnNeNumber gives the total count of managed NEs. A discrepancy between the expected h3cIpRanDcnNeNumber and the actual number of entries in h3cIpRanDcnNeInfoTable, or a missing h3cIpRanDcnNeInfoNeId, would indicate a network element that has dropped off the DCN management channel.
What Can Be Monitored
- network element ID and IP address
- network element device type
- DCN routing metric
- total managed network element count
Imported Objects
From HUAWEI-3COM-OID-MIB
| h3cCommon | OBJECT-IDENTITY |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString | |
| MacAddress | |
| TEXTUAL-CONVENTION |
OIDs
RFC description
Monitors network elements in IP RAN Data Communication Network infrastructure.
Start monitoring H3C IP RAN network element (mobile backhaul DCN) 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.