CN101854263B

CN101854263B - Method, system and management server for analysis processing of network topology

Info

Publication number: CN101854263B
Application number: CN 201010208446
Authority: CN
Inventors: 吴航
Original assignee: Beijing Star Net Ruijie Networks Co Ltd
Current assignee: Beijing Star Net Ruijie Networks Co Ltd
Priority date: 2010-06-13
Filing date: 2010-06-13
Publication date: 2013-03-13
Anticipated expiration: 2030-06-13
Also published as: CN101854263A

Abstract

The invention provides a method, a system and a management server for the analysis processing of a network topology. The method comprises the following steps: receiving topology information generated in a network and collected by ring network devices, and writing the topology information into an event library; and analyzing the state of the network topology based on the topology information, and generating a processing strategy for the fault event. The management server comprises a receiving module, a write-in module and an analysis module, wherein the receiving module is used for receiving the topology information generated in the network and collected by the ring network devices; the write-in module is used for writing the topology information into the event library; and the analysis module is used for analyzing the state of the network topology based on the topology information and generating the processing strategy for the fault event. The system for the analysis processing of the network topology comprises a plurality of ring network devices and the management server. The embodiment of the invention realize the collection and the analysis of network topology events, provides the analysis result of the topology event for network maintenance personnel, lowers the technical requirements for the network maintenance personnel, and improves the maintainability and the stability of the network.

Description

The analysis and processing method of network topology, systems and management server

Technical field

The embodiment of the invention relates to network communications technology field, relates in particular to a kind of analysis and processing method, systems and management server of network topology.

Background technology

Resilient Packet Ring (Resilient Packet Ring; Hereinafter to be referred as: RPR) as a kind of novel medium access control (Media Access Control; Hereinafter to be referred as: MAC) agreement has SDH (Synchronous Digital Hierarchy) (Synchronous Digital Hierarchy; Hereinafter to be referred as: SDH)/Synchronous Optical Network (Synchronous Optical Network; Hereinafter to be referred as: the SONET) validity of the protection mechanism of looped network and Ethernet data message transmission.Therefore, the RPR looped network has high reliability, stability, the quick failover capability of carrier-class, and is generally used in the backbone network of relative core.Correspondingly, it has also proposed higher requirement to net chromium attendant, locates fast and solve the fault that may occur, and immediately gets rid of hidden network danger.And because the complexity of RPR looped network, the network maintenance staff need to could understand and locate various failure causes in the current network through the training of specialty, and this has increased the operation cost of enterprise undoubtedly.

In the prior art, institute of electrical and electronic engineers (Institute of Electrical and Electronics Engineers; Hereinafter to be referred as: IEEE) tissue has proposed corresponding RPR management information bank (Management Information Base; Hereinafter to be referred as: MIB), be used for presenting the transmitting-receiving situation of RPR looped network message, current configuring condition and current network topology situation, so that the network maintenance staff is according to the information among the RPR MIB and the contingent fault of micro-judgment current network of self.

Yet, in the prior art analysis, location and the solution of fault in the RPR looped network still depended on network maintenance staff's self-ability, and can't in time find and get rid of some and one dodge and the fault that dies, thereby cause potential faults in the RPR looped network, reduce the maintainable and stable of looped network.

Summary of the invention

The embodiment of the invention provides a kind of analysis and processing method, systems and management server of network topology, depend on the defective that the network maintenance staff analyzed, locates and solved network failure in the prior art in order to solve, realization is to the Collection and analysis of network topology event, the analysis result of topological event is provided for the network maintenance staff, reduction improves the maintainable and stable of network to network maintenance staff's specification requirement.

The embodiment of the invention provides a kind of analysis and processing method of network topology, comprising:

Receive the topology information that produces in the network of looped network equipment collection, and with in the described topology information writing events storehouse;

Respectively the network topology state of single topology event is analyzed according to the topology information of obtaining, and generated the treatment Countermeasures of single failure event, described single failure event is the described single topology event that breaks down;

From described event base, read the recent history event corresponding to described single topology event of respective amount according to default related historical record number;

According to the described recent history event that reads the network topology state of historical events is analyzed, and generated the treatment Countermeasures of historical events.

The embodiment of the invention provides a kind of management server, comprising:

Receiver module, the topology information that the network of collecting for reception looped network equipment produces;

Writing module is used for described topology information writing events storehouse;

Analysis module is used for according to described topology information the network topology state being analyzed, and generates the treatment Countermeasures of event of failure;

Wherein, described analysis module comprises:

The first analytic unit is used for respectively the network topology state of single topology event being analyzed according to the topology information of obtaining, and generates the treatment Countermeasures of single failure event, and described single failure event is the described single topology event that breaks down;

Reading unit is used for the default related historical record number of basis reads respective amount from described event base recent history event corresponding to described single topology event;

The second analytic unit is used for according to the described recent history event that reads the network topology state of historical events being analyzed, and generates the treatment Countermeasures of historical events.

The embodiment of the invention provides a kind of analysis process system of network topology, comprises a plurality of looped network equipment and above-mentioned management server.

The analysis and processing method of the network topology of the embodiment of the invention, the systems and management server, by looped network equipment the various topology informations that produce in the network are carried out collection and treatment, management server receives the topology information that is sent by looped network equipment, according to this topology information the network topology state is analyzed, and the treatment Countermeasures of generation event of failure, treatment Countermeasures is fed back to webmaster, so that webmaster can carry out instant effectively processing to the event of failure in the network according to treatment Countermeasures, solved and depended on the network maintenance staff in the prior art and analyze, the defective of location and solution network failure, realized the Collection and analysis to the network topology event, the analysis result of topological event is provided for the network maintenance staff, reduce the specification requirement to the network maintenance staff, improved the maintainable and stable of network.

Description of drawings

In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, the below will do one to the accompanying drawing of required use in embodiment or the description of the Prior Art and introduce simply, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain according to these accompanying drawings other accompanying drawing.

Fig. 1 is the flow chart of the analysis and processing method embodiment one of network topology of the present invention;

Fig. 2 is the structural representation of RPR looped network among the analysis and processing method embodiment one of network topology of the present invention;

Fig. 3 is the work exemplary plot of RPR looped network among the analysis and processing method embodiment one of network topology of the present invention;

Fig. 4 is the flow chart of the analysis and processing method embodiment two of network topology of the present invention

Fig. 5 is the structural representation of management server embodiment one of the present invention;

Fig. 6 is the structural representation of management server embodiment two of the present invention.

Embodiment

For the purpose, technical scheme and the advantage that make the embodiment of the invention clearer, below in conjunction with the accompanying drawing in the embodiment of the invention, technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that obtains under the creative work prerequisite.

Fig. 1 is the flow chart of the analysis and processing method embodiment one of network topology of the present invention, and as shown in Figure 1, present embodiment provides a kind of analysis and processing method of network topology, can specifically comprise the steps:

