CN103428088A

CN103428088A - Tree root allocation and message processing method and routing network bridge

Info

Publication number: CN103428088A
Application number: CN2012101483950A
Authority: CN
Inventors: 廖婷; 翟洪军
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2012-05-14
Filing date: 2012-05-14
Publication date: 2013-12-04
Anticipated expiration: 2032-05-14
Also published as: CN103428088B

Abstract

The invention discloses a tree root allocation and message processing method and a routing network bridge which is applied to a transparent interconnection of lots of links (TRILL) network. The tree root allocation method comprises the steps of using one routing network bridge (RB) as a group designate node (GDRB) in a routing network bridge group, allocating tree roots for each RB in the group according to a tree selection strategy and then informing an allocation result to each RB in the group. Correspondingly, the routing network bridge comprises a tree selection unit for allocating the tree roots for each RB in the group according to the tree selection strategy when the RB is used as the GDRB in the routing network bridge group, an informing unit for informing the allocation result of the tree selection unit for allocating the tree roots for each RB to each RB in the group. After adopting the tree root allocation and message processing method and the routing network bridge, mistaken abandonment of messages can be avoided, tree root allocation is flexibly applied, and members in the group can perform full information share and flexible network configuration through the group designate node and provide guarantee for network application.

Description

A kind of tree root distributes, message is processed method and route-bridge

Technical field

The present invention relates to the communications field, relate in particular to a kind of method and route-bridge of processing at tree root distribution, message.

Background technology

TRILL (Transparent Interconnection over Lots of Links, multichain connects transparent interconnection) be the standard of articulamentum (L2) network of Internet Engineering task groups (Internet Engineering Task Force, referred to as IETF) recommendation.TRILL is incorporated into the L2 network by Intermediate System-to-Intermediate System (Intermediate System to Intermediate System, referred to as IS-IS) Routing Protocol, as chain of command, realizes.In the TRILL network, the equipment of operation TRILL agreement is called route-bridge (Router Bridge, referred to as RBridge or RB), the RB wherein be connected with terminal is called Edge RB (edge RB, referred to as ERB), entrance RB is called Ingress RB, and outlet RB is called Egress RB.Entrance at the TRILL network, to hold the initial data frame of equipment (End Station) to be packaged into the TRILL form (at initial data frame front interpolation TRILL head and outside frame head, the Nickname and the jumping figure that mainly comprise TRILL Web portal and outlet route-bridge in the TRILL head), this Frame that just forms TRILL transmits in the TRILL network.Other be responsible for by the TRILL Frame from Ingress RB hop-by-hop be sent to Egress RB route-bridge be called the transmission route bridge.Data message can be carried out to decapsulation on Egress RB, be reduced into the backward terminal transmission of original message, simultaneously Egress RB also can learn this primitive frame be from which Ingress RB, import and form corresponding MAC (Medium Access Control, medium access control) information table: { D_MAC, Ingress Nickname ....

For fear of loop, border at the TRILL network, at any one VLAN (Virtual Local Area Network, VLAN) in, can only provide service for an end system by a RBridge, this RBridge is called the ISP of this end system, such as the VLAN-x on shared link specifies forwarding person (Appointed Forwarder, referred to as AF).Although this regulation can effectively be avoided loop, has also brought some problems, such as: after the AF switching, brought the variation of Ingress Nickname in some MAC address entries on far-end Egress RB on shared link; When end system by point-to-point link belong to more (Multi-homing) (such as: by many device links aggregation group (Multi Chassis Link Aggregation Group, referred to as MCLAG)) while going up to a plurality of RBridge, same source has plural Ingress RB node to the literary composition of delivering newspaper on it, RB for the destination address place, receive the message of sending up on different I ngress RB, can ceaselessly be refreshed the MAC information table that comprises source MAC and node nickname mapping relations, this will cause MAC Address redirect (flip-flop) problem.For fear of the flip-flop problem that causes the upper MAC Address of far-end RBridge, these links can only be operated in Active-Standby (activation-standby) pattern, from having caused bandwidth waste, be difficult to meet the high-throughput at high-performance data center and the demand of high reliability.

For this reason, TRILL working group has proposed route-bridge group (RBridge Group, referred to as RBG) or has been called the concept of virtual route-bridge (Virtual RBridge, referred to as RBv).Member node in the route-bridge group often has some identical attributes, such as: belong to a LAN (Local Area Network, local area network (LAN)), meet the relation of MCLAG or belong to an area (zone) etc.In a RBG, the group membership shares a Nickname, is called group Nickname, below all with RBv, identifies this group Nickname.Each group membership can announce the group Nickname of own place group in the TRILL network, helps other RBridge and calculates the path that leads to this RBv.The member of same group of the inside is when carrying out message up sending, and Ingress RB all can adopt the Nickname of this group to carry out the encapsulation of message.Because RBv is a group of dividing in logic, not concrete real node, therefore when realizing, concrete chain of command can be considered to be carried at a node below the group membership.For data surface, may exist from group membership RB1 node go out the encapsulation the RBv message to far-end, and the message that far-end is replied to RBv returns to the situation of group membership RB2, for RB2, may can not identify this reply, this will cause message to be dropped on RB2 and RB1 can not receive the situation of this reply message all the time.

Especially also relate to the problem that the group membership selects tree to distribute under multicast scenarios, particularly: in the TRILL network, multicast message forwards along tree, and forwards the technology such as inspection (Reverse Path Forwarding, referred to as RPF) by reverse path and avoid loop.RPF refers to, for route-bridge RB1, on a given tree, can only receive the multicast message that another route-bridge RB2 sends from a port.If RB1 receives from other port outside this interface the multicast message that RB2 sends along this tree, can think that rpf check is failed, thereby abandon this message.Will use which distribution tree by announcing oneself, route-bridge can notify other bridges to calculate RPF information for it.When route-bridge has many trees available, can give tacit consent to preferred root distance from own nearest tree when E-Packeting, thereby improve forward efficiency.Because RPF is simple, think that a leaf node can only hang over one above father node on one tree, if different group membership is encapsulated with RBv simultaneously, this leaf of RBv will be considered to be articulated in the back of these member node simultaneously so.If having two group memberships to announce on same one tree oneself is RBv simultaneously, be equivalent to RBv and be articulated in two father node back simultaneously, can't be by rpf check.Therefore the distribution that need to be set in the time of will using the RBv encapsulation to the group membership of same group of the inside, when group membership RB1 selects Tree1 to carry out message repeating with RBv, other group membership's node just can not be used the RBv encapsulation on Tree1.Relate to thus the RBv encapsulation and set the problem of selecting, while requiring the group membership to use the RBv encapsulation, must distribute different trees.

Summary of the invention

The purpose of this invention is to provide a kind of tree root distributes, message is processed method and route-bridge, to solve message mistake in the group membership, abandon and set the problem of distribution.

For addressing the above problem, the invention provides a kind of method that tree root distributes, be applied in the TRILL network, comprising:

In the route-bridge group, as group specified node (GDRB), according to choosing tree strategy, for each RB in group, distribute tree root by one of them route-bridge (RB), then allocation result is notified to each RB in group.

Further,

GDRB in described route-bridge group is by keeper's specified configuration, or each RB elects out all RB in this group according to identical election regulation in described route-bridge group.

Further,

In the situation that described GDRB is by keeper's specified configuration, described GDRB is judging while self being configured to GDRB, to other RB in group, sends for meaning it self is the GDRB sign message of GDRB;

In described group, RB, after receiving described GDRB sign message, is known in the group of place and is had RB to be elected as GDRB.

Further,

Described GDRB is that each RB elects out all RB in this group according to identical election regulation in described route-bridge group, specifically comprises:

Before not receiving described GDRB sign message, each RB in described route-bridge group elects a RB as described GDRB in this group all RB according to identical election regulation.

Further,

In the link aggregation group network, described election regulation is in group, preferentially to elect RB that tree root priority is the highest as GDRB; Perhaps,

In local area network (LAN), described election regulation is in group, preferentially to elect RB that interface priority is the highest as GDRB; Perhaps,

In zone, described election regulation is selected a RB as GDRB for the Nickname according to each RB in group.

Further,

Described is that in group, each RB distributes tree root according to choosing tree strategy, specifically comprises:

Described GDRB is sorted to organizing interior all RB, then according to the order of sequence, for each RB in group, distributes successively tree root; For each RB in group, described GDRB, in current all unappropriated tree roots, selects or tree root that link bandwidth maximum the shortest with the link cost of this RB to distribute to this RB.

Further, described method also comprises:

In described route-bridge group, part RB detects on this equipment and has configured distribution tree information to be used, and this RB sends to the GDRB in the route-bridge group of place by described distribution tree information;

After the described GDRB distribution tree information configured that other RB send in receiving group, correspondingly by this tree priority allocation, give this RB; For each RB that does not configure distribution tree information in group, described GDRB, in current all unappropriated tree roots, selects or tree root that link bandwidth maximum the shortest with the link cost of this RB to distribute to this RB.

Further,

After the described GDRB distribution tree information configured that other RB send in receiving group, correspondingly by this tree priority allocation, give this RB, specifically comprise:

After the described GDRB distribution tree information configured that other RB send in receiving group, the identical plural RB for pre-configured distribution tree information, described GDRB preferentially distributes to the wherein high RB of tree root priority by described pre-configured distribution tree, and, from current all unappropriated tree roots, select or tree root that link bandwidth maximum the shortest with the link cost of RB to distribute to other RB.

Further,

Described by allocation result notify to the group in each RB, specifically comprise:

In local area network (LAN), by the HELLO message in the TRILL network, described allocation result is sent to each RB in group, perhaps by terminal address interaction protocol (ESADI) expansion, described allocation result is sent to each RB in group, perhaps pass through Link State packet (LSP) inundation to the TRILL network, or described allocation result is sent to each RB in group on the intra-portal link by between many device links aggregation group (MCLAG) member;

In point to point network, expand described allocation result is sent to each RB in group by ESADI, or pass through Link State packet (LSP) inundation to the TRILL network, or on the intra-portal link between MCLAG member, described allocation result is sent to each RB in group.

In addition, a kind of method that the present invention also provides message to process, be applied in the TRILL network, comprising:

In the route-bridge group, by one of them route-bridge (RB) conduct group specified node (GDRB);

After a certain member's route-bridge (RB) is received the message that far-end sends, as to judge this message be that self can not process and destination address be as described in the message of route-bridge group, this message is sent to the GDRB in this group;

Described GDRB is after receiving described message, response message corresponding to message that this message is not the Nickname encapsulation of route-bridge group as described in the use of self sending as judged, be transmitted to this message respectively other member RB except the member RB that sends this message.

Further,

Correspondingly, the invention provides a kind of route-bridge, be applied in the TRILL network, comprising:

Choosing tree unit, for during as group specified node (GDRB), distributing tree root according to choosing tree strategy for each RB in group in the route-bridge group at described route-bridge (RB);

Notification unit, for notifying described choosing tree unit to each RB in group for each RB distributes the allocation result of tree root.

Further,

Described notification unit is also for when judging this route-bridge and be configured to GDRB, to other RB in group, sends for meaning it self is the GDRB sign message of GDRB.

Further, described route-bridge also comprises:

The election unit, for before not receiving described GDRB sign message, all RB according to election regulation in the route-bridge group of this route-bridge place, a RB of election is as described GDRB.

Further,

Described GDRB is elected according to following election regulation in described election unit:

Further,

Described choosing tree unit, for tactful in each RB in group distributes tree root according to the choosing tree, specifically comprises:

Described choosing tree unit, for being sorted to organizing interior all RB, then distributes tree root according to the order of sequence for each RB in group successively; Described choosing tree unit is for each RB in group, in current all unappropriated tree roots, selects or tree root that link bandwidth maximum the shortest with the link cost of this RB to distribute to this RB.

Further,

Notification unit also, for having configured distribution tree information to be used detecting on this equipment, sends to the GDRB in the route-bridge group of this route-bridge place by described distribution tree information;

Described choosing tree unit for the distribution tree information configured that other RB send in receiving group after, correspondingly by this tree priority allocation to this RB; Also for each RB for not configuring distribution tree information in group, in current all unappropriated tree roots, select or tree root that link bandwidth maximum the shortest with the link cost of this RB to distribute to this RB.

Further,

Described choosing tree unit for the distribution tree information configured that other RB send in receiving group after, correspondingly by this tree priority allocation to this RB, specifically comprise:

Described choosing tree unit for the distribution tree information configured that other RB send in receiving group after, the identical plural RB for pre-configured distribution tree information, preferentially described pre-configured distribution tree is distributed to the wherein high RB of tree root priority, and, from current all unappropriated tree roots, select or tree root that link bandwidth maximum the shortest with the link cost of RB to distribute to other RB.

Further,

Described notification unit, for allocation result being notified to each RB in group, specifically comprises:

Described notification unit is used at local area network (LAN), by the HELLO message in the TRILL network, described allocation result is sent to each RB in group, perhaps by terminal address interaction protocol (ESADI) expansion, described allocation result is sent to each RB in group, perhaps pass through Link State packet (LSP) inundation to the TRILL network, or described allocation result is sent to each RB in group on the intra-portal link by between many device links aggregation group (MCLAG) member;

Described notification unit is also at point to point network, expand described allocation result is sent to each RB in group by ESADI, or pass through Link State packet (LSP) inundation to the TRILL network, or on the intra-portal link between MCLAG member, described allocation result is sent to each RB in group.

Correspondingly, the present invention also provides a kind of route-bridge, is applied in the TRILL network, comprising:

Receiving element, the message of sending for receiving message that far-end sends or place other route-bridges of route-bridge group (RB);

Judging unit, for receive the message that far-end sends at described receiving element after, judge whether this message is message that self can not process and that destination address is described route-bridge group; Also at described route-bridge during as the group specified node (GDRB) in self place route-bridge group, judge that whether the message from far-end that other RB that described receiving element receives send is the response message corresponding to message of the Nickname encapsulation of the described route-bridge group of use self sent;

Transmitting element, for go out the message that message is that self can not process and destination address is described route-bridge group that described far-end sends in described judgment unit judges after, send to the GDRB in the route-bridge group of place by described message; Also at described route-bridge during as the GDRB in self place route-bridge group, when described judgment unit judges goes out the message from far-end that other RB that described receiving element receives send and is not response message corresponding to the message of Nickname encapsulation of the described route-bridge group of use self sent, this message is transmitted to respectively to other member RB except the member RB that sends this message.

Further,

Described transmitting element is also for when judging this route-bridge and be configured to GDRB, to other RB in group, sends for meaning it self is the GDRB sign message of GDRB.

Further,

After adopting the present invention, can avoid the mistake of message to abandon, and tree is distributed and applied in a flexible way, the guarantee that the group member can carry out sufficient information sharing, flexible network configuration and network application is provided by organizing specified node.

The accompanying drawing explanation

The topological diagram that Fig. 1 is TRILL network in the embodiment of the present invention;

Fig. 2 carries out the method flow diagram of tree root distribution in the TRILL network in the embodiment of the present invention;

Fig. 3 is TRILL network LAG group membership structure chart in application example one of the present invention;

The content exemplary plot that Fig. 4 is a kind of notification message in application example one of the present invention;

The content exemplary plot that Fig. 5 is another kind of notification message in application example one of the present invention;

Fig. 6 is TRILL network LAN group membership structure chart in application example two of the present invention.

Embodiment

For making the purpose, technical solutions and advantages of the present invention clearer, hereinafter in connection with accompanying drawing, embodiments of the invention are elaborated.It should be noted that, in the situation that do not conflict, the embodiment in the application and the feature in embodiment be combination in any mutually.

In the present embodiment, a kind of method of carrying out the message processing in the TRILL network comprises:

Step 10: in the route-bridge group, by one of them RB as the group specified node (GDRB);

After a certain member RB receives the message that far-end sends, the message that this message is that self can not process as judged, destination address is self place route-bridge group, this message is sent to the group specified node (Distribute RB, be designated hereinafter simply as GDRB) in this group;

Step 20:GDRB is after receiving above-mentioned message, and response message corresponding to message that this message is not the use RBv encapsulation of self sending as judged, be transmitted to this message respectively other member RB except the member RB that sends this message.

As shown in Figure 1, RB1, RB2 and RB3 belong to same route-bridge group, and after the RBv1 encapsulated message that RB1 sends arrives far-end RB5, RB5 replies to RB2 by response message.RB2 is owing to not identifying this message, as OAM (Operations Administration and Maintenance, operation, management and maintenance) etc. message, RB2 preferentially issues this message group specified node RB3 (supposing that RB3 is the interior group specified node of this group herein); RB3 is after receiving the message that mails to RBv1 that RB2 sends, as judging this message, not to be that oneself needs to be processed, is transmitted to other member node except RB2 in group, also is transmitted to RB1 and processed; After RB1 receives this response message, can correctly process.

In addition, in the present embodiment, a kind of method of carrying out the tree root distribution in the TRILL network as shown in Figure 2, comprising:

Step 10: in the route-bridge group, by one of them RB, as GDRB, according to choosing tree strategy, for each RB in group, distribute tree root.According to tree root priority or other principle, the group membership is sorted, then according to choosing tree strategy, by clooating sequence, be followed successively by each RB in group and select tree to calculate.Wherein: choosing tree strategy can be: the little excellent principle of cost (cost) or other strategy (as bandwidth) etc.

Suppose take that the little excellent principle of cost is as choosing tree strategy, GDRB is when selecting tree for the group membership, can be that basis is selected tree root according to the link cost between this group membership and each tree root, also when to certain group membership's allocation tree, can in current all unappropriated tree roots, select the tree of link cost the shortest (being the link cost minimum of tree root apart from this group membership's node) distribute to this group membership.

