3Com | Release Notes

Multiprotocol Communications Server Release Notes Software-Version 6.2

Modified: 02/11/96

Product: CS/2500, CS/2600, CS/3000, CS/3100
Technology: Ethernet
Product Family: Terminal Servers
Product Line: CS/2x, CS/3x
SW Ver No. 6.2 FW Ver No. HW Ver No.

Multiprotocol Communications Server Release Notes Software-Version 6.2

Introduction

These release notes are included with the following 3Com® multiprotocol communications server software, version 6.2:

SW/2500-TO-3270 for CS/2500 or CS/2600

SW/3000-TO-3270 for CS/3000 or CS/3100

SW/2500-TLO-3270 for CS/2500 or CS/2600

SW/3000-TLO-3270 for CS/3000 or CS/3100

The first two products provide network connection services based on the Transmission Control Protocol/Internet Protocol (TCP/IP) and Open System Interconnection (OSI) protocol suites. The other two products also offer the local area transport (LAT) protocol. If your software does not include LAT, you can skip LAT-specific sections.

Model number references may include x to represent a set of products. For example, CS/2x00 means either CS/2500 or CS/2600.

These release notes provide information on the following topics:

New features

Software compatibility

Notes and cautions

Known problems

Limitations

Software packaging

Valid filenames

Installation, upgrade, and startup procedures

Changes and additions to the following manuals:

Multiprotocol Communications Server Operation Guide, May 1994

Multiprotocol Communications Server Reference Guide, May 1994

If you have questions about the software, the manuals, or these release notes, contact 3Com or your network supplier.

For information on the command syntax used in these release notes, see Before You Begin, Chapter 1, and Appendix D of the Multiprotocol Communications Server Reference Guide.

New Features in Version 6.2

This section describes new features in software version 6.2. For customers upgrading from version 6.0, the section following this one describes features that were added in version 6.1.

All-Zero IP Subnets

You can now assign 0 to the subnet field of an IP address.

File Management

You can centralize software change management by downloading boot and configuration files from or uploading them to a Trivial File Transfer Protocol (TFTP) server. You can format disks and list, copy, delete, or rename files on the communications servers local file system tasks over the user interface, Simple Network Management Protocol (SNMP), or Telnet.

New Protocols

The following standard protocols have been added.

Line Printer Daemon Protocol

Line Printer Daemon Protocol (LPDP) for sending files to printers is a standard protocol used in UNIX® environments. Software version 6.2 allows a user on a remote host to print a file on a printer attached to the communications servers serial port or parallel printer port using LPDP. PC users can also print a file on a local disk to an LPDP print-server.

Network Time Protocol

Network Time Protocol (NTP) is a nonproprietary way for devices on a network to synchronize their time-of-day clocks according to a designated source. The implementation of NTP in software version 6.2 enables the communications server to set its date and time over the network without a 3Com Remote Boot and Configuration Services (RBCS) server or a Network Control Server (NCS).

Syslogd

Syslogd is a daemon running on UNIX hosts that accepts system messages and forwards them to files, other hosts, or users. The implementation of syslogd in software version 6.2 allows you to log audit trail messages to generic UNIX hosts rather than requiring an RBCS server or an NCS.

Port Monitoring

Port monitoring is a debugging feature that allows network managers to view all data transmitted and received over any serial port on the communications server.

Telnet Options

The following enhancements have been made to Telnet sessions.

Echo Enhancement

You can now disable Telnet Echo.

Telnet Debug Option

The Telnet debug option allows you to view Telnet negotiation in progress, a convenient method for troubleshooting potential negotiation problems.

TN3270 Enhancements

The following enhancements have been made to TN3270 sessions.

ASCII Edit

You can now create and edit termcaps and keymaps using a host-based editor by creating a file on the host. You can also derive a termcap directly from a UNIX file (such as /etc/termcap).

File Transfer

You can transfer files between a local PC acting as a terminal and a remote host on a TN3270 session, using the Kermit protocol. The transfer is transparent, that is, the communications server does not process or interpret data during the transfer.

Print Screen Capability

The print screen feature enables a TN3270 user to print the current screen information to an ASCII printer attached to the communications server.

New Features in Version 6.1

For customers upgrading from software version 6.0, this section describes features that were added in version 6.1. The previous section describes new features in version 6.2.

For detailed descriptions of commands and parameters added in version 6.1, see the Multiprotocol Communications Server Operation Guide and Reference Guide.

PPP Protocol (IP Only)

Version 6.1 provides an implementation of the Point-to-Point Protocol (PPP), which allows direct access to the IP level of the LAN via the communications servers serial portsfor example, dial-up access. The capabilities of the PPP implementation parallel Serial Line Internet Protocol (SLIP) capabilities in earlier software versions. In particular, the communications server does not provide routing capability between multiple networks, but only single-host connections with no Routing Information Protocol (RIP)-generation.

The PPP Service configures the communications server for PPP operation. Some PPP parameters, such as addressing parameters and LineQueueLimit, are shared with the SLIP Service. The PPP command starts PPP on a serial port. The configuration parameters then determine how PPP option negotiation is carried out.

The communications server supports compression of Address/Control and Protocol fields, PAP authentication from the communications server to the client, Asynchronous Control Character Map (ACCM), and Van Jacobson (VJ) compression (up to 16 slots in each direction). It also supports negotiation for IP addresses. It does not support Challenge Handshake Authentication Protocol (CHAP) authentication or Link Quality Monitoring.

For PPP interoperability information, based on 3Com communications server testing experience, see PPP Interoperability on page-8 of these release notes.

CSLIP Protocol

SLIP connections can take advantage of VJ TCP/IP header compression by using the CSLIP command. The communications server allows a maximum of 16 compression slots. The CSLIP command should be used only when you know that the other end of the serial line also supports VJ compression. The communications server cannot select compression automatically.

FTP File Service

The software can use the File Transfer Protocol (FTP) to read and write its configuration files, including shared port configurations, macro files, and TN3270 termcap and key- map files. This feature allows the communications server to operate without a diskette, RBCS server, or NCS/AT, provided FTP and TFTP protocol and file support is available.

FTP support extends only to reading and writing configuration files as an FTP client. The communications server cannot act as an FTP server and does not offer an FTP-command.

With the addition of FTP, the SYS Service parameters FileSelection and FileServerAddr are now stored in EEPROM by the SYSgen command. The parameters UserId, UserPasswd, UserAccount, and ClientDIR, used by FTP, have been added to the SYS Service. These parameters are also stored in EEPROM, and are configured using the SYSgen command.

For details on the interaction of the communications server and its FTP file server, see Appendix B of the Multiprotocol Communications Server Operation Guide. For FTP interoperability information, based on 3Com communications server testing experience, see FTP Interoperability on page-8 of these release notes.

Termcap and Keymap Sharing

TN3270 termcap and keymap files are shared among all communications servers using the same file server. Changes to termcap or keymap definitions made on one commu- nications server are automatically propagated to the others without manual copying.

Any termcap or keymap that the communications server is using for active connections or editing must be present in communications server memory. Both TN3270 and TN3270TERM Services now include a cache that can hold up to 16 entries. Each service provides a CAche parameter that can be used to flush inactive copies of termcap and keymap definitions. Active entries, currently in use by the communications server, cannot be cleared from the cache.

Names for termcap and keymap definitions can now be up to 14 characters long.

Port Lists and Ranges

You can specify port lists in many configuration commands, reducing the number of commands required when many ports need to be configured similarly. You can also define named groups of ports, using the GRoup parameter in the SYS Service.

CS/3x00 Serial Line Extensions

Extensions to SW/3x00 software allow the use of both input control signals provided by CS/3x00 hardware, enabling input DTR detection (for modem hangup) to be used at the same time as input RTS detection (for hardware flow control). The -TERM UseDTRin parameter provides a new option to enable this additional input signal. For information on configuring this option, see SW/3000 Serial Port Configuration on page-37 of these release notes. Use of both input control signals also requires different wiring in the RS-232 interface adapter. See Notes and Cautions on page-9.

SW/3000 software offers two data rates above the 38.4k maximum offered by earlier versions, 64k and 76.8k.

Other 6.1 Enhancements

This section lists other changes in version 6.1 software. Some of these items were included in earlier maintenance releases, but they are mentioned here for the benefit of users upgrading directly from version 6.0 to version 6.2.

For SW/2500 software, the default port parameters have been changed to resemble SW/3000. Unless configured otherwise, all ports are terminal ports (-TERM DeVice = Terminal) with BAud set to AutoBaud and PARIty set to None. The communications server autobauds on the first carriage return. The [Return]. [Return] sequence is required only for AutoParity.

The AUToLogoFf parameter in the TERM Service and the LogoffStr parameter in the SYS Service allow a string to be sent before automatic (idle) disconnect on a host port.

The SUspendAction parameter in the TERM Service now controls the behavior of background (suspended) sessions. This feature allows background data to be discarded, which can be useful for real-time data streams.

The AllSessions and SESsions parameters in the TERM Service now include an option to display the remote TCP port. AllSessions also allows selective port display, and the SESsions display indicates when a port with sessions is in command mode.

The -TN3270 PortKeyMap and -TN3270TERM PortTermCap parameters can now be set to the value UNDEFINE to remove an assigned termcap or keymap.

The address list for SLIP has been increased from 8 entries to 48 entries on both communications server platforms. An entry in the list can represent multiple addresses by specifying a range in the last field of the IP address. For example, 129.213.154.100-112 represents addresses 129.213.154.100 through 129.213.154.112.

The new ADDRessControl parameter (shared by SLIP and PPP) allows the local address restriction to be lifted. This does not imply support for RIP announcements; if a non-local address is used, the communications server answers ARP requests for that address, or host routes can be configured on local routers to send packets for that address through the communications server.

The communications server now provides RS-232 MIB input and output signal table entries for its supported hardware signals, and returns dynamic values for the input and output flow-control states in the Char MIB.

If configuration files cannot be read from the file server, the communications server normally restarts the boot process rather than starting up with factory defaults. However, if the failure is due to a FileServerAddr whose first field is zero, the communications server starts in configuration mode to allow reconfiguration of file service parameters.

The communications server can now accept up to two Telnet connections for its user interface and provides echo and editing capability.

The TERM Service parameters DUplex and LineProtocol, present but not modifiable in previous releases, have been removed.

The macro variable $uname has been added. If access control is in use, references to this variable from macros on serial user ports expand to the username logged in on the port. If the user did not log in (access control is not used), this variable is empty and expands to the null string, which is interpreted by macro expressions as zero. Network sessions to the user interface always see the variable as empty, even if login was used.

When you use the menu interface to modify parameters, you must now precede port numbers with an exclamation mark (!), as in the command-line interface.

The PortGroups parameter in the LAT service can be configured on a per-port basis. You can configure different ports on a communications server with different access rights to LAT services on the network.

The PassXoff parameter in the TERM Service determines whether the communications server sends XOFF characters as data on a serial line configured for XON/XOFF flow control. The default value of OFF mimics the behavior of earlier software.

The per-port parameters ForwardSwitch and BackwardSwitch in the TERM Service de- fine characters that can be used to switch to the next or previous numbered session.

Software Compatibility

3Com tests with a variety of software to improve interoperability, but makes no specific vendor recommendations. This section describes PPP software, FTP software, and Line Printer Daemon Protocol interoperability.

PPP Interoperability

Table-1 lists PPP software vendors included in interoperability testing.

FTP Interoperability

Table-2 lists TCP/IP software vendors included in interoperability testing.

Line Printer Daemon Protocol

Line Printer Daemon Protocol (LPDP) normally describes the printer attached to the host in the /etc/printcaps file. One option for sending configuration data to the printer is through filter files.

Software version 6.2 has no printcaps and no support for filter files. To allow UNIX text files to print correctly, you may have to configure carriage return and line feed operation. The following example shows how to do this for a Hewlett-Packard LaserJet printer:

Telnet to the printers IP address.

Enter the following string:

