- Preface
- New and Changed Information
- Overview
- Configuring Basic Interface Parameters
- Configuring Layer 2 Interfaces
- Configuring Layer 3 Interfaces
- Configuring Bidirectional Forwarding Detection
- Configuring Port Channels
- Configuring vPCs
- Configuring IP Tunnels
- IETF RFCs supported by Cisco NX-OS Interfaces
- Configuration Limits for Cisco NX-OS Interfaces
- About Layer 3 Interfaces
- Licensing Requirements for Layer 3 Interfaces
- Prerequisites for Layer 3 Interfaces
- Guidelines and Limitations
- Default Settings
- Configuring Layer 3 Interfaces
- Verifying the Layer 3 Interfaces Configuration
- Monitoring the Layer 3 Interfaces
- Configuration Examples for Layer 3 Interfaces
- Related Documents
Configuring Layer 3 Interfaces
- About Layer 3 Interfaces
- Licensing Requirements for Layer 3 Interfaces
- Prerequisites for Layer 3 Interfaces
- Guidelines and Limitations
- Default Settings
- Configuring Layer 3 Interfaces
- Verifying the Layer 3 Interfaces Configuration
- Monitoring the Layer 3 Interfaces
- Configuration Examples for Layer 3 Interfaces
- Related Documents
About Layer 3 Interfaces
Layer 3 interfaces forward IPv4 and IPv6 packets to another device using static or dynamic routing protocols. You can use Layer 3 interfaces for IP routing and inter-VLAN routing of Layer 2 traffic.
- Routed Interfaces
- Subinterfaces
- VLAN Interfaces
- Loopback Interfaces
- High Availability
- Virtualization Support
Routed Interfaces
You can configure a port as a Layer 2 interface or a Layer 3 interface. A routed interface is a physical port that can route IP traffic to another device. A routed interface is a Layer 3 interface only and does not support Layer 2 protocols, such as the Spanning Tree Protocol (STP).
All Ethernet ports are routed interfaces by default. You can change this default behavior with the CLI setup script.
You can assign an IP address to the port, enable routing, and assign routing protocol characteristics to this routed interface.
You can also create a Layer 3 port channel from routed interfaces. For more information about port channels, see the “Configuring Port Channels” section.
Routed interfaces and subinterfaces support exponentially decayed rate counters. Cisco NX-OS tracks the following statistics with these averaging counters:
Subinterfaces
You can create virtual subinterfaces on a parent interface configured as a Layer 3 interface. A parent interface can be a physical port.
Subinterfaces divide the parent interface into two or more virtual interfaces on which you can assign unique Layer 3 parameters such as IP addresses and dynamic routing protocols. The IP address for each subinterface should be in a different subnet from any other subinterface on the parent interface.
You create a subinterface with a name that consists of the parent interface name (for example, Ethernet 2/1) followed by a period and then by a number that is unique for that subinterface. For example, you could create a subinterface for Ethernet interface 2/1 named Ethernet 2/1.1 where .1 indicates the subinterface.
Cisco NX-OS enables subinterfaces when the parent interface is enabled. You can shut down a subinterface independent of shutting down the parent interface. If you shut down the parent interface, Cisco NX-OS shuts down all associated subinterfaces as well.
One use of subinterfaces is to provide unique Layer 3 interfaces to each virtual local area network (VLAN) supported by the parent interface. In this scenario, the parent interface connects to a Layer 2 trunking port on another device. You configure a subinterface and associate the subinterface to a VLAN ID using 802.1Q trunking.
The following figure shows a trunking port from a switch that connects to router B on interface E 2/1. This interface contains three subinterfaces that are associated with each of the three VLANs carried by the trunking port.

For more information about VLANs, see the Cisco Nexus 9000 Series NX-OS Layer 2 Switching Configuration Guide.
VLAN Interfaces
A VLAN interface, or switch virtual interface (SVI), is a virtual routed interface that connects a VLAN on the device to the Layer 3 router engine on the same device. Only one VLAN interface can be associated with a VLAN, but you need to configure a VLAN interface for a VLAN only when you want to route between VLANs or to provide IP host connectivity to the device through a virtual routing and forwarding (VRF) instance that is not the management VRF. When you enable VLAN interface creation, Cisco NX-OS creates a VLAN interface for the default VLAN (VLAN 1) to permit remote switch administration.
You must enable the VLAN network interface feature before you can see configure it. The system automatically takes a checkpoint prior to disabling the feature, and you can roll back to this checkpoint. See the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide for information on rollbacks and checkpoints.
![]() Note | You cannot delete the VLAN interface for VLAN 1. |
You can route across VLAN interfaces to provide Layer 3 inter-VLAN routing by configuring a VLAN interface for each VLAN that you want to route traffic to and assigning an IP address on the VLAN interface. For more information about IP addresses and IP routing, see the Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide.
The following figure shows two hosts connected to two VLANs on a device. You can configure VLAN interfaces for each VLAN that allows Host 1 to communicate with Host 2 using IP routing between the VLANs. VLAN 1 communicates at Layer 3 over VLAN interface 1 and VLAN 10 communicates at Layer 3 over VLAN interface 10.

