About Omneon MediaGrid - Harmonic Inc
About Omneon MediaGrid - Harmonic Inc About Omneon MediaGrid - Harmonic Inc
Troubleshooting If all other services are running, then the likely cause is that time is not synchronized on ContentDirectors. Resolution: ntpdate -u ntpdate should be initiated on any ContentDirectors that are running first so that the time source is known. “ntpdate -u” can then be initiated on ContentDirectors that are receiving the above error message. Troubleshooting on the ContentBridge The ContentBridge provides access to the Omneon MediaGrid for clients not running the FSD or clients that need to access the Omneon MediaGrid via FTP or AFP. ContentBridge Mounts to the Omneon MediaGrid The primary problem experienced with the ContentBridge occurs when the Omneon MediaGrid file system has not been mounted. To determine that the file system has been mounted, use one or both of the following commands. Mount command on the ContentBridge [root@CLB01649 ~]# mount /dev/ram0 on / type ext2 (rw) /dev/proc on /proc type proc (rw) /dev/sys on /sys type sysfs (rw) /dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/shm on /dev/shm type tmpfs (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) //10.35.99.180/SBOD on /mnt/10.35.99.180/SBOD type cifs (rw,mand) /10.35.134.200/mg0 on /mnt/omfs/10.35.134.200/omneon/omfs/mg0 type omfs (rw,username=omneon,password=xxx) df command on the ContentBridge [root@CLB01649 ~]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/ram0 249551 124082 125469 50% / /dev/shm 1037296 0 1037296 10% /dev/shm //10.35.99.180/SBOD 5161484288 2706030592 2455453696 53% /mnt/10.35.99.180/SBOD /10.35.134.200/mg0 12975695328 2651456296 10324239032 21% /mnt/omfs/10.35.134.200/omneon/omfs/mg0 Note the line starting with /10.35.134.200/… This is the mount for the ContentBridge to the Omneon MediaGrid. Depending on the gateway configuration file, there may be multiple mount 260 Installation and Configuration Guide
Troubleshooting points. The number of mount points will vary depending on the number of mount points defined in the gateway file for different users. ContentBridge Configuration Files The second most common problem on the ContentBridge is that the config file or the gateway file has not been configured correctly. These are the two configuration files that the ContentBridge uses. The first configuration file, the “config” file, is the same for all ContentBridges in the Omneon MediaGrid. This file is located in the /tftpboot/config directory on the first two ContentDirectors in the Omneon MediaGrid. To edit this file, use the SystemManager, which pushes the configuration file to all ConentDirectors ensuring that when the ContentBridge downloads this file from the ContentDirector, the configuration information is the same across ContentDirectors. Refer to “Editing the ContentBridge Configuration File” in the Omneon SystemManager User Guide for instructions. The following is an example of this file. ContentServer and ContentBridge config file: [root@CLB01649 tmp]# cat config LOGHOST=10.35.134.200 REBOOT_ON_PANIC=YES SLICE_TIMEZONE=Etc/GMT+8 ENABLE_JUMBO_SERVER=NO ENABLE_JUMBO_BRIDGE=NO In addition to the config file on the first two ContentDirectors, there is a gateway file for each ContentBridge in the Omneon MediaGrid. The file name for the gateway file is CLBnnnnn and is case sensitive. The five n’s reflect the last five digits of the serial number of the ContentBridge. Again, any changes to this gateway file must be done on both ContentDirectors in the /tftpboot/config/gateway directory. When the CLBnnnnn file is downloaded to the gateway, it is stored in the /tmp directory with the file name gateway. This file can be examined using the “less,” “cat,” or “more” commands, or your preferred editor to ensure that the parameters in the file on the ContentBridge match the parameters on the ContentDirectors. The most common problem is that the changes to the gateway file are made on one ContentDirector but are never made on the file on the second ContentDirector. The output below is a listing of the files on one of the ContentDirectors and shows the CLBnnnnn notation of the file name. [root@CDL1 gateway]# ll total 8 -rwxr-xr-x 1 root root 58 Jan 29 18:33 CLB01634 -rwxr-xr-x 1 root root 81 Jan 30 16:14 CLB01649 Omneon, Now Part of Harmonic 261
- Page 233 and 234: Off White Blue Red Ethernet Port 0
- Page 235 and 236: Link indicator Port 0 Port 1 Figure
- Page 237 and 238: Yellow Power on White Red Ethernet
- Page 239 and 240: Table 21. Drive-status Indicator Pa
- Page 241 and 242: Power Supply LEDs Figure 93 and Tab
- Page 243 and 244: Table 26. ContentServer 1042 Ethern
- Page 245 and 246: Table 29. ContentServer 1042B Rear
- Page 247 and 248: Figure 99. Rear View of ContentServ
- Page 249 and 250: 1 PWR RST MediaGrid Figure 101. Con
- Page 251 and 252: Table 34. ContentServer 2122 Front
- Page 253 and 254: 2 1 2 1 3 ID Figure 104. ContentSer
- Page 255 and 256: Front Panel Components Front Bezel
- Page 257 and 258: Table 39. ContentServer 2124 Front
- Page 259 and 260: 2 1 2 1 3 ID Figure 109. ContentSer
- Page 261 and 262: ContentServer 3000 Hardware Referen
- Page 263 and 264: Left Control Panel Figure 113. Cont
- Page 265 and 266: Table 46. Disk Drive Status LEDs LE
- Page 267 and 268: Table 47. ContentServer 3000 Rear P
- Page 269 and 270: Figure 117. NVRAM Card LEDs 2 1 3 T
- Page 271 and 272: Figure 119. 10 Gigabit Ethernet Add
- Page 273 and 274: 1 Drive 15 15 OPEN 14 Figure 121. C
- Page 275 and 276: Table 55. ContentStore 3160 Front B
- Page 277 and 278: Table 57. ContentStore 3160 Rear Pa
- Page 279 and 280: CHAPTER 8 Troubleshooting This sect
- Page 281 and 282: Troubleshooting The dhcp-leases fil
- Page 283: Troubleshooting The two most import
- Page 287 and 288: Security with Microsoft Domain Cont
- Page 289 and 290: mdsclientn dialog output: Troublesh
- Page 291 and 292: sessions output: *** 1/64 RPC sessi
- Page 293 and 294: APPENDIX A Legacy Hardware Platform
- Page 295 and 296: Figure 127. ContentDirector Hard Dr
- Page 297 and 298: . Figure 129. ContentDirector Power
- Page 299 and 300: Table 65. ContentDirector Indicator
- Page 301 and 302: Drive-status Indicator Pattern Cond
- Page 303 and 304: 1. Link indicator 2. Activity indic
- Page 305 and 306: Figure 139 and Table 72 describe th
- Page 307 and 308: Figure 141. ContentBridge Front Pan
- Page 309 and 310: Table 77. ContentBridge 2010A Ether
- Page 311 and 312: Figure 145. ContentServer 1242 with
- Page 313 and 314: Table 81. ContentServer 1242 Ethern
Troubleshooting<br />
points. The number of mount points will vary depending on the number of mount points defined in<br />
the gateway file for different users.<br />
ContentBridge Configuration Files<br />
The second most common problem on the ContentBridge is that the config file or the gateway file has<br />
not been configured correctly. These are the two configuration files that the ContentBridge uses. The<br />
first configuration file, the “config” file, is the same for all ContentBridges in the <strong>Omneon</strong> <strong>MediaGrid</strong>.<br />
This file is located in the /tftpboot/config directory on the first two ContentDirectors in the <strong>Omneon</strong><br />
<strong>MediaGrid</strong>. To edit this file, use the SystemManager, which pushes the configuration file to all<br />
ConentDirectors ensuring that when the ContentBridge downloads this file from the<br />
ContentDirector, the configuration information is the same across ContentDirectors. Refer to<br />
“Editing the ContentBridge Configuration File” in the <strong>Omneon</strong> SystemManager User Guide for<br />
instructions. The following is an example of this file.<br />
ContentServer and ContentBridge config file:<br />
[root@CLB01649 tmp]# cat config<br />
LOGHOST=10.35.134.200<br />
REBOOT_ON_PANIC=YES<br />
SLICE_TIMEZONE=Etc/GMT+8<br />
ENABLE_JUMBO_SERVER=NO<br />
ENABLE_JUMBO_BRIDGE=NO<br />
In addition to the config file on the first two ContentDirectors, there is a gateway file for each<br />
ContentBridge in the <strong>Omneon</strong> <strong>MediaGrid</strong>. The file name for the gateway file is CLBnnnnn and is case<br />
sensitive. The five n’s reflect the last five digits of the serial number of the ContentBridge. Again, any<br />
changes to this gateway file must be done on both ContentDirectors in the /tftpboot/config/gateway<br />
directory.<br />
When the CLBnnnnn file is downloaded to the gateway, it is stored in the /tmp directory with the file<br />
name gateway. This file can be examined using the “less,” “cat,” or “more” commands, or your<br />
preferred editor to ensure that the parameters in the file on the ContentBridge match the parameters<br />
on the ContentDirectors. The most common problem is that the changes to the gateway file are made<br />
on one ContentDirector but are never made on the file on the second ContentDirector.<br />
The output below is a listing of the files on one of the ContentDirectors and shows the CLBnnnnn<br />
notation of the file name.<br />
[root@CDL1 gateway]# ll<br />
total 8<br />
-rwxr-xr-x 1 root root 58 Jan 29 18:33 CLB01634<br />
-rwxr-xr-x 1 root root 81 Jan 30 16:14 CLB01649<br />
<strong>Omneon</strong>, Now Part of <strong>Harmonic</strong> 261
Change language