Dell PowerEdge XL 5133-4 MXL 10/40GbE Switch IO Module FTOS Command Reference - Page 199

Port Monitoring, Important Points to Remember

Page 199 highlights

15 Port Monitoring The Aggregator supports user-configured port monitoring. See Configuring Port Monitoring for the configuration commands to use. Port monitoring copies all incoming or outgoing packets on one port and forwards (mirrors) them to another port. The source port is the monitored port (MD) and the destination port is the monitoring port (MG). Important Points to Remember • Port monitoring is supported on physical ports only; virtual local area network (VLAN) and port-channel interfaces do not support port monitoring. • The monitored (source, MD) and monitoring ports (destination, MG) must be on the same switch. • The monitored (source) interface must be a server-facing interface in the format slot/port, where the valid slot numbers are 0 or 1 and server-facing port numbers are from 1 to 32. • The destination interface must be an uplink port (ports 33 to 56). • In general, a monitoring port should have no ip address and no shutdown as the only configuration; FTOS permits a limited set of commands for monitoring ports. To display these commands, use the command ?. • A monitoring port may not be a member of a VLAN. • There may only be one destination port in a monitoring session. • A source port (MD) can only be monitored by one destination port (MG). If you try to assign a monitored port to more than one monitoring port, the following error is displayed (Message 1). Message 1 Assign a Monitored Port to More than One Monitoring Port FTOS(conf)#mon ses 1 FTOS(conf-mon-sess-1)#source tengig 0/1 destination tengig 0/33 direction both FTOS(conf-mon-sess-1)#do show monitor session SessionID Source Destination Direction Mode Type --------- ------ ----------- --------- ---- ---- 1 TenGig 0/1 TenGig 0/33 both interface Port-based FTOS(conf-mon-sess-1)#mon ses 2 FTOS(conf-mon-sess-2)#source tengig 0/1 destination tengig 0/33 direction both % Error: MD port is already being monitored. Note: There is no limit to the number of monitoring sessions per system, provided that there are only four destination ports per port-pipe. If each monitoring session has a unique destination port, the maximum number of session is four per port-pipe. Port Monitoring | 185

  • 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
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290

Port Monitoring
|
185
15
Port Monitoring
The Aggregator supports user-configured port monitoring. See
Configuring Port Monitoring
for the
configuration commands to use.
Port monitoring copies all incoming or outgoing packets on one port and forwards (mirrors) them to
another port. The source port is the monitored port (MD) and the destination port is the monitoring port
(MG).
Important Points to Remember
Port monitoring is supported on physical ports only; virtual local area network (VLAN) and
port-channel interfaces do not support port monitoring.
The monitored (source, MD) and monitoring ports (destination, MG) must be on the same switch.
The monitored (source) interface must be a server-facing interface in the format
slot
/
port
, where the
valid slot numbers are 0 or 1 and server-facing port numbers are from 1 to 32.
The destination interface must be an uplink port (ports 33 to 56).
In general, a monitoring port should have
no ip address
and
no shutdown
as the only configuration;
FTOS permits a limited set of commands for monitoring ports. To display these commands, use the
command
?
.
A monitoring port may not be a member of a VLAN.
There may only be one destination port in a monitoring session.
A source port (MD) can only be monitored by one destination port (MG). If you try to assign a
monitored port to more than one monitoring port, the following error is displayed (
Message 1
).
Message 1
Assign a Monitored Port to More than One Monitoring Port
FTOS(conf)#mon ses 1
FTOS(conf-mon-sess-1)#source tengig 0/1 destination tengig 0/33 direction both
FTOS(conf-mon-sess-1)#do show monitor session
SessionID
Source
Destination
Direction
Mode
Type
---------
------
-----------
---------
----
----
1
TenGig 0/1
TenGig 0/33
both
interface
Port-based
FTOS(conf-mon-sess-1)#mon ses 2
FTOS(conf-mon-sess-2)#source tengig 0/1 destination tengig 0/33 direction both
% Error: MD port is already being monitored.
Note:
There is no limit to the number of monitoring sessions per system, provided that there are only four
destination ports per port-pipe. If each monitoring session has a unique destination port, the maximum
number of session is four per port-pipe.