Loopback Interfaces
A loopback interface is a virtual interface with a single endpoint that is always up. Any packet transmitted over a loopback interface is immediately received by this interface. Loopback interfaces emulate a physical interface. You can configure up to 1024 loopback interfaces, numbered 0 to 1023.
You can use loopback interfaces for performance analysis, testing, and local communications. Loopback interfaces can act as a termination address for routing protocol sessions. This loopback configuration allows routing protocol sessions to stay up even if some of the outbound interfaces are down.
High Availability
Layer 3 interfaces support stateful and stateless restarts. After the switchover, Cisco NX-OS applies the runtime configuration after the switchover.
See the Cisco Nexus 9000 Series NX-OS High Availability and Redundancy Guide for complete information about high availability.
Virtualization Support
Layer 3 interfaces support Virtual Routing and Forwarding instances (VRFs). VRFs exist within virtual device contexts (VDCs). By default, Cisco NX-OS places you in the default VDC and default VRF .
You can configure up to 1024 loopback interfaces per VDC.
You can associate the interface with a VRF. For VLAN interfaces, you must configure the VLAN interface in the same VDC as the VLAN.
See the Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide for information about configuring an interface in a VRF.
![]() Note | You must assign an interface to a VRF before you configure the IP address for that interface. |
Licensing Requirements for Layer 3 Interfaces
The following table shows the licensing requirements for this feature:
Product |
License Requirement |
---|---|
Cisco NX-OS |
Layer 3 interfaces require no license. Any feature not included in a license package is bundled with the Cisco NX-OS image and is provided at no extra charge to you. |
Prerequisites for Layer 3 Interfaces
Layer 3 interfaces have the following prerequisites:
Guidelines and Limitations
Layer 3 interfaces have the following configuration guidelines and limitations:
-
If you change a Layer 3 interface to a Layer 2 interface, Cisco NX-OS shuts down the interface, reenables the interface, and removes all configuration specific to Layer 3.
-
If you change a Layer 2 interface to a Layer 3 interface, Cisco NX-OS shuts down the interface, reenables the interface, and deletes all configuration specific to Layer 2.
![]() Note | If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use. |
Default Settings
The following table lists the default settings for Layer 3 interface parameters.
Parameters |
Default |
---|---|
Admin state |
Shut |
Configuring Layer 3 Interfaces
- Configuring a Routed Interface
- Configuring a Subinterface on a Routed Interface
- Configuring a Subinterface on a Port-Channel Interface
- Configuring the Bandwidth on an Interface
- Configuring a VLAN Interface
- Configuring a Loopback Interface
- Assigning an Interface to a VRF
Configuring a Routed Interface
You can configure any Ethernet port as a routed interface.
1.
configure terminal
2.
interface ethernet
slot/port
3.
no switchport
4.
[ip address
ip-address/length |
ipv6
address
ipv6-address/length]
5.
show interfaces
6.
no shutdown
7.
copy running-config startup-config
DETAILED STEPS
Command |
Purpose |
---|---|
medium {broadcast | p2p} Example: switch(config-if)# medium p2p medium p2p |
Configures the interface medium as either point to point or broadcast. |
![]() Note | The default setting is broadcast, and this setting does not appear in any of the show commands. However, if you do change the setting to p2p, you will see this setting when you enter the show running config command. |
Command |
Purpose |
---|---|
switchport Example: switch(config-if)# switchportswitchport |
Configures the interface as a Layer 2 interface and deletes any configuration specific to Layer 3 on this interface. |
-
This example shows how to configure a routed interface:
switch# configure terminal switch(config)# interface ethernet 2/1 switch(config-if)# no switchport switch(config-if)# ip address 192.0.2.1/8 switch(config-if)# copy running-config startup-config
The default setting for interfaces is routed. If you want to configure an interface for Layer 2, enter the switchport command. Then, if you change a Layer 2 interface to a routed interface, enter the no switchport command.
Configuring a Subinterface on a Routed Interface
You can configure one or more subinterfaces on a routed interface made from routed interfaces.
Configure the parent interface as a routed interface.
See the “Configuring a Routed Interface” section.
1.
configure terminal
2.
interface ethernet
slot/port.number
3.
[ip address
ip-address/length |
ipv6
address
ipv6-address/length]
4.
encapsulation dot1Q
vlan-id
5.
show interfaces
6.
copy running-config startup-config
DETAILED STEPS
-
This example shows how to create a subinterface:
switch# configure terminal switch(config)# interface ethernet 2/1.1 switch(config-if)# ip address 192.0.2.1/8 switch(config-if)# encapsulation dot1Q 33 switch(config-if)# copy running-config startup-config
-
The output of the show interface eth command is enhanced for the subinterfaces as shown in the following :
switch# show interface ethernet 1/2.1 Ethernet1/2.1 is down (Parent Interface Admin down) admin state is down, Dedicated Interface, [parent interface is Ethernet1/2] Hardware: 40000 Ethernet, address: 0023.ac67.9bc1 (bia 4055.3926.61d4) Internet Address is 10.10.10.1/24 MTU 1500 bytes, BW 40000000 Kbit, DLY 10 usec reliability 255/255, txload 1/255, rxload 1/255 Auto-mdix is turned off EtherType is 0x8100 L3 in Switched: ucast: 0 pkts, 0 bytes - mcast: 0 pkts, 0 bytes L3 out Switched: ucast: 0 pkts, 0 bytes - mcast: 0 pkts, 0 bytes
Configuring a Subinterface on a Port-Channel Interface
You can configure one or more subinterfaces on a port-channel interface.
![]() Note | Subinterfaces on a port-channel interface do not support multicast routing, router ACLs, QoS, policy-based routing (PBR), SPAN, or ERSPAN. |
Configure the parent interface as a port-channel interface.
See the “Configuring Port Channels” chapter.
1.
configure terminal
2.
interface port-channel
channel-id.number
3.
[ip address
ip-address/length |
ipv6
address
ipv6-address/length]
4.
encapsulation dot1Q
vlan-id
5.
show interfaces
6.
copy running-config startup-config
DETAILED STEPS
This example shows how to create a subinterface:
switch# configure terminal switch(config)# interface port-channel 115.3 switch(config-subif)# ip address 141.143.101.2/24 switch(config-subif)# encapsulation dot1q 3 switch(config-subif)# copy running-config startup-config
Configuring the Bandwidth on an Interface
You can configure the bandwidth for a routed interface, port channel, or subinterface. Higher layer protocols use a bandwidth parameter to calculate path costs. You can configure the bandwidth on a subinterface with one of the following methods:
-
Explicit—Sets the bandwidth value for the subinterface directly
-
Inherit—Sets the bandwidth that all subinterfaces inherit from the parent interface as either a specific value or as the bandwidth of the parent interface.
If you do not set the subinterface bandwidth or configure it to inherit the bandwidth from the parent interface, Cisco NX-OS determines the subinterface bandwidth as follows:
-
If the parent interface is up, the bandwidth of the subinterface is the same as the operational speed of the parent interface. For ports, the subinterface bandwidth is the configured or negotiated link speed. For port channels, the subinterface bandwidth is the aggregate of the link speeds of individual members of the port channel.
-
If the parent interface is down, the bandwidth of the subinterface depends on the type of parent interface:
To configure the bandwidth of an interface, use the following command in interface mode:
Command |
Purpose |
---|---|
bandwidth Example: switch(config-if)# 100000bandwidth 100000 |
Configures the bandwidth parameter for a routed interface, port channel, or subinterface. |
To configure subinterfaces to inherit the bandwidth from the parent interface, use the following command in interface mode:
Command |
Purpose |
---|---|
bandwidth inherit [value]] Example: switch(config-if)# inherit bandwidth inherit 10000000 |
Configures all subinterfaces of this interface to inherit the bandwidth value configured. If you do not configure the value, the subinterfaces inherit the bandwidth of the parent interface. The range is from 1 to 10000000, in kilobytes. |
Configuring a VLAN Interface
You can create VLAN interfaces to provide inter-VLAN routing.
1.
configure
terminal
2.
feature
interface-vlan
3.
interface vlan
number
4.
[ip address
ip-address/length |
ipv6
address
ipv6-address/length]
5.
show interface vlan
number
6.
show interface status error
policy [detail]
7.
no shutdown
8.
copy running-config startup-config
DETAILED STEPS
This example shows how to create a VLAN interface:
switch# configure terminal switch(config)# feature interface-vlan switch(config)# interface vlan 10 switch(config-if)# ip address 192.0.2.1/8 switch(config-if)# copy running-config startup-config
Configuring a Loopback Interface
You can configure a loopback interface to create a virtual interface that is always up.
Ensure that the IP address of the loopback interface is unique across all routers on the network.
1.
configure terminal
2.
interface loopback instance
3.
[ip address ip-address/length | ipv6 address ipv6-address/length]
4.
show interface loopback instance
5.
copy running-config startup-config
DETAILED STEPS
This example shows how to create a loopback interface:
switch# configure terminal switch(config)# interface loopback 0 switch(config-if)# ip address 192.0.2.1/8 switch(config-if)# copy running-config startup-config
Assigning an Interface to a VRF
You can add a Layer 3 interface to a VRF.
1.
configure
terminal
2.
interface
interface-type
number
3.
vrf member
vrf-name
4.
ip address
ip-prefix/length
5.
show vrf [vrf-name]
interface
interface-type
number
6.
copy running-config startup-config
DETAILED STEPS
This example shows how to add a Layer 3 interface to the VRF:
switch# configure terminal switch(config)# interface loopback 0 switch(config-if)# vrf member RemoteOfficeVRF switch(config-if)# ip address 209.0.2.1/16 switch(config-if)# copy running-config startup-config
Verifying the Layer 3 Interfaces Configuration
To display the Layer 3 configuration, perform one of the following tasks:
Command |
Purpose |
---|---|
show interface ethernet slot/port |
Displays the Layer 3 interface configuration, status, and counters (including the 5-minute exponentially decayed moving average of inbound and outbound packet and byte rates). |
show interface ethernet slot/port brief |
Displays the Layer 3 interface operational status. |
show interface ethernet slot/port capabilities |
Displays the Layer 3 interface capabilities, including port type, speed, and duplex. |
show interface ethernet slot/port description |
Displays the Layer 3 interface description. |
show interface ethernet slot/port status |
Displays the Layer 3 interface administrative status, port mode, speed, and duplex. |
show interface ethernet slot/port.number |
Displays the subinterface configuration, status, and counters (including the f-minute exponentially decayed moving average of inbound and outbound packet and byte rates). |
show interface port-channel channel-id.number |
Displays the port-channel subinterface configuration, status, and counters (including the 5-minute exponentially decayed moving average of inbound and outbound packet and byte rates). |
show interface loopback number |
Displays the loopback interface configuration, status, and counters. |
show interface loopback number brief |
Displays the loopback interface operational status. |
show interface loopback number description |
Displays the loopback interface description. |
show interface loopback number status |
Displays the loopback interface administrative status and protocol status. |
show interface vlan number |
Displays the VLAN interface configuration, status, and counters. |
show interface vlan number brief |
Displays the VLAN interface operational status. |
show interface vlan number description |
Displays the VLAN interface description. |
show interface vlan number status |
Displays the VLAN interface administrative status and protocol status. |
show interface status error policy [detail] |
Displays errors about interfaces and VLANs that are inconsistent with hardware policies. The detail command displays the details of the interfaces that receive an error. |
Monitoring the Layer 3 Interfaces
Use the following commands to display Layer 3 statistics:
Command |
Purpose |
---|---|
load- interval {interval seconds {1 | 2 | 3}} |
Cisco Nexus 9000 Series devices set three different sampling intervals to bit-rate and packet-rate statistics. The range for VLAN network interface is 60 to 300 seconds, and the range for Layer interfaces is 30 to 300 seconds. |
show interface ethernet slot/port counters |
Displays the Layer 3 interface statistics (unicast, multicast, and broadcast). |
show interface ethernet slot/port counters brief |
Displays the Layer 3 interface input and output counters. |
show interface ethernet errors slot/port detailed [all] |
Displays the Layer 3 interface statistics. You can optionally include all 32-bit and 64-bit packet and byte counters (including errors). |
show interface ethernet errors slot/port counters errors |
Displays the Layer 3 interface input and output errors. |
show interface ethernet errors slot/port counters snmp |
Displays the Layer 3 interface counters reported by SNMP MIBs. |
show interface ethernet slot/port.number counters |
Displays the subinterface statistics (unicast, multicast, and broadcast). |
show interface port-channel channel-id.number counters |
Displays the port-channel subinterface statistics (unicast, multicast, and broadcast). |
show interface loopback number counters |
Displays the loopback interface input and output counters (unicast, multicast, and broadcast). |
show interface loopback number detailed [all] |
Displays the loopback interface statistics. You can optionally include all 32-bit and 64-bit packet and byte counters (including errors). |
show interface loopback number counters errors |
Displays the loopback interface input and output errors. |
show interface vlan number counters |
Displays the VLAN interface input and output counters (unicast, multicast, and broadcast). |
show interface vlan number counters detailed [all] |
Displays the VLAN interface statistics. You can optionally include all Layer 3 packet and byte counters (unicast and multicast). |
show interface vlan number counters snmp |
Displays the VLAN interface counters reported by SNMP MIBs. |
Configuration Examples for Layer 3 Interfaces
This example shows how to configure Ethernet subinterfaces:
interface ethernet 2/1.10 description Layer 3 ip address 192.0.2.1/8
This example shows how to configure a loopback interface:
interface loopback 3 ip address 192.0.2.2/32
Related Documents
Related Documents |
Document Title |
---|---|
IP |
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide |
VLANs |
Cisco Nexus 9000 Series NX-OS Layer 2 Switching Configuration Guide |