cc/td/doc/product/access/multicon/3810soft
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring a TFTP Server

Configuring a TFTP Server

To access a configuration remotely for use with the Cisco MC3810, you need to configure a TFTP server. This appendix describes how to configure the TFTP server so that you can access remote configurations to use with the Cisco MC3810 Visual Configuration Tool (VCT).


Note This appendix is adapted from the CiscoWorks Getting Started Guide. Refer to that document online on the documentation CD-ROM or the printed manual for more information.

Setting Up TFTP

The Trivial File Transfer Protocol (TFTP) enables you to transfer files to and from remote systems. The configuration management application in the VCT enables you to edit configuration files by using a text editor and download the files to devices on your network. It also enables you to retrieve a device's configuration file, view it, edit it, or load it to the device. TFTP is used to transfer the configuration files from a device to your system via the network.

You must verify that the TFTP daemon is enabled, the TFTP environment variable is set correctly, and a tftpboot directory exists. If you do not perform these tasks, you will not be able to remotely configure a device and a message will appear on the console screen stating that TFTP was not enabled. You are able to use VCT to create a startup configuration file from scratch.

Enabling the TFTP Daemon

In order for the VCT software to upload or download a configuration file, the TFTP daemon (tftpd) must be enabled. When you initiated the VCT , you might have noted a message stating that TFTP is not set up correctly. The steps in this section will correct that situation.

If you are using the standard Sun software, verify that tftpd is enabled by completing the following steps:

Step 1 Log in as a super user.

Step 2 Using a text editor such as vi, edit the /etc/inetd.conf file.

Step 3 Look in the file /etc/inetd.conf for the line that invokes tftpd. If the line is commented out (starts with a pound sign (#) as in the following example), remove the pound sign with an editor.

tftp dgram udp wait root /user/etc/in.tftpd in.tftpd -s /tftpboot

Step 4 Save the changes in the edited file and exit.

Step 5 At the UNIX prompt, enter the following command to display the process id number for the inetd configuration.

hostname# ps -ax | grep -v grep | grep inetd

The system response is similar to the following:


hostname# 119 ? S 0:05 inetd


The first number in the output is the process ID of the inetd process. You must restart the process by entering the following:


hostname# kill -HUP 119

Step 6 Verify that TFTP is enabled by typing:

hostname# netstat -a | grep tftp

The output should be similar to the following:


hostname# *.tftp Idle

If there is no output, tftpd is not enabled. For additional information on TFTP, refer to the UNIX man pages on tftp and tftpd.

Creating the tftpboot Directory

The tftpboot directory can be used to save and store configuration files that are loaded to a device when using the configuration management application in the VCT (VCT).


Note Creating and using the tftpboot directory on your system is optional. The tftpboot directory is accessible by all users. To protect the security of your system and limit access to it, you might choose not to set up this directory on your system.

Follow these steps to create the tftpboot directory:

Step 1 If the tftpboot directory does not exist, use the following command to create the directory:

hostname# mkdir /tftpboot

Step 2 The tftpboot directory must have the appropriate permissions. Modify the permissions with the following command:

hostname# chmod 777 /tftpboot

As a result, all users accessing the tftpboot directory will have read, write, and execute permissions.

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.