Kkula
Browse Questions » Industrial Edge: vmware industrial edge virtual Unit Link Issue

About User

Siemens Self Support

Questions Asked: 37.9K

Answers Given: 32

Statistics

Tags

0
  • Open
Siemens Self Support
Asked:12 Oct 2025

Industrial Edge: vmware industrial edge virtual Unit Link Issue

I configured the two industrial edge virtual machines on VMware ESXi: management and virtual device.
On the one hand, for IEM there is no connectivity problem. On the other hand, the IED is not reachable (ping test) only from some corporate network segments (VLAN).
In particular, the machine can be reached in the early stages of the boot and then lose connectivity after a few minutes. Please note: only from some network segments, while others remain easily accessible.
A troubleshooting activity has already been performed on the company network and no issues have been revealed, so much so that, as written above, the machine is reachable in the early boot phases.
I suppose it is a conflict with the application network that activates some loops or phenomena of "protection" against requests from certain IP addresses.
How to fix it? What can I control on the industrial side and what on the VMware side?
Thank you

#sosflex #Industrial Edge #siemens
1Answers 14Views 0Votes
0 Likes 0 Favourites 0 Followers 0 Comments
Answers(1)
Siemens Test Added an Answer on12 Oct 2025

Industrial Edge Device Connectivity Issue

It sounds like you're experiencing intermittent connectivity issues with your Industrial Edge Device (IED) after boot, specifically from certain VLANs, suggesting a network-related conflict. Here's a breakdown of troubleshooting steps, split between the Industrial Edge/VMware side and potential network considerations:

Industrial Edge & VMware Side Checks:

  • Firewall Configuration: Verify the IED's firewall (within the virtual machine) isn't blocking traffic after the applications start. Check for dynamically added rules that might be causing the issue.
  • Network Configuration: Double-check the IED's network configuration (IP address, subnet mask, gateway, DNS) within the VM. Ensure consistency with your corporate network.
  • VMware Network Settings: On the ESXi host, review the virtual switch configuration for the IED's VM. Confirm VLAN tagging is correct and consistent across the network. Inspect vSwitch port groups for any configured security policies.
  • Resource Contention: Although less likely, monitor CPU and memory usage within the IED VM. High resource utilization might cause temporary network hiccups.
  • Logs: Examine IED application logs and VMware logs (vmkernel.log, etc.) for any error messages around the time connectivity is lost.

Network Considerations (Collaboration with Network Team):

Since your network team found no immediate issues, focus on timing. The fact that it works briefly suggests a dynamic element. Consider:

  • MAC Address Learning: Ensure your switches are learning the IED's MAC address correctly and consistently.
  • ARP Issues: Investigate potential ARP conflicts or caching problems on the affected VLANs.
  • Security Appliances: Check for any security appliances (IPS/IDS, firewalls) that might be inspecting traffic and reacting to the IED's behavior *after* it's fully booted. This is your "protection" hypothesis.

For further assistance and detailed troubleshooting guides, please refer to these resources on SiePortal:

0