If you think you might be trying to collect too much information from the element, you might want to narrow down the collection. For example, if you are trying to collect monitoring information for three disks drives on a server, you might want to try collecting information for one disk drive.

The software stops trying to gather information after several unsuccessful attempts.

Monitoring with Direct Attached Storage

A port on a storage system directly attached to a host, does not appear in the left panel for monitoring. If you want to monitor the port, connect the port to a switch.

Supported Host Configurations for Monitoring

Refer to the following table to determine which host configurations the management server can monitor. The management server supports configurations that have a Y next to them. Nonsupported configurations have an N next to them.

NOTE: If a configuration listed in the following table is not supported, you can still obtain processor and memory statistics from the host. The exception, however, is Windows NT 4, which does not provide any monitoring information to the management server.

If the host has several configurations listed in the table below and one of them cannot be monitored, monitoring is not supported for all of the configurations on the host. For example, assume you have a host with Solaris 9 Sun Foundation Suite Leadville with MPXIO and Solstice Disksuite/Volume Manager. Even though the management server supports monitoring for Solstice Disksuite/Volume Manager, both of those devices, Sun Foundation Suite Leadville with MPXIO and Solstice Disksuite/Volume Manager, cannot be monitored because Solaris 9 Sun Foundation Suite Leadville with MPXIO is not supported, as shown with the following formula:

A monitorable configuration (Y) + a unmonitorable configuration (N)= unmonitorable configuration (N)

Keep in mind the following:

•In all configurations, you cannot monitor a VCM database device.

•The management server only monitors the top or bottom layer of Solstice Disksuite/Volume

Manager. For example assume you have a normal configuration for Solstice Disksuite/Volume Manager (/folder <- d1 <- d2 <- d3 <- d4 <- cxtydzs#). The management server reports on the folder and the highest layer, which is d1. Assume you have soft partitioning (/folder <- d1 <- d2 <- d3 <- d4 <- cxtydzs#). The management server reports on the folder and the lowest layer, which is d4. The management server skips all layers between the d# devices. You are not able to monitor the middle layers, which are d2 and d3 in the previous example.

The following table is a sample of possible configurations, not a complete list of all products in the marketplace.

510 Viewing Performance Data