A1SAi-2750F nmbclusters limit reached
-
Open shell, edit boot/loader.conf config file to increase MBUFs (say 512000) and restart
-
I dont see that in the file.
-
Just add the line….I'm on a tablet so cant check exact spelling etc but it should be something like
kern.ipc.nmbclusters="512000"
Save and restart.....you should be good then.
-
Seems to be working thank yoU!
-
don't add it to /boot/loader.conf …. it'll get overwritten by updates.
https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards
be sure to add it to /boot/loader.conf.local
-
I did this, Thank you very much for the help!
-
What causes more of these to get used? I have never seen my usage budge since I first installed PFSense. I changed it to 1,048,576 because a PFSense doc recommended this for high memory systems with 1Gb+ interfaces, and that increased my usage by a small amount.
Then I hear about people running out of them. Is it because they aren't being returns quickly enough?
-
high CPU core count for one thing….
-
What causes more of these to get used?
The Intel igb driver, by default, sets up 1 queue per CPU core per NIC. The C2750/2758 Rangeley boxes have 8 cores & 4 NICs.
I ran into the same issue with my boxes at work which have (8) logical cores, (12) igb NICs, and (2) ix NICs. You can either restrict the number of cores, the number of queues, or raise nmbclusters.
-
What causes more of these to get used?
The Intel igb driver, by default, sets up 1 queue per CPU core per NIC.
… in pfSense 2.2. (Which is the correct default.)
The C2750/2758 Rangeley boxes have 8 cores & 4 NICs.
C2750 is Avoton, not Rangeley.
I ran into the same issue with my boxes at work which have (8) logical cores, (12) igb NICs, and (2) ix NICs. You can either restrict the number of cores, the number of queues, or raise nmbclusters.
raising nmbclusters is, by far, the best approach here.