Packet data unit (PDU) structure for supporting distributed relay control protocol (DRCP)

• US 10,257,030 B2
• Filed: 10/31/2016
• Issued: 04/09/2019
• Est. Priority Date: 04/23/2013
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Saltsidis, Panagiotis
• Primary Examiner(s): Sinkantarakorn, Pao
• Assistant Examiner(s): Jahangir, Kabir U
• Application Number:
  US15/339,162
• Publication Number:
  US 20170111219A1
• Time in Patent Office: 890 Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 2012/5652 Cell construction, e.g. including header, packetisation, depacketisation, assembly, reassembly
• CPC Class Codes: H04L 2212/00 Encapsulation of packets
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element
• CPC Class Codes: H04L 41/342 between virtual entities, e.g. orchestrators, SDN or NFV entities
• CPC Class Codes: H04L 41/344 Out-of-band transfers
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/46 : Cluster building
• CPC Class Codes: H04L 49/253 : using establishment or release of connections between ports
• CPC Class Codes: H04L 49/354 : for supporting virtual local area networks [VLAN]
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/03 : Protocol definition or specification protocol conformance testing H04L1/244
• CPC Class Codes: H04L 69/324 : in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: Y02D 30/50 : in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

A method supporting distributed resilient network interconnect (DRNI) in a link aggregation group at a network device is disclosed. The method starts with encapsulating a distributed relay control protocol data unit (DRCPDU) in a frame, wherein the DRCPDU includes a protocol data unit (PDU) structure. The PDU structure includes a type field indicating that the DRCPDU is for DRCP, a version field indicating a version number of the DRCP, and a set of type/length/values (TLVs) including: a terminator TLV indicating an end of the PDU structure, a portal information TLV indicating characteristics of the first portal, a portal configuration information TLV indicating configuration information of the first portal, a DRCP state TLV indicating variables associated with an intra-portal link (IPP), a home ports information TLV and a neighbor ports information TLV. The method continues with transmitting the frame encapsulating the DRCPDU from the network device to a neighbor network device.

Claims

1. A method supporting a distributed resilient network interconnect (DRNI) at a network device, wherein the network device and a neighbor network device are included in a portal of a link aggregation group (LAG), wherein the network device is coupled to the neighbor network device via an intra-portal port (IPP), the method comprising:

encapsulating a distributed relay control protocol data unit (DRCPDU) in a frame,

wherein the DRCPDU includes a protocol data unit (PDU) structure, including;

a type field indicating that the DRCPDU is for DRCP,

a version field indicating a version number of the DRCP, and

a set of type/length/values (TLVs) including;

a terminator TLV indicating an end of the PDU structure,

a portal information TLV indicating characteristics of the portal,

a portal configuration information TLV indicating configuration information of the portal,

a DRCP state TLV indicating variables associated with the IPP,

a home ports information TLV indicating a current status of the network device, and

a neighbor ports information TLV indicating a current status of the neighbor network device; and

transmitting the frame encapsulating the DRCPDU from the network device to the neighbor network device via the IPP.

2. The method of claim 1, wherein the terminator TLV includes a TLV type field indicating a value of zero.

3. The method of claim 1, wherein the portal information TLV includes:

a TLV type field indicating a value of one;

an aggregator priority field indicating a priority assigned to an aggregator of the network device;

an aggregator identifier field indicating an identifier of the aggregator;

a portal priority field indicating a priority assigned to the portal; and

a portal address field indicating a media access control (MAC) address component associated with the network device.

4. The method of claim 1, wherein the portal configuration information TLV includes:

a TLV type field indicating a value of two;

a topology state field indicating a topology state of the portal;

an operational aggregator key field indicating an operational aggregator key of the network device;

a portal algorithm field indicating a portal algorithm used;

a gateway algorithm field indicating a gateway algorithm used;

a port digest field indicating a port digest used for port conversation identifier (ID) to aggregation port assignment; and

a gateway digest field indicating a gateway digest used for gateway conversation identifier to gateway assignment.

5. The method of claim 4, wherein the topology state of the portal indicates a first portal system number associated with the portal, a second portal system number associated with the neighbor network device that is attached to the IPP, and an indication of whether an other ports information TLV is associated with the neighbor network device.

6. The method of claim 5, wherein the first portal system number is represented by first two bits of a byte, the second portal system number is represented by the third and fourth bits of the byte, and the indication is represented by the eighth bit of the byte.

7. The method of claim 1, wherein the DRCP state TLV includes a DRCP state field indicating variables associated with the IPP.

8. The method of claim 1, wherein the home ports information TLV includes:

a TLV type field indicating a value of four;

an administrative aggregator key field indicating an administrative aggregator key value of an aggregator attached;

an operational partner aggregator key field indicating an operational partner aggregator key associated with the network device'"'"'s LAG identifier (ID); and

an active aggregation port field indicating a list of active aggregation ports in the network device.

9. The method of claim 1, wherein the neighbor ports information TLV includes:

a TLV type field indicating a value of five;

an administrative aggregator key field indicating an administrative aggregator key value of an aggregator attached to the neighbor network device;

an operational partner aggregator key field indicating an operational partner aggregator key associated with the neighbor network device'"'"'s LAG identifier (ID); and

an active aggregation port field indicating a list of active aggregation ports in the neighbor network device associated with the IPP.

10. The method of claim 1, wherein the portal includes a third network device of the portal, wherein the set of TLVs further includes an other ports information TLV that includes:

a TLV type field indicating a value of six;

an administrative aggregator key field indicating an administrative aggregator key value of an aggregator attached to the third network device;

an operational partner aggregator key field indicating an operational partner aggregator key associated with the third network device'"'"'s LAG Identifier (ID); and

an active aggregation port field indicating a list of active aggregation ports in the third network device associated with the IPP.

11. The method of claim 1, wherein the set of TLVs further includes a network/intra portal link (IPL) sharing method TLV and a network/IPL sharing encapsulation TLV, wherein the network/IPL sharing method TLV indicates a network and IPL sharing method associated with the network device, and wherein the network/IPL sharing encapsulation TLV indicates information relating to encapsulation of the sharing method.

12. A network device supporting a distributed resilient network interconnect (DRNI), wherein the network device and a neighbor network device are included in a portal of a link aggregation group (LAG), wherein the network device is coupled to the neighbor network device via an intra-portal port (IPP), the network device comprising:

ports coupled to one or more physical or aggregation links of the link aggregation group; and

a processor coupled to the ports, executing a DRNI function, the DRNI function operative to cause encapsulation of a distributed relay control protocol data unit (DRCPDU) in a frame, and further operative to cause transmission of the frame encapsulating the DRCPDU from the network device to the neighbor network device via the IPP,

wherein the DRCPDU includes a protocol data unit (PDU) structure, including;

a type field indicating that the DRCPDU is for DRCP,

a version field indicating a version number of the DRCP, and

a set of type/length/values (TLVs) including;

a terminator TLV indicating an end of the PDU structure,

a portal information TLV indicating characteristics of the portal,

a portal configuration information TLV indicating configuration information of the portal,

a DRCP state TLV indicating variables associated with the IPP,

a home ports information TLV indicating a current status of the network device, and

a neighbor ports information TLV indicating a current status of the neighbor network device.

13. The network device of claim 12, wherein the terminator TLV includes a TLV type field indicating a value of zero.

14. The network device of claim 12, wherein the portal information TLV includes:

a TLV type field indicating a value of one;

an aggregator priority field indicating a priority assigned to an aggregator of the network device;

an aggregator identifier field indicating an identifier of the aggregator;

a portal priority field indicating a priority assigned to the portal; and

a portal address field indicating a media access control (MAC) address component associated with the network device.

15. The network device of claim 12, wherein the portal configuration information TLV includes:

a TLV type field indicating a value of two;

a topology state field indicating a topology state of the portal;

an operational aggregator key field indicating an operational aggregator key of the network device;

a portal algorithm field indicating a portal algorithm used;

a gateway algorithm field indicating a gateway algorithm used;

a port digest field indicating a port digest used for port conversation identifier (ID) to aggregation port assignment; and

a gateway digest field indicating a gateway digest used for gateway conversation identifier to gateway assignment.

16. The network device of claim 15, wherein the topology state of the portal indicates a first portal system number associated with the portal, a second portal system number associated with the neighbor network device that is attached to the IPP, and an indication of whether an other ports information TLV is associated with the neighbor network device.

17. The network device of claim 16, wherein the first portal system number is represented by first two bits of a byte, the second portal system number is represented by the third and fourth bits of the byte, and the indication is represented by the eighth bit of the byte.

18. The network device of claim 12, wherein the home ports information TLV includes:

a TLV type field indicating a value of four;

an administrative aggregator key field indicating an administrative aggregator key value of an aggregator attached;

an operational partner aggregator key field indicating an operational partner aggregator key associated with the network device'"'"'s LAG identifier (ID); and

an active aggregation port field indicating a list of active aggregation ports in the network device.

19. The network device of claim 12, wherein the neighbor ports information TLV includes:

a TLV type field indicating a value of five;

an administrative aggregator key field indicating an administrative aggregator key value of an aggregator attached to the neighbor network device;

an operational partner aggregator key field indicating an operational partner aggregator key associated with the neighbor network device'"'"'s LAG identifier (ID); and

an active aggregation port field indicating a list of active aggregation ports in the neighbor network device associated with the IPP.

20. The network device of claim 12, wherein the portal includes a third network device of the portal, wherein the set of TLVs further includes an other ports information TLV that includes:

a TLV type field indicating a value of six;

an administrative aggregator key field indicating an administrative aggregator key value of an aggregator attached to the third network device;

an operational partner aggregator key field indicating an operational partner aggregator key associated with the third network device'"'"'s LAG Identifier (ID); and

an active aggregation port field indicating a list of active aggregation ports in the third network device associated with the IPP.