<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Is it normal to want to assign every object you own a serial number, then keep a database?</title>
	<atom:link href="http://www.snell-pym.org.uk/archives/2007/10/18/is-it-normal-to-want-to-assign-every-object-you-own-a-serial-number-then-keep-a-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.snell-pym.org.uk/archives/2007/10/18/is-it-normal-to-want-to-assign-every-object-you-own-a-serial-number-then-keep-a-database/</link>
	<description>Sarah and Alaric Snell-Pym living in interesting times</description>
	<pubDate>Tue, 22 May 2012 17:01:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: @ndy</title>
		<link>http://www.snell-pym.org.uk/archives/2007/10/18/is-it-normal-to-want-to-assign-every-object-you-own-a-serial-number-then-keep-a-database/comment-page-1/#comment-56404</link>
		<dc:creator>@ndy</dc:creator>
		<pubDate>Thu, 18 Oct 2007 21:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.snell-pym.org.uk/archives/2007/10/18/is-it-normal-to-want-to-assign-every-object-you-own-a-serial-number-then-keep-a-database/#comment-56404</guid>
		<description>&lt;p&gt;...and one more thing... In the past I've used some sticky cable labels. They're half label and half clear. You write on the label part and then wrap it around the cable, starting with the labely end. As you wrap, the clear end covers over the labely end and stops the text from rubbing off.&lt;/p&gt;

&lt;p&gt;These look much prettier than the clippy ones in your picture but it's a case of form over function as your ones use the power of colour to make identification easier.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>...and one more thing... In the past I've used some sticky cable labels. They're half label and half clear. You write on the label part and then wrap it around the cable, starting with the labely end. As you wrap, the clear end covers over the labely end and stops the text from rubbing off.</p>

<p>These look much prettier than the clippy ones in your picture but it's a case of form over function as your ones use the power of colour to make identification easier.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: @ndy</title>
		<link>http://www.snell-pym.org.uk/archives/2007/10/18/is-it-normal-to-want-to-assign-every-object-you-own-a-serial-number-then-keep-a-database/comment-page-1/#comment-56403</link>
		<dc:creator>@ndy</dc:creator>
		<pubDate>Thu, 18 Oct 2007 21:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.snell-pym.org.uk/archives/2007/10/18/is-it-normal-to-want-to-assign-every-object-you-own-a-serial-number-then-keep-a-database/#comment-56403</guid>
		<description>&lt;p&gt;"The cable spreadsheet" and "The patch spreadsheet" are never a good idea for anything except for maybe the most permenant of installations. It only takes one person once to forget to update it, or update it incorrectly and then you're into GIGO land.&lt;/p&gt;

&lt;p&gt;I'd get s switch that can tell you what it's got plugged into it, perhaps even via SNMP. Then, have different colour cable for each part of the redundancy. Then you plug all the "red" cables in one place, all the "white" ones in another and be happy that you have a "red" and a "white" connected to each server. You don't worry which port each one is in because it doesn't matter. You then write a script that works out which machine (MAC address?) is on the end of each port and changes the port settings appropriately.&lt;/p&gt;

&lt;p&gt;Your spreadsheet database will be troublesome because you will constantly be trying to keep two different copies of the same data in sync.... and we all know where that ends.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>"The cable spreadsheet" and "The patch spreadsheet" are never a good idea for anything except for maybe the most permenant of installations. It only takes one person once to forget to update it, or update it incorrectly and then you're into GIGO land.</p>

<p>I'd get s switch that can tell you what it's got plugged into it, perhaps even via SNMP. Then, have different colour cable for each part of the redundancy. Then you plug all the "red" cables in one place, all the "white" ones in another and be happy that you have a "red" and a "white" connected to each server. You don't worry which port each one is in because it doesn't matter. You then write a script that works out which machine (MAC address?) is on the end of each port and changes the port settings appropriately.</p>

<p>Your spreadsheet database will be troublesome because you will constantly be trying to keep two different copies of the same data in sync.... and we all know where that ends.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.snell-pym.org.uk/archives/2007/10/18/is-it-normal-to-want-to-assign-every-object-you-own-a-serial-number-then-keep-a-database/comment-page-1/#comment-56396</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Thu, 18 Oct 2007 13:40:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.snell-pym.org.uk/archives/2007/10/18/is-it-normal-to-want-to-assign-every-object-you-own-a-serial-number-then-keep-a-database/#comment-56396</guid>
		<description>&lt;p&gt;What you want is to give every object an IPv6 address and have it expose status over http plus something like mDNS for discoverability.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What you want is to give every object an IPv6 address and have it expose status over http plus something like mDNS for discoverability.</p>]]></content:encoded>
	</item>
</channel>
</rss>

