Can you do Wireless Networking in HA Clustering with a Spark appliance

[Eikkichi]

HI All, 

Im trying to setup a cluster with 2 x 1575 Units . 

But trying to cluster the Wireless networks that is centrally managed. 

FWA

WIFI : 172.16.101.252/24

Cluster IP : 172.16.101.2

FWB

WIFI : 172.16.101.253/24

Cluster IP : 172.16.101.2

This gives out DHCP , Security zone was set to internal and then no zone . No traffic was allowed out. 

But it seems in a tcpdump there are arp requests and the cluster IP of .2 isnt responding to any of internal IPs

12:52:11.361309 IP 172.16.101.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
12:52:12.353312 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:13.076336 IP 172.16.101.10.50483 > 239.255.255.250.1900: UDP, length 137
12:52:13.353097 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:14.358596 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:14.860087 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:15.356050 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:15.959111 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:16.091400 IP 172.16.101.10.50483 > 239.255.255.250.1900: UDP, length 137
12:52:16.355050 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:16.843355 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:17.345830 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:17.852226 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:18.847154 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:19.115700 IP 172.16.101.10.50483 > 239.255.255.250.1900: UDP, length 137
12:52:19.155848 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:19.845372 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:19.858052 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:20.852728 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:21.935677 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:22.117612 IP 172.16.101.10.50483 > 239.255.255.250.1900: UDP, length 137
12:52:22.839832 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:22.842009 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:23.235685 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:23.350983 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:23.438320 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:23.746028 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:23.836770 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:23.843922 ARP, Request who-has 172.16.101.2 tell 172.16.101.11, length 28
12:52:23.873766 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:24.105803 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:24.353013 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:24.631552 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:24.631895 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:25.118494 IP 172.16.101.10.50483 > 239.255.255.250.1900: UDP, length 137
12:52:25.430212 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656
12:52:26.055958 ARP, Request who-has 172.16.101.2 tell 172.16.101.10, length 28
12:52:26.233184 IP 172.16.101.10.63492 > 239.255.255.250.3702: UDP, length 656

[Chris_Atkinson]

For awareness in sk178604 we see the following limitation.

SMB-2286 In Centrally Managed appliances, the standby member does not bring down the wireless networks.