XF-SOFTWARE-MIB

All MIBs › XF-SOFTWARE-MIB

Organization: Ericsson-Norway

Last Updated: 2008-03-06

Category: Ericsson Radio Link

Description:

Manages Ericsson Norway XF device software inventory, version tracking, and upgrade status.

Imported Objects

entPhysicalIndex

OBJECT-TYPE

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DateAndTime
TEXTUAL-CONVENTION

From XF-TOP-MIB

XfProductRevision
XfProductnumber
xfPlatform	OBJECT-IDENTITY

What Is XF-SOFTWARE-MIB?

XF-SOFTWARE-MIB is an Ericsson Norway enterprise MIB dedicated to software inventory management on XF-branded devices, part of Ericsson's access/transport product line. It exposes objects describing installed software components, their version identifiers, and upgrade/activation status rather than interface or environmental data. This makes it a software-status-focused MIB: administrators use it to confirm which firmware/software image is currently active on a device, track pending or in-progress upgrades, and detect version mismatches across a fleet of XF units. As a vendor-specific software-inventory MIB it typically works alongside Ericsson's broader XF hardware and system MIBs rather than any IETF standard. It is deployed in telecom access/transport networks running Ericsson XF equipment where firmware version compliance and upgrade tracking are operational requirements. Engineers can download the XF-SOFTWARE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in XF-SOFTWARE-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

active software/firmware version
software upgrade status
installed software component inventory
version compliance across devices

Supported Devices

Ericsson XF access/transport equipment

Monitoring Examples

An operator would poll the software inventory table to read the currently active version identifier for a given XF unit and compare it against the fleet-wide target version to flag units still pending an upgrade. If the reported upgrade status stays in a pending or in-progress state longer than expected, that signals a stalled or failed firmware upgrade needing investigation. Because the module description confirms this MIB exists specifically to support software inventory information, its primary value is confirming version compliance rather than performance monitoring.

OIDs

