Symptom
Amazon-web services for some flows are not getting detected when traffic is passing through cEdge device
Conditions
NBAR is classifying the application correctly for some packets, but not for all. User is able to open
Path Trace
Feature: IPV4(Input)
Input : GigabitEthernet0/0/0
Output :
Source : 192.168.30.30
Destination : 192.168.10.1
Protocol : 6 (TCP)
SrcPort : 36506
DstPort : 443
Feature: NBAR
Packet number in flow: 25
Classification state: Final
Classification name: a mazon-web-services
Classification ID: [CANA-L7:603]
Classification source: Unknown
Number of matched sub-classifications: 0
Number of extracted fields: 0
Is PA (split) packet: False
TPH-MQC bitmask value: 0x4
Is optimize packet: False
Is allow packet: False
BR3-cEdge-1_Template#show ip nbar protocol-id | in amazon-web
amazon-web-services 603 L7 STANDARD
For some flows action is forward:
Summary
Input : GigabitEthernet0/0/0
Output : GigabitEthernet0/0/1
State : FWD
Path Trace
Feature: IPV4(Input)
Input : GigabitEthernet0/0/0
Output :
Source : 192.168.30.30
Destination : 192.168.20.1
Protocol : 6 (TCP)
SrcPort : 44516
DstPort : 443
Feature: NBAR
Packet number in flow: 1
Classification state: Not final << NBAR unable to classify this flow
Classification name: unknown
Classification ID: [CANA-L7:1]
Classification source: Unknown
Number of matched sub-classifications: 0
Number of extracted fields: 0
Is PA (split) packet: False
TPH-MQC bitmask value: 0x0
Is optimize packet: False
Is allow packet: False
