E-VPLS FAQ

What is Ethernet VPLS?

E-VPLS is an Ethernet-based point-to-multipoint and any-to-any Layer 2 VPN. It allows carriers to connect geographically dispersed Ethernet local area networks (LAN) sites to each other across an MPLS backbone. For carriers who implement TelePacific’s E-VPLS for their customers, all sites appear to be in the same Ethernet LAN even though traffic travels across TelePacific's network.

How does Ethernet VPLS work?

E-VPLS, in its implementation and configuration, has much in common with a Layer 2 VPN. In E-VPLS, a packet originating within an end-user customer’s network is sent first to a customer edge (CE) device (for example, a router or Ethernet switch). It is then sent to a provider edge (PE) router within TelePacific’s network. The packet traverses TelePacific’s network over a MPLS label-switched path (LSP). It arrives at the egress PE router, which then forwards the traffic to the CE device at the destination site. The destination site can be either the (1) carrier’s E-HUB/NNI in a point-to-multipoint solution, or (2) an end-user customer’s location in a fully meshed any-to-any network.

The difference is that for E-VPLS, packets can traverse the network in point-to-multipoint or any-to-any fashion, meaning that a packet originating from a CE device can be broadcast to all the PE routers participating in an E-VPLS routing instance. In contrast, a Layer 2 VPN forwards packets in point-to-point fashion only.

E-VPLS can be implemented using BGP or LDP…which network architecture does TelePacific utilize?

The paths carrying E-VPLS traffic between each PE router participating in a routing instance are called pseudowires. The pseudowires are signaled using either BGP or LDP. TelePacific uses BGP which allows the new PE router (supporting a new end-user customer site) to be automatically discovered by the other existing PEs as new sites are added.

Will customers be able to transparently pass VLAN tags over the Ethernet access circuit to our customer without any coordination with TelePacific?

Yes, TelePacific supports 802.1Q-in-Q VLAN tags (S-Tags) and customer VLAN tags (C-Tags) in the range of 1-4000 transparently passed across from one end-user customer site to the TelePacific carrier customer’s network (E-HUB/NNI).

Will E-VPL EVC connections be 100% transparent to allow the following to flow end-to-end: Multicast packets, CDP, VTP and ISO/CLNS?

Yes, end-to-end transparency of multicast, CDP, VTP, OSPF and ISO/CLNS packets is supported. Some vendor proprietary frames cannot be guaranteed, please contact TelePacific to request additional information.

Will carriers or end-user customers be able to transparently pass layer2 and layer3 QoS markings over the E-VPL Ethernet virtual circuit (EVC)?

Yes, customer CoS markings will be preserved end to end.

Will E-VPL EVC connections function as a circuit providing dedicated bandwidth?

Yes. TelePacific EVC connections are assigned dedicated bandwidth.

Will TelePacific E-VPL EVC connections support jumbo frames?

Yes, jumbo frames are supported up to 1600 bytes. TelePacific will support jumbo frames exceeding 9000 beginning 4Q of 2011.

Can TelePacific support S-Tag assignment for each end-user customer spoke-site during the provisioning process?

Yes, the end-user customer’s S-Tag will be treated as inner VLAN within TelePacific’s VLAN. TelePacific’s S-Tag will be stripped off at the spoke site and handed off at the destination in the manner the frame was received.

If the end-user customer requires both S-Tag and C-Tag use EtherType 0x8100 (VLAN-tagged frame), can TelePacific support?

Yes.

What E-VPL EVC bandwidths are supported?

TelePacific offers 1-20Mbps where qualified loops exist. Bandwidth available is directly impacted by the distance from the LSO, gauge of wire and condition of the line (i.e. absence of bridge taps, load coils, repeaters, pairgain and remote terminals).

At the E-HUB/NNI aggregation connection, what GigE interface does TelePacific support?

TelePacific will accept single mode and multi-mode fiber (1000Base-LX and 1000-Base-SX), twisted-pair cabling 1000Base-T (Cat5e, Cat6 or Cat7). TelePacific supports Gigabit Ethernet interface standards specified in IEEE 802.3 for interconnection.

