Configuring Cisco SG300-20 switch for Hyper-V networking

or rather networking in general on this switch..

As good and easy to use this SMB grade switch is, there’s a bit to do to get things going and not all of it is very straightforward/easy to find in the interface. I have the following requirements:

  • Hyper-V hosts are on the subnet, VLAN 10
  • iSCSI network is VLAN 20
  • Production VMs are on VLAN 100
  • Dev/Test VMs are on VLAN 200
  • SCVMM virtual machine does not live on the Hyper-V hosts it manages. It’s on a separate host on a home-conventional network
  • Domain Controller (of course does DNS work) is on the network too
  • The NAS and the switch are also on the network (the NAS is used for some video sharing in the house)

Quick diagram:


As is evident from the diagram, the switch will provide L2 and L3 connectivity for this network. The homegrade router as dumb as it is does not allow for a static route to be put in. With this in mind, here it is

1. Set the switch to have a static IP address. Out of the box, it does not have a static address. I gave it

2. Before doing anything else, change the switch’s mode from L2 to L3. This is because the switch resets its config when the mode’s changed:


Save the config before going further.

3. Next, define the VLANs:


4. Next, define an interface for the VLAN that’s just been created. In other words, define the default gateway for this VLAN:


Quick note that until a device on this VLAN connects to the switch, the VLAN interface state is disabled:


5. Then go to Port to VLAN and tag the port with the new VLAN. Say a new host connects to port 5 on the switch:


I’ve left the mode to trunk, you could go with making it an access port.

6. Finally, if you need to create a static route to get to your home/another network, throw in a static route here (I didn’t need to)


This completes the switch side of things.

7. With the home router being a dumb device with nowhere to put in a static route, I resorted to throwing in static routes to the network manually into my management PC, the DC and the SCVMM machines:


8. It’s a given that the Hyper-V hosts will need the right VLAN tags in their NICs but here’s a screenshot of where/how for completion’s sake:


Happy days..

Leave a Comment

Your email address will not be published.