Why is my traffic being classified under Default by PacketShaper?

book

Article ID: 167596

calendar_today

Updated On:

Products

PacketShaper

Issue/Introduction

For example, SAP traffic is being classified in Inbound/Default and Outbound/Default.

Resolution

Run the commands traffic flow -tupxsfIC inbound/default and traffic flow -tupxsfIC outbound/default, and refer to the Flag column. If you see S or s, the traffic is asymmetric. The flag S indicates that the packet has SYN-ACK but no SYN, while s indicates that the packet has SYN without SYN-ACK. PacketShaper requires a complete TCP handshake for classification.

 

InAddr           Port OutAddr          Port Idle S Flags ClasI            ClasO             Svc
----------------------------------------------------------------------------------------------------
192.168.21.243   3215 10.0.67.172      3452 33s X      S /Inbound/Default /Outbound/Default -
192.168.21.230   3600 10.0.67.172      3449 36s H O    S /Inbound/Default /Outbound/Default -
192.168.21.237   3218 172.0.37.43     49180 52s H O    S /Inbound/Default /Outbound/Default -

 

To avoid traffic being unclassified, you need to review the deployment and understand the packet path and route.