| Allocate Volumes with Configuration Manager |
Ops Center API Configuration Manager v10.7.0-00 or later |
- Register the LDEV ID and Host Group ID used by this service to the same resource group or virtual storage machine.
- 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.
-
Use the same credentials for each storage system managed by Configuration Manager for which the Web service connection was created. Also, in addition to having the same credentials connected to all the storage systems, ensure that these credentials are assigned the following roles:
- Security Administrator (View and Modify)
- Storage Administrator (Provisioning)
|
| Allocate Fabric Aware Volumes with Configuration Manager |
- 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 (network-admin role is required)
- When integrating with Brocade FC switches: Fabric OS (FOS) 8.2.1b or later, 9.0.1b or later
- For the default Fabric OS roles, Admin, FabricAdmin, or ZoneAdmin role is required.
- 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.
|
- 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 and 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.
|
| Allocate Like Volumes with Configuration Manager |
Ops Center API Configuration Manager v10.7.0-00 or later |
- Create a Web service connection for the Ops Center API Configuration Manager.
- Use the same credentials for each storage system managed by Ops Center API Configuration Manager for which the Web service connection was created. Also, in addition to having the same credentials connected to all the storage systems, ensure that these credentials are assigned the following roles:
- Security administrator (View, Edit)
- Storage administrator (Provisioning)
|
| Allocate Volumes with Clone/Snapshot |
- 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 (SAN System Administrator or Zone
Administrator role is required)
or
- Data Center Network Manager (DCNM) 7.1,
11.5 (network-admin role is required)
|
- 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.
- Assign users the following account permissions:
- Storage administrator (Provisioning)
- Storage administrator (Local Copy)
- Security administrator (View and Modify)
- Create a web service connection for the BNA or DCNM server.
- Verify that there are different DP Pools for the Primary and Secondary volumes for Clone.
|
| Allocate Volumes with Smart Provisioning |
- 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 (network-admin role is required)
- When integrating with Brocade FC switches:
Fabric OS (FOS) 8.2.1b or later, 9.0.1b or later
- Ops Center Administrator v10.0.0-00 or later
- Ops Center Analyzer v10.0.0-00 or later
|
- 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 and 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.
- 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
- 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.
Notes:
- 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 |
- Ops Center API Configuration Manager v10.7.0-00 or later
- Network management software
- Brocade Network Advisor (BNA) 14.2, 14.4 (SAN System Administrator or Zone Administrator role is required)
or
- Data Center Network Manager (DCNM) 7.1, 11.5 (network-admin role is required)
|
- 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.
- Assign users the following account privileges:
- Storage administrator (Provisioning)
- Storage administrator (Remote Copy)
- Security administrator (View and Modify)
- Create a web service connection for the BNA or DCNM server.
|
| Allocate Volumes, Fabric, and Datastore for ESXi Host |
|
- Properly connect the storage system and hosts in SAN and verify that they belong to the correct fabric.
- If Fabric Settings is enabled, configure a single Brocade Network Advisor or Cisco Data Center Network Manager to manage the 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 and Modify)
- Storage Administrator (Provisioning)
- Create a web service connection for the BNA or DCNM
server.
- 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.
Notes:
- 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) |
- Ops Center API Configuration Manager v10.7.0-00 or later
- Network Management Software
- Brocade Network Advisor (BNA) 14.2, 14.4 (SAN System Administrator or Zone Administrator role is required)
or
- Data Center Network Manager (DCNM) 7.1, 11.5 (network-admin role is required)
|
- 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 and Modify)
- Storage Administrator (Provisioning)
- Storage Administrator (Remote Copy)
- Create a web service connection for the BNA or DCNM server.
|
| Configure CIFS/NFS for Hitachi |
- OpenLDAP v2.x (LDAP v3 required
- SMU version 13.3 or 13.4
|
Use OpenLDAP v2.x (using LDAP v3) for access control configuration. |
Data Mobility
- Allocate Volumes from Virtual Storage Machine
- Export Virtual Storage Machine Configuration Across Sites
- Create High Availability Pair for Migration
- Migrate Data Using High Availability Pair
|
Ops Center API Configuration Manager v10.7.0-00 or later
Note: To use the Data Mobility services, an administrator
must install the Ops Center API Configuration Manager
on each site and register the storage systems by using the
Add Web Service Connections option on
the Administration tab. In addition, the
administrator must assign a common resource group name to all of
the VSMs used in the data mobility services and then update the
associated shared property using the Set Service
Shared Property option. Detailed information for
Admin users is provided in Configuring Ops Center API Configuration Manager
connections and Modifying shared service properties for data
mobility services.
Note:
Data Mobility service performance is affected by the
Configuration Manager storage access mode setting. You should
use the "fcConnectionMode" setting to obtain higher performance.
For details, see "Appendix A. Changing the communication mode of
the REST API server" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
|
- Create a VSM and assign resources before running this service.
- Register the LDEV ID and Host Group ID used by the service to the same resource group or virtual storage machine whose name follows the naming convention on virtual storage machine.
- Assign common resource group names to all VSMs across Storage Systems used in this service and modify the associated shared service property from the Shared Properties Settings pane.
- Install Configuration Manager and register all remote storage system information across all storage systems use by this service.
- 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 a 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 and Modify)
- Storage Administrator(Provisioning)
- Storage Administrator (Remote Copy)
|
| Allocate Fabric Aware Volumes and Create Datastore for ESX Cluster |
|
- 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.
- Configure a single Brocade Network Advisor to manage the fabric.
- 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.
- Register Brocade Network Advisor in Ops Center Automator.
- 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 Automatortruststore. 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.
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
- Host
- Configuration
- Change settings
- Storage partition configuration
- Tasks
Users registered in Agentless Remote Connections are required to have the Admin role.
|
| Add Host to Cluster in vCenter |
|
- Create an ESX cluster.
- Add hosts to the ESX cluster.
- Configure a single Brocade Network Advisor to manage the fabric.
- 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.
- Register Brocade Network Advisor in Ops Center Automator.
- 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 and 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 |
|
- Create an ESX cluster.
- Add hosts to the ESX cluster.
- Configure a single Brocade Network Advisor to manage the fabric.
- 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.
- Register Brocade Network Advisor in Ops Center Automator.
- 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 and 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.
|
| Expand Volume Capacity |
Ops Center API Configuration Manager v10.7.0-00 or later |
- One or more Web Service Connection instances must have been created for the Configuration Manager server.
- Use the same credentials for each storage system managed by Configuration Manager for which the Web Service connection was created. Additionally, the following privileges must be assigned:
- Storage administrator (provisioning)
- Security administrator
- The status of the volume to be expanded must be acceptable to the storage systems.
|
| Get IO Control Set IO Control
Remove IO Control
|
- Ops Center Administrator v10.0.1-00 or later
- Ops Center API Configuration Manager v10.0.1-00 or later
|
- Create a volume and LUN path for setting IO control in the storage system.
- Install the Server Priority Manager license in the storage system.
- Make sure that the Server Priority Manager is not being used by Storage Navigator.
- If configuration-change notifications from the storage system are disabled, update the Configuration Manager storage system information.
- Register the server and storage system where the LUN path is configured in Ops Center Administrator.
- Use the same credentials for each storage system managed by Configuration Manager for which the Web Service connection was created. Additionally, the following privileges must be assigned:
- Storage administrator (System Resource Management, Provisioning)
- Security administrator
- When specifying hosts in Select from Host, create a web service connection for Ops Center Administrator that uses credentials with System Administrator permissions.
- Host attached volumes can only be from a single storage system.
|
| Global-Active Device Setup |
- Ops Center API Configuration Manager v10.7.0-00
or later
-
When using
VSP G200, G400, G600, G800, VSP F400, F600, F800, VSP N400, N600, N800, VSP G1000, VSP G1500, VSP F1500, or VSP E990, enable SSL between the Ops Center API Configuration Manager
server and the storage system when registering the
storage by using the Ops Center API Configuration Manager. If you register
the storage from the Ops Center Automator
Administration tab, choose
the Enable SSL communication with
SVP option.
-
Stop all CCI instances between
1020-1039 on the Ops Center API Configuration Manager server.
- Add the
Ops Center API Configuration Manager
server to the Ops Center Automator
Agentless Remote Connections. When adding the
connection, match the IP Address/Host
Name setting of Web Service Connection
with the IP Address/Host Name
setting of the Agentless Remote Connection setting.
|
- 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 and Modify)
- Storage Administrator (Provisioning)
|
| Online Migration |
|
Resource prerequisites
You must create the following resources before you run this service:
- Ops Center Protector-Data Flow
Source: Specify the Ops Center Protector-Source Node
Target: Specify the Ops Center Protector-Target Node
Type: Active-Active Remote Clone (Global-active device)
Transfer Type: Continuous
- When using the host selection feature, create a web service connection for Ops Center Administrator that uses System Administrator credentials.
- Import the Ops Center Protector and Ops Center Administrator server certificates.
Secure communication (HTTPS) is required for communication between Ops Center Automator and Ops Center Protector/Ops Center Administrator.
Therefore, you must import the Ops Center Protector and Ops Center Administrator server certificate into the Ops Center Automator truststore.
For details, see "Setting up secure communication with a Ops Center Protector server" and "Setting up secure communication with an Ops Center Administrator" in the Hitachi Ops Center Automator Installation and Configuration Guide.
- Resolve the Ops Center Protector and Ops Center Administrator host name. After you import the Ops Center Protector and Ops Center Administrator server into the Ops Center Automator truststore, ensure that the system can resolve the Ops Center Protector and Ops Center Administrator server name.
- Create a web service connection for the BNA or DCNM server.
- 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 and Modify)
- Storage Administrator (Provisioning)
- If the source volumes have asynchronous remote clone pairs:
- The Hitachi Block Device node indicating
the storage system of the asynchronous remote clone
destination of the migration target volume must be
registered in Ops Center Protector.
- The journal volume that can be used in the asynchronous remote clone pair must be
created in the storage system of the migration
target volume and the storage system of the
asynchronous remote clone destination.
- The zoned remote path group must be defined between the storage system of the
migration target volume and the storage system of
the asynchronous remote clone destination.
- If you enable the Use Diskless Quorum option, an unused common Quorum ID must exist
for both the source and target storage systems.
|
| Create Online Migration Pair |
- 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 (network-admin role is required)
- When integrating with Brocade FC switches:
Fabric OS (FOS) 8.2.1b or later, 9.0.1b or later
- Ops Center Administrator
v10.1.0-00 or later
|
- 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.
- The Configuration Manager user has the following roles:
- Security Administrator (View and Modify)
- Storage Administrator (Provisioning, Remote Copy, and 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.
If you want to run multiple tasks concurrently, see Additional prerequisites for multiple runs.
|
| Create Online Migration Pair for
Multiple Hosts |
- 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 (network-admin role is required)
- When integrating with Brocade FC switches:
Fabric OS (FOS) 8.2.1b or later, 9.0.1b or later
- Ops Center Administrator v10.7.0-00 or later
|
- 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.
- The Configuration Manager user has the following
roles:
- Security Administrator (View and
Modify)
- Storage Administrator (Provisioning,
Remote Copy, and 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 Configuration Manager user has the following
roles:
- Security Administrator (View and
Modify)
- Storage Administrator (Provisioning,
Remote Copy, and 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.
- 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 Additional prerequisites for multiple runs.
|
| Migrate Data for Online Migration Pair |
Ops Center API Configuration Manager v10.7.0-00 or later |
- 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 Additional prerequisites for multiple runs.
|
| Clean up Online Migration Pair |
Ops Center API Configuration Manager v10.7.0-00 or later |
- 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 Additional prerequisites for multiple runs.
|
| Smart Allocation for Oracle Databases |
|
- Create a Web service connection for the Ops Center API Configuration Manager.
- Use the same credentials for each storage system managed by Ops Center API Configuration Manager for which the Web service connection was created. Also, in addition to having the same credentials connected to all the storage systems, ensure that these credentials are assigned the following roles:
- Security administrator (View, Edit)
- Storage administrator (Provisioning)
- Create a web service connection for the BNA server.
- Create an Agentless Connections for the Oracle servers. It is not necessary to specify authentication information when registering.
|
ServiceNow
- Create ServiceNow Incident Ticket
- Retrieve ServiceNow Incident Tickets
- Call ServiceNow Table API
- Update ServiceNow Incident Ticket
|
ServiceNow version: Quebec, Rome |
Register the ServiceNow Web Service Connection in Ops Center Automator |