
| PDN-TC | SNMPv2-SMI | SNMPv2-CONF |
| ENTITY-MIB | PDN-HEADER-MIB | SNMPv2-TC |
| 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 | |||
| mpeDevHwControl | 1.3.6.1.4.1.1795.2.24.12.10.1.1 | ||
| OBJECT IDENTIFIER | |||
| mpeDevControlTable | 1.3.6.1.4.1.1795.2.24.12.10.1.1.1 | ||
| A table that contains generic information about Card Control. | |||
| 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. | |||
| 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. The value read from this object is noOp(1). | |||
| OBJECT-TYPE | |||
| ResetStates | |||
| mpeDevFileXferConfig | 1.3.6.1.4.1.1795.2.24.12.10.1.2 | ||
| OBJECT IDENTIFIER | |||
| mpeDevFileXferConfigTable | 1.3.6.1.4.1.1795.2.24.12.10.1.2.1 | ||
| The Paradyne FileXfer Client Config Table. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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. | |||
| 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 | |||
| 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 . | |||
| 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. | |||
| 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. | |||
| OBJECT-TYPE | |||
| TimeTicks | |||
| mpeDevFirmwareControl | 1.3.6.1.4.1.1795.2.24.12.10.1.3 | ||
| OBJECT IDENTIFIER | |||
| 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. | |||
| 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. | |||
| 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). | |||
| 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. | |||
| 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. | |||
| 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. | |||
| OBJECT-TYPE | |||
| INTEGER | active(1), inactive(2) | ||
| mpeConfigChangeMgmt | 1.3.6.1.4.1.1795.2.24.12.10.1.4 | ||
| OBJECT IDENTIFIER | |||
| mpeCCMAutoBackup | 1.3.6.1.4.1.1795.2.24.12.10.1.4.1 | ||
| OBJECT IDENTIFIER | |||
| mpeCCMAutoBackupFixedDay | 1.3.6.1.4.1.1795.2.24.12.10.1.4.1.1 | ||
| This object indicates the days of the week on which fixed schedule automatic backups occur. If all bits are set, backups occur daily. If all bits are off, fixed schedule automatic backups are disabled. | |||
| OBJECT-TYPE | |||
| BITS | sunday(0), monday(1), tuesday(2), wednesday(3), thursday(4), friday(5), saturday(6) | ||
| mpeCCMAutoBackupFixedTime | 1.3.6.1.4.1.1795.2.24.12.10.1.4.1.2 | ||
| This object indicates the time of day, in minutes past midnight, at which automatic backups on a fixed schedule occur. | |||
| OBJECT-TYPE | |||
| Integer32 | 0..1440 | ||
| mpeCCMAutoBackupDynamicTime | 1.3.6.1.4.1.1795.2.24.12.10.1.4.1.3 | ||
| This object indicates the interval (in minutes) after the most recent configuration change, when a card's configuration will be backed up to the MCC Flash File System, when automatic backups are occurring on a dynamic schedule. The minimum non-zero interval is 30 minutes. The maximum interval is 24 hours (1440 minutes). When this object is zero, dynamic backups are disabled. | |||
| OBJECT-TYPE | |||
| Integer32 | 0..1440 | ||
| mpeCCMAutoRestore | 1.3.6.1.4.1.1795.2.24.12.10.1.4.2 | ||
| This object specifies whether the MCC Flash File System will restore stored configuration files to newly inserted cards in the DSLAM. | |||
| OBJECT-TYPE | |||
| SwitchState | |||
| mpeCCMResyncOperation | 1.3.6.1.4.1.1795.2.24.12.10.1.4.3 | ||
| This object contains the operation performed when ResyncState is enabled. The value 'get' retrieves configuration files from the MCC FFS to all the devices. The value 'put' stores all the configuration files on the MCC FFS. | |||
| OBJECT-TYPE | |||
| INTEGER | get(1), put(2) | ||
| mpeCCMResyncState | 1.3.6.1.4.1.1795.2.24.12.10.1.4.4 | ||
| This object allows for an instantaneous 'on-demand' backup or restore of all the device configuration files on a chassis to or from the MCC Flash File System of the DSLAM. Setting the value to 'enabled' commences the resynchronization. The value reverts to 'disabled' upon completion of the resync. | |||
| OBJECT-TYPE | |||
| SwitchState | |||
| mpeDevControlMIBTraps | 1.3.6.1.4.1.1795.2.24.12.10.2 | ||
| OBJECT IDENTIFIER | |||
| mpeDevControlMIBTrapsV2 | 1.3.6.1.4.1.1795.2.24.12.10.2.0 | ||
| The traps for the device control MIB. | |||
| OBJECT-IDENTITY | |||
| 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. | |||
| NOTIFICATION-TYPE | |||
| mpeDevFileXferStatus | |||
| mpeDevFileXferErrorStatus | |||
| mpeDevFileXferOperation | |||
| mpeDevFileXferFileType | |||
| mpeDevFileXferFileName | |||
| mpeDevAutoBackupFailEvent | 1.3.6.1.4.1.1795.2.24.12.10.2.0.2 | ||
| This trap indicates a condition exists, which prevents automated backup of a device's configuration to the Management Controller Card (MCC) Flash File System at a scheduled time. | |||
| NOTIFICATION-TYPE | |||
| entPhysicalIndex | |||
| mpeDevConfigRestoreFailEvent | 1.3.6.1.4.1.1795.2.24.12.10.2.0.3 | ||
| This trap is sent by a device to indicate that an incorrect or incompatible configuration file is being downloaded to the device from the MCC Flash File System. | |||
| NOTIFICATION-TYPE | |||
| entPhysicalIndex | |||
| mpeDevControlMIBGroups | 1.3.6.1.4.1.1795.2.24.12.10.3 | ||
| OBJECT IDENTIFIER | |||
| mpeDevHwControlGroup | 1.3.6.1.4.1.1795.2.24.12.10.3.1 | ||
| Objects necessary to implement minimal hardware control | |||
| OBJECT-GROUP | |||
| mpeDevFileXferConfigGroup | 1.3.6.1.4.1.1795.2.24.12.10.3.2 | ||
| Object group used to implement file transfer functionality | |||
| 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 | |||
| OBJECT-GROUP | |||
| mpeConfigChangeMgmtGroup | 1.3.6.1.4.1.1795.2.24.12.10.3.4 | ||
| Object group used to manage automatic backup and restore of device configuration files. | |||
| OBJECT-GROUP | |||
| mpeDevFileXferEventGroup | 1.3.6.1.4.1.1795.2.24.12.10.3.5 | ||
| Notifications associated with mpeDevFileXferConfigGroup | |||
| NOTIFICATION-GROUP | |||
| mpeCCMEventGroup | 1.3.6.1.4.1.1795.2.24.12.10.3.6 | ||
| Notifications indicating a failure occuring during automated backup or restore of device configuration files. | |||
| NOTIFICATION-GROUP | |||
| DevControlEntry | |||
| SEQUENCE | |||
| ResetStates as mpeDevControlReset | |||
| MpeDevFileXferConfigEntry | |||
| SEQUENCE | |||
| DisplayString as mpeDevFileXferFileName | |||
| INTEGER as mpeDevFileXferCopyProtocol | |||
| INTEGER as mpeDevFileXferFileType | |||
| IpAddress as mpeDevFileXferServerIpAddress | |||
| DisplayString as mpeDevFileXferUserName | |||
| DisplayString as mpeDevFileXferUserPassword | |||
| INTEGER as mpeDevFileXferOperation | |||
| Counter32 as mpeDevFileXferPktsSent | |||
| Counter32 as mpeDevFileXferPktsRecv | |||
| Counter32 as mpeDevFileXferOctetsSent | |||
| Counter32 as mpeDevFileXferOctetsRecv | |||
| OCTET STRING as mpeDevFileXferOwnerString | |||
| INTEGER as mpeDevFileXferStatus | |||
| Integer32 as mpeDevFileXferErrorStatus | |||
| INTEGER as mpeDevFileXferSendEvent | |||
| RowStatus as mpeDevFileXferRowStatus | |||
| TimeTicks as mpeDevFileXferXferTime | |||
| DevFirmwareControlEntry | |||
| SEQUENCE | |||
| Integer32 as mpeDevFirmwareControlIndex | |||
| DisplayString as mpeDevFirmwareControlRelease | |||
| INTEGER as mpeDevFirmwareControlOperStatus | |||
| INTEGER as mpeDevFirmwareControlAdminStatus | |||