JP2010157164A - Device and method for designning wiring, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform the wiring of a cable with optimal length on the basis of a created rack loading figure for quickly and accurately creating the lack loading figure in a short time. <P>SOLUTION: The wiring design device includes: a storage means for storing equipment management information for identifying equipment, the loading position information of a rack for loading equipment, and connection information showing a connection relation between equipment; a cable length calculation means for calculating the length of a cable connecting equipment according to the loading position information of the rack; a formation means for forming a rack figure showing the setting position of the equipment of the rack; and an arrangement means for arranging the equipment in the rack figure formed by the formation means from the equipment management information and the loading position information of the rack stored in the wiring storage means. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a wiring design method for rack mounting of information processing system equipment, and more particularly to a wiring design apparatus for accurately arranging information processing system equipment by automatically calculating design values for wiring essential for rack mounting. It is.

With the recent introduction of IT, the number of servers installed in data centers and server rooms continues to increase. A large number of cables such as a power source, LAN, SCSI / fiber, console, and serial are connected to the server mounted on the rack, and the back of the rack is very complicated. Server layout and cable wiring are closely related to heat generation that causes failures and downtime during maintenance, so appropriate design is required. As an appropriate design method, Patent Document 1 provides a mechanism for reducing the work impossibility at the time of construction by reading and comparing the real system configuration and the virtual system configuration in the Storage Area Network (SAN) system. Yes. Further, Patent Document 2 provides a mechanism for automatically generating a network physical configuration diagram.
JP 2007-250006 JP 2004-171330 A

  However, in Patent Document 1, the work necessary for the actual system configuration, that is, the generation of the calculation of the cable necessary for the physical connection between the devices has not been reached. There is no description about connection with peripheral devices other than SAN.

  In Patent Document 2, only a physical configuration diagram is created, and calculation of a cable necessary for physical connection between devices has not been generated. In addition, there is no description regarding connection with a peripheral device of a local area network (LAN).

  In order to solve the above-described problem, the wiring design apparatus according to claim 1 is characterized in that device management information for identifying a device, rack mounting position information for mounting the device, and a connection indicating a connection relationship between the devices. Wiring information storage means for storing information, and cable length calculation means for calculating a cable length for connecting the devices according to the rack mounting position information with respect to the equipment management information stored by the wiring information storage means. The rack diagram formed by the forming means from the forming means for forming the rack diagram showing the position for setting the equipment of the rack, the equipment management information and the rack mounting position information stored by the wiring storage means And an arrangement means for arranging the device.

  According to the present invention, it becomes possible to create a rack mounting diagram in a short time and accurately, so that a cable having an optimal length can be wired based on the created rack mounting diagram. It is possible to minimize downtime at the time of failure or maintenance.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a configuration diagram showing a schematic configuration of a wiring design apparatus according to an embodiment of the present invention.

  The wiring design apparatus 100 executes a program in a computer main body 102 having a program stored in advance to realize a schedule function for performing work management, a keyboard 104 for inputting data, etc., and the computer main body 102. The display 106 for displaying the result obtained is provided.

  Further, in the computer main body 102, an FDU, a CD-ROM device, a CD-RAM device, a DVD-ROM device, a DVD-RAM device in which an FD, CD, DVD, MD, MO as a storage medium can be inserted or removed. MD device, MO device, and the like are stored in advance in a storage medium, and the processing program is stored in the mass storage device by inserting the storage medium into each device. Etc. may be executed.

  Next, the hardware configuration of the wiring design apparatus 100 of FIG. 1 will be described with reference to FIG.

  FIG. 2 is a diagram illustrating a hardware configuration of the wiring design apparatus 100.

  The CPU 201 comprehensively controls each device and controller connected to the system bus 204. Further, the ROM 202 or the external memory 211 has a BIOS (Basic Input / Output System), an operating system program (hereinafter referred to as OS), which is a control program of the CPU 201, and a function necessary for realizing the function executed by the scheduling device 100, which will be described later. Various programs to be stored are stored.

  The RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program.

  An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown). A video controller (VC) 206 controls display on a display device such as a CRT display (CRT) 210. The display device may be a liquid crystal display as well as a CRT.

  The memory controller (MC) 207 is connected via an adapter to a hard disk (HD), FD or PCMCIA card slot for storing boot programs, browser software, various applications, font data, user files, editing files, various data, etc. The access to the external memory 211 such as a compact flash memory is controlled.

  A communication I / F controller (communication I / FC) 208 is connected to and communicates with an external device via a network, and executes communication control processing in the network. For example, Internet communication using TCP / IP is possible. Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  A program related to the wiring design method for realizing the present invention is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 202 as necessary. Furthermore, definition files and various information tables used by the program according to the present invention are stored in the external memory 211, and detailed descriptions thereof will be described later.

  FIG. 3 is a flowchart showing device information fetch processing in the wiring design apparatus according to the embodiment of the present invention. Note that the processing in each step is controlled and executed under the control of the CPU 201.

  In step S100, it is determined whether or not the device information import button has been pressed. If it is detected that the button has been pressed, the process proceeds to step S102. The device information capture button is the device information capture button shown in FIG. The device information import button on the screen is shown.

  In step S102, it is recognized that a device information file is selected. This device information file is stored in the external memory 211. In addition, a method for selecting and selecting a path by operating the keyboard 209 for the storage area of the external memory 211 in which the device information file to be selected is stored, or the configuration of the storage area of the external memory 211 in the CRT 210 It is also possible to use a method of displaying and specifying from there.

  In the next step S104, the device information file selected in step S102 is expanded in the RAM 203. As shown in FIG. 5, the device information file is a ReadMe indicating how to use the device information file, a device information file change history, server device information, storage device information, network device information, power supply device information, The device is configured to include other device information, and the details of the device information set in the device information file can be acquired. (See Figure 6)

  6 is a device information detail file that stores the contents of the device information for each of the server device information, storage device information, network device information, power supply device information, and other device information shown in FIG. Stored in the external memory 211. This device information detail file includes an item number for uniquely identifying a device, a machine type representing the device type, a device name representing the device name, a U number representing the number of units in the rack, and a rack mounted Arm length / arm length / cable length indicating the cable extra length.

  In step S106, the server device information is read from the device information detailed file and stored in the RAM 203. In step S108, the server device information stored in RAM 203 in step S106 is displayed in the server device information column of the device information import screen shown in FIG. The detailed processing in this step will be described later with reference to FIG.

  In step S 110, the storage device information is read from the device information detail file and stored in the RAM 203. In step S112, the storage device information stored in RAM 203 in step S110 is displayed in the storage device information column of the device information import screen shown in FIG. The detailed processing in this step will be described later with reference to FIG.

  In step S114, the network device information is read from the device information detail file and stored in the RAM 203. In step S116, the network device information stored in RAM 203 in step S114 is displayed in the storage device information column (not shown) of the device information fetch screen shown in FIG. The detailed processing in this step will be described later with reference to FIG.

  In step S118, the power supply device information is read from the device information detail file and stored in the RAM 203. In step S120, the power supply device information stored in RAM 203 in step S118 is displayed in the power supply device information column (not shown) of the device information fetch screen shown in FIG. The detailed processing in this step will be described later with reference to FIG.

  In step S122, other device information is read from the device information detail file and stored in the RAM 203. In step S124, the power supply device information stored in RAM 203 in step S120 is displayed in the other device information column (not shown) of the device information fetch screen shown in FIG. The detailed processing in this step will be described later with reference to FIG.

  It is possible to refer to the network device information column, the power device information column, the other device information column, and the like by operating the scroll bar in the lower right column of the device information import screen shown in FIG.

  In the next step S126, the device information file and the device information detail file developed in the RAM 203 in step S104 are closed, and in step S128, a processing end message is displayed and the processing ends. As an example of the message, the message shown in FIG. 8 is displayed, and when the OK button is pressed, the process is terminated.

  Next, FIG. 7 is a flowchart showing in detail the process of reading information from the device information file and the device information detail file and displaying the read information in the device information column of the device information import screen shown in FIG. .

  This processing is displayed in each device information column shown in FIG. 4 according to the processing of each device information in step S108, step S112, step S116, step S120, and step S124.

  In step S130, the item serial number set for the item number item in the device information detailed file is read. In step S132, if the item serial number does not exist in step S130, the process ends, and the item serial number is terminated. If exists, the process proceeds to step S134.

  In step S134, the item serial number read in step S130 is displayed as a management number on the device information import screen. For example, in the case of processing for server device information in step S108, the management number is displayed in the GsvNo column of the server device information column shown in FIG. 4, and in the case of processing for storage device information in step S112, FIG. The management number is displayed in the GstNo column of the storage device information column.

  In step S136, the device type set for the machine type item is read. In step S138, the device type read in step S136 is displayed in the machine type (MT) column shown in FIG.

  In step S140, the model name set for the model name item is read. In step S142, the model name read in step S140 is displayed in the model name column shown in FIG.

  In step S144, the number of equipment units at the time of rack mounting set for the item of U number is read. In step S146, the number of equipment units read in step S144 is displayed in the U number column shown in FIG. .

  In step S148, the arm length / cable length at the time of rack mounting set for the arm length / extra length item is read. In step S150, the arm length or extra length column shown in FIG. 4 is read in step S148. Displays the arm length / cable length.

  In the next step S152, the next record is read, and when this step is completed, the process returns to step S130.

  FIG. 9 is a flowchart showing a cable length calculation process in the wiring design apparatus according to the embodiment of the present invention. Note that the processing in each step is controlled and executed under the control of the CPU 201.

  In step S200, it is determined whether the necessary information collection button has been pressed. If it is detected that the button has been pressed, the process proceeds to step S202. The necessary information collection button indicates a necessary information collection button on the necessary information collection screen shown in FIG.

  The necessary information collection screen displays the LANo representing the cable management number for managing the cables for connecting the devices, the Japanese name representing the Japanese name of the connection target device, and the host representing the name of the host of the connection target device Name, the port that represents the name of the port to be connected, the extra length to be considered when routing the cable, the cable that represents the type of cable, the color that represents the color information when wiring a colored cable, and the cable that is required for wiring If the order unit is determined when ordering the cable to the customer and the required length that represents the length of the order, the order length that represents the value obtained by correcting the above-mentioned necessary length to the order unit (for example, the required length is in units of 1 meter) Etc.).

  The items LANo, Japanese name, port, extra length, and cable are preset by the user.

  In addition, a Japanese name, a host name, and a port are displayed in pairs, and this indicates a correspondence relationship that is connected using a cable.

  In step S202, the information set in the LANo item preset in the LAN cable column of the necessary information collection screen is read. In step S204, the cable management number set in the LANo item in step S202. If it exists, the process proceeds to step S208. If not, the process proceeds to step S206. In step S206, a message (not shown) for ending the process is displayed, and then the process ends.

  In step S208, information set in the item of Japanese name is read. In step S210, it is determined whether or not the Japanese name of the connection target device exists in the item of Japanese name. Advances the process to step S212, and if not, advances the process to step S226.

  In step S212, the information set in the port item is read. In step S214, it is determined whether or not the port name of the connection target device exists in the port item. If it exists, the process proceeds to step S216. If the process does not exist, the process proceeds to step S226.

  In step S216, the information set in the cable item is read. In step S218, it is determined whether the cable type exists in the cable item. If there is, the process proceeds to step S220. If not, the process proceeds to step S226.

  Next, in step S220, the host name corresponding to the Japanese name read in step S208 is read. As a reading method, the host name of the mounted device information screen of the record in which the Japanese name read in step S208 matches the Japanese name set in the mounted device information column of the mounted device information screen shown in FIG. Read. After reading, in step S222, the host name read in step S220 is set in the host name field of FIG.

  In step S224, the device name corresponding to the Japanese name read in step S208 is read. As a reading method, the device name on the mounted device information screen of the record in which the Japanese name read in step S208 matches the Japanese name set in the mounted device information column of the mounted device information screen shown in FIG. Is acquired, and a surplus length corresponding to the model name displayed on the device information fetch screen corresponding to the device name is acquired.

  In step S226, an error message (not shown) indicating that it does not exist is displayed, and the process ends.

  In step S228, RaNo corresponding to the Japanese name read in step S208 is read. As the reading method, the rack name on the mounted device information screen of the record in which the Japanese name read in step S208 matches the Japanese name set in the device information column of the mounted device information screen shown in FIG. Read the RaNo from the rack information record that matches the read rack name, and compare whether the RaNo of the two read devices is the same.

  If the rack names are different, the process proceeds to step S230. If the rack names are the same, the process proceeds to step S240. Here, “2” is described as the Japanese name and the host name are set for the pair on the necessary information collection screen shown in FIG. 11, and the combination of the pair is described.

  In step S230, it is determined whether the cable is passed between the racks from above or between the racks (for example, under the floor depending on the environment). This determination is made based on information preset in the cable position between racks on the necessary information collection screen (see FIG. 11).

  If it passes from the top between the racks, the process proceeds to step S246, and if it passes through the bottom between the racks, the process proceeds to step S232.

  In step S232, the inter-rack cable position designated by the user is read in advance, and a condition is determined as to whether the cable position passing between the racks is below the racks in the rack.

  In step S234, the right two digits of RaNo read in step S228 are extracted assuming that the cable position passing between the racks is below the rack (free access). Subtract the right two digits of RaNo of two devices to find the absolute number. The absolute number obtained here is the number of racks between devices.

  In step S236, in the case of another rack, between racks (free access), and when the number of racks is 2 or more, the number of racks between the devices obtained in step 234 and the distance between racks described in advance in the program are fixed. The value is used to calculate the distance between racks (lateral direction). There are two types of fixed values for the distance between racks, a long distance including the extra length and a normal distance between racks. The result of adding the normal distance between racks to the long distance including the extra length Is multiplied by a value obtained by subtracting 1 from the number between racks.

  Also, the position (U) corresponding to the Japanese name read in step S208 is read from the mounted device information on the mounted device information screen shown in FIG. Based on the number of U on which the device is mounted, the distance between the rack base and the mounting position of both devices is calculated in U number conversion. The U distance (vertical direction) is calculated by using a fixed value of the U distance previously described in the program for the calculated U number. The calculated rack-to-rack distance and U-to-U distance are summed to calculate the cable length between devices.

  In step S238, if another rack is under the rack (free access) and the number of racks is 1, the position (U) corresponding to the Japanese name read in step S208 is displayed on the mounted device information screen shown in FIG. Read from the information of installed devices. Based on the number of U on which the device is mounted, the distance from the rack base to the mounting position of both devices is calculated in U number conversion. The distance between U (vertical direction) is calculated using the fixed value of the distance between U previously described in the program for the calculated U number. The cable length between devices is calculated by summing the calculated distance between racks and the fixed value of the distance between racks (lateral direction) described in advance in the program.

  In step S240, it is determined whether the drop-up directions are the same. This determination is made based on information set at the cable position in the rack on the necessary information collection screen.

  If the drop direction is the same, the cable length between U can be calculated with the shortest distance, but if the drop direction is different, the cable is once dropped from the target device A to the bottom of the rack and then pulled up to the target device B. Therefore, the cable length calculation method is different.

  If the drop direction is the same, the process proceeds to step S242, and if the drop direction is different, the process proceeds to step S244.

  In step S242, the position (U) corresponding to the Japanese name read in step S208 is read from the mounted device information on the mounted device information screen shown in FIG. Two devices are subtracted using the number of U mounted on each device to obtain an absolute value. The absolute value calculated here is the U number between the two devices. The inter-U distance is calculated using a fixed value of the inter-U distance previously described in the program for the calculated inter-device U number. The value calculated here is the cable length between devices.

  In step S244, the position (U) corresponding to the Japanese name read in step S208 is read from the mounted device information on the mounted device information screen shown in FIG. Since the number of U devices mounted is counted from the rack base, the number of mounted U devices of the two devices is added. The distance between U (vertical direction) is calculated using the fixed value of the distance between U previously described in the program for the value calculated here. The calculated U-to-U distance and the rack width (described as a fixed value in the program) are added to calculate the cable length.

において読込んだ日本語名に対応する位置（Ｕ）を図１３の搭載機器情報画面の搭載機器情報より読込。さらに、ステップ２０８で読み込んだラック名と一致するラック情報のレコードよりＵ数を読込。

The position (U) corresponding to the Japanese name read in is read from the mounted device information on the mounted device information screen of FIG. Further, the U number is read from the rack information record that matches the rack name read in step 208.

  The position (U) is subtracted from the read U number, and the U number to the upper part between the racks is calculated. Add the number of U to the upper part between two racks, and calculate the distance between U (vertical direction) using the calculated value and the fixed value of the distance between U described in advance in the program .

  Extract the right two digits of RaNo read in step S228. By subtracting the two right-hand digits of RaNo of two devices and obtaining the absolute number, the number of devices between racks is obtained.

  The distance between racks (lateral direction) is calculated using the number of racks between devices and a fixed value of the distance between racks described in advance in the program. There are two types of fixed values: a long distance including the extra length and a normal distance between racks. In this calculation, the normal distance between racks is used. Calculated by multiplying the normal distance between racks by the number of racks. The calculated U-to-U distance and rack-to-rack distance are summed to calculate the cable length between devices.

  In step S248, in the case of another rack and between the racks (inside the rack), the position (U) corresponding to the Japanese name read in step S208 is read from the mounted device information on the mounted device information screen in FIG. Two devices are subtracted using the number of U mounted on each device to obtain an absolute value. The absolute value calculated here is the U number between the two devices. The inter-U distance (vertical direction) is calculated using a fixed value of the inter-U distance described in advance in the program for the calculated inter-device U number.

  The distance between racks (lateral direction) is calculated using the number of racks between the devices obtained in step 234 and the fixed value of the distance between racks described in advance in the program. There are two types of fixed values: a long distance including the extra length and a normal distance between racks. In this calculation, the normal distance between racks is used. Calculated by multiplying the normal distance between racks by the number of racks. The calculated U-to-U distance and rack-to-rack distance are summed to calculate the cable length between devices.

  In step S250, the extra length corresponding to the Japanese name read in step S208 is read from the necessary information collection screen, and the cable length calculated in step S236, step S238, step S242, step S244, step S246, or step S248 is obtained. to add.

  In the next step S252, a process for calculating the order length by correcting the cable length calculated in step S250 to the order unit is performed. In this embodiment, rounding up is performed in units of 1M.

  Thereafter, in step S254, the cable color is determined based on the port read in step S212. In the program, a color corresponding to the port number is determined in advance, and if applicable, that color becomes the cable color. Otherwise, if the port number is not a number, the other established color is the cable color.

  In step S256, the color determined in step S254, the cable length calculated in step S250, and the order length calculated in step S252 are set for each of the necessary information screen color, required length, and order length.

  In step S258, the next record displayed in the LAN cable column of the necessary information collection screen is read, and the process returns to step S202.

  FIG. 12 is a flowchart showing processing for creating a rack mounting diagram in the wiring design apparatus according to the embodiment of the present invention. Note that the processing in each step is controlled and executed under the control of the CPU 201.

  In step S300, it is determined whether or not the rack diagram creation button has been pressed. If it is detected that the button has been pressed, the process proceeds to step S302. The rack diagram creation button indicates the rack diagram creation button on the mounted device information screen shown in FIG.

  The mounted device information screen includes, as rack information, a RaNo that represents a management number for uniquely identifying and managing a rack, a rack name that represents the name of the rack, a U number that represents the number of units of the device mounted in the rack, As mounted device information, a device management number McNo that uniquely identifies a device, a device classification that represents the device type, a device name that represents the name of the device, and a position (U) that represents where the device is mounted in the rack , A rack name on which the device is mounted, a Japanese name representing the Japanese name of the device, and a host name representing the host name of the device.

  Next, in step S302, a rack diagram creation sheet as shown in FIG. 14 is created. After creation, in step S304, the rack management number set in the rack information column of the mounted device information screen, that is, the information set in the RaNo item is read, and in step S306, the rack set in the RaNo item. It is determined whether or not the management number exists. If it exists, the process proceeds to step S308, and if it does not exist, the process ends.

  In step S308, the information set in the item of U number set in the rack information column of the mounted device information screen corresponding to the rack management number read in step S304 is read. In the next step 310, step S308 is read. An array for the number of Us read in step (hereinafter referred to as device mounting identification array) is created.

  In step S312, the cells in the rack drawing creation sheet are shaped.

  In step S314, the information set in the device management number item set in the mounted device information column of the mounted device information screen is read, and in the next step S316, the device management set in the mounted device information column. If the number exists, the process proceeds to step S318, and if not, the process proceeds to step S336.

  In step S318, the information set in the rack name item set in the mounted device information column of the mounted device information screen is read. In the next step S320, the rack name set in the mounted device information column is read. Then, it is determined whether or not the rack diagram is to be created.

  In this determination, it is determined whether or not the rack name set in the column of mounted device information is the same as the rack name corresponding to the RaNo read in step S304. If they are the same, the process proceeds to step S322. If they are different, the process proceeds to step S334.

  In the next step S322, the information set in the device name item set in the mounted device information column of the mounted device information screen is read, and in the next step S324, the position (U) is read. Then, in the next step S326, it is determined whether or not the equipment is mounted so as to protrude from the uppermost part and the lowermost part of the rack.

  This determination is made by comparing the U number read in step S308 with the position (U) read in step S324. If the position (U) is larger or smaller than the U number, It is determined that the device is mounted so as to protrude from the bottom. If the device does not protrude, the process proceeds to step S328. If the device protrudes, the process proceeds to step S340.

  In step S328, it is determined whether information matching the position (U) read in step S324 is already stored for the device mounting identification array. That is, it is determined whether or not another device is mounted at the rack mounting position. If information matching the position (U) has already been stored, the process proceeds to step S340, and if not already stored, the process proceeds to step S330.

  In step S330, the device name read in step S322 is set in the column where the value shown in the left column of the rack diagram shown in FIG. 14 matches the position (U) read in step S324, and the next step In S332, the value of the position (U) is stored for the device mounting identification array.

  In step S334, the next record set in the mounted device information column on the mounted device information screen is searched, and the process proceeds to step S314.

  In step S336, the ruled lines around the rack diagram shown in FIG. 14 are drawn. In step S324, the next record set in the rack information column of the mounted device information screen is searched, and the process proceeds to step S304.

  In step S340, an error message is output and the process ends.

  As described above, according to the present embodiment, it becomes possible to create a rack mounting diagram in a short time and accurately, so that a cable having an optimal length can be wired based on the created rack mounting diagram. Administrators can minimize downtime during failures and maintenance.

  For example, in order to suppress wiring mistakes caused by excess or deficiency of equipment mounting information when mounting equipment on equipment mounting racks in Internet data centers, etc., by displaying a list of accurate equipment mounting information in advance, Wiring to the mounting position of each device can be performed appropriately.

  It is also possible to design a wiring according to the type of cable such as a LAN cable between devices, a Fiber Channel (hereinafter referred to as FC) cable, an AC cable, and a Console Switch (hereinafter referred to as CS) cable.

  Further, in the present embodiment, the form performed by a single computer has been described, but the present invention is not limited to this form. It is also possible to adopt a configuration of a client server system in which data to be displayed on each screen is stored in a recording medium such as a database or file on the server side and used as appropriate.

  Further, the present invention can take an embodiment as, for example, a method and a program or a recording medium recording the program.

