Background

[0001] A network server can utilize a management sub-system to perform computational tasks. A management sub-system can be utilized to monitor and/or control physical memory in a computer system.

Brief Description of the Drawings

[0002] Figure 1 illustrates a flow chart illustrating an example method for providing a network attached storage (NAS) device to a management sub-system according to the present disclosure.

[0003] Figure 2 illustrates an example diagram representing a system for providing a network attached storage (NAS) device to a management sub-system according to the present disclosure.

Detailed Description

[0004] Examples of the present disclosure include methods, systems, and computer-readable and executable instructions for providing network attached storage (NAS) devices to management subsystems. Methods for providing a NAS device to a management sub-system can include implementing a network file system (NFS) within the management sub-system. Providing a NAS device to a management sub-system also can include communicatively coupling the NFS and the NAS device. Furthermore, providing a NAS device to a management sub- system can include providing the management sub-system access to the NAS device via the implemented NFS.

[0005] In the foliowing detailed description of the present disclosure, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration how examples of the disclosure can be practiced. These examples are described in sufficient detail to enable those of ordinary skill in the art to practice the examples of this disclosure, and it is to be understood that other examples can be utilized and that process, electrical, and/or structural changes can be made without departing from the scope of the present disclosure.

[0006] A management sub-system can be utilized to perform various computational tasks (e.g., control physical memory in a computer system, monitor physical memory, and/or monitor computer processors, among other computational tasks). A management sub-system can be implemented in or communicatively coupled to a server. A management sub-system can lack, or have limited, storage capacity. The lack of, or limited, storage capacity can prevent the management sub-system from enabling applications (e.g., event logging). By implementing a network file system (NFS) within the management sub-system, the management sub-system can have access to a NAS device. The management sub-system can utilize the access to a NAS device to enable applications.

[0007] Figure 1 illustrates a flow chart illustrating an example method 100 for providing a NAS device to a management sub-system according to the present disclosure. The method 100 can be utilized to provide a management sub-system access to a NAS device. The management sub-system can utilize the NAS device in various ways (e.g., event logging, data storage, virtual media access, among other applications that require mass storage).

[0008] At 102, a NFS is implemented into a management sub-system. The NFS can allow a computing device to access files (e.g., directories, system files, among other files) over a network. The NFS can allow a computing device to access and share files on a remote system (e.g., as if the files were local files on the computing device).

[0009] Implementing the NFS into the management sub-system can include a set up that allows the management sub-system to utilize the NFS.

Implementation can also include a set up that allows the management sub-system to access a NAS device via the NFS. The implementation and set up can be different for various servers (e.g. , iL04 ^® by Hewlett-Packard (HP), among other servers). The implementation and set up can also be different for various versions of software (e.g., Windows 7 ^® , among other software versions) being utilized within the server.

[0010] A management sub-system can be a baseboard management controller (BMC). A management sub-system can be a specialized service processor that monitors a state (e.g., physical state) of a computing device (e.g., computer, network server, hardware, etc.) using sensors. In addition, a

management sub-system can communicate with a system administrator to communicate the state (e.g., state of the computing device). Furthermore, a management sub-system can be located in various locations (e.g., in a

motherboard, processor, etc.) within a computing device (e.g., a server).

[0011] At 104, the NFS is communicatively coupled to the NAS device. This coupling can allow the management sub-system to access the NAS device.

Coupling can include a network file system protocol. The network file system protocol can, for example, allow the management sub-system to access the NAS device as if it were local memory to the management sub-system. For example, the NFS can be electronically coupled (e.g. , via Ethernet, local area network (LAN), wide area network (WAN), personal area network (PAN), Wi-Fi ^® ) to the NAS device and the NFS can utilize a network file system protocol to communicate with the NAS device.

[0012] At 106, the management sub-system is provided access to the NAS device via the NFS. The NFS can, for example, provide the management subsystem access to the NAS device as if it were local storage. The management sub-system can utilize the NAS device to enable various applications. For example, the management sub-system can enable event logging. Event logging can include writing data to the NAS device concerning the event data of the physical state of the computing device. The event logging can also include writing related data to the event data of the physical state in the memory of the NAS device. For example, data related to the event can include, but are not limited to: the location, the date, the frequency of the event, the damage, and/or the urgency of repair.

[0013] The management sub-system can enable applications such as opening a file descriptor saved within the NAS device. A file descriptor can, for example, be an abstract indicator for accessing a file. For example, a file descriptor can be an index for an entry in a kernel-resident data structure containing the details of open files.

[0014] The management sub-system can open a file descriptor and write data in a file stored within the NAS device. For example, the management subsystem can write data in a file pertaining to the physical state of the computing device.

[0015] The management sub-system can open a file descriptor and read data in a file stored within the NAS device. For example, the management subsystem can read the data that has been collected and written pertaining to the physical state of the computing device.

[00 6] The NAS device can, for example, be mapped and utilized as physical memory for virtual media that is within the management sub-system. The virtual media can be accessed by a client/user via an internet protocol (e.g., http protocol, among others). The management sub-system, for example, can utilize the NAS device to distribute physical memory to the various virtual media within the management sub-system.

[0017] The NAS device can contain a file in an International Organization for Standardization format (ISO file). An ISO file can be an archive file. The ISO file can, for example, be composed of the data contents of every written sector of an optical device. The ISO file can, for example, be created from an optical disc or from a collection of files.

[0018] The method 100 can resolve a limitation, or lack of, storage capacity in the management sub-system and can simplify the management subsystem virtual media data access. The method 00 can be a cost effective way to provide mass storage capacity to a management sub-system compared to, for example, utilizing embedded flash parts for storage. The method 100 can remove the need for a proprietary client application in virtual media. Furthermore, the method 100 can be less processing intensive when compared to utilizing an internet protocol for storage.

[0019] Figure 2 illustrates an example diagram representing a system 2 0 for providing a NAS device 232 to a management sub-system 214 according to the present disclosure.

[0020] A server 212 can include various hardware and software

components. For example, the server 212 can include a management sub-system 214. As described herein, the management sub-system 214 can be a BMC, for example, and can perform various functions within the server 212.

[0021] The management sub-system 214 can be implemented with various hardware and/or software components. For example, the management subsystem 214 can be implemented with a NFS 220. As described herein, the NFS 220 can provide the management sub-system 214 access to a NAS device 232, for example, as if it were local storage within the management sub-system. The NFS 220 can communicate and/or access data from the NAS device 232 via a NFS protocol 224. The NFS 220 can provide the management sub-system 214 with access to the NAS device 232.

[0022] The management sub-system 214 can utilize the NAS device 232 to enable various applications 218. The management sub-system can, for example, utilize the NAS device 232 to enable event logging. For example, the management sub-system can utilize the NAS device 232 to write/read event data on the NAS device 232. [0023] The management sub-system 214 can, for example, be implemented with virtual media 216. Virtual media 2 6 can be enabled to allow a user to access virtual memory. Virtual media 216 can be a memory management technique that can virtualize various forms of data storage (e.g., NAS device 232, random access memory (RAM), disk storage, etc.). In some examples, the virtual media 216 can utilize data sourcing to retrieve data directly from the NAS device 232. Data sourcing can be retrieving information/data from various sources.

[0024] The virtual media 216 can be implemented by an electronic connection 222 (e.g., a universal serial bus (USB), Ethernet, among others) to the server 212. The virtual media 216 can utilize a physical memory (not shown) within the server 212 to provide virtual memory to a client system 230. The client system 230 can include a computing device able to access a number of computer readable media (e.g., compact disk, solid state memory, RAM, remote hard drive, among others).

[0025] The client system 230 can be connected to the virtual media via a webserver 228 (e.g. , an internet relay chat (IRC) webserver, among other web servers). The webserver 228 can include various other communication devices and utilize other internet protocols (e.g., JSRC webserver, among others). The webserver 228 can, for example, communicate with the virtual media 216 via an internet protocol (e.g., http protocol, among others) 226. The webserver 228 can be implemented in the client system 230 and provide virtual memory from the virtual media 216 to the various parts of the client system 230.

