A3COM0048-EMBEDDED-SCRIPTS

All MIBs › A3COM0048-EMBEDDED-SCRIPTS

Category: Switch Management

Description: Manages embedded script execution and scheduling on 3Com intelligent network devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock 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.

What Is A3COM0048-EMBEDDED-SCRIPTS?

This MIB manages embedded command scripts (macros) and their scheduled/on-demand execution on 3Com intelligent network devices. It exposes a macro-definition table (name, command string, owner, status) and a separate execution table tracking which unit ran a given macro and its process status. This gives clear software/process-status monitoring value: cmdExecProcessStatus lets an operator confirm whether a scheduled or triggered script executed successfully, failed, or is still running, similar to monitoring a job/task queue on a general-purpose OS. It is a 3Com-proprietary extension with no strong dependency on other standard MIBs beyond basic SNMPv2 conventions. It's deployed on 3Com switches/routers that support on-device command scripting/automation, and administrators typically load the A3COM0048-EMBEDDED-SCRIPTS MIB into their management tools to track macro execution status.

IPNetwork Monitor allows you to monitor SNMP objects defined in A3COM0048-EMBEDDED-SCRIPTS. 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.

Supported Devices

3Com switches/routers

Monitoring Examples

An admin would poll cmdExecProcessStatus in cmdExecTable (keyed by cmdExecUnit and cmdExecIndex) to confirm whether a scheduled configuration macro completed successfully or is stuck/failed on a particular stack unit, and cross-reference cmdMacroName and cmdMacroString in cmdMacroTable to verify exactly which command sequence was executed and by which cmdMacroOwner, useful when diagnosing an unexpected configuration change traced to an automated script.

What Can Be Monitored

macro/script execution status
script name and command content
script owner
macro status (active/inactive)
per-unit execution status

Imported Objects

From A3COM0004-GENERIC

rmonExtensions

OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1213-MIB

DisplayString

From RMON-MIB

EntryStatus
OwnerString

OIDs

