Configuring Access to the vCenter Server on Port 443 Using a Port-Forwarding Gateway

In this situation, your Commserve can reach your vCenter over port 443 without issue. However, your access node [xxx-ma01] (understanding you blanked out the name) is blocked from communicating with vCenter and needs to leverage the Commserve as a gateway to communicate with the vCenter, correct?

• Separately, if the Commserve is configured as the Access Node does the vCenter connection work?

Directly on the access node [xxx-ma01], if it’s running Windows, you can use netstat (say from Command Prompt: netstat -anob | find “9101”) to confirm that a Commvault executable is listening on port 9101.

If it reports nothing, you’ll need to review the TPPM configurations in your FwConfig.txt and FwConfigLocal.txt files on the Commserve and Access Node.

If it does report listening, still on the access node, you can attempt to telnet to IP 127.0.0.1 on port 9101 and see if the connection completes. If it completes, that’s a good sign that the route is being established.

Thank you.
I checked and you have right, there is no listening 9101 port on commserve.
This are Linux systems.

[root@ cs01 ~]#

[root@ cs01 ~]# netstat -an | grep 9101

[root@ cs01 ~]#

[root@ cs01 ~]# curl telnet://localhost:9101

curl: (7) Failed to connect to localhost port 9101: Connection refused

I have access to vcenter form commserve but media agent don’t have acess to this vlan with vcenter.

On CommServe FwConfigLocal.txt:

[incoming]

allowed_tppms=vcenter.waw.local443

On the MediaAgent (VSA), I have line I FwConfigLocal.txt file:

[outgoing]

xxx-ma01 cs01 remote_guid=A2410241-CEC9-4FE8-B03B-EE01EEE8FCD8 fallback=1 type=ondemand proto=httpsa cvfwd= cs01:8403 tppm=9101:vCenterhostname:443

On the FwConfig.txt there was no change, only I coped the line

xxx-ma01 cs01 remote_guid=A2410241-CEC9-4FE8-B03B-EE01EEE8FCD8 fallback=1 type=ondemand proto=httpsa cvfwd= cs01:8403