C H A P T E R  4

Update Multiple Hosts Using Image Tool and Agent Update

This chapter provides instructions for:



Note - Be sure you click Store Response Data during the Sun Management Center 3.5 base software setup process if you want to use the setup-responses-file to duplicate the setup on the current machine on other machines. That way all of your responses will be stored in /var/opt/SUNWsymon/install/setup-responses-file. For more information, refer to "Setting Up Base Products and Add-ons on the Solaris Platform" in the Sun Management Center 3.5 Installation and Configuration Guide.




Creating an Agent Update Image for Sun Fire Link

Sun Fire Link allows you to create an image of one, two, or all of the following Agent components:



Note - Before creating an image, the Sun Fire Link Server component must be installed on the server machine.



The primary use of Agent Update for the Sun Fire Link add-on software is to distribute the Cluster Node component to multiple nodes simultaneously. Because of a Sun Management Center 3.5 limitation, all component setup questions are asked, even when you select a single component for the image.

Typically, as recommended, the Sun Fire Link Manager and Switch components are installed and set up on a single target host machine. However, when you want to image the Manager and Switch components (as shown in CODE EXAMPLE 4-1), three main setup options appear: l, u, and d. Options l and u correspond to the Sun Management Center load and unload agent module commands. Use option d to end the setup for both components.

The Agent Update setup for these components asks you to:

Enter the hostname of the node that this data will be applied.... 

This information is used to apply setup information to a specified target host, as shown in CODE EXAMPLE 4-1. The setup information for a specific target host, while contained in an image which will be distributed to multiple hosts, will be applied only to that target host; for example, if a manager component is imaged for distribution on hosts tara and jenny, and you only supply setup information for tara, that information is only applied to the setup on tara.

Sun Fire Link 
---------------------------------------
 
----------------------------------------------------------
Welcome to the Sun Fire Link Addon Setup
----------------------------------------------------------
 
----------------------------------------------------------
Starting Sun Fire Link Manager Setup
----------------------------------------------------------
Enter "l" to load a module instance, "u" to unload an instance, "d" for done: l
Enter the hostname of the node that this data will be applied to (hostname MUST be able to be translated to an IP Address): tara
Enter the instance name of the module (unique internal name MUST start with alpha character and contain no whitespace or special characters): fminst1
Enter a short (few words, whitespace is OK) description of this module instance: Initial install of the Manager
Enter the name of the Fabric you are monitoring: fab1
Enter the FM RMI port number [1099]:
Hit RETURN key if this is NOT an initial install of the Sun Fire Link Manager on this node. Otherwise the entry will be ignored.
Enter a NON EXISTING Data Directory for the Sun Fire Link Manager (Suggested location is a new subdirectory of /var/opt/): /var/opt/fab1data
 
Enter "l" to load a module instance, "u" to unload an instance, "d" for done: u
Enter the hostname of the node that this data will be applied to (hostname MUST be able to be translated to an IP Address): jenny
Which instance of the Sun Fire Link Manager module would you like to remove? fminst1
 
Enter "l" to load a module instance, "u" to unload an instance, "d" for done: l
Enter the hostname of the node that this data will be applied to (hostname MUST be able to be translated to an IP Address): jenny
Enter the instance name of the module (unique internal name MUST start with alpha character and contain no whitespace or special characters): fminst2
Enter a short (few words, whitespace is OK) description of this module instance: This is an update of the Manager
Enter the name of the Fabric you are monitoring: fab2
Enter the FM RMI port number [1099]:
Hit RETURN key if this is NOT an initial install of the Sun Fire Link Manager on this node. Otherwise the entry will be ignored.
Enter a NON EXISTING Data Directory for the Sun Fire Link Manager (Suggested location is a new subdirectory of /var/opt/):
 
Enter "l" to load a module instance, "u" to unload an instance, "d" for done: d
 
----------------------------------------------------------
Starting Sun Fire Link Switch Setup
----------------------------------------------------------
Enter "l" to load a module instance, "u" to unload an instance, "d" for done: l
Enter the hostname of the node that this data will be applied to (hostname MUST be able to be translated to an IP Address): tara
Enter the instance name of the module (unique internal name MUST start with alpha character and contain no whitespace or special characters): swinst1
Enter a short (few words, whitespace is OK) description of this module instance: Monitors swinst1
Enter the hostname of the SWITCH System Controller (hostname MUST be able to be translated to an IP Address): dryvalley
Enter the public community string of the Switch: public
 
