- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- P4500 with 10 Gb Ethernet - IP Configuration / Sub...
StoreVirtual Storage
1753448
Members
5030
Online
108794
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
Go to solution
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
тАО10-29-2009 01:06 AM
тАО10-29-2009 01:06 AM
I have 2 x P4500 Nodes with 10 Gb Ethernet Adapters. We would like to (if possible) have a completely isolated iSCSI VLAN / Subnet.
The big question is, can CMC manage this from another Subnet? Or more to the point, how can I assign a couple of NICs to another Subnet for management, but not allow iSCSI connections to these management NICs.
As I understand it, when I give two NICs an address on a different Subnet (and attach the SANiQ to these NICs), the CMC (or SANiQ interfaces) must still communicate with the Virtual IP Address (on iSCSI Subnet). It can't because there is no routing between the subnets. If I add a VIP on the management Subnet, then I believe people can still make a connection to these targets defeating the purpose of a secure iSCSI Subnet.
Just to confuse matters I would ideally like all 10 Gb adapters on the iSCSI Subnet. Does replication occur only through the SANiQ interfaces? If so then would I lose out by using 1 Gb Ethernet for the SANiQ interfaces?
The big question is, can CMC manage this from another Subnet? Or more to the point, how can I assign a couple of NICs to another Subnet for management, but not allow iSCSI connections to these management NICs.
As I understand it, when I give two NICs an address on a different Subnet (and attach the SANiQ to these NICs), the CMC (or SANiQ interfaces) must still communicate with the Virtual IP Address (on iSCSI Subnet). It can't because there is no routing between the subnets. If I add a VIP on the management Subnet, then I believe people can still make a connection to these targets defeating the purpose of a secure iSCSI Subnet.
Just to confuse matters I would ideally like all 10 Gb adapters on the iSCSI Subnet. Does replication occur only through the SANiQ interfaces? If so then would I lose out by using 1 Gb Ethernet for the SANiQ interfaces?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2009 09:52 AM
тАО10-29-2009 09:52 AM
Solution
I'd advise you use the two 10Gb adapters (preferably bonded) for all you iSCSI and replication. You can make that a totally isolated network.
You'll assign the 10Gb network as the "SAN/iQ" network. That means all iSCSI traffic and replication will occur there.
Using either of the 1Gb adapters (or both bonded, also the preferred method) to connect to a "public" type network for you to do management is fine.
The CMC can connect and manage the system on either network.
The CMC does not need to connect to the VIP, VIP is only used for iSCSI discovery.
Essentially the "SAN/iQ interface" is the one used for iSCSI and replication, and management is allowed on any network.
You'll assign the 10Gb network as the "SAN/iQ" network. That means all iSCSI traffic and replication will occur there.
Using either of the 1Gb adapters (or both bonded, also the preferred method) to connect to a "public" type network for you to do management is fine.
The CMC can connect and manage the system on either network.
The CMC does not need to connect to the VIP, VIP is only used for iSCSI discovery.
Essentially the "SAN/iQ interface" is the one used for iSCSI and replication, and management is allowed on any network.
Adam C, LeftHand Product Manger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 08:03 AM
тАО11-02-2009 08:03 AM
Re: P4500 with 10 Gb Ethernet - IP Configuration / Subnets Question
For management, could you just manage the cluster from one of the machines that are connected to the iSCSI subnet? Meaning just remote desktop to a machine that connects to a volume on the cluster?
You've got other options for management as well, you can setup routing to the iSCSI VLAN and then use ACL's to block all but the specific management stations access to the iSCSI VLAN.
For management, you need access to all the nodes individually (I believe). The VIP is uses for iSCSI access and load balancing, not for management.
Hope that helps.
You've got other options for management as well, you can setup routing to the iSCSI VLAN and then use ACL's to block all but the specific management stations access to the iSCSI VLAN.
For management, you need access to all the nodes individually (I believe). The VIP is uses for iSCSI access and load balancing, not for management.
Hope that helps.
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