IBM 8265 Nways ATM Switch User Manual Download Page 166

Page: 166 / 192

Administrative Problems (Netview/SNMP/Telnet)

This section details problems occurring during the administration of your 8265

PING: Your 8265 cannot ping your management station.

Steps to Take:

1. Since all the management services are running over IP, you have to ensure that your 8265 can ping the

destination station where you will run either Telnet, the TFTP daemon (TFTP server), or the SNMP manager
(Campus Manager - ATM). If the ping fails, see previous sections on ping failures in Classical IP or LAN emulation
networks.

Telnet: You cannot Telnet to your 8265 from your management station.

Steps to Take:

1. If the ping does not work, see previous sections on ping failures.

2. Someone is already logged on the 8265 by another Telnet session. It is not possible to have more than one

Telnet session per 8265

To know from which station the other Telnet session is active, use the Campus Manager - ATM SVC Tracking tool
to determine at least which SVCs are connected to the internal port of the 8265 (interface 1). You will then know
the ATM addresses of the remote ends, as well as the 8265 ports to which they are connected to.

Note: It is recommended to set the Terminal Timeout parameter to a non-zero value, to force Telnet sessions to

close themselves after some inactivity.

TFTP: Upload fails from your 8265

Explanation: The upload can be done either from the terminal dialog (console or Telnet) or from the SNMP Manager
(Campus Manager - ATM or MIB Browser).

Before performing any upload, make sure that the machine hosting the TFTP server can ping the 8265

When an upload fails, an error code is returned. That error code can be different between the terminal dialog and the
Campus Manager - ATM/MIB browser, which is why both return codes are documented.

Note: When the upload fails from the terminal dialog (console or Telnet), check the return code by using the SHOW

TFTP command.

Steps to Take:

1. Messages: Error/generic error..Host Access Violation...Access Rights Violation/access-rights-violation...File

already exists/file-already exits..

The file that you want to upload already exists on the target machine, and is read-only.

Change the attributes of the file on the target machine or change the name of the file to be uploaded.

You are trying to upload to a directory that is not uploadable by TFTP.

If your target host runs AIX or Unix, use the directory /tmp, or configure the file /etc/tftpaccess.ctl with lines
beginning with 'allow:' (check the documentation of the daemon/server TFTPD. If you use another operating
system (OS/2 or others), configure the TFTP daemon on that system to accept uploads in the desired
directory.

You are trying to upload a file that can only be downloaded (operational code, boot code, or FPGA picocode).

Check the file type of the file to be uploaded.

2. Messages: Cannot connect to Host/no-response-from-host.

Check that you can ping the host from the 8265 If the ping fails, see the previous sections on ping failures.

150

IBM 8265: User's Guide