HP 1606 Fabric OS FCIP Administrators Guide v6.4.0 (53-1001766-01, November 20 - Page 113

Example of capturing an FTRACE on a tunnel, Verify an FTRACE has occurred

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

Page 113 highlights

FTRACE concepts 4 Example of capturing an FTRACE on a tunnel This process defines how to capture an FTRACE buffer for a 7800 switch or FR4-18i blade, save it, and then enter the supportSave command that includes that data. NOTE For the 7800 and FX8-24, any triggered or checked out and current non-empty trace buffers are captured in a supportSave automatically. There is no user command to force the saving of a trace buffer. If there is a need to capture and save an FTRACE buffer, you may check a buffer out manually, then take a supportSave and the FTRACE data will be included in the supportSave output. 1. Enable FTRACE on ge1 interface tunnel 0 using the default parameters: switch:admin> portcfg ftrace ge1 0 cfg -e 1 NOTE The -e 1 enables FTRACE with all of the default options. There may be times that the default parameters must be modified to capture more information. 2. Verify an FTRACE has occurred To verify if an FTRACE was generated on ge1 tunnel 0, issue the portShow ftrace ge1 0 stats command. You will notice the status of buffer ID 0 changed from Current to Triggered. The status of buffer 1 will change from unused to Current. | | | |Trace Header| Wrap | In | Out | Switch | Switch | | Id | State | Size | Address | Count | OXID | OXID | Date | Time | | 0 | Triggered | 200000 | 0x10010000 | 65 | FFFF | FFFF | 04/23/2008 | 23:14:14 | | 1| Current | 200000 | 0x10010100 | 0 | FFFF | FFFF | | | | 2| unused | 200000 | 0x10010200 | 0 | FFFF | FFFF | | | | 3| unused | 200000 | 0x10010300 | 0 | FFFF | FFFF | | | NOTE If there are multiple Triggered events, capture and manage them all in the procedures to follow. 3. Save an FTRACE to the blade processor (BP). The following command is used to save ge1 tunnel 0 buffer ID 0 to the BP: switch:admin> portshow ftrace ge1 0 save 0 Buffer 0 will be saved 16000320 bytes will be saved for buffer 0. Write Progress: 491840 of 16000320 bytes sent Write Progress: 1311040 of 16000320 bytes sent Write Progress: 2146624 of 16000320 bytes sent Write Progress: 2965824 of 16000320 bytes sent Write Progress: 3801408 of 16000320 bytes sent Write Progress: 4030784 of 16000320 bytes sent Write Progress: 4309312 of 16000320 bytes sent Write Progress: 5144896 of 16000320 bytes sent Fabric OS FCIP Administrator's Guide 99 53-1001766-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
Fabric OS FCIP Administrator’s Guide
99
53-1001766-01
FTRACE concepts
4
Example of capturing an FTRACE on a tunnel
This process defines how to capture an FTRACE buffer for a 7800 switch or FR4-18i blade, save it,
and then enter the
supportSave
command that includes that data.
NOTE
For the 7800 and FX8-24, any triggered or checked out and current non-empty trace buffers are
captured in a supportSave automatically. There is no user command to force the saving of a trace
buffer. If there is a need to capture and save an FTRACE buffer, you may check a buffer out manually,
then take a supportSave and the FTRACE data will be included in the supportSave output.
1.
Enable FTRACE on ge1 interface tunnel 0 using the default parameters:
switch:admin> portcfg ftrace ge1 0 cfg -e 1
NOTE
The –e 1 enables FTRACE with all of the default options. There may be times that the default
parameters must be modified to capture more information.
2.
Verify an FTRACE has occurred
To verify if an FTRACE was generated on ge1 tunnel 0, issue the p
ortShow ftrace ge1 0 stats
command. You will notice the status of buffer ID 0 changed from Current to Triggered. The
status of buffer 1 will change from unused to Current.
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
|
|
|
|Trace Header|
Wrap
| In
| Out
|
Switch
|
Switch
|
|
Id |
State
|
Size
|
Address
|
Count
| OXID | OXID |
Date
|
Time
|
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
|
0 |
Triggered | 200000 | 0x10010000 |
65 | FFFF | FFFF |
04/23/2008 | 23:14:14 |
|
1 |
Current | 200000 | 0x10010100 |
0 | FFFF | FFFF |
|
|
|
2 |
unused | 200000 | 0x10010200 |
0 | FFFF | FFFF |
|
|
|
3 |
unused | 200000 | 0x10010300 |
0 | FFFF | FFFF |
|
|
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
NOTE
If there are multiple Triggered events, capture and manage them all in the procedures to follow.
3.
Save an FTRACE to the blade processor (BP).
The following command is used to save ge1 tunnel 0 buffer ID 0 to the BP:
switch:admin> portshow ftrace ge1 0 save 0
Buffer 0 will be saved
16000320 bytes will be saved for buffer 0.
Write Progress: 491840 of 16000320 bytes sent
Write Progress: 1311040 of 16000320 bytes sent
Write Progress: 2146624 of 16000320 bytes sent
Write Progress: 2965824 of 16000320 bytes sent
Write Progress: 3801408 of 16000320 bytes sent
Write Progress: 4030784 of 16000320 bytes sent
Write Progress: 4309312 of 16000320 bytes sent
Write Progress: 5144896 of 16000320 bytes sent