WO2009006834A1

WO2009006834A1 - Method of network element managing, system of network element equipment managing and system of network element managing

Info

Publication number: WO2009006834A1
Application number: PCT/CN2008/071546
Authority: WO
Inventors: Xiaoxia Feng; Zejun Luo; Hongfang Ren
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-07-06
Filing date: 2008-07-04
Publication date: 2009-01-15
Also published as: CN101079745A; CN101079745B

Abstract

A method of network element managing is disclosed, including: establishing maintaining channels between a network element equipment management system and a network element equipment as well as between the network element equipment management system and a inner connection equipment separately (S101); the network element equipment management system managing the network element by the established maintaining channel between the network element equipment management system and the network element equipment, and the network element equipment management system managing the inner connection equipment by the established maintaining channel between the network element equipment management system and the inner connection equipment (S102). A system of network element equipment managing and a system of network element managing are disclosed.

Description

Network element management method, network element equipment management system and network element management system

This application claims the priority of the Chinese Patent Application filed on July 6, 2007 by the Chinese Patent Office, Application No. 200710126079.2, and the invention titled "Network Element Management Method, Network Element Equipment Management System and Network Element Management System". The content is incorporated herein by reference.

Technical field

The present invention relates to network management technologies, and in particular, to network element management technologies.

Background technique

Generally, a network element device can be configured to include three parts: a rack, a chassis, and a single board. A switch or other connecting device can be disposed between the racks, between the chassis, or between the boards. To connect two racks, chassis, or boards, we refer to this type of connected device as an internal connected device. Here, for convenience of description, the network element device and the connected device are collectively referred to as a network element.

In the core network area, the local maintenance terminal system or the network management system is generally used to maintain and manage the network element equipment. The local maintenance terminal system mainly manages a single network element device. The functions normally provided by this system include: configuration function, alarm function, tracking function, and device panel function. The network management system mainly implements centralized management of all network element devices in the network. Here, for convenience of description, the local maintenance terminal system and the network management system are collectively referred to as a network element device management system.

After careful analysis and careful study, the inventor found that: Currently, the NE device management system can only manage NE devices, but not internal devices. In practical applications, the internal connected devices are generally managed by the maintenance system that comes with the internal connected devices. The management of network element devices and internal connected devices is generally performed separately. This requires network administrators or maintenance personnel to be familiar with and use both systems to complete management of all network elements. This will inevitably increase the complexity of network element management. degree.

Summary of the invention

The technical problem to be solved by the embodiments of the present invention is to provide a network element management method, a network element device management system, and a network element management system, so as to reduce the complexity of network element management.

To solve the above problem, the present invention provides an embodiment of a network element management method, including: establishing a maintenance channel between a network element device management system and a network element device, and between the network element device management system and an internal connected device, respectively. The network element device management system manages the network element device through a maintenance channel established between the network element device and the internal connection through a maintenance channel established between the internal device and the internal connected device. The device is managed.

The present invention further provides an embodiment of a network element device management system, including: a maintenance channel establishing unit, configured to respectively establish a maintenance channel with the network element device and the internal connected device; and a device management unit, configured to establish a unit by using the maintenance channel The maintenance channel established between the NE and the NE device manages the NE device and manages the internal device through the maintenance channel established between the device and the internal device.

The present invention further provides an embodiment of a network element management system, including a network element device management system, a network element device, and an internal connection device, wherein the network element device management system is separately set between the network element device management system and the network element device and the internal connection device. There is a maintenance channel. The network element device management system manages the network element device through a maintenance channel set up between the network element device and the internal connection device through a maintenance channel set between the internal device and the internal connection device.

The present invention further provides an embodiment of a network element management system, including a network element device management system, a network element device, and an internal connection device, wherein the network element management system further includes a post management device, wherein the network element device management system A first maintenance channel is disposed between the rear management device and the network element device and the internal connection device, and the second maintenance channel and the third maintenance channel are respectively disposed between the rear management device and the internal management device; The network element device management system manages the network element device and the internal connection device through the second maintenance channel and the third maintenance channel respectively through the command issued by the first maintenance channel; the rear management device also connects the network element device and the internal connection The information sent by the device through the second maintenance channel and the third maintenance channel is provided to the network element device management system through the first maintenance channel.

The present invention further provides an embodiment of a network element management system, including a network element device management system, a network element device, and an internal connection device, where the network element device management system and the network element device are provided with a first maintenance channel, and the network A second maintenance channel is disposed between the meta-device and the internal connection device, where the network element device management system manages the network element device by using the first maintenance channel, and the network element device management system passes the first maintenance channel and the The second maintenance channel manages internal connected devices.

In the embodiment of the present invention, since the maintenance channel is set between the network element device management system and the network element device and the internal connection device, the network element device management system can uniformly manage the network element device and the internal connection device to avoid The two management systems are used to manage the network element device and the internal connection device respectively, which reduces the complexity of the network element management.

DRAWINGS

1 is a flowchart of an embodiment of a network element management method according to the present invention; 2 is a flowchart of obtaining, by the network element device management system, fault information about an internally connected device according to an embodiment of the present invention;

FIG. 3 is a flowchart of configuring an internal connected device by issuing a general command by a network element device management system according to an embodiment of the present invention;

4 is a schematic structural diagram of a network element device management system according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a first structure of an embodiment of a network element management system according to the present invention; FIG.

6 is a second schematic structural diagram of an embodiment of a network element management system according to the present invention;

FIG. 7 is a schematic diagram of a third structure of an embodiment of a network element management system according to the present invention.

detailed description

The present invention provides various embodiments such as a network element management method, a network element device management system, and a network element management system. These embodiments will be respectively described below with reference to the accompanying drawings. As shown, including:

Step S101: Establish a maintenance channel between the network element device management system and the network element device, and between the network element device management system and the internal connected device. The network element device here may be a Universal Media Gateway (UMG), a softswitch device or a Home Location Register (HLR), and the internal connection device may be a switch.

There are many ways to establish a maintenance channel. For example, you can use Telnet (a member of the TCP/IP protocol suite, which is the standard protocol and main method of Internet remote login service, which is the login and emulation program of TCP/IP network). You can also use the Simple Network Management Protocol (SNMP). Of course, you can also use other methods to establish maintenance channels.

In addition, a direct maintenance channel can be established between the NE device management system and the internal connected device, or a transit maintenance channel can be established between the NE device management system and the internal connected device through other devices. For example, a maintenance channel is established between the network element device management system and a device, and a maintenance channel is established between the device and the internal connected device, which is equivalent to having a network device management system and an internal connected device. The maintenance channel, more specifically, the device between the network element device management system and the internal connection device may be a network element device, that is, a maintenance channel is established between the network element device management system and the network element device. Established between the NE device and the internal connected device A maintenance channel is equivalent to having a maintenance channel between the network element device management system and the internal connected device. Certainly, the maintenance channel established between the network element device management system and the network element device may also be a direct maintenance channel or a transit maintenance channel.

In a practical application, the maintenance channel established between the NE device management system and the NE device may be the same as or different from the maintenance channel established between the NE device management system and the internal connected device. For example, one maintenance channel can be established by using the Telnet command. Another maintenance channel can be Telnet or SNMP. One maintenance channel can be a direct maintenance channel. The other maintenance channel can be a direct maintenance channel or a transit maintenance channel.

In addition, multiple maintenance channels can be established between the network element device management system and the network element device, or between the network element device management system and the internal connected device. These maintenance channels can be established in the same manner. It can be established in different ways. These maintenance channels can be either direct maintenance channels or transit maintenance channels, or both direct maintenance channels and relay maintenance channels.

In summary, the manner and type of the maintenance channel established between the network element device management system and the network element device, and the manner and type of the maintenance channel established between the network element device management system and the internal connected device may be arbitrarily selected or combined, as long as Ensure that an effective maintenance channel can be established between the NE device management system and the NE device and between the NE device management system and the internal connected device.

Step S102: The network element device management system manages the network element device by using a maintenance channel established between the network element device and the internal connection device by using a maintenance channel established between the network element device and the internal connection device.

In the prior art, the network element device management system has been able to manage the network element device. Therefore, how the network element device management system manages the network element device is not described herein.

In practice, internal connected devices may malfunction. If the internal connected device fails, the internally connected device can directly report the fault information through the maintenance channel or directly report the alarm information. The NE device management system can monitor the internal connected device. If the internal connected device is abnormal, the NE device management system can generate alarm information. In addition, if the maintenance channel set between the network element device management system and the internal connected device is a transit channel, at least one device disposed between the network element device management system and the internally connected device can also monitor the internally connected device. If this or these devices find that the internal connected device is not operating properly, then this or These devices can report information about the fault to the network element device management system or report the alarm information directly. In addition, if the maintenance channel set between the network element device management system and the internal connected device is a transit channel, at least one device disposed between the network element device management system and the internally connected device may also pass the maintenance channel according to the internally connected device. The directly reported information about the fault or the alarm information directly reported is reported to the network element device management system for information about the fault or directly reports the alarm information.

The flow chart shown in Figure 2 is taken as an example to illustrate how the network element device management system obtains fault information about the internally connected device. As shown in Figure 2, the maintenance channel between the NE device management system and the internal connected device is the transit channel, and the rear management device acts as the transit device.

