- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- HPE Nimble Storage Solution Specialists
- >
- Re: changing protocol
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
Forums
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
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
09-23-2023 09:03 AM - last edited on 09-26-2023 09:19 AM by support_s
09-23-2023 09:03 AM - last edited on 09-26-2023 09:19 AM by support_s
We have setup our HPE Nimble using the FC protocol.
Now we need to change the protocol to FC and iSCSI (to workaround a Veeam backup issue).
Is it safe and non-disruptive? The LUNs are all in use and in production.
Solved! Go to Solution.
- Tags:
- nimble
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2023 10:04 AM
09-23-2023 10:04 AM
SolutionHi Marcel_E,
The process of switching an HPE Nimble Storage array from FC (Fibre Channel) to a combination of FC and iSCSI can be complex and disruptive.
Especially when LUNs are in production, this change should be approached carefully.
Here are some guidelines before changing the protocol:
1. Ensure that you have a verified backup of your data before making any changes. It is always important to maintain data integrity.
2. Your HPE Nimble storage environment should be capable of supporting both FC and iSCSI protocols simultaneously.
3. Make sure your network infrastructure, including switches and routers, is configured to handle FC and iSCSI traffic. Zoning your FC switches and setting up iSCSI VLANs are part of this process.
4. Be aware of the implications of this change if you are using replication. Replication between FC and iSCSI can be complex, so plan accordingly.
5. Both FC and iSCSI must be supported by the host bus adapters (HBAs).
6. Make sure both FC and iSCSI paths are properly configured for multipathing.
7. Before making changes to production, perform thorough testing in a controlled environment. By doing this, you will be able to identify potential problems and mitigate them.
8. It may be necessary to have some downtime as part of the change and communicate this to your stakeholders in advance.
9. Contact the HPE Nimble Storage support team and get guidance specific to your environment and configuration.
Hope this helps.
Regards,
Satish
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2023 12:05 PM
09-23-2023 12:05 PM
Re: changing protocol
Thanks for the quick reply!
I already had a feeling that changing the protocol wasn't without some costs so I'm not going to do this.
I'd rather go and reinstall Veeam and restore the configuration. More safe.