Difference between revisions of "Site Computer"

From Cues
Jump to navigationJump to search
Line 7: Line 7:
  
 
CUES-Mac: 173 704 513
 
CUES-Mac: 173 704 513
 +
 +
New CUES-Mac (201212): 164 092 848
  
 
MASC: 974 763 535
 
MASC: 974 763 535

Revision as of 16:24, 7 December 2012

System name is CUES-Mini, it's at 192.168.220.251 on the MMSA Employee Net and at 72.67.190.65 from anywhere. SSH is the only port forwarded to the system from the outside.

TeamViewer

CUES-Win: 165 385 363

CUES-Win-new: 294 636 003

CUES-Mac: 173 704 513

New CUES-Mac (201212): 164 092 848

MASC: 974 763 535

VNC over SSH

Getting onto the system from the outside:

I've got the site system accepting VNC connections via an SSH tunnel. Here's a good VNC over SSH HowTo.

That's designed for the Mac but you'll get the idea. Username is "cues".

The key bit is the login tunnel:

ssh cues@72.67.190.65 -L 5900:localhost:5900

Then, on the Mac anyhow, you'll fire up a VNC session (Command-K from the Finder) and enter:

vnc://localhost:0

LiDAR

Power Cycling the LiDAR remotely

  • Get onto the CUES system at the site (SHOULD work from either the Mac or Win system)
  • Open up a cygwin or command terminal.
  • ssh cues@192.168.0.254
    • standard passwd you should all know.
    • It'll take a short while to login and then give you a "Sentry" prompt.
  • off
  • LiDAR
  • wait 5 seconds or humm the Jeapordy Tune.
  • on
  • LiDAR

Networks

en0 (MMSA ResNet): 192.168.220.251 255.255.255.0 192.168.220.1 SME

en2 (CUES Pre-20110920 private subnet): 10.1.1.251 255.255.255.0 10.1.1.1

en3 (CUES Mac on Private subnet): 192.168.0.251

Data Loggers:

  • CR3000-1: IP: 192.168.0.101
  • CR3000-2: IP: 192.168.0.102
  • CR3000-3: IP: 192.168.0.103

LiDAR:

  • IP 192.168.0.234

LiDAR IP-Power Switched CDU Manual:

  • IP: 192.168.0.254

Camera:

  • IP: 192.168.0.90

Backups

System is running TimeMachine onto "CUES-TimeMachine" drive which is a 160GB laptop drive plugged in via USB. The VMware Fusion system is set to take Auto-SnapShots in order to keep from having to backup the entire VM every TimeMachine instance as explained here.

Colee is also keeping a CCCloner copy of the system at UCSB.