<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for XILO News and Status</title>
	<link>http://blog.xilo.net</link>
	<description>http://www.xilo.net/</description>
	<pubDate>Sat, 05 Jul 2008 08:35:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>Comment on LiNX Network Issues by XILO</title>
		<link>http://blog.xilo.net/2008/05/27/linx-network-issues-2/service-outage-cat#comment-49</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Thu, 29 May 2008 16:10:27 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/05/27/linx-network-issues-2/service-outage-cat#comment-49</guid>
		<description>We have reports that after a brief outage last night at LINX, the network should now be back to normal service.

LINX gave the following statement: 'Yesterday evening we did experience a recurrence of one of the faults from the previous week. Our engineers, working alongside those from our vendor, implemented an alternate configuration returning the affected parts of our network to full service.'</description>
		<content:encoded><![CDATA[<p>We have reports that after a brief outage last night at LINX, the network should now be back to normal service.</p>
<p>LINX gave the following statement: &#8216;Yesterday evening we did experience a recurrence of one of the faults from the previous week. Our engineers, working alongside those from our vendor, implemented an alternate configuration returning the affected parts of our network to full service.&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BlueSquare 2 - UPS Issue by XILO</title>
		<link>http://blog.xilo.net/2008/04/30/bluesqare-2-ups-issue/service-outage-cat#comment-48</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Tue, 13 May 2008 01:47:09 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/04/30/bluesqare-2-ups-issue/service-outage-cat#comment-48</guid>
		<description>We have now received the final report from the engineers who travelled from Switzerland to visit the failed UPS system.

The summary of their report as below (please excuse the Swiss/Italian English language):
Situation of the failed UPS :

Input Rectifier fuses OK
Input By-pass fuses OK
Battery fuses OK

Input positive Booster fuses NOTOK	 Input negative Booster fuses NOTOK
Output positive Booster fuses OK	 Output negative Booster fuses OK

Inverter L1 T1 pos. NOTOK	 Inverter L1 T2 pos. NOTOK
Inverter L1 T1 neg. NOTOK	 Inverter L1 T2 neg. NOTOK

Inverter L2 T1 pos. NOTOK	 Inverter L2 T2 pos. NOTOK
Inverter L2 T1 neg. NOTOK	 Inverter L2 T2 neg. OK

Inverter L3 T1 pos. NOTOK	 Inverter L3 T2 pos. NOTOK
Inverter L3 T1 neg. NOTOK	 Inverter L3 T2 neg. NOTOK

Battery Charger pos. NOTOK	 Input Battery fuses pos. NOTOK
Battery Charger neg. OK	 Input Battery fuses neg. NOTOK

The unit failed because of a short circuit between positive booster and positive rectifier caused by insulation damage on the booster battery inductors cables near the positive capacitors.

The input breaker on the distribution cabinet, in case of a short circuit on By-pass, opened before the rupture of the input fuses.

As happen on site: the short circuit on the unit Nr.2 was supplied from the other UPS’s, the load has be transferred to By-pass which continued to supply the short circuit. As a consequence the input breaker of all the units trip and the units lost the load. 

Corrective Actions:
The power cables (Inductor Booster) holder are of units now in production are protected and in the same way the isolation sheet on the “sandwich” is now protected.

NEWAVE SA, after the suggested assembling critical points undertake immediately a corrective action but this unit left the factory before performing the enhancement. 
All new units have the protective enhancement, and a NEWAVE SA engineer will support a engineer of UPS Ltd to again check minutely all the cables of the other units at BlueSquare.

------

We will issue a further post in advance of any works to re-check the cabling of the remaining on site units. We expect this work to be completed within the next two weeks.</description>
		<content:encoded><![CDATA[<p>We have now received the final report from the engineers who travelled from Switzerland to visit the failed UPS system.</p>
<p>The summary of their report as below (please excuse the Swiss/Italian English language):<br />
Situation of the failed UPS :</p>
<p>Input Rectifier fuses OK<br />
Input By-pass fuses OK<br />
Battery fuses OK</p>
<p>Input positive Booster fuses NOTOK	 Input negative Booster fuses NOTOK<br />
Output positive Booster fuses OK	 Output negative Booster fuses OK</p>
<p>Inverter L1 T1 pos. NOTOK	 Inverter L1 T2 pos. NOTOK<br />
Inverter L1 T1 neg. NOTOK	 Inverter L1 T2 neg. NOTOK</p>
<p>Inverter L2 T1 pos. NOTOK	 Inverter L2 T2 pos. NOTOK<br />
Inverter L2 T1 neg. NOTOK	 Inverter L2 T2 neg. OK</p>
<p>Inverter L3 T1 pos. NOTOK	 Inverter L3 T2 pos. NOTOK<br />
Inverter L3 T1 neg. NOTOK	 Inverter L3 T2 neg. NOTOK</p>
<p>Battery Charger pos. NOTOK	 Input Battery fuses pos. NOTOK<br />
Battery Charger neg. OK	 Input Battery fuses neg. NOTOK</p>
<p>The unit failed because of a short circuit between positive booster and positive rectifier caused by insulation damage on the booster battery inductors cables near the positive capacitors.</p>
<p>The input breaker on the distribution cabinet, in case of a short circuit on By-pass, opened before the rupture of the input fuses.</p>
<p>As happen on site: the short circuit on the unit Nr.2 was supplied from the other UPS’s, the load has be transferred to By-pass which continued to supply the short circuit. As a consequence the input breaker of all the units trip and the units lost the load. </p>
<p>Corrective Actions:<br />
The power cables (Inductor Booster) holder are of units now in production are protected and in the same way the isolation sheet on the “sandwich” is now protected.</p>
<p>NEWAVE SA, after the suggested assembling critical points undertake immediately a corrective action but this unit left the factory before performing the enhancement.<br />
All new units have the protective enhancement, and a NEWAVE SA engineer will support a engineer of UPS Ltd to again check minutely all the cables of the other units at BlueSquare.</p>
<p>&#8212;&#8212;</p>
<p>We will issue a further post in advance of any works to re-check the cabling of the remaining on site units. We expect this work to be completed within the next two weeks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on LINX Network Issues by XILO</title>
		<link>http://blog.xilo.net/2008/05/02/linx-network-issues/status-cat#comment-47</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Fri, 02 May 2008 12:40:05 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/05/02/linx-network-issues/status-cat#comment-47</guid>
		<description>Update from LINX:

A crashed traffic manager (this is an element of the forwarding complex on an MLX linecard) is suspected to be the cause of the outage. This is being escalated as a P1 with the vendor.

In the meantime, we are taking steps to move traffic off the crashed card to a backup.</description>
		<content:encoded><![CDATA[<p>Update from LINX:</p>
<p>A crashed traffic manager (this is an element of the forwarding complex on an MLX linecard) is suspected to be the cause of the outage. This is being escalated as a P1 with the vendor.</p>
<p>In the meantime, we are taking steps to move traffic off the crashed card to a backup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BlueSquare 2 - UPS Issue by XILO</title>
		<link>http://blog.xilo.net/2008/04/30/bluesqare-2-ups-issue/service-outage-cat#comment-46</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Thu, 01 May 2008 09:14:08 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/04/30/bluesqare-2-ups-issue/service-outage-cat#comment-46</guid>
		<description>We have received the following update and reply from BlueSquare management.

--
Please find below a further status update on the power situation for BlueSquare 2 &#038; 3.

The parallel UPS system based in BlueSquare 2, which also feeds BlueSquare 3, consists of 4 separate UPS systems that are paralleled together and share a common bus bar system. UPS units 1,2 &#038; 3 have been running since the building went live, nearly 1 year ago. Unit 4 was added to the system yesterday to increase the overall system capacity ready for the load on first floor of BlueSquare 3 to go live.

During our maintenance window today which was performed by the UPS manufacturer, the new 4th UPS system was given a bypass check, and a battery test. This completed successfully. Approximately 15 minutes later, with all 4 systems running normally, the existing UPS unit 2 failed. Unfortunately it failed in a critical way, which meant a bypass message was sent to the remaining UPS systems which put them onto raw mains. The critical load transferred to the remaining three systems that were running on raw mains without any problem.

However, the failure of UPS 2 which was caused by a faulty component almost immediately created an overload situation on the mains incomers, which meant the mains incoming supplies to each UPS were tripped off. The UPS’s detected the loss of raw mains, and immediately reverted back to battery backup and out of bypass mode. During this sequence of events customers would have noticed a very short (sub-second) loss of power which may have resulted in some customers equipment rebooting.

The incomer mains circuit breakers were then reset back to the on position for the 3 remaining UPS units, and service was back to normal conditions.

Initial investigation by the manufactures onsite UPS engineers, and subsequent visit by senior engineers who travelled to site showed that a critical internal component had failed causing this knock on effect.

We have since been continually liaising with senior management from the UPS manufactures UK division, as well as the designers at the factory in Switzerland to find the cause of this component failure. An engineer is being flown over from Switzerland to arrive at BlueSquare within the next 48 hours to continue on site investigation work on UPS unit 2.

We have conducted a heath check of the remaining three UPS systems and we are happy that these are all working normally and are at no risk of developing any foreseeable faults.

We have N+1 redundancy on the UPS systems, and full generator backup if required.

We will issue a further update once the engineers from the factory arrive on site.

Again, we apologise for any inconvenience caused today.
--

Many thanks to all customers for their understanding and patience.</description>
		<content:encoded><![CDATA[<p>We have received the following update and reply from BlueSquare management.</p>
<p>&#8211;<br />
Please find below a further status update on the power situation for BlueSquare 2 &#038; 3.</p>
<p>The parallel UPS system based in BlueSquare 2, which also feeds BlueSquare 3, consists of 4 separate UPS systems that are paralleled together and share a common bus bar system. UPS units 1,2 &#038; 3 have been running since the building went live, nearly 1 year ago. Unit 4 was added to the system yesterday to increase the overall system capacity ready for the load on first floor of BlueSquare 3 to go live.</p>
<p>During our maintenance window today which was performed by the UPS manufacturer, the new 4th UPS system was given a bypass check, and a battery test. This completed successfully. Approximately 15 minutes later, with all 4 systems running normally, the existing UPS unit 2 failed. Unfortunately it failed in a critical way, which meant a bypass message was sent to the remaining UPS systems which put them onto raw mains. The critical load transferred to the remaining three systems that were running on raw mains without any problem.</p>
<p>However, the failure of UPS 2 which was caused by a faulty component almost immediately created an overload situation on the mains incomers, which meant the mains incoming supplies to each UPS were tripped off. The UPS’s detected the loss of raw mains, and immediately reverted back to battery backup and out of bypass mode. During this sequence of events customers would have noticed a very short (sub-second) loss of power which may have resulted in some customers equipment rebooting.</p>
<p>The incomer mains circuit breakers were then reset back to the on position for the 3 remaining UPS units, and service was back to normal conditions.</p>
<p>Initial investigation by the manufactures onsite UPS engineers, and subsequent visit by senior engineers who travelled to site showed that a critical internal component had failed causing this knock on effect.</p>
<p>We have since been continually liaising with senior management from the UPS manufactures UK division, as well as the designers at the factory in Switzerland to find the cause of this component failure. An engineer is being flown over from Switzerland to arrive at BlueSquare within the next 48 hours to continue on site investigation work on UPS unit 2.</p>
<p>We have conducted a heath check of the remaining three UPS systems and we are happy that these are all working normally and are at no risk of developing any foreseeable faults.</p>
<p>We have N+1 redundancy on the UPS systems, and full generator backup if required.</p>
<p>We will issue a further update once the engineers from the factory arrive on site.</p>
<p>Again, we apologise for any inconvenience caused today.<br />
&#8211;</p>
<p>Many thanks to all customers for their understanding and patience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Foxtrot - Unplanned reboot by XILO</title>
		<link>http://blog.xilo.net/2008/04/03/foxtrot-unplanned-reboot-2/service-outage-cat#comment-43</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Mon, 07 Apr 2008 16:04:34 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/04/03/foxtrot-unplanned-reboot-2/service-outage-cat#comment-43</guid>
		<description>Server is now once again online and we are arranging for a new server for the migration.</description>
		<content:encoded><![CDATA[<p>Server is now once again online and we are arranging for a new server for the migration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Foxtrot - Unplanned reboot by XILO</title>
		<link>http://blog.xilo.net/2008/04/03/foxtrot-unplanned-reboot-2/service-outage-cat#comment-42</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Mon, 07 Apr 2008 15:32:34 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/04/03/foxtrot-unplanned-reboot-2/service-outage-cat#comment-42</guid>
		<description>There has been a further unplanned reboot of this server today.

We now think that this maybe hardware related and will be planning to migrate this box to newer kit in the next week.

Notification will be sent to all resellers on Foxtrot with the exact time and date details.</description>
		<content:encoded><![CDATA[<p>There has been a further unplanned reboot of this server today.</p>
<p>We now think that this maybe hardware related and will be planning to migrate this box to newer kit in the next week.</p>
<p>Notification will be sent to all resellers on Foxtrot with the exact time and date details.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Foxtrot - Unplanned reboot by XILO</title>
		<link>http://blog.xilo.net/2008/04/03/foxtrot-unplanned-reboot-2/service-outage-cat#comment-41</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Thu, 03 Apr 2008 14:54:26 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/04/03/foxtrot-unplanned-reboot-2/service-outage-cat#comment-41</guid>
		<description>The disk check is now complete and the server is back in service.

We will continue our investigation to find out why the server rebooted without notice.</description>
		<content:encoded><![CDATA[<p>The disk check is now complete and the server is back in service.</p>
<p>We will continue our investigation to find out why the server rebooted without notice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Foxtrot - Unplanned reboot by XILO</title>
		<link>http://blog.xilo.net/2008/04/03/foxtrot-unplanned-reboot-2/service-outage-cat#comment-40</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Thu, 03 Apr 2008 14:38:36 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/04/03/foxtrot-unplanned-reboot-2/service-outage-cat#comment-40</guid>
		<description>The scan is on stage 1B. There are three stages remaining.</description>
		<content:encoded><![CDATA[<p>The scan is on stage 1B. There are three stages remaining.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on LINX Routing Issues by XILO</title>
		<link>http://blog.xilo.net/2008/03/29/linx-routing-issues/service-outage-cat#comment-39</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Sat, 29 Mar 2008 15:39:02 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/03/29/linx-routing-issues/service-outage-cat#comment-39</guid>
		<description>Connectivity should now be restored. A further update will follow.</description>
		<content:encoded><![CDATA[<p>Connectivity should now be restored. A further update will follow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DDoS Attack - Indigo by XILO</title>
		<link>http://blog.xilo.net/2008/02/23/ddos-attack-indigo/service-outage-cat#comment-38</link>
		<dc:creator>XILO</dc:creator>
		<pubDate>Sun, 24 Feb 2008 03:30:57 +0000</pubDate>
		<guid>http://blog.xilo.net/2008/02/23/ddos-attack-indigo/service-outage-cat#comment-38</guid>
		<description>Web access was restored an hour ago and we have added some further blocking to detect the attack.

At this time, the attack is on-going and the site that the attack was aimed against has been removed from our network in line with our acceptable policy.

Apologies for any problems this may have caused.</description>
		<content:encoded><![CDATA[<p>Web access was restored an hour ago and we have added some further blocking to detect the attack.</p>
<p>At this time, the attack is on-going and the site that the attack was aimed against has been removed from our network in line with our acceptable policy.</p>
<p>Apologies for any problems this may have caused.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
