[Top]
[Prev]
[Next]
[Bottom]
Cooperative Consoles 1.2 implements the sharing of information
between multiple instances of the Site/SunNet/Domain Manager Console.
Geographically dispersed organizations with large networks
often need a division to handle network management responsibilities among
multiple management Consoles. For such network environments, Cooperative Consoles
(CC) provides the ability to implement the forwarding of information about
selected changes in the state of critical network devices or changes in selected
aspects of network topology between multiple management stations running
Site/SunNet/Domain Manager. CC provides the flexibility to implement a variety
of possible information-sharing configurations between multiple Site/SunNet/Domain
Manager consoles.
NOTE - CC assumes that version
2.3 of Site/SunNet/Domain Manager has been installed for management stations
on the Solaris 1.x and Solaris 2.x environments.
NOTE - At this release, the CC_Receiver
is supported with Domain Manager only. Site Manager and SunNet Manager can
only function as a sending station.
CC currently enables the forwarding of four types of
information between Site/SunNet/Domain Manager consoles:
To implement information forwarding between Site/SunNet/Domain
Manager consoles, CC uses three executable software modules:
The Receiver and Sender processes are described in
Chapter 3, "Cooperative Consoles
Operation
." The use of the Configuration Tool is explained in
Chapter 4, "Using the Configuration Tool
."
A Site Manager and a SunNet Manager Console machine
can function as a sending station only. A Domain Manager Console machine can
function as both a sending station and a receiving station, or it can serve
as only a sending station, or as only a receiving station. The particular
distribution of the Sender and Receiver on the Site/SunNet/Domain Manager
Console machines in your network depends upon the desired network management
configuration. Several sample configurations are discussed in
Chapter 2, "Cooperative Consoles
Configurations
."
In addition to the Receiver and Sender processes, the
SNM Event Dispatcher (na.event) also plays an important role in
the functioning of CC on both receiving and sending stations.
The information flow between Site/SunNet/Domain Manager
consoles with CC installed is illustrated in
Figure 1-1
.
After installing the CC software, you need to load the
cooptools.schema file into Site/SunNet/Domain Manager in
order to add the Cooperative Consoles Receiver (Domain Manager only) and
Configuration Tool to the Site/SunNet/Domain Manager Console's Tools menu.
The methods for loading the cooptools.schema file are:
- If you start Site/SunNet/Domain Manager with the
-i option after installing CC, this forces Site/SunNet/Domain Manager
to reload all the schema files, including cooptools.schema.
NOTE - Starting Site/SunNet/Domain
Manager with the -i option erases your runtime management database.
To save your current runtime database, you need to use the Console File menu
Save\xe4 Management Database option to save your runtime database to an ASCII
file. You can then reload this database using the Load\xe4 Management Database
option after restarting Site/SunNet/Domain Manager with the -i
option.
- To use this method, pull down the Site/SunNet/Domain
Manager Console's File menu and select the Load\xe4 Management Database option.
The cooptools.schema file is located in the following directory:
- Select the cooptools.schema file, as
shown in
Figure 1-2
, and then click SELECT on the Load button.
After loading the cooptools.schema
file, quit Site/SunNet/Domain Manager, then restart Site/SunNet/Domain Manager
again. When you restart Site/SunNet/Domain Manager, you do not need to use
the -i option.
When a new schema file is added or when a record
is added to an existing schema file, you need to run the utility program
modify_el located in /opt/SUNWconn/snm/bin
for Solaris 2.x and /usr/snm/bin for Solaris 1.x.
The default location will be used when
modify_el is specified without an argument. If you used an install
directory other than the default installation path, you need to run the program
as follows:
% modify_el <installation_path>
/SUNWconn/snm.
To ensure that all SNM database/glyph traps are
sent to the local Sender daemon, make sure that the attribute snm.console.DBMgrTrapAlways
(for database traps) or snm.console.sendGlyphTraps (for glyph
traps) is set to TRUE in your.SNMdefaults file. The default setting
for this SNM attribute is FALSE. You can use vi or your favorite
text editor to change the setting of this attribute. If no.SNMdefaults
file exists in your home directory, you can force Site/SunNet/Domain Manager
to create one by making a minor change to some Console attribute from the
Console Properties menu.
[Top]
[Prev]
[Next]
[Bottom]
Copyright 1996 Sun Microsystems, Inc., 2550 Garcia Ave., Mtn.
View, CA 94043-1100 USA. All Rights Reserved