DCNet & enterprise connections
Connections are circuits that are routed between two On Demand ports.
There are three different connection types:
- Ethernet connection between ports in data centres and enterprise buildings
- Cloud connection between a physical port in a data centre or enterprise building and a cloud port
- Internet connection that terminates on a physical port in a data centre or enterprise building
This section covers Ethernet connections.
On Demand ports can be dynamically configured to support either Ethernet Private Line (“point to point”) based on transparent handover or Ethernet Virtual Private Line “(hub and spoke”) services based on a VLAN handover.
EPL and EVPL are not treated as different service types in the On Demand platform, although the services are configured differently.
Ethernet Private Line
The Ethernet Private Line (“point to point”) topology is illustrated below.
Ethernet Virtual Private Line
Ethernet Virtual Private Line (“Hub and Spoke”), based on a VLAN handover at the A end and port based handover at the B end is shown below:
On Demand enables a variation of Ethernet Virtual Private Line, based on a VLAN handover at both the A end B ends – supporting a mesh topology.
On Demand connections support bandwidths between 10Mbps and 20Gbps. Higher bandwidths are available on request.
The below table shows the bandwidths that are supported.
Core port speeds (On Demand Flex and Traditional / Fixed pricing models)
||1/10/100Gbps ports – full rate port speeds (logical = physical) 100/400Mbps & 4/40Gbps ports - logical port speed < physical port speed|
Additional logical port speeds (fixed pricing model only)
|Connection||All locations: 10, 20, 50, 100, 200, 300, 400, 500Mbps, 1, 2, 3, 4, 5, 10Gbps Key data centres only: 20Gbps||Logical Ethernet circuit connection between 2 On Demand ports|
The supported bandwidth of an On Demand circuit connection is based on the bandwidth of the ports at the A and B end points. This applies to both fixed term and flexible contracts.
For point to point (EPL) services where the A end and B end port speeds are equal, the circuit connection bandwidth is based on bandwidth ranges that are related to the speed of both ports.
The table below shows the bandwidths that are supported for EPL configurations.
This is illustrated below:
For EVPL services the NNI bandwidth is higher than the port bandwidth at the customer site and under this scenario, the maximum circuit connection bandwidth is determined by the B end port speed. There is no restriction at the A end port configured as a VLAN based NNI aggregating multiple circuit connections.
For example, the supported bandwidth range for a circuit connection routed between a 10Gbps NNI and a 1Gbps B end port is 10Mbps-1Gbps (i.e. the range associated with the lower speed port).
Customers should note that these bandwidth ranges apply to Ethernet connections between two physical On Demand ports. There are no restrictions on cloud and internet access services.
Data centre & enterprise connections
Under the On Demand flex pricing model, circuit connections are based on 1 hour and 3/6/12/24/36 month commitments. Customers are charged a per hour rental based on the bandwidth and commitment.
Under the traditional/fixed pricing model, circuit connections are based on fixed 12/24/36 month contracts.
For further details, please refer to the pricing section.
Connections have three VLAN modes, which apply to each end of the circuit connection:
|Open port||1 circuit connection per port||Port based handover, all VLANs are passed transparently|
|Add VLAN||Multiple circuit connections per port (Colt adds VLAN tag)||VLAN based handover, 1 VLAN per Connection. VLAN added on egress, towards customer (in translation mode). VLAN can be S-VLAN (88a8) or C-VLAN (8100)|
|Filter VLAN||Multiple circuit connections per port (Colt filters VLAN tags)||VLAN filtered on ingress to Colt network (against a single VLAN number).|
The supported combinations are shown in the below table (A end and B ends can be used interchangeably).
|A-end||Open port||Add VLAN||Add VLAN||Add VLAN||Filter VLAN||B-end||Open port||Open port||Add VLAN||Filter VLAN||Filter VLAN|
|Description||Standard Ethernet Private Line (EPL) configuration||Ethernet Virtual Private Line (EVPL) configuration||Ethernet Virtual Private Line (EVPL), hub presentation at both ends (note 3)||Ethernet Virtual Private Line (EVPL) with VLAN filtering at spoke site||As per scenario 3 above, except VLAN IDs are preserved (same at each end)|
|Equivalent Colt service||Ethernet Line (EPL)||Ethernet Hub & Spoke||n/a||MEF Access EVPL||Ethernet Line (EVPL)|
|DCNet & Ethernet On Demand||Supported||Supported||Supported||Supported||Supported|
|DCNet & Ethernet On Demand||n/a||Supported (note 1)||Supported (note 1)||Supported (note 1)||n/a|
|AWS/IBM/Oracle||n/a||Supported (note 1)||Supported (note 1)||Supported (note 1)||n/a|
|AWS dedicated||Supported||Supported (note 2)||Supported (note 2)||Supported (note 2)||Supported|
- The cloud end is automatically configured as “add VLAN”
- Only 8100 CVLANs supported at AWS end
- Supports different VLAN at each end. VLAN PCP will not be preserved
- For further details on cloud VLAN configurations, please refer to the cloud connectivity section