A.1 Saving Your Database for Upgrading

---

Caution - The following information is extremely important! Failure to read it could lead to the loss of your current management database.

---

Basically, the data records are compatible with earlier releases. When upgrading from one of these versions to Site/SunNet/Domain Manager 2.3, you must first save your own database records into an ASCII data file. It is very important to save your original runtime database prior to installation, or it will be overwritten.

When you have reloaded the ASCII data file containing your original database successfully, all of the element glyphs will be redisplayed and any requests started again.

To save your current 2.x runtime database into an ASCII data file:

1. From the Console, select the File >> Save option.

2. Specify the path and name of the file where you want to save your 2.x database in the Name: field.

   For example, you could save it to the /var/opt/SUNWconn/snm/db.mydata file.

3. Be sure to save the file to a directory with adequate space available.

A.2 Upgrade Procedures

Next you must install the software and start the Console. After the Console window appears, you have the option of reloading the ASCII data file in which you saved your original database back into the Console.

1. Install the product using the /usr/sbin/pkgadd utility.

2. Start the product by invoking snm -i& or snm -i <database filename>&.

3. SELECT the BasicStart icon from the QuickStart window to bring up the Console.

4. Only follow this step if you started the product without specifying the database file to use.

   Reload your original 2.x database file that you saved in Step 1 by using the File >> Load >> Management Database option. Specify the file you saved your original database to in the Name: field.

5. If the original database file loads successfully, the element glyphs will be displayed in the Console and, if there are any requests to be sent, they will be restarted.

A.3 Upgrading your Management Station

If you plan to upgrade your management station, you may want to preserve some of your current management capabilities. Following is a list of the steps you need to follow in order to accomplish the these tasks:

1. Make sure that any Site/SunNet/Domain Manager partner or other third-party Site/SunNet/Domain Manager application is available for Solaris 2.4 .

2. When you upgrade your operating system, you overwrite your system disk. There may be files that you want to save to either tape or another disk which won't be affected by the operating system upgrade. After you install Solaris 2.4 or later and Site/SunNet/Domain Manager, you can copy these files back onto your system. The following table lists some of the files that are candidates for backup.

Table A-1

File	Description
$HOME/.SNMdefaults $HOME/.Xdefaults	These files contain information relating to your user environment. They may contain path names (such as /usr/snm or /var/adm/snm) which must be changed for Site/SunNet/Domain Manager (such as /opt/SUNWconn/snm or /var/opt/SUNWconn/snm).
/etc/snm.conf /var/adm/snm/snmp.hosts /var/adm/snm/snmp.traps	These files may contain configuration changes you want to retain.
Your Site/SunNet/Domain Manager database	Save the existing MDB to ASCII using the Console Save option. After you install and start the product with the BasicStart option in the QuickStart window, reload the database from the Console Load option or restart the Console from the command line with the file name (for example, enter snm <filename>).
Any additions to the product hierarchy, such as: .third-party mibs and schemas .third-party applications .schema files .customized scripts .customized agents	Contact your supplier to be sure the third-party application is available for Solaris 2.4 . The command and programmatic interface is the same under 2.3 as under 2.0, 2.1, and 2.2. However, the new operating system may require changes to scripts and to existing agents in order for them to compile and run correctly.

3. If you have already installed an earlier version of the product on the machine you wish to install the product on, you must first do the following:

   a. Before removing the software from disk, be sure to quit the product software, if it is running on the systen where the new version is to be installed, and kill the agent processes. The na.<agent-name> process numbers can be displayed by entering the following command at a shell prompt:

hostname% ps -ef | grep na\.

b. After stopping product processes, the previously installed software is removed from disk by executing the pkgrm command. Refer to Appendix B, "Removing the Software," for information about removing software packages.

A.4 Differences in Agents Between SunOS 4.x and Solaris 2.x

A Console can manage both Solaris 2.x clients and SunOS 4.x clients. A number of agents were designed specifically to run on Solaris 2.x machines. These agents are based on agents that were designed to run on the SunOS 4.x operating system. To help you identify the Solaris 2.x agent, the number "2" has been appended to the original agent name. The table below shows the agents affected.

Table A-2

SunOS 4.x Agent	Solaris 2.x Agent
etherif	etherif2
hostmem	hostmem2
iostat	iostat2
layers	layers2