It is a block diagram which shows the system configuration | structure of the wiring design apparatus which concerns on embodiment of this invention. It is a block diagram which shows the hardware constitutions of the wiring design apparatus which concerns on embodiment of this invention. It is a flowchart which shows the process which takes in the information of each apparatus of the wiring design apparatus which concerns on embodiment of this invention. It is a block diagram which shows an example of the apparatus information acquisition screen used in order to acquire the apparatus information which concerns on embodiment of this invention. In an embodiment of the present invention, it is a lineblock diagram showing an example of a device information file for memorizing a kind of device made into a candidate for reading device information. In an embodiment of the present invention, it is a lineblock diagram showing an example of a device information detailed file for memorizing detailed information on a device. It is a flowchart which shows the process for displaying the data read from the apparatus information detailed file in embodiment of this invention on an apparatus information acquisition screen. It is a block diagram which shows an example of the screen which notifies that all the apparatus information was taken in in embodiment of this invention. It is a flowchart which shows the process for calculating cable length in embodiment of this invention. It is a flowchart which shows the process for calculating cable length in embodiment of this invention. It is a block diagram which shows an example of the required information collection screen which shows the connection relation of an apparatus and the relationship between the cable length in embodiment of this invention. It is a flowchart which shows the process which produces a rack figure in embodiment of this invention. It is a block diagram which shows an example of the mounting apparatus information screen which shows the relationship between an apparatus and the rack mounted in embodiment of this invention. It is the block diagram which showed an example of the rack figure in embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Wiring design apparatus 102 Computer main body 104 Keyboard 106 Display 201 CPU
202 ROM
203 RAM
204 System bus 205 Input controller 206 Video controller 207 Memory controller 208 Communication I / F controller 209 Keyboard 210 CRT
211 External memory

Claims (1)

Wiring information storage means for storing equipment management information for identifying equipment, rack mounting position information for mounting the equipment, and connection information indicating a connection relationship between the equipment;
Cable length calculation means for calculating the cable length for connecting between the devices according to the rack mounting position information for the equipment management information stored by the wiring information storage means,
Forming means for forming a rack diagram showing positions for setting the equipment of the rack;
Arrangement means for arranging the equipment in a rack diagram formed by the formation means from equipment management information stored in the wiring storage means and rack mounting position information;
A wiring design apparatus comprising:

Images