All MIBs › BDCOM-SMI
Organization: BDCom, Inc.
Last Updated: 20000628Z
Category: Device Management, SNMP Framework, Textual Conventions and Registries, Vendor: BDCOM
Description:
Defines the BDCOM Networking enterprise SMI root OID structure used across all BDCOM MIB modules.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| enterprises |
What Is BDCOM-SMI?
BDCOM-SMI defines the BDCOM Networking enterprise Structure of Management Information (SMI) root OID used across all BDCOM MIB modules. Like other enterprise SMI modules, it establishes the organizational OID tree rather than instrumenting any runtime management objects itself. It therefore has no direct role in reporting hardware/software status such as uptime, temperature, or CPU load—that instrumentation resides in the specific BDCOM product MIBs (switches, EPON/GPON OLT equipment) registered beneath this root. Every BDCOM device-specific MIB module depends on this SMI module for its enterprise OID assignment. It is deployed as the structural foundation wherever BDCOM Networking equipment (switches, optical access equipment) is SNMP-managed. Every device-specific object defined by BDCOM registers under the BDCOM-SMI OID root, so identifying a given switch or OLT object always starts by tracing its path back through this enterprise tree.
IPNetwork Monitor allows you to monitor SNMP objects defined in BDCOM-SMI. 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
- BDCOM S9500 — flagship modular data center/campus switch series, up to 56 Tbps switching capacity
- BDCOM S5700-P — multi-gigabit enterprise LAN switch series with Wi-Fi 6 uplink support
Monitoring Examples
This module defines no runtime objects (empty sample_objects), serving purely as the enterprise OID root for BDCOM's MIB suite. An admin would not query BDCOM-SMI directly for monitoring data; actual device status (interface state, optical levels, system health) would be obtained from the specific BDCOM product MIBs registered under this SMI tree.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| bdcom | 1.3.6.1.4.1.3320 | Initial version of this MIB module.The Structure of Management Information for the Bdcom enterprise. | ||
| bdcomProducts | 1.3.6.1.4.1.3320.1 | Bdcom Products is the root OBJECT IDENTIFIER from which sysObjectID values are assigned. | ||
| bdlocal | 1.3.6.1.4.1.3320.2 | Subtree beneath which pre-10.2 MIBS were built. | ||
| bdtemporary | 1.3.6.1.4.1.3320.3 | Subtree beneath which pre-10.2 experiments were placed. | ||
| bdMgmt | 1.3.6.1.4.1.3320.9 | bdMgmt is the main subtree for new mib development. | ||
| bdcomModules | 1.3.6.1.4.1.3320.12 | bdcomModules provides a root object identifier from which MODULE-IDENTITY values may be assigned. | ||
| bdcomPolicyAuto | 1.3.6.1.4.1.3320.18 | bdcomPolicyAuto is the root of the BDCOM-assigned OID subtree for OIDs which are automatically assigned for use in Policy Management. | ||
| bdcomPibToMib | 1.3.6.1.4.1.3320.18.2 | bdcomPibToMib is the root of the BDCOM-assigned OID subtree for MIBs which are algorithmically generated/translated from BDCOM PIBs with OIDs assigned under the bdcomPIB subtree. These generated MIBs allow management entities (other the current Policy Server) to read the downloaded policy. By convention, for PIB 'bdcomPIB.x', the generated MIB shall have the name 'bdcomPibToMib.x'. |
RFC description
Enterprise Structure of Management Information (SMI) for Shanghai Baud Data Communication (BDCOM) with OID root 1.3.6.1.4.1.3320.
Start monitoring BDCOM S9500/S5700-P switches 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.