A3COM0048-EMBEDDED-SCRIPTS
Standard SNMP MIB module defining data structures for A3COM0048-EMBEDDED-SCRIPTS.
Imported Objects
Objects
22 total| Object Name |
|---|
command OBJECT IDENTIFIER .1.3.6.1.4.1.42359.2.2.1.25.5 |
cmdMacroTableExtended RMON table that provides a macro execution facility
on the remote unit. SEQUENCE OF CmdMacroEntry .1.3.6.1.4.1.42359.2.2.1.25.5.1 |
cmdMacroEntry CmdMacroEntry .1.3.6.1.4.1.42359.2.2.1.25.5.1.1 |
cmdMacroIndexStandard RMON index column. INTEGER .1.3.6.1.4.1.42359.2.2.1.25.5.1.1.1 |
cmdMacroNameA short text name for this macro. This name can be
referenced in the cmdTable to execute a script.rw DisplayString .1.3.6.1.4.1.42359.2.2.1.25.5.1.1.2 |
cmdMacroStringText macro that is represented by this control entry.rw DisplayString .1.3.6.1.4.1.42359.2.2.1.25.5.1.1.3 |
cmdMacroOwnerRMON Owner of this process.rw OwnerString (RMON-MIB) .1.3.6.1.4.1.42359.2.2.1.25.5.1.1.4 |
cmdMacroStatusRmon RowStatus for this macro definition.rw EntryStatus (RMON-MIB) .1.3.6.1.4.1.42359.2.2.1.25.5.1.1.5 |
cmdExecTableExtended 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. SEQUENCE OF CmdExecEntry .1.3.6.1.4.1.42359.2.2.1.25.5.2 |
cmdExecEntry CmdExecEntry .1.3.6.1.4.1.42359.2.2.1.25.5.2.1 |
cmdExecUnitIdentifies one of a number of different 'execution units'.
Genrally each of these is a separate processor in a distributed
environment. INTEGER .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.1 |
cmdExecIndexStandard RMON index column. INTEGER .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.2 |
cmdExecProcessStatusThe 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.ro Enumeration .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.3 |
cmdExecStartTimesysUpTime when this process was started.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.4 |
cmdExecLastExecTimesysUpTime when this process last used any processor time.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.5 |
cmdExecSystemTimeNumber of time-ticks used by this process.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.6 |
cmdExecStatementGenerally 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_.ro INTEGER .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.8 |
cmdExecOperationThis 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.rw Enumeration .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.9 |
cmdExecLastErrorLast error detected by this process or the script executing
within the process.ro Enumeration .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.10 |
cmdExecOwnerRMON Owner of this process.rw OwnerString (RMON-MIB) .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.11 |
cmdExecStatusRmon RowStatus for this process.rw EntryStatus (RMON-MIB) .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.12 |
cmdExecMacroNameName 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.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.42359.2.2.1.25.5.2.1.13 |
More MIBs from Versa
Browse all VersaMIBs →The LLDP-EXT-DOT1-V2-MIB module extends the LLDP-V2 framework to expose IEEE 802.1Q and 802.1Qaz organizationally defined TLVs, enabling the monitoring of VLAN tagging configurations, Priority Flow Control (PFC) states, and Enhanced Transmission Selection (ETS) parameters on Layer 2 network switches. This allows administrators to verify and manage data center network flow control policies and VLAN membership attributes via SNMP.
The IEEE8021-Q-BRIDGE-MIB enables monitoring and configuration of IEEE 802.1Q VLAN-tagged bridging domains, specifically tracking VLAN membership, port filtering tables, and bridge protocol data unit (BPDU) states on Layer 2 network switches.
SNMP MIB module
The LLDP-V2-MIB module manages IEEE 802.1AB-2009 compliant Link Layer Discovery Protocol agents to monitor local system identity, remote neighbor topology, and per-port transmission statistics, specifically supporting multi-agent architectures where distinct MAC addresses are associated with a single physical port.
The IEEE8021-EVB-MIB provides SNMP management capabilities for Ethernet Virtual Bridging (EVB) devices, specifically monitoring and configuring virtual station interfaces (VSIs), virtual bridge ports, and associated bridge domain parameters as defined in IEEE 802.1Q-2014. It enables the retrieval of operational states, configuration parameters, and performance counters for virtualization features such as MAC-in-MAC encapsulation and port isolation within IEEE 802.1Q-compliant network infrastructure.
The IEEE8021-MSTP-MIB enables the monitoring and configuration of IEEE 802.1Q Multiple Spanning Tree (MSTP) instances, specifically tracking MST region definitions, instance-to-VLAN mappings, and port state transitions across bridged network devices. It provides granular visibility into MSTP topology convergence, including root bridge election status, path costs, and port roles (designated, root, blocked) to ensure loop-free Layer 2 redundancy.