ALCATEL-IND1-SYSTEM-MIB :: systemServicesAction

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsALCATEL-IND1-SYSTEM-MIBsystemServicesAction

systemServicesAction

Module: ALCATEL-IND1-SYSTEM-MIB

OID (symbolic): ALCATEL-IND1-SYSTEM-MIB::systemServicesAction

OID (numeric): 1.3.6.1.4.1.6486.801.1.1.1.2.1.1.5.24

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object identifies which of the above Actions is to be performed by the System Services Application. Most Actions require one or more parameters be set before the Action is executed. systemServicesAction - 26 for bootrom, 27 for default miniboot, and 28 for backup miniboot use systemServicesArg1 for name of the file

scp- the first 2 arguments are going to be used. Set arg 1 with the source and the arg 2 with the destination file(s). E.g. scp LocalDir/testfileX.txt admin@10.255.11.1:RemoteDir/testfileX.txt For mount and umount, systemServicesArg1 specifies the mount point (such as /uflash). For newfs, systemServicesArg1 contains the name of the file-system (/uflash or /flash) which will be created. On /uflash, a FAT16 file system is created with long name naming conventions. For fsck, systemServicesArg1 contains the name of the file-system (/uflash or /flash) which will be checked and systemServicesArg2 will contain the string repair or no-repair depending on if autocorrection is requested. To see all file systems currently mounted, refer to the systemFileSystemTable. For backup and restore, systemServicesArg1 contains the archive name and systemServicesArg2 through Arg9 contains the directories and/or files to be archived/extracted. For newfs, fsck, backup and restore, the systemServicesActionPercentComplete variable can be inspected to see a progress indication.

What is systemServicesAction?

An integer enumeration (mkdir, rmdir, copy, etc.) controlling which system action executes. Network engineers write to this object to trigger file operations or firmware updates on the device. Example: setting value 26 to initiate bootrom update, where Arg1 specifies the ROM file location.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6486.801.1.1.1.2.1.1.5.24
snmpwalk -v2c -c public <target> ALCATEL-IND1-SYSTEM-MIB::systemServicesAction

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6486.801.1.1.1.2.1.1.5.24.1
snmpget -v2c -c public <target> ALCATEL-IND1-SYSTEM-MIB::systemServicesAction.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.6486.801.1.1.1.2.1.1.5.24.1 i <value>

Start monitoring Alcatel-Lucent Enterprise OmniSwitch switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ALCATEL-IND1-SYSTEM-MIB::systemServicesAction OID value, configure state conditions and alerts, and monitor any Alcatel-Lucent Enterprise OmniSwitch switches from a single console.

OID Breakdown

Upper-level ancestors (12 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.6486alcatelALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801alcatelIND1BaseMIBALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1alcatelIND1ManagementALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1.1managementIND1HardwareALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1.1.1hardwareIND1EntitiesALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1.1.1.2hardentIND1SystemALCATEL-IND1-BASE
Numeric OIDNameModule
1.3.6.1.4.1.6486.801.1.1.1.2.1alcatelIND1SystemMIBALCATEL-IND1-SYSTEM-MIB
1.3.6.1.4.1.6486.801.1.1.1.2.1.1alcatelIND1SystemMIBObjectsALCATEL-IND1-SYSTEM-MIB
1.3.6.1.4.1.6486.801.1.1.1.2.1.1.5systemServicesALCATEL-IND1-SYSTEM-MIB
1.3.6.1.4.1.6486.801.1.1.1.2.1.1.5.24systemServicesActionALCATEL-IND1-SYSTEM-MIB