CN110572273B - Method for automatically deploying physical network - Google Patents
Method for automatically deploying physical network Download PDFInfo
- Publication number
- CN110572273B CN110572273B CN201910674758.6A CN201910674758A CN110572273B CN 110572273 B CN110572273 B CN 110572273B CN 201910674758 A CN201910674758 A CN 201910674758A CN 110572273 B CN110572273 B CN 110572273B
- Authority
- CN
- China
- Prior art keywords
- spine
- node
- leaf
- equipment
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000008569 process Effects 0.000 claims description 6
- 230000008859 change Effects 0.000 abstract description 5
- 101100513046 Neurospora crassa (strain ATCC 24698 / 74-OR23-1A / CBS 708.71 / DSM 1257 / FGSC 987) eth-1 gene Proteins 0.000 description 18
- 230000006855 networking Effects 0.000 description 6
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 235000017166 Bambusa arundinacea Nutrition 0.000 description 1
- 235000017491 Bambusa tulda Nutrition 0.000 description 1
- 241001330002 Bambuseae Species 0.000 description 1
- 235000015334 Phyllostachys viridis Nutrition 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 239000011425 bamboo Substances 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000012466 permeate Substances 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- 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
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for automatically deploying a physical network, which comprises the following steps: step 1: automatically deploying a physical network according to a network topology structure, and opening a bottom layer network through a BGP protocol or an OSP protocol; step 2: detecting that newly added equipment is required to be added into the existing network topology, issuing corresponding configuration to the newly added equipment, and issuing intercommunicated configuration data to associated equipment; and step 3: and when detecting that the equipment needs to be deleted, deleting the corresponding configuration of the equipment and deleting the corresponding configuration data on the equipment associated with the equipment. The method and the system automatically deploy the physical network based on the topological structure, and solve the problem of complicated configuration of the underlying network when the SDN controller is deployed; and the equipment configuration is automatically adjusted according to the change of the topological structure, so that the intercommunication of the physical network is ensured.
Description
Technical Field
The invention relates to a method for automatically deploying a physical network, belonging to the technical field of communication.
Background
With the rapid development of the internet, applications such as shopping platforms, social software, live broadcast platforms and the like, such as bamboo shoots in spring after raining, permeate into the aspects of life of people, and clothes and eating houses are closely connected with the internet. Therefore, new requirements are provided for the bandwidth, the time delay and the like of the network, and the network needs to be continuously upgraded to meet the requirements of people. However, the traditional network relies on network devices excessively, network innovation and upgrading are extremely difficult, and a Software Defined Network (SDN) is produced in order to get rid of the network dilemma.
The core design philosophy of software defined networking is control and forwarding separation, centralized control, and development of APIs. After the idea is proposed, various solutions are developed, wherein an Overlay Network proposed by a vendor represented by VMware is most widely applied, and Host Overlay, Network Overlay and Hybrid Overlay are the most mainstream, wherein Network Overlay is favored by many hardware equipment vendors. Network Overlay needs the support of hardware equipment, but the intercommunication configuration between physical equipment is very tedious, and also is very easy to make mistakes, especially when the Network scale is large. The automatic deployment of the physical network provides great convenience for deployment personnel.
The patent of 'equipment configuration method and device' with application number 201610191783, the equipment configuration method comprises: according to the stored configuration information of the equipment, establishing a first connection and a second connection with the equipment, wherein the equipment comprises bottom layer underlay equipment, gateway VTEP equipment and access VTEP equipment; transmitting an LLDP message to the equipment based on the first connection, and collecting a network topology; stacking and configuring the equipment based on the first connection and the second connection to obtain a simplified network topology; the device in the simplified network topology is route configured based on the second connection. However, the Underlay configuration only supports OSPF protocol, cannot be selected as required, and cannot dynamically support the addition and deletion of devices.
Disclosure of Invention
Aiming at the defects of the method, the invention provides a method for automatically deploying a physical network, which can solve the problem that the configuration of an underlying network is complicated when an SDN controller is deployed.
The technical scheme adopted for solving the technical problems is as follows:
the method for automatically deploying the physical network provided by the embodiment of the invention comprises the following steps:
step 1: automatically deploying a physical network according to a network topology structure, and opening a bottom layer network through a BGP protocol or an OSP protocol;
step 2: detecting that newly added equipment is required to be added into the existing network topology, issuing corresponding configuration to the newly added equipment, and issuing intercommunicated configuration data to associated equipment;
and step 3: and when detecting that the equipment needs to be deleted, deleting the corresponding configuration of the equipment and deleting the corresponding configuration data on the equipment associated with the equipment.
With reference to a possible implementation manner of this embodiment, in step 1, according to a topology structure of a Leaf-Leaf architecture network, a connection relationship between Leaf and Leaf is found, a resource pool is used to apply for a corresponding resource, and corresponding BGP configuration information or OSPF configuration information is generated and sent to a device through a southward interface of an SDN controller.
In combination with a possible implementation manner as this embodiment, when the underlying network is opened by using the BGP protocol, step 1 specifically includes the following steps:
collecting topology information of a Leaf-spine architecture network;
pre-configuring a resource pool: modifying AS numbers, loopback interface address fields and loopback interface numbers of the Spine node and the Leaf node AS required, and address fields of interconnection interfaces of the Spine node and the Leaf node;
pre-configuring a BGP public configuration template of the equipment;
and carrying out automatic deployment of the physical network.
In combination with a possible implementation manner as this embodiment, the deployment process of the physical network specifically includes:
firstly, finding all Spine nodes and polling by Spine node information;
the Spine node applies for own resources through the resource pool and records the resources;
the Spine node finds all Leaf nodes connected with the Spine node through the link information and conducts polling through the Leaf node information;
the Leaf node detects whether the own record has the applied common information, if so, the Leaf node reads the record, otherwise, the Leaf node applies for the own resource through the resource pool and records the resource;
finding the Ethernet interface of the Leaf node through the link relationship, and connecting and recording the Ethernet interface of the corresponding Spine node according to the link information;
applying for and recording IP addresses for the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node through the resource pool;
the Leaf node and the Leaf node respectively record 1 neighbor relation;
repeating the steps until all equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine architecture network according to a BGP public configuration template;
and issuing the configuration data to the equipment through the southbound interface.
In combination with a possible implementation manner as this embodiment, if the role of the newly added device is a Leaf node, the step 2 specifically includes the following steps:
(1) applying for resources for the newly added equipment through the resource pool and recording;
(2) finding a Spine node connected with the newly added Leaf node through the link relationship, and polling by using the Spine node;
(3) the Spine node reads own resources from the existing records;
(4) the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node are inquired through the link information and connected and recorded;
(5) applying for and recording resources for the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node through the resource pool;
(6) the Spine node and the Leaf node respectively record 1 neighbor relation;
(7) repeating the steps (2) to (6) until all the equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine architecture network according to a BGP public configuration template;
(8) and issuing the configuration data to the equipment through the southbound interface.
In combination with a possible implementation manner as this embodiment, if the role of the newly added device is a Spine node, the step 2 specifically includes the following steps:
(1) applying for resources for the newly added equipment through the resource pool and recording;
(2) finding a Leaf node connected with the newly added Spine node through the link relationship, and polling by using the Leaf node;
(3) reading own resources from the existing records by the Leaf node;
(4) the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node are inquired through the link information and are connected and recorded;
(5) applying for and recording resources for the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node through the resource pool;
(6) the Leaf node and the Spine node respectively record 1 neighbor relation;
(7) repeating the steps (2) to (6) until all the equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine architecture network according to a BGP public configuration template;
(8) and issuing the configuration data to the equipment through the southbound interface.
With reference to a possible implementation manner of this embodiment, if the role of the device to be deleted is a Leaf node, step 3 specifically includes the following steps:
(1) finding out a Leaf node needing to be deleted, and inquiring the resource of the Leaf node needing to be deleted from the existing records;
(2) finding all Spine nodes connected with the Leaf nodes needing to be deleted through link management, and polling by the Spine nodes;
(3) finding the resource of the Spine node according to the existing record;
(4) finding out that the Ethernet interface of the Spine node is connected with and recorded by the Ethernet interface of the Leaf node through the link relation;
(5) finding out the resources of the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node from the existing records;
(6) the Spine node records the deleted 1 neighbor relation;
(7) and (4) repeating the steps (2) to (6) until all the Spine nodes are polled, constructing configuration data of the Leaf-Spine architecture network, sending the configuration data to the equipment through the southward interface, deleting redundant neighbor configurations of the Spine nodes, and deleting the configuration data of the Leaf nodes.
In combination with a possible implementation manner as this embodiment, if the role of the newly added device is a Spine node, step 3 specifically includes the following steps:
(1) finding a Spine node needing to be deleted, and inquiring the resources of the Spine node needing to be deleted from the existing records;
(2) finding all Leaf nodes connected with Spine nodes needing to be deleted through link management, and polling by the Leaf nodes;
(3) finding out the resources of the Leaf node through the existing records;
(4) finding out that the Ethernet interface of the Leaf node is connected with the Ethernet interface of the Spine node through the link relationship and recording;
(5) finding out the resources of the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node from the existing records;
(6) the Leaf node records the deleted 1 neighbor relation;
(7) and (5) repeating the steps (2) to (6) until all the Spine nodes are polled, constructing configuration data of the Leaf-Spine architecture network, sending the configuration data to the equipment through the southward interface, deleting redundant neighbor configurations of the Leaf nodes, and deleting the configuration data of the Spine nodes.
In combination with a possible implementation manner as this embodiment, when the underlying network is opened through the OSPF protocol, the step 1 specifically includes the following steps:
collecting topology information of a Leaf-spine architecture network;
and pre-configuring a resource pool.
And finding the connected Leaf by polling Spine, and finding and printing the corresponding PORT _ NAME.
Applying for OSPF _ NAME, OSPF _ AREA, ROUTER _ ID, LOOPBACK _ NUMBER and LOOPBACK _ IP information from the resource pool;
and constructing configuration data according to a public configuration template with the protocol type of OSPF, and issuing configuration to the switch through the southbound interface.
The technical scheme of the embodiment of the invention has the following beneficial effects:
the technical scheme of the embodiment of the invention automatically deploys a physical network according to a network topology structure, a bottom layer network is opened through BGP or OSPF, if new equipment is detected to be added into the existing network topology, the corresponding configuration is issued to the newly added equipment, and the intercommunicated configuration is also issued to the equipment related to the newly added equipment; if a device deletion is detected, the corresponding configuration on the device with which it is associated is deleted. According to the invention, the physical network is automatically deployed through the topological relation, so that the complex and error-prone operation of one equipment operation of a deployment person is reduced, the deployment of the physical network becomes rapid and simple, the configuration of the equipment can be rapidly and flexibly adjusted according to the change of networking, and the intercommunication of the physical network is ensured.
Description of the drawings:
FIG. 1 is a flow diagram illustrating a method for automatic deployment of a physical network in accordance with an exemplary embodiment;
FIG. 2 is a network topology diagram of an original Spine Leaf architecture, according to an example embodiment;
fig. 3 is a diagrammatic illustration of a network topology in which a Leaf node has been added to the network of fig. 2.
Detailed Description
The invention is further illustrated by the following examples in conjunction with the accompanying drawings:
in order to clearly explain the technical features of the present invention, the following detailed description of the present invention is provided with reference to the accompanying drawings. The following disclosure provides many different embodiments, or examples, for implementing different features of the invention. To simplify the disclosure of the present invention, the components and arrangements of specific examples are described below. Moreover, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. It should be noted that the components illustrated in the figures are not necessarily drawn to scale. Descriptions of well-known components and processing techniques and procedures are omitted so as to not unnecessarily limit the invention.
FIG. 1 is a flow chart illustrating a method for automatic deployment of a physical network in accordance with an exemplary embodiment. As shown in fig. 1, a method for automatically deploying a physical network according to an embodiment of the present invention includes the following steps:
step 1: automatically deploying a physical network according to a network topology structure, and opening a bottom layer network through a BGP protocol or an OSP protocol;
step 2: detecting that newly added equipment is required to be added into the existing network topology, issuing corresponding configuration to the newly added equipment, and issuing intercommunicated configuration data to associated equipment;
and step 3: and when detecting that the equipment needs to be deleted, deleting the corresponding configuration of the equipment and deleting the corresponding configuration data on the equipment associated with the equipment.
The embodiment automatically deploys the physical network based on the topological structure, and solves the problem that the configuration of the underlying network is complicated when the SDN controller is deployed; and the equipment configuration is automatically adjusted according to the change of the topological structure, so that the intercommunication of the physical network is ensured.
With reference to a possible implementation manner of this embodiment, in step 1, according to a topology structure of a Leaf-Leaf architecture network, a connection relationship between Leaf and Leaf is found, a resource pool is used to apply for a corresponding resource, and corresponding BGP configuration information or OSPF configuration information is generated and sent to a device through a southward interface of an SDN controller.
With reference to a possible implementation manner of this embodiment, when the underlying network is opened through the BGP protocol, step 1 specifically includes the following steps:
collecting topology information of a Leaf-spine architecture network;
pre-configuring a resource pool: modifying AS numbers, loopback interface address fields and loopback interface numbers of the Spine node and the Leaf node AS required, and address fields of interconnection interfaces of the Spine node and the Leaf node;
pre-configuring a BGP public configuration template of the equipment;
and carrying out automatic deployment of the physical network.
In combination with a possible implementation manner as this embodiment, the deployment process of the physical network specifically includes:
firstly, finding all Spine nodes and polling by Spine node information;
the Spine node applies for own resources through the resource pool and records the resources;
the Spine node finds all Leaf nodes connected with the Spine node through the link information and then conducts polling through the Leaf node information;
the Leaf node detects whether the own record has the applied common information, if so, the Leaf node reads the record, otherwise, the Leaf node applies for the own resource through the resource pool and records the resource;
finding the Ethernet interface of the Leaf node through the link relationship, and connecting and recording the Ethernet interface of the corresponding Spine node according to the link information;
applying for and recording IP addresses for the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node through the resource pool;
the Leaf node and the Leaf node respectively record 1 neighbor relation;
repeating the steps until all equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine framework network according to a BGP public configuration template;
and issuing the configuration data to the equipment through the southbound interface.
In combination with a possible implementation manner as this embodiment, if the role of the newly added device is a Leaf node, the step 2 specifically includes the following steps:
(1) applying for resources for the newly added equipment through the resource pool and recording;
(2) finding a Spine node connected with the newly added Leaf node through the link relationship, and polling by using the Spine node;
(3) the Spine node reads own resources from the existing records;
(4) the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node are inquired through the link information and connected and recorded;
(5) applying for and recording resources for the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node through the resource pool;
(6) the Spine node and the Leaf node respectively record 1 neighbor relation;
(7) repeating the steps (2) to (6) until all the equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine architecture network according to a BGP public configuration template;
(8) and issuing the configuration data to the equipment through the southbound interface.
With reference to a possible implementation manner of this embodiment, if the role of the newly added device is a Spine node, step 2 specifically includes the following steps:
(1) applying for resources for the newly added equipment through the resource pool and recording;
(2) finding a Leaf node connected with the newly added Spine node through the link relationship, and polling by using the Leaf node;
(3) reading own resources from the existing records by the Leaf node;
(4) the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node are inquired through the link information and connected and recorded;
(5) applying for and recording resources for the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node through the resource pool;
(6) the Leaf node and the Spine node respectively record 1 neighbor relation;
(7) repeating the steps (2) to (6) until all the equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine architecture network according to a BGP public configuration template;
(8) and issuing the configuration data to the equipment through the southbound interface.
In combination with a possible implementation manner as this embodiment, if the device role to be deleted is a Leaf node, the step 3 specifically includes the following steps:
(1) finding out a Leaf node to be deleted, and inquiring the resource of the Leaf node to be deleted from the existing record;
(2) finding all Spine nodes connected with the Leaf nodes needing to be deleted through link management, and polling by the Spine nodes;
(3) finding the resource of the Spine node according to the existing record;
(4) finding out that the Ethernet interface of the Spine node is connected with and recorded by the Ethernet interface of the Leaf node through the link relation;
(5) finding out the resources of the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node from the existing records;
(6) the Spine node records the deleted 1 neighbor relation;
(7) and (4) repeating the steps (2) to (6) until all the Spine nodes are polled, constructing configuration data of the Leaf-Spine architecture network, sending the configuration data to the equipment through the southward interface, deleting redundant neighbor configurations of the Spine nodes, and deleting the configuration data of the Leaf nodes.
In combination with a possible implementation manner as this embodiment, if the role of the newly added device is a Spine node, step 3 specifically includes the following steps:
(1) finding a Spine node needing to be deleted, and inquiring the resources of the Spine node needing to be deleted from the existing records;
(2) finding all Leaf nodes connected with Spine nodes needing to be deleted through link management, and polling by the Leaf nodes;
(3) finding out the resources of the Leaf node through the existing records;
(4) finding out that the Ethernet interface of the Leaf node is connected with the Ethernet interface of the Spine node through the link relationship and recording;
(5) finding out the resources of the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node from the existing records;
(6) the Leaf node records the deleted 1 neighbor relation;
(7) and (5) repeating the steps (2) to (6) until all the Spine nodes are polled, constructing configuration data of the Leaf-Spine architecture network, sending the configuration data to the equipment through the southward interface, deleting redundant neighbor configurations of the Leaf nodes, and deleting the configuration data of the Spine nodes.
In combination with a possible implementation manner as this embodiment, when the underlying network is opened through the OSPF protocol, the step 1 specifically includes the following steps:
collecting topology information of a Leaf-spine architecture network;
and pre-configuring a resource pool.
And finding the connected Leaf by polling Spine, and finding and printing the corresponding PORT _ NAME.
Applying for OSPF _ NAME, OSPF _ AREA, ROUTER _ ID, LOOPBACK _ NUMBER and LOOPBACK _ IP information from the resource pool;
and constructing configuration data according to a public configuration template with the protocol type of OSPF, and issuing configuration to the switch through the southbound interface.
The process of using the method of the present invention to automatically deploy a physical network is described in detail below by taking 2 spine and 2 Leaf as examples of the current networking in combination with a classic Leaf-spine architecture.
For a classical Leaf-Spine architecture networking, as shown in fig. 2 and 3, according to a network topology structure, a connection relationship between a Spine and a Leaf is found, a resource pool is used for applying for a corresponding resource, corresponding configuration information is generated, and the configuration information is issued to a device through a southbound interface of an SDN controller, so that a physical network is opened through BGP or OSPF.
The configuration of the physical network can be flexibly adjusted according to the change of the networking, and the equipment configuration can be adjusted in real time when Spine or Leaf nodes are added or deleted, so that the intercommunication of the physical network is ensured.
1. As shown in fig. 2, which is an original network topology diagram of the present invention, an SDN controller collects topology information.
2. The protocol type, OSPF/BGP, is configured, and BGP is taken as an example in the present example for explanation.
3. Pre-configuring a resource pool, and modifying according to needs, for example:
spine node AS number: 600
And (3) looping an interface address field by the Spine node: 2.2.2.0/24
Line node loopback interface number 100
Leaf node AS number: 800
The Leaf node loopback interface address field: 1.1.1.0/24
Round node loopback interface number 100
Spine and Leaf connect the node interconnection interface address field: 192.168.10.0/24
4. And pre-configuring a common configuration template of the equipment, wherein the common configuration template is used for constructing configuration data together with the applied resources.
Taking a simple configuration behavior example of a command line, a common configuration template with a protocol type of BGP is as follows:
the xxxxxxxx indicates that corresponding configuration can be added according to requirements, and a 'no' is correspondingly added to a command when the configuration is deleted.
5. The automatic deployment of the physical network is carried out, and the specific deployment method comprises the following steps:
(1) all Spine nodes are found first, as shown in FIG. 2, Spine01 and Spine 02. Polling is performed by Spine node information. Take Spine01 as an example.
(2) Spine01 applies for its own resources through the resource pool and records:
AS＝600
LOOPBACK_NUMBER＝100
LOOPBACK _ IP 2.2.2.1/32 yields route _ ID 2.2.2.1.1
(3) Spine01 finds all Leaf connections to itself through link information, such as Leaf01 and Leaf02 shown in fig. 2. Then polling is performed with Leaf node information, for example Leaf 01.
(4) The Leaf01 detects that the record itself has the applied common information, if yes, it reads from the record, if not, it applies itself resource through the resource pool and records:
AS＝800
LOOPBACK_NUMBER＝100
LOOPBACK _ IP 1.1.1/32 yields route _ ID 1.1.1.1.1
(5) Finding that the Eth1/1 interface of the Spine01 is connected with the Eth1/1 interface of the Leaf01 through a link relation and recording:
Spine01:PORT_NAME＝Eth1/1
Leaf01:PORT_NAME＝Eth1/1
(6) applying for an IP address and recording through an Eth1/1 interface of the resource pool, Spine01 and an Eth1/1 interface of the Leaf 01:
Spine01:PORT_IP＝192.168.10.1/30
Leaf01:PORT_IP＝192.168.10.2/30
(7) spine01 records 1 neighbor relation:
NEIGHBOR_AS＝800，NEIGHBOR_IP＝192.168.10.2
the configuration of Spine01 at this time is as follows:
the expression xxxxxxxx can add corresponding configuration according to the requirement.
(8) Leaf01 records 1 neighbor relation:
NEIGHBOR_AS＝600，NEIGHBOR_IP＝192.168.10.1
the configuration of Leaf01 at this time is as follows:
the expression xxxxxxxx can add corresponding configuration according to the requirement.
(9) And after the polling of all the equipment node information is finished, replacing the initial configuration with the recorded resources, constructing configuration data according to a common configuration template with the protocol type being BGP, and finally issuing the configuration to the equipment through a southbound interface.
6. As shown in fig. 3, when detecting that there is a new device, a new Leaf03 is added on the basis of fig. 2, and the physical network is triggered to automatically deploy, the original BGP neighbor relationship is not changed, and a new neighbor relationship configuration is added, which includes the following specific processes:
(1) finding the new device Leaf03, and recording the new device Leaf for the device through the resource pool.
AS＝800
LOOPBACK_NUMBER＝100
LOOPBACK _ IP 1.1.1.5/32 gets ROUTER _ ID 1.1.1.5
(2) Judging that the role of the node is Leaf, finding a Spine node connected with the node through a link relationship, as shown in fig. 3, Spine01 and Spine02, and polling Spine, for example Spine 01.
(3) Spine01 reads its own resources from the existing records:
AS＝600
LOOPBACK_NUMBER＝100
LOOPBACK_IP＝1.1.1.1/32
ROUTER_ID＝1.1.1.1
(4) the Eth1/3 interface of the Spine01 inquired through the link information is connected with the Eth1/3 interface of the Leaf03 and records:
Spine01:PORT_NAME＝Eth1/3
Leaf03:PORT_NAME＝Eth1/3
(5) applying for resources and recording through an Eth1/3 interface of the resource pool, Spine01 and an Eth1/3 interface of the Leaf 03:
Spine01:PORT_IP＝192.168.10.17/30
Leaf03:PORT_IP＝192.168.10.18/30
(6) spine01 records 1 neighbor relation:
NEIGHBOR_AS＝800，NEIGHBOR_IP＝192.168.10.18
the configuration of Spine01 at this time is as follows:
the expression xxxxxxxx can add corresponding configuration according to the requirement.
(7) Leaf01 records 1 neighbor relation:
NEIGHBOR_AS＝600，NEIGHBOR_IP＝192.168.10.17
the configuration of Leaf01 at this time is as follows:
the expression xxxxxxxx can add corresponding configuration according to the requirement.
(8) And after all the related equipment nodes are polled, replacing the initial configuration with the recorded resources, constructing configuration data according to a common configuration template with the protocol type being BGP, and issuing the configuration for the equipment through a southbound interface.
7. The processing flow of the newly added Spine node is basically the same as that of the newly added Leaf node, and only in the step (2), the Spine node is identified, the connected Leaf nodes are found through the link relationship, and then polling is carried out by the Leaf nodes.
8. On the basis of fig. 3, deleting Leaf03, and returning to fig. 2, when detecting that there is a device deletion, triggering physical network automatic configuration, the specific flow is as follows:
(1) finding the deleted device node Leaf03, and inquiring the own resource from the existing record
AS＝800
LOOPBACK_NUMBER＝100
LOOPBACK_IP＝1.1.1.5/32
ROUTER_ID＝1.1.1.5
(2) All Spine connected to Leaf03 is found through link management, as shown in fig. 2 as Spine01 and Spine 02. Take the example of spin node polling, as spin 01.
(3) Find its own resources of Spine01 through existing records:
AS＝600
LOOPBACK_NUMBER＝100
LOOPBACK_IP＝1.1.1.1/32
ROUTER_ID＝1.1.1.1
(4) finding out that the Eth1/3 interface of Spine01 and the Eth1/3 interface of Leaf03 are connected and recorded through a link relation:
Spine01:PORT_NAME＝Eth1/3
Leaf03:PORT_NAME＝Eth1/3
(5) finding out the resources of Eth1/3 port of Spine01 and Eth1/3 port of Leaf03 from the existing records:
Spine01:PORT_IP＝192.168.10.17/30
Leaf03:PORT_IP＝192.168.10.18/30
(6) spine01 records the deleted 1 neighbor relations:
NEIGHBOR_AS＝800，NEIGHBOR_IP＝192.168.10.18
the configuration of Spine01 at this time is as follows:
(7) after polling, the Spine node constructs configuration data according to the common configuration template with the protocol type being BGP, and sends the configuration data to the equipment through the southbound interface, and the Spine node only needs to delete redundant neighbor configuration.
(8) Finally, all interconnect-related configurations of Leaf03 are deleted, and the configuration of Leaf03 is as follows:
9. the process of deleting Spine nodes and Leaf nodes is similar, except that in step (2), all Leaf nodes connected to Spine nodes are found through the deleted Spine nodes, and polling is started by the Leaf nodes.
10. When the OSPF protocol is selected, a configuration template corresponding to the OSPF is provided, configuration resources required by the OSPF configuration are applied, corresponding configuration data are constructed, and the configuration data are issued to the equipment through a southward interface.
For example: the OSPF configuration template is as follows:
the expression xxxxxxxx can add corresponding configuration according to the requirement.
(1) And pre-configuring a resource pool.
(2) And finding the connected Leaf by polling Spine, and finding and printing the corresponding PORT _ NAME.
(3) And applying for OSPF _ NAME, OSPF _ AREA, ROUTER _ ID, LOOPBACK _ NUMBER, LOOPBACK _ IP and other information from the resource pool.
(4) And constructing configuration data for a public configuration template of the OSPF according to the protocol type, and issuing the configuration to the switch through the southbound interface.
The invention automatically deploys a physical network according to a network topology structure, a bottom layer network is opened through BGP or OSPF, if new equipment is detected to be added into the existing network topology, the corresponding configuration is issued to the newly added equipment, and the intercommunicated configuration is issued to the equipment related to the newly added equipment; if a device deletion is detected, the corresponding configuration on the device with which it is associated is deleted. According to the invention, the physical network is automatically deployed through the topological relation, so that the complex and error-prone operation of one equipment operation of a deployment person is reduced, the deployment of the physical network becomes rapid and simple, the configuration of the equipment can be rapidly and flexibly adjusted according to the change of networking, and the intercommunication of the physical network is ensured.
The foregoing is only a preferred embodiment of the present invention, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and these modifications and improvements are also considered to be within the scope of the present invention.
Claims (9)
1. A method for automatically deploying a physical network is characterized by comprising the following steps:
step 1: automatically deploying a physical network according to a network topology structure, and opening a bottom layer network through a BGP protocol or an OSPF protocol;
step 2: detecting that newly added equipment is required to be added into the existing network topology, issuing corresponding configuration to the newly added equipment, and issuing intercommunicated configuration data to associated equipment;
and step 3: when detecting that the equipment needs to be deleted, deleting the corresponding configuration of the equipment, and deleting the corresponding configuration data on the equipment associated with the equipment;
when the underlying network is opened through the BGP protocol, the step 1 specifically comprises the following steps:
collecting topology information of a Leaf-spine architecture network;
pre-configuring a resource pool: modifying AS numbers, loopback interface address fields and loopback interface numbers of the Spine node and the Leaf node AS required, and address fields of interconnection interfaces of the Spine node and the Leaf node;
pre-configuring a BGP public configuration template of the equipment;
and carrying out automatic deployment of the physical network.
2. The method according to claim 1, wherein in step 1, according to a topology structure of a Leaf-Spine architecture network, a connection relationship between Spine and Leaf is found, a resource pool is used to apply for a corresponding resource, and corresponding BGP configuration information or OSPF configuration information is generated and sent to a device through a southbound interface of an SDN controller.
3. The method according to claim 1, wherein the physical network deployment process specifically comprises:
firstly, finding all Spine nodes and polling by Spine node information;
the Spine node applies for own resources through the resource pool and records the resources;
the Spine node finds all Leaf nodes connected with the Spine node through the link information and then conducts polling through the Leaf node information;
the Leaf node detects whether the own record has the applied common information, if so, the Leaf node reads the record, otherwise, the Leaf node applies for the own resource through the resource pool and records the resource;
finding the Ethernet interface of the Leaf node through the link relationship, and connecting and recording the Ethernet interface of the corresponding Spine node according to the link information;
applying for and recording IP addresses for the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node through the resource pool;
the Leaf node and the Leaf node respectively record 1 neighbor relation;
repeating the steps until all equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine framework network according to a BGP public configuration template;
and issuing the configuration data to the equipment through the southbound interface.
4. The method according to claim 1, wherein if the new device role is a Leaf node, the step 2 specifically includes the following steps:
(1) applying for resources for the newly added equipment through the resource pool and recording the resources;
(2) finding a Spine node connected with the newly added Leaf node through the link relationship, and polling by using the Spine node;
(3) the Spine node reads own resources from the existing records;
(4) the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node are inquired through the link information and connected and recorded;
(5) applying for and recording resources for the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node through the resource pool;
(6) the Spine node and the Leaf node respectively record 1 neighbor relation;
(7) repeating the steps (2) to (6) until all the equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine architecture network according to a BGP public configuration template;
(8) and issuing the configuration data to the equipment through the southbound interface.
5. The method according to claim 1, wherein if the newly added device role is a Spine node, the step 2 specifically includes the following steps:
(1) applying for resources for the newly added equipment through the resource pool and recording;
(2) finding a Leaf node connected with the newly added Spine node through the link relationship, and polling by using the Leaf node;
(3) reading own resources from the existing records by the Leaf node;
(4) the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node are inquired through the link information and connected and recorded;
(5) applying for and recording resources for the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node through the resource pool;
(6) the Leaf node and the Spine node respectively record 1 neighbor relation;
(7) repeating the steps (2) to (6) until all the equipment node information polling is completed, replacing the initial configuration with the recorded resources, and constructing configuration data of a Leaf-spine architecture network according to a BGP public configuration template;
(8) and issuing the configuration data to the equipment through the southbound interface.
6. The method according to claim 1, wherein if the device to be deleted is a Leaf node, the step 3 specifically includes the following steps:
(1) finding out a Leaf node to be deleted, and inquiring the resource of the Leaf node to be deleted from the existing record;
(2) finding all Spine nodes connected with the Leaf nodes needing to be deleted through link management, and polling by the Spine nodes;
(3) finding the resource of the Spine node according to the existing record;
(4) finding out that the Ethernet interface of the Spine node is connected with the Ethernet interface of the Leaf node through the link relation and recording;
(5) finding out the resources of the Ethernet interface of the Spine node and the Ethernet interface of the Leaf node from the existing records;
(6) the Spine node records the deleted 1 neighbor relation;
(7) and (4) repeating the steps (2) to (6) until all the Spine nodes are polled, constructing configuration data of the Leaf-Spine architecture network, sending the configuration data to the equipment through the southward interface, deleting redundant neighbor configurations of the Spine nodes, and deleting the configuration data of the Leaf nodes.
7. The method according to claim 1, wherein if the deleted device role is a Spine node, the step 3 specifically includes the following steps:
(1) finding a Spine node needing to be deleted, and inquiring the resources of the Spine node needing to be deleted from the existing records;
(2) finding all Leaf nodes connected with Spine nodes needing to be deleted through link management, and polling by the Leaf nodes;
(3) finding out the resources of the Leaf node through the existing records;
(4) finding out that the Ethernet interface of the Leaf node is connected with the Ethernet interface of the Spine node through the link relationship and recording;
(5) finding out the resources of the Ethernet interface of the Leaf node and the Ethernet interface of the Spine node from the existing records;
(6) the Leaf node records the deleted 1 neighbor relation;
(7) and (5) repeating the steps (2) to (6) until all the Spine nodes are polled, constructing configuration data of the Leaf-Spine architecture network, sending the configuration data to the equipment through the southward interface, deleting redundant neighbor configurations of the Leaf nodes, and deleting the configuration data of the Spine nodes.
8. A method for automatically deploying a physical network is characterized by comprising the following steps:
step 1: automatically deploying a physical network according to a network topology structure, and opening a bottom layer network through a BGP protocol or an OSPF protocol;
and 2, step: detecting that newly added equipment is required to be added into the existing network topology, issuing corresponding configuration to the newly added equipment, and issuing intercommunicated configuration data to associated equipment;
and step 3: when detecting that the equipment needs to be deleted, deleting the corresponding configuration of the equipment, and deleting the corresponding configuration data on the equipment associated with the equipment;
when the underlying network is opened through the OSPF protocol, the step 1 specifically includes the following steps:
collecting topology information of a Leaf-spine architecture network;
pre-configuring a resource pool;
finding out the connected Leaf by polling Spine, and finding and printing the corresponding PORT _ NAME;
applying for OSPF _ NAME, OSPF _ AREA, ROUTER _ ID, LOOPBACK _ NUMBER and LOOPBACK _ IP information from the resource pool;
and constructing configuration data according to a public configuration template with the protocol type of OSPF, and issuing configuration to the switch through the southbound interface.
9. The method according to claim 8, wherein in step 1, according to a topology structure of a Leaf-Spine architecture network, a connection relationship between Spine and Leaf is found, a resource pool is used to apply for a corresponding resource, and corresponding BGP configuration information or OSPF configuration information is generated and sent to the device through a southbound interface of the SDN controller.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910674758.6A CN110572273B (en) | 2019-07-24 | 2019-07-24 | Method for automatically deploying physical network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910674758.6A CN110572273B (en) | 2019-07-24 | 2019-07-24 | Method for automatically deploying physical network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110572273A CN110572273A (en) | 2019-12-13 |
| CN110572273B true CN110572273B (en) | 2022-05-24 |
Family
ID=68773134
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910674758.6A Active CN110572273B (en) | 2019-07-24 | 2019-07-24 | Method for automatically deploying physical network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110572273B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111341379B (en) * | 2020-02-22 | 2022-03-22 | 苏州浪潮智能科技有限公司 | Method and equipment for testing storage device |
| CN113839864A (en) * | 2020-06-23 | 2021-12-24 | 中兴通讯股份有限公司 | Network deployment method, device, system and storage medium of autonomous domain system AS |
| CN113055232B (en) * | 2021-03-11 | 2022-07-12 | 浪潮思科网络科技有限公司 | Network configuration deployment method, device and equipment |
| CN113381879B (en) * | 2021-05-17 | 2023-02-28 | 浪潮思科网络科技有限公司 | SDN-based network deployment method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000349778A (en) * | 1999-06-08 | 2000-12-15 | Nec Corp | Topological information automatic construction method, device for the same method and machine readable recording medium recording program |
| CN1696905A (en) * | 2001-11-06 | 2005-11-16 | 佳能株式会社 | Dynamic network device reconfiguration and device |
| CN106487558A (en) * | 2015-08-31 | 2017-03-08 | 中兴通讯股份有限公司 | A kind of method and apparatus realizing the scalable appearance of access device |
| CN107634842A (en) * | 2016-07-18 | 2018-01-26 | 阿里巴巴集团控股有限公司 | Method for discovering network topology and device |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2005340983A (en) * | 2004-05-25 | 2005-12-08 | Hitachi Ltd | Hierarchical network and configuration method thereof, and apparatus |
| CN100466611C (en) * | 2005-10-28 | 2009-03-04 | 华为技术有限公司 | Processing method for network node configuration information when network topology changing |
| WO2009049325A1 (en) * | 2007-10-12 | 2009-04-16 | Pie Digital, Inc. | System and method for automatic configuration and management of home network devices |
| EP2509273A4 (en) * | 2009-12-30 | 2014-05-14 | Zte Corp | Method and system for updating network topology in multi-protocol label switching system |
| US9331910B2 (en) * | 2013-06-19 | 2016-05-03 | Cumulus Networks, Inc. | Methods and systems for automatic generation of routing configuration files |
| US20180123896A1 (en) * | 2016-11-01 | 2018-05-03 | Huawei Technologies Co., Ltd. | Systems and methods for hierarchical network management |
-
2019
- 2019-07-24 CN CN201910674758.6A patent/CN110572273B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000349778A (en) * | 1999-06-08 | 2000-12-15 | Nec Corp | Topological information automatic construction method, device for the same method and machine readable recording medium recording program |
| CN1696905A (en) * | 2001-11-06 | 2005-11-16 | 佳能株式会社 | Dynamic network device reconfiguration and device |
| CN106487558A (en) * | 2015-08-31 | 2017-03-08 | 中兴通讯股份有限公司 | A kind of method and apparatus realizing the scalable appearance of access device |
| CN107634842A (en) * | 2016-07-18 | 2018-01-26 | 阿里巴巴集团控股有限公司 | Method for discovering network topology and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110572273A (en) | 2019-12-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110572273B (en) | Method for automatically deploying physical network | |
| US11200133B1 (en) | Intelligent device role discovery | |
| TWI324456B (en) | An intelligent automatic setting restoration method and device | |
| TW202026896A (en) | Asynchronous object manager in a network routing environment | |
| JP2019525631A (en) | Configuring forwarding policies | |
| US11575592B2 (en) | Message processing method and apparatus, control-plane device, and computer storage medium | |
| US11558252B2 (en) | Learning by inference from previous deployments | |
| US20110231543A1 (en) | Network management control program, network management control device, and network management control method | |
| CN110572439B (en) | Cloud monitoring method based on metadata service and virtual forwarding network bridge | |
| WO2017198003A1 (en) | Service processing method and system | |
| CN110855509A (en) | Novel cloud SPTN network architecture | |
| JP2004272905A (en) | Generation of virtual network topology | |
| US10560370B1 (en) | Intelligent exception recovery in network services | |
| US9231831B2 (en) | Method and network system of converting a layer two network from a spanning tree protocol mode to a routed mesh mode without a spanning tree protocol | |
| US20090207756A1 (en) | Network configuration management method | |
| CN103716181A (en) | LAN_WAN virtual channel implementation method under gateway device routing mode | |
| CN110351141A (en) | FlexE interface managerial method, device and network element | |
| KR20060040335A (en) | Network managing device and method thereof | |
| US11159370B2 (en) | Bulk discovery of devices behind a network address translation device | |
| US11907253B2 (en) | Secure cluster pairing for business continuity and disaster recovery | |
| CN108933680A (en) | A kind of method and apparatus of SPTN equipment resource management | |
| CN111416732B (en) | Method and device for automatically configuring service for capacity expansion of network equipment in SDN | |
| CN109218462A (en) | A kind of IP distribution method of cloud data center physical host | |
| WO2016065925A1 (en) | Controller replacing method and device | |
| CN110830598A (en) | Method and network equipment for establishing and transmitting interface address and alias in BGP (Border gateway protocol) session |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |