Quantcast
Channel: All SRX Services Gateway posts
Viewing all articles
Browse latest Browse all 17645

Re: Unable to ping default gw from SRX240 cluster Node0 using fxp0

$
0
0

Hi Ashvin,

 

Idid this and I get the following:

 

setnoc@SRX240-SNC-CLUSTER-NODE-0> monitor traffic interface fxp0 matching icmp
verbose output suppressed, use <detail> or <extensive> for full protocol decode
Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay.
Address resolution timeout is 4s.
Listening on fxp0, capture size 96 bytes

 

Reverse lookup for 172.24.0.1 failed (check DNS reachability).
Other reverse lookup failures will not be reported.
Use <no-resolve> to avoid reverse lookups on IP addresses.

07:39:12.887303 In IP truncated-ip - 68 bytes missing! 172.24.0.1 > 172.24.9.112: ICMP echo request, id 1024, seq 54500, length 108
07:39:12.887400 Out IP truncated-ip - 68 bytes missing! 172.24.9.112 > 172.24.0.1: ICMP echo reply, id 1024, seq 54500, length 108
07:39:13.777326 In IP truncated-ip - 68 bytes missing! 172.24.0.1 > 172.24.9.112: ICMP echo request, id 1024, seq 54600, length 108
07:39:13.777439 Out IP truncated-ip - 68 bytes missing! 172.24.9.112 > 172.24.0.1: ICMP echo reply, id 1024, seq 54600, length 108
07:39:14.777392 In IP truncated-ip - 68 bytes missing! 172.24.0.1 > 172.24.9.112: ICMP echo request, id 1024, seq 54700, length 108
07:39:14.777586 Out IP truncated-ip - 68 bytes missing! 172.24.9.112 > 172.24.0.1: ICMP echo reply, id 1024, seq 54700, length 108
07:39:15.777371 In IP truncated-ip - 68 bytes missing! 172.24.0.1 > 172.24.9.112: ICMP echo request, id 1024, seq 54800, length 108
07:39:15.777491 Out IP truncated-ip - 68 bytes missing! 172.24.9.112 > 172.24.0.1: ICMP echo reply, id 1024, seq 54800, length 108
07:39:16.777393 In IP truncated-ip - 68 bytes missing! 172.24.0.1 > 172.24.9.112: ICMP echo request, id 1024, seq 54900, length 108
07:39:16.777504 Out IP truncated-ip - 68 bytes missing! 172.24.9.112 > 172.24.0.1: ICMP echo reply, id 1024, seq 54900, length 108

 

So the icmp ariives and it responds. The arp is present on the EX4300.

So maybe the EX4300 IRB interface is blocking it somehow?

 

setnoc@SWT-SNC-EPC-4300> show arp
MAC Address Address Name Interface Flags
02:00:00:00:00:0a 128.0.0.5 128.0.0.5 bme0.0 permanent
02:00:00:00:00:0a 128.0.0.6 128.0.0.6 bme0.0 permanent
02:00:00:00:00:0a 128.0.0.16 128.0.0.16 bme0.0 permanent
02:00:00:00:00:0c 128.0.0.18 128.0.0.18 bme0.0 permanent
02:00:00:00:00:0d 128.0.0.19 128.0.0.19 bme0.0 permanent
00:10:db:ff:21:d0 172.24.0.1 172.24.0.1 irb.906 [ae1.0] none
54:1e:56:e6:64:40 172.24.9.110 172.24.9.110 irb.906 [ae1.0] none
54:1e:56:e6:4a:c0 172.24.9.112 172.24.9.112 irb.906 [ge-2/0/0.0] none
54:1e:56:e5:56:40 172.24.9.113 172.24.9.113 irb.906 [ge-3/0/0.0] none
54:4b:8c:5f:98:37 172.24.9.164 172.24.9.164 irb.906 [ge-2/0/16.0] none
54:4b:8c:61:34:37 172.24.9.165 172.24.9.165 irb.906 [ge-3/0/16.0] none
00:10:db:ff:21:d0 172.24.15.254 172.24.15.254 irb.906 [ae1.0] none


Viewing all articles
Browse latest Browse all 17645

Trending Articles



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