--- title: "Configuring Cisco Catalyst 1000 Series Switches for Livewire" slug: "configuring-cisco-catalyst-1000-series-switches-for-livewire" updated: 2026-01-06T15:14:20Z published: 2026-01-06T15:14:20Z canonical: "docs.telosalliance.com/configuring-cisco-catalyst-1000-series-switches-for-livewire" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring Cisco Catalyst 1000 Series Switches for Livewire ## Scope This document covers the configuration of the Cisco 1000 series of switches for use with a Livewire+ network. Testing and setup based on Cisco IOS Software, C1000 Software (C1000-UNIVERSALK9-M), Version 15.2(7)E4, RELEASE SOFTWARE. > [!CAUTION] > **UPDATE RECOMMENDATION -** There are some known issues around previous versions of Cisco software for these switches that cause some multicast flooding and connection issues. We recommend running version 15.2(7)E4 or higher. As of this writing, software can be downloaded from the Cisco site by clicking [here](https://software.cisco.com/download/home/286324112/type/280805680/release/15.2.7E4). [Click here for a full listing of models in this series (this will take you to the Cisco website)](https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-1000-series-switches/nb-06-cat1k-ser-switch-ds-cte-en.html?oid=otren019232#Switchmodelsandconfigurations). > [!CAUTION] > **Note:** This document applies **only** to the Cisco 1000 Series switches and **does not apply to the Cisco C1300 series**. The C1300 platform is programmed more like the **Cisco Business Series (CBS-350)** switches, and the commands and configuration methods described in this document are **not compatible** with the C1300. Applying these settings to a C1300 switch may result in unintended behavior. ## Introduction This document is **not intended to be a complete or step-by-step guide** for configuring your switch. It is provided as a **general reference** and assumes a working knowledge of switch configuration and networking concepts. If you are not comfortable connecting serial or console cables, assigning IP addresses, or working in a command-line interface, we recommend contacting your IT department or a qualified network administrator for assistance. For initial (first-time) configuration, you must connect to the switch using a **console cable and a serial connection** to complete the setup process. Once the initial configuration is complete, you may access the switch using a **Telnet session** or continue to use the **serial console**. Connect to this switch using a USB cable and a serial port driver from Cisco, or connect using a [standard Cisco "console" cable](https://www.amazon.com/s?k=cisco+serial+console+cable). ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/9c666e4a-ba07-4e5c-a6ca-10c958e5a488-image.png?sv=2026-02-06&spr=https&st=2026-11-03T20%3A55%3A43Z&se=2026-11-03T21%3A55%3A43Z&sr=c&sp=r&sig=bKCuUX9wi1gZwuMhFx8K%2BCmnxXks4LWuvwWkP9os5M4%3D) As of this writing, the Windows [USB driver](https://software.cisco.com/download/release.html?mdfid=282774230&softwareid=282855122&release=3.1) can be obtained from the Cisco website. Make sure you install the driver **before** connecting the switch to your USB ports. Installing the driver and connecting the cable will install a new COM port on your computer. Use the device manager for your operating system to determine what COM port has been installed. PuTTy is a free terminal program that can be used for configuration and can be downloaded [here](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html). ## Programming Once connected via the serial cable (default settings: 9600 baud), you will see messages on the screen as the switch boots. Seeing these messages confirms that your serial cable is working correctly. If prompted to enter any setup wizards, please answer ‘No.’ A couple of other notes that might be helpful: - Many commands can be abbreviated and just need to be unambiguous. For example, the `enable` command is often abbreviated as `en` and `configure terminal` is often abbreviated as `config t`. All commands can be abbreviated. - The TAB key completes a word and checks it for correctness. For example, if you type ‘en’ and then press TAB it will spell out the word ‘enable’. - The `#` (pound or hash sign) indicates you are in privileged mode. For example, if your prompt says `Switch>` and you try to type `config t`, you will receive an error because you are not in privileged mode. Typing the `enable` command will give you the `Switch#` prompt indicating the privileged mode. ### Set the passwords We suggest using a password of ‘Livewire’ or some other password that is easy to remember. ```plaintext Switch>enable Switch#configure terminal Switch(config)#username AAAA password Livewire Switch(config)#enable password Axia ``` ### Set the hostname We suggest setting the hostname of each switch to something descriptive. Suggestions might be AXIACORE01, or AXIAEDGE01, etc. In this example, we will use AXIA01. To change the hostname from the default of ‘Switch’, type the following from the prompt; ```plaintext Switch(config)#hostname AXIA01 AXIA01(config)# ``` ### Assigning an IP address to Vlan 1 By default, Livewire uses Vlan 1. It is possible to use other Vlans; however, support for that is outside of the scope of this document. Please contact your Cisco dealer, Cisco support, or your IT Group for assistance on using other Vlans. > [!WARNING] > By default, the IGMP Querier will be the lowest IP address switch in the subnet. For this reason, it is essential to set your **core** (central) switch with a lower IP than any other switch in the Livewire subnet. **Note that this includes any PowerStation, QOR, or xSwitch as well as other Cisco switches.** To set the IP address, type the following from the prompt (replace the IP address shown with one appropriate to your configuration): ```plaintext AXIA01>enable AXIA01#config terminal AXIA01(config)#interface vlan1 AXIA01(config-if)#ip address 192.168.2.2 255.255.255.0 AXIA01(config-if)#no shutdown AXIA01(config-if)#end ``` Let’s save our configuration: ```plaintext AXIA01#wr Building configuration... [OK] AXIA01# ``` ### Allow access from Telnet Again we suggest the use of a password that is easy to remember. In this case, “telnet123” is used as the password. ```plaintext AXIA01#configure terminal AXIA01(config)#line vty 0 15 AXIA01(config-line)#password telnet123 AXIA01(config-line)#login AXIA01(config-line)#exit ``` ### Configuring Global QoS ```plaintext AXIA01(config)#mls qos srr-queue output cos-map queue 1 threshold 1 6 7 AXIA01(config)#mls qos srr-queue output cos-map queue 2 threshold 1 5 AXIA01(config)#mls qos srr-queue output cos-map queue 3 threshold 1 0 1 AXIA01(config)#mls qos srr-queue output dscp-map queue 1 threshold 1 48 AXIA01(config)#mls qos srr-queue output dscp-map queue 2 threshold 1 46 34 AXIA01(config)#mls qos srr-queue output dscp-map queue 3 threshold 1 0 AXIA01(config)#mls qos AXIA01(config)#end AXIA01#wr Building configuration... [OK] AXIA01# ``` ### Setup IGMP ```plaintext AXIA01#config terminal AXIA01(config)#ip igmp snooping querier AXIA01(config)#ip igmp snooping vlan 1 immediate-leave AXIA01(config)#ip igmp snooping querier max-response-time 25 AXIA01(config)#ip igmp snooping querier timer expiry 205 AXIA01(config)#end ``` > [!WARNING] > It is recommended to set only one “ip igmp snooping querier” per VLAN and for proper operation the querier must be core switch. (core switch is defined as the “central” switch or the one that all other switches connect to). This is particularly important in cases where the total bandwidth on a Livewire network can exceed the capacity of any single link. To disable ip igmp querier on a Cisco switch use: ```plaintext AXIA01#config terminal AXIA01(config)#no ip igmp snooping querier AXIA01(config)#end ``` ### Configuring Axia Device Ports (Access Ports) Access ports are used for connecting “end point” devices like Axia nodes, engines, computers, as well as any other devices that are not considered “switches” (see note in trunk port configuration section). To configure multiple access ports at once, type the following from the prompt: > [!WARNING] > Replace GigabitEthernet1/0/1 - 22 with the ports that are appropriate to your configuration. In this example, we are configuring ports 1 thru 22 as access ports. ```plaintext AXIA01#config terminal AXIA01(config)#interface range GigabitEthernet1/0/1 - 22 AXIA01(config-if-range)#switchport mode access AXIA01(config-if-range)#switchport nonegotiate AXIA01(config-if-range)#switchport voice vlan dot1p AXIA01(config-if-range)#priority-queue out AXIA01(config-if-range)#no power efficient-ethernet auto AXIA01(config-if-range)#mls qos trust dscp *SEE NOTE BELOW* AXIA01(config-if-range)#spanning-tree portfast AXIA01(config-if-range)#no ip igmp snooping tcn flood AXIA01(config-if-range)#end ``` > [!CAUTION] > *NOTE* - for Engine, iPort, VX, or Omnia 8x versions older than 2011-06-15 use “mls qos trust cos” ### Configuring Trunk Ports Trunk ports are used for connecting other Cisco switches or Axia devices with switches built-in (like a PowerStation Main or QOR or xSwitch). Please note that when connecting to a PowerStation Main, only the GIG ports can be used, and they must be properly configured for Trunk operation in the Ethernet Switch configuration of the Element Control Center. QOR based devices and xSwitch should only be connected to the GIG Ports. To configure multiple trunk ports at once, type the following from the prompt: > [!WARNING] > Replace GigabitEthernet1/0/23 - 24 with the ports that are appropriate to your configuration. In this example we are configuring ports 23 and 24 for Trunk. ```plaintext AXIA01#config t AXIA01(config)#interface range GigabitEthernet1/0/23 - 24 AXIA01(config-if-range)#switchport mode trunk AXIA01(config-if-range)#switchport trunk allowed vlan 1 AXIA01(config-if-range)#priority-queue out AXIA01(config-if-range)#mls qos trust dscp AXIA01(config-if-range)#no ip igmp snooping tcn flood AXIA01(config-if-range)#no power efficient-ethernet auto AXIA01(config-if-range)#end ``` > [!CAUTION] > Note the inclusion of the Cisco EEE disabling command as we did in the Access ports. Again, an error when entering this command is possible and expected if not supported by the switch. ### Set Spanning-Tree settings It’s important for your core switch to be set up as the master for the Spanning Tree protocol. If this switch will be the core switch for your Axia network then set it as the Spanning Tree root. ```plaintext AXIA01#config t AXIA01(config)#spanning-tree vlan 1 root primary AXIA01(config)#end ``` ## Save and Check Your Work To save your work type the following; ```plaintext AXIA01#copy running-config startup-config ``` You will be prompted for a file name. Just press enter. ```plaintext Destination filename [startup-config]? Building configuration... [OK] AXIA01# ``` To check your work, from the command prompt, type; ```plaintext AXIA01#show run ``` Use the spacebar to proceed a page at a time and double check your configuration. ## Let us know how we can help If you have further questions on this topic or have ideas about improving this document please [contact us](https://www.telosalliance.com/support-request).