installation_configuration
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
installation_configuration [2017/06/19 11:39] – [Configure TimeZone] walkeradmin | installation_configuration [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 188: | Line 188: | ||
\\ | \\ | ||
vi / | vi / | ||
- | \\ | ||
\\ | \\ | ||
Add your ntp server to the server list, as below | Add your ntp server to the server list, as below | ||
\\ | \\ | ||
\\ | \\ | ||
- | # Use public servers from the pool.ntp.org project. | + | # Use public servers from the pool.ntp.org project.\\ |
# Please consider joining the pool (http:// | # Please consider joining the pool (http:// | ||
- | <color # | + | <color #ed1c24>\\ |
- | # server 0.centos.pool.ntp.org iburst | + | server 137.58.71.251 iburst</ |
- | # server 1.centos.pool.ntp.org iburst | + | # server 0.centos.pool.ntp.org iburst\\ |
- | # server 2.centos.pool.ntp.org iburst | + | # server 1.centos.pool.ntp.org iburst\\ |
- | # server 3.centos.pool.ntp.org iburst | + | # server 2.centos.pool.ntp.org iburst\\ |
+ | # server 3.centos.pool.ntp.org iburst\\ | ||
\\ | \\ | ||
\\ | \\ | ||
Line 208: | Line 208: | ||
\\ | \\ | ||
service ntpd stop | service ntpd stop | ||
- | \\ | ||
\\ | \\ | ||
Force the synchronisation with the NTP server | Force the synchronisation with the NTP server | ||
\\ | \\ | ||
ntpdate 137.58.71.251 | ntpdate 137.58.71.251 | ||
- | \\ | ||
\\ | \\ | ||
Restart the ntp daemon | Restart the ntp daemon | ||
\\ | \\ | ||
service ntpd restart | service ntpd restart | ||
- | \\ | ||
\\ | \\ | ||
Verify the ntp synchronization | Verify the ntp synchronization | ||
\\ | \\ | ||
ntpstat | ntpstat | ||
- | \\ | ||
\\ | \\ | ||
It should return “synchronized, | It should return “synchronized, | ||
- | \\ | ||
\\ | \\ | ||
< | < | ||
Line 235: | Line 230: | ||
\\ | \\ | ||
\\ | \\ | ||
+ | ==== Define the Multicast routes for the ingest ==== | ||
+ | This is very important. Unlike previous packager products, the ingest interface is not selected from the GUI, so we must define at the OS level where our multicast sources are coming from, and on what interface. | ||
+ | \\ | ||
+ | \\ | ||
+ | In the sample below, we will define that all multicast traffic in the range 239.X.Y.Z will be listened on the eth2 interface. | ||
+ | \\ | ||
+ | \\ | ||
+ | To do this, navigate to the location where all the interface configuration files are held | ||
+ | \\ | ||
+ | / | ||
+ | \\ | ||
+ | ==== Create a route file for the interface you want (eth2 in this example) ==== | ||
+ | \\ | ||
+ | vi / | ||
+ | \\ | ||
+ | Enter your routing syntax | ||
+ | \\ | ||
+ | < | ||
+ | GATEWAY0=11.0.100.1 | ||
+ | NETMASK0=255.0.0.0 | ||
+ | ADDRESS0=239.0.0.0 | ||
+ | </ | ||
+ | \\ | ||
+ | This will route all multicast traffic requests on 239.X.Y.Z scope to interface Eth2, which has the IP address 11.0.100.1. The ' | ||
+ | \\ | ||
+ | \\ | ||
+ | Save and close the file. Restart networking: | ||
+ | \\ | ||
+ | service network restart | ||
+ | \\ | ||
+ | Verify new routing table: | ||
+ | \\ | ||
+ | route | ||
+ | \\ | ||
+ | Destination | ||
+ | \\ | ||
+ | \\ | ||
+ | 192.168.27.0 | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | link-local | ||
+ | <color # | ||
+ | 10.0.0.0 | ||
+ | 11.0.0.0 | ||
+ | default | ||
+ | \\ | ||
+ | \\ | ||
+ | Verify you can see the multicast route | ||
+ | \\ | ||
+ | \\ | ||
+ | ==== Mount a NAS ==== | ||
+ | For anyone wanting to store a large amount of data, a NAS will be required as the standard G6/G7 does not have enough storage for hours of date from multiple services. | ||
+ | \\ | ||
+ | \\ | ||
+ | However, for most demonstration applications, | ||
+ | \\ | ||
+ | ==== Define a Publication Folder ==== | ||
+ | To create your sharing folder on your server. Navigate to: | ||
+ | \\ | ||
+ | / | ||
+ | \\ | ||
+ | Even if you are not publishing on a NAS, you will need to create a publication folder in this repository. | ||
+ | \\ | ||
+ | \\ | ||
+ | In the example below, we are creating a nas folder in / | ||
+ | \\ | ||
+ | < | ||
+ | cd / | ||
+ | mkdir nas | ||
+ | chown -R envivio: | ||
+ | </ | ||
+ | \\ | ||
+ | You need to change the group and owner of the folder you are publishing to using chown in order to give CentOS the rights to publish in this folder. | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
installation_configuration.1497868749.txt.gz · Last modified: 2023/03/09 22:35 (external edit)