Installation and Configuration Guide for Cisco WAAS NAM Virtual Blade
Installing NAM Virtual Blade Software
Downloads: This chapterpdf (PDF - 735.0KB) The complete bookPDF (PDF - 2.7MB) | Feedback

Installing NAM Virtual Blade Software

Table Of Contents

Installing NAM Virtual Blade Software

Installing NAM Software on a WAE Device

Enabling Virtual Blade on the WAE

Configuring the IP Address on the WAE

Setting Up the NAM Virtual Blade on the WAE

Copying the Cisco NAM Virtual Blade Software Image

Configuring Virtual Blade Parameters

Booting the NAM Virtual Blade

Initial NAM Configuration


Installing NAM Virtual Blade Software


This chapter provides information about installing NAM 4.1 virtual blade software on a supported WAAS device. NAM 4.1 virtual blade software supports the following WAAS appliances:

WAVE-574

WAE-674


Note Installing the CIsco NAM Virtual Blade software using Central Manager requires WAAS version 4.1.3 on both the Central Manager and the Managed WAAS device.


Installing NAM Software on a WAE Device

This section describes how to install Cisco NAM Virtual Blade software on a WAE device. If you are installing Cisco NAM Virtual Blade software on a previously purchased WAE device on which Cisco NAM Virtual Blade software is supported, you will need to use the Cisco NAM Virtual Blade software installation files from the Cisco NAM Virtual Blade Software, Recovery DVD.

This section includes the following:

Enabling Virtual Blade on the WAE

Configuring the IP Address on the WAE

Setting Up the NAM Virtual Blade on the WAE

Enabling Virtual Blade on the WAE

This section describes how to set up the WAE to support Virtual Blade. You can skip this step if the WAE device has already been setup to support VB. You can use either CLI commands or the Central Manager (CM) GUI windows.

Using the CLI

To enable a Virtual Blade on a WAE using the CLI, do the following steps:


Step 1 Log in to the WAE serial console.

Step 2 Enter the following command:

setup

Step 3 Check the Setup Menu and confirm the following:

Device mode is Application-Accelerator

Management interface is set to GigabitEthernet1/0

You can type setup at any time and accept the defaults or change them, and choose to save or not save at the end of the session.

Step 4 Enable the virtual-blade feature using the following commands:


Note This procedure reformats the disk and requires a reload.


conf t

virtual-blade enable

exit

wr mem

reload

After the login prompt returns, you are ready to log in and set up the Virtual Blade.


For details on configuring a virtual blade, see Chapter 14, Configuring Virtual Blades in the Cisco Wide Area Application Services Configuration Guide.

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v411/configuration/guide
/virtual.html

Using the GUI

To enable a Virtual Blade on a WAE device using the Central Manager GUI, do the following steps:


Step 1 Log in to the WAAS Central Manger GUI.

Step 2 In the Action menu, click Manage Devices as shown in Figure 2-1.

Figure 2-1 WAAS Central Manager GUI - Manage Devices

Step 3 Confirm that the mode is set to Application Accelerator and that the WAE is addressable as shown in Figure 2-2, seen when accessing the Manage Devices tab.

Figure 2-2 Checking Mode Setting


Note Click on the cube beside the device name to edit the device on which you want to install the Cisco NAM Virtual Blade software.


Enable the Virtual Blade feature on the selected device by clicking Admin > Virtualization -- General Settings, click the Enable Virtualization check box, then click Submit.

Figure 2-3 General Settings Window

You are prompted to confirm that you want to modify general settings. Doing so will cause the WAE to reboot. After the reboot, the WAE will have a disk partition and other resources reserved for virtual blade use.


Configuring the IP Address on the WAE

This section describes how to set up the IP address of the WAE. The management interface for the WAE and the Virtual Blade are the same.


Note If you have already configured the WAE with an IP address, skip these steps.


Using the CLI

To configure the IP address on a WAE device using the CLI, do the following steps:


Step 1 Log in to the WAE Serial console.

Step 2 Check to see if the first Ethernet interface is configured with an IP address using the following command:

show interface GigabitEthernet 1/0

WAAS# show int gigabitEthernet 1/0
Type:Ethernet
Ethernet address:00:1A:64:D4:E4:94
Internet address:172.20.122.42
Broadcast address:172.20.122.127
Netmask:255.255.255.128
Maximum Transfer Unit Size:1500
Metric:1
Packets Received: 531150131
Input Errors: 0
Input Packets Dropped: 4976
Input Packets Overruns: 0
Input Packets Frames: 0
Packet Sent: 7709986
Output Errors: 0
Output Packets Dropped: 0
Output Packets Overruns: 0
Output Packets Carrier: 0
Output Queue Length:1000
Collisions: 0
Interrupts:16
Flags:UP BROADCAST RUNNING PROMISC MULTICAST
Mode: autoselect, full-duplex, 1000baseTX 
WAAS#

If an IP address is not configured, continue with the Step 3. Otherwise, skip to the section Setting Up the NAM Virtual Blade on the WAE

Step 3 Enter the following commands to configure the IP address:

conf t

int GigabitEthernet 1/0

     ip address <IP-Address> <Subnet-Mask>

(Enter the IP address and subnet mask of the WAE device.)

     no shut

     exit

ip default-gateway <Gateway-IP-Address>

(Enter the IP address of the Gateway for the WAE device.)

exit


Using the WAAS CM GUI

To configure the IP address on a WAE device using the Central Manager GUI, do the following steps:


Step 1 Log in to the device on which the Virtual Blade software is being installed.

Step 2 Select Configure > Network > Network Interfaces window and configure GigabitEthernet 1/0 as the Primary Interface.

Step 3 Click the Edit icon.

Step 4 Configure GigabitEthernet 1/0 with the desired IP Address and Gateway, then click Submit.

Figure 2-4 shows the Network Interface window after entering the required IP address information for the WAE device.

Figure 2-4 WAE Device - Network Interfaces


Setting Up the NAM Virtual Blade on the WAE

At this point, you are ready to set up the blade parameters and load the NAM 4.1 software image onto the WAE disk. Use telnet and/or the console connection to log in, and open two session windows.


Note We recommend that you open two login sessions on the WAAS console. This enables you to use one for the Virtual Blade session and the other session to set the Virtual Blade parameters and control the blade.


Copying the Cisco NAM Virtual Blade Software Image

Configuring Virtual Blade Parameters

Copying the Cisco NAM Virtual Blade Software Image

To copy the NAM image onto the WAE, use a command like the following:

copy ftp disk <FTP-IP> <FTP-PATH> <NAM-ISO-FILE> /local1/vbs/appHelper.iso

Where:

FTP-PATH is the path to the NAM-ISO-FILE that contains the NAM image

NAM-ISO-FILE is the name of the file on the FTP server that contains the NAM image

/local1/vbs/appHelper.iso is the path and filename to the software image.

Configuring Virtual Blade Parameters

This section describes how to set up the Virtual Blade parameters. The minimum disk space required is 40 GB, minimum memory is 1 GB, as shown in procedure steps below. The total available disk space and memory might vary from one device to another, and devices with higher capacity can be used. The WAE initially boots from the .iso (cd-rom), but after installation is reconfigured to boot disk.

Using the CLI

To configure Virtual Blade parameters using the CLI, do the following steps:


Step 1 Log in to the WAE Serial console, and enter the following commands.

conf t

virtual-blade 1 boot cd-image disk /local1/vbs/appHelper.iso

virtual-blade 1 disk 40

virtual-blade 1 memory 1024

virtual-blade 1 interface 1 bridge GigabitEthernet 1/0

virtual-blade 1 description "NAM Virtual Blade"

virtual-blade 1 device cpu qemu64

virtual-blade 1 device nic e1000

virtual-blade 1 device disk ide

virtual-blade 1 boot from cd-rom

exit

Using CM GUI

To configure the VB parameters on a WAE device using the Central Manager GUI, do the following steps:


Step 1 Log in to the device on which the Virtual Blade software is being installed.

Step 2 Navigate to the Admin > Virtualization > Virtual Blades window and click Create.

The Virtual Blade Parameters window displays as shown in Figure 2-5.

Figure 2-5 Virtual Blade Parameters

Step 3 Enter the Virtual Blade parameters as shown in Table 2-1.

Table 2-1 Virtual Blade Parameters for WAE 

Field
Value and Usage Notes

Blade Number

1

Description

NAM Virtual Blade

AutoStart

 

Boot From

cd-rom

CD Image

disk and path to bootfile

Floppy Image

 

Disk Space

40

Memory

1024

Disk Emulation

IDE

NIC Emulation

e1000

CPU Emulation

qemu64


Step 4 Add GigabitEthernet 1/0 as a bridged interface and generate a MAC address for it.

Step 5 Log into the WAE and enter the following commands:

conf t

virtual-blade 1 device nic e1000

virtual-blade 1 boot from cd-rom


Booting the NAM Virtual Blade

This section describes how to boot the NAM Virtual Blade and set up its IP address to enable you to begin to use the NAM GUI. Use telnet and/or the console connection to log in, and open two session windows.


Note We recommend that you open two login sessions into the WAE. This enables you to use one session to issue commands on the WAE and the other to session into the NAM VB.



Step 1 Start two telnet sessions into the WAE.

Step 2 In one session, start the NAM VB using the following command:

virtual-blade 1 start


Note If a license issue occurs, see the section Virtual Blade Licensing to fix the issue, then retry.


Step 3 To start the VB from the CM GUI, click Admin > Virtualization > Actions.

Step 4 In the second session window, session into the NAM VB with the following command:

virtual-blade 1 session

The virtual-blade start command from Step #2 brings up the NAM boothelper menu on the NAM VB console session after a few minutes. as shown below:


=====================================================
Cisco Systems, Inc.
Network Analysis Module (NAM) helper utility
Version 4.1(1) 

-----
Main menu
1 - Download application image and write to HDD
2 - Download application image and reformat HDD
3 - Install application image from CD
4 - Display software versions
5 - Reset application image CLI passwords to default
6 - Change file transfer method (currently ftp/http)
7 - Send Ping
n - Configure network
h - Exit and shutdown Services Engine

Selection [1234567nh]: 

Step 5 Enter 3 to choose Install application image from CD and follow the prompts.

The NAM image filename is appHelpper.iso.

Step 6 After the NAM application image is installed on the disk, shutdown the NAM VB. Enter h to Exit and shutdown Service Engine.

It is important to shutdown the NAM VB so you can change the VB configuration to boot from disk so you boot the application image.

Step 7 Return to the first session, and stop the NAM VB with the following command:

virtual-blade 1 stop

Step 8 From the CM GUI, click Admin > Virtualization > Actions.

Step 9 Return to the first session and after the WAE console prompt returns, enter the following commands to configure the NAM VB to boot from disk:

conf t

virtual-blade 1 boot from disk

exit

wr mem

Step 10 Enter the following commands to boot the NAM application image, then wait for the NAM login prompt.

virtual-blade 1 start

virtual-blade 1 session


Initial NAM Configuration

This section describes the initial configuration of the NAM VB using the NAM CLI.


Step 1 Log in to the NAM console as user root.

The default password for user root is root.

Step 2 Enter the following CLI commands to enable IP access.

ip address <IP-Address> <Subnet-Mask>

ip gateway <Gateway-IP-Address>

ip domain <Domain-name>

ip nameserver <Nameserver-IP-Address>

ip http server enable

(Enter the web username and password)

exsession on

Step 3 Connect to the NAM IP Address in the URL field of your web browser, then login using the username and password you have selected.