OID symbolic	OID numeric	Type	Access	Description
xfDeviceProcessorSoftware	1.3.6.1.4.1.193.81.2.7.1.8.1			Used for DP software load modules.
xfPciFpgaCode	1.3.6.1.4.1.193.81.2.7.1.8.2			Used for PCI FPGA load modules.
xfSoftwareMIB	1.3.6.1.4.1.193.81.2.7			This MIB contains the objects which support software inventory information.
XFS xfSwAcceptFailure	1.3.6.1.4.1.193.81.2.7.1.9.4	XfSwEnableDisable	read-write	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.
XFS xfSwActiveRelease	1.3.6.1.4.1.193.81.2.7.1.3	XfSwRelease	read-only	Indicates which of the two Releases is active at the moment, i.e. active is the software actually running.
XFS xfSwAutoDowngrade	1.3.6.1.4.1.193.81.2.7.1.9.3	XfSwEnableDisable	read-write	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.
XFS xfSwAutoUpgrade	1.3.6.1.4.1.193.81.2.7.1.9.2	XfSwEnableDisable	read-write	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.
xfSwBoardEntry	1.3.6.1.4.1.193.81.2.7.1.6.1		not-accessible	Entry in the table.
I32 xfSwBoardLoadModuleIndex	1.3.6.1.4.1.193.81.2.7.1.6.1.1	Integer32	read-only	Index to the load module on the board. A board may contain more than one load module.
OID xfSwBoardLoadModuleType	1.3.6.1.4.1.193.81.2.7.1.6.1.2	OBJECT IDENTIFIER	read-only	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.
XFP xfSwBoardMinProductNumber	1.3.6.1.4.1.193.81.2.7.1.6.1.7	XfProductnumber	read-only	This is a string indicating the product number of the minimally acceptable software revision for this unit type/variant.
XFP xfSwBoardMinRevision	1.3.6.1.4.1.193.81.2.7.1.6.1.8	XfProductRevision	read-only	This is a string indicating the revision of the minimally acceptable software revision for this unit type/variant.
XFP xfSwBoardProductNumber	1.3.6.1.4.1.193.81.2.7.1.6.1.3	XfProductnumber	read-only	This is a string indicating the product number of the software in the active flash memory.
XFP xfSwBoardRevision	1.3.6.1.4.1.193.81.2.7.1.6.1.4	XfProductRevision	read-only	This is a string indicating the revision of the software in the active flash memory.
INT xfSwBoardStatus	1.3.6.1.4.1.193.81.2.7.1.6.1.5	INTEGER	read-only	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.
I32 xfSwBoardSuProgress	1.3.6.1.4.1.193.81.2.7.1.6.1.6	Integer32	read-only	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%.
xfSwBoardTable	1.3.6.1.4.1.193.81.2.7.1.6		not-accessible	This table holds the information about software present on the boards in the XF-NE. Boards without software will not be in this table.
INT xfSwBoardTrafficDisturbance	1.3.6.1.4.1.193.81.2.7.1.6.1.9	INTEGER	read-only	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.
DAT xfSwBootTime	1.3.6.1.4.1.193.81.2.7.1.4	DateAndTime	read-write	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.
INT xfSwCommitType	1.3.6.1.4.1.193.81.2.7.1.5	INTEGER	read-write	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).
xfSwCompliances	1.3.6.1.4.1.193.81.2.7.2.1
xfSwConformance	1.3.6.1.4.1.193.81.2.7.2
xfSwFullCompliance	1.3.6.1.4.1.193.81.2.7.2.1.1			The compliance statement for SNMP entities which implement everything.
BIT xfSwGlobalState	1.3.6.1.4.1.193.81.2.7.1.11	Bits	read-only	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.
xfSwGroup	1.3.6.1.4.1.193.81.2.7.2.2.1			Group of all software related objects.
xfSwGroups	1.3.6.1.4.1.193.81.2.7.2.2
INT xfSwLmUpgradeAdminStatus	1.3.6.1.4.1.193.81.2.7.1.10.1.6	INTEGER	read-write	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.
STR xfSwLmUpgradeDescription	1.3.6.1.4.1.193.81.2.7.1.10.1.10	SnmpAdminString	read-only	This object indicates a textual description of the load module, indicating PIU type as stated by the entPhysicalDescription MO.
xfSwLmUpgradeEntry	1.3.6.1.4.1.193.81.2.7.1.10.1		not-accessible	Entry in the table.
INT xfSwLmUpgradeFailure	1.3.6.1.4.1.193.81.2.7.1.10.1.9	INTEGER	read-only	This object specifies the cause of a software upgrade failure.
I32 xfSwLmUpgradeIndex	1.3.6.1.4.1.193.81.2.7.1.10.1.1	Integer32	read-only	Objects used to index the table.
INT xfSwLmUpgradeOperStatus	1.3.6.1.4.1.193.81.2.7.1.10.1.7	INTEGER	read-only	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.
XFP xfSwLmUpgradeProductNumber	1.3.6.1.4.1.193.81.2.7.1.10.1.3	XfProductnumber	read-only	Product number of the load module. Normally something like 'CAXR102_012/1'.
I32 xfSwLmUpgradeProgress	1.3.6.1.4.1.193.81.2.7.1.10.1.8	Integer32	read-only	This object indicates the progress in downloading the respective load module when part of an upgrade of an inserted PIU.
XFP xfSwLmUpgradeRevision	1.3.6.1.4.1.193.81.2.7.1.10.1.4	XfProductRevision	read-write	Revision to which the load module should be upgraded. Normally something like 'R1A'.
xfSwLmUpgradeTable	1.3.6.1.4.1.193.81.2.7.1.10		not-accessible	This table is used to upgrade a single load module. For each known load module an entry is present.
STR xfSwLoadModuleDescription	1.3.6.1.4.1.193.81.2.7.1.1.1.9	SnmpAdminString	read-only	This object indicates a textual description of the load module, indicating PIU type as stated by the entPhysicalDescription MO.
xfSwLoadModuleEntry	1.3.6.1.4.1.193.81.2.7.1.1.1		not-accessible	Information about 1 software load module.
INT xfSwLoadModuleFailure	1.3.6.1.4.1.193.81.2.7.1.1.1.6	INTEGER	read-only	The objects specifies the cause of a software upgrade failure for this load module.
I32 xfSwLoadModuleIndex	1.3.6.1.4.1.193.81.2.7.1.1.1.2	Integer32	read-only	Unique value within one release for each load module.
INT xfSwLoadModuleOperStatus	1.3.6.1.4.1.193.81.2.7.1.1.1.5	INTEGER	read-only	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.
XFP xfSwLoadModuleProductNumber	1.3.6.1.4.1.193.81.2.7.1.1.1.3	XfProductnumber	read-only	Product number of the load module. Normally something like 'CAXR102_012/1'.
I32 xfSwLoadModuleProgress	1.3.6.1.4.1.193.81.2.7.1.1.1.8	Integer32	read-only	This object indicates the progress in downloading the respective load module when part of an upgrade of an NE to a software baseline.
XFP xfSwLoadModuleRevision	1.3.6.1.4.1.193.81.2.7.1.1.1.4	XfProductRevision	read-only	Revision of the load module. Normally something like 'R1A'.
xfSwLoadModuleTable	1.3.6.1.4.1.193.81.2.7.1.1		not-accessible	This table contains information about the load modules that are part of the system releases as described by the xfSwReleaseTable.
xfSwLoadModuleTypes	1.3.6.1.4.1.193.81.2.7.1.8
xfSwNpuObjects	1.3.6.1.4.1.193.81.2.7.1.7
XFP xfSwNpuPassiveProductNumber	1.3.6.1.4.1.193.81.2.7.1.7.1	XfProductnumber	read-only	Product number of NPU software in passive bank.
XFP xfSwNpuPassiveRevision	1.3.6.1.4.1.193.81.2.7.1.7.2	XfProductRevision	read-only	Revision of software in passive bank on NPU.
INT xfSwNpuPassiveSwitch	1.3.6.1.4.1.193.81.2.7.1.7.3	INTEGER	read-write	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.
xfSwObjects	1.3.6.1.4.1.193.81.2.7.1
xfSwObsoleteGroup	1.3.6.1.4.1.193.81.2.7.2.2.3			Description.
XFS xfSwRelease	1.3.6.1.4.1.193.81.2.7.1.1.1.1	XfSwRelease	read-only	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.
INT xfSwReleaseAdminStatus	1.3.6.1.4.1.193.81.2.7.1.2.1.4	INTEGER	read-write	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.
xfSwReleaseEntry	1.3.6.1.4.1.193.81.2.7.1.2.1		not-accessible	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.
XFS xfSwReleaseIndex	1.3.6.1.4.1.193.81.2.7.1.2.1.1	XfSwRelease	read-only	Indicates the Release the info for which this row is applicable.
INT xfSwReleaseOperStatus	1.3.6.1.4.1.193.81.2.7.1.2.1.5	INTEGER	read-only	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.
XFP xfSwReleaseProductNumber	1.3.6.1.4.1.193.81.2.7.1.2.1.2	XfProductnumber	read-write	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.
XFP xfSwReleaseRevision	1.3.6.1.4.1.193.81.2.7.1.2.1.3	XfProductRevision	read-write	Revision of the installed software package in this Release. Normally something like 'R1A'. For the active release this is a read-only object.
INT xfSwReleaseSBLType	1.3.6.1.4.1.193.81.2.7.1.2.1.6	INTEGER	read-only	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.
xfSwReleaseTable	1.3.6.1.4.1.193.81.2.7.1.2		not-accessible	This contains the information on the active and passive software releases.
xfSwUpgradePreferences	1.3.6.1.4.1.193.81.2.7.1.9
XFS xfSwVersionControl	1.3.6.1.4.1.193.81.2.7.1.9.1	XfSwEnableDisable	read-write	Used to enable/disable version control. Default: disable.
xSwGroupR2	1.3.6.1.4.1.193.81.2.7.2.2.2			All objects added for MINI-LINK Traffic Node R2.