Step 101, management server receives the topology information that produces in the network of looped network equipment collection, and with in the described topology information writing events storehouse.

In this step, looped network equipment carries out collection and treatment to the topology information that produces in the network, comprise each change in topology event and the topological event of stablizing, management server receives topology information from coupled a plurality of looped network equipment, and the topology information that receives is write in the event base of management server.

The analysis and processing method of the network topology of present embodiment can specifically be applied in the RPR looped network, be illustrated in figure 2 as the structural representation of RPR looped network among the analysis and processing method embodiment one of network topology of the present invention, comprise 6 RPR websites among the figure, be S1-S6, connect by rpr interface between adjacent RPR website, to form a loop network.Wherein, each rpr interface includes receiving lines and transmitting line, but then forms the RPR looped network of transmitted in both directions as shown in Figure 2, namely clockwise or encircle 0, counterclockwise or encircle 1.Wherein, local area network (LAN) (Local Area Network; Hereinafter to be referred as: LAN) 1, LAN2, LAN3, LAN4, LAN5, LAN6 represent respectively the internal network interconnected with each RPR website, these networks are set up each other communication by the RPR looped network.

Be illustrated in figure 3 as the work exemplary plot of RPR looped network among the analysis and processing method embodiment one of network topology of the present invention, wherein, the connection of each direction between link (link) the expression RPR website, circuit (span) is the part between adjacent two websites in the RPR looped network, its unidirectional link by a pair of each other rightabout transmission forms, and for example the span between S0 and the S1 is comprised of to the link1 that S0 sends data to link0 and the S1 that S1 sends data S0 among Fig. 2.Each RPR website all carries out interconnectedly with other two RPR websites, and then each website is distinguished these two span usually to two span should be arranged according to the orientation, namely is divided into west span and east span.As for the S2 among Fig. 2, the interconnected span of S2 and S1 can be called the west span of S2, can be called the east span of S1, and the interconnected span of S2 and S3 can be called the east span of S2, can be called the west span of S3.Edge (edge) namely is in the span of malfunction for can not normally transmitting the span of data.

In the present embodiment, the Topology Discovery of RPR following several protection solicited status may occur with protection, can be Forced Switch (Forced Switch by its priority order from high to low; Hereinafter to be referred as: FS), Signal Fail (Signal Fail; Hereinafter to be referred as: SF), weak (the Signal Dgrade of signal; Hereinafter to be referred as: SD), the people is for switching (Manual Switch; Hereinafter to be referred as: MS), Wait-to-Restore (Wait To Restore; Hereinafter to be referred as: WTR) and idle (IDLE).Wherein, FS is the request of user's mandatory protection, and namely user's mandatory requirement is broken corresponding link and the protection request that causes; SF is the protection request that interface signal lost efficacy and causes; SD is the weak protection request that causes of interface signal; MS also is the request of user's mandatory protection, and itself and FS are similar, and just priority is lower; WTR is the protection request that is in during the WTR, and the WTR event is after the line fault that SF or SD occur is recovered, a kind of recovery transition state of RPR protocol definition, and main purpose is for preventing that SF, SD recovery event cause network topology frequently to be vibrated frequently.In addition, RPR also provides configuration whether to wish that for user selection the WTR event can automatically recover or forever keep the WTR state, unless the event of higher priority has occured it is substituted.IDLE is the unprotect solicited status.Wherein the reasons such as FS, SF, SD, MS, WTR may cause the edge state of span, are the links of paying close attention in this design.Wherein, the state of SF, SD is detected by the recipient, and its most situations are triggered by outside line fault or opposite end fault, and all the other states except SF, SD are initiatively announced by equipment, and it is triggered by user's configuration or the control of device interior state.For example, suppose among Fig. 2 that top link is called link1, following link is called link2 in interconnected two link of S3 and S4.The direction of arrow from figure can find out that link1 corresponds to the S3 transmission, S4 receives, and link2 corresponds to the S4 transmission, S3 receives.When the connection of link1 was broken, detected SF state by S4 this moment; When breaking with connection that should link2, then S3 can detect the SF state; If two link break simultaneously, then S3, S4 can detect the SF state simultaneously.

Step 102, management server is analyzed the network topology state according to described topology information, and generates the treatment Countermeasures of event of failure.

Management server is after receiving new topology information, according to the topology information that from event base, reads the network topology state is analyzed, and generate the correspondingly treatment Countermeasures of event of failure according to the result who analyzes, the treatment Countermeasures that generates is fed back to webmaster, can assist webmaster that the event of failure that occurs in the network is carried out effectively processing in real time.

Present embodiment provides a kind of analysis and processing method of network topology, by looped network equipment the various topology informations that produce in the network are carried out collection and treatment, management server receives the topology information that is sent by looped network equipment, according to this topology information the network topology state is analyzed, and the treatment Countermeasures of generation event of failure, treatment Countermeasures is fed back to webmaster, so that webmaster can carry out instant effectively processing to the event of failure in the network according to treatment Countermeasures, solved and depended on the network maintenance staff in the prior art and analyze, the defective of location and solution network failure, realized the Collection and analysis to the network topology event, the analysis result of topological event is provided for the network maintenance staff, reduce the specification requirement to the network maintenance staff, improved the maintainable and stable of network.

Fig. 4 is the flow chart of the analysis and processing method embodiment two of network topology of the present invention, and as shown in Figure 4, present embodiment provides a kind of analysis and processing method of network topology, can comprise the steps:

Step 401, looped network equipment carries out collection and treatment to the topology information that produces in the network.

In this step, looped network equipment topology information that the change in topology event that produces in the network, topology are stablized event etc. is carried out collection and treatment.Topology information herein can include but not limited to the relative position of all the other websites in real event, this website that change in topology occurs and described website and the network of change in topology of final continual and steady time of continual and steady time, last topology of time that this topology changes, time, this topology that this topology is stable, immediate cause that this topology changes, this root website that change in topology occurs, and the defective that exists in the current network is indicated.