How will the E-HUB/NNI ports be configured?

Fiber ports are configured as full duplex only. Auto negotiation for speed and duplex is preferable.

Can the E-HUB/NNI port support oversubscription?

Yes.

Does the E-HUB/NNI support CoS?

Yes. Unless otherwise specified by the wholesale customer, default configuration is real-time CoS.

What E-HUB/NNI port bandwidths are supported?

TelePacific offers 100MB-1Gigabyte in 100MB increments.

Where are your E-HUB/NNI attachment locations?

Los Angeles (two locations); San Diego and San Jose. Contact TelePacific for information about additional locations and Ethernet Exchanges.

Will the TelePacific E-HUB/NNI support Q-in-Q VLAN tagging?

Yes.

  

What are your SLAs for E-VPLS connections?

SLA Objectives are based on class of service levels within E-HUB/NNI market.

Ethernet
CoS
Packages		 General Description Service Performance
Standard Provides access to lowest Ethernet queue; primarily meant for non-real time services; common application: Internet Access Non Real-time
Delay < 30ms
Jitter = N/S
Loss < 0.5%
Silver Provides access to the lowest (non real-time) and highest (real-time) Ethernet CoS queues; suitable for combined voice/data or video/data services Non Real-time
Delay < 30ms
Jitter = N/S
Loss < 0.5%

Real-time
Delay < 5ms
Jitter = 5ms
Loss < 0.001%
Premium Provides access to all four Ethernet CoS queues; suitable for finer classification and priority treatment by application
  1. Lowest (non real-time): Internet Access
  2. Interactive, bursty data applications requiring bandwidth assurances; MS Exchange, CRM or dBase
  3. Mission critical applications requiring low loss and delay: Video
  4. Highest Ethernet CoS queue (real-time): IP Voice or IP Video
 Non Real-time
Delay < 30ms
Jitter = N/S
Loss < 0.5%

Interactive Bursty
Delay < 15ms
Jitter = N/S
Loss < 0.1%

Mission Critical
Delay < 5ms
Jitter = N/S
Loss < 0.01%

Real-time Delay < 5ms
Jitter = 5ms
Loss < 0.001%

How is SLA performance measured, (e.g.: P -> P, PE -> PE)?

Measurements are two-way.

Do we support DSCP (differentiated services code point) preservation?

Yes, DSCP will be preserved.

Do we support all-to-one bundling (NxCEVLANs mapped to single S-tag at customer UNI)?

Yes

Do we support CoS employed using 802.1p bit markings (as opposed to DSCP)?

Yes, on the MPLS cloud we map 802.1p to MPLS EXP.

Do we support static port CoS mapping, including 100% of any CoS on EVC?

Yes

Are EVCs policed at egress?

Yes, at the PE (Providers Edge)

What are your install and repair intervals?

Installation within 21 business days and mean time to repair (MTTR) is 4 hours.

What is your installation policy?

TelePacific's demarcation is the ILEC minimum point of entry (MPOE). Carrier partners should conduct a site survey prior to installation – information needed:

  1. Does the backboard have enough space to support the NTU (24"W x 24"D x 4"H)?
  2. Ensure there a power source within 6 feet of the backboard.
  3. The distance (feet) from MPOE to the customer’s telephone room/suite to determine the proper TelePacific NTU to install.

Does TelePacific extend demarcations?

If requested, TelePacific will provide a demarc extension based upon time and material rates. There are restrictions.

TelePacific cannot extend through brick, concrete and fire rated walls; through multi-tenants, multiple units; multiple stories or multiple telephone closets; or where external requirements demand weather proof wiring; or if conduit, coring or drilling is required.

What happens if there aren’t enough copper facilities in a building?

In some instances, the ILEC does not have sufficient DS0 cable pairs from the ILEC local serving office (LSO) to provide Ethernet VPLS Service. If construction is required, and if acceptable to the Customer, TelePacific will pass through ILEC construction costs.

BLOG

© 2011 TelePacific Communications All Rights Reserved.