- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: Rebalance Gateway Connections
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-10-2011 06:16 AM
10-10-2011 06:16 AM
Re: Rebalance Gateway Connections
You have a good point there. The FOM is there to decide which site must stay active in case of a split-brain situation on the network.
If you want to move the FOM to the first site, you can remove the FOM and start the manager on the third storage node... Result would be the same then...
If my post was useful, clik on my KUDOS! "White Star" !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2011 06:31 AM
10-10-2011 06:31 AM
Re: Rebalance Gateway Connections
That's exactly what I'm thinking: if the FOM is in the same site, there's no need for it anymore, just start a third manager in the primary site.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2011 08:03 AM
10-10-2011 08:03 AM
Re: Rebalance Gateway Connections
Can you inform me wether your systems (ESXi-servers) are grouped into sites, or not? I suspect your servers aren't grouped into a site, thus SAN/iQ has no idea that it needs to rebalance the Gateway Connections.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2011 11:16 AM
10-10-2011 11:16 AM
Re: Rebalance Gateway Connections
It depends from customer to customer... Some want site-aware servers, some others not... Performance versus high availability... A lot depends of the ISL between the sites...
Kr,
Bart
If my post was useful, clik on my KUDOS! "White Star" !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2011 02:07 AM
10-13-2011 02:07 AM
Re: Rebalance Gateway Connections
I'm still struggling with what the Gateway Connections actually do in a Multi-Site SAN with site-affinity for ESXi-hosts.
An ESXi-host connects to the cluster's Virtual IP and gets redirected to one of the storage nodes. You can see which storage node a host connects to for each volume by viewing the Gateway Connection. Each volume is accessed through the same storage node, so all hosts connecting to a volume show the same Gateway Connection.
What other implications does the Gateway Connection have when connecting ESXi-hosts in a Multi-Site SAN (single Virtual IP, two sites)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2011 04:13 AM
10-13-2011 04:13 AM
Re: Rebalance Gateway Connections
If the servers are site aware they should connect to a node (with a manager running) in their specific site.
If the servers are not site aware they should connect to all nodes available...
My test/demo setup is currently single site so I cannot validate this though... If I have the occasion I will take a deeper look at it...
Kr,
Bart
If my post was useful, clik on my KUDOS! "White Star" !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2011 05:39 AM
10-13-2011 05:39 AM
Re: Rebalance Gateway Connections
In other words, does a host connect to multiple hosts for a single volume?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 12:00 AM
10-14-2011 12:00 AM
Re: Rebalance Gateway Connections
If you install the MPIO DSM (currently available only for Windows) then yes the server will connect to all available storage nodes... If the MPIO DSM is not installed it will connect through the VIP...
Since the MPIO DSM does not exist yet for ESX, the only way to get the best performance is to create multiple VMkernel ports and bind them to the vmhba following the procedure that is already often mentioned here on the forums. Command line stuff in ESX4, via the GUI in ESX5...
Kr,
Bart
If my post was useful, clik on my KUDOS! "White Star" !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2011 07:35 AM
10-15-2011 07:35 AM
Re: Rebalance Gateway Connections
yeah, not having a DSM for ESXi is a real downer at the moment.
I did a test this week: the storage node that is the Gateway Connection for a volume handles *all* I/O to/from the ESXi-host. The storage node will communicate with other storage nodes on the back-end to fetch / write blocks. This limits the maximum performance of a single volume to the maximum performance of a storage node. Because SAN/iQ assigns Gateway Connections to as much storage nodes as possible, this will load balance a bit, but it's a non-optimal configuration.
HP needs to release a DSM (or MPP) for ESXi to get performance for a vSphere environment on par with a Windows environment.
- « Previous
-
- 1
- 2
- Next »