net sfc sf
net sfc sf(1) BIG-IP TMSH Manual net sfc sf(1)
NAME
sf - Service Function (SF)
MODULE
net sfc
SYNTAX
Configure a sf definition within the net sfc using the syntax in the
following sections.
CREATE/MODIFY
create sf [name]
modify sf [name]
options:
app-service [[string] | none]
description [string]
egress-interface [ [string] | none]
ingress-interface [ [string] | none]
ip-address [ [ip address] | none]
nsh-aware [disabled | enabled]
pool-name [[pool_name] | none]
virtual-name [[virtual_name] | none]
edit sf [ [ [name] | [glob] | [regex] ] ... ]
options:
all-properties
non-default-properties
DISPLAY
list sf
list sf [ [ [name] | [glob] | [regex] ] ... ]
show running-config net sfc sf
show running-config net sfc sf [ [ [name] | [glob] | [regex] ] ... ]
options:
all-properties
non-default-properties
one-line
DELETE
delete net sfc sf [all | [name] ]
DESCRIPTION
You can use the net sfc sf to define a service function (SF) to be
referenced by a net sfc chain.
EXAMPLES
create net sfc sf
Creates a sfc sf (see below).
list net sfc sf all-properties
Displays all of the properties of all of the sfc sf.
delete net sfc sf
Deletes a sfc sf (see below).
Example:
net sfc sf sf2-1 {
ip-address any
virtual-name __f5_sfc_app__ }
app-service
Specifies the name of the application service to which the object
belongs. The default value is none. Note: If the strict-updates
option is enabled on the application service that owns the object,
you cannot modify or delete the object. Only the application
service can modify or delete the object.
name Specifies a unique name for the sf. This option is required for
the commands create, delete, and modify.
description
User defined description.
egress-interface
Egress interface.
ingress-interface
Ingress interface.
ip-address
IP address of the SF. Only one of ip-address, pool-name, virtual-
name may be specified.
nsh-aware
Indicate if the SF is capable of network service header (NSH)
packets.
pool-name
Only one of ip-address, pool-name, virtual-name may be specified.
If specified, both ingress and egress interface, vlan name, need
to be specfied and of the same type. If nsh-aware is enabled,
then ingress and egress VXLAN-GPE tunnel names can be the same or
different.
virtual-name
Only one of ip-address, pool-name, virtual-name may be specified.
If specified, then no ingress or egress interface should be
specified. nsh-aware cannot be specified with virtual-name
defined.
SEE ALSO
create, delete, edit, glob, list, modify, regex, show, tmsh
COPYRIGHT
No part of this program may be reproduced or transmitted in any form or
by any means, electronic or mechanical, including photocopying,
recording, or information storage and retrieval systems, for any
purpose other than the purchaser's personal use, without the express
written permission of F5 Networks, Inc.
Fpp/tmsh/man/net_sfc_sf.pod5 Networks and BIG-IP (c) Copyright 2018.
All rights reserved.
BIG-IP 2018-07-20 net sfc sf(1)