WO2014201613A1 - 一种mep配置方法及网络设备 - Google Patents

一种mep配置方法及网络设备 Download PDF

Info

Publication number
WO2014201613A1
WO2014201613A1 PCT/CN2013/077349 CN2013077349W WO2014201613A1 WO 2014201613 A1 WO2014201613 A1 WO 2014201613A1 CN 2013077349 W CN2013077349 W CN 2013077349W WO 2014201613 A1 WO2014201613 A1 WO 2014201613A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
mep
ccm
port
configuration
Prior art date
Application number
PCT/CN2013/077349
Other languages
English (en)
French (fr)
Inventor
胡坤
陈锐
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP13883350.4A priority Critical patent/EP2840738B1/en
Priority to CN201380002617.0A priority patent/CN104471897B/zh
Priority to ES13883350.4T priority patent/ES2617974T3/es
Priority to PCT/CN2013/077349 priority patent/WO2014201613A1/zh
Publication of WO2014201613A1 publication Critical patent/WO2014201613A1/zh
Priority to US14/971,091 priority patent/US9985862B2/en

Links

Images

Classifications

    • 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/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
    • 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 belongs to the field of communications, and in particular, to a MEP configuration method and a network device.
  • Ethernet (English: Ethernet) technology has become one of the most important technologies in the entire communication network due to its ease of use and low cost. With the continuous development of telecommunication networks, Ethernet technology has been widely applied in the enterprise network, metropolitan area network, and wide area network. Traditional Ethernet technology management and maintenance methods are very limited, and carrier-class operation methods are even blank. Operators can only rely on simple network management protocols (English: simple Network management protocol , referred to as: SNMP) to manage the Ethernet network, the number of Ethernet devices managed in this way is limited and requires a large number of Internet protocols (English: internet protocol, referred to as: IP); The cost added by operators for the deployment, management, and maintenance of Ethernet is becoming more and more obvious, so Ethernet operation management and maintenance are filled. (English: Operation Administration and Maintenance, referred to as: OAM) The agreement gap is imperative.
  • simple network management protocol English: simple Network management protocol , referred to as: SNMP
  • IP internet protocol
  • OAM Operation Administration and Maintenance
  • Ethernet OAM The operation management maintenance on Ethernet is called Ethernet OAM, and the related protocol standard is IEEE 802.1ag.
  • IEEE 802.1ag protocol is a connection fault management protocol, also known as connection fault management. Management, referred to as: CFM) agreement.
  • the protocol has end-to-end fault detection, fault acknowledgment and fault location capabilities at the service level and network level.
  • a method for maintaining a terminal point MEP including the steps of:
  • the information of the peer device includes: a maintenance domain MD level, a maintenance set identifier MA ID, and a CCM sending period of the peer MEP;
  • Obtaining information about receiving the CCM packet port where the information of the port includes: receiving identifier information of the CCM packet port and a virtual local area network label VLAN of the CCM packet Tag;
  • the MEP configuration is completed according to the information of the peer device and the information of the port.
  • the method is configured before the MEP configuration is completed according to the information of the peer device and the information of the port. Also includes:
  • the MEP configuration is completed according to the information of the peer device and the ingress port information.
  • the completing the MEP configuration according to the information of the peer device and the information of the port specifically includes:
  • the MEP Perform MEP configuration on the preset port, and compare whether the identification information of the port is the same as the identifier of the preset port. If the identifier of the ingress port is the same as the identifier of the preset port, the MEP is The direction of the MEP is configured to be down. If the identifier of the ingress port is different from the identifier of the preset port, the direction of the MEP is configured to be up.
  • the MEP of the local device In combination with the second alternative of the first aspect, in the third alternative of the first aspect, the MEP of the local device The way to obtain the ID is as follows:
  • the ID calculates the MEP ID of the local device through a preset algorithm.
  • the method further includes:
  • the MEP configuration conflicts with the existing configuration according to the information of the peer device and the information about the port, the MEP configuration is not performed, and the CCM packet is not matched with the existing MEP, and the CCM report is confirmed. If the CCM message is not stored in the pre-set CCM information list, the information of the peer device in the CCM message is stored in the transit CCM. Inside the information list.
  • the determining, according to the information of the peer device and the information about the port, whether the MEP configuration is completed and existing Configuration conflicts include:
  • the MD name of the MA ID of the configured MEP and the MA in the CCM message is the same, but the MD level of the configured MEP is different from the MD level in the CCM message.
  • a network device including:
  • a receiving unit configured to receive a connectivity detection CCM message of the peer device
  • a parsing unit configured to parse the CCM packet to obtain information of the peer device;
  • the information of the peer device includes: a maintenance domain MD level of the peer MEP, and a maintenance set identifier MA ID And CCM transmission cycle;
  • a path obtaining unit configured to obtain information about receiving the CCM packet port, where the information of the port includes: identifier information for receiving the CCM packet port, and a virtual local area network label VLAN of the CCM packet Tag;
  • a configuration unit configured to complete the MEP configuration according to the information of the peer device and the information of the port.
  • the device further includes:
  • the determining unit is configured to determine whether the MEP configuration conflicts with the existing configuration according to the information of the peer device and the ingress port information.
  • the configuration unit is specifically configured to:
  • the CCM packet sending period in the information of the peer device is configured to configure a CCM packet sending period in the created MA:
  • the MEP Perform MEP configuration on the preset port, and compare whether the identification information of the port is the same as the identifier of the preset port. If the identifier of the ingress port is the same as the identifier of the preset port, the MEP is The direction of the MEP is configured to be down. If the identifier of the ingress port is different from the identifier of the preset port, the direction of the MEP is configured to be up.
  • the network device further includes:
  • An obtaining unit configured to directly obtain a pre-configured MEP ID of the network device or a MEP according to the peer device
  • the ID calculates the MEP ID of the network device through a preset algorithm.
  • the network device further includes:
  • the path processing unit is configured to: when the determining unit determines that the MEP configuration conflicts with the existing configuration according to the information of the peer device and the information of the port, does not perform MEP configuration, and confirms that the CCM packet matches If the CCM message is not matched with the pre-configured pre-configuration or the CCM message is not stored in the preset CCM information list, the CCM message is not in the CCM message.
  • the information of the peer device is stored in the list of transit CCM information.
  • the determining unit is specifically configured to:
  • the MD name of the MA ID of the configured MEP and the MA in the CCM message is the same, but the MD level of the configured MEP is different from the MD level in the CCM message.
  • a network device comprising: a processor, a memory, a communication interface, and a bus.
  • the communication interface is configured to receive a connectivity detection CCM message of the peer device
  • the processor is configured to: parse the information of the CCM packet to obtain the information of the peer device, and obtain the information of the CCM packet port, where the information of the port includes: receiving the identifier information of the CCM packet port and Virtual local area network label VLAN of the CCM message
  • the MEP configuration is completed according to the information of the peer device and the information of the port.
  • the processor is further
  • the processor is specifically configured to: maintain a domain MD type, an MD name, and an MD level according to the information of the peer device. Automatically creating an MD; automatically creating an MA according to the type of the maintenance set MA and the MA name in the information of the peer device; automatically creating the MA and the VLAN
  • the CCM packet sending period in the created MA is automatically configured according to the CCM packet sending period in the information of the peer device: the MEP ID of the peer device and the MEP of the network device 400 ID added to enter MEP List: Perform MEP configuration on a preset port, and compare whether the identifier of the ingress port is the same as the identifier of the preset port.
  • the direction of the MEP is configured to be down. If the identifier of the ingress port is different from the identifier of the preset port, the direction of the MEP is configured to be up.
  • a fourth aspect 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 connectivity detection CCM message to the second network device;
  • the second network device is configured to receive a CCM message of the peer device, and obtain the information about the port of the CCM message by the CCM message, and the information about the port includes: Receiving the identification information of the CCM message port and the virtual local area network label VLAN of the CCM message
  • the MEP configuration is completed according to the information of the peer device and the information of the port.
  • the technical solution provided by the present invention has the advantages of simple MEP configuration, high efficiency, and wide application.
  • FIG. 1 is a schematic structural diagram of a CCM message body according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for configuring an MEP according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for configuring a maintenance terminal point MEP according to Embodiment 1 of the present invention
  • FIG. 4 is a schematic structural diagram of a network device according to a specific mode of the present invention.
  • FIG. 5 is a schematic structural diagram of hardware of a network device according to an embodiment of the present invention.
  • a specific embodiment of the present invention provides a method for configuring a maintenance terminal point MEP, which is implemented by a local Ethernet device. The method is as shown in FIG.
  • the foregoing port information may include: an identifier of the port and a virtual local area network of the CCM message (English: Virtual Local Area Network, referred to as: VLAN) tag tag;
  • the foregoing method further includes: between 104:
  • the structure of the CCM message is shown in Figure 1.
  • the identifier (English: Flags) field is divided into three fields: the remote fault indication. Indication, RDI) field, reserved field, and CCM period field; as shown in Figure 1, the CCM message carries the maintenance domain (Maintenance Domain) , MD) level, MD type, MD name, maintenance set (Maintenance Association , MA) type, MA name, CCM transmission period. MD level and MA ID of the local MEP and the peer MEP in the MEP configuration. The CCM send cycle must be identical. Then it means that the MD level and MA ID of the peer MEP.
  • the CCM transmission period can be obtained by parsing the standard CCM message sent by the local MEP.
  • the ID may include: MD type, MD name, MA type, and MA name.
  • the configuration information can also include, in addition to the MD level, MA.
  • the ID and CCM transmit information other than the period. The specific embodiment of the present invention does not limit other configuration information (ie, information other than the MD level, the MA ID, and the CCM transmission period).
  • the local Ethernet device in the method provided by the embodiment of the present invention can automatically complete the MEP configuration according to the CCM message, so it has the advantages of simple MEP configuration, high efficiency, and wide application.
  • the embodiment 1 provides a specific method for completing the MEP configuration according to the information of the peer device and the information of the port. As shown in FIG. 2, the method includes:
  • 207. Perform MEP configuration on the preset port, and compare whether the identifier of the ingress port is the same as the identifier of the preset port. If the identifier of the ingress port is the same as the identifier of the preset port, The direction of the MEP is configured to be down. If the identifier of the ingress port is different from the identifier of the preset port, the direction of the MEP is configured to be up.
  • the specific meaning of configuring the direction of the MEP to be UP may be: a MEP defined in the bridge and sent to and received from the forwarding entity of the bridge;
  • the method for obtaining the MEP ID of the local device is specifically:
  • the ID calculates the MEP ID of the local device through a preset algorithm.
  • the MEP of the local device is calculated according to the preset algorithm.
  • the ID is suitable for the 1:1 mode.
  • the MEP ID of the local device that is pre-configured is suitable for the N:1 mode, where N is the number of local devices.
  • the foregoing preset algorithm may be a MEP capable of calculating a peer device different from the local device MEP ID according to the algorithm.
  • ID can be, for example, you can directly add 1 to the MEP ID of the peer device.
  • MEP ID of the local device [MEP of the peer device ID)%8191]+1;
  • other calculation methods are also possible, and the specific embodiment of the present invention does not specifically limit the algorithm.
  • the foregoing method further includes:
  • the MEP configuration conflicts with the existing configuration according to the information of the peer device and the information about the port, the MEP configuration is not performed, and the CCM packet is not matched with the existing MEP, and the CCM report is confirmed.
  • the CCM message is not stored in the pre-set CCM information list, the information of the peer device in the CCM message is stored in the transit CCM.
  • the foregoing CCM information list may include: information about the CCM message, which may include: the type, name, and level of the MD, the type and name of the MA, the CCM packet sending period, and the MEP. ID, etc.
  • the foregoing determining, according to the information of the peer device and the information about the port, whether the MEP configuration conflicts with the existing configuration includes:
  • the MD name of the MA ID of the configured MEP and the MA in the CCM message is the same, but the MD level of the configured MEP is different from the MD level in the CCM message. If the same, use the existing MA ID directly.
  • the first embodiment of the present invention provides a method for configuring a MEP of a maintenance terminal.
  • the technical scenario implemented in this embodiment is as follows: the local device is configured between the local device and the remote device, and the peer device has completed the configuration of the MEP.
  • the user pre-configuration of the local device includes: the specified port (of course, in the actual situation, the user may also have other pre-configurations, such as the pre-configured MD level), and the method for configuring the MEP of the peer device may be specifically : Enable the CFM function.
  • Create a maintenance domain MD You need to specify the MD type, MD name, and level. You need to specify the MA type and MA name for the maintenance set MA.
  • the tag is associated; the CCM packet sending period in the MA is configured.
  • the MEP list in the MA is configured.
  • the user is required to specify the MEP ID of the peer device and add the MEP ID of the peer device to the MEP.
  • the MEP ID of the local device is calculated based on the MEP ID of the peer device, and the MEP ID of the local device is also added to the MEP. List.
  • the method is shown in Figure 3 and includes:
  • Step 301 The local device parses the CCM packet sent by the peer device, and obtains the transmission path information of the CCM packet.
  • the information of the peer device is obtained by parsing the received CCM message, and the information of the peer device includes, but is not limited to, the type, name, and level of the MD, the type and name of the MA, the CCM packet sending period, and the MEP of the peer device. ID;
  • the information about the port is obtained, including but not limited to: the ingress port identifier of the CCM packet (for example, the ingress port number, of course, other types of identifiers), and the VLAN of the CCM packet.
  • the ingress port identifier of the CCM packet for example, the ingress port number, of course, other types of identifiers
  • the VLAN of the CCM packet is obtained, including but not limited to: the ingress port identifier of the CCM packet (for example, the ingress port number, of course, other types of identifiers), and the VLAN of the CCM packet.
  • Tag according to the VLAN of the CCM message Tag, you can identify the business it detects.
  • different vendors may need to parse more information when completing the MEP configuration.
  • the information of the peer device is required to be parsed.
  • Step 302 The local device performs judgment and comparison according to the information obtained by the foregoing analysis, and confirms whether the MEP needs to be configured according to the information of the peer device and the information of the port in the CCM message.
  • Judgment content includes but is not limited to:
  • the comparison with the existing MEP on the local device is used to determine whether the CCM packet is a CCM packet sent by the peer device to a configured MEP of the local device.
  • Comparisons include but are not limited to: MD The level, type, name, type and name of the MA. If the packets are inconsistent, the packet is not sent by the local device to a configured MEP.
  • the obtained peer device information conforms to other configurations (such as MD level) other than the port identifier in the pre-configuration of the user.
  • the scope of inspection includes but is not limited to: MD The level, type, name, type and name of the MA, check if the content is duplicated with the existing configuration. If it is repeated, it is determined to be a conflict.
  • the local device completes all configurations on the device according to the information obtained by the foregoing analysis and the information about the port.
  • the second embodiment of the present invention provides a method for configuring a MEP of a maintenance terminal.
  • the technical solution of the embodiment is the same as that of the first embodiment.
  • the difference between the embodiment and the first embodiment is that the local device in the embodiment is also provided with a CCM.
  • the information list, the list is used to store the CCM message, and the CCM message is specifically configured to pass the local device, but the local device does not need to perform the MEP configuration according to the CCM message; In the future, the following steps are also included:
  • the device that runs this mechanism parses the received CCM packets in real time.
  • the parsed content includes but is not limited to: MD type, name, level, MA type, name, CCM packet sending period, MEP. ID, etc.
  • the packet information is compared with the existing MEP configuration on the local device.
  • the comparison includes, but is not limited to, the type, name, and level of the MD, the type and name of the MA, and the CCM packet sending period.
  • the packet is sent to the local device on the local device.
  • the MEC does not need to be added to the CCM information list. If the content of the CCM packet is included in the CCM information list. Then, the CCM message is determined to be a transit packet, and the CCM can be transparently transmitted without performing MEP configuration.
  • the above comparison results may be the same, and the content included in the above comparison content is the same.
  • the following comparison results may be different: any one of the comparison contents is different in comparison result.
  • the packet is considered to be used by the local device to complete the local MEP configuration.
  • the device will complete the configuration of the local MEP based on the content of this packet. It does not need to join the CCM information list.
  • the port of the MEP specified in the pre-configuration receives the CCM packet but fails to match the other pre-configurations, for example, the user also specifies the name of the MD, indicating that this is not the packet sent to the device. If there is no such message information in the CCM information list, the message is added to the CCM information list. Otherwise, it is not necessary to repeatedly join the CCM information list.
  • the port of the MEP specified in the pre-configuration does not receive the packet. This indicates that the packet is not sent to the local device. If the CCM information list does not contain the packet, the packet is added. Pass the CCM information list, otherwise you do not need to repeatedly join the CCM information list.
  • the entries in the CCM information list will not be saved all the time, and there will be aging.
  • the aging mechanism is not limited here.
  • the time threshold aging mechanism is directly set, and of course, there may be other aging mechanisms.
  • a specific embodiment of the present invention further provides a network device 400, where the network device 400 includes:
  • the receiving unit 401 is configured to receive a connectivity detection CCM message of the peer device.
  • the parsing unit 402 is configured to parse the CCM packet to obtain information about the peer device.
  • the path obtaining unit 403 is configured to obtain, according to the path of the CCM packet, information about a port of the CCM packet, where the information of the port includes: an identifier of an ingress port of the CCM packet and the CCM packet VLAN Tag;
  • the determining unit 404 is configured to determine whether the MEP configuration conflicts with the existing configuration according to the information of the peer device and the information of the port;
  • the configuration unit 405 is configured to: when the determining unit determines that the MEP configuration does not conflict with the existing configuration according to the information of the peer device and the information of the port, according to the information and location of the peer device The information about the port completes the MEP configuration.
  • the configuration unit 405 is specifically configured to:
  • the CCM packet sending period in the created MA is automatically configured according to the CCM packet sending period in the information of the peer device:
  • the MEP Perform MEP configuration on the preset port, and compare whether the identifier of the ingress port is the same as the identifier of the preset port. If the identifier of the ingress port is the same as the identifier of the preset port, the MEP is The direction of the MEP is configured to be down. If the identifier of the ingress port is different from the identifier of the preset port, the direction of the MEP is configured to be up.
  • the network device 400 further includes:
  • the obtaining unit 406 is configured to directly obtain the MEP ID of the pre-configured network device 400 or the MEP according to the peer device
  • the ID calculates the MEP ID of the network device 400 through a preset algorithm.
  • the network device 400 further includes:
  • the processing unit 407 is configured to: when the determining unit determines that the MEP configuration conflicts with the existing configuration according to the information of the peer device and the information of the port, does not perform MEP configuration, and then confirms the CCM report. If the CME message does not match the pre-configured pre-configuration and the CCM message is not stored in the preset CCM information list, the CCM message is not matched with the existing MEP. The information of the peer device in the text is stored in the list of transit CCM information.
  • the determining unit 404 is specifically configured to:
  • the MD name of the MA ID of the configured MEP and the MA in the CCM message is the same, but the MD level of the configured MEP is different from the MD level in the CCM message.
  • a specific embodiment of the present invention further provides a network device 400.
  • the hardware structure of the network device 400 is as shown in FIG. 5, and includes a processor 501, a memory 502, a communication interface 503, and a bus 504.
  • the processor 501, the memory 502, and the communication interface 503 are connected to each other through a bus 504;
  • the bus 504 can be an industry standard architecture system (Industry Standard) Architecture, ISA) bus or peripheral component interconnection (English: Peripheral Component Interconnect, referred to as: PCI) bus.
  • Industry Standard Industry Standard
  • ISA Industry Standard
  • PCI Peripheral Component Interconnect
  • the processor 501 described above may be a general purpose processor, including a central processing unit (English: central processing) Unit, referred to as CPU), network processor (English: network processor, referred to as NP).
  • CPU central processing unit
  • NP network processor
  • the memory 502 is configured to store the program 5.
  • the program can include program code, the program code including computer operating instructions for instructing the processor 401 to issue computer operating instructions.
  • Memory 502 may contain high speed random access memory (English: random-access Memory, referred to as RAM, may also include non-volatile memory, such as at least one disk storage.
  • the communication interface 503 is configured to receive or send a message.
  • the message may be a CCM message, and may be other messages.
  • the communication interface 503 may be a communication port.
  • the communication interface 503 receives the connectivity detection CCM message of the peer device
  • the processor 501 parses the CCM packet to obtain the information of the peer device, and obtains information about the port of the CCM packet according to the path of the CCM packet, where the information of the port includes: the CCM packet ID of the ingress port and VLAN of the CCM packet Determining whether the MEP configuration conflicts with the existing configuration according to the information of the peer device and the information of the port; determining that the MEP configuration is completed according to the information of the peer device and the information of the port If some configurations do not conflict, the MEP configuration is completed according to the information of the peer device and the information of the port.
  • the processor 501 is specifically configured to enable the CFM function; automatically create an MD according to the maintenance domain MD type, the MD name, and the MD level in the information of the peer device; and according to the type of the maintenance set MA in the information of the peer device,
  • the MA name automatically creates an MA; the MA is automatically created with the VLAN.
  • the CCM packet sending period in the created MA is automatically configured according to the CCM packet sending period in the information of the peer device: the MEP ID of the peer device and the MEP of the network device 400 ID added to enter MEP List: Perform MEP configuration on a preset port, and compare whether the identifier of the ingress port is the same as the identifier of the preset port.
  • the direction of the MEP is configured to be down. If the identifier of the ingress port is different from the identifier of the preset port, the direction of the MEP is configured to be up.
  • the processor 501 directly obtains the MEP ID of the pre-configured network device 400 or the MEP according to the peer device.
  • the ID calculates the MEP ID of the network device 400 through a preset algorithm.
  • the processor 501 is further configured to: when determining that the MEP configuration conflicts with the existing configuration according to the information of the peer device and the information about the port, do not perform MEP configuration, and then confirm the CCM packet. If the CCM message is not matched with the existing MEP, and the CCM message is not matched with the preset CCM message, and the CCM message is not stored in the preset CCM information list, the CCM message is sent. The information of the peer device in the middle is stored in the list of the transit CCM information.
  • the processor 501 is further configured to use, in the CCM message, the MA.
  • the ID is the same as the configuration information of the configured MEP, it is determined to be a conflict;
  • the MD name of the MA ID of the configured MEP and the MA in the CCM message is the same, but the MD level of the configured MEP is different from the MD level in the CCM message.
  • a specific embodiment 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 connectivity detection CCM message to the second network device;
  • the second network device is configured to receive a CCM message of the peer device, and obtain the information about the port of the CCM message by the CCM message, and the information about the port includes: Receiving the identification information of the CCM message port and the virtual local area network label VLAN of the CCM message
  • the MEP configuration is completed according to the information of the peer device and the information of the port.
  • each module or unit included is only divided according to functional logic, but is not limited to the above division, as long as the corresponding function can be implemented; in addition, the specific name of each functional module is also They are only used to facilitate mutual differentiation and are not intended to limit the 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)