Wherein, the time that this topology changes can obtain according to the device start time of RPR looped network equipment, and namely the relative time relative with the device start time also can obtain according to the current standard time, is absolute time.This stable time of topology also can obtain according to device start time or the current standard time of RPR looped network equipment, and usually, the stable time interval from the change in topology to the topology of RPR looped network needs in the 50ms again.The continual and steady time of this topology can be determined according to this topology stabilization time, for example this topology is stablized event and is occurred in 2010-5-9 1:00, then when 2010-5-9 18:00 checks current network topology situation, the value in this territory is 0 day 17 hours, represents that this topology is continual and steady 17 hours.Owing to can only wait until to obtain the last time final stabilization time of topology when topology changes next time, then the final continual and steady time of last topology can obtain according to the time that this topology changes.The immediate cause that this topology changes may be protection configuration, SD, SF, FS, MS etc.; be that this topology changes and can show as the events such as SD or SF occur; when this topology changed, RPR looped network equipment can obtain the immediate cause that the inferior topology of wherein carrying changes according to the RPR message that receives.Root website for change in topology occurs namely for first fault website that detects fault, also needs to record the real event of change in topology.For example, triggering the reason of SF event can be for because connection disconnects, keep-alive is overtime or misconnection ring etc.Wherein, because interconnected two websites of each RPR span are in the normal situation of connection; the capital initiatively externally sends the keep-alive message; within the duration that a side is setting, do not receive the keep-alive message; then think the distance station point failure; and then detect the SF event that produces, then the real event of the SF event of this situation generation is that keep-alive is overtime.And the misconnection ring is two circuit generation connecting staggereds between interconnected two websites, and for example, connecting staggereds occur two link among Fig. 3 between S3 and the S4, i.e. the reception of link2 is received in the transmission of link1, and the reception of link1 is received in the transmission of link2.Looped network equipment also need record the relative position of all the other websites in this website that change in topology occurs and this website and the network, take Fig. 2 as example, suppose that the S2 website has caused change in topology, to be the S1 website first jump corresponding website what ring 0 sent to the website of the generation change in topology that then records at the S1 website, be website corresponding to the first jumping that the S1 website sends in the clockwise direction, perhaps website corresponding to the fifth jump that send at ring 1 of S1 website, i.e. website corresponding to the fifth jump that send in the counterclockwise direction of S1 website.In addition, looped network equipment also carries out record to the defective indication that exists in the current network, and looped network equipment can check whether there is the defective indication in the current RPR looped network, if exist, then record is carried out in this defective indication.

Step 402, management server receives the topology information that looped network equipment is collected, and with in the topology information writing events storehouse.

This step is that management server receives the topology information that each looped network equipment is collected from connected a plurality of looped network equipment, and this topology information is write in the event base of management server.The data message that carries out in the present embodiment communication between website and the management server can use Simple Network Management Protocol (Simple Network Management Protocol; Hereinafter to be referred as: SNMP) form, wherein, the load contents that carries in the SNMP message is the topology information of looped network equipment records in the above-mentioned steps 401.Communication modes in the present embodiment between management server and the RPR looped network equipment mainly comprises two kinds, wherein a kind of form is initiatively to management server announcement topology information by RPR looped network equipment, this situation mainly occurs in the situation that the network state of RPR looped network changes, namely may be because the configuration that is used for is revised, equipment changing or connect changes etc.; Another form is that management server is initiated query requests to looped network equipment, receives the topology information that looped network equipment is collected according to this query requests, and this situation occurs in the situation of the query manipulation of initiatively being initiated by webmaster.

Step 403, management server is analyzed the network topology state of single topology event respectively according to the topology information of obtaining, and generates the treatment Countermeasures of single failure event, and described single failure event is the described single topology event that breaks down.

Receive the topology information of looped network equipment collection by active inquiry mode or initiatively announcement mode of looped network equipment when management server after, management server writes the topology information that receives in the local event base, triggers the analysis process of management server with stylish topology information.In the present embodiment, the event that topology changes is divided into two classes, and a class is to break down to process, and another kind of is that fault is recovered, and need not to process.Therefore, for single topology event, need to adopt correspondingly countermeasure for the single failure event, the single failure event of present embodiment is that relevant event appearred in fault when single topology event was analyzed, and for historical events, then need to carry out the statistical analysis of all events, this step is specially the analyzing and processing to the single failure event.In this step, management server is when the execution analysis process, by recording last event handling numbering, and then which is identified is newly-increased event, numbering can adopt the 64bit coding, can record in theory 2 64 power bar records, and therefore the problem of unrolling can not occur to number.Event of people after upper once event handling numbering is newly-increased event, then management server reads first the complete record number of analyzing and processing last time, from event base, read this record number all records afterwards, then each record is carried out single analyses one by one and process.

Management server is when analyzing single topology event, can obtain according to topology information the particular type of event, because having recorded which span of which website in the topology information breaks down, therefore again by the record of equipment corresponding to two interconnected websites of this span, just can navigate to the concrete link that breaks down.When topology information was indicated some website generation Signal Fail SF events, management server can according to this topological event and the logout of this website adjacent sites of this website in the current topology information, be classified as follows this fault:

Particularly; when detecting this website generation keep-alive inefficacy according to topology information and not detecting described website generation link failure; the treatment Countermeasures that generates the single failure event probably breaks down for the equipment corresponding with the interconnected opposite end website of described fault website, especially detects too keep-alive when overtime when the interconnected website of the another one span of equipment corresponding to this opposite end website.For example; with reference to Fig. 3; it is overtime that the westspan of S4 detects keep-alive; it is overtime that the east span of S2 also detects keep-alive; substantially can determine that then fault has occured S3 equipment; lost efficacy if keep-alive all occurs in the both sides of S3, can advise then that webmaster S3 before fixing a breakdown was set to direct mode operation to guarantee that looped network moves by the mode of closed loop.When equipment corresponding to opposite end website did not break down, whether the equipment that monitoring station is corresponding broke down, may be because problem has appearred in the keep-alive testing mechanism of this website, as the situation of wrong report occurring.

Particularly, when detecting this website generation link failure according to topology information and during with the interconnected opposite end website generation link failure of this website, whether the treatment Countermeasures that generates the single failure event breaks down to the link that this website sends data for this opposite end website of suggestion webmaster main monitor.For example, with reference to Fig. 3, if the link2 of the west span of S4 detects SF, and the east span of S3 does not detect SF, advises then whether the link2 that webmaster is paid close attention among the span of S4 and S3 fault has occured.

Particularly, when detecting described website according to topology information and all link failure occuring with the interconnected opposite end website of described website, whether the treatment Countermeasures that generates the single failure event breaks down for the link between the suggestion described website of webmaster main monitor and the described opposite end website.For example, with reference to Fig. 3, if the link2 of the west span of S4 detects SF, and the east span of S3 also detects SF, advises then whether link2 and link1 that webmaster is paid close attention among the span of S4 and S3 fault has all occured.

Particularly, when detecting described website according to topology information and with the interconnected opposite end website of described website the misconnection ring occuring all, generate the treatment Countermeasures of single failure event and be the misconnection ring of circuit between the described website of revision and the described opposite end website.

When topology information was indicated the weak SD event of some website generation signals, management server can according to this topological event and the logout of this website adjacent sites of this website in the current topology information, be classified as follows this fault:

Particularly, described website generation line signal is weak and do not detect with the interconnected opposite end website of described website and line signal to occur when weak when detecting according to topology information, the quantity of the error message that the treatment Countermeasures that generates the single failure event receives from described opposite end website for the described website of statistics.When the difference of the quantity of described error message and default error message threshold value during less than default fault tolerant amount, improve described error message threshold value, when the difference of the quantity of described error message and default error message threshold value during greater than default fault tolerant amount, described opposite end website is changed processing to the link that described website sends data, wherein, described fault tolerant amount is that webmaster is set according to applicable cases, and namely the fault tolerant amount of webmaster is different under the different applicable cases.For example, with reference to Fig. 3, if the link2 of the west span of S4 detects SD, and the east span of S3 does not detect SD, advises that then webmaster pays close attention to the link2 circuit among S4 and the S3 span.Because the alarm of SD represents the signal quality existing problems of this section link, but might can also communication, therefore whether there is more error message in the data statistics that further the west span of suggestion webmaster observation S4 receives, if the difference of the quantity of error message and default error message threshold value is less than default fault tolerant amount, show that namely the quantity of error message is in tolerable scope, fault tolerant amount herein is relevant with current network application, need webmaster to preset according to actual conditions, advise that then webmaster improves the error message threshold value, namely reduce the thresholding that SD detects, then judge whether to get rid of this SD fault.Can't stand if the difference of the quantity of error message and default error message threshold value, shows namely that the quantity of error message is too many greater than default fault tolerant amount, advise that then webmaster changes this link.Wherein, described fault tolerant amount is that webmaster is set according to applicable cases, and namely the fault tolerant amount of webmaster is different under the different applicable cases.

Particularly, line signal all occurs when weak when detect the interconnected opposite end website of described website and described website according to topology information, the quantity of the error message that the quantity of the error message that the treatment Countermeasures that generates the single failure event receives from described opposite end website for the described website of statistics and described opposite end website receive from described website; The difference of the quantity of the error message that sends to described website when described opposite end website and the first default error message threshold value is during less than default fault tolerant amount, improve the poor of described the first error message threshold value, the difference of the quantity of the error message that sends to described website when described opposite end website and the first default error message threshold value is changed processing to described opposite end website to the link that described website sends data during greater than default fault tolerant amount; The difference of the quantity of the error message that sends to described opposite end website when described website and the second default error message threshold value is during less than default fault tolerant amount, improve described the second error message threshold value, the difference of the quantity of the error message that sends to described opposite end website when described website and the second default error message threshold value is changed processing to described website to the link that described opposite end website sends data during greater than default fault tolerant amount.For example, with reference to Fig. 3, if the link2 of the west span of S4 detects SD, the east span of S3 also detects SD, advises that then webmaster pays close attention to link2 and the link1 circuit among S4 and the S3 span.And advise further webmaster observes in the data statistics that the west span of S4 receives whether have more error message, if the quantity of error message is less than default fault tolerant amount, show that namely the quantity of error message is in tolerable scope, fault tolerant amount herein is relevant with current network application, need webmaster to preset according to actual conditions, advise that then webmaster reduces the SD detection threshold, namely improve the fault tolerant amount, then judge whether to get rid of this SD fault.Can't stand if the quantity of error message, shows namely that the quantity of error message is too many greater than default fault tolerant amount, advise that then webmaster changes corresponding link.

When topology information indicates some website generation Forced Switch FS or people when switching the MS event, management server can be according to this topological event and the logout of this website adjacent sites of this website in the current topology information, treatment Countermeasures to this fault is as follows: obtain in the described website circuit that FS or MS event occur according to topology information, the treatment Countermeasures that generates the single failure event be the circuit in the website of webmaster feedback generation FS or MS event.Namely dispose generation because FS or MS event only have by the user, so only need this moment certain span of certain website of notice webmaster that FS or MS event have occured, whether PLSCONFM is that the result who expects gets final product.

When topology information is indicated some website generation Wait-to-Restore WTR events; management server can be according to this topological event and the logout of this website adjacent sites of this website in the current topology information; treatment Countermeasures to this fault is as follows: management server obtains first the WTR configuration information of equipment corresponding to described website according to topology information; because WTR is an interim state; be introduced into the WTR state after the SF/SD fault recovery; this moment, span still was in the edge state; can't transceiving data; when (acquiescence is 10 seconds through after a while; the longest 1440 seconds) the protection event of other high priority does not occur after; if the user has disposed WTR and has allowed to recover; then WTR will revert to the IDLE state; this moment, the edge state was excluded, and communication is normal.When described WTR configuration information is WTR when irrecoverable, then only need feed back this WTR configuration information to webmaster, the notice webmaster judges whether this configuration is the result who expects.When described WTR configuration information is that WTR can recover, but and when equipment corresponding to described website still kept the WTR state after WTR surpasses the twice of default recovery time recovery time, it is unusual that the treatment Countermeasures that generates the single failure event is that the software of described equipment occurs.Further, in the retention fault content so that with outside equipment vendors exchange, can also be by carrying out the MS configuration at fault span, removing the operation of MS configuration to address this problem.

When topology information is indicated some website generation configuration change events, management server can be according to this topological event and the logout of this website adjacent sites of this website in the current topology information, treatment Countermeasures to this fault is as follows: obtain the configuration change information of described website according to topology information, generate the treatment Countermeasures of single failure event for to point out the configuration change information of described website to webmaster.Namely provide information to webmaster, show which configuration of which website has caused this change in topology event, judged the reasonability of this event by webmaster.

Step 404, management server read the recent history event corresponding to described single topology event of respective amount from described event base according to default related historical record number.

After a single topology event analysis is finished, management server reads the recent history event corresponding to this single topology event of respective amount from event base according to default related historical record number, related historical record number herein can be set as required by webmaster, as be set as 5, then management server reads 5 recent history events from event base, i.e. 5 recent history events before the record number of this single topology event.Present embodiment is the maximum difference of the analysis of historical events with the before analysis of single topology event, the SF event occurs in common single circuit, for example optical fiber is dug disconnected because of construction reason, then do not have artificial intervention to replace new optical fiber, so the SF event can't be recovered.And loose contact can recover within the extremely short time after causing circuit SF automatically mostly, therefore only checks that current topological state is difficult to perceive this fault, need to analyze a plurality of historical record events.

Management server judges whether the record number of the recent history event that reads is continuous, if so, then uses these recent history events to start the historical data analysis process; Otherwise directly use current continuous recent history event to start the historical data analysis process.Because webmaster can be inquired about or the operation such as deletion the historical data in the event base, then may cause historical data to lose, cause the forward-backward correlation of historical data to be lost, the discontinuous situation of record number namely appears, then present embodiment is only analyzed the historical events of serial number, in case find that numbering is discontinuous, then only analyze till historical events corresponding to numbering breakpoint.Only be one if finally find continuous historical events, then analyze according to the analytical method of the single of above-mentioned steps 403 topology event.

Step 405, management server is analyzed the network topology state of historical events according to the described recent history event that reads, and generates the treatment Countermeasures of historical events.

Management server can obtain according to topology information the statistical conditions of historical record event when historical events is analyzed, carry out analyzing and processing according to the statistical conditions of historical record event.Indicate a website that SF/SF occurs when the recent history event and recover the read-around ratio of event above the first default frequency threshold value, or when indicating website that number of times that SF/SF recovers event occurs to surpass the second default frequency threshold value, herein the first frequency threshold value and the second frequency threshold value can specifically be set according to actual conditions by webmaster, as being set as respectively 3 and 5, be that management server is known certain website continuous 3 times or above generation SF/SF recovery (from WTR to IDLE) event according to the historical data of obtaining, typically be certain website continuous several times SF/SF recovery event occurs, and the stable time that continues of each topology is all shorter, as in one hour, or know that certain website once occured at least or 5 times or above SF/SF recovery event.At this moment, management server can be classified as follows this fault:

Particularly, when according to described recent history event detection to described SF during by invalid the causing of link of described website, it is unusual that the treatment Countermeasures that generates historical events is that the interconnected optical fiber cable of circuit corresponding to described website or optical module occur.Modal situation is that the link generation SF event that is that triggers repeatedly SF causes that according to knowing in the single failure analysis, SF also divides single link that the SF event occurs and the SF event occurs two link simultaneously.Then management server can provide alarm to webmaster: might this fault span interconnected optical fiber cable loose contact or the optical module of notice webmaster is unusual, needs to change optical fiber cable or optical module.Further, if fault still fails to get rid of, then be likely the fault that equipment causes, the suggestion webmaster need to be notified manufacturer's maintenance and provide historical record for manufacturer's personnel inquiry.

Particularly; when being lost efficacy when causing by the keep-alive of described website to described SF according to described recent history event detection; generate the treatment Countermeasures of historical events for carrying out following countermeasure according to default execution probability; execution probability herein can be set up on their own by management server; more preferably for putting in order as the height of carrying out probability with following; namely come the preferential execution of front, if countermeasure is not before fixed a breakdown, then continue to carry out follow-up countermeasure.The suggestion webmaster is carried out following countermeasure according to carrying out probability: because both sides' protection mechanism is incompatible, advise that then the keep-alive out-of-service time that webmaster detects the website that keep-alive lost efficacy always is set to grow most the keep-alive out-of-service time; If a upper countermeasure can not be dealt with problems, then advise the interconnected optical fiber cable of the webmaster circuit that described website is corresponding, optical module or change processing with the optical module of the interconnected opposite end website of described website; If a upper countermeasure can not be dealt with problems, advise that then webmaster monitors processing to ruuning situation and the connectivity of equipment corresponding to described opposite end website, and keep in repair and provide corresponding historical record and observed result observing in the situation of fault in time contact manufacturer.

When the recent history event indicates the opposite end website of two circuits of a website that SF event or keep-alive failure event alternately occur, both sides adjacent sites S2 and S4 such as S3 among Fig. 3 are consecutively detected SF or keep-alive failure event, management server can generate the treatment Countermeasures of historical events for carrying out following countermeasure according to default execution probability according to the recent history event that reads, the explanation of execution probability herein is similar to the above, repeat no more: management server suggestion webmaster is monitored processing to ruuning situation and the connectivity of equipment corresponding to described website herein, keeps in repair and provide corresponding historical record and observed result observing in the situation of fault in time contact manufacturer; If a upper countermeasure can not be dealt with problems, then management server suggestion webmaster is changed processing to two circuits of described website interconnected optical fiber cable and optical module.

When the recent history event indicated the number of times of a website generation FS/MS event and FS releasing event to surpass default for the third time several threshold value, whether management server can be to detect the user's configuration script that uses in the test process not close according to the treatment Countermeasures of the recent history event generation historical events that reads.The user's configuration script that namely provides alarm and notify webmaster may exist some test processs to use to webmaster forgets and closes, and then deletes the FS/MS configuration ceaselessly carrying out FS/MS, needs webmaster to check the behavior of corresponding control terminal.

Present embodiment provides a kind of analysis and processing method of network topology, by looped network equipment the various topology informations that produce in the network are carried out collection and treatment, management server receives the topology information that is sent by looped network equipment, according to this topology information the network topology state is analyzed, and the treatment Countermeasures of generation event of failure, treatment Countermeasures is fed back to webmaster, so that webmaster can carry out instant effectively processing to the event of failure in the network according to treatment Countermeasures, solved and depended on the network maintenance staff in the prior art and analyze, the defective of location and solution network failure, realized the Collection and analysis to the network topology event, the analysis result of topological event is provided for the network maintenance staff, be conducive to webmaster better maintaining network equipment and analyze and solve fault in time, reduce the specification requirement to the network maintenance staff, improved the maintainable and stable of network.

One of ordinary skill in the art will appreciate that: all or part of step that realizes said method embodiment can be finished by the relevant hardware of program command, aforesaid program can be stored in the computer read/write memory medium, this program is carried out the step that comprises said method embodiment when carrying out; And aforesaid storage medium comprises: the various media that can be program code stored such as ROM, RAM, magnetic disc or CD.

Fig. 5 is the structural representation of management server embodiment one of the present invention, and as shown in Figure 5, present embodiment provides a kind of management server, can specifically carry out each step of said method embodiment one, repeats no more herein.The management server that present embodiment provides can specifically comprise receiver module 501, writing module 502 and analysis module 503.Wherein, receiver module 501 is used for receiving the topology information that network that looped network equipment collects produces.Writing module 502 is used for described topology information writing events storehouse.Analysis module 503 is used for according to described topology information the network topology state being analyzed, and generates the treatment Countermeasures of event of failure.

Fig. 6 is the structural representation of management server embodiment two of the present invention, and as shown in Figure 6, present embodiment provides a kind of management server, can specifically carry out each step of said method embodiment two, repeats no more herein.The management server that present embodiment provides is on above-mentioned basis shown in Figure 5, and analysis module 503 can specifically comprise the first analytic unit 513, reading unit 523 and the second analytic unit 533.Wherein, the first analytic unit 513 is used for respectively the network topology state of single topology event being analyzed according to the topology information of obtaining, and generates the treatment Countermeasures of single failure event, and described single failure event is the described single topology event that breaks down.Reading unit 523 is used for reading from described event base according to default related historical record number the recent history event corresponding to described single topology event of respective amount.The second analytic unit 533 is used for according to the described recent history event that reads the network topology state of historical events being analyzed, and generates the treatment Countermeasures of historical events.

Further, when a website generation Signal Fail SF event of described topology information indication, the first analytic unit 513 can comprise specifically that the first countermeasure generates subelement 5131, the second countermeasure generates subelement 5132, the 3rd countermeasure generation subelement 5133 and the 4th countermeasure and generates subelement 5134.Wherein, the first countermeasure generates subelement 5131 and is used for when detecting described website generation keep-alive inefficacy according to topology information and not detecting described website generation link failure; whether the treatment Countermeasures that generates the single failure event breaks down for equipment corresponding to the interconnected opposite end website of monitoring and described website; and when described opposite end equipment corresponding to website does not break down, monitor equipment corresponding to described website and whether break down.The second countermeasure generates subelement 5132 and is used for when detecting described website generation link failure according to topology information and during with the interconnected opposite end website generation link failure of described website, whether the treatment Countermeasures that generates the single failure event breaks down for the link of the described opposite end of monitoring website to described website transmission data.The 3rd countermeasure generates subelement 5133 and is used for when detecting described website according to topology information and all link failure occuring with the interconnected opposite end website of described website, and whether the treatment Countermeasures that generates the single failure event breaks down for the link of monitoring between described website and the described opposite end website.The 4th countermeasure generates subelement 5134 and is used for generating the treatment Countermeasures of single failure event for revising the misconnection ring of circuit between described website and the described opposite end website when detecting described website according to topology information and with the interconnected opposite end website of described website the misconnection ring occuring all.

