All MIBs › Unisphere-Data-FILE-XFER-MIB › usdFileXferRowStatus
usdFileXferRowStatus
Module: Unisphere-Data-FILE-XFER-MIB
OID (symbolic): Unisphere-Data-FILE-XFER-MIB::usdFileXferRowStatus
OID (numeric): 1.3.6.1.4.1.4874.2.2.23.1.1.1.10
Node type: OBJECT-TYPE
Type: RowStatus
Access: read-write
Description: The row status object controls the creation/deletion of rows in this table. Its semantics are the same as those for the RowStatus textual convention specified for SNMPv2.
Setting this object to createAndGo(4) is allowed. If required objects are missing, the agent will create the row and set its status to notReady(3). If all of the required objects are present and valid, the agent will create the row, set it to active and commence the file xfer. Upon completion of the file xfer, the agent will set the rowStatus to notInService(2), indicating that the row is valid and useable by a management client. To commence another transfer, a management client should set the rowStatus to active(1).
Setting this object to createAndWait(5) causes an entry to be created with usdFileXferRowStatus value of notInService(2) if all of the required objects are present and valid. Or, if some of the required objects are missing or invalid, the agent will create the row and sets its status to notReady(3).
Setting this object to active(1) causes the transfer to start for the given row. Objects within the row cannot be modified once a row has been set to active(1),
Setting this object to destroy(6) causes the corresponding row to be deleted.
Note that only a single instance of a row can be active at at any given moment, although several rows can exist in the table.
What is usdFileXferRowStatus?
This read-write RowStatus object both manages row lifecycle and actually starts and stops the file transfer job itself, per its unusually detailed description. Setting it to active(1) commences the transfer and locks the row's objects from further modification, completion moves the row to notInService(2), and only one row across the whole table can be active at any given moment. For example, an admin who has staged a transfer with createAndWait(5) later sets usdFileXferRowStatus to active(1) to actually kick off that specific file transfer.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.23.1.1.1.10 snmpwalk -v2c -c public <target> Unisphere-Data-FILE-XFER-MIB::usdFileXferRowStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.23.1.1.1.10.1 snmpget -v2c -c public <target> Unisphere-Data-FILE-XFER-MIB::usdFileXferRowStatus.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.4874.2.2.23.1.1.1.10.1 s <value>
Start monitoring Juniper (Unisphere) ERX edge routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Unisphere-Data-FILE-XFER-MIB::usdFileXferRowStatus OID value, configure state conditions and alerts, and monitor any Juniper (Unisphere) ERX edge routers from a single console.
OID Breakdown
Upper-level ancestors (13 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.4874 | juniperUni | Juniper-UNI-SMI |
| 1.3.6.1.4.1.4874.2 | juniperUniMibs | Juniper-UNI-SMI |
| 1.3.6.1.4.1.4874.2.2 | juniMibs | Juniper-MIBs |
| 1.3.6.1.4.1.4874.2.2.23 | juniFileXferMIB | Juniper-FILE-XFER-MIB |
| 1.3.6.1.4.1.4874.2.2.23.1 | juniFileXferObjects | Juniper-FILE-XFER-MIB |
| 1.3.6.1.4.1.4874.2.2.23.1.1 | juniFileXferTable | Juniper-FILE-XFER-MIB |
| 1.3.6.1.4.1.4874.2.2.23.1.1.1 | juniFileXferTableEntry | Juniper-FILE-XFER-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.4874.2.2.23.1.1.1.10 | usdFileXferRowStatus | Unisphere-Data-FILE-XFER-MIB |