Abstract

本发明适用于通信领域，提供了一种MEP配置方法方法及以太网设备，所述方法包括：以太网设备接收CCM报文，解析该CCM报文获取该CCM报文中的配置信息和该CCM报文的虚拟局域网VLAN；以太网设备根据所述配置信息判断所述CCM报文是否为需要配置的MEP配置，如判断所述CCM报文是需要配置的MEP配置，则依据所述配置信息和所述CCM报文的VLAN完成所述MEP配置。本发明具体实施方式提供方法具有自动配置MEP配置的优点。

Description

一种MEP配置方法及网络设备 技术领域
本发明属于通信领域，尤其涉及一种MEP配置方法及网络设备。
 背景技术
以太网（英文：Ethernet）技术凭借其易用及成本低廉的特点，已经成为整个通讯网络中最重要的技术之一。随着电信网络的不断发展，以太网技术在企业网、城域网、广域网范围内都已经得到大规模应用。传统的以太网技术管理和维护手段非常有限，电信级的运营手段更是空白，运营商只能依靠简单网络管理协议（英文：simple network management protocol ，简称：SNMP）来管理以太网络，此种方式管理的以太网设备数量有限且需要大量的网际协议（英文：internet protocol，简称：IP）; 运营商为以太网的部署、管理与维护所增加的成本日益明显，所以填补以太网操作管理维护（英文：Operation Administration and Maintenance ，简称：OAM）协议空白势在必行。
以太网上的操作管理维护称为Ethernet OAM，相关的协议标准有IEEE 802.1ag。IEEE 802.1ag协议为连接故障管理协议，也称之为连接故障管理（英文：connectivity fault management，简称：CFM）协议。该协议具有业务级与网络级的端到端的故障检测、故障确认以及故障定位的能力。
现有的维护终端点（英文：maintenance end point ，简称：MEP）配置为手动配置，所以现有的MEP配置的比较复杂，为CFM的实际应用的广泛推广增加了难度。
 技术问题
