Move end user Customer
VLANs between Service
VLANs
ORC2M- 16603, Release 1800
We’ve made this change to enable you to manage your network and your customer connections in
an efficient and productive manner. For example, you could balance GEA services between GEA
Cablelinks and SVLANs when the traffic in these approaches a critical point that could adversely
affect your customers’ experience. This could improve your customers’ satisfaction and help you to
manage your network traffic.
How does it work?
There are two types of Virtual Local Area Network VLAN used with GEA services. A Customer VLAN
(CVLAN) is created when a service (e.g. Data or Voice) is provisioned for one of your customers. At this
point you may specify a particular Service VLAN (SVLAN) or no SVLAN in which the CVLAN is placed. You
can create new SVLANs by raising a Modify order against your GEA Cablelink product.
The new VLAN moves functionality will allow CP’s consuming FTTC/FTTP/FVA to raise a Modify order to
move your customer’s CVLAN to an SVLAN if they weren’t already allocated to an SVLAN or between
SVLANs if they were in an existing SVLAN. This may be carried out as long as the CVLAN is being moved
within or between GEA Cablelinks on the same Layer 2 Switch.
With this functionality, you can configure your GEA Cablelink to suit how you want to manage your network.
Figure 1 shows an example where a CP has decided to group all their data services into SVLAN 100 and all
their voice services into SVLAN 4096. One set of services will be routed to their data server and one to their
voice server.
Figure 1.
How could you use this?
You could separate customers by Quality of Service or Service Level Agreement enabling customer
service centres to prioritise groups of customers in the event of high bandwidth demand or network
failure.
When can you start to do this?
This is available now.
What do you have to do before you can use it?
You must own the source and target GEA Cablelinks which must both be on the same Layer 2
Switch. If you wish to use this new functionality via the Openreach B2B interface then you’ll need to
upgrade to the R1800 interface code. For CPs using the Openreach Portal no upgrade is required.
Please note:
The VLAN moves transaction is designed to support daily management activities not bulk
migration. Please notify us if you plan to place in excess of 300 VLAN move transactions per
day.
You cannot change the CVLAN identity
Want to know more?
Further information available at:
http://www.openreach.co.uk/orpg/customerzone/products/superfastfibreaccess/releasedocumentation/releasedocumentation.do
Note:
This information is accurate at the time of writing and may be subject to change.
Openreach will provide regular status communications to our customers as the delivery of our
releases progress, but we reserve the right to amend the scope, and dates of the release, if
necessary, which means that Openreach accepts no liability for planning undertaken by CPs.