VMware Networking Community
HassanAlKak88
Expert
Expert
Jump to solution

Slowness/Crash on the vsphere web client after register NSX manager 6.4.5 with vCenter 6.0-U3h

Hello,

Noting that we're facing an issue with the vSphere web client after register NSX manager 6.4.5 with vCenter server 6.0 U3h (Windows version).

Each time the web client hang and go down, we have to restart the services from vcenter server or restart the whole server which not possible at all.

Any ideas?


If my reply was helpful, I kindly ask you to like it and mark it as a solution

Regards,
Hassan Alkak
Reply
0 Kudos
1 Solution

Accepted Solutions
HassanAlKak88
Expert
Expert
Jump to solution

Open a case with GSS team, problem solved after they increased the "MaxPermMB" value for vSphere client to 512 in the following file "service-layout.mfx"


If my reply was helpful, I kindly ask you to like it and mark it as a solution

Regards,
Hassan Alkak

View solution in original post

3 Replies
HassanAlKak88
Expert
Expert
Jump to solution

I unconfigured the integration with lookup service on NSX manager and restart the web client service. now is working fine.

What is wrong specialy that VMware said NSX 6.4.5 is supported with vCenter 6.0 U3h as per the below:

pastedImage_0.png

please advise,


If my reply was helpful, I kindly ask you to like it and mark it as a solution

Regards,
Hassan Alkak
Reply
0 Kudos
Sreec
VMware Employee
VMware Employee
Jump to solution

You should raise a ticket with GSS to help you with a precise answer. There are multiple reasons why slowness can happen when a plugin a registered , may be a increase in heap memory is required. So better get in touch with GSS ans show them the results (Take a snapshot before the integration ) ,it should be a quick one for them to get it sorted.

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 7x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
Reply
0 Kudos
HassanAlKak88
Expert
Expert
Jump to solution

Open a case with GSS team, problem solved after they increased the "MaxPermMB" value for vSphere client to 512 in the following file "service-layout.mfx"


If my reply was helpful, I kindly ask you to like it and mark it as a solution

Regards,
Hassan Alkak