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

VENDOR: PARADYNE


 Home MIB: PDN-CONTROL-MIB
Download as:   
SNMPv2-CONF, IF-MIB, SNMPv2-SMI, PDN-TC, PDN-HEADER-MIB, ENTITY-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 pdnControl 1.3.6.1.4.1.1795.2.24.2.10
This MIB Module allow 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.
       pdnControlMIBTrapsV2 1.3.6.1.4.1.1795.2.24.2.10.0
The traps for the device control MIB.
           devFileXferEvent 1.3.6.1.4.1.1795.2.24.2.10.0.1
This trap is to communicate a couple of things about the completion of a file transfer. devFileXferStatus - Did it complete successfully or not. devFileXferErrorStatus - If not, what was the error code. devFileXferOperation - What operation was performed?. devFileXferFileType - Was it a firmware xfer or config? devFileXferFileName - The name of the file transfered.
           devAutoBackupFailEvent 1.3.6.1.4.1.1795.2.24.2.10.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.
           devConfigRestoreFailEvent 1.3.6.1.4.1.1795.2.24.2.10.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.
           devAutoFwEvent 1.3.6.1.4.1.1795.2.24.2.10.0.4
This trap is to communicate the result of the Auto Firmware Download. The variable binding for this trap would be the devAutoFwStatus of pdnAutoFwGroup. The exact format of this display string will be well-documented.
           pdnDevFileXferEvent 1.3.6.1.4.1.1795.2.24.2.10.0.5
This trap is to communicate a couple of things about the completion of a file transfer. pdnDevFileXferStatus - Did it complete successfully or not. pdnDevFileXferErrorStatus - If not, what was the error code. pdnDevFileXferOperation - What operation was performed?. pdnDevFileXferFileType - Was it a firmware xfer or config? pdnDevFileXferFileName - The name of the file transfered.
       devHWControlReset 1.3.6.1.4.1.1795.2.24.2.10.1 integer read-write
Writing the value reset(2) to this object initiates a Hardware power-on reset of the device. The value read from this object is noOp(1). Enumeration: 'reset': 2, 'noOp': 1.
       devControlTestTable 1.3.6.1.4.1.1795.2.24.2.10.2 no-access
A list of Device tests that may be run.
           devControlTestEntry 1.3.6.1.4.1.1795.2.24.2.10.2.1 no-access
The device Test Table.
               devControlTest 1.3.6.1.4.1.1795.2.24.2.10.2.1.1 integer read-only
An index into the test table that indicates which test the row involves. Enumeration: 'v35DTELpbkTest': 2, 'lampTest': 1.
               devControlTestStatus 1.3.6.1.4.1.1795.2.24.2.10.2.1.2 integer read-only
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.
               devControlTestCmd 1.3.6.1.4.1.1795.2.24.2.10.2.1.3 integer read-only
Used to start or stop the indexed test. When read, the value returned will be the next logical command. Enumeration: 'start': 1, 'stop': 2.
       devControlDownLoadTable 1.3.6.1.4.1.1795.2.24.2.10.3 no-access
A list of the current Download Releases and their associated status. Each Download Release will be indexed by a number from 1 to N. The user will be able to view the Download Release String and Operational Status of the release (valid or invalid) and activate a valid Download Release by changing the Administration Status to active.
           devControlDownLoadEntry 1.3.6.1.4.1.1795.2.24.2.10.3.1 no-access
The Device DownLoad Release entry.
               devControlDownLoadIndex 1.3.6.1.4.1.1795.2.24.2.10.3.1.1 integer32 read-only
This object is used to index the download table (range 1 to N).
               devControlDownLoadRelease 1.3.6.1.4.1.1795.2.24.2.10.3.1.2 displaystring read-only
This object indicates the Software Release for this Download. If the Software Download is Operational Status is invalid, the Software Revision Number will be blank.
               devControlDownLoadOperStatus 1.3.6.1.4.1.1795.2.24.2.10.3.1.3 integer read-only
This object indicates whether or not the indexed download entry contains a valid(1) or invalid(2) download. Enumeration: 'valid': 1, 'invalid': 2.
               devControlDownLoadAdminStatus 1.3.6.1.4.1.1795.2.24.2.10.3.1.4 integer read-only
This object indicates whether or not the indexed download 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 download entry whose devControlDownloadOperStatus is invalid will return BAD VALUE. Writing inactive(2) will always return BAD VALUE. Enumeration: 'active': 1, 'inactive': 2.
       devControlRMON 1.3.6.1.4.1.1795.2.24.2.10.4
           devControlRMONAdminStatus 1.3.6.1.4.1.1795.2.24.2.10.4.1 integer read-write
The desired state of the RMON process. If set to enabled(1), the RMON process will perform the collection tasks it is set up to do. If it is disabled(2), RMON will not perform collection. Enumeration: 'disabled': 2, 'enabled': 1.
       devSNSwitchFirmwareTable 1.3.6.1.4.1.1795.2.24.2.10.5 no-access
A list of objects needed to switch bank and reset the Service Node (ASN).
           devSNSwitchFirmwareEntry 1.3.6.1.4.1.1795.2.24.2.10.5.1 no-access
The Service Node Switch Firmware table.
               devSNSwitchFirmwareIndex 1.3.6.1.4.1.1795.2.24.2.10.5.1.1 integer32 read-only
An index into the Service Node switch firmware table that indicates which interface the row involves. This index corresponds to the entityPhysicalIndex of the entity MIB
               devSNSwitchFirmwareBank 1.3.6.1.4.1.1795.2.24.2.10.5.1.2 integer read-only
Writing the value switch(2) to this object will switch the banks to change the firmware being used on the service node. The firmware from the stand by (not active) bank will be used as the currently running firmware. The value read from this object is noOp(1). Enumeration: 'switch': 2, 'noOp': 1.
       devControlFTP 1.3.6.1.4.1.1795.2.24.2.10.6
           devControlFTPRate 1.3.6.1.4.1.1795.2.24.2.10.6.1 integer32 read-write
FTP max transfer rate in (Kbps)
       devFileXferMIBObjects 1.3.6.1.4.1.1795.2.24.2.10.7
           devFileXferConfigTable 1.3.6.1.4.1.1795.2.24.2.10.7.1 no-access
The Paradyne FileXfer Client Config Table.
               devFileXferConfigEntry 1.3.6.1.4.1.1795.2.24.2.10.7.1.1 no-access
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 ifIndex 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 devFileXferFileName, DevFileXferFileType, . devFileXferServerIpAddress, devFileXferOperation. 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 DevFileXferConfigEntry request has been created (i.e. the devFileXferRowStatus 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.
                   devFileXferFileName 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.1 displaystring read-only
This object contains the name of the filetransfer file.
                   devFileXferCopyProtocol 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.2 integer read-only
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.
                   devFileXferFileType 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.3 integer read-only
Specifies the type of file your want to transfer. Enumeration: 'firmware': 1, 'config': 2.
                   devFileXferServerIpAddress 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.4 ipaddress read-only
This object contains the file transfer server's IP address.
                   devFileXferUserName 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.5 displaystring read-only
This object contains the username if a username is needed to login to the server.
                   devFileXferUserPassword 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.6 displaystring read-only
This object contains the password if a password is needed to login to the server. This object will return null on a read operation.
                   devFileXferOperation 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.7 integer read-only
This object contains the operation the file transfer wants to perform. Enumeration: 'put': 2, 'get': 1.
                   devFileXferPktsSent 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.8 counter32 read-only
This object contains the the number of packets sent to the server at the time of interrogation.
                   devFileXferPktsRecv 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.9 counter32 read-only
This object contains the the number of packets received from the server at the time of interrogation.
                   devFileXferOctetsSent 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.10 counter32 read-only
This object contains the the number of octets sent to the server at the time of interrogation.
                   devFileXferOctetsRecv 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.11 counter32 read-only
This object contains the the number of octets received from the server at the time of interrogation.
                   devFileXferOwnerString 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.12 octet string read-only
The entity which currently has the 'ownership' required to invoke the operation on this index.
                   devFileXferStatus 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.13 integer read-only
This object contains the status of the file transfer. Enumeration: 'failure': 3, 'none': 1, 'inprogress': 4, 'success': 2.
                   devFileXferErrorStatus 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.14 integer32 read-only
This object contains the reason code of the failure determined in devFileXferStatus. 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
                   devFileXferSendEvent 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.15 integer read-only
This object indicates whether or not to send the devFileXferEvent event trap . Enumeration: 'active': 1, 'inactive': 2.
                   devFileXferRowStatus 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.16 rowstatus read-only
This object is used to create a new row or delete an existing row in this table.
                   devFileXferXferTime 1.3.6.1.4.1.1795.2.24.2.10.7.1.1.17 timeticks read-only
This object indicates the elapsed time (in hundredths of a second) of the file transfer.
           pdnDevFileXferTable 1.3.6.1.4.1.1795.2.24.2.10.7.2 no-access
The Paradyne FileXfer Image Client Config Table accessed by session id.
               pdnDevFileXferEntry 1.3.6.1.4.1.1795.2.24.2.10.7.2.1 no-access
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 object/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 session id of the session that the transfer is done with. This is done by setting SessionID to 0 on SET and when session is establish entering that session id into this object. 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 pdnDevFileXferFileName, pdnDevFileXferFileType, . pdnDevFileXferServerIpAddress, pdnDevFileXferOperation. 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 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.
                   pdnDevFileXferSessionID 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.1 integer32 no-access
This object is the session id. This object is used by FileXfer Table to identify the row of this table. When creating the new row in the table the value of this object may be obtained by retreiving the value of pdnDevFileXferSessionIDNext.
                   pdnDevFileXferifIndex 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.2 integer32 read-only
This object specifies the interface number that corresponds to RFC1213. It this object is not used the value of this object should be zero.
                   pdnDevFileXferFileName 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.3 displaystring read-only
This object contains the name of the filetransfer file.
                   pdnDevFileXferCopyProtocol 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.4 integer read-only
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.
                   pdnDevFileXferFileType 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.5 integer read-only
Specifies the type of file your want to transfer. Enumeration: 'firmware': 1, 'config': 2.
                   pdnDevFileXferServerIpAddress 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.6 ipaddress read-only
This object contains the file transfer server's IP address.
                   pdnDevFileXferUserName 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.7 displaystring read-only
This object contains the username if a username is needed to login to the server.
                   pdnDevFileXferUserPassword 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.8 displaystring read-only
This object contains the password if a password is needed to login to the server. This object will return null on a read operation.
                   pdnDevFileXferUserAccount 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.9 displaystring read-only
This object contains the name of the the user account information that is stored on ftp server. Server would contain user name and password under this account name. This object will return null on a read operation. The default value fo this is a null string.
                   pdnDevFileXferOperation 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.10 integer read-only
This object contains the operation the file transfer wants to perform. Enumeration: 'put': 2, 'get': 1.
                   pdnDevFileXferPktsSent 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.11 counter32 read-only
This object contains the the number of packets sent to the server at the time of interrogation.
                   pdnDevFileXferPktsRecv 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.12 counter32 read-only
This object contains the the number of packets received from the server at the time of interrogation.
                   pdnDevFileXferOctetsSent 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.13 counter32 read-only
This object contains the the number of octets sent to the server at the time of interrogation.
                   pdnDevFileXferOctetsRecv 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.14 counter32 read-only
This object contains the the number of octets received from the server at the time of interrogation.
                   pdnDevFileXferOwnerString 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.15 octet string read-only
The entity which currently has the 'ownership' required to invoke the operation on this index.
                   pdnDevFileXferStatus 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.16 integer read-only
This object contains the status of the file transfer. Enumeration: 'failure': 3, 'none': 1, 'inprogress': 4, 'success': 2.
                   pdnDevFileXferApply 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.17 integer read-only
This object is configured to specify if the firmware download will be applied immediatley after file transfer or not. Enumeration: 'yes': 1, 'no': 2.
                   pdnDevFileXferErrorStatus 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.18 integer32 read-only
This object contains the reason code of the failure determined in devFileXferStatus. 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
                   pdnDevFileXferSendEvent 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.19 integer read-only
This object indicates whether or not to send the pdnDevFileXferEvent event trap . Enumeration: 'active': 1, 'inactive': 2.
                   pdnDevFileXferXferTime 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.20 timeticks read-only
This object indicates the elapsed time (in hundredths of a second) of the file transfer.
                   pdnDevFileXferRowStatus 1.3.6.1.4.1.1795.2.24.2.10.7.2.1.21 rowstatus read-only
This object is used to create a new row or delete an existing row in this table.
           pdnDevFileXferSessionIDNext 1.3.6.1.4.1.1795.2.24.2.10.7.3 integer32 read-only
This object contains an appropriate value to be used for pdnDevFileXferTable. The value of 0 indicates that no unassigned entries are available. To obtain pdnDevFileXferSessionID value for the new entry the manager issues a management protocol retrieval operation to obtain a current value of this object. After each retrieval, the agent should modify the value to the next unassigned index.
       devFileXferMIBTraps 1.3.6.1.4.1.1795.2.24.2.10.8
       devFirmwareControlMIBObjects 1.3.6.1.4.1.1795.2.24.2.10.9
           devFirmwareControlTable 1.3.6.1.4.1.1795.2.24.2.10.9.1 no-access
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.
               devFirmwareControlEntry 1.3.6.1.4.1.1795.2.24.2.10.9.1.1 no-access
The Device Firmware Release entry.
                   devFirmwareControlIndex 1.3.6.1.4.1.1795.2.24.2.10.9.1.1.1 integer32 read-only
This object is used to index the Firmware table (range 1 to N).
                   devFirmwareControlRelease 1.3.6.1.4.1.1795.2.24.2.10.9.1.1.2 displaystring read-only
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.
                   devFirmwareControlOperStatus 1.3.6.1.4.1.1795.2.24.2.10.9.1.1.3 integer read-only
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.
                   devFirmwareControlAdminStatus 1.3.6.1.4.1.1795.2.24.2.10.9.1.1.4 integer read-only
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 devFirmwareControlOperStatus is invalid will return BAD VALUE. Writing inactive(2) will always return BAD VALUE. Enumeration: 'active': 1, 'inactive': 2.
       pdnConfigChangeMgmt 1.3.6.1.4.1.1795.2.24.2.10.10
             pdnCCMAutoBackup 1.3.6.1.4.1.1795.2.24.2.10.10.1
                 pdnCCMAutoBackupType 1.3.6.1.4.1.1795.2.24.2.10.10.1.1 integer read-write
This object indicates whether automatic backup of device configuration files to the MCC Flash File System is disabled, performed according to a fixed schedule, or whether it occurs dynamically at a specified interval after the latest configuration change to a device. Enumeration: 'disabled': 0, 'fixed': 1, 'dynamic': 2.
                 pdnCCMAutoBackupFixedDay 1.3.6.1.4.1.1795.2.24.2.10.10.1.2 bits read-write
This object indicates the days of the week on which fixed schedule automatic backups occur. If all bits are set, backups occur daily. Bits: 'monday': 1, 'tuesday': 2, 'friday': 5, 'wednesday': 3, 'thursday': 4, 'sunday': 0, 'saturday': 6.
                 pdnCCMAutoBackupFixedTime 1.3.6.1.4.1.1795.2.24.2.10.10.1.3 integer32 read-write
This object indicates the time of day, in minutes past midnight, at which automatic backups on a fixed schedule occur.
                 pdnCCMAutoBackupDynamicTime 1.3.6.1.4.1.1795.2.24.2.10.10.1.4 integer32 read-write
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 interval is 30 minutes. The maximum interval is 24 hours (1440 minutes).
                 pdnCCMAutoBackupAppendTimeStampToFilename 1.3.6.1.4.1.1795.2.24.2.10.10.1.5 integer read-only
This object indicates that the time is to be appended to filename of the file stored to upon automated backup. The defualt value of this object is disabled(2). Enumeration: 'enable': 1, 'disable': 2.
                 pdnCCMAutoBackupFilename 1.3.6.1.4.1.1795.2.24.2.10.10.1.6 displaystring read-only
This is file name that the configuration will be stored to upon automated backup.
                 pdnCCMAutoBackupServerIpAddress 1.3.6.1.4.1.1795.2.24.2.10.10.1.7 ipaddress read-only
This object is to configure Ip address of the server used to perform autobackup.
                 pdnCCMAutoBackupUserName 1.3.6.1.4.1.1795.2.24.2.10.10.1.8 displaystring read-only
This object user name used to start ftp session for automatic backup.
                 pdnCCMAutoBackupUserPassword 1.3.6.1.4.1.1795.2.24.2.10.10.1.9 displaystring read-only
This object user password that is paired with user name for ftp server login.
                 pdnCCMAutoBackupUserAccount 1.3.6.1.4.1.1795.2.24.2.10.10.1.10 displaystring read-only
This object is user account name that ftp server contains. Under this name ftp server stores UserName and UserPassword info. If this object is null(not configured) than the pdnCCMAutoBackupUserName and pdnCCMAutoBackupUserPassword are used. The default is null string.
                 pdnCCMAutoBackupCopyProtocol 1.3.6.1.4.1.1795.2.24.2.10.10.1.11 integer read-only
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.
             pdnCCMAutoRestore 1.3.6.1.4.1.1795.2.24.2.10.10.2 switchstate read-write
This object specifies whether the MCC Flash File System will restore stored configuration files to newly inserted cards in the DSLAM.
             pdnCCMResyncOperation 1.3.6.1.4.1.1795.2.24.2.10.10.3 integer read-write
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. Querying this object always retrieves the value noOp(1) Enumeration: 'put': 3, 'noOp': 1, 'get': 2.
             pdnCCMOperation 1.3.6.1.4.1.1795.2.24.2.10.10.4 integer read-write
This object contains configuration options for operations performed to manage object. SAVE(3) operation is interpreted as copying running configuration to database (nvram). APPLY(2) is operation performed to make configuration paramters take in effect. RESET(4) operation is designed to upload database (nvram),saved, configuration, and make it running configuration. REVERT(5) is configuration option used in a case of error upon set operation (before DD applies configuration parameter(s)). It will effectively make previous applied configuration parameter set valid, running configuration. In some systems this will be an internal (user transperent) operation in case of error deteced by DD. DEFAULT(6) will upload default parameters to running configuration without changing saved configuration in a database (nvram). Querying this object always retrieves the value noOp(1). Enumeration: 'reset': 4, 'default': 6, 'revert': 5, 'noOp': 1, 'apply': 2, 'save': 3.
       pdnControlMIBGroups 1.3.6.1.4.1.1795.2.24.2.10.11
             devResetGroup 1.3.6.1.4.1.1795.2.24.2.10.11.1
Objects to initiate resets of a device
             devControlTestGroup 1.3.6.1.4.1.1795.2.24.2.10.11.2
Objects to control device level tests
             devControlDownloadGroup 1.3.6.1.4.1.1795.2.24.2.10.11.3
A list of the current Download Releases and their associated status.
             devControlRMONGroup 1.3.6.1.4.1.1795.2.24.2.10.11.4
The desired state of the RMON process.
             devSNSwitchFirmwareGroup 1.3.6.1.4.1.1795.2.24.2.10.11.5
Objects needed to switch bank and reset the Service Node.
             devControlFTPGroup 1.3.6.1.4.1.1795.2.24.2.10.11.6
FTP Max Transfer Rate
             devFileXferMIBGroup 1.3.6.1.4.1.1795.2.24.2.10.11.7
File Transfer Client Config Objects
             devFirmwareControlGroup 1.3.6.1.4.1.1795.2.24.2.10.11.8
Current Firmware Releases and associated status.
             devConfigChangeMgmtGroup 1.3.6.1.4.1.1795.2.24.2.10.11.9
Object group used to manage automatic backup and restore of device configuration files.
             devFileXferEventGroup 1.3.6.1.4.1.1795.2.24.2.10.11.10
Notifications associated with devFileXferConfigGroup
             devCCMEventGroup 1.3.6.1.4.1.1795.2.24.2.10.11.11
Notifications indicating a failure occuring during automated backup or restore of device configuration files.
             pdnAutoFwGroup 1.3.6.1.4.1.1795.2.24.2.10.11.12
Auto Firmware Download Feature and associated status.
             devAutoFwEventGroup 1.3.6.1.4.1.1795.2.24.2.10.11.13
Notifications indicating the result of the Auto Firmware Download.
             pdnDevFileXferMIBGroup 1.3.6.1.4.1.1795.2.24.2.10.11.14
File Transfer Client Objects
             devNextTableObjectMIBGroup 1.3.6.1.4.1.1795.2.24.2.10.11.15
Group of singular objects that decided next available object for mib tables.
             pdnDevFileXferEventGroup 1.3.6.1.4.1.1795.2.24.2.10.11.16
Notifications associated with pdnDevFileXferConfigGroup
       pdnAutoFw 1.3.6.1.4.1.1795.2.24.2.10.12
             devIsAutoFwEnabled 1.3.6.1.4.1.1795.2.24.2.10.12.1 switchstate read-write
Writing the value enabled(1) or disabled(2) to this object enables or disables the Automatic Firmware download feature.
             devAutoFwStatus 1.3.6.1.4.1.1795.2.24.2.10.12.2 displaystring read-only
This indicates the Status of Auto Firmware Download where each field is separated by a semi-colon. The get function will return the status of the latest card downloaded.