About Omneon MediaGrid - Harmonic Inc
About Omneon MediaGrid - Harmonic Inc About Omneon MediaGrid - Harmonic Inc
System Configuration If a mount command is issued immediately after loading the omfs module, the command may fail with an error message indicating, “Some resources could not be allocated, try again later.” Reissue the mount command later. This message indicates that the omfs module has not completed allocation of memory after loading. The Linux FSD does not request any large memory allocations during operation. The memory allocated at startup must be sufficient to accommodate the file buffer settings. The amount of memory allocated by the Linux FSD is controlled by the omfs_cache_pre_allocate system control variable. This parameter can be modified using the following command: sysctl omfs_cache_pre_allocate=2047 It can also be modified by inserting the following line into the /etc/sysctl.conf file: omfs_cache_pre_allocate=2047 The value is specified in units of 256KB. The default value is 2047, which is slightly less than 512MB. On a computer with 1GB RAM there will be 512MB left for other system operations. The Linux FSD will not release any memory it has acquired. Reducing the omfs_cache_pre_allocate value after memory has been allocated has no effect. Since the Linux FSD begins allocating memory as soon as the omfs module is loaded by the Linux kernel, trying to limit the amount of memory allocated to a value below 512MB using this method produces inconsistent results. To limit the memory usage to below 512MB, use the cachePreAllocLimit module load parameter. For example, when loading the omfs module with the modprobe command use the following format: modprobe omfs cachePreAllocLimit=40 The example above limits the Linux FSD to using only 10MB for cache memory. This parameter may also be used in the /etc/modprobe.conf configuration file. Specifying Buffer Memory for Windows Clients To configure the amount of memory used for ReadAhead buffering, refer to Setting Windows FSD Parameters. The memory used is specified in units of slices. For example, if each slice is 8MB in size, setting ReadAhead=2 would consume 16MB of memory for each active file. The default value is ReadAhead=3. To configure the amount of memory used for cache memory limit: IMPORTANT: The following procedure involves modifying the Windows registry. If you are unsure of the changes, please contact Omneon Technical Support for assistance. The default limit for the MaximumCacheSize value is four times that of the InitialcacheSize, which is calculated based on system physical memory size. 1. Start the regedit.exe program. (If the computer does not fully boot, boot in safe mode first). 2. Navigate to the following registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OmRdr\Parameters 3. Create a DWORD value in the above registry key with the name cacheMaxMem. 134 Installation and Configuration Guide
System Configuration 4. Set the value of the new DWORD to the desired memory. This value is in Megabytes. (Omneon recommends 200 or 400 for most cases). Specifying Maximum File Open Limit on a Linux Client To specify the maximum number of files that can be open at any time: 1. Type the following command: mount –t omfs /mediagrid/filesys /mnt –o username=username,password=password,readahead=2,filelimit=80 2. Set the file limit to the desired value. The above command sets the total number of simultaneously open files to 80. The default filelimit is 1024. Note that this is a Linux FSD option only. Configuring the Remote Media API on a ContentBridge Follow these steps if you would like to initiate transfers of clips using the Omneon Remote Media API on a ContentBridge. You will need to edit the ContentBridge configuration file to enable this functionality. The Remote Media API version can be selected by editing the MEDIA_API_VERSION parameter in the ContentBridge configuration file. For information on supported versions, refer to the Omneon MediaGrid Release Notes. For information on editing the configuration file, refer to Editing the ContentBridge Configuration File in the Omneon SystemManager User Guide. To configure the remote Media API: 1. Obtain copies of ommcp.exe and ommedia.dll from Omneon Engineering. 2. Ensure that the ContentBridge is configured correctly. Following is an example setup: Spectrum Server hostname (or IP): om-spect Filesystem name /fs0 Content Director hostname (or IP): om-cld Filesystem name /mg0 Content Bridge hostname (or IP): 10.3.1.40 serial number: CLB01523 NOTE: Short hostnames are supported in the ContentBridge configuration file if the hostname has the same domain name as the Omneon MediaGrid system being configured. Otherwise, a fully qualified domain name (FQDN) must be specified in the configuration file if you wish to use hostnames. Note that remote ommcp's will only work using the exact hostname or IP address specified in the configuration file. 3. Make sure that the desired mount type(s) is specified in the ContentBridge configuration boot file /tftpboot/config/gateway/ across all ContentDirectors. Note that on a ContentBridge there are three different types of remote mounts utilized. “CB” (ContentBridge) mounts are used for configuring a ContentBridge to share out a file system from a specific Omneon MediaGrid cluster via CIFS, FTP, AFP, and NFS. The other two types of mount points are utilized Omneon, Now Part of Harmonic 135
- Page 107 and 108: CHAPTER 3 System Configuration This
- Page 109 and 110: Password: OVN@SvCaUsa 3. Enter the
- Page 111 and 112: System Configuration 4. If you are
- Page 113 and 114: 6. Apply power to the ContentServer
- Page 115 and 116: Notes on Active Directory Configura
- Page 117 and 118: Follow the prompts to initialize th
- Page 119 and 120: Joining an Omneon MediaGrid Cluster
- Page 121 and 122: 1. From your SSH terminal, edit /et
- Page 123 and 124: A list of users in the domain displ
- Page 125 and 126: System Configuration 1. After confi
- Page 127 and 128: 4. Type the following commands to r
- Page 129 and 130: The expected result is: Domain=[SNV
- Page 131 and 132: System Configuration This mount poi
- Page 133 and 134: System Configuration c. Replace wi
- Page 135 and 136: Modify the file as follows: System
- Page 137 and 138: Omneon MediaGrid name ContentDirect
- Page 139 and 140: Editing the LDAP Configuration File
- Page 141 and 142: System Configuration 4. Create a Sa
- Page 143 and 144: Modify the file as follows: System
- Page 145 and 146: Figure 43. Server Admin Open Direct
- Page 147 and 148: The following is a sample output fr
- Page 149 and 150: System Configuration a. Replace dom
- Page 151 and 152: System Configuration NOTE: Upon joi
- Page 153 and 154: To verify the service: 1. Type the
- Page 155 and 156: System Configuration configurations
- Page 157: To configure the amount of memory u
- Page 161 and 162: System Configuration 9. As the tran
- Page 163 and 164: The acceptable options are “YES
- Page 165 and 166: CHAPTER 4 Installing the File Syste
- Page 167 and 168: Installing the File System Driver s
- Page 169 and 170: Installing the File System Driver 3
- Page 171 and 172: CHAPTER 5 Accessing the Omneon Medi
- Page 173 and 174: Figure 45. Omneon MediaGrid Login A
- Page 175 and 176: Accessing the Omneon MediaGrid •
- Page 177 and 178: Automatically Mounting a File Syste
- Page 179 and 180: 11. Click the Browse button and the
- Page 181 and 182: Figure 53. Connect to Omneon MediaG
- Page 183 and 184: Figure 54. Automatic MediaGrid Conn
- Page 185 and 186: Accessing the Omneon MediaGrid Moun
- Page 187 and 188: Table 4. Mount Options (Continued)
- Page 189 and 190: Table 5. Mount Options (Continued)
- Page 191 and 192: Accessing the Omneon MediaGrid To u
- Page 193 and 194: Figure 58. MyDir Properties Accessi
- Page 195 and 196: Accessing the Omneon MediaGrid •
- Page 197 and 198: Using AFP on a Macintosh Client Fol
- Page 199 and 200: Accessing the Omneon MediaGrid For
- Page 201 and 202: CHAPTER 6 Administrative Procedures
- Page 203 and 204: Table 6. mgcopy Values Values Descr
- Page 205 and 206: Figure 60. Firmware Version Selecti
- Page 207 and 208: Administrative Procedures Use the f
System Configuration<br />
4. Set the value of the new DWORD to the desired memory. This value is in Megabytes. (<strong>Omneon</strong><br />
recommends 200 or 400 for most cases).<br />
Specifying Maximum File Open Limit on a Linux Client<br />
To specify the maximum number of files that can be open at any time:<br />
1. Type the following command:<br />
mount –t omfs /mediagrid/filesys /mnt<br />
–o username=username,password=password,readahead=2,filelimit=80<br />
2. Set the file limit to the desired value.<br />
The above command sets the total number of simultaneously open files to 80. The default filelimit<br />
is 1024. Note that this is a Linux FSD option only.<br />
Configuring the Remote Media API on a ContentBridge<br />
Follow these steps if you would like to initiate transfers of clips using the <strong>Omneon</strong> Remote Media API<br />
on a ContentBridge. You will need to edit the ContentBridge configuration file to enable this<br />
functionality.<br />
The Remote Media API version can be selected by editing the MEDIA_API_VERSION parameter in<br />
the ContentBridge configuration file. For information on supported versions, refer to the <strong>Omneon</strong><br />
<strong>MediaGrid</strong> Release Notes. For information on editing the configuration file, refer to Editing the<br />
ContentBridge Configuration File in the <strong>Omneon</strong> SystemManager User Guide.<br />
To configure the remote Media API:<br />
1. Obtain copies of ommcp.exe and ommedia.dll from <strong>Omneon</strong> Engineering.<br />
2. Ensure that the ContentBridge is configured correctly. Following is an example setup:<br />
Spectrum Server hostname (or IP): om-spect Filesystem name /fs0<br />
Content Director hostname (or IP): om-cld Filesystem name /mg0<br />
Content Bridge hostname (or IP): 10.3.1.40 serial number: CLB01523<br />
NOTE: Short hostnames are supported in the ContentBridge configuration file if the hostname has the same<br />
domain name as the <strong>Omneon</strong> <strong>MediaGrid</strong> system being configured. Otherwise, a fully qualified domain name<br />
(FQDN) must be specified in the configuration file if you wish to use hostnames. Note that remote ommcp's<br />
will only work using the exact hostname or IP address specified in the configuration file.<br />
3. Make sure that the desired mount type(s) is specified in the ContentBridge configuration boot file<br />
/tftpboot/config/gateway/ across all ContentDirectors. Note that on a<br />
ContentBridge there are three different types of remote mounts utilized. “CB” (ContentBridge)<br />
mounts are used for configuring a ContentBridge to share out a file system from a specific <strong>Omneon</strong><br />
<strong>MediaGrid</strong> cluster via CIFS, FTP, AFP, and NFS. The other two types of mount points are utilized<br />
<strong>Omneon</strong>, Now Part of <strong>Harmonic</strong> 135
Change language