All MIBs › TIGER › bootpLocalFile
bootpLocalFile
Module: TIGER
OID (symbolic): TIGER::bootpLocalFile
OID (numeric): 1.3.6.1.4.1.1978.2.1.8.2.1.6
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
Description: When Tiger's bootp application is performing an FTP transaction, the bootpLocalFile object contains the destination path and filename for the incoming file.
If this field is empty, the downloaded file will be placed into a filename created by concatenating '/flash' with the filename (only) from the bootp response. That response will either contain a value specified in the BOOTP server database or if none there, then the value of bootpRemoteFile will be used.
When bootpLocalFile is specified it must always contain one of the valid TIGER filesystems of: '/flash' or '/ramdisk'.
It is assumed that this variable will always be written last when defining a bootpEntry. When this variable is written, the Bootp (or FTP) transaction will begin.
What is bootpLocalFile?
This read-write string sets the destination path and filename for a file downloaded via BOOTP/FTP; it must be under one of the Tiger's valid filesystems, /flash or /ramdisk. If left empty, the downloaded file is placed under /flash using just the filename from the BOOTP response, or from bootpRemoteFile if the response didn't specify one. Writing this variable is what actually triggers the BOOTP/FTP transaction to begin, so admins set it last when defining a new bootp table entry.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1978.2.1.8.2.1.6 snmpwalk -v2c -c public <target> TIGER::bootpLocalFile
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.1978.2.1.8.2.1.6.1 snmpget -v2c -c public <target> TIGER::bootpLocalFile.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.1978.2.1.8.2.1.6.1 s <value>
Start monitoring Northrop Grumman-Canada, Ltd. Tiger system equipment (interface-stack/hardware configuration status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIGER::bootpLocalFile OID value, configure state conditions and alerts, and monitor any Northrop Grumman-Canada, Ltd. Tiger system equipment (interface-stack/hardware configuration status) from a single console.
OID Breakdown
Upper-level ancestors (8 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.1978 | ngcan | ALC-MIB |
| 1.3.6.1.4.1.1978.2 | tiger | ALC-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.1978.2.1 | generalTiger | TIGER |
| 1.3.6.1.4.1.1978.2.1.8 | bootp | TIGER |
| 1.3.6.1.4.1.1978.2.1.8.2 | bootpTable | TIGER |
| 1.3.6.1.4.1.1978.2.1.8.2.1 | bootpEntry | TIGER |
| 1.3.6.1.4.1.1978.2.1.8.2.1.6 | bootpLocalFile | TIGER |