Hello Rob,

     Looking through the knowledgebase, article emc255976 is very informative in regards gatekeepers in general, and article emc186179 verifies that gatekeepers are single pathed but what you have listed below indicates that anyway.

Can you tell me is this a new install? Has this host previously used these gatekeepers?

Have you checked that the GK are accessible from the host?

Anything in the errprt?

And would you have any output from the symapi log file (or all daemon log files)  as well please?

Have you tried stopping and starting the daemon?

Sorry for the list of questions.

Thank you Rob,

     Nollaig

Hello Nollaig,

Thanks for your review.

Yesterday I got the answer from EMC support ( I had to make a problem report because of time issues )

EMC gave me the solution: here it is:

The disk hdiskpower0 comes from another symmetrix( let's call it the remote symmextrix ).

It is used as a heartbeat disk between this node and his 'brother'-node.

hdiskpower1 and hdiskpower2 are from the local EMC symmetrix.

So, there is also sym-communication  needed between this node and the remote EMC symmetrix.

But there are not any Gatekeeper devices from the remote symmetrix and Sol.enabler takes hdiskpower0 for his communication.

So we added a few gatekeepers from the remote symmetrix and the problem is solved !

I now have 2 GK devices from the remote symmetrix and 4 from the local symmetrix.

EMC advice is to have 6 GK devices.

In my situation then I will have a total of 12 GK devices.

Unfortunately this gives a big output of lspv , but that is only the output, nothing harming.

Hope you learn from my text and thanks again !

Rob

That is interesting, never heard of a remote GK usage. Did EMC mention about any primus being updated/existed with this information?

Ik ben niet aanwezig vanaf 12-11-2010 en kom terug op 01-01-2016.

Geachte, deze mailbox is niet meer in gebruik. Uw mail zal dan ook niet

gelezen en beantwoord worden. U kunt uw mail doorsturen naar

1Rob_Roos@nl.ibm.com