Max pppoe sessions #191
-
Hi, Have just run into a case where we are not able to go beyond 4096 sessions. At first thought it was the BNG, but checked and there is no limitation there. Is there a setting on bngblaster perhaps? Have checked but could not find any so far. many thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi, been digging deeper and not an obvious thing so far. Our current state on bngblaster: Notice the established count of 4037, howver DHCPv6 shows 4778. This is the session status on the BNG DUT: This is based from running bnglbaster with
{
"interfaces": {
"tx-threads": 8,
"tx-interval": 0.1,
"rx-threads": 8,
"rx-interval": 0.1,
"io-slots": 16384,
"network": {
"interface": "bond0",
"address": "100.127.1.2/24",
"gateway": "100.127.1.1",
"address-ipv6": "2001:db8:1::2/64",
"gateway-ipv6": "2001:db8:1::1",
"vlan": 100
},
"access": {
"interface": "bond0",
"vlan-mode": "N:1",
"outer-vlan": 702,
"type": "pppoe",
"stream-group-id": 1
}
},
"streams": [
{
"name": "general4",
"stream-group-id": 1,
"type": "ipv4",
"direction": "downstream",
"bps": 512000,
"length": 1450,
"network-interface": "bond0:100"
}
],
"sessions": {
"start-rate": 100,
"stop-rate": 100
},
"pppoe": {
"reconnect": true
},
"ppp": {
"mru": 1492,
"authentication": {
"username": "foo@lab.net",
"password": "testing",
"timeout": 3,
"retry": 5,
"protocol": "PAP"
},
"lcp": {
"conf-request-timeout": 1,
"conf-request-retry": 10,
"keepalive-interval": 30,
"keepalive-retry": 3
},
"ipcp": {
"enable": true,
"request-ip": true,
"request-dns1": true,
"request-dns2": true,
"conf-request-timeout": 1,
"conf-request-retry": 10
},
"ip6cp": {
"enable": true,
"conf-request-timeout": 1,
"conf-request-retry": 10
}
},
"dhcpv6": {
"enable": true,
"retry": 2
}
} Have looked into the radius setup, thought maybe it is getting throttled there, but nothing there so far. Any thoughts? thanks |
Beta Was this translation helpful? Give feedback.
-
hmm, so found it. the pool on the BNG DUT was too small to assign 5000 sessions. it does not fail in an obvious way to show local pool exhaustion ... Well, have clarified it in our UAT use cases to look specifically how pool exhaustion is flagged. thanks for all! |
Beta Was this translation helpful? Give feedback.
hmm, so found it. the pool on the BNG DUT was too small to assign 5000 sessions. it does not fail in an obvious way to show local pool exhaustion ...
Well, have clarified it in our UAT use cases to look specifically how pool exhaustion is flagged.
thanks for all!