This module has four 10 G slots or four 1 G slots. Each port supports a 1 G or 10 G connection. Catalyst switches support a wide range of optics. Because the list of supported optics is updated on a regular basis, consult the tables at this URL for the latest SFP compatibility information:. Table 3 lists the supported products of the Catalyst Switch. Table 3 Catalyst Switch Supported Products.
Cisco Aironet , W, , , , ,, , , , W, i, , , , , , , , , Table 4 lists the specific supported Cisco access points. Table 4 Supported Access Points. PI update PI 3. See Prime Infrastructure 3. Therefore, we recommend that you upgrade to MSE 8. Cisco WLC Release 7. Prime Infrastructure 2. For more information on the compatibility of wireless software components across releases, see the Cisco Wireless Solutions.
You can use the show version privileged EXEC command to see the software version that is running on your switch. Note Although the show version output always shows the software image running on the switch, the model name shown at the end of this display is the factory configuration and does not change if you upgrade the software license. You can also use the dir filesystem : privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Initiate auto upgrade for switches running incompatible software. Commit the provisioned software and cancel the automatic rollback timer. Expand a software bundle to local storage, default location is where the bundle currently resides. When you upgrade from any prior IOS 3. If the boot loader is automatically upgraded, it will take effect on the next reload. If you go back to an IOS 3. The updated boot loader supports all previous IOS 3.
The boot loader may be upgraded to version 4. For example:. The boot loader may be upgraded to version 3. Do not restart the switch during the upgrade or downgrade process.
It does not occur during switch reloads or on non-PoE switches. The following console messages are displayed during microcode upgrade:. Step 2 Copy the image from your tftp server to flash. Step 3 Use the dir flash command to confirm that the image has been successfully copied to flash.
You can point to the source image on your TFTP server or in flash if you have it copied to flash. Before upgrade, generate the server key using the crypto key generate rsa command in global configuration mode. To verify whether the RSA server key is available on your device, run the show crypto key command.
Note Old files listed in the logs should be removed using the request platform software package clean switch all command, after reload. If not, you can manually boot flash:packages. Note When you boot the new image, it will automatically update the boot loader.
Step 6 When the new image boots up, you can verify the version of the new image, by checking show version. Step 7 After you have successfully installed the image, you no longer need the. Refer to the upgrade sections in install mode.
Warning Starting from In order to do a software image upgrade, you must be booted into IOS using the boot flash:packages. Step 1 Ensure you have enough space in flash to expand a new image by cleaning up old installation files. Note Use the switch all option to clean up all switches in your stack. Step 2 Copy the new image to flash: or skip this step if you want to use the new image from your TFTP server.
Step 4 Use the request platform software package install switch all file flash: new auto-copy command to install the target image to flash. We recommend copying the image to a TFTP server or the flash drive of the active switch. If you point to an image on the flash or USB drive of a member switch instead of the active , you must specify the exact flash or USB drive - otherwise installation fails.
For example, if the image is on the flash drive of member switch Use the auto-copy option to copy the. Note When you execute the command, the following message is displayed: Unknown package type 21 This is expected and does not affect the upgrade.
See CSCux Note Old files listed in the logs will not be removed from flash. Step 5 After you have successfully installed the software, verify that the flash partition has six new. See sample output below:. Step 6 After you have successfully installed the image, you no longer need the. If you copied the file to flash, you can delete it from the flash of each switch. Step 7 Reload the switch.
Step 8 If the switch is configured with auto boot, then the stack automatically boots up with the new image. Step 9 When the new image boots up, you can verify the version of the new image, by using the show version command:. Step 4 Use the request platform software package install switch all file flash: auto-copy command to install the target image to flash.
If you point to an image on the flash or USB drive of a member switch instead of the active , you must specify the exact flash or USB drive. Note Use the switch all option to upgrade all switches in your stack Use the auto-copy option to copy the. Step 5 After the software has been successfully installed, verify that the flash partition has five new. See sample output below. Step 6 After you have successfully installed the image, you do not need the.
Step 8 If your switches are configured with auto boot, then the stack will automatically boot up with the new image. Step 9 When the new image boots up, you can verify the version of the new image, using the show version command:.
Step 4 Use the request platform software package install command with the new option to downgrade your stack. You can point to the source image on your tftp server or in flash if you have it copied to flash. Note Use the switch all option is needed to upgrade all switches in your stack. Note The old files listed in the logs should be removed using the software clean command, after reload. Step 5 After you have successfully installed the image, you no longer need the.
Step 6 Reload the switch. Step 7 If your switches are configured with auto boot, then the stack will automatically boot up with the new image. It will remain updated. Note If you have a stack, you must copy the image to the flash of each switch in your stack.
Step 4 Clear the boot variable. Step 5 Edit the boot variable to point to the new image. Step 6 Use the write memory command to save the configuration change. Step 7 Use the show boot command to confirm that your boot variable is pointing to the new image. Step 8 Reload the switch. Step 9 If your switches are configured with auto boot, the stack will automatically boot up with the new image.
Step 10 When the new image boots up, you can verify the version of the new image, by checking show version. Step 11 Ensure you have enough space in flash to expand a new image by cleaning up old installation files. Step 13 Use the software expand command to expand the target image to flash and move from bundle mode to install mode.
Step 14 Clear the boot variable. Step 15 Edit the boot variable to point to the new image. Step 16 Use the write memory command to save the configuration change. Step 17 Use the show boot command to confirm that your boot variable is pointing to the new image.
Step 18 Reload the switch. Step 19 If your switches are configured with auto boot, the stack will automatically boot up with the new image. Step 20 When the new image boots up, you can verify the version of the new image, by checking show version.
Step 21 After you have successfully installed the image, you no longer need the. The sub-package upgrade steps are similar to the bundle package upgrade, except that you only install one sub-package and not all packages. In order to perform a sub-package software image upgrade, you must be booted into IOS using boot flash:packages. Step 1 Copy new sub-package image to flash.
The pre-download steps are as follows:. Shows all APs connected to the controller, includes joined and not joined APs. Only joined AP s can perform the image pre-downloading process. While pre-downloading the AP image s , use show ap image to monitor the pre-downloading status.
Go to the next step after image pre-downloading is completed. Restarts all the APs that have connected to the controller. The mismatched switch will not be put into Lic-Mismatch state. Even though the switch with the mismatched license is allowed to join the stack, the following syslog message is displayed periodically reminding you to fix the RTU license level:. For more information, see CSCux This command provides options to activate or deactivate any license supported on the platform.
Activate IP Services license. Pass the switch id. Activate IP Services evaluation license. Check the reboot license level is ipservices eval. EULA will be accepted automatically without being prompted. Activate IP Base license on all the switches in the stack. Search instead for. Did you mean:. All Community This category This board. Dot1x failing now. Any help???
Labels: Labels: Other Switching. All forum topics Previous Topic Next Topic. Philip D'Ath. I would downgrade to the "gold star" release 3. In response to Philip D'Ath. Some users can't downgrade ie Multigig swtiches.
In the Releases field, enter the release for which you want to see bugs. To see more content about a specific bug, you can do the following: Mouse over a bug in the preview to display a pop-up with more information about that bug. To restrict the results of a search, choose from one or more of the following filters: Filter Description Modified Date. A predefined date range, such as last week or last six months. A specific type of bug, such as open or fixed. Support Cases.
Whether a support case has been opened or not. ASR Fails to detect power supply at startup. RP3: Polaris : Kernel warning messages seen on console. Speedracer, Kahuna and Nighster images do not support "show software authenticity". Traffic stalls on Argus-X after both FP reload. Display Third party SFP only if 'service unsupported-transceiver' enable. ASR1k: "sh plat software peer interface-manager rX" missing some info. Polaris: clear domain iwan border channel doesn't work on XE platform.
ASRX, frame counter increased after reload. CSR: Ingress over-subscription not represented by 'show controllers'. CSR startup config sometimes disappear after reload. Crypto low-queue queue-depth goes over queue-limit. Polaris: Firmware version displayed as "unknown" in latest CGE7 image. Traffic rate getting affected by qos policy. ESP crash observed while testing with Orange Configs.
NTP Leap second add not working in Polaris. Router crash when removing EzPM configs. PfR channels unreachable with quick monitor and quick monitor probes to 1 in 10 secs.
Dreamliner failed to power up PD in some kind of case. Power supplies showing "ps fail" when they function fine. Random Netclock error messages appearing on console. IOSd crash in QoS stats. Platform does not trigger license release when the port moves into error disable state. Router crashes using show BGP commands. Unable to pass traffic if spoke to spoke fails to build in phase 2. As1k CFM traffic frames being sent with 2 dot1q tags.
Vlan Oversubscription packets are not working. Ingress Unicast traffic not received on the BDI. POS interface doesn't come up on clearing alarms. BQS unable to resume processing leading to pending objects constantly increasing. Asr1k crashes at PPP process on pushing 4 or more per-user static ipv6 routes.
BGP crashes when removing advertise-map. Crash due memory corruption in AFW. Cube crashed when "sh sip-ua calls br" command entered. After reload route policy processing not re-evaluate with route-map using match RPKI. BGP crashed configuring different update-source interface with v6 LL peering. Router crashes on configuring bandwidth on the Dialer interface. VNET global vrf neighbor is down after an interface flap. Missing FIB subblock causes crash when configuring vrf. ASR1k crashed while unconfiguring Netflow.
Need API for ip best source address for given outgoing interface. Modifying crypto ACL leads to a removal of crypto map config. Crash at update of context nhrp. Behavior difference between XE3. ISIS route oscillation due to ldp sync and interface max metric.
Running command "show policy-map interface" or "show tech nbar" can cause crash. SRTE: Single hope tunnel doesn't install any repair path. Crash when interface with multiple tunnels sourced comes up. Multiple Parent Events Per Node lead to a crash. ESP crashes after manual failover.
To configure the router as an https server, enter the ip http secure-server command shown in the example:. Step 8 Configure the router for local authentication, by entering the ip http authentication local command, as shown in the example:.
Step 9 Configure the vty lines for privilege level For nonsecure access, enter the transport input telnet command. For secure access, enter the transport input telnet ssh command.
An example of these commands follows:. Severity 1 caveats are the most serious caveats. Severity 2 caveats are less serious. Severity 3 caveats are moderate caveats. This section includes severity 1, severity 2, and selected severity 3 caveats.
The open and resolved bugs for this release are accessible through the Cisco Bug Search Tool. This web-based tool provides you with access to the Cisco bug tracking system, which maintains information about bugs and vulnerabilities in this product and other Cisco hardware and software products. The Cisco Bug Search Tool enables you to filter the bugs so that you only see those in which you are interested. You can save searches that you perform frequently.
Note If the defect that you have requested cannot be displayed, this may be due to one or more of the following reasons: the defect number does not exist, the defect does not have a customer-visible description yet, or the defect has been marked Cisco Confidential. We recommend that you view the field notices for the current release to determine whether your software or hardware platforms are affected.
You can access the field notices from the following location:. Note You must have a Cisco. If you do not have one, you can register for an account. Step 2 If you are redirected to a Log In page, enter your registered Cisco.
Step 4 To search for bugs related to a specific software release, do the following:. If you begin to type the product name, the Cisco Bug Search Tool provides you with a drop-down list of the top ten matches. If you do not see this product listed, continue typing to narrow the search results. In the Releases field, enter the release for which you want to see bugs.
The Cisco Bug Search Tool displays a preview of the results of your search below your search criteria. Step 5 To see more content about a specific bug, you can do the following:. Step 6 To restrict the results of a search, choose from one or more of the following filters:. A predefined date range, such as last week or last six months.
The bug severity level as defined by Cisco. The rating assigned to the bug by users of the Cisco Bug Search Tool. Your search results update when you choose a filter. All open bugs for this release are available in the Cisco Bug Search Tool.
Stateful features enhancement for big flow Elephant flow -CFT infra dependency. Subscribers cannot re-login due to CoA time-out lite-sessions in routed mode. All resolved bugs for this release are available in the Cisco Bug Search Tool. Rekey Timer are same for both the Server and Client. Software crash due to memory corruption after packet trace was enabled. ASRHX crashed after huge traffic is transmitted over it. PKI incorrect fingerprint calulation during CA authentication.
ISR , wrongly adding to Port to subscriber field after translation. Unexpected reload in btrace routines due to division by NULL. Router crash occurs while running Dell software update.
Router reloads on 'show track' command when there is track object for deleted serial sub-interface. Hoot-n-holler multicast traffic marked with DSCP 0. Unable to remove command 'ip nat inside destination'. High Availability system with two Voice Gateways - Crash. BGP 'address-family ipv4' sub-configuration is not shown in the running configuration. Trap being generated with wrong oid ISR not re-calculating the hash value correctly after payload change.
Dreamliner: flowcontrol receive command on L2 ports does not take effect. Router runs Denali Mgig stack keeps crashing while configuring with Radius commands. ISRX sometime drop the packet when volume -based rekey occurred. Router crash due to PuntInject Keepalive Process - kmalloc failures. Protocol type for GRE header doesn't work consistently with "cts sgt inline" enable over auto-tunnel. ISR ISR crashing immediately following auto-CA certificate renewal.
ISR no collisions count up on duplex mismatch condition. Snmp v2 breaks due to Authentication failure, bad community string, The device crashes with "debug platform condition ipv4 access-list ". Nexthop is wrong in route-import table on branch when delete WAN interface and reconfigure it. Cisco XE
0コメント