We are currently in the process of migrating floors in a large building onto a new network infrastructure. So currently we have two LAN/WAN cores - the legacy and the new, with the legacy to be decommisioned at the end. As part of this we are re-IPing all workstations that are migrated. So what we will have midway is half the building on the legacy network and half on the new. Communication between the two is via the (private) MPLS core we have.
Now, all floors thus far have migrated beautifully with no problems, however, now we have a floor where we have some servers (they should be in the data centre but that's another story!), and users map/connect to a drive on one of these servers. The servers have yet to be migrated, however, the users that map to that drive on those servers have. Post-migration they can still connect to the drive, however, it is dead slow, painful even and they are not happy.
When we were troubleshooting we noticed that if we ping a migrated workstation (workstation A) from another workstation (workstation B) which is elsewhere in the network, i.e. from a different site, that the TTL on the ping is reduced to about 120. The strange thing is that if we ping the local LAN switch that workstation A connects to from B, we get a TTL of 246. Now, basic networking knowledge tells me that the TTL is essentially a value that get decremented by each router the packet travels through to stop the packet from endlessly travelling around the network. When we traceroute from the workstation B to A we see that it takes the route we expect, nothing out the ordinary. It travels through approximately 8 devices/hops. So why in the name of beelzebubs middle toe would the traceroute show 9 hops from workstation B to A, yet the TTL on the ping from B to A sees the TTL decremented from 255 to 120? And why would the TTL from workstation B to the LAN switch that connects A only be decremented by 8, i.e. the number of hops that the traceroute shows? Why do we lose a value of 126 on the TTL from B to A?
I would most appreciate you advuce in this matter. It's probably something silly and I've embarrased myself yet again.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...