Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Download Software
Research a Problem Login required
Case Management Login required
Contract & Product Management Login required
Technical Documentation
Documentation Archive
Enterprise MIBs
File Format Help
Glossary
Portable Libraries
End-of-Life Products
Contact Support
Guidelines and Policies
Security Resources
Home > Support > Technical Documentation > JunosE Software > rtr schedule life
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...

rtr schedule life

Syntax

rtr schedule rtrIndex life lifeValue

Release Information

Command introduced before JunosE Release 7.1.0.

Description

Specifies the length of the RTR probe. There is no no version.

Options

  • rtrIndex—Number of the operation to be configured, in the range 1–4294967295; no default
  • lifeValue—Number of operations or maximum TTL in the range 1–2147483647; value that depends on the type of the RTR entry
    • If the type of the RTR entry is echo, lifeValue relates to the number of operations sent until a test finishes. The default value is 90. If you use 60 operations * 60 seconds, the frequency between each operation that a test completes is 3,600 seconds (one hour).
    • If the type of the RTR entry is pathEcho, lifeValue relates to the maximum number of hops used by the traceRoute trap. The default value is 30. If you use 30 (as the maximum hops) * 3 (operations per hop) * 60 seconds frequency between each operation, a test is completed within 3,600 seconds. If a destination is reached in fewer than 30 hops, the test is completed earlier.

Mode

Global Configuration

Published: 2011-04-01

 
  • About Juniper
  • The New Network
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2011 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out