Check the adder AP count licenses are decremented on the given switch. Activated evaluation AP Count licenses on the stack. EULA will be prompted, accept it. Check the license type evaluation with maximum supported AP Count is displayed. Base and adder AP Count licenses are not seen. To check the base and adder apcount licenses, if any. Deactivates evaluation AP Count licenses on the stack. Base and Adder AP Count licenses are displayed.
The Catalyst switch supports three different feature sets:. Note A separate access point count license is required to use the switch as a wireless controller. For more information about the features, see the product data sheet at this URL:. This section describes the interoperability of this version of the switch software release with other client devices. Table 9 Test Bed Configuration for Interoperability. Connectivity, traffic, and roaming between two access points.
Table 10 lists the client types on which the tests were conducted. The clients included laptops, handheld devices, and phones. It is not supported on virtual interfaces, for example, VLAN, port channel nor other logical interfaces. NBAR2 match criteria will not be allowed in a policy that has queuing features configured.
Uplink can be attached as long as it is a single uplink and is not part of a port channel. Above this rate, AVC service is not guaranteed. Caveats describe unexpected behavior in Cisco IOS releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved. The Bug Search Tool BST , which is the online successor to Bug Toolkit, is designed to improve the effectiveness in network risk management and device troubleshooting.
The BST allows partners and customers to search for software bugs based on product, release, and keyword, and aggregates key data such as bug details, product, and version. The tool has a provision to filter bugs based on credentials to provide external and internal bug views for the search input. Enter the bug ID in the Search For: field. Click on the identifier to view the details of a caveat in the BST. MAB fails to start negotiation after device moves to another layer 2 adjacent switch.
APs with -S domain rejected to join the switch due to Invalid regulatory domain. MAC address learning failure on port configured with port-security. Inconsistent stack state after losing active member during "HA sync in progress".
Catalyst stack SFP cannot be recognized on some port and the port link also do not up. QinQ tunnels causing L2 loop in specific topology of Catalyst switch.
Catalyst Uplinkfast take time when recovery from link failure. Catalyst series switches crash while accessing OBFL. Powered Devices not getting PoE on multiple interfaces in Catalyst stack. WLC in X not sending vlan override info in guest anchor scenario. Standby running Interface on standby switch in stack is not coming up after soft reload. Wireless clients associating to controller with wrong downloadable acl.
Host limit of 32 for session monitoring sessions for PC mac deleted from port-security table even with sticky config. Removing FNF config using the command "no vlan config " causes watchdog forced crash. Should not install Policy Map that has a Table-map action in police used with priority feature. APs send block ACK packets using disabled data rates. Switch netflow export packet Vlan ID display as "unknown" in packet capture. BLK does not to change to forwarding state immediatly.
IP Phone authorization failing on switch after interface flap. SFP port detect link-flap error and it's in error-disabled state on switch.
NGWC guest accounts aren't deleted after lifetime expires. Traceback: Stack master crash at dot1x authentication.
Switch does NOT answer arp request for some specific mac addresses. UDLD error disables the 10G interface when enabling "udld aggresive" on peer. Device IP address AV pair replaced with Configuring "qos queue-softmax-multiplier" causes stackwise-virtual members to split or crash.
LLDP attibutes are not seen in accounting messages during config changes. Unresponsive on save wi th multiple privilege commands. Ten gig links gets err-disable after "UDLD enable" on Switch crashes continuously after booting up with autosmartport. Modified Rogue APs must be reclassified by new reports even if they are classified as Malicious.
When 'dot1x critical eapol' is configured, switch sends EAP failure instead of Success. Denali Observed traceback: "Node not found for wdb type 5". Switch prevents updating MAC address in multi-host mode. AP not receiving 11AC data rates configuration from wlc.
SSH logs showing empty username on successful authentication. Controller allows changing AP mode to monitor. Traffic is not excluded from role-based permissions when enforcement is disabled on interface. Access-session commands can never be removed from port. Line-by-Line sync verifying failure on command: client test01 server-key 0 Password. User intermittently blocked from local login to WebUI wrong credentials Received from 0.
Unicast ping stops working when "ip pim sparse-mode" removed from SVI. Custom Nbar protocol is classifying traffic incorrectly. Downlink port LEDs display green without plugging anything in the port. LOOP packets still can be seen when "no keepalive" configured. Port-channel flapping causing REP topology failure in 10 seconds. QinQ and L2PT do not work as expected on and switches. Output drops and Output errors increment simultaneously in show interfaces.
EFP deleted when unconfig otv overlay interface and then config back. Polaris REP Multicast Traffic does not resume after neighbor switch reloaded.
ACL matching IP option is not working with "no ip unreachables". IPv6 neighbor discovery packet processing behavior. Mode button functionality not working Intermittently.
PD's not getting PoE on multiple interfaces in stack. Latency increases with low priority background traffic. Wireless mobility client data tx via macsec uplink foreign is drop. When one vrf deletes with "no vrf definition", ip vrf receive is removed. Memory leak due to path querry with Null outgoing interface. CGM Traceback observed impacting client connectivity.
Crash after member link re-added to port-channel and clear counters CMD. Improper Reporting of FEPs on with 3. Infinity: Image name will need to be changed to not have Cisco reference. Switch not forwarding traffic after applying the policy-map. RLDP config does not get saved on reboot or upgrade. Should be in [1,5].
Secure Fabric, issuing "show fabric host-pool" is crashing box on C Leapsec 3. NTP leap second addition is not working during leap second event. CStack:Port-Channel:active mem switch power shut causes traffic loss. Passwords still encrypted after encryption key is removed. Secure LDAP with wired 1k dot1x sessions may reload the system. Session fails authz after few vlans in group brought down and up.
System traceback while Smart Call Home debugs turned on. Then choose your product and click Troubleshoot and Alerts to find information for the problem that you are experiencing.
The RSS feeds are a free service. All rights reserved. Skip to content Skip to search Skip to footer. Available Languages. Download Options. Updated: August 20, Introduction Cisco Catalyst Series Switches are the next generation of enterprise class stackable access layer switches that provide full convergence between wired and wireless networks on a single platform.
Description and License Level Information. New in Documentation. A client that fails to accept the response message with option 61, is not in compliance with RFC and requires a firmware upgrade. In a Smart Install network when vstack is enabled, system log messages are generated every hour. The running configuration displays whether vstack is enabled or disabled. When running the command show vstack config , there are a few output differences compared to the older releases.
Use SSH Version 2 instead. Optics Modules Catalyst switches support a wide range of optics. Access Points. We recommend 1 GHz. Cisco Wireless Control Module Version. Caution Do not power cycle your switch during the upgrade. Switch show run i tftp. Switch show run i ip route vrf. Current configuration : bytes. Switch ping vrf Mgmt-vrf ip 5. Type escape sequence to abort. Software Install Image to Flash.
Preparing install operation New software will load on reboot. Copyright c by Cisco Systems, Inc. Compiled Tue Sep by mcpre. Clean Up Step 1 Ensure you have enough space in flash to expand a new image by cleaning up old installation files. Switch request platform software package clean switch all file flash:. Running command on switch 1. Cleaning up unnecessary package files. Scanning boot directory for packages Preparing packages list to delete File is in use, will not delete.
Nothing to clean. Running command on switch 2. Running command on switch 3. Running command on switch 4. Software Install Image to Flash Step 4 Use the request platform software package install switch all file flash: new auto-copy command to install the target image to flash. Finished list of software package changes. Your device supports two modes to boot the software packages:. You can boot your device in installed mode by booting the software package provisioning file that resides in flash:.
The provisioning file contains a list of software packages to boot, mount, and run. The ISO file system in each installed package is mounted to the root file system directly from flash. The packages and provisioning file used to boot in installed mode must reside in flash.
Booting in installed mode from usbflash0: or tftp: is not supported. You can boot your device in bundle boot mode by booting the bundle. The provisioning file contained in a bundle is used to decide which packages to boot, mount, and run. Packages are extracted from the bundle and copied to RAM. The ISO file system in each package is mounted to the root file system. Unlike install boot mode, additional memory that is equivalent to the size of the bundle is used when booting in bundle mode.
The AP image pre-download feature is not supported in bundle boot mode. All the switches in a stack must be running in installed mode or bundle boot mode. A mixed mode stack is not supported. If a new switch tries to join the stack in a different boot mode then the active switch, the new switch is given a V-mismatch state. If a mixed mode switch stack is booted at the same time, then only those switches that boot up in a different mode than the active go to the V-mismatch state.
If the boot mode does not support auto-upgrade, then the switch stack members must be re-booted in the same boot mode as the active switch. If the stack is running in installed mode, the auto-upgrade feature can be used to automatically upgrade the new switch that is attempting to join the switch stack. The auto-upgrade feature changes the boot mode of the new switch to installed mode. If the stack is running in bundle boot mode, the auto-upgrade feature is not available. You will be required to use the bundle mode to boot the new switch so that it can join the switch stack.
Use the device setup program if you want to be prompted for specific IP information. With this program, you can also configure a hostname and an enable secret password.
It gives you the option of assigning a Telnet password to provide security during remote management and configuring your switch as a command or member switch of a cluster or as a standalone switch. If you are using DHCP, do not respond to any of the questions in the setup program until the device receives the dynamically assigned IP address and reads the configuration file. If you are an experienced user familiar with the device configuration steps, manually configure the device.
Otherwise, use the setup program described in the Boot Process section. The factory-assigned default hostname is Device. DHCP provides configuration information to Internet hosts and internetworking devices. This protocol consists of two components: one for delivering configuration parameters from a DHCP server to a device and an operation for allocating network addresses to devices.
DHCP is built on a client-server model, in which designated DHCP servers allocate network addresses and deliver configuration parameters to dynamically configured devices. This is to help ensure that these servers remain accessible in case one of the connected stack members is removed from the switch stack. A relay device forwards broadcast traffic between two directly connected LANs.
A router does not forward broadcast packets, but it forwards packets based on the destination IP address in the received packet. When you boot up your device , the DHCP client is invoked and requests configuration information from a DHCP server when the configuration file is not present on the device.
If the configuration file is present and the configuration includes the ip address dhcp interface configuration command on specific routed interfaces, the DHCP client is invoked and requests the IP address information for those interfaces. With this message, the client and server are bound, and the client uses configuration information received from the server.
The amount of information the device receives depends on how you configure the DHCP server. The offer from the DHCP server is not a guarantee that the IP address is allocated to the client; however, the server usually reserves the address until the client has had a chance to formally request the address.
If the device accepts replies from a BOOTP server and configures itself, the device broadcasts, instead of unicasts, TFTP requests to obtain the device configuration file. The configuration files on all clients are identical except for their DHCP-obtained hostnames.
If a client has a default hostname the hostname name global configuration command is not configured or the no hostname global configuration command is entered to remove the hostname , the DHCP hostname option is not included in the packet when you enter the ip address dhcp interface configuration command.
In this case, if the client receives the DCHP hostname option from the DHCP interaction while acquiring an IP address for an interface, the client accepts the DHCP hostname option and sets the flag to show that the system now has a hostname configured. You can use the DHCP image upgrade features to configure a DHCP server to download both a new image and a new configuration file to one or more devices in a network.
Simultaneous image and configuration upgrade for all switches in the network helps ensure that each new device added to a network receives the same image and configuration. The DHCP-based autoconfiguration with a saved configuration process stops if there is not at least one Layer 3 interface in an up state without an assigned IP address in the network. Unless you configure a timeout, the DHCP-based autoconfiguration with a saved configuration feature tries indefinitely to download an IP address.
The auto-install process stops if a configuration file cannot be downloaded or if the configuration file is corrupted. The configuration file that is downloaded from TFTP is merged with the existing configuration in the running configuration but is not saved in the NVRAM unless you enter the write memory or copy running-configuration startup-configuration privileged EXEC command. If the downloaded configuration is saved to the startup configuration, the feature is not triggered during subsequent system restarts.
The downloaded configuration file becomes the running configuration of the device. It does not over write the bootup configuration saved in the flash, until you reload the device. You can use DHCP auto-image upgrade with DHCP autoconfiguration to download both a configuration and a new image to one or more devices in your network. The device or devices downloading the new configuration and the new image can be blank or only have a default factory configuration loaded.
If the new configuration is downloaded to a switch that already has a configuration, the downloaded configuration is appended to the configuration file stored on the switch. Any existing configuration is not overwritten by the downloaded one. After you install the device in your network, the auto-image update feature starts. The downloaded configuration file is saved in the running configuration of the device , and the new image is downloaded and installed on the device.
When you reboot the device , the configuration is stored in the saved configuration on the device. Follow these guidelines if you are configuring a device as a DHCP server:. You should configure the DHCP server with reserved leases that are bound to each device by the device hardware address.
Router IP address default gateway address to be used by the device required. Boot filename the name of the configuration file that the client needs recommended. Depending on the settings of the DHCP server, the device can receive IP address information, the configuration file, or both.
If you do not configure the DHCP server with the lease options described previously, it replies to client requests with only those parameters that are configured. If the IP address and the subnet mask are not in the reply, the device is not configured. Unavailability of other lease options does not affect autoconfiguration. The device can act as a DHCP server. These features are not operational. If you did not specify the configuration filename, the TFTP server, or if the configuration file could not be downloaded, the device attempts to download a configuration file by using various combinations of filenames and TFTP server addresses.
The files include the specified configuration filename if any and these files: network-config, cisconet. For the device to successfully download a configuration file, the TFTP server must contain one or more configuration files in its base directory. The files can include these files:. The configuration file named in the DHCP reply the actual device configuration file. The router-confg or the ciscortr. The preferred solution is to configure the DHCP server with all the required information.
The TFTP server contains the configuration files for the device. If it is on a different LAN, the device must be able to access it through a router. Depending on the availability of the IP address and the configuration filename in the DHCP reserved lease, the device obtains its configuration information in these ways:. The IP address and the configuration filename is reserved for the device and provided in the DHCP reply one-file read method. The device sends a unicast message to the TFTP server to retrieve the named configuration file from the base directory of the server and upon receipt, it completes its boot up process.
The device sends a broadcast message to a TFTP server to retrieve the named configuration file from the base directory of the server, and upon receipt, it completes its boot-up process.
The configuration filename is not provided two-file read method. The device sends a unicast message to the TFTP server to retrieve the network-confg or cisconet. If the network-confg file cannot be read, the device reads the cisconet. The default configuration file contains the hostnames-to-IP-address mapping for the device.
The device fills its host table with the information in the file and obtains its hostname. If the hostname is not found in the file, the device uses the hostname in the DHCP reply.
If the hostname is not specified in the DHCP reply, the device uses the default Switch as its hostname. After obtaining its hostname from the default configuration file or the DHCP reply, the device reads the configuration file that has the same name as its hostname hostname -confg or hostname.
If the cisconet. If the device cannot read the network-confg, cisconet. If the device cannot read the router-confg file, it reads the ciscortr. With a normally operating device , you enter the boot loader mode only through the console connection configured for bps. Unplug the device power cord, and press the Mode button while reconnecting the power cord. You can release the Mode button after all the amber system LEDs turn on and remain solid. The boot loader device prompt then appears.
The device boot loader software provides support for nonvolatile environment variables, which can be used to control how the boot loader, or any other software running on the system, operates. Environment variables that have values are stored in flash memory outside of the flash file system. Each line in these files contains an environment variable name and an equal sign followed by the value of the variable.
A variable has no value if it is not present; it has a value if it is listed even if the value is a null string. Many environment variables are predefined and have default values. You can change the settings of the environment variables by accessing the boot loader or by using Cisco IOS commands. Under normal circumstances, it is not necessary to alter the setting of the environment variables.
This table describes the function of the most common environment variables. A semicolon-separated list of executable files to try to load and execute when automatically booting. Specifies the Cisco IOS image to load during the next boot cycle and the stack members on which the image is loaded. This command changes the setting of the BOOT environment variable. When booting in installed mode, the package provisioning file specified in the boot command is used to determine which packages to activate.
For example boot flash:packages. When booting in bundle mode, the package provisioning file contained in the booted bundle is used to activate the packages included in the bundle.
For example, boot flash:image. Decides whether the switch automatically or manually boots. Valid values are 1, yes, 0, and no. If it is set to no or 0, the boot loader attempts to automatically boot up the system.
If it is set to anything else, you must manually boot up the switch from the boot loader mode. The next time you reboot the system, the switch is in boot loader mode. Changes the filename that Cisco IOS uses to read and write a nonvolatile copy of the system configuration. Specifies the filename that Cisco IOS uses to read and write a nonvolatile copy of the system configuration.
Enables a break to the auto-boot cycle. You have 5 seconds to enter the break command. When the switch is connected to a PC through the Ethernet management port, you can download or upload a configuration file to the boot loader by using TFTP. Make sure the environment variables in this table are configured. However, if you modify this variable after the boot loader is up or the value is different from the saved value, enter this command before using TFTP. A reset is required for the new value to take effect.
Specifies the IP address and the subnet mask for the associated IP subnet of the switch. You can schedule a reload of the software image to occur on the device at a later time for example, late at night or during the weekend when the device is used less , or you can synchronize a reload network-wide for example, to perform a software upgrade on all devices in the network. Reload of the software to take affect in the specified minutes or hours and minutes.
The reload must take place within approximately 24 hours. You can specify the reason for the reload in a string up to characters in length.
Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book Updated: October 7, Chapter: StackWise Virtual Commands.
Chapter Contents StackWise Virtual Commands stackwise-virtual domain id stackwise-virtual link stackwise-virtual dual-active-detection show stackwise-virtual Close. StackWise Virtual Commands stackwise-virtual domain id stackwise-virtual link stackwise-virtual dual-active-detection show stackwise-virtual stackwise-virtual To enable Cisco StackWise Virtual on a switch, use the stackwise-virtual command in the global configuration mode. Command Default Disabled. The range is from 1 to The default is one.
Command Default No domain ID is configured. Usage Guidelines This command is optional. Example The following example shows how to enable Cisco StackWise Virtual and configure a domain ID: Device config stackwise-virtual Device config-stackwise-virtual domain 2 stackwise-virtual link To associate an interface with configured StackWise Virtual link, use the stackwise-virtual link command in the interface configuration mode.
0コメント