Enhance the traceroute output
After working with MPLS Traffic Engineering lab for a few days and interpreting IP addresses from various traceroute outputs, I finally had enough and wrote a simple Perl script that parses router configurations and produces ip host configuration commands for every interface IP address it encounters. When you paste the ip host commands into the configuration of the edge router from which you do the tests, the meaningless numbers finally make sense.
Just compare the “traditional” output produced in the MPLS TE test lab …
PE-A#traceroute PE-C Type escape sequence to abort. Tracing the route to PE-C (10.0.1.5) 1 10.0.7.6 [MPLS: Label 1017 Exp 0] 16 msec 136 msec 52 msec 2 10.0.7.26 [MPLS: Label 3018 Exp 0] 8 msec 20 msec 8 msec 3 10.0.7.30 [MPLS: Label 4018 Exp 0] 16 msec 20 msec 56 msec 4 10.0.7.33 [MPLS: Label 2017 Exp 0] 20 msec 44 msec 20 msec 5 10.0.7.17 24 msec * 24 msec
… with this one:
PE-A#traceroute PE-C Type escape sequence to abort. Tracing the route to PE-C (10.0.1.5) 1 Serial1-0.C1 (10.0.7.6) [MPLS: Label 1017 Exp 0] 56 msec 2 Serial1-2.C3 (10.0.7.26) [MPLS: Label 3018 Exp 0] 12 msec 3 Serial1-1.C4 (10.0.7.30) [MPLS: Label 4018 Exp 0] 48 msec 4 Serial1-2.C2 (10.0.7.33) [MPLS: Label 2017 Exp 0] 52 msec 5 Serial1-0.PE-C (10.0.7.17) 16 msec * 64 msec
0 comments:
Post a Comment