What is the functionality of the "crumbsperclasscount" variable?


<< Back to Knowledge Search

Solution

Overview

With this system variable, we are controlling granularity of the “traffic history” command, which records classification history per host, or per class.

It can be configured using the following command; -

sys set crumbsperclasscount integer

The "Traffic history" command is designed for troubleshooting and identifying where a miss-classified flow may have been handled in the class tree by displaying what passed through a given class or specifically which classes a given host may have matched depending on the parameter supplied, with a brief historic record of the source/destination hosts/ports, and the application or protocol name (if available) the shaper was able to identify, grouped by class.

The “crumbs” integer specified determines the level of granularity available in this command in terms of tree depth (by default, this is ten classes deep), and by entering 0 we can disable the functionality all-together which is very useful in complicated, or high bandwidth scenarios.
 

Examples of the traffic history command and output: 

traffic history recent /inbound/default

-----( /Inbound/Default )-----

11-Apr-2012 08:39:33      SNMP-Mon
   55.55.55.11         161
   55.55.55.69        1052
11-Apr-2012 08:39:24      DHCP-S
   255.255.255.255     67
   55.55.55.63          68
11-Apr-2012 08:39:13      UDP
   255.255.255.255  43440
   55.55.55.60       64707
11-Apr-2012 08:38:51      UDP
   255.255.255.255  43440
   55.55.55.26       64772
11-Apr-2012 08:38:47      UDP
   255.255.255.255  43440
   55.55.55.57       56090
11-Apr-2012 08:38:18      UDP
   255.255.255.255  43440
   55.55.55.28       52235
11-Apr-2012 08:38:14      UDP
   255.255.255.255  43440
   55.55.55.48       62401
11-Apr-2012 08:38:06      DHCP-S
   255.255.255.255     67
   55.55.55.68          68
11-Apr-2012 08:37:42      UDP
   255.255.255.255  43440
   55.55.55.29       62243
11-Apr-2012 08:37:11      UDP
   255.255.255.255  43440
   55.55.55.34       54884

traffic history find 55.55.55.47

-----( /Outbound/MSSQL )-----

05-Apr-2012 15:00:13      MSSQL-Server
   55.55.55.47       58736
   10.2.2.143        1433

-----( /Inbound/MSSQL )-----

05-Apr-2012 15:00:13      MSSQL-Server
   55.55.55.47       58736
   10.2.2.143        1433

-----( /Outbound/BITS )-----

11-Apr-2012 07:08:51      BITS
   55.55.55.47       55095
   10.2.2.135          80
10-Apr-2012 07:18:44      BITS
   55.55.55.47       61152
   74.125.4.50         80
10-Apr-2012 07:18:41      BITS
   55.55.55.47       61150
   74.125.4.19         80

-----( /Inbound/BITS )-----

11-Apr-2012 07:08:51      BITS
   55.55.55.47       55095
   10.2.2.135          80
10-Apr-2012 07:18:44      BITS
   55.55.55.47       61152
   74.125.4.50         80
10-Apr-2012 07:18:41      BITS
   55.55.55.47       61150
   74.125.4.19         80

-----( /Outbound/SSH )-----

11-Apr-2012 08:07:08      SSH
   55.55.55.47       55872
   55.55.55.4           22

-----( /Inbound/SSH )-----

11-Apr-2012 08:07:08      SSH
   55.55.55.47       55872
   55.55.55.4           22

 

Cause
Resolution
Workaround
Additional Information
Bug Number
InQuira Doc IdFAQ2071
Attachment

Article Feedback

Hide Properties
First Published      10/01/2014
Last Modified      10/01/2014
Last Published      10/01/2014
Article Audience
Product      PacketShaper
Software      PacketWise 8, PacketWise 9
Topic      Performance
Article Number      000015373
Summary     
Was this helpful?
Comments:
 
Previous MonthNext Month
SunMonTueWedThuFriSat