CN106254099B - Information synchronization method and device based on network element equipment - Google Patents
Information synchronization method and device based on network element equipment Download PDFInfo
- Publication number
- CN106254099B CN106254099B CN201610601911.9A CN201610601911A CN106254099B CN 106254099 B CN106254099 B CN 106254099B CN 201610601911 A CN201610601911 A CN 201610601911A CN 106254099 B CN106254099 B CN 106254099B
- Authority
- CN
- China
- Prior art keywords
- synchronized
- topology
- information
- network element
- forwarding
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides an information synchronization method and device of network element equipment. The method IS applied to first network element equipment from an intermediate system to an intermediate system IS-IS, and comprises the following steps: acquiring information to be synchronized, wherein the information to be synchronized comprises a topology identifier and a forwarding strategy; updating the forwarding information stored locally according to the topology identification and the forwarding strategy; generating a message to be synchronized, wherein the message to be synchronized carries the information to be synchronized; and sending the message to be synchronized to second network element equipment, so that the second network element equipment updates forwarding information in the second network element equipment according to the message to be synchronized. By the embodiment of the invention, the network element equipment in the same topological area can automatically update the forwarding information according to the information to be synchronized carried by the message to be synchronized, and the automatic synchronization function of the multi-topology forwarding strategy is realized, so that the configuration workload of the forwarding strategy is reduced, and the efficiency of deploying sub-topologies is improved.
Description
Technical Field
The present invention relates to the field of computer network technologies, and in particular, to an information synchronization method and an information synchronization apparatus for a network element device.
Background
In order to provide support for Internet Protocol (IP) routing of interconnection between networks, an Internet Engineering Task Force (IETF) expands and modifies an Intermediate System-to-Intermediate System (IS-IS) Protocol in RFC 1195, so that an IS-IS Protocol can be simultaneously applied to a Transmission control Protocol/Internet Protocol (TCP/IP) and an Open System Interconnection (OSI) environment to form an Integrated IS-IS (Integrated IS-IS or Dual IS-IS) environment. The IS-IS belongs to an Interior Gateway Protocol (IGP) and IS used in an autonomous system. IS-IS a link state protocol that uses a Shortest Path First (SPF) algorithm for route calculation.
Specifically, a Multi-Topology Routing (MTR) technology divides a physical Topology into multiple logical topologies, that is, networks of multiple logical topologies are virtually simulated on the same physical network to respectively carry different types of traffic such as voice and video. These logical topologies may be crossed or overlapped. Different logical topologies run respective routing computations to achieve network interworking. Generally, the global topology can be divided into a plurality of sub-topologies according to needs, so that different types of traffic can travel through different topologies, for example, a voice stream can travel through the sub-topology a, and a video stream can travel through the sub-topology B, that is, different logical topologies correspond to different services, thereby realizing logical separation and partial physical separation of the services, and realizing rapid service recovery when a link or a node fails. For example, fig. 1 shows a schematic diagram of a multi-topology in a networking, wherein a Router (Router) a, a Router D, and a Router C connected in sequence constitute a sub-topology a, i.e., for the sub-topology a, a Router B does not exist; the sequentially connected routers (Router) a, Router B, Router D and Router C form a sub-topology B, but for the sub-topology B, it is considered that Router a and Router D are not directly connected, and Router B and Router C are not directly connected. Each individual sub-topology calculates its own route according to the routing protocol, and the traffic belonging to the topology is forwarded according to the routing table of the topology. For example, when a Differentiated Services Code Point (DSCP) value in an IP header of a traffic IS 40, if the traffic needs to be forwarded in the sub-topology B, the IS-IS multi-topology function needs to be enabled on Router a, Router B, Router C, and Router D, and a neighbor relationship of the IS-IS sub-topology B IS established between them; meanwhile, in order to forward the corresponding traffic in the topology, it is also necessary to configure the same forwarding policy on each router, that is, the content included in the forwarding policy is the traffic matching the DSCP value of 40, and a forwarding table entry must be searched in the sub-topology B, so that the traffic can search the corresponding forwarding table entry in the sub-topology B, and the traffic is forwarded in the sub-topology B. When the forwarding policy of one Router in Router a, Router B, Router C, and Router D is inconsistent, if the forwarding policy on Router B is inconsistent with the other three routers, the traffic with the DSCP value of 40 is not matched, that is, in the process of searching for the forwarding table entry in sub-topology a, after the traffic comes from Router a, the forwarding table entry is first searched for in sub-topology B on Router a, and the forwarding table entry in sub-topology a is searched for, so that the traffic reaches Router B; and searching for a forwarding table entry in the sub-topology A on the Router B according to the forwarding strategy, wherein the sub-topology A does not have a corresponding forwarding table entry, and the flow is discarded. Similarly, if the Router B is not configured with the forwarding policy, the forwarding table entry in the basic topology is searched when the traffic reaches the Router B, and the traffic is discarded without a corresponding table entry in the basic topology, so that the traffic is not forwarded according to the established topology, and the traffic is discarded or the forwarding path is inconsistent with the expected path. Therefore, in order to ensure that the traffic can be forwarded according to the correct forwarding path, the same forwarding policy needs to be manually configured on each router.
When the IS-IS multi-topology network IS large, manual configuration of the forwarding policy needs to be performed for each router, and the problem of large configuration workload exists.
Disclosure of Invention
In view of the above problems, embodiments of the present invention are provided to provide an information synchronization method based on network element devices and a corresponding information synchronization apparatus based on network element devices, so as to implement automatic synchronization of forwarding policies, so as to solve the problem of large configuration workload.
In order to solve the above problem, an embodiment of the present invention discloses an information synchronization method based on network element devices, which IS applied to a first network element device from an intermediate system to an intermediate system IS-IS, and includes:
acquiring information to be synchronized, wherein the information to be synchronized comprises a topology identifier and a forwarding strategy;
updating the forwarding information stored locally according to the topology identification and the forwarding strategy;
generating a message to be synchronized, wherein the message to be synchronized carries the information to be synchronized;
and sending the message to be synchronized to second network element equipment, so that the second network element equipment updates forwarding information in the second network element equipment according to the message to be synchronized.
Correspondingly, the embodiment of the invention also discloses an information synchronization device based on network element equipment, which IS applied to the first network element equipment from the intermediate system to the intermediate system IS-IS, and comprises the following steps:
the information acquisition module is used for acquiring information to be synchronized, wherein the information to be synchronized comprises a topology identifier and a forwarding strategy;
the information updating module is used for updating the forwarding information stored locally according to the topology identifier and the forwarding strategy;
the message generating module is used for generating a message to be synchronized, and the message to be synchronized carries the information to be synchronized;
and the message sending module is used for sending the message to be synchronized to second network element equipment so that the second network element equipment updates forwarding information in the second network element equipment according to the message to be synchronized.
The embodiment of the invention has the following advantages:
in the embodiment of the invention, the first network element equipment from the intermediate system to the intermediate system IS-IS can update the forwarding information stored locally by acquiring the information to be synchronized, generate the message to be synchronized, and send the message to be synchronized carrying the synchronization information to the second network element equipment, so that the second equipment can update the forwarding information according to the message to be synchronized, wherein the synchronization information comprises the topology identifier and the forwarding strategy, namely, each network element equipment in the same topology area can automatically synchronize the forwarding strategy according to the synchronization information, thereby realizing the function of automatically synchronizing the multi-topology forwarding strategies, reducing the configuration workload of the forwarding strategies and improving the efficiency of deploying sub-topologies.
Drawings
FIG. 1 IS a schematic diagram of multiple topologies in IS-IS networking;
fig. 2 is a flowchart illustrating steps of an embodiment of an information synchronization method based on a network element device according to the present invention;
fig. 3 is a flowchart illustrating steps of another embodiment of an information synchronization method based on network element devices according to the present invention;
fig. 4 is an interaction diagram of two network element devices automatically synchronizing forwarding policy in a specific example of the present invention;
fig. 5 is a schematic diagram of a format of a field CLV added in a specific example of the present invention;
fig. 6 is a schematic diagram of a format of VALUE in CLV according to a specific example of the present invention;
fig. 7 is a block diagram of an embodiment of an information synchronization apparatus of a network element device according to the present invention;
fig. 8 is a block diagram of another embodiment of the information and device of the network element equipment according to the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.
To support large scale routing networks, IS-IS employs a two-level hierarchy within a routing domain, i.e., a large routing domain IS typically divided into multiple Areas (Areas). Wherein, the Level-1 router and the Level-2 router respectively maintain their Link State databases (Link State Data Base, LSDB). The state of all the connecting links within the network constitutes an LSDB, i.e. there IS at least one LSDB in each IS. The IS uses the SPF algorithm to generate its own route using the LSDB, so that traffic belonging to its own topology IS forwarded according to the routing table of its own topology, that IS, each router belonging to the same connection link forwards traffic according to the same forwarding policy. For example, IS-IS MRT refers to a technology that can run multiple independent IP topologies, such as IPv4 topology and IPv6 topology, within the same IS-IS autonomous domain, rather than treating them as an integrated single topology. This IS advantageous for IS-IS to consider IPv4 and IPv6 networks separately in routing computation according to actual networking conditions.
One of the core concepts of the embodiments of the present invention is that a first network element device obtains information to be synchronized, updates locally stored forwarding information according to a flapping identifier and a forwarding policy in the information to be synchronized, and then sends a message to be synchronized carrying the information to be synchronized to a second network element device, so that the second network element device can update the forwarding information according to the received message to be synchronized. The information to be synchronized comprises a topology identifier and a forwarding policy, that is, the embodiment of the present invention enables each network element device in the same topology area to update local forwarding information according to the information to be synchronized and automatically synchronize the forwarding policy, thereby reducing the configuration workload of the forwarding policy and improving the efficiency of deploying sub-topologies.
Referring to fig. 2, a flowchart illustrating steps of an embodiment of an information synchronization method based on a network element device according to the present invention is shown, which may specifically include the following steps:
In the embodiment of the present invention, the information to be synchronized may include a topology identifier and a forwarding policy. The forwarding policy may include a content of the forwarding policy, and may be specifically used to determine a forwarding policy of a topology area, so as to implement forwarding of traffic. The forwarding policy content may be determined according to the content of the forwarding policy input by the user for the topological area.
The user may input the forwarding policy content on the network element device for a certain topology area, so that the network element device configures the forwarding policy of the topology area according to the input forwarding policy content, for example, the network element device may use the forwarding policy content input by the user and the topology identifier of the topology area as information to be synchronized, and store the information in the local database. Specifically, in the IS-IS network, when network element equipment such as a Router (Router) acquires that a user inputs forwarding policy content for a certain topology area, the forwarding policy content and a topology identifier of the topology area may be used as information to be synchronized corresponding to the topology area, so as to update the forwarding policy of the topology area by using the information to be synchronized, that IS, update locally stored forwarding information.
Of course, the network element device may also obtain the information to be synchronized in other manners, for example, the forwarding policy content configured by the user for the topology area may be obtained from the data packet sent by other network element devices, and the topology identifier of the topology area and the obtained forwarding policy content may be used as the information to be synchronized.
And step 204, updating the forwarding information stored locally according to the topology identifier and the forwarding strategy.
In the embodiment of the present invention, the network element device may locally store forwarding information corresponding to each topology area, so as to repackage the received data packet according to the forwarding information, thereby implementing traffic forwarding. The locally stored forwarding information may specifically include a topology identifier of each topology area and a corresponding forwarding policy, and may be used to determine a forwarding path of the data packet.
Specifically, after the network element device of the embodiment of the present invention obtains the information to be synchronized, the network element device may serve as a first network element device, and may determine, according to the topology identifier in the information to be synchronized, a target topology region in which a forwarding policy needs to be updated, and then may replace, by using the forwarding policy in the information to be synchronized, the forwarding policy corresponding to the target topology region stored in the forwarding information, so as to update the forwarding policy corresponding to the target topology region, that is, update the locally stored forwarding information by using the forwarding policy in the information to be synchronized.
For example, an IS-IS multi-topology neighbor relationship IS established between Router a and Router B, and an automatic synchronization function of a multi-topology forwarding policy can be enabled on Router a by issuing a command, so that Router a, as a first network element device, can generate information to be synchronized corresponding to a topology area according to forwarding policy content input by a user for the topology area, and further can update the forwarding policy of the topology area by using the information to be synchronized. The Router a may use the configured forwarding policy content as the forwarding policy corresponding to the topology area, and may obtain the corresponding topology identifier. The topology identifier may be used to determine a topology area in which the forwarding policy needs to be updated. Router a may use the topology identifier and the forwarding policy as information to be synchronized, update the forwarding policy of the topology area corresponding to the topology identifier according to the forwarding policy included in the information to be synchronized, and generate the synchronization identifier corresponding to the topology area after the update is completed, for example, mark position 1 with an automatic synchronization function of the multi-topology forwarding policy to identify that the update of the forwarding policy of the topology area is completed.
The message to be synchronized according to the embodiment of the present invention may carry synchronization information. Specifically, the first network element device may encapsulate information to be synchronized into a message transmitted in the topology area, for example, encapsulate the forwarding policy into a link state data packet in a user-defined manner, and generate a corresponding message to be synchronized. The message to be synchronized may be flooded to a second network element device connected to the first network element device, such as a Link State Protocol Data Unit (LSPDU). The second network element device may specifically include a neighbor device connected to the first network element device, such as Router B connected to Router a in the above example. It should be noted that in the IS-IS network, each IS generates LSPDU. The LSPDU, which may be abbreviated as LSP, contains all link state information of the IS, and IS transmitted in the entire IS-IS network for interacting with other IS routers.
As a specific example of the present invention, the first network element device may extract the LSDB content from the LSDB by looking up the LSDB. The LSDB content may include System identification codes (System IDs) and names of all IS-IS routers in the IS-IS network, and contents of corresponding multi-topology IDs and multi-topology forwarding policies, etc. Therefore, the first network element device in the IS-IS network can obtain the forwarding policy corresponding to the topology area from the LSDB, and generate the corresponding information to be synchronized. The information to be synchronized may be added to the custom field of the link data packet in a custom manner, and specifically may include: and parameter information such as topology identification, forwarding strategy and information type of the topology area. Topology identification can be used to identify a topology region, such as a multi-topology ID; the information type may be used to identify information to be synchronized, such as a forwarding policy identifier (Code).
After generating the to-be-synchronized message, the first network element device of this embodiment may flood the to-be-synchronized message to other network element devices in the topology area, so that each network element device in the topology area may automatically update the forwarding policy of the topology area according to the to-be-synchronized information in the to-be-synchronized message. Specifically, after receiving the message to be synchronized, the second network element device may extract information to be synchronized, such as a forwarding policy and a topology identifier, from the message to be synchronized, and further may store the extracted forwarding policy and topology identifier in the local database, thereby implementing automatic configuration of the forwarding policy corresponding to the topology area.
As a specific example of the present invention, Router a may encapsulate information to be synchronized, which includes a forwarding policy and a topology identifier, into an LSP, and may flood the information to be synchronized into neighbor Router B through the LSP. After receiving the LSP, Router B may parse the LSP, extract the topology ID and the forwarding policy, and issue the configuration to the local. If Router B also enables the multi-topology forwarding policy automatic synchronization function, the forwarding policy and the topology identifier may be added to the LSP, and the LSP is flood-protected to other neighboring devices, so as to implement an automatic synchronization forwarding policy of each network element device in the topology area corresponding to the topology ID.
Through the embodiment of the invention, the first network element equipment from the intermediate system to the intermediate system IS-IS can update the forwarding information stored locally by acquiring the information to be synchronized, can generate the message to be synchronized, and sends the message to be synchronized carrying the synchronization information to the second network element equipment, so that the second equipment can update the forwarding information according to the message to be synchronized, namely, each network element equipment in the same topological area can automatically synchronize the forwarding strategy according to the synchronization information, thereby realizing the function of automatically synchronizing the multi-topology forwarding strategy, reducing the configuration workload of the forwarding strategy and improving the efficiency of deploying the sub-topology.
Referring to fig. 3, a flowchart illustrating steps of another embodiment of an information synchronization method based on network element devices according to the present invention is shown, which may specifically include the following steps:
The synchronization information may specifically include a topology identifier and a forwarding policy. The first network element device of the embodiment of the present invention may update the locally stored forwarding information according to the topology identifier and the forwarding policy in the synchronization information, so as to ensure that the traffic of the topology area can be forwarded according to the correct forwarding path.
Specifically, the first network element device in this embodiment may determine, according to the content input by the user for the forwarding policy of a certain topology area, the forwarding policy corresponding to the topology area, and update the forwarding policy of the topology area by using the forwarding policy. For example, the first network element device may use content input by the user as a forwarding policy of the topology area, establish an association relationship between the topology ID of the topology area and the forwarding policy, store the association relationship in the local database, and complete updating of the forwarding policy of the topology area, for example, configure the forwarding policy of the topology area with the forwarding policy, or update the forwarding policy of the topology area with the forwarding policy, which is not specifically limited in this embodiment of the present invention.
In a preferred embodiment of the present invention, updating the locally stored forwarding information according to the topology identifier and the forwarding policy in the synchronization information may specifically include: searching a target forwarding strategy corresponding to the topology identifier in the forwarding information according to the topology identifier; and replacing the target forwarding strategy with the forwarding strategy.
In particular, the first network element device may typically store the locally stored forwarding information in a local database. Therefore, the first network element device may use the topology identifier to search the local database to determine whether the locally stored forwarding information includes the target forwarding policy corresponding to the topology identifier. If the target forwarding policy corresponding to the topology identifier is not stored in the local database, it may be determined that the first network element device does not configure the forwarding policy of the topology area corresponding to the topology identifier, that is, the locally stored forwarding information does not include the target forwarding policy, and then the generated forwarding policy may be used to configure the forwarding policy of the topology area; if the forwarding policy of the topology area is stored in the local database, the generated forwarding policy may be used to replace the forwarding policy stored in the database, so as to update the forwarding policy of the topology area, for example, when it is determined that the locally stored forwarding information includes the target forwarding policy and when the forwarding policy is inconsistent with the stored target forwarding policy, the forwarding policy may be used to replace the target forwarding policy, so as to implement automatic updating of the forwarding policy of the topology area.
Wherein, the message to be synchronized carries the information to be synchronized.
In the embodiment of the present invention, when the first network element device completes updating the forwarding policy, the first network element device may generate a corresponding synchronization identifier to trigger the function of automatically synchronizing the forwarding policy. For example, a user may configure a forwarding policy corresponding to a certain topology area on Router a, and may enable the multi-topology forwarding policy automatic synchronization function of Router a, such as marking the multi-topology forwarding policy automatic synchronization function as position 1, by issuing a command to Router a, so that Router a may update the forwarding policy of the topology area according to the topology identifier and the forwarding policy in the information to be synchronized.
After the update is completed, the first network element device may generate a synchronization identifier corresponding to the topology identifier, so as to trigger the function of the automatic synchronization forwarding policy. After triggering the function of the automatic synchronization forwarding policy, the first network element device may identify a packet corresponding to the topology area through the topology identifier, and further may obtain a packet corresponding to the topology area, add information to be synchronized to the packet, for example, encapsulate the topology identifier and the forwarding policy into the packet in a user-defined manner, and generate a packet to be synchronized that carries the synchronization information.
Specifically, the network element device may determine the corresponding topology area by using the topology identifier, for example, identify the corresponding connection link by using the topology ID, so that the neighbor device connected to the connection link may be used as the second device. Therefore, the first network element device of the embodiment of the present invention may determine the second network element device in the topology area by using the topology identifier.
In a preferred embodiment of the present invention, the updating, by the network element device, the forwarding information may specifically include: when the message to be synchronized is received, extracting a forwarding strategy and a topology identifier from the message to be synchronized; and establishing a corresponding relation between the extracted forwarding strategy and the topology identifier, and storing the corresponding relation.
For example, when receiving a link data packet, the second network element device may parse the link status data packet, so as to extract information to be synchronized from the link data packet, such as a forwarding policy and a topology identifier, and further determine a corresponding topology area according to the extracted topology identifier data, and store the forwarding policy and the topology identifier in a local database, so as to update the forwarding policy of the determined topology area.
It should be noted that, after extracting the information to be synchronized, the second network element device in the embodiment of the present invention may also serve as the first network element device, and generate a corresponding synchronization identifier after the updating is completed, so as to add the forwarding policy to the link state data packet in the topology area based on the synchronization identifier, so that the forwarding policy may be flooded to other network element devices in the topology area through the link state data packet.
It can be seen that, in this embodiment, by adding a forwarding policy to a link state data packet, each network element device in the IS-IS network can automatically synchronize a forwarding policy according to the forwarding policy of the data packet, for example, in a sub-topology network, only one router needs to issue the forwarding policy, all routers in the topology network are automatically synchronized, the sub-topology deployment IS performed quickly and efficiently, and traffic can be correctly directed to be forwarded in the topology, that IS, the efficiency of deploying the sub-topology IS improved while reducing the configuration workload of the forwarding policy.
The maintenance table may include a system identification code, a forwarding policy, a topology identifier, and the like corresponding to each network element device in the topology area.
Specifically, in an IS-IS network, the local database of network element devices includes a link state database. The link state database may store link state information of the network element device interacting with other network element devices, such as System identification codes (System IDs) and names of all IS-IS routers in the IS-IS network, and contents of corresponding multi-topology IDs and multi-topology forwarding policies. Where the IS-IS router may maintain these contents in a table form. Therefore, the network element device may generate the maintenance table corresponding to the topology area by using the forwarding information stored in the link state database based on the synchronization identifier, for example, obtain the topology ID and the forwarding policy in the LSP, and generate the corresponding maintenance table.
For example, after all routers are synchronized, each IS-IS router in the IS-IS network can extract System IDs and names of all IS-IS routers in the IS-IS network, and corresponding multi-topology IDs and multi-topology forwarding policies on the IS-IS device at the multi-topology forwarding policy automatic synchronization function flag position 1 by looking up the internal data structure of the LSDB, so that the multi-topology IDs and multi-topology forwarding policies corresponding to the IS-IS routers in the network can be displayed in a topology tree diagram manner in a one-to-one correspondence manner. When different multi-topology forwarding strategies exist in the network, and the service flow in the topology IS not communicated, the System Id and the name of the IS-IS router corresponding to the multi-topology forwarding strategies can be quickly located by looking up the topology tree diagram, namely the table content, so that the forwarding strategies of which router in the connection link are inconsistent can be conveniently searched, and the maintenance and the modification of the multi-topology forwarding strategies of the IS-IS router are facilitated.
Referring to fig. 4, an interaction diagram of two network element devices for automatically synchronizing forwarding policy in a specific example of the present invention is shown, which specifically includes the following steps:
step 402, establishing IS-IS multi-topology neighbor relation between Router A and Router B.
In the present example, to implement the multi-topology forwarding policy automatic synchronization function, the IS-IS adds a field CLV. The CLV is abbreviated in Code/Length/Value format, and the format is shown in FIG. 5. C IS an abbreviation of Code, and can be used to represent an identification Code set according to IS-IS protocol, such as setting the value of Code to 241 to identify the CLV field as a multi-topology forwarding policy; l is an abbreviation for Length and may represent a range of the VALUE field, e.g., if CLV occupies 2 bytes, the data range for Length is 2 to 255. As shown in fig. 6, a format diagram of VALUE in CLV is shown. Wherein the R bit represents a reserved bit, such as the first 4 position 0 in VALUE can be set as a reserved bit; the MT ID is 12 bits and can be used for representing a multi-topology ID which can be consistent with the topology ID for establishing the multi-topology neighbor; the MT POLICY may include contents of forwarding policies issued by network element devices that enable the multi-topology forwarding POLICY automatic synchronization function, and the data range of the contents of the forwarding policies may be 0 to 253.
The topology ID corresponding to the link connected between Router A and Router B is 10.
And step 404, Router A enables the multi-topology forwarding strategy automatic synchronization function and fills CLV.
In the IS-IS system, a user can enter a synchronization state by issuing a synchronization command to Router a. In the synchronous state, Router a may fill a CLV in a preset manner, for example, the CLV with an encapsulation identifier Code of 241, where an MT ID field in the CLV is filled with a corresponding topology ID, that is, the topology ID in the MT ID field is 10, and the MTPOLICY content in the VALUE field is empty.
In step 406, Router A floods the LSP to a neighboring device RouteR B.
After the Router a fills the CLV, the CLV may be used as information to be synchronized, and the CLV may be encapsulated in the LSP, so that the information to be synchronized is flooded to the neighboring device Router b through the LSP, and meanwhile, the synchronization identifier may be used to identify that the forwarding policy of the connection link is configured automatically.
Step 408, after receiving the LSP, the RouterB may analyze the CLV carried by the LSP to extract the topology ID and the corresponding forwarding policy content and issue the configuration to the local.
Specifically, after receiving the LSP, the RouterB may identify the CLV according to 241 of the Code carried by the CLV, further analyze the CLV, extract the topology ID carried by the CLV and the corresponding forwarding policy content, and issue and configure the topology ID and the corresponding forwarding policy content to the local database, and may identify the forwarding policy of the topology area as being automatically configured, for example, identify the forwarding policy content corresponding to the topology ID of 10 as being automatically configured. Of course, this embodiment may also determine whether the Router B also enables the multi-topology forwarding policy automatic synchronization function, so that the forwarding policy in the topology area may be flooded to other neighbor devices of the Router B through the Router B when the Router B enables the multi-topology forwarding policy automatic synchronization function.
For example, a multi-topology forwarding policy mtr-policy1 IS issued in Router A, and IS-IS fills the content update of the forwarding policy into CLV with Code of 241. Router A generates the LSP based on the CLV, so that the multi-topology forwarding strategy mtr-policy1 can be flooded to the neighbor Router B through the LSP, namely the LSP containing the CLV is flooded to Router B, and meanwhile, the forwarding strategy can be identified to be automatically configured locally. After receiving the LSP in Router B, Router B may analyze the CLV, extract the forwarding policy content corresponding to the topology ID, and issue the configuration to the local, and may identify that the forwarding policy is automatically configured. If the Router B device is a Level-1-2 device, the CLV needs to be carried and flooded in both the LSP of Level-1 and the LSP of Level-2. Router B can enable the multi-topology forwarding strategy automatic synchronization function based on the synchronization identification data carried by CLV, so that the forwarding strategy content corresponding to the topology ID is flooded to other neighbor equipment
Step 410, Router a and Router a obtain the topology ID and forwarding policy in LSP from the local database, respectively, to generate a maintenance table.
In this embodiment, a device having an ability to automatically synchronize multi-topology forwarding policies, such as Router a and Router a, may automatically set an identifier of an automatic synchronization function of the multi-topology forwarding policy in an internal data structure of an LSDB of the device, generate an issued LSP to include relevant contents of the forwarding policy, and simultaneously obtain a topology ID and a forwarding policy in the LSP from a local LSDB, so as to generate a corresponding maintenance table by associating the multi-topology ID and the multi-topology forwarding policy corresponding to an IS-IS Router in a network one-to-one, thereby maintaining the topology and the corresponding forwarding policy contents on the topology nodes. Therefore, if different multi-topology forwarding strategies exist in the network and the service flow in the topology IS not communicated, the forwarding strategies of all routers connected with the connection link can be checked by checking the maintenance table of any IS-IS router of the connection link, so that the problem of the forwarding non-communication caused by the inconsistent forwarding strategies of any router can be conveniently, quickly and accurately positioned.
In summary, the present implementation implements an automatic synchronization function of forwarding policies of network element devices such as routers in the IS-IS network, so that forwarding policies of all routers connected through the same connection link in the topology network are matched, thereby solving a problem of traffic forwarding failure caused by inconsistent forwarding policies of routers connected through the same connection link. In addition, the relationship between the topology maintained in the maintenance table and the forwarding policy corresponding to the topology node in this embodiment can visually display what the forwarding policy corresponding to a certain router in the topology is, so that the forwarding policies of the routers connected to the link can be maintained and modified conveniently.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.
Referring to fig. 7, a block diagram of an embodiment of an information synchronization apparatus of a network element device according to the present invention is shown, and specifically includes the following modules:
an information obtaining module 702, configured to obtain information to be synchronized, where the information to be synchronized includes a topology identifier and a forwarding policy;
an information updating module 704, configured to update the locally stored forwarding information according to the topology identifier and the forwarding policy;
a message generating module 706, configured to generate a message to be synchronized, where the message to be synchronized carries the information to be synchronized;
a message sending module 708, configured to send the message to be synchronized to a second network element device, so that the second network element device updates forwarding information in the second network element device according to the message to be synchronized. It should be noted that the information synchronization apparatus in the embodiment of the present invention may be specifically applied to network element devices from an intermediate system to an intermediate system IS-IS, such as the first network element device in the foregoing method embodiment.
Through the embodiment of the present invention, the network element device in the IS-IS can flood the packet to be synchronized to other network element devices in the topology area through the packet sending module 708, so that each other network element device in the topology area can update the locally stored forwarding information according to the to-be-synchronized information carried in the packet to be synchronized, that IS, each network element device in the same topology area can automatically synchronize the forwarding policy according to the synchronization information, thereby implementing the function of automatically synchronizing the multi-topology forwarding policy, reducing the configuration workload of the forwarding policy, and improving the efficiency of deploying the sub-topology.
Referring to fig. 8, there is shown a block diagram of another embodiment of the information synchronization apparatus of the network element device according to the present invention.
Optionally, the message generating module 706 in the embodiment of the present invention may include: an acquisition submodule 7061 and a generation submodule 7063. The obtaining submodule 7061 is configured to obtain a message corresponding to the topological area; a generating submodule 7063, configured to add the information to be synchronized to the message, and generate the message to be synchronized.
In a preferred embodiment of the present invention, the message sending module 708 includes the following submodules:
the device determining submodule 7081 is configured to determine, by using the topology identifier, a second network element device in the topology area;
a sending submodule 7083, configured to send the message to be synchronized to the second network element device, so as to trigger the second network element device to update forwarding information in the second network element device.
Optionally, the second network element device in this embodiment may specifically extract information to be synchronized from the message to be synchronized when the message to be synchronized is received, and automatically update locally stored forwarding information according to the information to be synchronized, for example, when a link state packet carrying a forwarding policy and a topology identifier is received, extract the forwarding policy and the topology identifier from the link state packet; and establishing a corresponding relation between the extracted forwarding strategy and the topology identifier, and storing the corresponding relation.
In a preferred embodiment of the present invention, the information updating module 704 may include the following sub-modules:
the searching submodule 7041 is configured to search, according to the topology identifier, a target forwarding policy corresponding to the topology identifier in the forwarding information;
a replacing submodule 7043, configured to replace the target forwarding policy with the forwarding policy.
In a preferred embodiment of the present invention, the information synchronization apparatus based on network element equipment may further include the following modules:
a synchronization identifier generating module 710, configured to generate a synchronization identifier corresponding to the topology identifier after the forwarding information is updated. Specifically, after the forwarding policy is updated automatically, the network element device in the embodiment of the present invention may generate a synchronization identifier corresponding to the topology identifier through the synchronization identifier generating module 710, so as to invoke the message generating module 706 to add the synchronization information to the message corresponding to the topology area, and generate a to-be-synchronized message, and may send the to-be-synchronized message generated by the message generating module 706 to the second network element device in the topology area through the message sending module 708, thereby implementing synchronization of the forwarding policy in the to-be-synchronized information to other network element devices in the topology area.
The maintenance table generating module 712 may be configured to generate a corresponding maintenance table according to the synchronization identifier and the forwarding information. The maintenance table may specifically include a system identification code, a forwarding policy, a topology identifier, and the like corresponding to each network element device in the topology area, which is not specifically limited in this embodiment.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The information synchronization method based on the network element equipment and the information synchronization device based on the network element equipment provided by the invention are introduced in detail, and a specific example is applied in the text to explain the principle and the implementation mode of the invention, and the description of the above embodiment is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (8)
1. An information synchronization method based on network element equipment, wherein the method IS applied to a first network element equipment from an intermediate system to an intermediate system IS-IS, and the method comprises:
acquiring information to be synchronized, wherein the information to be synchronized comprises a topology identifier and a forwarding strategy;
updating the forwarding information stored locally according to the topology identification and the forwarding strategy;
generating a message to be synchronized, wherein the message to be synchronized carries the information to be synchronized;
sending the message to be synchronized to second network element equipment, so that the second network element equipment updates forwarding information in the second network element equipment according to the message to be synchronized;
the updating of the locally stored forwarding information according to the topology identifier and the forwarding policy includes:
searching a target forwarding strategy corresponding to the topology identifier in the forwarding information according to the topology identifier;
replacing the target forwarding strategy with the forwarding strategy;
the generating of the message to be synchronized includes:
acquiring a message corresponding to the topological area;
and adding the information to be synchronized into the message to generate the message to be synchronized.
2. The method of claim 1, wherein the sending the message to be synchronized to a second network element device comprises:
determining second network element equipment in the topological area by using the topological identification;
and sending the message to be synchronized to the second network element equipment to trigger the second network element equipment to update the forwarding information in the second network element equipment.
3. The method of claim 1, further comprising, before generating the message to be synchronized:
and after the forwarding information is updated, generating a synchronous identifier corresponding to the topology identifier.
4. The method of claim 3, further comprising:
and generating a corresponding maintenance table according to the synchronous identification and the forwarding information, wherein the maintenance table comprises forwarding strategies and topology identifications corresponding to network element equipment in the topology area.
5. An information synchronization apparatus based on network element devices, wherein the apparatus IS applied to a first network element device from an intermediate system to an intermediate system IS-IS, the apparatus comprising:
the information acquisition module is used for acquiring information to be synchronized, wherein the information to be synchronized comprises a topology identifier and a forwarding strategy;
the information updating module is used for updating the forwarding information stored locally according to the topology identifier and the forwarding strategy;
the message generating module is used for generating a message to be synchronized, and the message to be synchronized carries the information to be synchronized;
a message sending module, configured to send the message to be synchronized to a second network element device, so that the second network element device updates forwarding information in the second network element device according to the message to be synchronized;
the information updating module comprises:
the searching submodule is used for searching a target forwarding strategy corresponding to the topology identifier in the forwarding information according to the topology identifier;
a replacement sub-module for replacing the target forwarding strategy with the forwarding strategy;
the message generation module comprises:
the acquisition submodule is used for acquiring messages corresponding to the topological area;
and the generation submodule is used for adding the information to be synchronized into the message to generate the message to be synchronized.
6. The apparatus of claim 5, wherein the messaging module comprises:
the device determining submodule is used for determining second network element devices in the topological area by adopting the topological identification;
and the sending submodule is used for sending the message to be synchronized to the second network element equipment so as to trigger the second network element equipment to update the forwarding information in the second network element equipment.
7. The apparatus of claim 5, further comprising:
and the synchronous identifier generation module is used for generating a synchronous identifier corresponding to the topology identifier after the forwarding information is updated.
8. The apparatus of claim 5 or 6, further comprising:
and the maintenance table generating module is used for generating a corresponding maintenance table according to the synchronous identifier and the forwarding information, wherein the maintenance table comprises the forwarding strategy and the topology identifier corresponding to each network element device in the topology area.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610601911.9A CN106254099B (en) | 2016-07-26 | 2016-07-26 | Information synchronization method and device based on network element equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610601911.9A CN106254099B (en) | 2016-07-26 | 2016-07-26 | Information synchronization method and device based on network element equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106254099A CN106254099A (en) | 2016-12-21 |
| CN106254099B true CN106254099B (en) | 2020-03-31 |
Family
ID=57604070
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610601911.9A Active CN106254099B (en) | 2016-07-26 | 2016-07-26 | Information synchronization method and device based on network element equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106254099B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110518957B (en) * | 2019-07-30 | 2020-11-06 | 北京大学 | Bypass network guiding method in open wireless channel |
| CN113347221B (en) * | 2020-03-02 | 2023-05-12 | 海能达通信股份有限公司 | Data synchronization method, communication station, cluster system and storage device |
| CN114978872B (en) * | 2022-04-21 | 2023-06-06 | 山东浪潮科学研究院有限公司 | SCTP protocol stack synchronization method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102387042A (en) * | 2011-11-22 | 2012-03-21 | 华为技术有限公司 | Automatic configuration method and system as well as network node |
| CN103501260A (en) * | 2013-09-12 | 2014-01-08 | 北京创毅讯联科技股份有限公司 | Network configuration method and access device of enterprise network |
| CN105245382A (en) * | 2015-10-23 | 2016-01-13 | 小米科技有限责任公司 | Router configuration information modifying method and device |
| CN105392140A (en) * | 2015-11-19 | 2016-03-09 | 上海斐讯数据通信技术有限公司 | Key configuration automatic synchronization method among wireless routers |
-
2016
- 2016-07-26 CN CN201610601911.9A patent/CN106254099B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102387042A (en) * | 2011-11-22 | 2012-03-21 | 华为技术有限公司 | Automatic configuration method and system as well as network node |
| CN103501260A (en) * | 2013-09-12 | 2014-01-08 | 北京创毅讯联科技股份有限公司 | Network configuration method and access device of enterprise network |
| CN105245382A (en) * | 2015-10-23 | 2016-01-13 | 小米科技有限责任公司 | Router configuration information modifying method and device |
| CN105392140A (en) * | 2015-11-19 | 2016-03-09 | 上海斐讯数据通信技术有限公司 | Key configuration automatic synchronization method among wireless routers |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106254099A (en) | 2016-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3103230B1 (en) | Software defined networking (sdn) specific topology information discovery | |
| WO2018188464A1 (en) | Methods and devices for realizing ioam, and storage medium | |
| CN110661711B (en) | Method for generating label forwarding table, message sending method, device and equipment | |
| US11050664B2 (en) | Encapsulation method, device and node | |
| EP3070895B1 (en) | Encapsulation method and system for flow identifier | |
| US20160099874A1 (en) | Data packet routing method and device | |
| CN105024985A (en) | Message processing method and apparatus | |
| CN110401599B (en) | Data packet processing method and device, storage medium and electronic device | |
| CN106603413B (en) | Method and device for transmitting flow through designated path | |
| EP3043519A1 (en) | Method, controller, forwarding device, and network system for forwarding packets | |
| CN103841022A (en) | Method and device for building tunnel | |
| CN101986622B (en) | A kind of automatic identifying method of PCE status attribute and system | |
| EP4207701A2 (en) | Connections and accesses for hierarchical path computation element (pce) | |
| US8824451B2 (en) | Method and system for establishing an associated bidirectional label-switched path | |
| CN103828310B (en) | A kind of method of link discovery, system and equipment | |
| CN105591798B (en) | The method, apparatus of OAM Information is transmitted in DCN | |
| CN106254099B (en) | Information synchronization method and device based on network element equipment | |
| WO2015184771A1 (en) | Method and node device for operation, administration, and maintenance of service function chaining | |
| EP2638668A1 (en) | Prioritization of routing information updates | |
| CN108270673A (en) | File transmitting method, device and system | |
| CN107786442B (en) | Metadata transmission method and device | |
| CN103236990A (en) | Routing information synchronization method and equipment | |
| CN105637806A (en) | Method and apparatus for determining network topology, and centralized network state information storage device | |
| CN103746828A (en) | Method and device for network node management | |
| CN111884827B (en) | Method for synchronizing topological information in SFC network and routing network element |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou science and Technology Development Zone, Zhejiang high tech park, No. six and road, No. 310 Applicant before: Huasan Communication Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |