This document is designed to assist an RS/6000 system administrator in configuring a 7318 model P10 Style Port on a 7318 model S20. This document is designed for AIX System Administrators with a knowledge of AIX administration and the 7318. Using this document to troubleshoot a TTY's defined or stopped state takes approximately 20 minutes.
This document was designed to aid an IBM AIX Technical Specialist but can be used by any AIX Administrator with some knowledge in AIX administration and the 7318. This document does not contain any steps for TTY specific configuration on the P10 Style Port or detailed explanations about the steps used in the configuration methods.
The document is comprised of modules that contain specific troubleshooting steps. The modules have been arranged from general to specific configuration issues. If you are unable to configure TTYs on a 7318 S20 using this document, please contact an IBM AIX Technical Specialist.
This document begins by asking you to verify that the daemons needed for Terminal Server configuration are active. Then check the IPX communication channel between the host and the 7318. Using SMIT, modify and configure the S20 configuration file ttys for the 7318 ports. Finally, verify the Terminal Servers configuration and TTY device status.
This document applies to AIX levels 3.2.5 through 4.3.
NOTE: Since the P10 operates over IPX only, the 7318 P10 is commonly referred to as a Terminal Server. The S20 operates over IPX and TCP/IP, so it is called a Communications Server. Often, it is advantageous to configure the S20 as a Terminal Server which services TTYs and TTY-like devices. To configure the S20 as a Terminal Server, set up an IPX channel between the host and the S20. The S20 configuration file must be modified to specify TTY ports.
If the 7318 is on a remote network, TTY ports can still be configured for the 7318 on the host. An IPX communication channel must be configured and active between the host and the 7318. The steps for TTY configuration in this document are the same for a local or remote network configuration.
Before using this document, it is assumed that:
To use this document effectively, you must:
AIX Connections use an IPX protocol stack (indicating IPXd) that is slightly different than the IPX (indicating IPX) software that is used for NetWare and the 7318 Terminal Server. Both IPX software (IPX and IPXd) CANNOT be active on a host at the same time. To configure IPX for NetWare or the 7318, verify that AIX CONNECTIONS are not active on the host at the same time.
NOTE: Other hosts running AIX CONNECTIONS can reside on the same physical network without any incompatibility problems.
ps -ef | grep nw
Sample output is as follows:
root 11676 1 0 Oct 11 - 0:00 /usr/tn/nw/NWfile
root 23948 1 0 Oct 11 - 0:00 /usr/tn/nw/NWbinderyd
root 33958 1 0 Oct 11 - 0:00 /usr/tn/nw/NWprint
user 34264 47824 2 16:30:01 pts/22 0:00 grep nw
root 43820 11676 0 Oct 11 - 0:00 /usr/tn/nw/NWfile
root 46740 1 0 Oct 11 - 0:00 /usr/tn/nw/NWlockd
root 48002 1 0 Oct 11 pts/0 0:15 /usr/tn/nw/IPXd
root 48558 1 0 Oct 11 - 0:00 /usr/tn/nw/NWdiagd
If any AIX CONNECTIONS processes are active, you cannot configure an IPX network for NetWare or the 7318 on this host.
If AIX CONNECTIONS are NOT active, please continue with the next section.
The Terminal Server depends on many daemons for operation. The sapd and npsd daemons (Novell Protocol Suite) manage the IPX channel for communication and the cnsview daemon manages all Terminal Server devices and processes on the host. All three daemons must be active for a successful IPX boot and normal Terminal Server operation.
ps -ef | grep npsd
Sample output when the daemon is active is as follows:
root 5150 1 0 06:45:54 - 0:00 ./npsd root 16170 15336 2 15:47:33 pts/ 1 0:00 grep npsd
ps -ef | grep sapd
Sample output when the daemon is active is as follows:
root 5404 1 0 06:45:52 - 0:09 ./sapd root 16178 15336 5 15:47:39 pts/ 1 0:00 grep sapd
ps -ef | grep cnsview
Sample output when the daemon is active is as follows:
root 3370 1 0 06:46:03 - 0:03 /usr/bin/cnsview -c daemon start root 18978 15336 6 15: 47:25 pts/1 0:00 grep cnsview
If all three processes were listed in the output from the preceding ps commands, then proceed to the "Checking the IPX network" section. If the cnsview daemon was active but the sapd and/or npsd daemons are not active, stop the cnsview daemon and restart all three daemons using the sequence in the next step.
To stop the cnsview daemon, execute:
cnsview -c "daemon stop"
If all three processes were not listed in the output from the preceding ps commands, continue to start the daemons.
/usr/lpp/netware/bin/startnps
cnsview -c "daemon start"
NOTE: The cnsview daemon cannot be active until both the sapd and npsd daemons are active. If you are stopping daemons and yet they are still listed as an active system process, execute a kill -1 on the process id and restart all three daemons starting with step 4. If you are still unsuccessful, please contact your AIX support center.
The host's IPX routing table can be viewed by executing the program /usr/lpp/netware/bin/drouter. If the IPX network is configured properly, it will be listed in the IPX routing table.
All remote IPX networks will appear in the host's IPX routing table if there is an active IPX communication channel in between the two IPX networks (that is, the router or gateway is configured correctly and passes IPX packets).
/usr/lpp/netware/bin/drouter
Sample output looks like the following:
NETWORK HOPS TIME NODE NETWORK HOPS TIME NODE -------- ---- ---- ------------ ------- ---- ----- ------------ 00000001 0000 0001 000000000001 00000002 0000 0001 02608C2F7119 00000003 0000 0001 02608C2F1591 00000004 0001 0002 00406E0002F5 00000005 0001 0002 00406E0002DB END OF TABLE 5 known networks [root@levesconte] /#>
The column headings have the following meanings:
To set up P10 Style Ports on a 7318 model S20, the S20 ports must be reserved for Terminal Server operation (TTY devices). This section explains how to create a configuration file for the respective S20 (if it is not created already) and modify the configuration file for Terminal Server operation.
A configuration file name example is shown below:
00406eXXXXXX.cfg
XXXXXX consists of the last 6 digits of the S20's ethernet address (for example, 00406ee00123.cfg or 6ef00456.cfg). If this configuration file exists, continue with step 3. If this configuration file does NOT exist, continue with step 2 to create a configuration file.
NOTE: At this point it is good practice to save a current copy of the file you are about to edit in the event you need to restore it to its original form (for example, cp 00406ee00123.cfg 00406ee00123.sav).
Search for PortNN (where NN is the port number) on which to configure the P10 Style Port.
[Session0] port=0 session=0 application=reserved device=LDTCOM [Session1] port=0 session=1 application=reserved device=LDTCOM [Session2] port=0 session=2 application=reserved device=LDTCOM [Session3] port=0 session=3 application=reserved device=LDTCOM
Next, the 7318 needs to be updated with the modified S20 configuration file. You can force the 7318 to reload its configuration file in three ways.
If the 7318 has already been configured and you are just adding ttys to this configured 7318, then skip to the next section "Adding TTY devices to the 7318 through SMIT". If, at this point, the 7318 needs to be added, proceed with the rest of this section.
Verify that the 7318's device information, specified download image, and IPX network address are correct in its SMIT configuration.
smitty ts7318_cs_mnu
It should match an IPX network address listed in the host's IPX routing table on which the 7318 resides.
This number is the 7318's hardware address and is labeled on the back of the 7318.
Press Enter to implement the changes.
NOTE: SMIT automatically refreshes the cnsview daemons. Reboot the 7318. This can be done in two ways.
cnsXX is the 7318 cns number.
TTYs can be added to the ports on the 7318 Terminal Server using SMIT. This section lists the steps required to add a TTY to a port on the Terminal Server (S20 with P10 Style Ports). If more than one TTY needs to be added to the Terminal Server, repeat the steps in this section for each TTY.
This menu can also be reached from the main SMIT menu by following this path:
Sample configuration looks like the following:
Add a TTY to a ComNetServer Add Associated Virtual TTYs yes TTY ComNetServer Number 01 TTY Port Number 1 TTY Device Type VTTY2 Interface Type RS-232
If the TTYs will be used as login terminals, the host must be configured to spawn a getty which issues a login prompt to the terminal. Follow these steps below to enable the TTY for login.
This menu can also be reached from the main SMIT menu by following this path:
The 7318 and associated TTYs will be in one of these states:
defined
stopped
available
"Defined" or "stopped" means the TTY has been defined on the host, but the IPX communication channel (SPX link) between the 7318 and the host is not active. There may also be an incorrect configuration for the Terminal Server in the S20 configuration file, or the daemons that monitor the Terminal Server operation are not active (npsd, sapd, cnsview).
"Available" means the IPX communication channel is active and the ports are ready for use.
lsdev -C | grep NW | pg