Browse Prior Art Database

Smart Link Aggregation(SLAG)

IP.com Disclosure Number: IPCOM000235030D
Publication Date: 2014-Feb-25

Publishing Venue

The IP.com Prior Art Database

Abstract

In this disclosure, a solution called Smart Link Aggregation (SLAG) is disclosed to automatically link aggregating between switches by Predefined Port-Channel (PPC).After switch initialized with configuration, the switch ports which have the same properties to perform link aggregation will be assigned an ID number, it is named PPC ID.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 45% of the total text.

Page 01 of 12

Smart Link Aggregation

Smart Link Aggregation( ((SLAG SLAG

SLAG) )

Figure-1

Figure-1 is a normal case in networking. If users forget to configure port1~port 3 to a LAG, then it will generate loop (If STP is disable) or cause some ports block traffic (If STP is enabled), then

cannot achieve both load-lance and redundant back purpose.

1


Page 02 of 12

Figure-

Figure-2 if user configure port 1 and port 2 to a LAG, then later user add a new port 3, if user forget configure port 3 to this LAG, then it will also generate loop (If STP is disabled) or

cause some ports block traffic (If STP is enabled), then cannot achieve both load-lance and redundant back purpose.

2

2


Page 03 of 12

Figure-3

Figure-3 if the network topology is changed later, without change configuration the networking will have problem. Device A cannot communicate with Device C.

Currently there have no solution for such problems.

In this disclosure, a solution called Smart Link Aggregation (SLAG) is disclosed to automatically link aggregating between switches by Predefined Port-Channel (PPC).

After switch initialized with configuration, the switch ports which have the same properties to perform link aggregation will be assigned an ID number, It is named PPC ID.

3


Page 04 of 12

A new defined LLDP TLV - PPC ID TLV will be used to carry this port's PPC ID .

LLDP packets are exchanged between switches with mandatory TLVs (CHASSIS ID TLV, PORT ID TLV and TTL TLV) and PPC ID TLV.

Local switch go through local ports in same PPC ID, if some peer ports has same CHASSIS ID and PPC ID, then it means these links between local and peer ports could form into a LAG.

SLAG feature will trigger forming LAGs (dynamic or static) on these links.

SLAG provides benefits to customer that they do not need to configure the LAG themselves ; the LAG will be automatically formed.

1. Initially, a default PPC (Predefined Port-Channel) table will be formed automatically according to the running configuration after enable this feature.

On local switch, switch ports which have same port properties will be assigned a PPC ID, For example:

Figure-4

4


Page 05 of 12

On switch A, port 1-3 have the same port properties, Port 4-6 have the same port properties. On switch B, All the ports 1-6 have the same port properties.

Then an initial default PPC table will be formed on switch A like Table -1:

Local PPC

ID

0

1

Table-1

PPC ID: Predefined Port-Channel ID, port with same properties will be put into a same port group and assign a PPC ID . Local port ID: Local switch port number.

Remote Switch ID: CHASSIS ID get from peer switch LLDP packet, it is the ID to unique indicate the peer switch. Remote Port ID: PORT ID get from peer switch LLDP packet, it is the port number on peer switch.

Remote PPC ID: PPC ID get from peer switch LLDP packet, it is the PPC ID on peer switch port.

Port-Channel ID: After automatically link aggregating, a formal Port-Channel ID will be assigned to a formed LAG.

On switch A, Two port group...