What happens if a Lone symphony cluster does not join with SMC while adding Lone symphony cluster with SMC?

You are getting error while trying to join Lone Symphony cluster with SMC.

[root@hpc-primary-smc]# smcadmin cluster list
NAME     STATUS     MEMBERSHIP
lone       error      nonmember

This error happens when:

• The outbound connection configuration is unsuccessful.
• SMCP service is down in the lone symphony cluster.
• The network communication between SMC and lone symphony cluster is not communicable.
• The VEMKD port that is used to SMC is not correct.

To make the outbound connection:

• check whether in lone symphony cluster enabled outbound as <ego:EnvironmentVariable name="SMC_PROXY_INBOUND_CONNECTION">Y</ego:EnvironmentVariable> in SMCP.xml
• If SMCP service is down in lone symphony cluster, run command egosh service start SMCP to start SMCP service
• If network connection is not happening, check whether you added an SMC cidr block in the Lone symphony cluster security group or vice versa.

How to resolve “End of file or no input: ‘Operation interrupted or timed out'“ when trying to add a lone symphony cluster to SMC?

You see this message:

[root@hpc-primary-smc]# smcadmin cluster add -c lone1 -p 17870 -m "hpc-lone-primary-0,hpc-symphony-secondary-0"
End of file or no input: 'Operation interrupted or timed out'

When you try to add a lone symphony cluster with SMC, because of a time out issue you get the warning message. The message is a warning and does not impact adding a lone symphony cluster with SMC.

This error will not impact on adding a lone symphony cluster with SMC. Keep on adding other lone symphony clusters.

What happens after provisioning an SMC cluster, immediately if you try to logon as egosh user in secondary nodes of the SMC?

After provisioning the SMC cluster, if you immediately try to logon on secondary nodes of SMC you see this message:

[root@hpc-secondary-smc]# egosh user logon -u Admin -x Admin
bash: egosh command not found

It takes 10 min to sync primary host data of SMC to secondary nodes of SMC using rsync command.

Wait for 10 min after provisioning the SMC cluster, then try to login.