Chapter 4: Setting Up Common Configurations
This chapter includes several extended examples, or application notes, describing common RCS/4000 setups:
It also describes the procedures for the following:
The RCS/4000 can be configured to automatically connect a terminal to a host located anywhere on the network. This technique could be used in applications that require a user's terminal to communicate with one and only one host computer, perhaps running a specialized application program. This configuration closely models a terminal that is directly connected to a host, via a conventional serial interface. The following example shows how this can be done for the terminal connected to port 1.
A custom service configuration must be defined to support a direct connect. At the admin access level enter the following:
>add custom C1
The custom configuration that you define should be similar to this:.
Configuration name C1 Authentication none Capabilities user Terminal vt100 Restart Delay 1 Wait for keyboard hit no Display banner no One-key menus None Sessions Command for session 1: telnet 198.130.71.67
The IP address set in the telnet command (198.130.71.67 in the example) should be that of the target host system. The table below describes the service configuration options in detail. Once a service configuration has been defined, it must then be assigned to a port or range of ports. Enter the following:.
>set C1 1.
Option |
Description |
Configuration name (C0-C33) |
Define as C0 through C33. Must be different for each unique configuration. |
Authentication (none) |
Selecting none allows user to go directly to host system. Selecting user or admin requires a password before logging onto the host. |
Capabilities (user) |
Selecting user allows telnet and rlogin access. |
Terminal (vt100) |
Enter type appropriate for the user. |
Restart Delay (1) |
Specifies 1-second delay between ending a session and starting a new one. |
Display Banner (no) |
Login banner will not display when the terminal is first powered on or connected. |
One-key Menus (none) |
One-key menus are not used, since you want the user to automatically connect to the remote host, bypassing the RCS/4000 shell. |
Sessions |
Defines the command the RCS/4000 will executes to connect to the host: telnet or rlogin. If the host name has been added to the hosts list or if you are using DNS, you can use a host name instead of the IP address. The command shown in the example will establish a telnet session with the host whose IP address is 198.130.71.67. |
The RCS/4000 supports up to four sessions for each connected terminal. These sessions can be individually connected to any host on the network. The following example establishes three sessions for the terminal connected to port 1:
You must define a custom service configuration to support a connection with multiple sessions. Each port may have up to four sessions defined, allowing the user to enter the BREAK key to switch between the sessions. To define, enter the following at the admin level prompt:
>add custom C1
The custom configuration that you define should be similar to this:
Configuration name C1 Authentication user Capabilities user Terminal vt100 Restart Delay 1 Wait for keyboard hit no Display banner yes One-key menus None Sessions Command for session 1: shell Command for session 2: rlogin 198.130.71.12 Command for session 3: telnet 198.130.71.18
Once you define a service configuration, you must assign it to a port or range of ports. Enter the following:
>set C1 1
The terminal type determines how the screen is updated between session switches. Terminal modes that support multiple display pages (e.g., Wyse-50+; Wyse-60) will repaint the screen, restoring the state of the session at the previous switch. Most standard terminal modes (e.g., vt200; ansi) do not support multiple display pages and will only clear the screen on a session switch. If the selected terminal type does not support screen clearing, no screen update will occur on a session switch.
Option |
Description |
Configuration name (C0-C33) |
Define as C0 through C33. Must be different for each unique configuration. |
Authentication (user) |
Requires operator to enter user password before an active session begins. |
Capabilities (user) |
Selecting user allows telnet and rlogin access. |
Terminal (vt100) |
Enter type appropriate for the user. |
Restart Delay (1) |
Specifies 1-second delay between ending a session and starting a new one. |
Display Banner (yes) |
Identifies RCS/4000 unit to which operator is logging on. |
One-key Menus (none) |
No one-key menus are configured in this example. One-key menus could be defined and would be available to the user in the shell session (session 1) as shortcuts for commonly used commands. |
Sessions |
Defines what command the RCS/4000 will execute to connect to the host: telnet, shell or rlogin. If the host or nameserver has been defined, you can use a host name instead of the IP address. |
When you switch from one session to another and then return to the original session, the screen will either re-display the original screen or clear the screen. Whether the original session screen is re-displayed or the screen is cleared depends on the terminal type defined in your custom configuration. Only terminal types that support multiple page display can re-display the original screen. The terminal type must support a number of multiple pages equal to the number of sessions required. That is, if a user is switching between 4 sessions (the maximum number of sessions the RCS/4000 can support), the terminal must provide multiple page display support for at least 4 pages. Of the currently supported terminal types, only the Wyse 50+ terminal supports sufficient multiple display pages to support 4 sessions and, therefore, allows the original screen to be redisplayed after a switch when 4 sessions are configured. The Wyse 60 terminal supports up to 2 multiple display pages and so will re-display the original session if the user has only 2 sessions, but will clear the screen if the user has 3 or 4 sessions. All other supported terminal types will clear the screen when the user returns to the original session. (For a list of supported terminal types, see terminal types)
These directions show how to configure a modem on a serial port to allow users to dial-in and automatically start a slip, ppp, rlogin or telnet session. In this example, we will set up a hayes compatible modem on serial port 1.
set rtelnet 1 set speed 1 115200
Now connect to the modem with the following command:
telnet cuda1 9001
Assuming that cuda1 is the name of the RCS/4000 you are using, this will connect you to the modem attached to port 1.
*This parameter may vary on your modem. Motorola Lifestyle modems use \Q3 for this mode.
set speed 1 115200 set size 1 8 set parity 1 none set input 1 rtscts set output 1 rtscts
Configuration name C10
Authentication none
Capabilities user+net
Terminal vt100
Restart Delay 10
Wait for keyboard hit no
Display banner no
One-key menus None
Sessions
Command for session 1: (one of the following)
· ppp 198.130.71.15:198.130.71.213 (displayed when you enter show ip command)
· slip 198.130.71.213:198.130.71.15 (address assigned to the dial-in application)
· telnet <host name> or <IP address>
· rlogin <host name> or <IP address>
The commands shown will automatically start a service on the dial-in port as soon as the modem receives a call and connects to the remote (calling) modem.
set C10 1
save
The following example provides a quick step-by-step description of how to add a dial-out modem to the RCS/4000, including:
The following equipment is required before you can install and configure the dial-out modem:
In this example, a modem is being attached to port 1 of an RCS/4000 with a hostname cudasrv.
set rtelnet 1
This will set up the RCS/4000 to respond on tcp port 9001 to connect the telnet service to serial port 1. The tcp port number will change depending on the serial port to which you are connecting the modem. Each serial port has a tcp port associated with it. Serial ports 0 through 15 are associated with tcp ports 9000 through 9015, respectively.
set speed 1 115200
This sets the baud rate to 115200. Change this based on the type of modem you have. (Some modems may not be able to handle high DTE baud rates.)
save
There are two ways to access the modem through a host:
The quickest and easiest way to access the modem is by using the telnet command. However, this does not allow a device name to be associated with the modem, which might be required by some applications (e.g. terminal programs).
To access the modem via telnet, type:
telnet cudasrv 9001
cudasrv is the host name of the RCS/4000 and 9001 is the tcp port that the modem is attached to. The IP address of the RCS/4000 could be substituted for the host name.
You should now be able to type 'AT' commands to communicate with the modem. For example, to dial a number type:
ATDT555-5555
To show an example of how to access the modem via a reverse telnet connection and an application program we will use the 'tip' program and reverse telnet running on a Solaris system (see The rtn Utility, Chapter 7 for a full description of the rtn program).
The following steps show how this is accomplished.
rtn.soli -d /dev/modem1 -h cudasrv -p 9001
The "/dev/modem1" parameter in the above command is the name of the device that you want associated with the modem. You may name this anything you like.
modem1:\ :dv=/dev/modem1:br#38400:pa=none:el=^C^S^Q^D:ie=%$:oe=^D:
modem1 is the name of the device to be associated with the modem on the RCS/4000. Refer to the man pages of your system for an explanation of the other parameters.
tip modem1
This will connect you to the modem and you should now be able to type AT commands.
This section describes adding a pool of dial-out modems to the RCS/4000, including:
Make sure you have the following equipment:
In this example, modems are being attached to ports 1-3 of an RCS/4000 with the hostname cudasrv. These ports will be added to mpool 1.
set mpool 1-3 1
The parameter '1-3' specifies the ports to add to mpool 1, which is specified by the parameter '1'. These values may be different from the actual values that you are using, depending on what ports your modems are attached to and what mpool you would like to use.
set speed 1-3 115200
This sets the baud rate to 115200 on ports 1-3. You might want to change this, based on the type of the modem you have. (NOTE: Some modems may not be able to handle high DTE baud rates.)
save
There are two ways to access modems through a host:
The quickest and easiest way to access a modem in the pool is with the telnet command. However, this does not allow a device name to be associated with the modem, which might be required by some applications (such as terminal programs).
To access the modem through telnet, type:
telnet cudasrv 9101
cudasrv is the host name of the RCS/4000 and 9101 is the tcp port to which the modem pool is attached. The '91' in '9101' specifies an mpool and the '01' is the number of the mpool.
You should now be attached to the modem located on port 1. You can communicate with the modem by typing 'AT' commands. For example, to dial a number type:
ATDT555-5555
NOTE: To communicate to the modems attached to ports 2 and 3 issue additional telnet commands without terminating your session to port 1.
To access the modem in the pool with a reverse telnet connection and an application program, use the 'tip' program and reverse telnet running on a Solaris system. Do the following:
rtn.soli -d /dev/modem1 -h cudasrv -p 9101
The "/dev/modem1" parameter in the above command is the name of the device that you want associated with the modem. You may name this anything you like.
modem1:\ :dv=/dev/modem1:br#38400:pa=none:el=^C^S^Q^D:ie=%$:oe=^D:
'modem1' is the name of the device associated with the modem on the RCS/4000. Please refer to the man pages of your system for an explanation of the other parameters.
tip modem1
You should now be attached to the modem located on port 1. You can communicate with the modem by typing 'AT' commands. For example, to dial a number type:
ATDT555-5555
NOTE: To communicate to the modems attached to ports 2 and 3, issue additional rtn and tip commands.
The RCS/4000 provides on-demand network connectivity using point-to-point protocol (PPP). You can configure it to dial a remote system when a packet arrives for a specified remote site, and to disconnect the dialed line if it is idle for a specified amount of time.
In the above figure, whenever a machine on the local network needs to access data or systems on the remote network, the local RCS/4000 dials the remote RCS/4000, establishes the connection and keeps it alive as long as there is network activity between the two sites. This is transparent to the user.
This section describes how to configure the RCS/4000 using the dial on demand service. DOD provides "on-demand" network connectivity via PPP. DOD dials a remote system when a packet arrives for a pre-configured remote site. You will configure the local RCS/4000 (cuda1) and the remote RCS/4000 (cuda2).
On the Local RCS/4000
set speed 1 115200 set size 1 8 set parity 1 none set input 1 rtscts set output 1 rtscts set timeout 1 30 set def 1
Add the modem description and the corresponding chat script to the setup database. The chat script here describes the modem-specific conversation which must take place between the RCS/4000 and the modem in order to establish communication to any remote system. This could include initializing the modem and the dial string. (For more information on chat scripts, see Writing Chat Scripts.) For example:
[admin:1/7]>> add modem modem1 Enter the modem chat script : "" ATDT\T
sets the modem chat script to do the following:
The "\T" specifies: insert the phone number for the defined system here (see next section on setting up the system).
Enter the modem initialization string: AT
Now apply modem1 (the modem type you just defined) to a specific port that is to be used for dial-on-demand. Use the set command.
[admin:1/8]>> set modem 1 modem1
to set the modem type on port 1 to modem1.
Set up information about the remote system that you are dialing into. This would include the name of the system, the ports to use to dial to the remote system, the backoff time for dialout failures (see Bi-Directional Dial on Demand below for more information), and the login chat script.
The login chat script describes the system-specific conversation that must take place between the RCS/4000 and the remote system to establish the ppp service, once the modem has made the connection to the system.
Example:
[admin:1/9]>> add system remote71 Enter the ports to communicate through : 1 Enter the phone number to dial : 3485839 Enter backoff time (sec) (default 0) : 0 Enter the login chat script : Password: user >> "ppp 199.171.148.1:198.130.71.2"
The example sets up to connect to the remote system, remote71, using port 1, with the telephone number, 348-5839, and the login chat script as follows:
expect Password: send user expect >> (note: this is the prompt) send "ppp 199.171.148.1:198.130.71.2"
NOTE: The ppp command is the command that is run on the remote RCS to start ppp on the port that answers.
[admin:1/10]>> set dod 4
Enter system name : remote71
Enter remote IP address
(Enter 0 to automatically negotiate) : 198.130.71.2
Enter local IP address
(Enter 0 to automatically negotiate) : 199.171.148.1
Enter netmask in IP address format
(Enter 0 to automatically determine) : 255.255.255.0
Enter an interface name (e.g. 'ppp0') : ppp_remote71
Use Van Jacobsen header compression (y/n) : y
What kind of authentication should be used?
1 - Authenticate remote host using CHAP.
2 - Authenticate remote host using PAP.
3 - RCS/4000 must provide authentication to remote host.
4 - No authentication is required by either side.
Please select a number 1 - 4: 4
Remote IP address : 198.130.71.2
Local IP Address : 199.171.148.1
Subnet Mask : 255.255.255.0
Interface Name : ppp_remote71
Van Jacobsen header compression : on
Authentication Type : No authentication is required by either side
Are thes evalues correct (y/n) : y
Dial-on-demand interface dod4 added to the system.
Would you like to add a route for this interface? y
Enter the desination network (or 'default'): 198.130.71.0
The requested route was added.
[admin:1/12]>> save
On the Remote RCS/4000
set speed 2 115200 set size 2 8 set parity 2 none set input 2 rtscts set output 2 rtscts set def 2
Start some activity to the remote network to test the connection. On the local RCS/4000, enter the following command:
[admin:1/13]>> ping -c 60 198.130.71.20
The ping command will start dialing and establish a connection to the remote site.
To complete the setup, you need to setup proper routes on the local and remote systems. (For information on setting up routing, see ROUTING and Appendix B.)
The remote office and corporate headquarters may need a configuration where either side can initiate the dial-on-demand connection. This is done by setting up both a dial-on-demand service and the default service on the same port on both RCS/4000 units.
A dial-on-demand from the remote office will connect with the shell (default service) at the local office. Similarly, a dial-on-demand from the local office will connect with the shell at the remote office.
At the shell prompt, the login chat script initiates the PPP connection for the other end.
When setting up Bi-Directional Dial-on-Demand, you must configure the backoff time when adding the remote systems (for adding remote systems, see the SYSTEM command). The backoff time determines how long the RCS/4000 waits before retrying a failed dialout attempt. For uni-directional dial-on-demand configurations, this value should generally be 0 to specify no backoff.
For bi-directional configurations, one of the RCS/4000s must be configured to backoff in order to avoid the deadlock which would occur if both units dialed each other simultaneously (and continued to redial each other at regular intervals). Typically, one unit should be configured with a backoff time of 0, while the other unit should be configured with a backoff time approximately equal to the amount of time it takes for a DOD connection to be established. For asynchronous modems, this is in the neighborhood of about 30 seconds. For ISDN modems, this value should be in the neighborhood of about 5 seconds. Use a backoff time which is appropriate for your configuration.
Syslog can provide useful information for troubleshooting your dial-on-demand connection. Configure syslog to save data in a large buffer for easier debugging:
[admin:1/14]>> syslog config
Specify a remote loghost: <cr>
defaulting to <your host>
Do you wish to log messages to the local circular buffer?: yes
How many entries would you like in the circular buffer?(Max=3000): 100
[admin:1/15]>> save
[admin:1/16]>> reboot
...
[admin:1/1]>> syslog display
Depending on what the syslog display shows, check your modem and the remote modem speed, your login chat script, and the remote and local routes.
In the previous examples we used analog modems to dial in, dial out, or make an "on demand" connection. The same can be accomplished with an ISDN terminal adapter with an asynch communication port. This section describes how to set up a Motorola BitSurfrTM in place of an analog modem, including:
Make sure you have the following equipment:
To set up a terminal adapter, do the following:
NOTE: Network switch and Global parameters need to be entered only once - during initial terminal adapter powerup.
NOTE: Factory default configuration is used as a basis for further settings and therefore does not need to be reentered in order to change to another terminal adapter mode.
No additional commands necessary
Asynchronous Inverse Multiplexing Mode
AT%A2=3 AT@B0=2
You may now access the terminal adapter as you did a modem in the previous examples of a dial-in modem, dial-out modem or dial-on-demand routing.
(NOTE: only some RCS/4000 models have a synchronous WAN port. See Model Numbers)
The following example provides a quick step-by-step description of how to add an ISDN terminal adapter to the sync port of the RCS/4000, including:
Make sure you have the following equipment:
The following diagram illustrates using the RCS/4000 sync port and ISDN terminal adapters to route packets between isolated networks
We will first set up the terminal adapter in asynch mode.
Attach the terminal adapter to port 1 on the local RCS unit (cuda1). On the RCS, configure the following:
set rtelnet 1 set speed 1 115200
Now connect to the terminal adapter using the following command:
telnet cuda1 9001
You may now enter commands to configure the terminal adapter. To achieve proper ISDN operation, the Network switch and Global parameters must be set by the following commands to the terminal adapter: (Refer to ISDN documentation for your specific terminal adapter commands)
AT>F
Set Switch and Global parameters to factory default
AT!C0=0
Switch type - AT&T 5ESS
AT!C1=0
Switch version - AT&T Point-to-Point
AT!D3=255
Auto data TEI
AT!C6=x...x
Data SPID - Refer to ISDN service provider documentation
AT!N1=x...x
Directory number - Refer to ISDN service provider documentation
AT*!D3=255
Auto Voice TEI
AT>W>Z
Save switch parameters and restart the network
NOTE: Network switch and Global parameters need to be entered only once - during initial terminal adapter powerup.
Once the network settings are configured properly, you can restore the factory default configuration (which is usually sufficient) with the following commands to the terminal adapter:
AT&F0
Restore factory default profile 0
AT&D2
No DTR signal causes BitSurfr to hangup, used for port timeout
AT&C1
DCD on when BitSurfr establishes a connection
AT%A4=0
Line channel speed 64 Kbps
AT&M2
Synchronous Dial Mode - used at ISDN terminal adapter 1
AT&Z0=x...x
Store Dial number in register number 0
AT&W1
Save active profile to stored profile 1
AT>Z
Restore switch options and restart the network
NOTE: Factory default configuration is used as a basis for further settings and therefore does not need to be reentered in order to change to another terminal adapter mode.
After setting the terminal adapter to the factory default condition, issue the appropriate following commands to enter the desired sync mode.
To enter Clear Channel Synchronous Mode
AT%A2=0
To enter Synchronous Bonding Mode (enter both commands)
AT%A2=3 AT@B0=2
Ensure terminal adapter parameters are correct and return to the admin shell. ISDN terminal adapter 1 has been set up to automatically dial the stored number in register 0 when DTR is enabled (which occurs when the DOD connection is made e.g., pinging a remote host). ISDN terminal adapter 2 attached at the stored phone number location can be configured to answer the call by using the same command format but using AT&M1 in place of AT&M2.
AT&M1 Synchronous Pause Mode - used at ISDN terminal adapter 2
Once you have typed these commands and entered synchronous mode, move the terminal adapter over to be attached to the WAN port on the RCS/4000.
We will set up a dial on demand configuration on the local RCS/4000 (cuda1) and an automatic ppp session on the remote RCS/4000 (cuda2).
set wan interface RS232 set wan clock internal 128000 set timeout wan 30
This sets the baud rate to 128000. (ISDN terminal adapters support sync baud rates of 300-128000 bps.)
NOTE: If you change the WAN interface or clock, save and reboot the system for the WAN to work with the following commands.
save expert reboot
set wan interface RS232 set wan clock internal 128000 set ppp C2 33 Enter remote IP address : 199.171.148.1 Enter local IP address : 198.130.71.2 Enter netmask in IP address format : 255.255.255.0 Enter authentication type (chap|pap|none): none Use Van Jacobsen header compression (y/n): n Are these values correct (y/n): y
NOTE: If you change the WAN interface or clock, save and reboot the system for the WAN to work with the following commands:
save expert reboot
add system sync1 Enter the ports to communicate through : 33 Enter the phone number to dial : "" Enter the login chat script : ""
set dod 1 Enter system name : sync1 Enter remote IP address : 198.130.71.2 Enter local IP address : 199.171.148.1 Enter netmask in IP address format : 255.255.255.0 Enter authentication type (chap/pap/none) : none Use Van Jacobsen header compression (y/n) : n
add route 198.130.71.0 199.171.148.1 net 0
route add 198.130.71.0 199.171.148.11 1
NOTE: This command may vary depending on the OS running on apollo.
ping 198.130.71.20
VS Steady green DS Steady green CS Steady green TR Steady green RD Steady green TD Steady green
add route 199.171.148.0 198.130.71.2 net 0
route add 199.171.148.0 198.130.71.21 1
(NOTE: only some RCS/4000 models have a synchronous WAN port. See Model Numbers)
The following example shows how to configure the WAN ports on 2 RCS/4000s with a pair of CSU/DSUs to set up remote routing over the WAN.
Before you configure the WAN port, ask the following questions:
Generally, a CSU/DSU, ISDN terminal adapter or an external FRAD provides the clocking, so the clock should be set as external when such a device is being used. If two RCS/4000s are directly connected by a WAN port cable and no external device is involved then internal clocking is used.
The maximum speed for the WAN port is 2,048,000 bits/second. Unless an unacceptable error rate occurs at the speed due to the length of the cable or electrical interference, the speed should be set to 2,048,000.
Since this is a point-to-point connection, you need to know your remote IP address and your local IP address for this interface. The remote IP address on one side will be the local IP address on the other.
The type of physical interface is determined by the CSU/DSU or cable used to connect to the RCS/4000. Check the specifications for the CSU/DSU or cable to determine the appropriate settings. The possibilities are:
RS-232 EIA-530 RS-422 V.35
Using the RCS/4000 sync port to route packets between isolated networks as shown in the following WAN diagram:
Consider cuda2 (198.130.71.21) and cuda1 (199.171.148.11) are two RCS/4000s on two different networks. The two RCS/4000s are connected by means of a CSU (could be a modem eliminator or sync modems) which does the clocking.
Set up the WAN port for EIA-530 interface and external clock. If you change the WAN interface or clock, save and reboot the system.
[admin:1/2]>> set wan interface e530 [admin:1/3]>> set wan clock external
Setup ppp on the WAN port (make sure C9 - custom configuration - is not being used by any other ports; if so use any other custom configuration not being used). Select an IP address such that the local address is an address on the network.
Example:
Since cuda2 is on the 198.130.71.0 network the local address is 198.130.71.2, and since cuda1 is on the 199.171.148.0 network the IP address chosen is 199.171.148.1. This allows hosts on 198.130.71.0 net to access hosts on 199.171.148.1 network by using the ppp interface on cuda2.
As you will see, when configuring cuda1's sync port the remote and local IP addresses will be the opposite of cuda2.
[admin:1/4]>> set ppp C9 33 Enter remote IP address : 199.171.148.1 Enter local IP address : 198.130.71.2 Enter netmask in IP address format : 255.255.255.0 Enter authentication type (chap|pap|none): none Use Van Jacobsen header compression (y/n) : n Remote IP Address : 199.171.148.1 Local IP Address : 198.130.71.2 Subnet Mask : 255.255.255.0 Authentication Type : none Van Jacobsen header compression : off Are these values correct (y/n): y
On entering yes, ppp is started on the WAN interface. To set up routes for 199.171.148.0 network through the local ppp address :
[admin:1/5]>> add route 199.171.148.0 198.130.71.2 net 0
If you want to save the setup in the database for use during the next reboot, enter:
[admin:1/6]>> save
Set up the WAN port for EIA-530 interface and external clock:
[admin:1/2]>> set wan interface e530 [admin:1/3]>> set wan clock external
Set up ppp on the WAN port (make sure C9 - custom configuration - is not being used by any other ports; if so, use any other custom configuration not being used)
[admin:1/4]>> set ppp C9 33 Enter remote IP address : 198.130.71.2 Enter local IP address : 199.171.148.1 Enter netmask in IP address format : 255.255.255.0 Enter authentication type (chap|pap|none): none Use Van Jacobsen header compression (y/n): n Remote IP Address : 198.130.71.2 Local IP Address : 199.171.148.1 Subnet Mask : 255.255.255.0 Authentication Type : none Van Jacobsen header compression : off Are these values correct (y/n): y
To set up routes for 198.130.71.0 network through the local ppp address :
[admin:1/5]>> add route 198.130.71.0 199.171.148.1 net 0 [admin:1/6]>> save [admin:1/7]>> expert [expert:1/8]>> reboot
All other hosts on the 198.130.71.0 network should be setup to route to 198.130.71.2 to access any hosts on 199.171.148.0 network. Example:
dino# route add 199.171.148.0 198.130.71.2 1 add net 199.171.148.0: gateway 198.130.71.2 dino#
Similarly, all hosts on the 199.171.148.0 network should be set up to route to 199.171.148.1 to access any hosts on 198.130.71.0 network.
apollo> route add 198.130.71.0 199.171.148.1 1 add net 198.130.71.0: gateway 199.171.148.1 apollo>
Consider the same diagram, but instead of a CSU we use a cable (pinout shown in the diagram below) to connect the two RCS/4000 sync ports. Most of the setup will be the same, except the configuration part related to clock:
[admin:1/2]>> set wan clock internal 56000
The rest of the setup is the same.
2--------------3
14-------------16
3--------------2
16-------------14
4--------------5
19-------------13
5--------------4
13-------------19
6--------------20, 8
22-------------23, 10
7--------------7
8, 20----------6
23, 10---------22
15, 2----------17
11, 12---------9
17-------------24, 15
9--------------11, 12
EIA-530 Synch Back-to-back Cable
1/1>> admin Password: admin [admin:1/1]>> expert
[expert:1/6]>> prtr_test /dev/tty/32
This should print 10 lines of output.
1/1>> admin Password: admin [admin:1/1]>> expert
xon/xoff flow control
To change these characteristics, use the following commands:
set speed 4 19200 set size 4 7 set parity 4 even set stop 4 2 set output 4 rtscts
Save any changes to the configuration:
save
set rt 4 delete def 4
Use show port 4 to verify that the configuration is set to rtelnet and no default is set.
[expert:1/6]>> prtr_test /dev/tty/4
This should print 10 lines of output. See the section, Troubleshooting the serial printer if the output does not appear.
The RCS/4000 supports two different protocols for sending output to a printer:
The LPD protocol is the UNIX Line Printer Daemon protocol and is supported by all UNIX systems and Windows/NT.
Reverse Telnet is a protocol that will allow a port on the RCS/4000 to appear as a local device connected to a host on the network.
The following table compares the two print options: reverse telnet and the UNIX line printer daemon (lpd).
Reverse telnet |
lpd |
Setup requires more steps. |
Minimal setup on RCS unless using printer pool or serial ports; minimal setup on hosts. |
Less flexibility with multiple hosts. Denies connection if a shared printer is busy (or all printers in a pool are busy). |
Manages sharing of port or printer pool so that multiple hosts can queue print jobs. |
Allows host to enforce security. |
Allows any host on the network to connect and print. |
Host maintains accounting information. |
Maintains no accounting information. |
Use this option if ... |
Use this option if ... |
You need security and accounting. |
You want the RCS/4000 to act as a print server. |
The RCS/4000 can serve as a print server on a network. Print jobs can be sent to the RCS/4000 from any host on the network that supports the LPD protocol. This includes all UNIX systems and Windows/NT.
No setup is required to use a printer connected to the parallel port. For a printer connected to a serial port, the default service on the port must be deleted and the serial port must be configured to match the printer configuration (baud rate, flow control, ...). A printer pool may also be used with lpd. Setting up a printer pool is described below.
NOTE: If you do not delete the default service on a serial port, the default service will control the port and lpd will be unable to access it. Use:
delete default {portnum}
to configure a serial port for use with lpd.
The host system must be configured to use a remote printer. The steps involved vary depending upon the specific host system. However, in all cases the following information is required:
Use the print queue name for two purposes:
For examples, see the Sample configurations at the end of this section.
Use any name in either upper or lower case letters followed by the port number. The first letter of the printer name selects the default treatment of the data file. 'f' means that the data will be formatted text. Anything else means binary data. Serial ports are numbers 0-15. The parallel port is number 32.
The following special names are recognized:
Any other name ending in a sequence of digits is taken to mean the port whose number is specified by the digits.
Example
To specify a queue name selecting serial port 3, you could use any of the following:
port3 /dev/tty/3 3 f0003 my_favorite_port_is_3
A print job consists of control information and the data to print. The control information specifies how to print the data, including page parameters, fonts and data format.
The RCS/4000 supports printing of formatted or unformatted data. Unformatted data includes binary and PostScript.
The lpd protocol allows the host to send either the data or the control information first.
If the RCS/4000 receives the control information before the data file, it uses that information to format the data file.
If it receives the data file before the control information, it prints the file without the control information formatting and uses default file formatting. The host can control the default formatting with the queue name it uses (see the next section).
If you are using the RCS/4000 in a UNIX environment, the data file is usually sent before the control information. If you are printing both formatted and unformatted data, specify two queue names: one to support formatted data and the other to support unformatted data.
If you are using the RCS/4000 in a Windows NT environment, the control information is sent before the data file. Specify one queue name for your print jobs.
For examples, see the Sample configurations at the end of this section.
Once you have set up lpd, you can perform additional tasks on the RCS/4000, using the following commands:
NOTE: You should delete print jobs from the host. The host may resend print jobs if you delete them from the RCS/4000.
You may repeat these commands as many times as necessary.
This section describes setting up a remote printer with lpd in both the UNIX (AIX 4 or SunOS or DEC) and Windows NT and 95 environments.
To set up a remote printer with an AIX driver to print formatted text, do the following:
Name of QUEUE to Add linda HOSTNAME of remote server rcs-host Name of QUEUE on remote server fport32
where:
linda print queue name on host rcs-host name or IP address of the RCS/4000 fport32 send formatted job to parallel port
To set up a remote printer for Sun OS or DEC Alpha:
If you are printing both formatted and unformatted (binary or PostScript) data, set up a printer queue name for each.
Example-unformatted text
tom_lpt | tom lpd cuda test printer:\ :rm=cuda29:rp=printer:\ :sd=/var/spool/lpd.tom_lpt:\ :mx#0:
where:
tom_lpt
queue name for Sun OS
rm=cuda29:
remote machine (name or IP address of the RCS/4000) in /etc/hosts file
rp=printer:\
queue name for cuda 29 machine
sd=/var/spool/lpd.tom_lpt:\
set directory name for spooling
mx#0:
no maximum size for file to be printed
Example-formatted text
tom_fmt | tom lpd cuda test fprinter:\ :rm=cuda29:rp=fprinter:\ :sd=/var/spool/lpd.tom_fmt:\ :mx#0:
where:
tom_fmt
queue name for Sun OS
rm=cuda29:
remote machine (name or IP address of the RCS/4000) in /etc/hosts file
rp=fprinter:\
queue name for cuda 29 machine
sd=/var/spool/lpd.tom_fmt:\
set directory name for spooling
mx#0:
no maximum size for file to be printed
Before setting up a remote printer in the Microsoft Windows NT 3.51 environment, make sure you have installed Microsoft TCP/IP printing support.
To set up a remote printer in the Windows NT 3.51 environment, do the following:
Enter a printer name
Select a printer driver
Enter a description
Select "Other" for Print To.
Click OK.
NOTE: If the LPR Port does not appear on the dialog box, make sure you have installed Microsoft TCP/IP printing support.
Name or IP address of the RCS/4000.
Name of the printer on that machine (portn - where n is the RCS/4000 port number, e.g. port6).
Click OK.
Before setting up a remote printer in the Microsoft Windows NT 4.0 environment, make sure you have installed Microsoft TCP/IP printing support.
To set up a remote printer in the Windows NT 4.0 environment, do the following:
NOTE: If LPR Port option does not exist it means Microsoft TCP/IP Printing is not installed. To install, click Start, Control Panel, select Network and Services, highlight Server/workstation and click Add. From the list choose Microsoft TCP/IP Printing. This will require your installation CD.
Name or IP address of the RCS/4000
Name of the printer on that machine (portn, where n is the RCS/4000 port number, e.g., port6).
Click Close.
Printer driver
Printer name
Printer Shared or Not Shared
Print test page.
Click Next after each entry.
Before setting up a remote printer in the Microsoft Windows 95 environment, make sure you have installed it first in the Windows NT environment. An NT server is required.
To set up a remote printer in the Windows 95 environment, do the following:
\\servername\printername
or click Browse to select a server and then a printer. Click OK and click Next.
To print using reverse telnet:
> admin Password: admin
[admin:1/1]>> set rtelnet 32 port32 : tcp ports 9032 and 8032
[admin:1/2]>> save
To print from a remote host, use the supplied rtn application for that host. The following example is for a Motorola SVR4 system:
$rtn -d/dev/remote_lp -h198.130.71.113 -p9032 &
$ cat file_name > /dev/remote_lp
Setting up an rtn-based printer under AIX is a three step process: 1) If you have not already done so, set up an RCS/4000 parent device: 2) Add an RCS/4000 printer device; and 3) Add an RCS/4000 print queue for the printer device.
RCS/4000 Type RCS/4000 8-port terminal server IP Address or Host Name [leroy]
For serial printers, select the appropriate serial printer.
For parallel printers, select the rtn RCS/4000 Parallel Port option.
For serial printers, select the local Printer Attached to Local Host attachment type.
For parallel printers, select the rcs4000 Printer Attached to RCS/4000 Parallel port attachment type.
Then select the Printer Type.
The following example configures three serial printers attached to port 3,4, & 6 to a printer pool (ppool 1) on the RCS/4000.
1/1>> admin
Password: admin
[admin:1/1]>> set ppool 3-4,6 1 port3 added to ppool1 port4 added to ppool1 port6 added to ppool1
[admin:1/2]>> show ppool 1 ppool1 ------ port3 port4 port6
[admin:1/3]>> show rtelnet pool: ppool1 tcp port: 9106/8106
[admin:1/2]>> save
On the remote host to print from, use the supplied rtn application for your appropriate system. The following example is for a Motorola SVR4 system:
$ rtn -d/dev/remote_lp -h198.130.71.113 -p9106 &
NOTE: This connects to the first available printer in printer pool 1.
$ cat file_name > /dev/remote_lp
The configuration of a serial printer must match the port configuration on the RCS. Mismatches in this area are the most common cause of problems. Make sure the baud rate, character size, parity, and flow control settings all match.
No output
The most common reason for getting no output to the printer is a cabling problem. Try a null modem connector between the cable and the printer to see if this corrects the problem.
Lost data
Losing data that is sent to the printer is usually caused by the lack of flow control or a mismatch in the flow control settings between the printer and the RCS/4000. Be sure that the printer flow control is enabled (either RTS/CTS or XON/XOFF) and that the same type of flow control is enabled on the RCS/4000 port.
Output suddenly stops
If your printer prints some output (maybe a page or so) then suddenly stops, your printer may be using the DTR signal for flow control. Most DTE serial cables map the DTR signal to the DCD input signal on the RCS/4000 serial port connector. If the DCD signal is dropped, the RCS/4000 interprets this as a hangup and closes the connection, and terminating the print job.
This problem is best corrected by configuring the printer to not use DTR for flow control. If this is not possible then a cabling change can be made to have DCD wired high. This may mean that the RCS/4000 will not be able to determine when the printer has been turned off. In this case, the RCS/4000 cannot report the correct printer status and may try indefinitely to print on this port.
To upgrade RCS/4000 software, do the following:
Server running TFTP
filename of download image:
server name or IP address (return for default):
do you wish to reboot now? (y/n)
NOTE: The server may restrict access via TFTP to a particular directory such as /tftpboot. If this is the case, then the upgrade file from Systech must be copied into that directory. The filename given in response to the prompt "filename of download image:" is relative to the default tftp directory, so "/tftpboot/" should not be entered as part of the name.
This section describes copying configurations from the RCS/4000 to a server (uploading) and from the server to the RCS/4000 (downloading). For more information, see the flash_save and flash_update commands.
Before copying configurations, make sure you have the following:
To save (upload) a configuration to the server, do the following:
cd to the default TFTP directory: "cd /tftpboot"
create an empty file to receive the config "touch my_config.bdnl"
make the file writeable by everyone "chmod 666 my_config.bdnl"
Selection:
file name:
server name or IP address (return for default):
save complete.
To download a configuration from the server to the RCS/4000, do the following:
filename of download image:
server name or IP address (return for default):
do you wish to reboot now? (y/n)
Repeat Steps 1-9 for each RCS/4000 receiving a copy of the configuration.
BOOTP provides an address discovery feature; however, before it can "discover" the RCS/4000's IP address through a BOOTP request, you must configure BOOTP.
# ps -axc | grep bootp
On some systems, the command is:
# ps -ef | grep bootp
For ULTRIX:
bootp dgram udp wait /usr/etc/bootpd bootpd -i
For SunOS:
bootps dgram udp wait root /usr/etc/bootpd bootpd
The usual entries in /etc/services are:
bootps 67/udp bootpc 68/udp
Remove any pound signs (#) at the beginning of these entries.
To restart the daemon, find the inetd process ID and send a hangup signal as shown in the following example. This causes the daemon to re-read the configuration file and use the new information.
# ps -axc | grep inetd 17601 ? I 0:12 inetd # kill -HUP 17601
On some systems, the command to find the process ID is
# ps -ef | grep inetd
______________________________________________________________ FILE: /etc/bootptab.3.1.0 ______________________________________________________________ # $NCDId: @(#)bootptab,v 1.2 1992/06/16 22:55:23 mkm Exp $ # # /etc/bootptab: database for bootp server (/etc/bootpd) # Last update Mon 11/7/88 18:03 # Blank lines and lines beginning with `#' are ignored. # # Legend: # # first field - hostname # (may be full domain name and probably should be) # # hd - home directory # bf - bootfile # cs - cookie servers # ds - domain name servers # gw - gateway address # ha - hardware address # ht - hardware type # im - impress servers # ip - host IP address # lg - log servers # lp - LPR servers # ns - IEN-116 name servers # rl - resource location protocol servers # sm - subnet mask # tc - template host (points to similar host entry) # to - time offset (seconds) # ts - time servers # # Be careful to include backslashes where needed. Weird # (bad) things can happen when a backslash is omitted. # # First, we define a global entry which specifies the stuff # every host uses. quicc00:\ :ht=1:ha=123456789044:ip=199.171.148.29:hn:\ :sm=255.255.255.0:\ :hd=/tftpboot:bf=patxinu.bdnl:bs=auto:\ :ds=199.171.148.12 199.171.148.6:\ :ns=0x80020b4d 0x80020ffd:\ :ts=199.171.148.12:\ :to=0:
The general rules for bootptab file entries are:
The typical file structure is one or more template entries, containing information common to all RCS/4000s or a group of RCS/4000s, followed by individual entries, each containing information about a specific RCS/4000. For example:
# Template entry
template.name:\
tag=value:/
.
.
.
tag=value:/
# Entry for RCS4000
hostname:\
rcs=template.name:\
tag=value:/
.
.
.
tag=value:/
The tags required for each template file created for an individual RCS/4000 depend on the intended use/application of that particular RCS/4000. For example, if you are installing an RCS/4000 that will not access a gateway, the gateway address(es) tag, gw, need not be used.
As mentioned previously, bootptab files vary for different host systems. A sample bootptab template file for an RCS/4000 identified as RCS29, formatted for the SunOS, follows:
RCS29:\
:ht=1:ha=0080440c028f:ip=199.171.148.148:hn:\
:sm=255.255.255.0:\
:ds=199.171.148.12 199.171.148.6:\
:ns=0x80020b4d 0x80020ffd:\
:ts=199.171.148.12:\
:to=0:
The BOOTP/DHCP tags (from RFC 2132) which are used by the RCS/4000 are as follows:
Systech Corporation