03.02.2014 Views

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Cisco</strong> Network Analysis Module<br />

Chapter 6<br />

<strong>Medianet</strong> Management and Visibility Design Considerations<br />

Finally, when multiple redundant equal-cost paths exist within the medianet infrastructure, <strong>Cisco</strong><br />

Express Forwarding (formerly known as CEF) load balances the traffic across the equal-cost paths using<br />

a hash of the source and destination IP addresses for each session. Each router and switch along the path<br />

independently creates its <strong>Cisco</strong> Express Forwarding table based on IP routing protocols, and load<br />

balances sessions across its interfaces that represent equal-cost paths to the next hop along the path to<br />

the destination. An IPSLA probe generated by a switch or router has a different IP source address than<br />

the actual video device that is being pre-assessed. Therefore, the path taken by the IPSLA probes within<br />

a highly redundant network infrastructure may not be exactly the path taken by the actual video traffic<br />

from the device. The use of dedicated routers to perform an IPSLA network assessment eases this issue<br />

slightly, because the routers can be configured to use the actual IP addresses that the video endpoints<br />

will ultimately use. However, any changes to the <strong>Cisco</strong> Express Forwarding tables, brought about<br />

through routing changes or reloading of the switches/routers along the path, may result in a slightly<br />

different path established for the traffic when the actual video devices are installed. You should be aware<br />

of these limitations of IPSLA within a highly redundant medianet infrastructure.<br />

IPSLA as an Ongoing Performance Monitoring Tool<br />

If configured with careful consideration, IPSLAs can also be used as an ongoing performance<br />

monitoring tool. Rather than simulating an actual medianet video flow, IPSLA operations can be used to<br />

periodically send small amounts of traffic between two points within the network, per service class, to<br />

assess parameters such as packet loss, one-way latency, and jitter. Figure 6-20 shows an example of such<br />

a deployment between two branches.<br />

Figure 6-20<br />

Example of IPSLA Used for Ongoing Performance Monitoring<br />

Campus #1<br />

Campus #2<br />

SNMP<br />

Threshold<br />

Traps<br />

QFP<br />

Metro-Ethernet<br />

or<br />

MPLS Service<br />

IPSLA Operation<br />

QFP<br />

Branch #1 Branch #2<br />

228432<br />

6-32<br />

<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />

OL-22201-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!