As shown in Figure 2, if the state of the internally connected device changes, the internal connected device notifies the post-management device of its own state change information. After receiving the notification of the internally connected device, the management device encapsulates the state change information into an alarm message. The management device then sends the alarm information to the network element device management system. The process of how the network element device management system shown in FIG. 2 obtains the fault information about the network element device is not described here.

In addition, you can define the following types of alarms for internal connected devices according to the status changes of the internal connected devices: No. Alarm Name Description

1 port negotiation alarm

2 Internal connection device communication is interrupted Maintenance between the management device and the internal connected device Physical interruption occurs in the channel

3 Internal connection device communication interruption recovery After maintenance between the management device and the internal connected device The channel changes from interrupt to normal

4 Internally connected device cold start The internal connected device performs a cold start operation

5 Internally connected device hot start The internal connected device performs a warm start operation

The 6-port link is disconnected. The link of a port of the internal connected device is disconnected.

7-port link disconnected restores the link of a port of an internally connected device from disconnected to restored 8-port migration to blocking state The state of a port connected to the internal device becomes blocked.

9 port migration to forwarding state The status of a port on an internal connected device changes to the forwarding state

10 Internal connection device configuration has changed The configuration of the internal connection device has changed.

Table 1

The types of alarms shown in Table 1 are just a few examples of alarms. Those skilled in the art can define various types of alarms according to actual needs.

After receiving the information about the fault or the alarm information, the NE device management system can respond. For example, the alarm is masked, or information about the fault or alarm information is analyzed for fault location.

The description of the above-mentioned processing alarm is only one way for the network element device management system to manage the internal connection device. In practical applications, the network element device management system can manage the internal connection device in multiple ways.

For example, the network element device management system can remotely query the running status of the internally connected device, and display the running status on the simulation panel, wherein the simulation panel can display the running status and port performance of the internally connected device. The running status of the internal connected device may include the operating parameters of the internal connected device, the power supply situation, etc. The running state displayed by the simulation panel may be in various forms. When the running state of the internally connected device changes, the running state displayed by the simulation panel may also be Change accordingly. In addition, after the NE device management system queries the running status of the internally connected device, it can also analyze the running status according to this, and can also perform fault location. For example, if the current voltage of the internally connected device is low, the corresponding operation can be performed. The analysis determines which one or which of the links has an abnormality.

The NE device management system can also query the performance data of each port of the internal connected device for status analysis and fault location.

According to the maintenance and management requirements of the internal connected devices, the performance data of the internally connected device ports can be classified into the following categories: number of bytes received by the port, number of bytes sent by the port, number of unicast packets received by the port, and multicast packets received by the port. The number of broadcast packets received by the port, the number of broadcast/multicast packets received by the port, the number of received packets discarded by the port due to an error, the number of received packets discarded by the port due to protocol problems, and the number of packets sent by the port. The number of unicast packets, the number of multicast packets sent by the port, and the broadcast packets sent by the port. The number of packets, the number of packets that cannot be sent due to an error, the transmission bandwidth utilization of the port, and the receiving bandwidth utilization of the port.

If a port should be physically connected and the result of the query is not connected, you can initially determine that the connection to the port is abnormal. Specifically, the port performance data can be counted by using the cumulative mode. When querying the accumulated value of a port for a period of time, the performance data of a port can be cleared first by the clear function. Thereafter, the performance of the port is performed. The data will be accumulated from zero, and the network element device management system can determine whether the connection of the port is abnormal by means of such data analysis.

The performance data of the ports displayed on the emulation panel can take many forms. When the performance data of the port changes, the port performance displayed by the emulation panel can also be changed accordingly. For example, the performance data of each port can be displayed in a graphical manner, and the time period can be set according to actual needs, for example, 5 minutes, 30 minutes, and the like. The network element device management system can accumulate data in each time period, and the accumulated data can be used as a data point. Finally, at the start and end points of the specified time, the statistical data points are graphically displayed on the simulation panel.

The NE device management system can also query the running performance log of the internally connected device and/or the historical performance data of the port to backtrack the faults that occur. For example, if an abnormal situation such as power failure occurs and the NE device management system needs to be restarted, after the NE device management system is started, the NE device management system can query the history of the connected devices, so that the query can be performed. When the internal connected device is monitored, the internal connected device is abnormal.

The NE device management system can also remotely configure internal connected devices by issuing common commands. Specifically, if the maintenance channel between the network element device management system and the internal connection device is a direct maintenance channel, the network element device management system can directly send the command to the internal connection device, and after the internal connection device receives the command, according to the If the maintenance channel between the NE device management system and the internal connected device is a transit channel, the NE device management system can send the command between the NE device management system and the internal connected device. One or more devices, this or these devices configure internal connected devices according to these commands.

The following uses the flowchart shown in FIG. 3 as an example to describe how the network element device management system configures the internal connected device by issuing a general command. As shown in FIG. 3, the maintenance channel between the network element device management system and the internal connected device is a transit channel, and the rear management device acts as a transit device. As shown in Figure 3, the NE device management system issues a configuration command. After receiving the configuration command, the management device parses the command and configures the internal connected device according to the analysis result. The process of configuring the internal connected device by issuing a common command in the network element device management system shown in FIG. 3 is not described here.

The above describes the method embodiment of the present invention. It is not difficult to see from the above method embodiment that the network element device management system plays an important role in establishing the maintenance channel or managing the internal connected device. Thus, the present invention also provides an embodiment of a network element device management system.

An embodiment of a network element device management system, as shown in FIG. 4, includes: a maintenance channel establishing unit 401, configured to respectively establish a maintenance channel with a network element device and an internal connected device; and a device management unit 402, configured to pass the maintenance channel The maintenance channel established between the establishing unit 401 and the network element device manages the network element device, and manages the internal connected device through a maintenance channel established between the internal connected device and the internal connected device.

There are many ways to establish a maintenance channel. For example, you can use Telnet commands or SNMP. Of course, you can use other methods to establish maintenance channels.

In addition, the maintenance channel establishing unit 401 can establish a direct maintenance channel with the internal connected device, and can also establish a relay maintenance channel between the other device and the internal connected device.

The manner and type of the maintenance channel established between the maintenance channel establishment unit 401 and the network element device and the internal connection device can be arbitrarily selected or combined, as long as an effective maintenance channel is established between the network element device and the internal connection device.

The device management unit 402 may include: a network element device management unit, configured to manage the network element device; and an internal connection device management unit, configured to manage the internal connected device.

The internal connected device management unit can be composed in many different ways.

An internal connection device management unit may include: a monitoring unit configured to perform real-time monitoring on the internal connected device; and a data collecting unit configured to collect operation state data of the internal connected device according to monitoring of the internally connected device by the monitoring unit And performance data of each port; an emulation panel management unit, configured to display the running status and/or the performance of each port in the simulation panel according to the running state data collected by the data collecting unit and/or the performance data of each port The simulation panel is configured to display an operating state and a port performance of the internal connected device.

An internal connection device management unit may include: a monitoring unit, configured to connect internal devices Real-time monitoring; a data collecting unit, configured to collect operating state data of the internal connected device and/or performance data of each port according to the monitoring of the internally connected device by the monitoring unit; and a fault locating unit, configured to collect data according to the data The operational status data collected by the unit and/or the performance data of each port locates the fault.

The internal connection device management unit may include: a history query unit, configured to query an operation log of the internal connection device and/or historical performance data of the port; a fault backtracking unit, configured to run the log according to the history record query unit And/or historical performance data of the port, backtracking historical faults.

An internal connection device management unit may include: a general command issuing unit for issuing a general command; and a remote configuration unit configured to remotely configure the internal connected device according to the general command issued by the universal command issuing unit.

It should be noted that the above several internal connected device management units may exist independently or may be combined to form a new internal connected device management unit, so that the combined internal connected device management unit has multiple functions.

In addition, the device management unit 402 may further include: an interface management unit, configured to provide an interface for integrating the device panel of the network element device and the simulation panel of the internal connected device. If the device panel of the NE device and the emulation panel of the internal connected device are integrated on one interface, the maintenance personnel can view the running status of the NE device and the internal connected device at the same time, and manage the NE at the same time. Equipment and internal connected equipment.

What has been described above is an embodiment of the method and a network element device management system of the present invention. These embodiments can be applied to the network element management system. Therefore, the present invention also provides an embodiment of the network element management system.

The traditional network element management system includes the network element device management system, the internal connection device's own maintenance system, the network element device and the internal connection device, the network element device management system management network element device, and the internal connection device's own maintenance system management internal. Connect the device.

An embodiment of the network element management system provided by the present invention is as shown in FIG. 5, and includes a network element device management system 501, a network element device 502, and an internal connection device 503, wherein the network element device management system 501 and the network element device 502 and A maintenance channel is provided between the internal connection devices 503, and the network element device management system 501 can manage the network element device through a maintenance channel set between the network element device and the network element device. The internal connection device 503 is managed by a maintenance channel provided between the internal connection device. There are several ways to set the maintenance channel. For example, you can use the Telnet command or SNMP. Of course, you can use other methods to set the maintenance channel.

In a practical application, the maintenance channel set between the network element device management system 501 and the network element device 502 and the maintenance channel set between the network element device management system 501 and the internal connection device 503 may be the same or different. For example, one of the maintenance channels can be set using the Telnet command mode, and the other maintenance channel can be set using the Telnet command or SNMP mode.

In addition, between the network element device management system 501 and the network element device 502, or between the network element device management system 501 and the internal connection device 503, multiple maintenance channels can be set, and the maintenance channels can be set in the same manner. , can also be set in different ways.

Since the network element device management system 501 has been able to manage the network element device 502 in the prior art, how the network element device management system 501 manages the network element device 502 is not described herein.

In practice, the internal connected device 503 may malfunction. If the internal connected device 503 fails, the internal connected device 503 can directly report the information about the fault through the maintenance channel or directly report the alarm information. Of course, the network element device management system 501 can monitor the internal connection device 503. If the internal connection device 503 is found to be abnormal, the network element device management system 501 can generate alarm information.

In addition, the following types of alarms can be defined for the internal connected device 503 according to the state change of the internal connected device 503: No. Alarm Name Description

1 port negotiation alarm

2 Internal connection device 503 Communication interruption The maintenance channel between the internal connection device 503 and the biological channel is interrupted.

3 Internally connected device 503 Communication interruption The maintenance channel between the internal connection device 503 and the internal connection device is changed from recovery interrupt to normal.

4 Internal connection device 503 cold start Internal connection device 503 performs a cold start operation

5 Internal connection device 503 Warm start Internal connection device 503 performs a warm start operation

6-port link disconnects internal connection device 503 link of a port occurs Disconnected

7-port link disconnection recovery Internally connected device 503 Link to a port changed from disconnected to restored

8-port migration to blocking status Internally connected device 503 The status of a port becomes blocked

9 Ports are migrated to the forwarding state Internally connected devices 503 The status of a port changes to the forwarding state

10 Internally connected devices 503 configuration occurred Internal connection device 503 configuration changed

Variety

Table 2

The types of alarms shown in Table 2 are just a few examples of alarms. Those skilled in the art can define various types of alarms according to actual needs.

After receiving the information about the fault or the alarm information, the network element device management system 501 can respond. For example, the alarm is shielded, or information about the fault or alarm information is analyzed for fault location.

In addition, the network element device management system 501 can remotely query the running status of the internal connected device 503, and display the running status on the simulation panel. The operating state of the internal connecting device 503 may include operating parameters of the internal connecting device 503, power supply conditions, etc., and the operating state displayed by the simulation panel may have various forms. When the running state of the internal connecting device 503 changes, the operation of the simulation panel is displayed. The status can also be changed accordingly. In addition, after the network element device management system 501 queries the running state of the internal connection device 503, the operating state can be analyzed according to the operation state, and the fault location can also be performed. For example, if the current voltage of the internal connection device 503 is low, Corresponding analysis can be performed to determine which segment or nodes have anomalies.

The NE device management system 501 can also query the performance data of each port of the internal connected device 503 for state analysis and fault location.

According to the maintenance management requirements of the internal connection device 503, the performance data of the port of the internal connection device 503 can be classified into the following categories: the number of bytes received by the port, the number of bytes sent by the port, the number of unicast packets received by the port, and the number of ports received. The number of broadcast packets, the number of broadcast packets received by the port, the number of broadcast/multicast packets received by the port, the number of received packets discarded by the port due to an error, and the loss of the port due to a protocol problem. The number of discarded packets, the number of unicast packets sent by the port, the number of multicast packets sent by the port, the number of broadcast packets sent by the port, the number of packets that cannot be sent due to an error, and the transmission bandwidth utilization of the port. , the receiving bandwidth utilization of the port, and so on.

If a port should be physically connected and the result of the query is not connected, you can initially determine that the connection to the port is abnormal. Specifically, the port performance data can be counted by using the cumulative mode. When querying the accumulated value of a port for a period of time, the performance data of a port can be cleared first by the clear function. Thereafter, the performance of the port is performed. The data will be accumulated from zero, and the network element device management system 501 can determine whether the connection of the port is abnormal by means of such data analysis.

The performance data of the ports displayed on the emulation panel can take many forms. When the performance data of the port changes, the port performance displayed by the emulation panel can also be changed accordingly. For example, the performance data of each port can be displayed in a graphical manner, and the time period can be set according to actual needs, for example, 5 minutes, 30 minutes, and the like. The network element device management system 501 can accumulate data in each time period, and the accumulated data can be used as a data point. Finally, at the start and end points of the specified time, the statistical data points are graphically displayed on the simulation panel.

The network element device management system 501 can also query the running log of the internal connected device 503 and/or the historical performance data of the port to backtrack the faults that occur. For example, if an abnormality such as a power outage occurs, and the network element device management system 501 needs to be restarted, after the network element device management system 501 is started, the network element device management system 501 can query the history of the internal connection device 503, so that the network element The device management system 501 can query whether the internal connection device 503 is abnormal when the internal connection device 503 is not monitored.

The network element device management system 501 can also remotely configure the internal connected device 503 by issuing a general command. Specifically, the network element device management system 501 can directly send the command to the internal connection device 503. After receiving the command, the internal connection device 503 performs corresponding operations according to the command.

The embodiment shown in FIG. 5 is only one embodiment of the network element management system of the present invention. In practical applications, the implementation form of the network element device management system is not limited to the form shown in FIG. 5.

Therefore, the present invention also provides an embodiment of a second network element management system. As shown in FIG. 6, the embodiment of the network element management system includes a network element device management system 601, a network element device 602, an internal connection device 603, and a post management device 604, wherein the network element device management system 601 and the post management device are 604 A first maintenance channel is disposed between the rear management device 604 and the network element device 602 and the internal connection device 603, and the second maintenance channel and the third maintenance channel are respectively disposed. The post management device 604 can be managed according to the network element device. The system 601 manages the network element device 602 and the internal connection device 603 through the second maintenance channel and the third maintenance channel respectively through the command issued by the first maintenance channel. The post management device 604 also connects the network element device 602 and the internal connection device 603. The information sent by the second maintenance channel and the third maintenance channel is respectively provided to the network element device management system 601 through the first maintenance channel.

The maintenance channel can be configured in various ways. For example, you can use the Telnet command or the SNMP mode. Of course, you can use other methods to set the maintenance channel.

In the actual application, the maintenance channel set between the network element device management system 601 and the post-management device 604, the maintenance channel set between the post-management device 604 and the network element device 602, and the post-management device 604 and the internal connection device 603 are set. The maintenance channels can be the same or different. For example, one of the maintenance channels can be set using the Telnet command mode. Other maintenance channels can be set using the Telnet command or SNMP mode.

As described above, since the maintenance channel is set between the network element device management system 601 and the rear management device 604, a maintenance channel is set between the rear management device 604 and the network element device 602 and the internal connection device 603, so that it is equivalent to the network element. A maintenance channel is set between the device management system 601 and the network element device 602 and the internal connection device 603. The network element device management system 601 can perform unified management on the network element device 602 and the internal connection device 603 through the maintenance channel.

The post management device 604 can have the following functions:

(1) The internal connection device 603 is monitored in real time through the interface mechanism provided by the internal connection device 603, and a set of alarm types for the internal connection device 603 is encapsulated according to the change of the state of the internal connection device 603, and is managed to the network element device. The system 601 actively reports relevant alarm information.

(2) The internal connection device 603 is monitored in real time through the interface mechanism provided by the internal connection device 603, the operational status data of the internal connection device 603 is collected, and the operational status data is provided to the network element device management system 601.

(3) The internal connection device 603 provides real-time monitoring of each port of the internal connection device 603, collects performance data of each port, and provides the performance data to the network element device management system 601.

(4) Obtaining the internal connection device 603 through the interface mechanism provided by the internal connection device 603 The historical performance data of the log and the port is run, and the historical performance data of the running log and the port is provided to the network element device management system 601.

(5) The common command sent by the network element device management system 601 is received, and the internal connected device 603 is configured according to a general command.

The network element device management system 601 can have the following functions:

(1) The simulation panel is used to display the related situation of the internal connection device 603. Further, the simulation panel and the device panel of the network element device 602 can be integrated into one interface display.

(2) The alarm display function is provided, and the alarm information of the internal connected device 603 and the alarm information of the network element device 602 are displayed in a unified form.

(3) The performance of each port of the internal connection device 603 is displayed, and the performance data of each port of the internal connection device 603 can also be analyzed.

(4) Query the running log of the internal connected device 603 and the historical performance data of the port, and determine whether the internal connected device 603 has failed and specific information of the fault.

(5) A general command is issued to manage the internal connected device 603.

It should be noted that the manner in which the network element device management system 601 manages the network element device 602 through the post-management device 604 can be the same as the manner in which the internal connection device 603 is managed by the post-management device 604, and details are not described herein again.

Except for the implementation of the network element management system shown in FIGS. 5 and 6, the present invention also provides an embodiment of the third network element management system as shown in FIG. As shown in FIG. 7, the embodiment of the network element management system includes a network element device management system 701, a network element device 702, and an internal connection device 703. The network element device management system 701 and the network element device 702 are disposed between A first maintenance channel is provided between the network element device 702 and the internal connection device 703. The network element device management system 701 manages the network element device 702 through the first maintenance channel, and the network element device management system 701 passes the first maintenance. The channel and the second maintenance channel manage the internal connection device 703.

The working mode between the type and setting mode of the maintenance channel, the network element management system 701 and the network element device 702 and the internal connection device 703 are basically the same as those of the embodiment shown in FIG. 5, except that the network element management system is only The management of the internal connection device 703 by the 701 needs to be relayed via the network element device 702.

