BTWEthernetTechnicalProductHandbookV3 1
BTWEthernetTechnicalProductHandbookV3 1
BTWEthernetTechnicalProductHandbookV3 1
BT WHOLESALE ETHERNET
PRODUCT HANDBOOK
A world class enabler of converged network solutions
Product Handbook Issue 3 April 2009
3 COMMERCIAL
4 PROVISION
4.8 Support
5 MAINTENANCE
5.4 Performance
6 TRAINING
7 BILLING
9 CONTACT INFORMATION
10 GLOSSARY OF TERMS
BT Wholesale Ethernet (BTW Ethernet) meets the requirements of customers looking to provide an Ethernet option with full
UK coverage for short, medium and long distance data applications. Future plans also involve connectivity to BT’s Global
Ethernet platform.
Since its launch in 2008, the geographic coverage has grown from the 106 Metro (EEA) nodes being enabled, to 604 total nodes
via deployment of Ethernet Edge Switches (EES). Additional nodes will be deployed through subsequent rollouts (as detailed in
the 21CN Data Sets available from www.btwholesale.com. Click on Applications then Networks and enter the NIPP area). The
ultimate aim is to have full geographical availability with the vision of ‘any time, any place, anywhere’.
The service provides transparent, symmetrical, un-contended or contended (at 5:1) bandwidth between two Ethernet ports in a
point-to-point, point-to-multipoint or meshed configuration. It is a flexible bandwidth, connection-oriented Ethernet data
service enabling customers to link two or more of their sites together across the UK for data applications at defined ‘Etherflow’
bandwidths from 1Mbit/s through to 1Gbit/s and ‘Etherway’ fibre access speeds of 10Mbit/s, 100Mbit/s and 1000Mbit/s.
‘Etherway Copper’ access speeds range from 1Mbit/s to 10Mbit/s.
A resilient access option, Etherway Protected 1, between the BT serving node and the customer NTE (single interface
presentation) can also be provided for both 100Mb and 1000Mb access speeds at an additional cost.
Further enhancements will include 10Gb Etherway access speeds and Etherway Protected 2 based upon Openreach RO2
offering.
BTW Ethernet will be engineered for an end-to-end target availability of 99.93% a maximum one way latency of <10ms, a
maximum jitter of <3ms, and will come with a maintenance package within tariff and be subject to BT standard terms and
conditions for BTW Ethernet.
The core network will be engineered to meet the availability and Quality of Service (QoS) targets defined using automatic re-
routing on failure as required. The target end-to-end availability for BTW Ethernet using Etherway Protected access is 99.97%.
Each BTW Ethernet service will consist of two local access ends and a core link between BT nodes where required. A Service
Reference will be used to identify each component including the customer’s end-to-end Ethernet Virtual connection.
The number of remote sites connected to a single aggregate presented site will be limited for practical reasons to 120
connections for 10BaseT and FE (100Mb) access and 400 sites for Gigabit Ethernet fibre access and interface
presentation. Up to 10,000 components can be allocated to any single network structure. A component is considered to
be an Etherway or Etherflow.
‣ Support for the following order types at launch: provide and cease.
‣ Etherflow customers will have the ability to cancel orders or amend certain attributes, e.g. contact name or bandwidth.
Improved functionality is planned for future releases.
‣ Support for port-to-port, port-to-VLAN and VLAN to VLAN connections
BTW Ethernet is available across the UK and Northern Ireland with the exception of Kingston upon Hull, Isle of Man, Isles of
Scilly and the Channel Isles.
BTW Ethernet will be offered as ‘subject to survey’ and excess construction charges will apply where appropriate.
Stand-by power (battery back-up) is not available for BTW Ethernet; the customer can use their own UPS if desired.
The switching of customer traffic into these Ethernet Virtual connections will be based upon SVLANs applied by the customer.
A full or partial mesh of Ethernet Virtual connections will be possible as outlined in section 2.6.4.
Where a customer access only requires a single Ethernet Virtual connection (i.e. connectivity to a single destination), it is
possible to map the entire port into a Ethernet Virtual connection so that the customer does not have to apply SVLANs to traffic
from that site.
The minimum frame size is 64 bytes and the maximum is 1548 Bytes, anything outside of this range will be discarded leading to
data loss. Ability to accept frame sizes above 1548 Bytes will be available in a future release.
There is a published list of Layer 2 protocols which are tunnelled end to end, as detailed in SIN476 which can be located at
www.sinet.bt.com
Link Loss Forwarding (line monitoring) is available for 10Mbit/s, 100Mbit/s Access, as default, and 1000Mbit/s Access currently
using C1/C2 auto negotiate to signal this. This facility is not available for Etherway Copper access.
Depending on the physical interface presented to the customer, the following restrictions will be enforced for the number of
connections supported by the physical interface within the overall 400 site limit:
‣ 120 connections – this is offered the 10BaseT interface option.
‣ 120 connections – this is offered the 100BaseT interface option.
‣ 400 connections - this is offered on the 1000Base-SX and 1000Base-LX interface options.
It is possible to provide any combination of bandwidth sizes up to a maximum of 400 Ethernet Virtual connections on a single
access link.
Meshed service The service will use VLAN mapping on the Ethernet Switch.
Point-to-Point service The service will use port mapping on the Ethernet switch.
The customer in this case will not need to apply VLAN tags.
Point-to-Multipoint service The service will use a combination of Port and VLAN
mapping on the Ethernet Switch.
It should also be noted that switching based on MAC learning is initially not supported.
2.5 Access
The customer will be offered an access based on two components:
The maximum radial distance for the Etherway fibre access is 25km, extending to 35Km for 1000Mb access.
A resilient access option, Etherway Protected, between the BT serving node and the customer NTE (single interface
presentation) can also be provided for both 100Mb and 1000Mb fibre access speeds at an additional cost.
Etherway Copper is currently limited to the exchange area where the serving Wholesale Ethernet node is situated. Where
Etherway Copper is requested within these areas, BTW will determine the number of Openreach MPF required to meet the
required bandwidth at the customer site. The number of MPF required will vary depending on the distance from the customer
site to the serving node and the bandwidth required. A maximum of 8 MPF can be used to provide Etherway Copper, as a result
it may only be possible to provide limited bandwidth at some customer sites and occasionally it may not be possible to provide it
all together.
The number of MPF required for Etherway Copper will be determined from line characteristics obtained from Openreach
sufficient MPF will then be ordered to meet the required bandwidth. It is recognised that line characteristics vary in practice
and so the number of MPF is designed to ensure that the required bandwidth is met. The bandwidth will also be checked prior
to handover.
Multipoint
- sites
Connected using 10, 100 or 1000Mbit/s fibre access (WES) or
1-10Mbit/s Etherway Copper access. CPE must apply VLANs
2 Hub sites
to route traffic to Hub
Connected using 10, 100 or 1000M Access
CPE applies VLANs to determine destination Core
Product Handbook
Option of fibre resilience with
100 & 1000m access
Ethernet Virtual connections across core
Customer Sites
Connected using 10, 100 or 1000Mbit/s fibre access or 1-10Mbit/s Etherway Copper
CPE not required to apply VLANs to determine destination
Core
Note: Spokes may also be connected using 10Mbit/s fibre access or 1-10Mbit/s Etherway Copper acces
Note: Spokes may also be connected using 10Mbit/s fibre access or 1-10Mbit/s Etherway Copper access.
2.6.4
2.6.4Customer Network
Customer (Ethernet
Network Virtual
(Ethernet Connection)
Virtual Topologies
Connection) Topologies
The following
The diagram
following illustrates
diagram some of the
illustrates possible
some of theEthernet VirtualEthernet
possible connectionVirtual
topologies which a customer
connection couldwhich
topologies requesta
customer
between could
5 sites (a, b,request
c, d, andbetween 5 sitesshows
e). The diagram (a, b,connectivity
c, d, and across
e). Thethediagram shows
core network connectivity
between across
the customer theoncore
ports the
network between the customer ports on the
Ethernet Switches. Customer access circuits are not shown. Ethernet Switches. Customer access circuits are not shown.
a c a c a
1 2 3
e d
b b b
a c a c a c
4 5 6
e d e d e d
Point-to-Multipoint (hub & spoke) Full Mesh Partial Mesh
Customers are not expected to order a specific type of topology, instead it is likely that they will order their
accesses and Ethernet Virtual connections independently. Accesses should be ordered with consideration
Customers are not expected to order a specific type of topology, instead it is likely that they will order their
to required topology (i.e. the order should specify port or VLAN mapping) and then Ethernet Virtual
connections
accesses will Virtual
and Ethernet then be orderedindependently.
connections to provide the required
Accesses shouldtopology.
be orderedCustomers can order
with consideration subsequent
to required topology
accesses and Ethernet Virtual connections at any time.
(i.e. the order should specify port or VLAN mapping) and then Ethernet Virtual connections will then be ordered to provide the
required topology. Customers can order subsequent accesses and Ethernet Virtual connections at any time.
Topology 2 Both sites need to be VLAN mapped, however there will not be a diverse route
between the two Ethernet Virtual end points.
© British Telecommunications plc 2008
Topology 2 Both sites need to be VLAN mapped, however there will not
be a diverse route between the two Ethernet Virtual end
points.
Topology 3 All sites could be port mapped, but where evolution to other
topologies is planned, consideration should be given
towards starting some sites as VLAN mapped.
Topology 4 Site ‘a’ needs to be VLAN mapped. Other sites could be port
mapped, but where evolution to other topologies is planned,
consideration should be given towards starting some sites as
VLAN mapped. A maximum of 400 sites could be included
in this topology.
Topology 6 Sites ‘a’, ‘b’,and ‘d’ need to be VLAN mapped. Sites ‘c’ and
‘e’ could be port mapped, but where evolution to other
topologies is planned, consideration should be given
towards starting some sites as VLAN mapped. A maximum
of 400 sites could be included in this topology.
The VLAN IDs valid for use over BTW Ethernet are in the range1 to 4095. The customer may allocate their own VLANs or have BT
2.6.5 VLAN configuration guidance
apply them as part of the order journey.
The VLAN ID is valid for use over BTW Ethernet are in the range1 to 4095. The customer may alloc
The VLAN IDs are locally significant;
ownthere
VLANsis no relationship
or have BT applybetween the of
them as part VLAN IDs used
the order at either end of an Etherflow
journey.
connection. Therefore in a Hub and Spoke topology all spokes can use the same VLAN ID so long as different ones are used at
the hub end, as shown in the diagramThe VLAN IDs are locally significant; there is no relationship between the VLAN IDs used at either e
below.
Etherflow connection. Therefore in a Hub and Spoke topology all spokes can use the same VLAN ID
long as different ones are used at the hub end, as shown in the diagram below.
100
100
101 100
102
103 100
Product Handbook
101
The same VLAN ID cannot be used on any one port (Etherway access circuit). The VLAN IDs, shown in red below, are invalid as
they are duplications on the same port.
102
103 100
100
3 COMMERCIAL
BTW Ethernet is available to BT Wholesale customers only.
BTW customers must have signed the terms and conditions for BTW Ethernet.
BTW customers should address any queries regarding the BTW Ethernet terms and
nominated BT Commercial or Account Manager in the first instance.
3. COMMERCIAL
BTW Ethernet is available to BT Wholesale customers only.
BTW customers must have signed the terms and conditions for BTW Ethernet.
BTW customers should address any queries regarding the BTW Ethernet terms and conditions to their nominated BT Commercial
or Account Manager in the first instance.
The customer will specify the access speed and interface type required at each site and the Ethernet Virtual connection
bandwidth required between the two sites.
For fibre, pricing is dependent on access speed required and radial distance from the BT Network entry point. The radial distance
from the customer site to the node is calculated on a per km (rounded up) rental charge.
For “Etherway Copper”, the price will depend on the number of MPF required to provide the required bandwidth. Etherway
Copper is only available in exchange areas containing a serving node and so no additional radial distance charge is applicable.
Each local end will incur Connection and Annual Rental charges.
The radial distance from the customer site to the node is calculated on a per km (rounded up) rental charge for fibre based
delivery, and upon volume of copper pairs consumed for Etherway Copper.
Once an Etherflow bandwidth upgrade has been completed there will be a minimum 1-month period during which no further
downgrade to that same Etherflow will be allowed.
Each BTW Etherway order is subject to a 12 month minimum period from when the service is delivered.
Upgrades from Standard to Premium contention service will be available in a future release.
100Mbit/s 5 -9 50%
4 PROVISION
In order for BT to accept and progress orders, the customer must provide all relevant information; customer details, fibre access
Product Handbook
and Ethernet Virtual connection bandwidth requirements including existing connection IDs.
It is the customer’s responsibility to ensure accuracy of the CRF and keep End Users informed of progress.
1 3 10 16 30 35 40 45 50 55 60
Day 57
Auto KCIs are shown in blue
These KCIs can happen at any time - C11, C13, C16, C17, C18
The ‘C’ codes are internal BT refences and will not appear on the customer KCIs.
The ‘C’ codes are internal BT refences and will not appear on the customer KCIs.
For Etherway Copper delivery the following table represents the KCI timeline.
ETHCxxxxxx
ETHAxxxxxx ETHAyyyyyy
21CN
ETHNxxxxxx
BTWExxxxxx BTWEyyyyyy
Lead Time
(working days)
Lead Time
(working days)
Standard lead-times will not apply by default to large orders (those containing >10 Etherway access circuits). Such orders will be
project managed and delivery dates will be agreed independently with the customer. Where planning activity confirms that
standard lead times are feasible, the business rules should allow them to be applied to the orders at this stage.
The new proposal addresses the objectives of forecasting on two fronts; it provides BTW customers the opportunity to declare
anticipated order volumes and it provides BT with information so that it can aim to deliver Ethernet Virtual connections to
Contractual Delivery Date (CDD).
The forecast must be submitted on the Forecasting Submission Form, which is available online. You can submit this
via your Account Team.
‣ BTW customers are requested to provide a 12 month forecast which is to be updated on a quarterly basis.
‣ The first 3 months forecast is fixed at the time of submission and must be as accurate as possible.
‣ The remaining 9 months forecast is to be indicative. Volumes can be amended without cost on the next forecast submission.
‣ The forecast submission dates are fixed and are irrespective of when the BTW customer sign the BTW Ethernet standard
terms and conditions contract.
‣ New customers will be required to submit a forecast on the next due forecast date shown above.
‣ Openreach may use BTW customer forecasts to assess the forecast accuracy against actual sales over the period.
4.8 Support
Any unresolved technical queries and other reports of provisioning difficulties should be directed to the 21CN Data Services
Team in the first instance.
5. MAINTENANCE
A maintenance package will apply to BTW Ethernet services within tariff and provides the description and terms and
conditions of the repair service offering fault repair work carried out during 24 hours per day, 7 days per week including
public/bank holidays.
The 21CN Data Services Team will receive faults proven to BT network from the customer
‣ The 21CN Data Services Team will be responsible for logging the fault details and handling of faults on the BT network and
will be responsible for fault clearance notifications.
‣ A Manual Back-up is also available via the 21CN Data Services Team on 0800 0323 888, however, this method should only
be used when the portal is not available.
5.4 Performance
Access Type
10M Standard (inc 100M Standard 1000M Standard 100M ETHERWAY 1000M ETHERWAY
Etherway Copper) PROTECTED PROTECTED
Standard traffic will be dropped first and therefore has no latency target.
5.6.1 Introduction
Planned Engineering Works is a known programme of network engineering work within BT’s control.
BT will inform the customer of any foreseen work it finds necessary to carry out within its own network which may affect the
BTW Ethernet service or standards of performance as perceived by the customer. The request for deferment of a planned outage
by the customer will be subject to negotiation and agreement with each case considered on its own merits.
5.6.2 Notification
BT’s notification contact points are identified in the Customer Service Plan (CSP). The method to be used and target timescales
will be discussed, and documented if required, between the BT Customer Relationship Manager (CRM) and the customer.
5.6.3 Timescales
Timescales for notifying the customer of work on transmission line plant, which will have a direct bearing on the perceived
performance of BTW Ethernet, is a minimum of 3 working days.
a) Change over from MAIN to STANDBY working by the use of high speed switching equipment.
b) Momentary Interruptions (MI), which may be of maximum duration of 1 minute during ‘preferred’ hours
c) Out of service interruptions. Where it is necessary to carry out work and where a ‘make good’ route does not exist a
‘Scheduled Outage’ will be necessary.
If the customer is unable to agree to the interruption to service, they must promptly contact BT to discuss and agree an
alternative date and time.
If interruption of service cannot be agreed, BT will contact the relevant escalation contact point. The escalation contact points
for both BT and the customer will be identical to those identified for resolving BTW Ethernet escalations (see CSP).
Unless advised otherwise BT, the customer should assume that the work has been completed as planned; appropriate checks
should be made by the customer before attempting to resume service.
BT’s preferred hours for planned works is after 00:00 hrs and before 06:00 hrs.
6 TRAINING
A training guide will be provided when the customer signs up for the service
7 BILLING
Monthly and quarterly billing is available; the customer will choose the preferred option when setting up their billing account.
For Quarterly billing BT’s billing cycle is April/July/October/January. Connection is charged in arrears and rental in advance.
Billing will be via the Geneva billing system used for BT Wholesale Products.
9 CONTACT INFORMATION
Enquires about BTW Ethernet should firstly be addressed to your BT Account Team or the client reception team on
0800 671 045.
Information about BTW Ethernet and BT Wholesale products and services is available from the BT Wholesale website available at
the following URL: www.btwholesale.com
10 GLOSSARY OF TERMS
BTW BT Wholesale
CP Communications Provider
FE Fast Ethernet
KCI Keeping Customers Informed – Customer reporting process for provision and repair progression.
MI Momentary Interruptions
eCo Plus BT’s Portal –provides order placement, tracking, fault reporting & tracking direct with the customer
SM BT Service Manager