APPENDIX B
Solaris Server Intranet Extension Products

THE SOLARIS SERVER INTRANET EXTENSION 1.0 CD-ROM CONTAINS A SUITE OF PRODUCTS for system management, network services, and remote connectivity and security. Sun Microsystems automatically ships the Solaris Server Intranet Extension 1.0 CD-ROM with each server. The CD-ROM is not shipped with desktop systems. Most of the products available on this CD-ROM were previously part of the Solstice suite of tools. You can install these products on systems running Solaris 2.5.1 system software or later.

This appendix provides an overview of the products on the Solaris Server Intranet Extension CD-ROM to help you determine whether these products are useful for your system administration needs. It also lists system requirements and provides brief installation instructions for each product. If your site does not have the Solaris Server Intranet Extension CD-ROM, you can order it from your Sun sales representative or authorized reseller. You can also find information about the Solaris Server Intranet Extension products from Sun's Web page at http://www.sun.com.

Introducing the Solaris Server Intranet Extension Products

The products on the Solaris Server Intranet Extension CD-ROM provide functionality in three different areas:

•  System management

•  Network services

•  Remote connectivity and security

System Management

System management capabilities are the core of any complete server offering. The Solaris Server Intranet Extension system management product set offers powerful system and network management tools for centralized, simplified management of distributed, heterogeneous environments.

The following list briefly introduces the system management products:

•  AdminSuite software is a unified suite of tools for administering a distributed system and managing such functions as user accounts, groups, administrative data, printers, file systems, disks, and serial ports.

•  DiskSuite software is a disk storage management tool designed to meet the demands of mission-critical business applications. DiskSuite addresses the need for increased data safety, availability, and performance. DiskSuite uses the following technologies: disk mirroring, hot spares, RAID-5, concatenation, disk striping and RAID-5, and a logging UNIX file system.

•  AutoClient software is a desktop management application that centralizes administration, makes the desktop a field replaceable unit (FRU), eliminates software installation on desktops, and eliminates the need for desktop backups. Solstice AutoClient software reduces the cost of desktop management and is a key component of the centralized administration model.

•  Backup Utility software is the single-server version of the Solstice Data Backup Utility that enables you to back up a single server to a single backup device and supports non-automated backup devices (single devices) in 4 mm, 8 mm, and 1/4 inch formats.

Network Services

The network services products enable Solaris to seamlessly integrate Novell, Windows, and AppleTalk clients while maintaining their native environments. In addition to basic file and printing services, Solaris adds powerful messaging, Web publishing, and Java application support that is essential to the new Web group.

The following list briefly introduces the network services products:

•  TotalNET Advanced Server (TAS) software provides network operating system software integrated with UNIX print and application servers. You install TAS directory on to the server to enable client PC and UNIX computers to become instantaneously productive.

•  Sun Web Server software is designed for Internet Service Providers (ISPs) and corporations whose Internet/intranet servers must be high performance, scalable, and able to handle large numbers of users and transactions.

•  Solstice Internet Mail Server (SIMS) software is an advanced mail solution for today's Solaris workgroups. SIMS provides open, Internet-based mail built on key Internet standards such as IMAP4, POP3, SMTP, and MIME. SIMS 2.0 also includes use of five Solstice Internet Mail reference clients, which run on Solaris workstations and Microsoft Windows PCs. These clients provide the best mobile and disconnected mail client solutions available in the market today.

•  Java Interface Definition Language (IDL) software, Sun's 100 percent pure Java Object Request Broker (ORB) system, provides the software foundation necessary to deliver enterprise client/server applications for the Internet. Applications that use Java IDL seamlessly integrate with non-Java programs and programs from other vendors. The Java IDL system is based on the latest Common Object Request Broker Architecture (CORBA) and Internet Inter ORB Protocol (IIOP) industry standards.

Remote Connectivity and Security

Whether you need to connect workgroups over leased lines or through the Internet, Solaris meets your most demanding connectivity needs and ensures that your private information remains private.

The following list briefly introduces the remote connectivity and security products:

•  Solstice PPP software provides extended Internet connectivity for Solaris SPARC and x86 systems. With Solstice PPP, a Solaris system acts as an Internet router and supports all IP applications transparently over both leased lines and dial-up connections.

•  SunScreen SKIP software is Sun Microsystems' implementation of Simple Key-management for Internet Protocols (SKIP). SunScreen SKIP is replacement software and upgrade software for any previous version of SKIP for Solaris. SKIP software provides encryption for your data and authentication of the IP traffic stream. SunScreen SKIP enables you to securely conduct business over both the corporate intranet and the Internet.

CD-ROM Contents

Table B-1 lists the top-level files and directories on the Intranet Extension CD-ROM.

AdminSuite

The Solstice AdminSuite 2.3 product provides a suite of graphical user interface tools and commands that you can use to perform system administration tasks.

The Solstice AdminSuite software enables you to locally or remotely manage the following:

•  Important network-related system database files, such as aliases and hosts

•  User accounts and groups

•  File systems

•  Disk slices and x86 fdisk partitions

•  Terminals and modems

•  Diskless and dataless clients

•  AutoClient systems

•  Stand-alone systems

•  JavaStations

•  Servers

•  Printers

The Solstice AdminSuite software to perform system administration benefits you in the following ways:

•  The tools and commands are faster than using numerous Solaris commands to perform the same tasks.

•  System files are updated automatically without the risk of making errors by editing important system files manually.

•  You can manage systems remotely from one system.

Table B-2 lists the Solstice AdminSuite tools that run under an X Window System, such as the CDE and OpenWindows environments.

AdminSuite Files and Directories on the CD

The files and directories in the /cdrom/solaris_srvr_intranet_ext_1_0/ AdminSuite_2.3+AutoClient_2.1 directory are listed in Table B-3.

Installing Solstice AdminSuite

The following sections provide guidelines for installing Solstice AdminSuite software. For complete instructions refer to the Solstice AdminSuite 2.3 Installation and Product Notes documentation available in the /cdrom/ solaris_srvr_intranet_ext_1_0/AdminSuite_2.3+AutoClient_2.1/Manuals directory.

Reviewing Disk Space Requirements

You need 35 MB of free disk space plus an additional 15 MB of disk space for each architecture (SPARC and X86) to perform a full installation of the Solstice AdminSuite 2.3 software on a Solstice station manager system.

---

NOTE:  You do not need to do a full installation of Solstice AdminSuite 2.3 on each system. You can do a complete installation on one system and use the installation program to set up other systems to access the complete Solstice AdminSuite 2.3 software installation.

---

Checking Software Package Requirements

The Solstice AdminSuite 2.3 product verifies that the following software packages are installed on systems running the Solaris 2.5 or later operating environment:

•  SUNWadmc (System administration core libraries)

•  SUNWadmfw (System and network administration framework)

•  SUNWsadml (Solstice launcher)

•  SUNWmfrun (Motif runtime kit)

The SUNWsadml and SUNWmfrun software packages should be automatically installed on systems running the Solaris 2.3 and later releases. To verify that the packages are installed and available, type pkginfo | grep <pkgname> and press Return.

---

NOTE:  Although the Solstice AdminSuite 2.3 Installation and Product Notes documentation says that you must install these packages from the Solaris CD-ROM for Solaris 2.6, these packages may already be installed.

---

The SunSoft Print Client software assumes the following Federated Naming Service (FNS) packages are already installed:

•  SUNWfns

•  SUNWfnspr

These packages are automatically installed by the Solstice AdminSuite installation scripts on systems running Solaris 2.3 and later releases. On systems running the Solaris 2.3 and 2.4 operating environment, you must install the SUNWlibCf package to use the SunSoft Print Client software in the NIS+ name service. You can obtain this package from the Solaris media used to originally install the system.

Removing Previously Installed AdminSuite Software

If you have installed an earlier release of the Solstice AdminSuite software (for example, Solstice AdminSuite 2.2), you must remove the old version before installing your new software.

To remove previously installed software:

1.  Log in as root on the server running the old AdminSuite software.

2.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/ AdminSuite_2.3+AutoClient_2.1 and press Return.

3.  Type ./rm_admin -v 2.2 -d /opt [-f] and press Return. The -v option specifies the version to be removed. If you do not specify a version number, the command removes the 2.1 version from the /export/opt directory. The -d option specifies the directory where the AdminSuite software is installed. The optional -f option forces removal of software with no confirmation prompt.

Verifying sysadmin Group Membership

You must be a member of the sysadmin group (GID 14) to run the admin_install script. In addition, you must belong to the sysadmin group on each host you specify during installation.

