Configuring P10 Style Ports on an IBM 7318 Model S20


Contents

About this document
Prerequisite information
Checking for conflicting software
Checking daemons
Checking the IPX network
Remote configurations
Modifying the 7318's S20 configuration file
Forcing the 7318 to reload its configuration file
7318 SMIT configuration
Adding TTY devices to the 7318 through SMIT
Enabling TTYs for login
Checking the TTY state

About this document

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.

Remote configurations

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.


Prerequisite information

Assumptions

Before using this document, it is assumed that:

Terms used in this document

Requirements

To use this document effectively, you must:


Checking for conflicting software

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.

  1. To check if AIX CONNECTIONS are active, execute:
    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 
    
  2. Verify that AIX CONNECTIONS are inactive (AIX Connections are inactive if none of the processes listed above are running).

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.


Checking daemons

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.

  1. Verify to see if the IPX npsd daemon is active, execute:
    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 
    
  2. To check to see if the IPX sapd daemon is active, execute:
    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 
    
  3. To check to see if the cnsview daemon is active, execute:
    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.

  4. To start the sapd and npsd daemons, execute:
    /usr/lpp/netware/bin/startnps 
    
  5. To start the cnsview daemon, execute:
    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.

  6. Once these daemons are active, continue to the next section.

Checking the IPX network

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.


Remote configurations

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).

  1. To view the host's IPX routing table, execute:
       /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:

    NETWORK
    is the network number, internal or external. There should be one entry in this table for each network segment in the overall network and one for each host on the inter-network.
    HOPS
    is the number of routers that must be passed through to get to this network.
    NODE
    is the ethernet address of the station used to get to the network.

  2. Verify that the IPX network is shown in the listing. If the Terminal Server's IPX network is shown in the host's IPX routing table, proceed to the next section. If the Terminal Servers IPX network is NOT shown in the host's IPX routing table, the host needs to be configured for an IPX network. Refer to documentation in "Configuring an IPX Network" before continuing this Terminal Server configuration.

Modifying the 7318's S20 configuration file

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.

  1. Check for the S20's configuration file. By default, the configuration file resides in the /usr/lib/cns directory. The configuration file name should be <the_S20s_ethernet_address>.cfg or the <last_8_digits_of_ethernet_address>.cfg.

    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.

  2. Create a unique configuration file for the 7318 S20. The default S20 configuration file is /usr/lib/cns/s20.cfg. Copy the default configuration file (s20.cfg) and name it 00406eXXXXXX.cfg (where XXXXXX is the last 6 hexadecimal digits of the 7318's ethernet address). If the S20 has been previously configured and is booted, then this file may already exist.

    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).

  3. Open the S20 configuration file for your 7318 with your favorite editor.

    Search for PortNN (where NN is the port number) on which to configure the P10 Style Port.

  4. Each port has four session stanzas by default (each port can have up to seven session stanzas). Modify the application= line in each Session stanza to read application=reserved. Below is a sample configuration for Port00 (comments removed).
    [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 
    
  5. Modify the terminal type parameter in the [PortNN] stanza which best reflects the terminal type being used on this port. Recognized values are: ibm3151, ibm3164, vt100, ansi.

  6. Search for the next PortNN on which to add a TTY. Modify the application=reserved for each session in that port's stanza.

  7. Once all the Port stanzas have been modified, save any modifications and exit this file.

Forcing the 7318 to reload its configuration file

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.

  1. Issue the command cnsview -c "reboot" /dev/cnsXX (where cnsXX is the 7318 cns number).
  2. Recycle the 7318's power by unplugging the power cord.
  3. Issue the commands admin and reboot from an S20 command session.

7318 SMIT configuration

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.

  1. To start SMIT and use the fast path ts7318_cs_mnu, execute:
        smitty ts7318_cs_mnu 
    
  2. Choose Add a ComNetServer.

  3. The New ComNetServer Number should be the next unused number in the sequence 01 to 99 for cns devices on the system. If this is the only terminal server, then this number should be 01.
     
  4. Input the ComNetServer Network Address.

    It should match an IPX network address listed in the host's IPX routing table on which the 7318 resides.

  5. Input the ComNetServer Ethernet Address.

    This number is the 7318's hardware address and is labeled on the back of the 7318.

  6. Set the bootfile to /usr/lib/cns/cns-s20e.

    Press Enter to implement the changes.

    NOTE: SMIT automatically refreshes the cnsview daemons. Reboot the 7318. This can be done in two ways.


Adding TTY devices to the 7318 through SMIT

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.

  1. Start SMIT and select the fast path ts7318_tty_mnu. Then select Add a TTY to a ComNetServer from this menu.

    This menu can also be reached from the main SMIT menu by following this path:

  2. Select the 7318 on which to add the TTY.

  3. SMIT will list all of the Available TTY Ports. Select the port on which to add the TTY.

  4. SMIT will list the Available TTY Types. If a TTY has NOT been configured for the 7318 port, select Non-Virtual TTY. (If Non-Virtual TTY is not shown as an option, there may already be a device defined on this port.)

  5. If Virtual TTYs are to be added, press the Tab key until the Add Associated Virtual TTYs field is yes. (Virtual TTYs are used for multiple sessions on the same terminal, which can be accessed using hot keys defined in the Terminal Servers configuration file).

  6. Verify the information in the Add a TTY to a ComNetServer fields and press Enter.

    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 
    
  7. After the TTY has been added, press F10 to exit or F3 twice to return to the ComNetServer TTY Configuration menu if more TTYs are to be added. Repeat until you have added all the TTYs. If the TTYs will be used as terminal logons, continue with next section.

Enabling TTYs for login

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.

  1. Start SMIT and select the fast path tty.

  2. Choose Change / Show Characteristics of a TTY.

    This menu can also be reached from the main SMIT menu by following this path:

  3. Select the appropriate TTY (the TTYs on the 7318: NW-XX-XX-XX).

  4. Use the Tab key to change Enable LOGIN to enable.

  5. Find (scroll down to) TERMINAL Type parameter.

  6. Set the TERMINAL Type to the terminal type you are using.

  7. After you make the changes, press Enter to change the TTY.

Checking the TTY state

The 7318 and associated TTYs will be in one of these states:
defined
stopped
available

State definitions

"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.

  1. To check the state of the 7318 and associated TTY devices, execute:
        lsdev -C | grep NW | pg 
    
  2. Verify the device state. If the 7318 (cns device) or associated TTYs are in a "stopped" or a "defined" state, verify all the configuration steps listed above. If the 7318 (cns device) or associated TTYs are in an "available" state but you are still unable to communicate with the TTY devices, please contact your AIX support center.


Configuring P10 Style Ports on an IBM 7318 Model S20: 7318.p10.port.32-41.com ITEM: FAX
Dated: 99/06/23~00:00 Category: com
This HTML file was generated 99/06/24~12:42:09
Comments or suggestions? Contact us