All MIBs › Olicom-MIB › controlSwAdminStatus
controlSwAdminStatus
Module: Olicom-MIB
OID (symbolic): Olicom-MIB::controlSwAdminStatus
OID (numeric): 1.3.6.1.4.1.285.5.13
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: This object controls the state of the SW images in systems where more than one image is present.
In the OC-9100 the state of each image may be: empty(1) - no image is present, future1(2) - the image may be used later, futureTest(3) - the image will be used once on the next restart, future2(4) - the image may be used later, current1(5) - the image is in use now, past(6) - the image was previously used, current2(7) - the image is in use now, checksumError(8) - the image is faulty, erased(9) - the image has been erased. Because this information is stored in flash each state cannot be used arbitrarily. For example, the future state can only be used twice, namely as state future1 and future2. Normally, the state of a SW image progresses through numerically increasing states.
In the OC-8500 and OC-8700 series the status word is stored in BBS RAM. This releases the constraints to the sequence of states, thus only a subset of the above is needed: empty(1) - no image is present, future1(2) - the image may be used later, futureTest(3) - the image will be used once on the next restart, current1(5) - the image is in use now, past(6) - the image was previously used, checksumError(8) - the image is faulty, erased(9) - the image has been erased.
The value actually stored in this object is state1*256+state2, where state1 and state2 are the values of the two SW image states. Note that a number of combinations are illegal. For example, the value 6*256+6 (indicating two 'past' images) may not be written.
What is controlSwAdminStatus?
This controls the lifecycle state of each software image slot on chassis models that hold more than one image, with states like empty, future (staged for later use), current (in use now), past (previously used), or checksumError (faulty), encoded as two packed byte values (state1*256+state2). An admin manipulating this must respect the model-specific allowed state sequences described in the MIB, since combinations like two images both marked 'past' are explicitly illegal to write.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.285.5.13 snmpwalk -v2c -c public <target> Olicom-MIB::controlSwAdminStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.285.5.13.1 snmpget -v2c -c public <target> Olicom-MIB::controlSwAdminStatus.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.285.5.13.1 i <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> controlSwAdminStatus.1
Start monitoring Legacy Olicom A/S networking equipment (hardware/software inventory) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Olicom-MIB::controlSwAdminStatus OID value, configure state conditions and alerts, and monitor any Legacy Olicom A/S networking equipment (hardware/software inventory) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.285 | olicom | Olicom-crossfireAtmSwitch-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.285.5 | control | Olicom-MIB |
| 1.3.6.1.4.1.285.5.13 | controlSwAdminStatus | Olicom-MIB |