Michael Dell spells out his plans for VMware:…

Michael Dell spells out his plans for @VMware: “Crown jewel of the EMC federation”

Michael Dell spells out his plans for VMware:…

“We believe it is very important to maintain VMware’s successful business model supporting an open and independent ecosystem,” Dell said. “We do not plan to do anything proprietary with VMware as regards Dell or EMC, nor place any limitations on VWware’s ability to partner with any other company.”

VMware Advocacy

HOW TO: Upgrade EMC Virtual Storage Integrator (VSI) for VMware vSphere Web Client

The EMC Virtual Storage Integrator (VSI) for VMware vSphere Web Client is a plug-in for VMware vCenter. It enables administrators to view, manage, and optimize storage for VMware ESX/ESXi servers and hosts and then map that storage to the hosts.

VSI consists of a graphical user interface and the EMC Solutions Integration Service (SIS), which provides communication and access to the storage systems.

Depending on the platform, tasks that you can perform with VSI include:

  • Storage provisioning
  • Setting multipathing policies
  • Cloning
  • Block deduplication
  • Compression
  • Storage mapping
  • Capacity monitoring
  • Virtual desktop infrastructure (VDI) integration
  • Data protection using EMC AppSync or EMC RecoverPoint

Using the Solutions Integration Service, a storage administrator can enable virtual machine administrators to perform management tasks on a set of storage pools.

Some light reading and the OVA package:

OK, let’s discuss the upgrade procedure!  Well, it is not actually an upgrade (not an in-place upgrade) but rather a database backup, deployment of the new version and then the DB restore (migration).

I am going to upgrade VSI for VMware vSphere Web Client from to 6.6.3.

Note: For migration from VSI 6.1 only: A known limitation causes the migration of VMAX storage systems from 6.1 to 6.6 to fail. Before creating a backup of the existing database, the storage administrator must delete all VMAX storage systems and then re-register them and the VMAX users after the upgrade.

  1. Log in to your current version of the Solutions Integration Service https://<SIS IP Address>:8443/vsi_usm/, click Database and select Take a Backup from the Task drop-down and click Submit to create a backup file of the existing database, and save the backup to a secure location.
    EMC VSI SIS - Database backup
  2. Deploy the new Solutions Integration Service .
    I will actually power the existing VA off and rename it as the new VA will have the same VM name and be running in the same cluster.

    1. Deploy EMC Solutions Integration Service OVA file;
    2. Power On virtual machine with EMC Solutions Integration Service and wait for the deployment to finish;
    3. Log in to the new Solutions Integration Service as admin/ChangeMe (see Default Password for details) and change the default password;
      https://<SIS IP Address>:8443/vsi_usm/
      There is no need to configure the EMC SIS, the configuration will be restored from the DB backup
    4. Just to be safe, log in to the new Solutions Integration Service, click Database and select Take a Backup to create a backup of the new Solutions Integration Service database, and save the backup to a secure location.

    5. Log in to the new Solutions Integration Service, click Database and select Data Migration from the Task drop-down menu. Click Choose File and locate the database backup of the previous version. Click Submit.
      It should not matter but in my environment the Data Migration did not work in Mozila FireFox 41.0.2 but worked in Internet Explorer 11.
      EMC VSI SIS - Database migration
    6. If the migration is successful, all Solutions Integration Service data for the previous version are moved to the new version, including users, storage systems, and access control information.
      If you changed VM name (host name), deactivate the previous version of the Solutions Integration Service.
      Follow Step 8.
    7. If the migration fails:
      a. Restore the new Solution Integration Service database from the backup file you created in step 4.
      b. Manually provision all required elements.
    8. Register the VSI plug-in with vCenter:
      1. Log in to the new Solutions Integration Service  https://<SIS IP Address>:8443/vsi_usm/admin
      2. Click VSI Setup;
      3. Enter the values for the following parameters and click Register.
        • vCenter IP/Hostname: The IP address that contains the VSI plug-in package.
          This is the IP address of the vCenter to which you are registering the VSI plug-in. If you are using the vCenter hostname, ensure that DNS is configured.
        • vCenter Username: The username that has administrative privileges.
        • vCenter Password: The administrator’s password.
        • Admin Email (Optional): The email address to which notifications should be sent.
      4. If the registration was successful, the following will be displayed in the Status window:
        10/30/2015 17:23:12 sending your request ...
        10/30/2015 17:23:21 receiving your response ...
        The operation was successful.
        Registered VSI Plugin:
        Key: com.emc.vsi.plugin
        Name: EMC VSI Plugin
        Description: Integrated management support for EMC storage systems
        Admin Email: none
      5. Browse to the vSphere Web Client address.
        After you log in, the VSI plug-in is downloaded and deployed.
        Note: The download takes several minutes.
        If you have installed previous versions of the VSI plug-in, clear your browser cache to ensure that you use the newest version of VSI.

