User`s guide

200 XgOS User’s Guide • September 2014
In this example, Server1 attaches to an Oracle Fabric Interconnect over a vNIC. The
Oracle Fabric Interconnect is fitted with one 10 GE I/O card in slot 4 that connects to
a vNIC attached host. The Oracle Fabric Interconnect sends traffic to Server1 over a
vNIC named “test_1.whitney”. The QoS policer restricts the amount of ingress traffic
(from network to server) arriving on Server1 to 100 Mbps. The egress traffic (from
server to network) is also policed to 100 Mbps.
▼ Create a Policer for vNIC
The following steps were taken to create a policer for one vNIC. Use the same
approach for multiple vNICs:
1. Create a named policer policy:
In this example, the name of the set (policer policy) is “foo” and the CIR and PIR
are 100 Megabits per second. (Notice that you do not need to enter any qualifier
for CIR and PIR.) The “/100m_100m” is the name of the subset policy (profile)
within the policy called “foo”. It is a good practice to name your policer policies
after the conditions that they enforce on traffic. To differentiate your
configurations, the system enables you to assign different vNICs to different
subset policies.
Notice that automatic calculation is used to determine the CBS and PBS values for
this example. For more information about automatic calculation, see “Automatic
Calculation” on page 199.
2. Enable the QoS set and assign it to the appropriate I/O card (“4” in this
example):
3. On a vNIC, enable policing for the ingress direction (network to server):
Note – You can use the -policer=none option to remove the association of a QoS
profile and vNIC.
add qos network policer foo/100m_100m 100m 100m
set ethernet-card 4 qos -set=foo
set vnic test_1.whitney ingress-qos -policer=foo/100m_100m