Cisco SG300-28 Vlan for vmware

[rmccas]

Hi all

I recently bought a cisco sg300-28 ports for my vmware lab.

This is the current setup i have:

3x Supermicro with 6 nics each and a Synology 1813+ for VM storage.
HP switch v1910-24 Ports
A tplink router for the internet access


I can run the lab without issues on the same subnet 192.168.x.x/24 but with the cisco i would like to separate traffic with vlans.

Vlan 1 home network (laptot, mobile, internet, wifi etc etc)
Vlan 10 Management (2 nic LAG)
Vlan 20 vMotion (2 nic Lag)
Vlan 30 VMs (2 nic lag)
Vlan 40 NFS (4 nic lag)
Vlan 60 iscsi (2 nic lag)
Vlan 60 internet access (access from all vlans to have internet access)

The problem is that i have no knowledge on configure Cisco switches. I did configured some lag on the hp switch and all is working, but now Cisco is a new challenge...

I also added the static routes on my internet access router

tagged, untagged, trunk access is just Chinese to me

Every time i try i just break my kit and have to go back for on network again.

Any expert here ? any help is much appreciated. i can provide more information if needed

i guess my next goal will be some cisco certification course.

Thanks
RS

 

[bmh.01]

For a start the SG series aren't really cisco switches, so you've got it "easy" with a web based gui to use.

You'll need to read up on vlans in general if you are at this stage. But in a nutshell you need to make sure the switch is in L3 mode, configure your vlans, then interfaces on each vlan to route between them where required.

 

[Cmustang87]

VLANs get confusing if you don't really have an understanding really what you are trying to achieve. People will really muddle the terminology and get mixed up between layer 2 and layer 3 while learning this.

"Trunk" and "access" ports is Cisco IOS terminology, but everyone else uses "tagged" or "untagged". This is all relevant to IEEE 802.1q.

A VLAN is a Layer 2 technology. A VLANs goal is to chop up switchports at layer 2. Kind of like, taking a 16 port switch, and breaking it in half into 2x 8 port switches. If those two switches do not connect to each other directly, or through a router, you would have no way to have hosts communicate amongst themselves. Even if they EDIT: were on the same subnet, these are 2 completely separate broadcast domains!

Layer 3 switches allow you to add an IP address as a virtual interface called switched virtual interfaces (SVI), then configure them as a VLAN interface. These allow switch ports to process packets at layer 3, even though the SVI is not a "real" physical interface.

Implementing 802.1q (trunking, tagged) on ports basically tells that interface to encapsulate the packet with the VLAN tag (VLAN ID) of which VLAN that packet belongs to, so that way any interfaces upstream or downstream knows how to handle the information.

You would implement that technology if you had VLANs on a switch, but that switch had no way of routing information between the VLANs. You would "trunk" or "tag" that traffic up to a router or your edge firewall, and create "sub-interfaces" (which are virtual interfaces on 1 single physical interface) with an IP, so that sub-interface can be used as a gateway for that specific VLAN.

If you didn't implement trunking, you would need to use more ports on your router and your switch as egress/ingress to accommodate each of the VLANs.

I NINJA EDITED THIS INTO THE GROUND

 

[Cmustang87]

If I were you, I would roll back configuring link aggregation and get a firm hold on how VLANs work and function before implementing your LAG groups. Learning two things at the same time makes your troubleshooting and learning experience a nightmare.