Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: Network Interfaces and Network Virtualization Oracle Solaris 11 Information Library |
1. Overview of the Networking Stack
Network Configuration in This Oracle Solaris Release
The Network Stack in Oracle Solaris
Network Devices and Datalink Names
Administration of Other Link Types
3. NWAM Configuration and Administration (Overview)
Overview of NWAM Configuration
Description of the Automatic and User-Defined NCPs
Description of a Location Profile
Property Values of System-Defined Locations
How NWAM Profiles Are Activated
Location Activation Selection Criteria
Configuring Profiles by Using the netcfg Command
Administering Profiles by Using the netadm Command
Authorizations and Profiles That Are Related to NWAM
Authorizations That Are Required to Use the NWAM User Interfaces
4. NWAM Profile Configuration (Tasks)
5. NWAM Profile Administration (Tasks)
6. About the NWAM Graphical User Interface
Part II Datalink and Interface Configuration
7. Using Datalink and Interface Configuration Commands on Profiles
8. Datalink Configuration and Administration
9. Configuring an IP Interface
10. Configuring Wireless Interface Communications on Oracle Solaris
12. Administering Link Aggregations
16. Exchanging Network Connectivity Information With LLDP
Part III Network Virtualization and Resource Management
17. Introducing Network Virtualization and Resource Control (Overview)
18. Planning for Network Virtualization and Resource Control
19. Configuring Virtual Networks (Tasks)
20. Using Link Protection in Virtualized Environments
21. Managing Network Resources
There are two daemons that are used by NWAM: the nwamd daemon and the netcfgd daemon. The policy engine daemon, nwamd, controls network autoconfiguration by functioning in multiple roles. The repository daemon, netcfgd, controls access to the network configuration repository.
The nwamd daemon controls network autoconfiguration by assuming the following roles:
Event Collector
This role involves collecting link-related events that need to be detected through routing socket and sysevent registration. An example of how nwamd performs this task is that the daemon obtains an EC_DEV_ADD sysevent, which signifies that a NIC was hot-plugged into the system. All such events are packaged into the nwamd event structure and then sent to the event handling thread, which is responsible for that task.
Event Handler
This role involves running an event loop thread to respond to events of interest. The event handler operates on the state machines that are associated with the different objects that are managed by the NWAM service. In the course of handling events, the nwamd daemon detects changes in the network environment, which might trigger changes to a profile, or profiles, as a result.
Event Dispatcher
This role involves sending events to external consumers who have registered an interest in such events. Examples of event dispatching include wireless scan events that contain information about available WLANs, which is useful to the NWAM GUI. The GUI can, in turn, display the available options to the user.
Profile Manager
Management of these profiles by the nwamd daemon involves applying the network configuration, depending on the following information:
Which links and interfaces are activated
Characteristics of the connected networks
Contingencies and dependencies that are built into the enabled profiles
External events that are received
The profile daemon, netcfgd, controls and manages access to a network configuration repository. The daemon is started automatically by the svc:/network/netcfg:default SMF service. The daemon ensures that any application that is attempting to read information from or write information to the repository has the following authorizations:
solaris.network.autoconf.read
solaris.network.autoconf.write
For more information about authorizations, see the auth_attr(4) man page. For more information about security profiles, see the prof_attr(4) man page.
For more information about the netcfgd daemon, see the netcfgd(1M) man page.