12:42:37,416 ERROR [com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource] Error 1 out of 1: <DS name>[Internal error] - Unable to generate the model for device <IP-Adress>. Invalid Chas...12:42:37,416 ERROR [com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource] Error 1 out of 1: <DS name>[Internal error] - Unable to generate the model for device <IP-Adress>. Invalid Chassis Role ([Device name <IP-Adress>]: Unable to generate the model for device <IP-Adress> . Invalid Chassis Role)com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException: Unable to generate the model for device <IP-Adress>. Invalid Chassis Role . . Caused by: com.onaro.sanscreen…
Applies to Oncommand Unified Manager 9.5 and below ActiveIQ Unified Manager 9.6 and above Cluster discovery stuck for one cluster in UM Extensive execution time and returned records for different ZAPI...Applies to Oncommand Unified Manager 9.5 and below ActiveIQ Unified Manager 9.6 and above Cluster discovery stuck for one cluster in UM Extensive execution time and returned records for different ZAPI calls in foundation poll recordings under log_netappfoundation_xxxx_iterator_response_time.txt Some of the known ZAPI calls exhibiting the behavior are: datasource, zapi, timestamp, max-records, iterations, total-clock-time, total-zapi-time, total-invocations, total-records, returned-records-list
