- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Web and Unmanaged
- >
- Re: HP 1800-24G Trunking, vLANs and iSCSI
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
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
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
тАО02-17-2009 09:55 AM
тАО02-17-2009 09:55 AM
HP 1800-24G Trunking, vLANs and iSCSI
We have a client running a small iSCSI setup on a single 1800-24G. To make it a little bit more resilient, a second 1800-24G will be added to the configuration using a trunk of 2 (or maybe 4) ports. As I understand it the current config is pretty simple in that all the iSCSI host/target ports are in one VLAN with the MGT port in another. Using the GBic is not (currently) an option.
I believe an attempt was made at this in the past by someone else and when they created the trunk, it seemingly created some sort of broadcast storm taking out the first live switch (and thus the iSCSI connected servers)!
Now obviously, having been 'volunteered' to 'sort this out' I'd rather like to avoid emulating the previous lamb but understand that without a copy of the current configuration and the somewhat hazy secondhand information, thats not exactly straightforward!
The client has informed me that there has been one change since that first attempt - flow control was on for all ports but is now switched off for all ports (as it was causing intermittent iSCSI performance dropouts).
If anyone can either suggest:
a) why/how the trunk (could) cause the original problem
or
b) a suggested config for the trunk,vlans etc that wont cause a similar issue! :)
..then it would be much appreciated
..as I am due on site in a few days to add a second iSCSI SAN controller with half of its (4) ports on switch-A and half to switch-B; plus the same for the original iSCSI SAN controller too..
Cheers,
"larry the lamb"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2009 10:43 AM
тАО02-17-2009 10:43 AM
Re: HP 1800-24G Trunking, vLANs and iSCSI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2009 09:44 PM
тАО02-17-2009 09:44 PM
Re: HP 1800-24G Trunking, vLANs and iSCSI
There isn't enough info here to get a good enough idea of your overall design is to offer much advice. A network diagram would be helpful along with a more detailed explanation of what you├в re trying to do.
I work for HP, but my posts and replies are my own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-18-2009 03:02 AM
тАО02-18-2009 03:02 AM
Re: HP 1800-24G Trunking, vLANs and iSCSI
Also attached is a quick Rolf Harris sketch of proposed config for clarity :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-18-2009 03:05 AM
тАО02-18-2009 03:05 AM
Re: HP 1800-24G Trunking, vLANs and iSCSI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-18-2009 05:37 AM
тАО02-18-2009 05:37 AM
Re: HP 1800-24G Trunking, vLANs and iSCSI
For the server, you'll want to create the "team" so that you have one primary and one failover link, not a trunk that would act as a single logical link.
For the iSCSI Arrays, you could create separate logical links for the connections that go to each switch, but then one of those connections would need to be primary with the other one configured as a failover link.
The reason for this is that you cannot spread an 802.3ad link across switches. If the switches supported spanning tree, you'd need to make sure your server and array configurations supported this type of operation, otherwise it isn't necessary to even consider.
What make/model of server and arrays are these?
I work for HP, but my posts and replies are my own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 01:53 PM
тАО02-23-2009 01:53 PM
Re: HP 1800-24G Trunking, vLANs and iSCSI
I'm actually attempting to do the same thing but its for my esx environment. If you have found a solution please post it.
(My Issue for those interested)
3 IBM x3550 Servers
2 Procurve 1800-24 Switches
1 IBM DS3300 SAN
I'm completely confused by vlans and trunking but know that I need them in my environment. Google provides not much and the product manuals aren't very detailed, especially for a new user. Anyways hope to hear the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 03:24 AM
тАО02-24-2009 03:24 AM
Re: HP 1800-24G Trunking, vLANs and iSCSI
FYI, the arrays in question are Infortrend A16-G2130-4 (single controller(!), 4 x iSCSI channels). The intel servers are Dell 1900/1950's using either QLA405xC or MS iSCSI via internal NIC/TOE.
The connections between server and switch/array and switch are NOT grouped/trunked at this stage.
The only trunk being considered is/was for intra-switch bandwidth/failover.
-------------------------------------
To further confuse things? (sorry!)
What is/was strange is that even without any trunking enabled i.e. just a single cable connection between the two 1800s - inexplicable connectivity issues were occuring.
The only thing that I can imagine causing this are 'strange/undocumented' settings on their 'core' L3 switches. There is a connection to one of these via port 24 on the original switch #1 ..port 24 is in MGMT vLAN only.
What doesnt help here is the fact the customer doesnt know how/what is set on these 'core' switches - they're not HP's they are NetGear PROsafes I believe :(
Thus, unfortunately, as it stands at the moment the customer has taken the decision to keep the switches separate as (at present anyway) the SAN's are in effect islands :/
Some points dished out for assistance so far.. thanx folks :)