Visitors

EMC UIM Unified Infrastructure Manager/ Provisioning. Version 4.0 Patch 02

Hurray! EMC UIM 4.0 Patch 02 has been released! Lots of new features and bug fixes!

New features and changes

Decommission of shared storage service

When using UIM 4.0 and UIM 4.0 Patch 01 to perform a full decommission of a shared storage service, VMs were correctly deleted from the shared storage service, however VMs and datastores were also deleted from any attached standard services. This has been corrected in UIM 4.0 Patch 02, so that when decommissioning a shared storage service, VMs are no longer deleted from any attached standard services.
When using UIM 4.0 Patch 02 to decommission a shared storage service, UIM will check for any VMs (running or not) and display an override confirmation that lists all impacted disks. Also, if detaching a standard  service, UIM 4.0 Patch 02 will display a new override confirmation to warn of possible service interruption.

Naming convention for VMAX base initiator groups

With UIM 4.0, the pre-requisites for VPLEX configuration imposed a naming convention in which the name of the VMAX base initiator groups containing the actual initiators, were named according to the WWNN of the ports in that initiator group.
As of UIM 4.0 Patch 01, the WWNN naming convention, as described above, is no longer mandatory.
However, it should be noted that for unconfigured systems, UIM 4.0 Patch 02 uses a simple naming convention for VMAX initiator groups, whereby each initiator is in a base group of its own and that base group’s name is the WWPN of the initiator. Although not mandatory, it is highly recommended that you use the same group naming convention for consistency and ease of troubleshooting.
For details, refer to EMC Unified Infrastructure Manager/Provisioning Configuration Requirements for Converged Hardware Systems.

Handling of shared storage volumes

As of UIM 4.0 Patch 01, an issue has been fixed that may cause degraded performance on storage arrays, due to multiple HLUs being assigned to the same storage volume. It occurred when a shared storage volume, which had already been assigned an HLU for one host, was added to a standard service where that HLU was already in use by another volume, forcing UIM to use a different HLU, which could lead to severe performance issues over time as the volumes are used.
As of UIM 4.0 Patch 01, unique HLUs are used for all shared storage service volumes.

Support for Disjoint Layer 2

Optionally, for customers who want to implement Disjoint Layer 2 networks, UIM 3.2 P 01 and higher is compatible with UCSM 2.0, which supports Disjoint Layer 2 networks in end-host mode.
In a Disjoint Layer 2 network, separate vNICs are configured to communicate with different network domains to ensure that traffic for the different domains does not flow on the same interface.
VLANs for disjoint domains are assigned different uplink ports (or port channels). Traffic for a VLAN that is part of a disjoint network can only flow through a designated uplink port or port channel that is assigned to that VLAN. Traffic for that VLAN is dropped on all other uplinks. Therefore, with UIM 3.2 P 01 and greater, the vNICs that are to communicate with the disjoint domains should be pinned only to the uplink, which is designated to handle traffic for the VLANs on that domain.
The following limitations and assumptions apply:

  1. If the VLAN designated as the OS Install VLAN is associated with pin groups, and if any of those pin groups are specified on the vNICs, then operating system installation through UIM/P may fail. Therefore, it is not advisable to use pin groups in this case.
  2. If a vNIC is provisioned with two or more VLANs and then (outside of UIM/P) the VLANs are added to different disjoint domains, the port that the vNIC is pinned to will go down. However, UIM/P does not generate a service alert to indicate that the port is down.
  3. If the isolation zone for a service is updated and the new NFS VLAN or new ESX Management VLAN is pinned, then UIM/P does not add them to all vNICs; UIM/P removes the old management VLANs from all vNICs, but will only add the new vNICs if they are not pinned. However, UIM/P generates a validation error to indicate that the NFS VLAN and/or ESX Management VLAN will need to be manually added to at least one vNIC.
    To do so, open the Service Editor, select the Network tab, and edit the appropriate vNICs to add the VLANs.
Configuration Center console support — Java runtime 1.7.0

The UIM/P Configuration Center console requires Java runtime 1.7.0. As of UIM/P 4.0 Patch 01, the UIM/P Configuration Center launches with Java runtime versions 1.7.0_7 to 1.7.0_25.

For the full list of bug fixes please refer to Unified Infrastructure Manager/Provisioning (UIM/P) 4.0 Patch 2 Read Me.

Documentation/Release Notes/Update Media and Full Release ISO:

Unified Infrastructure Manager/Provisioning 4.0 Documentation Portfolio
Unified Infrastructure Manager/Provisioning (UIM/P) 4.0 Patch 2 Read Me
Unified Infrastructure Manager/Provisioning (UIM/P) 4.0 Patch 2 – Update Media
Unified Infrastructure Manager/Provisioning (UIM/P) 4.0 Patch 2 Virtual Appliance – Full Release

Gentlemen, start your engines and upgrade EMC UIM/P!

9 comments to EMC UIM Unified Infrastructure Manager/ Provisioning. Version 4.0 Patch 02

  • Just received an email from a fellow UIM/P enthusiast:
    ========================================================
    I’m working a lot with VCE Vblocks and EMC VSPEX solutions. We have our own lab and we’ve just replaced our VNX 5300 with VNX 5400.
    We’re using UIM/P at moment ( we’re testing UCS Director as well. Maybe we’ll use that instead ). But UIM/P isn’t able to discover the new VNX 5400. I’m using the same “Administration – VCE Vblock Systems – SVG-VSPEX “
    I’ve used the same ip-adresses on the new VNX 5400, so I just ran a new Discover.
    Will that work?
    ========================================================

    I have not played with VNX 5400 yet so don’t have a personal experience.
    I quickly checked the latest UIM/P 4.0 Patch 2 Support Matrix and apparently VNX5400 is not supported yet.
    Here is the link to the Documentation Portfolio. Support Matrix, page 19:
    https://support.emc.com/docu48610_Unified_Infrastructure_Manager/Provisioning_4.0_Documentation_Portfolio.pdf?language=en_US
    Let me know if you have any other questions.
    Mark

  • Ramkumar

    VCE has yet to certify EMC gen2 VNX storages under UIMp

  • Faizur

    Hi Mark ,..

    How can i add additional NIC in existing Service in Management from UIMP..Do I need to make the Service offering Mark Unavailable..?If so how to make it..without making any impact to the environment..

    Thanks

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>