Guest

Cisco Application and Content Networking System (ACNS) Software

Cisco vACNS Software Installation and Configuration Guide

  • Viewing Options

  • PDF (649.6 KB)
  • Feedback

Table Of Contents

Cisco Virtual ACNS Software Installation and Configuration Guide

Contents

Overview

Requirements

Installing the vACNS VM

Configuring vACNS

Displaying Version Information

CLI for vACNS

Related Documentation


Cisco Virtual ACNS Software Installation and Configuration Guide


July 22, 2013

Contents

This document describes how to install and configure virtual ACNS (vACNS) on a VMware virtual machine (VM). The vACNS software is a virtual form of ACNS for setting up and managing content delivery and content caching service.

This document includes the following sections:

Overview

Requirements

Installing the vACNS VM

Configuring vACNS

Displaying Version Information

CLI for vACNS

Related Documentation

Overview

The vACNS software supports managing content delivery and content caching service in a cloud environment where physical ACNS devices cannot usually be deployed. It also follows the VMware ESXi standard as the platform to deploy data center applications and services. Device modes supported by vACNS are Content Engine, Content Distribution Manager and Content Router.

Requirements

This section includes the requirements for vACNS:

Platforms supported:

Cisco UCS server including:

—64-bit CPU hardware from the VMware compatibility list.

—Intel VT (virtualization technology) enabled in the BIOS.

ESX/ESXi version:

Cisco UCS server—VMware ESX/ESXi 4.0+ hypervisor.

VMware vSphere client version 4.x management software.

For virtual ACNS models a datastore block size of minimum 4MB is required in ESXi version 4.1 and other ESXi versions accordingly.

The following VMFS (Virtual Machine File System) limitations apply:

Block Size
Maximum Disk Size

1 MB

256 GB

2 MB

512 GB

4 MB

1024 GB

8 MB

2046 GB


ESXi server datastore memory and disk space per model:

vACNS Model
Memory
Disk
CPUs

VCE 674

4 GB

600 GB

4

VCE 674

8 GB

600 GB

4

VCE 7341

12 GB

900 GB

4


For the vACNS datastore, use local storage on the ESXi server.

The OVA file for the specific virtual ACNS model (all models are available with ACNS version 5.5.31 and later):

vACNS Model
Filename

VCE 674

VCE674_4.ova

VCE 674

VCE674_8.ova

VCE 7341

VCE7341.ova


An ESXi server should have access to a Content Distribution Manager.

Installing the vACNS VM

For installing vACNS using vSphere Client, follow these steps:


Step 1 From the vSphere Client, choose File > Deploy OVF Template. (See Figure 1.)

Figure 1 vACNS—Deploy OVF Template

The Source window appears.

Step 2 Click Browse.

The Open window appears.

Step 3 Navigate to the location of the vACNS OVA file and click Open.

Step 4 Click Next to accept the selected OVA file.

The Name and Location window appears.

Step 5 Enter a name for the vACNS VM, choose the appropriate data center, and then click Next. (See Figure 2.)

Figure 2 vACNS—Name and Data Center Location

The Datastore window appears.

Step 6 Choose a datastore to host the virtual machine and click Next. (See Figure 3.)

Figure 3 vACNS—Datastore

The Disk Format window appears.

Step 7 Select default Thick provisioned format disk option and click Next. (See Figure 4.)

Figure 4 vACNS—Disk Format

The Ready to Complete window appears.

Step 8 Click Finish to complete the installation.

The status window appears while the OVA file is being deployed. (See Figure 5.)

Figure 5 vACNS—Status Window

Step 9 When the deployment is finished, the Deployment Completed Successfully window appears. (See Figure 6.)

Figure 6 vACNS—Completed

Click Close.

Step 10 Select the Deployed vACNS VM and click Power on Virtual Machine.

Step 11 After vACNS boots up, click the Console tab to get access to the device. (See Figure 7.)

Figure 7 vACNS—Console

For vACNS configuration information, see the "Configuring vACNS" section.

Configuring vACNS

Once the vACNS instance is created, configure the following settings:

IP address and netmask

Default gateway and primary interface

Content Distribution Manager address

CMS

To configure vACNS for network connectivity, follow these steps:


Step 1 In the vSphere Client, choose the Console tab and log in to the vACNS console.

The username is admin, and password is default.

Step 2 Configure the IP address and netmask using the interface virtual command:

vACNS(config)# interface virtual 1/0
vACNS(config-if)# ip address 2.1.6.111 255.255.255.0
vACNS(config-if)# exit
 
 

Step 3 Configure the default gateway and primary interface using the ip command:

vACNS(config)# ip default-gateway 2.1.6.1
 
 
vACNS(config)# primary-interface virtual 1/0
 
 

Ping the IP addresses of the default gateway and Content Distribution Manager to verify their reachability.

Step 4 Add the Content Distribution Manager address using the cdm command :

VACNS(config)# cdm ip 2.75.16.100
 
 

Step 5 Enable CMS to register with the Content Distribution Manager using the cms command:

VACNS(config)# cms enable
 
 

Note vACNS registration with the Content Distribution Manager is mandatory before services are enabled.



Displaying Version Information

To display vACNS version information, enter the following commands:

vce7341#show version
Application and Content Networking System Software (ACNS)
Copyright (c) 1999-2013 by Cisco Systems, Inc.
Application and Content Networking System Software Release 5.5.31 (build b1 Jul 15 2013)
Version: vce7341-5.5.31.1
 
 
Compiled 04:38:35 Jul 15 2013 by cnbuild
Compile Time Options: KQ SS
 
 
System was restarted on Mon Jul 22 06:43:26 2013.
The system has been up for 2 hours, 43 minutes, 7 seconds.
 
 
vce7341#show hardware
Application and Content Networking System Software (ACNS)
Copyright (c) 1999-2013 by Cisco Systems, Inc.
Application and Content Networking System Software Release 5.5.31 (build b1 Jul 15 2013)
Version: vce7341-5.5.31.1
 
 
Compiled 04:38:35 Jul 15 2013 by cnbuild
Compile Time Options: KQ SS
 
 
System was restarted on Mon Jul 22 06:43:25 2013.
The system has been up for 2 hours, 43 minutes, 28 seconds.
 
 
CPU 0 is GenuineIntel Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz (rev 12) running at 
2664MHz.
CPU 1 is GenuineIntel Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz (rev 12) running at 
2664MHz.
CPU 2 is GenuineIntel Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz (rev 12) running at 
2664MHz.
CPU 3 is GenuineIntel Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz (rev 12) running at 
2664MHz.
Total 4 CPUs.
12224 Mbytes of Physical memory.
1 CD ROM drive (VMware Virtual IDE CDROM Drive)
2 Virtual interfaces
1 Console interface
 
 
Manufactured As: Cisco Virtual ACNS
 
 
BIOS Information:
Vendor                             : Phoenix Technologies LTD
Version                            : 6.00
Rel. Date                          : 10/13/2009
 
 
  Cookie info:
    SerialNumber: VMware-56
    SerialNumber (raw): 86 77 119 97 114 101 45 53 54 0 0
    TestDate: 7-15-2013
    ExtModel: VCE7341
    ModelNum (raw): 55 0 0 0 1
    HWVersion: 1
    PartNumber: 53 54 55 56 57
    BoardRevision: 1
    ChipRev: 1
    VendID: 0
    CookieVer: 2
    Chksum: 0xfb28
 
 
This command provides information on direct attached SCSI storage arrays only.
 
 
No valid storage-array is detected on this device.
Check 'show disks details' output for additional info.
 
 
List of all disk drives:
disk00: Normal          (IDE disk)                460797MB(450.0GB)
        disk00/04: PHYS-FS       99193MB( 96.9GB) mounted internally
        disk00/04: CDNFS         51200MB( 50.0GB) mounted internally
        disk00/04: MEDIAFS       47993MB( 46.9GB) mounted internally
        System use:              21889MB( 21.4GB)
        FREE:                   336508MB(328.6GB)
disk01: Normal          (IDE disk)                460800MB(450.0GB)
        disk01/00: SYSFS         51199MB( 50.0GB) mounted at /local1
        disk01/01: CFS           51199MB( 50.0GB)
        FREE:                   358400MB(350.0GB)
No NAS share is attached to this device.

CLI for vACNS

Table 1 : CLIs for vACNS

Mode
Command
Description

EXEC

vm clock-sync

Synchronizes the vACNS clock with the host.

Global configuration

interface virtual

Creates a virtual interface on a vACNS device.

EXEC

show interface virtual

Gigabitethernet/Fibrechannel" option modified as "Virtual".

 

show running-config

Interfaces are modified as "Virtual" in show running config.

Global configuration

auto-register enable virtual

Gigabitethernet/Fastethernet" option modified as "Virtual".

 

primary-interface Virtual [slot/port]

Gigabitethernet /Portchannel/Standby " option modified as "Virtual".

 

snmp-server trap-source Virtual [slot/port]

Gigabitethernet/ Portchannel/Standby" option modified as "Virtual".


Table 2 : CLIs not Supported on vACNS

Mode
Command
Description

EXEC

show CDP neighbours

CDP neighbours command is not supported.

Global configuration

interface virtual [slot/port] <ip address> <subnet mask> <secondary address>

Secondary address option is not supported.

 

interface virtual [slot/port] autosense / bandwidth / channel-group / full-duplex / half-duplex / standby

Autosense / bandwidth / channel-group / full-duplex / half-duplex / standby options are not supported.



Note vACNS OVA has default Network Driver as VMXNET3 , this can also be modified to E1000 Driver.


Related Documentation

For additional information on the Cisco ACNS software, see the following documentation:

Cisco ACNS Software Configuration Guide for Locally Managed Deployments, Release 5.5.13

Cisco ACNS Software Configuration Guide for Centrally Managed Deployments, Release 5.5.13

Cisco ACNS Software Command Reference, Release 5.5.13