Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 863 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAN Link Failure after adding another internal NIC

pwerner
I'm currently evaluating Sophos UTM with the Home Edition installed on an ESXI 6 Server.

I have currently the following Setup:
eth0 -> Internal
eth1 -> WAN1
eth2 -> WAN2
eth3 -> WAN3

WAN1-3 are active/active/active uplink balanced which is working nicely.
Now i want to add another internal Network as eth4. As soon as i add eth4 in VMware WAN 1-3 are getting a link error. 

Even if i remove eth3(WAN3) from the VM and replace it with a new eth3 for the second internal network the WAN interfaces fail again.

What am i missing here?


This thread was automatically locked due to age.
Parents
  • 0
    Hi, and welcome to the User BB!

    This sounds like an ESXi problem or a hardware issue with the switch connected to the second LAN interface.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    Hi Bob,

    thanks for your reply, i haven't connected the physical port of the server to a switch yet. 
    I've only created another NIC (eth4) and added it to the Sophos UTM VM, haven't configured it in Sophos. Even if i deactivate eth4 in Sophos the problem persists.
Reply
  • 0 in reply to BAlfson
    Hi Bob,

    thanks for your reply, i haven't connected the physical port of the server to a switch yet. 
    I've only created another NIC (eth4) and added it to the Sophos UTM VM, haven't configured it in Sophos. Even if i deactivate eth4 in Sophos the problem persists.
Children
No Data
Unfiltered HTML