All MIBs › NBS-MIB
Organization: NBS
Last Updated: 2013-09-17
Category: Hardware Inventory, Products/Registration
Description:
Defines NBS enterprise root OID structure and top-level registration objects.
Imported Objects
From SNMPv2-SMI
| Counter64 | |
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| Unsigned32 | |
| enterprises |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
What Is NBS-MIB?
NBS-MIB defines textual conventions and top-level enterprise OID registration objects for a vendor's 'NBS' MIB family, along with a set of informal naming conventions (e.g. 'Persistent' versus 'Impulse' settings, 'Admin' object naming) used consistently across its dependent MIB modules. It does not itself expose device data; rather it establishes shared type definitions and documentation conventions (persistent/non-volatile configuration semantics versus one-shot 'impulse' actions) that other NBS-family MIBs follow. As a definitional/root module it has no hardware or software status objects of its own to poll for uptime, temperature, or load data. It is a structural and semantic dependency for the whole family of NBS-branded MIB modules, so keeping the NBS-MIB reference at hand is necessary since dependent modules assume its persistent/impulse naming conventions are already understood. It is deployed as a prerequisite compile-time MIB wherever NBS-family network equipment is managed via SNMP.
IPNetwork Monitor allows you to monitor SNMP objects defined in NBS-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
- NBS-family network equipment (vendor-specific)
Monitoring Examples
NBS-MIB has no sample objects because it is a textual-conventions/root module; it defines shared enumerated types and naming conventions ('Persistent' vs. 'Impulse' settings) that dependent NBS-family MIBs apply to their own configuration objects. There is no standalone monitoring scenario for this module — it must be loaded first so that the semantics and types used by the functional NBS MIBs are understood by the polling tool.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| nbs | 1.3.6.1.4.1.629 | Root OID of NBS mibs | ||
| nbsMib | 1.3.6.1.4.1.629.250 | Textual conventions for NBS mibs. Some informal NBS conventions used include the following: A DESCRIPTION specifying 'Persistent' indicates a user- configured attribute that can be stored in the Agent's non-volatile file system as a configuration file such as 'startup-config'. A DESCRIPTION specifying 'Impulse' indicates a user setting that the Agent will immediately attempt but will not store persistently. An object name containing 'Admin' indicates a setting requested by the user which may be overridden by the system. Admin objects should be updated in the Agent immediately, so a GET request immediately after the SET is accepted will be answered with a GET-RESPONSE indicating the new value. An object name containing 'Oper' indicates an attribute's actual state. An object name containing 'Caps' is a bitmask which refers to the capabilities of an entity to support corresponding entries in a specified feature table. |
RFC description
Network-based systems root MIB module serving as foundation for NBS device management extensions including trap control and monitoring objects.
Start monitoring NBS-family network equipment (vendor-specific textual conventions/root) 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.