For troubleshooting purposes, you can simulate a POP client and enter the XTND commands listed in Table A-2 to obtain information.

Table A-2 POP Extension (XTND) Commands

Command	Action
XTND CLIENT	Logs POP client information (if the client supplies it). Helpful for troubleshooting if you use POP with a variety of POP clients that identify themselves.
XTND LOGLEVEL	Dynamically adjusts POP logging level. Supported levels are INFORMATIONAL (default), ERROR, THREAD, and DEBUG.
XTND STATS	Displays POP statistics in the following format: +OK Statistics follow Version Number : TCPIP X5.0, OpenVMS V7.1 Alpha Logging Level : DEBUG Current Time : 1999-04-06 06:13:46 Start Time : 1999-04-04 06:42:17 CPU Seconds : 7.89 (0 mins, 7 secs) Current Threads : 1 Total Threads : 6 Max Threads : 1 Too Many Threads : 0 Normal Disconnects : 5 Abnormal Disconnects : 0 Client Timeouts : 0 Blocked Socket Count : 0 Retrieved Messages : 4 Retrieved Octets : 1102 Average Octets : 275 Minimum Octets : 222 Maximum Octets : 319 Auth Failures : 1 Current Users : 0. smith
XTND SHUTDOWN	Performs an orderly shutdown of POP. Waits for current client connections to disconnect. Recommended over the DCL command STOP.

To simulate a POP client and obtain information:

1. Enter the TELNET command to the POP port (110).
2. Using the USER and PASS command, enter your user name and password.
3. Enter an XTND command.

For example:

$ TELNET UCXSYS 110 %TELNET-I-TRYING, Trying ... 16.20.208.53 %TELNET-I-SESSION, Session 01, host ucxsys, port 110 +OK POP server TCPIP V5.0, OpenVMS V7.1 Alpha at ucxsys.acme.com, up since 1999-04-04 06:42:17 <24A00E61._6_APR_1999_06_02_31_15@ucxsys.acme.com> USER username +OK Password required for "username" PASS password +OK Username/password combination ok XTND LOGLEVEL DEBUG +OK logging level changed to debug QUIT +OK TCPIP POP server at ucxsys.acme.com signing off.

A.14 TELNET

To improve TELNET performance, try modifying some of the internet parameters. These changes might also decrease the use of system resources.

A.14.1 TELNET Characteristics That Affect Performance

The settings for the TELNET systemwide characteristics might affect TCP/IP Services and TELNET performance. To display the TELNET systemwide characteristics, enter:

TCPIP> SHOW SERVICE TELNET /FULL

The command generates a display similar to the following:

Service: TELNET State: Enabled Port: 23 Protocol: TCP Address: 0.0.0.0 Inactivity: 1 User_name: Process: not defined Limit:30 Active: 1 Peak: 4 File: not defined Flags: Listen Priv Rtty Socket Opts: Keepalive Receive: 3000 Send: 3000 Log Opts: Actv Dactv Conn Error Logi Logo Mdfy Rjct Addr File: not defined Security Reject msg: not defined Accept host: 0.0.0.0 Accept netw: 0.0.0.0

A.14.2 Requests That Cannot Be Satisfied

The TELNET Server sends the following error message for a TELNET login request that cannot be satisfied: SS$_EXQUOTA. This error is due to insufficient local resources, such as:

• Too many sessions
  Check to see if the maximum number of concurrent sessions has been exceeded. Enter:

  TCPIP> SHOW SERVICE TELNET

  
  If this number has been exceeded, the display shows: PEAK=limit. To increase the number of allowed sessions, enter:

  TCPIP> SET SERVICE TELNET /LIMIT=n

• Insufficient OpenVMS nonpaged pool
  Check to see if the OpenVMS nonpaged pool is insufficient for servicing a new TELNET connection. If so, monitor the server.
  To improve any of the parameters, redefine the logical names.
• Excessive OpenVMS login sessions
  Check to see if the limit for maximum OpenVMS sessions has been exceeded. If the current value is not appropriate, redefine it.

Verify that the CHANNELCNT parameter (in SYSGEN) is larger than the number of simultaneous TELNET and RLOGIN sessions that you plan to support.

This appendix describes how to configure the Gateway Routing Daemon (GATED).

B.1 The GATED Configuration File

You must configure the GATED protocols before starting GATED routing by editing the configuration file TCPIP$GATED.CONF, located in SYS$SYSDEVICE:[TCPIP$GATED]. A template file TCPIP$GATED.TEMPLATE is also available in this directory.

The file TCPIP$GATED.CONF contains statements that select routing protocols, manage routing information, manage independent system routing and control tracing options.

After editing the configuration, enter the command TCPIP START ROUTING/GATED to start the GATED process. If the configuration file is not formatted correctly, GATED will not be able to parse the file and GATED will terminate.

If you make changes to the GATED configuration file after the GATED process is already running, you must stop GATED by entering the command TCPIP STOP ROUTING/GATED then restart the GATED process to make the changes take affect.

See DIGITAL TCP/IP Services for OpenVMS Management Command Reference for detailed descriptions of the SET GATED and START ROUTING/GATED commands.

B.2 Configuration File Statement Syntax

Parameters shown in brackets ([]) show optional keywords and parameters. The vertical bar (|) indicates a choice of optional parameters. Parentheses (()) group keywords and parameters, when necessary. For example:

[backbone | (area area)]

In this example, the brackets indicate that either parameter is optional. The keywords are backbone and area. The vertical bar indicates that either backbone or area area can be specified. Because area is in the variable definition style, it is a parameter that needs to be provided.

The following comment styles are valid in a GATED configuration file. (Comments may appear anywhere in the file.)

• A number sign (#)
• The C-style comments that start with /* and end with */

The configuration file consists of statements grouped in the following order:

• Options statements
• Interface statements
• Definition statements
• Protocol statements
• Static statements
• Control statements
• Aggregate statements

The following statements do not fit in the above categories: %directive statements and %trace statements. These statements provide instructions to the parser and control tracing from the configuration file. They do not relate to the configuration of any protocol and may occur anywhere in the configuration file.

B.4 Configuration Statements

Table B-1 GATED Configuration Statements

Command	Type	Description
%directory	directive	Sets the directory for include files.
%include	directive	Includes a file into TCPIP$GATED.CONF.
traceoptions	trace	Specifies which events are traced.
options	definition	Defines gated options.
interfaces	definition	Defines gated interfaces.
autonomoussystem	definition	Defines the AS number.
routerid	definition	Defines the originating router (BGP, OSPF).
martians	definition	Defines invalid destination addresses.
rip	protocol	Enables the RIP protocol.
hello	protocol	Enables the HELLO protocol.
kernel	protocol	Configures kernel interface options.
ospf	protocol	Enables the OSPF protocol.
egp	protocol	Enables the EGP protocol.
bgp	protocol	Enables the BGP protocol.
redirect	protocol	Configures the processing of ICMP redirects.
icmp	protocol	Configures the processing of general ICMP packets.
snmp	protocol	Enables reporting to SNMP.
static	static	Defines static routes.
import	control	Defines which routes to import.
export	control	Defines which routes to export.
aggregate	control	Defines which routes to aggregate.
generate	control	Defines which routes to generate.

B.5 Creating the GATED Configuration File

To create a configuration file for your local host, edit a copy of the sample file TCPIP$GATED.TEMPLATE (located in SYS$SYSDEVICE:[TCPIP$GATED]) then save the file to SYS$SYSDEVICE:TCPIP$GATED.CONF.

The following sample shows a configuration file.

#--------------------------------------------------------------------- # # Copyright (c) Digital Equipment Corporation, 1998 # # TCPIP$GATED.CONF - Sample gateway routing daemon (GATED) # configuration file, preconfigured for RIP v1. # # This file contains information that is read by the GATED daemon at # initialization time. This file contains statements that # # o Control tracing options # o Select routing protocols # o Manage routing information # o Manage idependent system routing # # See the DIGITAL TCP/IP Services for OpenVMS Management guide for # instructions on using this file. # #____________________________________________________________________ interfaces { interface all passive ; }; # # Protocols: # rip on { broadcast; interface all ripin ripout version 1; }; # redirect on; routerdiscovery server off; hello off; ospf off; egp off; bgp off; snmp off; # # Static routes: # #static { # 10.1.2.0 mask 255.255.255.0 gateway 10.1.1.1; # default gateway 10.1.2.3; # }; # # Policy: # #export proto rip { # proto static { all metric 1; }; # proto direct { all; }; # proto rip { all; }; # };

B.6 Defining Preferences and Routing

The configuration file can define routes from one protocol or peer to another, assigning each route a value called a preference.

The preference value determines the order of routes to the same destination in a single routing database. The active route is chosen by the lowest preference value. Some protocols implement a second preference (preference2), sometimes referred to as a tie breaker.

Preferences have the following characteristics:

• May appear in several different configuration statements in the configuration file. Be aware, however, that the last, or most specific value set for a route is the value GATED will use.
• May specify one network interface over another, one protocol over another, or one remote gateway over another.
• Cannot be used to control the selection of routes within an interior gateway protocol (IGP). That function is accomplished automatically by the protocol based on metric.
• May select routes from the same exterior gateway protocol (EGP) learned from different peers or autonomous systems.

The GATED daemon selects a route based on the following preference criteria:

• The route with the best (numerically smallest) preference is selected.
• If the two routes have the same preference, the route with the best (numerically smallest) preference2 (also known as a tie breaker) is selected.
• A route from an IGP is selected over a route from an EGP. The least preferred is a route "learned" indirectly by an IGP from an EGP.
• If autonomous system (AS) path information is available, it is used to help determine the most preferred route as follows:
  • A route with an AS path is selected over one without an AS path.
  • If the AS paths and origins are identical, the route with the lower metric is selected.
  • A route with an AS path origin of IGP is preferred over a route with an AS path origin of EGP. The least preferred is an AS path with an unknown origin.
  • A route with a shorter AS path is preferred.
  • If both routes are from the same protocol and AS, the one with the lowest metric is selected.
  • The route with the lowest numeric next-hop address is used.

A default preference is assigned to each source from which GATED receives routes. Preference values range from 0 to 255, with the lowest number indicating the most preferred route.

Table B-2 lists each type of route, the statement (or clause within statements) that sets preference for the route, and the default preference for each type of route.

Note that a statement that is narrow in scope has a higher precedence given to its preference value, but affects a smaller set of routes.

Table B-2 Default Preference Values

Preference	Defined by Statement	Default
Direct connected networks	interface	0
OSPF routes	ospf	10
Internally generated default	gendefault	20
Redirects	redirect	30
Routes learned through route socket	kernel	40
Static routes from config	static	60
ANS SPF (SLSP) routes	slsp	70
HELLO routes	hello	90
RIP routes	rip	100
Point-to-point interface		110
Routes to interfaces that are down	interfaces	120
Aggregate/generate routes	aggregate/generate	130
OSPF AS external routes	ospf	150
BGP routes	bgp	170
EGP	egp	200

B.6.2 Sample Preference Specifications

In the following example, the preference applicable to routes learned through RIP from gateway 138.66.12.1 is 75. The last preference applicable to routes learned through RIP from gateway 138.66.12.1 is defined in the accept statement. The preference applicable to other RIP routes is found in the rip statement. The preference set on the interface statement applies only to the route to that interface.

interfaces { interface 138.66.12.2 preference 10 ; } ; rip yes { preference 90 ; } ; import proto rip gateway 138.66.12.1 preference 75 ;

B.7 Tracing Options

You can specify tracing options at the following levels: file specifications, control options, and global and protocol specific tracing options. Unless overridden, tracing options from the next higher level are inherited by lower levels. For example, Border Gateway Protocol (BGP) peer tracing options are inherited from BGP group tracing options, which are inherited from global BGP tracing options, which are inherited from global GATED tracing options. At each level, tracing specifications override the inherited options.

The syntax for trace options statements is as follows:

traceoptions [trace_file [replace] [size size[k|m] files files]] [control_options] trace_options[except trace_options] ; traceoptions none ;

Table B-3 describes the valid trace options.

Table B-3 Trace Options

Option	Definition
trace_file	Specifies the file to receive tracing information. If this file name does not begin with a slash (/), the directory in which GATED was started is prepended to the name.
replace	Replaces an existing trace file. The default is to append to an existing file.
size size[k|m] files files	Limits the maximum size of the trace file to the specified size (minimum 10 kilobytes). When the trace file reaches the specified size, it is renamed to file.0, then file.1, file.2, up to the maximum number of files (minimum specification is 2).
control_options	Specifies options that control the appearance of tracing. The only valid value is nostamp, which specifies that a timestamp should not be prepended to all trace lines.
except trace_options	Enables a broad class of tracing and then disables more specific options.
none	Specifies that all tracing should be turned off for this protocol or peer.

B.7.1 Global Tracing Options

There are two types of global options: those with global significance (Table B-4) and those with protocol significance (Table B-5).

Table B-4 Global Significance Options

Option	Definition
parse	Traces the lexical analyzer and parser. Used mainly by GATED developers for debugging.
adv	Traces the allocation of and freeing of policy blocks. Used mainly by the GATED developers for debugging.
symbols	Traces symbols read from the kernel at startup. The principal way to specify this level of tracing is by the -t option on the command line, because the symbols are read from the kernel before parsing the configuration file.
iflist	Traces the reading of the kernel interface list. It is useful to specify this with the -t option on the command line, because the first interface scan is done before reading the configuration file.

Table B-5 Protocol Significance Options

Option	Description
all	Turns on all of the options flags.
general	A shorthand notation for specifying both normal and route.
state	Traces state machine transitions in the protocols.
normal	Traces normal protocol occurrences. Abnormal protocol occurrences are always traced.
policy	Traces the application of protocol and user-specified policy to routes being imported and exported.
task	Traces system interface and processing associated with this protocol or peer.
timer	Traces timer usage by this protocol or peer.
route	Traces routing table changes for routes installed by this protocol or peer.

When protocols inherit their tracing options from the global tracing options, tracing levels that do not make sense (such as parse, adv, and packet tracing options) are masked out.

Global tracing statements have an immediate effect, especially parsing options that affect the parsing of the configuration file. Tracing values inherited by protocols specified in the configuration file are initially inherited from the global options in effect as they are parsed, unless they are overridden by more specific options.

After the configuration file is read, tracing options that were not explicitly specified are inherited from the global options in effect at the end of the configuration file.