Escolar Documentos
Profissional Documentos
Cultura Documentos
User’s Guide
Eaton, Intelligent Power Manager, ePDU, and Intelligent Power Protector are registered trademarks of Eaton
or its subsidiaries and affiliates. VMware is a registered trademark and VMCenter is a trademark of VMware,
Inc. Microsoft, Hyper-V, Windows Vista, Windows XP, and Internet Explorer are registered trademarks of
Microsoft Corporation in the United States and/or other countries. Citrix and Xen are registered trademarks of
Citrix Systems, Inc. Intel Core is a registered trademark of Intel Corporation. Ext JS is a registered trademark
of Sencha, Inc. SQLite is a registered trademark of Hipp, Wyrick & Company, Inc. OpenSSL is a registered
trademark of The OpenSSL Software Foundation Corporation, Inc. Google Chrome is a trademark of Google,
Inc. HyperTerminal is a registered trademark of Hilgraeve. Linux is a registered trademark of Linus Torvalds in
the United States, other countries, or both. Mozilla and Firefox are registered trademarks of the Mozilla
Foundation. National Electrical Code and NEC are registered trademarks of National Fire Protection
Association, Inc. Phillips is a registered trademark of Phillips Screw Company. All other trademarks are
property of their respective companies.
©Copyright 2015 Eaton, Raleigh NC, USA. All rights reserved. No part of this document may be reproduced in
any way without the express written approval of Eaton.
Class A EMC Statements
FCC Information
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to
part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates, uses
and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual,
may cause harmful interference to radio communications. Operation of this equipment in a residential area is
likely to cause harmful interference in which case the user will be required to correct the interference at his own
expense.
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 Règlement sur le matériel brouilleur du
Canada.
Eaton is not responsible for damage to this product resulting from accident, disaster, misuse, abuse, non-Eaton
modification of the product, or other events outside the reasonable control of Eaton or not arising under normal
operating conditions.
1F61
I.T.E.
Special Symbols
The following are examples of symbols used on the UPS or accessories to alert you to important information:
RISK OF ELECTRIC SHOCK - Observe the warning associated with the risk
of electric shock symbol.
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.
Table of Contents
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Eaton IPP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Performance Evaluations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Java Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
On the System Hosting Eaton IPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
On the System that Displays the Web-based GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
JRE Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
JRE Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Quick Start Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Graphical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
License Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installation Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Uninstalling the Eaton IPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Upgrading the Eaton IPM Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Installing/Uninstalling the Eaton IPM (Command Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configure Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Discover Nodes Connected on the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Quick Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Range Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Address Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Scan Settings for Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Change Driver Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configure Node Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configure User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Automatic Data Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuration Export/Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Action Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Create a New Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Edit Selected Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Action Type Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
E-mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
SSH Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Host Power Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
VM Power Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
VM Migrate Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
vApp Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Start a Recovery Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Storage Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Infrastructure Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Usage Sum-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Shutdown workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Remark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Event Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Object Selector Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Alarm Box Notification Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
System Tray Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Typical Use Cases Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Advanced Use Cases Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Advanced Events and Actions Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Advanced Sound Alarm Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5 SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Access to the Monitoring Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Local Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Node List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Flexible Panels View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Information Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Outlets Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Measures Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Environment Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Graph Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Synoptic Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Power Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Powered Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Events Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Statistics Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Power Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Subviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Defining Subviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Sharing Subviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Device Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Map View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Create a Customized Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Map Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Events Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
List Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Calendar Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Node Events List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Launching the Device Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Node List Export to CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6 SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Shutdown Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Shutdown Through Hibernate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Power Source View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Shutdown Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
7 ADVANCED MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Nodes Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Single Node Configuration Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Single Card Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Multiple Card Configurations Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Nodes Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Upload Device Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Upgrade Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
8 VIRTUALIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Eaton Solutions for VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Standalone Hypervisor and Local Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Multiple Hypervisor and Remote Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
VM and vApps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
VMware Site Recovery Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
VMware Load Shedding Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Eaton Solutions for Microsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Standalone Hypervisor and Local Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Multiple Hypervisor and Remote Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Eaton Solutions for Citrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Standalone Hypervisor and Local Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Multiple Hypervisor and Remote Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Eaton Solution for Red Hat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 iii
Table of Contents
9 REDUNDANCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Enabling Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Electrical Redundancy Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Configuring Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Redundancy Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Selection View in Node List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Composite Device in Power Source View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Redundancy Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Use Case #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Use Case #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Use Case #3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Use Case #4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Redundancy Advanced Behavior Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Redundancy Alarm Management with Four Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Protection Alarm Management with Four Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Redundancy Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
11 STORAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Enable the Infrastructure Connectors Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Create a Configuration Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
15 APPENDIX A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Create an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Create a Configuration Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Add a VMware vCenter Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Create a Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
VMware & VMHost Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
VMware & Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
VMware & VM Migrate on EMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Create Event from EMP Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Site Recovery Manager (SRM) with IPM 1.50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
VMware Documentation and Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
SRM Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Configure SRM Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Monitoring Events and SRM Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
VMware & VM Load Shedding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Result after a Power Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Site Recovery Manager (SRM) with EMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Example Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
l Discovery and supervision of power devices connected to the network including UPSs, ePDUs, automatic
transfer switches (ATSs) (for a complete list, click the Hardware and Software compatibility link at
http://pqsoftware.eaton.com)
l Supervision of the remote servers hosting the Eaton Intelligent Power Protector® (IPP) or Network
Shutdown Module V3 application
l Advanced management feature (mass configuration and mass upload) with the Network Management
Cards [Network-MS (example, 66102/103006826), Modbus-MS (example, 66103), and eNMC for ePDU G3]
l Local computer graceful shutdown through Network or local connectivity, such as USB or RS-232 por
l An agentless method for directly managing and controlling most virtualized infrastructure hypervisors
currently available including VMware® vCenter®, Microsoft® Hyper-V®, and Citrix® Xen® (for a complete list,
click the Hardware and Software compatibility link at http://pqsoftware.eaton.com)
l A powerful event manager able to launch alerts and/or corrective actions with customizable conditions
l A growing set of sophisticated actions to improve business continuity in industrial and IT environments
Compatibility
Eaton has tested the compatibility of the Eaton IPM with a comprehensive list of devices and applications (for
a complete list, click the Hardware and Software compatibility link at http://pqsoftware.eaton.com).
NOTE If a device doesn’t support the Quick Scan feature, it can be supervised if Address
Scan or Range Scan operations are performed. See “Discover Nodes Connected on
the Network” on page 14 for more information.
Performance Evaluations
To provide a performance evaluation, Eaton has tested the following configurations:
l 1000 nodes (including ~50 real), mainly Eaton IPMs, and some NSM and Network Management Card.
l Average CPU load: ~60%
l Memory load: 200 ~300MB
NOTE These tests have been performed on Windows Server Operating System. The
Windows 2003 or 2008 Operating Systems do not have the limitation of 10
simultaneous connections.
Network Ports
Table 1 lists the network ports used by the Eaton IPM.
Terms
This section provides related terms and definitions.
IP Address
When Transmission Control Protocol/Internet Protocol (TCP/IP) is installed on a computer, an Internet Protocol
(IP) address is assigned to the system. Each address is unique and is made up of four numbers, each between
0 and 255, such as 168.8.156.210.
The Secure Socket Layer (SSL) is a solution for securing transactions over the internet. SSL is a communication
protocol that authenticates the data exchanged, as well as ensuring its confidentiality and integrity. The protocol
uses a recognized encryption method, the RSA algorithm with a public key. SSL is built into Internet Web
browsers. The padlock in the bottom of your browser screen automatically displays if the server sending
information uses SSL.
TCP/IP is a family of network and communication protocols for the transport and network layers. Also known
as the Internet Protocol suite of network communication protocols.
Acknowledgements
The Eaton software development team is grateful to the following projects:
l Spider Monkey
l Ext JS®
l SQLite®
- The SQLite Project (http://www.sqlite.org) generously donated source code to the public domain that
helped us for this project.
l OpenSSL®
- This Eaton IPM product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http://www.openssl.org).
- This Eaton IPM product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
- This Eaton IPM product includes software written by Tim Hudson (tjh@cryptsoft.com).
l Lib USB
l Net SNMP
The full license version for each of these projects is available from Eaton IPM using the
Settings > System > About selection path.
Java Licensing
Eaton's advanced software (infra connector) uses the OSGI framework technology. All the constituent modules
of the new features (virtualization, storage, Cisco UCS) are based on OpenJDK (Open Java Development Kit,
which is a free and open source implementation of the Java Platform).
A Java Runtime Environment (JRE) must be installed on the target machine to use these features. This one can
be open source, such as OpenJRE, or business, such as Oracle.
! IMPORTANT
Acceptance of licenses, related to Java Runtime Environment, is the responsibility of the end user.
NOTE For a complete operating systems compatibility list, click the OS compatibility link
at http://pqsoftware.eaton.com.
Installation Prerequisites
This section provides installation prerequisites for the following:
l For better performances with multiple nodes, Eaton recommends a Microsoft® Windows Server® OS (that
does not have the limitation of 10 simultaneous network connections)
l To avoid network or serial port access conflicts, do not install the Eaton IPM on a machine that also hosts:
- Network management system, such as HP OpenView® or CA Unicenter®
- Eaton Intelligent Power Protector (IPP)
- Eaton Enterprise Power Manager
- Eaton Network Shutdown Module
- Network Management Proxy
- Eaton UPS Management Software
NOTE The Eaton UPS Management Software is a legacy Eaton software product for
managing UPSs. If you were using it previously, remove it before installing the new
Eaton IPM software.
l Google® Chrome™
l Mozilla Firefox®
l Microsoft® Internet Explorer® (IE) version 9 and later
NOTE For optimal performance, Google Chrome or Firefox is recommended. For good
performance, IE version 9 and later is recommended. IE6 performance is not
optimal.
JRE Prerequisites
For all features correlated to the infrastructure connector (such as VMware, UCS, NetApp), a Java Runtime
Environment (JRE) must be installed on the system hosting Eaton IPM (see “JRE Installation” on page 6).
JRE Installation
The installation of the JRE is Operating System platform-dependent. All new Eaton components have been
developed and tested for the Java version 1.7 or later. After installing the correct JRE, the IPM must be reloaded,
to take account this new environment.
Graphical Installation
To install the Eaton IPM:
1. On a computer with a Windows OS, run the Eaton Intelligent Power Manager package under an
administrator account. A Web browser displays the Eaton Intelligent Power Manager Installer Welcome
screen.
2. Observe the prompt and verify that the communication device is connected. Click Next (see Figure 2).
The Login screen displays.
3. Read the application description on the Login screen. Type the login and password and click Login (see
Figure 3).
Configuration
When started, the application automatically performs a discovery using the “Quick Scan” option:
l Using the “Quick Scan” operation, you will discover the following through broadcast: Network Management
Cards Network-MS (ex 66102/103006826) and Modbus-MS (ex 66103), PXGX2000, PXGXUPS,
ConnectUPS-BD, ConnectUPS-X, ConnectUPS-MS, Intelligent Power Protector, Network Shutdown Module
V3, Eaton G3 ePDU cards, HP UPS cards, monitored and managed HP PDU cards, Dell UPS card, or Lenovo
UPS cards, or IBM UPS card.
l Display the discovered nodes using Settings > Auto Discovery (see Figure 4).
l For the other nodes, perform the discovery based on IP address ranges using the “Range Scan” option.
Using “Range Scan” discovers the nodes that are outside of the network segment and nodes that are not
compatible with the “Quick Scan” feature.
l Refer to the Compatibility list to determine if your node supports the “Quick Scan” feature.
(Optional) To set the computer running Eaton IPM to shut down in the event of a power failure:
1. Select Settings > System. In the far right panel, select Edit modules settings. The Edit modules
settings dialog displays.
2. Select the Shutdown checkbox on the Edit modules settings dialog (see Figure 5). The Shutdown menu
selection displays in the Settings menu hierarchy list (see Figure 6).
License Code
The Eaton IPM monitors up to 10 power devices (including UPS Web Card, ePDU, or Eaton IPP Shutdown
Controller) without a license.
If there are more devices to be monitored or advanced features are desired, an appropriate license is needed.
The license can also be upgraded later without reinstallation.
Table 3 provides the differences between Basic mode (requires no license code) and Silver and Gold modes.
The Basic mode is free and does not require a Product Key reference. Only the “Silver” or “Gold” paid versions
require that you enter the product key as follows:
1. In the Settings > System path, double-click the System field set. Enter the license code in the Product
Key field. The license code is printed on the commercial CD booklet (inside the CD case) as follows:
l ref 66925 Eaton IPM Silver License
l ref 66926 Eaton IPM Gold License
NOTE Nodes that are not managed due to license limitation appear with this icon:
Operation
1. Use the Views > Node List menu item to supervise the current state of the compatible power devices
and applications.
2. Select a line in the list and the panels are updated with selected device information (see Figure 7).
l [Optional] If you have enabled the Shutdown module, the Views > Power Source menu item allows you to
supervise the current state of the UPS that powers the server running Eaton IPM. This menu is available
when you have enabled the Shutdown module in System > Settings > Edit Modules Settings.
l The Events > Event List view allows you to view the device events.
l The Management menu provides functions that allow you to mass configure and mass upgrade cards.
Installation Result
! IMPORTANT
If you install a new Eaton IPM release without uninstalling the old one, you will keep your database
and your product settings.
l At the end of the installation, the following shortcuts are created in the group Start > Programs > Eaton >
Intelligent Power Manager:
- Open Eaton Intelligent Power Manager: Starts the main Eaton IPM graphical interface
- Start Eaton Intelligent Power Manager: Starts the service
- Stop Eaton Intelligent Power Manager: Stops the service
- Uninstall Eaton Intelligent Power Manager: Uninstalls the program
l A service called “Eaton Intelligent Power Manager” is also created for the Database Acquisition Engine.
- This program continuously polls the status of Eaton devices and Applications connected on the network.
- This service automatically starts on machine boot-up.
- This service provides the Web Interface.
l A system tray icon displays the alarms on the local computer. Right-click this icon to display the same
shortcuts as in the Windows Start menu.
l Access the control panel selection for your operating system to uninstall programs and remove the Eaton
Intelligent Power Manager Vx.xx package per your system instructions.
l You can also uninstall from the shortcuts to remove the product and custom files (if you confirm the action):
Start > Programs > Eaton > Intelligent Power Manager> Uninstall Intelligent Power Manager.
Detail of available command options can be obtained using the following command:
<packageName> -help
<packageName> [COMMAND] [OPTION]...
-dir <installPath>
Example
The command <packageName> -install -silent -dir "C:\Program Files\MyFolder" will install
the Eaton IPM silently in C:\Program Files\MyFolder.
After the installation is completed, open a Web browser with the following URL:
l http://<host>:4679/, where <host> is the host name or IP address of the machine hosting the Eaton IPM.
Configure Nodes
Each node (Network Management Card, proxy, or application) must have a valid IP address (or a DNS name) in
the range that you have entered for auto-discovery (see “Compatibility” on page 2).
Eaton IPM automatically receives the alarms (through notification or polling) without specific configuration on
the network card, proxies, or applications.
For SNMP communication, configure the SNMP parameters using the System > Scan Settings selection.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > Auto
Discovery menu item.
2. From the right panel, select a discovery method (see Figure 8):
l Quick Scan: Automatically performed when application starts
l Range Scan: Click the Range scan button
l Address Scan: Click the Address(es) scan button
Quick Scan
The Quick Scan request is a broadcast frame on 4679 IANA reserved port and 69 standard TFTP port. Using
the Quick Scan operation, you will discover any of the following within a few seconds:
l Network Management Cards Network-MS (example, 66102/103006826) and Modbus-MS (example, 66103)
l PXGX2000, PXGXUPS, ConnectUPS-BD, ConnectUPS-X, or ConnectUPS-MS
l ePDUs
l Eaton Intelligent Power Protector (IPP) or Network Shutdown Module V3
Range Scan
Using the Range Scan operation, you will discover the nodes that are outside of the Network segment and
nodes that are not compatible with the Quick scan feature. See “Compatibility” on page 2 to determine if your
node supports Quick scan feature.
In the Range scan dialog box, you can edit IP address ranges. You can also select (check) the Override global
authentication settings checkbox to specify authentication parameters that are different from global scan
settings (see Figure 9).
Address Scan
This type of node discovery performs a single address scan (or for several IP addresses separated by the “;”
character).
l You can select (check) the Force node(s) creation checkbox to create a node with an IP address even if the
scan operation did not identify the device.
l You can also select (check) the Override global authentication settings checkbox to specify authentication
parameters that are different from global scan settings (see Figure 10).
NOTE The option Force node(s) creation will create empty nodes if the scan operation
did not identify the devices. Then it is possible to assign a different driver to the
nodes created (see “Change Driver Node” on page 19).
When discovered, manually or automatically, newly discovered devices will use these authentication
parameters. Depending on the device-supported protocols, IPM will choose the needed parameters. See
“Compatibility” on page 2 to determine which protocols are supported.
The administrator can also activate the automatic scanner to add any automatically discovered devices without
a direct scan action of the administrator. For example, with automatic scan enabled, the presence of a new card
on the network would be auto-discovered and added.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > System
menu item. The System page displays.
2. Click the Edit scan settings button on the right-side page. The Edit scan settings dialog box displays (see
Figure 12).
3. Set the scan settings by selecting or deselecting checkboxes, typing data, or make selections from the
drop-down list.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > Auto
Discovery menu item.The Nodes List page displays.
2. Select a node from the Nodes List page.
3. Click the Edit node information button or click the Set node access parameters button in the right
panel.
4. The Edit Node Information dialog or the Access parameters dialog displays (see Figure 14 and Figure 15):
l Edit node information dialog. The Edit node information dialog box allows editing the node name, the
user type, the node description and the associated load alarm threshold.
l Access parameters dialog. You can define the access settings for all selected devices. Only relevant
settings are set, depending on the capabilities of the selected device.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > User List
menu item. The User List page displays (see Figure 16).
2. Click Add user. The Add user dialog box displays.
3. Type the user’s login and the user’s password (see Figure 17).
4. Select the user's profile level. The following levels are available:
l Admin: User will be able to access all the features
l User: User will only access the visualization and cannot set changes to the system or nodes
5. Click Create new user.
Note that the Eaton IPM contains a default Administrator profile with:
l “admin” as login
l “admin” as password
WARNING
For security reasons, Eaton recommends that you change the default password immediately after
the installation. A pop-up message provides a security warning if the password contains less than
eight characters.
System Settings
From the Settings > System menu item, you can edit system information and settings (see Figure 18).
Select one of the items on the System page, and then double-click the item, or single-click the corresponding
button in the right-hand side menu:
NOTE The “User Drivers” feature allows IPM to supervise any SNMP- or Network UPS
Tools (NUT)-available devices. You can customize and adapt the IPM acquisition
engine to any kind of Data Center device, such as HVAC, Rack controller, storage, or
DC Power System controller.
These parameters can be modified in the “config.js” file in the logManager/purge section.
l Data of type alarm (see events section) maxTime: 28 days maxCount: 50000
l Data of type measure (see measures section) maxTime: 7 days maxCount: 200000
l Data of type statistic (see stats section) maxTime: 28 days maxCount: 20000
l Log system (see system section) maxTime: 28 days maxCount: 50000
Configuration Export/Import
You can backup the configuration to an external file. The external file can be used to restore the configuration.
This function is accessible through the GUI in the Settings > System page with the “Export configuration” and
“Import configuration” options available in the right column.
On windows systems, the same function can be called from the command line with the following syntax:
! IMPORTANT
Because of the potential complexity of final configuration, it is strongly recommended to test the
complete chain of events and actions before going into production.
Note that some restrictions could apply regarding your software licence and kind of devices you are managing.
Please check the license for more details.
! IMPORTANT
Be careful. VM power, VM migrate, and vApp power actions are not available on Hyper-V. To
protect Hyper-V virtualization servers, please perform configuration using selections in the
following path Management > Nodes Settings > Node configuration panel.
When triggered, an event provides the order for the action to occur while providing information to the events’
origin (ID, type of the event, and parameters) related to this type of event). That permits to the action to use
them and communicate more precisely about the source of this operation.
l Information Alarm
l Warning Alarm
l Critical Alarm
l Unknown State Alarm
l Power Failure
l Runtime Threshold reached
If these standard events are not enough to determine the possible cause of an action, users can define their
own custom events (see “Define Custom Events” on page 26).
Configuration Policies
The configuration policies panel allows you to define some policies using parameter sets and apply them either
to a single device or to any group of devices or applications monitored by IPM devices and applications
monitored by IPM.
In addition, the configuration policies panel is used to attach properties, such as the following:
l Power Source
l Runtime Threshold Settings
l User Settings
l Asset Information
It can be used to group devices by criticality, shutdown settings, power source, or what you think is relevant to
your environment.
A device or application that is attached to a configuration policy with a power source and Runtime Threshold
settings will be monitored and protected through the standard event called Runtime Threshold Reached.
l Actions can be linked to already defined events from their definition dialog.
l Events can be linked to already defined actions from their definition dialog.
l Settings attached to nodes through configuration policies can be used to define both event rules criteria and
action parameters.
l Any standard or custom events can be linked to any number of actions.
l Any standard or custom event can be combined together to build a rule of a new custom event.
Example Procedures
For more scenarios about how to use the new advanced features, see “Appendix A” on page 147. Those
scenarios will give you some examples of usage, but also a general approach to find out what has to be
configured to achieve a specific goal.
This is a way to create extensions for nodes by providing a new set of data and attaching new features to one
node or to a group of nodes.
The configuration policies view is accessible for all users (see Figure 19).
To create a configuration policy, click over a selection of target nodes in any node list (see Figure 20). For
example, if you intend to create a configuration policy and apply it to three well identified virtual machines, you
can select those three VMs, right click on the selection, and select Create new policy. This opens the “Edit
selected policy” dialog box with the target node field already initialized with the content of the selection (see
Figure 21).
A list of predefined configuration policies classes are associated with a set of features, such as:
l Asset Information
l Runtime Threshold Settings
l Power Source
l User Settings
Action Settings
From the Settings > Actions / Events menu item, notifications or executable actions can be set to occur as
the result of specific Eaton IPM actions (see Figure 22).
l All red fields marked with the “*” character are mandatory and must be defined.
l An action cannot be saved if all mandatory fields are not defined.
Tool tips with information for each action setting are available on the 'Name' column.
All red fields marked with the “*” character are mandatory and must be defined.
l In the list of settings, press the icon button on the row of the setting to edit.
l Double-click the row of the setting in the Action settings list.
Each setting type has its own edit window. You can insert an Object by pressing the icon button on the right
of the field displaying an object selector window (see Figure 25).
Editing
After creating an action, it is possible to modify it later.
To edit an action:
1. Select the action to edit in the list of actions and selecting the “Edit selected action” command in the right
panel (see Figure 26).
2. Double-click the action in the Action Settings panel (see Figure 27).
Then, the same window as shown in the creation process displays with all data from the selected action (see
Figure 23 on page 30).
Copy
You can clone an action by selecting one in the list of actions and selecting the Copy selected action command.
The Copy this action pop-up dialog displays a default name that is predefined and can be changed to your choice
(see Figure 28).
After saving a new action, it is listed on the Actions / Events page containing all the same data as the original
action.
Test
An action can be tested by selecting the “Test selected action” command in the right panel.
Select Yes to launch the test on the action (see Figure 29).
Remove
You can delete an action by selecting one in the list of actions and selecting “Remove selected action”
command in the right panel.
After confirming, the selected action is removed from the list of actions.
E-mail
E-mail actions need parameters such as the SMTP Server and recipients data provided by e-mail addresses.
You must indicate the SMTP server address and recipient e-mail address. Both logins and passwords are used
when the SMTP server requests authentication.
You can select between two modes (SSL or TCP) depending on your SMTP server capabilities and your
deployment constraints.
l Optional: You can customize the Subject, such as when you use a third-party service provider to translate
e-mail into SMS.
l Optional: You can specify that you want to receive a consolidation of the alarms that occurred during a delay
time duration (Digest period). For example, if you specify none, each alarm generates an e-mail. With this
setting, you will receive more e-mail for the same number of events.
Command
The command is executed by the supervision application when an action is triggered.
In order to execute a program on UPS events, the program path is required. The program is executed under the
SYSTEM account.
l If an action (script or program) cannot be executed under the SYSTEM account, it is necessary to modify the
execution context before it can run.
l To allow a user to run specific tools and programs with permissions that are different from those assigned to
the user's account, use the Windows “RunAs” command. This allows you to save the password (Windows
XP Service Pac 2 and more recent versions).
l Use the following Microsoft command:
l > runas /profile /user:<windows_ login> /savecred <my_program.exe>
l When first executed, a password is required; it is saved for subsequent executions.
SSH Action
To launch a command on an SSH server, type the hostname, port, a valid credential, and the command itself.
This action is suitable, for example, to remotely shut down any SSH enabled server or storage without an agent.
Notification
Notification produces a one line message displayed in the “Notifications” window. It is not necessary to include
the date and the origin object name of the action in the message as they are included in the notification.
Event Log
This action provides an event message to the node event list.
VM Power Action
This action executes a power command on a VM. A power command can be power on, power off, guest
shutdown, or suspend. Note that these actions are only available for VMware virtualization infrastructure.
VM Migrate Action
This migrates a virtual machine from its host to another host.
vApp Action
Allows you to start, shut down, or suspend a whole vApp in one action.
Storage Action
Currently one storage action is available: shutdown. It allows you to seamlessly shut down a storage or a set
of several storages (via policies). This procedure replaces the “Start a Recovery Plan” procedure required in
earlier IPM versions.
Infrastructure Shutdown
Parameters
1. vCenter target: the vCenter that manages the infrastructure to shut down
2. Critical group: select the configuration policy for all critical VMs to subscribe to. Those VMs are shut down
last and restarted at start up.
3. VM shutdown timeout: maximum time allowed for non-critical VMs shutdown
4. VM migrated timeout: maximum time allowed for critical VMs migration
Usage Sum-up
1. Create a configuration policy (Management > Configuration Policies).
2. Type the name you want (e.g., CriticalLoad).
Shutdown workflow
In the shutdown workflow, move the critical workload on one ESXi which is the last to stop. Call this ESXi the
"last ESXi".
The critical workload which is moved on the last ESXi contains the vCenter and IPM if they are virtualized. The
parameter 2 allows you to add a group of VMs of your choice to the critical workload.
The last ESXi is automatically determined. If vCenter is virtualized, the ESXi hosting vCenter is the last ESXi.
Otherwise, if IPM is virtualized, the ESXi hosting IPM is the last ESXi. In other cases, the last ESXi is the one
hosting the maximum number of critical VMs.
In order to select the VMs you want to consider as critical, you need to create a separate configuration policy
and subscribe your critical VMs to it.
The infrastructure shutdown process starts by the shutdown and power-off of all non-critical VMs.
Then (or after a delay equals to "VM shutdown timeout"), it migrates all remaining VMs on the last ESXi. Those
VMs are the critical ones (parameter 2), vCenter one and IPM one (each, when they are present).
When migration is achieved (or after a delay equal to the "VM migrated timeout"), all ESXi servers except the
last ESXi will be shut down.
At this point, only the last ESXi is live, hosting all and only critical VMs (including vCenter one and IPM). Before
it shuts down, it will record those VMs to be automatically restarted later.
At this stage, everything is in place to gracefully shut down the last remaining ESXi without crashing.
Remark
During the process above:
l DRS is disabled before the migration of critical VMs on the final ESXi.
l HA is disabled before the shutdown of the final ESXi.
Events
There are two types of events:
The following section provides the detailed information about custom events configuration. From the
Settings > Actions / Events menu item, it is possible to manage advanced events by selecting the “Edit event
rules” command on the right panel. The window also displays standard events, but it is just for supervision.
They cannot be modified.
l Event Name: The name of the event. Events can be grouped together by writing a group name just before
the event name and separate from it by a pipeline ( | ) character. Subgroups are not managed. For example,
“NewCustomEvent|event_1” name define the event named'event_1” in a group named
“NewCustomEvent.”
l Event Message: The message to display when the event occurs. An object can be inserted in the message
by using the button next to the field displaying an object selector window.
l Event Severity: Defines the severity of the event between these gradual choices: “None,” “Information,”
“Warning,” “Critical,” and “Unknown.
l Event mode: Defines the condition for the event to occur in function of its rules. There are two choices:
- Trigger if all conditions are satisfied: all rules must be satisfied.
- Trigger if any condition is satisfied: one of the rules is satisfied.
All rules that must be satisfied for the event to occur. (See “Event Rules” on page 39 for more details.)
The order of rules in the grid define the condition order for the event to occur.
To manage and define rules, use the following buttons below the grid:
A list of associated actions: Actions are launched when the event occurs. The event will appear in the list of
events of these selected actions (see “Create a New Action” on page 30). Actions can be selected by using the
Action List button displaying an action list configuration window (see Figure 31).
Event Rules
The Rule editor dialog allows you to create (add) or edit a rule. As part of defining the relationship between a
source object name and a destination object name, condition rules, and parameters are selected and applied in
this dialog (see Figure 32).
The Rule editor dialog is obtained by selecting a rule of a custom event, then clicking Edit, (or directly by
double-clicking on it). This functionality is not available when the license is basic (no possibility to add custom
events).
A trigger: The destination object that will be triggered by the rule (see “Triggers” on page 40 for more details).
An object can be defined using the button next to the field displaying an object selector window.
A source: The source object that will be used to evaluate the rule. It could be a device or a configuration policy.
A rule can also have a relationship with any sources. An object can be defined using the button next to the field
displaying a source selector window.
An operator: The source object that will be used to evaluate the rule. It could be a device or a configuration
policy. A rule can also have a relationship with any sources. An object can be defined using the button next to
the field displaying a source selector window. Available operators are:
A value: The comparison value for the operator. This value can also be an object that can be defined using the
button next to the field displaying an object selector window.
A grace period: Establishes a predefined period of time before the trigger event. The period must be between
0 to 300 seconds. A rule can be set to be ignored if its source trigger object is not defined on the node.
Triggers
The trigger base contains a list of objects with their trigger characteristics.
l Types: This lists objects able to trigger an event. Object can be associated with an item (node or
configuration policy) or can be global.
l Info (scope: node): This lists objects able to trigger an event. Object can be associated with an item (node
or configuration policy) or can be global.
l Alarms (scope: node): Objects used to display information, such as a name, a location, a node ID, a
configuration policy, and so forth.
l Measures (scope: node): Number objects related to a measure of current, voltage, power, time,
temperature, humidity, or a percentage rate.
l Virtualization (scope: node): All objects related to the virtualization, such as VM Host & VApp parameters
(name, path, state...), VM Name & Path.
l User Objects (scope: node): User objects are defined through user driver definition.The trigger type will be
defined by the user object definition.
l Configuration Policy Objects (scope: configuration policy): Triggers issue from configuration policy
objects. Can be used as comparison value.
l Events (scope: node/configuration policy/system): Events can be used as trigger of another event.
l Date (scope: system): All objects defined a date, a time, a day in the week, or in the month.
l System (scope: system): Events triggered by the MC2 application.
When the object is indexed, it is possible to select any index value or a specific one. There is no control on the
object index capability.The object info help text is provided for all well-known objects. It provides the object
description and possible values.
You first make the selection from the Rule Definition value list to display a trigger list or a reference value list.
Then you make a selection from the object list. For example, in the figures that follow, the Object selector
displays with from either the Rule Trigger>Utility present selection or the Value>{Shutdown timer} selection
(see Figure 33 or Figure 34).
l Nodes Triggers: The trigger list with the scope “node” listed above.
l Event Triggers: Predefined events and user defined events.
l Global Triggers: The global trigger list listed above.
l User Defined Objects: Objects defined through generic driver.
l Configuration Policy Attributes: Attributes defined through configuration policy class definition.
l Action Result Status: Result status returned by actions having feedback capability.
When the object is indexed, it is possible to select any index value or a specific one. There is no control on the
object index capability.
The object info help text is provided for all well-known objects. It provides the object description and possible
values.
The Alarm notification box is accessible from the System Tray icon (see Table 4 and Table 5). Click the icon to
open the window that displays the alarms on the local computer.
System Tray Icons
If no Power Source has been declared, the System Tray Icon will have the states described in Table 4.
Table 4. System Tray State Icons (Power Source not Declared; Shutdown module disabled)
Icon State Description
(BLUE) The System Tray Icon correctly receives alarms from Eaton IPM.
(GRAY) Communication is lost between the System Tray and the Eaton IPM.
If a Power Source has been declared, the System Tray Icon will have the states described in Table 5.
Table 5. System Tray State Icons (Power Source Declared)
Icon State Description
The System Tray Icon correctly receives alarms from the Eaton IPM. AC is present on the power source.
The System Tray Icon correctly receives alarms from the Eaton IPM. The power source runs in battery mode.
The System Tray Icon correctly receives alarms from the Eaton IPM. A Warning event occurred on the power source.
The System Tray Icon correctly receives alarms from the Eaton IPM. A critical event occurred on the power source.
NOTE Right-click the System Tray icon for fast access to the start and stop operations.
You can modify this script or create new scripts that define very specific events and actions. The sample script
in this folder provides details about the expected structure and syntax for defining new actions and triggers.
NOTE 1 You can change the alarm sound by setting the Windows sound preferences from
the Control Panel.
NOTE 2 The Eaton IPM alarms are linked to the audible “Low Battery Alarm” alarm sound
that you can change by selecting another .wav file.
Local Access
From the system where Eaton IPM is installed, you can use the following shortcut:
Start > Programs File > Eaton > Intelligent Power Protector > Open Eaton Intelligent Power Manager
Remote Access
1. From a remote computer, you can type either of the following URLs in a Web browser:
https://<name or IP address of computer hosting Eaton IPM>:4680/
-or-
http://<name or IP address of computer hosting Eaton IPM >:4679/
2. In SSL mode, accept the certificate using the procedure provided by your Browser.
3. Enter the login and password.
You can sort (ascending or descending) your device list by clicking the column titles (Status, Name, Description,
Location, Load Level, etc.). You can also add columns, as illustrated in Figure 37.
1. Select a device/applications in the list and Select panels displays in the right side of the window.
2. Click the bar title to collapse/extend the panel.
3. You can also show or hide all the views menu or selection view menu.
4. Select or deselect (check or uncheck) to select which panels you want to add in the selection view (see
Figure 38).
NOTE Some of the panels are only available for specific node types.
Information Panel
The following node information displays in this panel (see Figure 39):
l 166.99.xx.yy: DNS name (or IP address) displayed near the “status icon”
l Description: Commercial product name
l Nominal Apparent Power: Device load capacity in VA
l IP address: Device IP address
l Mac address: Device MAC address
l Serial Number: Device serial number (if available)
l Class:. Type of card
l Location: Device location (value of syslocation object can also be configured in the Device page)
l Contact: Device contact (value of syscontact object can also be configured in the Device page)
l Link: Link to device Web site (if available)
NOTE The information displayed in this panel depends on the node types you are viewing.
Status Panel
The following node status displays in this panel (see Figure 40):
NOTE The information displayed in this panel depends on the node capabilities.
Outlets Panel
The following outlets status information displays for the selected ePDU in this panel (see Figure 41):
Measures Panel
This panel displays the selected device electrical parameters for single-phase or three-phase devices,
depending on the node capabilities (see Figure 42 and Figure 43).
Environment Panel
This panel displays the selected device sensor information if a device is attached (see Figure 44):
NOTE For more information about the two optional input connections, please refer to the
Eaton Environmental Monitoring Probe (EMP) Quick Start Installation Manual.
Graph Panel
This panel displays the graph of the main measures of the selected device (see Figure 45):
Synoptic Panel
This panel displays the selected device synoptic (see Figure 46). A tool tip displays when you move the mouse
over one of the functional block.
The Synoptic color coded icons display for the following (see Table 7):
l UPS modules
l Battery modules
l Electrical flows
l Electrical power sources at UPS input
l Load at UPS output, with status linked to UPS output status
l Combined flow status and load status
Battery Modules
Green Status OK
Electrical Flows
Yellow Current flow through the cable
NOTE The object animation gives the direction of the current flow.
WARNING
Although there is no current flow through the cable, the cable may be under voltage.
Green/Gray Electrical power source is powered and does not provide electrical flow
Power Source
The Power Source panel displays information on the device that powers the selected application running on
the server (see Figure 47).
Powered Applications
The Powered applications panel displays information for the software applications (shutdown agents on the
servers) that are powered by the selected device (see Figure 48)”
l Status
l Name
l Shutdown diagram
l Shutdown duration
l Outlet group
Events Panel
This panel displays the events list of the selected node (see Figure 49). You can sort the events according to
status, date, and message by clicking the column header.
Statistics Panel
This panel displays the statistics of the selected node (see Figure 50). The button allows you to select the
time interval for the statistics. You can adjust the time interval by clicking the two buttons with the “From” and
“To” dates.
Power Components
Figure 51 illustrates the Power Components View. This panel displays the components of a redundant UPS
system if the Redundancy feature is activated (see “Redundancy” on page 97).
Subviews
Defining Subviews
When you need to monitor large configurations, it is helpful to define several subviews and then filter the nodes
or events in these categories. You can select many criteria in order to organize your tree.
To define a subview:
1. Select a view in the Views > Node List, such as Category: “Devices” or Location “HPO Finland” (see
Figure 52).
2. Right-click this selection. The contextual subview menu displays (see Figure 53).
3. Click Create a sub view from … and follow the instructions.
1. Select a view in the Views > Node List, such as “Location: Computer Room” (see Figure 52).
2. Right-click this selection. The contextual menu subviews displays (see Figure 53).
3. Click Edit a Filter View. The View Filter Rules dialog box displays (see Figure 54).
4. Click Add rule, then type the Object, Operation and Values.
NOTE With the setup shown in Figure 54, this filtered view allows you to view the devices
whose location field contains the value “Computer Room.”
As the result of creating a subview, the following default information appears in the Applications List View page
(see Figure 55).
l Type: Application
l Status: Status criticality of the server
l Name: Value configured in the Applications screen (by default this is an IP address or a DNS name)
l Description: Operating system
l Policies: Configuration policies list of the node (contact, location, IP address [Address IP of the node])
l Power Source: UPS that powers the Eaton IPP application/computer
l Estimated Run Time to Shutdown: Operating time in the event of a utility supply loss
l Shutdown Duration: Duration needed by the system to carry out its shutdown procedure (in seconds)
l Link: Link to the Web supervision interface of the Eaton IPP or Network Shutdown Module V3 module
NOTE The Eaton IPP or Network Shutdown Module V3 running on other computers in the
network can be monitored in this view.
Sharing Subviews
A customized subview is “attached” to the user that created it. It is private. The customized subview is marked
with a small man next to the icon of the subview (see Figure 56).
Figure 56. Shared View with Marker (left) and Public View without Marker (right)
If the owner of the subview wants to allow others to use the subview, he needs to share the view.
1. Right-click the view to open the contextual menu and click Share this View (see Figure 57).
NOTE Customizing a view cancels the sharing of this view. To allow all the users who were
sharing this file to view it, the owner of the view must share it again.
Device Supervision
The bar at the bottom of the page provides the status of nodes being supervised. Note the following in
Figure 58:
l 14 nodes are OK
l 4 nodes are in Warning status
l 2 nodes are in Critical status
l 0 nodes are in Unknown status
Figure 58. Bottom Bar for Device Supervision
Map View
This supervision map allows you to spatially represent your network nodes and uses “drag and drop”
functionality.
NOTE Clicking a node icon updates the information for that node on the right-hand panel.
The contextual tool button on the Node Map title bar provides tools to modify the map (see Figure 59):
l Change theme offers three kinds of icons representations (small tower icons, large tower icons, and large
rack icons).
l Manage backgrounds allows you to import a new background image in the supervision tool (png, jpeg, and
gif picture format types are supported). You can select a background already in the supervision tool for the
map or remove the background images.
l Regroup nodes rearranges the icons position on the Map.
l Add a label allows to create a user-defined text and to place it on the Map through drag and drop.
NOTE To delete a label, right-click the label and then click Delete.
Map Examples
This section provides examples of the following maps:
Events Logs
List Representation
Select Events > Events List to display the Events List page (see Figure 63). All new alarms are stored in this
log. You can sort the alarms according to the Status, Date, Name, and Acknowledge (ACK) fields.
l Acknowledge selected events: Adds a checkbox in the Ack column for selected events.
l Acknowledge all events: Adds a checkbox in the Ack column for all events.
NOTE When an alarm is acknowledged, it is marked with a checkbox but it is still viewable
in this Event list. The acknowledged alarms disappear in the Power Source > Event
dedicated portal panel.
NOTE The export command may take several seconds before allowing the download in
order to create the logs file.
Calendar Representation
Select Events > Events Calendar to display the Events Calendar page. In this matrix representation, each line
is a week and each column is a day in the week. If you select a day or an interval (with the date-picker or using
the shift+click command), the Events and Statistics panels provide all information for this selection and
automatically refresh when new statistics are computed (see Figure 64).
NORMAL With this event, the UPS device is returning to a normal status.
WARNING A problem occurred on the UPS device. Your application is still protected.
CRITICAL A serious problem occurred on the UPS device. This problem requires an urgent action. Your
application might NOT BE powered.
Figure 65 provides examples of the opening view from different Web interfaces.
If some nodes are selected in the list, the exported file contains only data for the selected nodes. If no node is
selected, the exported file contains data for all the nodes in the list. Only data from currently displayed columns
are exported.
The function is also available from the Auto Discovery > Export to CSV file menu selection.
This shutdown feature can be enabled or disabled from the Settings > System > Modules Settings selection
path.
NOTE 1 Refer to the Eaton Intelligent Power Protector (IPP) User’s Guide for a detailed
description of the Shutdown feature.
NOTE 2 When the Shutdown feature is enabled, the software displays a communication
error until the Power Source is correctly configured as described in the following
section, “Shutdown Configuration”.
Shutdown Configuration
To access the shutdown configuration options and verify that the Shutdown Module is enabled (administrator
access):
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > Shutdown
menu item.The Shutdown page displays (see Figure 67).
The following configuration options are provided on the right-side panel of the Shutdown page:
l Edit power source
l Edit shutdown criteria
l Edit advanced shutdown criteria
l Edit UPS configuration
l Test shutdown
l Run battery test
The Hibernate function must first have been activated in the operating system in the power options on the
Windows control panel Hibernate tab.
NOTE If you select hibernate, but your computer does not have this function, the Eaton
IPM will still protect the system by carrying out the normal (default) shutdown
action.
l To supervise the information from the UPS that powers the Eaton IPM computer.
l To drag and drop the panels in this window to different locations to personalize your viewing preference.
Shutdown Sequence
The Eaton IPM can acquire shutdown alarms from the Eaton IPP with the Shutdown Controller enabled.
NOTE Refer to the Eaton Intelligent Power Protector (IPP) User’s Guide for more
information about Shutdown sequence and Shutdown Use Case.
Nodes Settings
1. From the left-side Views panel of the Eaton IPM main interface window, select the Management >
Nodes Settings menu item. The Node List page displays.
2. Select one node (card) from the Node List page (see Figure 69).
3. After a few seconds, on the right hand, the Node configuration panel is updated.
4. If you wish to save a standard node configuration (for example to deploy to other similar nodes), use the
Configurations > Export Configuration file to export this configuration to a file.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Management >
Nodes Settings.
2. Select one node (one card) from the Node List page (see Figure 69).
3. Click the Node List button , select Set Login Parameters, and enter the card Login and Password.
The access status changes from Access Denied ( ) to Access OK ( ).
After a few seconds, the Node configuration panel is updated.
4. Click on the Edit button , or load a previously saved configuration.
5. In the Network Settings Configuration dialog box, check the parameters you want to change and type the
new values (see Figure 70).
NOTE The parameters that have different card and configuration values (unsynchronized)
are indicated by the sign.
! IMPORTANT
Some advanced parameter details are not displayed in the Network Settings Configuration dialog
box. For these details, you will need to change the advanced parameters details directly on one
device and then synchronize the configuration from this device to other devices (see Figure 71).
Figure 71 provides a typical example with PDU Power Schedule configuration. The details of Power Schedule
1 to Power Schedule 8 are available from the device Web interface. Checking all Power Schedule “n” advanced
parameters synchronizes all the advanced parameter details of the category.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Management >
Nodes Upgrade menu item.
2. Select the several cards on the Node List page.
3. Select the Node List button , select Set Login Parameters and enter the card login and password.
The access status changes from: Access Denied ( ) to Access OK ( ).
After a few seconds, the Node configuration panel is updated.
4. From the combo box, select the configuration that will be the model, or click Edit .
The parameters that have different values on the cards are indicated by the “not equal” sign.
5. Select the checkbox associated with the parameters you want to synchronize.
6. Click Synchronize.
Nodes Upgrade
NOTE Refer to the Network Management Card’s release notes to determine the latest
firmware release compatible with the hardware revision.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Management >
Nodes Upgrade menu item.
2. Select the cards on the Node List page.
3. From the Node List button , select Set Login Parameters and enter the card login and password.
The access status changes from: Access Denied ( ) to Access OK ( ).
4. From the Firmware > Import Firmware File… list box, the uploading window displays.
5. Click Browse to select the firmware from a disk accessible from the computer.
6. Click Import.
7. Click Firmware > Upload Firmware to nodes. The cards are updated with the selected firmware.
Upgrade Applications
To upgrade the applications (administrator access):
1. From the left-side Views panel of the Eaton IPM main interface window, select the Management >
Nodes Upgrade menu item.
2. Select the applications in the Node List.
3. From the Node List button , select Set Node Access Parameters and enter the access login and
password.
The access status changes from: Access Denied ( ) to Access OK ( ).
4. From the Applications upgrade panel, click Update. The status of the applications (with respect to the
version) is updated.
NOTE The UPS must be connected through a network interface. Peer-to-peer interfaces
between IPP and the UPS (USB/RS-232) communication protocols are not
supported for virtualization applications.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > System
menu item. The System page displays (see Figure 73).
2. Click Edit modules settings in the right panel. The Edit modules settings dialog box displays (see
Figure 72).
3. Ensure that the Infrastructure Connectors checkbox is selected (checked).
4. Click Save.
When a user tries to add a connector by Settings > Infrastructure Connectors > Add a connector, the
sequence of screens show options available, depending of the JRE prerequisite (see Figure 74). The
unselectable options are italic and grayed-out.
l If a JRE is installed on the system hosting Eaton IPM, VMware connectors are available (see “JRE
Prerequisites” on page 6).
NOTE For more information, refer to the Eaton Intelligent Power Protector (IPP) User’s
Guide.
l Remote graceful shutdown of multiple ESX/ESXi servers and hosted virtual machines (VMs)
l ESX/ESXi remote maintenance using VMware vMotion)
l Eaton IPM plug-in created in vCenter
l UPS events accessible through vCenter
These two solution architectures are illustrated in Figure 77 and Figure 78.
Figure 78. Eaton IPM Connected to ESX/ESXi to Protect VMware Infrastructure (Without vCenter)
Prerequisites
The Infrastructure Connectors module for virtualization requires the following prerequisites:
NOTE vCenter and Eaton IPM could be installed on the same system.
l To provide the virtual machine (VM) graceful shutdown, you must install VMware tools on each VM.
l You have knowledge and experience with Eaton IPM software and the VMware infrastructure.
NOTE Since IPM version 1.25, vSphere SDK for Perl is no longer required.
In this solution, ESX and ESXi hosts are not controlled by vCenter (paid version only), which provides following
features:
l Eaton IPP application is installed on VMware Infrastructure Management Agent (VIMA)/vMA for each host
l Eaton IPP configurations and actions can be managed centrally from the Eaton IPM client
l Some command line programming is required
l Remote graceful shutdown of multiple ESX/ESXi servers and hosted VMs
1. If you have not already enabled the Infrastructures Connectors module, use the Edit modules settings
dialog in the Settings > System menu. The Infrastructure Connectors menu entry displays as a selection
in the Settings menu.
2. Click Infrastructure Connectors.
3. Click Add a connector on the right-side panel. The Add a connector dialog displays.
NOTE To edit or remove connectors, you must first select a line in the center panel.
1. From the Add a Connector dialog, select VMware vCenter from the Product drop-down list (see
Figure 80). A second Add a connector dialog displays for your product connector selection.
2. Add identification information for the selected connector (see Figure 81).
l Product: Select VMware vCenter from the drop-down list
l Hostname or IP address: Type VMware vCenter Host name or IP address
l Port: Type the port number
l Username: Type VMware vCenter Administrator Username
l Password: Type VMware vCenter Administrator Password
l vCenter Plugin: Select (check) the checkbox to install and configure the Eaton IPM Plug-in to vCenter
NOTE See“Configuring the Eaton IPM vCenter Plug-in and WebPlug-in” on page 121
when using this feature.
3. Click Save after the fields are updated. The VMware ESXi hosts are automatically added to the managed
nodes.
NOTE 1 The encrypted password is stored in the following configuration file ({Eaton IPM
INSTALL DIRECTORY}\configs\vmconfig.js).
NOTE 2 When configuring the Login Username and Password, Eaton recommends using
the Eaton IPM Web interface through https. Using http is also possible but the
password is sent to the local or remote server in clear. The encrypted password is
stored in the configuration file <IPM-Install-Dir>/configs/infraconfig.js
1. From the Add a Connector dialog, select New VMware ESX/ESXi from the Virtualization drop-down list. A
second Add a connector dialog displays for your product connector selection.
2. Add identification information for the selected connector (see Figure 82)
l Product: VMware ESX/ESXi is already selected in the drop-down list.
l Hostname or IP address: Type VMware ESX/ESXi Hostname or IP address
l Username: Type VMware ESX/ESXi Administrator Username for the Administrator with admin rights on
the ESXi
l Password: Type VMware ESX/ESXi Administrator Password
3. Click Save after the fields are updated.
VM and vApps
Once you have connected IPM with a VMware vCenter or ESX/ESXi hypervisor, the VM and virtual applications
managed by the VMware server are automatically discovered by IPM and added as new nodes.
If you click a VM node, you can see its power state and the ESX/ESXi which hosts it.
Changes on VM/vApp power state are logged in the “event popup window.” With the “Advanced Event &
Actions,” you can trigger specific actions when such a change occurs.
See “VMware & VM Migrate on EMP” in Appendix A. VM and vApps are displayed only with a SILVER/GOLD
license.
l Starts recovery process on several different events: IPM initiates the execution of recovery plan upon
several different events.
l Less down time for end users: VMs will be down only for the amount of time required to transfer the latest
snapshot and will restart once transfer is complete. The unprotected VMs will continue to run on the
primary site.
l Customization for end users: You can customize the script included in the package as needed. For
example, you may want to customize the SRM with IPM for low battery and protection loss features. You
can trigger your customized SRM action when your customized event is triggered.
l Unattended execution of recovery plan before server crash: SRM with IPM provides recovery, even
before the entire site crashes. When the SRM feature is used, the backup will be ready even before the
crash, which keeps the site continually secured.
l See “Site Recovery Manager (SRM) with EMP” on page 170.
NOTE For more information, refer to the Eaton Intelligent Power Protector (IPP) User’s
Guide.
Figure 84. Eaton IPM Connected to SCVMM to Protect Microsoft Virtual Infrastructure
Prerequisites
The virtualization module requires the following prerequisites:
l The Powershell Snap-in for Microsoft SCVMM. Either install the VMM console on the machine hosting
Eaton IPM, or install Eaton IPM on the machine hosting SCVMM.
l The server hosting Eaton IPM must be on the same Windows Domain as the SCVMM Server.
l The server hosting Eaton IPM must enable the execution of third party scripts on the local machine
(minimum access “Remote Signed,” for example, Set-ExecutionPolicy RemoteSigned).
Figure 85 illustrates the parameters that display for an example configuration. To save settings, click Save when
the fields are updated.
NOTE When configuring the Login Username and Password, we recommend using the
Eaton IPM Web interface through https. Using http is also possible, but the
password is sent to the local or remote server in clear. In both cases, the encrypted
password is stored in Eaton IPM and never again sent on the Client side.
1. From the Add a Connector dialog, select Microsoft SCVMM from the Virtualization drop-down list. A
second Add a connector dialog displays for your product connector selection.
2. Add identification information for the selected connector (see Figure 82):
l Product: Microsoft SCVMM (already selected in the drop-down list)
l Hostname or IP address: Type Microsoft SCVMM Hostname or IP address
3. Click Save after the fields are updated.
This solution is integrated into Eaton IPM and provides the following features:
Figure 88. Eaton IPM Connected to XenServers (Triggers XenMotion and Eaton IPP Running on XenServer Infrastructure)
Figure 89 describes the recommended approach to protect your Citrix infrastructure. The latest Citrix
infrastructure connector allows you to define configuration policies and use them in advanced events and
actions schemes to address all your needs for business continuity. You can now install IPP on one IPM instead
of installing it on each server.
Prerequisites
The virtualization module requires the following prerequisites:
1. From the Add a Connector dialog, select Citrix XenServer from the Virtualization drop-down list. A second
Add a connector dialog displays for your product connector selection.
2. Add identification information for the selected connector (see Figure 90):
l Product: Citrix XenServer is already selected in the drop-down list
l Hostname or IP address: Type Citrix XenServer Hostname or IP address
l Username: Type Citrix XenServer Administrator Username
l Password: Type Citrix XenServer Administrator Password
3. Click Save after the fields are updated.
Adding a XenCenter
Because Citrix XenCenter is a Client and not a Manager, you can install a plug-in on the system where
XenCenter is installed (see Figure 91). This plug-in allows you to use Eaton IPM in XenCenter.
1. From the Add a Connector dialog, select Citrix XenCenter from the Virtualization drop-down list. A second
Add a connector dialog displays for your product connector selection.
1. Add identification information for the selected connector (see Figure 90):
l Product: Citrix XenCenter is already selected in the drop-down list
l XenCenter Plugin: Select the checkbox to use Eaton IPM in XenCenter
2. Click Save after the fields are updated.
l Provides graceful shutdown for KVM with Eaton IPP installed on each KVM system
NOTE For more information, refer to the Eaton Intelligent Power Protector (IPP) User’s
Guide.
NOTE For more information, refer to the Eaton Intelligent Power Protector (IPP) User’s
Guide.
l Provides graceful shutdown for Xen with Eaton IPP installed on each Xen system
NOTE For more information, refer to the Eaton Intelligent Power Protector (IPP) User’s
Guide.
Configuring Hypervisors
Descriptions of two methods for configuring hypervisors follow (see “Adding Infrastructure Connectors” on
page 82).
To configure the node and add a Power Source in the Shutdown Settings dialog:
1. From the Management > Nodes Settings menu item, click the host in the Nodes list (see “Nodes
Settings” on page 74).
2. In the Shutdown Settings panel on the right side of the page, select the applicable checkboxes to
configure the required parameters (see Figure 94 and Table 8).
NOTE The shutdown settings that display vary depending on the node you select. In this
example, the node functionalities include remote maintenance mode and remote
shutdown.
Figure 94. Example Shutdown Settings - Before Configuration
l The Maintenance Timer must be less than the Shutdown after value.
1. From the Management > Nodes Settings menu item, click the host in the Nodes list (see “Nodes
Settings” on page 74).
2. In the Shutdown Settings panel on the right side of the page, select the applicable checkboxes to
configure the required parameters (see Figure 96 and Table 9).
NOTE The shutdown settings that display vary depending on the node you select. In this
example, the node contains both remote maintenance mode feature parameters
and Eaton IPP shutdown parameters because the Eaton IPP performs the shutdown
locally.
! IMPORTANT
If you install an Eaton IPP on the VM Host after the Eaton IPM node has been created, first delete
the node in Eaton IPM. Then, rediscover the node with the “Address Scan” in the Auto Discovery
panel. The Eaton IPM creates the correct node type and retrieves both the VM Host information
and the Eaton IPP information.
The Eaton IPM can supervise composite devices. Composite devices are virtual nodes composed of two or
more UPSs mounted with specific redundancy topologies and a dedicated redundancy level.
NOTE Specific redundance topologies include Redundant supplies, Hot standby, Static
transfer switch (STS) for two components, and Parallel for two or more
components.
Enabling Redundancy
This Redundancy feature is enabled from Settings > System > Modules Settings (see Figure 97). After the
feature is enabled, the Eaton IPM performs the following:
NOTE You can also shut down a remote server linked to the composite device through the
infrastructure connector feature.
l Redundant supplies (such as dual feeds or triple feeds): Figure 98 illustrates a scenario when two UPSs
provide power on one or several multiple-feed servers.
l Hot standby mode: When the upstream UPS powers the load, the downstream UPS is on bypass (see
Figure 99).
l Static transfer switch for two components: For STS mode, there are several cases with single STS or
multiple STSs (see Figure 100).
l Parallel for two or more components: All the UPSs power the load at the same time (see Figure 101).
Configuring Redundancy
To configure redundancy:
1. From Start > Programs > Eaton > Intelligent Power Manager, select Open Eaton Intelligent Power
Manager to start the main Eaton IPM graphical interface. Login with an administrator user profile.
2. Select the Settings > Auto Discovery menu item.
3. From the Nodes List page, select two or more nodes.
4. Click Set composite device in the right panel (see Figure 102).
5. In the dialog box, specify a device name, redundancy mode, and level (see Figure 103):
l Device Name: Name of the composite device
l Redundancy Mode: Parallel, Redundant Supplies, Hot Standby, or Static Transfer Switch
l Redundancy Level: Minimal number of redundant UPSs powering your system (default value is 0)
NOTE If you set this parameter to a higher level, you will receive the “Redundancy Lost”
alarm.
Three actions you can perform on the new node are as follows (see Figure 102):
NOTE When created, a new virtual power source is counted as a node for the licensing
node limitation.
Redundancy Views
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 100
Redundancy
NOTE This view shows only components of the selected power source if it is a composite
device.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 101
Redundancy
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 102
Redundancy
Use Case #2
You want to have a shutdown after a predefined time of 10 min. The shutdown must occur, even if only one
UPS is on battery.
l The IPM default configuration is available from Settings > Shutdown > Edit Shutdown Configuration
(see Figure 110).
l In this case, each server can have its own shutdown timer (10 min, 8 min, 6 min, and so forth). To set a
predefined time of 10 min, configure the shutdown timer for 10 min in the Edit Shutdown Configuration
dialog box.
NOTE This is the default configuration on the Network Management Card (see “Use
Case #1” on page 102).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 103
Redundancy
Use Case #3
You want to start shutdown 10 min from the last detected Utility failure event. For this case, there are two
UPSs, and one UPS is redundant. In addition, all servers are shut down at the same time.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 104
Redundancy
Use Case #4
You want to have a shutdown when 10 min remain for the last UPS. In this case, each server can have an
individual shutdown duration, such as 10 min, 8 min, 3 min, and so forth.
l The IPM default configuration is available from Settings > Shutdown > Edit Shutdown Configuration
(see Figure 113).
l You must configure a shutdown duration of 10 min in the Eaton IPM.
NOTE This is the default configuration on the Network Management Card (refer to “Use
Case #3”).
l You must use the default Network Card Configuration. See “Use Case #1” on page 102 for more details.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 105
Redundancy
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 106
Redundancy
Redundancy Compatibility
The following UPSs and topologies have been tested in redundant mode. Other topologies or UPSs may work,
but have not been tested.
Table 12 provides a compatibility list for single-phase UPSs and Table 13 provides a compatibility list for
three-phase UPSs.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 107
Chapter 10 User Drivers
The User Drivers feature allows the Eaton Intelligent Power Manager (IPM) to supervise any available Simple
Network Management Protocol (SNMP) or Network UPS Tools (NUT) device. You can customize and adapt the
Eaton IPM acquisition engine to many types of Data Center devices, such as HVAC, rack controllers, storage
appliance, or DC power system controllers.
By default, the User Driver feature is activated. However, if you disable this function, previously discovered
nodes that are using a User Driver are still managed.
l UPS RFC1628/SNMP: Manages the UPS which implements the SNMP mib RFC1628
l NAS BUFFALO®/SNMP: Manages the SNMP Buffalo Network Attached Storage (NAS)
l NAS HP/SNMP: Manages the SNMP HP NAS
l NAS NetApp/SNMP: Manages the SNMP NetApp NAS
l NAS Netgear/SNMP: Manages the SNMP Netgear NAS
l NAS Qnap/SNMP: Manages the SNMP Qnap NAS
l NAS Synology/SNMP: Manages the SNMP Synology NAS
l PDU/NUT Protocol: Manages the SNMP PDU using NUT
l UPS/NUT Protocol: Manages the SNMP UPS using NUT
l ATS Eaton 32A: Manage the SNMP EATON STS
NOTE NUT is open source software that provides control and management features for
power devices, such as UPSs, through a control and management interface. Visit at:
http://www.networkupstools.org
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > Auto
Discovery menu item.
2. Select the User drivers editor... button from the right panel (see Figure 115). The User drivers editor
page displays.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 108
User Drivers
NOTE By default, the User Driver feature is enabled. You can enable or disable this
function on the Edit module settings dialog by selecting or deselecting (checking
or unchecking) the checkbox for the User Driver (see Figure 116).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 109
User Drivers
NOTE A rule defines the relationship between a source object name and a destination
object name.
l Buttons are provided at the bottom of the dialog to manage drivers and driver rules.
Buttons
The following buttons allow you to manage drivers and rules.
l New driver: Click the New driver button to add a new driver to the list and define the properties for the
driver. A new empty driver can be created or you can use a copy of an existing driver. Predefined drivers
provided with the application are read-only and cannot be changed. They can only be deactivated or
duplicated for customization purposes.
l Delete driver: The Delete driver button deletes the driver that is selected in the left panel.
NOTE When a driver is deleted after applying modifications, it is not possible to recover
this driver.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 110
User Drivers
You can enable or disable a rule by selecting (checking) or deselecting (unchecking) the checkbox in the first
column. When a rule is disabled, the data defined in the rule is no longer acquired.
Driver Data
The right side of the page provides data for the driver selected in the left panel.
The top right data fields identify the selected driver and allow you to set actions to occur during discovery as
follows:
l Scan active: This option provides the ability to activate or deactivate a driver. When this option is deselected
(unchecked), the driver is filtered during discovery action. It allows using a modified copy of a driver instead
of the default driver.
l Driver name: This name defines the unique friendly name of the driver. This name displays in the
information Class column of the node view.
l Type: Type defines the driver type as follows:
- UPS device
- PDU device
- Power meter
- Power generator
- DC controller
- Power over Ethernet (PoE) appliance
- Server
- Storage appliance
- Network appliance
- Ambiance meter
- Cooling system
- Other device
l Check with this address: Allows you to check the rules result with an address or a device host name.
- For SNMP protocol, it is the global scan settings you are using. If you need special access for the driver,
you need to temporarily change these settings.
- For NUT protocol, use <IP address or host name>/<Device ID>
where <Device ID> = Name of the NUT device, such as, the section header name defined in the
ups.conf file for a UPS.
l Check button: Enabled only if an address or a name is typed in the Check with this address/name entry
box. See “Rule List” on page 112 for more information.
l Protocol: Protocol field, either SNMP or NUT:
- SNMP: Provides support of SNMP v1 and v3 driver
- NUT: Provides support of NUT client Interface
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 111
User Drivers
l Device identification: Defines the device identification used for device recognition during discovery. For
SNMP device, use the SysOID value, or use the root OID of the device if the SysOID is not managed by the
device.
l Alarm polling rate: Defines the polling rate for objects of type alarm. Information type data are acquired
only once, at driver reset.
l Measure polling rate: Defines the polling rate for objects of measure type.
NOTE Measure data type polling can be performed simultaneously with alarm data type.
In this case, only one task will be cyclically executed.
Rule List
The table on the right side of the User drivers editor dialog lists defined rules associated with the selected
driver.
l Source object name: source object name of the data to acquire in the device
l Destination object name: internal object name managed by the IPM application
NOTE A destination object can be defined by several complementary rules. For a same
destination object, if a rule is not applicable, it takes the next rule defined in the list.
The Check button in the Rule list table header is used to compute and display the result for each rule according
parameters. The result is computed with the address or the name entered for Check with this address/
name.The Check button is enabled only if an address or a name is entered.
To edit or create a rule on the Edit rule dialog, you need to enter the following:
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 112
User Drivers
When the rule is created, you can test the rule using the Check result button. See the following section,
“Buttons” for a description of the Check result button.
Buttons
The following buttons allow you to create and test rules on the Rule editor dialog.
l Manage user defined objects...: Allows you to define your own object list to link for a specific device type
l Browse source object name...: Builds a list to help you to select the appropriate source object from a list of
value
l Check result: Used to compute the rule result according the given parameters. The source result and the
final rule result are both displayed.
NOTE The Check result button is enabled only if the address or name is entered for Check
with this address/name on the User drivers editor dialog.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 113
User Drivers
l Select a “well-known” and predefined object (which is a standard object managed by the IPM application)
from the standard objects list in Table 14.
l Select a specific user-defined object when the needed object is not defined in the standard object list.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 114
User Drivers
You can also define your own object list to create links for a specific device type in the User defined object editor
dialog. A new object can be defined by providing these properties:
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 115
User Drivers
! IMPORTANT
l The user-defined objects only display in a specific Node view panel named Other data (see
Figure 120). These user-defined objects display as a raw list that is sorted by groups.
l The standard objects are NOT displayed in the Other data panel. These standard objects are
defined in standard IPM panels (see Table 14).
l The user-defined object list is attached to the driver.
l Click the Manage user defined objects… button in the rule editor to manage user-defined
objects.
l If the destination object name is indexed (for a standard object or a user-defined object), use “x” in the
source object name for the index position.
l For an SNMP device, the source object name corresponds to the object ID (OID) name of the data to
acquire. The list is built from the device identification name which has been given. It corresponds to all OIDs
available under the OID root or the SysOID value.
l For a NUT device, the source object name corresponds to the internal NUT object name.
If you provided a valid address in the check item of the driver, an interface is provided to help you to select the
appropriate source object from a list of value.
1. From the Rule editor dialog, click on the Browse source object name… button. The object list is built
automatically when the window opens.
NOTE You can pause the object list acquisition at any time using the Pause button.
2. The Restart button restarts the object list acquisition from the beginning.
3. The Cancel button aborts the object list acquisition.
4. Select the appropriate object in the list and then click Ok.
Conversion Rules
The following notes apply when defining the conversion rules in the Rule editor dialog:
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 116
User Drivers
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 117
User Drivers
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 118
Chapter 11 Storage
The Eaton Intelligent Power Manager (IPM) can supervise storage devices. On the user interface, storage
devices are seen as a “Storage Appliance” type with the following information displayed:
l Type
l Status
l Name
l Description
l Class
l Location
l Contact
l Link
Using the User Drivers feature, you can launch a Range scan with the IP address of your storage equipment
(see “Range Scan” on page 15 and “User Driver Editor Dialog” on page 109). After performing a Range scan,
you will have a list of storage managed by Eaton IPM.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > System
menu item. The System page displays.
2. Click Edit modules settings in the right panel. The Edit modules settings dialog box displays (see
Figure 121).
3. Ensure that the Infrastructure Connectors checkbox is selected (checked).
4. Click Save.
5. Select Settings > Infrastructure Connectors. The Infrastructure Connectors Select Add a connector in
the right panel. The Add a connector dialog opens (see Figure 122).
6. Add identification information for the selected connector
l Product: Select NetApp storage from the drop-down list
l Hostname or IP address: Type the NetApp IP address
l Username: Type NetApp Administrator Username with admin rights on the NetApp
l Password: Type NetApp Administrator Password
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 119
Storage
To create a new configuration policy and define the protection (see Figure 123):
Shutdown
IPM manages the shutdown of storage through a simple and powerful shutdown action. For more information,
see “Advanced Events and Actions” on page 25.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 120
Chapter 12 Extended Functionality
This chapter describes extended functionality for the Eaton Intelligent Power Manager (IPM) including:
Various useful applications can be attached to vCenter to make it more useful. The vCenter Eaton Intelligent
Power Manager Plug-in is also called the Eaton vCenter Plug-in. It is easy to deploy and to use the plug-in to
manage the Eaton Intelligent Power Manager (IPM) from vCenter. This plug-in integrates the Eaton IPM with
vCenter environment. After the plug-in is deployed, a tab in vCenter will open the Eaton IPM and allows you to
configure and manage the Eaton IPM from the vCenter environment.
The VMware plug-in also allows the creation of new type of events that can be trigger type alarms (these are
alarms that trigger an action).
1. In the VMware vSphere Client, select the Plug-ins > Manage Plug-ins menu item (see Figure ).
2. Locate the Eaton IPM Plug-in for vCenter in the Plug-in Manager (see Figure 125).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 121
Extended Functionality
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 122
Extended Functionality
The Eaton IPM tab is visible in the vCenter Server Console and in the root folder . The Eaton IPM is now
available and is fully functional with the vSphere Client. Note that the Eaton Power Manager tab on the top is
selected (see Figure 127).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 123
Extended Functionality
On the Host level, you will see a widget with the UPS protecting your ESXi, and other information such as state,
and a link to go directly on the IPM web interface.
Prerequisites
The Eaton IPM must be installed on the same machine as Citrix® XenCenter™.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 124
Extended Functionality
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 125
Extended Functionality
Prerequisites
All VM images must be installed and configured on a file server.
Introduction
The Dynamic Resource Scheduler (DRS) application from VMware is used to provide load balancing within the
IT network. In particular, DRS is used to ensure the right resource capacity is available for the data center load.
A second application called VMware vMotion (used in conjunction with DRS) will enact movement of VMs from
physical server to physical server in order to provide the best load balance.
The Distributed Power Manager (DPM) application helps to maximize data center electrical power efficiency. It
checks DRS for physical server utilization and then, using vMotion, moves VMs to servers in order to fully
unload servers, idle them, or power them down for maximum power savings.
Eaton uses the same vMotion capability when a UPS is in a critical power situation to move VMs off of a server
that has a critical power situation. Eaton IPM then writes alarms/alerts into vCenter, which, in turn, triggers
vMotion.
VMware uses the term “setting a server into Maintenance mode” to trigger the vMotion. It is called this
because before performing maintenance on server, the data center manager needs to clear the VMs from the
server.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 126
Extended Functionality
A host enters or leaves maintenance mode only as the result of a user request. If the host is in a cluster when
it enters maintenance mode, the user is given the option to evacuate powered-off VMs. If this option is
selected, each powered-off VM is migrated to another host, unless there is no compatible host available for the
VM in the cluster. While in maintenance mode, the host does not allow deployment or “power-on” of a VM.
VMs that are running on a host entering maintenance mode need to be either migrated to another host or shut
down (either manually or automatically by DRS).
When no more operating VMs are on the host, the host's icon changes to include 'under maintenance'
designation and the host's Summary panel indicates the new state. The default automation mode of a VM
determines its behavior when the host (in a DRS cluster) it is running on enters maintenance mode:
NOTE With this example, you choose to move all the VMs from this server to another
server of the same cluster. You can also define other behaviors according to your
needs.
Configuration Test
To test the installation, please perform a power failure on the UPS and check on vSphere client that the
corresponding ESX/ESXi host enters in Maintenance mode after the “Maintenance mode timer.”
l Eaton IPM continues to move the VM from one server to the others, if all servers are powered by different
UPSs with different power source (see Figure 133).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 127
Extended Functionality
Eaton IPM continues to protect the hypervisor also when power fails.
Due to the deactivation of the automatic startup and shutdown, all VMs power-off at the end of utility failure
sequence.
l Configure the VMware ESX/ESXi nodes in Eaton IPM to shut down the VMs (remote shutdown of the VM
setting).
l Install a Eaton IPM on each VM, even if it is not an optimized solution. Take care to ensure that when VMs
move, the Eaton IPM still links to the same UPS power source.
NOTE For more information about the deactivation of the Automatic Startup/Shutdown
when creating a VMware HA Cluster, see links provided by “vSphere SDK for Perl”
on page 130.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 128
Extended Functionality
Maintenance Mode
In Virtual Machine Manager (VMM) 2008 R2, you can start maintenance mode for a VM host anytime that you
need to perform maintenance tasks on the physical host computer, such as applying security updates or
replacing hardware.
When you start maintenance mode on a Windows-based host, VMM automatically does the following:
l On a stand-alone host, VMM places all operating VMs into a saved state.
l On a Windows-based host cluster that is capable of live migration, VMM provides the following options:
- Live migration of all running, highly available VMs to other hosts in the cluster, and place any operating
VMs that are not highly available in a saved state.
- Place all operating VMs into a saved state.
In addition, failover clustering requires shared storage for the cluster nodes. This can include an iSCSI or
Fiber-Channel Storage Area Network (SAN). All VMs are stored in the shared storage area, and the running VM
state is managed by one of the nodes.
Configuration Test
To test the installation, perform a power failure on the UPS. On the Microsoft System Center Virtual Machine
Manager (SCVMM) console, verify that the corresponding Hyper-V host enters in Maintenance mode after the
“Maintenance mode timer.” Hyper-V machines must be started before the machine that is hosting the SCVMM.
The SCVMM service needs some time to refresh its status. If the starting sequence is not correct, the Hyper-V
stays in Maintenance mode.
VMware References
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 129
Extended Functionality
VMware does not endorse or make any representations about third-party information included in this
document. The inclusion of any VMware icon or diagram in this document does not imply such an endorsement.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > System
menu item. The System page displays.
2. Click Edit modules settings in the right panel. The Edit modules settings dialog box displays (see
Figure 134).
3. Ensure that the Infrastructure Connectors checkbox is selected (checked).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 130
Extended Functionality
4. Click Save.
1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings >
Infrastructure Connectors menu item. The Infrastructure Connectorspage displays (see Figure 135).
2. Click Add a connector in the right panel. The Add a connector dialog box displays (see Figure 136).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 131
Extended Functionality
3. From the Add a Connector dialog, select Cisco UCS Manager from the Product drop-down list (see
Figure 136).
4. Add identification information for the selected connector:
l Product: Cisco UCS Manager is already selected in the drop-down list.
l Hostname or IP address: Type Cisco UCS Manager IP address
l Port: Port number
l Username: Type Cisco UCS Manager Administrator Username for the Administrator with admin rights
on the Cisco UCS Manager
l Password: Type Cisco UCS Manager Administrator Password
5. Click Save after the fields are updated.
6. When the component is connected, the Cisco UCS Manager displays on the Infrastructure Connectors
page (see Figure 137).
7. If the component does not display, refresh the page. Also, check the log to ensure the Event details
display with an OK connection state (see Figure 138).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 132
Extended Functionality
Edit a Component
To edit a Component, right-click the component in the list. From the action box, click Edit connector (see
Figure 140). The Edit connector dialog displays.
NOTE IPM currently doesn't allow you to edit the IP address. To edit a new IP address,
please remove the connector and add another connector.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 133
Extended Functionality
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 134
Extended Functionality
1. Select Nodes Settings > “the UCS Manager component” > Shutdown Setting and click the pen icon
(see Figure 142).
.
Power source, Load Segment, Remote shutdown, Shutdown duration, and Shutdown after value are standard
IPM options and are not described here. The following topics are discussed:
The future Power Budget or Policy Priority are the values that will be temporarily set in your blade. When the
power failure occurs, the older values will be set back in your blade after the power come back.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 135
Extended Functionality
! IMPORTANT
A service profile has to be attached to a blade to set priorities on a blade.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 136
Extended Functionality
If the server encounters a spike in power usage that meets or exceeds the maximum configured for the server,
Cisco UCS Manager does not disconnect or shut down the server. Instead, Cisco UCS Manager reduces the
power that is made available to the server. This reduction can slow down the server, including a reduction in
CPU speed.
Priority is ranked on a scale of 1-10, where 1 indicates the highest priority and 10 indicates lowest priority. The
default priority is 5.
For mission-critical applications, a special power priority called no-cap is also available. Setting the priority to
no-cap prevents a Cisco UCS from leveraging unused power from that particular blade server. The server is
allocated the maximum amount of power that the blade can reach (see Figure 146 and Figure 147).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 137
Extended Functionality
Figure 147. Shutdown Settings-Current Power Not Set Due to No-Cap Service Profile
Power Budget
Power budget allows you to specify the maximum amount of power (in watt) that the server can consume at
one time.
If the value is set to “unbounded,” no power usage limitations are imposed upon the server and the future
temporary power budget is disabled (see Figure 148). The server can use as much power as it requires.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 138
Extended Functionality
Common Errors and Notifications for the Cisco UCS Manager Component
1. You can't set a shutdown to a blade that doesn't have a service profile assigned (see Figure 149).
2. You can't set a priority to a blade that doesn't have a service profile assigned (see Figure 150).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 139
Extended Functionality
4. A wrong value has been set for the power budget (see Figure 152).
5. A new power budget has been requested by the client (see Figure 153).
.
6. A new power budget has been successfully set by the server (see Figure 154).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 140
Chapter 13 Virtual Appliance
This chapter describes deploying the Eaton Intelligent Power Manager (IPM) as a virtual appliance including:
l 14 GB data store
l 1GB free memory
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 141
Virtual Appliance
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 142
Virtual Appliance
With a Standard Console, you will see the following screen (see Figure 156).
l Login: root
l Password: eaton
NOTE To enable the first remote access, the root access is enabled for the SSH daemon.
For security issues, you can disallow the connection of the root user in
“/etc/ssh/sshd_config” and set “PermitRootLogin” to no.
You can only connect on the virtual appliance through Eaton Web Page or SSH connection. For example, the
Virtual Appliance doesn't respond to “Ping” (an ICMP response is not allowed).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 143
Virtual Appliance
l Knowledge of iptables
l Credentials to connect on the Virtual Appliance
l SSH Client
To modify the default configuration, you need to edit the script in /etc/init.d/firewall.
You can see how the “firewall” is configured to be launched after each startup in Figure 158.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 144
Virtual Appliance
NOTE After upgrading IPM software (1.28 to 1.40 for example) you must add these two
rules in the firewall:
/sbin/iptables -A INPUT -p tcp --dport 61616 -j ACCEPT #EMC4J
MessageBus
/sbin/iptables -A INPUT -p tcp --dport 1099 -j ACCEPT
#rmiregistry
Configuring IPM
To configure IPM, see “Configuring IPM” on page 145.
Firewall (iptables)
l Visit the iptables project on the NetFilter website
l Project - http://www.netfilter.org/projects/iptables/index.html
l Documentation - http://www.netfilter.org/documentation/index.html
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 145
Chapter 14 Service and Support
If you have any questions or problems with the Eaton Intelligent Power Manager (IPM), call your Local Distributor
or the Help Desk at one of the following telephone numbers and ask for a technical representative.
Please have the following information ready when you call the Help Desk:
l Model number
l Serial number
l Version number (if available)
l Date of failure or problem
l Symptoms of failure or problem
l Customer return address and contact information
If repair is required, you will be given a Returned Material Authorization (RMA) Number. This number must
appear on the outside of the package and on the Bill Of Lading (if applicable). Use the original packaging or
request packaging from the Help Desk or distributor. Units damaged in shipment as a result of improper
packaging are not covered under warranty. A replacement or repair unit will be shipped, freight prepaid for all
warrantied units.
NOTE For critical applications, immediate replacement may be available. Call the
Help Desk for the dealer or distributor nearest you.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 146
Chapter 15 Appendix A
Create an Action
Prerequisites
None
Example Procedure
1. Select Settings > Actions / Events.
2. In the right panel, click Create a new action.
3. Select the Action type you want to perform (E-mail, VM Host Power action, and so forth).
4. Select the Event on which you want the action to be launched.
5. Configure the Settings of the Action (see Figure 159).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 147
Appendix A
Prerequisites
None
Example Procedure
1. Select Management > Configuration Policy.
2. In the right Selection view panel, click Create new configuration policy. The Create new configuration
policy dialog displays (see Figure 160).
3. Select the pen icon for Class list to enable the configuration of:
- Asset Information
- Runtime threshold settings
- Power Source
- User Settings
4. In this example case, select (check) the Power Source checkbox to add the Power Source class, and then
click Ok (see Figure 161).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 148
Appendix A
5. Select the pen associated with Target nodes to add or remove classes in the configuration policy.
6. In this example, select nodes from the “Available nodes list” and transfer them to the “Selected nodes
list” using the right arrows, and then click Ok (see Figure 162).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 149
Appendix A
7. Then, in the “Configuration policy settings”, configure the correct power source (see Figure 163).
8. With this configuration, the three ESXi selected have the Power Source ups09.mbt.lab.etn.com.
Prerequisites
None
Example Procedure
1. Select Settings > System.
2. In the right panel, select Edit modules settings and enable Infrastructure Connectors.
3. Select Settings > Infrastructure Connectors.
4. In the right panel, select Add a connector. In the Add a connector dialog, select product type VMware
vCenter (see Figure 164).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 150
Appendix A
5. Check that the connection is listed in the Infrastructure Connectors panel (see Figure 165).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 151
Appendix A
Create a Filter
Prerequisites
None
Example Procedure
You can create a subview from Type to filter the VMHost, VMs, and vApps.
4. You should see several new filters, depending on the nodes you have.
Prerequisites
l Know VMware vCenter and VMware ESXi
l Know how to Add a VMware vCenter Connector
l Know how to Create a filter (Optional)
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 152
Appendix A
Example Procedure
1. Select Management > Configuration Policies.
2. Create a new configuration policy with the Class Power Sources Identification in the configuration policy
name field and class shutdown settings (see Figure 167).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 153
Appendix A
5. After the runtime threshold is reached, the action will be launched on each VMHost (shutdown in this
case).
Prerequisites
l Know how to install and connect on IPM web interface
l Know VMware vCenter and VMware ESXi
l Know how to Add a VMware vCenter Connector
l Know how to Create a filter (Optional)
Example Procedure
1. Select Settings > Actions / Events.
2. In the right panel, select Edit event rules.
3. Add a custom event (see Figure 169 and Figure 170).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 154
Appendix A
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 155
Appendix A
NOTE Before version IPM 1.50, a maintenance timer was used to match this object.
4. On the Rule definition dialog, select the source and the value (see Figure 171).
5. Select Settings > Actions / Events. In the right panel, click Create a new action.
6. From the Create new action dialog, select the Action type Host Power action. Click Save (see Figure 172).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 156
Appendix A
7. From the Create new action dialog, select the Events List (see Figure 172).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 157
Appendix A
8. From the Select associated events pop-up, check the Custom box for MaintenanceMode Event. Click Ok
(see Figure 173).
9. From the Edit Action screen, select the command, “EnterMaintenanceMode” (see Figure 174).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 158
Appendix A
12. If you want to have this action launch on several servers, you can create a configuration policy with them
and launch the command on the configuration policy.
Prerequisites
l Know VMware vCenter and VMware ESXi
l Know how to Add a VMware vCenter Connector
l Know how to Create event from EMP Temperature
l Know how to Create a filter (Optional)
Example Procedure
1. Select Settings > Action / Events.
2. Create a new action with action type, “VM migrate action.”
3. Select the Temperature Event created previously. Click Ok (see Figure 175).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 159
Appendix A
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 160
Appendix A
4. From the Edit action dialog, configure the settings (see Figure 176).
5. Select the VMs to migrate (VMs or configuration policy containing VMs).
6. Select the target Host.
Prerequisites
None
Example Procedure
1. Select Settings > Action / Events.
2. Click Edit event rules in the right panel.
3. Add a custom event (see Figure 177).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 161
Appendix A
4. Add a Trigger.
5. Select the Rule trigger on the environment Object “Temperature.”
6. Select the Source if you want to check only one EMP.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 162
Appendix A
7. Select the value and click Ok (see Figure 178 and Figure 179).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 163
Appendix A
SRM Packages
l SRM 5.1
l SRM 5.5
Prerequisites
l Java installed
l Knowledge of IPM Infrastructure Connectors
l Knowledge of VMware vCenter and VMware SRM
l Requires a Silver or Gold license to activate the IPM SRM module
Example Procedure
1. Select Settings > System.
2. Click Edit Modules Settings in the right panel.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 164
Appendix A
3. From the Edit modules settings pop-up, check the box for Site Recovery Management and click Save (see
Figure 180).
NOTE The Site Recovery Management selection is disabled with a Basic license.
4. You should now see a new column for SRM state in the Infrastructure Connectors panel (see Figure 181).
NOTE IPM automatically discovers the IP address of the SRM server through the
ExtensionManager and connects to it using the vCenter credentials.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 165
Appendix A
3. From the Edit action dialog, complete the fields for your SRM action (see Figure 182).
l Action name: the action name (String field)
l Events List: the events that will trigger the SRM Recovery Plan, in the above example, a “Runtime
Threshold reached” event is selected.
l Action Settings: the action specific parameters
- Recovery plan: the recovery plan that will be launched (Failover Mode)
NOTE All fields followed by an asterisk “*” are mandatory. See the “Advanced Events and
Actions” on page 25 for more informations.
4. After you are satisfied with your settings, you can save the configuration (see Figure 183).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 166
Appendix A
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 167
Appendix A
Prerequisites
l Know VMware vCenter and VMware ESXi
l Know how to Add a VMware vCenter Connector
l Know how to Create a filter (Optional)
Example Procedure
1. Select Management > Configuration Policies.
2. Click Create a new configuration policy in the right panel.
3. From the Create new configuration policy dialog, create a new configuration policy with the Class,
including Runtime Threshold Settings and Power Sources Identification (see Figure 185).
4. Select the Node to add in this configuration policy.
5. Configure the configuration policy settings with remaining capacity limit on 70%.
6. Click Save.
7. Copy the configuration policy and modify the Nodes List and the configuration policy settings to match
your environment constraints (see Figure 186).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 168
Appendix A
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 169
Appendix A
Prerequisite
l Know how to install IPM
l Know how to configure VMware Site Recovery Manager
l Know how to Create event from EMP Temperature
Example Procedure
1. Select Settings > System.
2. Click Edit modules settings in the right panel and enable Infrastructure Connectors and Site Recovery
Manager.
3. Click Save.
4. Select Settings > Infrastructure Connectors (see Figure 189).
5. In the right panel, click Add a connector. Select product type VMware vCenter
6. After it is created, make sure the SRM state column is in the Infrastructure Connector panel.
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 170
Appendix A
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 171
Appendix A
10. Select the event you configured previously (see Figure 191).
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 172
Appendix A
Eaton Intelligent Power Manager (IPM) User’s Guide v1.50 P-164000289—Rev 3 173