Create fFW rules that blocked my Vcenter

[vmware3222]

Hi rvery one,

i changed my default fw rule to blocked and i don't access to Vcenter

i tried this issue but i have this message attached

Help me please

[larsonm]

403 is typically a result of bad credentials/authentication.

Are you using the correct credentials for NSX Manager?  Typically, the admin user with whatever password you configured.

[vmware3222]

Thank you for your response Larsonm

Now the message is 204: no contents

but i can't connect my VC

[larsonm · Accepted solution]

Via the API, query NSX Manager to list the existing firewall rules.  Verify that the rules are in fact cleared. 

Also, verify that the services on vCenter are started.

[vmware3222]

Thank you very much

why i can exclude VC from rules ?

[larsonm]

In the networking and security plug in, select the NSX Manager, and go to exclusion list.

This blog has pictures of the exact steps:

http://www.routetocloud.com/2014/05/create-firewall-rules-that-blocked-your-own-vc/