CN110830295B - Equipment management method and system - Google Patents

Equipment management method and system Download PDF

Info

Publication number
CN110830295B
CN110830295B CN201911065184.9A CN201911065184A CN110830295B CN 110830295 B CN110830295 B CN 110830295B CN 201911065184 A CN201911065184 A CN 201911065184A CN 110830295 B CN110830295 B CN 110830295B
Authority
CN
China
Prior art keywords
interface
layer device
information
virtual
core layer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201911065184.9A
Other languages
Chinese (zh)
Other versions
CN110830295A (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.)
Maipu Communication Technology Co Ltd
Original Assignee
Maipu Communication Technology 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 Maipu Communication Technology Co Ltd filed Critical Maipu Communication Technology Co Ltd
Priority to CN201911065184.9A priority Critical patent/CN110830295B/en
Publication of CN110830295A publication Critical patent/CN110830295A/en
Application granted granted Critical
Publication of CN110830295B publication Critical patent/CN110830295B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)

Abstract

The invention discloses a device management method and a system, which relate to the field of data communication.

Description

Equipment management method and system
Technical Field
The present invention relates to the field of data communications, and in particular, to a device management method and system.
Background
Through technical evolution and business development for many years, the network infrastructure of the current data center generally adopts a three-layer structure, which is divided into an access layer, a convergence layer and a core layer. In most cases, the data flow goes from the access layer to the aggregation layer to the core layer and then back again, the more layers not only the more devices used, but also the delay. Each hop in the network is costly and adds complexity. Due to the repetition and overlapping of these operations, the desired performance cannot be obtained, and the security is difficult to secure.
On the basis, the flat network architecture is developed. The flat network is changed into two layers from the original three layers, namely a core layer and an access layer two-stage architecture. Core layer equipment (such as gateway equipment and the like) is connected with the data center and the access layer equipment, and aggregation and high-speed data forwarding of each access layer equipment are executed. Generally, access stratum devices (such as switches and routers) are based on two layers, and in order to simplify network configuration and prevent attacks from the network, the access stratum devices do not need to configure IP addresses, so how to remotely manage the access stratum devices becomes a problem to be solved.
Disclosure of Invention
The invention provides a device management method and a device management system, which solve the problem that when an IP address is not configured on an access layer device in a flat network, the access layer device cannot be remotely managed.
In a first aspect, the present invention provides a device management method, including the following steps:
the access layer device periodically sends a Link Layer Discovery Protocol (LLDP) message to the core layer device to inform the interface information of each interface of the access layer device;
the core layer device acquires the interface information in the LLDP message and sequentially creates a one-to-one corresponding virtual interface for each interface of the access layer device;
And the core layer device manages the access layer device through the virtual interface.
The interface information includes a unique identifier of the interface and service configuration information of the interface.
The creating of the one-to-one virtual interface for each interface of the access layer device in sequence includes: and after the core layer device acquires the interface information in the LLDP message, creating a corresponding virtual interface according to the interface information of each interface in the LLDP message in sequence, wherein the interface information of each interface is consistent with the interface information of the corresponding virtual interface.
The core layer device manages the access layer device through the virtual interface, and the management comprises the following steps:
when the core layer device modifies the service configuration of any virtual interface, sending a first LLDP message including the updated interface information of the virtual interface to the access layer device; after the access layer device converts the updated interface information of the virtual interface in the first LLDP message into a configuration instruction of the interface corresponding to the virtual interface and successfully executes the configuration instruction, the access layer device updates the interface information of the interface corresponding to the virtual interface and sends a second LLDP message including the updated interface information of the interface corresponding to the virtual interface to the core layer device; and the core layer device modifies the interface information of the virtual interface according to the updated interface information of the interface corresponding to the virtual interface in the second LLDP message.
Further, the method of the invention also comprises the following steps: when the service configuration of any interface is modified on the access layer equipment, the access layer equipment updates the interface information of the interface and sends a third LLDP message including the updated interface information of the interface to the core layer equipment; and the core layer device modifies the interface information of the virtual interface corresponding to the interface according to the updated interface information of the interface in the third LLDP message.
In a second aspect, the present invention provides an apparatus management system, which specifically includes:
the access layer device is used for periodically sending a Link Layer Discovery Protocol (LLDP) message to the core layer device to inform the interface information of each interface of the access layer device;
the core layer device is used for acquiring the interface information in the LLDP message and sequentially creating a one-to-one corresponding virtual interface for each interface of the access layer device; and for managing the access stratum device through the virtual interface.
The interface information includes a unique identifier of the interface and service configuration information of the interface.
The core layer device is specifically configured to, after obtaining the interface information in the LLDP message, sequentially create a corresponding virtual interface according to the interface information of each interface in the LLDP message, where the interface information of each interface is consistent with the interface information of the corresponding virtual interface.
In one possible design, the core layer device is specifically configured to send a first LLDP packet including updated interface information of any virtual interface to the access layer device when modifying the service configuration of the virtual interface; the interface information modification unit is used for receiving a second LLDP message sent by the access layer equipment and modifying the interface information of the virtual interface according to the updated interface information of the interface corresponding to the virtual interface in the second LLDP message; the access layer device is specifically configured to, after receiving the first LLDP message sent by the core layer device, convert the updated interface information of the virtual interface in the first LLDP message into a configuration instruction of the interface corresponding to the virtual interface and execute the configuration instruction successfully, update the interface information of the interface corresponding to the virtual interface, and send the second LLDP message including the updated interface information of the interface corresponding to the virtual interface to the core layer device.
In another possible design, the access layer device is specifically configured to, when modifying the service configuration of any interface, update the interface information of the interface, and send a third LLDP packet including the interface information after the interface update to the core layer device; the core layer device is specifically configured to receive the third LLDP message, and modify the interface information of the virtual interface corresponding to the interface according to the updated interface information of the interface in the third LLDP message.
In summary, the virtual interfaces are created on the core layer device in the flat network and respectively correspond to each interface of the access layer device one to one, and it is ensured that the interface information of each interface of the access layer device and the interface information of the virtual interface corresponding to the core layer device are updated synchronously, so that the core layer device can manage the access layer device through the virtual interfaces, and the network configuration of the flat network is simplified.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a flowchart illustrating a device management method according to an embodiment of the present invention;
fig. 2 is a schematic diagram illustrating an application scenario provided by an embodiment of the present invention;
fig. 3 is a schematic diagram illustrating a device management system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
The following are detailed descriptions of the respective embodiments.
Example one
An embodiment of the present invention provides an apparatus management method, a processing flow chart of which is shown in fig. 1, and the method includes the following steps:
step S101, the access layer device periodically sends a link layer discovery protocol LLDP message to the core layer device to notify the interface information of each interface of the access layer device.
For example, in the application scenario shown in fig. 2, the interface of the core layer device a is connected to a plurality of access layer devices, and here, the access layer device a1 is taken as an example for description. Assume that access stratum device a1 has 3 interfaces in common, which are: if11, if12, if 13. The interface if11 of the access layer device a1 is connected to the interface if01 of the core layer device a, and the interfaces if12 and if13 of the access layer device a1 are connected to the user 1 and the user 2, respectively. The access layer device a1 periodically sends a Link Layer Discovery Protocol (LLDP) message to the core layer device a to notify the interface information of each interface of the access layer device a1, where the LLDP message is a multicast message. The interface information of each interface comprises the unique identification of the interface and the service configuration information of the interface. Optionally, the interface information of each interface may adopt a plurality of Type/Length/Value (TLV) formats to respectively load the unique identifier of the interface and the configuration information of different services of the interface. The interface information of each interface may include configuration information of one or more services, as shown below, when the configuration information of multiple services is included, the following manner may be used, one by one, where N is a positive integer:
The first TLV:
type value: the unique identification code used for representing the interface can be customized
Length value: for indicating the length of Value, i.e. the length of the unique identification of the interface
Value: unique identifier for representing an interface
Second TLV:
type value: the code used to represent service 1 can be customized
Length value: for indicating the length of Value, i.e. the length of configuration information of service 1 corresponding to the interface
Value: configuration information for indicating service 1 corresponding to the interface
……
N +1 th TLV:
type value: the code used to represent service N can be customized
Length value: for indicating the length of Value, i.e. the length of configuration information of service N corresponding to the interface
Value: the interface information of the plurality of interfaces for indicating the configuration information of the service N corresponding to the interface may be sequentially arranged in a sequential manner. Taking the application scenario shown in fig. 2 as an example, the unique identifiers of the interfaces of the 3 interfaces if11, if12, and if13 of the access layer device a1 are 1, 2, and 3, respectively. An interface if11 of the access layer device a1 is configured in a Trunk mode to allow the messages of the VLANs 10 and 20 to pass through; the interface if12 is configured in Access mode and is divided into VLAN 10; interface if13 is configured in Access mode and is divided in VLAN 20. VLAN10 and VLAN20 correspond to VLAN ids 10 and 20, respectively. Illustratively, the interface information of all interfaces of the access stratum device a1 is shown in table 1.
TABLE 1
Unique identification of an interface Mode(s) VLAN identification
1 Trunk 10、20
2 Access 10
3 Access 20
Assuming that the unique identifier of the customized interface is encoded to be 10, the traffic code of the VLAN is 11, and the interface information of the interfaces if11, if12 and if13 can be represented in the following TLV format:
Type:10
Length:2
Value:1
Type:11
Length:5
Value:Trunk:10；20
Type:10
Length:2
Value:2
Type:11
Length:3
Value:Access:10
Type:10
Length:2
Value:3
Type:11
Length:3
Value:Access:20
it should be noted that, no matter the interface state of the access layer device is UP or DOWN, the LLDP multicast packet periodically sent by the access layer device to the core layer device should include interface information of all interfaces of the access layer device.
Step S102, the core layer device obtains the interface information in the LLDP message, and creates a one-to-one virtual interface for each interface of the access layer device in sequence.
After the core layer device acquires the interface information in the LLDP message, a corresponding virtual interface is created in sequence according to the interface information of each interface in the LLDP message, and the interface information of each interface is consistent with the interface information of the corresponding virtual interface.
For example, as shown in fig. 2, after receiving an LLDP message sent by the access layer device a1, the core layer device a acquires interface information in the LLDP message, and creates one-to-one virtual interfaces vif11, vif12, and vif13 according to the interface information of the interfaces if11, if12, and if13 in the LLDP message, where the interface information of the virtual interfaces vif11, vif12, and vif13 is respectively consistent with the interface information of the interfaces if11, if12, and if13, as shown in table 2.
TABLE 2
Figure BDA0002263669510000071
Figure BDA0002263669510000081
After receiving the LLDP message periodically sent by the access layer device a1, the subsequent core layer device a sequentially determines whether the interface information of the interfaces if11, if12, if13 is the same as the interface information of the corresponding virtual interfaces vif11, vif12, vif13 according to the interface information in the LLDP message, and if there is a difference, the core layer device a updates the interface information of the corresponding virtual interfaces to ensure that the interface information of the virtual interfaces vif11, vif12, vif13 is consistent with the interface information of the interfaces if11, if12, if 13.
Step S103, the core layer device manages the access layer device through the virtual interface.
In the embodiment of the present invention, the core layer device may obtain the interface information of the interface corresponding to the virtual interface on the access layer device by checking the interface information of the virtual interface.
Further, when the core layer device modifies the service configuration of any virtual interface, the core layer device sends a first LLDP message including the interface information updated by the virtual interface to the access layer device, where the first LLDP message is a unicast message. Optionally, the interface information after the virtual interface is updated in the first LLDP message may adopt a plurality of TLV formats to respectively load the unique identifier of the virtual interface and the configuration information of the service after the virtual interface is updated. For example, the following methods can be used:
The first TLV:
type value: unique identification code for representing virtual interfaces
Length value: length for indicating Value, i.e. length of unique identification of virtual interface
Value: unique identification for representing virtual interfaces
Second TLV:
type value: coding for representing services
Length value: for indicating the total length of Subtype and Value
Subtype value: 1 represents an increase; 2 represents deletion; 3 denotes a modification
Value: the change condition is used for representing the configuration information of the service corresponding to the virtual interface, wherein when the Subtype is 1 or 2, the corresponding Value represents the configuration information of the service addition or deletion; when Subtype is 3, the corresponding Value can adopt a Value1: Value2 mode to indicate that the configuration information of the service is changed from a Value1 Value to a Value2 Value. It should be noted that the unique identifier code of the interface defined by the access layer device and the core layer device is the same as the unique identifier code of the virtual interface, and the codes of the services need to be guaranteed to be uniform at both ends of the access layer device and the core layer device.
And after receiving the LLDP message, the access layer equipment converts the interface information updated by the virtual interface into an adding, deleting or modifying configuration instruction of the related service of the corresponding interface and executes the adding, deleting or modifying configuration instruction. If the execution is successful, the access layer device updates the interface information of the interface corresponding to the virtual interface, and sends a second LLDP message including the updated interface information of the interface corresponding to the virtual interface to the core layer device, wherein the second LLDP message is a multicast message. The interface information after the interface update corresponding to the virtual interface in the second LLDP message may also be loaded in the TLV format as in the first LLDP message, which is not described herein again. And after receiving the second LLDP message, the core layer device modifies the interface information of the virtual interface according to the updated interface information of the interface corresponding to the virtual interface in the second LLDP message.
For example, after the VLAN identifier of the virtual interface vif12 is modified from 10 to 20 on the core layer device a, the core layer device a immediately sends a first LLDP message to the access layer device a1 to notify the virtual interface vif12 of the updated interface information, where the first LLDP message is a unicast message. The updated interface information of the virtual interface vif12 can be represented in the following TLV format:
Type:10
Length:2
Value:2
Type:11
Length:7
Subtype:3
Value:10:20
after receiving the first LLDP packet, the access layer device a1 obtains the unique identifier of the virtual interface vif12 and the configuration information after VLAN traffic update in the TLV format, converts the unique identifier into a modification configuration instruction for changing the VLAN identifier of the interface if12 from 10 to 20, and executes the modification configuration instruction. If the execution is successful, the access layer device a1 updates the interface information of the interface if12, and sends a second LLDP message including the updated interface information of the interface if12 to the core layer device a, where the second LLDP message is a multicast message. The updated interface information of the interface if12 in the second LLDP message may also be represented in the following TLV format:
Type:10
Length:2
Value:2
Type:11
Length:7
Subtype:3
Value:10:20
after receiving the second LLDP message, the core layer device a modifies the interface information of the corresponding virtual interface vif12 according to the updated interface information of the interface if12 in the second LLDP message.
As another embodiment of the present invention, when modifying the service configuration of any interface on the access layer device, the access layer device updates the interface information of the interface, and sends a third LLDP packet including the interface information after the interface update to the core layer device; and the core layer device modifies the interface information of the virtual interface corresponding to the interface according to the updated interface information of the interface in the third LLDP message.
For example, after the access layer device a1 issues a configuration command to change the VLAN identifier of the interface if12 from 10 to 20, the access layer device a1 updates the interface information of the interface if12, and immediately sends a third LLDP message including the interface information updated by the interface if12 to the core layer device a, where the third LLDP message is a multicast message. After receiving the third LLDP message, the core layer device a obtains the updated interface information of the interface if12, finds the corresponding virtual interface vif12 according to the unique identifier of the interface if12, and modifies the VLAN identifier in the interface information of the virtual interface vif 12.
The invention establishes the virtual interfaces on the core layer equipment in the flat network to respectively correspond to each interface of the access layer equipment one by one, and ensures that the interface information of each interface of the access layer equipment and the interface information of the virtual interface corresponding to the core layer equipment are synchronously updated, so that the core layer equipment can manage the access layer equipment through the virtual interfaces, and the network configuration of the flat network is simplified.
Example two
An embodiment of the present invention provides an apparatus management system 30, a schematic diagram of which is shown in fig. 3, including:
the access layer device 301 is configured to periodically send a link layer discovery protocol LLDP message to the core layer device 302 to notify interface information of each interface of the access layer device 301;
The core layer device 302 is configured to acquire interface information in the LLDP message, and sequentially create a one-to-one virtual interface for each interface of the access layer device 301; and for managing the access stratum device 301 through the virtual interface.
The interface information includes a unique identifier of the interface and service configuration information of the interface.
The core layer device 302 is specifically configured to, after obtaining the interface information in the LLDP message, sequentially create a corresponding virtual interface according to the interface information of each interface in the LLDP message, where the interface information of each interface is consistent with the interface information of the corresponding virtual interface.
As an embodiment of the present invention, the core layer device 302 is specifically configured to, when modifying a service configuration of any virtual interface, send a first LLDP packet including interface information updated by the virtual interface to the access layer device 301; and is configured to receive a second LLDP packet sent by the access layer device 301, and modify the interface information of the virtual interface according to the updated interface information of the interface corresponding to the virtual interface in the second LLDP packet; the access layer device 301 is specifically configured to, after receiving the first LLDP message sent by the core layer device 302, convert the interface information of the virtual interface updated in the first LLDP message into a configuration instruction of the interface corresponding to the virtual interface and execute the configuration instruction successfully, update the interface information of the interface corresponding to the virtual interface, and send the second LLDP message including the interface information of the virtual interface updated to the core layer device 302.
As another embodiment of the present invention, the access layer device 301 is specifically configured to, when modifying the service configuration of any interface, update the interface information of the interface, and send a third LLDP message including the interface information after the interface update to the core layer device 302; the core layer device 302 is specifically configured to receive the third LLDP message, and modify the interface information of the virtual interface corresponding to the interface according to the updated interface information of the interface in the third LLDP message.
The invention establishes the virtual interfaces on the core layer equipment in the flat network to respectively correspond to each interface of the access layer equipment one by one, and ensures that the interface information of each interface of the access layer equipment and the interface information of the virtual interface corresponding to the core layer equipment are synchronously updated, so that the core layer equipment can manage the access layer equipment through the virtual interfaces, and the network configuration of the flat network is simplified.
All parts of the specification are described in a progressive mode, the same and similar parts of all embodiments can be referred to each other, and each embodiment is mainly introduced to be different from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, and reference may be made to the description of the method embodiments for relevant points.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (10)

