User Tools
databaseandnetworkmanagement:kumu_networks
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| databaseandnetworkmanagement:kumu_networks [2022/01/24 20:15] – slawrence | databaseandnetworkmanagement: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 |
| - | kumuapps2.err | + | |
| - | kumuesk1.err | + | |
| - | kumulb.err | + | |
| - | kumulbdbrmq.err | + | |
| - | kumuoat1.err | + | |
| - | kumuoat2.err | + | |
| - | Currently, the system is only running the MDC agent on kumuoat1.err. | + | **Currently, the system is only running the MDC agent on kumuoat1.err. |
| - | The MDC purely runs on kumuoat1.err, | + | The MDC purely runs on kumuoat1.err, |
| - | 1. sudo systemctl stop orchestrator; | + | - |
| - | 2. sudo systemctl stop tracker; | + | |
| - | 3. sudo pkill -f rdfagent; | + | |
| - | Then run: | + | **Then run: |
| + | ** | ||
| + | - sudo semanage permissive -a ipsec_t | ||
| + | - sudo sysctl -w net.ipv4.tcp_timestamps=0 | ||
| + | - sudo systemctl start strongswan | ||
| + | - sudo systemctl start orchestrator | ||
| + | - sudo systemctl start tracker | ||
| - | 1. sudo semanage permissive -a ipsec_t | + | **Make sure you get positive ping results from: |
| - | 2. sudo sysctl | + | ** |
| - | 3. sudo systemctl start strongswan | + | |
| + | |||
| + | or the like, some production IP, which is available in the MySQL orch db at kumuesk1.err element table. | ||
| - | Make sure you get positive ping results from: | + | ** |
| + | Contact shea.lawrence@errigal.com (415-559-8389) if you have any questions. | ||
| - | 1. | + | NOTE: If disk space fills up, then you need to delete the / |
| - | or the like, some production IP, which is available in the MySQL orch db at kumuesk1.err element table. | + | NOTE: Currently, please do not start up the MDC on kumuoat2. |
| + | |||
| + | 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 / | ||
| + | // | ||
| + | NOTE: There is a script on kumuoat1.err -> / | ||
| + | This script can fully reboot the MDC with the VPN and all running. Please run as "sudo ./ | ||
databaseandnetworkmanagement/kumu_networks.1643055353.txt.gz · Last modified: 2022/01/24 20:15 by slawrence
Page Tools
