Creating composite object... Please Wait.

The amount of time this operation requires depends on how many Sun Fire 15K/12K domains are running.

You can see the Sun Fire 15K/12K folder added to the current location in the Sun Management Center domain topology. If the Sun Fire 15K/12K composite is not created, follow the steps in To Troubleshoot Composite Failure.

7. Open the composite folder to see all the objects associated with the Sun Fire 15K/12K platform.

See FIGURE 4-1 for an example of a Sun Fire 15K/12K composite.

 FIGURE 4-1 Example of a Sun Fire 15K/12K Composite

For more information about this procedure, refer to Chapter 4 of the Sun Management Center 3.5 User's Guide.

1. In the hierarchy view of the main console window, select the level in the Sun Management Center domain topology where you want to discover a Sun Fire 15K/12K composite object.

2. Select Discover from the Tools menu.

3. In the Discovery Requests panel, click Add.

4. Type information in the New Discover Request panel.

5. If the Sun Fire 15K/12K composite is not created, follow the steps in To Troubleshoot Composite Failure.

You can use the following Discovery Request filter options to customize your Sun Fire 15K/12K composite discovery request.

• The Platform Type filter criteria enable you to include or exclude Sun Fire 15K/12K domain and platform types.
• Sun Fire 15K/12K domain hosts and the system controller within the composite can be filtered by the host names and operating system filter criteria. The host names and operating system filter criteria do not filter Sun Fire 15K/12K platform objects.
• If the system controller is excluded by a filter criterion, the Sun Fire 15K/12K composite objects are still examined by the Discovery Manager for inclusion in the Sun Management Center domain.

Updating a Sun Fire 15K/12K Platform Composite

After you have created the Sun Fire 15K/12K platform composite, the contents and type of the composite Sun Management Center topology objects do not change. The composite objects must be updated if:

• Sun Fire 15K/12K domains become active (running the Solaris Operating System).
• Spare system controller is added to or deleted from the platform configuration.
• Sun Management Center monitoring for an object no longer shows the correct monitor type. For example, if the Sun Management Center agent is not running on the Sun Fire 15K/12K domain at the time the composite was created, an Internet Control Message Protocol (ICMP) Ping monitoring type host object is created for the Sun Fire 15K/12K domain. After the Sun Management Center agent is running again, the Sun Fire 15K/12K domain host object needs to be updated so that it can be monitored as a Sun Management Center Agent--Host type.

If the Sun Fire 15K/12K platform composite was created using the Create Topology Object window, perform all updates to the composite manually.

• If Sun Fire 15K/12K composite objects have been added or deleted, delete or create the objects as described in Chapter 3 of the Sun Management Center 3.5 User's Guide.
• If the monitoring type has changed, modify the topology object as described in the "Modifying Objects" section of Chapter 3 in the Sun Management Center 3.5 User's Guide.

1. If the Sun Fire 15K/12K platform composite was created by the Discovery Manager, you can make many of the updates by running a discovery request for the main system controller. This discovery request can either be started manually or scheduled for periodic running.

Running the discovery request makes these changes.

• New Sun Fire 15K/12K object, such as a spare system controller, is added to the platform composite.
• If an object monitoring type has changed to a level of higher monitoring capability, the monitoring type is updated. Monitoring capability increases from the ICMP Ping monitoring type to the SNMP Ping monitoring type to the Sun Management Center Agent - Host monitoring type.

When running a discovery request, be aware of the following.

• Topology objects are not deleted from the platform composite.
• If any of the topology objects have been modified from the Sun Management Center console window, the object monitoring type is not updated.

2. If you prefer, you can create an updated platform composite by deleting the Sun Fire 15K/12K platform composite from the topology and running a discovery request.

If you are unable to create a Sun Fire 15K/12K platform composite, check for the following.

1. Verify that the correct system controller host name and Sun Management Center agent port number were specified in the Create Topology Object procedure or discovery request.

2. Log in to the system controller and verify that the two Sun Management Center agents are running.

SC# ps -ef | grep esd root 21020 1 2 Mar 10 ? 84:03 esd - init agent -dir /var/opt/SUNWsymon root 21858 1 3 Mar 10 ? 103:07 esd - init platform -dir /var/opt/SUNWsymon

3. Try rerunning the discovery request or increasing the discovery request SNMP time-out value.

4. Create the Sun Fire 15K/12K platform object directly by creating a node as described in To Create a Sun Fire 15K/12K Platform Object.

5. Examine the Browser tab of the platform Details window to confirm that the Config Reader (Sun Fire 15K) module is loaded under Hardware and that the module is not disabled. The Discovery Object Table provided by this module defines the objects that are included in the Sun Fire 15K/12K platform composite.

6. On the system controller, run this command to ensure that the Discovery Table was created correctly.

SC# /opt/SUNWsymon/sbin/es-dt -v

If the output is not present or does not have the information contained in the following example, the Discovery Table was not created correctly.

Label Sun-Fire-15K-12K Host <host name> Port <port number> OID 1.3.6.1.4.1.42.2.85.1.1.22 Node Object Type Sun-Fire-15K-12K-platform-group

If you do not see this type of output, repeat the process starting with Step 5. If that still does not work, contact your Sun service representative.

---

Sun Fire 15K/12K Platform Objects

Sun Fire 15K/12K platform information is provided by a Sun Management Center platform agent running on the main system controller. When a spare system controller is configured, two Sun Fire 15K/12K platform objects are present in the Sun Fire 15K/12K platform composite. Sun Fire 15K/12K platform information is only available from the platform object associated with the main system controller. When a platform object is created as part of a composite, the platform object name includes the associated system controller name in square brackets. The spare system controller object and its associated spare Sun Fire 15K/12K platform topology objects are designated with a circled X on the lower-right corner of the icon to distinguish the spare from the main topology objects (TABLE 4-1).

After Sun Management Center has been installed and set up on the main and spare system controllers and the Sun Fire 15K/12K platform objects have been created, no Sun Management Center configuration changes are required when the spare system controller becomes the acting main system controller. When this switch from spare to acting main system controller occurs, the platform agent on the acting main system controller becomes active and collects current information about the Sun Fire 15K/12K platform.

Not all information that was available prior to this switch is available from the newly active platform agent. The number of domain stops (dstops) and record stops (rstops) encountered are reset to zero. A current error, such as a high temperature, is reported if the condition still persists.

The Sun Management Center agents on the spare and main system controller are not automatically synchronized. If you modify any of the default limits, attributes, or loaded modules on either the main or spare system controller, you should make the corresponding changes to the agents operating on the other system controller.

To Create a Sun Fire 15K/12K Platform Object

Sun Fire 15K/12K platform objects are created as part of the Sun Fire 15K/12K composite. You can also create the platform objects directly.

1. Follow the instructions in "Creating a Node" in Chapter 3 of the Sun Management Center 3.5 User's Guide to create a Sun Fire 15K/12K platform object.

2. In Step 3 of that procedure, select the Agent - Platform monitoring type from the pull-down menu (Monitor Via).

3. In Step 4 of that procedure, type the requested information.

---

Note - The default platform agent port number is port 166. Do not change this port number unless the platform agent was configured on a different port during Sun Management Center setup.

---

4. Click OK.

Sun Management Center 3.5 Supplement for Sun Fire 15K/12K Systems

816-7377-10

Copyright © 2003, Sun Microsystems, Inc. All rights reserved.