cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
451
Views
0
Helpful
2
Replies
Highlighted

Login to Hyperflex connect failing

Hi,

I have recently installed Hyperflex cluster - version 3.5(2b). Everything was working fine, but recently I have issues with login to HX connect management interface. The site loads up, I am prompted for credentials, after providing them it just sits there for quite a time and then I got red message "Check your cluster status or logs for possible solutions".

 

I am able to log to the cluster mgmt IP with ssh, "stcli cluster info" says cluster is healty:

 

--

cluster:
allFlash: False
healthState: healthy
capacity: 6.0T

--

 

It's not a browser issue, I tried from different browsers and computers. It happened before and I was able to fix the issue by rebooting whole cluster. Obviously that's not acceptable solution. Anyone has run into this problem?

 

Thanks,

Martin

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Login to Hyperflex connect failing

I was able to fix the issue. The whole environment is behind NAT (meaning NAT between HX and my client station I am using for management). Besides NAT for HX connect, I have natted SCVM adresses as well, as this seems to be required for Intersight connection (for the connection HX connect is using IP address of the SCVM, not HX connect cluster IP).

Turns out, this NAT for SCVM caused the issue. When I removed NAT, and left just the one for HX connect, everything works fine. Well, the intersight connection doen'ts work. Plus, I don't really understand why this matters. All key components (SCVM, ESXi, VC) are in the same network, why NAT of SCVM breaks the HX connect? 

Can anyone explain this?

 

2 REPLIES 2
Cisco Employee

Re: Login to Hyperflex connect failing

Please engage with Cisco TAC to address this issue as they may have to restart some services on the storage controllers to resolve this or it's due to a bug. The TAC engineer will make that determination once they're engaged

Re: Login to Hyperflex connect failing

I was able to fix the issue. The whole environment is behind NAT (meaning NAT between HX and my client station I am using for management). Besides NAT for HX connect, I have natted SCVM adresses as well, as this seems to be required for Intersight connection (for the connection HX connect is using IP address of the SCVM, not HX connect cluster IP).

Turns out, this NAT for SCVM caused the issue. When I removed NAT, and left just the one for HX connect, everything works fine. Well, the intersight connection doen'ts work. Plus, I don't really understand why this matters. All key components (SCVM, ESXi, VC) are in the same network, why NAT of SCVM breaks the HX connect? 

Can anyone explain this?

 

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards