All MIBs › NOKIA-COMMON-MIB-OID-REGISTRATION-MIB
Category: Network Management
Description:
Defines Nokia common OID registration arcs shared across Nokia enterprise product MIB modules.
Imported Objects
From NOKIA-OID-REGISTRATION-MIB
| ntcCommon | OBJECT-IDENTITY |
What Is NOKIA-COMMON-MIB-OID-REGISTRATION-MIB?
NOKIA-COMMON-MIB-OID-REGISTRATION-MIB is a Nokia enterprise MIB that defines the shared OID (Object Identifier) registration tree used across multiple Nokia product-specific MIB modules. Rather than exposing runtime data itself, it establishes common branches for alarms, alarm traps, trap destination configuration, and agent capability statements that other Nokia MIBs build upon. Its role in monitoring is largely structural: it underpins common alarm and notification objects (ntcCommonAlarm, ntcCommonAlarmTrap) that Nokia devices use to report fault conditions, and a trap destination object (ntcCommonTrapDest) used to configure where SNMP notifications are sent. It is explicitly a dependency root for other Nokia-specific MIB modules (ntcCommonModules, ntcCommonAgentCaps), which import definitions from it. It is deployed wherever Nokia enterprise network equipment (routers, switches, or telecom platforms) is managed via SNMP, forming the registration backbone rather than a standalone monitoring target, and troubleshooting an unfamiliar Nokia alarm object usually starts by tracing its position back to the NOKIA-COMMON-MIB-OID-REGISTRATION-MIB OID tree to confirm its lineage.
IPNetwork Monitor allows you to monitor SNMP objects defined in NOKIA-COMMON-MIB-OID-REGISTRATION-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
- common alarm notifications
- alarm trap generation
- trap destination configuration
Supported Devices
- Nokia network equipment (any product line, shared OID registration tree)
Monitoring Examples
The module exposes common infrastructure objects like ntcCommonAlarm and ntcCommonAlarmTrap, which downstream Nokia device MIBs use to raise standardized alarm notifications, and ntcCommonTrapDest, which configures the destination host for trap delivery. An administrator would not poll this MIB directly for performance data but would rely on its alarm and trap-destination objects being correctly referenced by other Nokia MIBs to ensure fault notifications are routed to the network management station. Because ntcCommonAgentCaps and ntcCommonModules are registration/conformance-oriented, they describe capability statements rather than live counters.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ntcCommonAlarm | 1.3.6.1.4.1.94.1.16.1 | |||
| ntcCommonAlarmTrap | 1.3.6.1.4.1.94.1.16.2 | |||
| ntcCommonTrapDest | 1.3.6.1.4.1.94.1.16.3 | |||
| ntcRS | 1.3.6.1.4.1.94.1.16.4 | |||
| ntcCommonModules | 1.3.6.1.4.1.94.1.16.5 | |||
| ntcHWModule | 1.3.6.1.4.1.94.1.16.5.1 | |||
| ntcNtpModule | 1.3.6.1.4.1.94.1.16.5.2 | |||
| ntcHWUnitTypeModule | 1.3.6.1.4.1.94.1.16.5.3 | |||
| ntcACModule | 1.3.6.1.4.1.94.1.16.5.4 | |||
| ntcGprsTracingModule | 1.3.6.1.4.1.94.1.16.5.5 | |||
| ntcCommonAgentCaps | 1.3.6.1.4.1.94.1.16.6 | |||
| ntcHWAgentCap | 1.3.6.1.4.1.94.1.16.6.1 | |||
| ntcNtpAgentCap | 1.3.6.1.4.1.94.1.16.6.2 | |||
| ntcHWUnitTypeAgentCap | 1.3.6.1.4.1.94.1.16.6.3 | |||
| ntcACAgentCap | 1.3.6.1.4.1.94.1.16.6.4 | |||
| ntcGprsTracingAgentCap | 1.3.6.1.4.1.94.1.16.6.5 | |||
| ntcCommonMibs | 1.3.6.1.4.1.94.1.16.7 | |||
| ntcHWMibs | 1.3.6.1.4.1.94.1.16.7.1 | |||
| ntcNtpMibs | 1.3.6.1.4.1.94.1.16.7.2 | |||
| ntcHWUnitTypeMibs | 1.3.6.1.4.1.94.1.16.7.3 | |||
| ntcACMibs | 1.3.6.1.4.1.94.1.16.7.4 | |||
| ntcGprsTracingMibs | 1.3.6.1.4.1.94.1.16.7.5 | |||
| ntcCommonReqs | 1.3.6.1.4.1.94.1.16.8 | |||
| ntcHWReqs | 1.3.6.1.4.1.94.1.16.8.1 | |||
| ntcNtpReqs | 1.3.6.1.4.1.94.1.16.8.2 | |||
| ntcHWUnitTypeReqs | 1.3.6.1.4.1.94.1.16.8.3 | |||
| ntcACReqs | 1.3.6.1.4.1.94.1.16.8.4 | |||
| ntcGprsTracingReqs | 1.3.6.1.4.1.94.1.16.8.5 |
FAQ
What role does NOKIA-COMMON-MIB-OID-REGISTRATION-MIB play when a Nokia device reports a fault via SNMP?
It underpins the common alarm and notification objects (ntcCommonAlarm, ntcCommonAlarmTrap) that Nokia enterprise equipment uses to report fault conditions, plus a trap-destination object (ntcCommonTrapDest) that configures where those SNMP notifications get sent. So when a Nokia router or switch raises an alarm trap, the shared plumbing for both the alarm representation and its destination configuration traces back to this common module.
Why does almost every Nokia product MIB reference this module even though it isn't itself the thing being monitored?
It establishes the shared OID registration tree -- covering alarms, alarm traps, trap-destination configuration, and agent capability statements -- that other Nokia-specific product MIBs build their own alarm and notification definitions on top of. Rather than each Nokia device MIB reinventing alarm plumbing, they import from this common module, making it the registration backbone across Nokia's enterprise network equipment.
RFC description
Nokia enterprise OID registration root for defining Nokia common MIB branches.
Start monitoring Nokia network equipment (any product line, shared OID registration tree) 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.