[0026] The system 210 shown in Figure 2 further illustrates a block diagram 290 of an example of a computer-readable medium (CRM) 272 in communication with processing resources 282-1 , 282-2, 282-N, for providing the NAS device 232 to the management sub-system 214. Block diagram 290 is represented within the server 212. Block diagram 290 can also be implemented outside of the server 212, either communicatively coupled to the server 212 and/or performed by a different computing device. [0027] CRM 272 can be in communication with a computing device 284 (e.g., a Java ^® application server, among others) having processor resources of more or fewer than 282-1 , 282-2, 282-N. The computing device 284 can be in communication with a tangible non-transitory CRM 272 storing a set of computer- readable instructions (CRI) 274 executable by one or more of the processor resources 282-1 , 282-2, 282-N, as described herein. The computing device 284 can include memory resources 278, and the processor resources 282-1 , 282- 2, 282-N can be coupled to the memory resources 278.

[0028] Processor resources 282-1 , 282-2, 282-N can execute CRI 274 that can be stored on an internal or external non-transitory CRM 272. A non- transitory CRM (e.g., CRM 272), as used herein, can include volatile and/or nonvolatile memory. Volatile memory can include memory that depends upon power to store information, such as various types of dynamic random access memory (DRAM), among others. Non-volatile memory can include memory that does not depend upon power to store information. Examples of non-voiatile memory can include solid state media such as flash memory, electrically erasable

programmable read-only memory (EEPROM), phase change random access memory (PCRAM), magnetic memory such as a hard disk, tape drives, floppy disk, and/or tape memory, optical discs, digital versatile discs (DVD), Blu-ray discs (BD), compact discs (CD), and/or a solid state drive (SSD), etc., as well as other types of computer-readable media.

[0029] The non-transitory CRM 272 can be integral, or communicatively coupled, to a computing device, in a wired and/or a wireless manner. For example, the non-transitory CRM 272 can be an internal memory, a portable memory, a portable disk, or a memory associated with another computing resource (e.g. , enabling computer-readable instructions to be transferred and/or executed across a network such as the Internet).

[0030] The CRM 272 can be in communication with the processor resources

282-1 , 282-2, 282-N via a communication path 276. The communication path 276 can be local or remote to a machine (e.g., a computer) associated with the processor resources 282-1 , 282-2 282-N. Examples of a local communication path 276 can include an electronic bus internal to a machine (e.g., a computer) where the CRM 272 is one of volatile, non-volatile, fixed, and/or removable storage medium in communication with the processor resources 282-1 , 282-2, 282-N via the electronic bus. Examples of such electronic buses can include Industry Standard Architecture (ISA), Peripheral Component Interconnect (PCI), Advanced Technology Attachment (ATA), Small Computer System Interface (SCSI),

Universal Serial Bus (USB), among other types of electronic buses and variants thereof.

[0031] The communication path 276 can be such that the CRM 272 is remote from the processor resources e.g., 282-1 , 282-2, 282-N, such as in a network connection between the CRM 272 and the processor resources (e.g., 282- 1 , 282-2, 282-N). That is, the communication path 276 can be a network connection. Examples of such a network connection can include a LAN, WAN, PAN, and the Internet, among others. In such examples, the CRM 272 can be associated with a first computing device and the processor resources 282-1 , 282-2, ... , 282-N can be associated with a second computing device (e.g., a Java ^® application server).

[0032] The processor resources 282-1 , 282-2, ... , 282-N coupled to the memory 278 can enable the NFS 220 to be implemented in a management subsystem 214. The processor resources 282-1 , 282-2, 282-N coupled to the memory 278 can also access the NAS device 232 utilizing the NFS 220.

Furthermore, the processor resources 282-1 , 282-2, 282-N coupled to the memory 278 can utilize the NAS device 232 for management sub-system

applications 218 (e.g., event logging, among other applications).

[0033] As used herein, "logic" is an alternative or additional processing resource to execute the actions and/or functions, etc., described herein, which includes hardware (e.g., various forms of transistor logic, application specific integrated circuits (ASICs), etc.), as opposed to computer executable instructions (e.g., software, firmware, etc.) stored in memory and executable by a processor. [0034] The specification examples provide a description of the applications and use of the system and method of the present disclosure. Since many examples can be made without departing from the spirit and scope of the system and method of the present disclosure, this specification sets forth some of the many possible example configurations and implementations.