Background on Flow Setup Throttling

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 5626 

Products
NetSight
Atlas Console 

Protocols/Features
Flow Setup Throttling
FST 

Symptoms
"Flow Setup Throttling Port Info"
"Flow Processing Layer" 

Solution
Flows are built with the minimum amount of information required by the configuration. Since switches generally operate with an L2 awareness, then for best flow granularity for FST they must be made to operate on both L3 (eg: add a priority classification for IP 1.2.3.4) and L4 (eg: add a priority classification for TCP port 65535). Using either Classifications or Policies operating on these layers would have the same effect. 

These are the possible "Flow Processing Layer" (right-most) column values (from OID 'etsysFlowLimitingIntfFlowProcessingLayer=1.3.6.1.4.1.5624.1.2.43.1.3.1.1.14') in the NetSight Atlas "Flow Setup Throttling Port Info" Flexview:
  • "None" = FST is not set up for the port.
  • "L2" = FST has been set up, but there is no Classification/Policy rule applied (to the port?).
  • "L3" = FST is operating using a L3 awareness.
  • "L4" = FST is operating using a L4 awareness.
It is possible to have "L4" listed, yet L3 is not part of the flow makeup because there is no L3 rule on the switch! 

If "L2" is listed while flows are being throttled; this is because the flow granularity is at L2, meaning that flows that would be separate at L3 or L4 are considered to be part of one flow. This would make for fewer overall flows that could be separately considered, for the same traffic content and connectivity. 
Note: The SmartSwitch 2nd/3rd Gens require that the Classification/Policy rules be assigned to the ports for which FST is expected to operate, before higher-layer granularity will apply to those ports. 

See also: 5289.
Photo of FAQ User

FAQ User, Official Rep

  • 13,610 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.