Risks, Limitations and Assumptions

  • Application can handle Critical/Recovery failure notifications for the following two cases when user enables App Failure Notifications in configuration.
    • Connectivity Exception
    • Authentication Exception
  • Application uses the provided IpAddress/hostname, Credentials for both REST APIs and SSH communications. SSH communication is used for powerscale_bootDrive_LifeRemaining metric collection. Rest API communication is used for rest of the functionalities.
  • Credentials used should have sudo root privileges for ssh connection used for powerscale_bootDrive_LifeRemaining metric collection.
  • App will not send any duplicate/repeat failure alert notification until the already existed critical alert is recovered.
  • Application cannot control monitoring pause/resume actions based on above alerts
  • Metrics can be used to monitor Dell PowerScale resources and can generate alerts based on the threshold values.
  • Dell PowerScale’s Event/Alert polling will be started only if user enables **Event/Alert Polling **in configuration.
  • Possible values of Event/Alert Severity Filter configuration property are emergency, critical, warning, information, unknown
  • OpsRamp has given sample mappings to map Dell PowerScale with OpsRamp Severities as part of **Event/Alert Severity Mapping **configuration filed. User can modify them as per their use-case at any point of time from app configuration page. Possible OpsRamp Severities are Critical, Warning, Ok, Info.
  • For Network Interfaces, we’re mapping the Ipaddress with external IPs of network interfaces and ignoring internal ips based on available pool details like “Internal_MGMT”.
  • Component level thresholds can be configured on each resource level.
  • No support of showing activity log and applied time.
  • The minimum supported version for the option to get Latest snapshot metric is nextgen-14.0.0.
  • Full discovery support requires gateway version 15.0.0 or above.
  • App is not compatible with Cluster Gateway.
  • The following read privilege is required to get the Zones API work: Auth access zones (ISI_PRIV_AUTH_ZONES).
  • From version 5, in order to stop the node getting reconciled with Cluster when having the same Ip address, Updating the MAC address of cluster and that Node as CU:00:00:00:00:FirstTwoCharsOfSerialNumber and ND:00:00:00:00:FirstTwoCharsOfSerialNumber respectively. For upgrade case , the cluster will still have the custom attributes of node as well even after the upgrade.