@stephenw10 ended up factory resetting and rebuilding from scratch. Had to do factory reset it twice, but the behavior is now gone. Thank you. Mind giving some of comments upvotes? I am running into another issue which I am attempting to create another post on in a different section of the forum, but I am hitting the spam blocker.

I also purchased a heat sink for my SG2100MAX, I do not think it needed it but it helps keep it cool. Looks like the same vendor except mine is the 2242 M.1 [image: 1705774876059-img_0095.jpeg] I also got one for my pcie mini wireless card. [image: 1705774938458-screenshot-2024-01-20-at-00.12.40-resized.jpeg] My SG2100 uses passive cooling. With the minipcie wireless card and the SSD the heatsinks can go a long way to help in the California summer heat waves. We will see this summer. The same 2100 cpu is in the Raspberry PI and it will use CPU throttling if it gets to 80C. I am also going to add a heat sink on the memory and the cpu next week.

I just went through the same upgrade (my SG-1000 was a rock for the ~7 years I had it in use) and found this thread very helpful. After a few attempts, I was able to get a working xml that imported everything correctly into the SG-1100. I had a bunch of vlans with opt interfaces that needed to be re-mapped into the internal switch. I started by booting the SG-1100 and exporting the default config to look at side-by-side with my SG-1000 config. I decided to keep my interface mappings of <opt#> to vlan consistent, so I re-mapped the builtin OPT port on the SG-1100 (<if>mvneta0.4092</if>) to <opt0> in my xml file. Since the SG-1000 doesn't have this port, my initial conversion process left it unused In the <interfaces> and <vlan> sections, I merged the SG-1100 defaults with my custom interfaces/vlans for the custom interfaces, I changed all the <if> tags from cpsw* to mvneta* but kept the subinterface numbers the same for the vlans, I updated the interface names to match what the resulting data interface data I also had to copy the <switches> section out of the default SG-1100 export and populate the <vlangroups> and <swports> subsections with the proper port tags / pvids for my vlans Just sharing my notes in case anyone else is searching for help with the same upgrade.

@stephenw10 Yes, exactly. No traffic. The downward one never flashes. I'm going to try to get spf+ modules and install the community version because I'm going around in circles :(

Just an update - I swapped out the router last night, moved the main router to my desk with the intention of booting it up isolated and connected only to my laptop - but it failed to boot! Luckily I still had the recovery USB handy - so I just did a usb recovery and restored the config....so I guess that is one way to upgrade ;) thanks again for the suggestions. J

You are able to connect to the serial console? What do you see when you try to boot the USB drive? How does it fail? https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html Steve

Yup updates are always included. And in fact you do have TAC-Lite with any Netgate hardware so you can open a ticket for basic setup, config conversions, firmware requests etc. Steve

Just add ports 1 and 5 as tagged members on those VLANs in the switch config. [image: 1705272549921-screenshot-from-2024-01-14-22-48-58.png]

What NICs does the CE device have? If it only has assigned NICs that actually do exist in the 8200 then it will just try to use them rather than asking you to reassign them. Since you have Netgate hardware you can open a ticket with us and have the old config converted so it will import directly. https://www.netgate.com/tac-support-request Steve

@OhMyFlavors Yea seems like a faulty drive. Luckily it was still under warranty and was approved for RMA. Thanks Stephen for all your support. Much appreciated.

@dscheive said in SG-1100 too bright leds: like the underglow from some teenagers civic. Ha.

I would recommend just re-installing clean. 21.02 is a very old version and trying to upgrade to 23.09.1 from that will require several steps. Make sure you have a backup on the config. Steve

Nope you can always open a ticket for firmware requests like that.

That's a great idea! I may just get lucky with a spare board laying around with a last-ditch-effort on this. Much appreciated, Steve! Best regards, Michael

@stephenw10 et all I've been liaising with QSFPTek.com support team and they've been very helpful and have stated the Intel branded DAC cables should work "out of the box". They provide MBR details and a 5 year repair warranty on their DAC cables, which I believe is a solid warranty option. However the proof is in the pudding... I have ordered the DAC cables and will post an update on the functionality when I can.

It should be on there I can see the replies internally. I replied on the ticket. We finally replicated the issue and it looks to be how Squid is handling the SRV requests/records. Digging continues. Steve

Hmm, not much we can do if the serial/usb device isn't even detected.

The firmware update will default the boot device value in the BIOS but won't change anything on the drives. You should be able to see what device you're booting from currently using a combination of the commands: `glabel status' and 'mount -p' To change the boot device you need to set it in the BIOS setup using the serial console. Most importantly though you will only be able to upgrade the firmware there from 23.05.1. 23.09(.1) currently has a bug preventing that. So you if you have that or an earlier version installed to the other boot device you may be to boot to that and run the update. Or if you are running ZFS you can probably roll back to a BE snapshot from 23.05.1 Otherwise you may need to install 23.05.1 in order to run the firmware upgrade. Open a ticket with us to get the install image for that if you don't have one: https://www.netgate.com/tac-support-request Steve

If it's showing anything on the console it's not the CPU issue. It looks like it sees the boot device and is loading the boot loader but never and actually tries to load the kernel if that's all that ever shows. I would just reinstall clean from there if you have a config backup. Open a ticket to get the image: https://www.netgate.com/tac-support-request Steve

It can't open the file to write the notice. Since you had to pull the power the first thing I would do is run a manual fsck: https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html#manual-filesystem-check Steve