(Page 5 of 7 in this chapter)

2.4 Installing Under UnixWare

This section provides instructions for installing the AG Access software from the command line. You will complete the following steps: Install the software Modify the superuser environment Modify the AG configuration file Configure the AG device drivers Note: Before installing AG Access, ensure that any earlier installation has been removed by the procedure in Section 2.4.7, Software Removal (UnixWare).

2.4.1 Command Line Software Installation (UnixWare)

Log in as root at your shell's command prompt by entering:
```
   su
```
Insert the first AG Access installation disk into your floppy disk drive.
Invoke the pkgadd utility by entering the following:
```
   pkgadd -d devicename agaccess
```
devicename is the name of the floppy disk drive from which you are installing. For example, if you are installing from your first floppy disk drive, at your shell's command prompt enter:
```
    pkgadd -d diskette1 agaccess
```
pkgadd displays the following prompt:
```
   Insert diskette into Floppy Drive 1.
   Type [go] when ready,
    or [q] to quit: (default: go)
```
Press Enter.
When the installation has completed, the following message appears:
```
   Installation of AG Access for UnixWare was successful.
```

2.4.2 Modifying the Superuser Environment (UnixWare)

Add /opt/nms/bin to the root user's PATH environment parameter and /opt/nms/lib to your LD_LIBRARY_PATH by completing the following steps:

a. Open a Terminal window.
b. Acquire root privileges by entering the following at your shell's command prompt:

su c. Enter the root password when prompted.
d. With your text editor, open the shell script file executed by the root user's login shell as part of the login sequence. If the root user's shell is the Bourne or Korn shell, you should edit the /.profile file. If the root user's shell is the C shell, you should edit the /.login file.
e. Append the following to the PATH environment parameter assignment:
/opt/nms/bin
For the Bourne and Korn shells, a sample PATH environment parameter assignment after your editing might look like:
PATH=$PATH:/opt/nms/bin
export PATH
For the C shell, a sample PATH assignment might look like:
setenv PATH "$PATH":/opt/nms/bin f. Append the following to the LD_LIBRARY_PATH environment parameter assignment:
/opt/nms/lib
For the Bourne and Korn shells, a sample LD_LIBRARY_PATH environment parameter assignment after your editing might look like
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/nms/lib
export LD_LIBRARY_PATH
For the C shell, a sample PATH assignment might look like
setenv LD_LIBRARY_PATH "$LD_LIBRARY_PATH":/opt/nms/lib g. Save the modified shell script file and exit your text editor.
For the changes to the root user's PATH environment parameter to take affect, log out and log back in as root.

2.4.3 Creating the AG Configuration File (UnixWare)

The AG loader/monitor program, agmon, interprets the AG configuration file to determine the interrupt, the I/O address, and other characteristics of an AG board, and uses it to download the firmware to a board. The AG configuration file is an ASCII file named /opt/nms/ag/cfg/ag.cfg. Note: /opt/nms/ag/cfg is the default directory to which the AG runtime software is installed. If you modified your software installation, replace the default directory with the path that you specified for your system.
There are several sample configuration files that were copied to your /opt/nms/ag/cfg directory during installation. The sample files include: File Name Description ag8.cfg For AG-8 running µ-law ag8a.cfg For AG-8 running A-Law ag8did.cfg For AG-8 DID ag24.cfg For AG-24 and AG-24+ ag30.cfg For AG-30 ag48.cfg For AG-48 ag60.cfg For AG-60 age1test.cfg For AG-E1 agt1.cfg For AG-T1

Each of these sample files configures one board at a default I/O address 0x2C0 and interrupt 12, and should work with an AG board of the appropriate type as it is shipped. The I/O addresses and interrupt that you chose during the installation of the AG boards must be entered into the AG configuration file. (The sample configuration files use the default values.) There are commented-out lines in the sample files for additional boards. If you are using two or more AG boards, refer to Section 4.4, Using Multiple AG Boards for instructions.
You must have an AG configuration file in the /opt/nms/ag/cfg directory or at a location specified on the command line in order to run agmon. See Chapter 5 for detailed information about agmon. See Chapter 4 for details about modifying the contents of the AG configuration file.

File Name	Description
`ag8.cfg`	For AG-8 running µ-law
`ag8a.cfg`	For AG-8 running A-Law
`ag8did.cfg`	For AG-8 DID
`ag24.cfg`	For AG-24 and AG-24+
`ag30.cfg`	For AG-30
`ag48.cfg`	For AG-48
`ag60.cfg`	For AG-60
`age1test.cfg`	For AG-E1
`agt1.cfg`	For AG-T1

2.4.4 Configuring the AG Device Drivers (UnixWare)

To configure the AG device drivers: Ensure that you have root privileges. At your shell's command prompt, start up the AG loader/monitor utility, agmon, by entering: agmon -c The -c command line option instructs agmon to check the interrupt and I/O address hardware settings of the AG boards for conflicts with other devices configured in your system and to add the AG device drivers to your UNIX system configuration. After the check for hardware conflicts has been completed, agmon displays the following message: AG device drivers are not part of your kernel configuration. Do you want to add them to the configuration now? (y/n) a. Enter y. After the device drivers have been added to the kernel configuration, agmon asks you to confirm that you want to rebuild the kernel. b. Enter y. If loading is successful, agmon exits. Once the system has been rebooted, leave agmon running.

2.4.5 Modifying Tunable Parameters (UnixWare)

AG Access requires the configuration of certain UNIX system resources and thresholds. If your system is using other-than-default values for some of the tunable parameters, you may see the following error message when agmon attempts to run diagnostics on Board 0: boot command failed : Invalid Argument
To correct this error, complete the following steps: Ensure that you have root privileges. Use the IDTUNE utility to determine the value of the STRMSGSZ parameter by entering the following at your command prompt: /etc/conf/bin/idtune -g -c STRMSGSZ IDTUNE displays the current, default, minimum and maximum values for the STRMSGSZ parameter, which may resemble the following. 4096 0 0 32767 The correct setting for the STRMSGSZ parameter is either 0 or 32767. If the current value (first number) is either 0 or 32767, and you continue to see the "Invalid Argument" error message, contact NMS Developer Support for assistance. If the STRMSGSZ parameter is set to anything other than 0 or 32767, reset it by entering the following at the command prompt: /etc/conf/bin/idtune STRMSGSZ 0 IDTUNE displays the following message: Tunable Parameter "STRMSGSZ" is currently set to 4096. Is it OK to change it to 32767? (y/n) Enter y. Rebuild the UNIX kernel by entering the following at the command prompt: /etc/conf/bin/idbuild -B Activate the new kernel by shutting down and restarting your system.

2.4.6 Changing Max Number of Opens (UnixWare)

The AG Access software, as shipped, supports 96 active open driver instances. The number of instances can be changed by following the procedure below. Because the AG device drivers are dynamically loadable modules (DLM), this procedure does not require a system reboot.

Invoke the IDTUNE utility by entering a command of the form:

/etc/conf/bin/idtune -c AGMXOPEN <newvalue>
where <newvalue> is the number of AG devices you want plus 2.
For example, if you are increasing the number to 120, enter:
/etc/conf/bin/idtune -c AGMXOPEN 122

To configure the AG multiplexor DLM with the changes you made to its configuration data, at your shell's command prompt enter:

/etc/conf/bin/idbuild -M agmx
The next time you run the AG loader/monitor, agmon, the newly configured AG multiplexor will be loaded into your running UNIX system.

2.4.7 Software Removal (UnixWare)

AG Access can be removed from your system using the command line interface. Note: Before removing the AG Access Library, ensure there are no applications running which access AG boards, including the AG loader/monitor, agmon.
To remove the AG device drivers and the AG Access software package from your system: Log in as root. At your shell's command prompt enter the following: agmon -r The -r command line option instructs agmon to remove the AG device drivers from your system's configuration. agmon displays the following message: Removing all AG device drivers. Do you really want to remove them? (y/n) Enter y. agmon displays the following messages: Removing AG device drivers ... AG device drivers removed from kernel configuration. A kernel rebuild and system reboot is required. Do you wish to rebuild the kernel now? (y/n) Enter y. Remove /opt/nms/bin from the root user's PATH environment parameter by completing the following steps: a. With your text editor, open the shell script file executed by the root user's login shell as part of the login sequence. If the root user's shell is the Bourne or Korn shell, you should edit the /.profile file. If the root user's shell is the C shell, you should edit the /.login file. b. Contract the PATH environment parameter by removing the following from its assignment: /opt/nms/bin c. Save the modified shell script file and exit your text editor. To invoke the pkgrm utility, enter the following at your shell's command prompt: pkgrm agaccess pkgrm displays the following prompt: The following package is currently installed: AG Access Software Development Kit for UNIX SVR4.x (i386) Do you want to remove this package [y,n,?,q] Enter y. After the removal has completed, pkgrm displays the following confirmation: Removal of <agaccess> was successful. Exit the root shell. At the shell command prompt, type: exit Shut down and reboot your system.

(Page 5 of 7 in this chapter)

Tech_Support@nmss.com