Digital Networks TM Network Access Software Problem Solving Guide DECserver PG-DNAS0-00
Network Access Software Problem Solving Guide Part Number: PG-DNAS0-00 February 2001 This book describes how to solve problems if an error is encountered while using the Network Access Software. Revision/Update Information: This is a new document.
Digital Networks makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
Contents Preface Overview ........................................................................................................................ xiii Purpose.................................................................................................................... xiii Intended Audience ................................................................................................ xiii Conventions Used in This Document ........................................................................
Contents Verify Access Server Memory Usage .................................................................. 2-6 Verify Service Rating ............................................................................................. 2-9 Verify Nodes That Offer the Service.................................................................. 2-10 Verify the Connection to a Service..................................................................... 2-10 Verify Communications to Another Access Server...............
Contents Procedure ................................................................................................................ 4-7 More Information................................................................................................... 4-7 SLIP Session Not Receiving Input .............................................................................. 4-8 Solution ...................................................................................................................
Contents Introduction ............................................................................................................ 6-1 SNMP Reporting Is Not Consistent with the Access Server................................... 6-2 Solution.................................................................................................................... 6-2 SNMP Reporting Is Not Consistent with the MIB ................................................... 6-3 Solution..........................................
Contents Verify the Access Server and Security Configuration.............................................. 8-8 Procedure ................................................................................................................ 8-8 Verify the User’s Authorization Data ........................................................................ 8-9 Procedure ................................................................................................................
Contents Test the Printer Port .................................................................................................... 11-4 Procedure .............................................................................................................. 11-4 Additional Steps................................................................................................... 11-4 More Information.................................................................................................
Contents Access Server Manager Procedure .................................................................... 13-7 Dial-In Modem Disconnects from the Server ......................................................... 13-8 Solution ................................................................................................................. 13-8 Cannot Connect to Dial-Out Modem Offered as a LAT Service .......................... 13-9 Solution ................................................................
Contents Introduction .......................................................................................................... 15-4 Verify Console Logging Is Enabled ................................................................... 15-4 Verify Server Console Port.................................................................................. 15-5 Chapter 16 Remote Login Problems Overview ................................................................................................................
Contents Chapter 19 Messages 200 – 299 Overview ...................................................................................................................... 19-1 Introduction .......................................................................................................... 19-1 Messages ............................................................................................................... 19-1 Chapter 20 Messages 300 – 399 Overview ..............................................
Contents Chapter 26 Messages 900 – 999 Overview ...................................................................................................................... 26-1 Introduction .......................................................................................................... 26-1 Messages................................................................................................................ 26-1 Chapter 27 Messages 1000 – 1099 Overview ............................................
Preface Overview Purpose This guide describes problem-solving tools and procedures for the various network access servers. Intended Audience The Network Access Server Problem Solving Guide is written for the person who troubleshoots the network access server. Conventions Used in This Document Conventions Familiarizing yourself with the conventions discussed in this section will help you use this manual effectively. • The Return key, which executes all commands, is not shown in command line displays.
Preface Typographical Conventions The following typographical conventions are used in this manual: xiv Convention Description Special type Special type in command examples indicates system output or user input. UPPERCASE Uppercase letters in command lines indicate keywords that must be entered. You can enter them in either uppercase or lowercase. You can abbreviate command keywords to the first three characters or to the minimum unique abbreviation.
Preface Associated Documents Additional Reading Refer to the following documents for more information: • Release Notes — Provides the latest information about the access server. The release notes are available with the software distribution kit and are stored in the load host directory with the other software distribution files. • Network Access Software Installation Guide (Windows 9x,me,2000 & NT, OpenVMS, UNIX) — Describes how to install the network access software on your operating system.
Chapter 1 Software Installation Problems Overview Introduction The following table lists the steps and page references to help you solve software installation problems: Problem Solution See Page Access Server Software does not Load Properly 1. Verify the Network Access Server Hardware 1-2 2. Verify the Image Name and Flash RAM 1-2 3. Verify the Load Host 1-3 4. Ensure the Logical MO*$LOAD Is Defined Correctly on the OpenVMS Host 1-9 5.
Software Installation Problems Access Server Software Does Not Load Properly Verify the Network Access Server Hardware Check the LEDs on the hardware. For information on the LED codes and site preparation information, refer to your access server hardware documentation. Verify the Image Name and Flash RAM The load image name should reflect your access server type and appropriate version number.
Software Installation Problems NOTES If Flash RAM is installed but its boot block is invalid, then the total memory size will appear as zero. If your system is equipped with Flash RAM, you can use the INITIALIZE command to load from either Flash RAM or the load host. If your system is not equipped with Flash RAM, you can only initialize from the load host. For more information on initialization, refer to the Network Access Server Management Guide.
Software Installation Problems BOOTP/TFTP - One of the following: Operating System Version SunOS Release 4.0 Digital UNIX Version 1.0 IBM AIX Version 3.1.1 SCO UNIX System V/386 Release 3.2 V2.0 HP-UX 8.0 Some System V systems, such as HP-UX and SCO, may not support the upline dump of server memory. OpenVMS Tailoring: For OpenVMS Version 5.
Software Installation Problems At an OpenVMS load host: NOTE In the following instructions, when you see MO*$LOAD, enter MOM$LOAD for the DECnet Phase IV software and MOP$LOAD for the DECnet/OSI software. Step Action 1 Check the logical symbol MO*$LOAD to see if it is defined in the DECSERVER directory: $ SHOW LOGICAL MO*$LOAD MO*$LOAD must be defined to include SYS$SYSROOT:[DECSERVER].
Software Installation Problems At a UNIX load host, do the following Verify that all distribution software was installed in the appropriate directory: # cd /tftpboot (UNIX ) # ls -l The directory should contain the name of the access server software image and the file: Release_Notes.txt. If it does not contain the image name, refer to the Network Access Software Installation Guide for more information.
Software Installation Problems For more information on the DSV$CONFIGURE database, refer to the Network Access Software Installation Guide. At a UNIX load host: # /etc/list_Decserver myds: tc=DS.default: ha=08002BFC0176: ip=192.12.79.6: bf=MNENG2: gw=192.12.79.3: sm=255.255.255.0 If your access server is missing or contains incorrect information, refer to the Network Access Software Installation Guide for information on adding an access server.
Software Installation Problems At DECnet/OSI load hosts: Step Action 1 Enter a SHOW SYSTEM command to see if the Net$MOP process exists on the load host.
Software Installation Problems NCP> SHOW KNOWN LINKS If there are no known links active, enter the following commands to enable service circuit BNA-0. Enabling the circuit disconnects the active links.
Software Installation Problems Ensure the Access Server Software Image File Name Is Defined Correctly For an OpenVMS load host: Problem: The following message appears on the load host console: %%%%%%%%%%% OPCOM 29-NOV-2000 11:55:18 %%%%%%%%%%% Message from user DECNET on SATRN DECnet event 0.7, aborted service request From node 12.467 (SATRN), 29-NOV-2000 11:55:18 Circuit BNA-0, Line open error, File open error, Load file %MOM-E-OPENIN, error opening SYS$COMMON:[DECSERVER]WWENG2.
Software Installation Problems Successful Downline Load Messages Messages The following examples show the messages for a successful downline load. For an OpenVMS load host: Problem: The following messages appear on the load host console: %%%%%%%%%%% OPCOM 29-NOV-2000 11:55:18 %%%%%%%%%%% Message from user DECNET on SATRN DECnet event 0.3, automatic line service From node 12.467 (SATRN), 29-NOV-2000 11:55:18 Circuit BNA-0, Load, Requested, Node = 13.
Chapter 2 LAT Service Connection Problems Overview Introduction The following table lists the steps and page references to help you solve problems that can occur when you attempt to connect to various resources using the LAT protocol. Problem Solution See Page Connection to resources using the LAT protocol fails 1. Verify the LAT Service Configuration 2-2 2. Verify the LAT Service Node Software 2-2 3. Verify LAT Group Codes 2-4 4. Verify Access Server Memory Usage 2-6 5.
LAT Service Connection Problems Connection to Resources Using the LAT Protocol Fails Verify the LAT Service Configuration This section enables you to determine whether a LAT service is defined and properly configured on your access server. On the access server that offers the service, enter the following command. Substitute the name of the service for Local_Service.
LAT Service Connection Problems At an OpenVMS host (Version 5.4-1 and later): Ask the system manager of a node that offers the LAT service to invoke the port driver as follows: $ RUN SYS$SYSTEM:LATCP • If you do not receive the LATCP prompt, LAT software is not running on your OpenVMS service node. Action: Run LAT$STARTUP using the following command: $ @SYS$STARTUP:LAT$STARTUP.
LAT Service Connection Problems To allow both incoming and outgoing connections, use the following command: LATCP> SET NODE/CONNECTIONS=BOTH Verify LAT Group Codes To determine whether a user’s access server port has a group code in common with the service, enter the following command. Substitute the port number for 1. Local> SHOW PORT 1 Port 1: Mariellen S.
LAT Service Connection Problems For services offered by the access server that you are on, enter the following command on your access server: Local> SHOW SERVER CHARACTERISTICS Network Access SW Vn.n for DS716 BLnn ROM Vn.
LAT Service Connection Problems For services offered by a service node: At an OpenVMS host, enter the following commands: $ RUN SYS$SYSTEM:LATCP LATCP> SHOW CHARACTERISTICS Node Name: SATRN LAT Protocol Version: 5.
LAT Service Connection Problems Command Pool Size: 20480 bytes Command Pool Used: 8428 bytes MOP Pool Size: 4096 bytes MOP Pool Used: 148 bytes To display the memory configuration of your system, enter the following command: Local> SHOW MEMORY CONFIGURATION Dynamic RAM: 4M bytes Non-Volatile RAM: 128K bytes FlashRAM: Installed: Total size: Boot block: Load image: Name: Size: Version: Yes 2 Mbytes Valid WWENG2 1756988 bytes Network Access SW Vn.
LAT Service Connection Problems If the number of Resource Errors is greater than zero, the access server memory might be full. Make the following corrections: Step Action 1 Adjust the group codes to restrict the least-used nodes from being stored in the access server database. For information on group codes, refer to the Network Access Server Management Guide. 2 Adjust the access server node, session, and queue limits to restrict memory usage.
LAT Service Connection Problems Verify Service Rating To determine if a LAT service is available, verify the service rating. For services offered by the access server that you are on, enter the following command on your access server.
LAT Service Connection Problems Verify Nodes That Offer the Service To verify nodes that offer a LAT service, enter the following access server command. Substitute the user’s service name for MONAHON. Local> SHOW SERVICE MONAHON If there are any nodes that offer the service but should not, you need to remove the service.
LAT Service Connection Problems Verify Communications to Another Access Server If you are on a different access server than the one offering the service, verify that the two access servers can communicate. Enter the following command on the user’s access server: Local> TEST LOOP 08-2B-66-10-12-61 NOTE When you use the TEST LOOP command, enter the Ethernet address of the target access server.
Chapter 3 Telnet Resource Problems Overview Introduction The following table lists steps and page references to help you solve problems that can occur when you attempt to connect to various resources using the Telnet protocol. Problem Solution See Page Telnet Resource Connection Problems Steps 1. Verify Internet Address 3-2 2. Verify Internet Host Name 3-3 3. Verify Domain Name System (DNS) Parameters 3-3 4. Verify Communication to Remote Internet Host 3-3 5.
Telnet Resource Problems Telnet Resource Connection Problems Introduction If you experience problems connecting to a Telnet resource, verify the following: • Internet address • Internet host name • Domain name system parameters • Communication to remote Internet host • Network access server memory usage Verify Internet Address If you are unable to connect to a Telnet resource using an Internet address, enter the following command: Local> SHOW INTERNET State Internet Address: Subnet Mask: DHCP: E
Telnet Resource Problems Verify Internet Host Name If you are unable to connect to a Telnet resource using an Internet host name, enter the following command: Local> SHOW INTERNET HOST ALL Internet Address Name 195.1.1.60 195.1.1.62 SALES.MKTG.FOO.COM ACCT.MKTG.FOO.COM Verify that the Internet host name is defined in the Internet database. For more information on configuring the Internet host name, refer to the Network Access Software Management Guide.
Telnet Resource Problems This command establishes a PING session on the access server port. This session will continue until the PING succeeds (and sends a verification message) or until the timeout period of 30 seconds is exceeded. If this command fails, then the Internet host is unavailable. NOTE The PING command is the same as the TEST INTERNET command. For more information on the PING command, refer to the Network Access Software Commands Reference Guide.
Telnet Resource Problems Telnet Client Keyboard Characters Do Not Display Properly Solution If a keyboard character does not display properly during a Telnet session, enter the following command.
Telnet Resource Problems Telnet Client Characters Do Not Display on Terminal Solution If characters do not display during a Telnet session, enter the following command.
Telnet Resource Problems More Information For more information on configuring Telnet client session characteristics, refer to the Network Access Software Management Guide.
Telnet Resource Problems Telnet Client Hung Solution If your Telnet session appears to be hung, the Telnet remote partner could have abnormally disconnected the session. Enter the following commands on your access server port: Local> SEND TELNET AYT Local> SEND TELNET SYNC Local> RESUME SESSION If the connection is down, these commands cause retransmissions to the remote partner. If the remote partner does not respond within 7 minutes, the connection aborts with a timeout message.
Telnet Resource Problems Telnet Client Hung After Sending AO Character Solution If your Telnet session appears to be hung and you previously sent an AO (Abort Output) character to the host either directly or indirectly, enter the following command on your access server port to cancel the AO: Local> SEND TELNET RESUME OUTPUT When an AO is sent to the host, the access server also sends a timing mark.
Telnet Resource Problems Telnet Client Does Not Respond to the Return Key Solution If the Return key does not function properly during a Telnet session, enter the following command.
Telnet Resource Problems More Information For more information on configuring Telnet client session characteristics, refer to the Network Access Software Management Guide.
Telnet Resource Problems Telnet Client Editor Characters Not Functioning Properly Solution If you experience unusual responses to keystrokes when using various editors during a Telnet session, enter the following command. Substitute the number of the port for 1 and the number of the session for 2: Local> SHOW PORT 1 SESSION 2 CHARACTERISTICS Port 1, Session Profile: Echo: Toggle Echo: Binary: Xmit Size: Rcv Size: Signal Req.
Chapter 4 SLIP/PPP Problems Overview Introduction This chapter discusses troubleshooting procedures for problems that might occur when you attempt to connect to various resources using the SLIP, SLIP compression (CSLIP), or PPP protocols. For similar conditions, SLIP and PPP share many of the same error messages. As a result, a SLIP message may follow a PPP command.
SLIP/PPP Problems Problem 4-2 Solution See Page SLIP Session Starts, Then Freezes 4-10 PPP Connection Problems 4-11
SLIP/PPP Problems SLIP Connection Problems Introduction You can establish only one datalink session (either SLIP or PPP) on a port at a given time. If you have a session established, another session is not permitted. In addition, SLIP and PPP use the same IP address for a port. You can clear this address only when another datalink session is not using it. Verify SLIP/CSLIP Enabled To determine if SLIP is enabled on the access server port, enter the following command.
SLIP/PPP Problems Verify SLIP Host Address If you are unable to connect using the SLIP protocol, enter the following command. Substitute the number of the port for 1: Local> SHOW PORT 1 SLIP Port 1: Development Server: MMS Host Address: 83.62.18.102 Header Compression: Disabled MTU: 1006 Compression States 16 Verify that the SLIP Host Address is defined and valid. The Internet address for the SLIP host must be unique on the subnet and have the same subnet identifier as the access server.
SLIP/PPP Problems If the TCP MSS given by the SLIP host exceeds the MTU on the SLIP line, poor performance, failed connections, and fragmentation occur. Adjust the MTU on the access server. For more information on configuring and managing SLIP ports, refer to the Network Access Software Management Guide. Verify Multisessions - Interactive SLIP Connection Only If you are unable to connect to a SLIP host, enter the following command.
SLIP/PPP Problems • Verify that Autobaud is Disabled. (If Disabled, Autobaud does not appear in the list under Enabled Characteristics.) • Verify that Input Speed and Output Speed are consistent with that of the device. • Verify that Default Protocol is set to SLIP. • Verify that Dedicated Service is set to SLIP. • Verify that Access is either Local or Dynamic. For more information on configuring and managing SLIP ports, refer to the Network Access Software Management Guide.
SLIP/PPP Problems SLIP Session Losing Send Packets Solution If your SLIP session appears to be dropping send packets, enter the following command. Substitute the number of the port for 1: Local> SHOW PORT 1 SLIP COUNTERS Port 1: Development Server: MMS Connect Time: 7 23:00:40 Bytes Received: 106 Bytes Sent: 560 Packets Received: 200 Packets Sent: 150 Receive Packets Lost: 100 Send Packets Lost: 25 Send Packets Queued: 0 Procedure Verify the ratio of Send Packets Lost to Packets Sent.
SLIP/PPP Problems SLIP Session Not Receiving Input Solution If your SLIP session will not transmit or receive, check that the port’s speed and the PC’s communication port speed match. If your SLIP session seems to transmit but is not receiving input, enter the following command. Substitute the number of the port for 1: Local> SHOW PORT 1 SLIP Port 1: Development Server: MMS Host Address: 83.62.18.
SLIP/PPP Problems SLIP Session Will Not Learn the PC Internet Address Solution If the access server port is unable to learn the SLIP host address, verify that the Internet address for the SLIP host has the same subnet identifier as the access server and is unique. See the section Verify SLIP Host Address (page 4-4).
SLIP/PPP Problems SLIP Session Starts, Then Freezes Solution If your SLIP session starts, then freezes, do the following: • Verify that there are no devices between the PC and the access server using XON/XOFF flow control. • Verify that the PC is not running CSLIP. If you are using CSLIP, both the access server and the attached device must have CSLIP enabled. For more information on configuring and managing SLIP ports, refer to the Network Access Software Management Guide.
SLIP/PPP Problems PPP Connection Problems Introduction PPP connection problems can be traced to incomplete PPP negotiations between peers or to network traffic not being passed. The following sections discuss some symptoms and possible solutions. Attempts to Use Multiple Sessions on a Port You can establish only one datalink session (either SLIP or PPP) on a port at a given time. If you have a session established, another session is not permitted.
SLIP/PPP Problems • Verify that flow control is functioning properly. By default, the low 32 characters of the ASCII set are not sent across an asynchronous line in the clear. They are "byte-stuffed." LCP allows the user to specify that some of these characters are sent in the clear. If this is done, then possibly a character that is being sent in the clear is being acted upon by the underlying hardware or software.
SLIP/PPP Problems • ATCP always executes a PASSIVE open, which in effect forces the attached device to initiate negotiations. • If the access server cannot acquire an AppleTalk address from the AppleTalk cache manager, ATCP cannot reach the OPEN state. • The peer's MTU may be too low. To determine the size of the MRU, enter the SHOW PORT LCP STATUS command and check the MRU field. The peer may negotiate the use of an MRU other than the default of 1500 bytes.
SLIP/PPP Problems Checking the Port’s PPP/IPX Configuration Type SHOW PORT n LCP CHARACTERISTICS and SHOW PORT n IPXCP CHARACTERISTICS to check the current PPP characteristics and verify that both LCP and IPXCP are enabled. Substitute the number of the port for ‘n’. Monitoring PPP/IPX Negotiations for Failure Reason If possible, you may want to monitor the port as the PPP negotiations occur after modem login. Type MONITOR PORT n LCP STATUS or MONITOR PORT n IPXCP STATUS.
SLIP/PPP Problems Failure Reasons Introduction When you display status, a failure reason field appears. Table: Failure Reasons describes the possible failure reasons. Failure Reason Description None No failure reason. Resources Insufficient resources. This error condition occurs when setting up an address for a port fails, typically due to insufficient system resources. Not converging Option negotiations are not converging.
SLIP/PPP Problems Failure Reason Description Peer address bad This occurs if the address negotiated for the peer is invalid. For IPXCP, this error occurs if the address is already in use or if the client agreed to use the server’s internal network but did not negotiate a unique node address. No net address Indicates the server does not have a net/node address for itself. Verify that the server’s internal IPX network has been set.
Chapter 5 AppleTalk Access Problems Overview Introduction The following table lists the steps and page references to help you solve problems that can occur when using the AppleTalk functionality on the access server. Problem Solution See Page Problems with Hosts Attached to Access Server Ports 1. Verify AppleTalk Is Enabled 5-3 2. Verify AppleTalk State Is Up 5-3 3. Verify AppleTalk Address Is Within the Network Range 5-4 4. Verify Cache Size Is Correct 5-4 5.
AppleTalk Access Problems 2. Verify Protocol Retransmission Timeouts 5-7 3. AppleTalk Gateway Route 5-8 Problems with attached host connections running AppleTalk are not discussed here, but are covered in Chapter 4.
AppleTalk Access Problems Problems with Hosts Attached to Access Server Ports Introduction If you experience problems creating an AppleTalk connection from an attached host or polling the access server from a network management station (NMS), verify the following: • AppleTalk is enabled on the access server. • AppleTalk state is Up. • AppleTalk address is within the network range. • Cache size is nonzero. • Access server is visible on the network. • Attached host is running AppleTalk over PPP.
AppleTalk Access Problems Verify AppleTalk Address Is Within the Network Range It is possible that the AppleTalk address is outside the network range. This situation can occur momentarily while the access server is booting and is considered normal. However, if this situation persists for more than a minute after initialization, then the problem could be caused by one of the following reasons: • All valid addresses in the network range are in use.
AppleTalk Access Problems • Access server could not acquire addresses in the network range. If this occurs, the access server sets the Last Error field in the SHOW APPLETALK STATUS display as follows: Attempt to acquire an AppleTalk address for cache failed Refer to the section Verify AppleTalk Address Is Within the Network Range for reasons why this can occur.
AppleTalk Access Problems To determine if ATCP is enabled on the access server port, enter the following command. Substitute the port number for 1: Local> SHOW PORT 1 ATCP The ATCP field should be set to Enabled. For more information on configuring and managing ATCP ports, refer to the Network Access Software Management Guide. Verify Attached Device Is an End Node The access server provides connections for devices acting as AppleTalk end nodes.
AppleTalk Access Problems Performance Problems Introduction It is possible that AppleTalk connections can be established, but performance is sluggish or unreliable. Some symptoms of this are long file transfer times or inability to access some services on the network. These problems are usually due to the slower data rates of remote connections. We recommend that remote AppleTalk connections by means of the access server run at rates of 9600 baud or higher.
AppleTalk Access Problems AppleTalk Gateway Route Solution If the AppleTalk node to which you wish to connect is outside your local LAN, there may be a problem connecting to a router between the LANs. The access server keeps track of a default AppleTalk router to which it directs all attached host-generated AppleTalk traffic that is destined off the local network.
Chapter 6 SNMP Access Problems Overview Introduction The following table lists page references to help you solve Simple Network Management Protocol (SNMP) problems. Problem Solution See Page SNMP Reporting Is Not Consistent with the access server 6-2 SNMP Reporting Is Not Consistent with the MIB 6-3 Problems Accessing the access server 1. Verify SNMP Enabled 6-4 2. Verify Community Name Access Information 6-5 3. Verify Operations Enabled for the Community Name 6-5 4.
SNMP Access Problems SNMP Reporting Is Not Consistent with the Access Server Solution If the data reported by SNMP does not appear to be consistent with that reported by the access server user interface, verify that the information in question is correct. For more information, refer to the Network Access Software Management Guide, the release notes, and the management information bases (MIBs).
SNMP Access Problems SNMP Reporting Is Not Consistent with the MIB Solution If the data reported by SNMP does not appear to be consistent with that reported by the MIB, verify that the information in question is correct. For more information, refer to the Network Access Software Management Guide and the release notes.
SNMP Access Problems Problems Accessing the Access Server Introduction If you experience problems with your access server responding to SNMP requests from a network management station (NMS), verify the following: • SNMP enabled • Community name access information • Operations enabled for the community name • Network configuration • Communication to a remote NMS Verify SNMP Enabled To determine if SNMP is enabled on the access server, enter the following command: Local> SHOW SNMP SNMP State: Enab
SNMP Access Problems Verify Community Name Access Information In order to communicate using SNMP, the user on the NMS must know the community name on the access server. To determine which community names exist on an access server, enter the following command: Local> SHOW SNMP SNMP State: Enabled Authentication Failure: Enabled Community Name Address GET GETNEXT SET TRAP PUBLIC SECRET ANY 60.10.12.
SNMP Access Problems Verify Network Configuration If the access server and network management station (NMS) are on different subnetworks, verify that there are one or more routers connecting the two subnetworks. If not, reconfigure the network or move either the access server or the NMS so that they are on the same network. If one or more routers exist between the access server and the NMS, verify that the routers are configured to pass SNMP messages.
SNMP Access Problems Access Server Not Responding with the Requested MIB Information Solution If your access server is not responding with the correct management information bases (MIBs), verify the MIB version on the network management station (NMS). The current MIB version of the access server fully supports the following specifications: RFC1158 - Obsoleted MIB II. Supported for backwards compatibility. RFC1213 - Management Information Base (MIB II) for Internet protocol suite management.
SNMP Access Problems • If the NMS does not support these exact versions of the MIBs but does support MIB enrollment, do the following: — Use the MIBs provided in the software installation kit as input for the MIB enrollment process. — Configure the NMS to associate these versions of the MIBs with the access server.
SNMP Access Problems Access Server Not Sending TRAP Messages If the access server is not sending TRAP messages to the Network Management Station (NMS), do the following: Step Action 1 Enter the following command on your access server: Local> SHOW SNMP SNMP State: Enabled Authentication Failure: Enabled Community Name Address PUBLIC SECRET GET ANY ENA 60.10.12.
SNMP Access Problems Authentication Failure TRAP Messages Reported Solution If an NMS is receiving authentication failure TRAP messages, the problem is that a network management station (NMS) is illegally trying to access the access server. Verify the following: 6-10 • If you are using gateways, configure the gateways between your network and the public network to filter SNMP messages. This will prevent an NMS from accessing the access server.
SNMP Access Problems Authentication Failure TRAP Messages Not Reported Solution If you suspect a network management station (NMS) is not receiving authentication failure TRAP messages from the access server, enter the following command: Local> SHOW SNMP SNMP State: Enabled Community Name PUBLIC SECRET • Authentication Address ANY 60.10.12.61 Failure: Enabled GET GETNEXT SET TRAP ENA ENA ENA ENA DIS DIS DIS ENA Verify that Authentication Failure is Enabled.
Chapter 7 3270 Terminal Emulation (TN3270) Access Problems Overview Introduction The following table lists steps and page references to help you solve TN3270 terminal emulation problems. Problem Solution See Page TN3270 Connection Problem 1. Verify Display Station Model Configuration 7-2 2. Verify ASCII Terminal Configuration 7-3 3. Verify the TN3270 Session Using the Status Line Function 7-3 4.
3270 Terminal Emulation (TN3270) Access Problems TN3270 Connection Problems Introduction If you experience problems with TN3270 connections and keymap functions, verify the following: • TN3270 model configuration • ASCII terminal configuration • TN3270 session status line • Keyboard mapping • Telnet negotiations Verify Display Station Model Configuration If a connection to an IBM system does not display formatted screens, verify that your display station model is configured properly.
3270 Terminal Emulation (TN3270) Access Problems For more information on configuring Display Station models for TN3270 access, refer to the Network Access Software Management Guide.
3270 Terminal Emulation (TN3270) Access Problems Table: Messages Appearing in the Status Line Indicator Message Description EXTEND You have pressed the EXT function. HIDDEN The status line is covering some screen data that you have not yet seen. This indicator turns off when you enable the status display after viewing the hidden data. INSERT The terminal is in insert mode. INHIB The application has suspended input from the keyboard.
3270 Terminal Emulation (TN3270) Access Problems To display the default keyboard map assigned to your port, enter the following command: Local> SHOW PORT 1 TN3270 CHARACTERISTICS Port 1: test Model: NONE Input Flow Control: Terminal: VT100 Output Flow Control: Keymap Default: VT100 Verification: Keymap NVRAM Limit: 0 Switch Character: Nulls: 3179 Enabled Enabled Enabled Enabled If the Keymap Default setting does not reflect your configuration, enter the following command.
3270 Terminal Emulation (TN3270) Access Problems Default Keyboard Maps Unsuitable Solution Before connection, you can customize any of the key definitions on the default keyboard map to suit your keyboard. For example, the following command defines the ASCII code for the IBM 3270 NEWLINE function: Local> CHANGE PORT TN3270 KEYMAP NEWLINE Ctrl/J In this example, the ASCII sequence Ctrl/J maps to the NEWLINE function.
3270 Terminal Emulation (TN3270) Access Problems Telnet Negotiations Problems Solution When you are using a TN3270 connection, certain Telnet options must negotiate successfully.
Chapter 8 User Authentication Configuration Problems Overview Introduction You can use the following types of security servers: • Kerberos • RADIUS • SecurID™ • Local User Accounts The following table lists the steps and page references to help you solve security configuration problems. Problem Solution See Page Security Configuration 1. Verify That Devices Are Connected Properly 8-3 2. Verify That Authentication Is Enabled 8-5 3.
User Authentication Configuration Problems This chapter discusses troubleshooting procedures for problems using the Kerberos, RADIUS and SecurID security user authentication systems. For information about the Local User Accounts security system, see the Network Access Software Management Guide.
User Authentication Configuration Problems Verify That Devices Are Connected Properly Procedure Problems that appear to be user authentication problems can occur if the devices on your system are not connected properly. For information about connecting device cables, refer to the access server hardware documentation.
User Authentication Configuration Problems Verify That the Device Is Using the Correct Authentication Protocol Procedure Be sure that you attached device (terminal, PC, Macintosh, or workstation) is configured with an authentication protocol matching the one enabled on the access server’s port. For PPP connections the options are PAP and CHAP. For SLIP or character cell terminal connections, interactive authentication must be used.
User Authentication Configuration Problems Verify That Authentication Is Enabled Procedure To use the security user authentication system, you must enable authentication for each port. To display the user authentication settings for an interactive user port, use the following command.
User Authentication Configuration Problems To display the user authentication settings for a network access port, use the following command.
User Authentication Configuration Problems Verify That Port and Devices Characteristics Match Procedure In order for user authentication to function properly, you must ensure that the physical characteristics of the access server port match the physical characteristics of the device. Verify that the following port and device characteristics match: Autobaud, Character Size, Parity, Speed, Stop Bits, and Type To display the physical characteristics of the access server port, use the following command.
User Authentication Configuration Problems Verify the Access Server and Security Configuration Procedure If the access server is not able to communicate over the network with a Kerberos security server, verify with the security system administrator that the access server is registered with all security servers within the same security realm, if using Kerberos, and that each realm has one master security server that contains a write-enabled database.
User Authentication Configuration Problems Verify the User’s Authorization Data Procedure Check these conditions: • If the user’s authorization information is incomplete or inconsistent, the user login may fail. If this happens, the security system administrator should verify that the services specified to be delivered to the user are consistent with the services enabled and available on both the individual access server port(s) and on the access server as a system.
Chapter 9 Telnet Remote Console, Connection and Port Problems Overview Introduction The following table lists steps and page references to help you solve problems that can occur when you attempt to establish a Telnet remote console connection. It also provides information on troubleshooting console port problems. Problem Solution See Page Telnet Remote Console Connection Problems 1. Verify Internet Address 9-2 2. Verify Telnet Listener Configuration 9-2 3.
Telnet Remote Console, Connection and Port Problems Telnet Remote Console Connection Problems Introduction If you experience problems establishing a remote console connection using Telnet, verify the following: • Internet address • Telnet listener configuration • Access server memory usage • Remote console port status Verify Internet Address If you are unable to establish a Telnet remote console connection, verify that the Internet address has been set on the access server.
Telnet Remote Console, Connection and Port Problems Verify Remote Console Port Status Only one remote console connection (MOP or Telnet) is allowed at a time. To determine if the remote console port is already in use, enter the following command: Local> SHOW SERVER STATUS If the remote console port is in use, the Console User characteristic displays either the Ethernet address (MOP) or the Internet address (Telnet) of the connected host.
Telnet Remote Console, Connection and Port Problems Console Port Problems Solution When the console port does not display 900-series messages, the problem might be that the port to which the terminal is physically connected is not defined as the console port or the console terminal is faulty. To determine if the port to which the terminal is physically connected is defined as the console port, enter the following command: Local> SHOW SERVER Network Access SW Vn.n for DS716 BLnn-nn ROM Vn.
Chapter 10 Terminal and Personal Computer Problems Overview Introduction The following table lists steps and page references to help you solve problems that appear to affect individual access server ports or interactive port devices, such as terminals and personal computers (PCs). Problem Solution See Page Problems With Interactive Devices 1. Device Does Not Respond or Nonsense Characters Appear 10-3 2. Characters Not Displayed on the Device 10-4 3. Command Line Recall Not Working 10-6 4.
Terminal and Personal Computer Problems Port and Device Problems Problem Action Power • • • • Ensure that the device is plugged into an active outlet. Ensure that the power switch is on. If the device has a fuse, replace it. If the device has a circuit breaker, reset it. Cables • • • Ensure that the device cable is secure at both ends. If the cable is spliced, ensure that all junctions are secure. Verify all device cable connections at couplers, adapters, and cable concentrators (harmonica).
Terminal and Personal Computer Problems Problems with Interactive Devices Solution An interactive device can be a terminal with a video monitor and keyboard, a printer with a keyboard, or a personal computer in terminal-emulation mode. If you have a problem with an interactive device, use the procedures described in Port and Device Problems table. If the problem persists, find the problem in the following sections.
Terminal and Personal Computer Problems b. Verify that the problem port has a Dedicated Service defined. If a dedicated service is defined, verify that the service is available. If the service is available, verify that the problem port and the service have a common group code. See the section Verify LAT Group Codes (page 2-4). c. Verify that Access is set to Local or Dynamic. If Access is set to Dynamic, set the Interrupts characteristic to Enabled.
Terminal and Personal Computer Problems Local> SHOW PORT 1 Port 1: Michael Server: GEMINI Character Size: 8 Flow Control: XON Parity: None Stop Bits: Dynamic Input Speed: 9600 Output Speed: 9600 Signal Control: Disabled Signal Select: CTS-DSR-RTS-DTR Access: Local Backwards Switch: None Break: Local Forwards Switch: ‘ Default Protocol: LAT Autolink Timer One:10 Two:10 Local Switch: ^^ Name: PORT_1 Session Limit: 8 Type: Ansi Default Menu: None Dialer Script: None Preferred Service: GALAXY Authorized
Terminal and Personal Computer Problems Command Line Recall Not Working If command line recall is not working, enter the following command.
Terminal and Personal Computer Problems Terminal Screen Scrolling When MONITOR Command Is Used If your terminal screen scrolls when you use the MONITOR command, enter the following command.
Terminal and Personal Computer Problems Verifying a Port for Hardware Failure Procedure To determine if there is a problem with the hardware, do the following: 1 Verify the status of the access server. Enter the following command: Local> SHOW SERVER STATUS Network Access SW Vn.0 for DS716 BLnn-nn ROM Vn.
Terminal and Personal Computer Problems c. From another port, enter the following command. Substitute the number of the port for 1: Local> TEST PORT 1 LOOPBACK EXTERNAL You can also specify an internal loopback to verify internal port hardware. Use the following command: Local> TEST PORT 1 LOOPBACK INTERNAL NOTE When you use the TEST PORT command for loopbacks, the input and the output speeds for the port must be the same.
Terminal and Personal Computer Problems PC File Transfer Fails over a LAT Network Solution If a PC file transfer fails over a LAT network, do the following: Step Action 1 To determine if flow control is required, refer to your file transfer program documentation. For more information on setting up flow control on an access server port, refer to the Network Access Software Management Guide.
Terminal and Personal Computer Problems PC File Transfer Fails over a SLIP Network Solution If a PC file transfer fails over a SLIP or PPP network, do the following: Step Action 1 Verify that there are no devices using flow control between the PC and the access server. 2 Verify the file transfer program to determine if it is in the correct mode. Some programs (such as FTP) have one mode for ASCII text files and another mode for binary data.
Terminal and Personal Computer Problems PC File Transfer Fails over a Telnet Network Solution If a PC file transfer fails over a TCP/IP network, do the following: 1 Enter the following command on the PC port of your access server.
Chapter 11 Printer Configuration Problems Overview Introduction The following table lists steps and page references to help you solve printer configuration problems. Printers can be configured on the access server for access through either a LAT service or a Telnet listener. Problem Solution See Page Printer Configuration Problems 1. Verify the Physical Port Characteristics 11-2 2. Verify the Port Configuration 11-3 3. Test the Printer Port 11-4 4. Verify Access Server Information 11-5 1.
Printer Configuration Problems Verify the Physical Port Characteristics Procedure The table Port and Device Problems lists the first items to verify when you have problems involving a printer (or any other device) and its port. For example, make sure that the Speed, Parity, and Character Size characteristics defined for the port match the printer’s settings. Once you have verified that the port characteristics are configured properly, try printing again. If you cannot print, use the TEST PORT command.
Printer Configuration Problems Verify the Port Configuration Procedure • Verify that the printer port is configured correctly.
Printer Configuration Problems Test the Printer Port Procedure To test a printer port, enter the following command on your access server. Substitute the number of the port for 1. Specify COUNT 10 for line printers and COUNT 70 (or greater) for laser printers: Local> TEST PORT 1 COUNT 70 NOTE The TEST PORT command is valid only when sending data to ANSI devices. However, the Port Type characteristic does not have to be set to ANSI.
Printer Configuration Problems Verify Access Server Information Procedure Verify the following information on the access server: 1 Verify the access server local connection queue to see if jobs are being placed in the queue. Enter the following command on your access server.
Printer Configuration Problems Access: Remote Current Service: SATURN Status: Connected Current Node: SATURN Sessions: 1 Current Port: Input XOFFed: No Output Signals: Output XOFFed: Yes Input Signals: DTR DSR Look at the display to see if the port status is in the Connected state. If the port is in the Connected state, there is an active session on the port. 4 Verify if Signal Check is working properly. Unplug the cable from the printer and enter the following command on your access server.
Printer Configuration Problems LAT Printing Problems Introduction If the device characteristics (see the section Verify the Physical Port Characteristics), port configuration (see the section Verify the Port Configuration), printer device and cables (see the section Test the Printer Port), and the access server information (see the section Verify Access Server Information) have been verified, do the following: Determine the Point of Failure To determine the point of failure, do the following At an OpenVMS
Printer Configuration Problems On the access server, enter the following command.
Printer Configuration Problems At an OpenVMS host, enter the following commands. Substitute the number of the LTA: port for 8000: $ RUN SYS$SYSTEM:LATCP LATCP> SHOW PORT LTA8000 Local Port Name: _LTA8000: (Queued) Local Port State: Local Port Type: Application Inactive Connected Link: Target Port Name: PORT_2 Actual Port Name: Target Node Name: MMS1 Actual Node Name: Target Service Name: Actual Service Name: ----------------------------------------------------------LAT Control Program, Version 5.
Printer Configuration Problems Having the queue in a paused state usually means a hard error. Perform the following to determine why: Step Action 1 Verify to see if the wrong queue processor is being used. Enter the following command.
Printer Configuration Problems Step Action 3 Check the print queue for any LAT error messages. Enter the following command.
Printer Configuration Problems Verify LAT Group Codes Verify that the group codes on the service node match that of the access server. At an OpenVMS host, enter the following commands: $ RUN SYS$SYSTEM:LATCP LATCP> SHOW CHARACTERISTICS Node Name: SATRN LAT Node State: On Node Ident: A VAX 6250 Cluster Member Protocol Version: 5.
Printer Configuration Problems On the access server, enter the following command: Local> SHOW SERVER Access Server Vn.0 for DSnnn-nn BLnn ROM Vn.
Printer Configuration Problems Telnet Printing Problems Introduction If the device characteristics (see the section Verify the Physical Port Characteristics), port configuration (see the section Verify the Port Configuration), printer device and cables (see the section Test the Printer Port), and access server information (see the section Verify Access Server Information) have been verified, perform the procedures in the sections Verify Telnet Listener Configuration and Verify Characteristics on Host Syste
Printer Configuration Problems Telnet Printer Not Creating a Newline Solution If your printer does not create a newline when printing, enter the following command on your access server.
Chapter 12 Computer Configuration Problems Overview Introduction The following table lists page references to help you solve problems that can occur when you attempt to access computers directly connected to access server ports. These connected devices are offered for access through either a LAT service or a Telnet listener.
Computer Configuration Problems Unable to Connect to a Computer Offered as a LAT Service Solution If you are unable to connect to a computer offered as a LAT service, do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command.
Computer Configuration Problems Computer Does Not Respond to LAT Service Connection Solution If you can connect to the LAT service but the computer does not respond, do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command.
Computer Configuration Problems Step Action 6 Monitor the port status to determine which modem signals are being asserted. Enter the following command on your access server.
Computer Configuration Problems Unable to Access a Computer Through a Telnet Listener Solution If you are unable to access a computer through a Telnet listener, do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command. Substitute the number of the port for 1: Local> SHOW PORT 1 The SHOW PORT display will vary depending on the hardware you are using.
Computer Configuration Problems Connected to Telnet Listener but Computer Does Not Respond Solution If you can connect to the Telnet listener but the computer does not respond, do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command.
Computer Configuration Problems Step Action 6 Monitor the port status to determine which modem signals are being asserted. Enter the following command on your access server.
Computer Configuration Problems Connection to a Telnet Listener Results in Double Echoes or Double Lines Solution If you are experiencing problems with double echoes or double lines after connecting to a Telnet listener, the problem might be that the attached Telnet listener host system and the Telnet client are both performing echoing. This is because the Telnet listener on the access server does not explicitly negotiate echoing when establishing a Telnet connection.
Chapter 13 Modem Configuration Problems Overview Introduction The following table lists page references to help you solve problems that can occur when you try to connect to a modem. Modems may be offered for dial-in access, dial-out access, or both.
Modem Configuration Problems NOTE 13-2 Configure DSR so that it complies with ITU (CCITT) recommendations.
Modem Configuration Problems Dial-In Modem Does Not Answer the Telephone Solution If the dial-in modem does not answer the phone, follow the dial-in user and access server manager procedures. Dial-In User Procedure Dial-in user should do the following: Step Action 1 Verify that the dial-in telephone number is correct. 2 Connect a telephone to the telephone line port on the modem (if provided) and put the modem into Talk mode (usually by pushing a button). Listen for a dial tone.
Modem Configuration Problems 13-4 Step Action 3 When the access server receives the call, verify that the dial-in modem is detecting data terminal ready (DTR). Usually, there is a light on the modem marked DTR or TD. Most modems will not answer without this signal. 4 If the modem is not detecting DTR, the modem cable might be faulty. Replace the cable and retry.
Modem Configuration Problems Dial-In Modem Answers but Carrier Detect Light Is Off Solution If the modem answers the telephone, but the carrier detect (CD or CAR) light is not on, the dial-in user should do the following: Step Action 1 Verify that the speed of your modem and that of the dial-in modem are the same. Contact the person responsible for the dial-in modem to determine its speed.
Modem Configuration Problems Dial-in Modem Is Unable to Communicate with the Access Server Solution If the modem answers the telephone and the CD (or CAR) light comes on, but you cannot communicate with the access server, follow the dial-in user and access server manager procedures. Dial-in User Procedure Dial-in user should do the following: 13-6 Step Action 1 If your modem has alternate speed (or fallback) capability, it is possible your modem might be using the alternate speed.
Modem Configuration Problems Access Server Manager Procedure Access server manager should do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command. Substitute the number of the dial-in modem port for 1: Local> SHOW PORT 1 The SHOW PORT display will vary depending on the hardware you are using.
Modem Configuration Problems Dial-In Modem Disconnects from the Server Solution If the dial-in modem disconnects from the server, the problem can be the result of one of the following conditions: • Noise on the line caused either your modem or the server modem to react as if the phone were hung up. Try the following: — Use a different phone jack or — Set the modem to a slower speed • The server is configured to call you back before granting you access.
Modem Configuration Problems Cannot Connect to Dial-Out Modem Offered as a LAT Service Solution If you cannot connect to the dial-out modem offered as a LAT service, do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command.
Modem Configuration Problems Connected to LAT Service but Dial-Out Modem Does Not Respond Solution If you can connect to the LAT service but you cannot communicate with the dial-out modem, do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command.
Modem Configuration Problems Step Action 8 Monitor the port status to determine which modem signals are being asserted. Enter the following command on your access server.
Modem Configuration Problems Cannot Connect to Dial-Out Modem Through a Telnet Listener Solution If you are unable to connect to a dial-out modem through a Telnet listener, do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command.
Modem Configuration Problems Connected to Telnet Listener but Dial-Out Modem Does Not Respond Solution If you can connect to the Telnet listener but the modem does not respond, do the following: Step Action 1 Verify that the physical port characteristics are configured correctly (Port and Device Problems). 2 Verify that the port is configured correctly. Enter the following command.
Modem Configuration Problems Step Action 8 Monitor the port status to determine which modem signals are being asserted. Enter the following command on your access server.
Modem Configuration Problems Cannot Complete Dial-Out to Remote Modem Solution If you can communicate with the modem but cannot complete the dial-out to the remote modem, verify the following: Step Action 1 If your access server supports alternate speed and your modem has alternate speed (or fallback) capability, it is possible your modem might be using the alternate speed. Set the access server modem port to the alternate speed while the connection is up and perform your normal login sequence.
Modem Configuration Problems Cannot Complete a Dialback Request Using a Dialer Service Solution If you requested a callback but the server did not call you back, do the following: Step Action 1 Verify that the port is configured correctly. Enter the following command. Substitute the number of the port for 1: Local> SHOW PORT 1 The SHOW PORT display will vary depending on the hardware you are using.
Chapter 14 IPX Problems Overview Introduction The following table lists steps and page references to help you solve problems that can occur when using the IPX protocol on the access server. Problem Solution See Page Problems with Dialing In to Access Server Ports 1. Checking PC Client Status Messages 14-2 2. Checking Cabling Between Port and Modem or Device 14-2 3. Checking Configuration of Attached Device 14-2 4. Checking Configuration for Login Method 14-2 5.
IPX Problems Problems with Dialing In to Access Server Ports Introduction If you experience problems with your PC client when dialing and logging in to access server ports, verify the following on the access server: • PC client status messages • Correct cabling between port and modem or device • Port configured correctly for attached device • Port configured correctly for login method • Active dial-in and login attempts function properly • PC client user understands login procedure Checking PC
IPX Problems Monitoring Active Dial-In and Login Attempt You may want to monitor the port as the modem dial-in and login attempt is being made by the PC client. Type MONITOR PORT n STATUS and verify that: • Output signals DTR/RTS are present • Input signals CTS, DSR, and RXD are present and status goes from "idle" to "local mode" when the dial-in modem makes its connection and the PC user logs in. Status goes to "Connected" and service goes to "PPP" when PPP is negotiated.
IPX Problems Problems With PPP/IPX Negotiations on the Access Server Port Solution If problems with PPP/IPX negotiations remain after successful dial-in and login, refer to Chapter 4.
IPX Problems Problems with Attaching to a Novell File Server Introduction If problems with connecting to a NetWare file server occur after successful dial-in, login, and PPP negotiations, verify the following: • Check the PC client status messages. • Check that the IPX frame type has a network address. • Check that SAP services are available. Checking PC Client Status Messages Check the remote node access software used on the PC client when connecting.
IPX Problems Problems with Relatively Slow File Transfer Solution If file transfer to or from Novell file servers seem unusually slow, type SHOW PORT n COUNTERS. Substitute the number of the port for ‘n’. If Send Packets Lost or Receive Packets Lost is high, check if the PC client user has NetWare Packet Burst enabled for the NetWare connection. Ask the PC client user to disable Packet Burst and try the file transfer again.
Chapter 15 Accounting Problems Overview Introduction The following table lists steps and page references to help you solve problems that can occur when using the accounting component on the access server. Problem Solution See Page Problems with Accounting Log Steps 1. Verify the Log Size 15-2 2. Verify That the Threshold is Appropriate 15-3 Problems with Accounting Console Logging 1. Verify Console Logging Is Enabled 15-4 2.
Accounting Problems Problems with Accounting Log Introduction If you experience problems creating an Accounting log file, verify the following: • The access server has enough memory to accommodate the LOG SIZE requirements of the accounting component. • The LOG SIZE specification is a valid value. • The THRESHOLD specification is appropriate.
Accounting Problems Verify That the Threshold is Appropriate To verify that the logging threshold is appropriate, enter the following command: Local> SHOW ACCOUNTING CHARACTERISTICS Accounting Characteristics: Threshold: None Log Size: 128K Console Logging: Enabled To change the threshold parameter, enter the following commands (substituting your desired threshold for QUARTER): Local> CHANGE ACCOUNTING THRESHOLD QUARTER 15-3
Accounting Problems Problems with Accounting Console Logging Introduction If you experience problems getting the accounting component to display events to the server console port as they occur, verify the following: • Console logging is enabled. • Server console port is enabled.
Accounting Problems Verify Server Console Port To verify that the server console port is enabled, enter the following command: Local> SHOW SERVER Network Access SW Vx.x for DS716 BLxx-xx ROM Vx.
Chapter 16 Remote Login Problems Overview The information in this chapter describes some of the problems you may encounter when managing the Rlogin feature of the access server software.
Remote Login Problems Rlogin Connection Problems If you experience problems connecting to a Rlogin resource, verify the following: 16-2 • Internet address • Internet host name • Domain name system parameters • Communication to remote Internet host • Access server memory usage • Rlogin server username
Remote Login Problems Verify Internet Address If you are unable to connect to a Rlogin resource using an Internet address, enter the following command: Local> SHOW INTERNET State: Internet Address: Subnet Mask: DHCP: Enabled 0.0.0.0 (Learning) 0.0.0.0 Enabled TCP Keepalive Timer: TCP Keepalive Retry: 120 8 Step Action 1 Verify that the Internet address and subnet mask are correct.
Remote Login Problems Verify Domain Name System (DNS) Parameters If you are unable to connect to a Rlogin resource using an Internet host name, enter the following command: Local> SHOW INTERNET NAME RESOLUTION CHARACTERISTICS Domain Name: MKTG.FOO.COM Resolution Host Limit: 32 Resolution Time Limit: 4 Resolution Mode: Ordered Resolution Retry Limit: 3 Nameservers: (Locally configured) 195.1.1.81 Local NAMED.MKTG.FOO.COM Nameservers: (Learned) 195.1.1.91 Local ELF.MKTG.FOO.COM 195.1.1.16 Local MINE.FOO.
Remote Login Problems Verify Access Server Memory Usage The access server has a limited pool of memory. With large networks or many port sessions, it is possible to run out of memory. When access server memory is filled, the access server cannot start additional Rlogin sessions.
Remote Login Problems Resource errors indicate the number of times an internal data structure could not be created due to the lack of system memory. To look at resource errors, enter the following command: Local> SHOW SERVER STATUS Network Access SW Vn.n for DS716 BLnn ROM Vn.
Remote Login Problems If the number of Resource Errors is greater than zero, the access server memory might be full. Make the following corrections: Step Action 1 Adjust the Internet Name Resolution Host Limit to store fewer nameservers, which further restricts memory usage. For information on managing an access server, refer to the Network Access Software Management Guide. Reducing the node limit can immediately reduce the number of service nodes stored in the database.
Remote Login Problems If the username is not specified on the command line, the port username is usually the name used. The following are exceptions to this situation: • If you have changed your port’s username since logging in, the username used to authenticate to the access server is the username used by Rlogin. The name given by SHOW PORT AUTHORIZATION is in the form "name@realm." Rlogin uses the name from "name@realm.
Remote Login Problems Rlogin Client Characters Do Not Display on Terminal Solution If characters do not display during a Rlogin session, enter the following command. Substitute the number of the port for 1. Local> SHOW PORT 1 RLOGIN CHARACTERISTICS Rlogin Characteristics Port 1: Terminal type: Unknown Escape character: ~ Suspend input to server: ^y Suspend server I/O: ^z Procedure Do the following: Step Action 1 Use Ctrl/] to get a Local> prompt.
Remote Login Problems Rlogin Client Hung Solution If your Rlogin session appears to be hung, the Rlogin remote partner could have abnormally disconnected the session, but you might have suspended input and output to the server. Verify that this is not the case by following the steps in Rlogin Client Characters Do Not Display on Terminal in this chapter. Unlike Telnet, there is no mechanism to recover an abnormally disconnected Rlogin session.
Remote Login Problems Rlogin Client Hung After Entering Suspend Input or Suspend IO Sequence Solution If your Rlogin session appears to be hung and you previously entered either the suspend input or suspend IO sequence, you must enter the suspend input character or suspend IO character again, to toggle the effects off. NOTE Entering either of the suspend characters without first entering the Rlogin escape character will not cause the Rlogin client to suspend any communication.
Remote Login Problems Rlogin Client Editor Characters Not Functioning Properly Solution If you experience unusual responses to Ctrl/S or Ctrl/Q keystrokes when using various editors during a Rlogin session, the terminal or terminal emulator settings must be adjusted. Reset your terminal so that it does not use XON/XOFF flow control.
Remote Login Problems Rlogin Terminal Type "Unknown" Insufficient for Some Applications Solution Change the Rlogin terminal setting using the following command: SET/DEFINE/CHANGE PORT RLOGIN TERMINAL VTxxx Only terminal types of VTxxx, where xxx is some integer, are permitted. If VTxxx does not sufficiently describe your terminal type, then start a Rlogin session normally and modify your environment variable that controls the terminal type.
Chapter 17 Directed TFTP Problems Overview This chapter describes some of the problems you may encounter after configuring your access server for Directed TFTP.
Directed TFTP Problems Missing Access Server IP Address The access server must have a local IP address at the time TFTP load requests are issued. This address may come from the access server’s NVRAM, for example, a DEFINE INTERNET ADDRESS command, from the Mini-Monitor, for example, a set IP address command (>>> s ip), or from a BOOTP reply packet. In the case of Directed TFTP, the latter option does not apply.
Directed TFTP Problems Missing Default Gateway IP Address If the TFTP server is not located in the same IP LAN subnet (i.e. reachable using ARP), then the access server must have a default gateway IP address configured. This address may come from the access server’s NVRAM, i.e. a DEFINE INTERNET GATEWAY command, from the Mini-Monitor, for example, the set gateway command (>>> s gw), or from a BOOTP reply packet. In the case of Directed TFTP, the latter option does not apply.
Directed TFTP Problems Incorrect Filename The access server must have the load image file name configured to perform a TFTP load. Typically the access server stores only the filename without any path information or file extension. The fully qualified pathname is typically specified by the BOOTP reply packet.
Directed TFTP Problems No or Poor Network Connectivity You may receive a timeout status message on the access server physical console port. If network connectivity is poor, the firmware will continue to retry, but the download may not ever complete successfully. There is nothing that the user can do at the access server to solve this kind of problem, other than to select an alternate load protocol and/or alternate load host if such is available.
Directed TFTP Problems Improperly Configured TFTP Server If your TFTP server host operating system uses case-sensitive file names, be sure that the filenames of the access server load images match the name the access server requests via TFTP. Note that the access server will typically request a file by name only, with no path or file extension information.
Directed TFTP Problems Directed TFTP Error and Status Messages Local -903- [DTFTP] Loading from host nnn.nnn.nnn.nnn [ETHERNET] Explanation: Indicates that a particular host is now loading from DTFTP. The BOOTP form of this message remains the same as before, for example: Local -903- [IP] Loading from host nnn.nnn.nnn.nnn [ETHERNET] Action: None. Local -912- [IP] Load failure, timeout. Explanation: The access server did not receive a completed image load within the allotted timeout period.
Directed TFTP Problems Local -962- [IP] TFTP Error message received, code: 01 File "FOO" not found. Explanation: The access server is attempting to load image FOO from a TFTP server. The file was not found at the specified TFTP server. The TFTP server address is obtained either from a BOOTP server response message, or from the Directed TFTP server configuration.
Chapter 18 Messages 000 – 099 Overview Introduction This chapter provides information on messages 000 – 099. Messages Local -008- Ping session currently active Explanation: User tried to execute a TEST INTERNET or PING command while another TEST INTERNET or PING command was active on the same port. Action: No action is required, try again later. Local -009- Session session_number to host_name established. Explanation: This message is displayed when a session was established to a host.
Messages 000 – 099 Action: Hang up the local modem by logging out of the access server. If necessary, prepare the local modem to receive the incoming callback from the access server. Local -020- Logged out port port_number on server server_name. Explanation: This message is displayed on the local terminal when the port is logged out. Action: No action is required. Local -040- Software initialization complete Explanation: This informational message indicates that the network access server is ready to use.
Chapter 19 Messages 200 – 299 Overview Introduction This chapter provides information on messages 200 – 299. Messages Local -201- Connection to service-name not established No response within timeout period Explanation: The connection request failed or the existing connection was terminated because the retransmit limit on the circuit has been reached. When the retransmit limit is reached, the circuit between the access server and the service node is terminated.
Messages 200 – 299 Local -203- Connection to service-name not established Service node retransmission limit exceeded Explanation: The connection request failed or the existing connection was terminated because the retransmit limit on the circuit has been reached. When the retransmit limit is reached, the circuit between the access server and the service node is terminated. Action: Verify the LAT service configuration (Chapter 2). Local-204- Autoconnect retry limit exceeded.
Messages 200 – 299 Explanation: The access server is receiving messages that violate the LAT protocol. Step Action 1 Try to reconnect to the service. 2 If the connection fails, reinitialize the access server to downline load the software. 3 Verify that the access server is running the latest software. 4 Try to reconnect to the service. 5 If the error messages reappear, you might have a software problem.
Messages 200 – 299 Explanation: The access server is receiving messages that violate the LAT protocol. Step Action 1 Try to reconnect to the service. 2 If the connection fails, reinitialize the access server to downline load the software. 3 Verify that the access server is running the latest software. 4 Try to reconnect to the service. 5 If the error messages reappear, you might have a software problem.
Messages 200 – 299 Explanation: The connection request failed or the existing connection was terminated because the service is not available. Action: Verify the LAT service configuration (Chapter 2). Local -220- Connection to service-name not established Server user disconnect request Explanation: The connection request failed or the existing connection was terminated because the access server disconnected the session. Action: Try to reconnect to the service.
Messages 200 – 299 Local -223- Connection to service-name not established Node user disconnect Explanation: The connection request failed or the existing connection was terminated because the remote node intentionally aborted the connection. This message might occur as a result of a user-written application running on the host. Action: Contact the remote node’s system manager.
Messages 200 – 299 Local -227- Connection to service-name not established Time limit expired Explanation: The connection request failed or the existing connection was terminated because the retransmit limit on the circuit has been reached. When the retransmit limit is reached, the circuit between the access server and the service node is terminated. Action: Verify the LAT service configuration (Chapter 2).
Messages 200 – 299 Explanation: The connection request failed or the existing connection was terminated because the requested service is not offered on your access server. Action: Use the SHOW SERVICES command to verify services offered on your access server. For more information on LAT service connection problems, refer to Chapter 2.
Messages 200 – 299 Local -238- Connection to service-name not established Corrupted solicit request Explanation: The access server is receiving messages that violate the LAT protocol. Step Action 1 Try to reconnect to the service. 2 If the connection fails, reinitialize the access server to downline load the software. 3 Verify that the access server is running the latest software. 4 Try to reconnect to the service. 5 If the error messages reappear, you might have a software problem.
Chapter 20 Messages 300 – 399 Overview Introduction This chapter provides information on messages 300 – 399. Messages Local -301- Telnet option negotiation in progress Explanation: The option requested in the current command is being negotiated; therefore, the command was not accepted. Action: No user action is required. Local -302- Telnet session disconnected Explanation: The Telnet connection has received a remote request to close the connection. Action: Verify access to the remote Internet host.
Messages 300 – 399 Local -303- Insufficient resources to complete Telnet connection Explanation: The access server could not complete the Telnet connection due to memory problems. Step Action 1 If every port on your access server is intended only for Telnet use, enter the following command: Local> CHANGE SERVER NODE LIMIT 1 2 This command will prevent the access server memory from being filled with LAT service node information. 3 Verify access server memory usage.
Messages 300 – 399 Local -307- Invalid operation on a Telnet server session Explanation: A command that is valid for a Telnet client connection was entered on a Telnet server connection. Action: For more information on valid commands, refer to the Network Access Software Commands Reference Guide. Local -308- Invalid operation on a Telnet client session Explanation: A command that is valid for a Telnet server connection was entered on a Telnet client connection.
Messages 300 – 399 Verify that the keyboard character is mapped to a Telnet function. For more information on mapping keys to Telnet client and Telnet server functions, refer to the Network Access Software Management Guide. Local -311- Telnet option not supported by peer Explanation: This command requires that an option be supported by the peer (remote host). Action: Verify operations supported by peer.
Messages 300 – 399 Local -323- Telnet listener failed to get a socket Explanation: The access server was unable to enable the Telnet listener due to memory problems. Step Action 1 If every port on your access server is only intended for Telnet use, enter the following command: Local> CHANGE SERVER NODE LIMIT 1 2 This command prevents the access server memory from being filled with LAT service node information. 3 Verify access server memory usage.
Messages 300 – 399 Local -326- Must first enable ports on this listener Explanation: A listener cannot be enabled because it has no physical ports associated with it. Action: Enter the following command on the access server that offers the Telnet listener. Substitute the number of the Telnet listener for 2014: Local> SHOW TELNET LISTENER 2014 Listener TCP-port: Identification: Ports: Connections: IP Address 2014 Listener Type: TELNET "Telnet Printer" 4 Enabled 0.0.0.
Messages 300 – 399 Local -333- Invalid terminal type specified Explanation: The terminal type you specified is invalid. Action: Enter a valid terminal type: ANSI, UNKNOWN, or VTnnn where nnn is a number between 10 and 999. For more information, refer to the Network Access Software Management Guide. Local -345- Listener 23 cannot be type RAW TCP Explanation: Listener 23 cannot be used as a RAW TCP connection. Action: Use another TCP port.
Messages 300 – 399 Local -351- Invalid subnet mask Explanation: The subnetwork address specified is not valid. Action: Enter a valid subnetwork mask. For more information on specifying TCP/IP network characteristics, refer to the Network Access Software Management Guide. Local -352- Invalid gateway address Explanation: The gateway address specified is not valid. Action: Enter a valid gateway address.
Messages 300 – 399 Local -357- ARP entry limit reached Explanation: The access server limit for ARP entries has been reached. Action: Remove an ARP entry to add another. For more information on specifying TCP/IP network characteristics, refer to the Network Access Software Management Guide. Local -358- Server Internet address already set Explanation: You set an Internet address and then tried to set a subnet mask.
Messages 300 – 399 Local -361- Error deleting gateway entry, entry not known Explanation: You attempted to delete (CLEAR or PURGE) a gateway that is not in the access server database. Action: Use the SHOW INTERNET GATEWAY command to display existing gateways. For more information on managing your access server as part of the TCP/IP network, refer to the Network Access Software Management Guide.
Messages 300 – 399 Local -366- Gateway entry checksum error Explanation: When the access server initialized or rebooted, it detected a gateway entry checksum error. This means that at least one of the gateway entries in the access server’s permanent database has been corrupted. Action: Enter the gateway entries again. If this action fails to correct the problem, the access server memory that stores the server characteristics is faulty. Refer to Chapter 29 for service information.
Messages 300 – 399 Local -372- Connection reset by peer Explanation: The remote host disconnected the access server session. Step Action 1 Verify the Internet counters. Enter the following command on your access server: Local> SHOW INTERNET COUNTERS Verify the TCP Segments - Data Retransmitted counter. This counter reflects the number of segments that contained retransmitted data.
Messages 300 – 399 Local -374- Connection timed out Explanation: The access server could not make the requested connection in the allotted time. Action: Try again later. Local -375- Connection refused Explanation: The access server user tried to connect to a Telnet listener, but the connection was refused. Step Action 1 On the access server that offers the Telnet listener, enter the following command.
Messages 300 – 399 Step Action 3 Verify the status of the access server port (in this case, port 4). Enter the following command: Local> SHOW SESSIONS PORT 4 If there are any invalid remote sessions on the port, enter the following command. Substitute the session number for 2: Local> DISCONNECT SESSION 2 4 Verify the Output XOFFed characteristic on the access server port. Enter the following command.
Messages 300 – 399 Local -377- No route to host Explanation: The Internet network interface has not been initialized because the access server Internet address has not been set or the Internet address cannot be reached by way of the known gateways. Action: Set the Internet address. See the section Verify Internet Address or Verify Communication to Remote Internet Host (Chapter 3).
Chapter 21 Messages 400 – 499 Overview Introduction This chapter provides information on messages 400 – 499. Messages Local -400- Insufficient resources to perform operation Explanation: The access server could not complete the operation due to memory problems.
Messages 400 – 499 Step Action 1 If every port on your access server is only intended for Telnet use, enter the following command: Local> CHANGE SERVER NODE LIMIT 1 This prevents the access server memory from being filled with service node information. 2 Verify the number of Internet hosts defined locally in the access server’s operational database. Enter the following command: Local> SHOW INTERNET HOST LOCAL If a lot of Internet hosts are defined locally, this might cause memory problems.
Messages 400 – 499 Local -411- PING successful: host reachable Explanation: A PING or TEST TELNET command was successful in reaching the specified host. Action: No action is required. Local -413- Insufficient resources: PING disallowed Explanation: The PING command cannot be executed due to insufficient resources. Local -414- PING timed out Explanation: The 30-second timer expired when the access server did not receive a reply from the target host. Action: Retry the PING command.
Messages 400 – 499 Local -426- Host name lookup failure Explanation: The access server cannot find the host name in its database. This error message is generated for one of the following reasons: Retry Limit reached, Time Limit expired, or no name server stored in the local cache. DNS cannot send out a query. Action: Verify Domain Name System (DNS) parameters. See the section Verify Domain Name System (DNS) Parameters (Chapter 3).
Messages 400 – 499 Local -428- No buffer available to resolve name or Local -429- Add to database failure Explanation: The access server could not complete the operation due to memory problems. Step Action 1 Try to reconnect to the Telnet resource. 2 If every port on your access server is only intended for Telnet use, enter the following command: Local> CHANGE SERVER NODE LIMIT 1 This prevents the access server memory from being filled with service node information.
Messages 400 – 499 Local -431- Illegal Internet address Explanation: You specified an illegal Internet address. Action: Verify the correct Internet address. See the section Verify Internet Address (Chapter 3). Local -432- Request in process Explanation: The access server is processing your request. Action: Wait for completion. Local -433- Maximum queries exceeded Explanation: The limit for concurrent user requests for resolving DNS name queries has been reached. Action: Try again later.
Messages 400 – 499 Local -438- DNS entry limit exceeded Explanation: You attempted to enter (using the SET, DEFINE, or CHANGE command) a DNS-related entry that exceeded the database storage limit for that entry class. Action: Delete or clear some of the entries. For information on managing your access server. See the section Telnet Resource Connection Problems (Chapter 3).
Messages 400 – 499 Local -454-Authentication failed, timed out Explanation: The system timed out before receiving a response from the Kerberos security server. Action: Reenter the correct login name and password. If the problem persists, verify that the Kerberos characteristics are correct and that the security servers for the realm in question can be reached over the network. The security servers for the realm must have correct Internet addresses or domain names.
Messages 400 – 499 Local -459-Duplicate security server host name Explanation: The security server host name entered is already in use. Action: Reenter the correct host name or select another host name. If the problem persists, refer to the Network Access Software Management Guide. Local -460-Duplicate domain name Explanation: The security server domain name entered is already in use. Action: Reenter the correct domain name or select another domain name.
Messages 400 – 499 Local -466-Security parameter out of range Explanation: The numeric value of the parameter is not allowed. Action: Reenter the value within the legal range. To verify the legal range of values, refer to the Network Access Software Commands Reference Guide. Local -467-Authentication failed, protocol error: error-code Explanation: There is a network or access server internal problem.
Messages 400 – 499 8008 - No SecurID server found A701 - Kerberos password service cannot fetch local realm A702 - Kerberos password service unable to fetch credentials A703 - Kerberos password service bad key supplied A704 - Kerberos password service cannot encrypt data A705 - Kerberos password service cannot encode/decode authentication info A706 - Kerberos password service principal attempting change is in wrong realm A707 - Kerberos password service packet is too large A708 - Kerberos password service
Messages 400 – 499 Local -469-Security server password has been changed Explanation: This is a system status message. Action: No user action is required. Local -470-Security server password remains unchanged Explanation: This system status message confirms that the password change transaction was not completed. Action: If you do not want to change the password, then no user action is required. If you want to change the Kerberos password, use either the KPASSWD or the KERBEROS PASSWORD command.
Messages 400 – 499 Action: Check both the Internet counters for errors and the operation of the security server host. For more information on security server host connectivity, refer to the Network Access Software Management Guide. Local -480-Security server host rejected new password as insecure Explanation: The new password chosen was deemed unacceptable to the security policy enforcement mechanism of the Kerberos security server host.
Messages 400 – 499 Local -487-User Account account-name does not exist Explanation: A user account with the specified name was not found in the database. Action: Enter a valid user account name, or contact the system administrator. Local -488-Insufficient resources to complete security operation Explanation: The access server could not complete the operation due to memory problems.
Messages 400 – 499 Explanation: The dial service name string is too long. Action: Use a shorter string. Local -492-Prompt too long Explanation: The security password prompt string is too long. Action: Use a shorter string. Local -495-Final warning nnn minutes left to forced logout Explanation: The allowed connect time, based on your authorization data, will expire in nnn minutes. Plan your work accordingly. Action: No action required.
Chapter 22 Messages 500 – 599 Overview Introduction This chapter provides information on messages 500 – 599. Messages Local -520- Could not acquire AppleTalk address for server, AppleTalk disabled Explanation: An unsuccessful attempt was made to acquire an AppleTalk address for the access server. The access server cannot run AppleTalk without an address. Action: Verify that AppleTalk is enabled. See the section Verify AppleTalk Is Enabled (Chapter 5).
Messages 500 – 599 Explanation: The access server could not create a cache entry to cache AppleTalk addresses for potential attached host connections. Attempted connections may fail. Action: Verify cache size is correct. See the section Verify Cache Size Is Correct (Chapter 5). Local -524- Attempt to acquire an AppleTalk address for cache failed Explanation: An unsuccessful attempt was made to acquire an AppleTalk address cache for potential attached host connections. Attempted connections may fail.
Messages 500 – 599 Local -550- SLIP not enabled on that port Explanation: The SLIP characteristic has not been enabled on the access server port. Action: Enable SLIP on the access server port. Enter the following command. Substitute the number of the port for 1: Local> CHANGE PORT 1 SLIP ENABLED For more information on configuring and managing SLIP ports, refer to the Network Access Software Management Guide.
Messages 500 – 599 Local> CHANGE PORT 1 MULTISESSIONS DISABLED For more information on configuring and managing SLIP ports, refer to the Network Access Software Management Guide. Local -558- Port already has SLIP HOST ADDRESS Explanation: The access server port already has a SLIP host address assigned. Action: Clear the SLIP host address on the access server port. Enter the following commands.
Messages 500 – 599 To disconnect the SLIP session, enter the following command. Substitute the session number for 2. Local> DISCONNECT SESSION 2 For more information on configuring and managing SLIP ports, refer to the Network Access Software Management Guide. Local -561- Starting SLIP or PPP datalink session Explanation: This message is displayed to the local terminal when the CONNECT "datalink" command is entered. Action: No action is required.
Messages 500 – 599 Local -569- Host address may be applied to one port only Explanation: Host addresses may not be applied to multiple ports. The SET/DEFINE/CHANGE PORT IPCP HOST ADDRESS may not contain a port_list as a parameter. Action: Re-enter the command specifying a single port. Local -570- Port already has IPCP HOST ADDRESS Explanation: Port already has IPCP HOST ADDRESS. Action: If you wish to modify the port’s IPCP HOST address, DEFINE the port’s IPCP HOST address then logout the port.
Chapter 23 Messages 600 – 699 Overview Introduction This chapter provides information on messages 600 – 699. Messages Local -600- Mandatory callback enabled, port will be logged out Explanation: The security or port attributes dictate that the user be called back to gain access to the LAN. Action: No action required.
Messages 600 – 699 Local -601- Internal memory error in port parameters Access server defaults in effect Explanation: Parameters in the access server port’s permanent database are corrupt and factory-set defaults were used during port login. Step Action 1 Use the CHANGE PORT command to reset the port characteristics to values of your choice. 2 If the error message appears again, reset the port characteristics using the software reset switch on the access server. 3 23-2 a.
Messages 600 – 699 Local -602- Internal memory error in server parameters Access server defaults in effect Explanation: Parameters in the access server permanent database are corrupt and factoryset defaults were used during port login. Action: Reset the server characteristic values. Step Action 1 Use the CHANGE SERVER command to reset the server characteristics to values of your choice.
Messages 600 – 699 Local -612- Flash RAM write protected Explanation: For network access servers with user-installable Flash RAM cards, this message indicates that the card installed has its write-protect switch in the protected position. Action: Set the switch to the write-enabled position. Local -613- Flash RAM erase failure Explanation: The Flash RAM failed verification of one or more erase cycles. Action: Retry the update. If it fails again, replace the defective Flash RAM card.
Messages 600 – 699 Local -616- Load image too large for Flash RAM free space Explanation: The network access server load image obtained over the network is too large to fit in the Flash RAM. Action: Make sure the image is the correct one for the hardware platform and that if a compressed version of the load image is available, you have specified it. Refer to the Network Access Software Release Notes for information regarding compressed images.
Messages 600 – 699 Local -654- Insufficient space: total unused community characters left is n Explanation: The community name you specified causes the total number of characters for all defined community names to exceed 80 characters. The total number of characters used to store a community name is broken down as follows: Overhead Community Name Internet Address (if defined) 2 + (Number of Characters) + 4 Action: • Remove any unused community names. Enter the following commands.
Messages 600 – 699 Local -657- Permanent database inaccessible at this moment Explanation: You attempted to use the DEFINE or CHANGE command with an SNMP characteristic, but the permanent database could not be accessed due to conflicting access requests. Action: Try again later. Local -658- No resources available at this moment Explanation: The access server could not complete the SNMP operation due to inadequate memory availability. Action: Verify the access server memory usage.
Messages 600 – 699 Local -664- Community name truncated Explanation: The community name you entered has been truncated to the 32-character limit. Action: Use the SHOW/LIST SNMP command to view the truncated name or reenter the name with fewer characters. NOTE 23-8 The total number of characters for all defined community names cannot exceed 80 characters.
Chapter 24 Messages 700 – 799 Overview Introduction This chapter provides information on messages 700 – 799. Messages Local -701- Command syntax error or Local -702- Keyword “keyword” not known or ambiguous Explanation: You entered a command or keyword incorrectly. Action: For the appropriate command syntax, refer to the Network Access Software Commands Reference Guide.
Messages 700 – 799 Local -705- Entry entry-id not in queue Explanation: You specified a nonexistent queue entry in a REMOVE QUEUE or SHOW/MONITOR QUEUE command. Action: Use the SHOW QUEUE ALL command to check the queue entries. For more information on configuring and managing the LAT connection queue, refer to the Network Access Software Management Guide. Local -706- Secure operation requires privilege Explanation: You entered a command that is not available from a nonprivileged or secure port.
Messages 700 – 799 • The access server node limit has been reached. • Group codes are not enabled. • The access server has used up its memory. Step Action 1 If you are trying to connect to a Telnet resource, set the Default Protocol characteristic on your port to TELNET or ANY.
Messages 700 – 799 Local -714- Preferred service/host has not been defined Explanation: You entered the CONNECT command without a service name and the PREFERRED SERVICE characteristic is set to None. Action: Use the SET/DEFINE/CHANGE PORT PREFERRED command to configure a preferred service or reenter the CONNECT command with a service name.
Messages 700 – 799 Local -716- Access to service service-name denied Explanation: The problem might be caused by one of the following: • The port and service nodes do not have a LAT group code in common or the access server has the correct authorized groups, but not current groups. • The access server node limit has been reached. • The access server has used up its memory. Step Action 1 Verify the LAT group codes. See the section Verify LAT Group Codes (Chapter 2).
Messages 700 – 799 Local -720- Protocol does not support operation Explanation: You entered a SET SESSION TELNET or SET SESSION TN3270 command when the current session does not use the referenced protocol. Action: Resume the session that uses the referenced protocol, returning to the Local> prompt. Reenter the SET SESSION command. Local -721- No dedicated service on port n Explanation: You entered the CONNECT PORT n or a DISCONNECT PORT n command to a port that does not have a dedicated service defined.
Messages 700 – 799 Local -725- Access to node node-name denied Explanation: The problem might be caused by one of the following: • The port and service nodes do not have a LAT group code in common or the access server has the correct authorized groups, but not current groups. • The access server node limit has been reached. • The access server has used up its memory. Step Action 1 Verify the LAT group codes. See the section Verify LAT Group Codes (Chapter 2).
Messages 700 – 799 Explanation: The problem might be caused by one of the following: • You did not specify a port number (you cannot loop back to your own port). • You specified a port that is under session management control. • The two ports are operating at different input and output speeds. Step Action 1 Ensure that you have specified a port number other than your own. 2 Disable session management on the port or use another port.
Messages 700 – 799 Local -737- Flash RAM is not installed or not supported Explanation: You entered a flash RAM command on a system that either does not support flash RAM or flash RAM is not installed. If flash RAM is installed, it may be malfunctioning. Action: If the flash RAM is user installable, ensure that it is installed properly. If you do not have flash RAM, you cannot use the flash RAM command.
Messages 700 – 799 Local -746- Monitor currently in use Explanation: You entered the MONITOR command when another MONITOR command is still in effect. Action: You must halt the first monitor display before the access server can begin a second one. Local -747- No entries removed or Local -748- No entries in local system queue Explanation: You specified a nonexistent queue entry in a REMOVE QUEUE or SHOW/MONITOR QUEUE command. Action: Use the SHOW QUEUE ALL command to check the queue entries.
Messages 700 – 799 Local -756- Specified server name already in use Explanation: You entered the SET/DEFINE/CHANGE SERVER NAME command specifying a name that already exists in the database. Action: Reenter the command and specify another name. Local -761- Unsupported by port hardware Explanation: You tried to enable a function that is not supported on your device. Action: For information on supported features, refer to your access server hardware documentation.
Messages 700 – 799 Step Action 1 Verify that the terminal is configured correctly for session management. 2 Ensure the terminal is configured correctly. Then, initiate another session. 3 If the session management software is not compatible between the terminal and the access server, you cannot use session management. For more information on configuring a session management (TD/ SMP) terminal, refer to the Network Access Software Management Guide.
Messages 700 – 799 Action: For the correct command syntax, refer to the Network Access Software Commands Reference Guide. Local -780- Parameter inappropriate for the console port Explanation: You tried to set a characteristic on the console port that is not applicable (for example, SET PORT 0 AUTOBAUD ENABLED). Action: Use the SET/DEFINE/CHANGE SERVER CONSOLE NONE command to disable the console port.
Messages 700 – 799 Action: Wait and try again. Local -794- Type only one character or control sequence Explanation: You tried to specify more than one character as a switch character. Action: Reenter the command using only one character or control sequence. Local -795- Logged in ports not changed Explanation: You attempted to use the SET or CHANGE command to modify a port characteristic that cannot be changed while the target port is logged in.
Chapter 25 Messages 800 – 899 Overview Introduction This chapter provides information on messages 800 – 899. Messages Local -800- TN3270: operator terminated session Explanation: You entered the EXIT TN3270 command. Action: No user action is required. Local -801- TN3270: Command ‘xxx’ from host not supported or Local -802- TN3270: Order ‘xxx’ from host not supported Explanation: The access server received an unsupported TN3270 command/order from the host/peer. Action: Restart the session.
Messages 800 – 899 Local -803- TN3270: initialization failed setting port Explanation: The TN3270 session failed to be initialized due to a temporary resource condition at the port. Action: Restart the session. If this action fails to correct the problem, refer to Chapter 29 for service information. Local -804- TN3270: initialization failed; insufficient memory Explanation: A TN3270 session could not be started due to insufficient memory. Action: Enter the SHOW SERVER STATUS command.
Messages 800 – 899 Local -809- TN3270: invalid operation Explanation: A command was entered that is not allowed while a TN3270 session is active. Action: No user action is required. Local -810- TN3270: invalid function Explanation: The TN3270 function name in the SET/DEFINE/CHANGE PORT TN3270 KEYMAP command is not a valid function name. Action: For a list of TN3270 functions, refer to the Network Access Software Commands Reference Guide.
Messages 800 – 899 Local -815- TN3270: Your keymap assignment conflicts with existing keymap function Explanation: The keymap assignment you tried to make in a SET PORT TN3270 KEYMAP command is ambiguous with an existing keymap. The keymap sequence you entered is either a subset of another or the other keymap is a subset of yours. In either case, the keymap assignment is not allowed.
Messages 800 – 899 Local -821- TN3270: keymap does not exist Explanation: You referred to a keymap type name that does not exist. Action: Check the available keymap type names using the SHOW TN3270 TERMINAL command. Local -822- TN3270: invalid name Explanation: You entered an invalid terminal or keymap name. This means the name is too long (maximum of 12 characters) or contains illegal characters. Action: Choose a name containing 12 or fewer legal characters.
Messages 800 – 899 Local -827- TN3270: Cannot CLEAR terminal while a port uses it Explanation: You tried to CLEAR a particular terminal type while one or more ports were using it. Action: Use the SHOW PORT TN3270 command to find the ports that use the particular terminal type. Then, use the SET PORT TN3270 TERMINAL command to reassign those ports with a new terminal type. Try the CLEAR command again.
Messages 800 – 899 Local -884- Command Group and Menu NVRAM entry limit exceeded Explanation: There is a finite amount of NVRAM allocated for storing command groups and this limit has been reached. Action: Purge unused command groups. Local -885- Command Group group_name not found Explanation: The Command Group names "group_name" doesn’t exist. Action: Check your spelling and that the command group does exist, SHOW/LIST COMMAND GROUP.
Chapter 26 Messages 900 – 999 Overview Introduction This chapter provides information on messages 900 – 999. These messages appear only on the console port and under the following circumstances: • When the access server is initialized. • When the access server crashes. Messages Local -901- Initializing DECserver ppppp address FW Vx.x-x HW x.x or Local -901- Initializing Access Server ppp address FW Vx.x-x HW x.x Explanation: In message 901, ppppp or ppp is the platform code of the access server device.
Messages 900 – 999 Local -903- [protocol] Loading from host address Explanation: This message indicates that the load host is downline loading the access server software. This message is displayed during the initialization process. Action: No user action is required. Local -904- Image load complete Explanation: The software has been successfully downline loaded. Action: No user action is required.
Messages 900 – 999 Local -912- [protocol] Load failure, timeout Explanation: A downline load sequence was interrupted because a load message was not received. The load sequence is restarted. Action: For information on software installation failure, refer to Chapter 1 . Local -913- Fatal Bugcheck, PC = n SP = n SR = n M = n C = n Explanation: The access server hardware detected an internal fatal error, called a fatal bugcheck error.
Messages 900 – 999 Local -914- [protocol] Dump failure, timeout • Explanation: The access server was unable to send an upline dump file to the load host. This failure can be caused by either incorrect information on the load host or a hardware error on the access server.. Step Action 1 If you are using the MOP protocol to downline load the software, do the following: a. Verify that the information in the NCP database is correct. At an OpenVMS load host, enter the following command.
Messages 900 – 999 Local -917- Load failure, invalid boot block CRC Explanation: Flash RAM contains a corrupted boot block. Action: No user action is required, the software will automatically reformat the Flash RAM Local -919- Load failure, invalid load image CRC Explanation: Flash RAM contains a corrupted load image. Action: Reset the Flash RAM using the INITIALIZE FROM ETHERNET UPDATE FLASH command. Local -922- Port hardware error on port n Explanation: There is a port hardware error.
Messages 900 – 999 Local -951- Server will retry operation in n seconds Explanation: The access server is unable to find the load host or the host system failed to complete the downline load to the access server. The access server will automatically try to downline load again. Step Action 1 If you are using the MOP protocol to downline load the software, do the following: 2 26-6 a. Verify the information on the load host.
Messages 900 – 999 Ask the system manager to perform the following command. Substitute the DECnet node name of the access server for server-node-name: At an OpenVMS load host, enter the following: NCP> LOOP CIRCUIT server-node-name The Network Control Program (NCP) shows the results of the loopback test at the DECnet node. Local -952- Enter ^P to repeat selftest Explanation: This message appears after an Ethernet loopback failure. Action: To restart the self-test, press Ctrl/P on the console terminal.
Messages 900 – 999 Ask the system manager to perform the following command. Substitute the DECnet node name of the access server for server-node-name: At an OpenVMS load host, enter the following: NCP> LOOP CIRCUIT server-node-name The Network Control Program (NCP) shows the results of the loopback test at the DECnet node. Local -954- [protocol] Attempting to locate dump host [datalink] Explanation: The access server has terminated abnormally.
Messages 900 – 999 Local -960- Available memory n Mbytes Explanation: In message 960, n is the number of megabytes of memory. This messages is generated approximately 10 seconds after powering up the access server or after executing the INITIALIZE command. Action: No user action is required. Local -961- [IP] ARP request failed Explanation: The access server transmits an Address Resolution Protocol (ARP) request when attempting to load or dump using the TFTP protocol.
Messages 900 – 999 Local -965- Dump failed Explanation: The access server has not been successful in performing a dump. It will try to perform a dump a number of times before generating this message. Action: Refer to message 914 for more information. Local -966- Transmission failure on NI Explanation: The transmission of a packet has failed on the network interface (NI) due to a physical layer problem. Action: Press Ctrl/P on the console terminal to perform a self-test.
Messages 900 – 999 Local -992- LOAD channel set to an IMB Explanation: Software load channel set to an IMB channel.
Chapter 27 Messages 1000 – 1099 Overview Introduction This chapter provides information on messages 1000 – 1099. These messages appear when you are using IPX or a dialer service. Messages Local -1000- Active IPXCP port connection; request denied Explanation: You attempted to use the SET command to change the IPX internal network number while an active serial line IPX connection existed. Action: You can use the SET command only when there are no active serial line IPX connections.
Messages 1000 – 1099 Local -1051- Port’s default protocol is not DIAL Explanation: A request to dial a phone number was made, but the current port’s default protocol is not DIAL. Action: Specify a dialer service name instead of simply a phone number, or define a preferred dialer service name and change the port’s default protocol to DIAL.
Chapter 28 Messages 1100 – 1208 Overview Introduction This chapter provides information on messages 1100 – 1208. Messages Local -1100- Authorization failure - login protocol not specified Explanation: The authorization information calls for a login session to be established, but the protocol (LAT or Telnet) was not specified. Action: Specify a login protocol. This can be done on the access server with the CHANGE PORT n DEFAULT PROTOCOL command or on a security server host.
Messages 1100 – 1208 Local -1102-Authorization failure - network address not specified Explanation: The authorization information calls for a framed session to be established, but the network address was not specified. Action: Specify a network address. This can be done on the access server with the CHANGE PROT n SLIP HOST ADDRESS n.n.n.n command or on a security server host. See the Network Access Software Management Guide for more information.
Messages 1100 – 1208 Local-1111- Authorization failure - host name > 16 char Explanation: The name of the host is too long. Action: Use a name no longer than 16 characters. Local-1112- Authorization failure - dest. port name > 16 char Explanation: The name of the destination port is too long. Action: Use a name no longer than 16 characters. Local-1113- Authorization failure - LAT service name > 16 char Explanation: The name of the LAT service is too long. Action: Use a name no longer than 16 characters.
Messages 1100 – 1208 Local-1116- Authorization failure - Rlogin host name too long Explanation: The name of the Rlogin host is too long. Action: Use a name no longer than 16 characters. Local -1117- Authorization failure - Rlogin port name too long Explanation: The tcp-port specification was greater than 16 characters. Action: Use a name no longer than 16 characters. Local -1200- Internal software error - no Rlogin connection Explanation: A memory error occurred.
Messages 1100 – 1208 Local -1204- Illegal Rlogin host specification Explanation: The Rlogin host name was more than 255 characters. Action: Specify a valid host name or address. If you did not specify one on the command line, or on the port settings for default or preferred service, then an internal software error has occurred. Log out the port, and try again. If the problem persists, reboot the access server, and contact your authorized service representative.
Chapter 29 Service Guidelines Overview Introduction This chapter provides guidelines to follow when you experience a problem with your access server. It also has instructions for returning your access server hardware and tells you what to return if you have a problem with your access server software. Contact your access server supplier for more information about the available hardware and software service options.
Service Guidelines • If possible, record the symptoms when the access server failed, the troubleshooting steps you took, and the results of those steps. • If you are reporting a software problem, use the privileged CRASH command to produce a dump file of the access server memory. The dump file is used to find internal logic errors in the software. For details on how to send dump files to your supplier, see the section Formatting and Sending the Dump File (page 29-2.).
Digital Networks TM PG-DNAS0-00
