Baldy2K
07-17-2009, 04:21 PM
While exploring the Path analysis module I ran into an interesting behavior. I attempted a couple pf path discovery methods;
SNMP failed when it attempted to query my carriers PE router,
Traceroute was broken when the tool attempted from an ASA running 7.2 code. (it attempted to use straight IOS style I'm sure I missed something here)
So I made the attempt using live route table. This worked across my L2 MPLS network (transparent, makes sense) But again when it got to the MPLS cloud it attempted to get the routes from the upstream peer. (I'm sure there is a security tech cursing loudly somewhere in the carriers NOC) and as a result it failed.
So the basic question is, has anyone found a smooth method for path discovery across an MPLS environment where you only manage the CE devices?
Also using a traceroute from an endstation to the target did yield better results, but there are occasions where I won't have access from a system on the source network.
I would prefer that the route table method be reliable as it should (and did where there is no L3 obsfucation via MPLS) find ALL paths, an important aspect of problem identification and resolution.
Thoughts?
SNMP failed when it attempted to query my carriers PE router,
Traceroute was broken when the tool attempted from an ASA running 7.2 code. (it attempted to use straight IOS style I'm sure I missed something here)
So I made the attempt using live route table. This worked across my L2 MPLS network (transparent, makes sense) But again when it got to the MPLS cloud it attempted to get the routes from the upstream peer. (I'm sure there is a security tech cursing loudly somewhere in the carriers NOC) and as a result it failed.
So the basic question is, has anyone found a smooth method for path discovery across an MPLS environment where you only manage the CE devices?
Also using a traceroute from an endstation to the target did yield better results, but there are occasions where I won't have access from a system on the source network.
I would prefer that the route table method be reliable as it should (and did where there is no L3 obsfucation via MPLS) find ALL paths, an important aspect of problem identification and resolution.
Thoughts?