Previous PageNext Page

Chapter 8 - Communications




source-level routing

Figure 8-1. /disk1/banyan/comm Directory Structure


Figure 8-2. /disk1/banyan/comm/drivers Directory Structure



Role of

Building device drivers after a fresh installation ( MENU).
Adding a card or protocol stack through bmenu's Add Cards/Change Card Configuration menu. ( BMENU).
Rebuilding device drivers after an upgrade ( RECOVER).
Booting a server normally, with no added cards or change of software. This loads all configured drivers and protocols and initializes them ( NORMAL).

Note: The information in this section is designed to give you a better understanding of how the Banyan Server communications software is configured. If you want to change the configuration of your communications software, you should do so from the server console menus, not from the UNIX prompt.

Installing and Configuring Third-Party Drivers

1. Select 6 (Configure and Diagnose Server) from the System Maintenance menu. The script /bin/bmenu calls the script /bin/cfgsvr. The Banyan Server Configuration menu appears.

2. Select 8 (Install/Remove drivers). The /bin/cfgsvr script calls the script /disk1/banyan/comm/drivers/util/

The script runs the script, which allows administrators to load third-party LAN drivers from diskettes. The software from these diskettes is copied to the directory /disk1/banyan/comm/drivers/extdrivers.

Note: The add_option script is a required file on any diskette that is to be loaded onto a Banyan server through Load Additional Software or through econfig. Third-party LAN driver developers are required to write this script to copy the contents of the floppy diskettes into /disk1/banyan/comm/drivers/extdrivers.

3. The script builds a list of available drivers from the following files:

- /disk1/banyan/comm/drivers/extdrivers/*/*.inc - These files are provided by the third-party vendors whose software is loaded by Note that the vendors are allowed to build their own directory structure in the extdrivers directory.

- /disk1/banyan/comm/drivers/installed/*.inc

The list of available drivers is saved in a file called /disk1/banyan/comm/util/

4. The script calls the program econfig.

5. The econfig program reads the file The administrator is given an opportunity to install these drivers through the econfig menu. Any drivers that are actually installed in this session are written in the file install.lst.

After this step, the following files are in the disk1/banyan/comm/drivers/util directory:

- ecfg.sav - Third-party drivers previously installed on this server.

- install.lst - Newly installed LAN drivers.

- disk1/banyan/comm/drivers/util/main.ddl - A master list of drivers supported on this hardware platform by the Version 7.0 Banyan server software. This file uses #include statements to incorporate driver definition files from the directory /disk1/banyan/comm/drivers/baseddl.

6. The script runs cpp to generate the file svconfig.ddl.

7. The script runs ddlcomp on svconfig.ddl to generate the file sv.cfg. This step is a test run only. It is designed to ensure that the svconfig.ddl file generated is valid. If this test completes successfully, the file sv.cfg is generated in the directory /disk1/banyan/comm/drivers/util.

8. The script tests for the presence of /disk1/banyan/comm/drivers/util/sv.cfg. If this file exists, then /disk1/banyan/comm/drivers/util/svconfig.ddl is copied to the /disk1/banyan/comm/drivers directory.

Information on the boards that the system administrator wants to add to the system is added to sv.cfg when the administrator adds a card through the Add Cards/Change Card Configuration option.

9. The following command is used to rebuild sv.cfg: RECOVER

This command retains all current configuration information.

Note: If a configured adapter is deleted from svconfig.ddl through the econfig menu, commboot RECOVER completes successfully, but all configuration information on that adapter is lost, and you cannot reconfigure the card from the Add Cards/Change Card Configuration menu. The only way to recover is to reinstall the driver from the vendor's diskette.




Figure 8-3. Directory Structure of /disk1/banyan/sna


What SNATRACE captures
Viewing SNATRACE information


SNATRACE switch service-name

-o - Tells the service to start tracing.

-f - Tells the service to stop tracing and write SNATRACE information to the service log.

-d - Tells the service to delete all existing SNATRACE information from the service log.

-x - Collects trace information on inbound SNA requests after the data has been sent to the host and the host has acknowledged receipt of the data. This method differs from the -O switch, which collects trace information on inbound data after the SNA service issues the SEND request.

-c - Turns on the client-server trace function. Data between the client and the server is collected.

Note: Do not run SNATRACE any longer than you must. When run over a lengthy period of time, SNATRACE adversely affects 3270/SNA service performance and consumes large amounts of disk space.

Running Traces in Combination






What SNATRACE Captures

Link header (LH)
Transmission header (TH)
Response header (RH)
Request/response unit (RU)
Link trailer (LT)

Viewing SNATRACE Information

Is the service responding correctly to all ACTPU and ACTLU sequences?
Is the service accepting all BIND requests?
Is the service receiving session limit exceeded errors from the host?

Previous PageTop Of PageNext Page