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

Other MTC Tools

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

Other MTC Tools Ch 7: Bsic Troubleshooting NOTE If you are monitoring the HP AA array using the Remote Marathon Manager, you only have access to the Marathon Manager and the Windows NT Event Viewer information. Marathon provides other tools with the system which are not necessarily troubleshooting tools, but they can be great for information gathering. MTCEINFO can provide the details of the Ethernet cards and MTCCPYNT can be used to bring back an OS directory, in effect, restore, one that was "saved" by the same utility. • Boot Process - IOP When in doubt about what component is failing, watch the Marathon boot process from POST of the server to the POST of the system, and at the same time, look at what the error logs are recording, and watch the Marathon Manager console. The above slide shows the boot process for the IOPs. Follow it along to make sure each step is getting completed, and if not find the component preventing any of the steps. • MTCTEST If the Marathon Manager were showing a failed Marathon Interface card than it would be the normal reaction to replace the MIC. There could be a problem with the Marathon configuration and the MIC should be further tested. MTCTEST has the ability to test the MIC locally and in tandem with another MIC. This test should be attempted outside of the Marathon array before replacing the card. The test is run from a DOS floppy disk and a second disk would be needed to test against another MIC for communication. Network Server Division 7-3

  • 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 7: Bsic Troubleshooting
Network Server Division
7-3
NOTE
If you are monitoring the HP AA array using the Remote
Marathon Manager, you only have access to the Marathon
Manager and the Windows NT Event Viewer information.
Other MTC Tools
Marathon provides other tools with the system which are not
necessarily troubleshooting tools, but they can be great for
information gathering.
MTCEINFO can provide the details of the
Ethernet cards and MTCCPYNT can be used to bring back an OS
directory, in effect, restore, one that was “saved” by the same utility.
•
Boot Process – IOP
When in doubt about what component is failing, watch the
Marathon boot process from POST of the server to the POST of
the system, and at the same time, look at what the error logs are
recording, and watch the Marathon Manager console.
The above slide shows the boot process for the IOPs.
Follow it
along to make sure each step is getting completed, and if not find
the component preventing any of the steps.
•
MTCTEST
If the Marathon Manager were showing a failed Marathon
Interface card than it would be the normal reaction to replace the
MIC.
There could be a problem with the Marathon
configuration and the MIC should be further tested.
MTCTEST has the ability to test the MIC locally and in tandem
with another MIC.
This test should be attempted outside of the
Marathon array before replacing the card.
The test is run from a
DOS floppy disk and a second disk would be needed to test
against another MIC for communication.