This chapter covers Metro Ethernet Services, a critical technology for connecting geographically dispersed enterprise sites over a metropolitan area. You will learn how Metro Ethernet delivers scalable, high-bandwidth connectivity using Ethernet standards, its key components like E-LINE and E-LAN services, and how it differs from traditional WAN technologies. On the N10-009 exam, expect approximately 5-8% of questions to touch on Metro Ethernet concepts, typically in the context of network implementation and troubleshooting scenarios. Mastering this topic is essential for understanding modern WAN architectures.
Jump to a section
Imagine a city with multiple office buildings, each owned by a different company. The city builds a network of highways connecting these buildings, but instead of each company building its own private road, the city creates a system of virtual lanes. Each company gets a dedicated lane that only its own vehicles can use, even though all lanes are on the same physical highway. The city installs toll booths at each building entrance that check the vehicle's company ID (VLAN tag) and ensure it stays in its designated lane. If a vehicle tries to cross into another company's lane, the toll booth strips the vehicle's ID and discards it. This is exactly how Metro Ethernet works: the service provider builds a shared physical infrastructure (the highway), but uses VLAN tags to create separate, isolated virtual circuits (the lanes) for each customer. The provider's switches at the edge (the toll booths) enforce separation by only allowing frames with the correct VLAN tag to enter or exit each customer's network. This eliminates the need for each customer to lease expensive private fiber, while still providing the security and performance of a dedicated connection.
What is Metro Ethernet?
Metro Ethernet (MetroE) is a service that uses Ethernet as the access technology to connect customer sites within a metropolitan area network (MAN). It leverages the ubiquity and low cost of Ethernet equipment to provide high-speed, scalable connectivity. The service is defined by the Metro Ethernet Forum (MEF) standards, which specify how to deliver carrier-grade Ethernet services over a service provider's network.
Why Metro Ethernet Exists
Traditional WAN technologies like T1/E1, Frame Relay, and ATM were expensive, complex, and offered limited bandwidth (typically up to 45 Mbps for DS3). Metro Ethernet provides: - Higher bandwidth: From 10 Mbps to 10 Gbps and beyond, easily scalable. - Lower cost: Uses commodity Ethernet hardware and fiber. - Flexibility: Supports multiple service types (point-to-point, multipoint). - Simpler management: Staff familiar with Ethernet can manage the WAN with the same skills.
How Metro Ethernet Works
Metro Ethernet operates by encapsulating customer Ethernet frames into service provider frames (often using Q-in-Q or MPLS) and transporting them across the provider's network. The key mechanism is the User Network Interface (UNI), the physical demarcation point between the customer edge (CE) and the provider edge (PE). Each UNI has a unique identifier and is configured with a service VLAN (S-VLAN) that maps to a specific service.
The provider uses Ethernet Virtual Connections (EVCs) to define the logical connectivity between UNIs. An EVC is a logical path that carries frames between two or more UNIs. The MEF defines two main EVC types: - E-LINE: A point-to-point EVC connecting exactly two UNIs. - E-LAN: A multipoint-to-multipoint EVC connecting multiple UNIs, like a virtual switch.
Key Components and Values
UNI: The physical port at the provider edge. Default speed/duplex is auto-negotiated; common speeds are 100 Mbps, 1 Gbps, 10 Gbps.
EVC: Identified by a 12-bit S-VLAN ID (IEEE 802.1ad). The S-VLAN ID ranges from 1 to 4094, with 0 and 4095 reserved.
CE-VLAN ID: The customer's own VLAN tag (C-VLAN). The provider may map multiple C-VLANs to a single EVC or use transparent mode.
Bandwidth Profile: Defines committed information rate (CIR), excess information rate (EIR), and burst sizes. Default CIR is the port speed; EIR is often zero.
Class of Service (CoS): Uses 3-bit PCP field in VLAN tag to prioritize traffic (e.g., voice, video, data). Default CoS is 0 (best effort).
Configuration and Verification Commands
On a Cisco provider edge switch, a typical Metro Ethernet configuration might look like:
! Configure the UNI interface
interface GigabitEthernet0/1
description Customer A UNI
switchport mode trunk
switchport trunk allowed vlan 100
switchport trunk native vlan 999
mtu 9216
no shutdown
!
! Create a service instance (EVC)
interface GigabitEthernet0/1
service instance 10 ethernet
encapsulation dot1q 100
rewrite ingress tag push dot1q 100 symmetric
bridge-domain 10
!
! Configure the bridge domain
bridge-domain 10
!
! Verify
show ethernet service instance
show bridge-domain
show interface gigabitEthernet 0/1.10Metro Ethernet and MPLS
Many Metro Ethernet deployments use MPLS in the core to provide scalability and traffic engineering. The provider edge routers encapsulate customer frames into MPLS labels. The EVC is mapped to a pseudowire (for E-LINE) or a VPLS instance (for E-LAN). The MPLS label stack includes the outer label for the transport LSP and an inner label for the pseudowire/VPLS.
Interconnection with Other Technologies
Metro Ethernet can interconnect with: - MPLS VPNs: The provider can hand off traffic to an MPLS Layer 3 VPN for IP routing. - Internet: Often combined with a separate Internet access circuit or via a dedicated EVC to an ISP. - SD-WAN: Metro Ethernet can serve as the underlay transport for SD-WAN overlays, providing high-bandwidth, low-latency links.
Performance Considerations
Latency: Typically 1-5 ms within a metro area.
Jitter: < 1 ms with proper CoS configuration.
Packet Loss: < 0.1% for committed traffic.
MTU: Support for jumbo frames up to 9216 bytes is common.
Troubleshooting Common Issues
VLAN mismatch: Customer and provider VLAN IDs must align. Use show vlan and show interface trunk.
MTU mismatch: If the customer sends jumbo frames but the provider only supports 1500 bytes, packets are dropped. Verify with ping size 9000.
Bandwidth congestion: Monitor CIR and EIR utilization. Use show interface for counters.
Summary of MEF Standards
MEF 6.1: Defines EVC attributes and service types.
MEF 10.3: Defines bandwidth profiles and performance metrics.
MEF 11: Defines UNI requirements and management.
MEF 20: Defines UNI Type 2 (support for multiple EVCs per UNI).
Customer orders Metro Ethernet service
The customer specifies the number of sites, required bandwidth (CIR/EIR), and service type (E-LINE or E-LAN). The provider designs the network, assigns S-VLAN IDs, and provisions UNIs at each site. The customer provides CE-VLAN mapping preferences. The provider configures the PE devices with service instances, bridge domains, or pseudowires. An installation date is set, and the provider coordinates with local fiber or copper access providers if needed.
Physical installation and UNI activation
The provider installs fiber or copper from the nearest provider point of presence (POP) to the customer's premises. A demarcation device (e.g., optical network terminal or Ethernet switch) is placed at the UNI. The provider verifies physical connectivity using optical power meters or cable testers. The UNI interface is configured with the agreed speed/duplex (usually auto-negotiation). The provider performs a loopback test at the physical layer to ensure the link is error-free.
Service instance and EVC configuration
On the PE, the provider creates a service instance that matches the customer's CE-VLAN tag (or uses untagged). The service instance is associated with an EVC, which is either a point-to-point pseudowire (E-LINE) or a multipoint VPLS instance (E-LAN). The provider configures the bandwidth profile (CIR/EIR) using policing or shaping. CoS marking rules are applied based on the customer's PCP values. The provider then tests the EVC by sending test frames from one UNI to another.
Customer edge device configuration
The customer configures their CE router or switch to match the provider's UNI settings. This includes setting the correct VLAN tagging (if any), MTU (typically 1500 or 9216), and any routing protocols if the service is used for IP connectivity. The CE must be configured with the provider's IP addressing scheme if the service is Layer 3. The customer tests connectivity by pinging the remote CE's IP address or sending traffic to verify the EVC is operational.
Performance testing and handover
The provider and customer jointly perform acceptance tests. This includes throughput tests (e.g., iPerf) at the contracted CIR and EIR, latency and jitter measurements, and packet loss tests. They verify that jumbo frames pass if supported. The provider may run a Y.1564 test to validate bandwidth profiles and CoS. Once all tests pass, the service is handed over for production use. The provider monitors the service using SNMP and NMS, and the customer can also monitor via standard Ethernet OAM tools (e.g., Link OAM, CFM).
Scenario 1: Enterprise Headquarters to Branch Offices
A financial services company with headquarters in downtown Chicago and three branch offices in the suburbs needs high-speed, low-latency connectivity for real-time trading applications. They choose Metro Ethernet E-LINE services, each point-to-point from HQ to each branch. The provider provisions 1 Gbps UNIs at each site with a CIR of 500 Mbps and EIR of 1 Gbps. The company uses jumbo frames (MTU 9000) to maximize throughput. In production, they see latency of 2 ms and zero packet loss. The primary challenge is ensuring the provider's network does not oversubscribe the aggregation links; the company monitors using SNMP and has a SLA with 99.99% uptime. A common issue is when the provider's EIR is not policed correctly, causing congestion during peak hours. The company mitigates by using CoS to prioritize trading traffic over file transfers.
Scenario 2: Data Center Interconnect (DCI)
A cloud provider operates two data centers 15 km apart in the same metro area. They need a high-bandwidth, low-latency link for storage replication (e.g., vSAN) and VM live migration. They deploy Metro Ethernet E-LINE with 10 Gbps UNIs and a CIR of 10 Gbps (no oversubscription). The service uses MPLS in the core for fast failover (< 50 ms). The provider configures the UNIs with transparent mode (no VLAN tagging) to carry the customer's existing VLANs (up to 4094). The customer uses LACP between the CE and PE for redundancy. Performance is critical: latency must be under 1 ms, and jitter under 100 μs. They run continuous latency monitoring using OWAMP. A misconfiguration occurred when the provider set the UNI MTU to 1500, causing dropped packets for jumbo frames; this was resolved by raising the MTU to 9216.
Scenario 3: Multisite Connectivity with E-LAN
A hospital system with five locations needs a private network for electronic health records (EHR) and VoIP. They choose Metro Ethernet E-LAN, which provides any-to-any connectivity like a giant switch. The provider provisions a single EVC connecting all five UNIs. Each UNI is 100 Mbps with CIR 50 Mbps. The hospital uses a single IP subnet (10.10.0.0/16) across all sites, with OSPF as the routing protocol. The E-LAN simplifies routing because all sites are directly connected. A challenge is broadcast traffic: the E-LAN forwards broadcasts to all sites, so the hospital uses VLAN segmentation and storm control on the CE switches. They also use IGMP snooping to limit multicast traffic. The provider's E-LAN is implemented using VPLS; a failure in the VPLS core caused a split-brain scenario, which was resolved by the provider enabling BGP-based auto-discovery and route reflectors.
N10-009 Objective 2.4: Network Implementation - Metro Ethernet
On the CompTIA Network+ N10-009 exam, you must be able to:
Identify the characteristics and benefits of Metro Ethernet.
Distinguish between E-LINE, E-LAN, and other service types.
Understand the role of the UNI, EVC, and VLAN tags.
Know typical bandwidths, distances, and applications.
Common Wrong Answers and Traps
Confusing E-LINE with E-LAN: Candidates often choose E-LAN when the question describes a point-to-point connection. Remember: E-LINE is for two sites only; E-LAN is for three or more sites.
Assuming Metro Ethernet requires MPLS: Not all Metro Ethernet uses MPLS; it can use Q-in-Q (802.1ad) in the core. MPLS is common for scalability but not mandatory.
Thinking Metro Ethernet is always Layer 2: Metro Ethernet can be Layer 2 (EVC) or Layer 3 (if the provider routes). The exam often tests that it is typically a Layer 2 service.
Mixing up CIR and EIR: CIR is guaranteed; EIR is best-effort. A question may state 'the provider guarantees 100 Mbps' - that's CIR, not EIR.
Specific Numbers and Terms
Bandwidth range: 10 Mbps to 10 Gbps (commonly 100 Mbps, 1 Gbps, 10 Gbps).
Distance: Typically up to 50 km (metro area).
MTU: Default 1500; jumbo frames up to 9216 bytes.
MEF: The standards body.
UNI: User Network Interface - the demarcation point.
EVC: Ethernet Virtual Connection.
Edge Cases and Exceptions
UNI Type 2: Supports multiple EVCs on a single UNI (MEF 20). The exam may ask about this for advanced scenarios.
E-TREE: A third service type (point-to-multipoint) that is less common but may appear in some questions. E-TREE has a root UNI and multiple leaf UNIs; traffic flows from root to leaves, but leaves cannot communicate directly.
CE-VLAN ID preservation: The provider may or may not preserve the customer's VLAN tag. Questions about transparent mode vs. mapping are common.
How to Eliminate Wrong Answers
If the question asks for 'point-to-point', eliminate E-LAN and E-TREE.
If the question mentions 'multipoint to multipoint', eliminate E-LINE.
If the question describes a service that connects multiple sites in a mesh, it's E-LAN.
If the question says 'dedicated bandwidth', look for CIR; if 'burstable', look for EIR.
If the question mentions 'carrier-grade' or 'MEF', it's likely Metro Ethernet.
Metro Ethernet provides high-speed, scalable connectivity within a metropolitan area using Ethernet technology.
The MEF defines three service types: E-LINE (point-to-point), E-LAN (multipoint-to-multipoint), and E-TREE (point-to-multipoint).
The UNI is the physical demarcation point between customer and provider; the EVC defines the logical connection.
Metro Ethernet can use Q-in-Q (802.1ad) or MPLS as the transport technology.
Bandwidth profiles include CIR (guaranteed) and EIR (best-effort); CIR is typically 50-100% of port speed.
Jumbo frames up to 9216 bytes are commonly supported.
Metro Ethernet is typically a Layer 2 service, but can be extended to Layer 3 with routing.
Performance metrics: latency < 5 ms, jitter < 1 ms, packet loss < 0.1% for committed traffic.
Common troubleshooting issues: VLAN mismatch, MTU mismatch, and bandwidth congestion.
The exam expects you to differentiate between E-LINE, E-LAN, and E-TREE based on connectivity requirements.
These come up on the exam all the time. Here's how to tell them apart.
E-LINE (Point-to-Point)
Connects exactly two UNIs.
Simple to configure; no spanning tree issues.
Bandwidth is dedicated between the two sites.
Cost scales linearly with number of connections (N-1).
Commonly used for site-to-site WAN links.
E-LAN (Multipoint-to-Multipoint)
Connects three or more UNIs in a full mesh.
Requires split-horizon or VPLS to avoid loops.
Bandwidth is shared among all sites; may oversubscribe.
Cost is independent of number of sites (single EVC).
Commonly used for multi-site LAN extension.
Mistake
Metro Ethernet is the same as Carrier Ethernet.
Correct
Metro Ethernet is a subset of Carrier Ethernet, specifically for metropolitan areas. Carrier Ethernet can span wider areas, including inter-city, and includes additional features like OAM and synchronization.
Mistake
Metro Ethernet only supports point-to-point connections.
Correct
Metro Ethernet supports multiple service types: E-LINE (point-to-point), E-LAN (multipoint-to-multipoint), and E-TREE (point-to-multipoint). The exam expects you to know all three.
Mistake
Metro Ethernet requires fiber optic cabling.
Correct
While fiber is common for higher speeds, Metro Ethernet can also run over copper (e.g., 1000BASE-T) or even DSL for lower bandwidths. The UNI is media-independent.
Mistake
The customer must use the same VLAN IDs as the provider.
Correct
The provider maps customer VLANs (C-VLAN) to service VLANs (S-VLAN). The customer can use any VLAN IDs, and the provider translates them. Transparent mode allows the customer's VLANs to pass through unchanged.
Mistake
Metro Ethernet cannot carry jumbo frames.
Correct
Most Metro Ethernet services support jumbo frames up to 9216 bytes. The standard MTU is 1500, but jumbo frames are common for data center interconnect.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Metro Ethernet is a subset of Carrier Ethernet limited to a metropolitan area (typically < 50 km). Carrier Ethernet can span any distance and includes additional features like standardized OAM (802.3ah, 802.1ag) and synchronization (SyncE). For the N10-009 exam, consider Metro Ethernet as Carrier Ethernet within a metro.
Metro Ethernet uses Q-in-Q (IEEE 802.1ad) where the provider adds an outer S-VLAN tag to the customer's inner C-VLAN tag. The S-VLAN identifies the EVC. The customer can use any C-VLAN IDs; the provider may preserve them (transparent mode) or map them to a different S-VLAN. The exam may ask about 'double tagging' or 'stacked VLANs'.
E-LINE is a point-to-point Ethernet Virtual Connection connecting exactly two UNIs, like a leased line. E-LAN is a multipoint-to-multipoint connection connecting three or more UNIs, like a virtual switch. On the exam, if the scenario has only two sites, choose E-LINE; if three or more, choose E-LAN.
Yes, Metro Ethernet can provide Internet access by connecting the customer's UNI to the provider's Internet gateway. This is often called 'Dedicated Internet Access' (DIA) over Ethernet. However, the exam typically focuses on private WAN connectivity, not Internet.
There is no hard limit, but Metro Ethernet is designed for metropolitan areas, typically up to 50 km. Beyond that, latency and fiber costs increase. For longer distances, Carrier Ethernet or MPLS WAN is used.
Metro Ethernet operates at Layer 2 (Ethernet), while MPLS VPN can be Layer 2 or Layer 3. Metro Ethernet is simpler and lower cost for metro areas, but MPLS VPN offers more advanced features like any-to-any routing and global reach. The exam may ask you to choose between them based on requirements.
The Metro Ethernet Forum (MEF) is the industry body that defines standards for Carrier Ethernet services, including service types (E-LINE, E-LAN, E-TREE), UNI requirements, and performance metrics. On the exam, MEF is referenced as the authority for Metro Ethernet specifications.
You've just covered Metro Ethernet Services — now see how well it sticks with free N10-009 practice questions. Full explanations included, no account needed.
Done with this chapter?