The following shows the secure communication routes for Ops Center Automator.
The following shows the secure communication routes that can be used in Ops Center Automator and the supported protocols for each route that is used. Note that the number in the table corresponds with the number in the figure.
| Route | Server (program) | Client | Protocol |
|---|---|---|---|
| 1 | Ops Center Automator1 | Management client (Web browser) | HTTPS2 |
| 2 | Ops Center Common Services1 | Ops Center Automator1 | HTTPS |
| 3 | Ops Center API Configuration Manager1 | Ops Center Automator1 | HTTPS2 |
| 4 | Ops Center Analyzer1 | Ops Center Automator1 | HTTPS2 |
| 5 | Ops Center Administrator1 | Ops Center Automator1 | HTTPS |
| 6 | LDAP directory server | Ops Center Automator1 | StartTLS3 |
| 7 | VMware vCenter Server | Ops Center Automator1 | HTTPS |
| 8 | Ops Center Automator1 | Ansible5 | HTTPS |
| 9 | ServiceNow | Ops Center Automator1 | HTTPS |
| 10 | Ops Center Automator1 | ServiceNow6 | HTTPS |
| 11 | Web service connection server (for example, DCNM) | Ops Center Automator1 | HTTPS2 |
| 12 | Agentless remote connection server | Ops Center Automator1 | SSH4 |
| 13 | Brocade Fabric OS | Ops Center Automator1 | HTTPS2 |
|
|||
- If the protocol used for communication with Ops Center Automator is HTTPS, TLS 1.2 and TLS 1.3 are supported. Note that if you have changed the server managing the Common Component user account to a remote host, only TLS 1.2 is supported for communication from Ops Center Automator to the server. For cipher suites supported by Ops Center Automator as a server, see Cipher suites supported as a server.
- For security settings for communication route 9 with Ansible, see the Hitachi Ops Center Automator User Guide.
- For security settings for communication route 10 and 11 with ServiceNow, see the Hitachi Ops Center Automator User Guide.