Enter "l" to load a module instance, "u" to unload an instance, "d" for done: u
Enter the hostname of the node that this data will be applied to (hostname MUST be able to be translated to an IP Address): jenny
Which instance of the SFL Switch module would you like to remove? swinst1
 
Enter "l" to load a module instance, "u" to unload an instance, "d" for done: d
CODE EXAMPLE 4-1 Image Manager and Switch Components and Specify Target Host




Note - Multiple instantiations of either component's agent module should not monitor the same Manager or Switch, from the same or different hosts.



If an image contains a Manager component, and setup information is not supplied for target hosts when the component is installed for the first time, default directory information is used when setup is run on that host. The default directory is an area for Sun Fire Link Manager data:

/var/opt/FM_xxx

where xxx represents date and time-specific values.

If a Manager component is included in an image to be applied to hosts in that scenario, setup information must be specified for the target hosts.

Once a Sun Fire Link image has been applied to a target host, regardless of the components that are contained with the image, another update is not allowed by Sun Management Center until an image with an updated version is presented, or the add-on software is removed through Sun Management Center tools.


procedure icon  To Create an Image File of Sun Fire Link Add-on Components

Use the preceding information to perform this step correctly for Sun Fire Link add-on components. For additional information, refer to Chapter 8, "Post-Installation Tasks," in the Sun Management Center 3.5 Installation and Configuration Guide for detailed instructions about using either the Wizard or the CLI Image Tool.

single-step bulletCreate an Image File of the desired Sun Fire Link add-on components to be distributed to the desired agent machines using either es-gui-imagetool or es-imagetool, which are base Sun Management Center scripts.


Updating Multiple Hosts Using Agent Update

Using the Agent Update process, you create an Image File of the add-on components to be distributed to the target machines, and then add a New Job to Manage Jobs Task list to be run when you specify.

The Agent Update process must be run from the Sun Management Center server machine. The target hosts must have only the Agent layer installed (the Console layer must not be present), and each target host must have the Sun Management Center Agent Update module running.


procedure icon  To Use the Agent Update Process to Update Multiple Hosts

1. From your main Sun Management Center console window, select the Manage Jobs... option from the Tools menu.

The system displays the Manage Jobs panel (FIGURE 4-1), which allows you to distribute the Image File.

 FIGURE 4-1 Manage Jobs Panel

Screen capture of the Manage Jobs panel.

2. In the Manage Jobs panel, select the New Task... button.

The system displays the New Task panel (FIGURE 4-2), which allows you to specify the Agent Update Image File to distribute.

 FIGURE 4-2 New Task Panel

Screen capture of the New Task panel.

3. In the New Task panel (FIGURE 4-2), do the following:

a. Select Agent Update for the Task Type.

b. Select the Image File you created in Step 1.

c. Enter the Task Name.

d. Click the Add Task button.

e. Click the Close button.

4. In the Manage Jobs panel (FIGURE 4-1), do the following:

a. Enter a Job Name.

b. Select the Task you created in Step 4.

c. Do one of the following to schedule when you want the Task to run:

    • If you want the Task to run immediately, click the radio button to the left of Run Immediately.
    • If you want to set a schedule for when the Task is to run, click the radio button to the left of Schedule Job, and set the schedule.


Note - Before you select objects (agent machines) where you want the Image File, you can create a group object containing all your agent machines. That way you do not have to select one agent machine at a time. Refer to Chapter 3, "To Create a Group," in the Sun Management Center 3.5 User's Guide for more information about creating object groups.



d. Do one of the following to select the objects (agent machines) to which you want to distribute the Image File:

    • Click the radio button to the left of All Objects in Domain to select all objects, and specify any filter you want to use to further select objects.
    • Click the radio button to the left of Selected Objects in Main Window to select one object at a time.

e. Preview the objects (agent machines) you have selected and redo your selections if necessary.

f. Click the Add Job button.

The job starts and distributes the Image File to the objects (agent machines) you selected. When the job is running, it appears in the Job list of the Manage Jobs panel. The panel shows the status of the job when running and when complete.



Note - When updating multiple hosts, any failure of a host results in a Failed status even though the majority of the hosts might have been updated successfully. Click on View Log to the right of the Jobs list on the Manage Jobs panel to see an individual list of the updates that succeeded and the updates that failed. If the Agent Update process did succeed, the Sun Management Center agents should restart automatically. You can open a host Details window on the Sun Management center console to each of the targeted hosts, and verify that the expected modules are present and working.