CN112887137A - Method and device for realizing interface index consistency - Google Patents

Method and device for realizing interface index consistency Download PDF

Info

Publication number
CN112887137A
CN112887137A CN202110090062.6A CN202110090062A CN112887137A CN 112887137 A CN112887137 A CN 112887137A CN 202110090062 A CN202110090062 A CN 202110090062A CN 112887137 A CN112887137 A CN 112887137A
Authority
CN
China
Prior art keywords
interface
message
forwarding
index
information
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.)
Granted
Application number
CN202110090062.6A
Other languages
Chinese (zh)
Other versions
CN112887137B (en
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.)
New H3C Security Technologies Co Ltd
Original Assignee
New H3C Security 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 New H3C Security Technologies Co Ltd filed Critical New H3C Security Technologies Co Ltd
Priority to CN202110090062.6A priority Critical patent/CN112887137B/en
Publication of CN112887137A publication Critical patent/CN112887137A/en
Application granted granted Critical
Publication of CN112887137B publication Critical patent/CN112887137B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0213Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/901Indexing; Data structures therefor; Storage structures

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application provides a method and a device for realizing interface index consistency, wherein the method is applied to forwarding vm and comprises the following steps: receiving a first message for controlling vm to send, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface; storing and establishing a mapping relation between the name information of the first interface and the first interface index; when the first interface starts an SNMP trap mode, sending a first trap message to the control vm, wherein the first trap message comprises the first interface index, so that the control vm forwards the first trap message to an SNMP client according to the first interface index.

Description

Method and device for realizing interface index consistency
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing interface index consistency.
Background
The Broadband Access Server (BRAS) is a product of the service evolution of the metropolitan area network. The business of the metropolitan area network is continuously developed, and under the condition that only access equipment and a backbone router exist, a user cannot perform authentication and authorization management, so that the operation management and the long-term development of the network are not facilitated. After introducing BRAS between access network and backbone network, BRAS is used as access gateway of network service, providing broadband access, authentication, authorization and charging for users, managing user bandwidth, converging user service flow, terminating Point-to-Point Protocol Over Ethernet (PPPoE) connection on user Ethernet, and providing multiple service.
As shown in fig. 1, fig. 1 is a schematic diagram of a transfer control separation architecture in the prior art. In fig. 1, a virtual machine (vm) is divided into three roles. Namely: control vm (CTRL-vm), forwarding vm (FWD-vm), and BRAS-vm. BRAS-CP runs in vm comprised by several tens of servers with virtualization technology, as shown within the dashed box shown in fig. 1.
CTRL-vm is in a main standby mode; the BRAS-vm is also in a master-standby mode and is managed by the CTRL-vm; FWD-vm is a separate network element and is subject to the management of CTRL-vm. BRAS-UP may communicate with BRAS-vm by forwarding vm. The FWD-vm is responsible for message forwarding between CTRL-vm and BRAS-UP; CTRL-vm can remotely configure and view the configuration in all vm's through local commands, and CTRL-vm can also control the communication between all vm's.
There are multiple types of interfaces on BRAS-CP, and the distribution of the multiple types of interfaces at each vm is shown in table 1 below:
table 1 distribution of multiple types of access in different vm
Figure BDA0002912113260000021
Note:
Figure BDA0002912113260000022
indicating that interface information exists, but no operational data, only for configuration;
the check mark indicates that the interface information exists and the operation data also exists, and the check mark is not only used for configuration but also used for operation of the service;
x denotes that interface information does not exist.
Because the OM channel is used as the only channel for controlling and configuring the BRAS-CP by peripheral equipment (such as an SNMP client, a NETCONF client and a command line terminal), for the configuration or display of an interface, a CTRL-vm is required to send a NETCONF request to a vm with the interface, and after the vm is processed, a processing result is returned to the CTRL-vm and is displayed by the CTRL-vm.
At this time, if the interface of the FWD-vm or BRAS-vm has configured the SNMP trap mode, when the FWD-vm or BRAS-vm sends a trap message, it needs to distinguish whether the trap message is related to the interface. And if the trap message is related to the interface, the vm adds interface name information in the trap message and transparently transmits the trap message to the CTRL-vm. The CTRL-vm converts the interface name into an interface index in the CTRL-vm, and after the conversion is completed, the CTRL-vm sends the interface index to a Simple Network Management Protocol (SNMP) client.
However, the above-mentioned method of exchanging trap information also brings the following problems: 1) each vm is a device independent of each other, and interfaces of the same type may exist in different vms, but because each vm only allocates an interface index of an interface in the vm, the interface indexes of the interfaces of the same type cannot be consistent; 2) before sending a trap message, each vm needs to obtain interface name information through an interface index allocated to the vm, and then the interface name information is packaged in a newly-added field. The CTRL-vm needs to analyze the interface name information in the newly added field, convert the interface name into an interface index in the CTRL-vm, replace the index before conversion with the converted index and send the index to the SNMP client, so that the efficiency is influenced; 3) fields need to be added in the trap message to represent interface name information, so that the coupling degree between each vm is increased.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for implementing interface index consistency, so as to solve the problem of efficiency caused by frequent index conversion of CTRL-vm when each vm sends trap information to CTRL-vm due to inconsistent interface indexes of interfaces of the same type between different vms, and the problem of increased coupling degree between vms due to the fact that fields need to be added to express interface name information in the trap information.
In a first aspect, the present application provides a method for implementing interface index consistency, where the method is applied to forwarding vm, and the method includes:
receiving a first message for controlling vm to send, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface;
storing and establishing a mapping relation between the name information of the first interface and the first interface index;
when the first interface starts an SNMP trap mode, sending a first trap message to the control vm, wherein the first trap message comprises the first interface index, so that the control vm forwards the first trap message to an SNMP client according to the first interface index.
In a second aspect, the present application provides a method for implementing interface index consistency, where the method is applied to control vm, and the method includes:
sending a first message to a forwarding vm, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface, so that the forwarding vm stores and establishes a mapping relationship between the name information of the first interface and the first interface index;
receiving a first trap message sent by the forwarding vm, wherein the first trap message comprises the first interface index;
and forwarding the first trap message to an SNMP client according to the first interface index.
In a third aspect, the present application provides an apparatus for implementing interface index consistency, where the apparatus is applied to forwarding vm, and the apparatus includes:
a receiving unit, configured to receive a first message for controlling a vm to send, where the first message includes name information of a first interface that the vm has and a first interface index corresponding to the first interface;
the storage establishing unit is used for storing and establishing the mapping relation between the name information of the first interface and the first interface index;
a sending unit, configured to send a first trap packet to the control vm when the first interface starts an SNMP trap mode, where the first trap packet includes the first interface index, so that the control vm forwards the first trap packet to an SNMP client according to the first interface index.
In a fourth aspect, the present application provides an apparatus for implementing interface index consistency, where the apparatus is applied to control vm, and the method includes:
a sending unit, configured to send a first message to a forwarding vm, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface, so that the forwarding vm stores and establishes a mapping relationship between the name information of the first interface and the first interface index;
a receiving unit, configured to receive a first trap packet sent by the forwarding vm, where the first trap packet includes the first interface index;
the sending unit is further configured to forward the first trap packet to an SNMP client according to the first interface index.
In a fifth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to perform the method provided by the first aspect of the present application.
In a sixth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to perform the method provided by the first aspect of the present application.
Therefore, by applying the method and the device for realizing interface index consistency provided by the application, the forwarding vm receives a first message for controlling the sending of the vm, and the first message comprises name information of a first interface of the forwarding vm and a first interface index corresponding to the first interface. And forwarding vm for storing and establishing a mapping relation between the name information of the first interface and the first interface index. When the first interface opens the SNMP trap mode, the forwarding vm sends a first trap message to the control vm, wherein the first trap message comprises a first interface index, so that the control vm directly forwards the first trap message to the SNMP client according to the first interface index.
Therefore, the problem of efficiency caused by frequent index conversion of the CTRL-vm when each vm sends the trap information to the CTRL-vm due to the fact that the interface indexes of the same type of interface among different vms are not consistent is solved, and the problem that the coupling degree among vms is increased due to the fact that fields need to be added to express interface name information in the trap information is solved. The processing efficiency is improved, and meanwhile, the maintenance cost is low and the coupling degree between the vms is reduced.
Drawings
FIG. 1 is a schematic diagram of a transfer control separation architecture in the prior art;
fig. 2 is a flowchart of a method for implementing interface index consistency according to an embodiment of the present application;
fig. 3 is a flowchart of another implementation method for interface index consistency according to an embodiment of the present application;
fig. 4 is a timing chart associated with an interface index according to an embodiment of the present disclosure;
fig. 5 is a timing diagram associated with another interface index according to an embodiment of the present disclosure;
fig. 6 is a structural diagram of an apparatus for implementing interface index consistency according to an embodiment of the present application;
fig. 7 is a structural diagram of another apparatus for implementing interface index consistency according to an embodiment of the present application;
fig. 8 is a hardware structure diagram of a network device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the corresponding listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The following describes in detail an implementation method of interface index consistency provided in the embodiment of the present application. Referring to fig. 2, fig. 2 is a flowchart of an implementation method for interface index consistency according to an embodiment of the present application. The method is applied to forwarding vm, and the implementation method of interface index consistency provided by the embodiment of the application may include the following steps.
Step 210, receiving a first message for controlling vm to send, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface.
Specifically, the vm is controlled to obtain name information of the first interface included in the forwarding vm. And controlling vm to allocate a corresponding first interface index to the first interface. The first interface index is used for indicating a first interface included in forwarding vm and also used for indicating a second interface included in controlling vm.
And controlling the vm to distribute a first interface index for the first interface and then generating a first message. And controlling the vm to send a first message to the forwarding vm, wherein the first message comprises name information of the first interface and a first interface index corresponding to the first interface.
And after the forwarding vm receives the first message, obtaining the name information of the first interface and the first interface index from the forwarding vm.
In this embodiment, the first message may specifically be a Netconf protocol message. The first interface may in particular be a physical interface and/or a logical interface comprised by the forwarding vm.
Step 220, storing and establishing a mapping relationship between the name information of the first interface and the first interface index.
Specifically, according to the description in step 210, after the forwarding vm obtains the name information of the first interface and the first interface index, the mapping relationship between the name information of the first interface and the first interface index is stored and established.
It is understood that the mapping relationship may be stored in the form of a table.
Step 230, when the first interface starts the SNMP trap mode, sending a first trap packet to the control vm, where the first trap packet includes the first interface index, so that the control vm forwards the first trap packet to the SNMP client according to the first interface index.
Specifically, in this embodiment of the application, if the SNMP trap mode is already enabled by the first interface, when the first interface needs to report a trap, the vm is first forwarded to obtain the second interface index of the first interface. And then, the forwarding vm determines the name information of the first interface according to the second interface index. And forwarding the vm from the mapping relation through the name information of the first interface to obtain a first interface index corresponding to the first interface.
Forwarding vm generates a first trap message, where the first trap message includes a first interface index.
And after the control vm receives the first trap message, acquiring a first interface index from the first trap message. And controlling the vm to determine that the first interface index is the interface index which is previously allocated to the first interface in the forwarding vm according to the first interface index, and controlling the vm to directly forward the first trap message to the SNMP client.
Therefore, by applying the method for implementing interface index consistency provided by the present application, the forwarding vm receives a first message that controls sending of the vm, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface. And forwarding vm for storing and establishing a mapping relation between the name information of the first interface and the first interface index. When the first interface opens the SNMP trap mode, the forwarding vm sends a first trap message to the control vm, wherein the first trap message comprises a first interface index, so that the control vm forwards the first trap message to the SNMP client according to the first interface index.
Therefore, the problem of efficiency caused by frequent index conversion of the CTRL-vm when each vm sends the trap information to the CTRL-vm due to the fact that the interface indexes of the same type of interface among different vms are not consistent is solved, and the problem that the coupling degree among vms is increased due to the fact that fields need to be added to express interface name information in the trap information is solved. The processing efficiency is improved, and meanwhile, the maintenance cost is low and the coupling degree between the vms is reduced.
Optionally, before step 210 in this embodiment of the present application, a step of forwarding vm to create a third interface and sending attribute information of the third interface to the control vm is further included.
In particular, the forwarding vm comprises an interface physical chip. And forwarding the vm to obtain interface data of the interface physical chip, and creating a third interface in the interface physical chip according to the interface data, wherein the third interface is a physical interface.
And forwarding vm to obtain attribute information of the third interface, wherein the attribute information of the interface specifically comprises interface name information, interface type information, interface physical type information, vm information of the interface, slot number information of the interface, daughter card number information and the like.
And after the forwarding vm is started, generating a registration message. And the forwarding vm sends a registration message to the control vm, and the control vm registers the forwarding vm after receiving the registration message. And after the registration is successful, controlling the vm to send a registration success message to the forwarding vm. And after receiving the registration success message, the forwarding vm generates a second message, wherein the second message comprises the attribute information of the third interface.
In this embodiment of the present application, the second message may specifically be a Netconf protocol message.
Forwarding vm sends a second message to the controlling vm. And after the control vm receives the second message, acquiring the attribute information of the third interface from the second message. And controlling vm to create a corresponding fourth interface according to the attribute information of the third interface. The fourth interface is also a physical interface.
It will be appreciated that each vm, after creating an interface locally, will assign an interface index to that interface. In the embodiment of the present application, forwarding vm and controlling vm allocate an interface index to an interface according to the same attribute information of a third interface after the interface is created locally, but the interface indexes are different.
Optionally, before step 210 in this embodiment of the present application, a step of forwarding a third message that is sent by the vm and is controlled by the vm and creating a fifth interface according to the third message is further included.
Specifically, controlling vm to obtain attribute information of an interface to be created from a configuration file or operating data, where the attribute information of the interface to be created includes interface name information, interface type information, interface physical type information, vm information where the interface is located, slot number information where the interface is located, daughter card number information, and the like.
Alternatively, the first and second electrodes may be,
and controlling the vm to receive the operation of the creation interface input by the user. The create interface operation can be realized by inputting a command line, an MIB operation and a Netconf operation by a user. The interface creating operation comprises interface name information, interface type information, interface physical type information, vm information of the interface, slot number information of the interface, sub card number information and the like.
It can be understood that the above interface name information, interface type information, interface physical type information, vm information where the interface is located, slot number information where the interface is located, and sub-card number information may be referred to as attribute information of the fifth interface to be created.
Controlling vm to generate a third message, the third message including attribute information of a fifth interface to be created. And controlling the vm to send a third message to the vm (for example, forwarding the vm) according to the vm information of the interface.
And after the forwarding vm receives the third message, acquiring the attribute information of the fifth interface from the forwarding vm. And forwarding vm to create a fifth interface locally according to the attribute information of the fifth interface. In the embodiment of the present application, the fifth interface is a logical interface.
And after the fifth interface is established, forwarding the vm to generate a fourth message, wherein the fourth message comprises information that the fifth interface is successfully established. Forwarding vm sends a fourth message to the controlling vm.
And after the control vm receives the fourth message, acquiring the fifth interface creation success information from the fourth message. And controlling the vm to create a sixth interface locally by using the attribute information of the fifth interface according to the successful creation information of the fifth interface. In the embodiment of the present application, the sixth interface is also a logical interface.
And after the sixth interface is created, controlling the vm to allocate an interface index to the sixth interface. And then controlling the vm to acquire the name information of the sixth interface and generate a first message, wherein the first message comprises the name information of the sixth interface and an interface index corresponding to the sixth interface. The control vm sends a first message to the forwarding vm that created the same interface (e.g., the forwarding vm that created the fifth interface) to cause the forwarding vm to perform the aforementioned steps 210-230.
In this embodiment, the third message and the fourth message may specifically be Netconf protocol messages.
It will be appreciated that each vm, after creating an interface locally, will assign an interface index to that interface. In this embodiment of the present application, the forwarding vm and the control vm allocate, according to the same attribute information of the fifth interface, interface indexes to the interfaces after the interfaces are created locally, but the interface indexes are different.
The following describes in detail an implementation method of interface index consistency provided in the embodiment of the present application. Referring to fig. 3, fig. 3 is a flowchart of another implementation method for interface index consistency according to an embodiment of the present application. The method is applied to control vm, and the implementation method of interface index consistency provided by the embodiment of the application may include the following steps.
Step 310, sending a first message to a forwarding vm, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface, so that the forwarding vm stores and establishes a mapping relationship between the name information of the first interface and the first interface index.
Specifically, the vm is controlled to obtain name information of the first interface included in the forwarding vm. And controlling vm to allocate a corresponding first interface index to the first interface. The first interface index is used for indicating a first interface included in forwarding vm and also used for indicating a second interface included in controlling vm.
And controlling the vm to distribute a first interface index for the first interface and then generating a first message. And controlling the vm to send a first message to the forwarding vm, wherein the first message comprises name information of the first interface and a first interface index corresponding to the first interface.
And after the forwarding vm receives the first message, obtaining the name information of the first interface and the first interface index from the forwarding vm.
In this embodiment, the first message may specifically be a Netconf protocol message. The first interface may in particular be a physical interface and/or a logical interface comprised by the forwarding vm.
And after the forwarding vm obtains the name information of the first interface and the first interface index, storing and establishing a mapping relation between the name information of the first interface and the first interface index.
It is understood that the mapping relationship may be stored in the form of a table.
Step 320, receiving a first trap packet sent by the forwarding vm, where the first trap packet includes the first interface index.
Specifically, if the SNMP trap mode is already opened by the first interface, when the first interface needs to report a trap, the vm is forwarded to obtain the second interface index of the first interface. And then, the forwarding vm determines the name information of the first interface according to the second interface index. And forwarding the vm from the mapping relation through the name information of the first interface to obtain a first interface index corresponding to the first interface.
Forwarding vm generates a first trap message, where the first trap message includes a first interface index.
And after the control vm receives the first trap message, acquiring a first interface index from the first trap message.
Step 330, forwarding the first trap message to an SNMP client according to the first interface index.
Specifically, according to the description in step 320, the control vm determines, according to the first interface index, that the first interface index is an interface index previously allocated to the first interface in the forwarding vm, and then controls vm to directly forward the first trap packet to the SNMP client.
Therefore, by applying the method for implementing interface index consistency provided by the present application, the vm is controlled to send a first message to the forwarding vm, where the first message includes the name information of the first interface of the forwarding vm and the first interface index corresponding to the first interface, so that the forwarding vm stores and establishes a mapping relationship between the name information of the first interface and the first interface index. And controlling the vm to receive a first trap message sent by the forwarding vm, wherein the first trap message comprises a first interface index. And controlling the vm to directly forward the first trap message to the SNMP client according to the first interface index.
Therefore, the problem of efficiency caused by frequent index conversion of the CTRL-vm when each vm sends the trap information to the CTRL-vm due to the fact that the interface indexes of the same type of interface among different vms are not consistent is solved, and the problem that the coupling degree among vms is increased due to the fact that fields need to be added to express interface name information in the trap information is solved. The processing efficiency is improved, and meanwhile, the maintenance cost is low and the coupling degree between the vms is reduced.
Optionally, before step 310 in this embodiment of the present application, a step of controlling the vm to receive and forward a second message sent by the vm and create a third interface according to the second message is further included.
In particular, the forwarding vm comprises an interface physical chip. And forwarding the vm to obtain interface data of the interface physical chip, and creating a third interface in the interface physical chip according to the interface data, wherein the third interface is a physical interface.
And the transfer control vm acquires attribute information of the third interface, wherein the attribute information of the interface specifically comprises interface name information, interface type information, interface physical type information, vm information of the interface, slot number information of the interface, daughter card number information and the like.
And after the forwarding vm is started, generating a registration message. And the forwarding vm sends a registration message to the control vm, and the control vm registers the forwarding vm after receiving the registration message. And after the registration is successful, controlling the vm to send a registration success message to the forwarding vm. And after receiving the registration success message, the forwarding vm generates a second message, wherein the second message comprises the attribute information of the third interface.
Forwarding vm sends a second message to the controlling vm. And after the control vm receives the second message, acquiring the attribute information of the third interface from the second message. And controlling vm to create a corresponding third interface according to the attribute information of the third interface. And the third interface for controlling vm to create is also a physical interface.
In this embodiment of the present application, the second message may specifically be a Netconf protocol message.
It will be appreciated that each vm, after creating an interface locally, will assign an interface index to that interface. In the embodiment of the present application, forwarding vm and controlling vm allocate an interface index to an interface according to the same attribute information of a third interface after the interface is created locally, but the interface indexes are different.
Optionally, before step 310 in this embodiment of the present application, a step of controlling the vm to obtain attribute information of the fourth interface and forwarding the attribute information of the fourth interface to the forwarding vm is further included.
Specifically, the vm is controlled to acquire attribute information of a fourth interface to be created to the forwarding vm.
The vm is controlled to acquire attribute information of a fourth interface from the configuration file or the operation data, wherein the attribute information of the fourth interface comprises interface name information, interface type information, interface physical type information, vm information where the interface is located, slot number information where the interface is located, daughter card number information and the like.
Alternatively, the first and second electrodes may be,
the control vm may further acquire attribute information of the fourth interface by receiving a create interface operation input by the user. The create interface operation can be realized by inputting a command line, an MIB operation and a Netconf operation by a user. The interface creating operation comprises interface name information, interface type information, interface physical type information, vm information of the interface, slot number information of the interface, sub card number information and the like.
It can be understood that the above interface name information, interface type information, interface physical type information, vm information where the interface is located, slot number information where the interface is located, and sub-card number information may be referred to as attribute information of the fourth interface.
Controlling vm to generate a third message, the third message comprising attribute information of a fourth interface to be created. And controlling the vm to send a third message to the vm (for example, forwarding the vm) according to the vm information of the interface.
And after the forwarding vm receives the third message, acquiring the attribute information of the fourth interface from the forwarding vm. And forwarding vm to create a fourth interface locally according to the attribute information of the fourth interface. In this embodiment, the fourth interface is a logical interface.
And after the fourth interface is established, forwarding the vm to generate a fourth message, wherein the fourth message comprises information that the fourth interface is successfully established. Forwarding vm sends a fourth message to the controlling vm.
And after the control vm receives the fourth message, obtaining the successful creation information of the fourth interface. And controlling the vm to create a fifth interface locally by using the attribute information of the fourth interface according to the successful creation information of the fourth interface. In the embodiment of the present application, the fifth interface is also a logical interface.
And after the fifth interface is established, controlling the vm to allocate an interface index to the fifth interface. And then controlling the vm to acquire the name information of the fifth interface and generate a first message, wherein the first message comprises the name information of the fifth interface and an interface index corresponding to the fifth interface. The control vm sends a first message to the forwarding vm that created the same interface (e.g., the forwarding vm that created the fourth interface) to cause the forwarding vm to perform the aforementioned steps 210-230.
In this embodiment, the third message and the fourth message may specifically be Netconf protocol messages.
It will be appreciated that each vm, after creating an interface locally, will assign an interface index to that interface. In this embodiment of the present application, forwarding vm and controlling vm allocate an interface index to an interface according to the same attribute information of a fourth interface after the interface is created locally, but the interface indexes are different.
The following describes in detail an implementation method of interface index consistency provided in the embodiment of the present application, by taking a process of processing interface index association between a control vm and a forwarding vm as an example. Referring to fig. 4, fig. 4 is a timing chart of an interface index association provided in an embodiment of the present application.
In fig. 4, for a GE type interface, the forwarding vm includes an interface physical chip. And forwarding vm to obtain interface data of the interface physical chip, and creating a first interface in the interface physical chip according to the interface data, wherein the first interface is a physical interface.
Forwarding vm to obtain attribute information of the first interface, wherein the attribute information of the interface specifically includes interface name information, interface type information, interface physical type information, vm information where the interface is located, slot number information where the interface is located, daughter card number information and the like. And after the first interface is established, forwarding vm to allocate a first interface index to the first interface.
And after the forwarding vm is started and registered successfully with the control vm, generating a first message, wherein the first message comprises attribute information of the first interface.
Forwarding vm sends a first message to the controlling vm. And after the control vm receives the first message, acquiring the attribute information of the first interface from the first message. And controlling vm to create a corresponding second interface according to the attribute information of the first interface. The second interface is also a physical interface.
And after the second interface is established, controlling the vm to allocate a second interface index to the second interface. It will be appreciated that each vm, after creating an interface locally, will assign an interface index to that interface. In the embodiment of the application, forwarding vm and controlling vm allocate an interface index to an interface according to the same attribute information of the first interface after the interface is created locally, but the interface indexes are different.
In the embodiment of the application, after obtaining the name information of the first interface, the control vm allocates a corresponding third interface index to the first interface.
And controlling vm to distribute a third interface index to the first interface and then generating a second message. And controlling the vm to send a second message to the forwarding vm, wherein the second message comprises the name information of the first interface and a third interface index corresponding to the first interface.
And after the forwarding vm receives the second message, obtaining the name information of the first interface and the index of the third interface from the second message. And forwarding vm for storing and establishing a mapping relation between the name information of the first interface and the index of the third interface.
It is understood that the mapping relationship may be stored in the form of a table.
In this embodiment of the application, if the SNMP trap mode is already enabled by the first interface, when the first interface needs to report a trap, the vm is first forwarded to obtain a first interface index of the first interface. And then, the forwarding vm determines the name information of the first interface according to the first interface index. And forwarding the vm from the mapping relation through the name information of the first interface to obtain a third interface index corresponding to the first interface.
Forwarding vm generates a first trap message, where the first trap message includes a third interface index.
And after the control vm receives the first trap message, acquiring a third interface index from the first trap message. And controlling the vm to determine that the third interface index is the interface index which is previously allocated to the first interface in the forwarding vm according to the third interface index, and controlling the vm to directly forward the first trap message to the SNMP client.
It can be understood that, in this embodiment of the present application, the control vm may further obtain attribute information of the interface to be created from the configuration file or the operating data, where the attribute information of the interface to be created includes interface name information, interface type information, interface physical type information, vm information where the interface is located, slot number information where the interface is located, daughter card number information, and the like.
The interface name information, the interface type information, the interface physical type information, the vm information where the interface is located, the slot number information where the interface is located, and the daughter card number information may be referred to as attribute information of a fourth interface to be created.
In this embodiment of the application, after the control vm obtains the name information of the fourth interface, it also allocates a corresponding fourth interface index to the fourth interface.
It will be appreciated that the control vm also generates a third message comprising attribute information of the fourth interface to be created. And controlling the vm to send a third message to the vm (for example, forwarding the vm) according to the vm information of the interface.
And after the forwarding vm receives the third message, acquiring the attribute information of the fourth interface from the forwarding vm. And forwarding vm to create a fifth interface locally according to the attribute information of the fourth interface. In the embodiment of the present application, the fourth interface and the fifth interface are logical interfaces.
At this time, when the control vm generates the second message, the name information and the fourth interface index of the fourth interface, the name information and the third interface index of the first interface may also be carried in the second message, and sent to the forwarding vm.
Therefore, after the forwarding vm receives the second message, the interface name information and the corresponding interface index of the plurality of interfaces are obtained from the forwarding vm. And the forwarding vm stores and establishes a mapping relation between the name information of the interfaces of the plurality of interfaces and the interface index.
The following describes in detail an implementation method of interface index consistency provided in the embodiment of the present application, by taking a process of processing interface index association between a control vm and a forwarding vm as an example. Referring to fig. 5, fig. 5 is a timing diagram of another interface index association provided in the embodiment of the present application.
In fig. 5, the control vm receives a create interface operation of a user input. The create interface operation can be realized by inputting a command line, an MIB operation and a Netconf operation by a user. The interface creating operation comprises interface name information, interface type information, interface physical type information, vm information of the interface, slot number information of the interface, sub card number information and the like.
It can be understood that the above interface name information, interface type information, interface physical type information, vm information where the interface is located, slot number information where the interface is located, and sub-card number information may be referred to as attribute information of the first interface to be created.
Controlling vm to generate a first message comprising attribute information of a first interface to be created. And controlling the vm to send a first message to the vm (for example, forwarding the vm) according to the vm information of the interface.
And after the forwarding vm receives the first message, acquiring the attribute information of the first interface from the forwarding vm. And forwarding vm to create the first interface locally according to the attribute information of the first interface. In the embodiment of the present application, the first interface is a logical interface.
And after the first interface is established, forwarding vm to allocate a first interface index to the first interface. Forwarding vm generates a second message including first interface creation success information. Forwarding vm sends a second message to the controlling vm.
And after the control vm receives the second message, acquiring the successful creation information of the first interface. And controlling the vm to distribute a corresponding second interface index to the first interface according to the successful creation information of the first interface. Meanwhile, the control vm also creates a second interface locally by using the attribute information of the first interface. In the embodiment of the present application, the second interface is also a logical interface.
And after the second interface is established, controlling the vm to allocate a third interface index to the second interface.
It will be appreciated that each vm, after creating an interface locally, will assign an interface index to that interface. In the embodiment of the application, forwarding vm and controlling vm allocate an interface index to an interface according to the same attribute information of the first interface after the interface is created locally, but the interface indexes are different.
And controlling the vm to acquire the name information of the first interface and generate a third message, wherein the third message comprises the name information of the first interface and the second interface index. The control vm sends a third message to the forwarding vm that created the same interface (e.g., the forwarding vm that created the first interface).
And after the forwarding vm receives the third message, obtaining the name information of the first interface and the second interface index from the forwarding vm. And forwarding vm for storing and establishing a mapping relation between the name information of the first interface and the index of the second interface.
In this embodiment of the application, if the SNMP trap mode is already enabled by the first interface, when the first interface needs to report a trap, the vm is first forwarded to obtain a first interface index allocated to the first interface by itself. And then, the forwarding vm determines the name information of the first interface according to the first interface index. And forwarding the vm from the mapping relation through the name information of the first interface to obtain a second interface index corresponding to the first interface.
Forwarding vm to generate a first trap message, where the first trap message includes a second interface index.
And after the control vm receives the first trap message, acquiring a second interface index from the first trap message. And controlling the vm to determine that the second interface index is the interface index which is previously allocated to the first interface in the forwarding vm according to the second interface index, and controlling the vm to directly forward the first trap message to the SNMP client.
Based on the same inventive concept, the embodiment of the application also provides a message processing device corresponding to the implementation method of the interface index consistency. Referring to fig. 6, fig. 6 is a structural diagram of an apparatus for implementing interface index consistency according to an embodiment of the present application, where the apparatus is applied to forward vm, and the apparatus includes:
a receiving unit 610, configured to receive a first message that controls a vm to send, where the first message includes name information of a first interface that the vm has and a first interface index corresponding to the first interface;
a storage establishing unit 620, configured to store and establish a mapping relationship between the name information of the first interface and the first interface index;
a sending unit 630, configured to send a first trap packet to the control vm when the first interface starts an SNMP trap mode, where the first trap packet includes the first interface index, so that the control vm forwards the first trap packet to an SNMP client according to the first interface index.
Optionally, the apparatus further comprises: a creating unit (not shown in the figure) configured to create a third interface and obtain attribute information of the third interface;
the sending unit 630 is further configured to send a second message to the control vm, where the second message includes the attribute information of the third interface, so that the control vm creates a corresponding fourth interface according to the attribute information of the third interface.
Optionally, the receiving unit 610 is further configured to receive a third message sent by the control vm, where the third message includes attribute information of a fifth interface to be created;
the creating unit (not shown in the figure) is further configured to create the fifth interface according to the attribute information of the fifth interface.
Optionally, the apparatus further comprises: an obtaining unit (not shown in the figure), configured to obtain a second interface index of the first interface when the first interface starts an SNMP trap mode, where the second interface index is allocated to the forwarding vm;
a determining unit (not shown in the figure) configured to determine name information of the first interface according to the second interface index;
the obtaining unit (not shown in the figure) is further configured to obtain, from the mapping relationship, a first interface index corresponding to the first interface through the name information of the first interface.
Optionally, the sending unit 630 is further configured to send a fourth message to the control vm, where the fourth message includes the fifth interface creation success information, so that the control vm creates a sixth interface according to the fifth interface creation success information.
Optionally, the first interface is specifically a physical interface and/or a logical interface; the third interface and the fourth interface are physical interfaces; the fifth interface and the sixth interface are logic interfaces.
Based on the same inventive concept, the embodiment of the application also provides an implementation device of the interface index consistency corresponding to the implementation method of the interface index consistency. Referring to fig. 7, fig. 7 is a structural diagram of another apparatus for implementing interface index consistency according to an embodiment of the present application, where the apparatus is applied to control vm, and the apparatus includes:
a sending unit 710, configured to send a first message to a forwarding vm, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface, so that the forwarding vm stores and establishes a mapping relationship between the name information of the first interface and the first interface index;
a receiving unit 720, configured to receive a first trap packet sent by the forwarding vm, where the first trap packet includes the first interface index;
the sending unit 710 is further configured to forward the first trap packet to an SNMP client according to the first interface index.
Optionally, the apparatus further comprises: an obtaining unit (not shown in the figure), configured to obtain name information of a first interface that the forwarding vm has;
an assigning unit (not shown in the figure) for assigning the first interface with the corresponding first interface index.
Optionally, the receiving unit 720 is further configured to receive a second message sent by the forwarding vm, where the second message includes attribute information of a third interface;
the device further comprises: a creating unit (not shown in the figure) configured to create the corresponding third interface according to the attribute information of the third interface.
Optionally, the obtaining unit (not shown in the figure) is further configured to obtain attribute information of a fourth interface to be created to the forwarding vm;
the sending unit 710 is further configured to send a third message to the forwarding vm, where the third message includes attribute information of the fourth interface, so that the forwarding vm creates the corresponding fourth interface according to the attribute information of the fourth interface.
Optionally, the receiving unit 720 is further configured to receive a fourth message sent by the forwarding vm, where the fourth message includes information that a fourth interface is successfully created;
the creating unit (not shown in the figure) is further configured to create the corresponding fifth interface according to the fourth interface creation success information.
Optionally, the first interface is specifically a physical interface and/or a logical interface; the third interface is a physical interface; the fourth interface and the fifth interface are logic interfaces.
Therefore, by applying the device for implementing interface index consistency provided by the present application, the forwarding vm receives a first message that controls sending of the vm, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface. And forwarding vm for storing and establishing a mapping relation between the name information of the first interface and the first interface index. When the first interface opens the SNMP trap mode, the forwarding vm sends a first trap message to the control vm, wherein the first trap message comprises a first interface index, so that the control vm directly forwards the first trap message to the SNMP client according to the first interface index.
Therefore, the problem of efficiency caused by frequent index conversion of the CTRL-vm when each vm sends the trap information to the CTRL-vm due to the fact that the interface indexes of the same type of interface among different vms are not consistent is solved, and the problem that the coupling degree among vms is increased due to the fact that fields need to be added to express interface name information in the trap information is solved. The processing efficiency is improved, and meanwhile, the maintenance cost is low and the coupling degree between the vms is reduced.
Based on the same inventive concept, the embodiment of the present application further provides a network device, as shown in fig. 8, including a processor 810, a transceiver 820 and a machine-readable storage medium 830, where the machine-readable storage medium 830 stores machine-executable instructions capable of being executed by the processor 810, and the processor 810 is caused by the machine-executable instructions to perform the method provided by the embodiment of the present application. The interface index consistency implementation apparatus shown in fig. 6 and fig. 7 may be implemented by using a hardware structure of a network device as shown in fig. 8.
The computer-readable storage medium 830 may include a Random Access Memory (RAM) and a Non-volatile Memory (NVM), such as at least one disk Memory. Alternatively, the computer-readable storage medium 830 may be at least one memory device located remotely from the processor 810.
The Processor 810 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; the Integrated Circuit can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
In embodiments of the present application, the processor 810 is caused by machine-executable instructions stored in the machine-readable storage medium 830 by reading the machine-executable instructions to enable the processor 810 itself and the call transceiver 820 to perform the methods described in embodiments of the present application.
In addition, the embodiment of the present application provides a machine-readable storage medium 830, the machine-readable storage medium 830 stores machine executable instructions, and when the machine executable instructions are called and executed by the processor 810, the machine executable instructions cause the processor 810 itself and the calling transceiver 820 to perform the implementation method of the interface index consistency described in the embodiment of the present application.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
For the embodiment of the apparatus for implementing interface index consistency and the machine-readable storage medium, since the content of the related method is substantially similar to that of the foregoing method embodiment, the description is relatively simple, and for the relevant points, reference may be made to part of the description of the method embodiment.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (14)

1. A method for implementing interface index consistency is applied to forwarding vm, and comprises the following steps:
receiving a first message for controlling vm to send, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface;
storing and establishing a mapping relation between the name information of the first interface and the first interface index;
when the first interface starts an SNMP trap mode, sending a first trap message to the control vm, wherein the first trap message comprises the first interface index, so that the control vm forwards the first trap message to an SNMP client according to the first interface index.
2. The method according to claim 1, wherein before receiving the first message controlling vm transmission, the method further comprises:
creating a third interface and acquiring attribute information of the third interface;
and sending a second message to the control vm, wherein the second message comprises the attribute information of the third interface, so that the control vm creates a corresponding fourth interface according to the attribute information of the third interface.
3. The method according to claim 1, wherein before receiving the first message controlling vm transmission, the method further comprises:
receiving a third message sent by the control vm, wherein the third message comprises attribute information of a fifth interface to be created;
and creating the fifth interface according to the attribute information of the fifth interface.
4. The method according to claim 1, wherein before sending the first trap packet to the control vm, the method further comprises:
when the first interface starts an SNMP trap mode, acquiring a second interface index of the first interface, wherein the second interface index is allocated for the forwarding vm;
determining name information of the first interface according to the second interface index;
and acquiring a first interface index corresponding to the first interface from the mapping relation through the name information of the first interface.
5. The method of claim 3, further comprising:
and sending a fourth message to the control vm, wherein the fourth message includes the fifth interface creation success information, so that the control vm creates a sixth interface according to the fifth interface creation success information.
6. The method according to any of claims 1 to 5, characterized in that the first interface is in particular a physical interface and/or a logical interface; the third interface and the fourth interface are physical interfaces; the fifth interface and the sixth interface are logic interfaces.
7. A method for realizing interface index consistency is applied to control vm, and comprises the following steps:
sending a first message to a forwarding vm, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface, so that the forwarding vm stores and establishes a mapping relationship between the name information of the first interface and the first interface index;
receiving a first trap message sent by the forwarding vm, wherein the first trap message comprises the first interface index;
and forwarding the first trap message to an SNMP client according to the first interface index.
8. The method according to claim 7, wherein before sending the first message to the forwarding vm, the method further comprises:
acquiring name information of a first interface of the forwarding vm;
and allocating a corresponding first interface index to the first interface.
9. The method according to claim 7, wherein before sending the first message to the forwarding vm, the method further comprises:
receiving a second message sent by the forwarding vm, wherein the second message comprises attribute information of a third interface;
and creating the corresponding third interface according to the attribute information of the third interface.
10. The method according to claim 7, wherein before sending the first message to the forwarding vm, the method further comprises:
acquiring attribute information of a fourth interface to be created to the forwarding vm;
and sending a third message to the forwarding vm, where the third message includes attribute information of the fourth interface, so that the forwarding vm creates the corresponding fourth interface according to the attribute information of the fourth interface.
11. The method of claim 10, further comprising:
receiving a fourth message sent by the forwarding vm, wherein the fourth message comprises information that a fourth interface is successfully created;
and creating the corresponding fifth interface according to the fourth interface creation success information.
12. Method according to any of claims 7-11, characterized in that the first interface is in particular a physical interface and/or a logical interface; the third interface is a physical interface; the fourth interface and the fifth interface are logic interfaces.
13. An apparatus for implementing interface index consistency, the apparatus being applied to forwarding vm, the apparatus comprising:
a receiving unit, configured to receive a first message for controlling a vm to send, where the first message includes name information of a first interface that the vm has and a first interface index corresponding to the first interface;
the storage establishing unit is used for storing and establishing the mapping relation between the name information of the first interface and the first interface index;
a sending unit, configured to send a first trap packet to the control vm when the first interface starts an SNMP trap mode, where the first trap packet includes the first interface index, so that the control vm forwards the first trap packet to an SNMP client according to the first interface index.
14. An apparatus for implementing interface index consistency, the apparatus being applied to control vm, the apparatus comprising:
a sending unit, configured to send a first message to a forwarding vm, where the first message includes name information of a first interface that the forwarding vm has and a first interface index corresponding to the first interface, so that the forwarding vm stores and establishes a mapping relationship between the name information of the first interface and the first interface index;
a receiving unit, configured to receive a first trap packet sent by the forwarding vm, where the first trap packet includes the first interface index;
the sending unit is further configured to forward the first trap packet to an SNMP client according to the first interface index.
CN202110090062.6A 2021-01-22 2021-01-22 Method and device for realizing interface index consistency Active CN112887137B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110090062.6A CN112887137B (en) 2021-01-22 2021-01-22 Method and device for realizing interface index consistency

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110090062.6A CN112887137B (en) 2021-01-22 2021-01-22 Method and device for realizing interface index consistency

Publications (2)

Publication Number Publication Date
CN112887137A true CN112887137A (en) 2021-06-01
CN112887137B CN112887137B (en) 2022-05-24

Family

ID=76050425

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110090062.6A Active CN112887137B (en) 2021-01-22 2021-01-22 Method and device for realizing interface index consistency

Country Status (1)

Country Link
CN (1) CN112887137B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102594668A (en) * 2012-02-03 2012-07-18 福建星网锐捷网络有限公司 Message forwarding method, device and exchange equipment
US20180227905A1 (en) * 2015-09-30 2018-08-09 Huawei Technologies Co., Ltd. Air interface resource determining method and apparatus and air interface resource indication method and apparatus
CN108616431A (en) * 2018-04-20 2018-10-02 新华三技术有限公司 A kind of message processing method, device, equipment and machine readable storage medium
CN110351107A (en) * 2018-04-03 2019-10-18 华为技术有限公司 Configuring management method and device
CN110855803A (en) * 2018-08-20 2020-02-28 北京神州泰岳软件股份有限公司 Data acquisition method and device
CN111835879A (en) * 2020-06-18 2020-10-27 烽火通信科技股份有限公司 Message processing method based on DHCP RELAY protocol and relay equipment

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102594668A (en) * 2012-02-03 2012-07-18 福建星网锐捷网络有限公司 Message forwarding method, device and exchange equipment
US20180227905A1 (en) * 2015-09-30 2018-08-09 Huawei Technologies Co., Ltd. Air interface resource determining method and apparatus and air interface resource indication method and apparatus
CN110351107A (en) * 2018-04-03 2019-10-18 华为技术有限公司 Configuring management method and device
CN108616431A (en) * 2018-04-20 2018-10-02 新华三技术有限公司 A kind of message processing method, device, equipment and machine readable storage medium
CN110855803A (en) * 2018-08-20 2020-02-28 北京神州泰岳软件股份有限公司 Data acquisition method and device
CN111835879A (en) * 2020-06-18 2020-10-27 烽火通信科技股份有限公司 Message processing method based on DHCP RELAY protocol and relay equipment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
张程烨: "一种基于SNMP协议的集群设备实时监控系统", 《电子测量技术》 *