In all the above embodiments, the internal connection device may be an internal data communication device, and the network element device management system manages the internal connection device through a maintenance channel between the internal connection device. It may include at least one of alarm management, security management, performance management, log management, and configuration management.

a. Alarm management

The monitoring of the status of the data communication device can be divided into two cases:

(1) The internal data communication device detects the occurrence of a specific event, and reports the event to the network element device management system through the maintenance channel between the internal data communication device and the network element device management system. The network element device management system parses the reported information or After the conversion and other processing, the processed information is sent to the user's operation and maintenance terminal display, so that the user can know the events occurring on the internal data communication device in time, so as to take corresponding measures.

(2) The network element device management system periodically sends instructions to the data communication device according to a certain policy or mechanism, such as a timing mechanism, obtains state information, and then parses or converts the obtained state information to be sent to the user. The operation and maintenance terminal displays that the working state of the internal data communication device is placed under the control of the user.

The alarm has its fixed format and level. The occurrence of the alarm and the clearing of the corresponding alarm are implemented through a certain association mechanism. The alarm content is shown in Table 3:

No. Alarm Name Type Level

1 Ethernet switch communication interruption Fault alarm Main

2 Ethernet switch communication recovery recovery alarm

3 There is a network cable crossing between the network planes. Fault alarm. The network cable cross between the network planes.

4 Recovery alarm Main

Recovery

5-port negotiation alarm event alarm

6 Ethernet interface link disconnection Fault alarm Main Ethernet interface link disconnected

7 Recovery alarm Main

8-port migration is a blocked state fault alarm. 9 port migration is the forwarding state recovery alarm.

10 Configuration changes Event alarm Main

11 Ethernet Switch Cold Start Event Alarm Main

12 Ethernet Switch Hot Start Event Alarm Main

table 3

b. Security management

Security management provides an effective control mechanism to restrict access to internal data access devices for user access and access operations, ensuring that each legitimate user can log in normally, use authorized software modules, and operate legal-level commands to prevent unauthorized access. In order to ensure the safe operation of network equipment, and to account for authentication, authorized access and other operations, the operation is non-repudiation. c. Performance management

In order to monitor the operation of the internal data communication device, performance management functions are required. Obtain the running information (various statistics) of the internal data communication device through SNMP.

The management content is shown in Table 4:

The name iflnUnknownProtos is caused by the protocol not recognized or not supported.

7

Number of lost packets

8 ifOutMulticastPkts The number of multicast packets sent to the underlying protocol

9 ifOutBroadcastPkts Number of broadcast packets sent to the underlying protocol

10 total number of bytes sent on the ifOutOctets port

11 ifOutUcastPkts Number of unicast packets sent to the underlying protocol

12 ifOutErrors Total number of discarded packets due to errors, high error rate indicates hardware problems

13 CpuCostRatePerlMin 1 minute CPU usage

14 MemFree free memory Table 4 d. Log management

In order to make some cases in the operation of the internal data communication device and the operation of the user well documented, it is necessary to provide a log function. The running log of the internal data communication device is obtained through the standard Syslog protocol. The log related settings need to be set to the internal data communication device in advance. The NE device management system needs to provide logs related to the internal data processing device: system logs, operation logs, security logs, and related management operations such as log settings, query, backup, and acquisition. e. Configuration Management

You need to perform the necessary configuration management for the internal data communication device. The configuration management is mainly related to the operation of the port and IP address. The rest of the configuration management is implemented by Telnet for security authentication.

Configuration management content includes: port-related operations; device basic information query; configuration maintenance frequency can be configured. Port-related operations such as activation/deactivation, query port operation mode.

Embodiment of network element management method, network element equipment management system and network element management system of the present invention The network element device management system can manage the network element device, and the network element device management system can manage the network element device in the embodiment. Meta-devices and internal connected devices. In the prior art, the network element device management system can only manage the network element device, and the management and maintenance personnel can only manage the network element device and the internal connected device separately, which requires the management and maintenance personnel to be familiar with the network element device management system at the same time. The internal connection device has its own maintenance system. Therefore, in the prior art, the management method of the network element is relatively complicated, and the skill of the management and maintenance personnel is relatively high. It can be seen that the embodiment provided by the present invention can reduce the complexity of network element management and does not require excessive requirements on the skills of management and maintenance personnel.

In the embodiment of the network element management method, the network element device management system, and the network element management system of the present invention, the network element device management system can receive fault information about the internally connected device, so that it is clear that the internal connected device is faulty. It is also clear what is going wrong. In the prior art, there is no mechanism for reporting fault information about the internally connected device. If a fault occurs, the management and maintenance personnel can only first determine whether there is an alarm about the network element device in the network element device management system. If not, then Troubleshoot if there is a problem with the internal connected device. It can be seen that the embodiment provided by the present invention can reduce the difficulty of fault location and facilitate timely detection of problems.

In the embodiment of the network element management method, the network element device management system, and the network element management system of the present invention, the network element device management system can configure the internal connected device by issuing a general command, and realize remote access to the internal connected device. management. In the prior art, due to different network IP address divisions, management and maintenance personnel are usually unable to directly manage internal connected devices at the remote end. In addition, for network security and other factors, the proxy cannot be directly set. The management and maintenance personnel are required to go to the site to configure the internal connected devices. Thus, embodiments of the present invention reduce the complexity of remote management over the prior art.

The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It is considered as the scope of protection of the present invention.

Claims

Rights request

A network element management method, comprising:

Establishing a maintenance channel between the network element device management system and the network element device, and between the network element device management system and the internal connection device;

The network element device management system manages the network element device through a maintenance channel established between the network element device and the internal connection device through a maintenance channel established between the network element device and the internal connection device.

The network element management method according to claim 1, wherein the maintenance channel established between the network element device management system and the network element device is a direct maintenance channel or a relay maintenance channel that is transited via at least one device. The maintenance channel established between the network element device management system and the internal connected device is a direct maintenance channel or a transit maintenance channel that is relayed through at least one device.

The network element management method according to claim 2, wherein, if the maintenance channel established between the network element device management system and the internal connected device is a transit maintenance channel, the transit maintenance channel is The device is the network element device.

The network element management method according to any one of claims 1-3, wherein the maintenance channel is established by using a Telnet command or a simple network management protocol SNMP.

The network element management method according to any one of claims 1 to 3, wherein the internal connection device is an internal data communication device.

The network element management method according to claim 5, wherein the network element management system manages the internal connection device through a maintenance channel established between the internal connection device, and includes alarm management and security. At least one of management, performance management, log management, and configuration management.

7. A network element device management system, comprising:

The maintenance channel establishing unit is configured to establish a maintenance channel with the network element device and the internal connected device respectively, and the device management unit is configured to manage the network element device by using the maintenance channel established between the maintenance channel establishing unit and the network element device, The internal connected devices are managed through a maintenance channel established between the internal connected devices.

The network element device management system according to claim 7, wherein the maintenance channel established between the maintenance channel establishing unit and the network element device is a direct maintenance channel or a transit maintenance channel via at least one device relay. Maintenance established between the maintenance channel establishing unit and the internal connected device The channel is a direct maintenance channel or a relay maintenance channel that is relayed via at least one device.

The network element device management system according to claim 8, wherein if the maintenance channel established between the maintenance channel establishing unit and the internal connected device is a transit maintenance channel, the device through which the relay maintenance channel passes It is the network element device.

The network element device management system according to any one of claims 7-9, wherein the maintenance channel establishing unit establishes a maintenance channel by using a Telnet command or an SNMP method.

The network element device management system according to claim 7, wherein the device management unit comprises: an interface management unit, configured to provide an integrated display panel of the device panel of the network element device and the internal connected device interface.

The network element device management system according to claim 7, 8, 9 or 11, wherein the internal connection device is an internal data communication device.

A network element management system, including a network element device management system, a network element device, and an internal connection device, wherein a maintenance channel is respectively disposed between the network element device management system, the network element device, and the internal connection device. The network element device management system manages the network element device by using a maintenance channel set between the network element device and the internal connection device through a maintenance channel set between the internal device and the internal connection device.

The network element management system according to claim 13, wherein the internal connection device is an internal data communication device.

The network element management system according to claim 14, wherein the network element management system manages the internal connection device through a maintenance channel established between the internal connection device, and includes alarm management and security. At least one of management, performance management, log management, and configuration management.

16. A network element management system, comprising a network element device management system, a network element device, and an internal connection device, wherein the device further includes a post management device;

A first maintenance channel is disposed between the network element device management system and the rear management device, and a second maintenance channel and a third maintenance channel are respectively disposed between the network management device and the internal connection device;

The post-management device controls the network element device and the internal connected device through the second maintenance channel and the third maintenance channel respectively according to the command issued by the network element device management system through the first maintenance channel. Reason

The post-management device also provides the information sent by the network element device and the internal connection device through the second maintenance channel and the third maintenance channel to the network element device management system through the first maintenance channel.

The network element management system according to claim 16, wherein the internal connection device is an internal data communication device.

18. A network element management system, comprising a network element device management system, a network element device, and an internal connection device, wherein the network element device management system and the network element device are provided with a first maintenance channel, the network element A second maintenance channel is disposed between the device and the internal connection device, where the network element device management system manages the network element device by using the first maintenance channel, and the network element device management system passes the first maintenance channel and the The second maintenance channel manages internal connected devices.

The network element management system according to claim 18, wherein the internal connection device is an internal data communication device.