Method and system for managing multiple overlapping address domains

• US 20050271047A1
• Filed: 06/02/2004
• Published: 12/08/2005
• Est. Priority Date: 06/02/2004
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Walker, Anthony P., Okine, Daniel, Ganesan, Nitya, Huonder, Russell J., Gupta, Dipankar, Natarajan, Srikanth
• Application Number:
  US10/858,891
• Publication Number:
  US 20050271047A1
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0846 based on copy from other elements
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 61/2535 Multiple local networks, e.g. resolving potential IP address conflicts
• CPC Class Codes: H04L 61/5061 Pools of addresses

Abstract

One embodiment disclosed relates to a method of configuring a network including multiple overlapping private address domains. A configuration file is created for each overlapping address domain (OAD). The configuration file includes an identifier for the OAD, a gateway address to the OAD, and mappings between private addresses in the OAD and corresponding management addresses. Another embodiment relates to a system for managing a network including multiple OADs. Another embodiment relates to a method of processing a trap from a network with multiple OADs. Another embodiment relates to a method of finding an active route across a static NAT device.

Claims

1. A system for managing a network including multiple overlapping private address domains, the system comprising:

a computer system including software for a network management system; and

a plurality of network address translation (NAT) devices, each NAT device in the plurality being communicatively coupled to said computer system and communicatively coupled to one of the overlapping private address domains,

wherein a route distinguisher is associated with each overlapping private address domain to facilitate management thereof.

2. The system of claim 1, wherein the route distinguisher comprises an identification number.

3. The system of claim 2, wherein the route distinguisher further comprises a name string.

4. The system of claim 1, further comprising:

one or more configuration files accessible by the network management system and configured to store the route distinguisher.

5. The system of claim 1, further comprising:

a transmission control protocol/internet protocol (TCP/IP) stack in said computer system; and

a communication layer above the TCP/IP stack,

wherein said communication layer is configured to be aware of the multiple overlapping private address domains.

6. The system of claim 5, further comprising:

an application programming interface (API) layer above said communication layer,

wherein the API layer includes a duplicated-IP-address API, an SNMP API, and an ICMP API.

7. The system of claim 6, further comprising:

a module for trap/syslog reception communicatively coupled to said communication layer and to the duplicated-IP-address API.

8. The system of claim 7, further comprising:

a discovery engine coupled to said API layer.

9. The system of claim 8, further comprising:

data storage for storing a duplicated-IP-address aware network topology,

wherein said data storage is configured to be accessed by the discovery engine and by a fault analysis engine.

10. A method of configuring a network including multiple overlapping private address domains (OADs), the method comprising creating a configuration file for each OAD, wherein the configuration file includes an identifier for the OAD, a gateway address to the OAD, and mappings between private addresses in the OAD and corresponding management addresses.

11. The method of claim 10, further comprising creating a seed file for each OAD, wherein the seed file defines a discovery zone for the OAD.

12. The method of claim 11, further comprising verifying a correct syntax of the configuration and seed files.

13. The method of claim 12, further comprising:

loading data from the configuration and seed files into a network management system using a graphical user interface (GUI) to said system.

14. The method of claim 13, wherein the GUI includes a screen configured to display an identifying number, an identifying name, and a seed file name for each OAD, and wherein the screen is further configured to allow a user to initiate discovery for each OAD and to initiate deployment of changes to the running configuration.

15. A method of processing a trap from a network with multiple overlapping private address domains, the method comprising:

receiving a trap packet originating from a managed network device;

extracting a management internet protocol (IP) address from a header of the trap packet;

determining a domain identifier and a private IP address corresponding to the management IP address; and

using the domain identifier and private IP address to uniquely identify the managed network device.

16. The method of claim 15, wherein the trap packet comprises a simple network management protocol (SNMP) trap.

17. The method of claim 15, wherein the header comprises a user datagram protocol (UDP) header.

18. The method of claim 15, wherein the domain identifier and private IP address are retrieved from a configuration file accessible by the network management system.

19. The method of claim 15, wherein the domain identifier comprises an identifier for an overlapping private address domain.

20. The method of claim 15, further comprising:

attaching the domain identifier and the private IP address to an internal trap event for use by other software processes.

21. A method of finding an active route across a static network address translation (NAT) device, the method comprising:

finding a gateway to a private network, wherein the gateway comprises the static NAT device;

looking-up a private address of a next device in the private network;

determining a corresponding management address;

adding the management address to a route being calculated; and

repeating the looking-up, determining, and adding steps until the next device comprises a destination device.

22. The method of claim 21, further comprising, prior to finding the gateway:

looking-up a management address of a next-hop device;

adding the management address to the route being calculated; and

repeating the preceding two steps until the next-hop device comprises the gateway or the destination device.

23. The method of claim 21, wherein the corresponding management address is determined from a configuration file for an overlapping private address domain including mappings between private and management addresses.

24. An apparatus for configuring a network including multiple overlapping private address domains (OADs), the apparatus comprising means for creating a configuration file for each OAD, wherein the configuration file includes an identifier for the OAD, a gateway address to the OAD, and mappings between private addresses in the OAD and corresponding management addresses.

25. An apparatus for processing a trap from a network with multiple overlapping private address domains, the apparatus comprising:

means for receiving a trap packet originating from a managed network device;

means for extracting a management internet protocol (IP) address from a header of the trap packet;

means for determining a domain identifier and a private IP address corresponding to the management IP address; and

means for using the domain identifier and private IP address to uniquely identify the managed network device.

26. An apparatus for finding an active route across a static network address translation (NAT) device, the apparatus comprising:

means for finding a gateway to a private network, wherein the gateway comprises the static NAT device;

means for looking-up a private address of a next device in the private network;

means for determining a corresponding management address;

means for adding the management address to a route being calculated; and

means for repeating the looking-up, determining, and adding steps until the next device comprises a destination device.