- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Nimble Data subnet discrepancy between active and ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2022 08:49 AM - last edited on 05-23-2022 09:30 AM by support_s
05-20-2022 08:49 AM - last edited on 05-23-2022 09:30 AM by support_s
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2022 10:14 AM
05-20-2022 10:14 AM
Re: Nimble Data subnet discrepancy between active and standby controller
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.
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2022 10:58 AM
05-20-2022 10:58 AM
Re: Nimble Data subnet discrepancy between active and standby controller
Thanks Sheldon, will do
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2022 01:00 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2022 10:28 PM
05-22-2022 10:28 PM
Re: Nimble Data subnet discrepancy between active and standby controller
Hi
Physical cabling correct yes, switch ports are being verified
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2022 02:05 AM
05-27-2022 02:05 AM
Re: Nimble Data subnet discrepancy between active and standby controller
Hi
Problem was resolved and it was related to switch vlan configuration not being correct. Once corrected swtich side problem was resolved.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2022 11:10 AM
05-27-2022 11:10 AM
Re: Nimble Data subnet discrepancy between active and standby controller
That's great to hear! Thank you for posting the root cause here.