Quantcast
Channel: Ethernet Switching topics
Viewing all articles
Browse latest Browse all 2326

Juniper EX4550 uses IP of neighbor port as the Source during ping directly connected remote peer

$
0
0

Hello.

We have 2xEX4550-32F (Virtual Chassis). Below configuration:

!

admin@EX4550> show configuration routing-instances TEST
instance-type virtual-router;
interface xe-0/0/29.0;
interface xe-1/0/29.0;
routing-options {
static {
route 192.168.0.0/24 {
next-hop 192.168.1.2;
qualified-next-hop 192.168.1.6 {
preference 10;
bfd-liveness-detection {
minimum-interval 5000;
multiplier 3;

}
}
bfd-liveness-detection {
minimum-interval 5000;
multiplier 3;
}
}
}
}

admin@EX4550> show configuration interfaces xe-0/0/29
description "Link A";
mtu 9216;
unit 0 {
family inet {
address 192.168.1.1/30;
}
}

{master:0}
admin@EX4550> show configuration interfaces xe-1/0/29
description "Link B";
mtu 9216;
unit 0 {
family inet {
address 192.168.1.5/30;
}
}

When I try to ping remote peer via 192.168.1.2 - ping is OK

When I try to ping remote peer via 192.168.1.6 - ping is FAIL

 

On remote peer tcpdump was turned on - incoming ICMP packets have Source IP = 192.168.1.1, not 192.168.1.5

Why so&


Viewing all articles
Browse latest Browse all 2326

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>