本发明的目的在于提供一种MEP配置方法，用于对MEP进行配置。
技术解决方案
一方面，提供一种维护终端点MEP的配置方法，包括步骤：
接收对端设备的连通性检测CCM报文；
解析所述CCM报文获取所述对端设备的信息； 所述对端设备的信息包括：对端MEP的维护域MD级别、维护集标识MA ID 和CCM发送周期；
获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；
根据所述对端设备的信息和所述端口的信息完成MEP配置。
结合第一方面的一种维护终端点MEP的配置方法，在第一方面的第一种可选方案中，所述方法在根据所述对端设备的信息和所述端口的信息完成MEP配置之前还包括：
判断根据所述对端设备的信息和所述入端口信息完成MEP配置是否与已有的配置冲突；如根据所述对端设备的信息和所述入端口信息完成MEP配置与已有的配置不冲突，则根据所述对端设备的信息和所述入端口信息完成MEP配置。
结合第一方面的一种维护终端点MEP的配置方法，在第一方面的第二种可选方案中，所述根据所述对端设备的信息和所述端口的信息完成MEP配置具体包括：
依据所述对端设备的信息中的维护域MD类型、MD名称和MD级别创建MD；
依据所述对端设备的信息中的维护集MA的类型和MA名称创建MA；
将所述创建MA与所述VLAN tag关联起来；
依据所述对端设备的信息中的CCM报文发送周期配置所述创建MA中的CCM报文发送周期：
将对端设备的MEP ID和本端设备的MEP ID添加进入MEP 清单 List：
对预先设定的端口进行MEP的配置，并比较所述端口的标识信息与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下down，如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上up。
结合第一方面的第二种可选方案，在第一方面的第三种可选方案中，所述本端设备的MEP ID的获取方式具体为：
直接获取预先配置的本端设备的MEP ID或依据所述对端设备的MEP ID通过预先设定的算法计算出本端设备的MEP ID 。
结合第一方面的第一种可选方案，在第一方面的第四种可选方案中，所述方法还包括：
如根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置冲突时，不进行MEP配置，确认所述CCM报文匹配不到已有的MEP、确认所述CCM报文也匹配不上用户预先设定的预配置或确认所述CCM报文未存储在预先设置的过路CCM信息列表后，将所述CCM报文中的对端设备的信息存储在所述过路CCM信息列表内。
结合第一方面的第一种可选方案，在第一方面的第五种可选方案中，所述判断根据所述对端设备的信息和所述端口的信息完成MEP配置是否与已有的配置冲突具体包括：
如所述CCM报文中的MA ID与已配置的MEP的配置信息相同时，判断为冲突；
或已配置的MEP的MD级别中存在所述CCM报文中的MD的级别且MD的名称或类型不同时，判断为冲突；
或配置的MA 的数量已经超过上限时，判断为冲突；
或已配置的MEP的MA ID的MD名称与所述CCM报文中的MA ID中的MD的名称相同，但是已配置的MEP的MD级别与所述CCM报文中的MD级别不同时，判断为冲突。
第二方面，提供一种网络设备，包括：
接收单元，用于接收对端设备的连通性检测CCM报文；
解析单元，用于解析所述CCM报文获取所述对端设备的信息；所述对端设备的信息包括：对端MEP的维护域MD级别、维护集标识MA ID 和CCM发送周期；
路径获取单元，用于获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；
配置单元，用于根据所述对端设备的信息和所述端口的信息完成MEP配置。
结合第二方面的一种网络设备，在第二方面的第一种可选方案中，所述设备还包括：
判断单元，用于判断根据所述对端设备的信息和所述入端口信息完成MEP配置是否与已有的配置冲突。
结合第二方面的一种网络设备，在第二方面的第二种可选方案中，所述配置单元具体用于：
依据所述对端设备的信息中的MD类型、MD名称和MD级别自动创建MD；
依据所述对端设备的信息中的MA的类型和MA名称自动创建MA；
将所述创建MA与所述VLAN tag关联起来；
所述对端设备的信息中的CCM报文发送周期配置所述创建MA中的CCM报文发送周期：
将对端设备的MEP ID和所述网络设备的MEP ID添加进入MEP 清单 List：
对预先设定的端口进行MEP的配置，并比较所述端口的标识信息与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下down，如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上up。
结合第二方面的第二种可选方案，在第二方面的第三种可选方案中，所述网络设备还包括：
获取单元，用于直接获取预先配置的所述网络设备的MEP ID或依据所述对端设备的MEP ID通过预先设定的算法计算出所述网络设备的MEP ID 。
结合第二方面的第一种可选方案，在第二方面的第四种可选方案中，所述网络设备还包括：
过路处理单元，用于在所述判断单元判断出根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置冲突时，不进行MEP配置，确认所述CCM报文匹配不到已有的MEP、确认所述CCM报文也匹配不上用户预先设定的预配置或确认所述CCM报文未存储在预先设置的过路CCM信息列表后，将所述CCM报文中的对端设备的信息存储在所述过路CCM信息列表内。
结合第二方面的第一种可选方案，在第二方面的第五种可选方案中，所述判断单元具体用于：
如所述CCM报文中的MA ID与已配置的MEP的配置信息相同时，判断为冲突；
或已配置的MEP的MD级别中存在所述CCM报文中的MD的级别且MD的名称或类型不同时，判断为冲突；
或配置的MA 的数量已经超过上限时，判断为冲突；
或已配置的MEP的MA ID的MD名称与所述CCM报文中的MA ID中的MD的名称相同，但是已配置的MEP的MD级别与所述CCM报文中的MD级别不同时，判断为冲突。
第三方面，提供一种网络设备，所述网络设备包括：处理器、存储器、通信接口和总线。
所述通信接口，用于接收对端设备的连通性检测CCM报文；
所述处理器，用于解析所述CCM报文获取所述对端设备的信息获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；根据所述对端设备的信息和所述端口的信息完成MEP配置。
结合第三方面的一种网络设备，在第三方面的第一种可选方案中，所述处理器还用于
判断根据所述对端设备的信息和所述入端口信息完成MEP配置是否与已有的配置冲突；在判断出根据所述对端设备的信息和所述入端口信息完成MEP配置与已有的配置不冲突时，则根据所述对端设备的信息和所述端口的信息完成MEP配置。
结合第三方面的一种网络设备，在第三方面的第二种可选方案中，所述处理器具体用于依据所述对端设备的信息中的维护域MD类型、MD名称和MD级别自动创建MD；依据所述对端设备的信息中的维护集MA的类型和MA名称自动创建MA；自动将所述创建MA与所述VLAN tag关联起来；依据所述对端设备的信息中的CCM报文发送周期自动配置所述创建MA中的CCM报文发送周期： 将对端设备的MEP ID和所述网络设备400的MEP ID添加进入MEP List：对预先设定的端口进行MEP的配置，并比较所述入端口的标识与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下down，如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上up。
第四方面，提供一种网络系统，所述系统包括：第一网络设备和第二网络设备；
所述第一网络设备，用于向第二网络设备发送连通性检测CCM报文；
所述第二网络设备，用于接收对端设备的CCM报文；解析所述CCM报文获取所述对端设备的信息获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；根据所述对端设备的信息和所述端口的信息完成MEP配置。
 有益效果
