- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: P4500 Remote Node Configuration
StoreVirtual Storage
1747985
Members
4928
Online
108756
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО06-01-2011 06:23 AM
тАО06-01-2011 06:23 AM
P4500 Remote Node Configuration
I have a P4500 Multi Site SAN with two nodes in each site (currently connected via fibre with a 10GB backbone)
The entire iSCSI network is contained inside a vlan with no interaction with 'normal' network traffic.
This has been in production for over a year with no issues.
I now have two additional nodes that I want to install as remote nodes (in a far far away place) which will only be connected via a 10MB pipe (slow.... remember those days when we thought it was fast?). I will use these nodes for remote copy snapshots.
My question is.....
What network IP address do I give them so that a: the primary nodes (and the CMC) can still see and communicate with them and b: I am not sending ALL iSCSI traffic over the slow 10MB pipe?
My production site is in the following range:
192.168.100.1 - .62
255.255.255.192
no gateway set.
Any thoughts would be appreciated!
Thanks
Scott MacLaren
The entire iSCSI network is contained inside a vlan with no interaction with 'normal' network traffic.
This has been in production for over a year with no issues.
I now have two additional nodes that I want to install as remote nodes (in a far far away place) which will only be connected via a 10MB pipe (slow.... remember those days when we thought it was fast?). I will use these nodes for remote copy snapshots.
My question is.....
What network IP address do I give them so that a: the primary nodes (and the CMC) can still see and communicate with them and b: I am not sending ALL iSCSI traffic over the slow 10MB pipe?
My production site is in the following range:
192.168.100.1 - .62
255.255.255.192
no gateway set.
Any thoughts would be appreciated!
Thanks
Scott MacLaren
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2011 07:16 PM
тАО06-01-2011 07:16 PM
Re: P4500 Remote Node Configuration
You will have to assign your iSCSI network a default gateway (firewall or router) that will route any traffic destined for the remote iSCSI network.
The remote iSCSI network should be on a separate network (subnet) connected via gateway.
Another way would be to add the other nodes to the iSCSI network as a part of the same stretched VLAN.
The remote iSCSI network should be on a separate network (subnet) connected via gateway.
Another way would be to add the other nodes to the iSCSI network as a part of the same stretched VLAN.
http://www.tdonline.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2011 12:41 AM
тАО06-02-2011 12:41 AM
Re: P4500 Remote Node Configuration
As mentioned by Teledata, you would require a Gateway on the Nodes to talk to outside world.
A router which would connect it to the DR site.
If possible bring the 2 additional Nodes to the Primary Site and perform a prime sync.
This makes sure that subsequent snapshots will of much smaller size.
A router which would connect it to the DR site.
If possible bring the 2 additional Nodes to the Primary Site and perform a prime sync.
This makes sure that subsequent snapshots will of much smaller size.
I work for HPE
--------------------------------------------------------------
How to assign points? Click the KUDOS! star!
--------------------------------------------------------------
How to assign points? Click the KUDOS! star!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2011 12:19 PM
тАО06-02-2011 12:19 PM
Re: P4500 Remote Node Configuration
Thanks for the quick feedback. This is along the lines I suspected (the lack of a gateway on my initial installation lead me to believe I would ultimately need a router in place.) We will be attempting the initial config this weekend and I will update if I have any issues.
I have the two new units at my main center and already plan to do the initial sync here at high speed once I get the config out of the way!
Rgds
Scott
I have the two new units at my main center and already plan to do the initial sync here at high speed once I get the config out of the way!
Rgds
Scott
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP