| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Administration: Network Interfaces and Network Virtualization Oracle Solaris 11 Information Library |
| 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)
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
22. Monitoring Network Traffic and Resource Usage
Monitoring Traffic and Use of Resources (Task Map)
Gathering Statistics About Network Traffic on Links
How to Obtain Basic Statistics About Network Traffic
How to Obtain Statistics About Ring Usage
How to Obtain Statistics About Network Traffic on Lanes
Gathering Statistics About Network Traffic on Flows
How to Obtain Statistics on Flows
How to Configure Extended Network Accounting
Packets traverse a path when they flow into or out of a system. On a granular level, packets are received and transmitted through receive (Rx) rings and transmit (Tx) rings of a NIC. From these rings, received packets are passed up the network stack for further processing while outbound packets are sent to the network.
Chapter 21, Managing Network Resources introduces the concept of network lanes. A combination of system resources that are allocated to manage network traffic constitutes a network lane. Thus, network lanes are customized paths for specific types of network traffic. Each lane can be either a hardware lane or a software lane. In addition, each lane type can be either a receive lane or a transmit lane. The distinction between hardware and software lanes is based on a NIC's ability to support ring allocation. For more information about ring allocation, see Transmit and Receive Rings. This chapter focuses primarily on incoming traffic that is received through receive lanes.
On hardware lanes, rings are dedicated to the packets that use those lanes. In contrast, rings on software lanes are shared among datalinks. Datalinks are configured to share rings for the following reasons:
Administrative intent. The datalink might not be performing intensive processes to require dedicated rings.
The NIC does not support ring allocation.
Despite support for ring allocation, rings are no longer available to be assigned for exclusive use.
Consider the following figure that shows different hardware lanes:
Figure 22-1 Hardware Lanes
The figure shows the following configuration:
The system has a single NIC, nxge.
Links are configured over the physical device: nxge0, vnic1, and vnic2. Note that as a datalink, nxge0 can be assigned a customized name. However, in the figure, the link retains its default device name.
The system has multiple CPUs.
The NIC supports dynamic ring allocation. Thus, a set of hardware rings can be assigned to each link to constitute a hardware lane. In addition, a set of CPUs is also allocated to each lane.
|