About Omneon MediaGrid - Harmonic Inc
About Omneon MediaGrid - Harmonic Inc About Omneon MediaGrid - Harmonic Inc
System Configuration You should see a reply similar to the following if the connection is successful: mdsclientn: built on 2006-Jun-11 01:36 (USM_Branch_1_0) Connecting to host “localhost”, protocol “tcp”, prog 0x20000003 New client is 0x56f8f0 Connected to “localhost” Opening default session... Found 4 IP addresses 192.168.0.200 192.168.1.200 10.31.6.200 10.31.7.200 Retrieving keys Retrieved keys successfully, mdslen=140, sslen=140 sessionID = 0x7dafec9c key = 78 56 34 12 f0 de bc 9a 44 33 22 11 88 77 66 55 currentTime = Tue Jun 13 10:42:17 2006 idleTime = 300 sec *host 0 = 2@10.31.6.200/10.31.7.200 id=0x7cc464a9b842dea host 1 = 4@10.31.7.201/10.31.6.201 id=0xaae24951f45af6df Opened default session of 0x7dafec9c The connection is unsuccessful if instead you see the following reply: mdsclientn: built on 2006-Jun-11 01:36 (USM_Branch_1_0) Connecting to host “localhost”, protocol “tcp”, prog 0x20000003 Unable to reconnect to “localhost”: RPC: Remote system error - Connection refused Unable to connect to “localhost”: RPC: Remote system error - Connection refused 2. If the connection is unsuccessful, wait 15 minutes and then try connecting again. 3. Type the following command to exit the mdsclientn program: exit Verifying ContentServer Disk Space Follow these steps to verify that each ContentServer has 100% space availability. To verify space: 1. Using SystemManager, click the Servers icon on the Configuration tab to access the Servers List page. 2. Locate the Total Disk Space and Free Disk Space for each ContentServer. For ContentServer 3000 series, the total Disk Space will vary according to your RAID configuration and drive type. Refer to Supported RAID Configurations for a description of the supported 130 Installation and Configuration Guide
System Configuration configurations. The Free Disk Space should be 100%. Refer to the Omneon SystemManager User Guide for more information. Verifying NFS Share is Exported by ContentBridge To verify that each ContentBridge has exported the NFS share correctly: 1. Type the following command using the client Linux machine: showmount –e (ContentBridge IP address or host name) You should see the following output (“cb1.mediagrid.com” is an example host name): Export list for cb1.mediagrid.com: /mnt/omfs/mds/csloh/omfs/fs0 0.0.0.0/0.0.0.0 /mnt/omfs/mds/omneon/omfs/fs0 0.0.0.0/0.0.0.0 The output from the command “showmount -e cb1.mediagrid.com” lists /mnt/omfs/mds/omneon/omfs/fs0 as one of the NFS shares available from the ContentBridge. To mount the NFS share: Type the following using the Linux client machine: mount –t nfs cb1.mediagrid.com: /mnt/omfs/mds/omneon/omfs/fs0 /mnt Opening Network Ports to Enable Client Access Specific network ports must be open to enable client access to Omneon MediaGrid. This is particularly important if any security measures, including firewalls, are in place. Omneon MediaGrid clients must connect to and communicate on TCP ports 10600-10604; UDP port 111 must be open as well. Note that these ports must be open for the entire subnet in which Omneon MediaGrid is contained. Contact the customer network administrator for assistance. Managing Memory Usage by the File System Driver The amount of memory allocated to memory buffers is controllable. Each client FSD (Linux, Windows, and Macintosh) allocates memory buffers to optimize performance. This allocation of memory takes memory away from application use. In general, the memory usage of the FSDs should be minimized unless an application requires a large number of simultaneous files to be open. The following parameters are available to control memory usage by each FSD. • Filelimit (Linux FSD only). This parameter controls the maximum number of simultaneously open files the Linux FSD supports. The default value is 16. Increase this value as necessary to support an application’s requirements. Note that increasing this value increases the amount of memory used by the Linux FSD. Increasing it too much may prevent an application from running due to memory starvation. Omneon, Now Part of Harmonic 131
- Page 103 and 104: 2. Continue connecting any remainin
- Page 105 and 106: System Installation with ContentSer
- 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: To verify the service: 1. Type the
- Page 157 and 158: To configure the amount of memory u
- Page 159 and 160: System Configuration 4. Set the val
- 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
System Configuration<br />
You should see a reply similar to the following if the connection is successful:<br />
mdsclientn: built on 2006-Jun-11 01:36 (USM_Branch_1_0)<br />
Connecting to host “localhost”, protocol “tcp”, prog 0x20000003<br />
New client is 0x56f8f0<br />
Connected to “localhost”<br />
Opening default session...<br />
Found 4 IP addresses<br />
192.168.0.200<br />
192.168.1.200<br />
10.31.6.200<br />
10.31.7.200<br />
Retrieving keys<br />
Retrieved keys successfully, mdslen=140, sslen=140<br />
sessionID = 0x7dafec9c<br />
key = 78 56 34 12 f0 de bc 9a 44 33 22 11 88 77 66 55<br />
currentTime = Tue Jun 13 10:42:17 2006<br />
idleTime = 300 sec<br />
*host 0 = 2@10.31.6.200/10.31.7.200 id=0x7cc464a9b842dea<br />
host 1 = 4@10.31.7.201/10.31.6.201 id=0xaae24951f45af6df<br />
Opened default session of 0x7dafec9c<br />
The connection is unsuccessful if instead you see the following reply:<br />
mdsclientn: built on 2006-Jun-11 01:36 (USM_Branch_1_0)<br />
Connecting to host “localhost”, protocol “tcp”, prog 0x20000003<br />
Unable to reconnect to “localhost”: RPC: Remote system error - Connection refused<br />
Unable to connect to “localhost”: RPC: Remote system error - Connection refused<br />
2. If the connection is unsuccessful, wait 15 minutes and then try connecting again.<br />
3. Type the following command to exit the mdsclientn program:<br />
exit<br />
Verifying ContentServer Disk Space<br />
Follow these steps to verify that each ContentServer has 100% space availability.<br />
To verify space:<br />
1. Using SystemManager, click the Servers icon on the Configuration tab to access the Servers List<br />
page.<br />
2. Locate the Total Disk Space and Free Disk Space for each ContentServer.<br />
For ContentServer 3000 series, the total Disk Space will vary according to your RAID configuration<br />
and drive type. Refer to Supported RAID Configurations for a description of the supported<br />
130 Installation and Configuration Guide
Change language