To verify that you are a member of the sysadmin group, type groups and press Return. If the sysadmin group is listed in the output, you are a member of the group.

In the following example, the user is a member of both the staff and sysadmin groups.

castle% groups
staff sysadmin
castle%

Running the admin_install Script

To install AdminSuite and AutoClient software:

1.  Log in as a member of the sysadmin group for the system.

2.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically.

3.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/AdminSuite_2.3+AutoClient_2.1 and press Return.

4.  Type ./admin_install and press Return.

5.  Follow the installation instructions displayed by the admin_install script. For complete instructions refer to the Solstice AdminSuite 2.3 Installation and Product Notes documentation available in the /cdrom/ solaris_srvr_intranet_ext_1_0/AdminSuite_2.3+AutoClient_2.1/Manuals directory.

Running AdminSuite

To run AdminSuite, type /usr/bin/solstice& and press Return. For complete instructions on how to use AdminSuite, refer to the Solstice AdminSuite 2.3 Administration Guide available in the /cdrom/solaris_srvr_intranet_ext_1_0/ AdminSuite_2.3+AutoClient_2.1/Manuals directory.

AutoClient

An AutoClient system is a system that caches (locally stores copies of data as it is referenced) all of its needed system software from a server. The Solstice AutoClient product enables you to set up systems as AutoClient systems and provide centralized administration for these systems. AutoClient systems use Solaris diskless and cache file system (CacheFS) technologies.

The AutoClient technology makes administration easier, enabling system administrators to maintain many AutoClient systems from a server. You do not have to make changes on each individual system. Users may notice improved performance as well on both AutoClient systems and servers.

An AutoClient system is nearly identical to a diskless client system. Diskless client systems have no hard disk and depend on a server for its software and storage areas. Diskless clients remotely mount root (/), /usr, and /home file systems from a server.

An AutoClient system has the following characteristics:

•  Requires 100 MB or larger local disk used for swapping and for caching its individual root (/) file system and the /usr file system from a server

•  Can be set up so that it can continue to access its cache when the server is unavailable

•  Relies on servers to provide other file systems and software applications

•  Contains no permanent data, making it a field replaceable unit (FRU)

---

NOTE:  You must obtain a license for each AutoClient system you want to add to your network. For licensing information, see the Solstice AutoClient 2.1 Installation and Product Notes.

---

Advantages of an AutoClient System

AutoClient technology provides many system administration advantages over existing system types.

AutoClient systems have the following advantages over diskless systems:

•  Provides better overall scalability in a network environment, which could result in less network load.

•  Uses less disk space on a server than a diskless system because an AutoClient system does not require any swap space on a server.

•  Uses significantly less network and server bandwidth than a diskless system.

AutoClient systems have the following advantages over dataless and standalone systems:

•  Require less system administration overhead. The data for an AutoClient system is on a server, which enables centralized administration. For example, with AutoClient systems need to back up only the server(s) that supports the AutoClient systems. You can also manipulate AutoClient root file systems from the server without accessing each system individually.

•  Are FRUs, which makes them easy to replace if they fail.

•  Are installed by setting up an AutoClient system with the Host Manager. You do not have to use the Solaris installation program to install the Solaris environment on an AutoClient system.

How an AutoClient System Works

The CacheFS technology is the important component of AutoClient systems. A cache is a local storage area for data. A cached file system is a local file system that is used to store files from a server as they are referenced. Subsequent references to the same files are accessed from the cache instead of being retrieved from the server. This functionally reduces the load on the network and the server and generally results in faster access for the AutoClient system. When the cache becomes full, space is reclaimed on a least-recently-used basis. Files that have been unreferenced from the longest time are discarded from the cache to free space for the files that are currently being referenced.

An AutoClient system uses its local disk for swap space and to cache its individual root (/) file system and the /usr file system from the server's back file system.

How an AutoClient System Cache Is Updated

An AutoClient system uses consistency checking to keep a cached file system synchronized with its back file system on the server.

By default, files that are updated in the server's back file systems are updated on the AutoClient system's cached file systems within 24 hours. However, if the update needs to be done sooner, you can use the autosync command to initiate consistency checking that updates (synchronizes) an AutoClient system's cached file systems with its server's back file systems.

Each time an AutoClient system is booted, the AutoClient system's cached file systems are checked for consistency and updated with its server's back file systems.

If you add new files to an AutoClient system, its server's back file systems are updated immediately because an AutoClient system uses a write-through cache. A write-through cache is one that immediately updates its back file system as data is changed or added to the cache.

---

NOTE:  Consistency checking for an AutoClient system is different from a system running CacheFS. AutoClient files (/ and /usr) are not likely to change very often, so consistency checking does not need to be done as frequently on an AutoClient system as on a system running CacheFS.

---

AutoClient Files and Directories on the CD

Refer to Table B-3 on page 502 for a list of file and directories in the /cdrom/ solaris_srvr_intranet_ext_1_0/AdminSuite_2.3+AutoClient_2.1 directory.

Installing AutoClient Software

The following sections provide guidelines for installing Solstice AutoClient software. For complete instructions refer to the Solstice AdminSuite 2.3 Installation and Product Notes documentation available in the /cdrom/ solaris_srvr_intranet_ext_1_0/AdminSuite_2.3+AutoClient_2.1/Manuals directory.

Supported Platforms and Operating Systems

You can set up both SPARC and x86 AutoClient systems on any systems running Solaris 2.4 and later system software.

AutoClient software is supported on Solaris 2.4 and later systems. If you plan on having 4.x clients on your server, and are running a version of Solaris later than 2.5.1, you need to manually install the SUNWhinst package that is included in the /cdrom/solaris_srvr_intranet_ext_1_0/ AdminSuite_2.3+AutoClient_2.1/4.x directory on the CD-ROM.

Reviewing Disk Space Requirements

You need 35 MB of free disk space for the spooled software area and an additional 7 MB of disk space for each architecture (SPARC and x86) to perform a full installation of the Solstice AutoClient 2.1 software.

Checking Software Package Requirements

The Solstice AutoClient 2.1 product verifies that the following software packages are installed on systems running the Solaris 2.5 or later operating environment:

•  SUNWadmc (System administration core libraries)

•  SUNWadmfw (System and network administration framework)

•  SUNWsadml (Solstice launcher)

•  SUNWmfrun (Motif runtime kit)

The SUNWsadml and SUNWmfrun software packages should be automatically installed on systems running the Solaris 2.3 and later releases. To verify that the packages are installed and available, type pkginfo | grep <pkgname> and press Return.

---

NOTE:  Although the Solstice AdminSuite 2.3 Installation and Product Notes documentation says that you must install these packages from the Solaris CD-ROM for Solaris 2.6, these packages may already be installed.

---

Removing Previously Installed AutoClient Software

If you have installed an earlier release of the Solstice AutoClient software, you must remove the old version before installing your new software.

To remove previously installed software:

1.  Log in as root on the server running the old AutoClient software.

2.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/ AdminSuite_2.3+AutoClient_2.1 and press Return.

3.  Type ./rm_admin -a -d /opt and press Return. The -a option specifies that you want to remove the AutoClient software. The -d option specifies the directory where the AutoClient software is installed.

Verifying sysadmin Group Membership

You must be a member of the sysadmin group (GID 14) to run the admin_install script. In addition, you must belong to the sysadmin group on each host you specify during installation.

To verify that you are a member of the sysadmin group, type groups and press Return. If the sysadmin group is listed in the output, you are a member of the group.

In the following example, the user is a member of both the staff and sysadmin groups.

castle% groups
staff sysadmin
castle%

Installing Patches

Support for automatically patching new diskless and AutoClient clients is not integrated into the AdminSuite and AutoClient tools. A command-line interface, admclientpatch, is provided to enable you to patch existing clients with one operation.

The AdminSuite product ships a small number of required patches for different releases of Solaris. The appropriate patches are applied as you create new clients. You can use the admclientpatch command to spool additional patches or you can remove patches from the spool area that you no longer need. You should, however, be careful when removing one of the patches that is shipped with Solstice AutoClient 2.1 because new clients may not work properly if a required patch is missing.

Because patches are applied automatically when you create a client, be aware that if you have existing clients, including dataless clients, that share the OS service with the new client, these existing clients now also have the patch. Use the admclientpatch command to be sure that all of the diskless and AutoClient systems also have the patch applied to their root file system. For dataless clients, you may need to go to each client and apply the patch to ensure that the dataless root is patched properly to match the shared OS service.