在本发明实施例中，本发明提供的技术方案有MEP配置简单，效率高，应用广泛的优点。
附图说明
图1是本发明具体实施方式提供的一种CCM报文体结构示意图；
图2是本发明具体实施方式提供的MEP配置方法方法的流程图；
图3是本发明实施例一提供的维护终端点MEP的配置方法的流程图；
图4是本发明具体方式提供的一种网络设备的结构示意图；
图5是本发明具体实施方式提供的一种网络设备的硬件结构示意图。
 本发明的实施方式
为了使本发明的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
本发明具体实施方式提供一种维护终端点MEP的配置方法，该方法由本端以太网设备完成，该方法如图1所示，包括步骤：
101、接收对端设备的连通性检测CCM报文；
102、解析所述CCM报文获取所述对端设备的信息；
103、获取接收所述CCM报文端口的信息；
上述端口信息可以包括：端口的标识和所述CCM报文的虚拟局域网（英文：Virtual Local Area Network，简称：VLAN）标签 tag；
104、根据所述对端设备的信息和所述端口的信息完成MEP配置。
可选的，上述方法在104之间还包括：
判断根据所述对端设备的信息和所述端口的信息完成MEP配置是否与已有的配置冲突；如根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置不冲突，执行104。
CCM报文体结构如图1所示，其中标识（英文：Flags）字段又具体分为三个字段：对端故障指示（remote defect indication ，RDI）字段、保留字段和CCM周期字段；由图1可知，CCM报文携带了维护域（Maintenance Domain ，MD）的级别、MD类型、MD名称，维护集(Maintenance Association ,MA)的类型、MA名称，CCM发送周期。在MEP配置时，本端MEP和对端MEP的MD级别、MA ID 和CCM发送周期必须完全相同。那么也就意味着，对端MEP的MD级别、MA ID 和CCM发送周期完全可以通过解析本端MEP发送的标准的CCM报文来获取。上述MA ID可以包括：MD类型、MD名称，MA的类型和MA名称。另外，配置信息还可以包含除了MD级别、MA ID和CCM发送周期以外的信息，本发明具体实施方式对其他的配置信息（即除了MD级别、MA ID和CCM发送周期以外的信息）不限定。
本发明具体实施方式提供的方法中的本端以太网设备能够依据CCM报文自动完成MEP配置，所以其具有MEP配置简单，效率高，应用广泛的优点。
实施例一
本实施例一提供根据所述对端设备的信息和所述端口的信息完成MEP配置具体方法，如图2所示，包括：
201、开启CFM功能；
上述201仅仅是一个实施例的具体实现方式，如果已经开启了CFM功能，则无需执行201，直接执行202以及后续步骤。
202、依据所述对端设备的信息中的维护域MD类型、MD名称和MD级别自动创建MD；
203、依据所述对端设备的信息中的维护集MA的类型和MA名称自动创建MA；
204、自动将所述创建MA与所述VLAN tag关联起来；
205、依据所述对端设备的信息中的CCM报文发送周期自动配置所述创建MA中的CCM报文发送周期：
206、将对端设备的MEP ID和本端设备的MEP ID添加进入MEP 清单（List）：
207、对预先设定的端口进行MEP的配置，并比较所述入端口的标识与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下（down），如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上（up）。
上述将所述MEP的方向配置成上（UP）具体含义可以为：定义在网桥中的，向网桥的转发实体发送并从其接受CFM消息的MEP；
将所述MEP的方向配置成下（Down ）：定义在网桥中的，向物理媒介发送并从其接受CFM消息的MEP。
可选的，上述本端设备的MEP ID的获取方式具体为：
获取预先配置的本端设备的MEP ID或依据所述对端设备的MEP ID通过预先设定的算法计算出本端设备的MEP ID 。
上述依据预先设定的算法计算出本端设备的MEP ID适合1:1的模式，上述直接获取预先配置的本端设备的MEP ID适合N:1模式，其中N表示本端设备的数量。
上述预先设定的算法可以为能够依据该算法计算出与本端设备MEP ID不同的对端设备的MEP ID即可，例如，可以直接在对端设备的MEP ID加1，当然也可以为复杂一点的算法，例如：本端设备的MEP ID=[对端设备的MEP ID）%8191]+1；当然还可以为其他的计算方法，本发明具体实施方式对该算法并不做具体的限定。
可选的，上述方法还包括：
如根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置冲突时，不进行MEP配置，确认所述CCM报文匹配不到已有的MEP、确认所述CCM报文也匹配不上用户预先设定的预配置或确认所述CCM报文未存储在预先设置的过路CCM信息列表后，将所述CCM报文中的对端设备的信息存储在所述过路CCM信息列表内。上述过路CCM信息列表具体可以包括：过路CCM报文的信息，具体可以包括：过路CCM报文内包含的：MD的类型、名称、级别，MA的类型、名称，CCM报文发送周期，MEP ID等。
可选的，上述判断根据所述对端设备的信息和所述端口的信息完成MEP配置是否与已有的配置冲突具体包括：
如所述CCM报文中的MA ID与已配置的MEP的相应配置信息相同时，判断为冲突；
或已配置的MEP的MD级别中存在所述CCM报文中的MD的级别且MD的名称或类型不同时，判断为冲突；
或配置的MA 的数量已经超过上限时，判断为冲突；
或已配置的MEP的MA ID的MD名称与所述CCM报文中的MA ID中的MD的名称相同，但是已配置的MEP的MD级别与所述CCM报文中的MD级别不同时，判断为冲突。如相同，直接使用现有的MA ID即可。
实施例二
本发明实施例一提供一种维护终端点MEP的配置方法，本实施例实现的技术场景为：本实施例在本端设备与对端设备之间完成，该对端设备已经完成了MEP的配置，本端设备的用户预配置包括：指定的端口（当然在实际情况中，用户也可以有其他的预配置，例如预先配置MD的等级等）；上述对端设备完成MEP的配置方法具体可以为：开启CFM功能；创建维护域MD，要求指定MD的类型、MD名称、级别；创建维护集MA，要求指定MA的类型、MA名称；将该MA与VLAN tag关联起来；配置该MA内的CCM报文发送周期；配置该MA内的MEP List，要求用户指定对端设备的MEP ID并将对端设备的MEP ID加入MEP List，依据对端设备的MEP ID采用预先设定的算法计算出本端设备的MEP ID，并将本端设备的MEP ID也加入到MEP List。该方法如图3所示，包括：
步骤301、本端设备解析对端设备发送的CCM报文，并获取该CCM报文的传输路径信息。
上述解析内容包括但不限于：
解析接收到的CCM报文获取对端设备的信息，上述对端设备的信息包括但不限于：MD的类型、名称、级别，MA的类型、名称、CCM报文发送周期和对端设备的MEP ID；
根据CCM报文传输的路径，获取端口的信息，这些信息包括但不限于：CCM报文的入端口标识（例如入端口号，当然也可以为其他的类型的标识）、CCM报文的VLAN tag，根据CCM报文的VLAN tag，可以明确其检测的业务。可选的，不同厂商在完成MEP的配置时，还可能需要额外解析更多的信息，上述对端设备的信息是必须要解析获取的信息。
步骤302、本端设备根据上述解析获取的信息，进行判断比较，确认是否需要根据CCM报文内对端设备的信息和端口的信息配置MEP，
判断内容包括但不限于：
与本端设备上已存在的MEP做比较，用于判断该CCM报文是否是对端设备发送给本端设备的某个已配置完成的MEP的CCM报文。
比较内容包括但不限于：MD 的级别、类型、名称，MA的类型、名称。如果不一致，说明该报文不是本端设备发送给对端上某个已配置完成的MEP的报文；
与用户的预配置做比较，用于判断获取的对端设备信息是否符合用户的预配置中除了端口标识以外的其他配置（例如MD级别）。
冲突检查，防止与已存在配置冲突。
检查范围包括但不限于：MD 的级别、类型、名称，MA的类型、名称，检查这些内容是否与已存在的配置重复。如重复，则确定为冲突。
303、本端设备根据上述解析获取的信息及端口的信息完成本设备上的所有配置。
303的实现方式可以参见实施例一的描述，这里不在赘述。
实施例三
本发明实施例二提供一种维护终端点MEP的配置方法，本实施例实施的技术场景与实施例一相同，与实施例一不同点在于，本实施例中的本端设备还设置有过路CCM信息列表，该列表用于存储过路CCM报文，该过路CCM报文具体为，经过本端设备，但是不需要本端设备依据该CCM报文进行MEP配置的报文；本实施例在确定冲突以后，还包括如下步骤：
确认所述CCM报文匹配不到已有的MEP、确认所述CCM报文也匹配不上用户预先设定的预配置或确认所述CCM报文未存储在预先设置的过路CCM信息列表后，将所述CCM报文中的对端设备的信息存储在所述过路CCM信息列表内。
上述冲突以后的具体实现方式具体可以为：
运行了此机制的设备实时解析收到的CCM报文，解析的内容包括但不限于：MD的类型、名称、级别，MA的类型、名称，CCM报文发送周期，MEP ID等。
解析完成后，将报文信息与本端设备上已经存在的MEP配置进行比较，比较内容包含但不限于：MD的类型、名称、级别，MA的类型、名称，CCM报文发送周期等。
如果比较结果相同，说明此报文是对端设备发送给本端设备上某个已经配置完成的MEP，不需要加入过路CCM信息列表；如判断该CCM报文包含的内容存储于过路CCM信息列表，则判断该CCM报文属于过路报文，将该CCM透传即可，无需进行MEP配置。上述比较结果相同具体可以为，上述比较内容所包含的内容均相同。下述比较结果不同具体可以为：比较内容中任一个不同即为比较结果不同。
如果比较结果不同，再判断用户是否有预配置：
a、如果有预配置，且预配置中指定的MEP所在端口收到此CCM报文，并且与预配置中其他信息均匹配成功，认为此报文是本设备期望用于完成本端MEP配置的报文，设备将根据此报文的内容，完成本端MEP的配置，不需要加入过路CCM信息列表。
b、如果有预配置，且预配置中指定的MEP所在端口收到此CCM报文，但与其他预配置匹配失败，比如用户还指定了MD的名称，说明这不是发送给本设备的报文，如果过路CCM信息列表没有此报文信息，将此报文加入过路CCM信息列表，否则不需要重复加入过路CCM信息列表。
c、如果有预配置，但预配置中指定的MEP所在端口收不到此报文，说明这不是发送给本设备的报文，如果过路CCM信息列表没有此报文信息，将此报文加入过路CCM信息列表，否则不需要重复加入过路CCM信息列表。
d、如果没有预配置，说明这不是发送给本设备的报文，如果过路CCM信息列表没有此报文信息，将此报文加入过路CCM信息列表，否则不需要重复加入过路CCM信息列表。
过路CCM信息列表中的表项不会一直保存，会存在老化，老化机制这里不限制。例如直接设定时间阈值老化机制，当然也可以有其他的老化机制。
本发明具体实施方式还提供一种网络设备400，网络设备400包括：
接收单元401，用于接收对端设备的连通性检测CCM报文；
解析单元402，用于解析所述CCM报文获取所述对端设备的信息；
路径获取单元403，用于依据所述CCM报文的路径获取所述CCM报文的端口的信息，所述端口的信息包括：所述CCM报文的入端口的标识和所述CCM报文的VLAN tag；
判断单元404，用于判断根据所述对端设备的信息和所述端口的信息完成MEP配置是否与已有的配置冲突；
配置单元405，用于在所述判断单元判断出根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置不冲突时，则根据所述对端设备的信息和所述端口的信息完成MEP配置。
可选的，配置单元405具体用于：
开启CFM功能；
依据所述对端设备的信息中的维护域MD类型、MD名称和MD级别自动创建MD；
依据所述对端设备的信息中的维护集MA的类型和MA名称自动创建MA；
自动将所述创建MA与所述VLAN tag关联起来；
依据所述对端设备的信息中的CCM报文发送周期自动配置所述创建MA中的CCM报文发送周期：
将对端设备的MEP ID和所述网络设备400的MEP ID添加进入MEP List：
对预先设定的端口进行MEP的配置，并比较所述入端口的标识与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下down，如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上up。
可选的，网络设备400还包括：
获取单元406，用于直接获取预先配置的网络设备400的MEP ID或依据所述对端设备的MEP ID通过预先设定的算法计算出网络设备400的MEP ID 。
可选的，网络设备400还包括：
过路处理单元407，用于在所述判断单元判断出根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置冲突时，不进行MEP配置，然后确认所述CCM报文匹配不到已有的MEP、确认所述CCM报文也匹配不上用户预先设定的预配置和确认所述CCM报文未存储在预先设置的过路CCM信息列表后，将所述CCM报文中的对端设备的信息存储在所述过路CCM信息列表内。
可选的，判断单元404具体用于：
如所述CCM报文中的MA ID与已配置的MEP的配置信息相同时，判断为冲突；
或已配置的MEP的MD级别中存在所述CCM报文中的MD的级别且MD的名称或类型不同时，判断为冲突；
或配置的MA 的数量已经超过上限时，判断为冲突；
或已配置的MEP的MA ID的MD名称与所述CCM报文中的MA ID中的MD的名称相同，但是已配置的MEP的MD级别与所述CCM报文中的MD级别不同时，判断为冲突。
本发明具体实施方式还提供一种网络设备400，该网络设备400的硬件结构如图5所示，包括：处理器501、存储器502、通信接口503和总线504。
处理器501、存储器502、通信接口503通过总线504相互连接；总线504可以是工业标准架构体系（Industry Standard Architecture，ISA）总线或外围组件互联（英文：Peripheral Component Interconnect，简称：PCI）总线等。
上述的处理器501可以是通用处理器，包括中央处理器（英文：central processing unit，简称CPU）、网络处理器（英文：network processor，简称NP）等。
存储器502，用于存放程序5。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令，该程序用于指示处理器401发出计算机操作指令。存储器502可能包含高速随机存储器（英文：random-access memory，简称：RAM）存储器，也可能还包括非易失性存储器（non-volatile memory），例如至少一个磁盘存储器。
通信接口503，用于接收或发送报文。具体地，该报文可以为CCM报文，当然也可以为其他报文，具体地，该通信接口503可以为通信端口。
通信接口503接收对端设备的连通性检测CCM报文；
处理器501解析所述CCM报文获取所述对端设备的信息，依据所述CCM报文的路径获取所述CCM报文的端口的信息，所述端口的信息包括：所述CCM报文的入端口的标识和所述CCM报文的VLAN tag；判断根据所述对端设备的信息和所述端口的信息完成MEP配置是否与已有的配置冲突；在判断出根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置不冲突时，则根据所述对端设备的信息和所述端口的信息完成MEP配置。
处理器501具体用于开启CFM功能；依据所述对端设备的信息中的维护域MD类型、MD名称和MD级别自动创建MD；依据所述对端设备的信息中的维护集MA的类型和MA名称自动创建MA；自动将所述创建MA与所述VLAN tag关联起来；依据所述对端设备的信息中的CCM报文发送周期自动配置所述创建MA中的CCM报文发送周期： 将对端设备的MEP ID和所述网络设备400的MEP ID添加进入MEP List：对预先设定的端口进行MEP的配置，并比较所述入端口的标识与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下down，如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上up。
可选的，处理器501还直接获取预先配置的网络设备400的MEP ID或依据所述对端设备的MEP ID通过预先设定的算法计算出网络设备400的MEP ID。
可选的，处理器501还用于在判断出根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置冲突时，不进行MEP配置，然后确认所述CCM报文匹配不到已有的MEP、确认所述CCM报文也匹配不上用户预先设定的预配置和确认所述CCM报文未存储在预先设置的过路CCM信息列表后，将所述CCM报文中的对端设备的信息存储在所述过路CCM信息列表内。
可选的，处理器501还用于如所述CCM报文中的MA ID与已配置的MEP的配置信息相同时，判断为冲突；
或已配置的MEP的MD级别中存在所述CCM报文中的MD的级别且MD的名称或类型不相同时，判断为冲突；
或配置的MA 的数量已经超过上限时，判断为冲突；
或已配置的MEP的MA ID的MD名称与所述CCM报文中的MA ID中的MD的名称相同，但是已配置的MEP的MD级别与所述CCM报文中的MD级别不同时，判断为冲突。
本发明具体实施方式提供一种网络系统，所述系统包括：第一网络设备和第二网络设备；
所述第一网络设备，用于向第二网络设备发送连通性检测CCM报文；
所述第二网络设备，用于接收对端设备的CCM报文；解析所述CCM报文获取所述对端设备的信息获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；根据所述对端设备的信息和所述端口的信息完成MEP配置。
上述单元和系统实施例中，所包括的各个模块或单元只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，各功能模块的具体名称也只是为了便于相互区分，并不用于限制本发明的保护范围。
本领域技术人员可以理解，本发明实施例提供的技术方案全部或部分步骤是可以通过程序指令相关的硬件来完成。比如可以通过计算机运行程来完成。该程序可以存储在可读取存储介质，例如，随机存储器、磁盘、光盘等。
以上所述仅为本发明的较佳实施例而已，并不用以限制本发明，凡在本发明的具体实施方式之内所作的等同替换或改进等，均应包含在本发明的保护范围之内。

