bmp

Configure an authentication algorithm.

• Values: Specify one of the following types of authentication algorithms:

  • aes-128-cmac-96—Cipher-based message authentication code (AES128, 96 bits).

  • hmac-sha-1-96—Hash-based message authentication code (SHA1, 96 bits).

  • md5—Message digest 5.

• Default: hmac-sha-1-96

  Note:

  The default is not displayed in the output of the show bgp bmp command unless a key or key-chain is also configured.

Configure an MD5 authentication key (password), which can be up to 126 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”). Neighboring routing devices use the same password to verify the authenticity of BMP packets sent from this system.

Apply and enable an authentication key chain to the routing device, which can be up to 126 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”).

Note that the referenced key chain must be defined. When configuring the authentication key update feature for BGP, you cannot commit the 0.0.0.0/allow statement with authentication keys or key chains. The CLI issues a warning and fails to commit the configuration.

Specify whether the BMP station connection is active or passive. If you configure the connection-mode statement as active, do not also configure the local-port statement. If you configure the connection-mode statement as passive, you must configure the local-port statement.

If the connection-mode statement is configured as active, a station port number is required. If the connection-mode statement is configured as passive, you must not configure a station port number.

• Values: Specify one of the following:

  • active—BMP initiates the connection to the BMP station.

  • passive—BMP does not initiate a connection to the BMP station. However, it does listen for a connection request from active BMP stations and will connect if a station is available.

(Optional) Specify a character string for a type 0 TLV to send to the BMP station with the initiation message. The message is transmitted when a BMP station establishes a connection to the device. You can provide some information to the BMP station system administrator (for example, a contact phone number). The initiation message includes a type 1 TLV containing the SNMP sysDescr value specified in RFC 1213 Management Information Base for Network Management of TCP/IP-based internets: MIB-II and a type 2 TLV containing the SNMP sysName value also from RFC 1213. The string in the initiation-message message is UTF-8.

The normal time for sending an initiation message is when the BMP session is first established. However, an initiation message change also triggers the transmission of an initiation message to current BMP sessions.

Another event that triggers the transmission of an initiation message is when you change in the sysName or sysDescr values in the SNMP configuration. The initiation message is sent to current BMP sessions.

• Range: 1 through 255 characters

(Optional) Configure this option to collect time series data. Note that collection of time series data uses additional memory resources. Disable this option to free the memory used to store the time series data.

(Optional) Enable this option to store BMP advertisement state for rib-out monitoring. Note that this option can use up valuable resources. Disable this option to free the memory used to store BMP advertisement state. We recommend toggling the BMP session after changing deleting this option to have a cosistent view for all prefixes advertised to the station..

• Default: keep-advertisement-state is disabled by default to ensure efficient memory utilization.

(Optional) Specifies the IPv4 or IPv6 address for the BMP connection on the device. We recommend that you configure a local address. For both active and passive connection modes, configure a loopback local address. This provides a consistent local endpoint, is useful for debugging, and assures greater reliability for the BMP connection since it is not tied to a single router interface.

For passive mode, specifying a local address is required. It also provides some security against a malicious BMP connection. For active mode, we also recommend configuring a local address to help ensure reliability.

If you change the local address, the BMP station connection flaps when you commit the configuration.

Specify the listening port for the BMP station connection.

If you configure the connection-mode statement as active, do not configure the local-port statement. If you configure the connection-mode statement as passive, you must configure local-port statement.

If you change the local port, the BMP station connection flaps when you commit the configuration.

• Range: 1 through 65,535

Specify the maximum number of local-rib outstanding buffers before blocking.

• Range: 1 through 50

(Optional) Explicitly enable or disable BMP monitoring of BGP peers. You can also selectively enable or disable BMP monitoring at various hierarchy levels (for example, [edit protocols bgp group group-name] or [edit protocols bgp group group-name neighbor address]). If you disable BMP monitoring, withdrawal messages are sent for any previously advertised routes. These are followed by a down message. If you enable BMP monitoring, an up message is sent first and then the route advertisements follow.

• Default: BMP monitoring is enabled by default.

• Values: Specify one of the following:

  • disable—Disable BMP monitoring.

  • enable—Enable BMP monitoring.

(Optional) Specify the dispatch priority for BMP. The dispatch priority controls the frequency with which the device is able to forward BMP messages to BMP stations.

• Default: The default dispatch priority is low, to minimize interference with other routing protocol process priorities and to match the behavior of previous versions of BMP.

• Values: Specify one of the following:

  • high—The routing protocol process handles BMP requests with high urgency.

  • medium—The routing protocol process handles BMP requests with medium urgency.

  • low—The routing protocol process handles BMP requests with low urgency.

Specify the name of the routing instance you want the BGP Monitoring Protocol (BMP) to use. This can be any routing instance name. If you want to use the reserved non-default management routing instance mgmt_junos, make sure you configure the management-instance statement.

When routing-instance is configured at both hierarchy levels— [edit routing-options bmp station station-name] and [edit routing-options bmp]— the configuration at the [edit routing-options bmp station station-name] hierarchy level takes precedence.

• Values:

  • default—Default routing instance

  • routing-instance-name—Name of the routing instance

(Required) Specify a name for the BMP monitoring station. Each station can use a significant amount of a device’s resources. You can configure up to three BMP monitoring stations.

Specify the address or name for the BMP monitoring station. You can specify one or the other but not both.

• Values: Specify one of the following:

  • station-address—Specify the address for the BMP station. The address should be a valid IPv4 or IPv6 address.

  • station-name—Specify the name for the BMP station.

Specify the port number for the BMP monitoring station. If the connection-mode statement is configured as active, a station port number is required. If the connection-mode statement is configured as passive, you must not configure a station port number.

• Range: 1 though 65535

(Optional) Specify how often statistics messages are sent to the BMP monitoring station. If you configure a value of 0, no statistics messages are sent.

• Default: 3600 seconds

• Range: 15 though 65535 seconds