The patch also affects any dataless clients that use CacheFS and that share the OS service. You need to apply the appropriate patch to the dataless client's root for the client to work properly.

The patches are in the spool area /opt/SUNWadmd/Patches. The /cdrom/ solaris_srvr_intranet_ext_1_0/AdminSuite_2.3+AutoClient_2.1/ Patches directory on the CD-ROM contains i386 patch number 104469-06 and SPARC patch 104468-06. Refer to the README file in the /cdrom/ solaris_srvr_intranet_ext_1_0/AdminSuite_2.3+AutoClient_2.1/Patches directories for more information.

Table B-4 lists the patches that need to be applied to the dataless client root.

Installing Solstice AdminSuite and AutoClient Software

To install AdminSuite and AutoClient software:

1.  On the server, log in as a member of the sysadmin group.

2.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically.

3.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/ AdminSuite_2.3+AutoClient_2.1 and press Return.

4.  Type ./admin_install and press Return.

5.  Follow the installation instructions displayed by the admin_install script. For complete instructions refer to the Solstice AutoClient 2.1 Installation and Product Notes documentation available in the /cdrom/ solaris_srvr_intranet_ext_1_0/AdminSuite_2.3+AutoClient_2.1/Manuals directory.

Running AutoClient

To run AutoClient, type /usr/bin/solstice& and press Return. For complete instructions on how to use AutoClient, refer to the Solstice AutoClient 2.1 Administration Guide available in the /cdrom/solaris_srvr_intranet_ext_1_0/ AdminSuite_2.3+AutoClient_2.1/Manuals directory.

DiskSuite

Solstice DiskSuite 4.1 is a software product that enables you to manage large numbers of disks and the file systems on those disks. Although you can use DiskSuite in many ways, most tasks include:

•  Increasing storage capacity

•  Increasing data availability

In some instances, DiskSuite can also improve I/O performance.

DiskSuite runs on all SPARC and x86 systems running Solaris 2.4 or later releases.

---

CAUTION:  If you do not use DiskSuite correctly, you can destroy data. As a minimum safety precaution, make sure you have a current backup of your data before using DiskSuite.

---

DiskSuite uses virtual disks to manage physical disks and their associated data. In DiskSuite, a virtual disk is called a metadevice. Applications and tools accessing file systems on metadevices consider them to be functionally identical to physical disks.

DiskSuite metadevices are built from slices (disk partitions). You can build metadevices easily with the DiskSuite Tool that comes with DiskSuite. DiskSuite Tool presents you with a view of all the slices available to you. You can quickly assign slices to metadevices by dragging and dropping slices onto metadevice objects. You can also build and modify metadevices by using DiskSuite's command-line utilities.

If, for example, you want to create more storage capacity, you can use DiskSuite to make the system treat a collection of many small slices as one larger slice or device. After you have created a large metadevice from the slices, you can immediately begin using it just as any “real” slice or device.

DiskSuite can increase the reliability and availability of data by using mirrors (copied data) and RAID5 metadevices. DiskSuite's hot spares can provide another level of data availability for mirrors and RAID5 metadevices. Hot spares are a collection of slices that are reserved to be automatically substituted in case of slice failure in either a submirror or RAID5 metadevice.

---

NOTE:  Running RAID5 with DiskSuite can have a substantial impact on CPU resources.

---

Once you have set up your configuration, you can use DiskSuite Tool to report on its operation. You can also use DiskSuite's SNMP trap-generating daemon so that you can work with a network monitoring console to automatically receive DiskSuite error messages.

---

NOTE:  Solstice DiskSuite 4.1 is not backwardly compatible with previous Online: DiskSuite 2.0.1 and 3.0 products. It is compatible with Solstice DiskSuite 4.0. If you have one of the earlier versions of Online: DiskSuite installed, you must convert your current metadevice configuration to Solstice DiskSuite 4.1.

---

DiskSuite Files and Directories on the CD

Table B-5 lists the files and directories in the /cdrom/ solaris_srvr_intranet_ext_1_0/DiskSuite_4.1 directory.

Installing Solstice DiskSuite

The following sections provide guidelines for installing Solstice DiskSuite software. For complete instructions refer to the Solstice DiskSuite 4.1 Installation and Product Notes documentation available in the /cdrom/ solaris_srvr_intranet_ext_1_0/DiskSuite_4.1/Manuals directory.

Reviewing Disk Space Requirements

You need 35 MB of free disk space plus an additional 15 MB of disk space for each architecture (SPARC and X86) to perform a full installation of the Solstice DiskSuite 4.1 software on a system that is set up to manage disk resources.

Choosing Software Packages

This section describes the DiskSuite packages. In addition to the DiskSuite packages, you can install the packages for Solstice AdminSuite Storage Manager, a graphical tool for administering file systems and disks. If AdminSuite 2.2 or later is already installed on your system, do not install any of the AdminSuite packages included with DiskSuite. Refer to Table B-5 for a description of the DiskSuite packages.

You must install packages in the order shown in Table B-6 for the software to function properly.

Installing Solstice DiskSuite

To install DiskSuite software from the command line:

1.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically. See Appendix A for information about volume management and mounting CDs.

2.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/DiskSuite_4.1/sparc | i386 and press Return.

3.  Become superuser. You must be superuser to run the pkgadd command.

4.  Type pkgadd -d . and press Return. A list of available packages is displayed and pkgadd prompts you to enter the number associated with a package. You must install packages in the order specified in Table B-6 on page 512.

castle# pkgadd -d .

The following packages are available:
  1  SUNWadm5r     Solstice AdminSuite root supplement for Solaris
       2.3 and 2.4
         (sparc) 6.5,REV=95.10.26.00.11
  2  SUNWadm5u     Solstice AdminSuite supplement for Solaris 2.3
       and 2.4
         (sparc) 6.5,REV=95.10.26.00.11
  3  SUNWadmsm     Solstice AdminSuite Storage Manager Application
         (sparc) 6.6,REV=96.11.18.00.43
  4  SUNWmd        Solstice DiskSuite
         (sparc) 4.1-FCS,REV=6.0
  5  SUNWmdg       Solstice DiskSuite Tool
         (sparc) 4.1-FCS,REV=6.0
  6  SUNWmdn       Solstice DiskSuite Log Daemon
         (sparc) 4.1-FCS,REV=6.0
  7  SUNWsadmc     Solstice AdminSuite Core Methods
         (sparc) 6.6,REV=96.11.18.00.42
  8  SUNWsadml     Solstice Admintool Launcher.
         (sparc) 6.5,REV=96.04.25.17.31
  9  SUNWsadmo     Solstice AdminSuite Object Libraries
         (sparc) 6.6,REV=96.11.18.00.42

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

5.  Type 2,1,7,9,8,3,4,5,6 and press Return.

6.  Follow the pkgadd prompts.

7.  When installation is complete, reboot the system.

8.  Modify the root account PATH variable to include /usr/opt/SUNWmd/sbin.

9.  Modify the root account MANPATH to include /usr/opt/SUNWmd/man.

For complete instructions and instructions on how to use Admintool to install DiskSuite packages, refer to the Solstice DiskSuite 4.1 Installation and Product Notes documentation available in the /cdrom/ solaris_srvr_intranet_ext_1_0/DiskSuite_4.1/Manuals directory.

For instructions on how to use DiskSuite, refer to the Solstice DiskSuite 4.1 User's Guide available in /cdrom/solaris_srvr_intranet_ext_1_0/ DiskSuite_4.1/Manuals directory.

Backup Utility

Solstice Backup is an easy-to-use network storage management software product. Backup performs automatic backups of files. You can also perform backups on an as-needed basis and archive project-related data for additional protection.

Backup automates the day-to-day process of backing up every computer on the network, thus protecting every system from file loss. Backup simplifies the management of backup media, gives notice of backup events, and is easy to operate and administer through an X Window System graphical user interface.

With Backup, file recovery is fast and convenient. Simply scroll through Backup's list of backed-up files and recover the files to disk. Backup even shows multiple versions of a file, backed up over time, enabling you to choose the version you want to recover. Backup provides access to these features through a graphical user interface. You can restore files to the same system or to a different one.

The optional Solstice Backup Archive Application provides the ability to take a snapshot of finished project files or directories residing on primary media, usually disk. To conserve disk space, you can choose to have archived files automatically removed from disk after Backup verifies the snapshot is safely stored on removable media.

