All MIBs › PRIV-VENDORDEF-MIB
Organization: BATM Advanced Communication
Last Updated: 2007-09-29
Category: System Management, Vendor SMI and Registration
Description:
Defines BATM Advanced Communication vendor-specific base OID structure and textual conventions for private enterprise MIBs.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| enterprises |
What Is PRIV-VENDORDEF-MIB?
PRIV-VENDORDEF-MIB is a minimal BATM Advanced Communication (BATM/Telco Systems) enterprise MIB that exists solely to register the vendor's private enterprise OID branch, defining a single MODULE-IDENTITY object (privateVendorOID) anchored at enterprises.738 with no OBJECT-TYPE instances of its own. Rather than modeling any managed data, it establishes the base OID structure and identity/contact metadata (BATM/Telco Systems support contacts for North America, North Europe, and elsewhere) that other BATM vendor-specific MIB modules build upon by extending downward from this root. Because it carries no monitorable objects, it has no direct diagnostic value on its own, but it depends on nothing beyond SNMPv2-SMI's enterprises node and is a prerequisite for correctly resolving OIDs in any other BATM/Telco Systems private MIB. It is deployed conceptually across all BATM Advanced Communication managed devices as the anchor point for their private MIB tree. Anyone browsing OIDs under enterprises.738 will want the PRIV-VENDORDEF-MIB OID list as the starting reference.
IPNetwork Monitor allows you to monitor SNMP objects defined in PRIV-VENDORDEF-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.
What Can Be Monitored
- private enterprise OID root registration (no direct monitorable objects; used for OID resolution only)
Supported Devices
- BATM Advanced Communication / Telco Systems devices (private enterprise OID root only, not a specific hardware family)
Monitoring Examples
An operator resolving an unrecognized OID beginning with 1.3.6.1.4.1.738 loads PRIV-VENDORDEF-MIB to confirm the branch belongs to BATM Advanced Communication, then loads the vendor's device-specific MIB modules that extend this root to decode the remaining OID suffix; an OID under this root with no matching child MIB loaded would explain why a management station shows it as unresolved.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| privateVendorOID | 1.3.6.1.4.1.738 | Vendor Id Definition |
RFC description
BATM vendor-specific MIB defining vendor identifiers for private enterprise extensions.
Start monitoring BATM Advanced Communication / Telco Systems devices (shared OID registration) 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.