Dell PowerConnect B-RX16 Installation Guide - Page 146

Displaying a packet log, 16 for BigIron RX-16.

Page 146 highlights

5 Enabling and disabling packet logging for management and interface modules Specify the stop keyword to stop packet logging. NOTE When finished gathering packet logging information for debugging purposes, Brocade recommends disabling the generation of a packet log, which is CPU-intensive and can affect the performance of the management module. Displaying a packet log You can use the following methods to display the contents of a packet log: • You can use the show packet-logging command, which is discussed in this section. • If you decided to write the log (pktlog.txt) to the management module flash memory, in addition to using the show packet-logging command, you can access and view the log using flash memory file management commands. For example, to display a packet log for the interface module in chassis slot 1 that has been written to the system's memory, enter the following command at any CLI level: BigIron RX# show packet-logging 1 memory ..Total 31 packet records TX (Assist Header 0x11f: ver-0, priority-0, pkt_type-ARP packet) (Foundry Header: fid-0x82, priority-3, sac-0, monitor-0, ipc_flag-0x1f, reserved-0, pri_tagged-0, multicast_vid-0, protocol_type-0x2, us-0, brd-0, dav-0, sav-0, dpv-0, sv-0, error-0, txa-0, sas-0, tagged-0, offset-16, vlan_prio-0, cfi- 0, vlan_id-1) 011f0082 cf820010 000107c0 0060800b 020000e0 52ea1f00 000cdb80 32820806 00010800 06040002 000cdb80 32820101 010100e0 52ea1f00 01010102 5204ab10 RX (Assist Header 0x0: ver-0, priority-0, pkt_type-IP packet) (LP2MP_ALT_FDRY_HDR 10 bytes: data-8 bytes, source_port-130, pkt_data_offset-30, virtual_src_int-130) 0000bfff cf808810 00012087 80824de9 4001000c db803282 00e052ea 1f000800 4500002c 28e40000 40014de9 01010102 01010101 08003916 abcd0001 61626364 TX (Assist Header 0xf: ver-0, priority-0, pkt_type-IP packet) (Foundry Header: fid-0x82, priority-3, sac-0, monitor-0, ipc_flag-0x1f, reserved-0, pri_tagged-0, multicast_vid-0, protocol_type-0x1, us-0, brd-0, dav-0, sav-0, dpv-0, sv-0, error-0, txa-0, sas-1, tagged-0, offset-16, vlan_prio-0, cfi- 0, vlan_id-1) 000f0082 cf810090 000107c0 004c800b 020000e0 52ea1f00 000cdb80 32820800 4500002c 86a20000 4001f02a 01010101 01010102 00004116 abcd0001 61626364 Syntax: show packet-logging memory | flash pktlog.txt For the parameter, you can specify 1 - 4 for BigIron RX-4, 1 - 8 for BigIron RX-8 or 1 - 16 for BigIron RX-16. The memory | flash pktlog.txt keyword specifies that the packet log is written to the system's memory or to a file (pktlog.txt) written to the system's flash memory. 134 BigIron RX Installation Guide 53-1001811-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
  • 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

134
BigIron RX Installation Guide
53-1001811-01
Enabling and disabling packet logging for management and interface modules
5
Specify the
stop
keyword to stop packet logging.
NOTE
When finished gathering packet logging information for debugging purposes, Brocade recommends
disabling the generation of a packet log, which is CPU-intensive and can affect the performance of
the management module.
Displaying a packet log
You can use the following methods to display the contents of a packet log:
You can use the
show packet-logging
command, which is discussed in this section.
If you decided to write the log (pktlog.txt) to the management module flash memory, in addition
to using the
show packet-logging
command, you can access and view the log using flash
memory file management commands.
For example, to display a packet log for the interface module in chassis slot 1 that has been written
to the system’s memory, enter the following command at any CLI level:
Syntax:
show packet-logging <slot-number> memory | flash pktlog.txt
For the <slot-number> parameter, you can specify 1 – 4 for BigIron RX-4, 1 – 8 for BigIron RX-8 or 1
– 16 for BigIron RX-16.
The
memory
|
flash pktlog.txt
keyword specifies that the packet log is written to the system’s
memory or to a file (pktlog.txt) written to the system’s flash memory.
BigIron RX# show packet-logging 1 memory
..Total 31 packet records...
-----------------------------------------------------------------------
--> TX
(Assist Header 0x11f: ver-0, priority-0, pkt_type-ARP packet)
(Foundry Header: fid-0x82, priority-3, sac-0, monitor-0, ipc_flag-0x1f,
reserved-0, pri_tagged-0, multicast_vid-0, protocol_type-0x2, us-0, brd-0,
dav-0, sav-0, dpv-0, sv-0, error-0, txa-0, sas-0, tagged-0, offset-16,
vlan_prio-0, cfi- 0, vlan_id-1)
011f0082 cf820010 000107c0 0060800b 020000e0 52ea1f00 000cdb80 32820806
00010800 06040002 000cdb80 32820101 010100e0 52ea1f00 01010102 5204ab10
-----------------------------------------------------------------------
--> RX
(Assist Header 0x0: ver-0, priority-0, pkt_type-IP packet)
(LP2MP_ALT_FDRY_HDR 10 bytes: data-8 bytes, source_port-130,
pkt_data_offset-30, virtual_src_int-130)
0000bfff cf808810 00012087 80824de9 4001000c db803282 00e052ea 1f000800
4500002c 28e40000 40014de9 01010102 01010101 08003916 abcd0001 61626364
-----------------------------------------------------------------------
==> TX
(Assist Header 0xf: ver-0, priority-0, pkt_type-IP packet)
(Foundry Header: fid-0x82, priority-3, sac-0, monitor-0, ipc_flag-0x1f,
reserved-0, pri_tagged-0, multicast_vid-0, protocol_type-0x1, us-0, brd-0,
dav-0, sav-0, dpv-0, sv-0, error-0, txa-0, sas-1, tagged-0, offset-16,
vlan_prio-0, cfi- 0, vlan_id-1)
000f0082 cf810090 000107c0 004c800b 020000e0 52ea1f00 000cdb80 32820800
4500002c 86a20000 4001f02a 01010101 01010102 00004116 abcd0001 61626364
-----------------------------------------------------------------------
...