CN101662383A - Method and equipment for configuring maintenance end points - Google Patents
Method and equipment for configuring maintenance end points Download PDFInfo
- Publication number
- CN101662383A CN101662383A CN200910093035A CN200910093035A CN101662383A CN 101662383 A CN101662383 A CN 101662383A CN 200910093035 A CN200910093035 A CN 200910093035A CN 200910093035 A CN200910093035 A CN 200910093035A CN 101662383 A CN101662383 A CN 101662383A
- Authority
- CN
- China
- Prior art keywords
- mep
- service instance
- maintenance field
- configuration parameter
- client device
- 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
Images
Abstract
The invention provides a method and equipment for configuring maintenance end points. By requesting for MEP configuration parameter from MEP server equipment by MEP customer side equipment, the methodand the equipment can automatically configure MEP according to the obtained MEP configuration parameter, thus improving the configuration efficiency of MEP and reducing the work load of manual configuration of MEP.
Description
Technical field
The present invention relates to be communicated with mismanage (CFM, Connectivity Fault Management) technical field, be specifically related to the method and apparatus of a kind of configuring maintenance end points (MEP, Maintenance association End Point).
Background technology
Dispose simply, safeguard simple advantage owing to have it, ethernet technology obtains immense success in the local area network (LAN) field, thereby impels service provider, equipment manufacturers and standardization body that ethernet technology is advanced to metropolitan area network and wide area network field.But ethernet technology enters the major obstacle that the operator field faced lacks effective maintenance and management instrument exactly, so the CFM technology is arisen at the historic moment.
CFM be a kind of two layers of (data link layer) link of defining in the IEEE 802.1ag standard, end to end, based on VLAN (VLAN, Virtual Local Area Network) Operations, Administration and Maintenance (OAM, Operations, Administration and Maintenance) mechanism is mainly used in and detects connectivity of link in double layer network, confirms fault, also determines the position that fault takes place.Please refer to Fig. 1, comprise device A～E among Fig. 1, each equipment all has 1～4 port.Below in conjunction with Fig. 1, simply introduce the related notion among the CFM.
Maintenance field (MD, Maintenance Domain): MD has indicated the network that connection error detection (CFD, Connectivity Fault Detection) is covered, and its border is defined by a series of maintaining end points that are configured on the device port.Maintenance field is with safeguarding that domain name identifies.For fault location point exactly, CFD has introduced the notion of level in maintenance field.It is 8 grades that maintenance field is divided into, and represents with integer 0～7, and the rank (Level) of the big more expression maintenance field of numeral is high more, and the scope of maintenance field is also big more.Two maintenance field MD_A and MD_B have been shown among Fig. 1.
Safeguard collection (MA, Maintenance Association): MA is the set of some maintenance points in the maintenance field.Safeguard that collection identifies with " safeguard domain name+safeguard set name ".MA has indicated the VLAN that is served, and the message that maintenance point sent among the MA has this VLAN label, and the maintenance point among the MA can receive the message that other maintenance point sends among this MA simultaneously.
Maintenance point (MP, Maintenance Point): be configured on the device port, belong to certain MA.Maintenance point can be divided into two kinds: MEP and Maintenance Intermediate Point (MIP, Maintenance associationIntermediate Point).
MEP:MEP is configured on the device port, belongs to certain MA, identifies with an integer, is called MEP sign (MEP ID).MEP has determined the scope and the border of maintenance field.For example, maintenance field MD_A is made of the port one of device A, the port 3 of equipment D and port 4 these three maintaining end points of equipment E among Fig. 1.Maintenance collection and maintenance field under the MEP have been determined the VLAN attribute and the rank of the message that MEP sent.MEP has directivity, is divided into export-oriented and introversive two kinds.For example, the port one of the device A among Fig. 1 is interior to MEP, and the port 3 of equipment B then is export-oriented MEP.The direction of MEP has shown the position of maintenance field with respect to this port, wherein export-oriented MEP is at the port at this extroversion MEP place transmitting-receiving CFM message, and interior then is to receive and dispatch the CFM message except interior other ports to the port at MEP place in the same VLAN on equipment to MEP
The communication with detection time interval (CCI, Continuity Check Interval): the time interval in the continuity detection messages (CCM, Continuity Check Message) that maintaining end point sends.
Service Instance (SI, Service Instance): Service Instance is with an integer representation, represented one in the maintenance field to safeguard collection.Maintenance field and maintenance collection have then been determined the level attribute and the VLAN attribute of the handled message of maintenance point in the Service Instance.
With Fig. 1 is example, and the device A among Fig. 1, equipment D and equipment E are in same maintenance field MD_A, and the port 4 of the port one of device A, equipment E and the port 4 of equipment D are maintaining end points of MD_A.
For making MEP can really bring into play the connection error detection function, prior art need be carried out the MEP configuration to the equipment at MEP place, specifically comprises following configuration step:
1, enables connection error detection (CFM) function of (unlatching) equipment.
2, configuration device adds a MD, and disposes the rank (Level) in this MD territory.
3, configuration device adds a MA, and with this MA and the VLAN binding of wanting to detect, promptly disposes the corresponding relation between MA and the VLAN, and the VLAN of this MA correspondence is exactly the VLAN that wants to carry out communication with detection.
4, this maintenance collection that adds for equipment is specified a Service Instance (SI), this SI has represented a MA that MD is interior, and this MD and MA have determined the level attribute (i.e. the rank of this MD) and the VLAN attribute (i.e. the VLAN of this MA correspondence) of the handled message of MEP in this SI.In the MEP configuration, MEP finally is configured in (being that MEP is corresponding to some Service Instances) on the Service Instance, and the maintenance field rank of this Service Instance correspondence and VLAN be the maintenance field rank and the VLAN of this MEP correspondence just.
5, be the time interval (CCI) of all the maintaining end point configuration transmission CCM in this SI;
6, be this SI configuration MEP tabulation (MEPList).The MEP tabulation is the set that allows Local MEP with the MEP ID of the far-end MEP that needs monitoring of configuration in the same MA, it defines the scope of choosing of the MEP ID in the MA: all the MEP ID on the distinct device in the same MA should be included in this tabulation, and each MEP ID does not repeat mutually.
7, dispose MEP under selected port, the MEP ID of this MEP must be within the MEP of SI tabulation.
8, enable the connection error detection function of this MEP, this MEP just can be communicated with error detection to real reception CCM like this;
9, enable the CCM sending function of this MEP, this MEP just can begin to send CCM like this, so that other MEP are communicated with error detection to this MEP.
Wherein above-mentioned steps 1,8 and 9 belongs to switching function, and each equipment vendor may realize different, and what have may not realize switching function, and directly acquiescence comes into force, and in other words, realizes switching function, but the switch acquiescence is opened.
From above layoutprocedure as can be seen, the MEP layoutprocedure of prior art is quite numerous and diverse.And, to set up normal diconnected error detection neighbours between two MEP in same maintenance field and the maintenance collection, these two MEP must meet following requirement:
The Level of a, MD title and MD must be identical;
The VLAN of b, MA title and MA control must be identical;
C, MD and CCI among the MA must be identical;
All maintaining end points on d, the distinct device in the same maintenance collection all should be included among the MEPList, and MEP ID does not repeat mutually.
More than every in if any wherein one do not meet, then can't normally set up two-way connection error detection neighbours between the MEP, equipment will report the interconnection mistake, receive wrong a series of error reportings such as CCM message.
From the above as can be seen, because the step of configuration MEP is very loaded down with trivial details, and configuration requirement is very high, and same maintenance field must be identical with the relevant configuration of safeguarding the MEP that collection is interior.Therefore, the shortcoming that there is inefficiency in the manual configuration method of prior art and makes mistakes easily, especially big, MEP quantity in network size more for a long time, this shortcoming is particularly outstanding.
Summary of the invention
Technical problem to be solved by this invention provides the method and apparatus of a kind of MEP of configuration, in order to improve the efficient of MEP configuration.
For solving the problems of the technologies described above, it is as follows to the invention provides scheme:
The method of a kind of configuring maintenance end points MEP comprises:
Steps A, when the MEP client device is a MEP at needs configuration self first port, according to a VLAN, the first maintenance field rank and the first direction of a predetermined MEP correspondence, multicast sends and carries described other first request message of the first maintenance field level in a VLAN;
Step B, described MEP client device receives second response message that carries the MEP configuration parameter that the MEP server apparatus returns, described MEP configuration parameter includes MEP sign, described MEP sign is that described MEP server apparatus is after receiving first request message from a described VLAN, the still untapped MEP sign of from the MEP tabulation of second Service Instance, selecting, described second Service Instance is the Service Instance corresponding to described first a maintenance field rank and a VLAN that disposes on the described MEP server apparatus;
Step C, described MEP client device obtain described MEP configuration parameter from described second response message, and dispose described first port according to described MEP configuration parameter.
Preferably, in the said method, among the described step C, describedly dispose described MEP client device according to described MEP configuration parameter and comprise: disposing described first port is a MEP, and dispose the described MEP of being designated of described MEP sign, and the direction that disposes a described MEP is described first direction.
Preferably, in the said method, described MEP configuration parameter also includes the maintenance field of the described second Service Instance correspondence and safeguards the communication with detection time interval of the title of collection, the described second Service Instance correspondence and the MEP tabulation of described second Service Instance;
Among the described step C, describedly dispose described first port according to described MEP configuration parameter and also comprise:
On described MEP client device, create first maintenance field, and in described first maintenance field, create first and safeguard collection, and described first maintenance field and first is set safeguards that the title of collection is respectively the maintenance field of the described second Service Instance correspondence and safeguards the title of collection;
On described MEP client device, create first Service Instance of safeguarding collection corresponding to described first maintenance field and first, MEP tabulation with described second Service Instance, be set to the MEP tabulation of described first Service Instance, and, with the communication with detection time interval of the described second Service Instance correspondence, be set to the communication with detection time interval of the described first Service Instance correspondence;
The Service Instance that disposes a described MEP correspondence is described first Service Instance.
Preferably, in the said method, also comprise between described steps A and the step B:
Described MEP client device receives first response message that carries described MEP configuration parameter that described MEP server apparatus returns, from described first response message, obtain described MEP configuration parameter, and multicast sends second request message that carries described MEP configuration parameter in a described VLAN;
Described MEP server apparatus is after receiving described second request message, extract the described MEP sign that comprises in described second request message, and judge whether described MEP sign is not used yet: if, then from the MEP tabulation of described second Service Instance, delete described MEP sign in the still untapped MEP sign, and send described second response message to described MEP client device; Otherwise, process ends.
Preferably, in the said method, obtain described MEP configuration parameter from described first response message after, described method also comprises:
Described MEP client device extracts the title of the maintenance field of the described second Service Instance correspondence in the described MEP configuration parameter, and judges the local maintenance field that whether disposes the described second Service Instance correspondence:
If judge then whether the rank of the maintenance field of the local described second Service Instance correspondence that disposes equals the described first maintenance field rank: if then multicast sends described second request message in a described VLAN; Otherwise, abandon described first response message and process ends;
Otherwise multicast sends described second request message in a described VLAN.
Preferably, in the said method, before sending described second request message, described method also comprises:
Described MEP client device extracts the MEP tabulation of described second Service Instance in the described MEP configuration parameter, and whether the MEP sign total number during the MEP that judges described second Service Instance tabulates and the MEP of described MEP client device tabulates exceeds predetermined thresholding: if then abandon described first response message and process ends; Otherwise, send described second request message.
Preferably, in the said method, after described step C, by mutual continuity detection messages, set up detection of connectivity neighborhood each other between described MEP client device and the MEP server apparatus, and start MEP configuration ageing timer respectively;
Described MEP client device is after described MEP configuration ageing timer is overtime, and the detection of connectivity neighborhood between deletion and the described MEP server apparatus is cancelled the MEP configuration of first port, and deleted described first Service Instance;
Described MEP server apparatus is after described MEP configuration ageing timer is overtime, detection of connectivity neighborhood between deletion and the described MEP server apparatus, and described MEP sign is added to again during still untapped MEP in the MEP tabulation of described second Service Instance identifies.
The present invention also provides a kind of MEP client device, comprising:
First transmitting element, be used for when needs dispose this MEP client device first port and are a MEP, according to a VLAN, the first maintenance field rank and the first direction of a predetermined MEP correspondence, multicast sends and carries described other first request message of the first maintenance field level in a VLAN;
Second receiving element, be used to receive second response message that carries the MEP configuration parameter that the MEP server apparatus returns, described MEP configuration parameter includes MEP sign, described MEP sign is that described MEP server apparatus is after receiving first request message from a described VLAN, the still untapped MEP sign of from the MEP tabulation of second Service Instance, selecting, described second Service Instance is the Service Instance corresponding to described first a maintenance field rank and a VLAN that disposes on the described MEP server apparatus;
Dispensing unit is used for obtaining described MEP configuration parameter from described second response message, and disposes described first port according to described MEP configuration parameter.
Preferably, in the above-mentioned MEP client device, described dispensing unit, also being used to dispose described first port is a MEP, and disposes the described MEP of being designated of described MEP sign, and the direction that disposes a described MEP is described first direction.
Preferably, in the above-mentioned MEP client device, described MEP configuration parameter also includes the maintenance field of the described second Service Instance correspondence and safeguards the communication with detection time interval of the title of collection, the described second Service Instance correspondence and the MEP tabulation of described second Service Instance;
Described dispensing unit also is used for:
Create first maintenance field, and in described first maintenance field, create first and safeguard collection, and described first maintenance field and first is set safeguards that the title of collection is respectively the maintenance field of the described second Service Instance correspondence and safeguards the title of collection;
First Service Instance of collection is safeguarded in establishment corresponding to described first maintenance field and first, MEP tabulation with described second Service Instance, be set to the MEP tabulation of described first Service Instance, and, with the communication with detection time interval of the described second Service Instance correspondence, be set to the communication with detection time interval of the described first Service Instance correspondence;
The Service Instance that disposes a described MEP correspondence is described first Service Instance.
Preferably, in the above-mentioned MEP client device, also comprise:
First receiving element is used to receive first response message that carries described MEP configuration parameter that described MEP server apparatus returns, and obtains described MEP configuration parameter from described first response message, and triggers second transmitting element;
Second transmitting element is used for sending second request message that carries described MEP configuration parameter at a described VLAN multicast;
Wherein, described second response message be described MEP server apparatus after receiving described second request message, after judging the described MEP sign that comprises in described second request message and not being used yet, just send to this MEP client device.
Preferably, in the above-mentioned MEP client device, described first receiving element also is used for extracting the title of maintenance field of the described second Service Instance correspondence of described MEP configuration parameter, and judges the local maintenance field that whether disposes the described second Service Instance correspondence:
If judge then whether the rank of the maintenance field of the local described second Service Instance correspondence that disposes equals the described first maintenance field rank: if then trigger described second transmitting element; Otherwise, abandon described first response message;
Otherwise, trigger described second transmitting element.
Preferably, in the above-mentioned MEP client device, described second transmitting element, also be used for extracting the MEP tabulation of described second Service Instance of described MEP configuration parameter, and whether the MEP sign total number during the MEP that judges described second Service Instance tabulates and the MEP of this MEP client device tabulates exceeds predetermined thresholding: if then abandon described first response message; Otherwise, send described second request message.
The present invention also provides a kind of MEP server apparatus, comprising:
First receiving element, be used for from what a VLAN received that the MEP client device sends carrying other first request message of the first maintenance field level, a described VLAN and the first maintenance field rank are respectively the pairing VLAN of MEP and the maintenance field ranks of described MEP client device desire configuration;
The configuration determining unit, be used for determining second Service Instance corresponding to described first a maintenance field rank and a VLAN of this MEP server apparatus configuration, and the still untapped MEP sign of selecting is distributed to described MEP client device from the MEP tabulation of second Service Instance;
Second transmitting element is used for sending second response message that carries the MEP configuration parameter to described MEP client device, and described MEP configuration parameter includes described MEP sign.
Preferably, in the above-mentioned MEP server apparatus, described MEP configuration parameter also includes the maintenance field of the described second Service Instance correspondence and safeguards the communication with detection time interval of the title of collection, the described second Service Instance correspondence and the MEP tabulation of described second Service Instance.
Preferably, in the above-mentioned MEP server apparatus, also comprise:
First transmitting element is used for after receiving described first request message, sends first response message that carries described MEP configuration parameter to described MEP client device;
Second receiving element is used to receive second request message that carries described MEP configuration parameter that described MEP client device sends, and after receiving described second request message, triggers described first transmitting element and send described second response message.
From the above as can be seen, the method and apparatus of configuration MEP provided by the invention, the MEP client can be from trend MEP server requests MEP configuration parameter, and carry out the configuration of MEP automatically according to the MEP configuration parameter that obtains, utilize the equipment automatization configuration to substitute the part manual configuration, thereby can significantly reduce the workload of manual configuration, raising is configured to power.Among the present invention, after the MEP client is received the MEP configuration parameter of MEP server transmission, judge further also whether maintenance field rank and the MEP tabulation in the MEP configuration parameter be available, improved the fail safe of MEP configuration.And the present invention also by mutual four messages, confirms the connection of two-way link between the MEP client and server, has guaranteed the reliability of MEP configuration.
Description of drawings
Fig. 1 is the schematic diagram of the maintenance field of prior art;
Fig. 2 is the schematic flow sheet of the method for the described configuration of embodiment of the invention MEP;
Fig. 3 is the schematic flow sheet of the method for the described configuration of another embodiment of the present invention MEP;
Fig. 4 is the structural representation of the described MEP client device of the embodiment of the invention;
Fig. 5 is the structural representation of the described MEP server apparatus of the embodiment of the invention.
Embodiment
The invention provides the method for a kind of MEP of configuration, in MEP configuration, introduce client/server mechanism: complete MEP of configuration on an equipment at first, and to dispose this MEP be the MEP server; Then, other need be configured to same maintenance field and safeguard the equipment of concentrating, under the prerequisite that configuration phase guarantees and the MEP server is communicated with, as long as the maintenance field rank (Level) that needs configuration is set on this equipment and safeguards the VLAN (being pairing maintenance field rank of predetermined MEP and VLAN) that collection is served, obtain remaining MEP configuration parameter by Level and these two fields of VLAN to the MEP server, and be configured automatically according to the MEP configuration parameter that is obtained, thereby greatly reduced the manual configuration workload, reduce the mistake that manual configuration may cause, improved allocative efficiency.Below with reference to accompanying drawing, the present invention is described further by specific embodiment.
＜embodiment 1 〉
In the present embodiment, the user needs in advance according to the network planning, determine to need to use all devices that CFM mechanism is carried out detection of connectivity, and then mark off corresponding maintenance field, and determine that maintenance field rank (Level), the maintenance collection in this maintenance field and this maintenance of this maintenance field collect the information such as VLAN of being served.Then, selecting an equipment (below be assumed to be second equipment) from above-mentioned all devices, is the MEP server with this equipment disposition, as the equipment of MEP server, can the special packet that the MEP client is sent be responded.Then, according to the complete MEP configuration flow of prior art, the MEP on the configuration MEP server.Miscellaneous equipment except that the MEP server all is configured to the MEP client, and the MEP client can send special packet, issues corresponding M EP configuration parameter in order to request MEP server, and disposes automatically according to this MEP configuration parameter.
Be example with first equipment below, illustrate how the MEP client disposes MEP.Please refer to Fig. 2, the method for the described configuration of present embodiment MEP comprises:
Here, first equipment is configured to the MEP client, and a VLAN of first port, a MEP correspondence, the first maintenance field rank and first direction all are pre-determined according to the network planning.The user can be to a VLAN, first maintenance field rank and the first direction information of first equipment input at first port, it is MEP that expression is wished first port arrangement, and wishes that the maintenance field rank of the first port correspondence and VLAN are respectively above-mentioned first a maintenance field rank and a VLAN; First equipment generates described first request message according to user's input information and multicast transmission in a VLAN, carries the information of a VLAN in the VLANID field in the ethernet header of described first request message.
Here, when the first direction of a described MEP correspondence was extroversion, described first request message was directly to send to a described VLAN multicast from described first port; The first direction of a described MEP correspondence be interior to the time, described first request message is other port except first port in the VLAN from first equipment, sends to a described VLAN multicast.
Step 22, be configured to second equipment of MEP server, after from a VLAN, receiving described first request message, extract the first maintenance field rank of carrying in described first request message, and judge local whether disposing and described first maintenance field rank and the corresponding Service Instance of a VLAN: if then enter step 24; Otherwise, enter step 23.
Here, second equipment can be provided with the MEP tabulation of second Service Instance as the MEP pond, comprising learning the MEP sign for far-end MEP, the MEP sign that has dispensed and having identified and still untapped MEP sign at the MEP of this locality configuration.Have only still untapped MEP sign to distribute to the MEP client as available resources.In the above-mentioned steps 24, after selecting MEP sign and distributing to first equipment, second equipment need be from the MEP tabulation of second Service Instance deletion the one MEP sign in the still untapped MEP sign.
Above-mentioned first, second response message all is the message of making an appointment, and for example can be that command code (OpCode) field is the CFM protocol massages of predetermined value.
In the above-mentioned flow process, first equipment can send described first request message according to particular time interval before not receiving second response message that the MEP server sends, and the concrete time interval can set up on their own as required; Certainly, the transmission number of times of first request message can also be set, after reaching predetermined transmission number of times, stop to send first request message.If in the scheduled time after for the first time sending described first request message, first equipment is not all received second response message, then can report relevant information to the upper strata, in order to indicating automatic configuration failure, and process ends.
By above-mentioned flow process, the MEP client can obtain the MEP sign of MEP server-assignment, and can guarantee that the MEP sign between each MEP client does not repeat mutually, improves the allocative efficiency of MEP sign.
Except the MEP sign, the MEP configuration also comprises other configuration item, for this reason, in above-mentioned steps 23, second equipment can also be included in the maintenance field of the described second Service Instance correspondence and the title of maintenance collection, the communication with detection time interval of the described second Service Instance correspondence and the MEP tabulation of described second Service Instance in the described MEP configuration parameter, sends to first equipment by described second response message; In above-mentioned steps 25, first equipment can get access to relevant configured parameter from described MEP configuration parameter, and then first port is done further configuration, specifically comprises:
On described first equipment, create first maintenance field, and in described first maintenance field, create first and safeguard collection, and described first maintenance field and first is set safeguards that the title of collection is respectively the maintenance field of the described second Service Instance correspondence and safeguards the title of collection;
On described first equipment, create first Service Instance of safeguarding collection corresponding to described first maintenance field and first, MEP tabulation with described second Service Instance, be set to the MEP tabulation of described first Service Instance, and, with the communication with detection time interval of the described second Service Instance correspondence, be set to the communication with detection time interval of the described first Service Instance correspondence;
The Service Instance that disposes a described MEP correspondence is described first Service Instance.
Here, the ID of first Service Instance can be set up on their own by first equipment, does not need to obtain from the MEP configuration parameter, and for example, first equipment can be with directly selecting the still original Service Instance ID in this locality to get final product.
Only by two mutual messages between MEP client and the MEP server, realized the automatic configuration of MEP in the present embodiment.As can be seen, in the whole layoutprocedure, the MEP client only need receive the information such as maintenance field rank, VLAN and direction of the predetermined MEP correspondence of user input, then the MEP client just can be voluntarily by with the MEP server alternately, finish all configuration efforts.This shows that present embodiment can reduce the workload of MEP configuration greatly, improve the automaticity of configuration, thereby improved allocative efficiency, and reduced the possibility that configuration error takes place.
＜embodiment 2 〉
By four mutual messages between MEP client and the MEP server, realize the relevant configuration of MEP in the present embodiment.Adopt more mutual message, can improve the reliability of MEP configuration
Similar with the foregoing description 1, be the MEP client also in the present embodiment with first equipment, second equipment is that example describes for the MEP server.Please refer to Fig. 3, the method for the described configuration of present embodiment MEP may further comprise the steps:
Here, second request message can send repeatedly according to particular time interval.When the first direction of a described MEP correspondence was extroversion, described first request message was directly to send to a described VLAN multicast from described first port; The first direction of a described MEP correspondence be interior to the time, described first request message is other port except first port in the VLAN from first equipment, sends to a described VLAN multicast.
Because on same equipment, a maintenance field can only be corresponding to a maintenance field rank, whether the maintenance field rank that therefore needs here to judge local configuration equates with the first maintenance field rank.
Here, second request message also can send repeatedly according to particular time interval.When the first direction of a described MEP correspondence was extroversion, described second request message was directly to send to a described VLAN multicast from described first port; The first direction of a described MEP correspondence be interior to the time, described second request message is other port except first port in the VLAN from first equipment, sends to a described VLAN multicast.
In the above-mentioned steps 323, described first port of first equipment disposition specifically comprises:
Disposing described first port is a MEP, and disposes the described MEP of being designated of described MEP sign, and the direction that disposes a described MEP is described first direction;
Create first maintenance field, and in described first maintenance field, create first and safeguard collection, and described first maintenance field and first is set safeguards that the title of collection is respectively the maintenance field of the described second Service Instance correspondence and safeguards the title of collection;
First Service Instance of collection is safeguarded in establishment corresponding to described first maintenance field and first, MEP tabulation with described second Service Instance, be set to the MEP tabulation of described first Service Instance, and, with the communication with detection time interval of the described second Service Instance correspondence, be set to the communication with detection time interval of the described first Service Instance correspondence;
The Service Instance that disposes a described MEP correspondence is described first Service Instance.
Certainly, if the local maintenance field that has disposed the described second Service Instance correspondence can be skipped the step of creating first maintenance field, directly in first maintenance field, create first and safeguard collection.
In the above-mentioned flow process of present embodiment, the MEP client does not directly dispose MEP after receiving first response message, but judge whether the MEP configuration parameter that the MEP server issues meets s own situation, only when meeting s own situation, just send second request message, and after receiving second response message, just carry out the MEP configuration, this processing mode can improve the reliability of MEP configuration.And, the MEP server is after receiving second request message that the MEP client sends, just with the deletion from still untapped MEP identifies of MEP sign, rather than when sending first response message, just MEP sign is deleted, do the waste that to avoid the available MEP identifying resource of MEP server like this, because if the MEP server is obstructed to the one way link of MEP client, the MEP client can not receive MEP sign, also just can't use MEP sign, if delete from available resources and when sending first response message, just a MEP is identified, will cause the waste of the available MEP identifying resource of MEP server.
By above-mentioned flow process, first equipment is MEP self having disposed first port.After this, first equipment and second equipment are set up detection of connectivity (CC) neighborhood each other by the CCM message interaction process and the MEP configuration aging mechanism of prior art, and start MEP configuration ageing timer respectively.First equipment is after the MEP configuration ageing timer of self is overtime, with the CC neighborhood of deletion with the foundation of second equipment, also cancel the MEP configuration (deleting the MPE sign and the direction of first port) of first port simultaneously, and delete described first Service Instance; Second equipment is after the MEP configuration ageing timer of self is overtime, also will delete with the CC neighborhood between first equipment, and will be the described MEP sign of first devices allocation, add to again in the still untapped MEP sign in the MEP tabulation of described second Service Instance.
Employed first, second request message and first, second response message all are the messages of making an appointment in the present embodiment, for example can be that command code (OpCode) field is the CFM protocol massages of predetermined value.Below be example with the CFM protocol massages, the message format that present embodiment can adopt is described.Need to prove that following message format is in order to help to understand present embodiment, but not limitation of the invention.
The CFM protocol massages of the newly-increased 4 kinds of similar CCM of present embodiment, its concrete message format is as shown in table 1 below:
Table 1
The below concrete definition of each field in the above-mentioned message of explanation:
1) Level field: preceding 3 bit of the 1st byte are Level, indicate the rank of maintenance field.For example, the first maintenance field rank of carrying in above-mentioned first request message is carried in this field exactly.
2) Version field: back 5 bit of the 1st byte are Version, and present embodiment is value 0 all.
3) OpCode field: be in the 2nd byte, indicate the action type of this message.For example, can define OpCode=11 and represent that this message is the first above-mentioned request message, OpCode=12 represents that this message is the first above-mentioned response message, and OpCode=13 represents that this message is the second above-mentioned request message, and it is the second above-mentioned response message that OpCode=14 shows this message.
4) RDI field: the 1st bit of the 3rd byte is RDI, and the FNG state machine is 1 when being NOCCM, and remaining situation is 0.For 4 kinds of messages of present embodiment, this field all is set to 0.
5) Reserved field: the 2nd to the 5th bit of the 3rd byte is reserved field, value 0.
6) CCI field: back 3 bit of the 3rd byte are the communication with detection time interval (CCI) fields.The MEP client device is not before MEP ID applies for, this field is set to 0 in first, second request message of its transmission; The MEP server apparatus then in first, second response message this field be set to the CCI of the described second Service Instance correspondence.
7) First TLV offset field: the 1st TLV field occupies the 4th byte apart from the deviant after this field.
8) SeqNum field: the 5th to the 8th byte, the sequence number of selecting when being MEP client device initiation request is used for identifying once request.
9) MEPID field: the 9th to the 10th byte is the MEPID field, is used to represent the sign (ID) of maintaining end point.The MEP client device is not before MEP ID applies for, this field is set to 0 in first, second request message of its transmission.
10) MAID field: the 11st to the 58th byte is the MAID field, mainly comprises Format and the Length (each 1 byte, totally 4 bytes) of MD and MA, and MD and MA title (both add up and are no more than 44 bytes, and insufficient section is filled with 0).The MEP client device is not before MEP ID applies for, this field is set to 0 in first, second request message of its transmission.
11) field Y.1731: the 59th to the 70th byte is field Y.1731, and this field is a reserved field at present, leaves for Y.1731 and uses, and is filled to 0 in the present embodiment.
12) the TLVs field mainly is made up of 3 TLV fields: Distribute MEP-ID TLV field, Distribute MEPList TLV field and End TLV field.
Wherein, Distribute MEP-ID TLV field is as shown in table 2 below:
Table 2
Wherein: 1) TLV the type field: 1 byte length, value is 1, represents that this field is a DistributeMEP-ID TLV field.
2) TLV Length field: 2 byte lengths, its value is fixed as 2, the length of the DistributeMEP-ID Value field of expression back.
3) Distribute MEP-ID Value field: 2 byte lengths, expression MEP server apparatus are distributed to the MEP ID (being above-mentioned MEP sign) of MEP client device.
Distribute MEPList TLV field is as shown in table 3 below:
Table 3
Wherein: 1) TLV the type field: 1 byte length, value is 2, represents that this field is a DistributeMEPList TLV field.
2) TLV Length field: 2 byte lengths, its value is fixed as 101, the length of the DistributeMEPList Value field of expression back.
3) Distribute MEP-ID Value field: 101 byte lengths, expression MEP server apparatus are distributed to the MEPList (being the MEP tabulation of above-mentioned second Service Instance) of MEP client device.
End TLV field has only a byte, value 0, and expression TLV field finishes, and also represents whole ENMES.
＜embodiment 3 〉
The method of the configuration MEP that provides based on above two embodiment, present embodiment provides a kind of MEP client device and MPE server apparatus.
Wherein, as shown in Figure 4, the MEP client 40 that present embodiment provides comprises:
First transmitting element, be used for when needs dispose this equipment first port and are a MEP, according to a VLAN, the first maintenance field rank and the first direction of a predetermined MEP correspondence, multicast sends and carries described other first request message of the first maintenance field level in a VLAN;
Second receiving element, be used to receive second response message that carries the MEP configuration parameter that the MEP server apparatus returns, described MEP configuration parameter includes MEP sign, described MEP sign is that described MEP server apparatus is after receiving first request message from a described VLAN, the still untapped MEP sign of from the MEP tabulation of second Service Instance, selecting, described second Service Instance is the Service Instance corresponding to described first a maintenance field rank and a VLAN that disposes on the described MEP server apparatus;
Dispensing unit is used for obtaining described MEP configuration parameter from described second response message, and disposes described first port according to described MEP configuration parameter.Here, described dispensing unit, also being used to dispose described first port is a MEP, and disposes the described MEP of being designated of described MEP sign, and the direction that disposes a described MEP is described first direction.
Preferably, described MEP configuration parameter also includes the maintenance field of the described second Service Instance correspondence and safeguards the communication with detection time interval of the title of collection, the described second Service Instance correspondence and the MEP tabulation of described second Service Instance.At this moment, described dispensing unit, also be used to create first maintenance field, and in described first maintenance field, create first and safeguard collection, and described first maintenance field and first is set safeguards that the title of collection is respectively the maintenance field of the described second Service Instance correspondence and safeguards the title of collection; First Service Instance of collection is safeguarded in establishment corresponding to described first maintenance field and first, MEP tabulation with described second Service Instance, be set to the MEP tabulation of described first Service Instance, and, be set to the communication with detection time interval of the described first Service Instance correspondence with communication with detection time interval of the described second Service Instance correspondence; The Service Instance that disposes a described MEP correspondence is described first Service Instance.
Corresponding to the foregoing description 2 described methods, the described MEP client device of present embodiment can also comprise:
First receiving element is used to receive first response message that carries described MEP configuration parameter that described MEP server apparatus returns, and obtains described MEP configuration parameter from described first response message, and triggers second transmitting element;
Second transmitting element is used for sending second request message that carries described MEP configuration parameter at a described VLAN multicast;
Wherein, described second response message be described MEP server apparatus after receiving described second request message, after judging the described MEP sign that comprises in described second request message and not being used yet, just send to this MEP client device.
Preferably, described first receiving element also is used for extracting the title of maintenance field of the described second Service Instance correspondence of described MEP configuration parameter, and judges the local maintenance field that whether disposes the described second Service Instance correspondence:
If judge then whether the rank of the maintenance field of the local described second Service Instance correspondence that disposes equals the described first maintenance field rank: if then trigger described second transmitting element; Otherwise, abandon described first response message;
Otherwise, trigger described second transmitting element.
Preferably, described second transmitting element, also be used for extracting the MEP tabulation of described second Service Instance of described MEP configuration parameter, and whether the MEP sign total number during the MEP that judges described second Service Instance tabulates and the MEP of this MEP client device tabulates exceeds predetermined thresholding: if then abandon described first response message; Otherwise, send described second request message.
As shown in Figure 5, the MEP server apparatus that present embodiment provides comprises:
First receiving element, be used for from what a VLAN received that the MEP client device sends carrying other first request message of the first maintenance field level, a described VLAN and the first maintenance field rank are respectively the pairing VLAN of MEP and the maintenance field ranks of described MEP client device desire configuration;
The configuration determining unit, be used for determining second Service Instance corresponding to described first a maintenance field rank and a VLAN of this equipment disposition, and the still untapped MEP sign of selecting is distributed to described MEP client device from the MEP tabulation of second Service Instance;
Second transmitting element is used for sending second response message that carries the MEP configuration parameter to described MEP client device, and described MEP configuration parameter includes described MEP sign.
Preferably, above-mentioned MEP configuration parameter also includes the maintenance field of the described second Service Instance correspondence and safeguards the communication with detection time interval of the title of collection, the described second Service Instance correspondence and the MEP tabulation of described second Service Instance.
Corresponding to the foregoing description 2 described methods, the described MEP server apparatus of present embodiment can also comprise:
First transmitting element is used for after receiving described first request message, sends first response message that carries described MEP configuration parameter to described MEP client device;
Second receiving element is used to receive second request message that carries described MEP configuration parameter that described MEP client device sends, and after receiving described second request message, triggers described first transmitting element and send described second response message.In sum, method and the equipment thereof of the configuration MEP that present embodiment provides can significantly reduce the workload of manual configuration, improve allocative efficiency and guarantee to be configured to power.
The above only is embodiments of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.
Claims (16)
1. the method for a configuring maintenance end points MEP is characterized in that, comprising:
Steps A, when the MEP client device is a MEP at needs configuration self first port, according to a VLAN, the first maintenance field rank and the first direction of a predetermined MEP correspondence, multicast sends and carries described other first request message of the first maintenance field level in a VLAN;
Step B, described MEP client device receives second response message that carries the MEP configuration parameter that the MEP server apparatus returns, described MEP configuration parameter includes MEP sign, described MEP sign is that described MEP server apparatus is after receiving first request message from a described VLAN, the still untapped MEP sign of from the MEP tabulation of second Service Instance, selecting, described second Service Instance is the Service Instance corresponding to described first a maintenance field rank and a VLAN that disposes on the described MEP server apparatus;
Step C, described MEP client device obtain described MEP configuration parameter from described second response message, and dispose described first port according to described MEP configuration parameter.
2. the method for claim 1, it is characterized in that, among the described step C, describedly dispose described MEP client device according to described MEP configuration parameter and comprise: disposing described first port is a MEP, and dispose the described MEP of being designated of described MEP sign, and the direction that disposes a described MEP is described first direction.
3. method as claimed in claim 2, it is characterized in that described MEP configuration parameter also includes the maintenance field of the described second Service Instance correspondence and safeguards the communication with detection time interval of the title of collection, the described second Service Instance correspondence and the MEP tabulation of described second Service Instance;
Among the described step C, describedly dispose described first port according to described MEP configuration parameter and also comprise:
On described MEP client device, create first maintenance field, and in described first maintenance field, create first and safeguard collection, and described first maintenance field and first is set safeguards that the title of collection is respectively the maintenance field of the described second Service Instance correspondence and safeguards the title of collection;
On described MEP client device, create first Service Instance of safeguarding collection corresponding to described first maintenance field and first, MEP tabulation with described second Service Instance, be set to the MEP tabulation of described first Service Instance, and, with the communication with detection time interval of the described second Service Instance correspondence, be set to the communication with detection time interval of the described first Service Instance correspondence;
The Service Instance that disposes a described MEP correspondence is described first Service Instance.
4. as each described method of claim 1 to 3, it is characterized in that,
Also comprise between described steps A and the step B:
Described MEP client device receives first response message that carries described MEP configuration parameter that described MEP server apparatus returns, from described first response message, obtain described MEP configuration parameter, and multicast sends second request message that carries described MEP configuration parameter in a described VLAN;
Described MEP server apparatus is after receiving described second request message, extract the described MEP sign that comprises in described second request message, and judge whether described MEP sign is not used yet: if, then from the MEP tabulation of described second Service Instance, delete described MEP sign in the still untapped MEP sign, and send described second response message to described MEP client device; Otherwise, process ends.
5. method as claimed in claim 4 is characterized in that, obtain described MEP configuration parameter from described first response message after, described method also comprises:
Described MEP client device extracts the title of the maintenance field of the described second Service Instance correspondence in the described MEP configuration parameter, and judges the local maintenance field that whether disposes the described second Service Instance correspondence:
If judge then whether the rank of the maintenance field of the local described second Service Instance correspondence that disposes equals the described first maintenance field rank: if then multicast sends described second request message in a described VLAN; Otherwise, abandon described first response message and process ends;
Otherwise multicast sends described second request message in a described VLAN.
6. method as claimed in claim 5 is characterized in that, before sending described second request message, described method also comprises:
Described MEP client device extracts the MEP tabulation of described second Service Instance in the described MEP configuration parameter, and whether the MEP sign total number during the MEP that judges described second Service Instance tabulates and the MEP of described MEP client device tabulates exceeds predetermined thresholding: if then abandon described first response message and process ends; Otherwise, send described second request message.
7. method as claimed in claim 4 is characterized in that,
After described step C, by mutual continuity detection messages, set up detection of connectivity neighborhood each other between described MEP client device and the MEP server apparatus, and start MEP configuration ageing timer respectively;
Described MEP client device is after described MEP configuration ageing timer is overtime, and the detection of connectivity neighborhood between deletion and the described MEP server apparatus is cancelled the MEP configuration of first port, and deleted described first Service Instance;
Described MEP server apparatus is after described MEP configuration ageing timer is overtime, detection of connectivity neighborhood between deletion and the described MEP server apparatus, and described MEP sign is added to again during still untapped MEP in the MEP tabulation of described second Service Instance identifies.
8. a MEP client device is characterized in that, comprising:
First transmitting element, be used for when needs dispose this MEP client device first port and are a MEP, according to a VLAN, the first maintenance field rank and the first direction of a predetermined MEP correspondence, multicast sends and carries described other first request message of the first maintenance field level in a VLAN;
Second receiving element, be used to receive second response message that carries the MEP configuration parameter that the MEP server apparatus returns, described MEP configuration parameter includes MEP sign, described MEP sign is that described MEP server apparatus is after receiving first request message from a described VLAN, the still untapped MEP sign of from the MEP tabulation of second Service Instance, selecting, described second Service Instance is the Service Instance corresponding to described first a maintenance field rank and a VLAN that disposes on the described MEP server apparatus;
Dispensing unit is used for obtaining described MEP configuration parameter from described second response message, and disposes described first port according to described MEP configuration parameter.
9. MEP client device as claimed in claim 8 is characterized in that,
Described dispensing unit, also being used to dispose described first port is a MEP, and disposes the described MEP of being designated of described MEP sign, and the direction that disposes a described MEP is described first direction.
10. MEP client device as claimed in claim 9, it is characterized in that described MEP configuration parameter also includes the maintenance field of the described second Service Instance correspondence and safeguards the communication with detection time interval of the title of collection, the described second Service Instance correspondence and the MEP tabulation of described second Service Instance;
Described dispensing unit also is used for:
Create first maintenance field, and in described first maintenance field, create first and safeguard collection, and described first maintenance field and first is set safeguards that the title of collection is respectively the maintenance field of the described second Service Instance correspondence and safeguards the title of collection;
First Service Instance of collection is safeguarded in establishment corresponding to described first maintenance field and first, MEP tabulation with described second Service Instance, be set to the MEP tabulation of described first Service Instance, and, with the communication with detection time interval of the described second Service Instance correspondence, be set to the communication with detection time interval of the described first Service Instance correspondence;
The Service Instance that disposes a described MEP correspondence is described first Service Instance.
11. as each described MEP client device of claim 8 to 10, it is characterized in that, also comprise:
First receiving element is used to receive first response message that carries described MEP configuration parameter that described MEP server apparatus returns, and obtains described MEP configuration parameter from described first response message, and triggers second transmitting element;
Second transmitting element is used for sending second request message that carries described MEP configuration parameter at a described VLAN multicast;
Wherein, described second response message be described MEP server apparatus after receiving described second request message, after judging the described MEP sign that comprises in described second request message and not being used yet, just send to this MEP client device.
12. MEP client device as claimed in claim 11 is characterized in that,
Described first receiving element also is used for extracting the title of maintenance field of the described second Service Instance correspondence of described MEP configuration parameter, and judges the local maintenance field that whether disposes the described second Service Instance correspondence:
If judge then whether the rank of the maintenance field of the local described second Service Instance correspondence that disposes equals the described first maintenance field rank: if then trigger described second transmitting element; Otherwise, abandon described first response message;
Otherwise, trigger described second transmitting element.
13. MEP client device as claimed in claim 12 is characterized in that,
Described second transmitting element, also be used for extracting the MEP tabulation of described second Service Instance of described MEP configuration parameter, and whether the MEP sign total number during the MEP that judges described second Service Instance tabulates and the MEP of this MEP client device tabulates exceeds predetermined thresholding: if then abandon described first response message; Otherwise, send described second request message.
14. a MEP server apparatus is characterized in that, comprising:
First receiving element, be used for from what a VLAN received that the MEP client device sends carrying other first request message of the first maintenance field level, a described VLAN and the first maintenance field rank are respectively the pairing VLAN of MEP and the maintenance field ranks of described MEP client device desire configuration;
The configuration determining unit, be used for determining second Service Instance corresponding to described first a maintenance field rank and a VLAN of this MEP server apparatus configuration, and the still untapped MEP sign of selecting is distributed to described MEP client device from the MEP tabulation of second Service Instance;
Second transmitting element is used for sending second response message that carries the MEP configuration parameter to described MEP client device, and described MEP configuration parameter includes described MEP sign.
15. MEP server apparatus as claimed in claim 14, it is characterized in that described MEP configuration parameter also includes the maintenance field of the described second Service Instance correspondence and safeguards the communication with detection time interval of the title of collection, the described second Service Instance correspondence and the MEP tabulation of described second Service Instance.
16. MEP server apparatus as claimed in claim 15 is characterized in that, also comprises:
First transmitting element is used for after receiving described first request message, sends first response message that carries described MEP configuration parameter to described MEP client device;
Second receiving element is used to receive second request message that carries described MEP configuration parameter that described MEP client device sends, and after receiving described second request message, triggers described first transmitting element and send described second response message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100930353A CN101662383B (en) | 2009-09-17 | 2009-09-17 | Method and equipment for configuring maintenance end points |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100930353A CN101662383B (en) | 2009-09-17 | 2009-09-17 | Method and equipment for configuring maintenance end points |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101662383A true CN101662383A (en) | 2010-03-03 |
| CN101662383B CN101662383B (en) | 2011-09-07 |
Family
ID=41790189
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009100930353A Expired - Fee Related CN101662383B (en) | 2009-09-17 | 2009-09-17 | Method and equipment for configuring maintenance end points |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101662383B (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102984011A (en) * | 2012-12-04 | 2013-03-20 | 杭州华三通信技术有限公司 | Link failure positioning method and equipment |
| CN103036793A (en) * | 2012-12-17 | 2013-04-10 | 杭州华三通信技术有限公司 | Delivery method of connectivity fault detection protocol messages and forwarding equipment |
| CN103152202A (en) * | 2013-03-13 | 2013-06-12 | 华为技术有限公司 | Parameter deployment method, communication node and communication network |
| CN103365846A (en) * | 2012-03-26 | 2013-10-23 | 百度在线网络技术（北京）有限公司 | Method, system and server for processing compressed files in network disk |
| WO2014201613A1 (en) * | 2013-06-17 | 2014-12-24 | 华为技术有限公司 | Mep configuration method and network device |
| WO2015070427A1 (en) * | 2013-11-15 | 2015-05-21 | 华为技术有限公司 | Method, device, and system for configuring maintenance association (ma) |
| CN104660469A (en) * | 2015-02-15 | 2015-05-27 | 华为技术有限公司 | Layer-2 network connectivity detecting method and associated equipment |
| CN103731322B (en) * | 2014-01-16 | 2017-02-15 | 杭州华三通信技术有限公司 | Method and device for detecting self-adapting link among devices with different capabilities |
| CN106559420A (en) * | 2016-11-07 | 2017-04-05 | 杭州迪普科技股份有限公司 | A kind of filter method and device of message |
| WO2018014742A1 (en) * | 2016-07-21 | 2018-01-25 | 中兴通讯股份有限公司 | Method and apparatus for configuring port of port extender |
| CN108011755A (en) * | 2017-11-29 | 2018-05-08 | 瑞斯康达科技发展股份有限公司 | A kind of method and device of NE management |
| WO2021120708A1 (en) * | 2019-12-19 | 2021-06-24 | 盛科网络（苏州）有限公司 | Message processing method and device, storage medium, and electronic device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100492987C (en) * | 2004-07-08 | 2009-05-27 | 阿尔卡特公司 | Domain configuration in an Ethernet oam network having multiple levels |
| CN101521603B (en) * | 2008-12-26 | 2011-10-26 | 中兴通讯股份有限公司 | Method and system for quickly detecting connectivity of link |
-
2009
- 2009-09-17 CN CN2009100930353A patent/CN101662383B/en not_active Expired - Fee Related
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103365846A (en) * | 2012-03-26 | 2013-10-23 | 百度在线网络技术（北京）有限公司 | Method, system and server for processing compressed files in network disk |
| CN102984011B (en) * | 2012-12-04 | 2015-05-13 | 杭州华三通信技术有限公司 | Link failure positioning method and equipment |
| CN102984011A (en) * | 2012-12-04 | 2013-03-20 | 杭州华三通信技术有限公司 | Link failure positioning method and equipment |
| CN103036793A (en) * | 2012-12-17 | 2013-04-10 | 杭州华三通信技术有限公司 | Delivery method of connectivity fault detection protocol messages and forwarding equipment |
| CN103036793B (en) * | 2012-12-17 | 2015-09-16 | 杭州华三通信技术有限公司 | Be communicated with sending method and the forwarding unit of error detection protocol message |
| CN103152202B (en) * | 2013-03-13 | 2016-03-30 | 华为技术有限公司 | Parameter deployment, communication node and communication network |
| CN103152202A (en) * | 2013-03-13 | 2013-06-12 | 华为技术有限公司 | Parameter deployment method, communication node and communication network |
| WO2014201613A1 (en) * | 2013-06-17 | 2014-12-24 | 华为技术有限公司 | Mep configuration method and network device |
| CN104471897A (en) * | 2013-06-17 | 2015-03-25 | 华为技术有限公司 | Mep configuration method and network device |
| US9985862B2 (en) | 2013-06-17 | 2018-05-29 | Huawei Technologies Co., Ltd. | MEP configuration method and network device |
| CN104471897B (en) * | 2013-06-17 | 2018-02-06 | 华为技术有限公司 | A kind of MEP collocation methods and the network equipment |
| CN105009512A (en) * | 2013-11-15 | 2015-10-28 | 华为技术有限公司 | Method, device, and system for configuring maintenance association (MA) |
| US9813159B2 (en) | 2013-11-15 | 2017-11-07 | Huawei Technologies Co., Ltd. | Method for setting maintenance association MA, apparatus, and system |
| WO2015070427A1 (en) * | 2013-11-15 | 2015-05-21 | 华为技术有限公司 | Method, device, and system for configuring maintenance association (ma) |
| CN105009512B (en) * | 2013-11-15 | 2018-09-07 | 华为技术有限公司 | Maintenance association MA setting methods, apparatus and system |
| CN103731322B (en) * | 2014-01-16 | 2017-02-15 | 杭州华三通信技术有限公司 | Method and device for detecting self-adapting link among devices with different capabilities |
| CN104660469A (en) * | 2015-02-15 | 2015-05-27 | 华为技术有限公司 | Layer-2 network connectivity detecting method and associated equipment |
| CN104660469B (en) * | 2015-02-15 | 2018-11-16 | 华为技术有限公司 | A kind of method for detecting connectivity and relevant device of double layer network |
| WO2018014742A1 (en) * | 2016-07-21 | 2018-01-25 | 中兴通讯股份有限公司 | Method and apparatus for configuring port of port extender |
| CN106559420A (en) * | 2016-11-07 | 2017-04-05 | 杭州迪普科技股份有限公司 | A kind of filter method and device of message |
| CN108011755A (en) * | 2017-11-29 | 2018-05-08 | 瑞斯康达科技发展股份有限公司 | A kind of method and device of NE management |
| CN108011755B (en) * | 2017-11-29 | 2021-02-26 | 瑞斯康达科技发展股份有限公司 | Network element management method and device |
| WO2021120708A1 (en) * | 2019-12-19 | 2021-06-24 | 盛科网络（苏州）有限公司 | Message processing method and device, storage medium, and electronic device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101662383B (en) | 2011-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101662383B (en) | Method and equipment for configuring maintenance end points | |
| CN101282237B (en) | Synthetic network management system based on SNMP | |
| TWI324456B (en) | An intelligent automatic setting restoration method and device | |
| CN101277299B (en) | Protocol conversion system and protocol conversion process | |
| CN104281511B (en) | Intelligent-platform management interface system, baseboard management controller and implementation method | |
| US9071508B2 (en) | Distributed fabric management protocol | |
| CN102123181A (en) | Method for automatically configuring IP address to network device | |
| CN102739495A (en) | Network system, machine allocation device and machine allocation method | |
| CN104184616A (en) | Intelligent management system for local area network resources | |
| CN103249075B (en) | Access point (AP) fault detecting and recovering method and device | |
| CN103312836A (en) | Large local network internet protocol (IP) address administration method | |
| CN101789980A (en) | Batch upgrading method based on cluster network | |
| CN101951325A (en) | Network terminal configuration system based on automatic discovery and configuration method thereof | |
| WO2012106883A1 (en) | Method, apparatus and system for initial deployment of layer 2 network device | |
| CN104618147A (en) | Longitudinally stacked system management method and system | |
| CN101826995A (en) | Method and system for managing home network equipment | |
| CN101599865A (en) | A kind of management method of the cluster network based on unique public network IP address | |
| CN107835222A (en) | Combustion gas data transmission method and Internet of things system based on compound Internet of Things | |
| CN107592360A (en) | A kind of Internet of Things data polymerization and system based on mixed cloud | |
| CN101888379B (en) | Multi-proxy server dynamic linking method of network television and network television system | |
| CN106506409A (en) | A kind of management method of network management exchange and network management exchange | |
| CN106533775A (en) | Virtual member equipment and neighbor discovery method | |
| CN107659636A (en) | Thermal data transmission method and Internet of things system based on compound Internet of Things | |
| CN101854256A (en) | Method and system for implementing locking indication | |
| CN106875660B (en) | Method and collector for the communication of meter equipment |
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 | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |
|
| CP03 | Change of name, title or address | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110907 Termination date: 20200917 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |