HPE Aruba Networking & ProVision-based
1832676 Members
2836 Online
110043 Solutions
New Discussion

Create Storage VLAN - Newbie

 
pparkerii
New Member

Create Storage VLAN - Newbie

Ok, here goes...  I inherited some tasks after someone left the company.... my excuse ;)

 

The way I understand HP VLAN'ing (as of today), is that you can have a port (set mode to) as "Untagged" in a single vlan (normally the default vlan),  "No" in a single vlan and "Tagged" in multiple vlans.  Is this a correct?

 

I need to (would really like to) create a storage VLAN at a remote site that currently has 2 VLAN's: vlan 1 (default) and vlan 200 (VoIP).  No storage vlan exists for vmware or for iSCSI, they currently access all storage over the same network as the desktops and servers - I would like to segregate the storage traffic from the Production Network because it's the right thing to do.

 

But, I don't want to lose access to the switch (remote) so I figured I would post here :)

 

After I create "vlan 20" (storage), I want to define 2-4 (and more in the future) switch ports for this storage vlan, to be used for a new (first one) VMware host server to connect NFS datastores on a NetApp filer for the VMware guest machines).

 

The ports that I want to use on the switch do not need access to anything other than the storage vlan because again, they're for back-end storage access.

 

The new storage "network" will be defined on a new 10.181.0.0 vlan (I have not yet created the VLAN or assigned an IP to the logical vlan interface because I wanted to run it by this group first).

 

The VMware vSwitch VMkernel Port will be assigned 10.181.0.2, the NetApp VIF will be assigned 10.181.0.3 and the logical VLAN Interface on the switch will be assigned 10.181.0.1

 

On the switch, when I'm "playing" with the port modes on a test vlan (no IP assigned yet to the vlan), for specific ports, it seems that (which is how I got my new "understanding" as mentioned above) I can set a port to "No" to 1 vlan, "Untagged" to 1 vlan and "Tagged" (again, I now have the three vlans) as I understand it to multiple vlans.

 

My question is... to segregate the storage vlan ports, do I have to set the vlan 20 (storage) ports to "untagged" on vlan 20" (storage), which will set the storage vlan as the "default vlan" for the selected ports, and if so, how I can I set the remaining ports (that I will use) to "No" on vlan 1 (default) and "No" on vlan 200 (VoIP)?  Because I do not want to "tag" either - It seems that when I select a port, I'm not able to set it to "No" on both of these vlan's, only one of them.  I'm able to change the port mode in default as "No", then set the port mode in storage vlan as "untagged", but it remains "tagged" in vlan 200 (VoIP) - do I (can I) set the port mode in VoIP vlan as "deny"?

 

Again, these ports need access to (only) vlan 20 (storage) so having the ports as "tagged" in VoIP doesn't make sense to me, yet I don't want to "play" with a remote switch and lose connectivity.

 

Thoughts?

2 REPLIES 2
pparkerii
New Member

Re: Create Storage VLAN - Newbie

After changing the three ports that I want to use in vlan 20 (storage) to "untagged", it seems that I could then change the port mode on these three ports to "No" in BOTH the default vlan and the VoIP - I couldn't do this previously, perhaps it was the sequence I took.... Is this the way it should be done? untagged in the vlan I will use for storage access and "no" in all others?
Chrisd131313
Trusted Contributor

Re: Create Storage VLAN - Newbie

Hi pparkerii,

 

If you have a Storage VLAN which will be segregated away from all other VLANs and there is no need to perform any inter-VLAN routing to/from it then you just need to add teh ports to the VLAN as untagged. This means that the port will be a member of the VLAN like a port is set to access on Nortel/Cisco, etc.

 

If you need multiple VLAns to traverse a port then you need to tag the VLANs on that port, i.e if you have a uplink from a core switch to an edge switch which has ports in multiple VLANs the uplink will need to be tagged for those VLANs so it will pass the traffic for all teh VLANs.

 

The "No" option is automatically added to any new VLANs that are added to a switch before you assign untagged or tagged ports to it. if you have set ports to tagged in specific VLANs and untagged on another then you can use "no" to remove the tagged port from the designated VLAN.

 

So with your scenario, I would have the ports that need to be in your storage VLAN as untagged and not tagged in any other VLAN, this will then automatically set all other VLANS on the switch to "no" for those ports. If you have already taged ports in multiple VLANs you will need to remove them by preceeding the cmd with "no".

 

   e.g.  no vlan 6 tagged a1

 

A port can only be untagged in one VLAN but it can be tagged in multiple...

 

Taken from a HP doc....

 

Note: When multiple VLANs exist on a switch, only one VLAN can be untagged for each port. (In the default configuration, this is VLAN 1, the DEFAULT_VLAN.) When you add a second VLAN to a switch, the default setting on that VLAN is No for all ports. Using the Web browser interface, if you then reconfigure a port to Untagged for a new VLAN while there is an Untagged setting on another VLAN for the same port, the switch automatically reconfigures the other VLAN setting to No. For example, if you configure Port A1  as Untagged for the 2nd VLAN, then the switch automatically reconfigures DEFAULT_VLAN for port A1 as No

 

HTH

 

-----------------------------------------------------

Don't forget to mark a post resolved if your question was answered.