NETWORK CHECK USING ROUTING DATABASE

• US 20080192651A1
• Filed: 02/07/2008
• Published: 08/14/2008
• Est. Priority Date: 02/09/2007
• Status: Abandoned Application

• Current Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Original Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Inventors: Gibbings, Christopher J.
• Application Number:
  US12/027,464
• Publication Number:
  US 20080192651A1
• Time in Patent Office: Days
• US Class Current: 370/254
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/03 by updating link state protocols
• CPC Class Codes: H04L 45/42 Centralised routing
• CPC Class Codes: H04L 45/52 Multiprotocol routers

Abstract

A system can check links of a plurality of networks that use different routing protocols. The system derives link states from a copy of a routing database according to the format of the routing database. The derived link states are formatted into a reference format and compared to reference link states to determine link state differences. A reference link state file can be updated based on the determined link state differences. A method involves obtaining a copy of a routing database from a router and deriving current link states from the copy of the routing database according to the format of the routing database. The derived link states are formatted into a reference format. The current link states are compared to reference link states to determine link state differences. User-friendly router names and router interface names are obtained from, for example, a router configuration file. IP addresses in the link state differences are mapped to the router names and router interface names. The link state differences can then be presented in a user friendly presentation to the user including router names and router interface names.

Claims

1. A method for determining changes in network topology, the method comprising:

obtaining a copy of a routing database from a router in a network;

deriving current link states from the copy of the routing database according to a routing database format associated with the routing protocol used on the network;

formatting the current link states into a reference format;

comparing the formatted current link states to reference link states to determine differences between the current link states and the reference link states.

2. The method of claim 1, wherein obtaining a copy of the routing database comprises logging in to the router and requesting the routing database from the router.

3. The method of claim 1, wherein obtaining a copy of the routing database comprises requesting the routing database through a management connection to the router.

4. The method of claim 1, wherein obtaining a copy of the routing database comprises receiving the copy of the routing database by a computer that does not participate in the routing protocol.

5. The method of claim 1, further comprising obtaining router interface names identifying router interfaces associated with one or more routers on the network.

6. The method of claim 5, further comprising mapping Internet Protocol addresses of router interfaces in the routing database with associated ones of the router interface names.

7. The method of claim 6, further comprising presenting the determined link state differences in a user-friendly presentation including the router interface names.

8. The method of claim 1, wherein the reference link states are prior network link states.

9. The method of claim 1, further comprising updating the reference link states based on the determined link state differences.

10. The method of claim 1, further comprising receiving input from a user indicating one or more link state changes that are permanent.

11. A system for determining changes in a network topology, the system comprising:

a link state capture module configured to obtain a copy of a routing database from a connected router;

a link state derivation module configured to derive current link states from the copy of the routing database according to a routing protocol database format associated with a routing protocol used by the router;

a formatting module configured to format the derived current link states into a reference format;

a comparing module configured to compare the current link states to reference link states to determine one or more link state differences.

12. The system of claim 11, further comprising a names determination module configured to obtain router interface names and map the router names to IP addresses in the link state differences.

13. The system of claim 11, wherein the link state capture module obtains a copy of the routing database by logging in to the network router via a management connection to the network router.

14. The system of claim 11, wherein the link state capture module does not participate in the routing protocol with the network router.

15. The system of claim 12, further comprising an output module configured to present the link state differences in a user-friendly presentation including the mapped router interface names.

16. The system of claim 15, wherein the user-friendly presentation presents link state differences on a link-by-link basis.

17. The system of claim 16, wherein the link-by-link presentation identifies both network routers on either end of a link and both router interfaces on either end of the link.

18. The system of claim 15 wherein the link state differences that are presented include one or more of removed links, added links, removed routers, added routers, changed metrics, changed bandwidth, changed router identifier, and changed color.

19. The system of claim 11, further comprising a reference link state update module configured to use the link state differences to update the reference link states to correspond to the current link states.

20. The system of claim 11, further comprising a reference link state update module configured to update the reference link states with changes that a user selects as permanent.

21. The system of claim 11, wherein the routing protocols include an Open Shortest Path First (OSPF) routing protocol, an OSPF protocol with Traffic Engineering (TE) extensions, and intermediate system to intermediate system (IS-IS) protocol.