Solaris computer system sensor

The Solaris computer system sensor discovers computer systems that are running the Solaris operating system.

If you want to discover the Solaris Virtualization systems, run the Sun Sparc Virtualization sensor. For more information, see Sun Sparc Virtualization sensor.

Sensor name that is used in the GUI and logs

SunSparcComputerSystemSensor

Limitations

All computer system sensors and the SNMP MIB2 sensor ignore network interfaces that are configured to be down. Agile Service Manager does not populate the net.IpNetwork attribute on the following types of IP interfaces:
  • loopback, for example, 127.0.0.1, 0:0:0:0:0:0:0:1
  • link-local, for example, 169.254.1.1, FE80:0:0:0:0:0:0:1
  • multicast, for example, 224.0.0.1, FF00:0:0:0:0:0:0:1
  • unspecified, for example, 0.0.0.0, 0:0:0:0:0:0:0:0
Therefore, IP networks are not populated in the Agile Service Manager user interface.
The sensor discovers the number of physical processors if one of the following commands are present on the target system:
  • psrinfo -p
  • prtconf and kstat -m cpu_info. The kstat command must return implementation statistics.

The sensor discovers the number of processor cores when the command kstat -m cpu_info is present on the target system. The kstat command must return core_id statistics.

For the sensor to discover information about promiscuous mode on the Solaris operating system, the following command must be available for the network interface on the target system: 
kstat network_interface_name | grep promisc

The sensor does not discover the ZFS file systems.

If you want to discover Solaris operating system by running generic server sensor, you must have the /usr/ucb/ps command on the Solaris server. To install the command, install one of the following packages on the Solaris targets:
  • Solaris versions earlier than 10: install one, or both of the following packages:
    • Solaris 32 bit: the SUNWscpu package
    • Solaris 64 bit: the SUNWscpux package
  • Solaris 10: the SUNWscpu package
  • Solaris 11: the compatibility/ucb package

Discovery of IPv6 interfaces and IPv6 routing and forwarding information

The sensor discovers IPv6 interfaces and IPv6 routing and forwarding information about target systems that are configured to support IPv6. Agile Service Manager runs discoveries against only IPv4 addresses. Agile Service Manager does not start a sensor against IPv6 addresses. For DNS lookups, Agile Service Manager uses either the IPv4 or the IPv6 addresses. Agile Service Manager does not populate the net.IpNetwork attribute on an IPv6 interface if the prefix length value is unspecified or equals zero.

The discovered IPv6 addresses are displayed in the Agile Service Manager user interface similarly to IPv4 addresses and are accessible using the Agile Service Manager API. Because IPv6 addresses use a prefix length value instead of an IPv4 netmask, only one of these values is populated for an IP address. The value depends on the address type.