Configuring BGP Neighbor Discovery Through RPM

BGP neighbors can be configured at the following hierarchy levels:

• [edit protocols bgp group group-name]—Default logical system and default routing instance.

• [edit routing-instances instance-name protocols bgp group group-name]—Default logical system with a specified routing instance.

• [edit logical-systems logical-system-name protocols bgp group group-name]—Configured logical system and default routing instance.

• [edit logical-systems logical-system-name routing-instances instance-name protocols bgp group group-name]—Configured logical system with a specified routing instance.

If a device has a large number of BGP neighbors configured, you can direct (filter) the RPM probes to a selected group of BGP neighbors rather than to all the neighbors. To identify the BGP devices to receive RPM probes, you can configure routing instances.

When you configure BGP neighbor discovery through RPM, if you do not specify a logical system, the RPM probe applies to configured BGP neighbors for all logical systems. If you do not specify a routing instance, the RPM probe applies to configured BGP neighbors in all routing instances. You can explicitly configure RPM probes to apply only to the default logical system, the default routing instance, or to a particular logical system or routing instance.

To configure BGP neighbor discovery through RPM, configure the probe properties at the [edit services rpm bgp] hierarchy:

• To specify the contents of the data portion of Internet Control Message Protocol (ICMP) probes, include the data-fill statement at the [edit services rpm bgp] hierarchy level. The value can be a hexadecimal value.

• To specify the size of the data portion of ICMP probes, include the data-size statement at the [edit services rpm bgp] hierarchy level. The size can be from 0 through 65400 and the default size is 0.

• To specify the User Datagram Protocol (UDP) port or Transmission Control Protocol (TCP) port to which the probe is sent, include the destination-port statement at the [edit services rpm bgp] hierarchy level. The destination-port statement is used only for the UDP and TCP probe types. The value can be 7 or from 49160 through 65535.

• To specify the number of stored history entries, include the history-size statement at the [edit services rpm bgp] hierarchy level. Specify a value from 0 to 512. The default is 50.

• To specify the logical system used by ICMP probes, include the logical-system logical-system-name statement at the [edit services rpm bgp] hierarchy level. If you do not specify a logical system, the RPM probe applies to configured BGP neighbors for all logical systems. To apply the probe to only the default logical system, you must set the value of logical-system-name to null.

• To specify a number of samples for making statistical calculations, include the moving-average-size statement at the [edit services rpm bgp] hierarchy level. Specify a value from 0 through 255.

• To specify the number of probes within a test, include the probe-count statement at the [edit services rpm bgp] hierarchy level. Specify a value from 1 through 15.

• To specify the time to wait between sending packets, include the probe-interval statement at the [edit services rpm bgp] hierarchy level. Specify a value from 1 through 255 seconds.

• To specify the packet and protocol contents of the probe, include the probe-type statement at the [edit services rpm bgp] hierarchy level. The following probe types are supported:

  • icmp-ping—Sends ICMP echo requests to a target address.

  • icmp-ping-timestamp—Sends ICMP timestamp requests to a target address.

  • tcp-ping—Sends TCP packets to a target.

  • udp-ping—Sends UDP packets to a target.

  • udp-ping-timestamp—Sends UDP timestamp requests to a target address.

    Note:

    Some probe types require additional parameters to be configured. For example, when you specify the tcp-ping or udp-ping option, you must configure the destination port using the destination-port port statement. The udp-ping-timestamp option requires a minimum data size of 12; any smaller data size results in a commit error. The minimum data size for TCP probe packets is 1.

• To specify the routing instance used by ICMP probes, include the routing-instances statement at the [edit services rpm bgp] hierarchy level. The default routing instance is Internet routing table inet.0. If you do not specify a routing instance, the RPM probe applies to configured BGP neighbors in all routing instances. To apply the RPM probe to only the default routing instance, you must explicitly set the value of instance-name to default.

• To specify the time to wait between tests, include the test-interval statement at the [edit services bgp probe] hierarchy level. Specify a value from 0 through 86400 seconds. A value of 0 seconds causes the RPM test to stop after one iteration. The default value is 1.