Example: Configuring Chassis Cluster Redundancy Group IP Address Monitoring (CLI)
Redundancy groups can be configured to monitor key upstream resources by pinging specific IP addresses reachable through redundant Ethernet interfaces on either node in a cluster. Global threshold, weight, retry-interval, and retry-count parameters can be set on a per-redundancy-group basis. IP address monitoring weights are configured against the redundancy group global-threshold, so when a monitored IP address becomes unreachable, the weight of that monitored IP address is deducted from the redundancy group IP address monitoring global-threshold. Only when the global-threshold reaches 0 will the global-weight be deducted from the redundancy group threshold. Retry-interval and retry-count settings determine the behavior of ping attempts for all IP addresses monitored by the redundancy group.
This section gives CLI configuration examples for:
- Configuring the IP address monitoring global-weight value
- Configuring the IP address monitoring global-threshold value
- Configuring the IP address retry-interval value
- Configuring the IP address retry-count value
- Configuring an IP address to monitor
Use the following command in configuration mode to set a global monitoring weight for all IP address monitoring by the redundancy group. The global-weight will be deducted from the redundancy group’s threshold when the IP address monitoring global-threshold value reaches 0. If you do not set a global-weight, the default global-weight is 255. Note that every redundancy group has a threshold of 255. If the threshold drops to 0 or below due to failures of monitored objects, the priority of that redundancy group on that node is reduced to 0. If the other node has a higher priority level at that point, it will take over and become the primary node.
Use the following command in configuration mode to set a global monitoring threshold for IP address monitoring by the redundancy group. The threshold applies cumulatively to all IP addresses monitored by the redundancy group. If you do not set a global-threshold, the default global-threshold is 0.
Use the following command in configuration mode to set the ping interval for each IP address monitored by the redundancy group. The pings begin to be sent as soon as the configuration is committed. If you do not set a retry-interval value, the default interval is 1 second, which means that IP monitoring pings are sent to each monitored address every second.
Use the following command in configuration mode to set the number of allowed consecutive ping failures for each IP address monitored by the redundancy group. If you do not set a retry-count value, the default count is 5, which means that an IP address monitored by the redundancy group can fail to reply to a ping request five consecutive times before being considered unreachable.
Use the following command in configuration mode to specify an IP address to be monitored by a specific redundancy group through a specific redundant Ethernet interface (known as a reth in CLI commands and interface listings) and give it a weight. You can configure a redundancy group to monitor any IP address reachable through a redundant Ethernet interface, but you must name the interface, its logical unit number, and a secondary IP address for use as the IP monitoring ping source for the secondary node. Each of these elements is required to configure an IP address for monitoring. Note that the secondary IP address being assigned must be on the same subnet as the IP address of the redundant Ethernet interface logical unit and it should not be the same as the IP address on the redundant Ethernet interface.
Related Topics
- JUNOS Software Feature Support Reference for SRX Series and J Series Devices
- Understanding Chassis Cluster Redundancy Group 0: Routing Engines
- Understanding Chassis Cluster Redundancy Groups 1 Through 128
- Understanding Chassis Cluster Redundancy Group Interface Monitoring
- Understanding Chassis Cluster Redundancy Group IP Address Monitoring
- Understanding Chassis Cluster Redundancy Group Failover
- Understanding Chassis Cluster Monitoring of Global-Level Objects