On certain group membership, during in advance for the certain tree of having used the RBv manual configuration, this group membership needs pre-configured tree information by this issue the interior GDRB of this group; After GDRB receives this configuration information, re-starting the choosing tree and calculate, is this pre-configured tree of this group membership's priority allocation; For the pre-configured group membership who clashes (as two above group memberships have gone up pre-configured, with one tree, carrying out the encapsulation of RBv), this tree is distributed to the group membership that tree root priority is high, the low node dispensed separately to tree root priority, for the dispensed that group membership of pre-configured tree is not set in residue tree root the inside according to choosing tree strategy.

Step 20:GDRB notifies allocation result to each member in group.

Wherein, allocation result can be chosen in different messages and be carried according to different scenes.If lan network, preferentially can select to be carried in the HELLO message of TRILL, perhaps can pass through LSP (Link State Packet, the Link State packet) inundation TRILL network, also can adopt expansion ESADI (End Station Address Distribution Information, the terminal address interaction protocol) carry out carrying of notice message, or the enterprising announcement that works of the intra-portal link between MCLAG member (MCLAG equipment room link); If the group of point to point network, as the group of MCLAG mode, can be passed through LSP inundation TRILL network, also can adopt expansion ESADI to carry out carrying of notice message, or the enterprising announcement that works of the intra-portal link between MCLAG member.Carry out the announcement of allocation result if adopt the LSP mode, can not identify this message in the situation that know the group exterior node, group membership RB is after receiving allocation result, send corresponding Affinity TLV (Affinity Tag Length Value according to result, allocation result while approximate label length value), wherein carrying the local RBv of use encapsulation; If know, outer other node of group as can be identified this message the time, organizes exterior node and can carry out RPF calculating according to the allocation result received, and the group membership only needs to encapsulate according to the RBv that is forwarded face for the tree of its distribution, no longer needs to carry out Affinity TLV announcement.

