You have your collector configured to use a netcnfg alias that is not defined in the netcnfg file in the Solutions Enabler installation.
Lets take a step back, and discuss a few concepts:
Solutions Enabler manages Symmetrix arrays by having a number of small "gatekeeper" volumes provisioned to them = SE has physical connectivity to the Symmetrix array via FC/iSCSI volumes
Solutions Enabler supports client/server mode, where you can have Solutions Enabler (client) speak to another Solutions Enabler (server) to manage arrays - it is this topology that the majority of CI users will use.
In Client/Server mode, you need to have the netcnfg file edited to define aliases for the various remote SE "servers" you want to access.
In CI, you need to define a valid netcnfg alias that will match one of those aliases set in the "Service Name" field, or, you need to not use "REMOTE" or "REMOTE_CACHED" in the advanced option "Connection Caching" - but that leaves "LOCAL" as the only connection mode, which requires your CI AU to have those gatekeeper volumes presented to it from 1 or more Symms.
Usernames and passwords are only relevant for performance, which will only be attempted if inventory is successful - it is a bit early to worry about that stuff.
It looks like this collector succeeded for inventory at 1:01pm EST - do you now see some number of Symmetrix arrays in the Devices section of the collector page?
If inventory is successful, we can contemplate performance.
The performance collection needs to work against a Solutions Enabler installation that has the SMI-S service/functionality, aka ECOM installed - this is NOT necessarily installed by default on Solutions Enabler servers.
~6 minutes ago, I see a collector failed to speak to SMI-S - the collector is configured to speak to an IP address whose last octet is 40. It looks like that server may NOT have SMI-S installed or running - CI is getting a TCP Connection Refused when attempting to initiate a TCP connection to https://......40:5989
Does that ...40 server have a "ECOM" service/daemon running?
We have configured one array and then added another, we see performance failure error intermittently. I am on a screen share, I asked him to add more GKs. As only 1 GK was configured. Now he is adding 5 more so total 6.
Can you pl. confirm that you are seeing performance data ? Thx
The SMI-S server that this collector is pointed at has 3 symms in it:
all with serial numbers like ......5xxx
The 2 arrays managed by the Solutions Enabler server that this collector is discovering have
serial numbers like ......2xxx
Therefore, this collector is failing to report performance because this collector cannot obtain performance data for the 2 arrays it is responsible for. Effectively, this collector looks like it is configured to speak to the wrong SMI-S server, a SMI-S server for a different collection of arrays.
The fact that this SMI-S server may or may not have performance data for other arrays in effectively irrelevant - this collector knows what it did for inventory (discover two arrays with .....2xxx serial numbers), and therefore for performance, it is only looking for those 2 array's data