TFTP procedure overview for ATI hubs and switches TFTP is Trivial File Transfer Protocol. It is a TCP/IP protocol that requires a TCP/IP stack, I.E, Wollongong TCP/IP stack, be installed in a PC or Apple MAC type computer. In addition to the TCP/IP stack, the TFTP utility must also be present. UNIX computers typically include TCP/IP and complete sets of TCP/IP utilities including TFTP. TFTP allows us to place a different version of hub software into a hub through the network. An IP address must be set in the destination hub and the hub must be responding to PING, the ICMP echo request utility in TCP/IP. TFTP utilities vary from vendor to vendor as does the TFTP syntax. The following defines the parameters that must be passed to the TFTP utility in order to download a binary image of hub software from a PC to the hub. A typical command line syntax might look like this: C:/>TFTP put ats5_24.img 192.2.200.200 ATXXXX octet Where: "TFTP" invokes the utility "put" means write or copy FROM this machine "ats5_24.img" is the local filename to be copied "192.2.200.200" is the destination hub's IP address "ATXXXX" is the destination hub's download password ("XXXX" depends on the hub). TFTP sees this parameter as the destination filename to be copied TO. The hub's download password can be changed in the Omega Manager /Administration/Network parameters section. "octet" is a binary mode that must be set. TFTP typically defaults to ASCII and must be told to do a binary transfer. TFTP is not very robust. It does not do the handshaking that an FTP file transfer does. TFTP may have trouble traversing slower network connections, highly loaded networks, or may be blocked by routers along a desired route. TFTP works best in moderately loaded, healthy networks. FTP is much more robust but cannot be used for this feature in the ATI family of hubs.