HP NetServer AA 4000 HP AA HP Netserver 4000 Reference Guide - Page 32

Test 3: Verify Host < - > MIC DMA, Test 4: Verify MIC < - > MIC Commnication, MIC

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

Page 32 highlights

HP NetServer AA 2-6 • Test 3: Verify Host < - > MIC DMA - Verifies the integrity of the Host-to-MIC PCI interface by accessing DMA, RAM, and runtime registers. Simulated MIC messages are transferred through the MIC and looped back to the host where they are verified for integrity. Failures in this test typically indicate a problem with the DMA engine on the host or MIC adapters. The DMA test completes after approximately one minute. When this test is successful, the following information displays: Starting HostMIC DMA test 456 MIC DMA operations successfully completed 833 MIC DMA operations successfully completed 1220 MIC DMA operations successfully completed 1663 MIC DMA operations successfully completed 2089 MIC DMA operations successfully completed 2390 MIC DMA operations successfully completed MIC DMA test completed If other information displays, a problem has occurred. • Test 4: Verify MIC < - > MIC Commnication - Tests the communication path between MICs and verifies the integrity of all HP AA 4000 components associated with that path. For the test to start, MTCTEST must be running at least one other MIC (minimally, one CE and one IOP). This test runs until it is stopped by manually pressing CTRL-C. Approximately one minute of error-free runtime indicates a fully functional path. The results of this test depend on the components participating in the test. For example, the following is the result (reported on the CE) while running this test between a CE and both IOPs. Starting MICMIC communication test - use Ctrl-C terminate Successful communication with IOP1 & IOP2 MIC (120 messages) Successful communication with IOP1 & IOP2 MIC (231 messages) Successful communication with IOP1 & iop2 MIC (344 messages) If the output does not indicate the communication was successful, a problem occurred. MIC Communication Test Paths With four servers there are six different paths commnications can occur between MICs. However, the MICs ability to function needs to be only tested once per server. The most effective and efficient way to test all MICs for functionality is to run MTCTEST once on CE1 and IOP2 at the same time, stop the test, then run it again on CE2 and IOP1 at the same time. Hewlett-Packard Company

  • 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
HP NetServer AA
Hewlett-Packard Company
2-6
•
Test 3: Verify Host < - > MIC DMA
- Verifies the integrity of
the Host-to-MIC PCI interface by accessing DMA, RAM, and
runtime registers. Simulated MIC messages are transferred
through the MIC and looped back to the host where they are
verified for integrity. Failures in this test typically indicate a
problem with the DMA engine on the host or MIC adapters. The
DMA test completes after approximately one minute. When this
test is successful, the following information displays:
Starting Host<->MIC DMA test
456 MIC DMA operations successfully completed
833 MIC DMA operations successfully completed
1220 MIC DMA operations successfully completed
1663 MIC DMA operations successfully completed
2089 MIC DMA operations successfully completed
2390 MIC DMA operations successfully completed
MIC DMA test completed
If other information displays, a problem has occurred.
•
Test 4: Verify MIC < - > MIC Commnication
- Tests the
communication path between MICs and verifies the integrity of
all HP AA 4000 components associated with that path.
For the
test to start, MTCTEST must be running at least one other MIC
(minimally, one CE and one IOP).
This test runs until it is
stopped by manually pressing CTRL-C.
Approximately one
minute of error-free runtime indicates a fully functional path.
The results of this test depend on the components participating in
the test. For example, the following is the result (reported on the
CE) while running this test between a CE and both IOPs.
Starting MIC<->MIC communication test - use
Ctrl-C terminate
Successful communication with IOP1 & IOP2 MIC
(120 messages)
Successful communication with IOP1 & IOP2 MIC
(231 messages)
Successful communication with IOP1 & iop2 MIC
(344 messages)
If the output does not indicate the communication was
successful, a problem occurred.
MIC Communication Test Paths
With four servers there are six different paths commnications
can occur between MICs.
However, the MICs ability to function
needs to be only tested once per server.
The most effective and
efficient way to test all MICs for functionality is to run
MTCTEST once on CE1 and IOP2 at the same time, stop the
test, then run it again on CE2 and IOP1 at the same time.