5 Create Interfaces Commands
6 ===========================
7 This section contains those interface commands that are associated to creating an interface:
9 * `Create Host-Interface`_
10 * `Create Interface Memif`_
11 * `Create Loopback Interface`_
12 * `Create Sub-Interfaces`_
14 .. note:: For a complete list of CLI Debug commands refer to the Debug CLI section of the `Source Code Documents <https://docs.fd.io/vpp/18.07/clicmd.html>`_ .
17 ++++++++++++++++++++++
21 create host-interface name <*ifname*> [*hw-addr <*mac-addr*>]
26 Create a host interface that will attach to a linux AF_PACKET interface, one side of a veth pair.
27 The veth pair must already exist. Once created, a new host interface will exist in VPP with the name
28 'host-<*ifname*>', where '<*ifname*>' is the name of the specified veth pair.
29 Use the `show interface` command to display host interface details.
31 This command has the following optional parameters:
33 hw-addr <*mac-addr*> - Optional ethernet address, can be in either X:X:X:X:X:X unix or X.X.X cisco format
38 Example of how to create a host interface tied to one side of an existing linux veth pair named vpp1:
40 .. code-block:: console
42 vpp# create host-interface name vpp1
46 Once the host interface is created, enable the interface using:
48 .. code-block:: console
50 vpp# set interface state host-vpp1 up
52 Declaration and Implementation
53 -------------------------------
55 **Declaration:** af_packet_create_command (src/vnet/devices/af_packet/cli.c line 133)
57 **Implementation:** af_packet_create_command_fn
59 Create Interface Memif
60 +++++++++++++++++++++++
65 create interface memif [id <*id*>] [socket-id <*socket-id*>] [ring-size <*size*>] [buffer-size <*size*>] [hw-addr <*mac-address*>] <master|slave> [rx-queues <*number*>] [tx-queues <*number*>] [mode ip] [secret <*string*>]
67 Declaration and Implementation
68 -------------------------------
70 **Declaration:** memif_create_command (src/plugins/memif/cli.c line 258)
72 **Implementation:** memif_create_command_fn
75 Create Loopback Interface
76 ++++++++++++++++++++++++++
81 create loopback interface [mac <*mac-addr*>] [instance <*instance*>]
86 Create a loopback interface. Optionally, a MAC Address can be provided. If not provided, de:ad:00:00:00:<*loopId*> will be used.
90 The following two command syntaxes are equivalent:
92 .. code-block:: console
94 vpp# loopback create-interface [mac <*mac-addr*>] [instance <*instance*>]
96 vpp# create loopback interface [mac <*mac-addr*>] [instance <*instance*>]
98 Example of how to create a loopback interface:
100 .. code-block:: console
102 vpp# create loopback interface
104 Declaration and Implementation
105 -------------------------------
107 **Declaration:** create_loopback_interface_command (src/vnet/ethernet/interface.c line 879)
109 **Implementation:** create_simulated_ethernet_interfaces
112 Create Sub-Interfaces
113 ++++++++++++++++++++++
115 This command is used to add VLAN IDs to interfaces, also known as
116 subinterfaces. The primary input to this command is the *interface*
117 and *subId* (subinterface Id) parameters. If no additional VLAN ID is
118 provide, the VLAN ID is assumed to be the *subId*. The VLAN ID and
119 *subId* can be different, but this is not recommended.
121 This command has several variations:
123 - **create sub-interfaces** <*interface*> <*subId*> - Create a subinterface
124 to process packets with a given 802.1q VLAN ID (same value as the
126 - **create sub-interfaces** <*interface*> <*subId*> default - Adding the
127 *default* parameter indicates that packets with VLAN IDs that do
128 not match any other subinterfaces should be sent to this
130 - **create sub-interfaces** <*interface*> <*subId*> untagged - Adding the
131 *untagged* parameter indicates that packets no VLAN IDs should be
132 sent to this subinterface.
133 - **create sub-interfaces** <*interface*> <*subId*>-<*subId*> - Create a
134 range of subinterfaces to handle a range of VLAN IDs.
135 - **create sub-interfaces** <*interface*> <*subId*> dot1q|dot1ad <*vlanId*>|any
136 [exact-match] - Use this command to explicitly specify the outer VLAN ID,
137 or to make the VLAN ID different from the *subId*.
138 - **create sub-interfaces** <*interface*> <*subId*> dot1q|dot1ad <*vlanId*>|any
139 inner-dot1q <*vlanId*>|any [exact-match] - Use this command to
140 specify the outer VLAN ID and the inner VLAN ID.
142 When *dot1q* or *dot1ad* is explicitly entered, subinterfaces can be
143 configured as either *exact-match* or *non-exact match*. *Non-exact match* is
144 the CLI default. If *exact-match* is specified, packets must have the
145 same number of VLAN tags as the configuration. For *non-exact-match*,
146 packets must at least that number of tags. L3 (routed) interfaces must
147 be configured as exact-match. L2 interfaces are typically configured as
148 non-exact-match. If *dot1q* or *dot1ad* is NOT entered, then the
149 default behavior is *exact-match*.
151 Use the **show interface** command to display all subinterfaces.
156 .. code-block:: shell
158 create sub-interfaces <interface> {<subId> [default|untagged]} | {<subId>-<subId>} | {<subId> dot1q|dot1ad <vlanId>|any [inner-dot1q <vlanId>|any] [exact-match]}
163 Example of how to create a VLAN subinterface 11 to process packets on 802.1q VLAN ID 11:
165 .. code-block:: console
167 vpp# create sub-interfaces GigabitEthernet2/0/0 11
169 The previous example is shorthand and is equivalent to:
171 .. code-block:: console
173 vpp# create sub-interfaces GigabitEthernet2/0/0 11 dot1q 11 exact-match
175 Example of how to create a subinterface number that is different from the VLAN ID:
177 .. code-block:: console
179 vpp# create sub-interfaces GigabitEthernet2/0/0 11 dot1q 100
181 Examples of how to create q-in-q and q-in-any subinterfaces:
183 .. code-block:: console
185 vpp# create sub-interfaces GigabitEthernet2/0/0 11 dot1q 100 inner-dot1q 200
186 vpp# create sub-interfaces GigabitEthernet2/0/0 12 dot1q 100 inner-dot1q any
188 Examples of how to create dot1ad interfaces:
190 .. code-block:: console
192 vpp# create sub-interfaces GigabitEthernet2/0/0 11 dot1ad 11
193 vpp# create sub-interfaces GigabitEthernet2/0/0 12 dot1ad 100 inner-dot1q 200
195 Examples of *exact-match* versus non-exact match. A packet with outer VLAN 100 and inner VLAN 200 would match this interface, because the default is non-exact match:
197 .. code-block:: console
199 vpp# create sub-interfaces GigabitEthernet2/0/0 5 dot1q 100
201 However, the same packet would NOT match this interface because *exact-match* is specified and only one VLAN is configured, but packet contains two VLANs:
203 .. code-block:: console
205 vpp# create sub-interfaces GigabitEthernet2/0/0 5 dot1q 100 exact-match
207 Example of how to created a subinterface to process untagged packets:
209 .. code-block:: console
211 vpp# create sub-interfaces GigabitEthernet2/0/0 5 untagged
213 Example of how to created a subinterface to process any packet with a VLAN ID that does not match any other subinterface:
215 .. code-block:: console
217 vpp# create sub-interfaces GigabitEthernet2/0/0 7 default
219 When subinterfaces are created, they are in the down state. Example of how to enable a newly created subinterface:
221 .. code-block:: console
223 vpp# set interface GigabitEthernet2/0/0.7 up