James Courtier-Dutton <james.dutton@???> wrote:
>Hi,
>
>I have been given the task of explaining Layer 3 Ethernet switch
>failover to a person who knows nothing about Ethernet or TCP/IP.
>I made a stab at explaining HSRP and VRRP and why avoiding the "alone,
>alone" scenario is a good idea etc., but lets just say, knowledge was
>not transferred!
>The problem is, if I fail to get the concept across correctly, actual
>lives might be lost!!! (It is going to be used in a safety related
>communications system)
>It is the job of the other person to decide if equipment X is good
>enough for the job or not from a safety perspective.
>
I wouldn't try to explain the technicalities. From my perspective, it doesn't really matter how the piece of equipment does what it does or even exactly what it does. I would explain that this piece of equipment is responsible for handling all communications within the system. I would say that it, like every piece of equipment, will eventually fail and that, when it does, if there is no spare to automatically take over, the whole system will stop working until someone attends with a replacement. I'd then use phrases like "legal exposure" if someone dies in the however many hours it will take to get a spare and an engineer out when when it fails at 2am on Christmas morning. I'd also point out that this risk to human life needs to be listed in the project risk assessment, mumble"duty of care" and if it's not mitigated and someone dies then the HSE could well prosecute.
Then just tell them that for £x you can fit a second unit and set it up to automatically take over so all this goes away. You can also say that it will save money in middle of the night engineer visits. I would follow your advice in writing and, if they decline, insist they put it in an email so you are covered.
Cheers,
Paul.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
