WO2014110729A1 - 一种trill oam报文实现方法，rb和trill网络 - Google Patents

一种trill oam报文实现方法，rb和trill网络 Download PDF

Info

Publication number
WO2014110729A1
WO2014110729A1 PCT/CN2013/070531 CN2013070531W WO2014110729A1 WO 2014110729 A1 WO2014110729 A1 WO 2014110729A1 CN 2013070531 W CN2013070531 W CN 2013070531W WO 2014110729 A1 WO2014110729 A1 WO 2014110729A1
Authority
WO
WIPO (PCT)
Prior art keywords
trill
oam
egress
vlan
mac address
Prior art date
Application number
PCT/CN2013/070531
Other languages
English (en)
French (fr)
Inventor
宗志刚
谢莹
吴光锐
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201380000092.7A priority Critical patent/CN104145456A/zh
Priority to PCT/CN2013/070531 priority patent/WO2014110729A1/zh
Priority to EP13871687.3A priority patent/EP2933962A4/en
Publication of WO2014110729A1 publication Critical patent/WO2014110729A1/zh
Priority to US14/797,566 priority patent/US20150319082A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • 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]
    • H04L12/4645—Details on frame tagging
    • H04L12/465—Details on frame tagging wherein a single frame includes a plurality of VLAN tags
    • 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/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's

