Category: Networking

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/

Add a VLAN on a Dell PowerConnect 5524p Switch

Adding a VLAN on a Dell PowerConnect 5524 Switch

Having spent the last few years of my career in a Dell networking environment, I have decided that I will be adding a Dell switch to my personal collection. In this tutorial, I will show you how to add a VLAN via the CLI on a Dell PowerConnect 5524p switch. This tutorial assumes you know how to connect to the switch either by a using a console cable or SSH.

Connecting with Putty

Use Putty (or another similar tool) to either SSH or serial/console into your switch. This will get you into the CLI.

Configuring the switch

To begin, we need to enter the configuration mode. To do this, type “conf t” at the prompt and press enter. You will now be in config mode and see (config) to the left of the # sign.

Creating the V-LAN itself is a fairly easy task. Type the command “vlan database” and press the enter key.

Pick your V-LAN number and type “vlan #” and press the enter key. Where the # is, place your vlan number. So, in this tutorial we will use vlan 55.

Basic VLAN Configuration

In order to configure an IP address for our newly created VLAN, we must use the command “interface vlan 55”. This allows us to enter the interface configuration.

Give your V-LAN an IP Address if so desired, use the command “ip address x.x.x.x x.x.x.x” The first set of x’s represents the IP Address, the second set represents the subnet mask. So in my case, the command would be, “ip address 192.168.55.1 255.255.255.0”

Giving your V-LAN a name also helps distinguish what the V-LAN is for. Enter the command “name” followed by the name you have picked. So: name “test vlan”

Before you exit Putty, make sure you issue the command “copy run start” otherwise, if you reboot your switch, you will lose the configuration changes you just made.

 

Please feel free to check out the rest of my blog posts for other tutorials and information from the home lab!

Permanent link to this article: https://achubbard.com/2018/02/09/vlan-configuration-on-dell-powerconnect/

Installing Untangle on Hyper-V

Background

Over the years I have had numerous different types of firewalls and UTMs in my home lab. For a while, I ran an ASA, then migrated to pfSense and soon after that I went over the a Ubiquiti USG-Pro. Looking for my next challenge, I stumbled across Untangle. Although I had heard of Untangle before I had never used it. I figured I would give it a try. Untangle has a home use version available for $50 per year. I purchased a subscription. So far, it has been a fairly decent application. I have been extremely happy with it. For $50 you get Untangle and most of their premium plugins. I thought it was a great deal.

To download and/or purchase Untangle at Home Please click the link below

Untangle at Home

The consumer can download Untangle in a couple of difference forms. ISO 32/64bit, Firmware or as a Virtual Appliance. I thought, great, I can download Untangle, spin up a VM and be on my way. As it turns out, Untangle only provides their appliance as an OVA. This is only supported by VMWare. Here in lies my issue, I am running Hyper-V. I was determined to get it this working either way. Untangle will install on Hyper-V, they just do not provide the virtual appliance.

Determination

Getting Untangle to work on Hyper-V took me some time. I ran into numerous configuration issues along the way. Almost to the point where I gave up on the whole project. However, I was fairly determined to make it work. My background is in ESXi and not Hyper-V so that was where most of my learning curve came from. For me, the biggest hangup was configuring the virtual switch for the WAN. Whatever my issue was, I could not get it to function. Hopefully my blog/tutorial post will help someone get their Untangle instance setup on Hyper-V

Virtual Switch Configuration

Prior to creating a new virtual machine for your Untangle install, open up the Hyper-V Management Console and create 2 virtual switches. The Virtual Switch Manager will help you do this. One will be for the LAN connection, the other will be for the WAN connection. 

WAN Configuration

We will start with the “External” or the WAN switch first. On your physical host, this is where you will plug your ISP’s modem into.

Create your virtual switch. Give it a name that indicates it’s use, so in this case, mine is simply, “WAN”. From the drop down menu under the “External Network” radio button, select the physical adapter that you will use. Be sure to un-check “Allow management operating system to share this network adapter” – this will prevent your host from trying to use it.

 

LAN Configuration

Repeat the virtual switch creation process again, only this time, select the physical network adapter on your host that you will be connecting to your LAN. Select “External” for this switch too. Be sure to check off “Allow management operating system to share this adapter” – this will allow your host to share LAN access with this VM.

Virtual Machine Creation and Specs

Create a new virtual machine. If you need help creating a virtual machine, please see my post titled “CentOS 7 Minimal Installation on Hyper-V”or click on the link to take you there. The only difference with this virtual machine will be the specs. Here is what I have chosen for my install:

Memory: 6gb

Processor: 2 Virtual Processors

Hard Drive: 40gb

Network Adapters: 2 – 1 for LAN, 1 for WAN

Untangle Installation

Once your VM has booted, you will see the “Untangle Installer Boot Menu” – I used the graphical install option

Select your language

Pick your location

Choose your keyboard type

Untangle will show you a system summary before beginning it’s installation process

To continue with the installation, select “yes” to format your VHD.

Write the changes to disk

Untangle will continue it’s base install. This process takes a little while, you may want to go make yourself a coffee and come back.

Untangle has now completed it’s long installation, click on continue and the VM will reboot.

Finalization

With Untangle on Hyper-V I have found that it sometimes has the tendency to appear to be hung up on this spot. Don’t worry though, let it sit and it will come right up. It is not stuck.

When the VM boots up and launches the OS, you will be prompted to go through the initial setup phase. This is fairly straight forward. At this point, you have now installed Untangle on Hyper-V.

I hope this tutorial helps you understand how to get Untangle installed on Hyper-V. It is a fairly straight forward process. Although I ran into some issues initially because I had never done it before.

Permanent link to this article: https://achubbard.com/2018/02/01/installing-untangle-hyper-v/

Unifi and NanoStation VLAN Configuration

Unifi and NanoStation VLAN Configuration

Background

This is a tutorial on how to configure a VLAN on a Ubiquiti Unifi Controller and switch. We will also go over how to use the second ethernet port on a Ubiquti NanoStation on a different VLAN for use with a Ubiquiti Security Camera.

I have a rather long driveway, our upper half of the driveway is where my office and house are located. The lower half houses an area for our growing animal population and parking. I have multiple VLANs, 1 of which is for my security cameras. I wanted the 2nd port on the Ubiquiti NanoStation placed on the lower portion of the driveway to be able to utilize my camera VLAN.

This tutorial will assume that all of the hardware is in place and you are ready to make the secondary ethernet port on the NanoStation work on another VLAN.

In my case, I have a Unifi Controller that will need to be configured with my security VLAN, VLAN35, prior to configuring my NanoStations.

Unfi Configuration

Enter the Unifi controller and navigate to Settings >Networks. 

Click on the “Create New Network” button. Select “VLAN Only” from the “Purpose” section. Give your VLAN a name and a number. I chose 35.

You can then configure any other settings for your new VLAN that you may need. In my case, I only needed the basics. No DHCP on my security VLAN. You can then click on the “Save” button.

Once saved, in the Unifi controller, navigate to “Devices”

Select your switch and it will open the device’s configurations on the right hand side of the page. Select your port from the list and click “Edit”

On my “Core” (I use quotations because it is not really a core switch, but it is my main switch) I picked port 2 to use for my NanoStation uplink.

You want to make sure the “Switch Port Profile” is set to “All” – The reason is that this port is going to act as a trunk port and provide all of the VLANs to your first NanoStation. You want this if you wish to pass all of your VLANs over the bridge. Click “Apply”

NanoStation Station 1 Configuration

Next, login to the web interface of your NanoStation that will be acting as the “Station” – Navigate to the “Wireless” tab. Here you want to configure your wireless bridge settings (IE: your SSID, WPA2 Key, Channel Width etc) – I will leave that up to you to determine what works for your application. Since this NanoStation is acting as the “Station” you want to make sure the “Wireless Mode” is set to “Station”

Below is what I chose for my settings:

Once the wireless portion of your first station is configured, go to the “Network” tab. Here you can configure your station with a static IP etc. For the purposes of this tutorial, we will assume you have already given your station a static IP address, gateway, mask, DNS and so forth. You will want to make sure that the “Network Mode” is set to “Bridge” and that the “Configuration Mode” is set to “Simple”

NanoStation Station 2 Configuration

After completing the setup of your first NanoStation, login to the web interface of the second NanoStation. First go to the “Wireless” tab on your second NanoStation. This time you will want “Wireless Mode” to be set as “Access Point” – You will then match the rest of the settings to the settings you configured on the “Wireless” tab on your first NanoStation.

Once you have selected your settings, navigate to the “Network” tab on your second NanoStation. This is where things get to be a little be more complex. Since the wireless bridge itself is passing all of the VLANs across it, we need to tell the NanoStation what VLAN to use for the 2nd onboard ethernet port. This is the port we will be daisy chaining our camera off of.

VLAN and Bridge Configuration

On station number 2, your “Network Mode” will also be set to “Bridge”, you will have the option to set a static IP, mask, gateway and so forth. The real difference here is that the “Configuration Mode” MUST be set to “Advanced” this will open up a slew of different options for you.

When “Advanced” is selected, you will now see a bunch of options at the bottom of the page. For this example, the LAN0 port is feeding a switch, the LAN1 port is what the camera will be daisy chained off of and WLAN0 is the wireless bridge between the two NanoStations.

Under the VLAN Network section, we first must add VLAN35 to each interface. This will allow the NanoStation to pass VLAN 35 over the wireless bridge and the 2 ethernet ports.

After adding the VLAN to the interfaces, come on down to the “Bridge Network” section. If memory serves me correctly, you must break the existing bridge to configure a new bridge.

BRIDGE0 is allowing LAN0 and WLAN0 to communicate thus passing management traffic to the switch connected to that ethernet port.

BRIDGE1 is allowing LAN1 and WLAN0.35 to communicate thus allowing camera traffic to pass from LAN1 to the wireless bridge, and back to the NVR.

After configuring the bridges, you must go up to the “Management Network Settings” section. Select “Management Interface”, in my case, it is “BRIDGE0” or my “management” VLAN.

The final step before you can plug the camera in, is to enable POE Passthrough. This allows the NanoStation to power the camera via POE on the secondary LAN port. On your second NanoStation, navigate to the “Advanced” tab. Scroll down until you find “Advanced Ethernet Settings”. Check the checkbox labeled “POE Passthrough enabled”. Click the change button and you should now be able to power up your camera on a separate VLAN.

 

Hope this helps someone, I spent a lot of time trying to get this to work on my property.

Permanent link to this article: https://achubbard.com/2018/01/30/ubiquiti-unifi-vlan-configuration-and-nanostation-ethernet-port-vlan-configuration/

Dell PowerConnect 5524P Firmware Upgrade

Dell PowerConnect 5524P Firmware Upgrade

Background

Upgrading the firmware on a Dell PowerConnect 5524p switch is a fairly simple task. For this tutorial, we are going to assume that you already have console and web access to the switch.

 

You can download the 5524’s firmware from Dell’s webpage located here: Dell Support

Steps to take

Login to the switch’s web interface.

Navigate to System > File Management > File Download.

In the “Download Protocol” section of the page, select “Download via HTTP” – This is where it is a little confusing because you are actually uploading the firmware to the switch.

Software Image Upload

Within the “Firmware Download” section, you should now see a “Browse” button. You can click this and navigate to the location you have stored your Dell firmware. There are two files to this procedure. The first one is the “Software Image” or the .ros file. Select the .ros file, hit the “Open” button on the dialogue box, then click “Activate” on the browser window.

Once the .ros file has completed it’s upload, you will see the following screen:

Click close and refresh the page. *NOTE* If you try and upload the second file without refreshing the page first, you may see a error stating “Invalid Image” or “Invalid File Type” – I ran into this on 2 separate 5524p switches that I have updated recently.

After refreshing the page, re-navigate to System > File Management > File Download. Re-select “Download via HTTP”

Boot Code Upload

In the “Firmware Download” section, click the drop down for “Destination File Type” and change it to “Boot Code” – This is the .rfb file we will be uploading. Then click on the browse button, navigate to where you have stored your Dell firmware files and select the .rfb file. Click “Open” on the dialogue box, then click “Activate” on the browser window.

You will see a box that says “Copy Finished” – Click Close

Navigate to System > File Management > Active Images. Here we will select which image to use after a reboot. This will display the current image being used by the system. Under the “After Reset” drop down, select the image which you just uploaded. Click on the “Apply” button.

Once you click “Apply” a green box will appear that says “Success” 

If you are in the console of the switch that you can issue the “Reload” command to reboot the switch.

Upon reboot, you can issue the command “show version” and see that the switch is using the new firmware version.

I hope this helped you out, thank you for reading my first blog post! Check out my links page for some awesome resources

Permanent link to this article: https://achubbard.com/2018/01/29/dell-powerconnect-5524p-firmware-upgrade/