[go: up one dir, main page]

WO2019184653A1 - 链路配置方法和控制器 - Google Patents

链路配置方法和控制器 Download PDF

Info

Publication number
WO2019184653A1
WO2019184653A1 PCT/CN2019/076607 CN2019076607W WO2019184653A1 WO 2019184653 A1 WO2019184653 A1 WO 2019184653A1 CN 2019076607 W CN2019076607 W CN 2019076607W WO 2019184653 A1 WO2019184653 A1 WO 2019184653A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
site
template
controller
configuration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/076607
Other languages
English (en)
French (fr)
Inventor
陈建涛
许昌年
冯伟权
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP23165836.0A priority Critical patent/EP4266641A1/en
Priority to EP19774700.9A priority patent/EP3758294B1/en
Publication of WO2019184653A1 publication Critical patent/WO2019184653A1/zh
Priority to US17/030,839 priority patent/US11924004B2/en
Anticipated expiration legal-status Critical
Priority to US18/431,000 priority patent/US20240179027A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
    • 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/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5061—Pools of addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements

Definitions

  • the present application relates to the field of communications, and in particular, to a link configuration method and a controller.
  • a software-defined wide area network is a network technology used for inter-branch interconnection.
  • the SD-WAN monitors the quality of different WAN links and transmits different network traffic over different quality links according to the policy specified by the tenant (the enterprise using the SD-WAN solution) to reduce the link usage of the tenant. The purpose of the cost.
  • the network devices at the branch of the enterprise form a branch site
  • the network devices at the headquarters are composed of the headquarters site.
  • the interconnection between the branch site and the headquarters site, or the interconnection between the branch sites is implemented by creating a dynamic smart virtual private network (DSVPN) tunnel.
  • the branch and the access router (AR) of the headquarters are registered to the controller, and the controller manages the AR and VPN of each station.
  • the administrator of the tenant needs to manually create the tunnel interface configuration parameters of the DSVPN on the controller, including the site type, the device corresponding to the site, the logical link type, and the physical interface and logical link on which the logical link depends. Parameters such as address related parameters, upstream bandwidth, and/or downstream bandwidth.
  • the controller sends the link configuration parameter corresponding to the logical link to the AR of the station according to the logical link information of the site configured by the tenant, and the AR of the station can obtain the link configuration parameter according to the link.
  • the configuration parameters create a DSVPN tunnel.
  • the embodiment of the present application provides a link configuration method, which is used to automatically generate a link configuration parameter according to a link template, and send a site device to create a DSVPN.
  • a first aspect of the embodiments of the present application provides a link configuration method, including:
  • SD-WAN technology can be used between the enterprise headquarters and branches to establish DSVPN tunnels between sites for communication.
  • the network device at the branch of the enterprise is a branch site.
  • the network device at the headquarters is the headquarters site.
  • the site AR is registered on the controller.
  • the link template library is preset on the controller.
  • the link template library includes multiple link templates.
  • the link profile contains information such as the gateway type, link type, link name, and the WAN physical port number of the gateway.
  • the controller needs to obtain the first link template selected by the tenant from the link template library for the first site and the second link template selected for the second site; in addition, the controller needs to acquire the controller preset Global configuration information, which contains the address pool of the link, which can be used to assign an IP address to the tunnel interface.
  • the controller generates a first link configuration parameter of the first site and a second link of the second site according to a preset link configuration rule according to the first link template, the second link template, and the address pool selected by the tenant.
  • the configuration parameter finally, the controller sends the first link configuration parameter to the first station; and sends the second link configuration parameter to the second station.
  • the link template, the global configuration information, and the association policy of the link are preset on the controller.
  • the tenant When generating a DSVPN tunnel interface configuration, the tenant only needs to select the site type and the site template according to the current requirements.
  • the controller can automatically create the tunnel configuration parameters required for the logical link according to the link configuration rule.
  • the application is implemented.
  • the method provided by the example can improve the automation of the link configuration, reduce the manual workload, and reduce the burden on the tenant.
  • the method further includes: acquiring, by the controller, a site type of the first site and the second site; If the site type of the first site or the second site is the headquarters site, the controller obtains the public IP address of the headquarters site.
  • the controller after the controller obtains the site type of the first site or the second site as the headquarters site, the controller can obtain the public network IP address configured by the tenant for the headquarters site, and is used to indicate the headquarters access.
  • the gateway interface of the router The link configuration method provided by the embodiment of the present application provides another situation for generating link configuration parameters, which enhances the flexibility of implementation of the solution.
  • the link template further includes: Bandwidth and/or downstream bandwidth.
  • the link configuration method provided by the embodiment of the present application may include the uplink bandwidth and/or the downlink bandwidth of the site gateway link in the link template, which enhances the flexibility of implementation.
  • the preset link configuration rule includes: Name matching and/or link type matching; wherein when the preset link configuration rule includes multiple rules, the prior rule has a higher priority than the later rule.
  • the link configuration method provided by the embodiment of the present application provides a specific example of a preset link configuration rule, which improves the feasibility of implementing the solution.
  • the controller when the preset link configuration rule includes link name matching and link type matching, Generating the first link configuration parameter of the first site and the second link configuration parameter of the second site according to the preset link configuration rule, the controller determining the first link template and the second link Whether there are two links with the same link name in the route template; when the link name of the first link in the first link template and the second link in the second link template are the same, the control The first link and the second link are configured as a logical link, and the link interface IP address of the logical link is respectively allocated to the first site and the second site according to the address pool, and the a first link configuration parameter and the second link configuration parameter; if the first link template and the second link template do not have two links with the same link name, the controller determines the first chain Whether there is a link in the route template and the second link template Two links of the same type; when the link type of the
  • the embodiment of the present application provides a specific implementation manner of a preset link configuration rule.
  • the link with the same link name can be preferentially determined. If not, the link with the same link type is determined.
  • Link orchestration provides a specific way to implement link configuration, which improves the achievability of the solution.
  • the controller configures the third link and the fourth link as one logical link.
  • the method includes: if there are multiple third links and/or multiple fourth links, the controller acquires a target third link and a target fourth link with the closest bandwidth, and the target third link and The target fourth link is configured as a logical link.
  • the controller determines a specific arrangement mode of the link according to the bandwidth, and provides a preset link configuration rule.
  • a second aspect of the embodiments of the present application provides a controller having a function of implementing the link configuration method in the above first aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a third aspect of the embodiments of the present application provides a controller, including: a processor, a memory, the processor executing the foregoing by running a software program stored in the memory, calling data stored in the memory The method of each of the embodiments provided by the first aspect of the embodiments is applied.
  • a fourth aspect of the present application provides a computer program product, the computer program product comprising computer program instructions, the computer program instructions being loadable by a processor to implement the first aspect and the methods in the implementation manners.
  • a fifth aspect of the embodiments of the present application provides a computer storage medium for storing computer program instructions, including a program for performing the steps of the foregoing embodiments provided by the first aspect of the embodiments of the present application.
  • FIG 1 shows the architecture of the SD-WAN solution
  • FIG. 2 is a schematic diagram of an embodiment of a link configuration method in an embodiment of the present application.
  • FIG. 3 is a schematic diagram of another embodiment of a link configuration method in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a topology map of a WAN side of a site in the embodiment of the present application;
  • FIG. 5 is a structural diagram of a corporate headquarters and a branch network in the embodiment of the present application.
  • FIG. 6 is a schematic diagram of an embodiment of a controller in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another embodiment of a controller in an embodiment of the present application.
  • An overlay network is built between the enterprise branch sites (such as Spoke1, Spoke2, and Spoke3) and the headquarters site (such as the HUB).
  • the headquarters site and branch sites, and the branch sites are interconnected by DSVPN tunnels.
  • Each DSVPN tunnel corresponds to a logical link, and the logical link is identified by the interface of the DSVPN tunnel.
  • the logical link type of each DSVPN tunnel may be Internet, Multiprotocol Label Switching (MPLS), Long-Term Evolution (LTE), or the like.
  • the interconnection between the sites is implemented by the ARs of the sites.
  • the ARs of the headquarters sites and the branch sites are respectively registered with the controllers.
  • the controllers are responsible for sending the link configuration parameters to the ARs at different sites.
  • the controller sends the link configuration parameter to the AR of the branch site (hereinafter referred to as the spoke AR).
  • each spoke AR After receiving the corresponding link configuration parameter, each spoke AR sends the next to the AR of the headquarters station (hereinafter referred to as the HUB AR).
  • the next Hop Resolution Protocol request is sent to the HUB AR of the public IP address of the outbound interface.
  • the HUB AR After receiving the NHRP request, the HUB AR creates or updates the NHRP peer entry (NHRP peer) entry of the spoke AR. .
  • the source spoke AR queries the next hop of the destination spoke AR in the routing table.
  • the source spoke AR If the NHRP peer of the source spoke AR does not query the public IP address corresponding to the next hop, the source spoke The AR sends an NHRP address resolution request to the HUB AR to obtain the public IP address of the destination spoke AR.
  • the two spoke ARs then dynamically create a VPN tunnel through the multipoint generic routing encapsulation (mGRE) interface, so that data can be directly transmitted between the two branches.
  • mGRE multipoint generic routing encapsulation
  • FIG. 2 is a schematic flowchart diagram of a link configuration method according to an embodiment of the present application.
  • the controller acquires a site type of the first site and the second site.
  • the network devices where the enterprise branch is located form a branch site, and the network devices at the headquarters are composed of the headquarters site.
  • the branch site and the AR of the headquarters site are respectively registered to the controller, and the controller manages the AR and VPN of each site.
  • An overlay network usually includes a headquarters site and at least one branch site.
  • the site type can be a headquarters site or a branch site.
  • the site type of the first site and the second site can be a headquarters site and a branch site, or two branches.
  • the site, wherein the site types of the first site and the second site are not specifically limited herein.
  • the controller obtains the site types of the first site and the second site respectively according to the input or selection of the tenant.
  • the controller acquires a first link template selected by the tenant from the link template library for the first site and a second link template selected for the second site.
  • the link template library is preset in the controller, and includes multiple link templates.
  • the specific number of link templates is not limited here.
  • the link template is a topology map template on the WAN side of the site preset in the controller, including the gateway type, link type, link name, and WAN physical port number of the gateway.
  • the gateway type includes a single gateway or a dual gateway.
  • the link type identifies the link type provided by the Internet service provider (ISP).
  • the link type can be Internet, MPLS, or LTE.
  • the link name can be customized, for example, by link type and ISP.
  • the ISP can be, for example, China Mobile Communications Corporation (CMCC), and the link name can be Internet-CMCC or MPLS-CMCC, for example.
  • the name can also be in other forms.
  • one site includes at least one AR.
  • the physical port number of the WAN on the gateway is the physical port information bound to the logical link.
  • the link profile may further include an uplink bandwidth and/or a downlink bandwidth and a public network IP address
  • the link template may include a specific uplink bandwidth and/or a downlink bandwidth, for example, 20M or 100M may also directly use the default uplink bandwidth.
  • the specific form of the downlink bandwidth, the uplink bandwidth, and/or the downlink bandwidth is not limited herein.
  • the public network IP address is used to indicate the gateway interface of the headquarters access router. You need to configure the public IP address for the headquarters site. You do not need to configure the public IP address for the branch site.
  • the IP address of the public network can be preset in the link profile. After the controller obtains the link profile of the headquarters site, the administrator can enter the IP address of the public network at the headquarters site.
  • the controller obtains a first link template selected by the tenant for the first station and a second link template selected for the second station.
  • an access router acts as a gateway to a site to communicate with access routers at other sites.
  • the tenant selects the corresponding template based on the gateway type and link type of the site, such as a single gateway Internet link template or a dual gateway hybrid single link template.
  • the controller acquires preset global configuration information.
  • the preset global configuration information includes an address pool of the logical link.
  • the controller allocates an IP address for the AR of the first site and the AR of the second site according to the address pool.
  • the controller generates the first link configuration parameter of the first site and the second site according to the preset link configuration rule according to the address pool, the first link template, and the second link template. Second link configuration parameter.
  • the controller obtains the first link template of the first site and the second link template of the second site, where the link template of the site includes information of at least one link, and the controller can follow the link between the different sites.
  • the preset link configuration rules are configured as logical links.
  • the preset link configuration rules may include link name matching and/or link type matching.
  • the link name matching refers to configuring two links with the same link name in two different link templates as one logical link; the link type matching refers to the two different link templates. Two links with the same link type are configured as one logical link.
  • Other rules can also be included in the preset link configuration rules. When the preset link configuration rule includes multiple rules, the prior rule has a higher priority than the later rule.
  • the controller determines whether there are two links with the same link name in the first link template and the second link template.
  • the controller configures the first link and the second link And is a logical link, and the link interface IP address of the logical link is respectively allocated to the first site and the second site according to the address pool, to obtain the first link configuration parameter and the second link configuration parameter. ;
  • the controller determines whether the link type is the same in the first link template and the second link template. Two links.
  • the controller configures the third link and the fourth link as one
  • the first link configuration parameter and the second link configuration parameter are obtained by assigning a link interface IP address of the logical link to the first site and the second site according to the address pool.
  • the controller sends the first link configuration parameter to the first station and sends the second link configuration parameter to the second station.
  • the sending manner may be: the controller generates a NETCONF packet for the first site and the second site according to the link configuration parameter, and then sends the corresponding NETCONF packet to the first site and the second node respectively. Site.
  • the link template, the global configuration information, and the preset link configuration rule are preset on the controller.
  • the controller can automatically configure the tunnel configuration parameters required to create the logical link according to the link configuration rule.
  • the method provided by the embodiment of the present application can improve the automation degree of the link configuration and reduce the manual. Workload to reduce the burden on tenants.
  • FIG. 3 a schematic diagram of another embodiment of a link configuration method in this embodiment of the present application:
  • the controller acquires a site type of the first site and the second site.
  • An overlay network usually includes a headquarters site and at least one branch site, and the combination of the site types of the first site and the second site may be a headquarters site and a branch site, or two branch sites, where the first site and the first site
  • the site type of the second site is not limited herein.
  • the controller obtains the site types of the first site and the second site respectively according to the input or selection of the tenant.
  • the controller may acquire the site type of multiple sites, for example, the controller acquires four sites selected by the tenant, and selects the site type as the headquarters, the branch, and the branch respectively.
  • the branch that is, the overlay network, includes one headquarters station (HUB) and three branch sites (Spoke1, Spoke2, and Spoke3).
  • Step 301 is an optional step of the present application.
  • the controller obtains a public network IP address of the headquarters site.
  • the public network IP address is used to indicate the gateway interface of the headquarters access router. You need to configure the public IP address for the headquarters site. You do not need to configure the public IP address for the branch site.
  • the IP address of the public network can be preset in the link profile. After the controller obtains the link profile of the headquarters site, the administrator can enter the IP address of the public network at the headquarters site.
  • step 302 may be performed before any of the steps 303 to 306, and the specific execution sequence is not limited herein.
  • the controller acquires a first link template selected by the tenant from the link template library for the first site and a second link template selected for the second site.
  • the link template library is preset in the controller, and includes multiple link templates.
  • the specific number of link templates is not limited here.
  • the link template is a topology map template on the WAN side of the site preset in the controller, including the gateway type, link type, link name, and WAN physical port number of the gateway.
  • the gateway type includes a single gateway or a dual gateway.
  • the link type identifies the link type provided by the Internet service provider (ISP).
  • the link type can be Internet, MPLS, or LTE.
  • the link name can be customized, for example, by link type and ISP.
  • the ISP can be, for example, China Mobile Communications Corporation (CMCC), and the link name can be Internet-CMCC or MPLS-CMCC, for example.
  • the name can also be in other forms.
  • one site includes at least one AR.
  • the physical port number of the WAN on the gateway is the physical port information bound to the created logical link.
  • the link profile may further include an uplink bandwidth and/or a downlink bandwidth
  • the link template may include a specific uplink bandwidth and/or a downlink bandwidth, for example, 20M, 100M, etc., or may directly use a default uplink bandwidth and/or
  • the specific values of the downlink bandwidth, the uplink bandwidth, and/or the downlink bandwidth are not limited herein.
  • IPsec Internet Protocol Security
  • the form of the link template library can be a list, for example:
  • the link profile can also visually display the gateway type and link type of the site in the form of a WAN topology of the site. See Figure 4, Template 1: Single Gateway Hybrid Dual Link; Template 2: Single Gateway MPLS Link; Template III : Single Gateway Internet Link; Template 4: Dual Gateway Mixed Single Link; Template 5: Single Gateway Dual Internet Link.
  • link template can be in multiple forms, which is not limited herein.
  • a site's access router acts as a gateway to the site to communicate with access routers at other sites.
  • the tenant selects a matching template based on the gateway type and link status of the site.
  • FIG. 5 the network architecture diagram of the enterprise headquarters and branches.
  • the link template of the Spoke2 site and the Spoke3 site can be:
  • the HUB site, the link template is a dual gateway hybrid dual link:
  • a site with a gateway type of dual gateways generally distinguishes between two gateways based on gateway device entries.
  • the link template is a single gateway hybrid dual link:
  • the link template is a single gateway MPLS link:
  • the link template is a single gateway Internet link:
  • the controller acquires preset global configuration information.
  • the preset global configuration information includes an address pool of the logical link, and the address pool obtained by the controller may be, for example, 172.16.1.0/16.
  • the specific IP information of the address pool is not limited here.
  • the global configuration information may be used to allocate the IP addresses of the site access routers to the first site and the second site respectively when the controller generates the link configuration information.
  • step 304 may be performed before any of the steps 301 to 306, and the specific execution sequence is not limited herein.
  • the controller determines whether two links with the same link name exist in the first link template and the second link template.
  • a link profile contains information about at least one link. After the controller obtains the link profile information of the first site and the second site, the link between the different sites can be configured according to a preset link configuration rule.
  • the link name is composed of the link type and the Internet service provider ISP information
  • the controller can determine whether there is a first link and a second link with the same link name, and the first link is the first link.
  • Link information in the template, the second link is link information in the second link template.
  • the gateway type and link type of the headquarters site and the three branch sites in Figure 5 are taken as an example.
  • the controller determines that the tenant is a HUB site, a Spoke1 site, Whether the link with the same link name exists in the link template determined by the Spoke2 site and the Spoke3 site respectively.
  • a link name of the link name "MPLS-CMCC" exists in the link profile of the HUB site, the link profile of the Spoke1 site, and the link profile of the Spoke2 site. Therefore, Go to step 306.
  • the controller configures the first link and the second link as a logical chain.
  • the first link configuration parameter and the second link configuration parameter are obtained by assigning the link interface IP address of the logical link to the first site and the second site respectively according to the address pool.
  • the controller configures the first link and the second link as one logical link. And assigning an IP address to the gateway interfaces at both ends of the link according to the address pool obtained in step 302, and finally obtaining the first link configuration parameter and the second link configuration parameter.
  • the controller obtains the link profile of the HUB site and the Spoke1 site.
  • the controller can find the link between the link template of the HUB site and the Spoke1 site.
  • the MPLS-CMCC link in the link profile of the HUB site and the MPLS-CMCC link in the link profile of the Spoke1 site are configured as one link type.
  • the logical link of the "MPLS" link is configured as the endpoint of the "MPLS" logical link, that is, the AR interface 2 of the HUB site and the AR device 2 of the Spoke1 site are respectively configured with the link interface IP address, which is generated for the HUB site.
  • the first link configuration parameters including the physical port number and the link interface IP address of the HUB AR
  • the second link configuration parameters of the Spoke1 site including the physical port number, the link interface IP address of the Spoke1AR, and the point to the HUB site
  • the IP address of the AR device 1 and the public IP address of the HUB site are generated, and the first NETCONF packet is sent to the HUB AR according to the first link configuration parameter, and the second NETCONF packet is generated according to the second link configuration parameter.
  • Spoke1AR .
  • the controller finds that the link name of the link between the HUB site and the Spoke1 site is "Internet-CMCC", and the link between the "Internet-CMCC” link and the Spoke1 site in the link profile of the HUB site.
  • the "Internet-CMCC” link in the template is configured as a logical link with the link type "Internet” and is based on the address pool as the endpoint of the "Internet” logical link, that is, the AR device 1 and the Spoke1 site of the HUB site.
  • the AR device 1 configures the link interface IP address to obtain the first link configuration parameters (including the physical port number and the link interface IP address of the HUB AR) generated by the HUB site and the second link configuration parameters of the Spoke1 site.
  • the physical port number, the IP address of the link interface of the Spoke1AR, the IP address of the AR device 1 and the public network IP address of the HUB site, and the first NETCONF packet is sent to the HUB AR according to the first link configuration parameter. And generating a second NETCONF message according to the second link configuration parameter and sending the message to the Spoke1AR.
  • the controller finds that the link name of the link between the HUB site and the Spoke2 site is "MPLS-CMCC", and the controller connects the "MPLS-CMCC” link in the link profile of the HUB site.
  • the "MPLS-CMCC” link in the link profile of the Spoke2 site is configured as a link type of "MPLS" logical link. Since the HUB site has been configured with an "MPLS" logical link between the site and the Spoke1 site, The link parameters are configured for the HUB site. Therefore, the controller can configure the link interface IP address according to the address pool only for the AR of the Spoke2 site at the other end of the "MPLS" logical link, and obtain the second link configuration of the Spoke2 site.
  • the parameter includes the physical port number, the link interface IP address of the Spoke2AR, the IP address of the AR device 2 pointing to the HUB site, and the public IP address of the HUB site, and generates a second NETCONF packet according to the second link configuration parameter. Give Spoke2AR.
  • the controller determines whether the link type is the same in the first link template and the second link template. Two links.
  • the controller determines whether two links of the same link type are present in the first link template and the second link template.
  • the links are the third link and the fourth link, and the third link is a link in the first link template, and the fourth link is a link in the second link template.
  • the controller determines the chain of the HUB site. Whether there is a link with the same link type in the link template of the route template and the Spoke3 site.
  • the controller configures the third link and the fourth link as one logic. Linking, and assigning, by the address pool, the link interface IP address of the logical link to the first site and the second site respectively, to obtain the first link configuration parameter and the second link configuration parameter.
  • the controller configures the third link and the fourth link as one logical link And assigning the link interface IP address according to the address pool obtained in step 302, obtaining the first link configuration parameter and the second link configuration parameter, and generating a NETCONF packet according to the link configuration parameter.
  • the link profile of the HUB site and the Spoke3 site has the same link type as the Internet.
  • the controller obtains the HUB site and the Spoke3 site.
  • the link type of the link is "Internet” in the link profile of the HUB site and the Spoke3 site.
  • the link between the Internet link and the Spoke3 site in the link profile of the HUB site is used.
  • the "Internet" link in the template is configured as an "Internet” logical link
  • the link interface IP is configured on the AR of the ARB and the AR of the Spoke3.
  • the controller can no longer configure the link interface for the HUB site. IP address, and first link configuration parameters.
  • the controller can obtain the uplink of the link from the link template.
  • the bandwidth and/or downlink bandwidth information is selected to be the closest one to the uplink bandwidth and/or the downlink bandwidth value of the Internet link of the HUB site, and is configured as a logical Internet link with the Internet link of the HUB site.
  • the controller sends the first link configuration parameter to the first station and sends the second link configuration parameter to the second station.
  • the sending manner may be: the controller generates a first NETCONF packet according to the first link configuration parameter, generates a second NETCONF packet according to the second link configuration parameter, and then respectively, the first NETCONF packet
  • the message and the second NETCONF message are sent to the first site and the second site.
  • the "MPLS" link created between the HUB site and the Spoke1 site is configured as follows for each site:
  • interface tunnel0/0/0 represents the interface of one end of the link (that is, the AR device 2 of the HUB site), and "ip address 172.16.1.1 255.255.255.0” is the IP address assigned by the controller from the address pool.
  • the link of the link is on the HUB site side;
  • source GigabitEthernet0/0/2 represents the Gigabit Ethernet interface number;
  • nhrp "redirect” represents the NHRP redirection for the headquarters site;
  • nhrp entry multicast dynamic means that the branch configured with dynamic registration joins the NHRP multicast member table.
  • the "nhrp entry 172.16.1.1 202.1.1.10 register" is the tunnel IP address and the public IP address (public IP) of the headquarters.
  • the NHRP registration request can be sent to the public IP address of the headquarters;
  • the nhrp shortcut command is used to save the route to the divquarters.
  • the next hop of the route from the source branch to the destination subnet is the tunnel address of the divquarters.
  • Other items have similar meanings to the configuration parameters of the headquarters, and are not described here.
  • the two types of logical link parameters are configured on the Spoke1 site of a single gateway.
  • the physical interface numbers can be distinguished. The specific meanings of other parameters are not mentioned here.
  • An "Internet” link is created between the HUB site and the Spoke3 site.
  • the link configuration is generated on the Spoke3 side because the link configuration is generated on the Spoke3 side.
  • Each station obtains configuration parameters based on the packets sent by the controller, and creates a VPN tunnel in a dynamic manner to perform data transmission between sites.
  • the link template, the global configuration information, and the preset link configuration rule are preset on the controller.
  • the tenant When generating a DSVPN tunnel interface configuration, the tenant only needs to select the site type and site template according to the current requirements.
  • the controller can automatically create the tunnel configuration parameters required for the logical link according to the template matching rule, and can also preset different chains according to actual conditions.
  • the path orchestration strategy is to link links with the same link type and the same ISP, or to link links with the same link type and close bandwidth.
  • the method provided in the embodiment of the present application can improve the automation degree of the link configuration, reduce the manual workload, and reduce the burden on the tenant.
  • the foregoing embodiment describes the link configuration method of the present application.
  • the following describes the controller for implementing the link configuration method. Referring to FIG. 6, a schematic diagram of an embodiment of the controller of the present application is shown.
  • the controller includes:
  • the first obtaining unit 601 is configured to acquire a first link template selected by the tenant from the link template library for the first station, and a second link template selected for the second station, where the link template library includes multiple link templates.
  • Each link template of the multiple link templates includes a gateway type, a link type, a link name, and a WAN side physical port number of the gateway;
  • the second obtaining unit 602 is configured to acquire preset global configuration information, where the global configuration information includes an address pool of the link.
  • the generating unit 603 is configured to generate, according to the address pool, the first link template, and the second link template, the first link configuration parameter of the first site and the second site according to a preset link configuration rule. Second link configuration parameter;
  • the generating unit 603 is specifically configured to:
  • the sending unit 604 is configured to send the first link configuration parameter to the first station; and send the second link configuration parameter to the second station.
  • the first obtaining unit 601 is further configured to:
  • the public network IP address of the headquarters site is obtained.
  • the generating unit 603 is further configured to:
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, can be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method of various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the device 700 may be a controller or a part thereof.
  • the controller 700 can vary considerably depending on configuration or performance, and can include one or more central processing units (CPUs) 701 (eg, one or more other types of processors) and memory 705.
  • CPUs central processing units
  • memory 705. One or more applications or data are stored in the memory 705.
  • the memory 705 can be volatile storage or persistent storage.
  • the program stored in memory 705 can include one or more modules, each of which can include a series of instruction operations in the controller.
  • central processor 701 can be configured to communicate with memory 705, executing a series of instruction operations in memory 705 on controller 700.
  • Controller 700 may also include one or more power sources 702, one or more wired or wireless network interfaces 703, one or more input and output interfaces 704, and/or one or more operating systems.
  • the various portions of controller 700 can form an entire chip or a plurality of individual chips.
  • the process performed by the central processing unit 701 in the controller 700 in this embodiment is similar to the method flow described in the foregoing embodiment shown in FIG. 2 or FIG. 3, and details are not described herein again.
  • the embodiment of the present application further provides a computer storage medium for storing computer program instructions used by the controller, which includes a program for executing a controller.
  • the embodiment of the present application further provides a computer program product, which includes computer program instructions, which can be loaded by a processor to implement the method flow in the foregoing embodiment shown in FIG. 2 or FIG.

Landscapes

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

Abstract

本申请实施例公开了一种链路配置方法，用于配置DSVPN隧道接口参数。控制器获取租户从链路模板库为第一站点选择的第一链路模板和为第二站点选择的第二链路模板，链路模板库包括多个链路模板，多个链路模板中的每个链路模板包含网关类型、链路类型、链路名称和网关的广域网侧物理端口号；控制器获取预置的全局配置信息，全局配置信息中包含链路的地址池；控制器根据地址池、第一链路模板和第二链路模板，按照预设的链路配置规则生成第一站点的第一链路配置参数和第二站点的第二链路配置参数；控制器向第一站点发送第一链路配置参数；以及，控制器向第二站点发送第二链路配置参数。

Description

链路配置方法和控制器
本申请要求于2018年3月28日提交中国专利局、申请号为201810265042.6、发明名称为“链路配置方法和控制器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，特别涉及链路配置方法和控制器。
背景技术
软件定义广域网(software-defined wide area network，SD-WAN)，是一种用于企业分支间互联的网络技术。SD-WAN通过监控不同广域网链路的质量，并根据租户(指使用SD-WAN解决方案的企业)指定的策略，将不同的网络流量通过不同质量的链路传输，达到降低租户的链路使用成本的目的。
SD-WAN解决方案中，企业分支所在地的网络设备组成分支站点(site)，总部所在地的网络设备组成总部站点。分支站点与总部站点之间互联，或者分支站点之间互联都是通过创建动态智能虚拟专用网络(dynamic smart virtual private network，DSVPN)隧道(tunnel)实现。分支与总部的接入路由器(access router，AR)注册到控制器上，控制器管理各站点的AR和VPN等。建立DSVPN之前，租户的管理员需要手动在控制器上创建DSVPN对应的tunnel接口配置参数，包括：站点类型、站点对应的设备、逻辑链路类型、逻辑链路所依赖的物理口、逻辑链路地址相关参数、上行带宽和/或下行带宽等参数。控制器依据租户所配置的站点的逻辑链路信息，向该站点的AR发送该逻辑链路对应的链路配置参数，该站点的AR在收到该链路配置参数后即可根据该链路配置参数创建DSVPN隧道。
现有技术中，建立DSVPN隧道需要租户的管理员手动输入链路的配置参数，自动化程度低，人工工作量大。
发明内容
本申请实施例提供了链路配置方法，用于根据链路模板自动生成链路配置参数，下发站点设备创建DSVPN。
本申请实施例第一方面提供了一种链路配置方法，包括：
企业总部与分支之间可以利用SD-WAN技术，在站点间通过创建DSVPN隧道进行通信。企业分支所在地的网络设备组成分支站点，总部所在地的网络设备组成总部站点，站点AR注册到控制器上，控制器上预置链路模板库，链路模板库包括多个链路模板，其中每个链路模板包含网关类型、链路类型、链路名称和网关的广域网侧物理端口号等信息。首先，控制器需先获取租户从链路模板库为第一站点选择的第一链路模板和为该第二站点选择的第二链路模板；此外，控制器还需获取预置于控制器中的全局配置信息，其中包含了链路的地址池，可用于为隧道接口分配IP地址。控制器根据租户选择的第 一链路模板、第二链路模板和地址池根据预设的链路配置规则生成该第一站点的第一链路配置参数和该第二站点的第二链路配置参数，最后，控制器向该第一站点发送该第一链路配置参数；并向该第二站点发送该第二链路配置参数。
根据本申请实施例提供的链路配置方法，控制器上预置了链路模板、全局配置信息和链路的编排策略算法(即链路配置规则)。在生成DSVPN隧道接口配置时，租户只需要根据当前需要选择站点类型和站点模板，控制器可以自动根据链路配置规则创建逻辑链路所需的tunnel配置参数，相较现有技术，本申请实施例提供的方法可提升链路配置的自动化程度，降低人工工作量，减轻租户的负担。
基于本申请实施例第一方面，本申请实施例第一方面的第一种实施方式中，该方法还包括：该控制器分别获取该第一站点和该第二站点的站点类型；若该第一站点或第二站点的站点类型为总部站点，则该控制器获取该总部站点的公网IP地址。
本申请实施例提供的链路配置方法，当控制器获取第一站点或第二站点的站点类型为总部站点后，可以获取租户为该总部站点配置的公网IP地址，用于指示总部接入路由器的网关接口。本申请实施例提供的链路配置方法提供了生成链路配置参数的另一种情况，增强了方案实现的灵活性。
基于本申请实施例第一方面或本申请实施例第一方面的第一种实施方式，本申请实施例第一方面的第二种实施方式中，其特征在于，该链路模板还包括：上行带宽和/或下行带宽。
本申请实施例提供的链路配置方法，在链路模板中可以包含站点网关链路的上行带宽和/或下行带宽，增强了方案实现的灵活性。
基于本申请实施例第一方面或本申请实施例第一方面的第一种实施方式，本申请实施例第一方面的第三种实施方式中，该预设的链路配置规则包括：链路名称匹配和/或链路类型匹配；其中，当该预设的链路配置规则包括多种规则时，在先的规则的优先级高于在后的规则的优先级。
本申请实施例提供的链路配置方法，提供了预设的链路配置规的具体的例子，提升了方案实现的可行性。
基于本申请实施例第一方面的第三种实施方式，本申请实施例第一方面的第四种实施方式中，当该预设的链路配置规则包括链路名称匹配和链路类型匹配时，该按照预设的链路配置规则生成该第一站点的第一链路配置参数和该第二站点的第二链路配置参数包括：该控制器确定该第一链路模板和第二链路模板中是否存在链路名称相同的两条链路；当该第一链路模板中的第一链路和该第二链路模板中的第二链路的链路名称相同时，该控制器将该第一链路和该第二链路配置为一条逻辑链路，并根据该地址池为该第一站点和该第二站点分别分配该逻辑链路的链路接口IP地址，得到该第一链路配置参数和该第二链路配置参数；若该第一链路模板和第二链路模板中不存在链路名称相同的两条链路，则该控制器确定该第一链路模板和第二链路模板中是否存在链路类型相同的两条链路；当该第一链路模板中的第三链路和该第二链路模板中的第四链路的链路类型相同时，该控制器将该第三链路和第四链路配置为一条逻辑链路，并根据该地址池为该第一站点和该第二站点分别分配该逻辑链路的链路接口IP地址，得到该第一链路配置参数和该第二链路配置参数。
本申请实施例提供了预设的链路配置规则的具体实现方式，可以通过优先确定链路名称相同的链路，若不存在时，再确定链路类型相同的链路，根据这一规则进行链路编排，提供了链路配置实现的一种具体方式，提升了方案的可实现性。
基于本申请实施例第一方面的第四种实施方式，本申请实施例第一方面的第五种实施方式中，该控制器将该第三链路和第四链路配置为一条逻辑链路包括：若存在多个第三链路和/或多个第四链路，则该控制器获取带宽最接近的目标第三链路和目标第四链路，并将该目标第三链路和目标第四链路配置为一条逻辑链路。
本申请实施例中当存在多个第三链路和/或多个第四链路时，控制器根据带宽确定链路的一种具体的编排方式，提供了预设的链路配置规则的又一种方式，提升了方案实现的灵活性。
本申请实施例第二方面提供了一种控制器，该控制器具有实现上述第一方面中链路配置方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例第三方面提供了一种控制器，该控制器包括：处理器、存储器、该处理器通过运行存储在该存储器内的软件程序、调用存储在该存储器内的数据，执行前述本申请实施例第一方面提供的各实施方式的方法。
本申请实施例第四方面提供了一种计算机程序产品，该计算机程序产品包括计算机程序指令，该计算机程序指令可通过处理器进行加载来实现上述第一方面及其各实现方式中的方法。
本申请实施例第五方面提供了一种计算机储存介质，用于储存计算机程序指令，其包含用于执行前述本申请实施例第一方面提供的各实施方式的步骤的程序。
附图说明
图1为SD-WAN解决方案架构图；
图2为本申请实施例中链路配置方法一个实施例示意图；
图3为本申请实施例中链路配置方法另一个实施例示意图；
图4为本申请实施例中站点广域网侧拓扑图模板示意图；
图5为本申请实施例中企业总部与分支网络架构图；
图6为本申请实施例中控制器的一个实施例示意图；
图7为本申请实施例中控制器的另一个实施例示意图。
具体实施方式
请参阅图1，为当前SD-WAN解决方案架构图。
企业的分支站点(如Spoke1、Spoke2、Spoke3)与总部站点(如HUB)之间构建覆盖网络(overlay)。总部站点和分支站点之间，以及分支站点相互之间通过DSVPN隧道互联。每条DSVPN隧道对应一条逻辑链路，该逻辑链路用该DSVPN隧道的接口标识。每条DSVPN隧道对应的逻辑链路类型可以是Internet、多协议标签交换(Multiprotocol Label Switching，MPLS)、长期演进(Long-Term Evolution，LTE)等。
站点之间的互联由各站点的AR实现，总部站点和分支站点的AR分别向控制器注册， 控制器负责给不同站点上的AR下发链路配置参数。
下面以两分支站点间的通信为例说明本申请的技术方案。控制器向各分支站点的AR(以下称为spoke AR)发送链路配置参数，每个spoke AR收到对应的链路配置参数后，向总部站点的AR(以下称为HUB AR)发送下一跳解析协议(Next Hop Resolution Protocol)请求，将其出接口公网IP地址告知HUB AR，HUB AR收到该NHRP请求后，在本地创建或更新此spoke AR的NHRP对端(NHRP peer)表项。当分支站点间需要传输数据传输时，源spoke AR在路由表中查询目的spoke AR的下一跳；如果在源spoke AR的NHRP peer查询不到下一跳对应的公网IP地址，则源spoke AR向HUB AR发送NHRP地址解析请求，获取目的spoke AR的公网IP地址。随后两个spoke AR间通过多点通用路由封装协议(multipoint generic routing encapsulation，mGRE)接口以动态方式创建VPN隧道，这样两分支站点间即可以直接传输数据。
请参阅图2，为本申请实施例提供的一种链路配置方法的流程示意图。
201、控制器获取第一站点和第二站点的站点类型。
企业分支所在地的网络设备组成分支站点(site)，总部所在地的网络设备组成总部站点。分支站点与总部站点的AR分别注册到控制器上，控制器管理各站点的AR和VPN等。一个覆盖网络中通常包含一个总部站点和至少一个分支站点，站点类型可以是总部站点或分支站点，该第一站点和第二站点的站点类型可以是一个总部站点和一个分支站点，或者两个分支站点，其中第一站点和第二站点的站点类型具体此处不做限定。控制器根据租户的输入或选择，分别获取第一站点和第二站点的站点类型。
其中，201为本申请的可选步骤。
202、控制器获取租户从链路模板库为第一站点选择的第一链路模板和为第二站点选择的第二链路模板。
链路模板库预置于控制器中，其中包括多个链路模板，链路模板的具体数量此处不做限定。链路模板为控制器中预置的站点广域网侧的拓扑图模板，包含网关类型、链路类型、链路名称和网关的广域网侧物理端口号。其中，网关类型包括单网关或双网关，链路类型(link type)标识互联网服务提供商(Internet service provider，ISP)提供的链路类型，链路类型可以是Internet、MPLS、LTE等。链路名称可以自定义，例如用链路类型和ISP组成，ISP例如可以是中国移动通信集团(China Mobile Communications Corporation，CMCC)，则链路名称例如可以是Internet-CMCC或MPLS-CMCC，链路名称还可以是其他的形式。本申请中，一个站点包括至少一个AR。网关的广域网侧物理端口号是逻辑链路所绑定的物理端口信息。此外，链路模板中还可以包括上行带宽和/或下行带宽和公网IP地址，链路模板中可以包含具体的上行带宽和/或下行带宽，例如20M或100M也可以直接使用默认的上行带宽和/或下行带宽，上行带宽和/或下行带宽的具体形式此处不做限定。公网IP地址用于指示总部接入路由器的网关接口，本申请需要为总部站点配置公网IP地址，而不需要为分支站点配置公网IP地址。公网IP地址可以预置在链路模板中，也可以在控制器获取总部站点的链路模板后由租户管理员输入，获取总部站点公网IP地址的方式具体此处不做限定。
控制器分别获取租户为第一站点选择的第一链路模板和为第二站点选择的第二链路模板。通常，接入路由器作为站点的网关与其他站点的接入路由器通信。租户根据站 点的网关类型和链路类型选择对应的模板，例如单网关Internet链路模板或者双网关混合单链路模板。
203、控制器获取预置的全局配置信息。
预置的全局配置信息中包括逻辑链路的地址池，在配置链路配置参数时，控制器将根据地址池为第一站点的AR和第二站点的AR分别分配IP地址。
204、该控制器根据该地址池、该第一链路模板和该第二链路模板，按照预设的链路配置规则生成该第一站点的第一链路配置参数和该第二站点的第二链路配置参数。
控制器获取第一站点的第一链路模板和第二站点的第二链路模板，一个站点的链路模板中包含了至少一条链路的信息，控制器可以将不同站点间的链路按照预设的链路配置规则配置成逻辑链路。预设的链路配置规则可以包括链路名称匹配和/或链路类型匹配。其中，链路名称匹配是指将两个不同的链路模板中的链路名称相同的两条链路配置为一条逻辑链路；链路类型匹配是指将两个不同的链路模板中的链路类型相同的两条链路配置为一条逻辑链路。预设的链路配置规则中还可以包括其他规则。当该预设的链路配置规则包括多种规则时，在先的规则的优先级高于在后的规则的优先级。
以预设的规则包括链路名称匹配和链路类型匹配为例，控制器判断第一链路模板和第二链路模板中是否存在链路名称相同的两条链路。
若该第一链路模板中的第一链路和该第二链路模板中的第二链路的链路名称相同时，则该控制器将该第一链路和该第二链路配置为一条逻辑链路，并根据该地址池为该第一站点和该第二站点分别分配该逻辑链路的链路接口IP地址，得到该第一链路配置参数和该第二链路配置参数；
若该第一链路模板和第二链路模板中不存在链路名称相同的两条链路，则该控制器确定该第一链路模板和第二链路模板中是否存在链路类型相同的两条链路。
若该第一链路模板中的第三链路和该第二链路模板中的第四链路的链路类型相同时，该控制器将该第三链路和第四链路配置为一条逻辑链路，并根据该地址池为该第一站点和该第二站点分别分配该逻辑链路的链路接口IP地址，得到该第一链路配置参数和该第二链路配置参数。
可以理解的是，上述规则只是预置规则的一个例子，预置规则的具体内容此处不做限定。
205、向该第一站点发送该第一链路配置参数；以及向该第二站点发送该第二链路配置参数。
控制器向第一站点发送该第一链路配置参数，并向第二站点发送第二链路配置参数。在一个实施方式中，下发方式可以是，控制器根据链路配置参数分别为第一站点和第二站点生成NETCONF报文，然后再分别将对应的NETCONF报文发送给第一站点和第二站点。
根据本申请实施例提供的链路配置方法，控制器上预置了链路模板、全局配置信息以及预置的链路配置规则，在生成DSVPN隧道接口配置时，租户只需要根据当前需要选择站点类型和站点模板，控制器可以自动根据链路配置规则配置创建逻辑链路所需的tunnel配置参数，相较现有技术，本申请实施例提供的方法可提升链路配置的自动化程度，降低人工工作量，减轻租户的负担。
请参阅图3，本申请实施例中链路配置方法的另一个实施例示意图：
301、控制器获取第一站点和第二站点的站点类型；
一个覆盖网络中通常包含一个总部站点和至少一个分支站点，该第一站点和第二站点的站点类型的组合可以是一个总部站点和一个分支站点，或者两个分支站点，其中第一站点和第二站点的站点类型具体此处不做限定。控制器根据租户的输入或选择，分别获取第一站点和第二站点的站点类型。
进一步地，当需要构建的覆盖网络包含多个分支站点时，控制器可以获取多个站点的站点类型，例如：控制器获取租户选择的四个站点，并分别选择站点类型为总部、分支、分支和分支，即覆盖网络包含一个总部站点(HUB)和三个分支站点(Spoke1、Spoke2、Spoke3)。
其中，步骤301为本申请的可选步骤。
302、若第一站点或第二站点的站点类型为总部站点，则控制器获取总部站点的公网IP地址。
公网IP地址用于指示总部接入路由器的网关接口，本申请需要为总部站点配置公网IP地址，而不需要为分支站点配置公网IP地址。公网IP地址可以预置在链路模板中，也可以在控制器获取总部站点的链路模板后由租户管理员输入，获取总部站点公网IP地址的方式具体此处不做限定。
需要说明的是，步骤302可以在步骤303至步骤306中任一步骤之前执行，具体执行顺序此处不做限定。
303、控制器获取租户从链路模板库为第一站点选择的第一链路模板和为第二站点选择的第二链路模板。
链路模板库预置于控制器中，其中包括多个链路模板，链路模板的具体数量此处不做限定。链路模板为控制器中预置的站点广域网侧的拓扑图模板，包含网关类型、链路类型、链路名称和网关的广域网侧物理端口号。其中，网关类型包括单网关或双网关，链路类型(link type)标识互联网服务提供商(Internet service provider，ISP)提供的链路类型，链路类型可以是Internet、MPLS、LTE等。链路名称可以自定义，例如用链路类型和ISP组成，ISP例如可以是中国移动通信集团(China Mobile Communications Corporation，CMCC)，则链路名称例如可以是Internet-CMCC或MPLS-CMCC，链路名称还可以是其他的形式。本申请中，一个站点包括至少一个AR。网关的广域网侧物理端口号为创建逻辑链路所绑定的物理端口信息。此外，链路模板中还可以包括上行带宽和/或下行带宽，链路模板中可以包含具体的上行带宽和/或下行带宽，例如20M、100M等，也可以直接使用默认的上行带宽和/或下行带宽，上行带宽和/或下行带宽的具体数值此处不做限定。
此外，链路模板中还可以包含Internet协议安全性(IPsec)加密信息和其他描述性信息。链路模板中的附件信息，具体此处不做限定。
链路模板库的形式可以是列表，例如：
选项 链路名称 网关类型 物理端口号 链路类型
□ Internet-CMCC 单网关 GE0/0/1 INET
□ MPLS-CMCC 单网关 GE0/0/2 MPLS
□ LTE-CTCC 单网关 GE0/0/1 ESCAPE
链路模板还可以站点的广域网侧拓扑图的形式直观展示站点的网关类型和链路类型，请参阅图4，模板一：单网关混合双链路；模板二：单网关MPLS链路；模板三：单网关Internet链路；模板四：双网关混合单链路；模板五：单网关双Internet链路。
可以理解的是，链路模板可以有多种形式，具体此处不做限定。
通常，一个站点的接入路由器作为该站点的网关与其他站点的接入路由器通信。租户根据站点的网关类型和链路情况选择匹配的模版。
下面举例说明：请参阅图5，企业总部与分支的网络架构图，在构建图5所示的网络架构时，首先需要为各个站点选择对应的链路模板，图中的HUB站点、Spoke1站点、Spoke2站点和Spoke3站点的链路模板可以是：
HUB站点，链路模板为双网关混合双链路：
Figure PCTCN2019076607-appb-000001
网关类型为双网关的站点，一般会根据网关设备项对两个网关进行区分。
Spoke1站点，链路模板为单网关混合双链路：
Figure PCTCN2019076607-appb-000002
Spoke2站点，链路模板为单网关MPLS链路：
选项 链路名称 网关类型 物理端口 链路类型
√ MPLS-CMCC 单网关 GE0/0/1 MPLS
Spoke3站点，链路模板为单网关Internet链路：
Figure PCTCN2019076607-appb-000003
304、控制器获取预置的全局配置信息。
预置的全局配置信息中包括逻辑链路的地址池，控制器获取的地址池例如可以是172.16.1.0/16。地址池的具体IP信息此处不做限定。全局配置信息可以在控制器生成链路配置信息时，用于为第一站点和第二站点分别分配站点接入路由器的IP地址。
需要说明的是，步骤304可以在步骤301至步骤306中任一步骤之前执行，具体执行顺序此处不做限定。
305、控制器确定第一链路模板和第二链路模板中是否存在链路名称相同的两条链路。
一个链路模板中包含了至少一条链路的信息，控制器获取第一站点和第二站点的链路模板信息之后，可以对不同站点间的链路按照预设的链路配置规则进行编排。
以链路名称由链路类型和互联网服务提供商ISP信息组成为例，控制器可以判断是否存在链路名称相同的第一链路和第二链路，该第一链路为第一链路模板中的链路信息，该第二链路为第二链路模板中的链路信息。
请参考图5及步骤303提供的各站点链路模板示例，以图5中总部站点和3个分支站点的网关类型和链路类型为例进行说明：控制器判断租户为HUB站点、Spoke1站点、Spoke2站点和Spoke3站点分别确定的链路模板中是否存在链路名称相同的链路。由步骤303提供的站点链路模板可知，HUB站点的链路模板、Spoke1站点的链路模板和Spoke2站点的链路模板中均存在链路名称为“MPLS-CMCC”的链路，因此，将执行步骤306。
306、当第一链路模板中的第一链路和第二链路模板中的第二链路的链路名称相同时，控制器将第一链路和第二链路配置为一条逻辑链路，并根据地址池为第一站点和第二站点分别分配逻辑链路的链路接口IP地址，得到第一链路配置参数和第二链路配置参数。
若存在链路名称相同的第一链路和第二链路，则该控制器将该第一链路和该第二链路两条链路配置为一条逻辑链路。并根据步骤302中获取的地址池，为链路两端的网关接口分别分配IP地址，最后得到第一链路配置参数和第二链路配置参数。
下面举例说明，请参考图5和步骤303提供的各站点链路模板示例，控制器获取HUB站点和Spoke1站点的链路模板，控制器可以发现HUB站点和Spoke1站点的链路模板中均存在链路名称为“MPLS-CMCC”的链路，将HUB站点的链路模板中的“MPLS-CMCC”链路与Spoke1站点的链路模板中的“MPLS-CMCC”链路配置为一条链路类型为“MPLS”的逻辑链路，并根据地址池为“MPLS”逻辑链路的端点，即HUB站点的AR设备2和Spoke1站点的AR设备2分别配置链路接口IP地址，得到为HUB站点生成的第一链路配置参数(包括物理端口号以及HUB AR的链路接口IP地址)和Spoke1站点的第二链路配置参数(包括物理端口号、Spoke1AR的链路接口IP地址以及指向HUB站点的AR设备1的IP地址和HUB站点的公网IP地址)，并根据第一链路配置参数生成第一NETCONF报文发送给HUB AR，根据第二链路配置参数生成第二NETCONF报文发送给Spoke1AR。
控制器发现HUB站点和Spoke1站点的链路模板中均存在链路名称为“Internet-CMCC”的链路，将HUB站点的链路模板中的“Internet-CMCC”链路与Spoke1站点的链路模板中的“Internet-CMCC”链路配置为一条链路类型为“Internet”的逻辑链路，并根据地址池为“Internet”逻辑链路的端点，即HUB站点的AR设备1和Spoke1站点的AR设备1分别配置链路接口IP地址，得到为HUB站点生成的第一链路配置参数(包括物理端口号以及HUB AR的链路接口IP地址)和Spoke1站点的第二链路配置参数(包括物理端口号、Spoke1AR的链路接口IP地址以及指向HUB站点的AR设备1的IP地址和HUB站点的公网IP地址)，并根据第一链路配置参数生成第一NETCONF报文发送给HUB AR，根据第二链路配置参数生成第二NETCONF报文发送给Spoke1AR。
类似地，控制器发现HUB站点和Spoke2站点的链路模板中均存在链路名称为 “MPLS-CMCC”的链路，控制器将HUB站点的链路模板中的“MPLS-CMCC”链路与Spoke2站点的链路模板中的“MPLS-CMCC”链路配置为一条链路类型为“MPLS”逻辑链路，由于此前HUB站点已经与Spoke1站点间已经配置了一条“MPLS”逻辑链路，并为HUB站点配置了链路参数，因此，控制器可以只为该“MPLS”逻辑链路的另一端端点Spoke2站点的AR根据地址池配置链路接口IP地址，得到Spoke2站点的第二链路配置参数(包括物理端口号、Spoke2AR的链路接口IP地址以及指向HUB站点的AR设备2的IP地址和HUB站点的公网IP地址)，并根据第二链路配置参数生成第二NETCONF报文发送给Spoke2AR。
307、若第一链路模板和第二链路模板中不存在链路名称相同的两条链路，则控制器确定第一链路模板和第二链路模板中是否存在链路类型相同的两条链路。
若第一链路模板和第二链路模板中不存在链路名称相同的两条链路，则该控制器确定第一链路模板和第二链路模板中是否存在链路类型相同的两条链路，即第三链路和第四链路，该第三链路为第一链路模板中的链路，该第四链路为第二链路模板中的链路。
下面举例说明，请参考图5和步骤303提供的各站点链路模板示例，由于HUB站点和Spoke3站点的链路模板中不存在链路名称相同的链路，因此，控制器确定HUB站点的链路模板和Spoke3站点的链路模板中是否存在链路类型相同的链路。
308、当第一链路模板中的第三链路和第二链路模板中的第四链路的链路类型相同时，控制器将该第三链路和第四链路配置为一条逻辑链路，并根据地址池为第一站点和第二站点分别分配逻辑链路的链路接口IP地址，得到第一链路配置参数和第二链路配置参数。
当第一链路模板中的第三链路和第二链路模板中的第四链路的链路类型相同时，控制器将该第三链路和第四链路配置为一条逻辑链路，并根据步骤302中获取的地址池分配链路接口IP地址，得到该第一链路配置参数和该第二链路配置参数，并根据链路配置参数生成NETCONF报文。
下面举例说明，请参阅图5和步骤303提供的各站点链路模板示例，HUB站点和Spoke3站点链路模板存在链路类型同为“Internet”的链路，控制器获取HUB站点和Spoke3站点的链路模板，控制器发现HUB站点和Spoke3站点的链路模板中均存在链路类型为“Internet”的链路，将HUB站点的链路模板中的“Internet”链路与Spoke3站点的链路模板中的“Internet”链路配置为一条“Internet”逻辑链路，并根据地址池为逻辑链路“Internet”的端点，即HUB站点的AR设备1和Spoke3站点的AR分别配置链路接口IP地址，得到第一链路配置参数(包括HUB AR设备1的链路接口IP地址)和该第二链路配置参数(包括以及Spoke3AR的链路接口IP地址)，并根据第一链路配置参数生成第一NETCONF报文发送给HUB AR设备1，根据第二链路配置参数生成第二NETCONF报文发送给Spoke3AR。需要说明的是，若此前，HUB站点AR设备1已经与Spoke1站点AR间配置了链路类型为“Internet”的逻辑链路，则本步骤中，控制器可以不再为HUB站点配置链路接口IP地址，以及第一链路配置参数。
需要说明的是，当两个站点间存在多条链路类型相同的链路时，例如，Spoke 3的链路模板为双Internet链路时，控制器可以从链路模板中获取链路的上行带宽和/或下行带宽信息，选取与HUB站点的Internet链路的上行带宽和/或下行带宽值最接近的一 条，与HUB站点的Internet链路配置成一条逻辑Internet链路。
309、向该第一站点发送该第一链路配置参数；以及向该第二站点发送该第二链路配置参数。
控制器向第一站点发送该第一链路配置参数，并向第二站点发送第二链路配置参数。在一个实施方式中，下发方式可以是，控制器根据第一链路配置参数生成第一NETCONF报文，根据第二链路配置参数生成第二NETCONF报文，然后再分别将该第一NETCONF报文和该第二NETCONF报文下发给第一站点和第二站点。
下面举例说明，请参阅图5和步骤303提供的各站点链路模板示例，HUB站点与Spoke1站点间创建的“MPLS”链路，为各站点生成的配置如下：
HUB站点侧：
interface Tunnel0/0/0
ip address 172.16.1.1 255.255.255.0
tunnel-protocol gre p2mp
source GigabitEthernet0/0/2
nhrp redirect
nhrp entry multicast dynamic
其中，“interface Tunnel0/0/0”代表链路一端(即HUB站点AR设备2)的接口，“ip address 172.16.1.1 255.255.255.0”为控制器从地址池中分配的IP地址，用于指示该条链路在HUB站点侧的接口；“tunnel-protocol gre p2mp”代表采用P2MP(点到多点)的GRE隧道模式；“source GigabitEthernet0/0/2”代表千兆以太网接口号；“nhrp redirect”代表NHRP重定向，用于总部站点；“nhrp entry multicast dynamic”代表配置动态注册的分支加入NHRP组播成员表。
Spoke1站点侧：
interface Tunnel0/0/0
ip address 172.16.1.2 255.255.255.0
tunnel-protocol gre p2mp
source GigabitEthernet0/0/2
nhrp shortcut
nhrp entry 172.16.1.1 202.1.1.10 register
其中，“nhrp entry 172.16.1.1 202.1.1.10 register”为指向总部的Tunnel IP和公网IP地址(public IP)，当支接入公网时，可向总部的公网IP发送NHRP注册请求；“nhrp shortcut”代表部署分支只保存到总部的汇聚路由方案，使源分支到目的分支子网的路由下一跳为总部的Tunnel地址，即shortcut场景。其他项与总部配置参数含义类似，此处不再赘述。
HUB站点与Spoke1站点间还创建了“Internet”链路,链路两端站点生成的配置如下。
HUB站点侧：
interface Tunnel0/0/0
ip address 172.16.1.3 255.255.255.0
tunnel-protocol gre p2mp
source GigabitEthernet0/0/1
nhrp redirect
nhrp entry multicast dynamic
Spoke1站点侧：
interface Tunnel0/0/1
ip address 172.16.1.4 255.255.255.0
tunnel-protocol gre p2mp
source GigabitEthernet0/0/1
nhrp shortcut
nhrp entry 172.16.1.3 202.1.1.11 register
由于单网关的Spoke1站点侧配置了两条链路类型不同的逻辑链路参数，通过物理接口号可以进行区分，其他参数的具体含义此处不再赘述。
HUB站点与Spoke2站点间也创建了“MPLS”链路，由于HUB站点与Spoke1站点间建立“MPLS”链路时已经生成了链路配置，因此，控制器只为Spoke2站点生成该条链路的链路配置：
Spoke2站点侧：
interface Tunnel0/0/0
ip address 172.16.1.5 255.255.255.0
tunnel-protocol gre p2mp
source GigabitEthernet0/0/1
nhrp shortcut
nhrp entry 172.16.1.1 202.1.1.10 register
参数的具体含义此处不再赘述。
HUB站点与Spoke3站点间创建“Internet”链路，由于HUB站点与Spoke1站点间建立“Internet”链路时已经生成了链路配置，因此，在Spoke3侧将生成该条链路的链路配置：
interface Tunnel0/0/0
ip address 172.16.1.6 255.255.255.0
tunnel-protocol gre p2mp
source GigabitEthernet0/0/1
nhrp shortcut
nhrp entry 172.16.1.3 202.1.1.11 register
链路配置参数的含义此处不再赘述。
各站点根据控制器下发的报文获取配置参数，将以动态方式创建VPN隧道，即可进行站点间的数据传输。
根据本申请实施例提供的链路配置方法，控制器上预置了链路模板、全局配置信息和预设的链路配置规则。在生成DSVPN隧道接口配置时，租户只需要根据当前需要选择 站点类型和站点模板，控制器可以自动根据模板匹配规则创建逻辑链路所需的tunnel配置参数，还可以根据实际情况预置不同的链路编排策略，编排链路类型相同且ISP相同的链路，或者编排链路类型相同且带宽接近的链路。本申请实施例提供的方法可提升链路配置的自动化程度，降低人工工作量，减轻租户的负担。
上述实施例介绍了本申请链路配置方法，下面将对实现该链路配置方法的控制器进行介绍，请参阅图6，本申请控制器的一个实施例示意图。
该控制器包括：
第一获取单元601，用于获取租户从链路模板库为第一站点选择的第一链路模板和为第二站点选择的第二链路模板，该链路模板库包括多个链路模板，该多个链路模板中的每个链路模板包含网关类型、链路类型、链路名称和网关的广域网侧物理端口号；
第二获取单元602，用于获取预置的全局配置信息，该全局配置信息中包含链路的地址池；
生成单元603，用于根据该地址池、该第一链路模板和该第二链路模板，按照预设的链路配置规则生成该第一站点的第一链路配置参数和该第二站点的第二链路配置参数；
在一个实施方式中，该生成单元603具体用于：
确定该第一链路模板和第二链路模板中是否存在链路名称相同的两条链路；
当该第一链路模板中的第一链路和该第二链路模板中的第二链路的链路名称相同时，将该第一链路和该第二链路配置为一条逻辑链路，并根据该地址池为该第一站点和该第二站点分别分配该逻辑链路的链路接口IP地址，得到该第一链路配置参数和该第二链路配置参数；
若该第一链路模板和第二链路模板中不存在链路名称相同的两条链路，则确定该第一链路模板和第二链路模板中是否存在链路类型相同的两条链路；
当该第一链路模板中的第三链路和该第二链路模板中的第四链路的链路类型相同时，将该第三链路和第四链路配置为一条逻辑链路，并根据该地址池为该第一站点和该第二站点分别分配该逻辑链路的链路接口IP地址，得到该第一链路配置参数和该第二链路配置参数。
发送单元604，用于向该第一站点发送该第一链路配置参数；以及，向该第二站点发送该第二链路配置参数。
该第一获取单元601还用于：
分别获取该第一站点和该第二站点的站点类型；
若该第一站点或第二站点的站点类型为总部站点，则获取该总部站点的公网IP地址。
该生成单元603还用于：
若存在多个第三链路和/或多个第四链路，则获取带宽最接近的目标第三链路和目标第四链路，并将该目标第三链路和目标第四链路配置为一条逻辑链路。
本申请实施例提供的控制器在实现链路配置方法的过程与前述图2或图3所示的实施例中描述的方法流程类似，此处不再赘述。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是 各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
该集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例该方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
基于以上介绍，下面为介绍本申请实施例控制器的另一个实施例，请参阅图7，为本申请实施例中控制器的另一个实施例示意图，该设备700可以是控制器或其中一部分。
该控制器700可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器(central processing units，CPU)701(例如，一个或一个以上其他类型处理器)和存储器705，该存储器705中存储有一个或一个以上的应用程序或数据。其中，存储器705可以是易失性存储或持久存储。存储在存储器705的程序可以包括一个或一个以上模块，每个模块可以包括对控制器中的一系列指令操作。更进一步地，中央处理器701可以设置为与存储器705通信，在控制器700上执行存储器705中的一系列指令操作。
控制器700还可以包括一个或一个以上电源702，一个或一个以上有线或无线网络接口703，一个或一个以上输入输出接口704，和/或，一个或一个以上操作系统。控制器700中的各个部分可以形成一整个芯片或多个独立芯片。
本实施例中控制器700中的中央处理器701所执行的流程与前述图2或图3所示的实施例中描述的方法流程类似，此处不再赘述。本申请实施例还提供一种计算机存储介质，该计算机存储介质用于储存为前述控制器所用的计算机程序指令，其包括用于执行为控制器所设计的程序。
本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机程序指令，该计算机程序指令可通过处理器进行加载来实现前述图2或图3所示的实施例中的方法流程。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (13)

  1. 一种链路配置方法，其特征在于，包括：
    控制器获取租户从链路模板库为第一站点选择的第一链路模板和为第二站点选择的第二链路模板，所述链路模板库包括多个链路模板，所述多个链路模板中的每个链路模板包含网关类型、链路类型、链路名称和网关的广域网侧物理端口号；
    所述控制器获取预置的全局配置信息，所述全局配置信息中包含链路的地址池；
    所述控制器根据所述地址池、所述第一链路模板和所述第二链路模板，按照预设的链路配置规则生成所述第一站点的第一链路配置参数和所述第二站点的第二链路配置参数；
    所述控制器向所述第一站点发送所述第一链路配置参数；以及，
    所述控制器向所述第二站点发送所述第二链路配置参数。
  2. 根据权利要求1所述的链路配置方法，其特征在于，所述方法还包括：
    所述控制器分别获取所述第一站点和所述第二站点的站点类型；
    若所述第一站点或第二站点的站点类型为总部站点，则所述控制器获取所述总部站点的公网IP地址。
  3. 根据权利要求1或2所述的链路配置方法，其特征在于，所述链路模板还包括：上行带宽和/或下行带宽。
  4. 根据权利要求1或2所述的链路配置方法，其特征在于，所述预设的链路配置规则包括：链路名称匹配和/或链路类型匹配；
    其中，当所述预设的链路配置规则包括多种规则时，在先的规则的优先级高于在后的规则的优先级。
  5. 根据权利要求4所述的链路配置方法，当所述预设的链路配置规则包括链路名称匹配和链路类型匹配时，所述按照预设的链路配置规则生成所述第一站点的第一链路配置参数和所述第二站点的第二链路配置参数包括：
    所述控制器确定所述第一链路模板和第二链路模板中是否存在链路名称相同的两条链路；
    当所述第一链路模板中的第一链路和所述第二链路模板中的第二链路的链路名称相同时，所述控制器将所述第一链路和所述第二链路配置为一条逻辑链路，并根据所述地址池为所述第一站点和所述第二站点分别分配所述逻辑链路的链路接口IP地址，得到所述第一链路配置参数和所述第二链路配置参数；
    若所述第一链路模板和第二链路模板中不存在链路名称相同的两条链路，则所述控制器确定所述第一链路模板和第二链路模板中是否存在链路类型相同的两条链路；
    当所述第一链路模板中的第三链路和所述第二链路模板中的第四链路的链路类型相同时，所述控制器将所述第三链路和第四链路配置为一条逻辑链路，并根据所述地址 池为所述第一站点和所述第二站点分别分配所述逻辑链路的链路接口IP地址，得到所述第一链路配置参数和所述第二链路配置参数。
  6. 根据权利要求5所述的链路配置方法，其特征在于，所述控制器将所述第三链路和第四链路配置为一条逻辑链路包括：
    若存在多个第三链路和/或多个第四链路，则所述控制器获取带宽最接近的目标第三链路和目标第四链路，并将所述目标第三链路和目标第四链路配置为一条逻辑链路。
  7. 一种控制器，其特征在于，包括：
    第一获取单元，用于取租户从链路模板库为所述第一站点选择的第一链路模板和为所述第二站点选择的第二链路模板，所述链路模板库包括多个链路模板，所述多个链路模板中的每个链路模板包含网关类型、链路类型、链路名称和网关的广域网侧物理端口号；
    第二获取单元，用于获取预置的全局配置信息，所述全局配置信息中包含链路的地址池；
    生成单元，用于根据所述地址池、所述第一链路模板和所述第二链路模板，按照预设的链路配置规则生成所述第一站点的第一链路配置参数和所述第二站点的第二链路配置参数；
    发送单元，用于向所述第一站点发送所述第一链路配置参数；以及，向所述第二站点发送所述第二链路配置参数。
  8. 根据权利要求7所述的控制器，其特征在于，所述第一获取单元还用于：
    分别获取所述第一站点和所述第二站点的站点类型；
    若所述第一站点或第二站点的站点类型为总部站点，则获取所述总部站点的公网IP地址。
  9. 根据权利要求7或8所述的控制器，其特征在于，当所述预设的链路配置规则包括链路名称匹配和链路类型匹配时，所述生成单元具体用于：
    确定所述第一链路模板和第二链路模板中是否存在链路名称相同的两条链路；
    当所述第一链路模板中的第一链路和所述第二链路模板中的第二链路的链路名称相同时，将所述第一链路和所述第二链路配置为一条逻辑链路，并根据所述地址池为所述第一站点和所述第二站点分别分配所述逻辑链路的链路接口IP地址，得到所述第一链路配置参数和所述第二链路配置参数；
    若所述第一链路模板和第二链路模板中不存在链路名称相同的两条链路，则确定所述第一链路模板和第二链路模板中是否存在链路类型相同的两条链路；
    当所述第一链路模板中的第三链路和所述第二链路模板中的第四链路的链路类型相同时，将所述第三链路和第四链路配置为一条逻辑链路，并根据所述地址池为所述第一站点和所述第二站点分别分配所述逻辑链路的链路接口IP地址，得到所述第一链路配置参数和所述第二链路配置参数。
  10. 根据权利要求9所述的控制器，其特征在于，所述生成单元还用于：
    若存在多个第三链路和/或多个第四链路，则获取带宽最接近的目标第三链路和目标第四链路，并将所述目标第三链路和目标第四链路配置为一条逻辑链路。
  11. 一种控制器，其特征在于，包括：
    所述存储器用于存储程序指令；
    所述处理器用于执行所述程序指令以实现权利要求1-6中任意一项所述的方法。
  12. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1至6中任一项所述的方法。
  13. 一种计算机可读存储介质，所述计算机可读存储介质用于存储程序指令，其特征在于，当所述程序指令在计算机上运行时，使得所述计算机执行如权利要求1至6中任一项所述的方法。
PCT/CN2019/076607 2018-03-28 2019-03-01 链路配置方法和控制器 Ceased WO2019184653A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP23165836.0A EP4266641A1 (en) 2018-03-28 2019-03-01 Link configuration method and controller
EP19774700.9A EP3758294B1 (en) 2018-03-28 2019-03-01 Link configuration method and controller
US17/030,839 US11924004B2 (en) 2018-03-28 2020-09-24 Link configuration method and controller
US18/431,000 US20240179027A1 (en) 2018-03-28 2024-02-02 Link configuration method and controller

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810265042.6A CN110324159B (zh) 2018-03-28 2018-03-28 链路配置方法、控制器和存储介质
CN201810265042.6 2018-03-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/030,839 Continuation US11924004B2 (en) 2018-03-28 2020-09-24 Link configuration method and controller

Publications (1)

Publication Number Publication Date
WO2019184653A1 true WO2019184653A1 (zh) 2019-10-03

Family

ID=68058566

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/076607 Ceased WO2019184653A1 (zh) 2018-03-28 2019-03-01 链路配置方法和控制器

Country Status (4)

Country Link
US (2) US11924004B2 (zh)
EP (2) EP3758294B1 (zh)
CN (1) CN110324159B (zh)
WO (1) WO2019184653A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111988323B (zh) * 2020-08-24 2022-09-23 北京天融信网络安全技术有限公司 IPSec隧道建立方法、装置、网络系统及电子设备
US11936522B2 (en) * 2020-10-14 2024-03-19 Connectify, Inc. Selecting and operating an optimal virtual private network among multiple virtual private networks
CN115396369A (zh) * 2021-05-21 2022-11-25 华为技术有限公司 一种报文处理的方法、系统和网络设备
CN113365166B (zh) * 2021-06-25 2022-04-22 北京轻网科技有限公司 网络配置方法及装置
CN113360300B (zh) * 2021-06-29 2023-10-24 北京思普艾斯科技有限公司 接口调用链路生成方法、装置、设备及可读存储介质
CN115514649B (zh) * 2022-08-24 2024-11-29 中国电信股份有限公司 一种企业SDWAN hub-spoke组网中智能隧道调度的方法与系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7609647B2 (en) * 2004-05-12 2009-10-27 Bce Inc. Method and apparatus for network configuration validation
CN102724117A (zh) * 2012-06-06 2012-10-10 华为技术有限公司 多协议标签交换流量工程隧道建立方法及设备
CN102946610A (zh) * 2012-10-25 2013-02-27 中兴通讯股份有限公司 一种微波网络规划的方法及系统
CN103023707A (zh) * 2012-12-28 2013-04-03 华为技术有限公司 一种策略配置的方法、管理服务器以及网络系统

Family Cites Families (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6463475B1 (en) * 1997-09-26 2002-10-08 3Com Corporation Method and device for tunnel switching
US6614809B1 (en) * 2000-02-29 2003-09-02 3Com Corporation Method and apparatus for tunneling across multiple network of different types
US7117267B2 (en) * 2001-06-28 2006-10-03 Sun Microsystems, Inc. System and method for providing tunnel connections between entities in a messaging system
US7779152B2 (en) 2003-01-24 2010-08-17 Nokia Corporation Establishing communication tunnels
US7673048B1 (en) * 2003-02-24 2010-03-02 Cisco Technology, Inc. Methods and apparatus for establishing a computerized device tunnel connection
US7421483B1 (en) * 2004-02-02 2008-09-02 Juniper Networks, Inc. Autodiscovery and self configuration of customer premise equipment
JP5038887B2 (ja) * 2004-04-15 2012-10-03 クリアパス・ネットワークス・インコーポレーテッド ネットワークを管理するシステムおよび方法
US7463584B2 (en) * 2004-08-03 2008-12-09 Nortel Networks Limited System and method for hub and spoke virtual private network
US7748035B2 (en) * 2005-04-22 2010-06-29 Cisco Technology, Inc. Approach for securely deploying network devices
CN101013995A (zh) * 2007-02-12 2007-08-08 华为技术有限公司 网络节点设备、网络系统及隧道建立方法
US8418244B2 (en) * 2007-04-27 2013-04-09 Yahoo! Inc. Instant communication with TLS VPN tunnel management
US7751405B1 (en) * 2007-09-26 2010-07-06 Juniper Networks, Inc. Automatic configuration of label switched path tunnels using BGP attributes
CN101471879A (zh) * 2007-12-27 2009-07-01 华为技术有限公司 一种层次化有序地址分组网络的路径控制系统和方法
WO2010068698A2 (en) * 2008-12-09 2010-06-17 Glue Networks, Inc. System and method for providing virtual private networks
WO2010127610A1 (zh) * 2009-05-04 2010-11-11 成都市华为赛门铁克科技有限公司 一种虚拟专用网节点信息的处理方法、设备及系统
JP5357707B2 (ja) * 2009-11-11 2013-12-04 株式会社日立製作所 ゲートウェイ装置およびポート番号割当て方法
US9256716B2 (en) * 2010-09-22 2016-02-09 Nec Corporation Access authority generation device
US20120087356A1 (en) * 2010-10-07 2012-04-12 Qualcomm, Incorporated Tunneled direct link setup through a tunnel
JP5915454B2 (ja) * 2011-09-01 2016-05-11 富士通株式会社 ネットワークシステム
KR20130101618A (ko) * 2012-02-10 2013-09-16 한국전자통신연구원 네트워크 가상화에 기반한 네트워크 운용 시스템 및 방법
CN103905284B (zh) * 2012-12-27 2018-04-06 新华三技术有限公司 一种基于evi网络的流量负载分担方法和设备
US9420003B2 (en) * 2013-06-24 2016-08-16 Cisco Technology, Inc. Dynamic communication between secure endpoints
CN104301192B (zh) * 2013-07-18 2019-06-11 新华三技术有限公司 一种vpn组网的网络设备发现方法及装置
EP3075128B1 (en) * 2013-11-26 2022-04-27 HMS Industrial Networks AB Communication system
US9391800B2 (en) * 2014-03-12 2016-07-12 Microsoft Technology Licensing, Llc Dynamic and interoperable generation of stateful VPN connection profiles for computing devices
KR20160122992A (ko) * 2015-04-15 2016-10-25 한국전자통신연구원 정책 기반으로 네트워크 간에 연결성을 제공하기 위한 네트워크 통합 관리 방법 및 장치
CN106301829B (zh) * 2015-05-21 2019-08-09 华为技术有限公司 一种网络业务扩容的方法和装置
US9825777B2 (en) * 2015-06-23 2017-11-21 Cisco Technology, Inc. Virtual private network forwarding and nexthop to transport mapping scheme
US10057084B2 (en) * 2015-10-06 2018-08-21 Citrix Systems, Inc. Systems and methods of extending on premise network into the cloud
US9980303B2 (en) * 2015-12-18 2018-05-22 Cisco Technology, Inc. Establishing a private network using multi-uplink capable network devices
EP3414932B1 (en) * 2016-02-10 2020-09-02 Hughes Network Systems, LLC System and method for policy-based multipath wan transports for improved quality of service over broadband networks
CN107147509B (zh) * 2016-03-01 2022-03-11 中兴通讯股份有限公司 虚拟专用网业务实现方法、装置及通信系统
EP3240234A1 (de) * 2016-04-25 2017-11-01 Siemens Aktiengesellschaft Verfahren zur konfiguration einer tunnel-verbindung für ein automatisierungs-netzwerk
US20180013798A1 (en) * 2016-07-07 2018-01-11 Cisco Technology, Inc. Automatic link security
CN107786353B (zh) * 2016-08-24 2020-06-26 华为技术有限公司 业务编排方法及装置、业务发放方法及装置
JP6987869B2 (ja) * 2017-01-13 2022-01-05 エルジー エレクトロニクス インコーポレイティドLg Electronics Inc. 無線通信システムにおいてサービス品質（ＱｏＳ）フロー基盤のＵＬパケットを送信する方法及びそのための装置
US10856203B2 (en) * 2017-01-19 2020-12-01 Qualcomm Incorporated Signaling for link aggregation setup and reconfiguration
US11095617B2 (en) * 2017-12-04 2021-08-17 Nicira, Inc. Scaling gateway to gateway traffic using flow hash
US10826722B2 (en) * 2017-12-18 2020-11-03 Futurewei Technologies, Inc. Controller based service policy mapping to establish different tunnels for different applications
US10797910B2 (en) * 2018-01-26 2020-10-06 Nicira, Inc. Specifying and utilizing paths through a network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7609647B2 (en) * 2004-05-12 2009-10-27 Bce Inc. Method and apparatus for network configuration validation
CN102724117A (zh) * 2012-06-06 2012-10-10 华为技术有限公司 多协议标签交换流量工程隧道建立方法及设备
CN102946610A (zh) * 2012-10-25 2013-02-27 中兴通讯股份有限公司 一种微波网络规划的方法及系统
CN103023707A (zh) * 2012-12-28 2013-04-03 华为技术有限公司 一种策略配置的方法、管理服务器以及网络系统

Also Published As

Publication number Publication date
EP3758294B1 (en) 2023-05-03
CN110324159B (zh) 2020-11-03
US11924004B2 (en) 2024-03-05
EP3758294A1 (en) 2020-12-30
EP4266641A1 (en) 2023-10-25
CN110324159A (zh) 2019-10-11
US20210021445A1 (en) 2021-01-21
EP3758294A4 (en) 2021-04-21
US20240179027A1 (en) 2024-05-30

Similar Documents

Publication Publication Date Title
US11736394B2 (en) Address resolution using multiple designated instances of a logical router
EP3824602B1 (en) Multi-cloud connectivity using srv6 and bgp
EP3815311B1 (en) Intelligent use of peering in public cloud
CN106487695B (zh) 一种数据传输方法、虚拟网络管理装置及数据传输系统
CN107071087B (zh) 逻辑l3路由
US10009267B2 (en) Method and system for controlling an underlying physical network by a software defined network
WO2019184653A1 (zh) 链路配置方法和控制器
EP3629529B1 (en) Ingress ecmp in virtual distributed routing environment
US20150043348A1 (en) Traffic Flow Redirection between Border Routers using Routing Encapsulation
US10742697B2 (en) Packet forwarding apparatus for handling multicast packet
WO2020108587A1 (zh) 数据处理方法、控制器和转发设备
US11290394B2 (en) Traffic control in hybrid networks containing both software defined networking domains and non-SDN IP domains
CN115499434B (zh) 跨vpc的流量转发方法
WO2022062506A1 (zh) 一种数据处理方法、装置、存储介质及电子装置
EP3588875B1 (en) Web services across virtual routing and forwarding
TWI759571B (zh) 基於流表的資料傳送方法
WO2015090087A1 (zh) 路由扩散的方法及装置
US20080298366A1 (en) Agnostic Network Architecture
WO2024113867A1 (zh) 一种通信方法及装置
AU2017304281A1 (en) Extending an MPLS network using commodity network devices
CN109714259B (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: 19774700

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: 2019774700

Country of ref document: EP

Effective date: 20200922