<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://stab.st-andrews.ac.uk/wiki/index.php?action=history&amp;feed=atom&amp;title=Node9_network_failure_incident_16-20.03.2017</id>
		<title>Node9 network failure incident 16-20.03.2017 - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://stab.st-andrews.ac.uk/wiki/index.php?action=history&amp;feed=atom&amp;title=Node9_network_failure_incident_16-20.03.2017"/>
		<link rel="alternate" type="text/html" href="http://stab.st-andrews.ac.uk/wiki/index.php?title=Node9_network_failure_incident_16-20.03.2017&amp;action=history"/>
		<updated>2026-05-01T23:39:00Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>http://stab.st-andrews.ac.uk/wiki/index.php?title=Node9_network_failure_incident_16-20.03.2017&amp;diff=1252&amp;oldid=prev</id>
		<title>Rf: Created page with &quot;= Introduction =  Node9 usually a perfectly behaving machine suddenly loses network connections.  = Troubleshooting =  Going through all the procedures to see which component...&quot;</title>
		<link rel="alternate" type="text/html" href="http://stab.st-andrews.ac.uk/wiki/index.php?title=Node9_network_failure_incident_16-20.03.2017&amp;diff=1252&amp;oldid=prev"/>
				<updated>2017-03-20T18:05:55Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;= Introduction =  Node9 usually a perfectly behaving machine suddenly loses network connections.  = Troubleshooting =  Going through all the procedures to see which component...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;= Introduction =&lt;br /&gt;
&lt;br /&gt;
Node9 usually a perfectly behaving machine suddenly loses network connections.&lt;br /&gt;
&lt;br /&gt;
= Troubleshooting =&lt;br /&gt;
&lt;br /&gt;
Going through all the procedures to see which component was to blame took an entire day, unfortunately during quite a busy period for projects. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It turns out the machine nor its network interfaces were not to blame. This was time wasted because it turned out to be a Network Services issue. They were chaning around network hubs and some cabling did not get re-seated properly, it would seem.&lt;br /&gt;
&lt;br /&gt;
Here are the details&lt;br /&gt;
&lt;br /&gt;
 The Butts Wynd Data Centre Core Switches&amp;#039; (BWDC Cisco Nexus 5672s) port-channel linking your High Performance Computing System (Viglen HX425Ca - Asset 03267, rack 17 position 35) is now up and running (see output included below), having re-seated the copper cabling connecting up both of its Ethernet interfaces. Please do let us know if this problem re-occurs.&lt;br /&gt;
 &lt;br /&gt;
 bwdc-n5672-0# show port-channel sum | inc Po146&lt;br /&gt;
 146   Po146(SU)   Eth      LACP      Eth108/1/28(P)&lt;br /&gt;
 &lt;br /&gt;
 bwdc-n5672-0# show logging | inc Ethernet108/1/28&lt;br /&gt;
 ...&lt;br /&gt;
 2017 Mar 20 16:15:03 bwdc-n5672-0 %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel146: first operational port changed from none to Ethernet108/1/28&lt;br /&gt;
 2017 Mar 20 16:15:03 bwdc-n5672-0 %ETHPORT-5-IF_UP: Interface Ethernet108/1/28 is up in mode access&lt;br /&gt;
 &lt;br /&gt;
 bwdc-n5672-1# show port-channel sum | inc Po146&lt;br /&gt;
 146   Po146(SU)   Eth      LACP      Eth109/1/28(P)bwdc-n5672-1#&lt;br /&gt;
 ...&lt;br /&gt;
 2017 Mar 20 16:15:00 bwdc-n5672-1 %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel146: first operational port changed from none to Ethernet109/1/28&lt;br /&gt;
 2017 Mar 20 16:15:00 bwdc-n5672-1 %ETHPORT-5-IF_UP: Interface Ethernet109/1/28 is up in mode access&lt;/div&gt;</summary>
		<author><name>Rf</name></author>	</entry>

	</feed>