TFTP-OPT-MIB

All MIBs › TFTP-OPT-MIB

Category: Testing and Diagnostics

Description: Manages TFTP protocol option negotiation parameters and transfer configuration.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TFTP-OPT-MIB?

TFTP-OPT-MIB appears to model TFTP protocol option negotiation, based on its name, though no module description or sample objects were provided for this module. TFTP option negotiation (as defined in RFC 2349) typically covers parameters like block size, timeout, and transfer size used when negotiating a file transfer. Without concrete object data it cannot be confirmed whether this module exposes runtime negotiation state or purely configuration defaults, so specific hardware/software status monitoring claims cannot be made here. It would logically relate to the base TFTP protocol and its option-extension RFCs if it follows IETF conventions. It would typically be deployed on any network device acting as a TFTP client or server, most often during firmware or configuration file transfers. Engineers implementing or auditing this functionality typically reference the TFTP-OPT-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in TFTP-OPT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer — generic device running a TFTP client or server

Monitoring Examples

No module description or object/table names were supplied for this MIB, so no concrete monitoring scenario or object names can be honestly given. Based on the module name alone, it likely relates to TFTP transfer option parameters such as block size, timeout, or transfer size negotiation, but this cannot be confirmed without object data.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

IpAddress
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
codex	1.3.6.1.4.1.449
cdxProductSpecific	1.3.6.1.4.1.449.2
cdx6500	1.3.6.1.4.1.449.2.1
cdx6500Statistics	1.3.6.1.4.1.449.2.1.3
cdx6500StatTFTPGroup	1.3.6.1.4.1.449.2.1.3.3
INT cdx6500StatTFTPoperation	1.3.6.1.4.1.449.2.1.3.3.1	INTEGER	read-only	Type and target of the last TFTP transfer or the one in progress, configuration download, configuration upload, software download, current or alternate bank. Configuration transfers will only be supported to/from the current bank at release 4.0.
IP cdx6500StatTFTPIPaddress	1.3.6.1.4.1.449.2.1.3.3.2	IpAddress	read-only	IP address of the remote TFTP application.
STR cdx6500StatTFTPfilename	1.3.6.1.4.1.449.2.1.3.3.3	DisplayString	read-only	File name used in the TFTP RRQ or WRQ message.
STR cdx6500StatTFTPtimestamp	1.3.6.1.4.1.449.2.1.3.3.4	DisplayString	read-only	Time of last operation. A null terminated string in the form `dd-mm-yyyy hh:mm:ss'. This will represent the starting time if the operation is in progress and the ending time if the operation has completed.
INT cdx6500StatTFTPbytecount	1.3.6.1.4.1.449.2.1.3.3.5	INTEGER	read-only	Total number of bytes transferred. This will represent a running total while the operation is in progress, and the final total after the operation has completed.
STR cdx6500StatTFTPstatus	1.3.6.1.4.1.449.2.1.3.3.6	DisplayString	read-only	Status of the latest configuration operation including an operation in progress. Possible status messages are: 'TFTP: No transfers since node last booted', 'TFTP: Transfer in progress' 'TFTP: Operation successful' 'TFTP: CMEM access failure' 'TFTP: Local transfer failure, , Error Code = ' 'TFTP: Remote transfer failure, , Error Code = ' 'TFTP: System failure' 'TFTP: UDP registration failure' 'TFTP: Flash erasure in progress' 'TFTP: Flash erasure failure' 'TFTP: Flash write failure' 'TFTP: Error in software image file' 'TFTP: Configuration script upload/download partial success' 'TFTP: Configuration script upload/download failure'
cdx6500Controls	1.3.6.1.4.1.449.2.1.4
cdx6500ContTFTP	1.3.6.1.4.1.449.2.1.4.2
INT cdx6500ContTFTPoperation	1.3.6.1.4.1.449.2.1.4.2.1	INTEGER	read-write	Type and target of the TFTP transfer, configuration download, configuration upload, software download, current or alternate bank. Configuration transfers will only be supported to/from the current bank at release 4.0. Note that value 'noOperation' is not valid for the write operation.
IP cdx6500ContTFTPIPaddress	1.3.6.1.4.1.449.2.1.4.2.2	IpAddress	read-write	IP address of the remote TFTP application.
STR cdx6500ContTFTPfilename	1.3.6.1.4.1.449.2.1.4.2.3	DisplayString	read-write	File name to be used in the TFTP RRQ or WRQ message.
INT cdx6500ContTFTPinitiateorder	1.3.6.1.4.1.449.2.1.4.2.4	INTEGER	write-only	Order to initiate the TFTP transfer.

RFC description

Monitors TFTP operations on Codex CDX6500 devices including configuration/software downloads and file transfers with remote servers.

Start monitoring vendor-neutral, standards-based MIB, generic device running a TFTP client or server (option negotiation) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TFTP-OPT-MIB

What Is TFTP-OPT-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description