== Available Servers ==
=== AArch64: Red ===
The first server is an [[ARMv8]] AArch64 system known simply as '''redaarchie''' or '''archie'''. This machine is accessible as <code>red.proximitya system that is currently located inside the [[EHL]].To connect to this system, you have to go through the EHL gateway onport 2200.ca</code> -- To connect from If you're using a command-line ssh clientsystem, and you are on the Seneca network, you can issue a command such as this:
ssh -p 2200 ''username''@redehl.proximityinternal.oncdot.casystems
{{Admon/note|Why Red?|When the first three servers arrived for the [[EHL]], we named them Red, Green, and Blue, after the colours of the ethernet cables we had - so that we could tell them apart easily. In the EHL cabinet, they're labelled x1 (Blue), x2 (Red), and x3 (Green), along with the other 1u ARM64 servers.}}To connect from outside Seneca:
=== x86_64: Australia === ssh -p 2200 ''username'@ehl.cdot.systems
The other server is an === x86_64 system known as <code>Australia.proximity.on.ca</code>. To connect to it, issue this command:===
ssh ''username''@australiaThe other server is an x86_64 system known as <code>xerxes</code>.proximity.on.caTo connect to it from within Seneca, issue this command:
{{Admon/note|Why Australia?|The [[CDOT]] servers are all named after countries; the person who installs the OS gets to pick the country ssh ''username''@xerxes.internal.cdot. When theresystems You can's a network issue in CDOTt yet connect to xerxes from outside Seneca, it always sounds like so connect to a major international incidentsystem inside Seneca first and then use the command above. Check back to this page to find out when external access is available.<!}}-- ssh ''username''@xerxes.cdot.systems-->
== Sudo Access ==