JP2006040302A - Communication network system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow a manager to correctly recognize, on a display screen of a management device, a configuration and status of a device to be managed with accuracy equivalent to the case where he or she goes down to the actual device. <P>SOLUTION: In a network management device 10, an acquisition request is transmitted to the device 20 to be managed having an IP address designated by using an input part 103 by the manager; and configuration/status management information of the device 20 to be managed which is transferred from the device 20 to be managed in response to the acquisition request is received by a management protocol 105d and managed by management middleware 105c. A screen display application 105b renders, on a display part 104, the configuration and status of the device 20 to be managed of the acquisition source in an actual-device image identical with the case where the configuration and status of the device 20 to be managed are actually viewed based on the configuration/status management information acquired by the middleware 105c. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a communication network system in which one or a plurality of communication devices and a network management device that manages the communication devices are connected by a communication path, and more particularly, a failure, configuration, or operation of the communication device in the network management device. The present invention relates to an improvement in control for displaying a state or the like on a display screen.

  For example, in the field of railroad management systems and road management systems, a network configuration is known in which a plurality of communication devices are distributed and information is collected and managed by a management center. In this type of system, for the purpose of network maintenance management, for example, a network management device is arranged in the network, and the network management device acquires various types of information from each managed communication device (managed device). Some of them have a function of displaying the management result on the display screen based on the acquired information.

  Here, as information acquired from the managed device by the network management device, for example, there is information related to the failure of the managed device. In general, the information regarding the failure of the managed device is acquired by the autonomous notification from each managed device, and the information regarding the failure for each managed device is displayed based on the autonomous notification. With regard to this autonomous notification display, for example, the network management device has a method of displaying an autonomous notification character that is autonomously notified from the managed device as it is. In this method, since the autonomous notification characters are simply listed on the display screen, there is a tendency for the administrator to recognize the occurrence of the failure of the managed device.

  As a countermeasure against this point, conventionally, an icon representing a managed device is prepared, and the color representing the occurrence of the failure is reflected on the icon of the corresponding managed device based on the autonomous notification of the failure occurrence from each managed device. There was a method. In this method, each managed device is captured as an icon, and the failure state is captured by a change in the color of the icon, so that the administrator recognizes the failure of the managed device compared to the case where only the autonomous notification character is displayed. Can be shortened. However, regarding the autonomous notification display using this icon, conventionally, for example, as shown in Patent Document 1 below, it is possible to restore the failure only by reflecting the color indicating the failure occurrence on the icon representing the managed device. The representing color was not reflected, and the administrator took time to know about the failure recovery.

In addition, information acquired from the managed device by the network management device includes information on the configuration of the managed device and the operation state when this configuration is assumed. With respect to the screen display related to the configuration and status of the managed device, conventionally, a simple graphic (for example, a square or the like) representing the substrate mounted on the managed device or the display related to the configuration using the icons as described above is used. ) Was still displayed. According to this method, the display contents on the display screen of the network management device are largely different from the actual image of the managed device, so the administrator cannot accurately grasp the configuration and status of the managed device, and maintenance There was a risk of confusion in administrative work.
JP-A-5-56043

  As described above, regarding the screen display on the network management device related to the configuration and state of the managed device, conventionally, the configuration is represented using the icon of the managed device or the board mounted on the managed device is simply represented. However, the contents of such changes were not reflected on the display screen in accordance with the increase or decrease of the substrate. In this method, since the display content is far from the actual image of the managed device, there is a risk that the administrator cannot accurately recognize the configuration and state of the managed device, causing confusion in maintenance management work. In addition, there is a problem that the state of the change cannot be grasped every time the configuration and state change.

  The present invention eliminates the above-mentioned problems, and the administrator can accurately recognize the configuration and state of the managed device on the display screen of the management device with the same accuracy as when actually going to the actual machine. It is an object of the present invention to provide a communication network system that can grasp changes at any time and prevent confusion in maintenance work.

  In order to achieve the above object, the invention described in claim 1 is a communication network system in which a communication device and a management device for managing the communication device are connected by a communication path. State monitoring means for detecting an operation state including occurrence of failure or recovery from failure, and autonomous management means for autonomously managing configuration / state management information relating to the state of the apparatus and the state related to the configuration detected by the state monitoring means; And a managed processing means for transferring the configuration / state management information to the management device according to a predetermined protocol in response to an acquisition request from the management device, and the management device sends the acquisition to the managed device. A request is sent, and the configuration / state management information transferred from the managed processing means in response to the acquisition request is acquired and managed by the predetermined protocol. Based on the management processing means and the configuration / state management information acquired by the management processing means, the configuration and state of the source communication device are the same real machine images as when the configuration and state of the communication device are actually viewed. And a configuration / state display processing unit for drawing on the display unit.

  According to a second aspect of the present invention, in the first aspect of the invention, the management device includes an address designation unit that designates an address of a communication device from which the configuration / state management information is acquired, and the management processing unit Sends the acquisition request to the communication device corresponding to the address designated by the address designation means.

  According to a third aspect of the present invention, in the first or second aspect of the present invention, in the communication device, the autonomous management unit is configured to perform fault management based on the occurrence or failure recovery of the own device detected by the state monitoring unit. Further managing information, the managed processing means autonomously notifies the management apparatus of the failure management information managed by the autonomous management means by the predetermined protocol when a failure occurs or recovers from the own apparatus The management device assigns a device icon corresponding to the communication device that is the transmission source of the autonomous notification based on the failure management information acquired from the communication device corresponding to the autonomous notification at the time of occurrence or failure recovery of the failure. It further includes an autonomous notification display processing means for displaying in a color indicating occurrence or recovery, and the management processing means is connected to the autonomous notification display processing means. Wherein the sending the acquisition request to the communication device corresponding to the selected device icon in response to the selection operation of the displayed device icon Ri.

  According to a fourth aspect of the present invention, in the management device according to any one of the first to third aspects, the management processing means periodically acquires the configuration / state management information from the communication device, The configuration / status display processing means updates and displays the image image being displayed on the display means as needed based on the acquired configuration / status management information.

  According to a fifth aspect of the present invention, in the communication device according to any one of the first to fourth aspects of the present invention, the autonomous management means includes an inside of a substrate mounted on the communication device as the configuration / state management information. Status information, main power operating status, system operating status, alarm status, fan operating status, temperature, contact alarm status information, and in the management device, the configuration / status display processing means is connected to the communication device. In addition to displaying the same board appearance structure as when the board is actually viewed, the board internal status, main power supply operating status, system operating status, alarm status, fan operating status, temperature, contact alarm status Is displayed together with the substrate appearance structure image display by color.

  According to the present invention, in the management device, information regarding the configuration of the managed device and the state based on the configuration is acquired from the managed device, and the configuration and state of the acquisition source managed device are based on the acquired information based on the acquired information. Since the image is displayed as it is on the display screen, the administrator can accurately recognize the configuration and status of the managed device from the display content on the display screen with the same accuracy as when going to the actual machine. It can prevent confusion in management work.

  In addition, according to the present invention, the management device periodically acquires the configuration information and status information of the managed device from the managed device, and if there is a change and the previously acquired content, the change is displayed on the display screen. Therefore, the administrator can grasp the change in the configuration and state of the managed device at any time by looking at the display content.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. FIG. 1 is a conceptual diagram showing the overall configuration of a communication network system according to the present invention, in which a network management device 10 and a plurality of managed devices 20a, 20b, 20c are connected in a ring shape via a communication path 30. Is done. Here, as the managed device 20 (20a, 20b, 20c), for example, an ATM (Asynchronous Transfer Mode) exchange can be used. The present invention is not limited to the configuration of the communication network system that connects the network management device 10 and the managed device 20 in a ring shape, and various connections such as a linear connection or a star-type connection are possible. The form is also acceptable.

  In the communication network system in FIG. 1, the network management device 10 and the managed device 20 are realized by the configurations shown in FIGS. 2 and 3, for example. 2, the network management apparatus 10 includes an interface unit 101 that controls an interface with the communication path 30, a control unit 102 that performs overall control, a mouse, a keyboard, and the like, and performs various instruction input operations for network management. An input unit 103 to perform, a display unit 104 for displaying information related to network management, and a storage unit 105 for storing various information necessary for network management in cooperation with the managed device 20 are configured.

  The storage unit 105 stores at least an autonomous notification display application 105a, a screen display application 105b, a management middleware 105c, and a management protocol 105d. The autonomous notification display application 105 a is an application that performs display processing based on information (failure management information 204 a) related to a failure autonomously notified from the managed device 20. On the other hand, the screen display application 105b has a configuration (interface / status management information 204b) related to various configurations such as the configuration of the interface slot of the managed device 20 and the internal board operation status and alarm operation based on this configuration. It is an application that performs display processing based on.

  As the management middleware 105c, for example, an SNMP (Simple Network Management Protocol) manager can be used, and as the management protocol 105d, for example, SNMP / UDP / IP (Internet Protocol) can be used. The applications 105a and 105b, the management middleware 105c, and the management protocol 105d are read into the control unit 102 and executed under the control of the control unit 102.

  In FIG. 3, the managed device 20 includes an interface unit 201 that controls an interface with the communication path 30, a control unit 202 that performs overall control, and a status monitor that monitors a failure occurrence state and a change in an operation state of the managed device. Unit 203 and a storage unit 204 for storing various information necessary for network management in cooperation with the network management apparatus 10.

  The storage unit 204 stores failure management information 204a that collects information related to various types of failures of the own device, the configuration of the interface slot of the own device, and information related to various states such as an internal board operation state and an alarm operation based on this configuration. The collected configuration / state management information 204b, managed middleware 204c, and management protocol 204d are stored at least. For example, an SNMP agent is used as the managed middleware 204c, and SNMP / UDP / IP is used as the management protocol 204d, for example. The managed middleware 204 c and the management protocol 204 d are read into the control unit 202 and executed under the control of the control unit 202.

  The display control process related to the failure management of the managed device 20 in the network management device 10 is performed after an autonomous notification from the managed device 20. That is, in the managed device 20, when a failure occurs or recovers, the state monitoring unit 203 detects this and notifies the control unit 202. The control unit 202 manages these detection results as failure management information 204a, and determines whether a failure has occurred as the entire managed device 20 or a failure has been recovered based on the detection results. Requesting an autonomous notification of failure occurrence or failure recovery according to the judgment result. In response to this request, the managed middleware 204c uses the management protocol 204d to issue an autonomous notification including the failure management information 204a to the network management apparatus 10 connected through the communication path 30.

  On the other hand, the network management device 10 receives the autonomous notification notification regarding the occurrence or failure recovery from the managed device 20 by the management protocol 105d, and passes the autonomous notification information (failure management information 204a) to the management middleware 105c. The management middleware 105c holds and manages this autonomous notification information in association with the issue source address (the IP address of the managed device 20 that issued the autonomous notification). Here, the management middleware 105 c also has a function of managing each managed device 20 that is a management target as a device icon representing each managed device 20.

  When the autonomous notification display application 105a receives the autonomous notification notification, the autonomous notification display application 105a refers to the notification source address to search for a device icon managed by the management middleware 105c, while the failure in the autonomous notification notification at this time With reference to the management information 204a, a color indicating the occurrence of a failure or a color indicating a failure recovery is reflected on the searched device icon and displayed on the display unit 104 according to the value. This autonomous notification display process is performed every time an autonomous notification notification is received from the managed device 20, whereby the color display of the device icon of the managed device 20 of the notification source is updated each time. . Specific processing of color display using the device icon will be described in detail later with reference to FIG.

  The autonomous notification display application 105a has a function of displaying the autonomous notification information managed by the management middleware 105c on the display unit 104 as character information, in addition to the above-described fault state display function using the device icon. Here, for convenience, the character display process in the autonomous notification display by the autonomous notification display application 105a will be described first.

  As described above, in this communication network system, the managed device 20 causes the managed middleware 204c to issue an autonomous notification to the network management device 10 through the management protocol 204d based on the monitoring result of the state monitoring unit 203. On the other hand, the network management apparatus 10 receives the autonomous notification issue by the management protocol 105d, and holds and manages it on the management middleware 105c. In this state, for example, when a predetermined display operation is performed from the input unit 103 by the administrator, the autonomous notification display application 105a reads the autonomous notification information managed by the management middleware 105c, and displays it as character information. 104.

  FIG. 4 shows an example of a display screen of the autonomous notification information display function (event browser) supported by the autonomous notification display application 105a. This event browser is a function for displaying the contents of the received autonomous notification information (event) as characters, and the screen items and display contents are as follows.

  (41) A screen name is displayed in the title bar. (42) Menu items are displayed in the menu bar. (43) A menu item can display a pull-down menu by clicking inside the item. (44) In the entrustment, a check mark column for displaying whether or not the event is entrusted is displayed. (45) In the importance level, the importance level of the event is displayed. The severity classification includes normal range, caution range, alert range, important alert range, danger range, unrecognizable, unmanaged, etc. (46) The day of the week, date, and time when the event occurred are displayed as the date and time. (47) In the source, an identifier (name of managed device, etc.) of the network object in which the event has occurred is displayed. (48) The content of the event is displayed in the message.

  As described above, the autonomous notification (hereinafter referred to as trap) event from the managed device 20 is displayed in the event browser window on the autonomous notification display application 105a. To display a trap event in this event browser window, the event ID of the trap event to be displayed on the event setting (or event addition) screen and the trap message to be displayed in accordance with the event ID are displayed as event log messages. It is necessary to set. The event ID corresponding to the trap event defined in the system is set as the event ID, and the event log message is directly input as the heading when displayed in the event browser window, and the trap is set. When displaying the data received in step 1, the position of the data to be displayed is designated immediately after $. Hereinafter, setting examples of event log messages and displayed contents will be described with reference to FIGS.

  First, in the event displayed on the display screen of FIG. 4, in the case of a hardware alarm (temperature abnormality notification = axtTemperatureAlarm), the node detailed description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime)], status type alarm monitoring point ID [xxxxxxxx (hexadecimal 8 digits) (axtLalmObsId)], status type alarm fault name [alarm name corresponding to status type alarm monitoring point ID (Maximum 35 characters) (axtLalmName)], status alarm failure status (1: failure recovery notification, 2: failure notification) [1: normal (axtLalmStatus = normal (1)), 2: abnormal (axtLalmStatus = alarm ( 2))], and a display example is as shown in FIG.

  For physical layer alarm (LOS notification = axtLosAlarm), detailed node description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxxhh: mm: ss (axtNodeDateTime)], status type Alarm monitoring point ID [xxxxxxxx (8 hexadecimal digits) (axtLalmObsId)], state type alarm failure name [alarm name corresponding to state type alarm monitoring point ID (maximum 35 characters) (axtLalmName)], state type alarm failure state (1: failure recovery notification, 2: failure occurrence notification) [1: normal (axtLalmStatus = normal (1)), 2: abnormal (axtLalmStatus = alarm (2))], I / F detailed description [comment (maximum full-width 128) (Character) (axtIfDefDescr)], and a display example thereof is as shown in FIG.

  For AAL layer alarm (AAL1RX lost cell number notification = axtAal1RxLostCellsAlarm), detailed node description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime) ] Gauge type alarm monitoring point ID [xxxxxxxx (8 hexadecimal digits) (axtGalmObsId)], Gauge type alarm fault name [Alarm name corresponding to gauge type alarm monitoring point ID (maximum 35 characters) (axtGalmName)], Gauge Type alarm failure status (1: Failure recovery notification, 2: Minor occurrence notification, 3: Major occurrence notification) [1: Normal (axtGalmStatus = normal (1)), 2: minor (axtGalmStatus = minor (2)), 3: major (axtGalmStatus = major (3))], I / F detailed description [comment (maximum full-width 128 characters) (axtIfDefDescr)], and a display example thereof is as shown in FIG.

  In the case of an AAL layer alarm (AAL1RX erroneous delivery cell count notification = axtAal1RxDstErrCellsAlarm), the node detailed description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime )], Gauge type alarm monitoring point ID [xxxxxxxx (hexadecimal 8 digits) (axtGalmObsId)], Gauge type alarm fault name [Alarm name corresponding to gauge type alarm monitoring point ID (maximum 35 characters) (axtGalmName)], Gauge type alarm failure status (1: Failure recovery notification, 2: Minor occurrence notification, 3: Major occurrence notification) [1: Normal (axtGalmStatus = normal (1)), 2: Minor (axtGalmStatus = minor (2)), 3 : Major (axtGalmStatus = major (3))], and a display example thereof is as shown in FIG.

  For loopback (automatic loopback execution notification = axtLpbkAutoSetNotice), detailed node description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime)] , Switch loopback interface number [interface number (axtLpbkSwIfIndex) corresponding to the trunk line for which switch loopback is set], switch loopback execution reason [1: manual, 2: LOS detection, 3: LOF detection, 4: LAIS detection, 5: LRDI detection, 6: LOP detection, 7: LCD detection, 8: PAIS detection, 9: PRDI detection (axtLpbkSwReason)]], and a display example thereof is as shown in FIG. 5 (e). .

  For loopback (auto loopback release execution notification = axtLpbkAutoRelNotice), detailed node description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime) ], Each item of the switch loopback interface number [interface number (axtLpbkSwIfIndex) corresponding to the trunk line for which the switch loopback is set] is shown as shown in FIG. 6 (a).

  If loopback (interface loopback release notification = axtLpbkIfRelNotice), detailed node description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime)] , Switch loopback interface number [interface number (axtLpbkSwIfIndex) corresponding to the trunk line for which switch loopback is set] and switch loopback type, and a display example thereof is as shown in FIG. .

  In case of clock (clock extraction switching notification = axtClkLinChangeNotice), each node detailed description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime)] There are items, and the display example is as shown in FIG.

  For the test (test OAM cell reception notification = axtTestCsRcvNotice), the node detailed description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime)] Each item is present, and a display example thereof is as shown in FIG.

  For contact alarm (contact alarm notification = axtCctBoxAlarm), detailed node description [comment (maximum 35 characters) (axtNodeDescr)], system date and time [yy / mm / dd xxx hh: mm: ss (axtNodeDateTime)], contact BOX alarm status (1: Normal, 2: Contact alarm is occurring) [All contact alarm status of connected contact BOX 1: Normal (axtLalmStatus = normal (1)) 2: Contact alarm is occurring (axtLalmStatus = alarm (2 )], Contact number index [contact table index (axtCctBoxPntNumIndex)], contact alarm name [contact alarm name (maximum 20 characters) (axtCctBoxPntAlmName)], contact alarm status (1: normal, 2: contact alarm status) [contact The alarm status of the corresponding contact in the BOX (axtCctBoxPntAlmStatus) 1: Normal (axtLalmStatus = normal (1)) 2: Contact alarm is occurring (axtLalmStatus = alarm (2)). The display example is shown in Fig. 6 (e ).

  The above (FIGS. 4 to 6) is a display example related to the process of displaying the autonomous notification information by the character among the autonomous notification display functions supported by the management middleware 105c of the network management apparatus 10. In addition, the management middleware 105c also supports a drawing processing function for displaying the autonomous notification information received from the managed device 20 using device icons representing the managed devices 20. The autonomous notification drawing processing function using this device icon will be described below.

  FIG. 7 shows an example of a display screen by the drawing application “IPMaP” supported by the management middleware 105c. This “IPMaP” displays, for example, the managed devices 20a, 20b, and 20c in the communication network system as shown in FIG. The process of changing and displaying the color of the device symbol 71 corresponding to the transmission source managed device 20 in accordance with the information indicating the system failure state in the autonomous notification information [see FIG. 5 and FIG. is there. In FIG. 7, the Hino center device corresponds to the managed device 20a in FIG. 1, for example. Similarly, in FIG. 7, the Toyota remote device 1 and the Toyota remote device 2 correspond to the managed devices 20b and 20c in FIG. 1, respectively. Regarding the operation of the device status color of the device symbol 71 arranged in “IPMaP”, for example, the normal region can be set to green, the warning region can be set to yellow, and the dangerous region can be set to red.

  Next, the apparatus symbol color operation processing operation on the “IPMaP” will be described with reference to the flowchart shown in FIG. When realizing the device symbol color operation, first, initialization setting processing is performed (step 801), and then trap event callback registration processing is performed (step 802). That is, in the initialization setting process, the API (Application Program Interface) function of the autonomous notification display application 105a can be used from the trap (autonomous notification) processing process by starting the process from the management middleware 105c. Initialize the connection status (OVwInit). In the trap event callback registration process, a trap event callback is registered (OVsnmpEventOpen) in order to receive a trap (callback call) from the management middleware 105c.

  After completion of the above processing, “IPMaP” performs state analysis processing of the device symbol 71 (step 803) when a trap is received from the managed device 20 through the management protocol 105d (step 811). Specifically, the current failure state of the trap transmission source device symbol 71 is read from the notified trap transmission source IP address, and compared with the notified trap system state to analyze whether there is a change.

  In this analysis, if there is no change in status, monitoring of trap generation (step 811) is continued, and if there is a change in status, device symbol color change processing is performed (step 804). In this device symbol color changing process, only when a change is detected in the device symbol state analyzing process in step 803, the color of the trap source device symbol 71 is changed according to the system failure received by the trap (OVwSetStatusOnSymbol). To do. FIG. 9 is a table showing a relationship between the system failure state received by the trap and the trap transmission source device symbol color changed from the status of the trap transmission source device symbol 71.

  As described above, in the network management device 10 of the present invention, not only the occurrence of a failure related to the managed device 20 but also the recovery from the failure is displayed as a color change of the device symbol 71 representing these managed devices 20. Therefore, the administrator can recognize the occurrence and recovery of the failure of the managed device 20 in a timely manner. Further, by combining the display by the device symbol 71 with the autonomous notification history display by the management middleware 105c, it is possible to realize a configuration capable of determining the occurrence or recovery of a past failure.

  The network management device 10 of the present invention has a configuration / status display function for displaying information related to the configuration and status of the managed device 20 in addition to the autonomous notification display function described above. The configuration referred to here is, for example, the configuration of the interface slot on the front surface of the housing of the managed device 20 and each user port therein, and the state is, for example, the operating state of the internal board connected to the interface slot, the power supply Indicates the status or alarm occurrence status. The screen display application 105b is responsible for processing related to this configuration / status display function.

  Hereinafter, the configuration / status display processing operation of the managed device 20 in the network management device 10 will be described. The configuration / status display process by the screen display application 105 b in the network management apparatus 10 can be activated in response to a predetermined configuration / status confirmation operation from the input unit 103, for example. As an example of this configuration / state confirmation operation, the administrator may perform an operation for instructing to start display processing after designating the IP address of the managed apparatus 20 to be confirmed in the input unit 103. In addition, for example, on the “IPMap” screen in FIG. 7, the device symbol 71 corresponding to the managed device 20 is displayed in a state where the failure symbol is displayed for the device symbol 71 corresponding to the managed device 20. An operation of clicking in the area may be performed, and the display function may be activated in response to the operation.

  After the startup operation described above, the screen display application 105b uses the management middleware 105c and the management protocol 105d to display information on the configuration and state of the managed device 20 connected via the communication path 30. Requested to the managed middleware 204 of the device 20. Here, it goes without saying that the destination of the request is the managed device 20 having the IP address input by the above-described operation.

  The managed device 20 that is the transmission destination of this request receives a request from the screen display application 105b using the management protocol 204d and passes the request to the managed middleware 204c. Upon receiving the request, the managed middleware 204 receives configuration / status management information 204b related to its own device from the storage unit 204 (such as the external connection slot structure, the operation state of the internal board, the power supply status, the alarm occurrence status, etc. in the device). Information reflecting the contents) is read, and the information 204b is sent to the network management apparatus 10 using the management protocol 204d.

  On the other hand, the network management apparatus 10 receives the configuration / state management information 204b sent out as a response from the managed apparatus 20 using the management protocol 105d, and stores the information 204b in the management middleware 105c. Further, the screen display application 105b performs a drawing process on the display unit 104 based on the configuration / state management information 204b stored in the management middleware 105c. In this drawing process, the screen display application 105b draws an image related to the configuration and state corresponding to each item in the configuration / state management information 204b acquired from the managed device 20 as it is as the actual machine image of the managed device 20. .

  In general, in the managed device 20 (actual machine), for example, an interface slot or the like is provided on the front surface of the casing, and an operation status of an internal board connected to the interface slot or the like, a power supply status, an alarm occurrence status, or the like is displayed. Elements and the like are provided. The actual machine image means image contents that can be recognized in the same manner as when the front surface of the managed device 20 (actual machine) is actually viewed.

  The network management device 10 draws the configuration and status of the managed device 20 with the actual machine image as described above, and then periodically acquires the configuration / status management information 204c of the managed device 20 by the same processing. get. On the other hand, in response to a periodic information acquisition request from the network management device 10, the managed device 20 returns configuration / state management information 204 c reflecting the latest contents based on the monitoring result of the state monitoring unit 203. The screen display application 105b uses the configuration / state management information information 204c acquired periodically, updates the past contents with the latest contents, and continues drawing with the actual machine image. As a result, even if the configuration or state of the managed device 20 changes, the latest configuration and state regarding the managed device 20 are always drawn as an actual machine image. As a result, the administrator can recognize the latest configuration and state of the managed device 20 in exactly the same way as when the user actually visits the managed device 20 and looks at the front of the casing.・ Management work can be carried out smoothly.

  Next, a specific example of a drawing image related to the configuration and state of the managed device 20 in the network management device 10 will be described. 10 and 11 show examples of the configuration and status of the managed device 20 in the network management device 10, respectively. 10 is a display example when the managed device 20 is a 3-slot version controlling ATM device, and FIG. 11 is a display example when the managed device 20 is a 12-slot version controlling ATM device. is there. As can be seen from these drawings, the structure of the interface slot, the operation state of the internal board connected to the interface slot, the state of the power supply, etc., for both the 3-slot version control ATM device and the 12-slot version control ATM device Alternatively, the lighting state of the display element for displaying the alarm occurrence status or the like is drawn in the same manner as the actual machine image.

  The screen display application 105b obtains configuration information (sysObjectID, axtBrdBaseOperStatus, axtBrdIfType, axtBrdIfOperStatus, axtBrdIfType) and status information (axtBoardAlarmStatus, axtBrdBaseOperStatus, axtBrdBaseAlarmStatus, axtIndLtStatus, axIndLIndLtStatus, axInBdBaseType, AxtBrdBaseType, AxtBrdBaseType Then, an image drawing process as shown in FIG. 10 or FIG. 11 is performed on the display unit 104 in accordance with the rules described below.

  Here, for example, the screen configuration and the drawing rule will be described by taking the display screen shown in FIG. 10 as an example. The parenthesis numbers given by the lead lines in the figure indicate the display items on the display screen. Of the display items (1) to (22) on the display screen, (1) the title of the screen is displayed in the title bar. (2) Top level menu items are displayed on the menu bar. (3) Top level menu items: As a breakdown of (operation), there are a plurality of items such as a file, a configuration, and an operation. A pull-down menu is displayed by clicking each item. (4) In the device type, the device type of the selected device is displayed. In this example, the ring network remote communication device is selected, but there are other ring network center communication devices and star connection remote devices. All of these device types are acquired from (sysObjectID).

  (5) Device name: (Display / Operation) displays the device name of the selected device (in this example, Toyota remote device No. 1) (axtNodeDescr). The maximum length of the label name character string is 32 full-width characters (64 half-width characters). If the character string exceeds the screen width, the caret is displayed by clicking on this display area, and the character string can be scrolled horizontally by the arrow key input. (6) The IP address of the selected device is displayed as the IP address. This IP address is acquired from the activation source application.

  (7) On the POWER, the main power supply operation state is displayed in color. For example, normal (axtIndPsStatus = normal (1) normal) is displayed in green, abnormal (axtIndPsStatus = abnormal (2) abnormal) in red, unrecognizable (axtIndPsStatus = unknown (-1) unknown) is displayed in light blue To do.

  (8) The system operating state is displayed in color on the RUN (RUN-LED state). For example, when blinking (normal) (axtIndRunLed = ledGrnBlink0 (4) blinking 0), green when operation is disabled (axtIndRunLed = ledOff (1), ledGrn (2) CPU stopped), red, not recognized (axtIndRunLed) = unknown (-1) Unknown) is displayed in light blue.

  (9) The device status is displayed in color on ALARM (ALM-LED status). For example, green is in normal operation (axtIndAlmLed = ledOff (1) OFF state), blinking in red (axtIndAlmLed = ledRedBlink0 (5) ledRedBlink1 (7) ledRedBlink5 (15) blinking state), abnormal state (axtIndAlmLed) = ledRedOn (3) ON state) is displayed in yellow, and when it cannot be recognized (axtIndAlmLed = unknown (-1) unknown), it is displayed in light blue.

  (10) In the NCONV board frame line: (in-frame area: operation), a dotted rectangle is overlapped on the front image of the apparatus to indicate that the NCONV board exists inside. By clicking in the dotted line rectangle, the highlight line rectangle representing the selection is made (see FIG. 18).

  (11) In the NCONV board state, the state of the internal board is displayed in color. For example, when normal (axtBoardAlarmStatus.n = normal (1) normal), green when alarm (axtBoardAlarmStatus.n = minAlm (2) alarm), abnormal (axtBoardAlarmStatus.n = majAlm (3) abnormal) Is red, unrecognizable (axtBoardAlarmStatus.n = unknown (-1) unknown), and (axtBoardType = nconv (2)) are displayed in light blue. In the above conditional expression, “n” means (n = instance index = index of entry corresponding to NCONV board).

  (12) In the MAIN substrate frame line: (in-frame region: operation), a dotted rectangle is overlapped on the front image of the apparatus to indicate that the MAIN substrate exists inside. By clicking in the dotted line rectangle, the highlight line rectangle representing the selection is made (see FIG. 18). In the case of a 3-slot image, if the device type is a star connection remote communication device, the line I / F image and the LED image are not displayed.

  (13) In the MAIN substrate state, the state of the internal substrate is displayed in color. For example, when normal (axtBoardAlarmStatus.n = normal (1) normal), green when alarm (axtBoardAlarmStatus.n = minAlm (2) alarm), abnormal (axtBoardAlarmStatus.n = majAlm (3) abnormal) Is red, unrecognizable (axtBoardAlarmStatus.n = unknown (-1) unknown), and (axtBoardType = mainb (1)) are displayed in light blue. In the above conditional expression, “n” means (n = instance index = index of entry corresponding to MAIN board).

  (14) Base I / F slot insertion board image: In (display / operation), a base I / F image corresponding to the mounting state and operating state of the corresponding board is displayed. For example, when the board is not mounted in the slot, an image of the front surface of the base I / F dummy board is displayed as shown in FIG. The state determination in this case is performed with reference to (axtBrdBaseOperStatus.p = (3) H / W recognition not possible) or (axtBrdBaseOperStatus.p = (-1) unknown). However, in the above conditional expressions, “p” means (p = instance index = axtBrdBaseIndex = base I / F slot number). Also, after the image is displayed, the next slot state is acquired.

  When the operation state is the built-in state or the disconnected state, the front image of the insertion board is displayed. In this case, each state is determined with reference to (axtBrdBaseOperStatus.p = (1) incorporation state) or (axtBrdBaseOperStatus.p = (2) detachment state). However, in the above conditional expressions, “p” means (p = instance index = axtBrdBaseIndex = base I / F slot number).

  Further, when the operation state is the built-in state or the disconnected state and the following conditions are satisfied, a user port image is further displayed on the base I / F image. For example, in the case of (axtBrdBaseType.p = sd15l (4)), an image as shown in FIG. 12B is displayed. In the case of (axtBrdBaseType.p = sd15u (5)), an image as shown in FIG. 12C is displayed.

  Similarly, in the case of (axtBrdBaseType.p = is15l (6)), an image as shown in FIG. 13A is displayed. In the case of (axtBrdBaseType.p = is15u (7)), an image as shown in FIG. 13B is displayed. In the case of (axtBrdBaseType.p = sd63l (8)), an image as shown in FIG. 13C is displayed. In the case of (axtBrdBaseType.p = sd63u (9)), an image as shown in FIG. 13D is displayed. In the case of (axtBrdBaseType.p = cr63 (10)), an image as shown in FIG. 13 (e) is displayed.

  Furthermore, in the case of (axtBrdBaseType.p = ifba (1)), (axtBrdBaseType.p = al1b (2)), or (axtBrdBaseType.p = brdNull (3)), the base I as shown in FIG. The / F image is displayed, and the interface board image is displayed thereon. In the case of (axtBrdBaseType.p = other than the above), an I / F image as shown in FIG. 14B is displayed. After display, the next slot state is acquired. On the other hand, when the operation state is other than “installed”, “detached”, “H / W recognition not possible”, “unknown”, an I / F image as shown in FIG. The state determination in this case is performed with reference to other than (axtBrdBaseOperStatus.p = (1), (2), (3), (-1)). Also, after the image is displayed, the next slot state is acquired.

  (15) In the slot insertion board state, an image of a lamp (which does not actually exist) is displayed, and the board state is represented by a color. Specifically, the respective states of the base substrate and the I / F substrate accommodated in each slot are collected, and the color with the highest failure level is displayed.

  Examples of display colors related to the status of the base board include, for example, normal status (axtBrdBaseOperStatus.p = up (1) built-in status) and (axtBrdBaseAlarmStatus.p = normal (1) normal), green, alarm status (axtBrdBaseAlarmStatus.p = minAlm (2) Alarm status) and (axtBrdBaseOperStatus.p = up (1) Embedded status) Yellow, abnormal status (axtBrdBaseAlarmStatus.p = majAlm (3) abnormal status) and (axtBrdBaseOperStatus.p = up (1) In the case of (embedded state), it is displayed in red, and in the case of stopped state (axtBrdBaseOperStatus.p = down (2) stopped state), it is displayed in orange, and not mounted (axtBrdBaseOperStatus.p = up (3) H / W cannot be recognized). In this case, there is no display. In the above conditional expression, “p” means (p = instance index = axtBrdBaseIndex = base I / F slot number).

  Similarly, examples of display colors related to interface board status are green for normal status (axtBrdBaseOperStatus.q = up (1) built-in status) and (axtBrdBaseAlarmStatus.q = normal (1) normal), alarm status ( axtBrdBaseAlarmStatus.q = minAlm (2) Alarm status) and (axtBrdBaseOperStatus.q = up (1) Embedded status) yellow, abnormal status (axtBrdBaseAlarmStatus.q = majAlm (3) abnormal status) and (axtBrdBaseOperStatus.q = up (1) Built-in status) is displayed in red, and stopped status (axtBrdBaseOperStatus.q = down (2) Stopped status) is displayed in orange, and not installed (axtBrdBaseOperStatus.q = up (3) H / W recognition No) is not displayed. In the above conditional expression, “q” means (q = instance index = axtBrdIfIndex = interface board slot number).

  (16) User ports 0 to 3 (display / operation) display the states of the trunk transmission line I / F ports (1 to 2) and the network management device I / F port (3) in colors. . Here, the display image of each port is composed of a connector image imitating a connector and an LED image imitating an LED adjacent thereto. In the display item, display color change processing is performed on each LED image according to the state of each port. Thus, for example, green when operating (axtIndLinAlmLed.q = ledGrn (2)), red when line failure (axtIndLinAlmLed.q = ledRed (3) line error), stopped (axtIndLinAlmLed.q = ledoff (1), ledRedBlink0 (5) Stopped) is displayed in orange, and unknown (axtIndLinAlmLed.q = unknown (-1) unknown) is displayed in light blue. In the above conditional expression, “q” means (q = instance index = axtIfIndex = user port number). Regarding the display item, by clicking in the drawing area rectangle, a frame line indicating selection is highlighted on the connector image.

  (17) Interface boards X0 to X3 (X = base I / F slot number): In (display / operation), the type of base I / F (axtBrdBaseType.n) is confirmed, and the base I / F slot image The interface board image is put on and displayed. In the above conditional expression, “n” means (n = instance index = axtBrdBaseIndex = base board slot number).

  As the interface board image in this display item, there are types as shown in FIGS. In accordance with each condition described below, a user port image is further displayed on the base I / F image. In the following conditional expression, “m” means (m = instance index = axtBrdIfIndex = interface board slot number).

  First, when no board is mounted in the slot, an image of the front surface of the base I / F dummy board is displayed as shown in FIG. The state determination in this case is performed with reference to (axtBrdIfOperStatus.m = (3) H / W recognition not possible) or (axtBrdIfOperStatus.m = (-1) unknown).

  Further, when the operation state is the built-in state or the detached state, the front image of the insertion board is displayed. In this case, each state is determined by referring to (axtBrdIfOperStatus.p = (1) Built-in state) or (axtBrdIfOperStatus.p = (2) Detached state). When the operating state is the built-in state or the disconnected state and the following conditions are satisfied, a line image is displayed on the interface board image. For example, in the case of (axtBrdIfType.m = ifea (1)), an image as shown in FIG. 15B is displayed. In the case of (axtBrdIfType.m = ifeb (2)), an image as shown in FIG. 15C is displayed. In the case of (axtBrdIfType.m = if63hsd (3)), an image as shown in FIG. 15D is displayed. In the case of (axtBrdIfType.m = if4wtp (4)), an image as shown in FIG. 15E is displayed.

  Similarly, in the case of (axtBrdIfType.m = a150ss (5)), an image as shown in FIG. 16A is displayed. In the case of (axtBrdIfType.m = a150mm (6)), an image as shown in FIG. 16B is displayed. In the case of (axtBrdIfType.m = a150sl (7)), an image as shown in FIG. 16C is displayed. In the case of (axtBrdIfType.m = clk (8)), an image as shown in FIG. 16 (d) is displayed. In the case of (axtBrdIfType.m = clk1 (9)), an image as shown in FIG. 16 (e) is displayed. In the case of (axtBrdIfType.m = clk2 (10)), an image as shown in FIG. 16 (f) is displayed.

  In the case of (axtBrdIfType.m = other than the above), an image as shown in FIG. 16G is displayed. In this case, the user port image is not displayed. On the other hand, when the operation state is other than embedded, disconnected, H / W recognition not possible, or unknown, an interface board image as shown in FIG. The state determination in this case is performed with reference to other than (axtBrdIfOperStatus.m = (1), (2), (3), (-1)). In this case, the user port image is not displayed.

  (18) User ports X0 to X3 (X = base I / F slot number): (display / operation) displays colors according to the type of interface board. Here, the display image of each port is composed of a connector image as shown in FIG. 17A and an LED image as shown in FIG. In the display item, when the type of the interface board is (axtBrdIfType.m = ifea (1) or axtBrdIfType.m = ifeb (2)), the line state is represented by a color. This color display is handled by changing the connector color as follows on the connector image shown in FIG. For example, it is green in the normal state (axtIfAlarmStatus.q = normal (1) startup state), red in the abnormal state (axtIfAlarmStatus.q = majAlm (3) major alarm level), and stopped (axtIfAlarmStatus.q = minAlm (2) ) Minor alarm level) is displayed in yellow, and stopped (axtIfAlarmStatus.q = unknown (-1) unknown state) is displayed in light blue. In the above conditional expression, “q” means (q = instance index = axtIfIndex = user port number).

  In the display item, when the type of the interface board is other than (axtBrdIfType.m = ifea (1) or axtBrdIfType.m = ifeb (2)), the LED state is represented by a color. This color display corresponds by changing the LED color as follows on the LED image shown in FIG. For example, it is green in the normal state (axtIndIfLed.q = ledGrn (2) startup state), red in the abnormal state (axtIndIfLed.q = ledRed (3) fault state), and stopped (axtIndIfLed.q = unknown (-1) ) In the case of unknown status), it is displayed in light blue, and in the case of stopped status (axtIndIfLed.q = ledOff (1), ledGrnBlink0 (4) stopped status), it is displayed in orange. In the above conditional expression, “q” means (q = instance index = axtIfIndex = LED index). For the display item as well, a frame line indicating selection is highlighted on the connector image by clicking in the drawing area rectangle.

  (19) An image of a lamp (which does not actually exist) is displayed on the fan, and the fan operating state is represented by a color. Examples of display colors related to the fan operating status are green for normal status (axtLalmStatus.t = normal (1) normal), red for abnormal status (axtLalmStatus.t = alarm (2) abnormal), unrecognizable In the case of (axtLalmStatus.t = unknown (-1) unknown), it is displayed in light blue. In the above conditional expression, “t” means (t = instance index = axtLalmObsId = corresponding monitoring point ID of fan alarm information: h01090002).

  (20) The image of the lamp (which does not actually exist) is displayed as the temperature, and the temperature state inside the apparatus is represented by a color. Examples of display colors related to temperature status include green for normal status (within rated value range) (axtLalmStatus.u = normal (1) normal), abnormal status (out of rated value range) (axtLalmStatus.u = alarm ( 2) If it is abnormal), it will be displayed in red. If it cannot be recognized (axtLalmStatus.u = unknown (-1) unknown), it will be displayed in light blue. In the above conditional expression, “u” means (u = instance index = axtLalmObsId = corresponding monitoring point ID of temperature alarm information: h01090000).

  (21) In the contact alarm, an image of a lamp (which does not actually exist) is displayed, and the contact alarm state inside the apparatus is represented by a color. Examples of display colors related to the contact alarm status are green for normal status (axtCctBoxAlmStatus = normal (1) normal) and (axtCctBoxConStatus = connect (1) connection), alarm status (axtCctBoxAlmStatus = minAlm (2) alarm) and Displayed in yellow when (axtCctBoxConStatus = connect (1) connection), abnormal status (axtCctBoxAlmStatus = majAlm (3) abnormal) and (axtCctBoxConStatus = connect (1) connection) displayed in red, and cannot be recognized (axtCctBoxAlmStatus = unknown) (-1) Unknown) or (axtCctBoxConStatus = disconnect (2) Not connected), no display. (22) The status is displayed on the status bar.

  On the display screen having the display items (1) to (22) (apparatus state diagram: see FIG. 10), a desired drawing area can be selected by the following operation. This selection operation will be described with reference to FIG. FIG. 18 shows a drawing area selection operation image of the apparatus state diagram in FIG.

  FIG. 18A shows an initial state, that is, a state where no drawing area is selected. In this state, the mouse pointer is moved to the corresponding drawing area and then clicked to select it. At this time, in order to show that the drawing area is in the selected state, for example, as shown in FIG. FIG. 6B shows a state in which the display item of (10) NCONV board frame line on the apparatus state diagram is selected.

  On this device state diagram, a plurality of display items (14) board image and (18) user port image cannot be selected. In addition, once the selection operation is performed, one of the selection states on the apparatus state diagram is always kept in the selected state. Specifically, for example, in (14) selection of a board image, first, an interface board slot number to be collected is set to X0 (where X corresponds to a base I / F slot number). If the collected interface board type is one user port mounted on one interface board, the next interface board slot number to be collected is the user port number on the left. When two user ports are mounted on one interface board, the interface board slot number to be collected next is X2.

  When the collected interface board type is (axtBrdIfType.m = other (-1) and undefined), the interface board slot number to be collected next is the same as when one user port is mounted on one interface board. Next user port number. That is, in the case of (axtBrdIfType.m = other (-1) and undefined), if the interface board type collected with the interface board slot number X0 is one user port mounted on one interface board, then the next collection The interface board slot number to be X1 is X1. When the interface board type collected by the interface board slot number X1 is one user port mounted on one interface board, the next interface board slot number to be collected is X2. When the interface board type collected by the interface board slot number X2 is one user port mounted on one interface board, the next interface board slot number to be collected is X3. FIG. 18C shows an example of selecting a user port according to the above rule, and particularly shows a state where the user port 21 is selected.

  10 and 12 to 18, the configuration / state management information display process, display image, and selection operation when the managed device 20 is a 3-slot version control ATM device have been described. These display processing, display image, and selection operation are similarly applied to the 12-slot version control ATM device shown in FIG.

  The present invention can be applied to a communication network system in which one or a plurality of communication devices and a network management device that manages the communication devices are connected by a communication path, and information on a configuration of a managed device and a state based on the configuration The management device acquires the management device from the managed device, and displays the configuration and state of the acquisition source managed device on the display screen as an actual machine based on the acquired information. From the contents, it is possible to accurately recognize the configuration and state of the managed device with the same accuracy as when the actual device is used.

