Storage enclosure and system including the storage enclosure

A storage enclosure connected to a server via an external network and includes a network switch, an expander that is connected to the network switch and that is configured to generate enclosure data that supports a format conforming with SCSI Enclosure Services, and a board management controller (BMC) that is connected to the network switch and the expander. The BMC is configured to translate the enclosure data into enclosure translating data that supports a Redfish® format. The expander is configured to, after generating the enclosure data, transmit the enclosure data through the network switch to the BMC via an internal network. The BMC is configured to translate the enclosure data into the enclosure translating data, and to transmit the enclosure translating data to the network switch. The network switch transmits the enclosure translating data to the server through the external network.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to Taiwanese Invention Patent Application No. 110147166, filed on Dec. 16, 2021.

FIELD

The disclosure relates to a storage enclosure, and more particularly to a storage enclosure that is configured to be manageable in one of an out-of-band management mode and an in-band management mode, and a system that includes the storage.

BACKGROUND

In the field of managing a Small Computer System Interface (SCSI) enclosure product such as a just a bunch of disks (JBOD) enclosure, a Serial Attached SCSI (SAS) expander is typically employed. In use, the SAS expander is configured to record a status of the JBOD enclosure such as a status of a hard disk drive (HDD) included in the JBOD enclosure, a status of a power supply of the JBOD enclosure, a status of one or more fans of the JBOD enclosure, a status of an input/output (I/O) module of the JBOD enclosure, or a status of one or more power cables, and to control various aspects of the JBOD enclosure such as a light-emitting diode associated with the HDD (HDD LED), a speed of the fans, etc.

The SCSI Enclosure Services (SES) is a protocol that is typically used for managing enclosure products. The SES has a set of SCSI commands that allows a host server to communicate with the enclosure products such as requesting a return of a message, transmitting a control command, etc. The host server is typically installed with a host bus adapter (HBA) card or a redundant array of independent disks (RAID) adapter so as to be enabled to connect to an external SAS JBOD enclosure via an external SAS cable. The SES is typically provided with an interface (known as a diagnosis page) for enabling the host server to manage the SAS JBOD enclosure, and in use, data is transmitted via the SAS cable, such that the status of the SAS JBOD enclosure is transmitted via the SAS cable to the main server, and data may be transmitted from the host server via the SAS cable to the SAS JBOD enclosure and stored therein. This manner of management of the SAS JBOD enclosure is known as in-band management.

It is noted that since the SAS JBOD enclosure is typically deployed under the host server, a user is required to have access to the main server in order to obtain the status of the SAS JBOD enclosure. That is to say, when the main server is shut down or under external attacks, the user would not be able to manage the SAS JBOD enclosure using in-band management. To address this issue, out-of-band management was proposed. In use, the SAS JBOD enclosure may be connected to, for example, an Ethernet network via an Ethernet interface. As such, the user may manage the SAS JBOD enclosure remotely, without accessing the main server.

The Redfish standard includes a suite of specifications that provides an industry standard protocol for out-of-band management of servers and storages. In use, the content of the SES diagnosis page needs to be convert into a format that conforms with the Redfish standard in order for the user to remotely implement out-of-band management using the Redfish standard. This task is considered difficult for the SAS expander, whose chipset is typically equipped with limited computing capabilities. As such, some personnel still prefer to implement in-band management, reserving the Ethernet interface for a troubleshooting (debug) port that is configured to transmit data related to troubleshooting. Additionally, in order to reduce cost, it is common that only one of in-band management and out-of-band management is established for the management of a conventional SAS JBOD enclosure.

SUMMARY

Therefore, one object of the disclosure is to provide a storage enclosure that may enable a user to choose freely between using one of an out-of-band management and an in-band management to perform remote management.

According to one embodiment of the disclosure, the storage enclosure is connected to a server via an external network and includes:a network switch;an expander that is connected to the network switch and that is configured to generate enclosure data that supports a format conforming with Small Computer System Interface (SCSI) Enclosure Services (SES); anda board management controller (BMC) that is connected to the network switch and the expander, and that is configured to translate the enclosure data that supports the format conforming with SES into enclosure translating data that supports a Redfish® format;

The expander is configured to, after generating the enclosure data, transmit the enclosure data through the network switch to the BMC via an internal network.

The BMC is configured to, in response to receipt of the enclosure data, translate the enclosure data into the enclosure translating data, and transmit the enclosure translating data to the network switch.

The network switch is configured to, in response to receipt of the enclosure translating data, transmit the enclosure translating data to the server through the external network.

Another object of the disclosure is to provide a system that includes the above-mentioned storage enclosure.

According to one embodiment of the disclosure, the system includes a storage enclosure and a server connected to the storage enclosure via an external network, the storage enclosure including:a network switch;an expander that is connected to the network switch and that is configured to generate enclosure data that supports a format conforming with Small Computer System Interface (SCSI) Enclosure Services (SES); anda board management controller (BMC) that is connected to the network switch and the expander, and that is configured to translate the enclosure data that supports the format conforming with SES into enclosure translating data that supports a Redfish® format.

The expander is configured to, after generating the enclosure data, transmit the enclosure data through the network switch to the BMC via an internal network.

The BMC is configured to, in response to receipt of the enclosure data, translate the enclosure data into the enclosure translating data, and transmit the enclosure translating data to the network switch.

The network switch is configured to, in response to receipt of the enclosure translating data, transmit the enclosure translating data to the server through the external network.

DETAILED DESCRIPTION

Throughout the disclosure, the term “coupled to” or “connected to” may refer to a direct connection among a plurality of electrical apparatus/devices/equipment via an electrically conductive material (e.g., an electrical wire), or an indirect connection between two electrical apparatus/devices/equipment via another one or more apparatus/devices/equipment, or wireless communication.

FIG.1is a block diagram illustrating a storage enclosure1according to one embodiment of the disclosure. In this embodiment, the storage enclosure1is connected to a server2via an external network.

The storage enclosure1includes a network switch11, an expander12that is connected to the network switch11, and a board management controller (BMC)13that is electronically connected to the network switch11and the expander12.

The server2includes a network card21and a Serial Attached SCSI (SAS) host bus adapter (HBA)22. In some embodiments, the server2may further include a processor, a memory module, and a communication unit. It is noted that in this embodiment, the server2is embodied using a host server, but is not limited as such.

The processor may include, but not limited to, a single core processor, a multi-core processor, a dual-core mobile processor, a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), and/or a radio-frequency integrated circuit (RFIC), etc.

The memory module may be embodied using, for example, random access memory (RAM), read only memory (ROM), programmable ROM (PROM), firmware, and/or flash memory, etc.

The communication unit may include one or more of a radio-frequency integrated circuit (RFIC), a short-range wireless communication module supporting a short-range wireless communication network using a wireless technology of Bluetooth® and/or Wi-Fi, etc., and a mobile communication module supporting telecommunication using Long-Term Evolution (LTE), the third generation (3G), the fourth generation (4G) or fifth generation (5G) of wireless mobile telecommunications technology, or the like.

The network switch11includes a first medium dependent interface (MDI) port111, a second MDI port112, a first reduced gigabit media independent interface (RGMII) port113, a second RGMII port114, and a first Management Data Clock/Management Data Input/Output (MDC/MDIO) port115.

In this embodiment, the network switch11is configured to operate in one of an out-of-band management mode and an in-band management mode. When operating in the out-of-band management mode, the network switch11is configured to serve as an intermediate to enable an internal connection between the BMC13and the expander12, and enable an external connection between the BMC13and the server2. When operating in the in-band management mode, the network switch11is configured to serve as an intermediate to enable an external connection to be established between the expander12and the server2.

It is noted that the internal connection may be implemented using an internal network that conforms with the connection protocols associated with the ports included in the network switch11, the expander12and the BMC13, and the external connection may be implemented using an external network (e.g., the Internet Protocol (IP)). In use, the second MDI port112of the network switch11may be connected to the network card21of the server2using an RJ45 connector14and an Ethernet interface of the network card21, and this connection serves as a part of the external connection.

The expander12includes a first media access control (MAC) port121, a first universal asynchronous receiver/transmitter (UART) port122, and a SAS port123. In use, the expander12is configured to generate enclosure data that supports a format that conforms with the SCSI Enclosure Services (SES).

The expander12is configured to operate in one of the out-of-band management mode and the in-band management mode. When the expander12operates in the out-of-band management mode, the internal connection between the expander12and the BMC13using the internal network is established through the network switch11. When the expander12operates in the in-band management mode, the external connection between the expander12and the server2using the external network is established through the network switch11. Additionally, the expander12and the server2are connected using an SAS cable (not depicted in the drawings) that interconnects an SAS connector15and the SAS HBA22. The SAS connector15is included in the storage enclosure1and is connected to the SAS port123of the expander12.

Specifically, when the expander12operates in the out-of-band management mode, the internal connection between the expander12and the BMC13is established by connecting the first MAC port121of the expander12to the first RGMII port113of the network switch11. Furthermore, data received by the network switch11through the first RGMII port113is transmitted using the internal network through the first MDI port111. On the other hand, when the expander12operates in the in-band management mode, the external connection between the expander12and the server2is established by connecting the first MAC port121of the expander12to the first RGMII port113of the network switch11. Furthermore, data received by the network switch11through the first RGMII port113is transmitted using the external network through the second MDI port112.

The BMC13includes a second MAC port131, a third MAC port132, a second MDC/MDIO port133, and a second UART port134. In use, the BMC13is configured to translate the enclosure data that supports the format conforming with SES into enclosure translating data that supports a Redfish® format, and is configured to translate data that supports the Redfish® format to data that supports the format conforming with SES.

The BMC13is configured to operate in one of the out-of-band management mode and the in-band management mode. When the BMC13operates in the out-of-band management mode, the internal connection between the BMC13and the expander12using the internal network through the network switch11is established, and the external connection between the BMC13and the server2is established through the network switch11. When the BMC13operates in the in-band management mode, no connection between the BMC13and the expander12is established using the network switch11.

Specifically, when the BMC13operates in the out-of-band management mode, the internal connection between the expander12and the BMC13is established by connecting the second MAC port131of the BMC13to the first MDI port111of the network switch11, and the external connection between the BMC13and the server2is established by connecting the third MAC port132of the BMC13to the second RGMII port114of the network switch11.

For the storage enclosure1, the components (the network switch11, the expander12and the BMC13) may be controlled by the server2to operate in one of the out-of-band management mode and the in-band management mode, and the storage enclosure1may thus operate in the one of the out-of-band management mode and the in-band management mode. Specifically, the expander12is configured to, in response to receipt of a command from the server2via the SAS cable that instructs the expander12to operate in one of the out-of-band management mode and the in-band management mode, proceed to operate in the one of the out-of-band management mode and the in-band management mode, and transmit a message to the second UART port134of the BMC13via the first UART port122. The message instructs the BMC13to operate in the one of the out-of-band management mode and the in-band management mode. The BMC13is configured to, in response to receipt of the message, proceed to operate in the one of the out-of-band management mode and the in-band management mode, and transmit an instruction to the first MDC/MDIO port115of the network switch11via the second MDC/MDIO port133. The instruction instructs the network switch11to operate in the one of the out-of-band management mode and the in-band management mode. In response to receipt of the instruction, the network switch11is configured to proceed to operate in the one of the out-of-band management mode and the in-band management mode.

FIG.2is a block diagram of the storage enclosure1and the server2, illustrating data transmission when the storage enclosure1is operating in the out-of-band management mode according to one embodiment of the disclosure.

FIG.3is a flow chart illustrating steps of an enclosure data transmission process of a method of management of the storage enclosure1in the out-of-band management mode according to one embodiment of the disclosure. In this embodiment, the enclosure data transmission process is implemented by the storage enclosure1and the server2as shown in the embodiment ofFIG.2, and involves transmitting data from the storage enclosure1to the server2.

In step31, the expander12generates enclosure data that supports the format conforming with SES, and transmits the enclosure data, using the first MAC port121of the expander12, to the first RGMII port113of the network switch11. As such, the enclosure data is available to be transmitted to the BMC13using the network switch11.

In step32, in response to receipt of the enclosure data via the first RGMII port113, the network switch11transmits the enclosure data, using the first MDI port111, to the second MAC port131of the BMC13through the internal network. As such, the enclosure data is transmitted from the expander12to the BMC13.

In step33, in response to receipt of the enclosure data via the second MAC port131through the internal network, the BMC13translates the enclosure data into enclosure translating data that supports the Redfish® format, and transmits the enclosure translating data, using the third MAC port132of the BMC13, to the second RGMII port114of the network switch11. As such, the network switch11is ready to transmit the enclosure translating data to the server2.

In step34, in response to receipt of the enclosure translating data via the second RGMII port114, the network switch11transmits the enclosure translating data, using the second MDI port112, to the server2through the external network.

In one alternative embodiment, the network switch11is configured to, in response to receipt of the enclosure data, transmit the enclosure data using the first MDI port111through the internal network, and in response to receipt of the enclosure translating data, transmit data using the second MDI port112through the external network.

It is noted that, in this embodiment, the network switch11is configured to transmit data based on a port from which data is received. Specifically, in the case that the network switch11receives data from the first RGMII port113, the network switch11is configured to transmit the data using the first MDI port111through the internal network. On the other hand, in the case that the network switch11receives data from the second RGMII port114, the network switch11is configured to transmit the data using the second MDI port112through the external network. However, in other embodiments, the network switch11is configured to detect an address associated with the received data (e.g., the enclosure data or the enclosure translating data). In the case that the address associated with the received data is determined to indicate that the received data is received via the internal network, the network switch11is configured to transmit the received data using the first MDI port111through the internal network. On the other hand, in the case that the address associated with the received data is determined to indicate that the received data is not received via the internal network (i.e., the data is determined to be received via the external network), the network switch11is configured to transmit the received data using the second MDI port112through the external network.

FIG.4is a flow chart illustrating steps of an external data transmission process of a method of management of the storage enclosure1in the out-of-band management mode according to one embodiment of the disclosure. In this embodiment, the external data transmission process is implemented by the storage enclosure1and the server2as shown in the embodiment ofFIG.2, and involves transmitting external data received from the server2to the expander12. It is noted that in the embodiments, the term “external data” refers to data transmitted by the server2that supports the Redfish® format.

In step41, in response to receipt of external data from the server2via the second MDI port112through the external network, the network switch11transmits the external data, using the second RGMII port114, to the third MAC port132of the BMC13.

In step42, in response to receipt of external data via the third MAC port132, the BMC13translates the external data into external translating data that supports the format conforming with SES. Then, the BMC13transmits the external translating data, using the second MAC port131, to the first MDI port111of the network switch11. As such, the external translating data is available to be transmitted to the expander12using the network switch11.

In step43, in response to receipt of the external translating data via the first MDI port111, the network switch11transmits the external translating data, using the first RGMII port113, to the first MAC port121of the expander12through the internal network.

It is noted that, in this embodiment, the network switch11is configured to transmit data based on a port from which data is received. Specifically, in the case that the network switch11receives data from the first MDI port111through the internal network, the network switch11is configured to transmit the data using the first RGMII port113. On the other hand, in the case that the network switch11receives data from the second MDI port112through the external network, the network switch11is configured to transmit the data using the second RGMII port114. However, in other embodiments, the network switch11is configured to detect an address associated with the received data (e.g., the external data or the external translating data) to determine how to transmit the received data (i.e., using the first RGMII port113or the second RGMII port114to transmit the received data). In the case that the address associated with the received data is determined to indicate that the received data is received via the internal network, the network switch11is configured to transmit the received data using the first RGMII port113. On the other hand, in the case that the address associated with the received data is determined to indicate that the received data is not received via the internal network (e.g., the address is determined to be received via the external network), the network switch11is configured to transmit the received data using the second RGMII port114.

In brief, using the above-mentioned enclosure data transmission process and the external data transmission process, the storage enclosure1may be configured to operate in the out-of-band management mode, in which the enclosure data generated by the expander12may be transmitted to the BMC13using the internal network, and the BMC13is configured to translate the enclosure data into enclosure translating data that supports the Redfish® format. As such, the enclosure translating data is available to be transmitted to the server2using the external network. In this manner, an Ethernet interface of the server2may be used by a user to remotely manage the storage enclosure1using out-of-band management, in addition to being used as a troubleshooting (debug) port. It is noted that in other embodiments, using the out-of-band management, the user is enabled to operate other electronic device other than the server2to perform the managing of the storage enclosure1through the RJ45 connector14.

FIG.5is a block diagram of the storage enclosure1and the server2, illustrating data transmission when the storage enclosure1is operating in the in-band management mode according to one embodiment of the disclosure. It is noted that, when the user intends to manage the storage enclosure1in the in-band management mode, he/she may operate the server2to transmit the command to the storage enclosure1using the SAS cable.

FIG.6is a flow chart illustrating a step of an enclosure data transmission process of a method of management of the storage enclosure1in the in-band management mode according to one embodiment of the disclosure. In this embodiment, the enclosure data transmission process is implemented by the storage enclosure1and the server2as shown in the embodiment ofFIG.5, and involves transmitting data from the storage enclosure1to the server2.

Specifically, after generating the enclosure data, in step61, the expander12transmits the enclosure data via the SAS port123to the server2using the SAS cable.

FIG.7is a flow chart illustrating a step of an external data transmission process of a method of management of the storage enclosure1in the in-band management mode according to one embodiment of the disclosure. In this embodiment, the external data transmission process is implemented by the storage enclosure1and the server2as shown in the embodiment ofFIG.5, and involves transmitting external data that supports the SCSI enclosure service format from the server2to the storage enclosure1.

Specifically, after generating the external data, in step71, the server2transmits the external data via the SAS HBA22to the expander12using the SAS cable.

FIG.8is a flow chart illustrating steps of a troubleshooting data transmission process of a method of management of the storage enclosure1in the in-band management mode according to one embodiment of the disclosure. In this embodiment, the troubleshooting data transmission process is implemented by the storage enclosure1and the server2as shown in the embodiment ofFIG.5, and involves transmitting troubleshooting data from the storage enclosure1to the server2.

Specifically, the troubleshooting data may be gathered by the expander12automatically, or generated by the expander12in response to receipt of a request from the server2. After generating the troubleshooting data, in step81, the expander12transmits the troubleshooting data via the first MAC port121to the first RGMII port113of the network switch11. As such, the troubleshooting data is available to be transmitted by the network switch11to the server2.

Then, in step82, in response to receipt of the troubleshooting data via the first RGMII port113, the network switch11transmits the troubleshooting data, using the second MDI port112, to the server2through the external network.

In brief, by using the above-mentioned enclosure data transmission process, the external data transmission process and the troubleshooting data transmission process, the storage enclosure1may be configured to operate in the in-band management mode, in which the enclosure data and the external data may be transmitted between the storage enclosure1and the server2via the SAS cable. In this manner, the Ethernet interface of the server2may be used as a troubleshooting (debug) port.

In sum, the embodiments of the disclosure provide a storage enclosure1that is controllable to operate in one of the out-of-band management mode and the in-band management mode. When operating in the out-of-band management mode, the enclosure data may be transmitted to the BMC13, which is configured to translate the enclosure data into enclosure translating data that supports the Redfish® format. As such, the enclosure translating data is available to be transmitted to the server2by the network switch11using the external network. Alternatively, when the user intends to manage the storage enclosure1in the in-band management mode, he/she may operate the server2to transmit the command to the storage enclosure1, so as to control the storage enclosure to operate in the in-band management mode. As such, the storage enclosure1is configured to be managed using one of the out-of-band management mode and the in-band management mode, depending on the user's choice.

According to one embodiment of the disclosure, there is provided a system that includes a storage enclosure1and a server2, exemplified inFIG.1. The system is configured such that a user is enabled to operate the server2to transmit a command to the storage enclosure1, so as to control the storage enclosure1to operate in one of the out-of-band management mode and the in-band management mode. That is to say, the system provides the operations of both of the out-of-band management and the in-band management, and therefore enables a user to choose freely between using one of the out-of-band management and the in-band management to perform remote management of the storage enclosure1.