All MIBs › TIGER › bootpRemoteFile
bootpRemoteFile
Module: TIGER
OID (symbolic): TIGER::bootpRemoteFile
OID (numeric): 1.3.6.1.4.1.1978.2.1.8.2.1.5
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
Description: If bootpRemoteFile is an empty string, the responding server will use its database entry to inform TIGER of the servers filename to use for this transaction.
If bootpRemoteFile contains a value, the BOOTP server will use that string to access its configuration database to determine the corresponding file that will be filled in the BOOTP response to inform TIGER of the servers filename to use for this transaction.
Normally, the bootp database will contain a entry that defines this name as the name of the configuration file that should be downloaded first (see bootpLocalFile).
What is bootpRemoteFile?
This read-write string names the file to request from the BOOTP/FTP server. If left empty, the server uses its own database entry to determine which file to send; if set, the server uses this string as a lookup key in its own configuration database to determine the corresponding file. Admins typically leave this pointing at whatever entry the BOOTP server has configured as the initial configuration file to download, as referenced by bootpLocalFile.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1978.2.1.8.2.1.5 snmpwalk -v2c -c public <target> TIGER::bootpRemoteFile
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.1978.2.1.8.2.1.5.1 snmpget -v2c -c public <target> TIGER::bootpRemoteFile.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.1978.2.1.8.2.1.5.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::bootpRemoteFile 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.5 | bootpRemoteFile | TIGER |