EMC VNXe3200 Release Notes

Transcription

RELEASE NOTES
EMC VNXe3200
Operating Environment 3.1.1.5395470
Release Notes
302-000-195
Rev 06
May 2015
This document contains information on these topics:
Product description ................................................................................... 2
New features and changes ......................................................................... 2
Fixed problems
..................................................................................... 8
Known problems and limitations ................................................................ 15
Technical notes
..................................................................................... 24
Documentation
..................................................................................... 25
Software, media, organization, and files ..................................................... 25
Installation
..................................................................................... 25
Troubleshooting and getting help ............................................................... 25
Product description
Product description
EMC® VNXe3200® is a simple, yet powerful hybrid-storage system that delivers
enterprise-class reliability and data availability. It provides a solution that is easy to
install, manage, service, and support. The enterprise-level features include Unified
Snapshots, Multicore Cache, Multicore RAID, FAST Cache, FAST VP, and many other
provisioning and monitoring features that support a wide range of workloads such as
databases, files, and virtual machines. Along with enhanced native iSCSI protocol
support, the VNXe3200 also supports Fibre Channel (FC) protocol, and expanded IPv6
functionality. The VNXe3200 delivers up to 3 times the performance of a VNXe3150
system.
The VNXe3200 Disk Processor Enclosure (DPE) contains two Storage Processors in the
2U rack mount form factor:
•
25-drive DPEs paired with 2.5" disks.
•
12-drive DPEs paired with 3.5" disks.
Each storage processor features an Intel Xeon Quad Core 2.2-GHz processor, 24 Gb of
internal memory (DIMM), two integrated 6-Gb/s mini-SAS HD ports, four integrated
10-GbE iSCSI Base-T ports, and one slot for an optional I/O module. Similar to the
existing models, VNXe3200 also supports hot swappable 2.5"/3.5" SAS and NL-SAS
rotating disks, and 2.5" Flash disks in the DPE and optional 12-disk or 25-disk Disk
Array Enclosures (DAEs). The VNXe3200 also supports NFS, CIFS, iSCSI through the
embedded I/O ports, and FC protocols through optional I/O modules.
Note: VNXe Operating Environment (OE) Version 3.1 is only supported on the
VNXe3200. Do not use the OE Version 3.1 on the VNXe3100, VNXe3150, or
VNXe3300.
New features and changes
This document contains the following new features and changes:
Upgrade enhancements
Although VNXe OE Version 3.1.1.5395470 is identical to the previously released
VNXe OE Versions 3.1.1.5134075, 3.1.1.4993502, and 3.1.1.4823793, this version
contains additional enhancements that make the upgrade process more reliable. It
also includes a new driver firmware that improves future firmware upgrade processes.
Multiprotocol file access
The multiprotocol feature lets you create and manage multiprotocol NAS servers and
file systems that support file sharing by users in Windows and UNIX environments.
UNIX users can access the file system data using NFS, and Windows users can access
the same file system data using CIFS.
This release contains the following multiprotocol-related enhancements:
•
2 VNXe3200 Release Notes
Ability to map UNIX user accounts to Windows user accounts. The system
automatically maps a Windows user to a UNIX user when the same user name
is defined in the Unix Directory Service (UDS) and Windows Active Directory
(AD). If the user names are different, you can modify and upload an ntxmap
configuration file template to create a custom mapping between them. This
mapping can contain wildcards and substitution sequences. To allow users
with unmapped user names to access a multiprotocol NAS server's file
systems, you can create default UNIX and Windows users on the NAS server.
•
Ability to use LDAP or NIS as a Unix Directory Service to map users, retrieve
netgroups, and build UNIX credentials.
•
Unified file-level security policy management for multiprotocol access,
including support for NFS credentials with more than16 groups. When you
configure a multiprotocol file system, you can choose the type of access
policy to use for that file system:

Unix Security, which uses the UNIX credential associated with the host
request to check mode bits.

Windows Security, which uses the Windows credential associated with the
host request to check the CIFS Access Control List(ACL)

Native, which uses the protocol's security (ACLs for CIFS and mode bits for
NFS) to manage host access to shared data.
Note: When you upgrade an older VNXe system, all file systems will retain their
current type (CIFS or NFS), and existing NAS servers will have multiprotocolmode disabled. Also, once you enable a NAS server for multiprotocol access,
you cannot disable it.
Data protection enhancements
This release contains the following data protection enhancements:
•
Native asynchronous replication support for LUNs, LUN groups, and VMware
VMFS datastores
•
Replication support for block-based storage resources using RecoverPoint
•
Snapshot of snapshots for 32-bit VMware NFS datastores
Native asynchronous replication support for block-based storage resources
VNXe now supports asynchronous replication for block-based storage resources
(LUNs, LUN groups, and VMware VMFS datastores). Both Unisphere and the CLI have
been updated to provide interfaces for the easy configuration and management of
replication sessions on storage resources. This feature leverages crash consistent
replicas to provide remote data protection of storage resources. It relies on the
Unified Snapshot technology, and provides a cost-effective and easy solution without
any dependency on additional software.
Replication support for block-based storage resources using RecoverPoint
In addition to the native asynchronous replication support, VNXe now also supports
replication for block-based storage resources using EMC RecoverPoint 4.1.1.
RecoverPoint brings you continuous data protection and continuous remote
replication for on-demand protection and recovery at any point in time. This remote
replication technology can run on a physical appliance (RPA) or a virtual appliance
VNXe3200 Release Notes
3
(vRPA). Both synchronous and asynchronous replication modes are supported.
RecoverPoint can also be used to replicate block-based storage resources between
VNXe3200 and VNX systems.
Snapshot of snapshots for 32-bit VMware NFS datastores
32-bit VMware NFS datastores, created after upgrading to this release, now
automatically include support for second-level snapshots at the file level. Using
VMware vStorage APIs for Array Integration (VAAI), you can create a fast clone of a
previously created fast clone at the virtual machine level. 64-bit VMware NFS
datastores also support second-level snapshots.
NAS server enhancements
This release contains the following NAS server enhancements:
•
Ability to create up to 10 IP interfaces per NAS server
•
IPv4 and IPv6 preferred interfaces to be used for general outbound traffic
initiated by the NAS server
•
Ability to create a NAS server that supports multiprotocol file system access.
Ability to create up to 10 IP interfaces per NAS server
In this release, you can create up to 10 IP interfaces per NAS server using IPv4, IPv6,
or both. This provides the ability to expose one NAS server to different IP subnets that
can be used for testing or other purposes. It also enables SMB 3.0 Multichannel
support for CIFS.
Preferred interfaces
When you create IP interfaces for a NAS server, the first IPv4 interface and first IPv6
interface configured with a gateway become preferred interfaces. The NAS server uses
the preferred interface gateways for outgoing communication with non-locally
connected hosts. For example, the NAS server forwards DNS and Active Directory
requests through a preferred interface and uses the same IP address as a source
address of the packets.
Note: Locally connected hosts, which are attached to the same subnets as the NAS
server interfaces, are accessed through corresponding interfaces directly, and
not through the preferred interface gateways.
When a NAS server initiates outbound traffic, it compiles a list of all the available
network interfaces on the proper subnet and performs one of the following actions:
•
If a preferred interface is in the compiled list, the NAS server chooses the
preferred interface.
•
If a preferred interface is not in the compiled list, the NAS server chooses a
network interface at random.
SMI-S enhancements
This release contains the following Storage Management Initiative Specification
(SMI-S) enhancements:
•
Integration with Microsoft System Center Virtual Machine Manager (SCVMM)
next generation.
•
Support for the profiles defined in SMI-S standard v1.6.0.4.
For more information about SMI-S, see the SMI-S Provider Programmer's Guide for
VNXe.
Integration with Microsoft SCVMM next generation
You can now use the SMI-S API to set up local and remote LUN mirroring, which
allows the system to integrate with Microsoft SCVMM 2012 R2 to support the Azure
Site Recovery Service. In addition, this release allows you to use the SMI-S API to
configure LUN storage tiering, expose access point information, and list and monitor
fan and power supply health.
Support for profiles defined in the SMI-S standard v1.6.0.4
This release supports the following new profiles and subprofile defined in SMI-S
standard v1.6.0.4:
•
Access Points Subprofile
•
Automated Storage Tiering Profile
•
Fan Profile
•
Power Supply Profile
•
Replication Services Profile (mirror part)
Storage efficiency enhancements
This release contains the following storage efficiency enhancements:
•
64-bit format for VMware NFS datastores
•
Shrink and space reclaim for 64-bit VMware NFS datastores
•
Fast clones for 64-bit VMware NFS datastores
•
Support for 400 GB FAST Cache
64-bit format for VMware NFS datastores
You can now create and manage 64-bit VMware NFS datastores, also known as
UFS64. UFS64 provides a number of benefits over existing 32-bit datastores (UFS32),
including:
•
Increased scalability
•
Improved resiliency/recoverability
•
Improved availability
•
Enhanced storage efficiency
5
To learn more about performance expectations, refer to the VNXe3200 Best Practices
for Performance white paper for VNXe Operating Environment Version 3.1.1.
Shrink and space reclaim for 64-bit VMware NFS datastores
You can now shrink the size of a 64-bit VMware NFS datastore (UFS64) without
affecting its accessibility. The shrink operation reduces the space the datastore uses
from the storage pool, which allows the storage pool to reclaim space. With thinprovisioned VMware NFS UFS64 datastores, you can shrink into the allocated size.
Fast clones for 64-bit VMware NFS datastores
For virtual machines using the 64-bit VMware NFS datastores, you can now create at
least 1024 fast clones. Each fast clone can have up to 256 snapshots.
Support for 400 GB FAST Cache
If you have a FAST Cache license and have the necessary SAS FLASH disks available,
you can now configure the FAST Cache to use up to 400 GB of space. This enables to
you get a better performance from the FAST Cache in your environment. The FAST
Cache is configured in RAID 1 pairs, and you can have various disk configuration
options. For more information on the disk configuration options, see the Unisphere
Online Help.
User experience enhancements
This release contains the following user experience enhancements:
•
Ability to display pool consumption information for all allocated resources in
a storage pool
•
Support for single sign-on from Unisphere Central or another VNXe Unisphere
instance
•
Display of warning-level messages in the Pre-upgrade Health Check. These
flag system issues that you may need to check or correct before proceeding
with an upgrade.
•
Enhanced progress bar for software upgrades that more accurately reflects
the upgrade status.
•
User-friendly object name support
Display pool consumption data for all allocated resources in a storage pool
You can now display and export pool consumption data for all allocated resources in
a storage pool by using the new Storage resources tab of the pool's details page. This
tab displays the following information about the resources (NAS servers, LUN groups,
LUNs, file systems, and VMware datastores) allocated to a pool:
•
Snapshot size, which is the total amount of pool space allocated for the
snapshots of the storage resource.
•
Total pool size used, which is the total amount of pool space allocated for the
storage resource, including its primary data, snapshot data, and metadata.
Having this type of data in one place can help you more effectively manage storage
pools. For example, you can use this data to narrow down the cause of pool
degradation, take measures if the pool is running out of space, and view pool
resources before-purposing a pool.
Single sign-on from Unisphere Central or another VNXe Unisphere instance
This release supports Single Sign-On (SSO) VNXe authentication from the Unisphere
Central GUI and the GUI of another VNXe system. With SSO, you can:
•
Log into the Unisphere Central GUI and launch one or more Unisphere GUIs for
VNXe systems without re-authenticating.
•
Log into a VNXe GUI, open another browser window, and launch another VNXe
system by entering the URL for that system. (You do not have to reauthenticate to open the second VNXe system.)
For information about setting up single sign-on support, see the VNXe Security
Configuration Guide.
User-friendly object name support
You can now use the name to retrieve and display historical and real-time
performance metrics for a LUN, file system, disk, pool, Ethernet port, iSCSI, and FC
objects when you issue the VNXe Unisphere CLI metrics command. Provide the userfriendly object name as the unique object identifier in the –path object qualifier of
the /metrics/value/hist and /metrics/value/rt commands.
Other enhancements
This release contains the following other enhancements:
•
Serviceability enhancements
•
Hardware enhancements
•
SLES11 Refresh
Serviceability enhancements
• Audit logs are now created for all service related actions. Some of the existing
audit log entries have also been enhanced for a better user experience.
•
You can now include customer contact information with ConnectEMC dial
home messages. This helps ensure that EMC Support has the most accurate
information for contacting you in response to an issue.
Hardware enhancements
• The storage system now supports the use of DC power supply.
•
The following I/O modules are now supported:

4 port 1Gbps iSCSI front end 10GBaseT (copper) - This interface can
negotiate to 10Mbps, 100Mbps, or 1000 Mbps.

4 port 10Gbps iSCSI front end optical - This interface is a hardware/driver
bundle that provides optical support connectivity through 10GbE SFP or
Active and Passive Twin-Ax cables.
Both modules support 256 initiators per port. They support a maximum of 8 VLANs
per port.
7
Fixed problems
SLES11 Refresh
This refresh ensures the system remains current with the latest OS distribution,
makes best use of the SUSE, and receives the latest security updates. Pacemaker is
the High Availability (HA) component from SUSE with updates to match the SUSE
distribution.
Fixed problems
This release contains the following fixed issues:
Priority
Symptom Description
Fix Summary
Tracking
Number
P01
The system rebooted with the following
stack:
The issue was fixed in the code.
622806
handle_fault+0x1d
_ZN9rodLayout9sendBreakEjyy+0x12f
4File_LocksData26checkConflictWith
RangeLoc
N14File_LocksData13checkConflictER
14lockCred
P01
A panic occurs during a rename with
symbolic link.
625384
P01
An outage occurs due to Block CIFS
threads because the CAVA server does
not answer to a scan request but still
answers to the heartbeat.
A parameter was added to the code
that sets a timeout for MSRPC scan
requests to 5 minutes.
625755
P01
When the CAVA signature changed, a free
page is not available with VirusChecker
and scan on read is enabled. If the high
water mark is reached, the caller thread is
blocked.
The code has been fixed to use an
open file with “scan on read”
enabled to start the scan.
625759/
59556484
P01
The system stopped sending the client IP
in some events.
The code has been fixed to add the
client IP to all system events.
625762
P01
The system and file server rebooted when
the Continuous Availability of the SMB3
protocol was implemented.
The Continuous Availability service
has been fixed to restore SMB3
persistent state accordingly.
626466/
58673698
P01
A race condition between the I/O
operation and the file deletion caused a
file service thread deadlock.
The issue was fixed in the CFS lock
manager in the critical code path.
626480/
58596446
P01
With unmodified data and the parameter
cifs.windowsTimeUpdate set, the
modification time of a file is updated
after a rename or a setSD.
The modification time is unchanged
after a rename or a setSD.
626495/
58605798
Fixed problems
Priority
Symptom Description
Fix Summary
Tracking
Number
P01
NFS mount is unresponsive. After a while,
the system rebooted with all the mount
threads blocked.
The conditions that triggered this
issue are fixed.
626497/
59135856
P01
The system can reboot when accessing
the NFSv4 client table and the NFSv4
service has stopped.
626503/
61114502
P01
The NAS server experienced an NFS
security issue.
The NFS security issue has been
fixed.
626504/
61102304
P01
Unable to set/unset offline DOS attribute
bit independently of DHSM.
This issue has now been fixed.
628477/
57894086
P01
When running the nas_fs translate Control Station command to
convert a file system access policy from
UNIX or secure to mixed, the system
rebooted.
628711/
628714/
628713
P01
The system rebooted with Hyper-V and an
error appeared.
631620
P01
The system rebooted because there was
not a free page.
634570/
49662840
P01
The system can reboot in NIS code while
the default domain is removed.
The code has been updated to
harden NIS code to ensure the NIS
objects are always valid before using
them.
639848/
52090850
P01
Users cannot delete a LUN group with
snapshots in one operation.
Delete all snapshots and then delete
the LUN group.
640616
P01
A “SPN mismatch” warning message did
not display when:
Updated the SPN mismatch code to
detect a mismatch between the host
name and the domain name.
641623/
•
A Kerberos system used a Fully
Qualified Domain Name (FQDN)
•
The host name and the CIFS server
had the same name
•
The domain name was different
11111111
P01
If using an SMB2 client for NAS access,
and an SP on the VNXe rebooted, the
client can stop responding before
recognizing that the VNXe has failed over.
Use a more modern client with
SMB3.
646014
P01
String buffer size is not set to right length
and caused an overwrite and reboot.
648895/
62007318
9
Fixed problems
Priority
Symptom Description
Fix Summary
Tracking
Number
P01
The LUN names must be unique across
the system. You can only create 100 LUNs
for the given LUN name. If there are no
free LUN names in the range, the GUI
mistakenly accepts the empty strings ""
as the names and sends them to the
backend for validation. The backend
responds with an error.
649175
P01
An error message appeared when
creating a snapshot of a file system, LUN,
or LUN Group object with the GUI, or
using the "/prot/snap", "/prot/snap/nfs"
or "/prot/snap/cifs" UEM CLI commands.
This issue was fixed in the code.
651348
P01
The NAS server crashed when setting a
NFSV4 ACL on a file with no Security
Descriptor.
The conditions which triggered the
crash have been fixed.
652510/
62789772
P01
The system reboots when mounting a file
system and trying to convert the UNIX
mount path into Unicode.
The code has been updated to set a
pointer to the shadow directory to
null.
654480/
63917158
P01
A corrupted SMB request contained a
length field larger than the remaining
data in the request. A data conversion
issue caused the boundary check to
overflow and a very large memory
allocation failed, causing the NAS server
to reboot.
The data conversion issue was fixed.
670574/
59848028
P01
A Service Principal Name (SPN) was
specified with an incorrect format. The
'empty' service name field caused a NAS
server to reboot.
The format of the SPN confirmed both
a service name and a host name are
included. An error appeared if the
SPN is not the correct format.
670859/
60584052
P01
An issue with error handling during NFS
request processing prevented memory
from being freed correctly, which lead to
the out of memory condition.
This issue has been resolved by
properly releasing the memory.
670892
P01
The thin file system is fully extended after
a system reboot (for example, after
upgrade) and the deduplication scan
failed due to the low high water mark
(hwm).
The assumption for size of the UFS32
mount string is incorrect under some
condition. It could cause the ufs32
mount string to be truncated. In this
case the hwm=75 is truncated to
hwm=7, which is not expected. The
code has been fixed to have enough
buffer for max possible length.
690807
P01
In some cases, an error may occur when
users try populating a thin-provisioned
file system. This may have occurred
because of an issue with the automatic
extend feature.
This issue has been fixed in the
code.
713438/
69843634
Fixed problems
Priority
Symptom Description
Fix Summary
Tracking
Number
P01
Modifying access permissions on any ESX
host in Unisphere resulted in the
datastore getting unmounted from all
other ESX hosts.
code.
719122/
69825372
P02
The replication destination appears as
the destination choice of another
replication session.
This transient issue resolves after the
internal poll on a remote system is
complete.
462661
After using Unisphere to create a
replication session between the source
object A on system ABC to destination
object B on system DEF, attempts to
create another session from source
object C on system ABC to an object on
system DEF will show the recommended
destination objects list of the already inuse destination object B as a possible
destination choice.
This leads to confusion as B on system
DEF is already part of a replication
session.
P02
CAVA sends incorrect notifications with
null as the file owner.
The code has been updated to obtain
the SID before releasing the
file_namingnode.
625751/
56617316
P02
The 'Null owner SID' in some CEPP events
Owner SID does not set in some CEPP
XML requests.
When attempting to open a file or a
directory to which you do not have
rights because the file_namingnode
is not present, you cannot obtain the
SID file/dir.
625752
The code has been update to retrieve
the SID before freeing the
file_namingnode.
When open or mkdir failed, send preevent with the fnn if possible in order
to get the ' owner SID ' of the
file/directory.
P02
Rename with SMB2/SMB3 does not
trigger a VirusChecker scan.
The code has been updated to check
if the file has been renamed using
set file info rename.
625757
P02
When renaming with SMB2/SMB3, there
is no trigger for the virus checker scan.
The code has been updated to
ensure that the file has been
renamed using the set file info
rename.
625758/
59402998
VNXe3200 Release Notes 11
Fixed problems
Priority
Symptom Description
Fix Summary
Tracking
Number
P02
When enumerating open sessions or
open files on a CIFS server that belonged
to a system with many servers, the
reports can include information that
belonged to other CIFS servers.
Ensure the information is related to
the audited CIFS server.
626183/
60397558
P02
CIFS clients cannot access a file on an
EMC Share for a lock conflict reason. The
file system unmounted or freeze
operation stopped responding.
The lock manager is fixed to properly
handle a race condition so that no
range lock object is left on the file.
626478/
59688542
P02
Error messages appeared frequently in
the server log.
This code has been fixed to properly
handle multiple sessions from a
single CIFS client.
626483/
59361952
P02
When the user mapping service has not
started or not configured on a Linux
client, access is unavailable through
NFSV4. The server string cannot be
interpreted.
626498/
59549160
P02
Cannot access the system with NFSv4
from a system that used UDP or NFSv4.
The server returned an incorrect error.
The issue was fixed in code to
automatically switch to NFSv3.
626500/
58917286
P02
On a very old Microsoft operating system
(DOS), if directory enumeration used all
filter bits including VOLUME, the VNXe
system did not return any entry.
The filter on volume bit was too
restrictive, and implemented for DOS
6.22. The code has been updated to
manage the VOLULME filter is to
return no entry only if the search
criteria is exclusively for VOLUME
information.
628540
P02
When a new file or directory was created
by a UNIX system in a parent directory
with both the UNIX setgid bit set and a
Windows Access Control List (ACL) with a
group security identifier (SID), the primary
group SID of the new file or directory was
not set to the SID of the parent directory.
This error occurred on a multiprotocol file
system mounted with MIXED access
checking policy and ntcredential
(generate Windows credentials) enabled.
Fixed the code to use the group SID
of the parent directory in this case.
628709/
55983968
P02
Windows audit auto-archive did not work
if:
This issue was fixed in code.
628716/
5803220
•
The Windows audit auto-archive is
enabled in a NAS server but not on
the system
•
The system tried to restart or
unload/load the NAS server.
Fixed problems
Priority
Symptom Description
Fix Summary
Tracking
Number
P02
The system can reboot when:
628728
•
Changing the location of the
Windows security event logging
file to a full file system
•
Restarting a NAS server with the
event auto- archive feature
enabled. The auto-archive files
that are not well configured can
saturate the audit file system
P02
Windows 8 or 8.1 and W2012/R2 servers
can lose access to a Data Mover CIFS
share when browsing the server UNC path
\\<server or IP>.
The code has been update to add the
FSCTL_DFS_GET_REFERRALS_EX
SMB2 IOCTL support for SMB3.
628748
P02
When the “All” option is used on
NetWorker NDMP, the backup stopped
because of a snapshot create failure on
the/.etc file system.
To avoid this issue, do not use “All”
option; specify each file system
separately.
633167
P02
After changing admin password for a CIFS
client connection, the original credential
can be still available in Kerberos cache.
This can cause a password mismatch and
the DHSM cannot recall the intended
data.
After setting a new password, bypass
the Kerberos cache and locate the
valid TGT from Kerberos server
directly.
634565/
45255446
P02
The Restore option in Windows Explorer
does not work when used with C$ path.
The code has been update to handle
the path access in
shadow_base.cxx=>ShadowDir
ectoryBase::parsePathname(
) in a similar manner as an NMFS
component.
638753/
47151218
P02
When a symbolic link is created with
NFSV4 in a file-system mounted in a
MIXED access policy, any user can delete
it.
This issue was fixed in the code. An
ACL is generated on the symbolic
link. Only users having Write
permission on the directory are
allowed to delete the symbolic link.
640159/
58131932
P02
A previous version of a deleted file
cannot be retrieved from Windows if wide
links are enabled.
Retrieve the previous version of the
file on a regular Windows server or
through the .ckpt directory.
641501/
57873800
P02
The windows security log can be
unreadable if a bad UNIX event log was
generated. The file name included in a
generated log can be truncated or invalid.
641503/
56016464
Fixed problems
Tracking
Number
Priority
Symptom Description
Fix Summary
P02
YP requests can stop indefinitely when
the domain is removed while some
requests are processed.
Fix bad error codes that are returned
when the domain is undefined in the
function. Determine if any YP request
must be tried again.
641545/
61583520
P02
If you discover multiple standalone ESX
hosts and add them in a single operation,
some of the hosts failed if the login
credentials are different for each of the
hosts.
Add standalone ESX hosts one at a
time.
651252/
63924250
P02
When a user attempts to add standalone
ESX hosts using the host name present in
DNS, the requests can fail if:
Update the host names and domain
information on the ESX servers to
match the host name entries on the
DNS server.
651648/
63924250
When the DHMS server does not exist, an
error appeared stating, “The ASA server
does not exist.”
An error does not appear if:
653291
P02
An error appeared stating the intermittent
data is unavailable on CIFS Share.
654188/
60876796
P02
When the CIFS server is a member of too
many groups, CIFS users cannot map to
the CIFS server share by name.
Support larger DNS T_KEY query
message (more than 8K) to establish
the secure context with the DNS
server when the CIFS server account
includes many groups.
654897/
62112774
P02
Unable to configure FT file bigger than
current max size of 100MB.
code.
658497/
60261046
P02
Deduplication functionality was lost when
74.25% to 75% of the current allocation
space of a thin-provisioned file system
was used.
The code has been updated to use
the correct parameter in the free
space threshold.
663695/
65183732
P02
Invalid CEPP event sent when opening a
file to read attributes.
The code has been updated to send
CEPP_OPEN_FILE_NOACCESS event
when opening file to read attributes.
664804
P02
Users were unable to upgrade to OE
Version 3.1.1.4993502.
code.
713756/
713766/
713758/
69876906
P02
•
The host name on one or more of
the hosts to be added does not
match the host name present on
the DNS server.
•
The host name is not set and still
has the default value
“localhost”.
• The ASA check box is cleared.
• A new DHMS server object
does not pass to the backend.
Known problems and limitations
Priority
Symptom Description
Fix Summary
Tracking
Number
P02
The data mover received an LDAP
response missing several bytes. An
uninitialized static object appeared. The
NAs server rebooted and tried to delete
the static object.
code.
670528/
52344416
P03
You cannot use any non-ASCII name in
snapCLI as these names could leave the
system in an unconfigurable state.
code.
626485/
622109
The following known problems and limitations have been identified in this release:
Tracking
Number
Priority
Symptom Description
Workaround Summary
P01
When a large size system is configured with
multiple file systems, checkpoints, protocols,
and so on, data failover (DU) and data failback
(DU) can take more than 60 seconds to
complete.
There is no workaround for this
issue.
665247
P01
When users modify access rights to allow the
ESX host to access VMware VMFS datastore for
the first time, the VNXe system requests the
ESX host to lay a VMFS partition on the VMFS
datastore. This can cause a data loss when the
VMFS partition is the result of a replicated
VMFS datastore.
The VNXe system only requests
the ESX to lay a VMFS partition
when ESX hosts are given
access to VMware VMFS
datastores and when the user
creates VMFS datastores
through the Unisphere GUI.
672984
If a user modifies access rights
on an existing VMware VMFS
datastores to allow access to
ESX hosts, the VNXe system will
only share the storage with the
ESX host, but not request the
ESX to lay a VMFS partition.
There is no workaround for this 686875
issue.
P01
Degradation in performance may occur when
replicating data to a VNXe3200 using
RecoverPoint.
P01
When upgrading from one 3.1.1.x VNXe software There is no workaround for this 692533
version to another 3.1.1.x version, thinissue.
provisioned file systems may extend
unexpectedly for the duration of the upgrade.
Tracking
Number
Priority
Symptom Description
Workaround Summary
P01
When replication synchronization is in
progress and the SP reboots, the replication
session can become inactive and the system
may go into a Critical health state. If the
synchronization was triggered by a manual
synchronization or failback command, the
command may fail with an I/O error.
To recover from this situation,
users can pause and resume
the operation as suggested by
System Health and Alert
recommendations.
698020
P01
When an SP fails over, the mgmtd service may
restart.
Although users may notice a
core dump for the mgmtd
service in such circumstances,
this happens occasionally and
the service restart does not
affect any other operations.
701773
P01
In an environment that has synchronous
replication set up for LUNs and asynchronous
replication set up for VMware VMFS
datastores, the VMware vCenter Site Recovery
Manager (SRM) based "reprotect" operation for
the synchronous replication may fail. This
occurs because of an issue with the "Element
Pairs" property of the asynchronous replication
set up for the VMware VMFS datastores on the
system.
Try the following:
705008
1. Identify and delete the
asynchronous replication
session(s) associated with
the VMware VMFS datastore
that is causing the failure:
a. To identify, run the
following UEM CLI
command, and note the
replication sessions that
do not include the
Element Pairs
information.
uemcli -u <user> -p
<passwd>
/prot/rep/session
show –detail
b. To delete, run the
following UEM CLI
command for each of the
identified sessions that
display this behavior.
uemcli -u <user> p <passwd>
/prot/rep/session
-id <session-id>
delete
2. Run the SRM "reprotect"
operation again.
Priority
Symptom Description
Workaround Summary
P01
If you create a NAS server with an IPv6
interface, delete it, and try creating a NAS
server again, the operation may fail. This
occurs because the associated Linux-based
routing tables for the IPv6 address remain on
the system even after the NAS server was
deleted. For such NAS servers, automatic
failback and subsequent failover operations
may also fail.
Try removing the IPv6 interface
before manually deleting the
NAS server. This will ensure that
the Linux-based routing tables
are cleared.
Tracking
Number
708936
In the case of automatic NAS
server removal during a failback
operation, restore the network
configuration by manually fixing
the relevant tables from the
Linux console. This means that
automatic NAS server failback is
disabled for NAS servers with
IPv6 interfaces.
In failover situations for such
NAS servers, contact your
service provider to clean up the
affected routing tables.
P02
System health checks may fail with
flr::check_if_storage_pool_recove
ry_is_required_2 error condition when
upgrading the operating environment software.
Add more LUNs to the pool, or
skip the Pre-Upgrade Health
Check (PUHC).
637235
P02
The usable capacity of a file system is less
than the size they specify. With a small file
system, a large portion of space cannot be
used.
issue. The space required for
the metadata throughout the
lifecycle of UFS64/UFS32 file
system may increase as the file
system fills up.
674992
UFS64 has a different layout
than UFS32 and has more
metadata overhead. Both
metadata and user data space
is removed. For example, if the
user creates a 3GB UFS64 file
system, then actual usable
space is less compared to
UFS32 file system. This
difference would generally be
noticeable for small file
systems, such as file systems
with a few Gigabytes (GBs)
space.
P02
In replication use cases, the Create Host
wizard displays storage system FC initiators on
the FC access page. The page should only
display host Fibre initiators.
issue.
676546
Tracking
Number
Priority
Symptom Description
Workaround Summary
P02
The prot/rep/session show command
stops responding (more than 30 minutes) if
one site is down.
Wait for request to timeout, and
reestablish connectivity with
the remote system. Once
connectivity is reestablished,
the /prot/rep/session
command will report updated
session information.
680959
P02
The amount free space reported is not always
accurate. Therefore, users may think there is
more space available than actual available
space.
To avoid this issue, create a file
system smaller in than the free
space reported by the system.
683278
P02
When the name of the datastore in Unisphere
is different from name of corresponding
datastore on the ESX server, the virtual
machines and virtual disks hosted by the
datastore may not show up under the Virtual
Machines tab on properties page of that
datastore in Unisphere.
Ensure that the name of the
datastore on the ESX server is
the same as the name of
corresponding datastore in
Unisphere.
683733
P02
During the RecoverPoint software installation
in a virtual RPA ISCSI environment, the
following warning message may appear:
RPA failed to see any LUN on the
array. Please check zoning and
LUN mapping
If this occurs, wait two minutes
and press refresh in the
RecoverPoint Deployment
Manager to rescan LUN.
687264
P02
After a pool is recovered, creation of a file
system may hang.
Cancel the file system creation
job. Create the file system again
approximately half an hour after
the recovery.
693474
P02
When configuring replication using the
Replication Wizard in Unisphere, the Select
Destination step may report an error with the
list of remote storage resources. The remote
resources are not shown and the error reports
that the system was unable to retrieve this
information.
Manually find the destination
storage resource by clicking the
Unisphere Refresh button on
this step.
694167
P02
When changing a Block-based storage
resource (such as a LUN) to a replication
destination, host access is automatically
disabled. Thus, the Change to Read-Only
button on the Replication tab does not apply.
No workaround.
695515
P02
When in service mode, the UI does not timeout.
Close the browser.
696015
There is not a fix or workaround
for this issue.
Priority
Symptom Description
Workaround Summary
Tracking
Number
P02
A false error message may display warning
users that the asynchronous replication
connection was lost. For example:
"2015-01-12T04:44:08.872Z" "spb"
"System_A" "4129" "N/A" "ERROR"
"14:6076c" :: "Communication with
replication host FNM12345678 has
been lost" :: Category=User
Component=Health
To verify the connection:
698836
-or2015-01-12T04:44:09.056Z" "spb"
"System_A" "4129" "N/A" "CRIT"
"14:60516" :: "System FNM12345678
has experienced one or more
problems that have had a major
impact" :: Category=User
Component=Health
P03
P03
If a language pack is erroneously uploaded to
the Software tab, the upload will fail with an
error directing the user to use the Languages
tab.
However, the first attempt to upload the
language pack to the Languages tab will fail with
a “corruption” error message.
When adding a set of hosts where two or more
have duplicate IQNs, one of the hosts
successfully logged in and the other attempted
logins that are rejected at a high rate. This
rejection resulted in SP reboots, no access to
storage and performance, and degraded hosts.
1. Click Hosts > Replication
Connections.
2. Select the system ID for
which the error was reported
from the list, and click Verify
and Update Connection.
False error messages will
automatically clear within
approximately 3 minutes of
being displayed.
Attempt to upload the language
pack to the Languages tab a
second time.
653930
Ensure that you assign correct,
unique IQNs to each host
connected to the VNXe3200.
655970/
64430424
Priority
Symptom Description
Workaround Summary
P03
The replication connection or replication
session operation fails after a software
upgrade or SP reboot, and the following
message appears.
The remote system failed
synchronous connection
validation. Ensure the fibre
channel connection is up and rerun the verify operation to
resolve the issue.
Complete the following steps
from Port Settings in Unisphere
or with the following command
in the CLI:
/net/port/fc -id
<value> set -speed
<value>
1.
3. Ensure that the FC cabling
and zoning configuration is
set up correctly.
The exact words in the message vary based on
the FC configuration.
Tracking
Number
665148
4. Change the FC port speed on
Port 0 from 8 Gbps to 4
Gbps.
5. Switch back to 8 Gbps on SP
A and SP B of the source and
destination systems to
trigger a new FC login
process.
6. Run the operation that failed
again.
If the same error message
reappears, use the following
procedure to restart
management services and reenable the sync replication
connection between systems.
2.
1. Log in to the Unisphere GUI.
2. Select Settings > Service
System to enter the
password for the service,
and then click Continue.
3. Select Restart Management
Software from the navigation
menu in the right pane.
4. Click the Execute Service
Action
P03
P03
The replication session displays a NonRecoverable Error state or Lost Sync
Communication states after a power on,
reboot, or panic of the SP(s).
Pause, and then resume the
session to change it to an Active
state.
Make sure that both SPs are up and running.
The source and destination
storage resources should have
the same SP owner.
If a health check fails from the GUI for the
Online Disk Firmware Upgrade (ODFU), there is
no way to restart the upgrade if the health
check fails with a warning.
Resolve the issue that is
causing the health check to fail
and try again, or use the CLI to
restart the upgrade.
668397
673112
Tracking
Number
Priority
Symptom Description
Workaround Summary
P03
Using a VNXe VSS hardware provider and
diskshadow to create a shadow copy and the
following error appears:
\DISKSHADOW> create
The last
operation failed.
Returned HRESULT: 80042314
- Error text:
VSS_E_HOLD_WRITES_TIMEOUT
Reduce the number of
concurrent initiate paths to the
resource.
P03
The user tries to create an asynchronous
replication session and the following error
appears:
4, Job failed with error:
Execution Errors: Replication
Internal Error (Error
Code:0x9881)
Wait a few minutes and retry the
operation. If the issue still
persists, contact your service
provider.
678536
P03
When the source LUN size is not 8k-aligned,
the replication session goes into nonrecoverable-error state during synchronization.
There no workaround for this
issue.
678707
P03
The following error message may appear when
opening Unisphere: Pre-login startup
service failed.
Launch another web browser to
access Unisphere.
679311
P01
The user cannot connect to Unisphere using
the Fully Qualified Domain Name (FQDN) of the
VNXe system.
Do not add a trailing dot “.” at
the end of the FQDN with the
HTTPS. If there is a trailing dot,
remove it and try again. You can
also use the IP address to
connect to Unisphere.
589382
P01
If vCenter makes network connections to the
storage system, this surpasses the web
server's connection limit and you cannot
connect to the array with other clients such as
Unisphere or UEMCLI.
Complete one of the following
actions:
617184
678530
If issues persist and PowerPath
is in use, switch to MPIO.
•
Remove and add the
array's Storage Provider
again in vCenter.
•
Reboot vCenter Server and
restart the management
service.
•
Upgrade vCenter to the
most recent patch release.
Refer to EMC Knowledge Base
article emc185241
P01
When attempting to add a VASA Provider to
VMware vCenter, the operation fails with the
"Vmomi.Fault.InvalidArgument" error.
Update the VMware vCenter's
SMS certificate. For more
information, refer to VMware
documentation.
620675
Tracking
Number
Priority
Symptom Description
Workaround Summary
P01
If an SP reboots while creating a snapshot, the
new snapshot can be in an "Offline" state.
Delete the newly created
snapshot that is in an "Offline"
state using the Unisphere GUI
or CLI. You can create another
snapshot again at the same
time.
623354
P01
If the user moves the DAEs across backend
buses (hot) the system reports a fault
indicating the DAE is missing.
Reboot the SPs to clear the
system.
623630
P02
The user can create two or more hosts with the
same name manually or same name can be
created by the user and by the system.
Users can modify names of the
hosts they created.
556807
P02
The EMC NetWorker stops responding if
snapshot creation fails on VNXe3200.
Identify and fix the root cause
for the snapshot failure. Try
running the backup from the
NetWorker again.
622251
P02
If the user renames a VMware VMFS datastore
that is unmounted from one or more ESX
hosts, and mounts the datastore again,
vCenter does not reflect the new name.
The user can manually rename
the datastore in vCenter to fix
the discrepancy.
622975
P02
When viewing the list of VMware hosts in
Unisphere, the total number of datastores
reported for an ESX host may not match the
number of datastores displayed when
expanding the ESX tree node.
Expand the ESX node. The
associated datastore is listed
for each virtual machine
running on the ESX.
623309
P02
Snapshot names cannot contain spaces.
To delimit words in snapshot
names, use alternative
characters such as an
underscore "_".
623879
P02
When uploading the upgrade file to the system
using Internet Explorer (IE8 or IE10), the
progress dialog box that indicates the upload
value appears up to a certain percentage, such
as 7%, and then disappears. The % complete
never appears again. After about 60 to 90
seconds, the processing file dialog box
appears. While the file uploaded correctly, the
disappearing dialog box may cause confusion.
Use web browsers other than
Internet Explorer.
624649
P02
The NFS resource graphic does not correctly
display the free capacity amount.
The user can use an NFS client
to confirm the exact amount of
free space in the file system.
626524
Tracking
Number
Priority
Symptom Description
Workaround Summary
P02
The size of a thin-provisioned file system may
increase automatically after the upgrade.
This action functions as
designed. During the upgrade,
the file system size is set to the
current allocated size. Once the
upgrade process is complete,
the file system size is restored
to the original size and the
current allocation increases by
a small amount.
723951
P03
An error occurs when the user tries to map an
Active Directory (AD) group to a Unisphere role
with an identical name in multiple domains.
This action is a known behavior
and does not impact
performance.
573054
P03
If you add an ESX server through Unisphere
(Hosts > Hosts > Create Hosts), VMware
datastore name change is not effective on the
ESX server.
VMware integration works well
when vCenter detects the ESX
host (Hosts > VMware Hosts >
Find ESX hosts). If you add an
ESX server, the VMware
datastore rename automatically
changes the name on the ESX
server.
596775
P03
The non-ASCII names created on Unisphere
may not display correctly on VSI (Virtual
Storage Integrator).
VSI supports only ASCII
characters. If you have
implemented VSI, use only
ASCII characters.
604216
P03
After a firmware update, a message indicating
a failure may appear.
The following message appears
in the log after the BMC comes
back online after the firmware
upgrades:
611993/
611997
SPB Suitcase 0 environment
interface failure cleared.
P03
While performing a software update through
Unisphere, the progress bar may become
unresponsive.
Wait about 10 minutes and
refresh the Unisphere browser
session. Log in again. If the
problem persists, contact EMC
service.
619374
Technical notes
Technical notes
Required update
EMC recommends that you keep your VNXe system up to date by upgrading to the
latest software version at your earliest opportunity.
Upgrade times
VNXe OE version 3.1.1 contains a firmware upgrade which will extend the OE upgrade
time for most systems to approximately 3 hours.
Problems downloading this release
If you have difficulty downloading this release using Microsoft Internet Explorer
version 7, try using another version of Microsoft Internet Explorer, Google Chrome, or
Mozilla Firefox version 4 or greater.
Obtain and install product licenses
Before you begin:
•
Register your product. This provides you instant access to easy-to-use tools to
plan, install, maintain, and service your product. It also entitles you to
software updates, installation tools, and more.
•
Ensure that you have the license authorization code (LAC) and the system's
14-digit serial number. As part of your software order delivery, a LAC letter is
sent by E-mail or physical letter. It includes the LAC, and directions for
entitlement activations and software downloads. The license key is included
in a License (.lic) file. It is based on your system's serial number, and unlocks
all features purchased at the time of sale. To obtain and activate your license
key, you will need to provide your system's serial number and LAC ID.
Before you can create storage, you must install product and feature licenses on your
system. To obtain and install the license files:
1.
Access the product page on the support website, and download the license
file locally.
Note: Do not change the name of the license file.
2.
Transfer the license file to a computer that has access to the storage
system, or connect the computer you used to obtain the license file to the
same subnet of the storage system.
3.
In Unisphere, click Settings > More configuration > Manage Licenses.
4.
On the Manage Licenses page, click Upload and Install License File.
5.
Review the End User License Agreement, click Accept license agreement,
and then click OK.
6.
In the Upload dialog box, locate the license file, select it, and click Open.
The license file is installed on the storage system.
Documentation
Documentation
For the most up-to-date documentation and help, go to EMC Online Support at
https://Support.EMC.com.
Software, media, organization, and files
VSS Hardware Provider
This service is on the host that ensures data consistency when making copies or
snapshots. It is for Block ISCSI and FC.
For the most up-to-date information on this service or other EMC products, go to EMC
Online Support at https://Support.EMC.com.
Installation
For installation and setup instructions, refer to the guide VNXe3200 Installation Guide
on the VNXe3200 product page of the VNXe Online Support website.
Troubleshooting and getting help
This section provides specific instructions for contacting EMC Customer Support and
obtaining additional information about EMC products.
Where to get help
EMC support, product, and licensing information can be obtained as follows:
Product information
For documentation, release notes, software updates, or for information about EMC
products, licensing, and service, go to EMC Online Support (registration required) at:
https://Support.EMC.com.
Troubleshooting
Go to EMC Online Support. After logging in, locate the appropriate Support by Product
page.
Technical support
For technical support and service requests, go to EMC Online Support. After logging
in, locate the appropriate Support by Product page and choose either Live Chat or
Create a service request. To open a service request through EMC Online Support, you
must have a valid support agreement. Contact your EMC Sales Representative for
details about obtaining a valid support agreement or to answer any questions about
your account.
Troubleshooting and getting help
Copyright © 2015 EMC Corporation. All rights reserved. Published in the USA.
Published May 2015
EMC believes the information in this publication is accurate as of its
publication date. The information is subject to change without notice.
The information in this publication is provided as is. EMC Corporation makes no
representations or warranties of any kind with respect to the information in this
publication, and specifically disclaims implied warranties of merchantability or
fitness for a particular purpose. Use, copying, and distribution of any EMC
software described in this publication requires an applicable software license.
EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC
Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC
Online Support (https://support.emc.com).

EMC VNXe3200 Release Notes

Transcription

Similar documents

We 1 Norman Lockyer Observatory

esxRanger … Hot Backup

NLP BASIC July 2015

NLPCT Overview of Programs

“Tell it like it is” engineering to clients and building owners

Licensed NLP Business Prac oner Training

Christopher Manning CS300 talk – Fall 2000

TOP 10 REASONS WHY MORE PEOPLE CHOOSE EMC DATA PROTECTION FOR VMWARE 1

See newsletter for further details.