Differences

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

--- installation_configuration [2017/06/19 11:07] – [Install the MF Packaging software] walkeradmin
+++ installation_configuration [2023/03/09 22:35] (current) – external edit 127.0.0.1
@@ Line 133: / Line 133: @@
 ./install.sh –standalone
 </file>
+\\
 Once the installation is completed and successfully processed, your MFVP Packaging server is ready for use.
 \\
 \\
 To check the installation and access your MFVP Packaging server user interface, open a web browser
-from a computer that has a network access to your server and enter the following address: http://
+from a computer that has a network access to your server and enter the following address: [[http://
-[LocalIPServer]:8080
+[LocalIPServer]:8080]]
 \\
 \\
 By default, the configuration is automatically done by the install.sh with the following values:
 \\
+    • LocalIP: first IP found (excluding 127.0.0.1)
+    • serverID: standalone
 \\
-• LocalIP: first IP found (excluding 127.0.0.1)
-• serverID: standalone
 To change these values, proceed with the following configuration step.
 \\
@@ Line 154: / Line 155: @@
 \\
     # /opt/mfvp/packaging/setup/configure.sh --localIP X.X.X.X --serverID XX
-\\
-• localIP:x.x.x.x corresponds to the management IP address for this server.\\
+    • localIP:x.x.x.x corresponds to the management IP address for this server.\\
-• serverID=xx: xx corresponds to your Server ID for this server (example: packaging_01). The server ID is used as the server name in the user interface. Default value is standalone.
+    • serverID=xx: xx corresponds to your Server ID for this server (example: packaging_01). The server ID is used as the server name in the user interface. Default value is standalone.
 \\
 For my server, I would use something like:
@@ Line 166: / Line 167: @@
 \\
 Test the server by navigating your browser to http://localserverip:8080
+\\
+\\
+===== NTP Settings =====
+The time source of the Packager, and the Encoder producing the ABR output should be from the same source. Faiure to properly time synchronise can result in the packager discarding data that is 'outside' sync times.
+\\
+\\
+==== Configure TimeZone ====
+Remove the local time file, in case it contains incorrect settings:
+\\
+    rm /etc/localtime
+\\
+\\
+Now re-create the local time file using UTC time.
+\\
+    ln -s /usr/share/zoneinfo/UTC /etc/localtime
+\\
+\\
+==== Configure NTP ====
+Define the ntp server you wish to use in the ntp.conf file.
+\\
+    vi /etc/ntp.conf
+\\
+Add your ntp server to the server list, as below
+\\
+\\
+# Use public servers from the pool.ntp.org project.\\
+# Please consider joining the pool (http://www.pool.ntp.org/join.html).
+<color #ed1c24>\\
+server 137.58.71.251 iburst</color>\\
+# server 0.centos.pool.ntp.org iburst\\
+# server 1.centos.pool.ntp.org iburst\\
+# server 2.centos.pool.ntp.org iburst\\
+# server 3.centos.pool.ntp.org iburst\\
+\\
+\\
+Save the file and exit (:wq)
+\\
+\\
+Stop the NTP daemon
+\\
+    service ntpd stop
+\\
+Force the synchronisation with the NTP server
+\\
+    ntpdate 137.58.71.251
+\\
+Restart the ntp daemon
+\\
+    service ntpd restart
+\\
+Verify the ntp synchronization
+\\
+    ntpstat
+\\
+It should return “synchronized, as below:
+\\
+<file>
+synchronised to NTP server (188.39.213.7) at stratum 2
+   time correct to within 48 ms
+   polling server every 1024 s
+</file>
+\\
+\\
+==== 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
+\\
+    /etc/sysconfig/network-scripts.
+\\
+==== Create a route file for the interface you want (eth2 in this example) ====
+\\
+    vi /etc/sysconfig/network-scripts/route-eth2
+\\
+Enter your routing syntax
+\\
+<file>
+GATEWAY0=11.0.100.1
+NETMASK0=255.0.0.0
+ADDRESS0=239.0.0.0
+</file>
+\\
+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 'Gateway' in this instance is an interface address.
+\\
+\\
+Save and close the file. Restart networking:
+\\
+    service network restart
+\\
+Verify new routing table:
+\\
+    route
+\\
+Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
+\\
+\\
+.168.27.0    *               255.255.255.0   U     0      0        0 eth0\\
+link-local      *               255.255.0.0     U     1002   0        0 eth2\\
+link-local      *               255.255.0.0     U     1003   0        0 eth3\\
+link-local      *               255.255.0.0     U     1004   0        0 eth4\\
+link-local      *               255.255.0.0     U     1005   0        0 eth5\\
+link-local      *               255.255.0.0     U     1006   0        0 eth0\\
+link-local      *               255.255.0.0     U     1007   0        0 eth1\\
+link-local      *               255.255.0.0     U     1008   0        0 eth7\\
+link-local      *               255.255.0.0     U     1009   0        0 eth6\\
+<color #ed1c24>239.0.0.0       11.0.100.1      255.0.0.0       UG    0      0        0 eth2</color> \\
+.0.0.0        *               255.0.0.0       U     0      0        0 eth4\\
+.0.0.0        *               255.0.0.0       U     0      0        0 eth2\\
+default         192.168.27.254  0.0.0.0         UG    0      0        0 eth0\\
+\\
+\\
+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, the internal storage should be enough to provide an overview of what the product capabilities are, without provision or integration of extra storage. For this reason, we will just use the internal storage of the packager.
+\\
+==== Define a Publication Folder ====
+To create your sharing folder on your server. Navigate to:
+\\
+    /opt/mfvp/mnt
+\\
+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 /opt/mfvp/mnt where we will publish to.
+\\
+<file>
+cd /opt/mfvp/mnt
+mkdir nas
+chown -R envivio:envivio nas
+</file>
+\\
+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.
+\\
 \\