This quick reference page provides a summary of the specifications of the EMC ISM v2 Pod. The EMC ISM v2 pod was designed to support the EMC Information Storage and Management (ISM) course.

The EMC ISM v2 pod is a 100% virtual machine pod consisting of three virtual machines. Linked together through virtual networking, these three virtual machines provide the environment for a student or team to perform the EMC ISM v2 labs.

You may request virtual machine templates for the EMC ISM v2 pod from CSSIA.


Lab Topology

EMC ISM v2 Pod

Virtual Machines

A description of the virtual machines in the EMC ISM v2 Pod is provided in the table below.

Virtual Machine Role
SAN Openfiler Storage Area Network appliance
Linux A Linux client

Storage Requirements

You should budget 6.9 gigabytes for each master pod instance. The datastore containing an ISM v2 pod must be accessible to the VMware host to which it is assigned, as either directly attached local storage or a Storage Area Network (SAN).

Details of the storage requirements for each of the lab virtual machines in the ISM pod are provided in the table below. Some fluctuation in the numbers may occur.

Lab Virtual Machines Initial Master Pod (thin provisioning
Linux 4.2GB
Total Recommended 6.9GB

Virtual Machine Templates

The Center for Systems Security and Information Assurance (CSSIA) provides virtual machine templates to install on the pod.

To request access to the preconfigured virtual machine templates from CSSIA:

  1. Go to the CSSIA Resources page:
  2. Select CSSIA VM Image Sharing Agreement.
  3. Complete and submit your access request by following the instructions on the request form.
  4. CSSIA will provide, via email, password-protected download links. Access to the download links is provided only to customers who are current with their NETLAB+ support contract and are participants in the appropriate partner programs (i.e., Cisco Networking Academy, VMware IT Academy, Red Hat Academy, and/or Palo Alto Networks Cybersecurity Academy).
  5. Once all virtual machines have been downloaded, they can be deployed following the steps in the appropriate pod installation guide. Each virtual machine is deployed individually.