Claims (16)

  1. 一种维护终端点MEP的配置方法，其特征在于，包括步骤：
    接收对端设备的连通性检测CCM报文；
    解析所述CCM报文获取所述对端设备的信息； 所述对端设备的信息包括：对端MEP的维护域MD级别、维护集标识MA ID 和CCM发送周期；
    获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；
    根据所述对端设备的信息和所述端口的信息完成MEP配置。
  2. 根据权利要求1所述的方法，其特征在于，所述方法在根据所述对端设备的信息和所述端口的信息完成MEP配置之前还包括：
    判断根据所述对端设备的信息和所述入端口信息完成MEP配置是否与已有的配置冲突；如根据所述对端设备的信息和所述入端口信息完成MEP配置与已有的配置不冲突，则根据所述对端设备的信息和所述入端口信息完成MEP配置。
  3. 根据权利要求1所述的方法，其特征在于，所述根据所述对端设备的信息和所述端口的信息完成MEP配置具体包括：
    依据所述对端设备的信息中的维护域MD类型、MD名称和MD级别创建MD；
    依据所述对端设备的信息中的维护集MA的类型和MA名称创建MA；
    将所述创建MA与所述VLAN tag关联起来；
    依据所述对端设备的信息中的CCM报文发送周期配置所述创建MA中的CCM报文发送周期：
    将对端设备的MEP ID和本端设备的MEP ID添加进入MEP 清单 List：
    对预先设定的端口进行MEP的配置，并比较所述端口的标识信息与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下down，如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上up。
  4. 根据权利要求3所述的方法，其特征在于，所述本端设备的MEP ID的获取方式具体为：
    直接获取预先配置的本端设备的MEP ID或依据所述对端设备的MEP ID通过预先设定的算法计算出本端设备的MEP ID 。
  5. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    如根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置冲突时，不进行MEP配置，确认所述CCM报文匹配不到已有的MEP、确认所述CCM报文也匹配不上用户预先设定的预配置或确认所述CCM报文未存储在预先设置的过路CCM信息列表后，将所述CCM报文中的对端设备的信息存储在所述过路CCM信息列表内。
  6. 根据权利要求2所述的方法，其特征在于，所述判断根据所述对端设备的信息和所述端口的信息完成MEP配置是否与已有的配置冲突具体包括：
    如所述CCM报文中的MA ID与已配置的MEP的配置信息相同时，判断为冲突；
    或已配置的MEP的MD级别中存在所述CCM报文中的MD的级别且MD的名称或类型不同时，判断为冲突；
    或配置的MA 的数量已经超过上限时，判断为冲突；
    或已配置的MEP的MA ID的MD名称与所述CCM报文中的MA ID中的MD的名称相同，但是已配置的MEP的MD级别与所述CCM报文中的MD级别不同时，判断为冲突。
  7. 一种网络设备，其特征在于，包括：
    接收单元，用于接收对端设备的连通性检测CCM报文；
    解析单元，用于解析所述CCM报文获取所述对端设备的信息；所述对端设备的信息包括：对端MEP的维护域MD级别、维护集标识MA ID 和CCM发送周期；
    路径获取单元，用于获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；
    配置单元，用于根据所述对端设备的信息和所述端口的信息完成MEP配置。
  8. 根据权利要求7所述的设备，其特征在于，所述设备还包括：
    判断单元，用于判断根据所述对端设备的信息和所述入端口信息完成MEP配置是否与已有的配置冲突。
  9. 根据权利要求7所述的网络设备，其特征在于，所述配置单元具体用于：
    依据所述对端设备的信息中的MD类型、MD名称和MD级别自动创建MD；
    依据所述对端设备的信息中的MA的类型和MA名称自动创建MA；
    将所述创建MA与所述VLAN tag关联起来；
    所述对端设备的信息中的CCM报文发送周期配置所述创建MA中的CCM报文发送周期：
    将对端设备的MEP ID和所述网络设备的MEP ID添加进入MEP 清单 List：
    对预先设定的端口进行MEP的配置，并比较所述端口的标识信息与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下down，如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上up。
  10. 根据权利要求9所述的网络设备，其特征在于，所述网络设备还包括：
    获取单元，用于直接获取预先配置的所述网络设备的MEP ID或依据所述对端设备的MEP ID通过预先设定的算法计算出所述网络设备的MEP ID 。
  11. 根据权利要求8所述的网络设备，其特征在于，所述网络设备还包括：
    过路处理单元，用于在所述判断单元判断出根据所述对端设备的信息和所述端口的信息完成MEP配置与已有的配置冲突时，不进行MEP配置，确认所述CCM报文匹配不到已有的MEP、确认所述CCM报文也匹配不上用户预先设定的预配置或确认所述CCM报文未存储在预先设置的过路CCM信息列表后，将所述CCM报文中的对端设备的信息存储在所述过路CCM信息列表内。
  12. 根据权利要求8所述的网络设备，其特征在于，所述判断单元具体用于：
    如所述CCM报文中的MA ID与已配置的MEP的配置信息相同时，判断为冲突；
    或已配置的MEP的MD级别中存在所述CCM报文中的MD的级别且MD的名称或类型不同时，判断为冲突；
    或配置的MA 的数量已经超过上限时，判断为冲突；
    或已配置的MEP的MA ID的MD名称与所述CCM报文中的MA ID中的MD的名称相同，但是已配置的MEP的MD级别与所述CCM报文中的MD级别不同时，判断为冲突。
  13. 一种网络设备，其特征在于，所述网络设备包括：处理器、存储器、通信接口和总线。
    所述通信接口，用于接收对端设备的连通性检测CCM报文；
    所述处理器，用于解析所述CCM报文获取所述对端设备的信息获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；根据所述对端设备的信息和所述端口的信息完成MEP配置。
  14. 根据权利要求13所述的设备，其特征在于，所述处理器还用于
    判断根据所述对端设备的信息和所述入端口信息完成MEP配置是否与已有的配置冲突；在判断出根据所述对端设备的信息和所述入端口信息完成MEP配置与已有的配置不冲突时，则根据所述对端设备的信息和所述端口的信息完成MEP配置。
  15. 根据权利要求13所述的网络设备，其特征在于，所述处理器具体用于依据所述对端设备的信息中的维护域MD类型、MD名称和MD级别自动创建MD；依据所述对端设备的信息中的维护集MA的类型和MA名称自动创建MA；自动将所述创建MA与所述VLAN tag关联起来；依据所述对端设备的信息中的CCM报文发送周期自动配置所述创建MA中的CCM报文发送周期： 将对端设备的MEP ID和所述网络设备400的MEP ID添加进入MEP List：对预先设定的端口进行MEP的配置，并比较所述入端口的标识与预先设定的端口的标识是否相同，如所述入端口的标识与预先设定的端口的标识相同，则将MEP的方向配置成下down，如所述入端口的标识与预先设定的端口的标识不相同，则将所述MEP的方向配置成上up。
  16. 一种网络系统，其特征在于，所述系统包括：第一网络设备和第二网络设备；
    所述第一网络设备，用于向第二网络设备发送连通性检测CCM报文；
    所述第二网络设备，用于接收对端设备的CCM报文；解析所述CCM报文获取所述对端设备的信息获取接收所述CCM报文端口的信息，所述端口的信息包括：接收所述CCM报文端口的标识信息和所述CCM报文的虚拟局域网标签VLAN tag；根据所述对端设备的信息和所述端口的信息完成MEP配置。
