WO2012149849A1 - 将mstp中的桥加入域的方法、系统及交换机 - Google Patents
将mstp中的桥加入域的方法、系统及交换机 Download PDFInfo
- Publication number
- WO2012149849A1 WO2012149849A1 PCT/CN2012/073477 CN2012073477W WO2012149849A1 WO 2012149849 A1 WO2012149849 A1 WO 2012149849A1 CN 2012073477 W CN2012073477 W CN 2012073477W WO 2012149849 A1 WO2012149849 A1 WO 2012149849A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- domain
- mstp
- domain information
- bridge
- downstream
- 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.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/48—Routing tree calculation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/18—Loop-free operations
Definitions
- the present invention relates to network communication technologies, and in particular, to a method, system, and switch for joining a bridge in a multiple spanning tree protocol (MSTP) to a domain.
- MSTP Spanning Tree Protocol
- BPDU Bridge Protocol Data Unit
- the Spanning Tree Protocol When a network fails, the Spanning Tree Protocol recalculates the congestion point and releases the redundant link to recover network traffic.
- the STP network calculates only one spanning tree. All the virtual local area networks (VLANs) are forwarded according to a spanning tree. Load balancing cannot be implemented.
- VLANs virtual local area networks
- MSTP divides a switched network into multiple domains. Generally, switches in a geographical area are divided into the same domain. The instances are divided into different virtual local area networks (VLANs) in the domain, and each instance calculates the spanning tree separately. Therefore, multiple spanning trees can be formed in each domain. Each spanning tree is called a multiple spanning tree instance (MSTI). By setting a VLAN mapping table, VLANs and MSTIs can be associated. Different MSTIs can be calculated according to the calculation. The spanning tree topology forwards the traffic of the VLANs in the instance. The load balancing of the spanning tree in the domain can be implemented through the different topologies of the spanning tree.
- VLANs virtual local area networks
- the embodiments of the present invention provide a method, a system, and a switch for adding a bridge in an MSTP to a domain, which are used to solve the problem of large workload, difficult deployment, and high operation and maintenance cost in the prior art.
- a method for adding a bridge in an MSTP to a domain includes: The root bridge in the MSTI of the multiple spanning tree instance to be generated obtains the MSTP domain information.
- the root bridge After the domain information of the MSTP is configured on the root bridge, the root bridge sends a domain join message to the downstream bridge, where the domain join message carries the domain information of the MSTP, and is used to enable the downstream bridge.
- the domain information of the MSTP is configured as domain information of the downstream bridge.
- a method for adding a bridge in an MSTP to a domain according to another aspect of the present invention includes:
- the downstream bridge receives the domain join message sent by the upstream node, and the domain join message carries the domain information of the MSTP; the downstream bridge configures the domain information of the MSTP with the domain information of the cost machine.
- a switch provided in another aspect of the present invention includes:
- An obtaining module configured to obtain domain information of a multi-spanning tree protocol MSTP;
- a sender configured to send the domain join message to the downstream bridge after the domain information of the MSTP is configured on the switch, where the domain join message carries the domain information of the MSTP, and is used to enable the downstream bridge
- the domain information of the MSTP is configured as domain information of the downstream bridge.
- a fourth aspect of the invention provides a switch, including:
- a receiver configured to receive a domain join message sent by the upstream node, where the domain join message carries the domain information of the multiple spanning tree protocol MSTP;
- a configuration module configured to configure domain information of the MSTP to domain information of the cost machine.
- the embodiment of the invention provides a network system, including:
- the root bridge is configured to send the obtained MSTP domain information to the downstream bridge.
- a downstream bridge configured to configure domain information of the MSTP as domain information of the downstream bridge.
- the embodiment of the present invention sends a domain join message to the downstream bridge through the total root bridge, and the domain join message carries the domain information, which can implement automatic configuration of the domain information, and the downstream bridge is automatically added to the corresponding domain.
- the domain join message carries the domain information, which can implement automatic configuration of the domain information, and the downstream bridge is automatically added to the corresponding domain.
- FIG. 1 is a schematic flow chart of a method according to a first embodiment of the present invention
- FIG. 2 is a schematic structural diagram of an intra-domain bridge in an embodiment of the present invention
- 3 is a schematic flow chart of a method according to a second embodiment of the present invention
- FIG. 4 is a schematic flow chart of a method according to a third embodiment of the present invention.
- FIG. 5 is a schematic flowchart of a method according to a fourth embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of a switch according to a fifth embodiment of the present invention.
- FIG. 7 is a schematic structural diagram of a switch according to a sixth embodiment of the present invention.
- FIG. 8 is a schematic structural diagram of a network system according to a seventh embodiment of the present invention.
- the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention.
- the embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
- FIG. 1 is a schematic flowchart of a method according to a first embodiment of the present invention
- FIG. 2 is a schematic structural diagram of an intra-domain bridge in an embodiment of the present invention.
- the name of the domain is Campus (CAMPUS), which includes four switches, SW-1, SW-2, SW-3, and SW-4.
- the switch can be divided into a root bridge and a downstream bridge (or a designated bridge) according to the role.
- SW-1 is the root bridge
- other switches are downstream bridges.
- MSTP multiple spanning trees can be generated in the same domain. Each spanning tree is called an MSTI.
- Each MSTI corresponds to one root bridge and at least one downstream bridge. Among them, the root bridge can be determined in a competitive manner (or called an election method) within each MSTI.
- the network topology is established, the tree is generated from the root bridge.
- the BPDUs are sent from the root bridge to the downstream bridge.
- this embodiment includes:
- Step 11 The root bridge in the MSTI to be generated obtains the MSTP domain information.
- the root bridge obtains the MSTP domain information and implements MSTP domain information on the root bridge.
- MSTP domain information can be represented by REGION-CONFIG, which is a triple consisting of three parameters: domain name (REGION_NAME), instance (REGION_INSTANCE), and revision level ( REGION — LEVEL).
- the domain name can indicate the name of the joined domain.
- the instance can indicate the list of VLANs corresponding to each instance in the domain and the configured instances.
- the revision level is reserved by the standard and the default value is 0.
- Table 1 Table 1
- Step 12 After the domain information of the MSTP is configured on the root bridge, the root bridge sends a domain join message to the downstream bridge, where the domain join message carries the domain information of the MSTP, and is used to The downstream bridge configures the domain information of the MSTP as domain information of the downstream bridge.
- the root bridge sends the domain join message through the MSTP port.
- the join message of the domain first reaches the downstream bridge directly connected to the root bridge. Then, the downstream bridge sends the domain join message to the last one. Downstream bridge.
- the SW-1 sends a domain join message to the SW-2.
- the SW-2 can configure the domain information of the MSTP carried in the domain as its own domain information, and implement the domain corresponding to the domain information. .
- the domain name may be set in advance on each downstream bridge.
- the downstream bridge receives the domain join message, it determines whether the domain name in the received MSTP domain information is the same as the domain name configured by itself.
- the MSTP domain information is configured as its own domain information. If it is different, it is not configured.
- the root bridge sends a domain join message to the downstream bridge, and the domain join message carries the domain information, so that the domain information can be automatically configured, so that the downstream bridge can be automatically added to the corresponding domain to avoid manual configuration.
- FIG. 3 is a schematic flowchart of a method according to a second embodiment of the present invention, including:
- Step 31 The downstream bridge receives the domain join message sent by the upstream node, where the domain join message carries the MSTP domain information.
- SW-2 receives the domain join message sent by SW-1; or SW-4 receives the domain join message sent by SW-2.
- the MSTP domain information can be represented by REGION_CONFIG, which is a triple consisting of three parameters: domain name (REGION_NAME), instance (REGION_INSTANCR), and revision level ( REGION — LEVEL).
- Step 32 The downstream bridge configures the domain information of the MSTP to the domain information of the cost machine.
- the downstream bridge configures the domain information of the MSTP to the domain information of the virtual machine.
- the domain name is pre-configured in the downstream bridge.
- the MSTP domain information is compared. If the domain name is the same as the domain name configured by itself, if the domain name is the same, configure the domain information of the MSTP domain information. Otherwise, the configuration is not performed.
- the downstream bridge continues to send the domain join message to its own downstream node until the last node in the domain, and the domain join message carries the domain information of the MSTP, so as to be downstream.
- the node configures the domain information of the MSTP as its own domain information.
- the downstream bridge receives the domain join message sent by the root bridge, and the domain information of the MSTP carried in the packet is configured to configure the domain information of the virtual machine, so that the domain information can be automatically configured, and then automatically added to the domain information.
- the corresponding domain which is the domain in which the root bridge is located.
- all the bridges that the domain joins the packet to join in the MSTP network are added to the domain where the root bridge resides, to avoid the large workload, difficult deployment, and operation and maintenance costs. High problem.
- FIG. 4 is a schematic flowchart of a method according to a third embodiment of the present invention, including:
- Step 41 The root bridge (using SW-1 as an example) starts the domain join function.
- the switch in the domain where the MSTI is located can determine the root bridge and the downstream bridge through competition.
- Each exchange opportunity in the MSTP network corresponds to a default domain, and the corresponding domain can be divided according to the geographical location of the switch. For example, if the first geographic location corresponds to the first domain, if the first switch and the second switch are both in the range of the first geographic location, the default domain of the first switch and the second switch is the first domain. After the first switch is started, the two switches will exchange BPDUs to compete for the root bridge.
- the specific competition process may be: Each switch corresponds to a bridge ID, and the bridge ID includes a priority. When the priority of the bridge ID of a switch is the highest (the corresponding priority value is the smallest), the switch is the root bridge. . Each switch exchanges BPDUs, and the corresponding BPDUs carry their own bridge IDs. By comparing the bridge IDs, the switch corresponding to the bridge ID with the highest priority is determined as the root bridge. Taking Figure 2 as an example, the root bridge is SW-1.
- Step 42 The root bridge sends the domain join message to the downstream node (for example, SW-2) through the MSTP port.
- the domain join message carries the MSTP domain information.
- Step 43 SW-2 reports the received domain join message to its own CPU, and refreshes the domain information configured by itself by using the MTSP domain information carried in the domain join message.
- the switch directly forwards the packet and does not report the packet to the CPU.
- the domain join message needs to be parsed. Therefore, in this embodiment, the domain join message will reach the CPU, and the CPU parses and obtains the MSTP domain information, and then the MSTP.
- the domain information is configured into its own domain information, that is, the domain information is refreshed.
- Step 44 SW-2 sends a domain join message to its downstream node (SW-4), which carries the MSTP domain information. Similar to the processing of the SW-2, after receiving the domain join message, the SW-4 configures the domain information of the MSTP carried in the field as its own domain information to be added to the domain to which the root bridge belongs.
- SW-4 sends a domain join message to its downstream node (SW-4), which carries the MSTP domain information. Similar to the processing of the SW-2, after receiving the domain join message, the SW-4 configures the domain information of the MSTP carried in the field as its own domain information to be added to the domain to which the root bridge belongs.
- all the bridges in the same domain can join the domain by obtaining the MSTP domain information in the domain join message and passing the domain join message.
- the root bridge sends a domain join message to the downstream bridge, and the domain join message carries the domain information, which can implement the automatic configuration of the domain information, and obtain the MSTP domain information in the domain join message to implement automatic joining of the downstream bridge. Corresponding domain.
- all the bridges in the same domain can be added to the domain to avoid the problems of large workload, difficult deployment, and high operation and maintenance cost.
- FIG. 5 is a schematic flowchart of a method according to a fourth embodiment of the present invention.
- a new switch is added as an example. Referring to FIG. 5, this embodiment includes:
- Step 51 The newly added switch SW-5 sends a BPDU packet to the upstream node SW-4 connected to it.
- SW-5 (not shown), and SW-5 is connected to SW-4, SW-5 sends a BPDU packet to SW-4, and the BPDU packet will be Carry the bridge ID of SW-5.
- Step 52 The upstream node SW-4 reports and parses the BPDU.
- the reporting and parsing process is reported to the CPU by the forwarding module and parsed by the CPU.
- the bridge ID of SW-5 can be obtained through parsing. If the priority in the bridge ID is lower than the priority of SW-4, it indicates that SW-5 is the downstream node of SW-4, and at this time, the BPDU sent by SW-5
- the packet is an inferior BPDU, that is, a BPDU with a lower priority. That is, the BPDU sent by the downstream node to the upstream node is called the inferior BPDU.
- the high priority value in the bridge ID indicates that the corresponding switch has a lower priority.
- Step 53 When the B-4 packet is determined to be an inferior BPDU packet, the SW-4 sends a response BPDU packet to the SW-5.
- Step 54 When the B-4 packet is determined to be a secondary BPDU, the SW-4 sends a domain join message to the SW-5, where the MSTP domain information is carried.
- the SW-5 After receiving the join message of the domain, the SW-5 can configure the MSTP domain information as its own domain information.
- the newly added switch of the root bridge sends the domain join message carrying the domain information, and newly joins the switch solution.
- the packet is parsed, and the domain information of the domain of the root bridge carried in the domain join message is used as the domain information of the root bridge.
- the newly added switch can also be added to the domain to which the root bridge belongs.
- FIG. 6 is a schematic structural diagram of a switch according to a fifth embodiment of the present invention.
- the switch may be a root bridge of an MSTI to be generated, and the switch includes an obtaining module 61 and a transmitter 62.
- the acquiring module 61 is configured to acquire domain information of the MSTP.
- the device 62 is configured to: after the domain information of the MSTP is configured on the switch, send a domain join message to the downstream bridge, where the domain join message carries the domain information of the MSTP, so that the downstream bridge
- the domain information of the MSTP is configured as domain information of the downstream bridge.
- the obtaining module may be specifically configured to receive domain information of the MSTP input by the user through the command line. After receiving the MSTP domain information entered by the user through the command line, the switch completes the configuration of the MSTP domain information on the switch.
- the root bridge sends a domain join message to the downstream bridge, and the domain join message carries the domain information, so that the downstream bridge can automatically configure the domain information, and the downstream bridge is automatically added to the corresponding domain.
- FIG. 7 is a schematic structural diagram of a switch according to a sixth embodiment of the present invention.
- the switch is a downstream bridge of an MSTI to be generated in an MSTP network, and the switch includes a receiver 71 and a configuration module 72.
- the receiver 71 is configured to receive the sending by the upstream node.
- the domain join message, the domain join message carries the domain information of the MSTP;
- the configuration module 72 is configured to configure the domain information of the MSTP to the domain information of the cost machine.
- the configuration module may be specifically configured to: after receiving the domain join message, configure the domain information of the MSTP to the domain information of the cost machine; or, after receiving the domain join message, compare the MSTP If the domain name in the domain information is the same as the domain name configured by itself, if the two are the same, the domain information of the MSTP is configured to the domain information of the cost machine.
- the switch may further include: a transmitter, configured to: when the downstream node exists, send a domain join message carrying the domain information of the MSTP to the downstream node, so that the downstream node configures the domain information of the MSTP as itself Domain information.
- a transmitter configured to: when the downstream node exists, send a domain join message carrying the domain information of the MSTP to the downstream node, so that the downstream node configures the domain information of the MSTP as itself Domain information.
- the domain join message is sent by the root bridge, and the domain join message carries the domain information, so that the domain information can be automatically configured. After the domain information is automatically configured, the domain is automatically added to the corresponding domain.
- FIG. 8 is a schematic structural diagram of a network system according to a seventh embodiment of the present invention, the system including a root bridge 81 and a downstream bridge
- the root bridge 81 is configured to send the configured MSTP domain information to the downstream bridge.
- the downstream bridge 82 is configured to configure the MSTP domain information as the domain information of the downstream bridge.
- the root bridge can be specifically as shown in FIG. 6, and the downstream bridge can be specifically shown in FIG. 7.
- the downstream bridge may be multiple, and one downstream bridge may also send a domain join message to its downstream bridge.
- the root bridge sends a domain join message to the downstream bridge, and the domain join message carries the domain information, which can enable
- the downstream bridge implements automatic configuration of domain information. After the domain information is automatically configured, the downstream bridge is automatically added to the corresponding domain.
- the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: various media that can store program codes, such as wake up, RAM, disk or optical disk.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
将 MSTP中的桥加入域的方法、 系统及交换机 本申请要求于 2011年 8月 9日提交中国专利局、 申请号为 201110226870. 7、 发明 名称为 "将 MSTP中的桥加入域的方法、 系统及交换机" 的中国专利申请的优先权, 其 全部内容通过引用结合在本申请中。 技术领域 本发明涉及网络通信技术,尤其涉及一种将多生成树协议(Multiple Spanning Tree Protocol , MSTP) 中的桥加入域中的方法、 系统及交换机。 背景技术 生成树协议 (Spanning Tree Protocol , MSTP) 通过在交换机之间传递桥协议数据 单元 (Bridge Protocol Data Unit, BPDU) 的协议报文, 依据 BPDU中包含的信息来完 成生成树计算, 达到消除二层网络环路的功能。 当网络故障后, 生成树协议会重新计算 堵塞点, 放开冗余链路以恢复网络业务。 STP网络只计算一个生成树, 全部虚拟局域网 (Virtual Local Area Network, VLAN) 按照一个生成树转发, 无法实现负载分担。
MSTP标准定义了域的概念, MSTP将一个交换网络划分成多个域, 通常情况下, 一 个地域范围内的交换机会划分在同一个域。 在域的内部按照不同的业务虚拟局域网 (Virtual Local Area Network, VLAN) 划分实例, 每个实例分别计算生成树。 因此, 每个域内可以形成多棵生成树,每棵生成树叫做一个多生成树实例(Multiple Spanning Tree Instance, MSTI ),通过设置 VLAN映射表,将 VLAN和 MSTI联系起来, 不同的 MSTI 可以按照计算的生成树拓扑转发实例内 VLAN的流量, 通过各个生成树的不同拓扑, 可 以实现域内生成树的负载分担。
当需要将一个区域的二层网络的全部桥加入同一个域时,现有技术采用手工配置的 方式, 由操作人员将 MSTP的域信息配置到每台交换机上。 但是, 手工配置方案存在工作 量大、 部署困难, 运维成本高的问题。 发明内容
本发明实施例提供一种将 MSTP中的桥加入域的方法、 系统及交换机, 用以解决现 有技术中手工配置域信息存在的工作量大、 部署困难, 运维成本高的问题。
本发明实施例一方面提供的一种将 MSTP中的桥加入域的方法, 包括:
待生成的多生成树实例 MSTI内的根桥获取 MSTP的域信息;
在所述根桥上配置所述 MSTP的域信息后, 所述根桥向下游桥发送域加入报文, 所述 域加入报文中携带所述 MSTP的域信息,用于使所述下游桥将所述 MSTP的域信息配置成所 述下游桥的域信息。
本发明实施例另一方面提供的一种将 MSTP中的桥加入域的方法, 包括:
下游桥接收上游节点发送的域加入报文, 所述域加入报文中携带 MSTP的域信息; 下游桥将所述 MSTP的域信息配置成本机的域信息。
发明实施例再一方面提供的一种交换机, 包括:
获取模块, 用于获取多生成树协议 MSTP的域信息;
发送器,用于在所述交换机上配置所述 MSTP的域信息后,向下游桥发送域加入报文, 所述域加入报文中携带所述 MSTP的域信息,用于使所述下游桥将所述 MSTP的域信息配置 成所述下游桥的域信息。
发明实施例第四方面提供一种交换机, 包括:
接收器, 用于接收上游节点发送的域加入报文, 所述域加入报文中携带多生成树协 议 MSTP的域信息;
配置模块, 用于将所述 MSTP的域信息配置成本机的域信息。
发明实施例提供一种网络系统, 包括:
根桥, 用于将获取的 MSTP的域信息发送给下游桥;
下游桥, 用于将所述 MSTP的域信息配置成所述下游桥的域信息。
由上述技术方案可知, 本发明实施例通过总根桥向下游桥发送域加入报文, 该域加 入报文中携带域信息, 可以实现域信息的自动配置, 实现下游桥自动加入对应的域中, 以避免手工配置存在的工作量大、 部署困难、 运维成本高的问题。 附图说明 为了更清楚地说明本发明实施例中的技术方案, 下面将对实施例描述中所需要使用 的附图作一简单地介绍, 显而易见地, 下面描述中的附图是本发明的一些实施例, 对于 本领域普通技术人员来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得 其他的附图。
图 1为本发明第一实施例的方法流程示意图;
图 2为本发明实施例中的域内桥的结构示意图;
图 3为本发明第二实施例的方法流程示意图;
图 4为本发明第三实施例的方法流程示意图;
图 5为本发明第四实施例的方法流程示意图;
图 6为本发明第五实施例的交换机的结构示意图;
图 7为本发明第六实施例的交换机的结构示意图;
图 8为本发明第七实施例的网络系统的结构示意图。 具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发明实施例中 的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例 是本发明一部分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普通技 术人员在没有做出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范 围。
图 1为本发明第一实施例的方法流程示意图, 图 2为本发明实施例中的域内桥的结 构示意图。 参见图 2, 该域的名称为校区 (CAMPUS ) , 该域内包括四个交换机, 分别为 SW— 1, SW— 2, SW— 3和 SW— 4。 对应每个 MSTI, 交换机按照角色的不同, 可以分为根桥和 下游桥 (或称为指定桥) , 本实施例中, SW— 1为根桥, 其他交换机为下游桥。 MSTP中, 同一个域内可以按照 VLAN 的不同生成多个生成树, 每个生成树称为一个 MSTI, 每个 MSTI对应一个根桥和至少一个下游桥。 其中, 在每个 MSTI内可以通过竞争方式 (或称 为选举方式) 确定根桥。 在建立网络拓扑时从根桥开始, 向下游桥逐级生成树, BPDU 报文也是从根桥逐级向下游桥下发。
参见图 1, 本实施例包括:
步骤 11 : 待生成的 MSTI内的根桥获取 MSTP的域信息;
其中, 用户可以通过命令行将 MSTP的域信息配置给根桥, 使得根桥获取该 MSTP的 域信息, 实现在根桥上配置 MSTP的域信息。
MSTP的域信息可以用 REGION— CONFIG表示,该 REGION— CONFIG是由三个参数组成的 三元组, 该三个参数分别为: 域名 (REGION— NAME) 、 实例 (REGION— INSTANCE) 和修订 等级 (REGION— LEVEL) 。 域名可以表示加入的域的名称, 实例可以表明该域内各实例、 以及配置的各实例对应的 VLAN列表。 修订等级由标准预留, 默认值为 0。
以图 2所示的系统为例, 该三元组可以如表 1所示:
表 1
步骤 12: 在所述根桥上配置所述 MSTP的域信息后, 所述根桥向下游桥发送域加入 报文, 所述域加入报文中携带所述 MSTP的域信息, 用于使所述下游桥将所述 MSTP的域 信息配置成所述下游桥的域信息。
其中, 根桥通过 MSTP端口发送域加入报文, 该域加入报文首先到达向与根桥直连 的下游桥, 之后由下游桥逐级向下发送该域加入报文直至能够到达的最后一个下游桥。
例如, SW— 1向 SW— 2发送域加入报文, SW— 2接收到该域加入报文后可以将其中携带 的 MSTP的域信息配置成自己的域信息, 实现加入该域信息对应的域内。
本实施例中,也可以在每个下游桥上预先设置域名,当下游桥接收到域加入报文时, 先判断接收的 MSTP的域信息中的域名是否与自身配置的域名相同,如果相同,则将 MSTP 的域信息配置成自身的域信息, 如果不同, 则不进行配置。 本实施例通过根桥向下游桥 发送域加入报文, 该域加入报文中携带域信息, 可以实现域信息的自动配置, 使得下游 桥可以自动加入对应的域中, 以避免手工配置存在的工作量大、 部署困难、 运维成本高 的问题。
图 3为本发明第二实施例的方法流程示意图, 包括:
步骤 31 : 下游桥接收上游节点发送的域加入报文, 所述域加入报文中携带 MSTP的 域信息;
例如, 参见图 2, SW— 2接收 SW— 1发送的域加入报文; 或者, SW— 4接收 SW— 2发送的 域加入报文。
MSTP的域信息可以用 REGION— CONFIG表示,该 REGION— CONFIG是由三个参数组成的 三元组, 该三个参数分别为: 域名 (REGION— NAME) 、 实例 (REGION— INSTANCR) 和修订 等级 (REGION— LEVEL) 。
步骤 32: 下游桥将所述 MSTP的域信息配置成本机的域信息。
例如, 可以是, 下游桥在接收到域加入报文后, 将 MSTP的域信息配置成本机的域 信息。 或者, 下游桥中预先配置域名, 当接收到域加入报文后, 比较 MSTP的域信息中
的域名与自身配置的域名是否相同, 如果相同, 则将 MSTP的域信息配置成本机的域信 息, 否则不进行配置。
进一步地, 如果该下游桥存在下游节点, 则该下游桥继续向自身的下游节点发送域 加入报文直至该域内的最后一个节点, 该域加入报文中携带所述 MSTP的域信息, 以便 下游节点将所述 MSTP的域信息配置成自身的域信息。
本实施例通过下游桥接收根桥发送的域加入报文,并将该域加入报文中携带的 MSTP 的域信息配置成本机的域信息, 可以实现域信息的自动配置, 进而自动加入域信息对应 的域, 即根桥所在的域中。 另外, 通过继续向下游节点发送域加入报文, 可以使得 MSTP 网络内该域加入报文到达的桥全部加入根桥所在域中, 以避免手工配置存在的工作量 大、 部署困难、 运维成本高的问题。
图 4为本发明第三实施例的方法流程示意图, 包括:
步骤 41 : 根桥 (以 SW— 1为例) 启动域加入功能。
其中, MSTP网络中, 针对不同的 VLAN生成不同的 MSTI, 对于要生成的 MSTI, 该 MSTI所在的域内的交换机可以通过竞争方式确定根桥和下游桥。 MSTP网络中的每个交 换机会对应一个默认的域, 可以按照交换机所在的地理位置划分对应的域。 例如, 如果 第一地理位置对应第一域, 则如果第一交换机和第二交换机均在第一地理位置的范围 内, 则第一交换机和第二交换机默认的域为第一域。 之后, 假设要生成的 MSTI所在的 域为第一域, 则在第一交换机和第二交换机启动后两者将交互 BPDU报文以竞争出根桥。
具体竞争过程可以为: 每个交换机对应一个桥 ID, 该桥 ID中包括优先级, 当一个 交换机的桥 ID中的优先级最高(对应的优先级数值最小) 时, 则表明该交换机为根桥。 各交换机通过交互 BPDU报文, 交互的 BPDU报文中会携带各自的桥 ID, 通过比较桥 ID, 将包含最高优先级的桥 ID对应的交换机确定为根桥。 以图 2为例, 根桥为 SW— 1。
在确定出根桥后, 用户可以通过命令行向根桥中输入 MSTP的域信息, 以实现对根 桥的配置。
步骤 42: 根桥通过 MSTP端口, 向下游节点 (以 SW— 2为例)发送域加入报文, 该域 加入报文中携带 MSTP的域信息。
例如, 参见图 2, 根桥 SW—1通过 MSTP端口发送域加入报文后, 将域加入报文将到 达 SW— 2。
步骤 43: SW— 2将接收的域加入报文上报给自身的 CPU, 并用域加入报文中携带的 MTSP域信息刷新自身配置的域信息。
通常, 交换机在接收到数据报文后是直接转发报文, 并不将报文上报给 CPU。但是, 本实施例中要完成域信息的配置, 则需要解析域加入报文, 因此, 本实施例中, 域加入 报文将到达 CPU, 并由 CPU解析获取 MSTP的域信息, 之后将该 MSTP的域信息配置成自 身的域信息, 即刷新域信息。
步骤 44: SW— 2向其下游节点 (SW— 4 ) 发送域加入报文, 其中携带 MSTP的域信息。 类似 SW— 2的处理, SW— 4接收到域加入报文后,将其中携带的 MSTP的域信息配置成 自身的域信息, 以加入到根桥所属的域中。
下游节点, 通过获取域加入报文中的 MSTP域信息并传递域加入报文, 可以实现同 一个域中的所有桥均加入该域中。
本实施例通过根桥向下游桥发送域加入报文, 该域加入报文中携带域信息, 可以实 现域信息的自动配置, 通过获取域加入报文中的 MSTP域信息, 实现下游桥自动加入对 应的域中。 另外, 通过继续向下游节点发送域加入报文, 可以使得同一域内的桥全部加 入该域中, 以避免手工配置存在的工作量大、 部署困难、 运维成本高的问题。
图 5为本发明第四实施例的方法流程示意图, 本实施例中以加入新的交换机为例。 参见图 5, 本实施例包括:
步骤 51 : 新加入的交换机 SW— 5向与其连接的上游节点 SW— 4发送 BPDU报文。
参见图 2, 假设新加入的交换机为 SW— 5 (图中未示出) , 且 SW— 5与 SW— 4连接, 则 SW— 5向 SW— 4发送 BPDU报文, 该 BPDU报文中会携带 SW— 5的桥 ID。
步骤 52 : 上游节点 SW— 4对该 BPDU报文进行上报及解析。
例如, 上报及解析过程由转发模块上报给 CPU, 由 CPU进行解析。 通过解析可以获 取 SW— 5的桥 ID, 如果该桥 ID中的优先级比 SW— 4的优先级低, 则表明 SW— 5是 SW— 4的 下游节点, 此时, SW— 5发送的 BPDU报文为次等 BPDU报文, 也就是优先级较低的 BPDU 报文, 也即下游节点向上游节点发送的 BPDU报文称为次等 BPDU报文。 其中, 桥 ID中 的优先级数值高则表明对应的交换机优先级低。
步骤 53 : SW— 4在确定出该 BPDU报文为次等 BPDU报文时, 向 SW— 5发送应答 BPDU 报文。
步骤 54: SW— 4在确定出该 BPDU报文为次等 BPDU报文时,向 SW— 5发送域加入报文, 其中携带 MSTP的域信息。
SW— 5接收到该域加入报文后, 可以将 MSTP的域信息配置成自身的域信息。
本实施例中, 根桥新加入的交换机发送携带域信息的域加入报文, 新加入交换机解
析报文, 并采用域加入报文中携带的根桥所在域的域信息作为自身的域信息, 可以使得 新加入的交换机也加入到根桥所属的域中。
图 6为本发明第五实施例的交换机的结构示意图, 该交换机可以为待生成的 MSTI 的根桥,该交换机包括获取模块 61和发送器 62 ;获取模块 61用于获取 MSTP的域信息; 发送器 62用于在所述交换机上配置所述 MSTP的域信息后, 向下游桥发送域加入报文, 所述域加入报文中携带所述 MSTP的域信息,用于使所述下游桥将所述 MSTP的域信息配 置成所述下游桥的域信息。
所述获取模块可以具体用于接收用户通过命令行输入的 MSTP的域信息。 交换机在 接收到用户通过命令行输入的 MSTP的域信息后则完成在该交换机上的 MSTP的域信息的 配置。
本实施例通过根桥向下游桥发送域加入报文, 该域加入报文中携带域信息, 可以使 得下游桥实现域信息的自动配置, 实现下游桥自动加入对应的域中。
图 7为本发明第六实施例的交换机的结构示意图, 该交换机为 MSTP网络中待生成 的 MSTI的下游桥, 该交换机包括接收器 71和配置模块 72 ; 接收器 71用于接收上游节 点发送的域加入报文, 所述域加入报文中携带 MSTP的域信息; 配置模块 72用于将所述 MSTP的域信息配置成本机的域信息。
所述配置模块可以具体用于: 接收到所述域加入报文后, 将所述 MSTP的域信息配 置成本机的域信息; 或者, 接收到所述域加入报文后, 比较所述 MSTP的域信息中的域 名与自身配置的域名, 如果两者相同, 则将所述 MSTP的域信息配置成本机的域信息。
进一步地, 该交换机还可以包括: 发送器, 用于在存在下游节点时, 向下游节点发 送携带 MSTP的域信息的域加入报文,使得所述下游节点将所述 MSTP的域信息配置成自 身的域信息。
本实施例通过接收根桥发送的域加入报文, 该域加入报文中携带域信息, 可以实现 域信息的自动配置, 在域信息自动配置后则完成自动加入对应的域中。
图 8为本发明第七实施例的网络系统的结构示意图, 该系统包括根桥 81和下游桥
82; 根桥 81用于将配置的 MSTP的域信息发送给下游桥; 下游桥 82用于将所述 MSTP的 域信息配置成所述下游桥的域信息。
其中, 根桥可以具体如图 6所示, 下游桥可以具体如图 7所示。
另外, 该下游桥可以为多个, 一个下游桥还可以向其下游桥发送域加入报文。 本实施例通过根桥向下游桥发送域加入报文, 该域加入报文中携带域信息, 可以使
得下游桥实现域信息的自动配置,在域信息自动配置后则使得下游桥自动加入对应的域 中。
可以理解的是, 上述方法及设备中的相关特征可以相互参考。 另外, 上述实施例中 的 "第一" 、 "第二"等是用于区分各实施例, 而并不代表各实施例的优劣。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤可以通过程 序指令相关的硬件来完成, 前述的程序可以存储于计算机可读取存储介质中, 该程序在 执行时, 执行包括上述方法实施例的步骤; 而前述的存储介质包括: 醒、 RAM, 磁碟或 者光盘等各种可以存储程序代码的介质。 最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其限制; 尽管 参照前述实施例对本发明进行了详细的说明, 本领域的普通技术人员应当理解: 其依然 可以对前述各实施例所记载的技术方案进行修改, 或者对其中部分技术特征进行等同替 换; 而这些修改或者替换, 并不使相应技术方案的本质脱离本发明各实施例技术方案的 精神和范围。
Claims
1、 一种将多生成树协议 MSTP中的桥加入域的方法, 其特征在于, 包括: 待生成的多生成树实例 MSTI内的根桥获取 MSTP的域信息;
在所述根桥上配置所述 MSTP的域信息后, 所述根桥向下游桥发送域加入报文, 所 述域加入报文中携带所述 MSTP的域信息,用于使所述下游桥将所述 MSTP的域信息配置 成所述下游桥的域信息。
2、根据权利要求 1所述的方法, 其特征在于, 所述根桥获取 MSTP的域信息, 包括: 根桥接收用户通过命令行输入的 MSTP的域信息。
3、 一种将 MSTP中的桥加入域的方法, 其特征在于, 包括:
下游桥接收上游节点发送的域加入报文, 所述域加入报文中携带 MSTP的域信息; 下游桥将所述 MSTP的域信息配置成本机的域信息。
4、 根据权利要求 3所述的方法, 其特征在于, 所述下游桥将所述 MSTP的域信息配 置成本机的域信息, 包括:
下游桥接收到所述域加入报文后, 将所述 MSTP的域信息配置成本机的域信息; 或 者,
下游桥接收到所述域加入报文后, 比较所述 MSTP的域信息中的域名与自身配置的 域名, 如果两者相同, 则将所述 MSTP的域信息配置成本机的域信息。
5、 根据权利要求 4或 5所述的方法, 其特征在于, 还包括:
如果所述下游桥存在下游节点, 则向下游节点发送携带 MSTP的域信息的域加入报 文, 使得所述下游节点将所述 MSTP的域信息配置成自身的域信息。
6、 一种交换机, 其特征在于, 包括:
获取模块, 用于获取多生成树协议 MSTP的域信息;
发送器, 用于在所述交换机上配置所述 MSTP的域信息后, 向下游桥发送域加入报 文, 所述域加入报文中携带所述 MSTP的域信息, 用于使所述下游桥将所述 MSTP的域信 息配置成所述下游桥的域信息。
7、 根据权利要求 6所述的交换机, 其特征在于, 所述获取模块具体用于接收用户 通过命令行输入的 MSTP的域信息。
8、 一种交换机, 其特征在于, 包括:
接收器, 用于接收上游节点发送的域加入报文, 所述域加入报文中携带多生成树协 议 MSTP的域信息; 配置模块, 用于将所述 MSTP的域信息配置成本机的域信息。
9、 根据权利要求 8所述的交换机, 其特征在于, 所述配置模块具体用于: 接收到 所述域加入报文后, 将所述 MSTP的域信息配置成本机的域信息; 或者, 接收到所述域 加入报文后, 比较所述 MSTP的域信息中的域名与自身配置的域名, 如果两者相同, 则 将所述 MSTP的域信息配置成本机的域信息。
10、 根据权利要求 8或 9所述的交换机, 其特征在于, 还包括:
发送器, 用于在存在下游节点时, 向下游节点发送携带 MSTP的域信息的域加入报 文, 使得所述下游节点将所述 MSTP的域信息配置成自身的域信息。
11、 一种网络系统, 其特征在于, 包括:
根桥, 用于将获取的 MSTP的域信息发送给下游桥;
下游桥, 用于将所述 MSTP的域信息配置成所述下游桥的域信息。
12、 根据权利要求 11所述的系统, 其特征在于, 所述根桥为权利要求 6或 7所述的交 换机, 以及, 所述下游桥为权利要求 8-10任一项所述的交换机。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP20120779660 EP2685678A4 (en) | 2011-08-09 | 2012-04-01 | Method, system, and switch for adding bridge in mstp to domain |
| US14/175,245 US9264314B2 (en) | 2011-08-09 | 2014-02-07 | Method, system, and switch for making bridge in MSTP join region |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011102268707A CN102291300A (zh) | 2011-08-09 | 2011-08-09 | 将mstp中的桥加入域的方法、系统及交换机 |
| CN201110226870.7 | 2011-08-09 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US14/175,245 Continuation US9264314B2 (en) | 2011-08-09 | 2014-02-07 | Method, system, and switch for making bridge in MSTP join region |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2012149849A1 true WO2012149849A1 (zh) | 2012-11-08 |
Family
ID=45337418
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2012/073477 Ceased WO2012149849A1 (zh) | 2011-08-09 | 2012-04-01 | 将mstp中的桥加入域的方法、系统及交换机 |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US9264314B2 (zh) |
| EP (1) | EP2685678A4 (zh) |
| CN (1) | CN102291300A (zh) |
| WO (1) | WO2012149849A1 (zh) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102291300A (zh) * | 2011-08-09 | 2011-12-21 | 华为技术有限公司 | 将mstp中的桥加入域的方法、系统及交换机 |
| CN103200071B (zh) * | 2013-04-07 | 2016-05-04 | 杭州华三通信技术有限公司 | 一种mstp多实例计算方法和设备 |
| CN106301964B (zh) * | 2016-10-31 | 2019-09-06 | 新华三技术有限公司 | 自动化配置实现方法和装置 |
| US10735247B2 (en) * | 2018-10-11 | 2020-08-04 | Dell Products L.P. | Spanning tree protocol traffic handling system |
| US11689455B2 (en) * | 2020-05-28 | 2023-06-27 | Oracle International Corporation | Loop prevention in virtual layer 2 networks |
| WO2022015883A1 (en) | 2020-07-14 | 2022-01-20 | Oracle International Corporation | Systems and methods for a vlan switching and routing service |
| US11909636B2 (en) | 2020-12-30 | 2024-02-20 | Oracle International Corporation | Layer-2 networking using access control lists in a virtualized cloud environment |
| WO2022146585A1 (en) | 2020-12-30 | 2022-07-07 | Oracle International Corporation | Layer-2 networking using access control lists in a virtualized cloud environment |
| WO2022146588A1 (en) | 2020-12-30 | 2022-07-07 | Oracle International Corporation | Layer-2 networking storm control in a virtualized cloud environment |
| US11671355B2 (en) | 2021-02-05 | 2023-06-06 | Oracle International Corporation | Packet flow control in a header of a packet |
| US11777897B2 (en) | 2021-02-13 | 2023-10-03 | Oracle International Corporation | Cloud infrastructure resources for connecting a service provider private network to a customer private network |
| EP4292262A1 (en) | 2021-02-13 | 2023-12-20 | Oracle International Corporation | Cloud infrastructure resources for connecting a service provider private network to a customer private network |
| US12592877B2 (en) | 2021-02-13 | 2026-03-31 | Oracle International Corporation | Packet flow in a cloud infrastructure based on cached and non-cached configuration information |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101014040A (zh) * | 2007-02-08 | 2007-08-08 | 杭州华为三康技术有限公司 | 一种触发下游设备处理报文的方法及交换设备 |
| US20070258390A1 (en) * | 2006-05-03 | 2007-11-08 | Tameen Khan | System and method for running a multiple spanning tree protocol with a very large number of domains |
| CN101640681A (zh) * | 2009-09-08 | 2010-02-03 | 杭州华三通信技术有限公司 | 一种修改多生成树域的域配置信息的方法及设备 |
| CN102291300A (zh) * | 2011-08-09 | 2011-12-21 | 华为技术有限公司 | 将mstp中的桥加入域的方法、系统及交换机 |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7292581B2 (en) * | 2002-10-24 | 2007-11-06 | Cisco Technology, Inc. | Large-scale layer 2 metropolitan area network |
| CN1510873A (zh) * | 2002-12-26 | 2004-07-07 | 华为技术有限公司 | 基于多生成树协议的域根切换实现方法 |
| US7480258B1 (en) * | 2003-07-03 | 2009-01-20 | Cisco Technology, Inc. | Cross stack rapid transition protocol |
| US7672314B2 (en) * | 2004-07-09 | 2010-03-02 | Cisco Technology, Inc. | Scaling VLANs in a data network |
| US7701881B1 (en) * | 2004-07-17 | 2010-04-20 | Cisco Technology, Inc. | System and method for determining the mergeability of spanning tree instances |
| US7821972B1 (en) * | 2005-09-29 | 2010-10-26 | Cisco Technology, Inc. | System and method for building large-scale layer 2 computer networks |
| US7580372B2 (en) * | 2005-12-15 | 2009-08-25 | Alcatel Lucent | System and method for implementing multiple spanning tree protocol automatic 802.1Q trunking |
| US7760668B1 (en) * | 2006-06-20 | 2010-07-20 | Force 10 Networks, Inc. | Self-reconfiguring spanning tree |
| US8693375B2 (en) * | 2006-10-17 | 2014-04-08 | Hewlett-Packard Development Company, L.P. | Automated multiple-instance spanning tree reconfiguration |
| CN101299671B (zh) | 2007-04-30 | 2013-03-13 | 上海贝尔阿尔卡特股份有限公司 | 用于组播数据包发送与接收的方法和装置 |
| US7911982B1 (en) * | 2008-05-01 | 2011-03-22 | Juniper Networks, Inc. | Configuring networks including spanning trees |
| US8467316B1 (en) * | 2010-12-29 | 2013-06-18 | Juniper Networks, Inc. | Enhanced address learning in layer two computer networks |
-
2011
- 2011-08-09 CN CN2011102268707A patent/CN102291300A/zh active Pending
-
2012
- 2012-04-01 EP EP20120779660 patent/EP2685678A4/en not_active Withdrawn
- 2012-04-01 WO PCT/CN2012/073477 patent/WO2012149849A1/zh not_active Ceased
-
2014
- 2014-02-07 US US14/175,245 patent/US9264314B2/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070258390A1 (en) * | 2006-05-03 | 2007-11-08 | Tameen Khan | System and method for running a multiple spanning tree protocol with a very large number of domains |
| CN101014040A (zh) * | 2007-02-08 | 2007-08-08 | 杭州华为三康技术有限公司 | 一种触发下游设备处理报文的方法及交换设备 |
| CN101640681A (zh) * | 2009-09-08 | 2010-02-03 | 杭州华三通信技术有限公司 | 一种修改多生成树域的域配置信息的方法及设备 |
| CN102291300A (zh) * | 2011-08-09 | 2011-12-21 | 华为技术有限公司 | 将mstp中的桥加入域的方法、系统及交换机 |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP2685678A4 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102291300A (zh) | 2011-12-21 |
| EP2685678A4 (en) | 2014-04-02 |
| EP2685678A1 (en) | 2014-01-15 |
| US9264314B2 (en) | 2016-02-16 |
| US20140153445A1 (en) | 2014-06-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2012149849A1 (zh) | 将mstp中的桥加入域的方法、系统及交换机 | |
| EP3188409B1 (en) | Oam mechanisms for evpn active-active services | |
| CN103348630B (zh) | 用于在组播网络中控制选择的方法 | |
| CN101459536B (zh) | 端口配置方法和交换设备 | |
| US20220255847A1 (en) | Packet Sending Method and First Network Device | |
| CN102549982A (zh) | 在计算机网络中控制数据转发的技术 | |
| CN106549774A (zh) | 一种基于软件定义网络的链路故障上报方法和转发设备 | |
| WO2013053276A1 (zh) | 一种网络路由收敛处理方法和装置 | |
| CN108243123A (zh) | 广播报文的处理方法、装置、控制器和交换机 | |
| TW201914265A (zh) | 自動配置的交換機、自動配置交換機的方法、交換機自動部署的軟體定義網路系統及其方法 | |
| CN104796339A (zh) | 快速泛洪处理方法及装置 | |
| WO2013086858A1 (zh) | 一种恢复用户业务的方法和装置 | |
| CN103812769B (zh) | Trill网络构建方法、节点及系统 | |
| WO2015027736A1 (zh) | 分层虚拟专用局域网服务的实现方法及装置 | |
| CN104919767A (zh) | 用于实现在虚拟专用lan服务网络上的最短路径桥接mac模式支持的方法和装置 | |
| US10771284B2 (en) | Troubleshooting method and apparatus for edge routing bridge in TRILL campus | |
| CN103067298B (zh) | 一种网络流量分担的方法及系统 | |
| WO2016131359A1 (zh) | 环型组网组播线路切换的方法及装置 | |
| WO2015018090A1 (zh) | 一种业务流链路的连通性检测方法、相关装置及系统 | |
| CN107018072B (zh) | 一种数据帧发送方法和接入设备 | |
| WO2011110037A1 (zh) | 一种环网架构下的组播实现方法、接入层设备及系统 | |
| JP2013198077A (ja) | ネットワーク及びブリッジ | |
| CN109995541B (zh) | 一种组播数据发送方法及节点设备 | |
| WO2015032261A1 (zh) | 路由更新方法和路由设备 | |
| CN107276774B (zh) | 一种组播报文传输方法以及转发设备 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12779660 Country of ref document: EP Kind code of ref document: A1 |
|
| REEP | Request for entry into the european phase |
Ref document number: 2012779660 Country of ref document: EP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2012779660 Country of ref document: EP |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