OID symbolic	OID numeric	Type	Access	Description
xfSoftwareMIB	1.3.6.1.4.1.193.81.2.7			This MIB contains the objects which support software inventory information.
xfSwObjects	1.3.6.1.4.1.193.81.2.7.1
xfSwLoadModuleTable	1.3.6.1.4.1.193.81.2.7.1.1		not-accessible	This table contains information about the load modules that are part of the system releases as described by the xfSwReleaseTable.
xfSwLoadModuleEntry	1.3.6.1.4.1.193.81.2.7.1.1.1		not-accessible	Information about 1 software load module.
XFS xfSwRelease	1.3.6.1.4.1.193.81.2.7.1.1.1.1	XfSwRelease	read-only	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.
I32 xfSwLoadModuleIndex	1.3.6.1.4.1.193.81.2.7.1.1.1.2	Integer32	read-only	Unique value within one release for each load module.
XFP xfSwLoadModuleProductNumber	1.3.6.1.4.1.193.81.2.7.1.1.1.3	XfProductnumber	read-only	Product number of the load module. Normally something like 'CAXR102_012/1'.
XFP xfSwLoadModuleRevision	1.3.6.1.4.1.193.81.2.7.1.1.1.4	XfProductRevision	read-only	Revision of the load module. Normally something like 'R1A'.
INT xfSwLoadModuleOperStatus	1.3.6.1.4.1.193.81.2.7.1.1.1.5	INTEGER	read-only	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.
INT xfSwLoadModuleFailure	1.3.6.1.4.1.193.81.2.7.1.1.1.6	INTEGER	read-only	The objects specifies the cause of a software upgrade failure for this load module.
I32 xfSwLoadModuleProgress	1.3.6.1.4.1.193.81.2.7.1.1.1.8	Integer32	read-only	This object indicates the progress in downloading the respective load module when part of an upgrade of an NE to a software baseline.
STR xfSwLoadModuleDescription	1.3.6.1.4.1.193.81.2.7.1.1.1.9	SnmpAdminString	read-only	This object indicates a textual description of the load module, indicating PIU type as stated by the entPhysicalDescription MO.
xfSwReleaseTable	1.3.6.1.4.1.193.81.2.7.1.2		not-accessible	This contains the information on the active and passive software releases.
xfSwReleaseEntry	1.3.6.1.4.1.193.81.2.7.1.2.1		not-accessible	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.
XFS xfSwReleaseIndex	1.3.6.1.4.1.193.81.2.7.1.2.1.1	XfSwRelease	read-only	Indicates the Release the info for which this row is applicable.
XFP xfSwReleaseProductNumber	1.3.6.1.4.1.193.81.2.7.1.2.1.2	XfProductnumber	read-write	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.
XFP xfSwReleaseRevision	1.3.6.1.4.1.193.81.2.7.1.2.1.3	XfProductRevision	read-write	Revision of the installed software package in this Release. Normally something like 'R1A'. For the active release this is a read-only object.
INT xfSwReleaseAdminStatus	1.3.6.1.4.1.193.81.2.7.1.2.1.4	INTEGER	read-write	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.
INT xfSwReleaseOperStatus	1.3.6.1.4.1.193.81.2.7.1.2.1.5	INTEGER	read-only	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.
INT xfSwReleaseSBLType	1.3.6.1.4.1.193.81.2.7.1.2.1.6	INTEGER	read-only	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.
XFS xfSwActiveRelease	1.3.6.1.4.1.193.81.2.7.1.3	XfSwRelease	read-only	Indicates which of the two Releases is active at the moment, i.e. active is the software actually running.
DAT xfSwBootTime	1.3.6.1.4.1.193.81.2.7.1.4	DateAndTime	read-write	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.
INT xfSwCommitType	1.3.6.1.4.1.193.81.2.7.1.5	INTEGER	read-write	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).
xfSwBoardTable	1.3.6.1.4.1.193.81.2.7.1.6		not-accessible	This table holds the information about software present on the boards in the XF-NE. Boards without software will not be in this table.
xfSwBoardEntry	1.3.6.1.4.1.193.81.2.7.1.6.1		not-accessible	Entry in the table.
I32 xfSwBoardLoadModuleIndex	1.3.6.1.4.1.193.81.2.7.1.6.1.1	Integer32	read-only	Index to the load module on the board. A board may contain more than one load module.
OID xfSwBoardLoadModuleType	1.3.6.1.4.1.193.81.2.7.1.6.1.2	OBJECT IDENTIFIER	read-only	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.
XFP xfSwBoardProductNumber	1.3.6.1.4.1.193.81.2.7.1.6.1.3	XfProductnumber	read-only	This is a string indicating the product number of the software in the active flash memory.
XFP xfSwBoardRevision	1.3.6.1.4.1.193.81.2.7.1.6.1.4	XfProductRevision	read-only	This is a string indicating the revision of the software in the active flash memory.
INT xfSwBoardStatus	1.3.6.1.4.1.193.81.2.7.1.6.1.5	INTEGER	read-only	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.
I32 xfSwBoardSuProgress	1.3.6.1.4.1.193.81.2.7.1.6.1.6	Integer32	read-only	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%.
XFP xfSwBoardMinProductNumber	1.3.6.1.4.1.193.81.2.7.1.6.1.7	XfProductnumber	read-only	This is a string indicating the product number of the minimally acceptable software revision for this unit type/variant.
XFP xfSwBoardMinRevision	1.3.6.1.4.1.193.81.2.7.1.6.1.8	XfProductRevision	read-only	This is a string indicating the revision of the minimally acceptable software revision for this unit type/variant.
INT xfSwBoardTrafficDisturbance	1.3.6.1.4.1.193.81.2.7.1.6.1.9	INTEGER	read-only	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.
xfSwNpuObjects	1.3.6.1.4.1.193.81.2.7.1.7
XFP xfSwNpuPassiveProductNumber	1.3.6.1.4.1.193.81.2.7.1.7.1	XfProductnumber	read-only	Product number of NPU software in passive bank.
XFP xfSwNpuPassiveRevision	1.3.6.1.4.1.193.81.2.7.1.7.2	XfProductRevision	read-only	Revision of software in passive bank on NPU.
INT xfSwNpuPassiveSwitch	1.3.6.1.4.1.193.81.2.7.1.7.3	INTEGER	read-write	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.
xfSwLoadModuleTypes	1.3.6.1.4.1.193.81.2.7.1.8
xfDeviceProcessorSoftware	1.3.6.1.4.1.193.81.2.7.1.8.1			Used for DP software load modules.
xfPciFpgaCode	1.3.6.1.4.1.193.81.2.7.1.8.2			Used for PCI FPGA load modules.
xfSwUpgradePreferences	1.3.6.1.4.1.193.81.2.7.1.9
XFS xfSwVersionControl	1.3.6.1.4.1.193.81.2.7.1.9.1	XfSwEnableDisable	read-write	Used to enable/disable version control. Default: disable.
XFS xfSwAutoUpgrade	1.3.6.1.4.1.193.81.2.7.1.9.2	XfSwEnableDisable	read-write	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.
XFS xfSwAutoDowngrade	1.3.6.1.4.1.193.81.2.7.1.9.3	XfSwEnableDisable	read-write	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.
XFS xfSwAcceptFailure	1.3.6.1.4.1.193.81.2.7.1.9.4	XfSwEnableDisable	read-write	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.
xfSwLmUpgradeTable	1.3.6.1.4.1.193.81.2.7.1.10		not-accessible	This table is used to upgrade a single load module. For each known load module an entry is present.
xfSwLmUpgradeEntry	1.3.6.1.4.1.193.81.2.7.1.10.1		not-accessible	Entry in the table.
I32 xfSwLmUpgradeIndex	1.3.6.1.4.1.193.81.2.7.1.10.1.1	Integer32	read-only	Objects used to index the table.
XFP xfSwLmUpgradeProductNumber	1.3.6.1.4.1.193.81.2.7.1.10.1.3	XfProductnumber	read-only	Product number of the load module. Normally something like 'CAXR102_012/1'.
XFP xfSwLmUpgradeRevision	1.3.6.1.4.1.193.81.2.7.1.10.1.4	XfProductRevision	read-write	Revision to which the load module should be upgraded. Normally something like 'R1A'.
INT xfSwLmUpgradeAdminStatus	1.3.6.1.4.1.193.81.2.7.1.10.1.6	INTEGER	read-write	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.
INT xfSwLmUpgradeOperStatus	1.3.6.1.4.1.193.81.2.7.1.10.1.7	INTEGER	read-only	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.
I32 xfSwLmUpgradeProgress	1.3.6.1.4.1.193.81.2.7.1.10.1.8	Integer32	read-only	This object indicates the progress in downloading the respective load module when part of an upgrade of an inserted PIU.
INT xfSwLmUpgradeFailure	1.3.6.1.4.1.193.81.2.7.1.10.1.9	INTEGER	read-only	This object specifies the cause of a software upgrade failure.
STR xfSwLmUpgradeDescription	1.3.6.1.4.1.193.81.2.7.1.10.1.10	SnmpAdminString	read-only	This object indicates a textual description of the load module, indicating PIU type as stated by the entPhysicalDescription MO.
BIT xfSwGlobalState	1.3.6.1.4.1.193.81.2.7.1.11	Bits	read-only	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.
xfSwConformance	1.3.6.1.4.1.193.81.2.7.2
xfSwCompliances	1.3.6.1.4.1.193.81.2.7.2.1
xfSwFullCompliance	1.3.6.1.4.1.193.81.2.7.2.1.1			The compliance statement for SNMP entities which implement everything.
xfSwGroups	1.3.6.1.4.1.193.81.2.7.2.2
xfSwGroup	1.3.6.1.4.1.193.81.2.7.2.2.1			Group of all software related objects.
xSwGroupR2	1.3.6.1.4.1.193.81.2.7.2.2.2			All objects added for MINI-LINK Traffic Node R2.
xfSwObsoleteGroup	1.3.6.1.4.1.193.81.2.7.2.2.3			Description.

