Restrictions for 1G and 10G Modes
-
Carrier delays of less than 2 seconds are not supported on both 1G and 10G modes.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides information about configuring the Gigabit Ethernet interface on the Cisco ASR 920 Series Router.
For more information about the commands used in this chapter, see the Cisco IOS XE 3S Command References.
Effective Cisco IOS-XE Release 3.16S, the Cisco ASR-920-12SZ-IM Aggregation Services Router was added to the Cisco ASR 920 Series Routers family.
Note |
On the Cisco ASR-920-12SZ-IM Aggregation Services Router, ports from 12 through 15 can operate at either 1G or 10G, and operates in a mutually exclusive way. You cannot insert both 1G and 10G together. If you insert IG IMs (A900-IMA8T1Z, A900-IMA8S1Z, A900-IMA8T, A900-IMA8S), the dual rate port supports only 10G. |
Carrier delays of less than 2 seconds are not supported on both 1G and 10G modes.
This section lists the required configuration steps to configure Gigabit and Ten Gigabit Ethernet interfaces. Follow these steps to configure your interface:
Note |
Carrier delays of less than 2 seconds are not supported on both 1G and 10G modes. |
Step 1 |
Router# configure terminal Enters global configuration mode. |
||
Step 2 |
Do one of the following:
Specifies the Gigabit Ethernet or Ten Gigabit Ethernet interface to configure and enters interface configuration mode, where:
|
||
Step 3 |
no negotiation auto Example:
(Optional) Disables automatic negotitation.
|
||
Step 4 |
speed { 10 | 100 | 1000 } Example:
(Optional) Specifies the speed for an interface to transmit at 10, 100, and 1000 Mbps (1 Gbps), where the default is 1000 Mbps. |
||
Step 5 |
Router(config-if)# carrier-delay down msec value (Optional) Sets the router to signal within the specified time delay, when an interface goes down, where:
|
||
Step 6 |
Router(config-if)# carrier-delay up msec value (Optional) Sets the router to signal within the specified time delay, when an interface should be up again, where:
You must wait for atleast 2 msec before bring the interface up again, this is to protect against link flaps. |
||
Step 7 |
Router(config-if)# ip address ip-address mask {secondary } | dhcp {client-id interface-name }{hostname host-name }] Sets a primary or secondary IP address for an interface that is using IPv4, where:
|
||
Step 8 |
Router(config-if)# mtu bytes (As Required) Specifies the maximum packet size for an interface, where:
The default is 1500 bytes; the range is from 1500 to 9216. |
||
Step 9 |
Router(config-if)# no shutdown Enables the interface. |
To configure or monitor Ethernet interfaces, you need to specify the physical location of the interface in the CLI. The interface address format is slot/port, where:
Note |
The interface slot number is always 0. |
Router(config)# interface GigabitEthernet 0/0/0
no ip address
shutdown
negotiation auto
no cdp enable
Hot Standby Router Protocol (HSRP) provides high network availability because it routes IP traffic from hosts without relying on the availability of any single router. You can deploy HSRP in a group of routers to select an active router and a standby router. (An active router is the router of choice for routing packets; a standby router is a router that takes over the routing duties when an active router fails, or when preset conditions are met).
HSRP is enabled on an interface by entering the standby [group-number ] ip [ip-address [secondary ]] command. The standby command is also used to configure various HSRP elements. This document does not discuss more complex HSRP configurations. For additional information on configuring HSRP, see to the HSRP section of the Cisco IP Configuration Guide publication that corresponds to your Cisco IOS XE software release. In the following HSRP configuration, standby group 2 on Gigabit Ethernet port 0/1/0 is configured at a priority of 110 and is also configured to have a preemptive delay should a switchover to this port occur:
Router(config)#interface GigabitEthernet 0/1/0
Router(config-if)#standby 2 ip 192.168.1.200
Router(config-if)#standby 2 priority 110
Router(config-if)#standby 2 preempt
The maximum number of different HSRP groups that can be created on one physical interface is 4. If additional groups are required, create 4 groups on the physical interface, and the remaining groups on the BDI or on another physical interface.
The maximum number of HSRP or VRRP groups allowed are:
RSP1A —128 HSRP or VRRP groups. 128 HSRP or VRRP groups restriction implies that the maximum number of different interfaces that can be configured with VRRP or HSRP is 128. You cannot configure HSRP or VRRP for more than 128 interfaces but you can configure upto 256 HSRP or VRRP groups in those 128 interfaces.
RSP1B —256 HSRP or VRRP groups
RSP2A-64 and RSP2-128—128 HSRP or VRRP groups, prior to Cisco IOS Release XE 3.15S
RSP2A-64 and RSP2-128 —256 HSRP or VRRP groups, starting Cisco IOS Release XE 3.15S
RSP3-200 and RSP3-400—255 HSRP or VRRP groups, starting Cisco IOS Release XE 3.18.1SP
Note |
TCAM space utilization changes when HSRP groups are configured on the router. If HSRP groups are configured the TCAM space is utilized. Each HSRP group takes 1 TCAM entry. The “Out of TCAM” message may be displayed if total number of TCAM space used by HSRP groups and prefixes on the router exceeds scale limit. |
Note |
HSRP state flaps with sub-second “Hello” or “Dead” timers. |
HSRPv2 is not supported.
To verify the HSRP information, use the show standby command in EXEC mode:
Router# show standby
Ethernet0 - Group 0
Local state is Active, priority 100, may preempt
Hellotime 3 holdtime 10
Next hello sent in 0:00:00
Hot standby IP address is 198.92.72.29 configured
Active router is local
Standby router is 198.92.72.21 expires in 0:00:07
Standby virtual mac address is 0000.0c07.ac00
Tracking interface states for 2 interfaces, 2 up:
UpSerial0
UpSerial1
Feature Name |
Release |
Description |
---|---|---|
Increase Maximum MTU Size |
Cisco IOS XE Cupertino 17.8.1 |
Maximum Transmission Unit (MTU) is increased to a maximum of 9670 bytes on the Cisco ASR 920 router. You can configure the MTU bytes using the mtu bytes command. |
Note |
The router supports only eight unique MTUs. |
The Cisco IOS software supports three different types of configurable maximum transmission unit (MTU) options at different levels of the protocol stack:
Interface MTU—The interface checks the MTU value of incoming traffic. Different interface types support different interface MTU sizes and defaults. The interface MTU defines the maximum packet size allowable (in bytes) for an interface before drops occur. If the frame is smaller than the interface MTU size, but is not smaller than the minimum frame size for the interface type (such as 64 bytes for Ethernet), then the frame continues to process.
IP MTU—Can be specified on an interface. If an IP packet exceeds the IP MTU size, then the packet is fragmented.
Tag or Multiprotocol Label Switching (MPLS) MTU—Can be specified on an interface and allows up to six different tag headers to be attached to a packet. The maximum number of tag headers (also referred to as labels) depends on your Cisco IOS software release.
Note |
If the MTU interface configuration exceeds the maximum number of supported bytes, then the input errors are incremented. For packets with maximum size, the counter does not support increment by using CLI as the ASIC is unable to handle it. This is applicable on Cisco ASR 920-10SZ-PD (OD), ASR-920-8S4Z-PD, ASR-920-12SZ-IM, ASR-920U-12SZ-IM, ASR-920-24SZ-IM, ASR-920-24SZ-M, and ASR-920-24TZ-M routers. |
Encapsulation methods and MPLS MTU labels add additional overhead to a packet. For example, Subnetwork Access Protocol (SNAP) encapsulation adds an 8-byte header, dot1q encapsulation adds a 4-byte header, and each MPLS label adds a 4-byte header (n labels x 4 bytes).
For the Gigabit Ethernet interface on the router, the default MTU size is 1500 bytes. The maximum configurable MTU is 9216 bytes. The interface automatically adds an additional 22 bytes to the configured MTU size to accommodate some of the additional overhead.
Effective Cisco IOS XE Cupertino 17.8.1, a maximum of 9644 MTU bytes are supported on the Cisco ASR 920 router.
Prior to this release, you can configure a maximum of 9216 bytes on the router.
The giants and input errors field counts are not incremented for both 1G and 10G ports on Cisco ASR 920 platforms.
In EtherLike-MIB, the dot3StatsFrameTooLongs frames count in SNMP increases when the frame packet size is more than the default MTU.
If the packet size is more than the configured MTU value and exceeds 1Mbps, packets are dropped. Packets are fragmented when the packet size is more than the configured MTU value and when traffic is lesser than 1Mbps.
Due to hardware limitation on the Cisco ASR 920 router, ping is not supported with MTU size of greater than 9215 bytes.
When configuring the interface MTU size, we recommend you consider the following guidelines:
Note |
The default interface MTU size always accommodates a 1500-byte packet, plus 22 additional bytes to cover the following additional overhead. |
An interface (without tagging applied), sends a maximum of 1522 bytes of data. Here the interface sends 1508 (Data) bytes + 14 (Layer 2 header) bytes = 1522 bytes.
An interface (with tagging applied) sends bytes as follows:
dot1q tagging — Interface sends 1504 (Data) bytes + 14 (Layer 2 header) + 4 (dot1q encapsulation header) bytes = 1522 bytes.
double dot1q tagging — Interface sends 1500 (Data) bytes + 14 (Layer 2 header) + 8 (double dot1q encapsulation header) bytes = 1522 bytes.
Interface MTU is not supported on BDI Interface.
If you are using MPLS labels, then you should increase the default interface MTU size to accommodate the number of MPLS labels. Each MPLS label adds 4 bytes of overhead to a packet.
Note |
If you are using MPLS, ensure that the mpls mtu command is configured for a value less than or equal to the interface MTU. This is not applicable on the RSP3 Module. |
To modify the MTU size on an interface, use the following command in interface configuration mode:
Command |
Purpose |
---|---|
|
Configures the maximum packet size for an interface, where:
The default is 1500 bytes and the maximum configurable MTU is 9216 bytes. |
To return to the default MTU size, use the no form of the command.
To verify the MTU size for an interface, use the show interfaces gigabitethernet privileged EXEC command and observe the value that is shown in the “MTU” field.
The following example shows an MTU size of 1500 bytes for interface port 0 (the first port) on the Gigabit Ethernet interface in slot 0 of the router:
Router# show interface gigabitEthernet 0/0/0
GigabitEthernet0/0/0 is down, line protocol is down
Hardware is 8xGE-4x10GE-FIXED, address is 6073.5cff.8080 (bia 6073.5cff.8080)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
The encapsulation supported by the interfaces is IEEE 802.1Q and IEEE 802.1ad encapsulation for virtual LANs (VLANs).
Note |
VLANs are only supported on Ethernet Virtual Connection (EVC) service instances and Trunk Ethernet Flow Point (EFP) interfaces. For more information about how to configure these features, see the Configuring Ethernet Virtual Connections document. |
Gigabit Ethernet interfaces use a connection-setup algorithm called autonegotiation. Autonegotiation allows the local and remote devices to configure compatible settings for communication over the link. Using autonegotiation, each device advertises its transmission capabilities and then agrees upon the settings to be used for the link.
For the Gigabit Ethernet interfaces on the router, flow control is autonegotiated when autonegotiation is enabled. Autonegotiation is enabled by default.
When enabling autonegotiation, consider these guidelines:
To enable autonegotiation on a Gigabit Ethernet interface, use the following command in interface configuration mode:
Command |
Purpose |
---|---|
|
Enables autonegotiation on a Gigabit Ethernet interface. Advertisement of flow control occurs. |
Autonegotiation is automatically enabled and can be disabled on Gigabit Ethernet interfaces . During autonegotiation, advertisement for flow control, speed, and duplex occurs, depending on the media (fiber or copper) in use.
Speed and duplex configurations can be advertised using autonegotiation. However, the only values that are negotiated are:
To disable autonegotiation, use the following command in interface configuration mode:
Command |
Purpose |
---|---|
|
Disables autonegotiation on Gigabit Ethernet interfaces. No advertisement of flow control occurs. |
For information about configuring an Ethernet interface as a layer 2 Ethernet virtual circuit (EVC) or Ethernet flow point (EFP), see Carrier Ethernet Configuration Guide, Cisco IOS XE Release 3S.
To save your running configuration to NVRAM, use the following command in privileged EXEC configuration mode:
Command |
Purpose |
---|---|
|
Writes the new configuration to NVRAM. |
For information about managing your system image and configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals Command Reference publications that correspond to your Cisco IOS software release.
You can shut down and restart any of the interface ports on an interface independently of each other. Shutting down an interface stops traffic and enters the interface into an “administratively down” state.
There are no restrictions for online insertion and removal (OIR) of Gigabit Ethernet interfaces; you can remove them at any time.
If you are preparing for an OIR, it is not necessary to independently shut down each of the interfaces prior to deactivation of the module.
Command |
Purpose |
---|---|
|
Restarts, stops, or starts an interface. |
To shut down an interface, use the following command in interface configuration mode:
Command |
Purpose |
---|---|
|
Disables an interface. |
To enable traffic on an interface, use the following command in interface configuration mode:
Command |
Purpose |
---|---|
|
Restarts a disabled interface. |
Besides using the show running-configuration command to display your router configuration settings, you can use the show interfaces gigabitethernet command to get detailed information on a per-port basis for your Gigabit Ethernet interface.
To find detailed interface information on a per-port basis for the Gigabit Ethernet interface, use the show interfaces gigabitethernet command.
The following example provides sample output for interface port 0 on the interface located in slot 1 of the router:
Router# show interface gigabitEthernet 0/0/7
GigabitEthernet0/0/7 is up, line protocol is up
Hardware is 8xGE-4x10GE-FIXED, address is 6073.5cff.8087 (bia 6073.5cff.8087)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is auto, media type is RJ45
output flow-control is off, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of “show interface” counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
You can use various show commands to view information specific to SFP, SFP+, CWDM, and DWDM optical transceiver modules.
Note |
The show interface transceiver command is not supported on the router. |
To check or verify the status of an SFP Module or SFP+ Module, use the following show commands:
Command |
Purpose |
||
---|---|---|---|
|
Displays information for the transceiver identification programmable read only memory (idprom).
|
||
|
Displays information for the transceiver initialization status.
|
||
|
Displays a dump of all EEPROM content that is stored in the transceiver. |
Following are sample output of several show commands for SFP Modules and SFP+ Modules.
The following show hw-module subslot command sample output is for SFP-GE-S:
Router# show hw-module subslot 0/0 transceiver 9 idprom
IDPROM for transceiver GigabitEthernet0/0/0:Description = SFP optics (type 3) Transceiver Type: = GE SX (19) Product Indentifier (PID) = FTRJ8519P1BNL-C6Vendor Revision = ASerial Number (SN) = FNS1037R8DHVendor Name = CISCO-FINISARVendor OUI (IEEE company ID) = 00.90.65 (36965)CLEI code = IPUIALJRAACisco part number = 10-2143-01Device State = Enabled.Date code (yy/mm/dd) = 06/09/14Connector type = LC.Encoding = 8B10BNRZNominal bitrate = GE (1300 Mbits/s) Minimum bit rate as % of nominal bit rate = not specifiedMaximum bit rate as % of nominal bit rate = not specified
The following show hw-module subslot command sample output is for CWDM 1490:
Router# show hw-module subslot 0/0 transceiver 2 idpromIDPROM for transceiver GigabitEthernet0/0/2:Description = SFP optics (type 3) Transceiver Type: = GE CWDM 1490 (28) Product Indentifier (PID) = FWDM-16217D49CSCVendor Revision = CSerial Number (SN) = FNS10500HA9Vendor Name = CISCO-FINISARVendor OUI (IEEE company ID) = 00.90.65 (36965)CLEI code = CNTRVX0FAACisco part number = 10-1884-01Device State = Enabled.Date code (yy/mm/dd) = 06/12/12Connector type = LC.Encoding = 8B10BNRZNominal bitrate = (2700 Mbits/s) Minimum bit rate as % of nominal bit rate = not specifiedMaximum bit rate as % of nominal bit rate = not specified
The following show hw-module subslot command sample output is for an SFP+ module:
Router# show
hw-module subslot 2/2 transceiver 9 idprom brief
IDPROM for transceiver TenGigabitEthernet0/0/9:
Description = SFP or SFP+ optics (type 3)
Transceiver Type: = SFP+ 10GBASE-SR (273)
Product Identifier (PID) = SFP-10G-SR
Vendor Revision = 1
Serial Number (SN) = JUS1803G2FT
Vendor Name = CISCO-JDSU
Vendor OUI (IEEE company ID) = 00.01.9C (412)
CLEI code = COUIA8NCAA
Cisco part number = 10-2415-03
Device State = Enabled.
Date code (yy/mm/dd) = 14/01/18
Connector type = LC.
Encoding = 4b5b
NRZ
Manchester
Nominal bitrate = (10300 Mbits/s)
Minimum bit rate as % of nominal bit rate = not specified
Maximum bit rate as % of nominal bit rate = not specified
The following show hw-module subslot command sample output is for an SFP+ module:
Router# show hw-module subslot 0/3 transceiver 9 status
The Transceiver in slot 0 subslot 0 port 9 is enabled.
Module temperature = +24.773 C
Transceiver Tx supply voltage = 3291.3 mVolts
Transceiver Tx bias current = 6024 uAmps
Transceiver Tx power = -2.3 dBm
Transceiver Rx optical power = -2.9 dBm
The following sample output is for SFP-GE-SX:
Router# show hw-module subslot 0/0 transceiver 9 idprom dump
IDPROM for transceiver GigabitEthernet0/0/0:Description = SFP optics (type 3) Transceiver Type: = GE SX (19) Product Indentifier (PID) = FTRJ8519P1BNL-C6Vendor Revision = ASerial Number (SN) = FNS1037R8DHVendor Name = CISCO-FINISARVendor OUI (IEEE company ID) = 00.90.65 (36965)CLEI code = IPUIALJRAACisco part number = 10-2143-01Device State = Enabled.
SFP IDPROM Page 0xA0:000: 03 04 07 00 00 00 01 00 00 00010: 00 01 0D 00 00 00 37 1B 00 00020: 43 49 53 43 4F 2D 46 49 4E 49030: 53 41 52 20 20 20 00 00 90 65040: 46 54 52 4A 38 35 31 39 50 31050: 42 4E 4C 2D 43 36 41 20 20 20060: 03 52 00 74 00 1A 00 00 46 4E070: 53 31 30 33 37 52 38 44 48 20080: 20 20 20 20 30 36 30 39 31 34090: 20 20 58 80 01
SFP IDPROM Page 0xA2:000: 6D 00 E3 00 67 00 F3 00 98 58010: 69 78 90 88 71 48 1D 4C 01 F4020: 17 70 03 E8 25 19 02 F5 25 19030: 04 A9 E3 EE 01 DF 8F C5 02 EC040: 00 00 00 00 00 00 00 00 00 00050: 00 00 00 00 00 00 00 00 00 00060: 00 00 00 00 00 00 00 00 3E 5D070: 01 79 C0 5B AC 86 01 00 00 00080: 00 AA FF FD 01 00 00 00 01 00090: 00 00 00 00 00 3A 1B 70 80 D8100: 00 62 00 28 00 22 00 00 00 00110: 82 F8 05 40 00 00 05 40 00 00120: 00 00 00 00 00 00 00 01 49 50130: 55 49 41 4C 4A 52 41 41 31 30140: 2D 32 31 34 33 2D 30 31 56 30150: 31 20 89 FB 55 00 00 00 00 78160: 00 00 00 00 00 00 00 00 00 00170: 00 00 00 00 00 00 00 00 00 00180: 00 00 00 00 00 00 00 00 00 00190: AA AA 53 46 50 2D 47 45 2D 53200: 20 20 20 20 20 20 20 20 20 20210: 20 20 00 00 00 00 00 00 00 00220: 00 00 00 A2 00 00 00 00 00 00230: 00 00 00 00 00 00 00 00 00 00240: 00 00 00 00 00 00 00 00 00 40250: 00 40 00 00 00 00Router#
Note |
VID for optics that are displayed in show inventory command and vendor revision that is shown in idprom detail command output are stored in different places in Idprom. |
The LAN/WAN-PHY controllers are configured in the physical layer control element of the Cisco IOS XE software. Use the hw-module subslot slot/subslot enable lan command to configure the LAN-PHY mode.
Note |
WAN-PHY Mode is not currently supported on the Cisco ASR 920 Series Router. |
This section describes how to configure the LAN-PHY mode on the Gigabit Ethernet interfaces.
Step 1 |
show controllers wanphy 0/0/1 Example:
Displays the configuration mode of the LAN/WAN-PHY controller. By default, prior to configuration of the LAN-PHY mode, the controller operates in the WAN-PHY mode. |
Step 2 |
configure terminal Example:
Enters the global configuration mode. |
Step 3 |
hw-module subslot slot/subslot enable LAN Example:
Configures the LAN PHY mode for the 1-Port 10-Gigabit Ethernet LAN/WAN PHY SPA. |
Step 4 |
exit Example:
Exits global-configuration (config) mode and enters privilege-exec mode. |
Step 5 |
show controllers wanphy 0/0/1 Example:
Displays the configuration mode for the LAN/WAN-PHY controller. The example shows the mode of operation as LAN mode for the 1-Port 10-Gigabit Ethernet LAN/WAN PHY SPA. |
Note |
WAN-PHY Mode is not supported on the Cisco ASR 920 Series Router. |
This section describes how to configure WAN-PHY Signal Failure (SF) and Signal Degrade (SD) Bit Error Rate (BER) reporting and thresholds.
A Signal Failure (SF) alarm is declared if the line bit error (B2) rate exceeds a user-provisioned threshold range (over the range of 10e-3 to 10e-9).
A Signal Degrade (SD) alarm is declared if the line bit error (B2) rate exceeds a user-provisioned threshold range (over the range of 10e-3 to 10e-9). If the B2 errors cross the SD threshold, a warning of link quality degradation is triggered. The WAN-PHY alarms are required for some users who are upgrading their Layer 2 core network from a SONET ring to a 10-Gigabit Ethernet ring.
Note |
The controller must be in the WAN-PHY mode prior to configuring the SF and SD BER reporting and thresholds. |
This section includes the following configuration examples:
The following example shows how to enter the global configuration mode to specify the interface that you want to configure, configure an IP address for the interface, and save the configuration.
! Enter global configuration mode.
!
Router# configure terminal
!
! Enter configuration commands, one per line. End with CNTL/Z.
!
! Specify the interface address.
!
Router(config)# interface gigabitethernet 0/0/1
!
! Configure an IP address.
!
Router(config-if)# ip address 192.168.50.1 255.255.255.0
!
! Start the interface.
!
Router(config-if)# no shut
!
! Save the configuration to NVRAM.
!
Router(config-if)# exit
Router# copy running-config startup-config
The following example shows how to set the MTU interface to 9216 bytes.
Note |
The interface automatically adds an additional 38 bytes to the configured MTU interface size. |
! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
!
! Specify the interface address
!
Router(config)# interface gigabitethernet 0/0/1
!
! Configure the interface MTU.
!
Router(config-if)# mtu 9216
The following example shows how to configure the interface port 2 (the third port), and configure the first interface on the VLAN with the ID number 268, using IEEE 802.1Q encapsulation:
! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface gigabitEthernet 0/0/5
!
! Specify the interface address
!
Router(config-if)# service instance 10 ethernet
!
! Configure dot1q encapsulation and specify the VLAN ID.
!
Router(config-if-srv)# encapsulation dot1q 268
VLANs are only supported on EVC service instances and Trunk EFP interfaces. For more information about how to configure these features, see the see the Carrier Ethernet Configuration Guide, Cisco IOS XE Release 3S.