Static Routes with IPPM

Static Routes with IP Performance Metrics (IPPM) enables the tracking of selected static routes against a watcher profile. If the IPPM profile linked to the watcher profile fails due to reachability issues, an alternative route is selected. This ensures network stability by dynamically adjusting routes based on real-time network conditions.

Watcher profiles are mapped to IPPM profiles, where the next-hop address of the static route will be the gateway for the specified target IP address with the desired metrics. If the scheduled IPPM test fails due to reachability issues, the watcher profile associated with the IPPM profile triggers a request to disable the static routes, thereby enabling an alternate route.

Different watcher profiles can be configured for each IPPM profile with specified actions, including logging success or failure messages. These actions can extend to performing certain measures on the network device to stabilize network performance.

Requirements

This feature is supported for all RUCKUS ICX devices. The maximum number of IPPM profiles that can be configured varies by device model:

  • RUCKUS ICX 7550: 32 profiles
  • RUCKUS ICX 7650: 64 profiles
  • RUCKUS ICX 7850: 64 profiles
  • RUCKUS ICX 8200: 16 profiles

Considerations

  • IPPM is enabled by default. However, the monitoring of metrics is based on the configured test profiles.
  • Selected static routes can be tracked against a watcher profile. When the IPPM profile associated with the watcher profile fails due to reachability issues, an alternative route can be enabled.
  • IPPM relies on the Ping functionality to conduct its tests. For more information, refer to the ping command in the RUCKUS FastIron Command Reference.
  • A maximum of four IPPM profiles can be mapped to a single watcher profile.

Best Practices

  • Ensure that test profiles are configured correctly to monitor the desired metrics. This includes setting appropriate values for jitter, RTT, TTL, and response time.
  • Schedule regular intervals for monitoring to ensure continuous performance tracking and timely detection of issues.
  • Use watcher profiles to analyze metrics and perform necessary actions, such as logging success or failure messages, to maintain network stability.

Prerequisites

This feature has no prerequisites to feature enablement or usage.

Parent topic: IP Performance Metrics Overview