Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: Network Interfaces and Network Virtualization Oracle Solaris 11 Express 11/10 |
Transitioning From a Previous NWAM Implementation
Where to Find Network Configuration Tasks
2. NWAM Configuration and Administration (Overview)
3. NWAM Profile Configuration (Tasks)
4. NWAM Profile Administration (Tasks)
5. About the NWAM Graphical User Interface
Part II Administering Single Interfaces
6. Overview of the Networking Stack
7. Datalink Configuration and Administration
8. Configuring an IP Interface
9. Configuring Wireless Interface Communications on Oracle Solaris
Part III Administering Interface Groups
11. Administering Link Aggregations
Part IV Network Virtualization and Resource Management
15. Introducing Network Virtualization and Resource Control (Overview)
16. Planning for Network Virtualization and Resource Control
17. Configuring Virtual Networks (Tasks)
18. Using Link Protection in Virtualized Environments
19. Managing Network Resources
NWAM works with the following other Oracle Solaris networking technologies:
IP Multipathing (IPMP)
Prior to configuring your network by using IPMP, you will need to disable the SMF service, network/physical:nwam, and then enable the SMF service, network/physical:default.
Network virtualization
NWAM works with the various Oracle Solaris network virtualization technologies as follows:
Virtual machines: Oracle VM Server for SPARC (formerly Logical Domains) and VirtualBox
NWAM is supported in both Oracle Solaris hosts and guests. NWAM manages only the interfaces that belong to the specified virtual machines and does not interfere with other virtual machines.
Zones and stack instances
NWAM works in global zones or in a exclusive stack, non-global zone.
Note - NWAM does not work in a shared stack zone.
VNICs
Although the current NWAM implementation does not manage VNICs, manually created VNICs persist across reboots and can be created, for example, for assignment to an exclusive-stack zone.
Bridging technology
Bridging technology is method of connecting separate network segments to enable communications between the attached nodes, as if only a single segment were in use. Although the current NWAM implementation does not actively support network configurations that use the bridging technology, you do not need to disable the network/physical:nwam service prior to using this technology on your system.
Traditional networking commands and utilities
At any given time, either the network/physical:default service or the network/physical:nwam service must be enabled on your system.
If the network/physical:default service is enabled, traditional network configuration is used. In addition, the content of the /etc/hostname.intf files determines which interfaces are configured at boot time and specify relevant configuration details for those interfaces. If the network/physical:nwam service is enabled, the /etc/hostname.intf files are ignored, and NWAM manages the network configuration according to the policy that is specified by the profiles that are enabled on the system.
When the network/physical:nwam service is enabled, you can still use command-line networking utilities, for example, dladm and ipadm, to view elements of your current network configuration.
Note - Making changes to network configuration by using command-line tools is not supported, as those changes might conflict with the policy that is enforced by NWAM.