Router products support Telnet access for diagnostic purposes. Access to Telnet services are restricted in two ways :
NOTE: Telnet is a read only application. All configuration is handled via SNMP which also may be secured via the Access List (Good Guys entries in the MIB).
The following setting are recommended when using the standard Microsoft version of Telnet (all setting are set by selecting the ‘Terminal’ menu then ‘Preferences’
Select ‘local echo’ ON
Select ‘Buffer size’ = 30
Select VT100/ANSI ON
Using the buffer size defined above allows all pages to be displayed as a single screen (except for rolling log pages 7 & 9). and depending on screen resolution may require selection of a suitable font size.
LINUX standard Telnet and some other Telnet applications will not work with the router Telnet pages due to the handling of echo characters. This restriction is under investigation and will be removed as soon as practical.
Router application version 69 onward requires a user to login to the Router before being able to invoke the diagnostics. The login sequence appears as follows
ZyTrax Router Diagnostics
Login:
enter the Router Name followed by [ENTER] key.
The Router Name is found in MIB under zytrax\router\system\sysName (default configuration name is always the model name e.g. WarpOne or WarpTwo) using a ZyTrax utility such as CoolFig or NT_Ser. (NOTE: login name is case sensitive).
If the login sequence is successful the following message appears
Select Initial Page:
Type a single page number (do not use ENTER required) e.g. “a” (without the inverted commnas) will display the Router Traffic screen.
If the Name is incorrect the message
Invalid Password
is displayed and you may try again to enter the Router Name. If after three attempts the correct password has not been entered then the message
Telnet session terminated
is displayed and the Telnet session is abandoned.
Each telnet page starts with a display of the format
Router Status Page X (PPPRRIIBBB)
Where
X is the page number selected
PPPRRIIBBB is the PRIB defining the Product, Release, Issue and Build number as follows:
In many cases it is better to log the telnet session to a disk file for subsequence analysis. Most versions of Telnet support this feature. The following instructions apply to the standard Microsoft Windows release of Telnet.
support home
contents
arp table
routing table
i/o stats
hotpools
ip stats
link states
system log
cpu stats
link log
traffic log
policy q's
security
isdn log
nat
multicast
dhcp
isdn test
If you are happy it's OK - but your browser is giving a less than optimal experience on our site. You could, at no charge, upgrade to a W3C STANDARDS COMPLIANT browser such as Mozilla
Copyright © 1994 - 2024 ZyTrax, Inc. All rights reserved. Legal and Privacy |
site by zytrax hosted by javapipe.com |
web-master at zytrax Page modified: January 20 2022. |