Device and driver identity and configuration has changed as follows:
Starting with Oracle Solaris 11.2, the Oracle Hardware Management Pack package is included in the Oracle Solaris release. Previously, this package was available as a separate download. These features provide cross platform components to assist you in managing your hardware better. For more information, go to www.oracle.com/goto/ohmp/solaris. See also the detailed documentation at www.oracle.com/goto/ohmp/solarisdocs.
As in Oracle Solaris 10 releases, all supported devices that are connected to the system when it is installed should be accessible after installation. You can configure devices by using the cfgadm command and most devices are hot-pluggable, which means you can add and remove devices while the system is booted.
The hotplug command provides offline and online capabilities, as well as enable and disable operations for PCI Express (PCIe) and PCI SHPC (Standard Hot Plug Controller) devices. Note that you can still use the cfgadm command to manage hot pluggable USB and SCSI devices. See Chapter 2, Dynamically Configuring Devices, in Managing Devices in Oracle Solaris 11.2 .
You can more easily identify devices by using the croinfo command to identify physical device location information.
Use the following commands to display information by chassis, receptacle, and occupant values for the devices on your system:
diskinfo – Display general information about physical disk locations
format – Display physical disk location information for disks when reviewing partition tables or relabeling. For example, the following format output identifies the two internal disks on this system, under /dev/chassis/SYS/HDO and /dev/chassis/SYS/HD1:
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <FUJITSU-MAY2073RCSUN72G-0401 cyl 8921 alt 2 hd 255 sec 63> /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@0,0 /dev/chassis/SYS/HD0/disk 1. c1t1d0 <FUJITSU-MAY2073RCSUN72G-0401-68.37GB> /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@1,0 /dev/chassis/SYS/HD1/disk
The previous output identifies two internal system disks but disks from a storage array are generally identified by their storage array name.
prtconf –l – Display system configuration information that includes physical disk location information
zpool status –l – Display physical disk location information for pool devices
In addition, you can use the fmadm add-alias command to include a disk alias name that helps you identify the physical location of disks in your environment, as shown in this example:
# fmadm add-alias SUN-Storage-J4200.0912QAJ001 J4200@RACK10:U26-27 # fmadm add-alias SUN-Storage-J4200.0905QAJ00E J4200@RACK10:U24-25
Use the diskinfo command as follows to determine where a disk is located:
% diskinfo -c c0t24d0 D:devchassis-path t:occupant-type c:occupant-compdev --------------------------------------------------- --------------- ------------------ /dev/chassis/J4200@RACK10:U26-27/SCSI_Device__9/disk disk c0t24d0
In this example, the /dev/chassis disk name includes an alias name that helps you locate the device in your environment.
The following example shows how to display a specific disk's physical location:
$ diskinfo -c c0t24d0 -o cp c:occupant-compdev p:occupant-paths ------------------ -------------------------------------------------------- c0t24d0 /devices/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@18,0
Driver customizations are made in the /etc/driver/drv directory rather than in the /kernel directory as in previous releases. This improvement means that your driver customizations are not overwritten when the system is upgraded. The files in the /etc/driver/drv directory are preserved during the upgrade. Customizing a driver configuration usually means that a per-device parameter or global property that impacts all devices is added or modified. See How to Customize a Driver Configuration in Managing Devices in Oracle Solaris 11.2 .