Configuring IP Monitoring in a Virtual Router
Real-time performance monitoring (RPM) probes can be sent from a virtual router. You can specify a route to be added in a virtual router from the IP monitoring configuration. You can also specify a backup interface to be enabled in a virtual router.
The following is a sample configuration for IP monitoring with route failover in a virtual router:
set services rpm probe Probe-Payment-Server test paysvr target address 5.1.1.2 set services rpm probe Probe-Payment-Server test paysvr probe-count 5 set services rpm probe Probe-Payment-Server test paysvr probe-interval 5 set services rpm probe Probe-Payment-Server test paysvr test-interval 3 set services rpm probe Probe-Payment-Server test paysvr routing-instance one set services rpm probe Probe-Payment-Server test paysvr thresholds successive-loss 5 set services rpm probe Probe-Payment-Server test paysvr hardware-timestamp set services ip-monitoring policy test-remote-server match rpm-probe Probe- Payment-Server set services ip-monitoring policy test-remote-server then preferred-route routing-instances one route 5.1.1.0/24 next-hop 2.1.1.2 set routing-instances one instance-type virtual-router set routing-instances one interface fe-0/0/1.0 set routing-instances one interface fe-0/0/2.0 set routing-instances one interface fe-0/0/7.0 set routing-instances one routing-options static route 5.1.1.0/24 next-hop 1.1.1.2
The following is a sample configuration for IP monitoring with interface failover in a virtual router:
set services rpm probe Probe-Payment-Server test paysvr target address 5.1.1.2 set services rpm probe Probe-Payment-Server test paysvr probe-count 5 set services rpm probe Probe-Payment-Server test paysvr probe-interval 5 set services rpm probe Probe-Payment-Server test paysvr test-interval 3 set services rpm probe Probe-Payment-Server test paysvr hardware-timestamp set services rpm probe Probe-Payment-Server test paysvr routing-instance one set services rpm probe Probe-Payment-Server test paysvr thresholds successive-loss 5 set services ip-monitoring policy test-remote-server match rpm-probe Probe- Payment-Server set services ip-monitoring policy test-remote-server then interface fe-0/0/2 enable set routing-instances one instance-type virtual-router set routing-instances one interface fe-0/0/1.0 set routing-instances one interface fe-0/0/2.0 set routing-instances one interface fe-0/0/7.0 set routing-instances one routing-options static route 5.1.1.0/24 qualified-nexthop 2.1.1.2 metric 1 set routing-instances one routing-options static route 5.1.1.0/24 qualified-nexthop 1.1.1.2 metric 10 set routing-instances one routing-options static route 5.1.1.2/32 next-hop 1.1.1.2 set routing-instances one routing-options static route 5.1.1.2/32 metric 1 set routing-instances one routing-options static route 5.1.1.2/32 preference 1
When you define the RPM probe in a virtual router, you
should not enter a value for the next-hop router at the [edit
set services rpm probe probe-owner test test-name]
hierarchy level. This is because the
RPM daemon always looks in the inet.0
route table for the
next-hop address, even if you have specified a virtual router in the
routing instance configuration. Because you cannot specify the next-hop
router in the RPM configuration stanza, you need to add a /32 route
with a preference of 1 to the tracked IP address so that the system
always uses the route through the primary link for the RPM probe.