Administrative Problems (Netview/SNMP/Telnet)
This section details problems occuring during the administration of your ONcore hub
(PING,Telnet,TFTP,SNMP/ATMC).
PING: Your ONcore hub cannnot ping your management station.
Steps to Take:
1. Since all the management services are running over IP, you have to ensure that
your ONcore hub can ping the destination station where you will run either Telnet,
the TFTP daemon (TFTP server), or the SNMP manager (ATMC). If the ping fails,
see previous sections on ping failures in Classical IP or LAN emulation networks.
Telnet: You cannot Telnet to your ONcore hub 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 ONcore hub by another Telnet session. It is not
possible to have more than one Telnet session per ONcore hub.
To know from which station the other Telnet session is active, use the ATMC SVC
Tracking tool to determine at least which SVCs are connected to the internal port of
the ONcore hub (interface 1). You will then know the ATM addresses of the remote
ends, as well as the ONcore hub 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 ONcore hub
Explanation: The upload can be done either from the terminal console (console or
Telnet) or from the SNMP Manager (ATMC or MIB Browser).
Before performing any upload, make sure that the machine hosting the TFTP server can
ping the ONcore hub.
7-34 ONcore ATM Switch/Control Module: Installation and User's Guide
