AVAYA-LOAD-MIB: View SNMP OID List / Download MIB

The avLoad MIB defines upload, download and copy of application software and configuration information. Copyright(c) 2004-2005 by Avaya Inc. All rights reserved.

The device has begun download operation.

The device has completed successful download operation.

The download operation was failed.

The device has begun download operation.

The device has completed successful download operation.

The download operation was failed.

The number of operational sessions in progress in this system

Table of configuration attributes which define the operational functions and the results on a per module basis. This group provides the mechanism by which available operations are initiated, monitored and reported.

An entry in the table, containing data about a single modules operations.

Index which identifies the module inside the chassis for which this entry contains information. Equals the number of the slot by which the group is accessed or the stackable index. Announcements file will be presented in Module ID == 9.

Index to identify the operation supported by this row entry. Each operation type that is supported by this module should be represented by a unique row in this MIB Table. A walk of this MIB table should reveal all the operations that are supported by the device. Note: avGenOpServerIP is used for IPv4 addresses only. avGenOpServerInetAddressType/avGenOpServerInetAddress are used for IPv4/IPv6 addresses. The operations supported are: uploadConfig -- The 'avGenOpDestIndex' should be set to 0 (to indicate destination of server). The 'avGenOpServerIP' should be set to the server to which the config will be saved. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the config file you are uploading. The 'avGenOpFileName' should be set to the name and path of the config file on the TFTP server. downloadConfig -- The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the config file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpServerIP' should be set to the server from which the config will be copied. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to 0 (to indicate source of server). The 'avGenOpFileName' should be set to the name and path of the config file on the TFTP server. report -- uploadSoftware -- The 'avGenOpDestIndex' should be set to 0 (to indicate destination of server). The 'avGenOpServerIP' should be set to the server to which the config file will be saved. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the software file you are uploading. The 'avGenOpFileName' should be set to the name and path of the image file on the TFTP server. downloadSoftware -- The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the software file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpServerIP' should be set to the server from which the config file will be copied. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to 0 (to indicate source of server). The 'avGenOpFileName' should be set to the name and path of the image file on the TFTP server. localConfigFileCopy -- (using a 'avGenOpType' of 'localPeerTransport') The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the config file you are copying to (if one does not exist you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the config file you are copying from. The 'avGenOpServerIP' should be set to NULL. The 'avGenOpProtocolType' should be set to 'localPeerTransport'. The 'avGenOpFileName' should be set to NULL. localSWFileCopy -- (using a 'avGenOpType' of 'localPeerTransport') The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the software file you are copying to (if one does not exist you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the software file you are copying from. The 'avGenOpServerIP' should be set to NULL. The 'avGenOpProtocolType' should be set to 'localPeerTransport'. The 'avGenOpFileName' should be set to NULL. localConfigFileCopy -- (using a 'avGenOpType' of 'localServerTransport') The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the config file you are copying to (if one does not exist you'll need to RowCreate it in the 'avGenAppFileTable') or ZERO (0) if copying to a localServer. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the config file you are copying from or ZERO (0) if copying from a localServer. The 'avGenOpServerIP' should be set to the address of the local server. The 'avGenOpProtocolType' should be set to 'localServerTransport'. localSWFileCopy -- (using a 'avGenOpType' of 'localServerTransport') The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the software file you are copying to (if one does not exist you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the software file you are copying from. The 'avGenOpServerIP' should be set to the address of the local server. The 'avGenOpProtocolType' should be set to 'localServerTransport'. uploadLogfile -- The 'avGenOpDestIndex' should be set to 0 (to indicate destination of server). The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the log file you are copying from. The 'avGenOpServerIP' should be set to the server to which the config will be saved. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpFileName' should be set to the name and path of the log file on the TFTP server. eraseFile -- The 'avGenOpDestIndex' Is not applicable for this command. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the file you wish to erase. The 'avGenOpServerIP' should be set to 0. The 'avGenOpProtocolType' should be set to 0. The 'avGenOpFileName' should be set to NULL. show -- Reporting information to the CLI. syncStandbyAgent(11) -- copy configuration AND software image files to the (non-active) standby agent in a P550/P880. The 'avGenOpDestIndex' should be set to 1 The 'avGenOpSourceIndex' should be set to 1 The 'avGenOpServerIP' should be set to NULL. The 'avGenOpProtocolType' should be set to 'localPeerTransport'. The 'avGenOpFileName' should be set to NULL. downloadAuthFile (12) -- copy Services Logins authentication file to the device. The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the auth file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpServerIP' should be set to the server from which the config will be copied. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to 0 (to indicate source of server). The 'avGenOpFileName' should be set to the name and path of the config file on the TFTP/ftp/scp server. downloadLicFile (13) - -- copy SLicense file to the device. The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the auth file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpServerIP' should be set to the server from which the config will be copied. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to 0 (to indicate source of server). The 'avGenOpFileName' should be set to the name and path of the config file on the TFTP/ftp/scp server. downloadPhoneScriptFile (14) - copy IP phone configuration file (or other endpoints configuration files) to the device TFTP Server directory. IP Phone configuration file includes Setting File and Upgrade Script. Non Volatile Storage. The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the phone configuration file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpServerIP' should be set to the server from which the config will be copied. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to 0 (to indicate source of server). The 'avGenOpFileName' should be set to the name and path of the config file on the TFTP/ftp/scp server. uploadPhoneScriptFile(15) - copy IP phone configuration file (or other endpoints configuration files) from the device TFTP Server directory to remote server. IP Phone configuration file includes Setting File and Upgrade Script. The 'avGenOpDestIndex' should be set to 0 (to indicate destination of server). The 'avGenOpServerIP' should be set to the server to which the config will be saved. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the config file you are uploading. The 'avGenOpFileName' should be set to the name and path of the config file on the TFTP/ftp/scp server. downloadPhoneImageFile(16) - copy IP phone images file (or other endpoints images files) to the device TFTP Server Directory. Volatile Storage. The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the software file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpServerIP' should be set to the server from which the config file will be copied. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to 0 (to indicate source of server). The 'avGenOpFileName' should be set to the name and path of the image file on the TFTP/ftp server. uploadDhcpBindingFile(17) - copy DHCP Binding File from the device to remote server. The binding file includes information of IP , MAC couples and leased time. Non Volatile Storage. The 'avGenOpDestIndex' should be set to 0 (to indicate destination of server). The 'avGenOpServerIP' should be set to the server to which the config will be saved. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the config file you are uploading. The 'avGenOpFileName' should be set to the name and path of the config file on the TFTP/ftp/scp server. uploadAnnouncements(18) - copy announcements files from the device to remote server. The announcements files are stored in Non Volatile Storage. The 'avGenOpDestIndex' should be set to 0 (to indicate destination of server). The 'avGenOpServerIP' should be set to the server to which the announcement file will be saved. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the announcement file you are uploading. The 'avGenOpFileName' should be set to the name and path of the announcement file on the remote server. downloadAnnouncements(19)- copy announcement file to the device from remote server. The 'avGenOpDestIndex' should be set to the 'avGenAppFileId' of the software file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'avGenAppFileTable'). The 'avGenOpServerIP' should be set to the server from which the announcement file will be copied. The 'avGenOpProtocolType' should be set to the IP protocol used to transport the file. The 'avGenOpSourceIndex' should be set to 0 (to indicate source of server). The 'avGenOpFileName' should be set to the name and path of the announcement file on the remote server. renameFile(20) - Rename announcement file name on the local device. The 'avGenOpDestIndex' is not applicable for this command. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the software file you are renaming. The 'avGenOpServerIP' should be set to 0. The 'avGenOpProtocolType' should be set to 'localPeerTransport'. The 'avGenOpFileName' should be set to the new name. Commit -- The 'avGenOpDestIndex' Is not applicable for this command. The 'avGenOpSourceIndex' should be set to the 'avGenAppFileId' of the file you wish to commit. The 'avGenOpServerIP' should be set to 0. The 'avGenOpProtocolType' should be set to 0. The 'avGenOpFileName' should be set to NULL. reset(48) -- The 'avGenOpDestIndex' Is not applicable for this command. The 'avGenOpSourceIndex' Is not applicable for this command. The 'avGenOpServerIP' should be set to 0. The 'avGenOpProtocolType' should be set to 0. The 'avGenOpFileName' should be set to NULL. Enumeration: 'restore': 29, 'downloadConfigurationWizardTaskFile': 44, 'show': 10, 'uploadAuthFile': 22, 'uploadConfig': 1, 'downloadCertificate': 36, 'downloadPhoneMessageFile': 42, 'downloadPhoneScriptFile': 14, 'uploadCertificate': 37, 'uploadAnnouncements': 18, 'generateFile': 35, 'uploadServicePack': 31, 'uploadPhoneScriptFile': 15, 'downloadLicFile': 13, 'uploadSyslogFile': 24, 'downloadConfig': 2, 'eraseFile': 9, 'downloadAuthFile': 12, 'uploadLicFile': 23, 'localSWFileMove': 46, 'uploadSoftware': 4, 'localVoiceMailFileMove': 47, 'downloadAnnouncements': 19, 'eraseAnnouncement': 21, 'localSWFileCopy': 7, 'renameAnnouncement': 20, 'uploadCDRFile': 25, 'downloadServicePack': 32, 'uploadConfigurationWizardTaskFile': 45, 'reset': 48, 'switchPartitions': 38, 'report': 3, 'backupConfig': 28, 'uploadPhoneMessageFile': 43, 'downloadVoiceMailFile': 40, 'uploadDhcpBindingFile': 17, 'downloadPhoneImageFile': 16, 'uploadLogfile': 8, 'localServicePackFileCopy': 33, 'localConfigFileCopy': 6, 'uploadPhoneImageFile': 39, 'downloadSoftware': 5, 'commit': 30, 'uploadVoiceMailFile': 41, 'backup': 34, 'syncStandbyAgent': 11.

Identifies the operation to perform and the state of that operation. This field acts as both the trigger to initiate the operation (via the beginOperation) and the status field of the operation itself (i.e. waiting-ip, running-ip, etc.). It is expected that all dependent MIB objects will be set before the trigger is set to beginOperation. The operations completion is triggered by the return to the idle state. idle(1), - Operation not in progress beginOperation(2), - Trigger by NMS to start the operation waitingIp(3), - Communication phase; waiting for response runningIp(4), - Communication phase; transferring data copyingLocal(5), - Local operation readingConfiguration(6), - Parsing / Executing configuration file executing(7) - Executing Command (such as erasing a file or reporting) blocked(8) - to be used when the Load MIB agent is unable to perform a requested operation, this could happen in CM if a firmware download job was submitted directly from the SAT. Since CM only accepts one job at a time, the Load MIB agent will be blocked until that job completes. reset(9) - to be used to request a reset only of a TN board, this capability is a existing capability in Software Update Manager that we want to support directly in the Load MIB. Enumeration: 'reset': 9, 'waitingIp': 3, 'beginOperation': 2, 'readingConfiguration': 6, 'executing': 7, 'idle': 1, 'copyingLocal': 5, 'runningIp': 4, 'blocked': 8.

The index value (taken from the avGenAppFileTable) of the source of the operation. NOTE: A value of zero (0) here indicates that the Server (specified below) is the source.

The index value (taken from the avGenAppFileTable) of the destination of the operation. NOTE: A value of zero (0) here indicates that the Server (specified below) is the Destination.

The IP Address of the server from/to which the file has to be Download/Upload. NOTE: In the case of localPeerTransport this value should be NULL. Please note that avGenOpServerIP is used for IPv4 addresses only. avGenOpServerInetAddressType/avGenOpServerInetAddress are used for IPv4/IPv6 addresses.

Contains the username to be used if the protocol specified in avGenOpProtocolType requires one. The default value will be the empty string

Contains the password to be used if the protocol specified in avGenOpProtocolType requires one. The default value will be the empty string

Identifies the protocol between the management station and the device for Download/Upload of the file. Enumeration: 'ftp': 2, 'localPeerTransport': 3, 'http': 8, 'usb': 7, 'ftpResume': 10, 'sftp': 6, 'https': 9, 'tftp': 1, 'localServerTransport': 4, 'scp': 5.

The location (including the FULL path) of the file in the server. NOTE: In the case of localPeerTransport this value should be NULL. In case of genOpProtocolType==usb(7) the file name shall include the prefix of the usbdevice/file system as follows: /usbdevice0-127/backupdirectory/backupsubdirectory/filename. An example can be: /usbdevice0/backupg350/IPPHONE/46xx_settings.txt. If there is only one usb mass storage device connected to the gateway then use /usbdevice0/ to copy from/to this device files.

The state of the operation for Display on the terminal during operation process.

While a download is in progress this will always be 'no-error'. After a download is complete this indicates the success or failure of the download. If it is anything other than 'no-error' then 'avGenOpLastFailureDisplay' will contain a textual description of the error. Error codes from 100 upwards are errors returned from a TFTP server. errors below this are locally generated. Configuration files may return errors after download as a result of reading a config file into the system. confFileGenErr - General (unknown error) confFileParseError - Reading of config file resulted in parsing errors. confFileExecError - Reading of config file resulted in execution errors. sshServerAuth - SCP server failed to authenticated himself to a device. sshDeviceAuth(109)- device failed to authenticate to the SCP server (unknown user/bad password) badChainOfTrust(201) - Failed to authenticate the download with Trusted Certificate Root Authority badChainOfTrustFormat (202) - Not supported chain of trust format notCodeSigningAuthority (203) Software image was signed by non-authorized Certificate Authority illegalDSA (204) - Software image is signed with non FIPS 140-2 certified algorithm badPublicKeyFormat(205) - Not supported public key format. illegalDSKeySize(206) - Software image is signed with non FIPS 140-2 certified key size badDSFormat(207) - Not supported digital signature format authDSFailure(208) - Failed to authenticate digital image signature New Errors use for with announcement files: readOnlyFile(15) - For cases where management system tries to erase/delete file which is read-only. emptyFile(16) - When trying to erase/upload file that does not exists or size with size 0. noEnoughFreeMemoryLeft(17) - When trying to download a file to the device and there is no place left to it. fileAlreadyExistsInDirectory(18) - when trying to download file which already exists in the directory (in one of the other AvGenAppFileTable rows, if we want to update it we need to use the same row in the table). Enumeration: 'badDSFormat': 207, 'nvramWriteError': 11, 'sshServerAuth': 108, 'readOnlyFile': 15, 'badPublicKeyFormat': 205, 'undefinedError': 100, 'sshDeviceAuth': 109, 'illegalDSA': 204, 'busy': 4, 'ftpResumeEmptyFile': 221, 'confFileParseError': 13, 'authDSFailure': 208, 'notCodeSigningAuthority': 203, 'noError': 1, 'configError': 3, 'fileTooBig': 8, 'emptyFile': 16, 'confFileGenErr': 12, 'accessViolation': 102, 'badChainOfTrustFormat': 202, 'illegalDSKeySize': 206, 'genError': 2, 'fileAlreadyExists': 106, 'ftpResumeBadFilename': 220, 'outOfMemory': 103, 'protocolError': 9, 'illegalOperation': 104, 'configFileSecretIntegrityFault': 210, 'noEnoughFreeMemoryLeft': 17, 'unknownTransferId': 105, 'confFileExecError': 14, 'ftpResumeNotSupported': 222, 'noSuchUser': 107, 'flashWriteError': 10, 'timeout': 5, 'cancelled': 6, 'fileNotFound': 101, 'badChainOfTrust': 201, 'incompatibleFile': 7.

Contains the last error, Null if there is no error.

Last warning which didn't stop the operation (not fatal error).

The Index in the 'avGenAppFileTable' under which an error log has been created. In the case of file that produce errors this file should contain a log of errors that occurred. (This item should be zero if it does not exist)

Indicates if a reset (after operation completion) is supported by this Module. Enumeration: 'notSupported': 2, 'supported': 1.

Whether to do a reset after the operation completed successfully. Enumeration: 'enable': 1, 'disable': 2.

The row in the 'avGenAppFileTable' of the default Application that the device will boot from when a standard reboot is performed.

The Index in the 'avGenAppFileTable' of the default Application that the device was last booted from.

Indicates what type of file system is supported by this module. A value of 'static' indicates that rows in the 'avGenAppFileTable' are not removable nor can new entries be created. A value of 'dynamic' indicates that entries in the 'avGenAppFileTable' are both removable and can be created. Enumeration: 'dynamic': 2, 'static': 1.

Contain modifiers to the Report operation. fullReport - Full configuration report partialReport - A report without the information stored in the OSPF database notSupported - For operations other than report, this MIB has no meaning and can return not Supported or not be supported. Enumeration: 'partialReport': 2, 'fullReport': 1, 'notSupported': 255.

While a download is in progress this indicates the number of bytes transferred so far.

The avGenOpDownloadProxy is the location of a CLAN board that will serve as the proxy for the firmware download of a TDM-based board, since these boards are unable to perform the download operation themselves. The CLAN will be responsible for obtaining the image. 1 - any 2 - self 6657-413216 - Board location. Default value is 1.

The address type of avGenOpServerInetAddress.

The Inet Address of the remote file server. 1. The address type of this object is specified in avGenOpServerInetAddress. 2. Management applications can use avGenOpServerIP or avGenOpServerInetAddressType/avGenOpServerInetAddress to set IPv4 server address and only avGenOpServerInetAddressType/avGenOpServerInetAddress to set IPv6 server address. 3. The avGenOpServerInetAddressType must always been set before the avGenOpServerInetAddress is set (the avGenOpServerInetAddress must conform to the avGenOpServerInetAddressType). 4. Setting avGenOpServerIP address mib item will change avGenOpServerInetAddressType to IPv4(1) and avGenOpServerInetAddress to IPv4 address configured. 5. Setting avGenOpServerInetAddress as IPv4 address will also set avGenOpServerIP. 6. Setting avGenOpServerInetAddress as IPv6 address will also set avGenOpServerIP to 0.0.0.0. 7. Default of avGenOpServerInetAddressType is unknown(0) and avGenOpServerInetAddress is zero length. 8. Setting avGenOpServerInetAddressType to IPv4 will return avGenOpServerIP and avGenOpServerInetAddress to default value of 0.0.0.0. Setting avGenOpServerInetAddressType to value other than IPv4 return avGenOpServerIP to default value of 0.0.0.0 and avGenOpServerInetAddress to default value of null string.

Table of Application (FILE) entries. Each row uniquely defines an application in the system. Applications can be defined as any entity that can be read or written from or to the system. This includes software images, boot code, configuration files, prom code, etc.

An entry in the table, containing data about a single application / config file.

Index which uniquely identifies the application. NOTE: This index CANNOT BE ZERO (0) since the index of zero is reserved as an indication of network server location in the avGenOpSourceIndex and avGenOpDestIndex above.

The name of the application.

The type (class) of the application. This class serves to catagorize the many application files in the system into some fixed types: runningConfiguration -- This entry represents a virtual file in the system. Use of this entry in the avGenOpTable should serve to cause the system to generate it's configuration or to force the system to read a new config into it's configuration. startupConfiguration -- This entry represents a real file that is used at start-up to configure the device. defaultConfiguration -- This entry represents a file which contains the default configuration of the device. report -- ?? genConfigFile -- This entry represents a file which contains configuration information (similar to the 'startupConfiguration' above but is not automatically read by the device. This entry is used to represent 'alternate', 'backup' or 'experimental' configurations that the user may which to store on the device. nvramFile -- This entry represents a file that is contain in the nvram files system that does not fit any of the other pre-defined types. swRuntimeImage -- This entry represents a software images that contains operational code that is currently being used to run the device. swBootImage -- This entry represents a software image that contain operational code that is used to initally boot the device. swComponent -- This entry represents a file that is stored as an 'alternate', 'backup' or 'experimental' version of operational code. other -- other swWebImage -- The Image file of the embedded Web application (java application, etc). swAPImage -- the firmware of the Light AP. Device stores the image to support Light AP firmwareless operation. image boot service swNonDownLoadRunTimeImage - image of a non-downloadable code e.g. a bootstrap code asgAuthFile - encrypted Services Logins file licenseFile - file controlling licensed features activation phoneScriptFile(17) - Avaya IP Phone Configuration files (or other endpoints configuration files) as Setting file and Upgrade Script, Stored in device TFTP Server directory, Non Volatile Storage. phoneImageFile(18) - Avaya IP Phone Images files (or other endpoints images files), stored in device TFTP Server directory, Volatile Storage. dhcpBindingFile(19) - Device DHCP server IP binding file. Includes information about bindings of IP to MAC and leased time. announcementFile(20) - Announcement files. Enumeration: 'swRuntimeServicePack': 24, 'dhcpBindingFile': 19, 'phoneAvayaUnicodeMessageFile': 31, 'swBootImage': 9, 'syslogFile': 22, 'swAPImage': 13, 'startupConfiguration': 2, 'cdrFile': 23, 'certificateRequest': 27, 'phoneImageFile': 18, 'defaultConfiguration': 3, 'asgAuthFile': 15, 'other': 11, 'backupDatabase': 21, 'phoneCustomUnicodeMessageFile': 32, 'announcementFile': 20, 'swComponentServicePack': 25, 'swWebImage': 12, 'privateKey': 29, 'genConfigurationWizardTaskFile': 34, 'swRuntimeImage': 8, 'licenseFile': 16, 'swNonDownLoadRunTimeImage': 14, 'report': 4, 'genConfigFile': 5, 'phoneScriptFile': 17, 'serverCertificate': 28, 'runningConfiguration': 1, 'nvramFile': 7, 'swComponent': 10, 'trustedCertificate': 26, 'staticLanguagePack': 30, 'startupConfigurationWizardTaskFile': 33, 'logFile': 6.

A description of the application.

The size (expressed as the number of bytes) of the application.

The current version of the application. If this file does not carry a version this field should be NULL. An example is a string of '24.6.0' for G350 software version.

The physical location of the application. Enumeration: 'flash': 7, 'flashBankB': 3, 'flashBankA': 2, 'ram': 1, 'nvram': 4, 'bootProm': 5, 'compactFlash': 6.

The time stamp is the Real Time if supported otherwise sysUpTime. The convention for this field is as follows: Real Time: Entry is prefixed with an 'R' character and time is formatted using the convention for date-and-time (rfc1903) DISPLAY-HINT 'R-2d-1d-1d,1d:1d:1d.1d,1a1d:1d' field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11 10 11 minutes from UTC 0..59 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: R-1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SysUpTime: Entry is prefixed with an 'S' character and time is formatted using a portion of that date-and-time convention DISPLAY-HINT 'S-1d-1d,1d:1d:1d.1d' field octets contents range ----- ------ -------- ----- 1 3 month 1..12 2 4 day 1..31 3 5 hour 0..23 4 6 minutes 0..59 5 7 seconds 0..60 6 8 deci-seconds 0..9 For example, S-5-26,13:30:15.0 Represents a file that has existed in the system for 5 months, 26 days, 13 hours, 30 minutes, 15 seconds exactly. This value will be reset after a reboot of the system.

The status of this entry in the table. Note the available states: active(1), -- Fully configured and active. notInService(2) -- NOT SUPPORTED. notReady(3), -- Entry NOT FULLY configured. createAndGo(4), -- Used to add new Applications in the system. createAndWait(5) -- Used to add new Applications in the system. destroy(6) -- Used to delete Applications in the system. Used only for destroying rows will file size 0. i.e. erase shall be done in operation mib and then destroy the row.

The avGenAppFilePortNetwork is the Port Network that a downloadable TN board is location in. This is useful to the customer in determining the Download Proxy, since location is a factor in determining whether a download is possible. This will represent the possible Port Networks of 1 through 64. Default is 1.

The avGenAppFileDuplStatus is the duplication state of the various TN boards that can be duplicated. These include the IPSI and Crossfire boards. This is also useful to the customer in order for them to determine whether a board is active or not. Typical operation is to update the firmware on the standbys first, then have the standbys become active, followed by updating the firmware on the standbys that were originally active. This will help the customer see if they are selecting an active board for upgrading. Default is standby(2). Enumeration: 'active': 1, 'standby': 2, 'not-administered': 3.

The compatability version relevant to other files on the system. If the value is not needed then this field should be NULL. An example is a string of '18.1'.

The system description.

The severity of the notification.

The SAT Connection status. For cases where the agent must log into the CM server via a SAT connection to collect the data. The agent retrieves the data via the SAT and converts it into SNMP MIB data which is accessible via standard SNMP get commands. The current state of the switch connection; this object can be set to 'off' to disable the connection and can be set to 'init' to re-initialize the connection. It can also be set to 'idle'. Enumeration: 'off': 2, 'up': 5, 'down': 3, 'init': 4, 'other': 1, 'idle': 6.

The state of the restore operation. The state will be: idle(1) when no restore operation is activated. executing(2) when restore operation is activated, after restore reset until restore operation is finished and then the status changed to idle(1). Enumeration: 'executing': 2, 'idle': 1.

Table of different application types and their memory allocation in the RAM and NvRAM.

An entry in the table, containing data about application and its memory type.

The module ID.

The Type of the memory that the the file is stored. Enumeration: 'nvram': 4, 'ram': 1, 'flashBankB': 3, 'bootProm': 5, 'flashBankA': 2.

The type of the application file. Enumeration: 'announcementFile': 20.

The size of the Memory in Bytes for specific application and memory type.

Total Bytes used for the specific module/memory type and file type.

Total Bytes free for the specific module/memory type and file type.

Table of dynamic applications. This MIB table can be used to show files on external USB mass storage device.

An entry in the table, containing data about the application.

The filename including file system, path and filename. An example: /usbdevice0/backup1/imageA.bin where /usbdevice0/ is the file system of external usb mass storage device. /backup1/ is directory and imageA.bin is the file.

Type of the entry (file or directory). Enumeration: 'directory': 2, 'file': 1.

The size (expressed as the number of bytes) of the file.

Time stamp of the file. Refer to avGenAppFileDateStamp syntax description.

The status of this entry in the table. Note the available states: active(1), -- Fully configured and active. notInService(2) -- NOT SUPPORTED. notReady(3), -- Entry NOT FULLY configured. NOT SUPPORTED. createAndGo(4), -- Used to add new Applications in the system. NOT SUPPORTED. createAndWait(5) -- Used to add new Applications in the system. NOT SUPPORTED. destroy(6) -- Used to delete Applications in the system. If destroy(6) is used on directory then all the files/directories inside this directory are also deleted.