PDN-MPE-DEVICE-CONTROL-MIB: View SNMP OID List / Download MIB

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.

A table that contains generic information about Card Control.

A list of information for device Control.

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).

A table containing information to control device specific Self-Test operations.

A list of objects for performing Self-Test operations.

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. Enumeration: 'enableExtendSelfTestAndReset': 2, 'noOp': 1.

The Paradyne FileXfer Client Config Table.

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.

This object contains the name of the filetransfer file.

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. Enumeration: 'ftp': 2, 'tftp': 1.

Specifies the type of file your want to transfer. Enumeration: 'firmware': 1, 'config': 2.

This object contains the file transfer server's IP address.

This object contains the username if a username is needed to login to the server.

This object contains the password if a password is needed to login to the server. This object will return null on a read operation.

This object contains the operation the file transfer wants to perform. Enumeration: 'put': 2, 'get': 1.

This object contains the the number of packets sent to the server at the time of interrogation.

This object contains the the number of packets received from the server at the time of interrogation.

This object contains the the number of octets sent to the server at the time of interrogation.

This object contains the the number of octets received from the server at the time of interrogation.

The entity which currently has the 'ownership' required to invoke the operation on this index.

This object contains the status of the file transfer. Enumeration: 'failure': 3, 'none': 1, 'inprogress': 4, 'success': 2.

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

This object indicates whether or not to send the mpeDevFileXferEvent event trap . Enumeration: 'active': 1, 'inactive': 2.

This object is used to create a new row or delete an existing row in this table.

This object indicates the elapsed time (in hundredths of a second) of the file transfer.

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). Enumeration: 'binary': 2, 'ascii': 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.

The Device Firmware Release entry.

This object is used to index the Firmware table (range 1 to N).

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.

This object indicates whether or not the indexed Firmware entry contains a valid(1) or invalid(2) Firmware. Enumeration: 'unknown': 3, 'valid': 1, 'invalid': 2.

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. Enumeration: 'active': 1, 'inactive': 2.

A table that contains configuration information to perform device specific tests.

A list of configuration information for device specific tests.

This object is used to specify the type of the test to start. Enumeration: 'lampTest': 1.

The test status on the device. This object indicates whether the indexed test is currently active(1) or inactive(2). Enumeration: 'active': 1, 'inactive': 2.

Used to start or stop the indexed test. When read, the value returned will be the next logical command. Enumeration: 'start': 1, 'stop': 2.

The traps for the device control MIB.

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.

Objects necessary to implement minimal hardware control

Object group used to implement file transfer functionality

Object group used to manage firmware releases on devices

Objects necessary to implement device specific tests

Notifications associated with mpeDevFileXferConfigGroup