Attach an existing volume to a server profile

Prerequisites

  • Minimum required session ID privileges: Server administrator

Attaching an existing volume to a server profile using REST APIs
  1. Obtain the hardware information:

    Get a list of available targets.

    GET /rest/server-profiles/available-targets

    • For an assigned profile, note the fields serverHardwareUri, serverHardwareTypeUri, and enclosureGroupUri for the hardware target of interest.

    • For an unassigned profile, note the serverHardwareTypeUri and enclosureGroupUri for the hardware target of interest.

    • For an empty bay, note the fields serverHardwareTypeUri, enclosureGroupUri, enclosureUri, and enclosureBay.

  2. Obtain the network information to create connections:

    1. Get a list of network connections.

      GET /rest/server-profiles/available-networks?serverHardwareTypeUri={uri}&enclosureGroupUri={uri)

      • Insert serverHardwareTypeUri and enclosureGroupUri from step 1.

      • Note the fields uri and limitedToPorts.

      • If manually selecting the storage targets, note which networks are fabric attach, as indicated via the accessType field.

    2. Get available ports.

      GET /rest/server-profiles/profile-ports?serverHardwareTypeUri={uri}&enclosureGroupUri={uri}

      • Insert serverHardwareTypeUri and enclosureGroupUri from step 1.

      • Note the fields portId, maximumLinkMbps, supportedFcGbps, and capabilities.

  3. Obtain the SAN storage information:

    1. Determine the desired host OS enumeration.

      GET /rest/storage-systems/host-types

    2. Pick an existing available storage volume.

      GET /rest/server-profiles/available-storage-systems?serverHardwareTypeUri={uri}&enclosureGroupUri={uri}

      Note the fields connections, storageSystemUri, and volumeUri for the desired volume to attach to the profile.

  4. If manually selecting the storage targets, obtain them.

    GET {storage system uri}/managedPorts

    Note the fields portWwn, expectedNetworkUri, and actualNetworkUri. Match the expectedNetworkUri with the uri field obtained in step 2a.

  5. Create the server profile with the information from the previous steps.

    POST /rest/server-profiles