Cisco vWAAS on Cisco CSP 5000-W Series

This chapter describes Cisco vWAAS on the Cisco Cloud Services Platform, 5000-W Series (Cisco CSP 5000-W Series) appliance, and contains the following sections:

About the Cisco CSP 5000-W Series

The Cisco Cloud Services Platform 5000 Series for WAAS (Cisco CSP 5000-W Series) is a Cisco open x86 hardware platform for deployment of Cisco datacenter Network Functions Virtualization (VNFs), and provides the following features:

  • Cisco CSP 5000-W Series contains an embedded KVM CentOS hypervisor, and enables you to monitor and manage the lifecycle of vWAAS on NFVIS.

  • The Cisco CSP 5000-W Series enables you to quickly deploy any Cisco network virtual service through a simple, built-in, native GUI, Cisco WAAS CLI, or Representational State Transfer (REST) API.

  • Cisco vWAAS on the Cisco CSP 5000-W platform supports off-path deployment for WCCP and Cisco AppNav traffic interception. However, the Cisco AppNav I/O Module (Cisco AppNav IOM) is not supported on the Cisco CSP 5000-W platform.

  • Three Cisco CSP 5000-W Models are supported for Cisco vWAAS

    • Cisco CSP 5228-W (12,000 connections): For Cisco vWAAS-12000

    • Cisco CSP 5228-W (50,000 connections): For Cisco vWAAS-50000

    • Cisco CSP 5436-W (150,000 connections): For Cisco vWAAS-150000

    Table 1. Cisco CSP 5000-W: Replaced and Supported Models

    Cisco CSP 5000-W Model

    Connections

    EOS/EOL Cisco WAVE Model Replaced

    Supported Cisco vWAAS Model

    CSP 5228-W

    12,000

    WAVE-7541

    vWAAS-12000

    CSP 5228-W

    50,000

    WAVE-7571

    vWAAS-50000

    CSP 5436-W

    150,000

    WAVE-8541

    vWAAS-150000

    These Cisco CSP 5000-W models replace three End-of-Sale and End-of-Life (EOS and EOL) Cisco WAVE models. The following table shows the corresponding Cisco CSP 5000-W and EOS and EOL Cisco WAVE models, the supported Cisco vWAAS models, and the Cisco UCS model used with CSP 5000-W.

    For more information, see the End-of-Sale and End-of-Life Announcement for the Cisco WAVE 294, 594, 694, 7541, 7571 and 8541.

Cisco CSP 5000-W Hardware Features and Specifications

Consider the following guidelines for using the Cisco CSP 5000-W Series:

  • The dedicated management port on the device is used for CIMC connectivity.

  • The first port on the four-port 1-G (I350) card is used for Cisco NFVIS management.

  • We recommend that you use CSP-SFPs (Intel) to connect the Intel X520-DA2 10-Gbps ports on both sides of end-to-end connections.

The following list shows the specifications for each Cisco CSP 5000-W model used with Cisco vWAAS.

  • Specifications for Cisco CSP 5228-W for Cisco vWAAS 12000:

    • CPU: 16 core

    • CPU speed: 2.2. GHz

    • Connections: 12,000

    • Memory: 52 GB

    • Storage: 1.5 TB

    • Network Interface Card and RAID:

      • PCIe Slot 1: Intel X520-DA2 10-Gbps 2-port NIC (2x10-GB fiber interfaces)

        RAID:

      • PCIe Slot 2: Intel i350 Quad Port 1-GB Adapter

    • RAID: Cisco 12-G Modular RAID controller with 2-GB cache, RAID 10

    • Hardware Platform: Cisco UCS-220-M5

  • Specifications for Cisco CSP 5228-W for Cisco vWAAS 50000:

    • CPU: 20 core

    • CPU speed: 2.2 GHZ

    • Connections: 50,000

    • Memory: 76 GB

    • Storage: 2.3 TB

    • Network Interface Card:

      • PCIe Slot 1: Intel X520-DA2 10-Gbps 2-port NIC (2x10-GB fiber interfaces)

      • PCIe Slot 2: Intel i350 Quad Port 1-GB Adapter

    • RAID: Cisco 12-G Modular RAID controller with 2-GB cache, RAID 10

    • Hardware Platform: Cisco UCS-220-M5

  • Specifications for Cisco CSP 5436-W for Cisco vWAAS-150000:

    • CPU: 28 core

    • CPU speed: 3.0 GHz

    • Connections: 150,000

    • Memory: 100 GB

    • Storage: 4.5 TB

    • Network Interface Card:

      • PCIe Slot 1: Intel X520-DA2 10-Gbps 2-port NIC (2x10-GB fiber interfaces)

      • PCIe Slot 2: Intel i350 Quad Port 1-GB Adapter

    • RAID: Cisco 12-G Modular RAID controller with 2GB cache, RAID 10

    • Hardware Platform: Cisco UCS-240-M5

For more information on RAID configuration, see the Cisco UCS Servers RAID Guide.

Cisco vWAAS on Cisco CSP 5000-W with Akamai Connect

Consider the following guidelines for Cisco vWAAS on Cisco CSP 5000-W with Akamai Connect:

  • Cisco CSP 5000-W devices have fixed resources. Therefore the memory on each device remains the same with or without Akamai Connect enabled.

  • As shown in the following table, a fourth disk is required for Cisco vWAAS on Cisco CSP 5000-W with Akamai Connect.

Table 2. System Requirements for Cisco vWAAS on Cisco CSP 5000-W with Akamai Connect

Cisco CSP 5000-W Model

Supported Cisco vWAAS Model

Memory Requirement without Akamai Connect

Fourth Disk Required When Akamai Connect is Enabled

CSP 5228-W

vWAAS-12000

18 GB

750 GB

CSP 5228-W

vWAAS-50000

48 GB

850 GB

CSP 5436-W

vWAAS-150000

96 GB

1500 GB

For more information, see the chapter "Cisco vWAAS with Akamai Connect."

Deploying, Registering, and Configuring Cisco vWAAS on Cisco CSP 5000-W

This section contains the following topics:

Workflow for Deploying, Registering, and Configuring Cisco vWAAS on Cisco CSP 5000-W

The following table shows the workflow for deploying, registering, and configuring Cisco vWAAS on Cisco CSP 5000-W.

Table 3. Workflow for Deploy, Registering, and Configuring Cisco vWAAS on Cisco CSP 5000-W

Task

Description or Section

1. Install the Cisco vWAAS on Cisco CSP 5000-W.

Installing Cisco vWAAS on a Cisco CSP 5000-W Device.

2. Register the Cisco CSP 5000-W device with the Cisco WAAS Central Manager.

Registering or Deregistering a Cisco CSP 5000-W Device with the Cisco WAAS Central Manager

3. Enable Akamai Connect.

Cisco vWAAS with Akamai Connect

4. Check Accelerator status.

To confirm that the operational status of accelerators is Running, run the show accelerator EXEC command.

5. Configure WCCP traffic interception.

The "Configuring Traffic Interception" chapter of the Cisco Wide Area Application Services Configuration Guide for your Cisco WAAS version.

Installing Cisco vWAAS on a Cisco CSP 5000-W Device

Cisco CSP 5000-W is a bundled solution and is shipped with a pre-installed image.

To install any of the three supported Cisco vWAAS models on the supported Cisco CSP 5000-W device, run the following show EXEC commands to verify that all hardware details for the CSP 5000-W device are displayed correctly.

  • show version: Verifies that the Cisco WAAS version is Version 6.4.3a or later.

  • show tfo detail: Verifies the number of Transport Flow Optimization (TFO) connections depending on the Cisco vWAAS model.

  • show hardware: Validates the CPU and memory depending on the Cisco vWAAS model.

  • show inventory: Validates the PID depending on the Cisco vWAAS model.

Configuring Port Channel and Standby Interfaces

This section contains the following topics:

Configuring a Port Channel Interface

Consider the following guidelines for configuring a port channel interface:

  • To provide increased bandwidth and redundancy, a port channel bundles individual interfaces within these NIC modules:

    • Virtual 1/0 and 2/0: 10 G Ethernet interface

    • Virtual 3/0 and 3/1: 10 G fiber interface

      For fiber connectivity, Intel SFP+ is required for connecting the Intel X520-DA2 10-Gbps two-port NIC (2x10-GB Fiber interfaces).

    • Virtual 4/0, 4/1, and 4/2: 1 G Ethernet interface

  • Port channeling load balances traffic across physical interfaces. The port channel stays operational as long as at least one physical interface within the port channel is operational.

  • You create a port channel by bundling compatible interfaces. You can configure and run either static port channels or ports channels running the Link Aggregation Control Protocol (LACP). Standby provides aggregation of several physical links into a logical one, but only for the purpose of furnishing fault-tolerance.

  • The following CLI commands are used in the context of port channels:

    • To create a port channel:

      CSP-APPLIANCE#config
CSP-APPLIANCE(config)#interface portchannel 1
CSP-APPLIANCE(config-if)#ip address <addr> <mask>
CSP-APPLIANCE(config-if)#exit

    • To remove a port channel:

      CSP-APPLIANCE#config
CSP-APPLIANCE(config)#interface portchannel 1
CSP-APPLIANCE(config-if)#no ip address <addr> <mask>
CSP-APPLIANCE(config-if)#exit
CSP-APPLIANCE(config)#no interface portchannel 1

    • To configure a port channel group for a network interface, run the (config-if) channel-group command: 

      CSP-APPLIANCE(config)#interface GigabitEthernet 1/0
CSP-APPLIANCE(config-if)#channel-group 1

    • To show the running configuration:

      interface PortChannel 1
  ip address <addr> <netmask>
  exit
!
interface Virtual 4/0
  channel-group 1
  exit
interface Virtual 4/1
  channel-group 1
  exit
interface Virtual 4/2
  channel-group 1
  exit

      The following figure shows annotated output for the show running-config interface command: 

      NO-HOSTNAME# show running-config interface
interface Virtual 1/0
ip address 1.1.1.1 255.255.255.0
exit                                 Onboard 10G         These are the
interface Virtual 2/0                interfaces (X550)   onboard interfaces.
ip address 2.2.2.2 255.255.255.0
exit
interface Virtual 3/0                10G interfaces in   This card goes in PCI
ip address 3.3.3.3 255.255.255.0     PCI slot (X250)     Slot 1 for both CSP-
exit                                                     5228 and CSP-5436
interface Virtual 3/1
ip address 4.4.4.4 255.255.255.0
exit
interface Virtual 4/0
ip address 5.5.5.5.5 255.255.255.0
exit
interface Virtual 4/1                3 * 1G interfaces  This card goes in Slot
ip address 6.6.6.6. 255.255.255.0    (I350)             2 for CSP-5228
exit                                                    and Slot 4 for CSP-5436.
interface Virtual 4/2
ip address 7.7.7.7 255.255.255.0

    • To show port channel or standby interface statistics:

      CSP-5228#sh interface standby 1
Interface Standby 1 (2 member interface(s)):
Virtual 3/0 (active) (primary) (in use)
Virtual 3/2 (active)
---------------------
Ethernet Address                 : 52:54:00:42:4f:a6
Internet Address                 : 2.93.82.20
Netmask                          : 255.255.255.240
IPv6 Enabled                     : No
Admin State                      : Up
Operation State                  : Running
Maximum Transfer Unit Size       : 1500
Input Errors                     : 0
Input Packets Dropped            : 0
Packets Received                 : 94939473
Output Errors                    : 0
Output Packets Dropped           : 0
Load Interval                    : 30
Input Throughput                 : 0 bits/sec, 0 packets/sec
Output Throughput                : 0 bits/sec, 0 packets/sec
Packets Sent                     : 93430587
Interception Statistics
CSP-5228#
CSP-5228#sh interface portChannel 1
Interface PortChannel 1 (3 member interface(s)):
Virtual 3/0 (active)
Virtual 3/1 (active)
Virtual 3/2 (active)
---------------------
Ethernet Address                 : 52:54:00:42:4f:aa
Internet Address                 : 22.22.22.2
Netmask                          : 255.255.255.0
IPv6 Enabled : No
Admin State : Up
Operation State : Down
Maximum Transfer Unit Size       : 1500
Input Errors                     : 0
Input Packets Dropped            : 0
Packets Received                 : 21568
Output Errors                    : 0
Output Packets Dropped           : 0
Load Interval                    : 30
Input Throughput                 : 2290669644 bits/sec, 159 packets/sec
Output Throughput                : 2290649224 bits/sec, 0 packets/sec
Packets Sent                     : 41
CSP-5228#

    • To configure an interface to be a standby for another interface, run the (config-if) standby command: 

      CSP-APPLIANCE#configure
CSP-APPLIANCE#interface standby 1
CSP-APPLIANCE(config-if)#

Configuring a Standby Interface

You can create two port channel groups and use them as the active and backup members of a standby group. Consider the following guidelines for configuring a standby interface:

  • The standby interface has two modes:

    • Active-backup mode: Implements the standby interface and provides fault tolerance. Only one server interface in the bond is active. A different server interface becomes active only if the active server interface fails.

    • SRC-DST-IP-PORT mode: Provides load balancing and fault tolerance. In this mode, all the frames between the same source and the same destination use the same link.

  • The following CLI commands are used in the context of a standby interface:

    • To create a standby interface:

      CSP-APPLIANCE#config
CSP-APPLIANCE(config)#interface Standby 1
CSP-APPLIANCE(config-if)#ip address <addr> <mask>
CSP-APPLIANCE(config-if)#exit

    • To remove a standby interface:

      CSP-APPLIANCE#config
CSP-APPLIANCE(config)#interface Standby 1
CSP-APPLIANCE(config-if)#no ip address <addr> <mask>
CSP-APPLIANCE(config-if)#exit
CSP-APPLIANCE(config)#no interface Standby 1

    • To show the running configuration:

      interface Standby 1
  ip address <addr> <netmask>
  exit
!
interface Virtual 1/0
  standby 1 primary
  exit
interface Virtual 2/0
  standby 1
  exit

    • To show port channel or standby interface statistics:

      CSP-5228#sh interface standby 1
Interface Standby 1 (2 member interface(s)):
Virtual 3/0 (active) (primary) (in use)
Virtual 3/2 (active)
---------------------
Ethernet Address               : 52:54:00:42:4f:a6
Internet Address               : 2.93.82.20
Netmask                        : 255.255.255.240
IPv6 Enabled                   : No
Admin State                    : Up
Operation State                : Running
Maximum Transfer Unit Size     : 1500
Input Errors                   : 0
Input Packets Dropped          : 0
Packets Received               : 94939473
Output Errors                  : 0
Output Packets Dropped         : 0
Load Interval                  : 30
Input Throughput               : 0 bits/sec, 0 packets/sec
Output Throughput              : 0 bits/sec, 0 packets/sec
Packets Sent                   : 93430587
Interception Statistics
CSP-5228#
CSP-5228#sh interface portChannel 1
Interface PortChannel 1 (3 member interface(s)):
Virtual 3/0 (active)
Virtual 3/1 (active)
Virtual 3/2 (active)
---------------------
Ethernet Address               : 52:54:00:42:4f:aa
Internet Address               : 22.22.22.2
Netmask                        : 255.255.255.0
IPv6 Enabled                   : No
Admin State                    : Up
Operation State                : Down
Maximum Transfer Unit Size     : 1500
Input Errors                   : 0
Input Packets Dropped          : 0
Packets Received               : 21568
Output Errors                  : 0
Output Packets Dropped         : 0
Load Interval                  : 30
Input Throughput              : 2290669644 bits/sec, 159 packets/sec
Output Throughput             : 2290649224 bits/sec, 0 packets/sec
Packets Sent                  : 41
CSP-5228#

Registering or Deregistering a Cisco CSP 5000-W Device with the Cisco WAAS Central Manager

This section contains the following topics:

Registering a Cisco CSP 5000-W Device with the Cisco WAAS Central Manager

Procedure

Step 1

At the Cisco datacenter CSP 5000-W CLI, enter the Cisco WAAS Central Manager IP address, for example: 10.78.99.141:

DC-CSP-WAE(config)#central-manager address 10.78.99.141
DC-CSP-WAE(config)#
DC-CSP-WAE(config)#end
DC-CSP-WAE#show running-config | i central central-manager address 10.78.99.141
Note 

The IP address configured in the Cisco NFVIS management port cannot be accessed from the Cisco WAAS Central Manager.
Step 2

To register the Cisco CSP 5000-W device, run the cms command : 

DC-CSP-WAE(config)#cms enable
Registering WAAS Application Engine...
Sending device registration request to Central Manager with address 10.78.99.141
Please wait, initializing CMS tables
Successfully initialized CMS tables
Registration complete.
Step 3

To preserve the running configuration, run the copy running-config startup-config command.

Note 

If you do not run the copy running-config startup-config command, the management service will not be started on reload, and the Cisco WAAS Central Manager will show the node as Offline.

Step 4

After the device is registered, it is displayed in the Cisco WAAS Central Manager as OE-CSP.

Figure 1. Cisco OE-CSP Displayed in the WAAS Central Manager Device Listings Window
Step 5

To view the Cisco CSP 5000-W device in the dashboard, choose Devices > device-name > Dashboard.

The Device Dashboard window is displayed. Information displayed for the device includes device model, IP address, interception method, and device-specific charts.

Step 6

You can also use the Cisco CSP 5000-W CLI to view device information:

DC-CSP-WAE#show cms info
Device registration information :
Device Id                              = 1769435
Device registered as                   = WAAS Application Engine
Current WAAS Central Manager           = 10.78.99.142
Registered with WAAS Central Manager   = 10.78.99.142
Status                                 = Online
Time of last config-sync               = Fri Jun 3 14:41:26 2018
CMS services information :
Service cms_ce is running

Deregistering a Cisco CSP 5000-W Device

Procedure

Step 1

At the Cisco datacenter CSP 5000-W CLI, use the cms deregister command to deregister the device:

DC-CSP-WAE#cms deregister

Deregistering WAE device from Central Manager will result in loss of data on encrypted
file systems.

If secure store is initialized and open, clear secure store.

If encrypted MAPI is enabled, windows-domain encryption-service identities will be
disabled. The passwords must be re-entered again the next time the WAE joins
a central manager.

Do you really want to continue (yes|no) [no]?yes
Step 2

To initiate the deregistering process, click yes. The system displays the following status messages: 

Disabling management service.
management services are already disabled.
Sending de-registration request to CM
SSMGR RETURNING: 7 (Success)
Removing cms database tables.
Re-initializing SSL managed store and restarting SSL accelerator.
Deregistration complete. Save current cli configuration using 'copy running-config
startup-config' command because CMS service has been disabled.
Step 3

To preserve the running configuration, run the copy running-config startup-config command.

Note 

If you do not run the copy running-config startup-config command, the management service will not be started on reload, and the Cisco WAAS Central Manager will show the node as Offline.

CLI Commands Used with Cisco vWAAS on Cisco CSP 5000-W

The following table shows the CLI commands used with Cisco vWAAS on Cisco CSP 5000-W.

Table 4. CLI Commands used with Cisco vWAAS on Cisco CSP 5000-W

Mode

Command

Description

Global Configuration

(config) interface PortChannel

Configures a port-channel interface.

Interface Configuration

(config-if) channel-group

Configures the port channel group for a network interface.

privileged-level EXEC

copy sysreport disk

Cisco CSP 5000-W logs will be part of the sysreport generation for debugging.

reload

Restarts the Cisco vWAAS VM.

show hardware

Validates the CPU and memory depending on the Cisco vWAAS model.

show inventory

Validates the PID depending on the Cisco vWAAS model.

show running-config interface

Displays a Cisco WAAS device current running configuration on the terminal.

show tfo detail

Verifies the number of TFO connections depending on the Cisco vWAAS model.

user-level EXEC and privileged-level EXEC

show version

Verifies that the Cisco WAAS version is Cisco WAAS Version 6.4.3a or later.

privileged-level EXEC

shutdown

Powers off the Cisco CSP 5000-W device.

Upgrade and Downgrade Guidelines for Cisco vWAAS on Cisco CSP 5000-W

Consider the following upgrade and downgrade guidelines for Cisco vWAAS on Cisco CSP 5000-W:

  • Upgrade is supported for the Cisco vWAAS bundled image in Cisco WAAS Version 6.4.3a and later, and the associated Cisco NFVIS version used with Cisco WAAS.

  • When there is more than one device type present at the Device Group level, the Cisco WAAS Central Manager supports upgrade and downgrade that is supported for each device type.

  • Downgrade is not supported for Cisco vWAAS for Cisco WAAS versions earlier than Cisco WAAS 6.4.3a.


Note

Cisco CSP 5000-W devices run with specific Cisco vWAAS and Cisco NFVIS versions. We recommend that you upgrade Cisco vWAAS and Cisco NFVIS together; do not upgrade each of these separately. For more information, see "Upgrade Guideliknes for Cisco Enterprise NFVIS" in the chapter “Cisco vWAAS with Cisco Enterprise NFVIS."