About max-db-size, you can have a look at KB34539 too, which explain how to configure tomcat for the first time (basically you configure subscriber-management and the max-db-size, reboot, remove the max-db-size conf, reboot again).
[Subscriber Management] Enhanced subscriber management failing to commit when configured for the first time
However I think that the db size more dynamic in more recent JunOS releases and that dealing with this is not longer needed.
But it's not your problem here actually...
------------------------------
Olivier Benghozi
------------------------------
Original Message:
Sent: 06-16-2025 05:37
From: Anonymous
Subject: MX BNG
This message was posted by a user wishing to remain anonymous
Thanks for the reply, never heard of this Tomcat subscriber architecture before your KB. Why is the database max size needed what does this do?
Original Message:
Sent: 06-13-2025 03:21
From: WOJCIECH JANISZEWSKI
Subject: MX BNG
Hi,
I'd start with the following required BNG configuration in Junos 15.1+ (see KB31899):
set chassis network-services enhanced-ip
set system services subscriber-management enable
set system configuration-database max-db-size 300m
set system dynamic-profile-options versioning
Regards,
Wojciech
Original Message:
Sent: 06-12-2025 07:51
From: Anonymous
Subject: MX BNG
This message was posted by a user wishing to remain anonymous
Hi All,
I've been tasked with upgrading an MX10 running v11.7 to an MX204 running v21.1 to act as a BNG. I used the existing config from the mx10 on the mx204 and it seems to take it with no errors. Long story short it uses stacked vlans, dynamic profiles and radius to deal with PPPoE subscibers all with licensing that juniper confirmed.
When I put the MX204 in live environment nothing works. I think i have narrowed it down to the interface that does the auto-configuration for the stacked vlans and triggering the dynamic profile because no demux interface is created.
This is the part i think isn't working and i can confirm i see the PADi request on the stacked vlan interface. Am i correct that the demux interface should be the next step and this would create even if the license was wrong or radius wasnt working?
This is a snippet of my config but can post more if required as i'm a little unfamiliar with the order junos processes everything regards to PPPoE, dynamic-profiles and the dreaded licensing.
set interfaces xe-0/1/2 description "PPPOE Subscriber Management"
set interfaces xe-0/1/2 stacked-vlan-tagging
set interfaces xe-0/1/2 auto-configure stacked-vlan-ranges dynamic-profile svlan-profile accept pppoe
set interfaces xe-0/1/2 auto-configure stacked-vlan-ranges dynamic-profile svlan-profile ranges 1-4094,1-4094
set dynamic-profiles svlan-profile interfaces demux0 unit "$junos-interface-unit" vlan-tags outer "$junos-stacked-vlan-id"
set dynamic-profiles svlan-profile interfaces demux0 unit "$junos-interface-unit" vlan-tags inner "$junos-vlan-id"
set dynamic-profiles svlan-profile interfaces demux0 unit "$junos-interface-unit" demux-options underlying-interface "$junos-interface-ifd-name"
set dynamic-profiles svlan-profile interfaces demux0 unit "$junos-interface-unit" family pppoe dynamic-profile PPPoE-Profile
Any help appreciated !