Network Switch Setup: How To Configure A Network Switch

A properly configured network switch is the backbone of any reliable AV system. Whether you’re setting up AV-over-IP endpoints, segmenting Dante audio traffic, or connecting Crestron control processors, knowing how to configure a network switch correctly determines whether your deployment runs cleanly or turns into a troubleshooting nightmare. Misconfigurations cause real downtime, and in commercial AV environments, downtime means missed meetings, failed presentations, and frustrated clients.

At MegaServices, our Mega Certified technicians configure and deploy network infrastructure on Pro AV projects across North America every day. That hands-on experience across thousands of installations since 2007 has taught us what works, what breaks, and what steps get skipped most often. We built this guide from that field knowledge, not from repackaged manufacturer docs.

Below, you’ll walk through the complete process: physical connections, console access, IP assignment, VLAN configuration, and security hardening. Each step reflects the same standard our technicians follow when they’re on site, so you can apply it to managed switches from Cisco, Netgear, HP, or any other major brand.

Before you touch the switch

Before you learn how to configure a network switch correctly, preparation separates a clean deployment from a costly rework. Every successful installation starts with a documented plan: an IP scheme, a VLAN layout, and a clear picture of which devices land on which ports. A power plan should be part of your port layout. There’s a lot of stuff that runs on Power over Ethernet and its SUPER important to know that your switch can support the load.  If you’ve got a 65W switch and two 65W cameras, you’re going to spend a lot of time wondering why something isn’t working.  Its small, but its important. Skipping this step is the single most common reason technicians spend hours troubleshooting issues that were entirely preventable from the start.

Build your network plan

You need three documents in hand before you power on the switch: a network diagram, an IP address scheme, and a VLAN plan. Your network diagram shows which devices connect to which switch ports. Your IP scheme defines the management IP for the switch itself, the gateway address, and the subnet mask. Your VLAN plan maps traffic types, such as AV-over-IP, control, and corporate data, to specific VLAN IDs and port assignments. Your power plan should account for wattage across all PoE devices and factor into your IP plan.

A missing VLAN plan is the leading cause of AV network configuration rework on commercial installations.

For AV deployments specifically, put your Dante or AV-over-IP traffic on a dedicated VLAN (commonly VLAN 10 or VLAN 20) to isolate latency-sensitive streams from general data traffic before you write a single line of config.

Confirm your tools and credentials

Three items belong on your bench before you open any interface: a console cable (typically USB-to-RJ45 or DB9 depending on the switch model), a laptop with a terminal emulator installed, and the factory default credentials for your specific switch. Cisco switches commonly ship with a blank username and the password “cisco.” HP ProCurve switches default to no username and no password.

Also verify that your terminal emulator matches the correct serial port settings: 9600 baud, 8 data bits, no parity, 1 stop bit, and no flow control. These values apply to nearly every major managed switch brand and will save you from a frustrating blank console screen on your first connection attempt.

Step 1. Unbox, rack, and connect

Physical setup seems simple, but small mistakes here create problems that surface later during configuration. Before you slide the switch into the rack, inspect the unit for shipping damage, confirm the model matches your network plan, and locate the console port on the front or rear panel.

Mount and power the switch

Rack-mount the switch using the included rack ears and secure it with cage nuts before powering on. Position the switch so the console port stays accessible while you work, since you need a direct connection in the next step. Once mounted, connect the power cable and confirm the status LED turns solid green.

Never move forward until the status LED confirms a clean power-on. A blinking or amber LED signals a hardware fault that configuration will not fix.

Cable the uplinks and access ports

Connect your uplink port (usually labeled “Uplink” or the highest-numbered port) to your core router or firewall first. Then run patch cables to your AV endpoints, control processors, and other devices according to your network diagram. Cable in this order to keep things organized:

1. Uplink to core router or firewall
2. AV-over-IP and Dante endpoints
3. Control processors and codecs
4. End-user devices and workstations

Label every cable at both ends before you finish, because unlabeled cables waste significant time during any future troubleshooting.

Step 2. Access the management interface

With your cables in place, your next task is getting into the switch before you touch any configuration. Console access gives you direct, out-of-band control over the switch regardless of IP settings, which makes it the only reliable method when the device has no management IP assigned yet. This is the foundation of learning how to configure a network switch without locking yourself out mid-setup.

Connect via console cable

Plug your USB-to-RJ45 console cable into the console port you identified during racking, then connect the other end to your laptop. Open your terminal emulator (PuTTY on Windows works well) and create a new Serial connection using these exact settings:

Speed (baud):    9600
Data bits:       8
Stop bits:       1
Parity:          None
Flow control:    None

Select the correct COM port for your cable, then click Open. Press Enter once to trigger the login prompt.

If your screen stays blank after pressing Enter, confirm you selected the right COM port in Device Manager before assuming a hardware fault.

Log in and confirm access

Enter the factory default credentials for your switch model. Once you see the command prompt (for example, Switch> on Cisco or HP-2920# on HP), type enable to enter privileged mode. Confirm you have full access by running show version, which returns the firmware version and confirms the session is live.

Step 3. Set management IP and SSH

Assigning a management IP and locking down remote access are the two configuration tasks that make every subsequent step faster and safer. Without a management IP, you’re stuck at the console for all future changes. Without SSH, you’re sending credentials across the network in plain text. Both settings are essential to how to configure a network switch for a production AV environment.

Assign the management IP

On most managed switches, the management IP lives on a dedicated VLAN interface, commonly VLAN 1. The following Cisco IOS commands apply that configuration:

Switch# configure terminal
Switch(config)# interface vlan 1
Switch(config-if)# ip address 192.168.1.10 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# exit
Switch(config)# ip default-gateway 192.168.1.1
Switch(config)# end
Switch# write memory

Replace 192.168.1.10 with the address from your IP scheme and 192.168.1.1 with your actual gateway. Run ping 192.168.1.1 from the switch to confirm connectivity before moving on.

Enable SSH and disable Telnet

SSH encrypts your management sessions; Telnet does not. Disable Telnet immediately and generate a local RSA key to activate SSH:

Switch(config)# crypto key generate rsa modulus 2048
Switch(config)# ip ssh version 2
Switch(config)# line vty 0 15
Switch(config-line)# transport input ssh
Switch(config-line)# login local

A 2048-bit RSA key meets current security baselines for managed switches in commercial installations.

Step 4. Configure VLANs, ports, and protections

VLANs and port security are where how to configure a network switch transitions from basic connectivity to a production-ready deployment. This step determines which traffic flows to which ports and prevents unauthorized devices from reaching your AV infrastructure. Rushing through it causes segmentation failures that are difficult to diagnose after the fact.

Create and assign VLANs

Start by creating each VLAN and giving it a descriptive name, then assign the correct ports. The Cisco IOS commands below create VLAN 10 for AV-over-IP traffic and apply it to port GigabitEthernet0/1 as an access port:

Switch(config)# vlan 10
Switch(config-vlan)# name AV_Traffic
Switch(config-vlan)# exit
Switch(config)# interface GigabitEthernet0/1
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 10
Switch(config-if)# exit

Ports connecting to a router or upstream switch need trunk mode with explicitly allowed VLANs to prevent unintended traffic from crossing VLAN boundaries.

Enable port security

Setting up port security restricts which devices can connect to each switch port by limiting the allowed MAC addresses per port. Apply it on every access port to block unauthorized endpoints before they reach your AV devices:

Switch(config-if)# switchport port-security
Switch(config-if)# switchport port-security maximum 1
Switch(config-if)# switchport port-security violation restrict

Restrict mode logs violations without shutting down the port, which keeps your AV system running while giving you the data you need to investigate.

You are ready to put it in production

You have now completed every critical step in how to configure a network switch for a live AV environment: physical installation, console access, management IP assignment, SSH hardening, VLAN segmentation, and port security. Each layer you added reduces the chance of a misconfig causing downtime during a real event or client presentation. Before you cut over to production, run show running-config one final time and verify that every setting matches your documented network plan. Save the config with write memory so a power cycle does not wipe your work.

From this point, your switch is a stable, segmented foundation that your AV endpoints, control systems, and Dante streams can rely on. Document your final IP scheme, VLAN assignments, and port map in a single reference file and store it with the project closeout package. That documentation protects you, your team, and your client the next time someone needs to troubleshoot or expand the system. If your next project needs a certified AV technician who handles network configuration at this level, book a MegaTech for your next Pro AV project.