topic Re: Nimble Data subnet discrepancy between active and standby controller in Array Setup and Networking

Nimble Data subnet discrepancy between active and standby controller

CRD — Mon, 23 May 2022 16:30:33 GMT

Hi there

Looking for some advice on how to resolve this. Have picked up at a client that there is a discrepancy between the Data Subnets Network, Netmask and VLAN id between the active and standby controllers.

This is causing controller manual failover and Nimble firmware update to fail with alert saying contact Nimble support...which will be done just thought I should get some advise here as well.

This array is in production and the active controller A has the correct settings

Thanks

Re: Nimble Data subnet discrepancy between active and standby controller

Sheldon Smith — Fri, 20 May 2022 17:14:11 GMT

Definitely contact Nimble Support!

I wouldn't have thought that to be possible. The subnets are managed at the Group level, which encompasses the array, which encompasses the controllers.

Please reply with whatever Nimble Support finds and the resolution.

Re: Nimble Data subnet discrepancy between active and standby controller

CRD — Fri, 20 May 2022 17:58:44 GMT

Thanks Sheldon, will do

Re: Nimble Data subnet discrepancy between active and standby controller

mamatadesaiNim — Fri, 20 May 2022 20:00:56 GMT

Is your physical cabling and config of switch ports verified to be correct for both controllers?

Re: Nimble Data subnet discrepancy between active and standby controller

CRD — Mon, 23 May 2022 05:28:58 GMT

Physical cabling correct yes, switch ports are being verified

Thanks

Re: Nimble Data subnet discrepancy between active and standby controller

CRD — Fri, 27 May 2022 09:05:28 GMT

Problem was resolved and it was related to switch vlan configuration not being correct. Once corrected swtich side problem was resolved.

Thank you

Re: Nimble Data subnet discrepancy between active and standby controller

mamatadesaiNim — Fri, 27 May 2022 18:10:11 GMT

That's great to hear! Thank you for posting the root cause here.