I am working with a service providers network. They want to get TTL disabled for the purpose of TRACEROUTING to be more visible, means when tracerouting is done, it should show the IP ADD where it is dropping the packet. Should I use no propagate ttl command or else? what will be the impact on the network if i do this?
ttl propagation is on by default on cisco routers doing mpls, this means they copy the ttl value from the ip packet and insert the value in mpls-header decrement by 1 and send the packet. If you want to turn off that then use no mpls ip propagate-ttl. The drawback of having ttl propagate, the network is visible by the customer (god or bad, I'm not sure). The icmp ttl-expired message have to be handled by the cpu, thus making it a security vulnerable. This is what comes into my mind. A link that explains it a little bit more.
I think the first question for you to address is whether or not the service provider wants TTL/traceroute enabled for their clients or for their own internal management VLAN/network?
There are many nuances to traceroute in an MPLS backbone, so consider reading up on all of the details before you implement any changes. Unfortunately, all of my references would be books vs. links, and I'm on the road and do not have access to my library at the moment. Most general-purpose MPLS books cover this topic in varying degrees of detail and no doubt the link given above has lots of good stuff...
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
Introduction Basic configuration for netflow Scale parameters for
netflow Netflow support Architecture Packet flow for netflow Inside the
LC CPU Netflow Cache size, maintenance and memory Sample usage Cache
Size Aging Permanent cache Characteristics Which...