Dell PowerVault NX1950 - Manual (Page 6)

Management Issues
Table 1 -4 provides information about the issues you may encounter when you perform management activities on the PowerVault NX1950 storage solution and
the possible workaround/solution.
Table 1-4. Management Issues
l TCP port = 1039: NSM
l TCP port = 25: Storage Processor
l TCP port = 443: Java CLI/Secure
l TCP port = 137: NetBIOS TCP
l TCP port = 139: NetBIOS Session Service
l TCP port = 445: SMB over TCP
l TCP port = 3389: Remote Desktop
The Action Pane displays
More Actions instead of
List of Actions The Action pane in the PowerVault NX1950
Management Console displays the menu name as
More Actions instead of List of Actions. When you click
More Actions, the menu is displayed. This issue is
observed in the following consoles:
l Microsoft Services for NFS
l iSCSI Software target
l Indexing Service
l Local User and Groups
l Event Viewer
l Performance Logs and Alerts
This feature is working as designed.
In Windows Unified Data
Storage Server 2003,
Standard Edition,
automatic failback is not
enabled by default The PowerVault NX1950 solution software does not set
the LUN_Rebalance registry key to enable re-balancing.
This prevents automatic failback.
NOTICE: Any unintended changes to the registry may
cause problems.
To enable failback manually, see the Dell PowerVault MD3000 User's
Guide available on the Dell Support website at support.dell.com.
In the Gateway solution,
creation of LUN is allowed
when no users are added
to the system
configuration (symcfg) This problem occurs if:
l No authorized users have been added to the
privileged user's list on each storage processor.
l Invalid users are added to the privileged user's
list on each storage processor.
l Authorized users are manually added to the
agent.config file.
This feature is working as designed.
In the Gateway solution,
the LUN Creation Wizard
does not display an error
when the storage group
is full The storage group has a maximum of 256 LUNs that
can be assigned to the storage group. Any additional
LUNs created through Storage Manager for SANs
console are not assigned to the storage group. No
warning or error messages are logged in the event log. This is a known issue.
Unable to extend volume
during I/O If the volume being extended also requires a LUN to be
extended, the volume extension fails while I/O is
running. To extend a volume while I/O is running:
l Extend the LUN through the Storage Manager for SANs
console.
OR
l Extend the LUN using Diskpart. For more information on
Diskpart, see the Microsoft Support website at
support.microsoft.com.
Network Interface Card
(NIC) Teaming is not
supported for iSCSI As per Microsoft's specification, NIC Teaming is only
supported for file protocols and not iSCSI. For more information about NIC teaming, see the Microsoft Windows
Server
® 2003 technology centers website at
www.microsoft.com/windowsserver2003/technologies.
In the Gateway solution,
VDS provider initialization
fails if user name contains
spaces While configuring Dell|EMC arrays using the Dell
Storage Initialization Wizard, you must enter the
array administrator username and password. If the
administrator username contains a space the Dell
Storage Initialization Wizard completes successfully
but the Share and Storage Management wizard
displays a VDS initialization error. Ensure that the array administrator username does not contain space
(s).
In the Gateway solution,
LUN can not be assigned
either to a server or
cluster Creating a LUN through storage manager for SANs fails
at the step Assign LUN to a server or cluster. Using navisphere, log-in, right-click on the storage array of your choice
and select properties.In the properties window, select the storage
access tab and check the access control enable check box.
In the Gateway solution,
Quorum disk can not be
assigned to a cluster Creating a LUN through storage manager for SANs fails
at the step Assign LUN to a server or cluster. Using navisphere, log-in, right-click on the storage array of your choice
and select properties.In the properties window, select the storage
access tab and check the access control enable check box. Rerun the
Dell Storage Initialization Wizard.
Issue Description Workaround/Solution