On 7/6/20 6:00 AM, Philip Homburg wrote:
> On 2020/07/05 19:55 , Bryan Fields wrote:
>> Is this normal or is there a problem with my probe?  I've never really taken
>> this close of a look before, I'm unsure if it has an issue or if this is 
>> normal.
> 
> Do you see any ARP request coming from the probe? It seems that the
> probe cannot reach it's default router on IPv4.

Yes, it responds sometimes on v4, and always on v6.  I'm at a loss to
understand it.

v4:
> bfields@colo> ping 199.47.174.226 interface vlan.200 source 199.47.174.225    
> PING 199.47.174.226 (199.47.174.226): 56 data bytes
> 64 bytes from 199.47.174.226: icmp_seq=4 ttl=64 time=1.629 ms
> 64 bytes from 199.47.174.226: icmp_seq=35 ttl=64 time=1.622 ms
> 64 bytes from 199.47.174.226: icmp_seq=43 ttl=64 time=1.562 ms
> 64 bytes from 199.47.174.226: icmp_seq=51 ttl=64 time=1.728 ms
> 64 bytes from 199.47.174.226: icmp_seq=55 ttl=64 time=2.327 ms
> ^C
> --- 199.47.174.226 ping statistics ---
> 60 packets transmitted, 5 packets received, 91% packet loss
> round-trip min/avg/max/stddev = 1.562/1.774/2.327/0.282 ms

v6:
> ping 2605:900::1:9fff:fe04:f4a3 
> PING6(56=40+8+8 bytes) 2605:900::1 --> 2605:900::1:9fff:fe04:f4a3
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=0 hlim=64 time=3.098 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=1 hlim=64 time=6.471 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=2 hlim=64 time=2.898 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=3 hlim=64 time=1.367 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=4 hlim=64 time=1.320 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=5 hlim=64 time=1.864 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=6 hlim=64 time=1.415 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=7 hlim=64 time=2.624 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=8 hlim=64 time=2.308 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=9 hlim=64 time=2.577 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=10 hlim=64 time=2.605 ms
> 16 bytes from 2605:900::1:9fff:fe04:f4a3, icmp_seq=11 hlim=64 time=2.855 ms
> ^C
> --- 2605:900::1:9fff:fe04:f4a3 ping6 statistics ---
> 12 packets transmitted, 12 packets received, 0% packet loss
> round-trip min/avg/max/std-dev = 1.320/2.617/6.471/1.309 ms
ARP:
> bfields@colo> show arp no-resolve |match 199.47.174.226                       
> 02:01:9f:04:f4:a3 199.47.174.226  vlan.200                 none

MAC Table:
> show ethernet-switching table interface ge-0/0/6.0       
> Ethernet-switching table: 1 unicast entries
>   VLAN              MAC address       Type         Age Interfaces
>   Atlas-Probe       *                 Flood          - All-members
>   Atlas-Probe       02:01:9f:04:f4:a3 Learn          0 ge-0/0/6.0



Interface:
> show interfaces ge-0/0/6                                        
> Physical interface: ge-0/0/6, Enabled, Physical link is Up
>   Interface index: 136, SNMP ifIndex: 514
>   Description: Server: Atlas Probe [1Mbit] (RIPE)
>   Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: Auto, Duplex: 
> Auto, BPDU Error: None,
>   MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, 
> Flow control: Enabled,
>   Auto-negotiation: Enabled, Remote fault: Online, Media type: Copper
>   Device flags   : Present Running
>   Interface flags: SNMP-Traps Internal: 0x0
>   Link flags     : None
>   CoS queues     : 8 supported, 8 maximum usable queues
>   Current address: 78:19:f7:82:a1:09, Hardware address: 78:19:f7:82:a1:09
>   Last flapped   : 2020-07-04 11:42:33 EDT (1d 23:43 ago)
>   Input rate     : 4160 bps (6 pps)
>   Output rate    : 1296 bps (2 pps)
>   Active alarms  : None
>   Active defects : None
>   Interface transmit statistics: Disabled
> 
>   Logical interface ge-0/0/6.0 (Index 78) (SNMP ifIndex 515)
>     Flags: Up SNMP-Traps Redundancy-Device 0x0 Encapsulation: ENET2
>     Input packets : 7039008
>     Output packets: 32913928
>     Protocol eth-switch
>       Flags: None
> 


-- 
Bryan Fields

727-409-1194 - Voice
http://bryanfields.net

Reply via email to