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

The FTRACE save process will automatically check out trace buffers that have been saved.

Page 114 highlights

4 FTRACE concepts Write Progress: 5964096 of 16000320 bytes sent Write Progress: 6799680 of 16000320 bytes sent Write Progress: 7078208 of 16000320 bytes sent Write Progress: 7700800 of 16000320 bytes sent Write Progress: 8520000 of 16000320 bytes sent Write Progress: 9355584 of 16000320 bytes sent Write Progress: 10174784 of 16000320 bytes sent Write Progress: 10338624 of 16000320 bytes sent Write Progress: 10846528 of 16000320 bytes sent Write Progress: 11665728 of 16000320 bytes sent Write Progress: 12501312 of 16000320 bytes sent Write Progress: 13320512 of 16000320 bytes sent Write Progress: 13451584 of 16000320 bytes sent Write Progress: 13975872 of 16000320 bytes sent Write Progress: 14795072 of 16000320 bytes sent Write Progress: 15630656 of 16000320 bytes sent Write Progress: 16000320 of 16000320 bytes sent Write completed. NOTE If the trace dump process failed, there is probably an issue with the amount of consumed disk on the Blade Processor (BP - the Linux system that is running BFOS). If this is the case, clean up file usage on the BP. 4. Check in the saved FTRACE buffer. The FTRACE save process will automatically "check out" trace buffers that have been saved. | | | |Trace Header| Wrap | In | Out | Switch | Switch | | Id | State | Size | Address | Count | OXID | OXID | Date | Time | | 0 | Checked Out | 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 | | | 5. Re-enable the buffer to be used for trace capture by checking it back in to the FTRACE pool. To check in the trace buffer, issue the following command: switch:admin> portshow ftrace ge1 0 ci 0 Buffer 0 is now checked in. | | | |Trace Header| Wrap | In | Out | Switch | Switch | | Id | State | Size | Address | Count | OXID | OXID | Date | Time | | 0| unused | 200000 | 0x10010000 | 0 | FFFF | FFFF | | | | 1| Current | 200000 | 0x10010100 | 0 | FFFF | FFFF | | | | 2| unused | 200000 | 0x10010200 | 0 | FFFF | FFFF | | | | 3| unused | 200000 | 0x10010300 | 0 | FFFF | FFFF | | | 6. Transfer the FTRACE information off of the switch. 100 Fabric OS FCIP Administrator's Guide 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

100
Fabric OS FCIP Administrator’s Guide
53-1001766-01
FTRACE concepts
4
Write Progress: 5964096 of 16000320 bytes sent
Write Progress: 6799680 of 16000320 bytes sent
Write Progress: 7078208 of 16000320 bytes sent
Write Progress: 7700800 of 16000320 bytes sent
Write Progress: 8520000 of 16000320 bytes sent
Write Progress: 9355584 of 16000320 bytes sent
Write Progress: 10174784 of 16000320 bytes sent
Write Progress: 10338624 of 16000320 bytes sent
Write Progress: 10846528 of 16000320 bytes sent
Write Progress: 11665728 of 16000320 bytes sent
Write Progress: 12501312 of 16000320 bytes sent
Write Progress: 13320512 of 16000320 bytes sent
Write Progress: 13451584 of 16000320 bytes sent
Write Progress: 13975872 of 16000320 bytes sent
Write Progress: 14795072 of 16000320 bytes sent
Write Progress: 15630656 of 16000320 bytes sent
Write Progress: 16000320 of 16000320 bytes sent
Write completed.
NOTE
If the trace dump process failed, there is probably an issue with the amount of consumed disk
on the Blade Processor (BP – the Linux system that is running BFOS). If this is the case, clean
up file usage on the BP.
4.
Check in the saved FTRACE buffer.
The FTRACE save process will automatically “check out” trace buffers that have been saved.
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
|
|
|
|Trace Header|
Wrap
| In
| Out
|
Switch
|
Switch
|
|
Id |
State
|
Size
|
Address
|
Count
| OXID | OXID |
Date
|
Time
|
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
|
0 | Checked Out | 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 |
|
|
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
5.
Re-enable the buffer to be used for trace capture by checking it back in to the FTRACE pool. To
check in the trace buffer, issue the following command:
switch:admin> portshow ftrace ge1 0 ci 0
Buffer 0 is now checked in.
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
|
|
|
|Trace Header|
Wrap
| In
| Out
|
Switch
|
Switch
|
|
Id |
State
|
Size
|
Address
|
Count
| OXID | OXID |
Date
|
Time
|
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
|
0 |
unused | 200000 | 0x10010000 |
0 | FFFF | FFFF |
|
|
|
1 |
Current | 200000 | 0x10010100 |
0 | FFFF | FFFF |
|
|
|
2 |
unused | 200000 | 0x10010200 |
0 | FFFF | FFFF |
|
|
|
3 |
unused | 200000 | 0x10010300 |
0 | FFFF | FFFF |
|
|
+-----+-------------+--------+------------+------------+------+------+-------------+----------+
6.
Transfer the FTRACE information off of the switch.