Thank you very much Chris for your prompt consideration on my problem. Actually sometimes we configure routers with static configuration in this case the priority is given to the path that is described by static route, in other words the dynamic protocols are ignored, similarly some times due to router failure or disable interface the path packet takes is not the one that we expect( IGP path) so how would i detect the situation through script that prompts me that the path is not expected one may be there is router failure or static configurtion. i am giving traceroute result that helps further to understand problem first traceroute result is the one that is expected by OSPF and second one is which represents problem that shows that there might be a static route configuration or disable interface

1 10.0.0.53 (10.0.0.49) 0.478 ms 0.457 ms 0.478 ms 2 10.0.0.58 (10.0.0.58) 0.867 ms 0.780 ms 0.846 ms 3 10.0.0.138 (10.0.0.138) 1.401 ms 1.438 ms 1.198 ms ========================================================= 2nd tracerroute result 1 10.0.0.73 (10.0.0.73) 0.452 ms 0.443 ms 0.382 ms 2 10.0.0.78 (10.0.0.78) 0.900 ms 0.782 ms 0.783 ms 3 10.0.0.62 (10.0.0.62) 1.246 ms 1.197 ms 1.145 ms 4 10.0.0.49 (10.0.0.49) 1.642 ms 1.497 ms 1.437 ms 5 10.0.0.58 (10.0.0.58) 1.976 ms 1.660 ms 1.755 ms 6 10.0.0.138 (10.0.0.138) 2.209 ms 2.114 ms 2.071 ms
========================================================== Question 2:how to do to build a model of the IGP shortest paths in perl by using one of Graph perl modules, and build the graph of the OSPF adjacencies between the routers, with their IGP weights to get shortest path that will give expected paths between all routers?

In reply to Re^2: Comparing routing path if it is in agreement to IGP by zakishah
in thread Comparing routing path if it is in agreement to IGP by zakishah

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.