PCT/CN2013/077349 2013-06-17 2013-06-17 一种mep配置方法及网络设备 WO2014201613A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP13883350.4A EP2840738B1 (en) 2013-06-17 2013-06-17 Mep configuration method and network device
CN201380002617.0A CN104471897B (zh) 2013-06-17 2013-06-17 一种mep配置方法及网络设备
ES13883350.4T ES2617974T3 (es) 2013-06-17 2013-06-17 Método de configuración de MEP y dispositivo de red
PCT/CN2013/077349 WO2014201613A1 (zh) 2013-06-17 2013-06-17 一种mep配置方法及网络设备
US14/971,091 US9985862B2 (en) 2013-06-17 2015-12-16 MEP configuration method and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/077349 WO2014201613A1 (zh) 2013-06-17 2013-06-17 一种mep配置方法及网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/971,091 Continuation US9985862B2 (en) 2013-06-17 2015-12-16 MEP configuration method and network device

Publications (1)

Publication Number Publication Date
WO2014201613A1 true WO2014201613A1 (zh) 2014-12-24

Family

ID=52103786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/077349 WO2014201613A1 (zh) 2013-06-17 2013-06-17 一种mep配置方法及网络设备

Country Status (5)

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

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

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101662383A (zh) * 2009-09-17 2010-03-03 杭州华三通信技术有限公司 一种配置维护端点的方法及设备
US20100238808A1 (en) * 2009-03-23 2010-09-23 Salam Samer M Connectivity fault management (cfm) auto-provisioning using virtual private lan service (vpls) auto-discovery
CN102215130A (zh) * 2011-06-16 2011-10-12 杭州华三通信技术有限公司 一种cfd协议配置方法及其装置
US8175008B1 (en) * 2008-06-17 2012-05-08 Juniper Networks, Inc. Auto MEP ID assignment within CFM maintenance association

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100536409C (zh) 2005-04-19 2009-09-02 华为技术有限公司 一种环回的实现方法
EP2595350B1 (en) * 2007-08-01 2018-10-17 Telefonaktiebolaget LM Ericsson (publ) GMPLS based OAM provisioning
JP4946851B2 (ja) * 2007-12-19 2012-06-06 富士通株式会社 フレーム転送方法及びフレーム転送装置
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
US8416696B2 (en) * 2010-01-04 2013-04-09 Cisco Technology, Inc. CFM for conflicting MAC address notification
US9264328B2 (en) * 2011-11-07 2016-02-16 Ciena Corporation Systems and methods for dynamic operations, administration, and management

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8175008B1 (en) * 2008-06-17 2012-05-08 Juniper Networks, Inc. Auto MEP ID assignment within CFM maintenance association
US20100238808A1 (en) * 2009-03-23 2010-09-23 Salam Samer M Connectivity fault management (cfm) auto-provisioning using virtual private lan service (vpls) auto-discovery
CN101662383A (zh) * 2009-09-17 2010-03-03 杭州华三通信技术有限公司 一种配置维护端点的方法及设备
CN102215130A (zh) * 2011-06-16 2011-10-12 杭州华三通信技术有限公司 一种cfd协议配置方法及其装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2840738A4 *

