Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 282 / 400

Media Flow Controller Troubleshooting Media Flow Controller Administrator’s Guide
282 Common Media Flow Controller Configuration Errors Copyright © 2010, Juniper Networks, Inc.
4. Email a generated debug-dump file to the list of recipients configured to receive info event
notices (see
“Configuring Media Flow Controller Fault Notifications (CLI)” on page 240 for
task details).
file debug-dump email <filename_of_debug_dump>
5. Upload a specific debug-dump file. The uploaded file is a gnu-zipped .tar file (.tgz) and can
be unzipped with this command on Linux: gunzip -c <filename>.tgz | tar tf -
or with WinZip on a Windows system.
file debug-dump upload <filename_of_debug_dump> <URL>
Note! Only FTP and TFTP URLs, as well as SCP pseudo-URLs are supported for the
destination. See “Terminology” on page 30 for the scp format.
Common Media Flow Controller Configuration Errors
This section offers some common configuration errors and suggested fixes.
•
“Media Flow Controller Licenses Invalid” on page 282
•
“Namespace Match Uri Configuration” on page 283
•
“Namespace Domain Configuration” on page 283
•
“File Not Getting Cached” on page 283
•
“Cache Promotion Not Happening” on page 283
•
“Incoming Requests’ URL Length” on page 283
Media Flow Controller Licenses Invalid
Release 2.0 and earlier Media Flow Controller licenses are tied to the MAC address of eth0.
Typically you must manually set the eth0 interface at installation with one of the Ethernet
naming options during installation. If not specified, the default assignation of ports is the order
in which the drivers are loaded and if eth0 is not assigned the MAC address associated with
your licenses at that time, your licenses will be invalid. If that happens, you should re-install
Media Flow Controller and use the Ethernet naming options to name the correct interface
eth0. However, if re-installation is not an option, you can use the management interface
command to name the correct interface as eth0.
Important! While this command does name the specified interface eth0, it also renames all
other interfaces, which can cause other problems if other interfaces are configured for specific
reasons.
To use the management interface command to name eth0:
1. Determine what MAC address your licenses are tied to:
show license
2. Determine which interface has the MAC address to which your licenses are tied (the last
two octets of the HWaddr are what you need):
show interface
3. Type the following command to name that interface as the eth0 management interface:
management interface <MAC_address>