Routing

 View Only
last person joined: 13 hours ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.

  • 1.  PPPoE sessions terminated unless input filter is define as interface-specific .

    Posted 03-20-2019 00:34

    Hi All,

     

    I was testing PPPoE set up on the MX and faced an issue  where sessions were not comming up.

    at the radius server, i was seeing "NAS-ERROR" (poiting to issue at the MX level). after searching around, i came accross another jnet forum post mentionign input/output filters must be defined as "interface-specific".  in my troubleshooting, i had traceoptions under PPP/PPP-service/PPPoE protocals with flag all set but those were not specific on the error. 

     

    Where in the MX is correct place to check for that particular filter error ? my setup is currently working but i just wish i could have an idea on where to turn on the correct traceoptions or which system log to check if any.  

     

    MX SW servion is 15.1R6.7 

     



  • 2.  RE: PPPoE sessions terminated unless input filter is define as interface-specific .

     
    Posted 03-20-2019 00:48

    Hi,

     

    That would be smg-service traceoptions under the system processes stanza.

     

    set system processes smg-service traceoptions file smg-service
    set system processes smg-service traceoptions file size 100m
    set system processes smg-service traceoptions file files 10
    set system processes smg-service traceoptions level all
    set system processes smg-service traceoptions flag all

     

     

    BTW, JUNOS 15.1R6.7 is quite old build now, this version will be considered EoL by Q3' 2019.

    I would recommend JUNOS 17.3R3-S3 (pick the latest Service Release which includes the move recent bug fixes)

     

     

     

     

     



  • 3.  RE: PPPoE sessions terminated unless input filter is define as interface-specific .

    Posted 03-20-2019 01:24

    Hi Kiran,

     

    Thanks for response. i tried to recreate the problem with the SMG traceoptions set. 

    i see the PPPoE client is not able to go through and checking the SMG log file, i can't seem to pick the error i was lookign for. what log entry shall i expect or look for in the smg log file? assuming i dont know what the issue is, is there anything in the log file that points to filter problem ? 

    I have attached log file here. 

     

     



  • 4.  RE: PPPoE sessions terminated unless input filter is define as interface-specific .

    Posted 03-20-2019 01:30
      |   view attached

    attaching log file

    Attachment(s)

    txt
    smg-log.txt   58 KB 1 version


  • 5.  RE: PPPoE sessions terminated unless input filter is define as interface-specific .
    Best Answer

     
    Posted 03-20-2019 01:38

    Hi Lish,

     

     

    The smg log messages will NOT specfically tell you what you're missing in the config but it certainly give you a solid hint

    that you should probably look/check in the dynamic profile (dprof) for dynamic firewall filter (DFW) configuration.

     

    Here is the smg log, it clearly gives you a hint that smgd couldn't add this subscriber becuase it got a NACK from DFW.

    Which mean you should review your dynamic firewall filter config.

     

     

    Mar 20 11:02:17 dprof_build_and_send_response: NACK from DFW sent for request: 20425, error: 40
    Mar 20 11:02:17 dprof_build_and_send_response: ACK from CoS sent for request: 20425
    Mar 20 11:02:17 dprof_build_and_send_response: ACK from BFD sent for request: 20425
    Mar 20 11:02:17 dprof_response_handler: Finding request 20425 for plugin: Central
    Mar 20 11:02:17 dprof_response_handler: NACK received for profile request id: 20425 from server plugin: DFW, error code: 40