![]() ![]() Note The procedures in this note contain CLI command examples. For more information about the commands used in the procedures, see the. This document contains the following sections: • • • • • • Information About Upgrading to Version 5.0, 5.1, or 5.2 This section provides general information about upgrading your WAAS software to version 5.0, 5.1, or 5.2 and contains these topics: • • • Upgrade Paths Upgrading to version 5.0, 5.1, or 5.2 is supported from certain older versions only. If you have a WAAS device that is running a version from which upgrading directly to version 5.0, 5.1, or 5.2 is not supported, first upgrade the device to the next highest supported intermediate version and then upgrade to the desired 5.0, 5.1, or 5.2 version. Specifies which WAAS software versions can be directly upgraded to version 5.0, 5.1, or 5.2 and which versions require an intermediate upgrade. The Cisco 3850 IOS upgrade procedure is very easy but it is a bit different than the usual software image of previous switches i.e 3750 etc. The main difference is the Cisco 3850 switch run IOS-XE so you have to copy the.bin file to the flash on the switch and then install the software on the switch. May 8, 2018 - Upgrade Part 5: Upgrade the Data Center WAAS Software. Upgrade Part 6. Procedure for Downgrading the WAAS CM to a Previous Version. Hi all, i'm currently starting software upgrade procedure in my WAAS environment. I'm upgrading from 4.1.5b to 4.2.3c. After rebooting my WAE's i'm having the following alarm. Note If you have to upgrade from CIFS legacy mode to the transparent CIFS application accelerator, make sure that you do so in a separate change window. • You must upgrade the Central Manager software to version 5.0, 5.1, or 5.2 prior to upgrading other Wide Area Application Engine (WAE) devices in your network. • Make sure the Cisco IOS release on the router or switch has been scrubbed for WCCP issues for your specific platform. Mcafee vse 8.8 product guide. You must do this action only on routers and switches that participate in transparent redirection and is not applicable to policy-based routing (PBR) or inline deployments. If you do not do this action and there is a current active WAAS network, disable WCCP in the routers and switches in the data center and all branches before the software upgrade to 5.0, 5.1, or 5.2. • You may need to update firmware or BIOS on some or all of your devices; see the for the latest information on firmware requirements and updates. • The following device platform is no longer supported on WAAS version 5.1 or later: NME-502. WAAS version 5.1 or later does not operate or install on this device. • The following device platforms are no longer supported on WAAS version 5.0 or later: NME-302, NME-522, WAE-512, and WAE-612 platforms. WAAS version 5.0 or later does not operate or install on these devices. Additionally, the NME-502 platform is not supported in WAAS version 5.1. • If you are using NTLM Windows domain authentication or are using a nonstandard port (other than port 88) for Kerberos authentication, you must change these configurations and ensure that your domain controller is configured for Kerebos authentication before proceeding with an upgrade to WAAS version 5.1 or later, which does not support NTLM or nonstandard ports. For more details on the procedure, see the WAAS. Note If you are using WCCP, the default value for the WCCP source IP mask changed in version 4.2.1 and later to 0xF00. However, if you are upgrading a WAE that used the previous default WCCP source IP mask of 0x1741 (or any custom mask), its WCCP mask will not be changed. If you are downgrading a WAE to a version earlier than 4.2.1, its WCCP source IP mask will not be changed. By not changing the mask during an upgrade or downgrade, the WAE avoids unexpected mask changes and WCCP farm disruptions. All WAEs in a WCCP farm must have the same mask or they will not participate in the farm. For important upgrade details, including to which software version you want to upgrade, see the WAAS. Capacity Planning Capacity planning is an ongoing process as branches and applications are added. Cisco Waas Training![]() Check the WAE devices to make sure that they are providing adequate caching and optimization and that connection limits are not exceeded. If you determine that you need more processing capacity, contact your Cisco representative. Upgrading Your WAAS Software This section contains the following topics: • • • • • • • • • Information About Upgrade Methods You can use one of the following methods to perform the WAAS upgrade and transfer the new software image onto the WAE devices in the WAAS network: • Use the Central Manager Software Update feature to distribute the WAAS software image to WAAS devices. • Install the software image directly using the Software Recovery CD or USB method to perform a clean install (not an upgrade), which deletes the previous WAAS software image, deletes any cache and so forth. • Use FTP or TFTP directly on the WAE through the command-line interface (CLI). The remainder of this document assumes that you are using FTP or TFTP and the CLI to upgrade your software. ![]() If you are using one of the other methods, see the 'Maintaining Your WAAS System' chapter of the. Upgrading Your Firmware On WAE and WAVE appliances, before proceeding with your software upgrade, we recommend that you update the following three types of system firmware to the latest versions to best support new WAAS features: • BIOS on the WAVE-594/694/7541/7571/8541 models—The latest BIOS is required for the AppNav operation in WAAS version 5.0 and later. • BMC firmware on the WAVE-294/594/694/7541/7571/8541 models—The latest BMC firmware is required for the Intelligent Platform Management Interface (IPMI) over LAN feature in WAAS version 5.0 and later. • RAID controller firmware on the WAE-674/7341/7371 and WAVE-7541/7571/8541—The latest RAID controller firmware is recommended to avoid some rarely encountered RAID controller issues. See the for the latest information on firmware requirements and updates. Selecting a WAAS Upgrade Software Image Two different WAAS software images are available. One provides only accelerator and AppNav Controller (ANC) functionality, while the other provides all (universal) functionality, as shown in. Descriptions Accelerator Includes Application Accelerator and ANC functionality only. This image is smaller than the Universe image, which makes it the preferred software image to use for upgrading your WAE devices. Universal Includes Central Manager, Application Accelerator functionality and ANC functionality. Cisco Waas Software Upgrade Procedures To RemoveYou can use this type of software file to upgrade either a Central Manager or an Application Accelerator device. This image is considerably larger than the Accelerator-only software image. ![]() Additionally, a separate set of No Payload Encryption (NPE) images are provided that have the disk encryption feature disabled. These images are suitable for use in countries where disk encryption is not permitted. Be sure to use the standard or NPE software images as required. You can recognize the NPE images by the '-npe' designation in the image filenames. Upgrading Sequence Use this procedure to upgrade your WAAS network to version 5.0, 5.1, or 5.2. Step 1 Create a backup of the Central Manager database and save it to an external hard drive, as described in the. Cisco Waas Design GuideStep 2 Upgrade the Secondary Central Manager, if present, as described in the. Step 3 Upgrade the primary Central Manager, as described in the. Note You must upgrade your Central Manager(s) before you upgrade the rest of the WAE devices in your WAAS network. Step 4 Upgrade the other WAE network devices, as described in the and the. Step 5 If you are migrating some or all of your devices from the CIFS application accelerator to the new SMB application accelerator, follow the migration steps described in the. Creating a Backup of the Primary Central Manager Use this procedure to back up the primary Central Manager (CM) database and copy the backup file to an FTP server. Procedure Step 1 Telnet to the primary CM. Step 7 Verify that all the WAE devices are online and in the AllWAASGroup.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |