LOAD-MIB: View SNMP OID List / Download MIB

Lucent Common Download / Upload Private MIB

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.

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. The operations supported are: uploadConfig -- The 'genOpDestIndex' should be set to 0 (to indicate destination of server). The 'genOpServerIP' should be set to the server to which the config will be saved. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpSourceIndex' should be set to the 'genAppFileId' of the config file you are uploading. The 'genOpFileName' should be set to the name and path of the config file on the TFTP server. downloadConfig -- The 'genOpDestIndex' should be set to the 'genAppFileId' of the config file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpServerIP' should be set to the server from which the config will be copied. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpSourceIndex' should be set to 0 (to indicate source of server). The 'genOpFileName' should be set to the name and path of the config file on the TFTP server. report -- uploadSoftware -- The 'genOpDestIndex' should be set to 0 (to indicate destination of server). The 'genOpServerIP' should be set to the server to which the config file will be saved. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpSourceIndex' should be set to the 'genAppFileId' of the software file you are uploading. The 'genOpFileName' should be set to the name and path of the image file on the TFTP server. downloadSoftware -- The 'genOpDestIndex' should be set to the 'genAppFileId' of the software file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpServerIP' should be set to the server from which the config file will be copied. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpSourceIndex' should be set to 0 (to indicate source of server). The 'genOpFileName' should be set to the name and path of the image file on the TFTP server. localConfigFileCopy -- (using a 'genOpType' of 'localPeerTransport') The 'genOpDestIndex' should be set to the 'genAppFileId' of the config file you are copying to (if one does not exist you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpSourceIndex' should be set to the 'genAppFileId' of the config file you are copying from. The 'genOpServerIP' should be set to NULL. The 'genOpProtocolType' should be set to 'localPeerTransport'. The 'genOpFileName' should be set to NULL. localSWFileCopy -- (using a 'genOpType' of 'localPeerTransport') The 'genOpDestIndex' should be set to the 'genAppFileId' of the software file you are copying to (if one does not exist you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpSourceIndex' should be set to the 'genAppFileId' of the software file you are copying from. The 'genOpServerIP' should be set to NULL. The 'genOpProtocolType' should be set to 'localPeerTransport'. The 'genOpFileName' should be set to NULL. localConfigFileCopy -- (using a 'genOpType' of 'localServerTransport') The 'genOpDestIndex' should be set to the 'genAppFileId' of the config file you are copying to (if one does not exist you'll need to RowCreate it in the 'genAppFileTable') or ZERO (0) if copying to a localServer. The 'genOpSourceIndex' should be set to the 'genAppFileId' of the config file you are copying from or ZERO (0) if copying from a localServer. The 'genOpServerIP' should be set to the address of the local server. The 'genOpProtocolType' should be set to 'localServerTransport'. localSWFileCopy -- (using a 'genOpType' of 'localServerTransport') The 'genOpDestIndex' should be set to the 'genAppFileId' of the software file you are copying to (if one does not exist you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpSourceIndex' should be set to the 'genAppFileId' of the software file you are copying from. The 'genOpServerIP' should be set to the address of the local server. The 'genOpProtocolType' should be set to 'localServerTransport'. uploadLogfile -- The 'genOpDestIndex' should be set to 0 (to indicate destination of server). The 'genOpSourceIndex' should be set to the 'genAppFileId' of the log file you are copying from. The 'genOpServerIP' should be set to the server to which the config will be saved. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpFileName' should be set to the name and path of the log file on the TFTP server. eraseFile -- The 'genOpDestIndex' Is not applicable for this command. The 'genOpSourceIndex' should be set to the 'genAppFileId' of the file you wish to erase. The 'genOpServerIP' should be set to 0. The 'genOpProtocolType' should be set to 0. The 'genOpFileName' 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 'genOpDestIndex' should be set to 1 The 'genOpSourceIndex' should be set to 1 The 'genOpServerIP' should be set to NULL. The 'genOpProtocolType' should be set to 'localPeerTransport'. The 'genOpFileName' should be set to NULL. Enumeration: 'downloadConfig': 2, 'eraseFile': 9, 'show': 10, 'localConfigFileCopy': 6, 'uploadConfig': 1, 'uploadSoftware': 4, 'downloadSoftware': 5, 'report': 3, 'localSWFileCopy': 7, 'uploadLogfile': 8, '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) Enumeration: 'waitingIp': 3, 'beginOperation': 2, 'readingConfiguration': 6, 'executing': 7, 'idle': 1, 'copyingLocal': 5, 'runningIp': 4.

The index value (taken from the genAppFileTable) 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 genAppFileTable) 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.

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

Contains the password to be used if the protocol specified in genOpProtocolType 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, 'tftp': 1, 'localServerTransport': 4, 'localPeerTransport': 3.

The location (including the FULL path) of the file in the server. NOTE: In the case of localPeerTransport this value should be NULL.

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 'genOpLastFailureDisplay' 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. Enumeration: 'nvramWriteError': 11, 'undefinedError': 100, 'busy': 4, 'confFileParseError': 13, 'noError': 1, 'configError': 3, 'fileTooBig': 8, 'confFileGenErr': 12, 'accessViolation': 102, 'genError': 2, 'fileAlreadyExists': 106, 'outOfMemory': 103, 'protocolError': 9, 'illegalOperation': 104, 'unknownTransferId': 105, 'confFileExecError': 14, 'noSuchUser': 107, 'flashWriteError': 10, 'timeout': 5, 'cancelled': 6, 'fileNotFound': 101, '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 'genAppFileTable' 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 'genAppFileTable' of the default Application that the device will boot from when a standard reboot is performed.

The Index in the 'genAppFileTable' 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 'genAppFileTable' are not removable nor can new entries be created. A value of 'dynamic' indicates that entries in the 'genAppFileTable' 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.

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 genOpSourceIndex and genOpDestIndex 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 genOpTable 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). Enumeration: 'runningConfiguration': 1, 'logFile': 6, 'nvramFile': 7, 'swComponent': 10, 'swWebImage': 12, 'swBootImage': 9, 'startupConfiguration': 2, 'defaultConfiguration': 3, 'swRuntimeImage': 8, 'report': 4, 'genConfigFile': 5, 'other': 11.

A description of the application.

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

The current version of the application. If this files does not carry a version this field should be NULL.

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

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.