PDN-MPE-DEVICE-CONTROL-MIB

File: PDN-MPE-DEVICE-CONTROL-MIB.mib (23442 bytes)

Imported modules

PDN-TC SNMPv2-SMI SNMPv2-CONF
ENTITY-MIB PDN-HEADER-MIB SNMPv2-TC

Imported symbols

ResetStates IpAddress Integer32
Counter32 TimeTicks NOTIFICATION-TYPE
OBJECT-IDENTITY OBJECT-TYPE MODULE-IDENTITY
OBJECT-GROUP NOTIFICATION-GROUP entPhysicalIndex
pdn-mpe RowStatus DisplayString

Defined Types

DevControlEntry  
SEQUENCE    
  mpeDevControlReset ResetStates

DevControlSelfTestEntry  
SEQUENCE    
  mpeDevControlExtendedSelfTest INTEGER

MpeDevControlTestEntry  
SEQUENCE    
  mpeDevControlTestType INTEGER
  mpeDevControlTestStatus INTEGER
  mpeDevControlTestCmd INTEGER

MpeDevFileXferConfigEntry  
SEQUENCE    
  mpeDevFileXferFileName DisplayString
  mpeDevFileXferCopyProtocol INTEGER
  mpeDevFileXferFileType INTEGER
  mpeDevFileXferServerIpAddress IpAddress
  mpeDevFileXferUserName DisplayString
  mpeDevFileXferUserPassword DisplayString
  mpeDevFileXferOperation INTEGER
  mpeDevFileXferPktsSent Counter32
  mpeDevFileXferPktsRecv Counter32
  mpeDevFileXferOctetsSent Counter32
  mpeDevFileXferOctetsRecv Counter32
  mpeDevFileXferOwnerString OCTET STRING
  mpeDevFileXferStatus INTEGER
  mpeDevFileXferErrorStatus Integer32
  mpeDevFileXferSendEvent INTEGER
  mpeDevFileXferRowStatus RowStatus
  mpeDevFileXferXferTime TimeTicks
  mpeDevFileXferFileFormat INTEGER

DevFirmwareControlEntry  
SEQUENCE    
  mpeDevFirmwareControlIndex Integer32
  mpeDevFirmwareControlRelease DisplayString
  mpeDevFirmwareControlOperStatus INTEGER
  mpeDevFirmwareControlAdminStatus INTEGER

Defined Values

mpeDevControl 1.3.6.1.4.1.1795.2.24.12.10
This MIB Module allows a user to reset a device in the DSLAM, as well as perform various operations related to the storage and retrieval of firmware and configuration files on devices.
MODULE-IDENTITY    

mpeDevControlMIBObjects 1.3.6.1.4.1.1795.2.24.12.10.1
OBJECT IDENTIFIER    

mpeDevControlMIBTraps 1.3.6.1.4.1.1795.2.24.12.10.2
OBJECT IDENTIFIER    

mpeDevControlMIBGroups 1.3.6.1.4.1.1795.2.24.12.10.3
OBJECT IDENTIFIER    

mpeDevHwControl 1.3.6.1.4.1.1795.2.24.12.10.1.1
OBJECT IDENTIFIER    

mpeDevFileXferConfig 1.3.6.1.4.1.1795.2.24.12.10.1.2
OBJECT IDENTIFIER    

mpeDevFirmwareControl 1.3.6.1.4.1.1795.2.24.12.10.1.3
OBJECT IDENTIFIER    

mpeDevTestControl 1.3.6.1.4.1.1795.2.24.12.10.1.4
OBJECT IDENTIFIER    

mpeDevControlMIBTrapsV2 1.3.6.1.4.1.1795.2.24.12.10.2.0
The traps for the device control MIB.
Status: current Access: read-only
OBJECT-IDENTITY    

mpeDevControlTable 1.3.6.1.4.1.1795.2.24.12.10.1.1.1
A table that contains generic information about Card Control.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DevControlEntry

mpeDevControlEntry 1.3.6.1.4.1.1795.2.24.12.10.1.1.1.1
A list of information for device Control.
Status: current Access: not-accessible
OBJECT-TYPE    
  DevControlEntry  

mpeDevControlReset 1.3.6.1.4.1.1795.2.24.12.10.1.1.1.1.1
Writing the value reset (2) to this object initiates a Hardware power-on reset of the device. Writing the value resetToFactoryDefaults (3) causes the device to re-configure itself with factory defaults. Writing the value (4) causes the device to re-configure itself with a previously loaded active configuration. The value read from this object is noOp(1).
Status: current Access: read-create
OBJECT-TYPE    
  ResetStates  

mpeDevControlSelfTestTable 1.3.6.1.4.1.1795.2.24.12.10.1.1.2
A table containing information to control device specific Self-Test operations.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DevControlSelfTestEntry

mpeDevControlSelfTestEntry 1.3.6.1.4.1.1795.2.24.12.10.1.1.2.1
A list of objects for performing Self-Test operations.
Status: current Access: not-accessible
OBJECT-TYPE    
  DevControlSelfTestEntry  

mpeDevControlExtendedSelfTest 1.3.6.1.4.1.1795.2.24.12.10.1.1.2.1.1
This object is used to start the extended Power-On Self-Test test. Writing the value enableExtendSelfTestAndReset(2) to this object resets the device and puts it into extended Power-On Self-Test mode. During device initialization, the extended Self-Test would be carried out first and then the device would carry out its normal boot operation. The value read from this object is noOp(1). Writing back the same value, noOp(1) will not start the test. Note that if extended Self-Test fails for some reason, after re-initialization, the value of this object will default to enableExtendSelfTestAndReset(2) again unless the manager explicitly chooses not to do so.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER noOp(1), enableExtendSelfTestAndReset(2)  

mpeDevControlTestTable 1.3.6.1.4.1.1795.2.24.12.10.1.4.3
A table that contains configuration information to perform device specific tests.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    MpeDevControlTestEntry

mpeDevControlTestEntry 1.3.6.1.4.1.1795.2.24.12.10.1.4.3.1
A list of configuration information for device specific tests.
Status: current Access: not-accessible
OBJECT-TYPE    
  MpeDevControlTestEntry  

mpeDevControlTestType 1.3.6.1.4.1.1795.2.24.12.10.1.4.3.1.1
This object is used to specify the type of the test to start.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER lampTest(1)  

mpeDevControlTestStatus 1.3.6.1.4.1.1795.2.24.12.10.1.4.3.1.2
The test status on the device. This object indicates whether the indexed test is currently active(1) or inactive(2).
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER active(1), inactive(2)  

mpeDevControlTestCmd 1.3.6.1.4.1.1795.2.24.12.10.1.4.3.1.3
Used to start or stop the indexed test. When read, the value returned will be the next logical command.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER start(1), stop(2)  

mpeDevFileXferConfigTable 1.3.6.1.4.1.1795.2.24.12.10.1.2.1
The Paradyne FileXfer Client Config Table.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    MpeDevFileXferConfigEntry

mpeDevFileXferConfigEntry 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1
Use of the File Tranfer MIB could be used with other MIBS in the following manner: a) Use another MIB/means to verify available space /make room for a file to be transfered to this device b) Use this MIB to download the file c) Use another MIB/means to select the file you want to make active if your selecting firmware for example. d) Use another MIB/means to reset the device. A management station wishing to initiate a file transfer needs to create an entry in this table. To do so, you must first identify the entPhysicalIndex of the device you intend to do the transfer with. You should then create the associated instance of the row status It must also, either in the same or in successive PDUs, create an instance of mpeDevFileXferFileName, mpeDevFileXferFileType, . mpeDevFileXferServerIpAddress, mpeDevFileXferOperation. It should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created, either by an explicit SNMP set request or by default, the row status should be set to active to initiate the request. Note that this entire procedure may be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted configuration objects. Once the MpeDevFileXferConfigEntry request has been created (i.e. the mpeDevFileXferRowStatus has been made active), the entry cannot be modified - the only operation possible after this is to delete the row. Once the request completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries could be aged out, but an entry will never be deleted within 5 minutes of completing.
Status: current Access: not-accessible
OBJECT-TYPE    
  MpeDevFileXferConfigEntry  

mpeDevFileXferFileName 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.1
This object contains the name of the filetransfer file.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString  

mpeDevFileXferCopyProtocol 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.2
The transfer protocol that should be used to copy the file across the network. If the file transfer is to occur locally on the SNMP agent, the method of transfer is left upto the implementation, and is not restricted to the protocols below.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER tftp(1), ftp(2)  

mpeDevFileXferFileType 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.3
Specifies the type of file your want to transfer.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER firmware(1), config(2)  

mpeDevFileXferServerIpAddress 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.4
This object contains the file transfer server's IP address.
Status: current Access: read-create
OBJECT-TYPE    
  IpAddress  

mpeDevFileXferUserName 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.5
This object contains the username if a username is needed to login to the server.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString  

mpeDevFileXferUserPassword 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.6
This object contains the password if a password is needed to login to the server. This object will return null on a read operation.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString  

mpeDevFileXferOperation 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.7
This object contains the operation the file transfer wants to perform.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER get(1), put(2)  

mpeDevFileXferPktsSent 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.8
This object contains the the number of packets sent to the server at the time of interrogation.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

mpeDevFileXferPktsRecv 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.9
This object contains the the number of packets received from the server at the time of interrogation.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

mpeDevFileXferOctetsSent 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.10
This object contains the the number of octets sent to the server at the time of interrogation.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

mpeDevFileXferOctetsRecv 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.11
This object contains the the number of octets received from the server at the time of interrogation.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

mpeDevFileXferOwnerString 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.12
The entity which currently has the 'ownership' required to invoke the operation on this index.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0..255)  

mpeDevFileXferStatus 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.13
This object contains the status of the file transfer.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER none(1), success(2), failure(3), inprogress(4)  

mpeDevFileXferErrorStatus 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.14
This object contains the reason code of the failure determined in mpeDevFileXferStatus. The reason code are specific to the file transfer protocol. Please refer to the file transfer protocols respective RFC for clarification of the error code value meanings. TFTP Error Codes from rfc 1350 FTP Error Codes from rfc 959
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

mpeDevFileXferSendEvent 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.15
This object indicates whether or not to send the mpeDevFileXferEvent event trap .
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER active(1), inactive(2)  

mpeDevFileXferRowStatus 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.16
This object is used to create a new row or delete an existing row in this table.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

mpeDevFileXferXferTime 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.17
This object indicates the elapsed time (in hundredths of a second) of the file transfer.
Status: current Access: read-only
OBJECT-TYPE    
  TimeTicks  

mpeDevFileXferFileFormat 1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1.18
This object contains the file representation type. A file representation type of ascii implies an ASCII, non-print text file. A file representation type of binary implies an binary image file. The default file representation type is binary(2).
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER ascii(1), binary(2)  

mpeDevFirmwareControlTable 1.3.6.1.4.1.1795.2.24.12.10.1.3.1
A list of the current Firmware Releases and their associated status. Each Firmware Release will be indexed by a number from 1 to N. The user will be able to view the Firmware Release String and Operational Status of the release (valid or invalid) and activate a valid Firmware Release by changing the Administration Status to active.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    DevFirmwareControlEntry

mpeDevFirmwareControlEntry 1.3.6.1.4.1.1795.2.24.12.10.1.3.1.1
The Device Firmware Release entry.
Status: current Access: not-accessible
OBJECT-TYPE    
  DevFirmwareControlEntry  

mpeDevFirmwareControlIndex 1.3.6.1.4.1.1795.2.24.12.10.1.3.1.1.1
This object is used to index the Firmware table (range 1 to N).
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

mpeDevFirmwareControlRelease 1.3.6.1.4.1.1795.2.24.12.10.1.3.1.1.2
This object indicates the Software Release for this Firmware. If the Software Firmware is Operational Status is invalid, the Software Revision Number will be blank.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(1..16)  

mpeDevFirmwareControlOperStatus 1.3.6.1.4.1.1795.2.24.12.10.1.3.1.1.3
This object indicates whether or not the indexed Firmware entry contains a valid(1) or invalid(2) Firmware.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER valid(1), invalid(2), unknown(3)  

mpeDevFirmwareControlAdminStatus 1.3.6.1.4.1.1795.2.24.12.10.1.3.1.1.4
This object indicates whether or not the indexed Firmware entry is active(1) or inactive(2). Writing active(1) will activate that software release and cause the unit to reset (response may timeout). Writing active(1) to a Firmware entry whose mpeDevFirmwareControlOperStatus is invalid will return BAD VALUE. Writing inactive(2) will always return BAD VALUE.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER active(1), inactive(2)  

mpeDevFileXferEvent 1.3.6.1.4.1.1795.2.24.12.10.2.0.1
This trap is to communicate a couple of things about the completion of a file transfer. mpeDevFileXferStatus - Did it complete successfully or not. mpeDevFileXferErrorStatus - If not, what was the error code. mpeDevFileXferOperation - What operation was performed?. mpeDevFileXferFileType - Was it a firmware xfer or config? mpeDevFileXferFileName - The name of the file transfered.
Status: current Access: read-create
NOTIFICATION-TYPE    

mpeDevHwControlGroup 1.3.6.1.4.1.1795.2.24.12.10.3.1
Objects necessary to implement minimal hardware control
Status: current Access: read-create
OBJECT-GROUP    

mpeDevFileXferConfigGroup 1.3.6.1.4.1.1795.2.24.12.10.3.2
Object group used to implement file transfer functionality
Status: current Access: read-create
OBJECT-GROUP    

mpeDevFirmwareControlGroup 1.3.6.1.4.1.1795.2.24.12.10.3.3
Object group used to manage firmware releases on devices
Status: current Access: read-create
OBJECT-GROUP    

mpeDevTestControlGroup 1.3.6.1.4.1.1795.2.24.12.10.3.4
Objects necessary to implement device specific tests
Status: current Access: read-create
OBJECT-GROUP    

mpeDevFileXferEventGroup 1.3.6.1.4.1.1795.2.24.12.10.3.5
Notifications associated with mpeDevFileXferConfigGroup
Status: current Access: read-create
NOTIFICATION-GROUP