Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

Collecting Subscriber Access Logs Before Contacting Juniper Technical Support

Problem

When you experience a subscriber access problem in your network, we recommend that you collect certain logs before you contact Juniper Technical Support. This topic shows you the most useful logs for a variety of network implementations. In addition to the relevant log information, you must also collect standard troubleshooting information and send it to Juniper Technical Support in your request for assistance.

Solution

• Redirect the command output to a file.
  user@host> request support information | save rsi-1

1. Review the following blocks of statements to determine which apply to your configuration.
   [edit]
set system syslog archive size 100m files 25

   
   

   set system auto-configuration traceoptions file filename

   set system auto-configuration traceoptions file filename size 100m files 25

   
   

   set protocols ppp-service traceoptions file filename size 100m files 25

   set protocols ppp-service traceoptions level all

   set protocols ppp-service traceoptions flag all

   
   

   set protocols ppp traceoptions file filename size 100m files 25

   set protocols ppp traceoptions level all

   set protocols ppp traceoptions flag all

   set protocols ppp monitor-session all

   
   

   set interfaces pp0 traceoptions flag all

   
   

   set demux traceoptions file filename size 100m files 25

   set demux traceoptions level all

   set demux traceoptions flag all

   
   

   set system processes dhcp-service traceoptions file filename

   set system processes dhcp-service traceoptions file size 100m

   set system processes dhcp-service traceoptions file files 25

   set system processes dhcp-service traceoptions flag all

   
   

   set class-of-service traceoptions file filename

   set class-of-service traceoptions file size 100m

   set class-of-service traceoptions flag all

   set class-of-service traceoptions file files 25

   
   

   set routing-options traceoptions file filename

   set routing-options traceoptions file size 100m

   set routing-options traceoptions flag all

   
   

   set routing-options traceoptions file files 25

   
   

   set interfaces traceoptions file filename

   set interfaces traceoptions file size 100m

   set interfaces traceoptions flag all

   set interfaces traceoptions file files 25

   
   

   set system processes general-authentication-service traceoptions file filename

   set system processes general-authentication-service traceoptions file size 100m

   set system processes general-authentication-service traceoptions flag all

   set system processes general-authentication-service traceoptions file files 25
2. Copy the relevant statements into a text file and modify the log filenames as you want.
3. Copy the statements from the text file and paste them into the CLI on your router to configure logging.
4. Commit the logging configuration to begin collecting information.

Note: The maximum file size for DHCP local server and DHCP relay log files is 1 GB. The maximum number of log files for DHCP local server and DHCP relay is 1000.

Best Practice: Enable these logs only to collect information when troubleshooting specific problems. Enabling these logs during normal operations can result in reduced system performance.