1 is a schematic diagram showing the overall configuration of a communication network system according to the present invention. The block diagram which shows the function structure of the network management apparatus in FIG. The block diagram which shows the function structure of the to-be-managed apparatus in FIG. The figure which shows the example of a display of the managed apparatus autonomous notification information in a network management apparatus. The figure which shows the example of a setting of the one part information of the display target for obtaining the display screen shown in FIG. The figure which shows the example of a setting of the other information of the display target for obtaining the display screen shown in FIG. The figure which shows another example of a display of the managed apparatus autonomous notification information in a network management apparatus. The flowchart which shows the apparatus symbol color operation process on the display screen in FIG. The table figure which shows the relationship between the apparatus symbol status in the apparatus symbol color operation, and the received system failure state. The figure which shows an example of the structure / status display screen of the managed apparatus in a network management apparatus. The figure which shows another example of the structure / status display screen of the managed apparatus in a network management apparatus. The figure which shows the display image of various base I / F slot insertion board | substrates. The figure which shows the display image of another various base I / F slot insertion board | substrate. Furthermore, the figure which shows the display image of another various base I / F slot insertion board | substrate. The figure which shows the display image of various interface boards. The figure which shows the display image of another various interface board | substrate. The figure which shows the display image of a user port. The figure which shows the drawing area selection operation image on the display screen in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Network management apparatus 101 Interface (I / F) part 102 Control part 103 Input part 104 Display part 105 Storage part 105a Autonomous notification display application 105b Screen display application 105c Management middleware 105d Management protocol 20, 20a, 20b, 20c Managed apparatus 201 Interface (I / F) unit 202 Control unit 203 Status monitoring unit 204 Storage unit 204a Fault management information 204b Configuration / status management information 204c Managed middleware 204d Management protocol 30 Communication path 71 Device symbol

Claims (5)

In a communication network system formed by connecting a communication device and a management device that manages the communication device through a communication path,
The communication device
State monitoring means for detecting an operation state including failure occurrence or failure recovery of the own device;
Autonomous management means for autonomously managing configuration / state management information related to the configuration related to the configuration detected by the status monitoring means and the configuration of the own device;
In response to an acquisition request from the management device, the configuration / state management information is transferred to the management device according to a predetermined protocol.
The management device
Management processing means for sending out the acquisition request to the managed device and acquiring and managing the configuration / state management information transferred from the managed processing means in response to the acquisition request by the predetermined protocol;
Based on the configuration / state management information acquired by the management processing unit, the configuration and state of the source communication device are drawn on the display unit with the same actual image as when the configuration and state of the communication device are actually viewed. A communication network system comprising: a configuration / status display processing unit. The management device
Address designation means for designating an address of a communication device from which the configuration / state management information is to be acquired;
The management processing means includes
The communication network system according to claim 1, wherein the acquisition request is sent to the communication device corresponding to the address designated by the address designation means. In the communication device,
The autonomous management means includes
Further managing failure management information based on the occurrence or failure recovery of the own device detected by the state monitoring means,
The managed processing means includes:
Upon failure occurrence or recovery of the own device, the failure management information managed by the autonomous management means is autonomously notified to the management device by the predetermined protocol.
The management device
Based on the failure management information acquired from the communication device corresponding to the autonomous notification at the time of failure occurrence or failure recovery, a color indicating the failure occurrence or recovery of the device icon corresponding to the communication device that is the transmission source of the autonomous notification Further comprising an autonomous notification display processing means for displaying at
The management processing means includes
The communication according to claim 1 or 2, wherein the acquisition request is sent to the communication device corresponding to the selected device icon in response to a selection operation of the device icon displayed by the autonomous notification display processing means. Network system. In the management device,
The management processing means includes
Periodically acquiring the configuration / status management information from the communication device;
The configuration / status display processing means includes:
The communication network system according to any one of claims 1 to 3, wherein an image being displayed on the display unit is updated and displayed as needed based on the acquired configuration / state management information. In the communication device,
The autonomous management means includes
As the configuration / state management information, information related to the state of the board mounted on the communication device, the main power supply operation state, the system operation state, the alarm state, the fan operation state, the temperature, and the contact alarm state are managed.
In the management device,
The configuration / status display processing means includes:
While displaying an image of the same board appearance structure as when the board mounted on the communication device is actually seen, the state inside the board, the main power supply operating state, the system operating state, the alarm state, the fan operating state, the temperature, The communication network system according to any one of claims 1 to 4, wherein an image of a contact alarm state is displayed together with the substrate appearance structure image display by color.

Images