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

    Having issues with the Netgate SG-3100 connecting to an Ubiquiti EdgeSwitch

    Scheduled Pinned Locked Moved General pfSense Questions
    11 Posts 4 Posters 677 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.
    • B
      bitttybit
      last edited by

      I have an EdgeSwitch connected to an EdgerouterX. Everything works fine. I recently bought an SG-3100 Negtate box and am going to use it as my router. The EdgerouterX will be replaced with this SG-3100.

      When I swapped out the EdgerouterX for the SG-3100, the the Edgeswitch was not detected. The light on the LAN port ( the one that connects to the switch ) does not light up. I followed the "Getting Started"  https://www.netgate.com/docs/pfsense/sg-3100/getting-started.htmlNetgate guide to configure the SG-3100. I also confirmed that this LAN port works by connecting it to my laptop. It works fine. What else needs to be done to get the EdgeSwitch to work properly?

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        I don't know that a pfSense forum is going to be the best place to get help with your edgeswitch.

        All 4 LAN ports on the SG-3100 are expecting to be connected to an untagged switch port by default.

        What port are you connecting to?

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

          I've tried LAN ports 2 and 3. Both don't connect to the switch

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Are you running pfSense 2.4.3 on the SG-3100? Define "Don't connect" - as in no carrier? Is the edgeswitch port hard-set to something other than auto-negotiate?

            Might be seeing some weird auto-mdx issue. Try a good, 8-conductor crossover cable to see.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

              @Derelict:

              Are you running pfSense 2.4.3 on the SG-3100? Define "Don't connect" - as in no carrier? Is the edgeswitch port hard-set to something other than auto-negotiate?

              Might be seeing some weird auto-mdx issue. Try a good, 8-conductor crossover cable to see.

              • Yes I'm running pfSense 2.4.3 on the SG-3100

              • What I mean by "don't connect" is that none of the green led lights on RJ45 jack on the SG-3100 light up. The switch does not work when plugged into the SG-3100 router.

              • The port is configured on auto-negotiate.

              • I've tried a good 8-conductor crossover cable.

              When I try the exact same setup and exact same Ethernet cables with and EdgerouterX router instead of the Netgate SG-3100, the EdgeSwitch works fine. As soon as I replace the EdgerouterX with the SG-3100, the EdgeSwitch no longer works as a switch. Nothing plugged into the switch gets connected the WAN.

              1 Reply Last reply Reply Quote 0
              • curtisgriceC
                curtisgrice
                last edited by

                are you able to ssh into the switch and see if there are any logs/console output wen plugging/unplugging?

                Slow code? Sounds like a good reason to buy more hardware!

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate
                  last edited by

                  Must be some sort of auto-neg problem with that switch. Works fine on everything I have tried. But I don't have one of those. Nobody has reported the same as you are seeing as far as I know.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  1 Reply Last reply Reply Quote 0
                  • SammyWooS
                    SammyWoo
                    last edited by

                    Bottom line: Dark LED=no Layer 2.  No layer 2 the rest doesn't matter. Are the boxes next to each other and separated by a single patch cable or are there are wall cabling in between?  Very disconcerting, more layer-2 issues in the forum than I had expected gone by the way of polio.

                    If u use multiple-LAN, something tells me to tell you to plug one LAN port only on the 3100 and see if lights.

                    The EdgeSwitch is not a POE-fed device is it? because that would be embarrassing-to-the-max.

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      Connect the a known-good, 8-conductor patch cable between OPT1 and one of the switch ports (not two of the switch ports as that will create a loop.)

                      Does link come up on both?

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                        Arghh. So it did end up being the patch cable. The RJ45 jack was not seating properly in the SG-3100, but somehow had no problems in the EdgerouterX. Thank you for taking the time to help fix this obvious yet un-obvious problem.

                        1 Reply Last reply Reply Quote 0
                        • SammyWooS
                          SammyWoo
                          last edited by

                          Sammy to user:  Plug in the RJ45 cable, it MUST go in with a SOLID POSITIVE CLICK and no mushiness.

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