- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Re: Nimble Replication
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
10-16-2014 06:38 PM
10-16-2014 06:38 PM
Hello,
We have purchased two nimble storage CS220 arrays.
We set up one successfully at our production site and now we are tasked with setting up the 2nd one at our DR site.
We are running into issues with figuring out how to route the replication traffic. We have successfully seeded our back ups onsite and have taken the 2nd unit to the DR site.
We have the production nimble using an iscsi vlan for mgmt and data and we want to do the same for the DR site.
Our onsite iscs vlan is 192.168.115.0/24 and the DR issci network vlan is 192.168.115.0/24 as well.
We have a private WAN connection going from our firewall to the DR firewall. We are using fortinets.
What do we need to do as far as routing to make sure these networks can talk to each other and handle replication?
Can you make iscsi networks routable?
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2014 12:23 AM
10-17-2014 12:23 AM
SolutionHello Riley, firstly a warm welcome to Nimble and Nimble Connect.
It's possible to route iSCSI networks but personally I wouldn't do it.
Within a Nimble system you had two options to replicate your data; over your management network or your iSCSI data network. Most customers chose to replicate over management.
With Nimble as long as you're on NimbleOS 2.1 you can create separate subnets for different requirements, which means you can create a dedicated Replication Subnet if you so wish.
This blog post might shed some light and give you some ideas in order to facilitate replication over your private WAN link: Nimble OS 2.1 Part 7: VLAN Tagging Support
twitter: @nick_dyer_