Unlike backed-up data, the media used for storing archived data is never recycled. Archived data is preserved for as long as you need it. Archiving data associated with a finished project frees up space for current projects while assuring future access to the archived data.

Sun Microsystems offers four base versions of its data protection software, designed to meet varying needs. You can easily upgrade to more powerful and feature-rich versions as your environment changes and grows.

The following list describes the four base Backup products:

•  Solstice Backup Single Server backs up a single file server to a single backup device connected to that server. It provides no network backup support for clients. Storage management uses preconfigured settings only. The Solstice Backup Single Server is bundled with the Solaris WorkGroup and Enterprise Servers only and is not available as a separate orderable product.

•  Solstice Backup, Server Edition backs up a single file server to multiple backup devices connected to that server. It provides preconfigured settings and enables you to create your own configurations. It includes Solstice Backup Turbo functionality, supports the Jukebox Software Modules, Solstice Archive Application, Solstice Hierarchical Storage Management Application, Solstice Database Module for Oracle Application, and the Solstice Backup Simple Network Management Protocol module. The Server Edition supports media cloning, the process of making exact duplicates of backup tapes.

•  Solstice Backup, Network Edition backs up a heterogeneous network of systems to one or two backup devices. It provides preconfigured settings and enables you to create your own configurations. It includes support for ten clients with the option to purchase additional client connections.

•  Solstice Backup, plus Solstice Backup Turbo backs up a heterogeneous network of systems to a maximum of sixteen backup devices concurrently. It provides preconfigured settings and enables you to create your own configuration. It supports the Jukebox Software Module, Solstice Archive Application, Solstice Hierarchical Storage Management Application, Solstice Database Module for Oracle Application, and the Solstice Backup Simple Network Management Protocol Module. This product supports media cloning.

You configure a backup server: a system with a backup device that automatically backs up all the systems on a network. Then you specify systems to be recognized by the server as Backup clients. You install Backup client software on those clients.

Backup Files and Directories on the CD

The files and directories in the /cdrom/solaris_srvr_intranet_ext_1_0/ Backup_4.2.6 directory are listed in Table B-7.

Installing Solstice Backup

The following sections provide guidelines for installing Backup software. For complete instructions refer to the Solstice Backup 4.2 Installation and Maintenance Guide documentation available in the /cdrom/ solaris_srvr_intranet_ext_1_0/Backup_4.2.6/Manuals directory.

The CD contains all of the Solstice Backup software:

•  Backup Administrator, Backup, and Recover programs

•  Upgrade to Backup Turbo

•  Support for additional client connections

•  Optional Solstice Jukebox Software Module

•  Optional Solstice Archive Application

•  Optional Hierarchical Storage Management Application

•  Optional Simple Network Management Protocol Module

•  Electronic versions of the Backup documentation set for UNIX in HTML and PostScript format

Your CD-ROM contains the Backup software for a server and clients of the same hardware platform. After installing the software on your server, use the same CD to install the client software on your Backup clients.

The clients may access the Backup software over the network or have it installed locally on their hard disks. Refer to Part 3 for information about using the automounter to provide network access to the Backup software. Refer to Part 5 for information about administering application software. If you install the software locally, you need to extract and install the software on each client system.

---

NOTE:  Once installed, you can use Backup for 30 days. After 30 days, if you have not already done so, you must purchase the appropriate enables for the Backup products you want or the software will time-out. Once enabled, you must register the Backup software as soon as possible. If you do not register Backup, it will time-out 45 days from the date you enabled it. You will not be able to Backup any more data until you register and authorize the software.

---

In summary, you must complete the following tasks to install and use Backup:

•  Install Backup server software on the server

•  Install Backup client software either on the server or on each client system

•  Enable and register the Backup products

Reviewing Disk Space Requirements

Table B-8 lists the default locations and space needed to install the Backup software.

To install Backup on a server, you need the following:

•  A directory (suggested name nsr_extract) for installing the Backup software. Make sure there is enough space in the default installation directory.

•  A directory on the server large enough for the Backup indexes (usually /usr/nsr). The installation script checks for space and suggests one or more locations for the indexes.

•  A directory with 679 KB of disk space for the Backup on-line manual pages (for example, /usr/man).

•  The system path name of the device used for extracting the Backup software. For example /cdrom for a system running SunOS 4.1.x.

•  The system path name of at least one nonrewinding backup device used by the Backup server to back up and recover files. For example, enter /dev/drst8 at the prompt for a system running SunOS 4.1.x. If you are using an optical jukebox to back up and recover data, use the raw name of the device. For example, use /dev/rsd1c instead of /dev/sd1c.

Installing Solstice DiskSuite for Solaris

To install DiskSuite software on the server:

1.  Become superuser.

2.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically. Refer to Appendix A for information about volume management and mounting CDs.

3.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/ Backup__4.2.6/Solaris/sparc | i386 and press Return.

4.  Type pkgadd -d . and press Return. A list of packages is displayed.

5.  Type the number of the package you want to install and press Return. If you install more than one package, separate the numbers with a comma.

6.  Follow the installation instructions displayed by the pkgadd command. For complete instructions refer to the Solstice Backup 4.2 Installation and Maintenance Guide available in the /cdrom/ solaris_srvr_intranet_ext_1_0/Backup_4.2.6/Manuals directory.

You use the same steps to install software on client systems.

Installing Solstice DiskSuite for SunOS

To install DiskSuite software on the server:

1.  Become superuser.

2.  Insert the product CD into your CD-ROM drive. If you system is running volume management, the CD is mounted automatically.

3.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/Backup__4.2.6/SunOS and press Return.

4.  Type ./nsr_ize and press Return.

5.  Follow the installation instructions displayed by the nsr_ize script. For complete instructions refer to the Solstice Backup 4.2 Installation and Maintenance Guide available in the /cdrom/ solaris_srvr_intranet_ext_1_0/Backup_4.2.6/Manuals directory.

You use the same script to install software on client systems.

Running Backup

To run Backup, type nwadmin& and press Return. For complete instructions on how to use Backup, refer to the Solstice Backup 2.3 User's Guide available in the /cdrom/solaris_srvr_intranet_ext_1_0/ Backup_4.2.6/Manuals directory.

TotalNET Advanced Server (TAS)

The TotalNET Advanced Server (TAS) 5.0 software provides transparent PC to UNIX connectivity. It enables a UNIX server to act as a file, print, and application server to a variety of client PCs in a heterogeneous, networked environment. TAS gives the following PC systems access to the same UNIX file, print, and server resources through each client's familiar desktop interface:

•  Macintosh

•  MS-DOS

•  Windows for Workgroups

•  Windows 95

•  Windows NT

•  OS/2 Warp

TAS is organized into three realms according to clients served and available network transport protocols:

•  AppleTalk Compatible Realm, for AppleTalk clients, with the AppleTalk transport

•  LM-NT-OS/2 Compatible Realm, for NetBIOS clients, with either TCP/IP or NetBEUI transport

•  Netware Compatible Realm, for NetWare clients, with the IPX/SPX transport

TAS provides an HTML-based tool called TotalAdmin to facilitate ease of installation, configuration, and administration. TotalAdmin enables administrators without extensive UNIX experience to use UNIX technology to meet their PC server needs. TotalAdmin also presents a single, consistent interface for managing various communication protocols used within the TAS realms.

TAS benefits the clients in a heterogeneous networked environment by enabling each client to use a familiar desktop to access server resources. To access TAS, client workstations need only the native networking software included with their operating systems. End users do not need any additional training or expertise to exploit UNIX resources because additional file and print services are presented within their particular user interface.

TAS Files and Directories on the CD

The files and directories in the /cdrom/solaris_srvr_intranet_ext_1_0/ Totalnet_Advanced_Server/solaris2_5 directory are listed in Table B-9.

Installing Solstice TAS

The following sections provide guidelines for installing TAS software. For complete instructions refer to the TotalNET Advanced Server Version 5.0 Release Notes available in the /cdrom/solaris_srvr_intranet_ext_1_0/ Totalnet_Advanced_Server/solaris2_5/docs directory.

Upgrading from TAS 4.1.1

TAS 5.0 is a major upgrade from TAS 4.1.1 and the two versions cannot operate together. Before proceeding with an upgrade, back up your entire TAS directory and then run the tconvert utility. The tconvert utility reads the existing server configuration files, converts the information, and writes the output to the log file at /etc/totalnet/convert. When the installation is complete, the converted files are placed in the TotalNET home directory TNHOME.

You must run the tconvert program as root before existing TotalNET servers are removed, and with existing TotalNET servers shut down.

For complete instructions on upgrading from TAS 4.1.1, refer to the TotalNET Advanced Server Version 5.0 Release Notes.

Reviewing System Requirements

The following list describes the system requirements for installing TAS on Solaris 2.x SPARC or x86 systems:

•  Solaris 2.4 or later operating environment on a SPARC or x86 system.

•  For systems running NetBEUI or AppleTalk over Token Ring on SPARC systems, you must install the following token-ring driver patch that fixes the multicast problem: token-ring for SPARC patch #102463-03. This patch is available from SunSoft.

•  For Solaris 2.5.1 and x86 systems, Driver update 6 is recommended if running either NetBEUI, IPX, or AppleTalk protocols.

•  Approximately 26 MB of free disk space in the /usr partition.

Installing Acrobat Readers

TAS 5.0 is bundled with Adobe's Acrobat Reader, version 3.0. To install an Acrobat reader, change to the /acroread directory and choose the reader relevant to your platform. Follow the installation instructions in the INSTGUID.TXT file and install the reader onto the appropriate directory of the server or the client PC.

---

NOTE:  Although the installation instructions say that TAS 5.0 is bundled with Adobe's Acrobat Reader, version 3.0, these files are not available on the Solaris Server Intranet Extension CD-ROM. Contact your Sun sales representative for more information.

---

Installing TAS

To install TAS software:

1.  Log in as root at the system login prompt.

2.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically. Refer to Appendix A for information about volume management and mounting CDs.

3.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/ Totalnet_Advanced_Server/ solaris2_5/sparc | i386 and press Return.

4.  Type pkgadd -d . and press Return. A list of available packages is displayed.

5.  Type the numbers of the packages you want to install, separated by commas, or press Return to install all packages.

6.  Answer yes to all prompts for the remainder of the installation.

7.  When the prompt is redisplayed, type q and press Return to quit the pkgadd program.

For complete installation instructions refer to the TotalNET Advanced Server Version 5.0 Release Notes available in the /cdrom/ solaris_srvr_intranet_ext_1_0/Totalnet_Advanced_Server/docs directory.

Connecting to TotalAdmin

To continue installation and configuration, you must connect to TotalAdmin and access the Getting Started Guide. Follow the instructions in the Getting Started Guide to complete the initial configuration wizard and start the TAS server.

The port number for connecting to TotalAdmin is displayed during the installation process. Make a note of the port number because you need to use it later. If you do not see the port number, you can find it in the /var/totalnet/tassetup.log file.

To connect to TotalAdmin:

1.  Using a Web browser, type http://hostname:<nnnn> and press Return. <nnnn> is the port number for TotalAdmin.

2.  From the Product Selection screen, click the link for the TotalAdmin main menu.

3.  At the bottom of the TAS 5.0 main menu, click the On-line Documentation and Readers link.

4.  Click the Getting Started Guide. If the appropriate Acrobat Reader for your platform is installed, clicking on the link activates it. If you do not have the Acrobat Reader for your platform, refer to the TotalNET Advanced Server Version 5.0 Release Notes for instructions on how to install it.

5.  Run either the Initial Configuration Wizard or the tnsetup script to complete the installation and initial configuration of TAS. Refer to the Getting Started Guide for instructions on running both the Initial Configuration Wizard and the tnsetup script.

Sun WebServer

Sun WebServer 1.0 is designed for ISPs and corporations whose Internet/intranet servers must be high performance, scalable, and able to handle large numbers of users and transactions.

The following list describes the key features of the Sun WebServer:

•  SSL 3.0 and certificate-based security is provided for secure transactions.

•  Extensive and flexible access control includes URL-based access control and delegation.

•  Web-based administration enables you to administer the system from any Web browser on any platform.

Sun WebServer Files and Directories on the CD

The files and directories in the /cdrom/solaris_srvr_intranet_ext_1_0/ Sun_WebServer_1.0/Sol_2.5.1+ directory are listed in Table B-10.

Installing Sun WebServer

The following sections provide guidelines for installing Sun WebServer software. For complete instructions refer to the Sun WebServer 1.0 Installation and Release Notes available in the /cdrom/ solaris_srvr_intranet_ext_1_0/Sun_WebServer_1.0/Sol_2.5.1+/common/Docs directory.

Reviewing System Requirements

The following list describes the system requirements for installing Sun WebServer on Solaris 2.x SPARC or x86 systems:

•  Platform: SPARC or Intel 486 (or greater).

•  System Software: Solaris 2.5, 2.5.1 or 2.6 system software.

•  Disk Space: Approximately 24 MB of disk space.

•  Memory: For SPARC systems, a minimum of 32 MB, 64 MB recommended. For x86 systems, a minimum of 16 MB, 32 MB recommended.

•  Swap space: for SPARC systems, a minimum of 64 MB, 192 MB recommended. For x86 systems, 64 MB, 96 MB recommended.

•  Supported Web Browsers: Sun Microsystems HotJava 1.0, Netscape Navigator 2.01 and greater, Microsoft Internet Explorer 3.0 and greater.

Installing Sun WebServer

Table B-11 describes the Sun WebServer packages:

Sun WebServer installs the packages in the default locations listed in Table B-12.:

You must always install the security tools packages to their default locations. Install the SUNWhttp packages only in custom locations.

To install Sun WebServer software:

1.  Become superuser.

2.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically. See Appendix A for information about volume management and mounting CDs.

3.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/ Sun_WebServer_1.0/Sol_2.5.1+/sparc | i386/Product and press Return.

4.  Type pkgadd -d . and press Return. A list of available packages is displayed as follows.

castle# pkgadd -d .

The following packages are available:
  1  SUNWfns     Federated Naming System
         (sparc) 11.5.1,REV=97.05.07.01.10
  2  SUNWhttpr   HTTP server root package
         (sparc) 1.0
  3  SUNWhttpu   HTTP server user package
         (sparc) 1.0
  4  SUNWhttpv   HTTP server var package
         (sparc) 1.0
  5  SUNWski     SKI 1.0 Software (User Package)
         (sparc) 1.0
  6  SUNWskica   SKI 1.0 Software (CA Package)
         (sparc) 1.0
  7  SUNWskicw   SKI 1.0 Software (Licensing Package for CA)
         (sparc) 1.0
  8  SUNWskimc   SKI 1.0 Software (CA Manual Page Package)
         (sparc) 1.0
  9  SUNWskimu   SKI 1.0 Software (User Manual Page Package)
         (sparc) 1.0
 10  SUNWssl     SSL 1.0 Software (Library Global Version)
         (sparc) 1.0

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

5.  Type 1,5,6,7,8,9,10,3,4,2 and press Return. You should install the packages in the order specified, with the SUNWhttpu, SUNWhttpv, and SUNWhttpr packages last because they depend on some of the other packages.

6.  Follow the installation instructions displayed by the pkgadd command. For complete instructions refer to the Sun WebServer 1.0 Installation and Release Notes available in the /cdrom/solaris_srvr_intranet_ext_1_0/ Sun_WebServer_1.0/Sol_2.5.1+/common/Docs directory.

7.  When the prompt is redisplayed, type q and press Return to quit the pkgadd program.

Running Sun WebServer

For security reasons, do not run Sun WebServer as user root or user nobody. It is a good idea to create a second user such as http and have the Sun WebServer HTTP daemon run under that username. To change the daemon username, you can modify the server_user and cgi_user directives in the httpd.conf file. For more information about Web server security issues refer to the security FAQ at: http://www-genome.wi.mit.edu/WWW/faqs/ www-security-faq.html.

You must start Sun WebServer as root to run on port 80. When you start Sun WebServer as root, it binds to its ports and changes its username to whatever server_user is. Only user root can use ports below 1024. Therefore, unless you change the default port setting, you must start httpd as user root even if it runs as another user. For example, if you run /usr/lib/hpptd as user http, it won't be able to bind to port 80. Therefore, you need to run on a port above 1024.

You can change the default port setting by editing the <install_root>/etc/http/httpd.conf file. If you install Sun WebServer on a port other than 80, you need to designate the port number when accessing Sun WebServer with a Web browser. For example, to access server castle on port 8080, you would type http://castle:8080/.

To run Sun WebServer, type /etc.init.d.httpd start and press Return. For complete instructions on how to use Sun WebServer, refer to the Sun WebServer v1.0 Administration Guide available in the /cdrom/ solaris_srvr_intranet_ext_1_0/Sun_WebServer_1.0/Sol_2.5.1+/common/Docs directory.

Solstice Internet Mail Server (SIMS)

Solstice Internet Mail Server (SIMS) 2.0 is composed of Internet message access protocol V4 (IMAP4) mail server for Solaris systems plus support for the following mail client systems:

•  Solaris

•  Microsoft Windows 3.1.x

•  Windows 95

•  Windows NT

Supported Network Communications Protocols

SIMS is an implementation of the server side of IMAP4 RFC 1730. IMAP4 is used by client mail applications to access Internet messages in distributed enterprise/Internet-wide message stores. In addition to IMAP4, SIMS 2.0 also supports the following protocols:

•  Post Office Protocol v3 (POP3) server for mailbox retrieval and support of popular mail clients such as Eudora and Pegasus

•  Multipurpose Internet Mail Extensions (MIME) standard for mail attachments

Supported Mail Access Models

Mail can be accessed in one of three ways:

•  Online

•  Off-line

•  Disconnected

In the online model, messages remain on a server and are remotely responded to by the mail client. Online access ensures that you can easily manage a single message store, but requires remote connection while users read and compose mail.

In the off-line model, the mail client fetches messages from a server system to a client system--which may be a desktop or portable system--and may delete them from the server. The mail client downloads the messages where users view and respond to them at their convenience.

In the disconnected model, the mail client connects to the server, makes a cache copy of selected messages, then disconnects from the server. Users may read and respond to the messages off-line. The mail client can later reconnect and resynchronize message status between the server and the client message cache. A key concept of this model is that the master copies of messages remain on the mail server where manageability and security are high, but enables the remote, off-line manipulation of selected messages.

Online and disconnected operations complement each other, as users can alternate between them depending on their needs. Off-line access, however, is incompatible with either online or disconnected models because the messages on the server can be removed after downloading to the client system.

SIMS 2.0 supports disconnected computing for mobile or remote users. The network traffic load is reduced by moving the mail message format parsing to a centralized server, thereby freeing up the local mail applications to concentrate on user interface issues. Users can send and receive messages in online, off-line, or disconnected modes. SIMS works equally well in connected, high-bandwidth modes of operation as in disconnected, remote access modes, using a low-bandwidth network connection.

SIMS 2.0 listens on TCP port 143 for the mail client to send a connection request. Once the connection is established, the server responds to commands sent from the client. When a session is complete, the client sends a logout command to the server, terminating the session and closing the TCP connection.

SIMS Features

SIMS 2.0 provides the following features:

•  Handles mail storage on the mail server instead of the mail client. This architecture reduces network load and provides flexibility in accessing mail remotely through a low-bandwidth connection.

•  Stores and fetches messages in response to a client mail request. IMAP4 functionality enhances connection performance over low-bandwidth links by fetching message headers to the client without downloading the entire message set. Mailboxes and mail folders stay resident on the server, so users can search for specific mail attributes and then download selected messages.

•  Supports management and access of multiple mailboxes. Users can name and access both Inbox and archive mail folders. Additionally, users can create, delete, list, and rename both inbox and archive message folders. Users can perform these actions on the same or on different servers; SIMS 2.0 enables users to view and move messages from one to another at the same time.

•  Supports concurrent updates and access to common mailboxes and folders. Changes in mailbox state can be updated in all concurrently active mail clients.

•  You can set standard and user-defined message status flags to notify mail users of changes in message status.

•  Supports efficient processing of MIME attachments. Users can selectively retrieve individual attachments in messages. For example, if a two-line mail message has several large attachments, users can search for the mail attachment header and download only the one they want.

•  Exchanges mail with a broad assortment of mail clients with a single system view, so users' mail looks the same from any client application.

•  Supports read-only or read/write shared mailboxes and folders.

SIMS Files and Directories on the CD

The files and directories in the /cdrom/solaris_srvr_intranet_ext_1_0/ Solstice_Internet_Mail_Server directory are listed in Table B-13.

Installing SIMS 2.0

The following sections provide guidelines for installing SIMS 2.0 software. For complete instructions refer to the Solstice Internet Mail 2.0 Installation and Configuration Guide available in the /cdrom/ solaris_srvr_intranet_ext_1_0/ Solstice_Internet_Mail_Server/docs directory.

Reviewing System Requirements

The following list describes the minimum system requirements for installing SIMS 2.0 on a Solaris host:

•  Solaris 2.4 or later with a fully installed and configured sendmail program.

•  A SPARC or x86 workstation.

Removing Previously Installed SIMS Software

If you have installed an earlier SIMS release, you must remove it before installing your new software.

To remove previously installed software:

1.  Log in to the mail server as root or superuser.

2.  Type pkgrm SUNWimap and press Return.

3.  Answer yes to any questions displayed by the pkgrm program.

Installing SIMS Software

To install SIMS software:

1.  Log in as root or superuser.

2.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically. Refer to Appendix A for information about volume management and mounting CDs.

3.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/Solstice_Internet_Mail/server/ sparc | i386 and press Return.

4.  Type pkgadd -d . and press Return. A list of packages is displayed.

castle# cd /cdrom/solaris_srvr_intranet_ext_1_0/Solstice_Internet_
 Mail_Server/server/sparc
castle# pkgadd -d .

The following packages are available:
  1  SUNWimap     Solstice Internet Mail IMAP4 Server
         (sparc) 2.0
  2  SUNWipop    Solstice Internet Mail POP3 Server (NL)
         (sparc) 2.0

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

5.  If you want only the IMAP4 server type 1 and press Return. If you also want the POP server, type all and press Return.

6.  Answer yes to any questions displayed by the pkgadd program.

7.  When the prompt is redisplayed, type q and press Return to quit the pkgadd program.

For complete instructions refer to the Solstice Internet Mail 2.0 Installation and Configuration Guide available in the /cdrom/ solaris_srvr_intranet_ext_1_0/ Solstice_Internet_Mail_Server/docs directory.

Licensing Information

SIMS 2.0 requires a license token from Sun, as described in the Solstice Internet Mail 2.0 Installation and Configuration Guide. The license card is included in the CD-ROM package. Contact the appropriate license center to receive your password. You can find contact information on the Web site at http://www.sun.com/licensing.

You install the password by using the /opt/SUNWimap/bin/simslicense utility or by manually editing the license.dat file in the /etc/opt/SUNWimap/ license_dir4 directory.

The license is a single line of text that begins with the word FEATURE and is followed by solstice.mail.imap. If you choose to manually edit the file, make sure the line is located before any other line starting with FEATURE in the file. Only the first feature of a given type is used, even if it is expired.

If you are able to log into the mail server from your mail client, the server license is activated properly.

Configuring the Mail Server

The IMAP4 and POP3 daemons are started by the inetd daemon. During the server package installation, pkgadd automatically configures the mail server by adding an entry to the following two configuration files:

•  /etc/services

•  /etc/inetd.conf

The /etc/services configuration file should contain the following two lines:

imap   143/tcp imap   #Internet Mail Access Prot
pop-3  110/tcp pop3d  #Post Office Protocol 3

The /etc/inetd.conf configuration file should include the following two lines:

imap stream tcp nowait root /opt/SUNWimap/lib/imapd imapd
pop-3 stream tcp nowait root /opt/SUNWipop/lib/ipop3d ipop3d

The server's inetd daemon is restarted automatically during the installation process.

If you get an error during connection, it means that the inetd daemon looked for the inetd configuration file before the configuration table was updated. To restart the inetd daemon:

1.  Type /usr/bin/ps -ef | grep inetd and press Return. Note the PID number for inetd.

2.  Type kill -HUP <pid> and press Return.

You also need to verify that the services entry in the /etc/nsswitch.conf file is set to files. To verify the services entry in the /etc/nsswitch.conf file:

1.  Type grep services /etc/nsswitch.conf and press Return. The command should return services: files. The entry may also contain NIS or NIS+, but files must be the first entry.

2.  If files is not the first entry, manually change the services entry by using NIS or NIS+ administration procedures. Refer to Part 2 for information about administering NIS+.

Verifying a Successful Installation

To test for a successful installation, type telnet <mailserver> 143 and press Return.

If a message similar to the following is displayed, the server is installed and running:

* OK <mailserver> Solstice (tm) Internet Mail Server (TM)
 IMAP4 service - 2.0 - at <date>

Java IDL

Java IDL (Interface Definition Language) is the application platform for Internet client/server computing. Java IDL, Sun's 100% Pure Java Object Request Broker (ORB) system, provides the software foundation necessary to deliver enterprise client/server applications for the Internet. Applications that use Java IDL seamlessly integrate with non-Java programs and programs from other vendors. The Java IDL system is based on the latest CORBA and IIOP industry standards.

