HP 6125XLG R2306-HP 6125XLG Blade Switch Network Management and Monitoring Con - Page 12

Debugging information control switches, Debugging a feature module, Network Management and Monitoring

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

Debugging information control switches The following switches control the display of debugging information: • Module debugging switch-Controls whether to generate the module-specific debugging information. • Screen output switch-Controls whether to display the debugging information on a certain screen. Use terminal monitor and terminal logging level commands to turn on the screen output switch. For more information about these two commands, see Network Management and Monitoring Command Reference. As shown in Figure 4, assume that the device can provide debugging for the three modules 1, 2, and 3. The debugging information can be output on a terminal only when both the module debugging switch and the screen output switch are turned on. Debugging information is typically displayed on a console. You can also send debugging information to other destinations. For more information, see "Configuring the information center." Figure 4 Relationship between the module and screen output switch Debugging a feature module Output of debugging commands is memory intensive. To guarantee system performance, enable debugging only for modules that are in an exceptional condition. When debugging is complete, use the undo debugging all command to disable all the debugging functions. To debug a feature module: Step Command 1. Enable debugging for a debugging { all [ timeout time ] | specified module in user view. module-name [ option ] } 2. (Optional.) Display the enabled debugging in any view. display debugging [ module-name ] Remarks By default, all debugging functions are disabled. N/A 6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
6
Debugging information control switches
The following switches control the display of debugging information:
•
Module debugging switch
—Controls whether to generate the module-specific debugging
information.
•
Screen output switch
—Controls whether to display the debugging information on a certain screen.
Use
terminal monitor
and
terminal logging level
commands to turn on the screen output switch. For
more information about these two commands, see
Network Management and Monitoring
Command Reference
.
As shown in
Figure 4
, assume that the device can provide debugging for the three modules 1, 2, and 3.
The debugging information can be output on a terminal only when both the module debugging switch
and the screen output switch are turned on.
Debugging information is typically displayed on a console. You can also send debugging information to
other destinations. For more information, see "
Configuring the information center
."
Figure 4
Relationship between the module and screen output switch
Debugging a feature module
Output of debugging commands is memory intensive. To guarantee system performance, enable
debugging only for modules that are in an exceptional condition. When debugging is complete, use the
undo debugging all
command to disable all the debugging functions.
To debug a feature module:
Step
Command
Remarks
1.
Enable debugging for a
specified module in user view.
debugging
{
all
[
timeout
time
] |
module-name
[
option
] }
By default, all debugging functions
are disabled.
2.
(Optional.) Display the
enabled debugging in any
view.
display
debugging
[
module-name
]
N/A