Hello,
In our test environment I am testing a setup using a dual-ISP connection with automatic failover using RPM Probes. I used this article as a guideline:
http://kb.juniper.net/InfoCenter/index?page=content&id=KB25052
I have 1 ISP connected to ge-0/0/0.0 (the main ISP) and another on ge-0/0/1.0 (fallback ISP).
There seems to be an issues with this part of my configuration:
-----------
destination-interface ge-0/0/0.0;
next-hop 10.4.0.1;
----------
The ICMP-Ping RPM probe keeps reporting a 'request timed out', even though I am 100% sure that the server 8.8.8.8 is pingable from that interface 0/0/0.0 (using next-hop 10.4.0.1, being the primary ISP router).
When I remove that section of the configuration, the probe reports OK response from 8.8.8.8. However this is not a workable solution because I need to specify that interface so the probe will only check this resource using my primary ISP. (otherwise in a failover scenario 8.8.8.8 becomes reachable again via the 2nd ISP and the failover is reverted, even when the primary ISP is not back online again)
Am I missing something?
here is my configuration (bear in mind this is a test setup):
## Last changed: 2012-11-29 17:42:04 UTC
version 11.2R4.3;
system {
host-name SRXTest;
root-authentication {
encrypted-password "$1erdG1";
}
name-server {
208.67.222.222;
208.67.220.220;
}
login {
user infra {
uid 2000;
class super-user;
authentication {
encrypted-password "/";
}
}
}
services {
ssh;
telnet;
xnm-clear-text;
web-management {
http {
interface [ vlan.0 ge-0/0/1.0 ];
}
https {
system-generated-certificate;
interface [ vlan.0 ge-0/0/1.0 ];
}
}
dhcp {
router {
192.168.1.1;
}
pool 192.168.1.0/24 {
address-range low 192.168.1.2 high 192.168.1.254;
}
propagate-settings ge-0/0/0.0;
}
}
syslog {
archive size 100k files 3;
user * {
any emergency;
}
file messages {
any critical;
authorization info;
}
file interactive-commands {
interactive-commands error;
}
}
max-configurations-on-flash 5;
max-configuration-rollbacks 5;
license {
autoupdate {
url https://ae1.juniper.net/junos/key_retrieval;
}
}
}
interfaces {
ge-0/0/0 {
unit 0 {
family inet {
address 10.4.0.88/16;
}
}
}
ge-0/0/1 {
unit 0 {
family inet {
address 192.168.1.150/24;
}
}
}
fe-0/0/2 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/3 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/4 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/5 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/6 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/7 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
vlan {
unit 0 {
family inet {
address 192.168.100.1/24;
}
}
}
}
routing-options {
static {
route 0.0.0.0/0 next-hop 10.4.0.1;
}
}
protocols {
stp;
}
security {
screen {
ids-option untrust-screen {
icmp {
ping-death;
}
ip {
source-route-option;
tear-drop;
}
tcp {
syn-flood {
alarm-threshold 1024;
attack-threshold 200;
source-threshold 1024;
destination-threshold 2048;
timeout 20;
}
land;
}
}
}
nat {
source {
rule-set trust-to-untrust {
from zone trust;
to zone untrust;
rule source-nat-rule {
match {
source-address 0.0.0.0/0;
}
then {
source-nat {
interface;
}
}
}
}
}
}
policies {
from-zone trust to-zone untrust {
policy trust-to-untrust {
match {
source-address any;
destination-address any;
application any;
}
then {
permit;
}
}
}
}
zones {
security-zone trust {
host-inbound-traffic {
system-services {
all;
}
protocols {
all;
}
}
interfaces {
vlan.0 {
host-inbound-traffic {
system-services {
all;
}
protocols {
all;
}
}
}
}
}
security-zone untrust {
screen untrust-screen;
interfaces {
ge-0/0/0.0 {
host-inbound-traffic {
system-services {
tftp;
}
}
}
ge-0/0/1.0;
}
}
}
}
services {
rpm {
probe example {
test test-name {
probe-type icmp-ping;
target address 8.8.8.8;
probe-count 3;
probe-interval 15;
test-interval 10;
thresholds {
successive-loss 3;
total-loss 3;
}
destination-interface ge-0/0/0.0;
next-hop 10.4.0.1;
}
}
}
ip-monitoring {
policy test {
match {
rpm-probe example;
}
then {
preferred-route {
route 0.0.0.0/0 {
next-hop 192.168.1.1;
}
}
}
}
}
}
vlans {
vlan-trust {
vlan-id 3;
l3-interface vlan.0;
}
}