The Oracle Solaris 11.3 Information Library has been updated with new information about storage and network configuration.
You might need to sanitize disks to alter the information in the cache and on the medium of a logical unit such as an SSD, a USB drive, or a flash drive. To securely sanitize the cache and medium so that recovery of the data is not possible, use the sg_sanitize command as described in “Scrubbing a Disk” in Managing Devices in Oracle Solaris 11.3.
Health checks on attached SAN devices are required to ensure that no faulty devices are present in the storage setup. Detailed configuration information about storage components helps you to determine the faulty devices in your setup. Commands such as fmadm faulty, zpool status, and mpathadm show lu are useful to obtain configuration details. To learn more about health checks on storage components, see “Performing Health Checks on Devices” in Managing SAN Devices and Multipathing in Oracle Solaris 11.3.
Oracle Solaris supports storage devices such as removable media, disks, Fibre Channel, iSCSI initiator and targets, and SAS. Oracle Solaris I/O multipathing provides load-balancing and failover mechanisms to maintain the availability of SAN devices such as Fibre Channel and iSCSI.
Find commonly used terms for referring to storage devices in the Glossary in Managing SAN Devices and Multipathing in Oracle Solaris 11.3.
For commands quick references, see:
Isolation of network traffic can be achieved by using Oracle Solaris networking features such as VLAN, PVLAN, and VXLAN. A VLAN is a subdivision of a local area network at the datalink layer of the protocol stack, and a PVLAN enables you to divide this VLAN into sub-VLANs. Using VXLAN, you can create a Layer 2 network on top of a Layer 3 network. For more information about these features and when you can deploy each of them, see “Comparing Networking Features” in Strategies for Network Administration in Oracle Solaris 11.3.
Datalink multipathing (DLMP) provides high availability across multiple switches without requiring switch configuration. IPMP enables you to configure multiple IP interfaces into a single group, called an IPMP group. In virtual environments, creating an IPMP group over interfaces coming from non-overlapping DLMP aggregations can offer better network performance, with the high availability offered by the DLMP aggregation at the L2 layer and the load spreading by the IPMP at the L3 layer across multiple switches. See the example configuration at “Configuring IPMP Over DLMP in a Virtual Environment for Enhancing Network Performance and Availability” in Managing Network Datalinks in Oracle Solaris 11.3.
You might need to modify the VLAN ID of a VLAN when you migrate from one VLAN to another. To learn how to modify the VLAN ID of a VLAN VNIC assigned to a zone, see Example 20, “Modifying the VLAN ID of VLAN VNICs Assigned to Zones,” in Managing Network Datalinks in Oracle Solaris 11.3.
You can configure multiple private virtual networks within a single network unit such as a switch by combining VLANs and Oracle Solaris zones. With PVLAN, you can provide network isolation between zones that are in the same VLAN without introducing any additional VLANs. You can either create a PVLAN and then assign it to a zone, or create a PVLAN while you configure the zone itself. For information about how to assign PVLANs to zones, see “Assigning a PVLAN to a Zone” in Managing Network Datalinks in Oracle Solaris 11.3.
Using Ethernet-based anets, you can create VNICs inside a kernel zone and configure them to be in their own VLAN. You can add extra VLAN IDs (VIDs) to an existing anet resource to create new VLANs. When transmitting data, packets from these VLANs are tagged by the kernel zone and passed on to the host.
The host forwards the packets without stripping the tag, based on the destination MAC. For more information about how to create VNICs inside a kernel zone, see “Using VLANs With Kernel Zones” in Managing Network Datalinks in Oracle Solaris 11.3.
In most deployments, the values of MAC addresses and VLAN IDs in a kernel zone can be statically configured before the zone is booted. However, in certain deployments such as a cloud deployment, the values of MAC address and VLAN IDs that the kernel zone needs to use are not known in advance. In such cases, you can specify prefixes of allowed MAC addresses and ranges of allowed VLAN IDs to enable the kernel zone to communicate to the global host. For more information, see “Using Dynamic MAC Addresses and VLAN IDs in Kernel Zones” in Managing Network Datalinks in Oracle Solaris 11.3.
Oracle Solaris supports file sharing across large deployments or over a network using technologies such as NFS and SMB. Commands for administering NFS and SMB file sharing are now consolidated into the following quick references for ease of use:
Oracle Solaris offers several attributes and options with the ipadm and dladm commands to administer IP and datalinks. These commands and options are now included in the Oracle Solaris 11.3 Network Administration Cheatsheet in “Commonly Used IP Administration Commands” and “Commonly Used Datalink Administration Commands”.
Unlike traditional UFS, a ZFS file system does not report “file system full” in /var/adm/messages when the file system exceeds the quota. A ZFS file system dataset size can be either the full size of the underlying zpool or the size of the quota set within the dataset property. The zfs list and the zpool list commands provide the ability to monitor dataset and zpool usage. See “What to Do If a File System Fills Up” in Troubleshooting System Administration Issues in Oracle Solaris 11.3.
For more information about Oracle Solaris 11.3 documentation updates, see Oracle Solaris 11.3 Documentation Updates, July 2017 and Do You Use Local IPS Package Repositories?.