Hope this will help.

EMC PowerPath Virtual Appliance Version 2.0 SP1: New features and changes

EMC PowerPath Virtual Appliance Version 2.0 SP1 brings the following enhancements to the PowerPath Virtual Appliance web console.

A new tab named PowerPath Monitor added. Includes:

  • PowerPath Monitor > Group/Host view lists all the PowerPath hosts under corresponding groups. Physical PowerPath hosts are organized under their corresponding user-defined host groups (created from the inventory tab) and ESXi hosts are grouped under the corresponding vCenter to which they belong.
  • PowerPath Monitor > Group/Host > Summary view Provides host monitoring capabilities including device/path monitoring. The monitor displays PowerPath volume, path, and bus details.
    Healthy state:
    EMC PowerPath Virtual Appliance Version 2.0 SP1 - ESX host summary - healthy

    EMC PowerPath Virtual Appliance Version 2.0 SP1 - ESX host summary - degraded

  • PowerPath Monitor > Group/Host > LUN view similar to PowerPath Viewer, LUN view adds Queued IO value displayed under LUN view, (not available with PowerPath Viewer).
    EMC PowerPath Virtual Appliance Version 2.0 SP1 - LUN view
  • PowerPath Monitor > Group/Host > BUS view shows the association between HBA Ports > Array > Array Ports along with the IOs queued for the bus.
    EMC PowerPath Virtual Appliance Version 2.0 SP1 - BUS view
  • EMC PowerPath Virtual Appliance capabilities available as a plug-in for VMware vCenter: PowerPath Virtual Appliance supports script plugins on vSphere vCenter 5.5 and above (only vCenter Web Client is supported). vCenter plugin provides a minimal view of the PowerPath Virtual Appliance GUI. The script plugin is registered and enabled on the vCenter server. It can be accessed via the short cut “EMC PowerPath/VE License Manager” in vCenter web client. Only the details of ESXi hosts belonging to the current instance of vCenter are displayed.
    EMC PowerPath Virtual Appliance Version 2.0 SP1 - vCenter Plugin
    Registering EMC PowerPath vCenter Plugin:

    • Click on Register vCenter Plugin;
    • Accept vCenter Server certificate if required;
    • By default script based plugins are disabled in vCenter Web Client. To enable script the plugin on vCenter server follow these steps:
      • Edit the file, and then append the following line at the end of the file (if not already added):
        scriptPlugin.enabled = true
        You can locate the file in the following locations of the vCenter server:

        • On vCenter server 5.x:
          • VMware vCenter Server Appliance: /var/lib/vmware/vsphere-client
          • Windows 2003: %ALLUSERSPROFILE%Application DataVMwarevSphere Web Client
          • Windows 2008/2012: %ALLUSERSPROFILE%VMwarevSphere Web Client
        • On vCenter server 6.0.x:
          • VMware vCenter Server Appliance: /etc/vmware/vsphere-client/
          • Windows 2008/2012: %ALLUSERSPROFILE%VMwarevCenterServercfgvsphereclient
      • Restart the vSphere Web client service on the vCenter server.
        • On Windows-based vCenter appliances, restart the service with name vSphere Web Client
        • On Linux-based vCenter appliances, run /etc/init.d/vsphere-client restart
    • Access the plugin after registering and enabling it. Use the short-cut, EMC PowerPath/VE License Manager, located in the vCenter Web client.
      EMC PowerPath Virtual Appliance Version 2.0 SP1 - vCenter Plugin - icon
      If you use the default self-signed certificate of Virtual Appliance, open the PowerPath Virtual Appliance GUI in a new tab in order to accept the certificate before accessing plugin via the vCenter web client.
  • Minimum configurable polling interval for PowerPath/VE changed to 10 minutes.
    Navigate to System > Settings, adjust polling interval if required
    EMC PowerPath Virtual Appliance Version 2.0 SP1 - ESXi poll interval
  • Added polling capability for PowerPath/VE 6.0 and later hosts – based on events.
  • Direct upgrade support from EMC PowerPath Virtual Appliance 2.0.0.
    See EMC PowerPath Virtual Appliance Upgrade from 1.2.x -> 2.0.0 and 2.0.0 to 2.0.1 for details.
  • Added user interface enhancement for Context menu option in PowerPath Monitor tab for inventory management
  • Enhanced back-up and restore capability of EMC PowerPath Virtual Appliance inventory.
    The EMC PowerPath Virtual Appliance Installation and Configuration Guide provides more information.
  • Added new fields in REST API response for host including:
    • osVersion: Version of OS running on the host
    • hostStateTimestamp: Time when the host state was updated in PowerPath Virtual Appliance
    • deadPathCount: Total number of dead paths in the host
    • totalPathCount : Total number of paths in the host
    • totalVolumeCount : Total number of volumes in the host
    • degradedVolumeCount: Total number of degraded volumes on the host
  • Support for RTOOLS 6.0 SP1
  • Queued IO count has been added in the response for Path REST API



