- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- 4800G Setting Up VLAN for 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
Forums
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
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
11-15-2011 12:39 AM - edited 11-15-2011 12:43 AM
11-15-2011 12:39 AM - edited 11-15-2011 12:43 AM
4800G Setting Up VLAN for iSCSI
I have a couple of 4800G switches which as far as I can tell are not stacked. Both switches are used for our 2-host VMware cluster and 2-node StorageWorks P4300 G2 cluster.
PROBLEM:
There doesn't appear to be any VLAN's setup and either one SAN node or the other drops on an almost daily basis from the network for a few seconds, then reappears and begins a resync. This hammers the network and the VM's which use the SAN. I'm sure this is all because of the lack of segregation of iSCSI and TCP/IP traffic.
Both switches are linked back to a core set of switches and I believe hosts on either switch can ping each other at the moment.
PROPOSED SOLUTION:
I'd like to create a VLAN on both switches, and from what I've read, so long as the VLAN-ID is the same, devices such as storage nodes and HBA's connected to ports which are members of that VLAN should be able to talk to each other, regardless of what switch they are on, even though the switches are not stacked. Is that correct?
I think the configuration should go as follows:
- system-view {enters config mode}
- vlan 196 {creates VLAN if it doesn't existand enters VLAN view}
- interface gigabitethernet1/0/19 {enters config for that port}
- port access vlan 196 {assigns port to VLAN 196}
I assume I could then repeat steps 3 & 4 for other ports which I wish to assign to the relevant VLAN? Have I mised anything?
I would then make the same changes on the other switch but would need to do so fairly quickly to make sure I didn't lose SAN connectivity. Is there a way to assign a VLAN to a group of ports at once?
I don't want any traffic coming in or out of this VLAN because it's purely for iSCSI, so I assume I don't need to set a vlan-interface?
I'd appreciate any insight you cuold give me as I'm not familiar with HP kit at the moment.