Cisco WS-X6708-10G-3CXL= - 10 Gigabit Ethernet Module Manual de usuario Pagina 32

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 62
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 31
White Paper
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Inf ormation. Page 32 of 62
Figure 19. CiscoView w ith Active and Standby Sw itch Views
High Availability
Central to the high-availability model of a Cisco Virtual Switching System are the concepts of NSF/SSO and RPR.
The intricacies of these protocols are beyond the scope of this paper; you can find more information on these
protocols in the Cisco Catalyst 6500 documentation materials as well as in the following white paper:
Nonstop Forwarding and Stateful Switchover on the Cisco Catalyst 6500
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_white_paper0900aecd801c5cd7.html
The high-availability model of the system changes when you integrate two chassis together into a single network
entity. In order to take advantage of the existing innovations in NSF/SSO technologies, Cisco Virtual Switching
System has implemented a high-availability model that uses this redundancy framework for an inter-chassis
environment (Figure 20).
Figure 20. Interchassis NSF/SSO in a Cisco Virtual Sw itching System Environment
In an SSO system, “high availability-aware” protocols and features may synchronize events and state information
from the active supervisor engine to the hot-standby supervisor engine. From a redundancy framework viewpoint, the
active supervisor engine acts as a server, whereas the standby supervisor engine acts as the client. Information that
is “high availability-aware” will be statefully synchronized between these entities such that in the event of a failover,
the standby supervisor engine does not need to re-learn this information, resulting in a minimal amount of outage
time.
As Figure 19 shows, the supervisor engine in the active virtual switch (switch 1 in the figure) assumes the role as the
active supervisor engine, whereas the supervisor engine in the standby virtual switch (switch 2) assumes the role as
the hot-standby supervisor engine. You can verify this situation with the following command:
VSS#sh switch virtual redundancy
My Switch Id = 1
Peer Switch Id = 2
Vista de pagina 31
1 2 ... 27 28 29 30 31 32 33 34 35 36 37 ... 61 62

Comentarios a estos manuales

Sin comentarios