Intel AFCSASRISER User Guide - Page 105

RAID Web Console 2 Client connected to a, RAID Web Console 2 framework mode.

Get Intel AFCSASRISER PDF manuals and user guides View all Intel AFCSASRISER manuals
Add to My Manuals
Save this manual to your list of manuals

Page 105 highlights

Access control is not supported. There is no support for full view or view only access modes. It is always full view access, and multiple clients can have full view access at the same time on the same server 3. Event Logging: Full functionality support is available for the VMware ESXi operating system, but it works differently than the normal Intel® RAID Web Console 2 framework mode. The event logging feature for the Intel® RAID Web Console 2 Client connected to a VMware ESXi system behaves as follows: - There is no support for retrieving initial logs (the events that occurred before a client logs in). Only those events that occur after a client logs in appear in the event logger dialog. - System log does not display. - The "Save log" feature is not supported; however, the "Save Log as Text" is still supported. - The "View Log" option allows you to view the logs saved in a text file on the event logger dialog. - The event descriptions might not be identical to a normal Intel® RAID Web Console 2 Client because the descriptions come from the firmware through the provider. - There is no filtering of events, unlike Monitor Service. - Refreshing of the Intel® RAID Web Console 2 GUI after any updates on the firmware is slower for a client connected to VMWare ESXi hosts, compared to one connected to Windows/Linux/Solaris hosts. 4. Remote discovery and heartbeat mechanism: For networks that do not have DNS configured, the "hosts" file in the machine on which the Intel® RAID Web Console 2 is installed must be edited as follows: - Add an entry to map the VMWare host's IP address with the hostname. This is for the discovery to happen correctly. In the absence of this entry, the VMWare host would be discovered as 0.0.0.0. - Add an entry to map its own IP address (not the loop back address) with the Hostname. This is to ensure that the Alert Event Notifications (AENs) are delivered correctly. For networks that has DNS configured, the "hosts" file in the machine on which Intel® RAID Web Console 2 is installed must be edited as follows: - When you do the initial configurations for the VMWare host, provide the correct DNS server IP address. - In the hosts file of the machine on which Intel® RAID Web Console 2 is installed, add an entry to map its own IP address (not the loop back address) with the Hostname. This is to ensure that the Asynchronous Event Notifications (AENs) are delivered correctly. 5. The VMWare hosts are discovered only when the Framework service starts on the host where Intel® RAID Web Console 2 is installed. 6. The VMWare ESX3i does not support the heartbeat mechanism to let Intel® RAID Web Console 2 know whether VMWare ESX3i is still connected. When the connection to the remote VMWare ESX3i is lost, Intel® RAID Web Console 2 does not indicate this. The only option is to rediscover by restarting the Intel® RAID Web Console 2 framework. Intel® RAID Software User's Guide 93

  • 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
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
Intel
®
RAID Software User’s Guide
93
Access control is not supported. There is no support for full view or view only access
modes. It is always full view access, and multiple clients can have full view access at
the same time on the same server
3.
Event Logging:
Full functionality support is available for the VMware ESXi operating system, but it
works differently than the normal Intel
®
RAID Web Console 2 framework mode. The
event logging feature for the Intel
®
RAID Web Console 2 Client connected to a
VMware ESXi system behaves as follows:
—
There is no support for retrieving initial logs (the events that occurred before a client
logs in). Only those events that occur after a client logs in appear in the event logger
dialog.
—
System log does not display.
—
The "Save log" feature is not supported; however, the "Save Log as Text" is still
supported.
—
The "View Log" option allows you to view the logs saved in a text file on the event
logger dialog.
—
The event descriptions might not be identical to a normal Intel
®
RAID Web Console
2 Client because the descriptions come from the firmware through the provider.
—
There is no filtering of events, unlike Monitor Service.
—
Refreshing of the Intel
®
RAID Web Console 2 GUI after any updates on the
firmware is slower for a client connected to VMWare ESXi hosts, compared to one
connected to Windows/Linux/Solaris hosts.
4.
Remote discovery and heartbeat mechanism:
For networks that do not have DNS configured, the "hosts" file in the machine on which
the Intel
®
RAID Web Console 2 is installed must be edited as follows:
—
Add an entry to map the VMWare host's IP address with the hostname. This is for
the discovery to happen correctly. In the absence of this entry, the VMWare host
would be discovered as 0.0.0.0.
—
Add an entry to map its own IP address (not the loop back address) with the
Hostname. This is to ensure that the Alert Event Notifications (AENs) are delivered
correctly.
For networks that has DNS configured, the "hosts" file in the machine on which Intel
®
RAID Web Console 2 is installed must be edited as follows:
—
When you do the initial configurations for the VMWare host, provide the correct
DNS server IP address.
—
In the hosts file of the machine on which Intel
®
RAID Web Console 2 is installed,
add an entry to map its own IP address (not the loop back address) with the
Hostname. This is to ensure that the Asynchronous Event Notifications (AENs) are
delivered correctly.
5.
The VMWare hosts are discovered only when the Framework service starts on the host
where Intel
®
RAID Web Console 2 is installed.
6.
The VMWare ESX3i does not support the heartbeat mechanism to let Intel
®
RAID Web
Console 2 know whether VMWare ESX3i is still connected. When the connection to the
remote VMWare ESX3i is lost, Intel
®
RAID Web Console 2 does not indicate this. The
only option is to rediscover by restarting the Intel
®
RAID Web Console 2 framework.