---
oid: "1.3.6.1.4.1.1978.2.1.8.2.1.6"
short-description: "bootpLocalFile OBJECT-TYPE"
last-modified: "2020-07-30"
parent-oid: "1.3.6.1.4.1.1978.2.1.8.2.1"
---

## OID: `1.3.6.1.4.1.1978.2.1.8.2.1.6`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 1978 tiger(2) generalTiger(1) bootp(8) bootpTable(2) bootpEntry(1) bootpLocalFile(6)}
```

### Description

```asn1
bootpLocalFile OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..128))
ACCESS read-write
STATUS mandatory
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."
DEFVAL {""}
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.