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

    Port OPT2 "no carrier" after rebooting SG-8860. Any way to diagnose the issue?

    Scheduled Pinned Locked Moved Hardware
    6 Posts 2 Posters 243 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.
    • P
      pfsosensai
      last edited by

      I'm wondering if I should just write that port off of if there's anything I can do to revive it? For the time being, I've moved the connection to OPT4 and it works ok. OPT2 has no lights - seems dead.

      Do they ever come back? Also, how do I look up the firewall rules on a disabled interface? I need to copy them over if I can't fix the port.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        It's unlikely to come back if the port is actually dead. You should check the ifconfig output though to make sure it's shown as UP and not just disabled.

        You don't need to copy firewall rules etc you can just re-assign the interface to a different NIC and all the rules will remain.
        So OPT2 is likely igb3. In Interfaces > Assign change it to igb5 (the default for OPT4). Remove OPT4 or assign it as the dead port.

        Steve

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

          Where can I see the ifconfig output? I don't see a networking log in the Status->logs, and there's no mention of ifconfig in the System->General log.

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            It's a CLI command so you can run it at the console via serial or SSH. Or you can run it from Diag > Command Prompt.

            Steve

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

              Well I'm not sure why - but another reboot seems to have brought the port back online.

              We were also having some general bandwidth / tcp connection stability issues that seem to have gone away. weird.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Hmm, yeah always worrying.

                I would check Status > Interfaces. Make sure you aren't seeing errors/collisions on that port.

                Could just be a bad cable or connection somewhere.

                Steve

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