When I do a traceroute I get multple responses for certain hops as in example:
1 10.169.1.5 0 msec 24 msec 4 msec
2 10.169.10.5 0 msec
10.169.10.45 12 msec
10.169.10.5 12 msec
3 10.250.4.189 20 msec
10.250.4.193 4 msec 0 msec
4 10.170.10.62 0 msec 0 msec 4 msec
5 10.170.10.30 4 msec 4 msec 0 msec
6 10.170.170.246 4 msec 4 msec 4 msec
Now in hop 2 I understand that there are multiple equal weight routes. This represents our redundant switches. I don't know why the 10.169.10.5 address comes up twice though. I've seen it before and just accepted it until I was showing a new kid and he asked but I don't have the answer for it. Why does the traceroute from Cisco devices pick up the redundant route? Does it function differently than a traceroute from Windows or Linux?
It's funny how after awhile of doing things you just accept it as normal but I can't explain something that should be very basic.
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Believe hop 2 is just round-robin. Try increasing your trace probes up from 3 and check results.
Inviting all network professionals in operations! We'd like to understand what would be valuable for you in a mobile application. Your response will help Cisco improve a product feature that could benefit you. Thanks!
Click here to take the sur...
Cisco’s software-defined wide area network (SD-WAN) solution allows user to quickly and seamlessly establish an overlay fabric to connect an enterprise’s data centers, branch and campus locations, as well as colocation facilities in order to imp...
1. Log into CLI of DNAC:
ssh maglev@< DNAC appliance IP> -p 2222
2. Run this curl command to get token to get member id:
curl -X POST -u admin:<admin user password> -H -V https://<CLUSTER-IP>/api/system/v1/identitymgmt/token
Enterprise Switching Business Unit is glad to announce Beta release 16.12.2 for all Catalyst 9200/9300/9400/9500/9600 and Catalyst 3650/3850 Platforms. This release is made available to allow users to test, evaluate and share fee...
Purpose of the document
This document describes the general recommendations or best practices when designing and deploying the Cisco SD-Access technology. The document assumes that the reader has a general overview of Cisco's SD-Access for Distributed C...