Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Medianet Classification of Jabber for Windows fails

Hello,

i am struggeling with setting up a classmap for jabber for windows 9.2.2 on my router. I created a class-map and added the application jabber but non of the incoming traffic is recognized as jabber application.

this is my configuration

[global]

metadata flow transmit

metadata flow

!

flow monitor type performance-monitor pm-m-tcp

record pm-r-tcp

exporter xport1

!

class-map match-any JABBER

match application jabber

!

policy-map type performance-monitor pm-1

class JABBER

   flow monitor pm-m-tcp

[interface GigabitEthernet0/0]

ip address 10.100.0.1 255.255.255.0

duplex auto

speed auto

metadata flow

service-policy type performance-monitor input pm-1

service-policy type performance-monitor output pm-1

after adding the command match application in the class map configuration i get these messages

*Jul 18 08:13:47.959: FMD CPL: fmd_classmap_filter_update:if:  filter: "application jabber" class: TP dir: IN event 0

*Jul 18 08:13:47.959: FMD CPL: fmd_classmap_filter_update:if: Gi0/0 filter: "application jabber" class: TP dir: IN event 33

*Jul 18 08:13:47.959: FMD CPL: fmd_classmap_filter_update:if: Gi0/0 filter: "application jabber" class: TP dir: OUT event 33

*Jul 18 08:13:47.959: FMD CPL::fmd_qoscli_if_policy_modified:(Gi0/0:IN): ptype: 42 event: 36

*Jul 18 08:13:47.959: FMD CPL: fmd_policy_interface_event_handler: if: Gi0/0 dir IN policy pm-1 event 36 pl_type 42

*Jul 18 08:13:47.959: FMD CPL: fmd_policy_interface_event_handler: event : 36

*Jul 18 08:13:47.959: FMD NBAR: Received Deactivate event

*Jul 18 08:13:47.959: FMD NBAR: Match application command found

*Jul 18 08:13:47.959: FMD NBAR: Failed to get protocol id for jabber, skipping

*Jul 18 08:13:47.959: FMD NBAR: class_id 1 name UDP

*Jul 18 08:13:47.959: FMD NBAR: Non Metadata filter type 2. Skipping

*Jul 18 08:13:47.959: FMD NBAR: class_id 2 name TCP

*Jul 18 08:13:47.959: FMD NBAR: Non Metadata filter type 2. Skipping

*Jul 18 08:13:47.959: FMD NBAR: class_id 3 name TP

*Jul 18 08:13:47.959: FMD NBAR: fmd filter "application jabber"

*Jul 18 08:13:47.959: FMD NBAR: Match application command found

*Jul 18 08:13:47.959: FMD NBAR: Failed to activate NBAR for jabber

*Jul 18 08:13:47.959: FMD NBAR: class_id 0 name class-default

*Jul 18 08:13:47.959: FMD NBAR: Non Metadata filter type 26. Skipping

*Jul 18 08:13:47.959: FMD CPL: Registering CFT for Gi0/0 dir IN

*Jul 18 08:13:47.963: FMD CPL:Gi0/0(IN): Walk and classify all the flows for policy type 1

*Jul 18 08:13:47.963: FMD CPL: Runtime policymap update - intf Gi0/0 dir IN policymap pm-1 event 197

*Jul 18 08:13:47.963: FMD CPL: fmd_policy_interface_event_handler: if: Gi0/0 dir IN policy pm-1 event 197 pl_type 42

*Jul 18 08:13:47.963: FMD CPL: fmd_policy_interface_event_handler: event : 197

*Jul 18 08:13:47.963: FMD NBAR: NULL Event Data

*Jul 18 08:13:47.963: FMD NBAR: class_id 1 name UDP

*Jul 18 08:13:47.963: FMD NBAR: Non Metadata filter type 2. Skipping

*Jul 18 08:13:47.963: FMD NBAR: class_id 2 name TCP

*Jul 18 08:13:47.963: FMD NBAR: Non Metadata filter type 2. Skipping

*Jul 18 08:13:47.963: FMD NBAR: class_id 3 name TP

*Jul 18 08:13:47.963: FMD NBAR: fmd filter "application jabber"

*Jul 18 08:13:47.963: FMD NBAR: Match application command found

*Jul 18 08:13:47.963: FMD NBAR: Failed to activate NBAR for jabber

*Jul 18 08:13:47.963: FMD NBAR: class_id 0 name class-default

*Jul 18 08:13:47.963: FMD NBAR: Non Metadata filter type 26. Skipping

*Jul 18 08:13:47.963: FMD CPL:Gi0/0(IN): Walk and classify all the flows for policy type 1

*Jul 18 08:13:47.963: FMD CPL::fmd_qoscli_if_policy_modified:(Gi0/0:OUT): ptype: 42 event: 36

*Jul 18 08:13:47.963: FMD CPL: fmd_policy_interface_event_handler: if: Gi0/0 dir OUT policy pm-1 event 36 pl_type 42

*Jul 18 08:13:47.963: FMD CPL: fmd_policy_interface_event_handler: event : 36

*Jul 18 08:13:47.963: FMD NBAR: Received Deactivate event

*Jul 18 08:13:47.963: FMD NBAR: Match application command found

*Jul 18 08:13:47.963: FMD NBAR: Failed to get protocol id for jabber, skipping

*Jul 18 08:13:47.963: FMD NBAR: class_id 1 name UDP

*Jul 18 08:13:47.963: FMD NBAR: Non Metadata filter type 2. Skipping

*Jul 18 08:13:47.963: FMD NBAR: class_id 2 name TCP

*Jul 18 08:13:47.963: FMD NBAR: Non Metadata filter type 2. Skipping

*Jul 18 08:13:47.963: FMD NBAR: class_id 3 name TP

*Jul 18 08:13:47.963: FMD NBAR: fmd filter "application jabber"

*Jul 18 08:13:47.963: FMD NBAR: Match application command found

*Jul 18 08:13:47.963: FMD NBAR: Failed to activate NBAR for jabber

*Jul 18 08:13:47.963: FMD NBAR: class_id 0 name class-default

*Jul 18 08:13:47.963: FMD NBAR: Non Metadata filter type 26. Skipping

*Jul 18 08:13:47.963: FMD CPL: Registering CFT for Gi0/0 dir OUT

*Jul 18 08:13:47.963: FMD CPL:Gi0/0(OUT): Walk and classify all the flows for policy type 1

*Jul 18 08:13:47.963: FMD CPL: Runtime policymap update - intf Gi0/0 dir OUT policymap pm-1 event 197

*Jul 18 08:13:47.963: FMD CPL: fmd_policy_interface_event_handler: if: Gi0/0 dir OUT policy pm-1 event 197 pl_type 42

*Jul 18 08:13:47.963: FMD CPL: fmd_policy_interface_event_handler: event : 197

any ideas what is missing?

regards

Alex

Everyone's tags (2)
277
Views
0
Helpful
0
Replies