Pruebas de corte de enlace VSS entre
chasis Catalyst 6500
Fecha: 27 de enero del 2017
El
sistema VSS es una característica en los chasis Catalyst 6500 que permite
agrupar dos chasis físicos en una sola entidad lógica.
Esta
opción proporciona un concepto similar al stack, pero sin las limitaciones de
distancia, por lo que tendremos un solo equipo
dividido
en dos sitios diferentes, facilitando la configuración y la administración.
La
limitación es que el enlace VSL (Virtyual Switch Link) no debería perder
conectividad entre ambos sitios.
La
pregunta es, que pasa si sucede ? aquí las pruebas, la curiosidad hace al gato.
Escenario
Ambos
chasis se encuentran conectados entre si mediante un enlase VSL (Virtyual
Switch Link) a través de dos
port
channel (Po1 y Po2), y que afectan a las interfaces Te5/4 y Te5/5 de cada
switch, cada port channes va por
recorridos
de fibra diferentes para una mejor tolerancia a fallos
Además
existen dos vínculos de detección dual-active mediante los puertos Gi2/47 y
Gi2/48, también cada uno
por
recorrido de fibras diferentes también para tolerancia a fallos.
1.- Verificación inicial:
Los
puertos, al igual que un stack, pasan a denominarse de slot/puerto a
chasis/slot/puerto, ejemplo Gi 1/1/5.
6500-SitioA#sh etherchannel
summary
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use N - not in use, no aggregation
f - failed to allocate aggregator
M - not in use, no aggregation due to
minimum links not met
m - not in use, port not aggregated due
to minimum links not met
u - unsuitable for bundling
d
- default port
w - waiting to be aggregated
Number of channel-groups in
use: 2
Number of aggregators: 2
Group Port-channel
Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(RU) - Te1/5/4(P) Te1/5/5(P) (para el chasis SitioA)
2 Po2(RU) - Te2/5/4(P) Te2/5/5(P) (para el chasis SitioB)
6500-SitioA#
6500-SitioA#sh switch
virtual role
RRP information for Instance 1
--------------------------------------------------------------------
Valid Flags
Peer Preferred Reserved
Count Peer
Peer
--------------------------------------------------------------------
TRUE V
1 1 1
Switch Switch
Status Priority Role
Local Remot
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1
UP 110(110) ACTIVE 0
0
REMOTE 2
UP 100(100) STANDBY 1374
1295
Peer 0 represents the local
switch
Flags : V - Valid
In dual-active recovery mode: No
6500-SitioA#
2.- Simuación corte de fibras que comunican los enlaces VSL y los sensores dual-active:
Las
conexiones de fibra se desconectan una a una, por lo que primero cae el enlace
VSL y luego caen los enlaces
dual-active,
por lo que se alcanza a enviar al menos un fast-hello a los 500 mSeg de la
caída del enlace VSL.
Todas
las interfaces (físicas y lógicas) del chasis activo quedan shutdown, también
se desactiva OSPF.
6500-SitioA#
*Jan 27 16:34:49.790:
%VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/5: Link down
*Jan 27 16:34:49.790:
%VSLP-SW2_STBY-3-VSLP_LMP_FAIL_REASON: Te2/5/4: Link down
*Jan 27 16:34:58.782:
%VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/4: Link down
*Jan 27 16:34:58.782:
%VSLP-SW1-2-VSL_DOWN: Last VSL
interface Te1/5/4 went down
*Jan 27 16:34:58.786:
%VSLP-SW1-2-VSL_DOWN: All VSL links went
down while switch is in ACTIVE role
*Jan 27 16:34:58.950:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 5 - Module Type LINE_CARD removed
*Jan 27 16:34:58.990:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 1 - Module Type LINE_CARD removed
*Jan 27 16:34:59.042:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 2 - Module Type LINE_CARD removed
*Jan 27 16:34:59.058:
%PFREDUN-SW1-6-ACTIVE: Standby processor removed or reloaded, changing to
Simplex mode
*Jan 27 16:34:59.170:
%DUAL_ACTIVE-SW1-1-DETECTION: Fast-hello running on Gi1/2/47 detected dual-active condition
(el chasis alcanza a detectar que ambos están en modo active)
*Jan 27 16:34:59.170:
%DUAL_ACTIVE-SW1-1-RECOVERY: Dual-active
condition detected: Starting recovery-mode, all
non-VSL and non-excluded
interfaces have been shut down (se caen todas las interfaces físicas y SVI)
*Jan 27 16:34:59.190:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 3 - Module Type LINE_CARD removed
*Jan 27 16:34:59.222:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 4 - Module Type LINE_CARD removed
*Jan 27 16:34:59.270:
%OSPF-SW1-5-SitioBJCHG: Process 1, Nbr 192.168.254.3 on Vlan10 from FULL to
DOWN,
Neighbor Down: Interface down or detached (se cae el OSPF)
*Jan 27 16:34:59.270:
%OSPF-SW1-5-SitioBJCHG: Process 1, Nbr 192.168.254.10 on Vlan10 from FULL to
DOWN,
Neighbor Down: Interface down
or detached
*Jan 27 16:34:59.270:
%OSPF-SW1-5-SitioBJCHG: Process 1, Nbr 192.168.254.11 on Vlan10 from EXSTART to
DOWN,
Neighbor Down: Interface down
or detached
*Jan 27 16:35:09.102:
%VSDA-SW1-3-LINK_DOWN: Interface Gi1/2/47
is no longer dual-active detection capable
*Jan 27 16:35:09.102:
%VSDA-SW1-3-LINK_DOWN: Interface Gi1/2/48
is no longer dual-active detection capable
6500-SitioA(recovery-mode)# (cambió el modo del switch)
Verificación:
6500-SitioA(recovery-mode)#show ip route (no hay redes conectadas, estáticas ni OSPF)
Codes: L - local, C -
connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O -
OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 -
OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF
external type 2
i - IS-IS, su - IS-IS summary, L1 -
IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate
default, U - per-user static route
o - ODR, P - periodic downloaded static
route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop
override, p - overrides from PfR
Gateway of last resort is not
set
6500-SitioA(recovery-mode)#
6500-SitioA(recovery-mode)#sh ip int brief | include Vlan (todas las interfaces en down)
Vlan1 unassigned YES NVRAM administratively down down
Vlan2 192.168.2.205 YES NVRAM
down down
Vlan10 192.168.10.3 YES manual down down
6500-SitioA(recovery-mode)#
6500-SitioA(recovery-mode)#sh switch virtual role
RRP information for Instance 1
--------------------------------------------------------------------
Valid Flags
Peer Preferred Reserved
Count Peer
Peer
--------------------------------------------------------------------
TRUE V
0 0 0
Switch Switch
Status Priority Role
Local Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1 UP 110(110) ACTIVE 0 0 (no se detecta chasis secundario)
Peer 0 represents the local
switch
Flags : V - Valid
In dual-active recovery mode:
Yes
Triggered by: Fast-hello detection
Triggered on interface: Gi1/2/47
6500-SitioA(recovery-mode)#
3.- Se reestablecen ambas fibras (enlaces VSL y dual active):
Según
el protocolo VSS, el chasis activo debe quedar en recovery-mode y el chasis
standby queda en modo activo
(roles
invertidos) por lo que se deben reestablecer los roles.
3.1.- Con cambios sin guardar:
6500-SitioA(recovery-mode)# (este es el chasis originalmente en modo ACTIVE y pasó a modo recovery, existen cambios sin guardar)
*Jan 27 16:38:41.462:
%VSLP-SW1-5-VSLP_LMP_PASS_REASON: interface Te1/5/4: Link up
*Jan 27 16:38:41.666:
%VSLP-SW1-5-RRP_MSG: Role change from Active to Standby and hence need to
reload
*Jan 27 16:38:41.666:
%VSLP-SW1-5-RRP_UNSAVED_CONFIG: Ignoring system reload since there are
unsaved configurations.
Please save the relevant
configurations
*Jan 27 16:38:41.666:
%VSLP-SW1-5-RRP_MSG: Use 'redundancy
reload shelf' to bring this switch to its preferred STANDBY role
*Jan 27 16:38:46.490:
%VSLP-SW1-5-VSLP_LMP_PASS_REASON: interface Te1/5/5: Link up
3.2.- Verificación:
6500-SitioA(recovery-mode)#sh switch virtual role
RRP information for Instance 1
--------------------------------------------------------------------
Valid Flags
Peer Preferred Reserved
Count Peer Peer
--------------------------------------------------------------------
TRUE V
1 1 1
Switch Switch
Status Priority Role Local Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1 UP 110(110) ACTIVE 0 0 (necesita reload pero hay cambios sin salvar)
REMOTE 2
UP 100(100) ACTIVE 7031 7750
Peer 0 represents the local
switch
Flags : V - Valid
In dual-active recovery mode: Yes
Triggered by: Fast-hello detection
Triggered on interface: Gi1/2/47
3.3.- Con cambios guardados:
6500-SitioA(recovery-mode)#
*Feb 6 14:02:41.767:
%VSLP-SW1-5-VSLP_LMP_PASS_REASON: interface Te1/5/4: Link up
*Feb 6 14:02:42.063:
%DUAL_ACTIVE-SW1-1-VSL_RECOVERED: VSL has recovered during dual-active
situation: Reloading switch 1
*Feb 6 14:02:42.063: %RF-SW1-5-RF_RELOAD: Shelf
reload. Reason: dual-active
*Feb 6 14:02:42.143:
%VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/4: Disabled by Admin reload
*Feb 6 14:02:42.147: %VSLP-SW1-2-VSL_DOWN: All VSL links went down while switch is in
ACTIVE role
***
*** --- SHUTDOWN NOW ---
***
*Feb 6 14:02:44.203: %SYS-SW1-5-RELOAD: Reload requested by Delayed Reload. Reload Reason: dual-active.
Resetting
....…
4.- Restablecimiento manual de la condición inicial:
Una
vez restablecido el VSL, si las configuraciones no fueron salvadas el reboot
del chasis no es automático, de todas maneras
luego
del reinicio (automático o no) hay que realizar el cambio de roles para que el
chasis SitioA quede activo y SitioB en stand-by.
4.1.- Se reinicia el chasis en modo recovery:
6500-SitioA(recovery-mode)#wri
Building configuration...
[OK]
6500-SitioA(recovery-mode)#reload
Warning: This command reloads
only this unit as dual
active is detected
Proceed with reload? [confirm]
(enter)
*Jan 27 16:42:59.542:
%SYS-SW1-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.
*Jan 27 16:42:59.630:
%VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/4: Disabled by Admin reload
*Jan 27 16:42:59.630:
%VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/5: Disabled by Admin reload
*Jan 27 16:42:59.634:
%VSLP-SW1-2-VSL_DOWN: All VSL links
went down while switch is in ACTIVE role
Resetting
.......
---resumido---
6500-SitioA-sdby> (el chasis sale de recovery-mode y queda en standby)
Standby console disabled
6500-SitioA-sdby>
4.2.- Cambio de rol en el SW sitio B:
6500-SitioA#sh switch
virtual role
RRP information for Instance 2
--------------------------------------------------------------------
Valid Flags
Peer Preferred Reserved
Count Peer
Peer
--------------------------------------------------------------------
TRUE V
1 1 1
Switch Switch
Status Priority Role Local Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 2 UP 100(100) ACTIVE 0
0
REMOTE 1
UP 110(110)
STANDBY 4564 9804
Peer 0 represents the local
switch
Flags : V - Valid
In dual-active recovery mode:
No
6500-SitioA#
6500-SitioA#redundancy
force-switchover
System configuration has been
modified. Save ? [yes/no]: y
This will reload the active
unit and force switchover to standby[confirm] (enter)
Preparing for switchover..
*Jan 27 16:49:43.174:
%RF-SW2-5-RF_RELOAD: Self reload. Reason: Admin CLI
*Jan 27 16:49:43.250: %VSLP-SW2-3-VSLP_LMP_FAIL_REASON:
Te2/5/4: Disabled by Admin reload
Resetting
.......
---resumido---
6500-SitioA-sdby> (al intentar ingresar por consola)
Standby console disabled
6500-SitioA-sdby>
4.3.- Verificación en SW SitioA (originalmente activo):
6500-SitioA#sh switch
virtual role
RRP information for Instance 1
--------------------------------------------------------------------
Valid Flags
Peer Preferred Reserved
Count Peer
Peer
--------------------------------------------------------------------
TRUE V
1 1 1
Switch Switch
Status Priority Role Local
Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1
UP 110(110) ACTIVE
0 0
REMOTE 2
UP 100(100) STANDBY
1374 1295
Peer 0 represents the local
switch
Flags : V - Valid
In dual-active recovery mode: No
6500-SitioA#
5.- Simulación del corte de luz en el sitio B:
5.1.- Verificación inicial:
6500-SitioA#sh switch
virtual role
RRP information for Instance 1
--------------------------------------------------------------------
Valid Flags
Peer Preferred
Reserved
Count Peer
Peer
--------------------------------------------------------------------
TRUE V
1 1 1
Switch Switch
Status Priority Role Local Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1
UP 110(110) ACTIVE 0 0
REMOTE 2
UP 100(100) STANDBY 1374
1295
Peer 0 represents the local
switch
Flags : V - Valid
In dual-active recovery mode:
No
5.2.- Se desenergiza el chasis del sitio B:
6500-SitioA#
*Jan 31 14:53:09.694:
%VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/5: Link down
*Jan 31 14:53:09.702:
%VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/4: Link down
*Jan 31 14:53:09.702:
%VSLP-SW1-2-VSL_DOWN: Last VSL
interface Te1/5/4 went down
*Jan 31 14:53:09.734:
%VSLP-SW1-2-VSL_DOWN: All VSL links
went down while switch is in ACTIVE role
*Jan 31 14:53:10.078:
%PFREDUN-SW1-6-ACTIVE: Standby processor removed or reloaded, changing to
Simplex mode
*Jan 31 14:53:10.202:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 5 - Module Type LINE_CARD removed
*Jan 31 14:53:10.242:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 1 - Module Type LINE_CARD removed
*Jan 31 14:53:10.294:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 2 - Module Type LINE_CARD removed
*Jan 31 14:53:10.342:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 3 - Module Type LINE_CARD removed
*Jan 31 14:53:10.374:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 4 - Module Type LINE_CARD removed
*Jan 31 14:53:17.270:
%VSDA-SW1-3-LINK_DOWN: Interface Gi1/2/47 is no longer dual-active detection
capable
*Jan 31 14:53:17.270:
%VSDA-SW1-3-LINK_DOWN: Interface Gi1/2/48 is no longer dual-active detection
capable
6500-SitioA#
5.3.- Verificación del funcionamiento de OSPF en SitioA luego del
apagado:
6500-SitioA#sh ip ospf nei (OK)
Neighbor ID Pri
State Dead
Time Address Interface
192.168.254.3 1
FULL/BDR
00:00:36 192.168.10.2 Vlan10
192.168.254.10 254
FULL/DR
00:00:37 192.168.10.1 Vlan10
192.168.254.11 253
2WAY/DROTHER 00:00:36 192.168.10.254 Vlan10
6500-SitioA#
6500-SitioA#sh switch
virtual role
RRP information for Instance 1
--------------------------------------------------------------------
Valid Flags
Peer Preferred Reserved
Count Peer
Peer
--------------------------------------------------------------------
TRUE V
0 0 0
Switch Switch
Status Priority Role Local
Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1
UP 110(110) ACTIVE
0 0 (no existe el
switch 2)
Peer 0 represents the local
switch
Flags : V - Valid
In dual-active recovery mode:
No
6500-SitioA#
Detalle: No se perdieron pings entre un host conectado a la VLAN 2 (192.168.2.188) y el gateway de la VLAN ( chasis 6500 192.168.2.1).
5.4.- Se energiza el chasis de sitio B:
6500-SitioA#
*Jan 31 14:56:51.582: %VSLP-SW1-5-VSLP_LMP_PASS_REASON:
interface Te1/5/4: Link up
*Jan 31 14:56:51.882:
%VSLP-SW1-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE by VSLP
*Jan 31 14:56:51.882:
%VSL-SW1-5-VSL_CNTRL_LINK: New VSL
Control Link 1/5/4
Initializing as Virtual Switch
ACTIVE processor
*Jan 31 14:56:51.882:
%VSLP-SW1-5-VSL_UP: Ready for control
traffic
*Jan 31 14:56:51.894:
%VSLP-SW1-5-VSLP_LMP_PASS_REASON: interface Te1/5/5: Link up
*Jan 31 14:57:03.258:
%PFREDUN-SW1-6-ACTIVE: Standby initializing for SSO mode
*Jan 31 14:57:46.802:
%OIR-SW1-6-INSREM: Switch 2 Physical Slot 5 - Module Type LINE_CARD inserted
*Jan 31 14:57:57.814:
%DIAG-SW1-6-RUN_MINIMUM: Switch 2 Module 5: Running Minimal Diagnostics...
*Jan 31 14:58:16.286:
%DIAG-SW1-6-DIAG_OK: Switch 2 Module 5: Passed Online Diagnostics
*Jan 31 14:58:16.918:
%OIR-SW1-6-SP_INSCARD: Card inserted in Switch_number = 2, physical slot 5,
interfaces are now online
*Jan 31 14:58:16.942:
%VSLP-SW1-5-VSL_UP: Ready for data
traffic
–-resumido---
*Jan 31 15:01:07.942: %OIR-SW1-6-SP_INSCARD:
Card inserted in Switch_number = 2, physical slot 2, interfaces are now online
*Jan 31 15:01:15.622:
%DIAG-SW1-6-RUN_MINIMUM: Switch 2 Module 4: Running Minimal Diagnostics...
*Jan 31 15:01:15.626:
%DIAG-SW2_STBY-6-RUN_MINIMUM: Switch 2 Module 4: Running Minimal Diagnostics...
*Jan 31 15:01:21.646:
%VSDA-SW1-5-LINK_UP: Interface Gi1/2/47 is now dual-active detection
capable
*Jan 31 15:01:21.646:
%VSDA-SW1-5-LINK_UP: Interface Gi1/2/48 is now dual-active detection
capable
*Jan 31 15:01:21.734:
%VSDA-SW2_STBY-5-LINK_UP: Interface Gi2/2/47 is now dual-active
detection capable
*Jan 31 15:01:21.734:
%VSDA-SW2_STBY-5-LINK_UP: Interface Gi2/2/48 is now dual-active
detection capable
*Jan 31 15:01:27.874:
%DIAG-SW1-6-DIAG_OK: Switch 2 Module 4: Passed Online Diagnostics
*Jan 31 15:01:27.858:
%DIAG-SW2_STBY-6-DIAG_OK: Switch 2 Module 4: Passed Online Diagnostics
*Jan 31 15:01:29.278:
%OIR-SW1-6-SP_INSCARD: Card inserted in Switch_number = 2, physical slot 4,
interfaces are now online
6500-SitioA#
5.5.- Verificación:
6500-SitioA#sh switch
virtual role
RRP information for Instance 1
--------------------------------------------------------------------
Valid Flags
Peer Preferred Reserved
Count Peer
Peer
--------------------------------------------------------------------
TRUE V
1 1 1
Switch Switch
Status Priority Role Local Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1
UP 110(110) ACTIVE 0
0
REMOTE 2
UP 100(100) STANDBY 1471
1789
Peer 0 represents the local
switch
Flags : V - Valid
In dual-active recovery mode:
No
6500-SitioA#
5.6.- Verificación de los tiempos de uptime en chasis de sitio B luego
de un corte de energía:
6500-SitioA#sh clock
*12:05:06.574 ARG Tue
Jan 31 2017 (se energiza el chasis)
6500-SitioA#
6500-SitioA#sh clock
*12:12:37.122 ARG Tue
Jan 31 2017 (chasis B on line)
6500-SitioA#
6.- Configuración afectada:
!
switch virtual domain 1
switch mode virtual
switch 1 priority 110
!
!
interface Port-channel1 (para puertos chasis
SitioA)
description VSS entre chasis
no switchport
no ip address
no platform qos channel-consistency
switch virtual link 1
!
interface Port-channel2 (para puertos chasis
SitioB)
no switchport
no ip address
no platform qos channel-consistency
switch virtual link 2
!
!
interface TenGigabitEthernet1/5/4 (puertos
chasis SitioA)
description VSS entre chasis
no switchport
no ip address
no cdp enable
channel-group 1 mode on
!
interface TenGigabitEthernet1/5/5 (puertos
chasis SitioA)
description VSS entre chasis
no switchport
no ip address
no cdp enable
channel-group 1 mode on
!
!
interface TenGigabitEthernet2/5/4 (puertos
chasis SitioB)
description VSS entre chasis
no switchport
no ip address
no cdp enable
channel-group 2 mode on
!
interface TenGigabitEthernet2/5/5 (puertos
chasis SitioB)
description VSS entre chasis
no switchport
no ip address
no cdp enable
channel-group 2 mode on
!
!
interface GigabitEthernet1/2/47 (puertos de detección dual-active chasis SitioA
no switchport
no ip address
no cdp enable
dual-active fast-hello
!
interface
GigabitEthernet1/2/48 (puertos de detección
dual-active chasis SitioA)
no switchport
no ip address
no cdp enable
dual-active fast-hello
!
!
interface
GigabitEthernet2/2/47 (puertos de detección
dual-active chasis SitioB)
no switchport
no ip address
no cdp enable
dual-active fast-hello
!
interface
GigabitEthernet2/2/47 (puertos de detección
dual-active chasis SitioB)
no switchport
no ip address
no cdp enable
dual-active fast-hello
!
7.- Resúmen:
-
Si se cortan ambas fibras entre SitioA y SitioB ambos chasis quedan en ACTIVE y
reenviando paquetes, pueden generarse
problemas
de IP duplicadas e inconsistencias de OSPF.
-
Cuando se reestablece una o ambas fibras, el chasis SitioA queda en modo
recovery con todos los puertos, interfaces VLAN y el
OSPF
en shutdown, si el running-config coincide con el startup-config (punto 3.3),
el chasis SitioA reinicia automáticamente y queda
en modo STAND-BY con todos los puertos en forwarding, hay que realizar el cambio de roles desde el chasis SitioB (punto 4.2).
-
Cuando se reestablece una o ambas fibras, el chasis SitioA queda en modo
recovery con todos los puertos, interfaces VLAN y el
OSPF
en shutdown, si el running-config no coincide con el startup-config (punto 3.1),
en el chasis SitioA debe guardarse la config
y
reiniciarse manualmente vía consola (punto 4.1), luego queda en modo
STAND-BY, hay que realizar el cambio de roles desde el
chasis SitioB (punto 4.2).
-
Cuando se realiza el cambio de roles, el chasis SitioB se reinicia y luego
queda en STAND-BY.
-
Cuando se realiza el cambio de roles, en el chasis SitioA se genera un
microcorte por la conmutación.
-
Si el chasis SitioB se apaga por corte de luz, no hay impacto en chasis SitioA.
-
El tiempo de startup de los chasis es de aproximadamente 7 minutos.
-
El tiempo de reload por cambio de estado es de aproximadamente 8 minutos.
(2017) Networking for lonely people
Rosario, Argentina