Previous Topic: Configure CA Network Automation

Next Topic: How to Configure Software Delivery


Configure the CA Network Automation Server

To run Network Automation scripts from CA Server Automation, configure one CA Network Automation server for use with CA Server Automation.

Follow these steps:

  1. Open the CA Server Automation user interface.
  2. In Management mode, click Administration, Configuration.
  3. In the Network/Storage section, click Network Automation Server.
  4. Click + (Add) and provide the following information:
    Server Name

    Specifies the name or IP address of the CA Network Automation server.

    User Name

    Specifies the user name for the CA Network Automation server.

    Password

    Specifies the password for the CA Network Automation server user.

    Protocol

    Specifies the protocol used to access the CA Network Automation server.

    Default: HTTP

    Port

    Specifies the port number used by the CA Network Automation server.

  5. Click OK.

    The CA Network Automation server is configured.

Storage Provisioning Features

As a System Administrator, you can provision storage in CA Server Automation for virtual and physical servers. To save time, you can create enhanced storage policies and associate them with managed servers. When servers need more space, you can select a different storage policy.

Storage provisioning is supported in Reservation Manager. You also can automate storage provisioning using CA Process Automation connectors.

The following table lists the supported storage vendors, protocols, servers, and features.

Storage Servers

Supported Protocols and Servers

Supported Provisioning Methods in User Interface

NetApp OnCommand

  • SAN-based iSCSI – VMware vCenter ESX, AIX LPAR Virtual I/O, physical and virtual servers (Windows, AIX, Linux, HPUX, Solaris)
  • SAN-based FCP – VMware vCenter ESX, Cisco UCS, physical and virtual servers (Linux)
  • NAS-based CIFS – physical and virtual servers
  • NAS-based NFS – physical, virtual, and VMware vCenter ESX
  • Enhanced storage policies
  • Storage services (NetApp Provisioning Manager)
  • Provisioning policy (NetApp Provisioning Manager)

EMC SMI-S

  • SAN-based iSCSI – VMware vCenter ESX, AIX LPAR Virtual I/O, physical and virtual servers (Windows, AIX, Linux, HPUX, Solaris)
  • SAN-based FCP – VMware vCenter ESX, Cisco UCS, physical, and virtual (Linux)
  • EMC SMI-S
  • Enhanced storage policies

For other storage tasks (discover, resize, move, deprovision), use the cadpmspm CLI.

Note: EMC SMI-S does not support the move option.

Storage Prerequisites

Review the following prerequisites before configuring storage:

How to Configure Storage

Follow these steps to configure storage for CA Server Automation:

  1. Configure your storage servers.
    NetApp OnCommand
    1. Verify that your data center uses NetApp Storage Systems that include NetApp Operations, Provisioning, and Protection Managers.
    2. Create a storage service catalog using the NetApp Provisioning Manager.
    EMC SMI-S

    Verify that EMC storage systems have been configured on the SMI-S server.

  2. If applicable, configure your IBM AIX LPAR iSCSI devices.
    1. Access the Virtual I/O servers.

      Example: chdev -dev iSCSIAdapterDeviceName -attr initiator_name=UNIQUE-ID

    2. Verify that the ID is unique (for RFC 3270).

      Example: iqn.2011-06.com.domain:storage:myMachine.0xa1afc0f.800010EBCD900004.

    3. Verify that Virtual I/O Servers have log in access using ssh.
  3. If applicable, configure your AIX (physical and virtual) iSCSI devices.

    Install the specific iSCSI ODM filesets (download from the EMC site) when connecting to EMC storage arrays.

  4. If applicable, configure your VMware vCenter ESX iSCSI devices.
    1. Configure the iSCSI Adapter.

      On the vSphere Client Configuration tab, click Storage Adapters in the Hardware panel.

    2. For Fiber Channel HBA, use the defaults.
    3. Configure Discovery Addresses for iSCSI Initiators so storage resources on the network are available.
  5. If applicable, configure your Windows (physical) iSCSI devices.
    1. Install Microsoft iSCSI initiator on the remote Windows host for iSCSI storage attachment.

      For Windows 2003, you can download the iSCSI initiator from the Microsoft website under downloads.

    2. Configure the primary DNS suffix for the fully qualified domain name to provision and attach new storage on the server where CA Server Automation is installed.
  6. If applicable, configure your NFS devices.
    Windows (physical or virtual)
    1. Install the NFS Client on the remote Windows host for NFS storage attachment.
    2. For Windows 2008, the NFS client is likely already installed; navigate to Control Panel, Server Manager, Roles, File Services, Add Role Services, Services for Network File System for verification.
  7. If applicable, configure your CIFS devices.
    Windows (physical or virtual)

    For CIFS attachment, if the storage is already mapped and you attach to the same storage with the same CIFS credentials, an error occurs.

    AIX, Linux, HPUX, Solaris (physical or virtual)

    For CIFS attachment on a UNIX platform, enable (or install and configure) the CIFS client package.

  8. Add your storage servers to the user interface.
    1. In the user interface, click the Administration tab, Configuration tab.
    2. In the left panel, go to Storage, Storage Providers, and click + (Add).
    3. Enter the server information.

      Note: The credentials on this dialog are used only to verify whether the storage server exists. This user must have privileges to schedule and provision storage on the storage system (NetApp Power Users and Administrators have these privileges). (The CA Server Automation login credentials are used to connect to storage server for storage provisioning.)

    4. Click Validate to verify the connection.
  9. Define credentials for CA Server Automation that match existing credentials for your storage server.
  10. (Optional) If you are using CA Process Automation connectors for storage management, review the CA Process Automation documentation for prerequisites.