Description

This article explains the meaning of the following syslog message seen on the device and indicates if any actions need to be taken:

jl2tpd:  Rx/Tx : sccrq 420 sccrp 0 scccn 11 stopccn 42 hello 7676 icrq 66 icrp 0 iccn 65 cdn 8 zlb 474

Symptoms

The following syslog messages are seen on the device: 

Jun 29 04:02:23  XXXX jl2tpd:   Rx : sccrq 420 sccrp 0 scccn 11 stopccn 42 hello 7676 icrq 66 icrp 0 iccn 65 cdn 8 zlb 474
Jun 29 04:02:23  XXXX jl2tpd:   Tx : sccrq 0 sccrp 141 scccn 0 stopccn 0 hello 357 icrq 0 icrp 66 iccn 0 cdn 112 zlb 7810
Jun 29 04:03:23  XXXX jl2tpd:   Rx : sccrq 420 sccrp 0 scccn 11 stopccn 42 hello 7676 icrq 66 icrp 0 iccn 65 cdn 8 zlb 474
Jun 29 04:03:23  XXXX jl2tpd:   Tx : sccrq 0 sccrp 141 scccn 0 stopccn 0 hello 357 icrq 0 icrp 66 iccn 0 cdn 112 zlb 7810

Solution

These syslog messages are usually seen due to L2TP configuration present on the device.

These syslog messages report the stats of the incoming packets. These messages do not indicate any errors. They are used to track the statistics of the L2TP LNS packet counts. They are triggered because the MX device received SCCRQ packets.

If the logging severity is set to notice or lower (info / debug), these messages would be printed because they are informational logs. They will are reported because there are l2tp packets hitting the box.

These are hello messages of l2tp. These log messages will no longer appear in syslog if log level is set to warning/error or higher. 

To prevent certain syslog messages from being written to the log file, refer to KB9382 - How to prevent syslog messages from being written to the log file [juniper.net] or use the following configuration on the device:  

user@lab-re0# show system syslog
user * {
    any emergency;
}
 file messages {
    any notice;
    match "!(.*sccrq​.*)";
}


If the logs appear even after applying the above configuration, please contact JTAC for further investigation. 

 

Related Information