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

    Calling all "MR BEARDY'S" Help needed for config migration from 4 PORT 1GIG NIC to 2 SFP+ NIC

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 504 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.
    • T
      TerrenceTtibbs
      last edited by TerrenceTtibbs

      Before I crash my network for the 50th time and pull all of my hair out completely can someone advise me in clever retard language how to migrate my config from a 4 port NIC to 2 port 10gig SFP+ NIC.

      I don't remember having these issues before when going from 1 port to 4 port 1 gig NIC.

      Ok, current setup is as follow's

      Onboard ports
      bge0 = WAN - Tbase
      bge1 =WIFI Failover router Tbase

      4 port NIC
      igb0 = LAN(lagg0) 3 vlans LACP Tbase
      igb1 = LAN(lagg0) LACP Tbase

      igb2 = Lagg1 15 vlans LACP Tbase
      igb3 = Lagg1 LACP Tbase

      I don't want LACP on my 10 gig NIC as I want to save the port on my switch for other stuff.

      So I just want this config with my new 10 gig card

      Onboard ports
      bge0 = WAN Tbase
      bge1 = I was going to use as Management Access port Tbase

      New NIC
      mlxen0 = All vlans, the whole sha-bang
      mlxen1 = (Use later for LACP when I get another 10 gig switch with more ports)

      My config is rather extensive and I can't face sitting here for hours rebuilding it all from scratch as I have forgot how I even did half of it.😨

      So I was thinking to DELETE WIFI failover on bge1 to free the port up for temporary migration.

      Create duplicate VLANS on the bge1 interface and assign the new VLANS to the interface.

      Then configure a Trunk port on my core switch.

      Run a cable from bge1 to Trunk port on core switch.

      Reboot Pfsense with the new 10gig NIC (I am using Dell R220 so only have 1 PCIE slot)

      Wait for Pfsense to have a fit when it can't find the old interfaces.

      bge1 should be ok and let me login to GUI.

      Do I need to Re create all the VLANS again 🙄
      OR
      Assign them to the new melx0 interface?

      Leave management VLAN on bge1.

      What do you guys think?

      Also I am now without a port for my WIFI backup router. any ideas? should I sacrifice the bge1 port for dedicated management VLAN and use it for the WIFI router?

      T 1 Reply Last reply Reply Quote 0
      • T
        TerrenceTtibbs @TerrenceTtibbs
        last edited by TerrenceTtibbs

        @terrencettibbs Ooh Aah Cantona!!!

        I did it. As there is an apparent insufficient supply of MR BEARDY'S left in the world to answer my post, I thought I would give it a go and I must say I am rather impressed with myself.

        Here is the procedure that I am sure you can adapt but it gives you an idea. The main thing here is not locking yourself out of the GUI. I have over 150 ports to deal with across my network switches so I was quite impressed.

        Migrating config from 4 port Tbase NIC to 2 port 10 gig fibre

        Make trunk port on core switch for all vlans

        Connect igb1 to trunk port on switch

        1. delete WAN2 on bge1

        2. Create new vlans on bge1, replicate what was on Lagg0 and lagg1 (Pfsense docs, never move vlans over from an interface, create a new one again)

        3. Assign the new vlans in interface assignments

        4. Delete the old vlans on old lagg interfaces

        5. Delete lagg1

        6. Delete all vlans on lagg0 once all new vlans are assigned to gbe1 so you don't lock yourself out of GUI

        7. Delete lagg0

        Everything now should be assigned to bge1

        Wan still assigned to bge0

        1. Remove old Tbase NIC and install new 10 gig Card. Reboot Pfsense

        2. Create all new Vlans again and assign them to new mlxen0 interface.

        reboot
        done!

        Hope this helps!

        P 1 Reply Last reply Reply Quote 1
        • E
          e-1-1
          last edited by

          So the secret sauce is having the control plane on redundant links and the data plane as well. Plus having one active at all times :)

          1 Reply Last reply Reply Quote 1
          • P
            ProperCactus Rebel Alliance @TerrenceTtibbs
            last edited by

            @terrencettibbs said in Calling all "MR BEARDY'S" Help needed for config migration from 4 PORT 1GIG NIC to 2 SFP+ NIC:

            As there is an apparent insufficient supply of MR BEARDY'S left in the world to answer my post, I thought I would give it a go and I must say I am rather impressed with myself.

            FKN GOLD 🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣

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