DCE FAQ

To troubleshoot devices or to create DCE DDFs, an output of a device's addresses and their values is necessary.  This page describes how to generate that output for SNMP, Modbus, and NetBotz devices.    SNMP for DCE version 7.6 and newer   Log in to the DCE web client, version DCE 7.6. and newer.   Click Status in the menu in the upper right corner of the page. Under Additional Information, select SNMP Device Walk and click Submit.   In the Target Host field, enter the IP address of the device you want to walk.   Select SNMPv1 or v3 and enter the credentials. Hint: If using SNMPv1, the default Read Community on most devices is public.   Click Submit.   DCE_SNMP_device_walk_2_360006388878.png   It takes a few minutes to process. Wait for the spinner to stop. The results will be printed on the page.   In the browser, select File > Save As, or copy and paste the text to a text file.   Save the file and send it to the DDF Team in an Asset Definition Request, or as requested by technical support.     For Modbus on any DCE version or SNMP with DCE versions prior to 7.6   Modbus.org announced it is expunging all occurrences of inappropriate language of the query and response paradigm of Modbus communications. This tool was updated to comply as of version 1.9.1. More...   Requirements   Windows 10+ or Windows Server 2012+ Admin access to Command Line or Windows PowerShell   Download the walk utility from here.   Unzip the file. Open and read the README.txt file for detailed instructions on how to use the command line utility. See information about general usage here.   Open a Command Prompt (Admin) or Windows PowerShell (Admin) and navigate to the folder you just unzipped.   Run: walk.bat <protocol> -ip <ip> <options> This will generate a walk file named using the IP Address and a ".walk", ".json", or ".xml" extension.  

NTLM and SMB versions may prevent a Windows share from being mounted.   In DCE, CIFS (Windows) mounts do not work when FIPS mode is enabled. MD5 authentication is required for CIFS, which is not supported in FIPS mode. See Server access  Having problems? See Troubleshooting DCE backups   Create a folder on the Windows system that you want to be the backup destination.   Right-click the folder and select Properties.   Select the Sharing, and then Share.   DCE_winshare1_360011485058.jpg   Add the specific user you want DCE to use to store the backup.   DCE_winshare2_360011485058.jpg   Set the user's permission level to be Read/Write.   DCE_winshare3_360011485058.jpg    Click Share. Select Advanced Sharing.   DCE_winshare4_360011485058.jpg   Make sure the Share this folder checkbox is checked, and then select Permissions.   Add the specific user that you want DCE to use to connect to this share (same user as step 5).   Set the user permissions for Full Control.  Click Apply and OK. NOTE: You will need the share name, IP address of the Windows system the share is stored on, and the credentials for the user you granted full control.     See How to perform a backup in DCE Complete update process for DCE

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

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).  

  Some devices, including many Uniflair cooling devices, use a network card from Carel called pCOWeb.  These cards can be problematic for Data Center Expert because the type of device they are installed in is not identified, and the same SNMP addresses (OIDs) are used to represent different things.   DCE cannot automatically choose the correct DDF for devices with pCOWeb network cards.   If you only have one DDF installed to support devices that use the pCOWeb card, it's not a problem.   If you need multiple DDFs to support devices that use the pCOWeb card, you must configure the card to provide identifying information and modify the DDF to look for that information.   To configure the pCOWeb card:   Follow the instructions on page 35 of the pCOWeb User Manual to change the value of the system name at OID 1.3.6.1.2.1.1.5. The name should identify the DDF to use, for example, amico_leonardo_ug40mp40.   To modify the DDF:   Open the DDF in a text editor and find this line (note that the xxxxxx will vary between DDFs: <oidMustExist ruleid="xxxxxx" oid=".1.3.6.1.4.1.9839.2.1" istree="yes" /> Insert the following lines immediate after the line above, but replace xxxxxx with the name you created in the first step:            <oidMustMatch ruleid="sysname" oid=".1.3.6.1.2.1.1.5.0">                  <valueList>                          <value>xxxxxx</value>                  </valueList>           </oidMustMatch>