US20030163582A1 - Network device and network management device - Google Patents

Network device and network management device Download PDF

Info

Publication number
US20030163582A1
US20030163582A1 US10/269,540 US26954002A US2003163582A1 US 20030163582 A1 US20030163582 A1 US 20030163582A1 US 26954002 A US26954002 A US 26954002A US 2003163582 A1 US2003163582 A1 US 2003163582A1
Authority
US
United States
Prior art keywords
management information
network
management
network device
processor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/269,540
Inventor
Rumiko Inoue
Satoshi Tsuchiya
Koichi Takeda
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Assigned to FUJITSU LIMITED reassignment FUJITSU LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TAKEDA, KOICHI, TSUCHIYA, SATOSHI, INOUE, RUMIKO
Publication of US20030163582A1 publication Critical patent/US20030163582A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0253—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]

Definitions

  • the present invention relates to a network device and a network management device, and in particular to a network device and a network management device managing the network device.
  • FIG. 9 shows an arrangement of a general network, which is composed of sub-networks 40 _ 1 - 40 _ 3 .
  • the sub-networks 40 _ 2 and 40 _ 3 are connected to the sub-network 40 _ 1 respectively with network devices (e.g. routers) 10 a _ 1 and 10 a _ 2 (hereinafter, occasionally represented by a reference numeral 10 a ).
  • network devices e.g. routers
  • a network management device (server) 20 a and a Web server 30 are connected to the sub-network 40 _ 1 .
  • Clients 50 _ 1 and 50 _ 2 are respectively connected to the sub-networks 40 _ 2 and 40 _ 3 .
  • the network management device 20 a manages the network device 10 a with SNMP (Simple Network Management Protocol: protocol for a network management prescribed with RFC1157).
  • SNMP Simple Network Management Protocol: protocol for a network management prescribed with RFC1157.
  • An agent (not shown) included in the network device 10 a notifies to the network management device 20 a management information defined with MIB (Management Information Base) for a request from a manager (not shown) included in the network management device 20 a.
  • MIB Management Information Base
  • a management information processor or application (not shown) of the network management device 20 a produces a screen display, an error display, or the like based on the management information from the network device 10 a.
  • a network device 10 a mounts thereon a function of converting management information of its own device into an HTML document of a data format which can be referred to by WWW (World Wide Web), and a WWW server offering the converted management information.
  • WWW World Wide Web
  • a network device comprises: a network management processor for preparing management information of its own device in a format displayable on a browser upon occurrence of a predetermined event; and a transmitter for transmitting the management information (claim 1).
  • the network device can easily transmit e.g. the management information of its own device to a network management device. Also, the network device can transmit optimal management information for the management of its own device, unique management information, and the like by the optimal display format.
  • the occurrence of the predetermined event may comprise at least one of a time of a startup, a time of a management information change, or a predetermined period (claim 5).
  • the network device can transmit the management information of its own device when its own device starts up, when the management information of its own device changes, or at a predetermined period.
  • the occurrence of the predetermined event may comprise a time when a management information request packet is received from a network management device (claim 6).
  • a network management device comprises: a receiver for receiving management information of a format displayable on a browser transmitted from a network device upon occurrence of a predetermined event; and a network management processor for displaying the management information (claim 7).
  • a network management processor receives and displays management information of a format displayable on a browser transmitted from a network device upon occurrence of a predetermined event.
  • the network management device is provided with the network management processor having only a minimum browser function, and can manage the network device. Also, it becomes possible for the network management processor to manage e.g. the management information unique to a newly added network device without changing a management application.
  • the network management processor may have a management information storage for storing received management information of the format and a management information processor for displaying management information based on the management information (claim 8).
  • a management information storage stores the management information of the format received from the network device, and a management information processor displays the management information.
  • the network management processor may generate a management information request packet requesting management information determined to be necessary and may transmit the packet to the network device (claim 9).
  • the network management processor (network management application) when determining that the management information for a certain network device is necessary, such as at a time of power-on, a reset, a specific time such as noon, or when determining that there is necessary management information based on inputted management information, the network management processor (network management application) generates a management information request packet and transmits the same to the network device. Thus, it becomes possible for the management information processor to obtain necessary management information.
  • the network management device may further comprise a management information generator for transmitting a management information request packet requesting the management information to the network device, when subsequent management information is not received from the network device after the management information of the network device is received and a predetermined time elapses (claim 10).
  • a management information generator transmits a management information request to the network device when the subsequent management information is not received from the network device after a predetermined time elapses.
  • the management information processor may display each management information from a plurality of network devices respectively on a window screen corresponding to each network device (claim 11).
  • the management information processor it becomes possible for the management information processor to display the management information of a plurality of network devices simultaneously tiled on the screen.
  • the management information processor may display the management information based on an attribute added to the management information of the format (claim 12).
  • FIG. 1 is a block diagram showing an embodiment of a network device according to the present invention
  • FIG. 2 is a block diagram showing an embodiment of a network management device according to the present invention.
  • FIG. 3 is a diagram showing a network example composed of a network device and a network management device according to the present invention
  • FIGS. 4A and 4B are diagrams showing an example of a management information notification packet and an example of management information according to the present invention.
  • FIGS. 5 A- 5 C are diagrams showing an example of a management screen of a display in a network management device according to the present invention.
  • FIG. 6 is a flow chart showing an operation procedure of a network device according to the present invention.
  • FIG. 8 is a sequence diagram showing an operation procedure example between a network device and a network management device according to the present invention.
  • FIG. 9 is a block diagram showing a general network arrangement.
  • FIG. 1 shows an embodiment of a network device 10 according to the present invention.
  • This network device 10 is, for example, a router, and is provided with a network management processor 11 and a routing processor 14 .
  • the network management processor 11 is provided with a management information generator 12 and a management information storage 13 .
  • the routing processor 14 is provided with a packet transmitter 15 and a packet receiver 16 .
  • FIG. 2 shows an embodiment of a network management device 20 according to the present invention.
  • This network management device 20 is, for example, a server, and is provided with a network management processor 21 , a packet transmitter 26 , and a packet receiver 27 .
  • the network management processor 21 is provided with a management information generator 22 , a management information storage 23 , and a management information processor 24 .
  • This management information processor 24 includes a display 25 .
  • FIG. 3 shows a network example including the network device 10 and the network management device 20 according to the present invention. While the arrangement of this network is the same as a general network arrangement shown in FIG. 9, in FIG. 3 network devices (routers or the like) 10 _ 1 and 10 _ 2 , and the network management device (server) 20 according to the present invention are substituted for the prior art network devices 10 a _ 1 , 10 a _ 2 , and network management device 20 a.
  • the router 10 _ 1 is connected to sub-networks 40 _ 1 and 40 _ 2 respectively through ports 0 and 1 .
  • the router 10 _ 2 is connected to sub-networks 40 _ 1 and 40 _ 3 respectively through the ports 0 and 1 .
  • the IP addresses of the sub-networks 40 _ 1 - 40 _ 3 are respectively (10.10.10.x), (10.10.11.x), and (10.10.12.x).
  • the IP addresses of the ports 0 and 1 of the router 10 _ 1 are respectively (10.10.10.1) and (10.10.11.1).
  • the IP addresses of the ports 0 and 1 of the router 10 _ 2 are respectively (10.10.10.2) and (10.10.12.1).
  • the network devices 10 _ 1 and 10 _ 2 transmit a management information notification packet 70 including the management information of their own devices to the network management device 20 , e.g. (1) at a startup, (2) upon occurrence of an error, (3) when the management information is changed, or (4) periodically, as a predetermined event.
  • FIG. 4A shows an arrangement of the management information notification packet 70 transmitted by the network device 10 _ 1 .
  • This packet 70 is composed of a MAC header 71 , an IP header 72 , a TCP header 73 , a data field 74 , and an FCS 75 .
  • Management information 76 is included in the data field 74 .
  • FIG. 4B shows an example of the management information 76 shown in FIG. 4A.
  • the network management processor 21 holds the management information 76 included in the management information notification packet 70 received from the packet receiver 27 in the management information storage 23 .
  • the management information processor 24 refers to the management information storage 23 to execute a network management application. Namely, the management information processor 24 displays the following example (1) or (2): Display example (1): the management information received from each network device 10 is displayed on the display 25 sequentially tiled on the screen; Display example (2): the management information received from each network device is checked, and a logical connection of the network device 10 is determined based on a respective IP address (attribute is ⁇ di:IPAddr>) to be displayed as a network arrangement.
  • the management information processor 24 makes the management information of the network device corresponding to the clicked icon displayed.
  • the management information processor 24 executes alarm transmission processings such as the followings (1)-(3): (1) Alarm sound is transmitted; (2) The device where an error has occurred is flashed on the screen; (3) Mail notification or the like is transmitted to the network administrator.
  • the management information processor 24 requests the management information generator 22 to inquire the network device to which a subsequent notification packet 70 has not reached even after a predetermined time has elapsed, from e.g. the network device which has been receiving the notification packet 70 so far.
  • the management information generator 22 transmits a management information request packet 80 . In the absence of the response thereto, the management information processor 24 determines that the network device 10 is down or failed.
  • the management information processor 24 may request the management information generator 22 to transmit the management information request packet 80 to the network device according to the circumstances, after power-on, after a reset, at a specific time such as noon, or when determining that there is management information to be preferably obtained based on the obtained management information.
  • the description of the management information may be given by the HTML (Hyper Text Markup Language).
  • HTML Hyper Text Markup Language
  • the management information processor 24 network management application only “displays sequentially tiled on the screen”, as mentioned in the above display example (1).
  • a value can be changed depending on the then states, in which two kinds of icons indicating the normal state and the abnormal state, for example are prepared so that they can be included in the management information to be transmitted according to the states.
  • FIGS. 5 A- 5 C show an example of a management screen displayed on the display 25 .
  • FIG. 5A shows a network composed of the network devices (routers) 10 _ 1 and 10 _ 2 .
  • FIG. 5B shows a screen displayed when the router 10 _ 1 on the screen in FIG. 5A is clicked, in which the management information of the router 10 _ 1 , i.e. the icon of the router 10 _ 1 , an alarm indication indicating that the port 1 is down, and a throughput transition is displayed.
  • FIG. 5C shows, in the same way as FIG. 5B, a screen displayed when the router 10 _ 1 on the screen of FIG. 5A is clicked. This screen indicates the case where the screen is simply displayed without interpreting the attribute of the management information described by the XML.
  • FIG. 6 is a flow chart showing an operation of the network device (router) 10 .
  • FIG. 7 is a flow chart showing an operation of the network management device (server) 20 .
  • FIG. 8 shows an example of an operation sequence between the network device 10 _ 1 and the network management device 20 .
  • this operation sequence will be described referring to FIGS. 6 and 7.
  • Step S 100 The power is turned “ON” in the router 10 _ 1 (see step S 200 in FIG. 6).
  • Step S 101 In the router 10 _ 1 (see FIG. 1), the management information generator 12 transmits a management information notification packet 70 _ 1 (hereinafter, occasionally represented by a reference numeral 70 ) including the management information of its own device, and starts a timer for periodical transmission (not shown in FIG. 1) (see step S 201 in FIG. 6).
  • a management information notification packet 70 _ 1 hereinafter, occasionally represented by a reference numeral 70
  • a timer for periodical transmission not shown in FIG. 1 (see step S 201 in FIG. 6).
  • This timer for periodical transmission is for periodically transmitting the management information notification packet 70 (e.g. every one minute).
  • Step S 110 In the network management device 20 (see FIG. 2), the management information processor 24 receives the notification packet 70 _ 1 through the packet receiver 27 (see step S 300 in FIG. 7).
  • This monitoring timer is for monitoring whether or not the management information notification packet 70 is periodically received from the router 10 _ 1 .
  • Step S 103 Further one minute later, in the same way as step S 102 , the management information generator 12 transmits a notification packet 70 _ 3 including the latest management information 76 , and restarts the timer for periodical transmission (steps S 202 and S 201 in FIG. 6).
  • Step S 112 In the network management server 20 , the monitoring timer times out (steps S 303 and S 304 in FIG. 7).
  • the management information generator 22 transmits the management information request packet 80 to the router 10 _ 1 through the packet transmitter 26 , and restarts the monitoring timer (see steps S 305 and S 302 in FIG. 7).
  • Step S 104 In the router 10 _ 1 , the management information generator 12 receives the request packet 80 through the packet receiver 16 (a predetermined event occurs), transmits a notification packet 70 _ 4 including the management information of its own device to the network management server 20 , and restarts the timer for periodical transmission (steps S 203 and S 201 in FIG. 6).
  • Step S 113 In the same way as step S 110 , the management information is displayed on the display 25 and the monitoring timer is started.
  • Steps S 105 and S 114 In the same way as steps S 102 and S 111 , the management information of the router 10 _ 1 is transmitted by a notification packet 70 _ 5 and displayed on the display 25 of the network management server 20 .
  • a network device and a network management device are arranged such that a network management processor of the network device transmits management information of its own device in a format displayable on the browser, e.g. an XML or an HTML upon occurrence of a predetermined event, and a network management processor of the network management device displays the management information. Therefore, it becomes possible for the network device to easily transmit the management information of its own device to the network management device.
  • the network device can transmit the optimal management information for the management of its own device, the unique management information, and the like by the optimal display format. Also, the network management device is provided with the minimum browser function, thereby enabling the network device to be managed.
  • the network management device can manage e.g. the management information unique to a newly added network device without changing management applications.
  • the optimal management information for each network device e.g. an icon according to each device, the management information concerning a support function unique to the network device, or the like can be displayed on the network management device.
  • the management of the network device can be realized without buying a network management device and a network management application with a high function.

Abstract

In a network device and a network management device managing the network device, network management processors of the network devices transmit management information of their own devices in a format displayable on the browser, e.g. XML or HTML upon occurrence of a predetermined event, and a network management processor of the network management device displays the management information.

Description

    BACKGROUND OF THE INVENTION
  • 1. Field of the Invention [0001]
  • The present invention relates to a network device and a network management device, and in particular to a network device and a network management device managing the network device. [0002]
  • Recently, together with a rapid spread of communication, a large-scale network formed of small-scale networks, constructed for applications or services, such as Ethernet or intranet mutually connected has been increasing. To this network, network devices of various makers are connected, so that it is important to manage such network devices. [0003]
  • 2. Description of the Related Art [0004]
  • FIG. 9 shows an arrangement of a general network, which is composed of sub-networks [0005] 40_1-40_3. The sub-networks 40_2 and 40_3 are connected to the sub-network 40_1 respectively with network devices (e.g. routers) 10 a_1 and 10 a_2 (hereinafter, occasionally represented by a reference numeral 10 a).
  • A network management device (server) [0006] 20 a and a Web server 30 are connected to the sub-network 40_1. Clients 50_1 and 50_2 are respectively connected to the sub-networks 40_2 and 40_3.
  • [1] SNMP-Based Network Management [0007]
  • The [0008] network management device 20 a manages the network device 10 a with SNMP (Simple Network Management Protocol: protocol for a network management prescribed with RFC1157).
  • An agent (not shown) included in the network device [0009] 10 a notifies to the network management device 20 a management information defined with MIB (Management Information Base) for a request from a manager (not shown) included in the network management device 20 a.
  • A management information processor or application (not shown) of the [0010] network management device 20 a produces a screen display, an error display, or the like based on the management information from the network device 10 a.
  • [2] WWW-Based Network Management [0011]
  • In the prior art network management system disclosed in the Japanese Patent Application Laid-open No.11-239136, a network device [0012] 10 a mounts thereon a function of converting management information of its own device into an HTML document of a data format which can be referred to by WWW (World Wide Web), and a WWW server offering the converted management information.
  • A [0013] network management device 20 a mounts thereon a WWW browser, and browses the management information of the network device 10 a by accessing the WWW server.
  • In the prior art SNMP-based network management system, when the network device [0014] 10 a having new unique information (called expansion MIB) is managed, the expanded MIB had to be newly reflected to the application of the network management device 20 a.
  • Also, in the WWW-based network management system, the network device [0015] 10 a was required to mount thereon the WWW server.
  • Furthermore, in the SNMP-based and the WWW-based network management systems, the [0016] network management device 20 a was generally required to obtain the management information from the network device 10 a by means of polling.
    • SUMMARY OF THE INVENTION
  • It is accordingly an object of the present invention to provide a network device and a network management device managing the network device, thereby carrying out managements which can easily accommodate to management information unique to the network devices. [0017]
  • In order to achieve the above-mentioned object, a network device according to the present invention comprises: a network management processor for preparing management information of its own device in a format displayable on a browser upon occurrence of a predetermined event; and a transmitter for transmitting the management information (claim 1). [0018]
  • Namely, a network device independently transmits management information of its own device by a format displayable on a browser, e.g. HTML (Hyper Text Markup Language), XML (eXtensible Markup Language), or the like upon occurrence of a predetermined event. [0019]
  • Thus, it becomes possible for the network device to easily transmit e.g. the management information of its own device to a network management device. Also, the network device can transmit optimal management information for the management of its own device, unique management information, and the like by the optimal display format. [0020]
  • Also, in the present invention according to the above-mentioned present invention, the network management processor may comprise a management information storage for storing or holding the management information and a management information generator for generating management information of a format displayable on the browser based on the management information (claim 2). [0021]
  • Namely, a management information storage holds the management information of its own device. A management information generator refers to the management information held in the management information storage to generate management information of a format displayable on the browser. [0022]
  • Also, in the present invention according to the above-mentioned present invention, the format displayable on the browser may comprise an HTML or an XML (claim 3). [0023]
  • Also, in the present invention according to the above-mentioned present invention, an attribute may be added to the management information (claim 4). [0024]
  • Thus, it becomes possible to classify the management information by the attribute. [0025]
  • Also, in the present invention according to the above-mentioned present invention, the occurrence of the predetermined event may comprise at least one of a time of a startup, a time of a management information change, or a predetermined period (claim 5). [0026]
  • Namely, the network device can transmit the management information of its own device when its own device starts up, when the management information of its own device changes, or at a predetermined period. [0027]
  • Furthermore, in the present invention according to the above-mentioned present invention, the occurrence of the predetermined event may comprise a time when a management information request packet is received from a network management device (claim 6). [0028]
  • Also, in order to achieve the above-mentioned object, a network management device according to the present invention comprises: a receiver for receiving management information of a format displayable on a browser transmitted from a network device upon occurrence of a predetermined event; and a network management processor for displaying the management information (claim 7). [0029]
  • Namely, a network management processor receives and displays management information of a format displayable on a browser transmitted from a network device upon occurrence of a predetermined event. [0030]
  • Thus, the network management device is provided with the network management processor having only a minimum browser function, and can manage the network device. Also, it becomes possible for the network management processor to manage e.g. the management information unique to a newly added network device without changing a management application. [0031]
  • Also, in the present invention according to the above-mentioned present invention, the network management processor may have a management information storage for storing received management information of the format and a management information processor for displaying management information based on the management information (claim 8). [0032]
  • Namely, a management information storage stores the management information of the format received from the network device, and a management information processor displays the management information. [0033]
  • Also, in the present invention according to the above-mentioned present invention, the network management processor may generate a management information request packet requesting management information determined to be necessary and may transmit the packet to the network device (claim 9). [0034]
  • Namely, when determining that the management information for a certain network device is necessary, such as at a time of power-on, a reset, a specific time such as noon, or when determining that there is necessary management information based on inputted management information, the network management processor (network management application) generates a management information request packet and transmits the same to the network device. Thus, it becomes possible for the management information processor to obtain necessary management information. [0035]
  • Also, in the present invention according to the above-mentioned present invention, the network management device may further comprise a management information generator for transmitting a management information request packet requesting the management information to the network device, when subsequent management information is not received from the network device after the management information of the network device is received and a predetermined time elapses (claim 10). [0036]
  • Namely, after receiving the management information from a certain network device, a management information generator transmits a management information request to the network device when the subsequent management information is not received from the network device after a predetermined time elapses. [0037]
  • Thus, it becomes possible for the network management device to request the management information from the network device. [0038]
  • Also, in the present invention according to the above-mentioned present invention, the management information processor may display each management information from a plurality of network devices respectively on a window screen corresponding to each network device (claim 11). [0039]
  • Namely, it becomes possible for the management information processor to display the management information of a plurality of network devices simultaneously tiled on the screen. [0040]
  • Furthermore, in the present invention according to the above-mentioned present invention, the management information processor may display the management information based on an attribute added to the management information of the format (claim 12). [0041]
  • Namely, when an attribute “alarm” is added to the management information, for example, it becomes possible for the management information processor to give an alarm sound.[0042]
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • The above and other objects and advantages of the invention will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which the reference numbers refer to like parts throughout and in which: [0043]
  • FIG. 1 is a block diagram showing an embodiment of a network device according to the present invention; [0044]
  • FIG. 2 is a block diagram showing an embodiment of a network management device according to the present invention; [0045]
  • FIG. 3 is a diagram showing a network example composed of a network device and a network management device according to the present invention; [0046]
  • FIGS. 4A and 4B are diagrams showing an example of a management information notification packet and an example of management information according to the present invention; [0047]
  • FIGS. [0048] 5A-5C are diagrams showing an example of a management screen of a display in a network management device according to the present invention;
  • FIG. 6 is a flow chart showing an operation procedure of a network device according to the present invention; [0049]
  • FIG. 7 is a flow chart showing an operation procedure of a network management device according to the present invention; [0050]
  • FIG. 8 is a sequence diagram showing an operation procedure example between a network device and a network management device according to the present invention; and [0051]
  • FIG. 9 is a block diagram showing a general network arrangement.[0052]
    • DESCRIPTION OF THE EMBODIMENTS
  • FIG. 1 shows an embodiment of a [0053] network device 10 according to the present invention. This network device 10 is, for example, a router, and is provided with a network management processor 11 and a routing processor 14. The network management processor 11 is provided with a management information generator 12 and a management information storage 13. The routing processor 14 is provided with a packet transmitter 15 and a packet receiver 16.
  • FIG. 2 shows an embodiment of a [0054] network management device 20 according to the present invention. This network management device 20 is, for example, a server, and is provided with a network management processor 21, a packet transmitter 26, and a packet receiver 27. The network management processor 21 is provided with a management information generator 22, a management information storage 23, and a management information processor 24. This management information processor 24 includes a display 25.
  • FIG. 3 shows a network example including the [0055] network device 10 and the network management device 20 according to the present invention. While the arrangement of this network is the same as a general network arrangement shown in FIG. 9, in FIG. 3 network devices (routers or the like) 10_1 and 10_2, and the network management device (server) 20 according to the present invention are substituted for the prior art network devices 10 a_1, 10 a_2, and network management device 20 a.
  • The router [0056] 10_1 is connected to sub-networks 40_1 and 40_2 respectively through ports 0 and 1. The router 10_2 is connected to sub-networks 40_1 and 40_3 respectively through the ports 0 and 1.
  • The IP addresses of the sub-networks [0057] 40_1-40_3 are respectively (10.10.10.x), (10.10.11.x), and (10.10.12.x). The IP addresses of the ports 0 and 1 of the router 10_1 are respectively (10.10.10.1) and (10.10.11.1). The IP addresses of the ports 0 and 1 of the router 10_2 are respectively (10.10.10.2) and (10.10.12.1).
  • The network devices [0058] 10_1 and 10_2 transmit a management information notification packet 70 including the management information of their own devices to the network management device 20, e.g. (1) at a startup, (2) upon occurrence of an error, (3) when the management information is changed, or (4) periodically, as a predetermined event.
  • FIG. 4A shows an arrangement of the management [0059] information notification packet 70 transmitted by the network device 10_1. This packet 70 is composed of a MAC header 71, an IP header 72, a TCP header 73, a data field 74, and an FCS 75. Management information 76 is included in the data field 74.
  • FIG. 4B shows an example of the [0060] management information 76 shown in FIG. 4A. This management information 76 is described by XML format, and includes (1) icon of the network device 10_1 (Icon_ng.gif: image file while the device is normal), (2) port 0 of the network device 10 and its IP address=10.10.10.1, (3) port 1 and its IP address=10.10.11.1, (4) alarm information: failure of port 1, (5) display information: throughput transition graph (image file indicating throughput transition for last one minute), (6) attached file: Icon_ng.gif, and (7) attached file: throughput.gif.
  • In the network management device [0061] 20 (see FIG. 2), the network management processor 21 holds the management information 76 included in the management information notification packet 70 received from the packet receiver 27 in the management information storage 23.
  • The [0062] management information processor 24 refers to the management information storage 23 to execute a network management application. Namely, the management information processor 24 displays the following example (1) or (2): Display example (1): the management information received from each network device 10 is displayed on the display 25 sequentially tiled on the screen; Display example (2): the management information received from each network device is checked, and a logical connection of the network device 10 is determined based on a respective IP address (attribute is <di:IPAddr>) to be displayed as a network arrangement.
  • At this time, the [0063] management information processor 24 uses an image file designated by the attribute <di:Icon> within the received management information 76 for the network arrangement.
  • Also, when each icon of the network arrangement is clicked, the [0064] management information processor 24 makes the management information of the network device corresponding to the clicked icon displayed.
  • Furthermore, when the management information of the attribute <di:Alarm> is received and when “alarm is transmitted”, the [0065] management information processor 24 executes alarm transmission processings such as the followings (1)-(3): (1) Alarm sound is transmitted; (2) The device where an error has occurred is flashed on the screen; (3) Mail notification or the like is transmitted to the network administrator.
  • The [0066] management information processor 24 requests the management information generator 22 to inquire the network device to which a subsequent notification packet 70 has not reached even after a predetermined time has elapsed, from e.g. the network device which has been receiving the notification packet 70 so far. The management information generator 22 transmits a management information request packet 80. In the absence of the response thereto, the management information processor 24 determines that the network device 10 is down or failed.
  • Also, the [0067] management information processor 24 may request the management information generator 22 to transmit the management information request packet 80 to the network device according to the circumstances, after power-on, after a reset, at a specific time such as noon, or when determining that there is management information to be preferably obtained based on the obtained management information.
  • It is to be noted that while the XML is used in FIG. 4B, as an example of a description format of the management information, the description of the management information may be given by the HTML (Hyper Text Markup Language). However, since the HTML can not define the attribute, the management information processor [0068] 24 (network management application) only “displays sequentially tiled on the screen”, as mentioned in the above display example (1).
  • Also, as for the management information transmitted from the [0069] network device 10, a value can be changed depending on the then states, in which two kinds of icons indicating the normal state and the abnormal state, for example are prepared so that they can be included in the management information to be transmitted according to the states.
  • FIGS. [0070] 5A-5C show an example of a management screen displayed on the display 25. FIG. 5A shows a network composed of the network devices (routers) 10_1 and 10_2. FIG. 5B shows a screen displayed when the router 10_1 on the screen in FIG. 5A is clicked, in which the management information of the router 10_1, i.e. the icon of the router 10_1, an alarm indication indicating that the port 1 is down, and a throughput transition is displayed.
  • FIG. 5C shows, in the same way as FIG. 5B, a screen displayed when the router [0071] 10_1 on the screen of FIG. 5A is clicked. This screen indicates the case where the screen is simply displayed without interpreting the attribute of the management information described by the XML.
  • FIG. 6 is a flow chart showing an operation of the network device (router) [0072] 10.
  • FIG. 7 is a flow chart showing an operation of the network management device (server) [0073] 20.
  • FIG. 8 shows an example of an operation sequence between the network device [0074] 10_1 and the network management device 20. Hereinafter, this operation sequence will be described referring to FIGS. 6 and 7.
  • Step S[0075] 100: The power is turned “ON” in the router 10_1 (see step S200 in FIG. 6).
  • Step S[0076] 101: In the router 10_1 (see FIG. 1), the management information generator 12 transmits a management information notification packet 70_1 (hereinafter, occasionally represented by a reference numeral 70) including the management information of its own device, and starts a timer for periodical transmission (not shown in FIG. 1) (see step S201 in FIG. 6).
  • This timer for periodical transmission is for periodically transmitting the management information notification packet [0077] 70 (e.g. every one minute).
  • Step S[0078] 110: In the network management device 20 (see FIG. 2), the management information processor 24 receives the notification packet 70_1 through the packet receiver 27 (see step S300 in FIG. 7).
  • Also, the [0079] management information processor 24 registers the management information included in the notification packet 70_1 in the management information storage 23 and displays the same on the display 25 (see step S301 in FIG. 7). Furthermore, the management information processor 24 starts a monitoring timer (not shown in FIG. 2) (see step S302 in FIG. 7).
  • This monitoring timer is for monitoring whether or not the management [0080] information notification packet 70 is periodically received from the router 10_1.
  • Step S[0081] 102: When the timer for periodical transmission has timed out (see step S202 in FIG. 6), namely one minute after the transmission of the notification packet 70_1, the management information generator 12 transmits a notification packet 70_2 including the latest management information 76 of its own device, and restarts the timer for the periodical transmission (see step S201 in FIG. 6).
  • Step S[0082] 111: The management information processor 24 updates the management information of the router 10_1 stored in the management information storage 23 by the management information 76 included in the received notification packet 70 2, and displays the management information 76 on the display 25 (see steps S303 and S301 in FIG. 7). Furthermore, the management information processor 24 restarts the monitoring timer (see step S302 in FIG. 7).
  • Step S[0083] 103: Further one minute later, in the same way as step S102, the management information generator 12 transmits a notification packet 70_3 including the latest management information 76, and restarts the timer for periodical transmission (steps S202 and S201 in FIG. 6).
  • The operation in case where the notification packet [0084] 70_3 is lost on the way and so does not reach the network management server 20 will now be described.
  • Step S[0085] 112: In the network management server 20, the monitoring timer times out (steps S303 and S304 in FIG. 7). The management information generator 22 transmits the management information request packet 80 to the router 10_1 through the packet transmitter 26, and restarts the monitoring timer (see steps S305 and S302 in FIG. 7).
  • Step S[0086] 104: In the router 10_1, the management information generator 12 receives the request packet 80 through the packet receiver 16 (a predetermined event occurs), transmits a notification packet 70_4 including the management information of its own device to the network management server 20, and restarts the timer for periodical transmission (steps S203 and S201 in FIG. 6).
  • Step S[0087] 113: In the same way as step S110, the management information is displayed on the display 25 and the monitoring timer is started.
  • Steps S[0088] 105 and S114: In the same way as steps S102 and S111, the management information of the router 10_1 is transmitted by a notification packet 70_5 and displayed on the display 25 of the network management server 20.
  • It is to be noted that in the above-mentioned embodiment, the routers [0089] 10_1 and 10_2 in FIG. 3 are the network devices according to the present invention and the case where the network devices are managed by the network management device has been described above. However, clients 50_1 and 50_2 are provided with the network management processor for transmitting the management information of its own device by a format displayable on a browser to the network management device 20, whereby the network management device 20 can manage the clients 50_1 and 50_2.
  • As described above, a network device and a network management device according to the present invention are arranged such that a network management processor of the network device transmits management information of its own device in a format displayable on the browser, e.g. an XML or an HTML upon occurrence of a predetermined event, and a network management processor of the network management device displays the management information. Therefore, it becomes possible for the network device to easily transmit the management information of its own device to the network management device. [0090]
  • Also, the network device can transmit the optimal management information for the management of its own device, the unique management information, and the like by the optimal display format. Also, the network management device is provided with the minimum browser function, thereby enabling the network device to be managed. [0091]
  • Furthermore, it becomes possible for the network management device to manage e.g. the management information unique to a newly added network device without changing management applications. [0092]
  • More specifically, when new products of the network device are shipped, a new function is added to the network device, or the like, it was difficult to immediately reflect its new management information to the network management application. However, if the network device and the network management device of the present invention are used, it will be possible to perform a network management to the new management information in this case. [0093]
  • Also, since the management information is transmitted to the network management device under the initiative of the network device, the optimal management information for each network device, e.g. an icon according to each device, the management information concerning a support function unique to the network device, or the like can be displayed on the network management device. [0094]
  • Furthermore, the management of the network device can be realized without buying a network management device and a network management application with a high function. [0095]

Claims (12)

What we claim is:
1. A network device comprising:
a network management processor for preparing management information of its own device in a format displayable on a browser upon occurrence of a predetermined event; and
a transmitter for transmitting the management information.
2. The network device as claimed in claim 1 wherein the network management processor comprises a management information storage for holding the management information and a management information generator for generating management information of a format displayable on the browser based on the management information.
3. The network device as claimed in claim 1 wherein the format displayable on the browser comprises an HTML or an XML.
4. The network device as claimed in claim 1 wherein an attribute is added to the management information.
5. The network device as claimed in claim 1 wherein the occurrence of the predetermined event comprises at least one of a time of a startup, a time of a management information change, or a predetermined period.
6. The network device as claimed in claim 1 wherein the occurrence of the predetermined event comprises a time when a management information request packet is received from a network management device.
7. A network management device comprising:
a receiver for receiving management information of a format displayable on a browser transmitted from a network device upon occurrence of a predetermined event; and
a network management processor for displaying the management information.
8. The network management device as claimed in claim 7 wherein the network management processor has a management information storage for storing received management information of the format and a management information processor for displaying management information based on the management information.
9. The network management device as claimed in claim 7 wherein the network management processor generates a management information request packet requesting management information determined to be necessary and transmits the packet to the network device.
10. The network management device as claimed in claim 8, further comprising a management information generator for transmitting a management information request packet requesting the management information to the network device, when subsequent management information is not received from the network device after the management information of the network device is received and a predetermined time elapses.
11. The network management device as claimed in claim 8 wherein the management information processor displays each management information from a plurality of network devices respectively on a window screen corresponding to each network device.
12. The network management device as claimed in claim 8 wherein the management information processor displays the management information based on an attribute added to the management information of the format.
US10/269,540 2002-02-15 2002-10-11 Network device and network management device Abandoned US20030163582A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2002-039256 2002-02-15
JP2002039256A JP2003244151A (en) 2002-02-15 2002-02-15 Network apparatus and network management apparatus

Publications (1)

Publication Number Publication Date
US20030163582A1 true US20030163582A1 (en) 2003-08-28

Family

ID=27750445

Family Applications (1)

Application Number Title Priority Date Filing Date
US10/269,540 Abandoned US20030163582A1 (en) 2002-02-15 2002-10-11 Network device and network management device

Country Status (2)

Country Link
US (1) US20030163582A1 (en)
JP (1) JP2003244151A (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040267918A1 (en) * 2003-06-30 2004-12-30 Guarraci Brian J Managing headless computer systems
US20050091068A1 (en) * 2003-10-23 2005-04-28 Sundaresan Ramamoorthy Smart translation of generic configurations
US20050105132A1 (en) * 2003-11-17 2005-05-19 Canon Kabushiki Kaisha Device managing apparatus, method of controlling the same, and control program
US20050260987A1 (en) * 2004-05-20 2005-11-24 Telefonaktiebolaget L M Ericsson (Publ) Management information handling
US20060067343A1 (en) * 2004-09-30 2006-03-30 Brother Kogyo Kabushiki Kaisha Address information display system and address information display program
US7475351B1 (en) 2003-12-02 2009-01-06 Sun Microsystems, Inc. Interactive drag and snap connection tool
US9787539B2 (en) 2015-01-16 2017-10-10 Dell Products, Lp System and method for discovering a server on insertion into a network
US20230017725A1 (en) * 2020-04-07 2023-01-19 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Device state identification method and apparatus, and intelligent terminal

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006085623A (en) * 2004-09-17 2006-03-30 Toshiba Corp Web monitoring system, data processing method and monitored apparatus
KR20070052645A (en) * 2005-11-17 2007-05-22 삼성전자주식회사 Apparatus and method for managing user interface

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6308205B1 (en) * 1998-10-22 2001-10-23 Canon Kabushiki Kaisha Browser-based network management allowing administrators to use web browser on user's workstation to view and update configuration of network devices
US20030028624A1 (en) * 2001-07-06 2003-02-06 Taqi Hasan Network management system
US20030237018A1 (en) * 2002-06-25 2003-12-25 Hitachi, Ltd. Server takeover system and method
US20040267103A1 (en) * 2001-10-22 2004-12-30 Luya Li Physiological parameter monitoring system and sensor assembly for same
US7028081B2 (en) * 1998-10-21 2006-04-11 Canon Kabushiki Kaisha Network-device management apparatus and method, recording medium, and transmission apparatus

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7028081B2 (en) * 1998-10-21 2006-04-11 Canon Kabushiki Kaisha Network-device management apparatus and method, recording medium, and transmission apparatus
US6308205B1 (en) * 1998-10-22 2001-10-23 Canon Kabushiki Kaisha Browser-based network management allowing administrators to use web browser on user's workstation to view and update configuration of network devices
US20030028624A1 (en) * 2001-07-06 2003-02-06 Taqi Hasan Network management system
US20040267103A1 (en) * 2001-10-22 2004-12-30 Luya Li Physiological parameter monitoring system and sensor assembly for same
US20030237018A1 (en) * 2002-06-25 2003-12-25 Hitachi, Ltd. Server takeover system and method

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040267918A1 (en) * 2003-06-30 2004-12-30 Guarraci Brian J Managing headless computer systems
US7424525B2 (en) * 2003-06-30 2008-09-09 Microsoft Corporation Managing headless computer systems
GB2408407B (en) * 2003-10-23 2006-05-24 Hewlett Packard Development Co Smart translation of generic configurations
GB2408407A (en) * 2003-10-23 2005-05-25 Hewlett Packard Development Co Network management with translation from generic to vendor-specific network policies
US20050091068A1 (en) * 2003-10-23 2005-04-28 Sundaresan Ramamoorthy Smart translation of generic configurations
US20050105132A1 (en) * 2003-11-17 2005-05-19 Canon Kabushiki Kaisha Device managing apparatus, method of controlling the same, and control program
US8233171B2 (en) * 2003-11-17 2012-07-31 Canon Kabushiki Kaisha Device managing apparatus, method of controlling the same, and control program
US7475351B1 (en) 2003-12-02 2009-01-06 Sun Microsystems, Inc. Interactive drag and snap connection tool
US20050260987A1 (en) * 2004-05-20 2005-11-24 Telefonaktiebolaget L M Ericsson (Publ) Management information handling
US7343376B2 (en) * 2004-05-20 2008-03-11 Telefonaktiebolaget L M Ericsson (Publ) Management information notification to a manager in a management system
US20060067343A1 (en) * 2004-09-30 2006-03-30 Brother Kogyo Kabushiki Kaisha Address information display system and address information display program
US7644154B2 (en) * 2004-09-30 2010-01-05 Brother Kogyo Kabushiki Kaisha Address information display system and address information display program
US9787539B2 (en) 2015-01-16 2017-10-10 Dell Products, Lp System and method for discovering a server on insertion into a network
US20230017725A1 (en) * 2020-04-07 2023-01-19 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Device state identification method and apparatus, and intelligent terminal

Also Published As

Publication number Publication date
JP2003244151A (en) 2003-08-29

Similar Documents

Publication Publication Date Title
US7398307B2 (en) Method and system for managing a network
JP4018638B2 (en) Method for providing topology awareness information in an IP network
US20030028577A1 (en) HTTP distributed XML-based automated event polling for network and E-service management
US8549119B1 (en) Error handling for device management configuration and operational data retrieval commands
JP5079917B2 (en) Method for monitoring events in a communication network
US6992985B1 (en) Method and system for auto discovery of IP-based network elements
JP2011254196A (en) Network system, network management device, and gateway device
US20030163582A1 (en) Network device and network management device
US20080228907A1 (en) Change detecting method for an it resource configuration
US7457866B1 (en) Method and apparatus for diagnosing connectivity problems from a network management station
CN114553867A (en) Cloud-native cross-cloud network monitoring method and device and storage medium
CA2987316A1 (en) Local object instance discovery for metric collection on network elements
Cisco Configuring Simple Network Management Protocol (SNMP)
Cisco Chapter 7 Command Line Interface Command Reference
Cisco Configuring Network Management
Cisco Configuring Simple Network Management Protocol (SNMP)
Cisco Configuring Network Management
Cisco Monitoring the System
Cisco In-Band Management
Cisco In-Band Management
Cisco Index: Cisco&nbsp;IOS Configuration&nbsp;Fundamentals Configuration&nbsp;Guide, Release&nbsp;12.2
Cisco Network Monitoring Using Cisco Service Assurance Agent
Cisco Configuring Network Management
Cisco In-Band Management
Cisco In-Band Management

Legal Events

Date Code Title Description
AS Assignment

Owner name: FUJITSU LIMITED, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:INOUE, RUMIKO;TSUCHIYA, SATOSHI;TAKEDA, KOICHI;REEL/FRAME:013393/0970;SIGNING DATES FROM 20020919 TO 20020926

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION