Keystone data flow

Contributors netapp-manini netapp-aruldeepa

Keystone systems encounter data flow through Keystone Collector traffic and monitoring data flows.

Keystone Collector data flow

Keystone Collector initiates REST API calls to the storage controllers and obtains usage details of the controllers periodically.

collector data flow

  1. NetApp Collector initiates an HTTPS session to the Active-IQ cloud portal.

  2. The firewall operated by the customer allows the connection.

  3. The Active IQ Cloud portal accepts the connection and establishes a tunnel to the NetApp Collector.

  4. The NetApp collector establishes a REST API session to the management connection of the storage controller, obtains the environmental data, and sends it to the Active IQ portal.

Monitoring data flows

Monitoring the health of the storage infrastructure continuously is one of the most important features of Keystone service. For monitoring, Keystone uses OpsRamp, which needs remote access to customer’s network. The following image describes how remote access to the customer location is secured by the OpsRamp tool.

monitoring flow

  1. The OpsRamp gateway initiates a TLS session to the OpsRamp cloud portal in the cloud.

  2. The firewall operated by the customer allows the connection.

  3. The OpsRamp server in the cloud accepts the connection.

  4. A TLS tunnel is established between the OpsRamp cloud portal and the OpsRamp local gateway.

  5. The NetApp controllers send alerts using SNMP protocol or respond to API requests to the OpsRamp local gateway.

  6. The OpsRamp local gateway sends these alerts to its cloud portal using the TLS session, which was established before.