Large-scale test network and implementation method thereof

Abstract

The invention provides an implementation method for a large-scale test network, and relates to the technical field of computer networks, and the method comprises the steps: employing a static routing or IGP protocol at an edge, employing a VRF technology on a router, and achieving the deployment of a wide-area test network, the wide-area test network comprises a test router and a core router, segmenting the wide area test network into at least one core network slice by the VRF technology; when the user applies for the test, the test router is used for managing the core network slice, the access of the user equipment is completed, and the test is completed, and the access mode comprises static routing access and IGP access. By adopting the scheme, the construction of a large-scale test network is realized.

Description

Technical Field

[0001] The present application relates to the field of computer network technology, and in particular to a large-scale test network and an implementation method thereof. Background Art

[0002] As the Internet faces many challenges in terms of security, performance, and scalability, research on the future Internet is in full swing. The purpose of the future Internet test facility is to support the test infrastructure for future Internet research. The history of the development of the Internet is a process of continuous exploration and continuous fault tolerance. There have been many studies on the challenges of the current Internet's scalability, security, performance, etc. However, due to the huge involvement of the existing Internet, some new ideas are difficult to be deployed on the existing Internet. Therefore, research on the future Internet test facility has been carried out one after another. This requires the test facility to comprehensively consider research in different directions, integrate them on the basis of these technologies, form core equipment, and finally combine large-scale test networks to carry out large-scale tests of these technologies and equipment.

[0003] There are many test network technologies, but there are not many solutions for wide-area and large-scale test networks. Most test networks focus on local area networks built in a small area. Even for wide-area test networks, existing backbone network resources are used as much as possible to connect small test networks in different places. The reason is that the construction of a wide-area backbone test network requires solving three key problems. The first is the isolation between tests. Since it is a test, unexpected failures may occur. If the failure of a test leads to the problem of the entire backbone network, it will bring huge problems. The second is the authenticity and observability of the test. The main reason for using a real network for testing is that it can be highly consistent with the production environment, and the results can be well applied to the existing network. This requires the network configuration to be real, the resources used to be real, and the observed results to be real. The third and most important thing is to solve the economic problem of the test. The operation cost of the wide-area network is high, and more parallel tests should be accommodated as much as possible to give full play to the use of the wide-area network. If a large network can only carry out one test at a time, the economic efficiency is difficult to guarantee.

[0004] In traditional test network facilities, virtual routers are generally used, and the lower-level network topology is invisible to the upper-level test. The advantage of this is that it can support a variety of tests, but the disadvantages are also obvious: on the one hand, this mode will lead to a decrease in routing performance, making it difficult to achieve a test environment close to the throughput of the existing network; on the other hand, this mode will also bring about an increase in complexity and a decrease in observation capabilities, which is not conducive to analyzing test results. Summary of the invention

[0005] The present application aims to solve one of the technical problems in the related art at least to some extent.

[0006] To this end, the first purpose of this application is to propose a method for implementing a large-scale test network, which realizes the construction of a large-scale test network. Based on this network, distributed, wide-area network experiments can be carried out. At the same time, multiple experiments can be carried out concurrently and isolated from each other. Each node in the experiment comes from a real network, so the test results can be observed.

[0007] The second objective of this application is to propose a large-scale test network.

[0008] To achieve the above-mentioned objectives, the first aspect of the present application proposes a method for implementing a large-scale test network, including: using static routing or IGP protocol at the edge and VRF technology on the router to implement the deployment of a wide area test network, wherein the wide area test network includes a test router and a core router, and VRF technology divides the wide area test network into at least one core network slice; when a user applies for a test, the core network slice is managed through the test router to complete the access of the user device and complete the test, wherein the access methods include static routing access and IGP access.

[0009] Optionally, in one embodiment of the present application, a static routing access method is used to complete access to a user-side router, including:

[0010] Provide pre-configured core network slices for trial users through the trial router VRF;

