CN101854263A - Method, system and management server for analysis processing of network topology - Google Patents

Method, system and management server for analysis processing of network topology Download PDF

Info

Publication number
CN101854263A
CN101854263A CN201010208446A CN201010208446A CN101854263A CN 101854263 A CN101854263 A CN 101854263A CN 201010208446 A CN201010208446 A CN 201010208446A CN 201010208446 A CN201010208446 A CN 201010208446A CN 101854263 A CN101854263 A CN 101854263A
Authority
CN
China
Prior art keywords
website
incident
topology
opposite end
error message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201010208446A
Other languages
Chinese (zh)
Other versions
CN101854263B (en
Inventor
吴航
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Star Net Ruijie Networks Co Ltd
Ruijie Networks Co Ltd
Original Assignee
Beijing Star Net Ruijie Networks Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Star Net Ruijie Networks Co Ltd filed Critical Beijing Star Net Ruijie Networks Co Ltd
Priority to CN 201010208446 priority Critical patent/CN101854263B/en
Publication of CN101854263A publication Critical patent/CN101854263A/en
Application granted granted Critical
Publication of CN101854263B publication Critical patent/CN101854263B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

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 the network maintenance staff, locatees and solve the fault that may occur fast, gets rid of hidden network danger immediately.And because the complexity of RPR looped network, the network maintenance staff need 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, make the network maintenance staff judge the contingent fault of current network according to information among the RPR MIB and the experience of self.
Yet, in the prior art faults analysis, location and solution in the RPR looped network are 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, locatees and solved network failure in order to solve in the prior art, realization is to the Collection and analysis of network topology incident, the analysis result of topological incident 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;
According to described topology information the network topology state is analyzed, and generated the treatment Countermeasures of event of failure.
The embodiment of the invention provides a kind of management server, comprising:
Receiver module is used for receiving the topology information that network that looped network equipment collects 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.
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 Collection and analysis to the network topology incident, the analysis result of topological incident is provided for the network maintenance staff, reduced specification requirement, improved the maintainable and stable of network the network maintenance staff.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do one to the accompanying drawing of required use in embodiment or the description of the Prior Art below introduces simply, apparently, accompanying drawing in describing below is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
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 is obtained 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 incident and the topological incident 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, promptly 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 represents respectively and the interconnected internal network of 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 transmission of rightabout each other forms, and for example the span between S0 and the S1 is made up 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, promptly 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) promptly 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 promptly 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 incident is that a kind of recovery transition state of RPR protocol definition, main purpose are to prevent that frequent SF, SD recovery incident from causing network topology frequently to be vibrated after the line fault that SF or SD take place is recovered.In addition, RPR also provides a configuration to select whether to wish that for the user WTR incident can be recovered automatically or the permanent WTR of reservation state, unless the incident of higher priority has taken place it is substituted.IDLE is the unprotect solicited status.Wherein 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 that SF, SD are initiatively announced by equipment, and it is triggered by user's configuration or device interior State Control.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 as can be seen, link1 corresponds to that S3 sends, S4 receives, link2 corresponds to that S4 sends, 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 real-time and effective and handle.
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 Collection and analysis to the network topology incident, the analysis result of topological incident is provided for the network maintenance staff, reduced specification requirement, improved the maintainable and stable of network the network maintenance staff.
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 incident that produces in the network, topology are stablized incident 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 takes place 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 takes place, 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 promptly relative with device start time relative time also can obtain according to the current standard time, is absolute time.This stable time of topology also can obtain according to the 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 incident 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, the then last final continual and steady time of 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 incidents such as SD or SF take place; 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 takes place promptly for first fault website that detects fault, also needs to write down the real event of change in topology.For example, trigger the SF incident reason can for since circuit connect disconnect, keep-alive is overtime or misconnection ring or the like.Wherein, because two interconnected websites of each RPR span connect under the normal situation at circuit; the capital initiatively externally sends the keep-alive message; in 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 incident that produces, then the real event of the SF incident of this situation generation is that keep-alive is overtime.And the misconnection ring be two circuits between interconnected two websites dislocation takes place to connect, for example, dislocation takes place to connect in two link among Fig. 3 between S3 and the S4, i.e. the reception of link2 is received in the transmission of link1, the reception of link1 is received in the transmission of link2.Looped network equipment also need write down the relative position of all the other websites in this website that change in topology takes place and this website and the network, with Fig. 2 is example, suppose that the S2 website has caused change in topology, the website of the generation change in topology that then writes down on the S1 website is the corresponding website of first jumping that the S1 website sends at ring 0, it is the corresponding website of first jumping that the S1 website sends in the clockwise direction, the perhaps website of the fifth jump correspondence of sending at ring 1 of S1 website, the i.e. website of the fifth jump correspondence of sending 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 communication in the present embodiment 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 content of carrying 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 under the situation that the network state of RPR looped network changes, promptly may be because the configuration that is used for is revised, equipment change or connect is changed 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 incident respectively according to the topology information of obtaining, and generates the treatment Countermeasures of single failure incident, and described single failure incident is the described single topology incident 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 incident that topology changes is divided into two classes, and a class is to break down to handle, and another kind of is that fault is recovered, and need not to handle.Therefore, for single topology incident, need adopt correspondingly countermeasure at the single failure incident, the single failure incident of present embodiment is that relevant incident appearred in fault when single topology incident was analyzed, and for historical events, then need to carry out the statistical analysis of all incidents, this step is specially the analyzing and processing to the single failure incident.In this step, management server is when the execution analysis process, by writing down last event handling numbering, and then which is discerned is newly-increased incident, numbering can adopt the 64bit coding, can write down 2 64 power bar records in theory, and therefore the problem of unrolling can not take place to number.Incident of people after last once event handling numbering is newly-increased incident, then management server reads the intact record number of analyzing and processing last time earlier, from event base, read this record number all records afterwards, then each record is carried out single analyses one by one and handle.
Management server is when analyzing single topology incident, can obtain the particular type of incident according to topology information, because having write down which span of which website in the topology information breaks down, therefore again by the record of two interconnected website corresponding equipment of this span, just can navigate to the concrete link that breaks down.When topology information is indicated some website generation Signal Fail SF incidents, management server can according to this website in the current topology information this topological incident and the logout of this website adjacent sites, this fault is classified as follows:
Particularly; when detecting according to topology information that this website generation keep-alive was lost efficacy and when not detecting described website generation link failure; the treatment Countermeasures that generates the single failure incident is for breaking down probably with the interconnected opposite end website corresponding equipment of described fault website, especially detects keep-alive too when overtime when the interconnected website of the another one span of this opposite end website corresponding equipment.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 taken place S3 equipment; lost efficacy if keep-alive all takes place 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 opposite end website corresponding equipment did not break down, whether the monitoring station corresponding equipment 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 incident is monitored this opposite end website for suggestion webmaster emphasis and is broken down to the link that this website sends data.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 taken place.
Particularly, when detecting described website according to topology information and all link failure taking place, generate the link that the treatment Countermeasures of single failure incident monitors between described website and the described opposite end website for suggestion webmaster emphasis and whether break down with the interconnected opposite end website of described 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 taken place.
Particularly, when detecting described website according to topology information and the misconnection ring all taking place, generate the misconnection ring of the treatment Countermeasures of single failure incident for circuit between described website of revision and the described opposite end website with the interconnected opposite end website of described website.
When topology information is indicated the weak SD incident of some website generation signals, management server can according to this website in the current topology information this topological incident and the logout of this website adjacent sites, this fault is classified as follows:
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 take place when weak when detecting according to topology information, the quantity of the error message that the treatment Countermeasures that generates the single failure incident 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, the fault tolerant amount difference of webmaster under the promptly 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 signal quality existing problems of this section link are represented in the alarm of SD, 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, the quantity that promptly shows 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, promptly reduce the thresholding that SD detects, judge whether to get rid of this SD fault then.Can't stand if the difference of the quantity of error message and default error message threshold value, shows promptly 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, the fault tolerant amount difference of webmaster under the promptly different applicable cases.
Particularly, line signal all takes place 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 incident 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 the described 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 the described 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, the quantity that promptly shows 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, promptly improve the fault tolerant amount, judge whether to get rid of this SD fault then.Can't stand if the quantity of error message, shows promptly 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 incident, management server can be according to this topological incident 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 circuit that FS or MS incident take place in the described website according to topology information, the treatment Countermeasures that generates the single failure incident is the circuit in the website of webmaster feedback generation FS or MS incident.Promptly dispose generation because FS or MS incident have only by the user, so only need this moment certain span of certain website of notice webmaster that FS or MS incident have taken place, whether PLSCONFM is that the result who expects gets final product.
When topology information is indicated some website generation Wait-to-Restore WTR incidents; management server can be according to this topological incident 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 the WTR configuration information of described website corresponding equipment earlier 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 transceive data; when (acquiescence is 10 seconds through after a while; the longest 1440 seconds) the protection incident of other high priority does not take place 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 described website corresponding equipment 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 incident 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 on fault span, carrying out the MS configuration, removing the operation of MS configuration to address this problem.
When topology information is indicated some website generation configuration change incidents, management server can be according to this topological incident 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, the treatment Countermeasures that generates the single failure incident is for to point out the configuration change information of described website to webmaster.Promptly provide information, show which configuration of which website has caused this change in topology incident, judge the reasonability of this incident by webmaster to webmaster.
Step 404, management server read the recent history incident of the described single topology incident correspondence of respective amount from described event base according to default related historical record bar number.
After a single topology event analysis is finished, management server reads the recent history incident of this single topology incident correspondence of respective amount from event base according to default related historical record bar number, related historical record bar number herein can be set as required by webmaster, as be set at 5, then management server reads 5 recent history incidents from event base, i.e. 5 recent history incidents before the record number of this single topology incident.Present embodiment is the maximum difference of the analysis of historical events with the analysis of single topology incident before, the SF incident takes place in common single circuit, for example optical fiber is dug disconnected, then do not have artificial intervention to replace new optical fiber, so the SF incident can't be recovered because of construction reason.And loose contact can recover in the extremely short time after causing circuit SF automatically mostly, therefore only checks that current topological state is difficult to perceive this fault, need analyze a plurality of historical record incidents.
Management server judges whether the record number of the recent history incident that reads is continuous, if then use these recent history incidents to start the historical data analysis process; Otherwise directly use current continuous recent history incident to start the historical data analysis process.Because webmaster can be inquired about or 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 promptly appears, then present embodiment is only analyzed the historical events of serial number, in case find that numbering is discontinuous, then only analyze till the numbering breakpoint corresponding historical incident.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 incident.
Step 405, management server is analyzed the network topology state of historical events according to the described recent history incident that reads, and generates the treatment Countermeasures of historical events.
Management server can obtain the statistical conditions of historical record incident according to topology information when historical events is analyzed, carry out analyzing and processing according to the statistical conditions of historical record incident.Indicate a website that SF/SF takes place when the recent history incident and recover the read-around ratio of incident above the first default frequency threshold value, or when indicating website that number of times that SF/SF recovers incident takes place to surpass the second default frequency threshold value, herein first frequency threshold value and second frequency threshold value can specifically be set according to actual conditions by webmaster, as being set at 3 and 5 respectively, be that management server is known certain website continuous 3 times or above generation SF/SF recovery (from WTR to IDLE) incident according to the historical data of obtaining, typically be certain website continuous several times SF/SF recovery incident takes place, and the stable time that continues of each topology is all shorter, as in one hour, or know that certain website once took place at least or 5 times or above SF/SF recovery incident.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, the treatment Countermeasures that generates historical events is that the circuit interconnected fibers line or the optical module of described website correspondence occurs unusual.Modal situation is that the link generation SF incident that is that triggers repeatedly SF causes that according to knowing in the single failure analysis, SF also divides single link that the SF incident takes place and the SF incident takes place two link simultaneously.Then management server can provide alarm to webmaster: the notice webmaster might this fault span interconnected fibers line loose contact or optical module unusual, need 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 be notified manufacturer's maintenance and provide historical record for manufacturer's personnel inquiry.
Particularly; when losing 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 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; promptly come the preferential execution of front,, then continue to carry out follow-up countermeasure if countermeasure is not before fixed a breakdown.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 the longest keep-alive out-of-service time; If a last countermeasure can not be dealt with problems, advise that then webmaster changes processing with the circuit interconnected fibers line of described website correspondence, optical module or with the optical module of the interconnected opposite end website of described website; If a last countermeasure can not be dealt with problems, advise that then webmaster monitors processing to the ruuning situation and the connectivity of described opposite end website corresponding equipment, and keep in repair and provide corresponding historical record and observed result observing under the situation of fault the manufacturer of contact in time.
When the recent history incident indicates the opposite end website of two circuits of a website that SF incident or keep-alive failure event alternately take place, both sides adjacent sites S2 and S4 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 incident that reads, execution explanations on probability herein is similar to the above, repeat no more: management server suggestion webmaster is monitored processing to the ruuning situation and the connectivity of described website corresponding equipment herein, keeps in repair and provide corresponding historical record and observed result observing under the situation of fault the manufacturer of contact in time; If a last countermeasure can not be dealt with problems, then management server suggestion webmaster is changed processing to two the circuit interconnected fibers lines and the optical module of described website.
Surpass defaultly when counting threshold value for the third time when number of times that FS/MS incident and FS remove incident takes place website of recent history incident indication, whether management server can not close for detecting the user's configuration script that uses in the test process according to the treatment Countermeasures that the recent history incident that reads generates historical events.Promptly provide user's configuration script that alarm and notice webmaster may exist some test processs to use and forget and close, delete the FS/MS configuration then, need webmaster to check the behavior of corresponding control terminal at the FS/MS that carries out that does not stop to webmaster.
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 Collection and analysis to the network topology incident, the analysis result of topological incident is provided for the network maintenance staff, help webmaster maintaining network equipment and analyze to solve fault in time better, reduced specification requirement, improved the maintainable and stable of network the network maintenance staff.
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: 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 first analytic unit 513, reading unit 523 and second analytic unit 533.Wherein, first analytic unit 513 is used for respectively the network topology state of single topology incident being analyzed according to the topology information of obtaining, and generates the treatment Countermeasures of single failure incident, and described single failure incident is the described single topology incident that breaks down.Reading unit 523 is used for reading from described event base according to default related historical record bar number the recent history incident of the described single topology incident correspondence of respective amount.Second analytic unit 533 is used for according to the described recent history incident that reads the network topology state of historical events being analyzed, and generates the treatment Countermeasures of historical events.
Further, when website generation Signal Fail SF incident of described topology information indication, first analytic unit 513 can comprise specifically that first countermeasure generates subelement 5131, second countermeasure generates subelement 5132, the 3rd countermeasure generation subelement 5133 and the 4th countermeasure and generates subelement 5134.Wherein, first countermeasure generates subelement 5131 and is used for when detecting described website generation keep-alive inefficacy according to topology information and do not detect described website generation link failure; whether the treatment Countermeasures that generates the single failure incident breaks down for the interconnected opposite end website corresponding equipment of monitoring and described website; and when described opposite end website corresponding equipment does not break down, monitor described website corresponding equipment and whether break down.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 incident 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 taking place with the interconnected opposite end website of described website, and whether the treatment Countermeasures that generates the single failure incident 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 when detecting described website according to topology information and with the interconnected opposite end website of described website the misconnection ring taking place all, and the treatment Countermeasures that generates the single failure incident is for revising the misconnection ring of circuit between described website and the described opposite end website.
Perhaps, when the weak SD incident of website generation signal of described topology information indication, 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 take place when weak, and the treatment Countermeasures that generates the single failure incident 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 taking place 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 incident 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 the described 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 the described 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 incident, 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 incident take place described website according to topology information, and the treatment Countermeasures that generates the single failure incident is the circuit in the website of webmaster feedback generation FS or MS incident.
Perhaps, when website generation Wait-to-Restore WTR incident of described topology information indication, 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 described website corresponding equipment.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 incident is for to feed back described WTR configuration information to webmaster.It is that WTR can recover that the 9th countermeasure generation subelement 5231 is used for working as described WTR configuration information, and when but described website corresponding equipment 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 incident is that the software of described equipment occurs.
Perhaps, when website generation configuration change incident of described topology information indication, 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, and the treatment Countermeasures that generates the single failure incident is for to point out the configuration change information of described website to webmaster.
Further, recover the read-around ratio of incident above the first default frequency threshold value when SF/SF takes place website of described recent history incident indication, or when indicating website that number of times that SF/SF recovers incident takes place to surpass the second default frequency threshold value, 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 circuit interconnected fibers line of described website correspondence 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 the longest keep-alive out-of-service time; Change processing with the circuit interconnected fibers line of described website correspondence, optical module or with the optical module of the interconnected opposite end website of described website; Ruuning situation and connectivity to described opposite end website corresponding equipment are monitored processing.
Perhaps, when described recent history incident indicates the opposite end website of two circuits of a website that SF incident or keep-alive failure event alternately take place, second analytic unit 533 can comprise specifically that the treatment Countermeasures that the 3rd historical countermeasure generation subelement 5333, the three historical countermeasures generation subelements 5333 are used for according to the recent history incident generation historical events that reads is to carry out following countermeasure according to the execution probability of presetting: ruuning situation and connectivity to described website corresponding equipment are monitored processing; Two circuit interconnected fibers lines and optical module to described website are changed processing.
Perhaps, surpass default when counting threshold value for the third time when number of times that FS/MS incident and FS remove incident takes place website of described recent history incident indication, second analytic unit 533 can comprise specifically that the 4th historical countermeasure generation subelement 5334, the four historical countermeasures generate subelements 5334 and are 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 incident 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 Collection and analysis to the network topology incident, the analysis result of topological incident is provided for the network maintenance staff, help webmaster maintaining network equipment and analyze to solve fault in time better, reduced specification requirement, improved the maintainable and stable of network the network maintenance staff.
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 put 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 (22)

1. the analysis and processing method of a network topology is characterized in that, 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;
According to described topology information the network topology state is analyzed, and generated the treatment Countermeasures of event of failure.
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 takes place 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 takes place, and the defective that exists in the current network is indicated.
3. method according to claim 1 is characterized in that, describedly according to described topology information the network topology state is analyzed, and the treatment Countermeasures that generates event of failure comprises:
Respectively the network topology state of single topology incident is analyzed according to the topology information of obtaining, and generated the treatment Countermeasures of single failure incident, described single failure incident is the described single topology incident that breaks down;
From described event base, read the recent history incident of the described single topology incident correspondence of respective amount according to default related historical record bar number;
According to the described recent history incident that reads the network topology state of historical events is analyzed, and generated the treatment Countermeasures of historical events.
4. method according to claim 3, it is characterized in that, when website generation Signal Fail SF incident of described topology information indication, the topology information that described basis is obtained is analyzed the network topology state of single topology incident respectively, and the treatment Countermeasures of generation single failure incident comprises:
When detecting according to topology information that described website generation keep-alive was lost efficacy and when not detecting described website generation link failure, whether the treatment Countermeasures that generates the single failure incident breaks down for the interconnected opposite end website corresponding equipment of monitoring and described website, and when described opposite end website corresponding equipment does not break down, monitor described website corresponding equipment 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 incident 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 taking place with the interconnected opposite end website of described website, whether the treatment Countermeasures that generates the single failure incident breaks down for the link between described website of monitoring and the described opposite end website;
When detecting described website according to topology information and the misconnection ring all taking place, generate the misconnection ring of the treatment Countermeasures of single failure incident for circuit between described website of revision and the described opposite end website with the interconnected opposite end website of described website.
5. method according to claim 3, it is characterized in that, when the weak SD incident 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 incident respectively, and the treatment Countermeasures of generation single failure incident 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 take place when weak when detecting according to topology information, the quantity of the error message that the treatment Countermeasures that generates the single failure incident 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 takes place 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 incident 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 described 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 the described 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.
6. method according to claim 3, it is characterized in that, when website generation Forced Switch FS of described topology information indication or people when switching the MS incident, the topology information that described basis is obtained is analyzed the network topology state of single topology incident respectively, and the treatment Countermeasures of generation single failure incident comprises:
Obtain the circuit that FS or MS incident take place in the described website according to topology information, the treatment Countermeasures that generates the single failure incident is the circuit in the website of webmaster feedback generation FS or MS incident.
7. method according to claim 3, it is characterized in that, when website generation Wait-to-Restore WTR incident of described topology information indication, the topology information that described basis is obtained is analyzed the network topology state of single topology incident respectively, and the treatment Countermeasures of generation single failure incident comprises:
Obtain the WTR configuration information of described website corresponding equipment according to topology information;
When described WTR configuration information is WTR when irrecoverable, the treatment Countermeasures that generates the single failure incident is for to feed back described WTR configuration information to webmaster;
When described WTR configuration information is that WTR can recover, but and when described website corresponding equipment 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 incident is that the software of described equipment occurs.
8. method according to claim 3, it is characterized in that, when website generation configuration change incident of described topology information indication, the topology information that described basis is obtained is analyzed the network topology state of single topology incident respectively, and the treatment Countermeasures of generation single failure incident comprises:
Obtain the configuration change information of described website according to topology information, the treatment Countermeasures that generates the single failure incident is for to point out the configuration change information of described website to webmaster.
9. according to each described method among the claim 3-8, it is characterized in that, recover the read-around ratio of incident above the first default frequency threshold value when SF/SF takes place website of described recent history incident indication, or when indicating website that number of times that SF/SF recovers incident takes place to surpass the second default frequency threshold value, the described recent history incident 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, the treatment Countermeasures that generates historical events is that the circuit interconnected fibers line or the optical module of described website correspondence occurs unusual;
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 for carrying out following countermeasure according to default execution probability: the keep-alive out-of-service time of described website is set to the longest keep-alive out-of-service time; Change processing with the circuit interconnected fibers line of described website correspondence, optical module or with the optical module of the interconnected opposite end website of described website; Ruuning situation and connectivity to described opposite end website corresponding equipment are monitored processing.
10. according to each described method among the claim 3-8; it is characterized in that; when described recent history incident indicates the opposite end website of two circuits of a website that SF incident or keep-alive failure event alternately take place; the described recent history incident that described basis reads is analyzed the network topology state of historical events, and the treatment Countermeasures of generation historical events comprises:
The treatment Countermeasures that generates historical events according to the recent history incident that reads is for carrying out following countermeasure according to default execution probability: ruuning situation and connectivity to described website corresponding equipment are monitored processing; Two circuit interconnected fibers lines and optical module to described website are changed processing.
11. according to each described method among the claim 3-8, it is characterized in that, surpass default when counting threshold value for the third time when number of times that FS/MS incident and FS remove incident takes place website of described recent history incident indication, the described recent history incident 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 incident that reads does not close for detecting the user's configuration script that uses in the test process.
12. a management server is characterized in that, comprising:
Receiver module is used for receiving the topology information that network that looped network equipment collects 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.
13. management server according to claim 12 is characterized in that, described analysis module comprises:
First analytic unit is used for respectively the network topology state of single topology incident being analyzed according to the topology information of obtaining, and generates the treatment Countermeasures of single failure incident, and described single failure incident is the described single topology incident that breaks down;
Reading unit is used for the default related historical record bar number of basis reads the described single topology incident correspondence of respective amount from described event base recent history incident;
Second analytic unit is used for according to the described recent history incident that reads the network topology state of historical events being analyzed, and generates the treatment Countermeasures of historical events.
14. management server according to claim 13 is characterized in that, when website generation Signal Fail SF incident of described topology information indication, described first analytic unit comprises:
First countermeasure generates subelement, be used for when detecting according to topology information that described website generation keep-alive was lost efficacy and when not detecting described website generation link failure, whether the treatment Countermeasures that generates the single failure incident breaks down for the interconnected opposite end website corresponding equipment of monitoring and described website, and when described opposite end website corresponding equipment does not break down, monitor described website corresponding equipment and whether break down;
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 incident breaks down to the link that described website sends data for the described opposite end of monitoring website;
The 3rd countermeasure generates subelement, be used for when detecting described website according to topology information and all link failure taking place with the interconnected opposite end website of described website, whether the treatment Countermeasures that generates the single failure incident breaks down for the link between described website of monitoring and the described opposite end website;
The 4th countermeasure generates subelement, be used for when detecting described website according to topology information and the misconnection ring all taking place, generating the misconnection ring of the treatment Countermeasures of single failure incident for circuit between described website of revision and the described opposite end website with the interconnected opposite end website of described website.
15. management server according to claim 13 is characterized in that, when the weak SD incident of website generation signal of described topology information indication, described first analytic unit comprises:
The 5th countermeasure generates subelement, be used for when detect described website generation line signal according to topology information weak and do not detect with the interconnected opposite end website of described website and line signal to take place when weak, the quantity of the error message that the treatment Countermeasures that generates the single failure incident 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;
The 6th countermeasure generates subelement, be used for line signal all taking place when weak the quantity of the error message that the quantity of the error message that the treatment Countermeasures that generates the single failure incident receives from described opposite end website for the described website of statistics and described opposite end website receive from described website when detect the interconnected opposite end website of described website and described website according to topology information; 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 described 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 the described 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.
16. management server according to claim 13 is characterized in that, when website generation Forced Switch FS of described topology information indication or people when switching the MS incident, described first analytic unit comprises:
The 7th countermeasure generates subelement, is used for obtaining the circuit that FS or MS incident take place described website according to topology information, and the treatment Countermeasures that generates the single failure incident is the circuit in the website of webmaster feedback generation FS or MS incident.
17. management server according to claim 13 is characterized in that, when website generation Wait-to-Restore WTR incident of described topology information indication, described first analytic unit comprises:
Obtain subelement, be used for obtaining the WTR configuration information of described website corresponding equipment according to topology information;
The 8th countermeasure generates subelement, be used for when described WTR configuration information be WTR when irrecoverable, the treatment Countermeasures of generation single failure incident 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 described website corresponding equipment 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 incident is that the software of described equipment occurs.
18. management server according to claim 13 is characterized in that, when website generation configuration change incident of described topology information indication, described first analytic unit comprises:
The tenth countermeasure generates subelement, is used for obtaining according to topology information the configuration change information of described website, and the treatment Countermeasures that generates the single failure incident is for to point out the configuration change information of described website to webmaster.
19. according to each described management server among the claim 13-18, it is characterized in that, recover the read-around ratio of incident above the first default frequency threshold value when SF/SF takes place website of described recent history incident indication, or when indicating website that number of times that SF/SF recovers incident takes place to surpass the second default frequency threshold value, described 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 is that the circuit interconnected fibers line or the optical module of described website correspondence occurs unusual;
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 for carrying out following countermeasure according to default execution probability: the keep-alive out-of-service time of described website is set to the longest keep-alive out-of-service time; Change processing with the circuit interconnected fibers line of described website correspondence, optical module or with the optical module of the interconnected opposite end website of described website; Ruuning situation and connectivity to described opposite end website corresponding equipment are monitored processing.
20. according to each described management server among the claim 13-18; it is characterized in that; when described recent history incident indicated the opposite end website of two circuits of a website that SF incident or keep-alive failure event alternately take place, described second analytic unit comprised:
The 3rd historical countermeasure generates subelement, and the treatment Countermeasures that is used for according to the recent history incident generation historical events that reads is to carry out following countermeasure according to default execution probability: ruuning situation and connectivity to described website corresponding equipment are monitored processing; Two circuit interconnected fibers lines and optical module to described website are changed processing.
21. according to each described management server among the claim 13-18, it is characterized in that, surpass defaultly when counting threshold value for the third time when number of times that FS/MS incident and FS remove incident takes place website of described recent history incident indication, described second analytic unit comprises:
Whether the 4th historical countermeasure generates subelement, be used for not closing for user's configuration script that the detection test process uses according to the treatment Countermeasures of the recent history incident generation historical events that reads.
22. the analysis process system of a network topology is characterized in that, comprises a plurality of looped network equipment and according to each described management server among the claim 12-21.
CN 201010208446 2010-06-13 2010-06-13 Method, system and management server for analysis processing of network topology Expired - Fee Related CN101854263B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN 201010208446 CN101854263B (en) 2010-06-13 2010-06-13 Method, system and management server for analysis processing of network topology

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN 201010208446 CN101854263B (en) 2010-06-13 2010-06-13 Method, system and management server for analysis processing of network topology

Publications (2)

Publication Number Publication Date
CN101854263A true CN101854263A (en) 2010-10-06
CN101854263B CN101854263B (en) 2013-03-13

Family

ID=42805541

Family Applications (1)

Application Number Title Priority Date Filing Date
CN 201010208446 Expired - Fee Related CN101854263B (en) 2010-06-13 2010-06-13 Method, system and management server for analysis processing of network topology

Country Status (1)

Country Link
CN (1) CN101854263B (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103797468A (en) * 2011-09-21 2014-05-14 惠普发展公司，有限责任合伙企业 Automated detection of a system anomaly
CN103905276A (en) * 2014-03-27 2014-07-02 国家电网公司 Fast network topology detecting method
CN104956338A (en) * 2012-12-04 2015-09-30 惠普发展公司，有限责任合伙企业 Displaying information technology conditions with heat maps
CN113721581A (en) * 2021-07-20 2021-11-30 深圳市风云实业有限公司 Fault diagnosis display device and method based on critical path
CN114978922A (en) * 2022-05-17 2022-08-30 重庆邮电大学 Dynamic topological data acquisition method

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1650274A (en) * 2002-12-26 2005-08-03 富士通株式会社 Operation managing method and operation managing server
CN101174899A (en) * 2007-11-26 2008-05-07 中兴通讯股份有限公司 Automatic testing method for service protection and recovery in ASON network
CN101247278A (en) * 2007-08-06 2008-08-20 北京高信达网络科技有限公司 Routing monitoring apparatus
CN101567814A (en) * 2009-05-22 2009-10-28 清华大学 Automatic network management method based on SNMP and stochastic Petri net

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1650274A (en) * 2002-12-26 2005-08-03 富士通株式会社 Operation managing method and operation managing server
CN101247278A (en) * 2007-08-06 2008-08-20 北京高信达网络科技有限公司 Routing monitoring apparatus
CN101174899A (en) * 2007-11-26 2008-05-07 中兴通讯股份有限公司 Automatic testing method for service protection and recovery in ASON network
CN101567814A (en) * 2009-05-22 2009-10-28 清华大学 Automatic network management method based on SNMP and stochastic Petri net

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103797468A (en) * 2011-09-21 2014-05-14 惠普发展公司，有限责任合伙企业 Automated detection of a system anomaly
US9292408B2 (en) 2011-09-21 2016-03-22 Hewlett Packard Enterprise Development Lp Automated detection of a system anomaly
CN104956338A (en) * 2012-12-04 2015-09-30 惠普发展公司，有限责任合伙企业 Displaying information technology conditions with heat maps
US10121268B2 (en) 2012-12-04 2018-11-06 Entit Software Llc Displaying information technology conditions with heat maps
CN103905276A (en) * 2014-03-27 2014-07-02 国家电网公司 Fast network topology detecting method
CN113721581A (en) * 2021-07-20 2021-11-30 深圳市风云实业有限公司 Fault diagnosis display device and method based on critical path
CN114978922A (en) * 2022-05-17 2022-08-30 重庆邮电大学 Dynamic topological data acquisition method
CN114978922B (en) * 2022-05-17 2023-09-12 重庆邮电大学 Dynamic topology data acquisition method

Also Published As

Publication number Publication date
CN101854263B (en) 2013-03-13

Similar Documents

Publication Publication Date Title
CN109104349B (en) Train network data transmission method, system and device based on CANopen protocol
CN102714607B (en) Connectivity fault management timeout period control
US7430688B2 (en) Network monitoring method and apparatus
CN101426306A (en) A disaster tolerance switching method, system and apparatus
CN101854263B (en) Method, system and management server for analysis processing of network topology
CN105323113A (en) A visualization technology-based system fault emergency handling system and a system fault emergency handling method
CN102045204B (en) Fault treatment system and method
EP2568733A1 (en) Method and apparatus for collecting mobile communication data
CN105430327A (en) NVR cluster backup method and device
CN109104325B (en) Train network data transmission method, system and device based on CANopen protocol
CN103532738A (en) Port connection relationship determination method and device
CN102231674A (en) Processing method and apparatus of far-end fault of Ethernet
CN101924661B (en) Alarm processing method and device
CN101980478B (en) Method and device for detecting and processing equipment failures and network equipment
EP1622310B1 (en) Administration method and system for network management systems
CN101895797A (en) Method and device for realizing all-fiber protection
CN103812697A (en) Remote disaster recovery method and remote disaster recovery system of distributed communication network
CN104639358A (en) Batched network port switching method and system
CN111309515A (en) Disaster recovery control method, device and system
CN117527653A (en) Cluster heartbeat management method, system, equipment and medium
CN110224872B (en) Communication method, device and storage medium
US20170070410A1 (en) System and method for providing redundant ethernet network connections
JP2008244902A (en) Failure recovery apparatus, failure recovery method, and failure recovery system
CN102833115B (en) A kind of alert processing method of port and system
CN115549775A (en) Method for processing optical signal transmission abnormity, optical transmission equipment and system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20130313

Termination date: 20160613

CF01 Termination of patent right due to non-payment of annual fee