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 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 database prior to installation, or it will be overwritten.

When you have reloaded the ASCII data file containing your original database, 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 /usr/snm/snm-databases/db.mydata.

3. Be sure you have write permission and adequate space available in the directory where you want to save the file.

4. To ensure the old NetISAM lock table is unlocked, enter:

# rm /var/tmp/NETISAM.LOCKTABLE

Upgrade Procedures

Before installing the product on a machine that already has another version of the product installed on it, be sure to quit SNM, if it is running, stop the snmp (or snmpv2) daemon, and stop the agent processes. To locate the process numbers for the na.<agent-name> processes, enter the following command at a shell prompt:

hostname% ps -aux | grep na\.

If you have already installed a 2.x version of the product on the machine you wish to install the product on, you must first remove the previously installed software. Refer to Appendix B, "Removing Software," for more information.

After saving your database, you can 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 as described in Chapter 3, "Installing the Software."

2. Start the product by entering snm -i& or snm -i <database filename>&. Specifying the -i option initializes (in effect clearing) the runtime database -- any existing runtime database is deleted. If <database filename> is also specified on the command line, that file will be loaded into the runtime database.

   If you want to load the database that you have previously saved to an ASCII file, you can do this by entering that file name as <database filename> on the command line, For example, if you saved your 2.x runtime database to /var/snm/db.mydata, you can automatically load that database when starting the product if you enter:

hostname% snm -i /var/snm/db.mydata

If you start the product by specifying the database file to load at the command line, go directly to Step 5

3. If you entered snm -i & without specifying a database file, the Quick Start window will appear.

   SELECT the BasicStart (not HeadStart) icon from the Quick Start window to bring up the Console.

4. Using the File >> Load >> Management Database option, reload your original 2.x database file that you saved in Step 1.

   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.

Upgrading your Management Station

If you plan to upgrade your management station, you may want to preserve some of your current management capabilities. This appendix provides some guidelines to consider before you upgrade from earlier releases.

Differences in Configuration from SunNet Manager 2.0 to Site/SunNet/Domain Manager 2.3

Site/SunNet/Domain Manager 2.3 contains the following configuration changes as distinguished from the 2.0 release:

• If you install the product in a non-default location (that is, anywhere other than /usr/snm), you must do the following:

  · Set the SNMHOME environment variable to the installation directory.

  · Set the LD_LIBRARY_PATH environment variable to $SNMHOME/lib, or append $SNMHOME/lib to the LD_LIBRARY_PATH variable if it already exists.

• In the 2.3 release, the .SNMdefaults file contains an attribute snm.console.DBMgrTrapAlways. The default value for this attribute is false. If set to true, the Console generates database manager traps to inform other applications when new elements are added to the runtime database. The generated trap contains the names of the elements that have been loaded.

Differences in Agents Between Solaris 2.x and SunOS 4.x (Solaris 1.x)

A Console installed on a Solaris 1.1 machine can manage both Solaris 2.x clients and SunOS 4.x clients.

A number of agents are designed specifically to run on Solaris 2.x machines. These agents are based on agents that had been 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-1

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

See the Administration Guide for information on the new agents and attributes.

Differences in APIs from SunNet Manager 2.0 to Site/SunNet/Domain Manager 2.3

Site/SunNet/Domain Manager 2.3 contains minor Application Programming Interface (API) differences compared to the 2.0 release. See the Administration Guide for more information on manager and agent writers.

When you are ready to upgrade from an earlier release to Site/SunNet/Domain Manager 2.3, see Chapter 3, "Installing the Software," for instructions.