1. Attachment Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 source images in d2cDCO space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2. Branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. PDF version of the User Assistance for StruxureWare Operations 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. Getting Started Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5. System Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6. Server Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7. Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8. User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9. Troubleshooting Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10. User Assistance for StruxureWare Operations 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 Using this wiki-based user assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 What is new in StruxureWare Operations 7.1? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 Installing StruxureWare Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4.1 Configuring the StruxureWare Operations installation USB key for installation on an HP server . . . . . . . . . . . . . . . . . . . . .
10.4.2 Changing the location of the StruxureWare Operations Client temporary files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5 Installing StruxureWare Operations in a cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.1 Setting maxcontext in clusters with more than 2 nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.6 Running StruxureWare Operations in a cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7 Installing StruxureWare Operations in a virtual environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.8 Optimizing performance of StruxureWare Operations running on VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.9 Upgrading from previous versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.9.1 Upgrading to StruxureWare Operations 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10 Setting up the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.1 Managing users in the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.2 Managing user rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.2.1 Granting access to web services API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.2.2 Granting user rights to Work Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.3 Configuring external system integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.3.1 Configuring StruxureWare Central integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.3.2 Configuring VMWare vCenter integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.3.3 Configuring Remedy integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.4 Configuring e-mail settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.5 Migrating data from StruxureWare Central . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.5.1 Migrating data to a StruxureWare Operations cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.6 Migrating data from Emerson Aperture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.6.1 Emerson Aperture migration mapping overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.6.2 Enabling Emerson Aperture migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.10.7 Managing system licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11 Managing server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.1 Configuring system time synchronization (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.2 Mounting a Windows share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.3 Uploading data to the StruxureWare Operations server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.4 Backing up and restoring backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.4.1 Scheduling regular backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.5 Enhancing security on the StruxureWare Operations server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.6 Reconfiguring locale on the StruxureWare Operations server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.7 Managing StruxureWare Operations services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.11.8 Changing the IP address of the StruxureWare Operations server through Webmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12 Getting started with StruxureWare Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.1 Monitoring data center operations in Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.2 Exploring the infrastructure in map, floor and rack layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.3 The look and feel of the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.3.1 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.3.2 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.3.3 Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.3.4 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.4 Showing or hiding floor and rack views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.5 Reviewing system preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.6 Suite part number list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.7 Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.12.8 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13 Building the infrastructure and adding inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.1 Importing a design from the InfraStruxure Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.2 Creating Supporting Infrastructure Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.3 Configuring the room layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.4 Adding rows to a room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.5 Adding gaps and blocks to the room layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.6 Adding doors and windows to the room layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.7 Inventory report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8 Editing Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7
7
7
7
7
7
7
7
8
8
8
8
8
9
9
10
10
10
11
11
11
11
12
12
12
12
13
13
13
13
13
14
14
14
15
15
15
15
16
16
16
16
16
16
17
17
17
17
17
18
18
18
18
19
19
19
20
20
21
21
21
21
22
22
22
22
23
23
23
23
23
23

10.13.8.1 Custom Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.13.8.2 General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.3 Device Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.4 Mounting Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.5 New Custom Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.6 Physical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.7 Power Properties (rack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.8 Power Properties (rack PDU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.9 Power Properties (server, blade server, blade enclosure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.10 Power Properties (UPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.11 Pump Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.13.8.12 Room Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.14 Working with the Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.15 Working with the List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.15.1 Editing multiple items in List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.15.2 Exporting List View Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.16 Working with the Floor Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.16.1 Configuring floor weight carrying capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.16.2 Positioning components in the floor layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.16.3 Exporting Layout as Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.16.4 Floor Layout Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.16.5 Floor Layout right-click options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.17 Working with the Rack Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.17.1 Rack Layout Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.17.2 Rack Layout right-click options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.18 Configuring Blade Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.18.1 Valid blade configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.19 Configuring power connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.19.1 Power Dependency Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.19.2 Power Distribution Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.19.3 New Power Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20 Configuring cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.1 Performing cooling simulation in the Cooling view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.1.1 Simulating rack and CRAC cooling changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.1.2 Troubleshooting why Capture Index values do not display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.1.3 What does the cooling tool tip tell me? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.2 Working with raised floor environments in the Plenum view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.3 About designs with perforated tiles on a raised floor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.4 Working with the temperature map in the 3D view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.4.1 Customizing 3D colors and thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.5 About cooling redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.6 About the Capture Index (CI) colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.7 About Capture Index prediction models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.8 Cooling configuration accuracy and design guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.9 Optimizing the cooling configuration accuracy by adjusting power and cooling estimates . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.10 Understanding real-time temperature predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.11 Tips & Tricks - Cooling Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.12 Row-based or room-based cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.20.13 Cooling Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.21 Working with the Equipment Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.21.1 Editing multiple items in the Equipment Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.21.2 Filtering Equipment Browser (Search) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.21.3 Exporting Equipment Browser Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.21.4 Configuring Equipment Browser Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.21.5 Editing IP address through the Equipment Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.22 Working with the Equipment Placement Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.22.1 Rack-Mount Equipment Placement Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.23 Managing network configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.23.1 Configuring network ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.23.2 Network Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.23.3 Route Notation in Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.23.4 Network Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.23.5 Network Summary report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.24 Viewing external system data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.24.1 About peak and average power data retrieval from StruxureWare Central . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.24.2 Associating live data from an external system to the layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.24.3 Launching to device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.24.4 How removing a server affects power values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.24.5 The importance of system time synchronization for accurate power values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.25 Viewing alarms from external systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.25.1 Locating alarms on failing equipment in the layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.25.2 Showing alarms for selected equipment only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24
24
24
24
24
24
24
24
24
25
25
25
25
26
26
26
26
27
27
27
27
28
28
28
29
29
29
29
30
30
30
30
31
31
31
31
31
31
31
32
32
32
32
32
33
33
33
33
33
34
34
34
34
34
34
34
35
35
35
35
35
36
36
36
36
37
37
37
37
37
38
38

10.26 Optimizing the design by following the recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

10.26.1 Showing recommendations for selected equipment only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.26.2 Cooling Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.26.2.1 Maximum perforated tile airflow is exceeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.26.2.2 There is no perforated tile airflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.26.2.3 The room has no perforated tiles for the CRAC airflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.26.3 General Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.26.3.1 Equipment weight exceeds the weight limit of the floor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.26.3.2 Max load weight of rack has been exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.26.3.3 Rack contains overlapping equipment at U position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.26.3.4 The tags assigned to the rack equipment in the rack do not match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.26.4 License Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.26.4.1 You are approaching the amount of racks supported by your StruxureWare for Data Centers - Operations Suite license
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.26.4.2 You are approaching the amount of racks supported by your StruxureWare Operations - Capacity license . . . . . . 39
10.26.4.3 You are approaching the amount of racks supported by your StruxureWare Operations - Change license . . . . . . . 39
10.26.4.4 You are exceeding the amount of racks supported by your StruxureWare for Data Centers - Operations Suite license
40
10.26.4.5 You are exceeding the amount of racks supported by your StruxureWare Operations - Capacity license . . . . . . . . 40
10.26.4.6 You are exceeding the amount of racks supported by your StruxureWare Operations - Change license . . . . . . . . 40
10.26.4.7 You have reached the amount of racks supported by your StruxureWare for Data Centers - Operations license . . 40
10.26.4.8 You have reached the amount of racks supported by your StruxureWare Operations - Capacity license . . . . . . . . 40
10.26.4.9 You have reached the amount of racks supported by your StruxureWare Operations - Change license . . . . . . . . . 40
10.26.5 Power Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
10.26.5.1 Amount of rack PDU power outlets has not been configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.26.5.2 An invalid power path has been configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.26.5.3 Associated device data has been lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.26.5.4 Breakers in module must have unique power phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.26.5.5 Capacity group equipment is placed in multiple rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.26.5.6 Connection has not been configured between PDU and power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.26.5.7 Connection has not been configured between Power Panel and power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.26.5.8 Connection has not been configured between remote distribution panel (RDP) and power supply . . . . . . . . . . . . . 41
10.26.5.9 Equipment connected to this PDU draws more power than is supported by the power supply breaker . . . . . . . . . . 41
10.26.5.10 Equipment connected to this Power Panel draws more power than is supported by the power supply breaker . . 42
10.26.5.11 Equipment connected to this remote distribution panel (RDP) draws more power than is supported by the power
supply breaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.26.5.12 Equipment in this rack receives power from multiple power supply devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.26.5.13 Equipment is connected to a rack PDU outside this rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.26.5.14 Internal redundancy setup for UPS and group must match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.26.5.15 PDU and connected rack PDU are placed in different rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.26.5.16 PDU output voltage has not been configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.26.5.17 Power connection configuration is invalid for equipment in one or more racks in the group . . . . . . . . . . . . . . . . . . 42
10.26.5.18 Power distribution equipment must have unique breaker module numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
10.26.5.19 Power feed connection for UPS and group must match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
10.26.5.20 Power Panel output voltage has not been configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
10.26.5.21 Rack's estimated load exceeds group's peak load settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
10.26.5.22 Rack's power configuration does not support distribution redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
10.26.5.23 Rack does not support the group's peak load settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
10.26.5.24 Rack is not included in a capacity group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
10.26.5.25 Rack is without rack PDU or a rack PDU is not powered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
10.26.5.26 The average estimated load of the racks in the group exceeds the group's average load settings . . . . . . . . . . . . 44
10.26.5.27 The breaker configuration does not support rack's estimated load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
10.26.5.28 The breaker configuration in the Power Distribution properties does not match the measured power data . . . . . . 44
10.26.5.29 The capacity group supports a higher redundancy than this server requires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
10.26.5.30 The input voltage setting required by the equipment is not available in current rack . . . . . . . . . . . . . . . . . . . . . . . 45
10.26.5.31 The measured load exceeds the estimated load per phase designed for the rack . . . . . . . . . . . . . . . . . . . . . . . . . 45
10.26.5.32 The measured load exceeds the total estimated load configured for the rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
10.26.5.33 The measured load of the connected rack PDU is 0, but an estimated load has been configured for the rack . . . 45
10.26.5.34 The measured load of the UPS exceeds the total estimated load of the connected equipment . . . . . . . . . . . . . . . 45
10.26.5.35 The phase configuration for the connected server is not supported by the rack PDU . . . . . . . . . . . . . . . . . . . . . . 45
10.26.5.36 The Rack PDU output voltage setting does not match the output voltage of the connected PDU or Power Panel 45
10.26.5.37 The server should not be supplied from different phases on 1 UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.26.5.38 The UPS in the layout does not supply enough power to match the configured load of connected equipment in the
layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.26.5.39 This equipment in store room is connected to equipment in a room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.26.5.40 This server requires a higher redundancy than is available in the capacity group . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.26.5.41 UPS internal redundancy has not been configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.26.5.42 UPS power feed has not been configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.27 Configuring the PUE DCiE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.28 Using the PUE DCiE Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
10.29 Working with reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
10.29.1 Working with report filter templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

10.29.2 Customizing report designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.29.3 Working with localized reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.29.4 Audit Trail report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.29.5 Energy Cost report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.29.6 Rack U-Space report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30 StruxureWare Operations - Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.1 Setting up cable connection settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.2 Setting up a capacity plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.3 Capacity Planning - Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.4 Working with capacity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.4.1 Capacity Group Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.4.2 Capacity Groups right-click options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.5 Finding the best location for a new server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.6 Best Rack Advisor - Redundancy configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7 Enabling placement recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.1 Available copper-based network ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.2 Available fiber-based network ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.3 Capacity group redundancy support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.4 Capacity group supports equipment's redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.5 Equipment fits into rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.6 Floor supports weight of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.7 PDU supports rack PDUs voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.8 Rack airflow supports equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.9 Rack PDU supports equipment's load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.10 Rack PDU supports equipment's voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.11 Rack supports equipment's load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.12 Rack supports equipment's Watts per U-height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.13 Rack supports weight of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.7.14 Rack tags support equipment tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.8 Working with Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.8.1 Creating tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.8.2 Managing tags in the Equipment Browser or List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.8.3 Tag Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.9 Saving KPIs over time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.10 Simulating IT Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.10.1 Configuring Cooling Impact Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.10.2 Configuring Simulated Impact Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.10.3 Exporting Impact Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.10.4 Filtering Simulated Impact List (Search) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.11 Performing an impact analysis on virtual machine hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.11.1 Enabling Impact Analysis with a VMware vCenter Server setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.11.2 Locating virtual machines hosts with impact in the layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.11.3 Refreshing Virtual Machine Host data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.11.4 Removing the maintenance mode on a host with a VMware vCenter Server setup . . . . . . . . . . . . . . . . . . . . . . . .
10.30.11.5 Virtual Machine Host Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.11.6 Working with virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.12 Capacity reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.13 Branch Circuit Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.13.1 Configuring Branch Circuit Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.30.13.2 Working with Branch Circuit Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31 StruxureWare Operations - Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.1 Change Management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.2 Rack equipment planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.2.1 Planning changes to rack equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.2.2 Equipment Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3 Working with work orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.1 Creating a controlled automated work order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.2 Creating a custom work order without recorded tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.3 Identifying work order task and equipment relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.4 Creating and applying work order templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.5 Work Order reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.6 Deleting old work orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.7 Configuring work order administrative settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.7.1 Scheduling work order recurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.3.7.2 Setting up automatic e-mail notification on work order completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.4 Integration with the Remedy Change Management system from BMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.4.1 Viewing tickets from Remedy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.4.2 Associating Remedy tickets and work orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.31.4.3 Remedy integration process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32 StruxureWare Operations - Energy Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.1 About PUE and DCiE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.2 Power Dependency Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

48
48
48
48
49
49
49
49
49
49
50
50
50
50
50
51
51
51
51
51
51
51
52
52
52
52
52
52
52
52
53
53
53
53
53
54
54
54
54
54
55
55
55
55
56
56
56
56
57
57
57
57
58
58
58
58
59
59
59
59
59
59
60
60
60
60
60
60
61
61
61
61

10.32.3 Energy System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.32.3.1 Configuring Infiltration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.2 Configuring IT load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.3 Configuring Ventilation and Lighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.4 Creating scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.5 Associating scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.6 Script Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.6.1 Custom Java code in Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.6.2 Sample Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.6.3 Startup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.7 Energy Efficiency Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.8 Energy System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.9 Infiltration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.10 IT Load Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.11 Lighting Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.3.12 Ventilation Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.4 StruxureWare Central Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.5 Database Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.5.1 Sample Startup Script for Database Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.5.2 Sample Simple Database Query Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.5.3 Sample Database Query Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.6 Web Service Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.6.1 Sample Startup Script for Web Service Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.6.2 Sample Data Retrieval Script for Web Service Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.7 Energy Efficiency Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.7.1 Exporting dashboard graphs to an external web site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.32.7.2 Customization of exported dashboard graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.33 StruxureWare Operations - Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.33.1 Designing simulations in StruxureWare Operations - Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.34 StruxureWare Operations - Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35 StruxureWare Operations - Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.1 Installing StruxureWare Operations - Mobile on the mobile device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.2 Logging on to StruxureWare Operations - Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.2.1 Troubleshooting logon problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.3 StruxureWare Operations - Mobile main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.4 Local and server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.5 Working in local mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.6 Synchronizing local changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.7 Troubleshooting connection and synchronization problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.8 Alarms on StruxureWare Operations - Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.8.1 Closing Active Alarm Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.8.2 Enabling or disabling Pop-up Alarm Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.9 Work Orders on StruxureWare Operations - Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.9.1 Filtering the work order list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10 Asset Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.1 Scanning equipment bar codes into StruxureWare Operations - Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.1.1 Troubleshooting scan problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.2 Adding Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.3 Connecting Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.4 Moving Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.5 Deleting Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.6 Working with Pending Changes on StruxureWare Operations - Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.7 Assigning tags on StruxureWare Operations - Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.8 Defining customized properties for a piece of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.10.9 Equipment stages on StruxureWare Operations - Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.11 Performing a Rack Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.35.12 Troubleshooting operational problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36 StruxureWare Operations - PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.1 Initial Setup of StruxureWare Operations PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.1.1 Installing StruxureWare Operations PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.1.2 Configuring StruxureWare Operations PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.1.3 Configuring StruxureWare Operations PRO Pack Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.2 Working with StruxureWare Operations PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.3 Working with Impact Analysis in StruxureWare Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.4 Working with StruxureWare Operations PRO Pack views in System Center Operations Manager . . . . . . . . . . . . . . . . . .
10.36.5 Working with StruxureWare Operations PRO Pack PRO Tips in Virtual Machine Manager . . . . . . . . . . . . . . . . . . . . . . . .
10.36.6 Troubleshooting virtualization issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.7 StruxureWare Operations PRO Pack PRO tip implementation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.36.8 StruxureWare Operations - PRO Pack Supported Alarm Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.37 StruxureWare Operations - VIZOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38 StruxureWare Operations - Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.1 Installing the StruxureWare Operations Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

62
62
62
62
62
63
63
63
63
63
63
63
64
64
64
64
65
65
65
65
65
66
66
66
66
67
67
67
67
67
68
68
68
68
69
69
69
69
69
70
70
70
70
70
71
71
71
71
72
72
72
72
72
73
73
73
73
73
74
74
74
75
75
75
75
75
76
76
76
77
77
77

10.38.1.1 Installing the StruxureWare Operations Dashboard on the StruxureWare Operations server . . . . . . . . . . . . . . . . .
10.38.2 Configuring the initial setup of the StruxureWare Operations - Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.3 Configuring StruxureWare Operations KPI tabs and portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.4 Configuring a tab slide show on the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.5 Configuring the dashboard theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.6 Hiding the cursor on the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.7 Hiding the tool icons on the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.8 Hiding the welcome page on the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.9 Changing the dashboard administration credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.10 Displaying the configured dashboard on a screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.11 Accessing the StruxureWare Operations - Dashboard from any computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.12 Invoking the sign in page, even if the page was deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.13 Troubleshooting StruxureWare Operations - Dashboard issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39 StruxureWare Operations Web Service API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.1 Inventory Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.1.1 Inventory web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.1.2 Inventory By Filter Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.1.2.1 Inventory by filter web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.2 Power Path Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.2.1 Power path web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.3 Custom Properties Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.3.1 Custom properties web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.4 Impact Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.4.1 Impact web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.5 Capacity History Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.5.1 Capacity history web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.6 Tutorial - Accessing web service Java API using CXF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.40 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.40.1 Troubleshooting error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.40.2 Troubleshooting performance issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.41 Video Tutorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.42 White Papers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.43 Write to us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.44 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.45 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

78
78
79
79
79
79
79
79
79
79
80
80
80
80
80
81
81
82
82
82
82
83
83
83
83
84
84
84
84
84
84
85
85
85
87

Attachment Library
This is the library of attachments in this space to keep them in one place and allow for reuse by linking to this page from multiple pages. Any
changes to an attachment used in multiple pages only need to be done here.

source images in d2cDCO space

Branding
The following are registered trademarks of Schneider Electric, Inc., in the United States and other countries. {multi-excerpt:name=ISXC}
StruxureWare Central {multi-excerpt} {multi-excerpt:name=ISXCb} StruxureWare Central {multi-excerpt} {multi-excerpt:name=ISX} InfraStruxure
{multi-excerpt} {multi-excerpt:name=ISXb} InfraStruxure {multi-excerpt} {multi-excerpt:name=ISXCOLD} InfraStruxure Central {multi-excerpt}
{multi-excerpt:name=ISXOOLD} InfraStruxure Operations {multi-excerpt} {multi-excerpt:name=ISXCHMOLD} InfraStruxure Change {multi-excerpt}
{multi-excerpt:name=ISXMOLD} InfraStruxure Mobile {multi-excerpt} {multi-excerpt:name=ISXCPMOLD} InfraStruxure Capacity {multi-excerpt}
{multi-excerpt:name=ISXEEOLD} InfraStruxure Energy Efficiency {multi-excerpt} {multi-excerpt:name=ISXTLOLD} InfraStruxure Data Center Lab
{multi-excerpt} {multi-excerpt:name=ISXEEOLD} InfraStruxure Energy Efficiency {multi-excerpt} {multi-excerpt:name=ISXOPROOLD}
InfraStruxure Operations PRO Pack {multi-excerpt} {multi-excerpt:name=ISXO} StruxureWare Operations {multi-excerpt}
{multi-excerpt:name=ISXOb} StruxureWare Operations {multi-excerpt} {multi-excerpt:name=ISXCPM} StruxureWare Operations: Capacity
{multi-excerpt} {multi-excerpt:name=ISXCPMb} StruxureWare Operations: Capacity {multi-excerpt} {multi-excerpt:name=ISXCHM} StruxureWare
Operations: Change {multi-excerpt} {multi-excerpt:name=ISXCHMb} StruxureWare Operations: Change {multi-excerpt}
{multi-excerpt:name=ISXM} StruxureWare Operations: Mobile {multi-excerpt} {multi-excerpt:name=ISXMb} StruxureWare Operations: Mobile
{multi-excerpt} {multi-excerpt:name=ISXEE} StruxureWare Operations: Energy Efficiency {multi-excerpt} {multi-excerpt:name=ISXEEb}
StruxureWare Operations: Energy Efficiency {multi-excerpt} {multi-excerpt:name=ISXEC} StruxureWare Operations: Energy Cost {multi-excerpt}
{multi-excerpt:name=ISXECb} StruxureWare Operations: Energy Cost {multi-excerpt} {multi-excerpt:name=ISXD} InfraStruxure Designer
{multi-excerpt} {multi-excerpt:name=ISXDb} InfraStruxure Designer {multi-excerpt} {multi-excerpt:name=nonISX} non-InfraStruxure {multi-excerpt}
{multi-excerpt:name=nonISXb} non-InfraStruxure {multi-excerpt} {multi-excerpt:name=ISXCp} (StruxureWare Central) {multi-excerpt}
{multi-excerpt:name=ISXTL} StruxureWare Operations: Lab {multi-excerpt} {multi-excerpt:name=ISXOPRO} StruxureWare Operations: PRO Pack
{multi-excerpt} {multi-excerpt:name=ISXOPROb} StruxureWare Operations: PRO Pack {multi-excerpt} {multi-excerpt:name=ISXOPROAgent}
StruxureWare Operations: PRO Pack Agent {multi-excerpt} {multi-excerpt:name=ISXOPROAgentb} StruxureWare Operations: PRO Pack Agent
{multi-excerpt} {multi-excerpt:name=DCI} StruxureWare Operations: Insight {multi-excerpt} {multi-excerpt:name=StrW} StruxureWare
{multi-excerpt} {multi-excerpt:name=ISXOserver} StruxureWare Operations {multi-excerpt} {multi-excerpt:name=Vizor} StruxureWare Operations:
VIZOR {multi-excerpt} {multi-excerpt:name=Dashboard} StruxureWare Operations: Dashboard {multi-excerpt}

PDF version of the User Assistance for StruxureWare

Operations 7.1
Download

Download the PDF version of the User Assistance for StruxureWare Operations 7.1 here.

Getting Started Guide

{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Download the PDF version of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 7.1 Getting Started Guide [here|^Getting Started with StruxureWare
Operations 7.1.pdf]. {panel} Click the individual pages in the list to view them online.
{contentbylabel:label=quickstart|space=@self|showSpace=false|showLabels=false|maxResults=10000|sort=title}

System Administration Guide

{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Sorry, the pdf version is currently not available. {panel} {section} {panel} Click the
individual pages in the list to view them online. {contentbylabel:labels=system
administration|showLabels=false|max=10000|spaces=@self|operator=AND|sort=title}{panel} {section}

Server Configuration Guide

{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Download the PDF version of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 7.1 Server Configuration Guide [here|^StruxureWare Operations 7.1 Server
Configuration Guide.pdf]. {panel} {section} {panel} Click the individual pages in the list to view them online.
{contentbylabel:label=serverconfig|space=@self|showSpace=false|showLabels=false|maxResults=10000|sort=title}{panel} {section}

Installation Guide
{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Download the PDF version of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 7.1 Installation Guide [here|^StruxureWare Operations 7.1 Installation
Guide.pdf]. {panel} {section} {panel} Click the individual pages in the list to view them online.
{contentbylabel:label=installation|space=@self|showSpace=false|showLabels=false|maxResults=10000|sort=title}{panel} {section}

User's Guide
{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Sorry, the pdf version is currently not available. {panel} {section} {panel} Click the
individual pages in the list to view them online. {contentbylabel:labels=usage
quickstart|showLabels=false|showSpace=false|max=10000|spaces=@self|sort=title}{panel} {section}

Troubleshooting Guide
{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Download the PDF version of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 7.1 Troubleshooting Guide [here|^StruxureWare Operations 7.1
Troubleshooting Guide.pdf]. {panel} {section} {panel} Click the individual pages in the list to view them
online.{contentbylabel:label=troubleshooting|space=@self|showSpace=false|showLabels=false|maxResults=10000|sort=title}{panel} {section}

User Assistance for StruxureWare Operations 7.1

{panel:borderWidth=0|bgColor=9FAOA4}The purpose of this wiki is to provide an overview of the key features and explain both the basic and
more advanced usage of {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. The wiki-based user assistance contains the
latest updates and allows you to provide feedback or ask questions.{panel} h2. Looking for one of these guides?
{navmap:label_structure_en|wrapAfter=13|cellWidth=140px} h2. Looking for help on a specific feature? Type the words you are looking for in the
*Search box* in the top right corner. h2. Browsing what is available? Let the links in the *Navigation panel* to the left guide you to the information.
{tip:icon=false}*Tip*: If you do not see the panel, toggle the box next to the *Search box* in the top right corner.{tip} h2. Looking for a *printable
version* of the entire documentation set? Download the PDF version from [here|PDF version of the User Assistance for StruxureWare Operations
7.1]. [Using this wiki-based user assistance] [What is new in StruxureWare Operations 7.1?] [Getting started with StruxureWare Operations] [Tips
and Tricks] [Glossary]

Using this wiki-based user assistance

{panel:borderWidth=0|bgColor=9FAOA4}The purpose of this wiki is to provide an overview of the key features and explain both the basic and
more advanced usage of {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. When you select *Help>Online Help* in the
application (or press F1), this page opens. The wiki-based user assistance contains the latest updates and allows you to provide feedback or ask
questions.{panel} h2. Find what you are looking for Missing the previously provided context-sensitive help for a specific feature? Type the words
you are looking for in the *Search box* in the top right corner. Browsing what is available? Let the links in the *Navigation panel* to the left guide
you to the information. {tip:icon=false}*Tip*: If you do not see the panel, toggle the box next to the *Search box* in the top right corner.{tip}
Looking for a *printable version* of the entire documentation set? Download the PDF version from [here|PDF version of the User Assistance for
StruxureWare Operations 7.1]. h2. Tell us what you think Comment, complain, suggest... We are committed to providing you with high quality
documentation and you can help us to continually improve the documentation that we offer by telling us what you think. We appreciate all types of
feedback and look forward to hearing from you. Write to us by clicking [here|write to us]. You can also comment, make a request, or ask questions
directly on a page by clicking *Add Comment* at the bottom of the page. Our documentation team will handle the feedback. You must register as
a user on the wiki to be able to add comments. Try browsing the support site, including the forum, or FAQ for answers to your questions as the
information may not have made it into the product documentation yet. {panel}

What is new in StruxureWare Operations 7.1?

h1. New features and changes in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 7.1: h2. {expand_plain:Change
Management: Merged perspectives}In previous versions of the software, you did rack equipment planning in a separate *IT Change* perspective
and work order management in a separate *Work Orders* perspective. The functionality has been merged into an integrated flow in the
*Planning>Data Center* perspective. [More...|Rack equipment planning] !StruxureWare Operations Change^rackplanning_WO_Editor.png|thumbnail! {expand_plain} h2. {expand_plain:Change Management: BMC Remedy Integration}Integration
to more systems are now supported, among these are the BMC Remedy IT Service Management Suite. You can now configure integration with a
BMC Remedy server in *System Setup>External System Configuration*. When you have configured the system integration, ticket data from the
Remedy server is integrated into the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} layout in the *Change Management*
pane, and {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} work order data related to the tickets is integrated into Remedy.
[More...|Integration with the Remedy Change Management system from BMC] !Integration with the Remedy Change Management system from
BMC^ticketsinOps.png|thumbnail! {expand_plain} h2. {expand_plain:Change Management: New work order editor}A new work order editor has
been introduced. [More...|Working with work orders] !StruxureWare Operations - Change^rackplanning_WO_Editor.png|thumbnail! {expand_plain}
h2. {expand_plain:Change Management: Work order templates}You can now create work order templates to minimize repetitive work.
[More...|Creating and applying work order templates] !WO_templateeditor.png|thumbnail! {expand_plain} h2. {expand_plain:Change Management:
Schedule work order recurrence}A new setting has been introduced to configure recurrence of work orders. This is especially useful for managing
service maintenance tasks occurring with a certain interval. [More...|Scheduling work order recurrence] !Scheduling work order
recurrence^schedule_WO_recur.png|thumbnail! {expand_plain} h2. {expand_plain:Change Management: New work order overview perspective}A
new overview provides a filter-based drill-down overview of work orders in the system based on location, project code, assignee, and time. It
allows managers to do resource planning and avoid scheduling conflicts. [More...|Change Management overview] !StruxureWare Operations Change^change_overview.png|thumbnail! {expand_plain} h2. {expand_plain:Change Management: New dashboard portlets and KPI data

available}New Work Order List and Project Code portlets are available for the
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}. In the generic Data Center KPI portlet, you can add and combine
work order data: total, completed, overdue, not started, in progress. !portlet_WOList.png|thumbnail!!portlet_ProjectCode.png|thumbnail!
{expand_plain} h2. {expand_plain:Change Management: Work order cleanup}Over time, the amount of old work orders in the system will grow.
You can now perform a cleanup and delete work orders older than 400 days, that is work orders with a Needed by date of minimum 400 days
prior to today's date. Use this operation with caution. Once performed, there is no way of retrieving deleted work orders. [More...|Deleting old work
orders] !Deleting old work orders^wo_cleanup.png|thumbnail! {expand_plain} h2. {expand_plain:New master product catalog introduces a new
flow to adding equipment} You can open the master catalog and drag and drop equipment directly into your custom catalog and rearrange
products without the need to open a separate dialog box. You can right-click the custom catalog to add, rename, or delete categories and to copy
or delete products. Multiple users can apply changes to the catalog at the same time. The new master catalog includes new products, such as
windows, doors, and grilles. [More...|Working with the Catalog] !master_catalog.png|thumbnail! {expand_plain} h2. {expand_plain:Support for
windows and doors}Windows and doors are now available in the catalog and allow you to create a more precise model of the data center, making
it easier to navigate the room. !doors_windows.png|thumbnail! {expand_plain} h2. {expand_plain:Cooling: Support for grilles}Grilles are now
available in the catalog and allow you to configure ventilation through grilles. !verticalgrille.png|thumbnail! {expand_plain} h2.
{expand_plain:Branch Circuit Monitoring, mapping of multiple device sensors}Now you can associate multiple device sensors to one component
in the layout using drag-and-drop. [More...|Branch Circuit Monitoring] !Branch Circuit Monitoring^props_powerdistr_highlighted.png|thumbnail!
{expand_plain} h2. {expand_plain:Aperture Import}A new software service is available to support migration from Emerson Aperture. If enabled,
migration from Aperture can be executed through a configuration wizard in *System Setup>External System Configuration*.
!ApertureMigration.png|thumbnail! {expand_plain}

System requirements
The following requirements are based on preliminary test results. They are subject to change. h2. Minimum Server Requirements
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} Suite requires an additional server. It can be installed on dedicated
hardware or in a virtual environment. No operating system installation is required as it is included in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} installation. * Memory: 16 GB RAM * CPU: Multicore is preferred. More
CPU is only beneficial if multiple (5+) clients are accessing the server constantly. * Storage: 40 GB storage The setup has been tested
successfully on the following makes and models: ** HP DL380 ** Dell PowerEdge R710 ** Dell Blade PowerEdge M610 h2. Minimum Client
Requirements * Processor: 2 GHz Intel Core 2 Duo (or equivalent) * Hard disk: 500 MB free hard disk space for installation * Memory: 4 GB RAM
* Display: 1024x768 screen resolution with 16 million colors * Operating System: MS Windows XP Service Pack 2, MS Windows Vista, Windows
7, 32-bit recommended, Linux (mainly tested on Ubuntu) * Browser: Internet Explorer (v7 and up), Chrome, and Firefox You must have local
administration rights on the client computer. h2. Proxy settings for {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} The
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client uses the proxy settings from the operating system. If you are running
on Windows, you can configure the settings through the Internet Explorer connection options. h2. Server communication *Client/server
communication across a firewall requires specific port configuration:* If it is required that the client and server communicate across a firewall, you
must ensure the firewall allows for communication on the following ports: * Port 80: (TCP) - HTTP * Port 443: (TCP) - HTTP using SSL * Port
4457: (TCP) - JMS binding port * Port 4459: (TCP) - JMS binding port using SSL * Port 4460: (TCP) - JMS control port * Port 4462: (TCP) - JMS
control port using SSL Communication across a NAT firewall is not supported. *External communication between
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and external systems:* Here are some default port configurations for
external communication (outgoing). You can use different ports if required. * Ports 443 and 80: (TCP) - VMWare, SCOM, and
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} integration * Port 25: (TCP) - SMTP communication to e-mail server * Port
53: (TCP/UDP) - DNS communication to DNS server * Port 111: (TCP) - NFS mount * Port 123: (UDP) - NTP communication to NTP server * Port
139: (TCP/UDP)- SMB communication to NAS/SAN * Port 445: (TCP) - CIFS communication to NAS/SAN * Port 2049: (UDP) - NFS
communication to NAS/SAN *Communication in a cluster environment:* If you configured a
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} cluster environment, remember to open the port configured in the cluster
setup. *Communication between {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and Webmin:* Port configuration for
communication with the browser-based server administration module. * Port 10000 (TCP) || See also || [Installing StruxureWare Operations]
[Troubleshooting performance issues]

Installing StruxureWare Operations

To install {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, install the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, and then the clients. To install from a DVD, download the
StruxureWare Operations ISO and use your favorite application to burn the ISO to the DVD. Insert the DVD and follow the instructions in the
installation wizard. The following instructions describe how to configure and install from a USB key. h2. Configuring the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} installation USB key{anchor:configUSB} If you are configuring the USB key
*for installation on an HP server, read separate instructions [here|Configuring the StruxureWare Operations installation USB key for installation on
an HP server]*. Configuring an installation USB key for {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} only requires you to
run UNetbootin ^1^ using the Disk Image and copy the ISO file to the USB key. Subsequently, you can install the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} from the installation USB key to any computer according to your
licenses. Prerequisites: Before configuring the installation USB key, you must have * A USB key (>=2GB) * The StruxureWare Operations Installer
Image file ^2^ * The USB Creator Disk Image zip file ^2^ * An installation of UNetbootin ^1^ on the computer you use for the USB key
configuration ^1^ You can download UNetbootin from [here|http://unetbootin.sourceforge.net/]. ^2^ You can download these from a location
provided by the support team. To locate the telephone number for the support you need, visit [Contact
Us|http://www.apc.com/site/software/index.cfm/Contact/]. \\ {section}{column:width=50%} # Format the USB key in FAT32 or VFAT
(recommended to ensure the installation is done from a clean USB key). ## Plug in the USB key and follow the next steps (these apply to
Windows). ## Double-click *My Computer* on the desktop. ## Right-click the USB key drive, and select *Format*. ## In the pop-up window, select
*Quick Format*. # Start UNetbootin ^1^. # Select *Diskimage* and make sure *ISO* is selected in the drop-down menu. Browse to the
StruxureWareOperations-USB-Diskimage-\[buildnumber\].zip file. # Select *Type*: *USB drive*. # Select *Drive*: The appropriate USB Drive (from
step 1). # Click *OK*. The disk image is now copied to the USB key. # When the operation is done, click *Exit*. # Copy the StruxureWare
Operations Installer Image file, StruxureWareOperations-\[buildnumber\].iso, to the USB key. # Safely remove the USB key. You now have a
bootable USB key and can install the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server to any computer
according to your licenses. {column}{column:width=50%} (Illustration of step 3-5) \\ !Unetbootin.png|thumbnail! {column}{section} h2. Installing the

{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server from the preconfigured installation USB

key{anchor:Installserver} It is recommended that you follow the on-screen instructions and select the default options unless you have specific
requirements. # Insert the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} installation USB key. # Connect a keyboard and
display. # Ensure the BIOS settings enable the server to boot from the USB key and the server is connected to the network during the entire
installation process. # In the *StruxureWare USB Install* menu, select *StruxureWare* or *StruxureWare Cluster* according to your license. # In
the language menu, select language and country. # In the prompt for partitioning method, select *Guided - use entire disk* (recommended option).
# In the next prompt, select disk to partition. # If you are installing a cluster setup, cluster preconfiguration is needed. Otherwise, the system
should retrieve the server information such as IP address automatically. # When the server reboots, remove the USB key. # When the cursor
reaches the login prompt, enter the root credentials (default: {{root/apc}}). To change the password, see [here|Enhancing security on the
StruxureWare Operations server#changeroot]. The {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server has been
installed and is ready for use. \\ \\ {tip:icon=false}*Tip*: Before leaving the command prompt, type {{ifconfig}} and make a note of the IP address of
the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. You need this address to install the clients and perform
[server management tasks|Managing server settings].{tip} h2. Installing {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}
clients{anchor:Installclients} Prerequisite: The server installation has been completed. # On the client computer, type the server's IP address in a
Web browser. # On the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page, click to download
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and follow the instructions in the installation wizard. # On the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page, click to download the add-on modules
according to your licenses and follow the instructions in the installation wizard. # Repeat the installation steps on all client computers. || See also ||
[System requirements] [Managing system licenses] [Installing StruxureWare Operations in a cluster environment]

Configuring the StruxureWare Operations installation USB key for installation on an HP

server
Configuring an installation USB key for installing {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} on an HP server requires
you to run UNetbootin ^1^ and follow the below instructions. Subsequently, you can install the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} from the installation USB key to any computer according to your
licenses. Prerequisites: Before configuring the installation USB key, you must have * A USB key (>=2GB) * The StruxureWare Operations Installer
Image file ^2^ * The USB Creator Disk Image zip file ^2^ * An installation of UNetbootin ^1^ on the computer you use for the USB key
configuration ^1^ You can download UNetbootin from [here|http://unetbootin.sourceforge.net/]. ^2^ You can download these from a location
provided by the support team. To locate the telephone number for the support you need, visit [Contact
Us|http://www.apc.com/site/software/index.cfm/Contact/]. \\ {section}{column:width=50%} # Format the USB key in FAT32 or VFAT
(recommended to ensure the installation is done from a clean USB key). ## Plug in the USB key and follow the next steps (these apply to
Windows). ## Double-click *My Computer* on the desktop. ## Right-click the USB key drive, and select *Format*. ## In the pop-up window, select
*Quick Format*. # Start UNetbootin ^1^. # Select *Diskimage* and click ... to browse to and select the .iso file. # Select *Type*: *USB drive*. #
Select *Drive*: The appropriate USB Drive (from step 1). # Click *OK*. The disk image is now copied to the USB key. # When the operation is
done, click *Exit*. # Safely remove the USB key. You now have a bootable USB key and can install the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server to any computer according to your licenses.
{column}{column:width=50%} \\ !Unetbootin_HPinstall.png|thumbnail! {column}{section} ||See also|| [Installing StruxureWare Operations]
[Installing StruxureWare Operations Server|Installing StruxureWare Operations#Installserver] [Installing StruxureWare Operations
Clients|Installing StruxureWare Operations#Installclients]

Changing the location of the StruxureWare Operations Client temporary files

Error: The XML content could not be parsed. There is a problem at line 8, column 62. Parser message: Unexpected character 'S' (code 83)
expected '=' at [row,col {unknown-source}]: [8,62]

Installing StruxureWare Operations in a cluster environment

h2. About {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} cluster environments Running
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} in a clustered environment requires low network latency. Therefore, it is
generally recommended to have the clustered servers installed on the same data center site. All nodes in the cluster setup must have a static IP
address. h2. Setting up a clustered environment The following instructions describe how to configure and install from a USB key. To install from a
DVD, download the ISO and diskimage.zip files to the DVD from the location provided by the support team. To locate the telephone number for
the support you need, visit [Contact Us|http://www.apc.com/site/software/index.cfm/Contact/]. Use your favorite application to burn the ISO to the
DVD. Insert the DVD and follow the instructions in the installation wizard. To set up the clustered environment with multiple servers, perform these
steps for each server that will be a node in the cluster. {tip:icon=false}*Recommendation*: Follow the on-screen instructions and select the default
options unless you have specific requirements.{tip} Prerequisite: [Install StruxureWare Operations|Installing StruxureWare Operations]. # Insert
the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} installation USB key. # Ensure the server boots from the USB key and
is connected to the network during the entire installation process. # Connect a keyboard and display. # In the StruxureWare USB Install menu,
select StruxureWare Cluster and wait for the installation to finish. # When the server reboots, remove the USB key. # Insert a preconfigured
installation USB key into each server that will be a node in the cluster setup and perform the above steps for all nodes before continuing. If you do
not perform these steps for all nodes before continuing to the cluster preconfiguration, it is to be expected that the server log will include errors.
This happens because the system tries to communicate with nodes that have not been set up yet. h2. Configuring the first (primary) node:
Prerequisite: You have followed the above steps. # When the cursor reaches the login prompt, enter {{root/apc}}. To change the password, see
[here|Enhancing security on the StruxureWare Operations server#changeroot]. # In the Cluster preconfiguration menu, select 2. # Enter the virtual
IP address of the cluster. This is the IP address that will serve as the common entry point to the cluster. It must be a proper IP address and it must
not be used by any other entities on the network. # Enter the common name for SSL certificate generation. Writing the IP address or hostname
here prevents access through other IP addresses or hostnames. # Enter the cluster multicast IP address postfix to be used for communication
between the nodes in the cluster (one address for all nodes, 224.1.xxx.xxx). In order for the nodes in the cluster to be able to communicate with
each other, they need a communication channel. This channel is an IP address and a port number. The IP address must not be used by any other
systems. The first two digits are fixed at 224.1 and you must select the final 2 digits (within the range 1-255). # Enter the cluster multicast IP port
number to be used for communication between the nodes in the cluster (within the recommended port number range 1024-65000). This port
number will be used in conjunction with the IP address that was just entered. # Enter a unique peer ID of this node within the range 1-255. # Enter

the virtual router ID. In order to create the common entry point to the cluster, a router is emulated through VRRP (Virtual Router Redundancy
Protocol) with that IP. This virtual router has an ID at it must be unique within the space of virtual routers configured on the network. # Wait for
JBoss to start up before continuing to the next node. The installation has finished when the word Started appears. You can monitor the web page
by typing the IP address of the node in a Web browser. Once the web page displays, the server has finished starting up. If you do not have Web
access, you can also monitor the node in this way: Type: service operations open-server-log and press Shift+F, and then Ctrl+C followed by Q to
stop executing the service operations command. Remember to configure [system time synchronization|Configuring system time synchronization
(NTP)]. h2. Configuring the additional nodes: Prerequisite: You have followed the above steps. # When the cursor reaches the login prompt, enter
{{root/apc}}. To change the password, see [here|Enhancing security on the StruxureWare Operations server#changeroot]. # In the Cluster
preconfiguration menu, select 3. # Enter the virtual IP address of the first node that was set up in the cluster. # Enter the root credentials for the
primary node. # Enter a unique ID of this node. (See explanation above.) # Wait for JBoss to start up on one node before continuing to the next
node. The installation has finished when the word Started appears. You can monitor the web page of the individual node by typing the IP address
of the node in a Web browser followed by :8080. Once the web page displays, the server has finished starting up. If you do not have Web access,
you can also monitor the nodes in this way: Type: service operations open-server-log and press Shift+F, and then Ctrl+C followed by Q to stop
executing the service operations command. When a following node is started, its database could be corrupt or "dirty". This means that it is
detached from the cluster, and that write operations will not be committed to this database. To remedy this, attach the database to the cluster.
You must do this on a node in OK state. To attach a database to a cluster: # Type the command {{service operations attach-db-node}}. The
command will display a list of the databases in the cluster and their state. The new database might be in a detached state. # Select the detached
database and press Enter. This will synchronize the new database with the database(s) already in the cluster. To attach the database through the
Webmin interface: In *System>StruxureWare Operations* *Status* tab, select the detached PostgreSQL Database and click *Attach DB*. Read
more [here|Managing StruxureWare Operations services]. {tip:icon=false}*Note*: This operation will block the cluster while synchronizing, which
may result in some warnings in the server log (about connections being destroyed). This is expected and should not cause any concern.{tip} If all
nodes are in OK state, click Ctrl+C to stop execution of the attach command. The cluster environment has now been set up and you can continue
to install the licenses. You can start running the application immediately for a trial period of 30 days after which you need to activate the real
licenses. Remember to configure [system time synchronization|Configuring system time synchronization (NTP)]. || See also || [Managing system
licenses] [Running StruxureWare Operations in a cluster environment|Running StruxureWare Operations in a cluster environment] [Configuring
system time synchronization (NTP)|Configuring system time synchronization (NTP)] [Migrating data to a StruxureWare Operations cluster
environment]

Setting maxcontext in clusters with more than 2 nodes

{section}{column:width=50%}If you are configuring a cluster environment with more than 2 nodes, you must set maxcontext: # Log on to the
physical node using secure shell. # Navigate to this file on the node: {{/etc/apache2/sites-enabled/000-default}}. # Add this line: {{Maxcontext
500}} to the file below the line {{-- MaxKeepAliveRequests 0}}. The line must be added to all nodes in the cluster. # Restart Apache. See
[here|Managing StruxureWare Operations services]. # Stop JBoss (StruxureWare Data Center Operation) on all servers and restart them one by
one. {column} {column:width=50%} !maxcontent.png|thumbnail! {column} {section} ||See also|| [Installing StruxureWare Operations in a cluster
environment] [Managing StruxureWare Operations services]

Running StruxureWare Operations in a cluster environment

For improved performance, you can run {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} in a [clustered environment with
multiple servers|Glossary#cluster]. When running {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} in a clustered
environment, you must have a Cluster Node license for each node in the cluster (besides the initial
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server). For example, a cluster setup with 3 servers requires: * 1
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} license * 2 Cluster Node licenses If a node has been unavailable, for
example rebooted, its database will be considered corrupt or "dirty" and will not automatically be attached to the cluster once the node comes up
again. This will trigger an alarm in {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} and can also be seen through the
command {{service operations print-db-status}}. A database that is considered dirty will be in a detached state. In order to remedy this, you must
have root credentials to the server and run the command {{service operations attach-db-node}}. This will block the cluster and synchronize the
databases. This command is likely to produce warnings and exceptions in the server log files, but this is expected and should not cause any
concern. {tip:icon=false}*Note*: Because this operation blocks the cluster, it is not safe to run it while a server node is starting up.{tip} When
troubleshooting errors in a clustered environment, you must log on to each node and get the log files. [More...|Troubleshooting error messages] ||
See also || [Managing system licenses] [Installing StruxureWare Operations in a cluster environment]

Installing StruxureWare Operations in a virtual environment

{tip:icon=false}*Recommendation*: When installing {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} in a virtual environment,
select Debian operating system (version 5 or 6, 64 bit) as the guest operating system.{tip} If you follow this recommendation, the configuration of
virtual hardware, especially drivers, becomes easier. During the configuration, you can simply select the default options that the system suggests.
These default options are based on knowledge about the driver installation on Debian 5 and 6, 64 bit. If the Debian guest operating system type is
not available in the virtual environment, configure the virtual hardware to be compatible with
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: CPU architecture: 64 bit SCSI Controller: LSI Logic Parallel Network
adaptor type: E1000 Apart from this recommendation, the same instructions and system requirements apply to the virtual environment as to a
stand-alone server. For example, you may experience issues with the installation if you do not assign enough vRAM. The recommendation is 16
GB RAM (as for a stand-alone server). ||See also|| [Installing StruxureWare Operations] [System requirements]

Optimizing performance of StruxureWare Operations running on VMware

You can deploy the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} platform on a physical or virtual server. If you deploy as
a virtual server on VMware, you can install VMware tools to optimize performance significantly. !Configuring the room layout^video24x20.jpg!
Follow the below steps or watch this short [video tutorial|Video Tutorials#VMwareinstalltools] (5:02). # Open the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server console, for example through the vSphere Client. # Log on to
the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server with the root credentials (default: {{root / apc}}) and press
*Enter*. # Enable Debian packages. ## Type {{nano /etc/apt/sources.list}} to open the file and press *Enter* ## Place the cursor in front of each
line and remove #. Press *Ctrl+X* to save and exit. ## Type {{Y}} to the save buffer question and press *Enter*. # Press *Ctrl+X* to exit and save.

# Update the package cache: Type {{aptitude update}} and press *Enter*. # Install development packages: Type {{aptitude install build-essential
linux-headers-`uname -r`}}.\\ \\ {tip:icon=false}*Tip*: Use back quote ` not ' (Alt+96).{tip} # If prompted to continue, press Y. # Insert a virtual CD in
the virtual machine's drive: Select *Inventory > Virtual Machine > Guest > Install/Upgrade VMware Tools* (in the vSphere Client). The option may
be located in another menu in other VMware products, such as Player or Workstation. # Click *OK* to the *Install VMware Tools* message. #
Mount the CD in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: Type: {{mount /dev/cdrom /mnt/}} and press *Enter*. The
*mount: block device...* message is expected. The VMware Tools on the CD is now available on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. # Extract the VMware Tools from the CD to the server: Type
{{tar xvf /mnt/VMwareTools-\*.tar.gz -C /tmp/}} and press *Enter*. # Run the installer: Type {{/tmp/vmware-tools-distrib/vmware-install.pl}} and
press *Enter*. You will be prompted with questions and instructions. # Press *Enter* to all of these. VMware Tools are now installed on the server.
# Comment all lines in /etc/apt/sources.list again: ## Type {{nano /etc/apt/sources.list}} to open the file and press *Enter*. ## Place the cursor in
front of each line and type #. Press *Ctrl+X* to save and exit. ## Type {{Y}} to the save buffer question and press *Enter*. # Open the *Summary*
tab and verify the line VMware Tools: OK (in the vSphere Client). The option may be available in another place in other VMware products, such as
Player or Workstation.

Upgrading from previous versions

Supported upgrades of {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: Migration from any version 6.x to any version 7.x,
for example from 6.2 to 7.0.2. Upgrades from previous versions of 7.x to the latest version. || From \\ || Migrate to || | 6.0 \\ 6.1 \\ 6.2 \\ | 7.x \\ | ||
From || Upgrade to || | 7.0 \\ | 7.0.1 \\ | | 7.0.1 \\ | 7.0.2 \\ 7.1 \\ | | 7.0.2 | 7.1 \\ | || See also || [Upgrading to StruxureWare Operations 7.1]
[d2cDCO70:Upgrading to StruxureWare Operations 7.0] [d2cDCO70:Upgrading to StruxureWare Operations 7.0.1] [d2cDCO70:Upgrading to
StruxureWare Operations 7.0.2]

Upgrading to StruxureWare Operations 7.1

Upgrading to {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} version 7.1 from version 7.0.1 or 7.0.2 takes about 10
minutes. You must have a valid service contract to be able to download this version. If upgrading a cluster environment, you must only upload the
upgrade file to one node. The upgrade scripts apply the upgrade to all the cluster nodes. However, you must ensure all cluster nodes run and can
access the upgrade file before beginning the upgrade. If you upgrade in a cluster environment, the upgrade takes up to about 20 minutes. #
Download the upgrade file and copy the MD5 key from a location provided by the support team. To locate the telephone number for the support
you need, visit [Contact Us|http://www.apc.com/site/software/index.cfm/Contact/]. #* struxureware-operations-upgrade-7.1.tgz: File with the new
version of the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server and scripts to upgrade
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} # Upgrade
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} ## Open the Webmin web interface by typing the address of your
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server followed by :10000 in a Web browser, https://yourservername:10000.
## Log on to Webmin using the root credentials (default root/apc). ## Select *System>StruxureWare Operations* to open the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} configuration module. ## Select *Module Config*. ## In *Upgrade directory*,
verify a directory has been set. If not, type {{/data/upgrade}}. ## Select *System>StruxureWare Operations* again to open the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} configuration module. ## In the *Upgrade* tab, select upgrade file and
browse to the location of the downloaded struxureware-operations-upgrade-7.1.tgz file. ## Copy the md5 key (available from the download page)
and paste it into the *MD5 key* field in the *Upgrade* tab. ## Click *Upgrade*. # When you have completed the upgrade, download the latest
version of the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client. ## To open the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page, type the address of your
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server in a Web browser, https://yourservername. ## Click to download
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and follow the instructions in the installation wizard. ## Click to download
the add-on modules according to your licenses and follow the instructions in the installation wizard. ||See also|| [Upgrading from previous
versions] [Managing server settings in the Webmin interface|Managing server settings]

Setting up the system

{section}{column:width=50%}{excerpt:hidden=false}In the *System Setup* menu, you find options to perform system administration tasks, if you
have the appropriate user rights. {excerpt} [*User Rights and Authentication*|Managing users in the system] allows you to manage user rights and
authentication servers. [*External System Configuration*|Configuring external system integration] allows you to set up integration to other systems
and manage the server configurations. [*E-mail Settings*|Configuring e-mail settings] allows you to set up e-mail notification functionality.
[*Migrate from StruxureWare Central*|Migrating data from StruxureWare Central] allows you to move data from previous versions to the new
stand-alone {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. *Migrate from Emerson Aperture* allows you to
migrate data from Emerson Aperture. This option is not available as default but a new software service is available to support this migration. For
further information, contact your local sales representative. [*System Licenses*|Managing system licenses] allows you to manage licenses.
{column} {column:width=50%} !menu_systemsetup.png|border=1! {column} {section} || See also || [Managing server settings] [Reviewing system
preferences]

Managing users in the system

{excerpt:hidden=false}In *System Setup>User Rights and Authentication*, you can set up users, user rights, and remote authentication servers.
To have access to these settings, you must be logged on to the system as a user administrator, i.e. the *User rights and Authentication Servers*
check box has been selected.{excerpt} When you add a new user, you are setting up a local user on the StruxureWare Operations server by
default. The user's e-mail address is used by the system to send automatic notifications, e.g. related to work order assignments (StruxureWare
Operations: Change feature). If you are setting up a remote user, you must fill out the information on the *Authentication Servers* tab to have the
information supplied by that server. h2. Managing local users Unless you set up a remote user as described below, new users are added as local
users on the StruxureWare Operations server. # Add and edit users in the system by using the buttons in the *Users* section of the *Users* tab. #
Fill out the user information, including defining that it is a local user. When you are setting up a local user, user information is stored directly on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. This method provides the ability to create user accounts
without the need to connect to any external systems or repositories. The user's e-mail address is used by the system to send automatic
notifications, e.g. related to work order assignments ({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature). h2.
Managing remote users # Fill out the information on the *Authentication Servers* tab. # Add and edit users in the system by using the buttons in

the *Users* section of the *Users* tab. # To fill out the user information, select *Remote* and the predefined authentication method from the
drop-down list. The name, e-mail address, and password data is supplied by the authentication server. When you are setting up a remote user,
user information is stored on * {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server as a remote repository with user
information. The {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server requires connection setup to the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server in order to obtain the user information. * LDAP or Active Directory
server. The {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server requires connection setup to the server and logon
information is required. When a remote user attempts to log on to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true}
server, the user credentials (user name and password) are sent to the authentication server associated with that user. It is that server, and not the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, that authenticates the log on attempt. User groups are not
supported in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and you cannot import user groups from a remote
authentication server. ||See also|| [Setting up the system] [Managing user rights]

Managing user rights

{section}{column:width=50%}{excerpt:hidden=false}Granting global system rights and fine-grained permissions for individual parts of the
application allows you to restrict access and protect system functions and locations and rooms that only you or a subset of your team is allowed to
see or edit.{excerpt} # Select the system functions that the user needs access to. {tip:icon=false}*Note*: Add-on modules are available for
selection here, if you have valid licenses on the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server.{tip} # Select if
the user needs access to features in the *Planning Data Center* perspective. # Select which locations and rooms the user needs access to, and if
the access should be restricted to only viewing or if editing rights should be applied. h2. Granting system administration rights: Select *System
Configuration*. This user will be able to access the *System Setup* menu items (except *User Rights and Authentication Servers*). Provided the
options have been selected, this user will be able to: * Configure external system integration for allowing communication between the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server and external systems, e.g. receiving alarms and measured
data from monitored devices. * Configure e-mail settings for enabling the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server to send automatic e-mails. * Migrate data from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} as part of the process to upgrade e.g. from version 6.2. * Manage system
licenses to the available modules. h2. Granting user administration rights: Select *User Rights and Authentication Servers*. This user will be able
to access *System Setup>User Rights and Authentication Servers* and add or edit users in the system, as well as their user rights to the various
parts of the application. h2. Granting rights to use the system: Clear *User Rights and Authentication Servers* and *System Configuration* and
select the rest of the check boxes. This user will be able to use all features in the system but will not be able to perform system configuration or
change user rights. Restrict the rights by clearing the check boxes to the different parts of the application as required, e.g. access to reports or
alarms. h2. Granting restricted rights to locations or rooms in the system: Select *Planning Data Center* to allow the user to access this
perspective. Apply the below fine-grained rights to the various locations and rooms. For example, a user might need access to edit only in one
room but view all rooms. Some settings are dependent on others, e.g. a user with access to Energy Efficiency configuration must also be granted
edit rights to all rooms. Until you make a change to the rights in a location or room, the rights of the global location will apply (highlighted check
box). Subsequently, when a user creates a room, the rights to this room will be the same as to the location in which it is placed. You can then
change existing rights to rooms as required. {column} {column:width=50%} !User Access Rights.png|thumbnail! {column}{section} ||See also||
[Managing users in the system] [Granting access to web services API] [Granting user rights to Work Orders]

Granting access to web services API

If you have been granted the necessary user rights, you can integrate with third party systems using the web service API. # Select *System
Setup>User Rights and Authentication*. # In the *Users* tab, select the user you want to grant this right, select *Web service APIs* and save and
close. The user is now able to create a web service account and access the data exposed by the system. ||See also|| [d2cDCO70:Managing user
rights] [d2cDCO70:Saving KPIs over time] [d2cDCO70:Initial Setup of StruxureWare Operations PRO Pack] [StruxureWare Operations Web
Service API]

Granting user rights to Work Orders

Users who have been granted the necessary user rights can create and work with work orders. To grant these rights: # Select *System
Setup>User Rights and Authentication*. # In the *Users* tab, select the user you want to grant this right, select *Work Orders* and save and
close. The user is now able to create and work with work orders, and if the system integration has been configured, he can also track Remedy
tickets and associate these to work orders. *Work Orders* is only available if the required
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} license is installed on the server. ||See also|| [Managing user rights]

Configuring external system integration

{section}{column:width=50%}{excerpt:hidden=false}In *System Setup > External Systems Configuration*, you can set up integration with an
external system. Select the type of server, e.g. {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} or VMWare vCenter server,
and enter the server communication data.{excerpt} Once the communication between the servers has been established, the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server retrieves alarms and measured data from the external
monitoring system or migration data from the virtualization system. When you have configured the physical location of these real-world devices,
the system can guide you and show any active and potential problem areas in your data center. Alarms and migration data is collected in real time
and allows you to monitor and react instantly on critical data. Measured data from the external systems will be collected daily, at the time of day
when you first set it up, and every day thereafter. Measured data is kept on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server for 400 days. You must ensure [time synchronization|The
importance of system time synchronization for accurate power values] has been configured for the servers. {column} {column:width=50%}
!externalsystem_Central_28March.PNG|thumbnail! {column} {section} ||See also|| [Viewing external system data] [The importance of system time
synchronization for accurate power values]

Configuring StruxureWare Central integration

{section}{column:width=50%}h2. Integrating with a {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server Configure user
credentials to allow {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to communicate with the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server and receive device data and alarms. It is possible to integrate with
multiple {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} servers. # Set up the server connection in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. ## Select *System Setup>External System Configuration*. ## Click *Add

server*, and select *{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}* as the server type. ## Type the

{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server information. ##* Server identification, such as name, IP, port, and
credentials. ##* Timeout settings for connection and response. *Connection timeout (secs)*: When you configure server connection and
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} tries to connect to
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}, this time specifies how long
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} will wait for
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} to respond. *Response timeout (secs)*: When
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} will subsequently request
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} to send device data, this time specifies how long
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} will wait for
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} to respond. ##* Data collection retrieval, such as time period to store power
data, interval for asking {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} for updated device and power data. ## Type the
callback information to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. ## Click *Test* to test the
connection. h2. Configuring a secure connection If you want to ensure a secure connection for the data exchanged between the systems, follow
these instructions to ensure the certificate is trusted on both {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} and
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} servers. # Access the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server management interface to access the certificate. ## Launch the
Webmin web interface by typing the address of the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server in a Web
browser and click *Server Configuration*. ## Log on to Webmin using the root credentials (default: {{root / apc}}). To change the password, see
[here|Enhancing security on the StruxureWare Operations server#changeroot]. ## In the Webmin interface menu, select *System>Upload and
Download*. ## Open the *Download from server* tab. ## Browse to the certificate: {{/etc/apache2/ssl/certificate.crt}} and click *Download*. ##
Open the .crt file with a text editor, such as Notepad. ## Select all and copy the contents (Ctrl+A/Ctrl+C). # Make the certificate available to
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}. ## Launch
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}. ## Select *System>Server Administration Settings>Server SSL
Certificates...* ## Click *Add...*, right-click and select *Paste* to paste in the contents of the .crt file (from above step), and click *Add*. The
connection has been set up and the certificate is trusted on both servers. {column} {column:width=50%} !Configuring external system
integration^externalsystem_Central_28March.PNG|thumbnail! {column} {section} ||See also|| [Viewing external system data] [The importance of
system time synchronization for accurate power values]

Configuring VMWare vCenter integration

{section}{column:width=50%}Configure the server communication preferences between
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and VMware vCenter Server. # Type the logon information of the vCenter
server to connect to: host name / IP address, port number, and user credentials. # For a high-security logon session, select *Use SSL* and accept
the certificate. Ask the vCenter Server administrator for details if you are unsure whether to use SSL. The user on VMWare vCenter must "Be able
to poll vCenter for information regarding the virtual hosts on the servers". Optional: * Set a server in "maintenance mode". * Add an "annotation" to
a server. {column} {column:width=50%} !externalsystem_VMWare.png|thumbnail! {column} {section} || See also || [Performing an impact analysis
on virtual machine hosts] [Working with virtualization]

Configuring Remedy integration

{section}{column:width=50%} Set up server communication preferences to allow the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server to communicate with the Remedy server and exchange ticket
data. When you have configured the integration, Remedy tickets will show in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and users can associate them to work orders. When the user completes
work orders in {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true}, this update is transferred back to Remedy. In this
way, the configuration ensures an integrated process from new ticket in Remedy through work order tasks in
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} to completed ticket in Remedy. h2. Configuring the server
communication and user credentials # Select *System Setup>External System Configuration*. # In *Type*, select *Remedy Server*. # Type the
logon information of the Remedy server to connect to: #* *Name* #* *Host* (IP address) #* *Remedy Server Name* #* *Port* #* User credentials
# For a high-security logon session, select *Use SSL* and accept the certificate. Ask the Remedy Server administrator for details if you are
unsure whether to use SSL. # Set the interval between which the system is to check for updates (Default: 300 secs). h2. Configuring a filter
defining which Remedy tickets to show in {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} The *Remedy Tickets*
pane will show the not completed Remedy tickets assigned to your user group (defined in the Remedy system) and limited by the defined
Remedy qualification filter. *Reuse a specific filter from Remedy*: # Copy the filter expression from the Remedy *Advanced Qualification Builder*
# In *Qualification Filter Samples*, select *User Defined Qualification Filter* # Paste the expression into *Build Search Qualification*. *Build a filter
based on sample filters as template*: {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} provides sample filters you can use
as a template to build your own user-defined filter. # In *Qualification Filter Samples*, select the sample filter that comes the closest to the filter
definition you want to create. # In *Build Search Qualification*, mark and copy the wanted filter expression. # In *Qualification Filter Samples*,
select *User Defined Qualification Filter* and paste the expression into *Build Search Qualification*. # Edit the expression as needed. # If you are
creating a combined complex filter, repeat the steps to copy another sample filter snippet and edit your combined custom filter. h2. Testing the
server configuration. * Click *Test* to test the connection before closing the dialog box. {column} {column:width=50%}
!Remedyconfiguration.png|thumbnail,border=1! {column} {section} ||See also|| [Integration with the Remedy Change Management system from
BMC] [Configuring external system integration]

Configuring e-mail settings

{excerpt:hidden=false}In *System Setup>E-mail Settings*, you can configure e-mail settings to enable the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server to send predefined e-mail notifications.{excerpt} For the
primary Simple Mail Transport Protocol (SMTP) server, then for the backup server (if required): # Type the e-mail "from" address that will identify
that the e-mails are sent by the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. # Identify the SMTP server
information needed by the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server for communication: ## Port number
at the SMTP server used for communication with the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server and
secure connection for the communication, if required. ## Logon credentials for the SMTP server that the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server must use to logon to the SMTP server, if required.\\ \\

{tip:icon=false}*Note*: Enable this option only when using an SMTP server that requires logon access.{tip} When you have configured these
settings, you can set up the system to send automatic notifications on work order changes. || See also || [Setting up automatic e-mail notification
on work order changes|Setting up automatic e-mail notification on work order completion]

Migrating data from StruxureWare Central

When [upgrading from a previous version|Upgrading to StruxureWare Operations 7.1] of
{multi-excerpt-include:pageTitle=Branding|name=ISXOOLD|nopanel=true} running on an
{multi-excerpt-include:pageTitle=Branding|name=ISXCOLD|nopanel=true} server, you must [back up your current configuration|Backing up and
restoring backup], install the new server and clients, and migrate the previous data to the new stand-alone
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. To migrate the previous configuration data to the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, select *System Setup>Migrate from StruxureWare Central*,
and follow the instructions in the wizard. NOTE: These instructions do not apply if you are migrating to a
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} cluster environment. Read instructions on migrating to a cluster
environment [here|Migrating data to a StruxureWare Operations cluster environment]. || See also || [Upgrading to StruxureWare Operations 7.1]
[Uploading data to the StruxureWare Operations server] [Backing up and restoring backup]

Migrating data to a StruxureWare Operations cluster environment

{section}{column:width=50%}If migrating to a cluster environment, ensure only 1 node in the cluster is running when you are performing the
migration. You can use the Webmin server management interface to manage the status of the nodes in the cluster. # Ensure only 1 node in the
cluster is running. ## Open the Webmin web interface by typing the address of your
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server followed by {{:10000}} in a Web browser,
https://yourservername:10000. ## Log on to Webmin using the root credentials (default {{root / apc}}). To change the password, see
[here|Enhancing security on the StruxureWare Operations server#changeroot]. ## In the menu to the left, select *System>StruxureWare
Operations*. ## In the *Status* tab, select to stop the *StruxureWare Operations* and *PostgreSQL Database* services on all nodes except one.
\\ # Perform the migration. ## Launch the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client. ## Select *System
Setup>Migrate from StruxureWare Central* and follow the instructions in the migration wizard. \\ # Start the other nodes in the cluster
environment. ## Open the Webmin web interface again and perform the following steps for one node at a time. ## In the *Status* tab, select the
detached *PostgreSQL Database* for one node and click *Attach DB*. Within approximately 1 minute, the database will be attached. ## If the
database is not up and running after 3 minutes, click *Attach DB* again. ## Start the *StruxureWare Operations* service for this node. ## Wait
approximately 5 minutes and repeat the above steps per additional node in the cluster. {column}
{column:width=50%}!onenoderunning_red.png|thumbnail! {column} {section} ||See also|| [Upgrading to StruxureWare Operations 7.0] [Migrating
data from StruxureWare Central] [Managing server settings in Webmin|Managing server settings]

Migrating data from Emerson Aperture

{section}{column:width=50%} You can migrate existing data from Emerson Aperture to
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} by following the instructions in the migration wizard. This feature is not
available by default. Contact your local sales representative to purchase a software service that enables the feature. h2. Prerequisites * Before
performing the migration, ensure {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} can access and retrieve data from the
Aperture database (it must be running, on the same network, no firewall between them, etc.). * To add spaces from Aperture to
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} (as rooms), you must have user rights in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to edit the global location. * To add products from Aperture to the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} custom catalog, you must have user rights to edit the catalog. {column}
{section} {section}{column:width=50%} h2. Migrating # Select *System Setup>Migrate from Emerson Aperture*. # In the migration wizard, specify
the Aperture database server credentials. Then follow the next steps: {column} {column:width=50%} !Aperturemigrationmen.png|thumbnail!
{column} {section} {section}{column:width=50%} h2. Migrating spaces (rooms) # Select to migrate data center spaces. # Click *Next* to select
which data center spaces (rooms) to migrate and if you want to migrate to the client or in batch mode. Migrating to the client allows you to preview
and cancel the migration before it is executed (recommended option). Migrating in batch mode allows you to migrate large solutions in one step. #
If you selected to migrate to the client, click *Next* to preview the changes and view or save a summary report before finishing the wizard. If you
selected to migrate in batch mode, go directly to the next step. # Click *Finish* to start the migration. {column} {column:width=50%}
!migratespaces.png|thumbnail! {column} {section} {section}{column:width=50%} h2. Migrating catalog # Select to migrate the product catalog. #
Click *Next* to select to migrate the products currently in use in Aperture or all products. # Click *Next* to preview the changes before clicking
*Finish* to start the migration. {column} {column:width=50%} !migratecatalog.png|thumbnail! {column} {section} || See also || [Emerson Aperture
migration mapping overview]

Emerson Aperture migration mapping overview

When migrating from Aperture to {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, data handled differently in the two
systems will be migrated by mapping the data to the closest possible match. *Network connections* The Aperture solution may include different
port types that are not available in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. These ports will be mapped to network
ports of specific types. The ports {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} does not support, such as USB, PS2,
HDMI will not be migrated. ||Aperture type||{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} type|| |RJ45 RJ-45|RJ45|
|FIBER_LC LC LC FIBER|Fiber LC| |FIBER_SC SC SC_DUPLEX|Fiber SC| |FC|Fiber FC| |FIBER FIBER_SX|Fiber| |FIBER_ST|Fiber ST| |RJ48
BNC|Other| |All other ports containing the text "fiber" in the type|Fiber| |Any other ports not listed here|Not migrated| *Spaces/Rooms* ||Aperture
type||{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} type|| |Space|Room| If you migrate an Aperture space and a room with
the same name already exists in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, it will still be migrated and you will see two
rooms with the same name. *Floor-mounted equipment* The floor-mounted equipment from Aperture will be mapped to the corresponding type in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. It will be positioned in the corresponding U-space with the corresponding
U-height. Equipment without a U-position in Aperture will be rear mounted in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. ||Aperture
type||{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} type|| |RACK CABINET|Rack| |PDU|PDU| |RPP|Remote Distribution
Panel (RDP)| |UPS|UPS| |HVAC UNIT|Downflow CRAC| |GENERATOR|Generator| |All other equipment|Generic Floor Powered Equipment|
*Rack-mounted equipment* The rack-mounted equipment from Aperture will be mapped to the corresponding type in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. ||Aperture

type||{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} type|| |SERVER|Server| |POWER STRIP|Rack PDU| |ATS|ATS|

|PATCH PANEL|Layer 1 Network Gear| |ATM SWITCH NETWORK SWITCH ROUTER FIREWALL|Layer 2 Network Gear| ||See also|| [Migrating
data from Emerson Aperture]

Enabling Emerson Aperture migration

Error: The XML content could not be parsed. There is a problem at line 14, column 5. Parser message: Unexpected close tag </xml>; expected
</versionnumber>. at [row,col {unknown-source}]: [14,5]

Managing system licenses

{section}{column:width=50%}{excerpt:hidden=false}The {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} is scalable and the
following license types are available to fit your business needs (10 racks, 100 racks, 200 racks, 500 racks, and enterprise). In addition, the
installation is available with Cluster Node licenses (clustered setup with multiple servers). You can manage the licenses in *System
Setup*.{excerpt} Separate add-on licenses are available for use with {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. The
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} license must be added before you can add the add-on licenses. Licenses
are handled on the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. This means that for example if you have
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} running on multiple clients, and you purchase a
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license, you only need to install it on the server. The clients will be
updated automatically, and you only need to restart the application to get the add-on features. In the System Licenses dialog box, accessed via
*System Setup > System Licenses*, you can manage your licenses for the entire product suite. h2. Summary The summary table provides you
with an overview of your licenses. You can see your installed licenses according to type, e.g. if you have one
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 100 racks license and two 10 racks licenses, this will show as a total of 120
nodes (nodes=racks supported by the license). The overview includes how many of these nodes are in use and how many remaining nodes you
still have available per license type. h2. Details The details table provides you with additional specifications about your individual licenses. You
can see a detailed list of your installed licenses, e.g. if you have one {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 100
racks license and two 10 racks licenses, these will show as three {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} licenses
with details of installation date, count (node count=amount of racks supported by the license), expiration date (applies to evaluation licenses), and
the license key. You can click *Add License Key*... to add new license keys. {tip:icon=false}*Tip*: To minimize the risk of typos, paste the license
key directly into the input field.{tip} If you add a new license type, the application will restart to apply the change. If you add additional license
nodes to existing licenses, you can continue to work without restarting the application. {column}{column:width=50%}
!systemlicenses.jpg|thumbnail! {column}{section} ||See also|| [License Recommendations]

Managing server settings

Server Management settings, such as server time synchronization, can be configured in the Webmin server management interface. h2. Accessing
Webmin The server management interface, Webmin, provides a web-based interface for server configuration. # Open the Webmin web interface
by typing the address of your {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server followed by {{:10000}} in a Web
browser, https://yourservername:10000. # Log on to Webmin using the root credentials (default {{root / apc}}). To change the password, see
[here|Enhancing security on the StruxureWare Operations server#changeroot]. # Use the menu to the left to access server management features,
such as #* *PostgreSQLDatabase Server* #* *System Time* #* *System Logs* ||See also|| [Configuring system time synchronization (NTP)]
[Mounting a Windows share] [Uploading data to the StruxureWare Operations server] [Backing up and restoring backup] [Scheduling regular
backup jobs] [Managing the status of nodes when migrating to a cluster environment|Migrating data to a StruxureWare Operations cluster
environment] [Managing StruxureWare Operations services]

Configuring system time synchronization (NTP)

System time synchronization is needed, especially if you are running in a clustered environment with multiple servers. # [Log on to
Webmin|Managing server settings] using the root credentials (default root / apc). # In the left menu, select *System>System Time*. # Click the
*Time server sync* tab. # Enter the server host information. # Select *Synchronize on schedule*, at *All Hours*. You must configure time
synchronization separately on each node. {tip:icon=false}*Recommendation*: Synchronize the time on all nodes with the same NTP server.{tip}
||See also|| [Managing server settings] [Installing StruxureWare Operations in a cluster environment]

Mounting a Windows share

{section}{column:width=50%}To enable sharing of files between the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true}
server (Linux) and folders on your network (Windows), you must share the network server in which the folder is and give it a share name. A
Windows share can be used to configure for example backups of {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} on your
network or migrate data to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server from previous versions.
!Configuring the room layout^video24x20.jpg! Follow the below steps or watch this short [video tutorial|Video Tutorials#mountsharevideo] (2:20) to
see how to mount a Windows share. # Open the Webmin web interface in one of these ways: #* Type the address of the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server followed by :10000 in a Web browser,
https://yourservername:10000. #* Type the address of your {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server
and click *Server Configuration*. # Log on to Webmin using the root credentials (default root / apc). To change the password, see
[here|Enhancing security on the StruxureWare Operations server#changeroot]. # In the left menu, select *System>Disk and Network
Filesystems*. # In the *Type* drop-down list, select *Windows Networking Filesystem (smbfs)*. # Click *Add Mount*. # In *Mounted As*, browse to
the folder on the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server that you want to use for sharing the files. It is
recommended that you create a share folder at /data/share/. # Select *Save and mount at boot* and *Mount*. # In *Server Name*, type the
hostname or IP address of the network server on which the folder resides. # In *Share Name*, type the name of the drive or folder on the network
server that you want to share. # If needed for accessing the server, type the login credentials. # Click *Create*. If, at any point, you want to delete
a mounted share: # Reopen the Webmin web interface. # In the left menu, *System>Disk and Network Filesystems*. # In the list of file systems,
click the share that you want to delete. # Select *Don't save* and *Unmount*.{column} {column:width=50%} !mountshare2.png|thumbnail!
{column}{section} ||See also|| [Backing up and restoring backup] [Scheduling regular backup jobs] [Uploading data to the StruxureWare
Operations server] [Migrating data from StruxureWare Central]

Uploading data to the StruxureWare Operations server

You can upload data to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server in the Webmin server
management interface. # Open the new {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's Webmin web
interface by typing the address of the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server followed by :10000 in a
Web browser, https://yourservername:10000. # Log on to Webmin using the root credentials (default root / apc). To change the password, see
[here|Enhancing security on the StruxureWare Operations server]. # In the left menu, select *System>Upload and Download*. # Select *Upload to
server* and browse to the location of data file (.tar file), and then specify the new location on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, and select *Upload*. ||See also|| [Upgrading to StruxureWare
Operations 7.1] [Mounting a Windows share]

Backing up and restoring backup

Error: The XML content could not be parsed. There is a problem at line 50, column 5. Parser message: Unexpected close tag </xml>; expected
</hh.mm>. at [row,col {unknown-source}]: [50,5]

Scheduling regular backup jobs

When you have created the backup configuration, you can set up the system to automatically backup regularly according to your backup strategy.
# Open the Webmin web interface by typing the address of your {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true}
server followed by :10000 in a Web browser, https://yourservername:10000. # Log on to Webmin using the root credentials (default root / apc). To
change the password, see [here|Enhancing security on the StruxureWare Operations server]. # In the left menu, select *System>Scheduled Cron
Jobs*. # To enable the default backup schedule: ## Select one of the 3 backup
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server options as needed: \\ ##* daily ##* weekly ##* monthly ##
Click *Enable Selected Jobs* to enable the job with the default settings. # To customize the backup schedule: ## Click one of the 3 backup
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server options as needed: \\ ##* daily ##* weekly ##* monthly ## Edit
the time for the system to automatically execute the backup job as needed. ## Select *Active: Yes* and save to enable the selected backup job.
The system will automatically run the job regularly with the specified interval. ||See also|| [Backing up and restoring backup]

Enhancing security on the StruxureWare Operations server

{section}{column:width=50%} h2. Changing the root password {anchor:changeroot} For security reasons, it is highly recommended that you
change the root password on the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. Keep this password secure
at all times and make it available to Schneider Electric service engineers who need it to be able to perform maintenance on the system.
||DISCLAIMER: THERE IS NO WAY TO RESET THE ROOT PASSWORD IF YOU FORGOT IT.|| # Log on to the server with an SSH client. For
example, use PuTTY. You can download it from [here|http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]. # Type the command
{{passwd}}. # Type the new password and type it again to confirm it. # Type exit. {column} {column:width=50%} !changepassw.png|thumbnail!
{column} {section} ||See also|| [Managing server settings]

Reconfiguring locale on the StruxureWare Operations server

The locale settings on the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server control the language of the alarm
messages, etc. displayed in {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true}. The locale is configured during
installation and you can subsequently reconfigure it as follows: {section}{column:width=50%} # Log on to the server with an SSH client. For
example, use PuTTY. You can download it from [here|http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]. # Type the command
{{dpkg-reconfigure locales}} and press Enter. {column} {column:width=50%} !PuTTY_1.png|thumbnail! {column} {section}
{section}{column:width=50%} 3. Select one of the locales supported in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, and
select Ok. || Language || Country Code\\ || | Brazilian Portuguese \\ | pt_BR.UTF-8 UTF-8 | | Chinese Simplified \\ | zh_CN.UTF-8 UTF-8 | |
Chinese Traditional\\ | zh_TW.UTF-8 UTF-8 | | English\\ | en_US.UTF-8 UTF-8 | | French\\ | fr_FR.UTF-8 UTF-8 | | German\\ | de_DE.UTF-8
UTF-8 | | Italian\\ | it_IT.UTF-8 UTF-8 | | Japanese\\ | ja_JP.UTF-8 UTF-8 | | Korean\\ | ko_KR.UTF-8 UTF-8 | | Russian\\ | ru_RU.UTF-8 UTF-8 | |
Spanish\\ | es_ES.UTF-8 UTF-8 | \\ {tip:icon=false}Tip: Use the arrows to move up and down the list, space key to select an option, and Tab key
to move the cursor to Ok.{tip} {column} {column:width=50%} !PuTTY_2.png|thumbnail! {column} {section} {section}{column:width=50%} 4. Select
the locale that you want to use again, and select Ok. {tip:icon=false}{*}Tip*: Use the arrows to move up and down the list, space key to select an
option, and Tab key to move the cursor to Ok.{tip} {column} {column:width=50%} !PuTTY_3.png|thumbnail! {column} {section} 5. Type {{reboot}}
and wait for the server to restart. 6. Type {{exit}} to close the command prompt. || See also || [Managing server settings] [Enhancing security on
the StruxureWare Operations server] [Working with localized reports]

Managing StruxureWare Operations services

{section}{column:width=50%}In the Webmin server management interface, you can monitor and manage the status of services running on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. All services must be running in order for
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to function properly. h2. Services *StruxureWare Operations:* Ensures the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} process functions. \\ \\ *PostgreSQL Database:* Ensures the configuration
database functions. The database contains all the data about your configuration, such as the rooms, equipment, power path, and network, etc. If
this service shows as *Detached*, the database on this server cannot synchronize with other databases. For example in a cluster environment,
the database on this server cannot synchronize with the databases on the other nodes in the cluster. To resolve this issue, select *Attach DB*. \\ \\
*Apache:* Ensures the web server functions and is used for example in configurations running secure connections and for load balancing
between nodes in a cluster environment. \\ \\ *Keepalived:* Acts as an agent in a cluster environment to monitor the other services and assign a
virtual IP to a specific node. h2. Service status in a cluster environment If you are installing or running
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} in a cluster environment, services will be listed per node. You must ensure
services are running on one node only when migrating to a cluster environment. [More...|Migrating data to a StruxureWare Operations cluster
environment] {column}{column:width=50%} !manageservices.png|thumbnail! {column}{section} || 123 Steps to... ||See also|| | *Monitoring and
changing the status of a service* \\ # Open the Webmin web interface by typing the address of your
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server followed by {{:10000}} in a Web browser,
https://yourservername:10000 # Log on to Webmin using the root credentials (default {{root / apc}}). To change the password, see
[here|Enhancing security on the StruxureWare Operations server#changeroot]. # In the left menu, select *StruxureWare Operations*. # In the

*Status* tab, monitor if the services are all running. # Select a service and use the buttons to start or stop it. \\ \\ When you have started a service,
wait 5 minutes for the operation to complete. | [Managing server settings] [Installing StruxureWare Operations in a cluster environment] [Migrating
data to a StruxureWare Operations cluster environment] |

Changing the IP address of the StruxureWare Operations server through Webmin

{section}{column:width=50%} # [Log on to Webmin|Managing server settings] using the root credentials (default root / apc). # Change the IP
address. ## In the left menu, select *System>Network Configuration*. ## Select *Network Interfaces*. ## Click the *Activated at Boot* tab. ## Set
*Activate* to *Yes*. ## Click the interface you want to change (for example eth0). ## Select *Static configuration* (recommended for cluster
setup), and type the IP address in *IPv4 address* and the *Netmask*, then save. It is recommended that you do not use IPv6 (not supported). #
Specify the Gateway. ## In the left menu, select *Network Configuration*. ## Select *Routing and Gateways*. ## In the *Boot time configuration*
tab, set *Default router* to *Gateway* and type the default route, then save. If you see this error message: Failed to save routing: '' is not a valid
IPv6 gateway, ignore it. # Specify the DNS server. ## In the left menu, select *Network Configuration*. ## Select *Hostname and DNS Client*. ##
In *DNS servers*, type the primary and secondary DNS servers, then save. # Restart the server. ## In the left menu, select *Boot and Shutdown*.
## Click *Reboot System* and wait for the system to finish rebooting. {column} {column:width=50%} !ChangingServerIPInWebmin.png|thumbnail!
{column} {section} ||See also|| [Managing server settings]

Getting started with StruxureWare Operations

{section}{column:width=50%}{excerpt:hidden=false}{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} creates a consolidated
view of your data center's physical infrastructure. Display of real-time device monitoring data from external systems as well as advanced model
design recommendations and placement advice all enable quick assessment and resolution of potential critical situations. {excerpt} You can use
the Application bar to navigate between the main parts of the application. * *Operations* for monitoring data center operations. * *Planning* for
planning the data center design, including planning for changes to the rack layout. * *Analytics* for accessing analytics, such as status reports.
Before you can get started using the application, initial system setup is required, including user administration, license and server management.
These options are available in the *System Setup* menu. If you have administration rights, you will be prompted to set up user credentials for
allowing server communication with external systems, and viewing device measurements and alarm data. When the system setup is ready, you
can start building the initial data center infrastructure and add to the inventory to create a model in the application that represents the real-world
physical infrastructure. {column}{column:width=50%} !Opsoverview.png|thumbnail! {column}{section} ||See also|| [The look and feel of the
application] [Monitoring data center operations in Map View] [Exploring the infrastructure in map, floor and rack layouts] [Setting up the system]

Monitoring data center operations in Map View

{section}{column:width=50%}{excerpt:hidden=false}You can use the map view to monitor the data center operations in a quick overview, including
any alarms in different locations and rooms. From the map overview, you can double-click to drill down to locations > rooms > racks > servers for
details or troubleshooting (and use the *Up* icon in the Toolbar to drill back up through the location hierarchy).{excerpt} The Map View is the
default view when you launch the application the first time. Subsequently, you can access it by clicking the *Map View* icon in the Toolbar
!icon_mapview.png|width=|height=|border=1! or by double-clicking a location folder in the *Navigation* pane. Locations and rooms are
represented by information boxes with pins pointing to a location on the map. You can collapse and expand the information boxes by toggling the
arrow icon in the upper right corner of the box. h2. Alarms overview (1) When collapsed, the information boxes hide the details but have an alarm
status icon in the upper left corner. This allows you to see if there are alarms even when the box is collapsed. When expanded, the information
boxes show the details, including an alarm section, summing up the total amount of alarms and the amount of normal, warning, critical alarms.
Normal: No alarm conditions exist. Warning: A condition exists that may require attention to ensure it does not deteriorate into a critical state.
Critical: A condition exists that requires immediate attention. When the system receives alarm updates from an external system, the info panel
icons will fade in and out. h2. Capacity overview (2) If you have a valid {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true}
license, the information boxes also show a capacity overview represented as a pie chart. It sums up the status of power, cooling, space, and
network of the selected location or room. Power is represented as the percentage of the available load (kW) that is utilized by the IT equipment in
the location or room. Cooling is represented as the percentage of the available load (kW) that is utilized by the IT equipment in the location or
room. U-space is represented as the percentage of the available U-positions (U-pos) that is populated with equipment in the location or room.
Network is represented as the percentage of the available Network ports (ports) that is utilized by networking equipment in the location or room.
{column} {column:width=50%} !map_callout.png|thumbnail! {column} {section} || 123 Steps to... || See also || | *Creating a geographical
representation of the data center infrastructure* \\ # Create a representation of locations and rooms. ## Select *Planning>Data Center* in the
Application bar to be able to edit. ## In *Navigation*, select the root location icon. ## Select *File>New* and one or more of the available
elements.\\ \- Location (option to add container elements for geographical enterprise hierarchy)\\ \- Sub location\\ \- Server Room (option to add
room elements for representing white space in the model)\\ \- Store Room (option to add space elements for representing store rooms in the
model, for example for storing newly arrived servers not yet installed in a server room)\\ \- Electrical Room (option to add room elements for
representing gray space in the model)\\ \- Supporting Infrastructure Space (option to add space elements for representing space outside the
rooms in the model, for example for chillers on the roof) # If you do not have the *Map View* open, double-click a location in *Navigation* to open
it. # Drag the information boxes representing the locations and rooms from the upper left corner into the wanted position on the map. # If you want
another background image for the map view, customize it. ## Right-click the map view and select *Properties*. ## Click *Select Image* and
browse to an image on the computer or network to import the image as background. # If you want to restore the default image, download the
image used [here|http://commons.wikimedia.org/wiki/File:BlankMap-World-1985.png] and insert it in the same way as with another image. |
[Exploring the infrastructure in map, floor and rack layouts] |

Exploring the infrastructure in map, floor and rack layouts

{excerpt:hidden=false}You can see an overview of the data center infrastructure in read-only mode (available when *Operations* is selected in the
Application bar). Before making any changes to the data center infrastructure, you must select to open *> Planning* *> Data Center* in the
Application bar. From the overview in the map view, you can drill down into the contents of the locations and rooms for details or troubleshooting.
{excerpt} # In *Navigation*, navigate to any location, room, or equipment that you want to see in the layout. # Double-click a location in
*Navigation* to open it in the layout, showing the *Map View*. # Double-click a room in *Navigation* to open it in the layout, showing the *Floor
Layout*. # Click a tab at the bottom of the layout to select a specific view, for example a physical information overlay or one with information about
floor loading or rack U-space. Which view tabs are available depend on the installed add-on modules and the display settings. For example,
*Cooling* will be available if you have {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} installed. You can display or hide
specific views using the display settings (accessed from the icon above the layout). # Switch to *Rack Layout* (available in the toolbar above the

layout or by double-clicking a rack in the room or a rack in *Navigation* to see the rack front layout of the selection. If you have
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} installed, equipment may appear with *+* or *x* and arrow symbols,
indicating that changes were proposed to the design, but not yet implemented. # Switch to *List View* (available in the toolbar above the layout) to
see the selection in a list. # Switch between the panes in the bottom of the application to see relevant information. For example, browse to see
any equipment listed in the *Equipment Browser*, get an overview of power connection configurations in *Power Dependency*, or any alarms on
associated devices in *Alarms*. \\ \\ {tip:icon=false}*Tip*:To identify which component in the layout is causing an alarm in the *Alarms* pane,
right-click the alarm in the *Alarms* pane and select *Show in Layout* to highlight the component representing the device in the floor or rack
layout.{tip} ||See also|| [Monitoring data center operations in Map View] [Working with the Floor Layout] [Working with the Rack Layout] [Working
with the List View]

The look and feel of the application

h2. Menu bar The [menu bar|Menus] provides different menu items depending on what part of the application is active. Some of the features
available from the menu bar can also be accessed in additional ways, e.g. through right-click options in various parts of the application. h2.
Application bar The Application bar provides access to the main parts of the application. The number of options (icons) varies depending on how
many add-on modules you have installed. For example, if you have {multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true}
installed, you can access *Planning* *> Work Orders*. The main entry points into the application and add-on modules are: * *Operations*: For
seeing an overview of the data center model and monitor alarms (read-only). * *Planning*: For configuration and planning of the data center
model (editing is possible). * *Analytics*: For data analytics to help you determine if your data center is operating efficiently. h2. Status bar The
status bar at the bottom provides information about the communication with the server. * An alarm icon with a pop-up notification to inform of
active alarms on devices monitored by the {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server or other external system
server. Clicking the icon will open the *Alarms* pane with a list of the active alarms. * The user name with which you are currently logged on to the
system * The IP address of the server to which you are connecting h2. Panes Different screen parts are referred to in this help as panes, for
example *Navigation*, *Catalog*. Several panes have a dynamic *Search* box. In the *Search* box, start typing some characters of the
equipment you want to see. As you type, the pane shows all items that contain the typed characters. Right-clicking a pane's name tab allows you
to change the size and location of any pane, and for a *Layout* pane, you can duplicate a selected layout, or close that layout, or all layouts. You
can resize, minimize, and maximize the panes to fit your preferences. A pane can be detached to have it open in a separate window. The panes
will be resized in the active perspective without affecting the appearance of those panes in any other perspective. {tip:icon=false}*Tip*: Select
*Window>Restore Default Screen Layout* to restore any screen parts to their default locations.{tip} ||See also|| [Getting started with StruxureWare
Operations]

Toolbar
{excerpt:hidden=false}The toolbar options depend on what part of the application is active and what add-on modules you have installed. When
you are configuring the room layout in an editor, layout-specific icons are available such as move and add corners
icons.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} !toolbariconsave.gif|align=center!\\ {table-cell} {table-cell:}Saves changes made
without exiting the display. {table-cell} {table-row} {table-row} {table-cell:} !toolbariconundo.gif|align=center!\\ {table-cell} {table-cell:}Undoes the
last action that was performed, regardless of the active perspective. This function is identical to *Edit* *> Undo*.{table-cell} {table-row} {table-row}
{table-cell:} !toolbariconredo.gif|align=center!\\ {table-cell} {table-cell:}Redoes the last action that was undone, regardless of the active perspective.
This function is identical to *> Edit* *> Redo*.{table-cell} {table-row} {table-row} {table-cell:} !icon_cut.png|align=center!\\ {table-cell}
{table-cell:}Cuts the selected item or items. The selection is only marked for being cut and not actually cut away from its position until you paste it
in another position. This function is identical to *> Edit* *> Cut*. {table-cell} {table-row} {table-row} {table-cell:} !icon_paste.png|align=center!\\
{table-cell} {table-cell:}Pastes a selection of one or more items into this position. This function is identical to *> Edit* *> Paste*. {table-cell}
{table-row} {table-row} {table-cell:} !toolbariconeditcatalog.gif|align=center!\\ {table-cell} {table-cell:}Opens the *Master Catalog* from which to
select products for the catalog. {table-cell} {table-row} {table-row} {table-cell:} !tool-generate-row.png|align=center!\\ {table-cell} {table-cell:}Opens
dialog box with options to configure a row layout. {table-cell} {table-row} {table-row} {table-cell:} !tool-select.png|align=center!\\ {table-cell}
{table-cell:}Selects to use the standard cursor while deactivating the corner or floor tile tools. {table-cell} {table-row} {table-row} {table-cell:}
!add-corner.png|align=center!\\ {table-cell} {table-cell:}Allows you to add a corner to a room's outline. {table-cell} {table-row} {table-row} {table-cell:}
!move-corner.png|align=center!\\ {table-cell} {table-cell:}Allows you to move corners and walls to a room's outline. {table-cell} {table-row}
{table-row} {table-cell:} !pan-grid.png|align=center!\\ {table-cell} {table-cell:}Allows you to move the tile grid to match the floor tiles in the layout with
the tile offset that exists at the data center. {table-cell} {table-row} {table-row} {table-cell:} !tool-zoom-in.png|align=center!\\ {table-cell}
{table-cell:}Zooms in on the layout. {table-cell} {table-row} {table-row} {table-cell:} !tool-zoom-out.png|align=center!\\ {table-cell} {table-cell:}Zooms
out on the layout. {table-cell} {table-row} {table-row} {table-cell:} !tool-zoom-fit.png|align=center!\\ {table-cell} {table-cell:}Sets the zoom level to a
size that allows you to see the entire room in the layout. {table-cell} {table-row} {table-row} {table-cell:} !physical-layout.png|align=center!\\
{table-cell} {table-cell:}Opens the *Floor Layout* for managing the floor layout (add, move, delete, or edit) for any room. {table-cell} {table-row}
{table-row} {table-cell:} !icon_manageoverlays.png|align=center!\\ {table-cell} {table-cell:}Selects to enable/disable views in the floor and rack
layouts. {table-cell} {table-row} {table-row} {table-cell:} !rack-layout.png|align=center!\\ {table-cell} {table-cell:}Opens the *Rack Layout* for
managing rack-mountable equipment (add, move, delete, or edit) for any room. {table-cell} {table-row} {table-row} {table-cell:}
!list-view.png|align=center!\\ {table-cell} {table-cell:}Opens the *List View* for managing any room (add, move, delete, or edit) in a table layout.
{table-cell} {table-row} {table-row} {table-cell:} !icon_worldmap.png|align=center!\\ {table-cell} {table-cell:}Opens the *Map View* for viewing a
geographical representation of the data center infrastructure. {table-cell} {table-row} {table-row} {table-cell:} !icon_worldmapup.png|align=center!\\
{table-cell} {table-cell:}Changes the view of the data center infrastructure *Map View* to the location one level up in the location hierarchy.
{table-cell} {table-row} {table-row} {table-cell:} !icon_3D.png|align=center!\\ {table-cell} {table-cell:}Opens the *3D View* for viewing the data center
temperature map in a 3D layout. {table-cell} {table-row} {table-row} {table-cell:} !icon_3Dmanagecontrolpanel.png|align=center!\\ {table-cell}
{table-cell:}Toggles display of the control panel. {table-cell} {table-row} {table-row} {table-cell:} !icon_3Dsavescreenshot.png|align=center!\\
{table-cell} {table-cell:}Opens a save dialog box to save a screenshot of the 3D layout. {table-cell} {table-row} {table} ||See also|| [The look and feel
of the application]

Menus
{excerpt:hidden=false}The active menu bar items vary depending on what part of the application is active. {excerpt} Some menu options are only
available when specific features are enabled. For descriptions of these specific menu options, refer to the topics about those features in the help.
{table:border=1|frame=box|} {table-row} {table-cell} *File* {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF|
bgColor=#FFFFFF} *New > Location*: Creates a new folder in the physical infrastructure hierarchy with the default name highlighted so you can
type another name. *New > Server Room*: Opens the wizard for creating a new server room. *New > Electrical Room*: Opens the wizard for

creating a new electrical room. *New > Store Room*: Opens the wizard for creating a new store room. *New > Supporting Infrastructure Space*:
Opens the wizard for creating a new space for supporting infrastructure elements (for example for chillers on the roof). *Save*: Saves your
changes. *Import > InfraStruxure Designer*: Opens the dialog box in which to browse to an InfraStruxure Designer configuration. Importing an
existing InfraStruxure Designer solution saves you from doing the basic configuration in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. *Import > Insight Report Design*: Opens the dialog box in which to browse
to a custom report design created in {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} to add the custom report.
[More...|Customizing report designs] *Export > Temperature Map...*: Opens the dialog box in which to export the temperature map to CSV format.
*Export > Plenum Airflows...*: Opens the dialog box in which to export the plenum airflow configuration to CSV format. *Export > CFD PDML
Export...*: Opens the dialog box in which to export the cooling configuration directly to .pdml without the need to use conversion tools. *Export >
CFD XML Export...*: Opens the dialog box in which to export the cooling configuration to .xml. *Export > Layout as Image*: Opens the *Export*
dialog box used to save a bmp or jpg copy of one or more of the server rooms. *Export > Insight Report Design*: Opens the dialog box in which to
select a built-in standard report design from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to use it as a template for a
new custom report design in {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. [More...|Customizing report designs] *Restart*:
Restarts the client and the server. For example, you can use this option if you are migrating from multiple
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} servers to restart after each migration. *Exit*: Closes the application.{panel}
{table-cell} {table-row} {table-row} {table-cell} *Edit* {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}
*Undo*: Selects to undo the last action that was performed, regardless of the perspective selected. *Redo*: Selects to redo the last action that
was performed, regardless of the perspective selected. *Cut*: Cuts the selected item or items. The selection is only marked for being cut and not
actually cut away from its position until you paste it in another position. *Paste*: Pastes a selection of one or more items into this position.{panel}
{table-cell} {table-row} {table-row} {table-cell} *Tools* {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}
*Open Master Catalog*: Opens the master catalog from which to add, edit or remove available components in the system. [More...|Working with
the Catalog] *Configure Tags*: Opens the Configure Tags dialog box in which to set up tags to categorize types of equipment in the layout
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature). [More...|Creating tags] *Generate Capacity Groups*: Opens
the Generate Capacity Groups dialog box in which to set up capacity planning.
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature) [More...|Working with capacity groups] *Create new Work
Order*: Opens the *Work Order Editor* and enables the controlled automated work order process. [More...|Working with work orders] *Configure
Work Order Templates*: Opens the *Configure Work Order Templates* dialog box to create templates and manage repetitive tasks.
[More...|Creating and applying work order templates] *Create Work Order Project Codes*: Opens the *Create Project Codes* dialog box to create
work order project codes. These codes will appear in the *Project Code* drop-down list in the *Work Order Editor*. *Preferences*: Opens the
Preferences dialog box.{panel} [More...|Reviewing system preferences] {table-cell} {table-row} {table-row} {table-cell} *System Setup* {table-cell}
{table-cell}*User Rights and Authentication*: Opens the dialog box in which to manage user rights and authentication servers. [More...|Managing
users in the system] *External System Configuration*: Opens the dialog box in which to set up integration to other systems and manage the
server configurations. [More...|Configuring external system integration] *E-mail Settings*: Opens the dialog box in which to set up e-mail
notification functionality. [More...|Configuring e-mail settings] *Migrate from StruxureWare Central*: Opens the dialog box in which to move data
from previous versions to the new stand-alone StruxureWare Operations server. [More...|Migrating data from StruxureWare Central] *System
Licenses*: Opens the dialog box in which to manage licenses. [More...|Managing system licenses] {table-cell} {table-row} {table-row} {table-cell}
*Window* {table-cell} {table-cell} *Restore Default Screen Layout*: Selects to restore any screen parts to their default locations if they have been
moved to new positions. {table-cell} {table-row} {table-row} {table-cell} *Help* {table-cell} {table-cell} *Online Help*: Provides access to the [online
user assistance|User Assistance for StruxureWare Operations 7.1]. *Download Log Files*: Opens a dialog box in which to define a location to
download the system log files to. [More...|Troubleshooting error messages] *Data Center Software Website*: Opens the [Data Center Software
Website|http://www.apc.com/site/software/index.cfm]. *About StruxureWare for Data Centers: Operations Suite*: Opens the dialog box with
copyright and version information for the application. [More...|Troubleshooting error messages] {table-cell} {table-row}{table}

Help menu
{excerpt:hidden=false}Help menu options provide access to the wiki-based user assistance, the [Data Center Software
website|http://www.apc.com/site/software], and copyright and version information for the application. They can be accessed at any
time.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell} *Online Help* {table-cell} {table-cell}Opens the wiki-based user assistance. You
can view the user assistance, and if you register as a user on the wiki, you can use the feedback options to comment on pages or send an e-mail
to the documentation team.{table-cell}{table-row} {table-cell} *Data Center Software Website* {table-cell} {table-cell} Opens the Data Center
Software website where you can read more about the applications and services and get contact information. {table-cell} {table-row} {table-row}
{table-cell} *About {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}* {table-cell} {table-cell}Opens the About dialog box,
which provides copyright and version information for the application. {table-cell} {table-row}{table} ||See also|| [User Assistance for StruxureWare
Operations 7.1]

Navigation
{excerpt:hidden=false}The *Navigation* pane lists the hierarchy of the data center model in a tree structure: Locations, rooms, rows,
floor-mounted equipment placed in the rows, such as racks, and rack-mounted equipment placed in racks. {excerpt} The pane provides a
hierarchical overview of the contents in the data center model placed in locations. It has dynamic search functionality: As you start typing in the
*Search* box, the tree structure shows all equipment that contains the typed characters. You can edit when you have selected *> Planning* *>
Data Center* in the Application bar and build the data center model to reflect the real-world infrastructure by adding new locations (such as
regions, countries, cities) and room items to the hierarchy. * Locations and rooms of different types can be added from *> File* *> New*. * New
rows, floor and rack-mountable components can be added from the *Catalog*. You can move equipment between the different rooms (and
locations) in the *Navigation* pane and *Layout* pane by dragging it. * Rack-mountable equipment can be dragged from any rack in the
*Navigation* pane to a store room, any rack in a selected rack layout, or any rack in the *Navigation* pane. * Floor equipment can be dragged
from any room in the *Navigation* pane to a store room, electrical room or any room shown in the floor layout, or any rack in the *Navigation*
pane. * Rack or floor equipment can be dragged from any room in the *Navigation* pane to any selected store room shown in the *Layout* pane.
You can highlight any listed equipment by right-clicking it and selecting *Show in Editor* to highlight the selected *Navigation* pane device in the
*Layout* pane. Double-clicking a room opens the selected room in the floor layout editor view. If a room is already open in the layout editor,
right-click and select *Open New Editor* to open the selected room in the layout in a separate pane. You can use the right-click menu to access
the most relevant options. For example: * Right-clicking a location allows you to create, rename, and delete locations and rooms. * Right-clicking a
room allows you to open the selected room in a new floor layout editor, copy, paste, rename, and show properties. * Right-clicking an item allows
you to highlight it in the layout (*Show in Editor*), cut, paste, rename, show properties. You can delete equipment by right-clicking it and selecting

*Delete*. {tip:icon=false}*Tip*: You can add, move or delete multiple items at the same time by using Ctrl-click or Shift-click.{tip} ||See also||
[Exploring the infrastructure in map, floor and rack layouts] [The look and feel of the application]

Showing or hiding floor and rack views

{section}{column:width=50%}You can enable/disable views in the floor and rack layouts by using the *Manage Visible Overlays* icon above the
graphical layout. {tip:icon=false}*Note*: This is a {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature. You must have
a valid license to use this feature.{tip} You cannot delete all views at the same time, so the system will gray out the last view to be able to show
something in the graphical layout. The *Alarms* view in read-only mode cannot be disabled. {column}{column:width=50%}
!manageoverlays.png|thumbnail! {column}{section} ||See also|| [Working with the Floor Layout] [Working with the Rack Layout] [Preferences:
Showing or hiding tool tips sections|Reviewing system preferences#pref_tooltip] [Preferences: Showing floor dimensions in meters or
feet|Reviewing system preferences#pref_meas]

Reviewing system preferences

h2. Accessing system preferences Define preferences according to your requirements e.g. enabling or disabling certain popup dialog boxes and
changing unit of measurement used in the system. # Select *Tools>Preferences* to access the Preferences dialog box. # Review and change the
settings in the available tabs, as required. The available preferences depend on the installation and licenses as some control settings of ad-on
features. h2. Setting system of measurement {anchor:pref_meas} In the *General* tab *Client Settings*, select to use metric or US standard unit
of measurements in the application displays. This affects for example if the floor dimensions are displayed in meters or feet. h2. Linking to custom
online help {anchor:pref_help} In the *General* tab *Online Help Settings*, set up a *Custom URL* to link to a custom user assistance source.
When you select *Help>Online Help*, the system will open this link rather than the link to the default wiki-based user assistance provided for the
application. If you leave this field empty, the system will default to the default wiki-based user assistance provided for the application. h2. Showing
or hiding confirmation dialog boxes {anchor:pref_confirm} In the *General* tab *Display Confirmation Dialogs*, clear the check boxes if you do not
want confirmation dialog boxes to pop up in the application. * *Confirm before making changes to data center* to prompt the user to confirm
before saving changes. * *Confirm valid user settings on start-up* to prompt users with administration rights when launching the application,
requesting to confirm the user credentials for server communication. {tip:icon=false}*Note*: If you deselect to display this popup, you potentially
risk missing alarms, because you will not be warned if the user credentials are invalid, and device and alarm data will not be available in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.{tip} h2. Enabling the customer experience program
{anchor:pref_customerprogr} In the *General* tab *Customer Experience Program*, select to *Enable Customer Experience Program*. By
participating in the program, you help making this software better by sending error and usage data to Schneider Electric. Your privacy will be
respected, and the data will be used for internal purposes only to help the engineers identify and fix errors in the software to improve your user
experience. h2. Setting Energy Efficiency metric {anchor:pref_EEmetric} In the *General* tab *Energy Efficiency Settings*, select to use Power
Usage Effectiveness (PUE) or Data Center Infrastructure Efficiency (DCiE) as energy efficiency metric in the application displays. This affects for
example if the dashboard shows values as PUE or DCiE. PUE: a measure of the ratio of the total amount of power used by the data center facility
to the power used by the IT load. DCiE: a measure which is expressed as the relationship between the IT load and the total data center input
power. h2. Showing or hiding tool tips {anchor:pref_tooltip} In the *General>Tool Tips* tab, select the information to show in the tool tips. The
selected information will be included as sections in the graphical layout tool tips. {tip:icon=false}*Tip*: Disable any irrelevant information to avoid
big tool tips blocking your view of equipment while working in the layout.{tip} ||See also|| [Saving KPIs over time] [Setting up cable connection
settings]

Suite part number list

|| Part Number\\ || Product Description\\ || | AP90010 | StruxureWare Operations Suite for Data Centers, 10 Rack License | | AP900100 |
StruxureWare Operations Suite for Data Centers, 100 Rack License | | AP900200 | StruxureWare Operations Suite for Data Centers, 200 Rack
License | | AP900500 | StruxureWare Operations Suite for Data Centers, 500 Rack License | | AP900ENT | StruxureWare Operations Suite for
Data Centers, Volume License | | AP90000 | StruxureWare Operations: Energy Efficiency License | | AP9700S | StruxureWare Operations: Mobile
License | | AP9110 | StruxureWare Operations: Capacity, 10 Rack License | | AP91100 | StruxureWare Operations: Capacity, 100 Rack License | |
AP91200 | StruxureWare Operations: Capacity, 200 Rack License | | AP91500 | StruxureWare Operations: Capacity, 500 Rack License | |
AP91ENT | StruxureWare Operations: Capacity Volume License | | AP9135 | StruxureWare Operations: Energy Cost License | | AP9710 |
StruxureWare Operations: Change, 10 Rack License | | AP97100 | StruxureWare Operations: Change, 100 Rack License | | AP97200 |
StruxureWare Operations: Change, 200 Rack License | | AP97500 | StruxureWare Operations: Change, 500 Rack License | | AP97ENT |
StruxureWare Operations: Change Volume License | | AP90055 | StruxureWare Operations: Insight License | | AP90065 | StruxureWare
Operations: Cluster Node License, 1 Additional Server | ||See also|| [Getting started with StruxureWare Operations] [What is new in StruxureWare
Operations 7.1?]

Tips and Tricks

{excerpt:hidden=false}To save time, you can use these keyboard shortcuts in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.{excerpt} h2. Double-click {table:border=1|frame=box|} {table-row}
{table-cell:}Double-click a rack in Floor Layout {table-cell} {table-cell:}Open the rack in Rack Layout {table-cell} {table-row} {table-row}
{table-cell:}Double-click an item of floor or rack-mount equipment {table-cell} {table-cell:}Open the Properties dialog box for the selected item
{table-cell} {table-row}{table} h2. Multi select {table:border=1|frame=box|} {table-row} {table-cell:}Ctrl-click multiple items {table-cell}
{table-cell:}Select multiple non-consecutive items {table-cell} {table-row} {table-row} {table-cell:}Shift-click multiple items {table-cell}
{table-cell:}Select multiple consecutive items {table-cell} {table-row} {table-row} {table-cell:}Draw a box around multiple items {table-cell}
{table-cell:}Select multiple consecutive items {table-cell} {table-row}{table} h2. Keyboard shortcuts{table:border=1|frame=box|} {table-row}
{table-cell:}Alt+Enter {table-cell} {table-cell:}Open Properties dialog box {table-cell} {table-row} {table-row} {table-cell:}Ctrl+C {table-cell}
{table-cell:}Copy {table-cell} {table-row} {table-row} {table-cell:}Ctrl+Shift+E {table-cell} {table-cell:}Execute Planned Change
({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature) {table-cell} {table-row} {table-row} {table-cell:}Ctrl+Shift+C
{table-cell} {table-cell:}Cancel Planned Change ({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature) {table-cell}
{table-row} {table-row} {table-cell:}Ctrl+K {table-cell} {table-cell:}Show selection in the *Navigation* pane {table-cell} {table-row} {table-row}
{table-cell:}Ctrl+L {table-cell} {table-cell:}Show selection in the *Layout* {table-cell} {table-row} {table-row} {table-cell:}Ctrl+N {table-cell}
{table-cell:}Open New Room dialog box {table-cell} {table-row} {table-row} {table-cell:}Ctrl+S {table-cell} {table-cell:}Save {table-cell} {table-row}
{table-row} {table-cell:}Ctrl+V {table-cell} {table-cell:}Paste {table-cell} {table-row} {table-row} {table-cell:}Ctrl+Y {table-cell} {table-cell:}Redo
{table-cell} {table-row} {table-row} {table-cell:}Ctrl+X {table-cell} {table-cell:}Cut (The selection is only marked for being cut, and not actually cut

away from its position until you paste it in another position.) {table-cell} {table-row} {table-row} {table-cell:}Ctrl+Z {table-cell} {table-cell:}Undo
{table-cell} {table-row} {table-row} {table-cell:}Ctrl+- {table-cell} {table-cell:}Zoom out {table-cell} {table-row} {table-row} {table-cell:}Ctrl++
{table-cell} {table-cell:}Zoom in {table-cell} {table-row} {table-row} {table-cell:}Shift+Delete {table-cell} {table-cell:}Delete the selection In
*Planning>IT Change*, mark the selection for deletion {table-cell} {table-row} {table-row} {table-cell:}F7 {table-cell} {table-cell:}Open the *Master
Catalog* {table-cell} {table-row}{table}

Support
Software Support Wiki
Access the Software Support Wiki to find the information you need to make the most of your software applications and share information with the
software team and the rest of the support community.
On the support wiki home page, you can access the following:
User Forum: Meet other users and ask questions.
Help Documentation: Access the latest user assistance on our applications, and read release notes and other product information.
Feature Request: Request new features or report a bug.
FAQ: Search the Knowledge Base.
Tip: Make a note of the installation details (version, build, and serial number) and have this information ready when contacting support. You
can access this information in the application Help>About StruxureWare Operations.

If a critical error message occurred, follow these instructions or watch this short video tutorial (2:26) before contacting support.

Data Center Software website

Access the Data Center Software website for background information to make an informed and smart investment into management software.
To locate the telephone number for the support you need, visit Contact Us.
See also
Getting started with StruxureWare Operations

Building the infrastructure and adding inventory

{section}{column:width=50%}{excerpt:hidden=false}When the system setup is ready, you can start building the initial data center infrastructure
and add to the inventory to create a model in the application that represents the real-world physical infrastructure.{excerpt} {column}
{column:width=50%} !infrastructurelocnroom.png|thumbnail! {column} {section} || 123 Steps to... || See also || | *Creating a representation of the
locations and rooms* You can add locations and rooms of different types to the system to represent the actual physical enterprise infrastructure. \\
# Select *Planning>Data Center* in the Application bar. # In *Navigation*, select the root location icon. # Select *> File* *> New* and one or more
of the available elements #* Location (option to add container elements for geographical enterprise hierarchy) #** EMEA #*** France #**** Paris
#**** Grenoble #*** Denmark #**** Kolding #** NAM #*** Server Room (option to add room elements for representing white space in the model)
#*** Store Room (option to add space elements for representing store rooms in the model, for example for storing newly arrived servers not yet
installed in a server room) #*** Electrical Room (option to add room elements for representing gray space in the model) #*** Supporting
Infrastructure Space (option to add space elements for representing space outside the rooms in the model, for example for chillers on the roof) \\ \\
# Follow the instructions in the wizard to select the shape that most closely resembles the actual shape of the room and to define any room
properties. (Applicable for server rooms and electrical rooms.) The hierarchy has been built according to your configuration and you can continue
with the configuration of the data center model, e.g. adding equipment to the rooms. | [Creating the equipment catalog|Working with the Catalog]
[Importing a design from the InfraStruxure Designer] [Adding gaps and blocks to the room layout] [Adding floor equipment to the room
layout|Working with the Floor Layout] [Adding rack-mountable equipment to the room layout|Working with the Rack Layout] [Adding blade
equipment to the rack layout|Configuring blade solutions] [Setting up the system]|

Importing a design from the InfraStruxure Designer

{section}{column:width=50%}Adding a room by importing a design from the {multi-excerpt-include:pageTitle=Branding|name=ISXD|nopanel=true}
minimizes the need for initial configuration, as key design information is automatically imported such as room shape, equipment placement, power
wiring, breaker rating, etc. Prerequisite: In the {multi-excerpt-include:pageTitle=Branding|name=ISXD|nopanel=true}, select File -> Export to
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and save the .xml file. # Select *Planning>Data Center* in the Application
bar. # Select *File>Import>InfraStruxure Designer* # In the *Open* dialog box that appears, browse to, and select the *.xml file. # Click *Open* to
add the selected {multi-excerpt-include:pageTitle=Branding|name=ISXD|nopanel=true} file as a new room. A new room with the
{multi-excerpt-include:pageTitle=Branding|name=ISXD|nopanel=true} data has been added. # Rename the room if necessary and adjust to make
the layout reflect the actual physical infrastructure of the data center, e.g. adding any equipment that the import did not include. # If you plan to
add more equipment of the same type as the imported products, add the imported products to the custom catalog. Imported products are not
automatically added to the catalog. {column} {column:width=50%} !importISXD.png|thumbnail! {column} {section} ||See also|| [Building the
infrastructure and adding inventory] [Working with the Catalog]

Creating Supporting Infrastructure Space

{excerpt:hidden=false}You can configure supporting infrastructure space that represents space in the actual physical enterprise infrastructure that
is not positioned in the available room types. This allows you to configure representations of supporting equipment in a building, outside a
building, or on a roof (e.g. chillers, cooling towers, switchgear).{excerpt} # Select *Planning>Data Center* in the Application bar. # In *Navigation*,
select the location icon representing the site where you want the space added. # Select *> File* *> New* *> Supporting Infrastructure Space* and
provide a name for the space. The space has been added to the *Navigation* hierarchy. You can see it in the *List View*, and in the graphical
layout. You can now start dragging supporting infrastructure equipment into the space from the catalog. ||See also|| [Building the infrastructure
and adding inventory] [Creating the equipment catalog|Working with the Catalog] [Adding gaps and blocks to the room layout] [Adding floor
equipment to the room layout|Working with the Floor Layout] [Adding rack-mountable equipment to the room layout|Working with the Rack Layout]
[Adding blade equipment to the rack layout|Configuring blade solutions] [Setting up the system]

Configuring the room layout

{excerpt:hidden=false}Use the toolbar icons to configure the room layout to ensure that the layout in the data center model accurately represents
the real-world physical environment of the room. This includes any physical attributes of the room such as size, shape, and walkways.
{excerpt}Before configuring the room layout you must select *Planning* *> Data Center* in the Application bar to open the room in the layout. #
Create a floor layout that resembles the actual physical room shape as closely as possible by adding walls and corners, for example to add a new
wall: ## Select the corner tool in the toolbar. !add-corner.png!\\ The cursor icon now looks like this when you move it into the layout:
!toolbariconcornercursor.jpg!\\ ## Click on a wall where you want to add the 2 new corners that will define where a new wall will begin and end. ##
Select the move tool in the toolbar. !move-corner.png!\\ The cursor icon changes into a double-headed arrow when you move it over a wall in the
layout. ## Click the wall between the dots and drag the new wall into position. \\ \\ {tip:icon=false}*Tip*: Use the toolbar zoom icons to drag a wall
or angle to a precise position.{tip} # If the room has a row layout, select the *Generate Rows* icon in the toolbar !tool-generate-row.png!\\ and
follow the instructions in the wizard. # If the tile grid does not match the actual physical environment, select the pane tile tool in the toolbar
!pan-grid.png!, and drag the tile grid around until the tiles are located properly in the floor layout. ||See also|| [Building the infrastructure and
adding inventory] [Creating the equipment catalog|Working with the Catalog] [Adding gaps and blocks to the room layout] [Adding floor equipment
to the room layout|Working with the Floor Layout] [Adding rack-mountable equipment to the room layout|Working with the Rack Layout] [Adding
blade equipment to the rack layout|Configuring blade solutions] [Setting up the system]

Adding rows to a room

{excerpt:hidden=false}Follow the instructions in the Generate Rows wizard to add rows to a room, or drag and drop rows from the *Catalog* into
the layout.{excerpt} # Select *Planning>Data Center* in the Application bar. # Open the room in which you want to add rows in the Floor Layout. #
To generate an automatic row layout for the entire room in one action: ## Select the *Generate Rows* icon in the toolbar. ## Follow the
instructions in the Generate Rows wizard to select the row settings that most closely resemble the actual physical layout. # To add individual rows
with specific properties from the custom catalog: ## Select the row from the *Catalog* and drag and drop it into position in the *Floor Layout*. ##
To customize the row layout, select the sides of the row and drag and drop until the row has the required size (or right-click and select
*Properties*), and right-click the row to access rotation and flip options. Rows have been added to the room and you can continue the design
process, e.g. adding equipment to the room. !Configuring the room layout^video24x20.jpg! Watch this short [video tutorial|Video
Tutorials#modifyroomvideo] (1:42) to see how to modify the room layout. ||See also|| [Configuring the room layout] [Building the infrastructure and
adding inventory]

Adding gaps and blocks to the room layout

{excerpt:hidden=false}Gaps and blocks represent areas in the room layout in which equipment cannot be placed. A gap is a section over which
cables and cooling lines can be routed (such as a walkway or ramp). A block is a section over which cables and cooling lines cannot be routed
(such as a support column).{excerpt} # Drag a *Gap* or *Block* icon from the *Catalog* pane into position in the room layout. # Right-click a
*Gap* or *Block* in the layout and select *Properties* to edit the name or other properties. # Repeat the above steps until all gaps and blocks that
can affect equipment positioning are represented in the room layout. ||See also|| [Working with the Floor Layout]

Adding doors and windows to the room layout

{section}{column:width=50%}Adding doors and windows allows you to create a more accurate model of the data center, making it easy to
navigate the room. # Drag a *Door* or *Window* icon from the *Catalog* pane into position in the room layout. # Right-click a *Door* or *Window*
in the layout and select *Properties* to edit the name or other properties. # Repeat the above steps until all doors and windows that can affect
equipment positioning are represented in the room layout. {column} {column:width=50%} !doors_windows.png|thumbnail! {column} {section} ||See
also|| [Working with the Floor Layout]

Inventory report
{section}{column:width=50%}{excerpt:hidden=false}You can generate an Inventory report that lists the contents of the selected item or items in
the application.{excerpt} In addition to being available from *Analytics>Reports*, it can be generated for individual components and racks in
*Operations>Data Center* by right-clicking a component or rack in the layout, and selecting *Asset Inventory*. The generated report displays in
the *Report View*. You can now use the *Report View* toolbar to navigate the report pages on the screen (arrow icons), or to print or export the
report to a file in any of the available formats (Export icon, down arrow for selection of format). {column} {column:width=50%}
!report_inventory.png|thumbnail! {column} {section} ||See also|| [Working with reports]

Editing Properties
{excerpt:hidden=false}Right-click any room, floor equipment (including racks), or rack-mountable equipment in a *Navigation* pane, or *Layout*
pane and select *Properties* to access and edit the properties. {excerpt} # To edit properties for a selected component, right-click it in the
floor/rack *Layout* or *Navigation* pane and select *Properties* and perform the edits in the Properties dialog box. # To edit properties for a
component in the catalog, i.e. all pieces of this equipment added to the floor or rack layout subsequently, open the catalog, select a component in
the *Floor Equipment* or *Rack-Mountable Equipment* pane and perform the edits in the *Properties* section. # To add custom properties,
perform one of the above steps, and in the *Properties (Custom)* section, select *Add*, then in the Add Custom Properties dialog box, type the
name and value for the new property. # To add power connection properties, perform one of the above steps, and in the New Power Connection
dialog box, accessed in the *Power Dependency* (CRAC) or *Power Distribution* (PDU or remote distribution panel (RDP)) section, select *New*

to add a new power connection or *Edit* to edit an existing connection. ||See also|| [Viewing external system data] [Room Properties] [Cooling
Properties] [Custom Properties] [General Properties] [Device Properties] [Mounting Properties] [Network Properties] [New Custom Properties]
[New Power Connection Properties] [Physical Properties] [Power Dependency Properties] [Power Distribution Properties] [Power Properties
(rack)] [Power Properties (rack PDU)] [Power Properties (server, blade server, blade enclosure)] [Power Properties (UPS)] [Pump Properties]

Custom Properties
{excerpt:hidden=false}This section of a Properties dialog box lists custom properties for the selected
component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Name* {table-cell} {table-cell:}Defines the property's name. {table-cell}
{table-row} {table-row} {table-cell:} *Value* {table-cell} {table-cell:}Defines the value the property provides. {table-cell} {table-row} {table}
{tip:icon=false}*Note*: The listed information is defined by add and edit versions of a Custom Properties dialog box that are accessed by the
*Add* and *Edit* buttons; *Delete* allows you to remove any listed custom property.{tip} ||See also|| [Editing Properties]

General Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component, provides relevant information that
identifies the selected component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Name* {table-cell} {table-cell:colspan=2|}A
user-definable value used to identify the component. {table-cell} {table-row} {table-row} {table-cell:} *Location* {table-cell}
{table-cell:colspan=2|}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Identifies the component by type and location. For
example: * *R/A-3/Z2* identifies a rack that is the third from the left in row A, and is included in the power zone identified as Z2. * *E2/Wall*
identifies the second of at least two emergency power off (EPO) buttons located against a wall.{panel} {table-cell} {table-row} {table-row}
{table-cell:} *Barcode* {table-cell} {table-cell:colspan=2|}A user-definable alphanumeric value that identifies the barcode assigned to the
component, if any. {table-cell} {table-row} {table-row} {table-cell:} *Product Information* {table-cell} {table-cell:colspan=2|}Identifies the
*Manufacturer*, *Model name* and *Part Number*, and provides a *Description* of the component. You can edit *Product Information* for a
generic component. {table-cell} {table-row}{table} ||See also|| [Editing Properties]

Device Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an associated device or component with an associated
device, identifies the general and measured data of the device. {excerpt}{table:border=1|frame=box|} {table-row} {table-cell} *Properties*
{table-cell} {table-cell}Identifies device details. {table-cell} {table-row} {table-row} {table-cell} *Power* {table-cell} {table-cell}Reports the measured
load values for the device. {table-cell} {table-row}{table} ||See also|| [Editing Properties]

Mounting Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component, identifies the mounting options of the
component in the rack.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Available mounting Positions* {table-cell}
{table-cell:}Identifies the position of the component in *Front*, *Rear*, *Left Rear*, *Right Rear*, *Not Mounted*, and *Top*. {table-cell}
{table-row}{table} ||See also|| [Editing Properties]

New Custom Properties

{excerpt:hidden=false}Use the Add Custom Property dialog box, which is accessed by using the *Properties (Custom)* buttons, to add a new
custom property (*Add*) or to edit an existing property (*Edit*).{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:colspan=2|} *Name*
identifies a name for the custom property. *Value* identifies the provided value. {table-cell} {table-row}{table} ||See also|| [Editing Properties]

Physical Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component, identifies physical attributes associated
with the component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Position* {table-cell} {table-cell:}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF}Provides information that varies based on the component type: * Floor: Identifies the location of the
component within the Layout pane: *X* identifies its distance from the left side of the pane; *Y* its distance from the top of the pane. *
Rack-mountable: Identifies the rack unit (U) position within its rack. {panel} {table-cell} {table-row} {table-row} {table-cell:} *Weight* {table-cell}
{table-cell:}Identifies how much the component weighs. For racks: *Weight* identifies how much the rack weighs when empty; *Maximum weight*
identifies the maximum weight that is allowed to be added to the rack; *Current weight* is the sum of the rack's weight and the weight of the
equipment added to the rack.{table-cell} {table-row} {table-row} {table-cell:} *Boundary* {table-cell} {table-cell:}Identifies the component's
dimensions (*Width*, *Depth*, and *Height*), and the *Orientation* that component has in relation to the server room's physical layout. {table-cell}
{table-row} {table-row} {table-cell:} *Frame* {table-cell} {table-cell:}Provides information about how many rack units (U) a rack provides
(*U-positions*), how many are still available (*Free U-positions*). {table-cell} {table-row}{table} ||See also|| [Editing Properties]

Power Properties (rack)

{excerpt:hidden=false}This section of the Properties dialog box identifies power attributes associated with a
rack.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Power Consumption* {table-cell} {table-cell:}Identifies the estimated load of the
component mounted in the rack. {table-cell} {table-row} {table-row} {table-cell:} *Power Availability* {table-cell} {table-cell:}Provides information
about the power available to the rack component. {table-cell} {table-row} {table-row} {table-cell:} *No Power Configuration* {table-cell}
{table-cell:}Selects to indicate that the equipment in the rack is not configured to be connected to other equipment on the floor for power supply.
The rack may receive power over Ethernet, or you may want to ignore power values for this rack in power calculations in the system for other
reasons. \\ \\ {tip:icon=false}*Note*: If selected, power for this rack will be excluded from any power calculations, and no power recommendations
will appear for equipment in this rack. {tip} {table-cell} {table-row} {table-row} {table-cell:} *Rack PDU list* {table-cell} {table-cell:}Provides
information about the rack PDUs mounted in the rack. {table-cell} {table-row} {table-row} {table-cell:} *Connection* {table-cell} {table-cell:}Provides
information about the device supplying power to the rack. {table-cell} {table-row} {table-row} {table-cell:} *Breaker* {table-cell} {table-cell:}Provides
information about the breaker for the rack. These options become active when a power supply has been selected in *Connection*. {table-cell}
{table-row}{table} ||See also|| [Editing Properties]

Power Properties (rack PDU)

{excerpt:hidden=false}This section of the Properties dialog box for a rack PDU identifies the number of *Power Outlets* the device
has.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Power Outlets* {table-cell} {table-cell:}Identifies the number of power outlets the
device has. {table-cell} {table-row} {table-row} {table-cell:} *Voltage Outputs* {table-cell} {table-cell:}Identifies the output voltages the device can
supply. {table-cell} {table-row}{table} ||See also|| [Editing Properties]

Power Properties (server, blade server, blade enclosure)

{excerpt:hidden=false}This section of the Properties dialog box identifies power attributes associated with a server, blade server, and blade
enclosure.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Consumption* {table-cell} {table-cell:}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF} * *Manufacturer's Nameplate*: Identifies the nameplate value of the selected server. * *Estimated
Load*: Identifies the estimated load of the selected server. You can use this field to decrease the load that is used by the system to compute the
capacity calculations. \\ \\ {tip:icon=false}*Note*: In blade solutions, the estimated load on the blade enclosure is used instead of the estimated
load on the blade servers. If the server is a blade server, this field is for your information only, and the value is not used for capacity calculations.
{tip} {panel} {table-cell} {table-row} {table-row} {table-cell:} *Input Voltage* {table-cell} {table-cell:}Lists the available input voltages. {table-cell}
{table-row} {table-row} {table-cell:} *Power Inlets* {table-cell} {table-cell:}Identifies the amount of power inlets. {table-cell} {table-row} {table-row}
{table-cell:} *Criticality options* {table-cell} {table-cell:}Lists redundancy options. {table-cell} {table-row} {table-row} {table-cell:} *Connections*
{table-cell} {table-cell:}Lists available rack PDUs (and phases) to connect the server to. {table-cell} {table-row}{table} ||See also|| [Editing
Properties]

Power Properties (UPS)

{excerpt:hidden=false}This section of the Properties dialog box identifies power attributes associated with a
UPS.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Distribution* {table-cell} {table-cell:}Defines the power capacity of a UPS, and
selects the PDU to which that UPS connects. {table-cell} {table-row} {table-row} {table-cell:} *Redundancy* {table-cell} {table-cell:}Selects the
power feed (A or B) for a UPS, and the internal redundancy for that UPS. {table-cell} {table-row} {table-row} {table-cell:} *Power Path Color*
{table-cell} {table-cell:}Allows you to change the color associated with the power path for the UPS. {table-cell} {table-row}{table} ||See also||
[Editing Properties]

Pump Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a pump, identifies the selected pump by pump package
type. Pump packages are specified based on desired flow rate and piping losses.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:}
*Chilled Water* {table-cell} {table-cell:colspan=2|}Identifies if the cooling method used is chilled water. The pump is circulating chilled water in a
chilled water cooling system. {table-cell} {table-row} {table-row} {table-cell:} *Heat Rejection* {table-cell} {table-cell:colspan=2|}Identifies if the
cooling method used is heat rejection. The pump is circulating glycol solutions and condenser water to the cooling tower or dry cooler. {table-cell}
{table-row}{table} ||See also|| [Editing Properties]

Room Properties
{excerpt:hidden=false}Relevant properties are displayed for the selected room. They vary based on the type of room.{excerpt} h2.
{expand_plain:Cooling Properties (room)} These properties identify cooling attributes associated with the room as a
whole.{table:border=1|frame=box|} {table-row} {table-cell:} *Raised floor leakage* {table-cell} {table-cell:}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF}Sets the percentage of air leaking through the raised floor. The leakage in a typical data center is
10-50%+. You can adjust the default value (30%) by moving the slider. This value is used by the system to calculate the airflow per perforated tile.
* 0%: Perfectly Sealed * 15%: Tight * 30%: Typical * 45%: Leaky * 60%: Very Leaky {panel} {table-cell} {table-row} {table-row} {table-cell:}
*Temperature* {table-cell} {table-cell:}Indicates the *Supply* temperature for all InRow cooling units in the room. The higher the supply
temperature, the higher Capture Index (CI) values you should design for. Ambient and max inlet temperatures are set to default values.
{table-cell} {table-row}{table} {expand_plain} h2. {expand_plain:Custom Room Properties} This section of the Properties dialog box, accessed by
right-clicking a room in the *Navigation* pane, lists custom properties for the selected room.{table:border=1|frame=box|} {table-row} {table-cell:}
*Name* {table-cell} {table-cell:}Defines the property's name. {table-cell} {table-row} {table-row} {table-cell:} *Value* {table-cell} {table-cell:}Defines
the value the property provides. {table-cell} {table-row} {table} {tip:icon=false}*Note*: The listed information is defined by add and edit versions of
a Custom Properties dialog box that are accessed by the *Add* and *Edit* buttons; *Delete* allows you to remove any listed custom property.{tip}
{expand_plain} h2. {expand_plain:General Room Properties} This section of the Properties dialog box, accessed by right-clicking a room in the
*Navigation* pane, provides relevant information that identifies the selected room.{table:border=1|frame=box|} {table-row} {table-cell:} *Name*
{table-cell} {table-cell:}A user-definable value used to identify the room. {table-cell} {table-row}{table} {expand_plain} h2. {expand_plain:Physical
Room Properties - Ceiling} This section of the Properties dialog box, accessed by right-clicking a room in the *Navigation* pane, identifies
physical attributes associated with the ceiling of the room.{table:border=1|frame=box|} {table-row} {table-cell:} *Ceiling height* {table-cell}
{table-cell:}Defines how much space exists between the floor and ceiling. {table-cell} {table-row} {table-row} {table-cell:} *Drop ceiling* {table-cell}
{table-cell:}Selects to identify that a dropped ceiling exists. {table-cell} {table-row} {table-row} {table-cell:} *Tile size* {table-cell}
{table-cell:}Matches the tile overlay in the *Floor Layout* pane to the tiles at the data center. \\ \\ The default setting may not match the data center
tiles. For example, if you selected to use metric measurements for a server room that uses US standard tiles, change the setting from *600 mm*
to *2 feet*. {table-cell} {table-row} {table-row} {table-cell:} *Drop ceiling height* {table-cell} {table-cell:}Defines how much space exists above the
dropped ceiling, when *Drop ceiling* is selected. {table-cell} {table-row} {table-row} {table-cell:} *The space above the drop ceiling extends beyond
the boundaries of the room* {table-cell} {table-cell:}Selects to identify that the space above the dropped ceiling extends beyond the room's walls,
when *Drop ceiling* is selected. {table-cell} {table-row}{table} {expand_plain} h2. {expand_plain:Physical Room Properties - Floor} This section of
the Properties dialog box, accessed by right-clicking a room in the *Navigation* pane, identifies physical attributes associated with the floor of the
room.{table:border=1|frame=box|} {table-row} {table-cell:} *Raised floor* {table-cell} {table-cell:}Selects to identify that the room has a raised floor.
{table-cell} {table-row} {table-row} {table-cell:} *Floor height* {table-cell} {table-cell:}Defines how much space exists below a raised floor, when
*Raised floor* is selected. {table-cell} {table-row} {table-row} {table-cell:} *Tile size* / *Tiles* (Electrical Room only) {table-cell} {table-cell:}Matches
the tile overlay in the *Floor Layout* pane to the tiles in the room. Electrical rooms have no tiles per default, but this can be selected here. \\ \\ The
default setting may not match the room tiles. For example, if you selected to use metric measurements for a server room that uses US standard
tiles, change the setting from *600 mm* to *2 feet*.{table-cell} {table-row} {table-row} {table-cell:} *Grid layout* {table-cell} {table-cell:}Defines the
distance between the grid lines in the layout. You can select between a fine-grained and coarse-grained layout. The grid lines help you align
equipment in the layout and show the distance between them. You will find it useful to select a fine-grained layout, if you want to align equipment
closer together in the layout using the *Snap to grid* right-click option on equipment, leaving no room for unintended space. {table-cell} {table-row}
{table-row} {table-cell:} *Maximum carrying capacity* {anchor:floorcarryprops} {table-cell} {table-cell:}Defines how much equipment weight the floor
supports, measured in kg/m2. {table-cell} {table-row} {table-row} {table-cell:} *Row Layout* (Electrical Room only) {table-cell} {table-cell:} *None*/
*Automatic*: Allows for adding row layout to the electrical room (default value is *None*). {table-cell} {table-row} {table-row} {table-cell:} *Aisle*
{table-cell} {table-cell:}Defines the width (space between rows) for the hot (*Hot aisle width*) and cold (*Cold aisle width*) aisles, as well as
whether the first (top) row is hot (*First aisle hot* selected) or cold. {table-cell} {table-row}{table} {expand_plain} ||See also|| [Editing Properties]

Working with the Catalog

{section}{column:width=50%}{excerpt:hidden=false} {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} includes 2 catalogs, a
master and a custom catalog. h2. Master catalog This is a read-only catalog of available products you can select from and add to the custom
catalog and use in your data center infrastructure, provided you have the necessary user rights. (*Master Catalog* pane to the right in the image).
You can open the master catalog and drag and drop equipment directly into your custom catalog and rearrange products. h2. Custom catalog
This is an editable catalog of selected products you can use in your data center infrastructure. This catalog shows the products relevant to the
selected layout. For example, if you are working in the rack layout, rack-mountable products are available. (*Catalog* pane to the left in the
image). You can right-click the custom catalog to add, rename, or delete categories and to copy or delete products. Multiple users can apply
changes to the catalog at the same time. The custom catalog lists all available equipment and allows you to add floor and rack-mountable
equipment to a rack or any type of room. It has dynamic search functionality: As you start typing in the *Search* box, the catalog shows all
equipment that contains the typed characters.{excerpt} {column} {column:width=50%} !What is new in StruxureWare Operations
7.1?^master_catalog.png|thumbnail! {column} {section} || 123 Steps to... || See also || | *Creating the equipment catalog* \\ Configure the custom
catalog to contain the floor and rack-mountable equipment to add to the data center infrastructure. \\ \\ {tip:icon=false}*Tip*: Before working with
the catalog, open the floor layout. This limits the amount of products to floor-mountable products only. Then open the rack layout before working
with rack-mountable products only.{tip} * *Add categories and products* # Select *Planning>Data Center* in the Application bar. # Access the
Master Catalog through *Tools>Open Master Catalog* or the *Open Master Catalog* icon in the Toolbar. # Drag and drop a product or category
from the master catalog to the custom catalog. The products are placed in the same structure as in the master catalog. # If you need a new sub
category, right-click a category in the custom catalog and select *Add category*. \\ * *Edit categories and products* # Right-click a category in the
custom catalog to add, rename, or delete categories. # Right-click a product to copy or delete products. # Drag and drop products and categories
if you want to restructure the catalog.| [Building the infrastructure and adding inventory]\\ [Adding floor equipment to the room layout|Working with
the Floor Layout]\\ [Adding rack-mountable equipment to the rack layout|Working with the Rack Layout] \\ [Adding gaps and blocks to the room
layout]|

Working with the List View

{section}{column:width=50%}{excerpt:hidden=false}The List view shows the equipment in a selected room or location as a list. You can use the
List View instead of the graphical floor and rack layouts and to view the contents of store rooms.{excerpt} You can open multiple locations or
rooms in the *List View* at the same time, allowing you to compare or drag equipment between them. You can also open one room in multiple
views at the same time, for example allowing you to see its contents in e.g. list view and floor layout at the same time.
{column}{column:width=50%} !listview.png|thumbnail! {column}{section} || 123 Steps to... || See also || | *Filtering List View (Search)* \\ \\ You can
set a filter on the List View to show only the equipment you want to see. \\ \\ 1. In the drop-down list, select a column to search for equipment only
in this column or keep the default value *All columns*. 2. In the *Search* box, start typing some characters of the equipment you want to see. \\ \\
As you type, the pane shows all items that contain the typed character. | [Editing multiple items in List View] [Exporting List View Table]
[Monitoring data center operations in Map View] [Working with the Floor Layout] [Working with the Rack Layout] [Working with the temperature
map in the 3D view]|

Editing multiple items in List View

{excerpt:hidden=false}You can edit multiple items at the same time in the *List View* by using the *Edit Multiple Items* dialog box.{excerpt} # In
*List View*, select the items you want to edit # Click the *Edit Multiple Items* icon or right-click and select the context menu item
!icon_eqbrowser_multiedit.png!\\ # In the *Edit Multiple Items* dialog, select a column to edit, and identify the new value to apply to the selection.
## If you want to ignore the selection of items in step 1, and edit all equipment shown in the *List View*, select the *Edit all items shown*. ||See
also|| [Working with the List View] [Exporting List View Table]

Exporting List View Table

{excerpt:hidden=false}You can export the list of equipment to a file.{excerpt} # Click the export icon to open the *Export* dialog box
!exporttable.png!. # Select file format and browse to identify the destination where you want the file sent, and click *OK* to execute the export and
exit the dialog. ## If you want to export more equipment data than is currently shown in the list, select to include filtered out equipment and/or
hidden columns. ||See also|| [Working with the List View] [Editing multiple items in List View]

Working with the Floor Layout

{section} {column:width=50%} {excerpt:hidden=false}Use the floor layout, accessed from *Floor Layout* in the *Toolbar*, to manage a room's floor
equipment (add, move, delete, or edit equipment properties).{excerpt} You can open multiple locations or rooms in the Floor Layout at the same
time, allowing you to compare or drag equipment between them. You can also open one room in multiple views at the same time, for example,
allowing you to see its contents in e.g. list view and floor layout at the same time. h2. Floor Layout Views The selected floor layout view defines
what information is shown in the layout pane for equipment in the floor layout. You can switch to see the floor layout in another view by selecting
another view tab at the bottom of the layout pane. {tip:icon=false}*Note*: You must have a valid license for the add-on modules to see [all
views|Floor Layout Views] in your system.{tip} {column}{column:width=50%} !floorview.png|thumbnail! {column}{section} || 123 Steps to... || See
also || | *Adding floor equipment to the room layout* \\ \\ Before adding floor-mounted equipment to the layout, select *Planning* *> Data Center*
in the Application bar and select to view a room in *Floor Layout* (by double-clicking the room that you want to add equipment to in *Navigation*).
# Drag the component icon into the position in the floor layout that matches its position in the data center: #* To add new equipment from the
product catalog, drag it from the *Catalog* pane. #* To add existing equipment from another position in the data center model, drag it from the
*Navigation* pane. When you drag equipment into a selected room, green highlights where it can be placed; red highlights where it cannot. In
addition, an exclamation-point icon indicates rack equipment that needs supporting equipment added to its rack. # Right-click the component icon
and select *Properties* to e.g. define a custom name for it, or to use other menu options. # Repeat steps 1 and 2 to add all floor equipment to the
floor layout. \\ \\ {tip:icon=false}*Tip*: You can move multiple items at the same time by using Ctrl-click or Shift-click.{tip}You can associate the
components added to the layout with devices monitored by the {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} or other
external system to get live data from the devices in operation. | [Adding gaps and blocks to the room layout] [Building the infrastructure and
adding inventory] [Configuring floor weight carrying capacity] [Exporting Layout as Image] [Positioning components in the floor layout] [Working

with raised floor environments in the Plenum view] [Floor Layout Views] [Showing or hiding floor and rack views] [Preferences: Showing or hiding
tool tips|Reviewing system preferences#pref_tooltip] [Preferences: Showing floor dimensions in meters or feet|Reviewing system
preferences#pref_meas] |

Configuring floor weight carrying capacity

{excerpt:hidden=false}The physical room properties for a room include how much equipment weight the floor can carry. The system guides you to
help you avoid placing equipment that is too heavy for the floor to carry.{excerpt} Different carrying weight values are used depending on type of
material and whether it is a raised floor environment. * Wooden floor: up to 400-500 kg/m (or about 82-102 lb/sq.ft) * Concrete floor: from about
500 kg/m ending well into a couple of thousand kg/m (or about 102 lb/sq.ft) * Standard raised floor: 600-1200 kg/m (or about 123-245 lb/sq.ft) *
Standard raised floor point-carrying weight: 150-300 kg/point (not covered by this version of the application). In addition, the system calculations
are based on the following: * The carrying weight of a floor or section of the floor is evenly distributed. This means that it does not matter where on
a specific tile a load is placed. \\ Calculations based on point-carrying weight are not covered by this version of the application. * Items other than
racks, such as UPS, PDU, or cooling units, do not add to the weight calculations. * Cables do not add to the weight of the racks. If you want to
include weight information in your configuration, define the carrying capacity of the floor and the weight of equipment placed in the floor layout. If
you do not want to use weight information, leave the weight options empty. # Configure floor carrying capacity. ## Right-click a room and select
*Properties>Room*. ## Define the *Floor Carrying Capacity* in the *Floor* page to match your physical environment. # Configure equipment
weight. ## Right-click the piece of equipment in the floor layout and select *Properties*. ## In the *Physical* page, define the *Weight* or
*Maximum Weight* of the rack or equipment in the rack. ||See also|| [Equipment weight exceeds the weight limit of the floor] [Floor supports
weight of equipment] [Maximum carrying capacity|Room Properties#floorcarryprops] [Physical Properties] [Working with the Floor Layout]

Positioning components in the floor layout

h2. Positioning components closely together Changing the layout to fine-grained might make it easier for you to position a component against
another. Before moving the floor-mounted equipment in the layout, select *Planning > Data Center* in the Application bar and select to view a
room in *Floor Layout* (by double-clicking the room that you want to add equipment to in *Navigation*). # Drag the component icon into the
position in the floor layout that matches its position in the data center: When you drag equipment, green highlights where it can be placed; red
highlights where it cannot. # If you cannot move the components close enough to one another, you can change the grid layout to fine-grained in
the floor properties and use the snap to grid option to be able to move the components along the fine-grained grid lines. ## Right-click the floor
layout and select *Properties > Floor*, and then select *Fine-grained Grid layout*. ## Right-click the component icon and select *Snap to grid*. ##
Drag the component icon to the position of your choice.\\ \\ {tip:icon=false}*Tip*: You can move multiple items at the same time by using Ctrl-click
or Shift-click.{tip} h2. Aligning selected components in the floor layout # Select multiple pieces of equipment by using Ctrl+click or Shift+click. #
Right-click and select *Align selected equipment*. This is useful, for example if you have imported a big data center layout with some misaligned
equipment. h2. Adding selected components to a new row # Select multiple pieces of equipment by using Ctrl+click or Shift+click. # Right-click
and select *Add to New Row*. You have moved the selected equipment into a new row in the floor layout. The new row fits the equipment. This is
useful to quickly create rows and position equipment, for example if you have a layout with both horizontal and vertical rows. ||See also|| [Working
with the Floor Layout]

Exporting Layout as Image

{excerpt:hidden=false}You can export the layout to a file.{excerpt} # Select *File* *> Export* *> Layout as image* to access the *Export* dialog. #
Select which room or rooms to export and which layout view to export. # Select the required image file format and browse to identify the
destination where you want the file to be saved, and click *OK* to execute the export and exit the dialog. ||See also|| [Working with the Floor
Layout]

Floor Layout Views

{excerpt:hidden=false}The selected floor layout view defines what information is shown in the layout pane for equipment in the floor layout. You
can switch to see the floor layout in another view by selecting another view tab at the bottom of the layout pane.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell:} *Alarms* {table-cell} {table-cell:}Alarm icons help you identify precisely where the alarms
occur in the data center model, for example on a specific UPS in the layout and what the severity of the alarm is. (This view is variable when
*Operations* is selected in the Application bar.) {table-cell} {table-row} {table-row} {table-cell:} *Capacity Group* {table-cell} {table-cell:}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Color is used to identify which racks are parts of specific capacity groups.
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature) * Racks in the same capacity group all use the same color. *
Racks not associated with a capacity group are shown in white. {panel} {table-cell} {table-row} {table-row} {table-cell:} *Cooling* {table-cell}
{table-cell:}The *Cooling* view gives you a good indication of the effectiveness of the active cooling configuration as well as a qualified estimation
of the effect of changes in supply temperature, airflow, and number of cooling units and room-based cooling parameters.{table-cell} {table-row}
{table-row} {table-cell:} *Floor Loading* {table-cell} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Color is used
to identify how much the equipment placed in the floor layout weighs compared to the carrying capability of the floor. * Green: the floor can carry
the equipment * Red: the weight of the equipment exceeds the floor's carrying capability. \\ \\ {tip:icon=false}*Note*: The floor weight capability is
measured in kg/m or lb/sq.ft. The weight of the equipment is converted into the same unit to identify how much it would weigh per m or lb/sq.ft,
and the percentage of used weight capacity is shown.{tip}{panel} {table-cell} {table-row} {table-row} {table-cell:} *Measured Load* {table-cell}
{table-cell:}Data is shown for UPS and racks in the layout that identify how much of each UPS or rack's maximum kW power is in use.
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature) {table-cell} {table-row} {table-row} {table-cell:} *Physical*
{table-cell} {table-cell:}Each device in the layout is identified by a device-type symbol. For example, a rack is identified by *R*. {table-cell}
{table-row} {table-row} {table-cell:} *Plenum* {table-cell} {table-cell:}This view of the data center floor layout shows plenum airflow velocities and
perforated tile airflow rates. The tile airflow rate is indicated by tile color and is also shown in the pop-up box when the cursor is placed over a
tile.{table-cell} {table-row} {table-row} {table-cell:} *Power Capacity* {table-cell} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF|
bgColor=#FFFFFF}A color bar is used to identify device capacity consumption compared to the planned recommended values for that device.
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature) * Green identifies device with remaining power * Red identifies
device exceeding the recommended capacity{panel} {table-cell} {table-row} {table-row} {table-cell:} *Power Path* {table-cell} {table-cell:}Color is
used to identify the power connections between equipment. If the connections span different rooms, the item that is supplied with power from an
item in another room will be marked with an icon to indicate the distance (white arrow on a blue background). {table-cell} {table-row} {table-row}
{table-cell:} *Rack U-Space* {table-cell} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Color is used to identify
how many U-positions are available in the racks. * Green: 0-50 % of available space in the rack has been used. * Yellow: 51-85 % of available

space in the rack has been used. * Red: 86-100 % of available space in the rack has been used. At zoom level 90% and above: A color bar is
used to identify how many U-positions are available in the each rack. The amount of Total, Used, and Free U-positions are displayed next to the
bar. At zoom level 89% and below: The racks are colored, and numbers indicate the amount of free U-positions. {panel} {table-cell}
{table-row}{table} ||See also|| [Working with the Floor Layout]

Floor Layout right-click options

{excerpt:hidden=false}When you are working in the *Floor Layout*, right-click options are available for equipment in the *Layout* or *Navigation*
pane of any room or store room, or in the *Catalog* pane. They may not all be available depending on where you access
them.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:colspan=2|}Shared Rack and Equipment Options {table-cell} {table-row}
{table-row} {table-cell:} *Snap* {table-cell} {table-cell:}Defines how racks and floor equipment will react to grids, rows, and walls when moved into
or around a room. {table-cell} {table-row} {table-row} {table-cell:} *Execute Planned Change* {table-cell} {table-cell:rowspan=2|} These two options
are available only for racks or equipment that have been marked with small circles with symbols (+, x, and arrows) to indicate changes planned
when *> Planning* *> IT Change* was selected in the Application bar. ({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true}
feature). \\ \\ A change that is executed and saved is incorporated in the layout for the affected server room or store room. {table-cell} {table-row}
{table-row} {table-cell:} *Cancel Planned Change* {table-cell} {table-row} {table-row} {table-cell:} *Asset Audit* {table-cell} {table-cell:}Generates an
Asset Audit Report window for a component. \\ \\ This option is disabled if more than one component is selected.{table-cell} {table-row} {table-row}
{table-cell:} *Show in Editor* {table-cell} {table-cell:}Highlights the selected device or room in the *Layout* pane when you right-click it in the
*Navigation*, *Equipment Browser*, or *Power Dependency* pane. {table-cell} {table-row} {table-row} {table-cell:} *Show in Navigation* {table-cell}
{table-cell:}Highlights the selected device or room in the *Navigation* pane when you right-click it in the *Layout*, *Equipment Browser*, or *Power
Dependency* pane. {table-cell} {table-row} {table-row} {table-cell:} *Cut* {table-cell} {table-cell:}Cuts the selected item or items. The selection is
only marked for being cut, and not actually cut away from its position until you paste it in another position. {table-cell} {table-row} {table-row}
{table-cell:} *Paste* {table-cell} {table-cell:}Pastes a selection of one or more items into this position. {table-cell} {table-row} {table-row} {table-cell:}
*Delete* {table-cell} {table-cell:}Deletes floor equipment, rack-mounted equipment, or a rack and all its contents. \\ \\ This option is disabled for a
rack that has any planned changes to any of its rack-mounted equipment that have not been executed (*Execute Planned Change*) or cancelled
(*Cancel Planned Change*).{table-cell} {table-row} {table-row} {table-cell:} *Properties* {table-cell} {table-cell:}Accesses the Properties dialog box
to view or modify the settings for a room, rack or other equipment. {table-cell} {table-row} {table-row} {table-cell:colspan=2|}Rack-only options
{table-cell} {table-row} {table-row} {table-cell:} *Asset Inventory* {table-cell} {table-cell:}Generates a report that identifies the contents of the
selected rack. This option is also available to identify the contents of a selected room when right-clicking a room.{table-cell} {table-row}{table}
||See also|| [Working with the Floor Layout]

Working with the Rack Layout

{section}{column:width=50%}{excerpt:hidden=false}Use the rack layout tool, accessed from *Rack Layout* in the *Toolbar*, to manage any
electrical room's or server room's rack-mountable equipment (add, move, delete, or edit equipment properties).{excerpt} You can open multiple
locations or rooms in the Rack Layout at the same time to compare or drag equipment between them. You can also open one room in multiple
views at the same time, for example to see its contents in the list view and rack layout at the same time. The applied view defines what
information is shown in the rack layout. You can change the selection by clicking the tabs at the bottom of the layout.
{column}{column:width=50%} !rackview.png|thumbnail! {column}{section} || 123 Steps to... || See also || | *Adding rack-mountable equipment to
the room layout* \\ \\ Before adding rack-mountable equipment to the layout, select *Planning* *> Data Center* in the Application bar and select to
view a room in *Rack Layout*, for example by double-clicking a rack in the *Floor Layout*. # Drag the component icon into the position in the rack
layout that matches its position in the data center or use the placement advisor functionality to automatically add components in the rack layout
according to the selections you make in the *Rack-Mount Equipment Placement* pane
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} functionality): #* To add new equipment from the product catalog, drag
it from the *Catalog* pane. #* To add existing equipment from another position in the data center model, drag it from the *Navigation* pane. #* To
add new equipment by using the placement advisor functionality of the *Rack-Mount Equipment Placement* pane in conjunction with the *Power
Details* view of the rack layout: ### Select the *Power Details* view (tab at the bottom of the rack layout pane) to activate the color-coded view of
the rack layout. ### Select the component in the *Catalog* pane. ### Review the *Equipment info* section of the *Rack-Mount Equipment
Placement* pane, e.g. making sure that the *Redundancy* setting is correct. ### Add or review tags as required in *Assign tags* section of the
*Rack-Mount Equipment Placement* pane to categorize the equipment. ### In the *Add Equipment* section of the *Rack-Mount Equipment
Placement* pane type how many copies of the component to add and select where to add it: *Selected racks*, *Each rack in the server room*,
*Best rack*. ### Click *Add Equipment*.\\ When you drag equipment into a selected rack, green highlights where it can be placed; red highlights
where it cannot be placed. # Repeat above steps to add all rack-mountable equipment to the rack layout.\\ \\ {tip:icon=false}*Tip*: You can move
or delete multiple items at the same time by using Ctrl-click or Shift-click.{tip} # Right-click the component icon and select *Properties* to e.g.
define a custom name for it, or to use other menu options. | [Rack Layout Views]\\ [Building the infrastructure and adding inventory]\\ [Working
with the Floor Layout]\\ [Showing or hiding floor and rack views] \\ [Preferences: Showing or hiding tool tips|Reviewing system
preferences#pref_tooltip] |

Rack Layout Views

{excerpt:hidden=false}The selected rack layout view defines what information is shown in the layout pane for equipment in the rack layout. You
can switch to see the rack layout in another view by selecting another view tab at the bottom of the layout pane.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell} *Alarms* {table-cell} {table-cell}Alarm icons help you identify precisely where the alarms occur
in the data center model, for example on a specific rack PDU in the layout and what the severity of the alarm is. (This view is variable when
*Operations* is selected in the Application bar.) {table-cell} {table-row} {table-row} {table-cell} *Equipment Loading* {table-cell} {table-cell}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Color bars below the racks identify how much weight has been placed in a rack or
room compared to the predefined carrying capability settings. The *Rack* bar illustrates the weight of the equipment added to the rack in the rack
layout compared to the maximum equipment loading capability of the rack. These values are also shown in the rack's *Physical Properties* page.
* Weight of equipment added to the rack: *Current weight* minus *Weight*. * Maximum equipment loading capability of the rack: *Maximum
weight*. The *Floor* bar illustrates the total weight of the rack and its contents compared to the floor carrying capability. {tip:icon=false}*Note*:
The calculation takes into account how much space the rack takes up in the floor layout (kg/footprint or lb/footprint), to get a per rack value rather
than per m or sq.ft. value for the available weight loading capacity.{tip} These values are also shown in the properties. * Weight of the rack and its
contents: *Current weight* in the rack's *Physical Properties* page. * Floor carrying capabilities: *Floor Carrying Capacity* in the room's *Floor
Properties* page. * Rack footprint: *Width* and *Depth* in the rack's *Physical Properties* page. {panel} {table-cell} {table-row} {table-row}

{table-cell} *Equipment Placement Advisor* {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Color

highlights are used in the racks to indicate what position is best suited for the selected equipment
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature) * Green: Optimum location for the equipment * Yellow: Not
optimum but possible location (may result in stranded capacity) * Red: Location violating your setup (may result in power overload){panel}
{table-cell} {table-row} {table-row} {table-cell} *Physical* {table-cell} {table-cell}The racks and their contents are shown, only. {table-cell}
{table-row} {table-row} {table-cell} *Power Details* {table-cell} {table-cell}Power capacity data is provided above each rack that identifies in detail
how much of each rack's estimated load is in use. ({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature) {table-cell}
{table-row}{table} ||See also|| [Working with the Rack Layout]

Rack Layout right-click options

{excerpt:hidden=false}When you are working in the Rack Layout, right-click options are available for rack and rack-mountable equipment in the
*Layout* or *Navigation* pane of any room, electrical room or store room, or in the *Catalog* pane. They may not all be available depending on
where you access them.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:colspan=2|}Shared Rack and Equipment Options {table-cell}
{table-row} {table-row} {table-cell} *Snap* {table-cell} {table-cell}Defines how racks and floor equipment will react to grids, rows, and walls when
moved into or around a room. {table-cell} {table-row} {table-row} {table-cell} *Simulate Impact* {table-cell} {table-cell}Generates a list of equipment
that would be impacted if the selected piece of equipment, e.g. a UPS or cooling unit, was to fail. {table-cell} {table-row} {table-row} {table-cell}
*Execute Planned Change* {table-cell} {table-cell:rowspan=2|} These two options are available only for racks or equipment that have been
marked with small circles with symbols (+, x, and arrows) to indicate changes planned when *> Planning* *> IT Change* is selected in the
Application bar. ({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature) A change that is executed and saved is
incorporated in the layout for the affected server room or store room. {table-cell} {table-row} {table-row} {table-cell} *Cancel Planned Change*
{table-cell} {table-row} {table-row} {table-cell} *Asset Audit* {table-cell} {table-cell}Generates an Asset Audit Report window for a component. This
option is disabled if more than one component is selected.{table-cell} {table-row} {table-row} {table-cell} *Show in Editor* {table-cell}
{table-cell}Highlights the selected device or room in the *Layout* pane when you right-click it in the *Navigation*, *Equipment Browser*, or *Power
Dependency* pane. {table-cell} {table-row} {table-row} {table-cell} *Show in Navigation* {table-cell} {table-cell}Highlights the selected device or
room in the *Navigation* pane when you right-click it in the *Layout*, *Equipment Browser*, or *Power Dependency* pane. {table-cell} {table-row}
{table-row} {table-cell} *Cut* {table-cell} {table-cell}Cuts the selected item or items. The selection is only marked for being cut and not actually cut
away from its position until you paste it in another position. {table-cell} {table-row} {table-row} {table-cell} *Paste* {table-cell} {table-cell}Pastes a
selection of one or more items into this position. {table-cell} {table-row} {table-row} {table-cell} *Delete* {table-cell} {table-cell}Deletes floor
equipment, rack-mounted equipment, or a rack and all its contents. This option is disabled for a rack that has any planned changes to any of its
rack-mounted equipment that have not been executed (*Execute Planned Change*) or cancelled (*Cancel Planned Change*). {table-cell}
{table-row} {table-row} {table-cell} *Properties* {table-cell} {table-cell}Accesses the Properties dialog box to view or modify the settings for a room,
rack or other equipment. {table-cell} {table-row} {table-row} {table-cell:colspan=2|}Rack-only options {table-cell} {table-row} {table-row} {table-cell}
*Asset Inventory* {table-cell} {table-cell}Generates a report that identifies the contents of the selected rack. This option is also available to identify
the contents of a selected room when right-clicking a room. {table-cell} {table-row} {table-row} {table-cell} *Clear Components* {table-cell}
{table-cell}Deletes devices from a rack. {table-cell} {table-row} {table-row} {table-cell:colspan=2|}Equipment-only options {table-cell} {table-row}
{table-row} {table-cell} *Rack* {table-cell} {table-cell}Accesses three options described in the Shared Rack and Equipment Options section of this
table: *Clear Components*, *Delete*, and *Properties*. These options are available only when you right-click rack-mountable equipment.
{table-cell} {table-row} {table-row} {table-cell} *Move to Rack* {table-cell} {table-cell}Moves rack-mountable equipment from one rack to another.
{table-cell} {table-row} {table-row} {table-cell} *Mounting* {table-cell} {table-cell}Views or modifies the rack mounting position of a rack-mountable
component. {table-cell} {table-row}{table} ||See also|| [Working with the Rack Layout]

Configuring Blade Solutions

{section}{column:width=50%}{excerpt:hidden=false}Blade solutions are typically used when there is a need for high server density, power and
cooling efficiency, and more flexible management functions than solutions with traditional servers provide. {excerpt} Blade servers are very
compact servers. Many components have been removed to save space, minimize power consumption, and other considerations. Power and
cooling supply is handled by the enclosure instead. A blade enclosure can be mounted in a rack and contains a number of bays in which the
blade servers (also referred to as blades) are placed. Bays and blade servers can be half-height or full-height, single-width or double-width. The
standard product catalog installed with the application contains the most commonly used blade products. You can configure any additional blades
and blade enclosures that you use to your custom catalog, setting the number of bays and bay height and width (in any combination). {column}
{column:width=50%} !blade.png|thumbnail! {column} {section} || 123 Steps to... || See also || | *Adding blade equipment to the rack layout* \\
{excerpt:hidden=false}The system guides you in placing the blade equipment in the rack layout. This ensures that blade enclosures fit into the
rack and that blades fit into the enclosure bays. {excerpt}Before adding blade equipment to the layout, select *Planning* *> Data Center* in the
Application bar and select to view a room in *Rack Layout*, for example by double-clicking a rack in the *Floor Layout*. # Drag the blade
enclosure icon into the position in the rack layout that matches its position in the data center. # Drag the blade server icon into the position in the
rack layout that matches its position in the data center. \\ * Green highlights where you can place the equipment * Yellow highlights where you can
place some of the equipment (the system will place what fits and leave out what does not fit) * Red highlights where you cannot place the
equipment \\ \\ 3. Repeat above steps to add all blade equipment to the rack layout. \\ \\ {tip:icon=false}*Tip*: You can move or delete multiple
items at the same time by using Ctrl-click or Shift-click.{tip} 4. Right-click the component icon and select *Properties* to e.g. define a custom name
for it, or to use other menu options.| [Valid blade configuration]

Valid blade configuration

{excerpt:hidden=false}The system ensures a valid configuration and guides you in placing blades in the bays of the blade enclosures based on
the configured physical properties of the equipment. {excerpt} {table:border=1|frame=box|} {table-row} {table-cell:}Supported configurations
{table-cell} {table-cell:}Any combination of full / half height with double / single width blades. {table-cell} {table-row} {table-row} {table-cell:}Amount
{table-cell} {table-cell:}The system validates that there are a sufficient amount of bays available in the blade enclosure to contain the amount of
bays that the blade servers take up. {table-cell} {table-row} {table-row} {table-cell:}Product family {table-cell} {table-cell:}If the blade enclosure has
been specified to be of a certain brand or product family, only blades with the same properties can be placed in it. If there is no product family
defined for the blade enclosure, only blades that have no product family defined either can be added to this enclosure. {table-cell}
{table-row}{table}

Configuring power connections

{section}{column:width=50%}{excerpt:hidden=false}Configuring power paths is a prerequisite for enabling some of the more advanced features,
such as the equipment placement advisor. Power dependencies can be configured on the device properties to identify the power connections,
e.g. from UPS to PDU to rack PDU.{excerpt} The *Power Dependency* pane lists the configured power dependencies between the equipment in
the data center model. The *Power Path* view in the *Floor Layout* highlights the configured power connections in the layout. You can
enable/disable views in the floor and rack layouts by using the *Manage Visible Overlays* icon above the graphical layout.
{column}{column:width=50%} !powerconnections.jpg|thumbnail!{column}{section} || 123 Steps to... || See also || | *Setting up a power path* \\ \\
{excerpt:hidden=false}You can set up the power connections between the equipment supplying and delivering power and the equipment requiring
power. Before configuring the power path, you must configure the data center layout and add equipment to the floor and rack layout.{excerpt} # In
the Application bar, select *Planning* *> Data Center*. # In a room's *Floor Layout*, right-click a PDU and select *Properties* or use the *Power
Dependency* or *Equipment Browser* pane to access the power property pages for any piece of equipment by right-clicking it, and selecting
*Properties*. # In the Properties dialog box, go to the *Power Dependency* section to select a power supply and enter connection details for the
connection between the UPS and PDU. # In the *Power Distribution* section, select the rack PDU and enter connection details for the connection
between the PDU and rack PDU. # Select the *Power Path* tab at the bottom of the floor layout pane to highlight the configuration of power
connections through the server room in the layout. The above describes a very basic setup. A power path can be more advanced and include
more components such as RDP or Power Panel. For example, the UPS and a Power Panel can be placed in one room and be connected to a
PDU or Power Panel in another room. \\ | [Working with the Equipment Placement Advisor] \\ [Showing or hiding floor and rack views] \\ [Rack is
without rack PDU or a rack PDU is not powered] \\ [An invalid power path has been configured] \\ [Connection has not been configured between
PDU and power supply] \\ [Connection has not been configured between Power Panel and power supply] \\ [Connection has not been configured
between remote distribution panel (RDP) and power supply] \\ [Equipment connected to this PDU draws more power than is supported by the
power supply breaker] \\ [Equipment connected to this Power Panel draws more power than is supported by the power supply breaker] \\
[Equipment connected to this remote distribution panel (RDP) draws more power than is supported by the power supply breaker] \\ [Equipment in
this rack receives power from multiple power supply devices] \\ [Equipment is connected to a rack PDU outside this rack] \\ [PDU and connected
rack PDU are placed in different rooms] \\ [Power connection configuration is invalid for equipment in one or more racks in the group] \\ [This
equipment in store room is connected to equipment in a room] \\ |

Power Dependency Properties

{excerpt:hidden=false}This section of the Properties dialog box identifies power dependency attributes associated with the
component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Connection* (e.g. Power Panel, RDP, PDU) {table-cell}
{table-cell:}Identifies the components that a remote distribution panel (RDP), PDU, Power Panel or rack PDU connects to for power. {table-cell}
{table-row} {table-row} {table-cell:} *Breaker* {table-cell} {table-cell:}Provides information about the breaker used by for the power provided to a
remote distribution panel (RDP), Power Panel, PDU, or rack PDU. {table-cell} {table-row}{table} ||See also|| [Configuring power connections]
[Editing Properties]

Power Distribution Properties

{excerpt:hidden=false}This section of a Properties dialog box allows you to identify the components that get power from a remote distribution
panel (RDP), Power Panel or PDU, and, for a PDU, the output voltage supplied to those components.{excerpt}{table:border=1|frame=box|}
{table-row} {table-cell:} *Power consumption list (RDP, Power Panel or PDU)* {table-cell} {table-cell:}Lists components that receive power from the
selected PDU, Power Panel or remote distribution panel (RDP), including information about the breakers involved. The listed information is
defined by new and edit versions of a Power Connection dialog box that are accessed by the *New* and *Edit* buttons; *Delete* allows you to
remove any listed component. {table-cell} {table-row} {table-row} {table-cell:} *Output Voltage (PDU only)* {table-cell} {table-cell:}Identifies the
output voltage values. The value selected here must match the value of the connected equipment to be able to set up a valid power connection.
{table-cell} {table-row}{table} ||See also|| [Configuring power connections] [Editing Properties]

New Power Connection Properties

{excerpt:hidden=false}Use the *New Power Connection* dialog box, which is accessed by *Power Dependency* (CRAC) or *Power Distribution*
(PDU or remote distribution panel (RDP)) buttons, to add a new power connection (*New*) or to edit an existing task (*Edit*). You must select the
device involved in the connection, and all breaker values must be defined, except the name, before clicking the *OK*
button.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Connection* {table-cell} {table-cell:}Select the component using the *Power
distribution* (CRAC) or *Power consumption* (PDU or remote distribution panel (RDP)) drop-down list. *Power consumption* identifies the
selected CRAC, and *Power supply*, the selected PDU or remote distribution panel (RDP); *Supplier location* (CRAC) or *Consumer location*
(PDU or remote distribution panel (RDP)) identifies the location of the device selected in the drop-down list. {table-cell} {table-row} {table-row}
{table-cell:} *Breaker* {table-cell} {table-cell:}Identify the breaker involved in the power connection, by name, rating, and derating values, as well
as the *Power phase* used to provide the connection's power. {table-cell} {table-row} {table} ||See also|| [Configuring power connections] [Editing
Properties]

Configuring cooling
{section}{column:width=50%}{excerpt:hidden=false}The application gives you a fail/pass indication of the effectiveness of the active cooling
configuration. As the design takes place, you get a qualified estimation of the effect of changes in supply temperature, airflow, and number of
cooling units and room-based cooling parameters.{excerpt} h2. Cooling The *Cooling* view of the data center floor layout shows a color-coded
overview of the Capture Index. You can use this view to get an overview of the reasons why the tile airflow may not be the same across the room.
Each rack in a well-formed hot aisle / cold aisle layout shows a color-coded capture index (CI) percentage. The CI value identifies inlet air which is
supplied by what fraction of the equipment's exhaust airflow is captured by the InRow cooling units included in that row pair or by the CRAC or
CRACs in the room through the perforated tiles. {column} {column:width=50%} !coolingview.png|thumbnail! {column} {section}
{section}{column:width=50%} h2. 2D Plenum airflow Subsequently, you can use the *Plenum* view to drill down into looking at specific velocity
issues in the plenum and estimate perforated tile airflow rates. When you drag in a new cooling unit or move a perforated tile, the flow vectors and
perforated tile flow rates update instantly. {column} {column:width=50%} !plenum_view.jpg|thumbnail! {column} {section}
{section}{column:width=50%} h2. Airflow in 3D In the *3D* view, you can see the room's airflow above the raised floor. Velocity vector and
temperature results look like those from traditional CFD applications and provide the same ability to quickly locate problem spots and understand

the underlying causes. You can have multiple rooms open in the 3D view at a time. When you have opened a room in 3D view or applied changes
to the configuration, click *Start* to regenerate the calculations and show the updated view. Subsequently, you can select *File>Export* and
export to .xml or export directly to .pdml without using conversion tools. {column} {column:width=50%} !3D.png|thumbnail! {column} {section} ||See
also|| [Performing cooling simulation in the Cooling view] [Working with raised floor environments in the Plenum view] [Working with the
temperature map in the 3D view] [Cooling configuration accuracy and design guidelines]

Performing cooling simulation in the Cooling view

{section}{column:width=50%}{excerpt:hidden=false}The cooling simulation tool enables you to simulate the effect of potential changes to the
cooling conditions. {excerpt} You can use the *Cooling* view, accessed through the *Cooling* tab in the Floor Layout, to see why the tile airflow
may not be the same across the room. You can simulate where to place equipment without overheating the room or creating hotspots by following
the color-coded indications, for example position new devices and move or delete existing devices without exceeding recommended exhaust air
captured by the cooling units. Select the *Cooling* tab in the *Floor Layout*. # Add CRACs, InRow cooling units and perforated tiles as needed
by dragging them from the *Catalog* into the layout. # Review or modify the cooling settings of the added equipment or the room as needed by
right-clicking the item, and selecting *Properties*, and using the settings in the *Cooling* page. # Simulate failure of one or more cooling units by
selecting one or more cooling units in the floor layout, right-clicking, and deselecting *Activate*. # Simulate cooling performance changes of one or
more racks by selecting one or more racks in the floor layout, right-clicking and selecting *> Cooling* *> Normal: 160 CFM/kW*, *Blade: 105
CFM/kW* or another value*, if available. \\ \\ {tip:icon=false}*Tip*: To select more than one cooling unit, hold down the Ctrl key and select the
items, or drag a box around the items you want to select.{tip} *Value defined in the Rack's cooling properties page. {column}{column:width=50%}
!CI_labelsexplained.png|thumbnail! {column}{section} ||See also|| [Configuring cooling] [Working with raised floor environments in the Plenum
view]

Simulating rack and CRAC cooling changes

{excerpt:hidden=false}{excerpt} 1. Simulate failure of one or more cooling units by selecting one or more cooling units in the floor layout,
right-clicking and deselecting *Activate CRAC*. Figure 1: A single InRow cooling unit was deactivated. This had no affect on the CI ratings for any
racks in the equipment cluster, indicating that the cluster can withstand a single failure (N+1). !cooling_cracairflowonedeactivated.png!\\ Figure 2:
An InRow cooling unit was deactivated in the other row, resulting in a rack in Row B turning yellow to indicate that not all exhaust air is being
captured. !cooling_cracairflowmoredeactivated.png!\\ You can simulate the effect deactivating different cooling units will have on the airflow in
equipment clusters, for example, on shutdown for maintenance. 2. Simulate cooling performance changes of one or more racks by selecting one
or more racks in the floor layout, right-clicking and selecting *> Cooling* *> Normal: 160 CFM/kW*, *Blade: 105 CFM/kW* or another value*, if
available. \*Value defined in the Rack's cooling properties page. \\ \\ Figure 3: The *Normal: 160 CFM/kW* option was selected for the yellow rack
placed as fourth from the left in row B. The CI percentage of this rack is 86% and the rack to its right 89%. !cooling_rackairflow160cfm.png!\\ \\
Figure 4: The Blade: 105 CFM/kW option was selected for that same rack as in Example 1, placed as fourth from the left in row B. The CI
percentage of this rack changes to 98% and the rack to its right to 98%. !cooling_rackairflow105cfm.png!\\ || See also || [Configuring cooling]
[Performing cooling simulation in the Cooling view]

Troubleshooting why Capture Index values do not display

{excerpt:hidden=false}The cooling simulation updates based on the equipment placement. If your configuration is invalid, the tool tip will inform
you of the problem. If the cooling calculations do not run, verify your configuration is not invalid due to one of the following: * The distance
between the racks is insufficient (at least 2 feet). Hot air blows from one rack into the front of another rack. To make the cooling configuration
valid, use the room layout icons and drag the row border to make the aisle wider. * The row layout is not well designed. * The equipment is placed
in pairs directly across from each other but is misaligned by 10 cm or more. To make the cooling configuration valid, drag the equipment closer to
each other. * There is a piece of equipment placed in the aisle between the rows. To make the cooling configuration valid, move the equipment
out of the aisle.{excerpt} ||See also|| [Performing cooling simulation in the Cooling view]

What does the cooling tool tip tell me?

h2. Cluster When the system calculates cooling based on the configuration, it groups equipment in clusters. The tool tip appears in the *Cooling*
view when hovering over equipment in the layout that is included in the calculations. For a definition, see [Cluster|Glossary#cluster]. h2. Cooler
supply temperature Cooler supply temperature is a function of cooler capacity and its control algorithm; however, it can be written generally as a
function of cooler return temperature and cooler airflow rate. The tool tip appears in the *Cooling* view when hovering over a cooling unit in the
layout. h2. Cooler return temperature Cooler return temperature is the result of the mixing of streams which originate at rack exhausts or from the
ambient. The tool tip appears in the *Cooling* view when hovering over a cooling unit in the layout. h2. Rack inlet temperature Rack inlet
temperature is the result of the mixing of streams which originate at each cooler source or from the ambient. The tool tip appears in the *Cooling*
view when hovering over a rack in the layout. ||See also|| [Configuring cooling] [Performing cooling simulation in the Cooling view]

Working with raised floor environments in the Plenum view

{section}{column:width=50%}The *Plenum* view of the data center floor layout shows plenum airflow velocities and perforated tile airflow rates for
rooms with raised floor cooling systems. The tile airflow rate is indicated by tile color and is also shown in the pop-up box when the cursor is
placed over a tile. !tile_airflow.jpg|thumbnail! You can relate the plenum velocities to the length or color of the arrows by changing the settings in
*Tools>Preferences>Plenum Velocities*. {column} {column:width=50%}!plenum_view.jpg|thumbnail! {column} {section} {section}
{column:width=50%} The pressure is generally high in areas of low velocity and vice versa. When perforated tiles are placed near CRACs in
regions of high velocity, these tiles will generally deliver less than the average tile airflow rate and may even result in negative airflow, i.e. airflow
directed down into the plenum. The parameters that affect tile airflow uniformity and suggested design practices are shown in the table. You can
set the plenum depth in the *Room Properties*, accessed by right-clicking the room and setting the raised floor height in *Properties>Floor*. You
can add two types of perforated tiles (25% and 56% open area) to the layout from the *Catalog*. The raised-floor leakage is defined as the
fraction of (downflow) CRAC airflow which does not enter the room through perforated tiles but escapes the plenum (but still into the room)
through other openings such as cable cutouts and leakage paths around tiles. Typical data centers may have leakage values in the 10-50%\+
range. You can set the leakage airflow by right-clicking the room layout and using the leakage slider in *Properties>Cooling*. {column}
{column:width=50%}!airflow_uniformity_table.jpg|thumbnail! {column} {section} ||See also|| [Configuring cooling]

About designs with perforated tiles on a raised floor

Error: The XML content could not be parsed. There is a problem at line 5, column 104. Parser message: Unexpected character '=' (code 61);
expected a semi-colon after the reference for entity 'Query_Type' at [row,col {unknown-source}]: [5,104]

Working with the temperature map in the 3D view

{section}{column:width=50%}You can view the data center temperature map in 3D. # Open a room and click the 3D icon. # Click *Start* to
generate the calculations and show the updated view. # Zoom and rotate using the navigation settings to the right to see specific areas in the
layout. # Review and customize the display settings to the right. You can have multiple rooms open in the 3D view at a time. When you have
opened a room in 3D view or applied changes to the configuration, click *Start* to regenerate the calculations and show the updated view.
{tip:icon=false}*Tip*: Click the icon at the bottom of the thermometer to customize the temperature thresholds and color scheme. If the
thermometer does not show, click the arrow icon to invoke it.{tip} {panel:borderWidth=0|bgColor=87D300} !Configuring the room
layout^video24x20.jpg! Watch this [video tutorial|Video Tutorials#3Dvideo] to see how to work in the 3D view. {panel} {column}
{column:width=50%} !Configuring cooling^3D.png|thumbnail! {column} {section} || See also || [Configuring cooling] [Customizing 3D colors and
thresholds]

Customizing 3D colors and thresholds

{section} {column:width=50%} In the 3D view, you can customize the temperature range by adjusting the thresholds for maximum and minimum
temperature. You can also customize the colors of the temperature scale. 1. Access the thermometer settings by clicking the icon at the bottom of
the thermometer in the 3D layout. 2. Customize the thresholds for minimum and maximum temperature in the temperature range by typing the
wanted degrees. 3. Customize the colors for the temperature range by selecting the 5 color icons one by one and defining the color range to
apply. If you regret the color selection, you can select to reset to use the default colors. \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ {tip:icon=false}*Tip*: If the
thermometer does not show, click the arrow icon to invoke it.{tip} \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ To customize the graphical representation of the
velocity arrows, use the settings in *Tools>Preferences>Temperature Map*. These settings define how the arrows will indicate the velocity in the
3D Velocity plane. The different velocities will be represented as arrows of a certain length or color. {column} {column:width=50%}
!3Dsettemperature.png|thumbnail! !invokethermometer.png|thumbnail! \\ Color:\\ !arrows_color.png|thumbnail! Length:\\
!arrows_length.png|thumbnail! {column} {section} ||See also|| [Working with the temperature map in the 3D view]

About cooling redundancy

In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, cooling redundancy refers to the amount of redundant cooling units in
this way: * N: There are no redundant cooling units for the rack. There are one or more coolers in the data center. If ONE cooler fails anywhere in
the data center, it would result in inadequate cooling (yellow or red CI). * N+1: There is one redundant cooling unit for the rack. ONE cooler
(CRAC, row-based, or OA unit) can fail anywhere in the data center and cooling will still be adequate (green CI). * N+2: There are two redundant
cooling units for the rack. TWO coolers (CRACs, row-based, or OA units) can fail anywhere in the data center and cooling will still be adequate
(green CI). * N+x: There are x redundant cooling units for the rack. X coolers (CRACs, row-based, or OA units) can fail anywhere in the data
center and cooling will still be adequate (green CI). ||See also|| [Configuring cooling]

About the Capture Index (CI) colors

{section}{column:width=50%}{excerpt:hidden=false}Each rack in a valid equipment cluster for which cooling can be calculated shows a capture
index (CI) value and is colored based on cooling performance: red ("bad"), yellow ("marginal"), or green ("good").{excerpt} Most configurations are
valid. However, cooling cannot be predicted for some configurations such as when racks are not arranged in alternating cold and hot aisles. In this
case, no CI value or color is shown for any rack in the immediate vicinity of the invalid configuration. For valid clusters, the actual CI value shown
and associated color is based on the larger of the two hot and cold aisle CI metrics for the rack. The CI color coding is related to the cooler supply
and maximum target temperature as shown in the figure below. This color coding ensures better airflow management is enforced as the
difference between cooler supply and maximum target temperatures approach zero. For example, if the cooler supply temperature and maximum
target temperature are both 20C then T=0 and CI must be 100% for a rack to achieve a "green" rating. If the cooler supply temperature is much
lower than the maximum target temperature, there is a large "operating margin" and more tolerance for less ideal airflow management. {column}
{column:width=50%} *Capture Index (CI) color* !CIcolors.png|thumbnail!\\ {column} {section} || See also || [Configuring cooling] [About Capture
Index prediction models]

About Capture Index prediction models

{section}{column:width=50%}h2. Capture Index Cooling-Performance Metric * Unlike temperature-based metrics, Capture Index (CI) is solely a
function of airflow. There are two kinds of CI: ** Cold Aisle CI: the fraction of air ingested by the rack which originates from local cooling resources
(e.g. perforated floor tiles or local coolers) ** Hot Aisle CI: the fraction of air exhausted by a rack which is captured by local extracts (e.g. local
coolers or return vents) * CI measures effectiveness of supplying cooling air to rack inlets or scavenging heated air from rack exhausts on a 0%
(bad) to 100% (good) scale. * CI is defined in terms of local cooling resources (airflow from tiles, local coolers, local extract vents, etc.) and it
measures the robustness and scalability of a grouping of equipment. h2. Example *Cold Aisle* The Cold Aisle Capture Index of the top-middle
rack is 84%. In other words, 84% of the airflow drawn in by that rack originated from the perforated floor tiles. The remaining 16% of inlet air
comes from other sources including the room ambient and recirculation from the subject rack and others. *Hot Aisle* The Hot Aisle Capture Index
of the bottom-right rack is 66%. In other words, 66% of the exhaust airflow from this rack is captured by the local coolers while the additional 34%
escapes, heating the room ambient and, potentially, entering rack inlets. {column} {column:width=50%} !CI.JPG|thumbnail! {column} {section} ||
See also || [Configuring cooling] [About the Capture Index (CI) colors|About the Capture Index (CI) colors]

Cooling configuration accuracy and design guidelines

h2. Cooling configuration accuracy The Potential Flow Models (PFM) used in this application are typically within about 10% of CFD for Capture
Index, Average Rack Inlet Temperature, and perforated tile airflow; they are not as good at predicting maximum rack inlet temperatures. h2.
Cooling design guidelines For the most efficient cooling design, equipment should be placed in clusters. An equipment cluster is two
nearly-equal-length rows of equipment separated by a hot or cold aisle. A row of equipment can be a member of one or two clusters. All heat
generating equipment (racks and UPS) properly positioned in rows will show up color-coded in the Floor layout. However, you will experience
better cooling performance with well formed clusters: * All rows are of similar length and aligned across hot or cold aisles. * The equipment rows
do not include blocks, gaps, or spaces. * In Hot Aisle Containment Systems (HACS), cooling units are positioned in pairs directly across from
each other. *Example: Well formed cluster* !cooling_cracairflowonedeactivated.png!\\ Cooling performance predictions, which assume the racks
are populated evenly, will be more accurate if racks are populated in bottom-to-top order and for more regular room shapes and well-formed
hot/cold aisle layouts. {tip:icon=false}*Note*: If you flip a row to face front to back, it affects the cooling simulation for up to 3 rows. {tip} h2. Cooler
airflow specifications * Cooler airflow in cubic feet per minute (CFM) is assumed to be: {table:border=1|frame=box|} {table-row:align=center}

{table-cell}*Cooler type* {table-cell} {table-cell}*Minimum CFM* {table-cell} {table-cell}*Maximum CFM* {table-cell} {table-row} {table-row}
{table-cell}InRow RC (300 mm) {table-cell} {table-cell}1450 {table-cell} {table-cell}2900 {table-cell} {table-row} {table-row} {table-cell}InRow RC
(600 mm) {table-cell} {table-cell}2760 {table-cell} {table-cell}6900 {table-cell} {table-row} {table-row} {table-cell}InRow RP (600 mm Chilled Water)
{table-cell} {table-cell}2760 {table-cell} {table-cell}6900 {table-cell} {table-row} {table-row} {table-cell}InRow RP (600 mm Air Cooled) {table-cell}
{table-cell}1920 {table-cell} {table-cell}4800 {table-cell} {table-row} {table-row} {table-cell}InRow RD (600 mm Air Cooled) {table-cell}
{table-cell}2000 {table-cell} {table-cell}5000 {table-cell} {table-row} {table-row} {table-cell}InRow RD (300 mm Air Cooled) {table-cell}
{table-cell}916 {table-cell} {table-cell}2300 {table-cell} {table-row} {table-row} {table-cell}InRow RD (300 mm Fluid Cooled) {table-cell} {table-cell}
916 {table-cell} {table-cell}2300 {table-cell} {table-row}{table} * Rack airflow is by default assumed to be 160 CFM/kW based on the total rack
power. This value can be changed by right-clicking a rack and selecting *Properties*, to change to, for example, 105 CFM/kW for blade server
racks. * CRAC airflow is, by default, assumed to be 6000 CFM. This can be changed by right-clicking a CRAC and selecting *Properties*. * UPS
airflow is automatically calculated by the system based on the UPS size and the number of power modules (assumed to be 10kW each). * Airflow
through each tile is calculated as the tiles are positioned in the layout. * Airflow for generic powered equipment is not included in the cooling
calculations by default. This can be changed by right-clicking a piece of generic powered equipment and selecting *Properties*. ||See also||
[Configuring cooling] [Performing cooling simulation in the Cooling view] [About Capture Index prediction models] [About the Capture Index (CI)
colors]

Optimizing the cooling configuration accuracy by adjusting power and cooling estimates
Since {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} uses estimates to calculate the temperatures in the 3D view, you
cannot expect the simulation to be completely accurate. However, you can improve the accuracy of these estimates to fit your particular setup by
providing the system with as much information about the power and cooling in your data center as possible. h2. Server load estimates In
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, every server in the data center has two power estimates. Per default, the
two values are the same. They define the maximum power consumption for a particular server in its maximum configuration. * Manufacturer's
Nameplate: Identifies the nameplate value of the selected server. {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} uses this
value as the reference value. * Estimated Load: Identifies the estimated load of the selected server.
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} uses this value for the calculations. You can lower the Estimated Load for
all servers in the data center if they do not consume all the power specified by the nameplate value. The option is available if you right-click the
server and select *Properties>Power*. h2. Cooling unit airflow estimates The accuracy of the cooling unit airflow is about 85-90% in typical
configurations. However, you can adjust the airflow properties for the cooling units if the default values in the system do not match your specific
setup. The option is available if you right-click the cooling unit and select *Properties>Cooling*. In this way, you can provide the system with the
specific power and cooling values for your data center and improve the accuracy of the configuration. ||See also|| [Cooling configuration accuracy
and design guidelines] [Configuring cooling]

Understanding real-time temperature predictions

The approach to predicting data center cooling performance in real time pioneered by Schneider Electric is to focus on airflow patterns rather than
temperature predictions. Airflow patterns, after all, are the root cause of cooling success or failure whereas temperatures are merely a symptom. It
is possible to have acceptable temperatures while the management of cooling airflow is out of control and inefficient. Additionally, while airflow
patterns are dominated by characteristics of nearby racks and coolers, temperatures "float" up or down with the surrounding ambient temperature.
Consequently, it is easier to develop real-time cooling-prediction algorithms which predict airflow pattern characteristics rather than predicting
temperatures directly. The primary metric developed for airflow-pattern prediction is the Capture Index (CI) which is defined as either the fraction
of a rack's airflow which comes directly from local cooling sources (Cold Aisle CI) or the fraction of the rack's airflow which is captured by local
sources (Hot Aisle CI). Once airflow patterns are known, however, it is possible to estimate all of the temperatures of primary interest (rack and
cooler inlet and outlet temperatures and a room ambient temperature). ||See also|| [Configuring cooling]

Tips & Tricks - Cooling Configuration

Here is a collection of tips and tricks for configuring cooling in the application. If you have any tips of your own that could be useful to others, feel
free to share them by adding a comment to the bottom of the page. h2. Adjusting estimated power load and cooling airflow You can improve the
accuracy of the cooling estimates to fit your particular setup by providing the system with as much information about the power and cooling in your
data center as possible. [More...|Optimizing the cooling configuration accuracy by adjusting power and cooling estimates] h2. Loading multiple
rooms You can load multiple rooms in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} but you can only have one room
loaded at a time in the 3D view. If your data center setup includes multiple rooms, close one room's tab before opening the next one in the 3D
view. h2. Viewing CI values in the Cooling view If you do not see CI values as expected for some equipment in the *Cooling* view, see
[Troubleshooting why Capture Index values do not display]. h2. Customizing colors and temperature thresholds In the 3D view, you can click the
icon at the bottom of the thermometer to customize the temperature range. You can adjust the thresholds for maximum and minimum temperature
and customize the colors of the temperature scale. If the thermometer does not show, click the arrow icon to invoke it. To customize the graphical
representation of the velocity arrows, use the settings in *Tools>Preferences*. These settings define how the arrows will indicate the velocity in
the Floor Layout *Plenum* view and in the 3D *Velocity plane*. The different velocities will be represented as arrows of a certain length or color.
h2. Getting a notification if there is an issue with the design You can enable a notification to alert you if there is a design issue that prevents the
system from rendering the 3D view of the temperature map. h2. Dragging InRow OA cooling units into the layout If you cannot drag an InRow OA
cooling unit into the layout, you may be trying to drag it into an unsupported position. InRow OA cooling units are positioned over a hot aisle
between two rows of racks to move the source of cooling close to the heat load in a thermal containment system. Drag a Hot Aisle Containment
system into the layout before dragging an InRow OA cooling unit between the rows. ||See also|| [Configuring cooling]

Row-based or room-based cooling

{section}{column:width=50%}h2. Row-based cooling Cooling is distributed through InRow cooling units placed in the rows close to the heat
generating equipment in an equipment cluster. {column} {column:width=50%}!coolinrowex.png! {column} {section}
{section}{column:width=50%}h2. Room-based cooling Cooling airflow is distributed through perforated tiles in a raised floor environment. Cooling
calculations include airflow distributed via perforated tiles for equipment in clusters spanning cold aisles with perforated tiles positioned in the cold
aisle. {column} {column:width=50%}!coolinroomex.png! {column} {section} ||See also|| [Configuring cooling]

Cooling Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component, identifies cooling attributes associated

with the component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Airflow* {table-cell} {table-cell:}Identifies the maximum cooler
airflow in cubic feet per minute (CFM). {table-cell} {table-row} {table-row} {table-cell:} *Discharge Pattern* {table-cell} {table-cell:}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Identifies the room air distribution system. * Downflow: Warm exhaust air is drawn
in through the top of the unit, cooled, and then cool air is distributed back into the room through a raised floor plenum. These systems are ideal for
areas with raised floors greater than 305 mm (12 in) high. * Upflow: Warm exhaust air is drawn in through the front of the unit. The warm exhaust
air is then cooled and discharged back into the room through a plenum or ductwork. These systems are ideal for areas without a raised floor, but
can also be used in a raised floor environment. {panel} {table-cell} {table-row} {table-row} {table-cell:} *Include in cooling calculation* {table-cell}
{table-cell:}Defines if the airflow from this equipment is to be included in the cooling calculations. You can set this for generic powered equipment.
{table-cell} {table-row}{table} ||See also|| [Editing Properties]

Working with the Equipment Browser

{section}{column:width=50%}The table displayed in the *Equipment Browser* pane shows equipment in the system according to your
preferences. What equipment is displayed depends on the [layout configuration|Configuring Equipment Browser Layout] and [filter setup|Filtering
Equipment Browser (Search)]. When working with future changes, items marked with pending changes appear in light gray in the Equipment
Browser available in the Application bar *> Planning* *> IT Change* when
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} installed) is installed. {column}{column:width=50%}
!eqbrowser.png|thumbnail! {column}{section} || 123 Steps to... || See also || | *Showing selected equipment in Equipment Browser* \\ \\
{excerpt:hidden=false}You can use the link functionality to filter the content of the Equipment Browser and only display selected
equipment.{excerpt} # Click the *Link view with selected equipment* icon to enable this feature !icon_linkviews.png!.\\ # Select equipment in
*Layout* or *Navigation* pane that you want to see in the Equipment Browser. # Click the *Link view with selected equipment* icon again to
disable this feature !icon_linkedviews.png!.\\ When this feature is enabled, the Equipment Browser will be filtered to only show the equipment and
what is contained in this equipment, e.g. a rack and all contents in the rack. If you select a piece of rack-mounted equipment in the layout, the
*Equipment Browser* will show that piece of equipment and any other equipment in the rack. | [Filtering Equipment Browser (Search)] [Exporting
Equipment Browser Table] [Editing multiple items in the Equipment Browser] [Configuring Equipment Browser Layout] [Working with the List View]

Editing multiple items in the Equipment Browser

{excerpt:hidden=false}You can edit multiple items at the same time in the Equipment Browser by using the Edit Multiple Items dialog box.{excerpt}
# In Equipment Browser select the items you want to edit # Click the *Edit Multiple Items* icon or right-click and select the context menu item
!icon_eqbrowser_multiedit.png!\\ # In the Edit Multiple Items dialog box, select a column to edit, and identify the new value to apply to the
selection. {tip:icon=false}*Note*: If your selection includes items in rooms that are not open, these items will not be edited. To include these items
in your selection, right-click the items in the Equipment Browser and select *Open room*.{tip} If you want to ignore the selection of items in step 1,
and edit all equipment shown in the Equipment Browser, select the *Edit all items shown*. ||See also|| [Working with the Equipment Browser]
[Showing selected equipment in Equipment Browser|Working with the Equipment Browser] [Filtering Equipment Browser (Search)] [Exporting
Equipment Browser Table] [Configuring Equipment Browser Layout]

Filtering Equipment Browser (Search)

{excerpt:hidden=false}You can set a filter on the Equipment Browser to show only the equipment that you want to see.{excerpt} # In the
drop-down list, select a column to only search for equipment in this column or keep the default value *All columns*. # In the *Search* box, type the
search criteria for the equipment you want to see and click *Search*. ||See also|| [Working with the Equipment Browser] [Editing multiple items in
the Equipment Browser] [Showing selected equipment in Equipment Browser|Working with the Equipment Browser] [Exporting Equipment
Browser Table] [Configuring Equipment Browser Layout]

Exporting Equipment Browser Table

{excerpt:hidden=false}You can export the list of equipment to a file.{excerpt} # Click the export icon to open the Export dialog box
!exporttable.png!. # Select file format and browse to identify the destination where you want the file sent, and click *OK* to execute the export and
exit the dialog. ## If you want to export more equipment data than is currently shown in the list, select to include filtered out equipment and/or
hidden columns. ||See also|| [Working with the Equipment Browser] [Editing multiple items in the Equipment Browser] [Showing selected
equipment in Equipment Browser|Working with the Equipment Browser] [Filtering Equipment Browser (Search)] [Configuring Equipment Browser
Layout]

Configuring Equipment Browser Layout

{excerpt:hidden=false}You can configure the layout of the Equipment Browser to show equipment according to your preferences.{excerpt} * Select
which columns to show from the dialog box opened by clicking *Configure columns* !icon_eqbrowser_showcolumns.png!\\ * Edit the column
width: *# Drag the boundary of a column header to the required position *# Double-click the boundary of a column header to make the column
width fit to contents * Drag and drop columns in the browser to move columns * Click a column header in the browser to sort on this column \\ An
arrow on the header indicates the sort order (ascending/descending) * Click column header in the browser to toggle sort order
(ascending/descending) ||See also|| [Working with the Equipment Browser] [Editing multiple items in the Equipment Browser] [Showing selected
equipment in Equipment Browser|Working with the Equipment Browser] [Filtering Equipment Browser (Search)] [Exporting Equipment Browser
Table]

Editing IP address through the Equipment Browser

You can edit IP address for multiple servers directly through the Equipment Browser. # Add the *IP Address* column to the *Equipment Browser*:
Click the *Configure columns* icon !configurecolumns.jpg!, and select *IP Address*. # Type the IP address in the *Equipment Browser* in the line
with the first server, and then continue to add the information to remaining servers with IP address. Alternatively, right-click each server and open
*Properties>Network* and add the information here. ||See also|| [Working with the Equipment Browser] [Configuring Equipment Browser Layout]

Working with the Equipment Placement Advisor

{section}{column:width=50%}{excerpt:hidden=false}The system recommends the best location for a server in the rack layout, using available
space, cooling, and power capacity to optimize capacity utilization and avoid stranded capacity. {excerpt} In the *Rack Layout*, the *Rack-Mount
Equipment Placement* pane is used with the *Equipment Placement Advisor* and *Power Details* views (available as tabs at the bottom of the

layout pane) to highlight the best position in the rack layout for a selected piece of equipment you want to add from the *Catalog* or move from
*Navigation* or *Layout*. To effectively identify the best location for the selected equipment using this feature, ensure the system is set up
correctly, including the appropriate rack PDUs, UPS and PDUs, power paths, and capacity groups. When you use the *Add Equipment* to *Best
rack* option, the system recommends the best position based on your setup: available space, cooling and power. This could be information about
supported voltage, redundancy, capacity group and tag associations, remaining power outlets, load balancing on the different phases, weight and
available network ports. In addition, color-coded messages in the *Placement Status* pane guide you in finding the optimum location for the
selected equipment.{column}{column:width=50%}!Enabling placement recommendations^placementadvisor.jpg|thumbnail!{column}{section} ||See
also|| [Enabling placement recommendations] [Finding the best location for a new server] [Setting up a capacity plan] [Capacity Planning Example] [Best Rack Advisor - Redundancy configuration]

Rack-Mount Equipment Placement Pane

{excerpt:hidden=false}The *Rack-Mount Equipment Placement* pane is used for guided addition/repositioning of equipment to the layout. It is
available in Rack Layout when *> Planning* *> Data Center* is selected in the Application bar. If you have
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} installed, it will also be available when *> Planning* *> IT Change* is
selected in the Application bar.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell} *New / Existing Equipment info* {table-cell}
{table-cell}Provides information about that component, e.g. how much power the equipment draws, how many power cords the equipment has,
how much space the equipment takes up in a rack. {table-cell} {table-row} {table-row} {table-cell} *Assign tags* {table-cell} {table-cell}Lists
available tags to select and assign to the equipment and rack in the new position in the layout. {table-cell} {table-row} {table-row} {table-cell}
*Required Redundancy* {table-cell} {table-cell}Selects the level of redundancy for this piece of equipment in the new position in the layout.
{table-cell} {table-row} {table-row} {table-cell} *Required network ports* {table-cell} {table-cell}Selects the amount of fiber or copper connections for
this piece of equipment in the new position in the layout. {table-cell} {table-row} {table-row} {table-cell} *Add / Move Equipment* {table-cell}
{table-cell}Adds one or more components to a *Selected racks*, *Each rack in the server room*, or *Best rack*. When you select *Best rack*,
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} uses information about space, cooling, and power requirements of the
equipment being added, to effectively determine the best placement for that equipment (available if you have
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} installed).{table-cell} {table-row} {table-row} {table-cell} *Show location*
{table-cell} {table-cell}Highlights the best location for the selected equipment in the layout. {table-cell} {table-row}{table} ||See also|| [Finding the
best location for a new server] [Enabling placement recommendations] [Working with the Equipment Placement Advisor]

Managing network configurations

{section}{column:width=50%}{excerpt:hidden=false}The *Network Management* pane lists the configured network connections and allows you to
set up new network routes between the configured equipment.{excerpt} The table view will be populated with network route data when you select
a piece of equipment with configured network in the layout or *Navigation*. The table shows a row per port configuration. The table will be empty if
the equipment has no network route configured or if the selection is not a piece of network equipment. You can type free text in the *Description*
column for start item and end item, e.g. if a specific port is not working. The *Route* column will be empty until you create routes for the selected
piece of equipment. To enable route editing, select a row in the table and double-click the *Route* field. Click the *Edit route* field and select from
the available options. You can right-click a row in the table and select *Show in Layout* or *Show in Navigation* to highlight the end item in the
rack layout or *Navigation*. You can add IP information to the equipment properties and use the *Equipment Browser* to filter and locate
equipment with specific addresses assigned. You can also set the tool tip preferences to show the IP address when you hover over a piece of
equipment in the rack layout. The system has built-in content assistance to guide you when setting up network routes. {column}
{column:width=50%} !network.png|thumbnail! {column} {section} || 123 Steps to... || See also || | *Configuring network routes* \\ \\
{excerpt:hidden=false}You can configure network routes in the *Network Management* pane for selected network equipment in the layout, for
example between a server and a switch or a switch and a switch.{excerpt} A route is defined as a connection from a piece of equipment
(communication endpoint, such as a server or layer 2/3 network gear, such as a switch) to the first piece of equipment that is a communication
endpoint or layer 2/3 network gear. The system has built-in content assistance to guide you when setting up network routes. # Select a piece of
equipment with network configured in the layout, e.g. a server in the rack layout. # In the *Network Management* pane, click the row with the port
that you want to configure in the list. # Place the cursor in the *Route* column and from the list, select a symbol, and press Enter. # From the list,
select the equipment that you want to connect to, and press Enter. Remember to enter the port number. # Click the next item in the list and repeat
steps 2 to 4 for all remaining items. You can configure as many routes as there are ports available. In the patch panel properties, you can
configure patch panel back connections. \\ \\ {tip:icon=false}*Recommendation*: Configure the patch panel back connections prior to configuring
the rest of the network route.{tip} | [Configuring network ports] \\ [Network Configuration Example] \\ [Route Notation in Network Management] \\ |

Configuring network ports

{excerpt:hidden=false}You can configure network port properties for network equipment in the catalog. {excerpt} # Open the *Catalog* pane. #
Select a piece of network equipment. # Click on the *Network* pane in the *Properties* section and perform the edits for the component in the
catalog. ## Click *Add* or *Edit*. ## Select the type, port range (first port and the amount of ports in the range), and the network speed if relevant.
## Repeat the above two steps for all port ranges needed. For example, a switch could be configured like this {table:border=1|frame=box|}
{table-row:align=center} {table-cell:}*Type* {table-cell} {table-cell:}*Start (First port in range)* {table-cell} {table-cell:}*Count (Amount of ports)*
{table-cell} {table-row} {table-row} {table-cell:}RJ45 {table-cell} {table-cell:}1 {table-cell} {table-cell:}16 {table-cell} {table-row} {table-row}
{table-cell:}RJ45 {table-cell} {table-cell:}17 {table-cell} {table-cell:}16 {table-cell} {table-row} {table-row} {table-cell:}RJ45 {table-cell} {table-cell:}33
{table-cell} {table-cell:}16 {table-cell} {table-row} {table-row} {table-cell:}Fiber Uplink {table-cell} {table-cell:}1 {table-cell} {table-cell:}4 {table-cell}
{table-row}{table} The configured properties will apply to all pieces of this equipment added to the layout subsequently. {tip:icon=false}*Tip*: To
change the properties for one specific component only rather than the product type in the catalog, right-click the component in the layout. The
same options are available but they will only apply to the one component.{tip} ||See also|| [Managing network configurations]

Network Configuration Example

Error: The XML content could not be parsed. There is a problem at line 6, column 13. Parser message: Unexpected character '-' (code 45) in
content after '<' (malformed start element?). at [row,col {unknown-source}]: [6,13]

Route Notation in Network Management

{excerpt:hidden=false}The system has built-in content assistance to guide you when setting up network routes.{excerpt} Based on the data in the
system, you are presented with only relevant options. The data entered into the network properties is used so that you will see only relevant

options to ensure that the network is connected logically.{table:border=1|frame=box|} {table-row:align=center} {table-cell:}*Notation* {table-cell}
{table-cell:colspan=2|}*Description* {table-cell} {table-row} {table-row} {table-cell:} > {table-cell} {table-cell:colspan=2|}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF} * Network gear in this rack{panel} {table-cell} {table-row} {table-row} {table-cell:} -> {table-cell}
{table-cell:colspan=2|}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} * Racks in this room and/or all rooms {panel}
{table-cell} {table-row} {table-row} {table-cell:} : {table-cell} {table-cell:colspan=2|}{panel: borderStyle=none| borderColor=#FFFFFF|
bgColor=#FFFFFF} * Port specification{panel} {table-cell} {table-row} {table-row} {table-cell:} / {table-cell} {table-cell:colspan=2|}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} * Location separator (room/row/rack){panel} {table-cell} {table-row}{table} ||See
also|| [Configuring network routes|Managing network configurations]

Network Properties
{excerpt:hidden=false}This section of the *Properties* dialog box, accessed by right-clicking a piece of network equipment, identifies network
attributes associated with it. The information may vary based on the type of equipment.{excerpt}{table:border=1|frame=box|} {table-row}
{table-cell:colspan=3|} *Network ports* {table-cell} {table-row} {table-row} {table-cell:} *Type* {table-cell} {table-cell:colspan=2|}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Provides information about the type of network port. The available options include
pairs of a regular port and an uplink port. * The regular port is selected for the piece of equipment that makes network available to other pieces of
equipment, such as a switch. * The uplink port is selected for the piece of equipment that requires network access. {panel} {table-cell} {table-row}
{table-row} {table-cell:} *Description* {table-cell} {table-cell:colspan=2|}Provides user-defined information. {table-cell} {table-row} {table-row}
{table-cell:} *Start* {table-cell} {table-cell:colspan=2|}Identifies the first port in the port range. {table-cell} {table-row} {table-row} {table-cell:} *Count*
{table-cell} {table-cell:colspan=2|}Identifies the amount of ports in the port range. {table-cell} {table-row} {table-row} {table-cell:} *Speed*
{table-cell} {table-cell:colspan=2|}Provides information about the network speed. {table-cell} {table-row} {table-row} {table-cell:colspan=3|}
*Connections* (available if the dialog box is accessed by right-clicking a component in the rack layout that has routes defined) {table-cell}
{table-row} {table-row} {table-cell:} *Port* {table-cell} {table-cell:colspan=2|}Identifies the port number. {table-cell} {table-row} {table-row}
{table-cell:} *Type* {table-cell} {table-cell:colspan=2|}Identifies the port type. {table-cell} {table-row} {table-row} {table-cell:} *Connected to*
{table-cell} {table-cell:colspan=2|}Identifies the network route between the start and end items. {table-cell} {table-row} {table-row} {table-cell:}
*Description* {table-cell} {table-cell:colspan=2|}Provides user-defined information. {table-cell} {table-row} {table-row} {table-cell:} *IP Address*
{table-cell} {table-cell:colspan=2|}Identifies the IP Address. {table-cell} {table-row} {table} ||See also|| [Editing Properties] [Managing network
configurations]

Network Summary report

{section}{column:width=50%}{excerpt:hidden=false}You can generate a *Network Summary* report with an overview of network connections per
rack in the selected rooms. The report lists layer 2/3 network gear (such as switches) and layer 1 network gear (patch panels) as well as a
summary per rack of mapped and unmapped routes equipment that is connected to a network (such as a server or PDU).{excerpt} The *Tag* filter
options are available if you have {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true}. The generated report displays in the
*Report View*. You can now use the *Report View* toolbar to navigate the report pages on the screen (arrow icons), or to print or export the
report to a file in any of the available formats (Export icon, down arrow for selection of format). {column}{column:width=50%}
!report_networksummary.png|thumbnail! {column}{section} ||See also|| [Working with reports] [Managing network configurations]

Viewing external system data

{excerpt:hidden=false}Once integration has been set up in *System Setup>External System Configuration* and the systems start communicating,
the data from the other systems will appear in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.{excerpt}
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} integrates with monitoring and virtualization systems: h2. Viewing
monitoring system data Integration with monitoring systems, such as {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}
servers allows for associating devices (UPS or rack PDUs) to physical locations in the layout and for retrieving actual measured data and alarm
data. The devices will appear in device groups according to the setup in the external system, including any sub devices, for example monitoring
equipment with multiple pods and cameras. A monitored device appears as unassigned in the pane (gray icon) until it has been associated with
the device representing it in the layout (blue icon), for example a UPS or rack PDU, (or if you selected to unassociate it again after that). h2.
Viewing virtualization management system data Integration with virtualization management systems, such as VMware vCenter Server or Microsoft
System Center Operations Manager and Microsoft Virtual Machine Manager allows for associating virtual machine hosts to physical locations in
the layout and managing and migrating virtual machines running on devices connected to failing physical equipment to healthy hosts in order to
prevent impact. The virtual machine hosts will appear according to the setup in the external system. A host will appear as unassigned in the pane
(gray icon) until it has been associated with the server representing it in the layout (blue icon). Any alarm on a device will show up to help you
locate the problem in the physical infrastructure and determine the nature of the problem. Alarm icons will appear in the *Status Bar* and
equipment with an alarm will be marked in the layout and in the *External Systems* pane. h2. Performing dynamic search * In the dynamic
*Search* box above the *External Systems* pane, start typing some characters of the devices you want to see. As you type, the pane shows all
items that contain the typed characters. h2. Locating an associated device in the layout * Right-click the device in the *External Systems* pane
and select *Show in Editor* to locate and select the device in its physical location in the floor or rack layout. * Right-click the device in the
*External Systems* pane and select *Show in Navigation* to locate and select the device in the *Navigation* pane. h2. Launching to a device *
Right-click the device in the *External Systems* pane and select *Launch to Device* for direct access to launch the device in the external system.
h2. Viewing properties * Right-click the monitored device or virtual machine host in the *External Systems* pane and select *Properties* to access
read-only information provided by the external system. The information may vary based on the type of equipment. ||See also|| [Configuring
external system integration] [Launching to device] [Viewing alarms from external systems] [The importance of system time synchronization for
accurate power values]

About peak and average power data retrieval from StruxureWare Central
Devices (for example Rack PDUs) in {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} must provide measured values
through power sensors in Watt. In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, all power measurements are assumed to
be in Watt. {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} includes measured power values from any device, supporting
real power measurements in Watt, regardless of make and model (including 3rd party devices). The power sensor value is assumed to be real
power (as apposed to apparent power VA), but the actual value is defined by the individual device and how
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} retrieves the value (could be done as a calculation in the DDF).\\
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} retrieves the peak power values from

{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} at the specified *Power information retrieval interval* (in *System

Setup>External systems*. The default value is 300 seconds) and average values once each day. The average power values are collected for the
specified time period (*Power data collected over period of days*, also in *System Setup>External systems*. The default value is 30 days). The
peak power value is the highest value {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} receives from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} in the specified time period. The retrieval of data between
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} and the device (rack PDU) is configured in
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}. ||See also|| [Viewing external system data]

Associating live data from an external system to the layout

{excerpt:hidden=false}When monitored devices from an external system, e.g.
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}, are associated with the corresponding devices representing them in the
application, the device data supports the capacity planning process. {excerpt} # To associate any of the devices with the component that
represents it in the layout, drag-and-drop the devices from the *External Systems* pane into position over the corresponding devices in the
*Navigation* pane or *Layout* pane. # To ensure downloaded values for the monitored devices from the external systems are reliable and based
on the correct data, verify the integration configuration in *System Setup>External System Configuration*. For example, make sure you have set
the correct date range for collecting measured data. Live data is shown for associated monitored devices, optimizing the planning when identifying
how much of each device maximum kW power is in use. # To remove the association between a device and the item representing it in the data
center layout, right-click the device or object and select *Unassociate from equipment*. ||See also|| [Viewing external system data] [Launching to
device] [Configuring external system integration]

Launching to device
{excerpt:hidden=false}You can access the device web interface directly from the *Launch to Device* right-click option.{excerpt} # Right-click a
device, in the *External Systems* pane, for example, and select *Launch to Device*. An error will occur if the HTTP/HTTPS protocol or port
definitions defined for this device at the external system server do not match the protocol and port definitions required by that device. # If an error
occurs, refer to the external system's documentation for instructions on how to check or set the HTTP/HTTPS settings. ||See also|| [Viewing
external system data] [Configuring external system integration]

How removing a server affects power values

{excerpt:hidden=false}If the system has been set up to collect live data from an external system, peak power values that occur in a configurable
time period (10, 20 or 30 days) are used for power calculations. This data is more accurate than if the system only has estimated values.
However, when removing a server from a rack, the power peak values from that server are still included in the measured data for the rack the next
30* days. {excerpt} To avoid this, the time period for measuring the data from the rack PDUs in the rack has been automatically reduced:
{table:border=1|frame=box|} {table-row:align=center} {table-cell}*When was the server removed from the rack?* {table-cell}
{table-cell:colspan=2|}*Measured data collected in time period:* {table-cell} {table-row} {table-row} {table-cell}Time {table-cell} {table-cell}From
{table-cell} {table-cell}To {table-cell} {table-row} {table-row} {table-cell}Less than 24 hours ago {table-cell} {table-cell}Present time - 24 hours
{table-cell} {table-cell}Present time {table-cell} {table-row} {table-row} {table-cell}Less than 30* days but more than 24 hours ago {table-cell}
{table-cell}Deletion time {table-cell} {table-cell}Present time {table-cell} {table-row} {table-row} {table-cell}More than 30* days ago {table-cell}
{table-cell}Present time - 30* days {table-cell} {table-cell}Present time {table-cell} {table-row}{table} *30 days is the default value set in the external
system configuration settings; this value can also be 10, or 20 days. {tip:icon=false}*Note*: The power peak measurements might still contain data
from the deleted server up to one day after a server has been removed; recommendations and capacity calculations for that rack can be less
accurate. It can take several days for the capacity calculations to stabilize because of changes in the server load over the following days.{tip}
||See also|| [Viewing external system data] [Configuring external system integration]

The importance of system time synchronization for accurate power values

When you have configured system integration correctly, {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} retrieves accurate
and up-to-date power measurements from {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}. The
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}
servers can be physically positioned in different time zones. The system integration handles the time difference. However, both servers must be
configured to synchronize time with the same NTP server: || Server || Time Synchronization Settings ||
|{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}|In the server's Webmin interface, *System>System Time*, *Time server
sync* tab| |{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}|In *System>Server Administration Settings*, *Time Settings*
option| Otherwise, the retrieved power measurements may be out of sync: || Server Time || Consequence ||
|{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} ahead of
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}|No measured peak data retrieved|
|{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} behind
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}|Incorrect measured peak data retrieved (out of sync)| For further
instructions on how to configure system time synchronization for the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server,
see [here|Configuring system time synchronization (NTP)]. For further instructions on how to configure system time synchronization for the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server, see the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} help documentation. || See also || [Configuring system time synchronization
(NTP)|Configuring system time synchronization (NTP)]

Viewing alarms from external systems

{section}{column:width=50%}When the system is configured to support [integration with external systems|Configuring external system integration],
alarms from devices in external systems associated with modeled components are highlighted in the layout. You can easily locate failing
equipment and servers that might be impacted by the failure. An icon in the *Status bar* with a pop-up notification informs you of active alarms on
devices monitored by an external system. Clicking the icon will open the *Alarms* pane with a list of all alarms from external systems. An alarm
icon also appears next to the device with the alarm in the *External Systems* pane. Alarms may occur with different severities: information,
warning, error, critical and failure. Clicking an alarm in the *Alarms* pane list opens the alarm details for the selected alarm, including
recommended actions for resolving the issue. Right-clicking an alarm in the *Alarms* pane and selecting *Show in Navigation* or *Show in Editor*
identifies and highlights the component with the alarm in the *Floor Layout*, *Rack Layout*, or *Navigation*. Alarm icons in the system help you

identify the exact location of the alarms in the data center model, for example on a specific UPS in the floor layout, and help you identify the
severity of the alarm. Alarm types ||Info||Warning||Error, Critical, and Failure|| | !ImgAlarmInfo.png! | !ImgAlarmWarning.png! |
!ImgAlarmCritical.png! | If enabled in *Tools>Preferences*, the tool tips include information about active alarms in *Rack Layout* (on
rack-mountable equipment) and *Floor Layout* (on equipment in the floor, e.g. UPS). You can view the device with the alarm on the external
system by right-clicking and selecting *Launch to Device*. {column} {column:width=50%} !externalsystem_alarms.png|thumbnail! {column}
{section} ||See also|| [Associating live data from an external system to the layout] [Showing alarms for selected equipment only] [Configuring
external system integration]

Locating alarms on failing equipment in the layout

{excerpt:hidden=false}When configured, the system shows alarms from external system devices associated with modeled components in the
layout, e.g. a UPS or rack PDU. {excerpt} In *Operations* (accessed in the Application bar *Data Center Operations*): 1. View alarms in the layout
by selecting for example the *Rack Layout* or *Floor Layout* icon, and clicking the *Alarms* tab to see any associated devices in alarm state
highlighted on the modeled components in the layout. * Yellow: Warning * Red: Error, Critical, and Failure If more alarms occur on a piece of
equipment, the component is highlighted according to the alarm with the highest priority; and if there is an alarm on a rack PDU, the rack is
highlighted. 2. Right-click the alarm in the *Alarms* pane, and select *Show in Navigation* or *Show in Editor* to identify and highlight the
component with the alarm in the *Floor Layout*, *Rack Layout*, or *Navigation*. ||See also|| [Viewing alarms from external systems]

Showing alarms for selected equipment only

{excerpt:hidden=false}You can filter the contents of the *Alarms* pane to display only alarms related to the selection (locations, rooms, equipment,
or devices) in the layout (floor, rack, or list) or *Navigation* pane.{excerpt} # Click the *Link view with selected equipment* icon to enable this
feature. !icon_linkviews.png!\\ # Select equipment in the *Layout* or *Navigation* pane that you want to see in the *Alarms* pane. # Click the link
icon again to disable this feature. !icon_linkedviews.png!\\ ||See also|| [Viewing alarms from external systems] [Locating alarms on failing
equipment in the layout]

Optimizing the design by following the recommendations

{section}{column:width=50%}{excerpt:hidden=false}Recommendations are displayed in the *Recommendation* pane to guide you as you design
the data center model.{excerpt} It is not a goal in itself to clear all messages. It is, however, a goal to review your modeled design to make it
reflect the real-world physical data center infrastructure as accurately as possible. h2. Message types and severities * Some messages are
related to the model alone. For example, a message will appear if a connection has not been configured in the model between a PDU and its
power supply. * Some messages are related to the model and the real-world physical data with which the model is associated. For example, a
message will appear if the measured load of a real-world physical device exceeds the estimated load for the object it was designed to represent in
the model. * Message types: *Power* !power_recommendation.png!\\ *Cooling* !cooling_recommendation.png!\\ *General*
!general_recommendation.png!\\ *License* !license_recommendation.png!\\ * Some messages are more severe than others. For example,
potential issues with the power design are assumed to be more severe than general issues. If there is both a power message and a general
message for as piece of equipment, the power message is displayed in the layout. h2. Highlight and filter messages * Highlight: To identify and
highlight the component related to the selected message, right-click the message and select *Show in Navigation* or *Show in Editor*. * Filter: To
define which messages to show in the pane, toggle the filter. If the filter is disabled, all messages related to the entire solution are listed. If the
filter is enabled, only messages related to the selected room or item are listed. {column}{column:width=50%} !recommendation.png|thumbnail!
{column}{section} ||See also|| [General Recommendations] [License Recommendations] [Power Recommendations] [Cooling Recommendations]
[Showing recommendations for selected equipment only]

Showing recommendations for selected equipment only

{excerpt:hidden=false}How to filter the content of the *Recommendation* pane and display only the recommendations related to selected room or
equipment.{excerpt} # Click the *Link view with selected equipment* icon to enable this feature. !icon_linkviews.png!\\ # Select equipment in
*Layout* or *Navigation* pane that you want to see in the *Recommendation* pane. # Click the link icon again to disable this feature.
!icon_linkedviews.png!\\ ||See also|| [Optimizing the design by following the recommendations]

Cooling Recommendations
{excerpt:hidden=false}Messages about the cooling configuration may occur in the *Recommendation* pane to guide you as you design the data
center model. Refer to the topics about the individual messages for information about how to optimize the design.{excerpt} ||See also|| [Optimizing
the design by following the recommendations] {contentbylabel:label=recommendation_cooling|space=@self|showSpace=false|showLabels=false}

Maximum perforated tile airflow is exceeded.

{set-metadata:UImapping}averagePerforatedTileAirflowTooHighConstraint{set-metadata} h2. Description {excerpt:hidden=false}The maximum
airflow per perforated tile is exceeded. {excerpt} h2. Recommended Action Drag one or more perforated tiles into the layout until the airflow per
tile is below the recommendation of 600 CFM. ||See also|| [Optimizing the design by following the recommendations]

There is no perforated tile airflow.

{set-metadata:_UImapping_}perforatedTileRequiringExistingCracConstraint{set-metadata} h2. Description {excerpt:hidden=false}You have added
one or more perforated tiles to the room but there are no CRACs to supply any airflow.{excerpt} h2. Recommended Action Drag one or more
CRACs into the layout. ||See also|| [Optimizing the design by following the recommendations]

The room has no perforated tiles for the CRAC airflow.

{set-metadata:_UImapping_}existingCracRequiringPerforatedTileConstraint{set-metadata} h2. Description {excerpt:hidden=false}You have added
one or more CRACs to the floor but there are no perforated tiles for the airflow.{excerpt} h2. Recommended Action Drag one or more perforated
tiles into the layout. ||See also|| [Optimizing the design by following the recommendations]

General Recommendations
{excerpt:hidden=false}Messages about the general configuration may occur in the *Recommendation* pane to guide you as you design the data
center model. Refer to the topics about the individual messages for information about how to optimize the design.{excerpt} ||See also|| [Optimizing
the design by following the recommendations] {contentbylabel:label=recommendation_general|space=@self|showSpace=false|showLabels=false}

Equipment weight exceeds the weight limit of the floor

{set-metadata:_UImapping_}FloorCarryingWeightExceededConstraint{set-metadata} h2. Description {excerpt:hidden=false}The equipment is too
heavy to be supported by the physical carrying properties of the floor layout.{excerpt} h2. Recommended Action # Select the *Floor Loading* tab
at the bottom of the layout pane for a color-coded display of the equipment weight compared to the carrying capabilities of the floor measured in
kg per m or lb per sq.ft. # Remove equipment or adjust the weight settings. #* Move or remove equipment until the equipment no longer weighs
more than is supported by the floor carrying capabilities. #* Review and adjust floor or equipment weight settings if these are incorrect. #** To
adjust the carrying capability of the floor layout: #**# Right-click the floor layout and select *Properties*. #**# Redefine the *Floor Carrying
Capacity* in the *Floor* page to match your physical environment. #** To adjust the equipment weight: #**# Right-click the piece of equipment in
the floor layout and select *Properties*. #**# Redefine the weight of the rack or equipment in the rack by lowering the *Weight* or *Maximum
Weight* in the *Physical* page. If you do not want to use weight information in your data center model, leave the weight options empty. ||See
also|| [Optimizing the design by following the recommendations]

Max load weight of rack has been exceeded

{set-metadata:_UImapping_}MaxLoadWeightInRackExceededConstraint{set-metadata} h2. Description {excerpt:hidden=false}The devices in this
rack are too heavy to be supported by the rack.{excerpt} h2. Recommended Action # Select the *Equipment Loading* tab at the bottom of the
layout pane to view color-coded bars below the racks in the rack layout showing how much weight can be added to the rack and floor, or whether
you have exceeded the supported weight. # Remove equipment or adjust the weight settings. #* Remove equipment from the rack until the
equipment no longer weighs more than is supported by the rack's carrying capabilities. #* Adjust the weight settings if these are incorrect. #*#
Right-click the rack and select *Properties*. #*# In the *Physical* page, redefine the weight of the rack or equipment in the rack by increasing the
*Current weight* or *Maximum Weight*. ||See also|| [Optimizing the design by following the recommendations]

Rack contains overlapping equipment at U position

{set-metadata:_UImapping_}overlappingEquipmentConstraint{set-metadata} h2. Description {excerpt:hidden=false}More than one piece of
equipment has been positioned in the same U position at a rack.{excerpt} h2. Recommended Action Remove or move the equipment in the rack
using drag-and-drop until only one piece of equipment is located at the U position. ||See also|| [Optimizing the design by following the
recommendations]

The tags assigned to the rack equipment in the rack do not match
{set-metadata:_UImapping_}KeywordMismatchConstraint{set-metadata} h2. Description {excerpt:hidden=false}The tags assigned to the
equipment in the rack must match the tag or tags assigned to the rack.{excerpt} h2. Recommended Action * If the wrong tag was assigned to the
rack or rack-mount equipment: *# Right-click the recommendation message and select *Show in Editor* to identify the rack in the layout. *#
Right-click the rack or rack-mount equipment in the rack and select Properties to access the Properties dialog box for the equipment. *# In the
*tags* section select the tag in question and select *Remove* to remove the tag assignment to this equipment. * If the tag information is correct
but the rack-mount equipment was accidentally placed in the wrong rack with a different tag assignment: *# Right-click the recommendation
message and select *Show in Editor* to identify the rack in the layout. *# Drag and drop the misplaced equipment into the correct rack. ||See
also|| [Optimizing the design by following the recommendations]

License Recommendations
{section}{column:width=50%}{excerpt:hidden=false}Messages about the installed licenses may occur in the *Recommendation* pane to guide you
as you design the data center model. Refer to the topics about the individual messages for information about how to optimize the design.{excerpt}
{column}{column:width=50%} !Optimizing the design by following the recommendations^recommendation.png|thumbnail! {column}{section} ||See
also|| [Managing system licenses] [You are approaching the amount of racks supported by your StruxureWare for Data Centers - Operations Suite
license] [You are approaching the amount of racks supported by your StruxureWare Operations - Capacity license] [You are approaching the
amount of racks supported by your StruxureWare Operations - Change license] [You are exceeding the amount of racks supported by your
StruxureWare for Data Centers - Operations Suite license] [You are exceeding the amount of racks supported by your StruxureWare Operations Capacity license] [You are exceeding the amount of racks supported by your StruxureWare Operations - Change license] [You have reached the
amount of racks supported by your StruxureWare for Data Centers - Operations license] [You have reached the amount of racks supported by
your StruxureWare Operations - Capacity license] [You have reached the amount of racks supported by your StruxureWare Operations - Change
license]

You are approaching the amount of racks supported by your StruxureWare for Data Centers Operations Suite license
{set-metadata:_UImapping_}operationsLicenseWarningCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are
approaching the amount of equipment supported by your license. If you continue adding equipment after you have reached the limit, you will not
be able to save your data center model.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center
Software website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also||
[Optimizing the design by following the recommendations]

You are approaching the amount of racks supported by your StruxureWare Operations - Capacity
license
{set-metadata:_UImapping_}capacityLicenseWarningCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are approaching
the amount of equipment supported by your license. If you continue adding equipment after you have reached the limit, you will not be able to
save your data center model. {excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]

You are approaching the amount of racks supported by your StruxureWare Operations - Change
license
{set-metadata:_UImapping_}changeLicenseWarningCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are approaching
the amount of equipment supported by your license. If you continue adding equipment after you have reached the limit, you will not be able to

save your data center model.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]

You are exceeding the amount of racks supported by your StruxureWare for Data Centers - Operations
Suite license
{set-metadata:_UImapping_}operationsLicenseErrorCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are exceeding the
amount of equipment supported by your license. If you continue adding equipment after you have reached the limit, you will not be able to save
your data center model.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]

You are exceeding the amount of racks supported by your StruxureWare Operations - Capacity license
{set-metadata:_UImapping_}capacityLicenseErrorCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are exceeding the
amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]

You are exceeding the amount of racks supported by your StruxureWare Operations - Change license
{set-metadata:_UImapping_}changeLicenseErrorCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are exceeding the
amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]

You have reached the amount of racks supported by your StruxureWare for Data Centers - Operations
license
{set-metadata:_UImapping_}operationsLicenseLimitReachedConstraint{set-metadata} h2. Description {excerpt:hidden=false}You have reached
the amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]

You have reached the amount of racks supported by your StruxureWare Operations - Capacity license
{set-metadata:_UImapping_}capacityLicenseLimitReachedConstraint{set-metadata} h2. Description {excerpt:hidden=false}You have reached the
amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]

You have reached the amount of racks supported by your StruxureWare Operations - Change license
{set-metadata:_UImapping_}changeLicenseLimitReachedConstraint{set-metadata} h2. Description {excerpt:hidden=false}You have reached the
amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]

Power Recommendations
{excerpt:hidden=false}Messages about the power configuration may occur in the *Recommendation* pane to guide you as you design the data
center model. Refer to the topics about the individual messages for information about how to optimize the design.{excerpt} ||See also|| [Amount of
rack PDU power outlets has not been configured] [An invalid power path has been configured] [Associated device data has been lost] [Capacity
group equipment is placed in multiple rooms] [Connection has not been configured between PDU and power supply] [Connection has not been
configured between Power Panel and power supply] [Connection has not been configured between remote distribution panel (RDP) and power
supply] [Equipment connected to this PDU draws more power than is supported by the power supply breaker] [Equipment connected to this
Power Panel draws more power than is supported by the power supply breaker] [Equipment connected to this remote distribution panel (RDP)
draws more power than is supported by the power supply breaker] [Equipment in this rack receives power from multiple power supply devices]
[Equipment is connected to a rack PDU outside this rack] [Internal redundancy setup for UPS and group must match] [PDU and connected rack
PDU are placed in different rooms] [PDU output voltage has not been configured] [Power connection configuration is invalid for equipment in one
or more racks in the group] [Power feed connection for UPS and group must match] [Power Panel output voltage has not been configured]
[Rack's estimated load exceeds group's peak load settings] [Rack does not support the group's peak load settings] [Rack is not included in a
capacity group] [Rack is without rack PDU or a rack PDU is not powered] [Rack's power configuration does not support distribution redundancy]
[The average estimated load of the racks in the group exceeds the group's average load settings] [The breaker configuration does not support
rack's estimated load] [The capacity group supports a higher redundancy than this server requires] [The input voltage setting required by the
equipment is not available in current rack] [The measured load exceeds the estimated load per phase designed for the rack] [The measured load
exceeds the total estimated load configured for the rack] [The measured load of the connected rack PDU is 0, but an estimated load has been
configured for the rack] [The measured load of the UPS exceeds the total estimated load of the connected equipment] [The phase configuration
for the connected server is not supported by the rack PDU] [The Rack PDU output voltage setting does not match the output voltage of the
connected PDU or Power Panel] [The server should not be supplied from different phases on 1 UPS] [The UPS in the layout does not supply

enough power to match the configured load of connected equipment in the layout] [This equipment in store room is connected to equipment in a
room] [This server requires a higher redundancy than is available in the capacity group] [UPS internal redundancy has not been configured] [UPS
power feed has not been configured]

Amount of rack PDU power outlets has not been configured

{set-metadata:_UImapping_}availablePowerPortUnknownConstraint{set-metadata} h2. Description {excerpt:hidden=false}The amount of power
outlets has not been configured for this rack PDU.{excerpt} h2. Recommended Action # Right-click the rack PDU and select *Properties*. # In the
*Power* page, fill in the appropriate amount of *Power Outlets*. ||See also|| [Optimizing the design by following the recommendations]

An invalid power path has been configured

{set-metadata:_UImapping_}solutionHasCircularPowerPathConstraint.{set-metadata} h2. Description {excerpt:hidden=false}There is an invalid
power connection in the power path. {excerpt} h5. Circular connection The power path has power connections going in both directions between a
device supplying power and a device receiving power. For example, PDU A is supplying power to PDU B that in turn is supplying power to PDU A.
h5. 2 cable connections A component has been configured to receive power from same power source through several cables. For example, PDU
A receives power from UPS A through both breaker A and breaker B. h5. 2 power sources A component has been configured to receive power
from several power sources. For example, PDU A receives power from both UPS A and UPS B. h5. Power source connected to 2 PDUs A
component has been configured to supply power to several components. For example, PDU A and PDU B receive power from the same UPS. h2.
Recommended Action # Right-click the message in *Recommendation* and select *Show in Editor* to identify the components with the invalid
power path in the layout. # Review the power connections of the invalid power path. #* Right-click the power component that is providing power to
or receiving power from a wrong component, select *Properties*, and remove the invalid power connection configured. ||See also|| [Optimizing the
design by following the recommendations]

Associated device data has been lost

{set-metadata:_UImapping_}deviceAssociationConstraint{set-metadata} h2. Description {excerpt:hidden=false}The component in the data center
model is associated to a real-world device but the device data from the {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} is
no longer available. {excerpt} h2. Recommended Action # Right-click the message in the *Recommendation* pane and select *Show in
Navigation*. # Review why the data center model no longer accurately represents the real-world infrastructure. #* Right-click the highlighted
component in the *Navigation* pane and select *Unassociate Device*, if the component should no longer be associated with the device. #*
Right-click the highlighted component in the *Navigation* pane and select *Delete*, if the modeled component no longer exists in the real-world
infrastructure. ||See also|| [Optimizing the design by following the recommendations]

Breakers in module must have unique power phases

{set-metadata:_UImapping_}breakersInModuleMustHaveUniquePowerPhasesConstraint{set-metadata} h2. Description {excerpt:hidden=false}In a
situation in which multiple users are working on the same system, another user might already have added the phase you added to the table in the
*Power Distribution* properties page for the RDP, PP, or PDU.{excerpt} The numbers in brackets tell you which module number and phase
combination causes the issue. {tip:icon=false} *Note*: This recommendation occurs only once for each item even if there are more issues on the
item. This means that you may see that resolving one issue on an item results in the message reoccurring with a different module number and
phase combination. {tip} h2. Recommended Action * Delete the entry if it is a duplicate. * Assign another phase to the module if you made a typo.
|| See also || [Optimizing the design by following the recommendations]

Capacity group equipment is placed in multiple rooms

{set-metadata:_UImapping_}capacityGroupSpanMultipleRoomsConstraint{set-metadata} h2. Description {excerpt:hidden=false}Capacity groups
should not include racks that are not placed in the same room.{excerpt} h2. Recommended Action # If the view tab selected in the floor layout is
other than *Capacity Group*, click it to select it. # In the Capacity Groups* pane, identify the group that includes racks in multiple rooms. # Drag all
the racks from this group into the same room, or right-click any racks that should not be in the group, and select *Remove from Capacity Group*.
||See also|| [Optimizing the design by following the recommendations]

Connection has not been configured between PDU and power supply
{set-metadata:_UImapping_}pduNotConnectedToSupplierConstraint{set-metadata} h2. Description {excerpt:hidden=false}A power connection is
missing in the data center model from this PDU to the power supply from which it should receive power.{excerpt} h2. Recommended Action #
Right-click the PDU and select *Properties* to open its Properties dialog box. # In *Power Dependency* page, select the appropriate *Power
supply*option to connect the PDU to the PDU or UPS from which it should receive power. ||See also|| [Optimizing the design by following the
recommendations]

Connection has not been configured between Power Panel and power supply
{set-metadata:_UImapping_}powerPanelNotConnectedToSupplierConstraint{set-metadata} h2. Description {excerpt:hidden=false}A power
connection is missing in the data center model from this Power Panel to the power supply from which it should receive power.{excerpt} h2.
Recommended Action # Right-click the Power Panel and select *Properties* to open its Properties dialog box. # In *Power Dependency* page,
select the appropriate *Power supply* option to connect the Power Panel to the Power Panel or UPS from which it should receive power. ||See
also|| [Optimizing the design by following the recommendations]

Connection has not been configured between remote distribution panel (RDP) and power supply
{set-metadata:_UImapping_}rdpNotConnectedToSupplierConstraint{set-metadata} h2. Description {excerpt:hidden=false}A power connection is
missing in the data center model from this Remote Distribution Panel (RDP) to the power supply from which it should receive power.{excerpt} h2.
Recommended Action # Right-click the RDP and select *Properties* to open its Properties dialog box. # In the *Power Dependency* page, select
the appropriate *Power supply* option to connect the RDP to the PDU from which it should receive power. ||See also|| [Optimizing the design by
following the recommendations]

Equipment connected to this PDU draws more power than is supported by the power supply breaker
{set-metadata:_UImapping_}pduMaxPowerDrawExceededConstraint{set-metadata} h2. Description {excerpt:hidden=false}The breaker does not
provide sufficient power to cover the power requirements of the equipment connected to this PDU. If you are working with 3 phase equipment, this
will trigger a recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action * If the equipment
drawing power from this PDU is part of a capacity group, reduce the average estimated load for the group: *# In the *Layout* pane, right-click a

rack in a capacity group and select *Properties* to open its Properties dialog box. *# In the *Capacity* page, reduce the *Average estimated load*
for all racks in the capacity group. *# Repeat steps 1 and 2 for any other capacity groups that get power from the PDU. * Lower the estimated load
by disconnecting as much of the equipment that receives power from the PDU as necessary to keep the estimated load on the PDU within the
values supported by the breaker: *# Right-click the PDU in the *Layout* pane and select *Properties* to open its Properties dialog box. *# Select
*Power Distribution* and edit or delete any surplus power connections * In the *Rack Layout*, select equipment in the racks that connect to the
PDU to drag that equipment to racks that are not connected to it. ||See also|| [Optimizing the design by following the recommendations]

Equipment connected to this Power Panel draws more power than is supported by the power supply
breaker
{set-metadata:_UImapping_}powerPanelMaxPowerDrawExceededConstraint{set-metadata} h2. Description {excerpt:hidden=false}The breaker
does not provide sufficient power to cover the power requirements of the equipment connected to this power panel. If you are working with 3
phase equipment, this will trigger a recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action *
If the equipment drawing power from this Power Panel is part of a capacity group, reduce the average estimated load for the group: *# In the
*Layout* pane, right-click a rack in a capacity group and select *Properties* to open its Properties dialog box. *# In the *Capacity* page, reduce
the *Average estimated load* for all racks in the capacity group. *# Repeat steps 1 and 2 for any other capacity groups which get power from the
Power Panel. * Lower the estimated load by disconnecting as much of the equipment that receives power from the Power Panel as necessary to
keep the estimated load on the Power Panel within the values supported by the breaker: *# Right-click the Power Panel in the *Layout* pane and
select *Properties* to open its Properties dialog box. *# Select *Power Distribution* and edit or delete any surplus power connections * In the
*Rack Layout*, select equipment in the racks that connect to the Power Panel to drag that equipment to racks that are not connected to it. ||See
also|| [Optimizing the design by following the recommendations]

Equipment connected to this remote distribution panel (RDP) draws more power than is supported by
the power supply breaker
{set-metadata:_UImapping_}rdpMaxPowerDrawExceededConstraint{set-metadata} h2. Description {excerpt:hidden=false}The breaker does not
provide sufficient power to cover the power requirements of the equipment connected to this RDP. If you are working with 3 phase equipment, this
will trigger a recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action * If the equipment
drawing power from this RDP is part of a capacity group, reduce the average estimated load for the group: *# In the *Layout* pane, right-click a
rack in a capacity group and select *Properties* to open its Properties dialog box. *# In the *Capacity* page, reduce the *Average estimated load*
for all racks in the capacity group. *# Repeat steps 1 and 2 for any other capacity groups that get power from the remote distribution panel (RDP).
* Lower the estimated load by disconnecting as much of the equipment that receives power from the remote distribution panel (RDP) as
necessary to keep the estimated load on the remote distribution panel (RDP) within the values supported by the breaker: *# Right-click the remote
distribution panel (RDP) in the *Layout* pane and select *Properties* to open its Properties dialog box. *# Select *Power Distribution* and edit or
delete any surplus power connections. * In the *Rack Layout*, select equipment in the racks that connect to the remote distribution panel (RDP) to
drag that equipment to racks that are not connected to it. ||See also|| [Optimizing the design by following the recommendations]

Equipment in this rack receives power from multiple power supply devices
{set-metadata:_UImapping_}PowerPathSetupForNetworkingRackConstraint{set-metadata} h2. Description {excerpt:hidden=false}Multiple power
connections have been set up for equipment in this rack. It can be supplied either through rack PDUs or, if it is a rack with network equipment,
Ethernet. Network equipment not using power from the UPS must be excluded from the power calculations. {excerpt} h2. Recommended Action
To configure a network power connection for the rack: # Remove the rack PDUs in the rack. # Right-click the rack in the layout and select
*Properties* to open its Properties dialog box. # Ensure *Exclude rack's load from power calculations* has been selected. To configure a rack
PDU power connection: # Right-click the rack in the layout and select *Properties* to open its Properties dialog box. # Ensure *Exclude rack's load
from power calculations* has been deselected. # Add rack PDUs to the rack and configure the power connection. ||See also|| [Optimizing the
design by following the recommendations]

Equipment is connected to a rack PDU outside this rack

{set-metadata:_UImapping_}serverIsConnectedToRmPduInAnotherRackConstraint{set-metadata} h2. Description {excerpt:hidden=false}The
power connection set up for this equipment is not optimum. It is set up to be supplied by a rack PDU that is not positioned in the same rack as the
equipment.{excerpt} Optimize the connection by editing the power connection of the piece of equipment that is not connected to the intended rack
PDU. h2. Recommended Action * Drag the server to the same rack as the connected rack PDU, or * Right-click the server and select *Properties*
to open its Properties dialog box. ** In the *Power* page, select the appropriate cable connection to connect to a rack PDU in the same rack as
the equipment. ||See also|| [Optimizing the design by following the recommendations]

Internal redundancy setup for UPS and group must match

{set-metadata:_UImapping_}InternalRedundancyOfCapacityGroupMustMatchUpsInternalRedundancyConstraint{set-metadata} h2. Description
{excerpt:hidden=false}The internal redundancy setup for the UPS and group does not match, for example N and N+1.{excerpt} h2.
Recommended Action Perform one of the following actions: * Right-click the UPS and select *Properties* to modify *Internal redundancy*, a
*Power* option in the Properties dialog box, to match the redundancy setting selected for the capacity group. * Right-click a rack in the capacity
group and select *Properties* to modify *Internal redundancy*, a *Capacity* option in the Properties dialog box, to match the redundancy setting
selected for the UPS. ||See also|| [Optimizing the design by following the recommendations]

PDU and connected rack PDU are placed in different rooms

{set-metadata:_UImapping_}powerDistributionEquipmentAndRmPduInSameRoomConstraint{set-metadata} h2. Description
{excerpt:hidden=false}This PDU is distributing power to one or more rack PDUs outside this room.{excerpt} h2. Recommended Action * Drag the
connected equipment into the same room. * Or reconnect to equipment in the same room. ||See also|| [Optimizing the design by following the
recommendations]

PDU output voltage has not been configured

{set-metadata:_UImapping_}pduOutputVoltageMustBeDefinedConstraint{set-metadata} h2. Description {excerpt:hidden=false}Output voltage has
not been configured for this PDU.{excerpt} h2. Recommended Action # Right-click the PDU and select *Properties* to open its Properties dialog
box. # In the *Power Distribution* page, select the appropriate *Output voltage* option. ||See also|| [Optimizing the design by following the
recommendations]

Power connection configuration is invalid for equipment in one or more racks in the group
{set-metadata:_UImapping_}rackInGroupMustConnectToSameUPSConstraint{set-metadata} h2. Description {excerpt:hidden=false}A rack PDU in
this capacity group is connected to a power supply that does not match the connection set up for the other rack PDUs, e.g. all rack PDUs in a rack
are connected to a specific UPS except for one that is connected to another UPS.{excerpt} h2. Recommended Action To make the connections
match, edit the power connection of the rack PDU that is not connected to the intended power supply as described below, or remove the rack
from the group by right-clicking it and selecting *Remove from Capacity Group*. # In the *Floor Layout*, select the *Power Path* tab at the bottom
of the layout pane. # Identify the rack in the group with the unwanted power connection setup (the color-coded connections help identify the
connections). # In the *Layout* pane, right-click the rack identified in step 2 and select *Properties* to open its *Properties* dialog box. # In the
*Power* page, set its power supply connection to match the other rack PDUs in the capacity group. Alternatively, you can right-click the PDU or
Power Panel and select *Properties*, then select the *Power Dependency* pane to access the *Power Distribution* properties to select a rack
PDU. Click *Edit* and edit the power connection to match the other connections for equipment in the same rack. ||See also|| [Optimizing the
design by following the recommendations]

Power distribution equipment must have unique breaker module numbers

{set-metadata:_UImapping_}powerDistributionEquipmentMustHaveUniqueBreakerModuleNumbersConstraint{set-metadata} h2. Description
{excerpt:hidden=false}In a situation in which multiple users are working on the same system, another user might already have added the breaker
module number you typed into the *Power Distribution* properties page for the RDP, PP, or PDU. The number in brackets tells you which module
number causes the issue.{excerpt} {tip:icon=false} *Note*: This recommendation occurs only once for each item even if there are more issues on
the item. This means that you may see that resolving one issue on an item results in the message reoccurring with a different module number and
phase combination. {tip} h2. Recommended Action * Delete the entry if it is a duplicate. * Assign a new breaker module number if you made a
typo. || See also || [Optimizing the design by following the recommendations]

Power feed connection for UPS and group must match

{set-metadata:_UImapping_}rackPowerFeedViolateGroupPowerFeedConstraint{set-metadata} h2. Description {excerpt:hidden=false}The Power
feed connection for the UPS and the capacity group does not match.{excerpt} h2. Recommended Action Perform one of the following actions: *
Right-click the UPS and select *Properties* to modify *Feed*, a *Power* option in the Properties dialog box, to match the feed selected for the
capacity group. * Right-click a rack in the capacity group and select *Properties* to modify *Power Feed*, a *Capacity* option in the Properties
dialog box, to match the feed selected for the UPS. * If you have redundant power supply (A+B Feed UPS), select *2N* in the *Power Feed* field.
||See also|| [Optimizing the design by following the recommendations]

Power Panel output voltage has not been configured

{set-metadata:_UImapping_}powerPanelOutputVoltageMustBeDefinedConstraint{set-metadata} h2. Description {excerpt:hidden=false}Output
voltage has not been configured for this Power Panel.{excerpt} h2. Recommended Action # Right-click the Power Panel and select *Properties* to
open its Properties dialog box. # In the *Power Distribution* page, select the appropriate *Output voltage* option. ||See also|| [Optimizing the
design by following the recommendations]

Rack's estimated load exceeds group's peak load settings

{set-metadata:_UImapping_}rackPeakExceedsGroupPeakPowerDrawConstraint{set-metadata} h2. Description {excerpt:hidden=false}The rack's
estimated load exceeds the peak load set up for the group. If you are working with 3 phase equipment, this will trigger a recommendation
message even if the value is exceeded for only one of the phases. {excerpt} h2. Recommended Action Perform one of the following actions: *
Change the group's peak estimated load settings: *# Select the *Floor Layout*. *# In the layout pane, right-click a rack in the capacity group and
select *Properties* to open its Properties dialog box. *# In the *Capacity* page, edit the *Peak load* for all racks in the capacity group. * Change
the phase settings: *# If a server's load on 1 phase is causing the warning and there is still capacity left on the other phases, right-click the server
and select *Properties* to open its Properties dialog box. *# In *Power* page, edit to connect to another phase in *Connections* section. \\ \\
{tip:icon=false}*Tip*: Select the *Power Details* tab available at the bottom of the *Rack Layout* pane to see a color-coded bar below the racks
illustrating the load distribution on the phases.{tip} * Remove equipment from one or more racks: *# Select the *Rack Layout*. *# In the layout
pane, select a rack in the capacity group and delete some equipment that requires power from the rack (or move that equipment to another rack).
*# Repeat step 2, as needed. * Remove the rack from the group and add it to another group: *# Select the *Floor Layout*. *# In the layout pane,
right-click rack and select *Remove from Capacity Group* to remove it from the capacity group. *# Repeat step 2, as needed. ||See also||
[Optimizing the design by following the recommendations]

Rack's power configuration does not support distribution redundancy

{set-metadata:_UImapping_}RacksInGroupWithDistributionRedundancyHasTwoOrMoreCompatibleRmPdusConstraint{set-metadata} h2.
Description {excerpt:hidden=false}The rack does not have two or more compatible rack PDUs to comply with the group's distribution
redundancy.{excerpt} h2. Recommended Action Perform one of the following actions: * Remove the rack from the group and add it to another
group: *# Select the *Floor Layout*. *# In the layout pane, right-click rack and select *Remove from Capacity Group* to remove it from the
capacity group. *# Repeat step 2, as needed. * Change the group's distribution redundancy settings: *# Select the *Floor Layout*. *# In the layout
pane, right-click a rack in the capacity group and select *Properties* to open its Properties dialog box. *# In the *Power* page, edit the
*Distribution redundancy* setting for all racks in the capacity group. * Add compatible rack PDUs to the racks that form the group: *# Select the
*Rack Layout*. *# In the layout pane, select a rack in the capacity group and add and connect rack PDUs to support distribution redundancy. *#
Repeat step 2, as needed. ||See also|| [Optimizing the design by following the recommendations]

Rack does not support the group's peak load settings

{set-metadata:_UImapping_}groupPlannedPeakExceedsRackPowerConstraint{set-metadata} h2. Description {excerpt:hidden=false}The breakers
or rack PDUs in a rack do not support the planned peak load set up for the capacity group: the planned power peak value setup for the group is
higher than the value the breaker can support. If you are working with 3 phase equipment, this will trigger a recommendation message even if
only one of the phases is overloaded.{excerpt} h2. Recommended Action Perform one of the following actions: * Change the breaker settings of
the rack PDUs in the selected rack, still accounting for the physical limits of the breaker: ** Right-click the rack and select *Properties* to open its
*Properties* dialog box. ** In the *Power* page, select the appropriate *Breaker rating*, *Breaker derating* and *Power phase*. * Add more rack
PDUs to the rack: ** Select the *Rack Layout* and drag a rack PDU or rack PDUs from the *Catalog* pane into the rack in the *Layout* pane. *

Reduce the capacity group's peak load setting: ** Right-click the rack and select *Properties* to open its *Properties* dialog box ** In the
*Capacity* page, reduce the *Peak Load (per rack)* value. * Remove the rack from this capacity group by right-clicking the rack, and selecting
*Remove from Capacity Group*. ||See also|| [Optimizing the design by following the recommendations]

Rack is not included in a capacity group

{set-metadata:_UImapping_}RackWithoutCapacityPlanInRoomConstraint{set-metadata} h2. Description {excerpt:hidden=false}The rack has not
been configured to be a part of a capacity group.{excerpt} {tip:icon=false}*Note*: A rack must have at least one rack PDU powered before it can
be included in a capacity group. (For more information, see [Rack is without rack PDU or a rack PDU is not powered|Rack is without rack PDU or
a rack PDU is not powered].) {tip} h2. Recommended Action If you want to include the rack in a capacity group, perform one of the following
actions: * Select *Tools* *> Generate Capacity Groups* to automatically include the rack in a capacity group: *# Select *> Generate Groups for*
*> Racks not currently in a Capacity Group* or *All Racks in selected room(s)* . *# Select the room(s) for which you want to generate groups. *
Select to manually include the rack in a capacity group: *# In the *Capacity Groups* pane, right-click the rack in the *Unassigned capacity groups
equipment* list and select *Add to Capacity Group* or *New Capacity Group*. *# Select to see the groups highlighted in the layout by clicking the
*Capacity Group* tab in the *Floor Layout*. ||See also|| [Optimizing the design by following the recommendations]

Rack is without rack PDU or a rack PDU is not powered

{set-metadata:_UImapping_}powerPathNotSetupForRackConstraint{set-metadata} h2. Description {excerpt:hidden=false}The rack is without rack
PDUs or its rack PDUs are not connected to a PDU, remote distribution panel (RDP) or power panel. {excerpt} h2. Recommended Action #
Perform one of the following actions: #* If there are no rack PDUs in the rack, select the *Rack Layout* and drag rack PDUs, one at a time, from
the *Catalog* pane into the rack in the *Layout* pane. \\ \\ {tip:icon=false}*Tip*: You can also select a rack PDU in the *Catalog* pane, and then
use the *Rack-Mount Equipment Placement* pane to add multiple copies to the selected rack.{tip} #* If there is no power supply (PDU or remote
distribution panel (RDP)), select the *Floor Layout* perspective and add the required power supply devices, one at a time, from the *Catalog*
pane into the floor layout. #* If there are rack PDUs in the rack and power supply in the solution, go directly to step 2. # Right-click the rack in the
*Layout* pane and select *Properties* to open its Properties dialog box. # In the *Power* page, set up the power connection between a rack PDU
and a PDU, Power Panel or remote distribution panel (RDP). # Repeat step 3 until there are no more unconnected rack PDUs in the rack. ||See
also|| [Optimizing the design by following the recommendations]

The average estimated load of the racks in the group exceeds the group's average load settings
{set-metadata:_UImapping_}RackTotalPowerDrawExceedsGroupPlannedAvg{set-metadata} h2. Description {excerpt:hidden=false}The estimated
load of the racks in the group is higher on average than what you are planning for the group. If you are working with 3 phase equipment, this will
trigger a recommendation message even if the value is exceeded for only one of the phases. {excerpt} h2. Recommended Action Perform one of
the following actions, making sure that the data center model still reflects the actual physical infrastructure: * Right-click racks in the capacity
group and select *Properties* to reduce the *Average Load (per rack)*, a *Capacity* option in the Properties dialog box for these racks until the
racks no longer exceed the group's average estimated load setting. * Remove equipment from one or more of the racks until the connected racks
no longer exceed the group's average estimated load setting. * Change the phase settings: *# If a server's load on only 1 phase is causing the
warning and there is still capacity left on the other phases, right-click the server and select *Properties* to open its Properties dialog box. *# In
*Power* page, edit to connect to another phase in *Connections* section. \\ \\ {tip:icon=false}*Tip*: Select the *Power Details* view tab available at
the bottom of the *Rack Layout* pane to see a color-coded bar below the racks illustrating the load distribution on the phases.{tip} * Remove one
or more of the racks from the group until the remaining connected racks no longer exceed the group's average load setting. ||See also||
[Optimizing the design by following the recommendations]

The breaker configuration does not support rack's estimated load

{set-metadata:_UImapping_}RackNameplateExceedsPhysicalMaxBreakerRatingConstraint {set-metadata} h2. Description
{excerpt:hidden=false}The equipment in the rack draws more power than the breaker supports. If you are working with 3 phase equipment, this
will trigger a recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action Perform one of the
following actions: * Select the *Rack Layout* and remove equipment from the rack to decrease its power requirement or add another rack PDU to
the rack. * Select the *Floor Layout* and edit the power properties for the rack PDUs in the rack: ** Right-click the rack in the *Layout pane* and
select *Properties* to open its *Properties* dialog box. ** In the *Power* page, select a rack PDU in the list. ** Modify its *Breaker* settings,
including *Power phase*, until *Power Availability* reports more available kilowatts the estimated load reported by *Power Consumption* (still
accounting for the physical limits of the breaker). ||See also|| [Optimizing the design by following the recommendations]

The breaker configuration in the Power Distribution properties does not match the measured power
data
{set-metadata:_UImapping_}measuredPowerDrawMatchesBreakerModuleSetupConstraint{set-metadata} h2. Description
{excerpt:hidden=false}When the configuration is done and the system is running with device associations and retrieval of measured data from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}, the system notifies you if the module number and phase configuration in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} do not match the measurements. The number in brackets tells you which
module number causes the issue. h2. Recommended Action * Reconfigure the breaker configuration to match the actual physical environment. *
If you have configured sensor mappings, reconfigure the sensor mapping configuration to match the actual physical environment. {tip:icon=false}
*Note*: When you have reconfigured and resolved the issue, it may take some time before new data is retrieved from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} and this message disappears.{tip} h2. Example The system will notify you
when there is a mismatch between the configuration and the measured data for a module. For example, you will get this notification if you have
configured Rack PDU connections for breaker module 10, 11, 12, and 13 on a modular PDU but measured data only exists for module 10, 11,
and 13. In this case, you can right-click the PDU and select *Launch to Device* to see the measured data and module numbers to see what the
issue is with module 12. It is occupied and {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} reports an issue with it because
no measurements are available to the system. {tip:icon=false}{*}Note*: You cannot directly compare the power values you see here with the ones
in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. The power values displayed on the device in
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} are instant values whereas the values in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} are peak values. {tip} To resolve the issue, you must remove the module
number 12 from the breaker configuration in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.
!launchtodevice_seemoduleno.png|thumbnail! || See also || [Optimizing the design by following the recommendations]

The capacity group supports a higher redundancy than this server requires
{set-metadata:_UImapping_}rackPowerConsumerRedundcyShouldMatchCapacityGroupConstraint{set-metadata} h2. Description
{excerpt:hidden=false}The redundancy set up for the selected equipment in a rack does not match the internal redundancy planned for the
capacity group. The group supports a higher redundancy than the server requires.{excerpt} h2. Recommended Action * To avoid stranded
capacity, replace the rack-mounted equipment with equipment that has redundancy settings matching the group settings. Remove it and add a
better match, either by using drag-and-drop or *Add to Best rack* (if you have the add-on product installed that enables this feature). * If the
equipment's redundancy settings are incorrect: *# In the *Rack Layout*, right-click the equipment and select *Properties*. *# In the *Power* page,
select the appropriate *Redundancy*. ||See also|| [Optimizing the design by following the recommendations]

The input voltage setting required by the equipment is not available in current rack
{set-metadata:_UImapping_}EquipmentInputVoltageIsNotSupportedByRackConstraint{set-metadata} h2. Description {excerpt:hidden=false}In the
data center model, the server's input voltage requirement cannot be supplied by the rack PDU in the rack. {excerpt} h2. Recommended Action
Make sure the voltage of the server matches the voltage of the rack PDU to which you want to connect: * Replace the rack PDU with one that
supports the required voltage. * Replace the server with one that has the correct input voltage supported by the rack PDU. * If the voltage
properties of either the server, rack PDU, PDU or Power Panel are incorrect, right-click that piece of equipment in the catalog and select
*Properties* to correct the value. ||See also|| [Optimizing the design by following the recommendations]

The measured load exceeds the estimated load per phase designed for the rack
{set-metadata:_UImapping_}MeasuredRackPeakExceedsRmPduAndPhaseMappedNameplatePowerDrawConstraint{set-metadata} h2.
Description {excerpt:hidden=false}Your physical infrastructure contains connected devices in the rack that use more power than the estimated
load per phase in the rack reflected in the data center model.{excerpt} {tip:icon=false}*Note*: This message only appears when all servers in a
rack have a power phase configuration. If you disconnect a phase connection for a server in a rack, this message will disappear, but it does not
necessarily mean there is no longer an issue with the configuration.{tip} h2. Recommended Action Update the solution to accurately reflect the
equipment in the physical infrastructure by adjusting the estimated load values for the equipment in the rack. * If you have added the appropriate
servers to the rack: ** Modify the estimated load: *** Right-click the servers in the rack and select *Properties*. *** Select the *Power* section to
access the power properties. *** Increase the *estimated load* value. ** Verify that the servers are connected to the correct phases in the system
to reflect your physical infrastructure: *** Right-click the servers in the rack and select *Properties*. *** Select the *Power* section to access the
power properties. *** Modify the phase connection in the *Power Cable Connection* table. * If you are in the process of designing your data center
and have not yet added the sufficient amount of servers to the rack: ** Drag the missing servers into the rack as required and configure phase
connection for each server. ||See also|| [Optimizing the design by following the recommendations]

The measured load exceeds the total estimated load configured for the rack
{set-metadata:_UImapping_}MeasuredRackPeakExceedsNameplatePowerDrawConstraint{set-metadata} h2. Description
{excerpt:hidden=false}Your physical infrastructure contains connected devices in the rack that use more power than the total estimated load in the
rack reflects.{excerpt} h2. Recommended Action Update the solution to accurately reflect the equipment in the physical infrastructure by adjusting
the estimated load values for the equipment in the rack. * If you have added the appropriate servers to the rack: ** Modify the estimated load: ***
Right-click the servers in the rack and select *Properties*. *** Select the *Power* section to access the power properties. *** Increase the
*Estimated load* value. * If you are in the process of designing your data center and have not yet added the sufficient amount of servers to the
rack: ** Drag the missing servers into the rack as required. ||See also|| [Optimizing the design by following the recommendations]

The measured load of the connected rack PDU is 0, but an estimated load has been configured for the
rack
{set-metadata:_UImapping_}MeasuredPowerDrawZeroConstraint{set-metadata} h2. Description {excerpt:hidden=false}The rack PDU in the layout
associated with an external system device reports no load, but in the data center model, an estimated load has been configured for the connected
servers in the layout.{excerpt} h2. Recommended Action Troubleshoot why the physical device is not reporting any measured data. It may be
turned off or not yet physically connected. ||See also|| [Optimizing the design by following the recommendations]

The measured load of the UPS exceeds the total estimated load of the connected equipment
{set-metadata:_UImapping_}MeasuredUpsPeakExceedsNameplatePowerDrawConstraint{set-metadata} h2. Description
{excerpt:hidden=false}Your physical infrastructure contains devices connected to the UPS that use more power than your design reflects or they
have not been assigned to the correct UPS in the data center model layout to correctly represent the physical infrastructure. If you are working
with 3 phase equipment, this will trigger a recommendation message even if the measured value is only too high for one of the phases.{excerpt}
{tip:icon=false}*Note*: This message will typically occur until the initial system setup has been completed. It can also occur if equipment has
recently been removed from the rack. The measured average value will change over time to reflect the change.{tip} h2. Recommended Action
Update the data center model to accurately reflect the equipment in the infrastructure by assigning devices to the correct location in the
*Navigation* pane. * If the device has been assigned to the wrong UPS in the *Layout* pane, drag it from that location in *Navigation* pane, or
floor layout, to the correct location. * If the value is wrong in the *Manufacturer's Nameplate* / *Estimated load* field for the connected equipment,
right-click the equipment and select *Properties* to correct the value. ||See also|| [Optimizing the design by following the recommendations]

The phase configuration for the connected server is not supported by the rack PDU
{set-metadata:_UImapping_}EquipmentIsConnectedToWrongPowerPhaseConstraint{set-metadata} h2. Description {excerpt:hidden=false}The
phase connection configured for this server is not valid. This message will typically occur if you have configured a power connection to this server
but subsequently make changes to the phase configuration.{excerpt} h2. Recommended Action * Modify the server's phase properties: **
Right-click the server in the rack and select *Properties*. ** Select the *Power* section to access the power properties. ** Modify the phase
connection by selecting a valid power phase connection in the *Power Cable Connection* table. ** If there is no available phase to choose, the
rack PDU output voltage might not match the server's voltage requirements. * Modify the rack PDU's phase properties: ** Right-click the rack PDU
in the rack and select *Properties*. ** Select the *Power Dependency* section to access the power properties. ** Modify the phase connection by
selecting a valid power phase connection in the *Power phase* drop-down. ||See also|| [Optimizing the design by following the recommendations]

The Rack PDU output voltage setting does not match the output voltage of the connected PDU or
Power Panel

{set-metadata:_UImapping_}RmPduVoltageIsNotSupportedByPduConstraint{set-metadata} h2. Description {excerpt:hidden=false}The power

connection is invalid because the voltage required by the rack PDU is not available from the power distribution component.{excerpt} h2.
Recommended Action * Make sure the voltage of the rack PDU match the voltage of the PDU or Power Panel to which you want to connect: **
Replace the PDU or Power Panel with one that supports the required voltage. ** Replace the rack PDU with one that has the correct input voltage
supported by the PDU or Power Panel. ** If the voltage properties of either the rack PDU, PDU or Power Panel are incorrect, right-click that piece
of equipment in the catalog and select *Properties* to correct the value, before setting up the power connections. * Make sure the required phases
are available on the rack PDU to make the connection: ** Right-click the rack PDU and select *Properties* to see the value. ||See also||
[Optimizing the design by following the recommendations]

The server should not be supplied from different phases on 1 UPS

{set-metadata:_UImapping_}TwoNServersConnectedToSamePhaseConstraint{set-metadata} h2. Description {excerpt:hidden=false}The system
does not support rack PDU redundancy configurations. If a server is connected to different phases on the same UPS, the system will assume the
server's load is drawn not on one phase at a time but on both. This means that the system's calculations and recommendations will seem
unnecessarily pessimistic and you may in fact have more available capacity on the UPS than the system implies. {excerpt} h2. Recommended
Action # Right-click the server and select *Properties* to open its Properties dialog box. # In the *Power* page, select the appropriate
*Connections* options. {tip:icon=false}*Note*: If you choose to ignore the message and keep the non-supported rack PDU redundancy
configuration, you may not be able to get the full benefit of the capacity functionality and proposed best location for adding or moving a server.
{tip} ||See also|| [Optimizing the design by following the recommendations]

The UPS in the layout does not supply enough power to match the configured load of connected
equipment in the layout
{set-metadata:_UImapping_}UpsCapacityExceedPlannedCapacityConstraint{set-metadata} h2. Description {excerpt:hidden=false}The load of the
equipment connected to the UPS is higher than the load that the UPS can supply. If you are working with 3 phase equipment, this will trigger a
recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action Perform one of the following actions:
* For racks in a capacity group, right-click racks in the group and select *Properties* to reduce the *Average Load (per rack)*, a *Capacity* option
in the *Properties* dialog box for these racks until the racks no longer exceed the capacity of the UPS. * For racks not in a capacity group, remove
equipment from one or more of the racks until the total power consumption of the connected racks no longer exceeds the capacity of the UPS.
Total power consumption is the sum of the *Estimated load*, a *Power* value in the Properties dialog box of the racks connected to the UPS. *
For other equipment connected to the UPS, for example a CRAC, review the estimated load value or disconnect its power connection to the UPS.
* Right-click the UPS and select *Properties* to increase its *Capacity*, a *Power* option in the Properties dialog box. * Replace the UPS with one
that can distribute more power. ||See also|| [Optimizing the design by following the recommendations]

This equipment in store room is connected to equipment in a room

{set-metadata:_UImapping_}ItemOnStorageHasAPowerPathConstraint{set-metadata} h2. Description {excerpt:hidden=false}Equipment
connected to other equipment in a room has been moved to a store room.{excerpt} h2. Recommended Action # Right-click the equipment in the
store room and select *Properties* to open its Properties dialog box. # For a server, change the *Power cable connection* setting in the *Power*
page. # For a rack PDU, PDU, Power Panel, or RDP, change the connection in the *Power supply* setting in the *Power Dependency* page.
||See also|| [Optimizing the design by following the recommendations]

This server requires a higher redundancy than is available in the capacity group
{set-metadata:_UImapping_}RackPowerConsumerRedundancyMustMatchCapacityGroup{set-metadata} h2. Description
{excerpt:hidden=false}The redundancy set up for the selected equipment in a rack does not match the internal redundancy planned for the
capacity group. The server requires a higher redundancy than is available in the group.{excerpt} h2. Recommended Action * Replace the
rack-mounted equipment with equipment that has redundancy settings matching the group settings or * If the equipment's redundancy settings
are incorrect: *# In the *Rack Layout*, right-click the equipment and select *Properties*. *# In the *Power* page, select the appropriate
*Redundancy*. ||See also|| [Optimizing the design by following the recommendations]

UPS internal redundancy has not been configured

{set-metadata:_UImapping_}UpsInternalRedundancyMustBeDefinedConstraint{set-metadata} h2. Description {excerpt:hidden=false}The internal
redundancy has not been configured for this UPS.{excerpt} h2. Recommended Action # Right-click the UPS in the *Layout* pane and select
*Properties* to open its *Properties* dialog box. # In the *Power* page, define the *Internal Redundancy*. ||See also|| [Optimizing the design by
following the recommendations]

UPS power feed has not been configured

{set-metadata:_UImapping_}UpsPowerFeedMustBeDefinedConstraint{set-metadata} h2. Description {excerpt:hidden=false}The power feed has
not been configured for this UPS.{excerpt} h2. Recommended Action # Right-click the UPS in the *Layout* pane and select *Properties* to open
its Properties dialog box. # In the *Power* page, define *Redundancy* as *A Feed* or *B Feed*. ||See also|| [Optimizing the design by following
the recommendations]

Configuring the PUE DCiE

{section}{column:width=50%}{excerpt:hidden=false}Configure the device sensor measurements, or any known constants of the energy system, to
ensure the configuration accurately reflects the live physical infrastructure of the system. When configured, you can view the PUE/DCiE dial
published to the PUE/DCiE Dashboard, showing the PUE/DCiE value based on the configured values for power entering the data center and IT
load.{excerpt} The PUE/DCiE Dashboard, available by selecting *> Analytics* *> PUE/DCiE Dashboard* in the Application bar, shows measured
data collected daily (midnight to midnight), also referred to as measurement sampling level 2, intermediate according to the Green Grid
definitions. For information about the energy efficiency concepts, such as Power Usage Effectiveness (PUE), go to: [the Green
Grid|http://www.thegreengrid.org/] and read the [White Papers|http://www.apc.com/go/promo/whitepapers/index.cfm]. * WP-157: Selecting an
Industry-Standard Metric for Data Center Efficiency * WP-154: Electrical Efficiency Measurement for Data Centers * WP-114: Implementing
Energy Efficient Data Centers * WP-113: Electrical Efficiency Modeling for Data Centers You can toggle the efficiency metric between PUE and
DCiE in *> Tools* *> Preferences* *> General*. {column}{column:width=50%} !PUE_DCiEConfig1.PNG|thumbnail! {column}{section} || 123 Steps
to... || See also || | *Configuring the energy system* \\ # Use the icons in *Power In* section of the *Configuration* tab to set up the system with
information about the total amount of power entering the data center. ## Add device sensor measurements by clicking this icon

!icon_instantPUE_adddevices.png!. ## In the wizard, follow the steps to select one or more devices and sensors from the list. \\ \\
{tip:icon=false}*Tip*: Select multiple non-consecutive items by using Ctrl-click, or multiple consecutive items by using Shift-click.{tip} ## You can
filter the list and search for one or more devices or sensors to add to the PUE/DCiE calculation by starting to type the name or model in the
*Search* field. As you type in the Search box, the list shows all equipment that contains the typed characters in the selected column. ## Add
custom values by clicking this icon !icon_instantPUE_addcustom.png!. ## In the dialog box, type *Name*, *Value*, *Unit*, and *Factor*. *Unit* and
*Factor* can be used to make adjustments to the value, e.g. if the unit of one item does not match the others, such as kW and W or kVA, or if
there is a factor that needs to be left out of the calculation, for example if the value is a total and some of it is used for other data centers as well.
## Delete any obsolete entries by clicking this icon !icon_instantPUE_deleteentry.png!. # Use the icons in *IT Load* section of the *Configuration*
tab to set up the system with information about how much power is needed by the IT load in the data center. ## Add device sensor measurements
by clicking this icon !icon_instantPUE_adddevices.png!. ## In the wizard, follow the steps to select one or more devices and sensors from the list.
\\ \\ {tip:icon=false}*Tip*: Select multiple non-consecutive items by using Ctrl-click, or multiple consecutive items by using Shift-click.{tip} ## You
can filter the list and search for one or more devices or sensors to add to the PUE/DCiE calculation by starting to type the name or model in the
*Search* field.\\ In the *Search* box, start typing some characters of the equipment you want to see. As you type, the pane shows all items that
contain the typed characters in the column that is selected. ## Add custom values by clicking this icon !icon_instantPUE_addcustom.png!. ## In
the dialog box, type *Name*, *Value*, *Unit*, and *Factor*. \\ *Unit* and *Factor* can be used to make adjustments to the value, e.g. if the unit of
one item does not match the others, such as kW and W or kVA, or if there is a factor that needs to be left out of the calculation, for example if the
value is a total and some of it is used for other data centers as well. \\ ## Delete any obsolete entries by clicking this icon
!icon_instantPUE_deleteentry.png!. # See the results of the configuration expressed as a graph in the PUE/DCiE dial published to the PUE/DCiE
Dashboard available from *> Analytics* *> PUE/DCiE Dashboard*. It can also be accessed at any time on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server for viewing without having the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application running. \\ \\ {tip:icon=false}*Note*: The PUE/DCiE graph shows
the calculated PUE/DCiE based on measured data collected on a daily basis (midnight to midnight). This data collection method is also referred to
as measurement sampling level 2, intermediate according to the Green Grid definitions. \\ When you add a sensor to the calculations, the data
collected from this sensor the previous day, if any, is included in the calculations immediately. When you add a newly-installed sensor, its value
will be included in the calculations once the data collection has run for 24 hours or at least since before the previous midnight.{tip}| [About PUE
and DCiE] [Preferences: Showing PUE or DCiE values|Reviewing system preferences#pref_EEmetric] [Using the PUE DCiE Dashboard]|

Using the PUE DCiE Dashboard

{section}{column:width=50%}{excerpt:hidden=false}See the results of the PUE/DCiE configuration expressed as a graph in the PUE/DCiE dial
published to the PUE/DCiE Dashboard. The PUE/DCiE graph on the PUE/DCiE Dashboard shows the calculated PUE/DCiE based on measured
data collected on a daily basis according to the configuration done in *Planning* *> PUE/DCiE Configuration*.{excerpt} For information about the
energy efficiency concepts used on the dashboard, such as Power Usage Effectiveness (PUE) and Data Center Infrastructure Efficiency (DCiE),
go to: [the Green Grid|http://www.thegreengrid.org/] and read the [White Papers|http://www.apc.com/go/promo/whitepapers/index.cfm]. * WP-157:
Selecting an Industry-Standard Metric for Data Center Efficiency * WP-154: Electrical Efficiency Measurement for Data Centers * WP-114:
Implementing Energy Efficient Data Centers * WP-113: Electrical Efficiency Modeling for Data Centers Select *Analytics* *> PUE/DCiE
Dashboard* to access the dashboard with the dial. You can also access it any time on the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} for viewing without having the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application running. The PUE/DCiE graph shows the calculated PUE/DCiE
based on measured data collected on a daily basis. When you add a sensor to the calculations, the data collected from this sensor the previous
day, if any, is included in the calculations immediately. When you add a newly-installed sensor, its value will be included in the calculations once
the data collection has run for 24 hours or at least since before the previous midnight. If you are using PUE as metric, the graph shows the PUE
up to 5. If the calculated PUE is greater than 5, the calculated value is displayed and the dial shows the maximum value possible (5).
{note:title=TIP:}You can toggle the metric between PUE and DCiE in *> Tools* *> Preferences* *> General*.{note}{column} {column:width=50%}
!PUE_DCiEDashboard1.png|thumbnail! {column}{section} ||See also|| [Configuring the PUE DCiE] [About PUE and DCiE] [Preferences: Showing
PUE or DCiE values|Reviewing system preferences#pref_EEmetric]

Working with reports

{section}{column:width=50%}{excerpt:hidden=false}Use the *Reports* tool, accessed by clicking *> Analytics > Reports* in the Application bar, to
generate report data for any server room's floor or rack-mountable equipment, or for the contents of store rooms. {excerpt} \\ \\ At any time, you
can generate reports from the application. The amount of available reports depends on your system setup, as some reports are
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} features,
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} features, or
{multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} features. \\ \\ In addition to the overview reports generated from *>
Analytics > Reports* in the Application bar, asset inventory and audit reports can also be generated for individual components and racks by
right-clicking a component or rack in the layout, and selecting *Asset Inventory* or *Asset Audit* (the audit report is available if you have
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} installed).{column}{column:width=50%}
!report.jpg|thumbnail!{column}{section} || 123 Steps to... || See also || | *Generating a report* \\ \\ {excerpt:hidden=false}You can generate various
reports based on standard or customized report designs.{excerpt} # From the Application bar, select *Analytics > Reports*. # In *All Reports View*
pane, select a report type from *Available Reports*. # Use the *Report Filter Options* to define the filter for what data to include in the report, for
example: ## Select the time range that you want the report to cover. ## Select the rooms that you want to include information about in the report.
## Select one or more tags if you want the report to only include information for specified equipment in specified room(s). TIP: You do not need to
select these options every time you generate a report. You can save the selected options as a filter and apply the filter the next time you need to
generate a report with the same filter options. # Select *Generate Report*.\\ The generated report displays in the *Report View*. You can now use
the *Report View* toolbar to navigate the report pages on the screen (arrow icons), or to print or export the report to a file in any of the available
formats (Export icon, down arrow for selection of format). | [Customizing report designs]\\ [Working with report filter templates] \\ [Audit Trail report]
\\ [Capacity reports] \\ [Energy Cost report] \\ [Inventory report] \\ [Network Summary report] \\ [Rack U-Space report] \\ [Work Order reports] \\ |

Working with report filter templates

You can save the selected filter options as a template to generate reports with the same settings, for example, a monthly inventory report for a
specific room. h2. Creating a report filter template # In *Available Reports*, select a report type. # In *Report Filter Options*, select the data that

you want to include when you generate a report based on these settings. # Click *Save Filter As...* in the top right corner of the options section.
Some data is required for certain report types. If you try to save without this data, you will be prompted to select the required options. # In the
Save dialog box, type a name for the report filter template. The saved report filter template now appears in the list of available reports as a sub
type to the selected report type. h2. Applying a previously saved report template # In *Available Reports*, click the + symbol next to the report
type to expand the list and see the available report filter templates. # Select the report filter template to apply. You can now see the filter settings
of the selected template. # Select *Generate Report*. The generated report displays in the *Report View*. You can now use the *Report View*
toolbar to navigate the report pages on the screen (arrow icons), or to print or export the report to a file in any of the available formats (Export
icon, down arrow for selection of format). ||See also|| [Working with reports] [Saving KPIs over time] [Customizing report designs]

Customizing report designs

In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, you can select a variety of filter options for the standard built-in reports.
This allows you to limit the available data to be included in the report, e.g. only data for a specific date range, or room. You can redesign and
customize the reports, including the filter parameters of the available data, and the available data itself, in a separate report design application,
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. !Configuring the room layout^video24x20.jpg! Watch this [video
tutorial|Video Tutorials#reportdesignvideo] to see how to work in {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} to change
the logo on a report. {tip:icon=false}*Note*: You must have a valid {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} license for
the application to be available for download.{tip} # Export one of the built-in standard report designs from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to use it as a template for the new custom report design. ## In
*File>Export*, select *Report Design*. ## Select from the list of report designs and save the report design to a location on your computer or
network with the extension .rptdesign. Skip the steps 2 through 4 if custom report designs have been created by someone else and made
available to you. # Open the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page in the web
browser by specifying the URL of the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server. # Click
*{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} Download* and follow the instructions to download and install
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. # Launch
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} and follow the instructions in the *New Report* wizard to create a new report
design. ## Type a name for the report with the extension .rptdesign. ## Select a report type to use as template for your design. These templates
contain the same data as the default reports available in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. In addition, there
is a blank report template for creating a new report without starting from predefined data. # Create the custom report design, save and publish to
the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server to make the report design available for use in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. #* For information about how to use
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}, refer to the built-in help system. #* To make the report design available on
the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, select *File>Publish to
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server*. # In
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, import the custom report design. ## If it is not already open, select
*Analytics>Reports* to switch to the report view. ## Select *File>Import>Report Design*. ## Select to save the custom report with a new name on
the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server or overwrite an existing report, and click OK. The new
report design has been saved to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server and appears in the list of
available reports in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. ||See also|| [StruxureWare Operations - Insight]
[Working with reports] [Working with report filter templates]

Working with localized reports

The reports are localized into the supported languages according to the locale set on the server. However, the built-in report names in the list of
*Available Reports* are only updated accordingly when you select to restore the default design. * Click the arrow down icon, and select *Restore
Default Designs*. \\ \\ !restoreDefaultDesigns.png|thumbnail! You can also specify the report name yourself. However, changing the name of the
available reports will only change the name in the list. Changing the title in the report requires you to redesign the report in
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. * Right-click the report name in the list of *Available Reports*, select
*Rename*, and type the new name. ||See also|| [Working with reports] [StruxureWare Operations - Insight] [Reconfiguring locale on the
StruxureWare Operations server]

Audit Trail report

{section}{column:width=50%}{excerpt:hidden=false}You can generate an Audit Trail report that lists actions recorded in the application, whether
those actions were in response to work orders, or changes made to the data center model.{excerpt} The Audit Trail report is available if you have
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true}. In addition to being available from *Analytics>Reports*, it can be
generated for individual components and racks in *Operations>Data Center* by right-clicking a component or rack in the layout, and selecting
*Asset Audit*. {column}{column:width=50%} !report_audittrail.png|thumbnail! {column}{section} ||See also|| [Working with reports]

Energy Cost report

{section}{column:width=50%}{excerpt:hidden=false}An Energy Cost report can be generated to calculate the costs for running specified
equipment used for charge back and efficient budgeting. {excerpt} The report will include data based on * The filter selections ** Time period **
Rooms ** Tags* * The entered kWh price * The entered overhead factor The system uses the best available data for the calculations. # Measured
load values: These values are used if the IT devices have been set up to report live measured data from an external monitoring system such as
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server. # Estimated load values from saved KPI data: These values are
used if there is no measured data available and the system has been set up to save KPI data (Capacity History preferences). The saved KPI
estimated load values result in a more accurate report than if only the present time estimated load is available. It allows for using the estimated
load throughout the specified time period. # Present time estimated load values: These values are used if there is no measured data or KPI data
available in the system, or if the manufacturer's nameplate value is all that is available to the system, this is the value that will be used. The
manufacturer's nameplate values are based purely on the manufacturer's nameplate of the specified equipment without taking any power loss into
account. The overhead factor can be used to adjust the costs to real world power usage effectiveness (PUE). Any changes done during the
specified time period will not be reflected in the report, which makes the report less accurate. For example, if you remove a piece of equipment in
between the start and end date, its estimated load value will be completely left out of the calculations. If you add a piece of equipment in between
the start and end date, its estimated load value will be included in the calculations as if it was in the solution throughout the entire time period. For

information about the energy efficiency concepts, such as Power Usage Effectiveness (PUE), go to: [the Green Grid|http://www.thegreengrid.org/]
and read the [White Papers|http://www.apc.com/go/promo/whitepapers/index.cfm]. * WP-157: Selecting an Industry-Standard Metric for Data
Center Efficiency * WP-154: Electrical Efficiency Measurement for Data Centers * WP-114: Implementing Energy Efficient Data Centers *
WP-113: Electrical Efficiency Modeling for Data Centers *Tags included in this report are tags on racks. If you include a piece of tagged
rack-mounted equipment and select to include this tag in the report, it will not be included in the report calculation. Only if the rack that the piece
of equipment is positioned in is tagged and selected for the report, it will be included. {column}{column:width=50%}
!report_energycost.png|thumbnail!{column}{section} ||See also|| [Working with reports]

Rack U-Space report

{section}{column:width=50%}{excerpt:hidden=false}A rack space report can be generated to review the amount of available positions in specified
racks for equipment that takes up one or more U-positions. {excerpt} The report will include data based on * The filter selections ** Rooms **
Tags* The calculations are based on equipment positioned in the rack layout and, if you have
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} installed, any equipment in pending state, even if it has not been added
yet (Pending Add), or if it has been marked for deletion (Pending Delete), or to be moved (Pending Move). *Tags included in this report are tags
on racks. If more tags have been assigned to a rack, the rack will only be included in the report if all tags assigned to it have been selected in the
report options. {column}{column:width=50%} !report_rackUspace.png|thumbnail!{column}{section} ||See also|| [Working with reports]

StruxureWare Operations - Capacity

{section}{column:width=50%} {excerpt:hidden=false}{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} allows you to design
a solution that maximizes the existing capacity for the devices monitored by an external system while designing that capacity to handle future
growth.{excerpt} Use the add-on capacity management module to simulate optimum capacity design by following the color-coded indications
when grouping new devices and moving or deleting existing devices in racks to avoid stranded capacity without exceeding the available power
distribution. {column} {column:width=50%} !Setting up a capacity plan^capacityplan.png|thumbnail! {column} {section} {section}
{column:width=30%} h5. Capacity Management [Setting up a capacity plan] [Finding the best location for a new server] h5. Capacity Groups
[Creating capacity groups|Working with capacity groups] [Working with capacity groups] {column} {column:width=30%} h5. Tags [Creating tags]
[Assigning tags|Working with Tags] h5. Cooling [Performing cooling simulation in the Cooling view] [Simulating rack and CRAC cooling changes]
h5. Reports [Capacity reports] {column} {column:width=30%} h5. Impact Analysis on Virtual Machine Hosts [Working with virtualization] [Locating
virtual machines hosts with impact in the layout] h5. IT Impact Simulation [Simulating IT Impact] [Configuring Simulated Impact Layout] [Filtering
Simulated Impact List (Search)|Filtering Simulated Impact List (Search)] [Exporting List View Table] {column} {section}

Setting up cable connection settings

{excerpt:hidden=false}In *Tools>Preferences>Cable Connection*, review or change the default cable connection settings between rack PDUs and
servers in the system. This is a {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature.{excerpt} # Define the default
power connection setup for a server when it is added to the layout from the *Catalog*. In *Cable Connection when moving a server*, select *Auto
calculate cable connection* or *No cable connection*. # Define the default power connection setup for a server when it is added to the layout from
another position in the *Rack Layout* or *Navigation*. In *Cable Connection when moving a server*, select *Auto calculate cable connection* or
*No cable connection*. {tip:icon=false}*Note*: If you add equipment using the [rack advisor functionality|Finding the best location for a new server]
in the *Rack-Mount Equipment Placement* pane, cable connections are automatically calculated regardless of the selection of cable connection
preferences.{tip} ||See also|| [Reviewing system preferences] [StruxureWare Operations - Capacity]

Setting up a capacity plan

{section}{column:width=50%}If you have set up a capacity plan in the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, the
system can make daily tasks significantly easier. The system can help you make decisions, such as where to add a new server, and advise you
on the best location with the right amount of free space, cooling, power, and redundancy available. !Configuring the room layout^video24x20.jpg!
Watch this [video tutorial|Video Tutorials#capacityplan] to see how to set up a capacity plan. h2. Example We have added some basic equipment
to the server room: a 40 kW UPS, a connected PDU, and 12 racks each with connected rack PDUs. Click [here|Building the infrastructure and
adding inventory] for instructions on adding equipment, and [here|Configuring power connections] for instructions on connecting the equipment.
We have a plan to reserve the load of the 40 kW UPS distributed as follows in the 12 racks: * Network equipment - We plan to position network
equipment in two of the racks. These racks will have low power requirements and we will group them together. * IT equipment - We plan to
distribute the load evenly in the remaining 10 racks for IT equipment and we will group them together. When we subsequently start populating the
racks with servers, the rack advisor will guide us to execute the capacity plan and obtain the optimum data center design.
{column}{column:width=50%} !capacityplan.png|thumbnail! {column}{section} ||See also|| [Capacity Planning - Example] [Working with capacity
groups] [Finding the best location for a new server] [Best Rack Advisor - Redundancy configuration]

Capacity Planning - Example

{excerpt:hidden=false}Capacity groups allow you to place your equipment in groups of racks with similar power capacity requirements to match
the IT equipment with availability needs and avoid stranded space, power, and cooling capacity.{excerpt} An example is a plan that groups 2
racks connected to the same UPS, with the load evenly distributed in both racks. We want to reserve 4 kW load on average for each rack in this
group, and because we do not plan to end up with 4 kW in both racks at all times, we plan for a peak value of 5 kW. {table:border=1|frame=void|}
{table-row} {table-cell:colspan=2|}Example 1 We add 2.5 kW to each rack, and the capacity values look like this: {table-cell} {table-row} {table-row}
{table-cell:} !capacityplan_example1.png|align=center!\\ {table-cell} {table-cell:} !cap_def.png|align=center!\\ The plan for the group is to use 5 kW
(2.5 kW in each rack) out of the available 8 kW in total and there is still 3kW (1.5 kW in each rack) remaining. Buffer = planned peak - (remaining
power + estimated load) Buffer: In this example, the buffer is the same as the difference between the Peak and Average values but that is not
always the case, as illustrated in example 2. In this case, the buffer in both racks: 5 kW - (1.5+2.5 kW) = 1 kW {table-cell} {table-row} {table-row}
{table-cell:colspan=2|}Example 2 Subsequently, we add more load (2 kW) to the one of the racks in this capacity group: {table-cell} {table-row}
{table-row} {table-cell:} !capacityplan_example2.png|align=center!\\ {table-cell} {table-cell:} !r1example.png|align=center!\\
!cap_def_borrowed.png|align=center!\\ The plan is now to use 4.5 kW in one rack (0.5 kW more than is available on average per rack in the
group). That means that this rack needs to borrow the 0.5 kW from the other rack. The plan for the group is to use 7 kW out of the available 8 kW
in total and there is still 1kW remaining. The buffer in the right rack is: 5 kW - (0 + 4.5) = 0.5 kW. The buffer in the left rack would have been: 5 kW
- (1+2.5 kW) = 1.5 kW, but because the right rack uses more power than was planned per rack on average, there is no more power available for
the left rack, and the buffer is set to 0. {table-cell} {table-row}{table} ||See also|| [StruxureWare Operations - Capacity]

Working with capacity groups

Error: The XML content could not be parsed. There is a problem at line 50, column 113. Parser message: Unexpected character '>' (code 62)
expected '=' at [row,col {unknown-source}]: [50,113]

Capacity Group Properties

{excerpt:hidden=false}Use the Capacity Group dialog box, accessed by right-clicking a capacity group or rack in a capacity group and selecting
*Properties*, to define the capacity options for the selected capacity group. {excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Name*
{table-cell} {table-cell:colspan=2|}Identifies the group's name. {table-cell} {table-row} {table-row} {table-cell:} *Color* {table-cell}
{table-cell:colspan=2|}Selects the group's color. {table-cell} {table-row} {table-row} {table-cell:rowspan=2|} *Group Power Options* {table-cell}
{table-cell:} *Power Feed* {table-cell} {table-cell:}Identifies the group's power feed selection. {table-cell} {table-row} {table-row} {table-cell:}
*Internal Redundancy* {table-cell} {table-cell:}Identifies the group's redundancy value. {table-cell} {table-row} {table-row} {table-cell:rowspan=4|}
*Group's Planned Load* {table-cell} {table-cell:} *Peak Load (per rack)* {table-cell} {table-cell:}Identifies the maximum estimated load allowed for
racks included in the capacity group. {table-cell} {table-row} {table-row} {table-cell:} *Average Load (per rack)* {table-cell} {table-cell:}Identifies the
estimated load allowed on average for racks included in the capacity group. Some racks are allowed to draw up to peak value, but this will cause
other racks to be allowed to draw less than the average value. {table-cell} {table-row} {table-row} {table-cell:} *Total Planned Load* {table-cell}
{table-cell:}Identifies the total estimated load of the group if all racks in the group on average draw what is defined as the average value.
{table-cell} {table-row} {table-row} {table-cell:} *Group draw description* {table-cell} {table-cell:}Provides read-only information about the power
density values typed in the above fields. {table-cell} {table-row} {table-row} {table-cell:rowspan=3|} *Advanced Phase Configuration* {table-cell}
{table-cell:colspan=2|}Allows you to review the detailed phase configuration. Typically, you do not need to use these settings, since the system
automatically handles these, except for special cases with custom setups. {table-cell} {table-row} {table-row} {table-cell:} *Peak* / *Recommended
Peak* (per phase) {table-cell} {table-cell:}The peak estimated load value defined per rack in the group is shared among the phases as defined. If
you have a custom setup that is not covered by this standard load distribution on the phases, you can adjust the values. The recommended value
is shown as read-only information. {table-cell} {table-row} {table-row} {table-cell:} *Average* / *Recommended Average* (per phase) {table-cell}
{table-cell:}The average estimated load value defined per rack in the group is shared among the phases as defined. If you have a custom setup
that is not covered by this standard load distribution on the phases, you can adjust the values. The recommended value is shown as read-only
information. {table-cell} {table-row}{table} ||See also|| [Working with capacity groups] [Editing Properties]

Capacity Groups right-click options

{excerpt:hidden=false}Right-click options are available in the *Capacity Groups* pane or for grouped racks in the *Layout* pane. They may not all
be available depending on where you access them.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Remove Capacity Group*
{table-cell} {table-cell:}Deletes a capacity group. {table-cell} {table-row} {table-row} {table-cell:} *Properties* {table-cell} {table-cell:}Opens the
Capacity Group Properties dialog box for the capacity group. {table-cell} {table-row} {table-row} {table-cell:} *Remove from Capacity Group*
{table-cell} {table-cell:}Deletes a rack from its capacity group. {table-cell} {table-row} {table-row} {table-cell:} *New Capacity Group* {table-cell}
{table-cell:}Creates a new capacity group that includes the selected rack only. {table-cell} {table-row} {table-row} {table-cell:} *Add to Capacity
Group* {table-cell} {table-cell:}Adds a rack to a listed group. {table-cell} {table-row}{table}

Finding the best location for a new server

{excerpt:hidden=false}Add or move servers and other equipment to the proposed best location in a rack and U-space by using the options in the
*Rack-Mount Equipment Placement* pane and the *Equipment Placement Advisor* or *Power Details* view of the rack layout.{excerpt} To
provide the system with the best foundation for the calculations, first add appropriate rack PDUs, UPS, and PDUs, set up power paths and
capacity groups. # Select the *Equipment Placement Advisor* or *Power Details* tab at the bottom of the rack layout pane for a color-coded
display of the estimated load per phase in the racks compared to the settings for the capacity group in which the racks are included. # Select a
server in the *Catalog* to add a new server or in the *Navigation* pane to move an existing server in the layout. # Review the equipment
information in the *Rack-Mount Equipment Placement* pane, assign tags, select the required redundancy and network setup, and select amount
to add as required. # Select *Best Rack* to have the system automatically calculate and select the rack and U-position that is best suited for the
new equipment based on the capacity values ({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature). # Click *Show
location* to highlight the best location for the selected equipment in the layout. # Select *Add Equipment* or *Move Equipment* to allow the
system to add or move the equipment to the best location in the layout. The color-coded layout highlights racks as follows: * Green: Optimum
location for the equipment * Yellow: Not optimum but possible location (may result in stranded capacity) * Red: Location violating your setup (may
result in power overload) To investigate why it is not recommended to place equipment in the racks, use the *Placement Status* pane. In addition,
bars below the racks show the load distribution on the phases. \\ {section}{column:width=50%}Color-coded bars in the example illustrate: * How
much kW each rack uses per phase (green in above example). * How much power capacity is available in the rack compared to what has been
designed for racks in the capacity group (from where green ends to the middle value (1,80 in the example). * How much power capacity is allowed
as maximum (light gray in the example). The next step is to install what was designed in the above steps in the real world data center (guided by
work orders through a handheld device, if you have {multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} and
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} installed). {column} {column:width=50%}
!example_racklayoutphasebars.jpg|align=center! {column}{section} ||See also|| [Working with the Equipment Placement Advisor] [Enabling
placement recommendations]

Best Rack Advisor - Redundancy configuration

The table illustrates how to set up the system redundancy options in Capacity Properties for the capacity groups and how this entered data
enables the Equipment Placement Advisor to advise on the best position of a new server based on the redundancy requirements for the server.
See the redundancy acronyms explained [here|Glossary]. || Equipment Placement Advisor \\ \\ \\ Required Redundancy \\ setting for server ||
Capacity Group settings \\ in Capacity Properties \\ \\ Power Feed \\ || Capacity Group settings \\ in Capacity Properties \\ \\ Internal Redundancy \\
|| Capacity Group settings \\ in Capacity Properties \\ \\ Distribution Redundancy \\ || | N | A or B \\ | N \\ | \- \\ | | N+1 | A or B \\ | N+1 | \- \\ | | DN | A
or B \\ | N \\ | \\ | | DN+1 | A or B \\ | N+1 \\ | \\ | | 2N | 2N \\ | N \\ | \- \\ | | 2N+1 | 2N \\ | N+1 \\ | \- \\ | For example, if you have the following capacity
group setup, the rack advisor will guide as follows when adding servers with or without redundancy requirements. You have grouped a range of
racks with this setup: A Feed, no internal redundancy, no distribution redundancy, and grouped another range of racks with this setup: 2N Feed,
N+1 internal redundancy, no distribution redundancy. The Best Rack Advisor will guide you to position servers with no redundancy requirements
in racks in the first group and servers with 2N redundancy requirements in racks in the second group. ||See also|| [Working with the Equipment
Placement Advisor] [Finding the best location for a new server] [Working with capacity groups]

Enabling placement recommendations

{section}{column:width=50%}{excerpt:hidden=false}Information about the selected rack is listed in the *Placement Status* pane to guide you on
available space, power, and cooling as you position equipment in the rack layout. For example, if you are looking for the best rack in which to add
a new piece of equipment, but the system does not advise you to add it to a rack you assume is suited for the equipment, the messages in the
*Placement Status* pane will help you investigate why it is not recommended.{excerpt} Select the *Placement Status* pane below the layout to
see how well a rack meets the requirements of the equipment you want to add. To enable and refresh the recommendations, click a piece of
equipment in *Catalog* (for adding equipment) or *Navigation* (for moving equipment), and then click the rack in which you want to place the
equipment. The LED symbol next to the information identifies the status of the information, see descriptions for each status message.
{column}{column:width=50%}!placementadvisor.jpg|thumbnail!{column}{section} ||See also|| [Available copper-based network ports] [Available
fiber-based network ports] [Capacity group redundancy support] [Capacity group supports equipment's redundancy] [Equipment fits into rack]
[Floor supports weight of equipment] [PDU supports rack PDUs voltage] [Rack airflow supports equipment] [Rack PDU supports equipment's load]
[Rack PDU supports equipment's voltage] [Rack supports equipment's load] [Rack supports equipment's Watts per U-height] [Rack supports
weight of equipment] [Rack tags support equipment tags]

Available copper-based network ports

{set-metadata:_UImapping_}r_placementmsg_copper_support_for_equipment{set-metadata} {excerpt:hidden=false}This status message notifies
you if there is a sufficient amount of copper-based network ports available for the selected equipment in the selected rack.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell} !icon_led_green.gif|align=center!\\ {table-cell} {table-cell}There is a sufficient amount of
available copper ports to support the network requirements of the selected equipment. {table-cell} {table-row} {table-row} {table-cell}
!icon_led_yellow.gif|align=center!\\ {table-cell} {table-cell}There are available copper ports to support some of the network requirements of the
selected equipment but the amount of available ports is insufficient. {table-cell} {table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\
{table-cell} {table-cell}There are no available copper ports to support the network requirements of the selected equipment. {table-cell}
{table-row}{table} \\ {tip:icon=false}*Note*: If you use the network type: other, the placement recommendations may not be reliable since the
advisor does not support network port types that are not defined as either fiber or copper.{tip} ||See also|| [Enabling placement recommendations]

Available fiber-based network ports

{set-metadata:_UImapping_}r_placementmsg_fiber_support_for_equipment{set-metadata} {excerpt:hidden=false}This status message notifies
you if there is a sufficient amount of fiber-based network ports available for the selected equipment in the selected rack.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell} !icon_led_green.gif|align=center!\\ {table-cell} {table-cell}There is a sufficient amount of
available fiber ports to support the network requirements of the selected equipment. {table-cell} {table-row} {table-row} {table-cell}
!icon_led_yellow.gif|align=center!\\ {table-cell} {table-cell}There are available fiber ports to support some of the network requirements of the
selected equipment but the amount of available ports is insufficient. {table-cell} {table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\
{table-cell} {table-cell}There are no available fiber ports to support the network requirements of the selected equipment. {table-cell}
{table-row}{table} \\ {tip:icon=false}*Note*: If you use the network type: other, the placement recommendations may not be reliable since the
advisor does not support network port types that are not defined as either fiber or copper.{tip} ||See also|| [Enabling placement recommendations]

Capacity group redundancy support

{set-metadata:_UImapping_}r_placementmsg_group_support_powerfeed{set-metadata} {excerpt:hidden=false}This status message notifies you if
the redundancy setup for the capacity group is supported in the system.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell}
!icon_led_green.gif|align=center!\\ {table-cell} {table-cell}The redundancy selected for the capacity group is supported by the system. {table-cell}
{table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\ {table-cell} {table-cell}The system does not support mixed redundancy setup.
{table-cell} {table-row}{table} ||See also|| [Enabling placement recommendations]

Capacity group supports equipment's redundancy

{set-metadata:_UImapping_}r_placementmsg_group_support_server_redundancy{set-metadata} {excerpt:hidden=false}This status message
notifies you if the redundancy of the selected equipment adheres to the plan for the selected rack (capacity group setup).{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell} !icon_led_green.gif|align=center!\\ {table-cell} {table-cell}The redundancy planned for the
capacity group supports adding the selected equipment. {table-cell} {table-row} {table-row} {table-cell} !icon_led_yellow.gif|align=center!\\
{table-cell} {table-cell}The capacity plan allows for better redundancy utilization than the selected equipment is designed for. If you add the
selected equipment to this rack, you will not be utilizing the available redundancy to the optimum. {table-cell} {table-row} {table-row} {table-cell}
!icon_led_red.gif|align=center!\\ {table-cell} {table-cell}The selected equipment requires better redundancy setup than is available according to the
redundancy setup for the capacity group. You may need to select a different piece of equipment requiring less redundancy and add to this rack.
{table-cell} {table-row}{table} ||See also|| [Enabling placement recommendations]

Equipment fits into rack

{set-metadata:_UImapping_}r_placementmsg_equipment_fit_into_rack{set-metadata} {excerpt:hidden=false}This status message notifies you if
there is sufficient space available in the selected rack.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell}
!icon_led_green.gif|align=center!\\ {table-cell} {table-cell}There is sufficient space in the selected rack for the selected piece of equipment.
{table-cell} {table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\ {table-cell} {table-cell}There is insufficient space in the selected rack
for the selected piece of equipment. {table-cell} {table-row}{table} ||See also|| [Enabling placement recommendations]

Floor supports weight of equipment

{set-metadata:_UImapping_}r_placementmsg_floor_support_weight{set-metadata} {excerpt:hidden=false}This status message notifies you if the
floor's carrying capability supports the weight of the selected equipment.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell}
!icon_led_green.gif|align=center!\\ {table-cell} {table-cell}The floor has sufficient carrying capability to support the weight of the selected piece of
equipment. {table-cell} {table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\ {table-cell} {table-cell}The floor has insufficient carrying
capability to support the selected piece of equipment. {table-cell} {table-row}{table} ||See also|| [Enabling placement recommendations]

PDU supports rack PDUs voltage

{set-metadata:_UImapping_}r_placementmsg_pdu_support_rpdu_voltage{set-metadata} {excerpt:hidden=false}This status message notifies you if
the connected PDU is capable of supplying the voltage needed by the rack PDU.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell}
!icon_led_green.gif|align=center!\\ {table-cell} {table-cell}The defined output voltage of the connected PDU and rack PDU is supported. {table-cell}

{table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\ {table-cell} {table-cell}The defined output voltage of the connected PDU and
rack PDU is not supported. You may need to select another PDU or rack PDU for this power connection, or change the properties of either
component if these are incorrect. {table-cell} {table-row}{table} ||See also|| [Enabling placement recommendations]

Rack airflow supports equipment

{set-metadata:_UImapping_}r_placementmsg_rack_support_airflow_server{set-metadata} {excerpt:hidden=false}This status message notifies you
if there is sufficient cooling available for the selected equipment in the rack.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell}
!icon_led_green.gif|align=center!\\ {table-cell} {table-cell}There is sufficient cooling available to support adding the selected equipment to the
selected rack since all or nearly all of the rack's exhaust airflow will be captured. {table-cell} {table-row} {table-row} {table-cell}
!icon_led_yellow.gif|align=center!\\ {table-cell} {table-cell}There is sufficient cooling available to support adding the selected equipment to the
selected rack but not all of the rack's exhaust airflow will be captured. {table-cell} {table-row} {table-row} {table-cell}
!icon_led_red.gif|align=center!\\ {table-cell} {table-cell}There is insufficient cooling available to support adding the selected equipment to the
selected rack since too little of the rack's exhaust airflow will be captured. {table-cell} {table-row}{table} ||See also|| [Enabling placement
recommendations]

Rack PDU supports equipment's load

{set-metadata:_UImapping_}r_placementmsg_rmpdu_support_server_powerdraw{set-metadata} {excerpt:hidden=false}This status message
notifies you if the connected rack PDU is capable of supplying the power needed by the equipment.{excerpt} {table:border=1|frame=box|}
{table-row} {table-cell} !icon_led_green.gif|align=center!\\ {table-cell} {table-cell}The rack PDU supports the needed power supply to the selected
equipment. {table-cell} {table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\ {table-cell} {table-cell}The rack PDU does not support
the needed power supply to the selected equipment. You may need to select another rack PDU or equipment, or change the breaker settings if
these are incorrect, to keep within the physical boundaries of the rack PDU breaker. {table-cell} {table-row}{table} ||See also|| [Enabling placement
recommendations]

Rack PDU supports equipment's voltage

{set-metadata:_UImapping_}r_placementmsg_rmpdu_support_server_voltage{set-metadata} {excerpt:hidden=false}This status message notifies
you if the connected rack PDU is capable of supplying if the voltage needed by the equipment.{excerpt} {table:border=1|frame=box|} {table-row}
{table-cell} !icon_led_green.gif|align=center!\\ {table-cell} {table-cell}The rack PDU supports the voltage needed by the selected equipment.
{table-cell} {table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\ {table-cell} {table-cell}The rack PDU does not support the voltage
needed by the selected equipment. You may need to select another rack PDU or equipment, or change the voltage settings if these are incorrect.
{table-cell} {table-row}{table} ||See also|| [Enabling placement recommendations]

Rack supports equipment's load

{set-metadata:_UImapping_}r_placementmsg_rack_max_capacity_support_server{set-metadata} {excerpt:hidden=false}This status message
notifies you if there is sufficient remaining power in the rack to supply the power that is required to the selected equipment.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell} !icon_led_green.gif|align=center!\\ {table-cell} {table-cell}There is sufficient remaining power
left for adding the selected equipment to the selected rack as planned per rack in the capacity group. {table-cell} {table-row} {table-row} {table-cell}
!icon_led_yellow.gif|align=center!\\ {table-cell} {table-cell}There is sufficient remaining power left for adding the selected equipment to the selected
rack. However, in this rack, you are exceeding the average value planned per rack in the capacity group, and you may need to add
correspondingly less load to one or more racks in the capacity group. {table-cell} {table-row} {table-row} {table-cell}
!icon_led_red.gif|align=center!\\ {table-cell} {table-cell}There is insufficient capacity available for adding the selected equipment to the selected
rack. You have exceeded the planned *Power Buffer* value. You may need to move or remove equipment in order to keep within the plan. If you
are working with 3 phase equipment, this will be a problem even if the load is only too high for one of the phases. {table-cell} {table-row}{table}
||See also|| [Enabling placement recommendations]

Rack supports equipment's Watts per U-height

{set-metadata:_UImapping_}r_placementmsg_rack_support_server_wattper_uheight{set-metadata} \\ {excerpt:hidden=false}This status message
notifies you if you utilize the remaining power of the rack if you keep filling it up with more pieces of the selected equipment.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell} !icon_led_green.gif|align=center!\\ {table-cell} {table-cell}The rack supports continuing to fill up
the rack with more pieces of the selected equipment as the sum of the estimated load per U-height will not leave unutilized capacity in the rack.
{table-cell} {table-row} {table-row} {table-cell} !icon_led_yellow.gif|align=center!\\ {table-cell} {table-cell}The rack does not support continuing to
add more pieces of the selected equipment. You may need to select another rack or piece of equipment, or change the watt settings if these are
incorrect, to keep within the physical boundaries of the rack. {table-cell} {table-row}{table} ||See also|| [Enabling placement recommendations]

Rack supports weight of equipment

{set-metadata:_UImapping_}r_placementmsg_rack_support_weight{set-metadata} {excerpt:hidden=false}This status message notifies you if the
rack's carrying capability supports the weight of the selected equipment.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell}
!icon_led_green.gif|align=center!\\ {table-cell} {table-cell}The selected rack has sufficient carrying capability to support the weight of the selected
piece of equipment. {table-cell} {table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\ {table-cell} {table-cell}The selected rack has
insufficient carrying capability to support the selected piece of equipment. {table-cell} {table-row}{table} ||See also|| [Enabling placement
recommendations]

Rack tags support equipment tags

{set-metadata:_UImapping_}r_placementmsg_rack_support_keyword_for_equipment{set-metadata} {excerpt:hidden=false}This status message
notifies you if there is a match between any tags assigned to the rack and tags assigned to the selected equipment.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell} !icon_led_green.gif|align=center!\\ {table-cell} {table-cell}Tags assigned to the selected rack
and equipment are consistent. {table-cell} {table-row} {table-row} {table-cell} !icon_led_yellow.gif|align=center!\\ {table-cell} {table-cell}There is an
inconsistency between the tags assigned to the selected rack and equipment. You may need to select another rack or piece of equipment, or
change the assigned tags on either rack or equipment if these are incorrect. {table-cell} {table-row} {table-row} {table-cell}!Attachment
Library^icon_led_red.gif|align=center!\\ {table-cell} {table-cell} There is an inconsistency between the tags assigned to the selected rack and
equipment. You must select another rack or piece of equipment, or change the assigned tags on either rack or equipment if these are incorrect. If
you do not want matching tags to be a strict requirement, you can change this setting in the tag setup. {table-cell}\\ {table-row}\\ {table} ||See also||
[Enabling placement recommendations]

Working with Tags

{section}{column:width=50%}{excerpt:hidden=false}Tags can be created and assigned to equipment in the floor or rack layout to categorize types
of equipment.{excerpt} For example, if you have tagged a server before adding it to the layout, the system can better guide you where to place it
and any other future servers of this kind when using the Add Equipment to Best rack functionality in the *Rack-Mount Equipment Placement*
pane. {tip:icon=false}*Note*: Tags must be created in *Tools>Configure Tags* before they become available in the application and can be
assigned to equipment in the floor and rack layout. The configuration includes an option to make matching tags a strict requirement when adding
a server to a rack.{tip} {column}{column:width=50%} !Attachment Library^tags.png|thumbnail!{column}{section} || 123 Steps to... || See also ||
|*Assigning tags* \\ Tags can be assigned to equipment in the floor or rack layout to categorize types of equipment and plan the best place for
new equipment automatically calculated based on the type of equipment. # Right-click on a piece of equipment e.g. a server and select
*Properties*. # In the Properties dialog box, select the *Tags* section. # Select *Add* or *Remove* to assign a tag or annul an assignment. #
Repeat previous step(s) until all required tags have been assigned. When used in the Rack Layout with the *Rack Equipment placement* pane to
find the best place for equipment, tags help you place e.g. servers used by Financial together to optimize use of the remaining power.|[Creating
tags]\\ [Managing tags in the Equipment Browser or List View]\\ [Tag Properties]|

Creating tags
{excerpt:hidden=false}Tags can be created in the Configure Tags dialog box accessed from *Tools* *> Configure Tags*. When tags have been
created, they are subsequently available in the application to be assigned to equipment in the floor and rack layout.{excerpt} # In the Configure
Tags dialog box, select *Add* to create new tags or categories. # Select if the tag is a strict requirement that must be met to be able to add a
piece of equipment to a rack*. # Select a tag from the list and select *Up* or *Down* to move it and create a hierarchical structure according to
your preferences. # If necessary, select a tag or category from the list and select *Edit* to modify it. # If necessary, select a tag or category from
the list and select *Remove* to delete it from the list. *This setting controls the behavior of the Add to best rack feature. If you select that a
matching tag is a strict requirement, the tag assigned to a piece of equipment must match the tag assigned to the rack to which you are adding it.
The placement status message: Rack tags support equipment tags will show with a red LED symbol next to it. If you select that a matching tag is
not a strict requirement, the tag assigned to a piece of equipment does not have to match the tag assigned to the rack, but it is recommended that
it does. The placement status message will show with a yellow LED symbol next to it. ||See also|| [Working with tags]

Managing tags in the Equipment Browser or List View

{excerpt:hidden=false}Tags can be assigned to individual equipment or to a selection of equipment in a variety of ways. One of these involves
editing categories and tag assignments for any number of items in the system through a table view.{excerpt} The tags must be created in the
system before they become available for use, and the table view includes the tag columns as set up in the column configuration. The *Category*
columns each shows all tags within that category; the *Tag* columns each shows an assigned tag; the *Tags* column lists all tags assigned. To
access the edit functionality in the tag columns, double-click an item in the columns and click the ... icon or drop-down box. # To add or remove
the tags assigned to an item, double-click the item in the *Tags* column, click the ... icon, and select or deselect the available tags. You can add
or remove all tags available in all categories. # To add or remove the tags of a specific category assigned to an item, double-click the item in that
*Category* column, and select or deselect the available tags. # To add or remove a specific tag assigned to an item, double-click the item in that
*Tag* column, and select *Yes* or *No* to select or deselect the available tag. Alternatively, you can edit the tag assignments in the *Edit Multiple
Items* dialog box. \\ {tip:icon=false}*Note*: When you remove tag assignments, they are still available in the system for future use. If you want to
remove a tag from the system, use the *Configure Tags* dialog box.{tip} ||See also|| [Working with Tags]

Tag Properties
{excerpt:hidden=false}This section of the Properties dialog box lists tags associated with a component, e.g. a rack or server.
{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Name* {table-cell} {table-cell:}Defines the tag name. {table-cell} {table-row}
{table-row} {table-cell:} *Description* {table-cell} {table-cell:}Defines the value the tag provides. {table-cell} {table-row} {table}
{tip:icon=false}*Note*: The listed information is defined by added tags in the Select Tags dialog box that are accessed by the *Add* button;
*Remove* allows you to remove any listed tag.{tip} ||See also|| [Working with Tags]

Saving KPIs over time

{section}{column:width=50%}{excerpt:hidden=false}In *Tools>Preferences>Capacity History*, you can set up the system to collect and save Key
Performance Indicators (KPIs) for a specified period of time. This is a {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true}
feature. \\ \\ Once you have configured how often you want the system to collect the data, and for how long you want it to be saved, the system
stores the data on the server and makes it possible for you to access and analyze critical data over time. You can use the data for creating
custom trending reports, display on the dashboard and integrate with external systems through web services. Read instructions on granting
access to web service APIs [here|Granting access to web services API] or read about the web service API [here|StruxureWare Operations Web
Service API]. {excerpt} For example, a standard built-in report allows you to create a report with the current amount of available U-positions in one
or more data centers. However, you may want to know the development over time in available u-space. The saved KPI data allows you to access
this data. {column}{column:width=50%} !capacityhistory.png|thumbnail! {column}{section} || 123 Steps to... || See also || | *Setting up the system to
save KPI data* \\ \\ In *Tools>Preferences>Capacity History*, define the KPI data recordings. \\ # In *Record data*, select the interval between the
recordings, e.g. *Daily*. # In *Clear data*, select the interval between clearing the data, e.g. *After 1 year*, or select *Never* to keep storing the
data indefinitely. \\ You can start using the data for a trending report after a while (more than one day). \\ \\ *Creating a trending report* \\ In
*Analytics>Reports*, select *Capacity History* in the list of available reports and define the filter options. 1. Select a rack and a *Date Range*, for
example the last week. 2. Select to include the data type, for example *Available U-space*, and click to generate the report. The capacity history
trending report shows with a graph of the amount of available U-positions per day in the *Report View* and can be printed or exported. \\ \\
{tip:icon=false}*Tip*: If you are planning to reuse the same selections, e.g. for a monthly report showing the development in space capacity, click
the *Save Filter As* icon and name the report template, e.g. Monthly U-space, to have it preset and ready for you to push the generate button
once a month.{tip} \\ \\ *Exporting capacity history* \\ When you have generated a report, you can export and use the data in other applications,
e.g. Excel or .csv format by clicking the Export icon at the top of the report view. | [Working with reports] [Working with report filter templates]
[Customizing report designs] [StruxureWare Operations - Dashboard] |

Simulating IT Impact
{section}{column:width=50%}{excerpt:hidden=false}The IT Impact simulation provides an indication of issues or potential issues with the active
power and cooling configuration in the event of a failure. {excerpt} The IT Impact simulation can be accessed by right-clicking a piece of

equipment in the Floor Layout (1). You can use the IT Impact option to simulate a failure to determine whether the design is strong enough to fit
the requirements of the real-world infrastructure, for example: * If a selected UPS was to fail, what connected equipment would be impacted and
lose the power supply or redundancy due to the failure (2). * If a selected cooling unit was to fail, what surrounding equipment would be impacted
and overheating or losing redundancy due to the failure. Simulated impact of cooling failure is based on calculated inlet temperature for individual
racks compared to the maximum target inlet temperature for the room. If the first value exceeds the latter, the impact will show as overheating all
equipment in the rack. The calculated inlet temperature for an individual rack can be seen by selecting the *Cooling* tab in the Floor Layout, and
hovering over the rack to see the tool tip. The inlet temperature is calculated as the high-level average inlet temperature for the rack. The
calculations are not detailed enough to specify the temperature more precisely, such as floor, middle, or top of the rack. In addition, the generic
cooling prerequisites, assumptions, and design guidelines apply. {tip:icon=false}*Note*: The simulation is only as accurate as the source
information (the data provided in the data center model). A simulation, although a helpful and informative tool, may not be accurate and only
shows eventual real effects.{tip} {column}{column:width=50%} !simulateimpact.png|thumbnail! !UPSfailtable.png|thumbnail! {column}{section} ||
123 Steps to... || See also || | *Viewing the IT impact of a failing piece of equipment* \\ # Select a piece of equipment in the *Floor Layout* that: #*
Supplies power to other equipment in the layout, for example a UPS or PDU. #* Supplies cooling to other equipment in the layout, for example a
row-based cooling unit. # Right-click it, and select *Simulate Impact* to simulate failure and see the impact. \\ In the *Simulated Impact* table, the
equipment that would be impacted is listed. The *Status (Live)* field is used for equipment that is associated with live devices and indicates the
device status: OK, Failure, Critical, Error, Warning, Informational. \\ \\ {tip:icon=false}*Note*: If a piece of equipment has not been associated with
a device, it will show as OK.{tip} \\ *Viewing the IT impact of an active alarm* \\ 1. Select an alarm in the *Alarms* pane below the layout (available
when *Operations* is selected in the Application bar). 2. Right-click it, and select *Simulate Impact* to see the impact if the live device that is
reporting the alarm would fail. \\ A list of equipment in the data center model that would be affected by the simulated failure pops up, including a
description about what type of impact the failure would have, such as power loss, or power redundancy loss. \\ | [Filtering Simulated Impact List
(Search)|Filtering Simulated Impact List (Search)] \\ [Exporting Impact Table] \\ [Configuring Simulated Impact Layout] \\ [Configuring Cooling
Impact Preferences] \\ [StruxureWare Operations - Capacity|StruxureWare Operations - Capacity] \\ |

Configuring Cooling Impact Preferences

{excerpt:hidden=false}You can configure the thresholds for impact so the system reacts to impacts that are important to your physical
infrastructure. {excerpt}Together with a virtual host configuration, the impact analysis on virtual machine hosts feature can be used to put
impacted hosts in maintenance mode, preventing failure. The IT impact simulation enables you to simulate the effect of potential power or cooling
failures. You can define custom criteria for when a server is marked as impacted in the system. # Select *Tools* *> Preferences* *> Cooling
Impact*. # Edit the value of the *Maximum Inlet Temperature* to modify the temperature thresholds of the impact. As long as a cooling failure
does not cause the temperature to exceed the configured threshold, virtual servers will not be migrated in response to the failure. Simulating
impact of a potential failure also behaves in the same way. {tip:icon=false}*Note*: If you select *No limit*, the system will not react to cooling
impact.{tip} ||See also|| [Simulating IT Impact] [Filtering Simulated Impact List (Search)] [Exporting Impact Table] [Configuring Simulated Impact
Layout]

Configuring Simulated Impact Layout

{excerpt:hidden=false}You can configure the layout of the Simulated Impact list to show equipment according to your preferences.{excerpt} * Click
*Configure Columns* and select which columns to show. * Edit the column width: ** Drag the boundary of a column header to the required
position. ** Double-click the boundary of a column header to make the column width fit to contents. Drag and drop columns in the list to move
columns. * Click on a column header in the list to sort on this column. \\ An arrow on the header indicates the sort order (ascending/descending). *
Click on column header in the list to toggle sort order (ascending/descending). {tip:icon=false}*Note*: The simulation is only as accurate as the
source information (the data provided in the data center model). A simulation, although a helpful and informative tool, may not be accurate and
only shows eventual real effects.{tip} ||See also|| [Simulating IT Impact] [Filtering Simulated Impact List (Search)] [Exporting Impact Table]
[Configuring Cooling Impact Preferences]

Exporting Impact Table

{excerpt:hidden=false}You can export the list of impacted equipment to a file.{excerpt} # Click *Export*. # Select file format and browse to identify
the destination where you want the file sent, and click *OK* to execute the export and exit the dialog. ## If you want to export more equipment
data than is currently shown in the list, select to include filtered out equipment and/or hidden columns. {tip:icon=false}*Note*: The simulation is
only as accurate as the source information (the data provided in the data center model). A simulation, although a helpful and informative tool, may
not be accurate and only shows eventual real effects.{tip} ||See also|| [Simulating IT Impact] [Filtering Simulated Impact List (Search)] [Configuring
Simulated Impact Layout] [Configuring Cooling Impact Preferences]

Filtering Simulated Impact List (Search)

{excerpt:hidden=false}You can set a filter on the Simulated Impact list to show only the equipment that you want to see.{excerpt} # In the
drop-down list, select a column to only search for equipment in this column or keep the default value *All columns*. # In the *Search* box, start
typing some characters of the equipment you want to see. As you type, the pane shows all items that contain the typed characters in the column
that is selected. {tip:icon=false}*Note*: The simulation is only as accurate as the source information (the data provided in the data center model).
A simulation, although a helpful and informative tool, may not be accurate and only shows eventual real effects.{tip} ||See also|| [Simulating IT
Impact] [Exporting Impact Table] [Configuring Simulated Impact Layout] [Configuring Cooling Impact Preferences]

Performing an impact analysis on virtual machine hosts

{excerpt:hidden=false}If the system has been set up to support this feature, the impact analysis data helps you manage and migrate virtual
machines running on devices connected to failing physical equipment to healthy hosts in order to prevent impact. {excerpt} This feature requires a
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license and prior installation and configuration of the communication to a
supported virtual machine management system: * Microsoft System Center Operations Manager and Microsoft Virtual Machine Manager (in the
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true}) For further information about prerequisites for enabling this feature,
select [{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true}|StruxureWare Operations - PRO Pack] in the navigation menu.
* VMware vCenter Server You can enable this feature by setting up the server communication in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} *System Setup>External System Configuration*. If you connect to more
than 5 vCenter servers, you may experience a performance decrease with the server communication. For each host for which you want to enable
impact, you must set the properties to include it in the impact analysis. Otherwise it will not show as impacted and the virtual machine
management system will not be notified of an impact on the host and enable migration. The impact analysis data is available in the rack layout in

*Data Center Planning* and as read-only information in *Data Center Operations*. You configure the position of your host servers in the data
center layout and associate the servers with your virtual servers. In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, a
number of alarms are considered crucial to the continuous operation of the virtual machines. If you have associated a host to a server in the
layout that is affected by one of the following scenarios, the system will notify the virtual machine management system of an impact on the host
that should be migrated: * A power supply with an alarm that could lead to imminent power loss, e.g. a UPS is failing or running low on battery * A
cooling unit with an alarm that could lead to a server overheating, e.g. a cooling unit's compressor or power supply is failing The associated host
will be marked as critically impacted (red icon). * In Microsoft Virtual Machine Manager, the location and impact data from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} will be available via the generated PRO tip, allowing the Virtual Machine
Manager administrator to configure automatic migration to a healthy location of the virtual machine servers marked as impacted. * In VMware
vCenter Server, the impacted hosts will be put into maintenance mode. For further information, refer to the VMware documentation. However, an
alarm that occurs on one of the power supplies in a redundant power supply setup is considered a non-critical impact and the associated host will
be marked as non-critically impacted (yellow icon). * No PRO tip will be generated from this type of impact in Virtual Machine Manager and no
servers will be migrated. * No data will be communicated from this type of impact to the vCenter Server and no servers will be migrated. By
default, the system supports [the standard critical alarm types|StruxureWare Operations - PRO Pack Supported Alarm Types]. However, it is
possible to customize the critical alarm and threshold configuration for migration of impacted servers. ||See also|| [Enabling Impact Analysis with a
VMware vCenter Server setup] [Locating virtual machines hosts with impact in the layout] [Refreshing Virtual Machine Host data] [Removing the
maintenance mode on a host with a VMware vCenter Server setup] [Virtual Machine Host Properties] [Working with virtualization]

Enabling Impact Analysis with a VMware vCenter Server setup

{excerpt:hidden=false}The impact analysis data helps you manage and migrate virtual machines running on devices connected to failing physical
equipment to healthy hosts in order to prevent impact. To enable impact analysis with a VMware vCenter Server setup, you must define the
server communication preferences between {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and VMware vCenter Server.
{excerpt} # Ensure you have the necessary user rights on the VMware vSphere Client. # In *System Setup>External System Configuration*,
configure the server communication settings to allow {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to exchange data with
the VMware environment. ## Click *Add server* to type the logon information of the new vCenter Server to connect to: hostname/IP address, port
number, and user credentials. If you connect to more than 5 vCenter servers, you may experience a performance decrease with the server
communication. ## For a high-security logon session, select *Use SSL* and accept the certificate. Ask the vCenter Server administrator for details
if you are unsure whether to use SSL. {tip:icon=false}*Recommendation*: If the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server is restarted, wait for several minutes before you make any
changes to the vCenter communication configuration.{tip} Once you have set up this server communication,
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} displays virtual machine host data from the VMware vCenter Server which,
in return, receives data from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} on the physical location of virtual machine
hosts. For each host for which you want to enable impact, you must set the properties to include it in the impact analysis. Otherwise, it will not
show as impacted and the virtual machine management system will not be notified of an impact on the host and enable migration. The option is
available by right-clicking the virtual machine host, and selecting *> Properties* *> Virtual Machine Host*. ||See also|| [Performing an impact
analysis on virtual machine hosts] [Working with virtualization] [Locating virtual machines hosts with impact in the layout] [Refreshing Virtual
Machine Host data] [Removing the maintenance mode on a host with a VMware vCenter Server setup] [Virtual Machine Host Properties]
[Configuring external system integration] [Viewing external system data]

Locating virtual machines hosts with impact in the layout

{excerpt:hidden=false}When configured, the system shows virtual machine hosts in the layout that have been associated with potentially failing
equipment, e.g. a UPS, PDU, or rack PDU. {excerpt} 1. View impact on virtual machine hosts in the layout by selecting the *Rack Layout* icon,
and clicking e.g. the *Power Details* tab to see the associated hosts highlighted on the modeled servers in the layout. !error_impact.JPG! Red
icon: Critically impacted virtual machine host. For example, if a critical alarm occurs on the power supply. !warning_impact.JPG! Yellow icon:
Non-critically impacted virtual machine host. For example, if a critical alarm occurs on one of the power supplies in a redundant power supply
setup. !no_impact.JPG! Gray icon: Non-impacted virtual machine host. {tip:icon=false}*Note*: If you have set up the tool tips to include this
information (in *> Tools* *> Preferences* *> Tool Tips*), Virtual machine host data will be shown when you hover over a virtual machine host icon
in the rack layout.{tip} 2. Locate a specific impacted virtual machine host in the layout. a. Double-click the room in *Navigation*. b. Right-click the
virtual machine host in the *External Systems* pane, and select *Show in Navigation* or *Show in Editor* to identify and highlight the server in the
rack layout with the associated host. ||See also|| [Working with virtualization] [Performing an impact analysis on virtual machine hosts] [Enabling
Impact Analysis with a VMware vCenter Server setup] [Locating virtual machines hosts with impact in the layout] [Refreshing Virtual Machine Host
data] [Removing the maintenance mode on a host with a VMware vCenter Server setup] [Virtual Machine Host Properties]

Refreshing Virtual Machine Host data

{excerpt:hidden=false}For configurations with data communication between {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}
and VMware vCenter Server, the host data refreshes dynamically. For configurations with data communication between
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and Microsoft Virtual Machine Manager, the data is refreshed at the
configured frequency.{excerpt} The {multi-excerpt-include:pageTitle=Branding|name=ISXOPROAgent|nopanel=true} ensures the data from the
Virtual Machine Manager server is updated at the configured frequency, e.g. every 10 minutes (minimum). The agent is installed with the
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} . You will see an icon on the task bar when the agent is running. #
Open the agent window by right-clicking the icon on the task bar and selecting Show (or if the agent is disabled, restart it through *Start* *> All
Programs* *> Startup* *> StruxureWare Operations PRO Pack*). # Define the interval of getting updated data from Virtual Machine Manager into
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} . Updates include: * Virtual machine hosts: Addition/removal, switch
between maintenance/normal mode * Virtual machines: Addition/move/deletion ||See also|| [Performing an impact analysis on virtual machine
hosts] [Working with virtualization] [Enabling Impact Analysis with a VMware vCenter Server setup] [Locating virtual machines hosts with impact in
the layout] [Removing the maintenance mode on a host with a VMware vCenter Server setup] [Virtual Machine Host Properties]

Removing the maintenance mode on a host with a VMware vCenter Server setup
{excerpt:hidden=false}You can remove the maintenance mode on a host that was critically impacted by an alarm in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} after the impact has been resolved. {excerpt}This can be done when
working in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} as well as in the VMware environment. To remove the
maintenance mode on a host in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: # In the *External Systems* pane, identify

the host that used to be critically impacted but is now safe. It is marked as in maintenance mode and is highlighted on the modeled servers in the
layout with a yellow or gray V icon (used to be red), and it is marked as in maintenance mode. # Right-click the virtual machine host in the
*External Systems* pane, and select *Exit Maintenance Mode* to remove the maintenance mode on the host. For information on how it is done in
the VMware environment, refer to the VMware documentation. ||See also|| [Performing an impact analysis on virtual machine hosts] [Working with
virtualization] [Enabling Impact Analysis with a VMware vCenter Server setup] [Locating virtual machines hosts with impact in the layout]
[Refreshing Virtual Machine Host data] [Virtual Machine Host Properties]

Virtual Machine Host Properties

{excerpt:hidden=false}Relevant properties, accessed by right-clicking a Virtual Machine Host in *Virtual Machine Hosts*, are displayed for the
selected host server as read-only information. The information may vary based on the type of equipment and can contain information about the
virtual machines running on that host. The check box enables the impact analysis feature for this host.{excerpt} ||See also|| [Performing an impact
analysis on virtual machine hosts] [Working with virtualization] [Enabling Impact Analysis with a VMware vCenter Server setup] [Locating virtual
machines hosts with impact in the layout] [Refreshing Virtual Machine Host data] [Removing the maintenance mode on a host with a VMware
vCenter Server setup]

Working with virtualization

{section}{column:width=50%}{excerpt:hidden=false}The *External Systems* pane lists the virtual machine hosts monitored by the supported
virtual machine management systems. {excerpt} The virtual machine hosts will appear in groups according to the setup in the virtual machine
management system. If you have set up your system to retrieve data from multiple servers, the virtual machine hosts will be grouped by the name
of these servers. {tip:icon=false}*Note*: The host groups and clusters shown in Virtual Machine Manager / vCenter Server are not shown in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.{tip} A virtual machine host appears as not associated (!server.JPG!) in the
*External Systems* pane until it has been associated with the device in representing it in the layout, for example a server. Then, it will appear as
associated (!server_link.JPG!). The *External Systems* pane has a dynamic *Search* box. In the *Search* box, start typing some characters of
the hosts you want to see. As you type, the pane shows all items that contain the typed characters. You can apply a filter to display only hosts that
match your selected criteria. * !servers.JPG! All * !server_link.JPG! Associated * !server.JPG! Not associated You can navigate to an associated
server represented in the rack layout by right-clicking the host in the *External Systems* pane and selecting *Show in Editor*, or double-clicking it,
or navigate to it in the *Navigation* pane by right-clicking and selecting *Show in Navigation*. {column}{column:width=50%}
!vmimpact.png|thumbnail! {column}{section} || 123 Steps to... || See also || | *Associating virtual machine hosts with servers in the layout* \\ \\
When monitored virtual machine hosts are associated with the corresponding servers representing them in the rack layout, the data supports
continual operation of the virtual machines running in the data center. \\ # To associate any of the unassociated virtual machine hosts with the
server that represents it in the data center model's rack layout, drag-and-drop the hosts from the *External Systems* pane into position over the
corresponding servers in the rack layout. To ensure that the retrieved values for the monitored virtual machine hosts are reliable and based on the
correct data, you can test that the server communication is running and that the setup is correct in Virtual Machine Manager or vCenter Server. #
To remove the association between a virtual machine host and the model object representing it in the rack layout, right-click the host in the
*External Systems* pane, and select *Unassociate Virtual Machine Host Server*. \\ | [Performing an impact analysis on virtual machine hosts] \\
[Enabling Impact Analysis with a VMware vCenter Server setup] \\ [Locating virtual machines hosts with impact in the layout] \\ [Refreshing Virtual
Machine Host data] \\ [Removing the maintenance mode on a host with a VMware vCenter Server setup] \\ [Virtual Machine Host Properties] \\ |

Capacity reports
{section}{column:width=50%}{excerpt:hidden=false}You can generate capacity reports showing an overview of the capacity and capacity over
time.{excerpt} h2. Power Capacity report You can generate a report with power data, i.e. available estimated load and planned estimated load. h2.
Capacity History report You can generate a report with a graph showing capacity data from a specified time period, e.g. the total load of all
connected equipment (calculated by the system) or the measured peak load on the UPS devices (actual measured data form associated UPS
devices). The Capacity History report is available if you have a valid {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true}
license. {tip:icon=false}*Note*: The report is based on data collected over the last 24 hours, so the server must have been running for at least 24
hours.{tip} When you select the report filter options, select what is appropriate according to the data types. For example, when you are generating
a report of available U-space, select a rack (not a UPS), and for a report of measured peak load, select a UPS (not a rack). The generated report
displays in the *Report View*. You can now use the *Report View* toolbar to navigate the report pages on the screen (arrow icons), or to print or
export the report to a file in any of the available formats (*Export* icon, down arrow for selection of format). {column}{column:width=50%}
!report_capacityhistory.png|thumbnail! {column}{section} ||See also|| [Working with reports]

Branch Circuit Monitoring

You must have a valid {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license to be able to configure Branch Circuit
Monitoring. h2. Rack PDU level or PDU level power data You can configure retrieval of power measurements from a rack in one of the following
ways: * Configure power distribution, retrieving measured values at rack PDU level * Configure power distribution, retrieving measured values at
PDU, RDP, or PP level through Branch Circuit Monitoring The system works with the same measurements regardless of method. A PDU breaker
module number in the *Power Distribution Properties* connects the PDU modules with the rack PDUs and allows the system to retrieve the rack
PDU level data. This means that all functions in the system using the power measurements (for example, capacity calculations and
recommendations) work as if you had configured measured values at rack PDU level even if these values are really retrieved at PDU, RDP, or PP
level through Branch Circuit Monitoring. h2. Modular or non-modular power distribution When configuring Branch Circuit Monitoring, you configure
the PDU breaker module number whether the power distribution is modular or not. The number is necessary for the system's power data
configuration, even though there are no breaker modules in the physical non-modular PDU. *Modular power distribution* The Branch Circuit
Monitoring configuration for modular PDUs is supported from {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} version 7.1.
!props_powerdistr_highlighted.png|thumbnail! *Breaker Module Number*: In this field, you type the module number per line to configure the
connections to the rack PDUs. You can edit this field for a new or existing line by clicking *New* or *Edit*. *Measured Peak Power*: When
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} integration has been configured, and the system starts retrieving
measurements, this field will automatically be populated with measurements. *Non-modular power distribution*
!deviceprops_sensormapping.png|thumbnail! For non-modular distribution, you fill in the sensor mapping per breaker in the *Sensor Mapping*
table, including information about phase, breaker module number, and multiplier. The *Multiplier* value is used to convert the unit of measurement
for the device type into Watts. h2. Collecting multiple measurements for one component in the floor layout In the non-physical representation in
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}, a physical PDU, RDP, or PP is represented as multiple measurement
points (devices). In the physical representation in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, a physical PDU, RDP, or

PP is represented in the layout as one component and, normally, one device from an external system is associated with one component in the
layout. However, if the physical and non-physical representations do not match, you can drag and drop sensors from multiple devices in *External
Systems* to one PDU, RDP, or PP in the layout. ||See also|| [Configuring Branch Circuit Monitoring] [Working with Branch Circuit Monitoring]

Configuring Branch Circuit Monitoring

{section}{column:width=50%}In a Branch Circuit Monitoring configuration, the system works as if you had configured power measurements at rack
PDU level, only these measurements are really retrieved at PDU, RDP, or PP level. You must have a valid
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license to configure Branch Circuit Monitoring. *Modular power
distribution* If your data center configuration includes modular power distribution, configure the connection between the power breaker modules
and the rack PDUs (Figure 1). # Right-click a modular PDU in the layout, and select *Properties*. # In the *Power Distribution* page, select output
voltage and select *New* to configure the connection to the rack PDU. Remember to fill in the *Module number*. # Repeat the above step until all
connections have been configured between the power breaker modules and the rack PDUs. # Associate the corresponding PDU device to the
PDU in the floor layout by dragging it from *External Systems* to the PDU in the layout. *Non-modular power distribution* If your data center
configuration includes non-modular power distribution, still configure the connection between rack PDUs and a PDU, RDP, or PP using a breaker
module number, even though there are no breaker modules in the physical PDU. # Right-click a power distribution device (PDU, RDP, or PP) in
*External Systems*, and select *Properties*. You are not required to associate the device to a component in the layout yet. # This step is only for
non-modular distribution (Figure 2): In the *Sensor Mapping* page, fill in the sensor mapping per breaker. #* Phase #* Breaker module number #*
Multiplier The *Multiplier* value converts the unit of measurement for the device type into Watts. The *Total* values must be in Watts. For
example, if the measured values are in kW, type 1,000, or if the measured values are in A, type the factor to convert it to Watts. # Associate the
device to a PDU, RDP, or PP component in the floor layout by dragging it from *External Systems* to the component in the layout. # Right-click
the component in the layout, and select *Properties*. # In the *Power Distribution* page, select output voltage and select *New* to configure the
connection to the rack PDU. Remember to fill in the *Module number*. # Repeat the above step until all connections have been configured
between the power breaker modules and the rack PDUs. Make sure the connection configuration matches the mapping done on the device in
step 2. The module number configuration must match and exist in both tables for the measurements to be included in the capacity calculations.
When you have saved your configuration, and the system has retrieved the first measurements from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}, *Measured Peak Power* values appear in *Properties>Power Distribution*
(Figure 1). It may take a while before they appear, depending on your settings. In *System Setup>External System Configuration*, you can
configure a shorter *Power information retrieval interval* to see the values quicker. {tip:icon=false}*Note*:The measured values in Figure 2 are
instant values from {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} whereas the measured values in Figure 1 are peak
values gathered over time. Since these values are different in nature, the values differ. Each time you edit the sensor mappings, the measured
data for that device will be deleted (the next time the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server gets data from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}), and peak and average data will only be collected from that point in time
and onwards in contrast to the normal 30 days "catch up" behavior.{tip} {column} {column:width=50%} Figure 1 !props_powerdistr.png|thumbnail!
Figure 2 !deviceprops_sensormapping.png|thumbnail! {column}{section} || See also || [Branch Circuit Monitoring] [Configuring power connections]
[Power Distribution Properties] [Configuring external system integration] [Associating live data from an external system to the layout] [Viewing
external system data] [Breakers in module must have unique power phases] [Power distribution equipment must have unique breaker module
numbers] [The breaker configuration in the Power Distribution properties does not match the measured power data]

Working with Branch Circuit Monitoring

When you have configured the Branch Circuit Monitoring, you can work with the
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} features in the same way as if you had configured measured values at
rack PDU level. Alarms on a breaker module in the PDU, RDP, or PP display as an issue on the entire PDU, RDP, or PP. The impact of a failure
displays as if all rack PDUs connected to the power distribution are at risk, even if the failure really only impacts the rack PDU connected to the
particular breaker. When collecting multiple measurements for one component in the floor layout, alarms on a breaker module in an additional
device do not display on the associated PDU, RDP, or PP. These alarms only display on the device in the *External Systems* view and are not
included in the impact analysis. ||See also|| [Branch Circuit Monitoring] [Configuring Branch Circuit Monitoring]

StruxureWare Operations - Change

{section}{column:width=50%}{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} ensures that changes are carried out in a
controlled process with minimum risk to the IT infrastructure. This minimizes the impact of change-related incidents and improves day-to-day
operations. h2. Change management overview of projects and resources (1) The *Changes* perspective allows managers to monitor and plan the
overall progress of projects and drill down on areas of interest by a number of categories, such as work order assignee, project code, and
location. For example: * Allocate resources based on amount of work orders assigned to a resource * Avoid scheduling conflicts * Handle work
order peaks * Create reports about work order actions (available in the Application bar *Analytics>Reports*). h2. Controlled work order process (2)
The *Work Order Editor* along with the *Work Orders* and *Remedy Change Tickets* panes allow management and execution of work orders in
a controlled process. For example: * Propose future changes to rack contents (possible in the rack layout with the *Work Order Editor* enabled
(toggle on/off by clicking *Cancel* in the *Work Order Editor*) * Manage work orders (available in the *Work Orders* pane at the bottom of the
screen by default). h2. End-to-end change management across systems (3) Supported integration with the BMC Remedy Change Management
system allows you to cover the entire change workflow from the Operations application without the need to run Remedy.
{column}{column:width=50%} Figure 1 !Change_overview.png|thumbnail! Figure 2 !rackplanning_WO_Editor.png|thumbnail! Figure 3 !Integration
with the Remedy Change Management system from BMC^ticketsinOps.png|thumbnail! {column}{section} {section} {column:width=25%} h5.
Change Management [Change Management overview] [Planning changes to rack equipment] {column} {column:width=25%} h5. Work Orders
[Working with work orders] [Identifying work order task and equipment relationship] [Configuring work order administrative settings] {column}
{column:width=25%} h5. Remedy Integration [Integration with the Remedy Change Management system from BMC] {column}
{column:width=25%} h5. Reports [Work Order reports] {column} {section}

Change Management overview

{section}{column:width=50%}The *Changes* perspective allows you to monitor and plan the overall progress of projects and drill down on areas of
interest by a number of categories, such as work order assignee, project code, and location. For example: * Allocate resources based on amount
of work orders assigned to a resource * Avoid scheduling conflicts * Handle work order peaks * Create reports about work order actions (available
in the Application bar *Analytics>Reports*). This perspective includes work orders with tasks only. Any work orders without tasks in the system will

not appear in this perspective. !Configuring the room layout^video24x20.jpg! Watch this [video tutorial|Video Tutorials#changesviewvideo] to see
how to monitor the structured change management process. h2. Monitoring You can use the charts and views for insight (read-only). They update
dynamically as you drill down left to right and top to bottom. * Click on a specific location to see all the related tasks or continue drilling down on
assignee, project code, time, etc. * In the *Tasks Overview*, navigate and zoom in on the time line, and hover over the colored bars to see tool tip
details. * Quickly identify overdue tasks in the *Summary* view: Click the word *Overdue*, and the *Work Order Tasks Overview* will show only
these overdue tasks. The same kind of filtering happens when you click on *Not Started*, *In Progress*, etc. * In the *Project Overview*, filter on
tasks with a specific project code. The charts and views update accordingly. {tip:icon=false}*Tip*: Over time, the amount of tasks in the system will
grow, and you can select *Hide completed projects* to only see the active tasks.{tip} h2. Editing The *Work Order Tasks Overview* pane,
however, provides an option to edit tasks across work orders. * Double-click a task in the list to open the work order with this task in the *Work
Order Editor* and apply changes. For example, if a resource is out sick or will be on vacation next week, select all tasks not started or in progress
for this assignee and reassign them to another resource or change the due date to postpone the tasks until he returns. * At any time, right-click
and print a list of tasks, for example assigned to a specific resource and hand it out. {column} {column:width=50%} !StruxureWare Operations Change^change_overview.png|thumbnail! {column} {section} ||See also|| [StruxureWare Operations - Change] [Working with work orders]

Rack equipment planning

{section}{column:width=50%}{excerpt:hidden=false}In previous versions of the software, you did rack equipment planning in a separate *IT
Change* perspective and work order management in a separate *Work Orders* perspective. The functionality has been merged into an integrated
flow in the *Planning>Data Center* perspective. Use the controlled automated work order process to propose changes to the non-power,
rack-mountable equipment included in the racks for existing rooms (drag and drop).{excerpt} Any changes proposed to the data center model will
appear color coded and with symbols added to the equipment icons until the changes saved. After you have saved and closed the *Work Order
Editor*, you can accept or reject the changes by right-clicking the equipment icon and selecting *Cancel Planned Change* or *Execute Planned
Change*. {tip:icon=false}*Note*: You cannot delete or reposition a rack PDU or rack-mounted UPS when you are working in the controlled work
order process as these are critical to the power connection setup for a server room. Instead, you can do changes of this kind when the *Work
Order Editor* is closed.{tip} {column}{column:width=50%} !StruxureWare Operations - Change^rackplanning_WO_Editor.png|thumbnail!
{column}{section} ||See also|| [StruxureWare Operations - Change] [Planning changes to rack equipment] [Equipment Stages] [Working with work
orders] [Creating a controlled automated work order]

Planning changes to rack equipment

{excerpt:hidden=false}Propose changes to the power-consuming rack-mountable equipment included in the racks for existing rooms and let the
system record automatic work orders for these actions. The proposed changes to the system can subsequently be executed or rejected.{excerpt}
# In *Planning>Data Center*, open the *Work Order Editor* pane to plan changes to the rack-mountable equipment: ## Add or move equipment
by dragging it from the *Catalog* pane or another location in the *Layout* or *Navigation* panes or by using the *Rack-Mount Equipment
Placement* pane. ## Delete equipment by right-clicking it and selecting *Delete*.\\ \\ {tip:icon=false}*Tip*: You can move or delete multiple items
at the same time by using Ctrl-click or Shift-click.{tip} Symbols are added to the equipment to indicate the pending change: +, x and arrows (up for
items to be moved from here, down for items to be moved to here). See an overview of equipment stages [here|Equipment Stages]. # Save and
close the *Work Order Editor* pane. # Select *Rack Layout* and execute or cancel the planned changes by right-clicking the equipment
*Navigation* or *Layout* pane and selecting *Execute Planned Change* or *Cancel Planned Change*. {tip:icon=false}*Note*: When you execute a
planned change, any associated work orders will be automatically updated, and when you set a work order to completed, the associated planned
change is executed.{tip} Properties can be changed for equipment at any time, even if it is in pending state. However, if you plan to move an item,
and then subsequently change properties for the pending move (source), these changes will be lost when you execute the planned change. ||See
also|| [Rack equipment planning] [Working with work orders]

Equipment Stages
{excerpt:hidden=false}When planning rack equipment, you can see equipment represented in various stages in the layout. The graphical
representation varies slightly at different zoom levels. {excerpt} {table:border=1|frame=box|} {table-row:align=center} {table-cell}*Layout*
{table-cell} {table-cell}*Equipment Stage* {table-cell} {table-cell}*Description* {table-cell} {table-row} {table-row} {table-cell:rowspan=5|}
!rackplanning.png|align=center!\\ {table-cell} {table-cell}Existing {table-cell} {table-cell}Equipment shown in its current location, with no action
pending. It displays in dark gray, indicating that it occupies the position shown. {table-cell} {table-row} {table-row} {table-cell}Pending Move
(Source) {table-cell} {table-cell}Equipment shown in its current location but has a move pending. It displays in blue with an arrow up, until you
select to save, indicating that it occupies the position shown but that you can still edit it. After you have saved, the color will change to light gray,
indicating that you can no longer edit it. {table-cell} {table-row} {table-row} {table-cell}Pending Move (Destination) / Planned {table-cell}
{table-cell}Equipment shown in its target location for a pending move. It displays in green with an arrow down, until you select to save, indicating
that the position is reserved, but that you can still edit it. After you have saved, the color will change to light gray, indicating that you can no longer
edit it. {table-cell} {table-row} {table-row} {table-cell}Pending Add {table-cell} {table-cell}Equipment shown in its target location for a pending
addition. It displays in green with a +, until you select to save, indicating that the position is reserved, but that you can still edit it. After you have
saved, the color will change to light gray, indicating that you can no longer edit it. {table-cell} {table-row} {table-row} {table-cell}Pending Deletion
{table-cell} {table-cell}Equipment shown in its current location, but with a pending deletion. It displays in green with an x in a circle, until you select
to save, indicating that it occupies the position shown but that you can still edit it. After you have saved, the color will change to light gray,
indicating that you can no longer edit it. {table-cell} {table-row} {table} ||See also|| [Rack equipment planning] [Planning changes to rack
equipment] [Working with work orders]

Working with work orders

{section}{column:width=50%}{excerpt:hidden=false}You can enable the controlled automated work order process in the *Planning>Data Center*
perspective by opening the *Work Order Editor* and making changes to the layout. Any changes done to add, move, or delete IT equipment are
recorded and work order tasks for implementing these changes in the data center are automatically generated.{excerpt} You can also view work
orders in a list without the need to open the *Work Order Editor*. The list is available in *Planning>Data Center* (and read-only in
*Operations>Data Center*) in the *Work Orders* pane if you have {multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true}
installed. See [Creating a controlled automated work order] and [Creating a custom work order without recorded tasks] for details about creating
work orders, adding them to the list. h2. Edit or view a listed work order # In the *Work Orders* pane, double-click a listed work order. # Edit or
view the selected work order in the *Work Order Editor*. ## Edit the work order summary and details. ## Add, edit, or delete task details. h2. Filter
work orders To limit the amount of work orders in the list to only include those you want to edit: * Use the search filters below the column headers
in the pane. * Use the link icon to only see work orders related to the selected equipment. h2. View, print or export work orders * To access print

and export options for the work order list, multi-select work orders (Ctrl+click or Shift+click) and select *Print Work Order List*. The report view
opens and you can click the *Print* icon and then *Export* icon to export it as a PDF, HTML, or XLS document. * To view or print an audit report,
listing the tasks in a selected work order, right-click a work order and select *Audit Work Order*. The report view opens and you can click the
*Print* icon and then *Export* icon to export it as a PDF, HTML, or XLS document. {column} {column:width=50%} !StruxureWare Operations Change^rackplanning_WO_Editor.png|thumbnail! {column} {section} ||See also|| [Creating a controlled automated work order] [Creating a custom
work order without recorded tasks] [Identifying work order task and equipment relationship] [Creating and applying work order templates]
[Configuring work order administrative settings] [Work Order reports]

Creating a controlled automated work order

{section}{column:width=50%}{excerpt:hidden=false}You can enable the controlled automated work order process in the *Planning>Data Center*
perspective by opening the *Work Order Editor* and making changes to the layout. Any changes done to add, move, or delete IT equipment are
recorded and work order tasks for implementing these changes in the data center are automatically generated.{excerpt} h2. Working with the
controlled automated work order process # In *Planning>Data Center*, open the *Work Order Editor*. # Edit the work order details, such as
summary, assignee, needed by date, and priority. # Select a project code (not obligatory). The project code can be used to identify the work order
type and you can filter the work order list using this code. To add a new code, click the plus icon and type the code. # Type a comment, (not
obligatory). If Remedy integration has been configured and the work order has been associated with a ticket, the comment will be transferred to
the Remedy system along with the work order on completion. # Add, move, or delete equipment in the layout (drag and drop). # Edit the task
details, if needed. # Save and close the *Work Order Editor*. The system automatically creates the work order. To exit the work order recording
mode and execute planned changes, click *Cancel* in the *Work Order Editor*. When you execute a planned change, any associated work orders
will be automatically updated, and when you set a work order to completed, the associated planned change is executed. Any work order at or past
the date requested for completion is highlighted in red text. To disable the automatic work order recording when adding, moving, or deleting
equipment in the layout, close the *Work Order Editor*. {column} {column:width=50%} !StruxureWare Operations Change^rackplanning_WO_Editor.png|thumbnail! {column} {section} ||See also|| [Creating a custom work order without recorded tasks] [Working
with work orders]

Creating a custom work order without recorded tasks

{section}{column:width=50%} You can create, review, and edit custom work orders without recorded tasks. # In *Planning>Data Center*, open the
*Work Order Editor*. # Edit the work order details, such as summary, assignee, needed by date, and priority. # Select a project code (not
obligatory). The project code can be used to identify the work order type and you can filter the work order list using this code. To add a new code,
type the code directly in the field or select *Tools>Create Work Order Project Codes* and add the new code. # Type a comment (not obligatory). If
Remedy integration has been configured and the work order has been associated with a ticket, the comment will be transferred to the Remedy
system along with the work order on completion. # Click *Create new task* if you want to add one or more tasks.
!icon_createnewtask.png|thumbnail! # Select the room the task is related to. In the system, tasks are related to a room or equipment. # Edit the
task details. # Add more tasks if needed. # Save and close the *Work Order Editor*. {column} {column:width=50%}
!WO_createnewtask.png|thumbnail! {column} {section} ||See also|| [Creating a controlled automated work order] [Working with work orders]

Identifying work order task and equipment relationship

{excerpt:hidden=false}When you are working with IT changes and related work orders, you can open the work order related to a selected piece of
equipment in the rack layout or navigation.{excerpt} Equipment with pending work order tasks are highlighted with pending change icons so you
can quickly find them in the rack layout or navigation tree structure. h2. Finding a related work order task You can select a piece of equipment in
the rack layout and navigate to the related work order. The option is available both when working with Operations (Data Center) and Planning
(Data Center). * Right-click a piece of equipment in the rack layout (or navigation tree structure) and select *Show Work Order* to view the work
order and see the tasks related to the selected equipment. \\ \\ This option does not allow you to edit the work order but allows you to continue to
work with the active operations. When you are done viewing the work order, you can use the right-click navigation options to get back to what you
were working with before you opened the work order. h2. Finding equipment related to a work order task In the *Work Order Editor*, you can
select a task and highlight the related equipment in the layout. * Click the *Show in Editor* icon next to the task for which you want to see the
related equipment. !icon_WO_ShowinLayout.png|thumbnail! ||See also|| [Working with work orders]

Creating and applying work order templates

{section}{column:width=50%}Often, working with change management in a data center requires certain tasks to be repeated regularly. In
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, work order templates and the option to schedule recurring work orders
assist you in managing repetitive tasks. A work order template is a work order that you can save and reuse for other similar work orders. As you
add to your templates library, it will grow into a valuable collection of best practices. !Configuring the room layout^video24x20.jpg! Watch this
[video tutorial|Video Tutorials#wotemplatesvideo] to see how to create and apply work order templates to establish best practices. h2. Creating a
work order template # In *Tools*, select *Configure Work Order Template*. # In the template dialog box, click the plus icon to create a new
template. # Fill in the work order template properties, such as name, priority, project code, etc. # Add one or more tasks to the work order
template. The saved work order template now appears in the list of available templates when you right-click a piece of equipment or a room layout
and select *Apply Template*. h2. Applying a work order template # Right-click one or more pieces of equipment or a room layout and select
*Apply Template*. # In the *Work Order Editor*, adjust the text if needed for this work order. \\ \\ {tip:icon=false}*Tip*: You can select multiple
items at the same time by using Ctrl-click or Shift-click.{tip} {column} {column:width=50%} !WO_templateeditor.png|thumbnail! {column} {section}
||See also|| [Working with work orders] [Scheduling work order recurrence]

Work Order reports

{section}{column:width=50%}{excerpt:hidden=false}You can generate work order reports showing a list of all the work orders in a specified work
order range or details of a specified work order. You find this option in *Analytics>Reports*.{excerpt} h2. Work Order List report A summary list of
work orders in the system. h2. Work Order Details report A list of work orders, including details about status, description, and comments. h2. Work
Order Tasks report A list of selected work order tasks from one or more work orders. The generated report displays in the *Report View*. You can
now use the *Report View* toolbar to navigate the report pages on the screen (arrow icons), or to print or export the report to a file in any of the
available formats (Export icon, down arrow for selection of format). You can also generate reports when working in *Planning>Data Center* by
right-clicking one or more work orders in the *Work Orders* pane. For example, click a work order and select *Print Work Order* to see all tasks in
the work order without the need to open the work order in the *Work Order Editor*. {column}{column:width=50%}
!report_workorderdetails.png|thumbnail! {column}{section} ||See also|| [Working with work orders] [Working with reports]

Deleting old work orders

{section}{column:width=50%}Over time, the amount of old work orders in the system will grow. You can perform a cleanup and delete work orders
older than 400 days, that is work orders with a *Needed by date* of minimum 400 days prior to today's date. {tip:icon=false}*Note*: Use this
operation with caution. Once performed, there is no way of retrieving deleted work orders.{tip} # Select *System Setup>Work Order Cleanup*. #
Type the minimum age of the old work orders to be deleted. # Type the confirmation text {{CoNfiRm}}. Type exactly what it says and be sure to
enforce case sensitivity. This step has been added to prevent you from unintentionally deleting work orders by accident. Work order related data
in the audit trail log will not be deleted. {column} {column:width=50%} !wo_cleanup.png|thumbnail! {column} {section} ||See also|| [StruxureWare
Operations - Change] [Working with work orders] [Configuring work order administrative settings]

Configuring work order administrative settings

{section}{column:width=50%}The *Work Order Administrative Settings* enable you to: * Schedule recurring work orders for managing repetitive
tasks. * Configure automatic e-mail notification to relevant individuals when a work order status changes to completed. {column}
{column:width=50%} !adm_settings_WO.png|thumbnail! {column} {section} ||See also|| [Scheduling work order recurrence] [Setting up automatic
e-mail notification on work order completion] [Working with work orders]

Scheduling work order recurrence

{section}{column:width=50%}Often, working with change management in a data center requires certain tasks to be repeated. In
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, work order templates and the option to schedule recurring work orders
assist you in managing repetitive tasks. A recurring work order will recur in the *Work Orders* pane with a given interval. h2. Configuring a work
order recurrence schedule # Open the work order for which you want to schedule recurrence. # Click the *Administrative Settings* icon and select
*Schedule recurrence*. # In the *Schedule Work Order Recurrence* dialog box, select *Recur every* and set the interval for the work order to
recur. After this configuration, when you complete a work order for which you have configured recurrence, it will show up again as a copy with a
new scheduled needed by date and a status of not started. {column} {column:width=50%} !schedule_WO_recur.png|thumbnail! {column} {section}
||See also|| [Working with work orders] [Configuring work order administrative settings] [Creating and applying work order templates]

Setting up automatic e-mail notification on work order completion

{section}{column:width=50%}{excerpt:hidden=false}The system can automatically send an e-mail notification to relevant individuals when a work
order status changes to *Completed*.{excerpt} For this feature to be available, [e-mail settings|Configuring e-mail settings] must have been
configured as well as [e-mail address for the users|Managing users in the system]. # Open the work order for which you want to configure e-mail
notification. # Click the *Administrative Settings* icon and select *E-mail notification*. # In the *E-mail notification* dialog box, select the users to
notify. If the user does not appear in the list: * Verify that the user's e-mail address has been added to the [user information|Managing users in the
system]. * If you had the *Work Order Editor* open while performing changes to the user information, close and reopen the *Work Order Editor*.
An e-mail is sent to the selected e-mail addresses, notifying the relevant individuals of the work order completion. When a work order is assigned
to a user in the system, an e-mail will automatically be sent to him. If it is reassigned, both the previous and new assignee will receive an e-mail.
For this feature to be available, [e-mail settings|Configuring e-mail settings] must have been set up but no further configuration is needed.
{column} {column:width=50%} !WO_emailnotify.png|thumbnail! {column} {section} || See also || [Configuring e-mail settings] [Working with work
orders]

Integration with the Remedy Change Management system from BMC

{section}{column:width=50%} This system integration ensures relevant information is shared between
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and the most commonly used process management system in the market.
A valid {multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} license allows you to use this feature. h2. End-to-end change
management, tracking changes across multiple systems If you are using the Remedy Change Management system to track changes in your data
center, you can configure and use a tracking solution that covers the entire process from new ticket in Remedy through work order tasks in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to completed ticket in Remedy. Before you can start working with work
orders and tickets from the external change management system, you must [configure the integration|Configuring Remedy integration] between
the systems in *External System Configuration* in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. You must also ensure
the appropriate [users get access to the feature|Managing user rights] in *System Setup>User Rights and Authentication Servers* (*Work
Orders*). h2. Working with work orders and Remedy tickets Once you have configured the system integration, you can start [tracking
tickets|Viewing tickets from Remedy] from Remedy in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and [associating
tickets with work orders|Associating Remedy tickets and work orders]. {column} {column:width=50%} Configuration of Remedy integration
!Remedyconfiguration.png|thumbnail,border=1,width=100! !arrowdown.png|thumbnail,width=30! Configuration of user rights for work orders
!userrights_wo.png|thumbnail,border=1,width=100! !arrowdown.png|thumbnail,width=30! Remedy tickets appear in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} !ticketsinOps.png|thumbnail,border=1,width=100!
!arrowdown.png|thumbnail,width=30! Work order changed to In progress !woinprogress.png|thumbnail,border=1,width=100!
!arrowdown.png|thumbnail,width=30! Changes updated in Remedy !updateRemedy.png|thumbnail,border=1,width=100! {column} {section} || See
also || [Configuring Remedy integration] [Managing user rights]

Viewing tickets from Remedy

{section}{column:width=50%}When the system has been configured to support [integration with the Remedy Change Management
system|Configuring Remedy integration], tickets from Remedy matching the filter settings show up in the *Remedy Change Tickets* pane.
Right-clicking a ticket and selecting one of the association options associates the ticket with a work order in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. You can identify associated tickets and work orders in the *Remedy
Change Tickets* and *Work Orders* panes by a number in the association column (1). In the status bar, you can see the number of tickets shown
out of the total number of tickets (2). To remove applied filters and show all tickets, click the remove all filters icon (3). {column}
{column:width=50%} !overviewtickets_wlayers.png|thumbnail! {column} {section} || 123 Steps to... || See also || | Filtering Remedy Tickets
(Search) {anchor:filtertickets} You can set a filter on the Remedy Tickets to show only the tickets you want to see. * In the column containing the
data you want to filter, select from list or type a filter matching your request. \\ \\ This filter only limits the list of tickets already in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and is not to be confused with the [qualification filter|Configuring Remedy
integration]. | [Associating Remedy tickets and work orders] [Configuring Remedy integration]

Associating Remedy tickets and work orders

Once you have configured the Remedy system integration, you can start associating tickets from Remedy with work orders in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. You can associate one or more tickets to one work order. h2. Associate
with a new work order # In the *Remedy Change Tickets* pane, right-click a Remedy ticket. # Select *Associate with a new work order*. The
*Work Order Editor* opens. # Edit the new work order data, and click *Save and close*. The new work order and the association have been
created. The associated work order/Remedy ticket is shown in the *Associated Work Order/ID* column in the *Remedy Change Tickets* and
*Work Orders* panes. h2. Associate with an existing work order If you have already started working on a work order in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, you can associate to an already existing work order. # In the *Remedy
Change Tickets* pane, right-click a Remedy ticket. # Select *Associate with an existing work order*. The *Work Orders* pane opens. # In the
*Work Orders* pane, select the work order to associate to, and click *OK*. The association has been created, and in both panes, the associated
work order/Remedy ticket is shown in the *Associated Work Order/ID* column. # Double-click the association column to switch between the
panes. Once you have made the association, whenever status changes happen to the work order or the ticket in either
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} or Remedy, these changes are reflected in both systems. ||See also||
[Integration with the Remedy Change Management system from BMC] [Viewing tickets from Remedy]

Remedy integration process overview

!Remedy_Operations_Process.png|border=1, thumbnail!

StruxureWare Operations - Energy Efficiency

{section}{column:width=50%}{excerpt:hidden=false}{multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} allows you to configure
the data for calculating the Power Usage Effectiveness (PUE) or Data Center Infrastructure Efficiency (DCiE), the cost and CO2 emission per
subsystem. Subsystem data can either be measured (live) or computed (without power meters). You can view the graphs that are published to the
Energy Efficiency Dashboard for IT load, current PUE/DCiE, historical PUE/DCiE, costs and CO2 emission per subsystem.{excerpt} For
information about the energy efficiency concepts, such as Power Usage Effectiveness (PUE) and Data Center Infrastructure Efficiency (DCiE), go
to [the Green Grid|http://www.thegreengrid.org/] and read the [White Papers|http://www.apc.com/go/promo/whitepapers/index.cfm] . * WP-161:
Allocating Data Center Energy Costs and Carbon to IT Users * WP-157: Selecting an Industry-Standard Metric for Data Center Efficiency *
WP-154: Electrical Efficiency Measurement for Data Centers * WP-114: Implementing Energy Efficient Data Centers * WP-113: Electrical
Efficiency Modeling for Data Centers * WP-66: Estimating a Data Center's Electrical Carbon Footprint {tip:icon=false}*Note*: You can toggle the
efficiency metric between PUE and DCiE in *Tools* *> Preferences* *> General*.{tip} {column} {column:width=50%} !Energy Efficiency
Dashboard^EEdashboard.png|thumbnail! {column} {section} {section} {column:width=30%} h5. Energy Efficiency Metrics [Showing PUE or DCiE
values|Reviewing system preferences#pref_EEmetric] [About PUE and DCiE] h5. Energy Efficiency Dashboard [Using the Energy Efficiency
Dashboard|Energy Efficiency Dashboard] [Exporting dashboard graphs to an external web site] {column} {column:width=30%} h5. Energy System
Configuration [Configuring an energy system|Energy System Configuration] [Configuring power dependencies|Power Dependency Configuration]
[Configuring Infiltration] [Configuring IT load] [Configuring Ventilation and Lighting] {column} {column:width=30%} h5. Scripting [Creating scripts]
[Associating scripts] {column} {section}

About PUE and DCiE

{excerpt:hidden=false}Power Usage Effectiveness (PUE) and Data Center Infrastructure Efficiency (DCiE) are commonly used metrics for
determining if energy efficiency improvements should be made. {excerpt} h2. PUE PUE = Total Facility Power / IT Equipment Power The range is
from 1 to infinity (5 in {multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true}). The lower the value is, the better the efficiency is. 1
being 100% efficiency (all power used by IT equipment only). h2. DCiE DCiE = IT Equipment Power / Total Facility Power x 100% The range is a
percentage. The higher the value is, the better the efficiency is. 100% being 100% efficiency (all power used by IT equipment only). *Total Facility
Power is the total power entering the data center. The measurement point is at or near the facility's utility meter. *IT Equipment Power is the
power delivered to the servers (after power conversion, switching, etc.). ||See also|| [Preferences: Showing PUE or DCiE values|Reviewing
system preferences#pref_EEmetric]

Power Dependency Configuration

{section}{column:width=50%}{excerpt:hidden=false}In the Power Dependency Editor, you can draw a diagram of the entire physical infrastructure
supporting the racks, including the power connections.{excerpt} When you open the *Power Dependency Editor*, some equipment may already
be shown in the upper left corner. There may be more components hidden behind the one that is visible. If the diagram is empty, you must
configure the physical infrastructure with rooms and equipment first. This editor includes equipment at PDU level and upstream to the switchgear,
and equipment from the PDU and downstream that supports the racks, such as cooling units and pumps. The IT load of the racks is included in
the PUE/DCiE calculation as an IT Load subsystem. Infiltration, lighting, and ventilation are also included as subsystems. You can move the
components one at a time from the initial position in the corner. Then you can draw power connections between the components in the diagram to
configure the power dependency setup of the entire physical infrastructure. {column} {column:width=50%} !ee_powerdependency.png|thumbnail!
{column} {section} || 123 Steps to... || See also || | *Configuring power dependencies* \\ Configure the power dependencies between the
equipment in the diagram to ensure the configuration accurately reflects the live physical infrastructure of your energy systems. # In the
Application bar, select *Planning* *> EE Configuration* to open the *Power Dependency Editor*. # Drag the equipment shown in the upper left
corner into any position in the diagram to reveal other pieces of equipment behind it, and continue to drag equipment from the upper left corner
until all components are visible in the diagram. \\ \\ {tip:icon=false}*Tip*: Whenever you add new equipment to the infrastructure in *> Planning* *>
Data Center*, it appears in the upper left corner of the *Power Dependency Editor*. To ensure you always see any new components in the
diagram, move all components away from the upper left corner.{tip} \\ If you have many components you do not want to see in the diagram, for
example many cooling units you want to see as one subsystem, you can drag them on top of each other so you only see them as one. # Move all
the components into the appropriate position by dragging them, and resize them by pulling the corners as needed. The diagram does not show
the exact position of the components, rather a line diagram representing the power connections between the components. # Select the connection
icon !connect.png! in the toolbar. # Click on a component you want to connect from, and click the other component you want to connect to. If you
are creating a PDU downstream connection, define the breaker involved in the power connection, by name, rating, and derating values. A line
now connects the two components in the diagram, with an arrow indicating the downstream power connection. # Repeat the above step to
continue to draw connections, until all connections in the live physical infrastructure are represented in the diagram (except for racks and
rack-mounted equipment). The rack-level power connections, for example from a PDU to a rack PDU is set up in the component properties in *>

Planning* *> Data Center*. # At any time, right-click a component to see the properties. The components now have a power path setup, and the
load is included in the power capacity calculations. They also appear in the *Equipment Browser*, *Power Dependency pane*, *Inventory Report*,
and *Audit Trail Report*. | [StruxureWare Operations - Energy Efficiency] |

Energy System Configuration

{section}{column:width=50%}{excerpt:hidden=false}The energy systems are listed in the *Systems* pane. You can define what parts of the
physical infrastructure to include in the system, and you can define the properties.{excerpt} You can create a new system by selecting *> File* *>
New Energy System* or by clicking the *Systems* pane *New Energy System* icon. !new-system16x16.png! In the dialog box, type a name and
define the environmental settings for designed IT load and outdoor temperature. You can double-click a system in the list (or right-click and select
*Configure Energy System*) to open it in a separate tab in the editor to configure the system. Multiple systems (maximum 10) can be open at the
same time. In the graphical editor, when you open a new system, there are no components included in the energy system. They all appear grayed
out. You can define which components of the physical infrastructure to include in this energy system by right-clicking the components in the
diagram and selecting to include / exclude them. The included components are no longer highlighted in gray. You can delete a system by
right-clicking it in the *Systems* pane and selecting *Delete*. Once you have configured power consumption from sensor measurements or
estimations, you can see the energy efficiency rating for the energy system on the dashboard. You can set the calculation interval and
environmental properties for a system by right-clicking it in the *Systems* pane and selecting *Properties*. For an overview of all components in
the entire physical infrastructure and all power dependencies across the energy systems, you can open the *Power Dependency Editor*.
{tip:icon=false}*Note*: The system needs a minimum energy system configuration to provide you with a calculated PUE/DCiE value. An energy
system must at least include: * Switchgear * Energy Efficiency properties set on the switchgear and PDU * A PDU connected to the switchgear * A
script configured on the PDU * IT load properties set to include measured calculation source{tip} {column} {column:width=50%}
!energysystem.png|thumbnail! {column} {section} || 123 Steps to... || See also || | *Configuring an energy system* \\ Configure the components of
the energy system to ensure the configuration accurately reflects the live physical infrastructure of the system. # Click the *Systems* pane *New
Energy System* icon !new-system16x16.png!\\ and type a name and define the environmental settings. # Double-click an energy system in
*Systems* to open it in the editor. # To include components in an energy system: ## Right-click a grayed out component in the diagram and select
*Include in energy system*. ## Repeat this for all the components that you want to include. When a component has been configured to be
included in the energy system, it will no longer be grayed out. ## If you regret including a component, right-click it and select *Exclude from
energy system*. # Configure IT load, infiltration, lighting, and ventilation subsystems by clicking the icons at the bottom of the energy system, or
by right-clicking the energy system in the *Systems* pane. # At any time, right-click a component to see the properties. # In the *Scripts* pane,
create scripts to include measurements in the energy system's PUE/DCiE calculation. # Associate the created scripts with the components to
indicate which scripted values to include for which components in the diagram by right-clicking the components in the diagram and selecting *>
Associate Scripts* *> Folder name* *> Script name*. You can see the PUE/DCiE, CO2 emission and cost results of the configuration expressed
as graphs published to the Energy Efficiency Dashboard available when typing the server's IP address into a Web browser. | [StruxureWare
Operations - Energy Efficiency] |

Configuring Infiltration
{excerpt:hidden=false}You can access and edit the data on the property tabs defining the configuration for infiltration by right-clicking an energy
system and selecting *Properties* or by clicking the icons at the bottom of the Energy System pane. The configuration options vary based on the
type of subsystem.{excerpt} # Right-click the energy system and select *> Properties* *> Infiltration*. # Define the *Dry bulb fixed loss* to indicate
the fraction of power that is lost per degree Celsius dry bulb. # Define the loss configuration in *Dry bulb fixed loss*: type a number between 0 and
100, indicating the fraction of power lost per degree Celsius dry bulb. ||See also|| [Energy System Configuration]

Configuring IT load
{excerpt:hidden=false}You can access and edit the data on the property tabs defining the configuration for IT load by right-clicking an energy
system and selecting *Properties* or by clicking the icons at the bottom of the Energy System pane.{excerpt} # Right-click the energy system and
select *> Properties* *> IT Load*. # Define the general settings for the energy system's IT load. ## Select if the IT load is on the critical or primary
power path. IT load must be included for the energy system. ## IT load is measured (live). # Use the *Script* tab for writing scripts that retrieve
measurements. ||See also|| [Energy System Configuration]

Configuring Ventilation and Lighting

{excerpt:hidden=false}You can access and edit the data on the property tabs defining the configuration for IT load, infiltration, ventilation, and
lighting by right-clicking an energy system and selecting *Properties* or by clicking the icons at the bottom of the *Energy System* pane. The
configuration options vary based on the type of subsystem.{excerpt} # Right-click the energy system and select *> Properties* *> Ventilation*. #
Define the general settings for the energy system's ventilation. ## Select if the ventilation is on the critical or primary power path, or if there is no
ventilation to be included in this energy system. ## Select if the ventilation data is measured (live) or computed (without power meters). # Define
the configuration of the energy system's ventilation. ## In *Actual kW Nameplate*, type the total nameplate value of the ventilation. ## In *Usable
fraction of nameplate w/o derating*, type a number between 0 and 100, indicating the usable fraction of power that can be used within the devices
in this subsystem without derating. ## In *Redundancy*, type the redundancy of the subsystem. ## In *Redundancy +1 kW Increment*, type the
loss in kilowatt caused by internal redundancy. (Only needed if the redundancy option includes +1) ## In *Derate Capacity fraction*, type a
number between 0 and 1, indicating the usable fraction of the ventilation equipment nameplate value. ## In *Typical PU*, type the power usage
(PU) of the ventilation in power units relative to the total power usage. # Define the loss configuration of the energy system's ventilation. ## In
*Fixed loss*, type a number between 0 and 100, indicating the fraction of power that is the fixed loss of the ventilation. ## In *Proportional loss*,
type a number between 0 and 100, indicating the fraction of power that is lost proportional to the load of the data center. ## In *Square Law loss*,
type a number between 0 and 100, indicating the fraction of power that is lost proportional to the square of the load of the data center. ## In *Dry
bulb fixed loss*, type a number between 0 and 100, indicating the fraction of power lost per degree Celsius dry bulb. # Use the *Script* tab for
writing scripts that retrieve measurements. # Click *Lighting* and repeat the above steps for configuring the energy system's lighting settings.
||See also|| [Energy System Configuration]

Creating scripts
{excerpt:hidden=false}Create scripts to extract any data, sensor measurements and estimations to be associated with the energy system's
components and included in the PUE/DCiE calculations.{excerpt} You must have created an energy system and included the components
representing your physical infrastructure. # In *Scripts* pane, click the *Add folder* icon, and type a name for the folder. # Select the created
folder, and click the *Add Script* icon to open the script editor. # Type the JavaScript to extract any data, sensor measurements and estimations.

# If you want to extract data from {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} devices, click *Devices* to access the
{multi-excerpt-include:pageTitle=Branding|name=ISXCb|nopanel=true} *Devices* dialog box. ## In the *Devices* section, select from the list of
devices to expand the list of device sensors below. ## In the *Device sensors* section, select from the list of device sensors. ## Double-click to
add the sensor ID to the script at cursor position.\\ \\ You can multi-select device sensors, and right-click to access functions to extract: #*
Minimum #* Maximum #* Sum #* Average \\ \\ The function will be inserted at the bottom of the script with a default name. If you insert more than
one function of the same type, e.g. to add two sets of average values, you must rename one of the average functions to avoid name conflicts. \\ \\
To use the result of the function as a measurement, assign it to the returnValue variable, e.g. {{returnValue=sum();}}. It is necessary to convert the
values you use to kW to avoid having some input values in W, and others in kW, and to ensure consistent data on the dashboard. \\ \\ # Click
*Evaluate* to validate, execute and display the result of the script. # Subsequently, if you want to edit the script, right-click it in the *Scripts* pane,
and select *Edit*. If the script has been associated with a component in an energy system, right-click the component and select *Edit Script*. # If
you regret creating a script, right-click the script in the *Scripts* pane, and select *Delete*. When the scripts have been created, you can associate
them with the components in an energy system to indicate which scripted values to include for which components. You can see the PUE/DCiE,
CO2 emission and cost results of the configuration expressed as graphs published to the Energy Efficiency Dashboard available when typing the
server's IP address into a Web browser. ||See also|| [Energy System Configuration] [Associating scripts] [Script Editor]

Associating scripts
{excerpt:hidden=false}Configure the association between the scripts and the components of the energy system to ensure the correct scripted data
is included in the configuration.{excerpt} You must have configured an energy system with included components and have created scripts before
you can start associating the scripts. # Double-click an energy system in the *Systems* pane to open it. # In the diagram, right-click a component
that has been included in the energy system, and select *> Associate Scripts* *> Folder name* *> Script name*. A green s icon appears on the
component in the diagram and on the script in the *Scripts* pane to illustrate the association. # If you regret associating a script with a component,
right-click the component and select *Unassociate Script*. # Subsequently, if you want to edit the associated script, right-click the component and
select *Edit Script*. ||See also|| [Creating scripts] [Script Editor]

Script Editor
{excerpt:hidden=false}The Script Editor allows for writing scripts, e.g. to extract measured data from devices using JavaScript.{excerpt} It is
accessed by clicking the *Add Script* icon in the *Scripts* pane, or by right-clicking an existing script or component in an energy system with an
associated script. Double-clicking a device sensor will add the sensor ID to the script window. Selecting multiple device sensors and right-clicking
will access functions to extract minimum, maximum, sum, and average values. Use the Energy Efficiency specific language construct returnValue
to return the value of the script. {tip:icon=false}*Note*: If you do not specify a returnValue, the script will return null.{tip} The script editor has
built-in content assistance, including: * Auto-complete on JavaScript language constructs and device sensor IDs (Ctrl-Space). * Text highlighting
of strings (blue), JavaScript language constructs (purple), comments (green), and reserved words, such as returnValue and importPackage
(orange). Clicking *Evaluate* will validate, execute and display the result of the script. ||See also|| [Creating scripts] [Associating scripts] [Energy
System Configuration]

Custom Java code in Script

{excerpt:hidden=false}You can add your own Java code to extend the possibilities of the
{multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} application. This can be helpful when integrating to legacy systems.
{excerpt} To enable this functionality, store the library files in the /opt/jboss-as/server/isxo/lib folder on the server. The classes in the jar file will
subsequently be available to the scripts after you restart the application. ||See also|| [Creating scripts] [Script Editor]

Sample Scripts
{excerpt:hidden=false}Sample scripts are provided as a guideline for creating the scripts needed to configure the energy systems. You can copy
and paste snippets or whole scripts into the script editor, and modify according to your needs.{excerpt} ||See also|| [Creating scripts] [Script Editor]
[Database Integration] [Sample Startup Script for Database Integration] [Sample Simple Database Query Script] [Sample Database Query Script]
[Web Service Integration] [Sample Startup Script for Web Service Integration] [Sample Data Retrieval Script for Web Service Integration]

Startup Script
{excerpt:hidden=false}The startup script is used for setting up data providers needed for retrieving measurements from sensors and third party
systems. The startup script is run when the {multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} server starts.{excerpt} The
script is a JavaScript file named startup.js located at /data/e2m on the server. To edit the file, you must log on to the server using SSH with
sufficient user rights. ||See also|| [Creating scripts] [Script Editor]

Energy Efficiency Properties

{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component in the floor layout in *Planning* *> Data
Center*, provides relevant information that identifies the energy efficiency values of the selected component. It is also available as read-only
information by right-clicking a component in an energy system in *> Planning* *> EE Configuration*.{excerpt} {table:border=1|frame=box|}
{table-row} {table-cell:} *Derate Capacity fraction* {table-cell} {table-cell:colspan=2|}Identifies the usable fraction of the nameplate value that can
be used for this component. For example, if you use a 20% safety margin, this value would be 0.8. {table-cell} {table-row} {table-row} {table-cell:}
*Redundancy* {table-cell} {table-cell:colspan=2|}Identifies the redundancy of this component. For example, if you have a redundant setup with two
80 kW UPS, this value would be 2N. {table-cell} {table-row} {table-row} {table-cell:} *Redundancy "+1" kW Increment* {table-cell}
{table-cell:colspan=2|}Identifies the loss in kilowatt caused by internal redundancy. (Only needed if redundancy option includes +1.) For example,
if you have a 40 kW UPS with one spare 10 kW power module, this value would be 10 kW. {table-cell} {table-row} {table-row} {table-cell:} *Typical
PU* {table-cell} {table-cell:colspan=2|}Identifies the power usage (PU) of this component relative to the total power usage. {table-cell} {table-row}
{table-row} {table-cell:} *Usable fraction of nameplate w/o derating* {table-cell} {table-cell:colspan=2|}Identifies the usable fraction of power that
can be used without derating the value. {table-cell} {table-row} {table-row} {table-cell:} *Fixed loss* {table-cell} {table-cell:colspan=2|}Identifies the
fraction of power that is the fixed loss of the component. {table-cell} {table-row} {table-row} {table-cell:} *Proportional loss* {table-cell}
{table-cell:colspan=2|}Identifies the fraction of power that is lost proportional to the load of the component. {table-cell} {table-row} {table-row}
{table-cell:} *Square Law loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost proportional to the square of the load of
the component. {table-cell} {table-row} {table-row} {table-cell:} *Dry Bulb Fixed loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of
power that is lost per degree Celsius dry bulb. {table-cell} {table-row}{table} ||See also|| [Energy System Configuration]

Energy System Properties

{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system, provides relevant information that
identifies the selected energy system.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Name* {table-cell} {table-cell:colspan=2|}A
user-definable value used to identify the energy system. {table-cell} {table-row} {table-row} {table-cell:} *Location* {table-cell}
{table-cell:colspan=2|}Identifies the country in which the energy system is located. This data is used for displaying the calculated amount of CO2
emitted per subsystem on the dashboard. {table-cell} {table-row} {table-row} {table-cell:} *Design IT Load Rating* {table-cell}
{table-cell:colspan=2|}Identifies the designed IT load. {table-cell} {table-row} {table-row} {table-cell:} *Outdoor Dry Bulb Temperature* {table-cell}
{table-cell:colspan=2|}Identifies the outdoor temperature. {table-cell} {table-row} {table-row} {table-cell:} *Calculation Interval* {table-cell}
{table-cell:colspan=2|}A user-definable value used to identify the interval for calculating the PUE / DCiE based on the data retrieved from the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server or other data provider. {table-cell} {table-row}{table} ||See also||
[Energy System Configuration]

Infiltration Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system or by clicking the relevant icon at the
bottom of the energy system, provides relevant information that identifies this subsystem. The information may vary based on the subsystem
type.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell:colspan=3|} *Configuration* {table-cell} {table-row} {table-row} {table-cell:} *Dry
bulb fixed loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost per degree Celsius dry bulb. {table-cell}
{table-row}{table} ||See also|| [Energy System Configuration]

IT Load Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system or by clicking the relevant icon at the
bottom of the energy system, provides relevant information that identifies this subsystem. The information may vary based on the subsystem type.
The IT load is a very dynamic value since it can change with the power consumption of each server in the data center. It will also change as
servers are added or removed from the date center.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:colspan=3|} *Configuration*
{table-cell} {table-row} {table-row} {table-cell:} *Power path* {table-cell} {table-cell:colspan=2|}Identifies whether the IT load is on the critical or
primary power path. You cannot choose to exclude it in this energy system. {table-cell} {table-row} {table-row} {table-cell:} *Calculation source*
{table-cell} {table-cell:colspan=2|}Identifies that the IT load is measured (live). {table-cell} {table-row} {table-row} {table-cell:} *Script* {table-cell}
{table-cell:colspan=2|}Opens the script editor for editing scripts to retrieve IT load measurements. {table-cell} {table-row}{table} ||See also||
[Energy System Configuration]

Lighting Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system or by clicking the relevant icon at the
bottom of the energy system, provides relevant information that identifies this subsystem. The information may vary based on the subsystem type.
Lighting covers the lighting is used to light the datacenter.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell:colspan=3|} *Configuration*
{table-cell} {table-row} {table-row} {table-cell:} *Power path* {table-cell} {table-cell:colspan=2|}Identifies if this subsystem is on the critical or
primary power path, or if it is not included in this energy system. {table-cell} {table-row} {table-row} {table-cell:} *Calculation source* {table-cell}
{table-cell:colspan=2|}Identifies if the load of the subsystem is measured (live) or computed (without power meters). {table-cell} {table-row}
{table-row} {table-cell:} *Actual kW Nameplate* {table-cell} {table-cell:colspan=2|}Sums up the total nameplate value of all equipment in this
subsystem. {table-cell} {table-row} {table-row} {table-cell:} *Usable fraction of nameplate w/o derating* {table-cell} {table-cell:colspan=2|}Identifies
the usable fraction of power that can be used within the devices in this subsystem without derating the value. {table-cell} {table-row} {table-row}
{table-cell:} *Redundancy* {table-cell} {table-cell:colspan=2|}Identifies the redundancy of this subsystem. For example, if you have a redundant
setup with two 80 kW UPS, this value would be 2N. {table-cell} {table-row} {table-row} {table-cell:} *Redundancy "+1" kW Increment* {table-cell}
{table-cell:colspan=2|}Identifies the loss in kilowatt caused by internal redundancy. (Only needed if redundancy option includes +1.) {table-cell}
{table-row} {table-row} {table-cell:} *Derate Capacity fraction* {table-cell} {table-cell:colspan=2|}Identifies the usable fraction of the nameplate
value that can be used in this subsystem. For example, if you use a 20% safety margin, this value would be 0.8. {table-cell} {table-row} {table-row}
{table-cell:} *Typical PU* {table-cell} {table-cell:colspan=2|}Identifies the power usage (PU) of this subsystem relative to the total power usage.
{table-cell} {table-row} {table-row} {table-cell:} *Fixed loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is the fixed loss of
the subsystem. {table-cell} {table-row} {table-row} {table-cell:} *Proportional loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power
that is lost proportional to the load of the subsystem. {table-cell} {table-row} {table-row} {table-cell:} *Square Law loss* {table-cell}
{table-cell:colspan=2|}Identifies the fraction of power that is lost proportional to the square of the load of the subsystem. {table-cell} {table-row}
{table-row} {table-cell:} *Dry bulb fixed loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost per degree Celsius dry
bulb. {table-cell} {table-row} {table-row} {table-cell:} *Script* {table-cell} {table-cell:colspan=2|}Opens the script editor for editing scripts for this
subsystem. {table-cell} {table-row}{table} ||See also|| [Energy System Configuration]

Ventilation Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system or by clicking the relevant icon at the
bottom of the energy system, provides relevant information that identifies this subsystem. Equipment that supplies fresh air to the data center.
Ventilation includes fans, and, if present, any heaters, humidifiers and dehumidifiers associated with the fresh air ventilation system.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell:colspan=3|} *Configuration* {table-cell} {table-row} {table-row} {table-cell:} *Power path*
{table-cell} {table-cell:colspan=2|}Identifies if this subsystem is on the critical or primary power path, or if it is not included in this energy system.
{table-cell} {table-row} {table-row} {table-cell:} *Calculation source* {table-cell} {table-cell:colspan=2|}Identifies if the data of this subsystem is
measured (live) or computed (without power meters). {table-cell} {table-row} {table-row} {table-cell:} *Actual kW Nameplate* {table-cell}
{table-cell:colspan=2|}Sums up the total nameplate value of all equipment in this subsystem. {table-cell} {table-row} {table-row} {table-cell:}
*Usable fraction of nameplate w/o derating* {table-cell} {table-cell:colspan=2|}Identifies the usable fraction of power that can be used within the
devices in this subsystem without derating the value. {table-cell} {table-row} {table-row} {table-cell:} *Redundancy* {table-cell}
{table-cell:colspan=2|}Identifies the redundancy of this subsystem. For example, if you have a redundant setup with two 80 kW UPS, this value is
2N. {table-cell} {table-row} {table-row} {table-cell:} *Redundancy "+1" kW Increment* {table-cell} {table-cell:colspan=2|}Identifies the loss in kilowatt
caused by internal redundancy. (Only needed if redundancy option includes +1.) For example, if you have a 40 kW UPS with one spare 10 kW
power module, this value would be 10 kW. {table-cell} {table-row} {table-row} {table-cell:} *Derate Capacity fraction* {table-cell}
{table-cell:colspan=2|}Identifies the usable fraction of the nameplate value that can be used in this subsystem. For example, if you use a 20%
safety margin, this value would be 0.8. {table-cell} {table-row} {table-row} {table-cell:} *Typical PU* {table-cell} {table-cell:colspan=2|}Identifies the
power usage (PU) of this subsystem relative to the total power usage. {table-cell} {table-row} {table-row} {table-cell:} *Fixed loss* {table-cell}

{table-cell:colspan=2|}Identifies the fraction of power that is the fixed loss of the subsystem. {table-cell} {table-row} {table-row} {table-cell:}
*Proportional loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost proportional to the load of the subsystem.
{table-cell} {table-row} {table-row} {table-cell:} *Square Law loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost
proportional to the square of the load of the subsystem. {table-cell} {table-row} {table-row} {table-cell:} *Dry bulb fixed loss* {table-cell}
{table-cell:colspan=2|}Identifies the fraction of power that is lost per degree Celsius dry bulb. {table-cell} {table-row} {table-row} {table-cell:}
*Script* {table-cell} {table-cell:colspan=2|}Opens the script editor for editing scripts for this subsystem. {table-cell} {table-row}{table} ||See also||
[Energy System Configuration]

StruxureWare Central Integration

{excerpt:hidden=false}You can integrate {multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} with one or more
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} servers.{excerpt} You must set up the server integration in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. # Select *System Setup>External System Configuration* # Add the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server details to enable communication between the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server and
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}. # Repeat the addition of server details for each
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server, if you want to integrate with more servers. ||See also||
[StruxureWare Operations - Energy Efficiency] [Configuring external system integration]

Database Integration
{excerpt:hidden=false}You can integrate {multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} with any JDBC or ODBC
compliant database. To do this, you must configure a data provider in the startup script.{excerpt} ||See also|| [StruxureWare Operations - Energy
Efficiency] [Sample Startup Script for Database Integration] [Sample Simple Database Query Script] [Sample Database Query Script]

Sample Startup Script for Database Integration

{excerpt:hidden=false}The configuration of the data provider, such as a database, is done in the startup script. {excerpt} You may need to add
additional database drivers to connect to the database, if the generic drivers shipped with
{multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} are not sufficient. Place these files in the folder /opt/jboss-as/server/isxo/lib
on the server. The sample script shows you how to connect to a Microsoft SQL database. The additional database drivers are located in the file
sqljdbc.jar, and the class name of the database driver is SQLServerDriver. Replace these values with values of choice to integrate to other
databases. {noformat} /* * Copyright (c) 2011 Schneider Electric. * * DISCLAIMER: The sample code described herein is provided on an "as is"
basis, without warranty of * any kind, to the fullest extent permitted by law. Schneider Electric does not warrant or * guarantee the individual
success developers may have in implementing the sample code on their development * platforms or in using their own Web server configurations.
* * Schneider Electric does not warrant, guarantee or make any representations regarding the use, * results of use, accuracy, timeliness or
completeness of any data or information relating to the * sample code. Schneider Electric disclaims all warranties, express or implied, and in
particular, * disclaims all warranties of merchantability, fitness for a particular purpose, and warranties related * to the code, or any service or
software related thereto. * * APC by Schneider Electric shall not be liable for any direct, indirect or consequential damages or costs * of any type
arising out of any action taken by you or others related to the sample code. */ /* * This script shows how to load the database driver for the MS
SQL database. * * The file and class names will vary between database providers. Please consult the documentation of * the JDBC driver
applicable to your database system of choice for further information. */ // Make the necessary classes available to the script
importPackage(com.apc.e2m.server.scripting); // Define location of driver file driverFile = "sqljdbc.jar"; // Add the driver to the classpath
ScriptClassPath.addFile(driverFile); // Load the driver class java.lang.Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); {noformat}

Sample Simple Database Query Script

{excerpt:hidden=false}An example of how to perform a simple database query from a
{multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} script.{excerpt}{noformat} /* * Copyright (c) 2011 Schneider Electric. * *
DISCLAIMER: The sample code described herein is provided on an "as is" basis, without warranty of * any kind, to the fullest extent permitted by
law. Schneider Electric does not warrant or * guarantee the individual success developers may have in implementing the sample code on their
development * platforms or in using their own Web server configurations. * * Schneider Electric does not warrant, guarantee or make any
representations regarding the use, * results of use, accuracy, timeliness or completeness of any data or information relating to the * sample code.
Schneider Electric disclaims all warranties, express or implied, and in particular, * disclaims all warranties of merchantability, fitness for a
particular purpose, and warranties related * to the code, or any service or software related thereto. * * Schneider Electric shall not be liable for any
direct, indirect or consequential damages or costs * of any type arising out of any action taken by you or others related to the sample code. */ /* *
This script shows how to make a simple connection to an MS SQL database * and read measurements using SQL * * The database drivers
(JDBC drivers) should be loaded in the startup script. An example of this is available * in the file databasedriver.js in the startup folder. * * This
script assumes that the MS SQL database driver has been loaded. */ // Make Java SQL classes available to the script importPackage(java.sql); //
Define connection properties // The properties needed to connect to the database and the format of the connection URL differ // between different
database. Please consult the documentation of the JDBC driver for the database used // for specific information on this matter username =
"user1"; password = "password1"; server = "159.215.173.127"; port = 1134; databaseName = "sample"; connectionUrl = "jdbc:sqlserver://" +
server + ":" + port + ";databaseName=" + databaseName + ";user=" + username + ";password=" + password + ";" // Create a connection to the
database connection = DriverManager.getConnection(connectionUrl); // Create a statement to execute SQL // The sample database contains the
Measurements table with two columns: measurement_id and measurement_value // We want to extract the value of the measurement with id
11111111 sql = "SELECT measurement_value FROM measurements WHERE measurement_id = '11111111'"; // Create and execute statement
statement = connection.createStatement(); result = statement.executeQuery(sql); // Move cursor to first result and retrieve the value of
measurement_value result.next(); value = result.getDouble("measurement_value"); // Return measurement returnValue = value; //Release
resources result.close(); statement.close(); connection.close();{noformat}

Sample Database Query Script

{excerpt:hidden=false}An example of how to retrieve data from a database and calculate an average.{excerpt}{noformat} /* * Copyright (c) 2011
Schneider Electric. * * DISCLAIMER: The sample code described herein is provided on an "as is" basis, without warranty of * any kind, to the
fullest extent permitted by law. Schneider Electric does not warrant or * guarantee the individual success developers may have in implementing
the sample code on their development * platforms or in using their own Web server configurations. * * Schneider Electric does not warrant,
guarantee or make any representations regarding the use, * results of use, accuracy, timeliness or completeness of any data or information

relating to the * sample code. Schneider Electric disclaims all warranties, express or implied, and in particular, * disclaims all warranties of
merchantability, fitness for a particular purpose, and warranties related * to the code, or any service or software related thereto. * * Schneider
Electric shall not be liable for any direct, indirect or consequential damages or costs * of any type arising out of any action taken by you or others
related to the sample code. */ /* * This script shows how to make a simple connection to an MS SQL database * and read measurements using
SQL * * The database drivers (JDBC drivers) should be loaded in the startup script. An example of this is available * in the file databasedriver.js in
the startup folder. * * This script assumes that the MS SQL database driver has been loaded. */ // Make Java SQL classes available to the script
importPackage(java.sql); // Define connection properties // The properties needed to connect to the database and the format of the connection
URL differ // between different database. Please consult the documentation of the JDBC driver for the database used // for specific information on
this matter username = "user1"; password = "password1"; server = "159.215.173.127"; port = 1134; databaseName = "sample"; connectionUrl =
"jdbc:sqlserver://" + server + ":" + port + ";databaseName=" + databaseName + ";user=" + username + ";password=" + password + ";" // Create a
connection to the database connection = DriverManager.getConnection(connectionUrl); // Create a statement to execute SQL // The sample
database contains the Measurements table with two columns: measurement_id and measurement_value // We want to extract the value of the
measurement with id 11111111 sql = "SELECT measurement_value FROM measurements WHERE measurement_id = '11111111'"; // Create
and execute statement statement = connection.createStatement(); result = statement.executeQuery(sql); // Move cursor to first result and retrieve
the value of measurement_value result.next(); value = result.getDouble("measurement_value"); // Return measurement returnValue = value;
//Release resources result.close(); statement.close(); connection.close();{noformat}

Web Service Integration

{excerpt:hidden=false}You can set up {multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} to retrieve values from SOAP
compliant web services. {excerpt} To enable web service integration, you must configure a data provider in the startup script. This data provider
must provide information on how to communicate with the web service. This information can be found in the WSDL file describing the web service
to be called. ||See also|| [StruxureWare Operations - Energy Efficiency] [Sample Startup Script for Web Service Integration] [Sample Data
Retrieval Script for Web Service Integration]

Sample Startup Script for Web Service Integration

{excerpt:hidden=false}The configuration of the data provider, such as a web service, is done in the startup script. {excerpt} {noformat} /* *
Copyright (c) 2011 Schneider Electric * * DISCLAIMER: The sample code described herein is provided on an "as is" basis, without warranty of *
any kind, to the fullest extent permitted by law. Schneider Electric does not warrant or * guarantee the individual success developers may have in
implementing the sample code on their development * platforms or in using their own Web server configurations. * * Schneider Electric does not
warrant, guarantee or make any representations regarding the use, * results of use, accuracy, timeliness or completeness of any data or
information relating to the * sample code. Schneider Electric disclaims all warranties, express or implied, and in particular, * disclaims all
warranties of merchantability, fitness for a particular purpose, and warranties related * to the code, or any service or software related thereto. * *
Schneider Electric shall not be liable for any direct, indirect or consequential damages or costs * of any type arising out of any action taken by you
or others related to the sample code. */ /* * This script shows how to configure the Web Service Data Provider in the startup * script to ensure that
is available to subsequent scripts */ // Make the data provider class available to the script
importPackage(com.apc.e2m.server.dataproviders.webservice); // Configure data provider webserviceConfiguration = new
WebserviceDataProviderConfiguration(); // Location of WSDL file
webserviceConfiguration.setWsdl("http://ws.cdyne.com/WeatherWS/Weather.asmx?wsdl"); // Name of web service interface as specified in the
WSDL - namespace and local part webserviceConfiguration.setInterfaceName("http://ws.cdyne.com/WeatherWS/", "WeatherSoap"); // Name of
binding as specified in the WSDL - namespace and local part webserviceConfiguration.setBindingName("http://ws.cdyne.com/WeatherWS/",
"WeatherSoap12"); // Name of operation to invoke as specified in the WSDL - namespace and local part
webserviceConfiguration.setOperationName("http://ws.cdyne.com/WeatherWS/", "GetCityWeatherByZIP"); // Add data provider to list of providers
com.apc.e2m.server.dataproviders.DataProviders.addProvider ("weatherService", new WebserviceDataProvider(webserviceConfiguration));
{noformat}

Sample Data Retrieval Script for Web Service Integration

Error: The XML content could not be parsed. There is a problem at line 68, column 16. Parser message: Unexpected character ' ' (code 32) in
content after '<' (malformed start element?). at [row,col {unknown-source}]: [68,16]

Energy Efficiency Dashboard

{section}{column:width=50%}{excerpt:hidden=false}The Energy Efficiency Dashboard shows a graphical representation of the IT load, current
PUE/DCiE, historical PUE/DCiE, costs and CO2 emission per subsystem of an energy system according to the configuration done in the
{multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} application.{excerpt} For information about the energy efficiency concepts
used on the dashboard, such as Power Usage Effectiveness (PUE) and Data Center Infrastructure Efficiency (DCiE), go to: [the Green
Grid|http://www.thegreengrid.org/] and read the [White Papers|http://www.apc.com/go/promo/whitepapers/index.cfm]. * WP-157: Selecting an
Industry-Standard Metric for Data Center Efficiency * WP-154: Electrical Efficiency Measurement for Data Centers * WP-114: Implementing
Energy Efficient Data Centers * WP-113: Electrical Efficiency Modeling for Data Centers {column} {column:width=50%}
!EEdashboard.png|thumbnail! {column} {section} || 123 Steps to... || See also || | *Using the Energy Efficiency Dashboard* \\ The settings below
the graphs on the dashboard define the data (for example energy system and time period) that will be displayed in the graphs. # Open the Energy
Efficiency Dashboard in a browser. # In the *Current PUE* / *Current DCiE* tab, use the *Dial Settings* option below the graphs to select the time
period for which to average the measurements for the dial, and select the energy system for which you want to display the measurements. # In
the *Historical PUE* / *Historical DCiE* tab, use the *Graph settings* options to define the time period and resolution of the graph, and select the
energy system for which you want to display the measurements. Resolution is measured in time and defines the detail level of the graph. #*
Decrease the resolution if you want to increase the detail level. #* Increase the resolution if you want to decrease the detail level. If you are using
PUE as metric, the graph shows the PUE up to 5. If the calculated PUE is greater than 5, the calculated value is displayed and the dial shows the
maximum value possible (5). Before performing the next step, make sure that you have selected a country in the energy system's *> Properties*
*> General* *> Location*. # In the *Subsystem Cost* tab, use the *Graph settings* options to define the time period, kWh cost, and CO2 emission,
and select the energy system for which you want to display the measurements. #* Click *Get price and CO2 emission* to have the system update
the currency, cost per kWh, and CO2 per kWh fields based on your input and on the country selection in the energy system's *> Properties* *>
General* *> Location*. #* If you switch between multiple energy systems, remember to click *Get price and CO2 emission* after selecting another
energy system to get the latest data for the selected energy system. #* Type customized values rather than using the standard values for the
selected country, if the standard values do not apply to the configured energy system. \\ \\ {tip:icon=false}*Tip*: You can toggle the metric between

PUE and DCiE in *> Tools* *> Preferences* *> General*.{tip} | [Exporting dashboard graphs to an external web site] [Customization of exported
dashboard graphs] [StruxureWare Operations - Energy Efficiency]|

Exporting dashboard graphs to an external web site

{excerpt:hidden=false}The graphs from the dashboard can be exported to any web site, for example to an Intranet site.{excerpt} # Open the
dashboard in a browser. # Right-click the image that you want to export and select *Properties*. # Copy the address (URL) to paste into the
location of your choice. # Modify one or more parameters if you want to customize the graph, for example the size of the image. ||See also||
[Energy Efficiency Dashboard]

Customization of exported dashboard graphs

Error: The XML content could not be parsed. There is a problem at line 10, column 36. Parser message: Unexpected character '>' (code 62)
expected '=' at [row,col {unknown-source}]: [10,36]

StruxureWare Operations - Lab

{section}{column:width=50%}{multi-excerpt-include:pageTitle=Branding|name=ISXTL|nopanel=true} is a separate application you can use to
simulate changes to data center models without affecting the model of the actual live environment in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application. The
{multi-excerpt-include:pageTitle=Branding|name=ISXTL|nopanel=true} client application is available from the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page. You need a valid
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license to log on to the application. You can use the
{multi-excerpt-include:pageTitle=Branding|name=ISXTL|nopanel=true} to simulate different scenarios, for example, whether the design is strong
enough to cover your future requirements. If you continue to add equipment at the current pace, would the power supply suffice, or would you
need additional power supplies or cooling units; would you continue to have the necessary redundancy, etc. You can simulate future scenarios in
the existing model of the live environment from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, or you can delete it to start
a new lab model from scratch. Subsequently, when you launch the application, and at least one lab model has previously been saved, a dialog
box will appear asking you to select the model that you want to open. You will be working in a separate environment, similar to the one you know
from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. However, as this is a separate test environment only, you will not
have all features available that you know from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: - No
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} features - No view of device and alarm data - No measured data from
devices (Capacity calculations are purely based on computed data, i.e. on the load you input into model, not measured values collected from the
devices.) - No reports Your changes to lab models do not affect the model of the actual live environment in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application. However, any changes to available products in the catalog will
subsequently be available in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application. To simulate changes to a product
that you want to continue to use in its original version in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, make a copy and
use it as a template for a new product in the {multi-excerpt-include:pageTitle=Branding|name=ISXTL|nopanel=true}. You can delete any obsolete
lab models in File > Manage Models.{column}{column:width=50%} !lab.jpg|thumbnail! {column}{section} || 123 Steps to... || See also || | *Installing
StruxureWare Operations - Lab* \\ The {multi-excerpt-include:pageTitle=Branding|name=ISXTL|nopanel=true} client application is available from
the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page. # Open a Web browser and type the
address of your {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server: https://yourservername. # On the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page, click LAB Download and follow the
instructions to download the {multi-excerpt-include:pageTitle=Branding|name=ISXTL|nopanel=true} client. You can now proceed to logging on to
the application with the same credentials as for {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.| [Designing simulations in
StruxureWare Operations - Lab] |

Designing simulations in StruxureWare Operations - Lab

{excerpt:hidden=false}Simulations designed and edited in the {multi-excerpt-include:pageTitle=Branding|name=ISXTL|nopanel=true} exist only as
separate simulation solutions and do not affect the data center model of the live environment created in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application.{excerpt} When you launch the application, it will open a copy of
the existing data center model of the live environment from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. If you have
more rooms designed, a dialog box will appear asking you to select the room or rooms that you want to open. Subsequently, when you launch the
application, and at least one solution has previously been saved, a dialog box will appear asking you to select the solution that you want to open.
# To simulate how planned changes would affect the existing {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} data center
model without affecting it: ## In the Open Solution dialog box, select *Current StruxureWare Operations solution* and click *Open*. (This step is
not necessary if you launch the application without any previously saved solutions, as the application opens a copy of the existing
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} data center model.) ## Perform the desired edits, e.g. adding equipment.
## Select *File* *> Save as* and type a file name. # To edit a previously saved test simulation: ## In the Open Solution dialog box, select
*Existing {multi-excerpt-include:pageTitle=Branding|name=ISXTL|nopanel=true} solution* and click *Open*. ## Perform the desired edits, e.g.
adding equipment. ## Select *File* *> Save*. ||See also|| [StruxureWare Operations - Lab] [Installing StruxureWare Operations Lab|StruxureWare Operations - Lab]

StruxureWare Operations - Insight

{section}{column:width=50%}{excerpt:hidden=false}{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} is a separate report
design application in which you can configure and design custom reports in addition to the standard built-in reports available in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application.{excerpt} The
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} client application is available from the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page. You need a separate license for this
product. You will be working in a separate environment, based on a 3rd party report design tool (BIRT) that looks quite different from the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} Suite. {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}
includes the option to publish the configured report designs to {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} provides default templates, data sources, data sets, and filter parameters
predefined for you. If you are an advanced user or expert in scripting and designing reports, you can create your own data sources, data sets, and

reports but this is not supported. For generic information about how to use the 3rd party features, refer to the built-in help system. You should
already have a working knowledge about scripting or find it easy to acquire this knowledge. {column}
{column:width=50%}!Insight.jpg|thumbnail!{column}{section} ||See also|| [Customizing report designs] [Working with reports]

StruxureWare Operations - Mobile

{section}{column:width=50%}The {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} application allows you to use a mobile
device to work with the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application, including add-on
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} and
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} functionality. Do not confuse
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} with {multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true}.
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} allows you to work with
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} on-the-fly and synchronize changes with the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, whereas the
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} app allows you to monitor data center operations through read-only KPI
data using an iPhone. {column} {column:width=50%}!mobile.jpg!{column}{section} {section} {column:width=30%} h5. Installation and logon
[Installing StruxureWare Operations - Mobile on the mobile device] [Logging on to StruxureWare Operations - Mobile] [Troubleshooting logon
problems] [Troubleshooting operational problems] h5. Local mode [Working in local mode] [Synchronizing local changes] [Troubleshooting
connection and synchronization problems] {column} {column:width=30%} h5. Alarms [Viewing alarms on StruxureWare Operations Mobile|Alarms on StruxureWare Operations - Mobile] [Enabling or disabling Pop-up Alarm Notifications] [Closing Active Alarm Notifications] h5.
Asset management [Adding Equipment] [Connecting Equipment] [Defining customized properties for a piece of equipment] [Deleting Equipment]
[Moving Equipment] [Canceling a pending change|Working with Pending Changes on StruxureWare Operations - Mobile] [Executing a pending
change|Working with Pending Changes on StruxureWare Operations - Mobile] {column} {column:width=30%} h5. Scanning [Scanning equipment
bar codes into StruxureWare Operations - Mobile] [Troubleshooting scan problems] h5. Rack audit [Performing a Rack Audit] {column} {section}
||See also|| [StruxureWare Operations - VIZOR]

Installing StruxureWare Operations - Mobile on the mobile device

{excerpt:hidden=false}How to install {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}.{excerpt} # In the Web browser on the
mobile device, specify the URL of the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server. # On the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page, click *Download* in the Mobile box to
download the application to the mobile device. {tip:icon=false}*Note*: You must have a valid license for the module to be available for
download.{tip} 3. Follow the on-screen instructions to install it. If the mobile device is not connected to a wireless network, it must be securely in
its cradle when you install the application. The cradle must be connected to a computer that is on your network and is running Microsoft
ActiveSync or Windows Mobile Device Center (WMDC) for Windows Vista. You can now proceed to logging on to the application on the
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} logon page. ||See also|| [StruxureWare Operations - Mobile]

Logging on to StruxureWare Operations - Mobile

If you want to launch the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} in another language, select the desired language
in *Start* *> Settings* *> System* *> Regional Settings*. # On the opening screen of the mobile device, select *> Start* *> Programs* *>
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}*. This step is necessary except at installation, when the application starts
automatically at the logon page. # On the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} logon screen: ## Enter the server
name or IP address of your {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server. ## Enter your user name and password,
and select *> Menu* *> Show Password* if you want the password displayed as you enter it. ## If you want to use the high-security access that
Secure Sockets Layer (SSL) provides, select *Use SSL* to enable SSL access. ### If there is no valid SSL certificate on the mobile device,
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} prompts you to accept the required certificate from the server. ### View the
SSL certificates that are on your mobile device by selecting *> Menu* *> SSL Certificates*. ### Delete any certificate that is invalid or expired or
that allows access to a server that you no longer use. ## Select *Local mode* if you want to start the application in local mode. ## Select OK.
||See also|| [Troubleshooting logon problems]

Troubleshooting logon problems

{excerpt:hidden=false}Correcting problems that may occur during logon.{table:border=1|frame=box|} {table-row:align=center}
{table-cell:}*Symptom* {table-cell} {table-cell:}*Explanation* {table-cell} {table-cell:}*Solution* {table-cell} {table-row} {table-row} {table-cell:}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Either of these error messages: * You must enter a user name. * You must enter a
password. * You must enter a server name or IP address. * You must enter a port number. {panel} {table-cell} {table-cell:}One of the fields of the
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} logon screen was blank. {table-cell} {table-cell:}Enter the missing data in
the correct field. {table-cell} {table-row} {table-row} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Either of
these error messages: * The supplied user name/password is not valid. * The specified user does not have permission to log on to this
application. {panel} {table-cell} {table-cell:}You must have a user account at the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server that includes your user name, your password, and permissions
for the user role of {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} Admin. {table-cell} {table-cell:}Try again to log on to
ensure that you entered your password correctly. If the error message occurs again at your second attempt, contact your
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server administrator. {table-cell} {table-row} {table-row} {table-cell:}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Error message: * Could not resolve specified hostname. {panel} {table-cell}
{table-cell:}DNS could not resolve the name of the host computer. {table-cell} {table-cell:}Contact your
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server administrator. {table-cell} {table-row} {table-row}
{table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Error message: * You must accept the SSL certificate in order to
log on.{panel} {table-cell} {table-cell:}You selected *Use SSL* but declined to accept the displayed certificate. {table-cell} {table-cell:}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Try again, and do one of the following as you log on: * For a high-security logon
session, select *Use SSL* and accept the certificate. * For a logon session protected only by an unencrypted username and password, deselect
*Use SSL*. {panel} {table-cell} {table-row} {table-row} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Error
message: * The client and server version do not match. It is advised that you download the client from the specified server.{panel} {table-cell}
{table-cell:}The {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client version has been updated to a later version, and you

should update the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} client. {table-cell} {table-cell:}{panel: borderStyle=none|

borderColor=#FFFFFF| bgColor=#FFFFFF} * In the Web browser on the mobile device, specify the URL of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server. * In the Web browser on the mobile device, specify the URL of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server and add /frontpage to the address. * On the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page, click *Download* in the Mobile box to
download the latest version to the mobile device. * Follow the on-screen instructions to install it. {panel} {table-cell} {table-row}{table} {excerpt}
||See also|| [Logging on to StruxureWare Operations - Mobile]

StruxureWare Operations - Mobile main screen

{excerpt:hidden=false}The main screen that opens when you have logged in to
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} provides access to
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} features as well as add-on
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} and
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} features.{excerpt} * [Alarms|Alarms on StruxureWare Operations Mobile]: Displays a list of alarms on devices in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} that are monitored by
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}. * [Work Orders|Working with work orders]: Displays a list of work orders.
Tap any listed work order to open that work order or select Filter to limit the scope of the work order list to display only a selection of work orders.
\\ \\ {tip:icon=false}*Note*: This is an add-on feature and is available only if you have a valid
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} license.{tip} * [Asset Management|Asset Management]: Enables you to
view, move, edit, or delete equipment in the system. * [Add Equipment|Adding Equipment]: Provides access to the Add Equipment screen that
enables you to add equipment to a rack. * [Rack Audit|Performing a Rack Audit]: Provides access to the Audit screen that enables you to verify
the system information.\\ \\ {tip:icon=false}*Note*: This is an add-on feature and is available only if you have a valid
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} license.{tip} * [Synchronize|Synchronizing local changes]: (Available in
local mode) Synchronizes to update any changes made in {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} on the mobile
device or in the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client installed on the host computer, while the mobile
device was in local mode. {tip:icon=false}*Tip*: In *Menu*, you can toggle server/local mode.{tip} ||See also|| [StruxureWare Operations - Mobile]

Local and server mode

{excerpt:hidden=false}When using {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}, you can work in either local or server
mode. Synchronizing updates {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} data center model with changes made in
local mode through {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} and vice versa. {excerpt} For connection and
synchronization to occur when the mobile device is not on a wireless network that can access the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server: The mobile device must be in its cradle, which must be
connected to a computer that is on the network and running Microsoft ActiveSync or Windows Mobile Device Center (WMDC) for Windows Vista.
h2. Server mode Server mode means that you are working in the database on the server, and any saved changes will immediately be updated in
the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} as well. Any changes made by other users will also be instantly
reflected in {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}. h2. Local mode Local mode means that you are working in a
local copy. It does not require that you have network connection and your changes will not be updated in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} until it is synchronized.
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} will also only receive changes made by other users when synchronized.
||See also|| [Working in local mode] [Synchronizing local changes]

Working in local mode

You can operate the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} application in local mode without accessing the
network to connect to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. The launch to device feature,
however, requires network access. {tip:icon=false}*Recommendation*: Synchronize regularly so you are always working on the updated data
when in local mode. Enable local mode, either in the logon screen or in the main screen *File* menu. \\ \\ To prolong battery lifetime, you can
disable Wi-Fi by deselecting *> Menu* *> Connections...* *> Enable Wi-Fi* in the main screen.{tip} # Work on a local copy of
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} performing any changes that you want. # Synchronize any changes made
to the data center model in either {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} or
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} local mode by selecting *Synchronize* in the
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} main screen. ||See also|| [Local and server mode] [Synchronizing local
changes]

Synchronizing local changes

{excerpt:hidden=false}When you are using {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} in local mode, it is
recommended that you synchronize regularly with the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server to
ensure that you are always working on the updated data center model when in local mode.{excerpt} # Place the mobile device firmly in the cradle.
# Open {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}. # On the main screen, select *Synchronize*. # Select what data
you want to synchronize. For example, if the complete data center model includes many rooms, you can select to only synchronize data for rooms
relevant to you. ## Select if you want to send any changes done while working in local mode on the mobile device to the server. ## Select if you
want to receive any changes happening on the server while you were working in local mode on the mobile device. If you do not need to work on
the complete data center model including all rooms and products, you can exclude the data that you do not need from the synchronization for
better performance. \\ \\ Any deselected items from the server will no longer be available to you when working in the
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} application. * Toggle *Product Catalog* to define if you want to have the
products from the server's product catalog available on the mobile device. * Select or deselect any rooms in the list of rooms in the complete data
center model to define if you want to have these available on the mobile device. * Toggle *Work Orders* to define if you want to have these
available on the mobile device ({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature). ||See also|| [Local and server
mode] [Working in local mode]

Troubleshooting connection and synchronization problems

{excerpt:hidden=false}Correcting connection or synchronization problems that may occur when using the mobile
device.{table:border=1|frame=box|} {table-row:align=center} {table-cell:}*Symptom* {table-cell} {table-cell:}*Explanation* {table-cell}
{table-cell:}*Solution* {table-cell} {table-row} {table-row} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Error
message: * Could not connect to server at specified address. Ensure the specified server is running. {panel} {table-cell} {table-cell:}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}One or more of the following conditions might exist: * The specified server is not
responding because it is not running. * The specified server refused the connection request because it is not a
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. {panel} {table-cell} {table-cell:}Contact your
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server administrator. {table-cell} {table-row} {table-row}
{table-cell:rowspan=3|}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Error Condition: * The mobile device application
cannot connect to or synchronize with the server. {panel} {table-cell} {table-cell:}If the mobile device is on a wireless network, that network may be
experiencing problems, or the server may be off-line. {table-cell} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}
* Ensure that the wireless network is enabled. * Use the ping command from a desktop computer or through the network connection software on
the mobile device to determine whether the server is operating correctly. {panel} {table-cell} {table-row} {table-row} {table-cell:}If the mobile device
is in its cradle, one or more physical connections may be loose. {table-cell} {table-cell:}Ensure that the cable from the cradle is securely attached
and that the mobile device is firmly in the cradle. {table-cell} {table-row} {table-row} {table-cell:}Microsoft ActiveSync or Windows Mobile Device
Center (WMDC) for Windows Vista might be unavailable or not running. {table-cell} {table-cell:}Ensure that ActiveSync or WMDC is available and
running on the computer. {table-cell} {table-row}{table}{excerpt} ||See also|| [Local and server mode]

Alarms on StruxureWare Operations - Mobile

{excerpt:hidden=false}The list of *Alarms*, available from the *Alarms* option on the main screen, displays a list of the alarms on devices in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} monitored by
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} and provides options to open individual alarms for viewing alarm details.
The system will notify you of new alarms occurring.{excerpt} h2. List of Active Alarms You can select to view an alarm, including details and
recommended actions for clearing it by double-clicking it in the list of alarms. Alarm types * Info !ImgAlarmInfo.png!\\ * Warning
!ImgAlarmWarning.png!\\ * Error, Critical, and Failure !ImgAlarmCritical.png!\\ h2. Pop-up Alarm Notifications The system will notify of any new
alarms occurring at any time by showing a notification icon at the top of the screen and a pop-up alarm notification with the alarm text. By
selecting *View...* in the pop-up notification, you can access the Alarm Details screen for further information about the alarm. The pop-up alarm
notifications can be disabled if you do not want to be notified of new alarms while working in
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}, but only have them appear in the list the alarms. || 123 Steps to... || See
also || | *Viewing Alarms* \\ The Alarms screen, accessed through the *Alarms* option on the main screen, allows you to view active alarm data
from {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}. # Tap *Alarms* on the main screen to open the Alarms screen. #
Select a an alarm in the list to open the Alarm Details screen to access the alarm details, such as severity and what time it occurred. # Select
*More* in the bottom menu to see the recommended action on the next screen for how to resolve the alarm. # Select *> Menu* *> Device...* in the
bottom of the screen to launch to the device data on the {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server. # Select *>
Menu* *> Equipment...* in the bottom menu of the screen to browse directly to the associated equipment in *Asset Management* if the alarm is
happening on a device associated with a piece of equipment in the system. | [Closing Active Alarm Notifications] [Enabling or disabling Pop-up
Alarm Notifications] |

Closing Active Alarm Notifications

{excerpt:hidden=false}Existing alarm notifications, informing you of active alarms while working in
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}, can be closed (no longer displayed). {excerpt} When you close alarm
notifications, the icons at the top of the screen will be removed and the active notifications will be ignored. This does not stop new alarms from
occurring, only that the already displayed notifications will be ignored. # To close all active alarm notifications ## In the Main screen, select
*Alarms*. ## In the Alarms screen, select *> Menu* *> Close All Notifications*. # To close the active notification ## Open the pop-up notification
box by selecting the notification icon at the top of the screen. ## Select *Close* to stop displaying the notification for this alarm. ||See also||
[Alarms on StruxureWare Operations - Mobile]

Enabling or disabling Pop-up Alarm Notifications

{excerpt:hidden=false}From the menu in the Alarms screen, you can select to enable or disable alarm notifications to define if you want to be
notified of new alarms while working in {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}.{excerpt} Alarm notification is
enabled by default. A notification will appear at the top of the screen, regardless what screen is open, to notify you of any new alarms. If you no
longer want to be notified of new alarms occurring, you can disable the feature. # In the Main screen, select *Alarms*. # In the Alarms screen,
clear *Menu > Enable Notifications*. # If, at any time, you want to enable the feature, select *Menu > Enable Notifications* to reintroduce it and
toggle the feature on again. ||See also|| [Alarms on StruxureWare Operations - Mobile]

Work Orders on StruxureWare Operations - Mobile

The list of *Work Orders* in the system, available through the *Work Orders* option on the main screen, provides options to filter and open
individual work orders for viewing or editing. This is an add-on feature and is available only if you have a valid
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} license. You can track work order tasks when planning and executing
changes, such as adding, moving or deleting a server. The icons identify the priority of the work order: || High || Medium || Low || |
!iconworkorder_high.gif! | !iconworkorder_medium.gif! | !iconworkorder_low.gif! | Any work order at or past the date requested for completion is
listed in red text. You can select a work order to open it for viewing or editing. You can access filter settings for which work orders to display by
selecting *Filter* in the bottom menu bar. Work orders can be created only through the desktop application. || 123 Steps to... || See also || |
*Viewing or editing a work order* \\ From the Work Orders screen, you can select a work order and open it for viewing or editing. # Select a work
order in the list and tap, hold, and select *Open...* to open it. # In the Work Orders screen, tap the *Tasks* tab to view the task information. # Tap
and hold a task to track or change the status of the task. ## Select *Not Started* !ImgWorkOrderStatusNotStarted.png!\\ if no work has begun on
the task. ## Select *In Progress* !ImgWorkOrderStatusInProgress.png!\\ if the task is started but is incomplete. ## Select *Completed*
!ImgWorkOrderStatusComplete.png!\\ if the task is finished. ## Select *Cancelled* !ImgWorkOrderStatusCanceled.png!\\ if the task is no longer
an active part of the work order, but remains on the list of tasks. # See the *Summary* for overview information about the selected work order. #
Select *More* to review the overall *Work Order Status*. It will automatically change according to the status of the tasks in the work order. You
can only change the status of a work order if no tasks have been defined for it. # Select *More* to open the *Comment* text field and view, add, or
edit comments about the work order. # In the bottom menu bar, select *Apply* to save the changes | [Filtering the work order list] |

Filtering the work order list

{excerpt:hidden=false}You can set up a filter in the Work Orders screen to display only work orders that match your selected criteria.{excerpt} # In
the Work Orders screen, select *Filter...* in the bottom menu bar to access the Work Order Filter screen. # Select temporary filter options: ##
Enter a character string of up to 100 characters in the *Summary* field. This character string will match a character string anywhere in the
*Summary* field of a work order. For example, either Move or PDU will match a work order with Move three PDUs to Rack 6 in the *Summary*
field. ## To select a range of work orders by number, in the *Order Number* section, select *Enable*, and specify the numbers at the start and
end of the range. ## To select a range of dates by which work orders are to be completed, in the Date section, select *Enable*, and specify the
start and end dates of the range by selecting in the pop-up calendar. The temporary settings apply only during the active logon session of
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}. # Select persisted filter options: ## Enter a number in the *Max Count* field
to limit the amount of work orders shown in the filtered list. ## Enter a character string of up to 100 characters in the *Assigned To* field. This
character string will match a character string anywhere in the *Assigned to* field of a work order. For example, John will match work orders
assigned to John Jones and Jane Johnson. ## Select the *Priority*, (*High*, *Medium*, and *Low*) that you want to include in the filtered list, if
they also match the other criteria that you select. ## Select the *Status*, (*Not Started*, *In Progress*, *Completed*, and *Cancelled*) that you
want to include in the filtered list, if they also match the other criteria that you select. The saved settings remain as filter criteria from session to
session until you revise them. # Select *OK* to apply the filter settings and view the filtered list containing only work orders that match all the
filtered criteria. ||See also|| [Work Orders on StruxureWare Operations - Mobile]

Asset Management
{excerpt:hidden=false}The *Asset Management* option on the main screen provides options to view, edit and audit equipment in the data center
model. {excerpt} || 123 Steps to... || See also || | *Viewing Equipment* \\ The Browse screen, accessed from the *Asset Management* option on
the main screen, allows you to view equipment in the data center model and access edit options.{excerpt} # Select *Asset Management* on the
main screen to open the Browse screen. # Select a room to view the racks within that room by double-clicking (or by tapping, holding, and
selecting *Open...*). # Select *Filter* in the bottom menu and select to show all floor-mounted items in the list (*Show All*), or only racks (*Show
Racks*). # Select a row in the *Select Row* list at the top of the Browse screen if the racks in the selected room are placed in multiple rows. #
Select a floor-mounted item such as UPS, PDU, or cooling unit to access details by double-clicking (or by tapping, holding, and selecting
*Open...*) to access details. # Select a rack to view the equipment in that rack by double-clicking (or by tapping, holding, and selecting *Open...*.).
# Select a piece of equipment in a rack by double-clicking a rack (or by tapping, holding, and selecting *Open...*.) to access equipment details,
e.g. for a server or blade enclosure. If you have {multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true}, the stage of a piece of
equipment determines which menu options are available for that item on the Browse screen. For an overview of the icons that identify equipment
stages, see [Equipment Stages]. # To view blade servers in a blade enclosure, continue to drill down by double-clicking the enclosure (or by
tapping, holding, and selecting *Open...*). # To view network routes for a piece of connected network equipment (read-only), select the
equipment, then *> Menu* *> Network*. # To navigate to a specific piece of equipment in the system based on the barcode, scan it with a barcode
scanner, or select *> Menu* *> Search Barcode*, and type the barcode manually. In the bottom menu, you can enable editing capabilities, for
example selecting *Add...* will open the Add Equipment screen. | [Adding Equipment] [Connecting Equipment] [Moving Equipment] [Deleting
Equipment] [Scanning equipment bar codes into StruxureWare Operations - Mobile] |

Scanning equipment bar codes into StruxureWare Operations - Mobile

{excerpt:hidden=false}You can scan a piece of equipment to record it with a unique bar code in the system, or use it for locating an existing piece
of equipment in the system.{excerpt} Depending on the hardware that you use, you can use the scanner of the mobile device or an external
Bluetooth scanner. To enable Bluetooth communication, from the main screen select *Menu* *> Connections...*, select *Enable Bluetooth*, and
select the communication port. For information about pairing the Bluetooth devices, refer to the documentation provided by the manufacturer. #
From a distance of approximately 6 inches (15 centimeters), point the scanner at the bar code. # Press and hold the button that activates the
scanner, either on the mobile device or the external scanner. A beep indicates that the bar code was successfully scanned. If the scanner projects
an image, such as the lighted corners of a rectangle, the bar code to be scanned must be fully within the boundaries of that image. # Review or
edit the equipment details of the scanned equipment, e.g. change the *Name* on the Edit screen. ||See also|| [Asset Management]

Troubleshooting scan problems

{excerpt:hidden=false}How to correct problems that may occur when scanning bar codes.{table:border=1|frame=box|} {table-row:align=center}
{table-cell:}*Symptom* {table-cell} {table-cell:}*Explanation* {table-cell} {table-cell:}*Solution* {table-cell} {table-row} {table-row} {table-cell:}No
response to pressing the button to activate the mobile device's scanner. {table-cell} {table-cell:}The scanning function of
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} may be in conflict with the scanning function of another application.
{table-cell} {table-cell:}Restart the mobile device and reattempt the scan or close the other application that is using the scanning function.
{table-cell} {table-row}{table} {excerpt} ||See also|| [Asset Management]

Adding Equipment
{excerpt:hidden=false}The Add Equipment screen allows you to add equipment to the data center model.{excerpt} # Select by double-clicking, or
tapping and holding a rack name on the Browse screen accessed through *Asset Management* on the main screen, and selecting *Add...*. The
Add Equipment screen opens. # Select an item of equipment to add from the list of latest products or by using *Search* or *Browse* to find it in
the product catalog. #* Select an item of equipment to add from the list of latest products. The available selections are configured through the
product catalog in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. # Select the piece of equipment by double-clicking or
tapping and holding, and display fields for a bar code and name. Specifying values for these fields is optional. ## *Bar Code*: Scan the item's bar
code into this field (or enter the characters of the code manually). ## *Name*: Enter a name to identify the item within your data center
configuration (Rack PDU 1, for example). If you omit this name, the model name of the item is used in screen displays. # Select *Next...* in the
bottom menu bar, and display custom properties. ## Tap and hold, and select to *Add*, *Edit* or *Remove* custom properties on the product that
you are adding. # Select *Next...* in the bottom menu bar, and display the location: room, rack, and location for the item of equipment within the
rack. ## Rack Mount Position: On the drop-down list, select one from the following: ##* *Front* for equipment that uses one or more U-positions
inside the front of the rack. ##* *Right Rear*, *Left Rear*, or *Rear* for equipment that is installed inside the back of the rack. ##* *Top* for
equipment that is on top of the rack. ##* *Not Mounted* for equipment that does not use any U-positions, such as a Rack PDU installed vertically.
## *Bottom U-Position*: For an item being added to the front view only, select the lowest-numbered U-position that the item will occupy. For
equipment that needs multiple U-positions, a U-position is available for selection only if it has enough U-positions above it to fit the equipment. #
Click *OK* to add the item of equipment. # Define if you want to configure a power connection to the equipment. #* If you select *Yes*, the Power

screen opens, in which you can configure how the equipment is connected for power. #* If you select *No*, the equipment will be added to the
specified position in the data center model. ||See also|| [Asset Management]

Connecting Equipment
{excerpt:hidden=false}The Power screen, accessed from the *Asset Management* option on the main screen, allows you to access options to set
up power connections.{excerpt} # Tap *Asset Management* on the main screen to open the Browse screen. # Tap and hold a location's name to
view the rooms in that location. # Tap and hold a room's name to view the racks in that room. # Tap and hold a rack's name to view the equipment
in that rack. # Tap and hold a server or rack PDU to open the Edit screen for this piece of equipment # Select *Power* in the menu, and review
the power connection setup as you may need to change the connection and phase settings. For example, if a server has been moved to a
different rack, verify that it is connected to the correct rack PDU (you might want to either move the connected rack PDU to the same rack or
reconnect the server to a rack PDU in the same rack). ## Tap and hold in the list to access add or remove connection options. ## To remove a
power connection select *Remove*. ## To add a connection select *Add...* and in the *Add Outlet Connection* screen, select between available
rack PDU and phase options. ||See also|| [Asset Management]

Moving Equipment
{excerpt:hidden=false}The Browse screen, accessed from the *Asset Management* option on the main screen, allows you to view equipment in
the data center and access edit options to move equipment.{excerpt} # Tap *Asset Management* on the main screen to open the Browse screen.
# Select a room to view the racks within that room by double-clicking (or by tapping, holding, and selecting *Open...*). # Select a rack to view the
equipment in that rack by double-clicking (or by tapping, holding and selecting *Open...*). # Select a piece of equipment in a rack by
double-clicking (or by tapping, holding and selecting *Open...*). # Select *Move...* in the bottom menu bar. #* To change the room or rack in
which the item is to be located, tap the button labeled with an ellipsis (...) to the right of the location fields and browse to a new location or, if the
field has focus, you can scan the barcode of a rack to select this rack as new location. #* Use the drop-down lists to select a position for the
moved equipment in the selected rack (*Top*, *Right Rear*, *Left Rear*, *Not Mounted*, *Front*, or *Rear*) and, for the front view, the bottom
U-position that the moved equipment will occupy. # Select *OK*. # Select *Power...* in the bottom menu bar to review the power connection setup
as you may need to change the rack PDU and Phase settings. For example, if a server has been moved to a different rack, verify that it is
connected to the correct rack PDU (you might want to either move the connected rack PDU to the same rack or reconnect the server to a rack
PDU in the same rack). ## Tap and hold in the list to access add or remove connection options. ## To remove a power connection select
*Remove*. ## To add a connection select *Add...* and in the *Add Outlet Connection* screen, select between available rack PDU and phase
options. ||See also|| [Asset Management]

Deleting Equipment
{excerpt:hidden=false}The View screen, accessed from the *Asset Management* option on the main screen, allows you to view equipment in the
data center and access edit options to delete equipment.{excerpt} # Select *Asset Management* on the main screen to open the View screen and
navigate to the item that you want to delete. ## Select a room to view the racks within that room by double-clicking (or by tapping, holding, and
selecting *Open...*). ## Select a floor-mounted item such as UPS, PDU, or cooling unit to access details by double-clicking (or by tapping,
holding, and selecting *Open...*) to access details. ## Select a rack to view the equipment in that rack by double-clicking (or by tapping, holding,
and selecting *Open...*.). ## Select a piece of equipment in a rack by double-clicking a rack (or by tapping, holding, and selecting *Open...*.) to
access equipment details. # Select *Delete* in the bottom menu. {tip:icon=false}*Note*: You are always asked to confirm that you want to perform
the deletion. Deleting a piece of equipment removes it completely from the system. You cannot retrieve a deleted item.{tip} Although you cannot
retrieve a deleted item, all actions including deletes performed through {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} are
listed in the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application *Audit Trail* report. [More...|Audit Trail report] ||See
also|| [Asset Management]

Working with Pending Changes on StruxureWare Operations - Mobile

{excerpt:hidden=false}You can execute a pending change configured through the
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} module in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: deletion, move, or addition of a new item for which space has been
reserved in the data center.{excerpt} The pending options are only available if there is equipment that was marked for deletion, moved or added in
Planning IT Change mode ( {multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}). A rack or item of equipment for which a move is pending is displayed in
two locations in {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} : * At the source of the move in black text with equipment
stage of *Pending Move (Source)*. * At the destination of the move in grayed out text with equipment stage of *Pending Move (Destination)*. You
can execute (or cancel) a pending change from either location, but the only values you can change at the destination are those that define the
target location of the pending move. All other values are read-only at the destination and can be changed only at the source location. || 123 Steps
to... || See also || | *Executing a pending change* \\ You can execute a pending change configured through the
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} module in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: deletion, move, or addition of a new item for which space has been
reserved in the data center. # In the View screen, accessed through *Asset Management* on the main screen, tap and hold a piece of equipment
with a pending move displayed at its active (source) location. # Select *Execute Pending Change*.
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} displays the pending destination and prompts you to confirm that you want
the piece of equipment moved. The equipment stage changes from *Pending Move (Source)* or *Pending Move (Destination)* to *Existing* and is
subsequently displayed only at the destination of the move. \\ \\ \\ *Canceling a pending change* \\ You can cancel a pending change configured
through the {multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} module in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. 1. In the View screen, accessed through *Asset Management* on the main
screen, tap and hold a piece of equipment with a pending change displayed at its active (source) location. 2. Select *Cancel Pending Change* to
retract the pending change that is specified through the desktop application for the selected piece of equipment. | [StruxureWare Operations Mobile] |

Assigning tags on StruxureWare Operations - Mobile

You can assign tags to equipment in {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} to categorize types of equipment
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature). 1. Tap *Asset Management* on the main screen to open the
*Browse* screen. 2. Select a room to view the racks within that room by double-clicking the room. 3. Double-click a rack or double-click a piece of
equipment in a rack. 4. Select *Menu>Tags...* to open the list of tags assigned to the selected rack or piece of equipment in the rack. 5. Select

*Add...* to access the list of available tags. 6. Double-click a tag to select it and assign the tag to the selected rack or piece of equipment in the
rack. ||See also|| [Asset Management]

Defining customized properties for a piece of equipment

{excerpt:hidden=false}The *Properties* tab of the Edit Equipment screen lists any customized properties defined for the piece of equipment.
{excerpt} # Access the Edit Equipment screen: ## Select *Asset Management* on the main screen. ## Tap and hold a piece of equipment on the
View Equipment screen and select *Open...*. # Tap the *Properties* tab, then tap *Add...* to add a property and define *Property Name* and
*Property Value*. For example, you could add a property name of Operating System and a property value of Windows XP, or a property name of
Installation Date and a property value of 3/4/08. # If you regret and want to remove a property, tap the property to highlight it in the list, and tap
*Remove*. {tip:icon=false}*Note*: You cannot define customized properties for a piece of equipment with the equipment status of *Pending Move
(Destination)*. To define properties for an item that is to be moved, you must use the *Properties* tab at the item's source location, where it is
displayed with an equipment status of *Pending Move (Source)*.{tip} ||See also|| [Asset Management]

Equipment stages on StruxureWare Operations - Mobile

The stage of a piece of equipment determines which menu options are available for that item on the *View* screen. Here is a brief overview
({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature). {table:border=1|frame=box|} {table-row:align=center}
{table-cell:width=10%}*Icon* {table-cell} {table-cell:width=30%}*Equipment Stage* {table-cell} {table-cell:width=30%}*Description* {table-cell}
{table-cell:width=30%}*Options Available* {table-cell} {table-row} {table-row} {table-cell:}!ImgEquipmentStageExisting.png|align=center!{table-cell}
{table-cell:}Existing {table-cell} {table-cell:}Equipment shown in its current location, with no action pending. It displays in dark gray, indicating that it
occupies the position shown.{table-cell} {table-cell:} * View Rack * Edit Equipment * Delete Equipment {table-cell} {table-row} {table-row}
{table-cell:}!ImgEquipmentStagePendingMoveSource.png|align=center!{table-cell} {table-cell:}Pending Move (Source){table-cell}
{table-cell:}Equipment that is shown in its current location but has a move pending. It displays in dark gray, indicating that it occupies the position
shown.{table-cell} {table-cell:} * View Rack * Edit Equipment * Execute Pending Change * Cancel Pending Change{table-cell} {table-row}
{table-row} {table-cell:}!ImgEquipmentStagePendingMoveDestination.png|align=center!{table-cell} {table-cell:}Pending Move (Destination)
{table-cell} {table-cell:}Equipment shown in its target location for a pending move. It displays in gray (dimmed), indicating that the position shown,
although unoccupied, is reserved for the equipment.{table-cell} {table-cell:} * View Rack * Edit Equipment * Execute Pending Change * Cancel
Pending Change{table-cell} {table-row} {table-row} {table-cell:}!ImgEquipmentStagePendingAdd.png|align=center!{table-cell} {table-cell:}Pending
Add{table-cell} {table-cell:}Equipment shown in its target location for a pending addition (configured through the desktop application with the item
selected from the equipment catalog). It displays in gray (dimmed), indicating that the position shown, although unoccupied, is reserved for the
equipment.{table-cell} {table-cell:} * View Rack * Edit Equipment * Delete Equipment * Execute Pending Change * Cancel Pending Change
{table-cell} {table-row} {table-row} {table-cell:} !ImgEquipmentStagePendingDelete.png|align=center!{table-cell} {table-cell:}Pending
Deletion{table-cell} {table-cell:}Equipment shown in its current location, but with a pending deletion configured through the desktop application. It
displays in dark gray, indicating that it occupies the position shown.{table-cell} {table-cell:} * View Rack * Edit Equipment * Delete Equipment *
Execute Pending Change * Cancel Pending Change{table-cell} {table-row} {table} ||See also|| [Asset Management]

Performing a Rack Audit

{excerpt:hidden=false}You can audit the contents of the racks in your data center, verifying manual bar code scans and system information about
what equipment is in a rack.{excerpt} # Tap *Asset Management* on the main screen to open the View screen. # Select the rack that you want to
audit by tapping it in the list (or by scanning its bar code). # Tap and hold the selected rack, and select *Audit Rack...* to access the Audit screen.
A list of equipment in the rack shows up, all with a status of *Not Verified* (!ImgAuditNotVerified.png! icon). # Scan the equipment in the rack, one
by one. The status icon listed next to the scanned equipment changes to *Verified* (!ImgAuditVerified.png! icon). If you scan a piece of equipment
that has not yet been added to the system, it will be added to the list with a status of *Not in System* ( !ImgAuditNotExisting.png! icon). If you scan
a piece of equipment that already exists in the system but was added to another rack, it will appear with the status of *Misplaced*
(!ImgAuditMisplaced.png! icon). # At any time during the audit, if you want to restart auditing the equipment in the rack, tap *Restart* in the bottom
menu bar. # Review and change the data as needed: #* Select *Location...* to move the server to another position if it is misplaced. #* Close the
Audit Screen to return to Asset Management, tap and hold the selected rack, and select *Open*... to edit, add, or delete equipment. ||See also||
[StruxureWare Operations - Mobile]

Troubleshooting operational problems

{excerpt:hidden=false}How to correct problems that may occur when performing
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} functions.{table:border=1|frame=box|} {table-row:align=center}
{table-cell:}*Symptom* {table-cell} {table-cell:}*Explanation* {table-cell} {table-cell:}*Solution* {table-cell} {table-row} {table-row} {table-cell:}You
experience frequent error messages, or your mobile device interface or the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}
application is frequently unresponsive. {table-cell} {table-cell:}You are working in server mode, and the network connection is unstable.
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} can run with a variety of other applications, but if other applications are too
numerous or too large, insufficient memory can cause errors. {table-cell} {table-cell:}Check your wireless network connection, or connect through
the cradle and switch to local mode to work in a mode that does not require network connection. (Remember to connect and synchronize
regularly.) See your mobile device documentation for instructions on checking memory usage. If memory is insufficient, uninstall unnecessary
applications. {table-cell} {table-row}{table}{excerpt} ||See also|| [StruxureWare Operations - Mobile]

StruxureWare Operations - PRO Pack

{section}{column:width=50%}{excerpt:hidden=false}The PRO-enabled management pack ensures Virtual Machine Manager is aware of critical
physical infrastructure alarms and events and can execute corrective actions to move virtual machines to non-impacted areas within the data
center. {excerpt} {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} offers a consolidated view of the data center's physical
infrastructure. It holds data about the physical location of the equipment in the data center as well as an advanced configuration of for example
power path and alarm data. Combining the data about the modeled physical location from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} with real-time device monitoring data from the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} enables quick assessment of how an alarm on one piece of equipment may
impact other equipment located in the data center. Data is communicated from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to the System Center Operations Manager server. Based on this data,
Microsoft Virtual Machine Manager is then able to move the relevant virtual machines to healthy hosts. For example: * Rack 1 is powered by UPS

A * Rack 2 is powered by UPS B * An alarm is triggered on UPS A * Virtual Machine Manager migrates the virtual machines from hosts in Rack 1
to hosts in Rack 2 that is powered by UPS B {column}{column:width=50%} !systemoverview.png|thumbnail! {column}{section} || See also|| [Initial
Setup of StruxureWare Operations PRO Pack] [Working with StruxureWare Operations PRO Pack]

Initial Setup of StruxureWare Operations PRO Pack

{excerpt:hidden=false}You must perform the installation and configuration process of the
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} before you are able to import it into Microsoft System Center
Operations Manager. When you have set up a profile, you are ready to monitor the health of the virtual machine hosts and implement the
migration of impacted virtual machines to healthy hosts.{excerpt} h2. Installation and data retrieval configuration The
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} installer is available from a location provided by the support team. To
locate the telephone number for the support you need, visit [Contact Us|http://www.apc.com/site/software/index.cfm/Contact/]. Once you have run
the installer, you need to configure the server communication between the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}
server and the Virtual Machine Manager server, and then import the {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true}
into Microsoft System Center Operations Manager. For information on installation, configuration, and general usage of Microsoft System Center
Operations Manager and Microsoft Virtual Machine Manager, refer to the Microsoft documentation.
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} is available for System Center Operations Manager 2007 R2 and
Virtual Machine Manager 2008 R2 as well as for System Center Operations Manager 2012 and Virtual Machine Manager 2012. These versions of
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} are available: * com.apcc.ISXO.PRO.2008R2.mp *
com.apcc.ISXO.PRO.2012.mp A complete configuration of {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} with
{multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license is required (including association of monitored devices from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}). h2. Data configuration in StruxureWare Operations The
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application must be populated with modeled data representing the physical
enterprise infrastructure. This includes objects representing coolers and the physical servers, their location in the data center rack layout, and
their power connections. Once the data center has been modeled with the correct inventory, virtual machine hosts can be associated to the
graphical objects in the layout representing the actual servers. You can make the data available to
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} through web services including a definition of the polling interval. Read
instructions on granting access to web service APIs [here|Granting access to web services API] or read about the web service API
[here|StruxureWare Operations Web Service API]. {tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup
may look a little different from the instructions and images in this user assistance since these have been created for integration with Virtual
Machine Manager 2008 R2.{tip} ||See also|| [StruxureWare Operations - PRO Pack] [Installing StruxureWare Operations PRO Pack] [Configuring
StruxureWare Operations PRO Pack] [Configuring StruxureWare Operations PRO Pack Agent]

Installing StruxureWare Operations PRO Pack

{excerpt:hidden=false}{excerpt} # In a browser, open the download location provided by the support team. To locate the telephone number for the
support you need, visit [Contact Us|http://www.apc.com/site/software/index.cfm/Contact/]. # Download the
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} .msi package to a location on your Microsoft System Center
Operations Manager server. # Run the installer from the selected location. The following files are now installed to the specified location on your
System Center Operations Manager server in a {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} folder, and
StruxureWare Operations PRO Pack configuration is available from *Start* *> StruxureWare Operations PRO Pack* *> Configuration*. *
APC.ISXOCmdlet.dll * APC.ISXOCmdlet.InstallLog * APC.ISXOCmdlet.InstallState * com.apcc.ISXO.PRO.2008R2.mp or
com.apcc.ISXO.PRO.2012.mp * InstallActions.dll * InstallActions.InstallState * IsxoMPConfig.exe * System.Management.Automation.dll To
complete the setup, you must configure the server communication between the
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} and Virtual Machine Manager servers and import the .mp file from the
installed location into Microsoft System Center Operations Manager. If you want to uninstall the
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} at any time, remove it from Microsoft System Center Operations
Manager before you run the uninstaller. After uninstalling the {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true}, the
computer must be rebooted. {tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup may look a little different
from the instructions and images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.{tip}
||See also|| [Initial Setup of StruxureWare Operations PRO Pack] [Configuring StruxureWare Operations PRO Pack] [Configuring StruxureWare
Operations PRO Pack Agent]

Configuring StruxureWare Operations PRO Pack

{excerpt:hidden=false}The setup includes configuring the server communication between the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and Virtual Machine Manager servers.{excerpt} If you selected to launch it
in the installation wizard, the configuration dialog box will open automatically. Otherwise, you can open the configuration dialog box at any time
from *Start* *> StruxureWare Operations PRO Pack* *> Configuration*. # Type the description of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server that you want to display in Microsoft System Center Operations
Manager. # Type the host name of the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server that will be sending location,
power, cooling, and impact data. # Click *Add* and type the host name of the Virtual Machine Manager server or servers that you want to receive
this data and from which you want to send virtual machine data and the port number (if you do not want to use the default port configuration). # To
complete the setup, import the .mp file from the installed location into Microsoft System Center Operations Manager and set up a new profile. #*
Open Microsoft System Center Operations Manager, select *> Administration* *> Management Packs*, open the *Import Management Packs*
dialog box from *> Actions* *> Import Management Packs*, and browse to the location of the StruxureWare Operations PRO Pack.mp file. #* In
*> Administration* *> Run As Configuration*, select *Profiles*. In the list, right-click
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and select *Properties*. Select *Run As Accounts* and click *Add*. Click
*New account with Simple Authentication*, and type the account credentials that match a
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} user with access rights to Web services API. Read instructions on granting
access to web service APIs [here|Granting access to web services API] or read about the web service API [here|StruxureWare Operations Web
Service API]. The {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} is now imported and configured in Microsoft System
Center Operations Manager. It appears in *Monitoring* *> StruxureWare Operations PRO*. {tip:icon=false}*Note*: The list of virtual machine hosts
is not a complete list of all hosts monitored in Microsoft System Center Operations Manager; it is a list of those that have been associated with
modeled objects in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.{tip} You can customize what details to display in

Microsoft System Center Operations Manager from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. Select *StruxureWare

Operations* or *Impacted Virtual Machine Hosts* in *Monitoring* *> StruxureWare Operations PRO*, and select *> Actions* *> Personalize
view...* and select the columns to display in the *Detail View*. {tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012,
your setup may look a little different from the instructions and images in this user assistance since these have been created for integration with
Virtual Machine Manager 2008 R2.{tip} || See also || [Initial Setup of StruxureWare Operations PRO Pack] [Installing StruxureWare Operations
PRO Pack] [Configuring StruxureWare Operations PRO Pack Agent]

Configuring StruxureWare Operations PRO Pack Agent

{excerpt:hidden=false}The agent is installed with the {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true}. You will see an
icon on the task bar when the agent is running.{excerpt} The {multi-excerpt-include:pageTitle=Branding|name=ISXOPROAgent|nopanel=true}
ensures the data from the Virtual Machine Manager server is updated in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} at
the configured frequency, e.g. every 10 minutes (minimum). # Open the agent window by right-clicking the icon on the task bar and selecting
*Show* (or if the agent is disabled, restart it in *Start* *> All Programs* *> Startup* *> StruxureWare Operations PRO Pack*). # Define the interval
of getting updated data from Virtual Machine Manager into {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. Updates
include: * Virtual machine hosts: Addition/removal, switch between maintenance/normal modes * Virtual machines: Addition/move/deletion
{tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup may look a little different from the instructions and
images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.{tip} ||See also|| [Initial Setup
of StruxureWare Operations PRO Pack] [Installing StruxureWare Operations PRO Pack] [Configuring StruxureWare Operations PRO Pack]

Working with StruxureWare Operations PRO Pack

{section}{column:width=50%}{excerpt:hidden=false}Overview of how to work with
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} in the applications involved.{excerpt} Before you can begin using
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true}, you must have finished the installation and configuration process by
completing these steps. # In Microsoft System Center Operations Manager, review the list of configured Virtual Machine Manager servers.
{tip:icon=false}*Note*: The management pack runs discovery tasks at an interval of 4 hours, so it may take a while for the list to refresh.{tip}
{column}{column:width=50%} !SCOM_viewImpactedVMHs.png|thumbnail! {column}{section} {section}{column:width=50%} 2. In
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, review the inventory configuration, power path and alarm setup in the floor
layout. Some hosts are fed by one UPS, others by another UPS. 3. In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, set
up and review the associations between the hosts and the servers representing them in the rack layout. If a host has been associated, there will
be a V icon on it in the layout. If a host is critically impacted, there will be a red V icon on it and a tool tip describing the impact
{column}{column:width=50%} !impacttooltip.JPG|thumbnail! {column}{section} {section}{column:width=50%} 4. In System Center Operations
Manager Virtual Machine Hosts view, review the impact data from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to get an
overview and monitor if the hosts are healthy. 5. In Virtual Machine Manager, monitor the hosts and implement the PRO tips.
{tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup may look a little different from the instructions and
images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.{tip}
{column}{column:width=50%} !VMM_PROtip.png|thumbnail! {column}{section} ||See also|| [StruxureWare Operations - PRO Pack]

Working with Impact Analysis in StruxureWare Operations

{section}{column:width=50%}# Configure the inventory, including the position of your host servers in the rack layout, set up the power path down
to server level, and associate the power source with devices receiving alarms. # Associate the servers in the layout with your virtual hosts by
dragging a server from the *External Systems* pane over the server representing it in the layout. # Review the virtual machine setup. The V icons
on the servers in the layout indicate if the hosts have been associated, and if an impact occurred. {column}{column:width=50%}
!impacttooltip.JPG|thumbnail! {column}{section} ||See also|| [StruxureWare Operations - PRO Pack]

Working with StruxureWare Operations PRO Pack views in System Center Operations
Manager
{excerpt:hidden=false}When the {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} has been imported and configured in
System Center Operations Manager, a {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} folder with two views will be
available.{excerpt} # In *Monitoring*, select {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} and observe the two views
listed. # Click {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and observe the view open with a
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} list view and a *Detail View*.
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} servers that have been set up to communicate with the System Center
Operations Manager server appear in the list.\\ \\ {tip:icon=false}*Note*: These servers appear as Not monitored in this view. However, this does
not mean that the virtual machine hosts are not monitored. It means that the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server itself is not monitored by System Center Operations Manager.{tip} #
Click a list item and observe the details for the selected item. # Click *Impacted Virtual Machine Hosts* and observe the view open with an
*Impacted Virtual Machine Hosts* view and a *Detail View*. Impact analysis data from the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} servers appears in this view. # Click a list item and observe the details for
the selected item. # Right-click *Impacted Virtual Machine Hosts*, and select *Personalize view...* Then select the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} data that you want to display in Virtual Machine Manager, such as *Room
Name*, *Rack Name*, etc. {tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup may look a little different
from the instructions and images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.{tip}
||See also|| [StruxureWare Operations - PRO Pack]

Working with StruxureWare Operations PRO Pack PRO Tips in Virtual Machine Manager
{excerpt:hidden=false}The {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} PRO tips are communicated to Virtual
Machine Manager. You can manually implement the PRO tips, or set up the system to automatically do so. {excerpt} Before you can work with the
PRO tips, you must configure how they should be enabled in the Virtual Machine Manager Administrator Console. In *Administration*, click
*General*, and then click *PRO Settings*, and select *Automatically implement PRO tips* if you want the system to automatically implement the
critical PRO tips. Or if you want the PRO settings to apply to a host group or cluster, in *Hosts* or *Virtual Machines*, right-click the group or

cluster and select *Properties* *> PRO*.\\ {tip:icon=false}*Note*: The option for the system to receive PRO tips of severity level *Critical Only* or
*Warning and Critical* does not have any effect on {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} PRO tips as only
impacts of severity level of critical are received.{tip} # Click *PRO Tips* in the toolbar to open the *PRO Tips* window to view active PRO tips for
the host groups that you are administering. # Select the PRO tip, and review the details about the issue that caused the PRO tip and how to
resolve the issue. # Click *Implement* to implement the recommended action to resolve the issue, or click *Dismiss* to remove the tip and close
the *PRO Tips* window. If you have configured the PRO tips to be automatically implemented, the issues are automatically resolved and the PRO
tips are removed. You can troubleshoot any issues with discovery, monitoring or recovery in the Event Viewer Application log.
{tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup may look a little different from the instructions and
images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.{tip} ||See also||
[StruxureWare Operations - PRO Pack]

Troubleshooting virtualization issues

{excerpt:hidden=false}You can troubleshoot any {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} issues in the Event
Viewer Application log. Type of events that you might see: * Discovery * Monitoring * Recovery h2. Why don't I see all my virtual machine hosts in
the list in Microsoft System Center Operations Manager? * The list of virtual machine hosts is not a complete list of all hosts monitored in
Microsoft System Center Operations Manager. It is a list of those that have been associated with modeled objects in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.\\ \\ *
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} retrieves data from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} at a specified polling interval. If you do not see all the virtual machine hosts
that you expect to see, wait for the specified period of time and the view will be updated with the latest data. ** Discovery: 4 hours ** Monitoring:
30 seconds h2. I get many reports of impacted virtual machine hosts. What could be the cause of this? Ensure the configuration represents the
real-world physical environment as accurately as possible. For example, the system will reflect the real-world more accurately if you configure
power connections all the way down to the server level than if you stop at the rack PDU level. If the system is missing the server connection data,
it will use the information available. It will report more impacts because it does not know which servers are connected to which rack PDUs. * If a
rack PDU in a rack is critically impacted by an alarm, the system will assume that all servers are connected to that rack PDU are impacted by the
alarm. * If there are two rack PDUs in a rack, the system will assume that all servers with redundancy are connected to these two rack PDUs are
impacted by the alarm. h2. Virtual Machine Manager does not migrate virtual machines to a host. What could be the cause of this? If a host
outside a cluster was previously impacted, {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} changed the status of this
host from available for placement to unavailable. Once you have resolved the issue and the host is healthy, you must make it available again: In
Virtual Machine Manager, right-click the host in *Virtual Machines* *> Host Groups*, select *Properties* *> Status*, and select *This host is
available for placement*.{excerpt} {tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup may look a little
different from the instructions and images in this user assistance since these have been created for integration with Virtual Machine Manager
2008 R2.{tip} ||See also|| [StruxureWare Operations - PRO Pack]

StruxureWare Operations PRO Pack PRO tip implementation rules

{excerpt:hidden=false}List of recovery rules applied for virtual machine hosts in or outside clusters.{excerpt} {table:border=1|frame=box|}
{table-row} {table-cell}Hyper-V hosts in a cluster {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} * If
there are hosts in a cluster, impacted hosts are put in maintenance mode. * Virtual machines on those hosts are migrated within the cluster.
{panel} {table-cell} {table-row} {table-row} {table-cell}Hyper-V hosts outside a cluster {table-cell} {table-cell}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF} * If there are hosts outside a cluster, the recovery script finds potential hosts and virtual machines are
migrated from the impacted host. * The status of the impacted host is changed from available to unavailable.{panel} {table-cell} {table-row}
{table-row} {table-cell}Stand-alone Hyper-V host in a cluster {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF|
bgColor=#FFFFFF} * If there is one host in a cluster, the virtual machines on the host will be put in saved state and the host is still put in
maintenance mode. * Virtual machines on that host are not migrated from that host.{panel} {table-cell} {table-row} {table-row}
{table-cell}Stand-alone Hyper-V host outside cluster {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} *
If there is a stand-alone host outside a cluster, an error message is displayed in the PRO tip. ** PRO cannot migrate virtual machine (virtual
machine name) because no other hosts are available in the host group or host cluster. ** PRO cannot migrate a virtual machine. * The status of
the impacted host is changed from available to unavailable.{panel} {table-cell} {table-row} {table-row} {table-cell}Multiple Hyper-V hosts in
maintenance mode {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} * If multiple hosts are being
impacted at the same time, a PRO tip is created for each impacted host. The PRO tips will be automatically implemented if automatic
implementation of PRO tips has been configured. Otherwise, you should manually implement the PRO tips. {panel} {table-cell} {table-row}
{table-row} {table-cell}Virtual machine is excluded from PRO host-level action {table-cell} {table-cell}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF} * If there are Hyper-V hosts in a cluster that have been set to be excluded from PRO host-level
action, the hosts are put in maintenance mode. This means that Virtual Machine Manager will still migrate these virtual machines. * If there are
Hyper-V hosts outside a cluster that have been set to be excluded from PRO host-level action, Virtual Machine Manager will not migrate these
virtual machines.{panel} {table-cell} {table-row}{table} {tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup
may look a little different from the instructions and images in this user assistance since these have been created for integration with Virtual
Machine Manager 2008 R2.{tip} ||See also|| [StruxureWare Operations - PRO Pack]

StruxureWare Operations - PRO Pack Supported Alarm Types

{excerpt:hidden=false}These standard alarm types are supported in
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true}.{excerpt} {tip:icon=false}*Note*: The alarms with the exact wording as
listed are supported. Any alarms with a different wording will not be recognized by the
{multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true}. However, it is possible to customize the critical alarm and threshold
configuration for migration of impacted servers.{tip} {table:border=1|frame=box|} {table-row} {table-cell}APC/MGE UPS{table-cell}
{table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} * The battery power is too low to continue to support the load;
the UPS will transfer to Bypass. The load will be powered by Bypass AC. * The battery power is too low to continue to support the load; the UPS
will shut down if input power does not return to normal soon. * The battery power is too low to support the load; if power fails, the UPS will be shut
down immediately. * Lost the management interface-to-UPS communication while the UPS was on battery. * The load exceeds 100% of rated
capacity. * A battery fault exists. * On battery power in response to an input power problem. * The UPS failed its diagnostic self-test, due to either
an overload or poor battery health. Symmetra MW: * Alarm low battery warning. * Alarm Overload. {panel} {table-cell} {table-row} {table-row}

{table-cell}Liebert{table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} * The system has detected an

overload condition. * The system has performed an emergency transfer to bypass. * This system has detected an overload condition. * This
system has detected Output to Load is in an overload condition. * This system has detected Output overload condition. * The system has detected
a self-test failure. * Overload error present on at least one phase of static bypass switch. * The battery capacity is low. * The system has detected
a battery low shutdown error. {panel} {table-cell} {table-row} {table-row} {table-cell}APC Coolers{table-cell} {table-cell}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF} InRow RC: * Cooling failure exists * Condensate pan full fault exists * On standby, input contact fault
exists InRow RD: * A cooling failure exists. * A unit type conflict alarm exists. InRow RP: * Cooling failure exists. * On standby, an input contact
fault exists. * High discharge pressure alarm exists. * Compressor drive fault exists. InRow SC: * Cooling failure exists. * A persistent high
discharge pressure alarm exists. * A persistent low suction pressure alarm exists. * A startup low suction pressure alarm exists. * A startup line
pressure imbalance alarm exists * On standby, an input contact fault exists. {panel} {table-cell} {table-row} {table-row} {table} ||See also||
[StruxureWare Operations - PRO Pack]

StruxureWare Operations - VIZOR

{section}{column:width=50%}The {multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} app is available for real-time graphical
presentation of power, cooling, network, and space capacity utilization. It allows you to monitor data center operations through read-only KPI data
on your iPhone, iPad, or smartphone with Android. Using your phone, you can access the data from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to: * Drill down to a location or room * Trend capacity utilization over time *
See a prediction of remaining days of capacity at current growth rate for a location or room (applies to iPad version) * Access asset inventory and
details * Use a built-in barcode scanner to easily identify assets Do not confuse
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} with StruxureWare Operations: Mobile. The
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} app allows you to monitor data center operations through read-only KPI
data using an iPhone, iPad or smartphone with Android, whereas {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} allows
you to work with {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} on-the-fly and synchronize changes with the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. h2. Prerequisites for valid data in
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} * You must have a working connection to the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. * The
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} that you connect to must have the required configurations for the
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} to be able to show the data. ** Required space data: You must have at least
a room with a rack setup. ** Required power data: Power properties on equipment in the system and valid power path setup. ** Required cooling
data: Cooling properties on equipment in the system. ** Required network data: Configured network properties on equipment in the system and
network connections. ** Required measured data: In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, you must have
communication setup with an external monitoring system, such as {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} to
retrieve the measured data. You must configure associations between the devices with measured data and equipment in the data center layout. **
Trending data: You must have data from a period of time before the trending data will be meaningful, and
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} must be set up to save KPI data over time. h2. Installing the
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} app on your phone or iPad Download the
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} app from Android Market or Apple App Store. h2. Setting up the
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} app The first time you start the
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} app, you must establish connection to the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. * In the *Settings* page, that appears the first time you start
the app, enter: ** {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server name \\ On a smartphone with Android, you
must enter the IP address as DNS aliases are not supported. ** Port number \\ Port 443 is not supported. ** User name and password If the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server has been set up behind a firewall, the
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} app needs to be running with your smartphone or iPad setup for VPN or on
a local WIFI network behind the firewall. If, at any point, you want to change the
{multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} settings: * On an iPhone, go to the home screen, and click on *iPhone
Settings*. {multi-excerpt-include:pageTitle=Branding|name=Vizor|nopanel=true} will be listed there. * On a smartphone with Android, click the
Android options menu, and select *Settings*. {column} {column:width=50%}!Power.png|thumbnail! {column}{section} ||See also|| [Saving KPIs
over time] [StruxureWare Operations - Mobile]

StruxureWare Operations - Dashboard

{section}{column:width=50%}The {multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true} provides a customizable CEO-level
overview of the data center operations. The dashboard runs on Mozilla Firefox 4 and later versions. You can configure the dashboard by choosing
between a selection of predefined portlets showing different {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} KPI data and
adding these to the dashboard. You can also use the Data Center KPI portlet for more advanced custom portlets. You can apply specific themes
and designs to match your company profile. The open platform based on the Liferay platform makes it possible to bring in other data center
metrics as well according to your needs. !Configuring the room layout^video24x20.jpg! Watch this [video tutorial|Video
Tutorials#installingdashboardvideo] to see how to get started with the installation, or read more [here|Installing the StruxureWare Operations
Dashboard]. !Configuring the room layout^video24x20.jpg! Watch this [video tutorial|Video Tutorials#configdashboardvideo] to see how to get
started with the configuration, or read more [here|Configuring the initial setup of the StruxureWare Operations - Dashboard]. Only features related
to the {multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true} are described here. For further details about Liferay features,
refer to the [Liferay documentation|http://www.liferay.com/documentation]. {column} {column:width=50%} !dashboard.png|thumbnail! {column}
{section} ||See also|| [Installing the StruxureWare Operations Dashboard] [Configuring the initial setup of the StruxureWare Operations Dashboard] [Configuring StruxureWare Operations KPI tabs and portlets] [Configuring a tab slide show on the dashboard] [Configuring the
dashboard theme] [Hiding the cursor on the dashboard] [Hiding the tool icons on the dashboard] [Hiding the welcome page on the dashboard]
[Changing the dashboard administration credentials] [Displaying the configured dashboard on a screen] [StruxureWare Operations - VIZOR]
[Saving KPIs over time]

Installing the StruxureWare Operations Dashboard

To install the {multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}, first install the Liferay portal, then download the

{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} DashboardAddons .zip file. The .zip file contains the

{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} data for the portlets and theme for the look-and-feel of the dashboard. You
must have a valid {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license on the server for the
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true} to be available for download. {tip:icon=false}{*}Recommendation*:
Install the Liferay platform on another server than the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server.{tip}
Ensure the server can [look up the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server|Troubleshooting
StruxureWare Operations - Dashboard issues]. Liferay is based on Java and is supported on all common operating systems, such as Windows
XP and later versions, Debian. It requires 4 GB RAM but you can run it on almost any computer. If you decide to install both
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and Liferay on the same server, you may experience performance issues.
Read instructions [here|Installing the StruxureWare Operations Dashboard on the StruxureWare Operations server] on installing the
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true} on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. Follow the below steps or !Configuring the room
layout^video24x20.jpg! watch this [video tutorial|Video Tutorials#installingdashboardvideo] to see how to get started with the installation. #
Download the Liferay Portal Community Edition 6.0 GA4 (Bundled with Tomcat)
[here|http://www.liferay.com/downloads/liferay-portal/available-releases]. The
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true} should also work on later versions of Liferay. However, this is not
supported yet as it has not been thoroughly tested. # Extract the .zip file to a location on your computer, e.g. C:\Liferay, and open the folder. #
Download the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} DashboardAddons-7.1.0-\[buildnummer\].zip. file from the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's download page. Type the IP address of the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server in a Web browser to open the server's download page. # Copy
the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} files from the .zip file into this folder: C:\Liferay\deploy. # Open a
command prompt and run the startup script to launch Liferay. ## Select *Start>Run...* and type {{cmd}}. ## Type {{c:}} and press Enter. ## Type
{{cd \Liferay\tomcat-6.0.29\bin}} and press Enter. ## Type {{startup.bat}} and press Enter. Liferay opens in a Web browser on the Welcome page
and you are ready to proceed with the [configuration|Configuring the initial setup of the StruxureWare Operations - Dashboard]. || See also ||
[StruxureWare Operations - Dashboard|StruxureWare Operations - Dashboard] [Configuring the initial setup of the StruxureWare Operations Dashboard|Configuring the initial setup of the StruxureWare Operations - Dashboard] [Troubleshooting StruxureWare Operations - Dashboard
issues|Troubleshooting StruxureWare Operations - Dashboard issues]

Installing the StruxureWare Operations Dashboard on the StruxureWare Operations server

# Download the Liferay Portal Community Edition 6.0 GA4 (Bundled with Tomcat)
[here|http://www.liferay.com/downloads/liferay-portal/available-releases]. The
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true} should also work on later versions of Liferay. However, this is not
supported yet as it has not been thoroughly tested. # Extract the .zip file to a location on your computer, e.g. C:\Liferay, and open the folder. #
Open the C:\Liferay\liferay-portal-6.0.6\tomcat-6.0.29\conf folder. # Locate the server.xml file and replace it with [this file|^server.xml]. The file
contains necessary new port details for the configuration as the standard port configuration is already in use. # Use a compression application,
such as 7-Zip, to compress the C:\Liferay folder to tar format. # Upload the compressed tar file from step 5 to the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server through the Webmin server management interface. ## Open
the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's Webmin web interface by typing the address of the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server followed by :10000 in a Web browser,
https://yourservername:10000. ## Log on to Webmin using the root credentials (default root/apc). To change the password, see [here|Enhancing
security on the StruxureWare Operations server]. ## In the left menu, select *System>Upload and Download*. ## In the *Upload to server* tab:
### In *Files to upload*, browse to the location of the .tar file. ### In *File or directory to upload to*, type /Liferay, and select *Create directory if
needed*. ### Answer the question *Extract archive or compressed files?* with *Yes, then delete*. ### Select *Upload*. # Download and extract
the StruxureWare Operations Dashboard Addons-7.1.0-\[buildnumber].zip. file from the StruxureWare Operations server's download page. Type
the IP address of the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server in a Web browser to open the server's
download page and click *Download* on the Dashboard image. # Upload the extracted .war files to the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server /Liferay/liferay-portal-6.0.6/deploy folder: ## Open Webmin. ##
In the *Upload to server* tab: ### Browse to the location of one .war file, then the next .war file in the *Files to upload* field. ### In the *File or
directory to upload to* field, type /Liferay/liferay-portal-6.0.6/deploy, and select *Create directory if needed*. ### Select *Upload*. # Open [this
file|^liferay] (no extension), for example with Notepad, and upload it to the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server /etc/init.d folder in the same way as described in step 8 for
uploading the .war files. The file contains the startup script. # Log on to the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server with an SSH client. For example, use PuTTY. You can
download it from [here|http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]. ## Navigate to the init.d folder: Type {{cd /etc/init.d}}
and press Enter. ## Type the command {{chmod 755 liferay}} and press Enter. ## Type the command {{insserv liferay}} and press Enter. ## Type
reboot, and then exit. You can now launch Liferay on the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server by
typing the server's IP address followed by :9080 in a Web browser, https://yourservername:9080. ||See also|| [StruxureWare Operations Dashboard] [Installing the StruxureWare Operations Dashboard]

Configuring the initial setup of the StruxureWare Operations - Dashboard

When Liferay has been installed, the browser opens on the Welcome page and you are ready to proceed with the configuration.
{tip:icon=false}*Tip*: The Sign In fields are at the bottom right corner of the Welcome page.{tip} h2. Signing into Liferay The first time you sign in,
you need to sign in as an administrator to Liferay with the default credentials. # In *E-mail address:*, type {{test@liferay.com}}. # In *Password:*,
type {{test}}. # [Change your credentials|Changing the dashboard administration credentials]. This is recommended for security reasons. If you
accidentally delete the sign in page, see [here|Invoking the sign in page, even if the page was deleted] for instructions on how to invoke it again.
h2. Setting up connection to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server The initial setup also includes
setting up a connection to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server for the Liferay server to get
access to the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} KPI data. # Select *Manage>Control Panel*. # In the *Portal*
section, select *Operations KPI*. # Enter the logon credentials to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true}
server. The system informs you that the connection was successful (*Configuration saved*). # Click *Back to Liferay* in the top left corner to

return to the Welcome page. You now have the initial setup and are ready to start configuring the data to be shown on the dashboard and the look
and feel. ||See also|| [Configuring StruxureWare Operations KPI tabs and portlets] [Configuring the dashboard theme] [Configuring a tab slide
show on the dashboard]

Configuring StruxureWare Operations KPI tabs and portlets

When you have completed the initial setup of the dashboard, the dashboard has a welcome page only. See the below instructions for adding
pages and portlets to the pages. Most of the predefined {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} KPI portlets show
data for one location only. The predefined PUE portlet shows data from one energy system only. You can add multiple portlets to a page to show
data for multiple locations or create an advanced portlet. Using the advanced Data Center KPI portlet, you can create advanced portlets with data
for multiple locations or mix multiple data categories in one graph. The Schneider Electric theme included with the installation displays pages as
tabs, and you can hide tools, etc. and set up the dashboard to show a slide show. h2. Adding a new page # Select *Add>Page*. # Type the page
title and press Enter. If you regret adding a page to the dashboard, go back to the dashboard overview and click the x on the page tab. h2.
Configuring the page layout # Click the page tab. # Select *Manage>Page Layout*. # Select the layout matching the look and feel you want for the
dashboard, e.g. 2 column layout (50/50) or free form. The Liferay default layout is 2 columns (30/70). h2. Adding
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} KPI portlets to a page # Click the page tab. # Select *Add>More*. # Click
*StruxureWare Operations*, and click *Add* next to the portlet you want to add to the page or drag it into the page. # Repeat the above steps, if
you want to add more portlets to the page. h2. Configuring the added {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} KPI
portlets # Click the tool icon and select *Preferences*. # Set the available display options. h2. Configuring advanced KPI portlets # In the list of
available {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} portlets (described above), select to add *Data Center KPI*. #
Perform the same steps as for configuring one of the other predefined portlets, but select multiple locations or multiple data types. For example,
you can show both network and power data for a room, or rack u-space for 2 rooms in the same graph. # Select different types of graphs per data
type or room, e.g. *Dotted Line* for network data and *Line* for power data in the above example. ||See also|| [Configuring the dashboard theme]
[Configuring a tab slide show on the dashboard]

Configuring a tab slide show on the dashboard

You can set up a dynamic dashboard that periodically switches between the different pages. The mentioned slide show add-on is available for
Mozilla Firefox: # In a Web browser, open the [add-on page|https://addons.mozilla.org/en-US/firefox/addon/tab-slideshow/] and click *Add to
Firefox*. # Restart Mozilla Firefox and create a new tab (Ctrl+T) for each dashboard page that you want to include in the slide show, typically, one
tab per page on the dashboard. # Select *Tools>Start Tab Slideshow*. ||See also|| [Configuring the initial setup of the StruxureWare Operations Dashboard]

Configuring the dashboard theme

You can configure the dashboard theme according to your needs. The default Schneider Electric theme is available, if you included the theme file
in the [installation|Installing the StruxureWare Operations Dashboard]. h2. Enabling the Schneider Electric theme # In *Manage>Page*, select
*Look and Feel*. # In *Available Themes*, click the Schneider Electric Theme. h2. Customizing the theme For example, follow the below steps to
change the logo. Prerequisite: Ensure the dimensions of the image file match the theme resolution (123x45 pixels if you have applied the
Schneider Electric theme). # In *Manage>Settings*, select *Logo*. # Browse to the image file you want to use as the logo on the dashboard and
select *Use* and *Save*. The Schneider Electric logo (schneider_electric_123x45.gif) is provided with the installation together with the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} .war files. For general information about how to create a custom theme in
Liferay, refer to the [Liferay documentation|http://www.liferay.com/documentation]. ||See also|| [Configuring the initial setup of the StruxureWare
Operations - Dashboard] [Installing the StruxureWare Operations Dashboard]

Hiding the cursor on the dashboard

On the dashboard displaying the KPI data, you may want to hide cursor. For example, you can use this utility (version 1.5 has been tested on
Windows XP and Windows 7): # In a Web browser, open the utility [download page|http://home.cogeco.ca/~icorrupt/nomousy.html] and download
nomousy.exe. # Open a command prompt and point to the Liferay server. # Type the command {{nomousy.exe /hide}}. ||See also|| [Configuring
the initial setup of the StruxureWare Operations - Dashboard]

Hiding the tool icons on the dashboard

{section}{column:width=50%}On the dashboard displaying the KPI data, you may want to hide configuration tools only needed when configuring
the dashboard. Click *Toggle Edit Controls* at the top of the page. At any time, click it again to toggle and make the icons reappear.{column}
{column:width=50%} !togglecontrols_layered.png|thumbnail! {column}{section} ||See also|| [Configuring the initial setup of the StruxureWare
Operations - Dashboard]

Hiding the welcome page on the dashboard

On the dashboard displaying the KPI data, you may want to hide configuration tools, such as the sign in portlet and the welcome page. You will
still be able to sign in. # Create at least one other page in Liferay [Configuring StruxureWare Operations KPI tabs and portlets]. # Rearrange the
order of the pages, so the welcome page is the last page. ## In *Manage>Control Panel*, select *Pages* in the left pane. ## Select *Display
Order*, move the welcome page down to the list, and click *Update Display Order*. # In *Manage>Page*, select the welcome page and set it to
"Hidden". Now, the welcome page has been removed from the displayed dashboard. You can still access the welcome page to sign in or out by
using this URL: http://localhost:8080/web/guest/home (Replace localhost:8080 with Liferay server:port). ||See also|| [Configuring the initial setup
of the StruxureWare Operations - Dashboard]

Changing the dashboard administration credentials

h2. Changing the default administration credentials # In *Manage>Control Panel*, select *My Account*, or click *Joe Bloggs* in the top right
corner. # In *My Account* page, change the e-mail address. # In the pane to the right, click *Password* and type the current and new password.
||See also|| [Configuring the initial setup of the StruxureWare Operations - Dashboard]

Displaying the configured dashboard on a screen

The computer used for displaying the configured dashboard on a screen must be connected to the screen and run Mozilla Firefox 4.0 or later

version. It could be the Liferay server or another computer. # Open Mozilla Firefox on this computer. # Type the Liferay dashboard address
(http://dashboard_server_ip:8080} into the browser address bar. # Press F11 to allow the browser to take up the full screen. At any time, press
F11 again to toggle full screen on/off. # Set the display options: \\ [Configuring a tab slide show on the dashboard] [Hiding the welcome page on
the dashboard] [Hiding the tool icons on the dashboard] [Hiding the cursor on the dashboard] ||See also|| [Configuring the initial setup of the
StruxureWare Operations - Dashboard]

Accessing the StruxureWare Operations - Dashboard from any computer

You can access the {multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true} from any computer: Type
http://dashboard_server_ip:8080 into the browser address bar. If the welcome page is hidden, you can still access it by using this URL:
http://localhost:8080/web/guest/home (Replace localhost:8080 with Liferay server:port). ||See also|| [Displaying the configured dashboard on a
screen]

Invoking the sign in page, even if the page was deleted

{section}{column:width=50%}If you accidentally delete the sign in page, you can still sign into the
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}: * In a Web browser, type this URL: http://host:port/c/portal/login
(replace host:port with the Liferay server:port). {column} {column:width=50%}Invoked sign in page !invokingsignin.png|thumbnail! {column}
{section}

Troubleshooting StruxureWare Operations - Dashboard issues

h2. *Temporarily unavailable* error when configuring {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} KPI portlets If the
server is not able to look up the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server: * Give the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server a proper DNS name and restart the Operations service. This
method will make the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} portlet data available on any computer running the
dashboard. * Change the host file on the server on which the Liferay dashboard is installed. This method will make the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} portlet data available on any computer running the dashboard: # Log on to
the server with an SSH client. For example, use PuTTY. You can download it from
[here|http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]. # In the console, type {{hostname -f}} and press Enter. It returns
something like {{operations.localdomain}} or {{aspgcnpekn432.apa.gad.schneider-electric.com}}, depending on your setup. # On your local
computer, navigate to the hosts folder {{C:\Windows\System32\drivers\etc\hosts}}. # Open the hosts file and add a new entry, such as: #*
192.168.228.128 operations.localdomain operations or #* 10.219.11.133 aspgcnpekn076.apa.gad.schneider-electric.com aspgcnpekn076
Replace the IP address with the IP address of your {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server and
replace the hostname with the hostname you got when running the hostname command above. # Save the file. # Verify the availability: ## Open a
command prompt: ##* Select *Start>Run...* and type {{cmd}}. ## Ping the hostname: ##* Example: Type {{ping operations.localdomain}} and
press Enter Now you get a ping response, and the portlets are available. ||See also|| [StruxureWare Operations - Dashboard] [Installing the
StruxureWare Operations Dashboard] [Configuring the initial setup of the StruxureWare Operations - Dashboard] [Configuring StruxureWare
Operations KPI tabs and portlets]

StruxureWare Operations Web Service API

The {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} Web Service API is a set of web services that provide access to
various parts of {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. You can access the API documentation
[here|http://dcimsupport.apc.com/ws-javadoc/index.html?index-all.html]. Here is an overview of the methods available along with some illustrative
examples. h2. Web Services Overview To keep the WSDLs (Web Services Description Language) and any stubs generated from them at a
manageable size, the web service API has been partitioned into different areas. || Name || Description || WSDL\* || Java class || |
[Inventory|Inventory Web Service] | Basic access to layout and structure of data center. | webservices/equipment/InventoryWebService-v2?wsdl |
[com.apc.webservice.equipment.v2.InventoryWebService|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/equipment/v2/I
nventoryWebService.html] | | [Power path| Power Path Web Service] | Navigate up\- and downstream in power path. |
webservices/equipment/PowerWebService-v2?wsdl |
[com.apc.webservice.equipment.v2.power.PowerWebService|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/equipment
/v2/power/PowerWebService.html] | | [Custom properties|Custom Properties Web Service] | Access and modify custom properties. |
webservices/customproperties/CustomPropertiesWebService-v2?wsdl |
[com.apc.webservice.customproperty.v2.CustomPropertiesWebService|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/
customproperty/v2/CustomPropertiesWebService.html] | | [Impact|Impact Web Service] | Analyze what happens if e.g. a UPS fails. |
impact/ImpactWebService-v2?wsdl |
[com.apc.webservice.impact.v2.ImpactWebService|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/impact/v2/ImpactWe
bService.html] | | [Capacity History|Capacity History Web Service] | Various key performance indicators through time. |
history/HistoryReportService?wsdl |
[com.apc.webservice.history.HistoryReportService|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/history/HistoryReport
Service.html] | \* The URLs are relative to /isxo/webservices/ on the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true}
server, so for the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, swo001, the URL of the inventory WSDL is:
http://swo001/isxo/webservices/equipment/InventoryWebService-v2?wsdl. If you are working in Java, you can code against our existing
interfaces. You can find these in com.apc.config.webservices-XXX.jar in the application/dropins folder on the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client. Alternatively, generate new stubs based on the WSDLs. You can find
a list of the exposed {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} web services in the Javadoc
[here|http://dcimsupport.apc.com/ws-javadoc/index.html?index-all.html]. It describes in detail what the different methods do, the format and order
of input/output, how they handle border cases, fault modes, etc. {tip:icon=false}*Tip*: Since there are numerous classes corresponding to the
different kinds of input, output, and fault types, use the Java class links in the above table as a starting point.{tip} || See also || [Inventory Web
Service] [Power Path Web Service] [Custom Properties Web Service] [Impact Web Service] [Capacity History Web Service] [Tutorial - Accessing
web service Java API using CXF]

Inventory Web Service

The [inventory web service|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/equipment/v2/InventoryWebService.html] is

suited for browsing the data center in a top-down manner: * Get all rooms * Get all racks and other floor-mounted equipment in a particular room *
Get the equipment in a rack along with some basic properties (label, barcode, u-height,...) A typical use case could be a mobile application that
will list the rooms, allow the user to drill down to one of the rooms, further drill down to a rack in the room, etc. Each web service call provides
keys for the equipment returned that can then be supplied to the next call in either the inventory web service or in some of the more specialized
web services, such as custom properties, simulate impact, or performance history. The inventory web service is the most obvious entry point into
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. See a complete list of inventory web service call snippets [here|Inventory
web service calls] or follow the links in the below text to look up a specific web service call. {composition-setup} h2. {toggle-cloak:id=WSRooms}
Rooms {cloak:id=WSRooms} In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, you operate with different types of rooms: *
server rooms * electrical rooms * store rooms You typically want to access data from the server rooms. To get this data, use
[{{getAllServerRooms}}|Inventory web service calls#F2.1] with no arguments. It returns all server rooms. Similar methods exist to get the other
kinds of rooms: * {{getAllElectricalRooms}} returns all electrical rooms * {{getAllStorages}} returns all storages * {{getAllRooms}} returns all three
kinds of rooms {cloak} h2. {toggle-cloak:id=WSRows} Rows {cloak:id=WSRows} A row is an optional level between rooms and racks. If you are
working with a big room, you can group by rows to get an overview. {{getRowsInRoom}} takes the key of a room and returns the rows in the room.
Read more [here|Inventory web service calls#F2.3] and [here|Inventory web service calls#F2.4]. {cloak} h2. {toggle-cloak:id=WSRacks} Racks
{cloak:id=WSRacks} {{getRacksInRoom}} takes the key of a room and returns all racks in the room. Read more [here|Inventory web service
calls#F2.5] and [here|Inventory web service calls#F2.6]. Similarly, {{getRacksInRow}} takes the key of a row and returns all racks in the row.
{cloak} h2. {toggle-cloak:id=WSFlooreq} Other floor-mounted equipment {cloak:id=WSFlooreq} You can use these methods to get typical kinds of
floor-mounted equipment: * UPS: {{getUpsInRoom}} * PDUs: {{getPdusInRoom}} * Power Panels: {{getPowerPanelsInRoom}} * Remote
Distribution Panels (RDPs): {{getRemoteDistributionPanelsInRoom}} * InRow and downflow coolers: {{getCoolersInRoom}} {cloak} h2.
{toggle-cloak:id=WSEqinracks} Equipment in racks {cloak:id=WSEqinracks} You can use these methods to get typical kinds of equipment in
racks: * Servers: {{getServersInRack}} or {{getServersInRoom}} * Blade enclosures: {{getBladeEnclosuresInRack}} * Rack PDUs:
{{getRackMountPdusInRack}} For example, to get the servers in a particular rack, use {{getServersInRack}}. Read more [here|Inventory web
service calls#F2.7] and [here|Inventory web service calls#F2.8]. NOTE: Blades are not considered servers in this regard. Instead, you must
retrieve the blade enclosures and then get the blades from them. Read more [here|Inventory web service calls#F2.6]. {cloak} h2.
{toggle-cloak:id=WSBlades} Blades {cloak:id=WSBlades} You can use these methods to get blades: * Get all blades in a room:
{{getBladesInRoom}} * Get all blades in a blade enclosure {{getBladesInEnclosure}} Read more about how to get blade enclosures
[here|Inventory web service calls#F2.4]. For example, to get the blades in a particular blade enclosure, call {{getBladesInEnclosure}}. Read more
[here|Inventory web service calls#F2.9] and [here|Inventory web service calls#F2.10]. {cloak} h2. {toggle-cloak:id=WSGeneraldcitems} General
data center items {cloak:id=WSGeneraldcitems} In some cases, you might want to get a particular item without knowing exactly what type it is or
where to look for it. {{getDataCenterItems}} takes one or more keys for items that may be of different types. Read more [here|Inventory web
service calls#F2.11]. It returns the items in the order corresponding to the keys. Read more [here|Inventory web service calls#F2.12]. {cloak} ||See
also|| [Inventory web service calls] [Inventory By Filter Web Service] [StruxureWare Operations Web Service API]

Inventory web service calls

Error: The XML content could not be parsed. There is a problem at line 201, column 30. Parser message: Undeclared namespace prefix "soap" at
[row,col {unknown-source}]: [201,30]

Inventory By Filter Web Service

In addition to the [Inventory web service methods|Inventory Web Service], the Inventory web service contains a more powerful and general
method, {{getDataCenterItemsByFilter}}. As an alternative to the top-down approach, it supports more ad-hoc lookups, such as: * Equipment of a
given model * Equipment with a given keyword * Equipment with a particular barcode * Arbitrary combinations such as: *# Equipment of a given
model with a given keyword *# Equipment of a given model or with a given keyword *# Equipment of a given model without a given keyword h2.
Inventory Filters Overview || Element || Description || |modelName|[Model name, e.g. PowerEdge 2500|#modelname1]{anchor:modelname2}|
|barcode|Barcode, see 3.1.2| |contained|Equipment within other items, see 3.2| |productType|Equipment of a particular type, see 3.3|
|customProperty|Equipment with a particular custom property, see 3.5| |device|Equipment associated with a
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} device, see 3.6| |not|Equipment not matching a filter criterion, see 3.7.1|
|or|Equipment matching all criteria in a list of filters, see 3.7.2| A filter request example searching by model name is shown [here|Inventory by filter
web service calls#F3.1] and the response is similar to the other Inventory responses, see [here|Inventory by filter web service calls#F3.2]. The
available types of filters are listed in the above overview. A particular filter can only be of one type, but filters can be combined into a new filter.
{composition-setup} h2. {toggle-cloak:id=WSBasicprops} Basic properties {cloak:id=WSBasicprops} *Model name* When [filtering by model
name|#modelname2]{anchor:modelname1}, you must write the exact model name. It is case sensitive. *Barcode* To get equipment with a
particular bar code (e.g. 12345678), make a request as shown [here|Inventory by filter web service calls#F3.3]. Since bar codes must be unique
in the system, we expect this to return at most one piece of equipment. {cloak} h2. {toggle-cloak:id=WSContained} Contained in other equipment
{cloak:id=WSContained} To get equipment contained within another item, make a request as shown [here|Inventory by filter web service
calls#F3.4]. The type of equipment returned depends on the type of the containing item: * Rooms and rows give floor-mounted equipment (racks,
etc.) * Racks give rack-mounted equipment (servers, blade enclosures, etc.) * Blade enclosures give blades The {{recur}} option is optional and
defaults to false. If enabled, it will also return the equipment within the contained equipment. For example, a rack gives blades in addition to
servers and blade enclosures. {cloak} h2. {toggle-cloak:id=WSProdtype} Product type {cloak:id=WSProdtype} To get e.g. all racks, make a call as
shown in [here|Inventory by filter web service calls#F3.5]. See how to get all available product types
[here|http://dcimsupport.apc.com/ws-javadoc/classcom_1_1apc_1_1webservice_1_1equipment_1_1v2_1_1filter_1_1_data_center_item_filter_v_
o.html]. {cloak} h2. {toggle-cloak:id=WSKeywords} Keywords {cloak:id=WSKeywords} To get all equipment with the tag "foo", make a call as
shown [here|Inventory by filter web service calls#F3.6]. {cloak} h2. {toggle-cloak:id=WSCustomprops} Custom properties
{cloak:id=WSCustomprops} To get all equipment for which the custom property "foo" has value "bar", make a call as shown [here|Inventory by
filter web service calls#F3.7]. {cloak} h2. {toggle-cloak:id=WSDevices} Devices {cloak:id=WSDevices} When used in its most basic form, just
adding a device term returns any equipment associated with a {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} device as
shown [here|Inventory by filter web service calls#F3.8]. The device element can have one or more of the following nested elements to further limit
the search: * name: limits the name (label) of the device * type: limits the type of the device* * state: limits the state of the device* * hostName:
limits the hostname of the device * ip: limits the IP address of the device The IP address can either be a specific one or denote a range. * location:
limits the location of the device NOTE: This refers to the device location, not the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} location. See [here|Inventory by filter web service calls#F3.9] for a more
advanced example. It gives all equipment associated with a UPS on subnet 10.216.2-3.*. *See all available types
[here|http://dcimsupport.apc.com/ws-javadoc/classcom_1_1apc_1_1webservice_1_1equipment_1_1v2_1_1filter_1_1_device_filter_v_o.html].

{cloak} h2. {toggle-cloak:id=WSCombi} Combinations {cloak:id=WSCombi} You can combine filters into new filters with negations, conjunctions
and disjunctions. You can combine these, in turn, into new filters, and so forth. Arbitrary nesting is supported as illustrated as shown
[here|Inventory by filter web service calls#F3.13]. *Negation* A negation gives all equipment that does *not* match a certain filter. To get e.g. all
equipment without a particular tag, make a call as shown [here|Inventory by filter web service calls#F3.10]. The {{not}} tag can contain the same
things as the filter tag. A negation in itself might not be useful since it may yield a large amount of (irrelevant) equipment. It typically makes more
sense to put it in a conjunction to further limit the result. *Conjunctions* A conjunction gives all equipment that matches all of one or more filters.
See how to get all PowerEdge 2600 servers tagged "foo" [here|Inventory by filter web service calls#F3.13]. *Disjunction* A disjunction gives all
equipment that matches any of one or more filters. See how to get all equipment that is either a PowerEdge 2600 or has the tag "foo" or both
[here|Inventory by filter web service calls#F3.12]. {cloak} ||See also|| [Inventory by filter web service calls] [Inventory Web Service] [StruxureWare
Operations Web Service API]

Inventory by filter web service calls

h2. Sample filter request{anchor:F3.1} {code:language=xml}
Generic Rack
{code} h2. Sample filter response{anchor:F3.2} {code:language=xml}
d68e7bb0-e490-4005-a0c8-429e09b066bf A/room/myLocation/ R-1 f651f873-bd4d-4096-9d0c-741c480bd508 Generic Generic Rack GEN_RACK
R-1 125000.0 42 29 1000000.0 0 304090.0 13
{code} h2. Lookup by barcode{anchor:F3.3} {code:language=xml}
12345678
{code} h2. Lookup by containing item{anchor:F3.4} {code:language=xml}
d68e7bb0-e490-4005-a0c8-429e09b066bf True
{code} h2. Lookup by product type{anchor:F3.5} {code:language=xml}
Rack
{code} h2. Lookup by keyword{anchor:F3.6} {code:language=xml}
foo
{code} h2. Lookup by custom property{anchor:F3.7} {code:language=xml}
foo bar
{code} h2. Get equipment with any device association{anchor:F3.8} {code:language=xml}
{code} h2. Get equipment associated with specific device type on subnet{anchor:F3.9} {code:language=xml}
10.216.2-3.* UPS
{code} h2. Negation example{anchor:F3.10} {code:language=xml}
foo
{code} h2. Conjunction example{anchor:F3.11} {code:language=xml}
PowerEdge 2600 foo
{code} h2. Disjunction example{anchor:F3.12} {code:language=xml}
PowerEdge 2600 foo
{code} h2. Example of using combinations{anchor:F3.13} {code:language=xml}
Generic Server usage accounting foo
{code} ||See also|| [Inventory By Filter Web Service]

Power Path Web Service

The [power path web
service|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/equipment/v2/power/PowerWebService.html] allows navigating
through the power path. E.g., from a rack PDU, you can get information about the servers connected to it (downstream) or the PDU it connects to.
The starting point for reading power paths is the key of the equipment. To get the key, use the [Inventory web service|d2cDCO70:Inventory Web
Service]. The methods will also give information about the phase and breaker rating when applicable. The methods only return the power path
one level ahead, so to get a complete power path, you might need multiple successive calls. However, you can batch the calls to get the
immediate up/downstream for multiple consumers/providers by supplying multiple keys. The output is ordered by the keys and each part of the
output holds the key of the consumer/provider. {composition-setup} h2. {toggle-cloak:id=WSDownstream} Downstream {cloak:id=WSDownstream}
The {{getPowerConsumers}} method takes the key of a (presumed) power provider and returns the equipment connected to it. Read more
[here|Power path web service calls#F4.1] and [here|Power path web service calls#F4.2]. {cloak} h2. {toggle-cloak:id=WSUpstream} Upstream
{cloak:id=WSUpstream} The {{getPowerProviders}} takes the key of a (presumed) power consumer and returns its power providers. Read more
[here|Inventory web service calls#F4.3] and [here|Inventory web service calls#F4.4] Depending on the type of equipment and redundancy, there
will be one or two power providers. {cloak} ||See also|| [Power path web service calls] [StruxureWare Operations Web Service API]

Power path web service calls

h2. Request to get power consumers{anchor:F4.1} {code:language=xml}
cff9f354-4255-4b41-b642-2cefe4cc5af5
{code} h2. Response with power consumers{anchor:F4.2} {code:language=xml}
cff9f354-4255-4b41-b642-2cefe4cc5af5 0022fd97-64ba-4b8d-9676-9c978ba1e489 MyServer U-15/R-3/room/ MyServer baf61696-0fea-4256-8a3
5-02e9b6fbb25e Generic Generic Server GEN_SER 0.0 MyServer 10000.0 Front Mounted 1 15 L1 cdd87dff-1aed-4da9-ac8b-00c5170c64d9 My
SecondServer U-11/R-3/room/ MySecondServer baf61696-0fea-4256-8a35-02e9b6fbb25e Generic Generic Server GEN_SER 0.0 MySecondSer
ver 10000.0 Front Mounted 1 11 L1
{code} h2. Request to get power providers{anchor:F4.3} {code:language=xml}
cff9f354-4255-4b41-b642-2cefe4cc5af5
{code} h2. Response with power providers{anchor:F4.4} {code:language=xml}
cff9f354-4255-4b41-b642-2cefe4cc5af5 10.0 57e45e9e-6b22-46fd-a0e8-49908835c4e4 MyPdu -/room/ MyPdu 6e68b049-f509-4309-a2c8-ace4f7
56673d Generic Generic PDU GEN_PDU MyPdu 100000.0 AC 60 208 L1
{code} ||See also|| [Power Path Web Service]

Custom Properties Web Service

The [custom properties web

service|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/customproperty/v2/CustomPropertiesWebService.html] is a
separate web service for performance reasons and to avoid expanding the inventory web service. The starting point for accessing custom
properties is the key of the equipment. To get the key, use the [Inventory web service|Inventory Web Service] and [Inventory by filter web
service|Inventory By Filter Web Service]. {composition-setup} h2. {toggle-cloak:id=WSReading} Reading {cloak:id=WSReading} You can use the
{{getCustomProperties}} method to get the custom properties for a particular data center item. If you need the custom properties for several items,
it might be faster to batch them into one call. The method {{getCustomPropertiesForMultiple}} accepts the keys of multiple items and returns their
custom properties in the order corresponding to the order of the keys. The method {{getCustomPropertiesIn}} takes the key of a room and returns
all custom properties for all equipment in this room. The method {{getAllCustomProperties}} returns all custom properties for all equipment
altogether. Only call this method for small solutions or when custom properties are used sparingly. {cloak} h2. {toggle-cloak:id=WSModifying}
Modifying {cloak:id=WSModifying} Custom properties can also be modified through web services. This is useful for example for batch jobs that
import data from a third party system into custom properties in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. See
[here|Custom properties web service calls#F5.3] for an example to add or overwrite two custom properties. If you do not use the value element,
you remove the custom property. Read more [here|Custom properties web service calls#F5.4]. As with reading, there is a variant
{{setCustomPropertiesForMultiple}} to add, modify or remove custom properties for multiple items at a time. {cloak} ||See also|| [Custom
properties web service calls] [StruxureWare Operations Web Service API]

Custom properties web service calls

h2. Request to get custom properties{anchor:F5.1} {code:language=xml}
b74a8e93-9f75-405e-ae39-3ed738ecf9a6
{code} h2. Response with custom properties{anchor:F5.2} {code:language=xml}
usage accounting
{code} h2. Adding/changing custom properties{anchor:F5.3} {code:language=xml}
b74a8e93-9f75-405e-ae39-3ed738ecf9a6 usage HR ip 127.0.0.1
{code} h2. Removing a custom property{anchor:F5.4} {code:language=xml}
b74a8e93-9f75-405e-ae39-3ed738ecf9a6 ip
{code} ||See also|| [Custom Properties Web Service]

Impact Web Service

The [impact web service|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/impact/v2/ImpactWebService.html] is analogous
to the *Simulate Impact* right-click menu in the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client. It analyzes what
happens if one or more items fail. The method {{simulateImpact}} takes the key of the items. See an example [here|Impact web service
calls#F6.1]. To get the key of the item, use the [Inventory web service|Inventory Web Service] and [Inventory by filter web service|Inventory By
Filter Web Service]. The response contains the keys of the impacted equipment and a summary of the impact. See an example [here|Impact web
service calls#F6.2]. The key can then be fed into e.g. {{getDataCenterItems}} in the [Inventory web service|Inventory Web Service] to get more
information about the impacted equipment. The analysis depends on the item type: * Power providers (UPS, PDUs, etc.): equipment supplied by
this particular power provider is impacted. Depending on the setup, power will either be lost completely or the redundancy will degrade. See an
example of the latter [here|Impact web service calls#F6.2]. * Cooling equipment: cooling will be lost for servers if their inlet temperature exceeds a
certain threshold as a result of the cooling failure. You can configure the threshold in *Tools>Preferences>Cooling Impact* in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client. If the servers already had a too high inlet temperature, the system
does not consider them impacted as that particular cooler was not the tipping point. The cooler might not cause the servers to exceed the
threshold. But if it means that it will now lose cooling if another cooler fails, the system indicates that cooling redundancy was lost. If a UPS
supplies a cooler, the cooler will fail and the system analyzes the effect of the chain reaction. {composition-setup} h2.
{toggle-cloak:id=WSCombinedimpact} Combined impact {cloak:id=WSCombinedimpact} To produce the combined impact, you can supply
multiple keys. For example, in a 2N power setup, the impact of both power feeds failing would be that servers completely lose power instead of
just redundancy. Read more [here|Impact web service calls#F6.3] and [here|Impact web service calls#F6.4]. A more advanced example is the
combined impact of a UPS and cooler failure: * Cooling loss if the UPS is not a supplier of the servers. * Cooling and power redundancy loss if the
UPS is a supplier of the servers in a 2N setup. * Power loss if the UPS is the sole supplier of the servers, but not cooling loss since the servers no
longer produce heat if they lose power. ||See also|| [Impact web service calls] [StruxureWare Operations Web Service API]

Impact web service calls

h2. Request to simulate impact{anchor:F6.1} {code:language=xml}
69b50b87-94f2-401e-bf15-234e66ecbac1
{code} {tip:icon=false}*Note*: The key refers to a UPS.{tip} h2. Response from simulating impact{anchor:F6.2} {code:language=xml}
2ca0d9a5-775a-4626-9615-fcd315c220a2 Warning WARNING Warning Redundancy lost Warning WARNING Warning ...
{code} h2. Request to simulate combined impact{anchor:F6.3} {code:language=xml}
69b50b87-94f2-401e-bf15-234e66ecbac1 c82de629-c5a3-44cc-b286-d2f932468db1
{code} h2. Response from simulating combined impact{anchor:F6.4} {code:language=xml}
2ca0d9a5-775a-4626-9615-fcd315c220a2 Critical CRITICAL Critical Power lost Critical CRITICAL Critical ...
{code} ||See also|| [Impact Web Service]

Capacity History Web Service

The [capacity history web service|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/history/HistoryReportService.html]
provides access to a number of figures, either the present (latest) or through time. Here are a few examples: * Available u-space for a rack or an
entire room * Available network ports for a rack or an entire room * The (calculated) remaining cooling capacity for a single cooling unit or an
entire room You can obtain keys for rooms or equipment with the [Inventory web service|Inventory Web Service]. The system computes the
figures at a regular schedule. You can configure the schedule in *Tools>Preferences>Capacity History* in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client. {composition-setup} h2. {toggle-cloak:id=WSTimeseries} Time series
{cloak:id=WSTimeseries} To get the figures as a time series, use the {{getTimeSeries}} method. See an example [here|Capacity history web
service calls#F7.1]. The method takes the following parameters: * fromTime: limits to points at or after this time, indicated in milliseconds since
January 1st 1970. Omit this for no limit. * toTime: limits to points at or before this time. Omit this for no limit. * itemUuid: is the key of the
equipment or room. You can supply multiple values. This will give one time series per item corresponding to the order of the keys. Read more
[here|Capacity history web service calls#F7.3] and [here|Capacity history web service calls#F7.4]. * type: is a key indicating the figure. Read more

[here|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/history/Type.html]. You can supply multiple values. This gives

multiple values per time series corresponding to the order of the keys. See examples [here|Capacity history web service calls#F7.3] and
[here|Capacity history web service calls#F7.4]. *Padding* The system only stores performance figures when there has been an actual change.
Also, if you request figures in the period 2 to 3 PM but they are only computed daily at 12 pm, there will not be any data points within the period of
the request. To alleviate callers from having to cope with this, time series are padded by the following rules: * If you specify {{fromTime}}, a data
point is added at that time with the newest known value before it. This is why there is a data point at 1325372400000 in this [example|Capacity
history web service calls#F7.2]. * If you specify {{toTime}} (and not in the future), a data point is added at the end. This is because, if we recorded
for example available rack u-space to 38 at 12 PM and then ask for the u-space between 2 and 3 PM the next day, 38 is the best "guess" for 2
PM. If you do not want this behavior, you can override the padding rules by using {{getTimeSeriesPadding}} instead of {{getTimeSeries}}. See an
example [here|Capacity history web service calls#F7.5]. {cloak} h2. {toggle-cloak:id=WSNewdata} Newest data {cloak:id=WSNewdata} Rather
than a looking at a time series, you can look at whichever is the newest data. This is provided by the {{getNewest}} method. Read more
[here|Capacity history web service calls#F7.6] and [here|Capacity history web service calls#F7.7]. It takes the following parameters: * beforeTime:
limits to points before or at this time. Omit this for no limit. * itemUuid and type: are exactly as for time series (see above). You can supply multiple
values. {cloak} ||See also|| [Capacity history web service calls] [StruxureWare Operations Web Service API]

Capacity history web service calls

h2. Request to get u-space through time for a rack{anchor:F7.1} {code:language=xml}
1293836400000 1325372400000 4da5485f-4bc6-4194-8fa8-9bc7a6053b52 AVAILABLE_USPACE
{code} h2. Response with u-space through time for a rack{anchor:F7.2} {code:language=xml}
4da5485f-4bc6-4194-8fa8-9bc7a6053b52
1319114096903 39.0
1319114205512 38.0
1325372400000 38.0
{code} h2. Request to get multiple time series for multiple items{anchor:F7.3} {code:language=xml}
1293836400000 1325372400000 4da5485f-4bc6-4194-8fa8-9bc7a6053b52 AVAILABLE_USPACE
{code} h2. Response with multiple time series for multiple items{anchor:F7.4} {code:language=xml}
4da5485f-4bc6-4194-8fa8-9bc7a6053b52
1319114096903 39.0 20.0 ... d68e7bb0-e490-4005-a0c8-429e09b066bf
20.0 ...
{code} h2. Specify padding rules{anchor:F7.5} {code:language=xml}
1293836400000 1325372400000 4da5485f-4bc6-4194-8fa8-9bc7a6053b52 AVAILABLE_USPACE true false
{code} h2. Request to get newest figure{anchor:F7.6} {code:language=xml}
1325372400000 4da5485f-4bc6-4194-8fa8-9bc7a6053b52 AVAILABLE_USPACE
{code} h2. Response with newest figure{anchor:F7.7} {code:language=xml}
4da5485f-4bc6-4194-8fa8-9bc7a6053b52
1319114205512 38.0
{code} ||See also|| [Capacity History Web Service]

1319018544145 42.0

Tutorial - Accessing web service Java API using CXF

Error: The XML content could not be parsed. There is a problem at line 9, column 11. Parser message: Unexpected character ',' (code 44)
excepted space, or '>' or "/>" at [row,col {unknown-source}]: [9,11]

Troubleshooting
{excerpt-include:Troubleshooting error messages} {excerpt-include:Troubleshooting performance issues} {excerpt-include:Troubleshooting
virtualization issues} {excerpt-include:Troubleshooting scan problems} {excerpt-include:Troubleshooting operational problems}
{excerpt-include:Troubleshooting logon problems} {excerpt-include:Troubleshooting connection and synchronization problems}
{excerpt-include:Troubleshooting why Capture Index values do not display} ||See also||
{contentbylabel:labels=troubleshooting|showLabels=false|space=@self|showSpace=false|spaces=@self}

Troubleshooting error messages

h2. What do I do if I get a critical error message? {excerpt:hidden=false}Search for the error message in the user assistance, forum, and FAQ. If
you do not find instructions for solving this particular issue, the log files can be helpful when troubleshooting why an error occurred. !Configuring
the room layout^video24x20.jpg! Follow the below steps or watch this short [video tutorial|Video Tutorials#errorreporting] (2:26). # Take a
screenshot of the application and error message. # Write down the installation details (version, build, and serial number). You can access this
information in the application *Help>About StruxureWare Operations*. # Write down (in steps) what you were doing before the message
appeared. # Select *Help>Download Log Files* and save the server and client log files to a location of your choice. Log files are also available
from the Webmin server management interface (*StruxureWare Operations>Download server log files*). # Send this information to technical
support ## Error description ## Description of what you were doing when the message appeared ## Log files (A log folder is created at the
location you specified in step 4. It is named with the timestamp, e.g. 2011-09-23--12-57-50.) {tip:icon=false}*Note*: In a clustered environment,
you must log on to each node and get the log files.{tip}{excerpt} || See also || [Troubleshooting]

Troubleshooting performance issues

h2. Slow server/client connection {excerpt:hidden=false}If the connection between the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server and client is slow, add an exception in the connection options for the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} IP address. The
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client uses the proxy settings from the operating system. If you are running
on Windows, you can configure the settings through the Internet Explorer connection options. # In Internet Explorer, select *Tools>Internet
Options*. # Select the *Connections* tab. # Click *LAN settings*. # In *Proxy server*, select *Use a proxy server for your LAN*. # Click
*Advanced*. # In *Exceptions*, add your exceptions separated by semi-colon.{excerpt} ||See also|| [System requirements]

Video Tutorials
{panel:borderWidth=0|bgColor=9FAOA4}h2. Getting Started Take a quick tour of the application and get started with the basics and more
advanced features by watching these short video tutorials. {panel} {section}{column:width=50%} TIP: For optimum quality, select to watch the
video full screen and ensure the highest quality has been selected in the bottom right corner of the video (YouTube setting). {column}
{column:width=50%} !youtube_changequality_icon.png|thumbnail! {column} {section} {composition-setup} h1. {toggle-cloak:id=CPM} *Working

with {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true}* {cloak:id=CPM} ||Setting up a capacity

plan{anchor:capacityplanvideo}|| |Watch this short video tutorial (1:56) to see how to set up a capacity plan. \\ \\
{widget:url=http://www.youtube.com/watch?v=ws1Yj2hJB1s?rel=0|width=300}| {cloak} h1. {toggle-cloak:id=CHM} *Working with
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true}* {cloak:id=CHM} || Monitoring the structured change management
process{anchor:changesviewvideo}||Establishing best practices by using work order templates{anchor:wotemplatesvideo}|| |Watch this short video
tutorial (1:05) to see how to use the Changes view to monitor the structured change management process.\\ \\
{widget:url=http://www.youtube.com/watch?v=rZbq7TPec5M?rel=0|width=300}|Watch this short video tutorial (1:47) to see how to use work order
templates to establish and apply best practices\\ \\ {widget:url=http://www.youtube.com/watch?v=EGaZszTnQJw?rel=0|width=300}| ||Working with
work orders in an integrated BMC Remedy solution|| |Watch this short video tutorial (5:27) to see how to work with an integrated BMC Remedy
solution \\ \\ {widget:url=http://www.youtube.com/watch?v=my3CVdwuCyQ?rel=0|width=300}| {cloak} h1. {toggle-cloak:id=DCI} *Customizing
report design in {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}* {cloak:id=DCI} ||Customizing
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} report designs in
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}{anchor:reportdesignvideo}|| |Watch this short video tutorial (3:06) to see how
to change the logo in a report. \\ \\ {widget:url=http://www.youtube.com/watch?v=8DVnpOcryZE?rel=0|width=300}| {cloak} h1.
{toggle-cloak:id=Dashboard} *Configuring the {multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}* {cloak:id=Dashboard}
||Installing the {multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}{anchor:installingdashboardvideo}||Configuring the
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}{anchor:configdashboardvideo}|| | Watch this short video tutorial (2:23)
to see how to install the {multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}\\ \\
{widget:url=http://www.youtube.com/watch?v=6WvygkwMypQ?rel=0|width=300}| Watch this short video tutorial (1:52) to see how to configure the
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}. \\ \\
{widget:url=http://www.youtube.com/watch?v=FyTvkUp4NxE?rel=0|width=300}| {cloak} h1. {toggle-cloak:id=Cooling} *Working with cooling*
{cloak:id=Cooling} ||Working with the 3D view{anchor:3Dvideo}|| | Watch this short video tutorial (1:24) to see how to use and navigate the 3D
view.\\ \\ {widget:url=http://www.youtube.com/watch?v=OU45eOrPZhg?rel=0|width=300} \\ \\ | {cloak} h1. {toggle-cloak:id=logs} *Reporting errors
to technical support* {cloak:id=logs} ||Downloading log files for support purposes{anchor:errorreporting}|| | Watch this short video tutorial (2:26) to
see how to download log files and prepare for reporting errors to technical support. \\ \\
{widget:url=http://www.youtube.com/watch?v=SCkgmiKes2Y?rel=0|width=300}| {cloak} h1. {toggle-cloak:id=sysadm} *Performing system
administration tasks* {cloak:id=sysadm} ||Introduction to the server management interface||Mounting a Windows share{anchor:mountsharevideo}||
| Watch this short video tutorial (4:55) to get a quick tour of the Webmin interface.\\ \\
{widget:url=http://www.youtube.com/watch?v=jDc67-wvBUI?rel=0|width=300}| Watch this short video tutorial (2:20) to see how to mount a
Windows share. \\ \\ {widget:url=http://www.youtube.com/watch?v=TWJXFWiZ76Q?rel=0|width=300}| ||Optimizing StruxureWare Operations
performance in a virtual environment{anchor:VMwareinstalltools}|| | Watch this short video tutorial (5:02) to see how to optimize performance
when running the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server in a virtual environment.\\ \\
{widget:url=http://www.youtube.com/watch?v=UlIIO4k2-JM?rel=0|width=300}| {cloak}

White Papers
Error: The XML content could not be parsed. There is a problem at line 2, column 143. Parser message: Unexpected character '=' (code 61);
expected a semi-colon after the reference for entity 'Query_Type' at [row,col {unknown-source}]: [2,143]

Write to us
h5. Contact the documentation team directly and provide us with your feedback by filling out this form. Your feedback is highly appreciated in our
attempt to improve the help that we provide. Use the form when you want to contact the documentation team directly or write to
!feedbackmail.png!. You are also welcome to comment, make a request, or ask questions directly on a page by clicking Add Comment at the
bottom of the page. Use this option when you want to share your comment with everybody as it will be visible to everybody viewing the page.
{mail-form:id=documentationFeedback} {mail-input:type=hidden|name=subject|vtlValue=Documentation feedback #if($user) from
$!user.fullName#end} {mail-input:type=hidden|name=confUser|vtlValue=$!user.name}
{mail-input:type=hidden|name=URL|vtlValue=$req.requestURL#if($req.queryString)?$req.queryString#end} || Contact Name |
{mail-input:type=text|name=contactName|cssStyle=width: 170px|vtlValue=$!user.fullName|required=true} | || Contact Email |
{mail-input:type=text|name=contactEmail|cssStyle=width: 100%|validation=email|vtlValue=$!user.email|required=true} | || Contact Address |
{mail-textarea:name=contactAddress|cssStyle=width: 300px; height: 120px}{mail-textarea} | || Your Schneider contact |
{mail-input:type=text|name=schneiderContact|cssStyle=width: 170px;}| || Your question/comment | {mail-textarea:name=desc|cssStyle=width:
600px; height: 320px|required=true}{mail-textarea} | {mail-submit:Submit} {mail-success:render=wiki} {tip:title=Feedback submitted}Thank you for
taking the time to write to us.{tip} {mail-success} {mail-form}

Glossary
{excerpt:hidden=false}This overview lists data center related glossary terms.{excerpt} h2. Block {anchor:block} A block in the room layout
represents a section over which cables and cooling lines cannot be routed (such as a support column). h2. Capacity Group {anchor:capgroup}
Capacity groups allow you to group your equipment, placing it in groups of racks with similar power capacity requirements. Grouping your racks in
capacity groups with similar racks will help you plan and manage the capacity and prevent failure. h2. Capture Index (CI) {anchor:ci} Unit of
measurement used to measure how much exhaust airflow of a rack is captured by the cooling units included in that rack's equipment cluster.
*Cold Aisle Capture Index (CACI)*: The cold aisle capture index is defined as the fraction of air ingested by the rack that originates from local
cooling resources (e.g. perforated floor tiles or local coolers). *Hot Aisle Capture Index (HACI)*: The hot aisle capture index is defined as the
fraction of air exhausted by a rack that is captured by local extracts (e.g. local coolers or return vents). Based on these airflow patterns, the
system calculates the following cooling values: Inlet temperature, Exhaust temperature, Estimated heat loss. The cooling values can be seen by
selecting the Cooling tab in the Floor Layout, and hovering over a rack to see the tool tip. h2. Cluster {anchor:cluster} When used in connection
with cluster environment, cluster is used as follows: {quote} A *computer cluster* is a group of linked
[computers|http://en.wikipedia.org/wiki/Computer], working together closely thus in many respects forming a single computer. The components of
a cluster are commonly, but not always, connected to each other through fast [local area
networks|http://en.wikipedia.org/wiki/Local_area_network]. Clusters are usually deployed to improve performance and availability over that of a
single computer, while typically being much more cost-effective than single computers of comparable speed or availability. {quote} Source:
[Wikipedia. Wikimedia Foundation, Inc. 5 May 2011|http://en.wikipedia.org/wiki/Computer_cluster] When used in connection with cooling, cluster

is used as follows: An equipment cluster is two nearly-equal-length rows of equipment separated by a hot or cold aisle. A row of equipment can be
a member of one or two clusters. h2. Cubic Feet per Minute (CFM) {anchor:cfm} Unit of measurement used to measure the airflow of a cooling
unit. h2. Data Set {anchor:dataset} This term is used in {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. A data set is a
collection of data. You can combine data from various data sets to make your custom report design. The data sets that have been exposed from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} are available in
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. h2. Data Source {anchor:datasource} This term is used in
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. A data source is used for connecting to the database to get the requested
data. h2. Distribution Redundancy {anchor:distrredundancy} A type of redundancy setup in which the power source is not redundant, only the
power distribution in the form of redundant rack PDUs. Distribution redundancy does not provide as much security as the full redundancy setup at
power source level (redundant UPS), because even if a server is connected to different Rack PDUs, the UPS remains the single point of failure. In
the system, you can come across these variations: DN and DN+1, see these explained in the Redundancy section. h2. Estimated Downstream
Load {anchor:estdownstream} The *Estimated Downstream Load* value identifies how much capacity the selected piece of equipment (UPS,
PDU, RDP, Power Panel) needs from its power supply to distribute the power you plan to the connected equipment. This value is the sum of the
estimated load of the connected equipment, i.e. the sum of what has been set per piece of equipment in *Properties > Power > estimated load*
value. h2. Gap {anchor:gap} A gap icon in a room layout represents a section over which cables and cooling lines can be routed (such as a
walkway or ramp). h2. Group's Planned Average Load {anchor:plannedavg} The planned average load per rack in a capacity group. This setting
can be accessed by right-clicking a rack and selecting *> Properties > Capacity > Average estimated load (per rack)*. It identifies the estimated
load allowed on average for racks that are included in the capacity group. Some racks are allowed to draw up to peak value, but this will cause
other racks to be allowed to draw less than the average value. It is displayed in the *Capacity Summary* above the racks in the layout, when
\*Rack Layout* is selected with the \*Power Details* view active. h2. Group's Planned Peak Load {anchor:plannedpeak} The planned peak load
value identifies the maximum load that is allowed for any rack included in the capacity group. It is displayed in the Capacity Summary above the
racks in the layout, when Rack Layout is selected with the Power Details view active. A well-balanced planned peak and planned average power
draw ratio will help you plan an even load in all racks and avoid stranded capacity. h2. High Availability {anchor:highavail} High Availability
enables you to run the application in a clustered environment with multiple servers for improved performance. You must have a Cluster Node
license for each node in a cluster setup. h2. Key Performance Indicator (KPI) KPI is a business term used for critical data collected to measure
the success of a business. When you use software supporting KPI trending, it enables you to identify areas of improvement to most efficiently
spend resources where they are needed the most. h2. Local Mode {anchor:localmode} When using the
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}, you can work in either local or server mode. Local mode means that you
are working in a local copy. It does not require that you have network connection and your changes will not be updated in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client application until it is synchronized. The
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} will also only receive changes made by other users when synchronized. h2.
Measured Average Load {anchor:measavg} The measured average load per rack. The measured average value is measured over a specified
period of time, and will be affected by any changes to the load in that period, e.g. due to equipment being switched off for maintenance. h2.
Network Communication Endpoint {anchor:netwendpoint} Equipment that is not network gear as such, rather equipment that is connected to a
network, such as a server or PDU. h2. Network Gear, Layer 1, 2, 3 {anchor:netwgear} Equipment dedicated to dealing with network, e.g.
switches, routers, patch panels, etc. * Layer 1: Non-powered non-intelligent network equipment, e.g. a patch panel. * Layer 2: Powered
non-intelligent network equipment, e.g. a hub. * Layer 3: Powered intelligent network equipment, e.g. a switch or router. h2. Network
Redistribution Point {anchor:netwredistr} Network gear, such as routers and switches. h2. Node {anchor:node} When used in connection with
licenses, such as the {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license, a node is a rack supported by the license.
You must buy a license covering as many racks as you want supported (10, 100, etc.). When used in connection with cluster setup, a node is a
single server that is part of a distributed installation with multiple servers. You must buy a license per additional node added to the cluster setup.
h2. Partial loading {anchor:partload} Partial loading means that the system only loads active parts of the application (rooms, etc. on demand).
Because the system does not need to load the entire data center model all the time, performance is increased significantly. h2. Perspective
{anchor:persp} A perspective is a collection of views in a window. The active perspective is indicated by the selected element in the toolbar.
Available perspectives are Operations, Analytics Reports and, depending on the installed add-on modules, possibly more, e.g. Planning Work
Orders ({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature). h2. Phase Balancing {anchor:phasebalance} Phases
are also referred to as L1, L2, L3. If the load of equipment is distributed on more than one phase, make sure the load is distributed evenly on all
phases in a Capacity Group to obtain an optimum solution. The configuration of phases is done in the Properties. h2. Plenum {anchor:plenum} A
pocket of space used for air distribution below a raised floor or above a suspended ceiling. h2. Power Buffer {anchor:pwbuffer} When doing
capacity planning, some racks are allowed to draw up to peak value, but this will cause other racks to be allowed to draw less than the average
value. This means that the maximum additional load that can be added to a rack equals the *Remaining Power* and *Power Buffer*. In line with
the group's *Reserved Power* being utilized, the *Power Buffer* will decrease. h2. Power Feed {anchor:pwfeed} This term is used in connection
with a redundant configuration where one UPS is referred to A feed and the other as B feed. h2. Redundancy {anchor:redund} The provision of
multiple interchangeable components to perform a single function in order to cope with failures and errors, e.g. the setup of more power supplies
to reduce the risk of failure of the entire system in case one of them fails. You may come across these terms in connection with redundancy in the
system: Power redundancy: * N: No redundancy. * N+1: One UPS with one redundant power module (also referred to as internal redundancy in
the UPS Power properties page). If the UPS fails, there is no redundant UPS serving as backup, but if one of the power modules inside the UPS
fails, the redundant module ensures that the UPS still has full capacity. In other words, the spare power is at least equal to the capacity of one
system module. * N+2: One UPS with two redundant power modules (also referred to as internal redundancy in the UPS Power properties page).
If the UPS fails, there is no redundant UPS serving as backup, but if one or two of the power modules inside the UPS fail, the redundant modules
ensure that the UPS still has full capacity. In other words, the spare power is at least equal to two system modules. * 2N: Two UPS where one
serves as backup for the other in case one of them fails. One UPS is referred to as A feed and the other as B feed. * 2N+1: This is a combination
of N+1 and 2N for combined external and internal redundancy, both one redundant UPS and one redundant power module inside both UPS. *
2N+2: This is a combination of N+2 and 2N for combined external and internal redundancy, both one redundant UPS and two redundant power
modules inside both UPS. * DN: This is a combination of D (distribution redundancy) and N (above). For this type of redundancy, the power
distribution is redundant but there is no redundancy on the UPS level. Therefore, you are still vulnerable to failure on the power supply. * DN+1:
This is a combination of D (distribution redundancy) and N+1 (above). For this type of redundancy, the power distribution is redundant and there is
internal redundancy on the UPS level (one UPS with one redundant power module). Cooling redundancy: * N: There are no redundant cooling
units for the rack. There are one or more coolers in the data center. If ONE cooler fails anywhere in the data center, it would result in inadequate
cooling (yellow or red CI). * N+1: There is one redundant cooling unit for the rack. ONE cooler (CRAC, row-based, or OA unit) can fail anywhere in
the data center and cooling will still be adequate (green CI). * N+2: There are two redundant cooling units for the rack. TWO coolers (CRACs,
row-based, or OA units) can fail anywhere in the data center and cooling will still be adequate (green CI). * N+x: There are x redundant cooling

units for the rack. X coolers (CRACs, row-based, or OA units) can fail anywhere in the data center and cooling will still be adequate (green CI).
h2. Remaining Power {anchor:remainpw} The *Remaining Power* value identifies how much power capacity remains in the rack without
exceeding the allowed average load that you planned for the racks in the active capacity group. It is displayed in the *Capacity Summary* above
the racks in the layout, when *Rack Layout* is selected with the *Power Details* view active. h2. Reserved Capacity {anchor:reserved} The
*Reserved Capacity* value identifies how much capacity the selected piece of equipment (UPS, PDU, RDP, Power Panel) needs from its power
supply to distribute the power you plan to the connected equipment. This value is the sum of the estimated load of the connected equipment, i.e.
the sum of what has been set per rack in a capacity group in *Properties > Capacity > estimated load*. h2. Server Mode {anchor:servermode}
When using the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}, you can work in either local or server mode. Server mode
means that you are working in the database on the server, and any saved changes will immediately be updated in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client application as well. Any changes made by other users will also be
instantly reflected in the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}. h2. Stranded Capacity {anchor:stranded} Capacity
that cannot be utilized by IT loads due to the design or configuration of the system. The presence of stranded capacity indicates an imbalance
between two or more of the following capacities: Floor and rack space, Power, Power distribution, Cooling, Cooling distribution. h2. Tags
{anchor:tags} Tags are category labels that can be created and assigned to equipment in the floor or rack layout to group equipment. Tags can be
used to help plan the best place for new equipment automatically. h2. Temperature Map {anchor:tempmap} A color map showing the temperature
in different parts of a room. The temperature map is 3-dimensional with movable planes. h2. Temperature Plane {anchor: tempplane} The
temperature plane is a movable plane (vertically and horizontally) that shows a color-coded cross section of the temperature in the room. h2.
Unreserved Capacity {anchor:unreserv} The unreserved capacity value identifies how much remaining power there is for the selected PDU, RDP,
or Power Panel. That means that this value does for instance not take into account that other power distribution units may reduce the actual
value. h2. Velocity Plane {anchor:velplane} The velocity plane is a movable plane (vertically and horizontally) that shows a color-coded cross
section of the airflow vectors in the room. h2. Wizard {anchor:wizard} A wizard leads you through dialog steps. h2. Work Order {anchor:worder} A
work order contains tasks. A list of work orders can be created in the system, listing what actions need to be executed in the data center, e.g.
installing new servers in specific positions.

Index
{index}