CISCO-SM-FILE-DOWNLOAD-MIB.mib object view, vendor Cisco

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CISCO-SM-FILE-DOWNLOAD-MIB and use it to monitor vendor specific OID's.

CISCO-SM-FILE-DOWNLOAD-MIB file content

Object view of CISCO-SM-FILE-DOWNLOAD-MIB:

Scalar Object
csDefineFileEntry	.1.3.6.1.4.1.9.9.199.1.1.1.1
Information for processing the file to be downloaded to service modules. To process a file an application creates an entry in this table. This entry contains information on the file name (csDefineFileName), file operation i.e whether to download contents from the file specified or from contents saved in the database (csDefineFileOperation), slot number of the service module to download to (csDefineSlotNumber), etc. When the entry status (csDefineFileEntryStatus) in this table is 'active', the application uses csDefineFileOperation to perform the necessary operation on the file. csDefineFileStatus contains the overall status of file validation and download. Corresponding entries are created in csFileStatusTable that contains the slot-specific status of the download to service modules. Entries may not be modified or deleted if csDefineFileStatus has a value of 'inProgress'. Further, the entries may not be deleted if csDefineFileEntryStatus is 'active' i.e if the current entry status is 'active', it has to be set to 'notInService' before deletion. Deleting an entry in csDefineFileTable deletes any corresponding entries in csFileStatusTable. Rows may not be created without explicitly setting csDefineFileEntryStatus to either 'createAndGo' or 'createAndWait'.
csFileStatusEntry	.1.3.6.1.4.1.9.9.199.1.2.1.1
Status of file download to a particular service module. Entries start to exist in this table only when csDefineFileStatus has been set to 'inProgress'. The number of entries per csFileStatusTable is dependant on csDefineSlotNumber specified. If a valid slot number (between values 1 and 32) is specified then this table would contain only one entry for the slot number specified. If csDefineSlotNumber has value 100, signifying a download to all SMs, an entry exists in csFileStatusTable for each applicable service module on the shelf. Hence, an entry in csDefineFileTable could result in multiple entries in csFileStatusTable. Related entries can be associated due to the common index, csDefineFileIndex, in the tables.
Tabular Object
csDefineFileIndex	.1.3.6.1.4.1.9.9.199.1.1.1.1.1
An integer to uniquely identify this entry.
csDefineFileName	.1.3.6.1.4.1.9.9.199.1.1.1.1.2
The name of the file that has been downloaded on some non-volatile storage on the controller card. Explicit device or path names could be prepended to the file name.
csDefineSlotNumber	.1.3.6.1.4.1.9.9.199.1.1.1.1.3
An integer that specifies the slot number of the service module to which the file needs to be downloaded. A value of 100 would indicate that file needs to be downloaded to all applicable service modules.
csDefineFileStatus	.1.3.6.1.4.1.9.9.199.1.1.1.1.4
The overall status of the file validation and service module download as surmised by the controller card. A more detailed status on service module downloads could be obtained in csFileStatusTable which stores download information specific to a particular slot. inProgress - processing file validation/download request success - file has been validated and downloaded to all applicable service modules (as per value in csDefineSlotNumber) successfully. noMemory - failure due to insufficient dynamic memory fileOpenFailed - failure to open the file downloaded to some non-volatile storage on the controller card. fileReadFailed - failure to read the file downloaded to some non-volatile storage on the controller card. fileNotValid - file parsing/validation failed downloadFailed - download to service module failed aborted - download aborted due to switchover in a redundant controller card configuration dbUpdateFailed - error in accessing/updating the database miscError - miscellaneous error due to lack of internal resource (eg. error obtaining semaphore etc) This object is valid only after the entry status becomes 'active'. This object is especially useful when csDefineSlotNumber has a value of 100 signifying a download to all applicable service modules. This object gives overall status of the download request and hence, has a value of 'downloadFailed' even if one SM fails the download. csFileStatusTable could be consulted for the purpose of obtaining a list of SMs that failed the download and their corresponding reasons.
csDefineFileOperation	.1.3.6.1.4.1.9.9.199.1.1.1.1.5
An integer that defines the file operation: sendToSMsOnly - send file contents saved in database to all applicable service modules. updateAndSend - validate file, save contents into database and send to all applicable service modules. The database here refers to either a disk or a RAM database that is saved during controller card switchovers. The file contents are saved prior to service module download. In case of failure to download to SMs,the operation could be re-initiated with csDefineFileOperation having value sendToSMsOnly. This would avoid unnecessary download of the same file to controller card storage and file parsing/validation.
csDefineFileEntryStatus	.1.3.6.1.4.1.9.9.199.1.1.1.1.6
The control that allows creation, modification, and deletion of entries. For detailed rules see the DESCRIPTION for csDefineFileEntry.
csFileStatusSlotNumber	.1.3.6.1.4.1.9.9.199.1.2.1.1.1
Slot number that has an applicable service module.
csFileSlotState	.1.3.6.1.4.1.9.9.199.1.2.1.1.2
The status of the file download to each applicable service module. This status is specific to each slot. inProgress currently downloading file to service module notProcessed not started downloading to service module success successfully downloaded file to service module fileOpenFailed failed to open file on service module fileWriteFailed failed to write file on service module aborted download was terminated (eg. due to switchover in a redundant configuration) miscFailure miscellaneous error during file download
Table
csDefineFileTable	.1.3.6.1.4.1.9.9.199.1.1.1
A table of files that have been downloaded on some non- volatile storage (For example: Hard Disk, Flash Disk etc) on the controller card by mechanisms such as ftp, tftp etc and available for transfer to applicable service modules.
csFileStatusTable	.1.3.6.1.4.1.9.9.199.1.2.1
A table containing status of the downloaded file for each applicable service module.
Object Identifier
ciscoSmFileDownloadMIB	.1.3.6.1.4.1.9.9.199
The MIB module for downloading files to the Service Modules specifically designed for an architecture containing a controller card and a group of sub- ordinate cards or service modules (as in a Switch). These files could contain information for performing any specific operation on the modules. For example, they could contain information on statistics retrieval like, the statistics type, bucket interval etc. The format of these files is implementation dependent.
csFileMIBObjects	.1.3.6.1.4.1.9.9.199.1
csDefineFile	.1.3.6.1.4.1.9.9.199.1.1
csFileStatus	.1.3.6.1.4.1.9.9.199.1.2
csFileMIBNotificationPrefix	.1.3.6.1.4.1.9.9.199.2
csFileMIBNotifications	.1.3.6.1.4.1.9.9.199.2.0
csFileMIBConformance	.1.3.6.1.4.1.9.9.199.3
csFileMIBCompliances	.1.3.6.1.4.1.9.9.199.3.1
csFileMIBGroups	.1.3.6.1.4.1.9.9.199.3.2
Group
csDefineFileGroup	.1.3.6.1.4.1.9.9.199.3.2.1
File download management.
csFileStatusGroup	.1.3.6.1.4.1.9.9.199.3.2.2
File status management for applicable service modules.