-
null
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to perform other system tasks such as setting the system clock, modifying the default system configuration settings, and enabling alarm overload detection, after you have done a basic configuration of your Cisco WAAS device. This chapter also describes how to register and manage Cisco IOS routers running Cisco AppNav-XE and Cisco WAAS Express.
Note Throughout this chapter, the term Cisco WAAS device is used to refer collectively to the Cisco WAAS Central Managers and Cisco WAEs in your network. The term Cisco WAE refers to Cisco WAE and Cisco WAVE appliances, and Cisco vWAAS instances.
This chapter contains the following sections:
Use the Cisco WAAS Central Manager GUI to make the following changes to the properties of a Cisco WAE device:
You can also use the Cisco WAAS Central Manager GUI to check the status of a device to determine if it is Online, Pending, or Inactive.
You can only rename a Cisco WAAS Central Manager device from the GUI.
To modify a device’s properties, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name.
Step 2 Choose device-name > Activation.
The Device Activation window appears with fields for editing the properties of the selected device.
For a Cisco WAAS Central Manager device, the only fields that you can change in this window are the Name and NetBIOS Name of the device. In addition, the device IP address and role are displayed.
Step 3 Under the General Configuration heading, set or modify the following device properties:
– The name must use only alphanumeric characters and hyphens (-).
– The first and last character must be a letter or a digit.
– Maximum length is 30 characters.
– The following characters are considered illegal and cannot be used when naming a device:
@, #, $,%, ^, &, *, (), |, \””/, <>.
You can also click the Deactivate icon in the task bar to deactivate the device. Deactivating a device allows you to replace the device in the event of a hardware failure without losing all of its configuration settings.
Step 4 Under the Locality heading, set or change the location by choosing a new location from the Location drop-down list. To create a location for this device, see Creating Locations in the chapter “Using Device Groups and Device Locations” .
Step 5 Under the Management Interface Configuration with NAT heading, configure the NAT settings using the following fields:
Note If the Cisco WAAS Central Manager cannot contact a device using the primary IP address, it attempts to communicate using the Management IP address.
Step 6 In the Comments field, enter any comments that you want to display for this device.
This section contains the following topics:
Cisco WAAS Version 4.1.1 and later provides software licenses that enable specific Cisco WAAS optimization and acceleration features. A software license must be installed and configured before the features that it enables will operate.
Table 10-1 lists the software licenses that may be purchased and the features that each license enables.
Consider the following operating guidelines for Cisco WAAS software licenses:
The exact WAAS Express licensing process depends on the version of IOS running on your WAAS Express router:
– Prior to Cisco IOS Version 15.3(3), the Cisco WAAS Express license is managed by using the router CLI command license install. This uses a single license that enables the Cisco WAAS Express optimization feature.
– For Cisco IOS Version 15.3(3)M, the Cisco WAAS Express feature no longer requires a separate license, but is a Right To Use (RTU) feature included in the AppxK9 license.
– For Cisco IOS Version 15.4(1)T and later, Cisco WAAS Express is a Right To Use (RTU) feature that is included in the default license that is delivered with the router; no specific license needs to be installed.
Note If you are upgrading the Cisco WAAS Express devices to Cisco IOS Version 15.3(3)Mn, as part of the new Appxk9 license support in Cisco WAAS Express IOS 15.3(3)M, you need to upgrade the Cisco WAAS Central Manager to Cisco WAAS Version 5.3.1 or later. or else the devices will go off offline.
To add a license to a Cisco WAE from the Cisco WAAS Central Manager, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name.
Do not choose a Cisco WAAS Central Manager device to add a license, because you must use the Cisco WAAS CLI to manage licenses on Cisco WAAS Central Managers.
Step 2 Choose Admin > History > License Management.
Step 3 Check the check box next to each license that you want to add.
Consider the following guidelines to add, remove, manage, or display Cisco WAAS software licenses:
Consider the following recommendations, restrictions, and requirements when using the Cisco WAAS setup utility:
– For Cisco WAAS Version 6.0 and later, the Cisco WAAS setup utility will accept IPv6 address for Interface, Cisco WAAS Central Manager, Domain Name Server Entry and Network Time Protocol settings. You can configure IPv4 only, IPv6 only or dual stack network using the Cisco WAAS setup utility.
– The Cisco WAAS setup utility requires a minimum 25 row x 80 column terminal window for proper display (terminal length, if configured, must be 24).
- Set the emulation to vt100, so that all lines show up properly.
- Set the Input Translation to Shift-JIS on the File > Properties menu.
– When executing the Cisco WAAS setup utility from the Cisco WAAS CLI, disable console logging, to avoid system message flooding on the screen.
– After a restore factory-default, we recommend that you follow the system prompt to run the Cisco WAAS setup utility.
Smart Licensing is a cloud-based, software license management solution that allows you to manage and track the status of your license, hardware and software usage trends. Smart Licensing enables you to automate time-consuming, manual licensing tasks by simplifying the three core functions of purchasing, managing and reporting of licenses. Smart Licensing on the device works with the Cisco Smart Software Manager (CSSM), the portal that enables you to manage all of your Cisco Smart software licenses from one centralized website.
Smart Licensing is available when you upgrade your Cisco WAAS Central Manager and all other devices registered with it to release version 6.4.3 and later. Table 10-2 shows the models considered for smart licensing as part of this release.
Table 10-2 Cisco Device Models Considered for Smart Licensing
|
|
|
|
|
---|---|---|---|---|
Table 10-3 provides an overview of the steps you must complete to set up and enable Smart Licensing.
|
|
---|---|
Create a Smart Account |
Identifies the information that you need to setup before configuring Smart licenses for your WAAS devices. For more information, see Creating a Smart Account. |
Enable Smart Licensing |
Describes the steps to enable smart licensing for the device. For more information, see Enabling Smart License for a device. |
Obtain token from Cisco Smart Software Manager (CSSM). |
Describes how to obtain tokens to be used for registering your device. For more information, see Creating a New Token. |
Register/de-register device with CSSM. |
Describes the steps to register and de-register the device from the CSSM portal. For more information, see Enabling Smart License for a device. |
A Smart Account provides a single location for all Smart License-enabled products and entitlements. It assists in speed procurement, deployment and maintenance of Cisco Software. When creating a Smart Account the submitter must have the authority to represent the requesting organization. After submitting the request goes through a brief approval.
A Virtual Account exists as a sub-account within the Smart Account. Virtual Accounts are a customer defined structure based on organizational layout, business function, geography or any defined hierarchy. They are created and maintained by the Smart Account administrator(s).
The creation of a new Smart Account is a one-time event and subsequent management of users is a capability provided through the tool.
To request a Smart Account, follow these steps:
Step 1 Log into the software.cisco.com and select Administration>Request a Smart Account.
Step 2 Select the type of Smart Account to create. There are two options:
Step 3 Provide the required domain identifier and the preferred account name.
The account request will be pending an approval of the Account Domain Identifier. A subsequent email will be sent to the requester to complete the setup process.
Smart Account user management is available in the Administration section of software.cisco.com. To add a new user to a Smart Account, follow these steps:
Step 1 Log in to software.cisco.com and choose Manage Smart Account> Administration.
Step 2 From the Administration window, choose Users > New User and provide the required email address, Cisco ID and role. Roles may be defined to manage the entire Smart Account or specific Virtual Accounts.
Step 3 Click Continue to complete the process.
A token is required for registering a device to the Cisco Smart Software Manager (CSSM).
Step 1 Log into the CSSM, select the appropriate Virtual Account and in the General tab, select New Token.
Step 2 Follow the dialog to provide a name, duration and export compliance applicability before accepting the terms and responsibilities. Choose Create Token to continue.
Step 3 Copy the token ID. The Cisco Smart Software Manager will respond with a dialogue, indicating that the token has been copied to your clipboard
From release 6.4.3, WAAS devices support both traditional licensing and smart software licensing. Eventually all devices in WAAS will support only the smart software licensing model in which case it will be enabled by default and the product instance will start in Evaluation Mode. Evaluation Mode means that a product instance has enabled Smart Licensing (either manually or by default and has not registered with Cisco Smart Software Manager or Cisco Smart Software Manager satellite).
To enable smart license on a device for the first time, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Devices > device-name.
Step 2 Choose Admin > Licenses> Smart License.
The Smart License Configuration window appears.
Step 3 Select Enable Smart License under Smart License Registration.
Step 4 View/Edit the Transport Settings to see how your device communicates with the CSSM. The Transport methods are
Step 5 Click Submit. The product is in Evaluation mode after enabling Smart Software License and you can see the Authorization Status reflecting the same. The evaluation mode is for 90 days. You can continue to use the product in the Evaluation mode state.
A functioning Smart Account is required to complete the registration process. If you do not have a smart account, you can create and account. For more information, see Creating a Smart Account.
Three key elements are exchanged with the Cisco Smart Software Manager (CSSM) over https during the registration process.
To register an unregistered device with CSSM, follow the steps:
Step 1 Ensure that you have completed steps 1-5 in Enabling Smart License for a device.
Step 2 A token id is required to register your device to CSSM. If you do not have a token, log into the Cisco Smart Software Manager and do the needful. For more information, see Creating a New Token.
Step 3 On the WAAS Central Manager GUI, enter the token id obtained earlier, in the ID Token field and trigger the smart license registration by selecting the Register action from the dropdown.
Note Conversion status and wait time for next poll will be updated in Smart Agent after 1 hour and the same will be updated in WAAS Central Manager GUI. This is because the Smart Agent running on the WAAS device takes one hour to check with the CSSM portal. Please ensure not to perform any actions (re-register/reload/restart) on the device when conversion is in progress state.
Device is smart-enabled and accounted for after completion of this process. Table 10-4 shows the refreshed details of the following under the Smart Licensing Status after the registration is complete.
You can select the Refresh button to see latest device smart license status in the WAAS Central manager GUI after each Submit action.
Table 10-4 Smart License Status Field Details
Step 4 In the case of Registration or Authorization failure: After viewing the failure message in the Cisco WAAS Central Manager GUI, use the Force Register button to register the product (in case there is an issue with the registration).
Step 5 Table 10-5 shows the actions you can choose to initiate after the device is in Registered state.
Table 10-5 Registered State Actions
Step 6 You can choose to disable or de-register the device from CSSM. by selecting the Deregister/Disable option from the Action drop-down list and click Submit. This will release the license from CSSM portal after successful deregistration.
After each action the details under the Smart Licensing Status are updated.
Periodic synchronization between Cisco WAAS and CSSM every 24 hrs, ensures that the Smart Licensing status for the devices is up to date and in sync with the CSSM.
Note You can monitor the smart license logs in the smart-license.log file under errorlog.
To display the smart license status, run the show license tech-support EXEC command.
File Transfer Protocol (FTP) lets you download, upload, and copy configuration files between remote hosts and a switch. Unlike TFTP, which uses User Datagram Protocol (UDP), a connectionless protocol, FTP uses TCP, which is connection oriented. Inetd (an Internet daemon) is a program that listens for connection requests or messages for certain ports and starts server programs to perform the services associated with those ports. FTP copies files between devices.
FTP is a subset of the UNIX rshell service, which allows UNIX users to execute shell commands on remote UNIX systems. It is a UNIX built-in service. This service uses TCP as the transport protocol and listens for requests on TCP port 514. FTP service can be enabled on Cisco WAAS devices that use Cisco WAAS software.
To enableFTP services on a Cisco WAAS device, follow these steps:
Note For the FTP transfer to be successful, configure a Pass-Through policy for the FTP server. If an Optimized policy is configured for the FTP server, the FTP transfer will fail.
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name ( or Device Groups > device-group-name).
Step 2 Choose Configure > Network > Network Services. The Network Services window appears.
Step 3 Check the Enable FTP check box to enable Inetd FTP services. By default, this option is disabled.
Note The Inetd daemon listens for FTP, and TFTP services. For Inetd to listen to FTP requests, it must be explicitly enabled forFTP service.
Step 4 Click Submit to save your changes.
A Click Submit to Save message appears in red next to the Current Settings line when there are pending changes to be saved after you have applied default or device group settings. You can also revert to the previously configured settings by clicking the Reset button. The Reset button is visible only when you have applied default or group settings to change the current device settings but you have not yet submitted the changes.
If you try to leave this window without saving the modified settings, a Warning dialog box prompts you to submit the changes. The Warning dialog box appears only if you are using the Internet Explorer browser.
This section explains how to configure date and time settings for your Cisco WAAS network devices and contains the following topics:
The Cisco WAAS Central Manager GUI allows you to configure the time and date settings using a Network Time Protocol (NTP) host on your network. NTP allows the synchronization of time and date settings for the different geographical locations of the devices in your Cisco WAAS network, which is important for proper system operation and monitoring. On each Cisco WAAS device, be sure to set up an NTP server to keep the clocks synchronized.
To configure NTP settings, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name ( or Device Groups > device-group-name).
Step 2 Choose Configure > Date/Time > NTP. The NTP Settings window appears.
Step 3 In the NTP Server field, enter up to four hostnames or IP addresses, separated by spaces.This field now accepts IPv6 addresses.
Unexpected time changes can result in unexpected system behavior. We recommend reloading the system after configuring an NTP server or changing the system clock.
If you have an outside source on your network that provides time services (such as an NTP server), you do not need to set the system clock manually. When manually setting the clock, enter the local time.
Note Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at startup to initialize the software clock.
To configure the time zone on a device or device group, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name ( or Device Groups > device-group-name).
Step 2 Choose Configure > Date/Time > Time Zone. The Time Zone Settings window appears.
Step 3 To configure a standard time zone, follow these steps:
a. Under the Time Zone Settings section, click the Standard Time Zone radio button. The default is UTC (offset = 0) with no summer time configured. When you configure a standard time zone, the system is automatically adjusted for the UTC offset, and the UTC offset need not be specified.
The standard convention for time zones uses a Location/Area format in which Location is a continent or a geographic region of the world and Area is a time zone region within that location.
b. From the Standard Timezone drop-down list, choose a location for the time zone. (For an explanation of the abbreviations in this list, see Table 10-6 .)
The window refreshes, displaying all area time zones for the chosen location in the second drop-down list.
c. Choose an area for the time zone. The UTC offset is automatically set for standard time zones.
Summer time is built-in for some standard time zones (mostly time zones within the United States), and will result an automatic change in the UTC offset during summer time. For a list of standard time zones that can be configured and their UTC offsets, see Table 10-7 .
Step 4 To configure a customized time zone on the device, follow these steps:
a. Under the Time Zone Settings section, click the Customized Time Zone radio button.
b. In the Customized Time Zone field, specify the name of the time zone. The time zone entry is case-sensitive and can contain up to 40 characters including spaces. If you specify any of the standard time zone names, an error message is displayed when you click Submit.
c. For UTC Offset, from the first drop-down list choose the plus sign (+) or minus sign (–) sign to specify whether the configured time zone is ahead or behind UTC. Also, choose the number of hours (0 to 23) and minutes (0–59) offset from UTC for the customized time zone. The range for the UTC offset is from -23:59 to 23:59, and the default is 0:0.
Step 5 This step shows how to configure two types of customized summer time, Absolute Summer Time and Recurring Summer Time.
Note You can specify a customized summer time for both standard and customized time zones.
Configuring Absolute Summer Time
a. From the Customized Summer Time Savings section, click the Absolute Dates radio button.
You can configure a start date and end date for summer time in absolute dates or recurring dates. Absolute date settings apply only once and must be set every year. Recurring dates apply repeatedly for many years.
b. In the Start Date and End Date fields, specify the month (January through December), day (1 to 31), and year (1993 to 2032) on which summer time must start and end, in the mm/dd/yyyy format. Make sure that the end date is always later than the start date.
Configuring Recurring Summer Time
a. From the Customized Summer Time Savings section, click the Recurring Dates radio button.
b. From the Start Day drop-down list, choose a day of the week to start (Monday to Sunday).
c. From the Start Week drop-down list, choose an option to set the starting week (first, 2nd, 3rd, or last).
For example, choose first to configure summer time to recur beginning the first week of the month or last to configure summer time to recur beginning the last week of the month.
d. From the Start Month drop-down list, choose a month to start (January to December).
e. From the End Day drop-down list, choose a day of the week to end (Monday to Sunday).
f. From the End Week drop-down list, choose an option to set the ending week (first, 2nd, 3rd, or last).
For example, choose first to configure summer time to end beginning the first week of the month or last to configure summer time to stop beginning the last week of the month.
g. From the End Month drop-down list, choose a month to end (January to December).
Step 6 Start Time and End Time fields for summer time are the times of the day when the clock is changed to reflect summer time. By default, both start time and end time are set to 00:00.
To configure start time and end time:
a. From the Start Time drop-down lists, choose the hour (0 to 23) and minute (0 to 59) at which daylight saving time should start.
b. From the End Time drop-down lists, choose the hour (0 to 23) and minute (0 to 59) at which daylight saving time should end.
Step 7 In the Offset field, specify the minutes offset from UTC (0–1439). (See Table 10-7 .)
The summer time offset specifies the number of minutes that the system clock moves forward at the specified start time and backward at the end time.
Step 8 Click the No Customized Summer Time Configured radio button to not specify a summer or daylight saving time for the corresponding time zone.
Step 9 Click Submit to save the settings.
A Click Submit to Save message appears in red next to the Current Settings line when there are pending changes to be saved after you have applied default or device group settings. You can also revert to the previously configured settings by clicking the Reset button. The Reset button is visible only when you have applied default or group settings to change the current device settings but have not yet submitted the changes.
If you attempt to leave this window without saving the modified settings, a warning dialog box prompts you to submit the changes. This dialog box only appears if you are using the Internet Explorer browser.
|
|
---|---|
|
|
---|---|
UTC was formerly known as Greenwich Mean Time (GMT). The offset time (number of hours ahead or behind UTC) as displayed in the table is in effect during winter time. During summer time or daylight saving time, the offset may be different from the values in the table and is calculated and displayed accordingly by the system clock.
Secure Store encryption provides strong encryption and key management for your Cisco WAAS system. The Cisco WAAS Central Manager and Cisco WAE devices use Secure Store encryption for handling passwords, managing encryption keys, and for data encryption.
This section contains the following topics:
With Secure Store encryption on the Cisco WAAS Central Manager or a Cisco WAE device, the Cisco WAAS system uses strong encryption algorithms and key management policies to protect certain data on the system. This data includes encryption keys used by applications in the Cisco WAAS system, user login passwords and certificate key files.
Secure Store encryption on the Cisco WAAS Central Manager is always enabled and uses a password that is auto-generated or user-provided. This password is used to generate the key encryption key according to secure standards. The Cisco WAAS system uses the key encryption key to encrypt and store other keys generated on the Cisco WAAS Central Manager or Cisco WAE devices. These other keys are used for Cisco WAAS functions including disk encryption, SSL acceleration, or to encrypt user passwords.
Data on the Cisco WAAS Central Manager is encrypted using a 256-bit key encryption key generated from the password and using SHA1 hashing and an AES 256-bit algorithm. When Secure Store is enabled on a WAE device the data is encrypted using a 256-bit key encryption key generated using SecureRandom, a cryptographically strong pseudo random number generator.
Secure Store encryption on a Cisco Central Manager uses one of the following modes:
To implement Secure Store your system must meet the following requirements:
To implement strong Secure Store encryption, follow these steps:
Step 1 Enable strong storage encryption on your primary Cisco WAAS Central Manager. See Enabling Secure Store Encryption on the Cisco WAAS Central Manager.
Step 2 Enable strong storage encryption on any standby Cisco WAAS Central Managers. See Enabling Secure Store Encryption on a Standby Central Manager.
Step 3 Enable strong storage encryption on Cisco WAE devices or Cisco WAE device groups. See Enabling Secure Store Encryption on a Cisco WAE Device. (Secure Store must be enabled on the Cisco WAAS Central Manager before you enable it on the Cisco WAE devices.)
You can enable Secure Store independently on the Cisco WAAS Central Manager and on the Cisco WAE devices. To ensure full protection of your encrypted data, enable Secure Store on both the Cisco WAAS Central Manager and the Cisco WAE devices. You must enable Secure Store on the Cisco WAAS Central Manager first.
Note When you reboot the Cisco Central Manager, if Secure Store is in user-provided passphrase mode, you must manually open Secure Store encryption. All services that use the Secure Store (such as disk encryption, SSL acceleration, or AAA) on the remote Cisco WAE devices do not operate properly until you enter the Secure Store password on the Cisco WAAS Central Manager to open Secure Store encryption.
Note the following considerations regarding the Secure Store:
If you have a backup made when the Secure Store was in auto-generated passphrase mode and you restore it to a system where the Secure Store is in user-provided passphrase mode, you do not need to enter a password. After the restore, the system is in auto-generated passphrase mode.
Secure Store is enabled by default on a new Cisco WAAS Central Manager, with a system-generated password that opens the Secure Store after the system boots. You do not need to do anything to enable Secure Store.
If a Cisco WAAS Central Manager is configured in user-provided passphrase mode, you must manually open the Secure Store after the system boots. To open Secure Store encryption on the Cisco WAAS Central Manager, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Admin > Secure Store. The Configure CM Secure Store window appears.
Step 2 At the Open Secure Store area, enter the Secure Store passphrase in the Current passphrase field.
The Secure Store is opened. Data is encrypted using the key derived from the password.
To open the Secure Store from the Cisco WAAS CLI, run the cms secure-store open EXEC command.
Note Whenever you reboot a Cisco WAAS Central Manager that is configured in user-provided passphrase mode, you must reopen the Secure Store manually. All services that use the Secure Store (such as disk encryption, SSL acceleration, or AAA) on the remote Cisco WAE devices do not operate properly until you enter the Secure Store password on the Cisco WAAS Central Manager to reopen the Secure Store. Switch to auto-generated passphrase mode to avoid having to reopen the Secure Store after each reboot.
Note When you enable Secure Store on the primary Cisco WAAS Central Manager in user-provided passphrase mode, you should also enable Secure Store on the standby Cisco WAAS Central Manager. See Enabling Secure Store Encryption on a Standby Central Manager.
To check the status of the Secure Store encryption, run the show cms secure-store command.
Note A standby Cisco WAAS Central Manager provides limited encryption key management support. If the primary Cisco WAAS Central Manager fails, the standby Cisco WAAS Central Manager provides only encryption key retrieval to the Cisco WAE devices but does not provide new encryption key initialization. Do not enable disk encryption or Secure Store on Cisco WAE devices when the primary Cisco WAAS Central Manager is not available.
The Secure Store passphrase mode on the primary Cisco WAAS Central Manager is replicated to the standby Cisco WAAS Central Manager (within the standard replication time). If the primary Cisco WAAS Central Manager is switched to auto-generated passphrase mode, the standby Cisco WAAS Central Manager Secure Store changes to the Open state. If the primary Cisco WAAS Central Manager is switched to user-provided passphrase mode or the passphrase is changed, the standby Cisco WAAS Central Manager Secure Store changes to the initialized but not open state and an alarm is raised. You must manually open the Secure Store on the standby Cisco WAAS Central Manager.
To enable Secure Store encryption on a standby Cisco WAAS Central Manager when the primary Cisco WAAS Central Manager is in user-provided passphrase mode, open the Secure Store on the primary Cisco WAAS Central Manager and then use the Cisco WAAS CLI to run the cms secure-store open EXEC mode command on the standby Cisco WAAS Central Manager:
Step 1 Enable Secure Store encryption on the primary Cisco WAAS Central Manager. See Enabling Secure Store Encryption on the Cisco WAAS Central Manager.
Step 2 Wait until the standby Cisco WAAS Central Manager replicates the data from the primary Central Manager.
The replication should occur in sixty seconds (default) or as configured for your system.
Step 3 Enter the cms secure-store open EXEC command on the standby Cisco WAAS Central Manager to activate Secure Store encryption.
The standby Cisco WAAS Central Manager responds with the Please enter pass phrase message.
Step 4 Type the password and press Enter.
The standby Cisco WAAS Central Manager encrypts the data using Secure Store encryption.
Note Repeat Step 3 and Step 4 for each standby Cisco WAAS Central Manager on your system.
You can check the status of Secure Store encryption by entering the show cms secure-store EXEC command.
To enable Secure Store encryption on a Cisco WAE device, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name).
Note The Secure Store status must be the same for all Cisco WAE devices in a device group. Either all Cisco WAE devices in the group must have Secure Store enabled, or all must have Secure Store disabled. Before you add a Cisco WAE device to a device group, set its Secure Store status to match the others. See Working with Device Groups in the chapter “Using Device Groups and Device Locations”.
Step 2 Choose Configure > Security > Secure Store. The Secure Store Settings window appears.
Step 3 Check the Initialize CMS Secure Store box. (The Open CMS Secure Store check box will be checked automatically.)
Step 4 Click Submit to activate Secure Store encryption.
A new encryption key is initialized on the Cisco WAAS Central Manager, and the Cisco WAE encrypts the data using Secure Store encryption.
To enable Secure Store from the Cisco WAAS CLI, run the cms secure-store init EXEC command.
Note If you have made any other Cisco WAAS CLI configuration changes on a Cisco WAE within the datafeed poll rate time interval (five minutes by default) before executing the cms secure-store EXEC command, those prior configuration changes are lost and you must redo them.
Note When you enable or disable Secure Store on a device group, the changes do not take effect on all Cisco WAE devices simultaneously. When you view the Cisco WAE devices be sure to give the Cisco WAAS Central Manager enough time to update the status of each Cisco WAE device.
The Secure Store can operate either in user-provided mode or auto-generated passphrase mode and you can switch between these modes.
To change from user-provided passphrase mode to auto-generated passphrase mode, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Admin > Secure Store.
Step 2 In the Switch to CM auto-generated passphrase mode area, enter the password in the Current passphrase field.
Step 3 Click the Switch button.
Step 4 Click OK in the Confirmation message that appears.
The Secure Store is changed to auto-generated passphrase mode and remains in the Open state.
To change from auto-generated passphrase mode to user-provided passphrase mode, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Admin > Secure Store.
Step 2 In the Switch to User-provided passphrase mode area, enter a password in the New passphrase field and reenter the password in the Confirm passphrase field.
The password must conform to the following rules:
Step 3 Click the Switch button.
Step 4 Click OK in the confirmation message that appears.
The Secure Store is changed to user-provided passphrase mode and remains in the open state. If you have a standby Cisco WAAS Central Manager, you must manually open its Secure Store (see Enabling Secure Store Encryption on a Standby Central Manager).
To change Secure Store passphrase mode from the Cisco WAAS CLI, run the cms secure-store mode EXEC command.
Note When you reboot a Cisco WAAS Central Manager that is configured in user-provided passphrase mode, you must reopen the Secure Store manually. All services that use the Secure Store (such as disk encryption, SSL acceleration, or AAA) on the remote Cisco WAE devices do not operate properly until you enter the Secure Store password on the Cisco WAAS Central Manager to reopen the Secure Store. Switch to auto-generated passphrase mode to avoid having to reopen the Secure Store after each reboot.
The Secure Store encryption password is used by the Cisco WAAS Central Manager to generate the encryption key for the encrypted data. If the Cisco WAAS Central Manager is configured for user-provided passphrase mode, you can change the password.
To change the password and generate a new encryption key on the Cisco WAAS Central Manager, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Admin > Secure Store.
Step 2 In the Change Secure Store passphrase area, in the Current passphrase field, enter the current password.
Step 3 In the New passphrase field, enter the new password.
The password must conform to the following rules:
Step 4 In the Confirm passphrase field, enter the new password again.
Step 5 Click the Change button.
The Cisco WAAS device reencrypts the stored data using a new encryption key derived from the new password.
Note There may be a delay of a few minutes after you click the Change button before the changes take effect.
To change the password and generate a new encryption key on the Cisco WAAS Central Manager from the Cisco WAAS CLI, run the cms secure-store change EXEC command.
To generate a new encryption key for a Cisco WAE device from the Cisco WAAS Central Manager, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name).
Step 2 Choose Configure > Security > Secure Store.
Step 3 Check the Change CMS Secure Store box and then click Submit.
A new encryption key is generated in the Cisco WAAS Central Manager. The Cisco WAAS Central Manager replaces the encryption key in the Cisco WAE with the new key. The Cisco WAE re-encrypts the stored data using the new encryption key.
Note There may be a delay of a few minutes after you click the Submit button before the changes take effect.
To configure the Secure Store encryption key from the Cisco WAAS CLI, run the cms secure-store change EXEC command.
You can reset the Secure Store if you reload the Cisco WAAS Central Manager and you cannot open the Secure Store because it is configured in user-provided passphrase mode and you forget the Secure Store password. This procedure deletes all encrypted data, certificate and key files, and key manager keys. The Secure Store is reinitialized, configured in auto-generated passphrase mode, and opened.
To reset Secure Store encryption on a Cisco WAAS Central Manager, follow these steps:
Step 1 At the primary Cisco WAAS Central Manager CLI, enter the cms secure-store reset EXEC command to reset Secure Store encryption.
Step 2 Wait until the standby Cisco WAAS Central Manager replicates the data from the primary Central Manager.
The replication should occur in sixty seconds (default) or as configured for your system.
Step 3 Enter the cms secure-store reset EXEC command on the standby Cisco WAAS Central Manager if Secure Store is in the initialized and open state.
Step 4 From the primary Cisco WAAS Central Manager, reset all user account passwords.
For information on resetting user passwords, see Changing the Password for Another Account in the chapter “Creating and Managing Administrator User Accounts and Groups” .
Step 5 On each Cisco WAE registered to the Cisco WAAS Central Manager, follow these steps:
a. If Secure Store is initialized and open, from the Cisco WAAS Central Manager, clear Secure Store (see Disabling Secure Store Encryption on a Cisco WAE Device). Or, from the Cisco WAAS CLI, enter the cms secure-store clear EXEC command.
b. From the Cisco WAAS Central Manager, initialize Secure Store (see Enabling Secure Store Encryption on a Cisco WAE Device) or from the Cisco WAAS CLI, enter the cms secure-store init EXEC command. (This step is needed only if you performed Step 5a.)
c. Enter the crypto pki managed-store initialize EXEC command and restart the SSL accelerator.
d. If disk encryption is enabled, from the Cisco WAAS Central Manager, disable disk encryption from the Cisco WAAS CLI, enter the no disk encrypt enable global configuration command.
e. If disk encryption had been enabled before Step 5, reload the device. After the reload, reenable disk encryption and reload the device again.
Note If the Cisco WAE is reloaded before doing Step 5, disk encryption, SSL acceleration, and Secure Store does not function properly. In this case, you must restore the Cisco WAE to factory defaults.
Step 6 From the primary Cisco WAAS Central Manager, reimport all certificate and key files for all the accelerated and peering services which are configured on the Cisco WAEs.
To disable Secure Store encryption on a Cisco WAE device, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name).
Step 2 Choose Configure > Security > Secure Store. The Secure Store Settings window appears.
Step 3 Check the Clear CMS Secure Store box and then click Submit to disable Secure Store encryption and return to standard encryption.
You can also enter the cms secure-store clear EXEC command to disable Secure Store encryption and return to standard encryption.
Consider the following when you disable Secure Store in the Cisco WAAS Central Manager or with the cms secure-store clear EXEC command:
This section contains the following topics:
The Cisco WAAS software comes with default, preconfigured system properties that you can modify to alter the default behavior of the system.
The following list describes the default system properties that you can modify.
Maximum number of days since their last login after which external users will be deleted from the Cisco WAAS Central Manager database.
For example, if cdm.remoteuser.deletionDaysLimit is set to 5, external users will be deleted from the database if the difference between their last login time and the current time is more than 5 days. The default is 60 days.
External users are users that are defined in an external AAA server and not in the Cisco WAAS Central Manager. Any reports scheduled by such users are also deleted when the users are deleted.
Timeout in minutes of a Cisco WAAS Central Manager GUI session. The default is 10 minutes. If the session is idle for this length of time, the user is automatically logged out.
Status of whether a device can belong to more than one device group. The default is true (devices can belong to more than one device group).
The rate (in seconds) at which AppNav Controller collects and sends Cluster status to the Cisco WAAS Central Manager from the AppNav IOM. The default is 30 seconds.
Poll rate between a Cisco WAAS (or Cisco WAAS Express) device and the Cisco WAAS Central Manager (in seconds). The default is 300 seconds.
Device identity recovery key. This property enables a device to be replaced by another node in the Cisco WAAS network.
Scheme to use(IP address or FQDN) to launch the Device Manager GUI.
Collect and send rate in seconds for the CMS device health (or status) monitor. If the rate is set to 0, the health monitor is disabled. The default is 120 seconds.
The rate (in seconds) at which the Cisco WAAS Central Manager collects Cluster Status data from Cisco IOS Routers.
The rate (in seconds) at which the Cisco WAAS Central Manager collects Cluster Status data from Cisco IOS Routers for Cluster Topology view.
This setting controls propagation of device CLI configuration changes back to the Cisco WAAS Central Manager. If disabled, configuration changes done in the device's CLI will not be communicated to the Cisco WAAS Central Manager. This setting is system wide and applies to all managed Cisco WAAS devices. Note that disabling this setting may result in Cisco WAAS Central Manager and Cisco WAAS device(s) configuration to go out of sync.
To customize this setting for a specific device, choose Device > Admin > Config Synchronization UI page.
This setting controls whether Cisco WAAS devices accept or ignore configuration changes received from the Cisco WAAS Central Manager. It could be used in deployments where Cisco WAAS devices are not managed by Cisco WAAS Central Manager but other entity (that is, directly via the Cisco WAAS CLI). Note that disabling this setting may result in Cisco WAAS Central Manager and Cisco WAAS device(s) configuration to go out of sync.
To customize this setting for a specific device, choose Device > Admin > Config Synchronization UI page.
Rate at which a Cisco WAE collects and sends the monitoring report to the Cisco WAAS Central Manager (in seconds). For a Cisco WAAS Express device, this is the rate at which the Cisco WAAS Central Manager collects the monitoring data from the Cisco WAAS Express device. The default is 300 seconds (5 minutes). Reducing this interval impacts the performance of the Cisco WAAS Central Manager device.
Hour at which the Cisco WAAS Central Manager consolidates hourly and daily monitoring records. The default is 1 (1:00 a.m.).
Cisco WAAS and Cisco WAAS Express statistics monitoring (enable or disable). The default is True.
Maximum number of RPC failures after which statistics from Cisco WAE to Cisco WAAS Central Manager will not be transmitted.
Maximum number of devices for which monitoring is supported in location level reports. The default is 25.
Maximum number of completed or failed report instances to store for each custom report. The default is 10 report instances.
How often, in days, the Cisco WAAS Central Manager consolidates daily monitoring records into monthly records. If this setting is set to 1, the Cisco WAAS Central Manager checks if consolidation needs to occur every day, but only performs consolidation if there is enough data for consolidation to occur. The default is 14 days.
When a monthly data record is created, the corresponding daily records are removed from the database. Consolidation occurs only if there is at least two calendar months of data plus the consolidation frequency days of data. This ensures that the Cisco WAAS Central Manager always maintains daily data records for the past month and can display data on a day level granularity for the last week.
For example, if data collection starts on February 2nd, 2006 and System.monitoring.monthlyConsolidationFrequencyis set to 14, then the Cisco WAAS Central Manager checks if there is data for the past two calendar months on the following days: Feb 16th, March 2nd, March 16th, and March 30th. No consolidation will occur because there is not enough data on these days.
On April 13th, however, two calendar months of data exists. The Cisco WAAS Central Manager then consolidates data for the month of February and deletes the daily data records for that month.
Maximum number of days of monitoring data to maintain in the system. The default is 1825 days.
Default time frame to be used for plotting all the charts. Settings saved by the user will not be changed. The default is Last Hour.
Timeout in seconds for the GUI synchronization operations for the Cisco WAAS Central Manager to the Cisco WAE connection. The default is 50 seconds.
Maximum number of concurrent Cisco WAAS Central Manager sessions permitted for a user. Specify 0 (zero, the default) for unlimited concurrent sessions. A user must log off the Central Manager to end a session. If a user closes the browser without logging off, the session is not closed until after it times out after 120 minutes (the timeout is not configurable).
If the number of concurrent sessions permitted is exceeded for that user, there is no way for that user to regain access to the Cisco WAAS Central Manager GUI until after the timeout expires. This setting does not affect Cisco WAAS CLI access to the Central Manager device.
Status of the web application filter, which rejects any javascript, SQL, or restricted special characters in input. The default is False.
Maximum number of statistics data records, in thousands, that will be replicated to a standby Cisco WAAS Central Manager. The range is 10 to 300 records. The default is 200 (200,000 records). We do not recommend increasing this number.
Maximum number of seconds to wait for replication to a standby Cisco WAAS Central Manager. The range is 300 to 3600 seconds. The default is 900 seconds. We do not recommend decreasing this timeout.
Enables creation of a Cisco WAAS Central Manager user on the registered Cisco IOS device. Global or Device level or Device Group level IOS Router credential pages will be hidden if this system property is enabled.
Enables configuration of time interval for retaining alarm records. The default is 7 days but can be configured for 365 days.
Number of health monitor cycles to force a synchronization of alarm data between a Cisco WAE device and Cisco WAAS Central Manager. The default is 1 health monitor cycle. To disable this alarm update, configure 0.
Number of days to keep alarm email history in the table. The default is 7 days.
To view or modify the value of a default system property, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Configure > Global > System Properties. The Config Properties window appears.
Step 2 Click the Edit icon next to the system property that you want to change. The Modifying Config Property window appears.
Step 3 From a drop-down list, enter a new value or choose a new parameter, depending on the system property that you want to change.
Step 4 To save the settings, click Submit.
Web Application Filter is a security feature that protects the Cisco WAAS Central Manager GUI against Cross-Site Scripting (XSS) attacks. XSS security issues can occur when an application sends data that originates from a user to a web browser without first validating or encoding the content, which can allow malicious scripting to be executed in the client browser, potentially compromising database integrity.
This security feature verifies that all application parameters sent from Cisco WAAS users are validated and/or encoded before populating any HTML pages.
This section contains the following topics:
To enable the Web Application Filter, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Configure > Global > System Properties. The Config Properties window appears.
Note You cannot enable the Web Application Filter using the Cisco WAAS CLI. This feature is disabled by default.
Step 2 Click the Edit icon next to the system.security.webApplicationFilter entry.
The Modifying Config Property window appears.
Step 3 To enable the Web Application Filter feature, choose True from the Value drop-down list.
A confirmation message appears to advise Cisco WAAS Central Manager users to log out and then log back in after enabling this feature.
Step 4 Click OK and then Submit.
Step 5 Log out and then back in again.
The Web Application Filter feature verifies security using two methods, input verification and sanitization. Input validation validates all input data before accepting data. Sanitization prevents malicious configuration and scripts already present in the data from getting executed.
Input validation scans all data that is input to the Cisco WAAS Central Manager database and is only configurable by the admin user.
Any input submitted using the Cisco WAAS Central Manager GUI that is suspicious of XSS is blocked. Blocked input results in a warning.
Input data is checked against the following XSS filter rules:
The sanitizer prevents malicious configuration and scripts from getting executed in the browser when there is an XSS attack on the database. Sanitization is not configurable by the user.
Configuration data coming from the Cisco WAAS Central Manager that is suspect for XSS is shown in red on the Device Groups > All Device Groups window.
This section contains the following topics:
Communication between the Cisco WAAS device and Cisco WAAS Central Manager utilizing User Datagram Protocol (UDP) allows faster detection of devices that have gone offline.
– The primary WAAS Central Manager tracks the last time that it received a UDP heartbeat packet from each device. If the Cisco WAAS Central Manager has not received the specified number of UDP packets, it displays a status of the nonresponsive devices as Offline.
– Because UDP heartbeats require less processing than a getUpdate request, they can be transmitted more frequently, and the Cisco WAAS Central Manager can detect offline devices much faster.
– The default for the UDP feature is disabled.
– Heartbeat packet rate is defined as the interval between two UDP packets. Using the specified heartbeat packet rate and failed heartbeat count values, the Cisco WAAS Central Manager GUI displays the resulting offline detection time as a product of heartbeat rate and failed heartbeat count.
– If you enable the fast detection of offline devices, the Cisco WAAS Central Manager detects devices that are in network segments that do not support UDP and uses getUpdate (get configuration poll) request to detect offline devices.
You can detect offline Cisco WAAS devices more quickly if you enable the fast detection of offline devices. A Cisco WAAS device is declared as offline when it has failed to contact the Cisco WAAS Central Manager for a getUpdate (get configuration poll) request for at least two polling periods.
To configure fast detection of offline Cisco WAAS devices, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Configure > Global > Fast Device Offline Detection. The Configure Fast Offline Detection window appears.
Note The fast detection of offline devices feature is in effect only when the Cisco WAAS Central Manager receives the first UDP heartbeat packet and a getUpdate request from a device.
Step 2 Check the Enable Fast Offline Detection check box to enable the Cisco WAAS Central Manager to detect the offline status of devices quickly.
Step 3 In the Heartbeat Rate field, specify how often devices should transmit a UDP heartbeat packet to the Cisco WAAS Central Manager, in seconds. The default is 30 seconds.
Step 4 In the Heartbeat Fail Count field, specify the number of UDP heartbeat packets that can be dropped during transmission from devices to the Cisco WAAS Central Manager before a device is declared offline. The default is 1 UDP heartbeat packet.
Step 5 In the Heartbeat UDP Port field, specify the port number using which devices will send UDP heartbeat packets to the primary Cisco WAAS Central Manager. The default is port 2000.
The Maximum Offline Detection Time field displays the product of the failed heartbeat count and heartbeat rate.
Maximum Offline Detection Time = Failed heartbeat count * Heartbeat rate
If you have not enabled the fast detection of offline devices feature, then the Cisco WAAS Central Manager waits for at least two polling periods to be contacted by the device for a getUpdate request before declaring the device to be offline. However, if you enable the fast detection of offline devices feature, then the Cisco WAAS Central Manager waits until the value displayed in the Maximum Offline Detection Time field is exceeded.
If the Cisco WAAS Central Manager receives the Cisco Discovery Protocol (CDP) from a device, then the Cisco WAAS Central Manager GUI displays the device as offline after a time period of 2* (heartbeat rate) * (failed heartbeat count).
Note Any changes to the Configure Fast WAE offline detection window in the Cisco WAAS Central Manager could result in devices temporarily appearing to be offline. After the configuration changes are propagated to the devices, they again show as online.
Cisco WAAS devices can track the rate of incoming alarms from the Node Health Manager. If the rate of incoming alarms exceeds the high-water mark (HWM), then the Cisco WAAS device enters an alarm overload state. This situation occurs when multiple applications raise alarms at the same time to report error conditions. When a Cisco WAAS device is in an alarm overload state, the following occurs:
When the Cisco WAAS device is in an alarm overload state, the Node Health Manager continues to record the alarms being raised on the Cisco WAAS device and keeps a track of the incoming alarm rate. Alarms that have been raised on a Cisco WAAS device can be listed using the show alarm EXEC commands that are described in the restore factory-default EXEC command, see the Cisco Wide Area Application Services Command Reference Guide.
To configure alarm overload detection for a Cisco WAAS device or device group, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name).
Step 2 Choose Configure > Monitoring > Alarm Overload Detection. The Alarm Overload Detection Settings window appears.
Step 3 Uncheck the Enable Alarm Overload Detection check box if you do not want to configure the WAAS device (or device group) to suspend alarm raise and clear operations when multiple applications report error conditions. This check box is checked by default.
Step 4 In the Alarm Overload Low Water Mark (Clear) field, enter the number of incoming alarms per second below which the WAAS device comes out of the alarm overload state.
The low-water mark is the level up to which the number of alarms must drop before alarms can be restarted. The default value is 1. The low-water mark value should be less than the high-water mark value.
Step 5 In the Alarm Overload High Water Mark (Raise) field, enter the number of incoming alarms per second above which the WAAS device enters the alarm overload state. The default value is 10.
Step 6 To save the settings, click Submit.
To configure alarm overload detection from the Cisco WAAS CLI, run the alarm overload-detect global configuration command.
You can schedule reports to be generated periodically, and when they are generated, a link to the report can be e-mailed to one or more recipients. (For more information, see Managing Reports in the chapter “Monitoring Your Cisco WAAS Network” .
Note The Enable Notification for Cleared Alarms generates emails for cleared alarms only if you have cleared alarms after more than 24 hours of system time. If you clear alarms at 24 hours or less of system time, emails are not triggered for cleared alarms.
The Enable Notification for Raised Alarms generates emails for raised alarms independent of when alarms are cleared.
To enable e-mail notification, you must configure e-mail server settings for the Cisco WAAS Central Manager by following these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name. You must choose a Cisco WAAS Central Manager device.
Step 2 Choose Configure > Monitoring > Email Notification. The Configure Email Server Details window appears.
Step 3 In the Mail Server Hostname field, enter the hostname of the SMTP e-mail server that is to be used to send e-mail.
Note Only SMTP mail servers are supported. If any other type of mail server is configured, the email notification fails.
Step 4 In the Mail Server Port field, enter the port number. The default is port 25.
Step 5 In the Server Username field, enter a valid e-mail account username.
Step 6 In the Server Password field, enter the password for the e-mail account.
Step 7 In the From Address field, enter the e-mail address shown as the sender of the e-mail notification.
This section contains the following topics:
Intelligent Platform Management Interface (IPMI) over LAN provides remote platform management service for WAVE-294/594/694/7541/7571/8541 appliances. IPMI is an open standard technology that defines how administrators monitor system hardware and sensors, control system components, and retrieve logs of important system events to conduct remote management and recovery.
IPMI runs on the Baseboard Management Controller (BMC) and operates independently of Cisco WAAS. After IPMI over LAN is set up and enabled on Cisco WAAS, authorized users can access BMC remotely even when Cisco WAAS becomes unresponsive or the device is powered down but connected to a power source. You can use an IPMI v2 compliant management utility, such as ipmitool or OSA SMbridge, to connect to the BMC remotely to perform IPMI operations.
The IPMI over LAN feature provides the following remote platform management services:
IPMI over LAN and IPMI SoL features can be configured using Cisco WAAS CLI commands and include the following:
For more information on configuring IPMI over LAN, see Configuring BMC for Remote Platform Management.
IPMI over LAN requires that a specific BMC firmware version be installed on the device. The minimum supported BMC firmware versions are:
Cisco WAAS appliances shipped from the factory with Cisco WAAS Version 4.4.5 or later do have the correct firmware installed. If you are updating a device that was shipped with an earlier version of Cisco WAAS software, you must update the BMC firmware, unless it was updated previously.
To determine if you are running the correct firmware version, run the show bmc info EXEC command. The following example displays the latest BMC firmware version installed on the device (48a here):
If a BMC firmware update is needed, you can download it from cisco.com at the Cisco Wide Area Application Service (WAAS) Software download page ( registered customers only). The firmware binary image is named waas-bmc-installer-48a-48a-26a-k9.bin or a newer version may be available. Use the latest firmware update that is available.
Run the following command to update the firmware from the image file that is available through FTP on your network:
copy ftp install ip-address remotefiledir waas-bmc-installer-48a-48a-26a-k9.bin
The update process automatically checks the health status of the BMC firmware. If BMC firmware corruption is detected, BMC is recovered during the BMC firmware update procedure. The complete update process can take several minutes and the device may appear unresponsive but do not interrupt the process or power cycle the device. After the update is complete, you must reload the device.
After the device reboots, you can verify the firmware version by using the show bmc info EXEC command.
BMC recovery and BMC firmware update restores the factory defaults on the BMC and all the current IPMI over LAN configurations are erased.
If BMC firmware corruption happens, a critical alarm is raised.
This section describes the minimum steps needed to enable IPMI over LAN and IPMI SoL to conduct remote platform management. This section includes the following topics:
To enable IPMI over LAN, perform the following steps using the bmc lan command:
Step 1 Change the default BMC LAN IP address.
Step 2 Change the password for the BMC default user, which is User 2.
Step 4 Access the BMC from a remote client over IPMI session v2.0 using the username and password for the number 2 user. The default cipher suite used to access the BMC is 3, which specifies RAKP-HMAC-SHA1 authentication, HMAC-SHA1-96 integrity, and AES-CBC-128 encryption algorithms.
Step 5 To access the BMC over a IPMI session v1.5, change the user 2 IPMI-session-version setting from v2.0 to v1.5.
To enable IPMI SoL, perform the following steps:
Step 1 On the Cisco WAAS device, configure and enable IPMI over Lan (IoL).
Step 2 On the remote client make sure that the BMC user can do IoL operations successfully over IPMI session v2.0.
Step 3 On the remote client, change the baud-rate of the terminal to match the Cisco WAAS console baud rate of 9600 bps.
Step 4 On the Cisco WAAS device, enable IPMI SoL.
Step 5 On the remote client, if the IPMI management tool is ipmitool, check the SoL payload status of the specific BMC user with the following command:
ipmitool -I lanplus -H bmc-ip-address -U bmc-user-name sol payload status 1 bmc-user-userid
Step 6 If the SoL payload is disabled for this user, enable the SoL payload for this user with the following command:
ipmitool -I lanplus -H bmc-ip-address -U bmc-user-name sol payload enable 1 bmc-user-userid
Step 7 On the remote client, run the following command to open the serial console to the WAAS device:
ipmitool -I lanplus -H bmc-ip-address -U bmc-user-name sol activate
Step 8 On the remote client, you have now entered the console session of the Cisco WAAS device. When you are done, use the ~. escape character to terminate the connection.
This section contains the following topics:
You can use the Cisco WAAS Central Manager to manage Cisco WAAS Express and AppNav-XE devices, which are both Cisco IOS routers deployed with Cisco WAAS related software. The Cisco Central Manager menu displays a subset of the full menu when a Cisco WAAS Express or Cisco AppNav-XE is selected as the context, as these devices implement a subset of WAAS appliance functionality.
The Cisco WAAS Central Manager and a Cisco IOS device communicate using the HTTPS protocol. To establish communication between a Cisco WAAS Central Manager and a Cisco IOS router device, you must register the Cisco IOS router device with the Cisco WAAS Central Manager. Using the Cisco WAAS Central Manager GUI to register a Cisco IOS router device is the easiest method.
Before you register a router with the WAAS Central Manager, remove all banner configurations (with keywords such as username, password, hostname), because these banner configurations interfere with the registration process, and will generate errors.
To register a Cisco IOS router device, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Admin > Registration > Cisco IOS Routers. The Cisco IOS Router Registration window appears.
Note To register a Cisco IOS router device using the Central Manager GUI, SSH v1 or v2 must be enabled on the router.
Step 2 Select the type of IP address (IPv4 or IPv6) that the Router will use. The IPv6 option is available only when the Cisco WAAS Central Manager is configured with a valid IPv6 address.
Step 3 In the IP Address(es) field, enter the router IP addresses to register, separated by commas. The IP address, hostname, router type, and status are displayed in the Registration Status table.
Note Although an IOS router can have a dot (“.”) in the hostname, this special character is not allowed in a Cisco WAAS device hostname. If you try to import an AppNav-XE device that has a dot in the hostname, the import will fail and the following error message is displayed: Registration failed for the device devicename ConstraintException; Invalid AppNav-XE name: X.X since name includes invalid character ‘.’.
You may also upload a CSV file that contains a list of IP addresses to register. To upload a list, click the Import CSV file radio button and click the Choose File button to browse to the file and click Open. Each IP address must be on a separate line.
Step 4 Configure the router login credentials by entering the username and password. If you need to create a user on the router, see Configuring a User.
Step 5 Choose the HTTP Authentication Type, local or AAA.
Note Be sure to choose the HTTP authentication type that is currently configured on the router. If you choose an HTTP authentication type that differs from your current configuration, your existing configuration on the router will be overwritten and you may not be able to use HTTP to communicate with the router. Communications with routers with previously established authentication credentials will fail.
Step 6 In the Central Manager IP Address field, enter the IP address you want the router to use for the Cisco WAAS Central Manager. This field is initially filled in with the current Central Manager IP address but you may need to change this in a NAT environment.
Step 7 Click the Register button and verify that the registration status was successful.
You may view the results in the log file: /local/local1/errlog/waasx-audit.log
After you successfully register a Cisco IOS router device, the Cisco WAAS Central Manager displays it in the Registration Status table and in the All Devices list.
In case your want to register additional devices, use the Reset button to clear data from all the fields, to enter the next configuration.
You may need to install a software license on the Cisco IOS router device. For details, see Installing a License on the Router.
For the Cisco WAAS Central Manager to access a Cisco IOS router device, you must configure the router credentials in the Cisco WAAS Central Manager.
On the Cisco WAAS Central Manager, you can define global credentials that apply to all Cisco IOS router devices, or you can define credentials at the device group or individual device level by using the Admin > Authentication > WAAS Express Credentials/AppNav-XE Credentials menu item. To configure device group or individual device credentials, you must first complete the Cisco IOS router registration process and then configure credentials for a router device group or device. Device and device group credentials have precedence over global credentials.
To configure global router credentials, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Admin > Security > Cisco IOS Router Global Credentials. The Cisco IOS Router Global Credentials window appears.
Step 2 In the Username field, enter a username that is defined on the Cisco IOS router. If you need to create a user on the router, see Configuring a User.
Note The Username field is optional if you are not using local or AAA authentication for the HTTP server on the Cisco IOS router device; that is, if you use the default HTTP server configuration of ip http authentication enable. (See Enabling the HTTP Secure Server on the Router.)
Step 3 In the Password field, enter the password for the specified username.
To configure credentials at the device group or individual device level, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name).The Device/ Device Group window appears. Go to Admin > Authentication > WAAS Express Credentials/AppNav-XE Credentials menu item.
Step 2 In the Username field, enter a username that is defined on the Cisco IOS router. If you need to create a user on the router, see Configuring a User.
Note The Username field is optional if you are not using local or AAA authentication for the HTTP server on the Cisco IOS router device; that is, if you use the default HTTP server configuration of ip http authentication enable. (See Enabling the HTTP Secure Server on the Router.)
Step 3 In the Password field, enter the password for the specified username.
Note Changing the router credentials on the Cisco WAAS Central Manager does not change the configuration on the router device itself. It affects only the router credentials that are stored on the Cisco WAAS Central Manager.
You can also register a Cisco IOS router device with the Cisco WAAS Central Manager using the Cisco WAAS CLI by completing the steps outlined in Table 10-8 . This procedure applies to Cisco IOS routers running both WAAS Express and AppNav-XE.
|
|
---|---|
Configure a username and password. |
The same username and password are configured on the router and the Cisco WAAS Central Manager, so the Cisco WAAS Central Manager can log in to the router for management purposes. For more information, see Configuring a User. |
Import the primary Central Manager administrative server certificate into the router. |
The router requires the Cisco WAAS Central Manager certificate for secure HTTPS server communication. For more information, see Importing the Cisco WAAS Central Manager Certificate. |
Configure a router certificate. |
The Cisco WAAS Central Manager device requests this router certificate for secure HTTPS server communication. For more information, see Configuring a Cisco IOS Router Certificate. |
Enable the secure HTTP server with user authentication. |
Enables the Cisco WAAS Central Manager and router to communicate. For more information, see Enabling the HTTP Secure Server on the Router. |
Install a permanent WAAS software license. |
Allows the Cisco WAAS software to operate on the router. For more information, see Installing a License on the Router. |
Configure an NTP server. |
Keeps the time synchronized between the router and the Cisco WAAS Central Manager. For more information, see Configuring an NTP Server. |
Register the router with the Central Manager. |
Registers the router with the Cisco WAAS Central Manager. For more information, see Registering a Router with the Cisco WAAS Central Manager. |
The first step in setting up your router and Cisco WAAS Central Manager to communicate is to configure the same user on the router and the Cisco WAAS Central Manager.
To configure a user, follow these steps:
Step 1 Log in to the router Cisco WAAS CLI.
Step 2 Configure a local user with privilege level 15 on the router by using the username IOS configuration command:
Alternatively, you can configure an external TACACS+ or RADIUS user; see details after this procedure.
Step 3 Save the running configuration:
Step 4 In the Cisco WAAS Central Manager, configure the router credentials as described in Configuring Cisco IOS Router Credentials.
To configure an external TACACS+ user on the router, run the following configuration commands on the router:
To configure an external RADIUS user on the router, run the following configuration commands on the router:
The external authentication server for TACACS+ or RADIUS must be Cisco ACS 4.x or 5.x.
The next step is to import the certificate from the Cisco WAAS Central Manager into the router.
To import the certificate, follow these steps:
Step 1 Log in to the Cisco WAAS Central Manager CLI.
Step 2 Display the administrative certificate by using the show crypto EXEC command:
Step 3 Copy the certificate text, which is the part in between the BEGIN CERTIFICATE and END CERTIFICATE lines in the output.
Step 4 Log in to the router CLI.
Step 5 Configure a certificate for the Cisco WAAS Central Manager:
Step 6 Paste in the certificate that you copied from the Cisco WAAS Central Manager in Step 3.
The router needs a certificate that is requested by the Cisco WAAS Central Manager when establishing HTTPS communication. This procedure describes how to configure a persistent self-signed certificate on the router, but you can also use a CA signed certificate.
To configure a router certificate, follow these steps:
Step 1 Log in to the router CLI.
Step 2 Create a self-signed certificate on the router:
Note Due to CSCsy03412, you must configure ip domain name name before enrolling the certificate. If you do not configure ip domain name, Cisco IOS regenerates the self-signed certificate upon reload and this affects the communication with the Cisco WAAS Central Manager.
For a Cisco AppNav XE device, if the self signed certificate is generated with key label as hostname and if you change the hostname through the Cisco WAAS Central Manager GUI or router CLI, then there is a SSL handshake failure and the device goes offline. This is because the existing certificate is a valid only with respect to the old host name and the certificate needs to be validated against the hostname with which it was generated.
The Cisco WAAS Central Manager and a router communicate using the HTTPS protocol. You must enable the HTTP secure server on the router.
To enable the HTTP secure server, follow these steps:
Step 1 On the router, enable the HTTP secure server:
Note Be sure to choose the HTTP authentication type that is currently configured on the router. If you choose an HTTP authentication type that differs from your current configuration, your existing configuration on the router will be overwritten and you will not be able to use HTTP to communicate with the router.
Step 2 To configure authentication for the HTTP server, use the following options.
Note If you do not configure local or AAA authentication for the HTTP server, only the enable password is used for authentication. (The default is ip http authentication enable, which uses only the enable password and no username.) If this default configuration is used, it is not necessary to define a username credential for the router on the Cisco WAAS Central Manager. (See Configuring a User.)
The router requires one or more licenses to operate the Cisco WAAS Express or Cisco AppNav-XE software. Refer to the router documentation for details.
To install a license on the router, follow these steps:
Step 1 Obtain and copy the appropriate license to a location accessible to the license command on the router.
Step 2 On the router, install the license:
This example uses FTP to get and install the license but there are various options available for this command. Choose one that best suits your deployment.
Step 3 Save the running configuration:
It is important to keep the time synchronized between devices in your Cisco WAAS network. You should already have an NTP server configured for the Cisco WAAS Central Manager (see Configuring NTP Settings).
To configure an NTP server for the router, on the router run the ntp server global configuration command, as follows:
The final step in setting up a router with the Cisco WAAS Central Manager is to register the device. You will need to know the IP address of the Cisco WAAS Central Manager.
To register a router with the Cisco WAAS Central Manager, follow these steps:
Step 1 For a Cisco WAAS Express router, register with the Cisco WAAS Central Manager as follows:
If you want to register the Cisco WAAS Express router with an IPv6 address, register it with the following commands:
For a Cisco AppNav-XE router, register with the Cisco WAAS Central Manager as follows:
In the URL for this command, specify the Cisco WAAS Central Manager IP address as indicated. Be sure to include a colon and the port number of 8443.
If a permanent Cisco WAAS license is not installed on the router, you must accept the terms of the evaluation license to continue. The evaluation license is valid for 60 days.
Step 2 Save the running configuration:
If the router device certificate changes after you have registered the router device with the Cisco WAAS Central Manager, you must reimport a matching certificate into the Cisco WAAS Central Manager.
To reimport a router device certificate, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Devices > device-name.
Step 2 Choose Admin > Authentication > Identity Certificate.
The Certificate window appears
Step 3 Import this certificate into the Cisco WAAS Central Manager by selecting one of the following radio buttons that are shown above the tabs:
A router that has already been registered with the Cisco WAAS Central Manager before the system property was enabled needs to be migrated to communicate with the Cisco WAAS Central Manager. To enable this communication, you need to create a new Cisco WAAS Central Manager IOS user so that the ongoing communication uses the same to communicate with the Cisco WAAS Central Manager.
The WAAS Express User Creation Tool window is visible only when the System.WcmIosUser.enable is enabled on the Home > Configure > System Properties > WcmIosUser window.
To create a new Cisco WAAS Central Manager IOS user on the registered Cisco IOS device, follow these steps:
Step 1 From the Cisco WAAS Central Manager menu, choose Home > Admin > Security > WCM Cisco IOS User Creation Tool. The WAAS Express User Creation Tool window appears.
Step 2 Configure the router login credentials by entering the username, password, and enable.
Step 3 Select the Router IP address type: IPv4 or IPv6.
Step 4 Select the Router IP Address entry method.
Step 5 In the IP Address(es) field, enter the Cisco WAAS Express router IP addresses to migrate, separated by commas. The IP address, hostname and status are displayed in the Status table.
You can also upload a CSV file that contains a list of IP addresses to migrate:
a. To upload a list, click the Upload File check box.
b. Click the Choose File button to browse to the file.
Each IP address must be on a separate line.
Step 6 Click the Update button to create a new Cisco WAAS Central Manager IOS user on the router.
If you create a Cisco IOS WCM user, using the Home > Admin > Security > WCM Cisco IOS User Creation Tool by specifying the Cisco IOS username, password and enable:
1. You must manually log in to the Cisco IOS router.
2. Save the running configuration by running the write memory EXEC command.
Note If you do not save the running configuration and reload the device, the Cisco IOS router goes off line in the Cisco WAAS Central Manager.
Consider the following operating guidelines for Cisco WAAS, Cisco ISR-WAAS, and Cisco IOS-XE Interoperability:
After you format the Cisco 4000 Series ISR-router bootflash, you must reload the router to ensure a successful activation of Cisco ISR-WAAS. If you do not reload the Cisco ISR router after formatting the bootflash, you will be unable to activate Cisco ISR-WAAS. For more information on formatting the Cisco 4000 Series ISR router bootflash, see the Configuration Guide for Integrated AppNav/AppNav-XE and ISR-WAAS on Cisco 4000 Series ISRs.
You must complete a new OVA deployment of Cisco WAAS version 6.2.3c or 6.3.1 for this configuration to work successfully. This configuration will not automatically work after an upgrade to Cisco WAAS Version 6.2.3c or 6.3.1 from Cisco WAAS Version 5.x or 6.x.
To ensure a successful WAAS installation of ISR-WAAS and the intrusion detection and prevention system Snort on an ISR router, you must install ISR-WAAS before you install Snort. If you do not follow this installation order, ISR-WAAS will not install and a disk error will be displayed.
When you configure Cisco ISR-WAAS with EZConfig: VirtualPortGroup31, the Cisco WAAS service and router interface, is automatically created, and you can then add or modify specific parameters for it.
Do not add Virtual Routing and Forwarding (VRF) to VirtualPortGroup31, because VRF causes VirtualPortGroup31 to lose its IP address and to disable Cisco AppNav. To re-establish these, you must uninstall and reinstall CIsco ISR-WAAS without VRF.
For more information on VirtualPortGroup31, see the Configuration Guide for Integrated AppNav/AppNav-XE and ISR-WAAS on Cisco 4000 Series ISRs.
This section contains the following topics:
For Cisco WAAS Version 5.5.5 and later, you can configure the Cisco ISR-WAAS hostname. For Cisco WAAS versions earlier than Cisco WAAS Version 5.5.1, Cisco ISR-WAAS receives a system-generated hostname from the Cisco ISR router, which cannot be edited.
Cisco ISR-WAAS is the specific implementation of Cisco vWAAS running in a Cisco IOS-XE Software container (the hypervisor that runs virtualized applications on a Cisco ISR 4000 Series router). Table 10-9 shows the Cisco ISR-WAAS models supported for vWAAS.
Table 10-9 Cisco ISR-WAAS Models Supported for vWAAS
|
|
|
|
---|---|---|---|
Consider the following guidelines for the Cisco ISR-WAAS hostname:
Note To change the Cisco ISR-WAAS profile of an active Cisco ISR-WAAS, you must first uninstall and then reinstall the Cisco ISR-WAAS.
If you only deactivate the existing Cisco ISR-WAAS instance and then change the Cisco ISR-WAAS profile, the Cisco ISR-WAAS will become unstable and the TFO limit will show Zero on the Cisco ISR-WAAS console.
Note For information on how to deploy and register a Cisco ISR-WAAS on the Cisco ISR-4451-X, see the Configuration Guide for Integrated AppNav/AppNav-XE and ISR-WAAS on Cisco ISR-4451-X.
To configure the Cisco ISR-WAAS hostname with the Cisco WAAS Central Manager, follow these steps:
Step 1 Verify that the Cisco ISR-WAAS device is online by choosing Devices > device-name.
The Device Dashboard window appears, and displays information including device status: Pending, Installed, Online, or Inactive.
Note During a fresh OVA deployment of a Cisco ISR-WAAS instance, the Cisco ISR-WAAS default hostname is router-name isr-waas. After the hostname is changed on the vwaas instance, the vwaas instance does not get an update from the router until you change it in the vwaas instance with the Cisco WAAS CLI no-hostname command.
Step 2 To change the Cisco ISR WAAS hostname, choose Devices > ISR WAAS Device > Activation.
The Device Activation window appears, with fields for editing properties of the selected device. The Name field initially has the default Cisco ISR-WAAS hostname, router-hostname-isr-waas.
Step 3 In the Name field of the Activation window, enter the new name of the Cisco ISR-WAAS hostname.
Enter a maximum of 30 alphanumeric characters, including a hyphen. The hostname is case sensitive. Special characters such as $, #, or * are not allowed.
Step 5 To verify that the new hostname is saved, click the Cisco WAAS CLI show hosts command.
To configure the hostname for a Cisco ISR-WAAS using the Cisco ISRO router CLI, follow these steps:
Step 1 To verify that the to verify that the Cisco ISR-WAAS device is online, run the router CLI command show virtual-service list. The show virtual-service list command displays the status for each device, as shown in Figure 10-1. Possible states are Initializing, Installing, Installed, Install Failed, Activating, Activated, Activated Failed, Deactivating, Deactivated, and Error.
Figure 10-1 Sample Output for show virtual-service list Command
Step 2 Log in to the Cisco ISR-WAAS device.
Step 3 Enter Configuration mode and run the router global configuration command hostname hostname to specify a new hostname.
Enter a maximum of 30 alphanumeric characters, including a hyphen. Special characters such as $, #, or * are not allowed.
Step 4 To verify that the new Cisco ISR-WAAS hostname has been saved, run the show hosts command.
To reset a Cisco ISR-WAAS hostname, run the restore factory default command.
Consider the different results generated by the restore factory default command and its parameters:
The restore factory-default preserve basic-config version of the command resets all device configuration and all data back to the manufacture factory status but preserves the Cisco ISR-WAAS hostname, as well as domain name, name server, and network interfaces.
For more information on using the restore factory-default command, see the Cisco Wide Area Application Services Command Reference Guide.