Also Published As

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

Similar Documents

Publication Publication Date Title
WO2014121502A1 (zh) 在基站中，一种开站配置方法、基站及服务器
WO2012141556A2 (en) Machine-to-machine node erase procedure
WO2023033585A1 (ko) 분산 게이트웨이 환경에 최적화된 터널링 및 게이트웨이 접속 시스템 및 그에 관한 방법
WO2014201613A1 (zh) 一种mep配置方法及网络设备
WO2015072709A1 (ko) Sdn에서 네트워크 장애 해소를 위한 컨트롤러 및 스위치의 동작 방법과, 이를 위한 컨트롤러 및 스위치
WO2014209075A1 (ko) 인터넷 프로토콜을 이용한 서비스를 위한 다중 연결 시스템 및 방법
WO2013129832A1 (en) Method for reporting radio link failure information
WO2014082261A1 (zh) 一种以太端口自协商的方法及通信设备
WO2016144068A1 (ko) 이동 통신 시스템에서 사용자 체감 품질 관리 방법 및 장치
WO2020042464A1 (zh) 数据交互方法、装置、设备及可读存储介质
WO2018117279A1 (ko) 네트워크 장치 및 네트워크 장치의 전송 선택 방법
WO2015078008A1 (zh) 一种链路发现的方法、系统及设备
WO2016065619A1 (zh) 一种数据流量管理方法及装置
WO2011019144A2 (ko) 전자 패치 장치, 네트워크 시스템 및 네트워크 시스템에서의 동작 방법
WO2015024167A1 (zh) 一种处理用户报文的方法及转发面设备
WO2015062052A1 (zh) 一种m2m数据的查询、调用方法、查询、调用设备及系统
WO2018117280A1 (ko) 네트워크 장치 및 네트워크 장치의 큐 관리 방법
WO2018079948A2 (ko) 단말장치 및 기지국장치와, qos 제어방법
WO2017113618A1 (zh) 一种基于条件接受模块网络数据分发处理的方法和装置
WO2018184302A1 (zh) 数据转发方法、系统、虚拟负载均衡器及可读存储介质
WO2017131285A1 (ko) 컨테이너 네트워크 관리 시스템 및 컨테이너 네트워킹 방법
WO2020130158A1 (ko) 오픈 프론트홀 네트워크 시스템
WO2015080525A1 (ko) Sdn 환경에서 트래픽의 동적 제어를 위한 방법 및 장치
WO2016195158A1 (ko) 오버레이 sdn 망의 브릿지 도메인 확장 방법
WO2014079006A1 (zh) 一种ospf报文的流量控制方法及装置

Legal Events

Date Code Title Description
REEP Request for entry into the european phase

Ref document number: 2013883350

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013883350

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13883350

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE