All MIBs › CHASSIS-MIB › chasControlFFSFileAction
chasControlFFSFileAction
Module: CHASSIS-MIB
OID (symbolic): CHASSIS-MIB::chasControlFFSFileAction
OID (numeric): 1.3.6.1.4.1.800.2.1.3.2.1.6
Node type: OBJECT-TYPE
Type: XylanFFSFileAction
Access: read-write
Description: none(1) No action has been requested for this file writingTo(2) can only be specified for Primary causes the specified file to be written from Primary to Secondary. deletingFrom(3) this file is being removed can be specified for files on both Primary and Secondary. readingFrom(4) can only be specified for Secondary causes the specified file to be copoed from the Secondary to the Promary. This value may be set to delete files from an MPM or copy files between the Primary and Secondary. Only one action is permitted at a time. If a SET is attempted to ANY chasControlFFSFileAction when chasControlLastFFSActionSlot is inProgress(2) the resource will be unavailable.
What is chasControlFFSFileAction?
This object triggers a specific file operation on the flash file system: none for no action, writingTo (only from Primary) to push a file to the Secondary, deletingFrom to remove a file from either controller, or readingFrom (only from Secondary) to pull a file back to the Primary. An admin manually syncing firmware between dual controllers, outside the automatic sync mechanism, or cleaning up old images would SET this object per file, and the constraint that writingTo can only be requested from the Primary reflects the master/standby relationship between the two controllers. To manually push a newly uploaded firmware image from the Primary to the Secondary controller, an admin would SET this object to writingTo(2) for that specific file entry.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.800.2.1.3.2.1.6 snmpwalk -v2c -c public <target> CHASSIS-MIB::chasControlFFSFileAction
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.800.2.1.3.2.1.6.1 snmpget -v2c -c public <target> CHASSIS-MIB::chasControlFFSFileAction.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.800.2.1.3.2.1.6.1 s <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> chasControlFFSFileAction.1
Start monitoring Modular/chassis-based network switches and routers (any vendor) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CHASSIS-MIB::chasControlFFSFileAction OID value, configure state conditions and alerts, and monitor any Modular/chassis-based network switches and routers (any vendor) from a single console.
OID Breakdown
Upper-level ancestors (9 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.800 | xylan | XYLAN-BASE-MIB |
| 1.3.6.1.4.1.800.2 | xylanArch | XYLAN-BASE-MIB |
| 1.3.6.1.4.1.800.2.1 | xylanChassis | XYLAN-BASE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.800.2.1.3 | chasController | CHASSIS-MIB |
| 1.3.6.1.4.1.800.2.1.3.2 | chasControlFFSTable | CHASSIS-MIB |
| 1.3.6.1.4.1.800.2.1.3.2.1 | chasControlFFSEntry | CHASSIS-MIB |
| 1.3.6.1.4.1.800.2.1.3.2.1.6 | chasControlFFSFileAction | CHASSIS-MIB |