The present application relates to network management systems, and more particularly to a system for acquiring and providing physical location information and other information related to physical layer infrastructure, such as environmental information, about network elements.
Communication networks are growing in number and complexity. Data centers that house network elements have likewise grown increasingly large and complex. With this growing complexity, it can be difficult for network administrators to maintain accurate records regarding the physical locations of assets within a communication network. In many cases, the physical location of network assets is tracked manually, with significant opportunities for errors or omissions.
This can lead to many problems for network administrators and technicians. It is possible for an administrator or technician to know where a fault is within a network based on the logical network topology, but not to know exactly where in a particular building the fault is located. More particularly, it is possible in some network management systems to know that a server connected to a particular switch port is experiencing a fault, but if the physical location records are not accurate, it may take a significant amount of work to actually determine the physical location of the faulty server.
The lack of information regarding physical location of assets can also cause problems with network growth planning. For example, a network administrator or technician may have little idea of how much free space, connectivity, thermal capacity, power capacity, or functioning physical layer is available in cabinets in a data center without undertaking a significant effort in manually mapping out the location of network assets and related physical layer infrastructure elements on a cabinet-by-cabinet basis.
Another challenge encountered in expansion planning is a lack of knowledge about the physical environment where expansion is desirable or necessary. For example, an administrator may know that rack space is available for installation of a new group of servers. But the administrator may have little to no information about the impact that adding a server group will have on the power consumption, heat generation, structural cabling, power capacity, weight, security, or grounding in a cabinet or area of a data center. In some cases, this could necessitate an engineering review that will add expense and delay to network expansion projects. In addition, the lack of important information inhibits automation since the physical representation of a network may not be reconciled with the logical connections within the network.
It is desirable to have a system that addresses the problems listed above by automatically acquiring and tracking physical location information regarding network assets and by providing physical layer infrastructure data and other environmental information regarding network installations.
The present application provides a system that uses intelligent patch panels with enhanced patch cords and software to enable the discovery and updating of physical location information for network elements, as well as other information associated with a container or other boundary relevant to network design and operations information. The present invention uses hardware and methodologies discussed in U.S. Provisional Patent Application Ser. No. 61/113,868, entitled “Intelligent Patching System,” and filed on Nov. 12, 2008, which is incorporated herein by reference in its entirety.
Patch panels can be incorporated into a network in two different general deployment styles. In the first style, called “interconnect,” a patch panel is connected directly to network switching over horizontal cabling, with the horizontal cabling generally attached to the back panel of the patch panel. In an interconnect deployment, other network equipment is connected to the front of the patch panel for communication with the network switches. In the second style, called “cross connect,” two patch panels are used between a switch and other network equipment that connects to the switch. Both styles of deployment have advantages. An interconnect deployment saves money and space because fewer patch panels are needed, but a cross connect deployment makes it easier to implement changes in connectivity in a network.
A variety of specialized patch cords may be used in connection with the present invention, depending on the particular application. Patch cords may be considered as falling into two general embodiments: a “nine wire” patch cord style, which has one additional conductor in addition to the traditional four-pair Ethernet patch cord, and a “ten wire” patch cord style, which has two additional conductors. While the terms “nine wire” and “ten wire” will be used herein, it is to be understood that these terms are used to refer to patch cords having either one or two additional conductors used for patch cord management functions. For example, a “nine wire” patch cord could be replaced with a fiber optic patch cord having one conductor used for patch cord management functions, in addition to the optical fiber.
According to certain embodiments and applications of the present invention, different specific types of patch cord may be used. In interconnect deployments, nine-wire and ten-wire patch cords that integrate hardware for allowing detection of insertion or removal of their remote ends (the ends not attached to the patch panel) may be used. In cross-connect deployments, intelligent patch panels can be used in conjunction with a nine-wire patch cord style that does not necessarily need to incorporate hardware that allows insertion or removal detection at the remote end of the patch cord. This is because two intelligent patch panels can be used to communicate connectivity information to one another over ninth wires of patch cords.
Turning to
Ten-wire patch cords 18 connect patch ports 20 of the intelligent patch panels 10 to network hardware installed in the cabinets 12, including switches 22 and servers 24. For example, in
According to one embodiment, the patch cords 18 are provided with insertion detection switches at the plugs of the patch cords that are plugged into the network elements such as the switches and servers (i.e., the plugs on the ends of the patch cord that are not connected to the intelligent patch panels 10). According to another embodiment, insertion or removal detection is accomplished by a ground detection scheme as explained in U.S. Provisional Patent Application Ser. No. 61/113,868.
Environmental data collected by sensors can provide critical information to data center managers for decision-making related to physical server deployments. The environmental information can also provide useful criteria to virtualization software for its selection of the optimum hardware (including physical infrastructure and server hardware) resources to host virtual machines. Sensor data logs can also provide a record of evidence that compels hardware vendors to honor their warranty repair obligations. Software can turn data such as temperature and current data into easy-to-use and relevant information such as information about thermal capacity, power capacity, and grounding quality, for example.
Actuators 36 can also be connected to the sensing and control ports 30. Examples of actuators that can be used with the present invention include cabinet door locks for security and optical signal beacons (mounted, for example, atop each cabinet) to assist in locating targeted physical assets within large data centers.
Systems and methods of the present invention allow for physical location information regarding network assets connected to intelligent patch panels to be provided to a network management system or PIM software. In addition, the physical locations of network assets later connected to an intelligent patch panel (following initial installation of the intelligent patch panel) will be known because the physical locations of each intelligent patch panel in a network are known by software on the PIM server 15, and perhaps other network management software as may be used in specific network deployments.
The right server cabinet 12′ in
A method of associating physical location data and automated horizontal link detection with network assets will now be described. Returning to
Using a PC to access the intelligent patch panel's management port, a data center technician assigns a unique identifier into each intelligent patch panel's nonvolatile memory to represent:
(a) Identification labeling of the cabinet (cabinet number);
(b) Location on the physical floor plan of the data center;
(c) Cabinet type (switch or server cabinet); and
(d) Network elements associated with the intelligent patch panel.
If more than one intelligent patch panel resides in a given cabinet, they all receive the same cabinet number and type identifier.
Following the installation of switches 22 and the intelligent patch panel 10 in the first cabinet, the provisioning port 23 is used with the ten-wire patch cords 18 to enable the intelligent patch panel 10 to report to the PIM server 15 which switch ports 21 are connected to which panel ports 20. This can be accomplished using a patch cord installation procedure as described in U.S. Provisional Patent Application Ser. No. 61/113,868, with information about switch port connections being collected when the switch plug of a patch cord is plugged into a switch port and the panel plug of the patch cord is connected to the provisioning port of the intelligent patch panel.
Additional exemplary, useful information that can be collected by or provided to the PIM Software includes:
(a) switch MAC address;
(b) switch IP address;
(c) switch chassis id or serial number;
(d) switch port identification, MAC address, or IP address;
(e) assigned host name;
(f) 3D visualization information in real time or real time;
(g) uptime;
(h) model and manufacturer;
(i) service level agreement information;
(j) mean time to recovery (MTTR); and
(k) mean time between failures (MTBF).
Next, the process of provisioning the intelligent patch panel 12′ will be described. According to one embodiment of the present invention, a particular provisioning method should be used when installing intelligent patch panels and other network assets in a cabinet to enable physical location information to be collected and managed by a PIM server or other management system. These steps occur after installation of the main distribution area cabinets and switches, horizontal cabling, and server cabinets, along with their intelligent patch panels:
Through repetition of this method at all of the intelligent patch panel ports in all of the server cabinets in a network, the PIM software maps end-to-end connectivity of all of the copper horizontal cabling in the data center. The PIM software then knows: (1) the spatial location and logical port identification of each terminus of each horizontal cable; (2) the physical and logical location of switches and their cabinets; and (3) the physical and logical location of server cabinets and the associated intelligent patch panels. At this point in the process, the PIM software does not have information about specific server identifications or locations.
Next, the servers are patched in a method that enables the specific physical locations of servers to be known. These steps occur after the provisioning of the server cabinets in conjunction with steps (a) through (f) above. As discussed above, two different patch cord styles may be used in connection with provisioning the ports of the intelligent patch panel 10′.
PIM software utilizes SNMP (Simple Network Management Protocol) to enable messaging between network devices and a central management console or server. Management Information Blocks (MIBs) contain statistic counters, port status, and other information about these network devices. A management console issues GET and SET commands to operate on particular MIB variables for network equipment nodes. The various network device agents, such as those contained in distributed intelligent patch panels modules, can issue TRAP messages to the PIM server to report events such as patch disconnects and other alerts. Third-party SNMP-based network management systems, such as HP OpenView, may integrate or cooperate with Panduit PIM software if the extended MIB variable structures are shared.
PIM Software discovers all of the devices within the network. According to one embodiment, certain limitations exist with respect to the availability of switch information: the switches must have SNMP activated, and their address table information must generally be made available to the PIM software. With these permissions, the PIM software can discover and aggregate:
a) Switch MAC address;
b) Switch IP address;
c) Switch chassis id or serial number;
d) Switch port identification, MAC address, or IP address;
e) Assigned host name;
f) Model and manufacturer; and
g) The IP and MAC addresses of the active devices connected to each switch port.
Again, data center personnel assigned a unique identifier to the intelligent patch panel in the field to represent its cabinet. Since the intelligent patch panels 10 and 10′ (and therefore the PIM software) have memorized the intelligent patch panels' lists of connected switch ports, and since these switches have made their port-connection-to-server data available to the PIM software, then the PIM software can map and designate each of these connected switches and servers as physically resident within their respective cabinets. The PIM software can also map the horizontal cabling connectivity within the data center.
Knowing the physical locations of the intelligent patch panels of the present invention, it is possible for the PIM software to go beyond a typical topological map 54 of network assets, as shown in
The ability of a physical infrastructure management system as disclosed herein to automatically reconcile itself (i.e., to confirm that all connections have been implemented as intended and flag any improper implementations) enables automated decisions to be made, such as the virtual movement of an application from one server to another, without the need for a manual verification or reconciliation step.
In the above description, it is to be understood that references to “cabinets” refer to one embodiment of the present invention. It is also possible for the physical location information and other benefits of the present invention to be provided with reference to racks or rooms or other relevant physical locations (i.e., “containers”) that house intelligent patch panels.
This application is a continuation of U.S. patent application Ser. No. 13/666,430, filed Nov. 1, 2012, which will issue as U.S. Pat. No. 8,719,205 on May 6, 2014; which is a continuation of U.S. patent application Ser. No. 12/640,160, filed Dec. 17, 2009, which claims priority to U.S. Provisional Application No. 61/139,975, filed Dec. 22, 2008, the subject matter of which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
3052842 | Frohman et al. | Sep 1962 | A |
3431428 | Van Valer | Mar 1969 | A |
3573789 | Sharp et al. | Apr 1971 | A |
3573792 | Reed | Apr 1971 | A |
3914561 | Schardt et al. | Oct 1975 | A |
4018997 | Hoover et al. | Apr 1977 | A |
4072827 | Oman | Feb 1978 | A |
4096359 | Barsellotti | Jun 1978 | A |
4140885 | Verhagen | Feb 1979 | A |
4169220 | Fields | Sep 1979 | A |
4196316 | McEowen et al. | Apr 1980 | A |
4517619 | Uekubo | May 1985 | A |
4673246 | Schembri | Jun 1987 | A |
4773867 | Keller et al. | Sep 1988 | A |
4796294 | Nakagawara | Jan 1989 | A |
4869566 | Juso et al. | Sep 1989 | A |
4890102 | Oliver | Dec 1989 | A |
4901004 | King | Feb 1990 | A |
4937529 | O'Toole, III et al. | Jun 1990 | A |
4937835 | Omura | Jun 1990 | A |
5037167 | Beaty | Aug 1991 | A |
5081627 | Yu | Jan 1992 | A |
5107532 | Hansen et al. | Apr 1992 | A |
5111408 | Amjadi | May 1992 | A |
5145380 | Holcomb et al. | Sep 1992 | A |
5161988 | Krupka | Nov 1992 | A |
5170327 | Burroughs | Dec 1992 | A |
5204929 | Machall et al. | Apr 1993 | A |
5222164 | Bass, Sr. et al. | Jun 1993 | A |
5226120 | Brown et al. | Jul 1993 | A |
5233501 | Allen et al. | Aug 1993 | A |
5265187 | Morin et al. | Nov 1993 | A |
5270658 | Epstein | Dec 1993 | A |
5305405 | Emmons et al. | Apr 1994 | A |
5353367 | Czosnowski et al. | Oct 1994 | A |
5375028 | Fukunaga | Dec 1994 | A |
5394503 | Dietz, Jr. et al. | Feb 1995 | A |
5432847 | Hill et al. | Jul 1995 | A |
5459478 | Bolger et al. | Oct 1995 | A |
5463706 | Dumont et al. | Oct 1995 | A |
5483467 | Krupka et al. | Jan 1996 | A |
5487666 | DiGiovanni | Jan 1996 | A |
5521902 | Ferguson | May 1996 | A |
5532603 | Bottman | Jul 1996 | A |
5546282 | Hill et al. | Aug 1996 | A |
5550755 | Martin et al. | Aug 1996 | A |
5583874 | Smith et al. | Dec 1996 | A |
5666453 | Dannenmann | Sep 1997 | A |
5684796 | Abidi et al. | Nov 1997 | A |
5726972 | Ferguson | Mar 1998 | A |
5727055 | Ivie et al. | Mar 1998 | A |
5754112 | Novak | May 1998 | A |
5764043 | Czosnowski et al. | Jun 1998 | A |
5790041 | Lee | Aug 1998 | A |
5832071 | Voelker | Nov 1998 | A |
5847557 | Fincher et al. | Dec 1998 | A |
5854824 | Bengal et al. | Dec 1998 | A |
5870626 | Lebeau | Feb 1999 | A |
5876240 | Derstine et al. | Mar 1999 | A |
5878030 | Norris | Mar 1999 | A |
5892756 | Murphy | Apr 1999 | A |
5898837 | Guttman et al. | Apr 1999 | A |
5915993 | Belopolsky et al. | Jun 1999 | A |
5923663 | Bontemps et al. | Jul 1999 | A |
5944535 | Bullivant et al. | Aug 1999 | A |
6002331 | Laor | Dec 1999 | A |
6041352 | Burdick et al. | Mar 2000 | A |
6067014 | Wilson | May 2000 | A |
6078113 | True et al. | Jun 2000 | A |
6086415 | Sanchez et al. | Jul 2000 | A |
6094261 | Contarino, Jr. | Jul 2000 | A |
6168555 | Fetterleigh et al. | Jan 2001 | B1 |
6175865 | Dove et al. | Jan 2001 | B1 |
6222908 | Bartolutti et al. | Apr 2001 | B1 |
6229538 | McIntyre et al. | May 2001 | B1 |
6234830 | Ensz et al. | May 2001 | B1 |
6243510 | Rauch | Jun 2001 | B1 |
6285293 | German et al. | Sep 2001 | B1 |
6330307 | Bloch et al. | Dec 2001 | B1 |
6350148 | Bartolutti et al. | Feb 2002 | B1 |
6381283 | Bhardwaj et al. | Apr 2002 | B1 |
6421322 | Koziy et al. | Jul 2002 | B1 |
6424710 | Bartolutti et al. | Jul 2002 | B1 |
6434716 | Johnson et al. | Aug 2002 | B1 |
6437894 | Gilbert et al. | Aug 2002 | B1 |
6453014 | Jacobson et al. | Sep 2002 | B1 |
6456768 | Boncek et al. | Sep 2002 | B1 |
6499861 | German et al. | Dec 2002 | B1 |
6522737 | Bartolutti et al. | Feb 2003 | B1 |
6543941 | Lampert | Apr 2003 | B1 |
6561827 | Frostrom et al. | May 2003 | B2 |
6574586 | David et al. | Jun 2003 | B1 |
6577243 | Dannenmann et al. | Jun 2003 | B1 |
6588938 | Lampert et al. | Jul 2003 | B1 |
6601097 | Cheston et al. | Jul 2003 | B1 |
6626697 | Martin et al. | Sep 2003 | B1 |
6629269 | Kahkoska | Sep 2003 | B1 |
6684179 | David | Jan 2004 | B1 |
6688910 | Macauley | Feb 2004 | B1 |
6714698 | Pfeiffer et al. | Mar 2004 | B2 |
6725177 | David et al. | Apr 2004 | B2 |
6750643 | Hwang et al. | Jun 2004 | B2 |
6778911 | Opsal et al. | Aug 2004 | B2 |
6784802 | Stanescu | Aug 2004 | B1 |
6798944 | Pfeiffer et al. | Sep 2004 | B2 |
6802735 | Pepe et al. | Oct 2004 | B2 |
6823063 | Mendoza | Nov 2004 | B2 |
6857897 | Conn | Feb 2005 | B2 |
6871156 | Wallace et al. | Mar 2005 | B2 |
6894480 | Back | May 2005 | B2 |
6898368 | Colombo et al. | May 2005 | B2 |
6905363 | Musolf et al. | Jun 2005 | B2 |
6906505 | Brunet et al. | Jun 2005 | B2 |
6975242 | Dannenmann et al. | Dec 2005 | B2 |
6992491 | Lo et al. | Jan 2006 | B1 |
7005861 | Lo et al. | Feb 2006 | B1 |
7027704 | Frohlich et al. | Apr 2006 | B2 |
7028087 | Caveney | Apr 2006 | B2 |
7029137 | Lionetti et al. | Apr 2006 | B2 |
7038135 | Chan et al. | May 2006 | B1 |
7049937 | Zweig et al. | May 2006 | B1 |
7068043 | Lo et al. | Jun 2006 | B1 |
7068044 | Lo et al. | Jun 2006 | B1 |
7160143 | David et al. | Jan 2007 | B2 |
7207846 | Caveney et al. | Apr 2007 | B2 |
7234944 | Nordin et al. | Jun 2007 | B2 |
20020069277 | Caveney | Jun 2002 | A1 |
20020071394 | Koziy et al. | Jun 2002 | A1 |
20020090858 | Caveney | Jul 2002 | A1 |
20020116485 | Black et al. | Aug 2002 | A1 |
20030046339 | Ip | Mar 2003 | A1 |
20030061393 | Steegmans et al. | Mar 2003 | A1 |
20030065766 | Parry | Apr 2003 | A1 |
20030073343 | Belesimo | Apr 2003 | A1 |
20030152087 | Shahoumian et al. | Aug 2003 | A1 |
20040044599 | Kepner et al. | Mar 2004 | A1 |
20040052471 | Colombo et al. | Mar 2004 | A1 |
20040065470 | Goodison et al. | Apr 2004 | A1 |
20040073597 | Caveney et al. | Apr 2004 | A1 |
20040077220 | Musolf et al. | Apr 2004 | A1 |
20040219827 | David et al. | Nov 2004 | A1 |
20050052174 | Angelo et al. | Mar 2005 | A1 |
20050111491 | Caveney | May 2005 | A1 |
20050136729 | Redfield et al. | Jun 2005 | A1 |
20050141431 | Caveney et al. | Jun 2005 | A1 |
20050186819 | Velleca et al. | Aug 2005 | A1 |
20050195584 | AbuGhazaleh et al. | Sep 2005 | A1 |
20050224585 | Durrant et al. | Oct 2005 | A1 |
20050231325 | Durrant et al. | Oct 2005 | A1 |
20050239339 | Pepe | Oct 2005 | A1 |
20050245127 | Nordin et al. | Nov 2005 | A1 |
20060047800 | Caveney et al. | Mar 2006 | A1 |
20060057876 | Dannenmann et al. | Mar 2006 | A1 |
20060282529 | Nordin et al. | Dec 2006 | A1 |
20070032124 | Nordin et al. | Feb 2007 | A1 |
20070132503 | Nordin | Jun 2007 | A1 |
20080265722 | Saliaris | Oct 2008 | A1 |
20080266063 | James | Oct 2008 | A1 |
Number | Date | Country |
---|---|---|
0297079 | Mar 1992 | EP |
0575100 | Dec 1993 | EP |
0745229 | Mar 2003 | EP |
2680067 | Feb 1993 | FR |
2236398 | Apr 1991 | GB |
2347751 | Sep 2000 | GB |
2347752 | Sep 2000 | GB |
676878 | Mar 1994 | JP |
2004349184 | Dec 2004 | JP |
9926426 | May 1999 | WO |
0060475 | Oct 2000 | WO |
0155854 | Aug 2001 | WO |
2004044599 | Mar 2004 | WO |
2005072156 | Aug 2005 | WO |
2006052686 | May 2006 | WO |
Entry |
---|
“Finding the Missing Link,” Cabling Installation & Maintenance, Jun./Jul. 2002. |
“IntelliMAC—The New Intelligent Cable Management Solution by ITRACS & NORDX/CDT,” Press Release 2003. |
“RiT Technologies Ltd. SMART Cabling System,” RiT Technologies Ltd., 2004. |
“Ortronics Launches iTRACS—Ready Structured Cabling Solutions,” News Release Mar. 7, 2003. |
“The SYSTIMAX iPatch System—Intelligent yet simple patching . . . ”, CommScope, Inc., 2004. |
“White Paper—intelligent Patching.” David Wilson, Nov. 2002. |
“PatchView for the Enterprise (PV4E) technical backround/Networks for Business,” Jun. 24-26, 2003. |
“RiT Technologies Ltd. Go Patch-less,” May 2000 Edition of Cabling Systems. |
“Intelligent Cable Management Systems—Hot Topics”, Trescray. |
“Brand-Rex Network solutions Access racks Cat 5E6 cabling UK”. |
“Molex Premise Networks/Western Europe—Real Time Patching System” Molex Prem. Networks, 2001. |
“Product of the Week—Molex's Real Time Patching System”. |
“EC&M Taking Note of Patch Panel Technology,” Mark McElroy, Jun. 1, 1998. |
“Intellegent Patching SMART Patch for the Enterprise (SP4E)”. |
Number | Date | Country | |
---|---|---|---|
20140258200 A1 | Sep 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13666430 | Nov 2012 | US |
Child | 14269222 | US | |
Parent | 12640160 | Dec 2009 | US |
Child | 13666430 | US |