CN112671711A - Network equipment management method and device - Google Patents
Network equipment management method and device Download PDFInfo
- Publication number
- CN112671711A CN112671711A CN202011350342.8A CN202011350342A CN112671711A CN 112671711 A CN112671711 A CN 112671711A CN 202011350342 A CN202011350342 A CN 202011350342A CN 112671711 A CN112671711 A CN 112671711A
- Authority
- CN
- China
- Prior art keywords
- connection
- openflow
- blacklist
- newly
- built
- 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
Links
Images
Abstract
The present specification provides a method and an apparatus for managing a network device, where the method includes: determining whether the newly-built openflow connection is an openflow connection in a blacklist; if the newly-built openflow connection is not in the blacklist, acquiring connection information of openflow established by managed network equipment in a managed connection pool; judging whether the newly-built openflow connection exists in the nano-tube connection pool or not, and if not, adding the newly-built openflow connection into an unknown connection pool; and judging whether the newly-built openflow connection conforms to a rule for pulling in a blacklist, if so, adding the newly-built openflow connection to the blacklist, and disconnecting the newly-built openflow connection. The method disclosed by the invention provides a management mechanism for automatically pulling black openflow connections, and when the black-pulling rules are met, the connections are automatically pulled into a blacklist, so that the connection and processing resources of a controller are not occupied.
Description
Technical Field
The present disclosure relates to the field of network device management technologies, and in particular, to a method and an apparatus for managing a network device.
Background
SDN (Software Defined Network ) is a novel Network innovation architecture, and is an implementation manner of Network virtualization, and a core technology of the SDN is to separate a control layer and a forwarding layer of a Network device, such as a switch or a router, through a unified southbound interface Protocol, such as OpenFlow and Network Configuration Protocol (Network Configuration Protocol), so as to implement control layer intelligent management and operation and maintenance of Network resources and Network services.
Between the SDN controller and the network device, or authentication is not performed, that is, any network device supporting the OpenFlow protocol can establish connection with the SDN controller; or digital certificate authentication, such as SSL (Secure Sockets Layer) certificate authentication, but restricts the connection of other vendor network devices or remote network devices. Meanwhile, the SDN controller does not intelligently manage multiple connections of the same network device.
The above manner results in poor security of the SDN controller, and an external illegal network device may acquire the relevant configuration of the entire SDN network. Meanwhile, unknown openflow can occupy controller resources connected by normal openflow.
Disclosure of Invention
In order to overcome the problems in the related art, the present specification provides a method and an apparatus for managing a network device.
According to a first aspect of embodiments herein, there is provided a method for managing a network device, the method including:
if the newly-built openflow connection is monitored, obtaining a blacklist of the openflow connection;
determining whether the newly-built openflow connection is an openflow connection in a blacklist;
if the newly-built openflow connection is not in the blacklist, acquiring connection information of openflow established by managed network equipment in a managed connection pool;
judging whether the newly-built openflow connection exists in the nano-tube connection pool or not, and if not, adding the newly-built openflow connection into an unknown connection pool;
and judging whether the newly-built openflow connection conforms to a rule for pulling in a blacklist, if so, adding the newly-built openflow connection to the blacklist, and disconnecting the newly-built openflow connection.
Optionally, the determining whether the newly-built openflow connection conforms to a rule of pulling into a blacklist includes:
and judging whether the connection times of the current newly-built openflow connection in a preset time length is larger than a first preset threshold, and if so, determining that the newly-built openflow connection conforms to a rule of pulling in a blacklist.
Optionally, the blacklist is periodically acquired, whether openflow connections in the blacklist conform to activation rules is judged, if yes, the openflow connections conforming to the activation rules are moved into the nanotube connection pool, and the openflow connections conforming to the activation rules in the blacklist are deleted.
Optionally, the determining whether openflow connection in the blacklist meets an activation rule includes:
and judging whether the connection times of the openflow connection to be judged currently are less than or equal to a second preset threshold value between the time before the preset duration and the current time in the blacklist, and if so, adding the openflow connection to be judged currently into a corresponding connection pool according to the connection pool type of the openflow connection recorded in the blacklist.
Optionally, if the openflow connection in the blacklist does not meet the activation rule, determining whether the openflow connection in the blacklist meets the aging rule, and if the openflow connection in the blacklist meets the aging rule, deleting the openflow connection meeting the aging rule in the blacklist.
According to a second aspect of embodiments herein, there is provided an apparatus for managing a network device, the apparatus including: the system comprises a monitoring module, an acquisition module, a judgment module and a resource pool module; the resource pool module comprises a blacklist, a nanotube connection pool and an unknown connection pool;
the monitoring module is used for prompting the acquisition module to acquire a blacklist of openflow connections if the new openflow connections are monitored;
the judging module is used for determining whether the newly-built openflow connection is an openflow connection in a blacklist;
the judging module is further configured to prompt the obtaining module to obtain connection information of openflow established by managed network devices in the managed connection pool if it is determined that the newly-built openflow connection is not in the blacklist;
the judging module is also used for judging whether the newly-built openflow connection exists in the nanotube connecting pool or not, and if not, adding the newly-built openflow connection into an unknown connecting pool;
the judging module is further used for judging whether the newly-built openflow connection conforms to a rule for pulling in a blacklist, if so, adding the newly-built openflow connection to the blacklist, and disconnecting the newly-built openflow connection.
Optionally, the determining module is specifically configured to determine whether a connection frequency of the currently newly-built openflow connection within a preset time duration is greater than a first preset threshold, and if so, determine that the newly-built openflow connection conforms to a rule of pulling into a blacklist.
Optionally, the obtaining module is further configured to periodically obtain the blacklist, and the determining module is further configured to determine whether openflow connections in the blacklist meet an activation rule, if yes, move openflow connections meeting the activation rule into the nanotube connection pool, and delete openflow connections meeting the activation rule in the blacklist.
Optionally, the determining module is specifically configured to determine whether a connection frequency of the openflow connection to be currently determined is less than or equal to a second preset threshold between a time before a preset duration and a current time in the blacklist, and if the connection frequency of the openflow connection to be currently determined is less than or equal to the second preset threshold, add the openflow connection to be currently determined to a corresponding connection pool according to a connection pool type of the openflow connection recorded in the blacklist.
Optionally, the determining module is specifically configured to determine whether openflow connections in the blacklist conform to the aging rule if the openflow connections in the blacklist do not conform to the activation rule, and delete openflow connections that conform to the aging rule in the blacklist if the openflow connections in the blacklist conform to the aging rule.
The technical scheme provided by the embodiment of the specification can have the following beneficial effects: in the management method of the network device provided by the disclosure, a management mechanism for automatically pulling black openflow connections is provided, and when a black pulling rule is met, the connections are automatically pulled into a blacklist, and connection and processing resources of a controller are not occupied any more.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present specification and together with the description, serve to explain the principles of the specification.
FIG. 1 is a schematic flow diagram of a management method provided by the present disclosure;
FIG. 2 is a schematic flow chart diagram of a management method according to another embodiment of the disclosure;
FIG. 3 is a schematic structural diagram of a management device provided by the present disclosure;
fig. 4 is a schematic structural diagram of a controller provided by the present disclosure.
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 specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
Example one
The utility model discloses a management method of network equipment, is applied to the controller, can establish the connection through openflow agreement between this controller and the network equipment.
In an alternative embodiment, for a network device that establishes a connection with a controller, the controller will add the established openflow connection to the nanotube connection pool. The nanotube connection pool can be understood as being used for recording openflow connection established with the controller, and also recording the establishment time of the openflow connection and the number of times of initiating connection to the controller within a preset time length of the connection establishment.
Fig. 1 is a schematic flowchart of a management method of a network device provided by the present disclosure, and as shown in fig. 1, the method includes:
and step 101, if the controller monitors the newly-built openflow connection, acquiring a blacklist of the openflow connection.
The openflow connection newly established here may be an openflow connection successfully established with the controller, or may be an openflow connection that initiates an openflow connection request only to the controller.
And 102, determining whether the newly-built openflow connection is an openflow connection in a blacklist.
The openflow connection blacklist generally records openflow connections, the connection times of which with the controller exceed a preset threshold value within a certain time. In particular, the devices in the black list may be of the following types:
illegal devices may acquire relevant information on the controller by frequently establishing connection with the controller; or another possible situation is a legal network device, which is disconnected and reconnected after the connection with the controller is established due to network failure or device self-failure, and the connection with the controller is frequently established within a certain time period due to the repetition of the disconnection and reconnection. For such a connection, the controller may add it to the blacklist; or there may be a case where the network device has not previously established a connection with the controller, and does not exist in the nanotube connection pool, but is added to the blacklist for some other reason, as will be described in detail below.
However, for the newly-built connection, whether the openflow connection meets the condition of blacklisting cannot be judged, so that the newly-built openflow connection can be added into the non-nanotube connection pool. The non-managed connection pool is used for storing the connection which can not judge whether the newly-built openflow connection is established for managed network equipment or not, or whether the newly-built openflow connection is established for illegal network equipment and the controller.
Specifically, the controller may first determine whether the newly created openflow connection exists in the blacklist, and if so, disconnect the openflow connection.
And judging whether the connection frequency of the current newly-built openflow connection in a preset time length is larger than a preset threshold value, and if so, determining that the newly-built openflow connection conforms to a rule of pulling in a blacklist. For example, it may be determined whether the openflow connection is connected more than 10 times within 10 minutes, and if so, the openflow connection is added to the blacklist.
In addition, if the newly-built openflow connection exists in the blacklist, the number of the openflow connection is increased by one, and the time for establishing the openflow connection is recorded.
Of course, the rules of the black list may be set or changed according to actual situations.
And 103, if the newly-built openflow connection is not in the blacklist, acquiring connection information of openflow established by managed network equipment in the managed connection pool.
And 104, judging whether the newly-built openflow connection exists in the nano-tube connection pool or not, and if not, adding the newly-built openflow connection to an unknown connection pool.
And if the newly-built openflow connection is not in the blacklist, determining whether the newly-built openflow connection is the connection established by the managed network equipment, if the newly-built openflow connection exists in the managed connection pool, adding the establishing time of the newly-built openflow connection, and adding one to the connection times.
If the newly-built connection is not in the managed connection pool or the blacklist, whether the network device is a legal device or not can not be judged, and therefore the network device is added into the unknown connection pool.
And 105, judging whether the newly-built openflow connection conforms to a rule of pulling in a blacklist, if so, adding the newly-built openflow connection to the blacklist, and disconnecting the newly-built openflow connection.
Whether the newly-built openflow connection is currently in a blacklist or an unknown connection pool or a managed connection pool, the state of the openflow connection is judged, whether the openflow connection accords with a blacklist pulling-in rule or not is judged, specifically, the connection frequency within a preset time length is judged to be larger than a first preset threshold, and if the connection frequency is larger than the first preset threshold, the newly-built openflow connection is determined to accord with the blacklist pulling-in rule.
Optionally, when the newly-created openflow connection is added to the blacklist, the type of the connection pool in which the openflow connection is located is labeled, for example, the openflow connection is a nanotube connection or an unknown connection. And simultaneously emptying the connection time and connection times in the corresponding connection pool.
In the management method of the network device provided by the disclosure, a management mechanism for automatically pulling black openflow connections is provided, and when a black pulling rule is met, the connections are automatically pulled into a blacklist, and connection and processing resources of a controller are not occupied any more.
Example two
It is possible for legitimate devices to be on the blacklist for which activation is required.
Therefore, on the basis of the foregoing embodiment, in this implementation, an activation method for a valid device in a blacklist is further provided, and the method further includes:
step 201, obtaining a blacklist periodically, judging whether openflow connections in the blacklist accord with activation rules, if so, moving the openflow connections which accord with the activation rules into an nanotube connection pool, and deleting the openflow connections which accord with the activation rules in the blacklist.
The period for obtaining the blacklist and the activation rule can be set according to actual conditions.
There may be multiple connections in the blacklist, which may be processed sequentially in order. In this embodiment, for an example of one of the connections, the connection becomes an openflow connection to be currently determined.
In one implementation, the determining whether openflow connections in the blacklist conform to activation rules includes:
and judging whether the connection times of the openflow connection to be judged currently are less than or equal to a second preset threshold value between the time before the preset duration and the current time in the blacklist, and if so, adding the openflow connection to be judged currently into a corresponding connection pool according to the connection pool type of the openflow connection recorded in the blacklist.
For example, the current time is 11:30, the preset time duration is 10 minutes, and if the openflow to be currently determined is connected to 11: 20 to 11:30, the number of times of connection establishment with the controller is less than or equal to a second preset threshold, for example, less than 1 time, which indicates that the network device does not frequently attack the controller. Therefore, the openflow connection to be currently judged can be added into the corresponding connection pool according to the type of the connection pool corresponding to the openflow in the blacklist. In particular, a schematic diagram shown in fig. 2 may be provided as the present disclosure, in which the activation and aging processes of the blacklist are given.
Specifically, if the type of the connection pool corresponding to the openflow connection is a nano-tube connection pool, it is indicated that the openflow connection is added to the blacklist from the nano-tube connection pool before; if the type of the connection pool corresponding to the openflow connection is the unknown connection pool, the openflow connection is added to the blacklist from the unknown connection pool before the openflow connection is established.
Therefore, at this time, the openflow connection can be returned to the original resource pool according to the type of the nanotube connection pool.
In an optional implementation manner, if the openflow connections in the blacklist do not meet the activation rule, it is determined whether the openflow connections in the blacklist meet the aging rule, and if the openflow connections in the blacklist meet the aging rule, the openflow connections in the blacklist that meet the aging rule are deleted.
Specifically, the aging rule may be set according to an actual requirement, for example, the connection frequency of the openflow connection within 1 day may be set to be 0, and if it is determined that the openflow connection meets the aging rule, the openflow connection is deleted.
According to the method, a management mode for activating openflow connection is provided, when an activation mechanism is met, the openflow connection is automatically added back to an original connection pool, and timely processing after connection is recovered to be normal is guaranteed. Meanwhile, an aging mechanism of the blacklist is provided, so that the phenomenon that the connection processing performance is influenced due to overlong blacklist is prevented.
In addition, for the connection in the unknown connection pool, an interface can be provided in the disclosure for a user to select, for example, a page is provided to show the connection in the unknown connection pool, the user selects which connections to manage and selects a management mode, the connection needing management is removed from the unknown connection pool, the connection time and the connection times are cleared, and the connection needing management is added to the management connection pool; and removing the connection needing to be pulled into the blacklist from the unknown connection pool, emptying the connection time and connection times, and adding the connection into the blacklist.
Implementation III
Fig. 3 is a schematic structural diagram of the management apparatus provided in the present disclosure, and as shown in fig. 3, the apparatus includes:
a monitoring module 301, an obtaining module 302, a judging module 303 and a resource pool module 304; the resource pool module comprises a blacklist, a nanotube connection pool and an unknown connection pool;
a monitoring module 301, configured to prompt the obtaining module 302 to obtain a blacklist of openflow connections if a newly-built openflow connection is monitored;
the judging module 303 is configured to determine whether the newly-built openflow connection is an openflow connection in a blacklist;
the judging module 303 is further configured to, if it is determined that the newly established openflow connection is not in the blacklist, prompt the obtaining module to obtain connection information of openflow established by managed network devices in the managed connection pool;
the judging module 303 is further configured to judge whether the newly-built openflow connection exists in the nanotube connecting pool, and if not, add the newly-built openflow connection to an unknown connecting pool;
the determining module 303 is further configured to determine whether the newly-built openflow connection conforms to a rule for pulling in a blacklist, and if so, add the newly-built openflow connection to the blacklist, and disconnect the newly-built openflow connection.
Optionally, the determining module 303 is specifically configured to determine whether the connection frequency of the currently newly-built openflow connection within a preset time duration is greater than a first preset threshold, and if so, determine that the newly-built openflow connection conforms to a rule of pulling into a blacklist.
Optionally, the obtaining module 302 is further configured to periodically obtain the blacklist, and the determining module 303 is further configured to determine whether openflow connections in the blacklist conform to an activation rule, if so, move openflow connections that conform to the activation rule into the nanotube connection pool, and delete openflow connections that conform to the activation rule in the blacklist.
Optionally, the determining module 302 is specifically configured to determine whether the connection frequency of the openflow connection to be currently determined is less than or equal to a second preset threshold between before the preset time and the current time in the blacklist, and if the connection frequency of the openflow connection to be currently determined is less than or equal to the second preset threshold, add the openflow connection to be currently determined to a corresponding connection pool according to the connection pool type of the openflow connection recorded in the blacklist.
Optionally, the determining module is specifically configured to determine whether openflow connections in the blacklist conform to the aging rule if the openflow connections in the blacklist do not conform to the activation rule, and delete openflow connections that conform to the aging rule in the blacklist if the openflow connections in the blacklist conform to the aging rule.
The apparatus provided in this disclosure is configured to execute the method in the first embodiment or the second embodiment, and a specific execution process is not described in detail in this disclosure. Reference may be made to method embodiments specifically, which are not described in detail in this embodiment.
On the basis of the foregoing embodiment, the present disclosure further provides a controller 40, and fig. 4 is a schematic structural diagram of a controller according to another embodiment of the present disclosure, as shown in fig. 4, the controller 40 includes a processor 401 and a memory 402, where the memory 402 is used to store program instructions, the processor 401 is used to call the program instructions stored in the memory, and when the processor 401 executes the program instructions stored in the memory 402, the controller is used to execute the method executed by the controller according to the foregoing embodiment.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a readable storage medium, which includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (10)
1. A management method of a network device is applied to a controller, and is characterized by comprising the following steps:
if the newly-built openflow connection is monitored, obtaining a blacklist of the openflow connection;
determining whether the newly-built openflow connection is an openflow connection in a blacklist;
if the newly-built openflow connection is not in the blacklist, acquiring connection information of openflow established by managed network equipment in a managed connection pool;
judging whether the newly-built openflow connection exists in the nano-tube connection pool or not, and if not, adding the newly-built openflow connection into an unknown connection pool;
and judging whether the newly-built openflow connection conforms to a rule for pulling in a blacklist, if so, adding the newly-built openflow connection to the blacklist, and disconnecting the newly-built openflow connection.
2. The method of claim 1, wherein the determining whether the newly-built openflow connection complies with a pull-in blacklist rule comprises:
and judging whether the connection times of the current newly-built openflow connection in a preset time length is larger than a first preset threshold, and if so, determining that the newly-built openflow connection conforms to a rule of pulling in a blacklist.
3. The method according to claim 1, wherein the blacklist is periodically acquired, whether openflow connections in the blacklist conform to activation rules or not is judged, if yes, the openflow connections conforming to the activation rules are moved into the nanotube connection pool, and the openflow connections conforming to the activation rules in the blacklist are deleted.
4. The method of claim 3, wherein determining whether openflow connections in the blacklist comply with activation rules comprises:
and judging whether the connection times of the openflow connection to be judged currently are less than or equal to a second preset threshold value between the time before the preset duration and the current time in the blacklist, and if so, adding the openflow connection to be judged currently into a corresponding connection pool according to the connection pool type of the openflow connection recorded in the blacklist.
5. The method according to claim 3, wherein if the openflow connections in the blacklist do not comply with the activation rule, determining whether the openflow connections in the blacklist comply with the aging rule, and if so, deleting the openflow connections in the blacklist complying with the aging rule.
6. An apparatus for managing a network device, the apparatus comprising: the system comprises a monitoring module, an acquisition module, a judgment module and a resource pool module; the resource pool module comprises a blacklist, a nanotube connection pool and an unknown connection pool;
the monitoring module is used for prompting the acquisition module to acquire a blacklist of openflow connections if the new openflow connections are monitored;
the judging module is used for determining whether the newly-built openflow connection is an openflow connection in a blacklist;
the judging module is further configured to prompt the obtaining module to obtain connection information of openflow established by managed network devices in the managed connection pool if it is determined that the newly-built openflow connection is not in the blacklist;
the judging module is also used for judging whether the newly-built openflow connection exists in the nanotube connecting pool or not, and if not, adding the newly-built openflow connection into an unknown connecting pool;
the judging module is further used for judging whether the newly-built openflow connection conforms to a rule for pulling in a blacklist, if so, adding the newly-built openflow connection to the blacklist, and disconnecting the newly-built openflow connection.
7. The apparatus according to claim 6, wherein the determining module is specifically configured to determine whether a connection frequency of the currently newly-built openflow connection within a preset duration is greater than a first preset threshold, and if so, determine that the newly-built openflow connection conforms to a rule of pulling into a blacklist.
8. The apparatus according to claim 7, wherein the obtaining module is further configured to periodically obtain the blacklist, and the determining module is further configured to determine whether openflow connections in the blacklist conform to an activation rule, and if so, move openflow connections that conform to the activation rule into the nanotube connection pool, and delete openflow connections that conform to the activation rule in the blacklist.
9. The apparatus according to claim 8, wherein the determining module is specifically configured to determine whether a connection frequency of the openflow connection to be currently determined is less than or equal to a second preset threshold between a time before a preset duration and a current time in the blacklist, and if the connection frequency of the openflow connection to be currently determined is less than or equal to the second preset threshold, add the openflow connection to be currently determined to a corresponding connection pool according to a connection pool type of the openflow connection recorded in the blacklist.
10. The apparatus according to claim 8, wherein the determining module is specifically configured to determine whether openflow connections in the blacklist conform to an aging rule if the openflow connections in the blacklist do not conform to the activation rule, and delete openflow connections in the blacklist that conform to the aging rule if the openflow connections in the blacklist conform to the aging rule.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011350342.8A CN112671711B (en) | 2020-11-26 | 2020-11-26 | Network equipment management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011350342.8A CN112671711B (en) | 2020-11-26 | 2020-11-26 | Network equipment management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112671711A true CN112671711A (en) | 2021-04-16 |
| CN112671711B CN112671711B (en) | 2022-07-12 |
Family
ID=75404159
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011350342.8A Active CN112671711B (en) | 2020-11-26 | 2020-11-26 | Network equipment management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671711B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015146884A1 (en) * | 2014-03-28 | 2015-10-01 | ブラザー工業株式会社 | Control device, head-mounted display, and system |
| CN106534048A (en) * | 2015-09-11 | 2017-03-22 | 中国电信股份有限公司 | Method of preventing SDN denial of service attack, switch and system |
| CN107819648A (en) * | 2017-11-14 | 2018-03-20 | 新华三技术有限公司 | Network configuration NETCONF connecting detection method and apparatus |
| CN108183950A (en) * | 2017-12-28 | 2018-06-19 | 新华三技术有限公司 | A kind of network equipment establishes the method and device of connection |
| CN108322467A (en) * | 2018-02-02 | 2018-07-24 | 云宏信息科技股份有限公司 | Virtual firewall configuration method, electronic equipment and storage medium based on OVS |
| CN110233766A (en) * | 2019-06-26 | 2019-09-13 | 和记奥普泰通信技术有限公司 | A method of OTN, PTN, IPRAN, SPN and PON network automatic deployment based on IPv6 |
-
2020
- 2020-11-26 CN CN202011350342.8A patent/CN112671711B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015146884A1 (en) * | 2014-03-28 | 2015-10-01 | ブラザー工業株式会社 | Control device, head-mounted display, and system |
| CN106534048A (en) * | 2015-09-11 | 2017-03-22 | 中国电信股份有限公司 | Method of preventing SDN denial of service attack, switch and system |
| CN107819648A (en) * | 2017-11-14 | 2018-03-20 | 新华三技术有限公司 | Network configuration NETCONF connecting detection method and apparatus |
| CN108183950A (en) * | 2017-12-28 | 2018-06-19 | 新华三技术有限公司 | A kind of network equipment establishes the method and device of connection |
| CN108322467A (en) * | 2018-02-02 | 2018-07-24 | 云宏信息科技股份有限公司 | Virtual firewall configuration method, electronic equipment and storage medium based on OVS |
| CN110233766A (en) * | 2019-06-26 | 2019-09-13 | 和记奥普泰通信技术有限公司 | A method of OTN, PTN, IPRAN, SPN and PON network automatic deployment based on IPv6 |
Non-Patent Citations (1)
| Title |
|---|
| 徐洋等: "SDN中DDoS检测及多层防御方法研究", 《信息网络安全》, no. 12, 10 December 2017 (2017-12-10) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112671711B (en) | 2022-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109842528B (en) | Service function chain deployment method based on SDN and NFV | |
| EP3804389B1 (en) | Dynamic backup amf determination and publication | |
| CN109474508B (en) | VPN networking method, VPN networking system, VPN master node equipment and VPN master node medium | |
| CN101291305A (en) | Method and customer terminal realizing plug-in management | |
| EP3477894B1 (en) | Method and device for controlling virtualized broadband remote access server (vbras), and communication system | |
| CN111984561B (en) | IPMI command processing method, system, device and medium for BMC | |
| CN106571942B (en) | Configuration data updating method, client and server | |
| US8054831B2 (en) | Method and apparatus for transmitting and receiving information regarding UPnP event | |
| CN111813576B (en) | Business service management method and system based on micro-service | |
| CN109039764B (en) | Network parameter configuration method of distributed storage system | |
| EP3197207A1 (en) | Method for managing application resources and registered node in m2m | |
| CN112671711B (en) | Network equipment management method and device | |
| CN107105037B (en) | Distributed video CDN resource management system and method based on file verification | |
| CN109150921B (en) | Login method, device, equipment and storage medium of multi-node cluster | |
| CN111176904A (en) | Method, system, equipment and medium for data backup under private cloud architecture | |
| CN116633766A (en) | Fault processing method and device, electronic equipment and storage medium | |
| CN114866265B (en) | Network connection method, router, administrator terminal device, and communication device | |
| CN115174596A (en) | Equipment remote copying method, device and medium | |
| CN111478937B (en) | Load balancing method and device | |
| CN116107687A (en) | Cluster resource automatic telescoping method, device and system | |
| CN113472566A (en) | Status monitoring method of union block chain and master node status monitoring system | |
| CN104735097A (en) | Information collecting method and system | |
| JP4143766B2 (en) | Congestion control device, congestion control method and program | |
| CN110856248B (en) | PDP management and deactivation algorithm for LTE single-mode system | |
| WO2018126483A1 (en) | Method and apparatus for controlling network services |
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 |