Routing

Expand all | Collapse all

Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

Jump to Best Answer
  • 1.  Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

    Posted 04-26-2020 03:59

    Hi!

     

    The creation of Q-in-Q autoconf interface fails, but the VLAN-tags are recognised by the router.

    I tried that on ae- and xe-Interfaces with no luck. Also down-/upgrade of router firmware was not helpful.

    I do not find anything in the autoconf.log.

     

    show version > Model: mx204, Junos: 18.2R3-S3.11

     

    I get this error: BBE_AUTOCONF_P_SDB_CREATE_FAILED Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2

    (more log in the text below).

     

    If I create the Q-in-Q-VLAN manually everything works.

    I also tried the configuriation samples on the juniper pages and browsed trough this forum. Seems to be a very uniqe problem. But maybe it's just one simple typo...

     

     

    show configuration interfaces xe-0/1/5 
    flexible-vlan-tagging;
    auto-configure {
        stacked-vlan-ranges {
            dynamic-profile DYNPROF-VLAN {
                accept any;
                ranges {
                    any,any;
                }
            }
        }
        remove-when-no-subscribers;
    }
    mtu 1598;
    

     

     

    show configuration dynamic-profiles DYNPROF-VLAN 
    interfaces {
        demux0 {
            unit "$junos-interface-unit" {
                demux-source inet;
                proxy-arp;
                vlan-tags outer "$junos-stacked-vlan-id" inner "$junos-vlan-id";
                demux-options {
                    underlying-interface "$junos-interface-ifd-name";
                }
                family inet {
                    unnumbered-address lo0.0 preferred-source-address 192.168.0.244;
                }
                family inet6 {
                    unnumbered-address lo0.0 preferred-source-address 2002:1234::192:168:0:244;
                }
                family pppoe {
                    duplicate-protection;
                    dynamic-profile DYNPROF-PPPOE;
                }
            }
        }
    }

     

     

    bbe-smgd-debug          511 Apr 26 10:17:20.092820 BBEMG_UI_CLI_UNLOCK_SUCCESS                                  cli unlock success, lock cnt:0, ref cnt:0, lock tid:0x0a416900, my tid:0x0a416900
    bbe-autoconf-debug      512 Apr 26 10:17:21.014684 BBE_AUTOCONF_D_L2_ENQUEUE                                    Enqueuing packet to autoconf: ifd xe-0/1/5, ovid 3903, ivid 32, underlying ifl 0x00000000, packet 0x0d5c9400
    bbe-autoconf-prio       513 Apr 26 10:17:21.014693 BBE_AUTOCONF_P_L2_NO_PKT_TYPES_L3                            No packet types accepted for this ifd/vlan-id combination, sending to L3
    bbe-autoconf-info       514 Apr 26 10:17:21.014694 BBE_AUTOCONF_I_L2_SENT_TO_L3                                 Sending packet 0x0d5ca000 to L3
    bbe-autoconf-debug      515 Apr 26 10:17:21.014718 BBE_AUTOCONF_D_PRE_PACKET_RECEIVED                           Autoconf plugin processing packet 0x0d5c9400
    bbe-autoconf-info       516 Apr 26 10:17:21.014724 BBE_AUTOCONF_I_VIF_PROCEED                                   ifd xe-0/1/5 ovid 3903, ivid 32, wait_count 0, curr_pkt_time 1587896241 (0 seconds)
    bbe-autoconf-debug      517 Apr 26 10:17:21.014743 BBE_AUTOCONF_D_OOB_SESSION_STATE                             2592: ifd xe-0/1/5 vtag 3903 oob session state 0
    bbe-autoconf-prio       518 Apr 26 10:17:21.014780 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd (unknown) outer tag 3903 inner tag 32 session type 2
    bbe-autoconf-prio       519 Apr 26 10:17:21.014781 BBE_AUTOCONF_P_PRE_NO_SESSION                                Session create failed
    bbe-autoconf-debug      520 Apr 26 10:17:21.014781 BBE_AUTOCONF_D_POST_FAILURE                                  Vlan create failed: ifd xe-0/1/5, ovid 3903, ivid 32

     

     

     


    #auto-configureQ-in-Q


  • 2.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

     
    Posted 04-26-2020 04:05

    Hi,

     

    Do you have subscriber-mgmt enabled?

     

    set system services subscriber-management enable

    set chassis network-services enhanced-ip

     

     

     

     

     



  • 3.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

    Posted 04-26-2020 05:05

    Yes, subscriber-mgmt is enabled. I also rebooted with no effect. Same problem - auto-Interface not comming up.

     

    License usage: 
                                     Licenses     Licenses    Licenses    Expiry
      Feature name                       used    installed      needed 
      subscriber-accounting                 1            1           0    permanent
      subscriber-authentication             0            1           0    permanent
      subscriber-address-assignment         1            1           0    permanent
      subscriber-vlan                       0            1           0    permanent
      subscriber-ip                         0            1           0    permanent
      service-dc                            0            1           0    permanent
      service-accounting                    0            1           0    permanent
      service-qos                           0            1           0    permanent
      service-ancp                          0            1           0    permanent
      service-cbsp                          0            1           0    permanent
      scale-subscriber                      0        32000           0    permanent
      scale-l2tp                            0         1000           0    permanent
      scale-mobile-ip                       0         1000           0    permanent
      l2tp-inline-lns                       1            1           0    permanent
    

    This time with a DHCP-Request. As before I do not see nothing about xe-0/1/5 in autoconf.log

    bbe-autoconf-debug       30 Apr 26 12:02:54.641254 BBE_AUTOCONF_D_L2_ENQUEUE                                    Enqueuing packet to autoconf: ifd xe-0/1/5, ovid 3903, ivid 32, underlying ifl 0x00000000, packet 0x0d5aa000
    bbe-autoconf-debug       31 Apr 26 12:02:54.641276 BBE_AUTOCONF_D_PRE_PACKET_RECEIVED                           Autoconf plugin processing packet 0x0d5aa000
    bbe-autoconf-info        32 Apr 26 12:02:54.641283 BBE_AUTOCONF_I_VIF_PROCEED                                   ifd xe-0/1/5 ovid 3903, ivid 32, wait_count 0, curr_pkt_time 1587902574 (0 seconds)
    bbe-autoconf-debug       33 Apr 26 12:02:54.641301 BBE_AUTOCONF_D_OOB_SESSION_STATE                             2592: ifd xe-0/1/5 vtag 3903 oob session state 0
    bbe-autoconf-prio        34 Apr 26 12:02:54.641350 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2
    bbe-autoconf-prio        35 Apr 26 12:02:54.641351 BBE_AUTOCONF_P_PRE_NO_SESSION                                Session create failed
    bbe-autoconf-debug       36 Apr 26 12:02:54.641352 BBE_AUTOCONF_D_POST_FAILURE                                  Vlan create failed: ifd xe-0/1/5, ovid 3903, ivid 32


  • 4.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

     
    Posted 04-26-2020 05:27

    Are you brring up a DHCP Subscriberr or PPPoE?

    Your Vlan profile is nested with PPPoE only..

     

    Can you share output for the following:

     

    > show subscribers extenstive output

    > show configuration chassis

    > show configuration system configuration-database

    > monitor traffic interface xe-0/1/15

    > show config dynamic-profiles  DYNPROF-PPPOE

    > show configuration system services 

     

     

     



  • 5.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

    Posted 04-26-2020 05:39

    >Are you brring up a DHCP Subscriberr or PPPoE?

    >Your Vlan profile is nested with PPPoE only..

     

    I try with PPPoE (but there is also DHCP in VLAN3903.32 and 3903.31 which I am not focussing on yet).

     

    > show subscribers extenstive output

     

    show subscribers extensive                     
    Total subscribers: 0, Active Subscribers: 0

     

    > show configuration chassis

     

    show configuration chassis 
    aggregated-devices {
        ethernet {
            device-count 10;
        }
    }
    fpc 0 {
        pic 0 {
            max-queues-per-interface 4;
            port 0 {
                speed 40g;
            }
            port 1 {
                speed 40g;
            }
        }
        pic 1 {
            inline-services;
            max-queues-per-interface 4;
            port 0 {
                speed 10g;
            }
            port 1 {
                speed 10g;
            }
            port 2 {
                speed 10g;
            }
            port 3 {
                speed 10g;
            }
            port 4 {
                speed 10g;
            }
            port 5 {
                speed 10g;
            }
            port 6 {
                speed 10g;
            }
            port 7 {
                speed 10g;
            }
        }
    }
    network-services enhanced-ip;

     

    > show configuration system configuration-database

     

    show configuration system configuration-database 
    max-db-size 698343424;

    > monitor traffic interface xe-0/1/5

     

     

    Listening on xe-0/1/5, capture size 96 bytes
    
    12:32:01.062715  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:01.994518  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:02.997514  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:04.039052  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:05.091607  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:06.103696  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:07.048820  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:08.178770  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:09.080379  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:10.082822  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:12.322640  In IP truncated-ip - 530 bytes missing! [|ip]
    12:32:17.143178  In e8:0a:81:00:0f:3f > cc:cc:6c:3b:6b:8a, ethertype 802.1Q (0x8100), length 50: 
                             cccc 6c3b 6b8a e80a 8100 0f3f 8100 0020
                             0058 aaaa 0300 000c 2000 0178 ac74 0001
                             000a 7377 312e 6978 0003 001b 7366 7031
                             2d64 6973 7431 2e69 7823 372e 3339 3033
    12:32:17.493106  In 
            [|LLDP]
    12:32:21.082777  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:21.954039 Out 
            [|LLDP]
    12:32:22.155024  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:23.077222  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:23.969402  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:25.040768  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:26.163086  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:27.225123  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:28.287595  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:29.229664  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:30.121911  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:41.138136  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:42.110572  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:43.162979  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:44.165044  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:45.158182  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:46.056857  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:46.364799  In 
            [|LLDP]
    12:32:47.110820  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:48.173627  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:49.115776  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:50.048755  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:32:50.885907 Out 
            [|LLDP]
    12:33:01.043505  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]
    12:33:02.085683  In PPPoE PADI [Host-Uniq UTF8] [Service-Name "bng1"] [TAG-0x120 UTF8]

     

    > show config dynamic-profiles  DYNPROF-PPPOE

     

    show configuration dynamic-profiles DYNPROF-PPPOE 
    predefined-variable-defaults {
        input-filter ACCEPT-ALL-IPV4;
        input-ipv6-filter ACCEPT-ALL-IPV6;
    }
    interfaces {
        pp0 {
            unit "$junos-interface-unit" {
                actual-transit-statistics;
                no-traps;
                ppp-options {
                    chap;
                }
                pppoe-options {
                    underlying-interface "$junos-underlying-interface";
                    server;
                }
                keepalives interval 60;
                family inet {
                    rpf-check;
                    filter {
                        input "$junos-input-filter";
                    }
                    unnumbered-address lo0.0;
                }
                family inet6 {
                    rpf-check;
                    filter {
                        input "$junos-input-ipv6-filter";
                    }
                    unnumbered-address lo0.0;
                }
            }
        }
    }
    routing-options {
        rib "$junos-ipv6-rib" {
            access {
                route $junos-framed-route-ipv6-address-prefix next-hop "$junos-framed-route-ipv6-nexthop";
            }
        }
        access {
            route $junos-framed-route-ip-address-prefix next-hop "$junos-framed-route-nexthop";
        }

    > show configuration system services 

     

    show configuration system services 
    ssh;
    subscriber-management {
        traceoptions {
            file submgmt.log size 10m files 3;
            flag all;
        }
        enable;
    }


  • 6.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

     
    Posted 04-26-2020 05:58

    As you per monitor logs, look like there is no PADO pkt from MX.

    Since you're getting PADI pkt in monitor commmand, it means you vlan created and pkt is getting up to RE.

     

    Can you remove duplicate protection from vlan profile once, and then run > clear pppoe lockout

     

    After that, dial subscriber and run "show subscribers extensive | no-more | refresh 2"  at the same time to understand if the vlan goes active and to check subscriber state.

     

    and also share output for:

     

    show network-access aaa statistics authentication

     

     



  • 7.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

    Posted 04-26-2020 06:10

    I removed duplicate protection and cleared pppoe lockout.

     

    > Since you're getting PADI pkt in monitor commmand, it means you vlan created and pkt is getting up to RE.

    > As you per monitor logs, look like there is no PADO pkt from MX.

     

    Yes and it really tries to bring the interface up but that failes. So maybe thats why no talking back.

     

    If I set up the interface manually (it's deactviated at the moment) it communicates as expected:

    show configuration interfaces demux0.3932 
    ##
    ## inactive: interfaces demux0 unit 3932
    ##
    description "temp static subscriber subif";
    demux-source inet;
    proxy-arp;
    vlan-tags outer 3903 inner 32;
    demux-options {
        underlying-interface xe-0/1/5;
    }
    family inet {
        unnumbered-address lo0.0 preferred-source-address 192.168.0.244;
    }
    family inet6 {
        unnumbered-address lo0.0 preferred-source-address 2000:1234::192:168:0:244;
    }
    family pppoe {
        duplicate-protection;
        dynamic-profile DYNPROF-PPPOE;
    }

    Here the requested outputs:

     

    show network-access aaa statistics authentication 
    Authentication module statistics
      Requests received: 0
      Accepts: 0
      Rejects: 0
      Challenges: 0
      Timed out requests: 0

    I do not see any numbers going up here:

    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:17 UTC)---
    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:19 UTC)---
    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:21 UTC)---
    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:23 UTC)---
    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:25 UTC)---
    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:27 UTC)---
    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:29 UTC)---
    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:31 UTC)---
    Total subscribers: 0, Active Subscribers: 0
    ---(refreshed at 2020-04-26 13:04:33 UTC)---
    Total subscribers: 0, Active Subscribers: 0

     

     



  • 8.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

     
    Posted 04-26-2020 07:54

    Hi,

     

    revert config back interface to dynamic auto-configure.

     

    in the dynamic-profile, under the family inet, remove "lo0.0 preferred-source-address 192.168.0.244"

    and replace with family inet unnumbered-address $junos-loopback-interface.

    And for inet6, replace with family inet6 unnumbered-address $junos-ipv6-address. (and remove v6 if subscriber is not v6)

     

    Can you share the config of your lo0? Remove filter from lo0 if any for testing.

    Also share  >

     

    show system subscriber-management detail

    clear shmlog entries logname all

    dial subscriber..

    show shmlog entries logname all

     

     

     

     

     

     

     



  • 9.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

    Posted 04-26-2020 08:17

    > ... and replace with family inet unnumbered-address $junos-loopback-interface.

     

    while commit I get this error:

     

    error: routing-instance should be a variable in profile DYNPROF-VLAN
    error: foreign file propagation (ffp) failed

     

    So I just set family inet unnumbered-address lo0.0 and removed the rest including v6.

     

     

    show configuration interfaces lo0 
    unit 0 {
        family inet {
            filter {
                input-list PROTECT-RE-V4;
            }
            address 192.168.0.244/32 {
                primary;
                preferred;
            }
            address 123.234.5.0/32;
        }
        family inet6 {
            filter {
                input-list PROTECT-RE-V6;
            }
            address 2000:1234::192:168:0:244/128;
        }
    }

    after exporting that I removed the filters.

     

     

     

    show system subscriber-management detail 
    General:
        Graceful Restart     Disabled
        Mastership           Master
        Database             Available
        Standby              Disconnected
        Chassisd ISSU State  IDLE
        ISSU State           IDLE
        ISSU Wait            0
     
    Daemon        Pid     Recovery  Issu State          Issu Wait
    ------        ---     --------  ----------          ---------
    jl2tpd        6140    Done      IDLE                0        
    jpppd         6141    Done      IDLE                0        
    mobiled       6043    N/A       N/A                 N/A      
    dfcd          6102    Done      IDLE                0        
    smihelperd    6116    N/A       N/A                 N/A      
    l2ald         6082    N/A       N/A                 N/A      
    rpd           6081    Done      N/A                 N/A      
    cosd          6085    Done      N/A                 N/A      
    bbe-smgd      6147    Done      IDLE                0        
    dcd           6131    Done      N/A                 N/A      
    dfwd          6137    Done      N/A                 N/A      
    authd         6138    Done      IDLE                0        
    autoconfd     6113    Done      IDLE                0        
    jdhcpd        6139    Done      IDLE                0        
    pfed          6135    Done      IDLE                0        
    pppoed        6098    Done      IDLE                0        
    Total 16

     

    log                   entry              date_time event_id                                                     argument_values
    bbe-autoconf-debug        0 Apr 26 15:16:42.844582 BBE_AUTOCONF_D_L2_ENQUEUE                                    Enqueuing packet to autoconf: ifd xe-0/1/5, ovid 3903, ivid 32, underlying ifl 0x00000000, packet 0x0d5e8800
    bbe-autoconf-debug        1 Apr 26 15:16:42.855089 BBE_AUTOCONF_D_PRE_PACKET_RECEIVED                           Autoconf plugin processing packet 0x0d5e8800
    bbe-autoconf-info         2 Apr 26 15:16:42.855098 BBE_AUTOCONF_I_VIF_PROCEED                                   ifd xe-0/1/5 ovid 3903, ivid 32, wait_count 0, curr_pkt_time 1587914202 (0 seconds)
    bbe-autoconf-debug        3 Apr 26 15:16:42.866076 BBE_AUTOCONF_D_OOB_SESSION_STATE                             2592: ifd xe-0/1/5 vtag 3903 oob session state 0
    bbe-autoconf-prio         4 Apr 26 15:16:42.866110 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2
    bbe-autoconf-prio         5 Apr 26 15:16:42.876063 BBE_AUTOCONF_P_PRE_NO_SESSION                                Session create failed
    bbe-autoconf-debug        6 Apr 26 15:16:42.876064 BBE_AUTOCONF_D_POST_FAILURE                                  Vlan create failed: ifd xe-0/1/5, ovid 3903, ivid 32
    bbe-autoconf-debug        7 Apr 26 15:16:43.952564 BBE_AUTOCONF_D_L2_ENQUEUE                                    Enqueuing packet to autoconf: ifd xe-0/1/5, ovid 3903, ivid 32, underlying ifl 0x00000000, packet 0x0d5ea000
    bbe-autoconf-debug        8 Apr 26 15:16:43.952589 BBE_AUTOCONF_D_PRE_PACKET_RECEIVED                           Autoconf plugin processing packet 0x0d5ea000
    bbe-autoconf-info         9 Apr 26 15:16:43.952598 BBE_AUTOCONF_I_VIF_PROCEED                                   ifd xe-0/1/5 ovid 3903, ivid 32, wait_count 0, curr_pkt_time 1587914203 (0 seconds)
    bbe-autoconf-debug       10 Apr 26 15:16:43.952621 BBE_AUTOCONF_D_OOB_SESSION_STATE                             2592: ifd xe-0/1/5 vtag 3903 oob session state 0
    bbe-autoconf-prio        11 Apr 26 15:16:43.952661 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2
    bbe-autoconf-prio        12 Apr 26 15:16:43.952663 BBE_AUTOCONF_P_PRE_NO_SESSION                                Session create failed
    bbe-autoconf-debug       13 Apr 26 15:16:43.952664 BBE_AUTOCONF_D_POST_FAILURE                                  Vlan create failed: ifd xe-0/1/5, ovid 3903, ivid 32
    jl2tpd-debug             14 Apr 26 15:16:44.375340 stateSyncTimerExpiry                                         instance=0, timer expiry count=233520
    bbe-autoconf-debug       15 Apr 26 15:16:44.874583 BBE_AUTOCONF_D_L2_ENQUEUE                                    Enqueuing packet to autoconf: ifd xe-0/1/5, ovid 3903, ivid 32, underlying ifl 0x00000000, packet 0x0d580800
    bbe-autoconf-debug       16 Apr 26 15:16:44.874604 BBE_AUTOCONF_D_PRE_PACKET_RECEIVED                           Autoconf plugin processing packet 0x0d580800
    bbe-autoconf-info        17 Apr 26 15:16:44.874610 BBE_AUTOCONF_I_VIF_PROCEED                                   ifd xe-0/1/5 ovid 3903, ivid 32, wait_count 0, curr_pkt_time 1587914204 (0 seconds)
    bbe-autoconf-debug       18 Apr 26 15:16:44.874626 BBE_AUTOCONF_D_OOB_SESSION_STATE                             2592: ifd xe-0/1/5 vtag 3903 oob session state 0
    bbe-autoconf-prio        19 Apr 26 15:16:44.874655 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2
    bbe-autoconf-prio        20 Apr 26 15:16:44.874656 BBE_AUTOCONF_P_PRE_NO_SESSION                                Session create failed
    bbe-autoconf-debug       21 Apr 26 15:16:44.874657 BBE_AUTOCONF_D_POST_FAILURE                                  Vlan create failed: ifd xe-0/1/5, ovid 3903, ivid 32
    bbe-autoconf-debug       22 Apr 26 15:16:45.809349 BBE_AUTOCONF_D_L2_ENQUEUE                                    Enqueuing packet to autoconf: ifd xe-0/1/5, ovid 3903, ivid 32, underlying ifl 0x00000000, packet 0x0d582000
    bbe-autoconf-debug       23 Apr 26 15:16:45.809373 BBE_AUTOCONF_D_PRE_PACKET_RECEIVED                           Autoconf plugin processing packet 0x0d582000
    bbe-autoconf-info        24 Apr 26 15:16:45.809380 BBE_AUTOCONF_I_VIF_PROCEED                                   ifd xe-0/1/5 ovid 3903, ivid 32, wait_count 0, curr_pkt_time 1587914205 (0 seconds)
    bbe-autoconf-debug       25 Apr 26 15:16:45.809399 BBE_AUTOCONF_D_OOB_SESSION_STATE                             2592: ifd xe-0/1/5 vtag 3903 oob session state 0
    bbe-autoconf-prio        26 Apr 26 15:16:45.809432 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2
    bbe-autoconf-prio        27 Apr 26 15:16:45.809434 BBE_AUTOCONF_P_PRE_NO_SESSION                                Session create failed
    bbe-autoconf-debug       28 Apr 26 15:16:45.809434 BBE_AUTOCONF_D_POST_FAILURE                                  Vlan create failed: ifd xe-0/1/5, ovid 3903, ivid 32
    bbe-autoconf-debug       29 Apr 26 15:16:46.873407 BBE_AUTOCONF_D_L2_ENQUEUE                                    Enqueuing packet to autoconf: ifd xe-0/1/5, ovid 3903, ivid 32, underlying ifl 0x00000000, packet 0x0d583800
    bbe-autoconf-debug       30 Apr 26 15:16:46.873431 BBE_AUTOCONF_D_PRE_PACKET_RECEIVED                           Autoconf plugin processing packet 0x0d583800
    bbe-autoconf-info        31 Apr 26 15:16:46.873439 BBE_AUTOCONF_I_VIF_PROCEED                                   ifd xe-0/1/5 ovid 3903, ivid 32, wait_count 0, curr_pkt_time 1587914206 (0 seconds)
    bbe-autoconf-debug       32 Apr 26 15:16:46.873458 BBE_AUTOCONF_D_OOB_SESSION_STATE                             2592: ifd xe-0/1/5 vtag 3903 oob session state 0
    bbe-autoconf-prio        33 Apr 26 15:16:46.873492 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2
    bbe-autoconf-prio        34 Apr 26 15:16:46.873494 BBE_AUTOCONF_P_PRE_NO_SESSION                                Session create failed
    bbe-autoconf-debug       35 Apr 26 15:16:46.873494 BBE_AUTOCONF_D_POST_FAILURE                                  Vlan create failed: ifd xe-0/1/5, ovid 3903, ivid 32
    jl2tpd-debug             36 Apr 26 15:16:50.581946 stateSyncTimerExpiry                                         instance=0, timer expiry count=233640
    pfed-debug               37 Apr 26 15:16:56.272284 request-iflstats-full:                                       ifl-index: 67, gen-num: 132
    pfed-debug               38 Apr 26 15:16:56.273638 process-iflstats-full-msg:                                   if-index: 67, type: 0, stats-id: 0, flags: 0x102, bbe-flow: 0 iflset: 0
    pfed-debug               39 Apr 26 15:16:56.273738 ondemand-stats-data-create:                                  session_id=0, index: 67, bucket-index: 242, req-id: 3776, loc_offset: 0, filter_type:0
    pfed-debug               40 Apr 26 15:16:56.273740 bulkget-store-stats-request:                                 socket: 255, request-size: 24, buffer-offset: 8, msg-type: 5, msg-subtye: 3
    pfed-debug               41 Apr 26 15:16:56.273741 bulkget-allocate-buffer:                                     msg-type: 5
    pfed-debug               42 Apr 26 15:16:56.273741 bulkget-store-stats-request-flush-immediate:                 socket: 255, request-size: 24, buffer-offset: 32, msg-type: 5, msg-subtye: 3 inflight reqs:0
    pfed-debug               43 Apr 26 15:16:56.273766 bulkget-free-buffer:                                         msg-type: 5, buffer-offset: 32
    pfed-debug               44 Apr 26 15:16:56.273766 bulkget-send-request-to-pfe:                                 ipcconn-session: 0x90a5518, slot: 255, buffer-offset: 8, msg-type: 0 inflight reqs:1
    pfed-debug               45 Apr 26 15:16:56.273978 pfe-conn-process-msg:                                        ipcconn_session: 0x90a5518, type: 5, length: 160
    pfed-info                46 Apr 26 15:16:56.273981 bulkget-process-full-stats-ipv4-rx:                          ifl-index: 67, pkts: 0, bytes: 0
    pfed-debug               47 Apr 26 15:16:56.273981 process-full-stats:                                          ifl-index: 67
    pfed-info                48 Apr 26 15:16:56.274974 bulkget-process-full-stats-ipv4-tx:                          ifl-index: 67, pkts: 0, bytes: 0
    pfed-info                49 Apr 26 15:16:56.274974 bulkget-process-full-stats-ipv6-rx:                          ifl-index: 67, pkts: 0, bytes: 0
    pfed-info                50 Apr 26 15:16:56.274974 bulkget-process-full-stats-ipv6-tx:                          ifl-index: 67, pkts: 0, bytes: 0
    pfed-debug               51 Apr 26 15:16:56.274975 update-and-send-ondemand-iflstats-full:                      if-index: 67, request-id: 3776 iflset: 0
    pfed-debug               52 Apr 26 15:16:56.275010 update-and-send-ondemand-iflstats-full-add-element:          ifl-index: 67, peer-idx: 0 iflset: 0
    pfed-debug               53 Apr 26 15:16:56.275022 reconcile-iflstats-full:                                     ifl-index: 67, nbr-element-from-db: 3, nbr-element-from-pfe: 1
    pfed-debug               54 Apr 26 15:16:56.275023 reconcile-iflstats-full-found-match-full:                    ifl-index: 67, peer-idx: 0
    pfed-debug               55 Apr 26 15:16:56.275049 pfe-conn-process-msg-last:                                   ipcco_ses:0x90a5518, type:5, idx:0, slot:255 infli reqs:1 status:1 ifl_ind:67 resp late:0
    jl2tpd-debug             56 Apr 26 15:16:56.771134 stateSyncTimerExpiry                                         instance=0, timer expiry count=233760
    bbe-autoconf-debug       57 Apr 26 15:16:57.789716 BBE_AUTOCONF_D_L2_ENQUEUE                                    Enqueuing packet to autoconf: ifd xe-0/1/5, ovid 3903, ivid 32, underlying ifl 0x00000000, packet 0x0d5a9400
    bbe-autoconf-debug       58 Apr 26 15:16:57.789739 BBE_AUTOCONF_D_PRE_PACKET_RECEIVED                           Autoconf plugin processing packet 0x0d5a9400
    bbe-autoconf-info        59 Apr 26 15:16:57.789747 BBE_AUTOCONF_I_VIF_PROCEED                                   ifd xe-0/1/5 ovid 3903, ivid 32, wait_count 0, curr_pkt_time 1587914217 (0 seconds)
    bbe-autoconf-debug       60 Apr 26 15:16:57.789767 BBE_AUTOCONF_D_OOB_SESSION_STATE                             2592: ifd xe-0/1/5 vtag 3903 oob session state 0
    bbe-autoconf-prio        61 Apr 26 15:16:57.789803 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2
    bbe-autoconf-prio        62 Apr 26 15:16:57.789804 BBE_AUTOCONF_P_PRE_NO_SESSION                                Session create failed
    bbe-autoconf-debug       63 Apr 26 15:16:57.789805 BBE_AUTOCONF_D_POST_FAILURE                                  Vlan create failed: ifd xe-0/1/5, ovid 3903, ivid 32

     

     



  • 10.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP
    Best Answer

     
    Posted 04-29-2020 14:17

     

    The error below means that SDB entry for vlan couldn't be created due to SDB memory allocation failure:

    bbe-autoconf-prio        61 Apr 26 15:16:57.789803 BBE_AUTOCONF_P_SDB_CREATE_FAILED                             Error -2 ifd xe-0/1/5 outer tag 3903 inner tag 32 session type 2

    This part of your configuration looks a bit unusual:

    max-db-size 698343424;

     

    As the first step I'd suggest configuring this value and rebooting the router:

    set system configuration-database max-db-size 419430400

    If it doesn't help, you may want to enable bbe-smgd trace logs to investigate it further:

    set system processes smg-service traceoptions file jtac-bbesmgd.log
    set system processes smg-service traceoptions file size 100m
    set system processes smg-service traceoptions file files 20
    set system processes smg-service traceoptions level all
    set system processes smg-service traceoptions flag all

    In any case, please keep us updated on the results.

     

    Best regards,

    Sergii

    -------------------------------------------------------------------

    Please accept the solution if your problem is resolved Smiley Happy

    -------------------------------------------------------------------

     



  • 11.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

    Posted 04-29-2020 19:36

    Hi Sergii!

     

    Thank you very much, your recommondation

     

    set system configuration-database max-db-size 419430400

    did the trick! The creation of the vlans works now as designed 😉

     

    Is 419430300 a "ideal" setting for MX204?

    We will have around 30k subscribers on the router - pppoe/dhcp mixed.

     



  • 12.  RE: Juniper MX - auto-configure / auto-creation Q-in-Q fails for PPPoE and DHCP

     
    Posted 04-30-2020 00:29

    Hi inventer,

     

    I'm glad to hear that the issue has been resolved now! Unfortunately, MX204 is not mentioned here:

    https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/max-db-size-edit-system-configuration-database.html

     

    Essentially there is a contention for the shared memory between between subscriber-management and configuration database. If too much memory is reserved for the configuration database, subscriber-management won't function properly. Size of the configuration database may vary, but usually it's less than 100MB. The following command can be used to check it:

    lab@mx> show configuration | display set | match max-db
    set system configuration-database max-db-size 419430400
    
    lab@mx> show system configuration database usage
    Maximum size of the database: 370.50 MB
    Current database size on disk: 1.50 MB
    Actual database usage: 1.47 MB
    Available database space: 369.03 MB

    Best regards,

    Sergii

    -------------------------------------------------------------------

    Please accept the solution if your problem is resolved Smiley Happy

    -------------------------------------------------------------------