Java IDL includes:

•  100% Pure Java Object Request Broker

•  Full Internet Inter-ORB Protocol (IIOP) implementation

•  CORBA 2.0 standard IDL to Java mapping

•  CORBA 2.0 standard Naming Service

The Java IDL 1.1 runtime system is included with the Solaris Server Intranet Extension 1.0 CD-ROM. In addition, you can download the complete runtime and developer package from the Web site http://www.sun.com.solaris/java-idl/ index.html.

The developer package includes the IDL to Java compiler and related documentation for developing Java IDL applications.

Java IDL is a Java API as defined by JavaSoft. For more information, visit http://java.sun.com/products/jdk/idl/.

Java IDL is part of JavaSoft's platform APIs. It provides standards-based interoperability and connectivity with CORBA, the open industry standard for heterogeneous computing. As part of the Java Enterprise API set, Java IDL enables seamless interoperability and connectivity to heterogeneous enterprise information assets.

Java IDL leverages the efforts of OMG (Object Management Group)'s CORBA, IIOP, and IDL.

The Java IDL Language Mapping Specification defines the mapping from IDL to Java. The idltojava tool automatically generates stub code for specific remote interfaces. These stubs are ORB independent and call into ORB specific protocol modules for all data marshalling or other ORB specific operations. Java IDL also includes nameserv, an implementation of the CORBA (COS) name service. The portable Java ORB core which supports IIOP version 1.0 is structured to make it easy to plug in new ORB protocols.

Java IDL Files and Directories on the CD

The files and directories in the /cdrom/solaris_srvr_intranet_ext_1_0/ JavaIDL_1.1/Sol_2.5.1+/common directory are listed in Table B-14.

Installing Java IDL

The following sections provide guidelines for installing Java IDL 1.1 software. For complete instructions refer to the Java IDL 1.1 Manual Installation Guide available in the /cdrom/ solaris_srvr_intranet_ext_1_0/ JavaIDL_1.1/Docs directory.

Reviewing System Requirements

The following list describes the minimum system requirements for installing Java IDL 1.1 on a Solaris host:

•  Solaris 2.5.1 or later

•  JDK 1.0.2 or later

•  Clients (Microsoft Win 32) Win NT 3.5.1 or higher, Windows 95 Visual C++ 4.0 or higher

•  One of the following Web browsers to run Java IDL applets: HotJava 1.0 or later, Netscape Navigator 3.0.2 or later, Microsoft Internet Explorer 3.0.2 or later

Installing Java IDL Software

To install Java IDL software:

1.  Type pkginfo SUNWjvrt and press Return. If the JavaVM runtime environment is not installed, install it or install JDK 1.1 or later on your system.

2.  Log in as root or superuser.

3.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically. Refer to Appendix A for information about volume management and mounting CDs.

4.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/JavaIDL_1.1/ 2.5.1+/common/Product and press Return.

5.  Type pkgadd -d SUNWOirun and press Return.

6.  At the prompt type /usr/java and press Return.

7.  Answer yes to any questions displayed by the pkgadd program.

8.  When the prompt is redisplayed, type q and press Return to quit the pkgadd program.

Starting the Name Server

On Solaris, you must be root to run the name server because, by default, it uses port 900 as the initial port.

To start the name server:

1.  Become superuser.

2.  Type tnameserv -ORBInitialPort and press Return.

Solstice PPP 3.0.1

Solstice point-to-point protocol (PPP) is the ideal solution for system administrators who want to:

•  Set up an Internet or office server to service multiple clients.

•  Set up multiple clients to access an Internet or office server.

•  Enable mobile communications and telecommuting.

•  Conduct frequent or bulk transfers over leased lines.

•  Connect interoffice networks and distributed resources.

•  Interconnect LANs over wide area networks.

Solstice PPP implements asynchronous and synchronous PPP in a single homogeneous environment. Asynchronous PPP enables Solaris systems to route IP traffic over public and private telephone networks and is targeted at the growing Internet client/server market. Synchronous PPP enables Solaris systems to route IP traffic over dedicated leased lines and is used primarily for LAN-to-LAN interconnectivity and to replace dedicated routing equipment.

Solstice PPP 3.0.1 provides software for both PPP clients and PPP servers. The Solstice PPP Client initiates connections across public and private telephone networks through a single modem link. You are authorized to install and use the Solstice PPP client on an unrestricted number of systems.

The Solstice PPP Server provides all the functionality of a PPP server, including synchronous connectivity, support for up to 512 modems, support for IP routing, and the capability to accept incoming connections. This product incorporates a floating-license system that restricts the number of Solstice PPP servers that can run concurrently. To access all of the features of the Solstice PPP server, you must purchase and obtain a license password.

Solstice PPP 3.0.1 Files and Directories on the CD

The files and directories in the /cdrom/solaris_srvr_intranet_ext_1_0/ PPP_3.0.1 directory are listed in Table B-15.

Installing Solstice PPP

The following sections provide guidelines for installing Solstice PPP 3.0.1 software. For complete instructions refer to Installing and Licensing Solstice PPP 3.0.1 available in the /cdrom/ solaris_srvr_intranet_ext_1_0/PPP_3.0.1/ docs directory.

The following list summarizes the installation process:

1.  Plan your installation to determine where to install the packages supplied with Solstice PPP and to ensure your systems meet the installation requirements.

2.  Request a license password from one of the authorized Sun license distribution centers. You can skip this step if you are upgrading from a previous version of Solstice PPP, or if you are using only the Solstice PPP client software.You can obtain information about your nearest License Distribution Center from the http://www.sun.com/licensing Web site.

3.  Install Solstice PPP packages.

4.  Install the license password.

5.  Configure and start Solstice PPP.

Reviewing System Requirements

The following list describes the minimum system requirements for installing Solstice PPP software:

•  Solaris 2.3 or later operating environment

•  X Window System window manager to use ppptool or the license installation tool (lit)

Table B-16 describes the PPP packages and lists the directory where the software is installed and the disk space requirements in MB.

The following modems have been tested and qualified for use with Solstice PPP:

•  AT&T DataPort Express

•  BocaModem V.34 DataFax

•  Cardinal V.34/V.FC 28.8 data/fax

•  Cardinal MVP288I 28.8 Kbps V.34 Fax Modem

•  Hayes Accura 144B and 288V.FC

•  Megahertz XJ2288 PCMCIA

•  Motorola Codex 326X V.34

•  MultiModem MT2834BLF

•  MultiModem MT1432BF

•  Olitec 288

•  Practical 14400 V32bis

•  SupraFaxModem 288

•  USRobotics Sporter 14400

•  USRobotics Sporter 288

•  USRobotics Courier V.34

•  Zoom V34

---

NOTE:  This information does not imply a support contract, commitment to continued compatibility, or warranty from Sun Microsystems, Inc. for any of the listed devices.

---

Table B-17 lists synchronous serial interfaces that have been tested and qualified for use with Solstice PPP.

Table B-18 lists asynchronous serial interfaces that have been tested and qualified for use with Solstice PPP.

---

NOTE:  The SPC board is not supported.

---

Reviewing Licensing Requirements

The Solstice PPP server incorporates a floating license system. Each license entitles you to one or more Rights To Use (RTUs), according to the number requested when you ordered the product. This number defines the maximum number of Solstice PPP servers that can run concurrently. You can install the software on a larger number of systems.

You can purchase additional licenses without purchasing extra copies of the software. You can add these licenses to your existing license configuration.

The systems on which you install the license daemon are called license servers. Each license server can handle the licenses for multiple license clients, providing the server is accessible across an existing network.

You can choose from the following possible license server configurations:

•  Single-independent license server: This configuration is the simplest and most frequently used. The license daemon is installed on a single system and a single password is required to enable all of the associated RTUs. All clients access the same license server.

•  Multiple-independent license servers: You can share the total number of RTUs that you purchased between multiple-independent license servers. This configuration enables you to define separate workgroups that access a subset of the total RTUs. You must obtain a unique password for each license server in your configuration.

•  Multiple-redundant license servers: Three license servers can work together to emulate a single-independent license server. This configuration improves stability of the license system because licensed products will not shut down as long as the majority of license servers is accessible and able to communicate. A single password enables all of the RTUs.

If you are installing Solstice PPP for the first time, you must contact your nearest Sun license distribution center to obtain the passwords that enable the license system. When you contact the License Distribution Center, you need the following information:

