Method and system for supporting distributed relay control protocol (DRCP) operations upon misconfiguration

Patent metadata

Field	Value
Publication number	US-9813290-B2
Application number	US-201514838353-A
Country	US
Kind code	B2
Filing date	Aug 27, 2015
Priority date	Aug 29, 2014
Publication date	Nov 7, 2017
Grant date	Nov 7, 2017

Abstract

A method supporting a distributed resilient network interconnect (DRNI) in a link aggregation group at a network device is disclosed. The method starts with receiving a distributed relay control protocol data unit (DRCPDU), where the DRCPDU includes neighbor network device's state information and configuration information, wherein the configuration information includes its operational aggregation key, gateway digest, port digest. The method continue with determine whether or not the received configuration information is different from the one of the network device and how, and causing the next DRCPDU to be transmitted to the neighbor network device to include or not include certain information accordingly.

First claim

What is claimed is:

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, wherein the first portal is coupled via links of the link aggregation group with a second portal including of one or more remote network devices, 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:
receiving a distributed relay control protocol data unit (DRCPDU), wherein the DRCPDU includes neighbor network device's state information and configuration information, wherein the configuration information includes its operational aggregation key, gateway digest, and port digest;
determining whether at least some of the received configuration information is different from the configuration information of the network device;
determining whether a portion of the received operational aggregation key is identical to a corresponding portion of an operational aggregation key of the network device upon determining that the at least some of the received configuration information is different from the configuration information of the network device;
determining whether settings for being three system portal and gateway algorithms are the same as received values for being three system portal and gateway algorithms upon determining that the portion of the received operational aggregation key is identical to a corresponding portion of an operational aggregation key of the network device;
determining whether the received gateway digest is identical to a gateway digest of the network device upon determining that settings for being three system portal and gateway algorithms are the same; and
causing not to include a gateway conversation type/length/value (TLV) in a next DRCPDU to be transmitted by the network device to the neighbor network device upon determining that the received gateway digest is identical to the gateway digest of the network device.

2. The method of claim 1 , wherein the determining whether the portion of the received operational aggregation key is identical to the corresponding portion of the operational aggregation key of the network device includes comparing the 14 least significant bits in the received operational aggregation key and the operational aggregation key of the network device.

3. The method of claim 1 , further comprising:
upon determining that the received gateway digest is different from the gateway digest of the network device, indicating to a transmit operation of the network device to include a gateway conversation TLV in the next DRCPDU to be transmitted by the network device to the neighbor network device.

4. The method of claim 3 , further comprising:
determining whether a gateway conversation TLV is included in the received DRCPDU; and
upon determining that the gateway conversation TLV is included in the received DRCPDU, setting a variable for a neighbor network device's operational gateway conversation vector to a gateway conversation vector that is carried in the gateway conversation TLV.

5. The method of claim 1 , further comprising:
determining whether a received port algorithm is identical to a configured port algorithm of the network device;
determining whether the received port digest is identical to a port digest of the network device upon determining that the received port algorithm is identical to the configured port algorithm of the network device;
causing not to include a port conversation TLV in the next DRCPDU to be transmitted by the network device to the neighbor network device upon determining that the received port digest is identical to a port digest of the network device; and
recording the neighbor network device's state information contained in the received DRCPDU as state operational variables of the neighbor network device.

6. The method of claim 5 , further comprising:
upon determining that the received port digest is different from the port digest of the network device, indicating to a transmit operation of the network device to include a port conversation TLV in the next DRCPDU to be transmitted by the network device to the neighbor network device.

7. The method of claim 6 , further comprising:
determining whether a port conversation TLV is included in the received DRCPDU; and
upon determining that the port conversation TLV is included in the received DRCPDU, setting a variable for a neighbor network device's operational port conversation vector to a gateway conversation vector that is carried in the port conversation TLV.

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, wherein the first portal is coupled via links of the link aggregation group with a second portal including of one or more remote network devices, 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 the physical or aggregation link 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: receive a distributed relay control protocol data unit (DRCPDU), wherein the DRCPDU includes neighbor network device's state information and configuration information, wherein the configuration information includes its operational aggregation key, gateway digest, and port digest, determine whether at least some of the received configuration information is different from the configuration information of the network device, determine whether a portion of the received operational aggregation key is identical to a corresponding portion of an operational aggregation key of the network device upon a determination that the at least some of the received configuration information is different from the configuration information of the network device, determine whether settings for being three system portal and gateway algorithms are the same as received values for being three system portal and gateway algorithms upon determining that the portion of the received operational aggregation key is identical to a corresponding portion of an operational aggregation key of the network device, determine whether the received gateway digest is identical to a gateway digest of the network device upon determining that settings for being three system portal and gateway algorithms are the same, and cause not to include a gateway conversation type/length/value (TLV) in a next DRCPDU to be transmitted by the network device to the neighbor network device upon the determination that the received gateway digest is identical to the gateway digest of the network device.

9. The network device of claim 8 , wherein the DRNI function is further operative to: upon the determination that the received gateway digest is different from the gateway digest of the network device, indicate to a transmit operation of the network device to include a gateway conversation TLV in the next DRCPDU to be transmitted by the network device to the neighbor network device.

10. The network device of claim 9 , wherein the DRNI function is further operative to: determine whether a gateway conversation TLV is included in the received DRCPDU, and upon the determination that the gateway conversation TLV is included in the received DRCPDU, set a variable for a neighbo

Assignees

• Ericsson Telefon Ab L M
• ERICSSON TELEFON AB L M (publ)

Inventors

• Saltsidis Panagiotis

Classifications

• H04L41/082

  the condition being updates or upgrades of network functionality · CPC title

• H04L45/28

  using route fault recovery · CPC title

• H04L41/0853 Primary

  by actively collecting configuration information or by backing up configuration information · CPC title

• H04L65/102

  Gateways (arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66) · CPC title

• H04L45/021

  Ensuring consistency of routing table updates, e.g. by using epoch numbers · CPC title