
Chapter 9 Troubleshooting
© 2017 Harmonic Inc. All rights reserved.
286
Harmonic MediaGrid Release 4.1
Troubleshooting on the ContentBridge
/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
Harmonic MediaGrid. Depending on the gateway configuration file, there may be multiple mount
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
Harmonic MediaGrid. This file is located in the /tftpboot/config directory on the first two
ContentDirectors in the Harmonic 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
Harmonic
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 Harmonic 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
The next output sample is of the file contents being displayed using the “cat” command. These
contents can be compared to the gateway file on the ContentBridge to indicate if the gateway file
has been downloaded or that the latest changes should be downloaded by rebooting the
ContentBridge.
[root@CDL1 gateway]# cat CLB01649
CB 10.35.134.200 mg0 omneon usm
MEDIA_API=YES