Intelligent Power Manager (IPM) FAQ

Any network-connected UPS, compatible with NUT (Network UPS Tools) acquisition engine, will communicate with IPM. IPM treats them the same as a premium Eaton UPS, and the user gets whatever functions are available in the IPM edition they are using:

• IPM Monitor can monitor UPSs that are NUT compatible.
• IPM Manage use the NUT compatible UPSs as a power source to trigger host power actions.
• IPM Optimize will use NUT compatible UPSs as a power source to trigger VM power actions and cluster actions.

• On the IPM OVA, you can access the vCenter remote console or connect via SSH using the OVA’s IP address.
• If you can access the network, you can start an SSH connection. Try to connect on the port 22 (standard SSH port). 
• You can log into the system using your credentials.

• When you can’t identify the root cause of an issue, a factory reset may fix most problems, but the customer will lose all of their data (including all the commissioned data such as the data center topology, devices, etc.).
• Before performing a factory reset, try to run the diagnostic tools. If it works, you should be able to save the CSV file containing the asset configuration.
• You can run the diagnostic tool with:
  • sudo diagnostic-information -m -t [your mail address] to send the data to your mailbox.
• In order to reset the OVA, launch the remote console via vCenter then log in with the customer credentials. Once in the system, launch the “exit” command and you should access the blue console menu screen. Select “Factory Reset and Reboot.”

• When you configure the network using DHCP, the software may not display the IP address obtained even though it is correctly configured.  If the DNS settings appear correctly, the IP address has also been configured.
• After the initial wizard network configuration, you need to restart the software in order for the new settings to be applied.
• When configuring the proxy settings through the initial wizard, please note that it must follow the syntax “http://myProxy@myDomain.com:portNumber”If DHCP is not available, you may configure the network settings from the vCenter console.

• If the system’s date seems to not be correctly updated despite a seemingly correct NTP configuration, check to see if the NTP server in question is a Windows server.   We have observed some incompatibility issues with some versions of Windows NTP servers. Try changing to another NTP server.
• Local time is synchronized to the physical host on which it is running.

• All the assets are editable in the asset management page.
• Alternatively, you may also use the CSV export/import feature.
• Export the CSV file using the Export button in the asset management page. Open the file, find your asset line, apply your change(s), delete all unnecessary lines and re-import the file. 

• When exporting a CSV file, it is created with an ‘id’ column. This column is used for enabling assets to be edited.  If you import a line with an id, the system will look for the corresponding asset and update it with all the column values.
• If you want to import a CSV file in order to create new assets (for instance, when you recover from a factory reset) you need to simply remove the ‘id’ column prior to the import.
• Keep in mind that this CSV file only contains asset configuration data. Other settings, e.g. credentials, need to be configured manually.

• There are two main reasons you may receive error messages when importing a CSV file:
  • You try to create an asset that already exists.
  • You try to modify an asset which is not commissioned yet.
• Keep in mind that the CSV import is a step by step process. The system will read the file line by line and, if in the line ‘n’ you use an asset defined in the line ‘n + x’, the import will fail.
• If a line produces an error during import, it is skipped and the CSV import continues.
• If you encounter an unexpected error during the CSV import, try to create or update the asset using the Create Asset feature from the Asset Management page.

If you are not seeing any data from an rack PDU, please check:

• That SNMP is enabled on the ePDU.
• The community name is correct with respect to the SNMP configuration selected in the security wallet.

• All credentials (monitoring, mass management & user scripts) are stored in an encrypted repository.  You associate credentials with a device from the asset management page by selecting one or more devices, clicking on Configure and then selecting the appropriate credentials from Security Wallet.
• Basic credentials are used for mass management while SNMP credentials are used for monitoring.

• The Max Duration Timeout enables you to set a timeout which applies to the entire automation sequence.  It can be adjusted from its default setting.
• Automations are executed in a sequential manner.  It is recommended to test your automation and verify its execution history in order to ensure that it is functioning as expected.
• Custom user defined scripts may be used as an action in an automation.  Python, BASH and PERL scripts are supported. 
• By default, new automations are inactive, don’t forget to activate the automation after creation.