Tag: Cisco

Create VLANs on a Cisco 2960G

Add VLANs and Assign Ports on Cisco 2960G Switch

This post will be focusing on the Cisco 2960G Switch I acquired in my post titled “Homelab Rebuild – Part 1 – Intro“.  Here I will be working on configuring the switch. This includes adding a VLAN for my WAN connection, adding ports to the VLANs and setting up a management interface.

Creating VLANs on a Cisco 2960G switch is a pretty straight forward task. You will need a Cisco WS-C2960G-8TC-L Switch and a USB to Serial ConverterPutty, or your favorite serial/SSH client, will also be needed. This tutorial assumes you already know how to connect to your switch using Putty.

Looking to configure similar settings on a Dell switch? Take a look at my blog post titled, Add a VLAN on a Dell PowerConnect 5524p Switch for help.

 

Follow along with the video tutorial!

Create the VLANs

First off, we need to enter configuration mode on the Cisco 2960G Switch. To accomplish this, type: “conf t” and hit the enter key.

Cisco 2960G VLANs conf t

Create VLAN5 – this our WAN VLAN. Type the command “vlan 5” and hit enter. Give your VLAN a name. In my case, VLAN5 is used for my WAN connection, so I gave it the name of “WAN” – you do not have to type name twice. I goofed on the first attempt. I wanted WAN in all caps. Then type “exi” or “exit” and hit enter.

Cisco 2960G VLANs database config

Create VLAN25 – this is our management/production VLAN. Type “vlan 25” and hit enter. Again, give your VLAN a name. Type “name Production” and hit enter. Exit VLAN 25.

Cisco 2960G VLANs 25 Creation

 

Change the host name

Also, while we are in config mode, lets take a moment to setup the switch’s host name. You do this by entering the command “hostname SW-ACH-WAN” and hitting enter. You will now see the switch’s host name change.

Cisco 2960G VLANs - Hostname Change

 

Assigning ports

After creating our VLANs, we need to assign switch ports to them. Otherwise, they are just VLANs. You can issue the command “show vlan” and the switch will show you all of the VLANs present on the Cisco 2960G and which switch ports are assigned to which VLAN.

Cisco 2960G VLANs - assign ports

In the screenshot above, you can see all eight ports are assigned to VLAN 1. You can also see we’ve created VLAN 5 with the name of “WAN” and VLAN 25 with the name of “Production”.

To assign ports to these VLANs, you must again enter config mode by typing “conf t” and hitting the enter key. Then, you need to enter each interface. Enter an interface by typing “interface gigabitEthernet 0/#” – Where the # is, is the port number. So, “interface gigabitEthernet 0/1” and hit enter.

Next, type “switchport access vlan 5” – this allows the switch port to access vlan 5. Then add your description by typing: description “Modem Uplink” and hitting enter. Finally, exit the interface you are working on and proceed to the next.

Cisco 2960G VLANs - switch interfaces

The table below gives a good break down of each port that I am using, what VLAN it is on and the purpose.

Switch Ports

SwitchportVLANDescriptionPurpose
15Modem UplinkThis port is where I will plug my Spectrum modem into, thus being my modem uplink on VLAN 5
25Uplink to ACH-FW01I will plug the physical NIC on HOST01 that is assigned to my firewall, ACH-FW01 into this port so that it can access the WAN connection.
35Uplink to ACH-FW02I will plug the physical NIC on HOST02 that is assigned to my firewall, ACH-FW02 into this port so that it can access the WAN connection.
725Management NetworkThis will connect the switch to my Dell switch stack so that I can manage the WAN switch from my production network, VLAN25.

 

Management VLAN

Since we are using VLAN 25 to access our management network, we need to assign it an IP Address. We do this by entering the VLAN as an interface. So, enter the command “interface vlan 25” and hit enter. You will now be in the interface config mode. Next, type the command “ip address 192.168.25.4 255.255.255.0” and hit enter. Be sure to use your IP addressing scheme for your management network. The 255.255.255.0 is a /24 subnet mask.

Cisco 2960G VLANs - assign ip

 

Saving the configuration

Now that we have configured our switch, it is time to save your running config. If you do not save the running configuration, all of the changes will be lost when you reboot the switch. To save the config, type “copy run start” and hit enter.

Cisco 2960G VLANs - save running config

Summary

Some good reference reading can be found right from the manufacturer, in this case it is Cisco. You can check out this article regarding VLAN configuration on the Cisco 2960G switch.

Please feel free to check out some of my latest blog posts or my about me page to learn more!

Permanent link to this article: https://achubbard.com/2018/03/05/create-vlans-cisco-2960g/

Homelab Rebuild – Part 1 – Intro

Homelab Rebuild

For the last year and a half, I have been all about consolidating my gear. I got into this funk where I absolutely wanted nothing to do with enterprise equipment in my home. I wanted to go home and just be home. However, that attitude has sacrificed a lot of my personal learning and growth. I am a guy who LOVES to tinker. Doesn’t really matter what it is, I just love to tinker and I love gear.

After talking with some fellow IT guys during a meeting recently, I realized, I miss having the gear to work on at home. I missed having the resources to test something and not give a care if I break something.

I’ve also recently started this blog and am attempting to teach myself about WordPress, it’s plugins and WAFs (Web Application Firewalls). I felt re-invigorated to acquire some gear new gear. I am hoping this blog, and purchasing some new gear, will keep me interested in a hobby that has turned into a career for me.

 Hardware – Dell R510, R610

Hosts

I have acquired 2 Dell PowerEdge R610s to use in my rebuilt homelab. Both are outfitted with only 16GB of RAM. Ideally, I would love to increase this to 32-48gb of RAM per host. The price was right on the two machines the way they sit so I figured I would just outfit them as needed. As low power is a slight concern for me, I ordered a pair of Xeon L5630s for each machine.

Shared Storage

I would love to have a true Dell SAN to go with the rest of my Dell stack, however, they are subtly out of my price range at the moment. Can you tell? I am a rather big Dell guy when it comes to servers. I picked up an 8 bay Dell R510, was hoping for a 12 bay, but this will give me a start. Honestly, with the size of drives these days, 8 bays should be sufficient for what I am using it for. This will allow me to install my collection of hard drives and pass them through to FreeNAS. I have also picked up a set of 10gb Mellanox cards and cables.

Mellanox Network Cards - 10GB

Dell R510 FreeNAS SAN, Dell R610 Hosts

Network

I picked up a pair of Dell PowerConnect 5524Ps. Initially, I planned on using these as my VM switches and picking up a 48 port Cisco of some variation for my core switch. However, I’ve decided I would use both of these for the time being and forgo the Cisco idea. The 5500 series Dell switches support stacking via HDMI cable, not something I have ever tried, but I scored both switches for a song and this is homelab right?

Dell Switches Homelab Rebuild Network

I did however, purchase a Cisco WS-C2960G-8TC-L switch to hand off my modem to my firewalls. This will give me some redundancy…err at least to my firewalls. Maybe someday I will get a secondary WAN connection and setup some type of failover.

Homelab Rebuild Cisco Network Switch 2960G

VLANs, what good is a homelab without VLANs?

WAN – VLAN5

I will provision 3 ports on the Cisco C2960G on what I call VLAN5. Taking the link from my cable modem, I will feed the WAN into 1 port, and send it out the other 2 additional ports to my redundant firewalls. VLAN5 will only exist on the Cisco switch. By setting up the environment this way, it gives me a little bit of redundancy, at least, in my mind. Obviously my two single points of failure are my cable modem and the Cisco switch.

iSCSI Network – VLAN10

As the hosts will have no local storage, we will need to create this VLAN to handle all of the iSCSI/Storage traffic for both. This VLAN will only be present on the Dell stack.

vMotion Network – VLAN15

This VLAN will allow the movement of virtual machines back and forth between my two hosts.

Production/Home Network – VLAN25

VLAN25 is where most of the err….action…happens. This is where my end devices sit. I don’t typically try to break that stuff up in my home environment. This VLAN will be on both the Dell stack and Cisco switch. It will only be present on the Cisco switch so that I can manage the switch from my workstation.

Security Cam Network – VLAN35

My security cameras were once on VLAN25….with everything else… my network was in essence…flat. I currently have 9 cameras with the plan to add a few more (small farm, we have animals etc so we like to keep an eye on things) – I decided it was time to break them out into their own VLAN. Enter stage left, VLAN35. Some of you reading this may be asking, how does this guy pick his VLAN numbers?? Honestly, the number is in direct correlation to the 3rd octet of the VLAN. So, an example might be, 10.10.35.0/24 – the x.x.35.x is where the number comes from. Just something I came up with and ran with.

Guest Network – VLAN45

I do not typically have a lot of guests at my house, we’re out in the woods and people don’t like to visit. I’m ok with that. However, when we do have the occasional guest, I would rather they be on their own VLAN and have no access to anything other than the internet.

Area 51 – VLAN51

This is a new one for me. VLAN51 will become my secure VLAN. It will have no access to the internet. No access to the rest of the network. Any VMs that are apart of VLAN51 will be shut down when not in use. VLAN51 will be used to network my penetration testing VMs.

Network Layout

Homelab Rebuild Network Design

Power

Since I am moving my office to my basement, I will be working on installing two dedicated circuits for my new lab. My electrical panel is right there and access is fairly easy. Most likely these will be 2 – 20 amp circuits. I am not an electrician, I just play one on the internet. Just kidding, please if you are going to run your own circuits, be aware of the risks involved. I am fairly comfortable working with electricity.

One thing I regret selling is my UPS. That is a pricey component that I will need to re-acquire at some point. I have a couple of smaller ones, and frankly, it’s my homelab, if it goes offline, eh not the end of the world.

Rack

One item that I had a hard time selling when I was consolidating my lab, is my 25u StarTech Open Frame rack. I had advertised it locally numerous times and never had anyone actually come and buy it. So I kept it and I am glad I did. It’s one less thing I need to purchase for the this adventure. I am planning on either enclosing it or putting it in a small server closet in my shop/office. This will hopefully help keep the noise down.

Software – FreeNAS, VMWare, pfSense

Hypervisor

Something I never needed before was a VMUG subscription. I always had access to VMWare products through work. This time around I will be purchasing the $200 subscription so that I can utilize all of the products that come with it. Both of my hosts will be running ESXi. I will also be using the vCenter appliance instead of the Windows based vCenter install since that is the way things are headed anyways.

Shared Storage

Several years ago I utilized FreeNAS as my SAN for a POC (Proof of Concept) for a previous employer. This worked out very well. FreeNAS will be once again utilized for this en-devour. It will be installed on an R510 as stated above. Then I will create an iSCSI target and present that to VMWare as a LUN. Once the LUN has been presented to VMWare, we can go to town building out the Virtual Machines. Fairly straight forward here.

Virtual Machines

As of the moment my virtual machines are…..lacking. I went from having numerous VMs to accomplish one or two tasks down to one physical host and only a couple VMs to do a lot of tasks. Some things on my list to virtualize:

Firewall – pfSense and CARP – this is something I have never tried. Never really had a reason to. I feel like in the spirit of homelab, I should attempt this. Currently I am running a single Untangle firewall on Hyper-V. I love Untangle (so far) but I do not believe there is a way to create a failover cluster. None the less, this could change at any time. I jump from UTM to UTM or Firewall to Firewall. Keeps things exciting you know?

Monitoring – Nagios, Observium (perhaps Grafana will make a debut at some point too)

Domain Controllers – Currently I am working on my Master’s in IT, so I have access to the Microsoft Imagine program, so I will more then likely be spinning up a couple DCs to work with.

File Server (either nextcloud or something)

Security related – AlienVault, Nessus, and a dedicated KALI VM. Perhaps even a couple other pentest VMs on a secure VLAN.

Patch Management – ManageEngine

Web Server – Centos 7/WordPress/MySQL

Home Automation and Security – HomeSeer

Media – Plex (and maybe iHome Media Server too)

Physical Machines

Additionally, aside from my 2 hosts and the R510 SAN, I do have several physical machines present in the lab. One of the biggest tasks will be to remove all of my VMs off my Hyper-V box and turn my Hyper-V box into a BlueIris/Nakivo backup box. I switched to BlueIris from Ubiquiti’s NVR recently, and although I am loving Blue Iris, I find it resource intensive. So I will be leaving it as a physical box. The way I figure it, I can remove all the other tasks off my SuperMicro Mini and then have room for Nakivo along side Blue Iris. That machine has plenty of oomph for those two tasks.

I have a custom built workstation that I can never figure out what to do with, so I ordered up a 2u case and will be racking that as well. This will server as my media ingest machine. By that I mean, when I buy my next lot of DVDs and Bluerays or borrow them, I will use this machine to ingest the media and flip it to my Plex server.

A secure homelab or network environment should have a jump box or jump point. For me, my Intel Skull Canyon NUC will become this. Just a versatile box that is always on. Something I can hit from the field. My NUC will also be tied to a TV or screen in my office so that I can monitor the systems in real time.

*Update*

Check out my latest Home Lab rebuild posts

Dell R610 Intel Xeon CPU Upgrades – to see my progress on the two new hosts!

Add VLANs and Assign Ports on Cisco 2960G Switch – to see some configurations on my WAN switch

Permanent link to this article: https://achubbard.com/2018/02/24/homelab-rebuild-network-hosts-freenas-dell-r510/