debug metadata
To enable debugging for metadata flow, use the debug metadata command in privileged EXEC mode. To disable debugging for metadata flow, use the no form of this command.
Cisco IOS Release 15.1(1)SY and Later Releases
debug metadata {encode-decode {details | errors | events} | flow {all | core | cpl | table} | ha | nbar}
no debug metadata {encode-decode {details | errors | events} | flow {all | core | cpl | table} | ha | nbar}
Releases Prior to Cisco IOS Release 15.1(1)SY
debug metadata {encode-decode {details | errors | events} | flow {core | table}}
no debug metadata {encode-decode {details | errors | events} | flow {core | table}}
Syntax Description
encode-decode |
Enables debugging of the metadata encoding and decoding mechanism. |
details |
Enables debugging of the details related to the metadata encoding and decoding mechanism. |
errors |
Debugs any errors that occurred during the encode-decode process. |
events |
Debugs events that occurred during the encode-decode process. |
flow |
Debugs details related to metadata flow. |
all |
Debugs metadata flow information. |
core |
Debugs core metadata events information. |
cpl |
Debugs metadata flow classification information. |
table |
Debugs metadata flow table information. |
ha |
Debugs details related to metadata high availability (HA). |
nbar |
Debugs details related to metadata network-based application recognition (NBAR). |
Command Default
Debugging for metadata flow is disabled.
Command Modes
Privileged EXEC (#)
Command History
Release |
Modification |
---|---|
15.2(1)T |
This command was introduced. |
15.1(1)SY |
This command was modified. The all , cpl , ha , and nbar keywords were added. |
Examples
The following is sample output from the debug metadata encode-decode details command. The debug output shows the process for creating the IP Flow Information Export (IPFIX) template and decoding the metadata information. The last two lines indicate the length, variable length information ID, and the metadata application name.
Device# debug metadata encode-decode details
*Jul 14 03:24:50.395: MED-IPFIX: Hdr: Ver 10 msg len 66
*Jul 14 03:24:50.395: MED-IPFIX: Hdr: Export time = Thu
*Jul 14 08:54:50 2011
*Jul 14 03:24:50.395: MED-IPFIX: Hdr: Seq num = 4
*Jul 14 03:24:50.395: MED-IPFIX: Hdr: Obs dom ID = 0
*Jul 14 03:24:50.395: MED-IPFIX: Creating IP FIX Template, 79CD778
*Jul 14 03:24:50.395: MED-IPFIX: Decoded and saved ID 256 Templates Address 79CD778
*Jul 14 03:24:50.395: MED-IPFIX: Decoding 2 Template fields
*Jul 14 03:24:50.395: MED-IPFIX: len=4 936750775487430656
*Jul 14 03:24:50.395: MED-IPFIX: VLIE len 17 [telepresence-data]
The following is sample output from the debug metadata flow all command. The first line of the output displays the addition of an event. The output then shows the details of the ingress and egress interfaces. Next, the display shows the various application names and the associated application IDs. The ID is followed by the classification types and the matching of the applications. The last line indicates that an appropriate match was detected and the control plane classification has completed successfully.
Device# debug metadata flow all
*Jul 14 08:07:23.155: FMD SIG: Process RSVP Event RSVP_FMD_EVENT_PAYLOAD_RECEIVED(1)
*Jul 14 08:07:23.155: FMD : fmd_post_events: posting event 0
*Jul 14 08:07:23.167: FMD Process Event - FMD_RSVP_TRANSPORT_ADD
*Jul 14 08:07:23.167: (fmd_add_event_process): For Source IP/Port : 67372036/1000
*Jul 14 08:07:23.167: FMD DB Lookup: Hash 391
*Jul 14 08:07:23.167: FMD Event for Ingress Interface Ethernet0/0 , Egress Interface Ethernet0/1
*Jul 14 08:07:23.167: FMD Classification Src Type 96, Len 17, Value telepresence-data
*Jul 14 08:07:23.167: FMD Classification Dest Type 95, Len 4, Value
*Jul 14 08:07:23.167: App name telepresence-data id 218104286 in Metadata local app table *Jul 14 08:07:23.167: FMD Classification Src Type 96, Len 11, Value webex-audio
*Jul 14 08:07:23.167: FMD Classification Dest Type 95, Len 4, Value
*Jul 14 08:07:23.167: App name webex-audio id 12 in Metadata local app table
*Jul 14 08:07:23.167: FMD Classification Src Type 96, Len 11, Value webex-audio
*Jul 14 08:07:23.167: FMD Classification Dest Type 96, Len 17, Value telepresence-data *Jul 14 08:07:23.167: FMD Classification Src Type 96, Len 11, Value webex-audio
*Jul 14 08:07:23.167: FMD Classification Dest Type 0, Len 0, Value
*Jul 14 08:07:23.167: FMD Classification: Match Passed for type 95 value Router-201
*Jul 14 08:07:23.167: FMD Classification: Found 1 filters matching
*Jul 14 08:07:23.167: FMD Event: Input policy Matched, Add flow to CFT
*Jul 14 08:07:23.167: FMD Event: PPCP Binding Succeeded
*Jul 14 08:07:23.167: FMD fmd_add_update_ingress_cft_fo : fid 4
*Jul 14 08:07:23.167: FMD Event: Local Flow ID 0
*Jul 14 08:07:23.167: (fmd_add_event_process): Update with Template Addres 79CD778, Md Addr 947F810
*Jul 14 08:07:23.167: fmd_add_ipv4_flow_node_to_hash: Hash 391
*Jul 14 08:07:23.167: FMD Event: DB Addition Succeded