Bits (1)
BIT xfSwGlobalState	1.3.6.1.4.1.193.81.2.7.1.11	Bits	read-only	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.
DateAndTime (1)
DAT xfSwBootTime	1.3.6.1.4.1.193.81.2.7.1.4	DateAndTime	read-write	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.
INTEGER (12)
INT xfSwBoardStatus	1.3.6.1.4.1.193.81.2.7.1.6.1.5	INTEGER	read-only	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.
INT xfSwBoardTrafficDisturbance	1.3.6.1.4.1.193.81.2.7.1.6.1.9	INTEGER	read-only	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.
INT xfSwCommitType	1.3.6.1.4.1.193.81.2.7.1.5	INTEGER	read-write	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).
INT xfSwLmUpgradeAdminStatus	1.3.6.1.4.1.193.81.2.7.1.10.1.6	INTEGER	read-write	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.
INT xfSwLmUpgradeFailure	1.3.6.1.4.1.193.81.2.7.1.10.1.9	INTEGER	read-only	This object specifies the cause of a software upgrade failure.
INT xfSwLmUpgradeOperStatus	1.3.6.1.4.1.193.81.2.7.1.10.1.7	INTEGER	read-only	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.
INT xfSwLoadModuleFailure	1.3.6.1.4.1.193.81.2.7.1.1.1.6	INTEGER	read-only	The objects specifies the cause of a software upgrade failure for this load module.
INT xfSwLoadModuleOperStatus	1.3.6.1.4.1.193.81.2.7.1.1.1.5	INTEGER	read-only	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.
INT xfSwNpuPassiveSwitch	1.3.6.1.4.1.193.81.2.7.1.7.3	INTEGER	read-write	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.
INT xfSwReleaseAdminStatus	1.3.6.1.4.1.193.81.2.7.1.2.1.4	INTEGER	read-write	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.
INT xfSwReleaseOperStatus	1.3.6.1.4.1.193.81.2.7.1.2.1.5	INTEGER	read-only	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.
INT xfSwReleaseSBLType	1.3.6.1.4.1.193.81.2.7.1.2.1.6	INTEGER	read-only	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.
Integer32 (6)
I32 xfSwBoardLoadModuleIndex	1.3.6.1.4.1.193.81.2.7.1.6.1.1	Integer32	read-only	Index to the load module on the board. A board may contain more than one load module.
I32 xfSwBoardSuProgress	1.3.6.1.4.1.193.81.2.7.1.6.1.6	Integer32	read-only	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%.
I32 xfSwLmUpgradeIndex	1.3.6.1.4.1.193.81.2.7.1.10.1.1	Integer32	read-only	Objects used to index the table.
I32 xfSwLmUpgradeProgress	1.3.6.1.4.1.193.81.2.7.1.10.1.8	Integer32	read-only	This object indicates the progress in downloading the respective load module when part of an upgrade of an inserted PIU.
I32 xfSwLoadModuleIndex	1.3.6.1.4.1.193.81.2.7.1.1.1.2	Integer32	read-only	Unique value within one release for each load module.
I32 xfSwLoadModuleProgress	1.3.6.1.4.1.193.81.2.7.1.1.1.8	Integer32	read-only	This object indicates the progress in downloading the respective load module when part of an upgrade of an NE to a software baseline.
OBJECT IDENTIFIER (1)
OID xfSwBoardLoadModuleType	1.3.6.1.4.1.193.81.2.7.1.6.1.2	OBJECT IDENTIFIER	read-only	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.
SnmpAdminString (2)
STR xfSwLmUpgradeDescription	1.3.6.1.4.1.193.81.2.7.1.10.1.10	SnmpAdminString	read-only	This object indicates a textual description of the load module, indicating PIU type as stated by the entPhysicalDescription MO.
STR xfSwLoadModuleDescription	1.3.6.1.4.1.193.81.2.7.1.1.1.9	SnmpAdminString	read-only	This object indicates a textual description of the load module, indicating PIU type as stated by the entPhysicalDescription MO.
XfProductnumber (6)
XFP xfSwBoardMinProductNumber	1.3.6.1.4.1.193.81.2.7.1.6.1.7	XfProductnumber	read-only	This is a string indicating the product number of the minimally acceptable software revision for this unit type/variant.
XFP xfSwBoardProductNumber	1.3.6.1.4.1.193.81.2.7.1.6.1.3	XfProductnumber	read-only	This is a string indicating the product number of the software in the active flash memory.
XFP xfSwLmUpgradeProductNumber	1.3.6.1.4.1.193.81.2.7.1.10.1.3	XfProductnumber	read-only	Product number of the load module. Normally something like 'CAXR102_012/1'.
XFP xfSwLoadModuleProductNumber	1.3.6.1.4.1.193.81.2.7.1.1.1.3	XfProductnumber	read-only	Product number of the load module. Normally something like 'CAXR102_012/1'.
XFP xfSwNpuPassiveProductNumber	1.3.6.1.4.1.193.81.2.7.1.7.1	XfProductnumber	read-only	Product number of NPU software in passive bank.
XFP xfSwReleaseProductNumber	1.3.6.1.4.1.193.81.2.7.1.2.1.2	XfProductnumber	read-write	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.
XfProductRevision (6)
XFP xfSwBoardMinRevision	1.3.6.1.4.1.193.81.2.7.1.6.1.8	XfProductRevision	read-only	This is a string indicating the revision of the minimally acceptable software revision for this unit type/variant.
XFP xfSwBoardRevision	1.3.6.1.4.1.193.81.2.7.1.6.1.4	XfProductRevision	read-only	This is a string indicating the revision of the software in the active flash memory.
XFP xfSwLmUpgradeRevision	1.3.6.1.4.1.193.81.2.7.1.10.1.4	XfProductRevision	read-write	Revision to which the load module should be upgraded. Normally something like 'R1A'.
XFP xfSwLoadModuleRevision	1.3.6.1.4.1.193.81.2.7.1.1.1.4	XfProductRevision	read-only	Revision of the load module. Normally something like 'R1A'.
XFP xfSwNpuPassiveRevision	1.3.6.1.4.1.193.81.2.7.1.7.2	XfProductRevision	read-only	Revision of software in passive bank on NPU.
XFP xfSwReleaseRevision	1.3.6.1.4.1.193.81.2.7.1.2.1.3	XfProductRevision	read-write	Revision of the installed software package in this Release. Normally something like 'R1A'. For the active release this is a read-only object.
XfSwEnableDisable (4)
XFS xfSwAcceptFailure	1.3.6.1.4.1.193.81.2.7.1.9.4	XfSwEnableDisable	read-write	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.
XFS xfSwAutoDowngrade	1.3.6.1.4.1.193.81.2.7.1.9.3	XfSwEnableDisable	read-write	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.
XFS xfSwAutoUpgrade	1.3.6.1.4.1.193.81.2.7.1.9.2	XfSwEnableDisable	read-write	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.
XFS xfSwVersionControl	1.3.6.1.4.1.193.81.2.7.1.9.1	XfSwEnableDisable	read-write	Used to enable/disable version control. Default: disable.
XfSwRelease (3)
XFS xfSwActiveRelease	1.3.6.1.4.1.193.81.2.7.1.3	XfSwRelease	read-only	Indicates which of the two Releases is active at the moment, i.e. active is the software actually running.
XFS xfSwRelease	1.3.6.1.4.1.193.81.2.7.1.1.1.1	XfSwRelease	read-only	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.
XFS xfSwReleaseIndex	1.3.6.1.4.1.193.81.2.7.1.2.1.1	XfSwRelease	read-only	Indicates the Release the info for which this row is applicable.
No type (22)
xfDeviceProcessorSoftware	1.3.6.1.4.1.193.81.2.7.1.8.1			Used for DP software load modules.
xfPciFpgaCode	1.3.6.1.4.1.193.81.2.7.1.8.2			Used for PCI FPGA load modules.
xfSoftwareMIB	1.3.6.1.4.1.193.81.2.7			This MIB contains the objects which support software inventory information.
xfSwBoardEntry	1.3.6.1.4.1.193.81.2.7.1.6.1		not-accessible	Entry in the table.
xfSwBoardTable	1.3.6.1.4.1.193.81.2.7.1.6		not-accessible	This table holds the information about software present on the boards in the XF-NE. Boards without software will not be in this table.
xfSwCompliances	1.3.6.1.4.1.193.81.2.7.2.1
xfSwConformance	1.3.6.1.4.1.193.81.2.7.2
xfSwFullCompliance	1.3.6.1.4.1.193.81.2.7.2.1.1			The compliance statement for SNMP entities which implement everything.
xfSwGroup	1.3.6.1.4.1.193.81.2.7.2.2.1			Group of all software related objects.
xfSwGroups	1.3.6.1.4.1.193.81.2.7.2.2
xfSwLmUpgradeEntry	1.3.6.1.4.1.193.81.2.7.1.10.1		not-accessible	Entry in the table.
xfSwLmUpgradeTable	1.3.6.1.4.1.193.81.2.7.1.10		not-accessible	This table is used to upgrade a single load module. For each known load module an entry is present.
xfSwLoadModuleEntry	1.3.6.1.4.1.193.81.2.7.1.1.1		not-accessible	Information about 1 software load module.
xfSwLoadModuleTable	1.3.6.1.4.1.193.81.2.7.1.1		not-accessible	This table contains information about the load modules that are part of the system releases as described by the xfSwReleaseTable.
xfSwLoadModuleTypes	1.3.6.1.4.1.193.81.2.7.1.8
xfSwNpuObjects	1.3.6.1.4.1.193.81.2.7.1.7
xfSwObjects	1.3.6.1.4.1.193.81.2.7.1
xfSwObsoleteGroup	1.3.6.1.4.1.193.81.2.7.2.2.3			Description.
xfSwReleaseEntry	1.3.6.1.4.1.193.81.2.7.1.2.1		not-accessible	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.
xfSwReleaseTable	1.3.6.1.4.1.193.81.2.7.1.2		not-accessible	This contains the information on the active and passive software releases.
xfSwUpgradePreferences	1.3.6.1.4.1.193.81.2.7.1.9
xSwGroupR2	1.3.6.1.4.1.193.81.2.7.2.2.2			All objects added for MINI-LINK Traffic Node R2.

RFC description

Tracks software inventory, upgrade status, and load module management for Ericsson XF platform network devices.

Start monitoring Ericsson XF access/transport equipment (software-inventory/version/upgrade status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download XF-SOFTWARE-MIB

This MIB depends on

Related MIBs

What Is XF-SOFTWARE-MIB?

What Can Be Monitored

Supported Devices

Monitoring Examples

RFC description