cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3278
Views
15
Helpful
2
Replies

HX managment subnet

Networker_eg
Level 1
Level 1

If I have 2 HX-Clusters sharing the same FI and uplink switches

 

Is it okey to share :

 

HX-mgmt vlan

HX-storage vlan

HX-replication vlan

 

between the 2 clusters or it is recommended to use different sub nets for each cluster 

 

My concern is HX management interface uses the MC address 224.0.0.18 to advertise so if the 2 clusters use the same subnet the SCVM of both clusters will join ,

1 Accepted Solution

Accepted Solutions

Clifford Aldan
Cisco Employee
Cisco Employee

It is ok to have both clusters using the same subnets
When each HX storage cluster is created, the storage controllers are assigned to a storage domain unique to each cluster

Thus, storage controllers from different storage domains will not join a cluster it's not assigned to

Keep the VLAN names different, but the VLAN ID can be the same

For example, a two 3-node cluster would look like this:
=====
HX-1 VLANs
=====
-----
VLAN NAME: hx-1-mgmt
VLAN ID: 10
Subnet: 172.16.10.0/24
-----
- hx-1-esxi-1: 172.16.10.101
- hx-1-esxi-2: 172.16.10.102
- hx-1-esxi-3: 172.16.10.103
- hx-1-scvm-1: 172.16.10.111
- hx-1-scvm-2: 172.16.10.112
- hx-1-scvm-3: 172.16.10.113
- hx-1-scvm-mgmt-ip: 172.16.10.120

-----
VLAN NAME: hx-1-storage-data
VLAN ID: 20
Subnet: 172.16.20.0/24
-----
- hx-1-esxi-1: 172.16.20.101
- hx-1-esxi-2: 172.16.20.102
- hx-1-esxi-3: 172.16.20.103
- hx-1-scvm-1: 172.16.20.111
- hx-1-scvm-2: 172.16.20.112
- hx-1-scvm-3: 172.16.20.113
- hx-1-scvm-data-mgmt-ip: 172.16.20.120

-----
VLAN NAME: hx-1-vmotion
VLAND ID: 30
Subnet: 172.16.30.0/24
-----
- hx-1-esxi-1: 172.16.30.101
- hx-1-esxi-2: 172.16.30.102
- hx-1-esxi-3: 172.16.30.103

-----
VLAN NAME: hx-1-vm-network
VLAN ID: 40
Subnet: 172.16.40.0/24
-----

=====
HX-2 VLANs
=====
-----
VLAN NAME: hx-2-mgmt
VLAN ID: 10
Subnet: 172.16.10.0/24
-----
- hx-2-esxi-1: 172.16.10.201
- hx-2-esxi-2: 172.16.10.202
- hx-2-esxi-3: 172.16.10.203
- hx-2-scvm-1: 172.16.10.211
- hx-2-scvm-2: 172.16.10.212
- hx-2-scvm-3: 172.16.10.213
- hx-2-scvm-mgmt-ip: 172.16.10.220

-----
VLAN NAME: hx-2-storage-data
VLAN ID: 20
Subnet: 172.16.20.0/24
-----
- hx-2-esxi-1: 172.16.20.201
- hx-2-esxi-2: 172.16.20.202
- hx-2-esxi-3: 172.16.20.203
- hx-2-scvm-1: 172.16.20.211
- hx-2-scvm-2: 172.16.20.212
- hx-2-scvm-3: 172.16.20.213
- hx-2-scvm-data-mgmt-ip: 172.16.20.220

-----
VLAN NAME: hx-2-vmotion
VLAND ID: 30
Subnet: 172.16.30.0/24
-----
- hx-2-esxi-1: 172.16.30.201
- hx-2-esxi-2: 172.16.30.202
- hx-2-esxi-3: 172.16.30.203

-----
VLAN NAME: hx-2-vm-network
VLAN ID: 40
Subnet: 172.16.40.0/24
-----

View solution in original post

2 Replies 2

Clifford Aldan
Cisco Employee
Cisco Employee

It is ok to have both clusters using the same subnets
When each HX storage cluster is created, the storage controllers are assigned to a storage domain unique to each cluster

Thus, storage controllers from different storage domains will not join a cluster it's not assigned to

Keep the VLAN names different, but the VLAN ID can be the same

For example, a two 3-node cluster would look like this:
=====
HX-1 VLANs
=====
-----
VLAN NAME: hx-1-mgmt
VLAN ID: 10
Subnet: 172.16.10.0/24
-----
- hx-1-esxi-1: 172.16.10.101
- hx-1-esxi-2: 172.16.10.102
- hx-1-esxi-3: 172.16.10.103
- hx-1-scvm-1: 172.16.10.111
- hx-1-scvm-2: 172.16.10.112
- hx-1-scvm-3: 172.16.10.113
- hx-1-scvm-mgmt-ip: 172.16.10.120

-----
VLAN NAME: hx-1-storage-data
VLAN ID: 20
Subnet: 172.16.20.0/24
-----
- hx-1-esxi-1: 172.16.20.101
- hx-1-esxi-2: 172.16.20.102
- hx-1-esxi-3: 172.16.20.103
- hx-1-scvm-1: 172.16.20.111
- hx-1-scvm-2: 172.16.20.112
- hx-1-scvm-3: 172.16.20.113
- hx-1-scvm-data-mgmt-ip: 172.16.20.120

-----
VLAN NAME: hx-1-vmotion
VLAND ID: 30
Subnet: 172.16.30.0/24
-----
- hx-1-esxi-1: 172.16.30.101
- hx-1-esxi-2: 172.16.30.102
- hx-1-esxi-3: 172.16.30.103

-----
VLAN NAME: hx-1-vm-network
VLAN ID: 40
Subnet: 172.16.40.0/24
-----

=====
HX-2 VLANs
=====
-----
VLAN NAME: hx-2-mgmt
VLAN ID: 10
Subnet: 172.16.10.0/24
-----
- hx-2-esxi-1: 172.16.10.201
- hx-2-esxi-2: 172.16.10.202
- hx-2-esxi-3: 172.16.10.203
- hx-2-scvm-1: 172.16.10.211
- hx-2-scvm-2: 172.16.10.212
- hx-2-scvm-3: 172.16.10.213
- hx-2-scvm-mgmt-ip: 172.16.10.220

-----
VLAN NAME: hx-2-storage-data
VLAN ID: 20
Subnet: 172.16.20.0/24
-----
- hx-2-esxi-1: 172.16.20.201
- hx-2-esxi-2: 172.16.20.202
- hx-2-esxi-3: 172.16.20.203
- hx-2-scvm-1: 172.16.20.211
- hx-2-scvm-2: 172.16.20.212
- hx-2-scvm-3: 172.16.20.213
- hx-2-scvm-data-mgmt-ip: 172.16.20.220

-----
VLAN NAME: hx-2-vmotion
VLAND ID: 30
Subnet: 172.16.30.0/24
-----
- hx-2-esxi-1: 172.16.30.201
- hx-2-esxi-2: 172.16.30.202
- hx-2-esxi-3: 172.16.30.203

-----
VLAN NAME: hx-2-vm-network
VLAN ID: 40
Subnet: 172.16.40.0/24
-----

Hi Clifford. Does this mean that I can ignore the warning that pops up for the VLAN for the storage network?

 

VLAN
Validating 'storage-data' VLAN: 'xxx' specified for new cluster is already assigned

 

This is the only warning that pops up during validation. Can I skip validation.