Page History

...

For every new device detected where the current controller instance is a MASTER (Either first time device connected or MASTER-SHIP changes), the SR application would initiate default group handling procedures for that device.

• @Activation
  
  • Get the Segment IDs of all devices in the network from Network Config service
  • Get "isEdgeRouter" attribute for this device from Network Config service
  • Create Neighbor <-> Port mapping database based on current topology
  • Create Port <-> Neighbor mapping database based on current topology
  • If AUDIT is in progress at Group subsystem for this device
    • Start a timer and perform the Sanity check
  • Sanity Check
    • Compute power set of all Neighbors
    • Pair them with all applicable Segment IDs if the current device is a edge router
    • Determine the SRDefaultGroupKeys for each pair and create groups using Group service API if there is no group existing with this Key
• @LINK_UP involving one of device ports
  • Find the Neighbor Device ID
  • If (Neighbor is already present in the database for this device)
    • That means this new link is part of group of links to that Neighbor (e.g. LAG)
    • Determine all SRDefaultGroupKeys that are impacted due to this new link from the information of existing device ports and Segment IDs
    • Invoke "addBucketsToGroup()" API of the GroupService with a new SRDefaultGroupKey for all the impacted Groups
    • Update Neighbor <-> Port mapping database
    • Update Port <-> Neighbor mapping databaseUpdated Neighbor database with this new port
  • Else
    
    • That means this new link discovers a new neighbor

Segment Routing application interacts with the Group subsystem using the below SR specific GroupKey. So SR application associate a SRDefaultGroupKey or SRPolicyGroupKey for every group it creates. The SRGroupKey consists of collection of <PortNumber + Label Stack to be pushed on that port> where leftmost label representing the outermost label and rightmost label representing innermost label to be pushed.

Default Group Handler & Recovery

During Start-up:

Create Segment Id database of all the nodes in the network

Get all devices from Topology service

Add to above list when DEVICE_ADDED event received

For each switch that this instance is master,

If the Group subsystem peforming Group AUDIT, then wait until AUDIT completes

Create Neighbor list

Get all outgoing links from Link service

Update above list when LINK_ADDED event received

Get all Groups from the Store

• • • Update Neighbor <-> Port mapping database
    • Update Port <-> Neighbor mapping database
    • Recompute neighbor power sets with updated neighbor database and determine the delta entries and pair them up with applicable segment IDs
    • Determine the SRDefaultGroupKeys for each pair and create groups using Group service API if there is no group existing with this Key.
• @PORT_UP
  
  • No Action
• @PORT_DOWN
  
  • 
    

 Perform Audit using above Neighbor list

Policy Group Handler & Recovery

...