| System Notices and Comments | |
|---|---|
| gates-sw-3-3.Stanford.EDU | This switch has not been deployed yet. https://rt.stanford.edu/rt/Ticket/Display.html?id=51411 |
| cellar.Stanford.EDU | RAID problems causing disk problems. |
| unicorn6.Stanford.EDU | Gates B14, D8 U8 |
| Device | State | Summary | First time | Last time | |
|---|---|---|---|---|---|
New ProblemsThese are problems that we are aware of, but have not neccesarily begun working on. | jen.Stanford.EDU | Production | /Status/Ping | ip 172.24.67.102 is down | |
| cs-lb-2.Stanford.EDU | Production | /Status/Ping | ip 171.64.64.84 is down | ||
| sunburst.Stanford.EDU | Preproduction | /Status/Ping | ip 171.64.64.73 is down | ||
| pod36.Stanford.EDU | Production | /Status/Ping | ip 171.67.231.169 is down | ||
| harley.Stanford.EDU | Preproduction | /Status/Ping | ip 171.64.40.250 is down | ||
| unicorn8.Stanford.EDU | Production | /Status/Ping | ip 172.24.69.17 is down | ||
| gnat-1-ipmi.Stanford.EDU | Preproduction | /Status/Ping | ip 172.24.70.44 is down | ||
| gryphon10 | Production | /Status/Ping | ip 171.64.68.120 is down | ||
| visionlab4.Stanford.EDU | Production | /Status/Ping | ip 171.64.68.151 is down | ||
| nash-9.Stanford.EDU | Production | /Status/Ping | ip 172.24.68.25 is down | ||
| cs-hostplex-3-ipmi.Stanford.EDU | Preproduction | /Status/Ping | ip 172.24.64.65 is down | ||
| cs-www-3.Stanford.EDU | Production | /Status/Ping | ip 172.24.64.43 is down | ||
| watts-7.Stanford.EDU | Production | /Status/Ping | ip 172.24.64.26 is down | ||
| watts-6.Stanford.EDU | Production | /Status/Ping | ip 172.24.64.25 is down | ||
| watts-10.Stanford.EDU | Production | /Status/Ping | ip 172.27.64.44 is down | ||
| loft.Stanford.EDU | Production | root | /Unknown | [ID 702911 local0.alert] Solstice Backup media: (waiting) Waiting for 1 writable volumes to backup pool 'Default' tape(s) on lof | |
| loft.Stanford.EDU | Production | root | /Unknown | [ID 702911 local0.alert] Solstice Backup media: (critical) Waiting for 2 writable volumes to backup pool 'Default' tape(s) on lo | |
| loft.Stanford.EDU | Production | root | /Unknown | [ID 702911 local0.alert] Solstice Backup media: (critical) Waiting for 1 writable volumes to backup pool 'Default' tape(s) on lo | |
MaintenanceThese are undergoing maintenance. | gates-sw-3-3.Stanford.EDU | Production | /Status/Ping | ip 172.24.70.22 is down | |
| watts-9.Stanford.EDU | Production | /Status/Ping | ip 172.24.64.29 is down |
When you ssh into the myth, pod, or xenon systems, you will receive a waning that the host key has changed. The warning will look something like this:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 96:90:ab:7c:29:07:52:9d:4a:7e:ad:1e:27:d8:2e:92. Please contact your system administrator. Add correct host key in /afs/ir/users/m/i/miles1/.ssh/known_hosts to get rid of this message. Offending key in /etc/ssh/ssh_known_hosts:3 RSA host key for myth has changed and you have requested strict checking. Host key verification failed.
You will need to remove the old key entry from your known_hosts file -- the error will give you the name of the file to edit and the line to remove.
The new fingerprints are:
myth/pod dsa 4b:6e:39:85:47:fd:7b:e5:03:0f:b4:9c:bc:1c:47:58 myth/pod rsa 9c:fe:9b:f2:b5:25:d0:31:fd:63:16:2d:f9:8a:b7:52 xenon dsa 02:02:c4:07:96:51:e8:e5:7b:3b:3c:de:40:63:aa:c4 xenon rsa f8:2c:1e:64:a7:8e:4a:fa:73:cd:3b:99:5f:84:ff:15