3.1 Adding SunNet Manager to Your PATH Variable

Use the command line to start SunNet Manager. To do this, you could type the full path name.

For example, if SunNet Manager was installed on a Solaris 2.x machine in the default location, you could enter:

host% /opt/SUNWconn/bin/snm &

However, to avoid typing the complete path each time you start the Console, set the PATH environment variable in your.cshrc file (or .profile file if you use a Bourne or Korn shell) to point to the location of the executable files (the SunNet Manager Console, and tools). For a C-shell, enter the following in your .cshrc file:

For Solaris 1.x:

setenv PATH ${PATH}:/usr/snm/bin

For Solaris 2.x:

setenv PATH ${PATH}:/opt/SUNWconn/bin

For a Bourne or Korn shell, consult the examples in your installation guide. Examples in the rest of this chapter assume that your PATH environment variable points to the appropriate location.

---

Note - If you installed SunNet Manager in a location other than the default (/usr/snm on Solaris 1.x machines, /opt/SUNWconn/snm on Solaris 2.x), you must set the environment variable SNMHOME to the installation directory before invoking the command to start SunNet Manager. See your installation guide for instructions for setting this variable.

---

3.2 Starting the Console

If no management database exists when you start the Console -- which is the case for first-time users--you receive a Quick Start window show in Figure 3-1.

Figure 3-1

If a database exists, you go directly to the SunNet Manager Console window shown in Figure 3-2.

Figure 3-2

---

Note - You can use the -q option to suppress the Quick Start window.

---

3.2.1 Startup Commands

• To start the Console when there is no database or to restart the Console with the runtime management database from the last Console session (assuming no intervening reboot), enter

host% snm &

Appending an ampersand (&) to the command line puts the command in the background.

• To start the Console and initialize (in effect clearing) the runtime database, enter the command below. You receive the Quick Start window.

host% snm -i &

---

Caution - Use the -i option with care. If you have created a runtime management database in a prior Console session, the -i option deletes this database.

---

• You can use the -i option in conjunction with the file name of an ASCII database file. For example:

host% snm -i /home/alex/snm/osaka.dbase &

This command deletes a runtime database, and loads the specified ASCII database file into the runtime database. The Quick Start window does not appear.

• A variation of the preceding command example is to specify an ASCII database, but not the -i option. The specified ASCII database file is merged into the runtime database. For example:

host% snm /home/alex/snm/osaka.dbase &

• The snm command has two additional command-line options, v1 and v2. Use the v1 option if you are loading database files used with SNM 1.x. Use the v2 option only if you are loading multiple database files, one or more, but not all, of which are for SunNet Manager version 1.x. The v2 option allows you to distinguish those files that are not from version 1.x. For example:

host% snm -v1 /home/alex/snm/west.dbase -v2 /home/alex/snm/osaka.dbase

3.2.2 Managing Duplicate Databases

Starting with version 2.3, if a database you specify has elements in common with a runtime database already present, you can either abort the database you are loading, ignore the duplicates and proceed with the load, or replace the old database with the new one from the ASCII database. See Chapter 18, "Management Database," for more information.

3.2.3 Disk Space Requirements

A minimum of 10-15 Mbytes of disk space should be available in the directory that stores the runtime database. You can check the available disk space with the following command:

