Table Of Contents
Configuring Virtual Ethernet Interfaces
Information About vEthernet Interfaces
Guidelines and Limitations
Default Settings
Configuring vEthernet Interfaces
Configuring Global vEthernet Properties
Configuring a vEthernet Access Interface
Configuring a Private VLAN on a vEthernet Interface
Enabling or Disabling a vEthernet Interface
Verifying the vEthernet Interface Configuration
Monitoring the vEthernet Interface Configuration
Configuration Examples for vEthernet Interfaces
Additional References
Related Documents
Standards
Feature History for vEthernet Interfaces
Configuring Virtual Ethernet Interfaces
This chapter describes how to configure virtual Ethernet (vEthernet or vEth) interfaces.
This chapter includes the following sections:
•
Information About vEthernet Interfaces
•Guidelines and Limitations
•Default Settings
•Configuring vEthernet Interfaces
•Verifying the vEthernet Interface Configuration
•Monitoring the vEthernet Interface Configuration
•Configuration Examples for vEthernet Interfaces
•Additional References
•Feature History for vEthernet Interfaces
Information About vEthernet Interfaces
Virtual Ethernet (vEthernet or vEth) interfaces are logical interfaces. Each vEthernet interface corresponds to a switch interface that is connected to a virtual port. The interface types are as follows:
•VM (interfaces connected to VM NICs)
•Service console
•vmkernel
vEthernet interfaces are created on the Cisco Nexus 1000V to represent virtual ports in use on the distributed virtual switch.
vEthernet interfaces are mapped to connected ports by MAC address as well as DVPort number. When a server administrator changes the port profile assignment on a vNIC or hypervisor port, the same vEthernet interface is reused. This is a change in Release 4.2(1)SV1(4). In previous releases, the VSM assigned a new vEthernet interface.
When bringing up a vEthernet interface where a change in the port profile assignment is detected, the VSM automatically purges any manual configuration present on the interface. You can use the following command to prevent purging of the manual configuration:
no svs veth auto-config-purge
Guidelines and Limitations
vEthernet interface configuration has the following guideline and limitation:
•MTU cannot be configured on a vEthernet interface.
Default Settings
The following table lists the default settings for vEthernet interface configuration.
Parameters
|
Default
|
Switchport mode
|
Access
|
Allowed VLANs
|
1 to 4094
|
Access VLAN ID
|
VLAN1
|
Native VLAN ID
|
VLAN1
|
Native VLAN ID tagging
|
Disabled
|
Administrative state
|
Shut
|
Automatic deletion of vEthernet interfaces
|
Enabled
|
Automatic purge of manual configuration on vEthernet interfaces
|
Enabled
|
Automatic creation of vEthernet interfaces
|
Enabled
|
Configuring vEthernet Interfaces
This section includes the following topics:
•Configuring Global vEthernet Properties
•Configuring a vEthernet Access Interface
•Configuring a Private VLAN on a vEthernet Interface
•Enabling or Disabling a vEthernet Interface
Configuring Global vEthernet Properties
You can use this procedure to enable or disable the following automatic controls for vEthernet interfaces:
•Deleting unused vEthernet interfaces
•Purging of manual vEthernet configurations
•Creating vEthernet interfaces
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
SUMMARY STEPS
1. config t
2. (Optional) [no] svs veth auto-delete
3. (Optional) [no] svs veth auto-config-purge
4. (Optional) [no] svs veth auto-setup
5. show running-config all | grep "svs-veth"
6. copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
n1000v# config t
n1000v(config)#
|
Enters the global configuration mode.
|
Step 2
|
[no] svs veth auto-delete
Example:
n1000v(config)# svs veth auto-delete
n1000v(config)#
|
(Optional) Enables the VSM to automatically delete DVPorts no longer used by a vNIC or hypervisor port.
The default setting = enabled
The no form of this command prevents the VSM from deleting unused DVPorts.
|
Step 3
|
[no] svs veth auto-config-purge
Example:
n1000v(config)# svs veth
auto-config-purge
n1000v(config)#
|
(Optional) Enables the VSM to remove all manual configuration on a vEthernet interface when the system administrator changes a port profile on the interface.
The default setting = enabled
The no form of this command prevents the manual configuration from being deleted in this situation.
Note Port profiles with ephemeral bindings are purged regardless of this setting.
|
Step 4
|
[no] svs veth auto-setup
Example:
n1000v(config)# svs veth auto-setup
n1000v(config)#
|
(Optional) Enables the VSM to automatically create a vEthernet interface when a new port is activated on a host.
The no form of this command disables the automatic creation of vEthernet interfaces in this situation.
Note You can use no form of the command to temporary block automatic creation of vEthernet interfaces.
|
Step 5
|
show running-config all | grep
"svs-veth"
Example:
n1000v(config)# show running-config all
| grep "svs veth"
svs veth auto-setup
svs veth auto-delete
svs veth auto-config-purge
n1000v(config)#
Example:
n1000v(config)# show running-config all
| grep "svs veth"
n1000v(config)#
|
(Optional) Displays the default global vEthernet settings that are in effect on the VSM for verification. If a setting is disabled, it does not display in the show command output.
|
Step 6
|
copy running-config startup-config
Example:
n1000v(config)# copy running-config
startup-config
|
(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.
|
Configuring a vEthernet Access Interface
You can use this procedure to configure a vEthernet interface for use as an access interface.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•You are logged into the CLI in EXEC mode.
•If you do not add a description to the vEthernet interface, then one of the following descriptions is added at attach time. If you add a description and then remove it using the no description command, then one of the following descriptions is added to the interface:
–For a VM—VM-Name, Network Adapter number
–For a VMK—VMware VMkernel, vmk number
–For a VSWIF—VMware Service Console, vswif number
SUMMARY STEPS
1. config t
2. interface vethernet interface-number
3. (Optional) description string
4. switchport access vlan vlan-id
5. switchport mode access
6. show interface interface-number
7. copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
n1000v# config t
n1000v(config)#
|
Enters the global configuration mode.
|
Step 2
|
interface vethernet interface-number
Example:
n1000v(config)# interface vethernet 100
n1000v(config-if)#
|
Enters the interface configuration mode for the specified vEthernet interface (from 1 to 1048575).
|
Step 3
|
description string
Example:
n1000v(config-if)# description
accessvlan
|
(Optional) Adds a description of up to 80 alphanumeric characters to the interface in the running configuration.
Note If you do not add a description, the default description is added.
Note You do not need to use quotations around descriptions that include spaces.
|
Step 4
|
switchport access vlan vlanid
Example:
n1000v(config-if)# switchport access
vlan 5
|
Configures the vEthernet interface as an access interface and specifies the VLAN ID (1 to 4094) in the running configuration.
|
Step 5
|
switchport mode access
Example:
n1000v(config-if)# switchport mode
access
n1000v(config-if)#
|
Configures the vEthernet interface for use as an access interface in the running configuration.
|
Step 6
|
show interface vethernet
interface-number
Example:
n1000v(config-if)# show interface
vethernet1
|
(Optional) Displays the specified interface for verification.
|
Step 7
|
copy running-config startup-config
Example:
n1000v(config)# copy running-config
startup-config
|
(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.
|
Configuring a Private VLAN on a vEthernet Interface
You can use this procedure to configure a private VLAN (PVLAN) on a vEthernet interface.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•You are logged into the CLI in EXEC mode.
SUMMARY STEPS
1. config t
2. interface vethernet interface-number
3. (Optional) description string
4. switchport access vlan vlan-id
5. switchport mode private-vlan host
6. switchport private-vlan host-association primary-vlan-id
7. show interface
8. copy running-config startup-config
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
n1000v# config t
n1000v(config)#
|
Enters the global configuration mode.
|
Step 2
|
interface vethernet interface-number
Example:
n1000v(config)# interface vethernet 1
n1000v(config-if)#
|
Enters the interface configuration mode for the specified vEthernet interface (from 1 to 1048575).
|
Step 3
|
description string
Example:
n1000v(config-if)# description
isp_pvlan1
|
(Optional) Adds a description of up to 80 alphanumeric characters to the interface in the running configuration.
Note If you do not add a description, the default description is added.
Note You do not need to use quotations around descriptions that include spaces.
|
Step 4
|
switchport access vlan vlan-id
Example:
n1000v(config-if)# switchport access
vlan 5
|
Configures the vEthernet interface as an access interface and specifies the VLAN ID (from 1 to 4094) in the running configuration.
|
Step 5
|
switchport mode private-vlan host
Example:
n1000v(config-if)# switchport mode
private-vlan host
|
Configures the vEthernet interface for a PVLAN host in the running configuration.
|
Step 6
|
switchport private-vlan host-association
primary-vlanid
Example:
n1000v(config-if)# switchport
private-vlan host-association 5
|
Configures the vEthernet interface for a host association with a specific primary VLAN ID (from 1 to 4094) in the running configuration.
|
Step 7
|
show interface
Example:
n1000v# show interface
|
(Optional) Displays the interface status and information.
|
Step 8
|
copy running-config startup-config
Example:
n1000v(config)# copy running-config
startup-config
|
(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.
|
EXAMPLES
The following example shows how to configure a vEthernet interface to use in a private vlan:
n1000v(config)# interface vethernet 1
n1000v(config-if)# switchport access vlan 5
n1000v(config-if)# switchport mode private-vlan host
n1000v(config-if)# switchport private-vlan host-association 5
n1000v(config-if)# show interface vethernet 1
Vethernet1 is up
Port description is gentoo, Network Adapter 1
Hardware is Virtual, address is 0050.5687.3bac
Owner is VM "gentoo", adapter is Network Adapter 1
5 minute input rate 1 bytes/second, 0 packets/second
5 minute output rate 94 bytes/second, 1 packets/second
655 Input Packets 594 Unicast Packets
0 Multicast Packets 61 Broadcast Packets
98875 Output Packets 1759 Unicast Packets
80410 Multicast Packets 16706 Broadcast Packets 0 Flood Packets
0 Input Packet Drops 0 Output Packet Drops
Enabling or Disabling a vEthernet Interface
You can use this procedure to enable or disable a vEthernet interface.
SUMMARY STEPS
1. config t
2. interface vethernet interface-number
3. [no] shutdown
4. show interface
5. copy running-config startup-config
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•You are logged into the CLI in EXEC mode.
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
n1000v# config t
n1000v(config)#
|
Enters the global configuration mode.
|
Step 2
|
interface vethernet interface-number
Example:
n1000v(config)# interface vethernet 100
n1000v(config-if)#
|
Enters the interface configuration mode for the specified vEthernet interface (from 1 to 1048575).
|
Step 3
|
[no] shutdown
Example:
n1000v(config-if)# no shutdown
n1000v(config-if)#
|
Enables or disables the vEthernet interface in the running configuration:
•shutdown—Disables the vEthernet interface.
•no shutdown—Enables the vEthernet interface.
|
Step 4
|
show interface
Example:
n1000v# show interface
|
(Optional) Displays the interface status and information.
|
Step 5
|
copy running-config startup-config
Example:
n1000v(config)# copy running-config
startup-config
|
(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.
|
EXAMPLES
The following example shows how to enable a vEthernet interface:
n1000v(config)# interface vethernet 100
n1000v(config)# no shutdown
n1000v(config-if)# show interface veth100 status
--------------------------------------------------------------------------------
Port Name Status Vlan Duplex Speed Type
--------------------------------------------------------------------------------
Veth100 -- up 1 auto auto --
Verifying the vEthernet Interface Configuration
You can use the following commands to display the vEthernet interface configuration:
Command
|
Purpose
|
show interface vethernet interface-number [brief | counters [detailed [all] | errors] | description | mac-address | status [ down | err-disabled | inactive | module num | up ] | switchport]
|
Displays the vEthernet interface configuration.
|
show interface [vethernet interface-number]
|
Displays the complete interface configuration.
|
show interface [vethernet interface-number] brief
|
Displays abbreviated interface configuration.
|
show interface [vethernet interface-number] description
|
Displays the interface description.
|
show interface [vethernet interface-number] mac-address
|
Displays the interface MAC address.
Note For vEth interfaces this shows the MAC address of the connected device.
|
show interface [vethernet interface-number] status [ down | err-disabled | inactive | module num | up ]
|
Displays interface line status.
|
show interface [vethernet interface-number] switchport
|
Displays interface switchport information.
|
show interface virtual [vm [vm_name] | vmk | vswif] [module mod_no]
|
Displays virtual interfaces only.
|
show interface virtual port-mapping [ vm [ name] | vmk | vswif | description] [ module_num]
|
Displays mappings between veth and VMware DVPort.
|
The following example shows how to display vEthernet 1:
n1000v# show interface veth1
Port description is gentoo1, Network Adapter 1
Hardware is Virtual, address is 0050.56bd.42f6
Owner is VM "gentoo1", adapter is Network Adapter 1
491242 Input Packets 491180 Unicast Packets
7 Multicast Packets 55 Broadcast Packets
504958 Output Packets 491181 Unicast Packets
1 Multicast Packets 13776 Broadcast Packets 941 Flood Packets
11 Input Packet Drops 0 Output Packet Drops
The following example shows how to display information for all vEthernet interfaces:
n1000v# show interface virtual
--------------------------------------------------------------------------------
Port Adapter Owner Mod Host
--------------------------------------------------------------------------------
Veth1 Net Adapter 1 austen-gentoo1 33 austen-strider.austen.
Veth2 Net Adapter 2 austen-gentoo1 33 austen-strider.austen.
The following example shows how to display the descriptions for all vEthernet interfaces:
n1000v# show interface virtual description
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Veth1 gentoo1, Network Adapter 1
Veth2 gentoo1, Network Adapter 2
Veth3 VMware VMkernel, vmk1
Veth4 VMware Service Console, vswif1
The following example shows how to display the virtual port mapping for all vEthernet interfaces:
n1000v# show interface virtual port-mapping
-------------------------------------------------------------------------------
Port Hypervisor Port Binding Type Status Reason
-------------------------------------------------------------------------------
Veth1 DVPort5747 static up none
Veth2 DVPort3361 static up none
The following example shows how to display the running configuration information for all vEthernet interfaces:
n1000v# show running-config interface veth1
inherit port-profile vlan48
description gentoo1, Network Adapter 1
vmware dvport 2968 dvswitch uuid "d4 02 20 50 16 4b 36 97-46 09 dc d8 5b c6 1e c1"
vmware vm mac 0050.56A0.0000
Monitoring the vEthernet Interface Configuration
You can use the following commands to monitor the vEthernet interface configuration:
Command
|
Purpose
|
show interface [vethernet interface-number] counters
|
Displays the interface incoming and outgoing counters.
|
show interface [vethernet interface-number] counters detailed [all]
|
Displays detailed information for all counters.
Note If 'all' is not specified then only non-zero counters are shown.
|
show interface [vethernet interface-number] counters errors
|
Displays the interface error counters.
|
The following example shows how to display the counters for all vEthernet interfaces:
n1000v# show interface counters
--------------------------------------------------------------------------------
Port InOctets InUcastPkts InMcastPkts InBcastPkts
--------------------------------------------------------------------------------
Eth2/2 41423421 112708 125997 180167
Eth5/2 39686276 119152 93284 180100
Eth5/6 4216279 9530 31268 40
--------------------------------------------------------------------------------
Port OutOctets OutUcastPkts OutMcastPkts OutBcastPkts
--------------------------------------------------------------------------------
Eth2/2 23964739 116150 516 52768
Eth5/2 26419473 111598 571 52420
Eth5/6 1042930 9548 536 14
Configuration Examples for vEthernet Interfaces
The following example shows how to configure a vEthernet access interface and assign the access VLAN for that interface:
n1000v# configure terminal
n1000v(config)# interface vethernet 100
n1000v(config-if)# switchport
n1000v(config-if)# switchport mode access
n1000v(config-if)# switchport access vlan 5
The following example shows how to configure a Layer 2 trunk interface, assign the native VLAN and the allowed VLANs, and configure the device to tag the native VLAN traffic on the trunk interface:
n1000v# configure terminal
n1000v(config)# interface vethernet 1
n1000v(config-if)# switchport
n1000v(config-if)# switchport mode trunk
n1000v(config-if)# switchport trunk native vlan 10
n1000v(config-if)# switchport trunk allowed vlan 5, 10
Additional References
For additional information related to implementing access and trunk port modes, see the following sections:
•Related Documents
•Standards
Related Documents
Related Topic
|
Document Title
|
Complete command syntax, command modes, command history, defaults, usage guidelines, and examples for all Cisco Nexus 1000V commands.
|
Cisco Nexus 1000V Command Reference, Release 4.2(1)SV1(5.1)
|
Port Profiles
|
Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(5.1)
|
VLANs and private VLANs
|
Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.2(1)SV1(5.1)
|
System management
|
Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(5.1)
|
Release Notes
|
Cisco Nexus 1000V Release Notes, Release 4.2(1)SV1(5.1)
|
Standards
Standards
|
Title
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
|
—
|
Feature History for vEthernet Interfaces
This section provides the feature history for vEthernet interfaces.
Feature Name
|
Releases
|
Feature Information
|
Global vEthernet interface controls
|
4.2(1)SV1(4)
|
You can enable or disable the following automatic vEthernet interface controls:
•Deleting unused vEthernet interfaces
•Purging of manual vEthernet configurations
•Creating vEthernet interfaces
|
vEthernet interface parameters
|
4.0(4)SV1(1)
|
This feature was introduced.
|
Feedback