WO2020147683A1 - 一种连通性检测会话的创建方法、网络设备和系统 - Google Patents

一种连通性检测会话的创建方法、网络设备和系统 Download PDF

Info

Publication number
WO2020147683A1
WO2020147683A1 PCT/CN2020/071795 CN2020071795W WO2020147683A1 WO 2020147683 A1 WO2020147683 A1 WO 2020147683A1 CN 2020071795 W CN2020071795 W CN 2020071795W WO 2020147683 A1 WO2020147683 A1 WO 2020147683A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
session
network
connectivity detection
integrated multicast
Prior art date
Application number
PCT/CN2020/071795
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 EP20741320.4A priority Critical patent/EP3893447A4/en
Publication of WO2020147683A1 publication Critical patent/WO2020147683A1/zh
Priority to US17/375,348 priority patent/US11863394B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • 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
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
    • H04L12/1877—Measures taken prior to transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's

Definitions

  • This application relates to the field of communication technology, and in particular to a configuration method and controller.
  • Ethernet virtual private network (ethernet virtual private network, EVPN) is a virtual private network (virtual private network, VPN) technology used to realize layer 2 network intercommunication.
  • EVPN extends the border gateway (border gateway protocol, BGP) protocol or multi-protocol label switching (multi-protocol label switching, MPLS) protocol to add several new routing types for use at the edge (provider edge, PE) of different operators.
  • BGP border gateway protocol
  • MPLS multi-protocol label switching
  • the media access control (MAC) address and internet protocol (IP) address of the host are notified between the devices.
  • the network structure of EVPN is similar to the network structure of BGP or MPLS.
  • Each EVPN site communicates with each other at Layer 2, and the PE device establishes an EVPN instance to access the customer edge (CE) device of each site.
  • CE customer edge
  • the network structure of EVPN mainly includes two kinds, one is virtual private wire service (VPWS), and the other is ethernet local area network (E-LAN).
  • VPWS is also called E-LINE.
  • E-LINE is a Layer 2 VPN service based on MPLS. It refers to a two-way intercommunication relationship between two PEs and is a point-to-point communication service.
  • E-LAN provides a multipoint-to-multipoint Layer 2 VPN service. In E-LAN, packets are transmitted transparently, so that the communication between multiple PEs is like in the same LAN.
  • E-LINE and E-LAN require connection fault management (connectivity fault management, CFM).
  • CFM connection fault management
  • E-LINE mainly configures matching CFM instances for the PEs at both ends of E-LINE communication through the network administrator, so that when the local PE sends a CFM session creation message to the opposite PE, the opposite PE can communicate with the local PE Create a CFM session.
  • CFM solution used by the above-mentioned E-LINE is used, it is necessary to configure a paired CFM instance between every two PEs, which is a huge workload and time-consuming configuration.
  • the embodiments of the present application provide a method, network device, and system for establishing a connectivity detection session, which are used to create a connectivity detection session in an EVPN network.
  • the first aspect of the present application provides a method for creating a connectivity detection session, which is used in an EVPN network.
  • the EVPN network includes a first network device and a second network device. The method includes:
  • the first network device receives a connectivity detection session creation message from the second network device, and the connectivity detection session creation message carries the integrated multicast routing of the second network device and the session information of the second network device; the first network device It is determined that the integrated multicast route of the second network device is included in the local integrated multicast routing table; the first network device creates a connectivity detection session with the second network device according to the session information of the second network device.
  • the first network device When the first network device is added to the EVPN network, it is only necessary to configure the integrated multicast routing table for the first network device, so that when the connection creation message from the second network device is received, the The creation message of the connectivity detection session of the second network device carries the integrated multicast route of the second network device and the session information of the second network device, and the local integrated multicast routing table includes the integrated multicast route of the second network device. Broadcast routing, the first network device can create a connectivity detection session with the second network device based on the session information of the second network device, so there is no need to communicate between the first network device and each existing network device in the EVPN network. Once the instance of the connectivity detection session is configured, the configuration of the instance of the connectivity detection session between the first network device and the original network devices in the EVPN network can be implemented, which simplifies the configuration process.
  • the first network device is a PE to provide a solution for establishing a connectivity detection session between each PE in EVPN 100. In this solution, there is no need to communicate between the first network device and EVPN 100. Some instances of connectivity detection sessions are configured one by one between each network device, which simplifies the configuration process.
  • that the first network device receives the connection detection session creation message from the second network device includes: the first network device receives the connectivity detection sent by the second network device through broadcast or multicast.
  • the creation message of the conversation Due to the broadcast or multicast method, the second network device only needs to send a connection detection session creation message, instead of sending it to each network device in the EVPN network separately, which reduces the burden on transmission resources and improves Transmission efficiency.
  • the method before the first network device receives the establishment message of the connectivity detection session from the second network device, the method further includes: the first network device obtains the integrated multicast routing table, and the integrated multicast routing table includes the second network device. Integrated multicast routing of network equipment. Since the integrated multicast routing table includes the integrated multicast routing of the second network device, the first network device can therefore determine that the first network device and the second network device belong to the same EVPN network, thereby determining that a connectivity detection session needs to be created.
  • the manner in which the first network device obtains the integrated multicast routing table may include:
  • the first network device obtains the integrated multicast routing table according to the configuration of the command line received locally, so the network administrator can input the integrated multicast routing table locally on the network device.
  • control and management device receives and sends the integrated multicast routing table to the first network device, and the first network device saves the integrated multicast routing table, so the network administrator can remotely set the integrated multicast routing table through the control and management device.
  • the first network device receives the integrated multicast route of the second network device advertised by the second network device, and the first network device stores the integrated multicast route of the second network device in the integrated multicast routing table, and no pre-editing is required
  • the integrated multicast routing table is well integrated, and the integrated multicast routing table can be dynamically and automatically updated to meet the needs of its own integrated multicast routing to inform other network devices in the EVPN network when new network devices enter the network, and reduce network administrators.
  • the workload has improved work efficiency.
  • the connectivity detection session includes a connection fault management (connectivity fault management, CFM) session to perform fault detection and management on the connection between the first network device and the second network device.
  • CFM connection fault management
  • the tag-length-value (TLV) field in the creation message of the connectivity detection session includes the integrated multicast route of the second network device, and the TLV field includes the type, length, and value.
  • the type is used to indicate that the type of the TLV field is integrated multicast routing
  • the length is used to indicate the length of the TLV field
  • the value is the integrated multicast routing of the second network device. Therefore, the position of the integrated multicast route in the creation message of the connectivity detection session can be determined, so that the first network device can obtain the integrated multicast route from the value of the TLV field in the creation message of the connectivity detection session.
  • the session information of the second network device includes the maintenance alliance edge node identification (maintenance association end point ID, MEP ID) or the session ID Session ID of the second network device.
  • MEP ID maintenance alliance edge node identification
  • the first network device and the second network device can negotiate and establish the connectivity detection session.
  • the method also includes:
  • the first network device obtains the MEP ID range or Session ID range.
  • the MEP ID range includes the MEP ID of the second network device, or the Session ID range includes the Session ID of the second network device.
  • the first network device is based on the session information of the second network device. Before establishing a connectivity detection session with the second network device, it also includes: the first network device determines that the MEP ID of the second network device is within the MEP ID range; or, the first network device determines that the Session ID of the second network device is in the Session Within the ID range, so that the first network device can limit the network device with a specific MEP ID or Session ID to create a connectivity detection session.
  • the first network device determines the fault statistics message according to the MEP ID of the first network device and the MEP ID of the second network device
  • the sender and receiver of the fault statistics message or the first network device determines the sender and receiver of the fault statistics message according to the Session ID of the first network device and the Session ID of the second network device, where the sender is the first network device and One of the second network devices, and the receiver is one of the first network device and the second network device that is different from the sender.
  • the second aspect of the present application provides a method for creating a connectivity detection session, which is used in an EVPN network.
  • the EVPN network includes a first network device and a second network device. The method includes:
  • the second network device obtains the integrated multicast route of the second network device; the second network device sends a connectivity detection session creation message to the first network device, and the connectivity detection session creation message carries the integrated multicast route of the second network device And session information, session information is used to create a connectivity detection session.
  • the first network device When the first network device is added to the EVPN network, it is only necessary to configure the integrated multicast routing table for the first network device, so that when the connection creation message from the second network device is received, the The creation message of the connectivity detection session of the second network device carries the integrated multicast route of the second network device and the session information of the second network device, and the local integrated multicast routing table includes the integrated multicast route of the second network device. Broadcast routing, the first network device can create a connectivity detection session with the second network device based on the session information of the second network device, so there is no need to communicate between the first network device and each existing network device in the EVPN network. Once the instance of the connectivity detection session is configured, the configuration of the instance of the connectivity detection session between the first network device and the original network devices in the EVPN network can be implemented, which simplifies the configuration process.
  • obtaining the integrated multicast route by the second network device includes:
  • the second network device obtains the integrated multicast routing of the second network device according to the configuration of the command line, so the network administrator can input the integrated multicast routing table locally on the network device.
  • the second network device receives the integrated multicast route sent by the control and management device as the integrated multicast route of the second network device, so the network administrator can remotely set the integrated multicast routing table through the control and management device.
  • the integrated multicast routing table does not need to be edited in advance, and the integrated multicast routing table can be dynamically and automatically updated to satisfy the new network
  • the device enters the network its own integrated multicast routing needs to inform other network devices in the EVPN network, while reducing the workload of network administrators and improving work efficiency.
  • the second network device sending the connectivity detection session creation message to the first network device includes: the second network device broadcasts or multicasts the connectivity detection session creation message to each network device in the EVPN network . Therefore, the second network device only needs to send one message instead of sending one message to each network device in the EVPN network, which reduces the burden of transmission resources and improves transmission efficiency.
  • the connectivity detection session includes a CFM session, so fault detection and management can be performed on the connection between the first network device and the second network device.
  • the TLV field in the creation message of the connectivity detection session includes the integrated multicast route of the second network device, and the TLV field includes type, length, and value, where the type is used to indicate the type of the TLV field
  • the length is used to indicate the length of the TLV field
  • the value is the integrated multicast routing of the second network device.
  • the session information of the second network device includes the MEP ID or Session ID of the second network device, so that the first network device and the second network device can negotiate and create a connectivity detection session.
  • the second network device after the second network device sends a connectivity detection session creation message to each network device in the EVPN, the second network device receives the connectivity detection session response packet sent by the first network device, and connects
  • the response message of the sex detection session includes the session information of the first network device, and the sender and receiver of the fault statistics message are determined according to the session information of the first network device and the session information of the second network device, where the sender is One of the first network device and the second network device, and the receiver is one of the first network device and the second network device different from the sender.
  • the third aspect of this application provides a network device used as the first network device, including:
  • Transceiver memory and processor.
  • the processor is used to execute computer-readable instructions in the memory to perform the following operations:
  • the connectivity detection session creation message carries the integrated multicast routing of the second network device and the session information of the second network device; determine the local integrated multicast routing table It includes the integrated multicast routing of the second network device; and creates a connectivity detection session with the second network device according to the session information of the second network device.
  • the first network device When the first network device is added to the EVPN network, it is only necessary to configure the integrated multicast routing table for the first network device, so that when the connection creation message from the second network device is received, the The creation message of the connectivity detection session of the second network device carries the integrated multicast route of the second network device and the session information of the second network device, and the local integrated multicast routing table includes the integrated multicast route of the second network device. Broadcast routing, the first network device can create a connectivity detection session with the second network device based on the session information of the second network device, so there is no need to communicate between the first network device and each existing network device in the EVPN network. Once the instance of the connectivity detection session is configured, the configuration of the instance of the connectivity detection session between the first network device and the original network devices in the EVPN network can be implemented, which simplifies the configuration process.
  • the first network device is a PE to provide a solution for establishing a connectivity detection session between each PE in the EVPN network. In this solution, there is no need to communicate between the first network device and the EVPN network. Some instances of connectivity detection sessions are configured one by one between each network device, which simplifies the configuration process.
  • the processor receiving the connectivity detection session creation message from the second network device includes: the processor receiving the connectivity detection session creation message sent by the second network device in a broadcast or multicast manner .
  • the second network device only needs to send one message, instead of sending one message to each network device in the EVPN network, which reduces the burden of transmission resources and improves transmission efficiency.
  • the processor is further configured to: obtain an integrated multicast routing table, where the integrated multicast routing table includes the integrated multicast routing of the second network device. Therefore, the processor can determine that the first network device and the second network device belong to the same EVPN network, thereby determining that a connectivity detection session needs to be established.
  • the manner in which the processor obtains the integrated multicast routing table may include:
  • the integrated multicast routing table is obtained according to the configuration of the command line received locally, so the network administrator can input the integrated multicast routing table locally on the network device.
  • the first network device saves the integrated multicast routing table, so the network administrator can remotely set the integrated multicast routing table through the control and management device.
  • the routing table can dynamically and automatically update the integrated multicast routing table to meet the needs of its own integrated multicast routing to notify other network devices in the EVPN network when new network devices enter the network, and reduce the workload of network administrators. Improve work efficiency.
  • the connectivity detection session includes a connection failure management CFM session to perform failure detection and management on the connection between the first network device and the second network device.
  • the TLV field in the creation message of the connectivity detection session includes the integrated multicast route of the second network device, and the TLV field includes type, length, and value, where the type is used to indicate the type of the TLV field
  • the length is used to indicate the length of the TLV field
  • the value is the integrated multicast routing of the second network device.
  • the session information of the second network device includes the MEP ID or Session ID of the second network device, so that the first network device and the second network device can negotiate and create a connectivity detection session.
  • the processor is also used to:
  • the MEP ID range includes the MEP ID of the second network device, or the Session ID range includes the Session ID of the second network device.
  • the processor is further configured to: determine that the MEP ID of the second network device is within the MEP ID range; or, determine the session of the second network device The ID is within the session ID range, so that the first network device can limit the network device with a specific MEP ID or Session ID to create a connectivity detection session.
  • the processor is further configured to perform the following operations: according to the MEP ID of the first network device and the MEP ID of the second network device Determine the sender and receiver of the fault statistics message, or determine the sender and receiver of the fault statistics message according to the Session ID of the first network device and the Session ID of the second network device, where the sender is the first network device And one of the second network device, the receiver is one of the first network device and the second network device different from the sender.
  • the fourth aspect of the present application provides a network device used as a second network device, and the second network device includes:
  • Transceiver memory and processor.
  • the processor is used to execute computer-readable instructions in the memory to perform the following operations:
  • the connectivity detection session creation message carries the integrated multicast routing and session information of the second network device, and the session information is used for Create a connectivity detection session.
  • the first network device When the first network device is added to the EVPN network, it is only necessary to configure the integrated multicast routing table for the first network device, so that when the connection creation message from the second network device is received, the The creation message of the connectivity detection session of the second network device carries the integrated multicast route of the second network device and the session information of the second network device, and the local integrated multicast routing table includes the integrated multicast route of the second network device. Broadcast routing, the first network device can create a connectivity detection session with the second network device based on the session information of the second network device, so there is no need to communicate between the first network device and each existing network device in the EVPN network. Once the instance of the connectivity detection session is configured, the configuration of the instance of the connectivity detection session between the first network device and the original network devices in the EVPN network can be implemented, which simplifies the configuration process.
  • the network device may include a PE to provide a solution for establishing a connectivity detection session between each PE in the EVPN network.
  • a PE to provide a solution for establishing a connectivity detection session between each PE in the EVPN network.
  • connectivity detection sessions are configured one by one between each network device, which simplifies the configuration process.
  • obtaining the integrated multicast route by the second network device includes:
  • the second network device obtains the integrated multicast routing of the second network device according to the configuration of the command line, so the network administrator can input the integrated multicast routing table locally on the network device.
  • the second network device receives the integrated multicast route sent by the control and management device as the integrated multicast route of the second network device, so the network administrator can remotely set the integrated multicast routing table through the control and management device.
  • the integrated multicast routing table does not need to be edited in advance, and the integrated multicast routing table can be dynamically and automatically updated to satisfy the new network
  • the device enters the network its own integrated multicast routing needs to inform other network devices in the EVPN network, while reducing the workload of network administrators and improving work efficiency.
  • the processor sending the connectivity detection session creation message to the first network device includes: broadcasting or multicasting the connectivity detection session creation message to each network device in the EVPN network. Therefore, the second network device only needs to send one packet, and does not need to send to each network device in the EVPN network, which reduces the burden of transmission resources and improves transmission efficiency.
  • the connectivity detection session includes a CFM session to perform fault detection and management on the connection between the first network device and the second network device.
  • the TLV field in the creation message of the connectivity detection session includes the integrated multicast route of the second network device, and the TLV field includes type, length, and value, where the type is used to indicate the type of the TLV field
  • the length is used to indicate the length of the TLV field
  • the value is the integrated multicast routing of the second network device.
  • the session information of the second network device includes the MEP ID or Session ID of the second network device. Therefore, the first network device can limit the network devices with a specific MEP ID or Session ID to establish connectivity detection. Conversation.
  • the second network device after the second network device sends a connectivity detection session creation message to each network device in the EVPN, the second network device receives the connectivity detection session response packet sent by the first network device, and connects
  • the response message of the sex detection session includes the session information of the first network device, and the sender and receiver of the fault statistics message are determined according to the session information of the first network device and the session information of the second network device, where the sender is One of the first network device and the second network device, and the receiver is one of the first network device and the second network device different from the sender.
  • the fifth aspect of the present application also provides a computer-readable medium, including instructions, which when run on a computer, cause the computer to execute the methods described in the various implementation manners in the first aspect.
  • the sixth aspect of the present application also provides a computer-readable medium, including instructions, which when run on a computer, cause the computer to execute the methods described in the various implementation manners in the second aspect.
  • the seventh aspect of the present application also provides a system, including the first network device described in the various implementation manners of the third aspect and the second network device described in the various implementation manners of the fourth aspect.
  • the first network device When the first network device is added to the EVPN network, it is only necessary to configure the integrated multicast routing table for the first network device, so that when the connection creation message from the second network device is received, the The creation message of the connectivity detection session of the second network device carries the integrated multicast route of the second network device and the session information of the second network device, and the local integrated multicast routing table includes the integrated multicast route of the second network device. Broadcast routing, the first network device can create a connectivity detection session with the second network device based on the session information of the second network device, so there is no need to communicate between the first network device and each existing network device in the EVPN network. Once the instance of the connectivity detection session is configured, the configuration of the instance of the connectivity detection session between the first network device and the original network devices in the EVPN network can be implemented, which simplifies the configuration process.
  • Figure 1 is an EVPN 100 in an embodiment of this application
  • Figure 2-1 is a method for establishing a connectivity detection session in an embodiment of this application
  • FIG 2-2 is a schematic diagram of TLV in an embodiment of this application.
  • Figure 3 is a schematic diagram of a first network device in an embodiment of the application.
  • FIG. 4 is a schematic diagram of a second network device in an embodiment of this application.
  • Figure 5 is a schematic diagram of a system in an embodiment of the application.
  • the embodiments of the present application provide a method, network device, and system for establishing a connectivity detection session, which are used to create a connectivity detection session in an EVPN network.
  • EVPN is a Layer 2 network interconnection technology.
  • media access control (MAC) learning between network devices for example, PE devices
  • the control protocol uses the border gateway protocol (border gateway protocol).
  • Border gateway protocol Border gateway protocol
  • Gateway protocol, BGP is used as a control plane protocol for MAC address learning, access topology, and VPN site discovery.
  • EVPN mainly includes two kinds, one is VPWS network, the other is E-LAN network.
  • VPWS network also known as E-LINE network, is a Layer 2 VPN service based on MPLS. It refers to a two-way intercommunication relationship between two network devices and is a point-to-point communication service.
  • the E-LAN network provides a multipoint-to-multipoint Layer 2 VPN service.
  • the communication between multiple network devices is the same as in the same local area network.
  • the data messages sent by each network device can be multicast, that is, any network device in the E-LAN network can send messages to all network devices in the E-LAN network through multicast ,
  • the multicast can be broadcast or multicast, which is not limited here.
  • network devices are devices that perform routing and forwarding functions, and can be devices such as routers, switches, and repeaters.
  • the routers, switches, and repeaters may be physical devices, or virtual devices (such as virtual servers, virtual routers, virtual switches, and virtual repeaters) implemented based on virtualization technology, depending on where the network device is deployed in the network Unlike the role, the network device may also be a PE device or the like.
  • EVPN 100 includes at least two network devices, such as PE1, PE2, and PE3.
  • the three sites (Site1, Site2, and Site3) of the virtual private network (virtual private network, VPN) service 1 (VPN1 for short) access EVPN through CE1, CE2, and CE3, respectively, and realize the interconnection of the three sites through EVPN.
  • VPN virtual private network
  • the EVPN 100 in the embodiment of the present application may also include a control and management device, and the control and management device is used to control and manage the network devices in the EVPN 100.
  • EVPN can also be called an EVPN network.
  • connection of any two of the at least two network devices after interconnection may cause problems such as device restart, link failure, etc., resulting in network disconnection or disconnection, then any two network devices In time, connectivity testing is required, such as CFM testing.
  • CFM testing is required, such as CFM testing.
  • the two network devices periodically send CFM detection messages to each other. If one of the network devices does not receive the CFM detection message sent by the other party in several cycles, it can be determined that the two network devices are offline, and an alarm message needs to be reported to the control and management device.
  • the control and management device may be a server in the EVPN network.
  • the control and management device is configured to receive and process the alarm messages reported by the at least two network devices.
  • the server may have relatively large differences due to different configurations or performance, and may include one or more central processing units (CPU) (for example, one or more processors) and memory , One or more storage media for storing application programs or data (for example, one or one storage device with a large amount of storage).
  • the memory and storage medium may be short-term storage or persistent storage.
  • the program stored in the storage medium may include one or more modules, and each module may include a series of instruction operations on the server.
  • the central processing unit may be configured to communicate with the storage medium, and execute a series of instruction operations in the storage medium on the server.
  • the first network device when the first network device is added to the EVPN network, only the integrated multicast routing table needs to be configured for the first network device, so that when the establishment of a connectivity detection session from the second network device is received Message, because the connectivity detection session creation message from the second network device carries the integrated multicast routing of the second network device and the session information of the second network device, and the local integrated multicast routing table includes the second network device’s Integrated multicast routing, the first network device can create a connectivity detection session with the second network device based on the session information of the second network device, so there is no need to communicate between the first network device and each existing network device in the EVPN network. Once the instance of the connectivity detection session is configured, the configuration of the instance of the connectivity detection session between the first network device and the original network devices in the EVPN network can be implemented, which simplifies the configuration process.
  • the EVPN network includes a first network device and a second network device.
  • the second network device is the initiator of the connectivity detection session
  • the first network device is the initiator of the connectivity detection session.
  • the second network device may also be the initiated end of the connectivity detection session
  • the first network device may also be the initiator of the connectivity detection session, which is not limited here.
  • the method includes:
  • the second network device obtains an integrated multicast route of the second network device.
  • the second network when the second network device enters the EVPN network, the second network can obtain the integrated multicast route of the second network device.
  • the second network device may receive the integrated multicast route of the second network device added by the network administrator through the command line on the local machine. In a specific implementation manner, the second network device may receive remote control performed by the network administrator by controlling the management device to add the integrated multicast route of the second network device.
  • control and management device may send the integrated multicast route to the second network device, and after receiving it, the second network device serves as the integrated multicast route of the second network device to complete the configuration of the integrated multicast route.
  • the network administrator can send the integrated multicast route to the second network device through the control and management device, or the control and management device can automatically send the integrated multicast route to the second network device, which is not limited here. .
  • control and management device may select an available integrated multicast route from a pre-stored integrated multicast routing table, and configure it to the second network device.
  • control and management device may also randomly set a value, configure it to the second network device, and update the integrated multicast routing table so that the value of an entry in the integrated multicast routing table is the second network device Integrated multicast routing. It should be noted that the above execution steps of controlling and managing the device may be executed under the operation of a network administrator, or may be automatically executed by the controlling and managing device, which is not limited here.
  • the integrated multicast routing can carry the route distinguisher (RD) and route target (RT) values of the EVPN instance on the local network device, as well as the source IP, such as the local network device’s Local loopback interface (loopback) address, and provider multicast service interface (PMSI) information, where PMSI is used to carry tag information encapsulated during multicast packet transmission.
  • the PMSI and RT values are carried in the attribute information of the route, and the RD and source IP are carried in the network layer reachability information (NLRI) of the route.
  • NLRI network layer reachability information
  • the first network device obtains the integrated multicast routing table.
  • an integrated multicast routing table when the first network device newly enters the network, an integrated multicast routing table can be obtained.
  • the integrated multicast routing table includes a plurality of entries, and the value of each entry is an integrated multicast route. It should be noted that the integrated multicast routing table includes the integrated multicast routing of the second network device, that is, the value of one of the entries in the integrated multicast routing table is the value of the integrated multicast routing of the second network device.
  • the first network device may receive the value of each entry in the integrated multicast routing table added by the network administrator through the command line on the local machine. In a specific implementation, the first network device may also receive remote control from the network administrator to add the value of each entry in the integrated multicast routing table, which is not limited here.
  • control and management device may send the integrated multicast routing table to the first network device, so that the first network device saves the integrated multicast routing table.
  • the network administrator can send the integrated multicast routing table to the first network device through the control and management device, or the control and management device can automatically send the integrated multicast routing table to the first network device. Make a limit.
  • control and management device can gather all possible integrated multicast routing values at one time to make an integrated multicast routing table, and then send it to all network devices in the EVPN network.
  • control and management device may send the integrated multicast routing table to the first network device when the first network device enters the network, or it may broadcast or multicast the integrated multicast routing table to all network devices in the EVPN network regularly. There are no restrictions.
  • control and management device may also periodically update the integrated multicast routing table, and then periodically broadcast or multicast the updated integrated multicast routing table for each network device of the EVPN network.
  • control management device can also configure an integrated multicast route for the second network device when the second network device enters the network, and then broadcast or multicast the second network device to all network devices in the EVPN network Integrated multicast routing, so that all network devices in EVPN (such as the first network device) update the local integrated multicast routing table, so that the value of one of the entries in the integrated multicast routing table is the integration of the second network device Multicast routing is not limited here. It should be noted that the above-mentioned execution steps of controlling the management device may be executed under the operation of the network administrator, or may be executed automatically, which is not limited here.
  • the first network device and the second network device will transmit respective integrated multicast routes. Therefore, after the second network device obtains the integrated multicast route, it can advertise to each network device with a BGP neighbor relationship in the EVPN network through broadcast or multicast. For example, if the first network device and the second network device have a BGP neighbor relationship, the first network device can receive the integrated multicast route of the second network device sent by the second network device, and integrate the integrated multicast route of the second network device. The broadcast routing is stored in the integrated multicast routing table to update the integrated multicast routing table. In a specific implementation, the first network device may also receive an integrated multicast route sent by a network device other than the second network device in the EVPN network, and then save it locally, which is not limited here.
  • the integrated multicast routing table is an electronic table, electronic file or similar database stored in a router or a networked computer.
  • the integrated multicast routing table stores a path to a specific network address. It should be noted that the integrated multicast routing table can be fixed in advance by the network administrator, or can be dynamically modified, which is not limited here.
  • the integrated multicast routing tables configured by different network devices may be the same, while the integrated multicast routing tables configured by different network devices are different. For example, if the first network device and the second network device obtain the same integrated multicast routing table, the values of the entries in the integrated multicast routing table are:
  • the integrated multicast route obtained by the first network device may be 0:32:1.1.1.1
  • the integrated multicast route obtained by the second network device may be 0:32:2.2.2.2.
  • the second network device sends a connectivity detection session creation message to the first network device, where the connectivity detection session creation message carries the integrated multicast routing of the second network device and the session information of the second network device.
  • the second network device after the second network device enters the EVPN network, in order to perform connectivity detection between the second network device and each network device in the EVPM network, the second network device can send a message to each network device in the EVPN network.
  • the network device (including the first network device) sends a connection detection session creation message.
  • the second network device after the second network device enters the EVPN network, it can broadcast or multicast the connectivity detection session creation message to each network device in the EVPN network.
  • it may broadcast or multicast only one connectivity detection session creation message, or may broadcast or multicast periodically, which is not limited here.
  • the connectivity detection session may be a CFM session.
  • CFM sessions are used to implement the operation-administration and maintenance (OAM) function provided in the 802.1ag standard of the Institute of Electrical and Electronics Engineers (IEEE) Network equipment, such as equipment, optical network equipment, etc., performs the function of timely detection, recovery and management of abnormal network errors or abnormal problems such as service degradation and service failure.
  • OAM operation-administration and maintenance
  • the CFM session can be created through a three-way handshake, that is, after the second network device sends the CFM session creation message to the first network device, the first network device can reply to the CFM session response message, and finally, Second, the network device sends a confirmation message to the first network device again to complete the creation of the CFM session between the second network device and the first network device.
  • the creation of the CFM session may also be through a two-way handshake or a four-way handshake, which is not limited here.
  • the connectivity detection session creation message sent by the second network device carries the integrated multicast route of the second network device.
  • the type length value TLV field in the creation message of the connectivity detection session includes the integrated multicast route of the second network device, and the TLV field includes type, length, and value.
  • the type can have 8 characters to indicate that the type of the TLV field is integrated multicast routing
  • the length can have 8 characters to indicate the length of the TLV field
  • the value can have 16 characters and is used to indicate the integrated multicast routing of the second network device.
  • the first network device determines that the local integrated multicast routing table includes the integrated multicast routing of the second network device.
  • the first network device when the first network device receives the connectivity detection session creation message sent by the second network device, it may obtain the integrated multicast route of the second network device from the connectivity detection session creation message. It is compared with the values of the entries in the local integrated multicast routing table one by one. If the first network device finds the integrated multicast route of the second network device from the integrated multicast routing table, it can be considered that the first network device and the second network device belong to the same EVPN network, and communication can be carried out, and a connection needs to be created If the connectivity detection session is detected, the first network device may return a response message of the connectivity detection session to the second network device. If the first network device does not find the integrated multicast route from the integrated multicast routing table, it can be considered that the first network device and the second network device do not belong to the same EVPN network, and the first network device may not communicate, and No connectivity detection session is created.
  • each entry in the local integrated multicast routing table of the first network device are:
  • the integrated multicast routing table has the integrated multicast route of the second network device, and it is determined that the second network device is connected to the The first network device belongs to the same EVPN network, the first network device determines to establish a connectivity detection session with the second network device.
  • the session information includes MEP ID or Session ID.
  • the CFM session creation message sent by the second network device to the first network device will carry the MEP of the second network device ID as session information. Then the first network device will return a response message of the CFM session to the second network device, and the response message carries the MEP ID of the first network device, so that both parties can finally create a CFM session.
  • the first network device may preset a MEP ID range, and the MEP ID range includes multiple MEP IDs.
  • the first network device receives the CFM session creation message sent by the second network device, it acquires the session information in the creation message, that is, the MEP ID of the second network device.
  • the first network device determines whether the MEP ID of the second network device is within the MEP ID range. If it is, the first network device performs the step of creating a CFM session with the second network device; otherwise, the step is not performed.
  • the second network device may also set the MEP ID range.
  • the second network device When receiving the CFM session creation response returned by the first network device, it can obtain the session information in the creation response, that is, the first network device's ID range. MEP ID.
  • the second network device determines whether the MEP ID of the first network device is within the MEP ID range. If it is, the first network device performs the step of creating a CFM session with the second network device; otherwise, the step is not performed.
  • the MEP ID range and the MEP ID range can be the same or different, and are not limited here.
  • the first network device or the second network device may not set the MEP ID range or the MEP ID range, which is not limited here.
  • the Session ID is carried in the session message, so that the first network device determines whether to create a connectivity detection session based on the Session ID range.
  • the procedure is similar to the case where the MEP ID is carried in the above-mentioned session message, and will not be repeated here.
  • the first network device sends a response packet of the connectivity detection session to the second network device, where the response packet of the connectivity detection session includes session information of the first network device.
  • the first network device can communicate with the second network device according to the session information of the second network device.
  • the device creates a connectivity detection session.
  • the first network device may send a response packet of the connectivity detection session to the second network device, and the response packet of the connectivity detection session includes the session information of the first network device, so that the second network device can The session information of the device creates a connectivity detection session with the first network device.
  • the second network device will also send a confirmation message to the first network device, and the two complete the creation of the connectivity detection session. If the connectivity detection session is created by a two-way handshake, the second network device does not need to send an acknowledgement message to the first network device. After the first network device sends a response message of the connectivity detection session to the second network device, The two complete the establishment of the connectivity detection session.
  • the establishment of the connectivity detection session can also be a four-way handshake, which is not limited here.
  • the first network device sends the response message of the connectivity detection session to the second network device to carry the integrated multicast route of the first network device, so that the second network device can determine the local integrated multicast route Whether there is an integrated multicast route for the first network device in the table, if so, the second network device will return a confirmation message to the first network device to complete the creation of the connectivity detection session.
  • the network administrator to configure the connectivity detection session instance between the first network device and the existing network devices in the EVPN network one by one, and the connection to the first network can be realized.
  • the device performs the configuration of the connectivity detection session instance with each original network device in the EVPN network, which simplifies the configuration process.
  • first network device and the second network device can periodically send connectivity detection packets to each other, that is, the first network device periodically sends connectivity detection messages to the second network device.
  • the connectivity detection message, and/or the first network device receives the connectivity detection message periodically sent by the second network device.
  • the alarm message is reported to the control and management device, that is, if the first network device is in the preset number of cycles If the connectivity detection message sent by the second network device is not received, the first network device reports an alarm message to the control and management device, or if the second network device does not receive the first network within a preset number of cycles If the device sends a connectivity detection message, the second network device reports an alarm message to the control and management device.
  • the first network device and the second network device can send and receive fault statistics messages, in which one party sends and the other receives.
  • the first network device and the second network device can determine the sender and receiver of the fault statistics message according to the MEP ID of the first network device and the MEP ID of the second network device.
  • the sender is one of the first network device and the second network device
  • the receiver is one of the first network device and the second network device that is different from the sender.
  • the sender and the receiver can be determined according to the numerical value of the MEP ID of the first network device and the MEP ID of the second network device.
  • a network device with a MEP ID with a larger value is used as the receiver, and a network device with a smaller MEP ID as the sender.
  • the network device with the MEP ID with a larger value may also be used as the sender, and the network device with the MEP ID with a smaller value may be used as the receiver, which is not limited here.
  • it can also be determined in other ways, such as the size of the integrated multicast route or the size of the Session ID, which is not limited here.
  • This application also provides a network device used as the first network device 300, including:
  • the processor 303 is configured to execute computer-readable instructions in the memory 302 to perform the following operations:
  • the connectivity detection session creation message carries the integrated multicast routing of the second network device and the session information of the second network device; determine the local integrated multicast routing table It includes the integrated multicast routing of the second network device; and creates a connectivity detection session with the second network device according to the session information of the second network device.
  • the configuration of the connectivity detection session instance between the first network device and the original network devices in the EVPN network can be realized, without the need for the first network device Instances of connectivity detection sessions are configured one by one with each existing network device in the EVPN network, which simplifies the configuration process.
  • the first network device may be a PE to provide a solution for establishing a connectivity detection session between each PE in the EVPN network.
  • the first network device may be a PE to provide a solution for establishing a connectivity detection session between each PE in the EVPN network.
  • the processor 303 may also receive a connectivity detection session creation message sent by the second network device through broadcast or multicast, and the second network device only needs to send a message instead of It needs to be sent to every network device in the EVPN network, which reduces the burden of transmission resources and improves transmission efficiency.
  • the processor 303 may also obtain an integrated multicast routing table.
  • the integrated multicast routing table includes the integrated multicast routing of the second network device, so it can be determined that the first network device and the second network device belong to the same EVPN network, thereby determining that the first network device and the second network device need to establish a connection Sex detection session.
  • the manner in which the processor 303 obtains the integrated multicast routing table may include:
  • the integrated multicast routing table is obtained according to the configuration of the command line received locally, so the network administrator can input the integrated multicast routing table locally on the network device.
  • the integrated multicast routing table can be dynamically and automatically updated to meet the needs of different network equipment in different periods, while reducing the workload of network administrators and improving work efficiency.
  • the processor 303 is further configured to obtain a MEP ID range or a session ID range.
  • the MEP ID range includes the MEP ID of the second network device, or the Session ID range includes the session ID of the second network device, so that the first network device can limit the specific Only the network device with MEP ID or Session ID can create a connectivity detection session.
  • the processor 303 may also determine that the MEP ID of the second network device is within the MEP ID range, or determine the second network If the Session ID of the device is within the Session ID range, the connectivity detection session can be created, otherwise, it does not need to be created.
  • the processor 303 may also determine the failure statistical report according to the MEP ID of the first network device and the MEP ID of the second network device.
  • the sender and receiver of the message or determine the sender and receiver of the fault statistics message according to the Session ID of the first network device and the Session ID of the second network device, where the senders are the first network device and the second network One of the devices, and the receiver is one of the first network device and the second network device that is different from the sender.
  • the processor 303 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.
  • the processor 303 may also be an application-specific integrated circuit (ASIC), a programmable logic device (programmable logic device, PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field programmable logic gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • the processor 303 may refer to one processor, or may include multiple processors.
  • the transceiver 301 is configured to receive the BGP routing information from the second network device, and send the message to the processor 303 for subsequent operation processing.
  • the BGP routing information includes a destination address, a next hop address to the destination address, and attribute information.
  • the attribute information indicates a manner in which the first network device performs iterative processing on the next hop address.
  • the memory 302 may include a volatile memory (English: volatile memory), such as random-access memory (random-access memory, RAM); the memory may also include a non-volatile memory (English: non-volatile memory), such as read-only Memory (read-only memory, ROM), flash memory (English: flash memory), hard disk (HDD) or solid-state drive (SSD); memory can also include a combination of the above types of memory .
  • Computer readable instructions are stored in the memory 302, and the computer readable instructions include at least one software module. After executing each software module, the processor 303 can perform corresponding operations according to the instructions of each software module.
  • this application also provides a network device used as a second network device 400, and the second network device 400 includes:
  • the processor 403 is configured to execute computer-readable instructions in the memory 402 to perform the following operations:
  • the configuration of the connectivity detection session instance between the second network device 400 and the original network devices in the EVPN network can be implemented, without the need for the second network
  • the device 400 and each existing network device in the EVPN network are configured with instances of connectivity detection sessions one by one, which simplifies the configuration process.
  • the second network device 400 includes a PE to provide a solution for establishing a connectivity detection session between each PE in the EVPN network.
  • a PE to provide a solution for establishing a connectivity detection session between each PE in the EVPN network.
  • the instances of connectivity detection sessions are configured one by one among the existing network devices in the network, which simplifies the configuration process.
  • the processor 403 is specifically configured to:
  • the second network device 400 Broadcasting or multicasting the establishment message of the connectivity detection session to each network device in the EVPN network, the second network device 400 only needs to send a message, instead of sending to each network device in the EVPN network, which reduces The burden of transmission resources improves transmission efficiency.
  • the processor 403 obtaining the integrated multicast route includes:
  • the integrated multicast routing of the second network device 400 is obtained according to the configuration of the command line, so the network administrator can input the integrated multicast routing table locally on the network device.
  • the integrated multicast routing of the second network device 400 can be advertised to each network device in the EVPN, there is no need to edit the integrated multicast routing table in advance, and the integrated multicast routing table can be dynamically and automatically updated to meet different periods of time. The need for network equipment also reduces the workload of network administrators.
  • the processor 403 may broadcast or multicast the establishment message of the connectivity detection session by each network device in the EVPN network, and the second network device 400 only needs to send a message, and does not need to send a message to the EVPN network.
  • Each network device in the network transmits, which reduces the burden of transmission resources and improves transmission efficiency.
  • the processor 403 is further configured to execute:
  • the response message of the connectivity detection session includes the session information of the first network device 300, and is based on the session information of the first network device 300 and the second network device
  • the session information of 400 determines the sender and receiver of the fault statistics message, where the sender is one of the first network device 300 and the second network device 400, and the receiver is the first network device 300 and the second network device 400 The one that is different from the sender.
  • the processor 403 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and an NP.
  • the processor 403 may also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field programmable logic gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • the processor 403 may refer to one processor, or may include multiple processors.
  • the transceiver 401 is configured to receive BGP routing information from the second network device, and send the message to the processor 403 for subsequent operation processing.
  • the BGP routing information includes a destination address, a next hop address to the destination address, and attribute information.
  • the attribute information indicates a manner in which the first network device performs iterative processing on the next hop address.
  • the memory 402 may include a volatile memory (English: volatile memory), such as a random-access memory (random-access memory, RAM); the memory may also include a non-volatile memory (English: non-volatile memory), such as read-only Memory (read-only memory, ROM), flash memory (English: flash memory), hard disk (HDD) or solid-state drive (SSD); memory can also include a combination of the above types of memory .
  • the memory 402 stores computer readable instructions, and the computer readable instructions include at least one software module. After the processor 403 executes each software module, it can perform corresponding operations according to the instructions of each software module.
  • the present application also provides a system 500. It includes a first network device 300 and a second network device 400.
  • the first network device 300 is the first network device described in FIG. 3 above
  • the second network device 400 is the second network device described in FIG. 4 above.
  • each device in the system 500 please refer to relevant chapters such as FIG. 3 and FIG. 4 above, and will not be repeated here.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium, or a semiconductor medium) and the like.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or software function unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the foregoing storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请实施例公开了一种连通性检测会话的创建方法、网络设备和系统，用于在EVPN网络中进行连通性检测会话的创建。本申请实施例方法包括：所述第一网络设备接收来自所述第二网络设备的连通性检测会话的创建消息，所述连通性检测会话的创建消息中携带所述第二网络设备的集成多播路由和所述第二网络设备的会话信息；所述第一网络设备确定本地的集成多播路由表中包括所述第二网络设备的集成多播路由；所述第一网络设备根据所述第二网络设备的会话信息与所述第二网络设备创建所述连通性检测会话。

Description

一种连通性检测会话的创建方法、网络设备和系统
本申请要求于2019年1月16日提交中国国家知识产权局、申请号为201910040453.X、发明名称为“一种连通性检测会话的创建方法、网络设备和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种配置方法及控制器。
背景技术
以太网虚拟专用网络(ethernet virtual private network，EVPN)是一种用于实现二层网络互通的虚拟专用网络(virtual private network，VPN)技术。EVPN通过扩展边界网关(border gateway protocol，BGP)协议或多协议标签交换(multi-protocol label switching，MPLS)协议，新增了几种路由类型，用于在不同运营商边缘(provider edge，PE)设备之间通告主机的媒体访问控制(media access control，MAC)地址和互联网协议(internet protocol，IP)地址。EVPN的网络结构和BGP或MPLS的网络结构相似，各个EVPN站点之间二层互通，PE设备上通过建立EVPN实例以接入各个站点的客户侧边缘(customer edge，CE)设备。
EVPN的网络结构主要包括两种，一种是虚拟私人有线服务(virtual private wire service，VPWS)，另一种是以太本地局域网(ethernet local area network，E-LAN)。VPWS又称为E-LINE，E-LINE是基于MPLS的二层VPN业务，是指两个PE之间是双向互通的关系，是点到点的通信业务。而E-LAN是提供一种多点到多点的二层VPN服务，在E-LAN中，通过透明传送报文，使得多个PE之间的通信就像在同一个局域网一样。
无论是E-LINE还是E-LAN都需要进行连接故障管理(connectivity fault management,CFM)。当前，E-LINE主要通过网络管理员对进行E-LINE通信的两端PE配置匹配的CFM实例，使得当本端PE发送CFM会话创建消息给对端PE时，对端PE可以与本端PE创建CFM会话。但是对于E-LAN架构，由于PE数量众多，若使用上述E-LINE所使用的进行CFM的方案，需要在每两个PE之间配置配对的CFM实例，工作量巨大，配置耗时耗力。
发明内容
本申请实施例提供了一种连通性检测会话的创建方法、网络设备和系统，用于在EVPN网络中进行连通性检测会话的创建。
本申请第一方面提供了一种连通性检测会话的创建方法，用于EVPN网络，EVPN网络包括第一网络设备和第二网络设备，该方法包括：
第一网络设备接收来自第二网络设备的连通性检测会话的创建消息，连通性检测会话的创建消息中携带第二网络设备的集成多播路由和第二网络设备的会话信息；第一网络设备确定本地的集成多播路由表中包括第二网络设备的集成多播路由；第一网络设备根据第二网络设备的会话信息与第二网络设备创建连通性检测会话。
当在EVPN网络中新增第一网络设备时，只需要对该第一网络设备配置集成多播路由表，使得当接收到来自该第二网络设备的连通性检测会话的创建消息时，由于来自第二网络设备的连通性检测会话的创建消息携带该第二网络设备的集成多播路由和该第二网络设备的会话信息，且本地的集成多播路由表包括该第二网络设备的集成多播路由，该第一网络设备可以根据该第二网络设备的会话信息与第二网络设备创建连通性检测会话，因此不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，就可以实现对第一网络设备与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，简化了配置流程。
在一些可能的实现方式中，第一网络设备为PE，以提供EVPN 100中的各个PE之间创建连通性检测会话的方案，在该方案中，不需要对第一网络设备与EVPN 100中现有的各个网络设备之间一一配置连通性检测会话的实例，简化了配置流程。
在一些可能的实现方式中，第一网络设备接收来自第二网络设备的连通性检测会话的创建消息包括：第一网络设备接收来自第二网络设备通过广播或组播的方式发送的连通性检测会话的创建消息。由于通过广播或组播的方式，第二网络设备仅需发送一份连通性检测会话的创建消息，而不需要对EVPN网络中的每一个网络设备分别发送，降低了传输资源的负担，提高了传输的效率。
在一些可能的实现方式中，第一网络设备接收来自第二网络设备的连通性检测会话的创建消息之前，还包括：第一网络设备获得集成多播路由表，集成多播路由表包括第二网络设备的集成多播路由。由于集成多播路由表包括第二网络设备的集成多播路由，第一网络设备因此可以确定第一网络设备与第二网络设备同属一个EVPN网络，以此确定需要创建连通性检测会话。
在一些可能的实现方式中，第一网络设备获得集成多播路由表的方式可以包括：
第一网络设备根据本地接收的命令行的配置获得所述集成多播路由表，因此网络管理员可以在网络设备本地输入集成多播路由表。
或，控制管理设备向第一网络设备接收发送集成多播路由表，第一网络设备保存集成多播路由表，因此网络管理员可以通过控制管理设备远程设置集成多播路由表。
或，第一网络设备接收第二网络设备通告的第二网络设备的集成多播路由，第一网络设备在集成多播路由表中保存第二网络设备的集成多播路由，则不需要预先编辑好集成多播路由表，可以动态地自动更新集成多播路由表，以满足新的网络设备入网时自身的集成多播路由对EVPN网络中的其他网络设备进行告知的需要，同时减少网络管理员的工作量，提高了工作效率。
在一些可能的实现方式中，连通性检测会话包括连接故障管理(connectivity fault management，CFM)会话，以对第一网络设备和第二网络设备之间的连通进行故障检测和管理。
在一些可能的实现方式中，连通性检测会话的创建消息中的类型长度值 (tag-length-value，TLV)字段中包括第二网络设备的集成多播路由，TLV字段包括类型、长度和值，其中，类型用于指示TLV字段的类型为集成多播路由，长度用于指示TLV字段的长度，值为第二网络设备的集成多播路由。因此，可以确定连通性检测会话的创建消息中集成多播路由的位置，以使得第一网络设备可以从连通性检测会话的创建消息中的TLV字段的值中获取集成多播路由。
在一些可能的实现方式中，第二网络设备的会话信息包括第二网络设备的维护联盟边缘节点标识(maintenance association end point ID，MEP ID)或会话标识Session ID。以使得第一网络设备和第二网络设备可以对连通性检测会话进行协商创建。
在一些可能的实现方式中，该方法还包括：
第一网络设备获得MEP ID范围或Session ID范围，MEP ID范围包括第二网络设备的MEP ID，或Session ID范围包括第二网络设备的Session ID，第一网络设备根据第二网络设备的会话信息与第二网络设备创建连通性检测会话之前，还包括：第一网络设备确定第二网络设备的MEP ID在MEP ID范围之内；或，第一网络设备确定第二网络设备的Session ID在Session ID范围之内，以使得第一网络设备可以限定具有特定MEP ID或Session ID的网络设备才能创建连通性检测会话。
在一些可能的实现方式中，当第一网络设备与第二网络设备创建连通性检测会话之后，第一网络设备根据第一网络设备的MEP ID和第二网络设备的MEP ID确定故障统计报文的发送者和接收者，或第一网络设备根据第一网络设备的Session ID和第二网络设备的Session ID确定故障统计报文的发送者和接收者，其中，发送者为第一网络设备和第二网络设备中的一个，接收者为第一网络设备和第二网络设备中不同于发送者的一个。
本申请第二方面提供了一种连通性检测会话的创建方法，用于EVPN网络，EVPN网络包括第一网络设备和第二网络设备，该方法包括：
第二网络设备获得第二网络设备的集成多播路由；第二网络设备向第一网络设备发送连通性检测会话的创建消息，连通性检测会话的创建消息携带第二网络设备的集成多播路由和会话信息，会话信息用于创建连通性检测会话。
当在EVPN网络中新增第一网络设备时，只需要对该第一网络设备配置集成多播路由表，使得当接收到来自该第二网络设备的连通性检测会话的创建消息时，由于来自第二网络设备的连通性检测会话的创建消息携带该第二网络设备的集成多播路由和该第二网络设备的会话信息，且本地的集成多播路由表包括该第二网络设备的集成多播路由，该第一网络设备可以根据该第二网络设备的会话信息与第二网络设备创建连通性检测会话，因此不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，就可以实现对第一网络设备与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，简化了配置流程。
在一些可能的实现方式中，第二网络设备获得集成多播路由包括：
第二网络设备根据命令行的配置获得第二网络设备的集成多播路由，因此网络管理员可以在网络设备本地输入集成多播路由表。
或，第二网络设备接收控制管理设备发送的集成多播路由，作为第二网络设备的集成多播路由，因此网络管理员可以通过控制管理设备远程设置集成多播路由表。
第二网络设备向EVPN中的各个网络设备通告第二网络设备的集成多播路由，则不需要预先编辑好集成多播路由表，可以动态地自动更新集成多播路由表，以满足新的网络设备入网时自身的集成多播路由对EVPN网络中的其他网络设备进行告知的需要，同时减少网络管理员的工作量，提高了工作效率。
在一些可能的实现方式中，第二网络设备向第一网络设备发送连通性检测会话的创建消息包括：第二网络设备向EVPN网络中的各个网络设备广播或组播连通性检测会话的创建消息。则第二网络设备仅需发送一份报文，而不需要对EVPN网络中的每一个网络设备各发送一份报文，降低传输资源的负担，提高了传输的效率。
在一些可能的实现方式中，连通性检测会话包括CFM会话，因此可以对第一网络设备和第二网络设备之间的连接进行故障检测和管理。
在一些可能的实现方式中，连通性检测会话的创建消息中的TLV字段中包括第二网络设备的集成多播路由，TLV字段包括类型、长度和值，其中，类型用于指示TLV字段的类型为集成多播路由，长度用于指示TLV字段的长度，值为第二网络设备的集成多播路由。以确定连通性检测会话的创建消息中集成多播路由的位置，以使得第一网络设备可以从连通性检测会话的创建消息中的TLV字段的值中获取集成多播路由。
在一些可能的实现方式中，第二网络设备的会话信息包括第二网络设备的MEP ID或Session ID，以使得第一网络设备和第二网络设备可以对连通性检测会话进行协商创建。
在一些可能的实现方式中，第二网络设备向EVPN中的各个网络设备发送连通性检测会话的创建消息之后，第二网络设备接收第一网络设备发送的连通性检测会话的响应报文，连通性检测会话的响应报文包括第一网络设备的会话信息，并根据第一网络设备的会话信息和第二网络设备的会话信息确定故障统计报文的发送者和接收者，其中，发送者为第一网络设备和第二网络设备中的一个，接收者为第一网络设备和第二网络设备中不同于发送者的一个。
本申请第三方面提供了一种网络设备，用作第一网络设备，包括：
收发器、存储器和处理器。
处理器用于执行存储器中的计算机可读指令从而执行以下操作：
接收来自第二网络设备的连通性检测会话的创建消息，连通性检测会话的创建消息中携带第二网络设备的集成多播路由和第二网络设备的会话信息；确定本地的集成多播路由表中包括第二网络设备的集成多播路由；根据第二网络设备的会话信息与第二网络设备创建连通性检测会话。
当在EVPN网络中新增第一网络设备时，只需要对该第一网络设备配置集成多播路由表，使得当接收到来自该第二网络设备的连通性检测会话的创建消息时，由于来自第二网络设备的连通性检测会话的创建消息携带该第二网络设备的集成多播路由和该第二网络设备的会话信息，且本地的集成多播路由表包括该第二网络设备的集成多播路由，该第一网络设备可以根据该第二网络设备的会话信息与第二网络设备创建连通性检测会话，因此不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，就可以实现对第一网络设备与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，简化了配置流程。
在一些可能的实现方式中，第一网络设备为PE，以提供EVPN网络中的各个PE之间创建连通性检测会话的方案，在该方案中，不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，简化了配置流程。
在一些可能的实现方式中，处理器接收来自第二网络设备的连通性检测会话的创建消息包括：处理器接收来自第二网络设备通过广播或组播的方式发送的连通性检测会话的创建消息。第二网络设备仅需发送一份报文，而不需要对EVPN网络中的每一个网络设备各发送一份报文，降低传输资源的负担，提高了传输的效率。
在一些可能的实现方式中，处理器还用于：获得集成多播路由表，集成多播路由表包括第二网络设备的集成多播路由。因此处理器可以确定第一网络设备与第二网络设备同属一个EVPN网络，以此确定需要建立连通性检测会话。
在一些可能的实现方式中，处理器获得集成多播路由表的方式可以包括：
根据本地接收的命令行的配置获得所述集成多播路由表，因此网络管理员可以在网络设备本地输入集成多播路由表。
或，接收控制管理设备发送的集成多播路由表，第一网络设备保存集成多播路由表，因此网络管理员可以通过控制管理设备远程设置集成多播路由表。
或，接收第二网络设备通告的第二网络设备的集成多播路由，第一网络设备在集成多播路由表中保存第二网络设备的集成多播路由，则不需要预先编辑好集成多播路由表，可以动态地自动更新集成多播路由表，以满足新的网络设备入网时自身的集成多播路由对EVPN网络中的其他网络设备进行告知的需要，同时减少网络管理员的工作量，提高了工作效率。
在一些可能的实现方式中，连通性检测会话包括连接故障管理CFM会话，以对第一网络设备和第二网络设备之间的连通进行故障检测和管理。
在一些可能的实现方式中，连通性检测会话的创建消息中的TLV字段中包括第二网络设备的集成多播路由，TLV字段包括类型、长度和值，其中，类型用于指示TLV字段的类型为集成多播路由，长度用于指示TLV字段的长度，值为第二网络设备的集成多播路由。以确定连通性检测会话的创建消息中集成多播路由的位置，以使得第一网络设备可以从连通性检测会话的创建消息中的TLV字段的值中获取集成多播路由。
在一些可能的实现方式中，第二网络设备的会话信息包括第二网络设备的MEP ID或Session ID，以使得第一网络设备和第二网络设备可以对连通性检测会话进行协商创建。
在一些可能的实现方式中，处理器还用于：
获得MEP ID范围或Session ID范围，MEP ID范围包括第二网络设备的MEP ID，或Session ID范围包括第二网络设备的Session ID。处理器接收来自所述第二网络设备的连通性检测会话的创建消息之前，处理器还用于：确定第二网络设备的MEP ID在MEP ID范围之内；或，确定第二网络设备的Session ID在Session ID范围之内，以使得第一网络设备可以限定具有特定MEP ID或Session ID的网络设备才能创建连通性检测会话。
在一些可能的实现方式中，当第一网络设备与第二网络设备创建连通性检测会话之后，处理器还用于执行以下操作：根据第一网络设备的MEP ID和第二网络设备的MEP ID 确定故障统计报文的发送者和接收者，或根据第一网络设备的Session ID和第二网络设备的Session ID确定故障统计报文的发送者和接收者，其中，发送者为第一网络设备和第二网络设备中的一个，接收者为第一网络设备和第二网络设备中不同于发送者的一个。
本申请第四方面提供了一种网络设备，用作第二网络设备，第二网络设备包括：
收发器、存储器和处理器。
处理器用于执行存储器中的计算机可读指令从而执行以下操作：
获得第二网络设备的集成多播路由；向第一网络设备发送连通性检测会话的创建消息，连通性检测会话的创建消息携带第二网络设备的集成多播路由和会话信息，会话信息用于创建连通性检测会话。
当在EVPN网络中新增第一网络设备时，只需要对该第一网络设备配置集成多播路由表，使得当接收到来自该第二网络设备的连通性检测会话的创建消息时，由于来自第二网络设备的连通性检测会话的创建消息携带该第二网络设备的集成多播路由和该第二网络设备的会话信息，且本地的集成多播路由表包括该第二网络设备的集成多播路由，该第一网络设备可以根据该第二网络设备的会话信息与第二网络设备创建连通性检测会话，因此不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，就可以实现对第一网络设备与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，简化了配置流程。
在一些可能的实现方式中，网络设备可以包括PE，以提供了EVPN网络中的各个PE之间创建连通性检测会话的方案，在该方案中，不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，简化了配置流程。
在一些可能的实现方式中，第二网络设备获得集成多播路由包括：
第二网络设备根据命令行的配置获得第二网络设备的集成多播路由，因此网络管理员可以在网络设备本地输入集成多播路由表。
或，第二网络设备接收控制管理设备发送的集成多播路由，作为第二网络设备的集成多播路由，因此网络管理员可以通过控制管理设备远程设置集成多播路由表。
第二网络设备向EVPN中的各个网络设备通告第二网络设备的集成多播路由，则不需要预先编辑好集成多播路由表，可以动态地自动更新集成多播路由表，以满足新的网络设备入网时自身的集成多播路由对EVPN网络中的其他网络设备进行告知的需要，同时减少网络管理员的工作量，提高了工作效率。
在一些可能的实现方式中，处理器向第一网络设备发送连通性检测会话的创建消息包括：向EVPN网络中的各个网络设备广播或组播连通性检测会话的创建消息。则第二网络设备仅需发送一份报文，而不需要对EVPN网络中的每一个网络设备发送，降低了传输资源的负担，提高了传输的效率。
在一些可能的实现方式中，连通性检测会话包括CFM会话，对第一网络设备和第二网络设备之间的连通进行故障检测和管理。
在一些可能的实现方式中，连通性检测会话的创建消息中的TLV字段中包括第二网络设备的集成多播路由，TLV字段包括类型、长度和值，其中，类型用于指示TLV字段的类型为集成多播路由，长度用于指示TLV字段的长度，值为第二网络设备的集成多播 路由。以确定连通性检测会话的创建消息中集成多播路由的位置，以使得第一网络设备可以从连通性检测会话的创建消息中的TLV字段的值中获取集成多播路由。
在一些可能的实现方式中，第二网络设备的会话信息包括第二网络设备的MEP ID或Session ID，因此，第一网络设备可以限定具有特定MEP ID或Session ID的网络设备才能创建连通性检测会话。
在一些可能的实现方式中，第二网络设备向EVPN中的各个网络设备发送连通性检测会话的创建消息之后，第二网络设备接收第一网络设备发送的连通性检测会话的响应报文，连通性检测会话的响应报文包括第一网络设备的会话信息，并根据第一网络设备的会话信息和第二网络设备的会话信息确定故障统计报文的发送者和接收者，其中，发送者为第一网络设备和第二网络设备中的一个，接收者为第一网络设备和第二网络设备中不同于发送者的一个。
本申请第五方面还提供了一种计算机可读介质，包括指令，当其在计算机上运行时，使得计算机执行上述第一方面中各种实现方式所述的方法。
本申请第六方面还提供了一种计算机可读介质，包括指令，当其在计算机上运行时，使得计算机执行上述第二方面中各种实现方式所述的方法。
本申请第七方面还提供了一种系统，包括上述第三方面中各种实现方式所述的第一网络设备和上述第四方面中各种实现方式所述的第二网络设备。
从以上技术方案可以看出，本申请实施例具有以下优点：
当在EVPN网络中新增第一网络设备时，只需要对该第一网络设备配置集成多播路由表，使得当接收到来自该第二网络设备的连通性检测会话的创建消息时，由于来自第二网络设备的连通性检测会话的创建消息携带该第二网络设备的集成多播路由和该第二网络设备的会话信息，且本地的集成多播路由表包括该第二网络设备的集成多播路由，该第一网络设备可以根据该第二网络设备的会话信息与第二网络设备创建连通性检测会话，因此不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，就可以实现对第一网络设备与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，简化了配置流程。
附图说明
图1为本申请实施例中的EVPN 100；
图2-1为本申请实施例中的一种连通性检测会话的创建方法；
图2-2为本申请实施例中的TLV的示意图；
图3为本申请实施例中的第一网络设备的示意图；
图4为本申请实施例中的第二网络设备的示意图；
图5为本申请实施例中的系统的示意图。
具体实施方式
本申请实施例提供了一种连通性检测会话的创建方法、网络设备和系统，用于在EVPN网络中进行连通性检测会话的创建。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请应用于通过技术实现VPN站点之间互联的网络场景中。EVPN是一种二层网络互联技术，在EVPN中，网络设备(例如，PE设备)之间的媒体接入控制(media access control，MAC)学习在控制平面实现，控制协议使用边界网关协议(border gateway protocol,BGP)作为控制平面的协议，进行MAC地址学习、接入拓扑和VPN站点(site)发现。EVPN主要包括两种，一种是VPWS网络，另一种是E-LAN网络。VPWS网络又称为E-LINE网络，是基于MPLS的二层VPN业务，是指两个网络设备之间是双向互通的关系，是点到点的通信业务。而E-LAN网络提供一种多点到多点的二层VPN服务.在E-LAN网络中，通过透明传送报文，使得多个网络设备之间的通信就像在同一个局域网一样。在E-LAN网络中，各个网络设备发送的数据报文可以是多播的，即E-LAN网络中的任意一个网络设备可以通过多播的方式向E-LAN网络中的所有网络设备发送消息，所述多播可以为广播或组播，此处不做限定。
需要说明的是，网络设备是执行路由转发功能的设备，可以是路由器、交换机、转发器等设备。所述路由器、交换机、转发器可以是物理设备，也可以是基于虚拟化技术实现的虚拟设备(如，虚拟服务器、虚拟路由器、虚拟交换机、虚拟转发器)，根据网络设备在网络中部署的位置和角色不同，所述网络设备也可以为PE设备等。
以图1示例，EVPN 100包括至少两个网络设备，例如PE1、PE2和PE3。虚拟专用网络(virtual private network，VPN)业务1(简称VPN1)的三个站点(Site1、Site2和Site3)分别通过CE1、CE2和CE3接入EVPN，通过EVPN实现三个站点的互联。
需要说明的是，本申请实施例中的EVPN 100还可以包括控制管理设备，控制管理设备用于对EVPN 100中的网络设备进行控制和管理。EVPN也可以称为EVPN网络。
还需要说明的是，互联后的至少两个所述网络设备中任意两个网络设备的连接可能会发生设备重启、链路故障等问题，导致断网、掉线，那么任意两个网络设备之间则需要进行连通性检测，如CFM检测。在CFM检测的过程中，两个网络设备相互周期性地向对方发送CFM检测报文。若其中一个网络设备在若干个周期中没有接收到对方发送的CFM检测报文，则可以确定两个网络设备掉线，则需要向控制管理设备上报告警消息。
在一个具体的实施方式中，控制管理设备可以为EVPN网络中的一个服务器。控制管理设备用于接收并处理所述至少两个网络设备上报的告警消息。在一个具体的实施方式中，服务器可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央 处理器(central processing units，CPU)(例如，一个或一个以上处理器)和存储器，一个或一个以上存储应用程序或数据的存储介质(例如一个或一个以上海量存储设备)。其中，存储器和存储介质可以是短暂存储或持久存储。存储在存储介质的程序可以包括一个或一个以上模块，每个模块可以包括对服务器中的一系列指令操作。更进一步地，中央处理器可以设置为与存储介质通信，在服务器上执行存储介质中的一系列指令操作。
但是由于EVPN网络中的网络设备数量众多，若使用与E-LINE网络相同的连通性检测技术，即在每两个网络设备之间设置一个CFM实例，工作量大，配置耗时耗力。
在本申请实施例中，当在EVPN网络中新增第一网络设备时，只需要对第一网络设备配置集成多播路由表，使得当接收到来自第二网络设备的连通性检测会话的创建消息时，由于来自第二网络设备的连通性检测会话的创建消息携带第二网络设备的集成多播路由和第二网络设备的会话信息，且本地的集成多播路由表包括第二网络设备的集成多播路由，第一网络设备可以根据第二网络设备的会话信息与第二网络设备创建连通性检测会话，因此不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，就可以实现对第一网络设备与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，简化了配置流程。
有鉴于此，请参考图2-1，本申请提供了一种连通性检测会话的创建方法，用于EVPN网络，EVPN网络包括第一网络设备和第二网络设备。在本申请实施例中，第二网络设备为连通性检测会话的发起端，第一网络设备为连通性检测会话的被发起端。在一个具体的实施方式中，第二网络设备也可以为连通性检测会话的被发起端，第一网络设备也可以为连通性检测会话的发起端，此处不做限定。该方法包括：
201、第二网络设备获得该第二网络设备的集成多播路由。
在本申请实施例中，当第二网络设备进入EVPN网络时，第二网络可以获得该第二网络设备的集成多播路由。
在一个具体的实施方式中，第二网络设备可以在本机接收网络管理员通过命令行添加第二网络设备的集成多播路由。在一个具体的实施方式中，第二网络设备可以接收网络管理员通过控制管理设备进行的远程控制，以添加第二网络设备的集成多播路由。
在一个具体的实施方式中，控制管理设备可以向第二网络设备发送集成多播路由，第二网络设备接收后，作为第二网络设备的集成多播路由，以完成配置集成多播路由。在一个具体的实施方式中，网络管理员可以通过控制管理设备向第二网络设备发送集成多播路由，也可以由控制管理设备自动向第二网络设备发送集成多播路由，此处不做限定。
在一个具体的实施方式中，控制管理设备可以从预存的集成多播路由表中选取一个可用的集成多播路由，配置给第二网络设备。在一个具体的实施方式中，控制管理设备也可以随机设置一个值，配置给第二网络设备，并更新集成多播路由表，使得集成多播路由表的一个表项的值为第二网络设备的集成多播路由。需要说明的是，上述控制管理设备的执行步骤可以是在网络管理员操作下执行的，也可以是控制管理设备自动执行的，此处不做限定。
需要说明的是，集成多播路由中可以携带本端网络设备上EVPN实例的路由区分符 (route distinguisher，RD)和路由目标(route target，RT)值，以及源IP，如本端网络设备的本地环回接口(loopback)地址，以及提供者组播服务接口(provider multicast service interface，PMSI)信息，其中PMSI用于携带多播报文传输时封装的标签信息。PMSI和RT值承载在路由的属性信息中，RD和源IP承载在路由的网络层可通达性信息(network layer reachability information，NLRI)中。
202、第一网络设备获得集成多播路由表。
在本申请实施例中，当第一网络设备新入网时，可以获得集成多播路由表，集成多播路由表包括多个表项，其中每个表项的值为一个集成多播路由。需要说明的是，集成多播路由表包括第二网络设备的集成多播路由，即集成多播路由表的其中一个表项的值为第二网络设备的集成多播路由的值。
在一个具体的实施方式中，第一网络设备可以在本机接收网络管理员通过命令行添加集成多播路由表中各个表项的值。在一个具体的实施方式中，第一网络设备还可以接收网络管理员的远程控制，以添加集成多播路由表中各个表项的值，此处不做限定。
在一个具体的实施方式中，控制管理设备可以向第一网络设备发送集成多播路由表，使得第一网络设备保存集成多播路由表。在一个具体的实施方式中，网络管理员可以通过控制管理设备向第一网络设备发送集成多播路由表，也可以由控制管理设备自动向第一网络设备发送集成多播路由表，此处不做限定。
在一个具体的实施方式中，控制管理设备可以一次性将所有可能的集成多播路由的值进行汇集，制成一份集成多播路由表，然后向EVPN网络中的所有网络设备发送。具体的，控制管理设备可以在第一网络设备入网的时候向第一网络设备发送集成多播路由表，也可以定时向EVPN网络中的所有网络设备进行广播或组播集成多播路由表，此处不做限定。
在一个具体的实施方式中，控制管理设备也可以定时更新集成多播路由表，然后定时对EVPN网络的各个网络设备进行广播或组播更新后的集成多播路由表。在一个具体的实施方式中，控制管理设备也可以在第二网络设备入网时，为第二网络设备配置一个集成多播路由，然后向EVPN网络中的所有网络设备广播或组播第二网络设备的集成多播路由，以使得EVPN中的所有网络设备(如第一网络设备)更新本地的集成多播路由表，使得集成多播路由表的其中一个表项的值为第二网络设备的集成多播路由，此处不做限定。需要说明的是，上述控制管理设备的执行步骤可以是网络管理员操作下执行的，也可以是自动执行的，此处不做限定。
在一个具体的实施方式中，当第一网络设备和第二网络设备之间的BGP邻居关系建立成功后，第一网络设和第二网络设备之间会传递各自的集成多播路由。因此，当第二网络设备获得集成多播路由之后，可以向EVPN网络中的具有BGP邻居关系的各个网络设备通过广播或组播的方式进行通告。例如，若第一网络设备与第二网络设备具有BGP邻居关系，则第一网络设备可以接收到第二网络设备发送的第二网络设备的集成多播路由，并将第二网络设备的集成多播路由保存在集成多播路由表中，以更新集成多播路由表。在一个具体的实施方式中，第一网络设备还可以接收EVPN网络中的除了第二网络设备之外的网络设备发送的集成多播路由，然后保存在本地，此处不做限定。
需要说明的是，集成多播路由表是一种存储在路由器或者联网计算机中的电子表 格、电子文件或类数据库。在一个具体的实施方式中，集成多播路由表中存储着指向特定网络地址的路径。需要说明的是，集成多播路由表可以由网络管理员预先固定设置好的，也可以动态修改，此处不做限定。
需要说明的是，在同一个EVPN网络中，不同网络设备所配置的集成多播路由表可以是相同的，而不同网络设备所配置的集成多播路由是不同的。例如，若第一网络设备和第二网络设备获得同一个集成多播路由表，集成多播路由表的各个表项的值分别是：
0:32:1.1.1.1、0:32:2.2.2.2、0:32:3.3.3.3、0:32:4.4.4.4和0:32:10.10.10.10。
则第一网络设备获得的集成多播路由可以为0:32:1.1.1.1，而第二网络设备获得的集成多播路由可以为0:32:2.2.2.2。
203、第二网络设备向第一网络设备发送连通性检测会话的创建消息，连通性检测会话的创建消息中携带第二网络设备的集成多播路由和第二网络设备的会话信息。
在一个具体的实施方式中，当第二网络设备进入EVPN网络后，为了进行第二网络设备和EVPM网络中的各个网络设备之间的连通性检测，第二网络设备可以向EVPN网络中的各个网络设备(包括第一网络设备)发送连通性检测会话的创建消息。具体的，当第二网络设备进入EVPN网络后，可以向EVPN网络中的各个网络设备广播或组播连通性检测会话的创建消息。在一个具体的实施方式中，当第二网络设备进入EVPN网络后，可以仅广播或组播一次连通性检测会话的创建消息，也可以周期性地广播或组播，此处不做限定。
在一个具体的实施方式中，连通性检测会话可以为CFM会话。需要说明的是，CFM会话用于实现电气和电子工程师协会(institute of electrical and electronics engineers，IEEE)的802.1ag标准中提供的操作-管理-维护(operation administration and maintenance，OAM)功能，即对交换设备、光网络设备等网络设备进行业务降级、业务失败等网络异常错误或者异常问题进行及时检测、恢复和管理的功能。
需要说明的是，CFM会话的创建可以通过三次握手的方式，即第二网络设备向第一网络设备发送CFM会话的创建消息后，第一网络设备可以回复CFM会话的响应报文，最后，第二网络设备再次向第一网络设备发送确认消息，即可完成第二网络设备和第一网络设备之间的CFM会话的创建。在一个具体的实施方式中，CFM会话的创建也可以通过二次握手或四次握手的方式，此处不做限定。
需要说明的是，有关CFM会话的详细描述，请参见IEEE发布的征求意见802.1ag标准，该文档与此相关部分的内容好像整体复制一般以引入的方式并入(incorporated by reference)本文本中，对于其中与本申请矛盾或冲突的描述，以本申请的描述为准。此处为了简洁，不再赘述。
在本申请实施例中，第二网络设备发送的连通性检测会话的创建消息中携带第二网络设备的集成多播路由。在一个具体的实施方式中，连通性检测会话的创建消息中的类型长度值TLV字段中，包括第二网络设备的集成多播路由，TLV字段包括类型、长度和值。其中，如图2-2所示(为TLV的示意图)，类型可以具有8个字符，用于指示TLV字段的类型为集成多播路由，长度可以具有8个字符，用于指示TLV字段的长度，值可以具有16个字符，用于指示第二网络设备的集成多播路由。
204、第一网络设备确定本地的集成多播路由表包括第二网络设备的集成多播路由。
在本申请实施例中，当第一网络设备接收到第二网络设备发送的连通性检测会话的创建消息时，可以从连通性检测会话的创建消息中获取第二网络设备的集成多播路由，并与本地的集成多播路由表中的表项的值进行一一比对。若第一网络设备从集成多播路由表中找到第二网络设备的集成多播路由，则可以认为第一网络设备和第二网络设备属于同一个EVPN网络，则可以进行通信，且需要创建连通性检测会话，则第一网络设备可以向第二网络设备返回连通性检测会话的响应报文。若第一网络设备从集成多播路由表中没有找到集成多播路由，则可以认为第一网络设备和第二网络设备不属于同一个EVPN网络中，则第一网络设备可以不进行通信，且不进行连通性检测会话的创建。
例如，若第一网络设备本地的集成多播路由表中各个表项的值分别为：
0:32:1.1.1.1、0:32:2.2.2.2、0:32:3.3.3.3、0:32:4.4.4.4和0:32:10.10.10.10。
若第一网络设备接收到第二网络设备的集成多播路由为0:32:2.2.2.2，则集成多播路由表中具有第二网络设备的集成多播路由，则确定第二网络设备与第一网络设备同属于一个EVPN网络，则第一网络设备确定与第二网络设备进行连通性检测会话的创建。
需要说明的是，在第一网络设备和第二网络设备之间进行连通性检测会话的创建时，需要通过双方的会话信息进行协商，进而创建连通性检测会话。在一个具体的实施方式中，会话信息包括MEP ID或Session ID。
以CFM会话为例，当第一网络设备和第二网络设备之间要创建CFM会话时，第二网络设备向第一网络设备发送的CFM会话的创建消息中，会携带第二网络设备的MEP ID作为会话信息。然后第一网络设备会向第二网络设备返回CFM会话的响应报文，响应报文中携带第一网络设备的MEP ID，以使得双方最终创建CFM会话。
在一个具体的实施方式中，第一网络设备可以预先设置MEP ID范围，MEP ID范围包括多个MEP ID。当第一网络设备接收到第二网络设备发送的CFM会话的创建消息时，获取创建消息中的会话信息，即第二网络设备的MEP ID。第一网络设备判断第二网络设备的MEP ID是否在MEP ID范围之内。如果在，则第一网络设备执行与第二网络设备创建CFM会话的步骤，否则，不进行步骤。
在一个具体的实施方式中，第二网络设备也可以设置MEP ID范围，当接收到第一网络设备返回的CFM会话的创建响应时，可以获取创建响应中的会话信息，即第一网络设备的MEP ID。第二网络设备判断第一网络设备的MEP ID是否在MEP ID范围内。如果在，则第一网络设备执行与第二网络设备创建CFM会话的步骤，否则，不进行步骤。
需要说明的是，MEP ID范围和MEP ID范围可以相同，也可以不同，此处不做限定。在一个具体的实施方式中，第一网络设备或第二网络设备也可以不设置MEP ID范围或MEP ID范围，此处不做限定。
在一个具体的实施方式中，会话消息中会携带Session ID，以使得第一网络设备通过Session ID范围判断是否要进行连通性检测会话的创建。其步骤上述的会话消息中会携带MEP ID的情况类似，此处不做赘述。
205、第一网络设备向第二网络设备发送连通性检测会话的响应报文，连通性检测会话的响应报文包括第一网络设备的会话信息。
在本申请实施例中，当第一网络设备确定第二网络设备的集成多播路由在本地的集成多播路由表内之后，第一网络设备可以根据第二网络设备的会话信息与第二网络设备 创建连通性检测会话。具体的，第一网络设备可以向第二网络设备发送连通性检测会话的响应报文，连通性检测会话的响应报文包括第一网络设备的会话信息，以使得第二网络设备根据第一网络设备的会话信息与第一网络设备创建连通性检测会话。
在一个具体的实施方式中，若连通性检测会话的创建为三次握手的方式，则第二网络设备还会向第一网络设备发送确认消息，则二者完成连通性检测会话的创建。若连通性检测会话的创建为二次握手的方式，则第二网络设备不需要向第一网络设备发送确认消息，第一网络设备向第二网络设备发送连通性检测会话的响应报文后，二者即完成连通性检测会话的创建。连通性检测会话的创建还可以是四次握手，此处不做限定。
在本申请实施例中，第一网络设备向第二网络设备发送连通性检测会话的响应报文携带第一网络设备的集成多播路由，以使得第二网络设备可以确定本地的集成多播路由表中是否有第一网络设备的集成多播路由，若有，则第二网络设备才会向第一网络设备返回确认消息，以完成连通性检测会话的创建。
在本申请实施例中，通过上述步骤，不需要网络管理员对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，就可以实现对第一网络设备与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，简化了配置流程。
需要说明的是，当第一网络设备和第二网络设备创建了连通性检测会话后，二者可以周期性互相发送连通性检测报文，即第一网络设备向第二网络设备周期性发送连通性检测报文，和/或第一网络设备接收第二网络设备周期性发送的连通性检测报文。若第一网络设备或第二网络设备在若干个周期内没有接收到对方发送的连通性检测报文，则向控制管理设备上报告警消息，即若第一网络设备在预设个数的周期内没有接收到第二网络设备发送的连通性检测报文，则第一网络设备向控制管理设备上报告警消息，或若第二网络设备在预设个数的周期内没有接收到第一网络设备发送的连通性检测报文，则第二网络设备向控制管理设备上报告警消息。
在一个具体的实施方式中，当第一网络设备和第二网络设备创建连通性检测会话之后，需要对发生故障或断线等问题进行故障统计，如Y1731统计。在Y1731统计中，第一网络设备和第二网络设备之间可以收发故障统计报文，其中，一方进行发送，另一方进行接收。
以会话信息为MEP ID为例，第一网络设备和第二网络设备之间可以根据第一网络设备的MEP ID和第二网络设备的MEP ID来确定故障统计报文的发送者和接收者，其中，发送者为第一网络设备和第二网络设备中的一个，接收者为第一网络设备和第二网络设备中不同于发送者的一个。
具体的，可以根据第一网络设备的MEP ID和第二网络设备的MEP ID的数值大小，确定发送者和接收者。例如，以数值较大的MEP ID的网络设备为接收者，以数值较小的MEP ID的网络设备为发送者。在一个具体的实施方式中，也可以以数值较大的MEP ID的网络设备为发送者，以数值较小的MEP ID的网络设备为接收者，此处不做限定。在一个具体的实施方式中，也可以通过其他方式确定，如集成多播路由的大小或Session ID的大小，此处不做限定。
以上通过方法步骤的角度描述了本申请的技术方案，以下对本申请以功能装置的角 度进行描述。
请参考图3，本申请还提供了一种网络设备，用作第一网络设备300，包括：
收发器301、存储器302、处理器303和总线304，其中，收发器301、存储器302和处理器303通过总线304连接。
处理器303用于执行存储器302中的计算机可读指令从而执行以下操作：
接收来自第二网络设备的连通性检测会话的创建消息，连通性检测会话的创建消息中携带第二网络设备的集成多播路由和第二网络设备的会话信息；确定本地的集成多播路由表中包括第二网络设备的集成多播路由；根据第二网络设备的会话信息与第二网络设备创建连通性检测会话。
由于仅需要在第一网络设备的本地配置集成多播路由表，就可以实现对第一网络设备与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，简化了配置流程。
在一个具体的实施方式中，第一网络设备可以为PE，以提供EVPN网络中的各个PE之间创建连通性检测会话的方案。在该方案中，不需要对第一网络设备与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，简化了配置流程。
在一个具体的实施方式中，处理器303还可以接收来自第二网络设备通过广播或组播的方式发送的连通性检测会话的创建消息，第二网络设备仅需发送一份报文，而不需要对EVPN网络中的每一个网络设备发送，降低了传输资源的负担，提高了传输的效率。
在一个具体的实施方式中，处理器303还可以获得集成多播路由表。集成多播路由表包括第二网络设备的集成多播路由，因此可以确定第一网络设备与第二网络设备同属一个EVPN网络，以此确定第一网络设备与第二网络设备之间需要建立连通性检测会话。
在一个具体的实施方式中，处理器303获得集成多播路由表的方式可以包括：
根据本地接收的命令行的配置获得集成多播路由表，因此网络管理员可以在网络设备本地输入集成多播路由表。
或，接收控制管理设备发送的集成多播路由表，以使得通过存储器302保存集成多播路由表，因此网络管理员可以通过控制管理设备远程设置集成多播路由表。
或，接收第二网络设备通告的第二网络设备的集成多播路由，通过存储器302在集成多播路由表中保存第二网络设备的集成多播路由，则不需要预先编辑好集成多播路由表，可以动态地自动更新集成多播路由表，以满足不同时期的不同网络设备的需要，同时减少网络管理员的工作量，提高了工作效率。
处理器303还用于获得MEP ID范围或Session ID范围，MEP ID范围包括第二网络设备的MEP ID，或Session ID范围包括第二网络设备的Session ID，以使得第一网络设备可以限定具有特定MEP ID或Session ID的网络设备才能创建连通性检测会话。
在执行根据第二网络设备的会话信息与第二网络设备创建连通性检测会话的步骤之前，处理器303还可以确定第二网络设备的MEP ID在MEP ID范围之内，或，确定第二网络设备的Session ID在Session ID范围之内，则可以进行连通性检测会话的创建，否则可以不创建。
在一个具体的实施方式中，当第一网络设备与第二网络设备创建连通性检测会话之 后，处理器303还可以根据第一网络设备的MEP ID和第二网络设备的MEP ID确定故障统计报文的发送者和接收者，或根据第一网络设备的Session ID和第二网络设备的Session ID确定故障统计报文的发送者和接收者，其中，发送者为第一网络设备和第二网络设备中的一个，接收者为第一网络设备和第二网络设备中不同于发送者的一个。
需要说明的是，处理器303可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器303还可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。处理器303可以是指一个处理器，也可以包括多个处理器。收发器301用于接收来自第二网络设备的BGP路由信息，并将所述报文发送给处理器303，以便用于后续的操作处理。所述BGP路由信息包括目的地址、去往所述目的地址的下一跳地址和属性信息。所述属性信息指示所述第一网络设备对所述下一跳地址进行路由迭代处理的方式。存储器302可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器(英文：flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器还可以包括上述种类的存储器的组合。存储器302中存储有计算机可读指令，所述计算机可读指令包括至少一个软件模块。处理器303执行各个软件模块后可以按照各个软件模块的指示进行相应的操作。
请参考图4，本申请还提供了一种网络设备，用作第二网络设备400，第二网络设备400包括：
收发器401、存储器402和处理器403和总线404，其中，收发器401、存储器402和处理器403通过总线404连接。
处理器403用于执行存储器402中的计算机可读指令从而执行以下操作：
获得第二网络设备400的集成多播路由；向第一网络设备300发送连通性检测会话的创建消息，连通性检测会话的创建消息携带第二网络设备400的集成多播路由和会话信息，会话信息用于创建连通性检测会话。
由于仅需要在第二网络设备400的本地配置集成多播路由，就可以实现对第二网络设备400与EVPN网络中原有的各个网络设备进行连通性检测会话实例的配置，不需要对第二网络设备400与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，简化了配置流程。
在一个具体的实施方式中，第二网络设备400包括PE，以提供了EVPN网络中的各个PE之间创建连通性检测会话的方案，在该方案中，不需要对第一网络设备300与EVPN网络中现有的各个网络设备之间一一配置连通性检测会话的实例，简化了配置流程。
在一个具体的实施方式中，处理器403具体用于：
向EVPN网络中的各个网络设备广播或组播连通性检测会话的创建消息，则第二网络设备400仅需发送一份报文，而不需要对EVPN网络中的每一个网络设备发送，降低 了传输资源的负担，提高了传输的效率。
在一个具体的实施方式中，处理器403获得集成多播路由包括：
根据命令行的配置获得第二网络设备400的集成多播路由，因此网络管理员可以在网络设备本地输入集成多播路由表。
或，接收控制管理设备发送的集成多播路由，作为第二网络设备400的集成多播路由，因此网络管理员可以通过控制管理设备远程设置集成多播路由表。
由于可以向EVPN中的各个网络设备通告第二网络设备400的集成多播路由，则不需要预先编辑好集成多播路由表，可以动态地自动更新集成多播路由表，以满足不同时期的不同网络设备的需要，同时减少网络管理员的工作量。
在一个具体的实施方式中，处理器403可以EVPN网络中的各个网络设备广播或组播连通性检测会话的创建消息，则第二网络设备400仅需发送一份报文，而不需要对EVPN网络中的每一个网络设备发送，降低了传输资源的负担，提高了传输的效率。
在一个具体的实施方式中，处理器403向EVPN中的各个网络设备发送连通性检测会话的创建消息之后，处理器403还用于执行以操作：
接收第一网络设备300发送的连通性检测会话的响应报文，连通性检测会话的响应报文包括第一网络设备300的会话信息，并根据第一网络设备300的会话信息和第二网络设备400的会话信息确定故障统计报文的发送者和接收者，其中，发送者为第一网络设备300和第二网络设备400中的一个，接收者为第一网络设备300和第二网络设备400中不同于发送者的一个。
需要说明的是，处理器403可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器403还可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。处理器403可以是指一个处理器，也可以包括多个处理器。收发器401用于接收来自第二网络设备的BGP路由信息，并将所述报文发送给处理器403，以便用于后续的操作处理。所述BGP路由信息包括目的地址、去往所述目的地址的下一跳地址和属性信息。所述属性信息指示所述第一网络设备对所述下一跳地址进行路由迭代处理的方式。存储器402可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器(英文：flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器还可以包括上述种类的存储器的组合。存储器402中存储有计算机可读指令，所述计算机可读指令包括至少一个软件模块。处理器403执行各个软件模块后可以按照各个软件模块的指示进行相应的操作。
如图5所示，本申请还提供了一种系统500。包括第一网络设备300和第二网络设备400。第一网络设备300为上述图3所述的第一网络设备，第二网络设备400为上述图4所述的第二网络设备。有关系统500中各设备的详细描述，请参见上述图3和图4 等相关章节，此处不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质、或者半导体介质)等。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对 前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (27)

  1. 一种连通性检测会话的创建方法，其特征在于，用于EVPN网络，所述EVPN网络包括第一网络设备和第二网络设备，所述方法包括：
    所述第一网络设备接收来自所述第二网络设备的连通性检测会话的创建消息，所述连通性检测会话的创建消息中携带所述第二网络设备的集成多播路由和所述第二网络设备的会话信息；
    所述第一网络设备确定本地的集成多播路由表中包括所述第二网络设备的集成多播路由；
    所述第一网络设备根据所述第二网络设备的会话信息与所述第二网络设备创建所述连通性检测会话。
  2. 根据权利要求1所述方法，其特征在于，所述第一网络设备接收来自所述第二网络设备的连通性检测会话的创建消息包括：
    所述第一网络设备接收来自所述第二网络设备通过广播或组播的方式发送的连通性检测会话的创建消息。
  3. 根据权利要求1或2所述方法，其特征在于，所述第一网络设备接收来自所述第二网络设备的连通性检测会话的创建消息之前，还包括：
    所述第一网络设备获得所述集成多播路由表，所述集成多播路由表包括所述第二网络设备的集成多播路由。
  4. 根据权利要求1-3中任一项所述方法，其特征在于，所述连通性检测会话包括连接故障管理CFM会话。
  5. 根据权利要求1-4中任一项所述方法，其特征在于，所述连通性检测会话的创建消息中的类型长度值TLV字段中包括所述第二网络设备的集成多播路由，所述TLV字段包括类型、长度和值，其中，所述类型用于指示所述TLV字段的类型为集成多播路由，所述长度用于指示所述TLV字段的长度，所述值为所述第二网络设备的集成多播路由。
  6. 根据权利要求1-5中任一项所述方法，其特征在于，所述第二网络设备的会话信息包括所述第二网络设备的维护联盟边缘节点标识MEP ID或会话标识Session ID。
  7. 根据权利要求6所述方法，其特征在于，所述方法还包括：
    所述第一网络设备获得MEP ID范围或Session ID范围，所述MEP ID范围包括所述第二网络设备的MEP ID，或所述Session ID范围包括所述第二网络设备的Session ID；
    所述第一网络设备根据所述第二网络设备的会话信息与所述第二网络设备创建所述连通性检测会话之前，还包括：
    所述第一网络设备确定所述第二网络设备的MEP ID在所述MEP ID范围之内；
    或，所述第一网络设备确定所述第二网络设备的Session ID在所述Session ID范围之内。
  8. 一种连通性检测会话的创建方法，其特征在于，用于EVPN网络，所述EVPN网络包括第一网络设备和第二网络设备，所述方法包括：
    所述第二网络设备获得所述第二网络设备的集成多播路由；
    所述第二网络设备向所述第一网络设备发送连通性检测会话的创建消息，所述连通性检测会话的创建消息携带所述第二网络设备的集成多播路由和会话信息，所述会话信 息用于创建所述连通性检测会话。
  9. 根据权利要求8所述方法，其特征在于，所述第二网络设备向所述第一网络设备发送连通性检测会话的创建消息包括：
    所述第二网络设备向所述EVPN网络中的各个网络设备广播或组播所述连通性检测会话的创建消息。
  10. 根据权利要求8或9所述方法，其特征在于，所述连通性检测会话包括CFM会话。
  11. 根据权利要求8-10中任一项所述方法，其特征在于，所述连通性检测会话的创建消息中的TLV字段中包括所述第二网络设备的集成多播路由，所述TLV字段包括类型、长度和值，其中，所述类型用于指示所述TLV字段的类型为集成多播路由，所述长度用于指示所述TLV字段的长度，所述值为所述第二网络设备的集成多播路由。
  12. 根据权利要求8-11中任一项所述方法，其特征在于，所述第二网络设备的会话信息包括所述第二网络设备的MEP ID或Session ID。
  13. 一种网络设备，用作第一网络设备，其特征在于，包括：
    收发器、存储器和处理器；
    所述处理器用于执行所述存储器中的计算机可读指令从而执行以下操作：
    接收来自所述第二网络设备的连通性检测会话的创建消息，所述连通性检测会话的创建消息中携带所述第二网络设备的集成多播路由和所述第二网络设备的会话信息；
    确定本地的集成多播路由表中包括所述第二网络设备的集成多播路由；
    根据所述第二网络设备的会话信息与所述第二网络设备创建所述连通性检测会话。
  14. 根据权利要求13所述第一网络设备，其特征在于，所述处理器接收来自所述第二网络设备的连通性检测会话的创建消息包括：
    所述处理器接收来自所述第二网络设备通过广播或组播的方式发送的连通性检测会话的创建消息。
  15. 根据权利要求13或14所述第一网络设备，其特征在于，所述处理器还用于：
    获得所述集成多播路由表，所述集成多播路由表包括所述第二网络设备的集成多播路由。
  16. 根据权利要求13-15中任一项所述第一网络设备，其特征在于，所述连通性检测会话包括CFM会话。
  17. 根据权利要求13-16中任一项所述第一网络设备，其特征在于，所述连通性检测会话的创建消息中的TLV字段中包括所述第二网络设备的集成多播路由，所述TLV字段包括类型、长度和值，其中，所述类型用于指示所述TLV字段的类型为集成多播路由，所述长度用于指示所述TLV字段的长度，所述值为所述第二网络设备的集成多播路由。
  18. 根据权利要求13-17中任一项所述第一网络设备，其特征在于，所述第二网络设备的会话信息包括所述第二网络设备的MEP ID或Session ID。
  19. 根据权利要求13-18中任一项所述第一网络设备，其特征在于，所述处理器还用于：
    获得MEP ID范围或Session ID范围，所述MEP ID范围包括所述第二网络设备的MEP ID，或所述Session ID范围包括所述第二网络设备的Session ID；
    所述处理器接收来自所述第二网络设备的连通性检测会话的创建消息之前，所述处理器还用于：
    确定所述第二网络设备的MEP ID在所述MEP ID范围之内；
    或，确定所述第二网络设备的Session ID在所述Session ID范围之内。
  20. 一种网络设备，用作第二网络设备，其特征在于，所述第二网络设备包括：
    收发器、存储器和处理器；
    所述处理器用于执行所述存储器中的计算机可读指令从而执行以下操作：
    获得所述第二网络设备的集成多播路由；
    向所述第一网络设备发送连通性检测会话的创建消息，所述连通性检测会话的创建消息携带所述第二网络设备的集成多播路由和会话信息，所述会话信息用于创建所述连通性检测会话。
  21. 根据权利要求20所述第二网络设备，其特征在于，所述处理器向所述第一网络设备发送连通性检测会话的创建消息包括：
    所述处理器向所述EVPN 100中的各个网络设备广播或组播所述连通性检测会话的创建消息。
  22. 根据权利要求20或21所述第二网络设备，其特征在于，所述连通性检测会话包括CFM会话。
  23. 根据权利要求20-22中任一项所述第二网络设备，其特征在于，所述连通性检测会话的创建消息中的TLV字段中包括所述第二网络设备的集成多播路由，所述TLV字段包括类型、长度和值，其中，所述类型用于指示所述TLV字段的类型为集成多播路由，所述长度用于指示所述TLV字段的长度，所述值为所述第二网络设备的集成多播路由。
  24. 根据权利要求20-23中任一项所述第二网络设备，其特征在于，所述第二网络设备的会话信息包括所述第二网络设备的MEP ID或Session ID。
  25. 一种计算机可读介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-7中任一项所述的方法。
  26. 一种计算机可读介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求8-12中任一项所述的方法。
  27. 一种系统，其特征在于，所述系统包括如权利要求13-19中任一项所述的第一网络设备和如权利要求20-24中所述的第二网络设备。
PCT/CN2020/071795 2019-01-16 2020-01-13 一种连通性检测会话的创建方法、网络设备和系统 WO2020147683A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20741320.4A EP3893447A4 (en) 2019-01-16 2020-01-13 METHOD OF ESTABLISHING A CONNECTIVITY DETECTION SESSION AND NETWORK DEVICE AND SYSTEM
US17/375,348 US11863394B2 (en) 2019-01-16 2021-07-14 Connectivity detection session creation method, network device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910040453.X 2019-01-16
CN201910040453.XA CN111447130B (zh) 2019-01-16 2019-01-16 一种连通性检测会话的创建方法、网络设备和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/375,348 Continuation US11863394B2 (en) 2019-01-16 2021-07-14 Connectivity detection session creation method, network device, and system

Publications (1)

Publication Number Publication Date
WO2020147683A1 true WO2020147683A1 (zh) 2020-07-23

Family

ID=71614398

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/071795 WO2020147683A1 (zh) 2019-01-16 2020-01-13 一种连通性检测会话的创建方法、网络设备和系统

Country Status (4)

Country Link
US (1) US11863394B2 (zh)
EP (1) EP3893447A4 (zh)
CN (2) CN114363118A (zh)
WO (1) WO2020147683A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11425044B2 (en) * 2020-10-15 2022-08-23 Cisco Technology, Inc. DHCP layer 2 relay in VXLAN overlay fabric
CN114338459B (zh) * 2021-12-24 2024-02-13 迈普通信技术股份有限公司 路径检测方法、装置、网络设备及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090073988A1 (en) * 2007-09-14 2009-03-19 Morteza Ghodrat Systems and methods for a self-healing carrier ethernet topology
CN101785257A (zh) * 2007-03-01 2010-07-21 极进网络有限公司 用于交换机和路由器的软件控制平面
WO2014120758A1 (en) * 2013-01-29 2014-08-07 Cisco Technology, Inc. Using ethernet ring protection switching with computer networks
CN108462635A (zh) * 2016-12-09 2018-08-28 青岛璐琪信息科技有限公司 一种多宿网络中的通信网络路径和状态信息

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8767731B2 (en) * 2010-05-19 2014-07-01 Alcatel Lucent Method and apparatus for MPLS label allocation for a BGP MAC-VPN
US8953590B1 (en) * 2011-03-23 2015-02-10 Juniper Networks, Inc. Layer two virtual private network having control plane address learning supporting multi-homed customer networks
US8948169B2 (en) * 2011-12-07 2015-02-03 Cisco Technology, Inc. Mechanism for E-VPN interoperability with VPLS
CN104253759B (zh) * 2013-06-30 2017-08-29 华为技术有限公司 报文转发方法、装置及系统
US10833880B2 (en) * 2014-08-07 2020-11-10 Nokia Technologies Oy Controlled switching of multicast traffic between selective and inclusive routes based on number of multicast receivers
US10009218B2 (en) * 2016-04-01 2018-06-26 Nicira, Inc. Automatic setup of failure detection sessions
US10644987B1 (en) * 2016-04-04 2020-05-05 Juniper Networks, Inc. Supporting label per EVPN instance for an EVPN virtual private wire service
US10158567B1 (en) * 2016-04-14 2018-12-18 Cisco Technology, Inc. PBB-EVPN customer MAC synchronization among all-active multi-homing PEs
US10050873B2 (en) * 2016-05-17 2018-08-14 Juniper Networks, Inc. Egress node protection for broadcast, unknown unicast, or multicast traffic in EVPN topologies
WO2017221050A1 (en) * 2016-06-23 2017-12-28 Telefonaktiebolaget Lm Ericsson (Publ) Efficient handling of multi-destination traffic in multi-homed ethernet virtual private networks (evpn)
US10218627B2 (en) * 2016-06-30 2019-02-26 Juniper Networks, Inc. Disaggregated broadband network gateway functionality for efficient content delivery network peering
US10230535B2 (en) * 2016-07-29 2019-03-12 Juniper Networks, Inc. Communicating IGMP leave requests between load-balanced, multi-homed provider-edge routers in an ethernet virtual private network
CN107800602B (zh) * 2016-08-29 2021-01-15 华为技术有限公司 一种报文处理方法、设备及系统
US20180091445A1 (en) * 2016-09-29 2018-03-29 Juniper Networks, Inc. Evpn designated forwarder state propagation to customer edge devices using connectivity fault management
US10142239B2 (en) * 2017-02-27 2018-11-27 Juniper Networks, Inc. Synchronizing multicast state between multi-homed routers in an Ethernet virtual private network
CN108574616B (zh) * 2017-03-14 2021-02-12 华为技术有限公司 一种处理路由的方法、设备及系统
US10193812B2 (en) * 2017-03-31 2019-01-29 Juniper Networks, Inc. Multicast load balancing in multihoming EVPN networks
US10291532B1 (en) * 2017-06-29 2019-05-14 Juniper Networks, Inc. Enabling interconnection between ethernet virtual private networks (EVPNs) and provider backbone bridging EVPNs (PBB-EVPNs)
US10425325B2 (en) * 2017-10-30 2019-09-24 Dell Products Lp Optimizing traffic paths to orphaned hosts in VXLAN networks using virtual link trunking-based multi-homing
US11277281B2 (en) * 2017-12-18 2022-03-15 Telefonaktiebolaget Lm Ericsson (Publ) Provider edge device and method implemented thereon for ethernet virtual private network
WO2019134067A1 (en) * 2018-01-02 2019-07-11 Telefonaktiebolaget Lm Ericsson (Publ) Controlling device and method implemented thereon for ethernet virtual private network
US10630509B2 (en) * 2018-03-30 2020-04-21 Juniper Networks, Inc. Aliasing behavior for traffic to multihomed sites in ethernet virtual private network (EVPN) networks
US10924332B2 (en) * 2018-10-17 2021-02-16 Juniper Networks, Inc. Node protection for bum traffic for multi-homed node failure
US11349749B2 (en) * 2018-10-17 2022-05-31 Juniper Networks, Inc. Node protection for bum traffic for multi-homed node failure
US11323308B2 (en) * 2018-12-28 2022-05-03 Juniper Networks, Inc. Core isolation for logical tunnels stitching multi-homed EVPN and L2 circuit

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101785257A (zh) * 2007-03-01 2010-07-21 极进网络有限公司 用于交换机和路由器的软件控制平面
US20090073988A1 (en) * 2007-09-14 2009-03-19 Morteza Ghodrat Systems and methods for a self-healing carrier ethernet topology
WO2014120758A1 (en) * 2013-01-29 2014-08-07 Cisco Technology, Inc. Using ethernet ring protection switching with computer networks
CN108462635A (zh) * 2016-12-09 2018-08-28 青岛璐琪信息科技有限公司 一种多宿网络中的通信网络路径和状态信息

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN114363118A (zh) 2022-04-15
US11863394B2 (en) 2024-01-02
US20210344567A1 (en) 2021-11-04
CN111447130A (zh) 2020-07-24
EP3893447A4 (en) 2022-03-16
EP3893447A1 (en) 2021-10-13
CN111447130B (zh) 2021-12-14

Similar Documents

Publication Publication Date Title
US10148456B2 (en) Connecting multiple customer sites over a wide area network using an overlay network
EP3188409B1 (en) Oam mechanisms for evpn active-active services
US7995483B1 (en) Simultaneously testing connectivity to multiple remote maintenance endpoints of the same maintenance association
EP3065342B1 (en) Update of mac routes in evpn single-active topology
US11374857B2 (en) Network device management method and apparatus, and system for indicating a network device to perform management operation
EP3713162A1 (en) Route processing method and apparatus, and data transmission method and apparatus
EP3301861A1 (en) Evpn designated forwarder state propagation to customer edge devices using connectivity fault management
EP3425858B1 (en) Signaling multicast information to a redundant multi-homing router for a layer 2 virtual private network
US11611509B2 (en) Communication method, communications device, and communications system
US11799688B2 (en) Method for managing virtual private network, and device
WO2020168854A1 (zh) 一种evpn组播方法、装置及系统
US8675658B2 (en) Using multiple IGMP queriers in a layer 2 network
US11489752B2 (en) Forwarding entry monitoring method and apparatus
WO2020001389A1 (zh) 一种避免环路的通信方法、设备和系统
WO2014176989A1 (zh) 网络管理方法及系统、虚拟网络实体、网络设备
US11522792B2 (en) Method for discovering forwarding path and related device thereof
US11863394B2 (en) Connectivity detection session creation method, network device, and system
US8670299B1 (en) Enhanced service status detection and fault isolation within layer two networks
WO2021077991A1 (zh) 报文检测方法、连通性协商关系建立方法以及相关设备
CN111600737B (zh) 一种拓扑信息收集方法及网络设备

Legal Events

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

Ref document number: 20741320

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020741320

Country of ref document: EP

Effective date: 20210816

ENP Entry into the national phase

Ref document number: 2020741320

Country of ref document: EP

Effective date: 20210707