JP2008027149A - Maintenance information management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To construct a maintenance information management system for performing maintenance quickly with respect to a plurality of server devices so as to cover both hardware maintenance and software maintenance without omission. <P>SOLUTION: In the maintenance information management system equipped with a maintenance management server for maintaining and managing information on hardware or software in a server to be maintained and managed, the maintenance management server 008 manages a hardware configuration and software version information of servers 001 and 002 in a customer database and, when hardware maintenance, a periodical inspection, or software update of the server occurs, instructs the server to reserve the hardware maintenance or periodical inspection on the basis of the customer information in the customer database 009 or notifies the relevant server propriety of selection of the software update. According to a response from the server, the maintenance management server performs work for the hardware maintenance or hardware periodical inspection of the server or executes the software update. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a maintenance information management system and a maintenance information management method, and in particular, by maintaining the latest state of a customer server in a customer information database using the maintenance management server, leakage of maintenance work is performed. The present invention relates to a system and method that can perform quick maintenance for customers so that there is no problem, and can automatically perform maintenance work arrangements for periodic inspections.

A conventional technique for remotely monitoring devices, collecting information, analyzing information, and providing maintenance services via a network is proposed in, for example, Patent Document 1. The management system disclosed in Patent Document 1 is a maintenance monitoring system in which a monitoring target device, a diagnostic device, and a maintenance service providing device are connected via a network, and the diagnostic device stores device information of the monitoring target device. It grasps and requests the maintenance service providing apparatus from the monitoring target apparatus for information necessary for maintenance, and performs the maintenance service.
JP 2005-301712 A

  However, in the conventional technology as shown in the above-mentioned Patent Document 1, the monitoring target device requires a procedure for confirming with the diagnostic device whether or not maintenance work is performed, but depending on the setting of the access frequency of the monitoring target device to the diagnostic device. The response of maintenance work may be delayed.

  In addition, if the administrator of the monitored device does not know that maintenance work has occurred, software maintenance can automatically provide maintenance services (by downloading software), but hardware maintenance can provide maintenance. Since this is accompanied by work by personnel, there may be a situation in which it is impossible to cope with this work management.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a maintenance information management system capable of more quickly performing maintenance work so that there is no omission in performing hardware maintenance and software maintenance for a plurality of servers at a customer site. It is another object of the present invention to provide a maintenance information management system capable of managing maintenance schedules necessary for hardware maintenance and automating the arrangement of maintenance work.

In order to solve the above problems, the present invention mainly adopts the following configuration.
Communication between a customer site having a plurality of servers to be subjected to maintenance management, a maintenance site having a maintenance management server for maintenance management of hardware configuration or software version information in the server, and communication between the customer site and the maintenance site A maintenance management system comprising a network for performing
The server at the customer site manages its own hardware configuration and software version information, and notifies the maintenance management server via the network when a change in the hardware configuration and the software version information occurs,
The maintenance management server of the maintenance site manages the hardware configuration and the software version information notified from the server in a customer database storing various customer information,
Further, the maintenance management server schedules the hardware maintenance or the hardware periodic inspection based on the customer information of the customer database when the hardware maintenance or the hardware periodic inspection or the software update of the server occurs. Instruct the appropriate server or notify the appropriate server whether or not to select the software update,
When the server that is instructed to make a reservation or is notified of whether or not to select the software update, executes the reservation for the maintenance management server or selects the update, the maintenance management server can execute the hardware of the server. It is configured to perform work for hardware maintenance or periodic hardware inspection, or execute software update.

A maintenance information management system comprising a maintenance management server that maintains and manages hardware configuration or software version information on a plurality of servers that are maintenance targets,
The maintenance management server receives, from the server, information in which the hardware configuration and software version information of the server itself are changed, and the changed hardware configuration and software version information are stored in the customer in which various customer information is stored. Managed in the database,
Further, the maintenance management server schedules the hardware maintenance or the hardware periodic inspection based on the customer information of the customer database when the hardware maintenance or the hardware periodic inspection or the software update of the server occurs. Instruct the appropriate server or notify the appropriate server whether or not to select the software update,
The maintenance management server is configured to perform a task for hardware maintenance or hardware periodic inspection of the server or to perform software update according to a reservation execution or update response by the server.

The maintenance information management system includes a maintenance staff management server for managing a maintenance staff schedule, and a maintenance reservation server for registering a reservation date for hardware maintenance work.
The maintenance management server is configured to perform maintenance management of the maintenance staff by allocating a maintenance staff schedule to the maintenance staff management server based on information on a maintenance work reservation date registered in the maintenance reservation server. .

  According to the present invention, it is possible to quickly perform maintenance work on a plurality of servers so that hardware maintenance and software maintenance are not missed. In addition, personnel costs can be reduced by managing the schedule of maintenance personnel necessary for hardware maintenance and automating maintenance work.

  A maintenance information management system according to an embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing an overall maintenance system including a maintenance information management system according to an embodiment of the present invention. FIG. 2 is a block diagram of the customer side including a maintenance management target server and a management PC according to the present embodiment. FIG. 3 is a diagram showing a basic information management table managed by the server management software in the maintenance management target server according to this embodiment. FIG. 4 is a diagram showing a server information management table managed by the server management software in the maintenance management target server according to the present embodiment. FIG. 5 is a diagram showing the contents of packet data transmitted from the customer side to the maintenance side at the time of information update in the maintenance management target server.

  FIG. 6 is a diagram showing a customer information management table managed by a customer database provided in the maintenance information management system according to the present embodiment. FIG. 7 is a diagram showing a component management table managed by a component database provided in the maintenance information management system according to the present embodiment. FIG. 8 is a view showing a module management table managed by a module database provided in the maintenance information management system according to the present embodiment.

  In FIG. 1 showing an overall maintenance system including a maintenance information management system according to this embodiment, the overall maintenance system includes a maintenance information management system according to this embodiment, which is shown as a maintenance company 007 in the drawing, a network 016, And at least one customer site (including maintenance management target servers 1 to n) 003.

  001 represents a server, and 002 represents a plurality of servers n. The server 001 and the server n002 incorporate server management software 102 that manages its own hardware configuration and software information (see FIG. 2). The server management software 102 manages information data in the server in a format as shown in FIG. 003 represents a customer site where a plurality of servers from server 001 to server n002 are installed.

  004 represents an administrator who manages the server, and 005 represents a management PC of the administrator 004. The management PC 005 incorporates a server management console 114 for managing the server (see FIG. 2). 006 represents a server information packet transmitted from the server management software 102. When the server configuration changes, the server management software transmits packet data 006 to the maintenance management server 008.

  007 represents a maintenance company that is a maintenance base that performs maintenance of the server 001. Reference numeral 008 denotes a maintenance management server installed in the maintenance company 007. The server 001 hardware and software update information packet transmitted from the server 101 is registered in the customer database 009 in the data format shown in FIG.

  The maintenance management server 008 periodically checks the necessity of update information with respect to the module database 010 and the parts database 012 regarding the necessity of maintenance work, and confirms with the customer database 009 about the necessity of periodic inspection. . The maintenance management server 008 provides maintenance parts replacement work (for example, replacement of a defective HDD) and software (for example, driver and firmware) update work (the maintenance management server sends update information of software such as a driver to the servers 1 to n). When a periodic inspection operation occurs, a search is performed from the customer database 009 (for example, a corresponding server in which an old version HDD to be checked is installed is searched from the customer database 009).

  In other words, the maintenance management server 008 confirms information on parts that require maintenance and replacement from the parts database 012, confirms information on modules for software update from the module database 010, and requires periodic inspection from the customer database 009. The information of the right customers. The maintenance management server 008 notifies the maintenance information to the management PC 005 of the server administrator 004 that needs the maintenance work based on the maintenance work information.

  Reference numeral 009 denotes a customer database that manages information on shipped servers. In the customer database 009, the customer information management table shown in FIG. 6 is managed, and the hardware configuration and software version at the time of factory shipment of the server are registered. When customer server update information (for example, downloaded updated software information) is transmitted from the maintenance management server 008, the customer information management table is updated. In other words, the customer information shown in FIG. 6 is created based on the data at the time of server shipment, and the addition / update data is updated from the server management software as needed.

  Reference numeral 010 denotes a module database that manages and registers the latest software version of the server shipped so far. The module database 010 manages the version of BIOS, firmware, and driver for each model / optional part in the module management table shown in FIG. 8, and the latest version of each is registered.

  Reference numeral 011 denotes a module data server in which a server update tool is stored. The maintenance management server 008 requests an update tool necessary for the software update operation based on the update tool name managed in the module database 010. The update tool stored in the module data server 011 is stored in an automatically updateable file format.

  Reference numeral 012 denotes a parts database in which parts information of servers shipped so far is registered. The parts database 012 manages model / option part information in the parts management table shown in FIG. When a replacement target part is generated, a replacement necessity flag cell for registering and changing the corresponding part as a replacement part is provided. In FIG. 7, reference numeral 605 denotes a part Ver. Represents.

  013 is a maintenance person. 014 is a maintenance staff management server that manages the schedule of maintenance staff 013. The maintenance staff management server 014 receives the registration of the maintenance reservation server 015 and automatically allocates the schedule of each maintenance staff. When the maintenance staff 013 inputs the work completion information after the work is performed, the maintenance completion information is registered in the maintenance management server 008. Reference numeral 015 denotes a maintenance reservation server. The server administrator 004 can access the maintenance reservation server 015 via the server management console 114 and reserve a maintenance part replacement date and a hardware periodic inspection date with the customer name and registered password. Regarding the setting of the reservation available date in the maintenance reservation server 015, the maintenance worker management server 014 adjusts the schedule, and the date and time when maintenance personnel cannot be handled cannot be selected in advance as the maintenance reservation date. Reference numeral 016 denotes a wide area network.

  FIG. 2 shows a block diagram of the server 001, and 101 represents the server 001. Reference numeral 102 denotes server management software that manages hardware configuration information and software version of the server 001 itself. The server management software 102 manages the basic information management table 103 and the server information management table 104.

  Reference numeral 103 denotes a basic information management table that manages basic information of the server. The basic information management table 103 manages the model name, serial number, and OS type as basic hardware information (see FIG. 3). A server information management table 104 manages server configuration information and software version information. The server information management table 104 includes, as hardware configuration and software version information, information on the RAID board 105, CPU 106, and memory 107 incorporated in the server 101, BIOS 108, RAID board 105 driver 110, and F / W (firmware) llll. Centrally manages version information.

  A communication cable 112 connects the server 101 and the management PC 113. Reference numeral 113 denotes a management PC. A server management console 114 can refer to the basic information management table 103 and the server information management table 104 in the server management software 102.

  The server management console 114 transmits the information in the server information management table 104 to the maintenance management server 008. The server management console 114 receives software update, hardware maintenance, and periodic inspection notifications from the maintenance management server 008. When a change occurs in the server configuration, after restarting the server, the server management software 102 reads the hardware configuration and software version information again, and updates the server information management table 104. The server management console 114 transmits the updated server information management table 104 information to the maintenance management server 008.

  FIG. 3 is a basic information management table 103 that manages server basic information of the server management software 102. In the basic information management table 103, a model name cell 201, a serial number cell 202, and an OS type cell 203 of the server body are registered.

  FIG. 4 is a server information management table 104 that manages the hardware configuration / software version information of the server management software 102. Reference numeral 301 denotes a division cell indicating information on the system apparatus main body or optional items. Reference numeral 302 denotes a model name cell. Reference numeral 303 denotes a part type name cell. Reference numeral 304 denotes a part name cell, and reference numeral 305 denotes a part detailed information cell. Reference numeral 306 denotes a software category cell, and reference numeral 307 denotes a software version information cell. The server information management table is rewritten whenever the hardware configuration or software version of the server is updated.

  FIG. 5 shows packet data transmitted from the server 001 when the hardware configuration or software version of the server 001 is updated. 401 is the IP address of the maintenance management server 008. Reference numeral 402 denotes information on the serial number cell 202 of the server 001. Reference numeral 403 denotes information on cells 301 to 307 updated and added in the server information management table. Reference numeral 404 denotes packet data obtained by packetizing 401 to 403 in order to notify the maintenance management server 008 of information through the wide area network 016.

  FIG. 6 is a customer information management table for managing the contents of customer information in the customer database 008 in the maintenance company (maintenance base or maintenance side) 007. Reference numeral 501 denotes an IP address cell of the management PC 005 of the server administrator 004. Reference numeral 502 denotes a manufacturing number cell of the customer server. The production number is unique and can be specified even if a plurality of servers are stored in the customer site 003. Reference numeral 503 denotes a model name cell of the server. Reference numeral 504 denotes a part type name cell. Reference numeral 505 denotes a category cell of software when rewritable software exists in the server component. Reference numeral 506 denotes a software version cell. Reference numeral 507 denotes a customer name cell.

  Reference numeral 508 denotes an email address cell of the server administrator 004. Reference numeral 509 denotes a telephone number cell of the server administrator 004. Reference numeral 510 denotes an address cell of the customer site 003. Reference numeral 511 denotes a shipping date cell in which the server shipping date is registered. Reference numeral 512 denotes a scheduled maintenance date cell for registering a maintenance date reserved by the server administrator 004 in the maintenance reservation server 015 when the server 001 corresponds to the hardware maintenance target. Reference numeral 513 denotes a periodic inspection reservation date cell for registering the periodic inspection date reserved by the server administrator 004 in the maintenance reservation server 015 when the server 001 corresponds to the periodic inspection target. Reference numeral 514 denotes a periodic inspection execution date cell for registering the date when the hardware periodic inspection of the server 001 is performed when the server 001 corresponds to the periodic inspection target.

  FIG. 7 is a component management table for managing component information in the component database 012 in the maintenance company 007. Reference numeral 601 denotes a classification cell indicating information on the system apparatus main body or optional items. Reference numeral 602 denotes a model name cell, and reference numeral 603 denotes a part model name cell. Reference numeral 604 denotes a part name cell, and reference numeral 605 denotes a part version cell. Reference numeral 606 denotes a latest version cell for registering the latest version information. Reference numeral 607 denotes a replacement necessity cell indicating whether or not parts need to be replaced. Reference numeral 608 denotes a registration date cell indicating the registration date of the replacement necessity cell. Reference numeral 609 denotes an importance cell indicating the importance of performing part replacement. Reference numeral 610 denotes a reason cell indicating the reason for replacement of parts.

  When a replacement part is registered, information corresponding to the latest version is added. At the same time, the column of the old part version cell is not deleted, the latest version cell is rewritten to the latest version, and the update necessity cell is registered with “Y”. Further, in order to reduce the processing work load of the maintenance management server 008, the replacement necessity cell is registered with “Y”, the corresponding server is searched from the customer information management table shown in FIG. 6, and the corresponding server exists. If not, the exchange necessity cell is rewritten to “−”.

  When the importance cell 609 of the parts management table is “large” (maintenance staff 013 and maintenance staff management server 014 make “large”), the server administrator who corresponds to parts replacement in the parts replacement work described later. If 004 does not make a reservation in the maintenance reservation server 015 on the day when the replacement notification is received, the maintenance management server 008 searches again for the component replacement corresponding server 001 described later, but the administrator 004 of the corresponding server After confirming from the maintenance reservation date cell 512 in the customer information management table that the reservation has not been made, the maintenance management server 008 calls the corresponding server administrator 004 to the task list of the maintenance worker management server 014 on the day, Instructs you to enter a replacement date reservation.

  If the importance cell 609 of the parts management table is “small”, the customer confirms that the server administrator 004 corresponding to parts replacement has not made a reservation one week after the notification date in parts replacement work described later. After confirming from the maintenance reservation date cell 512 of the information management table, the maintenance management server 008 calls the corresponding server administrator 004 to the task list of the maintenance worker management server 014 and inputs the part replacement date reservation. To instruct.

  FIG. 8 is a module management table for managing a driver and firmware update tool corresponding to each system device / optional product in the module database 010. Reference numeral 701 denotes a division cell indicating information on the system apparatus main body or optional items. Reference numeral 702 denotes a model name cell, and reference numeral 703 denotes a part name cell. Reference numeral 704 denotes a software category cell relating to the component, and reference numeral 705 denotes a software version information cell. Reference numeral 706 denotes a latest version cell for registering the latest version information corresponding to the part or category.

  Reference numeral 707 denotes an update necessity cell indicating whether or not the software version needs to be updated. Reference numeral 708 denotes a registration date cell indicating the registration date of the update necessity cell. Reference numeral 709 denotes an update tool name cell indicating an update tool name for updating to the latest version when the software version needs to be updated. Reference numeral 710 denotes an importance cell indicating the importance of performing software update. Reference numeral 711 denotes a reason cell indicating the reason for software update.

  When a new version of a module is added, information corresponding to a new latest version is added. At the same time, for a column of old software version cells, the column is not deleted, the latest version cell is rewritten to the latest version, the update necessity cell 708 is registered with “Y”, and the latest version is stored in the update tool name cell 709. Register the update tool name. Further, in order to reduce the processing work load of the maintenance management server 006, the update necessity cell 707 is registered with “Y”, the corresponding server is searched from the customer information management table, and the corresponding server does not exist. The update necessity cell 707 is rewritten to “−”.

  When the importance cell 710 of the module management table is “large”, when the server administrator 004 corresponding to the software update receives the update notification in the software update operation and does not perform the software update on the day, On the next day, the maintenance management server 008 searches for the corresponding server for software update again. After confirming from the software version cell 307 of the customer information management table that the software version of the corresponding server is not up-to-date, the maintenance management server 008 Calls the corresponding server administrator 004 and instructs to update the software in the task list of the maintenance personnel management server 012 that day.

  When the importance cell 710 of the module management table is “small”, the server administrator 004 corresponding to the software update in the software update operation does not have the latest software version of the corresponding server one week after the notification date. After confirming this from the software version cell 307 of the customer information management table, the maintenance management server 008 calls the corresponding server administrator 004 to the task list on the day of the maintenance staff management server 012 to update the software. To instruct.

  FIG. 9 is a diagram showing an operation flow for updating server configuration information to a customer database when a LAN board is mounted on the server 001 and a hardware configuration change occurs.

  The server administrator 004 or maintenance staff 013 adds a LAN board to the PCI slot of the server 001 (step 801 in FIG. 9). After starting the server 001, the server management software 102 recognizes the added LAN board, and “option” is displayed in the section cell 301 of the server information management table 104, “LANBD01” in the model name cell 302, and “LAN” in the part name cell 304. The information “board”, “driver” in the software category cell 306, and “01” in the version cell 307 are updated (S802) (see the bottom column shown in FIG. 4).

  When there is information added to the server management software 102, the server management console 114 of the management PC 004 communicates with the maintenance management server 008 via the wide area network 016 information on the serial number cell 202 in the basic information management table and server information management. Information from 301 to 306 in the table is packetized and transmitted (S803). The maintenance management server 008 installed in the maintenance company 007 receives the packet (S804). The maintenance management server 008 searches the customer database 009 based on the serial number 402 of the received packet. In the column 515 shown in FIG. 6, the model cell 503 “LANBD01” of the server 001 to which the LAN board is added this time, “driver” in the category cell 505, and “01” in the version cell 506 are additionally registered. Other information cells are automatically input based on the serial number (S805).

  FIG. 10 is a diagram showing a basic form of an operation flow of the maintenance information management system including the maintenance management server when a server maintenance part replacement, software update, and periodic inspection occur in the present embodiment. Next, with reference to FIGS. 10 to 12, the operation flow of the maintenance management system from the search of the corresponding customer server to the completion of the replacement work when the replacement work occurs in the HDD of the server installed at the customer site. However, it will be described below.

  The maintenance management server 008 confirms whether or not update information is necessary with respect to the parts database 012 about the necessity of maintenance work once a day (S901 in FIG. 10). The maintenance management server 008 checks the replacement necessity cell 607 of the parts management table (see FIG. 7) managed in the parts database 012 (S1001 in FIG. 11). It is confirmed that the replacement part cell in the hard disk column 607 of the model name “HDD073” is registered as “Y” (requires replacement) (S1002). Based on the model name “HDDO73”, the maintenance management server 008 searches the model cell in the customer information management table of the customer database 009 for a server corresponding to the model name “HDD073” (S1003).

  It is confirmed whether or not the scheduled maintenance date cell 512 in the column 516 of the model name “HDD073” of the corresponding server is input (S1004). If the scheduled maintenance date has not been registered, the management IP address cell 501 of the customer information management table shown in FIG. The server management console 114 is notified to contact the parts replacement and make a reservation for the date of parts replacement.

  Since the server manager 004 may be absent or the management PC 005 may not be turned on, the maintenance management server 008 refers to the manager email cell 508 of the customer management information and sends an email to the server manager 004. The same content is communicated (S1005). The server administrator 004 accesses the maintenance reservation server 015 and registers a part replacement reservation on a reservation available day (S1006).

  When reservation of the part replacement date of the server 001 is entered in the maintenance reservation server 015, the maintenance management server 008 allocates a schedule to the maintenance staff management server 014 (S1007). The maintenance staff 013 confirms the schedule table of each maintenance staff managed by the maintenance staff management server 014 (S1008 in FIG. 12). On the day of the replacement date, the maintenance staff 013 visits the customer site 003 and performs replacement work (S1009). After completing the replacement work, the server management software 102 in the server 001 recognizes that the hard disk has been replaced, and updates the hard disk information column 308 of the server information management table 104 (S1010).

  When there is information added to the server management software 102, the server management console 114 of the management PC 005 sends the information of the manufacturing number cell 202 and the server information of the basic information management table 103 to the maintenance management server 008 through the wide area network 016. Information from 301 to 306 in the management table is packetized and transmitted (S1011). The maintenance management server 008 searches the customer database 009 based on the received manufacturing number 402 of the packet, and additionally registers “04” in the version cell 506 of the column 516 of the model name cell “HDD073”. Other information cells are automatically input based on the serial number (S1012).

  Next, returning to S901 shown in FIG. 10, the maintenance management server 008 confirms whether or not update information is necessary with the module database 010 about the necessity of maintenance work once a day (S901 in FIG. 10). The maintenance management server 008 checks the replacement necessity cell 707 in the module management table (see FIG. 8) managed in the module database 010 (S1101 in FIG. 13). It is confirmed that the update necessity cell in the BIOS column 707 of the model name “070PD” is registered as “Y” (need to be updated) (S1102).

  The maintenance management server 008 searches for the corresponding server in the customer information management table of the customer database 009 from the model cell, category cell, and version cell to be updated (S1103). Based on the IP address cell 501 of the corresponding server administrator 004, the maintenance management server 008 notifies the server management console 114 screen of the management PC 004 of the administrator 004 of the reason for updating and an instruction to select whether or not to update (S1104). .

  The server administrator 004 selects whether or not to update (S1105). The maintenance management server 008 receives a packet to update from the server management console 114 (S1106). The maintenance management server 008 searches for an update tool from the module data server 011 based on the update tool name in the corresponding module row of the module management table (see FIG. 8) of the module database 010 (S1107). The update tool is sent to the target server via the server management console 114 of the server management PC 005, and the update is automatically executed on the target server (S1108).

  After completing the update, the target server recognizes that the version has been updated, and updates the information in the table managed in the server management software 102 (S1109). The server management software 102 transmits a packet to the maintenance management server 008 at the maintenance base (maintenance company) (S1110). Upon receiving the packet contents, the maintenance management server 008 updates the customer server information in the customer database 009 (S1111) and completes the update.

  Next, returning to S901 shown in FIG. 10, the maintenance management server 008 confirms whether or not the periodic inspection is necessary with respect to the customer database 009 (S901 in FIG. 10). The maintenance management server 008 searches for a server to be inspected one year after the shipment date in the shipment date cell 511 of the customer information management table (see FIG. 6) in the customer database 009 (S1201 in FIG. 15). It is checked whether the shipping date cell is dated one year before today (S1202). If the date is one year ago, the maintenance management server 008 gives an inspection notification and an inspection date reservation instruction on the server management console screen of the management PC 005 based on the administrator IP address cell of the inspection target server. Notification is made (S1202).

  The server administrator 004 determines whether or not to reserve and register the maintenance replacement date in the maintenance reservation server 015 (S1203). Once registered, the maintenance reservation server 915 makes an inspection date reservation and allocates a maintenance staff schedule to the maintenance staff management server 014 (S1204). The maintenance staff checks the schedule table of each maintenance staff managed by the maintenance staff management server 014 (S1205).

  On the day of the inspection, the maintenance staff visits the base of the customer server and performs the inspection work (S1206). After the inspection, the maintenance staff registers the maintenance inspection execution date in the maintenance staff management server 014 (S1207). Next, based on the information registered in the maintenance management server 014, the maintenance management server 008 inputs the maintenance inspection date cell 514 of the customer information management table (see FIG. 6) of the customer database 009.

  As described above, the maintenance information management system according to the embodiment of the present invention solves the problem of performing maintenance work quickly on a plurality of servers so as not to leak hardware maintenance and software maintenance. As such, it has the following characteristics. That is, a maintenance management server is installed on the maintenance side, and the hardware configuration and software version information of multiple servers installed on the customer site (customer side) are dynamically managed in the customer database (that is, the management target) If there is a change in the hardware and software configuration of the server, it is dynamically managed by the maintenance information management system on the maintenance side by active notification from the server side).

  When hardware maintenance, software maintenance, or periodic hardware inspection work occurs, the server that corresponds to the maintenance work is searched based on the customer information managed in the customer database on the maintenance side. The customer server is instructed to schedule hardware maintenance and periodic inspections, and is notified to perform software maintenance work. In this way, in the case of hardware maintenance and periodic inspections, after the server administrator on the customer side makes a reservation with the maintenance reservation server on the maintenance side, the maintenance person on the maintenance side arranges maintenance personnel, Ensure maintenance work. After the maintenance work is completed, the latest version of hardware and software information is updated in the customer database on the maintenance side.

1 is a block diagram showing an overall maintenance system including a maintenance information management system according to an embodiment of the present invention. It is a block diagram of a customer site (customer side) including a maintenance management target server and a management PC according to the present embodiment. It is a figure which shows the basic information management table | surface managed with the server management software in the server of a maintenance management object regarding this embodiment. It is a figure which shows the server information management table | surface managed with the server management software in the server of a maintenance management object regarding this embodiment. It is a figure which shows the content of the packet data transmitted to the maintenance side from the customer side at the time of the information update in the server of maintenance management regarding this embodiment. It is a figure which shows the customer information management table managed with the customer database provided in the maintenance information management system which concerns on this embodiment. It is a figure which shows the components management table managed with the components database provided in the maintenance information management system which concerns on this embodiment. It is a figure which shows the module management table managed with the module database provided in the maintenance information management system which concerns on this embodiment. It is a figure which shows the operation | movement flow which updates the structure information of a server to a customer database, when the change of the hardware configuration of a server regarding this embodiment occurs. It is a figure which shows the basic form of the operation | movement flow of the maintenance information management system including the maintenance management server at the time of the maintenance part replacement | exchange of a server regarding this embodiment, software update, and a periodic inspection having occurred. It is a figure which shows the flow 1 to the completion of replacement | exchange operation | work when the maintenance parts replacement | exchange of the server regarding this embodiment generate | occur | produced. It is a figure which shows the flow 2 to the completion of replacement | exchange operation | work when the maintenance parts replacement | exchange of the server regarding this embodiment generate | occur | produced. It is a figure which shows the flow 1 to the completion of work when the software update of the server regarding this embodiment generate | occur | produces. It is a figure which shows the flow 2 until work completion when the software update of the server regarding this embodiment generate | occur | produces. It is a figure which shows the flow 1 until the completion of an inspection operation in the case where there is a server corresponding to the one-year periodic inspection among servers related to this embodiment. It is a figure which shows the flow 2 until the completion of an inspection operation in the case where there is a server corresponding to the one-year periodic inspection among servers related to the present embodiment.

Explanation of symbols

001 ... Server, 002 ... Server n, 003 ... Customer site, 004 ... Server administrator, 005 ... Management PC, 006 ... Packet data, 007 ... Maintenance company, 008 ... Maintenance management server, 009 ... Customer database, 010 ... Module database , 011 ... Module data server, 012 ... Parts database, 013 ... Maintenance personnel, 014 ... Maintenance personnel management server, 015 ... Maintenance reservation server, 016 ... Wide area network, 101 ... Server, 102 ... Server management software, 103 ... Basic information management Table, 104 ... Server information management table, 105 ... RAID board, 106 ... CPU, 107 ... Memory, 108 ... BIOS, 109 ... OS, 110 ... RAID board driver, 111 ... RAID board F / W, 112 ... Communication cable, 113 ... Management PC, 114 ... Service Management console, 201 ... server model name cell, 202 ... serial number cell, 203 ... OS type cell, 301 ... section cell, 302 ... model name cell, 303 ... part model name cell, 304 ... part name cell, 305 ... detailed information cell, 306 ... software category cell, 307 ... software version cell, 308 ... information content when replacement work occurs, 401 ... maintenance management server IP address, 402 ... server serial number, 403 ... server update Additional information 404 ... IP packet data, 501 ... IP address cell of administrator PC, 502 ... Production number cell, 503 ... Model name cell, 504 ... Part type name cell, 505 ... Software category cell, 506 ... Software version cell, 507 ... Customer name cell, 508 ... Administrator email address cell, 509 ... Electricity Number cell, 510 ... Address cell of customer site, 511 ... Server shipping date cell, 512 ... Scheduled maintenance date cell, 513 ... Scheduled periodic inspection date cell, 514 ... Periodical inspection implementation date cell, 515 ... When server information is changed 516 ... Information content when replacement work occurs, 601 ... Division cell, 602 ... Model name cell, 603 ... Part type name cell, 604 ... Part name cell, 605 ... Version cell, 606 ... Latest version cell 607 ... Replacement necessity cell, 608 ... Registration date cell, 609 ... Importance cell, 610 ... Reason cell, 611 ... Information content when exchange work occurs, 701 ... Partition cell, 702 ... Model name cell, 703 ... Component name cell, 704 ... Software category cell, 705 ... Software version cell, 706 ... Latest software version cell, 70
7 ... Update necessity cell, 708 ... Registration date cell, 709 ... Update tool name cell, 710 ... Importance cell, 711 ... Reason cell,

Claims (6)

Communication between a customer site having a plurality of servers to be subjected to maintenance management, a maintenance site having a maintenance management server for maintenance management of hardware configuration or software version information in the server, and communication between the customer site and the maintenance site A maintenance management system comprising a network for performing
The server at the customer site manages its own hardware configuration and software version information, and notifies the maintenance management server via the network when a change in the hardware configuration and the software version information occurs,
The maintenance management server of the maintenance site manages the hardware configuration and the software version information notified from the server in a customer database storing various customer information,
Further, the maintenance management server schedules the hardware maintenance or the hardware periodic inspection based on the customer information of the customer database when the hardware maintenance or the hardware periodic inspection or the software update of the server occurs. Instruct the appropriate server or notify the appropriate server whether or not to select the software update,
When the server that is instructed to make a reservation or is notified of whether or not to select the software update, executes the reservation for the maintenance management server or selects the update, the maintenance management server can execute the hardware of the server. An overall maintenance management system characterized by performing work for hardware maintenance or periodic hardware inspection, or performing software updates. A maintenance information management system comprising a maintenance management server for maintaining and managing hardware configuration or software version information in a plurality of servers subject to maintenance management,
The maintenance management server receives, from the server, information in which the hardware configuration and software version information of the server itself are changed, and the changed hardware configuration and software version information are stored in the customer in which various customer information is stored. Managed in the database,
Further, the maintenance management server schedules the hardware maintenance or the hardware periodic inspection based on the customer information of the customer database when the hardware maintenance or the hardware periodic inspection or the software update of the server occurs. Instruct the appropriate server or notify the appropriate server whether or not to select the software update,
The maintenance management server performs a work for hardware maintenance or periodic hardware check of the server or executes software update according to a response of execution of reservation or update by the server. Maintenance information management system. In claim 2,
The maintenance information management system provides a parts database for storing information about various parts provided in the server,
The maintenance management server acquires information on parts that require hardware maintenance from the parts database, searches for a server corresponding to hardware maintenance from customer information in the customer database, and corresponds to the reservation for hardware maintenance. A maintenance information management system characterized by instructing the server. In claim 1 or 2,
The maintenance information management system is provided with a module database for storing information on various software provided in the server,
The maintenance management server acquires information on software that needs software update from the module database, searches a server corresponding to software update from customer information in the customer database, and determines whether the software update can be selected or not. A maintenance information management system characterized by notification. In claim 1, 2 or 3,
In the customer information of the customer database, information related to the hardware periodic inspection in the server is provided,
The maintenance management server acquires hardware information that requires periodic hardware inspection from the customer database, searches for a server corresponding to periodic hardware inspection from customer information in the customer database, and performs the periodic hardware inspection. A maintenance information management system characterized by instructing the relevant server to make a reservation. In claim 2,
The maintenance information management system includes a maintenance staff management server for managing a maintenance staff schedule, and a maintenance reservation server for registering a reservation date for hardware maintenance work.
The maintenance management server performs maintenance management of maintenance personnel by allocating a maintenance staff schedule to the maintenance staff management server based on information on a maintenance work reservation date registered in the maintenance reservation server. Maintenance information management system.

Images