XF-SOFTWARE-MIB: View SNMP OID List / Download MIB

This MIB contains the objects which support software inventory information.

This table contains information about the load modules that are part of the system releases as described by the xfSwReleaseTable.

Information about 1 software load module.

There are two software releases present on the node: - an active release, normally the most recent release and the one that is running - a passive release, that is the previous release or the one that is currently being download to upgrade the active release. xfSwRelease is an index into the active or passive release. xfSwActiveRelease indicates which release is active.

Unique value within one release for each load module.

Product number of the load module. Normally something like 'CAXR102_012/1'.

Revision of the load module. Normally something like 'R1A'.

Indicates the status of the software upgrade process for this load module. passive(1) the load module is not involved in a upgrade process and is not active. I.e.it is part of the previous software release. upgradeStarted(2) a load module will have this status directly after the SBDF info for this module is loaded and the xfSwLoadModuleAdminStatus of the release was set to upgradeStarted. upgradeFinished(3) indicates that this load modules has been retrieved and burned into the flash memories. This is the state of load modules that are part of an active release. upgradeFailed(4) upgraded has failed for a reason, e.g. file transfer checksum was wrong, see xfSwLoadModuleFailure. upgradeAborted(5) when the manager has aborted the upgrade of the complete release whilst this load module wasn't upgradedFinished yet this will be its status. Enumeration: 'passive': 1, 'upgradeFinished': 3, 'upgradeAborted': 5, 'upgradeStarted': 2, 'upgradeFailed': 4.

The objects specifies the cause of a software upgrade failure for this load module. Enumeration: 'downloadFailure': 1, 'programFailure': 2, 'noFailure': 3.

This object indicates the progress in downloading the respective load module when part of an upgrade of an NE to a software baseline.

This object indicates a textual description of the load module, indicating PIU type as stated by the entPhysicalDescription MO.

This contains the information on the active and passive software releases.

Information about a software release. There are always only two releases. For the active release write is possible but will have no impact and will result in a inconsistentValue error response.

Indicates the Release the info for which this row is applicable.

Product number of the installed software package in this release. Normally something like 'CAXR102 012/1'. For the active release this is a read-only object.

Revision of the installed software package in this Release. Normally something like 'R1A'. For the active release this is a read-only object.

Indicates the desired status for this release. To start a software upgrade the manager has to set xfSwReleaseProductNumber and xfSwReleaseRevision. After that it will set this object to upgradeStarted. Which will lead to downloading the SBDF-file from the FTP Server. For the active release this is a read-only object. Enumeration: 'upgradeTest': 6, 'upgradeAborted': 2, 'upgradeStarted': 1, 'activeAndRunning': 5.

Indicates the status of this release. passive(1) release not involved in upgrade and currently not running. upgradeStarted(2) the release is in the process of being upgraded upgradeFinished(3) All load modules of the release are downloaded and burned in the respective flash memories. testing(4) This release is running as test and not committed yet. upgradeFailed(5) The upgrade to this release failed, e.g. due to FTP server failure. upgradeAborted(6) The manager has order to abort the upgrade to this release. running(7) This is the release that is running now and all new boards should upgrade to. testingFromManual(8) Same as value testing(4) but indicating that this a test phase after a SBL from Manual mode. As such a fall-back will result in manual mode, i.e. no SBL. The 50 series errors are reported by the FTP client on the node. errorInternalError(50) An internal error detected before FTP operation. errorFileStorage(51) Error when erasing flash to store the downloaded file at the node. ftpPingFailed(52) FTP ping failed. ftpNoAccess(53) Not able to send the FTP commands. ftpConnectionDetailsMissing(54) FTP connection details are missing. ftpConnectionDetailsInvalid(55) FTP connection details are invalid. ftpConnectionTimeout(56) FTP connection timeout is detected. ftpNoSuchRemoteFile(57) No such remote file exists. ftpNoSuchRemoteDir(58) No such remote directory exists. The 400 series errors occur when the command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. ftpServiceNotAvailable(421) Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down. Possible causes are transfer timeouts and/or FTP server resets. ftpUnableToOpenDataConnection(425) Can't open data connection. Try changing from PASV to PORT mode. ftpConnectionClosed(426) Connection closed and file transfer is aborted. Possible causes are out of local diskspace and loss of connection. ftpFileBusy(450) Requested file action not taken. File unavailable (e.g file busy). ftpLocalError(451) Requested action aborted due to local error in processing. ftpInsufficienStorageSpace(452) Requested action not taken due to insufficient storage space on the server. The 500 series errors occur when the command was not accepted and the requested action did not take place. ftpSyntaxError(501) FTP Syntax error in parameters or arguments. ftpCommandNotImplemented(502) FTP Command not implemented. ftpBadSequenceCommands(503) Bad sequence of the FTP commands. ftpParameterNotImplemented(504) FTP command not implemented for that parameter. ftpNotLoggedIn(530) Not logged in. Your username and/or password is being rejected, contact the server adminstrator. ftpNeedAccount(532) Need account for storing files. ftpFileUnavailable(550) Requested action not taken. File unavailable (e.g.file not found, no access). Contact the server adminstrator. ftpExceededStorageAllocation(552) Requested file action aborted.Exceeded storage allocation (for current directory or data set). Contact the server adminstrator. ftpFileNameNotAllowed(553) Requested action not taken. File name not allowed. Try changing the file name or getting rid of spaces in the file name. Enumeration: 'ftpNoAccess': 53, 'ftpNoLoggedIn': 530, 'testing': 4, 'ftpFileBusy': 450, 'ftpNoSuchRemoteFile': 57, 'upgradeFinished': 3, 'ftpNoSuchRemoteDir': 58, 'ftpConnectionDetailsMissing': 54, 'ftpFileUnavailable': 550, 'errorInternal': 50, 'ftpPingFailed': 52, 'passive': 1, 'ftpParameterNotImplemented': 504, 'ftpConnectionDetailsInvalid': 55, 'ftpConnectionTimeout': 56, 'ftpConnectionClosed': 426, 'ftpExceededStorageAllocation': 552, 'errorFileStorage': 51, 'ftpLocalError': 451, 'ftpServiceNotAvailable': 421, 'ftpCommandNotImplemented': 502, 'ftpFileNameNotAllowed': 553, 'running': 7, 'ftpInsufficientStorageSpace': 452, 'ftpNeedAccount': 532, 'testingFromManual': 8, 'upgradeAborted': 6, 'upgradeStarted': 2, 'ftpUnableToOpenDataConnection': 425, 'ftpBadSequenceCommands': 503, 'upgradeFailed': 5, 'ftpSyntaxError': 501.

This object indicates whether the SBL information in the SBDF is generated by Ericsson or by an operator. This is based on a check of the SBDF. Of course this will only be a reliable object when the software can distinguish between Ericsson and operator defined SBDFs, i.e. upgrading from R2A. Enumeration: 'definedByEricsson': 1, 'definedByOperator': 2.

Indicates which of the two Releases is active at the moment, i.e. active is the software actually running.

Indicates when the XF NE will warm restart to test the new software release. If all fields have value 0 an immediate boot will be performed.

In case of a scheduled restart, i.e. valid date and time in xfSwBootTime, two different commit procedures can be followed: operatorCommit(1) The manager commits the software release under test by setting the xfSwRelease- AdminState to activeAndRunning. nodeCommit(2) The release under test is accepted when the node is able to establish contact through the DCN with an external IP-address. Default values is operatorCommit(1). Enumeration: 'operatorCommit': 1, 'nodeCommit': 2.

This table holds the information about software present on the boards in the XF-NE. Boards without software will not be in this table.

Entry in the table.

Index to the load module on the board. A board may contain more than one load module.

This object indicates of what type the software is, like DP (Device Processor) or FPGA (Field Programmable Gate Array) or another type. New type can be defined by defining a new OID in a other MIB.

This is a string indicating the product number of the software in the active flash memory.

This is a string indicating the revision of the software in the active flash memory.

Indicates the status of the software on the board: Unknown(1) The status of the software is unknown for example at startup. Active(2) Software on the board is OK and running Upgrading(3) Software is in the process of being upgraded WrongSoftware(4) Wrong software on the board and for some reason not being upgraded yet. MinSoftware revision(5) The board was tried to downgrade to a software revision that is not compatible with the hardware. The xfSwBoardStatus is only of use in case version control is enabled. If version control is not enabled the unit will always runs its software. Enumeration: 'active': 2, 'unknown': 1, 'upgrading': 3, 'wrongSoftware': 4, 'minSoftwareRevision': 5.

This object indicates the progress of the software upgrade process for each individual PIU. This indicates both flash erasing and programming. This object indicates this for both upgrade to a baseline as well as for inserted PIUs. In case the software upgrade of the board takes less than 10 seconds this objects will directly go to 100%.

This is a string indicating the product number of the minimally acceptable software revision for this unit type/variant.

This is a string indicating the revision of the minimally acceptable software revision for this unit type/variant.

This object indicates that software upgrade of this load module on this unit might lead to traffic disturbance. This could for example happen in the exceptional case where the load module includes FPGA code for the traffic system. Enumeration: 'unknown': 1, 'notDisturbing': 3, 'disturbing': 2.

Product number of NPU software in passive bank.

Revision of software in passive bank on NPU.

This object can be used to switch the NPU passive software. As a safety precaution this object is only available when the node is in installation mode or when the node is accessed through the USB port (if present). A warm restart is required to activate the fallback. A switch leads to all xfSwUpgradePreferences being set to their default values, i.e. no version control. Enumeration: 'switch': 1.

Used for DP software load modules.

Used for PCI FPGA load modules.

Used to enable/disable version control. Default: disable.

Used to enable/disable automatic software upgrade. In case xfSwVersionControl is enabled a change of the value will cause all PIUs to be checked again. Default: disable.

Used to enable/disable automatic software downgrade. In case xfSwVersionControl is enabled a change of the value will cause all PIUs to be checked again. Default: disable.

Used to enable/disable setting of new PIUs, that fail to up/downgrade, in 'out of service'. PIUs that are out of service will not be taken into service on the disable/enable transistion. Default: enable.

This table is used to upgrade a single load module. For each known load module an entry is present.

Entry in the table.

Objects used to index the table.

Product number of the load module. Normally something like 'CAXR102_012/1'.

Revision to which the load module should be upgraded. Normally something like 'R1A'.

Indicates the desired status for this release. To start a software upgrade the manager has to set xfSwLmUpgradeRevision. After that it will set this object to upgradeStarted. Which will lead to downloading the SBDF-file from the FTP Server. For the active release write is possible but will have no impact. Enumeration: 'upgradeTest': 4, 'upgradeAborted': 2, 'upgradeStarted': 1, 'activeAndRunning': 3.

