Overview of Work
Impacted Services: DSL EFM EAD EoFTTC FTTC FTTP - OR
++++++++++++++++++++++++++++
Exchange Delivery Change-MPS-NGE Double Re-Peer Helium - WMSTO - STONE :: CRQ000000102557
Detailed Description of Request:
ANT - METRO -> COLLECTOR DOUBLE RE-PEER
To implement the new Helium Project there is a requirement to re-peer the Metro Exchange with the Collector (NGE). This work will impact services that have bene migrated onto the ANT Topology.
We will complete this by replacing the existing backhauls between the MPS's and NGE's with new Helium backhaul's which by design may terminate on the original NGE but may move to an alternative NGE. This is required to allow for further expansion and to balance the traffic at the collector locations. This also conforms to the correct Access Network Topology. If the Metro node is also a collector node then the backhaul may connect directly to a local NGE but could still be re-peered from NGE001 to NGE002 to complete the balancing requirement.
We will be impacted all migrated services; (1. PPP; 2. EAD; 3. EOFTTC 4. Multicast 5. EFM 6. Voice 7. Management) on the ANT Topology.
This work is required to balance the collector estate and allow room for further backhaul expansion as bandwidth demand increases.
Effective comms and planning will allow multiple resources to complete multiple services on the same night.
Customers should only a loss of resilience during the implementation window.
Affected Customer circuits will see multiple impacts as per the below within the change window as alternate legs are worked
For MPF and DSL customers who are forced to re-auth they will see an outage of 3 mins for PPP and up to 15 mins for FTTC/DHCP.
For EAD; EoFTTC and EFM customers; their outage would be a maximum of 300 milliseconds and therefore considered as non impact.
This work is either a backhaul replacement (Replacing EAD/EBD with a new Helium Route) or the addition of a new resilient backhaul (where a secondary didn't already exist) and in some instances involves an NGE re-peer; all of which are tasks that are completed regularly on the TT access network.
Due to the setup of the Access Network; all services will failover to the alternative path whilst the other Helium route is being configured and therefore this work will be loss of resiliency only.
Testing
This concept has been proven in a LAB environment
Live tests will be recording on test logs
R:\01 Projects\01. Projects Network Design Specialists\09. Gavin Ditchfield\1445247103_Access Network Topology\1445247103_6 Network Solution\02 NDD
Business Justification:
This migration activity is part of the overall Helium project and is necessary to deliver continuous and sustainable bandwidth growth across the TTT access network and is part of the wider network brilliance programme.Barlaston Eccleshall Stone
Overview of Work This work on this date has been cancelled, the engineering resource has had to be moved around. A new CRQ notice with the amended date will be sent out shortly. Impacted Services: DSL EFM EAD EoFTTC FTTC FTTP - OR ++++++++++++++++++++++++++++ Exchange Delivery Change-MPS-NGE Double Re-Peer Helium - WMSTO - STONE :: CRQ000000102557 Detailed Description of Request: ANT - METRO -> COLLECTOR DOUBLE RE-PEER To implement the new Helium Project there is a requirement to re-peer the Metro Exchange with the Collector (NGE). This work will impact services that have bene migrated onto the ANT Topology. We will complete this by replacing the existing backhauls between the MPS's and NGE's with new Helium backhaul's which by design may terminate on the original NGE but may move to an alternative NGE. This is required to allow for further expansion and to balance the traffic at the collector locations. This also conforms to the correct Access Network Topology. If the Metro node is also a collector node then the backhaul may connect directly to a local NGE but could still be re-peered from NGE001 to NGE002 to complete the balancing requirement. We will be impacted all migrated services; (1. PPP; 2. EAD; 3. EOFTTC 4. Multicast 5. EFM 6. Voice 7. Management) on the ANT Topology. This work is required to balance the collector estate and allow room for further backhaul expansion as bandwidth demand increases. Effective comms and planning will allow multiple resources to complete multiple services on the same night. Customers should only a loss of resilience during the implementation window. Affected Customer circuits will see multiple impacts as per the below within the change window as alternate legs are worked For MPF and DSL customers who are forced to re-auth they will see an outage of 3 mins for PPP and up to 15 mins for FTTC/DHCP. For EAD; EoFTTC and EFM customers; their outage would be a maximum of 300 milliseconds and therefore considered as non impact. This work is either a backhaul replacement (Replacing EAD/EBD with a new Helium Route) or the addition of a new resilient backhaul (where a secondary didn't already exist) and in some instances involves an NGE re-peer; all of which are tasks that are completed regularly on the TT access network. Due to the setup of the Access Network; all services will failover to the alternative path whilst the other Helium route is being configured and therefore this work will be loss of resiliency only. Testing This concept has been proven in a LAB environment Live tests will be recording on test logs R:\01 Projects\01. Projects Network Design Specialists\09. Gavin Ditchfield\1445247103_Access Network Topology\1445247103_6 Network Solution\02 NDD Business Justification: This migration activity is part of the overall Helium project and is necessary to deliver continuous and sustainable bandwidth growth across the TTT access network and is part of the wider network brilliance programme.