All MIBs › CYAN-MIB
Organization: Cyan, Inc.
Last Updated: 2014-12-07
Category: Optical and WDM, Vendor: Ciena
Description:
Top-level MIB defining the Cyan optical networking management framework and OID hierarchy.
Imported Objects
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE | |
| enterprises |
From SNMPv2-TC
| DisplayString | |
| TEXTUAL-CONVENTION |
What Is CYAN-MIB?
CYAN-MIB is the top-level MIB module for Cyan Inc.'s (Cyan Optics) packet-optical networking management framework, establishing the overall OID hierarchy and shared conventions used by the vendor's other Cyan-specific MIBs. Rather than exposing individual device sensors directly, it centers on a rich alarm/event model, defining objects for alarm probable cause, severity, source type/address, node name, and reporting timestamp, alongside a generic event-type object. This makes it fundamentally a fault-management MIB: its alarm severity, probable-cause, and state objects are the primary mechanism for monitoring hardware and service faults across a Cyan optical network element. It follows patterns similar to ITU-T/Telcordia alarm/event models common in optical transport equipment and is depended upon by other Cyan product-specific MIBs that extend this common alarm framework. It is deployed in Cyan (later Ciena) packet-optical transport platforms used by service providers for metro/regional optical networking. The CYAN-MIB MIB module is thus best understood as a fault-management framework rather than a raw hardware sensor MIB.
IPNetwork Monitor allows you to monitor SNMP objects defined in CYAN-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
- active alarm severity
- alarm probable cause
- alarm source node/address
- alarm state (raised/cleared)
- alarm reporting timestamp
- general event log
Supported Devices
- Cyan (Ciena) packet-optical transport network element
Monitoring Examples
An NMS subscribed to Cyan alarm notifications would inspect cyanAlarmSeverity and cyanAlarmProbCause to triage an incoming fault, for example a critical-severity alarm pointing to an optical transceiver failure. cyanAlarmSourceAddress and cyanAlarmNodeName identify exactly which network element raised the alarm, while cyanAlarmState and cyanAlarmReportingTimeStamp let an operator track the alarm's raised/cleared lifecycle. cyanEventType provides broader classification for non-alarm events logged by the system.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| cyan | 1.3.6.1.4.1.28533 | Sub-tree for Cyan enterprise OID | ||
| cyanProducts | 1.3.6.1.4.1.28533.1 | This module maps Cyan hardware types to OIDs | ||
| cyanZ77 | 1.3.6.1.4.1.28533.1.1 | |||
| cyanLAMP | 1.3.6.1.4.1.28533.1.2 | |||
| cyanZ33 | 1.3.6.1.4.1.28533.1.3 | |||
| cyanZ22 | 1.3.6.1.4.1.28533.1.5 | |||
| cyanMibModules | 1.3.6.1.4.1.28533.5 | Sub-tree to register MIB modules. | ||
| cyanAlarmMibModule | 1.3.6.1.4.1.28533.5.20 | This is the MIB module for Cyan specific MIBs. | ||
| cyanAlarmObjectTypes | 1.3.6.1.4.1.28533.5.20.20 | Objects that get reported with alarms / traps | ||
| CYA cyanAlarmProbCause | 1.3.6.1.4.1.28533.5.20.20.1 | CyanProbablecauseTc | read-only | Probable cause |
| CYA cyanAlarmProbCauseQualifier | 1.3.6.1.4.1.28533.5.20.20.2 | CyanProbablecausequalifierTc | read-only | A qualifier to uniquely identify the probable cause |
| CYA cyanAlarmSourceType | 1.3.6.1.4.1.28533.5.20.20.3 | CyanTypeTc | read-only | Type of the managed entity that gave rise to the alarm or event |
| STR cyanAlarmSourceAddress | 1.3.6.1.4.1.28533.5.20.20.4 | DisplayString | read-only | AID of the object that gave rise to alarm |
| CYA cyanAlarmState | 1.3.6.1.4.1.28533.5.20.20.5 | CyanAlarmstateTc | read-only | Alarm state |
| ASS cyanAlarmSeverity | 1.3.6.1.4.1.28533.5.20.20.6 | AssignedseverityTTc | read-only | Processed & reported alarm severity |
| I32 cyanAlarmReportingTimeStamp | 1.3.6.1.4.1.28533.5.20.20.7 | Integer32 | read-only | Reporting time stamp in seconds since Jan 1 1970 GMT |
| STR cyanAlarmAdditionalText | 1.3.6.1.4.1.28533.5.20.20.8 | DisplayString | read-only | User-definable text |
| EVE cyanEventType | 1.3.6.1.4.1.28533.5.20.20.9 | EventtypeTc | read-only | Event type name |
| STR cyanEventName | 1.3.6.1.4.1.28533.5.20.20.10 | DisplayString | read-only | Event name |
| CYA cyanEventSourceType | 1.3.6.1.4.1.28533.5.20.20.11 | CyanTypeTc | read-only | Type of the managed entity that gave rise to the alarm or event |
| STR cyanEventSourceAddress | 1.3.6.1.4.1.28533.5.20.20.12 | DisplayString | read-only | AID of the object that gave rise to event |
| I32 cyanEventReportingTimeStamp | 1.3.6.1.4.1.28533.5.20.20.13 | Integer32 | read-only | Reporting time stamp in seconds since Jan 1 1970 GMT |
| STR cyanEventAdditionalText | 1.3.6.1.4.1.28533.5.20.20.14 | DisplayString | read-only | List of attribute names and new values |
| STR cyanEventNodeName | 1.3.6.1.4.1.28533.5.20.20.15 | DisplayString | read-only | NativeEMSName of the node |
| STR cyanAlarmNodeName | 1.3.6.1.4.1.28533.5.20.20.16 | DisplayString | read-only | NativeEMSName of the node |
| STR cyanAlarmSourceDescription | 1.3.6.1.4.1.28533.5.20.20.17 | DisplayString | read-only | Description of the object that gave rise to alarm |
| STR cyanAlarmSourceOSSLabel | 1.3.6.1.4.1.28533.5.20.20.18 | DisplayString | read-only | OSS Lable of the object that gave rise to alarm |
| STR cyanEventSourceDescription | 1.3.6.1.4.1.28533.5.20.20.19 | DisplayString | read-only | Description of the object that gave rise to event |
| STR cyanEventSourceOSSLabel | 1.3.6.1.4.1.28533.5.20.20.20 | DisplayString | read-only | OSS Lable of the object that gave rise to event |
| cyanAlarmObjectGroups | 1.3.6.1.4.1.28533.5.20.21 | Groups of objects that get reported with alarms / traps | ||
| cyanAlarmObjectGroup | 1.3.6.1.4.1.28533.5.20.21.1 | Group of objects that come with alarms | ||
| cyanEventObjectGroup | 1.3.6.1.4.1.28533.5.20.21.2 | Group of objects that come with events | ||
| cyanAlarms | 1.3.6.1.4.1.28533.5.20.30 | traps that can get reported to the manager | ||
| NTF cyanAlarmNa | 1.3.6.1.4.1.28533.5.20.30.1 | NA | ||
| NTF cyanAlarmUnequipped | 1.3.6.1.4.1.28533.5.20.30.2 | UNEQUIPPED | ||
| NTF cyanAlarmEqptRestart | 1.3.6.1.4.1.28533.5.20.30.3 | EQPT_RESTART | ||
| NTF cyanAlarmEqptFail | 1.3.6.1.4.1.28533.5.20.30.4 | EQPT_FAIL | ||
| NTF cyanAlarmEqptDgrade | 1.3.6.1.4.1.28533.5.20.30.5 | EQPT_DGRADE | ||
| NTF cyanAlarmEqptMismtch | 1.3.6.1.4.1.28533.5.20.30.6 | EQPT_MISMTCH | ||
| NTF cyanAlarmEqptUnexpected | 1.3.6.1.4.1.28533.5.20.30.7 | EQPT_UNEXPECTED | ||
| NTF cyanAlarmEqptWarning | 1.3.6.1.4.1.28533.5.20.30.8 | EQPT_WARNING | ||
| NTF cyanAlarmNotConfig | 1.3.6.1.4.1.28533.5.20.30.9 | NOT_CONFIG | ||
| NTF cyanAlarmAutoUpgrade | 1.3.6.1.4.1.28533.5.20.30.12 | AUTO_UPGRADE | ||
| NTF cyanAlarmBatFail | 1.3.6.1.4.1.28533.5.20.30.32 | BAT_FAIL | ||
| NTF cyanAlarmBatDgrade | 1.3.6.1.4.1.28533.5.20.30.33 | BAT_DGRADE | ||
| NTF cyanAlarmTpLol | 1.3.6.1.4.1.28533.5.20.30.50 | TP_LOL | ||
| NTF cyanAlarmPreAmp | 1.3.6.1.4.1.28533.5.20.30.51 | PRE_AMP | ||
| NTF cyanAlarmTpLos | 1.3.6.1.4.1.28533.5.20.30.52 | TP_LOS | ||
| NTF cyanAlarmTpLoc | 1.3.6.1.4.1.28533.5.20.30.53 | TP_LOC | ||
| NTF cyanAlarmTpLof | 1.3.6.1.4.1.28533.5.20.30.54 | TP_LOF | ||
| NTF cyanAlarmTpAis | 1.3.6.1.4.1.28533.5.20.30.55 | TP_AIS | ||
| NTF cyanAlarmTpLom | 1.3.6.1.4.1.28533.5.20.30.56 | TP_LOM | ||
| NTF cyanAlarmTpSf | 1.3.6.1.4.1.28533.5.20.30.57 | TP_SF | ||
| NTF cyanAlarmTpBdi | 1.3.6.1.4.1.28533.5.20.30.58 | TP_BDI | ||
| NTF cyanAlarmTpFdi | 1.3.6.1.4.1.28533.5.20.30.59 | TP_FDI | ||
| NTF cyanAlarmTpPmi | 1.3.6.1.4.1.28533.5.20.30.60 | TP_PMI | ||
| NTF cyanAlarmTpSd | 1.3.6.1.4.1.28533.5.20.30.61 | TP_SD | ||
| NTF cyanAlarmTpRdi | 1.3.6.1.4.1.28533.5.20.30.62 | TP_RDI | ||
| NTF cyanAlarmTpTim | 1.3.6.1.4.1.28533.5.20.30.63 | TP_TIM | ||
| NTF cyanAlarmTpIae | 1.3.6.1.4.1.28533.5.20.30.64 | TP_IAE | ||
| NTF cyanAlarmTpBiae | 1.3.6.1.4.1.28533.5.20.30.65 | TP_BIAE | ||
| NTF cyanAlarmTpOci | 1.3.6.1.4.1.28533.5.20.30.66 | TP_OCI | ||
| NTF cyanAlarmTpLck | 1.3.6.1.4.1.28533.5.20.30.67 | TP_LCK | ||
| NTF cyanAlarmTpLoflom | 1.3.6.1.4.1.28533.5.20.30.68 | TP_LOFLOM | ||
| NTF cyanAlarmTpSsf | 1.3.6.1.4.1.28533.5.20.30.69 | TP_SSF | ||
| NTF cyanAlarmTpOorangeAlm | 1.3.6.1.4.1.28533.5.20.30.70 | TP_OORANGE_ALM | ||
| NTF cyanAlarmTpOorangeWrn | 1.3.6.1.4.1.28533.5.20.30.71 | TP_OORANGE_WRN | ||
| NTF cyanAlarmTpFaclpbk | 1.3.6.1.4.1.28533.5.20.30.72 | TP_FACLPBK | ||
| NTF cyanAlarmTpHighLoss | 1.3.6.1.4.1.28533.5.20.30.73 | TP_HIGH_LOSS | ||
| NTF cyanAlarmTpLowLoss | 1.3.6.1.4.1.28533.5.20.30.74 | TP_LOW_LOSS | ||
| NTF cyanAlarmTpFiber | 1.3.6.1.4.1.28533.5.20.30.75 | TP_FIBER | ||
| NTF cyanAlarmTpPlm | 1.3.6.1.4.1.28533.5.20.30.76 | TP_PLM | ||
| NTF cyanAlarmTpLtc | 1.3.6.1.4.1.28533.5.20.30.77 | TP_LTC | ||
| NTF cyanAlarmTpMsim | 1.3.6.1.4.1.28533.5.20.30.78 | TP_MSIM | ||
| NTF cyanAlarmProtFail | 1.3.6.1.4.1.28533.5.20.30.79 | PROT_FAIL | ||
| NTF cyanAlarmCcm | 1.3.6.1.4.1.28533.5.20.30.80 | CCM | ||
| NTF cyanAlarmTpLfd | 1.3.6.1.4.1.28533.5.20.30.81 | TP_LFD | ||
| NTF cyanAlarmTpLink | 1.3.6.1.4.1.28533.5.20.30.82 | TP_LINK | ||
| NTF cyanAlarmTpGfp | 1.3.6.1.4.1.28533.5.20.30.83 | TP_GFP | ||
| NTF cyanAlarmTpTpt | 1.3.6.1.4.1.28533.5.20.30.84 | TP_TPT | ||
| NTF cyanAlarmGtp | 1.3.6.1.4.1.28533.5.20.30.85 | GTP | ||
| NTF cyanAlarmTpSqm | 1.3.6.1.4.1.28533.5.20.30.86 | TP_SQM | ||
| NTF cyanAlarmTpLoa | 1.3.6.1.4.1.28533.5.20.30.87 | TP_LOA | ||
| NTF cyanAlarmTpLti | 1.3.6.1.4.1.28533.5.20.30.88 | TP_LTI | ||
| NTF cyanAlarmLtm | 1.3.6.1.4.1.28533.5.20.30.89 | LTM | ||
| NTF cyanAlarmAps | 1.3.6.1.4.1.28533.5.20.30.90 | APS | ||
| NTF cyanAlarmTpLop | 1.3.6.1.4.1.28533.5.20.30.91 | TP_LOP | ||
| NTF cyanAlarmTpUneq | 1.3.6.1.4.1.28533.5.20.30.92 | TP_UNEQ | ||
| NTF cyanAlarmCsf | 1.3.6.1.4.1.28533.5.20.30.93 | CSF | ||
| NTF cyanAlarmExmism | 1.3.6.1.4.1.28533.5.20.30.94 | EXMISM | ||
| NTF cyanAlarmUpm | 1.3.6.1.4.1.28533.5.20.30.95 | UPM | ||
| NTF cyanAlarmProtCmd | 1.3.6.1.4.1.28533.5.20.30.96 | PROT_CMD | ||
| NTF cyanAlarmFarendCmd | 1.3.6.1.4.1.28533.5.20.30.97 | FAREND_CMD | ||
| NTF cyanAlarmProtocolErr | 1.3.6.1.4.1.28533.5.20.30.98 | PROTOCOL_ERR | ||
| NTF cyanAlarmLoopback | 1.3.6.1.4.1.28533.5.20.30.99 | LOOPBACK | ||
| NTF cyanAlarmLmm | 1.3.6.1.4.1.28533.5.20.30.100 | LMM | ||
| NTF cyanAlarmDmm | 1.3.6.1.4.1.28533.5.20.30.101 | DMM | ||
| NTF cyanAlarmCommFail | 1.3.6.1.4.1.28533.5.20.30.102 | COMM_FAIL | ||
| NTF cyanAlarmCommDgrade | 1.3.6.1.4.1.28533.5.20.30.103 | COMM_DGRADE | ||
| NTF cyanAlarmPacketLpbk | 1.3.6.1.4.1.28533.5.20.30.104 | PACKET_LPBK | ||
| NTF cyanAlarmXcspktsloss | 1.3.6.1.4.1.28533.5.20.30.105 | XCSPKTSLOSS | ||
| NTF cyanAlarmXcspktserr | 1.3.6.1.4.1.28533.5.20.30.106 | XCSPKTSERR | ||
| NTF cyanAlarmSrcaddrmis | 1.3.6.1.4.1.28533.5.20.30.107 | SRCADDRMIS | ||
| NTF cyanAlarmArp | 1.3.6.1.4.1.28533.5.20.30.108 | ARP | ||
| NTF cyanAlarmTsa | 1.3.6.1.4.1.28533.5.20.30.109 | TSA | ||
| NTF cyanAlarmErpPort | 1.3.6.1.4.1.28533.5.20.30.110 | ERP_PORT | ||
| NTF cyanAlarmTpLoomfi | 1.3.6.1.4.1.28533.5.20.30.111 | TP_LOOMFI | ||
| NTF cyanAlarmSyncFail | 1.3.6.1.4.1.28533.5.20.30.202 | SYNC_FAIL | ||
| NTF cyanAlarmSyncDgrade | 1.3.6.1.4.1.28533.5.20.30.203 | SYNC_DGRADE | ||
| NTF cyanAlarmHoldover | 1.3.6.1.4.1.28533.5.20.30.204 | HOLDOVER | ||
| NTF cyanAlarmXcsholdover | 1.3.6.1.4.1.28533.5.20.30.205 | XCSHOLDOVER | ||
| NTF cyanAlarmSyncExcmdActive | 1.3.6.1.4.1.28533.5.20.30.206 | SYNC_EXCMD_ACTIVE | ||
| NTF cyanAlarmEnvAlm | 1.3.6.1.4.1.28533.5.20.30.302 | ENV_ALM | ||
| NTF cyanAlarmEnvWrn | 1.3.6.1.4.1.28533.5.20.30.303 | ENV_WRN | ||
| NTF cyanAlarmIncmpld | 1.3.6.1.4.1.28533.5.20.30.402 | INCMPLD | ||
| NTF cyanAlarmAdmin | 1.3.6.1.4.1.28533.5.20.30.403 | ADMIN | ||
| NTF cyanEventTca | 1.3.6.1.4.1.28533.5.20.30.10008 | TCA | ||
| cyanAlarmGroup | 1.3.6.1.4.1.28533.5.20.50 | Group of all the alarms that Cyan nodes can send as taps | ||
| cyanAlarmCompliance | 1.3.6.1.4.1.28533.5.20.60 | The basic info needed to be a cyan node wrt traps | ||
| cyanEntityModules | 1.3.6.1.4.1.28533.5.30 | Sub-tree to register Entity modules. |
FAQ
How does CYAN-MIB support fault monitoring on a Cyan packet-optical network element?
It defines an alarm/event model with objects for probable cause, severity, source type/address, node name, and reporting timestamp, plus a generic event-type object, so an operator can identify what's alarming, how severe it is, where it originated, and when it was raised or cleared across the optical network element.
Is CYAN-MIB used to read hardware sensors directly, or something else?
Something else -- it's fundamentally a fault-management framework rather than a raw hardware sensor MIB; actual per-device sensor readings come from other Cyan product-specific MIBs, while CYAN-MIB's alarm severity, probable-cause, and state objects are the primary mechanism for tracking hardware and service faults.
RFC description
Cyan Inc transport equipment management MIB for managing optical and telecom devices.
Start monitoring Cyan (Ciena) packet-optical transport network element (alarm/fault framework) 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.