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

Using the Marathon Manager Administration window

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

Ch 7: Bsic Troubleshooting connection does not exist. The best assurance of a good connection is the MTCTEST utility running packet transfers between MICs. The two devices participating in the test must be CE and IOP. While the test is being run, these devices cannot be participating members of the array. 2. Using the Marathon Manager Administration window and the Device Status window, note any components that are not active, online or standby. The Marathon Manager can be launched from any device in the array as well as a remotely from a client. However, depending on the state of the array and the device used for viewing, the results may vary. In most cases, examining the array from the view of the CE will offer the best results assuming at least one CE is operational and the array is running. Network Server Division The graphic above shows an array with all devices green. Examine the Component Status window for any devices that are not active/online or standby. Devices that are yellow, white or red indicate potential problems. The exception to this is the SSDLs which are white by default. This screen will, in many cases, point you to the device or devices that are faulted. It is not safe to make changes or take action on the array based off the information on this screen without first examining the NT Event Log for the specific error message. 3. Check and correct any obvious failures (such as loose cables) This often occurs during initial installation or after an array has been moved or a component replaced. The Marathon Manager 7-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 7: Bsic Troubleshooting
Network Server Division
7-5
connection does not exist.
The best assurance of a good
connection is the MTCTEST utility running packet transfers
between MICs.
The two devices participating in the test must be
CE and IOP.
While the test is being run, these devices cannot be
participating members of the array.
2.
Using the Marathon Manager Administration window and
the Device Status window, note any components that are not
active, online or standby.
The Marathon Manager can be launched from any device in the
array as well as a remotely from a client.
However, depending
on the state of the array and the device used for viewing, the
results may vary.
In most cases, examining the array from the view of the CE will
offer the best results assuming at least one CE is operational and
the array is running.
The graphic above shows an array with all devices green.
Examine the Component Status window for any devices that are
not active/online or standby.
Devices that are yellow, white or
red indicate potential problems.
The exception to this is the
SSDLs which are white by default.
This screen will, in many cases, point you to the device or
devices that are faulted.
It is not safe to make changes or take
action on the array based off the information on this screen
without first examining the NT Event Log for the specific error
message.
3.
Check and correct any obvious failures (such as loose cables)
This often occurs during initial installation or after an array has
been moved or a component replaced.
The Marathon Manager