| OID symbolic | OID numeric | Type | Access | Description |
|---|
| luminous | 1.3.6.1.4.1.4614 | | | |
| lumADM | 1.3.6.1.4.1.4614.1 | | | |
| lumProvisioningMIB | 1.3.6.1.4.1.4614.1.2 | | | The Luminous Provisioning MIB
contains management information
required to provision Luminous
PacketWave ports.
NOTE: additional settings (like
T1 ports setting in DS1 MIB
(RFC2495) ) may be required to
complement the cross-connect
requests in the current MIB. |
| lumTdmCrossConnect | 1.3.6.1.4.1.4614.1.2.2 | | | |
| lumTdmCrossConnectTable | 1.3.6.1.4.1.4614.1.2.2.1 | | not-accessible | The Luminous TDM Cross Connect Table.
This table is used to provision TDM cross connects,
including T1, E1, T3 and E3. |
| lumTdmCrossConnectEntry | 1.3.6.1.4.1.4614.1.2.2.1.1 | | not-accessible | This table can have a variable number of
entries(rows), containing cross-connect
parameters as seen from this side of the
cross-connect.
When started for the very first time
this table is empty (has no rows present).
SNMP manager actions are required to
create or delete rows in the table.
One row typically represents a cross-connect,
as seen from this side of cross-connect.
Once created, a row is saved in non-volatile
memory, and is guarantied to persist after
card/shelf reset or a redundant switchover
occurs.
The lumTdmConnectionStatus object is used
to control the process of dynamic row
creation and removal as described in RFC2579.
Luminous specific adaptation of RFC2579
RowStatus convention follows:
- To create a new cross-connect an SNMP
Manager must in the one SNMP SET request
supply not yet existing instances of at
least those read-create objects that
have no DEFVAL clause specified.
The lumTdmConnectionStatus object's
instance value MUST be either
createAndGo(4) or createAndWait(5).
If the row does not already exist
and request is accepted, the SNMP Agent
will respond with positive response
where it will set the value of
lumTdmConnectionStatus instance equal to
active(1) or notInService(2) respectfully.
- SNMP Manager is allowed to change existing
cross-connect from active(1) to
notInService(2) and vice versa.
- To remove cross-connect completely an SNMP
Manager must in one SNMP SET request
supply desired instance of
lumTdmConnectionStatus with the value of
destroy(6). |
| LUM lumTdmLocalCardSlotId | 1.3.6.1.4.1.4614.1.2.2.1.1.1 | LumSlotNum | read-create | The slot number occupied by a card
on this node containing the port
to be connected. This must be
a valid slot number. |
| LUM lumTdmLocalPortNumber | 1.3.6.1.4.1.4614.1.2.2.1.1.2 | LumPortNum | read-create | The local port number to be connected.
This must be a valid port number. |
| IP lumTdmConnectNodeIP | 1.3.6.1.4.1.4614.1.2.2.1.1.3 | IpAddress | read-create | The IP address of the destination node.
This is only used when the port is using
IP encapsulation. |
| LUM lumTdmConnectCardSlotId | 1.3.6.1.4.1.4614.1.2.2.1.1.4 | LumSlotNum | read-create | The slot number of the card in
the destination node. |
| LUM lumTdmConnectPortNumber | 1.3.6.1.4.1.4614.1.2.2.1.1.5 | LumPortNum | read-create | The port number on the card in the
destination node. |
| I32 lumTdmConnectNumber | 1.3.6.1.4.1.4614.1.2.2.1.1.6 | Integer32 | read-create | An arbitrary positive number the user may
specify as a connection identifier. |
| LUM lumTdmConnectionName | 1.3.6.1.4.1.4614.1.2.2.1.1.7 | LumDescr | read-create | An arbitrary name that the user may
specify as a connection identifier. |
| DAT lumTdmConnectionStartTime | 1.3.6.1.4.1.4614.1.2.2.1.1.8 | DateAndTime | read-create | Currently not used. |
| DAT lumTdmConnectionStopTime | 1.3.6.1.4.1.4614.1.2.2.1.1.9 | DateAndTime | read-create | Currently not used. |
| INT lumTdmConnectConfigParam | 1.3.6.1.4.1.4614.1.2.2.1.1.10 | INTEGER | read-create | pointToPoint(1) - indicates
normal TDM cross-connect;
slc96(2) - no longer supported. |
| TIK lumTdmConnectionUpTime | 1.3.6.1.4.1.4614.1.2.2.1.1.11 | TimeTicks | read-only | The actual time passed since
the connection has been established.
Supplied by the SNMP Agent. |
| ROW lumTdmConnectionStatus | 1.3.6.1.4.1.4614.1.2.2.1.1.12 | RowStatus | read-write | Connection Status. Used to create,
change and remove TDM crossconnect.
The format and usage is described in
RFC2579. Currently only the following
are used :
- active(1) - returned after
successful createAndGo;
also can be set when a change from
notInService(2) is desired.
- notInService(2) - returned after
successful createAndWait(5);
also can be set when a change from
active(1) (disabling) is desired.
- createAndGo(4) for create operation;
when successful the resulting state
will be transitioned into active(1).
- createAndWait(5) - for create only;
when successful the resulting state
will be transitioned into
notInService(2).
- destroy(6) for delete operation.
This object MUST always be present
in any SNMP Manager TDM cross connect
request. |
| LUM lumTdmConnectType | 1.3.6.1.4.1.4614.1.2.2.1.1.13 | LumTdmType | read-only | The type of TDM service being carried. |
| lumDPProvision | 1.3.6.1.4.1.4614.1.2.3 | | | |
| lumDPProvisionTable | 1.3.6.1.4.1.4614.1.2.3.1 | | not-accessible | The Luminous Data Provision Table. |
| lumDPProvisionEntry | 1.3.6.1.4.1.4614.1.2.3.1.1 | | not-accessible | This table can have a variable number of
entries(rows), containing provisioning
parameters as seen from this side of the
cross-connect.
When started for the very first time
this table is empty (has no rows present).
SNMP manager actions are required to
create or delete rows in the table.
One row typically represents a provisioning,
as seen from this of the connection.
Once created, a row is saved in non-volatile
memory, and is guarantied to persist after
card/shelf reset or a redundant switchover
occurs.
The lumDPConnectionStatus object is used
to controls the process of dynamic row
creation, removal and modification,
as described in RFC2579. Luminous specific
adaptation of RFC2579 RowStatus convention
follows:
- To create a new provisioning an SNMP
Manager must in one SNMP SET request
supply not yet existing instances of at
least those read-write and read-create
DEFVAL clause
specified. The lumDPConnectionStatus
object's instance value MUST be either
createAndGo(4) or createAndWait(5).
If the row does not already exist and
request is accepted, the SNMP Agent will
respond with positive response with the
value of lumDPConnectionStatus set to
active(1) or notInService(2) respectfully.
- SNMP Manager is allowed to change existing
provisioning from active(1) to
notInService(2) and vice versa.
- To remove provisioning completely an SNMP
Manager must in one SNMP SET request
supply desired instance of
lumDPConnectionStatus object with the
value of destroy(6). |
| LUM lumDPLocalCardSlotId | 1.3.6.1.4.1.4614.1.2.3.1.1.1 | LumSlotNum | read-create | The slot number occupied by a card
on this node with the port to be
provisioned. SNMP Manager must
supply a valid positive number
for the instance of this object.
SNMP Application writer using
this MIB may consider analyzing the
value of lumShelfType from
LUMINOUS-SHELF-MIB and use internal
knowledge of the layout of that shelf
type to determine the valid slot
values. |
| LUM lumDPLocalPortNumber | 1.3.6.1.4.1.4614.1.2.3.1.1.2 | LumPortNum | read-create | The local port number to be provisioned.
SNMP Manager must supply a valid
positive value to the instance on this
object when establishing provisioning.
SNMP Application writer using this MIB
may consider analyzing the value of
lumCardNumbOfPorts from
LUMINOUS-SHELF-MIB for the card in this
slot to determine a valid range. |
| I32 lumDPConnectNumber | 1.3.6.1.4.1.4614.1.2.3.1.1.3 | Integer32 | read-create | An arbitrary, unique positive number
to distinguish between multiple
provisioning established on the same
local port.
SNMP Provisioning Application is
responsible to supply unique instance
value of this object per a given
lumDPLocalCardSlotId and
lumDPLocalPortNumber pair when
establishing provisioning. |
| IP lumDPConnectNodeIP | 1.3.6.1.4.1.4614.1.2.3.1.1.4 | IpAddress | read-create | The IP address of the connecting node.
When establishing provisioning SNMP
Manager must set the value of the
instance of this objects to an
existing Luminous node'd IP Addess. |
| LUM lumDPConnectCardSlotId | 1.3.6.1.4.1.4614.1.2.3.1.1.5 | LumSlotNum | read-create | The slot number occupied by the card in
the connecting node. SNMP Manager must
supply a valid positive number
for the instance of this object.
Internal knowledge of shelf layout
is required to determine the valid
values. SNMP Application writer using
this MIB may consider analyzing the
value of lumShelfType from
LUMINOUS-SHELF-MIB and use internal
knowledge of that shelf type layout to
determine the valid slot values. |
| LUM lumDPConnectPortNumber | 1.3.6.1.4.1.4614.1.2.3.1.1.6 | LumPortNum | read-create | The remote port number on the card in
the connection node. SNMP Manager must
set this field to a valid positive
value when establishing provisioning.
SNMP Application writer using this MIB
may consider analyzing the value of
lumCardNumbOfPorts from
LUMINOUS-SHELF-MIB for the card in the
slot to determine the valid port values. |
| LUM lumDPConnectionName | 1.3.6.1.4.1.4614.1.2.3.1.1.7 | LumDescr | read-create | An arbitrary name that the user
may wish to specify. |
| DAT lumDPConnectionStartTime | 1.3.6.1.4.1.4614.1.2.3.1.1.8 | DateAndTime | read-create | Currently not used. |
| DAT lumDPConnectionStopTime | 1.3.6.1.4.1.4614.1.2.3.1.1.9 | DateAndTime | read-create | Currently not used. |
| INT lumDPCategory | 1.3.6.1.4.1.4614.1.2.3.1.1.10 | INTEGER | read-create | Provisioning Category. Indicates
the provisioning model. |
| INT lumDPClassOfService | 1.3.6.1.4.1.4614.1.2.3.1.1.11 | INTEGER | read-create | Supported Class of Services. |
| I32 lumDPPeakBandwidth | 1.3.6.1.4.1.4614.1.2.3.1.1.12 | Integer32 | read-create | Peak Bandwidth in Bits/Sec;
-1 indicates autonegotiation
enabled. |
| I32 lumDPSustainedBandwidth | 1.3.6.1.4.1.4614.1.2.3.1.1.13 | Integer32 | read-create | Sustained Bandwidth in in Bits/Sec;
positive number. |
| I32 lumDPMaximumBurstSize | 1.3.6.1.4.1.4614.1.2.3.1.1.14 | Integer32 | read-create | Maximum Burst Size. In bytes.
A positive number. |
| INT lumDPNonConformingAction | 1.3.6.1.4.1.4614.1.2.3.1.1.15 | INTEGER | read-create | Non-Conforming Action.
Indicates rate limiting action. |
| INT lumDPProtectionType | 1.3.6.1.4.1.4614.1.2.3.1.1.16 | INTEGER | read-create | Protection type. protected(2)
provides protection in the
case of ring span failure. |
| I32 lumDPFacilityProtection | 1.3.6.1.4.1.4614.1.2.3.1.1.17 | Integer32 | read-create | TBD. |
| IP lumDPIpPrefix1 | 1.3.6.1.4.1.4614.1.2.3.1.1.18 | IpAddress | read-create | The first IP address to augment
the IP Prefix Table. |
| IP lumDPIpPrefix2 | 1.3.6.1.4.1.4614.1.2.3.1.1.19 | IpAddress | read-create | The second IP address to augment
the IP Prefix Table. |
| IP lumDPIpPrefix3 | 1.3.6.1.4.1.4614.1.2.3.1.1.20 | IpAddress | read-create | The third IP address to augment
the IP Prefix Table. |
| STR lumDPConfigFile | 1.3.6.1.4.1.4614.1.2.3.1.1.21 | DisplayString | read-create | Full qualified path and the
file name of the file on
NMS to contain a large amount
of provisioning data, as
IP Prefixes for Static
IP Provisioning. |
| I32 lumDPVLANId | 1.3.6.1.4.1.4614.1.2.3.1.1.22 | Integer32 | read-create | VLAN Id. TBD. |
| I32 lumDPBufferSize | 1.3.6.1.4.1.4614.1.2.3.1.1.23 | Integer32 | read-create | A positive number.TBD |
| TIK lumDPConnectionUpTime | 1.3.6.1.4.1.4614.1.2.3.1.1.24 | TimeTicks | read-only | The time past since this
provisioning has been
established. Supplied by SNMP
Agent. |
| ROW lumDPConnectionStatus | 1.3.6.1.4.1.4614.1.2.3.1.1.25 | RowStatus | read-write | Connection Status. Used to create,
change and remove Data Port
provisioning.
The format and usage of RowStatus
are described in RFC2579.
The following values are supported:
- active(1) - returned after
successful createAndGo;
also can be set when a change from
notInService(2) is desired.
- notInService(2) - returned after
successful createAndWait(5);
also can be set when a change from
active(1) (disabling) is desired.
- createAndGo(4) for create operation;
when successful the resulting state
will be transitioned into active(1).
- createAndWait(5) - for create only;
when successful the resulting state
will be transitioned into
notInService(2).
- destroy(6) for delete operation.
An instance of this object needs
always to be present in any SNMP
Manager provisioning request. |