Indicates the status of the software upgrade process for this load module. active(1) the load module is active and running on the PIU. upgradeStarted(2) a load module will have this status directly after the SRDF info for this module is loaded and the xfSwLmUpgradeAdminStatus of the release was set to upgradeStarted. upgradeFinished(3) indicates that this load modules has been retreived and burned into the flash memories.This is the state of load modules that are part of an active release. upgradeTested(4) This release is running as test and not committed yet. upgradeFailed(5) upgraded has failed for a reason, e.g. file transfer checksum was wrong, see xfSwLmUpgradeFailure. upgradeAborted(6) when the manager has aborted the upgrade of the complete release whilst this load module wasn't upgradedFinished yet this will be its status. The 50 series errors are reported by the FTP client on the node. errorInternalError(50) An internal error detected before FTP operation. errorFileStorage(51) Error when erasing flash to store the downloaded file at the node. ftpPingFailed(52) FTP ping failed. ftpNoAccess(53) Not able to send the FTP commands. ftpConnectionDetailsMissing(54) FTP connection details are missing. ftpConnectionDetailsInvalid(55) FTP connection details are invalid. ftpConnectionTimeout(56) FTP connection timeout is detected. ftpNoSuchRemoteFile(57) No such remote file exists. ftpNoSuchRemoteDir(58) No such remote directory exists. The 400 series errors occur when the command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. ftpServiceNotAvailable(421) Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down. Possible causes are transfer timeouts and/or FTP server resets. ftpUnableToOpenDataConnection(425) Can't open data connection. Try changing from PASV to PORT mode. ftpConnectionClosed(426) Connection closed and file transfer is aborted. Possible causes are out of local diskspace and loss of connection. ftpFileBusy(450) Requested file action not taken. File unavailable (e.g file busy). ftpLocalError(451) Requested action aborted due to local error in processing. ftpInsufficienStorageSpace(452) Requested action not taken due to insufficient storage space on the server. The 500 series errors occur when the command was not accepted and the requested action did not take place. ftpSyntaxError(501) FTP Syntax error in parameters or arguments. ftpCommandNotImplemented(502) FTP Command not implemented. ftpBadSequenceCommands(503) Bad sequence of the FTP commands. ftpParameterNotImplemented(504) FTP command not implemented for that parameter. ftpNotLoggedIn(530) Not logged in. Your username and/or password is being rejected, contact the server adminstrator. ftpNeedAccount(532) Need account for storing files. ftpFileUnavailable(550) Requested action not taken. File unavailable (e.g.file not found, no access). Contact the server adminstrator. ftpExceededStorageAllocation(552) Requested file action aborted.Exceeded storage allocation (for current directory or data set). Contact the server adminstrator. ftpFileNameNotAllowed(553) Requested action not taken. File name not allowed. Try changing the file name or getting rid of spaces in the file name. Enumeration: 'ftpNoAccess': 53, 'ftpFileBusy': 450, 'ftpNoSuchRemoteFile': 57, 'upgradeFinished': 3, 'ftpNoSuchRemoteDir': 58, 'ftpInsufficienStorageSpace': 452, 'ftpConnectionDetailsMissing': 54, 'ftpFileUnavailable': 550, 'ftpPingFailed': 52, 'ftpParameterNotImplemented': 504, 'ftpNotLoggedIn': 530, 'ftpConnectionDetailsInvalid': 55, 'ftpConnectionTimeout': 56, 'ftpConnectionClosed': 426, 'ftpExceededStorageAllocation': 552, 'errorFileStorage': 51, 'ftpLocalError': 451, 'ftpServiceNotAvailable': 421, 'ftpCommandNotImplemented': 502, 'ftpFileNameNotAllowed': 553, 'errorInternalError': 50, 'active': 1, 'ftpNeedAccount': 532, 'upgradeTested': 4, 'upgradeAborted': 6, 'upgradeStarted': 2, 'ftpUnableToOpenDataConnection': 425, 'ftpBadSequenceCommands': 503, 'upgradeFailed': 5, 'ftpSyntaxError': 501.

This object indicates the progress in downloading the respective load module when part of an upgrade of an inserted PIU.

This object specifies the cause of a software upgrade failure. Enumeration: 'downloadFailure': 1, 'programFailure': 2, 'noFailure': 3.

This object indicates a textual description of the load module, indicating PIU type as stated by the entPhysicalDescription MO.

This objecty indicates the global state of the Software Upgrade process. noUpgrade(0), no Software upgrade ongoing sblStarted(1), a SBL upgrade is started and SBDF and Load Modules are downloading sblWaitForActivate(2), a SBL upgrade is finished and waiting for an activation sblWaitForCommit(3), a SBL upgrade is in test phase and waiting for commit manualStarted(4), a manual upgrade is started and Load Modules are downloading manualWaitForActivate(5), a manual upgrade is finished and waiting for an activation manualWaitForCommit(6), a manual upgrade is in test phase and waiting for commit unitUpgrade(7), an unit is inserted and in the process of upgrading cachingLoadModules(8), software upgrade is in the process of downloading the load modules for cache. preparingForTest(9), a period after a power-up/restart the node prepares to enter the test phase. During this period some units might restart and it is not possible to commit the software upgrade. Bits: 'noUpgrade': 0, 'unitUpgrade': 7, 'manualStarted': 4, 'manualWaitForCommit': 6, 'manualWaitForActivate': 5, 'sblWaitForActivate': 2, 'sblWaitForCommit': 3, 'preparingForTest': 9, 'sblStarted': 1, 'cachingLoadModules': 8.

The compliance statement for SNMP entities which implement everything.

Group of all software related objects.

All objects added for MINI-LINK Traffic Node R2.

Description.