Internal Errigal Collaboration Wiki

User Tools

Site Tools

Trace:
databaseandnetworkmanagement:kumu_networks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
databaseandnetworkmanagement:kumu_networks [2022/01/24 20:32] – slawrencedatabaseandnetworkmanagement:kumu_networks [2022/01/25 17:48] (current) – slawrence
Line 1: Line 1:
-Kumu is an on-boarding customer.+**Kumu is an on-boarding customer.
  
-We have 1 lab relay and 3 production relays.+We have 1 lab relay and 3 production relays.**
  
-There is an AWS instance that is running our production trial environment.+**There is an AWS instance that is running our production trial environment. 
 +**
  
   * kumuapps1.err   * kumuapps1.err
Line 13: Line 14:
   * kumuoat2.err   * kumuoat2.err
  
-Currently, the system is only running the MDC agent on kumuoat1.err.  kumuoat2.err functionality has been shut down (more on that later).+**Currently, the system is only running the MDC agent on kumuoat1.err.  kumuoat2.err functionality has been shut down (more on that later).
  
-The MDC purely runs on kumuoat1.err, though we have a strange VPN currently.  If the kumuoat1.err server is restarted, please stop all MDC services:+The MDC purely runs on kumuoat1.err, though we have a strange VPN currently.  If the kumuoat1.err server is restarted, please stop all MDC services:**
  
   -  sudo systemctl stop orchestrator;   -  sudo systemctl stop orchestrator;
Line 21: Line 22:
   -  sudo pkill -f rdfagent;   -  sudo pkill -f rdfagent;
  
-Then run: +**Then run: 
- +** 
-  -  sudo semanage permissive -a ipsec_t +  - sudo semanage permissive -a ipsec_t 
-  -  sudo sysctl -w net.ipv4.tcp_timestamps=0 +  - sudo sysctl -w net.ipv4.tcp_timestamps=0 
-  -  sudo systemctl start strongswan +  - sudo systemctl start strongswan 
- +  - sudo systemctl start orchestrator 
-Make sure you get positive ping results from:+  - sudo systemctl start tracker
  
 +**Make sure you get positive ping results from:
 +**
   -  ping 10.8.1.8   -  ping 10.8.1.8
      
 or the like, some production IP, which is available in the MySQL orch db at kumuesk1.err element table. or the like, some production IP, which is available in the MySQL orch db at kumuesk1.err element table.
  
 +**
 Contact shea.lawrence@errigal.com (415-559-8389) if you have any questions. Contact shea.lawrence@errigal.com (415-559-8389) if you have any questions.
  
Line 40: Line 43:
 NOTE: Currently, please do not start up the MDC on kumuoat2.  The playbook may do that.  We are simply in a period where running on both may cause complications, which is being investigated.  Thanks! NOTE: Currently, please do not start up the MDC on kumuoat2.  The playbook may do that.  We are simply in a period where running on both may cause complications, which is being investigated.  Thanks!
  
 +NOTE:  As per usual, you can generally see if the MDC Agent is running simply by tailing the log file with something like:**
 +
 +//sudo tail -f /home/rdfagent/rdfagent/logs/agent/spring.log
 +//
  
 +NOTE:  There is a script on kumuoat1.err -> /home/scotty/start_commands.sh
 +This script can fully reboot the MDC with the VPN and all running. Please run as "sudo ./start_commands.sh".
databaseandnetworkmanagement/kumu_networks.1643056329.txt.gz · Last modified: 2022/01/24 20:32 by slawrence

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki