DUP!

Hi All,

I have 2x N5K in a vPC. When ping'ng from 2nd Nexus I get (DUP!). This is my secondary vPC member.

When ping'ng from primary vPC memmber I don't get DUP!

Is this a ping duplicate? What cause the duplicate?

 

 

N5K-2(config-if)# ping 10.5.3.113

PING 10.5.3.113 (10.5.3.113): 56 data bytes

36 bytes from 10.5.1.2: Destination Host Unreachable

Request 0 timed out

64 bytes from 10.5.3.113: icmp_seq=1 ttl=62 time=3.099 ms

64 bytes from 10.5.3.113: icmp_seq=1 ttl=63 time=3.633 ms (DUP!)

64 bytes from 10.5.3.113: icmp_seq=2 ttl=62 time=2.379 ms

64 bytes from 10.5.3.113: icmp_seq=2 ttl=63 time=7.426 ms (DUP!)

64 bytes from 10.5.3.113: icmp_seq=3 ttl=62 time=5.215 ms

64 bytes from 10.5.3.113: icmp_seq=3 ttl=63 time=5.683 ms (DUP!)

64 bytes from 10.5.3.113: icmp_seq=4 ttl=62 time=27.854 ms

64 bytes from 10.5.3.113: icmp_seq=4 ttl=63 time=28.05 ms (DUP!)

Comments

  • What are you pinging?  Can you paste your configs in?

  • Yes you have received duplicate packets from your network.

    Duplicate are caused when there is loop somewhere in network. When you ping to one device and you get reply from the same device and others too, it's a duplicate packet.

    Can you post your topology and your configs?

    Hi All,

    I have 2x N5K in a vPC. When ping'ng from 2nd Nexus I get (DUP!). This is my secondary vPC member.

    When ping'ng from primary vPC memmber I don't get DUP!

    Is this a ping duplicate? What cause the duplicate?

     

     

    N5K-2(config-if)# ping 10.5.3.113

    PING 10.5.3.113 (10.5.3.113): 56 data bytes

    36 bytes from 10.5.1.2: Destination Host Unreachable

    Request 0 timed out

    64 bytes from 10.5.3.113: icmp_seq=1 ttl=62 time=3.099 ms

    64 bytes from 10.5.3.113: icmp_seq=1 ttl=63 time=3.633 ms (DUP!)

    64 bytes from 10.5.3.113: icmp_seq=2 ttl=62 time=2.379 ms

    64 bytes from 10.5.3.113: icmp_seq=2 ttl=63 time=7.426 ms (DUP!)

    64 bytes from 10.5.3.113: icmp_seq=3 ttl=62 time=5.215 ms

    64 bytes from 10.5.3.113: icmp_seq=3 ttl=63 time=5.683 ms (DUP!)

    64 bytes from 10.5.3.113: icmp_seq=4 ttl=62 time=27.854 ms

    64 bytes from 10.5.3.113: icmp_seq=4 ttl=63 time=28.05 ms (DUP!)


     

  • You can disable ICMP redirect !!

    I beleive your primary GW is not Letting you to pass the traffic may be route not present or something !! so it is sending the ICMP redirects to other VPC peer for response..It ususally seen in FHRP envirnoment..

  • Thanks Fragilemohi, "no ip redirect" stop the duplicate....

    mmmm...but, I overlooked it since I read that when you enable “peer-gateway”
    in vPC it automatically  disable ip
    redirects. Is this still valid in  NXOS 6.0(2)N1(2)?

     

  • The manner is evaluated for the feeble counts of the team. The implication of the turn and https://resumehelpaustralia.com/careers-booster-review/ is ensured or the held course for the individuals. The change iodine for all options. The true value is granted for the individuals. elements found for the use of the offers for all skilled and invited tips of the field.

Sign In or Register to comment.