1 '\" te
2 .\" Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH FLOWADM 1M "April 9, 2016"
7 .SH NAME
8 flowadm \- administer bandwidth resource control and priority for protocols,
9 services, containers, and virtual machines
10 .SH SYNOPSIS
11 .LP
12 .nf
13 \fBflowadm show-flow\fR [\fB-pP\fR] [\fB-S\fR] [\fB-s\fR [\fB-i\fR \fIinterval\fR]] [\fB-l\fR \fIlink\fR]
14 [\fB-o\fR \fIfield\fR[,...]] [\fIflow\fR]
15 .fi
16
17 .LP
18 .nf
19 \fBflowadm add-flow\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-l\fR \fIlink\fR \fB-a\fR \fIattr\fR=\fIvalue\fR[,...]
20 \fB-p\fR \fIprop\fR=\fIvalue\fR[,...] \fIflow\fR
21 \fBflowadm remove-flow\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] {\fB-l\fR \fIlink\fR | \fIflow\fR}
22 .fi
23
24 .LP
25 .nf
26 \fBflowadm set-flowprop\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-p\fR \fIprop\fR=\fIvalue\fR[,...] \fIflow\fR
27 \fBflowadm reset-flowprop\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] [\fB-p\fR \fIprop\fR[,...]] \fIflow\fR
28 \fBflowadm show-flowprop\fR [\fB-cP\fR] [\fB-l\fR \fIlink\fR] [\fB-o\fR \fIfield\fR[,...]]
29 [\fB-p\fR \fIprop\fR[,...]] [\fIflow\fR]
30 .fi
31
32 .LP
33 .nf
34 \fBflowadm show-usage\fR [\fB-a\fR] [\fB-d\fR | {\fB-p\fR \fIplotfile\fR \fB-F\fR \fIformat\fR}] [\fB-s\fR \fItime\fR]
35 [\fB-e\fR \fItime\fR] \fB-f\fR \fIfilename\fR [\fIflow\fR]
36 .fi
37
38 .SH DESCRIPTION
39 .LP
40 The \fBflowadm\fR command is used to create, modify, remove, and show
41 networking bandwidth and associated resources for a type of traffic on a
42 particular link.
43 .sp
44 .LP
45 The \fBflowadm\fR command allows users to manage networking bandwidth resources
46 for a transport, service, or a subnet. The service is specified as a
47 combination of transport and local port. The subnet is specified by its IP
48 address and subnet mask. The command can be used on any type of data link,
49 including physical links, virtual NICs, and link aggregations.
50 .sp
51 .LP
52 A flow is defined as a set of attributes based on Layer 3 and Layer 4 headers,
53 which can be used to identify a protocol, service, or a virtual machine. When a
54 flow is identified based on flow attributes, separate kernel resources
55 including layer 2, 3, and 4 queues, their processing threads, and other
56 resources are uniquely created for it, such that other traffic has minimal or
57 zero impact on it.
58 .sp
59 .LP
60 Inbound and outbound packet are matched to flows in a very fast and scalable
61 way, so that limits can be enforced with minimal performance impact.
62 .sp
63 .LP
64 The \fBflowadm\fR command can be used to identify a flow without imposing any
65 bandwidth resource control. This would result in the traffic type getting its
66 own resources and queues so that it is isolated from rest of the networking
67 traffic for more observable and deterministic behavior.
68 .sp
69 .LP
70 \fBflowadm\fR is implemented as a set of subcommands with corresponding
71 options. Options are described in the context of each subcommand.
72 .SH SUBCOMMANDS
73 .LP
74 The following subcommands are supported:
75 .sp
76 .ne 2
77 .na
78 \fB\fBflowadm show-flow\fR [\fB-pP\fR] [\fB-s\fR [\fB-i\fR \fIinterval\fR]]
79 [\fB-o\fR \fIfield\fR[,...]] [\fB-l\fR \fIlink\fR] [\fIflow\fR]\fR
80 .ad
81 .sp .6
82 .RS 4n
83 Show flow configuration information (the default) or statistics, either for all
84 flows, all flows on a link, or for the specified \fIflow\fR.
85 .sp
86 .ne 2
87 .na
88 \fB\fB-o\fR \fIfield\fR[,...]\fR
89 .ad
90 .sp .6
91 .RS 4n
92 A case-insensitive, comma-separated list of output fields to display. The field
93 name must be one of the fields listed below, or a special value \fBall\fR, to
94 display all fields. For each flow found, the following fields can be displayed:
95 .sp
96 .ne 2
97 .na
98 \fB\fBflow\fR\fR
99 .ad
100 .sp .6
101 .RS 4n
102 The name of the flow.
103 .RE
104
105 .sp
106 .ne 2
107 .na
108 \fB\fBlink\fR\fR
109 .ad
110 .sp .6
111 .RS 4n
112 The name of the link the flow is on.
113 .RE
114
115 .sp
116 .ne 2
117 .na
118 \fB\fBipaddr\fR\fR
119 .ad
120 .sp .6
121 .RS 4n
122 IP address of the flow. This can be either local or remote depending on how the
123 flow was defined.
124 .RE
125
126 .sp
127 .ne 2
128 .na
129 \fB\fBtransport\fR\fR
130 .ad
131 .sp .6
132 .RS 4n
133 The name of the layer for protocol to be used.
134 .RE
135
136 .sp
137 .ne 2
138 .na
139 \fB\fBport\fR\fR
140 .ad
141 .sp .6
142 .RS 4n
143 Local port of service for flow.
144 .RE
145
146 .sp
147 .ne 2
148 .na
149 \fB\fBdsfield\fR\fR
150 .ad
151 .sp .6
152 .RS 4n
153 Differentiated services value for flow and mask used with \fBDSFIELD\fR value
154 to state the bits of interest in the differentiated services field of the IP
155 header.
156 .RE
157
158 .RE
159
160 .sp
161 .ne 2
162 .na
163 \fB\fB-p\fR, \fB--parsable\fR\fR
164 .ad
165 .sp .6
166 .RS 4n
167 Display using a stable machine-parsable format.
168 .RE
169
170 .sp
171 .ne 2
172 .na
173 \fB\fB-P\fR, \fB--persistent\fR\fR
174 .ad
175 .sp .6
176 .RS 4n
177 Display persistent flow property information.
178 .RE
179
180 .sp
181 .ne 2
182 .na
183 \fB\fB-S\fR, \fB--continuous\fR\fR
184 .ad
185 .sp .6
186 .RS 4n
187 Continuously display network utilization by flow in a manner similar to the way
188 that \fBprstat\fR(1M) displays CPU utilization by process.
189 .RE
190
191 .sp
192 .ne 2
193 .na
194 \fB\fB-s\fR, \fB--statistics\fR\fR
195 .ad
196 .sp .6
197 .RS 4n
198 Displays flow statistics.
199 .RE
200
201 .sp
202 .ne 2
203 .na
204 \fB\fB-i\fR \fIinterval\fR, \fB--interval\fR=\fIinterval\fR\fR
205 .ad
206 .sp .6
207 .RS 4n
208 Used with the \fB-s\fR option to specify an interval, in seconds, at which
209 statistics should be displayed. If this option is not specified, statistics are
210 displayed once.
211 .RE
212
213 .sp
214 .ne 2
215 .na
216 \fB\fB-l\fR \fIlink\fR, \fB--link\fR=\fIlink\fR | \fIflow\fR\fR
217 .ad
218 .sp .6
219 .RS 4n
220 Display information for all flows on the named link or information for the
221 named flow.
222 .RE
223
224 .RE
225
226 .sp
227 .ne 2
228 .na
229 \fB\fBflowadm add-flow\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-l\fR
230 \fIlink\fR \fB-a\fR \fIattr\fR=\fIvalue\fR[,...] \fB-p\fR
231 \fIprop\fR=\fIvalue\fR[,...] \fIflow\fR\fR
232 .ad
233 .sp .6
234 .RS 4n
235 Adds a flow to the system. The flow is identified by its flow attributes and
236 properties.
237 .sp
238 As part of identifying a particular flow, its bandwidth resource can be limited
239 and its relative priority to other traffic can be specified. If no bandwidth
240 limit or priority is specified, the traffic still gets its unique layer 2, 3,
241 and 4 queues and processing threads, including NIC hardware resources (when
242 supported), so that the selected traffic can be separated from others and can
243 flow with minimal impact from other traffic.
244 .sp
245 .ne 2
246 .na
247 \fB\fB-t\fR, \fB--temporary\fR\fR
248 .ad
249 .sp .6
250 .RS 4n
251 The changes are temporary and will not persist across reboots. Persistence is
252 the default.
253 .RE
254
255 .sp
256 .ne 2
257 .na
258 \fB\fB-R\fR \fIroot-dir\fR, \fB--root-dir\fR=\fIroot-dir\fR\fR
259 .ad
260 .sp .6
261 .RS 4n
262 Specifies an alternate root directory where \fBflowadm\fR should apply
263 persistent creation.
264 .RE
265
266 .sp
267 .ne 2
268 .na
269 \fB\fB-l\fR \fIlink\fR, \fB--link\fR=\fIlink\fR\fR
270 .ad
271 .sp .6
272 .RS 4n
273 Specify the link to which the flow will be added.
274 .RE
275
276 .sp
277 .ne 2
278 .na
279 \fB\fB-a\fR \fIattr\fR=\fIvalue\fR[,...], \fB--attr\fR=\fIvalue\fR\fR
280 .ad
281 .sp .6
282 .RS 4n
283 A comma-separated list of attributes to be set to the specified values.
284 .RE
285
286 .sp
287 .ne 2
288 .na
289 \fB\fB-p\fR \fIprop\fR=\fIvalue\fR[,...], \fB--prop\fR=\fIvalue\fR[,...]\fR
290 .ad
291 .sp .6
292 .RS 4n
293 A comma-separated list of properties to be set to the specified values.
294 .RE
295
296 .RE
297
298 .sp
299 .ne 2
300 .na
301 \fB\fBflowadm remove-flow\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-l\fR
302 {\fIlink\fR | \fIflow\fR}\fR
303 .ad
304 .sp .6
305 .RS 4n
306 Remove an existing flow identified by its link or name.
307 .sp
308 .ne 2
309 .na
310 \fB\fB-t\fR, \fB--temporary\fR\fR
311 .ad
312 .sp .6
313 .RS 4n
314 The changes are temporary and will not persist across reboots. Persistence is
315 the default.
316 .RE
317
318 .sp
319 .ne 2
320 .na
321 \fB\fB-R\fR \fIroot-dir\fR, \fB--root-dir\fR=\fIroot-dir\fR\fR
322 .ad
323 .sp .6
324 .RS 4n
325 Specifies an alternate root directory where \fBflowadm\fR should apply
326 persistent removal.
327 .RE
328
329 .sp
330 .ne 2
331 .na
332 \fB\fB-l\fR \fIlink\fR | \fIflow\fR, \fB--link\fR=\fIlink\fR | \fIflow\fR\fR
333 .ad
334 .sp .6
335 .RS 4n
336 If a link is specified, remove all flows from that link. If a single flow is
337 specified, remove only that flow.
338 .RE
339
340 .RE
341
342 .sp
343 .ne 2
344 .na
345 \fB\fBflowadm set-flowprop\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-p\fR
346 \fIprop\fR=\fIvalue\fR[,...] \fIflow\fR\fR
347 .ad
348 .sp .6
349 .RS 4n
350 Set values of one or more properties on the flow specified by name. The
351 complete list of properties can be retrieved using the \fBshow-flow\fR
352 subcommand.
353 .sp
354 .ne 2
355 .na
356 \fB\fB-t\fR, \fB--temporary\fR\fR
357 .ad
358 .sp .6
359 .RS 4n
360 The changes are temporary and will not persist across reboots. Persistence is
361 the default.
362 .RE
363
364 .sp
365 .ne 2
366 .na
367 \fB\fB-R\fR \fIroot-dir\fR, \fB--root-dir\fR=\fIroot-dir\fR\fR
368 .ad
369 .sp .6
370 .RS 4n
371 Specifies an alternate root directory where \fBflowadm\fR should apply
517 .na
518 \fB\fB-P\fR, \fB--persistent\fR\fR
519 .ad
520 .sp .6
521 .RS 4n
522 Display persistent flow property information.
523 .RE
524
525 .sp
526 .ne 2
527 .na
528 \fB\fB-p\fR \fIprop\fR[,...], \fB--prop\fR=\fIprop\fR[,...]\fR
529 .ad
530 .sp .6
531 .RS 4n
532 A comma-separated list of properties to show.
533 .RE
534
535 .RE
536
537 .sp
538 .ne 2
539 .na
540 \fB\fBflowadm show-usage\fR [\fB-a\fR] [\fB-d\fR | {\fB-p\fR \fIplotfile\fR
541 \fB-F\fR \fIformat\fR}] [\fB-s\fR \fItime\fR] [\fB-e\fR \fItime\fR]
542 [\fIflow\fR]\fR
543 .ad
544 .sp .6
545 .RS 4n
546 Show the historical network flow usage from a stored extended accounting file.
547 Configuration and enabling of network accounting through \fBacctadm\fR(1M) is
548 required. The default output will be the summary of flow usage for the entire
549 period of time in which extended accounting was enabled.
550 .sp
551 .ne 2
552 .na
553 \fB\fB-a\fR\fR
554 .ad
555 .sp .6
556 .RS 4n
557 Display all historical network usage for the specified period of time during
558 which extended accounting is enabled. This includes the usage information for
559 the flows that have already been deleted.
560 .RE
561
562 .sp
563 .ne 2
564 .na
565 \fB\fB-d\fR\fR
566 .ad
567 .sp .6
568 .RS 4n
569 Display the dates for which there is logging information. The date is in the
570 format \fIDD\fR/\fIMM\fR/\fIYYYY\fR.
571 .RE
572
573 .sp
574 .ne 2
575 .na
576 \fB\fB-F\fR \fIformat\fR\fR
577 .ad
578 .sp .6
579 .RS 4n
580 Specifies the format of \fIplotfile\fR that is specified by the \fB-p\fR
581 option. As of this release, \fBgnuplot\fR is the only supported format.
582 .RE
583
584 .sp
585 .ne 2
586 .na
587 \fB\fB-p\fR \fIplotfile\fR\fR
588 .ad
589 .sp .6
590 .RS 4n
591 When specified with \fB-s\fR or \fB-e\fR (or both), outputs flow usage data to
592 a file of the format specified by the \fB-F\fR option, which is required.
593 .RE
594
595 .sp
596 .ne 2
597 .na
598 \fB\fB-s\fR \fItime\fR, \fB-e\fR \fItime\fR\fR
599 .ad
600 .sp .6
601 .RS 4n
602 Start and stop times for data display. Time is in the format
603 \fIYYYY\fR.\fIMM\fR.\fIDD\fR,\fIhh\fR:\fImm\fR:\fIss\fR.
604 .RE
605
606 .sp
607 .ne 2
608 .na
609 \fB\fB-f\fR \fIfilename\fR\fR
610 .ad
611 .sp .6
612 .RS 4n
613 Read extended accounting records of network flow usage from \fIfilename\fR.
614 .RE
615
616 .sp
617 .ne 2
618 .na
619 \fB\fIflow\fR\fR
620 .ad
621 .sp .6
622 .RS 4n
623 If specified, display the network flow usage only from the named flow.
624 Otherwise, display network usage from all flows.
625 .RE
626
627 .RE
628
629 .SS "Flow Attributes"
630 .LP
631 The flow operand that identify a flow in a \fBflowadm\fR command is a
632 comma-separated list of one or more keyword, value pairs from the list below.
633 .sp
634 .ne 2
635 .na
636 \fB\fBlocal_ip\fR[\fB/\fR\fIprefix_len\fR]\fR
637 .ad
638 .sp .6
639 .RS 4n
640 Identifies a network flow by the local IP address. \fIvalue\fR must be a IPv4
641 address in dotted-decimal notation or an IPv6 address in colon-separated
642 notation. \fIprefix_len\fR is optional.
643 .sp
644 If \fIprefix_len\fR is specified, it describes the netmask for a subnet
645 address, following the same notation convention of \fBifconfig\fR(1M) and
646 \fBroute\fR(1M) addresses. If unspecified, the given IP address will be
647 considered as a host address for which the default prefix length for a IPv4
648 address is \fB/32\fR and for IPv6 is \fB/128\fR.
649 .RE
650
651 .sp
652 .ne 2
653 .na
654 \fB\fBremote_ip\fR[\fB/\fR\fIprefix_len\fR]\fR
655 .ad
656 .sp .6
657 .RS 4n
658 Identifies a network flow by the remote IP address. The syntax is the same as
659 \fBlocal_ip\fR attributes
660 .RE
661
662 .sp
663 .ne 2
664 .na
665 \fB\fBtransport\fR={\fBtcp\fR|\fBudp\fR|\fBsctp\fR|\fBicmp\fR|\fBicmpv6\fR}\fR
666 .ad
667 .sp .6
668 .RS 4n
669 Identifies a layer 4 protocol to be used. It is typically used in combination
670 with local_port to identify the service that needs special attention.
671 .RE
672
673 .sp
674 .ne 2
675 .na
676 \fB\fBlocal_port\fR\fR
677 .ad
678 .sp .6
679 .RS 4n
680 Identifies a service specified by the local port.
681 .RE
682
683 .sp
684 .ne 2
685 .na
686 \fB\fBdsfield\fR[\fB:\fR\fIdsfield_mask\fR]\fR
687 .ad
688 .sp .6
689 .RS 4n
690 Identifies the 8-bit differentiated services field (as defined in RFC 2474).
691 .sp
692 The optional \fIdsfield_mask\fR is used to state the bits of interest in the
693 differentiated services field when comparing with the \fBdsfield\fR value. A
694 \fB0\fR in a bit position indicates that the bit value needs to be ignored and
695 a \fB1\fR indicates otherwise. The mask can range from \fB0x01\fR to
696 \fB0xff\fR. If \fIdsfield_mask\fR is not specified, the default mask \fB0xff\fR
697 is used. Both the \fBdsfield\fR value and mask must be in hexadecimal.
698 .RE
699
700 .sp
701 .LP
702 The following five types of combinations of attributes are supported:
703 .sp
704 .in +2
705 .nf
706 local_ip[/\fIprefixlen\fR]=\fIaddress\fR
707 remote_ip[/\fIprefixlen\fR]=\fIaddress\fR
708 transport={tcp|udp|sctp|icmp|icmpv6}
709 transport={tcp|udp|sctp},local_port=\fIport\fR
710 dsfield=\fIval\fR[:\fIdsfield_mask\fR]
711 .fi
712 .in -2
713 .sp
714
715 .sp
716 .LP
717 On a given link, the combinations above are mutually exclusive. An attempt to
718 create flows of different combinations will fail.
719 .SS "Restrictions"
720 .LP
721 There are individual flow restrictions and flow restrictions per zone.
722 .SS "Individual Flow Restrictions"
723 .LP
724 Restrictions on individual flows do not require knowledge of other flows that
725 have been added to the link.
726 .sp
727 .LP
728 An attribute can be listed only once for each flow. For example, the following
729 command is not valid:
730 .sp
731 .in +2
732 .nf
733 # \fBflowadm add-flow -l vnic1 -a local_port=80,local_port=8080 httpflow\fR
734 .fi
735 .in -2
736 .sp
737
738 .sp
739 .LP
740 \fBtransport\fR and \fBlocal_port\fR:
741 .sp
742 .LP
743 TCP, UDP, or SCTP flows can be specified with a local port. An ICMP or ICMPv6
749 # \fBflowadm add-flow -l e1000g0 -a transport=tcp,local_port=80 \e
750 udp80flow\fR
751 .fi
752 .in -2
753 .sp
754
755 .sp
756 .LP
757 The following commands are not valid:
758 .sp
759 .in +2
760 .nf
761 # \fBflowadm add-flow -l e1000g0 -a local_port=25 flow25\fR
762 # \fBflowadm add-flow -l e1000g0 -a transport=icmpv6,local_port=16 \e
763 flow16\fR
764 .fi
765 .in -2
766 .sp
767
768 .SS "Flow Restrictions Per Zone"
769 .LP
770 Within a zone, no two flows can have the same name. After adding a flow with
771 the link specified, the link will not be required for display, modification, or
772 deletion of the flow.
773 .SS "Flow Properties"
774 .LP
775 The following flow properties are supported. Note that the ability to set a
776 given property to a given value depends on the driver and hardware.
777 .sp
778 .ne 2
779 .na
780 \fB\fBmaxbw\fR\fR
781 .ad
782 .sp .6
783 .RS 4n
784 Sets the full duplex bandwidth for the flow. The bandwidth is specified as an
785 integer with one of the scale suffixes(\fBK\fR, \fBM\fR, or \fBG\fR for Kbps,
786 Mbps, and Gbps). If no units are specified, the input value will be read as
787 Mbps. The default is no bandwidth limit.
788 .RE
789
790 .sp
791 .ne 2
792 .na
793 \fB\fBpriority\fR\fR
794 .ad
795 .sp .6
796 .RS 4n
797 Sets the relative priority for the flow. The value can be given as one of the
798 tokens \fBhigh\fR, \fBmedium\fR, or \fBlow\fR. The default is \fBmedium\fR.
799 .RE
800
801 .SH EXAMPLES
802 .LP
803 \fBExample 1 \fRCreating a Policy Around a Mission-Critical Port
804 .sp
805 .LP
806 The command below creates a policy around inbound HTTPS traffic on an HTTPS
807 server so that HTTPS obtains dedicated NIC hardware and kernel TCP/IP
808 resources. The name specified, \fBhttps-1\fR, can be used later to modify or
809 delete the policy.
810
811 .sp
812 .in +2
813 .nf
814 # \fBflowadm add-flow -l bge0 -a transport=TCP,local_port=443 https-1\fR
815 # \fBflowadm show-flow -l bge0\fR
816 FLOW LINK IP ADDR PROTO PORT DSFLD
817 https1 bge0 -- tcp 443 --
818 .fi
819 .in -2
820 .sp
821
822 .LP
823 \fBExample 2 \fRModifying an Existing Policy to Add Bandwidth Resource Control
824 .sp
825 .LP
826 The following command modifies the \fBhttps-1\fR policy from the preceding
827 example. The command adds bandwidth control and give the policy a high
828 priority.
829
830 .sp
831 .in +2
832 .nf
833 # \fBflowadm set-flowprop -p maxbw=500M,priority=high https-1\fR
834 # \fBflowadm show-flow https-1\fR
835 FLOW LINK IP ADDR PROTO PORT DSFLD
836 https1 bge0 -- tcp 443 --
837
838 # \fBflowadm show-flowprop https-1\fR
839 FLOW PROPERTY VALUE DEFAULT POSSIBLE
840 https-1 maxbw 500 -- --
841 https-1 priority HIGH -- LOW,NORMAL,HIGH
842 .fi
843 .in -2
844 .sp
845
846 .LP
847 \fBExample 3 \fRLimiting the UDP Bandwidth Usage
848 .sp
849 .LP
850 The following command creates a policy for UDP protocol so that it cannot
851 consume more than 100Mbps of available bandwidth. The flow is named
852 \fBlimit-udp-1\fR.
853
854 .sp
855 .in +2
856 .nf
857 # \fBflowadm add-flow -l bge0 -a transport=UDP -p maxbw=100M, \e
858 priority=low limit-udp-1\fR
859 .fi
860 .in -2
861 .sp
862
863 .LP
864 \fBExample 4 \fRShowing Flow Usage
865 .sp
866 .LP
867 Flow usage statistics can be stored using the extended accounting facility,
868 \fBacctadm\fR(1M).
869
870 .sp
871 .in +2
872 .nf
873 # \fBacctadm -e extended -f /var/log/net.log net\fR
874
875 # \fBacctadm net\fR
876 Network accounting: active
877 Network accounting file: /var/log/net.log
878 Tracked Network resources: extended
879 Untracked Network resources: none
880 .fi
881 .in -2
882 .sp
883
884 .sp
885 .LP
886 The historical data that was saved can be retrieved in summary form using the
887 \fBshow-usage\fR subcommand of \fBflowadm\fR.
888
889 .LP
890 \fBExample 5 \fRSetting Policy, Making Use of \fBdsfield\fR Attribute
891 .sp
892 .LP
893 The following command sets a policy for EF PHB (DSCP value of 101110 from RFC
894 2598) with a bandwidth of 500 Mbps and a high priority. The \fBdsfield\fR value
895 for this flow will be \fB0x2e\fR (101110) with the \fBdsfield_mask\fR being
896 \fB0xfc\fR (because we want to ignore the 2 least significant bits).
897
898 .sp
899 .in +2
900 .nf
901 # \fBflowadm add-flow -l bge0 -a dsfield=0x2e:0xfc \e
902 -p maxbw=500M,priority=high efphb-flow\fR
903 .fi
904 .in -2
905 .sp
906
907 .sp
908 .LP
909 Display summary information:
910
911 .sp
912 .in +2
913 .nf
914 # \fBflowadm show-usage -f /var/log/net.log\fR
915 FLOW DURATION IPACKETS RBYTES OPACKETS OBYTES BANDWIDTH
916 flowtcp 100 1031 546908 0 0 43.76 Kbps
917 flowudp 0 0 0 0 0 0.00 Mbps
918 .fi
919 .in -2
920 .sp
921
922 .sp
923 .LP
924 Display dates for which logging information is available:
925
926 .sp
927 .in +2
928 .nf
929 # \fBflowadm show-usage -d -f /var/log/net.log\fR
930 02/19/2008
931 .fi
932 .in -2
933 .sp
934
935 .sp
936 .LP
937 Display logging information for \fBflowtcp\fR starting at 02/19/2008, 10:38:46
938 and ending at 02/19/2008, 10:40:06:
939
940 .sp
941 .in +2
942 .nf
943 # \fBflowadm show-usage -s 02/19/2008,10:39:06 -e 02/19/2008,10:40:06 \e
944 -f /var/log/net.log flowtcp\fR
945 FLOW TIME IPACKETS RBYTES OPACKETS OBYTES BANDWIDTH
946 flowtcp 10:39:06 1 1546 4 6539 3.23 Kbps
947 flowtcp 10:39:26 2 3586 5 9922 5.40 Kbps
948 flowtcp 10:39:46 1 240 1 216 182.40 bps
949 flowtcp 10:40:06 0 0 0 0 0.00 bps
950 .fi
951 .in -2
952 .sp
953
954 .sp
955 .LP
956 Output the same information as above as a plotfile:
957
958 .sp
959 .in +2
960 .nf
961 # \fBflowadm show-usage -s 02/19/2008,10:39:06 -e 02/19/2008,10:40:06 \e
962 -p /home/plot/myplot -F gnuplot -f /var/log/net.log flowtcp\fR
963 # \fBTime tcp-flow\fR
964 10:39:06 3.23
965 10:39:26 5.40
966 10:39:46 0.18
967 10:40:06 0.00
968 .fi
969 .in -2
970 .sp
971
972 .SH EXIT STATUS
973 .ne 2
974 .na
975 \fB\fB0\fR\fR
976 .ad
977 .sp .6
978 .RS 4n
979 All actions were performed successfully.
980 .RE
981
982 .sp
983 .ne 2
984 .na
985 \fB\fB>0\fR\fR
986 .ad
987 .sp .6
988 .RS 4n
989 An error occurred.
990 .RE
991
992 .SH ATTRIBUTES
993 .LP
994 See \fBattributes\fR(5) for descriptions of the following attributes:
995 .sp
996
997 .sp
998 .TS
999 box;
1000 c | c
1001 l | l .
1002 ATTRIBUTE TYPE ATTRIBUTE VALUE
1003 _
1004 Interface Stability Committed
1005 .TE
1006
1007 .SH SEE ALSO
1008 .LP
1009 \fBacctadm\fR(1M), \fBdladm\fR(1M), \fBifconfig\fR(1M), \fBprstat\fR(1M),
1010 \fBroute\fR(1M), \fBattributes\fR(5), \fBdlpi\fR(7P)
|
1 '\" te
2 .\" Copyright 2020 Peter Tribble
3 .\" Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH FLOWADM 1M "February 26, 2020"
8 .SH NAME
9 flowadm \- administer bandwidth resource control and priority for protocols,
10 services, containers, and virtual machines
11 .SH SYNOPSIS
12 .nf
13 \fBflowadm add-flow\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-l\fR \fIlink\fR \fB-a\fR \fIattr\fR=\fIvalue\fR[,...]
14 [\fB-p\fR \fIprop\fR=\fIvalue\fR[,...]] \fIflow\fR
15 \fBflowadm remove-flow\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] {\fB-l\fR \fIlink\fR | \fIflow\fR}
16 \fBflowadm show-flow\fR [\fB-p\fR] [\fB-l\fR \fIlink\fR] [\fB-o\fR \fIfield\fR[,...]] [\fIflow\fR]
17 .fi
18
19 .LP
20 .nf
21 \fBflowadm set-flowprop\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-p\fR \fIprop\fR=\fIvalue\fR[,...] \fIflow\fR
22 \fBflowadm reset-flowprop\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] [\fB-p\fR \fIprop\fR[,...]] \fIflow\fR
23 \fBflowadm show-flowprop\fR [\fB-cP\fR] [\fB-l\fR \fIlink\fR] [\fB-o\fR \fIfield\fR[,...]]
24 [\fB-p\fR \fIprop\fR[,...]] [\fIflow\fR]
25 .fi
26
27 .SH DESCRIPTION
28 The \fBflowadm\fR command is used to create, modify, remove, and show
29 networking bandwidth and associated resources for a type of traffic on a
30 particular link.
31 .sp
32 .LP
33 The \fBflowadm\fR command allows users to manage networking bandwidth resources
34 for a transport, service, or a subnet. The service is specified as a
35 combination of transport and local port. The subnet is specified by its IP
36 address and subnet mask. The command can be used on any type of data link,
37 including physical links, virtual NICs, and link aggregations.
38 .sp
39 .LP
40 A flow is defined as a set of attributes based on Layer 3 and Layer 4 headers,
41 which can be used to identify a protocol, service, or a virtual machine. When a
42 flow is identified based on flow attributes, separate kernel resources
43 including layer 2, 3, and 4 queues, their processing threads, and other
44 resources are uniquely created for it, such that other traffic has minimal or
45 zero impact on it.
46 .sp
47 .LP
48 Inbound and outbound packet are matched to flows in a very fast and scalable
49 way, so that limits can be enforced with minimal performance impact.
50 .sp
51 .LP
52 The \fBflowadm\fR command can be used to define a flow without imposing any
53 bandwidth resource control. This would result in the traffic type getting its
54 own resources and queues so that it is isolated from rest of the networking
55 traffic for more observable and deterministic behavior.
56 .sp
57 .LP
58 \fBflowadm\fR is implemented as a set of subcommands with corresponding
59 options. Options are described in the context of each subcommand.
60 .SH SUBCOMMANDS
61 The following subcommands are supported:
62 .sp
63 .ne 2
64 .na
65 \fB\fBflowadm add-flow\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-l\fR
66 \fIlink\fR \fB-a\fR \fIattr\fR=\fIvalue\fR[,...] [\fB-p\fR
67 \fIprop\fR=\fIvalue\fR[,...]] \fIflow\fR\fR
68 .ad
69 .sp .6
70 .RS 4n
71 Adds a flow to the system. The flow is identified by its flow attributes and
72 properties.
73 .sp
74 As part of identifying a particular flow, its bandwidth resource can be limited
75 and its relative priority to other traffic can be specified. If no bandwidth
76 limit or priority is specified, the traffic still gets its unique layer 2, 3,
77 and 4 queues and processing threads, including NIC hardware resources (when
78 supported), so that the selected traffic can be separated from others and can
79 flow with minimal impact from other traffic.
80 .sp
81 .ne 2
82 .na
83 \fB\fB-t\fR, \fB--temporary\fR\fR
84 .ad
85 .sp .6
86 .RS 4n
87 The changes are temporary and will not persist across reboots. Persistence is
88 the default.
89 .RE
90
91 .sp
92 .ne 2
93 .na
94 \fB\fB-R\fR \fIroot-dir\fR, \fB--root-dir\fR=\fIroot-dir\fR\fR
95 .ad
96 .sp .6
97 .RS 4n
98 Specifies an alternate root directory where \fBflowadm\fR should apply
99 persistent creation.
100 .RE
101
102 .sp
103 .ne 2
104 .na
105 \fB\fB-l\fR \fIlink\fR, \fB--link\fR=\fIlink\fR\fR
106 .ad
107 .sp .6
108 .RS 4n
109 Specify the link to which the flow will be added.
110 .RE
111
112 .sp
113 .ne 2
114 .na
115 \fB\fB-a\fR \fIattr\fR=\fIvalue\fR[,...], \fB--attr\fR=\fIvalue\fR\fR
116 .ad
117 .sp .6
118 .RS 4n
119 A mandatory comma-separated list of attributes to be set to the specified
120 values.
121 .RE
122
123 .sp
124 .ne 2
125 .na
126 \fB\fB-p\fR \fIprop\fR=\fIvalue\fR[,...], \fB--prop\fR=\fIvalue\fR[,...]\fR
127 .ad
128 .sp .6
129 .RS 4n
130 An optional comma-separated list of properties to be set to the specified
131 values. Flow properties are documented in the "Flow Properties" section, below.
132 .RE
133
134 .RE
135
136 .sp
137 .ne 2
138 .na
139 \fB\fBflowadm remove-flow\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-l\fR
140 {\fIlink\fR | \fIflow\fR}\fR
141 .ad
142 .sp .6
143 .RS 4n
144 Remove an existing flow identified by its link or name.
145 .sp
146 .ne 2
147 .na
148 \fB\fB-t\fR, \fB--temporary\fR\fR
149 .ad
150 .sp .6
151 .RS 4n
152 The changes are temporary and will not persist across reboots. Persistence is
153 the default.
154 .RE
155
156 .sp
157 .ne 2
158 .na
159 \fB\fB-R\fR \fIroot-dir\fR, \fB--root-dir\fR=\fIroot-dir\fR\fR
160 .ad
161 .sp .6
162 .RS 4n
163 Specifies an alternate root directory where \fBflowadm\fR should apply
164 persistent removal.
165 .RE
166
167 .sp
168 .ne 2
169 .na
170 \fB\fB-l\fR \fIlink\fR | \fIflow\fR, \fB--link\fR=\fIlink\fR | \fIflow\fR\fR
171 .ad
172 .sp .6
173 .RS 4n
174 If a link is specified, remove all flows from that link. If a single flow is
175 specified, remove only that flow.
176 .RE
177
178 .RE
179
180 .sp
181 .ne 2
182 .na
183 \fB\fBflowadm show-flow\fR [\fB-pP\fR] [\fB-s\fR [\fB-i\fR \fIinterval\fR]]
184 [\fB-o\fR \fIfield\fR[,...]] [\fB-l\fR \fIlink\fR] [\fIflow\fR]\fR
185 .ad
186 .sp .6
187 .RS 4n
188 Show flow configuration information, either for all
189 flows, all flows on a link, or for the specified \fIflow\fR.
190 .sp
191 .ne 2
192 .na
193 \fB\fB-o\fR \fIfield\fR[,...]\fR
194 .ad
195 .sp .6
196 .RS 4n
197 A case-insensitive, comma-separated list of output fields to display. The field
198 name must be one of the fields listed below, or a special value \fBall\fR, to
199 display all fields. For each flow found, the following fields can be displayed:
200 .sp
201 .ne 2
202 .na
203 \fB\fBflow\fR\fR
204 .ad
205 .sp .6
206 .RS 4n
207 The name of the flow.
208 .RE
209
210 .sp
211 .ne 2
212 .na
213 \fB\fBlink\fR\fR
214 .ad
215 .sp .6
216 .RS 4n
217 The name of the link the flow is on.
218 .RE
219
220 .sp
221 .ne 2
222 .na
223 \fB\fBipaddr\fR\fR
224 .ad
225 .sp .6
226 .RS 4n
227 IP address of the flow. This can be either local or remote depending on how the
228 flow was defined.
229 .RE
230
231 .sp
232 .ne 2
233 .na
234 \fB\fBproto\fR\fR
235 .ad
236 .sp .6
237 .RS 4n
238 The name of the layer for protocol to be used.
239 .RE
240
241 .sp
242 .ne 2
243 .na
244 \fB\fBlport\fR\fR
245 .ad
246 .sp .6
247 .RS 4n
248 Local port of service for flow.
249 .RE
250
251 .sp
252 .ne 2
253 .na
254 \fB\fBrport\fR\fR
255 .ad
256 .sp .6
257 .RS 4n
258 Remote port of service for flow.
259 .RE
260
261 .sp
262 .ne 2
263 .na
264 \fB\fBdsfld\fR\fR
265 .ad
266 .sp .6
267 .RS 4n
268 Differentiated services value for flow and mask used with \fBDSFIELD\fR value
269 to state the bits of interest in the differentiated services field of the IP
270 header.
271 .RE
272
273 .RE
274
275 .sp
276 .ne 2
277 .na
278 \fB\fB-p\fR, \fB--parsable\fR\fR
279 .ad
280 .sp .6
281 .RS 4n
282 Display using a stable machine-parsable format.
283 .RE
284
285 .sp
286 .ne 2
287 .na
288 \fB\fB-P\fR, \fB--persistent\fR\fR
289 .ad
290 .sp .6
291 .RS 4n
292 Display persistent flow property information.
293 .RE
294
295 .sp
296 .ne 2
297 .na
298 \fB\fB-l\fR \fIlink\fR, \fB--link\fR=\fIlink\fR | \fIflow\fR\fR
299 .ad
300 .sp .6
301 .RS 4n
302 Display information for all flows on the named link or information for the
303 named flow.
304 .RE
305
306 .RE
307
308 .sp
309 .ne 2
310 .na
311 \fB\fBflowadm set-flowprop\fR [\fB-t\fR] [\fB-R\fR \fIroot-dir\fR] \fB-p\fR
312 \fIprop\fR=\fIvalue\fR[,...] \fIflow\fR\fR
313 .ad
314 .sp .6
315 .RS 4n
316 Set values of one or more properties on the flow specified by name. The
317 complete list of properties can be retrieved using the \fBshow-flowprop\fR
318 subcommand.
319 .sp
320 .ne 2
321 .na
322 \fB\fB-t\fR, \fB--temporary\fR\fR
323 .ad
324 .sp .6
325 .RS 4n
326 The changes are temporary and will not persist across reboots. Persistence is
327 the default.
328 .RE
329
330 .sp
331 .ne 2
332 .na
333 \fB\fB-R\fR \fIroot-dir\fR, \fB--root-dir\fR=\fIroot-dir\fR\fR
334 .ad
335 .sp .6
336 .RS 4n
337 Specifies an alternate root directory where \fBflowadm\fR should apply
483 .na
484 \fB\fB-P\fR, \fB--persistent\fR\fR
485 .ad
486 .sp .6
487 .RS 4n
488 Display persistent flow property information.
489 .RE
490
491 .sp
492 .ne 2
493 .na
494 \fB\fB-p\fR \fIprop\fR[,...], \fB--prop\fR=\fIprop\fR[,...]\fR
495 .ad
496 .sp .6
497 .RS 4n
498 A comma-separated list of properties to show.
499 .RE
500
501 .RE
502
503 .SS "Flow Attributes"
504 The flow operand that identify a flow in a \fBflowadm\fR command is a
505 comma-separated list of one or more keyword, value pairs from the list below.
506 .sp
507 .ne 2
508 .na
509 \fB\fBlocal_ip\fR[\fB/\fR\fIprefix_len\fR]\fR
510 .ad
511 .sp .6
512 .RS 4n
513 Identifies a network flow by the local IP address. \fIvalue\fR must be a IPv4
514 address in dotted-decimal notation or an IPv6 address in colon-separated
515 notation. \fIprefix_len\fR is optional.
516 .sp
517 If \fIprefix_len\fR is specified, it describes the netmask for a subnet
518 address, following the same notation convention of \fBifconfig\fR(1M) and
519 \fBroute\fR(1M) addresses. If unspecified, the given IP address will be
520 considered as a host address for which the default prefix length for a IPv4
521 address is \fB/32\fR and for IPv6 is \fB/128\fR.
522 .RE
523
524 .sp
525 .ne 2
526 .na
527 \fB\fBremote_ip\fR[\fB/\fR\fIprefix_len\fR]\fR
528 .ad
529 .sp .6
530 .RS 4n
531 Identifies a network flow by the remote IP address. The syntax is the same as
532 the \fBlocal_ip\fR attribute.
533 .RE
534
535 .sp
536 .ne 2
537 .na
538 \fB\fBtransport\fR={\fBtcp\fR|\fBudp\fR|\fBsctp\fR|\fBicmp\fR|\fBicmpv6\fR}\fR
539 .ad
540 .sp .6
541 .RS 4n
542 Identifies a layer 4 protocol to be used. It is typically used in combination
543 with local_port to identify the service that needs special attention.
544 .RE
545
546 .sp
547 .ne 2
548 .na
549 \fB\fBlocal_port\fR\fR
550 .ad
551 .sp .6
552 .RS 4n
553 Identifies a service specified by the local port.
554 .RE
555
556 .sp
557 .ne 2
558 .na
559 \fB\fBremote_port\fR\fR
560 .ad
561 .sp .6
562 .RS 4n
563 Identifies a service specified by the remote port.
564 .RE
565
566 .sp
567 .ne 2
568 .na
569 \fB\fBdsfield\fR[\fB:\fR\fIdsfield_mask\fR]\fR
570 .ad
571 .sp .6
572 .RS 4n
573 Identifies the 8-bit differentiated services field (as defined in RFC 2474).
574 .sp
575 The optional \fIdsfield_mask\fR is used to state the bits of interest in the
576 differentiated services field when comparing with the \fBdsfield\fR value. A
577 \fB0\fR in a bit position indicates that the bit value needs to be ignored and
578 a \fB1\fR indicates otherwise. The mask can range from \fB0x01\fR to
579 \fB0xff\fR. If \fIdsfield_mask\fR is not specified, the default mask \fB0xff\fR
580 is used. Both the \fBdsfield\fR value and mask must be in hexadecimal.
581 .RE
582
583 .sp
584 .LP
585 The following six types of combinations of attributes are supported:
586 .sp
587 .in +2
588 .nf
589 local_ip[/\fIprefixlen\fR]=\fIaddress\fR
590 remote_ip[/\fIprefixlen\fR]=\fIaddress\fR
591 transport={tcp|udp|sctp|icmp|icmpv6}
592 transport={tcp|udp|sctp},local_port=\fIport\fR
593 transport={tcp|udp|sctp},remote_port=\fIport\fR
594 dsfield=\fIval\fR[:\fIdsfield_mask\fR]
595 .fi
596 .in -2
597 .sp
598
599 .sp
600 .LP
601 On a given link, the types of combinations above are mutually exclusive. An
602 attempt to create flows of different types on a given link will fail.
603 .SS "Restrictions"
604 There are individual flow restrictions and flow restrictions per zone.
605 .SS "Individual Flow Restrictions"
606 Restrictions on individual flows do not require knowledge of other flows that
607 have been added to the link.
608 .sp
609 .LP
610 An attribute can be listed only once for each flow. For example, the following
611 command is not valid:
612 .sp
613 .in +2
614 .nf
615 # \fBflowadm add-flow -l vnic1 -a local_port=80,local_port=8080 httpflow\fR
616 .fi
617 .in -2
618 .sp
619
620 .sp
621 .LP
622 \fBtransport\fR and \fBlocal_port\fR:
623 .sp
624 .LP
625 TCP, UDP, or SCTP flows can be specified with a local port. An ICMP or ICMPv6
631 # \fBflowadm add-flow -l e1000g0 -a transport=tcp,local_port=80 \e
632 udp80flow\fR
633 .fi
634 .in -2
635 .sp
636
637 .sp
638 .LP
639 The following commands are not valid:
640 .sp
641 .in +2
642 .nf
643 # \fBflowadm add-flow -l e1000g0 -a local_port=25 flow25\fR
644 # \fBflowadm add-flow -l e1000g0 -a transport=icmpv6,local_port=16 \e
645 flow16\fR
646 .fi
647 .in -2
648 .sp
649
650 .SS "Flow Restrictions Per Zone"
651 Within a zone, no two flows can have the same name. After adding a flow with
652 the link specified, the link will not be required for display, modification, or
653 deletion of the flow.
654 .SS "Flow Properties"
655 The following flow properties are supported. Note that the ability to set a
656 given property to a given value depends on the driver and hardware.
657 .sp
658 .ne 2
659 .na
660 \fB\fBmaxbw\fR\fR
661 .ad
662 .sp .6
663 .RS 4n
664 Sets the full duplex bandwidth for the flow. The bandwidth is specified as an
665 integer with one of the scale suffixes(\fBK\fR, \fBM\fR, or \fBG\fR for Kbps,
666 Mbps, and Gbps). If no units are specified, the input value will be read as
667 Mbps. The default is no bandwidth limit.
668 .RE
669
670 .sp
671 .ne 2
672 .na
673 \fB\fBpriority\fR\fR
674 .ad
675 .sp .6
676 .RS 4n
677 Sets the relative priority for the flow. The value can be given as one of the
678 tokens \fBhigh\fR, \fBmedium\fR, or \fBlow\fR. The default is \fBmedium\fR.
679 .RE
680
681 .SH EXAMPLES
682 \fBExample 1 \fRCreating a Policy Around a Mission-Critical Port
683 .sp
684 .LP
685 The command below creates a policy around inbound HTTPS traffic on an HTTPS
686 server so that HTTPS obtains dedicated NIC hardware and kernel TCP/IP
687 resources. The name specified, \fBhttps-1\fR, can be used later to modify or
688 delete the policy.
689
690 .sp
691 .in +2
692 .nf
693 # \fBflowadm add-flow -l bge0 -a transport=TCP,local_port=443 https-1\fR
694 # \fBflowadm show-flow -l bge0\fR
695 FLOW LINK IPADDR PROTO LPORT RPORT DSFLD
696 https1 bge0 -- tcp 443 -- --
697 .fi
698 .in -2
699 .sp
700
701 .LP
702 \fBExample 2 \fRModifying an Existing Policy to Add Bandwidth Resource Control
703 .sp
704 .LP
705 The following command modifies the \fBhttps-1\fR policy from the preceding
706 example. The command adds bandwidth control and give the policy a high
707 priority.
708
709 .sp
710 .in +2
711 .nf
712 # \fBflowadm set-flowprop -p maxbw=500M,priority=high https-1\fR
713 # \fBflowadm show-flow https-1\fR
714 FLOW LINK IPADDR PROTO LPORT RPORT DSFLD
715 https-1 bge0 -- tcp 443 -- --
716
717 # \fBflowadm show-flowprop https-1\fR
718 FLOW PROPERTY VALUE DEFAULT POSSIBLE
719 https-1 maxbw 500 -- --
720 https-1 priority high -- low,medium,high
721 .fi
722 .in -2
723 .sp
724
725 .LP
726 \fBExample 3 \fRLimiting the UDP Bandwidth Usage
727 .sp
728 .LP
729 The following command creates a policy for UDP protocol so that it cannot
730 consume more than 100Mbps of available bandwidth. The flow is named
731 \fBlimit-udp-1\fR.
732
733 .sp
734 .in +2
735 .nf
736 # \fBflowadm add-flow -l bge0 -a transport=UDP -p maxbw=100M, \e
737 priority=low limit-udp-1\fR
738 .fi
739 .in -2
740 .sp
741
742 .LP
743 \fBExample 4 \fRSetting Policy, Making Use of \fBdsfield\fR Attribute
744 .sp
745 .LP
746 The following command sets a policy for EF PHB (DSCP value of 101110 from RFC
747 2598) with a bandwidth of 500 Mbps and a high priority. The \fBdsfield\fR value
748 for this flow will be \fB0x2e\fR (101110) with the \fBdsfield_mask\fR being
749 \fB0xfc\fR (because we want to ignore the 2 least significant bits).
750
751 .sp
752 .in +2
753 .nf
754 # \fBflowadm add-flow -l bge0 -a dsfield=0x2e:0xfc \e
755 -p maxbw=500M,priority=high efphb-flow\fR
756 .fi
757 .in -2
758 .sp
759
760 .SH EXIT STATUS
761 .ne 2
762 .na
763 \fB\fB0\fR\fR
764 .ad
765 .sp .6
766 .RS 4n
767 All actions were performed successfully.
768 .RE
769
770 .sp
771 .ne 2
772 .na
773 \fB\fB>0\fR\fR
774 .ad
775 .sp .6
776 .RS 4n
777 An error occurred.
778 .RE
779
780 .SH ATTRIBUTES
781 See \fBattributes\fR(5) for descriptions of the following attributes:
782 .sp
783
784 .sp
785 .TS
786 box;
787 c | c
788 l | l .
789 ATTRIBUTE TYPE ATTRIBUTE VALUE
790 _
791 Interface Stability Committed
792 .TE
793
794 .SH SEE ALSO
795 \fBdladm\fR(1M), \fBflowstat\fR(1M), \fBifconfig\fR(1M),
796 \fBroute\fR(1M), \fBattributes\fR(5)
797
798 .SH NOTES
799 The display of statistics by the \fBshow-flow\fR subcommand, and the
800 \fBshow-usage\fR subcommand, have been removed. This functionality can
801 now be accessed using the \fBflowstat\fR(1M) utility.
|