All MIBs › TROPIC-SLOT-MIB
Organization: Nokia
Last Updated: 2016-07-13
Category: Nokia Optical Transport
Description:
Covers slot configuration and card occupancy within Nokia Tropic optical transport chassis.
Imported Objects
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From TROPIC-GLOBAL-REG
| tnSlotMIB | OBJECT-IDENTITY |
| tnSlotModules | OBJECT-IDENTITY |
From TROPIC-SHELF-MIB
| tnShelfIndex | OBJECT-TYPE |
From TROPIC-TC
| TropicAdminStateType | |
| TropicOperationalCapabilityType | |
| TropicOperationalStateType | |
| TropicResetType | |
| TropicSlotIndexType | |
| TropicStateQualifierType |
What Is TROPIC-SLOT-MIB?
TROPIC-SLOT-MIB is a vendor-specific Nokia (from Tropic Networks, folded into the Nokia/Alcatel-Lucent optical lineage) MIB module for managing slot-level configuration and card occupancy within an optical transport chassis. It is expected to expose data on which line cards or modules are physically inserted in each chassis slot, their configured/expected card type, and slot-level administrative and operational state. This makes it primarily a hardware-status MIB: it would let an operator detect an empty slot, a card-type mismatch, or a slot reporting a non-operational or failed state within the optical transport shelf. As a chassis/slot management module it likely depends on or parallels ENTITY-MIB conventions for representing physical containment relationships between chassis, slots, and cards. It is deployed on Nokia/Tropic optical transport network equipment in telecom and carrier network environments, and locating the correct TROPIC-SLOT-MIB OID for a given chassis slot is typically the first step in correlating a card-type mismatch or down slot with the physical card actually installed.
IPNetwork Monitor allows you to monitor SNMP objects defined in TROPIC-SLOT-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
- slot occupancy (card present/absent)
- slot configured vs actual card type
- slot administrative status
- slot operational status
Supported Devices
- Nokia/Tropic Networks optical transport chassis
Monitoring Examples
No sample objects were provided for this module, so specific table or column names cannot be confirmed; based on the module's description as 'the slot MIB,' a realistic scenario would involve polling a slot table for the installed card type versus the expected/provisioned type and the slot's operational status. A mismatch, or a slot reporting down/empty when a card should be present, would indicate a card failure, seating problem, or misconfiguration. This should be treated as an inferred scenario rather than one grounded in confirmed object names.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| tnSlotMibModule | 1.3.6.1.4.1.7483.1.1.2.2.2.1 | The slot MIB. | ||
| tnSlotConf | 1.3.6.1.4.1.7483.2.2.2.1.1 | |||
| tnSlotGroups | 1.3.6.1.4.1.7483.2.2.2.1.1.1 | |||
| tnSlotGroup | 1.3.6.1.4.1.7483.2.2.2.1.1.1.1 | |||
| tnSlotResetGroup | 1.3.6.1.4.1.7483.2.2.2.1.1.1.2 | |||
| tnSlotCompliances | 1.3.6.1.4.1.7483.2.2.2.1.1.2 | |||
| tnSlotCompliance | 1.3.6.1.4.1.7483.2.2.2.1.1.2.1 | |||
| tnSlotObjs | 1.3.6.1.4.1.7483.2.2.2.1.2 | |||
| tnSlotBasics | 1.3.6.1.4.1.7483.2.2.2.1.2.2 | |||
| tnSlotTable | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1 | not-accessible | ||
| tnSlotEntry | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1 | not-accessible | ||
| TRO tnSlotIndex | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1.1 | TropicSlotIndexType | not-accessible | |
| OID tnSlotProgrammedType | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1.2 | OBJECT IDENTIFIER | read-create | Type of card to be provisioned in the given Slot. |
| OID tnSlotPresentType | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1.3 | OBJECT IDENTIFIER | read-only | Actual card present in the given slot. |
| TRO tnSlotAdminState | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1.4 | TropicAdminStateType | read-create | |
| TRO tnSlotOperationalState | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1.5 | TropicOperationalStateType | read-only | |
| TRO tnSlotOperationalCapability | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1.6 | TropicOperationalCapabilityType | read-only | |
| TRO tnSlotStateQualifier | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1.7 | TropicStateQualifierType | read-only | |
| OCT tnSlotAlmProfName | 1.3.6.1.4.1.7483.2.2.2.1.2.2.1.1.17 | OCTET STRING | read-create | |
| tnSlotResetTable | 1.3.6.1.4.1.7483.2.2.2.1.2.2.2 | not-accessible | ||
| tnSlotResetEntry | 1.3.6.1.4.1.7483.2.2.2.1.2.2.2.1 | not-accessible | ||
| TRO tnSlotReset | 1.3.6.1.4.1.7483.2.2.2.1.2.2.2.1.1 | TropicResetType | read-create | |
| INT tnSlotResetReason | 1.3.6.1.4.1.7483.2.2.2.1.2.2.2.1.2 | INTEGER | read-only | |
| U32 tnSlotResetTime | 1.3.6.1.4.1.7483.2.2.2.1.2.2.2.1.3 | Unsigned32 | read-only | The last reset time measured in total time ticks (seconds) from the year 1970. This is not supported on fan controllers. |
FAQ
How would TROPIC-SLOT-MIB help identify a card-type mismatch in a Nokia/Tropic optical transport chassis?
It's expected to expose which line cards are physically inserted in each slot, their configured/expected card type, and slot administrative and operational state, letting an operator compare the configured card type against what's actually installed and spot a mismatch or a slot reporting non-operational status.
What would an operator check first when a slot in a Tropic optical shelf reports a problem?
They'd check slot occupancy and operational status to see whether the slot is empty, has a card-type mismatch, or is failed/non-operational, correlating that against the physical card actually installed in the chassis.
RFC description
Manages Nokia Tropic slot configuration and card occupancy in optical transport chassis.
Start monitoring Nokia/Tropic Networks optical transport chassis (slot occupancy/card-type-mismatch 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.