Streaming Media Supplement sa2150 and sa2250

104
Chapter 10 Logging and Monitoring
On each collation client:
4. Open the logs_xml.config file in VI.
5. Locate the log object which defines the summary-mixt.log file, which looks like this:
<!-- Media-IXT summary log object -->
<LogObject>
<Format="summary-mixt"/>
<Filename="summary-mixt"/>
<Protocols="mixt"/>
</LogObject>
<!-- Media-IXT complete log object -->
6. Add a CollationHosts parameter to the summary log object, after the Protocols parameter.
In generic form, the CollationHosts parameter looks like this:
<CollationHosts="collation_host_IP:collation_PORT"/>
Make the CollationHosts parameter reflect the IP address or hostname and collation port of your collation
host, for example:
<CollationHosts="11.11.11.11:28006"/>
7. Locate the Log Object which defines the complete-mixt.log file, which looks like this:
<LogObject>
<Format="complete-mixt"/>
<Filename="complete-mixt"/>
<Protocols="mixt"/>
</LogObject>
8. Add a CollationHosts parameter to the complete log object, after the Protocols parameter.
In generic form, the CollationHosts parameter looks like this:
<CollationHosts="collation_host_IP:collation_PORT"/>
Make the CollationHosts parameter reflect the IP address or hostname and port of your collation host, for
example:
<CollationHosts="11.11.11.11:28006"/>
On the collation host and on each collation client:
9. Restart Media-IXT
RealNetworks logging
The RealProxy component of Media-IXT maintains the proxy.log logfile.
RealProxy’s proxy.log logs live and on-demand RealNetworks content, while Media-IXT only logs on-
demand RealNetworks content.
RealNetworks logging in hierarchical deployments
In hierarchical deployments, RealProxy’s proxy.log and Media-IXT’s logs handle the same connections
differently.
On-demand content
• RealProxy’s proxy.log on a child cache shows a demand cache hit; on a parent cache proxy.log
shows demand passthrough.
NOTE Do not make any changes to logs_xml.config on the collation host.