JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Using Virtual Networks in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


1.  Network Virtualization and Resource Management in Oracle Solaris

2.  Creating and Administering Virtual Networks in Oracle Solaris

3.  Managing Network Resources in Oracle Solaris

Working With Clients, Transmit Rings, and Receive Rings

MAC Clients and Ring Allocation

Ring Allocation in VLANs

Datalink Properties for Ring Allocation

Commands for Working With Receive and Transmit Rings

Obtaining and Interpreting Ring Information

Displaying Ring Allocation Capabilities of a Datalink

Displaying Ring Use and Ring Assignments on a Datalink

How to Configure Clients and Allocate Rings

Working With Pools and CPUs

How to Configure a CPU Pool for a Datalink

How to Allocate CPUs to a Link

Managing Resources on Flows

How to Configure Flows

4.  Monitoring Network Traffic and Resource Usage in Oracle Solaris


Managing Resources on Flows

Flows consist of network packets that are organized according to an attribute. Flows enable you to further allocate network resources. For an overview of flows, see Network Resource Management by Using Flows.

Using flows for managing resources involves the following general steps:

  1. Creating the flow by basing it on a specific attribute as listed in Network Resource Management by Using Flows.

  2. Customizing the flow's use of resources by setting properties that pertain to network resources. Currently, only the bandwidth for processing packets can be set.

How to Configure Flows

  1. If necessary, list the available links to determine the link on which you will configure flows.
    # dladm show-link
  2. Verify that IP interfaces over the selected link are properly configured with IP addresses.
    # ipadm show-addr
  3. Create flows according to the attribute you have determined for each flow.
    # flowadm add-flow -l link -a attribute=value[,attribute=value] flow

    Refers to the link on which you are configuring the flow.


    Refers to one of the following classifications by which you can organize network packets into a flow:


    Refers to the name that you assign to the particular flow.

    For more details about flows and flow attributes, see the flowadm(1M) man page.

  4. (Optional) Display the possible range of values for the datalink's bandwidth.
    # dladm show-linkprop -p maxbw link

    where link is the datalink on which the flow is configured.

    The range of values is listed on the POSSIBLE field.

  5. Allocate bandwidth share to the flow.
    # flowadm set-flowprop -p maxbw=value flow

    The value you set must be within the allowed range of values for the link's bandwidth.

    Note - Currently, only a flow's bandwidth can be customized.

  6. (Optional) Display the flows that you have created over the link.
    # flowadm

    Note - The flowadm command, if used without any subcommand, provides the same information as the flowadm show-flow command.

  7. (Optional) Display the property values for a specified flow.
    # flowadm show-flowprop flow

Example 3-8 Managing Resources by Setting Link and Flow Properties

This example combines the steps for allocating network resources to both datalinks and flows. The example is based on the configuration shown in the following figure.

image:The figure shows a configuration for managing resources on datalinks and flows.

The figure shows two physical hosts that are connected to each other.

The tasks in this example involve the following:

Note that the example does not include any procedures for zone configuration. To configure zones, refer to Chapter 17, Planning and Configuring Non-Global Zones (Tasks), in Oracle Solaris 11.1 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management.

First, view information about links and IP interfaces on Host1.

# ipadm
lo0              loopback   ok        --         --
    lo0/v4        static     ok        --
net0             ip         ok        --         --
    net0/v4       static     ok        --
net1             ip         failed    ipmp0      --
    net1/v4       static     ok        --

Next, create a flow over net1 to isolate UDP traffic to Host2. Then, implement resource controls on the flow.

# flowadm add-flow -l net1 -a transport=udp udpflow
# flowadm set-flowprop -p maxbw=80 udpflow

Then, check the information about the created flow.

udpflow     net1   --       udp     --      --      --

# flowadm show-flowprop
FLOW         PROPERTY        VALUE          DEFAULT        POSSIBLE
udpflow      maxbw              80          --             --

On Host2, configure VNICs over net0 for each zone. Implement resource controls on each VNIC. Then, assign the VNICs to their respective zones.

# dladm create-vnic -l net0 vnic0
# dladm create-vnic -l net0 vnic1
# dladm create-vnic -l net0 vnic2

# dladm set-prop -p rxrings=4,txrings=4 vnic0
# dladm set-prop -p rxrings=2,txrings=2 vnic1
# dladm set-prop -p rxrings=1,txrings=1 vnic2

# zonecfg -z zone1
# zonecfg:zone1> add net
# zonecfg:zone1:net> set physical=vnic0
# zonecfg:zone1:net> end
# zonecfg:zone1> commit
# zonecfg:zone1> exit
# zoneadm -z zone1 reboot

# zonecfg -z zone2
# zonecfg:zone2> add net
# zonecfg:zone2:net> set physical=vnic1
# zonecfg:zone2:net> end
# zonecfg:zone2> commit
# zonecfg:zone2> exit
# zoneadm -z zone2 reboot

# zonecfg -z zone3
# zonecfg:zone3> add net
# zonecfg:zone3:net> set physical=vnic2
# zonecfg:zone3:net> end
# zonecfg:zone3> commit
# zonecfg:zone3> exit
# zoneadm -z zone3 reboot

Suppose that pool1, a set of CPUs in Host2, was previously configured for use by zone1. Bind that pool of CPUs to also manage network processes for zone1 as follows:

# dladm set-prop -p pool=pool1 vnic0

Finally, create a software-based client that shares rings with net0, the primary interface.

# dladm create-vnic -p rxrings=sw,txrings=sw -l net0 vnic3