US20190391946A1 - Das storage cable identification - Google Patents
Das storage cable identification Download PDFInfo
- Publication number
- US20190391946A1 US20190391946A1 US16/013,526 US201816013526A US2019391946A1 US 20190391946 A1 US20190391946 A1 US 20190391946A1 US 201816013526 A US201816013526 A US 201816013526A US 2019391946 A1 US2019391946 A1 US 2019391946A1
- Authority
- US
- United States
- Prior art keywords
- cable
- storage
- storage device
- network system
- server
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4063—Device-to-bus coupling
- G06F13/4068—Electrical coupling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q1/00—Details of selecting apparatus or arrangements
- H04Q1/02—Constructional details
- H04Q1/13—Patch panels for monitoring, interconnecting or testing circuits, e.g. patch bay, patch field or jack field; Patching modules
- H04Q1/135—Patch panels for monitoring, interconnecting or testing circuits, e.g. patch bay, patch field or jack field; Patching modules characterized by patch cord details
- H04Q1/136—Patch panels for monitoring, interconnecting or testing circuits, e.g. patch bay, patch field or jack field; Patching modules characterized by patch cord details having patch field management or physical layer management arrangements
-
- G—PHYSICS
- G02—OPTICS
- G02B—OPTICAL ELEMENTS, SYSTEMS OR APPARATUS
- G02B6/00—Light guides; Structural details of arrangements comprising light guides and other optical elements, e.g. couplings
- G02B6/24—Coupling light guides
- G02B6/36—Mechanical coupling means
- G02B6/38—Mechanical coupling means having fibre to fibre mating means
- G02B6/3807—Dismountable connectors, i.e. comprising plugs
- G02B6/3895—Dismountable connectors, i.e. comprising plugs identification of connection, e.g. right plug to the right socket or full engagement of the mating parts
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3041—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is an input/output interface
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/325—Display of status information by lamps or LED's
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1668—Details of memory controller
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
-
- 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
-
- 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/24—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using dedicated network management hardware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F2213/0016—Inter-integrated circuit (I2C)
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Definitions
- This application relates to a server device and method to detect proper cable assembly to improve assembly and problem diagnosis.
- computing equipment are connected by cables via connectors.
- cables are connected to a board having a large number of pins.
- One example of such a connection is between a computer peripheral and a main or host computer. It is often a challenge to ensure the connector leading from a peripheral component is connected properly to the matching connector, or to the pins on a board.
- Manufacturers also typically use colored coating on a portion of the cable insulation leading up to a connector to prevent incorrect connection. While the color identification can aid the user in correctly identifying a particular pin on the connector, the part to which the connector will be attached, such as a motherboard, may not have color identification to match the connector. As with other conventional methods, this approach only helps the user prior to establishing the connection but does not offer assistance in correcting the connection.
- a network system for identifying a cable connection includes a management server, a server device, and a storage device.
- the management server includes system-management software.
- the server device is connected to the management server.
- the server device includes a BMC configured to communicate with the system-management software of the management server.
- the storage device includes at least one cable port configured to receive a storage cable that connects the storage device to the server device.
- the cable port includes a non-volatile memory, an indicator light, and an Inter-IC (I 2 C) bus.
- the server device is communicatively coupled to the management server via a local area network.
- the storage device can be a DAS storage.
- the storage cable can include a MiniSAS HD cable.
- the non-volatile memory can be an Electrically Erasable Programmable Read-Only Memory (EEPROM).
- the indicator light can include a light-emitting diode (LED).
- the storage device can include a JBOD (“just a bunch of disks”), a JBOF (“just a bunch of flash”), a JBOG (“Just a Box of GPUs”), or any combination thereof as a RAID array.
- the system-management software can be configured to send an IPMI OEM command to the BMC of the server device.
- the IPMI OEM command can include a CABLE ID of the storage cable.
- the storage cable can include a MiniSAS HD cable.
- the MiniSAS HD cable can connect a cable port of the at least one storage device to an Ethernet network interface of the server device.
- a method for authenticating a cable connection also includes receiving, at a BMC on a server device, an IPMI OEM command including a CABLE ID.
- the method also includes receiving, from the BMC, a value for a storage device non-volatile memory reserve bit to coincide with the received CABLE ID.
- the method also includes detecting a CABLE ID from a storage cable inserted into the storage device.
- the method includes determining whether the CABLE ID from the storage cable matches the received CABLE ID.
- the method also includes actuating an indicator light at the storage device upon determining that the CABLE ID from the storage cable matches the received CABLE ID.
- the method includes disabling the indicator light at the storage device upon determining that the CABLE ID from the storage cable does not match the received CABLE ID.
- FIG. 1A illustrates a diagram of an example network system, in accordance with an embodiment of the disclosure
- FIG. 1B illustrates a Cable Port of the network system of FIG. 1A , in accordance with an embodiment of the disclosure.
- FIG. 2 depicts a flow chart describing the process for authenticating a CABLE ID using the network system 100 of FIG. 1 , in accordance with an embodiment of the disclosure.
- FIG. 3 depicts a flow chart describing the process for disassembling a cable connection of a storage cable from a server device to a storage device, in accordance with an embodiment of the disclosure.
- a network system in accordance with the present disclosure can include a data center, a server device, and a storage device.
- the data center can include a system-management software.
- the server device can be connected to the data center.
- the server device can include a BMC configured to communicate with the system-management software of the data center.
- the storage device can include at least one cable port configured to receive a storage cable that connects the storage device to the server device.
- the cable port can include a non-volatile memory, an indicator light, and a I 2 C bus.
- FIG. 1A illustrates a simplified block diagram of an example network system 100 in accordance with an embodiment of the disclosure.
- the network system 100 includes a management server 130 , a server device 160 , and a direct-attached storage (hereinafter “DAS Storage”) 190 .
- DAS Storage direct-attached storage
- the network system 100 can be configured as an Intelligent Platform Management Bus (IPMB) architecture.
- IPMB Intelligent Platform Management Bus
- the DAS storage 190 can be configured as a JBOD (“just a bunch of disks”), or a collection of hard disks that have not been configured to act as a redundant array of independent disks (RAID) array.
- the DAS storage 190 can be configured as a JBOF (“just a bunch of flash”), or a collection of solid state drives that have not been configured to act as a redundant array of independent disks (RAID) array.
- the DAS storage 190 can be configured as a JBOG (“Just a Box of GPUs”), or a collection of graphic processing units. It should be understood by one of ordinary skill in the art that the DAS storage 190 can include any combination thereof as a RAID array.
- the management server 130 can include an Ethernet network interface 131 .
- the management server 130 can also include a system-management software 135 .
- the Ethernet network interface 131 can be configured to connect to a Local Area Network (hereinafter “LAN”) 110 .
- LAN Local Area Network
- other networks can be implemented.
- WAN wide-area network
- the server device 160 is configured to connect to the LAN 110 .
- the server device 160 can be configured to communicate to the system-management tool or software 135 at the management server 130 .
- the management server 130 can be configured to send an Intelligent Platform Management Interface (IPMI) Original Equipment Manufacturer (OEM) command (herein after “IPMI OEM command”) 120 to the server device 160 via the LAN 110 . This is discussed in greater detail below with respect to FIG. 2 .
- IPMI Intelligent Platform Management Interface
- OEM command Intelligent Platform Management Interface
- the server device 160 can include a baseboard management controller (hereinafter “BMC”) 165 .
- the BMC 165 can be configured to provide the intelligence in the IPMI architecture (network system 100 ).
- the BMC 165 can be a specialized microcontroller embedded on the motherboard (not shown) of the server device 160 .
- the BMC 165 can be configured to manage the interface between the system-management software 135 and the platform hardware of the server device 160 .
- the BMC 165 can receive reports from sensors within the server device 160 on various parameters such as temperature, cooling fan speeds, power status, operating system (OS) status, etc.
- the BMC 165 can monitor the sensors and can send alerts to the system-management software 135 via the LAN 110 if any of the parameters exceed pre-set limits, indicating a potential failure of the system.
- An administrator utilizing the system-management software 135 can also remotely communicate with the BMC 165 to take corrective actions.
- the server device 160 can also include an Ethernet network interface 161 .
- the Ethernet network interface 161 can include ports configured to receive a PCI Express (PCIe) card (not shown), or other types of is a high-speed serial computer expansion bus standard.
- PCIe PCI Express
- the Ethernet network interface 161 can also include MiniSAS HD cable ports (not shown).
- the Mini-SAS HD cable ports can provide channel bandwidth of 6 Gb/s, 12 Gb/s, and 14 Gb/s.
- the DAS storage 190 can include cable ports 181 N.
- FIG. 1B illustrates a plurality of cable ports 181 N of the example network system 100 in accordance with an embodiment of the disclosure.
- the cable ports 181 N can also be configured as MiniSAS HD cable ports.
- the cable ports 181 N can be configured with indicator lights 180 N.
- the indicator lights 180 N can be light-emitting diodes (LED). Other types of indicator lights can be implemented herein.
- the cable ports 181 N can also be configured with a non-volatile memory 191 N.
- the non-volatile memory 191 N can be configured as Electrically Erasable Programmable Read-Only Memory (EEPROM).
- EEPROM Electrically Erasable Programmable Read-Only Memory
- non-volatile memory 191 N can include any non-volatile memory used in computers and other electronic devices to store relatively small amounts of data but allowing individual bytes to be erased and reprogrammed.
- the cable port 181 N can also be configured with an Inter-IC (I 2 C) bus 195 N.
- the I 2 C bus 195 N is a bi-directional two-wire serial bus that provides a communication link between the non-volatile memory 191 N and the BMC 165 of the server device 160 .
- the I 2 C bus 195 N includes a bidirectional data (SDA) line and a unidirectional serial clock (SCL) line (not shown).
- SDA bidirectional data
- SCL unidirectional serial clock
- the server device 160 can be connected to the DAS storage 190 by a storage cable 170 .
- the storage cable 170 can be configured as a MiniSAS HD cable.
- the storage cable 170 can connect a cable port 181 N of the DAS storage 190 to the Ethernet network interface 161 of the server device 160 .
- the server device 160 is also configured to connect to the LAN 110 to communicate to the system-management software 135 at the management server 130 .
- Physical interfaces to the BMC 165 can include an Intelligent Platform Management Bus (IPMB), that enables the BMC 165 to accept the IPMI OEM command 120 from the system-management software 135 .
- IPMB Intelligent Platform Management Bus
- FIG. 2 depicts a flow chart describing the process 200 for authenticating a CABLE ID using the network system 100 of FIG. 1 .
- the process 200 starts with communication between the system-management software 135 and the BMC 165 in step 201 .
- the system-management software 135 can be configured to send an IPMI OEM command 120 to the BMC 165 of the server device 160 .
- the IPMI OEM command 120 can be received by the BMC 165 via the Ethernet network interface 161 .
- the IPMI OEM command 120 can include a CABLE ID.
- the process 200 Upon receipt of the CABLE ID, the process 200 advances to step 202 .
- the BMC 165 can communicate with the non-volatile memory 191 N of the DAS storage 190 via the I 2 C bus 195 N.
- the BMC 165 can set a value for the DAS storage EEPROM reserve bit to coincide with the received CABLE ID.
- the bit value can be set to “1” for enable, or “0” for disable, when authenticating the CABLE ID.
- the non-volatile memory 191 N can detect the CABLE ID of the storage cable 170 .
- FIG. 3 depicts a flow chart describing the process 300 for disassembling a cable connection of a storage cable from a server device to a storage device as exemplified in the network system 100 of FIG. 1 .
- the process starts with communication between the system-management software 135 of the management server 130 and the BMC 165 of the server device 160 in step 301 .
- the system-management software 135 sends a command to the BMC 165 to actuate an indicator light 180 N associated with a specific storage cable 170 .
- an administrator operating at the management server 130 can determine that storage cable 170 should be disconnected to the DAS storage 190 to perform maintenance.
- the administrator can implement the system-management software 135 to identify the appropriate storage cable 170 via the corresponding indicator light 180 N.
- the indicator light 180 N can be actuated to illuminate.
- the illumination of the indicator light 180 N can provide a visual indicator to the administrator physically removing the corresponding storage cable 170 .
- the process 300 advances to 302 , where a determination is made as to whether the indicator light 180 N is illuminated. For example, an administrator can service the DAS storage 190 and determine whether the indicator light 180 N is illuminated. Upon determining that the indicator light 180 N is not illuminated, the process advances to 303 . At step 303 , the assessment at step 302 is repeated to determine which indicator light 180 N is illuminated. Conversely, where it is determined that the indicator light is illuminated, the process 300 advances to 304 . At step 304 , the storage cable 170 is removed from the cable port 181 N of the DAS storage 190 .
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Optics & Photonics (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
- This application relates to a server device and method to detect proper cable assembly to improve assembly and problem diagnosis.
- In the field of information systems, connecting equipment together is often a daunting task. In some instances, computing equipment are connected by cables via connectors. In other instances, cables are connected to a board having a large number of pins. One example of such a connection is between a computer peripheral and a main or host computer. It is often a challenge to ensure the connector leading from a peripheral component is connected properly to the matching connector, or to the pins on a board.
- When a system is powered up with an improperly connected component, the main system, such as a personal computer, will not work. Administrators or system owners may resort to dismantling their equipment to diagnose the problem, or call a customer support line to seek resolution of the problem—both of which are time-consuming approaches. Repeated unsuccessful attempts to connect cables can also result in damage to the computer or to a peripheral component, in the form of broken connection pins, improper connections of power supplies to ground, and improper connections of high voltage levels to delicate circuits.
- To alleviate such issues, manufacturers typically provide diagrams illustrating the location for each connector. These diagrams can be quite complex, depending on the size of the system. Also, they do not address the proper orientation of a cable into a connector. Furthermore, this approach can only provide guidance to the user prior to connection. Once a faulty connection is made, the manufacturer provided diagram offers no assistance in rectifying the connection.
- Manufacturers also typically use colored coating on a portion of the cable insulation leading up to a connector to prevent incorrect connection. While the color identification can aid the user in correctly identifying a particular pin on the connector, the part to which the connector will be attached, such as a motherboard, may not have color identification to match the connector. As with other conventional methods, this approach only helps the user prior to establishing the connection but does not offer assistance in correcting the connection.
- Therefore, there is a need for a system and method for facilitating proper cable connections. Specifically, there is a need for a system and method for identifying proper cable connection, and to provide information to correct an incorrect cable connection.
- The following is a simplified summary of one or more embodiments in order to provide a basic understanding of present technology. This summary is not an extensive overview of all contemplated embodiments of the present technology. It is intended neither to identify key or critical elements of all examples, nor to delineate the scope of any or all aspects of the present technology. Its sole purpose is to present some concepts of one or more examples in a simplified form as a prelude to the more detailed description that is presented later.
- A network system for identifying a cable connection is provided. The network system includes a management server, a server device, and a storage device. The management server includes system-management software. The server device is connected to the management server. The server device includes a BMC configured to communicate with the system-management software of the management server. The storage device includes at least one cable port configured to receive a storage cable that connects the storage device to the server device. The cable port includes a non-volatile memory, an indicator light, and an Inter-IC (I2C) bus.
- In some embodiments, the server device is communicatively coupled to the management server via a local area network. In some embodiments, the storage device can be a DAS storage. In some embodiments, the storage cable can include a MiniSAS HD cable. In some embodiments, the non-volatile memory can be an Electrically Erasable Programmable Read-Only Memory (EEPROM). In some embodiments, the indicator light can include a light-emitting diode (LED).
- In some embodiments, the storage device can include a JBOD (“just a bunch of disks”), a JBOF (“just a bunch of flash”), a JBOG (“Just a Box of GPUs”), or any combination thereof as a RAID array. In some embodiments, the system-management software can be configured to send an IPMI OEM command to the BMC of the server device. The IPMI OEM command can include a CABLE ID of the storage cable. In some embodiments, the storage cable can include a MiniSAS HD cable. In some embodiments, the MiniSAS HD cable can connect a cable port of the at least one storage device to an Ethernet network interface of the server device.
- A method for authenticating a cable connection also is provided. The method includes receiving, at a BMC on a server device, an IPMI OEM command including a CABLE ID. The method also includes receiving, from the BMC, a value for a storage device non-volatile memory reserve bit to coincide with the received CABLE ID. The method also includes detecting a CABLE ID from a storage cable inserted into the storage device. Moreover, the method includes determining whether the CABLE ID from the storage cable matches the received CABLE ID. The method also includes actuating an indicator light at the storage device upon determining that the CABLE ID from the storage cable matches the received CABLE ID. Alternatively, the method includes disabling the indicator light at the storage device upon determining that the CABLE ID from the storage cable does not match the received CABLE ID.
- In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles described above will be rendered by reference to specific examples illustrated in the appended drawings. These drawings depict only example aspects of the disclosure, and are therefore not to be considered as limiting of its scope. These principles are described and explained with additional specificity and detail through the use of the following drawings.
-
FIG. 1A illustrates a diagram of an example network system, in accordance with an embodiment of the disclosure; -
FIG. 1B illustrates a Cable Port of the network system ofFIG. 1A , in accordance with an embodiment of the disclosure. -
FIG. 2 depicts a flow chart describing the process for authenticating a CABLE ID using thenetwork system 100 ofFIG. 1 , in accordance with an embodiment of the disclosure; and -
FIG. 3 depicts a flow chart describing the process for disassembling a cable connection of a storage cable from a server device to a storage device, in accordance with an embodiment of the disclosure. - The present invention is described with reference to the attached figures, where like reference numerals are used throughout the figures to designate similar or equivalent elements. The figures are not drawn to scale and are provided merely to illustrate the instant invention. Several aspects of the invention are described below with reference to example applications for illustration. It should be understood that numerous specific details, relationships, and methods are set forth to provide a full understanding of the invention. One having ordinary skill in the relevant art, however, will readily recognize that the invention can be practiced without one or more of the specific details, or with other methods. In other instances, well-known structures or operations are not shown in detail to avoid obscuring the invention. The present invention is not limited by the illustrated ordering of acts or events, as some acts may occur in different orders and/or concurrently with other acts or events. Furthermore, not all illustrated acts or events are required to implement a methodology in accordance with the present invention.
- A network system in accordance with the present disclosure can include a data center, a server device, and a storage device. The data center can include a system-management software. The server device can be connected to the data center. The server device can include a BMC configured to communicate with the system-management software of the data center. The storage device can include at least one cable port configured to receive a storage cable that connects the storage device to the server device. The cable port can include a non-volatile memory, an indicator light, and a I2C bus.
-
FIG. 1A illustrates a simplified block diagram of anexample network system 100 in accordance with an embodiment of the disclosure. Thenetwork system 100 includes amanagement server 130, aserver device 160, and a direct-attached storage (hereinafter “DAS Storage”) 190. For the purposes of this example, thenetwork system 100 can be configured as an Intelligent Platform Management Bus (IPMB) architecture. - The
DAS storage 190 can be configured as a JBOD (“just a bunch of disks”), or a collection of hard disks that have not been configured to act as a redundant array of independent disks (RAID) array. In other embodiments, theDAS storage 190 can be configured as a JBOF (“just a bunch of flash”), or a collection of solid state drives that have not been configured to act as a redundant array of independent disks (RAID) array. In alternative embodiments, theDAS storage 190 can be configured as a JBOG (“Just a Box of GPUs”), or a collection of graphic processing units. It should be understood by one of ordinary skill in the art that theDAS storage 190 can include any combination thereof as a RAID array. - The
management server 130 can include anEthernet network interface 131. Themanagement server 130 can also include a system-management software 135. TheEthernet network interface 131 can be configured to connect to a Local Area Network (hereinafter “LAN”) 110. In other embodiments, other networks can be implemented. For example, in some embodiments, a wide-area network (WAN) can be implemented. Theserver device 160 is configured to connect to theLAN 110. Theserver device 160 can be configured to communicate to the system-management tool orsoftware 135 at themanagement server 130. Themanagement server 130 can be configured to send an Intelligent Platform Management Interface (IPMI) Original Equipment Manufacturer (OEM) command (herein after “IPMI OEM command”) 120 to theserver device 160 via theLAN 110. This is discussed in greater detail below with respect toFIG. 2 . - The
server device 160 can include a baseboard management controller (hereinafter “BMC”) 165. TheBMC 165 can be configured to provide the intelligence in the IPMI architecture (network system 100). TheBMC 165 can be a specialized microcontroller embedded on the motherboard (not shown) of theserver device 160. TheBMC 165 can be configured to manage the interface between the system-management software 135 and the platform hardware of theserver device 160. - For example, the
BMC 165 can receive reports from sensors within theserver device 160 on various parameters such as temperature, cooling fan speeds, power status, operating system (OS) status, etc. TheBMC 165 can monitor the sensors and can send alerts to the system-management software 135 via theLAN 110 if any of the parameters exceed pre-set limits, indicating a potential failure of the system. An administrator utilizing the system-management software 135 can also remotely communicate with theBMC 165 to take corrective actions. - The
server device 160 can also include anEthernet network interface 161. TheEthernet network interface 161 can include ports configured to receive a PCI Express (PCIe) card (not shown), or other types of is a high-speed serial computer expansion bus standard. TheEthernet network interface 161 can also include MiniSAS HD cable ports (not shown). The Mini-SAS HD cable ports can provide channel bandwidth of 6 Gb/s, 12 Gb/s, and 14 Gb/s. TheDAS storage 190 can includecable ports 181N. -
FIG. 1B illustrates a plurality ofcable ports 181N of theexample network system 100 in accordance with an embodiment of the disclosure. Thecable ports 181N can also be configured as MiniSAS HD cable ports. Thecable ports 181N can be configured withindicator lights 180N. The indicator lights 180N can be light-emitting diodes (LED). Other types of indicator lights can be implemented herein. Thecable ports 181N can also be configured with anon-volatile memory 191N. Thenon-volatile memory 191N can be configured as Electrically Erasable Programmable Read-Only Memory (EEPROM). It should be understood by one of ordinary skill in the art that thenon-volatile memory 191N can include any non-volatile memory used in computers and other electronic devices to store relatively small amounts of data but allowing individual bytes to be erased and reprogrammed. Thecable port 181N can also be configured with an Inter-IC (I2C)bus 195N. - The I2C bus 195N is a bi-directional two-wire serial bus that provides a communication link between the
non-volatile memory 191N and theBMC 165 of theserver device 160. Specifically, the I2C bus 195N includes a bidirectional data (SDA) line and a unidirectional serial clock (SCL) line (not shown). This configuration allows for an open-drain, multi-drop bus, meaning that multiple devices can be hooked to the bus and communicate with one another. The bus master transmits this address in the first byte of a message to identify the recipient of the message. - Referring back to
FIG. 1 , theserver device 160 can be connected to theDAS storage 190 by astorage cable 170. Thestorage cable 170 can be configured as a MiniSAS HD cable. Thestorage cable 170 can connect acable port 181N of theDAS storage 190 to theEthernet network interface 161 of theserver device 160. Theserver device 160 is also configured to connect to theLAN 110 to communicate to the system-management software 135 at themanagement server 130. Physical interfaces to theBMC 165 can include an Intelligent Platform Management Bus (IPMB), that enables theBMC 165 to accept theIPMI OEM command 120 from the system-management software 135. -
FIG. 2 depicts a flow chart describing theprocess 200 for authenticating a CABLE ID using thenetwork system 100 ofFIG. 1 . As seen inFIG. 2 , theprocess 200 starts with communication between the system-management software 135 and theBMC 165 instep 201. The system-management software 135 can be configured to send anIPMI OEM command 120 to theBMC 165 of theserver device 160. TheIPMI OEM command 120 can be received by theBMC 165 via theEthernet network interface 161. TheIPMI OEM command 120 can include a CABLE ID. - Upon receipt of the CABLE ID, the
process 200 advances to step 202. Atstep 202, theBMC 165 can communicate with thenon-volatile memory 191N of theDAS storage 190 via the I2C bus 195N. For example, theBMC 165 can set a value for the DAS storage EEPROM reserve bit to coincide with the received CABLE ID. In some embodiments, the bit value can be set to “1” for enable, or “0” for disable, when authenticating the CABLE ID. Atstep 203, when thestorage cable 170 is connected to theDAS storage 190, thenon-volatile memory 191N can detect the CABLE ID of thestorage cable 170. Atstep 204, a determination is made as to whether the CABLE ID of thestorage cable 170 matches the received CABLE ID. If the CABLE ID of thestorage cable 170 matches the received CABLE ID, theprocess 200 advances fromstep 204 to step 205 where theDAS storage 190 actuates the indicator lights 180N to indicate the cable is correct. Conversely, if the CABLE ID of thestorage cable 170 does not match the received CABLE ID, theprocess 200 advances fromstep 204 to step 206 where theDAS storage 190 can disable the indicator lights 180N to indicate the cable is incorrect. -
FIG. 3 depicts a flow chart describing theprocess 300 for disassembling a cable connection of a storage cable from a server device to a storage device as exemplified in thenetwork system 100 ofFIG. 1 . As can be seen inFIG. 3 , the process starts with communication between the system-management software 135 of themanagement server 130 and theBMC 165 of theserver device 160 instep 301. The system-management software 135 sends a command to theBMC 165 to actuate an indicator light 180N associated with aspecific storage cable 170. For example, an administrator operating at themanagement server 130 can determine thatstorage cable 170 should be disconnected to theDAS storage 190 to perform maintenance. The administrator can implement the system-management software 135 to identify theappropriate storage cable 170 via the corresponding indicator light 180N. Theindicator light 180N can be actuated to illuminate. The illumination of theindicator light 180N can provide a visual indicator to the administrator physically removing the correspondingstorage cable 170. - The
process 300 advances to 302, where a determination is made as to whether the indicator light 180N is illuminated. For example, an administrator can service theDAS storage 190 and determine whether the indicator light 180N is illuminated. Upon determining that the indicator light 180N is not illuminated, the process advances to 303. Atstep 303, the assessment atstep 302 is repeated to determine whichindicator light 180N is illuminated. Conversely, where it is determined that the indicator light is illuminated, theprocess 300 advances to 304. Atstep 304, thestorage cable 170 is removed from thecable port 181N of theDAS storage 190. - The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (15)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/013,526 US10515042B1 (en) | 2018-06-20 | 2018-06-20 | DAS storage cable identification |
TW107128853A TWI677250B (en) | 2018-06-20 | 2018-08-17 | Network system and authenticating method |
CN201811010247.6A CN110620677A (en) | 2018-06-20 | 2018-08-31 | Network system and authentication method |
EP18192949.8A EP3585062B1 (en) | 2018-06-20 | 2018-09-06 | Network system for identifying cable connection and method for authenticating cable id |
JP2018167147A JP2019220128A (en) | 2018-06-20 | 2018-09-06 | Network system for identifying cable connection and method of authenticating cable id |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/013,526 US10515042B1 (en) | 2018-06-20 | 2018-06-20 | DAS storage cable identification |
Publications (2)
Publication Number | Publication Date |
---|---|
US10515042B1 US10515042B1 (en) | 2019-12-24 |
US20190391946A1 true US20190391946A1 (en) | 2019-12-26 |
Family
ID=63524152
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/013,526 Active US10515042B1 (en) | 2018-06-20 | 2018-06-20 | DAS storage cable identification |
Country Status (5)
Country | Link |
---|---|
US (1) | US10515042B1 (en) |
EP (1) | EP3585062B1 (en) |
JP (1) | JP2019220128A (en) |
CN (1) | CN110620677A (en) |
TW (1) | TWI677250B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210182441A1 (en) * | 2019-12-12 | 2021-06-17 | Mellanox Technologies Tlv Ltd. | Cable Security |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021202587A1 (en) * | 2020-03-31 | 2021-10-07 | Commscope Technologies Llc | Bladed panel system with port occupancy monitoring |
US11582297B1 (en) | 2022-01-20 | 2023-02-14 | Nvidia Corporation | Mechanism to identify link down reasons |
US11729063B1 (en) * | 2022-01-20 | 2023-08-15 | Nvidia Corporation | Visually guided topology wiring |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20060130517A (en) | 2005-06-14 | 2006-12-19 | 팬듀트 코포레이션 | Method and apparatus for monitoring physical network topology information |
US7561060B2 (en) * | 2006-11-16 | 2009-07-14 | International Business Machines Corporation | Electroluminescent data cable identification and computer system diagnostics |
US8019940B2 (en) | 2006-12-06 | 2011-09-13 | Fusion-Io, Inc. | Apparatus, system, and method for a front-end, distributed raid |
US8994547B2 (en) | 2009-08-21 | 2015-03-31 | Commscope, Inc. Of North Carolina | Systems for automatically tracking patching connections to network devices using a separate control channel and related patching equipment and methods |
JP5282063B2 (en) * | 2010-03-26 | 2013-09-04 | 株式会社野村総合研究所 | Network route display method, cable removal method, network route display system |
US8996778B2 (en) | 2012-12-13 | 2015-03-31 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Cable adapter correlation in a cluster |
CN103473018B (en) * | 2013-09-10 | 2016-09-14 | 华为技术有限公司 | hard disk and management method |
CN106662713B (en) * | 2013-09-24 | 2018-10-02 | 康普技术有限责任公司 | Connection with management and control is supported and the pluggable active light module of emulated memory table |
US9709757B2 (en) | 2014-10-17 | 2017-07-18 | Commscope Technologies Llc | Systems and methods for port mapping |
CN204539135U (en) * | 2015-04-28 | 2015-08-05 | 国家电网公司 | A kind of communications patching recognition device |
-
2018
- 2018-06-20 US US16/013,526 patent/US10515042B1/en active Active
- 2018-08-17 TW TW107128853A patent/TWI677250B/en active
- 2018-08-31 CN CN201811010247.6A patent/CN110620677A/en active Pending
- 2018-09-06 JP JP2018167147A patent/JP2019220128A/en active Pending
- 2018-09-06 EP EP18192949.8A patent/EP3585062B1/en active Active
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210182441A1 (en) * | 2019-12-12 | 2021-06-17 | Mellanox Technologies Tlv Ltd. | Cable Security |
US11934568B2 (en) * | 2019-12-12 | 2024-03-19 | Mellanox Technologies, Ltd. | Cable security |
Also Published As
Publication number | Publication date |
---|---|
TWI677250B (en) | 2019-11-11 |
EP3585062A1 (en) | 2019-12-25 |
EP3585062B1 (en) | 2020-12-16 |
JP2019220128A (en) | 2019-12-26 |
US10515042B1 (en) | 2019-12-24 |
TW202002684A (en) | 2020-01-01 |
CN110620677A (en) | 2019-12-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10515042B1 (en) | DAS storage cable identification | |
US8640118B2 (en) | Managing firmware on a system board | |
US20180074993A1 (en) | Implementing sideband control structure for pcie cable cards and io expansion enclosures | |
US9697167B2 (en) | Implementing health check for optical cable attached PCIE enclosure | |
US9697155B2 (en) | Detecting and configuring of external IO enclosure | |
US9367510B2 (en) | Backplane controller for handling two SES sidebands using one SMBUS controller and handler controls blinking of LEDs of drives installed on backplane | |
US8832347B2 (en) | Automatic detection device, system and method for inter-integrated circuit and serial general purpose input/output | |
US6202160B1 (en) | System for independent powering of a computer system | |
AU2011264940A1 (en) | Systems and methods for intelligent and flexible management and monitoring of computer systems | |
CN111694760B (en) | Server system, flash memory module and method for updating firmware mapping file | |
CN105261329A (en) | Multi-LED display module management method | |
TWI604304B (en) | Electronic apparatus and detection method using the same | |
US20060209680A1 (en) | Network link backup system | |
JP2016206912A (en) | Electronic device, control apparatus, automated teller machine, and usb connector monitoring program | |
US8554974B2 (en) | Expanding functionality of one or more hard drive bays in a computing system | |
US7096300B2 (en) | Method and apparatus for suspending communication with a hard disk drive in order to transfer data relating to the hard disk drive | |
CN105357799A (en) | LED display module management apparatus | |
CN210721440U (en) | PCIE card abnormity recovery device, PCIE card and PCIE expansion system | |
US10928451B2 (en) | Information handling system optional component detection and management | |
US6954358B2 (en) | Computer assembly | |
CN110321263B (en) | Hard disk monitoring system | |
US10592462B2 (en) | Cable detection | |
CN114857069A (en) | Fan smelting tool plate | |
CN114356824A (en) | vpx blade node, state monitoring method, device and storage medium | |
CN116795610A (en) | Hard disk fault detection method, system, device, computer equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: QUANTA COMPUTER INC., TAIWAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YANG, TING-HAO;KUNG, TSU-TAI;LIN, HOU-LUNG;REEL/FRAME:046147/0843 Effective date: 20180611 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
RF | Reissue application filed |
Effective date: 20211223 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |