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

Analyzing an Event

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

HP NetServer AA will show a link down and in many cases a quick check of the cable connector may solve the problem. The Marathon cables are heavy and if not properly tightened can come loose to a degree that will cause a fault. 4. If the CE is active, check the Windows NT Event Viewer for Marathon caution or critical messages. Check the IOPs for the error messages, each IOP will vary from the other IOP. It is absolutely critical this tool be used to diagnose problems with the array. Personnel performing troubleshooting on the Marathon Array sometimes approach the array with the idea that they are troubleshooting Windows NT. In most cases this will result in a lot of wasted time and in extreme cases a downed array. The event log contains error messages for almost every fault situation the Marathon array is liable to encounter. 5. Use the Marathon documentation to look up the event. The Marathon User Guide containing descriptions of all events is available in printed or online versions. The online version can be installed on one of the servers in the array or on a client. Use this documentation to locate the specific error message from the Event viewer. Analyzing an Event Events are reported by different Marathon subsystems depending on the fault. Reporting Source MtcKMR MtcDgs MtcDsl The following table lists the Reporting source within Marathon, the prefix that will be listed in the event and the area this reporting source deals with. Event Prefix Reports on ..... None IOPn.MtcDgs status IOPn.MtcDsl status These events are keyboard and mouse events and are only logged in the event viewer of the CE. Events in this category pertain to the CE ability to acquire use of the redirected keyboard and mouse. Critical errors in the area point to corrupted registry settings and problems with CE memory. Events with this prefix most often point to errors in the bindings of the Datagram service to the NICs. A corrupted or unsupported LAN adapter driver could also cause error messages here. Device Synchronization Layer events occur because of errors in the Endurance 4000 software or intermittent hardware errors. In many cases, rebooting the IOP and allowing it to rejoin the array will clear the error. In the case of intermittent hardware errors on the IOP other HP tools may need to be used to diagnose the 7-6 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
7-6
will show a link down and in many cases a quick check of the
cable connector may solve the problem.
The Marathon cables are heavy and if not properly tightened can
come loose to a degree that will cause a fault.
4.
If the CE is active, check the Windows NT Event Viewer for
Marathon caution or critical messages.
Check the IOPs for
the error messages, each IOP will vary from the other IOP.
It is absolutely critical this tool be used to diagnose problems
with the array.
Personnel performing troubleshooting on the
Marathon Array sometimes approach the array with the idea that
they are troubleshooting Windows NT.
In most cases this will
result in a lot of wasted time and in extreme cases a downed
array.
The event log contains error messages for almost every fault
situation the Marathon array is liable to encounter.
5.
Use the Marathon documentation to look up the event.
The Marathon User Guide containing descriptions of all events is
available in printed or online versions.
The online version can
be installed on one of the servers in the array or on a client.
Use this documentation to locate the specific error message from
the Event viewer.
Analyzing an Event
Events are reported by different Marathon subsystems depending on
the fault.
The following table lists the Reporting source within Marathon, the
prefix that will be listed in the event and the area this reporting
source deals with.
Reporting
Source
Event Prefix
Reports on …..
MtcKMR
None
These events are keyboard and mouse events and
are only logged in the event viewer of the CE.
Events in this category pertain to the CE ability to
acquire use of the redirected keyboard and mouse.
Critical errors in the area point to corrupted
registry settings and problems with CE memory.
MtcDgs
IOPn.MtcDgs status
Events with this prefix most often point to errors
in the bindings of the Datagram service to the
NICs.
A corrupted or unsupported LAN adapter
driver could also cause error messages here.
MtcDsl
IOPn.
MtcDsl
status
Device Synchronization Layer events occur
because of errors in the Endurance 4000 software
or intermittent hardware errors.
In many cases,
rebooting the IOP and allowing it to rejoin the
array will clear the error.
In the case of
intermittent hardware errors on the IOP other HP
tools may need to be used to diagnose the