Perhaps, when a weak SD event of website generation signal of described topology information indication, the first analytic unit 513 can comprise specifically that the 5th countermeasure generates subelement 5135 and the 6th countermeasure generates subelement 5136.Wherein, the 5th countermeasure generates subelement 5135 and is used for when detect described website generation line signal according to topology information weakly and do not detect with the interconnected opposite end website of described website and line signal to occur when weak, and the treatment Countermeasures that generates the single failure event is the quantity of the error message adding up described website and receive from described opposite end website; When the difference of the quantity of described error message and default error message threshold value during less than default fault tolerant amount, improve described error message threshold value, when the difference of the quantity of described error message and default error message threshold value during greater than default fault tolerant amount, described opposite end website is changed processing to the link that described website sends data, wherein, described fault tolerant amount is for setting according to applicable cases.The 6th countermeasure generates subelement 5136 and is used for line signal all occuring when weak when detect the interconnected opposite end website of described website and described website according to topology information, the quantity of the error message that the treatment Countermeasures that generates the single failure event receives from described website for the quantity of the error message adding up described website and receive from described opposite end website and described opposite end website; The difference of the quantity of the error message that sends to described website when described opposite end website and the first default error message threshold value is during less than default fault tolerant amount, improve described the first error message threshold value, the difference of the quantity of the error message that sends to described website when described opposite end website and the first default error message threshold value is changed processing to described opposite end website to the link that described website sends data during greater than default fault tolerant amount; The difference of the quantity of the error message that sends to described opposite end website when described website and the second default error message threshold value is during less than default fault tolerant amount, improve described the second error message threshold value, the difference of the quantity of the error message that sends to described opposite end website when described website and the second default error message threshold value is during greater than default fault tolerant amount, described website is changed processing to the link that described opposite end website sends data, wherein, described fault tolerant amount is for setting according to applicable cases.

Perhaps, when website generation Forced Switch FS of described topology information indication or people when switching the MS event, the first analytic unit 513 can comprise specifically that the 7th countermeasure generates subelement 5137, the 7th countermeasure generates subelement 5137 and is used for obtaining the circuit that FS or MS event occur described website according to topology information, and the treatment Countermeasures that generates the single failure event be the circuit in the website of webmaster feedback generation FS or MS event.

Perhaps, when a website generation Wait-to-Restore WTR event of described topology information indication, the first analytic unit 513 can comprise specifically that obtaining subelement 5138, the 8th countermeasure generation subelement 5139 and the 9th countermeasure generates subelement 5231.Wherein, obtain the WTR configuration information that subelement 5138 is used for obtaining according to topology information equipment corresponding to described website.The 8th countermeasure generate subelement 5139 be used for when described WTR configuration information be WTR when irrecoverable, the treatment Countermeasures of generation single failure event is for to feed back described WTR configuration information to webmaster.It is that WTR can recover for working as described WTR configuration information that the 9th countermeasure generates subelement 5231, and when but equipment corresponding to described website still kept the WTR state after WTR recovery time surpassing the twice of default recovery time, it is unusual that the treatment Countermeasures that generates the single failure event is that the software of described equipment occurs.

Perhaps, when a website generation configuration change event of described topology information indication, the first analytic unit 513 can comprise specifically that the tenth countermeasure generates subelement 5232, the tenth countermeasure generates the configuration change information that subelement 5232 is used for obtaining according to topology information described website, generates the treatment Countermeasures of single failure event for to point out the configuration change information of described website to webmaster.

Further, recover the read-around ratio of event above the first default frequency threshold value when SF/SF occurs website of described recent history event indication, or when indicating website that number of times that SF/SF recovers event occurs to surpass the second default frequency threshold value, the second analytic unit 533 can comprise specifically that the first historical countermeasure generates subelement 5331 and the second historical countermeasure generates subelement 5332.Wherein, the first historical countermeasure generate subelement 5331 be used for when according to described recent history event detection to described SF during by invalid the causing of link of described website, the treatment Countermeasures that generates historical events be the interconnected optical fiber cable of circuit corresponding to described website or optical module appearance unusually.The second historical countermeasure generates subelement 5332 and is used for when being lost efficacy when causing by the keep-alive of described website to described SF according to described recent history event detection, and the treatment Countermeasures that generates historical events is to carry out following countermeasure according to the execution probability of presetting: the keep-alive out-of-service time of described website is set to grow most the keep-alive out-of-service time; The interconnected optical fiber cable of the circuit that described website is corresponding, optical module or change processing with the optical module of the interconnected opposite end website of described website; Ruuning situation and connectivity to equipment corresponding to described opposite end website are monitored processing.

Perhaps, when described recent history event indicates the opposite end website of two circuits of a website that SF event or keep-alive failure event alternately occur, the second analytic unit 533 can comprise specifically that it is to carry out following countermeasure according to default execution probability for the treatment Countermeasures that generates historical events according to the recent history event that reads that the 3rd historical countermeasure generation subelement 5333, the three historical countermeasures generate subelements 5333: ruuning situation and connectivity to equipment corresponding to described website are monitored processing; Optical fiber cable and optical module that two circuits of described website are interconnected are changed processing.

Perhaps, when described recent history event indicates the number of times of a website generation FS/MS event and FS releasing event to surpass default for the third time several threshold value, the second analytic unit 533 can comprise specifically that the 4th historical countermeasure generates subelement 5334, the four historical countermeasures generation subelements 5334 and is used for whether not closing for user's configuration script that the detection test process uses according to the treatment Countermeasures of the recent history event generation historical events that reads.

Present embodiment provides a kind of management server, by looped network equipment the various topology informations that produce in the network are carried out collection and treatment, management server receives the topology information that is sent by looped network equipment, according to this topology information the network topology state is analyzed, and the treatment Countermeasures of generation event of failure, treatment Countermeasures is fed back to webmaster, so that webmaster can carry out instant effectively processing to the event of failure in the network according to treatment Countermeasures, solved and depended on the network maintenance staff in the prior art and analyze, the defective of location and solution network failure, realized the Collection and analysis to the network topology event, the analysis result of topological event is provided for the network maintenance staff, be conducive to webmaster better maintaining network equipment and analyze and solve fault in time, reduce the specification requirement to the network maintenance staff, improved the maintainable and stable of network.

Present embodiment also provides a kind of analysis process system of network topology, specifically can comprise a plurality of looped network equipment and above-mentioned Fig. 5 or management server shown in Figure 6.

It should be noted that at last: above embodiment only in order to technical scheme of the present invention to be described, is not intended to limit; Although with reference to previous embodiment the present invention is had been described in detail, those of ordinary skill in the art is to be understood that: it still can be made amendment to the technical scheme that aforementioned each embodiment puts down in writing, and perhaps part technical characterictic wherein is equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution break away from the spirit and scope of various embodiments of the present invention technical scheme.

Claims

1. the analysis and processing method of a network topology is characterized in that, comprising:

2. method according to claim 1, it is characterized in that, described topology information comprises the relative position of all the other websites in real event, this website that change in topology occurs and described website and the network of change in topology of final continual and steady time of continual and steady time, last topology of time that this topology changes, time, this topology that this topology is stable, immediate cause that this topology changes, this root website that change in topology occurs, and the defective that exists in the current network is indicated.

3. method according to claim 1, it is characterized in that, when a website generation Signal Fail SF event of described topology information indication, the topology information that described basis is obtained is analyzed the network topology state of single topology event respectively, and the treatment Countermeasures of generation single failure event comprises:

When detecting described website generation keep-alive inefficacy according to topology information and not detecting described website generation link failure, whether the treatment Countermeasures that generates the single failure event breaks down for equipment corresponding to the interconnected opposite end website of monitoring and described website, and when described opposite end equipment corresponding to website does not break down, monitor equipment corresponding to described website and whether break down;

When detecting described website generation link failure according to topology information and during with the interconnected opposite end website generation link failure of described website, whether the treatment Countermeasures that generates the single failure event breaks down to the link that described website sends data for the described opposite end of monitoring website;

When detecting described website according to topology information and all link failure occuring with the interconnected opposite end website of described website, whether the treatment Countermeasures that generates the single failure event breaks down for the link between the described website of monitoring and the described opposite end website;

When detecting described website according to topology information and with the interconnected opposite end website of described website the misconnection ring occuring all, generate the treatment Countermeasures of single failure event and be the misconnection ring of circuit between the described website of revision and the described opposite end website.

4. method according to claim 1, it is characterized in that, when a weak SD event of website generation signal of described topology information indication, the topology information that described basis is obtained is analyzed the network topology state of single topology event respectively, and the treatment Countermeasures of generation single failure event comprises:

Described website generation line signal is weak and do not detect with the interconnected opposite end website of described website and line signal to occur when weak when detecting according to topology information, the quantity of the error message that the treatment Countermeasures that generates the single failure event receives from described opposite end website for the described website of statistics; When the difference of the quantity of described error message and default error message threshold value during less than default fault tolerant amount, improve described error message threshold value, when the difference of the quantity of described error message and default error message threshold value during greater than default fault tolerant amount, described opposite end website is changed processing to the link that described website sends data, wherein, described fault tolerant amount is for setting according to applicable cases;

Line signal all occurs when weak when detect the interconnected opposite end website of described website and described website according to topology information, the quantity of the error message that the quantity of the error message that the treatment Countermeasures that generates the single failure event receives from described opposite end website for the described website of statistics and described opposite end website receive from described website; The difference of the quantity of the error message that sends to described website when described opposite end website and the first default error message threshold value is during less than default fault tolerant amount, improve described the first error message threshold value, the difference of the quantity of the error message that sends to described website when described opposite end website and the first default error message threshold value is changed processing to described opposite end website to the link that described website sends data during greater than default fault tolerant amount; The difference of the quantity of the error message that sends to described opposite end website when described website and the second default error message threshold value is during less than default fault tolerant amount, improve described the second error message threshold value, the difference of the quantity of the error message that sends to described opposite end website when described website and the second default error message threshold value is during greater than default fault tolerant amount, described website is changed processing to the link that described opposite end website sends data, wherein, described fault tolerant amount is for setting according to applicable cases.

5. method according to claim 1, it is characterized in that, when website generation Forced Switch FS of described topology information indication or people when switching the MS event, the topology information that described basis is obtained is analyzed the network topology state of single topology event respectively, and the treatment Countermeasures of generation single failure event comprises:

Obtain in the described website circuit that FS or MS event occur according to topology information, the treatment Countermeasures that generates the single failure event be the circuit in the website of webmaster feedback generation FS or MS event.

6. method according to claim 1, it is characterized in that, when a website generation Wait-to-Restore WTR event of described topology information indication, the topology information that described basis is obtained is analyzed the network topology state of single topology event respectively, and the treatment Countermeasures of generation single failure event comprises:

Obtain the WTR configuration information of equipment corresponding to described website according to topology information;

When described WTR configuration information is WTR when irrecoverable, generate the treatment Countermeasures of single failure event for to feed back described WTR configuration information to webmaster;

When described WTR configuration information is that WTR can recover, but and when equipment corresponding to described website still kept the WTR state after WTR surpasses the twice of default recovery time recovery time, it is unusual that the treatment Countermeasures that generates the single failure event is that the software of described equipment occurs.

7. method according to claim 1, it is characterized in that, when a website generation configuration change event of described topology information indication, the topology information that described basis is obtained is analyzed the network topology state of single topology event respectively, and the treatment Countermeasures of generation single failure event comprises:

Obtain the configuration change information of described website according to topology information, generate the treatment Countermeasures of single failure event for to point out the configuration change information of described website to webmaster.

8. each described method according to claim 3-7, it is characterized in that, recover the read-around ratio of event above the first default frequency threshold value when SF/SF occurs website of described recent history event indication, or when indicating website that number of times that SF/SF recovers event occurs to surpass the second default frequency threshold value, the described recent history event that described basis reads is analyzed the network topology state of historical events, and the treatment Countermeasures of generation historical events comprises:

When according to described recent history event detection to described SF during by invalid the causing of link of described website, it is unusual that the treatment Countermeasures that generates historical events is that the interconnected optical fiber cable of circuit corresponding to described website or optical module occur;

When being lost efficacy when causing by the keep-alive of described website to described SF according to described recent history event detection, generate the treatment Countermeasures of historical events for carrying out following countermeasure according to default execution probability: the keep-alive out-of-service time of described website is set to grow most the keep-alive out-of-service time; The interconnected optical fiber cable of the circuit that described website is corresponding, optical module or change processing with the optical module of the interconnected opposite end website of described website; Ruuning situation and connectivity to equipment corresponding to described opposite end website are monitored processing.

9. each described method according to claim 3-7; it is characterized in that; when described recent history event indicates the opposite end website of two circuits of a website that SF event or keep-alive failure event alternately occur; the described recent history event that described basis reads is analyzed the network topology state of historical events, and the treatment Countermeasures of generation historical events comprises:

Generate the treatment Countermeasures of historical events according to the recent history event that reads for carrying out following countermeasure according to default execution probability: ruuning situation and connectivity to equipment corresponding to described website are monitored processing; Optical fiber cable and optical module that two circuits of described website are interconnected are changed processing.

