User Tools
operations:documentation.errors
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
operations:documentation.errors [2017/08/13 18:22] Tiege McCarthy |
operations:documentation.errors [2017/08/13 22:15] Tiege McCarthy |
||
|---|---|---|---|
| Line 128: | Line 128: | ||
| ==== Ceduna Network Down ==== | ==== Ceduna Network Down ==== | ||
| - | ssh into hobart and make sure to forward the X server | + | |
| + | First ssh into hobart and make sure to forward the X server | ||
| <code>ssh -X oper@hobart.phys.utas.edu.au</code> | <code>ssh -X oper@hobart.phys.utas.edu.au</code> | ||
| - | VNC into the 'manager' PC | + | From terminal on hobart, VNC into the 'manager' PC |
| <code>vncviewer manager</code> | <code>vncviewer manager</code> | ||
| - | Go to network connections in the bottom right, left-click on this icon and then right-click on 'CEDUNA-NETWORK' and connect. May need to click 'dial' on a pop up window. Once this connection is established open up TightVNC (should be in start menu). VNC into the router PC, details should already be in, just press connect. The password is not standard for this PC (ask for it in group chat and remember/write it down). | + | Go to network connections in the bottom right, left-click on this icon and then right-click on 'CEDUNA-NETWORK' and connect. May need to click 'dial' on a pop up window. Once this connection is established open up TightVNC (should be in start menu). VNC into the router PC, details should already be in, just press connect. **The password is not standard for this PC** (ask for it in group chat and remember/write it down). |
| Check status of 3G network on the status page, navigate to system tools on the left. Click on the reboot sub-menu. Click reboot and confirm. | Check status of 3G network on the status page, navigate to system tools on the left. Click on the reboot sub-menu. Click reboot and confirm. | ||
| Line 138: | Line 139: | ||
| Start pinging the ceduna gateway (131.217.61.129) on your PC (not in the VNC window). In a terminal or command prompt: | Start pinging the ceduna gateway (131.217.61.129) on your PC (not in the VNC window). In a terminal or command prompt: | ||
| <code>ping 131.217.61.129</code> | <code>ping 131.217.61.129</code> | ||
| - | After the router finishes rebooting, click on the status menu (top-left) and check the 3G status. Ideally, the pings will start reaching the the Ceduna gateway. If not try another reboot or call Brett | + | After the router finishes rebooting, click on the status menu (top-left) and check the 3G status. Ideally, the pings will start reaching the the Ceduna gateway, If so skip the next step, If not it may be the VPN that needs fixing, to do this run putty.exe (on the desktop), ssh into 192.168.1.61, login as 'physics' (different password again) and run the following command: |
| - | as the VPN may not have come up properly. | + | |
| - | Once you have established connection, exit out of the router PC VNC window, then go down to network connections on 'manager', right-click on CEDUNA-NETWORK and click disconnect. | + | <code>clear crypto ipsec client ezvpn</code> |
| + | |||
| + | Once you have established connection (can ping the gateway), exit out of the router PC VNC window, then go down to network connections on 'manager', **right-click on CEDUNA-NETWORK and click disconnect. This is important.** | ||
| Now you are done! | Now you are done! | ||
| + | |||
| + | Brett is the expert on this setup, so if anything is not as described above, he is the best contact person. | ||
| + | |||
| + | Not really in the ideal spot, however, not sure I have the ability to add to the RA wiki -Tiege 14/08/17 | ||
| + | |||
/home/www/auscope/opswiki/data/pages/operations/documentation.errors.txt · Last modified: 2017/09/27 06:29 by Jamie McCallum
Page Tools
