Method and system for synchronizing with neighbor in a distributed resilient network interconnect (DRNI) link aggregation group

• US 9,509,556 B2
• Filed: 04/21/2014
• Issued: 11/29/2016
• 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): Gidado, Rasheed
• Application Number:
  US14/257,637
• Publication Number:
  US 20140313939A1
• Time in Patent Office: 953 Days
• US Class Current: 1/1
• 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 of supporting a distributed resilient network interconnect (DRNI) at a network device is disclosed. The method starts with initializing the network device for operating distributed resilient control protocol (DRCP) on an intra-portal port (IPP) coupled to a neighbor network device using an intra-port link (IPL). The method continues with the network device checking that DRCP is enabled at the IPP and then enters an expired state. The network device then receives a DRCPDU and determines that the received DRCPDU is associated with the first portal it is assigned to. It determines that the received DRCPDU is compatible with the network device, and records neighbor network device'"'"'s state information included in the received DRCPDU as state operational variables of the neighbor network device at the network device, wherein the neighbor network device'"'"'s state information includes DRCP variables for the IPP.

Claims

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

initializing the network device for operating distributed resilient control protocol (DRCP) on the IPP coupled to the neighbor network device using the IPL, wherein the initialization includes setting default parameter values for the neighbor network device on the IPP to be operational parameters of the neighbor network device provided by an administrator of the first portal;

checking that DRCP is enabled at the IPP, wherein the checking includes determining a variable indicating that the IPP is operating DRCP;

entering an expired state at the network device, wherein the network device performs;

setting a distributed relay control protocol (DRCP) state parameter of the network device to expired,

setting an IPP activity of the neighbor network device to be inactive, and

setting a timer for receiving a distributed relay control protocol data unit (DRCPDU);

upon receiving a DRCPDU before expiration of the timer, wherein the DRCPDU includes neighbor network device'"'"'s state information,

determining that the received DRCPDU is associated with the first portal;

determining, if it was determined that the received DRCPDU is associated with the first portal, that the received DRCPDU is compatible with the network device, wherein the determination comprises determining that administratively configured values associated with the first portal are consistent with that of the received DRCPDU; and

recording, if it was determined that the received DRCPDU is compatible with the network device, neighbor network device'"'"'s state information included in the received DRCPDU as state operational variables of the neighbor network device at the network device, wherein the neighbor network device'"'"'s state information includes DRCP variables for the IPP.

2. The method of claim 1, further comprising:

upon the timer expiring without receiving the DRCPDU, the network device entering a defaulted state, wherein in the defaulted state, the network device sets default parameter values for the neighbor network device on the IPP to be current operational parameters of the neighbor network device provided by the administrator of the first portal, and the network device reports a status of the defaulted state to a management system of the first portal.

3. The method of claim 1, wherein determining the received DRCPDU being associated with the first portal includes recording portal parameter values carried in the received DRCPDU as corresponding operational parameter values for the neighbor network device on the IPP.

4. The method of claim 1, further comprising:

upon determining that a received DRCPDU is not associated with the first the reporting a status of no association to a management system of the first portal.

5. The method of claim 1, wherein determining that the received DRCPDU is compatible with the network device includes recording neighbor network device'"'"'s configured parameter values carried in the received DRCPDU as corresponding operational parameter values for the neighbor network device on the IPP.

6. The method of claim 1, further comprising:

upon determining that the received DRCPDU is incompatible with the network device, reporting a status of incompatibility to a management system of the first portal.

7. The method of claim 1, further comprising:

setting one or more triggers to notify the neighbor network device upon determining that the recorded neighbor network device'"'"'s state operational variables differ from the network device'"'"'s state operational variables.

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

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

a network processor coupled to the ports, the network processor executing a DRNI function, the DRNI function operative to initialize the network device for operating distributed resilient control protocol (DRCP) on the IPP coupled to the neighbor network device using the IPL, wherein the initialization includes setting default parameter values for the neighbor network device on the IPP to be operational parameters of the neighbor network device provided by an administrator of the first portal, further operative to check that DRCP is enabled at the IPP, wherein the check is to include determining a variable indicating that the IPP is operating DRCP, further operative to enter an expired state at the network device, wherein the DRNI function is operative to set a distributed relay control protocol (DRCP) state parameter of the network device to expired, set an IPP activity of the neighbor network device to be inactive, and set a timer for receiving a distributed relay control protocol data unit (DRCPDU), further operative to, upon receiving a DRCPDU before expiration of the timer, wherein the DRCPDU includes neighbor network device'"'"'s state information, determine that the received DRCPDU is associated with the first portal, determine, if it was determined that the received DRCPDU is associated with the first portal, that the received DRCPDU is compatible with the network device, wherein the determination is further to determine that administratively configured values associated with the first portal are consistent with that of the received DRCPDU, and record, if it was determined that the received DRCPDU is compatible with the network device, neighbor network device'"'"'s state information included in the received DRCPDU as state operational variables of the neighbor network device at the network device, wherein the neighbor network device'"'"'s state information is to include DRCP variables for the IPP.

9. The network device of claim 8, wherein entering the expired state at network device is further to:

set a timer to expire if no DRCPDU is received, wherein the network device is to enter a defaulted state, wherein in the defaulted state, the network device is to set default parameter values for the neighbor network device on the IPP to be current operational parameters of the neighbor network device provided by the administrator of the first portal, and the network device is to report a status of the defaulted state to a management system of the first portal.

10. The network device of claim 8, wherein determining the received DRCPDU being associated with the first portal includes to record portal parameter values carried in the received DRCPDU as corresponding operational parameter values for the neighbor network device on the IPP.

11. The network device of claim 8, the DRNI function further operative to:

upon determining that a received is not associated with the first portal, report a status of no association to a management system of the first portal.

12. The network device of claim 8, wherein determining that the received DRCPDU is compatible with the network device includes to record neighbor network device'"'"'s configured parameter values carried in the received DRCPDU as corresponding operational parameter values for the neighbor network device on the IPP.

13. The network device of claim 8, the DRNI function further operative to:

upon determining that the received DRCPDU is incompatible with the network device, report a status of incompatibility to a management system of the first portal.

14. The network device of claim 8, the DRNI function further operative to:

set one or more triggers to notify the neighbor network device upon determining the recorded neighbor network device'"'"'s state operational variables differ from the network device'"'"'s state operational variables.

15. A non-transitory machine-readable storage medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations at a network device to support a distributed resilient network interconnect (DRNI) in a link aggregation group, wherein the network device and a neighbor network device are included in a first portal of the link aggregation group, and wherein the network device is communicatively coupled to the neighbor network device via an intra-portal port (IPP) using an intra-portal link (IPL), the operations comprising:

initializing the network device for operating distributed resilient control protocol (DRCP) on the IPP coupled to the neighbor network device using the IPL, wherein the initialization includes setting default parameter values for the neighbor network device on the IPP to be operational parameters of the neighbor network device provided by an administrator of the first portal;

checking that DRCP is enabled at the IPP, wherein the checking includes determining a variable indicating that the IPP is operating DRCP;

entering an expired state at the network device, wherein the network device performs;

setting a distributed relay control protocol (DRCP) state parameter of the network device to expired,

setting an IPP activity of the neighbor network device to be inactive, and

setting a timer for receiving a distributed relay control protocol data unit (DRCPDU);

upon receiving a DRCPDU before expiration of the timer, wherein the DRCPDU includes neighbor network device'"'"'s state information,

determining that the received DRCPDU is associated with the first portal;

determining, if it was determined that the received DRCPDU is associated with the first portal, that the received DRCPDU is compatible with the network device, wherein the determination comprises determining that administratively configured values associated with the first portal are consistent with that of the received DRCPDU; and

recording, if it as determined that the received DRCPDU is compatible with the network device, neighbor network device'"'"'s state information included in the received DRCPDU as state operational variables of the neighbor network device at the network device, wherein the neighbor network device'"'"'s state information includes DRCP variables for the IPP.

16. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise:

upon the timer expiring without receiving the DRCPDU, the network device entering a defaulted state, wherein in the defaulted state, the network device sets default parameter values for the neighbor network device on the IPP to be current operational parameters of the neighbor network device provided by the administrator of the first portal, and the network device reports status of the defaulted state to a management system of the first portal.

17. The non-transitory machine-readable storage medium of claim 15, wherein determining the received DRCPDU being associated with the first portal includes recording portal parameter values carried in the received DRCPDU as corresponding operational parameter values for the neighbor network device on the IPP.

18. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise:

upon determining that a received DRCPDU is not associated with the first portal, reporting a status of no association to a management system of the first portal.

19. The non-transitory machine-readable storage medium of claim 15, wherein determining that the received DRCPDU is compatible with the network device includes recording neighbor network device'"'"'s configured parameter values carried in the received DRCPDU as corresponding operational parameter values for the neighbor network device on the IPP.

20. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise:

upon determining that the received DRCPDU is incompatible with the network device, reporting a status of incompatibility to a management system of the first portal.

21. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise:

setting one or more triggers to notify the neighbor network device upon determining the recorded neighbor network device'"'"'s state operational variables differ from the network device'"'"'s state operational variables.