After this, the group membership, according to the tree allocation result of receiving, carries out the RBv encapsulation to the data message, and whether optional realization needs to carry out chain of command Affinity TLV announcement.Other outer node of group carries out the rpf check of RBv according to the allocation result of each member in the group received.

It should be noted that, in the route-bridge group, the GDRB that sets distribution and transfer message can be same RB, can be also different RB.

When specific implementation, GDRB can be specified by the keeper, also can elect by certain rule, as: in LAG (Link Aggregation Group, link aggregation group) network, can in group, preferentially elect RB that tree root priority is the highest as GDRB; While having the highest RB of plural tree root priority in group, can select according to system id (as selected the maximum or minimum RB of system id as GDRB the RB the highest from a plurality of tree root priority, certainly, can also adopt other rules to conduct an election according to system id); When the system of the RB selected according to certain rule id is also identical, can also further according to Nickname, be selected; In lan network, can in group, preferentially elect RB that interface priority is the highest as GDRB; While having the highest RB of plural tree root priority in group, can select according to system id (as selected the maximum or minimum RB of system id as GDRB the RB the highest from a plurality of tree root priority, certainly, can also adopt other rules to conduct an election according to system id); When the system of the RB selected according to certain rule id is also identical, can also further according to Nickname, be selected; In area, can carry out preferred GDRB according to Nickname.

