CN114745250B - Port management method and device - Google Patents

Port management method and device Download PDF

Info

Publication number
CN114745250B
CN114745250B CN202210290903.2A CN202210290903A CN114745250B CN 114745250 B CN114745250 B CN 114745250B CN 202210290903 A CN202210290903 A CN 202210290903A CN 114745250 B CN114745250 B CN 114745250B
Authority
CN
China
Prior art keywords
port
multicast
layer multicast
layer
state
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210290903.2A
Other languages
Chinese (zh)
Other versions
CN114745250A (en
Inventor
徐娜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to CN202210290903.2A priority Critical patent/CN114745250B/en
Publication of CN114745250A publication Critical patent/CN114745250A/en
Application granted granted Critical
Publication of CN114745250B publication Critical patent/CN114745250B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/04—Network management architectures or arrangements
    • 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/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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/16—Multipoint routing
    • 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/58—Association of routers
    • H04L45/586—Association of routers of virtual routers

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

The application provides a port management method and device. The method is applied to two-layer multicast equipment in VRRP networking, and by managing the port roles (which can be member ports, router ports or set ports) of the ports and the states of related two-layer multicast forwarding entries comprising the ports, when the two-layer multicast equipment receives related multicast data messages through the port roles as the router ports or the set ports, the two-layer multicast equipment forwards the multicast data messages only through the member ports connected with multicast receivers of a designated multicast group, and does not forward the multicast data messages through the port roles as the set ports, so that bandwidth resources are saved to a certain extent.

Description

Port management method and device
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for port management.
Background
In the existing virtual routing redundancy protocol (Virtual Router Redundancy Protocol, VRRP) networking (as shown in fig. 1), the two-layer multicast device 1 enables the internet group management protocol snooping (Internet Group Management Protocol Snooping, IGMP snooping), and when receiving an internet group management protocol (Internet Group Management Protocol, IGMP) membership report (Membership Report) message sent by a multicast receiver (i.e., host 1) of a designated multicast group through a Port (Port) 3 (i.e., a multicast group Member Port, abbreviated as a Member Port), generates a two-layer multicast forwarding table for managing and controlling forwarding of multicast data messages.
The second layer multicast device 1 is connected with the third layer multicast device 1 and the third layer multicast device 2 respectively, the third layer multicast device 1 and the third layer multicast device 2 are connected with the third layer multicast device 3 which is connected with the multicast source corresponding to the appointed multicast group respectively, and the third layer multicast device 1 and the third layer multicast device 2 are not connected with the multicast receiver of the appointed multicast group. And, the two-layer multicast device 1, the three-layer multicast device 1 and the three-layer multicast device 2 belong to the same spanning tree protocol (Spanning Tree Protocol, STP) ring network, and the blocking port is located on the three-layer multicast device 1.
The three-layer multicast device 1 and the three-layer multicast device 2 constitute a VRRP backup group, and both protocol independent multicast-Sparse Mode (PIM-SM) and IGMP are enabled. The three-layer multicast device 1 and the three-layer multicast device 2 will establish PIM neighbors by mutually interacting protocol independent multicast (Protocol Independent Multicast, PIM) Hello messages, and both will establish PIM neighbors by interacting PIM Hello messages with the three-layer multicast device 3 that is PIM-SM enabled and acts as a Rendezvous Point (RP) node; in addition, the two nodes also elect a designated router (Designated Router, DR), for example, elect a three-layer multicast device 2 as a DR node, and the three-layer multicast device 2 is responsible for sending PIM joining messages to the three-layer multicast device 3 so as to create a routing table item with an interface being Port1 on the three-layer multicast device 2 by the three-layer multicast device 3; both will also establish the multicast group and maintain the multicast group membership through IGMP.
Under such networking, the three-layer multicast device 1 and the three-layer multicast device 2 periodically send PIM Hello messages to each other through the two-layer multicast device 1, and the two-layer multicast device 1 sets ports (i.e., ports 1 and 2 on the two-layer multicast device 1) that receive the PIM Hello messages as Router ports (Router ports). In this way, when the three-layer multicast device 3 receives the multicast data packet of the specified multicast group, it sends the multicast data packet to the three-layer multicast device 2 based on the relevant routing table entry, the three-layer multicast device 2 sends the multicast data packet to the two-layer multicast device 1, and after receiving the multicast data packet through the Port2 on the self-body, the subsequent two-layer multicast device forwards the multicast data packet to the host 1 through the Port3 based on the relevant two-layer multicast forwarding table entry, and forwards the multicast data packet to the three-layer multicast device 1 through other routing ports (i.e., ports 1) on the self-body.
However, the multicast data packet is discarded on the side of the three-layer multicast device 1 because there is no corresponding outgoing interface. The reason why the three-layer multicast device 1 side has no corresponding outgoing interface is mainly that the three-layer multicast device 1 side has no multicast receiver of the multicast group, in this case, the multicast data packet sent by the two-layer multicast device 1 through the Port1 is actually redundant, which results in wasting more bandwidth resources.
Disclosure of Invention
In order to overcome the problems in the related art, the application provides a port management method and a device.
According to a first aspect of an embodiment of the present application, there is provided a port management method applied to a two-layer multicast device with IGMP snooping enabled in a VRRP network, the VRRP network further including a multicast receiver of a specified multicast group connected to the two-layer multicast device, a first three-layer multicast device, and a second three-layer multicast device, and a third three-layer multicast device connected to the first three-layer multicast device and the second three-layer multicast device and connected to a multicast source corresponding to the specified multicast group, the first three-layer multicast device and the second three-layer multicast device forming a VRRP backup group, and neither the multicast receiver of the specified multicast group nor the multicast receiver of the PIM-SM and IGMP being enabled, the two-layer multicast device, the first three-layer multicast device, and the second three-layer multicast device belonging to the same STP ring network, the method comprising:
when a first IGMP membership report message sent by a multicast receiver of the specified multicast group connected with the second multicast device is received for the first time, setting a port role of a first port receiving the first IGMP membership report message as a member port, setting a state of a first two-layer multicast forwarding table item of a virtual local area network (Virtual Local Area Network, VLAN) of the multicast receiver of the specified multicast group, which comprises the first port, an address of the specified multicast group and the specified multicast group, in a two-layer multicast forwarding table, which is created by the two-layer multicast device, as an active state, and guiding the two-layer multicast device to forward a multicast data message of the specified multicast group received through a port connected with a three-layer multicast device serving as a DR node of a specified router in the first three-layer multicast device and the second three-layer multicast device through an outbound interface in the two-layer multicast table item which is matched with the multicast data message and is in the active state;
When an IGMP query message or a first PIM Hello message sent by a three-layer multicast device serving as an IGMP query device in the first three-layer multicast device and the second three-layer multicast device is received for the first time, setting a port role of a second port which receives the IGMP query message or the first PIM Hello message as a router port, setting a state of a second two-layer multicast forwarding table which is created by the second port, an address of the appointed multicast group and a VLAN to which a multicast receiver of the appointed multicast group belongs in a two-layer multicast forwarding table as an effective state, and after setting the port role of the second port as a router port, if only the IGMP query message and the first PIM Hello message are received through the second port in a first set period, switching the port role of the second port from the router port to a set port, and changing the state of the second multicast forwarding table from the effective state to an invalid state; and
when a second PIM Hello message sent by a three-layer multicast device serving as a DR node in the first three-layer multicast device and the second three-layer multicast device is received for the first time, setting a port role of a third port receiving the second PIM Hello message as a router port, setting a state of a third two-layer multicast forwarding table including the third port, an address of the designated multicast group and a VLAN to which a multicast receiver of the designated multicast group belongs in a two-layer multicast forwarding table created by the first three-layer multicast device and the second three-layer multicast device as an effective state, and after setting the port role of the third port as a router port, if only the second PIM Hello message is received through the third port in a second set period, switching the port role of the third port from the router port to the set port, and changing the state of the third two-layer multicast forwarding table item from the effective state to the ineffective state, wherein the three-layer multicast device serving as an IGMP querier is different from the three-layer multicast device serving as a DR node.
According to a second aspect of an embodiment of the present application, there is provided a port management apparatus applied to a IGMP snooping enabled two-layer multicast device in a VRRP network, the VRRP network further including a multicast receiver of a specified multicast group connected to the two-layer multicast device, a first three-layer multicast device and a second three-layer multicast device, and a third three-layer multicast device connected to the first three-layer multicast device and the second three-layer multicast device and connected to a multicast source corresponding to the specified multicast group, the first three-layer multicast device and the second three-layer multicast device forming a VRRP backup group, and neither the multicast receiver of the specified multicast group nor the PIM-SM and IGMP being enabled, the two-layer multicast device, the first three-layer multicast device and the second three-layer multicast device belonging to the same STP ring network, the apparatus comprising:
a first management module, configured to, when receiving a first IGMP membership report packet sent by a multicast receiver of the specified multicast group connected to the first management module, set a port role of a first port that receives the first IGMP membership report packet as a member port, and set a state of a first two-layer multicast forwarding table item including the first port, an address of the specified multicast group, and a VLAN to which the multicast receiver of the specified multicast group belongs in a two-layer multicast forwarding table created by the two-layer multicast device as an active state, where the two-layer multicast forwarding table item in the active state in the two-layer multicast forwarding table created by the two-layer multicast device is used to instruct the two-layer multicast device to forward a multicast data packet of the specified multicast group received through a port connected to a three-layer multicast device serving as a DR node in the first three-layer multicast device and the second three-layer multicast device through an egress interface in the two-layer multicast table item in the active state that matches the multicast data packet;
A second management module, configured to, when an IGMP query message or a first PIM Hello message sent by a three-layer multicast device that is an IGMP querier in the first three-layer multicast device and the second three-layer multicast device is received for the first time, set a port role of a second port that receives the IGMP query message or the first PIM Hello message as a router port, set a state of a second two-layer multicast forwarding table that includes the second port, an address of the designated multicast group, and a VLAN to which a multicast receiver of the designated multicast group belongs in a two-layer multicast forwarding table that is created by itself as an active state, and after setting a port role of the second port as a router port, if only the IGMP query message and the first PIM Hello message are received through the second port in a first set period, switch the port role of the second port from the router port to a set port, and change the state of the second layer multicast forwarding table to an inactive state; and
and a third management module, configured to, when receiving, for the first time, a second PIM Hello packet sent by a three-layer multicast device that is a DR node in the first three-layer multicast device and the second three-layer multicast device, set a port role of a third port that receives the second PIM Hello packet as a router port, set a state of a third two-layer multicast table entry including the third port, an address of the specified multicast group, and a VLAN to which a multicast receiver of the specified multicast group belongs in a two-layer multicast forwarding table created by the third management module, to an active state, and after setting the port role of the third port as a router port, if only the second PIM Hello packet is received through the third port in a second set period, switch the port role of the third port from the router port to the set port, and change the state of the third two-layer multicast table entry from the active state to the inactive state, where the three-layer multicast device that is an IGMP querier is different from the three-layer multicast device that is a three-layer multicast node.
The technical scheme provided by the embodiment of the application can comprise the following beneficial effects:
in the embodiment of the application, for the two-layer multicast device which enables IGMP snoring in the VRRP networking, a new port role (namely a set port) is newly added for the port on the VRRP networking, and the two-layer multicast device only forwards the multicast data message through the member port which is connected with the multicast receiver of the designated multicast group on the VRRP networking and does not forward the multicast data message through the port role as the set port by managing the port roles (which can be member ports, router ports or set ports) of the ports and the states of the relevant two-layer multicast forwarding table items comprising the ports, so that the bandwidth resources are saved to a certain extent.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 is one of schematic diagrams of a VRRP networking architecture according to an embodiment of the present application;
fig. 2 is a flow chart of a port management method according to an embodiment of the present application;
FIG. 3 is a second schematic diagram of a VRRP networking architecture according to an embodiment of the present application;
FIG. 4 is a third schematic diagram of a VRRP networking architecture according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a VRRP networking architecture according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a port management device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. The word "if" or "if" as used herein may be interpreted as "at … …" or "at … …", depending on the context.
The embodiments of the present application will be described in detail.
The embodiment of the application provides a port management method, which is applied to two-layer multicast equipment enabling IGMP snoring in a VRRP (virtual router redundancy protocol) networking, wherein the VRRP networking further comprises a multicast receiver, a first three-layer multicast equipment and a second three-layer multicast equipment which are connected with the two-layer multicast equipment and a third three-layer multicast equipment which is connected with a multicast source and is connected with the first three-layer multicast equipment and the second three-layer multicast equipment, the first three-layer multicast equipment and the second three-layer multicast equipment form a VRRP backup group, the multicast receiver which is not connected with the designated multicast group and the PIM-SM and the IGMP are enabled, and the two-layer multicast equipment, the first three-layer multicast equipment and the second three-layer multicast equipment belong to the same STP ring network, as shown in figure 1, and the method can comprise the following steps:
S21, when a first IGMP membership report message sent by a multicast receiver of a specified multicast group connected with the self is received for the first time, setting a port role of a first port receiving the first IGMP membership report message as a member port, and setting a state of a first two-layer multicast forwarding table item including the first port, an address of the specified multicast group and a VLAN to which the multicast receiver of the specified multicast group belongs in a two-layer multicast forwarding table created by the self as an effective state.
The second layer multicast forwarding table item in an effective state in the second layer multicast forwarding table created by the second layer multicast device is used for guiding the second layer multicast device to forward the multicast data message of the designated multicast group received through the port connected with the third layer multicast device serving as the DR node in the first third layer multicast device and the second third layer multicast device through the output interface in the second layer multicast table item in an effective state, which is matched with the multicast data message.
S22, when an IGMP query message or a first PIM Hello message sent by a three-layer multicast device serving as an IGMP query device in a first three-layer multicast device and a second three-layer multicast device is received for the first time, setting a port role of a second port receiving the IGMP query message or the first PIM Hello message as a router port, setting a state of a second two-layer multicast forwarding table in a two-layer multicast forwarding table built by the first three-layer multicast device, wherein the second port, an address of a designated multicast group and a VLAN to which a multicast receiver of the designated multicast group belongs, in the two-layer multicast forwarding table are included as valid states, and after the port role of the second port is set as the router port, if only the IGMP query message and the first PIM Hello message are received through the second port in a first set time period, switching the port role of the second port from the router port to the set port, and changing the state of the second two-layer multicast forwarding table from the valid state to the invalid state.
In this step, a specific election process of electing a three-layer multicast device as an IGMP querier between the first three-layer multicast device and the second three-layer multicast device is a prior art, and will not be described in detail herein.
In addition, in this step, the first set duration may be a duration of a transmission period of the first set number of IGMP query messages or the first PIM Hello message.
Here, the first set number may be set according to actual network requirements of the VRRP networking. For example, in one example, the duration of the transmission period of the IGMP query message is assumed to be 105s, and the first set number is assumed to have a value of 3, so that the first set duration is 315s.
S23, when a second PIM Hello message sent by a three-layer multicast device serving as a DR node in the first three-layer multicast device and the second three-layer multicast device is received for the first time, setting a port role of a third port receiving the second PIM Hello message as a router port, setting a state of a third two-layer multicast forwarding table item including the third port, an address of a designated multicast group and a VLAN to which a multicast receiver of the designated multicast group in a two-layer multicast forwarding table created by the router per se belongs as an effective state, and after setting the port role of the third port as the router port, if only the second PIM Hello message is received through the third port in a second set period, switching the port role of the third port from the router port to the set port, and changing the state of the third two-layer multicast forwarding table item from the effective state to the invalid state.
In this step, the three-layer multicast device of the IGMP querier is different from the three-layer multicast device as a DR node.
In addition, in this step, the second set duration may be a duration of a second set number of transmission periods of the second PIM Hello packet.
The steps S22 and S23 are not sequentially divided.
In addition, in the embodiment of the present application, for the second layer multicast device, when receiving a multicast data packet of a designated multicast group sent by the third layer multicast device as a DR node through a port (the port role of the port may be a router port or a set port) connected to the third layer multicast device as a DR node in the first third layer multicast device and the second third layer multicast device, only the second layer multicast table item matching the multicast data packet is searched from the second layer multicast table items in the active state in the local second layer multicast forwarding table, and then the multicast data packet is forwarded through the egress interface in the searched second layer multicast table item. In this way, once the port role of the port on the two-layer multicast device connected with the three-layer multicast device serving as the non-DR node is a set port, the two-layer multicast device will not forward the related multicast data packet through the port, thereby saving bandwidth resources to a certain extent.
The specific election process between the first third layer multicast device and the second third layer multicast device to elect the third layer multicast device as a DR node is prior art, and will not be described in detail herein.
Further, in the embodiment of the present application, the two-layer multicast device may further execute the following operation flow:
the first operation flow is as follows: after the port role of the second port is switched to the set port by the router port, if a second IGMP membership report message broadcast by a three-layer multicast device serving as a non-DR node in the first three-layer multicast device and the second three-layer multicast device is received for the first time through the second port, switching the port role of the second port to the member port and the set port by the set port, and changing the state of a second two-layer multicast forwarding table item from an invalid state to an valid state, wherein the second IGMP membership report message is broadcast when the three-layer multicast device serving as the non-DR node is connected with a new multicast receiver of a designated multicast group and receives the second IGMP membership report message sent by the new multicast receiver;
when the second IGMP membership report message is not received through the second port within the third set time period, switching the port role of the second port from the member port to the set port to the router port, and maintaining the state of the second two-layer multicast forwarding table item unchanged;
After the port role of the second port is switched to the router port, the step of switching the port role of the second port from the router port to the set port is started to be executed if only the IGMP query message and the first PIM Hello message are received through the port within the first set time period. That is, after switching the port role of the port to the router port, the two-layer multicast device re-executes the step of switching the port role of the port from the router port to the set port if only the IGMP query message and/or the PIM Hello message is received through the port within the first set period of time, and executes the step of changing the state of the two-layer multicast forwarding table item including the port, the address of the designated multicast group, and the VLAN to which the multicast receiver of the designated multicast group belongs in the two-layer multicast forwarding table created by itself from the valid state to the invalid state.
The second operation flow is as follows: after the port role of the second port is switched to the set port, if the PIM joining message sent by the first three-layer multicast equipment or the second three-layer multicast equipment is received for the first time through the second port, the port role of the second port is switched to the router port, and the state of the second two-layer multicast forwarding table item is changed from an invalid state to an valid state; the PIM joining message is sent by the first three-layer multicast equipment or the second three-layer multicast equipment when receiving a third IGMP membership report message sent by a new multicast receiver connected with the PIM joining message and determining that the PIM joining message is switched from a non-DR node to a DR node and a link between the PIM joining message and the third three-layer multicast equipment fails;
After the port role of the second port is switched to the router port, if only the first PIM Hello message is received through the second port within the fourth set time period, the port role of the second port is switched from the router port to the set port, and the state of the second two-layer multicast forwarding table item is changed from the valid state to the invalid state. Here, the setting manner of the fourth set period of time may be the same as the setting manner of the second set period of time described above.
It should be noted that, the first operation flow is applicable to a scenario in which, after the second layer multicast device switches the port role of the second port from the router port to the set port, a new multicast receiver of the designated multicast group is deployed on the three-layer multicast device side that is a non-DR node in the first three-layer multicast device and the second three-layer multicast device. The second-layer multicast device can ensure that a new multicast receiver connected with the third-layer multicast device as a non-DR node can receive the related multicast data message in time by executing the first operation procedure, and can avoid wasting bandwidth resources for a long time after the new multicast receiver goes offline.
Here, the VLAN to which the new multicast receiver of the designated multicast group deployed on the three-layer multicast device side, which is a non-DR node, belongs may be the same as or different from the VLAN to which the multicast receiver of the designated multicast group on the two-layer multicast device side belongs.
Specifically, in the first operation flow, the third set duration may be a duration of a transmission period of a third set number of second IGMP membership report messages. Here, the third set number may also be set according to actual network requirements of VRRP networking.
The second operation flow is applicable to a scenario in which after the two-layer multicast device switches the port role of the port from the router port to the set port, DR nodes in the first three-layer multicast device and the second three-layer multicast device change, a new multicast receiver of the designated multicast group is located at the three-layer multicast device as a new DR node, and a link between the three-layer multicast device as a new DR node and the third three-layer multicast device fails. The second operation flow is executed by the second multicast device, so that a new multicast receiver connected with the third multicast device serving as a new DR node can be guaranteed to receive the related multicast data message in time, and bandwidth resources can be prevented from being wasted for a long time after the new multicast receiver goes offline.
The above-described port management method is described in detail with reference to specific embodiments.
Taking the VRRP networking architecture shown in fig. 1 as an example, assume that the three-layer multicast device serving as the DR node is the three-layer multicast device 2, and the three-layer multicast device serving as the IGMP querier is the three-layer multicast device 1; assuming that the transmission period of the PIM Hello message sent by the three-layer multicast device 1 and the three-layer multicast device 2 is 105s, the transmission period of the IGMP query message sent by the three-layer multicast device 1 is also 105s.
For the two-layer multicast device 1, when the IGMP membership report packet 1 sent by the host 1 is received for the first time, the Port role of the Port (i.e., port 3) that receives the IGMP membership report packet 1 is set as a member Port, and the state of the two-layer multicast forwarding table (denoted as the two-layer multicast forwarding table 1) including the Port3, the address of the designated multicast group, and the VLAN (e.g., VLAN 100) to which the host 1 belongs in the two-layer multicast forwarding table created by itself is set as a valid state.
When an IGMP query message or a PIM Hello message 1 sent by a three-layer multicast device 1 is received for the first time, setting a Port role of a Port (i.e., port 1) receiving the IGMP query message or the PIM Hello message 1 as a router Port, and setting a state of a two-layer multicast forwarding table (denoted as a two-layer multicast forwarding table 2) including the Port1, an address of a designated multicast group, and a VLAN (i.e., VLAN 100) to which the host 1 belongs in a two-layer multicast forwarding table created by the host as an active state.
After setting the Port role of the Port1 as the router Port, once only the IGMP query message and the PIM Hello message 1 are received through the Port1 within 3 consecutive 105s (i.e., within the first set period of time), the Port role of the Port1 is switched from the router Port to the set Port, and the state of the two-layer multicast forwarding table entry 2 is changed from the active state to the inactive state.
When the PIM Hello message 2 sent by the three-layer multicast device 2 is received for the first time, setting a Port role of a Port (i.e., port 2) receiving the PIM Hello message 2 as a router Port, and setting a state of a two-layer multicast forwarding table entry (denoted as a two-layer multicast forwarding table entry 3) including the Port2, an address of a designated multicast group, and a VLAN (i.e., VLAN 100) to which the host 1 belongs in the two-layer multicast forwarding table created by the device.
After setting the Port role of the Port2 as the router Port, once only the PIM Hello message 2 is received through the Port2 within 3 consecutive 105s (i.e., within the second set period of time described above), the Port role of the Port2 is switched from the router Port to the set Port, and the state of the two-layer multicast forwarding table item 3 is changed from the active state to the inactive state.
It should be noted that, for the second layer multicast device 1, when receiving a multicast data packet of a specified multicast group sent by the third layer multicast device 2 through a Port2 (the corresponding Port role may be a router Port or a set Port) (the multicast data packet is sent to the third layer multicast device 2 when receiving a multicast data packet from a multicast source corresponding to the specified multicast group) by the third layer multicast device 3, only the second layer multicast table item matching the multicast data packet is searched for from the second layer multicast table items in a valid state in the local second layer multicast forwarding table, and then the multicast data packet is forwarded through the output interface in the searched second layer multicast table item. In this way, in the case that the Port role of the Port1 on the two-layer multicast device 1 is the set Port, the two-layer multicast device 1 will not forward the multicast data packet through the Port1 (as shown in fig. 3), so that bandwidth resources are saved to a certain extent.
In addition, after the Port role of Port1 on the two-layer multicast device 1 is switched from the router Port to the set Port, if a new multicast receiver of the designated multicast group, for example, the host 2 as shown in fig. 4, is deployed on the three-layer multicast device 1, the VLAN to which the new multicast receiver belongs is VLAN100, in which case the three-layer multicast device 1 receives the IGMP membership report message sent by the host 2 through Port3 on the three-layer multicast device 1, and then the three-layer multicast device 1 broadcasts the IGMP membership report message in the VLAN to which the host 1 belongs.
Subsequently, for the second layer multicast device 1, when the IGMP membership report message 2 broadcast by the third layer multicast device 1 is received for the first time through the Port1, the Port role of the Port1 is switched from the set Port to the member Port and the set Port, and the state of the second layer multicast forwarding table entry 2 is changed from the invalid state to the valid state, so as to ensure that the host 2 can receive the related multicast data message in time.
Next, if the IGMP membership report 2 is not received through the Port1 within a third set period (for example, 260 s), that is, the host 2 is disconnected, at this time, the Port role of the Port1 is switched from the member Port to the set Port to the router Port, and the state of the two-layer multicast forwarding table entry 2 is maintained unchanged.
After the Port role of the Port1 is switched to the router Port, once only the IGMP query message and the PIM Hello message 1 are received through the Port1 within 3 consecutive 105s (i.e., within the first set period of time), the Port role of the Port1 is switched from the router Port to the set Port, and the state of the two-layer multicast forwarding table entry 2 is changed from the valid state to the invalid state, so as to avoid bandwidth waste.
Still further, after the Port role of the Port1 on the two-layer multicast device 1 is switched from the router Port to the set Port, if a new multicast receiver of the designated multicast group, for example, the host 3 shown in fig. 5, is deployed on the three-layer multicast device 1, the VLAN to which the new multicast receiver belongs is, for example, VLAN200, in fig. 4, it is assumed that the link between the three-layer multicast device 1 and the three-layer multicast device 3 has failed, and the three-layer multicast device 1 is changed to a DR node, in which case the three-layer multicast device 1 receives the IGMP membership report message transmitted by the host 2 through the Port3 on the three-layer multicast device 1 then transmits the PIM join message to the two-layer multicast device 1.
Subsequently, for the second-layer multicast device 1, when the PIM join message sent by the third-layer multicast device 1 is received for the first time through the Port1 Port, the Port role of the Port1 is switched to the Port of the router, and the state of the second-layer multicast forwarding table entry 2 is changed from the invalid state to the valid state, so as to ensure that the host 2 can receive the relevant multicast data message in time.
After that, after the Port role of the Port1 is switched to the router Port, once only the PIM Hello message 1 is received through the Port1 within 3 consecutive 105s (i.e., within the fourth set period of time), the Port role of the Port1 is switched from the router Port to the set Port, and the state of the two-layer multicast forwarding table entry 2 is changed from the valid state to the invalid state, so as to avoid the bandwidth waste.
As can be seen from the above technical solutions, in the embodiments of the present application, for a two-layer multicast device in VRRP networking that enables IGMP snooping, a new port role (i.e., a set port) is newly added for a port on its own, and by managing the port roles (which may be a member port, a router port or a set port) of its own port and the states of relevant two-layer multicast forwarding table entries including these ports, when the two-layer multicast device receives relevant multicast data packets through the port role as the router port or the set port, the two-layer multicast device forwards the multicast data packets only through the member port connected with the multicast receiver of the designated multicast group on its own, and does not forward the multicast data packets through the port role as the set port, thereby saving bandwidth resources to a certain extent.
Based on the same inventive concept, the present application further provides a port management apparatus, where the apparatus is applied to a two-layer multicast device in a VRRP networking that enables IGMP snooping, the VRRP networking further includes a multicast receiver of a specified multicast group connected to the two-layer multicast device, a first three-layer multicast device, and a second three-layer multicast device, and a third three-layer multicast device connected to the first three-layer multicast device and the second three-layer multicast device and connected to a multicast source corresponding to the specified multicast group, where the first three-layer multicast device and the second three-layer multicast device form a VRRP backup group, and neither the multicast receiver of the specified multicast group is connected to the two-layer multicast device, nor the first three-layer multicast device and the second three-layer multicast device belong to the same STP ring network, and the structure of the apparatus is shown in fig. 6, and the structure schematic diagram of the apparatus specifically includes:
a first management module 61, configured to, when receiving a first IGMP membership report packet sent by a multicast receiver of the specified multicast group connected to the first management module for the first time, set a port role of a first port that receives the first IGMP membership report packet as a member port, and set a state of a first two-layer multicast forwarding table entry including the first port, an address of the specified multicast group, and a virtual local area network VLAN to which the multicast receiver of the specified multicast group belongs in a two-layer multicast forwarding table created by the two-layer multicast device as an active state, where the two-layer multicast forwarding table entry in the active state is used to instruct the two-layer multicast device to forward a multicast data packet of the specified multicast group received through a port connected to a three-layer multicast device as a DR node of a specified router in the first three-layer multicast device and the second three-layer multicast device out an egress interface in the active state that matches the multicast data packet;
A second management module 62, configured to, when an IGMP query message or a first protocol independent multicast PIM Hello message sent by a three-layer multicast device that is an IGMP querier among the first three-layer multicast device and the second three-layer multicast device is received for the first time, set a port role of a second port that receives the IGMP query message or the first PIM Hello message as a router port, set a state of a second two-layer multicast forwarding table that includes the second port, an address of the designated multicast group, and a VLAN to which a multicast receiver of the designated multicast group belongs in a two-layer multicast forwarding table that is created by itself as an active state, and after setting the port role of the second port as a router port, if only the IGMP query message and the first PIM Hello message are received through the second port in a first set period, switch the port role of the second port from the router port to a set port, and change the state of the second multicast forwarding table from the active state to an inactive state; and
and a third management module 63, configured to, when receiving, for the first time, a second PIM Hello packet sent by a three-layer multicast device that is a DR node in the first three-layer multicast device and the second three-layer multicast device, set a port role of a third port that receives the second PIM Hello packet as a router port, set a state of a third two-layer multicast table entry including the third port, an address of the specified multicast group, and a VLAN to which a multicast receiver of the specified multicast group belongs in the two-layer multicast table created by itself as an active state, and after setting the port role of the third port as a router port, if only the second PIM Hello packet is received through the third port in a second set period, switch the port role of the third port from the router port to the set port, and change the state of the third two-layer multicast table entry from the active state to the inactive state, where the three-layer multicast device that is an IGMP querier is different from the three-layer multicast device that is a different node.
Preferably, the second management module 62 is further configured to:
after the port role of the second port is switched to a set port by a router port, if a second IGMP membership report message broadcast by a three-layer multicast device serving as a non-DR node of the first three-layer multicast device and the second three-layer multicast device is received for the first time through the second port, switching the port role of the second port to a member port and the set port from the set port, and changing the state of the second two-layer multicast forwarding table item from an invalid state to an valid state, wherein the second IGMP membership report message is broadcast by the three-layer multicast device serving as the non-DR node when a new multicast receiver of the designated multicast group is connected and the second IGMP membership report message sent by the new multicast receiver is received;
when the second IGMP membership report message is not received through the second port within a third set time period, switching the port role of the second port from a member port to a set port to a router port, and maintaining the state of the second two-layer multicast forwarding table item unchanged;
After the port role of the second port is switched to the router port, the step of switching the port role of the second port from the router port to the set port is started to be executed if only the IGMP query message and the first PIM Hello message are received through the port within the first set time period.
Preferably, the second management module 62 is further configured to:
after the port role of the second port is switched to a set port, if a PIM (PIM) joining message sent by the first three-layer multicast device or the second three-layer multicast device is received for the first time through the second port, switching the port role of the second port to a router port, and changing the state of the second two-layer multicast forwarding table item from an invalid state to an valid state;
after switching the port roles of the second port to the router port, if only the first PIM Hello message is received through the second port within a fourth set time period, switching the port roles of the second port from the router port to the set port, and changing the state of the second layer multicast forwarding table item from the valid state to the invalid state;
The PIM joining message is sent by the first three-layer multicast device or the second three-layer multicast device when receiving a third IGMP membership report message sent by a new multicast receiver connected with the PIM joining message, and determining that the PIM joining message is switched from a non-DR node to a DR node and that a link between the PIM joining message and the third three-layer multicast device fails.
Preferably, the first set duration is a duration of a transmission period of a first set number of IGMP query messages or the first PIM Hello messages; the second set duration is a second set number of durations of sending periods of the second PIM Hello messages.
Preferably, the third set duration is a duration of a transmission period of a third set number of the second IGMP membership report messages.
Preferably, the fourth set duration is a duration of a fourth set number of transmission periods of the first PIM Hello message.
As can be seen from the above technical solutions, in the embodiments of the present application, for a two-layer multicast device in VRRP networking that enables IGMP snooping, a new port role (i.e., a set port) is newly added for a port on its own, and by managing the port roles (which may be a member port, a router port or a set port) of its own port and the states of relevant two-layer multicast forwarding table entries including these ports, when the two-layer multicast device receives relevant multicast data packets through the port role as the router port or the set port, the two-layer multicast device forwards the multicast data packets only through the member port connected with the multicast receiver of the designated multicast group on its own, and does not forward the multicast data packets through the port role as the set port, thereby saving bandwidth resources to a certain extent.
An embodiment of the present application also provides an electronic device, as shown in fig. 7, including a processor 71 and a machine-readable storage medium 72, the machine-readable storage medium 72 storing machine-executable instructions executable by the processor 71, the processor 71 being caused by the machine-executable instructions to: the method for port management is realized.
The machine-readable storage medium may include random access Memory (Random Access Memory, RAM) or Non-Volatile Memory (NVM), such as at least one magnetic disk Memory. In the alternative, the machine-readable storage medium may also be at least one memory device located remotely from the foregoing processor.
The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
In yet another embodiment of the present application, there is also provided a computer readable storage medium having stored therein a computer program which, when executed by a processor, implements the steps of the port management method described above.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.

Claims (10)

1. A port management method, wherein the method is applied to a two-layer multicast device in a virtual routing redundancy protocol VRRP networking, wherein the two-layer multicast device is capable of snooping IGMP snooping, the VRRP networking further comprises a multicast receiver of a designated multicast group connected with the two-layer multicast device, a first three-layer multicast device and a second three-layer multicast device, and a third three-layer multicast device connected with the first three-layer multicast device and the second three-layer multicast device and connected with a multicast source corresponding to the designated multicast group, the first three-layer multicast device and the second three-layer multicast device form a VRRP backup group, and neither the multicast receiver of the designated multicast group nor the multicast receiver of the two-layer multicast device enable protocol independent multicast-sparse mode PIM-SM and internet group management protocol IGMP, and the two-layer multicast device, the first three-layer multicast device and the second three-layer multicast device belong to the same spanning tree protocol STP, the method comprises:
When a first IGMP membership report message sent by a multicast receiver of the designated multicast group connected with the second multicast device is received for the first time, setting a port role of a first port receiving the first IGMP membership report message as a member port, setting a state of a first two-layer multicast forwarding table item including the first port, an address of the designated multicast group and a virtual local area network VLAN to which the multicast receiver of the designated multicast group belongs in a two-layer multicast forwarding table created by the two-layer multicast device as an effective state, and guiding the two-layer multicast forwarding table item in the two-layer multicast table created by the two-layer multicast device to forward a multicast data message of the designated multicast group received through a port connected with a three-layer multicast device serving as a designated router DR node in the first three-layer multicast device and the second three-layer multicast device out of an outgoing interface in the two-layer multicast table item in the effective state, wherein the two-layer multicast data message is matched with the multicast data message;
when an IGMP query message or a first protocol independent multicast (PIM Hello) message sent by a three-layer multicast device serving as an IGMP querier in the first three-layer multicast device and the second three-layer multicast device is received for the first time, setting a port role of a second port which receives the IGMP query message or the first PIM Hello message as a router port, setting a state of a second layer multicast forwarding table item including the second port, an address of the designated multicast group and a VLAN to which a multicast receiver of the designated multicast group belongs in a two-layer multicast forwarding table created by the router, as an active state, and after setting the port role of the second port as a router port, if only the IGMP query message and the first PIM Hello message are received through the second port in a first set period, switching the port role of the second port from the router port to a set port, and changing the state of the second layer multicast forwarding item from the active state to the inactive state; and
When a second PIM Hello message sent by a three-layer multicast device serving as a DR node in the first three-layer multicast device and the second three-layer multicast device is received for the first time, setting a port role of a third port receiving the second PIM Hello message as a router port, setting a state of a third two-layer multicast forwarding table including the third port, an address of the designated multicast group and a VLAN to which a multicast receiver of the designated multicast group belongs in a two-layer multicast forwarding table created by the first three-layer multicast device and the second three-layer multicast device as an effective state, and after setting the port role of the third port as a router port, if only the second PIM Hello message is received through the third port in a second set period, switching the port role of the third port from the router port to the set port, and changing the state of the third two-layer multicast forwarding table item from the effective state to the ineffective state, wherein the three-layer multicast device serving as an IGMP querier is different from the three-layer multicast device serving as a DR node.
2. The method according to claim 1, wherein the method further comprises:
after the port role of the second port is switched to a set port by a router port, if a second IGMP membership report message broadcast by a three-layer multicast device serving as a non-DR node of the first three-layer multicast device and the second three-layer multicast device is received for the first time through the second port, switching the port role of the second port to a member port and the set port from the set port, and changing the state of the second two-layer multicast forwarding table item from an invalid state to an valid state, wherein the second IGMP membership report message is broadcast by the three-layer multicast device serving as the non-DR node when a new multicast receiver of the designated multicast group is connected and the second IGMP membership report message sent by the new multicast receiver is received;
When the second IGMP membership report message is not received through the second port within a third set time period, switching the port role of the second port from a member port to a set port to a router port, and maintaining the state of the second two-layer multicast forwarding table item unchanged;
after the port role of the second port is switched to the router port, the step of switching the port role of the second port from the router port to the set port is started to be executed if only the IGMP query message and the first PIM Hello message are received through the port within the first set time period.
3. The method according to claim 1, wherein the method further comprises:
after the port role of the second port is switched to a set port, if a PIM (PIM) joining message sent by the first three-layer multicast device or the second three-layer multicast device is received for the first time through the second port, switching the port role of the second port to a router port, and changing the state of the second two-layer multicast forwarding table item from an invalid state to an valid state;
after switching the port roles of the second port to the router port, if only the first PIM Hello message is received through the second port within a fourth set time period, switching the port roles of the second port from the router port to the set port, and changing the state of the second layer multicast forwarding table item from the valid state to the invalid state;
The PIM joining message is sent by the first three-layer multicast device or the second three-layer multicast device when receiving a third IGMP membership report message sent by a new multicast receiver connected with the PIM joining message, and determining that the PIM joining message is switched from a non-DR node to a DR node and that a link between the PIM joining message and the third three-layer multicast device fails.
4. The method of claim 1, wherein the first set duration is a duration of a transmission period of a first set number of IGMP query messages or the first PIM Hello message;
the second set duration is a second set number of durations of sending periods of the second PIM Hello messages.
5. The method of claim 2 wherein the third set duration is a duration of a transmission period of a third set number of the second IGMP membership report messages.
6. A port management apparatus, wherein the apparatus is applied to a second layer multicast device in a virtual routing redundancy protocol VRRP networking, wherein the VRRP networking further includes a multicast receiver of a specified multicast group connected to the second layer multicast device, a first third layer multicast device, and a second third layer multicast device, and a third layer multicast device connected to the first third layer multicast device and the second third layer multicast device, wherein the third layer multicast device is connected to a multicast source corresponding to the specified multicast group, wherein the first third layer multicast device and the second third layer multicast device form a VRRP backup group, and wherein no multicast receiver of the specified multicast group is connected to the third layer multicast device, and protocol independent multicast-sparse mode PIM-SM and internet group management protocol IGMP are all enabled, and wherein the second layer multicast device, the first third layer multicast device, and the second third layer multicast device belong to the same spanning tree protocol STP, the apparatus comprises:
A first management module, configured to, when receiving a first IGMP membership report packet sent by a multicast receiver of the specified multicast group connected to the first management module, set a port role of a first port that receives the first IGMP membership report packet as a member port, and set a state of a first two-layer multicast forwarding table item including the first port, an address of the specified multicast group, and a virtual local area network VLAN to which the multicast receiver of the specified multicast group belongs in a two-layer multicast forwarding table created by the two-layer multicast device as an active state, where the two-layer multicast forwarding table item in the active state is used to instruct the two-layer multicast device to forward a multicast data packet of the specified multicast group received through a port connected to a three-layer multicast device as a DR node of the specified router in the first three-layer multicast device and the second three-layer multicast device out of an egress interface in the active state that matches the multicast data packet;
a second management module, configured to, when an IGMP query message or a first protocol independent multicast PIM Hello message sent by a three-layer multicast device that is an IGMP query device in the first three-layer multicast device and the second three-layer multicast device is received for the first time, set a port role of a second port that receives the IGMP query message or the first PIM Hello message as a router port, set a state of a second two-layer multicast forwarding table that includes the second port, an address of the designated multicast group, and a VLAN to which a multicast receiver of the designated multicast group belongs in a two-layer multicast forwarding table that is created by itself as an active state, and after setting the port role of the second port as a router port, if only the IGMP query message and the first PIM Hello message are received through the second port in a first set period, switch the port role of the second port from the router port to a set port, and change the state of the second multicast forwarding table to an inactive state; and
And a third management module, configured to, when receiving, for the first time, a second PIM Hello packet sent by a three-layer multicast device that is a DR node in the first three-layer multicast device and the second three-layer multicast device, set a port role of a third port that receives the second PIM Hello packet as a router port, set a state of a third two-layer multicast table entry including the third port, an address of the specified multicast group, and a VLAN to which a multicast receiver of the specified multicast group belongs in a two-layer multicast forwarding table created by the third management module, to an active state, and after setting the port role of the third port as a router port, if only the second PIM Hello packet is received through the third port in a second set period, switch the port role of the third port from the router port to the set port, and change the state of the third two-layer multicast table entry from the active state to the inactive state, where the three-layer multicast device that is an IGMP querier is different from the three-layer multicast device that is a three-layer multicast node.
7. The apparatus of claim 6, wherein the second management module is further configured to:
After the port role of the second port is switched to a set port by a router port, if a second IGMP membership report message broadcast by a three-layer multicast device serving as a non-DR node of the first three-layer multicast device and the second three-layer multicast device is received for the first time through the second port, switching the port role of the second port to a member port and the set port from the set port, and changing the state of the second two-layer multicast forwarding table item from an invalid state to an valid state, wherein the second IGMP membership report message is broadcast by the three-layer multicast device serving as the non-DR node when a new multicast receiver of the designated multicast group is connected and the second IGMP membership report message sent by the new multicast receiver is received;
when the second IGMP membership report message is not received through the second port within a third set time period, switching the port role of the second port from a member port to a set port to a router port, and maintaining the state of the second two-layer multicast forwarding table item unchanged;
after the port role of the second port is switched to the router port, the step of switching the port role of the second port from the router port to the set port is started to be executed if only the IGMP query message and the first PIM Hello message are received through the port within the first set time period.
8. The apparatus of claim 6, wherein the switching module is further configured to:
after the port role of the second port is switched to a set port, if a PIM (PIM) joining message sent by the first three-layer multicast device or the second three-layer multicast device is received for the first time through the second port, switching the port role of the second port to a router port, and changing the state of the second two-layer multicast forwarding table item from an invalid state to an valid state;
after switching the port roles of the second port to the router port, if only the first PIM Hello message is received through the second port within a fourth set time period, switching the port roles of the second port from the router port to the set port, and changing the state of the second layer multicast forwarding table item from the valid state to the invalid state;
the PIM joining message is sent by the first three-layer multicast device or the second three-layer multicast device when receiving a third IGMP membership report message sent by a new multicast receiver connected with the PIM joining message, and determining that the PIM joining message is switched from a non-DR node to a DR node and that a link between the PIM joining message and the third three-layer multicast device fails.
9. The apparatus of claim 6, wherein the first set duration is a duration of a transmission period of a first set number of IGMP query messages or the first PIM Hello message; the second set duration is a second set number of durations of sending periods of the second PIM Hello messages.
10. The apparatus of claim 7, wherein the third set duration is a duration of a transmission period of a third set number of the second IGMP membership report messages.
CN202210290903.2A 2022-03-23 2022-03-23 Port management method and device Active CN114745250B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210290903.2A CN114745250B (en) 2022-03-23 2022-03-23 Port management method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210290903.2A CN114745250B (en) 2022-03-23 2022-03-23 Port management method and device

Publications (2)

Publication Number Publication Date
CN114745250A CN114745250A (en) 2022-07-12
CN114745250B true CN114745250B (en) 2023-12-12

Family

ID=82277429

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210290903.2A Active CN114745250B (en) 2022-03-23 2022-03-23 Port management method and device

Country Status (1)

Country Link
CN (1) CN114745250B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102082720A (en) * 2009-12-01 2011-06-01 杭州华三通信技术有限公司 Method and device for forwarding multicast flow
CN103441940A (en) * 2013-08-29 2013-12-11 华为技术有限公司 Method and device for switching network device from stand-by state to main state and network device
CN113472656A (en) * 2021-06-29 2021-10-01 新华三信息安全技术有限公司 Two-layer switching equipment and method for forwarding multicast data message

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101035009A (en) * 2007-03-31 2007-09-12 华为技术有限公司 Multicast traffic redundancy protection method and device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102082720A (en) * 2009-12-01 2011-06-01 杭州华三通信技术有限公司 Method and device for forwarding multicast flow
CN103441940A (en) * 2013-08-29 2013-12-11 华为技术有限公司 Method and device for switching network device from stand-by state to main state and network device
CN113472656A (en) * 2021-06-29 2021-10-01 新华三信息安全技术有限公司 Two-layer switching equipment and method for forwarding multicast data message

Also Published As

Publication number Publication date
CN114745250A (en) 2022-07-12

Similar Documents

Publication Publication Date Title
US8102848B1 (en) Multicast high availability enhancements for faster convergence
US9077551B2 (en) Selection of multicast router interfaces in an L2 switch connecting end hosts and routers, which is running IGMP and PIM snooping
US7944811B2 (en) Multiple multicast forwarder prevention during NSF recovery of control failures in a router
US8345536B1 (en) Multicast high availability enhancements for non-stop forwarding
US7787360B2 (en) System and method for preserving multicast data forwarding during control failures in a router
US7720066B2 (en) System and method for distributed multicast routing
US8340095B2 (en) Equipment in a data network and methods for monitoring, configuring and/or managing the equipment
US8619605B2 (en) Method and apparatus for maintaining port state tables in a forwarding plane of a network element
US8385335B2 (en) Method and apparatus for providing fast reroute of a unicast packet within a network element to an available port associated with a multi-link trunk
US7778266B2 (en) Switch and network fault recovery method
US9031070B2 (en) Methods for controlling elections in a multicast network
JP2013543687A (en) Multicast branch, protocol independent multicast router, and pruning method for layer 2 switch
US20080259913A1 (en) Achieving super-fast convergence of downstream multicast traffic when forwarding connectivity changes between access and distribution switches
EP3883182B1 (en) Evpn multicast ingress forwarder election using source-active route
CN107547367B (en) Multicast switching method, device and machine readable storage medium
CN102185776B (en) The method of Ethernet Layer 2 Multicast Fast Convergent and Ethernet system
EP1774683B1 (en) System and method for preserving multicast data forwarding during control failures in a router
CN101610200A (en) Multicast path by changing method and device
CN114745250B (en) Port management method and device
EP4057578A1 (en) Internet group management protocol host mobility in ethernet virtual private network multicast networks
Fenner et al. RFC 4601: Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification (Revised)
Cisco Configuring IP Multicast Layer 3 Switching
Cisco Configuring IP Multicast Layer 3 Switching
Cisco Configuring IP Multicast Routing
Cisco Configuring IP Multicast Routing

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant