Professional Documents
Culture Documents
Eaton IPM Infrastructure v1.4.0 User Guide 20180719
Eaton IPM Infrastructure v1.4.0 User Guide 20180719
User guide
Rev 1.4.0-v01 07/19/2018
1 Class A EMC Statements
1.2 ICES-003
This Class A Interference Causing Equipment meets all requirements of the Canadian Interference
Causing Equipment Regulations ICES-003.
Cet appareil numérique de la classe A respecte toutes les exigences du Reglement sur le matériel
brouilleur du Canada.
1.3 EN 62040-2
Some configurations are classified under EN 62040-2 as “Class-A UPS for Unrestricted Sales Distribution.”
For these configurations, the following applies:
1.3.1 WARNING
This is a Class A-UPS Product. In a domestic environment, this product may cause radio
interference, in which case the user may be required to take additional measures.
2 Requesting a Declaration of Conformity
Units that are labeled with a CE mark comply with the following harmonized standards and EU directives:
• Harmonized Standards: IEC 61000-3-12
• EU Directives:
73/23/EEC, Council Directive on equipment designed for use within certain voltage limits
93/68/EEC, Amending Directive 73/23/EEC 89/336/EEC, Council Directive relating to
electromagnetic compatibility
92/31/EEC, Amending Directive 89/336/EEC relating to EMC
The EC Declaration of Conformity is available upon request for products with a CE mark.
-----------------------------------------------------------------------------------------------------------------------------------------------
CAUTION: REFER TO OPERATOR'S MANUAL - Refer to your operator's manual for additional
information, such as important operating and maintenance instructions.
-----------------------------------------------------------------------------------------------------------------------------------------------
This symbol indicates that you should not discard the UPS or the UPS batteries in the trash. This product
contains sealed, lead-acid batteries and must be disposed of properly. For more information, contact your
local recycling/reuse or hazardous waste center.
-----------------------------------------------------------------------------------------------------------------------------------------------
This symbol indicates that you should not discard waste electrical or electronic equipment (WEEE) in the
trash. For proper disposal, contact your local recycling/reuse or hazardous waste center.
Eaton is a registered trademark of Eaton Corporation or its subsidiaries and affiliates.
National Electrical Code and NEC are registered trademarks of National Fire Protection Association, Inc.
Microsoft®, Windows®, and Windows Server® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.
No part of this document may be reproduced in any way without the express written approval of Eaton Corporation.
4 Table of Contents
6 Contextual Help 48
6.1 Dashboard View .................................................................................................................................. 48
6.2 Power Chain View ............................................................................................................................... 48
6.3 Rack View............................................................................................................................................ 49
6.4 UPS View ............................................................................................................................................ 54
6.5 Environmental View............................................................................................................................. 55
6.6 Alarms View......................................................................................................................................... 56
6.7 Asset Management View..................................................................................................................... 57
6.7.1 Main actions ...................................................................................................................................... 58
6.7.1.1 Auto Discovery .................................................................................................................................58
6.7.1.2 Upload CSV file ................................................................................................................................60
6.7.1.3 Add New Asset .................................................................................................................................60
6.7.1.4 Export Assets ...................................................................................................................................62
6.7.1.5 Delete Asset .....................................................................................................................................62
6.7.2 Asset list statistics and report............................................................................................................ 63
6.7.2.1 Asset List ..........................................................................................................................................63
6.8 Setting Views....................................................................................................................................... 64
6.8.1 Account view ..................................................................................................................................... 64
6.8.2 Alarms settings view.......................................................................................................................... 64
6.8.2.1 Data Center Alarm Settings..............................................................................................................65
6.8.2.2 UPS Alarm Settings..........................................................................................................................66
6.8.2.3 Row Alarm Settings ..........................................................................................................................67
6.8.2.4 Rack Alarm Settings .........................................................................................................................68
6.8.2.5 PDU Alarm Settings..........................................................................................................................68
6.8.3 Date & time........................................................................................................................................ 68
6.8.4 Datacenter Layout ............................................................................................................................. 69
6.8.5 License .............................................................................................................................................. 70
6.8.6 Monitoring.......................................................................................................................................... 70
6.8.7 Network settings view........................................................................................................................ 71
6.8.8 Notifications....................................................................................................................................... 71
6.8.9 Users View ........................................................................................................................................ 72
6.9 Feedback Tool ..................................................................................................................................... 72
6.10 Login page........................................................................................................................................... 73
6.11 Status dashboard ................................................................................................................................ 74
7 Troubleshooting 75
7.1 Factory Reset ...................................................................................................................................... 75
7.2 Send debug information through the feedback tool ............................................................................ 75
7.3 Using the diagnostic tool ..................................................................................................................... 75
7.3.1 Examples of usage:........................................................................................................................... 76
7.4 Using the Service port ......................................................................................................................... 76
5 General information
Login Wizard
After installing the unit in a rack and navigating to its assigned IP address, you should first accept the
untrusted certificate warning in your browser which is due to a self signed certificate being present by default
in the device.
After doing so, you are presented with the following login page:
As you are logging into the IPM Infra for the first time, you must enter the factory default username and
password which are set to:
Username = admin
Password = admin
As can be seen in the image below, the password details are obscured from view so please ensure to enter
the password carefully and correctly.
At first login, the system requires that you change the default admin password.
• The user is presented with the message shown below requesting the current admin password
("admin") and the new password.
• Follow the password format recommendations on the tooltip in order to define a secure password;
• A secure password is mandatory.
• Click "Continue"
After changing the password, the user is presented with the License Agreement.
Please read it and accept it to continue.
Please refer to the Legal Information below for more information.
On the next page, the user is presented with is the network configuration settings.
The user must confirm the network configuration settings are correct. If no changes are necessary, the user
may proceed to the next step, by clicking on Continue.
NOTE If changes are made on the network configuration page, the user will be automatically logged
out when all the steps of the wizard are complete in order to restart the network services.
At this stage the user must enter the details related to their site.
Please note that fields highlighted with "*" are mandatory and that the system has a pre-defined asset
hierarchy (DC -> Rooms -> Rows -> Racks -> devices).
The user can also configure SMTP settings and test his connection.
On the following step the user is able to create the Data Center Layout.
The user may specify its data center topology including the number of Rooms, Rows and Racks present in
the Data Center.
The default Rack U size is 42. It can be modified in the Asset menu (see Asset Edit menu for more details).
On this tool the user will find that for every Room created, a Row and Rack are also created automatically.
NOTE The data center layout can be updated later on from the Settings page.
At this stage, the user is now prompted for a license key. As mentinoned on the associated screen, the
license key can be entered later as the software comes with a 7 days of intial trial.
NOTE If network parameters have been changed, the user will be automatically logged out after this
screen and will be required to login to start a new session.
Finally, the user is presented the Data Center assets management page.
There are different tools available to setup the infrastructure of the data center and define your assets:
1. CSV file import . This is an advanced configuration tool which will allow you to create your data
center's topology freely but can lead to configuration issues if misused. It is not advised to use it at
first time if you don't have already a correct CSV file or help from an experienced service consultant.
2. Graphical tool for topology configuration. This tool is available in the Datacenter Layout tab of the
settings page. This will allow you to easily create your data center's topology. It is the recommended
option to start with.
3. Once you have defined your Datacenter layout, you can
a. use the automatic discovery function to automatically import the power devices discoverable on
the local network into IPM Infrastucture assets data base
b. use the "Add new asset" function to manually define some additional assets you might need
5.2.1 Introduction
IPM Infrastructure offers to the user the capability of managing alerts.
An event can be defined as any detectable or discernible occurrence that has significance for the
management of the IT infrastructure or delivery of an IT service as well as the evaluation of the impact a
deviation might have on the infrastructure or service. Any event must be made visible to the user.
There are two types of alarm currently existing in the application:
• Alarms are generated at the IPM Infrastructure level, using the user defined or automatically imported
thresholds (see Setting Thresholds chapter for reference)
• Alarms acquired directly from the monitored power devices (ePDUs, UPS)
Independent on the alarm type, any alarm has a set of attributes and follows a specific lifecycle.
The severity types are predefined priority levels for alarms related to particular elements and systems within
the data center. All alarms need to be well defined and categorized depending on the impact caused to the
business. However incorrectly defining alarms, such as under-prescribing priority levels can have serious
consequences, not setting the appropriate priority level may result in a business impacting issue that is
costly to resolve at too late a stage.
Over-prescribing the priority level, can cost a company more in the long run, costs such as remote hands
work, overtime and call-out charges for on-call engineers.
Below are examples of how data center priority levels could be set:
• P1 (Priority 1): Absolute Highest Priority - Directly impacting business
• Any alarm related to the data center power chain that directly negatively impacts on
redundancy should always fall into this category
• Any alarm related to IT Network Connectivity that is directly negatively impacting business
should fall into this category
• Any alarm related to IT Systems that is directly negatively impacting business should also fall
into this category
• Any alarm related to main chillers, pumps, AHU (Air Handling Units) and CRAC (Computer
Room Air Conditioning) units that are directly impacting on the cooling of the data center and
will therefore directly impact the business
• Any alarm related to smoke alarms, fire alarms, fire suppression systems.
• Any alarm related to data center physical security systems.
• P2 (Priority 2): High Priority - Not yet impacting business but has potential to escalate quickly.
• Alarms related to the data center power chain that have potential to impact redundancy soon,
but are not yet at the business critical level.
• Alarms relating to IT Network Connectivity that has potential to become a business impacting
issue, but are not yet at the business critical level.
• Alarms related to IT Systems that has potential to become a business impacting issue soon,
but are not yet at the business critical level.
• Alarms related to main chillers, pumps, AHU (Air Handling Units) and CRAC (Computer Room
Air Conditioning) units that have potential to impact on the cooling of the data center soon, but
are not yet at the business critical level.
• P3 (Priority 3): Medium Priority - Not impacting business but could become critical in the short term
• Alarms related to the Data Center power chain that will not impact redundancy immediately, but
can negatively impact on performance, and have the potential to escalate into more serious
issues.
• Alarms relating to IT Network Connectivity that will not impact business immediately, but can
negatively impact on performance, and have the potential to escalate into more serious issues
• Alarms related to IT Systems that will not impact business immediately, but can negatively
impact on performance, and have the potential to escalate into more serious issues.
• Alarms related to main chillers, pumps, AHU (Air Handling Units) and CRAC (Computer Room
Air Conditioning) units that will not impact the cooling of the data center immediately, but can
negatively impact on performance, and have the potential to escalate into more serious issues.
• P4 (Priority 4): Low Priority - Not impacting business but could become critical in the long term if left
unaddressed.
• Alarms related to the Data Center power chain that will not impact redundancy immediately, but
can negatively impact on performance, and have the potential to escalate into more serious
issues if ignored long term.
• Alarms relating to IT Network Connectivity that will not impact business immediately but can
negatively impact on performance and have the potential to escalate into more serious issues if
ignored long term.
• Alarms related to IT Systems that will not impact business immediately but can negatively
impact on performance and have the potential to escalate into more serious issues if ignored
long term.
• Alarms related to main chillers, pumps, AHU (Air Handling Units) and CRAC (Computer Room
Air Conditioning) units that will not impact the cooling of the Data Center immediately, but can
negatively impact on performance and have the potential to escalate into more serious issues if
ignored long term.
• P5 (Priority 5): Minimal Priority - Not impacting business but worth taking note of to be resolved in
futures service/maintenance intervals.
• Alarms related to the Data Center power chain that are not impacting performance in any way,
but will need to be resolved during maintenance periods.
• Alarms relating to IT Network Connectivity that will not impact business or performance, but will
require resolution during prescribed downtime/maintenance periods
• Alarms related to IT Systems that will not impact business or performance, but will require
resolution during prescribed downtime/maintenance periods.
• Alarms related to main chillers, pumps, AHU (Air Handling Units) and CRAC (Computer Room
Air Conditioning) units that will not impact the cooling of the Data Center or its performance but
will require resolution during prescribed downtime/maintenance periods.
In IPM Infra, the user can define such priority levels for each asset existing in the application. All
alarms related to any asset will inherit the priority level of the asset and they will be treated accordingly.
NOTE
Once the alarm is acknowledged into any of the states listed, it cannot be unacknowledged. An
Acknowledged alarm can only be changed to another state of acknowledgement.
If an alarm occurs on the system and is not acknowledged, the notification must be resent until the alarm is
acknowledged into one of the states listed above.
Simplified Alarm Retry Table
critical p1 5 min
p2 15 min
p3
p4
p5
warning p1 1h
p2 4h
p3
p4
p5
info p1 8h
p2 24h
If you have not already completed your CSV file in advance of the IPM Infra installation and you want to
continue with asset configuration through CSV, you can simply export a copy of the CSV with all the
information filled during the wizard steps. To do this just click on "Export Assets"
All the remaining details relating to the devices installed in the Data Center must be entered into the CSV
file. Please check the dedicated documentation about the CSV creation tool. This tool enables the user to
complete the CSV file in a step-by-step manner and explains the relationship between the devices recorded.
Once the CSV file is created it will look like the populated sample displayed below.
When you are done or if you already have a CSV file, you can upload it clicking on the "Choose File" button
which will open a file browser in order to select your CSV file. Then click on "Upload" to import it in the
system.
While the upload is being processed a dial indicates the progress of the activity.
In case of upload errors, they are returned to the user, specifying at which line the error occurred and some
details about it;.
In case only some CSV lines will be imported successfully, the message returned to the end user after the
import will detail the import errors.
If the file upload is successful the user is given confirmation of the activity performed.
Import Errors
Load csv was success, but error occurred during configuration sending of asset change 42
42 notification. Consult system log.
Request document has invalid syntax. Cannot detect the delimiter, use comma (,), 48
semicolon (;) or tabulator.
To view and scroll through the Asset Management page just click on the "Close" button, this will allow the
user to interact with the Asset Management page.
The details submitted via CSV upload can now be viewed on the Asset Management page in a simplified
spreadsheet format.
You can edit the data center assets using the CSV file as follows:
1. Press the "Export Assets" button
2. Update the downloaded CSV file
3. Re-upload the CSV file using the "Upload CSV File" button.
NOTE
In version 1.0.0, the data center objet may not be deleted from the UI.
Asset creation
All asset management operations are available in the Asset Management page.
From the Dashboard, the user can access the page from the top menu Asset management. All possible
operations on assets are accessible through the page menu:
In order to create a new asset, the user must use the button "Add New Asset". A pop up window will appear
in order to introduce the basic asset information.
Before proceeding with adding assets to your system, please consider the below comments:
1. Create the appropriate Input Power topology of your data center. See the different recommended
topologies available in the Appendix 1.
There is a specific Power Chain in our system called "Input Power Chain". These are the power
devices (Feed, Genset, stand-alone UPS) which provide power to your Data center. In order to define
a device as being part of the Input Power Chain, you need to set its location as "data center".
2. After defining the input power chain of the data center, we recommend to proceed to the creation of all
rack mounted power devices (rack mounted UPS, rack PDUs) in order to complete the power chain
down to the rack device level.
3. For adding sensors to the asset list, there is a dedicated "Sensor" Section in this User Guide.
4. For adding daisy chained rack PDUs to the asset list Refer to Chapter 2, “ePDU G3 Daisy Chaining”
on1 page 18.2
5. For the Eaton power devices communication with the IPC3000, the user has to enable SNMP v1
protocol from the Web interface of the ePDU. This is mandatory in order to get all data. Please don't
forget to add SNMP v1 community in the Settings page if the ePDU community name is different than
"public".
1
file:///C:/Users/C9903574/Downloads/P-164000637_Eaton%20%20Intelligent%20Power%20Manager%20(IPM)
%20Infrastructure%20Initial%20Login%20and%20Operation%20User%20Guide_May%20Edit.docx#page24
2
file:///C:/Users/C9903574/Downloads/P-164000637_Eaton%20%20Intelligent%20Power%20Manager%20(IPM)
%20Infrastructure%20Initial%20Login%20and%20Operation%20User%20Guide_May%20Edit.docx#page24
NOTE
Make sure you define the power source of your assets in order to get measured data in the User
Interface.
Some of the fields from the section "Other Information" are used for display purposes or for building location
or power chain topologies.
Once all the information has been input, the user presses Add and the device will appear in the Asset list.
A pop up window containing all existing asset information will appear and the user will be able to edit the
editable fields (there can be non-editable fields, visible in grey, eg: Name).
NOTE
You will need to create the device where the EMP001 will be plugged before creating the sensor
itself. If you want to plug the sensor on your IPC3000, it has been created automatically when you
first connected to the graphical user interface. In case it would have been deleted, you can recreate
it by adding a new asset of subtype "Rack Controller" which will represent the IPC3000.
TH1 9
TH2 10
TH3 11
TH4 12
Any sensor is mounted physically in a rack, therefore the user must specify the rack. He can do it through
the field "Logical asset". Once assigned to a rack, the values returned by the sensor will be used for
computing the average temperature and humidity for that specific rack.
The temperature and humidity values for rows are computed as averages of values of racks contained in the
row, averages being propagated to the DC level.
IMPORTANT NOTE
As for the ePDU in Single mode, the user has to enable SNMP v1 protocol from the Web interface of the
ePDU. This is mandatory to get data from the ePDUs. Don't forget to add SNMP v1 community in the
Settings menu if the ePDU community name is different than "public".
On the IPC side, the user has to create a new ePDU asset with the type "EPDU", fill all mandatory fields.
This operation has to be done for all ePDUs in Daisy Chain configuration (Host and all devices connected to
the host).
NOTE
The user has to check that the configuration defined in the rack is matching the configuration defined on
the ePDU power Chain topology, see table below:
0 (Host) 1 - Host
1 (Device) 2
2 (Device) 3
3 (Device) 4
4 (Device) 5
5 (Device) 6
6 (Device) 7
7 (Device) 8
Main Administrator
By default on the first install of IPM infra, two user accounts are created : "admin" and
"monitor". (see default password below)
The "admin" account will be automatically defined as Main administrator account. it means,
this account is not editable by others user account with administrator profile.
The first connection is only possible with the "admin" account created by default. The
password change will be requested on first connection.
Default passwords:
Login Password
admin admin
Monitor monitor
Both users can change the password from the Settings page, in the Preferences section.
NOTE
It is strongly recommended to change the default passwords.
NOTE
Password strength requirements include:
• Minimum of 8 characters
• At least 1 special character
• At least 1 digit
Only user with an admin profile have permission to access to this settings menu.
• or enter manually : user has to create the password, taking care to respect the parameters defined in
password strength
First connection
If checkbox "force password" is selected. The new user will have to change his password on first
connexon. By default, this option is activated
Password confirmation
When a password is created or edited (reset) on a user account, the user logged on must confirm
his own password to validate the creation / modification.
Example : to finalize the user account creation, Administrator has to enter his own password. "save"
button will be available then. Same behaviour when administrator want to reset a user account
password.
First connection
The password change is requested on first connection of the user account :
Edit User accounts
Administrator profiles
Users with administrator profile have permission to edit their own account, but also the others user accounts
by clicking on the pencil icon :
A modal box will display : "edit user". All account details are editable. It's also possible to reset account
password.
Main Administrator
The main administrator account is not editable by others users.
Change Password
From the account settings menu, user logged-on can modify his password, and his account details
information :
Password Strength
It's possible to define the complexity of the password, but not Mandatory. By default the minimum length is 6
characters with no specific format.
User has to save to take into account modifications.
The password change will be requested once the password expiration delay is reached. On "change
password" modal box, a tooltip will retrieve format expected.
5.5 Licensing
IPM Infrastructure Software comes with one week of initial trial embedded.
You can start configuring your software and commission your assets just after the initial deployment and
prior the activation of any additional license.
Note
Please note that after one week, the access to the software will be blocked and that an activation ID
will be required to connect to the software again.
During these first days a yellow notification bar will appear on top of all the screens telling you how many
days are left for this initial trial mode.
During this phase you can submit a license key to activate the software on a longer basis.
To do so, click on "Activate your license" in the notification bar.
This points you to the "License" tab of the Settings page. The current status of the License is always
available here.
In the above screen, we see can that the trial period is about expire and what we are still entitled to.
At the bottom of this licensing information panel, you can click on the action button to activate a new license.
This points you to the license activation wizard.
Note
To get access to online activation, the configuration of the proxy address to be used to access to
internet from your local network can be needed. Refer to the network settings tab described in the
contextual help chapter of this document to understand how to set this up.
The above screen shows the situation where IPM Infrastructure is not connected to the internet.
As a consequence, a notification is displayed telling that Online activation is not available.
Type (or paste) your Activation ID in the corresponding input field and click "Next" to start a manual
activation.
a. Click on "Choose File" and select the capability request you generated at step 1
b. Click on "Upload". You should be notified of the license generation success.
c. Click on the link in the notification ribbon to download the generated license. This will download
a file named "capabilityResponse.bin"
You can now close this tab and get back to IPM Infrastructure tab in your browser.
3. Step 3 consists in importing the capability response file into your software.
a. Click on "Choose File" button
b. Select the capability response generated at step 2.
c. Click on "Import"
You should be notified about the software activation success. Congratulations!
NOTE
The product embeds a tool that can be used to extract information from devices that are not yet
supported.This tool can be used through Secure Shell (SSH) connection.
1. Connect to your IPM Infrastructure using SSH, using the "admin" account
2. Run " fty-device-scan <IP address of the device> <your email address>"
Example: fty-device-scan 192.168.0.10 john.doe@organization.com3
3. Send the archive received by mail to EatonProductFeedback@eaton.com4.
If possible, provide as much information on the device as possible in your mail, such as:
• Mentioning the type of device, exact manufacturer and model names
• Attaching the MIBs related to the device, or pointing the online versions, if available
• Any other information that you may find suitable.
Information and directions will be provided back to you shortly by mail to add support for your device.
2. Minimal resilience configuration with 1 main feed and 1 UPS protecting the infrastructure.
3. Minimal resilience configuration with 1 main, 1 GenSet, 1 ATS and a rack mounted UPS (instead of a
standalone UPS) installed in the white space with the IT devices.
4. Minimal resilience configuration with 2 main feeds (Utility A & Utility B), an ATS and a rack mounted
UPS (instead of
3
mailto:john.doe@organization.com
4
mailto:EatonProductFeedback@eaton.com
5. N configuration (Tier I) with 1 main, 1 GenSet, 1 standalone UPS installed in the grey space.
6. N configuration (Tier I) with 2 main (Utility A & Utility B), 1 ATS and 1 standalone UPS installed in the
grey space.
7. N+1 (Tier II) Smart grid Configuration: 1 Mains, 2 Gen Sets for additional redundancy, and 2 UPS.
8. N+1 (Tier II) Smart grid Configuration: 2 Mains (Utility A & Utility B), 1 Gen Set for additional
redundancy, and 2 UPS.
Step 1: connect to IPC as admin and generate a Certificate Signing Request (CSR)
# login as admin
:; ssh admin@eaton-rc-002085ec0072
# generate a new private key and a the CSR
:; openssl req -new -newkey rsa:2048 -nodes -sha256 \
> -keyout bios2048.key -out bios2048.csr
Generating a 2048 bit RSA private key
.........+++
................................+++
writing new private key to 'bios2048.key'
-----
You are about to be asked to enter information that will be incorporated into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:FR
State or Province Name (full name) [Some-State]: France
Locality Name (eg, city) []:Montbonnot
Organization Name (eg, company) [Internet Widgits Pty Ltd]: Eaton
Organizational Unit Name (eg, section) []:Eaton Industrie France
Common Name (e.g. server FQDN or YOUR name) []:eaton-rc-002085ec0072
Email Address []:johndoe@eaton.com5
Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
5
http://eaton.com
Step 2: After successful generation of the keys and CSR, you should transfer the
bios2048.csr file created above to your Microsoft CA system. Then submit the CSR for
signing and the save the new fresh signed certificate.
# login as admin into Microsoft CA
:; certreq -submit -attrib "CertificateTemplate:WebServer" bios2048.csr
This command should produce output similar to the following:
Active Directory Enrollment Policy
{922335A5-82E4-4179-8E98-4DF7EEAFDE18}
ldap:
RequestId: 8
RequestId: "8"
Certificate retrieved(Issued) Issued
Save the certificate as bios2048.crt
Step 4: Export your root certificate and install it on the PCs client.
# login as admin into Microsoft CA
:; certutil -ca.cert ca_name.cer
• Reset button.
• 4 Status LEDs.
Memory and CPU • 1 mSATA port for SSD (SSD not included, see SSD mounting
instructions in this manual).
• IP based (RJ45)
Standards • CISPR 22
• CISPR 24
• IEC 60950-1
• EN 55022
• EN 55024
• EN 60950-1
• RoHS
• REACH
• WEEE
Front panel:
• 4 Status LEDs, power, heart-beat (system clock), serial communication and network connection. Only
power & heart-beat is active in this version.
PIN SIGNAL
1 CTS
2 DCD
3 RXD
4 GND
5 DSR
6 TXD
7 DTR
8 RTS
• 4 Serial RS-232 ports with RJ45 connector. Used as environmental ports, to connect EATON's
temperature and humidity sensor (EMP001). See pinout below:
PIN SIGNAL
1 RTS
2 TXD
3 DTR
4 GND
5 RXD
6 CTS
7 DSR
8 DCD
• 4 SW selectable RS-485 (Modbus compatible) / RS-232 ports with RJ45 connectors are able to
provide 12V/0.5A distributed between the 4 ports. These ports are compatible with the next generation
of temperature and humidity sensors from EATON. See pinout below:
1 TXD TX+
2 RTS TX-
3 DTR ---
4 RXD RX-
5 CTS RX+
6 DCD ---
7 12V 12V
8 GND GND
• DB9 service only port.
• 4 USB 2.0 ports, one of them (USB 1) with powering capabilities (5V/2A).
• 2 redundant LAN ports (3x10/100/1000 RJ45) with independent MAC address. MAC address
indicated in the product label corresponds to LAN1.
Back Panel:
• Dual internal independent power supplies with dual universal socket 110-240VAC 50/60Hz. System
power consumption less is than 20W.
• Erase button, soft reset (reboot) the system by pressing the button for more than 1 second and factory
reset the system when pressing the button for more than 5 seconds
• 3rd LAN port (3x10/100/1000 RJ45). This port allows extra connectivity, i.e. by connecting a switch to
connect appliances (ePDUs).
• 1 x 12V / 1.8A fused output relays which allows you to power external devices (first two connections +
and - starting on the left side of the connector).
• 4 x 12V / 500mA fused output relays which allows you to power external devices.
• 10 dry contact inputs which enable you to connect various dry contact sensors such as a water leak
detection sensor, door contact sensor, smoke detector, etc.
• embedded into IPC3000 rack controllers units as before
• as a Virtual Appliance.
The VIrtual Appliance can be deployed on your virtualization platform and consists in a virtual machine
hosting an OS and all required applicative modules IPM Infrastructure is made of.
The Virtual Appliance is pakaged as an OVA file. This format is supported by several virtualization platforms
but Eaton only support deployments done in a VMware context (other ones have not been tested).
5.11 Cybersecurity
At Eaton we are focusing on analyzing emerging threats and ensuring that we are developing secure
products and helping our customers deploy and maintain our solutions in a secure environment. We continue
to evaluate cybersecurity updates that we become aware off and provide the necessary communication on
our website as soon as possible.
Eaton strongly recommends our customers to apply the deployment practices that are outlined on our
Cybersecurity white paper "Cybersecurity considerations for electrical distribution systems" accessible on the
Eaton website :
Cybersecurity considerations for electrical distribution systems6
6
http://www.eaton.com/ecm/idcplg?
IdcService=GET_FILE&allowInterrupt=1&RevisionSelectionMethod=LatestReleased&Rendition=Primary&dDocName=
WP152002EN
6 Contextual Help
The purpose of this page is to give a general snapshot of the health of the Data Center via key metrics.
This includes real-time data and trends over 24 hours, 1 week and 1 month periods for Power and
Environmental metrics.
The leftmost Power gauge provides the user with a view of the total power usage of their Data Center,
allowing them to quickly see and understand the current status of their power.
The Temperature and Humidity gauges enable the user to view the current environmental status of their Data
Center, providing an aggregated value for probes deployed within their site.
The top right Active Alerts panel provides the user with visibility of the most recent active alerts occurring
within their Data Center along with timestamps and a brief description of the issue impacting a particular
device.
The bottom right panel displays a Data Center uptime KPI based on the main feed to the UPS. It is a quick
way to understand the stability of the power in the data center.
Here the user is presented with a simplified line diagram of their power chain. They are also shown a graph
of the total power consumption of their Data Center over the last 24 hours, 1 week and 1 month. A custom
date range may also be entered manually. Active alarms are also shown on this page ensuring the user will
not miss any new alarms that might occur.
If the UPS present is a 3-phase UPS, the user is also able to select a high level overview of the phase
balance.
A list of posible configurations for the input power infrastructure can be found in Supported Power Chain
Topologies.
The user is able to see detailed information for this rack including total rack power, percentage of load
balance between both rack ePDUs, load levels on each rack ePDU. They may also view the power usage
graphs over 24 hours, 7 days and 1 month periods. The user can also see the most recent alerts.
The top banner of the rack view clearly indicates the power source of each feed (UPS, Mains).
The system can display which outlet of a racj PDU a device is connected to , along with the state of each of
the outlets.
The Question Mark icon on the top right of the Rack topology is a reminder of the outlet colour legend:
• GREEN = Management on & device connected and within threshold
• YELLOW = Management on & device connected and above warning threshold
• RED = Management on & device connected and above critical threshold
• WHITE = Management on & no device connected
• GREY = Management off
• Grey with strike-through = Communication lost or belongs to non-intelligent PDU
When the user performs a mouse-over on one of the outlets, the device supplied is displayed with a Bold
rectanglular highlight. If there is another outlet supplying the device, that (those) outlet(s) is (are) also
displayed in bold.
When the user performs a mouse-over on a rack mounted IT device in the view, a popup appears with the
name of the device, the name of the power supplies and the outlet number if the device is power supplied by
a PDU, as well as the total power consumed by the device from all outlets. Both device and outlets are
displayed surrounded by a Bold rectanglular highlight.
PDU sections are represented with their name in a colored rectangle and Eaton G3 ePDUs are represented
in the rack view with the same colors as those applied to the HW unit itself making it easy to quickly identify
the relevant section and outlet.
The user can mouse-over on the top of colored rectangle identifiying each section. When doing so, each
device powered by the selected section's outlets is displayed with a bold surrounding rectangle.
A tooltip is also displayed with the group name of the section, the phase powering the section and the
instananeous values of the active power, current and load % of the section.
A feed identifier is displayed above each of the rack PDU gauges. When available from the rack PDU, the
feed color and name are automatically displayed.
The user can also obtain greater details related to each of the rack PDUs installed. They can do this by
simply clicking on the "Details" button. Details such as serial number, installation date, warranty expiration
date, etc are provided.
Here the user can view more detailed measurements such as the status of the UPS, Voltage, Load and
Internal Temperature, while still maintaining an overview of the total critical power and active alerts. By
clicking on the "Details" button the user is presented with further details related to the UPS such as IP
address serial number, location etc.
Alternatively, the user may click on the IP Address link which will take them directly to the UPS own web
interface.
Returning to the Power View page, the user can see the power consumption per rack installed.
Similar to the layout of the power view page, the user can see the readings taken directly form sensor
installed in the suggested location (front of rack). The user can change the selected view by selecting the
grid format view on the top right of the temperature and humidity display. See below image for details.
On the right hand side of the page the user is presented with a snap shot of their current and most recent
alerts. The user can also view the historical graphing related to either temperature or humidity over the last
24hrs, 7 days or 30 days.
Alarms can be placed in several possible states allowing the user to take appropriate action when treating an
incident. All alarm states can be filtered by use of the search function at the top of the page. Refer to Alarms
Management (see page 14) 7for more detailed information.
At all times the user as visibility of any issues that might be occurring with this device via the alarm icon
displayed beside the asset's name.
7
file:///C:/Users/C9903574/Downloads/P-164000637_Eaton%20%20Intelligent%20Power%20Manager%20(IPM)
%20Infrastructure%20Initial%20Login%20and%20Operation%20User%20Guide_May%20Edit.docx#page45
Auto Discovery
This button allows the user to perform a scan of the network to discover connected assets and to add
them automatically to the asset list. The devices elligible to the discovery are of following types:
• Uninteruptible Power Supply (UPS)
• Power Device Unit (PDU)
• Automatic/Static Transfer Switch (ATS/STS)
Once the Auto Discovery button is pressed, the user is prompted with the Auto Discovery Settings dialog.
Three methods are available to control the scope of the discovery process over the network. The user can
choose the desired method by clicking on the corresponding tab. Then, (optional) settings can be entered.
Pressing the "Start" button will launch the configured automatic discovery process. One can press the cancel
button at any time to go back to the asset management view without starting the discovery.
Auto mode
In this mode, there is no additional setting. The scan will apply to all local network IP addresses.
IP Ranges mode
In this mode, the user can enter one (or multiple) IP adresses range(s).
These range(s) are either defined:
• as a contiguous list of IP adresses defined by the first and the last ones.
• as a set of addresses defined by a base IP address and a netmask
The scan will be processed over all the IP addresses included in the ranges defined by the user.
Select IP mode
In this mode, the user can enter one (or multiple) indivual IP adress(es) to be scanned.
The scan will only be performed on the individual IP addresses entered by the user.
Based on the selected asset type, additional fields with other information will appear where the user can
input extra device information (e.g. for ePDU below).
NOTE
Make sure you define the power source of your assets in order to get measured data in the User
Interface.
Some of the fields from the section "Other Information" are used for display purposes or for building location
or power chain topologies.
Once all the information has been input, the user presses Add and the device will appear in the Asset list.
Export Assets
This button generates a CSV file that contain the description of all the known assets.
This file will be usable to restore the asset list later if needed (see "Upload CSV file" above).
Delete Asset
This button is active only if, at least, one asset is selected.
When active and pressed, this button deletes all the selected assets from the list.
Depending on the way each asset has been added, its power source and location in the data center might
not be set. These two informations are mandatory for the asset to be monitored by IPM Infrastructure. In
such a situation, a red alert message (displayed below the indicator of the number of assets) will point user's
attention to the need to complete the setup. The provided link uses filtering capability of the asset list (see
below about Asset List) to focus on the assets that need further configuration to be correctely monitored by
IPM Infrastructure.
Asset List
The main content of the asset management view is the asset list itself.
This list can be managed through the icons on the top right of the list:
• the funnel icon enables the user to focus on some particular assets by filtering the list.
The navigation between pages is available at the bottom of the list along with the confiuration of the number
of items displayed per page.
NOTE
Setting multiple alarms to set a same output contact will work as expected mostly when the
corresponding alarms are all mutually exclusive.
If multiple alarms are:
• configured to set the same output contact to ON,
• raised at the same time
The output contact will be set to OFF as soon as a first alarm is resolved no matter the status of the
other ones.
Any data center must have at minimum a room containing a row with a rack inside.
Additional rooms, rows and racks can be defined. None of the existing assets can be edit in this page, but
only completely removed.
For all the new assets added, the user can change the standard name before the configuration is saved.
Once saved, no edit operation will be possible from this page.
Once the full layout has been defined by the user, he must press Save. All new assets are visible now in the
Asset management page.
NOTE
If the user wants to remove a Room, Row or Rack, all the devices configured in the appropriate area
have to be removed first.
6.8.5 License
License section displays the license status of your software.
IPM infrastructure comes with a one week initial trial License.
Other licenses can be purchased and need to be activated.
In any case, all information regarding what this software copy is entitled for and the expiration dates are
displayed here.
To activate a license, click on the action button. This will point you to the activation wizard detailed in the
Licensing section of the General Information chapter.
6.8.6 Monitoring
The user has the ability to add SNMP v1 & v2 community names.
By default, public community name is already configured in the software. All added community names have
only READ access.
6.8.8 Notifications
The Feedback tool allows you to communicate questions or comments directly to Eaton.
1. Select the radio button accordingly to feedback you are giving, if it's something relative to the all IPM
Infra, or specific to your current page.
2. In the "Comment" field, please try to describe all the details of the issue you want to report. Give us
any piece of information about the context you are using IPM Infra.
3. Give us the email to which we should reply.
4. Add a file that can complement your text description by clicking on "Choose File".
5. Click Send.
Both the admin and the monitor users can send feedback.
It is also possible to send an email to EATON support at this address: EatonProductFeedback@Eaton.com8
8
mailto:EatonProductFeedback@Eaton.com
7 Troubleshooting
CAUTION
A factory reset will put the device in its initial factory state. All monitored data, configuration
settings and password will be removed.
To do a factory reset of the device, press the reset button from the back panel for at least 10 seconds.
NOTE
Please consider that the feedback tool supports as attachment only one file with a maximum size of
1MB.
Access to the product logs. The user can download the SW logs and send them to the Eaton representative
if requested. The logs can be downloaded from the Settings page.
IPM Infra User Guide Rev 1.4.0-v01 07/19/2018 Troubleshooting - 75
Using the Service port
Consider that creating the archive can take some time and it can be longer if there are coredumps in /var/
crash.
Consider that there is no feedback to user that collecting of information is finished. Use some USB stick with
LED activity signalization might help and is, therefore, recommended.
2. Run the tool and send the details to Eaton product support.
76 - Troubleshooting IPM Infra User Guide Rev 1.4.0-v01 07/19/2018