WO2011124183A2 - 路由器集群转发信息库的获得方法及路由器 - Google Patents

路由器集群转发信息库的获得方法及路由器 Download PDF

Info

Publication number
WO2011124183A2
WO2011124183A2 PCT/CN2011/074055 CN2011074055W WO2011124183A2 WO 2011124183 A2 WO2011124183 A2 WO 2011124183A2 CN 2011074055 W CN2011074055 W CN 2011074055W WO 2011124183 A2 WO2011124183 A2 WO 2011124183A2
Authority
WO
WIPO (PCT)
Prior art keywords
router
cluster
information base
forwarding information
interface
Prior art date
Application number
PCT/CN2011/074055
Other languages
English (en)
French (fr)
Other versions
WO2011124183A3 (zh
Inventor
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/074055 priority Critical patent/WO2011124183A2/zh
Priority to CN2011800006695A priority patent/CN102204189A/zh
Publication of WO2011124183A2 publication Critical patent/WO2011124183A2/zh
Publication of WO2011124183A3 publication Critical patent/WO2011124183A3/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/54Organization of routing tables

Definitions

  • the embodiments of the present invention relate to the field of router technologies, and in particular, to a method and a router for obtaining a router cluster forwarding information base.
  • router cluster technology came into being.
  • the so-called router cluster is to interconnect multiple physically independent routers to form a logically integrated router system.
  • Each independent router is centrally and uniformly managed, and operates like a router, greatly simplifying the operation and maintenance of the equipment.
  • router cluster configuration multiple independent routers are usually interconnected by a star topology through a specific central switching frame.
  • the centralized control and management of the router cluster are also located in the central switching frame.
  • the forwarding information base (Forwarding Information Base, FIB for short) of the router cluster is stored in the central switching box, and each router needs a specific interface. Communication with the central switching frame to obtain data routing after the FIB, the cost of software and hardware investment is higher.
  • the embodiment of the invention provides a method for obtaining a router cluster forwarding information base and a router, which are used to solve the problem that the router cluster in the prior art needs a separate central switching frame, and each router needs an additional port to be connected to the central switching frame. The problem of higher costs.
  • An embodiment of the present invention provides a method for obtaining a router cluster forwarding information base, including: a router in a router cluster obtains an internal forwarding information base and an external forwarding information base, where the internal forwarding information base includes: a router from the cluster Go to another router in the cluster Routing information; the external forwarding information base includes: routing information from a router in which the cluster interface is located to the network outside the cluster;
  • the router obtains the router where the cluster interface is located according to the outbound interface information in the external forwarding information base; and obtains routing information to the router where the cluster interface is located in the internal forwarding information base;
  • the destination address corresponding to the outbound cluster interface information in the external forwarding information base, and the routing information in the internal forwarding information base destined for the router where the outbound cluster interface is located are merged into a forwarding information base.
  • the embodiment of the invention further provides a router in a cluster, including:
  • an obtaining module configured to obtain an internal forwarding information base and an external forwarding information base, where the internal forwarding information base includes: routing information from one router in the cluster to another router in the cluster; the external forwarding The information base includes: routing information from a router in which the cluster interface is located to the network outside the cluster;
  • a merging module configured to obtain, according to the outbound interface information in the external forwarding information base, a router where the outbound cluster interface is located, and obtain routing information destined for the router where the outbound cluster interface is located in the internal forwarding information base And combining the destination address corresponding to the outbound cluster interface information in the external forwarding information base and the routing information in the internal forwarding information base to the router where the outbound cluster interface is located into the forwarding information base.
  • the method for obtaining a router cluster forwarding information base and the router in the embodiment of the present invention obtain an internal forwarding information base and an external forwarding information base by each node, and combine the obtained internal forwarding information base with an external forwarding information base to obtain a router. Forward the information base. No additional central switch chassis is required, and each router does not require an additional interface to connect to the central switch chassis to obtain a forwarding information base, which saves software and hardware costs.
  • FIG. 1 is a flowchart of a method for obtaining a router cluster forwarding information base according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a router cluster according to another embodiment of the present invention
  • FIG. 3 is a flow chart of a method for obtaining a router cluster forwarding information base according to another embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a router in a cluster according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of a router in a cluster according to another embodiment of the present invention. detailed description
  • FIG. 1 is a flowchart of a method for obtaining a router cluster forwarding information base according to an embodiment of the present invention. As shown in FIG. 1, the method includes:
  • Step 101 The router in the cluster obtains an Internal Forwarding Information Base (iFIB) and an External Forwarding Information Base (eFIB);
  • iFIB Internal Forwarding Information Base
  • eFIB External Forwarding Information Base
  • the iFIB may include: routing information from one router in the cluster to another router in the cluster.
  • the eFIB can include: Routing information from the router where the cluster interface resides to the network outside the cluster.
  • step 101 may be: the master router receives the information input by the operator to generate the iFIB, and obtains the first routing information connected to the cluster interface according to the dynamic routing protocol, and receives the slave router with the cluster interface.
  • the second route sent to the outbound cluster interface The information generates an eFIB according to the first routing information and the second routing information.
  • the process of generating an eFIB according to the first routing information and the second routing information may include, but is not limited to, a process of selecting an optimal route from multiple routes.
  • step 101 may be: receiving the iFIB and eFIB sent by the master router.
  • Step 102 The router combines iFIB and eFIB into the FIB of the router.
  • the process of merging the iFIB with the eFIB can be understood as follows: According to the outbound interface information in the eFIB, the router where the cluster interface is located is obtained. In iFIB, the routing information of the router to which the cluster interface is located is obtained, and the destination address corresponding to the cluster interface information in the eFIB and the routing information of the router in the iFIB to the outbound cluster interface are merged into a forwarding information base.
  • FIG. 2 is a schematic diagram of a router cluster according to another embodiment of the present invention. It is assumed that routers R1, R2, and R3 are formed as one router cluster. The configuration of each router can be as shown in Table 1:
  • FIG. 3 is a flow chart of a method for obtaining a router cluster forwarding information base according to another embodiment of the present invention. This method is based on the router cluster configuration shown in Fig. 2 and is not intended to limit the scope of protection of the present invention.
  • the frame router generally consists of multiple boards, including a main control board and several interface boards.
  • the main control board is responsible for controlling and managing the interface boards in the frame.
  • the main control board sends configuration and forwarding information to the interface board through inter-board communication. It also collects status information about the interface board.
  • the backplane is connected to a high-speed Ethernet network to form a physical path for inter-board communication.
  • each board is assigned a board number (which can also be a slot number). If the main board wants to send data to an interface board, it only needs to provide the board number of the destination board, so that the data can be passed. The above high speed Ethernet is sent to the destination board.
  • Step 301 The router that forms the router cluster receives the cluster setup command, establishes a router cluster according to the cluster setup command, and distinguishes the primary router from the secondary router.
  • the parameters carried in the grouping command include: node identifiers of all routers that constitute a router cluster, such as router 1, router 2, router 3, or R1, R2, R3, etc., any of which can distinguish the identifiers of the routers. use.
  • the primary router obtains the node ID and IP address of other routers in the router cluster.
  • the other routers in the router cluster get the node ID and IP address of the primary router.
  • R1 is the main router
  • R2 and R3 are slave routers as an example. It should be noted that when the primary router R 1 performs its function as a primary router, it also operates as its own secondary router.
  • the router cluster uses a common data interface on the router for interconnection.
  • the data packet and the control packet in the cluster share the same interface/link. Therefore, after the data packet topology is formed, the topology of the cluster is naturally formed. No additional equipment and networking work is required. Only a few routers are designated to join the cluster, and a router is appointed as the primary router of the cluster. Just fine.
  • the main control board of the main router can centrally manage all interface boards in the cluster. In this case, the main control board and the interface board in a router frame in the cluster are still interconnected by the in-frame Ethernet, and the original inter-board communication mechanism can be used. However, there is no such interconnection mechanism between the main control board of the master router and the interface board of the slave router, and the inter-board communication between the frames depends on the IP address.
  • Step 302 The primary router generates the cluster iFIB and sends it to all the routers in the cluster, and all the routers receive the iFIB sent by the primary router.
  • the main router can generate an iFIB based on input from the operator.
  • iFIB contains routing information from one router in the cluster to another router in the cluster.
  • the information in iFIB can include, but is not limited to, the information shown in Table 2: Table 2
  • the primary router sends the iFIB to all the routers in the cluster by the following methods:
  • the primary router sends the iFIB to the intranet of the destination router according to the IP address of the router where the destination board is located.
  • the interconnect board sends the iFIB to the destination board using the original inter-board communication method. In this way, each router only needs to have one IP address to achieve cross-frame communication.
  • the inner board may be an interface board or a main control board, and the inner board may be pre-designated.
  • Step 303 The primary router generates the cluster eFIB and sends it to all the routers in the cluster, and all the routers receive the eFIB sent by the primary router.
  • the master router can obtain the first routing information that is connected to the cluster interface through the dynamic routing protocol.
  • the router can obtain the second routing information that is connected to the cluster interface through the dynamic routing protocol and send the routing information to the main control board of the main router.
  • the main control board generates an eFIB according to the obtained first routing information and the received second routing information.
  • eFIB contains the routing information of the routers in the cluster where the cluster interface is located to the out-of-cluster network, but does not include the routing information to each router in the cluster.
  • eFIB can include, but is not limited to, information as shown in Table 3:
  • the eFIB is generated as follows: A router with a cluster interface in the cluster (can be used) Therefore, the primary router or the secondary router obtains routing information connected to its own outbound cluster interface according to the dynamic routing protocol, which may include, but is not limited to, including the router's own IP address, mask, outbound cluster interface, and next hop.
  • the address is passed to the main control board of the main router.
  • the above information may be transmitted according to the IP address of the main router, and the information is sent to the interconnecting board of the main router via the interconnecting board of the router, and the original inter-board communication mode is used by the interconnecting board of the main router. The above information is sent to the main control board of the main router.
  • Step 304 All routers in the cluster combine the received iFIB and eFIB to obtain their own forwarding information base.
  • the router cluster shown in Figure 2 is still taken as an example. Assume that R1 obtains such a message when generating eFIB: Go to network A, the next hop is R4, and the outbound interface is Ethl/1. Rl will include this one. When the eFIB of the information is sent to R2 and R3, the information that the cluster interface is located at R1 is also attached.
  • R2 receives this eFIB, extracts the outbound interface location to Rl, and then queries its own iFIB to get to R1, the next hop IP address is IP12, and the outbound interface is Eth2/1, thus realizing the merger of iFIB and eFIB. That is: Go to network A, the next hop address is IP12, and the outbound interface is Eth2/1.
  • the FIB obtained by combining iFIB and eFIB in R3 is: Go to network A, the next hop IP address is IP13, and the outbound interface is Eth3/1.
  • the following steps may be included: If the router in the cluster receives the data to be forwarded, according to the destination address of the data to be forwarded, obtain the router where the router belongs to the destination interface corresponding to the destination address in the FIB. The routing information is forwarded to the destination address according to the routing information.
  • the embodiment of the invention provides a method for obtaining a router cluster forwarding information base, which obtains an internal forwarding information base and an external forwarding information base by each node, and combines the obtained internal forwarding information base with an external forwarding information base to obtain a router. Forwarding information base. No additional central switch chassis is required, and each router does not require an additional interface to connect to the central switch chassis to obtain a forwarding information base, which saves software and hardware costs.
  • FIG. 4 is a schematic structural diagram of a router in a cluster according to an embodiment of the present invention.
  • the router includes: an obtaining module 401 and a merging module 402.
  • the obtaining module 401 is configured to obtain an internal forwarding information base and an external forwarding information base, where the internal forwarding information base includes: routing information from one router in the cluster to another router in the cluster; the external forwarding information base includes: Routing information from the router where the cluster interface resides to the network outside the cluster.
  • the merging module 402 is configured to obtain, according to the outbound interface information in the external forwarding information base, the router where the outbound cluster interface is located, obtain routing information of the router to which the cluster interface is located, and forward the information database to the external forwarding information base.
  • the destination address corresponding to the cluster interface information and the routing information of the internal forwarding information base to the router where the cluster interface is located are merged into a forwarding information base.
  • the router that is required to be protected by the embodiment of the present invention is a primary router in the cluster
  • the obtaining module 401 includes at least: an external forwarding information base generating unit.
  • the external forwarding information base generating unit is configured to obtain first routing information that is connected to the cluster interface of the cluster interface according to the dynamic routing protocol, and receive second routing information that is sent from the router and that is connected to the outbound cluster interface.
  • a routing information and a second routing information generate an external forwarding information base.
  • the router claimed in the embodiment of the present invention is a slave router in the cluster, and the obtaining module 401 is configured to receive an internal forwarding information base and an external forwarding information base sent by the primary router in the cluster.
  • FIG. 5 is a schematic structural diagram of a router in a cluster according to another embodiment of the present invention; and further includes: a forwarding module 403.
  • the forwarding module 403 is configured to obtain, according to the destination address of the to-be-forwarded data, the routing information of the router where the router belongs to the destination interface corresponding to the destination address, according to the routing information, according to the destination address of the data to be forwarded. Forward the data to be forwarded to the destination address.
  • An embodiment of the present invention provides a router in a cluster, which obtains an internal forwarding information base and an external forwarding information base by each node, and combines the obtained internal forwarding information base with an external forwarding information base to obtain a forwarding information base of the router. . No additional central switch chassis is required, and each router does not require an additional interface to connect to the central switch chassis to obtain a forwarding information base, which saves software and hardware costs.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes the steps of the foregoing method embodiment; and the foregoing storage medium includes: ROM, RAM , a variety of media that can store program code, such as a disk or an optical disk.

Abstract

本发明提供一种路由器集群转发信息库(FIB)的获得方法及路由器。方法包括:路由器集群中的路由器获得内部FIB(iFIB)和外部FIB(eFIB),其中iFIB包括从集群内的一个路由器去往集群内的另一个路由器的路由信息,eFIB包括从集群内出集群接口所在的路由器去往集群外的网络的路由信息;路由器将iFIB和eFIB合并为路由器的FIB。路由器包括:获得模块和合并模块。

Description

路由器集群转发信息库的获得方法及路由器 技术领域
本发明实施例涉及路由器技术领域, 尤其涉及一种路由器集群转发信息 库的获得方法及路由器。
背景技术
随着互联网的不断发展, 路由器集群技术应运而生。 所谓路由器集群, 就是将多台物理上独立的路由器互联起来, 形成一套逻辑上一体的路由器系 统。每一台独立的路由器都被集中统一地管理起来,操作上如同一台路由器, 极大地简化了设备的运行和维护。
现有的路由器集群形态, 通常需要通过一个特定的中央交换框将多个独 立的路由器以星形拓朴互连, 路由器集群的集中控制和管理也都位于中央交 换框中。
在实现本发明过程中, 发明人发现现有技术中至少存在如下问题: 路由器集群的转发信息库 (Forwarding Information Base, 简称为: FIB ) 保存在中央交换框中, 每一台路由器需要特定的接口与中央交换框进行通信 以获得 FIB后方能实现数据的路由, 软件和硬件投入的成本较高。 发明内容
本发明实施例提供一种路由器集群转发信息库的获得方法及路由器, 用以 解决现有技术中路由器集群需要单独的中央交换框, 且每一台路由器都需要额 外的端口与中央交换框相连, 成本较高的问题。
本发明实施例提供一种路由器集群转发信息库的获得方法, 包括: 路由器集群中的路由器获得内部转发信息库和外部转发信息库, 所述内部 转发信息库包括: 从所述集群内的一个路由器去往所述集群内的另一个路由器 的路由信息; 所述外部转发信息库包括: 从所述集群内出集群接口所在的路由 器去往所述集群外的网络的路由信息;
所述路由器根据所述外部转发信息库中的出集群接口信息, 获得该出集群 接口所在的路由器; 在所述内部转发信息库中获得去往所述出集群接口所在的 路由器的路由信息; 将所述外部转发信息库中所述出集群接口信息对应的目的 地址、 所述内部转发信息库中去往所述出集群接口所在的路由器的路由信息合 并为转发信息库。 。
本发明实施例还提供了一种集群中的路由器, 包括:
获得模块, 用于获得内部转发信息库和外部转发信息库, 所述内部转发信 息库包括: 从所述集群内的一个路由器去往所述集群内的另一个路由器的路由 信息; 所述外部转发信息库包括: 从所述集群内出集群接口所在的路由器去往 所述集群外的网络的路由信息;
合并模块, 用于根据所述外部转发信息库中的出集群接口信息, 获得该出 集群接口所在的路由器, 在所述内部转发信息库中获得去往所述出集群接口所 在的路由器的路由信息, 将所述外部转发信息库中所述出集群接口信息对应的 目的地址、 所述内部转发信息库中去往所述出集群接口所在的路由器的路由信 息合并为所述转发信息库。
本发明实施例的路由器集群转发信息库的获得方法及路由器, 通过由各节 点获得内部转发信息库与外部转发信息库, 并将获得的内部转发信息库与外部 转发信息库进行合并, 得到路由器的转发信息库。 不再需要额外的中央交换框, 各路由器不需要额外的接口与中央交换框连接获取转发信息库, 节约了软件和 硬件的成本。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实施 例或现有技术描述中所需要使用的附图作一简单地介绍, 显而易见地, 下面描 述中的附图是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出 创造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明一个实施例提供的路由器集群转发信息库的获得方法流程图; 图 2为本发明又一个实施例提供的路由器集群形态示意图;
图 3 为本发明又一个实施例提供的路由器集群转发信息库的获得方法流程 图;
图 4为本发明一个实施例提供的集群中的路由器的结构示意图; 图 5为本发明又一个实施例提供的集群中的路由器的结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发明 实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于本发明中 的实施例, 本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其 他实施例, 都属于本发明保护的范围。
图 1为本发明一个实施例提供的路由器集群转发信息库的获得方法流程图, 如图 1所示, 该方法包括:
步骤 101 : 集群中的路由器获得内部转发信息库 (Internal Forwarding Information Base , 简称为: iFIB ) 和外部转发信息库 (External Forwarding Information Base, 简称为: eFIB ) ;
其中的 iFIB可以包括: 从该集群内的一个路由器去往集群内的另一个路由 器的路由信息。 eFIB 可以包括: 从集群内出集群接口所在路由器去往集群外的 网络的路由信息。
当本路由器为主路由器时, 步骤 101 可以为: 主路由器接收操作人员输入 的信息生成 iFIB, 并根据动态路由协议获得与自身出集群接口相连的第一路由 信息, 接收具有出集群接口的从路由器发送的与其出集群接口相连的第二路由 信息, 根据第一路由信息和第二路由信息生成 eFIB。 其中, 根据第一路由信息 和第二路由信息生成 eFIB的过程可以但不限于包括从多条路由中选择最优路由 的过程。
当本路由器为从路由器时, 步骤 101可以为: 接收主路由器发送的 iFIB和 eFIB。
步骤 102: 路由器将 iFIB和 eFIB合并为本路由器的 FIB。
其中, 将 iFIB与 eFIB合并的过程可以理解为: 根据 eFIB中的出集群接口 信息, 获得该出集群接口所在的路由器。 在 iFIB中获得去往该出集群接口所在 的路由器的路由信息, 将 eFIB中该出集群接口信息对应的目的地址、 iFIB中去 往该出集群接口所在的路由器的路由信息合并为转发信息库。
图 2 为本发明又一个实施例提供的路由器集群形态示意图, 假设将路由器 Rl、 R2和 R3组建为一个路由器集群。 各路由器的配置可以如表 1所示:
表 1
Figure imgf000005_0001
图 3为本发明又一个实施例提供的路由器集群转发信息库的获得方法流程 图。 该方法是以图 2所示的路由器集群形态为基础进行说明的, 不用以限制本 发明的保护范围。
需要说明的是, 框式路由器一般由多块板卡组成, 其中包括一块主控板和 若干块接口板。 主控板负责控制、 管理框内的接口板。 主控板通过板间通信向 接口板下发配置、 转发表等信息, 同时也收集接口板的状态信息。 这些板卡经 由背板连接到一个高速以太网中, 形成板间通信的物理通路。 软件上, 每块板 卡被分配一个板卡号 (也可以成为槽位号) , 主控板如果要给某接口板发送数 据, 只需要提供目的板卡的板卡号, 便能将数据经由上述高速以太网发送至目 的板卡。
步骤 301 : 组建路由器集群的路由器接收集群组建命令, 根据集群组建命令 建立路由器集群, 并区分主路由器和从路由器;
该组建命令中携带的参数包括: 组成一个路由器集群的所有路由器的节点 标识, 如路由器 1、 路由器 2、 路由器 3 , 或者 Rl、 R2、 R3等等, 任意一种可 以区分各路由器的标识均可以使用。 在集群组建成功后, 主路由器获得路由器 集群中其他路由器的节点标识和 IP地址。 路由器集群中的其他路由器获得主路 由器的节点标识和 IP地址。
这里以 R1为主路由器, R2和 R3为从路由器为例进行说明。需要说明的是, 主路由器 R 1在作为主路由器执行其功能时,也同样作为自身的从路由器在工作。
需要说明的是, 本发明实施例所提供的路由器集群使用的是路由器上普通 的数据接口进行互联的。 数据报文和集群内的控制报文共享同一接口 /链路。 因 此, 在组建数据报文拓朴之后, 集群的拓朴互联也天然地形成了, 无需额外的 设备和组网工作, 只需指定某几台路由器加入集群, 并任命某路由器为集群的 主路由器即可。 主路由器的主控板可集中管理集群中的所有接口板。 在这种情 况下, 集群内某个路由器框内的主控板和接口板之间仍由框内以太网进行互联, 可使用原有的板间通信机制。 但主路由器的主控板与从路由器的接口板之间没 有这种互联机制, 跨框的板间通信依赖的是 IP地址。
步骤 302: 主路由器生成集群 iFIB并下发给集群内的全部路由器, 全部路 由器接收主路由器发送的 iFIB;
主路由器可以根据操作人员的输入信息生成 iFIB。 iFIB 中包含了从集群内 的一个路由器去往集群内另一个路由器的路由信息。 iFIB 中可以但不限于包括 如表 2所示的信息: 表 2
Figure imgf000007_0001
需要说明的是, 主路由器将 iFIB下发给集群内的全部路由器可以通过如下 方法实现: 主路由器根据目的板卡所在路由器的 IP地址, 将 iFIB发送给目的路 由器的内连板, 由目的路由器的内连板使用原有的板间通信方式将 iFIB发送给 目的板卡。 这样, 每个路由器只需要有一个 IP地址即可实现跨框的通信。 需要 的说明的是, 内连板可以是接口板, 也可以是主控板, 内连板可以是预先指定 的。
步骤 303: 主路由器生成集群 eFIB并下发给集群内的全部路由器, 全部路 由器接收主路由器发送的 eFIB;
主路由器可以通过动态路由协议获得与自身出集群接口相连的第一路由信 息, 从路由器可以通过动态路由协议获得与其出集群接口相连的第二路由信息 并发送给主路由器的主控板, 主路由器的主控板根据获得的第一路由信息和接 收到的第二路由信息生成 eFIB。 eFIB中包含了集群内的出集群接口所在的路由 器去往集群外网络的路由信息,但不包含去往集群内各路由器的路由信息。 eFIB 中可以但不限于包括如表 3所示的信息:
表 3
Figure imgf000007_0002
对于 eFIB的生成方式做如下解释: 集群内具有出集群接口的路由器(既可 以是主路由器, 又可以是从路由器)根据动态路由协议, 获得与自身的出集群 接口相连的路由信息, 其中可以但不限于包括路由器自身的 IP地址、 掩码、 出 集群接口和下一跳地址传递至主路由器的主控板。 上述信息的传递过程可以为: 根据主路由器的 IP地址, 将上述信息经由从路由器的内连板发送至主路由器的 内连板, 由主路由器的内连板使用原有的板间通信方式将上述信息发送给主路 由器的主控板。
步骤 304: 集群内的全部路由器将接收到的 iFIB和 eFIB进行合并, 得到自 身的转发信息库。
仍以图 2所示的路由器集群为例进行具体说明: 假设 R1在生成 eFIB时, 获得这样一条信息: 去往网络 A, 下一跳为 R4, 出接口为 Ethl/1 , Rl将包含这 条信息的 eFIB发送给 R2和 R3时, 还附加了出集群接口位于 R1这样的信息。
R2接收到此 eFIB, 提取到出接口位置为 Rl , 然后查询自己的 iFIB, 得到去往 R1 , 下一跳 IP地址为 IP12, 出接口为 Eth2/1 , 这样就实现了 iFIB与 eFIB的合 并, 即: 去往网络 A, 下一跳地址为 IP12, 出接口为 Eth2/1。 同理, R3中 iFIB 与 eFIB合并后得到的 FIB为: 去往网络 A, 下一跳 IP地址为 IP13 , 出接口为 Eth3/1。
在步骤 304之后, 还可以包括可选的步骤: 如果集群中的路由器接收到待 转发数据, 根据待转发数据的目的地址, 在 FIB 中获得本路由器去往目的地址 对应的出集群接口所在的路由器的路由信息, 根据该路由信息将待转发数据转 发至目的地址。
本发明实施例提供了一种路由器集群转发信息库的获得方法, 通过由各节 点获得内部转发信息库与外部转发信息库, 并将获得的内部转发信息库与外部 转发信息库进行合并, 得到路由器的转发信息库。 不再需要额外的中央交换框, 各路由器不需要额外的接口与中央交换框连接获取转发信息库, 节约了软件和 硬件的成本。
图 4为本发明一个实施例提供的集群中的路由器的结构示意图。 如图 4所 示, 该路由器包括: 获得模块 401和合并模块 402。 其中, 获得模块 401用于获 得内部转发信息库和外部转发信息库, 该内部转发信息库包括: 从集群内的一 个路由器去往集群内的另一个路由器的路由信息; 该外部转发信息库包括: 从 集群内出集群接口所在的路由器去往集群外的网络的路由信息。 合并模块 402 用于根据外部转发信息库中的出集群接口信息, 获得该出集群接口所在的路由 器, 在内部转发信息库中获得去往出集群接口所在的路由器的路由信息, 将外 部转发信息库中所述出集群接口信息对应的目的地址、 内部转发信息库中去往 出集群接口所在的路由器的路由信息合并为转发信息库。
一种实施方式下,本发明实施例要求保护的路由器为集群中的主路由器, 该获得模块 401至少包括: 外部转发信息库生成单元。 该外部转发信息库生 成单元用于根据动态路由协议获得与自身出集群接口相连的第一路由信息, 并接收具有出集群接口的从路由器发送的与其出集群接口相连的第二路由信 息, 根据第一路由信息和第二路由信息生成外部转发信息库。
另一种实施方式下, 本发明实施例要求保护的路由器为集群中的从路由 器, 该获得模块 401用于接收集群中主路由器发送的内部转发信息库和外部 转发信息库。
进一步的, 图 5为本发明又一实施例提供的集群中的路由器的结构示意 图; 还可以包括: 转发模块 403。 该转发模块 403用于如果接收到待转发数 据, 根据该待转发数据的目的地址, 在转发信息库中获得本路由器去往目的 地址对应的出集群接口所在的路由器的路由信息, 根据该路由信息将待转发 数据转发至目的地址。
本发明实施例提供了一种集群中的路由器, 通过由各节点获得内部转发信 息库与外部转发信息库, 并将获得的内部转发信息库与外部转发信息库进行合 并, 得到路由器的转发信息库。 不再需要额外的中央交换框, 各路由器不需要 额外的接口与中央交换框连接获取转发信息库, 节约了软件和硬件的成本。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤可 以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读取存 储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述的存储 介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其 限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通技术 人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修改, 或 者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求
1、 一种路由器集群转发信息库的获得方法, 其特征在于, 包括:
路由器集群中的路由器获得内部转发信息库和外部转发信息库, 所述内部 转发信息库包括: 从所述集群内的一个路由器去往所述集群内的另一个路由器 的路由信息; 所述外部转发信息库包括: 从所述集群内出集群接口所在的路由 器去往所述集群外的网络的路由信息;
所述路由器根据所述外部转发信息库中的出集群接口信息, 获得该出集群 接口所在的路由器; 在所述内部转发信息库中获得去往所述出集群接口所在的 路由器的路由信息; 将所述外部转发信息库中所述出集群接口信息对应的目的 地址、 所述内部转发信息库中去往所述出集群接口所在的路由器的路由信息合 并为转发信息库。
2、根据权利要求 1所述的方法,其特征在于, 当所述路由器为主路由器时, 所述获得外部转发信息库包括:
所述主路由器根据动态路由协议获得与自身出集群接口相连的第一路由信 息, 并接收具有出集群接口的从路由器发送的与其出集群接口相连的第二路由 信息, 根据所述第一路由信息和所述第二路由信息生成外部转发信息库。
3、根据权利要求 2所述的方法, 其特征在于, 所述接收具有出集群接口的 从路由器发送的与其出集群接口相连的第二路由信息, 包括:
所述主路由器的内连板接收所述具有出集群接口的从路由器根据所述主路 由器的 IP地址发送的第二路由信息;
所述主路由器的内连板将接收到的第二路由信息发送给所述主路由器的主 控板。
4、根据权利要求 1所述的方法,其特征在于, 当所述路由器为从路由器时, 所述获得内部转发信息库和外部转发信息库包括:
所述从路由器接收主路由器发送的内部转发信息库和外部转发信息库。
5、根据权利要求 4所述的方法, 其特征在于, 当所述路由器为具有出集群 接口的从路由器时, 所述方法还包括:
所述从路由器根据动态路由协议获得与自身出集群接口相连的第二路由信 息, 并将得到的第二路由信息发送给主路由器。
6、根据权利要求 5所述的方法, 其特征在于, 所述将得到的第二路由信息 发送给主路由器, 包括:
所述从路由器根据主路由器的 IP地址,将所述获得的第二路由信息经由自 身的内连板发送给所述主路由器的内连板, 所述主路由器的内连板将接收到的 第二路由信息传递至所述主路由器的主控板。
7、根据权利要求 1至 6中任一项所述的方法, 其特征在于, 所述将所述内 部转发信息库和所述外部转发信息库合并为路由器的转发信息库之后, 所述方 法还包括:
如果所述路由器接收到待转发数据, 根据所述待转发数据的目的地址, 在 所述转发信息库中获得所述路由器去往所述目的地址对应的出集群接口所在的 路由器的路由信息, 根据所述路由信息将所述待转发数据转发至目的地址。
8、 一种集群中的路由器, 其特征在于, 包括:
获得模块, 用于获得内部转发信息库和外部转发信息库, 所述内部转发信 息库包括: 从所述集群内的一个路由器去往所述集群内的另一个路由器的路由 信息; 所述外部转发信息库包括: 从所述集群内出集群接口所在的路由器去往 所述集群外的网络的路由信息;
合并模块, 用于根据所述外部转发信息库中的出集群接口信息, 获得该出 集群接口所在的路由器, 在所述内部转发信息库中获得去往所述出集群接口所 在的路由器的路由信息, 将所述外部转发信息库中所述出集群接口信息对应的 目的地址、 所述内部转发信息库中去往所述出集群接口所在的路由器的路由信 息合并为所述转发信息库。
9、根据权利要求 8所述的路由器, 其特征在于, 当所述路由器为主路由器 时, 所述获得模块至少包括: 外部转发信息库生成单元, 用于根据动态路由协议获得与自身出集群接口 相连的第一路由信息, 并接收具有出集群接口的从路由器发送的与其出集群接 口相连的第二路由信息, 根据所述第一路由信息和所述第二路由信息生成外部 转发信息库。
10、 根据权利要求 8所述的路由器, 其特征在于, 当所述路由器为从路由 器时, 所述获得模块用于接收主路由器发送的内部转发信息库和外部转发信息 库。
11、 根据权利要求 8至 10任一项所述的路由器, 其特征在于, 所述路由器 还包括:
转发模块, 用于如果接收到待转发数据, 根据所述待转发数据的目的地 址,在所述转发信息库中获得本路由器去往所述目的地址对应的出集群接口 所在的路由器的路由信息,根据所述路由信息将所述待转发数据转发至目的 地址。
PCT/CN2011/074055 2011-05-13 2011-05-13 路由器集群转发信息库的获得方法及路由器 WO2011124183A2 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/074055 WO2011124183A2 (zh) 2011-05-13 2011-05-13 路由器集群转发信息库的获得方法及路由器
CN2011800006695A CN102204189A (zh) 2011-05-13 2011-05-13 路由器集群转发信息库的获得方法及路由器

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/074055 WO2011124183A2 (zh) 2011-05-13 2011-05-13 路由器集群转发信息库的获得方法及路由器

Publications (2)

Publication Number Publication Date
WO2011124183A2 true WO2011124183A2 (zh) 2011-10-13
WO2011124183A3 WO2011124183A3 (zh) 2012-04-19

Family

ID=44662811

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/074055 WO2011124183A2 (zh) 2011-05-13 2011-05-13 路由器集群转发信息库的获得方法及路由器

Country Status (2)

Country Link
CN (1) CN102204189A (zh)
WO (1) WO2011124183A2 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103166859B (zh) * 2011-12-14 2016-08-03 中国电信股份有限公司 业务路由方法及系统
CN104618248A (zh) * 2015-01-27 2015-05-13 首都师范大学 集群路由器多播转发表设计与转发算法
CN114928589B (zh) * 2022-03-17 2024-04-12 京东科技信息技术有限公司 数据传输方法、数据传输装置、计算机可读介质及设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227405A (zh) * 2008-02-18 2008-07-23 中兴通讯股份有限公司 路由汇聚方法及系统
CN101931587A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 虚拟集群路由方法及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227405A (zh) * 2008-02-18 2008-07-23 中兴通讯股份有限公司 路由汇聚方法及系统
CN101931587A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 虚拟集群路由方法及系统

Also Published As

Publication number Publication date
WO2011124183A3 (zh) 2012-04-19
CN102204189A (zh) 2011-09-28

Similar Documents

Publication Publication Date Title
US10382315B2 (en) Framework for universally specified affinity topologies with partial path invalidation and generalized network flows
US9065768B2 (en) Apparatus for a high performance and highly available multi-controllers in a single SDN/OpenFlow network
EP2974133B1 (en) Method and system for controlling an underlying physical network by a software defined network
JP4714750B2 (ja) ハードウェア抽象化レイヤ
US9130870B1 (en) Methods for determining network topologies
EP2962431B1 (en) Spanning tree in fabric switches
US10237179B2 (en) Systems and methods of inter data center out-bound traffic management
JP6384696B2 (ja) 転送テーブル同期方法、ネットワークデバイスおよびシステム
US9515927B2 (en) System and method for layer 3 proxy routing
JP2017506025A (ja) ネットワークサービス挿入を実行するシステム及び方法
JP5488979B2 (ja) コンピュータシステム、コントローラ、スイッチ、及び通信方法
EP3069471B1 (en) Optimized multicast routing in a clos-like network
JP2007166666A (ja) ネットワーク管理のための方法とシステム
JP5455139B2 (ja) マルチキャストパケットを処理するための方法及び装置
WO2007041919A1 (fr) Méthode et système d’implémentation de vrrp sur le rpr
WO2011113394A2 (zh) 一种路由器、虚拟集群路由器系统及建立方法
RU2513918C1 (ru) Кластерный маршрутизатор и способ кластерной маршрутизации
WO2014121468A1 (zh) 在网络虚拟化系统中组播数据通道建立的方法及设备
WO2017113929A1 (zh) 一种软件定义网络中控制转发设备集群的方法及控制器
WO2010069382A1 (en) Method and apparatus for transferring data packets between a first network and a second network
WO2017185780A1 (zh) 转发表项建立方法和装置
JP7357123B2 (ja) 直接相互接続ゲートウェイ
EP2892196B1 (en) Method, network node and system for implementing point-to-multipoint multicast
WO2016019676A1 (zh) 一种软件定义网络sdn中处理数据包的方法、装置及系统
WO2011124183A2 (zh) 路由器集群转发信息库的获得方法及路由器

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000669.5

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11765101

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11765101

Country of ref document: EP

Kind code of ref document: A2