Service template prerequisites

Ops Center Automator User Guide
Version
11.0.x
Audience
anonymous
Part Number
MK-99AUT001-22

The following shows the software and setup prerequisites for each of the service templates.

Allocate Fabric Aware Volumes with Configuration Manager

Software prequisites

  • Ops Center API Configuration Manager v10.7.0-00 or later
  • When integrating with Cisco FC switches: Data Center Network Manager (DCNM) 7.1, 11.5
  • When integrating with Brocade FC switches: Fabric OS (FOS) 8.2.2d, 8.2.3a, 8.2.3c1, 9.0.1b, 9.0.1e1, 9.1.0b

Setup prerequisites

  • Register the LDEV ID and Host Group ID used by this service to the same resource group or virtual storage machine.
  • Create a web service connection for the Ops Center API Configuration Manager that uses the same credentials for each storage system managed by Ops Center API Configuration Manager.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
  • Create a web service connection for DCNM or FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For DCNM, verify that the registered user is assigned the network-admin role.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
  • For user-defined roles, a role with both of the following permissions is required:
    • Fabric=O(Observe) or OM(Observe and Modify)
    • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.

Allocate Volumes with Clone/Snapshot

Software prequisites

  • Ops Center API Configuration Manager v10.7.0-00 or later
  • Network Management software:
    • Brocade Network Advisor (BNA) 12.4, 14.0, 14.2, 14.4

      or

    • Data Center Network Manager (DCNM) 7.1, 11.5

Setup prerequisites

  • Register the LDEV ID and the Host Group ID used by this service to the same resource group.
  • Create at least one web service connection for the Ops Center API Configuration Manager server.
  • Use the same credentials for each of the storage systems managed by the Ops Center API Configuration Manager server registered to the web service connections.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Storage Administrator (Provisioning)
    • Storage Administrator (Local Copy)
    • Security Administrator (View & Modify)
  • Create a web service connection for the BNA or DCNM server.
  • For BNA, verify that the registered user is assigned one of the following roles:
    • SAN System Administrator
    • Zone Administrator
  • For DCNM, verify that the registered user is assigned the network-admin role.
  • Verify that there are different DP Pools for the Primary and Secondary volumes for Clone.

Allocate Volumes with Smart Provisioning

Software prequisites

  • Ops Center API Configuration Manager v10.9.3-00 or later
  • When integrating with Cisco FC switches:

    Data Center Network Manager (DCNM) 7.1, 11.5

  • When integrating with Brocade FC switches:

    Fabric OS (FOS) 8.2.2d, 8.2.3a, 8.2.3c1, 9.0.1b, 9.0.1e1, 9.1.0b

  • Ops Center Administrator v10.0.0-00 or later
  • Ops Center Analyzer v10.0.0-00 or later

Setup prerequisites

  • Create a web service connection for the Ops Center API Configuration Manager that uses the same credentials for each storage system managed by Configuration Manager.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
  • Create a web service connection for DCNM or FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For DCNM, verify that the registered user is assigned the network-admin role.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
    • For user-defined roles, a role with both of the following permissions is required:
      • Fabric=O(Observe) or OM(Observe and Modify)
      • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • When specifying hosts in Host Settings, create a web service connection for Ops Center Administrator that uses credentials with System Administrator permissions.
  • When using performance data for provisioning, create a web service connection for Ops Center Analyzer that uses credentials with any one of the following roles
    • Admin
    • Modify
  • Only one Ops Center Analyzer server can be selected when using provisioning, and the required amount of performance information is stored in the Ops Center Analyzer.
  • When allocating volumes in VSM, add the LDEV ID, host group ID, and port to the VSM resource group.

If you want to use Virtual Storage Scale Out, see Using Virtual Storage Scale Out (VSSO).

Note:
  • If the automatic selection of a storage system is specified (default), a storage system that has a pool whose usage rate is low and which satisfied the following conditions is automatically selected.
    • When Disk Type is specified: A Pool configured with the specified Disk Type (if multiple items are selected, they will be selected within that range)
    • When using Performance data for provisioning is specified: the pool must have a BusyRate that is less than the specified Pool BusyRate. If there is no pool that satisfies the specified Pool BusyRate, the pool candidate is not excluded by BusyRate.
  • If the automatic selection of a storage system is specified (default), an LDEV and a Host Group are automatically created in meta_resource.
  • If an LDEV is to be created on a VSM, the user must select the VSM (resource group) on which the LDEV is to be created.

Allocate Volumes with 2DC Remote Replication

Software prequisites

  • Ops Center API Configuration Manager v10.7.0-00 or later
  • Network management software
    • Brocade Network Advisor (BNA) 14.2, 14.4

      or

    • Data Center Network Manager (DCNM) 7.1, 11.5

Setup prerequisites

  • Set up remote paths between the primary and secondary storage systems using the Fibre Channel or iSCSI.
  • When using Universal Replicator, create a journal and add a journal volume to it.
  • Register the LDEV ID, the port, and the Host Group ID used by this service to the same resource group.
  • Create at least one Web Service connection for the Ops Center API Configuration Manager server.
  • Use the same credentials for each storage system managed by the Ops Center API Configuration Manager server registered in Web Service Connections.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Storage Administrator (Provisioning)
    • Storage Administrator (Remote Copy)
    • Security Administrator (View & Modify)
  • Create a web service connection for the BNA or DCNM server.
  • For BNA, verify that the registered user is assigned one of the following roles:
    • SAN System Administrator
    • Zone Administrator
  • For DCNM, verify that the registered user is assigned the network-admin role.

Allocate Volumes, Fabric, and Datastore for ESXi Host

Software prequisites

Setup prerequisites

  • Properly connect the storage system and hosts in SAN and verify that they belong to the correct fabric.
  • Verify that the storage ports and HBA ports that are used by this service template belong to the fabric.
  • The Web Service Connection is created for the VMware vCenter Server.
  • At least one Web Service Connection is created for the Ops Center API Configuration Manager server.
  • Create one web service connection for the Ops Center API Configuration Manager that uses the same credentials for each storage system managed by the Configuration Manager. Ensure that the credentials for accessing all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
  • Create a web service connection for DCNM or FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For DCNM, verify that the registered user is assigned the network-admin role.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
    • For user-defined roles, a role with both of the following permissions is required:
      • Fabric=O(Observe) or OM(Observe and Modify)
      • Zoning=OM(Observe and Modify)
  • For switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • When allocating volumes in VSM, add LDEV ID, host group ID, and Port to the VSM resource group.
  • Specify the python execution path in the shared properties of the Python Interpreter Path in the Administration tab.
  • If LIP reset is enabled, register all ESXi server information with login credentials as Agentless Remote Connections in the Administration tab.
  • When specifying email addresses in Notification Settings, configure SMTP settings in the Administration Tab and verify that the SMTP server is accessible from the Ops Center Automator server.
  • When specifying the datastore cluster to which to add the datastores you are creating, you must first create the datastore cluster.
  • Disable storage DRS before using this service template. Adding a Datastore into a Datastore cluster can fail when Storage DRS is enabled.
Note:
  • You must import the VMware vCenter Server root certificates into the OS truststore and the Ops Center Automator truststore. Detailed information is provided in the Hitachi Ops Center Automator Installation and Configuration Guide.
  • If the automatic selection of a storage system is specified (default), a storage system that has a pool whose usage rate is low is automatically selected.
  • If the automatic selection of a storage system is specified (default), an LDEV and a Host Group are automatically created in meta_resource.
  • If an LDEV is to be created on a VSM, the user must select the VSM (resource group) on which the LDEV is to be created.
  • When you use LIP reset, if the ESXi host has an existing datastore, I/O to the existing datastore might be stopped.

Allocate Volumes with Remote Replication (Global-Active Device)

Software prerequisites

  • Ops Center API Configuration Manager v10.7.0-00 or later
  • Network Management Software
    • Brocade Network Advisor (BNA) 14.2, 14.4

      or

    • Data Center Network Manager (DCNM) 7.1, 11.5

Setup prerequisites

  • Set up remote paths between the primary and secondary storage systems using the Fibre Channel or iSCSI.
  • Create a virtual storage machine (VSM) on the secondary storage system. Add resources such as host group IDs and LDEV IDs to the resource group that is created for the virtual storage machine.
  • Map the Quorum disk on the external storage system to the primary and secondary storage systems. Quorum disks without LDEV are not supported.
  • Register the LDEV ID, the Port, and the Host Group ID used by this service to the same resource group.
  • Create at least one Web Service connection for the Ops Center API Configuration Manager server.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • Create one web service connection for the Ops Center API Configuration Manager that uses the same credentials for each storage system managed by the Ops Center API Configuration Manager. In addition to using the same credentials to access all storage systems, ensure that these credentials are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
    • Storage Administrator (Remote Copy)
  • Create a web service connection for the BNA or DCNM server.
  • For BNA, verify that the registered user is assigned one of the following roles:
    • SAN System Administrator
    • Zone Administrator
  • For DCNM, verify that the registered user is assigned the network-admin role.

Allocate Fabric Aware Volumes and Create Datastore for ESX Cluster

Software prequisites

Setup prerequisites

  • Create a datastore cluster.
  • Connect the storage system and hosts to the SAN and verify that they belong to the correct fabric.
  • Create a storage pool.
  • Disable storage DRS before using this service template. Adding a Datastore into a Datastore cluster can fail when Storage DRS is enabled.
  • When specifying email addresses in Notification Settings, configure the SMTP settings in the Administration Tab and verify that the SMTP server is accessible from the Ops Center Automator server.
  • If LIP reset is enabled, register all ESX server information with login credentials as Agentless Remote Connections in the Administration Tab.
  • Create an ESX cluster.
  • Add hosts to the ESX cluster.
  • Verify that all storage ports and HBA ports, which are used by this service template, belong to the fabric.
  • When allocating volumes in VSM, add all required resources such as LDEV ID and host group ID to the VSM resource group.
  • Register Ops Center API Configuration Manager in Ops Center Automator.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
  • Register VMware vCenter Server in Ops Center Automator.
  • Create a web service connection for FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
    • For user-defined roles, a role with both of the following permissions is required:
      • Fabric=O(Observe) or OM(Observe and Modify)
      • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • Register the storage system in Ops Center API Configuration Manager.
  • Specify the python execution path in the shared properties of the Python Interpreter Path in the Administration Tab.
Note: You must import the VMware vCenter Server root certificates into the OS truststore and the Ops Center Automator truststore. Detailed information is provided in the Hitachi Ops Center Automator Installation and Configuration Guide.
Note: Users are required to have the following privileges.

Users registered in Web Service Connections (vCenter Category):

  • Datastore
    • Allocate space
    • Browse datastore
    • Configure datastore
    • Low level file operations
    • Move datastore
  • Folder
    • Create folder
  • Host
    • Configuration
    • Change settings
    • Storage partition configuration
  • Tasks
    • Create task

Users registered in Agentless Remote Connections are required to have the Admin role.

Note: This service does not support VMware Hyperconverged infrastructure (HCI) clusters.

Add Host to Cluster in vCenter

Software prequisites

Setup prerequisites

  • Create an ESX cluster.
  • Add hosts to the ESX cluster.
  • Verify that all storage ports and HBA ports, which are used by this service template, belong to the fabric.
  • When allocating volumes in VSM, add all required resources such as LDEV ID and host group ID to the VSM resource group.
  • Register Ops Center API Configuration Manager in Ops Center Automator.
  • Register VMware vCenter Server in Ops Center Automator.
  • Create a web service connection for FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
    • For user-defined roles, a role with both of the following permissions is required:
      • Fabric=O(Observe) or OM(Observe and Modify)
      • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • Register all storage systems in Ops Center API Configuration Manager.
  • Properly connect the storage system and hosts in SAN and verify that they belong to the correct fabric.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
Note: You must import the VMware vCenter Server root certificates into the OS truststore and the Ops Center Automator truststore. Detailed information is provided in the Hitachi Ops Center Automator Installation and Configuration Guide.
Note: This service does not support VMware Hyperconverged infrastructure (HCI) clusters.

Remove Host from Cluster in vCenter

Software prequisites

Setup prerequisites

  • Create an ESX cluster.
  • Add hosts to the ESX cluster.
  • Verify that all storage ports and HBA ports, which are used by this service template, belong to the fabric.
  • When allocating volumes in VSM, add all required resources such as LDEV ID and host group ID to the VSM resource group.
  • Register Ops Center API Configuration Manager in Ops Center Automator.
  • Register VMware vCenter Server in Ops Center Automator.
  • Create a web service connection for FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
    • For user-defined roles, a role with both of the following permissions is required:
      • Fabric=O(Observe) or OM(Observe and Modify)
      • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • Register all storage systems in Ops Center API Configuration Manager.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
  • When you select the maintenance mode check box, verify the DRS setting. If DRS is disabled, the task of entering maintenance mode is not completed until all virtual machines that are running on a host are shut down or moved to other hosts manually. If DRS is enabled, virtual machines are moving automatically by DRS.
  • Make sure that no virtual machines are running on a host that resides on the datastore:
    • Make sure that the Storage DRS does not manage the datastore.
    • Make sure that Storage I/O Control is disabled for the datastore.
    • Make sure that the datastore is not used by vSphere HA Heartbeating.
  • Properly connect the storage system and hosts in SAN and verify that they belong to the correct fabric.
Note: You must import the VMware vCenter Server root certificates into the OS truststore and the Ops Center Automator truststore. Detailed information is provided in the Hitachi Ops Center Automator Installation and Configuration Guide.
Note: This service does not support VMware Hyperconverged infrastructure (HCI) clusters.

Global-Active Device Setup

Software prequisites

Ops Center API Configuration Manager v10.7.0-00 or later

Setup prerequisites

  • Create an external volume to use as a Quorum Disk, and register it in Primary and Secondary Storage.
  • Prepare ports for the remote path.

    Prepare a minimum of two ports for the remote path for Primary Storage and Secondary Storage.

    • For VSP G1000, VSP G1500, and VSP F1500, prepare one MCU port and one RCU port.
    • For VSP 5000 series models, VSP Gx00 models, VSP Fx00 models, VSP N series models, and VSP E series models, you can share an MCU/RCU/Target/Initiator port by setting the port attribute to bidirectional mode, but you should prepare a dedicated port to avoid migration performance degradation.
    • Set the zone between the ports.
    Note: You cannot create remote paths using the iSCSI port.
  • Host Group (optional)

    Create a Host Group to use for Command Device allocation, and register the pair management server WWN.

    When creating a path with this service, the host and storage port are created individually, but to control how to create a path (for example, to create it with Full Mesh), create a Host Group beforehand and when you are in the Existing Host Group/iSCSI Target in the Edit/Config window, select the Host Group you created.

  • Create a web service connection for the Ops Center API Configuration Manager that uses the same credentials for each storage system managed by Ops Center API Configuration Manager.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)

Create Online Migration Pair

Software prequisites

  • Ops Center API Configuration Manager v10.7.0-00 or later
  • When integrating with Cisco FC switches:

    Data Center Network Manager (DCNM) 7.1, 11.5

  • When integrating with Brocade FC switches:

    Fabric OS (FOS) 8.2.2d, 8.2.3a, 8.2.3c1, 9.0.1b, 9.0.1e1, 9.1.0b

  • Ops Center Administrator v10.1.0-00 or later

Setup prerequisites

  • At least one remote path using FC or iSCSI has been defined for the storage systems of the migration source and the migration target used in this service.
  • The path group, including the previous remote path, has been set up.
  • A pool has been created in the migration target storage system.
  • A VSM in the migration target storage system has been duplicated from the VSM (resource group) in the migration source volume.
  • At least one Configuration Manager server has been added to Web Service Connection.
  • The storage systems registered in Configuration Manager have the same credentials.
  • Each source/target storage system must not be registered in more than one Configuration Manager.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
    • Storage Administrator (Remote Copy)
    • Storage Administrator (Initial Configuration)
  • The migration source volumes must not have any remote copy pairs configured.
  • Create a web service connection for DCNM or FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
  • For user-defined roles, a role with both of the following permissions is required:
    • Fabric=O(Observe) or OM(Observe and Modify)
    • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • For DCNM, verify that the registered user is assigned the network-admin role.

If you want to run multiple tasks concurrently, see Running multiple tasks.

Create Online Migration Pair for Multiple Hosts

Software prequisites

  • Ops Center API Configuration Manager v10.7.0-00 or later
  • When integrating with Cisco FC switches:

    Data Center Network Manager (DCNM) 7.1, 11.5

  • When integrating with Brocade FC switches:

    Fabric OS (FOS) 8.2.2d, 8.2.3a, 8.2.3c1, 9.0.1b, 9.0.1e1, 9.1.0b

  • Ops Center Administrator v10.7.0-00 or later

Setup prerequisites

  • The Create Online Migration Pairs for Multiple Hosts must be the same version (VV.RR) as the Create Online Migration Pair service.
  • When multiple hosts are selected, they must not have the same volume allocated to them.
  • At least one remote path using FC or iSCSI has been defined for the storage systems of the migration source and the migration target used in this service.
  • The path group, including the previous remote path, has been set up.
  • A pool has been created in the migration target storage system.
  • A VSM in the migration target storage system has been duplicated from the VSM (resource group) in the migration source volume.
  • At least one Configuration Manager server has been added to Web Service Connection.
  • The storage systems registered in Configuration Manager have the same credentials.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
    • Storage Administrator (Remote Copy)
    • Storage Administrator (Initial Configuration)
  • The migration source volumes must not have any remote copy pairs configured.
  • Each source/target storage system must not be registered in more than one Configuration Manager.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • The migration source volumes must not have any remote copy pairs configured.
  • Create a web service connection for DCNM or FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
    • For user-defined roles, a role with both of the following permissions is required:
      • Fabric=O(Observe) or OM(Observe and Modify)
      • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • For DCNM, verify that the registered user is assigned the network-admin role.
  • If you already have Ops Center Administrator installed, you must import the Ops Center Administrator server certificate in the Ops Center Automator truststore, to use the host selection feature.
  • If you enable the Use Diskless Quorum option, an unused common Quorum ID must exist for both the source and target.
  • If you do not enable the Use Diskless Quorum option, you must create a Quorum disk to be used with global-active device.

If you want to run multiple tasks concurrently, see Running multiple tasks.

Migrate Data for Online Migration Pair

Software prerequisites

Setup prerequisites

  • Submit the service as a user with the same permissions as the user who submitted the Create Online Migration Pair service.
  • The target storage systems scheduled for migration must be registered in the same API Configuration Manager that was used when running the Create Online Migration Pair service and the API Configuration Manager must be registered in Web Service Connections.
  • Each source/target storage system must not be registered in more than one Configuration Manager.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • After the Create Online Migration Pair task that you select in the Edit/Submit Service window completes, you cannot make any changes to the configuration of the target resources before running the task.
  • The migration source volumes must not have any remote copy pairs configured.

If you want to run multiple tasks concurrently, see Running multiple tasks.

Clean up Online Migration Pair

Software prequisites

Ops Center API Configuration Manager v10.7.0-00 or later
Ops Center API Configuration Manager v10.7.0-00 or later

Setup prerequisites

  • Submit the service as a user with the same permissions as the user who submitted the Create Online Migration Pair service.
  • The target storage systems scheduled for cleanup must be registered in the same API Configuration Manager that was used when running the Create Online Migration Pair service and the API Configuration Manager must be registered in Web Service Connections.
  • Each source/target storage system must not be registered in more than one Configuration Manager.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • If you want to clean up a failed task due to an error instead of the task that was completed, remove the cause of the error and then submit the service.
  • After the Create Online Migration Pair task that you select in the Edit/Submit Service window completes or fails, you cannot make any changes to the configuration of the target resources before running the task.

  • If you want to run multiple tasks concurrently, see Running multiple tasks.

ServiceNow

Ops Center Automator has the following service templates for ServiceNow

  • Create ServiceNow Incident Ticket
  • Retrieve ServiceNow Incident Tickets
  • Call ServiceNow Table API
  • Update ServiceNow Incident Ticket

Software prequisites

ServiceNow version: Utah, Vancouver, Washington DC

Setup prerequisites

Register the ServiceNow Web Service Connection in Ops Center Automator.

Combinations of supported versions of VMware vCenter Server, VMware vSphere Hypervisor (ESXi), Python, and Python libraries

VMware vCenter Server and VMware vSphere Hypervisor (ESXi) Python Python library
7.0 U1, 7.0 U2, 7.0 U3 3.8
  • certifi 2021.10.8
  • charset-normalizer 2.0.8
  • idna 3.3
  • pyvmomi 7.0.3
  • requests 2.26.0
  • six 1.16.0
  • urllib3 1.26.7
3.9, 3.10, 3.11
  • certifi 2022.6.15
  • charset-normalizer 2.0.12
  • idna 3.3
  • pyvmomi 7.0.3
  • requests 2.28.0
  • six 1.16.0
  • urllib3 1.26.9
3.12
  • certifi 2023.5.7
  • charset-normalizer 2.0.12
  • idna 3.4
  • pyvmomi 8.0.2.0.1
  • requests 2.31.0
  • six 1.16.0
  • urllib3 2.0.3