(Page 7 of 7 in this chapter)

2.6 Installing Under Solaris

This section provides instructions for installing the AG Access software for Solaris 2.5x. You will complete the following steps:

2.6.1 Command Line Software Installation (Solaris)

      1. Log in as root at your shell's command prompt by entering:

           su

        

      2. Insert the first AG Access installation disk into your floppy disk drive.
        

        

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

        
Note:  In order to use the diskette device, the vold process must be killed before performing installation from the command line.

pkgadd displays the following prompt:
           Insert diskette into Floppy Drive 1.
           Type [go] when ready,
            or [q] to quit: (default: go)        

        

      4. Press Enter.
        

        

      5. You will have to enter the device name again when the system informs you that it has reached the end of media.
        

        
The installation program will guide you through the installation. When the installation has completed, the following message appears:
           Installation of AG Access for Solaris was successful.

      



2.6.2	 Modifying the Superuser Environment (Solaris)


        


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

        

      2. For the changes to the root user's PATH environment parameter to take affect, log out and log back in as root.
        

      

    


    

Note:  The AG device driver files (agXX, agswXX, aghwXX) are accessible by a user with root privileges only. If other users need access to these files, use the chmod command to change the file permissions.

    



2.6.3	 Creating the AG Configuration File (Solaris)





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.






2.6.4	 Configuring the AG Device Drivers (Solaris)





To configure the AG device drivers:


    


  1. Log in as root at your shell's command prompt by entering:
    

       su

    

  2. The /usr/kernel/drv/aghw.conf file specifies the I/O addresses for all boards in the system. The file is defaulted to one board at address 0x02c0.
    

    name="aghw" class="sysbus" intr=7,12 ioaddr=0x02c0 reg=0x02c0,0,6 slotalias=1;




intr specifies the interrupt value. The first value is the priority. The second value is an interrupt level. If you have any interrupt conflicts modify the second value.



ioaddr is the start of I/O memory to be used by this board.



reg should be set to the value of ioaddr followed by 0,6.



slotalias is sequential from 1.



The following is an example of a system with 6 AG boards:


name="aghw" class="sysbus" intr=7,12 ioaddr=0x02c0 reg=0x02c0,0,6 slotalias=1;
name="aghw" class="sysbus" intr=7,12 ioaddr=0x22c0 reg=0x22c0,0,6 slotalias=2;
name="aghw" class="sysbus" intr=7,12 ioaddr=0x42c0 reg=0x42c0,0,6 slotalias=3;
name="aghw" class="sysbus" intr=7,12 ioaddr=0x62c0 reg=0x62c0,0,6 slotalias=4;
name="aghw" class="sysbus" intr=7,12 ioaddr=0x82c0 reg=0x82c0,0,6 slotalias=5;
name="aghw" class="sysbus" intr=7,12 ioaddr=0xa2c0 reg=0xa2c0,0,6 slotalias=6;


    


  1. The /usr/kernel/drv/agsw.conf file contains configuration values passed to the switching driver agsw. The number of ports is defaulted to 8. Change the number-ports line to specify the actual number of ports by modifying the line:
    

       number-ports=200

    

  2. The /usr/kernel/drv/agmx.conf file specifies the number of boards and the number of ports for the mux driver agmx. The number of boards defaults to 1 and the number of ports is defaulted to 8. Modify the file to specify the actual number of ports and the number of boards by modifying the lines:
    

       ag-ports=200
       ag-boards=6    

    

  3. Make sure the values defined in the .conf files match the values defined in the ag.cfg file.
    

    

  4. Install the drivers by entering:
    

       add_drv aghw
       add_drv agsw
       add_drv agmx    


    
Note:  The installation scripts add a table fragment to the /etc/devlink.tab file. 
    This table fragment is not removed from the /etc/devlink.tab file during the uninstall procedure. Subsequent installations of AG Access will detect the fragment in the table.
    

  5. Proceed to Chapter 3 to verify your installation.
    







2.6.5	 Software Removal (Solaris)





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:


    


  1. Log in as root.
    

    

  2. At your shell's command prompt, remove the drivers by entering:
    

       rem_drv aghw
       rem_drv agsw
       rem_drv agmx    

    

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

    

  4. 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 Solaris
       (i386)
       Do you want to remove this package [y,n,?,q]    

    

  5. Enter y.
    

    
After the removal has completed, pkgrm displays the following confirmation:
       Removal of <agaccess> was successful.

    

  6. Exit the root shell.
    

    
At the shell command prompt, type:
       exit

    

  7. Shut down and reboot your system.
    

    
Note:  The installation scripts add a table fragment to the /etc/devlink.tab file.
    This table fragment is not removed from the /etc/devlink.tab file during the uninstall procedure. Subsequent installations of AG Access will detect the fragment in the table.









 
    (Page 7 of 7 in this chapter)









Tech_Support@nmss.com



Copyright © 1996, Natural MicroSystems, Inc.   All rights
reserved.