Also Published As

Publication number Publication date
CN112887137B (en) 2022-05-24

Similar Documents

Publication Publication Date Title
US11283684B2 (en) Network slice deployment method and apparatus
JP7012836B2 (en) Network slice management method and equipment
US10375015B2 (en) Methods and system for allocating an IP address for an instance in a network function virtualization (NFV) system
US11750453B2 (en) Network slice configuration method, apparatus, and system
WO2018006381A1 (en) Network resource management method, apparatus and system
EP3595244A1 (en) Network slice management method, unit and system
US11575592B2 (en) Message processing method and apparatus, control-plane device, and computer storage medium
CN111865621B (en) Method and device for accessing gateway
CN111183614B (en) Interaction between 5G and non-5G management function entities
US10361970B2 (en) Automated instantiation of wireless virtual private networks
CN106375486B (en) A kind of system of cloud platform software definition DHCP service
CN105071965B (en) A kind of management system of the network equipment
WO2016150139A1 (en) Method and apparatus for establishing network service instance
CN108347472B (en) Configuration method of IP address, cloud server, cloud platform and readable storage medium
WO2020249080A1 (en) Virtual network function (vnf) deployment method and apparatus
CN111629059B (en) Cluster communication method, system, equipment and computer readable storage medium
CN113965938A (en) Slicing service system and slicing service processing method
CN112887137B (en) Method and device for realizing interface index consistency
US20220350637A1 (en) Virtual machine deployment method and related apparatus
WO2022183796A1 (en) Network service (ns) creation method and related apparatus
EP3258655B1 (en) Method and apparatus for determining nsd to be uploaded
CN113055211B (en) Method for instantiating network service and network function virtualization orchestrator
Wu et al. A cloud-ict convergence service architecture sdn/nfv powered
CN115550313A (en) Communication method and device of external equipment, electronic equipment and storage medium
CN115733743A (en) Network service deployment method, NFVO (network function virtualization) and NFV (network function virtualization) system

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