Cisco N5K-C5010P-BF Troubleshooting Guide - Page 20

Suspending the SPAN Session, Debugging, Command-Line Debugging, Debug Logging

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 20 highlights

Fabric Manager Tools and CLI Commands Chapter 1 Troubleshooting Overview Send document comments to [email protected]. switch# show monitor session 1 session 1 type : local state : up source intf : rx : fc3/1 tx : fc3/1 both : fc3/1 source VLANs : rx : source VSANs : rx : destination ports : fc3/2 Suspending the SPAN Session Example: switch(config)# monitor session 1 suspend switch(config)# show monitor session 1 session 1 type : local state : down (Session suspended) source intf : rx : fc3/1 tx : fc3/1 both : fc3/1 source VLANs : rx : source VSANs : rx : destination ports : fc3/2 Debugging Command-Line Debugging Available debugs depend on features enabled in NX-OS. There are many different options to select when turning on debugs. Determine the destination of the output: • Logfile-Data file in switch memory. • Capture to direct to screen via console, Telnet, or SSH. You must have administrator privileges to run debugs. Debugs can only be run from the CLI. Debug Logging Set the log file as CiscoLive_debugs, using the debug logfile command. Then, use the show debug command to see name of the debug file. 1-12 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01

  • 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
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
Send document comments to [email protected].
1-12
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 1
Troubleshooting Overview
Fabric Manager Tools and CLI Commands
switch# show monitor session 1
session 1
---------------
type
: local
state
: up
source intf
:
rx
: fc3/1
tx
: fc3/1
both
: fc3/1
source VLANs
:
rx
:
source VSANs
:
rx
:
destination ports : fc3/2
Suspending the SPAN Session
Example:
switch(config)# monitor session 1 suspend
switch(config)# show monitor session 1
session 1
---------------
type
: local
state
: down (Session suspended)
source intf
:
rx
: fc3/1
tx
: fc3/1
both
: fc3/1
source VLANs
:
rx
:
source VSANs
:
rx
:
destination ports : fc3/2
Debugging
Command-Line Debugging
Available debugs depend on features enabled in NX-OS. There are many different options to select when
turning on debugs.
Determine the destination of the output:
•
Logfile—Data file in switch memory.
•
Capture to direct to screen via console, Telnet, or SSH.
You must have administrator privileges to run debugs. Debugs can only be run from the CLI.
Debug Logging
Set the log file as CiscoLive_debugs, using the
debug logfile
command. Then, use the
show debug
command to see name of the debug file.