News
Jan 2 |
[Cloud Ethernet] Maintenance window 17th January 2015
Posted by David Croft on 02 January 2015 11:13 PM |
Please be advised of the following maintenance window scheduled by Openreach: Date: Saturday, 17th January 2015 Start time: 20:00 GMT End time: 06:00 GMT Purpose: Openreach have advised us that they will be performing cable diversion on the 21CN circuit servicing our Interxion (CLBIS02) node ahead of future roadworks/building works. Services affected: Cloud Ethernet (All BT variants) terminating in our Interxion (CLBIS02) node. Impact: HIGH. There will be a interruption to all Cloud Ethernet services single-homed to our Interxion (CLBIS02) node during this window while the circuits are re-routed. Other services hosted in Interxion will not be affected, and resilient Cloud Ethernet services will not be affected. Comtec NOC is tracking this issue under ticket [#JQL-302-41577]. BT PEW ref PW246851. Regards, David Croft Read more » | |
Nov 19 |
[Core Network] Service Alert 19th November 2014 - Update 1
Posted by David Croft on 19 November 2014 10:45 PM |
This is an incident notification regarding Internet connectivity. Date: Wednesday, 19th November 2014 Start time: 14:50 GMT End time: 22:00 GMT Services affected: Internet access. Summary: The LONAP peering exchange experienced issues which had a knock-on effect on Internet connectivity across UK ISPs. We resolved the issue at the time by disabling our connections to LONAP, and have now restored them. Report: Due to an instability on the LONAP peering exchange causing packet loss and dropped sessions, we shut down our connections in order to reduce the impact to our customers. Traffic was routed via resilient alternate peering and transit routes and no further packet loss occurred. At 15:35 we were informed by LONAP that the issue was a result of high CPU across all switches caused by a large volume of multicast traffic from a reseller member port. The port was shut down and continues to be shut down until the member has demonstrated that they have resolved their issue. LONAP is continuing to investigate why port-security did not automatically shut down the affected port, however the exchange has been stable since that time. As it is our policy not to make non-emergency engineering changes during working hours, we did not re-establish our connections until 22:00 GMT. We are observing no continuing problems, although we will continue to monitor carefully. This is the final update. Comtec NOC was tracking this issue under ticket [#OTX-874-67976]. Regards, David Croft Read more » | |
Nov 19 |
[Core Network] Service Alert 19th November 2014
Posted by David Croft on 19 November 2014 03:22 PM |
This is an incident notification regarding Internet connectivity. Date: Wednesday, 19th November 2014 Start time: 14:50 GMT Services affected: Internet access. Summary: The LONAP peering exchange is experiencing issues which is having a knock-on effect on Internet connectivity across UK ISPs. Report: Due to an ongoing instability on the LONAP peering exchange causing packet loss and dropped sessions, we have shut down our connections in order to reduce the impact to our customers. Traffic will be routed via resilient alternate peering and transit routes. We will await an all-clear from LONAP before re-establishing connections overnight. Comtec NOC is tracking this issue under ticket [#OTX-874-67976]. Regards, David Croft Read more » | |
Oct 13 |
Christmas moratorium 2014-2015
Posted by David Croft on 13 October 2014 01:20 PM |
Please be advised of the following Christmas moratorium scheduled on our network. Start date: Monday, 15th December 2014 End date: Wednesday, 7th January 2015 Purpose: In line with industry best practice, we and our suppliers will be instituting our annual change freeze between these dates in order to protect customer services. Services affected: All. Impact: There will be an moratorium on changes across our network during this period. Provision activities may be delayed and lead times will be impacted if they fall within or after this window. Repair activities will not be affected. If we carry out any maintenance activity during this window, it will be for emergency reasons and will be carried out to protect customer service and the network from an uncontrolled loss of service. Please ensure any new orders are submitted in good time to avoid being affected by this window. Regards, David Croft Read more » | |
Sep 8 |
[Cloud Ethernet] Maintenance window 11th September 2014
Posted by David Croft on 08 September 2014 08:26 AM |
Please be advised of the following maintenance window scheduled by BT on the 21C network: Date: Thursday, 11th September 2014 Start time: 02:00 BST (UTC+0100) End time: 06:00 BST (UTC+0100) Purpose: BT have advised us that they will be performing maintenance on the 21C network. Services affected: Cloud Ethernet (All BT variants). Impact: HIGH. As part of this work, BT will perform software upgrades on the devices terminating our 21CN connections. There will be an expected outage of up to 90 minutes during this window. Comtec NOC is tracking this issue under ticket [#IPQ-935-86950]. Regards, David Croft Read more » | |
Aug 4 |
[QUAR] [IP Voice Services] Maintenance window 16th August 2014 - ACTION REQUIRED
Posted by David Croft on 04 August 2014 11:39 AM |
Please be advised of the following maintenance window scheduled on IP Voice Services. PLEASE READ CAREFULLY IF YOU USE HOSTED IP VOICE SERVICES. ACTION IS REQUIRED TO AVOID INTERRUPTION TO YOUR SERVICE. Date: Saturday, 16th August 2014 Start time: 10:30 BST (UTC+0100) End time: 23:59 BST (UTC+0100) Purpose: The Engineering Team will be performing works to migrate a portion of traffic from one Session Border Controller (SBC) cluster to another to offer upgraded capacity. Services affected: IP Voice Services. Impact: HIGH. Required Action: As part of this work, all hosted phones/ATAs that are currently registering with 85.119.63.1 will start registering with 85.119.63.17 instead. This will be accomplished by changing the DNS records that they use. Please ensure that your firewalls have been updated to allow communication with this IP address, and that you have the appropriate route installed if you do not have a default route. These changes can and should be made in advance of the maintenance window. Detail: These works will affect ALL public (IC) registering hosted IP phones/ATAs and mobile/desktop applications; their configuration files use the uk.ic.hnt.hipcom.co.uk/uk.ic.56hnt.hipcom.co.uk (85.119.63.1) proxy. The change will be activated by modifying the public DNS records for the above proxies to the new IP address of 85.119.63.17. This will ensure that this is a more gradual and staggered change with as little disruption to users as possible. These works have an extended window due to the nature of DNS updates through the internet and the time it will take to propagate fully. The Panasonic range of phones will require a config update, which will be applied during these works, these WILL require a reboot for the change to take effect to allow the phones to successfully move over to the new environment; this can be done at the customer's discretion as the DNS change will not affect service for currently registered handsets. Due to the nature of this change, some handsets may require a reboot in order to start sending SIP REGISTER messages to the new gateway, even if they have correctly picked up the new IP via DNS. If you do experience any disruption beyond the maintenance window, please restart your device to ensure that it re-registers cleanly to the platform before raising a ticket. This change will also affect UC Office and Mobile Office clients. The clients will need restarting after the DNS change has propagated in order to move over to the new SBC environment, or if experiencing any issues. Handsets and clients will lose service if the end users' firewall(s) have not been configured to allow SIP/RTP traffic to/from 85.119.63.17. The Engineering team will be working to ensure that the effect on service is minimised during this low traffic period. Our Engineering Team will be closely monitoring all systems and services, as well as the above, to ensure any disruption is as brief as possible if experienced. Regards, David Croft Read more » | |