Identifying hardcoded IP addresses

• US 10,171,301 B2
• Filed: 07/27/2015
• Issued: 01/01/2019
• Est. Priority Date: 07/27/2015
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Hunt, Anthony M., Perpetua, Jr., Dennis A., Raghavan, Srinivasa, Zolotow, Clea A.
• Primary Examiner(s): Vu, Viet D
• Assistant Examiner(s): Sowa, Timothy J
• Application Number:
  US14/809,353
• Publication Number:
  US 20170033994A1
• Time in Patent Office: 1,254 Days
• Field of Search: 709220
• CPC Class Codes: H04L 2101/622 Layer-2 addresses, e.g. medium access control [MAC] addresses
• CPC Class Codes: H04L 41/0859 by keeping history of different configuration generations or by rolling back to previous configuration versions
• CPC Class Codes: H04L 61/103 across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/58 Caching of addresses or names

Abstract

A method and associated systems for identifying hardcoded network addresses. A network-migration tool requests from a network certain types of data that may identify IP addresses used by the network and receives a subset of the requested data. The system infers from the manner in which received data characterizes IP addresses which of those addresses are likely to be hardcoded. If the system receives a list of server affinities, it infers that an IP address used for communication between servers in a same affinity group is hardcoded if that address is not listed by an associated DNS server. If a received ARP cache lists an IP address as having been resolved to a MAC address, the system infers that the IP address cannot be hardcoded. If a received TCP trace log lists an address without a corresponding hostname the system infers that the address is hardcoded.

Claims

1. A computerized network-migration system component of a network-management system comprising a processor, a memory coupled to the processor, a computer-readable hardware storage device coupled to the processor, and an interface to the network-management system, wherein the network-management system identifies network-configuration information that describes at least one component of a computer network to be migrated, wherein the interface allows the network-migration system to interactively access the network-configuration information, and wherein the storage device contains program code configured to be run by the processor via the memory to implement a method for identifying hardcoded IP addresses, the method comprising:

the network-migration system requesting a latest version of the network-configuration information;

the network-migration system receiving, in response to the requesting, a subset of the requested network-configuration information; and

the network-migration system choosing, as a function of a way in which an Internet Protocol address of a component of the computer network to be migrated is characterized in the received network-configuration information, where the received network-configuration information does not comprise source code of a software application, a method of identifying whether the Internet Protocol address is hardcoded,

where the method is selected from the group consisting of;

a network-view method that determines whether a received DNS list comprises a first network address identified by a received server-affinity listing

a server-based method that determines whether a received list of ARP address lookups identifies a first network address, and

a trace-log method that determines whether a received TCP trace log identifies a first network address but does not associate a hostname with the first network address.

2. The network-migration system of claim 1, wherein the network-configuration information requested by the network-migration system comprises:

a server-affinity listing that identifies a network address and corresponding hostname used by two or more servers comprised by the network to be migrated, wherein the two or more servers must use the network address and corresponding hostname to communicate with each other in order to function correctly,

a list of ARP address lookups stored in an address-resolution protocol cache associated with the computer network,

a DNS list of hostnames maintained by a Domain Name System server associated with the computer network,

a listing of open network connections between a component of the computer network and a component of a remote resource that is not comprised by the computer network, and

a TCP trace log that has recorded one or more operations of the computer network.

3. The network-migration system of claim 1, wherein the network-view method determines that the first network address is a hardcoded address because the first network address is not comprised by the received DNS list.

4. The network-migration system of claim 1, wherein the server-based method determines that the first network address is a hardcoded address because the address is not identified by the received list of ARP address lookups.

5. The network-migration system of claim 1, wherein the trace-log method determines that the first network address is a hardcoded address because the address is not associated in the received TCP trace log with a hostname.

6. The network-migration system of claim 1, wherein the system chooses the network-view method in response to receiving the received server-affinity listing and the received DNS list.

7. The network-migration system of claim 1, wherein the system chooses the server-based method in response to receiving the received list of ARP address lookups and a received listing of open network connections and in further response to a failure to receive a server-affinity listing.

8. The network-migration system of claim 1, wherein the system chooses the trace-log method in response to receiving the received TCP trace log.

9. The network-migration system of claim 8, wherein the system further chooses the trace-log method in response to determining that utilization of the computer network to be migrated falls below a threshold level.