VMware Networking Community
rajeevsrikant
Expert
Expert

Last publish operation failed on host XXXXX - DFW

In NSX DFW I am getting the below error message

Last publish operation failed on host XXXXX - DFW

The NSX Manager to Firewall Agent - Down

For the host XXXXX the firewall policies are not pushed. I checked the firewall status is running & I know how to resolve it. There are no communication block issue like Firewall blocking or something

But the question is how to find out by when this problem is started on this particular host. What logs should I check & confirm why this has happened.

What could be the reason to this & track the relevant logs to this.

Tags (1)
Reply
0 Kudos
7 Replies
bayupw
Leadership
Leadership

- check for system events. Network & Security > NSX Managers > Monitor > System Events. You can filter on vShield Firewall Module, see below screenshot

pastedImage_0.png

- make sure time is sync, check NTP

- check for nsx manager log, show manager log from nsx manager, you can search for the time based on system events

- vsfwd.log

- esxi host vmkernel.log if you still can't find anything especially around vsip kernel module logs

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw
Reply
0 Kudos
rajeevsrikant
Expert
Expert

Thanks.

I ran the below command

esxcli network ip connection list | grep 5671

The output shows closed instead of established.

What could be the reason ?

Reply
0 Kudos
bayupw
Leadership
Leadership

Which NSX version are you using?

Check if you are having this issue vsfwd connection to the NSX Manager fails (2146873) | VMware KB

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw
Reply
0 Kudos
rajeevsrikant
Expert
Expert

initially the hosts were running 6.2.2 . NSX Manager & controllers were running on 6.3.2

I upgrade the hosts to 6.2.2 to 6.3.2 yesterday & after that the issue was fixed

Reply
0 Kudos
bayupw
Leadership
Leadership

Were you having the issue when running NSX 6.2.2 on the hosts?

How about ESXi host version? Did you do any upgrade/patch on the ESXi that fixed the issue?

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw
Reply
0 Kudos
rajeevsrikant
Expert
Expert

Yes the hosts were running on NSX version 6.2.2

The ESXi hosts were running 6.0 U2.

I just upgraded the NSX version to 6.3.2 after that it got resolved.

Or may be because of reboot during the upgrade the issue is resolved.

Reply
0 Kudos
rajeevsrikant
Expert
Expert

Can i confirm that this is due to bug in NSX 6.2.2 version or is it related to NSX version & ESXi compatibility ?

Is this addressed in NSX 6.3.2

Reply
0 Kudos