Below by several examples of the present invention, be further described.

Application example one: the LAG application scenarios of point-to-point

Due in the individual draft draft-tissa-trill-cmt-00 of TRILL working group, a kind of Affinity TLV has been proposed, for what the group membership was used when using the RBv encapsulation, be which tree is announced away.But the scheme that the document is taked the distribution method of tree is: tree root sequencing numbers and group membership's sequencing numbers is carried out to modulo operation, if n tree arranged, sequence is 1-n, there is j group membership the group the inside, the blaze of i group membership's distribution is n i, i+j, the i+2j...i+xj in tree, wherein i+xj<n<i+ (x+1) j.It doesn't matter fully for the physical location of this method of salary distribution and concrete node and root vertex, supposing to adopt this mode is RBi for the tree root that member RB1 distributes, the tree root distributed for member RB2 is RBj, and geographically RB1 close to RBj, RB2 from close to RBi the time, can cause the waste of intermediate line link bandwidth.If, while having the group membership to want to configure certain tree separately, the method can not meet this demand.

In view of this, for giving the group membership, comparatively reasonably distribute the tree of required use, need to calculate negotiation according to the little excellent principle of cost or other strategy (as bandwidth) between the group membership.Because may have the situations such as congested on the link of cost minimum, so can select other strategy to be considered as bandwidth considerations.The group membership is according to the calculating of sorting of the principles such as priority, when the more and tree root of group membership is also more, each member node will calculate the tree of oneself, just need group membership's cycle calculations one by one just can draw, this is equivalent to all group memberships and has all calculated each tree that will use of all nodes, implements more complicated.

As shown in Figure 3, in point to point network, RB1～RBk is a route-bridge group the inside, this group nickname be RBv, if the tree root priority of RB1～RBk sorts from high to low, (also can be sorted according to other principle, as when tree root priority is consistent, can just be sorted by system id, as consistent as system id, by the nickname size, sorted) be RB1～RBk, suppose in RB1～RBk according to configuring or electing RB1 as GDRB.

Suppose has 3 trees in current TRILL network, and the tree root of these 3 trees is RBm, RBj, RBi in Tree id the inside order.If all there is no the appointment tree of configuration on all group memberships,, according to the minimum priority principle of COST, RB1 is limit priority, and RB1 can be preferably oneself and first select one tree.According to the choosing tree strategy of selecting the tree root the shortest from the RB1 distance, calculating RBi is first tree root of RB1; Then RB1 is that RB2 distributes tree root, and calculating RBj in remaining tree root except RBi is the tree root nearest from RB2, chooses RBj to distribute to RB2; Can only select remaining last tree root RBm when selecting to calculate for RB3.

If k+1 tree arranged in current TRILL network, this k+1 tree root is followed successively by RB1+m, RB2+m, RB3+m, RBk+1+m (wherein, m is the positive integer that is greater than k).Divide timing in the selection of being set, the tree root that RB1 distributes to RBk-2 to RB1 is followed successively by RB1+m to RBk+m-2, and, when selecting tree for RBk-1, also not selected tree root has RBk+m-1, RB k+m and RBk+m+1.If nearest from RBk-1 is RB k+m+1, the tree root distributed to RBk-1 so is RBk+m+1; While for RBk, selecting tree, that distance R Bk is nearest is RB k+m-1, and the tree root of distributing to RBk is RB k+m-1, and the one tree had more is circulated to RB1 and selects, carries out in this way dispensed, is equivalent to distribute two trees for RB1.

After having assigned, by result of calculation, the mode with notification message sends out RB1, as shown in Figure 4, carries the group membership in this notification message and the corresponding relation of the blaze that distributes.Because this part information is incomplete, useless to other group interior nodes, therefore only need in group, transmit this notification message gets final product and (as the intra-portal link link transmission by between the group membership or by the group member, all adds an ESADI example, by ESADI in group, transmit carried the group membership and distribute the corresponding informance of blaze), the group membership sends relevant AFF TLV inundation TRILL network after receiving above-mentioned allocation result, completes thus distribution and the rpf check of tree.

And if carry RBv, group membership in notification message and the corresponding relation of the blaze of the tree of distributing, as shown in Figure 5, but GDRB selects to pass through intra-portal link link transmission in this notification message inundation TRILL territory or group, if during inundation, outer other node of this extend information group also can be identified, the group membership is without having sent relevant AFF TLV again, and the group exterior node directly just can extract effective information according to this notification message and carry out rpf check; Pass through intra-portal link link transmission if there is the group exterior node can not identify or only be chosen in group, after the group membership receives this notification message, send relevant AFF TLV inundation TRILL network, complete thus distribution and the rpf check of tree.

Application example two: LAN application scenarios

As shown in Figure 6, RB1～RBk is a route-bridge group the inside, the nickname of this route-bridge group is RBv, if sorting from high to low, the tree root priority of RB1～RBk (also can be sorted according to other principle, as when tree root priority is consistent, can just be sorted by system id, as consistent as system id, by the nickname size, sorted) be RB1～RBk, suppose in RB1～RBk according to configuring or electing RB2 as GDRB.According to the described method of application example one, by RB2, select tree to calculate, and will set allocation result and be distributed to other group membership.

The announcement information that contains allocation result can be chosen in the HELLO message on LAN and carry, message structure as shown in Figure 4, all the other nodes can be without the existence of this message of perception like this, after the notified message of group membership, allocation result is carried at as sent in Affinity TLV.All the other group exterior nodes carry out corresponding rpf check according to this message information.Certainly, if what send is notification message as shown in Figure 5, if want, allow the group exterior node receive and to identify, can select the inundation by LSP, the group membership receives after message the literary composition of can separately transmitting messages like this, and all the other group exterior nodes just can carry out corresponding rpf check according to the information received.If certainly under the LAN scene, want to carry out the transmission of notification message with ESADI and intra-portal link link, also allow.

The appointment of application example three: GDRB, election and crash handling

Appointment, election and the crash handling of GDRB in above-mentioned application example one and application example two can be specially:

When the GDRB of appointment is arranged in group, GDRB is according to the automatic election rule, can be automatically oneself election priority be set to the highest, and send oneself is the sign message (can be transmitted by the intra-portal link link in organizing) of GDRB simultaneously, other group membership is after receiving the GDRB sign message that other member sends, stop election, wait for peacefully GDRB issue allocation result.While knowing this GDRB as other group memberships and lost efficacy (as the DBR machine of delaying), if there is other node to be configured GDRB in this group, this node is set to the highest by the election priority of oneself, and transmission GDRB sign message, organize thus interior nodes and can know have the member to bear GDRB role, wait for peacefully allocation result.When not receiving GDRB sign message, do not specify GDRB in expression group, in group, each member can conduct an election automatically according to unified election regulation, that is: in the network environment of point-to-point, can the dependent tree root priority election regulation such as height, system id size, nickname be big or small elect, the election principle that can follow GDRB in lan environment (conducts an election according to the priority of interface, interface MAC etc., can certainly be by the election principle in above-mentioned point to point network), each group membership conducts an election in accordance with a certain unified rule wherein in a word.Elected GDRB sends one and shows it oneself is the GDRB sign message (can be transmitted by the intra-portal link link in organizing) of GDRB in group, other group membership knows has the member to bear after GDRB role with regard to no longer carrying out the GDRB election, waits for peacefully GDRB allocation result is sent to local terminal.Therefore, once GDRB be detected, lost efficacy, and had new GDRB and elected, the election of this new GDRB, elected according to there being configuration to configure, without configuration according to election regulation elected mode carry out; After elected GDRB lost efficacy, continue to elect in all the other group members by mentioned above principle, when the group member receives new GDRB sign message, mean to elect successfully.When receiving the GDRB sign message that many parts of different nodes send simultaneously, by a plurality of nodes that send GDRB sign message, by preset rules, conducted an election, elect unique result, send GDRB sign message by the GDRB elected, and after being group member's allocation tree, cycle sends allocation result, carries out thus updating maintenance.

Application example four: tree Distribution Calculation when specifying the tree configuration if having on the group membership

As shown in Figure 3, if RB1, RB2, configured respectively tree used above RBk and be respectively RBj, RBm, RBi, and announcements of these tree information are announced away by Tree Used ID, rpf check at this time is to be RPF's with the nickname of node separately.And the tree carried out with the RBv encapsulation of being calculated by node is distributed, carry out RPF with RBv to do inspection, so there is not conflict.And if configuration to be tree specified configuration when tree is used the RBv encapsulation exist, when on member node during for the certain tree of having used the RBv manual configuration, this member node can be issued GDRB by the distribution tree information of configuration.After GDRB collects the distribution tree information of configuration, re-start calculating, tree for this configuration of node priority allocation that configures distribution tree, for the node of configuration conflict (as two configurations above node, use and carry out the encapsulation of RBv with one tree), by tree root priority, high node occupies the tree of this configuration, for the low node of tree root priority in conflict, passes through dispensed.Need the member node of dispensed according to the account form in application example one, according to choosing tree strategy, remaining the dispensed of being set inside tree root.As subsequent node continues to select successively in unappropriated tree root from own nearest tree root, as long as guarantee not repeat in the tree of distributing on each member node, in the situation that take into account manual configuration, specify tree to distribute the unique distribution of realization tree on the group membership to use.

Application example five: GDRB is responsible for the OAM message transfer between the group membership

Suppose that RB1, RB2, RB3 belong to same route-bridge group, wherein RB3 is GDRB, and after the RBv encapsulation of data message that RB1 sends arrives far-end RB5, RB5 finds that this message encapsulation may have problems, and need return to an OAM and report an error to RBv.By inquiring about local list item information, the optimum route that find to arrive RBv be and RB2 between path, RB5 sends the OAM message that reports an error to have replied to RB2 by the path of RB2 direction.Because RB2 does not send the OAM message of message in describing that report an error, this message is sent out by RB1, receives report an error message and can not identify the time of OAM as RB2 so, and this OAM message that reports an error is issued and organized specified node RB3 by intra-portal link.RB3 receives that destination address that RB2 sends is that the OAM of RBv reports an error after message, first judge whether oneself needs to be processed this message, if not, by intra-portal link, be transmitted to other the member node except this message sender, in this example this other member node RB1 namely.RB1 receives that this OAM reports an error after message, correctly processes this message.

In addition, in the present embodiment, a kind of route-bridge, be applied in the TRILL network, comprising:

Preferably,

Preferably, described route-bridge also comprises:

Preferably,

Correspondingly, in the present embodiment, a kind of route-bridge, be applied in the TRILL network, comprising:

Preferably,

One of ordinary skill in the art will appreciate that all or part of step in said method can come the instruction related hardware to complete by program, described program can be stored in computer-readable recording medium, as read-only memory, disk or CD etc.Alternatively, all or part of step of above-described embodiment also can realize with one or more integrated circuits.Correspondingly, each the module/unit in above-described embodiment can adopt the form of hardware to realize, also can adopt the form of software function module to realize.The present invention is not restricted to the combination of the hardware and software of any particular form.

The foregoing is only the preferred embodiments of the present invention, be not intended to limit protection scope of the present invention.According to summary of the invention of the present invention; also other various embodiments can be arranged; in the situation that do not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art are when making according to the present invention various corresponding changes and distortion; within the spirit and principles in the present invention all; any modification of doing, be equal to replacement, improvement etc., within protection scope of the present invention all should be included in.

Claims

1. the method that tree root distributes, be applied in multichain and connect in transparent interconnection (TRILL) network, comprising:

2. the method for claim 1 is characterized in that:

3. method as claimed in claim 2 is characterized in that:

4. method as claimed in claim 3 is characterized in that:

5. method as described as claim 2 or 4 is characterized in that:

6. the method for claim 1 is characterized in that:

7. the method for claim 1, is characterized in that, also comprises:

8. method as claimed in claim 7 is characterized in that:

9. the method for claim 1 is characterized in that:

10. the method that message is processed, be applied in multichain and connect in transparent interconnection (TRILL) network, comprising:

11. method as claimed in claim 10 is characterized in that:

12. method as claimed in claim 11 is characterized in that:

13. method as claimed in claim 12 is characterized in that:

14. method as described as claim 11 or 13 is characterized in that:

15. a route-bridge, be applied in multichain and connect in transparent interconnection (TRILL) network, comprising:

16. route-bridge as claimed in claim 15 is characterized in that:

17. route-bridge as claimed in claim 16, is characterized in that, also comprises:

18. route-bridge as claimed in claim 17 is characterized in that:

19. route-bridge as claimed in claim 15 is characterized in that:

20. route-bridge as claimed in claim 15 is characterized in that:

21. route-bridge as claimed in claim 20 is characterized in that:

22. route-bridge as claimed in claim 15 is characterized in that:

23. a route-bridge, be applied in multichain and connect in transparent interconnection (TRILL) network, comprising:

24. route-bridge as claimed in claim 23 is characterized in that:

25. route-bridge as claimed in claim 24, is characterized in that, also comprises:

26. route-bridge as claimed in claim 25 is characterized in that: