Workgroup Remote Access Switch 357S YSTEM VERIFICATIONVerifying an X.25 ConnectionV ERIFYING AN X.25 C ONNECTIONTo verify an X.25 to the CyberSWITCH, the WAN lines that are connected to the System must beavailable for use, and the routing option must be properly initialized. Follow the steps below toverify that you have an X.25 connection.Enter thex25 stats command at the administration console. If the statistics display appears, theX.25 subsystem should be operational. If the following message is displayed, X.25 is not configured:No X.25 Accesses configuredRefer to X.25 Connections of the Problem Diagnosis chapter.V ERIFYING R EMOTE D EVICE CONNECTIVITYTo verify remote device connectivity to the CyberSWITCH, the WAN lines that are connected tothe system must be available for use, and the bridging and/or routing options must be properlyinitialized. The remote devices must be operational and available to initiate ISDN WANconnections.The method of connection initiation is dependent upon the remote device type. Refer to the remotedevice 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” oras the configured Device Name (if security is enabled) on the Monitor Connections screen. Todisplay the Monitor Connections screen, enter the following console command:mc Note: The terminal type must be the same for Telnet and the terminal emulation. Use theterm set administration console command to set the terminal type.If each remote device is able to connect to the CyberSWITCH, then WAN connectivity issuccessful.If a remote device is NOT able to connect to the system, then refer to Remote Device Connectivityin the Problem Diagnosis chapter.V ERIFYING M ULTI -L EVEL S ECURITYTo verify device and user level security to the CyberSWITCH, the WAN lines that are connected tothe system must be available for use, and IP, AppleTalk, or bridging options must be properlyinitialized. The remote devices must be operational and available to initiate ISDN WANconnections. The remote device must be configured on a device database, with User LevelAuthentication initially disabled. A client PC on the LAN of the remote device must a user ID andpassword for a user level database on an off-node server. Both databases must be enabled andavailable.