10. each described method according to claim 3-7, it is characterized in that, when described recent history event indicates the number of times of a website generation FS/MS event and FS/MS releasing event to surpass default for the third time several threshold value, the described recent history event that described basis reads is analyzed the network topology state of historical events, and the treatment Countermeasures of generation historical events comprises:

Whether the treatment Countermeasures that generates historical events according to the recent history event that reads does not close for detecting the user's configuration script that uses in the test process.

11. a management server is characterized in that, comprising:

Wherein, described analysis module comprises:

12. management server according to claim 11 is characterized in that, when a website generation Signal Fail SF event of described topology information indication, described the first analytic unit comprises:

The first countermeasure generates subelement, be used for when detecting described website generation keep-alive inefficacy according to topology information and not detecting described website generation link failure, whether the treatment Countermeasures that generates the single failure event breaks down for equipment corresponding to the interconnected opposite end website of monitoring and described website, and when described opposite end equipment corresponding to website does not break down, monitor equipment corresponding to described website and whether break down;

The second countermeasure generates subelement, be used for when detecting described website generation link failure according to topology information and during with the interconnected opposite end website generation link failure of described website, whether the treatment Countermeasures that generates the single failure event breaks down for the link of the described opposite end of monitoring website to described website transmission data;

The 3rd countermeasure generates subelement, be used for when detecting described website according to topology information and all link failure occuring with the interconnected opposite end website of described website, whether the treatment Countermeasures that generates the single failure event breaks down for the link of monitoring between described website and the described opposite end website;

The 4th countermeasure generates subelement, be used for when detecting described website according to topology information and with the interconnected opposite end website of described website the misconnection ring occuring all, generating the treatment Countermeasures of single failure event for revising the misconnection ring of circuit between described website and the described opposite end website.

13. management server according to claim 11 is characterized in that, when a weak SD event of website generation signal of described topology information indication, described the first analytic unit comprises:

The 5th countermeasure generates subelement, be used for when detect described website generation line signal according to topology information weakly and do not detect with the interconnected opposite end website of described website and line signal to occur when weak, the treatment Countermeasures that generates the single failure event is the quantity of the error message adding up described website and receive from described opposite end website; When the difference of the quantity of described error message and default error message threshold value during less than default fault tolerant amount, improve described error message threshold value, when the difference of the quantity of described error message and default error message threshold value during greater than default fault tolerant amount, described opposite end website is changed processing to the link that described website sends data, wherein, described fault tolerant amount is for setting according to applicable cases;

The 6th countermeasure generates subelement, be used for line signal all occuring when weak when detect the interconnected opposite end website of described website and described website according to topology information the quantity of the error message that the treatment Countermeasures that generates the single failure event receives from described website for the quantity of the error message adding up described website and receive from described opposite end website and described opposite end website; The difference of the quantity of the error message that sends to described website when described opposite end website and the first default error message threshold value is during less than default fault tolerant amount, improve described the first error message threshold value, the difference of the quantity of the error message that sends to described website when described opposite end website and the first default error message threshold value is changed processing to described opposite end website to the link that described website sends data during greater than default fault tolerant amount; The difference of the quantity of the error message that sends to described opposite end website when described website and the second default error message threshold value is during less than default fault tolerant amount, improve described the second error message threshold value, the difference of the quantity of the error message that sends to described opposite end website when described website and the second default error message threshold value is during greater than default fault tolerant amount, described website is changed processing to the link that described opposite end website sends data, wherein, described fault tolerant amount is for setting according to applicable cases.

14. management server according to claim 11 is characterized in that, when website generation Forced Switch FS of described topology information indication or people when switching the MS event, described the first analytic unit comprises:

The 7th countermeasure generates subelement, is used for obtaining the circuit that FS or MS event occur described website according to topology information, and the treatment Countermeasures that generates the single failure event be the circuit in the website of webmaster feedback generation FS or MS event.

15. management server according to claim 11 is characterized in that, when a website generation Wait-to-Restore WTR event of described topology information indication, described the first analytic unit comprises:

Obtain subelement, be used for obtaining according to topology information the WTR configuration information of equipment corresponding to described website;

The 8th countermeasure generates subelement, be used for when described WTR configuration information be WTR when irrecoverable, the treatment Countermeasures of generation single failure event is for to feed back described WTR configuration information to webmaster;

The 9th countermeasure generates subelement, being used for working as described WTR configuration information is that WTR can recover, and when but equipment corresponding to described website still kept the WTR state after WTR recovery time surpassing the twice of default recovery time, it is unusual that the treatment Countermeasures that generates the single failure event is that the software of described equipment occurs.

16. management server according to claim 11 is characterized in that, when a website generation configuration change event of described topology information indication, described the first analytic unit comprises:

The tenth countermeasure generates subelement, is used for obtaining according to topology information the configuration change information of described website, generates the treatment Countermeasures of single failure event for to point out the configuration change information of described website to webmaster.

17. each described management server according to claim 11-16, it is characterized in that, recover the read-around ratio of event above the first default frequency threshold value when SF/SF occurs website of described recent history event indication, or when indicating website that number of times that SF/SF recovers event occurs to surpass the second default frequency threshold value, described the second analytic unit comprises:

The first historical countermeasure generates subelement, be used for when according to described recent history event detection to described SF during by invalid the causing of link of described website, the treatment Countermeasures that generates historical events be the interconnected optical fiber cable of circuit corresponding to described website or optical module appearance unusually;

The second historical countermeasure generates subelement, be used for when being lost efficacy when causing by the keep-alive of described website to described SF according to described recent history event detection, the treatment Countermeasures that generates historical events is to carry out following countermeasure according to the execution probability of presetting: the keep-alive out-of-service time of described website is set to grow most the keep-alive out-of-service time; The interconnected optical fiber cable of the circuit that described website is corresponding, optical module or change processing with the optical module of the interconnected opposite end website of described website; Ruuning situation and connectivity to equipment corresponding to described opposite end website are monitored processing.

18. each described management server according to claim 11-16; it is characterized in that; when described recent history event indicated the opposite end website of two circuits of a website that SF event or keep-alive failure event alternately occur, described the second analytic unit comprised:

The 3rd historical countermeasure generates subelement, and the treatment Countermeasures that is used for according to the recent history event generation historical events that reads is to carry out following countermeasure according to default execution probability: ruuning situation and connectivity to equipment corresponding to described website are monitored processing; Optical fiber cable and optical module that two circuits of described website are interconnected are changed processing.

19. each described management server according to claim 11-16, it is characterized in that, when described recent history event indicated the number of times of a website generation FS/MS event and FS/MS releasing event to surpass default for the third time several threshold value, described the second analytic unit comprised:

Whether the 4th historical countermeasure generation subelement is used for not closing for user's configuration script that the detection test process uses according to the treatment Countermeasures of the recent history event generation historical events that reads.

20. the analysis process system of a network topology is characterized in that, comprise a plurality of looped network equipment and according to claim 11-19 in each described management server.