•  The product serial number which is printed on the label located on the license certificate supplied with the product.

•  A description of your license server configuration (single-independent, multiple-independent, or multiple-redundant).

•  The hostname and hostid of each license server.

•  The number of SPARC and x86 RTUs you require.

You can obtain information about your nearest License Distribution Center from the http://www.sun.com/licensing Web site.

Installing PPP Software

To install PPP software:

1.  Become superuser.

2.  If you have a previous version of Solstice PPP installed, type pkgrm SUNWpppk SUNWpppr SUNWpppu and press Return to remove the packages.

3.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically. Refer to Appendix A for information about volume management and mounting CDs.

4.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/PPP_3.0.1/sparc | x86 and press Return.

5.  Type pkgadd -d . and press Return. A list of the packages is displayed.

castle# pkgadd -d .

The following packages are available:
   1  SUNWlicsw     FlexLM License System
           (sparc) 4.1
   2  SUNWlit       STE License Installation Tool
           (sparc) 3.0
   3  SUNWpppk      Solstice PPP Device Drivers
           (sparc) 3.0.1
   4  SUNWpppm      Solstice PPP Man Pages
           (sparc) 3.0.1
   5  SUNWpppr      Solstice PPP Configuration Files
           (sparc) 3.0.1
   6  SUNWppps      Solstice PPP Login Service
           (sparc) 3.0.1
   7  SUNWpppu      Solstice PPP Daemon and User Programs
           (sparc) 3.0.1
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

6.  Type the numbers corresponding to the packages you want to install, or press Return to install all of the packages. You can install the packages in any order.

7.  Answer yes to any questions displayed by the pkgadd program.

8.  When the installation is complete, type q to quit pkgadd.

9.  Eject the CD-ROM from the drive.

10.  Repeat the procedure for each system on which you want to run Solstice PPP.

11.  Install the license passwords. For complete instructions, refer to Installing and Licensing Solstice PPP 3.0.1 available in the /cdrom/solaris_srvr/intranet_ext_1_0/PPP_3.0.1/docs directory on the CD.

Getting Started with Solstice PPP

Once the installation is complete and license passwords are installed, Solstice PPP is ready to configure and use. You configure Solstice PPP for the first time using the pppinit initialization script.

Refer to Configuring and Using Solstice PPP Clients and Configuring and Using Solstice PPP Servers and Routers for detailed information on configuring and using this product.

SunScreen SKIP

SKIP (Simple Key-management for Internet Protocols) software provides encryption for your data and authentication of the IP traffic stream. SunScreen SKIP enables you to securely conduct business over both the corporate intranet and the Internet.

SunScreen SKIP provides the most flexible methods to conduct business over an intranet or the Internet with the SunScreen SKIP product line. An easy-to-install software module, SunScreen SKIP provides secure communications transparently to users without requiring any modification of existing applications.

With SunScreen SKIP:

•  Telecommuters and business travelers can remotely get to their corporate network services and businesses can securely place orders with their vendors.

•  Customers can confidently perform financial transactions with their bank.

•  Retail businesses can process credit card transactions for their customers.

SunScreen SKIP authenticates all incoming IP traffic. It also provides integrity and privacy of your outgoing data by ensuring that it will not be altered or viewed by others while in transit. SunScreen SKIP rounds out the security solution by interoperating with the SunScreen SPF-100/100G, and SunScreen EFS products. SunScreen SKIP is available on Solaris, Windows 3.11, Windows 95, and Windows NT operating systems.

While the SPF-100, SPF-200, and EFS products provide unparalleled security and encryption capabilities with site-to-site communication, SunScreen SKIP provides customers with the ability to communicate back to the corporate network server via the SPF-100 or EFS. Thus, a secure virtual private network is created with a client/server relationship. SunScreen SKIP also has client-to-client capabilities, enabling remote users to communicate among themselves just as securely and easily as they would with a network server.

SunScreen SKIP Files and Directories on the CD

The files and directories in the /cdrom/solaris_srvr_intranet_ext_1_0/ Skip_1.1.1 directory are listed in Table B-19.

Installing SunScreen SKIP

The following sections provide guidelines for installing SunScreen SKIP 1.1.1 software. For complete instructions refer to the SunScreen SKIP User's Guide available in the /cdrom/solaris_srvr_intranet_ext_1_0/Skip_1.1.1/docs directory.

Reviewing System Requirements

The following list describes the minimum system requirements for installing SunScreen SKIP 1.1.1 on a Solaris host:

•  Solaris 2.4 or later for SPARC or x86 platforms

•  Minimum of 16 MB of RAM is required, 32 MB of RAM is recommended.

•  A minimum of 6 MB of free disk space is required for installation. 3 MB of disk space is used permanently.

•  One or more supported network interfaces.

SunScreen SKIP supports the following protocol versions:

•  SKIP, Version 1, for SunScreen SPF-100/100G and SPF-200 compatibility.

•  Any platform that has implemented SKIP as described in the ICGT Technical Reports listed in Section 1.1.2, including the SunScreen product line, except SunScreen SPF-100, which only implements SKIP, Version 1.

•  Raw mode (also known as ESP/AH, manual keying, or S/WAN) for compliance with RFC 1825: Security Architecture for the Internet Protocol.

•  SunScreen SKIP Release 1.1 is the upgrade for SKIP for Solaris, Release 1.0.

To run SunScreen SKIP you must have the Solaris SunCore software group of packages installed. This software group contains the minimum software required to boot and run the Solaris operating system. It includes some networking software and the drivers needed to run the OpenWindows environment; it does not include the OpenWindows software. If you plan to use the skiptool GUI, install the packages for OpenWindows.

In addition, you must have installed the packages listed in Table B-20.

Installing SunScreen SKIP Software

To install SunScreen SKIP software:

1.  Become superuser.

2.  Insert the product CD into your CD-ROM drive. If your system is running volume management, the CD is mounted automatically. See Appendix A for information about volume management and mounting CDs.

3.  Type cd /cdrom/solaris_srvr_intranet_ext_1_0/SKIP_1.1.1/sparc | x86 and press Return.

4.  Type pkgadd -d . and press Return. A list of the packages is displayed.

castle# cd /cdrom/solaris_srvr_intranet_ext_1_0/Skip_1.1.1/sparc
castle# pkgadd -d .

The following packages are available:
  1  SICGbdcdr   SKIP Bulk Data Crypt 1.1.1 Software
          (sparc) 1.1.1
  2  SICGcrc2    SKIP RC2 Crypto Module 1.1.1 Software
          (sparc) 1.1.1
  3  SICGcrc4    SKIP RC4 Crypto Module 1.1.1 Software
          (sparc) 1.1.1
  4  SICGes      SKIP End System 1.1.1 Software
          (sparc) 1.1.1
  5  SICGkeymg   SKIP Key Manager Tools 1.1.1 Software
          (sparc) 1.1.1
  6  SICGkisup   SKIP I-Support module 1.1.1 Software
          (sparc) 1.1.1

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

5.  At the prompt press Return to install all of the packages.

6.  Answer yes to any questions displayed by the pkgadd program.

7.  When the packages are installed, type q and press Return to quit pkgadd.

8.  Add /opt/SUNWicg/bin to root's PATH variable.

9.  Add /opt/SUNWicg/man to root's MANPATH variable.

To complete the installation you must:

•  Generate and install SKIP Unsigned Diffie-Hellman (UDH) certificates or install SunCA certificates.

•  Install SunScreen SKIP on your network interface.

For information on how to complete these tasks, refer to the SunScreen SKIP User's Guide.

Using SunScreen SKIP

SunScreen SKIP provides two interfaces that you can use for configuring and managing the SunScreen SKIP software:

•  The graphical user interface tool: skiptool

•  The command-line interface: skiphost

Using skiptool is the easiest way to set up and administer SunScreen SKIP. The GUI allows you to enable and disable access to systems, set the type of encryption used for hosts or network connections to your system and determine how to deal with unauthorized hosts that try to connect to your system. It also enables you to view the following statistics:

•  Network interface

•  SKIP header

•  Key

•  Encryption

•  Authentication

To run skiptool, you must be able to enable access for any client to the X server for Solaris 2.x systems by entering the xhost +<localhost> command before you become root. You must be able to become root on your system.

To start skiptool:

1.  Type xhost +<localhost> and press Return.

2.  Become superuser.

3.  Type skiptool& and press Return.

Refer to the SunScreen SKIP User's Guide for complete information on how to use both skiptool and skiphost commands.