EP2840738B1 - Procédé de configuration mep et dispositif de réseau - Google Patents

Procédé de configuration mep et dispositif de réseau Download PDF

Info

Publication number
EP2840738B1
EP2840738B1 EP13883350.4A EP13883350A EP2840738B1 EP 2840738 B1 EP2840738 B1 EP 2840738B1 EP 13883350 A EP13883350 A EP 13883350A EP 2840738 B1 EP2840738 B1 EP 2840738B1
Authority
EP
European Patent Office
Prior art keywords
information
mep
port
peer device
configuration
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.)
Active
Application number
EP13883350.4A
Other languages
German (de)
English (en)
Other versions
EP2840738A4 (fr
EP2840738A1 (fr
Inventor
Kun Hu
Rui Chen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP2840738A1 publication Critical patent/EP2840738A1/fr
Publication of EP2840738A4 publication Critical patent/EP2840738A4/fr
Application granted granted Critical
Publication of EP2840738B1 publication Critical patent/EP2840738B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/407—Bus networks with decentralised control
    • H04L12/413—Bus networks with decentralised control with random access, e.g. carrier-sense multiple-access with collision detection (CSMA-CD)
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H04L43/103—Active monitoring, e.g. heartbeat, ping or trace-route with adaptive polling, i.e. dynamically adapting the polling rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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
    • 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/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • 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/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H04L41/0869—Validating the configuration within one network element
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity

Definitions

  • the present invention relates to the communications field, and in particular, to an MEP configuration method and a network device.
  • Ethernet Ethernet
  • SNMP Simple Network Management Protocol
  • IP Internet Protocol
  • US 2010/0188983A1 refers to a method and related network node including one or more of the following: configuring a maintenance domain on a first network node; configuring a maintenance association within the maintenance domain on a first network node; configuring, within the maintenance association, a local maintenance endpoint (MEP) on the first network node; and establishing a plurality of point-to-point connections within the maintenance association, each point-to-point connection established between the local MEP and a respective remote MEP on a respective network node of the plurality of network nodes using an identifier of the respective remote MEP and a Media Access Control (MAC) address of the respective remote MEP, wherein each point-to-point connection enables transmission of unicast CFM messages from the local MEP to the respective remote MEP, and the plurality of point-to-point connections are established within a single maintenance association.
  • MEP local maintenance endpoint
  • XP 17631149 refers to virtual bridge local area networks, in particular to connectivity fault management.
  • Ethernet OAM The operation, management and maintenance of the Ethernet is referred to as Ethernet OAM, and a related protocol standard is IEEE 802.1ag.
  • IEEE 802.1ag protocol is a Connectivity Fault Management protocol (connectivity fault management, CFM for short) protocol.
  • CFM connector fault management protocol
  • the protocol has capabilities of end-to-end fault detection, fault verification, and fault location at a service level and a network level.
  • the purpose of the present invention is to provide an MEP configuration method used to perform configuration for an MEP.
  • a maintenance end point MEP configuration method including the following steps:
  • the completing MEP configuration according to the information about the peer device and the information about the port specifically includes:
  • a manner of acquiring the MEP ID of the local device specifically is:
  • the method further includes:
  • the determining whether MEP configuration to be completed according to the information about the peer device and the information about the port conflicts with existing configuration specifically includes:
  • a network device including:
  • the configuring unit is specifically configured to:
  • the network device further includes:
  • the network device further includes:
  • the determining unit is specifically configured to:
  • a network device includes: a processor, a memory, a communications interface, and a bus, wherein:
  • the processor is specifically configured to: automatically create an MD according to a maintenance domain MD type, an MD name, and an MD level in the information about the peer device; automatically create an MA according to a maintenance association MA type and an MA name in the information about the peer device; automatically associate the created MA with the VLAN tag; automatically configure a CCM message transmission interval in the created MA according to a CCM message transmission interval in the information about the peer device; add an MEP ID of the peer device and an MEP ID of the network device 400 to an MEP List; perform MEP configuration for a preset port and compare whether an identifier of the port is the same as an identifier of the preset port; if the identifier of the port is the same as the identifier of the preset port, configure an MEP direction to down; and if the identifier of the port is different from the identifier of the preset port, configure the MEP direction to up up.
  • a network system includes: a first network device and a second network device, where:
  • a specific implementation manner of the present invention provides a maintenance end point MEP configuration method, where the method is completed by a local Ethernet device. As shown in FIG 1 , the method includes the following steps:
  • the information about the port may include: an identifier of the port and a virtual local area network (Virtual Local Area Network, VLAN for short) tag of the CCM message.
  • VLAN Virtual Local Area Network
  • step 104 further includes:
  • a CCM message body is shown in FIG. 1 , where a flag (Flags) field is further specifically divided into three fields: a remote defect indication (remote defect indication, RDI) field, a reserved field, and a CCM interval field.
  • a remote defect indication remote defect indication
  • RDI remote defect indication
  • CCM interval field a CCM interval field.
  • the MD level, the MA ID, and the CCM transmission interval of the peer MEP can be acquired by parsing a standard CCM message sent by the local MEP.
  • the MA ID may include: an MD type, an MD name, an MA type, and an MA name.
  • configuration information may further include information except the MD level, the MA ID, and the CCM transmission interval. This specific implementation manner of the present invention does not set limitations on other configuration information (that is, the information except the MA level, the MA ID, and the CCM transmission interval).
  • a local Ethernet device in a method provided in this specific implementation manner of the present invention can automatically complete MEP configuration according to a CCM message, and therefore the method has advantages of easy MEP configuration, high efficiency, and wide application.
  • Embodiment 1 provides a specific method for completing MEP configuration according to the information about the peer device and the information about the port, as shown in FIG. 2 , including:
  • the configuring the MEP direction to up may specifically mean: an MEP that is defined in a bridge and sends a CFM message to a forwarding entity of the bridge and receives a CFM message from the forwarding entity of the bridge; and the configuring an MEP direction to down (Down) may specifically mean:
  • a manner of acquiring the MEP ID of the local device specifically is:
  • the calculating the MEP ID of the local device according to a preset algorithm is suitable for a 1:1 mode; and the directly acquiring a pre-configured MEP ID of the local device is suitable for an N:1 mode, where N represents the number of local devices.
  • the preset algorithm may be an algorithm according to which the MEP ID of the local device different from the MEP ID of the peer device can be calculated, for example, 1 may be directly added to the MEP ID of the peer device.
  • the preset algorithm may be another calculation method, and this specific implementation manner of the present invention does not specifically limit thereto.
  • the method further includes:
  • the determining whether MEP configuration to be completed according to the information about the peer device and the information about the port conflicts with existing configuration specifically includes:
  • Embodiment 2 of the present invention provides a maintenance end point MEP configuration method.
  • a technical scenario implemented in this embodiment is as follows: This embodiment is completed between a local device and a peer device, where MEP configuration has been completed on the peer device.
  • User pre-configuration of the local device includes a designated port (certainly, in an actual situation, a user may also have other pre-configurations, such as pre-configuring an MD level).
  • a method for completing the MEP configuration on the peer device may specifically be: enabling a CFM function; creating a maintenance domain MD, where an MD type, an MD name, and a level need to be designated; creating a maintenance association MA, where an MA type and an MA name need to be designated; associating the MA with a VLAN tag; configuring a CCM message transmission interval in the MA; and configuring an MEP List in the MA, where the user is required to designate an MEP ID of the peer device, add the MEP ID of the peer device to the MEP List, calculate an MEP ID of the local device according to the MEP ID of the peer device by using a preset algorithm, and add the MEP ID of the local device to the MEP List.
  • the method includes:
  • the parsing content includes but is not limited to:
  • Step 302 The local device performs determining and comparison according to the parsed and acquired information, so as to confirm whether it is necessary to configure an MEP according to the information about the peer device and the information about the port in the CCM message.
  • Determining content includes but is not limited to:
  • Comparison content includes but is not limited to: the MD level, type, and name, and the MA type and name. If information about the message is inconsistent with configuration of the existing MEP on the local device, it indicates that the message is not a message, of a configured MEP, that is sent by the local device to the peer device.
  • Comparison is performed with user pre-configuration to determine whether the acquired information about the peer device accords with other configurations (for example, an MD level) except an identifier of a port in the user pre-configuration.
  • a conflict check is performed to prevent a conflict with existing configuration.
  • a check range includes but is not limited to: the MD level, type, and name, and the MA type and name. Whether the content is duplicate with the existing configuration is checked. If duplicate, a conflict is determined.
  • the local device completes all configuration on the local device according to the parsed and acquired information and the information about the port.
  • step 303 For an implementation manner of the step 303, refer to the description in Embodiment 1, and details are not described here again.
  • Embodiment 3 of the present invention provides a maintenance end point MEP configuration method.
  • a technical scenario implemented in this embodiment is the same as that in Embodiment 2.
  • a difference from Embodiment 1 is that a pass-through CCM information list is configured on a local device in this embodiment, where the list is used to store a pass-through CCM message.
  • the pass-through CCM message specifically is a message that passes the local device but the local device does not need to perform MEP configuration according to the CCM message. After a conflict is determined, this embodiment further includes the following step:
  • a specific implementation manner after the conflict may specifically be:
  • Comparing content includes but is not limited to: the MD type, name, and level, the MA type and name, the CCM message transmission interval, and the like.
  • a comparison result indicates that the message is a message, of a configured MEP on the local device, that is sent by the peer device and does not need to be added to the pass-through CCM information list. If it is determined that content included in the CCM message is stored in the pass-through CCM information list, it is determined that the CCM message is a pass-through message; and the CCM is transparently transmitted, and the MEP configuration is not required. That a comparison result is the same may specifically be that: all content included in the compared content is the same. That a difference exists in the comparison result described below may specifically be that: any difference in the compared content means a difference in the comparison result.
  • An entry in the pass-through CCM information list is not permanently stored, and ageing may exist.
  • An ageing mechanism is not limited herein, for example, an ageing mechanism of a time threshold is directly set. Certainly, there may be other ageing mechanisms.
  • a specific implementation manner of the present invention further provides a network device 400, where the network device 400 includes:
  • the configuring unit 405 is specifically configured to:
  • the network device 400 further includes:
  • the network device 400 further includes:
  • the determining unit 404 is specifically configured to:
  • a specific implementation manner of the present invention further provides a network device 400.
  • a hardware structure of the network device 400 is shown in FIG. 5 .
  • the network device includes: a processor 501, a memory 502, a communications interface 503, and a bus 504.
  • the processor 501, the memory 502, and the communications interface 503 are connected to each other by using the bus 504.
  • the bus 504 may be an Industry Standard Architecture (Industry Standard Architecture, ISA) bus, a Peripheral Component Interconnect (Peripheral Component Interconnect, PCI for short) bus, or the like.
  • the processor 501 may be a general processor, including a central processing unit (central processing unit, CPU for short), a network processor (network processor, NP for short), and the like.
  • CPU central processing unit
  • NP network processor
  • the memory 502 is configured to store a program 5.
  • the program may include program code.
  • the program code includes a computer operation instruction.
  • the program is configured to instruct the processor 401 to send the computer operation instruction.
  • the memory 502 may include a high-speed random-access memory (random-access memory, RAM for short) and may further include a non-volatile memory (non-volatile memory), for example, at least one disk storage.
  • the communications interface 503 is configured to receive or send a message.
  • the message may be a CCM message and certainly may be another message.
  • the communications interface 503 may be a communications port.
  • the communications interface 503 receives a continuity check message CCM from a peer device.
  • the processor 501 parses the CCM message to acquire information about the peer device and acquire information about a port of the CCM message according to a path of the CCM message, where the information about the port includes: an identifier of an access port of the CCM packet and a VLAN tag of the CCM message; determines whether MEP configuration to be completed according to the information about the peer device and the information about the port conflicts with existing configuration; and when it is determined that the MEP configuration to be completed according to the information about the peer device and the information about the port does not conflict with the existing configuration, completes MEP configuration according to the information about the peer device and the information about the port.
  • the processor 501 is specifically configured to: enable a CFM function; automatically create an MD according to a maintenance domain MD type, an MD name, and an MD level in the information about the peer device; automatically create an MA according to a maintenance association MA type and an MA name in the information about the peer device; automatically associate the created MA with the VLAN tag; automatically configure a CCM message transmission interval in the created MA according to a CCM message transmission interval in the information about the peer device; add an MEP ID of the peer device and an MEP ID of the network device 400 to an MEP List; and perform MEP configuration for a preset port and compare whether the identifier of the access port is the same as an identifier of the preset port; if the identifier of the access port is the same as the identifier of the preset port, configure an MEP direction to down down; and if the identifier of the access port is different from the identifier of the preset port, configure the MEP direction to up up.
  • the processor 501 further directly acquires a pre-configured MEP ID of the network device 400 or calculates the MEP ID of the network device 400 according to the MEP ID of the peer device by using a preset algorithm.
  • the processor 501 is further configured not to perform the MEP configuration when it is determined that the MEP configuration to be completed according to the information about the peer device and the information about the port conflicts with the existing configuration; and then after it is confirmed that the CCM message does not match an existing MEP, it is confirmed that the CCM message also does not match pre-configuration preset by a user, and it is confirmed that the CCM message is not stored in a preset pass-through CCM information list, store the information about the peer device in the CCM message in the pass-through CCM information list.
  • the processor 501 is further configured to: determine that a conflict exists if an MA ID in the CCM message is the same as configuration information of a configured MEP; or
  • a specific implementation manner of the present invention provides a network system, where the system includes a first network device and a second network device.
  • the first network device is configured to send a continuity check message CCM to the second network device; and the second network device is configured to receive a CCM message from a peer device; parse the CCM message to acquire information about the peer device and acquire information about a port receiving the CCM message, where the information about the port includes: identifier information of the port receiving the CCM message and a virtual local area network tag VLAN tag of the CCM message; and complete MEP configuration according to the information about the peer device and the information about the port.
  • modules or units involved in the foregoing unit and system embodiments are divided merely based on function logic; however, the division is not limited to the division manner described above, as long as corresponding functions can be implemented; in addition, specific names of the functional modules are only used for distinguishing the modules from each other, and are not intended to limit protection scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Claims (12)

  1. Procédé de configuration de point d'extrémité de maintenance MEP, consistant à :
    - recevoir un message de vérification de continuité CCM d'un dispositif pair (101) ;
    - analyser le message CCM pour acquérir des informations sur le dispositif pair (102), les informations sur le dispositif pair comprenant : un niveau de domaine de maintenance MD, un identifiant d'association de maintenance MA ID, un intervalle de transmission de CCM du dispositif pair ;
    - acquérir des informations sur un port recevant le message CCM (103), les informations sur le port comprenant : des informations d'identifiant du port recevant le message CCM et une étiquette de réseau local virtuel VLAN tag du message CCM ;
    - déterminer si une configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port est en conflit avec une configuration existante ;
    et
    - si la configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port n'est pas en conflit avec la configuration existante, finaliser la configuration MEP en fonction des informations sur le dispositif pair et des informations sur le port (104).
  2. Procédé selon la revendication 1, dans lequel la finalisation de la configuration MEP en fonction des informations sur le dispositif pair et des informations sur le port consiste spécifiquement à :
    - créer un MD en fonction d'un type de domaine de maintenance MD, d'un nom de MD et du niveau de MD dans les informations sur le dispositif pair ;
    - créer une MA en fonction d'un type d'association de maintenance MA et d'un nom de MA dans les informations sur le dispositif pair ;
    - associer la MA créée à la VLAN tag ;
    - configurer un intervalle de transmission de message CCM dans la MA créée en fonction de l'intervalle de transmission de message CCM dans les informations sur le dispositif pair ;
    - ajouter un MEP ID du dispositif pair et un MEP ID d'un dispositif local à une liste MEP ; et
    - effectuer une configuration MEP pour un port prédéfini et comparer si les informations d'identifiant du port sont identiques à un identifiant du port prédéfini ; si un identifiant du port est identique à l'identifiant du port prédéfini, configurer une direction MEP vers le bas ; et si l'identifiant du port est différent de l'identifiant du port prédéfini, configurer la direction MEP vers le haut.
  3. Procédé selon la revendication 2, dans lequel une manière d'acquérir le MEP ID du dispositif local consiste spécifiquement à acquérir directement un MEP ID préconfiguré du dispositif local ou calculer le MEP ID du dispositif local en fonction du MEP ID du dispositif pair en utilisant un algorithme prédéfini.
  4. Procédé selon la revendication 1, lequel consiste en outre à ne pas effectuer la configuration MEP si la configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port est en conflit avec la configuration existante ; et une fois confirmé que le message CCM ne correspond pas à un MEP existant, il est confirmé que le message CCM ne correspond pas non plus à une pré-configuration prédéfinie par un utilisateur, ou il est confirmé que le message CCM n'est pas stocké dans une liste d'informations CCM de passage prédéfinie, stocker les informations sur le dispositif pair dans le message CCM dans la liste d'informations CCM de passage.
  5. Procédé selon la revendication 1, dans lequel le fait de déterminer si la configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port entre en conflit avec une configuration existante consiste spécifiquement à :
    - déterminer qu'un conflit existe si le MA ID dans le message CCM est identique aux informations de configuration d'un MEP configuré ; ou
    - déterminer qu'un conflit existe si le niveau de MD dans le message CCM existe dans un niveau de MD d'un MEP configuré et un nom ou un type de MD est différent ; ou
    - déterminer qu'un conflit existe si le nombre de MA configurées dépasse une limite supérieure ; ou
    - déterminer qu'un conflit existe si un nom de MD dans un MA ID d'un MEP configuré est identique à un nom de MD dans le MA ID dans le message CCM, mais qu'un niveau de MD du MEP configuré est différent du niveau de MD dans le message CCM.
  6. Dispositif de réseau comprenant :
    - une unité de réception (401) conçue pour recevoir un message de vérification de continuité CCM d'un dispositif pair ;
    - une unité d'analyse (402) conçue pour analyser le message CCM pour acquérir des informations sur le dispositif pair, les informations sur le dispositif pair comprenant : un niveau de domaine de maintenance MD, un identifiant d'association de maintenance MA ID, un intervalle de transmission CCM du dispositif pair ;
    - une unité d'acquisition de trajet (403) conçue pour acquérir des informations sur un port recevant le message CCM, les informations sur le port comprenant : des informations d'identifiant du port recevant le message CCM et une étiquette de réseau local virtuel VLAN tag du message CCM ;
    - une unité de détermination (404) conçue pour déterminer si une configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port est en conflit avec une configuration existante ; et
    - une unité de configuration (405) conçue pour finaliser la configuration MEP en fonction des informations sur le dispositif pair et des informations sur le port si la configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port n'est pas en conflit avec la configuration existante.
  7. Dispositif de réseau selon la revendication 6, dans lequel l'unité de configuration est spécifiquement conçue pour :
    - créer automatiquement un MD en fonction d'un type de MD, d'un nom de MD et du niveau de MD dans les informations sur le dispositif pair ;
    - créer automatiquement une MA en fonction d'un type de MA et d'un nom de MA dans les informations sur le dispositif pair ;
    - associer la MA créée à la VLAN tag ;
    - configurer un intervalle de transmission de message CCM dans la MA créée en fonction de l'intervalle de transmission de message CCM dans les informations sur le dispositif pair ;
    - ajouter un MEP ID du dispositif pair et un MEP ID du dispositif de réseau à la liste MEP ; et
    - effectuer une configuration MEP pour un port prédéfini et comparer si les informations d'identifiant du port sont identiques à un identifiant du port prédéfini ; si un identifiant du port est identique à l'identifiant du port prédéfini, configurer une direction MEP vers le bas ; et si l'identifiant du port est différent de l'identifiant du port prédéfini, configurer la direction MEP vers le haut.
  8. Dispositif de réseau selon la revendication 6, lequel comprend en outre :
    - une unité de traitement de passage conçue pour ne pas effectuer la configuration MEP lorsque l'unité de détermination détermine que la configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port est en conflit avec la configuration existante ; et une fois confirmé que le message CCM ne correspond pas à un MEP existant, il est confirmé que le message CCM ne correspond pas non plus à une pré-configuration prédéfinie par un utilisateur, ou il est confirmé que le message CCM n'est pas stocké dans une liste d'informations CCM de passage prédéfinie, stocker les informations sur le dispositif pair dans le message CCM dans la liste d'informations CCM de passage.
  9. Dispositif de réseau selon la revendication 6, dans lequel l'unité de détermination est spécifiquement conçue pour :
    - déterminer qu'un conflit existe si le MA ID dans le message CCM est identique aux informations de configuration d'un MEP configuré ; ou
    - déterminer qu'un conflit existe si le niveau de MD dans le message CCM existe dans un niveau de MD d'un MEP configuré et un nom ou un type de MD est différent ; ou
    - déterminer qu'un conflit existe si le nombre de MA configurées dépasse une limite supérieure ; ou
    - déterminer qu'un conflit existe si un nom de MD dans un MA ID d'un MEP configuré est identique à un nom de MD dans le MA ID dans le message CCM, mais qu'un niveau de MD du MEP configuré est différent du niveau de MD dans le message CCM.
  10. Dispositif de réseau, lequel comprend : un processeur (501), une mémoire (502), une interface de communication (503) et un bus (504), dans lequel :
    - l'interface de communication (503) est conçue pour recevoir un message de vérification de continuité CCM d'un dispositif pair ; et
    - le processeur (501) est conçu pour :
    - analyser le message CCM pour acquérir des informations sur le dispositif pair et acquérir des informations sur un port recevant le message CCM, les informations sur le port comprenant : des informations d'identifiant du port recevant le message CCM et une étiquette de réseau local virtuel VLAN tag du message CCM ;
    - déterminer si une configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port est en conflit avec une configuration existante ; et lorsqu'il est déterminé que la configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port n'est pas en conflit avec la configuration existante, finaliser la configuration MEP en fonction des informations sur le dispositif pair et des informations sur le port.
  11. Dispositif de réseau selon la revendication 10, dans lequel le processeur est spécifiquement conçu pour : créer automatiquement un MD en fonction d'un type de domaine de maintenance MD, d'un nom de MD et d'un niveau de MD dans les informations sur le dispositif pair ; créer automatiquement une MA en fonction d'un type d'association de maintenance MA et d'un nom de MA dans les informations sur le dispositif pair ; associer automatiquement la MA créée à la VLAN tag ; configurer automatiquement un intervalle de transmission de message CCM dans la MA créée en fonction d'un intervalle de transmission de message CCM dans les informations sur le dispositif pair ; ajouter un MEP ID du dispositif pair et un MEP ID du dispositif de réseau à la liste MEP ; effectuer une configuration MEP pour un port prédéfini et comparer si un identifiant du port est identique à un identifiant du port prédéfini ; si l'identifiant du port est identique à l'identifiant du port prédéfini, configurer une direction MEP vers le bas ; et si l'identifiant du port est différent de l'identifiant du port prédéfini, configurer la direction MEP vers le haut.
  12. Système de réseau, lequel système comprend un premier dispositif de réseau et un second dispositif de réseau, dans lequel :
    - le premier dispositif de réseau est conçu pour envoyer un message de vérification de continuité CCM au second dispositif de réseau ; et
    - le second dispositif de réseau est conçu pour :
    - recevoir un message CCM d'un dispositif pair et analyser le message CCM afin d'acquérir des informations sur le dispositif pair et d'acquérir des informations sur un port recevant le message CCM, les informations sur le port comprenant : des informations d'identifiant du port recevant le message CCM et une étiquette de réseau local virtuel VLAN tag du message CCM ;
    - déterminer si une configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port entre en conflit avec une configuration existante ; et lorsqu'il est déterminé que la configuration MEP à finaliser en fonction des informations sur le dispositif pair et des informations sur le port n'est pas en conflit avec la configuration existante, finaliser la configuration MEP en fonction des informations sur le dispositif pair et des informations sur le port.
EP13883350.4A 2013-06-17 2013-06-17 Procédé de configuration mep et dispositif de réseau Active EP2840738B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/077349 WO2014201613A1 (fr) 2013-06-17 2013-06-17 Procédé de configuration mep et dispositif de réseau

Publications (3)

Publication Number Publication Date
EP2840738A1 EP2840738A1 (fr) 2015-02-25
EP2840738A4 EP2840738A4 (fr) 2015-08-26
EP2840738B1 true EP2840738B1 (fr) 2016-12-21

Family

ID=52103786

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13883350.4A Active EP2840738B1 (fr) 2013-06-17 2013-06-17 Procédé de configuration mep et dispositif de réseau

Country Status (5)

Country Link
US (1) US9985862B2 (fr)
EP (1) EP2840738B1 (fr)
CN (1) CN104471897B (fr)
ES (1) ES2617974T3 (fr)
WO (1) WO2014201613A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9847911B1 (en) * 2015-06-16 2017-12-19 Juniper Networks, Inc. System and method for customized port configuration
US10193746B2 (en) * 2016-12-21 2019-01-29 Juniper Networks, Inc. Deadlock avoidance using modified ethernet connectivity fault management signaling
CN110233799B (zh) * 2018-03-05 2021-10-26 华为技术有限公司 一种端口配置的方法和通信设备
US11483195B2 (en) * 2018-09-20 2022-10-25 Ciena Corporation Systems and methods for automated maintenance end point creation

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100536409C (zh) 2005-04-19 2009-09-02 华为技术有限公司 一种环回的实现方法
HUE040657T2 (hu) * 2007-08-01 2019-03-28 Ericsson Telefon Ab L M GMPLS alapú OAM ellátás
JP4946851B2 (ja) * 2007-12-19 2012-06-06 富士通株式会社 フレーム転送方法及びフレーム転送装置
US8175008B1 (en) * 2008-06-17 2012-05-08 Juniper Networks, Inc. Auto MEP ID assignment within CFM maintenance association
CN101651575A (zh) 2008-08-14 2010-02-17 华为技术有限公司 发现邻居的方法及节点
CN101369922B (zh) 2008-09-28 2011-04-06 华为技术有限公司 一种连通性检测方法和维护域终点及系统
US8125914B2 (en) * 2009-01-29 2012-02-28 Alcatel Lucent Scaled Ethernet OAM for mesh and hub-and-spoke networks
US8385353B2 (en) * 2009-03-23 2013-02-26 Cisco Technology, Inc. Connectivity fault management (CFM) auto-provisioning using virtual private LAN service (VPLS) auto-discovery
CN101662383B (zh) * 2009-09-17 2011-09-07 杭州华三通信技术有限公司 一种配置维护端点的方法及设备
US8416696B2 (en) * 2010-01-04 2013-04-09 Cisco Technology, Inc. CFM for conflicting MAC address notification
CN102215130B (zh) * 2011-06-16 2013-12-11 杭州华三通信技术有限公司 一种cfd协议配置方法及其装置
US9264328B2 (en) * 2011-11-07 2016-02-16 Ciena Corporation Systems and methods for dynamic operations, administration, and management

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP2840738A4 (fr) 2015-08-26
US9985862B2 (en) 2018-05-29
WO2014201613A1 (fr) 2014-12-24
EP2840738A1 (fr) 2015-02-25
ES2617974T3 (es) 2017-06-20
CN104471897A (zh) 2015-03-25
CN104471897B (zh) 2018-02-06
US20160105348A1 (en) 2016-04-14

Similar Documents

Publication Publication Date Title
US11223514B2 (en) Method and system of a dynamic high-availability mode based on current wide area network connectivity
US7995483B1 (en) Simultaneously testing connectivity to multiple remote maintenance endpoints of the same maintenance association
US11374857B2 (en) Network device management method and apparatus, and system for indicating a network device to perform management operation
US10091274B2 (en) Method, device, and system for controlling network device auto-provisioning
EP2843906B1 (fr) Procédé, appareil et système de transmission de données
EP2725737A1 (fr) Procédé de configuration de politique de réseau, dispositif de gestion et centre de gestion de réseau
US10277454B2 (en) Handling failure of stacking system
US9883010B2 (en) Method, apparatus, device and system for generating DHCP snooping binding table
US8432833B2 (en) Auto MEP ID assignment within CFM maintenance association
US10470111B1 (en) Protocol to detect if uplink is connected to 802.1D noncompliant device
US9985862B2 (en) MEP configuration method and network device
US10862735B2 (en) Method and apparatus for implementing operation, administration, and maintenance function
US9350628B2 (en) Dynamic management of maintenance association membership in a computer network
CN108234234B (zh) 维护端点设备、用于通信的方法和计算机可读介质
CN110912727B (zh) 用于非侵入式网络性能监测的系统和方法
US11522754B2 (en) Systems and methods for Zero-Touch Provisioning of a switch in intermediate distribution frames and main distribution frames
AU2015361776B2 (en) Method, apparatus and system for managing terminal device in passive optical network
CN109379239B (zh) 一种OpenStack环境中配置接入交换机的方法及装置
US10680930B2 (en) Method and apparatus for communication in virtual network
EP2858302A1 (fr) Procédé de vérification de connectivité sur une liaison de flux de service, appareil connexe, et système
WO2016015606A1 (fr) Procédé de localisation d'erreur de connexion de port et dispositif associé
CN107528788B (zh) 实现网络设备之间自动堆叠的方法和装置
US9256416B1 (en) Methods and apparatus for automatic session validation for distributed access points
WO2020029928A1 (fr) Procédé d'établissement d'une session bgp et d'envoi d'une adresse d'interface et d'alias, et dispositif de réseau
CN108616390B (zh) 刀箱管理方法、装置和刀箱管理的实现装置

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20141106

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20150727

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/24 20060101AFI20150721BHEP

Ipc: H04L 12/26 20060101ALI20150721BHEP

17Q First examination report despatched

Effective date: 20151222

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

DAX Request for extension of the european patent (deleted)
INTG Intention to grant announced

Effective date: 20160707

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 856320

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170115

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602013015766

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20161221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170321

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170322

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 5

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 856320

Country of ref document: AT

Kind code of ref document: T

Effective date: 20161221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2617974

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20170620

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170421

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170421

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170321

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602013015766

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20170922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170630

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170617

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170617

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170630

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170617

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20130617

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161221

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602013015766

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012240000

Ipc: H04L0041000000

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20230510

Year of fee payment: 11

Ref country code: FR

Payment date: 20230510

Year of fee payment: 11

Ref country code: DE

Payment date: 20230502

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230504

Year of fee payment: 11

Ref country code: ES

Payment date: 20230712

Year of fee payment: 11