From the NSX Edge CLI, which command would show VIP statistics?
A.
show service loadbalancer pool
B.
show service loadbalancer virtual
C.
show service loadbalancer monitor
D.
show service loadbalancer
Explanation:
https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=2122708
Correct Answer is D:
Refer to https://kb.vmware.com/s/article/2122708
VMware NSX for vSphere 6.2.4 Enhancements
The show service loadbalancer command is improved to show all active sessions that are used globally per NSX Edge.
The L4 load balancer connection statistics (active/inactive/total/max connection number) is also added when running the show service loadbalancer command.
For example:
show service loadbalancer
Loadbalancer Services Status:
L7 Loadbalancer : running
L7 Loadbalancer Status Information:
STATUS PID MAX_MEM_MB MAX_SOCK MAX_CONN MAX_PIPE CUR_CONN CONN_RATE CONN_RATE_LIMIT MAX_CONN_RATE
running 2604 0 2079 1024 0 0 50 43 0
L4 Loadbalancer Statistics:
MAX_CONN ACT_CONN INACT_CONN TOTAL_CONN
65536 245 537 782
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.117.6.30:80 wrr
-> 192.168.10.2:80 Masq 1 24 171
-> 192.168.10.3:80 Masq 1 25 169
TCP 10.117.6.30:443 wrr
-> 192.168.10.2:80 Masq 1 196 1
-> 192.168.10.3:80 Masq 1 0 196
B is correct. Refer to the same link https://kb.vmware.com/s/article/2122708
Load Balancer Virtual Machine information example
The output of the load balanced virtual server information command:
> show service loadbalancer virtual http-vip
———————————————————————–
Loadbalancer VirtualServer Statistics:
VIRTUAL http-vip
| ADDRESS [10.117.35.186]:80
| SESSION (cur, max, limit, total) = (0, 0, 1024, 0)
| RATE (cur, max, limit) = (0, 0, 100)
| BYTES in = (0), out = (0)
+->POOL http-pool
| LB METHOD leastconn
| LB PROTOCOL L7
| Transparent disabled
| SESSION (cur, max, limit, total) = (0, 0, 103, 0)
| BYTES in = (0), out = (0)
+->POOL MEMBER: http-pool/m1, STATUS: UP
| | STATUS = UP, MONITOR STATUS = default_http_monitor:OK
| | SESSION (cur, max, limit, total) = (0, 0, , 0)
| | BYTES in = (0), out = (0)
+->POOL MEMBER: http-pool/m2, STATUS: UP
| | STATUS = UP, MONITOR STATUS = default_http_monitor:OK
| | SESSION (cur, max, limit, total) = (0, 0, , 0)
| | BYTES in = (0), out = (0)
+->POOL MEMBER: http-pool/m3, STATUS: UP
| | STATUS = UP, MONITOR STATUS = default_http_monitor:OK
| | SESSION (cur, max, limit, total) = (0, 0, , 0)
| | BYTES in = (0), out = (0)
SnowBB is correct. I saw same information at the KB.