Home/Catalog/LUMINOUS-PROVISIONING-MIB

LUMINOUS-PROVISIONING-MIB

Name: SNMP MIBs and OID Database
Creator: Quadrata FZCO
License: https://opensource.org/licenses/MIT

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.

Main OID:

lumProvisioningMIB.1.3.6.1.4.1.4614.1.2

Objects

Active

Status

Dependencies

Imported Objects

Objects

47 total

Object Name	Syntax	OID
luminous OBJECT IDENTIFIER `.1.3.6.1.4.1.4614`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.4614`
lumADM OBJECT IDENTIFIER `.1.3.6.1.4.1.4614.1`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.4614.1`
lumProvisioningMIBThe 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. MODULE-IDENTITY `.1.3.6.1.4.1.4614.1.2`	MODULE-IDENTITY	`.1.3.6.1.4.1.4614.1.2`
lumTdmCrossConnect OBJECT IDENTIFIER `.1.3.6.1.4.1.4614.1.2.2`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.4614.1.2.2`
lumTdmCrossConnectTableThe Luminous TDM Cross Connect Table. This table is used to provision TDM cross connects, including T1, E1, T3 and E3. SEQUENCE OF LumTdmCrossConnectEntry `.1.3.6.1.4.1.4614.1.2.2.1`	SEQUENCE OF LumTdmCrossConnectEntry	`.1.3.6.1.4.1.4614.1.2.2.1`
lumTdmCrossConnectEntryThis 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). LumTdmCrossConnectEntry `.1.3.6.1.4.1.4614.1.2.2.1.1`	LumTdmCrossConnectEntry	`.1.3.6.1.4.1.4614.1.2.2.1.1`
lumTdmLocalCardSlotIdThe slot number occupied by a card on this node containing the port to be connected. This must be a valid slot number.rw LumSlotNum (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.2.1.1.1`	LumSlotNum (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.2.1.1.1`
lumTdmLocalPortNumberThe local port number to be connected. This must be a valid port number.rw LumPortNum (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.2.1.1.2`	LumPortNum (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.2.1.1.2`
lumTdmConnectNodeIPThe IP address of the destination node. This is only used when the port is using IP encapsulation.rw IpAddress `.1.3.6.1.4.1.4614.1.2.2.1.1.3`	IpAddress	`.1.3.6.1.4.1.4614.1.2.2.1.1.3`
lumTdmConnectCardSlotIdThe slot number of the card in the destination node.rw LumSlotNum (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.2.1.1.4`	LumSlotNum (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.2.1.1.4`
lumTdmConnectPortNumberThe port number on the card in the destination node.rw LumPortNum (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.2.1.1.5`	LumPortNum (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.2.1.1.5`
lumTdmConnectNumberAn arbitrary positive number the user may specify as a connection identifier.rw Integer32 `.1.3.6.1.4.1.4614.1.2.2.1.1.6`	Integer32	`.1.3.6.1.4.1.4614.1.2.2.1.1.6`
lumTdmConnectionNameAn arbitrary name that the user may specify as a connection identifier.rw LumDescr (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.2.1.1.7`	LumDescr (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.2.1.1.7`
lumTdmConnectionStartTimeCurrently not used.rw DateAndTime (SNMPv2-TC) `.1.3.6.1.4.1.4614.1.2.2.1.1.8`	DateAndTime (SNMPv2-TC)	`.1.3.6.1.4.1.4614.1.2.2.1.1.8`
lumTdmConnectionStopTimeCurrently not used.rw DateAndTime (SNMPv2-TC) `.1.3.6.1.4.1.4614.1.2.2.1.1.9`	DateAndTime (SNMPv2-TC)	`.1.3.6.1.4.1.4614.1.2.2.1.1.9`
lumTdmConnectConfigParampointToPoint(1) - indicates normal TDM cross-connect; slc96(2) - no longer supported.rw Enumeration `.1.3.6.1.4.1.4614.1.2.2.1.1.10`	Enumeration	`.1.3.6.1.4.1.4614.1.2.2.1.1.10`
lumTdmConnectionUpTimeThe actual time passed since the connection has been established. Supplied by the SNMP Agent.ro TimeTicks (SNMPv2-SMI) `.1.3.6.1.4.1.4614.1.2.2.1.1.11`	TimeTicks (SNMPv2-SMI)	`.1.3.6.1.4.1.4614.1.2.2.1.1.11`
lumTdmConnectionStatusConnection 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.rw RowStatus (SNMPv2-TC) `.1.3.6.1.4.1.4614.1.2.2.1.1.12`	RowStatus (SNMPv2-TC)	`.1.3.6.1.4.1.4614.1.2.2.1.1.12`
lumTdmConnectTypeThe type of TDM service being carried.ro LumTdmType (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.2.1.1.13`	LumTdmType (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.2.1.1.13`
lumDPProvision OBJECT IDENTIFIER `.1.3.6.1.4.1.4614.1.2.3`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.4614.1.2.3`
lumDPProvisionTableThe Luminous Data Provision Table. SEQUENCE OF LumDPProvisionEntry `.1.3.6.1.4.1.4614.1.2.3.1`	SEQUENCE OF LumDPProvisionEntry	`.1.3.6.1.4.1.4614.1.2.3.1`
lumDPProvisionEntryThis 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). LumDPProvisionEntry `.1.3.6.1.4.1.4614.1.2.3.1.1`	LumDPProvisionEntry	`.1.3.6.1.4.1.4614.1.2.3.1.1`
lumDPLocalCardSlotIdThe 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.rw LumSlotNum (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.3.1.1.1`	LumSlotNum (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.3.1.1.1`
lumDPLocalPortNumberThe 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.rw LumPortNum (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.3.1.1.2`	LumPortNum (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.3.1.1.2`
lumDPConnectNumberAn 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.rw Integer32 `.1.3.6.1.4.1.4614.1.2.3.1.1.3`	Integer32	`.1.3.6.1.4.1.4614.1.2.3.1.1.3`
lumDPConnectNodeIPThe 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.rw IpAddress `.1.3.6.1.4.1.4614.1.2.3.1.1.4`	IpAddress	`.1.3.6.1.4.1.4614.1.2.3.1.1.4`
lumDPConnectCardSlotIdThe 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.rw LumSlotNum (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.3.1.1.5`	LumSlotNum (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.3.1.1.5`
lumDPConnectPortNumberThe 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.rw LumPortNum (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.3.1.1.6`	LumPortNum (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.3.1.1.6`
lumDPConnectionNameAn arbitrary name that the user may wish to specify.rw LumDescr (LUMINOUS-TC-MIB) `.1.3.6.1.4.1.4614.1.2.3.1.1.7`	LumDescr (LUMINOUS-TC-MIB)	`.1.3.6.1.4.1.4614.1.2.3.1.1.7`
lumDPConnectionStartTimeCurrently not used.rw DateAndTime (SNMPv2-TC) `.1.3.6.1.4.1.4614.1.2.3.1.1.8`	DateAndTime (SNMPv2-TC)	`.1.3.6.1.4.1.4614.1.2.3.1.1.8`
lumDPConnectionStopTimeCurrently not used.rw DateAndTime (SNMPv2-TC) `.1.3.6.1.4.1.4614.1.2.3.1.1.9`	DateAndTime (SNMPv2-TC)	`.1.3.6.1.4.1.4614.1.2.3.1.1.9`
lumDPCategoryProvisioning Category. Indicates the provisioning model.rw Enumeration `.1.3.6.1.4.1.4614.1.2.3.1.1.10`	Enumeration	`.1.3.6.1.4.1.4614.1.2.3.1.1.10`
lumDPClassOfServiceSupported Class of Services.rw Enumeration `.1.3.6.1.4.1.4614.1.2.3.1.1.11`	Enumeration	`.1.3.6.1.4.1.4614.1.2.3.1.1.11`
lumDPPeakBandwidthPeak Bandwidth in Bits/Sec; -1 indicates autonegotiation enabled.rw Integer32 `.1.3.6.1.4.1.4614.1.2.3.1.1.12`	Integer32	`.1.3.6.1.4.1.4614.1.2.3.1.1.12`
lumDPSustainedBandwidthSustained Bandwidth in in Bits/Sec; positive number.rw Integer32 `.1.3.6.1.4.1.4614.1.2.3.1.1.13`	Integer32	`.1.3.6.1.4.1.4614.1.2.3.1.1.13`
lumDPMaximumBurstSizeMaximum Burst Size. In bytes. A positive number.rw Integer32 `.1.3.6.1.4.1.4614.1.2.3.1.1.14`	Integer32	`.1.3.6.1.4.1.4614.1.2.3.1.1.14`
lumDPNonConformingActionNon-Conforming Action. Indicates rate limiting action.rw Enumeration `.1.3.6.1.4.1.4614.1.2.3.1.1.15`	Enumeration	`.1.3.6.1.4.1.4614.1.2.3.1.1.15`
lumDPProtectionTypeProtection type. protected(2) provides protection in the case of ring span failure.rw Enumeration `.1.3.6.1.4.1.4614.1.2.3.1.1.16`	Enumeration	`.1.3.6.1.4.1.4614.1.2.3.1.1.16`
lumDPFacilityProtectionTBD.rw Integer32 `.1.3.6.1.4.1.4614.1.2.3.1.1.17`	Integer32	`.1.3.6.1.4.1.4614.1.2.3.1.1.17`
lumDPIpPrefix1The first IP address to augment the IP Prefix Table.rw IpAddress `.1.3.6.1.4.1.4614.1.2.3.1.1.18`	IpAddress	`.1.3.6.1.4.1.4614.1.2.3.1.1.18`
lumDPIpPrefix2The second IP address to augment the IP Prefix Table.rw IpAddress `.1.3.6.1.4.1.4614.1.2.3.1.1.19`	IpAddress	`.1.3.6.1.4.1.4614.1.2.3.1.1.19`
lumDPIpPrefix3The third IP address to augment the IP Prefix Table.rw IpAddress `.1.3.6.1.4.1.4614.1.2.3.1.1.20`	IpAddress	`.1.3.6.1.4.1.4614.1.2.3.1.1.20`
lumDPConfigFileFull 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.rw DisplayString (SNMPv2-TC) `.1.3.6.1.4.1.4614.1.2.3.1.1.21`	DisplayString (SNMPv2-TC)	`.1.3.6.1.4.1.4614.1.2.3.1.1.21`
lumDPVLANIdVLAN Id. TBD.rw Integer32 `.1.3.6.1.4.1.4614.1.2.3.1.1.22`	Integer32	`.1.3.6.1.4.1.4614.1.2.3.1.1.22`
lumDPBufferSizeA positive number.TBDrw Integer32 `.1.3.6.1.4.1.4614.1.2.3.1.1.23`	Integer32	`.1.3.6.1.4.1.4614.1.2.3.1.1.23`
lumDPConnectionUpTimeThe time past since this provisioning has been established. Supplied by SNMP Agent.ro TimeTicks (SNMPv2-SMI) `.1.3.6.1.4.1.4614.1.2.3.1.1.24`	TimeTicks (SNMPv2-SMI)	`.1.3.6.1.4.1.4614.1.2.3.1.1.24`
lumDPConnectionStatusConnection 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.rw RowStatus (SNMPv2-TC) `.1.3.6.1.4.1.4614.1.2.3.1.1.25`	RowStatus (SNMPv2-TC)	`.1.3.6.1.4.1.4614.1.2.3.1.1.25`