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

Using MTCTEST, Test 1: Reset MIC Adpater, Test 2: Verify Host < - > MIC RAM Access

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 31 highlights

Ch 2: HPAA System Boot Up MICs must be used meaning the MTCTEST must be run on two NetServers simultaneously. NOTE Create two utility diskettes for easier testing. Before running the MTCTEST verify: • All MIC cables and the tuple link cable are securely attached. • The tuple ID LED buttons are correct on each SSDLl. • The SSDL is powered on and all SSDL LEDs are green MTCTEST confirms the following: • The server can identify and access the local MIC registers and RAM spaces over the PCI bus. • DMA operations are working. • A MIC can be located on the PCI bus and it responds to requests. • A MIC can communicate with other MICs also running MTCTEST. • The communication paths (MIC cables and SSDLs) between MIC adapters Using MTCTEST Boot two NetServers with a DOS-bootable floppy containing the MTCTEST. To run the test simply type 'MTCTEST' at the DOS Network Server Division prompt (make sure the DOS context is the correct directory). A menu of different tests will be provided. The tests available perform the following: • Test 1: Reset MIC Adpater - Allows you to repeat the reset sequence. This is usually not necessary because the MIC adapter automatically resets when MTCTEST is started. This option may momentarily cause other instances to fail if running option 4. • Test 2: Verify Host < - > MIC RAM Access - Verifies host access to the MICs memory-mapped RAM space. This standalone test runs for approximately one minute. Use this test if you suspect that the MIC/PCI interface is not operating correctly. 2-5

  • 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
Ch 2: HPAA System Boot Up
Network Server Division
2-5
MICs must be used meaning the MTCTEST must be run on two
NetServers simultaneously.
NOTE
Create two utility diskettes for easier testing.
Before running the MTCTEST verify:
•
All MIC cables and the tuple link cable are securely attached.
•
The tuple ID LED buttons are correct on each SSDLl.
•
The SSDL is powered on and all SSDL LEDs are green
MTCTEST confirms the following:
•
The server can identify and access the local MIC registers and
RAM spaces over the PCI bus.
•
DMA operations are working.
•
A MIC can be located on the PCI bus and it responds to requests.
•
A MIC can communicate with other MICs also running
MTCTEST.
•
The communication paths (MIC cables and SSDLs) between
MIC adapters
Using MTCTEST
Boot two NetServers with a DOS-bootable floppy containing the
MTCTEST.
To run the test simply type ‘MTCTEST’ at the DOS
prompt (make sure the DOS context is the correct directory).
A
menu of different tests will be provided.
The tests available perform the following:
•
Test 1: Reset MIC Adpater
- Allows you to repeat the reset
sequence. This is usually not necessary because the MIC adapter
automatically resets when MTCTEST is started. This option may
momentarily cause other instances to fail if running option 4.
•
Test 2: Verify Host < - > MIC RAM Access
- Verifies host
access to the MICs memory-mapped RAM space. This
standalone test runs for approximately one minute. Use this test
if you suspect that the MIC/PCI interface is not operating
correctly.