Release 2.0.1.0 Resolutions - Dell PowerVault Storage Area Network Release Note

Release 2.0.1.0 Resolutions

The following table lists the issue, description, and the solution or workarounds for the DR4000/DR4100 system 2.0.1.0
release.
Error Issue
Code
16083 Unit comes up in an error
state due to additional PS
sensors that are discovered
with newer iDRAC FW.
15795 There is no message
instructing user to upgrade
the Client OST plugin when
DR4X00 FW is upgraded.
15695 GUI "Usage" page doesn't
show any stats graphs in a
special case.
15275 Windows OST plug-in install
fails on a DC.
15067 Handle the '.' as part of the
NETBIOS name.
14959 System didn't come to
operational state after
upgrade due hardware
monitor failing to start.
14957 Support bundles can be
large. We need to support
options to gather more
specific info in these special
situations.
12
Description
DR4100 unit may come up in an error state
due to an issue with the total number of
power supply sensors being detected.
This was caused by a new version of the
iDRAC FW which discovered additional
sensors.
Added messaging to the UI so that during
the upgrade the user is told to also
upgrade the OST plugin if OST is being
used.
If the client machine and the DR are not in
the same timezone, then the usage
graphs may not show the stats for some
period.
Installing the OST plug-in on a DC fails.
Domain join to the AD domain controller is
ok but access to DR4000 share fails.
Handle/allow '.' in NETBIOS name.
Access from windows client using
test.com\administrator.
smb.conf: workgroup =
TEST.COM realm = ad.test.com
administrator@swsys-84 >
authenticate --show Domain:
ad.test.com Login group:
test.com\domain users
administrator@swsys-84 >
Intermittently after an upgrade the unit
does not come into an operational state
and remained in maintenance mode.
Add following new options for diagnostics
collection.
• --logs — Collect only logs and
system configuration.
• —cores —Collect only cores
• --auto_diags <#> —
Collect only specified number of
previous auto diagnostics.
Workaround/Solution
Corrected the issue in the
Hardware Monitor code.
Added messaging to inform the
user to upgrade the plug also.
We now use the timezone of the
server rather than the client
running the browser.
The code now supports this option.
Corrected the code path to allow '.'
for domain login groups.
Added code to check the status of
the SNMPD before starting the
hardware monitor which resolves
this issue.
diagnostics --help collect
Usage:
diagnostics --collect
[--name <name>]
[--reason <reason>]
[--force] [--dset]