Table Of Contents
Cisco Virtual ACNS Software Installation and Configuration Guide
July 22, 2013
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:
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.
This section includes the requirements for vACNS:
–Cisco UCS server including:
—64-bit CPU hardware from the VMware compatibility list.
—Intel VT (virtualization technology) enabled in the BIOS.
–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:
•ESXi server datastore memory and disk space per model:
•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):
•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
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.
Once the vACNS instance is created, configure the following settings:
•IP address and netmask
•Default gateway and primary interface
•Content Distribution Manager address
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/0vACNS(config-if)# ip address 184.108.40.206 255.255.255.0vACNS(config-if)# exit
Step 3 Configure the default gateway and primary interface using the ip command:vACNS(config)# ip default-gateway 220.127.116.11vACNS(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 18.104.22.168
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 versionApplication 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-22.214.171.124Compiled 04:38:35 Jul 15 2013 by cnbuildCompile Time Options: KQ SSSystem was restarted on Mon Jul 22 06:43:26 2013.The system has been up for 2 hours, 43 minutes, 7 seconds.vce7341#show hardwareApplication 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-126.96.36.199Compiled 04:38:35 Jul 15 2013 by cnbuildCompile Time Options: KQ SSSystem 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 interfaces1 Console interfaceManufactured As: Cisco Virtual ACNSBIOS Information:Vendor : Phoenix Technologies LTDVersion : 6.00Rel. Date : 10/13/2009Cookie info:SerialNumber: VMware-56SerialNumber (raw): 86 77 119 97 114 101 45 53 54 0 0TestDate: 7-15-2013ExtModel: VCE7341ModelNum (raw): 55 0 0 0 1HWVersion: 1PartNumber: 53 54 55 56 57BoardRevision: 1ChipRev: 1VendID: 0CookieVer: 2Chksum: 0xfb28This 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 internallydisk00/04: CDNFS 51200MB( 50.0GB) mounted internallydisk00/04: MEDIAFS 47993MB( 46.9GB) mounted internallySystem use: 21889MB( 21.4GB)FREE: 336508MB(328.6GB)disk01: Normal (IDE disk) 460800MB(450.0GB)disk01/00: SYSFS 51199MB( 50.0GB) mounted at /local1disk01/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
Table 2 : CLIs not Supported on vACNS
Note vACNS OVA has default Network Driver as VMXNET3 , this can also be modified to E1000 Driver.
For additional information on the Cisco ACNS software, see the following documentation:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2010-2013 Cisco Systems, Inc. All rights reserved.