^[&k2G

where ^[ represents [Ctrl]+[.

Exit the Telnet session.

In addition, the communications server software does not distinguish between text and PostScript data. If you send multiple PostScript jobs to the printer with header pages turned on, some files may not be printed. To prevent this problem, you can suppress the header page on an individual print job by using the LPR -h option, or you can turn off printing of all header pages by entering the following command:

SETDefault !<printer_port> -LinePrinter HeaDer = No

Notes and Cautions

This section describes notes, cautions, and other considerations to be aware of when using communications server software.

SLIP and PPP

SLIP and PPP require the TERM Service flow control parameters FlowCtrlFrom and FlowCtrlTo to be set to either None or CTS_RTS. CTS_RTS is the preferred setting. Do not use Xon_Xoff or Enq_Ack.

Upgrades to CLNP Service

When you copy configuration information to a 6.2 diskette from an earlier version, parameters in the CLNP Service are not copied. You must reenter the CLNP configuration.

Known Problems

The following problems are known to exist in version 6.2:

If the communications server is configured to use Bootstrap Protocol (BOOTP) and is given a server IP address on the same network, the BOOTP request to the server is sent in an Ethernet broadcast packet. If another system responds with an Internet Control Message Protocol (ICMP) Redirect packet, this packet may cause the communications server to install an incorrect default route in its routing table, and thus be unable to reach an FTP file server on another network.

The CS/3x00 does not send a Break character to the serial port when a Telnet Interrupt Process (IP) command is received from the network. Only the Telnet Break command produces a serial Break from the CS/3x00. The CS/2x00 produces a Break in either case.

The Multiprotocol Communications Server Reference Guide incorrectly indicates a number of options for the SecControl parameter in the IP Service. The only values permitted for this parameter are EXTended and NoEXTended.

The CS/2x00 does not remain flow-controlled if an XOFF is received on the serial line when there is no network connection. Any new connection to the port is not flow-controlled. (The CS/3x00 does retain the flow-control state, so new connections are allowed but cannot send data.) Both models clear the flow-control state when an active network connection is aborted.

When the EXPirationTimer in the AC service is set to Never, the SHow -AC CONFiguration command displays it as -1. In addition, the RBCS configuration editor always displays the value Never as -1, and does not allow that value to be set.

When the communications server receives an SNMP request whose destination IP address is one of its port addresses (assigned with the PortMAP parameter in the TCPAPPL Service), it provides a full SNMP response, with the communications server IP address as the source address.

Limitations

Software version 6.2 is subject to the following limitations:

The additional memory needed for new software features requires the number of TN3270 sessions available when running SW/2500-TO-3270 to be reduced from 40 (in version 6.0 and earlier) to 30 in versions 6.1 and 6.2. The number of TN3270 sessions in SW/2500-TLO-3270 has been reduced from 20 (in version 6.1 and earlier) to 14. The number of TN3270 sessions in SW/3000 remains at 96. The total number of sessions remains the same in all cases: 41 for SW/2500 and 193 for SW/3000.

Although the TRansmit command is available to send data through a suspended ses- sion, the session remains suspended (and flow-controlled), and does not receive any data from the network. This affects TN3270 sessions most severely, since a TN3270 ses- sion processes user input (such as TRansmit data) according to the data received from the network (such as the 3270 screen format). TRansmit data applies only to the last screen displayed, making TRansmit effectively unusable in macros for TN3270--sessions.

Communications Server PDF Limitations

Parameters and services available to the configuration editor in RBCS 2.0 and 2.1 are described in a parameter description file (PDF). The communications server PDF does not support certain parameters and services. Table-3 shows parameters and services that are not supported.

Software Packaging

The software package includes:

Eight 3.5-inch diskettes for use with diskette-based CS/2600 or CS/3100 systems

One 5.25-inch and one 3.5-inch tar-format diskette for use with NCS/AT-based systems

One 3.5-inch tar-format diskette for use with RBCS-based systems

One 3.5-inch DOS-format diskette for use with non-3Com servers

One 3.5-inch tar-format diskette for use with non-3Com servers

The label on each diskette indicates its use: -LOCAL, -NCS/AT, -RBCS, -DOS, or -UNIX. The diskettes are packaged in two cardboard diskette holders, one containing the local-boot floppies, the other the network-boot floppies.

3Com no longer supports NCS/AT servers. This is the last version of communications server software that will include NCS/AT diskettes.

Valid Filenames

This section lists valid names for files and directories on the multiprotocol communications server software local diskette. Table-4 lists the names of image files. Table-5 lists configuration files. Table-6 lists directories.

Installation

This section provides installation, upgrade, and startup procedures for each of the software distribution media.

All CS/3x00 and CS/2x00 communications servers are capable of booting and managing configuration data over the network. Network booting requires the software image to be installed on the boot server, and may require additional files to be installed on the file server.

The communications server firmware can use either System Load Protocol (SLP) or TFTP for booting, and the software can use either File Access Protocol (FAP) or FTP to access configuration files on the network. Both SLP and FAP are 3Com proprietary protocols. TFTP and FTP are standard protocols often available in a TCP/IP environment. A 3Com NCS/AT or RBCS server can act as a boot server and file server for a communications server using SLP and FAP; an RBCS server can also provide TFTP boot capability.

Models CS/3100 and CS/2600 include a diskette drive. These platforms can use the network for boot and file service, but also provide the option of using the local diskette.

The following sections provide installation instructions based on the expected boot source: local diskette, NCS/AT, RBCS server, or some other TFTP/FTP-capable host. In each case, it is assumed that the boot source is also used for file service: local diskette, FAP on the NCS/AT, FAP on the RBCS server, or FTP on a non-3Com FTP file server.

Booting from Diskette

To install and boot your communications server from diskette, insert the diskette in the drive. Turn the power on or, if it is already on, press the Reset switch on the front panel.

The software package includes several copies of the diskettes. Set at least one aside as a safe master, and use the others as working diskettes. If a working diskette becomes damaged, or if you need more than the number provided, you can produce new working diskettes by copying the master. See your communications server installation guide for information on copying disks.

If you are upgrading from earlier software, you can copy 6.0-level or 6.1-level configuration information from your current diskette onto your 6.2 working diskette. This is done by using firmware monitor commands to read and write diskette data. There are different procedures for the CS/2600 and the CS/3100.

Entering the Firmware Monitor

This section briefly describes how to enter the firmware monitor. For more information, see the installation guide and release notes for your communications server hardware.

To use the firmware monitor, you must place the communications server in monitor mode. This mode suspends normal operation and allows interaction only with the monitor command interface. After using the monitor, you must usually reboot the communications server to resume normal operation.

On a running CS/3x00, the easiest way to enter the firmware monitor is to use the MONitor command from a terminal attached to the console port. Otherwise, follow this procedure to enter monitor mode:

Connect a console terminal to port 0 (connector J0C) on the CS/2x00, or the console port (connector J1) on the CS/3x00.

Configure the terminal to 9600 baud, 8 bits, 1 stop bit, and no parity.

These instructions assume the default firmware configuration. If you have used firmware configuration commands to change the baud rate or to select a different console port, modify the instructions accordingly.

Make sure there is no diskette in the servers disk drive and the server is not connected to a boot source (for example, an NCS or RBCS server on the network).

If a diskette is in the disk drive, remove it. If the server is connected to a boot source, disconnect it.

Make sure the power is on and press the Reset switch on the front panel to reboot.

CAUTION: Do not press the hardware interrupt switch in the next step while the Self Test LED is on. Doing so can corrupt memory or firmware configurations. The Self Test LED can take several minutes to go out.

After the Self Test LED has gone out, press the hardware interrupt switch on the left side panel to enter monitor mode.

The hardware interrupt switch is recessed into the left side panel (as you face the front panel) and can be reached through the small hole in the air intake ventthe front vent for the CS/3x00 and the rear vent for the CS/2x00.

Wait a few seconds, then press the Return key on the console terminal keyboard.

The monitor greeting appears, followed by the monitor prompt (>).

Upgrading from 6.0 to 6.2 on a CS/2600

To copy configuration information from a SW/2500 version 6.0 diskette to a 6.2 diskette, follow this procedure:

Insert your 6.0 diskette.

At the monitor prompt (>) enter:

r 653 903000 1cc00

Remove the diskette and insert your 6.2 diskette.

At the monitor prompt, enter the following commands:

w 870 903000 4c00

w 89b 907c00 a00

w 8a0 908800 8200

w 8e2 910a00 ec00

w 959 91f600 400

The 6.2 diskette is ready to be booted. Remember to check parameter settings after the software starts.

Upgrading from 6.1 to 6.2 on a CS/2600

To copy configuration information from a SW/2500 version 6.1 diskette to a 6.2 diskette, follow this procedure:

Insert your 6.1 diskette.

At the monitor prompt (>) enter:

r 770 903000 27c00

Remove the diskette and insert your 6.2 diskette.

At the monitor prompt, enter the following command:

w 870 903000 27c00

The 6.2 diskette is ready to be booted. Remember to check parameter settings after the software starts.

Upgrading from 6.0 to 6.2 on a CS/3100

To copy configuration information from a SW/3000 version 6.0 diskette to a 6.2 diskette, follow this procedure:

Insert your 6.0 diskette.

At the monitor prompt (>) enter:

r 650 1003000 1d200

Remove the diskette and insert your 6.2 diskette.

At the monitor prompt, enter the following commands:

w 870 1003000 4c00

w 89b 1007c00 9000

w 8e3 1010c00 200

w 8e5 1010e00 e800

w 959 101f600 400

w 95c 101fa00 400

The 6.2 diskette is ready to be booted. Remember to check parameter settings after the software starts.

Upgrading from 6.0.2 to 6.2 on a CS/3100

To copy configuration information from a SW/3000 version 6.0.2 diskette to a 6.2 diskette, follow this procedure:

Insert your 6.0.2 diskette.

At the monitor prompt (>) enter:

r 650 1003000 1d200

Remove the diskette and insert your 6.2 diskette.

At the monitor prompt, enter the following commands:

w 870 1003000 4c00

w 89b 1007c00 9200

w 8e5 1010e00 ec00

w 95c 101fa00 400

The 6.2 diskette is ready to be booted. Remember to check parameter settings after the software starts.

Upgrading from 6.1 to 6.2 on a CS/3100

To copy configuration information from a SW/3000 version 6.1 diskette to a 6.2 diskette, follow this procedure:

Insert your 6.1 diskette.

At the monitor prompt (>) enter:

r 770 1003000 28200

Remove the diskette and insert your 6.2 diskette.

At the monitor prompt, enter the following commands:

w 870 1003000 28200

The 6.2 diskette is ready to be booted. Remember to check parameter settings after the software starts.

Booting from an NCS/AT

To boot your communications server from an NCS/AT, you must install the software image on an NCS running version 3.0.2 or later (earlier versions are not supported). You must also bind the communications server to the NCS.

If you are upgrading from 6.0-level or 6.1 software, you should first back up the /usr/NCS/CLIENTS/<Ethernet-address> directory. The 6.2 software automatically upgrades existing configuration files in that directory, and may change their internal-structure.

If you have TN3270 connections, the communications server uses existing termcap and keymap files in the /usr/NCS directory to maintain keymap and termcap definitions, which are shared by all 6.2 communications servers using the same NCS. If these files are not present, the communications server automatically creates files that hold 16 entries each. If you need more than 16 entries, you can install empty files large enough for 64 entries, following the instructions in step 3.

Installing the Software

To install the software on your NCS, follow this procedure:

Execute the floppyread command. The following files are installed:

/usr/NCS/BIN/cs25T.6.2 or

/usr/NCS/BIN/cs25TL.6.2 or

/usr/NCS/BIN/cs30T.6.2 or

/usr/NCS/BIN/cs30TL.6.2 communications server software image

/usr/NCS/termcap.init empty termcap files

/usr/NCS/keymap.init empty keymap files

For SW/3000, the following files are also installed:

/usr/NCS/BIN/siodiags SIO Processor diagnostics

/usr/NCS/BIN/sio30170 SIO Processor driver

If you use TN3270 and need more than 16 termcap or keymap definitions, use the mv command to rename the following empty termcap and keymap files to the names required by the communications server:

mv termcap.init termcap

mv keymap.init keymap

Binding the Server

After installing the software on your NCS, you must bind the NCS to the communications server. If you are upgrading your communications server, you must first unbind from the earlier software image using the unbind command. If you want to retain your existing configuration information, answer n when the NCS asks if the configuration directory should be removed. For example:

% unbind 122.123.124.125

% Do you wish to remove the directory /usr/NCS/CLIENTS/080002032D22? (y/n) n

Now use the bind command as described in the NCS/AT documentation. For example:

% bind %08000201adfc 122.123.124.125 -f cs25T.6.2

% bind %08000201adfc 122.123.124.125 -f cs30TL.6.2

Firmware Boot Configuration

For your communications server to boot successfully from an NCS, it must be configured to use the SLP protocol. SLP is the default. If the boot protocol has been changed, you can set it to SLP using the firmware monitor. See your communications server installation guide for instructions on entering the firmware monitor and using the fc command to change the firmware configuration.

You can now boot your communications server by turning it on or by pressing the Reset switch on the front panel.

Booting from RBCS

You can boot a communications server from a Sun SPARCstation running RBCS software version 2.0 or later. See your RBCS documentation for more information.

If you have TN3270 connections, the communications server uses termcap and keymap files and TERMCAPS and KEYMAP subdirectories. The RBCS requires an update to its fapd.conf file to notify the fapd server that these directories exist, and an update to fapd itself is required for the RBCS to handle large termcap and keymap data records. These updates are included on the distribution diskette.

Installing the Software

The installation procedure and update script is the same for all four varieties of 6.2 software. If you are installing more than one, complete steps 1 through 4 for each release, then continue with step 5.

Change to the RBCS home directory:

cd `cat /etc/nmhome.3Com`/rbcs

This directory varies with your installation and RBCS version.

Insert the communications server software diskette in the RBCS servers diskette drive.

Enter the following command:

tar xvpf /dev/fd0

Entering this command causes the appropriate files to be installed from the software distribution diskette. The following filenames should be displayed:

./data/image/c.s25T.6.2 or

./data/image/cs25TL.6.2 or

./data/image/cs30T.6.2 or

./data/image/cs30TL.6.2 communications server software image

./etc/fapd.s3 updated FAP demon

./etc/fapd.conf.s3 updated fapd.conf file

For SW/3000, the following files are also installed:

./data/BIN/siodiags SIO processor diagnostics

./data/BIN/sio30170 SIO processor driver

Files similar to the following should also appear:

./conf/pdf/3000-TLO-6.2.pdf.s3

./help/3000-TLO-6.2.pdf.info.s3

./data/CLIENTS/defcs30.6.2/<default files>

These files contain data to be used by the RBCS configuration editor. The actual file and directory names vary with the software being installed.

Finally, an installation script is loaded:

./install/update.cs6.2

Enter the following command to change to the install subdirectory:

cd install

Enter the following command to run the installation script and update RBCS files:

update.cs6.2

Review the execution output messages in /tmp/update.cs6.2.out for errors. You may want to save this file in the ./logs directory for future reference.

Add the following line to conf/fapd.conf:

SHAREDF: termcaps 1024 1024 TERMCAPS # shared termcaps

If you are upgrading from an earlier software version, and you are upgrading all communications servers, move the data/TERMCAP subdirectory under the RBCS home directory to data/TERMCAPS under the home directory. If some communications servers will continue to use earlier versions of software, create a data/TERMCAPS directory under the RBCS home directory, and copy all files under data/TERMCAP to this new directory.

Stop RBCS if it is running. Go to the RBCS main window, select MENU on the headline, and choose Quit from the popup menu.

Restart RBCS from the console window, logged in as RBCS user. Enter this command:

rbcs &

Restart RBCS servers by selecting RBCS Server from the RBCS main window on your screen. Select all, then stop and restart the RBCS servers.

You have now completed software installation.

Updating the Database

If this is an upgrade, proceed to Changing an Existing Client Entry on page-22. If this is a new installation, add the communications server to the boot database, using the Add submenu of the Bootdb menu of the RBCS Tools window. If you psee edit the boot database manually, you can use the editbd command from the command line.

See the Remote Boot and Configuration Services Users Guide for complete information on performing this task, using either of the two methods. Table--7 lists the software database values followed by examples of database entries.

Add 6.2 templates to the installation script using the mandb command. This command places the new entries at the end of the file. If you normally use editbd to modify the boot database, you may want to move these new entries to the area in the file where the other tc templates are grouped.

A boot database entry using editbd might look as follows:

For SW/2500:

cs2500:bf=cs25TL.6.2:ha=0x080002012345:ip=129.213.200.201:\

tc=SW2500-TLO-3270-6.2:sm=255.255.252.0:sa=SW/2500-TLO-3270-6.2:

For SW/3000:

cs3000:bf=cs30TL.6.2:ha=0x080002012345:ip=129.213.200.201:\

tc=SW3000-TLO-3270-6.2:sm=255.255.252.0:sa=SW/3000-TLO-3270-6.2:

Changing an Existing Client Entry

To upgrade from earlier software to 6.2, follow this procedure:

In the RBCS Tools menu, click on the BOOTdb button.

Choose Modify from the BOOTdb menu that appears.

Select the desired communications server, then click on Modify.

The Client menu display appears.

Change the bootfile entry and click on Apply.

This completes the addition or modification of a client entry.

Firmware Boot Configuration

For your communications server to boot successfully from an RBCS server, it must be configured to use the SLP protocol. SLP is the default. If the boot protocol has been changed, you can set it to SLP using the firmware monitor. See your communications server installation guide for instructions on entering the firmware monitor and using the fc command to change the firmware configuration.

You can now boot your communications server by turning it on or by pressing the Reset switch on the front panel.

Booting from Generic TFTP/FTP Hosts

Your communications server can boot from a non-3Com host, as long as that host supports a TFTP server, and an FTP server is also available on the network. The FTP and TFTP servers may be, and usually are, on the same host, but this is not required.

To operate using TFTP/FTP, the communications server software image must be loaded onto the TFTP server, and for a CS/3x00 the SIO image files must be loaded onto the FTP server. These files are provided on 3.5-inch DOS or tar format (UNIX) diskettes.

On the DOS diskette, the communications server software image is one of the-following:

T25V61 SW/2500-TO-3270-6.2
TL25V61 SW/2500-TLO-3270-6.2
T30V61 SW/3000-TO-3270-6.2
TL30V61 SW/3000-TLO-3270-6.2

TO versions include TCP/IP and OSI services. TLO versions include TCP/IP, OSI, and LAT.

With SW/3000, the following SIO files are also present:

SIO30170 SIO processor driver
SIODIAGS SIO processor diagnostics

On the tar diskette, the communications server software image is one of the following:

cs25T.6.2 SW/2500-TO-3270-6.2
cs25TL.6.2 SW/2500-TLO-3270-6.2
cs30T.6.2 SW/3000-TO-3270-6.2
cs30TL.6.2 SW/3000-TLO-3270-6.2

With SW/3000, the following SIO files are also present:

sio30170 SIO Processor driver
siodiags SIO Processor diagnostics

The software image itself should be loaded onto the TFTP server in a location appropriate for your host. (For security reasons, some hosts impose restrictions on directories that can have TFTP access.) If you plan to use BOOTP in order to pass TFTP information to the communications server, remember to add the appropriate BOOTP configuration to your BOOTP server.

TFTP/FTP Host Configuration

To configure the FTP server for the communications server to use it as a file server, follow this procedure:

Create a user login with a password (and an account if needed) on the FTP server.

This is the login for the communications server to use when reading or writing configuration files via FTP.

Create the user (login) directory. All files read and written by the communications server see subdirectories of the login directory.

For a CS/3x00, create a BIN subdirectory in the login directory, and install the SIO files from the distribution diskette there.

This needs to be done only once. It does not need to be repeated for each communications server using the same login.

If you are upgrading from an earlier software version, and you are upgrading all communications servers, move the $home/TERMCAP directory to $home/TERMCAPS. If some communications servers will continue to use earlier versions of software, create a $home/TERMCAPS directory, and copy all files under $home/TERMCAP to this new directory.

$home is the home directory of the FTP user account or value of the -SYS ClientDIR parameter.

See Appendix B of the Multiprotocol Communications Server Operation Guide for more information on the communications servers use of FTP, including assumptions and requirements about directory names and placement, and filenames.

Communications Server Firmware Boot Configuration for TFTP Boot

For your communications server to boot successfully using TFTP, you must configure the communications server firmware appropriately, using the firmware monitor. To access the firmware monitor, see Entering the Firmware Monitor on page-15 or to your hardware installation guide. The following procedure assumes that you have obtained a monitor prompt (>).

Use the fc (firmware configuration) command to enter the configuration menu system. Follow the prompts to select configuration parameters and values.

Change the Boot Protocol to TFTP.

Select Boot Protocol from the main menu and choose the TFTP option. When the Boot Protocol is TFTP, an additional submenu (Change IP/TFTP parameters) becomes available from the main menu.

Enter the IP/TFTP submenu by selecting Change IP/TFTP parameters.

Configure the items in the submenu as your environment requires.

If you plan to use BOOTP, select BOOTP for address discovery. The communications server obtains its IP address, server IP address, subnet mask, and bootfile name from the BOOTP exchange.

The host BOOTP server must be configured to answer the communications server BOOTP request and provide the desired information. See the documentation provided with your boot server on setting up BOOTP/TFTP. If you are using a 3Com RBCS server as a boot server for BOOTP/TFTP, an entry in the boot database provides the necessary BOOTP configuration.

If you do not plan to use BOOTP, select Local Information as the Address Discovery option. Configure the Client IP address and Subnet mask value with the IP address and subnet mask for the communications server. Configure the Server IP address as the address of the TFTP server. If the TFTP server is on a different IP subnetwork from the communications server, configure the Gateway IP address accordingly. Return to the main menu, and configure the Network boot string option with the pathname for the download image. The communications server uses this string in the TFTP download request.

If the TFTP server (boot server) and the communications server are on the same subnet, but the FTP server (file server) is on a different net, you may need to configure the Gateway IP address in order for the communications server to reach its file server. If the gateway between the communications server and its file server answers proxy ARP requests, the gateway address is not required.

Software Configuration for FTP Boot

When the firmware configuration is complete and the communications server image has been installed on the boot server, use the following procedure to configure the communications server:

Connect a console terminal to port 0 (connector J0C) on the CS/2x00, or the console port (connector J1) on the CS/3x00.

Configure the terminal to 9600 baud, 8 bits, 1 stop bit, and no parity.

Make sure the power is on and press the Reset switch on the front panel to reboot.

After self-test is complete, the communications server downloads its software image, and the software comes up in configuration mode.

Configure file service parameters.

Press the Return key to obtain a command prompt from the software, and set your privilege level to Network Manager using the command:

SET PRI = NetMgr

The communications server prompts for a password. Since none has been configured, press the Return key. The network manager prompt (cs #) appears.

You can now configure file service parameters using the SYSgen command. You must assign at least the FileSelection, FileServerAddr, UserId, and UserPasswd parameters:

SYSgen -SYS FileServerAddr = <ip address>

SYSgen -SYS FileSelection = FTP

SYSgen -SYS UserID = "<name>"

SYSgen -SYS UserPasswd = "<password>"

The values assigned must agree with the configuration of your FTP server. Also configure the UserAccount and ClientDir parameters, if applicable:

SYSgen -SYS UserAccount = "<account>"

SYSgen -SYS ClientDIR = "<commservername>"

Use the SHow -SYS SYSgen command to check the configuration of these parameters.

Confirm FTP access by using the SHow -SYS MACros command.

The response Disk I/O error indicates that access is not available.

Press the Reset switch again.

After downloading the software image, the communications server uses the file service information configured above to access its file server and read its configuration files. If this is an initial boot, there are no configuration files, and the communications server uses factory defaults for all parameters.

See Appendix B of the Multiprotocol Communications Server Operation Guide for more information on how the communications server uses FTP, including directory names and placement and filenames.

Operation Guide Updates

This section describes changes and additions to the Multiprotocol Communications Server Operation Guide, May 1994.

Chapter 2, Getting Started

Add the following information to the section on Setting the Date and Time on page 2-10.

Setting the Date and Time Using NTP

Network Time Protocol (NTP) is a nonproprietary way for devices on a network to synchronize their time-of-day clocks according to a designated source. If you have an NTP server on your network, the communications server can set its date and time over the network without a 3Com Remote Boot and Configuration Services (RBCS) server or Network Control Server (NCS). NTP parameters are found in the SYS Service.

To configure your communications server to set its date and time using NTP, follow this procedure:

Specify the IP address that NTP should use as the primary time server, using the following syntax:

SETDefault -SYS NTPPrimarySrvr <ipaddr>

The default is 0.0.0.0. You must enter a different value, because this is not a valid time server address.

Specify the IP address that NTP should use as the backup time server, using the following syntax:

SETDefault -SYS NTPBackupSrvr <ipaddr>

The default is 0.0.0.0. You must enter a different value, because this is not a valid time server address.

The communications server uses this address if the primary time server address is 0.0.0.0 or unreachable, or if the address does not respond to NTP packets. If NTPBackupSrvr is also 0.0.0.0 or unreachable or does not respond, then NTP uses any NTP server that is broadcasting NTP packets as its time server.

Set the communications server to use NTP to synchronize its clock by entering the following command:

SETDefault -SYS NetworkTimeSource = NTP

Change the poll interval if desired, using the following syntax:

SETDefault -SYS NTPPollInterval = <number> (120 minutes)

NTPPollInterval defines the longest interval at which the communications server sends NTP packets to the primary and backup time servers. The default is 1 minute. After reset or reconfiguration, the communications server initially sends NTP packets to each server at one-minute intervals. This interval can increase automatically up to the value of NTPPollInterval if the communications server remains closely synchronized with network time.

To verify the status of NTP, enter the following command:

SHow -SYS NTPStatus

This command displays information about the current status of NTP on the communications server.

For information about interpreting the display, or about NTP commands, see Chapter 17, SYS Service Parameters on page-49 of these release notes.

Chapter 4, Using Your Server in TCP/IP Environments

Software version 6.2 allows you to assign 0 to the subnet field of an IP address.

Chapter 7, Using Your Server in TN3270 Environments

Add the following material on ASCII edit, file transfer, and print screen features to this chapter.

ASCII Edit

In addition to using the KeyMapEntry and TermCapEntry parameters in the TN3270TERM Service, you can now create or edit keymap and termcap files using a host-based editor. You can also derive a termcap directly from a UNIX file (such as /etc/termcap).

If the communications servers configuration file source is FAP, it can take up to 30 minutes to recognize keymap and termcap files created through the use of an editor on the host. Restarting the FAP daemon on the RBCS server allows the communications server to recognize the new files immediately.

Using a Host Editor to Create a Termcap File

Each line in a termcap file starts and ends with a colon (:), and entries are separated by colons. See the TermCapEntry parameter in Chapter 22, TN3270TERM Service Parameters, of the Multiprotocol Communications Server Reference Guide for information about available entries.

For example, to create a VT100 termcap on a UNIX host, use the vi editor to create a file named vt100 in the termcaps directory:

vi <termcaps>/vt100

If the -SYS FileSelection parameter is set to Remote (the communications servers configuration file source is FAP), <termcaps> is the data/TERMCAPS directory under the RBCS home directory. If FileSelection is set to FTP, it is the $home/TERMCAPS directory, where $home is the home directory of the FTP user account or value of the -SYS ClientDIR parameter.

Now type in the following data:

:do=^J:co#80:li#24:cl=50\E[;H\E[2J:sf=5\ED:

:le=^H:bs:am:cm=5\E[%i%d;%dH:nd=2\E[C:up=2\E[A:

:ce=3\E[K:cd=50\E[J:so=2\E[7m:se=2\E[m:us=2\E[4m:ue=2\E[m:

:md=2\E[1m:mr=2\E[7m:mb=2\E[5m:me=2\E[m:is=\E[1;24r\E[24;1H:

:rs=\E>\E[?3l\E[?4l\E[?5l\E[?7h\E[?8h:ks=\E[?1h\E=:ke=\E[?1l\E>:

:ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:kb=^H:

:ho=\E[H:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:pt:sr=5\EM:vt#3:xn:

:sc=\E7:rc=\E8:cs=\E[%i%d;%dr:

Save the file and exit the editor.

Suppose you want to create a Wyse 50 termcap on a UNIX host using existing /etc/termcap information. The /etc/termcap file might include the following lines for the Wyse 50 terminal:

ye|w50|wy|wyse30|wyse50|wyse-50|Wyse 50 in Wyse mode:

:al=\EE:am:bs:bt=\EI:cd=\EY:ce=\ET:cl=^Z:cm=\E=%+ %+ :co#80:\

:da:db:dc=\EW:dl=\ER:ei=\Er:im=\Eq:is=\E`\072\200\EC\EDF\E'\E(:\

:kd=^J:kl=^H:kr=^L:ku=^K:li#24:nd=^L:up=^K:us=\EG8:ue=\EG0:\

:so=\EG4:se=\EG0:sg#1:sr=\Ej:ho=^^:ug#1:

Copy all these lines except the first to <termcaps>/wyse50:

:al=\EE:am:bs:bt=\EI:cd=\EY:ce=\ET:cl=^Z:cm=\E=%+ %+ :co#80:\

:da:db:dc=\EW:dl=\ER:ei=\Er:im=\Eq:is=\E`\072\200\EC\EDF\E'\E(:\

:kd=^J:kl=^H:kr=^L:ku=^K:li#24:nd=^L:up=^K:us=\EG8:ue=\EG0:\

:so=\EG4:se=\EG0:sg#1:sr=\Ej:ho=^^:ug#1:

Make any modifications you need and save the file.

Using a Host Editor to Create a Keymap File

Each line in a keymap file starts and ends with a colon (:), and entries are separated by colons. See the KeyMapEntry parameter in Chapter 21, TN3270 Service Parameters, of the Multiprotocol Communications Server Reference Guide for information about available entries.

For example, to create a VT100 keymap on a UNIX host, create a file using the vi editor:

vi <keymap>/vt100

If the -SYS FileSelection parameter is set to Remote (the communications servers configuration file source is FAP), this directory is the /data/KEYMAP directory under the RBCS home directory. If FileSelection is set to FTP, it is the $home/KEYMAP directory, where $home is the home directory of the FTP user account or value of the -SYS ClientDIR parameter.

Now type in the following data:

:ku=\EOA=Up arrow:kl=\EOD=Left arrow:kr=\EOC=Right arrow:

:kd=\EOB=Down arrow:K1=\EOP=PF1:K2=\EOQ=PF2:K3=\EOR=PF3:P1=\EOq=Num 1:

:P2=\EOr=Num 2:P3=\EOs=Num 3:P4=\EOt=Num 4:P5=\EOu=Num 5:P6=\EOv=Num 6:

:P7=\EOw=Num 7:P8=\eox=num 8:P9=\EOy=Num 9:PA=\033\060=ESC 0:

:PB=\E1=Esc 1:PC=\E2=Esc 2:PM=\E3=Esc 3:PN=\E4=Esc 4:PO=\E5=Esc 5:

:PP=\E6=Esc 6:PQ=\E7=Esc 7:PR=\E8=Esc 8:PS=\E9=Esc 9:PT=\E0=Esc 0:

:PU=\E\EOq=Esc Num-1: :PV=\E\EOr=Esc Num-2:PW=\E\EOs=Esc Num-3:

:PX=\E\EOt=Esc Num-4:BT=\E^I=Esc TAB:JP=\Ej=Esc j:DU=\E#=Esc #:

:kh=\Eh=Esc h:L5=^Y=Ctrl-y:rP=^R=Ctrl-r:Lp=^B=Ctrl-b:Rm=^U=Ctrl-u:

:Xp=^X=Ctrl-x:TB=^I=TAB:eF=^P=Ctrl-p:EI=^E=Ctrl-e:FM=^D=Ctrl-d:

:CL=^W=Ctrl-w:RE=^Z=Ctrl-z:CX=^C=Ctrl-c:IN=^N=Ctrl-n:hK=^A=Ctrl-a:

:EN=^M=Return:CR=^O=Ctrl-o:bs=^H=Ctrl-h:tR=^T=Ctrl-t:DL=\177=Del:

:cS=\el=Esc l:

Save the file and exit the editor.

File Transfer

You can transfer files between a local PC acting as a terminal and a remote host of a TN3270 session, using the Kermit protocol. The transfer is transparent, that is, the communications server does not process or interpret data during the transfer. The KermitEchar parameter for file transfer is found in the TN3270 Service.

Transferring from the Server to a PC.

To transfer a text file from a TN3270 server to a PC, follow this procedure:

Establish a TN3270 session from the communications server to a host.

Execute the kermit command on the host.

Set the end packet character to be the same on the PC, communications server, and host. If the end packet character is not [Ctrl]+M (displayed as ^M), set this character on the communications server using the following syntax:

SET -TN3270 KermitEchar = <char>

Execute the kermit send command on the host.

Press the XPARENT key ([Ctrl]+X by default) on the PC to put the communications server session in transparent mode.

Escape to the PC and execute the kermit get command.

The communications server session returns to normal data mode after the file transfer is completed, or after a fatal error occurs.

For further information about the Kermit end packet character and the XPARENT key, see Chapter 21, TN3270 Service Parameters on page-54 of these release notes.

Transferring from a PC to the Server.

To transfer a text file from a PC to a TN3270 server, follow this procedure:

Establish a TN3270 session from the communications server to a host.

Execute the kermit command on the host.

SET -TN3270 KermitEchar = <char>

Execute the kermit receive command on the host.

Press the XPARENT key ([Ctrl]+X by default) on the PC to put the communications server session in transparent mode.

Escape to the PC and execute the send kermit command.

The communications server session returns to normal data mode after the file transfer is completed, or after a fatal error occurs.

For further information about the Kermit end packet character and the XPARENT key, see Chapter 21, TN3270 Service Parameters on page-54 of these release notes.

Binary Files.

To transfer a binary file, add the following steps between step 3 and step 4 in the previous two procedures:

Set the Kermit controller type to graphics on the host. (This may be the default.)

Execute the kermit set file type binary command on the host.

Print Screen

The print screen feature enables a TN3270 user to print the current screen information to a designated printer attached to the communications server. The designated printer can be either a dumb ASCII printer attached to a serial port or a parallel printer that can print plain ASCII data.

To print a screen, press the PRINT key. The default value for PRINT is [Ctrl]+B. To cancel a print request, press the CANCEL key. The default value for CANCEL is [Ctrl]+U. To assign different values to these keys, see KeyMapEntry on page-54.

Print screen configuration parameters belong to the LinePrinter Service. To configure the print screen feature, follow this procedure:

Assign a port to a printer port, for example:

ADD !7 -LinePrinter PRinter !0-!6

This command assigns the printer attached to port 7 to ports 0, 1, 2, 3, 4, 5, and 6. Configure all other port-dependent parameters for port 7 under the TERM Service according to the printer characteristics. DeVice should be set to Host, and BAud should be the fixed rate that the printer runs at.

Assign a name to the printer, for example:

SETDefault !7 -LinePrinter PRinterName = local

This command assign the name local to the printer on port 7. The printer name can be up to 10 characters long.

The PrinterLineterm parameter determines the termination string that is inserted at the end of each line: carriage return (CR), line feed (LF), or both (CRLF). The default is CRLF. If your printer requires a different termination character, change this setting, as in the following example:

SETDefault !7 -LinePrinter PrinterLineterm = CR

This command tells the communications server to set the line termination string to CR for the printer attached to port 7.

Adjust the print queue size.

By default, no more than five print jobs can be queued for a printer, in order to prevent exhaustion of system resources when a printer is not functioning. When a print queue reaches its limit, additional print requests are rejected. To change the print queue size, set the MaxPrintQueue parameter, as in the following example:

SETDefault !7 -LinePrinter MaxPrintQueue = 2

This command changes the print queue size for port 7 to 2.

You can disable a printer by setting its MaxPrintQueue to 0. This prevents new jobs from being appended to the queue, but jobs already in the queue are still printed out.

To manage the print queue, use the PrintQueue parameter:

FLush !7 -LinePrinter PrintQueue

This command flushes the print queue for printer port 7.

For more information about these commands, see Chapter 1, Commands on page-42 and New Chapter, LinePrinter Service Parameters on page-56 of these release notes.

Chapter 12, Using Printing Resources

For information about the TN3270 print screen feature, see Print Screen on page-31 of these release notes.

Add the following new section to this chapter.

Using Line Printer Daemon Protocol

Line Printer Daemon Protocol (LPDP), described in RFC 1179, is a TCP-based protocol used in UNIX environments for sending files to printers. Software version 6.2 supports LPDP in both server and client mode. LPDP in server mode allows a user on a host that supports LPDP client to print files to a printer attached to a communications server. LPDP in client mode allows a PC user to print a file on a local disk to an LPDP print server. This feature uses the LPR, LPQ, and LPRM commands, as well as parameters in the LinePrinter Service.

Configuring Server Mode

To allow remote users to print files on a printer attached to the communications server, follow this procedure:

Add an entry in the /etc/printcap file on a host that allows users to enter LPR, LPQ, and LPRM commands, for example:

csprt:

:rm=129.232.97.55:

:rp=csprt:

:sd=/usr/spool/csprt:

:mx#0:

where 129.232.97.55 is the IP address of the communications server, and csprt is a printer name on the communications server.

Enable LPDP server mode on the printer port of the communications server by entering a command similar to this one:

SETDefault !48 -LinePrinter PRinterName = csprt

Configuring Client Mode

To allow users to print a text file residing on the local disk to a remote printer, follow this procedure:

Define the remote printer on a communications server using the ADD RemotePRinter command, for example:

ADD -LinePrinter RemotePRinter lp 129.232.97.102

where lp is a printer name defined in the /etc/printcap file on the 129.232.97.102 node. 129.232.97.102 is the IP address of a host that either has a physical connection to the target printer or knows how to route the print request to the target printer.

Assign a default remote printer for each port, for example:

SETDefault !ALL -LinePrinter DefPRinter = lp

This command sets the default printer for all ports to lp.

Configuring Printing of PC Files

You can also print files from a PC to a printer attached to the communications server. To configure printing with queueing capability, follow this procedure:

Set up an LPDP server for the printer, following the procedure under Configuring Server Mode on page-32 of these release notes.

Define a remote printer with an IP address that points to a host that knows the printer. For example, to enable the csprt printer to accept local print requests:

ADD -LinePrinter RemotePRinter csprt 129.232.97.21

where 129.232.97.21 is the IP address of a remote host that has a csprt entry in its /etc/printcap file.

To configure printing of files from a PC to a printer attached to the communications server but without queueing capability, follow this procedure:

Define a remote printer with an IP address that points to the communications server, for example:

ADD -LinePrinter RemotePRinter local 129.232.97.55

where 129.232.97.55 is the IP address of the communications server and local is the printer name.

Define a local printer whose name is the same as the remote printer name:

SETDefault -LinePrinter !7 PRinterName = local

If you configure local printing without queuing, printer contention may cause the remote host to delay printing of host files for an indeterminate time.

Printing Files

To print files in client mode, use the LPR command. The following command prints 3,210 bytes of a file named report to the image printer three times:

LPR -Pimage -#3 3210 report

The following command prints 3,210 bytes of a file named report to the image printer in 132 columns without the header page:

LPR -Pimage -w132 -h 3210 report

To remove jobs from the print queue by job number, use the LPRM command. (To find a job number, use the LPQ command.) The following command attempts to remove job 5 and job 7 from the image printer queue, even though job 5 is not in the queue:

LPRM -Pimage 5 7

prtserver.org.net.COM: dfA007bangle.org.net.COM dequeued

prtserver.org.net.COM: cfA007bangle.org.net.COM dequeued

In this display, 007 is the job number, and df and cf see data file and control file.

This command removes all jobs issued by the port from the image printer queue:

LPRM -Pimage -

prtserver.org.net.COM: dfA002bangle.org.net.COM dequeued

prtserver.org.net.COM: cfA002bangle.org.net.COM dequeued

To display the contents of a print queue, including the numbers assigned to print jobs, use the LPQ command. The following command displays the print queue of a remote printer named image:

LPQ -Pimage

Rank Owner Job Files Total Size

active frank 31 standard input 9332 bytes

1st liza 32 lpr.c 1952 bytes

The following command displays the print queue of the default printer in long form:

LPQ -l

frank: active [job 031mtview.org.net.COM]

standard input 9332 bytes

liza: 1st [job 032mtview.org.net.COM]

lpr.c 1952 bytes

For information about the syntax of the LPQ, LPR, and LPRM commands, see Chapter 1, Commands on page-42.

Chapter 13, Using Network Management

Configuring Your Server to Generate Audit Trail Messages

You can send audit trail messages to any UNIX server running syslogd, as well as to an RBCS server or an NCS using the proprietary 3Com FAP protocol. The commands for this feature belong to the SYS Service.

To configure the syslogd protocol on your communications server, follow these steps:

Set the LogServerProt parameter to Syslogd by entering the following command:

SETDefault -SYS LogServerProt = Syslogd

Set the threshold priority above which audit trail messages are sent to the audit server, using the following syntax:

SETDefault -SYS SyslogTHreshold = Info | Notice | Warning |

Err | Crit | Alert | Emerg

The value of SyslogTHreshold is the lowest priority message that is sent. If you set SyslogTHreshold to Info, all messages are sent. If you set SyslogTHreshold to Emerg, only messages with priority LOG_EMERG are sent.

For a list of syslogd priority codes associated with each audit trail message, see New Chapter, SW/3000 Serial Port Control on page-37 of these release notes.

If you are using an audit macro, define a priority level for it, using the following syntax:

SETDefault -SYS MacroAuditLevel = Info | Notice | Warning |

Err | Crit | Alert | Emerg

For further information about syslogd protocol commands, see Chapter 17, SYS Service Parameters on page-49 of these release notes.

Telnet Debug Option

Add the following new section on the Telnet debug option to Using the Telnet or Connect Command on page 13-7.

The Telnet debug option allows you to view Telnet negotiation in progress, a convenient method for troubleshooting potential negotiation problems. To turn on this option, enter one of the following commands:

SET -TERM TNOptionDebug = On

SETDefault -TERM TNOptionDebug = On

Alternatively, you can turn on debugging for a particular Telnet session by including the -d option when you open the connection, using the following syntax:

TELnet [!<port>] <address | name> -d

Example

TWhen Telnet debugging is turned on, the display looks like this:

TELnet 129.213.16.57

Trying: 129.213.16.57

Connecting using IP ... connected session 1, ECMChar is ^^

SENT will SUPPRESS GO AHEAD

SENT do SUPPRESS GO AHEAD

SENT do ECHO

RCVD do TERMINAL TYPE

SENT will TERMINAL TYPE

RCVD do SUPPRESS GO AHEAD

RCVD will SUPPRESS GO AHEAD

RCVD will ECHO

RCVD do ECHO

SENT will ECHO

SunOS UNIX (sthelens.NSD.3Com.COM)

RCVD dont ECHO

SENT wont ECHO

jvh

Password:

Last login: Mon Oct 10 14:59:42 from jvh-70.NSD.3Com.

Port Monitoring

Add the following new section on port monitoring.

Port monitoring is a debugging feature that allows network managers to view all data transmitted and received over any serial port on the communications server. The data is displayed on the network managers port, either a serial port, a network management host port, or a console port. This tool can help resolve problems with modem, terminal, or network connections.

In order to debug TN3270, SLIP and PPP sessions, as well as Telnet connections or simple terminal sessions without network connections, port monitoring provides two display modes, ASCII and Hex.

To monitor a port, enter the following syntax:

PortMonitor !<port> [Ascii | Hex]

The default is Hex.

Example 1

This display shows a port monitored in hex mode:

pm !1 hex

< = transmitted > = received

> 0D *.*

< 0D 0A *..*

< 57 65 6C 63 6F 6D 65 20 74 6F 20 74 68 65 20 33 *Welcome to the 3*

< 43 6F 6D 20 43 6F 6D 6D 75 6E 69 63 61 74 69 6F *Com Communicatio*

< 6E 73 20 53 65 72 76 65 72 0D 0A *ns Server..*

< 5B 36 5D 43 53 3E 20 [1]CS > *

Example 2

This display shows a port monitored in ASCII mode:

pm !2 a

< = transmitted > = received

> <CR>

< <CR><LF>

< Welcome to the 3Com Communications Server<CR><LF>

< [1]CS >

The arrow at the start of each line indicates the direction of data flow.

You can start a monitoring session regardless of whether the monitored port is in Listen, Command, or Data Transfer mode. To end a monitoring session, type a break character on the monitoring port. An audit message is sent when a monitoring session is started and when one is terminated.

To show all ports being monitored and the ports monitoring them, use the PortMonStat command:

SHow -TERM PortMonStat

If the monitoring port is a network management port reached by a Telnet or VTP connection, it is shown as Network Manager UI. This parameter also displays the number of bytes transmitted, received, and lost in each direction.

Example 3

The following display shows port monitoring statistics:

SHow -TERM PortMonStat

Monitored Monitoring bytes bytes xmit rcvd

port port xmit rcvd lost lost

5 9 10 8 0 0

7 NMUI 98 47 1 0

8 Console 14 76 0 0

SHow -TERM PortMonStat

No ports being monitored.

Restrictions

Port monitoring is subject to the following restrictions:

You can monitor only serial ports, not the parallel port.

A port can monitor only one port at a time.

A port can be monitored by only one port at a time.

A port that is monitoring cannot be monitored.

Monitoring continues regardless of which session owns the data. If the current session on the monitored port is suspended, monitoring is not suspended, but the session that replaces the current session is monitored. Monitoring does not end until you type a break character.

The SHow !<port> -TERM SESsions and SHow -TERM AllSessions commands do not report port monitoring.

Chapter 14, Using Aliases and Macros

New Chapter, SW/3000 Serial Port Control

Add the following new chapter on SW/3000 serial port control.

Versions of SW/3000 software before 6.1 supported the use of a single input control signal on each port, whose interpretation is controlled by the -TERM UseDTRin and FlowCtrlTo parameters. With UseDTRin set to Ignore and FlowCtrlTo to CTS_RTS, the input signal could be used to flow-control the communications server. Otherwise the signal would be interpreted as DTR (according to UseDTRin), and FlowCtrlTo would have no effect.

Version 6.1 and higher enable the use of a second input control line on CS/3x00 serial ports, so that RTS and DTR need not share one signal. The second input allows an attached device to use CTS/RTS flow control and still use DTR to signal the communications server to disconnect (or DCD to signal when a hangup has occurred).

The syntax of the UseDTRin parameter allows software control of input pin selection, as well as signal interpretation:

SETD [!<portlist>] UseDTRin = ([Ignore | AsDTR | AsDCD],

[OnRTS | OnDTR])

If the second value is OnRTS, then DTR and RTS share the same signal. This behavior is identical to earlier software and is the default. If the second value is set to OnDTR, then the original input line is interpreted only as RTS, and the second input line is interpreted as DTR.

The behavior of the single output control signal has not changed. If FlowCtrlFrom is set to CTS_RTS, the signal is used (as CTS) to flow-control the attached device. If not, the signal behaves according to the configuration of the UseDCDout parameter.

Configuration Examples

The following examples illustrate the options for UseDTRin when determining the behavior of control signals on a serial port. The software uses a data communications equipment (DCE) point of view for signal names; for instance, DTR is a control input and DCD is a control output. The signals actually used depend on the wiring adapters (see RS-232 Interface Adapters on page-39 of these release notes).

The examples all use port !7 and assume an attached modem. They involve configuration of the UseDTRin, UseDCDout, FlowCtrlFrom, and FlowCtrlTo parameters. See the Multiprotocol Communications Server Reference Guide for more information on these parameters.

The default configuration for a CS/3x00 port is:

UseDTRin = (Ignore,OnRTS)

FlowCtrlTo = Xon_Xoff

Modem Dial-In Configuration

To configure a dial-in modem so that modem hangup puts the communications server port in listen mode, and to use the second control input as this hangup signal, configure the UseDTRin parameter as follows:

SETDefault !7 -TERM UseDTRin = (AsDTR, OnDTR)

Since DTR no longer shares the RTS input, CTS/RTS can be used for flow-control. The following commands disable XON/XOFF flow-control and enable CTS/RTS in both directions:

SETDefault !7 -TERM FlowCtrlFrom = CTS_RTS

SETDefault !7 -TERM FlowCtrlTo = CTS_RTS

With these parameter settings, hardware flow control is enforced in both directions, and the modem can signal the communications server on hangup by dropping the second control input (usually the desired behavior for a dial-in modem). Although this explanation refers to that input as DTR, it would be labeled DCD on the modem.

The single output control signal from the CS/3x00 is used for CTS/RTS flow-control, as determined by the FlowCtrlFrom parameter. The communications server cannot use this signal to notify the modem that the network connection has terminated or the port has entered Listen mode, requiring dial-in users to hang up their modems after logging out.

This setting requires a modified adapter, wired according to Table--8 on page-40.

Modem Dial-Out Configuration

If a modem is to be used for dial-out, the communications server must be able to signal the modem that the network connection has been lost. In this case, the communications servers one output control signal must be configured to indicate connection state rather than flow control. Hardware flow control can be used in the other direction:

SETDefault !7 -TERM FlowCtrlFrom = None

SETDefault !7 -TERM FlowCtrlTo = CTS_RTS

SETDefault !7 -TERM UseDCDout = (OnConnection, NoToggle)

In addition, the UseDTRin parameter must be configured so the communications server allows a network connection to the modem while the modem is idle:

SETDefault !7 -TERM UseDTRin = (AsDCD, OnDTR)

In this configuration, the communications server uses its single output control signal to indicate when a network connection has been made to the port. Hardware flow control is used in only one direction. This example turns off flow control completely for incoming data, but XON/XOFF flow-control could be enabled.

This setting requires a modified adapter, wired according to Table--9 on page-40.

Dial-In/Dial-Out Configuration

If a modem is to be used for both dial-in and dial-out, the UseDCDout and UseDTRin parameters must be configured for the modem to answer incoming calls and for the communications server to accept network connections:

SETDefault !7 -TERM UseDCDout = (AlwaysAssert, ToggleonDisc)

SETDefault !7 -TERM UseDTRin = ((AsDCD, OnDTR)

Since the CS/3x00 output control signal is used as a modem hangup indication, it cannot be used for flow control. There are two input control signals, so hardware flow control can be configured in that direction (that is, the modem can flow-control the communications server):

SETDefault !7 -TERM FlowCtrlFrom = None

SETDefault !7 -TERM FlowCtrlTo = CTS_RTS

In this configuration, the communications server keeps the control output signal active, indicating to the modem that it should accept incoming calls (dial-in). When the port enters listen mode, as when a network-initiated connection (dial-out) is broken, the communications server toggles its output control to signal the modem to hang up. Hardware flow control is used in only one direction.

RS-232 Interface Adapters

The use of both input control lines, as described in the previous sections, requires the use of specially wired adapters. Table--8 and Table--9 describe the wiring needed to support dual-input configurations. Although the description in Configuration Examples on page-38 refers only to modem attachment (DCE devices), dual-input configurations can also be used for attachment to DTE devices (such as PCs). The wiring tables cover both types of attachment.

The signal names in the tables see the DB-25 connector, not the CS/3x00 50-pin connector. For example, when the communications server output is being used as DTR for attachment to a modem, it is labeled DTR. When it is used as DCD for attachment to a DTE, it is labeled DCD, and when it is being used for flow control, it is labeled RTS or CTS.

Regardless of the connector used, behavior of the control output (RJ-12 pin 1) is determined by the FlowCtrlFrom and UseDCDout parameters, while interpretation of the control inputs (RJ-12 pins 3 and 6) is determined by FlowCtrlTo and UseDTRin.

Table--8 and Table--9 describe adapter connections between RJ-12 pins and DB-25 pins. Many RS-232 interface adapters provide connections to RJ-45 cables rather than RJ-12 cables. You can still use an RJ-12 cable with an RJ-45 adapter, fitting the six-pin RJ-12 cable into the middle six pins of the eight-pin adapter. In this case, RJ-45 pins 1 and 8 are not connected, and RJ-12 pins 1 through 6 correspond to RJ-45 pins 2 through 7.

If you use an RJ-45 adapter, add one to the RJ-12 pin numbers in Table--8 and Table--9.

Many cabling vendors provide custom wiring services. At least one wiring supplier (MOD-TAP®) provides prewired adapters for each of the four configurations described in Table--8 and Table--9. MOD-TAP part numbers are shown in Table-10. The MOD-TAP adapters are actually RJ-45 adapters, and any wiring information provided with them may see RJ-45 pin numbers, which are one greater than RJ-12 pin numbers.

Appendix C, Audit Trail Messages

You can send audit trail messages to any UNIX server running the syslogd protocol, as well as to an RBCS server or an NCS using the proprietary 3Com FAP protocol. For information on configuring the syslogd protocol on your communications server, see Configuring Your Server to Generate Audit Trail Messages on page-34 of these release notes. Table-11 shows the syslogd priority codes associated with each audit trail message.

Reference Guide Updates

This section describes changes and additions to the Multiprotocol Communications Server Reference Guide, May 1994.

Chapter 1, Commands

The COpy, ForMat, DiskFile, PortMonitor, RemoveFile, and ReName commands have been added, and an option has been added to the TELnet command.

COpy

Syntax

COpy :<src_filename> :

Minimum Privilege Level

Network Manager

Default

<dest_filename> is the same as <src_filename>

Description

The COpy command allows the network manager to copy boot image and configuration files between a communications servers local diskette and a remote host. It cannot perform a local-to-local or remote-to-remote copy.

Directories copied to a remote host cannot be used on a FAP or FTP-based system.

Because this command is based on TFTP, the filename must exist on the remote host before this command is issued.

Values

<ipaddr> The IP address of the remote TFTP server. For the communications server, the local diskette is assumed.

<src_filename> The name of the file to copy. On the remote server, you can specify a pathname using a forward slash (/) as the directory separator. If you do not specify a directory name, the default directory is assumed. You cannot specify a path on the communications server, but you can copy an entire subdirectory by specifying it instead of a file.

<dest_filename> The destination filename (optional). If not specified, assumed to be the same as <src_filename>.

You can also specify the filename on the remote server using the two special characters @M and @m. During transfer, @M is replaced by the MAC address of the communications server. @m is replaced by the last six characters of the MAC address of the communications server. You can use these characters to create directories identifying different communications servers.

Example 1

To save a copy of defined macros onto a TFTP server by copying the file named macros:

COpy macros 129.232.19.5:3Com/@M

Copying a:macros to 129.232.19.5:/home/rbcs/3Com/080002039281

17408 bytes transmitted. File transfer complete.

Example 2

To back up existing configuration files onto a TFTP server:

COpy * 129.232.19.5:3Com/@m/

Copying * to 129.232.19.5:/home/rbcs/3Com/039281

..15872 bytes of siodiags transmitted.

.....40960 bytes of sio30163 transmitted.

.512 bytes of fxfer transmitted.

DiskFile

Syntax

DiskFile

Minimum Privilege Level

Network Manager

Default

<path> is the root directory

Description

The DiskFile command displays a listing of all files in a root directory or subdirectory on the local floppy device. The command is valid only when the configuration file source is set to local floppy.

<path> can be either a configuration filename or a subdirectory name.

Example 1

List all valid files under the root directory:

DiskFile

binary siodiags sio30163 global MACROS/

tcp ip rtm arp alias

CONFIG/ USRDIR/ NSNAMES/ DIR_FILE/ IS/

ES/ TERMCAPS/ KEYMAP/ lpdp

Example 2

List existing macros:

DiskFile macros

schedule callin test

ForMat

Syntax

ForMat

Minimum Privilege Level

Network Manager

Description

The ForMat command performs a high-level format on the disk in the floppy drive. Before using this command, perform a low-level format using the monitor mode fo command or the format command on a PC.

When you enter this command, the following prompt appears:

Do you really want to format the disk? (y/n)

Type y to format the disk.

LPQ

Syntax

LPQ [-P<printer>] [-l]

Parameters in this command are case-sensitive. You must enter them exactly as shown.

Default

<printer> is the printer set for the port by the -LinePrinter DefPRinter parameter.

Description

The LPQ command displays the content of a printer queue.

<printer> is the name of a remote printer. If you do not specify the -P option, the ports default printer is used, as specified by the SET or SETDefault -LinePrinter DefPRinter command.

If you specify the -l (lowercase L) option, queue information is displayed in long format, which includes the name of the host where the job originated.

The content and format of print queue information are determined by the lpd program running on the remote host.

LPR

Syntax

LPR [-P<printer>] [-#<copies>] [-C<class>] [-J<job>]

[-T<title>] [-i] [{ -1 | -2 | -3 | -4 }]

[-w<cols>] [-h] [-p | -l | -t | -n | -d | -g | -v | -c | -f]

Parameters in this command are case-sensitive. You must enter them exactly as shown.

Default

<printer> is the printer set for the port by the -LinePrinter DefPRinter parameter.

Description

The LPR command creates a print job in a remote spooling area, waiting for the target printer to become available. Each print job consists of a data file and a control file.

When you enter an LPR command, a connection to the target printer spooler is initiated. If the connection is established successfully, a one-minute timeout is set, and the following message is displayed:

Escape to local PC and send the print file

Once the first character is detected, a five-second timeout is set. A print job may fail if no data is received in one minute after the LPR command is entered or if no data is received in five seconds after the previous received data byte. The ECM character and the break character are ignored during data transfer.

A control file containing all user-specified options is transferred after the specified <filesize> bytes of data are transferred. The print request may fail if you provide the wrong <filesize>.

The spool area is managed by the lpd program running on a remote host. The address of the host is defined by the ADD -LinePrinter RemotePRinter command.

Values

-P<printer> The target printer spooler. If you do not specify this option, the ports default printer is used. You select the default printer using the SET or SETDefault -LinePrinter DefPRinter command.

-#<copies> The number of copies to print. The default is 1.

-C<class> The job classification on the header page. The default classification is the system name, set by the SETDefault -SYS SysNAMe command. If SysNAMe is not set, the default class is set to csxxxxxx, where xxxxxx is the last three hexadecimal bytes of the communications servers MAC address.

-J<job> The job name on the header page. If not specified, <filename> is used instead. If you do not specify a filename, stdin is used instead.

-T<title> Title. The default is the filename.

-i The number of space characters in the output. If -i is specified without an <indent> value, the number of space characters is set to 8. If -i is not specified, the output is not indented.

-1 Mounts the specified file on font position 1, 2, 3 or 4.

-2

-3

-4

-w<cols> Page width.

-h Suppresses printing of the header page.

The following filter options notify the line printer spooler that the data file is not a standard text file. The spooling daemon uses the appropriate filters to print the data.

-p Use pr to format the files.

-l (lowercase L) Print control characters and suppress page breaks.

-t The file contains troff binary data.

-n The file contains data from ditroff.

-d The file contains data from tex.

-g The file contains standard plot data produced by plot routines.

-v The file contains a raster image.

-c The file contains data produced by cifplot.

-f Interpret the first character of each line as a standard FORTRAN carriage control character.

If no filter option is given, the string %! as the first two characters of the file indicates that it contains PostScript commands.

For some printers, certain filter options may be unavailable or inapplicable.

<filesize> The size of the input file. This argument is required. An incorrect <filesize> may result in print failure. <filesize> should reflect the actual file size on the local disk; no CR/LF translation should be done in the ASCII transfer mode. CR/LF translation should be done instead by the LPDP server. The communications server does not perform CR/LF translation in either server mode or client mode.

<filename> If you do not specify a filename, stdin is used.

LPRM

Syntax

LPRM [-P<printer>] {- | <job#> } Default is the printer set for the port by the -LinePrinter DefPRinter parameter. DescriptionThe LPRM command removes a job or jobs from a printers queue. Since the spooling directory is protected from users, LPRM is normally the only way you can remove a print job. To provide security, a print job can be removed only by an LPRM command entered on the same communications server port that initiated the print job. The network manager cannot remove other users print jobs on the remote host.A user name is composed of the system name assigned by the -SYS SysNAMe parameter and a port number. For example, a user on port 1 of a communications server named bangle has a user name bangle_1 for the print job. This name appears on the header page. -P specifies the queue associated with a particular printer. If you do not specify this option, the ports default printer is used. The - parameter removes all jobs owned by a port. You can remove a specific print job by supplying its job number as an argument. To find a job number, use the LPQ command.LPRM reports the names of any files it removes, and is silent if there are no applicable jobs to remove.PortMonitorSyntaxPortMonitor ! [Ascii | Hex

Minimum Privilege Level

Network Manager

Default

Hex

Description

The PortMonitor command displays data transmitted and received on the target ports serial line in either ASCII or Hex mode.

In ASCII mode, all 128 ASCII characters are displayed. For example, 0x1B is shown as <ESC> and 0x33 is shown as 3. Nonprintable characters are displayed as *.

In Hex mode, the display is in two columns. The first column displays the data in hexadecimal. The second column displays all printable characters, with nonprintable characters represented by a period. In both modes, a carriage return or carriage return-line feed pair causes the display to start on a new line.

The command is successful if the indicated port is valid, is not already being monitored, and is not monitoring another port. Otherwise the command is unsuccessful. Monitor port data is displayed until the user on the monitoring port types a break character.

An audit message is sent when a monitoring session is started and when one is terminated. The message type is PM. The message includes the monitored and monitoring ports and either START or END.

Error Messages

Port !<port> already being monitored.

A port can be monitored by only one port at a time.

Port !<port> is monitoring another port.

A port can monitor only one port at a time.

This port is being monitored.

A port that is being monitored cannot monitor another.

You cannot monitor this port.

A port cannot monitor itself.

RemoveFile

Syntax

RemoveFile <filename>

Minimum Privilege Level

Network Manager

Default

No default

Description

This command allows a network manager to delete files from a local floppy. The command is valid only when the configuration file source is set to local floppy.

ReName

Syntax

ReName <path> <oldname> <newname>

Minimum Privilege Level

Network Manager

Default

No default

Description

The ReName command changes the name of a file in a subdirectory on the local floppy drive. The path is not case-sensitive. The command is valid only when the configuration file source is set to local floppy.

Example

Change the name of the schedule macro to dosched:

ReName macros schedule dosched

TELnet

The following modification has been made to the existing TELnet command.

Syntax

TELnet [!<port>] <address | name> [,<address | name>] [-d]

[-] ["<session label>"] [ECM]

Description

If the new -d command line option is present, TNOptionDebug is turned on for this session, and Telnet option negotiations are displayed as they occur. If -d is absent, debugging depends on the state of the TNOptionDebug parameter.

Chapter 5, CLNP Service Parameters

The correct syntax for SETDefault -CLNP CONTrol is:

Chapter 9, IP Service Parameters

When you use the NETaddr parameter, you can now assign an IP subnet address consisting of all zeros.

The correct syntax for SETDefault -IP CONTrol is:

SETDefault -IP CONTrol = EXTended | NoEXTended

Chapter 13, PPP Service Parameters

When you use the ADDRess and ADDRessList parameters, you can now assign an IP subnet address consisting of all zeros.

The correct syntax for SETDefault -PPP LineCONTrol is:

SETDefault [!<portlist>] -PPP LineCONTrol = Enable | Disable

Chapter 14, RIPIP Service Parameters

The correct syntax for SETDefault -RIPIP CONTrol is:

SETDefault -RIPIP CONTrol = Listen | NoListen

Chapter 15, SLIP Service Parameters

When you use the ADDRess and ADDRessList parameters, you can now assign an IP subnet address consisting of all zeros.

The SHow -SLIP CONFiguration display has a new column, Session Address. This column displays the IP address used for the active session on the port. If no session is active, it displays - -.

The correct syntax for SETDefault -SLIP LineCONTrol is:

SETDefault [!<portlist>] -SLIP LineCONTrol = Enable | Disable

Chapter 16, SNMP Service Parameters

The correct syntax for the COMmunity parameter is:

ADD -SNMP COMmunity "<com name>" [TRiv] [RO | RW] [GEnr | AUth |

ALl | NOne]

DELete -SNMP COMmunity "<com name>"

SHow -SNMP COMmunity

where <com name> is the commmunity string. The correct syntax for the MANager parameter is:

ADD -SNMP MANager "<com name>" <IP address>

DELete -SNMP MANager "<com name>" <IP address>

SHow -SNMP MANager

Chapter 17, SYS Service Parameters

The GRoup parameter has no default.

In the SHow -SYS STATistics command, the Day option now summarizes the average load for the prior 16 hours rather than 24 hours.

The following parameters related to Network Time Protocol and the syslogd protocol have been added to the SYS Service.

LogServerProt

Syntax

SETDefault -SYS LogServerProt = Fap | Syslogd

SHow -SYS LogServerProt

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

Fap

Description

The LogServerProt parameter determines whether audit messages are sent to the syslogd well-known port using the FAP protocol or UDP.

MacroAuditLevel

Syntax

SHow -SYS MacroAuditLevel

Minimum Privilege Level

Network Manager for both SHow and SETDefault

Default

Info

Description

The MacroAuditLevel parameter sets the priority level of audit messages generated by the macro keyword audit. This parameter is significant only when LogServerProt is set to Syslogd and LogServerAddr is set to a valid IP address.

NetworkTimeSource

Syntax

SETDefault -SYS NetworkTimeSource = NetMap | NTP | NOne

SHow -SYS NetworkTimeSource

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

NetMap

Description

The NetworkTimeSource parameter determines the method used to synchronize the time-of-day clock. A value of NetMap means time is set by NetMap packets and NTP packets are ignored. A value of NTP means time is set by NTP packets and NetMap packets are ignored. A value of NOne means time is not synchronized.

NTPBackupSrvr

Syntax

SETDefault -SYS NTPBackupSrvr <ipaddr>

SHow -SYS NTPBackupSrvr

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

0.0.0.0

Description

The NTPBackupSrvr parameter specifies the IP address that NTP uses as the backup time server. The communications server uses this address if the primary time server address is 0.0.0.0 or unreachable, or if the address does not respond to NTP packets. The communications server then transmits NTP packets to NTPBackupSrvr as long as its address is not 0.0.0.0 or unreachable and the communications server receives NTP packets in response. If NTPBackupSrvr is also 0.0.0.0 or unreachable or does not respond, then NTP uses any NTP server that is broadcasting NTP packets as its time server.

If NetworkTimeSource is not set to NTP, the value of this parameter is meaningless.

NTPPollInterval

Syntax

SETDefault -SYS NTPPollInterval = <number> (120 minutes)

SHow -SYS NTPPollInterval

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

Description

NTPPollInterval defines the longest interval at which the communications server sends NTP packets to the primary and backup time servers. After reset or reconfiguration, the communications server initially sends NTP packets to each server at one-minute intervals. This interval can increase automatically up to the value of NTPPollInterval if the communications server remains closely synchronized with network time.

If NetworkTimeSource is not set to NTP, the value of this parameter is meaningless.

NTPPrimarySrvr

Syntax

SETDefault -SYS NTPPrimarySrvr <ipaddr>

SHow -SYS NTPPrimarySrvr

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

0.0.0.0

Description

The NTPPrimarySrvr parameter specifies the IP address that NTP uses as the primary time server. If NetworkTimeSource is set to NTP, the communications server transmits NTP packets to this address and uses the response to set the time, provided the address is not 0.0.0.0 or unreachable and the address responds to NTP packets. Otherwise the communications server resorts to the NTPBackupSrvr or any NTP server that is broadcasting NTP packets.

If NetworkTimeSource is not set to NTP, the value of this parameter is meaningless.

NTPStatus

Syntax

SHow -SYS NTPStatus

Description

The NTPStatus parameter displays information about the current status of NTP on the communications server. The display includes the address of the NTP server (peer) which was the source of the latest time update, the mode of the server (client or broadcast), the version of NTP the peer is using, the stratum of the system (distance from the communications server to a primary time source), the logarithm base 2 of the precision of NTP calculations on the communications server, the last time an NTP packet was received from the peer, the last time an adjustment was made to communications server time, and a list of the five last times an adjustment greater than 30 minutes was made to communications server time.

Example

SHow -SYS NTPStatus

system peer address: 129.213.48.7

system peer mode: client

system peer version: 2

stratum: 4

precision: -4

reference time: B236DCF1.526E8000 Fri Sep 30 11:52:33 1994

last adjustment: B236D763.74394000 Fri Sep 30 11:28:51 1994

no major adjustments

SyslogFacCode

Syntax

SHow -SYS SyslogFacCode

Minimum Privilege Level

Network Manager for SETDefault

Default

Loglocal7

Description

The SyslogFacCode parameter determines the facility code used for audit messages sent by syslogd. Possible values are Loglocal0 through Loglocal7. This parameter is meaningful only when LogServerProt is set to Syslogd and LogServerAddr is assigned a value other than 0.0.0.0.

SyslogTHreshold

Syntax

SHow -SYS SyslogTHreshold

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

Info

Description

When LogServerProt is set to Syslogd and LogServerAddr is set to a valid address, the SyslogTHreshold parameter sets a threshold above which audit trail messages are sent to the audit server based on their priority level. The value of SyslogTHreshold is the lowest priority message that is sent. If you set SyslogTHreshold to Info, all messages are sent. If you set SyslogTHreshold to Emerg, only messages with priority LOG_EMERG are sent.

The communications server does not use Debug priority level.

Chapter 19, TCPAPPL Service Parameters

When you use the PORtMap parameter, you can now assign an IP subnet address consisting of all zeros.

Chapter 20, TERM Service Parameters

The BAud parameter has been given the new values 64k and 76.8k. The ECHOData parameter has been given the new value Auto or Fixed. The PortMonStat, PvcDcdAction, and TNOptionDebug parameters have been added to the TERM Service.

BAud

The BAud parameter can now take on the values 64k and 76.8k.

ECHOData

Syntax

SETDefault [!<port>] -TERM ECHOData = ([OFF | ON], [Auto | Fixed])

Default

Auto

Description

A value of Auto means that the on-off setting of ECHOData can change according to the final state of Telnet Echo negotiations. A value of Fixed means that the on-off setting of ECHOData does not change no matter what the result of Telnet Echo negotiations. Setting ECHOData to (OFF, Fixed) disables echo by the communications server.

PortMonStat

Syntax

SHow -TERM PortMonStat

Minimum Privilege Level

Network Manager

Description

The PortMonStat parameter shows all ports being monitored and the ports monitoring them. If the monitoring port is a network management port reached by a Telnet or VTP connection, it is shown as Network Manager UI. The parameter also displays the number of bytes transmitted, received, and lost in each direction.

PvcDcdAction

Syntax

SET !<port-list> -TERM PvcDcdAction = BeforeNetwork | AfterNetwork

SETD !<port-list> -TERM PvcDcdAction = BeforeNetwork | AfterNetwork

SHow !<port-list> -TERM PvcDcdAction

SHow !<port-list> -TERM DefaultParams PvcDcdAction

Default

BeforeNetwork

Description

When UseDCDout is set to OnConnection, the PvcDcdAction parameter controls when the DCD circuit is raised during the establishment of a PVC connection. If it is set to BeforeNetwork (the default), the circuit is raised before the network connection is complete. If it is set to AfterNetwork, DCD is raised only after the network connection is fully established.

TNOptionDebug

Syntax

SET -TERM TNOptionDebug = Off | On

SETDefault [!<portlist>] -TERM TNOptionDebug = Off | On

SHow [!<portlist>] -TERM TNOptionDebug

SHow [!<portlist>] -TERM DefaultParams TNOptionDebug

Minimum Privilege Level

User for SET and SHow

Network Manager for SETDefault

Default

Off

Description

The TNOPtionDebug parameter determines whether Telnet option negotiations are displayed as they occur.

Chapter 21, TN3270 Service Parameters

The KermitEchar parameter has been added to this service.

The CANCEL, PRINT, and XPARENT keys have been added to the KeyMapEntry parameter. The default key value for PA1 has been changed from [Ctrl]+X to [Ctrl]+V. This change does not affect existing keymaps that include a PA1 definition, only keymap files that do not have PA1 defined.

KermitEchar

Syntax

SET -TN3270 KermitEchar = <char>

SETDefault [!<portlist>] -TN3270 KermitEchar = <char>

SHow [!<portlist>] -TN3270 KermitEchar

Minimum Privilege Level

User for SET and SHow

Network Manager for SETDefault

Default

13 (^M)

Description

The KermitEchar parameter changes or shows the Kermit end packet character. You can set the character by its control-key combination, indicated by a caret (^), or by its ASCII value in decimal. The default is 13, meaning the [Ctrl]+M key combination. The SHow -TN3270 KermitEchar command displays this value as ^M.

When the communications server detects KermitEchar in the terminal input, it transfers a Kermit packet to the remote host. KermitEchar should be the same as the block-end character set on the local PC and the IBM host.

Example 1

To change KermitEchar to [Ctrl]+N on the current active port:

SET -TN3270 KermitEchar = 14

SET -TN3270 KermitEchar = ^N

Example 2

To display KermitEchar for port 3:

SHow !3 -TN3270 KermitEchar

KermitEchar = ^N

KeyMapEntry

CANCEL.

The CANCEL key has been added to the existing keymaps. If you press the CANCEL key during a TN3270 session, all print screen requests originating from the current session are removed from the print queue. The default values are Ctrl-U for the label and ^U for the key string.

Example 1

To add the CANCEL key value to the current keymap, or to change the value of CANCEL:

ADD -TN3270 KeyMapEntry CANCEL "Ctrl-C" "^C"

Example 2

To return the CANCEL key to the default value:

DELete -TN3270 KeyMapEntry CANCEL

Using a default label "Ctrl-U" string "\025" for key CANCEL

PRINT.

The PRINT key has been added to the existing keymaps. If you press the PRINT key during a TN3270 session, the current TN3270 screen is printed on the designated printer. The default values are Ctrl-B for the label and ^B for the key string.

Example 1

To add the PRINT key value to the current keymap, or to change the value of PRINT:

ADD -TN3270 KeyMapEntry PRINT "Ctrl-P" "^P"

Example 2

To return the PRINT key to the default value:

DELete -TN3270 KeyMapEntry PRINT

Using a default label "Ctrl-B" string "\002" for key PRINT

XPARENT

The XPARENT key has been added to the existing keymaps in order to toggle the data transfer mode. The default values are Ctrl-X for the label and ^X for the key string.

The first XPARENT keystroke puts the current TN3270 session in transparent mode. During transparent mode, data coming from a TN3270 server is transferred to the PC without standard TN3270 data processing, and data coming from the PC is transferred to the TN3270 server without translation.

Termination of transparent mode is usually automatic. The session state returns to normal data mode after file transfer is complete or after a fatal error occurs. If needed, a second XPARENT keystroke also returns the session to normal data mode.

Because the XPARENT default is [Ctrl]+X, the default key value for PA1 has been changed from [Ctrl]+X to [Ctrl]+V. This change does not affect existing keymaps that include a PA1 definition, only keymap files that do not have PA1 defined.

Example 1

To add the XPARENT key value to the current keymap, or to change the value of XPARENT:

ADD -TN3270 KeyMapEntry XPARENT "Ctrl-T" "^T"

Example 2

To return the XPARENT key to the default value:

DELete -TN3270 KeyMapEntry XPARENT

Using a default label "Ctrl-X" string "\030" for key XPARENT

Example 3

To display the current keymap value:

SHow -TN3270 KeyMapEntry

-----------------------Keymap mapping (vt100)----------------------

3270 Key Label String 3270 Key Label String

UP Up arrow \EOA LEFT Left arrow \EOD

PRINT Ctrl-B ^B CANCEL Ctrl-U \025

XPARENT Ctrl-X ^X

PortKeyMap

To delete an assignment, set the PortKeyMap parameter to the value UNDEFINE. If a TN3270 session is started on a port without a defined termcap, the TERMType parameter in the TERM Service is checked for a valid termcap name. If none is found, the communications server defaults to a VT102 termcap and an ANSI keymap.

TN3270TERM Service

To delete a PortTermCap assignment, set the PortTermCap parameter to the value UNDEFINE.

New Chapter, LinePrinter Service Parameters

Add the following chapter on the LinePrinter Service. These commands support the Line Printer Daemon Protocol (LPDP) running in client mode and the TN3270 print screen feature.

DefPRinter

Syntax

SET -LinePrinter DefPRinter = <name>

SETDefault [!<portlist>] -LinePrinter DefPRinter = <name>

SHow [!<portlist>] -LinePrinter DefPRinter

Minimum Privilege Level

User for SET and SHow

Network Manager for SETDefault

Default

No default

Description

The DefPRinter parameter sets the default printer for a port on a communications server. The default printer is used when the -P switch is not specified in an LPR, LPQ, or LPRM command.

The SETDefault command fails if the specified printer name is not defined in the remote printer list. Remote printers are defined by the ADD -LinePrinter RemotePRinter command.

Example 1

Set the default printer to image:

SETDefault !1-!10 -LinePrinter DefPrinter = image

Example 2

Set the default printer on the active port temporarily to the printer named postscript:

SET -LinePrinter DefPrinter = postscript

Example 3

Show the default printer:

SHow -LinePrinter DefPrinter

PORT NAME PORT NAME

-----------------------------------------------------------

0 None 1 image

2 postscript 3 image

30 hp1 31 hp1

HeaDer

Syntax

SETDefault !<printer_port> -LinePrinter HeaDer = Yes | No

SHow [!<printer_port>] -LinePrinter HeaDer

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

Yes

Description

The HeaDer parameter determines whether a header page is printed. It should be set to No for a PostScript printer. This parameter applies only to LPDP. The TN3270 print screen feature always prints a header page.

MaxPrintQueue

Syntax

SETDefault !<portlist> -LinePrinter MaxPrintQueue = <num> (0-20)

SHow [!<portlist>] -LinePrinter MaxPrintQueue

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

Description

The MaxPrintQueue parameter applies to the TN3270 print screen feature only. It limits the number of print jobs that can be queued for a printer. When a print queue reaches its MaxPrintQueue limit, additional print requests are rejected.

You can disable the designated print-screen printer by setting its MaxPrintQueue to 0. Jobs already in the queue are still printed out.

Example 1

Set the MaxPrintQueue size to 2 for the !1 and !10 printer ports:

SETDefault !1 !10 -LinePrinter MaxPrintQueue = 2

Example 2

Set the MaxPrintQueue size to 10 for the parallel port:

SETDefault !PRINTER -LinePrinter MaxPrintQueue = 10

Example 3

Display the current MaxPrintQueue value for the parallel printer port:

SHow !48 MaxPrintQueue

MaxPrintQueue = 10

PRinter

Syntax

ADD !<printer_port> -LinePrinter PRinter [ALL | <port> [{- | ,} !<port>] ]

DELete !<printer_port> -LinePrinter PRinter [ALL | !<port> [{- | ,}

!<port] ]

SHow [!<printer_port>] -LinePrinter PRinter

Minimum Privilege Level

User for SHow

Network Manager for ADD and DELete

Default

No default

Description

The PRinter parameter assigns a port to other ports as their designated printer. <printer_port> specifies the communications server port that has a printer attached.

The printer port can be either a serial port or a parallel port. All other port-dependent parameters under the TERM Service should be set according to the printer characteristics. You can assign a printer port to be an LPDP server and a designated printer for TN3270 ports at the same time.

A warning message is displayed if the specified printer port is not configured as a host port with fixed baud rate.

If you specify ALL after the ADD command, all ports, except the printer port itself and the parallel printer port, are assigned to the specified printer port. If you specify ALL after the DELete command, all ports assigned to the printer port are removed from the assignment list.

If a port specified in the ADD command already has a designated printer, the following message is displayed:

Warning: Port <port> is assigned to <printer_port>.

Reassign port <port> to printer <printer_port>? (y/n, def:n)

If you answer y, the new designated printer port overwrites the existing one.

This parameter is intended primarily for use with the TN3270 print screen feature. However, if users want to see local printers that support LPDP in server mode (providing print service to remote hosts), the network manager can set a port as a printer port by entering the ADD !<port> -LinePrinter PRinter command without arguments.

Example 1

Assign ports 2, 3, 4, 5, 6, 7, 8, and 9 to serial printer port 1:

ADD !1 -LinePrinter PRinter !2-!9

Example 2

Delete port 8 from serial printer port 1:

DELete !1 LinePrinter PRinter !8

Example 3

Display current printer and port assignments:

SHow -LinePrinter PRinter

PORT NAME QSIZE Header TN3270 Ports

---------------------------------------------------------------

!1 Area1 2 Yes !2-!7, !9

!10 Area2 2 Yes !11-!19

!12 lp 5 No

!48 port_48 10 Yes !20-!47

In this configuration, !8 does not have a designated printer, and printer port 12 has no ports assigned to it.

PrinterLineterm

Syntax

SETDefault !<portlist> -LinePrinter PrinterLineterm = CR | LF | CRLF

SHow [!<portlist>] -LinePrinter PrinterLineterm

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

CRLF

Description

The PrinterLineterm parameter determines the line termination string for the specified printer ports. It applies to the TN3270 print screen feature only.

If PrinterLineterm is set to CR, a carriage return is inserted at the end of each line. If PrinterLineterm is set to LF, a line feed is inserted at the end of each line. If PrinterLineterm is set to CRLF, a carriage return-line feed pair is inserted at the end of each line.

Example 1

Change the line termination string for printers attached to port 1 and port 10:

SETDefault !1,!10 -LinePrinter PrinterLineterm = LF

Display the PrinterLineterm setup for all printer ports on a CS/3x00:

SHow -LinePrinter PrinterLineterm

01: PrinterLineterm = LF

10: PrinterLineterm = LF

48: PrinterLineterm = CRLF

PRinterName

Syntax

SETDefault !<port> -LinePrinter PRinterName = <name>

SHow [!<port>] -LinePrinter PRinterName

Minimum Privilege Level

User for SHow

Network Manager for SETDefault

Default

port_xx, where xx is the port number

Description

This parameter sets and displays the name of a printer attached to the specified port. A printer name can be up to 10 characters long. It applies both to the TN3270 print screen feature and to LPDP running in server mode.

A valid printer port must be a host port with a fixed baud rate. A warning message is displayed if the specified !<port> is not a valid printer port.

If PRinterName is not set on a printer port, the default port_xx is used .

When LPDP is running in server mode, the printer queue name specified in LinePrinter Service commands is checked against the PRinterName on all ports. If no match is found, the command fails.

Example 1

Assign a name to a printer:

SETDefault !12 -LinePrinter PRinterName = lp

Example 2

Display the printer port name:

SHow !12 -LinePrinter PRinterName

PRinterName = lp

Example 3

Display all printer port names:

SHow -LinePrinter PRinterName

01: PRinterName = Area1

10: PRinterName = port_10

12: PRinterName = lp

48: PRinterName = port_48

PrintQueue

Syntax

FLush [!<portlist>] -LinePrinter PrintQueue [!<port>]

SHow [!<portlist>] -LinePrinter PrintQueue

Minimum Privilege Level

User for SHow

Network Manager for FLush

Default

All printer ports

Description

The PrintQueue command allows a user or network manager to monitor and manage print queues. It applies to the TN3270 print screen queue only.

The SHow command allows users to see the status of current print queues. The FLush command allows a network manager to remove all jobs from one or multiple printer queues, to remove all jobs from all printer queues, or to remove all print jobs issued from one port.

!<portlist> can include multiple printer ports. !<port> is the port where print requests-originate.

If a network manager enters the FLush command without specifying a printer port and a print request port, the following prompt is displayed:

Clear all the print queues? (y/n, def:n)

The command is executed only when the network manager answers y.

Example 1

Display current print jobs:

SHow -LinePrinter PrintQueue

PORT NAME STATUS QUEUE

-------------------------------------------------------

!1 Area1 busy !3,!2

!10 Area2 idle

!12 lp idle

!48 port_48 wait !25,!32,!8

Busy means the printer is busy printing. Idle means no job is printing or in the queue. Wait means no connection can be established to the printer. Wait may also mean that the printer is busy printing a job from another source, or that it is turned off.

Example 2

Remove all print jobs from port 48:

FLush !48 -LinePrinter PrintQueue

RemotePRinter

Syntax

ADD -LinePrinter RemotePRinter <name> <ipaddr>

DElete -LinePrinter RemotePRinter <name>

SHow -LinePrinter RemotePrinter

Minimum Privilege Level

User for SHow

Network Manager for ADD and DELete

Default

No default

Description

The RemotePRinter parameter defines a remote printer name and the IP address of the remote printer. It applies to LPDP running in client mode only. The maximum number of remote printers that can be defined on a communications server is 10.

Values

<name> A string up to 18 characters long.

<ipaddr> The IP address of the remote printer in dotted decimal format.

Example 1

Define a remote printer image:

ADD -LinePrinter RemotePRinter image 129.232.97.2

Example 2

Delete the remote printer remote:

DELete -LinePrinter RemotePRinter remote

Example 3

Show the defined remote printers:

SHow -LinePrinter RemotePRinter

Printer Name IP Address

----------------------------------

hp 129.232.97.6

lp 129.232.97.3

image 129.232.97.2