Resiliency; Nonstop Forwarding With Stateful Switchover (Nsf/Sso) - Cisco Catalyst 6500-E Series Manual

utilization information for incoming and outgoing interfaces, CPUs, memory, and any changes to IP routes or the
Cisco Mediatrace monitoring state.
Mediatrace is enabled on each network node from which flow information is collected. The Mediatrace Initiator is
enabled on the network node that will be used to control the Mediatrace sessions or polls. The Mediatrace
Responder is enabled on each of the network nodes from which information will be collected. Figure 24 shows an
example of how Mediatrace is used to collect information about an infrastructure.
Figure 24. Using Mediatrace to Assess an Infrastructure
In this example, the Mediatrace Initiator has gathered information about specific endpoints in the unified access
campus architecture to assess their readiness for telepresence communications. High-level information for each
hop in the Mediatrace path is displayed in the middle box, while more granular information about a specific node in
the path is displayed in the right box. The box on the far left shows the type of information that this particular
profile is configured to gather. Mediatrace sessions can be run on demand, at a specific time or date, and within
the body of an EEM script.
Cisco Prime Collaboration Monitor provides GUI-based control for medianet to complement the CLI-based
statistics and control available on the individual medianet-capable nodes.

Resiliency

The introduction of more delay-sensitive and mission-critical applications into the unified access campus
architecture as a result of BYOD, video, and collaboration means that the infrastructure must achieve the highest
possible level of availability and reliability to guarantee that these applications function properly. The Cisco
Catalyst 6500-E with Supervisor Engine 2T delivers more resilient capabilities than any other backbone platform.
These capabilities include, but are not limited to, Nonstop Forwarding with Stateful Switchover (NSF/SSO); VSS
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 24 of 28