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

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 62
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 34
White Paper
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Inf ormation. Page 35 of 62
In addition to fully booting the in-chassis standby supervisor and providing fully operational uplink ports, the RPR-
Warm redundancy mode also provides synchronization of the necessary information to allow the In-chassis Standby
supervisor to reload and take over as the in-chassis active supervisor if needed. The RPR- Warm redundancy mode
synchronizes the following key variables and data structures:
Startup-config
Vlan.dat
BOOT ROMMON variable
CONFIG_FILE ROMMON variable
BOOTLDR ROMMON variable
DIAG ROMMON variable
SWITCH_NUMBER ROMMON variable
It is important to note that the RPR- Warm redundancy mode is not a stateful redundancy mode as it applies to the
local chassis. In other words if the in-chassis active supervisor does fail then the In-chassis standby supervisor will
detect the failure and reload the local chassis. Subsequently the former in-chassis standby supervisor will boot as the
in-chassis active supervisor.
During the local chassis reload the line cards will also reload. For devices connected to the Virtual Switching System
in a dual-homed manner using a multi-chassis Etherchannel connection or using Layer 3 Equal Cost Multipath links,
only the interfaces attached to the chassis performing the reload will be affected. Based on the peer devices ability to
detect the loss of link on the interfaces associated with reloading chassis, traffic will switched to the remaining active
chassis in the Virtual Switching System. Typically for Multi-chassis Etherchannel or Layer 3 Equal Cost links this is a
hardware based subsecond convergence event.
In-chassis Standby Boot Process
The boot process for the second supervisor installed in VSS chassis is different compared to the boot process for a
second supervisor in a standalone chassis. Early in the boot process the supervisor will perform a role negotiation
with the existing supervisor in the chassis. Once the supervisor determines that it will become the standby supervisor
for the chassis it will then detect if the system is configured for the VSS. If the VSS configuration is detected the
supervisor will then extract and boot a new software image dedicated to an In-chassis standby supervisor in a VSS.
The new software image will proceed to boot and reach the RPR-WARM redundancy mode.
As shown in Figure 22, the second supervisor proceeds to boot to the RPR-WARM redundancy mode by loading a
different Cisco IOS Software image. The new software image is specifically developed for a supervisor module
operating as the VSS in-chassis standby role. The new image is called the “Sup-LC” image, as in Supervisor-Line
Card. The Sup-LC image file is extracted out of the image already running on the supervisor in much the same way
as a line card extracts its image file from the Cisco IOS Software image running on the active supervisor. Therefore
there are no additional requirements to copy a separate image to the file system of the switch.
Once the supervisor successfully loads the Sup-LC image the supervisor will primarily operate as DFC-enabled line
card, In addition the supervisor will perform synchronization of key supervisor subsystems so that if needed the
supervisor may reload and assume the role of the in-chassis active supervisor.
Vista de pagina 34
1 2 ... 30 31 32 33 34 35 36 37 38 39 40 ... 61 62

Comentarios a estos manuales

Sin comentarios