1. A method for device management, the method comprising:
the access layer device periodically sends a Link Layer Discovery Protocol (LLDP) message to the core layer device to inform the interface information of each interface of the access layer device;
the core layer device acquires the interface information in the LLDP message and sequentially creates a one-to-one corresponding virtual interface for each interface of the access layer device;
and the core layer device manages the access layer device through the virtual interface.
2. The method of claim 1, wherein the interface information comprises a unique identification of the interface and service configuration information for the interface.
3. The method of claim 1, wherein the creating a one-to-one virtual interface for each interface of the access stratum device in turn comprises:
And after the core layer device acquires the interface information in the LLDP message, creating a corresponding virtual interface according to the interface information of each interface in the LLDP message in sequence, wherein the interface information of each interface is consistent with the interface information of the corresponding virtual interface.
4. The method of any of claims 1-3, wherein the core layer device managing the access layer device through the virtual interface comprises:
when the core layer device modifies the service configuration of any virtual interface, sending a first LLDP message including the updated interface information of the virtual interface to the access layer device; after the access layer device converts the updated interface information of the virtual interface in the first LLDP message into a configuration instruction of the interface corresponding to the virtual interface and successfully executes the configuration instruction, the access layer device updates the interface information of the interface corresponding to the virtual interface and sends a second LLDP message including the updated interface information of the interface corresponding to the virtual interface to the core layer device; and the core layer device modifies the interface information of the virtual interface according to the updated interface information of the interface corresponding to the virtual interface in the second LLDP message.
5. The method of any one of claims 1-3, further comprising:
when the service configuration of any interface is modified on the access layer equipment, the access layer equipment updates the interface information of the interface and sends a third LLDP message including the updated interface information of the interface to the core layer equipment; and the core layer device modifies the interface information of the virtual interface corresponding to the interface according to the updated interface information of the interface in the third LLDP message.
6. A device management system, the system comprising:
the access layer device is used for periodically sending a Link Layer Discovery Protocol (LLDP) message to the core layer device to inform the interface information of each interface of the access layer device;
the core layer device is used for acquiring the interface information in the LLDP message and sequentially creating a one-to-one corresponding virtual interface for each interface of the access layer device; and for managing the access stratum device through the virtual interface.
7. The system of claim 6, wherein the interface information comprises a unique identification of the interface and service configuration information for the interface.
8. The system of claim 6, wherein the core layer device is specific to,
and after the interface information in the LLDP message is acquired, creating a corresponding virtual interface according to the interface information of each interface in the LLDP message in sequence, wherein the interface information of each interface is consistent with the interface information of the corresponding virtual interface.
9. The system of any one of claims 6-8,
the core layer device is specifically configured to send a first LLDP packet including updated interface information of any virtual interface to the access layer device when modifying the service configuration of the virtual interface; the interface information of the virtual interface is modified according to the updated interface information of the interface corresponding to the virtual interface in the second LLDP message;
the access layer device is specifically configured to, after receiving the first LLDP message sent by the core layer device, convert the interface information of the virtual interface updated in the first LLDP message into a configuration instruction of the interface corresponding to the virtual interface and execute the configuration instruction successfully, update the interface information of the interface corresponding to the virtual interface, and send the second LLDP message including the interface information of the virtual interface updated to the core layer device.
10. The system of any one of claims 6-8,
the access layer device is specifically configured to, when modifying the service configuration of any interface, update the interface information of the interface, and send a third LLDP packet including the interface information updated by the interface to the core layer device;
the core layer device is specifically configured to receive the third LLDP message, and modify the interface information of the virtual interface corresponding to the interface according to the updated interface information of the interface in the third LLDP message.
CN201911065184.9A 2019-11-08 2019-11-08 Equipment management method and system Active CN110830295B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911065184.9A CN110830295B (en) 2019-11-08 2019-11-08 Equipment management method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911065184.9A CN110830295B (en) 2019-11-08 2019-11-08 Equipment management method and system

