Cisco N5K-C5010P-BF Troubleshooting Guide - Page 19

Monitor Caveats, SPAN Configuration, Verifying the SPAN Session - list

Page 19 highlights

Chapter 1 Troubleshooting Overview Fabric Manager Tools and CLI Commands Send document comments to [email protected]. • Does not participate in spanning tree while the SPAN session is active. • Is excluded from the source list and is not monitored if it belongs to a source VLAN of any SPAN session. • Receives copies of sent and received traffic for all monitored source ports. If a destination port is oversubscribed, it can become congested. This congestion can affect traffic forwarding on one or more of the source ports. Monitor Caveats Limitations of Nexus 5000 SPAN CoS values are not preserved at the monitor (span) destination. • Packets coming in on the monitor source with an unknown VLAN tag are spanned ouf with a 0 VLAN tag (priority tag). • For Ethernet destination, the monitor session is up only if the destination port is configured as switch port monitor. • Out of 18 configurable sessions, only two are active (up state). The rest are in down state (hardware resource unavailable). Configuration limitations: VLAN or port-channel cannot be configured as egress source • VLAN or port channel cannot be a monitor destination. • Only two egress sources supported. • Only one destination port can be configured for a session. SPAN Configuration Example: switch(config)# interface fc3/2 switch(config-if)# switchport mode sd switch(config-if)# switchport speed 1000 switch(config-if)# no shut switch(config-if)# exit switch(config)# monitor session 1 switch(config-monitor)# source interface fc3/1 tx switch(config-monitor)# source interface fc3/1 rx switch(config-monitor)# destination interface fc3/2 DS-PAA Nexus 5020 FC3/2 FC3/1 199999 Verifying the SPAN Session Example: switch# show monitor session SESSION STATE REASON 1 up The session is up DESCRIPTION OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 1-11

  • 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-11
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 1
Troubleshooting Overview
Fabric Manager Tools and CLI Commands
Does not participate in spanning tree while the SPAN session is active.
Is excluded from the source list and is not monitored if it belongs to a source VLAN of any SPAN
session.
Receives copies of sent and received traffic for all monitored source ports. If a destination port is
oversubscribed, it can become congested. This congestion can affect traffic forwarding on one or
more of the source ports.
Monitor Caveats
Limitations of Nexus 5000 SPAN CoS values are not preserved at the monitor (span) destination.
Packets coming in on the monitor source with an unknown VLAN tag are spanned ouf with a 0
VLAN tag (priority tag).
For Ethernet destination, the monitor session is up only if the destination port is configured as switch
port monitor.
Out of 18 configurable sessions, only two are active (up state). The rest are in down state (hardware
resource unavailable).
Configuration limitations: VLAN or port-channel cannot be configured as egress source
VLAN or port channel cannot be a monitor destination.
Only two egress sources supported.
Only one destination port can be configured for a session.
SPAN Configuration
Example:
switch(config)# interface fc3/2
switch(config-if)# switchport mode sd
switch(config-if)# switchport speed 1000
switch(config-if)# no shut
switch(config-if)# exit
switch(config)# monitor session 1
switch(config-monitor)# source interface fc3/1 tx
switch(config-monitor)# source interface fc3/1 rx
switch(config-monitor)# destination interface fc3/2
Verifying the SPAN Session
Example:
switch# show monitor session
SESSION
STATE
REASON
DESCRIPTION
-------
-----------
----------------------
--------------------------------
1
up
The session is up
FC3/1
FC3/2
Nexus 5020
DS-PAA
199999