Dell Unity 300 EMC Unity-SC-Isilon-ME4 Uptime Bulletin for Q4 2021
Dell Unity 300 Manual
 |
View all Dell Unity 300 manuals
Add to My Manuals
Save this manual to your list of manuals |
Dell Unity 300 manual content summary:
- Dell Unity 300 | EMC Unity-SC-Isilon-ME4 Uptime Bulletin for Q4 2021 - Page 1
tries to query the vVol nothing is returned to vCenter. This issue is resolved in Unity OE 5.1.2.x. Alternatively, a ticket may be opened with support referencing the KB noted above, and support can manually modify the vVols to make them visible. IMPORTANT NOTE: This only affects vVols that were - Dell Unity 300 | EMC Unity-SC-Isilon-ME4 Uptime Bulletin for Q4 2021 - Page 2
KB 191159 describes a second "out of inodes" condition where an NDU to Unity OE 5.1.0 or 5.1.1 could get stuck at 59% completed if an internally cause excessive log file creation. Support has been proactively reviewing customer systems that are SRS enabled and manually cleaning up systems found to - Dell Unity 300 | EMC Unity-SC-Isilon-ME4 Uptime Bulletin for Q4 2021 - Page 3
"adoption rates" in http://support.emc.com for current Dell EMC Unity/SC/Isilon target code adoption rates. Dell EMC UNITY OE VERSION RELEASE DATE STATUS vvols after an upgrade to 5.1.0 or 5.1.1. • Resolves an problem introduced in 5.1.0 and 5.1.1 where old performance archive files were not - Dell Unity 300 | EMC Unity-SC-Isilon-ME4 Uptime Bulletin for Q4 2021 - Page 4
Webhooks content by navigating to Admin > Integrations. PowerSwitch Support We've added support for PowerSwitch. You can now view detailed information in CloudIQ and be notified about risks in your environment via health score, or troubleshoot using our built-in analytics. You must configure the
-
1 -
2 -
3 -
4
 |
 |
You can always access the
latest
Uptime Bulletin
here:
h°ps://dl.dell.com/content/
docu99193
WE
’
D LIKE YOUR FEEDBACK
ABOUT THE UPTIME
BULLETIN. SEND US YOUR
IDEAS FOR FUTURE TOPICS
AT :
Unity Customer
Documentation
h°ps://www.dell.com/support/
home/en
-
us/product
-
support/
product/unity
-
all
-
flash
-
family/docs
Unity Ethernet port
speed or MTU
speed of ports may
change after up-
grade to 5.1
1
Can
’
t see VVols
after upgrade to 5.1
1
Performance ar-
chives not properly
removed in 5.1 with
CloudIQ enabled
2
Don
’
t remove hosts
from host groups in
Unity OE 5.1
2
Inode related up-
grade issues with
5.1.0 and/or 5.1.1
Did you know?
2
Apache Log4j re-
sponse
2
Latest code
releases and
targets.
3
CloudIQ update.
4
UPTIME BULLETIN
A Newsletter from CEE, a Division of Dell EMC
For Unity/SC/isilon/ME4
Q4
VOLUME 39
December,
2021
Ethernet port speed and MTU size of physical inter-
face may change on Unity after upgrade to 5.1
Two Lightning knowledge base articles have been written to cover two different scenarios seen
where either the Ethernet port speed changes to 10g after a Unity OE code upgrade to 5.1, or
the Unity MTU size of physical ports involved in a link aggregation may revert to a default value
after a Unity OE code upgrade to 5.1.
The first issue where the Ethernet port speed may change is detailed in KB
193444
.
This issue may occur if the Ethernet card has only 1 single speed value (10g).
Prior to Unity OE
5.1, Unisphere would show
“10
g
”
and
“
Auto
”
as available settings for such cards.
This change
has no effect on the way the card or the interface will behave.
The second issue where the MTU size of physical ports involved in link aggregation may
change is detailed in an KB viewable only by Dell and partners.
This issue may occur if the port
speed is set to
“
auto
”
after the Unity has been upgraded to OE 5.1.
If you are running OE 5.1
and you wish to set the port speed involved in link aggregation to
“
auto
”,
or if you have already
done so and are experiencing DU as a result, please open a ticket with Dell EMC technical sup-
port for guidance, and refer to internal KB 193445.
Administrators may be unable to browse pre
-
existing
vVols in the datastore from vCenter after upgrading
storage system to 5.1
KB
193020
describes an issue whereby existing vVols may no longer be visible to the adminis-
trator in vCenter after upgrading a Unity storage system to OE version 5.1.0 or 5.1.1. After up-
grading Unity OE to 5.1.0 or 5.1.1, vCenter will show an existing vVol as having no VM objects
when trying to browse it. The VMs are online, however, and running without issue. Using ssh to
log into of one of the ESX servers attached to the vVol on Unity as root will also show zero VM
objects.
The cause of this issue is due to a new vVol Native snapshot feature added to OE 5.1.0 Unity
code. The feature allows Unity to identify if the vVol is a native snapshot or not.
A new field is
added internally to the Unity storage database which has recorded an invalid value during the
upgrade. When ESX tries to query the vVol nothing is returned to vCenter.
This issue is resolved in Unity OE 5.1.2.x.
Alternatively, a ticket may be opened with support
referencing the KB noted above, and support can manually modify the vVols to make them visi-
ble.
IMPORTANT NOTE: This only affects vVols that were created on the Unity prior to the OE up-
grade. Any new vVols created after the Unity is at 5.1.0 will not be impacted as they will have
the correct field needed.