- Ordering FAQs
- Q : Where do I send my Wholesale Domestic order requests?
-
A : Submit each order based on the product and type of request:
Submit Low Bandwidth (DS0 and DS1) service orders to: wholesale-icr@verizon.com
Submit High bandwidth (DS3 and above) service orders to: bne-orders@verizon.com
Submit LD Switched service orders to: switchedvzorders@verizon.com
Option 4 Internet and Data Center orders - whlsoption4om@one.verizon.com
-
- Q : Where do I submit disconnect orders?
-
A : Submit disconnect orders to: wholesale-disconnects@verizon.com
-
- Q : How long does OE (Order Entry) have to enter or reject an order request?
-
A : 48 hours (2 business days)
-
- Q : What is a RFC?
-
A : Request for Clarification. The order will move to "rejected status" if a response to the RFC is not provided.
-
- Q : What is an OCD?
-
A : Order Confirmation Document
-
- Q : What is included in an OCD?
-
A1 : OCD for Option 1 services includes order number, and Customer Requested Due Date (CRDD). Circuit ID will be provided on FOC.
A2 : OCD for all other Options includes Circuit ID, order number, and Customer Requested Due Date (CRDD).
-
- Q : Where do I find order forms for services?
-
A : Click for link to order forms.
-
- Q : Where are the instructions to complete the order forms?
-
A : Click the "Instructions" tab at the bottom of each applicable order form.
-
- Q : How do I get the DMARC extended after the circuit has been installed?
-
A: Submit a new "Change" order to re-schedule an installation. Change orders are subject to additional charge.
-
- Q : Where do I send my Wholesale Domestic order requests?
- Sales Engineering FAQs
- Q : When will I be given my Firm Order Commitment (FOC) or Due Date?
-
A : FOC will be provided as soon as it is available based on the specific product being ordered. For Tier 3 accounts, if you have not received FOC within 10 days after firm order confirmation, please contact your Service Delivery Specialist (SDS) for status. For all other accounts, customers may obtain FOC updates via whlsorderupdates@verizon.com. (Only Tier 3 Accounts have assigned SDS. All other accounts are handled by Project Managers and they are assigned to the DS3 and above orders. Customers will need to get update regarding FOC via whlsorderupdates@verizon.com)
Standard delivery timeframes are based on product and are subject to change. Please contact your Sales Account Team for a list of most current Standard Delivery Dates.
Normally, once FOC has been issued for an order, a committed delivery date will be given to the customer.
-
- Q : What Ethernet handoff types are available; can I have different handoffs for each end?
-
A : Available handoffs can be found in the drop down selections on the order form entitled "Verizon Partner Solutions U.S. Private Line, Metro Private Line, Ethernet and Wavelength Order Form." Verizon Partner Solutions will support different handoff types at each location.
-
- Q : Where do I go for order status and updates?
-
A : Please contact a Service Delivery Specialist at whlsorderupdates@verizon.com
-
- Q : What BAN # do I use for the different products? (The F&E provisioning and Billing account number are both required on the order.)
-
A : Metro Private Line (intraLATA circuits) - Require a city specific metro account number. Example: "Metro BAN ATL 12345." (customer)
Option 1 IXC (national circuits)require an F&E Provisioning BAN number. Example: "F&E BAN is 22222."
Option 2 IXC (national circuits)require a COMS provisioning BAN number. Example: "COMS BAN is 9999999."
EPL, EVPL, WAVErequire an F&E Provisioning BAN number.
PIP, IDA, Data Center Collocation, ISDN
If you do not know your Verizon Partner Solutions account number, please contact your Sales Account Representative for assistance.
-
- Q : What is the difference between Option 1 IXC and Option 2 IXC and MPL?
-
A : Option 1 IXC - National (or interLATA) circuits traverse the former WorldCom network. Circuits are provisioned under an F&E BAN number.
Option 2 IXC - National (or interLATA) circuits traverse the former MCI network. Circuits are provisioned under a COMS BAN number.
MPL - Metro Private Line (intraLATA) circuits traverse the former MCI Local, MFS, Brooks networks. Circuits are provisioned under city-specific BAN number.
-
- Q : What is the difference between Type 1, 2, and 3?
-
A : Type 1 is on-net to the fVzB network. Type 2 is on-net to the fVzB on one end, and on-net to the fVzT on the other end. Type 3 is off-net to all Verizon networks.
-
- Q : When will I be given my Firm Order Commitment (FOC) or Due Date?
- Product FAQs
- Basic EVPL Questions
- Q : Does EVPL provide Point-to-Multipoint Service?
-
A : Yes, in addition to Point-to-Point service, EVPL can provide Point-to-Multipoint service. This is accomplished by establishing a Hub with a Service Multiplexed UNI which then would have EVCs/Flows connecting to the remote locations. On the Hub side, each EVC is distinguished by a distinct Virtual Local Area Network (VLAN) Tag.
-
- Q :What is the difference between the UNI/Handoff, Ethernet Access and the EVC or flow? What are the general guidelines?
-
A : UNI (User Network Interface) or Handoff refers to the physical connection between the customer's premise equipment and Verizon provided equipment (BEAS/NID). Ethernet Access provides connectivity from the customer location, through the UNI and underlying facilities, to the Verizon EVPL "Cloud". EVC (Ethernet Virtual Circuit) or Flow connects two locations through the "Cloud".
The UNI/Handoff must be equal to or greater than the Ethernet Access and the Ethernet Access must be greater or equal to the sum of all EVCs/Flow provisioned to that location.
-
- Q : Does the Ethernet Access at connecting locations have to be equal?
-
A : No. As long as the Ethernet Access at each end supports the connecting EVC (or the sum of connecting EVCs) for that location, they do not have to be equal.
-
- Q : Can there be multiple VLAN tags per EVC/Flow?
-
A : No. Each EVC must have a distinct VLAN tag.
-
- Q : Does EVPL have CoS?
-
A : Yes, EVPL currently has a single Class of Service: Premium Data/Real Time RT
-
- Q : Does EVPL have any mileage limitations?
-
A : No.
-
- Q : Does EVPL support Q-in-Q Stacking or Tunneling?
-
A : Yes. EVPL supports 802.1 Q VLAN tag stacking.
-
- Q : When establishing an EVC, can the customer assign the VLAN?
-
A : Yes. Customers can assign their own VLAN tag (i.e., from 02 to 4090) when ordering an EVC. If a customer does not specify a VLAN tag for a Tagged EVC, Verizon will assign an appropriate Tag to distinguish the EVC/Flow.
-
- Q : What are the rate elements for EVPL service?
-
A :The basic billable items for EVPL are:
- Ethernet Access at location A
- Ethernet Access at location Z
- EVC/Flow connecting the two locations
-
- Q : What are the EVPL bandwidth steps?
-
A : The standard EVPL speeds are as follows:
1 , 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100, 150, 200, 300, 400, 500, 600, 700, 800, 900, 1,000 Mbps
Note: EVC speeds greater than 1Gbps are available in the Continental U.S. on an individual case basis, in select markets.
-
- Q : Is the EVPL MEF certified?
-
A : Yes, EVPL is MEF 14 certified.
-
- Q : Does EVPL provide Point-to-Multipoint Service?
- Access
- Q : A customer is looking for a 1 Gbps EVPL circuit from Boca Raton FL to Atlanta, GA that avoids 50 NE 9th Street in Miami, FL. This is not a diversity issue since they don't have a secondary circuit that must be diverse from, it's a routing issue. Is there a process to follow that delivers a design that will meet the customer's requirement?
-
A : The product used would be EVPL National. This would not be a diversity request, but would be a request for location avoidance. Because the design is highly specific, a customer would work with their Sales Account Team to initiate an individual case basis review for engagement of the appropriate Verizon stakeholders to determine if the network design request can be supported.
-
- Q : The new EVPL Service Level Agreement (SLA) distinguishes “Off-net” Premium and "Off-net" Standard, what's the difference between the two and when does one versus the other apply?
-
A : Type 2 and Type 4 Ethernet Access Service (Off-Net Premium ). The Ethernet connection at the customer-designated location is furnished via non-MCI Legacy Company facilities, and the Ethernet connection at the MCI Legacy Company IXC Point of Presence location is furnished via MCI Legacy Company Facilities. Non-MCI Legacy Company facilities use an Ethernet facility class and MCI Legacy Company facilities use either a TDM facility class or an Ethernet Facilities class. The connection provides a higher level of performance than Off-Net Standard Service
Type 3 Ethernet Access Service (Off-Net Premium). The Ethernet connection at the customer-designated location is furnished via non-MCI Legacy Company facilities, and the Ethernet connection at the MCI Legacy Company IXC Point of Presence location may or may not be furnished via MCI Legacy Company facilities. Facilities furnished by both MCI Legacy Company and non-MCI Legacy Company use Time Division Multiplexing (TDM) services as the facility class method.
Standard Ethernet Access Service (Off-Net Standard). The Ethernet connection at the customer-designated location is furnished via non-MCI Legacy Company facilities, and the Ethernet connection at the MCI Legacy Company IXC Point of Presence location is furnished via MCI Legacy Company Facilities. Non-MCI Legacy and MCI Legacy Company facilities use either a TDM facility class or an Ethernet Facilities class.
Off-Net Premium Access connection types provide a higher level of performance than Off-Net Standard Service.
-
- Q :When providing at 200Mbps EVPL circuit using Type 3 access, what is the underlying transport infrastructure used? OC-12 or 2xOC-3?
-
A : The access choice could be either 2xOC3s or an OC12. This would be determined by the Network Capacity Planning, Operations, and Service Delivery Teams working with the respective ILEC to secure the access. The table below represents general TDM transport to Ethernet bandwidth translation which can vary and is subject to change depending on infrastructure capacity at the time an order for service is placed:
Channels TDM Increment Bandwidth Mbps 672 DS3 1 672 DS3 2 672 DS3 3 672 DS3 4 672 DS3 5 672 DS3 6 672 DS3 7 672 DS3 8 672 DS3 9 672 DS3 10 672 DS3 20 672 DS3 30 672 DS3 40 2016 OC3 50 2016 OC3 60 2016 OC3 70 2016 OC3 80 2016 OC3 90 2016 OC3 100 2016 OC3 150 4032 2xOC3 200 4032 2xOC3 300 8064 OC12 400 8064 OC12 500 8064 OC12 600 16128 2xOC12 700 16128 2xOC12 800 16128 2xOC12 900 16128 2xOC12 1000 32256 OC48 700-1000
-
- Q : What are the "Access Convergence" business rules if a customer is in a fMCI Lit building (in-franchise) and ordering a 1 Gbps Ethernet Access (EA) for a 100Mbps PIP, EVPL, or IDE service; is it required to be delivered via Type 2 Access to the VzT TLS (SES) Metro network? Is there a limitation in Quality of Service (QoS) on an EVC or Flow throughput resulting from Connection Access Control (CAC) rules that would limit the port to 50% of Access (500Mbps)?
-
A : Access Convergence impacts Ethernet Access (EA) (in-franchise only) when ordering On-Net (Type 1). If VzT facilities are available, they will be used instead of VzB facilities. Service Delivery, is transpartent to the customer; an EA Type 1 circuit is ordered and billed. LPL: The fact that EA treatment under AC in-franchise is transparent to the Customer has less of an impact. The impact is on how Verizon internally treats the facilities in-franchise; the impact to Customers again is transparent resulting in On-net/Type 1 treatment from a pricing and ordering perspective.
EA Type 2 is not required but can be ordered if facilities exist to provide service. EA Type 2 is provided via "Off-net" Premium which supports the same high quality of performance as a Type 3, or Type 4 Ethernet Access connection. Associated CAC rules currently supports 50% throughput on an Access UNI.
-
- Q : Is a Service Availability Request (SAR) required for an existing EA Type 2 that a customer is seeking to upgrade from a 10Mbps to 50Mbps EVC which has an existing 100Mbps electrical hand off? Other than iNet/PER for 50Mbps EVC, is a SAR required?
-
A : A SAR is not required on an EA Type 2 upgrade as long as the UNI interface/handoff does not change in correspondence with associated Connection Access Control (CAC) business rules.
-
- Q : For Customer Terminating Equipment (CTE) or Building Ethernet Aggregation Systems (BEAS) with bundled T1 (nxT1) transport, are individual T1 outages detected and can a customer be notified of such an outage?
-
A : Older legacy CTE or BEAS equipment does not provide for this function, meaning no notification between the NID and a customer in detecting individual T1 outages. A customer would have to monitor the throughput on the service in determining whether there are packets being dropped or a service affecting impact as a result. If a trouble is detected, customers should contact Verizon. Further, newer CTE or NIDs can be configured to indicate and support shutting down the Access loop if one of the T1s fail.
-
- Q : For Customer Terminating Equipment (CTE) or Building Ethernet Aggregation Systems (BEAS) with bundled T1 (nxT1) transport, how is load sharing or load balancing across the T1's handled?
-
A : The traffic is striped across all T1s in the bundle.
-
- Q : A customer is ordering 300Mbps Type 2 Ethernet Access (EA) into the Terremark Culpeper facility (LATA 246). Single Mode Fiber (SMF) is required by Verizon Telecom (VzT) to deliver the service. What type of Customer Terminating Equipment (CTE) or Network Interface Device (NID) should a customer anticipate being installed to support the service order? Will it be one NID or two NIDs (one from VzT & one from VzB)?
-
A : Verizon is enhancing Type 2 Access features that will eventually support a single NID design for Type 2 in most applications. Currently, Type 2 supports a dual NID design with a VzT and VzB NID deployed to provide end to end visibility from a customer POP to and end user location.
-
- Q : Ethernet Access (EA) Diversity supports the following (UNI card, UNI device, L2 geographical switch) available at 50Mbps bandwidth or higher. Is Ethernet Access (EA) Diversity available sub-50Mbps speeds?
-
A : Ethernet Access (EA) Diversity under 50Mbps requires individual case basis (ICB) review by Verizon. A customer would work with their Account Team to initiate an ICB review for engagement of the appropriate Verizon stakeholders to determine if it can be supported.
Note: EA Diversity requests could be subject to backhaul charges depending on the location of the customer premises and the VzB network in place, in that market.
Regulatory review is not required. Ethernet Access coverage expansion under a Forborn product is supported under Carrier Management agreements established with LEC/CLEC/3rd party vendors to extend last mile reach back thorugh the Verizon Business CPA network. Subsequent pricing has been established and this Access Type for Ethernet (currently available in the Enterprise channel is on track to be brought to market in Wholesale 10/2012.
-
- Q : Can you confirm that Type 4 Ethernet Access (EA) pricing and service is now available in the upper Midwest / Ohio valley LEC region?
-
A : Type 4 Ethernet Access rates specific to this regional LEC territory is targeted for pricing and service availability in 4Q12.
-
- Q : A customer has 1Gbps Ethernet Access with a 250Mbps PIP port and the customer would like to add three Flows onto the Access; is it possible to oversubscribe the Flows, having one 250Mbps Flow, and two 10Mbps Flows on the Access?
-
A : There are two components to Ethernet Access:
- The UNI (Interface/Handoff); and
- The Ethernet Access Bandwidth across that UNI.
They are typically referred to as UNI/Bandwidth combinations, and not all combinations are offered with all EA configurations ("Types").
For example, if a customer has a 1Gbps UNI and 300Mbps of EA across that UNI, customer would have 300Mbps/1,000Mbps of EA.
The aggregate bandwidth of all the PIP Ports required across that bandwidth cannot exceed 300Mbps. A PIP Port of 250Mbps, a second PIP Port of 10Mbps, and yet a third PIP Port of 10Mbps could be supported as the aggregate bandwidth (270Mbps) as long as the aggregate does not exceed the 300Mbps of EA.
Sales and Marketing often times receives questions related to Industry Standards and Data Networking protocol capabilities offered with Verizon’s Ethernet product which we are attempting to address below. Other questions as it relates to MTU sizing specifically addresses product feature/functionality which isn't considered proprietary and is available for Customer consumption.
-
- Q : A customer is looking for a 1 Gbps EVPL circuit from Boca Raton FL to Atlanta, GA that avoids 50 NE 9th Street in Miami, FL. This is not a diversity issue since they don't have a secondary circuit that must be diverse from, it's a routing issue. Is there a process to follow that delivers a design that will meet the customer's requirement?
- Industry Standards & Data Networking Protocols
- Q : Does our EVPL service provide 802.1ag Fault Management? Is this some type of error detection notification?
-
A : This requires E-OAM Ethernet (Operations, Administration and Maintenance) standards support for error detection and fault management. This feature is currently not supported, although future product enhancements may support this feature.
-
- Q : Is fault propagation (i.e. if light is lost on one end, the failure is passed through the entire circuit and the light lasers are to be disabled on the light enabled end) supported for Layer 2 and Layer 3 Ethernet services? If available is it limited to a particular bandwidth?
-
A : Currently, fault propagation is not supported. There are future plans to enable this functionality as part of OAM Ethernet supportability. Customers may have the capability within their equipment to implement a solution. (For Example: Bi-directional forwarding detection (BFD); level 7 Ethernet OAM, Proprietary Cisco IPSLA protocols and standard BGP timers). The Verizon network will pass these protocols as viable customer solutions without changes to their traffic.
-
- Q : If a customer uses Layer 3 switches with EVPL Metro, can they use Layer 3 routing instead of Layer 2? Does Verizon provide a serial link interface at each end (For Example: Customer Site A and Customer Site B), with a point-to-point subnet using Verizon IP addresses?
-
A : EVPL Metro is a Layer 2 end-to-end service with standard Ethernet customer interfaces (10Mbps, 100Mbps, 1,000Mbps electrical and optical handoffs). EVPL does not interact with customer's IP traffic or Layer 3 routing information. Therefore, customers are free to pass any Layer 3 traffic over the physical Ethernet Access (EA) connections. It is worth noting that any IP addresses utilized would need to be provided by the customer, either out of their own public address pools or by using private addressing (e.g., RFC 1918 for IPv4). A separate consideration is that since EVPL is a Layer 2 network, a customer could utilize IPv6 , assuming the customer's end devices supported it and that was a customer requirement.
-
- Q : What is the largest MTU that a full rate GigE EVPL Metro (SES/TLS) Type 2 solution will support? Is an MTU size of 1600 supported as standard or is it on an ICB? If an ICB is required please advise as to the process ?
-
A : EVPL Metro (SES/TLS) Type 2 is capable of supporting Maximum Transmission Units (MTUs) up to 2,000 Bytes, including all VLAN tags. The 2,000 MTU is standard and does not require ICB processing. By comparison, EVPL Metro (Type 1) MTU is 1,522 as standard, and can support higher; i.e. 5,000 bytes, if required by a customer on an ICB. This means that a customer would work with their Account Team to initiate an ICB review for engagement of the appropriate Verizon stakeholders to provide support for the higher MTU requirements depending on customer interface/handoff. Once a determination for support is made, the customer specific requirements for higher MTU would also require notation on the customer service order.
-
- Q : Does our EVPL service provide 802.1ag Fault Management? Is this some type of error detection notification?
- Pricing
- Q : Can a single UNI be used for both EVPL Metro and EVPL National? If a customer has several locations, of which some will be categorized as intraLATA or Metro service, and some will be interLATA or National service, how is the UNI priced?
-
A : Yes, the UNI is Access and priced as Ethernet Access (EA), agnostic to Metro and National EVCs/Flows. Each EVC is priced as a Metro or National Service Type.
-
- Q : Do business rules for "Corridors" apply to EVPL Metro if one end requires Type 3 Access?
-
A : Yes, cross Lata Metro "Corridors" (where available) apply to EVPL Metro, regardless of Ethernet Access (EA) Type.
-
- Q : Can a single UNI be used for both EVPL Metro and EVPL National? If a customer has several locations, of which some will be categorized as intraLATA or Metro service, and some will be interLATA or National service, how is the UNI priced?
- Billing
- Q : Please explain billing Option 1, 2, 3, and 4?
-
A : Billing Options refer to Legacy MCI billing platforms established through years of mergers and acquisitions. The billing platform "Options" today can distinguish how product and service features are ordered and billed depending on service attributes built-in provisioning systems and linked to customer bill invoicing. Over time, Legacy MCI billing platforms, although varied, continue to evolve in following a migration path toward single source integrated billing in the future. Existing Legacy MCI billing systems/platforms are as follows:
[#- Option 1 : Legacy WorldCom network billed on IXPlus and previously on Facilities & Engineering (F&E). Now Option 1 data services are billed on Wholesale Invoicing Network (WIN) and can be billed on Global Communications Services (GCS) for some IPS services.
- Option 2 : Legacy MCI network billing supported on Integrated Billing and Reporting Solution (IBRS) with future planned migration to a single platform, Prime Biller.
- Option 3 : Legacy MCI network billing on Integrated Billing and Reporting Solution (IBRS) blended into Option 2 with the exception of the VNet product.
- Option 4 : Legacy UUNET network billed on Integrated Billing and Reporting Solution (IBRS).
Option 1 : Legacy WorldCom network billed on IXPlus and previously on Facilities & Engineering (F&E). Now Option 1 data services are billed on Wholesale Invoicing Network (WIN) and can be billed on Global Communications Services (GCS) for some IPS services.
Option 2 : Legacy MCI network billing supported on Integrated Billing and Reporting Solution (IBRS) with future planned migration to a single platform, Prime Biller.
Option 3 : Legacy MCI network billing on Integrated Billing and Reporting Solution (IBRS) blended into Option 2 with the exception of the VNet product.
Option 4 : Legacy UUNET network billed on Integrated Billing and Reporting Solution (IBRS).
-
- Q : What is the process to set up a customer account for Option 1 or Option 2 billing? Does a Corp ID need to be established for a customer contract, or is there some other customer ID required?
-
A : The Customer Account Set-up process can differ based on existing customer contract, as well as products and services that are or are not outlined under their respective agreement. Many services do originate in different ordering systems and as a result, bill on Option 2 / Integrated Billing and Reporting Solution (IBRS). (For Example: EA Type IV, EA Standard, and EVPL International Access and Service Level Order Types). Customer Account Set-up require establishment of customer Corp ID, T-Corp, RevLoc, and COMS Bill IDs. Billing platforms such as Option 1 / Wholesale Invoicing Network (WIN), require Customer Account Set-up for Facilities & Engineering (F&E) Billing Account Numbers (BANs) to support ordering and billing of Ethernet-based products and services.
-
- Q : Please explain billing Option 1, 2, 3, and 4?
- Methods & Procedures (M&Ps)
- Q : A customer has an existing GigE EVPL between Connecticut and Maryland. Both locations are Type 1 Lit facilities. The customer is moving the Maryland office to a building that is "Non-Lit". What is the process to move this circuit?
-
A : Customer should reference business rules for supporting Move, Add, Change, Disconnect (MACD) orders. Under this example, a customer should submit a disconnect order and issue a new order for service. Moving a circuit end point from a "Lit Building" to a "Non-Lit Building" is subject to re-pricing and constitutes a change in Access service type.
-
- Q : A customer with a 40Mbps EVPL point-to-point service is possibly seeking to upgrade to a higher bandwidth. The customer would like to have pricing for 50Mbps, 60Mbps and 70Mbps. What options exists?
-
A : EVPL can support the customer requirement for upgrade to 50Mbps, 60Mbps or 70Mbps service. Please refer to the Partner Solutions Pricing (GWP) User Guide and tools for support.
-
- Q : A customer has an existing GigE EVPL between Connecticut and Maryland. Both locations are Type 1 Lit facilities. The customer is moving the Maryland office to a building that is "Non-Lit". What is the process to move this circuit?
- Product-Related
- Q : Can a customer over subscribe their EVPL CPA network? A customer wants to terminate 2 EVCs/Flows into the same host location at 100Mbps each, but currently, only has a 100Mbps E-UNI. This can be supported with EVPL SES/TLS service, but not sure about EVPL on the Converged Packet Architecture (CPA) network?
-
A : EVPL on the CPA network does not support over subscription. The total EVCs cannot exceed the bandwidth of the EA/UNI. The CPA packets are treated as Real Time/Premium Data traffic; therefore, each EVC and UNI cannot exceed ordered bandwidth.
-
- Q : Can EVPL support a 2.5Gbps EVC long haul or InterLATA?. Customer requirements for 2.5Gbps EVC connecting Type 1/on-net sites with 10Gbps DWDM local loops for Ethernet Access (EA)
-
A : From an Ethernet Access (EA) perspective, a 2.5Gbps EVPL EVC/Flow would be subject to an individual case basis review by Verizon. This means that a customer would work with their Account Team to initiate an ICB review for engagement of the appropriate Verizon stakeholders to provide support for the higher speed EVC including, Sales submission of iNetInquiry/Pre-Engineering Request (PER) to validate capacity for 10Gbps Access and Layer 2 capacity to support 2.5Gbps EVC/Flow.
-
- Q : Is it possible to have different Access UNI handoffs at each end of an EVPL EVC/Flow; for example, a GigE UNI handoff at the POP/Host end (Location A) and a FastE connection at the far end (Location Z) supporting a 20Mbps EVPL EVC?
-
A : From a technical perspective yes. However, there are some limitations on Ethernet Access (EA) UNI to Bandwidth combinations by Access Type. Please refer to the Ethernet Access (EA) UNI Interface Handoff Matrix tab on the Ethernet Access (EA) Data Gathering Form (DGF) for details.
-
- Q : Is traffic shaping business rules applicable on EVPL within the Converged Packet Architecture (CPA) network or at the Layer 2 switches? Some customers have this requirement, or at a minimum need to understand whether the Ethernet Service Provider (ESP) applies traffic shaping business rules and how are they defined?
-
A : EVPL traffic is policed on ingress to the CPA network supporting Committed Information Rate (CIR), guaranteed bandwidth or throughput with some limited burst capability Excess Information Rate (EIR), EVPL packets receiving the highest priority queuing in the CPA network with all traffic treated in a Real Time/Premium Data tier. There are no additional traffic shaping points specific to EVPL, as the service is designed and provisioned to emulate ordinary private line service to significantly reduce the likelihood of packets being dropped.
-
- Q : Does EVPL share the same MPLS backbone infrastructure with Private or Public IP services?
-
A : Sometimes referred to as the MPLS backbone or the CPA core network, both support the EVPL, PIP, and IDE services, with Layer 2 switching (L2S) specifically supporting EVPL. Devices that provide Label Switching Routing (LSR) functions are sometimes referred to as an MPLS switch. A MPLS switch can be considered a logical function that can reside in a stand-alone device or can co-exist with other functions (Layer 2 Switch/Aggregator) in a common device.
-
- Q : How would a customer order EVPL-Metro as a point-to-multipoint solution? Customer has four (4) remote sites going into one (1) hub site for aggregation of Ethernet traffic and requires four (4) EVC/flows at the Ethernet aggregation UNI/Hub.
-
A : Customer must define Ethernet Access (EA) UNI requirements for each site or end point in the point-to-multipoint design. Customer must then create or request Verizon to assign four (4) EVPL EVCs/Flows for slotting/mapping back to the customer POP/Host location in order to aggregation each remote site. The POP side Hub arrangement must be ordered and configured as a Service Multiplexed UNI, while the remote EA UNIs or Spoke end points can be ordered and configured as Service Multiplexed or All- to-One Bundling UNIs depending on whether the customer requirements are for Tagged, Transparent, or Compound EVPL EVCs/Flows:
Tagged: If the EVPL EVC/Flow Type is selected as "Tagged" then both of the associated EA UNIs must be configured as "Service Multiplexed" on the Ethernet Access (EA).
Transparent: If the EVPL EVC/Flow Type is selected as "Transparent" then both of the associated EA UNIs must be configured as "All- to-One Bundled" on the Ethernet Access (EA). An All-to-One Bundled EA UNI can only support a single EVPL EVC/Flow associated to it.
Compound: If the EVPL EVC/Flow Type is selected as "Compound" then one of the associated EA UNIs must be configured as "Service Multiplexed" (customer POP/Host side) and the other must be configured as "All- to-One Bundled" on the Ethernet Access.
-
- Q : Does Verizon EVPL support jumbo frames with MTU to 9,000 bytes?
-
A : Possibly, as it depends upon Access and Interface speed requirements and would be subject to individual case basis review by Verizon.
-
- Q : Does the EVPL product have inherent or included Circuit protection in the CPA core network? Customer requirements for a Sydney to New York EVPL circuit supporting circuit protection and failover.
-
A : The answer is yes. Verizon's CPA network supports circuit restoration. If a failure in the network is detected and potentially impacts an EVPL EVC/Flow; Fast Re-route protocols allow for another route to determine the EVPL/Flow traffic is switched to it. Fast Re-route is configured for Path and Nodal protection. Re-optimization timers cycle through the network and uses Open Shortest Path First - Traffic Engineering (OSPF-TE) and Resource Reservation Protocol - Traffic Engineering (RSVP-TE) to verify that each Label Switched Path (LSP) is on the most efficient path. If a shorter path is available, a new Label Switched Path (LSP) is signaled and the Pseudowire bridges are moved to the shorter route using a make-before-break logic.
-
- Q : If a customer has ONLY two sites with EVPL service supporting All-To-One Bundled UNIs at each end and a single Transparent EVPL EVC/Flow, is this any different than a Switched Ethernet Service (SES) Transparent LAN service (TLS) Tunneled Access solution? Can the EVPL service be terminated in a customer Layer 2 switch at each site to form a single broadcast domain (L2CP are "tunneled")?
-
A : Yes, that is correct.
EVPL Transparent EVC with All-to-One Bundled UNIs on both Ethernet Access circuits will transmit Tagged and Untagged Ethernet Frames.
EVPL Transparent EVCs will tunnel Layer 2 Control Protocols (L2CPs):
L2CP Flow/EVC Tagged
UNI - Service MultiplexedFlow/EVC Transparent
UNI - All to one BundlingSpanning Tree Protocol (STP)
Rapid Spanning Tree Protocol (RSTP)
Multiple Spanning Tree Protocol (MSTP)Discard Tunnel PAUSE (802.3x) Discard Discard Link Aggregation Control Protocol (LACP) Discard Tunnel All LANs Bridge Management Group Block of Protocols with destination MAC address 0x0180c2000010 Discard Tunnel Generic Attribute Registration Protocol (GARP) Block of Protocols with destination MAC addresses 0x0180c2000020 through 0x0180c200002f Discard Tunnel
-
- Q : Is EVPL International (EVPL-I) available today from the U.S. to Mexico? If not, what is the target date? Will Verizon have CPA nodes in Mexico? If so, how many and where?
-
A : Infrastructure is in place to support EVPL service into Mexico. Nodes exist in Mexico City and Monterrey. Verizon Partner Solutions has planned new market expansion of EVPL service into Mexico by late 2012 or early 2013.
-
- Q : Does Verizon Partner Solutions have plans to expand the EVPL service into Canadian markets? Can you provide an update or status? Additionally is budgetary pricing available, prior to the formal Partner Solutions launch?
-
A : Infrastructure is in place to support EVPL service into Canada. Nodes exist in Montreal, Toronto, and Vancouver. Verizon Partner Solutions has planned new market expansion of EVPL service into Canada by late 2012 or early 2013. Pre-positioning of EVPL-I quoting prior to launch into Canada is now available.
-
- Q : Can a customer over subscribe their EVPL CPA network? A customer wants to terminate 2 EVCs/Flows into the same host location at 100Mbps each, but currently, only has a 100Mbps E-UNI. This can be supported with EVPL SES/TLS service, but not sure about EVPL on the Converged Packet Architecture (CPA) network?
- Service Level Agreement (SLA)
- Q : Can a customer request projected Latency numbers for proposed EVPL National solution? Is there a tool that provides that information today?
-
A : Latency estimates, e.g., Round Trip Delay (RTD), for EVPL can vary by geographic region and/or international city pairs. CPA Network Roundtrip transit delay service level objectives are calculated as a provider edge PE-to-PE monthly average round trip transit delay in milliseconds between respective Provider Edge device pairs on the Verizon CPA Network. RTD is determined by measuring transit delay in milliseconds across the Verizon EVPL Core Network and averaging the results over a 30 day period. The Round Trip Delay (RTD) average is generally 20ms or less where Metro configurations or shorter distances are concerned.
RTD delay over CPA is generally determined with a combination of city pairs; i.e. originating and terminating routes
Ethernet Virtual Private Line (EVPL) Performance Service Level Objectives (SLOs) are for reference purposes only, and are not offered under contractual obligation. Please consult your Verizon Account Team for more information.
-
- Q : Can a customer request projected Latency numbers for proposed EVPL National solution? Is there a tool that provides that information today?
- Basic EVPL Questions
- Service Delivery FAQs
- Q : What are the VZB SUPP intervals for each product type, for each service?
-
A : The shortest interval for a SUPP is 5 business days. The interval will depend upon the stage that the order is in.
-
- Q : When will I receive an FOC/OCD?
-
A : 10 business days, but Ethernet may have a longer interval.
-
- Q : Where do I send PRI request and what type of order form do I use to submit the request?
-
A : PRI orders are sent to Priority-Orders@verizon.com . See attached ISDN and Local Service Order forms.
-
- Q : How do I turn up my IDE/IDA circuit Hot Cut vs. Activation?
-
A : Per the IVUE website, if your order is ready for activation (ITEMS marked Admin Billable and/or Option2 is 599 Complete) then please call 1-866-829-9719 to be routed to a technician that can help you with the activation of Layer 3 services. If your order is a Hot cut or involves participation of other teams (including DTAC/BNE), then please submit IVUE requests to those respective groups.
-
- Q : How do I receive a valid LOA/CFA or DLR?
-
A : If the customer has direct contact with the Provisioning team, customer should ask the Provisioning team for a valid LOA, CFA, or DLR. If customer does not have direct contact with the Provisioning team, customer sould ask their Project Manager or Service Delivery team member for this information. Then the PM or SDS member would reach out to the Provisioning team to send this information to customer.
-
- Q : Are there shorter intervals for CDRs on expedited orders?
-
A : If the order is a customer-paid expedite, then the answer is yes. Your Project Manager or Service Delivery team member may be required to reach out to the CDR Manager to ensure the "Expedite" option is selected or approved.
-
- Q : What are the VZB SUPP intervals for each product type, for each service?