Definitions

  • TRILL 0AM message implementation method RB and TRILL network
  • the embodiments of the present invention relate to the field of network communications, and in particular, to a TRILL OAM packet implementation method, an RB and a TRILL network. Background technique
  • TRILL transparent interconnection of lots of links
  • TRILL is a protocol applied to router bridges or RBridge (RB) devices.
  • TRILL runs on the data link layer, which is the layer 2 (L2) in the open system interconnection (0SI) reference model.
  • L2 layer 2
  • SI open system interconnection
  • the intermediate system is used in the intermediate system.
  • IS-IS intermediate system
  • link state routing technology to spread and advertise topology and logical network membership, apply link state routing technology to the data link layer, and provide logic on the traditional Ethernet architecture. Ethernet.
  • the encapsulation format of a TRILL packet includes an Outer Ethernet Header, a TRILL header, an Inner Ethernet Header, a payload (payload), and a checksum.
  • sequence bad 1 J frame check sequence, referred to the FCS
  • TRILL Payload packets usually Payload original Ethernet frame, usually the inner Ethernet header original Ethernet frame header.
  • the fields in the TRILL header have the following meanings:
  • Ethertype Ethernet type, 16 bits (bit); usually, the Ethernet type of the TRILL data frame is TRILL, and the Ethernet type of the TRILL IS-IS frame is L2-IS-IS;
  • R reserved field, 2 bits (bit);
  • Multicast identity 1 bit (bit); 0 is known unicast, 1 For unknown unicast/multicast/broadcast;
  • Op-Length Length of the Options field, 5 bits (bit);
  • the length of the Options field defined by Op-Length is 4 bytes. For example, the value of Op-Length is 1, then Indicates that the length of Options is 4 bytes, that is, 32 bits;
  • Hop Count hop count, 6 bits (bit); hop by hop 1, discard when the Hop Count is 0, to prevent loop storms;
  • Egress RBridge Nickname The nickname of the egress router, 16 bits, which usually identifies the packet leaving the target edge of the TRILL RB; the intermediately transmitted RB node cannot change the value of this field;
  • Ingress RBridge Nickname The nickname of the ingress RBridge, 16 bits (bit), which usually identifies the initial edge of the TRILL message.
  • the intermediate transmission RB node cannot change the value of this field.
  • Options Options, length is determined by Op-Length.
  • the outer Ethernet header and the inner Ethernet header of a TRILL packet are usually in the same format.
  • the meanings of the fields are as follows:
  • Dst-MAC destination media access control (MAC) address, 64 bits (bit);
  • Src-MAC source MAC address, 64 bits (bit);
  • Ethertype Ethernet type, 16 bits (bit);
  • VLAN tag Virtual local area network (VLAN) label information, 16 bits. It includes a 14-bit VLAN identifier (ID).
  • ID VLAN identifier
  • each RB in TRILL maintains a list of VLANs that it cares about.
  • the RB receives a TRILL message sent to itself, that is, the egress RB in the TRILL header is called the nickname of the RB, the RB decapsulates.
  • the TRILL packet check whether the VLAN ID in the inner Ethernet header is in its own VLAN list. If the VLAN ID is not in the RB, discard the TRILL packet. If the RB is in the VLAN list of the RB, Then, the TRILL decapsulated packet will continue to be processed by the RB.
  • Operations, administration, and maintenance are used to maintain the link status of the network, such as the ping, the ping, and the bidirectional forwarding detection (BFD).
  • TRILL the TRILL OAM packet, that is, the TRAMP encapsulated 0 AM packet, maintains the link state between RBs.
  • the OAM packet does not carry the VLAN ID. Therefore, you need to select a VLAN.
  • the VLAN ID of the VLAN is used as the VLAN ID in the inner Ethernet header of the TRILL OAM packet.
  • VLAN 0 or VLAN 1 is selected for TRILL OAM, that is, the VLAN ID is 0 or 1 as the VLAN ID in the inner Ethernet header of the TRILL OAM packet; however, the VLAN ID is 0.
  • the packet is usually considered to be an illegal packet type and is discarded during processing. If VLAN 0 is used for TRILL OAM, it cannot be guaranteed to be supported on each RB, and the availability of the TRILL OAM function cannot be guaranteed.
  • VLAN 1 is the default VLAN configured on the RB and is added to all ports. When VLAN 1 is used, the RB learns the MAC address that should be learned from VLAN 1 and affects the original forwarding process in VLAN 1.
  • the embodiment of the present invention provides a method for implementing a TRILL OAM packet, and the routing bridge RB and the TRILL network ensure that the TRILL OAM function is available, and no additional VLAN resources are occupied, and the RB is not learned. Learn the MAC address and affect the TRILL forwarding process.
  • an embodiment of the present invention provides a method for implementing OAM in TRILL, including:
  • the ingress RB RB encapsulation generates a first TRILL OAM packet, and the inner VLAN ID and the outer VLAN identifier of the first TRILL OAM packet are the DVLAN identifier of the TRILL where the ingress RB is located, and the first TRILL OAM packet
  • the inner destination destination MAC address is the MAC address of the egress RB, the entry RB in the TRILL header is called the nickname of the ingress RB, and the egress RB is called the nickname of the egress RB;
  • the method further includes: the ingress RB receiving a second TRILL OAM packet, where the outer VLAN ID of the second TRILL OAM packet is the DVLAN identifier
  • the exit routing bridge in the TRILL header is referred to as the nickname of the entry RB;
  • the ingress RB performs TRILL decapsulation on the second TRILL OAM packet to obtain a second OAM packet.
  • the destination MAC address of the second OAM packet is the MAC address of the ingress RB, and the VLAN identifier is the DVLAN identifier;
  • the ingress RB processes the second OAM message.
  • the first RB encapsulation generating a TRILL OAM packet includes:
  • the ingress RB finds a next hop RB according to the nickname of the egress RB;
  • the MAC address of the next hop RB is used as the outer destination MAC address, and the MAC address of the ingress RB is used as the outer source MAC address.
  • the method before the initiating the RB encapsulation to generate the first TRILL OAM packet, the method further includes:
  • the ingress RB is configured with the OAM inner VLAN designation feature, and the OAM inner VLAN designation feature is specifically the TRILL DVLAN identifier as the inner VLAN ID of the TRILL OAM.
  • the ingress RB and the egress RB are configured with the DVLAN.
  • the embodiment of the present invention provides a routing bridge RB in TRILL, including: an encapsulating module, configured to encapsulate a first TRILL OAM packet, an inner VLAN identifier and an outer layer of the first TRILL OAM packet
  • the VLAN identifier is the DVLAN identifier of the TRILL where the RB is located
  • the inner MAC address of the first TRILL OAM packet is the MAC address of the egress RB
  • the egress router in the TRILL header is called the nickname of the egress RB.
  • the sending module sends the first TRILL OAM message to the egress RB, so that the egress RB processes the first TRILL OAM message.
  • the RB further includes: a receiving module, configured to receive a second TRILL OAM packet, where the second TRILL
  • the outer VLAN ID of the OAM is the DVLAN identifier
  • the egress routing bridge in the TRILL header is called the nickname of the RB.
  • a decapsulation module configured to perform TRILL decapsulation on the second TRILL OAM packet to obtain a second OAM packet;
  • the destination MAC address of the second OAM packet is a MAC address of the RB, and the VLAN identifier is Describe the D VLAN identifier;
  • An OAM processing module configured to process the second OAM packet.
  • the encapsulating module is specifically configured to find a next hop RB according to the nickname of the egress RB
  • the MAC address of the next hop is used as the outer destination MAC address
  • the MAC address of the RB is used as the outer source MAC address.
  • the RB further includes: a feature processing module, configured to enable or disable The OAM inner VLAN can be specified as the inner VLAN ID of the TRILL OAM.
  • the DVLAN is configured on the RB.
  • an embodiment of the present invention provides a TRILL network, including an entry RB and an exit RB;
  • the ingress RB encapsulation generates a TRILL operation and maintenance management OAM message, and sends the TRILL OAM to the egress RB; wherein the TRILL OAM identifies the inner VLAN of the inner VLAN and the outer VLAN ID.
  • the DVLAN ID is identified for the specified virtual local area network of the TRILL; the media access control MAC address of the TRILL OAM packet is the MAC address of the egress RB, and the ingress RB of the TRILL header is called the nickname of the ingress RB. Routing bridge Nickname of RB;
  • the egress RB receives the TRILL OAM packet, performs TRILL decapsulation on the TRILL OAM packet, and obtains an OAM packet, and processes the OAM packet.
  • the ingress RB is specifically the RB according to the foregoing second aspect or any possible implementation manner of the second aspect.
  • the RB generates TRILL OAM in the package.
  • a DVLAN is configured and created in each RB of the TRILL. Therefore, packets with the inner VLAN that is not the RB are discarded, and the DVLAN is a legal VLAN. The packets are not checked for validity. Discard, thus ensuring the availability of TRILL OAM functionality.
  • the DVLAN ID is used as the inner VLAN ID of the TRILL OAM packet, and no additional VLAN resources are occupied.
  • the DVLAN does not learn the MAC address by default, it can also prevent the RB from learning the MAC address that should not be learned, which affects the TRILL forwarding process.
  • FIG. 1 is a schematic diagram of a package format of a TRILL packet in the prior art
  • FIG. 2 is a flowchart of a method for implementing OAM in TRILL according to an embodiment of the present invention
  • FIG. 3 is another flowchart of a method for implementing OAM in TRILL according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a TRILL network according to an embodiment of the present invention. detailed description
  • the VALN ID in the inner Ethernet header is usually called the inner VALN ID, and the identified VLAN is called the inner VLAN.
  • the VALN ID in the outer Ethernet header is called the outer VALN ID, and the identified VLAN is called For the outer VLAN.
  • the source MAC address and the destination MAC address in the outer Ethernet header are respectively referred to as the outer source MAC address and the outer destination destination MAC address; the source MAC address and the destination MAC address in the inner layer Ethernet header are respectively referred to as Inner source source MAC address and inner layer destination MAC address.
  • a DVLAN is configured in the TRILL for interworking between RBs, and the D VLAN is configured by default to not learn MAC addresses.
  • Each RB in TRILL configures and creates a DVLAN, and saves the D VLAN ID in the VLAN list for the protocol. Interactions, packet forwarding, and so on.
  • the DVLAN is the legal VLAN and the related legality check is also performed.
  • the outer VLAN ID of the TRILL packet is the default. For example, in the TRILL deployed by the carrier 1, the VLAN with the ID of 1000 is the DVLAN. In the TRILL deployed by the carrier 1, the DVLAN ID is stored in the VLAN list of each RB, 1000; and during the TRILL packet forwarding process.
  • the outer VLAN ID of the TRILL packet is 1000.
  • the VLAN with the ID 2048 is the DVLAN.
  • the VLAN list of each RB is usually saved with the DVLAN ID, 204; and the TRILL packet forwarding process is performed.
  • the outer VLAN ID of the TRILL packet is 2048.
  • FIG. 2 is a flowchart of a method for implementing OAM in TRILL according to an embodiment of the present invention, where the method includes: 201.
  • the ingress RB RB encapsulation generates a TRILL OAM packet, and the inner VLAN ID and the outer VLAN ID of the TRILL OAM packet are the designated VLAN (DVLAN) ID of the TRILL of the ingress RB.
  • the destination destination MAC address of the TRILL OAM packet is the MAC address of the egress RB.
  • the entry RB in the TRILL header is called the nickname of the ingress RB, and the egress route bridge is called the nickname of the egress RB.
  • the egress RB After receiving the TRILL OAM, the egress RB finds that the egress RB of the TRILL OAM packet is a nickname of the egress RB, that is, the nickname of the egress RB; The TRILL OAM performs the TRILL decapsulation to obtain the OAM packet.
  • the egress RB checks the VLAN identifier of the OAM packet.
  • the VLAN identifier of the OAM is the DVLAN identifier.
  • the destination MAC address of the essay is the MAC address of the egress RB, and therefore the egress RB processes the OAM.
  • the DVLAN is used for the TRILL OAM, and the DVLAN ID is used as the inner VLAN ID of the TRILL OAM packet.
  • the DVLAN is usually configured in the TRILL, and the DVLAN is created on each RB. Therefore, the packet can be avoided.
  • the layer VLAN is not the VLAN that the RB is interested in and is discarded.
  • the DVLAN is a valid VLAN. The packets are not discarded due to related legality check. This ensures the availability of the TRILL OAM function.
  • the specified DVLAN is used for TRILL 0 AM, and no additional VLAN resources are occupied.
  • FIG. 3 Another method for implementing OAM in TRILL according to an embodiment of the present invention is provided.
  • a flowchart, the method comprising:
  • Ingress RB enable 0AM inner VLAN designation feature
  • the VLAN designation feature of the OAM is as follows:
  • the DVLAN of the TRILL is used for the TRILL OAM, that is, the DVLAN ID of the TRILL is used as the inner VLAN ID of the TRILL OAM packet to implement the TRILL OAM function.
  • the DBR of the ingress RB is configured with a DVLAN; the DVLAN ID is stored in the VLAN list of the ingress RB.
  • the ingress RB enables the OAM inner VLAN designation feature.
  • the OAM inner VLAN designation feature is configured on each RB in the TRILL where the ingress RB is located. Further optionally, each RB enables the OAM inner VLAN designation feature.
  • the ingress RB encapsulation generates a first TRILL OAM packet, where an inner VLAN ID and an outer VLAN ID of the first TRILL OAM packet are the DVLAN ID.
  • the inner destination destination MAC address of the first TRILL OAM packet is the MAC address of the egress RB
  • the ingress RB of the TRILL header is called the nickname of the ingress RB
  • the egress RB is called the nickname of the egress RB.
  • the ingress RB searches for the next hop RB according to the nickname of the egress RB; and uses the MAC address of the next hop as the outer
  • the MAC address of the layer is used as the outer source MAC address.
  • the VLAN with the ID of 1000 is configured as the DVLAN.
  • the ping packet can be TRILL encapsulated by the RB1 to generate the TRILL ping report.
  • the message is sent to RB2; the inner VLAN ID and the outer VLAN ID of the TRILL ping packet are both The DVLAN ID is 1000.
  • the inner MAC address of the TRILL ping packet is the RBI MAC address, and the inner destination MAC address is the source MAC address of RB2.
  • the entry RB in the TRILL header is called the RB1 nickname and the egress route.
  • the bridge is called the nickname of RB2; the outer source MAC address is the source MAC address of RB1, and the outer destination destination MAC address is the MAC address of the next hop RB of RB1 to RB2.
  • the egress RB After receiving the first TRILL OAM packet, the egress RB finds that the egress routing bridge nickname in the TRILL header of the first TRILL OAM packet is its own nickname, that is, the nickname of the egress RB; The egress RB performs the TRILL decapsulation of the first TRILL OAM packet to obtain the first OAM packet.
  • the egress RB checks the VLAN ID of the first OAM packet, and the VLAN of the first OAM packet. The ID is a DVLAN ID, and the destination MAC address of the first OAM packet is the MAC address of the egress RB. Therefore, the egress RB processes the first OAM packet.
  • the ingress RB receives a second TRILL OAM packet.
  • the ingress RB receives the second TRILL OAM packet, and the outer VLAN ID of the second TRILL OAM packet is the DVLAN ID, and the ingress RB obtains the TRILL header of the second TRILL OAM packet. If the egress RB is not the nickname of the ingress RB, the ingress RB searches for the next hop RB according to the egress RB nickname, and uses the MAC of the next hop RB The address is used as the outer destination MAC address, and the MAC address of the ingress RB is used as the outer source MAC address to forward the second TRILL OAM packet. The process ends.
  • execution 305 is continued. 305.
  • the ingress RB performs a TRILL solution on the second TRILL OAM packet. Encapsulating, obtaining a second OAM packet; the egress routing bridge in the TRILL header of the second TRILL OAM packet is referred to as a nickname of the ingress RB;
  • the ingress RB After receiving the second TRILL OAM packet, the ingress RB finds that the egress routing bridge nickname in the TRILL header of the second TRILL OAM packet is its own nickname, that is, the nickname of the ingress RB; And the ingress RB performs TRILL decapsulation on the second TRILL OAM packet to obtain the second OAM packet.
  • the ingress RB processes the second OAM packet, where a destination MAC address of the second OAM packet is a MAC address of the ingress RB, and a VLAN ID is the DVLAN ID.
  • the ingress RB performs TRILL decapsulation on the second TRILL OAM packet, and after obtaining the second OAM packet, the ingress RB checks the VLAN ID of the second 0 AM ⁇ message;
  • the destination MAC address of the second OAM packet is the MAC address of the ingress RB, and the ingress RB processes the second OAM packet; Refer to the usual OAM processing, and details are not described herein again. In the list, the second OAM packet is discarded.
  • the DVLAN ID is used as the inner VLAN ID of the TRILL OAM packet. Since each RB in the TRILL is configured and created with a DVLAN, the packet can be avoided because the inner VLAN is not the VLAN that the RB cares about. If the DVLAN is a valid VLAN, the packets are not discarded due to the related validity check. This ensures the availability of the TRILL OAM function.
  • the DVLAN ID is specified as the inner VLAN ID of the TRILL OAM packet, and the VLAN resource is not used. The default is that the DVLAN does not learn the MAC address. The learned MAC address, which affects the TRILL forwarding process. Referring to FIG. 4, it is a structural block diagram of the RB bridge RB in the TRILL according to the embodiment of the present invention, which is used to implement the method shown in FIG. 2 and FIG. :
  • the encapsulating module 401 is configured to generate a first TRILL OAM packet, where an inner VLAN ID and an outer VLAN ID of the first TRILL OAM packet are the DVLAN ID of the TRILL, and the first TRILL OAM packet is The inner destination destination MAC address is the MAC address of the egress RB, and the egress route bridge in the TRILL header is called the nickname of the egress RB.
  • the sending module 402 is configured to send the first TRILL OAM message to the egress RB, so that the egress RB processes the first TRILL OAM message.
  • the DVLAN is configured on the RB.
  • the encapsulating module 401 is specifically configured to: find a next hop RB according to the nickname of the egress RB; use the MAC address of the next hop as the outer destination MAC address, and use the MAC address of the RB as the outer layer. Source MAC address.
  • the RB is configured with an OAM inner VLAN designation feature, and the OAM inner layer VLAN designation feature is specifically used to specify the TRILL DVLAN for the TRILL OAM, that is, the TRILL DVLAN ID is used as the TRILL OAM.
  • the inner VLAN ID of the packet to implement the TRILL OAM function is configured with an OAM inner VLAN designation feature, and the OAM inner layer VLAN designation feature is specifically used to specify the TRILL DVLAN for the TRILL OAM, that is, the TRILL DVLAN ID is used as the TRILL OAM.
  • the RB further includes:
  • the feature processing module is used to enable or disable the OAM inner VLAN designation feature. Further, as shown in FIG. 5, the RB may further include:
  • the receiving module 403 is configured to receive the second TRILL OAM packet, where the outer VLAN ID of the second TRILL OAM is the DVLAN ID, and the egress routing bridge in the TRILL header is called the nickname of the RB.
  • the decapsulation module 404 is configured to perform TRILL on the second TRILL OAM packet. Decapsulating, obtaining a second OAM message;
  • the OAM processing module 405 is configured to process the second OAM packet.
  • the destination MAC address of the second OAM packet is a MAC address of the RB, and the VLAN ID is the DVLAN ID.
  • the OAM processing module 405 is further configured to generate a second response message that is responsive to the second TRILL OAM.
  • the encapsulating module 401 is further configured to perform TRILL encapsulation on the second response packet.
  • the sending module 402 is further configured to send the second response packet after the TRILL encapsulation.
  • the receiving module 403 is further configured to receive the first response packet of the egress RB to the first TRILL OAM packet.
  • the decapsulation module 404 is further configured to perform TRILL decapsulation on the first response packet.
  • the OAM processing module 405 is further configured to process the first response after the TRILL is decapsulated.
  • the RB uses the DVLAN ID as the inner VLAN ID of the TRILL OAM packet. Since each RB in the TRILL is configured and created with a DVLAN, the packet can be avoided because the inner VLAN is not the RB. The VLAN is discarded, and the DVLAN is a legal VLAN. The packets are not discarded due to legality check, thus ensuring the availability of the TRILL OAM function.
  • the DVLAN ID is specified as the internal VLAN ID of the TRILL OAM, and the VLAN resource is not used. The default is that the DVLAN does not learn the MAC address. .
  • the RB includes a processor 601, a memory 602, a communication interface 603, and a bus 604.
  • the processor 601, the memory 602, and the communication interface 603 pass The bus 604 is connected to each other; the bus 604 may be a peripheral component interconnect (PCI) bus or an extended industry standard structure (extended industry) Standard architecture, referred to as EISA) bus.
  • PCI peripheral component interconnect
  • EISA extended industry standard structure
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 6, but it does not mean that there is only one bus or one type of bus.
  • the memory 602 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 602 may include a high-speed RAM memory, and may also include a non-volatile memory (nvm), such as an electrically erasable and programmable read only memory (EEPROM). Flash (Flash), etc.
  • nvm non-volatile memory
  • EEPROM electrically erasable and programmable read only memory
  • Flash Flash
  • the processor 601 executes a program stored in the memory 602, and is configured to encapsulate and generate a first TRILL OAM packet, where an inner VLAN ID and an outer VLAN ID of the first TRILL OAM packet are DVLAN IDs of the TRILL;
  • the inner destination destination MAC address of the first TRILL OAM packet is the MAC address of the egress RB, the ingress RB of the TRILL header is called the nickname of the RB, and the egress RB is called the nickname of the egress RB.
  • the first TRILL OAM message is sent to the egress RB, so that the egress RB processes the first TRILL OAM message.
  • the DVLAN is configured on the RB.
  • the processor 601 is specifically configured to: find a next hop RB according to the nickname of the egress RB; use the MAC address of the next hop as the outer destination MAC address, and use the MAC address of the RB as the outer source.
  • the MAC address is encapsulated to generate the first TRILL OAM packet.
  • the RB is configured with an OAM inner VLAN designation feature
  • the inner VLAN designation feature is specifically configured to specify the TRILL DVLAN for the TRILL layer VLAN ID to implement the TRILL OAM function.
  • the processor 601 is further configured to Can or disable the inner VLAN designation feature.
  • the processor 601 is further configured to receive a second TRILL OAM packet, where an outer VLAN ID of the second TRILL OAM packet is the DVLAN ID, and an egress routing bridge in the TRILL header is referred to as the a nickname of the RB; performing a TRILL decapsulation on the second TRILL OAM packet, obtaining a second OAM packet, and processing the second OAM packet, where the destination MAC address of the second OAM packet is the RB MAC address, the VLAN ID is the DVLAN ID.
  • the processor 601 is configured to receive the second TRILL OAM packet, and obtain an exit routing bridge nickname in a TRILL header of the second TRILL OAM packet; if the egress routing bridge nickname is not the ingress RB The nickname, the next hop RB is found according to the egress RB nickname, and the MAC address of the next hop RB is used as the outer destination MAC address, and the MAC address of the RB is used as the outer source MAC address, and the nickname is forwarded.
  • the second TRILL OAM packet if the egress routing bridge is called the nickname of the RB, performing TRILL decapsulation on the second TRILL OAM packet to obtain a second OAM packet, where the ingress RB check The VLAN ID of the second OAM packet; if the VLAN ID of the second OAM packet is a DVLAN ID, the destination MAC address of the second OAM packet is the MAC address of the ingress RB, and the ingress RB And processing the second OAM packet; if the VLAN ID of the second OAM packet is not in the VLAN list of the ingress RB, discarding the second OAM packet.
  • the RB is configured to generate a TRILL OAM packet by using the DVLAN ID as the inner VLAN ID of the TRILL OAM packet, and the RBs in the TRILL are usually configured and created by the DVLAN.
  • the packet is discarded because the inner VLAN is not the VLAN that the RB is interested in, and the DVLAN is a valid VLAN.
  • the packets are not discarded due to legality check. This ensures the availability of the TRILL OAM function.
  • specify the DVLAN ID as TRILL OAM
  • the inner VLAN ID of the packet does not occupy any additional VLAN resources.
  • FIG. 7 is a schematic diagram of a TRILL network according to an embodiment of the present invention, where the TRILL includes an ingress RB RB and an egress RB;
  • the ingress RB encapsulation generates a TRILL OAM packet, and sends the TRILL OAM packet to the egress RB.
  • the inner VLAN ID and the outer VLAN ID of the TRILL OAM packet are the DVLAN ID of the TRILL.
  • the inner destination destination MAC address of the TRILL OAM packet is the MAC address of the egress RB, the ingress RB of the TRILL header is called the nickname of the ingress RB, and the egress routing bridge is called the nickname of the egress RB.
  • the egress RB receives the TRILL OAM packet, performs TRILL decapsulation on the TRILL OAM packet, obtains an OAM packet, and processes the OAM packet.
  • the TRILL network configures the DVLAN; the ingress RB and the egress RB configure and create the DVLAN.
  • the egress RB after receiving the TRILL OAM packet, the egress RB obtains an egress routing bridge nickname of the TRILL OAM packet, and the egress RB is called a nickname of the egress RB, and the TRILL OAM
  • the TRILL decapsulation is performed to obtain an OAM packet.
  • the VLAN ID of the OAM packet is a DVLAN ID
  • the destination MAC address is the MAC address of the egress RB.
  • the egress RB processes the OAM packet. The usual OAM processing will not be described here.
  • entry RB specifically includes:
  • An encapsulation module configured to encapsulate and generate the TRILL OAM packet
  • a sending module configured to send the TRILL OAM to the egress RB.
  • the ingress RB is configured with an OAM inner VLAN designation feature.
  • the DAM inner VLAN designation feature is specifically configured to specify the DILL of the TRILL for the TRILL OAM, that is, the DVLAN ID is used as the inner VLAN ID of the TRILL OAM packet.
  • the ingress RB enables the VLAN-specific feature of the OAM inner layer.
  • the DVLAN ID of the TRILL is used as the inner VLAN ID.
  • the ingress RB further includes a feature processing module, configured to enable or disable the OAM inner VLAN designation feature.
  • exit RB specifically includes:
  • a receiving module configured to receive the TRILL OAM packet
  • a decapsulation module configured to perform TRILL decapsulation on the TRILL OAM packet to obtain the OAM packet
  • An OAM processing module configured to process the OAM.
  • the TRILL network uses the DVLAN for the TRILL OAM. Since the RBs of the TRILL are configured and created by the RBs, the packets are discarded because the inner VLAN is not the VLAN of the RB. The DVLAN is a valid VLAN. The packets are not discarded because of the validity check. This ensures the availability of the TRILL OAM function.
  • the DVLAN ID is used as the inner VLAN ID of the TRILL OAM packet, and the VLAN resource is not used. The default is that the DVLAN does not learn the MAC address. This prevents the RB from learning the MAC address that cannot be learned, which affects the TRILL forwarding process.

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