[0011] On the test router, static routing across VPNs is used to achieve access from the local node to the remote node and from the public VRF to the slice VRF.

[0012] Plan a public VRF and public IGP process, configure a sub-interface on the physical interface between the test router and the core router, and add the sub-interface to the public VRF on the test router.

[0013] Plan a public VRF and public IGP process on the core router, configure a sub-interface on the physical interface between the core router and the test router, add the sub-interface to the public VRF on the core router side, and form an IGP neighbor relationship with the test router.

[0014] Optionally, in one embodiment of the present application, the access of the user-side router is completed by adopting an IGP access mode, including:

[0015] Provide several preset core network slices for test users through the test router VRF, and plan a corresponding number of independent IGP processes to be applied to each core network slice;

[0016] On the core router, the independent IGP process and the public IGP process are introduced to each other, and the routes belonging to the corresponding core network slice in the public VRF are introduced to the virtual slice through tag control;

[0017] The core router plans a public VRF, independent IGP processes with the same process number as the access router, and a public IGP process. Each independent IGP process and the public IGP process are associated with the public VRF.

[0018] To achieve the above-mentioned purpose, a second aspect of the present invention provides a large-scale test network, which is implemented by the above-mentioned large-scale test network implementation method.

[0019] The implementation method of the large-scale test network of the embodiment of the present application uses VRF technology to divide the wide-area test network into several slices, each slice operates independently, and the resources are isolated from each other. Even if a slice fails, it will not affect the network operation of other slices. The slices can communicate through a common exchange center. The interconnection topology of the nodes inside the slice is visible to the test user. The tester can observe the actual operation status of the network and can see the IP addresses of the backbone network routers along the way through traceroute.

[0020] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0022] Figure 1 A flowchart of a method for implementing a large-scale test network provided in Example 1 of the present application;

[0023] Figure 2 A logical architecture diagram of a large-scale test network according to an embodiment of the present application;

[0024] Figure 3 A node logic architecture diagram of an embodiment of the present application;

[0025] Figure 4 A schematic diagram of static routing access in an embodiment of the present application;

[0026] Figure 5 This is a schematic diagram of IGP access according to an embodiment of the present application. DETAILED DESCRIPTION

[0027] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0028] The following describes a large-scale test network and an implementation method thereof according to an embodiment of the present application with reference to the accompanying drawings.

[0029] Figure 1 A flowchart of a method for implementing a large-scale test network provided in Example 1 of the present application.

[0030] like Figure 1 As shown, the implementation method of the large-scale test network includes the following steps:

[0031] Step 101, deploying a wide area test network by using static routing or IGP protocol at the edge and VRF technology on the router, wherein the wide area test network includes a test router and a core router, and the VRF technology divides the wide area test network into at least one core network slice;

[0032] In this embodiment, a large-scale white box test network based on VRF is proposed. VRF (Virtual Route Forwarding) is a VPN (Virtual Private Network) construction technology, which aims to solve the problem of the same private network address segment of different enterprises. In order to prevent conflicts, the same private network address is placed in different VRF tables. Since a device may be connected to multiple users at the same time, these users (routes) need to be isolated from each other, so VRF is used at this time, and each user on the device corresponds to a VRF. In addition to maintaining the global IP routing table, the device also maintains an independent IP routing table for each VRF, which is called a VRF routing table. It should be noted that the global IP routing table and each VRF routing table are independent or isolated from each other. For each VRF table, there are two major attributes: route distinguisher (Route Distinguisher: RD) and route target (Route Target: RT). RD (Route-Distinguisher) is used to distinguish the local VRF, and this attribute is only valid locally. 8-byte RD + 4-byte IPv4 address constitutes a 96-bit VPNv4 route, which converts a non-unique IPv4 address into a unique VPN-IPv4 address. The VPNv4 route is transmitted (distinguished) within the ISP domain, and RD tags the routes in a VRF, thereby achieving address reuse without conflict. RT (Route Tagert) is an extended community attribute of BGP, which is divided into Import RT and Export RT, which are used for route import and export policies respectively. By configuring import and export RT, you can control the sending and receiving routes. When exporting routes from the VRF table, the VRF routes must be marked with export RT. When importing routes into the VRF table, only routes with RT tags that match any import RT in the VRF table will be imported into the VRF table.

