Cisco Cisco IOS Software Release 12.4(15)XM Références techniques
debug condition
28
Cisco Mobile Wireless Home Agent Feature for IOS Release 12.4(15)XM2
12.4(15)XM2
Usage Guidelines
Use the debug condition command to restrict the debug output for some commands. If any debug
condition commands are enabled, output is only generated for interfaces associated with the specified
keyword. In addition, this command enables debugging output for conditional debugging events.
Messages are displayed as different interfaces meet specific conditions.
condition commands are enabled, output is only generated for interfaces associated with the specified
keyword. In addition, this command enables debugging output for conditional debugging events.
Messages are displayed as different interfaces meet specific conditions.
If multiple debug condition commands are enabled, output is displayed if at least one condition
matches. All the conditions do not need to match.
matches. All the conditions do not need to match.
The no form of this command removes the debug condition specified by the condition identifier. The
condition identifier is displayed after you use a debug condition command or in the output of the show
debug condition command. If the last condition is removed, debugging output resumes for all interfaces.
You will be asked for confirmation before removing the last condition or all conditions.
condition identifier is displayed after you use a debug condition command or in the output of the show
debug condition command. If the last condition is removed, debugging output resumes for all interfaces.
You will be asked for confirmation before removing the last condition or all conditions.
Not all debugging output is affected by the debug condition command. Some commands generate output
whenever they are enabled, regardless of whether they meet any conditions. The commands that are
affected by the debug condition commands are generally related to dial access functions, where a large
amount of output is expected. Output from the following commands is controlled by the debug condition
command:
whenever they are enabled, regardless of whether they meet any conditions. The commands that are
affected by the debug condition commands are generally related to dial access functions, where a large
amount of output is expected. Output from the following commands is controlled by the debug condition
command:
•
debug aaa {accounting | authorization | authentication}
•
debug dialer events
•
debug isdn {q921 | q931}
•
debug modem {oob | trace}
•
debug ppp {all | authentication | chap | error | negotiation | multilink events | packet}
Ensure that you enable TID/IMSI-based conditional debugging by entering debug condition calling
before configuring debug gprs gtp and debug gprs charging. In addition, ensure that you disable the
debug gprs gtp and debug gprs charging commands using the no debug all command before disabling
conditional debugging using the no debug condition command. This will prevent a flood of debugging
messages when you disable conditional debugging.
before configuring debug gprs gtp and debug gprs charging. In addition, ensure that you disable the
debug gprs gtp and debug gprs charging commands using the no debug all command before disabling
conditional debugging using the no debug condition command. This will prevent a flood of debugging
messages when you disable conditional debugging.
Examples
Example 1
In the following example, the router displays debugging messages only for interfaces that use a username
of fred. The condition identifier displayed after the command is entered identifies this particular
condition.
of fred. The condition identifier displayed after the command is entered identifies this particular
condition.
Router# debug condition username fred
Condition 1 set
Example 2
The following example specifies that the router should display debugging messages only for VC 1000:
Router# debug condition vcid 1000
Condition 1 set
01:12:32: 1000 Debug: Condition 1, vcid 1000 triggered, count 1
01:12:32: 1000 Debug: Condition 1, vcid 1000 triggered, count 1
Other debugging commands are enabled, but they will only display debugging for VC 1000.
Router# debug mpls l2transport vc event