Difference between revisions of "Computers"
Jump to navigation
Jump to search
imported>Bob |
|||
| (16 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
Stub here to act as a table of contents sorts to our important computers / servers / related information. | Stub here to act as a table of contents sorts to our important computers / servers / related information. | ||
===Loggernet Systems=== | ===Loggernet Systems=== | ||
| − | [https://docs.google.com/a/alaska.edu/spreadsheets/d/1CFV-2dh7pPBvACJbi8AFLTF7aF6Bf3JSwRjbcY5aBMY/edit?usp=sharing LoggerNet configuration] (Partial GIPL & IARC)<br> | + | * Lognet (listed lower on the page) - [https://docs.google.com/a/alaska.edu/spreadsheets/d/1CFV-2dh7pPBvACJbi8AFLTF7aF6Bf3JSwRjbcY5aBMY/edit?usp=sharing LoggerNet configuration] (Partial GIPL & IARC)<br> |
* Monitor real time connections here: | * Monitor real time connections here: | ||
** http://ngeedata.iarc.uaf.edu/data/data.html | ** http://ngeedata.iarc.uaf.edu/data/data.html | ||
| + | * Super Site Debian Laptop | ||
| + | ** exclusively handles Super-site Data loggers at Poker Flat Research Range on an MD485 wired network | ||
===Serial Server Systems=== | ===Serial Server Systems=== | ||
| Line 9: | Line 11: | ||
[[Several Important Network Devices]] (Covers much of the same ground)<br> | [[Several Important Network Devices]] (Covers much of the same ground)<br> | ||
* [https://docs.google.com/a/alaska.edu/document/d/1rRO1Ess8hwZkxBgZB5HRP-FZ8u2NcKENp2TvAYmtYTE/edit?usp=sharing Fairbanks IARC Base Station server (Ralph) Configuration]<br> | * [https://docs.google.com/a/alaska.edu/document/d/1rRO1Ess8hwZkxBgZB5HRP-FZ8u2NcKENp2TvAYmtYTE/edit?usp=sharing Fairbanks IARC Base Station server (Ralph) Configuration]<br> | ||
| + | ** follow that link for data radio setup, too. | ||
* [https://docs.google.com/a/alaska.edu/document/d/1cvtqjE0w6MpFALUuruchsc71XF1WgvOJFbtLxnAWBQo/edit?usp=sharing Barrow Base Station server (Trout) Configuration]<br> | * [https://docs.google.com/a/alaska.edu/document/d/1cvtqjE0w6MpFALUuruchsc71XF1WgvOJFbtLxnAWBQo/edit?usp=sharing Barrow Base Station server (Trout) Configuration]<br> | ||
| Line 16: | Line 19: | ||
* [[Ser2Net Config Reference]] (Hopefully this reflects all of them) | * [[Ser2Net Config Reference]] (Hopefully this reflects all of them) | ||
| − | |||
| − | |||
* '''Barrow Dreamplug''' -- Kind of decommissioned at this point. | * '''Barrow Dreamplug''' -- Kind of decommissioned at this point. | ||
| + | ** Related though is [https://docs.google.com/document/d/1YK5Bt3QrWyU5LtWgWrdJ9skdwRxcxilH--8yFzSlQJ4/edit# Network Information on Barrow] | ||
** It is old and still up in Barrow in the control shed. Still works but I sent the raspberry pis up to replace it. My plan is to replace it with a small server with a different computer architecture this winter. The reason for that over these small ARM processors is that I'm still trying to work around this weak telemetry problem. Thinking that if it is an x86 (well 64 bit but that style of CPU) that we can leave a copy of loggernet running up there so that when the network goes down as long as the unit is on we are still in business. I am working to put all of its configs in one location though. What was unique to it that hasn't been documented yet is that it used its second ethernet port as a DHCP server in support of a PTZ web cam. That required an additional package, special iptables rules, and some scripts in /usr/local/bin. On the to do list to get going at some point. | ** It is old and still up in Barrow in the control shed. Still works but I sent the raspberry pis up to replace it. My plan is to replace it with a small server with a different computer architecture this winter. The reason for that over these small ARM processors is that I'm still trying to work around this weak telemetry problem. Thinking that if it is an x86 (well 64 bit but that style of CPU) that we can leave a copy of loggernet running up there so that when the network goes down as long as the unit is on we are still in business. I am working to put all of its configs in one location though. What was unique to it that hasn't been documented yet is that it used its second ethernet port as a DHCP server in support of a PTZ web cam. That required an additional package, special iptables rules, and some scripts in /usr/local/bin. On the to do list to get going at some point. | ||
| + | * [[Decommisioned Serial Server Config and notes]] | ||
===Virtual Machines=== | ===Virtual Machines=== | ||
What is a [[Virtual Machine]]?<br> | What is a [[Virtual Machine]]?<br> | ||
| − | ==== | + | ====LogNet==== |
Primary LoggerNet server | Primary LoggerNet server | ||
* CentOS Linux virtual machine | * CentOS Linux virtual machine | ||
| Line 29: | Line 32: | ||
* Function is ''main LoggerNet server'' for related projects. | * Function is ''main LoggerNet server'' for related projects. | ||
* This computer pushes data to ngeedata after automated retrievals. | * This computer pushes data to ngeedata after automated retrievals. | ||
| + | * [https://docs.google.com/a/alaska.edu/spreadsheets/d/1CFV-2dh7pPBvACJbi8AFLTF7aF6Bf3JSwRjbcY5aBMY/edit?usp=sharing LoggerNet configuration] (Partial GIPL & IARC) | ||
====NGEEDATA==== | ====NGEEDATA==== | ||
| Line 35: | Line 39: | ||
* Located in IARC server room | * Located in IARC server room | ||
* Function is ''main data processing server'' and ''web server'' for sharing data with 3rd parties | * Function is ''main data processing server'' and ''web server'' for sharing data with 3rd parties | ||
| − | + | * Online repositories for processing scripts: | |
| + | ** Cron related: https://github.alaska.edu/rcbusey/processing_bash_scripts | ||
| + | ** Bash Utilities: https://github.alaska.edu/rcbusey/bash_utilities | ||
| + | ** Python Utilities: https://github.alaska.edu/rcbusey/python_utilities | ||
| + | ** DataPro V3 & other python utilities from Ross: https://github.com/rwspicer/csv_utilities | ||
| + | ====WERC==== | ||
| + | Similar to NGEEDATA | ||
| + | * Debian VM | ||
| + | * Function is ''main data processing server'' and ''web server'' for sharing data with 3rd parties | ||
| + | * [[werc.uaf]] | ||
===Other=== | ===Other=== | ||
| − | [[High precision computer logger]] | + | * [[High precision computer logger]] |
| + | * [[Airplane Computer 2016]] | ||
| + | * http://www.jubilinux.org/ (for edison installations rather than raspberry pi. | ||
===Other Important Information=== | ===Other Important Information=== | ||
| − | [[Initial Debian Server Setup]]<br> | + | * [[Initial Debian Server Setup]]<br> |
| − | [[Baud Rate Backgrounder]] - (I know...)<br> | + | * [[Baud Rate Backgrounder]] - (I know...)<br> |
| + | * [[Automated System Work Flow]] | ||
| + | * [[IP Tables Firewall Example]] | ||
| + | * Disable Autoreboot in windows 10 update: http://www.tenforums.com/windows-updates-activation/17530-disable-automatic-reboot-updates.html | ||
| + | * Side note: If you do any buliding of these low power linux systems, start with an industrial microSD card. Have had intermittent issues with memory corruption on consumer grade cards. Search digikey etc for extended temperature industrial models. SLC or MLC and temperature range to -25C or -40C is easy to find there. Similar deal for the Compact Flash cards for the CSI cmf100. | ||
| + | * Related... I've kind of standardized on 16 or 32GB industrial cards. to back them up I use the command line tool dd: | ||
| + | dd if=/dev/sdb of=backupofsystem.img bs=4096 | ||
| + | * that creates a pretty large file that is mostly empty. So, follow this page to shrink things: | ||
| + | ** https://softwarebakery.com/shrinking-images-on-linux | ||
| + | ** I guess the alternative is to just gzip the large file... then use dd to copy the file onto new media: | ||
| + | dd if=backpuofsystem.img of=/dev/sdb bs=4096 | ||
| + | ** if say the image is 32gb but the media is a 16gb card the file system will extend beyond the length of the card. That caused a boot error (of course) but I was able to use gparted the tool mentioned on the softwarebakery link to resize the file system on the new card. | ||
| + | * https://serverfault.com/questions/363922/how-to-move-files-with-scp | ||
Latest revision as of 18:49, 30 July 2018
Stub here to act as a table of contents sorts to our important computers / servers / related information.
Contents
Loggernet Systems
- Lognet (listed lower on the page) - LoggerNet configuration (Partial GIPL & IARC)
- Monitor real time connections here:
- Super Site Debian Laptop
- exclusively handles Super-site Data loggers at Poker Flat Research Range on an MD485 wired network
Serial Server Systems
What is a Serial Server?
Several Important Network Devices (Covers much of the same ground)
- Fairbanks IARC Base Station server (Ralph) Configuration
- follow that link for data radio setup, too.
- Barrow BARC bandwidth tester (Grayling)Configuration
- Lab 113 (Salmon) Configuration
- Ser2Net Config Reference (Hopefully this reflects all of them)
- Barrow Dreamplug -- Kind of decommissioned at this point.
- Related though is Network Information on Barrow
- It is old and still up in Barrow in the control shed. Still works but I sent the raspberry pis up to replace it. My plan is to replace it with a small server with a different computer architecture this winter. The reason for that over these small ARM processors is that I'm still trying to work around this weak telemetry problem. Thinking that if it is an x86 (well 64 bit but that style of CPU) that we can leave a copy of loggernet running up there so that when the network goes down as long as the unit is on we are still in business. I am working to put all of its configs in one location though. What was unique to it that hasn't been documented yet is that it used its second ethernet port as a DHCP server in support of a PTZ web cam. That required an additional package, special iptables rules, and some scripts in /usr/local/bin. On the to do list to get going at some point.
- Decommisioned Serial Server Config and notes
Virtual Machines
What is a Virtual Machine?
LogNet
Primary LoggerNet server
- CentOS Linux virtual machine
- Located in IARC server room
- Function is main LoggerNet server for related projects.
- This computer pushes data to ngeedata after automated retrievals.
- LoggerNet configuration (Partial GIPL & IARC)
NGEEDATA
Primary Data processing server & data sharing web server
- Debian Linux virtual machine
- Located in IARC server room
- Function is main data processing server and web server for sharing data with 3rd parties
- Online repositories for processing scripts:
- Cron related: https://github.alaska.edu/rcbusey/processing_bash_scripts
- Bash Utilities: https://github.alaska.edu/rcbusey/bash_utilities
- Python Utilities: https://github.alaska.edu/rcbusey/python_utilities
- DataPro V3 & other python utilities from Ross: https://github.com/rwspicer/csv_utilities
WERC
Similar to NGEEDATA
- Debian VM
- Function is main data processing server and web server for sharing data with 3rd parties
- werc.uaf
Other
- High precision computer logger
- Airplane Computer 2016
- http://www.jubilinux.org/ (for edison installations rather than raspberry pi.
Other Important Information
- Initial Debian Server Setup
- Baud Rate Backgrounder - (I know...)
- Automated System Work Flow
- IP Tables Firewall Example
- Disable Autoreboot in windows 10 update: http://www.tenforums.com/windows-updates-activation/17530-disable-automatic-reboot-updates.html
- Side note: If you do any buliding of these low power linux systems, start with an industrial microSD card. Have had intermittent issues with memory corruption on consumer grade cards. Search digikey etc for extended temperature industrial models. SLC or MLC and temperature range to -25C or -40C is easy to find there. Similar deal for the Compact Flash cards for the CSI cmf100.
- Related... I've kind of standardized on 16 or 32GB industrial cards. to back them up I use the command line tool dd:
dd if=/dev/sdb of=backupofsystem.img bs=4096
- that creates a pretty large file that is mostly empty. So, follow this page to shrink things:
- https://softwarebakery.com/shrinking-images-on-linux
- I guess the alternative is to just gzip the large file... then use dd to copy the file onto new media:
dd if=backpuofsystem.img of=/dev/sdb bs=4096
- if say the image is 32gb but the media is a 16gb card the file system will extend beyond the length of the card. That caused a boot error (of course) but I was able to use gparted the tool mentioned on the softwarebakery link to resize the file system on the new card.
- https://serverfault.com/questions/363922/how-to-move-files-with-scp