OID symbolic	OID numeric	Type	Access	Description
command	1.3.6.1.4.1.43.10.25.5
cmdMacroTable	1.3.6.1.4.1.43.10.25.5.1		not-accessible	Extended RMON table that provides a macro execution facility on the remote unit.
cmdMacroEntry	1.3.6.1.4.1.43.10.25.5.1.1		not-accessible
INT cmdMacroIndex	1.3.6.1.4.1.43.10.25.5.1.1.1	INTEGER	not-accessible	Standard RMON index column.
STR cmdMacroName	1.3.6.1.4.1.43.10.25.5.1.1.2	DisplayString	read-write	A short text name for this macro. This name can be referenced in the cmdTable to execute a script.
STR cmdMacroString	1.3.6.1.4.1.43.10.25.5.1.1.3	DisplayString	read-write	Text macro that is represented by this control entry.
STR cmdMacroOwner	1.3.6.1.4.1.43.10.25.5.1.1.4	OwnerString	read-write	RMON Owner of this process.
ENT cmdMacroStatus	1.3.6.1.4.1.43.10.25.5.1.1.5	EntryStatus	read-write	Rmon RowStatus for this macro definition.
cmdExecTable	1.3.6.1.4.1.43.10.25.5.2		not-accessible	Extended RMON table that provides a script execution facility on the remote unit. Note that scripts executed by this table do not have to reside in the macro table. A script is identified by its 'cmdExecMacroName'. The agent will search all available script sources for that named script. The script _may_ be found in the macro table but this is not mandated.
cmdExecEntry	1.3.6.1.4.1.43.10.25.5.2.1		not-accessible
INT cmdExecUnit	1.3.6.1.4.1.43.10.25.5.2.1.1	INTEGER	not-accessible	Identifies one of a number of different 'execution units'. Genrally each of these is a separate processor in a distributed environment.
INT cmdExecIndex	1.3.6.1.4.1.43.10.25.5.2.1.2	INTEGER	not-accessible	Standard RMON index column.
INT cmdExecProcessStatus	1.3.6.1.4.1.43.10.25.5.2.1.3	INTEGER	read-only	The current status of this process. The various possible values are described as follows: inactive : This process is not currently executing any script. This is the default state after creating a row in the table. running: The process is currently executing a script, and that script is not currently blocked by any internal asynchronous activity. 'running' actually means that this process is capable of being scheduled and is in a 'ready to run' scheduling queue. suspended: The script being executed by this process is currently blocked waiting for the completion of some asynchronous activity. dying: The script that was being executed by this process has completed and is waiting to be tidied up. When the tidyup has been completed this process will either automatically be destroyed or will enter the 'inactive' state. paused: The script being executed has been manually stopped, generally for debug purposes. A script can enter this state either voluntarily be requesting the system to stop it (ie similar to a breakpoint) or can be paused by writing to the cmdExecOperation variable. searching: When a process is given a script to execute the engine must first find that script. The script is identified by name (spe cified in cmdExecMacroName). The agent must search all possible sources for the script, which may take some time. The MIB allows the script to be specified by any name and so some implementations may allow the name to identify a file on some remote file system, for example by using a URL. While the agent searches for the script the process enters the 'searching' state. If the agent locates the script it will enter the 'running' state. If the script cannot be located then the process re-enters the 'inactive' state.
TIK cmdExecStartTime	1.3.6.1.4.1.43.10.25.5.2.1.4	TimeTicks	read-only	sysUpTime when this process was started.
TIK cmdExecLastExecTime	1.3.6.1.4.1.43.10.25.5.2.1.5	TimeTicks	read-only	sysUpTime when this process last used any processor time.
TIK cmdExecSystemTime	1.3.6.1.4.1.43.10.25.5.2.1.6	TimeTicks	read-only	Number of time-ticks used by this process.
INT cmdExecStatement	1.3.6.1.4.1.43.10.25.5.2.1.8	INTEGER	read-only	Generally scripts are broken into statements, this is just about true for any scripting mechanism. The statement number is generally useful for debugging. This object reports the current statement that will be executed _next_.
INT cmdExecOperation	1.3.6.1.4.1.43.10.25.5.2.1.9	INTEGER	read-write	This object can be set to cause some action to be applied to a executing process. Note that this variable can only be set if the row- status is valid. Operations are: none - Value returned for _any_ read operation. execute - If the operational state of the macro is 'inactive' then this command will attempt to execute the script named in cmdMacroName. If the process is in any other state this command will be rejected. suspend - This command will suspend the process at the end of the current statement. Command is rejected if the macro is inactive. continue - If a macro is suspended due to a 'suspend' command this will cause it to continue execution from its current point. step - Execute the next statement and then stop. kill - Stop this process from running and put it in the inactive state. Note that this deletes all resource associated with the executing script, but not the process itself. abort - If the current macro status is 'suspended' Will cause it to terminate at its current point. next - Execute the next statement, stepping over child processes.
INT cmdExecLastError	1.3.6.1.4.1.43.10.25.5.2.1.10	INTEGER	read-only	Last error detected by this process or the script executing within the process.
STR cmdExecOwner	1.3.6.1.4.1.43.10.25.5.2.1.11	OwnerString	read-write	RMON Owner of this process.
ENT cmdExecStatus	1.3.6.1.4.1.43.10.25.5.2.1.12	EntryStatus	read-write	Rmon RowStatus for this process.
STR cmdExecMacroName	1.3.6.1.4.1.43.10.25.5.2.1.13	DisplayString	read-write	Name of the script to execute in the process. The script can reside in either the macro table in this MIB module, or in some other internal script repository.

RFC description

Provides macro and script execution facility for managing scripts remotely on 3Com network devices.

Start monitoring Legacy 3Com switches/routers 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 A3COM0048-EMBEDDED-SCRIPTS

What Is A3COM0048-EMBEDDED-SCRIPTS?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description