LUMINOUS-PROVISIONING-MIB

File: LUMINOUS-PROVISIONING-MIB.mib (30404 bytes)

Imported modules

SNMPv2-SMI RFC1213-MIB SNMPv2-TC
LUMINOUS-TC-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
TimeTicks IpAddress ObjectName
Integer32 Counter32 enterprises
DisplayString RowStatus DateAndTime
LumSlotNum LumPortNum LumName
LumDescr LumTdmType

Defined Types

LumTdmCrossConnectEntry  
SEQUENCE    
  lumTdmLocalCardSlotId LumSlotNum
  lumTdmLocalPortNumber LumPortNum
  lumTdmConnectNodeIP IpAddress
  lumTdmConnectCardSlotId LumSlotNum
  lumTdmConnectPortNumber LumPortNum
  lumTdmConnectNumber Integer32
  lumTdmConnectionName LumDescr
  lumTdmConnectionStartTime DateAndTime
  lumTdmConnectionStopTime DateAndTime
  lumTdmConnectConfigParam INTEGER
  lumTdmConnectionUpTime TimeTicks
  lumTdmConnectionStatus RowStatus
  lumTdmConnectType LumTdmType

LumDPProvisionEntry  
SEQUENCE    
  lumDPLocalCardSlotId LumSlotNum
  lumDPLocalPortNumber LumPortNum
  lumDPConnectNumber Integer32
  lumDPConnectNodeIP IpAddress
  lumDPConnectCardSlotId LumSlotNum
  lumDPConnectPortNumber LumPortNum
  lumDPConnectionName LumDescr
  lumDPConnectionStartTime DateAndTime
  lumDPConnectionStopTime DateAndTime
  lumDPCategory INTEGER
  lumDPClassOfService INTEGER
  lumDPPeakBandwidth Integer32
  lumDPSustainedBandwidth Integer32
  lumDPMaximumBurstSize Integer32
  lumDPNonConformingAction INTEGER
  lumDPProtectionType INTEGER
  lumDPFacilityProtection Integer32
  lumDPIpPrefix1 IpAddress
  lumDPIpPrefix2 IpAddress
  lumDPIpPrefix3 IpAddress
  lumDPConfigFile DisplayString
  lumDPVLANId Integer32
  lumDPBufferSize Integer32
  lumDPConnectionUpTime TimeTicks
  lumDPConnectionStatus RowStatus

Defined Values

luminous 1.3.6.1.4.1.4614
OBJECT IDENTIFIER    

lumADM 1.3.6.1.4.1.4614.1
OBJECT IDENTIFIER    

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.
MODULE-IDENTITY    

lumTdmCrossConnect 1.3.6.1.4.1.4614.1.2.2
OBJECT IDENTIFIER    

lumTdmCrossConnectTable 1.3.6.1.4.1.4614.1.2.2.1
The Luminous TDM Cross Connect Table. This table is used to provision TDM cross connects, including T1, E1, T3 and E3.
OBJECT-TYPE    
  SEQUENCE OF  
    LumTdmCrossConnectEntry

lumTdmCrossConnectEntry 1.3.6.1.4.1.4614.1.2.2.1.1
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).
OBJECT-TYPE    
  LumTdmCrossConnectEntry  

lumTdmLocalCardSlotId 1.3.6.1.4.1.4614.1.2.2.1.1.1
The slot number occupied by a card on this node containing the port to be connected. This must be a valid slot number.
OBJECT-TYPE    
  LumSlotNum  

lumTdmLocalPortNumber 1.3.6.1.4.1.4614.1.2.2.1.1.2
The local port number to be connected. This must be a valid port number.
OBJECT-TYPE    
  LumPortNum  

lumTdmConnectNodeIP 1.3.6.1.4.1.4614.1.2.2.1.1.3
The IP address of the destination node. This is only used when the port is using IP encapsulation.
OBJECT-TYPE    
  IpAddress  

lumTdmConnectCardSlotId 1.3.6.1.4.1.4614.1.2.2.1.1.4
The slot number of the card in the destination node.
OBJECT-TYPE    
  LumSlotNum  

lumTdmConnectPortNumber 1.3.6.1.4.1.4614.1.2.2.1.1.5
The port number on the card in the destination node.
OBJECT-TYPE    
  LumPortNum  

lumTdmConnectNumber 1.3.6.1.4.1.4614.1.2.2.1.1.6
An arbitrary positive number the user may specify as a connection identifier.
OBJECT-TYPE    
  Integer32  

lumTdmConnectionName 1.3.6.1.4.1.4614.1.2.2.1.1.7
An arbitrary name that the user may specify as a connection identifier.
OBJECT-TYPE    
  LumDescr  

lumTdmConnectionStartTime 1.3.6.1.4.1.4614.1.2.2.1.1.8
Currently not used.
OBJECT-TYPE    
  DateAndTime  

lumTdmConnectionStopTime 1.3.6.1.4.1.4614.1.2.2.1.1.9
Currently not used.
OBJECT-TYPE    
  DateAndTime  

lumTdmConnectConfigParam 1.3.6.1.4.1.4614.1.2.2.1.1.10
pointToPoint(1) - indicates normal TDM cross-connect; slc96(2) - no longer supported.
OBJECT-TYPE    
  INTEGER pointToPoint(1), slc96(2)  

lumTdmConnectionUpTime 1.3.6.1.4.1.4614.1.2.2.1.1.11
The actual time passed since the connection has been established. Supplied by the SNMP Agent.
OBJECT-TYPE    
  TimeTicks  

lumTdmConnectionStatus 1.3.6.1.4.1.4614.1.2.2.1.1.12
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.
OBJECT-TYPE    
  RowStatus  

lumTdmConnectType 1.3.6.1.4.1.4614.1.2.2.1.1.13
The type of TDM service being carried.
OBJECT-TYPE    
  LumTdmType  

lumDPProvision 1.3.6.1.4.1.4614.1.2.3
OBJECT IDENTIFIER    

lumDPProvisionTable 1.3.6.1.4.1.4614.1.2.3.1
The Luminous Data Provision Table.
OBJECT-TYPE    
  SEQUENCE OF  
    LumDPProvisionEntry

lumDPProvisionEntry 1.3.6.1.4.1.4614.1.2.3.1.1
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).
OBJECT-TYPE    
  LumDPProvisionEntry  

lumDPLocalCardSlotId 1.3.6.1.4.1.4614.1.2.3.1.1.1
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.
OBJECT-TYPE    
  LumSlotNum  

lumDPLocalPortNumber 1.3.6.1.4.1.4614.1.2.3.1.1.2
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.
OBJECT-TYPE    
  LumPortNum  

lumDPConnectNumber 1.3.6.1.4.1.4614.1.2.3.1.1.3
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.
OBJECT-TYPE    
  Integer32  

lumDPConnectNodeIP 1.3.6.1.4.1.4614.1.2.3.1.1.4
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.
OBJECT-TYPE    
  IpAddress  

lumDPConnectCardSlotId 1.3.6.1.4.1.4614.1.2.3.1.1.5
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.
OBJECT-TYPE    
  LumSlotNum  

lumDPConnectPortNumber 1.3.6.1.4.1.4614.1.2.3.1.1.6
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.
OBJECT-TYPE    
  LumPortNum  

lumDPConnectionName 1.3.6.1.4.1.4614.1.2.3.1.1.7
An arbitrary name that the user may wish to specify.
OBJECT-TYPE    
  LumDescr  

lumDPConnectionStartTime 1.3.6.1.4.1.4614.1.2.3.1.1.8
Currently not used.
OBJECT-TYPE    
  DateAndTime  

lumDPConnectionStopTime 1.3.6.1.4.1.4614.1.2.3.1.1.9
Currently not used.
OBJECT-TYPE    
  DateAndTime  

lumDPCategory 1.3.6.1.4.1.4614.1.2.3.1.1.10
Provisioning Category. Indicates the provisioning model.
OBJECT-TYPE    
  INTEGER wireModel(1), staticIP(2), dynamicIP(3)  

lumDPClassOfService 1.3.6.1.4.1.4614.1.2.3.1.1.11
Supported Class of Services.
OBJECT-TYPE    
  INTEGER bestEffort(1), expressForwarding(2), assuredForwarding(3)  

lumDPPeakBandwidth 1.3.6.1.4.1.4614.1.2.3.1.1.12
Peak Bandwidth in Bits/Sec; -1 indicates autonegotiation enabled.
OBJECT-TYPE    
  Integer32  

lumDPSustainedBandwidth 1.3.6.1.4.1.4614.1.2.3.1.1.13
Sustained Bandwidth in in Bits/Sec; positive number.
OBJECT-TYPE    
  Integer32  

lumDPMaximumBurstSize 1.3.6.1.4.1.4614.1.2.3.1.1.14
Maximum Burst Size. In bytes. A positive number.
OBJECT-TYPE    
  Integer32  

lumDPNonConformingAction 1.3.6.1.4.1.4614.1.2.3.1.1.15
Non-Conforming Action. Indicates rate limiting action.
OBJECT-TYPE    
  INTEGER off(1), markDown(2), drop(3)  

lumDPProtectionType 1.3.6.1.4.1.4614.1.2.3.1.1.16
Protection type. protected(2) provides protection in the case of ring span failure.
OBJECT-TYPE    
  INTEGER unprotected(1), protected(2)  

lumDPFacilityProtection 1.3.6.1.4.1.4614.1.2.3.1.1.17
TBD.
OBJECT-TYPE    
  Integer32  

lumDPIpPrefix1 1.3.6.1.4.1.4614.1.2.3.1.1.18
The first IP address to augment the IP Prefix Table.
OBJECT-TYPE    
  IpAddress  

lumDPIpPrefix2 1.3.6.1.4.1.4614.1.2.3.1.1.19
The second IP address to augment the IP Prefix Table.
OBJECT-TYPE    
  IpAddress  

lumDPIpPrefix3 1.3.6.1.4.1.4614.1.2.3.1.1.20
The third IP address to augment the IP Prefix Table.
OBJECT-TYPE    
  IpAddress  

lumDPConfigFile 1.3.6.1.4.1.4614.1.2.3.1.1.21
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.
OBJECT-TYPE    
  DisplayString  

lumDPVLANId 1.3.6.1.4.1.4614.1.2.3.1.1.22
VLAN Id. TBD.
OBJECT-TYPE    
  Integer32  

lumDPBufferSize 1.3.6.1.4.1.4614.1.2.3.1.1.23
A positive number.TBD
OBJECT-TYPE    
  Integer32  

lumDPConnectionUpTime 1.3.6.1.4.1.4614.1.2.3.1.1.24
The time past since this provisioning has been established. Supplied by SNMP Agent.
OBJECT-TYPE    
  TimeTicks  

lumDPConnectionStatus 1.3.6.1.4.1.4614.1.2.3.1.1.25
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.
OBJECT-TYPE    
  RowStatus