Device Definition Files (DDF) were updated in Data Center Expert 7.4.3 to address a recently discovered issue in Data Center Expert v7.4.0, v7.4.1, and v7.4.2. Earlier Data Center Expert versions are not affected.  Affected devices have duplicate sensor entries in Data Center Expert, with sensor status reported as unplugged.  The values for the following sensors could not be corrected, causing some sensors to report as unplugged in DCE 7.4.3.  You can delete the unplugged sensors, but historical sensor data will be lost. Otherwise, you can leave the sensor in the unplugged state to maintain historical data. Contact your local technical support if you have questions about a specific sensor value. Sensor Model affected* Number of External Battery Packs Smart-UPS 1500/3000 Battery Current Symmetra PX 250/500 and Galaxy VM/VX 3-phase UPS (Main/Bypass) Input Apparent Power - Phase (1-3) Symmetra PX 250/500 and Galaxy VM/VX 3-phase UPS (Main/Bypass) Input Power - Phase (1-3) Symmetra PX 250/500 and Galaxy VM/VX 3-phase UPS (Main/Bypass) Input Current Phase - (1-3) Smart-UPS VT/RT, Symmetra PX, Silcon and Galaxy 3-phase UPS (Main/Bypass) Input Apparent Power Total Symmetra PX, Symmetra 250/500 UPS, and Silcon UPS Output Power VA - Phase (1-3) Smart-UPS VT/RT, Symmetra PX, Silcon and Galaxy 3-phase UPS Output Peak Current - Phase (1-3) Galaxy VM/VX UPS Output Current THD - Phase (1-3) Galaxy VM/VX UPS Input Peak Current Phase - (1-3) Galaxy VM/VX UPS Output Power Watts - Phase (1-3) Symmetra PX 250/500 and Galaxy VM/VX 3-phase UPS Battery Type Galaxy VM 180/200 UPS Battery Status Single phase Smart-UPS and Matrix UPS *Other models may be affected.

Device status may be inaccurate because an attempt to transfer a device definition file (DDF) failed   If you have followed the instructions in NetBotz 750 appliance discovery process in DCE and the error has not cleared: Ping from the DCE server to the NetBotz 750. If ping fails, allow or enable ICMP in your firewall from the DCE server IP address to the NetBotz 750 IP address.  You might need to rediscover the device in DCE. For best results, update your DCE and NetBotz 750 to the latest versions. 

Hello! It's nice to see you here! Welcome to the EcoStruxure IT Help Center!  Check out the EcoStruxure IT Expert demo This read-only self-service demo is based on a real organization with real data that demonstrates IT Expert functionality in a preconfigured environment - no signup required! More info     

WARNING: This process requires a reboot of the appliance.  The appliance will not collect any data from devices, including alarms that may occur, until the system comes back up after the reboot.  If multiple users use the system, you may want to notify them that the system will be rebooted in order to perform the steps listed below. For physical appliances, connect a keyboard and monitor to the appliance.  For virtual appliances, connect to the console. Reboot the DCE server by power cycling the physical appliance or virtual appliance. For DCE 7.7.x and older, log in within 5 minutes of rebooting with the following credentials: Username: apcreset Password: apc For DCE 7.8.0 and newer, log in within 5 minutes of rebooting with the following credentials: Username: apcreset Password: Use the password you set when you first deployed the DCE server. This was required in DCE 7.8.0 and newer to comply with California law. See DCE 7.8.0 release notes Follow the instructions when prompted to reset the apc admin user to factory defaults (apc/apc). NOTE: This will not reset the whole appliance to defaults, only the username and password for the default admin user. Log in to the DCE desktop client with the factory default username and password apc/apc. Go to System > Users and Device Group Access.  Select the apc user and then select Edit to change the password. If you experience any issues during this process, contact your local technical support.

Gracefully shut down the DCE virtual appliance: In the DCE desktop client, go to File > Shut down server. In your vSphere (VMware) virtual server settings, provide the new value for the amount of RAM (memory) or number of CPU (processors) desired. Save the settings and power on the DCE virtual appliance. See Complete update process for DCE

Some customers have reported that devices disappear after upgrading DCE to version 7.9.0. A file system issue was discovered in DCE 7.9.0 that was addressed in DCE 7.9.2. If you are experiencing this issue, it is recommended that you restore the system using the last working backup taken before the issue occurred, and then upgrade your DCE server to version 7.9.2 (or newer when available).  If you do not have a DCE 7.8.1, 7.9.0, or 7.9.1 backup, you must start with a fresh install to resolve this issue, preferably DCE 7.9.2 (or newer when available).  

Gracefully shut down the DCE virtual appliance: In the DCE desktop client, go to File > Shut down server. In your vSphere (VMware) virtual server settings, select the option to add a network adapter. Specify the type and the network connection. Make sure this connection is mapped correctly, particularly when the DHCP server will be enabled on the private network interface. Save the settings and power on the virtual appliance. Log into the vSphere console for the DCE virtual appliance using the following credentials (default, but can be changed): Username: apcsetup Password: apcsetup Within five (5) seconds, press m to modify the settings. Accept the settings that were previously configured, or modify the settings if needed. Press y to accept the Enable private network interface option. Specify whether you want to enable the DHCP server on the private network interface. See Complete update process for DCE