05-09-2018 12:59 PM - edited 05-09-2018 01:00 PM
Hi,
We have migrated a PA500 500 config to a newly installed VM-100 (ver. 8.1) running as the only VM under a standalone ESXi 6.5 host (not in vSphere). All interfaces are assigned and I have verified the assignment of each by plugging and unplugging cables and checked the different vmnics' status. Furthermore all the VM-100 interfaces are correctly assigned to each VMWare virtual port groups and vSwitches.
However something is prohibiting traffic, when connecting a notebook directly to vmnic ports assigned to VM-100 interfaces with basic DHCP servers involved (no VLANs etc) I'm not able to receive an IP lease or ping the VM-100 interface.
What is the culprit? Do you have some white paper describing how to troubleshoot this situation? There must be something obvious I have missed.... Please comment.
regards Tor
05-09-2018 03:22 PM
Hello,
For the ping part, try th efollowing:
You migth also need associated security policies to allow the ping. To verify, put in a DENY all rule at the end and set it to log at session end so you can see which rule the ping is hitting.
For the DHCP issue, what is handing out the address?
Regards,
05-09-2018 10:59 PM
Thanks for the ping tips.
As of DHCP it is the VM-100. I use its standard DHCP server settings that have always worked.
Tor
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
