The local DLCI value on which the TFTP host can be
reached. This DLCI should be active prior to
initiating the TFTP session. This parameter is only
required for Piggyback in-band frame relay managed
applications. With Private management (Local, Remote
or Bi-directional in-band applications) the DLCI is
known and will be reported here (Sets will be ignored).
In SLIP-based applications the DLCI value is not
applicable and a value of -1 is reported (Sets will
be ignored).
Parsed from file TFRAP.MIB.txt
Company: None
Module: TFRAP-MIB
The local DLCI value on which the TFTP host can be
reached. This DLCI should be active prior to
initiating the TFTP session. This parameter is only
required for Piggyback in-band frame relay managed
applications. With Private management (Local, Remote
or Bi-directional in-band applications) the DLCI is
known and will be reported here (Sets will be ignored).
In SLIP-based applications the DLCI value is not
applicable and a value of -1 is reported (Sets will
be ignored).
Parsed from file TFRAP-MIB.mib
Module: TFRAP-MIB
Vendor: Sync Research, Inc.
Module: TFRAP-MIB
[Automatically extracted from oidview.com]
tfrapCfgTftpDlci OBJECT-TYPE SYNTAX INTEGER (-1..63487) ACCESS read-write STATUS mandatory DESCRIPTION "The local DLCI value on which the TFTP host can be reached. This DLCI should be active prior to initiating the TFTP session. This parameter is only required for Piggyback in-band frame relay managed applications. With Private management (Local, Remote or Bi-directional in-band applications) the DLCI is known and will be reported here (Sets will be ignored). In SLIP-based applications the DLCI value is not applicable and a value of -1 is reported (Sets will be ignored)." ::= {tfrapCfgTftpTable 5}
tfrapCfgTftpDlci OBJECT-TYPE SYNTAX INTEGER (-1..63487) ACCESS read-write STATUS mandatory DESCRIPTION "The local DLCI value on which the TFTP host can be reached. This DLCI should be active prior to initiating the TFTP session. This parameter is only required for Piggyback in-band frame relay managed applications. With Private management (Local, Remote or Bi-directional in-band applications) the DLCI is known and will be reported here (Sets will be ignored). In SLIP-based applications the DLCI value is not applicable and a value of -1 is reported (Sets will be ignored)." ::= {tfrapCfgTftpTable 5}
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.1.2.5.0 | tfrapCfgTftpDlci | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.1.2.1 | tfrapCfgTftpInitiate | 1 | 1 | Setting this object to a value that matches the TFTP Password will command the unit to attempt a TFTP file transfer. A TFTP profi… |
| 1.3.6.1.4.1.485.5.2.1.2.2 | tfrapCfgTftpIpAddress | 1 | 1 | The IP address of the TFTP host with which the unit will attempt to establish a TFTP session when initiated. |
| 1.3.6.1.4.1.485.5.2.1.2.3 | tfrapCfgTftpFilename | 1 | 1 | The name of the file located on the TFTP host that will be transferred to the unit. Typically this is a product-specific software… |
| 1.3.6.1.4.1.485.5.2.1.2.4 | tfrapCfgTftpInterface | 1 | 1 | The physical interface out which the TFTP host is located. This parameter is only required for Piggyback and Bi-directional in-ba… |
| 1.3.6.1.4.1.485.5.2.1.2.6 | tfrapCfgTftpStatus | 1 | 1 | The status of current or most recent TFTP operation. (1) TFTP inactive, sets to this value will abort the session (2) TFTP reques… |
| 1.3.6.1.4.1.485.5.2.1.2.7 | tfrapCfgTftpNumBytes | 1 | 1 | The number of Bytes from the ROM image that have been TFTP'd to the unit |