Junos OS

Expand all | Collapse all

Recurring log entry on MX running as PWHT PPPoE BNG

Jump to Best Answer
  • 1.  Recurring log entry on MX running as PWHT PPPoE BNG

    Posted 09-07-2018 10:21

    I have an MX running several pseudowires (head-end termination "ps" interfaces) for PPPoE termination and I get entries in my log like this *all* the time:

     

    if_pfe_pppoe_iflconfig_tlv: ps16.1073743378: underlying interface configurable only on a pppoe ifl

     

    Can anyone explain why this is happening?   PPPoE is working fine, but is there a way I can stop this particular log entry at the source without just filtering it?



  • 2.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

     
    Posted 09-07-2018 10:32

    Hi Sean,

     

    What JUNOS release you're on?

     

     



  • 3.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

     
    Posted 09-07-2018 11:07

    Sean,

     

    I believe you should be getting these logs when subscriber logs out or log in. The log basically indicates that ps driver is processing pppoe tvl which it should not, thus the log message. The tlv(s) on pppoe ifl should be handled by pppoe driver.. there is known bug in this area.. may i know what JUNOS version your running?

     

     

     

     



  • 4.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

    Posted 09-07-2018 13:35

    I am on 14.2R8.4.



  • 5.  RE: Recurring log entry on MX running as PWHT PPPoE BNG
    Best Answer

     
    Posted 09-07-2018 19:30

    Hi,

     

    The logs were orginally reported in JUNOS 13.3R6 and was later fixed in 14.1X50 branches and in subscriber qualified builds tracked via PR 1090944. The fix as i mentioned in previous post - the tlv(s) on pppoe ifl would be handled by pppoe driver..(instead of ps)

     

    You must note that JUNOS 14.2R8 (or matter of fact 14.2 branch) is NOT qualified for any of the subscribers use case.

    For now, you can filter out these logs, and would recommend upgrading to JUNOS 16.1R7-S1 or the latest 17.3R3-S1 for subscriber use.

     



  • 6.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

    Posted 09-27-2018 10:13

    I have not tried 16 or 17, however I did try running 15.1 on an MX104 running subscriber services and apparentley in version 15, they completely re-vamped the subscriber management.  Anyway, it ran for one evening fine and then the next day the subsciber-mangement was crashing/core-dumping every few minutes.  I had to revert back to 14.2.

     

    Where can I find information on subscriber mangement and JunOS versions?  I had no idea 14.2 is not suitable for subscriber management....where is that information?



  • 7.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

     
    Posted 09-27-2018 19:47

    Subscriber management has been redesigned from junOS 15.1R3 onwards enhancing scale, performace and to support higher cps(call per second) subscriber login rate.

     

    In a dual routing engine setup, after upgrading from previous builds such as Junos 12.3, 13.3, 14.1x50 or on a fresh install of the Junos Subscriber Management build, the system must be rebooted. Refer to Configuring Junos OS Enhanced Subscriber Management.

     

    For initial setup, operators normally follow Juniper's tech document, Configuring Junos OS Enhanced Subscriber Management.  However in dual routing-engine setup, due to certain misconceptions, operators may not follow the complete procedure in order for the router to enable Enhanced Subscriber Management features and this can cause router to be unstable. May I know what was the exact junos version in 15.1 branch?

     

    As i mentioned earlier, NOT all junOS version are quailfied for subscribers-mgmt used. Since you're currently non quailfied subscriber-mgmg build, i would recommend that you reach out to local juniper accounts team to evaluate your current subscriber related config and suggest JunOS version accordingly.

     

    Following are subscribers-mgmt quailfied:

     

    JUNOS 15.1R4 onwards: (15.1R5, 15.1R6, 15.1R7)

    JUNOS 16.1R4 onwards: (16.1R5, 16.1R6, 16.1R7)

     

    If you ask me or JTAC (me again), I would recommend following JUNOS for subscribers-mgmt use:

    JUNOS: 16.1R7, 17.3R3, 17.4.R2

     

    Note1: 15.1 branch is going be EoL soon.

    Note2: Use the latest SR JunOS of an mainstream branch cause its includes the most recent bug fixes.

     

    Coming back to the orginal post, its known bug condition that i've explained in previous posts.

    Those logs are not harmful and you can filter them using KB9382 or resolve by means of S/w upgrade.

     

     

     

     

     



  • 8.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

    Posted 09-28-2018 10:04

    The version I had tried was 15.1R6.7.  It was on an MX104 without a redundant RE.



  • 9.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

     
    Posted 09-29-2018 20:52

    Temporarily to mitigate, KB on “How to prevent certain syslog messages from being written to the log file” https://kb.juniper.net/InfoCenter/index?page=content&id=KB9382



  • 10.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

     
    Posted 09-29-2018 21:01

     


    @python@ python wrote:

    Temporarily to mitigate, KB on “How to prevent certain syslog messages from being written to the log file” https://kb.juniper.net/InfoCenter/index?page=content&id=KB9382


     

    Hello python - what's the point of rewriting the same information which is already provided???

    Hope you read the complete thread before posting.

     

     



  • 11.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

     
    Posted 09-30-2018 22:56

    My bad! Really, I missed it bro! I was burning the midnight oil 😞

     

     



  • 12.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

    Posted 11-26-2018 14:08

    karand,


    On the MX204, what should the max-db-size be set to when running subsciber-management?  I am running 17.2R4 on it.  The docs say "no more than 300MB if you have <32GB ram" -- how do I properly decide that?

     

    Also, the specsheet for the MX204 says it has 32GB RAM, however my MX204 says 16GB:

     

    # run show chassis routing-engine
    Routing Engine status:
        Temperature                 46 degrees C / 114 degrees F
        CPU temperature             46 degrees C / 114 degrees F
        DRAM                      16341 MB (16384 MB installed)

     

    # run show version
    Hostname: dnvrco-cmfl-mx204-1
    Model: mx204
    Junos: 17.4R2-S1.2
    JUNOS OS Kernel 64-bit  [20180814.8630ec5_builder_stable_11]
    JUNOS OS libs [20180814.8630ec5_builder_stable_11]
    JUNOS OS runtime [20180814.8630ec5_builder_stable_11]
    JUNOS OS time zone information [20180814.8630ec5_builder_stable_11]
    JUNOS network stack and utilities [20181003.235426_builder_junos_174_r2_s1]
    JUNOS libs [20181003.235426_builder_junos_174_r2_s1]
    JUNOS OS libs compat32 [20180814.8630ec5_builder_stable_11]
    JUNOS OS 32-bit compatibility [20180814.8630ec5_builder_stable_11]
    JUNOS libs compat32 [20181003.235426_builder_junos_174_r2_s1]
    JUNOS runtime [20181003.235426_builder_junos_174_r2_s1]
    Junos vmguest package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS py extensions [20181003.235426_builder_junos_174_r2_s1]
    JUNOS py base [20181003.235426_builder_junos_174_r2_s1]
    JUNOS OS vmguest [20180814.8630ec5_builder_stable_11]
    JUNOS OS crypto [20180814.8630ec5_builder_stable_11]
    JUNOS mx libs compat32 [20181003.235426_builder_junos_174_r2_s1]
    JUNOS mx runtime [20181003.235426_builder_junos_174_r2_s1]
    JUNOS common platform support [20181003.235426_builder_junos_174_r2_s1]
    JUNOS mtx network modules [20181003.235426_builder_junos_174_r2_s1]
    JUNOS modules [20181003.235426_builder_junos_174_r2_s1]
    JUNOS mx modules [20181003.235426_builder_junos_174_r2_s1]
    JUNOS mx libs [20181003.235426_builder_junos_174_r2_s1]
    JUNOS mtx Data Plane Crypto Support [20181003.235426_builder_junos_174_r2_s1]
    JUNOS daemons [20181003.235426_builder_junos_174_r2_s1]
    JUNOS mx daemons [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services URL Filter package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services TLB Service PIC package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services SSL [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services SOFTWIRE [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services Stateful Firewall [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services RPM [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services PTSP Container package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services PCEF package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services NAT [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services Mobile Subscriber Service Container package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services MobileNext Software package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services Logging Report Framework package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services LL-PDF Container package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services Jflow Container package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services Deep Packet Inspection package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services IPSec [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services IDS [20181003.235426_builder_junos_174_r2_s1]
    JUNOS IDP Services [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services HTTP Content Management package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services Crypto [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services Captive Portal and Content Delivery Container package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services COS [20181003.235426_builder_junos_174_r2_s1]
    JUNOS AppId Services [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services Application Level Gateways [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Services AACL Container package [20181003.235426_builder_junos_174_r2_s1]
    JUNOS SDN Software Suite [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Extension Toolkit [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Packet Forwarding Engine Support (wrlinux) [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Packet Forwarding Engine Support (MX/EX92XX Common) [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Packet Forwarding Engine Support (M/T Common) [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Packet Forwarding Engine Support (MX Common) [20181003.235426_builder_junos_174_r2_s1]
    JUNOS jfirmware [20181003.235426_builder_junos_174_r2_s1]
    JUNOS Online Documentation [20181003.235426_builder_junos_174_r2_s1]
    JUNOS jail runtime [20180814.8630ec5_builder_stable_11]

     

     



  • 13.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

     
    Posted 11-27-2018 02:48

    Hi Sean,

     

    I would suggest to configure db size of 300MB (no less or more) for MX204.

     

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

     

    Regarding the Memory on MX204. Its true, the RE comes with 32GB .

    You can confirm physical memory size with “show vmhost hardware”.
    MX204 has 32GB memory totally as physical memory.

    labroot@MRS-PE1> show vmhost hardware
    Compute cluster: rainier-re-cc

      Compute node: rainier-re-cn                   
       Hardware inventory:
        
        
        Item       Capacity             Part number               Serial number             Description
        DIMM 0     16384 MB             VLXXXXXXXX-N6SD-JUN        0xXXXXXXXX               DDR4 2133 MHz
        DIMM 1     16384 MB             VLXXXXXXXX-N6SD-JUN        0xXXXXXXXX                DDR4 2133 MHz
        Disk1      100  GB              SFSAXXXXXXXXXXO            0000XXXXXXXXXXX      SLIM SATA SSD
        Disk2      100  GB              SFSAXXXXXXXXXXO            0000XXXXXXXXXXX      SLIM SATA SSD


    Although physical memory is 32GB Junos runs as administrative guest VM and uses/is allocated 16GB.
    The rest is allocated to VM etc. The followings indicate only Junos side memory.

    labroot@MRS-PE1> show system boot-messages | match memory
    real memory  = 17179869184 (16384 MB)
    avail memory = 16577871872 (15809 MB)

    labroot@MRS-PE1> show chassis routing-engine | match RAM
        DRAM                      16340 MB (16384 MB installed)

    labroot@MRS-PE1> show system memory | match total
           Total memory: 16732368 Kbytes (100%)

     

     

     



  • 14.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

    Posted 11-27-2018 13:13

    karand,

     

    Thank you!

     

    One other inquiry for you -- I noticed that the /32 access-internal routes that are installed for a subscriber are now showing "Private unicast" as the next hop (before it showed the ppX interface).  What exactly is going on here?

     

    x.x.x.x/32   *[Access-internal/12] 00:12:09
                          Private unicast


    Also, the PPPoE client in this case is my own router in the lab.  I am trying to ssh/telnet to that /32 access-internal IP it was handed, however it's not working.  I can ping it, but for some reason I cannot "run system telnet x.x.x.x" to it from the BNG.  Any ideas why?



  • 15.  RE: Recurring log entry on MX running as PWHT PPPoE BNG

     
    Posted 11-28-2018 04:38

    Sean,

     

    Your query related MX204 MEM/RAM and the one the below are not really related to the orginal post.

    For a new query, I would suggest to post new query so that other general folks on community and folks outside community don't get misdirected to post which do not relate at some extend.  I know sometimes, some query can you co-related indirectly, but again, would suggest to post a new query for simplicity & for better tracking of specfic post.

     

    Coming onto your query on telnet/ssh:

     

    On JunOS 15.1 onwards, when enchance JunOS Subscriber Mgmt is are enabled, TCP connections terminated by the router are supported for statically configured logical interfaces only.  These connections are not supported on dynamically configured interfaces (for example, dynamic-interface create auto-config or by variable called in dynamic-profile). Thus your telnet to/from subscriber would fail. (using TCP/Port 23  telnet) and this would be discarded for dynamically configured logical subscriber interfaces.

     

    Could you enable "routing-services” in dynamic profile? and check. After enabling, logout the subscriber and login agin and then try.

     

    private unicast for access-internal is expected o/p. To check pp0.xxx or demux0.xxx interface,

    use show subscriber username <username> or show subscriber address x.x.x.x/32

     

    run show subscribers address x.x.x.x 
    Interface           IP Address/VLAN ID                      User Name                      LS:RI
    pp0.3221427827      x.x.x.x                         karand@test.com         default:INSIDETEST