US7734739B2 - Method and system for consolidating network topology in duplicate IP networks - Google Patents

Method and system for consolidating network topology in duplicate IP networks Download PDF

Info

Publication number
US7734739B2
US7734739B2 US09/838,239 US83823901A US7734739B2 US 7734739 B2 US7734739 B2 US 7734739B2 US 83823901 A US83823901 A US 83823901A US 7734739 B2 US7734739 B2 US 7734739B2
Authority
US
United States
Prior art keywords
management
network
computer
collection
management domain
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US09/838,239
Other languages
English (en)
Other versions
US20020156883A1 (en
Inventor
Srikanth Natarajan
Darren D. Smith
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hewlett Packard Enterprise Development LP
Original Assignee
Hewlett Packard Development Co LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hewlett Packard Development Co LP filed Critical Hewlett Packard Development Co LP
Assigned to HEWLETT-PACKARD COMPANY reassignment HEWLETT-PACKARD COMPANY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NATARAJAN, SANATH, SMITH, DARREN D.
Priority to US09/838,239 priority Critical patent/US7734739B2/en
Priority to JP2002038530A priority patent/JP2002344486A/ja
Assigned to HEWLETT-PACKARD COMPANY reassignment HEWLETT-PACKARD COMPANY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NATARAJAN, SRIKANTH, SMITH, DARREN D.
Priority to GB0208167A priority patent/GB2375919B/en
Publication of US20020156883A1 publication Critical patent/US20020156883A1/en
Assigned to HEWLETT-PACKARD DEVELOPMENT COMPANY L.P. reassignment HEWLETT-PACKARD DEVELOPMENT COMPANY L.P. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HEWLETT-PACKARD COMPANY
Publication of US7734739B2 publication Critical patent/US7734739B2/en
Application granted granted Critical
Assigned to HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP reassignment HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP ASSIGNMENT OF ASSIGNOR'S INTEREST Assignors: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5046—Resolving address allocation conflicts; Testing of addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies

Definitions

  • the present invention relates to computer networks. More particularly, the present invention relates to consolidating network topologies in duplicate Internet Protocol (IP) networks.
  • IP Internet Protocol
  • Management stations connected to a network are often configured by a management software package to discover the network topology, for example, the network nodes and node interconnections. From the network topology, the station constructs a network management map, which comprises a collection of various sub-maps. Each sub-map corresponds with a different view of the network and any sub-map can be displayed on a display device. These sub-maps can be arranged in a hierarchy.
  • a network management map implemented in the known “OPENVIEW”TM management software commercially available from the Hewlett-Packard Company, U.S.A.
  • An Internet sub-map is defined at an Internet level and is generated by exploding an object (i.e., providing more data regarding the object) within the root sub-map. This process of exploding can be iteratively repeated to any desired level of detail.
  • NNM Network Node Manager
  • the topology is populated by various techniques, such as discovery of network elements, manual addition of network elements by the end user and by collection of topology information sent by other NNM stations, known as collection stations. Collection stations send their data to another NNM station known as the management station.
  • IP Internet Protocol
  • a NNM management station receives data concerning a network element with an Internet Protocol (IP) address as a part of topology data from a collection station, it determines if some other collection station also reported the same IP address for a network element. If so, the NNM management station makes one network element a primary element and the other a secondary element.
  • IP Internet Protocol
  • a duplicate IP address can be a repeated IP host/interface address, a repeated hostname, or a repeated network name or address.
  • Duplicate IP addresses can occur when different companies use the same private or unregistered IP addresses. Duplicate IP addresses can also occur as a result of, for example, improperly configured network devices in which network elements in the same collision domain are communicating with the same IP address or two network nodes have the same hostname. Duplicate IP addresses can also occur as a result of stand-by router configurations (where the router and its stand-by use the same IP address).
  • a known technique for consolidating duplicate IP addresses into a single network topology involves displaying networks of different companies in a single console window, but separating them within that window in different customer containers based on the originating collection computer.
  • this technique does not provide the network manager with a consolidated network topology of all the customer networks that the network manager is managing, as the topology of each collection computer is displayed individually.
  • a collection computer is assigned a management domain identifier uniquely associated with a management domain in which each collection computer resides.
  • Information that includes the management domain identifier is received in at least one management computer from the collection computer.
  • a database of the information accessed using the management domain identifier is maintained within the at least one management computer.
  • FIG. 1 is a block diagram illustrating a network topology for managing a computer network in accordance with an exemplary embodiment of the present invention
  • FIG. 2 is a flow chart showing the steps for managing a computer network in accordance with an exemplary embodiment of the present invention
  • FIG. 3 is a flow chart showing the steps for determining primary and secondary network addresses in accordance with an exemplary embodiment of the present invention
  • FIG. 4 is a flow chart illustrating an exemplary method that can be used for verifying object identifiers in accordance with an exemplary embodiment of the present invention.
  • FIG. 5 is a block diagram illustrating identifications that can be accorded to objects in accordance with an exemplary embodiment of the present invention.
  • FIG. 1 is a block diagram illustrating a network 100 that is managed in accordance with an exemplary embodiment of the present invention.
  • network 100 can include a plurality of collection computers, wherein each collection computer is assigned a management domain identifier uniquely associated with a management domain in which each collection computer resides.
  • the collection computers can be, for example, collection stations 120 , 125 , 130 , and 135 .
  • Network 100 can also include at least one management computer for receiving information, from the plurality of collection computers, that includes the management domain identifier.
  • the management computer can be, for example, management station 105 .
  • Network 100 can also include at least one computer database for maintaining within the at least one management computer information accessed using the management domain identifier. Collection stations and management stations are described in, for example, U.S. Pat. No. 5,948,055.
  • collection stations can be deployed to monitor computer networks within, for example, remote customer sites.
  • collection stations 120 and 125 have been deployed to monitor a first computer network (e.g., a customer site designated as “CO”), while collection stations 130 and 135 have been deployed to monitor a second computer network (e.g., a customer site designated as “NY”).
  • each of the first and second computer networks can be connected to at least one management station, for example, management station 105 .
  • a first network element 140 is designated by any IP address, for example, “10.2.112.1”, that is unique within first computer network 140 .
  • a second network element is designated by any IP address, for example, “10.2.112.1”, that is unique within second computer network 145 .
  • the designated IP address of, for example, “10.2.112.1” is not unique.
  • collection stations have been deployed at different customer sites, where the different customer sites have duplicate IP addresses between them.
  • those of ordinary skill will recognize that different customer sites can have not only duplicate IP addresses between them, but also duplicate network names and duplicate hostnames.
  • a collection computer can be assigned a management domain identifier uniquely associated with a management domain in which the collection computer resides.
  • a management domain is a network within which IP addresses, network names, and hostnames are unique. Accordingly, IP addresses, network names, and hostnames can repeat across management domains.
  • at least one management domain can be established, wherein each management domain can include at least one collection computer.
  • the collection stations monitoring first computer network 140 can be designated as a first management domain 110 .
  • First management domain 110 can include, for example, collection stations 120 and 125 .
  • the collection stations monitoring second computer network 145 can be designated as a second management domain 115 .
  • Second management domain 115 can include, for example, collection stations 130 and 135 .
  • a management domain identifier is uniquely associated with each management domain.
  • the management domain identifier can be, for example, the domain name of the management domain.
  • the management domain identifier for collection stations 120 and 125 corresponding to management domain 110 would be “CO”.
  • the management domain identifier for collections stations 130 and 135 corresponding to management domain 115 would be “NY”. However, any management domain identifier which uniquely identifies a management domain can be associated with each management domain. Consequently, different management domain identifiers can be assigned to the collection stations monitoring networks of different customers, and the same management domain identifiers can be assigned to the collection stations monitoring the networks of the same customer.
  • At least one management computer receives information from the collection computers (e.g., collection stations 120 , 125 , 130 , and 135 ) that is gathered while monitoring the collection computers' respective computer networks.
  • the information received at the management station from the collection computers can be network topology information that includes the management domain identifier of the management domain in which the collection computer resides.
  • a database of the information received at the at least one management computer can be maintained within the at least one management computer.
  • the information such as, for example, network topology information
  • the management domain identifiers can be used to consolidate network topology information from collection computers having identical network addresses and belonging to different management domains.
  • the consolidated network topology can be, for example, displayed to an operator on the management computer, such as, for example, management station 105 or any other computer display device.
  • management domains 110 and 115 can be simultaneously displayed to an operator through the management computer as a consolidated network topology. Since management domains 110 and 115 correspond to different domains (e.g., customer sites), management domains 110 and 115 are not merged in the consolidated topology displayed to an operator. However, the information received from collection computers contained within a management domain can be merged. For example, the information from collection stations 120 and 125 can be merged in management domain 110 and the information from collection stations 130 and 135 can be merged in management domain 115 .
  • an operator can view the merged information from the collection computers within each management domain in a single, merged topology through the management computer (e.g., management station 105 ), and the operator can also view the consolidated topology across management domains through the management computer (e.g., management station 105 ), even though IP addresses are duplicated across management domains.
  • “merging” can refer to the consolidation of network topology within a management domain
  • “consolidation” can refer to the consolidation of network topology across management domains. Merging and displaying a network topology to an operator is discussed, for example, in U.S. Pat. No. 5,948,055.
  • collection stations 120 and 125 can each monitor first computer network 140 having a first network element, and collection stations 130 and 135 can each monitor second computer network 145 having a second network element. Because two collection stations can monitor the same computer network, overlapping coverage of network elements by collection stations within a management domain can cause duplicate IP addresses to be reported to a management station. As discussed previously, when a management station receives duplicate IP addresses, it can attempt to assign a network element reported from one collection station as a primary network element and the network element reported from the other collection station as a secondary network element.
  • At least one management computer can receive first information from a first collection computer, wherein the first information includes a first network address and a first management domain identifier.
  • the management computer can receive second information from a second collection computer, wherein the second information includes a second network address and a second management domain identifier.
  • the second network address can be identical to the first network address.
  • the management computer can compare the second network address to the first network address using the second management domain identifier and the first management domain identifier.
  • the management computer can assign the network element associated with the second network address as a primary network element when the second network address belongs to a different management domain than the first network address.
  • the management computer can assign the second network element associated with the second network address as a secondary network element when the second network address belongs to the same management domain as the first network address.
  • management station 105 when management station 105 receives an IP address as a part of topology data from a collection station, management station 105 can check to determine whether some other collection station also reported the same IP address. If so, management station 105 designates one network element with that IP address as the primary network element and the other network element as the secondary network element. Thus, to determine whether a network element is primary or secondary, management station 105 can use the management domain identifier to determine whether the network element with the received IP address belongs to the same domain as the duplicate IP address or not. If the network element does belong to the same domain, then the network element is a secondary network element, otherwise the network element is designated as a primary network element.
  • topology objects are the internal representation of real world objects, and the term is used to refer both to the organization of the data as well as to the internal structures used to track that data.
  • the DIMS will track a body of data about that node. That data is stored in a form that models that node in a topology database that resides within a management station.
  • topology manager running within a management station and the applications that deal with it will read that data into an internal structure that represents that node's data, and that internal structure is referred to as a “topology node object” or just a “node.”
  • each topology manager can track the following types of objects: (a) a node object that represents the computers and connective devices in a network; (b) an interface object that represents the logical connections of the node to various networks; every interface must be associated with a node, and a node may have zero or more interfaces; (c) a segment object that represents a physical cable to which nodes are attached via interfaces; a segment conceptually contains those nodes which have interfaces connected to the segment; (d) a network object that represents a logical IP network; (e) the network object conceptually contains several segments and the nodes that are connected to those segments; (f) a global Internet object that contains global information and conceptually contains all other objects; and (g) a station object that represents a remote node that is acting as a host for the collection station software; a station object conceptually contains all the objects that are reported by that collection station's topology manager.
  • Each type of object can have a unique type of “name” field that is used to identify it.
  • names For example, networks have an “IP Network Name” that is based on the IP subnet address and subnet mask of the network. Segments can have an “IP Segment Name” that can be composed of the name of the network that contains the segment, and the word “segment” with a unique number after it.
  • Nodes can have an “IP Hostname” that can be based on the official IP hostname of the node, while each interface can have an IP address.
  • IDs identifiers
  • each individual object has a “universal unique identifier” (UUID).
  • UUID universalal unique identifier”
  • the UUID is basically a string that is guaranteed to be unique across multiple collection computers.
  • each object has associated with it a local identifier called the “local object ID”.
  • This identifier is an integer for use within a collection computer.
  • DIMS when multiple versions of an object are reported with the same name field, they should all map to the same local object ID.
  • a collection computer can be represented by the following topology node object in the DIMS:
  • two additional fields can be added to the topology node object: a management domain identifier and a trust name flag.
  • the management domain identifier can be, for example, an attribute of the collection station object and the trust name can be, for example, a single bit flag in the collection station object. If no management domain identifier is specified, the management station can assign the collection station a management domain identifier, such as, for example, “Default.”
  • the trust name flag can be used by the management station to determine whether or not the hostname is name trustworthy, i.e., whether or not to use or trust the hostname being reported by the collection station.
  • the hostname of the network element as reported from the collection station will be used as the name of the network element, otherwise it will be recomputed at the management station based on, for example, the IP address of the interfaces associated with the network element or node.
  • a field name such as, for example, “DOMAIN NAME”
  • the “FLAGS” field can reflect whether, for example, the “TRUSTNAME” is set or not for the collection station.
  • the command used to configure a station as a collection station is the “xnmtopoconf” command.
  • This command takes numerous options, including the “-add” option.
  • the add option can be modified to accept two additional options: “-domain ⁇ domain name>” and “-trustname”, respectively.
  • the “ ⁇ domain name>” is the name of the management domain that is to be assigned to the collection station. If “-trustname” is specified as part of the command, then the hostname being reported by the collection station will be trusted and used to name a network element.
  • the xnmtopoconf command can automatically send an event to a remote collection station telling the remote collection station that it should transmit the names of all objects about which it is reporting.
  • An example of using the xnmtopoconf is: xnmtopoconf -add -domain “domainA” -trustname.
  • a management station includes a topology replicator that enables the management station to obtain other sets of topology data from other management stations or collection stations in order to derive a global view of the network.
  • the topology replicator is responsible for tracking data from remote topology managers, which are situated within other management stations and collection stations, and merging that data into the local topology database.
  • the replicator process receives an object from one of the stations, the management station attempts to get the hostname of the object even though the collection station had sent the name as part of the object information (e.g., the “STATION NAME” field).
  • each collection computer can manage at least one network object.
  • a network object can be, for example, a computer, a router, another collection computer, or any other computer network device.
  • the management computer e.g., management station 105
  • the management computer can be configured to perform hostname resolution of the network objects that are managed by each collection computer.
  • a collection computer e.g., collection stations 120 , 125 , 130 , and 135
  • each collection computer can resolve a network address or hostname of each network object.
  • the resolved network address or hostname can be included in the information that is received at the at least one management computer.
  • the management station can determine if the collection station from which the object came is name trustworthy or not. If it is name trustworthy, then the replicator will not try to perform hostname resolution for the hostname for the object, otherwise it will. Performing hostname resolution by the collection computers can prevent management computers from failing because of an inability to resolve hostnames or because of the occurrence of duplicate hostnames.
  • an object can be added by the topology manager to the consolidated network topology maintained within the topology database residing within the management station.
  • the add object process for example, verifies the integrity of the object, inserts the object into the network topology database and determines if there is an overlap with another object reported from a collection station or another management station.
  • step 401 a determination is made as to whether the object has a UUID. If not, then step 401 transfers to step 402 , which sets an error indicator, and the subroutine 402 concludes by returning to the add object process. If the object does have a UUID, then step 401 transfers to step 403 . At step 403 , an inquiry is made as to whether the local object ID has been set for the object. If not, then step 403 transfers to step 404 .
  • step 404 a determination is made as to whether the object has the same attributes (e.g., name, type, physical or link-level address, or subnet mask) in the same management domain as an existing object in the local object ID set. If not, then step 404 transfers to step 405 , which allocates a new local object ID for the object. If there is a match, then step 404 transfers to step 406 , which sets the local object ID to match the existing object ID. After steps 405 , 406 , or alternatively, when it is determined that the object has a local object ID at step 403 , step 407 is executed. At step 407 , a determination is made as to whether the object has a remote object ID. If not, then step 407 transfers to step 408 , where a determination is made as to whether the object is locally monitored. If yes, then step 408 transfers to step 409 , which sets the remote object ID to the local object ID.
  • the same attributes e.g., name, type, physical or link-level address, or sub
  • network object representation 502 is the representation of a network object in a first collection station (e.g., collection station 120 of FIG. 1 )
  • network object representation 504 is the representation of a network object in a second collection station (e.g., collection station 125 of FIG. 1 )
  • network object representation 506 is the representation of a network object in a third collection station (e.g., collection station 130 of FIG. 1 )
  • network object representation 508 is the representation of a network object in a fourth collection station (e.g., collection station 135 of FIG. 1 ).
  • the local object ID on the remote collection station is copied into a field in the object called the “remote object ID” at the management station.
  • the remote object ID is tracked by the replicator of the management station and used to communicate with the remote collection station.
  • the UUID for each object remains the same in both the remote collection station and the management station.
  • network objects with the same hostname get the same local object ID.
  • internal network object representations can be separated by management domain.
  • internal network object representations 510 and 512 correspond to management domain 514
  • internal network object representations 516 and 518 correspond to management domain 520 .
  • the management station can assign the same object IDs to network object representations belonging to the same management domain and different object IDs to network object representations belonging to different management domains.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
US09/838,239 2001-04-20 2001-04-20 Method and system for consolidating network topology in duplicate IP networks Active 2026-10-26 US7734739B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US09/838,239 US7734739B2 (en) 2001-04-20 2001-04-20 Method and system for consolidating network topology in duplicate IP networks
JP2002038530A JP2002344486A (ja) 2001-04-20 2002-02-15 二重ｉｐネットワークにおいてネットワークトポロジを統合するための方法
GB0208167A GB2375919B (en) 2001-04-20 2002-04-09 Method and system for consolidating network topology in duplicate ip networks

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US09/838,239 US7734739B2 (en) 2001-04-20 2001-04-20 Method and system for consolidating network topology in duplicate IP networks

Publications (2)

Publication Number Publication Date
US20020156883A1 US20020156883A1 (en) 2002-10-24
US7734739B2 true US7734739B2 (en) 2010-06-08

Family

ID=25276615

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/838,239 Active 2026-10-26 US7734739B2 (en) 2001-04-20 2001-04-20 Method and system for consolidating network topology in duplicate IP networks

Country Status (3)

Country Link
US (1) US7734739B2 (enExample)
JP (1) JP2002344486A (enExample)
GB (1) GB2375919B (enExample)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120131156A1 (en) * 2010-11-24 2012-05-24 Brandt Mark S Obtaining unique addresses and fully-qualified domain names in a server hosting system
US20120315037A1 (en) * 2011-06-09 2012-12-13 Ciena Corporation Splitting and merging routing domains
US20140330868A1 (en) * 2012-04-23 2014-11-06 Citrix Systems, Inc. Trusted file indirection
US11070435B2 (en) 2019-01-16 2021-07-20 Servicenow, Inc. Service model re-computation based on configuration item change type

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7398326B2 (en) * 2002-04-25 2008-07-08 International Business Machines Corporation Methods for management of mixed protocol storage area networks
FR2841077B1 (fr) * 2002-06-17 2004-11-19 Orange France Sa Systeme et procede de gestion sur un terminal de l'architecture dediee a un reseau de communication
US7672268B2 (en) * 2004-06-18 2010-03-02 Kenneth Stanwood Systems and methods for implementing double wide channels in a communication system
US8862722B2 (en) * 2010-03-31 2014-10-14 Verizon Patent And Licensing Inc. Method and system for providing monitoring of network environment changes
US8825839B2 (en) * 2010-11-24 2014-09-02 Unisys Corporation Snooping DNS messages in a server hosting system providing overlapping address and name spaces
US8850322B2 (en) * 2011-11-18 2014-09-30 Verizon Patent And Licensing Inc. Customized diagrammatic view of a network topology
WO2014094224A1 (zh) 2012-12-18 2014-06-26 华为技术有限公司 一种确定管理域的方法、网络设备及虚拟集群
US9584367B2 (en) * 2013-11-05 2017-02-28 Solarwinds Worldwide, Llc Node de-duplication in a network monitoring system
US20180077169A1 (en) * 2016-09-14 2018-03-15 Rapid Focus Security, Llc Reflective Network Device Position Identification
US10509541B2 (en) * 2016-10-25 2019-12-17 Servicenow, Inc. System and method for generating geographical maps for initiating discovery of a computer network
US10320619B2 (en) * 2016-11-12 2019-06-11 Solana Networks Inc. Method and system for discovery and mapping of a network topology
US12340249B2 (en) 2017-12-29 2025-06-24 Virtual Instruments Worldwide, Inc. Methods and system for throttling analytics processing
US11223534B2 (en) 2017-12-29 2022-01-11 Virtual Instruments Worldwide, Inc. Systems and methods for hub and spoke cross topology traversal
US10768970B2 (en) 2017-12-29 2020-09-08 Virtual Instruments Corporation System and method of flow source discovery
WO2020092658A1 (en) * 2018-10-30 2020-05-07 Devin Blinn Avery Systems and methods for hub and spoke cross topology traversal
US11561699B2 (en) * 2020-04-24 2023-01-24 EMC IP Holding Company LLC Input-output path selection using switch topology information

Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5448727A (en) * 1991-04-30 1995-09-05 Hewlett-Packard Company Domain based partitioning and reclustering of relations in object-oriented relational database management systems
US5577252A (en) * 1993-07-28 1996-11-19 Sun Microsystems, Inc. Methods and apparatus for implementing secure name servers in an object-oriented system
US5787252A (en) * 1995-11-01 1998-07-28 Hewlett-Packard Company Filtering system and method for high performance network management map
US5793974A (en) * 1995-06-30 1998-08-11 Sun Microsystems, Inc. Network navigation and viewing system for network management system
US5948055A (en) 1996-08-29 1999-09-07 Hewlett-Packard Company Distributed internet monitoring system and method
US5968121A (en) * 1997-08-13 1999-10-19 Microsoft Corporation Method and apparatus for representing and applying network topological data
US6041349A (en) * 1996-02-29 2000-03-21 Hitachi, Ltd. System management/network correspondence display method and system therefor
US6076114A (en) * 1997-04-18 2000-06-13 International Business Machines Corporation Methods, systems and computer program products for reliable data transmission over communications networks
WO2000049769A1 (en) 1999-02-16 2000-08-24 Electronic Data Systems Corporation System and method for remote management of private networks having duplicate network addresses
US6119171A (en) * 1998-01-29 2000-09-12 Ip Dynamics, Inc. Domain name routing
US6125447A (en) * 1997-12-11 2000-09-26 Sun Microsystems, Inc. Protection domains to provide security in a computer system
US6167052A (en) * 1998-04-27 2000-12-26 Vpnx.Com, Inc. Establishing connectivity in networks
US6343064B1 (en) * 1998-08-04 2002-01-29 Electronic Data Systems Corporation Method and system for remote management of equipment having duplicate network addresses
US6405248B1 (en) * 1998-12-02 2002-06-11 Micromuse, Inc. Method and apparatus for determining accurate topology features of a network
US6408336B1 (en) * 1997-03-10 2002-06-18 David S. Schneider Distributed administration of access to information
US6430613B1 (en) * 1998-04-15 2002-08-06 Bull, S.A. Process and system for network and system management
US6457053B1 (en) * 1998-09-21 2002-09-24 Microsoft Corporation Multi-master unique identifier allocation
US20020156882A1 (en) 2001-04-20 2002-10-24 Srikanth Natarajan Method and system for identifying event source in duplicate IP networks
US6574633B1 (en) * 1999-11-01 2003-06-03 Honeywell International Inc. Method for dynamically grouping limited range physical entities in a topological space
US6665715B1 (en) * 2000-04-03 2003-12-16 Infosplit Inc Method and systems for locating geographical locations of online users
US6697851B1 (en) * 1999-09-02 2004-02-24 International Business Machines Corporation Method and apparatus for identifying clients using incoming option data
US6854016B1 (en) * 2000-06-19 2005-02-08 International Business Machines Corporation System and method for a web based trust model governing delivery of services and programs

Patent Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5448727A (en) * 1991-04-30 1995-09-05 Hewlett-Packard Company Domain based partitioning and reclustering of relations in object-oriented relational database management systems
US5577252A (en) * 1993-07-28 1996-11-19 Sun Microsystems, Inc. Methods and apparatus for implementing secure name servers in an object-oriented system
US5793974A (en) * 1995-06-30 1998-08-11 Sun Microsystems, Inc. Network navigation and viewing system for network management system
US6425007B1 (en) * 1995-06-30 2002-07-23 Sun Microsystems, Inc. Network navigation and viewing system for network management system
US5787252A (en) * 1995-11-01 1998-07-28 Hewlett-Packard Company Filtering system and method for high performance network management map
US6041349A (en) * 1996-02-29 2000-03-21 Hitachi, Ltd. System management/network correspondence display method and system therefor
US5948055A (en) 1996-08-29 1999-09-07 Hewlett-Packard Company Distributed internet monitoring system and method
US6408336B1 (en) * 1997-03-10 2002-06-18 David S. Schneider Distributed administration of access to information
US6076114A (en) * 1997-04-18 2000-06-13 International Business Machines Corporation Methods, systems and computer program products for reliable data transmission over communications networks
US5968121A (en) * 1997-08-13 1999-10-19 Microsoft Corporation Method and apparatus for representing and applying network topological data
US6125447A (en) * 1997-12-11 2000-09-26 Sun Microsystems, Inc. Protection domains to provide security in a computer system
US6119171A (en) * 1998-01-29 2000-09-12 Ip Dynamics, Inc. Domain name routing
US6430613B1 (en) * 1998-04-15 2002-08-06 Bull, S.A. Process and system for network and system management
US6167052A (en) * 1998-04-27 2000-12-26 Vpnx.Com, Inc. Establishing connectivity in networks
US6343064B1 (en) * 1998-08-04 2002-01-29 Electronic Data Systems Corporation Method and system for remote management of equipment having duplicate network addresses
US6457053B1 (en) * 1998-09-21 2002-09-24 Microsoft Corporation Multi-master unique identifier allocation
US6405248B1 (en) * 1998-12-02 2002-06-11 Micromuse, Inc. Method and apparatus for determining accurate topology features of a network
WO2000049769A1 (en) 1999-02-16 2000-08-24 Electronic Data Systems Corporation System and method for remote management of private networks having duplicate network addresses
US6697851B1 (en) * 1999-09-02 2004-02-24 International Business Machines Corporation Method and apparatus for identifying clients using incoming option data
US6574633B1 (en) * 1999-11-01 2003-06-03 Honeywell International Inc. Method for dynamically grouping limited range physical entities in a topological space
US6665715B1 (en) * 2000-04-03 2003-12-16 Infosplit Inc Method and systems for locating geographical locations of online users
US6854016B1 (en) * 2000-06-19 2005-02-08 International Business Machines Corporation System and method for a web based trust model governing delivery of services and programs
US20020156882A1 (en) 2001-04-20 2002-10-24 Srikanth Natarajan Method and system for identifying event source in duplicate IP networks

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Bannerman, S.; Stockdell, B.; Stutz, M.; "Network topology configuration management experience report" Telecommunications Information Networking Architecture Conference Proceedings, 1999. TINA '99 , Apr. 12-15, 1999 pp. 137-139. *
GB Search Report for Appln. No. GB 0208167.7 dated Sep. 18, 2002 1 page submitted.
Hwa-Chun Lin; Shou-Chuan Lai; Ping-Wen Chen; "An algorithm for automatic topology discovery of IP networks" Communications, 1998. ICC 98. Conference Record.1998 IEEE International Conference on , vol. 2 , Jun. 7-11, 1998 pp. 1192-1196 vol. 2. *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120131156A1 (en) * 2010-11-24 2012-05-24 Brandt Mark S Obtaining unique addresses and fully-qualified domain names in a server hosting system
US20120315037A1 (en) * 2011-06-09 2012-12-13 Ciena Corporation Splitting and merging routing domains
US8572485B2 (en) * 2011-06-09 2013-10-29 Ciena Corporation Splitting and merging routing domains
US20140330868A1 (en) * 2012-04-23 2014-11-06 Citrix Systems, Inc. Trusted file indirection
US10013421B2 (en) * 2012-04-23 2018-07-03 Citrix Systems, Inc. Trusted file indirection
US10929344B2 (en) * 2012-04-23 2021-02-23 Citrix Systems, Inc. Trusted file indirection
US11070435B2 (en) 2019-01-16 2021-07-20 Servicenow, Inc. Service model re-computation based on configuration item change type

Also Published As

Publication number Publication date
GB2375919B (en) 2004-06-16
US20020156883A1 (en) 2002-10-24
JP2002344486A (ja) 2002-11-29
GB0208167D0 (en) 2002-05-22
GB2375919A (en) 2002-11-27

Similar Documents

Publication Publication Date Title
US7734739B2 (en) Method and system for consolidating network topology in duplicate IP networks
US5948055A (en) Distributed internet monitoring system and method
US7809667B1 (en) Rule-based network resource compliance
US6442144B1 (en) Method and apparatus for discovering network devices using internet protocol and producing a corresponding graphical network map
US7340578B1 (en) Method and apparatus for maintaining an accurate inventory of storage capacity in a clustered data processing system
US7467203B2 (en) System and methods for robust discovery of servers and services in a heterogeneous environment
US6816896B2 (en) Method and apparatus for detecting changes to network elements
EP1021014B1 (en) Method and system for network management
US7702655B1 (en) Maintaining and using user-created mapping history for network resource mapping
US20040230828A1 (en) Software update and patch audit subsystem for use in a computer information database system
CN109861861B (zh) 一种可用于网络通信设备的快速配置方法及系统
US20040093408A1 (en) IT asset tracking system
US20060031435A1 (en) System and method for configuring a network device
US20020019864A1 (en) System and method for managing the configuration of hierarchically networked data processing devices
US20010029534A1 (en) Network resource location detection probe apparatus and method
JP2004254270A (ja) ストレージネットワーク管理のシステムと方法
EP2361465B1 (en) Retrieving configuration records from a configuration management database
US7657499B2 (en) Grouping of computers in a computer information database system
EP1589691B1 (en) Method, system and apparatus for managing computer identity
US7673031B1 (en) Resource mapping in a network environment
US8595339B2 (en) Network management apparatus and method
US20060195566A1 (en) Method and system for taking remote inventory in a network
CN114338419B (zh) 一种IPv6全球组网边缘节点监测及预警方法及系统
US7398310B1 (en) Method and system for tracking entities in a computer network
US20020156882A1 (en) Method and system for identifying event source in duplicate IP networks

Legal Events

Date Code Title Description
AS Assignment

Owner name: HEWLETT-PACKARD COMPANY, COLORADO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NATARAJAN, SANATH;SMITH, DARREN D.;REEL/FRAME:011723/0795

Effective date: 20010419

Owner name: HEWLETT-PACKARD COMPANY,COLORADO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NATARAJAN, SANATH;SMITH, DARREN D.;REEL/FRAME:011723/0795

Effective date: 20010419

AS Assignment

Owner name: HEWLETT-PACKARD COMPANY, COLORADO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NATARAJAN, SRIKANTH;SMITH, DARREN D.;REEL/FRAME:012797/0079

Effective date: 20020328

Owner name: HEWLETT-PACKARD COMPANY,COLORADO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NATARAJAN, SRIKANTH;SMITH, DARREN D.;REEL/FRAME:012797/0079

Effective date: 20020328

AS Assignment

Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY L.P., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD COMPANY;REEL/FRAME:014061/0492

Effective date: 20030926

Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY L.P.,TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD COMPANY;REEL/FRAME:014061/0492

Effective date: 20030926

STCF Information on status: patent grant

Free format text: PATENTED CASE

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP, TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.;REEL/FRAME:037079/0001

Effective date: 20151027

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552)

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12