OPTIX-SONET-CRS-MIB-V2
File:
OPTIX-SONET-CRS-MIB-V2.mib (9179 bytes)
Imported modules
Imported symbols
Defined Types
RowStatus |
|
Enter the description for the RowStatus TEXTUAL-CONVENTION converted from type assignment. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6) |
|
OptixsonetCrsEntry |
|
SEQUENCE |
|
|
|
|
optixsonetCrsMod2 |
INTEGER |
|
|
optixsonetCrsFrom |
OCTET STRING |
|
|
optixsonetCrsTo |
OCTET STRING |
|
|
optixsonetCrsCct |
INTEGER |
|
|
optixsonetCrsCktId |
OCTET STRING |
|
|
optixsonetCrsPreferredPath |
OCTET STRING |
|
|
optixsonetCrsRDLD |
INTEGER |
|
|
optixsonetCrsActivePath |
OCTET STRING |
|
|
optixsonetCrsRowStatus |
RowStatus |
|
Defined Values
optixsonetCRS |
1.3.6.1.4.1.2011.2.25.4.20.1 |
Enter the description for this MIB module. |
MODULE-IDENTITY |
|
|
|
optixsonetCrsEntry |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1 |
Description. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
OptixsonetCrsEntry |
|
|
optixsonetCrsMod2 |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.1 |
The modifier that identifies the type of STS and VT path |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
crsSTS1(9), crsSTS3C(10), crsSTS6C(11), crsSTS9C(12), crsSTS12C(13), crsSTS24C(15), crsSTS48C(16), crsSTS192C(17), crsVT1(21), crsVT2(22) |
|
optixsonetCrsFrom |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.2 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
Size(0..32) |
|
optixsonetCrsTo |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.3 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
Size(0..32) |
|
optixsonetCrsCct |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.4 |
Cross connect type. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
twoWay(1), oneWay(2) |
|
optixsonetCrsCktId |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.5 |
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. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
Size(0..32) |
|
optixsonetCrsPreferredPath |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.6 |
Preferred path. It is only supplied for UPSR. Two values separated by '&' are applicable to only UPSR with 2 sources and 2 destinations. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
Size(0..32) |
|
optixsonetCrsRDLD |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.7 |
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. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
rdld(1), rdldDEA(2) |
|
optixsonetCrsActivePath |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.8 |
Active path. It is only supplied for UPSR. Two values separated by '&' are applicable to only UPSR with 2 sources and 2 destinations. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
|
|
optixsonetCrsRowStatus |
1.3.6.1.4.1.2011.2.25.4.20.1.3.1.10 |
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'). |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
RowStatus |
|
|
currentObjectGroup |
1.3.6.1.4.1.2011.2.25.4.20.1.4.1.1 |
Enter the description of the created OBJECT-GROUP. |
Status: current |
Access: read-write |
OBJECT-GROUP |
|
|
|
basicCompliance |
1.3.6.1.4.1.2011.2.25.4.20.1.4.2.1 |
Enter the description of the created MODULE-COMPLIANCE. |
Status: current |
Access: read-write |
MODULE-COMPLIANCE |
|
|
|