CCNA Security online course

Install Cisco ACS in a Virtual Machine

Learn how to install Cisco ACS from an ISO in VMware Workstation or ESXi, including VM sizing, ISO attachment, boot steps, verification, and troubleshooting.

Cisco Access Control System (ACS) is an identity and access-control platform used for centralized AAA: Authentication, Authorization, and Accounting. Unlike a conventional application that you install inside Windows or a manually prepared Linux server, ACS is deployed as an appliance-style system. The ACS installer supplies and configures its own appliance environment.

This lesson covers installation from an ISO image in a virtual machine. It does not cover the later work of creating AAA policies, adding network devices, configuring RADIUS or TACACS+, or connecting external identity stores. For background, see What Is Cisco ACS and AAA Explained.

Cisco ACS Installation Overview

The installation process has two distinct phases. First, you install the ACS appliance into a virtual machine. Second, you perform the initial appliance setup and configure ACS services.

1. Obtain the correct Cisco ACS installation ISO for the intended release and platform.
2. Check the release documentation for supported hypervisors, CPU, memory, storage, and network requirements.
3. Create a virtual machine in VMware Workstation or VMware ESXi.
4. Attach the ACS ISO to the VM's virtual CD/DVD drive.
5. Power on the VM and select the standard installation entry in the ACS installer menu.
6. Allow the appliance installer to write to the virtual disk and reboot.
7. Disconnect the ISO if necessary and verify that the VM boots from its installed virtual disk.
8. Complete initial network and administrator configuration from the appliance console.
9. Configure AAA services, identity sources, network-device integration, and access policies as a separate task.

The initial installation normally requires little interaction after the first installer selection. Do not interrupt the VM while the installer is formatting the disk, copying files, configuring the appliance, or rebooting.

Choosing a VMware Platform

VMware ESXi is a bare-metal VMware hypervisor commonly used for enterprise virtual appliance deployments. It is appropriate when ACS must run on managed host infrastructure with controlled storage, networking, and resource allocation.

VMware Workstation is a desktop virtualization product suitable for local training, demonstrations, and security labs. It is a practical choice for a CCNA Security student building an isolated AAA environment on a workstation.

VMware Player may be suitable for a lightweight lab where the product and selected ACS release are compatible. It offers fewer management features than a full enterprise virtualization platform, so verify that it supports the required VM configuration.

Installation Media and Compatibility Preparation

Obtain the ACS ISO image appropriate for the version you intend to deploy. Keep the original image in a controlled, persistent location rather than on temporary storage that may be deleted during the lab or deployment.

When checksum information is available, verify the downloaded file before using it. A checksum comparison can detect an incomplete or altered download. Use the checksum utility appropriate for the operating system hosting the file and compare its result with the value supplied with the approved media.

Example verification process:
1. Obtain the published checksum for the approved ACS ISO.
2. Calculate the checksum of the downloaded file.
3. Compare the two values exactly.
4. Download the image again if the values do not match.

Before creating the VM, review release-specific requirements for:

• Supported VMware products and hypervisor versions.
• Virtual CPU count and memory allocation.
• Virtual disk capacity and disk-controller expectations.
• Virtual NIC requirements and management-network connectivity.
• Host resource availability and any required reservations.

Plan a persistent VM storage location. The host or datastore must have enough free space for the virtual disk, snapshots or operational overhead where applicable, and other VM files. Also plan the IP addressing, DNS or name-resolution needs, gateway, and management access that will be used during initial setup.

Cisco ACS Virtual Installation Prerequisites

Creating the VM in VMware Workstation

The following workflow uses VMware Workstation. The labels can vary slightly between product versions, but the purpose of each choice remains the same.

Start the New Virtual Machine wizard

1. Open VMware Workstation.
2. From the File menu, select New Virtual Machine.
3. Choose the Typical or standard configuration path.
4. Select the option to install the operating system later. This lets you connect the ACS ISO manually after the basic VM definition is created.
5. For the guest operating-system family, select Linux.
6. For the guest profile or version, select CentOS as the closest available profile in the wizard.

Name and locate the VM

Give the VM a recognizable name, such as ACS-Lab or a name that identifies its release and purpose. Select a storage location with adequate persistent capacity. A clear name helps distinguish the appliance from routers, switches, directory servers, and other lab systems.

Create the virtual disk

Configure the virtual hard disk with a capacity of at least 60 GB. A virtual hard disk is the VM-provided storage used by ACS for its appliance installation and data. CPU, memory, NIC count, and any additional storage requirements depend on the ACS release and intended scale, so use the release documentation rather than guessing.

Workstation commonly offers a choice between storing the virtual disk as one large file or splitting it into multiple files:

• Single large file: keeps the disk in one file and can simplify handling on fast, stable local storage. It may be less convenient to copy through file systems with file-size limits.
• Split files: divides the virtual disk into smaller files, which can make movement across file systems or portable storage easier. It also creates more files to track and manage.

The choice is mainly about portability and manageability. Use the option that fits the host file system and how the lab VM will be moved or backed up.

Attaching the ACS ISO

Open the VM hardware customization settings before completing VM creation, or open the VM's settings immediately afterward.

1. Select Customize Hardware.
2. Select the virtual CD/DVD device.
3. Choose Use ISO image file.
4. Browse to the approved Cisco ACS ISO and select it.
5. Enable the option to connect the virtual optical device at power-on.
6. Confirm that the ISO path points to the intended file, not an old image from another lab.

VMware Workstation GUI path:
File > New Virtual Machine
  > Typical
  > Install the operating system later
  > Linux / CentOS
  > Name and storage location
  > Virtual disk: 60 GB or larger
  > Customize Hardware
  > CD/DVD: Use ISO image file
  > Connect at power on

Booting and Installing ACS

1. Finish creating the VM.
2. Power on the virtual machine.
3. Watch the console to confirm that the VM boots from the mounted ISO rather than an empty virtual disk.
4. At the ACS installer boot menu, select the normal or first installation option for a standard installation.
5. Allow the installer to continue. It may perform most of the remaining work without additional prompts.
6. Wait for the installation to complete and for the VM to reboot.

Installation writes the appliance to the virtual hard disk. Avoid powering off, suspending, resetting, or closing the VM while this process is in progress. An interruption can leave the appliance incomplete and require a fresh installation.

VMware Workstation Installation Workflow

Post-Installation Verification and Initial Setup

After the reboot, the console should show the installed ACS appliance rather than the installation menu. The exact prompts and display vary by ACS release, so use the release documentation for the required values and commands.

• Confirm that the VM remains powered on and reaches the expected appliance console state.
• Disconnect the ISO or disable the virtual CD/DVD connection at power-on so the VM does not repeatedly start the installer.
• Verify that the virtual hard disk is still attached and accessible.
• Perform the initial console-based appliance setup.
• Configure management network details and administrative access according to the ACS release documentation.
• Test management connectivity from the planned administration network.

Basic appliance access configuration is not the same as AAA service configuration. After the appliance is reachable, you still need separate configuration for identity stores, network devices, authentication protocols, authorization rules, accounting, and operational policies. Continue with Cisco ACS Setup and Configure Cisco ACS when those tasks are required.

Virtual Machine Resource and Storage Planning

The 60 GB virtual disk minimum is an installation requirement stated for this workflow. It is not a universal sizing recommendation for every ACS release or production workload. Larger deployments may need different resources based on authentication volume, logging, reporting, redundancy, and enabled features.

• CPU: Allocate the supported virtual CPU count and avoid severe host contention.
• Memory: Provide the release-supported amount and reserve adequate host memory for the appliance and VMware overhead.
• NICs: Use the number and network placement required by the selected release and design. At minimum, management connectivity must be planned.
• Disk: Provide at least 60 GB, use persistent storage, and monitor datastore or host free space.
• Host capacity: Reserve enough CPU, memory, and storage performance so installation and boot processes are not interrupted.

Lab and Production Deployment Considerations

Troubleshooting Installation Problems

The VM does not start the ACS installer

• Confirm that the correct ISO is selected in the virtual CD/DVD settings.
• Enable connection of the optical device at power-on.
• Check whether the VM is booting from an empty virtual disk instead of the ISO.
• Restart the VM and use its boot menu or virtual firmware settings to select the optical device.

The installer rejects storage or cannot complete

• Confirm that the virtual disk is at least 60 GB.
• Check free space on the physical host or ESXi datastore.
• Verify that the virtual disk remains attached and that the host storage is accessible.
• Review the selected ACS release's appliance sizing and virtual hardware requirements.

The VM is slow, freezes, or fails during installation

• Check whether other VMs or host applications are consuming CPU or memory.
• Allocate supported resources and avoid severe resource contention.
• Validate the hypervisor version and virtual hardware against ACS compatibility guidance.
• Do not suspend or forcibly power off the VM while the installer is writing to disk.

The appliance reboots but does not reach the expected console

• Disconnect the ISO or change the boot preference so the installed virtual disk is used.
• Inspect the VM console for installation errors.
• Verify that the virtual disk is attached and stored on accessible persistent storage.
• If installation did not finish successfully, correct the resource or media problem and reinstall rather than assuming the appliance is usable.

Exam-Relevant Notes

• ACS is an appliance-style system; selecting Linux and CentOS in Workstation does not mean that CentOS must be installed separately.
• The installation media is an ISO attached through a virtual CD/DVD drive.
• The VMware Workstation workflow uses the typical wizard, defers operating-system installation, selects Linux/CentOS as the closest profile, and attaches the ACS ISO manually.
• The virtual disk must be at least 60 GB for this installation requirement.
• After installation, remove or disconnect the ISO so the appliance boots from its installed disk.
• Installing the appliance is separate from configuring AAA services, identity sources, network devices, and policies.
• ESXi is common for enterprise deployment, while Workstation and compatible Player deployments are generally useful for labs.