HOW TO: Upgrade EMC PowerPath Virtual Appliance

This article covers EMC® PowerPath® Virtual Appliance upgrade from 2.0.0 to 2.0.1. Please refer to “HOW TO: Upgrade EMC PowerPath Virtual Appliance” article for the upgrade from EMC® PowerPath® Virtual Appliance 1.2.x.

  1. Download EMC® PowerPath® Virtual Appliance upgrade package from EMC Online Support portal:
  2. Shutdown PowerPath Virtual Appliance and:
    1. Take a snapshot;
    2. Add a new 10 GB disk from storage to PowerPath Virtual Appliance (VM). It is recommended that you increase the size of root file system in case of upgrade from PowerPath Virtual Appliance 2.0.0
  3. Power on PowerPath Virtual Appliance;
  4. SSH to EMC PowerPath Virtual Appliance, login as root and follow this procedure to extend the root file system:
    1. epp001:~ # df
      Filesystem                  1K-blocks    Used Available Use% Mounted on
      rootfs                        3853936 1652176   2000852  46% /
      udev                          2028592     108   2028484   1% /dev
      tmpfs                         2028592       0   2028592   0% /dev/shm
      /dev/mapper/systemVG-LVRoot   3853936 1652176   2000852  46% /
      /dev/mapper/systemVG-LVswap   6094400  143484   5636344   3% /swap
      /dev/sda1                      165602   24037    133015  16% /boot
    2. epp001:~ # cat /proc/partitions
      major minor  #blocks  name
      8        0   10485760 sda
      8        1     171012 sda1
      8        2   10311680 sda2
      8       16   10485760 sdb
      253        0    6291456 dm-0
      253        1    4018176 dm-1
    3. epp001:~ # ls -l /sys/class/scsi_host
      total 0
      lrwxrwxrwx 1 root root 0 Oct 29 12:18 host0 -> ../../devices/pci0000:00/0000:00:10.0/host0/scsi_host/host0
      lrwxrwxrwx 1 root root 0 Oct 29 12:18 host1 -> ../../devices/pci0000:00/0000:00:07.1/ata2/host1/scsi_host/host1
      lrwxrwxrwx 1 root root 0 Oct 29 12:18 host2 -> ../../devices/pci0000:00/0000:00:07.1/ata3/host2/scsi_host/host2
    4. epp001:~ # echo "- - -" > /sys/class/scsi_host/host0/scan

      This command is used to rescan scsi host. Echoing a wildcard value of “channel target and lun”, and the operating system will rescan the device path.

    5. epp001:~ # cat /proc/partitions
      major minor  #blocks  name
      8        0   10485760 sda
      8        1     171012 sda1
      8        2   10311680 sda2
      8       16   10485760 sdb
      253        0    6291456 dm-0
      253        1    4018176 dm-1
    6. epp001:~ # fdisk -l /dev/sdb
      Disk /dev/sdb: 10.7 GB, 10737418240 bytes
      255 heads, 63 sectors/track, 1305 cylinders, total 20971520 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disk identifier: 0x00000000
      Disk /dev/sdb doesn't contain a valid partition table
    7. epp001:~ # vgdisplay
        --- Volume group ---
        VG Name               systemVG
        System ID
        Format                lvm2
        Metadata Areas        1
        Metadata Sequence No  4
        VG Access             read/write
        VG Status             resizable
        MAX LV                0
        Cur LV                2
        Open LV               2
        Max PV                0
        Cur PV                1
        Act PV                1
        VG Size               9.83 GiB
        PE Size               4.00 MiB
        Total PE              2517
        Alloc PE / Size       2517 / 9.83 GiB
        Free  PE / Size       0 / 0
        VG UUID               RHiVZ9-cqSo-srmH-NGZs-zm4W-rAAm-fLeC15
    8. epp001:~ # vgextend systemVG /dev/sdb
      No physical volume label read from /dev/sdb
      Physical volume "/dev/sdb" successfully created
      Volume group "systemVG" successfully extended
    9. epp001:~ # vgdisplay
      --- Volume group ---
      VG Name               systemVG
      System ID
      Format                lvm2
      Metadata Areas        2
      Metadata Sequence No  5
      VG Access             read/write
      VG Status             resizable
      MAX LV                0
      Cur LV                2
      Open LV               2
      Max PV                0
      Cur PV                2
      Act PV                2
      VG Size               19.83 GiB
      PE Size               4.00 MiB
      Total PE              5076
      Alloc PE / Size       2517 / 9.83 GiB
      Free  PE / Size       2559 / 10.00 GiB
      VG UUID               RHiVZ9-cqSo-srmH-NGZs-zm4W-rAAm-fLeC15
    10. epp001:~ # lvextend -L +5GB /dev/systemVG/LVRoot
      Extending logical volume LVRoot to 8.83 GiB
      Logical volume LVRoot successfully resized
    11. epp001:~ # resize2fs /dev/systemVG/LVRoot
      resize2fs 1.41.9 (22-Aug-2009)
      Filesystem at /dev/systemVG/LVRoot is mounted on /; on-line resizing required
      old desc_blocks = 1, new_desc_blocks = 1
      Performing an on-line resize of /dev/systemVG/LVRoot to 2315264 (4k) blocks.
      The filesystem on /dev/systemVG/LVRoot is now 2315264 blocks long.
    12. epp001:~ # df
      Filesystem                  1K-blocks    Used Available Use% Mounted on
      rootfs                        8884968 1653164   6771068  20% /
      udev                          2028592     108   2028484   1% /dev
      tmpfs                         2028592       0   2028592   0% /dev/shm
      /dev/mapper/systemVG-LVRoot   8884968 1653164   6771068  20% /
      /dev/mapper/systemVG-LVswap   6094400  143484   5636344   3% /swap
      /dev/sda1                      165602   24037    133015  16% /boot
  5. Upgrade EMC PowerPath Virtual Appliance:
    1. Upload ‘‘ to a directory on Virtual Appliance VM, /tmp for example;
    2. SSH into the PowerPath Virtual Appliance VM, login as root;
    3. Unzip the upgrade package:
      epp001:~ # cd /tmp
      pdc1epp001:/tmp # unzip
        creating: applianceUpdate/
       inflating: applianceUpdate/
       inflating: applianceUpdate/
    4. Run
      epp001:/tmp # cd applianceUpdate
      epp001:/tmp/applianceUpdate #
    5. Run
      epp001:/tmp/applianceUpdate # /bin/bash applianceUpdate
      14:19:23 [INFO]: * Starting the appliance update process *
      14:19:23 [INFO]: Updating PowerPath: -&gt;
      14:19:23 [INFO]: Logs can be found here:
      14:19:23 [INFO]: /opt/ADG/update/logs/update-
      14:19:23 [INFO]: * Validating update *
      14:19:24 [INFO]: Checking installed product version ...
      14:19:24 [INFO]: Product version check is successful.
      14:19:24 [INFO]: Adding update repo ...
      14:19:24 [INFO]: Update repo added successfully.
      14:19:24 [INFO]: Checking OS version ...
      14:19:24 [INFO]: OS version check is successful.
      14:19:24 [INFO]: Update validation successful.
      14:19:24 [INFO]: * Starting Update *
      14:19:24 [INFO]: * Running pre-update script *
      14:19:56 [INFO]: Updating the existing packages. This may take some time. Please wait ...
      14:21:15 [INFO]: Update of existing packages completed.
      14:21:15 [INFO]: Installing new packages. This may take some time. Please wait ...
      14:21:17 [INFO]: Installation of new packages completed.
      14:21:17 [INFO]: Updating the product version to ...
      14:21:17 [INFO]: * Running post-update script *
      14:21:19 [INFO]: * COMPLETE: Appliance update completed successfully *
    6. Reboot the PowerPath Virtual Appliance:
      epp001:/tmp/applianceUpdate # reboot
      Broadcast message from root (pts/0) (Thu Oct 29 14:22:27 2015):
      The system is going down for reboot NOW!
  6. Log in to EMC PowerPath Virtual Appliance, navigate to System / Health and check all services are running.

Hope this will help.

HOW TO: Upgrade EMC Secure Remote Services Virtual Edition (ESRS VE)

What is EMC® Secure Remote Services (ESRS)?

EMC® Secure Remote Services (ESRS) is a two way remote connection between EMC Customer Service and your EMC products and solutions, available with Enhanced or Premium warranties and maintenance agreements at no additional cost. ESRS maintains connectivity with your EMC products around the clock and automatically notifies EMC if a problem or potential problem occurs. If troubleshooting is necessary, an authorized and authenticated EMC Customer Service professional uses the secure connection to establish a remote session based on your customized security and remote access settings to diagnose, and if necessary, to repair your EMC products and solutions. If unexpected issues arise, our proven processes ensure the fastest possible response, escalation, and resolution time to maximize information availability and reduce your costs. ESRS also connects you with EMC’s Big Data and predictive analytics capabilities, arming you with actionable intelligence to optimize your IT environment and your business.

As of ESRS v. 3.0.4, ESRS IP gateway and, ESRS Policy Manager (optional) are customer installable!

Please refer to the following articles for the information on how to deploy or upgrade Windows based ESRS IP Gateways to ESRS Virtual Edition / Virtual Appliances:

OK, let’s go through the EMC SRS Virtual Edition upgrade:
N.B. I am using screenshots from the 3.04–>3.06 upgrade.  ESRS v. 3.08 was released on the 18th of September. UPDATE: ESRS v. 3.10 released on the the 14th of December.

Please make sure you take a snapshot of the Virtual Appliance before you proceed with the upgrade!

Login to ESRS VE VA, you will notice the message that the UPDATE is AVAILABLE, click on the View Update link:

This will bring you to the following screen, click on Download button to download the latest ESRS software update:

ESRS Virtual Edition Upgrade - 01

Wait for the download to finish:
ESRS Virtual Edition Upgrade - Downloading

Depending on the speed of your Internet connection, you may get the following message:
ESRS Virtual Edition Upgrade - The download is taking longer than expected

Refresh the web page or click through the tabs.  The new new version will be available for the installation.

ESRS Virtual Edition Upgrade - 02

Click Apply and Yes, Apply Update to commence the update.

ESRS Virtual Edition Upgrade - 03

ESRS Virtual Edition Upgrade - 04

Open ESRS VE VA’s console and wait for the update to finish.  Login to the web interface https://ESRS_VE_VA_nameor_IP:9443, confirm the running version, Service Status and System Status.

If you have ESRS VE configured as a cluster, update the second appliance as well.

Hope this will help.

Cannot fetch NSX Controllers after NSX Manager upgrade

I am upgrading NSX Manager from 6.1.4 to 6.2 in the environment with two vCenters configured in Linked Mode.

When NSX Manager was upgraded in one of them and vCenter Web Client service restarted, I logged back to the Web Client to proceed with the upgrade.  Both NSX Managers were visible and correct versions were displayed.  Upon navigating to Networking & Security / Installation / Management, the list of NSX Controllers could not be fetched and the following error was displayed:

Cannot fetch NSX Controllers
faultCode:Server.Processing faultString:’java.lang.NullPointerException : null’ faultDetail:’null’

Suspecting there may be a compatibility issue between the new NSX Manager Web Client extension and the old version, I tried to restart vCenter Web Client service on the vCenter where NSX Manager was not upgraded yet but it did not help.

To proceed with the upgrade I stopped the NSX Management Service on the second vCenter and re-lauched Web Client.

As suspected, Web Client successfully discovered one NSX Manager and all three NSX Controllers.

NSX Manager Upgrade NSX Controllers

Click on the Upgrade Available to upgrade NSX Controllers.

Hope this will help.

VMware ESXi 5.5/6 installation on Cisco FlexFlash drive fails with “Can’t have a a partition outside the disk!” error

I’m trying to install VMware vSphere ESXi 5.5 on Cisco UCS C220 M3 server. The local storage is Cisco Flexible Flash (FlexFlash) internal 32GB SD Card.

Cisco FlexFlash Physical Drive Info

I repartitioned the whole SD card as one HV (Hypervisor) bootable 29GB partition:

Cisco FlexFlash Virtual Drive Info

Please refer to ‘Cisco FlexFlash: Use and Manage Cisco Flexible Flash Internal SD Card for Cisco UCS C-Series Standalone Rack Servers’ for details how to configure and use internal SD cards.

During VMware vSphere ESXi 5.5 installation, the installer sees local 29GB partition:

Select a Disk to Install or Upgrade

Select language, root password and when I press F11 to Install, it gives the following error:

This program has encountered an error:
partedUtil failed with message: Error: Can’t have a a partition outside the disk!
Unable to read partition table for device

partedUtil failed with message Error Cant have a partition outside the disk

VMware Knowledge Base Article “Formatting LUN as VMFS 5 fails with the error: Can’t have a partition outside the disk! (2082806)” suggests that the Device/LUN already has a partition configured. To resolve this issue, you need to create a normal MS-DOS partition (I guess ANY partition that can be deleted by the Installer) on the affected disks using partedUtil utility.  There is no need to map/attach the LUN/SD to another host, you can press ALT-F1, open the DCUI and run partedUtil utility.  Unfortunately, it did not work for me.

The workaround is to install VMware vSphere ESXi 5.5 Update 1 and then either upgrade the host with vCenter Update Manager or install install ESXi 5.5 Update 2 for a clean installation.

Many thanks to malabelle on VMware Community forum for suggesting the workaround.

PS I also tried to use ESXi 6.0 installer but got the same error message. It must be one of these scenarios where you better go back than forward…

PPS This issue has been recorded as a bug by Cisco: Unable to install ESXi 5.5 U2 on UCS FlexFlash


HOW TO: Configure Cisco UCS power management for VMware DPM

  1. Login to Cisco UCS Manager
  2. Configure Service Profile Management IP address
    Servers – Service Profile – Actions – Change Management IP address
  3. Change/Create IPMI user
    Servers – Policies – IPMI Access Policies
    IPMI over LAN – Enable
    Create IPMI user. The user name is CaseSENSITIVE!
    Cisco UCS Create IPMI user
  4. Check the policy is associated to the Service Profile or Template
    Policies – IPMI Access Profile Policy – IPMI
    Cisco UCS IPMI Access Profile Policy
  5. Make a note the blade’s CIMC MAC address:
    Equipment – Chassis X – Servers – Server X – Inventory – CIMC – Management Interface
    NB You can hover over the MAC address, Right Click and select Copy
    Cisco UCS CIMC Management Interface MAC
  6. Configure VMware vSphere ESXi host – Configuration – Power Management – Properties
    VMware DPM Edit IPMI iLO Settings
  7. Click OK.
  8. Configure Cluster Power Management:
    Cluster settings – vSphere DRS – Power Management (Manual/Automatic)
  9. You can also put the host in Standby mode manually if required.

EMC Secure Remote Services (ESRS) Policy Manager 6.6 “General System Error”

I installed ECM Secure Remote Services (ESRS) Policy Manager 6.6 using default settings. Launching the application page (https://name_or_IP:8443/aps/) failed with General System Error, see screenshot for details.

General System Error:
An unknown error was detected, please contact your system administrator with the details below: FaultEvent fault=[RPC Fault faultString=” : Failed to get root light group” faultCode=”Server.Processing” faultDetail=”null”]

ESRS Policy Manager General System Error

Apparently, if you install the ESRS Database on the same server as the Policy Manager, all you need to do is to change the Database Port Number from the default port 9001 to, for example, 9002.

ESRS Policy Manager Database Port Number

Hope this will help.

HOW TO: VCE Vblock® Systems Password Change

VCE Vblock consist of many components and when it gets built in the VCE factory, these components are configured with a standard VCE password(s). These passwords can be found in the documentation provided by VCE.  This can be in a form of a spreadsheet or as part of VCE Vblock System As-Built documentation which also includes all technical details for your Vblock (host names, IPs, serial numbers, Site IDs, diagrams etc).

Obviously, it is a security risk to keep standard passwords when Vblock goes into production and therefore it is recommended to get them changes according to your security standards.

If you are not familiar with where and how to change the default passwords, this can be quite time consuming process.  But there is no need to stress about this anymore!  VCE have finally released a document that lists the procedures for changing password on all Vblock components.

The VCE Vblock Systems Password Management document is available on VCE Support Portal under Article Number 3581 / vce3581 (requires VCE Support Portal account).


PS My Default Passwords page has a good selection of standard passwords for EMC, Cisco and VMware products as well.