Scheduling the Probe

When you have configured the RTR probe, you must schedule the operation to begin collecting statistics and other information about problems that may arise.

rtr schedule

• Use to create an RTR schedule.
• Example

  host1(config)#rtr schedule 5

• Use the no version to stop the test. The no version stops the probe operation by putting it in the pending state. The no version also resets the restart-time attribute and the life attribute.
• See rtr schedule

rtr schedule life

• Use to schedule the test’s length.
• Life is a value that depends on the type of the RTR entry; it is not a length of time.
  • If the type is echo, life relates to the number of probes sent until a test finishes.
  • If the type is pathEcho, life relates to the maximum number of hops used by the traceRoute trap.
• Example

  host1(config)#rtr schedule 5 life 1800

• Use the no version to stop the test. The no version stops the probe operation by putting it in the pending state. The no version also resets the life attribute.
• See rtr schedule life

rtr schedule restart-time

• Use to specify a restart time, in seconds, after which a test is restarted.
• Example

  host1(config)#rtr schedule 5 restart-time 15

• Use the no version to stop the test. The no version stops the probe operation by putting it in the pending state. The no version also resets the restart-time attribute.
• See rtr schedule restart-time

rtr schedule start-time

• Use to schedule a test’s starting time (now or pending).
• Example

  host1(config)#rtr schedule 5 start-time now

• Use the no version to stop the test. The no version stops the probe operation by putting it in the default state, pending.
• See rtr schedule start-time

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.