Publications (2)

Publication Number Publication Date
CN110830295A CN110830295A (en) 2020-02-21
CN110830295B true CN110830295B (en) 2022-07-29

Family

ID=69552647

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911065184.9A Active CN110830295B (en) 2019-11-08 2019-11-08 Equipment management method and system

Country Status (1)

Country Link
CN (1) CN110830295B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113726822B (en) * 2021-11-02 2022-02-11 深圳大学 General block chain system of heterogeneous equipment of industry internet

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1728702A (en) * 2004-07-29 2006-02-01 国家数字交换系统工程技术研究中心 Method for separating control plane of router from hardware of data plane
CN105337751A (en) * 2014-07-30 2016-02-17 杭州迪普科技有限公司 ACL configuration method and device
WO2016122934A1 (en) * 2015-01-30 2016-08-04 Hewlett-Packard Development Company, L.P. Multi-chassis link aggregation (lag) switches
CN106572475A (en) * 2015-10-10 2017-04-19 电信科学技术研究院 Access node management method, access network management entity, equipment and access nodes
CN107612702A (en) * 2016-07-12 2018-01-19 中兴通讯股份有限公司 A kind of method for configuring routers and device
CN108632091A (en) * 2018-05-09 2018-10-09 烽火通信科技股份有限公司 The service of connection devices is adaptively adapted to the implementation method of encapsulation in a kind of DCN networks

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1728702A (en) * 2004-07-29 2006-02-01 国家数字交换系统工程技术研究中心 Method for separating control plane of router from hardware of data plane
CN105337751A (en) * 2014-07-30 2016-02-17 杭州迪普科技有限公司 ACL configuration method and device
WO2016122934A1 (en) * 2015-01-30 2016-08-04 Hewlett-Packard Development Company, L.P. Multi-chassis link aggregation (lag) switches
CN106572475A (en) * 2015-10-10 2017-04-19 电信科学技术研究院 Access node management method, access network management entity, equipment and access nodes
CN107612702A (en) * 2016-07-12 2018-01-19 中兴通讯股份有限公司 A kind of method for configuring routers and device
CN108632091A (en) * 2018-05-09 2018-10-09 烽火通信科技股份有限公司 The service of connection devices is adaptively adapted to the implementation method of encapsulation in a kind of DCN networks

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Link-Layer Event Notification for Detecting Network Attachments";S.Krishnan.etc;《https://datatracker.ietf.org/doc/html/rfc4957#page-12》;20070831;全文 *
"类Kubernetes扁平化网络模型的研究与实现";李文龙，沈炜，李文丽;《工业控制计算机》;20170425;全文 *

Also Published As

Publication number Publication date
CN110830295A (en) 2020-02-21

Similar Documents

Publication Publication Date Title
US9622276B2 (en) Method and device for determining to establish multi-protocol label switching traffic engineering tunnel
EP3208977B1 (en) Data forwarding method, device and system in software-defined networking
EP2378720B1 (en) Extranet networking method, system and device for multicast virtual private network
EP2843906B1 (en) Method, apparatus, and system for data transmission
EP2701342A1 (en) Method and system for implementing elastic network interface and interconnection
CN109660441B (en) Method and device for multicast replication in Overlay network
EP3267721B1 (en) Air-interface protocol stack configuration method, and data transmission method and device
US10855576B2 (en) Information transmission method and device
CN102576353A (en) Systems and methods for fractional routing redundancy
WO2023011217A1 (en) Communication method and apparatus
WO2018068588A1 (en) Method and software-defined networking (sdn) controller for providing multicast service
WO2023000936A1 (en) Data processing method, function device and readable storage medium
CN103944836A (en) Multicast traffic forwarding on pruned interface
CN108632147A (en) Message multicast processing method and device
CN110830295B (en) Equipment management method and system
CN110493733A (en) A kind of Mesh network system based on Bluetooth Low Energy mobile device
CN109120657B (en) Service configuration method and node
CN112312481B (en) Communication method and system for MEC and multi-operator core network
CN107786441B (en) Communication method, OpenFlow switch and communication system
WO2020147784A1 (en) Message decapsulation method and device, message encapsulation method and device, electronic device, and storage medium
CN102932186B (en) Trunking system and method of removing loop circuits
CN109600837B (en) System information generation method and device
CN112511403A (en) Virtual local area network communication method, equipment and storage medium
CN104753705B (en) Generation method, equipment and the system in the domains DS
WO2017084411A1 (en) Software-defined network management method and communication 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
CP02 Change in the address of a patent holder

Address after: 610041 nine Xing Xing Road 16, hi tech Zone, Sichuan, Chengdu

Patentee after: MAIPU COMMUNICATION TECHNOLOGY Co.,Ltd.

Address before: 610041 15-24 floor, 1 1 Tianfu street, Chengdu high tech Zone, Sichuan

Patentee before: MAIPU COMMUNICATION TECHNOLOGY Co.,Ltd.

CP02 Change in the address of a patent holder