Cisco Catalyst 3850 Quick reference guide

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 36
Cisco Catalyst 3850 Switch
Deployment Guide
Deployment Guide

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 2 of 36
Contents
Preface......................................................................................................................................................................3
Purpose ................................................................................................................................................................3
Audience...............................................................................................................................................................3
Conventions..........................................................................................................................................................3
Introduction.............................................................................................................................................................. 3
Initializing the Cisco Catalyst 3850 Switch............................................................................................................ 3
Console Setup ......................................................................................................................................................4
Using the USB Console Port............................................................................................................................4
Using the RJ45 Port.........................................................................................................................................4
Cisco IOS XE Software Bundle and Packages Overview ..................................................................................... 4
Booting Cisco IOS XE Software............................................................................................................................6
Booting the Switch in Install Mode....................................................................................................................6
Booting the Cisco Catalyst 3850 Switch in Bundle Mode................................................................................. 7
Updating Cisco IOS XE Software.......................................................................................................................... 7
Software Rollback.................................................................................................................................................9
Software Clean .....................................................................................................................................................9
Migration to Install Mode from the Bootloader Prompt........................................................................................12
Cisco Catalyst 3850 Switch Right-to-Use Licensing Model ...............................................................................15
RTU License Types ............................................................................................................................................15
Permanent RTU License................................................................................................................................15
Image-Based License in a Stack.................................................................................................................... 17
AP-Count License in a Stack.......................................................................................................................... 19
License Migration between Switches .............................................................................................................21
Evaluation RTU License................................................................................................................................. 23
License Usage Monitoring...................................................................................................................................25
License Storage Management............................................................................................................................26
Cisco Catalyst 3850 Switch Stacking................................................................................................................... 26
Overview.............................................................................................................................................................26
Plug-and-Play Stack Deployment .......................................................................................................................28
Deploying Cisco Catalyst 3850 Switch StackWise-480 NSF and SSO...............................................................31
Cisco Catalyst 3850 Switch Database Manager Template ................................................................................. 32
SDM Template Resources: VLAN and Advanced...............................................................................................32
SDM Template Configuration..............................................................................................................................33
Monitoring SDM Resources................................................................................................................................35
Appendix A: List of Bootloader Commands........................................................................................................ 36

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 3 of 36
Preface
Purpose
The purpose of this guide is to explain the basic concepts and provide general procedures and commands to
deploy Cisco®Catalyst®3850 Switches. It does not provide detailed information about these commands.
Audience
This guide is for networking professionals who are responsible for designing, implementing, or administering a
network that includes a standalone Cisco Catalyst 3850 Switch or a Cisco Catalyst 3850 Switch stack, referred to
as the switch. Readers of this guide are expected to have prior experience working with the Cisco IOS®Software
and familiarity with the concepts and terminology of local area networking, wireless local area networking, and
Layer 2 and Layer 3 switching.
Conventions
This publication uses these conventions to convey instructions and information:
●Command names are in boldface text.
●System displays are in screen font.
Introduction
The next-generation Cisco Catalyst 3850 Switch meets the current and future demands of enterprise access-layer
networks. As these networks incorporate ever more technologies, they must be secure, scalable, and resilient. The
Cisco Catalyst 3850 Switch offers operational simplicity, scalability, and superb performance. The new Cisco
StackWise-480 stack architecture delivers the industry’s best-in-class stack bandwidth and resiliency.
The Cisco Catalyst 3850 Switch supports the powerful next-generation Cisco IOS XE Software. The modular Cisco
IOS XE Software architecture enables rich, scalable, and cost-effective integrated borderless networking services.
The Cisco Catalyst 3850 Switch is the first stackable access-layer switch that provides both wired and wireless
services on a single Cisco IOS XE Software-based platform.
This guide describes the procedures required to deploy a Cisco Catalyst 3850 Switch:
1. Initializing the Cisco Catalyst 3850 Switch
2. Cisco Catalyst 3850 Switch right-to-use (RTU) licensing model
3. Cisco Catalyst 3850 Switch stacking
4. Cisco Catalyst 3850 Switch Database Manager (SDM) template
Initializing the Cisco Catalyst 3850 Switch
●Console setup
●Cisco IOS XE Software bundle and packages overview
●Booting Cisco IOS XE Software
●Updating Cisco IOS XE Software
●Software rollback
●Software clean
●Boot loader upgrade
●Migration to installed mode

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 4 of 36
Console Setup
The Cisco Catalyst 3850 Switch (similar to the Cisco Catalyst 3750-X Switch) has two console ports: a USB mini
console port in the front and an RJ45 console port in the rear. You can use either port (but not both) for input.
However, both ports always display the switch output.
The default console port speed setting is 9600 baud, 8 data bits, no parity, 1 stop bit, and no flow control.
Using the USB Console Port
Figure 1. USB Console Port
The USB console port is the default management port and is supported in both install and boot loader modes.
Before using the USB port, download the required driver to your PC from Cisco.com:
http://software.cisco.com/download/release.html?mdfid=282979369&softwareid=282855122&release=3.1.
The USB console port has a configurable inactivity timer that automatically disables the port after a specified period
from 1 to 240 minutes. Use this command to configure the inactivity timeout interval:
Switch(config)# line console 0
Switch(config-line)# usb-inactivity-timeout switch 1 ?
<1-240> Inactivty minutes before console reverts to RJ45
Using the RJ45 Port
Figure 2. RJ45 Console Port
To use the RJ45 port, you must configure precedence for it by using these commands:
Switch(config)# line console 0
Switch(config-line)# media-type rj45 switch 1
Configuring precedence for the RJ45 port enables it for input and disables input on the USB console port.
However, switch output is always displayed on both ports.
Cisco IOS XE Software Bundle and Packages Overview
The Cisco Catalyst 3850 Switch uses Cisco IOS XE Software. Cisco IOS XE Software is delivered as a bundle that
contains a set of packages. The Cisco IOS XE Software bundle uses this image name convention:
<platform_name>_<bundle_feature_set>.<key_ver>.<IOS-XE_version>.<IOS_image_version> .bin
Example: cat3k_caa-universalk9.SPA.03.07.00.E.152-3.E.bin

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 5 of 36
Explanation of bundle naming convention:
Image Name Element
Explanation
Example
platform_name
The name of the platform supported by the Cisco IOS XE Software bundle; caa represents
converged access architecture
cat3k_caa
bundle_feature set
The feature set provided by the Cisco IOS XE Software bundle
universalk9
key_ver
A three-character string indicating that the Cisco IOS XE Software bundle (or the packages it
contains, or both) is digitally signed
SPA
IOS_XE_version
The bundle’s Cisco IOS XE Software release number
3.7.0SE
IOS_image_version
The Cisco IOS Software image version of the Cisco IOS Software package contained in the
bundle
15.2(3)E
The Cisco IOS XE Software bundle contains a set of packages and a provisioning file, called packages.conf, that
is created automatically during the install process.
The show version running EXEC command displays the current running package(s) version:
Switch# show version running
Package: Base, version: 03.07.00E, status: active
File: cat3k_caa-base.SPA.03.07.00E.pkg, on: Switch1
Built: Mon Dec 08 00:30:04 PST 2014, by: gereddy
Package: Drivers, version: 03.07.00E, status: active
File: cat3k_caa-drivers.SPA.03.07.00E.pkg, on: Switch1
Built: Mon Dec 08 00:34:53 PST 2014, by: gereddy
Package: Infra, version: 03.07.00E, status: active
File: cat3k_caa-infra.SPA.03.07.00E.pkg, on: Switch1
Built: Mon Dec 08 00:31:51 PST 2014, by: gereddy
Package: IOS, version: 152-3.E, status: active
File: cat3k_caa-iosd-universalk9.SPA.152-3.E.pkg, on: Switch1
Built: Mon Dec 08 00:33:09 PST 2014, by: gereddy
Package: Platform, version: 03.07.00E, status: active
File: cat3k_caa-platform.SPA.03.07.00E.pkg, on: Switch1
Built: Mon Dec 08 00:32:37 PST 2014, by: gereddy
Package: WCM, version: 10.3.100.0, status: active
File: cat3k_caa-wcm.SPA.10.3.100.0.pkg, on: Switch1
Built: Mon Dec 08 00:34:17 PST 2014, by: gereddy

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 6 of 36
The Cisco IOS XE Software bundle includes these packages:
Package Name
File Name
Contents
Base
cat3k_caa-base.SPA.03.07.00E.pkg
Kernel distribution
Drivers
cat3k_caa-drivers.SPA.03.07.00.E.pkg
Platform drivers
Infra
cat3k_caa-infra.SPA.03.07.00E.pkg
Infrastructure software, including system manager, installer, HA
manager, and more
Cisco IOS Software
cat3k_caa-iosd-universalk9.SPA.152-3.E.pkg
Cisco IOS Software image
Platform
cat3k_caa-platform.SPA.03.07.00.E.pkg
Software not specific to the Cisco IOS Software platform and stack
manager, platform manager, and more
WCM
cat3k_caa-wcm.SPA.10.3.100.0.pkg
Wireless controller software
Booting Cisco IOS XE Software
You can boot and run the Cisco IOS XE Software on the Cisco Catalyst 3850 Switch in either of two modes:
●Install mode (recommended mode of operation)
●Bundle mode
Booting the Switch in Install Mode
Cisco Catalyst 3850 Switches shipped to customers from manufacturing boot up in install mode. The Cisco
Catalyst 3850 Switch is booted in install mode using a package provisioning file packages.conf. Do not modify this
file.
In this example, the Cisco Catalyst 3850 Switch is configured to autoboot from the built-in flash memory:
Switch# show boot
---------------------------
Switch 1
---------------------------
Current Boot Variables:
BOOT variable does not exist
Boot Variables on next reload:
BOOT variable = flash:packages.conf
Allow Dev Key = yes
Manual Boot = no
Enable Break = no
The show version command output displays the Cisco Catalyst 3850 Switch mode of operation:
Switch# show version | begin Switch Ports
Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 32 WS-C3850-24U 03.07.00.E cat3k_caa-universalk9 INSTALL
Configuration register is 0x102
The packages and the provisioning file reside in the flash.

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 7 of 36
Note: Booting in install mode from a USB flash drive or using Trivial File Transfer Protocol (TFTP) is not
supported.
Booting the Cisco Catalyst 3850 Switch in Bundle Mode
Booting a Cisco Catalyst 3850 Switch in bundle mode is just like booting a monolithic Cisco IOS Software image on
a Cisco Catalyst 3750-X Switch.
This command boots the switch in bundle mode:
switch: boot flash:cat3k_caa-universalk9.SPA.03.07.00.E.152-3.E.bin
Reading full image into
memory...........................................................................
.................................................................................
.................................................................................
..............................................................done
Bundle Image
<Output Truncated>
Note: Booting the switch in bundle mode consumes more memory than booting in install mode because the
packages are extracted from the bundle and copied to the RAM.
You can boot the switch in bundle mode from the built-in flash memory, an external USB drive (usbflash0), or
TFTP. Bundle mode is used to boot a Cisco Catalyst 3850 Switch from the boot loader prompt.
Updating Cisco IOS XE Software
When the switch is in install mode, you can install any new Cisco IOS XE Software bundle by using the software
install command.
Note: This command works only when the Cisco Catalyst 3850 Switch is booted in install mode.
Use the show switch command to check the status of the switch or switch stack. This example shows the status
of a two-switch stack, where switch 1 is active:
Switch# show switch
Switch/Stack Mac Address : 00e1.6d52.c600 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
-------------------------------------------------------------
*1 Active 00e1.6d52.c600 15 V03 Ready
2 Standby 44ad.d96d.b480 1 V01 Ready

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 8 of 36
This example shows the command syntax and the console log from a software install in a stack of two switches:
Switch# software install file flash: cat3k_caa-universalk9.SPA.03.07.00.E.152-
3.E.bin
Preparing install operation ...
[2]: Copying software from active switch 1 to switch 2
[2]: Finishing copying software to switch 2
[1 2]: Starting install operation
[1 2]: Expanding bundle flash: cat3k_caa-universalk9.SPA.03.07.00.E.152-3.E.bin
[1 2]: Copying package files
[1 2]: Package files copied
[1 2]: Finished expanding bundle flash: cat3k_caa-universalk9.SPA.03.07.00.E.152-
3.E.bin
[1 2]: Verifying and copying expanded package files to flash:
[1 2]: Verified and copied expanded package files to flash:
[1 2]: Starting compatibility checks
[1 2]: Finished compatibility checks
[1 2]: Starting application pre-installation processing
[1 2]: Finished application pre-installation processing
[1]: Old files list:
Removed cat3k_caa-base.SPA.03.03.03SE.pkg
Removed cat3k_caa-drivers.SPA.03.03.03SE.pkg
Removed cat3k_caa-infra.SPA.03.03.03SE.pkg
Removed cat3k_caa-iosd-universalk9.SPA.150-1.EZ3.pkg
Removed cat3k_caa-platform.SPA.03.03.03SE.pkg
Removed cat3k_caa-wcm.SPA.10.1.130.0.pkg
[2]: Old files list:
Removed cat3k_caa-base.SPA.03.03.03SE.pkg
Removed cat3k_caa-drivers.SPA.03.03.03SE.pkg
Removed cat3k_caa-infra.SPA.03.03.03SE.pkg
Removed cat3k_caa-iosd-universalk9.SPA.150-1.EZ3.pkg
Removed cat3k_caa-platform.SPA.03.03.03SE.pkg
Removed cat3k_caa-wcm.SPA.10.1.130.0.pkg
[1]: New files list:
Added cat3k_caa-base.SPA.03.07.00E.pkg
Added cat3k_caa-drivers.SPA.03.07.00E.pkg
Added cat3k_caa-infra.SPA.03.07.00E.pkg
Added cat3k_caa-iosd-universalk9.SPA.152-3.E.pkg
Added cat3k_caa-platform.SPA.03.07.00E.pkg
Added cat3k_caa-wcm.SPA.10.3.100.0.pkg
[2]: New files list:
Added cat3k_caa-base.SPA.03.07.00E.pkg
Added cat3k_caa-drivers.SPA.03.07.00E.pkg
Added cat3k_caa-infra.SPA.03.07.00E.pkg
Added cat3k_caa-iosd-universalk9.SPA.152-3.E.pkg

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 9 of 36
Added cat3k_caa-platform.SPA.03.07.00E.pkg
Added cat3k_caa-wcm.SPA.10.3.100.0.pkg
[1 2]: Creating pending provisioning file
[1 2]: Finished installing software. New software will load on reboot.
[1 2]: Committing provisioning file
[1 2]: Do you want to proceed with reload? [yes/no]: yes
[1 2]: Reloading
Software Rollback
The software rollback command allows you to revert to an earlier Cisco IOS XE Software package after a
software install. Software rollback is functional only when at least one rollback package with the file name
packages.conf.00- is present. The rollback file is created automatically during the Cisco Catalyst 3850 Switch
Cisco IOS XE Software image update process.
This example shows the flash directory of a switch with an available rollback package:
Switch# dir flash:
Directory of flash:/
38738 -rw- 856 Apr 14 2015 21:06:25 +00:00 vlan.dat
12 -rw- 1248 Jul 7 2014 07:07:46 +00:00 packages.conf.00-
<Output Truncated>
To revert to an earlier software image, use the software rollback command with the rollback package name:
Switch# software rollback provisioning-file flash:packages.conf.00-
Software Clean
Flash space in a Cisco Catalyst 3850 Switch can be recovered safely by using the software clean command. This
command deletes any redundant package files (.pkg), bundle files (.bin), or provisioning files (packages.conf*),
without deleting the active .pkg and .conf file.
Do not use the delete command to remove unnecessary files from flash, because you might also delete the active
.pkg or .conf files that are required for booting the switch.
Note: After you use the software clean command, the switch cannot revert to an earlier software image,
because the required rollback files are deleted by this operation.
This example shows the results of the software clean command on a stack of two Cisco Catalyst 3850 Switches:
Switch# software clean
Preparing clean operation ...
[1 2]: Cleaning up unnecessary package files
[1 2]: No path specified, will use booted path flash:packages.conf
[1 2]: Cleaning flash:
[1]: Preparing packages list to delete ...
In use files, will not delete:
cat3k_caa-base.SPA.03.07.00E.pkg
cat3k_caa-drivers.SPA.03.07.00E.pkg

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 10 of 36
cat3k_caa-infra.SPA.03.07.00E.pkg
cat3k_caa-iosd-universalk9.SPA.152-3.E.pkg
cat3k_caa-platform.SPA.03.07.00E.pkg
cat3k_caa-wcm.SPA.10.3.100.0.pkg
packages.conf
[2]: Preparing packages list to delete ...
In use files, will not delete:
cat3k_caa-base.SPA.03.07.00E.pkg
cat3k_caa-drivers.SPA.03.07.00E.pkg
cat3k_caa-infra.SPA.03.07.00E.pkg
cat3k_caa-iosd-universalk9.SPA.152-3.E.pkg
cat3k_caa-platform.SPA.03.07.00E.pkg
cat3k_caa-wcm.SPA.10.3.100.0.pkg
packages.conf
[1]: Files that will be deleted:
cat3k_caa-base.SPA.03.03.03SE.pkg
cat3k_caa-drivers.SPA.03.03.03SE.pkg
cat3k_caa-infra.SPA.03.03.03SE.pkg
cat3k_caa-iosd-universalk9.SPA.150-1.EZ3.pkg
cat3k_caa-platform.SPA.03.03.03SE.pkg
cat3k_caa-universalk9.SPA.03.07.00.E.152-3.E.bin
cat3k_caa-wcm.SPA.10.1.130.0.pkg
packages.conf.00-
[2]: Files that will be deleted:
cat3k_caa-base.SPA.03.03.03SE.pkg
cat3k_caa-drivers.SPA.03.03.03SE.pkg
cat3k_caa-infra.SPA.03.03.03SE.pkg
cat3k_caa-iosd-universalk9.SPA.150-1.EZ3.pkg
cat3k_caa-platform.SPA.03.03.03SE.pkg
cat3k_caa-universalk9.SPA.03.07.00.E.152-3.E.bin
cat3k_caa-wcm.SPA.10.1.130.0.pkg
packages.conf.00-
[1 2]: Do you want to proceed with the deletion? [yes/no]: y
[1 2]: Clean up completed
Boot Loader Upgrade
The Cisco Catalyst 3850 Switch shipped from manufacturing is configured to autoboot Cisco IOS XE Software from
the built-in flash and display the autoconfiguration dialog. In special circumstances a boot loader upgrade might be
necessary for a Cisco IOS XE Software image upgrade.
These are the steps to upgrade a Cisco Catalyst 3850 Switch boot loader image:
Step 1. Enable manual boot and power cycle the switch.

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 11 of 36
Enter the boot manual command, along with the switch name or number:
Switch(config)# boot manual switch 1
Switch(config)#^Z
Switch#wr mem
*Mar 17 22:34:15.142: %SYS-5-CONFIG_I: Configured from console by console
Building configuration...
Compressed configuration from 8910 bytes to 3178 bytes[OK]
Switch# reload
This is a sample of the switch display following a manual boot:
Booting...Initializing RAM +++++++@@@@@@@@...++++++++++++++++++++++++++++++++
Base ethernet MAC Address: f8:4f:57:6f:e1:00
Interface GE 0 link down***ERROR: PHY link is down
Initializing Flash...
flashfs[7]: 0 files, 1 directories
flashfs[7]: 0 orphaned files, 0 orphaned directories
flashfs[7]: Total bytes: 6784000
flashfs[7]: Bytes used: 1024
flashfs[7]: Bytes available: 6782976
flashfs[7]: flashfs fsck took 1 seconds....done Initializing Flash.
The system is not configured to boot automatically. The
following command will finish loading the operating system
software:
boot
switch:
There is a limited set of commands that are supported at the boot loader command prompt. Enter a question mark
to view the available commands.
Note: Appendix A of this guide shows the complete list of boot loader commands.
Use the version boot loader command to display the current boot loader version:
switch: ver
CAT3K_CAA Boot Loader (CAT3K_CAA-HBOOT-M) Version 1.3, RELEASE SOFTWARE (P)
Compiled Thu Jun 6 08:04:54 PDT 2013 by rel

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 12 of 36
Step 2. Load the new boot loader image from a TFTP server.
This example shows how to establish TFTP connectivity to the switch from the boot loader prompt:
switch: IP_ADDR=10.1.104.130/255.255.255.0
switch: DEFAULT_ROUTER=10.1.104.1
switch: MANUAL_BOOT=yes
switch: ping 10.1.104.211
ping 10.1.104.211 with 32 bytes of data …
Up 1000 Mbps Full duplex (port 0) (SGMII)
Host 10.1.104.211 is alive.
This example shows how to copy the boot loader image from TFTP:
switch: copy tftp://10.1.104.211/cat3850_loader.img.12Sep12.SSA bs:
Up 1000 Mbps Full duplex (port 0) (SGMII)
………………………………………………………………………………………………………………………………………………………………………………………………………………………
……………………………………………………………………………………….…………………………………………………………………………………………………………
File “tftp://10.1.104.211/cat3850_loader.img.12Sep12.SSA” successfully copied
to”bs:”
Note: You can also copy the boot loader image from a USB flash drive.
Step 3. Reset the switch.
The reset command reloads the switch, and it starts up with the new boot loader image:
switch: reset
To install the Cisco IOS XE Software, migrate from the boot loader prompt to the install mode.
Migration to Install Mode from the Bootloader Prompt
The Cisco IOS XE Software image for the Cisco Catalyst 3850 Switch is distributed as a bundle image. You cannot
copy this bundle directly to the flash and then boot the switch. You must install the Cisco IOS XE Software bundle
into the flash and then boot the switch from the installed software using the install mode. Perform this procedure if
the Cisco IOS XE Software image that resides in the flash memory becomes corrupted.
Use the ping command to confirm TFTP connectivity from the boot loader prompt:
switch: ping 10.1.104.211
ping 10.1.104.211 with 32 bytes of data …
Up 1000 Mbps Full duplex (port 0) (SGMII)
Host 10.1.104.211 is alive.
Boot the switch from TFTP:
switch: boot tftp://10.1.104.211/switch/cat3k_caa-universalk9.SPA.03.07.00.E.152-
3.E.bin
Reading full image into memory….
<Output Truncated>

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 13 of 36
Use the show version command to display the software image version and the mode:
Switch#show version | begin Switch Ports
Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 32 WS-C3850-24U 03.07.00.E cat3k_caa-universalk9 BUNDLE
The display shows bundle mode because the switch booted by loading the bundle either from TFTP or from a USB
flash drive.
Copy the final bundle image to the flash either from the TFTP server or from a USB flash drive.
Use the software expand command to expand the bundle image in the flash:
Switch#$software expand file flash:cat3k_caa-universalk9.SPA.03.07.00.E.152-
3.E.bin
Preparing expand operation ...
[1]: Expanding bundle flash:cat3k_caa-universalk9.SPA.03.07.00.E.152-3.E.bin
[1]: Copying package files
[1]: A different version of provisioning file packages.conf already exists in
flash:.
The provisioning file from the expanded bundle will be saved as
flash:cat3k_caa-universalk9.SPA.03.07.00.E.152-3.E.conf
[1]: Package files copied
[1]: Finished expanding bundle flash:cat3k_caa-universalk9.SPA.03.07.00.E.152-
3.E.bin
Confirm that the bundle is expanded and packages.conf file is present in the flash memory:
Switch# dir flash:
Directory of flash:/
7753 -rw- 1242 Mar 17 2013 22:29:11 +00:00 packages.conf
7746 -rw- 796 Mar 12 2015 00:07:01 +00:00 vlan.dat
38727 -rw- 82245716 Mar 17 2015 22:28:39 +00:00 cat3k_caa-
base.SPA.03.07.00E.pkg
38728 -rw- 7019196 Mar 17 2015 22:28:51 +00:00 cat3k_caa-
drivers.SPA.03.07.00E.pkg
38729 -rw- 36901896 Mar 17 2015 22:28:41 +00:00 cat3k_caa-
infra.SPA.03.07.00E.pkg
38730 -rw- 45841724 Mar 17 2015 22:28:45 +00:00 cat3k_caa-iosd-
universalk9.SPA.152-3.E.pkg
38731 -rw- 26858380 Mar 17 2015 22:28:42 +00:00 cat3k_caa-
platform.SPA.03.07.00E.pkg
38726 -rw- 1234 Mar 17 2015 22:29:08 +00:00 cat3k_caa-
universalk9.SPA.03.07.00.E.152-3.E.conf
38732 -rw- 111475520 Mar 17 2015 22:28:51 +00:00 cat3k_caa-
wcm.SPA.10.3.100.0.pkg
<Output Truncated>

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 14 of 36
1621966848 bytes total (719454208 bytes free)
Switch#
Reload the switch and boot with the newly created flash:packages.conf:
switch: boot flash:packages.conf
Getting rest of image
Reading full image into memory....done
Reading full base package into memory...: done = 79331128
<Output Truncated>
Switch#show version | begin Switch Ports
Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 32 WS-C3850-24U 03.07.00.E cat3k_caa-universalk9 INSTALL
Configuration register is 0x102
By default, when the software expand command is executed in the active switch of a switch stack, it is executed
on all switches in the stack.
To autoload the installed image, perform these steps:
Use the no boot manual command to disable manual boot:
Switch(config)# no boot manual switch 1
Use the boot system command to modify the boot command to boot from flash:
Switch(config)# boot system switch 1 flash:packages.conf
Use the copy running-config startup-config command to save the configuration:
Switch# copy running-config startup-config
Use the show boot command to verity that the switch is configured to boot from flash memory:
Switch# show boot
Current Boot Variables:
BOOT variable = flash:packages.conf;
Boot Variables on next reload:
BOOT variable = flash:packages.conf;
Allow Dev Key = yes
Manual Boot = no
Enable Break = no

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 15 of 36
Cisco Catalyst 3850 Switch Right-to-Use Licensing Model
The Cisco Catalyst 3850 Switch right-to-use (RTU) is a trust-based licensing model designed to give customers the
flexibility to upgrade, downgrade, or move the license for RMA purposes by using simple EXEC commands. The
RTU licensing model allows customers to specify the desired image-based licensing level (LAN Base, IP Base, and
IP Services) and AP-Count on the switch or switch stack through EXEC commands.
About the Cisco Catalyst 3850 Switch RTU license:
●The RTU license is purchased along with the Cisco Catalyst 3850 Switch (or separately) and is NOT tied to
the unique device identifier (product ID + serial number) of a switch.
●When you purchase a switch, the license you specified in the purchase order is preinstalled.
●To upgrade the license, you can order an upgrade license and receive an electronic or printed license. After
accepting the end-user license agreement (EULA), you enable the upgrade by using a simple CLI
command.
●To transfer RTU licenses from one switch to another, deactivate the license on one switch and activate it on
another.
RTU License Types
There are two main categories of Cisco Catalyst 3850 Switch RTU license: a permanent RTU license and a 90-day
evaluation RTU license.
Permanent RTU License
This is a paid license that does not expire. You can activate permanent RTU licenses after you accept the EULA.
The EULA assumes you have purchased the permanent license. There are two types of permanent RTU licenses:
●Image-based (or feature set) license
●Adder AP-Count license
Image-based license: This license is activated by Cisco before the switch is shipped and requires no customer
configuration to enable it. Supported license levels include LAN Base, IP Base, and IP Services.
You can upgrade, disable, or move image-based licenses by using the license right-to-use command, either for
individual switches or for all switches in a stack. Reload the switch or stack to activate the highest level license. For
example, if you upgrade the license level from IP Base to IP Services, then the IP services license is activated by
reloading the switch.
This command enables the ipservices license and accepts the EULA on all switches in the stack:
Switch# license right-to-use activate ipservices all acceptEULA
% switch-1:stack-mgr:Reboot the switch to invoke the highest activated License
level
Switch#
*Feb 25 23:54:40.909: %SMN_HBL_LICENSE-6-LIC_ACT: 1 stack-mgr: ipservices
license is activated successfully on switch 1
*Feb 25 23:54:40.909: %SMN_HBL_LICENSE-6-LIC_CHANGE: 1 stack-mgr: Switch 1
reboot license level changed from lanbase to ipservices. Reboot the switch to
invoke the new license level.

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 16 of 36
Switch# show license right-to-use summary
License Name Type Count Period left
-----------------------------------------------
ipbase permanent N/A Lifetime
apcount base 0 Lifetime
apcount adder 0 Lifetime
----------------------------------------------
License Level In Use: ipbase
License Level on Reboot: ipservices
Evaluation AP-Count: Disabled
Total AP Count Licenses: 0
AP Count Licenses In-use: 0
AP Count Licenses Remaining: 0
Adder AP-Count license: The adder AP-Count license is an “add as you grow” license. You can add access point
licenses as your network grows. You activate an adder AP-count license by using EXEC commands, and it is
activated without a switch reload.
This example shows the license summary display for a switch with an activated adder AP-Count license:
Switch# show license right-to-use summary
License Name Type Count Period left
-----------------------------------------------
ipservices permanent N/A Lifetime
apcount base 0 Lifetime
apcount adder 10 Lifetime
--------------------------------------------
License Level In Use: ipservices
License Level on Reboot: ipservices
Evaluation AP-Count: Disabled
Total AP Count Licenses: 10
AP Count Licenses In-use: 0
AP Count Licenses Remaining: 10
Switch# license right-to-use activate apcount 25 slot 1 acceptEULA
Switch#
*Mar 19 00:28:50.506: %SMN_HBL_LICENSE-6-AP_ADD: 1 stack-mgr: 25 adder AP-count
licenses are added
Switch# show license right-to-use summary
License Name Type Count Period left
-----------------------------------------------
ipservices permanent N/A Lifetime
apcount base 0 Lifetime

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 17 of 36
apcount adder 35 Lifetime
--------------------------------------------
License Level In Use: ipservices
License Level on Reboot: ipservices
Evaluation AP-Count: Disabled
Total AP Count Licenses: 35
AP Count Licenses In-use: 0
AP Count Licenses Remaining: 25
This example shows the license summary display for a switch with a deactivated adder AP-Count license:
Switch# license right-to-use deactivate apcount 25 slot 1
Switch#
*Mar 19 00:32:10.186: %SMN_HBL_LICENSE-6-AP_DEL: 1 stack-mgr: 25 adder AP-count
licenses are removed.
Switch# show license right-to-use summary
License Name Type Count Period left
-----------------------------------------------
ipservices permanent N/A Lifetime
apcount base 0 Lifetime
apcount adder 10 Lifetime
----------------------------------------------
License Level In Use: ipservices
License Level on Reboot: ipservices
Evaluation AP-Count: Disabled
Total AP Count Licenses: 10
AP Count Licenses In-use: 0
AP Count Licenses Remaining: 10
Image-Based License in a Stack
In a Cisco Catalyst 3850 Switch stack, all switches must be at the same image-based license (IP Services/IP
Base/LAN Base) level. The active switch license level is considered the reference, and the member switch
licenses are compared to it. If there is a mismatch, the active switch displays a syslog message saying that the
stack configuration was unsuccessful.
This is an example of the display on the active switch console:
%STACKMGR-1-STACK_LINK_CHANGE: Stack port 1 on switch 2 is up
Switch 2 has a license mismatch with the stack. Only on activating a compatible
license will the switch join the stack.
Switch# show switch

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 18 of 36
Switch/Stack Mac Address : 00e1.6d52.c600 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
--------------------------------------------------------------------
*1 Active 00e1.6d52.c600 15 V03 Ready
2 Member 44ad.d96d.b480 1 0 Lic-Mismatch
3 Member 0000.0000.0000 0 0 Provisioned
This message appears on the member switch console:
Switch# show license right-to-use mismatch
Slot# License Name Adder AP Count Base AP Count
----------------------------------------------------------
2 ipbase 50 0
Switch# show license right-to-use summary
License Name Type Count Period left
-----------------------------------------------
ipservices permanent N/A Lifetime
apcount base 0 Lifetime
apcount adder 0 Lifetime
--------------------------------------------
License Level In Use: ipservices
License Level on Reboot: ipservices
Evaluation AP-Count: Disabled
Total AP Count Licenses: 0
AP Count Licenses In-use: 0
AP Count Licenses Remaining: 0
To enable the member switch to join the stack, change the license level of the member switch (switch 2) by
activating the license from the active switch console:
Switch# license right-to-use activate ipservices slot 1 acceptEULA
% switch-1:stack-mgr:Reboot the switch to invoke the highest activated License
level
Switch#
*Mar 3 21:03:58.309: %SMN_HBL_LICENSE-6-LIC_ACT: 1 stack-mgr: ipservices
license is activated successfully on switch 1
*Mar 3 21:03:58.309: %SMN_HBL_LICENSE-6-LIC_CHANGE: 1 stack-mgr: Switch 1
reboot license level changed from lanbase to ipservices. Reboot the switch to
invoke the new license level.

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 19 of 36
Switch# reload
Reload command is being issued on Active unit, this will reload the whole stack
Proceed with reload? [confirm]
After switch 2 reloads successfully, it joins the stack with the active switch.
Switch# show switch
Switch/Stack Mac Address : 00e1.6d52.c600 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
------------------------------------------------------------------
*1 Active 00e1.6d52.c600 15 V03 Ready
2 Standby 44ad.d96d.b480 1 V03 Ready
3 Member 0000.0000.0000 0 0 Provisioned
AP-Count License in a Stack
AP-Count license is available only with IP Base and IP Services licenses. A Cisco Catalyst 3850 Switch stack can
support a maximum of 50 access points. An AP-Count license is required only if a Cisco Catalyst 3850 Switch is
configured as both a mobility controller and a mobility agent. An AP-Count license is not needed if the Cisco
Catalyst 3850 Switch is configured only as an mobility agent, which is the default configuration.
The total AP-Count license of a Cisco Catalyst 3850 Switch stack is equal to the sum of all the individual member
AP-Count licenses, up to a maximum of 50 AP-Counts. The total AP-Count license of the stack is affected when
stack members are added or removed:
●When new members are added to the stack, the total AP-Count license of the stack is automatically
recalculated.
●When members are removed from the stack, the AP-Count license contributed by the removed switch is
decremented from the total available AP-Count license in the stack.
●If more AP-Counts are connected than the available AP-Count license, a syslog warning message indicates
this fact without disconnecting the excess connected AP-Counts until a stack reload.
●After the stack reload, the surplus AP-Count s are removed from the total AP-Count. The following
examples explain the process.
Stack member addition example: A Cisco Catalyst 3850 Switch stack includes 3 switches, each with an AP-
Count license that allows 10 AP-Counts, for a total of 30 supported AP-Counts. When a new Cisco Catalyst 3850
Switch (switch 4) is added to the stack with an AP-Count license allowing 25 AP-Counts, the stack supports a total
of 50 AP-Counts because the total number of 55 access points (30+25) exceeds the stack limit.
Stack member removal example: In the preceding example, if switch 4 is removed from the stack, the AP-Count
license remains at 50 AP-Counts until the stack is reloaded, if 50 AP-Counts are connected and active in the stack.
After reload, the stack returns to its original value of 30 AP-Counts.

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 20 of 36
When the AP-Count for a stack exceeds 50, a syslog message appears in the active and member switches to
indicate the excess AP-Count:
%SMN_HBL_LICENSE-1-EXCESS_AP_LIC: Total AP Count Licenses available have exceeded
the Maximum supported AP Count by 60
Switch# show license right-to-use summary
License Name Type Count Period left
-----------------------------------------------
ipservices permanent N/A Lifetime
apcount base 0 Lifetime
apcount adder 110 Lifetime
--------------------------------------------
License Level In Use: ipservices
License Level on Reboot: ipservices
Evaluation AP-Count: Disabled
Total AP Count Licenses: 50
AP Count Licenses In-use: 0
AP Count Licenses Remaining: 50
By default the Cisco Catalyst 3850 Switch stack is configured as a mobility agent. In the wireless licensing model, a
mobility agent is the access point count enforcement point. A mobility controller is the access point count
management point. A Cisco Catalyst 3850 Switch stack can be configured as either a mobility controller or a
mobility agent, or both, depending on the deployment requirement.
Figure 3 shows a typical licensing protocol interaction between an AP-Count, a mobility agent, and a mobility
controller: