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.

English  

English

Tracing Mobile IP Operations for Subscriber Access

The Junos OS trace feature tracks Mobile IP operations and records events in a log file. The error descriptions captured in the log file provide detailed information to help you solve problems.

• Trace messages common to all logical systems and routing instances in which Mobile IP is configured. Examples of this global message type are the messages generated by Mobile IP during initialization after it starts up. These trace messages are stored in the default trace file, /var/log/mipd. You cannot configure Mobile IP to save global messages in a different file. Mobile IP traces global messages by default.
• Trace messages specific to a logical system or routing instance in which Mobile IP is configured. An example of this message type is the message generated by Mobile IP when it receives a registration request. These trace messages are stored in the trace file configured for that logical system or routing instance. These messages cannot be saved in /var/log/mipd.

1. Important events are logged in a file located in the /var/log directory. By default, the router uses the filename mipd for global tracing. You can specify a different filename, but you cannot change the directory in which trace files are located. Logical system and routing instance messages are logged in a file that you must configure separately from mipd in the /var/log directory.
2. When the trace log file filename reaches 128 kilobytes (KB), it is compressed and renamed filename.0.gz. Subsequent events are logged in a new file called filename, until it reaches capacity again. At this point, filename.0.gz is renamed filename.1.gz and filename is compressed and renamed filename.0.gz. This process repeats until the number of archived files reaches the maximum file number. Then the oldest trace file—the one with the highest number—is overwritten.

   You can optionally specify the number of trace files to be from 2 through 1000. You can also configure the maximum file size to be from 10 KB through 1 gigabyte (GB). (For more information about how log files are created, see the Junos OS System Log Messages Reference.)

By default, only the user who configures the tracing operation can access log files. You can optionally configure read-only access for all users.

1. (Optional) Configure a trace log filename.

   See Configuring the Mobile IP Trace Log Filename.

2. (Optional) Configure the number and size of trace logs.

   See Configuring the Number and Size of Mobile IP Log Files.

3. (Optional) Configure user access to trace logs.

   See Configuring Access to the Mobile IP Log File.

4. (Optional) Configure a regular expression to filter the information to be included in the trace log.

   See Configuring a Regular Expression for Mobile IP Messages to Be Logged.

5. (Optional) Configure flags to specify which events are logged.

   See Configuring the Mobile IP Tracing Flags.

6. (Optional) Configure a severity level for messages to specify which event messages are logged.

   See Configuring the Severity Level to Filter Which Mobile IP Messages Are Logged.