Does not connect to switch after switch reset
-
@stephenw10
Here are the sysctls:
sysctl hw.igc.txtNow I did a test by changing PfS to use igc.2 in place of igc.1 attached are resulting files.
After reboot.txt
After unplug igc.2 and plug back in.txtAs you will notice I experienced the same issue.
Thanks for all your help.
-
Hmm, looks near identical to any igc port I have here.
It does that when connected to anything? A host directly for example?
-
@stephenw10
I will check that in the morning. -
@stephenw10
Ran the test with my laptop (intel nic) same result. See attached
Log 12APR23-a.txt -
I'm no FreeBSD/pfSense boot-log guru.
But wasn't it an 8-port Qotom ?I only see it detect igc0..igc4 ... where are the last 3 net IF's ?
Could it be bad hw ?
/Bingo
-
@bingo600
I think that's what I said early on but it is a 5 port. -
Can you get the log covering it start to fail after it has been stable?
So showing what is logged when you first disconnect and reconnect the cable.
-
@stephenw10
The file show a fresh boot through disconnect and reconnect then another fresh boot to bring everything back up.
Log 12APR23-b.txt -
Hmm, the only thing of any significance I see there is that when the interface comes up after boot it does so before check_reload_status runs. Later the order is reversed and the link bounces. However that's no different to the igc NICs in the 6100 or 4100.
Are you able to try a 2.7 snapshot there? It has slightly more recent code. I'm not aware of any updates that would affect igc but there may be something.
I can only imagine it has a different PHY and that is somehow seeing the link change.
-
@stephenw10
I haven't given up. I got really busy and haven't had time to get back to fixing the problem. What I have decided to do is to format the drive and start over completely fresh. I didn't have anything setup that was beyond just getting on the internet so I have nothing to lose. If I remember right the problem started when I did a reset of the system and had it load factory defaults. But those defaults didn't include a few firewall settings which I entered myself. I can only imagine when I put in the firewall settings I messed something up. I believe we have more than proven the hardware is not the problem.I hope I can get that done this week. I'm still swamped but just maybe I can get an hour and get this done.
-
@stephenw10
Sorry it took so long to get back to this. I did a complete reinstall of pfsense and now everything works as it should. No more port not reconnecting after a physical disconnect and reconnect. So, as I believed previously there was something not right in the settings when I tried to have pfsense go back to factory settings which wiped out all the firewall rules. My attempt to recreate those rules I believe is what broke things.Thank you so much stephenw10 for your help. I learned alot working with you.
-
Ah, good result.
