03-22-2014 02:27 PM - edited 03-01-2019 11:35 AM
I have a pair of n1010 appliances in an HA pair. The redundancy is working as expected. I have an existing virtual-service-blade configured and enabled, which is operating as expected in an HA mode. When I attempt to build a second virtual-service-blade with a unique svs domain number, HA never establishes. Both virtual-service-blades are configured in an L3 mode. Both use the same vlan for control and packet interfaces. Both virtual-service-blades have management interfaces configured in the same subnet. I am not sure why the second virtual service blade is failing to establish HA.
Note that the vsb failing to establish HA is v1ksdc04.
Relevant code from the n1010
virtual-service-blade SDC-UCS01
virtual-service-blade-type name VSM-1.2
interface control vlan 480
interface packet vlan 480
ramsize 2048
disksize 3
numcpu 1
cookie 199249335
no shutdown primary
no shutdown secondary
interface VsbEthernet1/1
interface VsbEthernet1/2
interface VsbEthernet1/3
virtual-service-blade v1ksdc04
virtual-service-blade-type name VSM-1.2
interface control vlan 480
interface packet vlan 480
ramsize 2048
disksize 3
numcpu 1
cookie 824653835
no shutdown
interface VsbEthernet2/1
interface VsbEthernet2/2
interface VsbEthernet2/3
svs-domain
domain id 2
control vlan 480
management vlan 480
svs mode L2
Relevant code from the vsb that is functioning as expected:
svs-domain
domain id 1000
control vlan 480
packet vlan 480
svs mode L3 interface mgmt0
v1ksdc01# sho redun stat
Redundancy role
---------------
administrative: secondary
operational: secondary
Redundancy mode
---------------
administrative: HA
operational: HA
This supervisor (sup-2)
-----------------------
Redundancy state: Active
Supervisor state: Active
Internal state: Active with HA standby
Other supervisor (sup-1)
------------------------
Redundancy state: Standby
Supervisor state: HA standby
Internal state: HA standby
System start time: Sat Sep 14 22:20:57 2013
System uptime: 190 days, 7 hours, 10 minutes, 19 seconds
Kernel uptime: 190 days, 6 hours, 51 minutes, 56 seconds
Active supervisor uptime: 190 days, 7 hours, 9 minutes, 35 seconds
v1ksdc01# sh mod
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V ha-standby
2 0 Virtual Supervisor Module Nexus1000V active *
3 332 Virtual Ethernet Module NA ok
4 332 Virtual Ethernet Module NA ok
5 332 Virtual Ethernet Module NA ok
6 332 Virtual Ethernet Module NA ok
7 332 Virtual Ethernet Module NA ok
8 332 Virtual Ethernet Module NA ok
Mod Sw Hw
--- ------------------ ------------------------------------------------
1 4.2(1)SV2(2.1) 0.0
2 4.2(1)SV2(2.1) 0.0
3 4.2(1)SV2(2.1) VMware ESXi 5.1.0 Releasebuild-1312873 (3.1)
4 4.2(1)SV2(2.1) VMware ESXi 5.1.0 Releasebuild-1312873 (3.1)
5 4.2(1)SV2(2.1) VMware ESXi 5.1.0 Releasebuild-1312873 (3.1)
6 4.2(1)SV2(2.1) VMware ESXi 5.1.0 Releasebuild-1312873 (3.1)
7 4.2(1)SV2(2.1) VMware ESXi 5.1.0 Releasebuild-1312873 (3.1)
8 4.2(1)SV2(2.1) VMware ESXi 5.1.0 Releasebuild-1312873 (3.1)
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
1 151.171.106.43 NA NA
2 151.171.106.43 NA NA
3 151.171.97.238 262e7161-f008-e311-0000-000000000003 shc003a.servers.chrysler.com
4 151.171.97.237 262e7161-f008-e311-0000-000000000006 shc003b.servers.chrysler.com
5 151.171.97.236 262e7161-f008-e311-0000-000000000002 shc003c.servers.chrysler.com
6 151.171.97.235 262e7161-f008-e311-0000-000000000005 shc003d.servers.chrysler.com
7 151.171.97.234 262e7161-f008-e311-0000-000000000001 shc003e.servers.chrysler.com
8 151.171.97.233 262e7161-f008-e311-0000-000000000004 shc003f.servers.chrysler.com
* this terminal session
Relevant code from the vwb that is not establishing HA:
svs-domain
domain id 1004
control vlan 480
packet vlan 480
svs mode L3 interface mgmt0
v1ksdc04# sho redun stat
Redundancy role
---------------
administrative: primary
operational: primary
Redundancy mode
---------------
administrative: HA
operational: None
This supervisor (sup-1)
-----------------------
Redundancy state: Active
Supervisor state: Active
Internal state: Active with warm standby
Other supervisor (sup-2)
------------------------
Redundancy state: Standby
Error in getting supervisor and internal state of other supervisor.
System start time: Mon Mar 24 05:03:14 2014
System uptime: 0 days, 0 hours, 32 minutes, 12 seconds
Kernel uptime: 0 days, 0 hours, 32 minutes, 47 seconds
Active supervisor uptime: 0 days, 0 hours, 31 minutes, 38 seconds
v1ksdc04# sho mod
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V active *
2 0 Virtual Supervisor Module powered-up
Mod Sw Hw
--- ------------------ ------------------------------------------------
1 4.2(1)SV2(2.1) 0.0
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
1 151.171.106.144 NA NA
* this terminal session
I am not certain why there is an error in getting the supervisor and internal state of the secondary supervisor. Any help would be greatly appreciated.
04-21-2014 10:24 AM
Hi,
'Active with warm standby' means that the VSB sees the other VSB on the management VLAN but not the control VLAN. So you would want to trace the control VLAN between these VSBs and verify that it is end to end.
HTH,
Joe
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: