Filter
Top Products
Workgroup Remote Access Switch 357
S
YSTEM
V
ERIFICATION
Verifying an X.25 Connection
VERIFYING AN X.25 CONNECTION
To verify an X.25 to the CyberSWITCH, the WAN lines that are connected to the System must be
available for use, and the routing option must be properly initialized. Follow the steps below to
verify that you have an X.25 connection.
Enter the
x25 stats
command at the administration console. If the statistics display appears, the
X.25 subsystem should be operational. If the following message is displayed, X.25 is not configured:
No X.25 Accesses configured
Refer to X.25 Connections of the Problem Diagnosis chapter.
VERIFYING REMOTE DEVICE CONNECTIVITY
To verify remote device connectivity to the CyberSWITCH, the WAN lines that are connected to
the system must be available for use, and the bridging and/or routing options must be properly
initialized. The remote devices must be operational and available to initiate ISDN WAN
connections.
The method of connection initiation is dependent upon the remote device type. Refer to the remote
device documentation to determine how to initiate an ISDN WAN connection.
To verify remote device connectivity:
1. In a controlled manner, initiate an ISDN connection from each remote device.
2. When each remote device connects to the system, it will appear as either a “REMOTE site” or
as the configured Device Name (if security is enabled) on the Monitor Connections screen. To
display the Monitor Connections screen, enter the following console command:
mc
<return>
Note: The terminal type must be the same for Telnet and the terminal emulation. Use the
term set
administration console command to set the terminal type.
If each remote device is able to connect to the CyberSWITCH, then WAN connectivity is
successful.
If a remote device is NOT able to connect to the system, then refer to Remote Device Connectivity
in the Problem Diagnosis chapter.
VERIFYING MULTI-LEVEL SECURITY
To verify device and user level security to the CyberSWITCH, the WAN lines that are connected to
the system must be available for use, and IP, AppleTalk, or bridging options must be properly
initialized. The remote devices must be operational and available to initiate ISDN WAN
connections. The remote device must be configured on a device database, with User Level
Authentication initially disabled. A client PC on the LAN of the remote device must a user ID and
password for a user level database on an off-node server. Both databases must be enabled and
available.