It takes long to access vManage

[interfacedy]

Hi There are several cases of vManage. It takes long to access vManage successfully. Its about half hour to one hour or more to access the vManage. The below is its configuration. Is there some configuration wrong? Initially I thought RAM , cpu or hard disk are not enough. After i added more enough, it still has the issue. and some of vManage are stuck there like the below. Is this relative with certificate? because it happen during or after installing certificate with vsmart or vbond. Anyone can share some experience? Thank you very much.

vManager3# sh run
system
host-name vManager3
system-ip 10.0.0.3
site-id 100
admin-tech-on-failure
no vrrp-advt-with-phymac
sp-organization-name sxyz
organization-name sxyz
vbond 10.0.0.1
aaa
auth-order local radius tacacs
usergroup basic
task system read
task interface read
!
usergroup global
!
usergroup netadmin
!
usergroup operator
task system read
task interface read
task policy read
task routing read
task security read
!
usergroup resource_group_admin
task system read
task interface read
!
usergroup resource_group_basic
task system read
task interface read
!
usergroup resource_group_operator
task system read
task interface read
!
usergroup tenantadmin
!
user admin
password $6$721e8c94cfe0131e$lXqBTI8WK6qa5mX1HAZM8MzyrLy9ZNA17WRV4EbXpLWtS6Xn54EEyliEWAxQdTMmrptbroH.0qWVDwsnu70
!
ciscotacro-user true
ciscotacrw-user true
!
logging
disk
enable
!
!
ntp
parent
no enable
stratum 5
exit
!
!
vpn 0
interface eth0
ip address 192.168.1.13/24
ipv6 dhcp-client
tunnel-interface
allow-service all
allow-service dhcp
allow-service dns
allow-service icmp
no allow-service sshd
no allow-service netconf
no allow-service ntp
no allow-service stun
allow-service https
!
no shutdown
!
ip route 0.0.0.0/0 192.168.1.100
!
vpn 512
!
vManager3#

[Dan Frey]

What hardware resources (cpu, ram, disk) did you allocate to vmanage?   If you log into vmanage cli, then go into vshell and execute lscpu what is the output? Does CPU(s) match the hardware resources allocated during instantiation?   

ENvManage# vshell
ENvManage:~$ lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              16
On-line CPU(s) list: 0-15

I had a similar issue with vManage web UI availability in KVM (centos 7) as I allocated 16 CPU to the instance but lscpu showed only 1 cpu was present.   I had to expose the CPU architecture in KVM during instantiation in order for vManage to consume all 16 CPUs to fix the issue with web UI availability.