• df -a (if you're running Solaris 1.x)
• df -k (if you're running Solaris 2.x)

You specify the database location during installation of SunNet Manager or by using the environment variable SNMDBDIR. If you have not specified SNMDBDIR, then the following directory is assumed:

• /var/adm/snm for Solaris 1.1.1
• /var/opt/SUNWconn/snm for Solaris 2.4

The disk space required may vary according to the size of the network being discovered. For example, a database that contains 647 components, 9 buses, and 11 views takes approximately 3.2 Mbytes of disk space. If your runtime database grows very large, your file system can run out of space. This can be a problem if the /var directory is in the root partition, which generally does not have a large amount of free disk space. In this case, you can change the directory specified by the SNMDBDIR environment variable to point to another partition with more free disk space.

---

Note - When the database directory is changed, the files under the current $SNMDBDIR should be moved to the new location to ensure smooth operation.

---

The new directory should be created with mode 777 so that the database files can be written to the directory. When you run the IP Discover Tool, both you (as user) and root must be able to write to this directory--therefore, you should locate the database on a local file system rather than an NFS-mounted file system. (NFS servers usually do not allow root users on remote machines to have write permission.)

3.2.4 Quick Start Window

After invoking SunNet Manager with the -i option or with no command-line arguments when there is no database present, you receive a Quick Start window.

You can suppress the Quick Start window by using the -q option. This option works when you invoke snm with no other options or with the -i option.

The Quick Start window has the HeadStart and BasicStart options. The Progress bar is dimmed. If you are a first-time user, HeadStart is recommended.

Clicking SELECT on the buttons has the following effects:

• The HeadStart button launches the SunNet Manager Console and discovers a few nodes (up to a maximum of ten) on the local subnetwork, so that you can begin using SunNet Manager immediately.
• The BasicStart button skips the discovery of local nodes and directly invokes the SunNet Manager Console window.

3.2.5 Console Window Characteristics

You can configure a number of Console window characteristics. For example, you can change text that appears in the title bar. For more information on changes you can make, see "Part 2: Reference."

You initiate most SunNet Manager activities through pull-down menus accessed in the abbreviated menu buttons in the Console's control area. The effect of a menu selection differs depending on whether or not you select a glyph in the Console window. In general, if you select a glyph, your menu choice affects only the highlighted element. If no glyph is selected, your menu choice either affects all elements or has no consequences for any single element.

3.3 Using IP Discover and IPX Discover

This section discusses the discover function of the IP Discover and IPX Discover tools. You use these functions normally when you first bring up the Console. More details on these tools is in Chapter 22, "IP Discover" and Chapter 23, "IPX Discover."

3.3.1 Using IP Discover

The IP Discover tool, invoked from the Tools menu in the Console window or from a command line, finds networks, subnetworks, routers, and hosts. By default, IP Discover limits search to the local subnetwork to which your SunNet Manager machine's Console is attached.

The IP Discover tool has two functions:

• IP Discover, which finds hosts, routers, networks, subnetworks, and Simple Network Management Protocol (SNMP) devices reachable from the Console machine. IP Discover stores a record in the runtime database for each element it finds.

• Monitor, which compares elements stored in the runtime database with the elements found at a specified interval or specified time. If new elements are detected, the monitor function stores elements in a holding area view (which you can name) and records these elements in a log file.

Both the discover and monitor functions have configuration windows, available through the Configuration Options button, that allow you to fine-tune the depth and breadth of the activities.

3.3.1.1 Invoking IP Discover

Use one of the following two methods to invoke the IP Discover tool:

1. Press MENU on the Tools button in the Console window.

2. Press MENU on Discover.

3. Release MENU over IP Discover.

4. You see the window shown in Figure 3-3.

Figure 3-3

5. Click SELECT on Start Discover to start the IP Discover function.

   The Start IP Discover button changes to Stop IP Discover. The IP Discover function continues to run, within the boundaries you have configured in your local subnetwork until it finds all elements within the subnetwork

6. Click SELECT on Stop Discover.

   From the SunOS command line, if you have the path to the SunNet Manager executables in your PATH variable, invoke snm_discover. For example, to run IP Discover and invoke the user interface, enter:

hostname# snm_discover -T

The path to snm_discover is:

• /usr/snm/bin on SunOS 4.x
• /opt/SUNWconn/snm/bin on Solaris 2.x

You can start IP Discover directly, bypassing the initial Home window if you use the snm_discover command without the -T option.

3.3.1.2 IP Discover Views Beyond the Local Subnetwork

IP Discover reports progress in the IP Discover Console Output window and adds elements to the current view in the SunNet Manager Console window. Simultaneously, it adds these elements to the runtime database.

Running IP Discover with the Default option will find network elements in the subnetwork to which the Console system is attached. If you enable IP Discover to reach beyond your local subnetwork, it constructs a hierarchy of views. See Chapter 22, "IP Discover," for more information. The Home view is the top level in the hierarchy of your management domain views.

1. Double-click the SELECT button on each network/subnetwork glyph to display the elements, usually hosts and routers, contained in each of these views.

   The console output section of the IP Discover window displays information about the program's progress.

You can display logical groupings of elements, such as routers in your management domain, or all the SNMP devices in a particular subnet.

2. Click SELECT on the Configuration Options button to display the Properties sheet.

Figure 3-4 shows the Properties sheet. For a description of fields, see Chapter 22, "IP Discover."

Figure 3-4

3.4 Using IPX Discover

Starting with version 2.3 of SunNet Manager, you can use IPX Discover to discover IPX Netware nodes and networks. See "Part 2: Reference" for detailed information on IPX Discover functionality.

3.5 Netware Management System Export/Import Agent

IPX Discovers and models IPX networks by communicating with a topology export/import agent (NXIS) located on the Novell Management platform (Managewise). NXIS exports topology data discovered by Managewise; Managewise need not be running during this process.

IPX Discover has scheduling capability and can be configured to periodically poll the NXIS agent for changes to the network.

Refer to the IPX Discover man page for command syntax.

3.6 Invoking IPX Discover

To invoke IPX Discover, follow the steps below

1. Click SELECT on the Tools Menu >> Discover >> IPX Discover to see the screen in Figure 3-5.

Figure 3-5

2. Click SELECT on Configuration to see the Properties sheet in Figure 3-6.

Figure 3-6

3.6.1 IPX Discover Options

From this point, you can use IPX Discover any of the following four ways:

A. Perform a load to export a database from the Export Services Agent without using the scheduler.

B. Perform a load using the scheduler without specifying time period to export the database.

C. Perform an update using the scheduler and specifying how often to report changes that have occurred on the Novell network.

D. Perform multiple loads and updates from multiple Export Services Agents.

Steps for each of these options are provided below.

A. Load without using the scheduler:

1. On the IPX Discover Properties sheet, enter the Server Name of the Novell export agent.

2. Enter the password for the Novell export agent.

3. Enter the IP address of the console on which the export agent resides.

4. Click SELECT on Add >> Apply.

5. On the IPX Discover Home screen, click SELECT on Discover.

B. Load using the scheduler without specifying period time:

1. On the IPX Discover Properties sheet, enter the Server Name of the Novell export agent.

2. Enter the password for the Novell export agent.

3. Enter the IP address of the console on which the export agent resides.

4. Click SELECT on Add.

5. Click SELECT on Schedule Discover.

6. Enter Start and Stop Dates in the appropriate date format.

7. Click SELECT on Start Time and Stop Time, and choose the desired times.

8. Click SELECT on am or pm button.

9. Click SELECT on Add >> Apply.

10. On the IPX Discover Home screen, click SELECT on Discover.

    C. Update using the scheduler and specifying period time:

1. On the IPX Discover Properties sheet, enter the Server Name of the Novell export agent.

2. Enter the password for the Novell export agent.

3. Enter the IP address of the console on which the export agent resides.

4. Click SELECT on Add.

5. Click SELECT on Schedule Discover.

6. Enter Start and Stop Dates in the appropriate date format.

7. Click SELECT on Start Time and Stop Time, and click on the desired times.

8. Click SELECT on am or pm button.

9. Click SELECT on Period Time button, and click on the desired time.

10. Click SELECT on am or pm button.

11. Click SELECT on Add >> Apply.

12. On the IPX Discover Home screen, click SELECT on Discover.

    D. Perform multiple loads and updates with multiple export agents:

1. On the IPX Discover Properties sheet, enter the Server Name of the first Novell export agent.

2. Enter the password for the Novell export agent.

3. Enter the IP address of the console on which the export agent resides.

4. Click SELECT on Add.

5. For each additional export agent, follow steps 1 - 3.

6. Click SELECT on Schedule Discover.

7. Enter Start and Stop Dates in the appropriate date format.

8. Click SELECT on Start Time and Stop Time, and click on the desired times.

9. Click SELECT on am or pm button.

10. Click SELECT on Period Time button, and click on the desired time.

11. Click SELECT on am or pm button.

12. Click SELECT on Add >> Apply.

13. On the IPX Discover Home screen, click SELECT on Discover.

3.6.2 Change, Remove, and Reset Options

To change the configuration of an IPX Discover, enter new information in the appropriate fields and click SELECT on Change >> Apply >> Start Discover.

To remove a configuration from the Export Agent Services list, use the mouse to highlight you choice, then click SELECT on the Remove button.

To reset your configuration if you have not clicked on the Add button, click SELECT on the Reset button. All fields become blank. If you have clicked on the Add button, click SELECT on the Change button.

3.7 Traversing the View Hierarchy

Whenever you start the Console, the Home view is displayed. Elements that are views can contain other elements, including other views. Other types of elements, such as components, can also contain other elements. The Console keeps track of up to 16 different views or elements as they are displayed. You can traverse through the Console view hierarchy in several ways.

1. If the element is a view, double-click SELECT over the glyph that represents the element to display the elements contained in the view.

2. To return to any of the views that have already been displayed, press MENU on the Goto button and release MENU over the name of the view you want to display, as indicated in Figure 3-7.

Figure 3-7

3. To return to the last view that was displayed, click SELECT on the Goto button. The default is the first item on the menu, Home, in this case

3.7.0.1 Selecting an Element or View by Name

• If you know the name of an element in a view, you can use the Find option in the View menu to display the view(s) that contain the particular element. See the Section on "Finding Elements" later in this Chapter.
• If you know the name of the view you want to see, type in the view name on the line next to the Goto button and press Return. If the view name you specify is not part of the runtime database, the Console displays a message "View name <view_name> does not exist" in the Console window footer area and leaves you in the current view.

3.7.1 Returning to the Home View

1. Press MENU on the Goto button; choose the Home option.

   a. Or, type "Home" in the Goto line and click SELECT on the Goto button.

If you often find it necessary to return to the Home view, you could have the Home view displayed whenever you click SELECT on the Goto button. This change is made in the Console Properties window Miscellaneous category. Refer to "Part 2: Reference" for more information.

3.8 Creating Elements Using the Editor

This section describes the Console's graphical editor function, accessible through the Edit >> Create button. This function limits you to creating elements one-at-a-time. Use IP Discover as a more convenient way to create elements in large networks.

You can create new elements of different types to represent particular views, networks, devices, and other components in your network. Elements are represented by glyphs, a type of icon, which appear in one or more views. To create new elements follow the steps below:

1. In the Console's control area, press MENU on the Edit button.

2. Release MENU over the Create item. (Alternatively, you can press MENU over an empty space in the view to obtain a floating popup menu. You receive the window shown in Figure 3-8.

Figure 3-8

3. Click SELECT on your choices for Category and Type.

4. Click SELECT on Create. If you select a Component as a category, you receive the window shown in Figure 3-9.

Figure 3-9

The top portion of the window is the element data.

1. Complete the Name field using a valid IP address or name. This field is required.

   If you enter a name, it should be in a local operating-system configuration file (such as /etc/hosts) or in a directory service map or table. SunNet Manager does not check for the correctness of an IP address or name until you send a request to that element.

   Other fields are optional; you can use them to record information about the element for your reference.

The middle portion of the new-element window is the list of agent schema files that the Console knows about. This and the bottom portion are the same for all categories of elements as shown in Figure 3-9.

In the middle portion, click SELECT on the box to the left of a listed schema to toggle a check mark--this specifies that the element can be managed with this schema. Check all schemas that apply to the element. The line to the right of some schema names indicates that a proxy system can be defined. If you do not define a proxy system, the default proxy system will be the system on which you are running the Console.

---

Note - Checking a schema does not make the element manageable from the Console; the appropriate agent software must be installed and running on the target system. See your installation guide for instructions on running the getagents script to install agents. The exceptions to this are the hostperf and ping proxy agents. On most Sun and those of many other vendors on a TCP/IP network, you can check off the hostperf and ping agents and use the Console machine (localhost) as the proxy.

---

The bottom portion of the Properties window allows you to specify a color for the glyph associated with the element.

When you finish entering data and making selections in the new-element window, click SELECT on Apply. A glyph for the element you just defined appears in the current view with the name you specified.

Figure 3-10 shows the data portion of the Object Properties windows for the remaining element categories: view, connection, and bus.

Figure 3-10

3.8.0.1 Glyphs for Multiple Element Types

The glyphs in Table 3-1 are used for more than one type of element.

Table 3-1

Glyph	Element Category	Element Type
	Component	ss330 ss370 sun-deskside
	Component	sun-server sun470
	Connection	link rs232
	Component	IPX-Latern Device IPX-PC Unixware
	Component	IPX-Bridge IPX-Router Netware Router
	Component	IPX Print Server IPX Printer

3.8.1 Useful Information About Creating Elements

Figure 3-11

3.8.1.1 IP Address

The IP Address field in the Properties window for the element is not used to manage the device--it is for your information only. See Figure 3-11 for location of the IP Address field.

3.8.1.2 Proxy Agent System Name

The blank line next to some agent schema names allows you to specify the name of the system on which the proxy agent resides. (For example, in Figure 3-11, blank lines exist next to each schema file on the left side of the window.) This system name is for a default proxy system. You can specify a different proxy system name for data reports and when specifying events. If

you do not specify a proxy system in the Properties window or in the report request, the system on which the Console is running is assumed to be where the proxy agent resides.

3.8.1.3 Creating Elements Within Elements

You can create an element that logically contains other elements. For example, if managing all the file servers in your management domain is important, you might want to create a view called File Servers. To do so, perform the following steps:

1. Create an element of category View, as described previously.

2. Double-click SELECT on the new glyph.

3. In the empty view, create the element instance for each device. If the element instance definition already exists, copy the glyph into the view. (See the Section on "Copying Elements" later in this chapter.)

3.8.1.4 Changing Label Fonts

You can change the font used for the labels under element glyphs. This is done in the Console Properties window. (If you change the font, you must restart the Console for the change to take effect.) See the description of the Icon Font setting in "Part 2: Reference."

3.9 Creating Aliases

SunNet Manager has an alias feature that allows you assign multiple names to an element. This feature is useful with machines that have multiple network interfaces (usually routers). You can use an alias in the same way that you use element names. That is, you can search on an alias or send requests that specify an alias.

If you use unique names for each interface, the Discover tool fills in aliases automatically when it creates a router. The first name it finds is the one filled in as the name of the element and the names of subsequently-found network interfaces as aliases.

To add one or more aliases for an element, do the following:

1. Press MENU over the glyph to which you want to add aliases.

   You can also click SELECT on the glyph to highlight it, then press MENU over the glyph. You receive the Properties window for that element.

2. In the Properties window, click SELECT on the Alias button.

   You receive the window shown in Figure 3-12.

Figure 3-12

3. Enter a name and click SELECT on Add.

   The name you entered appears in the Aliases List.

To change or delete an alias:

1. Click SELECT on the alias in the Aliases List

2. Click SELECT on Change or Delete.

The same rules apply to aliases as to element names, as specified in the subsection on "Creating Elements" later in this chapter. You can use an IP address or a name.

The Properties window for a router has two IP address fields as shown in Figure 3-13.

Figure 3-13

You are not, however, limited to managing the two interfaces identified in the IP Address fields. The alias feature allows you to add a name for each interface on a machine. Note that the IP Discover tool does this automatically.

3.10 Finding Elements

The Find option of the View menu displays the view(s) in which a specified element is located.

1. In the Console window, invoke View >> Find.

Figure 3-14

2. In the Find window, enter the name of the element you want to find.

3. Click SELECT on the Find button in the window or press Return.

   The element is highlighted when found.

4. Click SELECT on the Next button to see the next view (if any) in which the element is located.

Use the Find function key on the left side of your keyboard to search on any of the names (aliases) associated with an element.

3.11 Modifying Element Properties

You can modify the following properties of an element instance in the element's Properties sheet:

• Agent schemas that apply to the element
• Element color
• Optional fields information

"Part 2: Reference" describes the fields in the Properties window. Note that you cannot modify the name of an element instance once it has been created.

To rename an element instance, you must delete and re-create it with the new name using the following steps:

1. Over the glyph that represents the element, press MENU. Or, click SELECT on the glyph and press the Props button on the left side of your keyboard.

2. Release MENU over Properties to open the Properties window for the element.

Figure 3-15

3. Modify the fields within the Properties window for the element. Click SELECT on the Apply button to incorporate the changes to the element.

3.12 Changing Element Types

SunNet Manager has four categories of elements: component, view, bus, and connection, as shown in Figure 3-16.

Figure 3-16

Of these categories, you can only change an element type in the component category. To change a component type, follow the steps below:

1. Over the glyph that represents the element that you want to modify. Press MENU.

2. Release MENU over Change Type. You receive the Change Type window shown in Figure 3-17.

Figure 3-17

3. Click SELECT on the new element type; click SELECT on Change.

   The Change Type window disappears and the changed element appears in the Console window represented by a new glyph.

3.12.1 Restrictions on Changing Element Types

You can change element types for components, such as workstations, servers, printers. These types are displayed in the Type menu in the Change Type window, such as the one shown in Figure 3-17. You cannot change elements of category view, bus, or connection.

3.12.1.1 Elements on Different Machines

As the Discover tool finds network elements, it distinguishes among machines running SunNet Manager agents, SNMP devices, routers, and networks and subnetworks. (You can restrict the search to one or any combination of these types of objects.) The first three object types are in the component category of elements. The last, networks and subnetworks, are in the view category and cannot be changed.

3.13 Moving Elements within a View

You can move elements within a view as described in the following steps:

1. Over the glyph that represents the element to be moved, press SELECT. If you wish to move multiple elements at the same time, click ADJUST on subsequent glyphs.

2. Drag the mouse pointer to the desired new location and release. Figure 3-18 shows moving a glyph.

Figure 3-18

3.14 Moving Elements from One View to Another

You can move elements between views using the steps below:

1. Over the glyph that represents the element to be moved, click SELECT.

   To move multiple elements at the same time, click ADJUST on subsequent glyphs.

2. In the control area of the Console window, invoke Edit >> Cut. Or, press MENU over an empty space in the view to open the Edit menu as a floating popup menu.

3. Release MENU over Cut.

4. Use the Goto button in the Console's control area to switch to the view where the glyph(s) will be moved.

   See "Traversing the View Hierarchy" earlier in this Chapter for more information.

5. In the Console's control area, invoke Edit >> Paste.

3.14.1 Useful Tips

1. You can use the Cut and Paste function keys on the left side of your keyboard instead of Edit menu functions.

2. When you cut or copy an element or set of elements, the element(s) is stored in the clipboard. To view the contents of the clipboard in the Console window, press MENU on View >> Clipboard and release MENU.

3. You cannot cut an element with an associated request, nor delete an element that contains another element in its subview.

3.15 Connecting Elements

You can draw a connection from a selected (highlighted) element to the element glyph where the mouse pointer is located.

1. Click SELECT over one of the elements (the element to connect from).

2. Press MENU over the other element (the element to connect to).

3. Release MENU over Connect.

   Figure 3-19 shows a connect example.

Figure 3-19

3.15.1 Simple Connections

These connections should not be confused with the Connections element type category, which includes RS-232 connections and other links. The connections described in this task are also known as "simple" connections. They are not elements and cannot be managed. Simple connections are useful only for showing a graphic representation of the connectivity between elements.

When either of the connected elements is moved, the connection also moves.

The color of the connection is based on the color of the second, "connected to" element. Whenever you select (highlight) this element, the connection is also highlighted.

3.16 Copying Elements

After you have created an element, you can create many instances of that element in various views in your database. To do this, copy the element from one view to another as explained below.

1. Click SELECT on the glyph that represents the element to be copied to highlight it.

   If you wish to copy multiple elements in a view at the same time, click ADJUST on subsequent glyphs.

2. In the control area of the Console window, invoke Edit >> Copy. Or, press MENU over an empty space in the view

Figure 3-20

3. Use the Goto menu to move to the view to which the element will be copied.

4. Invoke Edit >> Paste (from the Edit button or from a floating popup menu in an empty space in the new view).

When you cut or copy an element or set of elements, the element(s) is stored in the clipboard. To view the contents of the clipboard in the Console window, press MENU on View >> Clipboard and release MENU.

3.16.0.1 Using Function Keys for Copy and Paste

You can use the Copy and Paste function keys on the left side of your keyboard instead of the Edit menu functions. The Copy function copies the element into the Console clipboard. After an element has been copied into the clipboard, it can be pasted into as many views as needed.

3.16.0.2 Drag and Drop

If an element and the view into which it will be copied are both displayed in the same view, you can use the Console's "drag and drop" function:

1. Press SELECT over the glyph that represents the element to be copied.

2. While still pressing the SELECT mouse button, drag the mouse pointer to the glyph that represents the view to which the element will be copied. Release the mouse button.

3.17 Deleting Elements

You can delete an element instance from a view using the steps below:

1. Click SELECT over the glyph to be deleted. If you wish to delete multiple elements at the same time, click ADJUST on subsequent glyphs.

2. In the Console's control area, invoke Edit >> Delete.Or, press MENU over an empty space in the view.

Figure 3-21

3.17.1 Useful Notes About Delete

You cannot delete an element that has a request associated with it. You also cannot delete an element that contains another element in its subview.

Delete removes the element from the view and from the database. The element is not placed in the clipboard, so you cannot paste a deleted element.

3.18 Saving the Management Database

The runtime database contains element and request instances that you have created. You can save the database to an ASCII file, allowing you to reinvoke the Console with the same database. Follow the steps below:

1. In the Console window, press MENU on File >> Save >> Management Database and release MENU.

Figure 3-22 >> >>

2. In the Save pop-up window, enter the directory and file name for the database.

3. Click SELECT on the Save button to store the database.

After you invoke File >> Save >> Management Database, SunNet Manager takes a snapshot of the current database and stores it in a single ASCII file. The structure of this stored database--a single file--is entirely different from the structure of the runtime database. The runtime database consists of a set of special database files under a directory name having the following form:

• /var/adm/snm (or $SNM_HOME)/db.<login> (or db.<$SNM_NAME>) for Solaris 1.1.1
• /var/opt/SUNWconn/snm (or $SNM_HOME)/db.<login> (or db.<$SNM_NAME>) for Solaris 2.x

3.18.0.1 Don't Store Under /Var

It is recommended that you not store the ASCII files under /var because /var is for files that grow and because a saved ASCII database is static and possibly large.

When restarting the Console, you can specify whether to continue to use the runtime database from the previous run of the Console, or to reinitialize the database from ASCII structure and instance files. See the section "Starting the Console" in this Chapter for instructions for reinitializing the database.

3.19 Quitting the Console

You quit a Console session by using the Quit option of the Console's window menu.

1. In the title bar of the Console window, press MENU and release MENU over Quit.

2. If there are any active requests, you see the pop-up verification window in Figure 3-23.

Figure 3-23

Click SELECT on one of the following:

• Quit, to have the Console kill all active requests before stopping.
• View Requests, to display the Request Viewer window.
• Resume, to continue running the Console.

When you quit a Console session, the verification window is displayed by default if there are any active requests. You can choose to have the verification window always displayed or never displayed--this is specified in the Console Properties window, under the Miscellaneous category. See the description of the Verify Quit setting in "Part 2: Reference."