---
oid: "1.3.6.1.4.1.1978.2.1.8.2.1.5"
short-description: "bootpRemoteFile 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.5`

```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) bootpRemoteFile(5)}
```

### Description

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