VMware Cloud Community
JaySMX
Hot Shot
Hot Shot
Jump to solution

VC showing AAM Ports not open... ESX host says they are.

I have a system up for an accredidation, otherwise I would apply the "If it works, leave it alone." rule to this. VC 2.0.2 and ESX 3.0.2. VirtualCenter does not show that the AAM client is open in the security section, however here is a snipped output of the esxcfg-firewall -q command:

Chain INPUT

dpts:2050:5000 state NEW

9 5740 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpts:2050:5000 state NEW

8 480 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpts:8042:8045 state NEW

1055K 262M ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpts:8042:8045 state NEW

1 48 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 state

Chain OUTPUT

dpts:2050:5000 state NEW

1460 2864K ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpts:2050:5000 state NEW

11574 694K ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpts:8042:8045 state NEW

1051K 261M ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpts:8042:8045 state NEW

0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:27000

Incoming and outgoing ports blocked by default.

Enabled services: CIMSLP CIMHttpsServer vpxHeartbeats AAMClient LicenseClient sshServer CIMHttpServer

That seems to show that the client service is enabled and the proper incoming and outgoing ports are open. HA is also functioning with no errors, which I would think would not be the case if the AAM client was unable to communicate with the VC server. Any ideas on how to get VC to agree with the ESX host on this??

-Justin
Reply
0 Kudos
1 Solution

Accepted Solutions
weinstein5
Immortal
Immortal
Jump to solution

As a friend of mine says - the VI Client lies - I would try restarting mgmt-vmware service - service mgmt-vmware restart - this should refresh the VI Client -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

View solution in original post

Reply
0 Kudos
4 Replies
weinstein5
Immortal
Immortal
Jump to solution

As a friend of mine says - the VI Client lies - I would try restarting mgmt-vmware service - service mgmt-vmware restart - this should refresh the VI Client -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
JaySMX
Hot Shot
Hot Shot
Jump to solution

Wouldn't a restart do the same thing? The host has been restarted multiple times since I noticed this, it comes up the same way each time.

Another thing I noticed, when I try to enable the AAM client through VC, I get this error: "Failure due to a malformed request to the server."

-Justin
Reply
0 Kudos
kjb007
Immortal
Immortal
Jump to solution

Is this a new config, or you just noticed? Try running refresh on the security profile section of the host config in virtual center. Sometimes, vc updates are manual at best regarding configs.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
JaySMX
Hot Shot
Hot Shot
Jump to solution

It turns out that restarting the service did in fact fix it. Strange since I had rebooted it before and it still displayed incorrectly.

-Justin
Reply
0 Kudos