CN109194520A - A kind of Trap information processing method and device - Google Patents
A kind of Trap information processing method and device Download PDFInfo
- Publication number
- CN109194520A CN109194520A CN201811150567.1A CN201811150567A CN109194520A CN 109194520 A CN109194520 A CN 109194520A CN 201811150567 A CN201811150567 A CN 201811150567A CN 109194520 A CN109194520 A CN 109194520A
- Authority
- CN
- China
- Prior art keywords
- trap
- file
- information
- retrieval
- time
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Abstract
The embodiment of the present invention provides a kind of Trap information processing method and device.In the embodiment of the present invention, NM server obtains the Trap information sent that managed devices record from managed devices, meanwhile, NM server locally records received Trap information.If in received Trap information not including the Trap information that managed devices have been sent, alerted based on Trap information not to be covered, is leaked to avoid NM server and alert missing caused by receiving Trap information.
Description
Technical field
The present invention relates to network communication technology field more particularly to a kind of Trap information processing methods and device.
Background technique
In the network management for being based on SNMP (Simple Network Management Protocol, Simple Network Management Protocol)
In system, when managed devices state change (for example, failure), Trap (trap) message actively can be sent to NM server.
NM server is alerted according to the Trap information carried in Trap message, is managed with reminding network administrator to handle in time
The equipment problem (for example, repairing failure).
After managed devices send Trap message to NM server, managed devices can wait returning for NM server
It answers, to confirm whether NM server receives Trap information.If NM server is because failure can not receive Trap message and return
It answers, then managed devices can retransmit Trap message.When sending times reach preset frequency threshold value, no longer retransmit.In this phase
Between, if NM server does not restore normally, alarm can be caused to lack because Trap information is received in leakage.
Summary of the invention
The present invention proposes to solve the problems, such as to alert missing caused by existing NM server receives Trap information because of leakage
A kind of Trap information processing method and device are lacked with alerting caused by receiving Trap information because of leakage to avoid NM server.
For achieving the above object, the present invention provides the following technical scheme that
In a first aspect, the present invention provides a kind of Trap information processing method, it is applied to NM server, the method packet
It includes:
The first Trap file is obtained from managed devices, the first Trap file is logical for recording the managed devices
Cross the first Trap information of Trap message transmission；
From the 2nd Trap file being locally stored, the first Trap information is retrieved, the 2nd Trap file is for recording
The 2nd Trap information that the NM server is received by Trap message；
If not retrieving the first Trap information, alerted based on the first Trap information.
Second aspect, the present invention provide a kind of Trap information processing unit, are applied to NM server, described device packet
It includes:
Acquiring unit, for obtaining the first Trap file from managed devices, the first Trap file is for recording institute
State the first Trap information that managed devices are sent by Trap message；
Retrieval unit, for retrieving the first Trap information, the 2nd Trap from the 2nd Trap file being locally stored
File is for recording the 2nd Trap information that the NM server is received by Trap message；
Alarm Unit, if being alerted for not retrieving the first Trap information based on the first Trap information.
In the embodiment of the present invention it can be seen from above description, NM server is managed from managed devices acquisition and sets
The Trap information of note sent, meanwhile, NM server locally records received Trap information.If received
Do not include the Trap information that managed devices have been sent in Trap information, is then alerted based on Trap information not to be covered, with
Missing is alerted caused by avoiding NM server leakage from receiving Trap information.
Detailed description of the invention
To describe the technical solutions in the embodiments of the present invention more clearly, make required in being described below to embodiment
Attached drawing is briefly described, it should be apparent that, drawings in the following description are only some embodiments of the invention, for
For those of ordinary skill in the art, without creative efforts, it can also be obtained according to these attached drawings other
Attached drawing.
Fig. 1 is a kind of Trap information processing method flow chart shown in the embodiment of the present invention；
Fig. 2 is the 2nd Trap file generated process shown in the embodiment of the present invention；
Fig. 3 is the implementation process of the step 102 shown in the embodiment of the present invention；
Fig. 4 is a kind of structural schematic diagram of Trap information processing unit shown in the embodiment of the present invention.
Specific embodiment
Example embodiments are described in detail here, and the example is illustrated in the accompanying drawings.Following description is related to
When attached drawing, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements.Following exemplary embodiment
Described in embodiment do not represent all embodiments consistented with the present invention.On the contrary, they be only with it is such as appended
The example of device and method being described in detail in claims, some aspects of the invention are consistent.
It is only to be not intended to limit the invention merely for for the purpose of describing particular embodiments in terminology used in the present invention.
It is also intended in the present invention and the "an" of singular used in the attached claims, " described " and "the" including majority
Form, unless the context clearly indicates other meaning.It is also understood that term "and/or" used herein refers to and wraps
It may be combined containing one or more associated any or all of project listed.
It will be appreciated that though various information, but this may be described using term first, second, third, etc. in the present invention
A little information should not necessarily be limited by these terms.These terms are only used to for same type of information being distinguished from each other out.For example, not departing from
In the case where the scope of the invention, negotiation information can also be referred to as the second information, and similarly, the second information, which can also be referred to as, assists
Quotient's information.Depending on context, word as used in this " if " can be construed to " ... when " or " when ...
When " or " in response to determination ".
The embodiment of the present invention provides a kind of Trap information processing method, and in this method, NM server is from managed devices
The Trap information of managed devices record sent is obtained, meanwhile, NM server locally records received Trap information.
If in received Trap information not including the Trap information that managed devices have been sent, based on Trap information not to be covered into
Row alarm alerts missing caused by receiving Trap information because of leakage to avoid NM server.
It is with reference to the accompanying drawing and specific real in order to keep the purposes, technical schemes and advantages of the embodiment of the present invention clearer
It applies example and detailed description is executed to the embodiment of the present invention:
It is Trap information processing method flow chart provided in an embodiment of the present invention referring to Fig. 1.The process takes applied to network management
Business device.
As shown in Figure 1, the process can comprise the following steps that
Step 101, NM server obtains the first Trap file from managed devices.
First Trap file is for recording the first Trap information that managed devices are sent by Trap message.Here,
First Trap file, the first Trap information are only named for ease of description, are not intended to limit.
In specific implementation, the Trap journal function of managed devices can be started.One Trap of the every transmission of managed devices
Message records one article of Trap information (the first Trap information) in Trap journal file (the first Trap file).
When NM server restores from malfunction, then the acquisition of Trap journal file can be sent to managed devices and is asked
It asks, to obtain the first Trap file from managed devices.
Step 102, from the 2nd Trap file being locally stored, the first Trap information is retrieved.
2nd Trap file is for recording the 2nd Trap information that NM server is received by Trap message.This
In, the 2nd Trap file, the 2nd Trap information are only named for ease of description, are not intended to limit.
The process for retrieving the first Trap information, is described below, and wouldn't repeat here.
Step 103, if not retrieving the first Trap information, NM server is based on the first Trap information and is alerted.
It does not include the first Trap information that managed devices have been sent in the received Trap information of NM server, because
This, NM server is alerted based on the first Trap information that the leakage is received.
So far, process shown in Fig. 1 is completed.
As can be seen from the flow chart shown in fig. 1, in embodiments of the present invention, NM server obtains quilt from managed devices
The Trap information of management equipment record sent, meanwhile, NM server locally records received Trap information.If having connect
Do not include the Trap information that managed devices have been sent in the Trap information of receipts, is then accused based on Trap information not to be covered
It is alert, it is leaked to avoid NM server and alerts missing caused by receiving Trap information.
It further include the product process of the 2nd Trap file before executing step 102 as one embodiment.
As shown in Fig. 2, the process can comprise the following steps that
Step 201, the 2nd Trap information is stored in temporary file by NM server.
In specific implementation, NM server can parse the 2nd Trap information from received Trap message, and deposit is faced
When file.
Step 202, if the size of temporary file reaches preset size threshold value, and/or, temporary file there are when be up to
To preset duration threshold value, NM server generates the 2nd Trap file according to the temporary file.
For example, preset size threshold value is 100M, preset duration threshold value is 1 hour, then when the size of temporary file reaches
To 100M, and/or, temporary file there are when it is long reach 1 hour when, which is renamed, the 2nd Trap text is generated
Part.
So far, process shown in Fig. 2 is completed.
By process shown in Fig. 2, NM server, which is realized, generates the 2nd Trap file.
Below to step 102 from the 2nd Trap file being locally stored, the first Trap information of retrieval is described.Referring to
Fig. 3 is the implementation process of the step 102 shown in the embodiment of the present invention.
As shown in figure 3, the process can comprise the following steps that
Step 301, NM server determines the period of this retrieval.
In the embodiment of the present invention, managed devices and NM server are same using the existing time synchronization protocol progress time
Step, the time scale to guarantee managed devices and management server are unified.Managed devices record in the first Trap file
The generation time of first Trap information.NM server records the receiving time of the 2nd Trap information in the 2nd Trap file.
The initial time of the period of this retrieval is the deadline of last retrieval, and specifically, which is
The generation time of the last one the first Trap information of last time retrieval；The end time of the period of this retrieval is currently to deposit
The 2nd Trap file in the receiving time of the 2nd Trap information that finally receives.
It should be noted that the primary retrieval in the embodiment of the present invention refers to that NM server reads one from managed devices
After secondary first Trap file, the first Trap information of each of the first Trap file whether there is in the 2nd Trap file
It is retrieved.
Step 302, from the 2nd Trap file, determine that there are the 3rd Trap of time intersection with the period of this retrieval
File.
As previously mentioned, NM server is based on the 2nd Trap file of long generation in the presence of file size or file, therefore, net
Can generally there are multiple 2nd Trap files in pipe server.
The period that this step is determined based on step 301 screens the 3rd Trap file from the 2nd Trap file, to reduce
Range of search.Here, the 3rd Trap file is only named for ease of description, is not intended to limit.
The specific process for determining the 3rd Trap file, is described below, wouldn't repeat here.
Step 303, from the 3rd Trap file, the first Trap information is retrieved.
So far, process shown in Fig. 3 is completed.
By process shown in Fig. 3, NM server, which can be realized, reduces range of search based on the period, avoids repeated retrieval.
Below to step 302 from the 2nd Trap file, the with period of this retrieval there are time intersection is determined
Three Trap files are described.
As one embodiment, NM server obtains the receiving time of each 2nd Trap information in the 2nd Trap file.
Based on the receiving time of each 2nd Trap information, NM server determines connecing for the 2nd Trap information that the 2nd Trap file includes
Receive time range.From the 2nd Trap file, NM server determines that the period of receiving time range and this retrieval exists
3rd Trap file of intersection.
For example: if the receiving time of the first 2nd Trap information recorded in current 2nd Trap file is 9:00,
The receiving time of the last one the 2nd Trap information of record is 10:00, then the 2nd Trap letter that the 2nd Trap file includes
The receiving time range of breath is 9:00~10:00.If this retrieval time section is 9:30~10:30, current 2nd Trap text
Period of the corresponding receiving time section of part and this retrieval there are time intersection (9:30~10:00), accordingly, it is determined that current the
Two Trap files are the 3rd Trap file.
As another embodiment, when naming the 2nd Trap file, can include in the filename of the 2nd Trap file
Temporal information.The temporal information is the receiving time of the first 2nd Trap information recorded in the 2nd Trap file.Based on second
The temporal information for including in the filename of Trap file determines that there are the 3rd Trap of time intersection with the period of this retrieval
File.
For example: if the receiving time of the first 2nd Trap information recorded in file 1 (the 2nd Trap file) is 9:
00, then the filename of file 1 can be trap0900, wherein " 0900 " represents time 9:00；If file 2 is (after file 1
The 2nd Trap file generated) in the receiving time of first 2nd Trap information that records be 10:00, the then filename of file 2
It can be trap1000, wherein " 1000 " represent time 10:00.The period of this retrieval is 9:30~10:30.Obtain text
The temporal information for including in the filename of part, i.e. 1000 in the filename of 0900 and file 2 in the filename of file 1, can
Know, there may be the 2nd Trap information received after 9:30 in file 1, accordingly, it is determined that file 1 be with this retrieval when
Between section there are the 3rd Trap files of time intersection；There are the 2nd Trap information received after 10:00 in file 2, therefore,
Determine that file 2 is that there are the 3rd Trap files of time intersection with the period of this retrieval.
So far, NM server, which is realized, determines the 3rd Trap file based on the period.
As one embodiment, the invention also includes: NM server determines the corresponding last inspection of each managed devices
Minimum deadline in the deadline of rope.If the corresponding receiving time section of the 2nd Trap file is less than minimum deadline,
Then delete the 2nd Trap file.
Due to managed devices be it is multiple, each managed devices correspond to it is respective it is last retrieve it is part-time when
Between, NM server can be determined multiple according to the deadline of the respective corresponding last retrieval of each managed devices
The smallest deadline in deadline.That is, the 2nd Trap file before minimum deadline will not be fallen into again
The corresponding retrieval time section of any one managed devices, therefore, the 2nd Trap file that the embodiment of the present invention will not be used
It deletes, to save memory space.
As one embodiment, the invention also includes: if the first Trap information in the first Trap file has executed inspection
Rope (for example, the first Trap information in the first Trap file is usually stored according to the sequencing of generation, and therefore, network manager service
Device can successively execute retrieval to the first Trap information of each of the first Trap file, until complete to the last one first
The retrieval of Trap information just confirms that the first Trap information of each of the first Trap file has executed retrieval), i.e., to first
The first Trap information of each of Trap file had verified that whether be that NM server leaks the Trap information received, then network management
Server can delete the first Trap file being locally stored, to save the memory space of NM server.
Method provided in an embodiment of the present invention is described below by specific embodiment:
It is with a NM server (being denoted as Server1) and two managed devices (being denoted as Device1 and Device2)
Example.Wherein, Server1, Device1 and Device2 time synchronization.
Managed devices (Device1, Device2) start Trap journal function.When Trap event occurs, it is managed and sets
It is standby to send Trap message to Server1, and corresponding Trap information is recorded in Trap journal file (being denoted as Logfile).
Server1 receives the Trap message that Device1 and Device2 is sent, and the Trap information that Trap message carries is deposited
Enter temporary file, is denoted as Tempfile.Default temporary file is 1 hour there are duration threshold value, and file size threshold value is 100M,
Then Tempfile there are when long reach 1 hour and/or when file size reaches 100M, Server1 orders Tempfile again
Name, generates formal Trap file, is denoted as Trapfile.
After Server1 is restarted because of failure, Logfile is read from Device1 and Device2 respectively.It here, will be from
The Logfile that Device1 is read, is denoted as Logfile1；The Logfile read from Device2, is denoted as Logfile2.As one
A embodiment, Server1 is after managed devices reading Logfile, using the IP address of managed devices to Logfile weight
New name, so as to it is subsequent can be which quilt according to what is recorded in filename (IP address of managed devices) quickly confirmation file
The Trap information of management equipment.
It is the example of Logfile1 referring to table 1.
Table 1
It is the example of Logfile2 referring to table 2.
Table 2
Server1 has currently generated 3 Trapfile, is denoted as Trapfile1, Trapfile2, Trapfile3 respectively.
It is the example of Trapfile1 referring to table 3.
Table 3
Wherein, IP1 is the IP address of Device1；IP2 is the IP address of Device2, respectively represents to be managed from difference and sets
The standby Trap information received.
It is the example of Trapfile2 referring to table 4.
Table 4
It is the example of Trapfile3 referring to table 5.
Table 5
For ease of description, this example has ignored to generate and that may be present between time and receiving time slightly be delayed.I.e.
The time that Trap information generates on managed devices is identical as the time that the Trap information is received by Server1.
It should be noted that journal file (Logfile) and network manager service that NM server is obtained from managed devices
The format of the Trap file (Trapfile) that device locally generates may be different, therefore, before retrieval, need from journal file and
It is parsed in Trap file and is used directly for the information that retrieval compares, that is, with parsing the IP of the equipment recorded in above-mentioned file
Location, Trap information, generation time, receiving time etc..
In addition, also record has each managed devices corresponding last deadline (upper one retrieved in Server1
The generation time of secondary the last one the Trap information retrieved).If managed devices were not retrieved also after network management system is added,
The deadline of record is the time that network management system is added in managed devices.Referring to table 6, when being the retrieval recorded in Server1
Between record sheet.
Table 6
Now by taking the Logfile1 read from Device1 as an example, following inspection is executed to the Trap information recorded in Logfile1
Rope operation:
As previously mentioned, after Server1 reads the Logfile1 in Device1, using the IP address (IP1) of Device1
It renames, therefore, Server1 can obtain the corresponding last retrieval of IP1 according to the IP1 inquiry table 6 for including in filename
Deadline (T5)；Meanwhile obtaining the receiving time of the Trap information received the latest recorded in the Trapfile of local
(T10).The period that [T5, T10] is retrieved as this.It should be noted that T1~T10 is time identifier, numerical value is bigger
Indicate the time more rearward.
Determine that there are the Trapfile of time intersection with the period [T5, T10].As shown in Table 3, Trapfile1 connects
Receiving the period is [T1, T4]；As shown in Table 4, the receiving time section of Trapfile2 is [T5, T7]；As shown in Table 5,
The receiving time section of Trapfile3 is T10.Accordingly, it can be determined that with the period [T5, T10], there are the Trapfile of time intersection
Including Trapfile2 and Trapfile3.Logfile1 (the log of Device1 is retrieved i.e. in Trapfile2 and Trapfile3
File) in Trap information.
Deadline due to having recorded last retrieval in table 6 is T5, i.e. the Trap information generated before T5 has been retrieved
It crosses, therefore, is this time retrieved Trap information of the retrieval after T5 in Logfile1 (table 1).
Firstly, with the presence or absence of M14 in Server1 retrieval Trapfile2 (the generation time is T6).As shown in Table 4,
There are M14 in Trapfile2, and therefore, Server1, which determines not leak, receives M14.
Server1 is retrieved with the presence or absence of M15 (the generation time is T8) in Trapfile2, as shown in Table 4, in Trapfile2
There is no M15.Continue to retrieve with the presence or absence of M15 in Trapfile3, as shown in Table 5, M15 is also not present in Trapfile3.Cause
This, Server1 determines that M15 has been received in leakage, and M15 is recorded in record alert database, carries out alarm amended record, and accused based on M15
It is alert.
M15 is the last one Trap information in Logfile1, and this time retrieval terminates.Server1 is by the generation time of M15
T8 is recorded in retrieval time record sheet, as the initial time retrieved next time.Updated retrieval time record sheet, such as table
Shown in 7.
Table 7
Since Trap information had all been retrieved in Logfile1, it can delete and be stored in Server1
Logfile1, to save memory space.
Similarly, it is retrieved to from the Trap information in the Logfile2 that Device2 is read, details are not described herein.Complete
After the retrieval of Trap information in pairs of Logfile2, retrieval time record sheet is as shown in table 8.
Table 8
As shown in Table 8, minimum retrieval deadline is T8, and receiving time section is located at the Trapfile before T8
(Trapfile1 and Trapfile2) no longer needs in later retrieval, and therefore, Trapfile1 and Trapfile2 is deleted, with
Save memory space.
So far, the description to this specific embodiment is completed.
Method provided in an embodiment of the present invention is described above, below to device provided in an embodiment of the present invention into
Row description:
It referring to fig. 4, is the structural schematic diagram of device provided in an embodiment of the present invention.The device include: acquiring unit 401,
Retrieval unit 402 and Alarm Unit 403, in which:
Acquiring unit 401, for obtaining the first Trap file from managed devices, the first Trap file is for recording
The first Trap information that the managed devices are sent by Trap message；
Retrieval unit 402 retrieves the first Trap information for from the 2nd Trap file being locally stored, and described second
Trap file is for recording the 2nd Trap information that the NM server is received by Trap message；
Alarm Unit 403, if being accused for not retrieving the first Trap information based on the first Trap information
It is alert.
As one embodiment, described device further include:
Generation unit, for the 2nd Trap information to be stored in temporary file；If the size of the temporary file reaches default
Size threshold value, and/or, the temporary file there are when length reach preset duration threshold value, it is raw according to the temporary file
At the 2nd Trap file.
It further include the generation time of the first Trap information as one embodiment, in the first Trap file；
The retrieval unit 402, specifically for determining the period of this retrieval, the initial time of the period is upper
The deadline of primary retrieval, end time of the period be there is currently the 2nd Trap file in finally receive
The receiving time of 2nd Trap information, wherein the deadline of the last retrieval be last retrieval the last one the
The generation time of one Trap information；From the 2nd Trap file, the with period of this retrieval there are time intersection is determined
Three Trap files；From the 3rd Trap file, the first Trap information is retrieved.
As one embodiment, the retrieval unit 402 determines the period with this retrieval from the 2nd Trap file
There are the 3rd Trap files of time intersection, comprising:
Obtain the receiving time of each 2nd Trap information in the 2nd Trap file；
Based on the receiving time of each 2nd Trap information, the 2nd Trap information that the 2nd Trap file includes is determined
Receiving time range；
From the 2nd Trap file, determine that receiving time range and this period retrieved, there are the 3rd Trap of intersection
File；
Alternatively,
It include temporal information in the filename of the 2nd Trap file, the temporal information is the 2nd Trap file
The receiving time of the first 2nd Trap information of middle record；
The temporal information for including in filename based on the 2nd Trap file determined and in the presence of the period of this retrieval
Between intersection the 3rd Trap file.
As one embodiment, described device further include:
Unit is deleted, when the minimum in deadline for determining the corresponding last retrieval of each managed devices is ended
Between；If the corresponding receiving time section of the 2nd Trap file is less than the minimum deadline, the 2nd Trap file is deleted；If the
The first Trap information in one Trap file has executed retrieval, deletes the first Trap file being locally stored.
So far, the description of Fig. 4 shown device is completed.In embodiments of the present invention, NM server is obtained from managed devices
The Trap information sent for taking managed devices to record, meanwhile, NM server locally records received Trap information.If
Do not include the Trap information that managed devices have been sent in received Trap information, is then carried out based on Trap information not to be covered
Alarm leaks to avoid NM server and alerts missing caused by receiving Trap information.
The foregoing is merely the preferred embodiments of the embodiment of the present invention, are not intended to limit the invention, all in this hair
Within the spirit and principle of bright embodiment, any modification, equivalent substitution, improvement and etc. done should be included in protection of the present invention
Within the scope of.
Claims (10)
1. a kind of Trap information processing method is applied to NM server, which is characterized in that the described method includes:
The first Trap file is obtained from managed devices, the first Trap file passes through for recording the managed devices
The first Trap information that Trap message is sent；
From the 2nd Trap file being locally stored, the first Trap information is retrieved, the 2nd Trap file is described for recording
The 2nd Trap information that NM server is received by Trap message；
If not retrieving the first Trap information, alerted based on the first Trap information.
2. the method as described in claim 1, which is characterized in that described from the 2nd Trap file being locally stored, retrieval the
Before one Trap information, further includes:
2nd Trap information is stored in temporary file；
If the size of the temporary file reaches preset size threshold value, and/or, the temporary file there are when length reach pre-
If duration threshold value, according to the temporary file generate the 2nd Trap file.
3. the method as described in claim 1, which is characterized in that further include the first Trap letter in the first Trap file
It is the generation time of breath, described from the 2nd Trap file being locally stored, retrieve the first Trap information, comprising:
Determine the period of this retrieval, the initial time of the period is the deadline of last retrieval, the time
The end time of section be there is currently the 2nd Trap file in the receiving time of the 2nd Trap information that finally receives,
In, the deadline of the last retrieval is the generation time of the last one the first Trap information of last retrieval；
From the 2nd Trap file, determine that there are the 3rd Trap files of time intersection with the period of this retrieval；
From the 3rd Trap file, the first Trap information is retrieved.
4. method as claimed in claim 3, which is characterized in that it is described from the 2nd Trap file, it determines and this retrieval
Period, there are the 3rd Trap files of time intersection, comprising:
Obtain the receiving time of each 2nd Trap information in the 2nd Trap file；
Based on the receiving time of each 2nd Trap information, the reception for the 2nd Trap information that the 2nd Trap file includes is determined
Time range；
From the 2nd Trap file, determine that receiving time range and this period retrieved, there are the 3rd Trap of intersection texts
Part；
Alternatively,
It include temporal information in the filename of the 2nd Trap file, the temporal information is to remember in the 2nd Trap file
The receiving time of the first 2nd Trap information of record；
The temporal information for including in filename based on the 2nd Trap file determines that there are time friendships with the period of this retrieval
3rd Trap file of collection.
5. method as claimed in claim 3, which is characterized in that the method also includes:
Determine the minimum deadline in the deadline of the corresponding last retrieval of each managed devices；
If the corresponding receiving time section of the 2nd Trap file is less than the minimum deadline, the 2nd Trap file is deleted；
If the first Trap information in the first Trap file has executed retrieval, the first Trap file being locally stored is deleted.
6. a kind of Trap information processing unit, it is applied to NM server, which is characterized in that described device includes:
Acquiring unit, for obtaining the first Trap file from managed devices, the first Trap file is for recording the quilt
The first Trap information that management equipment is sent by Trap message；
Retrieval unit, for retrieving the first Trap information, the 2nd Trap file from the 2nd Trap file being locally stored
The 2nd Trap information received for recording the NM server by Trap message；
Alarm Unit, if being alerted for not retrieving the first Trap information based on the first Trap information.
7. device as claimed in claim 6, which is characterized in that described device further include:
Generation unit, for the 2nd Trap information to be stored in temporary file；If the size of the temporary file reaches preset big
Small threshold value, and/or, the temporary file there are when length reach preset duration threshold value, generate the according to the temporary file
Two Trap files.
8. device as claimed in claim 6, which is characterized in that further include the first Trap letter in the first Trap file
The generation time of breath；
The retrieval unit, specifically for determining the period of this retrieval, the initial time of the period is last inspection
The deadline of rope, end time of the period be there is currently the 2nd Trap file in finally receive second
The receiving time of Trap information, wherein the deadline of the last retrieval be last retrieval the last one first
The generation time of Trap information；From the 2nd Trap file, determine that there are the thirds of time intersection with the period of this retrieval
Trap file；From the 3rd Trap file, the first Trap information is retrieved.
9. device as claimed in claim 8, which is characterized in that the retrieval unit determines and this from the 2nd Trap file
The period of secondary retrieval, there are the 3rd Trap files of time intersection, comprising:
Obtain the receiving time of each 2nd Trap information in the 2nd Trap file；
Based on the receiving time of each 2nd Trap information, the reception for the 2nd Trap information that the 2nd Trap file includes is determined
Time range；
From the 2nd Trap file, determine that receiving time range and this period retrieved, there are the 3rd Trap of intersection texts
Part；
Alternatively,
It include temporal information in the filename of the 2nd Trap file, the temporal information is to remember in the 2nd Trap file
The receiving time of the first 2nd Trap information of record；
The temporal information for including in filename based on the 2nd Trap file determines that there are time friendships with the period of this retrieval
3rd Trap file of collection.
10. device as claimed in claim 8, which is characterized in that described device further include:
Unit is deleted, the minimum deadline in deadline for determining the corresponding last retrieval of each managed devices；
If the corresponding receiving time section of the 2nd Trap file is less than the minimum deadline, the 2nd Trap file is deleted；If first
The first Trap information in Trap file has executed retrieval, deletes the first Trap file being locally stored.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811150567.1A CN109194520B (en) | 2018-09-29 | 2018-09-29 | Trap information processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811150567.1A CN109194520B (en) | 2018-09-29 | 2018-09-29 | Trap information processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109194520A true CN109194520A (en) | 2019-01-11 |
| CN109194520B CN109194520B (en) | 2022-04-26 |
Family
ID=64908067
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811150567.1A Active CN109194520B (en) | 2018-09-29 | 2018-09-29 | Trap information processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109194520B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020069199A1 (en) * | 2000-12-01 | 2002-06-06 | Young-Hyun Kang | Method for managing alarm information in a network management system |
| CN1925427A (en) * | 2006-09-04 | 2007-03-07 | 华为技术有限公司 | Warning system and warning method |
| CN101127715A (en) * | 2002-11-20 | 2008-02-20 | 华为技术有限公司 | Reliability guarantee method for data packet transmission in SNMP |
| CN101577646A (en) * | 2009-06-22 | 2009-11-11 | 武汉烽火网络有限责任公司 | Alarm synchronizing method based on SNMP |
| CN101877653A (en) * | 2010-06-29 | 2010-11-03 | 中兴通讯股份有限公司 | Method and system for judging whether alarm variable information is lost or not as well as master control board |
| CN105991320A (en) * | 2015-02-05 | 2016-10-05 | 中兴通讯股份有限公司 | Method for processing warning information of passive optical network(PON) device and optical line terminal (OLT) |
-
2018
- 2018-09-29 CN CN201811150567.1A patent/CN109194520B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020069199A1 (en) * | 2000-12-01 | 2002-06-06 | Young-Hyun Kang | Method for managing alarm information in a network management system |
| CN101127715A (en) * | 2002-11-20 | 2008-02-20 | 华为技术有限公司 | Reliability guarantee method for data packet transmission in SNMP |
| CN1925427A (en) * | 2006-09-04 | 2007-03-07 | 华为技术有限公司 | Warning system and warning method |
| CN101577646A (en) * | 2009-06-22 | 2009-11-11 | 武汉烽火网络有限责任公司 | Alarm synchronizing method based on SNMP |
| CN101877653A (en) * | 2010-06-29 | 2010-11-03 | 中兴通讯股份有限公司 | Method and system for judging whether alarm variable information is lost or not as well as master control board |
| CN105991320A (en) * | 2015-02-05 | 2016-10-05 | 中兴通讯股份有限公司 | Method for processing warning information of passive optical network(PON) device and optical line terminal (OLT) |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109194520B (en) | 2022-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107943951B (en) | Method and system for retrieving block chain service information | |
| US7865548B2 (en) | Email recovery method and system | |
| CN107465549B (en) | Distributed message processing method and system | |
| EP1929705B1 (en) | Device management method using nodes having additional attribute and device management client thereof | |
| US7664848B2 (en) | System and method for monitoring networked devices employing RSS functionality | |
| US8930402B1 (en) | Systems and methods for automatic collection of data over a network | |
| US20030187868A1 (en) | Data acquisition system | |
| CN109871392B (en) | Slow sql real-time data acquisition method under distributed application system | |
| CN112052247A (en) | Index updating system, method and device of search engine, electronic equipment and storage medium | |
| CN108347459A (en) | A kind of high in the clouds data quick storage method and device | |
| CN113986649A (en) | System monitoring device and method based on prometheus service | |
| CN110888790B (en) | Log management method and device, electronic equipment and storage medium | |
| EP1929706A1 (en) | Device management system using log management object and method for generating and controlling logging data therein | |
| US6609155B1 (en) | Method and apparatus for providing relationships in simple network management protocol management information base | |
| CN109194520A (en) | A kind of Trap information processing method and device | |
| US9852031B2 (en) | Computer system and method of identifying a failure | |
| CN110858813A (en) | Network camera safety detection method and device | |
| WO2012139462A1 (en) | Method, device, and system that enable signaling tracking | |
| JP2002063007A (en) | Notification system for printing environment information change | |
| CN101764707A (en) | Processing method, conversion device and processing system for network configuration event notification message | |
| Faltstrom et al. | How to interact with a WHOIS++ mesh | |
| CN110300193B (en) | Method and device for acquiring entity domain name | |
| CN110647298B (en) | Data storage control method and device | |
| CN105634789B (en) | A kind of method, equipment and the Log Collect System of collector associate device | |
| US20040243653A1 (en) | System and method for generating an alarm when an abnormal database backup status occurs |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |