Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    ESXi how to?

    Scheduled Pinned Locked Moved Virtualization
    14 Posts 5 Posters 6.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nutt318
      last edited by

      biggsy,

      Yea, I found that I had to manually enter the interface name for each instead of doing the auto assign. So now that I've got my interface configured I've got a strange issue. For some reason both the wan and lan iterface have to be plugged into the same switch for me to access the admin page. Also for some reason at random times my ESXi server crashes while switching cables, not sure why but maybe you might have an idea. Here is the screen shot of my ESXi server after switching some network cables. Maybe 1 of my NIC's isnt fully supported?

      1 Reply Last reply Reply Quote 0
      • B
        biggsy
        last edited by

        nutt318,

        Yep,  I've never managed to get auto assign to work under ESXi.

        For some reason both the wan and lan iterface have to be plugged into the same switch for me to access the admin page.

        That's definitely not good.  Does this happen when you're swapping cables to get to the admin interface or to figure out which interface is which?

        What choices did you make when creating the VM - O/S, NIC type, etc?

        1 Reply Last reply Reply Quote 0
        • N
          nutt318
          last edited by

          Hi biggsy,

          Yea, I get that error trying to figure out which NIC is wan/lan. What is weird its random, one time I booted up the ESXi server without any cables connected to the NIC's and started pluging them in and the pink error. Another time everything was connected and I was unplugging cables and noticed the pink error.

          Anyways when I setup pfSense I choosed other linux OS 64bit

          As for the NIC type it says E1000.

          Any ideas?

          1 Reply Last reply Reply Quote 0
          • P
            podilarius
            last edited by

            one thing I have noticed with ESX and pfSense is that they are assigned in order.

            vnic0 - em0
            vnic1 - em1

            and so on. I personally have not run into a case where that is any different. I an not saying that one does not exist.

            1 Reply Last reply Reply Quote 0
            • B
              biggsy
              last edited by

              …I choosed other linux OS 64bit

              That could well be your problem then.  pfSense is FreeBSD.

              Choose Other > FreeBSD (64-bit) - assuming you are using the 64-bit and not the 32-bit pfSense.

              Podilarius,

              I don't disagree but the problem is really how to identify which vSwitch is presenting em0 to pfSense.  For example,
              my cable modem is connected to physical adapter vmnic1 and it's connected to vSwitch1 but that appears to pfSense as em0.  My LAN is vmnic3 and its connected to vSwitch2 which appears as em1.

              1 Reply Last reply Reply Quote 0
              • B
                biggsy
                last edited by

                Podilarius,

                Now I see what you're saying.  Under Edit Settings for the VM, Network adapter 1 = em0 and so on.

                Thanks for making me think about that.  It never occurred to me that it might be that simple.

                1 Reply Last reply Reply Quote 0
                • P
                  podilarius
                  last edited by

                  Yes, sorry about that. I should have not used existing VMWare speak to convey that I was just talking about order in the settings.

                  1 Reply Last reply Reply Quote 0
                  • L
                    luke240778
                    last edited by

                    strangely enough i just installed pfsense and have setup the interfaces and everything just works… pfsense works, i can still get to my ESXi through vSphere.. do i actually need to do anything with the NIC settings? it seems that it all just works...

                    1 Reply Last reply Reply Quote 0
                    • B
                      biggsy
                      last edited by

                      Congratulations.

                      If it isn't broken…  ;)

                      1 Reply Last reply Reply Quote 0
                      • L
                        luke240778
                        last edited by

                        :) agreed.. i just want to be sure that i havent got it setup wrong and have future problems

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.