[0033] In this embodiment, a wide area test network is designed. By using virtual router VRF technology on user-side routers, test routers, and core routers, the wide area test network is divided into several slices. Each slice runs independently and the resources are isolated from each other. Even if a slice fails, it will not affect the network operation of other slices. The slices can communicate through a common exchange center. The interconnection topology of the nodes inside the slice is visible to the test user. The tester can observe the actual operation status of the network and can see the IP addresses of the backbone network routers along the way through traceroute. Figure 2 shown.

[0034] In this embodiment, the test network includes a core router, a test router, and user equipment. The main function of the core router is core forwarding and edge interconnection. The test router is mainly responsible for the division and interconnection of resources of the preset core network slices, access to self-developed equipment or test networks, slicing of test sites, and interconnection with corresponding slice resources of the test sites. The access router is mainly responsible for providing access, including providing access to existing network users and providing test networks without preset slices. The access router provides the original network slice to the test user. This original slice is built based on VRF and does not run any internal routing process. The user designs and configures the corresponding routing strategy. Figure 3 As shown in the figure, the test network uses static routing or internal routing protocols at the edge and VRF on routers to achieve wide-area, large-scale test network deployment, user-visible backbone network, pre-configured network, and plug-and-play for test users.

[0035] Step 102, when the user applies for a test, the core network slice is managed through the test router, the user equipment access is completed, and the test is completed, where the access methods include static routing access and IGP access.

[0036] In this embodiment, a large-scale test network implementation based on static routing is proposed. For each test, there is a wide area test network slice, an address block, and several access nodes. The address block is allocated to each access node. Each access node is connected to the test router through static routing, and the test router is used as the default gateway. The test router and the core router run a common IGP process. The interconnection address between the test router and the core router is equipped with a sub-interface, and the static route is published to the public IGP by using RT and RD. No matter how many test slices there are, there is only one public IGP process. Specifically, the steps are as follows:

[0037] Provide pre-configured core network slices for trial users through trial router VRF (based on different physical / sub-interface VLANs).

[0038] On the experimental router, static routing across VPNs is used to achieve access from the local node to the remote node, and access from the public VRF to the slice VRF.

[0039] Plan a public VRF (vpn-WhiteBox) and a public IGP process (process 2), configure a sub-interface on the physical interface between the test router and the core router, and add the sub-interface to the public VRF on the test router.

[0040] Plan a public VRF (vpn-WhiteBox) and a public IGP process (process 2) on the core router, configure a sub-interface on the physical interface between the core router and the test router, add the sub-interface to the public VRF on the core router side, and form an IGP neighbor relationship with the test router.

[0041] IGP can be ISIS protocol, OSPF protocol or any internal routing protocol supported by the router. Figure 4 shown.

[0042] The following is an example configuration, assuming that each VRF corresponds to the 2001:db8:: / 32 summary address space, each node VRF corresponds to a / 40 detailed address space, and the routing protocol is ISIS.

[0043] Configuration of user equipment (CE equipment)

[0044] #Use loopback port to simulate white box slicing users

[0045] interface LoopBack100

[0046] ipv6 address 2001:db8:100::100 / 40

[0047] interface GigabitEthernet1 / 5 / 4.1001

[0048] mtu9600

[0049] statistic enable

[0050] ipv6 mtu 9600

[0051] vlan-type dot1q1001

[0052] ipv6 address 2001:db8:100::2 / 64

[0053] #User test network summary route points to PE device

[0054] ipv6 route-static 2001:db8::32 2001:db8:100::1

[0055] Test router (PE device) configuration

[0056] #Configure slice VPN and backbone network public VPN

[0057] ip vpn-instance slice1001

[0058] ipv6-family

[0059] route-distinguisher 38272:1001

[0060] apply-label per-instance

[0061] vpn-target 38272:1001export-extcommunity

[0062] vpn-target 38272:1001import-extcommunity

[0063] #Configure the backbone network public VPN

[0064] ip vpn-instance vpn-WhiteBox

[0065] ipv6-family

[0066] #Configure the ISIS process of the backbone network public VPN and introduce static routes into ISIS. Use the routing policy to limit the import of only the 40-bit routes of the slice.

[0067] isis 2vpn-instance vpn-WhiteBox

[0068] is-level level-2

[0069] cost-style wide

[0070] network-entity 02.1829.0020.0002.00

[0071] #

[0072] ipv6 enable topology ipv6

[0073] ipv6 import-route static route-policy W-Box

[0074] #

[0075] route-policy W-Box permit node 10

[0076] if-match ipv6 address prefix-list W-Slice

[0077] #

[0078] route-policy W-Box deny node 1000

[0079] #

[0080] ip ipv6-prefix W-Slice index 10permit 2001:db8::20less-equal 40

[0081] Test router (PE device) configuration

[0082] #Subinterface connected to CE

[0083] interface GigabitEthernet1 / 0 / 9.1001

[0084] vlan-type dot1q 1001

[0085] mtu9600

[0086] ip binding vpn-instance slice1001

[0087] ipv6 enable

[0088] ipv6 address 2001:db8:100::1 / 64

[0089] ipv6 mtu 9600

[0090] statistic enable

[0091] #Subinterface connected to P - Public VPN, VPN address can be set according to convention

[0092] interface FlexE2 / 0 / 1000.2

[0093] vlan-type dot1q 2

[0094] mtu9600

[0095] ip binding vpn-instance vpn-WhiteBox

[0096] ipv6 enable

[0097] ipv6 address 2001:203:2:10::1 / 64

[0098] ipv6 mtu 9600

[0099] statistic enable

[0100] isis ipv6 enable 2

[0101] isis circuit-type p2p

[0102] #Configure static routing from the slice to the remote node, specifying the destination VPN as the backbone network public VPN

[0103] ipv6 route-static vpn-instance slice1001 2001:db8::32vpn-instancevpn-WhiteBox tag 1

[0104] #Configure static routing across VPNs and specify the destination VPN as the slice VPN

[0105] ipv6 route-static vpn-instance vpn-WhiteBox 2001:db8:100::40vpn-instance slice1001 tag 1

[0106] Configuration of core router (P device)

[0107] #Configure the backbone network public VPN

[0108] ip vpn-instance vpn-WhiteBox

[0109] ipv6-family

[0110] In this embodiment, a large-scale test network implementation with IGP access is provided. Specifically, the user connects to the test router by using the IGP protocol. Each test router runs the IGP process of this slice and interconnects with the IGP in the user-side router. The core router runs a public VRF and a public IGP process. The test router will mark the routes learned from the user side for each slice, indicating the attributes of the slice corresponding to the route, and publish it to the public IGP after marking. On the core router, the IGP processes of each independent test need to be run at the same time. The specific configuration steps are as follows:

[0111] 1) Provide several pre-set core network slices for test users through the test router VRF (based on different physical / sub-interface VLANs), and plan a corresponding number of independent IGP processes to be applied to each core network slice (CE in each VRF publishes its own routing prefix through IGP)

[0112] 2) The core routers introduce routes between independent IGP processes and public IGP processes, and use tags to control the import of only routes in the public VRF that belong to the corresponding core network slice into the virtual slice.

[0113] 3) The core router plans a public VRF (vpn-WhiteBox, same as static / VRF slicing), independent IGP processes with the same process number as the access router, and a public IGP process (process 2, same as static / VRF slicing). All independent IGP processes and the public IGP process are associated with the public VRF.

[0114] IGP can be ISIS protocol, OSPF protocol or any internal routing protocol supported by the router. Figure 5 shown.

[0115] The following is a specific use case. The address block used is 2001:db8:: / 32. Eight ISIS slices are preset, with flags from 2041 to 2048, and RD flags are 38272:2401, etc.

[0116] Configuration of user equipment (CE equipment)

[0117] #Use loopback port to simulate white box slicing users

[0118] interface LoopBack100

[0119] ipv6 address 2001:db8:101::100 / 40

[0120] ISIS 2041

[0121] is-level level-2

[0122] cost-style wide

[0123] network-entity 11.2041.0100.0001.00

[0124] #

[0125] ipv6 enable topology ipv6

[0126] #

[0127] #

[0128] interface GigabitEthernet1 / 5 / 4.2041

[0129] mtu9600

[0130] statistic enable

[0131] ipv6 mtu 9600

[0132] isis ipv6 enable 2041

[0133] vlan-type dot1q 2041

[0134] ipv6 address 2001:db8:101::2 / 64

[0135] Test router (PE device) configuration

[0136] #Configure slice VPN and backbone network public VPN

[0137] ip vpn-instance slice2401

[0138] ipv6-familyroute-distinguisher 38272:2401

[0139] apply-label per-instance

[0140] vpn-target 38272:2401export-extcommunity

[0141] vpn-target 38272:2401import-extcommunity

[0142] #Configure the ISIS process for slice VPN

[0143] isis 2041vpn-instance slice2041

[0144] is-level level-2

[0145] cost-style widenetwork-entity 11.2041.0020.0002.00

[0146] #

[0147] ipv6 enable topology ipv6

[0148] #

[0149] Test router (PE device) configuration

[0150] #Subinterface connected to CE

[0151] interface GigabitEthernet1 / 0 / 9.2401

[0152] vlan-type dot1q 2401

[0153] mtu9600

[0154] ip binding vpn-instance slice2401

[0155] ipv6 enableipv6 address 2001:db8:101::1 / 64

[0156] ipv6 mtu 9600

[0157] statistic enable isis ipv6 enable 2401

[0158] #Subinterface connected to P - Slice VPN, VPN address can be set according to convention

[0159] interface FlexE2 / 0 / 1000.2401

[0160] vlan-type dot1q 2401

[0161] mtu9600

[0162] ip binding vpn-instance slice2401

[0163] ipv6 enable

[0164] ipv6 address 2001:203:2:10::1 / 64

[0165] ipv6 mtu 9600

[0166] statistic enable

[0167] isis ipv6 enable 2401

[0168] isis circuit-type p2p

[0169] Configuration of core router (P device)

[0170] #Configure the backbone network public VPN

[0171] ip vpn-instance vpn-WhiteBox

[0172] ipv6-family

[0173] #Configure the ISIS process of the backbone network public VPN. When the public process leads to the slice process routing, add the tag isis 2vpn-instance vpn-WhiteBox

[0174] is-level level-2

[0175] cost-style widenetwork-entity 02.1829.0020.0010.00

[0176] #

[0177] ipv6 enable topology ipv6

[0178] ipv6 import-route isis 2401tag 2401

[0179] ipv6 import-route isis 2402tag 2402

[0180] ipv6 import-route isis 2403tag 2403

[0181] ipv6 import-route isis 2404tag 2404

[0182] ipv6 import-route isis 2405tag 2405

[0183] ipv6 import-route isis 2406tag 2406

[0184] ipv6 import-route isis 2407tag 2407

[0185] ipv6 import-route isis 2408tag 2408

[0186] #

[0187] Configuration of core router (P device)

[0188] #Configure the ISIS process of the slice VPN. When the slice process leads the public process route, it is based on tag filtering (using route-policy)

[0189] #

[0190] isis 2401vpn-instance vpn-WhiteBox

[0191] is-level level-2

[0192] cost-style wide

[0193] network-entity 11.2401.0020.0010.00

[0194] #

[0195] ipv6 enable topology ipv6

[0196] ipv6 import-route isis 2route-policy 2401

[0197] #

[0198] #

[0199] route-policy 2401permit node 10

[0200] if-match tag 2401

[0201] #

[0202] route-policy 2401deny node 1000

[0203] #

[0204] Configuration of core router (P device)

[0205] #Subinterface connected to PE - Slice VPN

[0206] interface GigabitEthernet1 / 0 / 0.2401

[0207] vlan-type dot1q 2401

[0208] mtu9600

[0209] ip binding vpn-instance vpn-WhiteBox

[0210] ipv6 enable

[0211] ipv6 address 2001:203:2:10::2 / 64

[0212] ipv6 mtu 9600

[0213] statistic enable

[0214] isis ipv6 enable 2401

[0215] isis circuit-type p2p

[0216] #

[0217] Configuration of core router (P device)

[0218] #Subinterface connected to the remote P device

[0219] interface GigabitEthernet1 / 0 / 1.2

[0220] vlan-type dot1q 2

[0221] mtu9600

[0222] ip binding vpn-instance vpn-WhiteBox

[0223] ipv6 enable

[0224] ipv6 address 2001:203:10:19::1 / 64

[0225] ipv6 mtu 9600

[0226] statistic enable

[0227] isis ipv6 enable 2

[0228] isis circuit-type p2p

[0229] #

[0230] In this embodiment, a large-scale test network is proposed to achieve rapid test network construction through pre-set network slices. Specifically, several static routing slices and several slices using IGP access are pre-set on the test router and core router. When the test user applies for a test, a static routing or a test network slice using IGP is automatically allocated according to the requirements.

[0231] In this embodiment, a large-scale test network implementation is proposed. When static routing or IGP slicing does not meet the needs, an original slice is allocated to the test user by using an access router. This original slice is built based on VRF and does not run any internal routing process. The user designs and configures the corresponding routing strategy.

[0232] In order to implement the above embodiments, the present application also proposes a large-scale test network, which is implemented by the implementation method of the large-scale test network described in the above embodiments.

[0233] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0234] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0235] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0236] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute the instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0237] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0238] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0239] In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0240] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A method for implementing a large-scale test network, characterized in that: include: The wide area test network is deployed by using static routing or IGP protocol at the edge and VRF technology on the router, wherein the wide area test network includes a test router and a core router, and the VRF technology divides the wide area test network into at least one core network slice; When the user applies for a test, the core network slice is managed through the test router to complete the access of the user device and complete the test. The access methods include static routing access and IGP access.

2. The method according to claim 1, characterized in that Use static routing access to complete the user-side router access, including: Provide pre-configured core network slices for trial users through the trial router VRF; On the test router, static routing across VPNs is used to achieve access from the local node to the remote node and from the public VRF to the slice VRF. Plan a public VRF and public IGP process, configure a sub-interface on the physical interface between the test router and the core router, and add the sub-interface to the public VRF on the test router. Plan a public VRF and public IGP process on the core router, configure a sub-interface on the physical interface between the core router and the test router, add the sub-interface to the public VRF on the core router, and form an IGP neighbor relationship with the test router.

3. The method according to claim 1, characterized in that The IGP access method is used to complete the user-side router access, including: Provide several preset core network slices for test users through the test router VRF, and plan a corresponding number of independent IGP processes to be applied to each core network slice; On the core router, the independent IGP process and the public IGP process are introduced to each other, and the routes belonging to the corresponding core network slice in the public VRF are introduced to the virtual slice through tag control; The core router plans a public VRF, independent IGP processes with the same process number as the access router, and a public IGP process. Each independent IGP process and the public IGP process are associated with the public VRF.

4. A large-scale test network, characterized in that: The test network is implemented by the method according to claims 1-3.

Images