close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

rpm-scale

date_range 20-Nov-23

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
rpm-scale {
    destination {
        interface interface-name.logical-unit-number;
        subunit-cnt subunit-cnt;
    }
    source {
        address-base ipv4-address-base;
        count ipv4-count;
        step ipv4-step;
    }
    source-inet6 {
        address-base ipv6-address-base;
        count ipv6-count;
        step ipv6-step;
    }
    target {
        address-base ipv4-address-base;
        count ipv4-count;
        step ipv4-step;
    }
    target-inet6 {
        address-base ipv6-address-base;
        count ipv6-count;
        step ipv6-step;
    }
    tests-count tests-count;
}

Hierarchy Level

[edit services rpm probe owner test test-name]

Description

Configure the generation of multiple IPv4 RPM tests for a probe owner. Starting in Junos OS Release 18.2R1, you can also configure the generation of multiple IPv6 RPM tests for a probe owner. Tests are generated for multiple combinations of source and target addresses, which are incremented based on your configuration. Tests are first generated for all the source addresses with the initial target address, then tests are generated for all the source addresses with the next available target address, and so on.

Options

`interface-name.logical-unit-number`	The services interface that is generating RPM probes and the logical unit number that is used for the first test that is generated.
`ipv4-address-base`	The IPv4 source or target address that is incremented to generate the addresses used in the RPM tests.
`ipv4-count`	The maximum number of IPv4 source or target addresses to use for the generated RPM tests.
`ipv4-step`	The amount to increment the IPv4 source or target address for each generated RPM test.
`ipv6-address-base`	The IPv6 source or target address that is incremented to generate the addresses used in the RPM tests.
`ipv6-count`	The maximum number of IPv6 source or target addresses to use for the generated RPM tests.
`ipv6-step`	The amount to increment the IPv6 source or target address for each generated RPM test.
`subunit-cnt`	The maximum number of logical units used by the services interface in the generated tests. The first generated test uses the logical unit specified in the `interface-name.logical-unit-number` option, and each successive test increments the logical unit number by one. Once the maximum number of logical units has been used, the next generated test cycles back to the logical unit that was used in the first test.
`tests-count`	The maximum number of RPM tests to generate. This number must be less than or equal to the number of generated source addresses multiplied by the number of generated target addresses. Range: 1 through 500,000 for probes generated on an MS-MPC or MS-MIC. 1 through 2,000 for probes generated on the Routing Engine.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 17.4R1.

arrow_backward PREVIOUS rpm (Interfaces)

NEXT arrow_forward rpm (Services)

Junos CLI Reference

ON THIS PAGE

rpm-scale

Syntax

Hierarchy Level

Description

Options

Required Privilege Level

Release Information

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Junos CLI Reference

ON THIS PAGE

rpm-scale

Syntax

Hierarchy Level

Description

Options

Required Privilege Level

Release Information

Related Documentation

Stay in touch