OPTIX-SONET-CRS-MIB-V2: View SNMP OID List / Download MIB

VENDOR: HUAWEI


 Home MIB: OPTIX-SONET-CRS-MIB-V2
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, OPTIX-OID-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 optixsonetCRS 1.3.6.1.4.1.2011.2.25.4.20.1
Enter the description for this MIB module.
     optixsonetCrsTable 1.3.6.1.4.1.2011.2.25.4.20.1.3 no-access
Description.
         optixsonetCrsEntry 1.3.6.1.4.1.2011.2.25.4.20.1.3.1 no-access
Description.
             optixsonetCrsMod2 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.1 integer read-only
The modifier that identifies the type of STS and VT path Enumeration: 'crsSTS1': 9, 'crsSTS24C': 15, 'crsSTS192C': 17, 'crsSTS3C': 10, 'crsSTS9C': 12, 'crsSTS6C': 11, 'crsSTS48C': 16, 'crsVT2': 22, 'crsVT1': 21, 'crsSTS12C': 13.
             optixsonetCrsFrom 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.2 octet string read-only
Access identifier. It can be source or destination of cross connection, or any one path of source or destination. It can be null, that means retrieve all cross connection with entered rate level. '&' is allowed.
             optixsonetCrsTo 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.3 octet string read-only
Access identifier identifies the other end of the cross connection. If creating 1-to-N one-way cross-connection, multiple '&' and '&&'are allowed. Else only one '&' is allowed. cannot be null.
             optixsonetCrsCct 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.4 integer read-only
Cross connect type. Enumeration: 'twoWay': 1, 'oneWay': 2.
             optixsonetCrsCktId 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.5 octet string read-write
The circuit identification. It is a string of max length 32 ASCII characters. The circuit identification parameter contains the common language circuit ID or other alias of the circuit being provisioned.
             optixsonetCrsPreferredPath 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.6 octet string read-write
Preferred path. It is only supplied for UPSR. Two values separated by '&' are applicable to only UPSR with 2 sources and 2 destinations.
             optixsonetCrsRDLD 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.7 integer read-write
Redline state.Vaild values are RDLD and RDLDDEA. RDLD This value indicates that the entity is a special (red-lined) circuit. RDLDDEA Deactive RDLD state. Enumeration: 'rdld': 1, 'rdldDEA': 2.
             optixsonetCrsActivePath 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.8 octet string read-only
Active path. It is only supplied for UPSR. Two values separated by '&' are applicable to only UPSR with 2 sources and 2 destinations.
             optixsonetCrsRowStatus 1.3.6.1.4.1.2011.2.25.4.20.1.3.1.10 rowstatus read-write
The RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady').
     optixsonetCRSConformance 1.3.6.1.4.1.2011.2.25.4.20.1.4
         optixsonetCRSGroups 1.3.6.1.4.1.2011.2.25.4.20.1.4.1
             currentObjectGroup 1.3.6.1.4.1.2011.2.25.4.20.1.4.1.1
Enter the description of the created OBJECT-GROUP.
         optixsonetCRSCompliances 1.3.6.1.4.1.2011.2.25.4.20.1.4.2
             basicCompliance 1.3.6.1.4.1.2011.2.25.4.20.1.4.2.1
Enter the description of the created MODULE-COMPLIANCE.