本发明实施例公开了TRILL中OAM实现方法、RB和TRILL网络，通过指定TRILL的DVLAN用于TRILL OAM，使得TRILL OAM报文的内层VLAN ID和外层VLAN ID都为DVLAN ID，保证了TRILL OAM功能的可用性。

Description

一种 TRILL 0AM报文实现方法， RB和 TRILL网络 技术领域
本发明实施例涉及网络通信领域， 尤其涉及一种 TRILL OAM报 文实现方法， RB和 TRILL网络。 背景技术
多链接透明互联 ( transparent interconnection of lots of links , 简称 TRILL )是一种应用于路由桥（ router bridge或 RBridge, 简称 RB )设 备的协议。 TRILL运行在数据链路层（ data link layer ), 即开放式系统 互联 (open system interconnection , 简称 0SI)参考模型中的二层 ( layer 2 , 简称 L2 ) , 使用基于中间系统到中间系统 ( Intermediate system to intermediate system, IS-IS )的链路状态路由技术来扩散和通告拓朴以 及逻辑网络的成员关系， 将链路状态路由技术应用在数据链路层， 在 传统以太网架构上提供了逻辑的以太网。
如图 1所示， 为一种 TRILL报文的封装格式， 包括外层以太网 头（ Outer Ethernet Header ), TRILL头， 内层以太网头（ Inner Ethernet Header ), 载荷 ( Payload )和贞校验序歹1 J ( frame check sequence , 简 称 FCS );其中， TRILL报文的 Payload通常是原始以太网帧的 Payload, 内层以太网头通常是原始以太网帧的头。 其中 TRILL头中各个字段 含义如下：
Ethertype: 以太类型， 16比特 ( bit ) ； 通常 TRILL数据帧的以太 类型为 TRILL, TRILL IS-IS帧的以太类型为 L2-IS-IS;
V (Version): TRILL版本号， 2比特 ( bit ) ；
R (Reserved): 保留字段， 2比特（bit ) ；
M (Multi-destination): 多播标识， 1比特（bit ) ; 0为已知单播， 1 为未知单播 /组播 /广播；
Op-Length (Options Length): 选项（Options)字段的长度， 5比特 (bit); Op-Length定义的 Options字段的长度以 4个字节为单位，例如， Op-Length的值为 1, 则表示 Options的长度为 4个字节， 也即 32比特 (bit) ；
Hop Count: 跳数， 6比特（bit) ; 逐跳减 1, Hop Count为 0时丟弃， 以防止环路风暴；
Egress RBridge Nickname: 出口路由桥昵称， 16比特（bit) , 通 常标识报文离开 TRILL的目标边缘 RB; 中间传输的 RB节点不能改变 此字段的值；
Ingress RBridge Nickname: 入口路由桥昵称， 16比特 (bit) , 通 常标识报文进入 TRILL的初始边缘 RB; 中间传输 RB节点不能改变此 字段的值；
Options： 选项， 长度由 Op-Length确定。
TRILL报文的外层以太网头和内层以太网头格式通常一样 ,各个 字段含义如下：
Dst-MAC: 目的介质访问控制（ media access control, 简称 MAC ) 地址， 64比特（bit);
Src-MAC: 源 MAC地址， 64比特（bit);
Ethertype: 以太网类型， 16比特（ bit );
VLAN Tag: 虚拟局域网（ virtual local area network, 简称 VLAN ) 标签信息， 16 比特（bit); 其中包括 14 比特（bit) 的 VLAN标识 (identifier, 简称 ID)。
TRILL报文在 RB之间转发时， TRILL头中， 除了 Hop Count逐 跳减 1, 其他字段保持不变。 内层以太网头和 Payload的内容不变， 而外层以太网头的源 MAC地址和目的 MAC地址逐跳更新。
通常 TRILL中每个 RB会维护一张自己关心的 VLAN列表， 当 RB 收到发给自己的 TRILL报文， 即 TRILL头中的出口路由桥昵称为所述 RB的昵称时， 所述 RB解封装该 TRILL报文， 并检查内层以太网头中 的 VLAN ID是否在自己的 VLAN列表中，如果不在该 RB的 VLAN列表 中， 则丟弃该 TRILL报文； 如果在该 RB的 VLAN列表中， 则 TRILL解 封装后的报文会被该 RB继续处理。
操作维护管理 ( operations, administration and maintenance , 简称 OAM)才艮文， 例 口 ping, 双向转发检测 ( bidirectional forwarding detection, 简称 BFD )等报文， 是用于维护网络中链路状态的报文； 在 TRILL中， 通过 TRILL OAM报文， 即 TRILL封装后的 0 AM报文， 可以维护 RB间的链路状态。 通常 OAM报文中没有携带 VLAN ID , 因 此需要选择一个 VLAN,将该 VLAN的 VLAN ID作为 TRILL OAM报文 的内层以太网头中的 VLAN ID , 封装生成的 TRILL OAM报文到达目 标 RB时， 才可能被该目标 RB处理。
现有技术一中， 选择 VLAN 0 或者 VLAN 1用于 TRILL OAM, 即， 选择 VLAN ID为 0或 1 , 作为 TRILL OAM报文的内层以太网头中 的 VLAN ID; 但是， 携带 VLAN ID为 0的报文通常被认定为非法的报 文类型， 在处理过程中被丟弃； 如果将 VLAN 0用于 TRILL OAM, 将 无法保证在各个 RB上都支持， 从而无法保证 TRILL OAM功能的可用 性； 而 VLAN 1通常是 RB上默认配置的 VLAN, 并加入所有端口， 使 用 VLAN 1将导致 RB在进行 OAM处理时， 从 VLAN 1内学习到不应该 学习的 MAC地址， 影响 VLAN 1内原有的转发流程。
现有技术二， 通过配置一个保留 VLAN, 用于 TRILL OAM; 但 是， 由于 TRILL中各个设备的厂商、 形态等不统一， 往往无法保证保 留统一的 VLAN; 如果一个 RB上配置的保留 VLAN, 其他 RB上并没 有创建， 则 TRILL OAM报文仍会被丟弃， 无法真正实现 TRILL OAM 功能； 此外， 当下 VLAN资源紧缺， 配置保留 VLAN用于 OAM, 也额 外占用了 VLAN资源。 发明内容
有鉴于此， 本发明实施例提供了一种 TRILL OAM报文实现方法， 路由桥 RB和 TRILL网络，在保证 TRILL OAM功能可用的同时， 没有 额外占用 VLAN资源， 也不会使 RB学习到不应该学习的 MAC地址、 而影响 TRILL转发流程。
第一方面， 本发明实施例提供了一种 TRILL中 OAM实现方法， 包括：
入口路由桥 RB封装生成第一 TRILL OAM报文 ,所述第一 TRILL OAM报文的内层 VLAN标识和外层 VLAN标识为所述入口 RB所在 TRILL的 DVLAN标识 ,所述第一 TRILL OAM报文的内层目的 MAC 地址为出口 RB的 MAC地址， TRILL头中入口路由桥昵称为所述入 口 RB的昵称， 出口路由桥昵称为所述出口 RB的昵称；
发送所述第一 TRILL OAM报文至所述出口 RB, 以使所述出口 RB处理所述第一 TRILL OAM报文。
在第一方面的第一种可能实现方式中， 所述方法还包括 ： 所述入口 RB接收第二 TRILL OAM报文，所述第二 TRILL OAM 才艮文的外层 VLAN标识为所述 DVLAN标识， TRILL头中的出口路 由桥昵称为所述入口 RB的昵称；
所述入口 RB对所述第二 TRILL OAM报文进行 TRILL解封装， 得到第二 OAM报文； 所述第二 OAM报文的目的 MAC地址为所述 入口 RB的 MAC地址， VLAN标识为所述 DVLAN标识； 所述入口 RB处理所述第二 OAM报文。
结合第一方面或第一方面的第一种可能实现方式，在第一方面的 第二种可能实现方式中， 所述第一 RB封装生成 TRILL OAM报文包 括：
所述入口 RB根据所述出口 RB的昵称查找出下一跳 RB;
将所述下一跳 RB的 MAC地址作为外层目的 MAC地址， 将所 述入口 RB的 MAC地址作为外层源 MAC地址。
结合第一方面或第一方面的第一种或第二种可能实现方式，在所 述入口 RB封装生成第一 TRILL OAM报文之前 , 还包括：
所述入口 RB使能 OAM内层 VLAN指定特性， 所述 OAM内层 VLAN指定特性具体为指定 TRILL的 DVLAN标识作为 TRILL OAM 才艮文的内层 VLAN标识。
结合第一方面或第一方面的上述任一种可能实现方式，在第一方 面的第四种可能实现方式中， 所述入口 RB和所述出口 RB配置了所 述 DVLAN。
第二方面，本发明实施例提供了一种 TRILL中路由桥 RB,包括： 封装模块，用于封装生成第一 TRILL OAM报文，所述第一 TRILL OAM报文的内层 VLAN标识和外层 VLAN标识为所述 RB 所在 TRILL的 DVLAN标识 ,所述第一 TRILL OAM报文的内层目的 MAC 地址为出口 RB的 MAC地址， TRILL头中的出口路由桥昵称为所述 出口 RB的昵称；
发送模块， 发送所述第一 TRILL OAM报文至所述出口 RB, 以 使所述出口 RB处理所述第一 TRILL OAM报文。
在第二方面的第一种可能实现方式中， 所述 RB还包括 ： 接收模块， 用于接收第二 TRILL OAM报文， 所述第二 TRILL OAM ^艮文的外层 VLAN标识为所述 DVLAN标识， TRILL头中的出 口路由桥昵称为所述 RB的昵称；
解封装模块， 用于对所述第二 TRILL OAM报文进行 TRILL解 封装， 得到第二 OAM报文； 所述第二 OAM报文的目的 MAC地址 为所述 RB的 MAC地址 , VLAN标识为所述 D VLAN标识；
OAM处理模块， 用于处理所述第二 OAM报文。
结合第二方面或第二方面的第一种可能实现方式，在第二方面的 第二种可能实现方式中， 所述封装模块， 具体用于根据所述出口 RB 的昵称查找出下一跳 RB; 将所述下一跳 RB的 MAC地址作为外层 目的 MAC地址， 将所述 RB的 MAC地址作为外层源 MAC地址。
结合第二方面或第二方面的第一种或第二种可能实现方式，在第 二方面的第三种可能实现方式中， 所述 RB还包括： 特性处理模块， 用于使能或去使能 OAM内层 VLAN指定特性，所述 OAM内层 VLAN 指定特性具体为指定 TRILL的 DVLAN标识作为 TRILL OAM 4艮文 的内层 VLAN标识。
结合第二方面或第二方面的上述任一种可能实现方式，在第二方 面的第四种可能实现方式中， 所述 RB上配置了所述 DVLAN。
第三方面， 本发明实施例提供了一种 TRILL网络， 包括入口 RB 和出口 RB;
所述入口 RB封装生成 TRILL操作维护管理 OAM 艮文， 发送 所述 TRILL OAM才艮文至所述出口 RB; 其中， 所述 TRILL OAM才艮 文的内层虚拟局域网标识 VLAN ID和外层 VLAN ID为所述 TRILL 的指定虚拟局域网标识 DVLAN ID; 所述 TRILL OAM报文的内层目 的介质访问控制 MAC地址为出口 RB的 MAC地址， TRILL头中入 口路由桥昵称为所述入口 RB 的昵称， 出口路由桥昵称为所述出口 RB的昵称；
所述出口 RB接收所述 TRILL OAM报文， 对所述 TRILL OAM 报文进行 TRILL解封装， 得到 OAM报文， 处理所述 OAM报文。
在第三方面的第一种可能实现方式中， 所述入口 RB具体为上述 第二方面或第二方面任一可能实现方式所述的 RB。
釆用本发明实施例提供的技术方案， RB在封装生成 TRILL OAM
TRILL中各个 RB通常都配置和创建了 DVLAN, 因此可以避免报文因 内层 VLAN不是 RB所关心的 VLAN被丟弃， 且 DVLAN是合法 VLAN, 报文也不会因相关的合法性检查而被丟弃， 从而保证了 TRILL OAM 功能的可用性。 同时， 指定 DVLAN标识作为 TRILL OAM报文内层 VLAN标识， 也不额外占用 VLAN资源。 此外， 由于 DVLAN默认为不 学习 MAC地址， 因此也可避免 RB学到不该学习的 MAC地址， 影响 TRILL转发流程。 附图说明
图 1是现有技术中一种 TRILL报文的封装格式示意图；
图 2是本发明实施例提供的 TRILL中 OAM实现方法的流程图； 图 3是本发明实施例提供的 TRILL中 OAM实现方法的另一流程图；
图 7是本发明实施例提供的 TRILL网络示意图。 具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术 方案进行清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发 明的一部分实施例， 而不是全部的实施例。 基于本发明中的实施 例， 本领域普通技术人员在没有做出创造性劳动前提下所获得的 所有其他实施例， 都属于本发明保护的范围。
通常将内层以太网头中的 VALN ID称为内层 VALN ID , 所标识 的 VLAN称为内层 VLAN; 将外层以太网头中的 VALN ID称为外层 VALN ID , 所标识的 VLAN称为外层 VLAN。 将外层以太网头中的 源 MAC地址和目的 MAC地址， 分别称为外层源 MAC地址和外层 目的 MAC地址； 将内层以太网头中的源 MAC地址和目的 MAC地 址， 分别称为内层源 MAC地址和内层目的 MAC地址。
通常 TRILL中会配置一个 DVLAN用于 RB间的互联互通，并且 D VLAN默认配置为不学习 MAC地址； TRILL中的各个 RB会配置 并创建 DVLAN, 将 D VLAN ID保存在 VLAN列表中， 用于协议交 互、 报文转发等； 在 TRILL中 DVLAN作为合法 VLAN, 也能够满 足相关的合法性检查； TRILL报文的外层 VLAN ID通常默认使用 DVLAN ID。 例如， 运营商 1部署的 TRILL中， 指定 ID为 1000的 VLAN为 DVLAN, 在运营商 1部署的 TRILL中， 各个 RB的 VLAN 列表中都保存了 DVLAN ID, 1000; 并且在 TRILL报文转发过程中 会检查 TRILL报文的外层 VLAN ID是否为 1000。而在运营商 2部署 的 TRILL中， 指定 ID为 2048的 VLAN为 DVLAN, 在运营商 2部 署的 TRILL中，各个 RB的 VLAN列表中通常都保存了 DVLAN ID, 204;并且在 TRILL报文转发过程中会检查 TRILL报文的外层 VLAN ID是否为 2048。 参见图 2,为本发明实施例提供的 TRILL中 OAM实现方法的流 程图， 所述方法包括： 201、 入口路由桥 RB封装生成 TRILL OAM报文， 所述 TRILL OAM报文的内层 VLAN ID和外层 VLAN ID为所述入口 RB所在 TRILL的指定虚拟局域网 （ Designated VLAN, 简称 DVLAN ) ID;
所述 TRILL OAM报文的内层目的 MAC地址为出口 RB的 MAC 地址， TRILL头中入口路由桥昵称为所述入口 RB的昵称， 出口路由 桥昵称为所述出口 RB的昵称。
202、发送所述 TRILL OAM报文至所述出口 RB, 以使所述出口 RB处理所述 TRILL OAM报文。
所述出口 RB收到所述 TRILL OAM才艮文后， 发现所述 TRILL OAM报文的 TRILL头中的出口路由桥昵称是自己的昵称， 即所述出 口 RB的昵称； 则所述出口 RB对所述 TRILL OAM才艮文进行 TRILL 解封装， 得到 OAM报文； 首先所述出口 RB检查所述 OAM报文的 VLAN标识， 由于所述 OAM ^艮文的 VLAN标识为 DVLAN标识，所 述 OAM ^艮文的目的 MAC地址为所述出口 RB的 MAC地址， 因此 所述出口 RB处理所述 OAM才艮文。
本发明实施例中，指定 DVLAN用于 TRILL OAM,将 DVLAN ID 作为 TRILL OAM报文的内层 VLAN ID, 由于 TRILL中通常都会配 置 DVLAN, 每个 RB上创建了 DVLAN, 因此可以避免报文因内层 VLAN不是 RB 所关心的 VLAN 而被丟弃， 并且 DVLAN是合法 VLAN , 报文也不会因相关的合法性检查而被丟弃， 从而保证了 TRILL OAM功能的可用性。 同时， 指定 DVLAN用于 TRILL 0 AM, 也不额外占用 VLAN资源。 此外， 由于 DVLAN默认为不学习 MAC 地址， 因此也可避免 RB学到不该学习的 MAC地址， 影响 TRILL转 发流程。 参见图 3 ,为本发明实施例提供的 TRILL中 OAM实现方法的另 一流程图， 所述方法包括：
301、 入口 RB使能 0AM内层 VLAN指定特性；
所述 OAM内层 VLAN指定特性具体为：指定 TRILL的 DVLAN 用于 TRILL OAM, 即， 将 TRILL的 DVLAN标识作为 TRILL OAM 报文的内层 VLAN标识， 以实现 TRILL OAM功能。
本发明中 , 所述入口 RB所在 TRILL配置了 DVLAN; 所述入口 RB的 VLAN列表中保存有所述 DVLAN ID。 所述入口 RB使能所述 OAM内层 VLAN指定特性。
可选地，所述入口 RB所在 TRILL中各个 RB上配置了所述 OAM 内层 VLAN指定特性。 进一步可选地， 各个 RB使能所述 OAM内层 VLAN指定特性。
302、 所述入口 RB封装生成第一 TRILL OAM报文， 所述第一 TRILL OAM报文的内层 VLAN ID和外层 VLAN ID为所述 DVLAN ID;
所述第一 TRILL OAM报文的内层目的 MAC地址为出口 RB的 MAC地址， TRILL头中入口路由桥昵称为所述入口 RB的昵称， 出 口路由桥昵称为所述出口 RB的昵称。
可选地，在所述入口 RB封装生成第一 TRILL OAM报文过程中， 所述入口 RB根据所述出口 RB的昵称查找出下一跳 RB; 将所述下 一跳 RB的 MAC地址作为外层目的 MAC地址， 将所述入口 RB的 MAC地址作为外层源 MAC地址。
举例来说，在运营商 1部署的 TRILL中，配置 ID为 1000的 VLAN 作为 DVLAN, 当需要测试 RB1 和 RB2之间的连通性时， 可以由 RB1将 Ping报文进行 TRILL封装， 生成 TRILL Ping报文， 发送到 RB2； 该 TRILL Ping报文的内层 VLAN ID和外层 VLAN ID均为该 DVLAN ID,即 1000;该 TRILL Ping报文的内层源 MAC地址为 RBI 的 MAC地址， 内层目的 MAC地址为 RB2的源 MAC地址； TRILL 头中的入口路由桥昵称为 RB1的昵称，出口路由桥昵称为 RB2的昵 称； 外层源 MAC地址为 RB1的源 MAC地址， 外层目的 MAC地址 为 RB1到 RB2的下一跳 RB的 MAC地址。
303、发送所述第一 TRILL OAM报文至所述出口 RB, 以使所述 出口 RB处理所述第一 TRILL OAM报文。
所述出口 RB收到所述第一 TRILL OAM报文后， 发现所述第一 TRILL OAM报文的 TRILL头中的出口路由桥昵称是自己的昵称，即 所述出口 RB的昵称； 则所述出口 RB对所述第一 TRILL OAM报文 进行 TRILL解封装， 得到第一 OAM报文； 首先所述出口 RB检查所 述第一 OAM报文的 VLAN ID,由于所述第一 OAM报文的 VLAN ID 为 DVLAN ID,所述第一 OAM报文的目的 MAC地址为所述出口 RB 的 MAC地址， 因此所述出口 RB处理所述第一 OAM报文。
304、 所述入口 RB接收第二 TRILL OAM报文；
具体地， 所述入口 RB接收第二 TRILL OAM报文， 所述第二 TRILL OAM报文的外层 VLAN ID为所述 DVLAN ID , 所述入口 RB 获取所述第二 TRILL OAM报文的 TRILL头中的出口路由桥昵称； 若所述出口路由桥昵称不是所述入口 RB 的昵称， 则所述入口 RB根据所述出口路由桥昵称查找出下一跳 RB, 并用所述下一跳 RB 的 MAC地址作为外层目的 MAC地址，用所述入口 RB的 MAC地址 作为外层源 MAC地址， 转发所述第二 TRILL OAM报文； 本流程结 束。
若所述出口路由桥昵称为所述入口 RB的昵称，则继续执行 305。 305、 所述入口 RB对所述第二 TRILL OAM报文进行 TRILL解 封装，得到第二 OAM报文； 所述第二 TRILL OAM报文的 TRILL头 中的出口路由桥昵称为所述入口 RB的昵称；
具体地， 所述入口 RB收到所述第二 TRILL OAM报文后， 发现 所述第二 TRILL OAM报文的 TRILL头中的出口路由桥昵称是自己 的昵称， 即所述入口 RB的昵称； 则所述入口 RB对所述第二 TRILL OAM报文进行 TRILL解封装， 得到所述第二 OAM报文。
306、 所述入口 RB处理所述第二 OAM报文， 所述第二 OAM报 文的目的 MAC地址为所述入口 RB的 MAC地址， VLAN ID为所述 DVLAN ID。
具体地， 所述入口 RB对所述第二 TRILL OAM报文进行 TRILL 解封装， 得到所述第二 OAM报文之后， 所述入口 RB检查所述第二 0 AM ^艮文的 VLAN ID;
如果所述第二 OAM报文的 VLAN ID为 DVLAN ID, 所述第二 OAM报文的目的 MAC地址为所述入口 RB的 MAC地址，所述入口 RB处理所述第二 OAM报文； 过程可以参考通常的 OAM处理， 在 此不再赘述。 列表中， 丟弃所述第二 OAM报文。
本发明实施例中， 用 DVLAN ID作为 TRILL OAM报文的内层 VLAN ID, 由于 TRILL中各个 RB通常都配置和创建了 DVLAN, 因 此可以避免报文因内层 VLAN不是 RB所关心的 VLAN而被丟弃， 并且 DVLAN是合法 VLAN,报文也不会因相关的合法性检查而被丟 弃， 从而保证了 TRILL OAM功能的可用性。 此外， 指定 DVLAN ID 作为 TRILL OAM报文内层 VLAN ID , 也不额外占用 VLAN资源； 并且由于 DVLAN默认为不学习 MAC地址， 也可避免 RB学到不该 学习的 MAC地址， 影响 TRILL转发流程^ 参见图 4,为本发明实施例提供的 TRILL中的路由桥 RB的结构 框图， 用于实现本发明图 2和图 3所示的方法， 所述 RB包括：
封装模块 401 , 用于封装生成第一 TRILL OAM报文， 所述第一 TRILL OAM报文的内层 VLAN ID和外层 VLAN ID为所述 TRILL 的 DVLAN ID, 所述第一 TRILL OAM报文的内层目的 MAC地址为 出口 RB的 MAC地址， TRILL头中的出口路由桥昵称为所述出口 RB 的昵称；
发送模块 402, 用于发送所述第一 TRILL OAM报文至所述出口 RB , 以使所述出口 RB处理所述第一 TRILL OAM报文。
所述 RB上配置所述 DVLAN。
所述封装模块 401， 具体用于根据所述出口 RB的昵称查找出下 一跳 RB; 将所述下一跳 RB的 MAC地址作为外层目的 MAC地址 , 将所述 RB的 MAC地址作为外层源 MAC地址。
可选的， 所述 RB上配置有 OAM内层 VLAN指定特性， 所述 OAM内层 VLAN指定特性具体为指定所述 TRILL的 DVLAN用于 TRILL OAM, 即， 将所述 TRILL的 DVLAN ID作为 TRILL OAM报 文的内层 VLAN ID, 以实现 TRILL OAM功能。
可选地， 所述 RB还包括：
特性处理模块， 用于使能或去使能 OAM内层 VLAN指定特性。 进一步的， 如图 5所示， 所述 RB还可以包括：
接收模块 403 ,用于接收第二 TRILL OAM报文，所述第二 TRILL OAM才艮文的外层 VLAN ID为所述 DVLAN ID, TRILL头中的出口 路由桥昵称为所述 RB的昵称；
解封装模块 404 , 用于对所述第二 TRILL OAM报文进行 TRILL 解封装， 得到第二 OAM报文；
OAM处理模块 405 , 用于处理所述第二 OAM报文； 所述第二 OAM报文的目的 MAC地址为所述 RB的 MAC地址， VLAN ID为 所述 DVLAN ID。
进一步可选地， 所述 OAM处理模块 405, 还可用于生成响应所 述第二 TRILL OAM的第二响应报文。 所述封装模块 401 , 还可用于 对所述第二响应报文进行 TRILL封装。 所述发送模块 402,还可用于 发送所述 TRILL封装后的第二响应报文。
可选地， 所述接收模块 403 , 还可用于接收所述出口 RB对所述 第一 TRILL OAM报文的第一响应报文。 所述解封装模块 404, 还可 用于对所述第一响应报文进行 TRILL解封装。 所述 OAM处理模块 405, 还可用于处理所述 TRILL解封后的第一响应 ^艮文。
本发明实施例中，所述 RB用 DVLAN ID作为 TRILL OAM报文 的内层 VLAN ID , 由于 TRILL 中各个 RB 通常都配置并创建了 DVLAN, 因此可以避免报文因内层 VLAN不是 RB所关心的 VLAN 而被丟弃， 并且 DVLAN是合法 VLAN,报文也不会因为合法性检查 而被丟弃， 从而保证了 TRILL OAM 功能的可用性。 此外， 指定 DVLAN ID作为 TRILL OAM才艮文内层 VLAN ID, 也不额外占用 VLAN资源； 并且由于 DVLAN默认为不学习 MAC地址 , 也可避免 RB学到不该学习的 MAC地址， 影响 TRILL转发流程。
参见图 6,为本发明实施例提供的 TRILL中路由桥 RB的硬件结 构示意图， 所述 RB包括处理器 601、 存储器 602、 通信接口 603和 总线 604; 处理器 601、 存储器 602、 通信接口 603通过总线 604相 互连接； 总线 604 可以是外设部件互连标准 （peripheral component interconnect, 简称 PCI )总线或扩展工业标准结构 ( extended industry standard architecture, 简称 EISA )总线等。 所述总线可以分为地址总 线、数据总线、控制总线等。为便于表示， 图 6中仅用一条粗线表示， 但并不表示仅有一根总线或一种类型的总线。
存储器 602, 用于存放程序。 具体地， 程序可以包括程序代码， 所述程序代码包括计算机操作指令。 存储器 602可能包含高速 RAM 存储器， 也可能还包括非易失性存储器 （non-volatile memory, 简称 nvm ) , 例如电可擦可编程只读存储器 （ electrically erasable and programmable read only memory,简称为 EEPROM )和闪存 ( Flash ) 等。
处理器 601执行存储器 602所存放的程序， 用于封装生成第一 TRILL OAM报文，所述第一 TRILL OAM报文的内层 VLAN ID和外 层 VLAN ID为所述 TRILL的 DVLAN ID; 所述第一 TRILL OAM报 文的内层目的 MAC地址为出口 RB的 MAC地址， TRILL头中入口 路由桥昵称为所述 RB的昵称， 出口路由桥昵称为所述出口 RB的昵 称； 还用于发送所述第一 TRILL OAM报文至所述出口 RB, 以使所 述出口 RB处理所述第一 TRILL OAM报文。
所述 RB上配置所述 DVLAN。
所述处理器 601具体用于根据所述出口 RB的昵称查找出下一跳 RB; 将所述下一跳 RB的 MAC地址作为外层目的 MAC地址， 将所 述 RB的 MAC地址作为外层源 MAC地址， 以封装生成所述第一 TRILL OAM报文。
可选的， 所述 RB上还配置有 OAM内层 VLAN指定特性， 所述 内层 VLAN指定特性具体为指定所述 TRILL的 DVLAN用于 TRILL 层 VLAN ID, 以实现 TRILL OAM功能。 所述处理器 601 , 还用于使 能或去使能内层 VLAN指定特性。
进一步地， 所述处理器 601 , 还可用于接收第二 TRILL OAM报 文，所述第二 TRILL OAM报文的外层 VLAN ID为所述 DVLAN ID, TRILL头中的出口路由桥昵称为所述 RB的昵称；对所述第二 TRILL OAM报文进行 TRILL解封装， 得到第二 OAM报文， 并处理所述第 二 OAM报文， 所述第二 OAM报文的目的 MAC地址为所述 RB的 MAC地址 , VLAN标识为所述 DVLAN ID。
所述处理器 601 , 具体用于接收所述第二 TRILL OAM报文， 获 取所述第二 TRILL OAM报文的 TRILL头中的出口路由桥昵称； 若 所述出口路由桥昵称不是所述入口 RB的昵称， 则根据所述出口路由 桥昵称查找出下一跳 RB , 并用所述下一跳 RB的 MAC地址作为外 层目的 MAC地址， 用所述 RB的 MAC地址作为外层源 MAC地址， 转发所述第二 TRILL OAM报文； 若所述出口路由桥昵称为所述 RB 的昵称， 则对所述第二 TRILL OAM报文进行 TRILL解封装， 得到 第二 OAM报文，所述入口 RB检查所述第二 OAM报文的 VLAN ID; 如果所述第二 OAM报文的 VLAN ID为 DVLAN ID,所述第二 OAM 报文的目的 MAC地址为所述入口 RB的 MAC地址， 所述入口 RB 处理所述第二 OAM报文； 如果所述第二 OAM报文的 VLAN ID不 在所述入口 RB的 VLAN列表中， 丟弃所述第二 OAM报文。
本发明实施例中， 所述 RB通过所述处理器将 DVLAN ID作为 TRILL OAM报文的内层 VLAN ID, 封装生成 TRILL OAM报文， 由 于 TRILL中各个 RB通常都配置并创建了 DVLAN, 因此可以避免报 文因内层 VLAN不是 RB所关心的 VLAN而被丟弃， 并且 DVLAN 是合法 VLAN, 报文也不会因为合法性检查而被丟弃， 从而保证了 TRILL OAM功能的可用性。此外，指定 DVLAN ID作为 TRILL OAM 报文内层 VLAN ID, 也不额外占用 VLAN资源； 并且由于 DVLAN 默认为不学习 MAC地址，也可避免 RB学到不该学习的 MAC地址， 影响 TRILL转发流程。 参见图 7 ,是本发明实施例提供的 TRILL网络示意图，所述 TRILL 中包括入口路由桥 RB和出口 RB;
所述入口 RB封装生成 TRILL OAM 艮文，发送所述 TRILL OAM 报文至所述出口 RB; 其中， 所述 TRILL OAM报文的内层 VLAN ID 和外层 VLAN ID为所述 TRILL的 DVLAN ID; 所述 TRILL OAM报 文的内层目的 MAC地址为出口 RB的 MAC地址， TRILL头中入口 路由桥昵称为所述入口 RB的昵称， 出口路由桥昵称为所述出口 RB 的昵称；
所述出口 RB接收所述 TRILL OAM报文， 对所述 TRILL OAM 报文进行 TRILL解封装， 得到 OAM报文， 并处理所述 OAM报文。
所述 TRILL网络配置了所述 DVLAN; 所述入口 RB和所述出口 RB配置并创建了所述 DVLAN。
具体地， 所述出口 RB接收到所述 TRILL OAM报文后， 获取所 述 TRILL OAM报文的出口路由桥昵称， 由于所述出口路由桥昵称为 所述出口 RB的昵称， 对所述 TRILL OAM 文进行 TRILL解封装， 得到 OAM报文， 由于所述 OAM报文的 VLAN ID为 DVLAN ID, 目的 MAC地址为所述出口 RB的 MAC地址， 所述出口 RB处理所 述 OAM报文； 过程可以参考通常的 OAM处理， 在此不再赘述。
进一步地， 所述入口 RB具体包括：
封装模块， 用于封装生成所述 TRILL OAM报文；
发送模块， 用于发送所述 TRILL OAM才艮文至所述出口 RB。 可选地， 所述入口 RB上配置了 OAM内层 VLAN指定特性， 所 述 OAM内层 VLAN指定特性具体为指定所述 TRILL的 DVLAN用 于 TRILL OAM, 即， 将所述 DVLAN ID作为 TRILL OAM报文的内 层 VLAN ID。 所述入口 RB使能所述 OAM内层 VLAN指定特性， 在封装生成所述 TRILL OAM报文时 , 用所述 TRILL的 DVLAN ID 作为内层 VLAN ID。
可选地， 所述入口 RB还包括特性处理模块， 用于使能或去使能 所述 OAM内层 VLAN指定特性。
进一步地， 所述出口 RB具体包括：
接收模块， 用于接收所述 TRILL OAM报文；
解封装模块， 用于对所述 TRILL OAM报文进行 TRILL解封装， 得到所述 OAM报文；
OAM处理模块， 用于处理所述 OAM ^艮文。
本发明实施例中 ,所述 TRILL网络将 DVLAN用于 TRILL OAM, 由于 TRILL中各个 RB通常都配置和创建了 DVLAN,可以避免因内 层 VLAN不是 RB所关心的 VLAN而使报文被丟弃， 并且 DVLAN 是合法 VLAN, 报文也不会因为合法性检查而被丟弃， 从而保证了 TRILL OAM功能的可用性。此外，指定 DVLAN ID作为 TRILL OAM 报文内层 VLAN ID, 也不额外占用 VLAN资源； 并且由于 DVLAN 默认为不学习 MAC地址，也可避免 RB学到不该学习的 MAC地址， 影响 TRILL转发流程。
以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范 围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技 术范围内， 可轻易想到的变化或替换， 都应涵盖在本发明的保护范围 之内。

Claims

权 利 要 求 书
1、一种多链接透明互联 TRILL中操作维护管理 OAM实现方法， 其特征在于， 包括：
入口路由桥 RB封装生成第一 TRILL OAM报文 ,所述第一 TRILL OAM报文的内层虚拟局域网标识 VLAN ID和外层 VLAN ID为所述 入口 RB所在 TRILL的指定虚拟局域网标识 DVLAN ID, 所述第一 TRILL OAM报文的内层目的介质访问控制 MAC地址为出口 RB的 MAC地址， TRILL头中入口路由桥昵称为所述入口 RB的昵称， 出 口路由桥昵称为所述出口 RB的昵称；
发送所述第一 TRILL OAM报文至所述出口 RB, 以使所述出口 RB处理所述第一 TRILL OAM报文。
2、 根据权利要求 1所述的方法， 其特征在于， 还包括： 所述入口 RB接收第二 TRILL OAM报文，所述第二 TRILL OAM 报文的外层 VLAN ID为所述 DVLAN ID, TRILL头中的出口路由桥 昵称为所述入口 RB的昵称；
所述入口 RB对所述第二 TRILL OAM报文进行 TRILL解封装， 得到第二 OAM报文； 所述第二 OAM报文的目的 MAC地址为所述 入口 RB的 MAC地址 , VLAN标识为所述 DVLAN标识；
所述入口 RB处理所述第二 OAM报文。
3、根据权利要求 1或 2所述的方法， 其特征在于， 所述第一 RB 封装生成第一 TRILL OAM报文包括：
所述入口 RB根据所述出口 RB的昵称查找出下一跳 RB;
将所述下一跳 RB的 MAC地址作为外层目的 MAC地址， 将所 述入口 RB的 MAC地址作为外层源 MAC地址。
4、 根据权利要求 1至 3任一项所述的方法， 其特征在于， 在所 述入口 RB封装生成第一 TRILL OAM报文之前 , 还包括：
所述入口 RB使能 OAM内层 VLAN指定特性， 所述 OAM内层 VLAN 指定特性具体为指定所述 TRILL 的 DVLAN 用于 TRILL OAM。
5、 根据权利要求 1至 4任一项所述的方法， 其特征在于， 所述 入口 RB和所述出口 RB上配置了所述 DVLAN。
6、 多链接透明互联 TRILL中的路由桥 RB , 其特征在于， 包括： 封装模块， 用于封装生成第一 TRILL操作维护管理 OAM报文， 所述第一 TRILL OAM报文的内层虚拟局域网标识 VLAN ID和外层 VLAN ID为所述 RB所在 TRILL的指定虚拟局域网标识 D VLAN ID , 所述第一 TRILL OAM报文的内层目的介质访问控制 MAC地址为出 口 RB的 MAC地址， TRILL头中的出口路由桥昵称为所述出口 RB 的昵称；
发送模块，用于发送所述第一 TRILL OAM报文至所述出口 RB, 以使所述出口 RB处理所述第一 TRILL OAM报文。
7、 根据权利要求 6所述的 RB, 其特征在于， 还包括：
接收模块， 用于接收第二 TRILL OAM报文， 所述第二 TRILL OAM才艮文的外层 VLAN ID为所述 DVLAN ID, TRILL头中的出口 路由桥昵称为所述 RB的昵称；
解封装模块， 用于对所述第二 TRILL OAM报文进行 TRILL解 封装， 得到第二 OAM报文； 所述第二 OAM报文的目的 MAC地址 为所述 RB的 MAC地址 , VLAN ID为所述 DVLAN ID;
OAM处理模块， 用于处理所述第二 OAM报文。
8、根据权利要求 6或 7所述的 RB,其特征在于，所述封装模块， 具体用于根据所述出口 RB的昵称查找出下一跳 RB; 将所述下一跳 RB的 MAC地址作为外层目的 MAC地址， 将所述 RB的 MAC地址 作为外层源 MAC地址。
9、 根据权利要求 6至 8任一项所述的 RB, 其特征在于， 所述 RB还包括：
特性处理模块， 用于使能或去使能 OAM内层 VLAN指定特性， 所述 OAM内层 VLAN指定特性具体为指定所述 TRILL的 DVLAN 用于 TRILL OAM。
10、 根据权利要求 6至 9任一项所述的 RB, 其特征在于， 所述 RB上配置了所述 DVLAN。
11、 一种多链接透明互联 TRILL 网络， 其特征在于， 包括入口 路由桥 RB和出口 RB;
所述入口 RB封装生成 TRILL操作维护管理 OAM 艮文， 发送 所述 TRILL OAM才艮文至所述出口 RB; 其中， 所述 TRILL OAM才艮 文的内层虚拟局域网标识 VLAN ID和外层 VLAN ID为所述 TRILL 的指定虚拟局域网标识 DVLAN ID; 所述 TRILL OAM报文的内层目 的介质访问控制 MAC地址为出口 RB的 MAC地址， TRILL头中入 口路由桥昵称为所述入口 RB 的昵称， 出口路由桥昵称为所述出口 RB的昵称；
所述出口 RB接收所述 TRILL OAM报文， 对所述 TRILL OAM 报文进行 TRILL解封装， 得到 OAM报文， 处理所述 OAM报文。
PCT/CN2013/070531 2013-01-16 2013-01-16 一种trill oam报文实现方法，rb和trill网络 WO2014110729A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201380000092.7A CN104145456A (zh) 2013-01-16 2013-01-16 一种trill oam报文实现方法，rb和trill网络
PCT/CN2013/070531 WO2014110729A1 (zh) 2013-01-16 2013-01-16 一种trill oam报文实现方法，rb和trill网络
EP13871687.3A EP2933962A4 (en) 2013-01-16 2013-01-16 METHOD FOR IMPLEMENTING TRILL OAM PACKAGES, RB AND TRILL NETWORK
US14/797,566 US20150319082A1 (en) 2013-01-16 2015-07-13 Method, RB and TRILL Network for Implementing TRILL OAM Packet

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/070531 WO2014110729A1 (zh) 2013-01-16 2013-01-16 一种trill oam报文实现方法，rb和trill网络

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/797,566 Continuation US20150319082A1 (en) 2013-01-16 2015-07-13 Method, RB and TRILL Network for Implementing TRILL OAM Packet

Publications (1)

Publication Number Publication Date
WO2014110729A1 true WO2014110729A1 (zh) 2014-07-24

Family

ID=51208930

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/070531 WO2014110729A1 (zh) 2013-01-16 2013-01-16 一种trill oam报文实现方法，rb和trill网络

Country Status (4)

Country Link
US (1) US20150319082A1 (zh)
EP (1) EP2933962A4 (zh)
CN (1) CN104145456A (zh)
WO (1) WO2014110729A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102185781A (zh) * 2011-05-12 2011-09-14 中兴通讯股份有限公司 多端口以太网接口装置及其vpn业务接入的方法
US20110299533A1 (en) * 2010-06-08 2011-12-08 Brocade Communications Systems, Inc. Internal virtual network identifier and internal policy identifier
CN102868614A (zh) * 2012-09-13 2013-01-09 杭州华三通信技术有限公司 Trill网络中的报文转发方法和路由网桥

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8619595B2 (en) * 2010-02-05 2013-12-31 Cisco Technology, Inc. Fault isolation in trill networks
US8634308B2 (en) * 2010-06-02 2014-01-21 Brocade Communications Systems, Inc. Path detection in trill networks
US8885488B2 (en) * 2010-06-02 2014-11-11 Brocade Communication Systems, Inc. Reachability detection in trill networks
US8755383B2 (en) * 2011-03-21 2014-06-17 Avaya, Inc. Usage of masked ethernet addresses between transparent interconnect of lots of links (TRILL) routing bridges

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110299533A1 (en) * 2010-06-08 2011-12-08 Brocade Communications Systems, Inc. Internal virtual network identifier and internal policy identifier
CN102185781A (zh) * 2011-05-12 2011-09-14 中兴通讯股份有限公司 多端口以太网接口装置及其vpn业务接入的方法
CN102868614A (zh) * 2012-09-13 2013-01-09 杭州华三通信技术有限公司 Trill网络中的报文转发方法和路由网桥

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
EASTLAKE, D. ET AL.: "TRILL: RBridge Channel Support, draft-ietf-trill-rbridge-channel-08.txt", 13 July 2012 (2012-07-13), XP055204733, Retrieved from the Internet <URL:http://tools.ietf.org/html/draft-ietf-trill-rbridge-channel-08> *
See also references of EP2933962A4 *

Also Published As

Publication number Publication date
CN104145456A (zh) 2014-11-12
US20150319082A1 (en) 2015-11-05
EP2933962A4 (en) 2015-12-09
EP2933962A1 (en) 2015-10-21

Similar Documents

Publication Publication Date Title
US11240065B2 (en) NSH encapsulation for traffic steering
US20200296025A1 (en) Route Processing Method and Apparatus, and Data Transmission Method and Apparatus
EP3720066B1 (en) Packet sending and processing method and apparatus, pe node, and node
US8098656B2 (en) Method and apparatus for implementing L2 VPNs on an IP network
US11902049B2 (en) BIER packet sending method and apparatus
US9843504B2 (en) Extending OpenFlow to support packet encapsulation for transport over software-defined networks
US20230283554A1 (en) BIER Packet Forwarding Method, Device, and System
WO2022062506A1 (zh) 一种数据处理方法、装置、存储介质及电子装置
JP2014090468A (ja) Ｐｂｔネットワークの中間ノードにおけるイーサネットｏａｍ
WO2018014803A1 (zh) 报文转发
US9531564B2 (en) Single hop overlay architecture for line rate performance in campus networks
WO2022021818A1 (zh) 数据报文的处理方法及装置、存储介质、电子装置
WO2022026208A1 (en) Normalized lookup and forwarding for diverse virtual private networks
WO2021093463A1 (zh) 报文转发的方法、第一网络设备以及第一设备组
WO2012122844A1 (zh) 一种多链接互连网络分域互连的方法和系统
CN112737954B (zh) 报文处理方法、装置、系统、设备及存储介质
JP6629681B2 (ja) スイッチ装置および中継システム
WO2021073357A1 (zh) 报文处理方法、装置、系统、设备及存储介质
US20230318974A1 (en) BIER Packet Forwarding Method, Device, and System
US11855888B2 (en) Packet verification method, device, and system
WO2021254454A1 (zh) Bier oam检测的方法、设备以及系统
EP3896924A1 (en) Packet detection method and first network device
WO2014110729A1 (zh) 一种trill oam报文实现方法，rb和trill网络
Nykänen EVPN in Private Cellular Networks

Legal Events

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

Ref document number: 13871687

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2013871687

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013871687

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE