Tested release: 22.1.x


This KB demonstrates how to capture logs on Analytics per forwarding class (FC) sub queues.


By default, enabling cos fc logs on interface will not capture logs for FC sub queues, but will only capture logs for the main Traffic Class (TC) i.e. fc_nc, fc_ef, fc_af, fc_be


In order to capture logs for FC sub queues per Traffic Class (TC), enable cos fc logs on the network

Total:16 forwarding class queues fc0 - fc15




Tested lab configuration for reference below

* Prerequisite: Considering class of service is configured for the site


Class of Service: 


QoS Profile

* You configure a QoS profile to create ingress policers, which limit the rate of ingress traffic and associating ingress traffic with a forwarding class/ loss priority.



set orgs org-services <ORG> class-of-service qos-profiles Custom-Profile forwarding-class fc13
set orgs org-services <ORG> class-of-service qos-profiles Custom-Profile loss-priority low
set orgs org-services <ORG> class-of-service qos-profiles Custom-Profile dscp-rw-enable yes
set orgs org-services <ORG> class-of-service qos-profiles Custom-Profile dot1p-rw-enable no



QoS Policy/App QoS Policy

* QoS policies define how to handle traffic when a network becomes congested. 



set orgs org-services <ORG> class-of-service app-qos-policies Default-Policy rules Business-Traffic rule-disable false
set orgs org-services <ORG> class-of-service app-qos-policies Default-Policy rules Business-Traffic match source user user-type any
set orgs org-services <ORG> class-of-service app-qos-policies Default-Policy rules Business-Traffic match application predefined-filter-list [ Business-Traffic ]
set orgs org-services <ORG> class-of-service app-qos-policies Default-Policy rules Business-Traffic set action allow
set orgs org-services <ORG> class-of-service app-qos-policies Default-Policy rules Business-Traffic set qos-profile Custom-Profile



Associate Interface / Network

* QoS logs are exported only when shaping is configured with logging enabled on an SD-WAN link.  Enable a nonzero logging interval for each WAN interface. If you set the logging interval to zero, no logs are sent


set orgs org-services <ORG> class-of-service networks Internet logging-interval 50 (sec)
set orgs org-services <ORG> class-of-service networks Internet log-fc-stats true
set orgs org-services <ORG> class-of-service networks Internet shaping-rate
set orgs org-services <ORG> class-of-service networks Internet shaping-rate rate 100000 (kbps)
set orgs org-services <ORG> class-of-service networks Internet shaping-rate burst-size 125000 (bytes)



#######################################################################


Troubleshooting


Branch site

  • Verify if qos statistics towards collector is incrementing

show orgs org-services <ORG> lef collectors <Collector> statistics | grep sdwan


  • Verify tx packets, tx dropped, qlen, tx rate and burst size for the interface in network for which logging is required

show class-of-services interfaces extensive <vni-interface>


Analytics

  • On Analytics node verify if sdwanAccCktCosFCLog is being receivedeved for respective ORG and Site

sudo su

cd /var/tmp/log/tenant-<ORG>/backup/

cd VSN0-<Branch>

grep -iR "cos" *




This KB is for demonstration purpose only, all configurations should be as per organizational requirement.

* In case logs for FC sub queues are still not seen on Analytics. Please reach out to Versa Support and open a TAC case.