Online Help

StruxureWare Data Center 2SHUDWLRQ

Version 3
1. User Assistance for StruxureWare Data Center Operation 8.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 What is new in StruxureWare Data Center Operation 8.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1.1 DCO 8.x may be affected by a critical memory leak in the latest Java package . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.1.2 Understanding the new Capacity implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.2 Getting from previous versions to DCO 8.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.3 How to transition from a clustered environment to disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.4 Clustered Environment no longer available in DCO 8.2.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.5 StruxureWare Data Center Operation release summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.6 StruxureWare Data Center Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1.7 StruxureWare Data Center Operation for Colo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
1.7.1 StruxureWare Data Center Operation for Colo Desktop Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1.7.1.1 Cage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
1.7.1.2 Room Colo overlay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
1.7.2 StruxureWare Data Center Operation: Tenant Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
1.7.2.1 Tenant Portal Guide for Colo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1.7.2.1.1 Onboarding a customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1.7.2.1.2 Managing customers and customer users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1.7.2.1.3 Customizing branding towards your tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
1.7.2.2 Tenant Portal Guide for Tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
1.7.2.2.1 Working with inventory in the Tenant Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
1.7.2.2.2 Tenant Portal dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
1.7.2.2.3 Changing the Tenant Portal language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
1.7.2.2.4 Managing your Tenant Portal user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
1.8 StruxureWare Data Center Operation security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
1.8.1 Web proxy server setup guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
1.8.2 StruxureWare Data Center Operation Network Firewall Port Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
1.8.3 StruxureWare Data Center Operation Software Vulnerability Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
1.8.4 Changing SSL certificate on the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
1.8.5 Resetting user password on the DCO server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
1.9 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
1.9.1 Linux desktop client compatibility guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
1.10 Initial installation and system setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
1.10.1 Installing StruxureWare Data Center Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
1.10.1.1 Installing DCO on Red Hat Enterprise Linux 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
1.10.1.1.1 List of Dependent Packages for Red Hat Enterprise Linux Installation . . . . . . . . . . . . . . . . . . . . . . . . 99
1.10.1.2 Installing the DCO server using out-of-band management interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
1.10.1.3 Installing StruxureWare Data Center Operation in a virtual environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
1.10.1.4 Installing DCO in a location without public Internet access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
1.10.1.5 Creating a bootable media with the DCO ISO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
1.10.2 Installing StruxureWare Data Center Operation in a clustered environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
1.10.2.1 Setting up a clustered environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
1.10.3 Setting up the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
1.10.3.1 Configuring external system integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
1.10.3.1.1 Configuring StruxureWare Data Center Expert integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
1.10.3.1.2 Configuring VMware vCenter integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
1.10.3.1.3 Configuring Remedy integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
1.10.3.1.4 Configuring Cisco UCS Manager integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
1.10.3.1.5 Configuring StruxureWare Power Monitoring Expert integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
1.10.3.1.6 HP OneView integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
1.10.3.1.7 External system integration through ETL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
1.10.3.1.8 DCO SNMP status codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
1.10.3.1.9 RF Code CenterScape Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
1.10.3.1.10 ServiceNow Asset Management Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
1.10.3.1.11 ServiceNow Change Management Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
1.10.3.2 Configuring email settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
1.10.3.3 Working with multiple languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
1.10.3.3.1 Starting StruxureWare Data Center Operation Client in a Different Language . . . . . . . . . . . . . . . . . . 158
1.10.4 Changing the location of the StruxureWare Data Center Operation client temporary files . . . . . . . . . . . . . . . . . . . 160
1.10.5 Configuring disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
1.11 StruxureWare Data Center Operation Desktop Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
1.11.1 The look and feel of the DCO desktop client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
1.11.1.1 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
1.11.1.2 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
1.11.1.3 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
1.11.2 Monitoring operations in Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
1.11.3 Exploring the infrastructure in Map, Floor and Rack Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
1.11.4 Showing or hiding room overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
1.11.5 Reviewing system preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
1.11.6 Keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
1.11.7 Building the infrastructure and adding inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
1.11.7.1 Configuring the room design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
1.11.7.1.1 Configuring floor weight carrying capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
1.11.7.1.2 Configuring room design preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
1.11.7.2 Adding room elements to the floor layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
1.11.7.3 Adding equipment to the floor layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
1.11.7.3.1 Positioning components in the floor layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
1.11.7.4 Adding rack-mountable equipment to the room layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Page 1
 1.11.7.5 Adding multiple pieces of equipment with bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
1.11.7.6 Editing properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
1.11.7.6.1 Custom properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
1.11.7.7 Working with the genome library and genomes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
1.11.7.7.1 Genome icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
1.11.7.8 Configuring equipment not available in the genome library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
1.11.7.9 CAD Import Supported Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
1.11.8 Working with the room layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
1.11.8.1 Room overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
1.11.8.2 Exporting layout as image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
1.11.8.3 Inventory report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
1.11.8.4 Room layout toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
1.11.8.5 What does the power tool tip tell me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
1.11.8.5.1 Power tool tip troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
1.11.8.6 What does the cooling tool tip tell me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
1.11.9 Configuring power connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
1.11.9.1 Configuring DC power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
1.11.9.2 Working with Rack PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
1.11.9.3 Configuring multiple power connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
1.11.9.4 Configuring distributed redundant UPS systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
1.11.9.5 Working with breaker panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
1.11.9.6 Reorganizing breaker panels after upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
1.11.9.7 Power redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
1.11.9.8 Power dependency description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
1.11.9.9 Voltage supported in Data Center Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
1.11.10 Configuring blade solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
1.11.10.1 Valid blade configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
1.11.11 Configuring cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
1.11.11.1 Row-based or room-based cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
1.11.11.2 Working with Capture Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
1.11.11.2.1 About the Capture Index (CI) colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
1.11.11.2.2 About Capture Index prediction models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
1.11.11.2.3 Troubleshooting why Capture Index values do not display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
1.11.11.3 Designs with perforated tiles on a raised floor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
1.11.11.3.1 Working with plenum velocities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
1.11.11.3.2 Working with plenum pressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
1.11.11.4 Working with the 3D temperature map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
1.11.11.4.1 Customizing 3D Colors and Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
1.11.11.4.2 Troubleshooting inaccurate 3D calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
1.11.11.5 Exporting Cooling Data to 3rd Party Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
1.11.11.6 Cooling Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
1.11.11.7 Cooling Configuration Accuracy and Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
1.11.11.8 Optimizing the Cooling Configuration Accuracy by Adjusting Power and Cooling Estimates . . . . . . . . . . . 257
1.11.11.9 Understanding Real-time Temperature Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
1.11.11.10 Tips and tricks for configuring cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
1.11.11.11 Designs with CRAC Units Placed Outside the Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
1.11.12 Managing network configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
1.11.12.1 Configuring network connections in rack view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
1.11.12.2 Configuring network connections in table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
1.11.12.3 Configuring network ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
1.11.12.4 Configuring network cable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
1.11.12.5 Network configuration example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
1.11.12.6 Route notation in network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
1.11.12.7 Network properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
1.11.12.8 Network Summary report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
1.11.13 Working with the List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
1.11.13.1 Editing multiple items in List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
1.11.13.2 Exporting List View table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
1.11.14 Working with the Power Path Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
1.11.15 Working with the Equipment Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
1.11.15.1 Editing multiple items in the Equipment Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
1.11.15.2 Filtering and finding equipment in Equipment Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
1.11.15.3 Exporting Equipment Browser table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
1.11.15.4 Configuring Equipment Browser layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
1.11.15.5 Creating predefined table configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
1.11.15.6 Editing IP address through the Equipment Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
1.11.15.7 Properties description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
1.11.16 Working with Asset Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
1.11.16.1 Installation Requirements Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
1.11.17 Optimizing the Design by Following the Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
1.11.17.1 Showing Recommendations for Selected Equipment Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
1.11.17.2 Cooling Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
1.11.17.2.1 There is no Perforated Tile Airflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
1.11.17.2.2 The Room has no Perforated Tiles for the CRAC Airflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
1.11.17.3 General Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
1.11.17.3.1 Equipment Weight Exceeds the Weight Limit of the Floor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
1.11.17.3.2 Max Load Weight of Rack has been Exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Page 2
 1.11.17.3.3 Rack Contains Overlapping Equipment at U Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
1.11.17.3.4 The Tags Assigned to the Rack Equipment in the Rack do not Match . . . . . . . . . . . . . . . . . . . . . . . 296
1.11.17.4 License recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
1.11.17.4.1 You are Approaching the Amount of Racks Supported by your StruxureWare Data Center Operation -
Capacity License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
1.11.17.4.2 You are Approaching the Amount of Racks Supported by your StruxureWare Data Center Operation -
Change License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
1.11.17.4.3 You are Approaching the Amount of Racks Supported by your StruxureWare for Data Centers -
Operations Suite License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
1.11.17.4.4 You are Exceeding the Amount of Racks Supported by your StruxureWare Data Center Operation -
Capacity License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
1.11.17.4.5 You are Exceeding the Amount of Racks Supported by your StruxureWare Data Center Operation -
Change License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
1.11.17.4.6 You are Exceeding the Amount of Racks Supported by your StruxureWare for Data Centers -
Operations Suite License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
1.11.17.4.7 You have Reached the Amount of Racks Supported by your StruxureWare Data Center Operation -
Capacity License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
1.11.17.4.8 You have Reached the Amount of Racks Supported by your StruxureWare Data Center Operation -
Change License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
1.11.17.4.9 You have Reached the Amount of Racks Supported by your StruxureWare for Data Centers -
Operations License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
1.11.17.5 Power Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
1.11.17.5.1 Amount of Rack PDU Power Outlets has not been Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
1.11.17.5.2 An Invalid Power Path has been Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
1.11.17.5.3 Associated Device Data has been Lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
1.11.17.5.4 Breakers in Module must have Unique Power Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
1.11.17.5.5 Connection has not been Configured between PDU and Power Supply . . . . . . . . . . . . . . . . . . . . . . 312
1.11.17.5.6 Connection has not been Configured between Power Panel and Power Supply . . . . . . . . . . . . . . . . 313
1.11.17.5.7 Connection has not been Configured between Remote Distribution Panel (RDP) and Power Supply 314
314
1.11.17.5.8 Equipment Connected to this PDU Draws more Power than is Supported by the Power Supply Breaker
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
1.11.17.5.9 Equipment Connected to this Power Panel Draws more Power than is Supported by the Power Supply
Breaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
1.11.17.5.10 Equipment Connected to this Remote Distribution Panel (RDP) Draws more Power than is Supported
by the Power Supply Breaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
1.11.17.5.11 Equipment in this Rack Receives Power from Multiple Power Supply Devices . . . . . . . . . . . . . . . . 318
1.11.17.5.12 Equipment is Connected to a Rack PDU Outside this Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
1.11.17.5.13 PDU and Connected Rack PDU are Placed in Different Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
1.11.17.5.14 PDU Output Voltage has not been Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
1.11.17.5.15 Power Distribution Equipment must have Unique Breaker Module Numbers . . . . . . . . . . . . . . . . . 322
1.11.17.5.16 Power Panel Output Voltage has not been Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
1.11.17.5.17 Rack's Power Configuration does not Support Distribution Redundancy . . . . . . . . . . . . . . . . . . . . . 324
1.11.17.5.18 Rack is without Rack PDU or a Rack PDU is not Powered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
1.11.17.5.19 The Breaker Configuration does not Support Rack's Estimated Load . . . . . . . . . . . . . . . . . . . . . . . 326
1.11.17.5.20 The Breaker Configuration in the Power Distribution Properties does not Match the Measured Power
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
1.11.17.5.21 The Input Voltage Setting Required by the Equipment is not Available in Current Rack . . . . . . . . . 328
1.11.17.5.22 The Measured Load Exceeds the Estimated Load per Phase Designed for the Rack . . . . . . . . . . 329
1.11.17.5.23 The Measured Load Exceeds the Total Estimated Load Configured for the Rack . . . . . . . . . . . . . 330
1.11.17.5.24 The Measured Load of the Connected Rack PDU is 0, but an Estimated Load has been Configured for
the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
1.11.17.5.25 The Measured Load of the UPS Exceeds the Total Estimated Load of the Connected Equipment 332
1.11.17.5.26 The Phase Configuration for the Connected Server is not Supported by the Rack PDU . . . . . . . . . 333
1.11.17.5.27 The Rack PDU Output Voltage Setting Does not Match the Output Voltage of the Connected PDU or
Power Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
1.11.17.5.28 The Server Should not be Supplied from Different Phases on 1 UPS . . . . . . . . . . . . . . . . . . . . . . . 335
1.11.17.5.29 The UPS in the Layout does not Supply Enough Power to Match the Configured Load of Connected
Equipment in the Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
1.11.17.5.30 This Equipment in Store Room is Connected to Equipment in a Room . . . . . . . . . . . . . . . . . . . . . . 337
1.11.17.5.31 UPS Internal Redundancy has not been Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
1.11.17.5.32 UPS Power Feed has not been Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
1.11.17.5.33 Rack PDU internal breaker is overloaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
1.11.18 Viewing External System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
1.11.18.1 About Peak and Average Power Data Retrieval from StruxureWare Data Center Expert . . . . . . . . . . . . . . 343
1.11.18.2 Associating Live Data from an External System to the Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
1.11.18.3 Launching to Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
1.11.18.4 How Removing a Server Affects Power Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
1.11.18.5 The Importance of System Time Synchronization for Accurate Power Values . . . . . . . . . . . . . . . . . . . . . . 348
1.11.18.6 Power profiles and power value accuracy levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
1.11.19 Viewing Alarms From External Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
1.11.19.1 Locating Alarms on Failing Equipment in the Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
1.11.19.2 Showing Alarms for Selected Equipment Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
1.11.19.3 Acknowledging Alarm Notifications from StruxureWare Data Center Expert . . . . . . . . . . . . . . . . . . . . . . . . 353
1.11.20 Configuring the PUE DCiE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
1.11.21 Working with Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
1.11.21.1 Working with Report Filter Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Page 3
 1.11.21.2 Customizing Report Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
1.11.21.3 Working with Localized Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
1.11.21.4 Audit Trail Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
1.11.21.5 Energy Cost Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
1.11.21.6 Rack U-Space Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
1.11.22 Understanding what Happens when Multiple Users Work Simultaneously in DCO . . . . . . . . . . . . . . . . . . . . . . . . 364
1.12 StruxureWare Data Center Operation Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
1.12.1 Working with the inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
1.12.1.1 Editing rack inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
1.12.1.2 Searching the inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
1.12.2 Dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
1.12.2.1 Using the Energy Efficiency Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
1.12.2.2 Using the PUE DCiE Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
1.12.3 Changing the language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
1.12.4 Managing your user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
1.12.5 Customizing web branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
1.12.6 Managing licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
1.12.7 Managing DCO users and user rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
1.12.7.1 About users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
1.12.7.2 Granting access to legacy SOAP web service API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
1.12.8 Configuring authentication servers used for managing remote users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
1.12.8.1 Setup an AD (Active Directory) Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
1.12.9 Working with SSL certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
1.13 StruxureWare Data Center Operation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
1.13.1 Managing DCO server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
1.13.1.1 File sharing between Data Center Operation and your network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
1.13.1.2 Backing up and restoring backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
1.13.1.2.1 Restoring IT Optimize backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
1.13.1.2.2 Scheduling regular backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
1.13.1.3 Disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
1.13.1.4 Managing StruxureWare Data Center Operation services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
1.13.1.5 Changing the IP address of the StruxureWare Data Center Operation server through Webmin . . . . . . . . . . 410
1.13.1.6 Reconfiguring locale on the StruxureWare Data Center Operation server . . . . . . . . . . . . . . . . . . . . . . . . . . 411
1.13.1.7 Configuring log rotation and archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
1.13.1.8 Managing Webmin user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
1.13.1.9 Managing Webmin interface security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
1.13.1.10 Enabling Data Center Operation monitoring through Data Center Expert . . . . . . . . . . . . . . . . . . . . . . . . . . 418
1.13.1.11 Disabling redirection of http requests to https . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
1.13.1.12 Software packages and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
1.14 StruxureWare Data Center Operation: Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
1.14.1 Understanding estimated load and how it is calculated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
1.14.2 Adjusted nameplate or predicted power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
1.14.3 About predicted power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
1.14.4 About power supply unit uncertainty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
1.14.5 Redundancy examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
1.14.6 Finding the best location for a new server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
1.14.7 Enabling provisioning match recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
1.14.7.1 Available copper-based network ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
1.14.7.2 Available fiber-based network ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
1.14.7.3 Equipment fits into rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
1.14.7.4 Floor supports weight of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
1.14.7.5 PDU supports rack PDUs voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
1.14.7.6 Rack airflow supports equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
1.14.7.7 Rack PDU supports equipment's load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
1.14.7.8 Rack PDU supports equipment's voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
1.14.7.9 Rack supports equipment's redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
1.14.7.10 Rack supports equipment's Watts per U-height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
1.14.7.11 Rack supports weight of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
1.14.7.12 Rack tags support equipment tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
1.14.7.13 Rack supports equipment's plug type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
1.14.8 Working with tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
1.14.8.1 Creating tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
1.14.8.2 Managing tags in the Equipment Browser or List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
1.14.8.3 Tag properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
1.14.9 Simulating impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
1.14.9.1 Configuring cooling impact preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
1.14.9.2 Configuring simulated impact layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
1.14.9.3 Exporting impact table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
1.14.9.4 Filtering and finding equipment in simulated impact list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
1.14.9.5 Filtering network impact analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
1.14.10 VMware integration enabling migration of virtual machines impacted by alarms . . . . . . . . . . . . . . . . . . . . . . . . . 458
1.14.10.1 Configuring VMware integration to automatically migrate virtual machines impacted by alarms . . . . . . . . . 459
1.14.10.2 Locating virtual machines hosts with impact in the layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
1.14.10.3 Refreshing virtual machine host data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
1.14.10.4 Disabling maintenance mode on a virtual machine host after the impact has been resolved . . . . . . . . . . . 462
1.14.10.5 Virtual Machine Host Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
1.14.11 Branch circuit monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

Page 4
 1.14.11.1 Configuring branch circuit monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
1.14.11.2 Working with branch circuit monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
1.14.12 Advanced power configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
1.14.13 Capacity history KPIs over time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
1.14.13.1 Capacity history KPI description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
1.14.14 Capacity reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
1.14.15 How power measurements are processed in Data Center Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
1.15 StruxureWare Data Center Operation: Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
1.15.1 Change management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
1.15.2 Rack equipment planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
1.15.2.1 Planning changes to rack equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
1.15.2.2 Equipment stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
1.15.3 Working with work orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
1.15.3.1 Creating a controlled automated work order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
1.15.3.2 Creating a custom work order without recorded tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
1.15.3.3 Define a Work order workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
1.15.3.4 Identifying work order task and equipment relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
1.15.3.5 Creating and applying work order processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
1.15.3.6 Work order reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
1.15.3.7 Deleting old work orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
1.15.3.8 Configuring work order administrative settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
1.15.3.8.1 Scheduling work order recurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
1.15.3.8.2 Setting up automatic email notification on work order completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
1.15.3.8.3 Locking a work order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
1.15.3.9 User roles when working with work orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
1.15.4 Executing work orders using the web client on mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
1.15.4.1 Work order task status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
1.15.5 Integration with the Remedy change management system from BMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
1.15.5.1 Viewing tickets from Remedy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
1.15.5.2 Associating Remedy tickets and work orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
1.15.5.3 Remedy integration process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
1.16 StruxureWare Data Center Operation: Energy Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
1.16.1 About PUE and DCiE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
1.16.2 Power dependency configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
1.16.3 Energy system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
1.16.3.1 Configuring infiltration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
1.16.3.2 Configuring IT load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
1.16.3.3 Configuring ventilation and lighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
1.16.3.4 Energy Efficiency properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
1.16.3.5 Energy system properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
1.16.3.6 Infiltration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
1.16.3.7 IT load properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
1.16.3.8 Lighting properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
1.16.3.9 Ventilation properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
1.16.4 Database integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
1.16.4.1 Sample startup script for database integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
1.16.4.2 Sample simple database query script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
1.16.4.3 Sample database query script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
1.16.5 Web service integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
1.17 StruxureWare Data Center Operation: Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
1.17.1 Designing simulations in StruxureWare Data Center Operation: Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
1.17.2 Troubleshooting issues saving large solutions in Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
1.18 StruxureWare Data Center Operation: Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
1.19 StruxureWare Data Center Operation: Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
1.19.1 Required setting for Mobile 8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
1.19.2 Installing StruxureWare Data Center Operation: Mobile on the mobile device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
1.19.3 Logging on to StruxureWare Data Center Operation: Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
1.19.3.1 Troubleshooting logon problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
1.19.4 StruxureWare Data Center Operation: Mobile main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
1.19.5 Local and server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
1.19.6 Working in local mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
1.19.7 Synchronizing local changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
1.19.8 Troubleshooting connection and synchronization problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
1.19.9 Alarms on StruxureWare Data Center Operation: Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
1.19.9.1 Closing active alarm notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
1.19.9.2 Enabling or disabling pop-up alarm notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
1.19.10 Work Orders on StruxureWare Data Center Operation: Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
1.19.10.1 Filtering the work order list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
1.19.11 Asset management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
1.19.11.1 Scanning equipment bar codes into StruxureWare Data Center Operation: Mobile . . . . . . . . . . . . . . . . . . 557
1.19.11.1.1 Troubleshooting scan problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
1.19.11.2 Adding equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
1.19.11.3 Connecting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
1.19.11.4 Moving equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
1.19.11.5 Deleting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
1.19.11.6 Working with Pending Changes on StruxureWare Data Center Operation: Mobile . . . . . . . . . . . . . . . . . . . 563
1.19.11.7 Assigning tags on StruxureWare Data Center Operation: Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564

Page 5
 1.19.11.8 Defining customized properties for a piece of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
1.19.11.9 Equipment stages on StruxureWare Data Center Operation: Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
1.19.12 Performing a rack audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
1.19.13 Troubleshooting operational problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
1.20 StruxureWare Data Center Operation: PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
1.20.1 Initial setup of StruxureWare Data Center Operation PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
1.20.1.1 Installing StruxureWare Data Center Operation PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
1.20.1.2 Configuring StruxureWare Data Center Operation PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
1.20.1.3 Configuring StruxureWare Data Center Operation PRO Pack Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
1.20.2 Working with StruxureWare Data Center Operation PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
1.20.3 Working with Impact Analysis in StruxureWare Data Center Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
1.20.4 Working with StruxureWare Data Center Operation PRO Pack views in System Center Operations Manager . . . 577
1.20.5 Working with StruxureWare Data Center Operation PRO Pack PRO Tips in Virtual Machine Manager . . . . . . . . . 578
1.20.6 Troubleshooting virtualization issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
1.20.7 StruxureWare Data Center Operation PRO Pack PRO tip implementation rules . . . . . . . . . . . . . . . . . . . . . . . . . . 580
1.20.8 StruxureWare Data Center Operation: PRO Pack supported alarm types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
1.21 StruxureWare Data Center Operation: IT Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
1.21.1 What's new in IT Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
1.21.2 Installing IT Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
1.21.2.1 Upgrading IT Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
1.21.3 StruxureWare Data Center IT Optimize Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
1.21.4 StruxureWare Data Center IT Optimize client requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
1.21.5 Configuring StruxureWare Data Center IT Optimize Server Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
1.21.5.1 Workaround for ITO discovery of the StruxureWare Data Center Operation server . . . . . . . . . . . . . . . . . . . 593
1.21.6 StruxureWare Data Center: IT Optimize security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
1.21.6.1 WMI Command Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
1.21.6.2 WMI Windows Required Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
1.21.6.3 SNMP Command Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
1.21.6.4 VMware vSphere Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
1.21.6.5 SSH Sudo Discovery Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
1.21.6.6 SSH Command Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
1.21.6.7 StruxureWare Data Center: IT Optimize Software Vulnerabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
1.21.6.7.1 Upgrading IT Optimize 7.3.6 to Fix FREAK Vulnerability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
1.21.6.8 Software Packages in StruxureWare Data Center IT Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
1.21.7 Configuring IT Asset Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
1.21.7.1 Configuring discovery of HPUX Solaris and AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
1.21.8 Server Power Consumption Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
1.21.9 Server Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
1.21.10 Underutilized Servers Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
1.22 StruxureWare Data Center Operation: IT Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
1.22.1 Configuring IT Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
1.23 StruxureWare Data Center Operation: Server Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
1.23.1 Configuring the Server Access Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
1.23.2 Installing the StruxureWare Data Center Server Access Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
1.23.3 Server Access through Various Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
1.23.4 Using the Server Access module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
1.24 StruxureWare Data Center Operation: Cooling Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
1.24.1 Configuring Cooling Optimize Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
1.24.2 Configuring the Cooling Optimize Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
1.24.3 Cooling Optimize Benchmark Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
1.24.4 Temperature Compliance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
1.24.5 StruxureWare Data Center Operation Cooling Optimize system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
1.25 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
1.25.1 Downloading log files for troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
1.25.2 Resolving error collecting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
1.25.3 Correcting False Power Values Reported by StruxureWare Data Center Expert 7.2.6 . . . . . . . . . . . . . . . . . . . . . . 640
1.25.4 Troubleshooting Performance Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
1.25.5 Troubleshooting incorrect power values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
1.25.6 Protocols and Modules used for IT related features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
1.25.7 Troubleshooting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
1.25.8 Troubleshooting DCO client out-of-memory error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
1.26 Advanced use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
1.26.1 DCO web service API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
1.26.2 About migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
1.27 Recommended reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
1.28 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
1.29 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

Page 6
What is new in StruxureWare Data Center Operation 8.x
The 8.2.12 release contains functionality to handle user change requests to the data center in customized forms; updates to the U-space
and Forecast report; and some server configuration management has moved from Webmin to the web client.

This release contains a critical security update for the ZipSlip vulnerability. It is recommended that all customers update to this version.
For more information, see StruxureWare Data Center Operation Software Vulnerability Fixes.

To verify your support contracts and receive the latest download links, please fill out this form.

Remedy 9.1 is not supported in any DCO version. Only Remedy versions prior to 9.1 are supported.

What is new in StruxureWare Data Center Operation 8.3

Rack PDU internal breakers and power outlets

From 8.3 release in genome library there are rack PDUs with additional banks and outlets definition. Thanks to this extension user can
now connect end power consumer in rack to selected outlet. More information can be found here
Vertical U-Positions
Vertical extension panels now can be configured for racks. Each rack can be equipped with two vertical extension panels at most. More
information can be found here
New ETL attributes added in export database
The new attributes weight, depth, height, width, design limit are now included in the ETL export database. More information can be found
here
Other changes
Energy Cost license removed and energy cost is now under ops license
StruxureWare Insight removed
Improvements/bug fixes:

- Untitled row, HACS and CACS are now titled with smartname (meaning Row will be named row hacs will be named hacs and
so on)
- Aligned Naming of ETL Configuration
- Indication when there is no ETL Configuration
- Minor improvements to ETL in Webclient

Certificate page improvements:

- Certificate page now indicates that you can not add certificates
Capacity KPI calculations are now set pr default.

What is new in StruxureWare Data Center Operation 8.2.14

The 8.2.14 release includes security updates, update java to openJDK and angular upgrade to version 7. Web Client now is separated
from JBoss server.
In Web Client power connection feature is simplified.

What is new in StruxureWare Data Center Operation 8.2.12

Change Request
This new functionality enables users to request changes to the data center through custom build change request forms called Change
Request Templates.

License
Change Request requires StruxureWare Data Center Operation: Change License

Change request templates

Change request templates are managed by Administrators (users with permission "Planning Work Orders") to prepare a Request Form
in the DCO web client using the Change Management > Change Request Templates option. The Request Form is then filled in by
users to request changes in the data center.

Each template has a Name, Activation state, and Form field to specify information about the change. Templates are flexible; multiple
templates can be defined in the system. For example, you can create a template for adding equipment, another for moving items, and
another for creating users or custom properties.

Administrators can create, edit, delete, activate, or deactivate a template. Only active templates can be used to create change requests.

Page 11
Form fields that can be used in the template (and then in the change requests):

Text input
Numeric input
Date input
Multi-line text field
Email input
Checkbox
Select input (combo box)
Radio button
Header
Genome selector
Location selector
Blank space - separator

The Genome selector allows you to specify the equipment model from the Custom Catalogue. This is useful for creating a template for
adding equipment. You can specify the kinds of equipment (PDU, UPS, Server) and/or mounting types to select in the field.

Three value fields are available for publishing properties from a work order task to an asset: Barcode, Serial number, and Name.

You can use the Location selector to select the existing Location, Floor Plan, or Room from the data set.

You can define basic validation on each field to prevent users from submitting a change request with incorrect or missing information.
For example, each field can be made optional or required; text fields can have a minimum or maximum length. When you edit the
template form, you can enter values into the fields to see how they work. These values are not persisted.

The Administrator can define the form layout for four different screen sizes to make the form adjustable to the user's screen size when
they are creating or editing a change request.

Creation, deletion, and editing change request templates are logged by the Audit log and can be verified in the desktop client by running
the report.

Change Requests

A change request can be created by all non-tenant users in DCO based on templates created by an Administrator (a user with
permission "Planning Work Orders") in the DCO web client: Change Management > Change Requests.

A typical scenario:

1. A user creates a change request, and fills in the form. The change request can be saved as Draft.
2. A Draft or a newly created request can be Submitted if all fields are filled in according to the validation specified in the form.
3. The Submitted request is read-only and waits for an Administrator to act. The request can be Unsubmitted by the author if
some corrections need to be done, which puts it back into Draft.
4. The Administrator can do one of three operations on a Submitted change request:

Approve: The Administrator has accepted and processed the request, for example, by creating a work order for
executing the change.
Reject: Indicates the change is impossible to complete.
Require more information: The request status is changed to Need update. The author can modify the form data and
resubmit the request.
Closed: The final step, used when the request has been executed. The request can then be deleted by the author or
the Administrator.

Requests in Draft state are only visible to the author; they are not visible to other users.

Requests in other states are visible only to the author and Administrators.

If the author of a request is removed from the system, requests in Draft and Needs Update states are deleted. Requests in Submitted,

Page 12
Rejected, and Approved states survive so administrators can act on them.

Requests in Approved state

If a request contains one Genome, the Admin can Copy Genome Properties to populate properties from the Genome in the request to
an asset in an open work order. The values that are copied are: Barcode, Serial number, and Name. There is validation on the barcode
to keep it unique in the model.

Note: The work order must be created in the DCO desktop client.

You can comment on requests in states other than Draft to allow further communication between the author and the administrator.

When a request changes state, or a comment is posted, a notification email is sent to interested parties:

1. If the change or comment is made by the author of the request, email is sent to all administrators.
2. If the change or comment is made by an administrator, email is sent to the author of the request.

Email is sent in the user’s preferred language.

Note: You must configure mail settings with the Mail configuration REST web service.

Creating, deleting and changing the request state is logged in the Audit log. You can run a report in the desktop client to view the audit
log.
Barcode lock feature
When you import data via ETL, you can configure the option to lock the bar code, serial number, and name fields to avoid data changing
from a synchronisation.
Improvements to reports
The U-space report was updated to include full-depth U-space. Free front, rear, and full depth U-space is now included in the report.

The Forecast report now includes the power capacity for planned changes in a room based on work orders.
Server management options moved from Webmin to the web client
The management of backup and restore have been moved to the new Backup and Restore page in the web client. See the updated
backup and restore documentation here Backup and Restore.

Server log files can now be downloaded from the Download Server Log files page in the web client.

ETL and Power Monitoring Expert integrations can now be configured from the web client. See the updated documentation here ETL
configuration.
Other changes
ITO log files have been removed from DCO.
The ITO server must now be backed up separately.
The ZipSlip vulnerability (CVE-2018-7806) has been fixed. CVSS score: 6.6, CVSS vector: AV:A/AC:L/PR:H/UI:R/S:U/C:H/I:H/A
:H. The issue affects all previous versions.
ZipSlip vulnerability allows authenticated users to upload malicious file which could contain path traversal file names,
this could potentially allow for the arbitrary upload of files contained with the zip onto the server file system outside of
the intended directory. See more on the StruxureWare Data Center Operation Software Vulnerability Fixes page.

What is new in StruxureWare Data Center Operation 8.2.7

Extended power capacity information for rack mount PDUs in the web client
When you select a rack that contains items that report measured values, the Power tile displays the total of all the maximum values for a
time specified in the desktop client. This is now labeled Theoretical Peak (Theo. Peak) rather than Measured Peak.

Click the Power tile to view the Power History and Power Path Items for the rack.

Page 13
The Power Path Items section contains tiles for each rack mount PDU. No tiles are displayed for disconnected rack mount PDUs.

Page 14
In the Power Path Items section, click the tile for the rack mount PDU, then click the Power tile to view its power capacity charts.

Note: This information is also available in the desktop client tool tips.

The Power chart shows calculated values per phase: measured peak power per phase, estimated load, and potential failover load. A bar
indicates the physical limitations of the device.

The Power History charts shows the measured values in more detail. You click the items in the legend to show and hide values.

Page 15
Page 16
Page 17
User messages
Administration > User Messages option

In a Colocation environment, DCO admin users or operations users with a Colocation license can create messages to be displayed to
tenants.

Page 18
When you create a message, you choose the date and time you want the message to be active, and the recipients you want to see it. If
you do not select recipients, all users will receive the message.

You can send a message to tenants in locations or groups you select, or only some tenants in the locations or groups you select. Use
the list and the search field to narrow your selection and find the tenants you want to receive the message.

Your selections are highlighted with a green bar. Click Show selected to see the list of tenants you chose to receive the message.

Page 19
When the tenant users log in, they will see the message bar at the bottom of the screen. Controls on the left side of the message
minimize the message, scroll through multiple active messages, or zoom to display a long message.

Desktop client not included with ISO

The desktop client is now hosted and is no longer included with the ISO. There is no longer a strict version number match between the
server and client.

You do not always need to update desktop clients when you update your Data Center Operation server. If a client update is required, a
message will appear when you start the client for the first time after updating your server. The desktop client now seamlessly handles
new server versions by downloading the required files the first time it connects to the server. The desktop client stores files for each
version and use the files corresponding to the server version it connects to. There is also an option to download the desktop client in
your profile in the web client.
You can now configure the default folder where desktop client modules are installed.
When the Data Center Operation client is started for the first time, it downloads modules from the server. Users who do not have
permission to write to the installation folder cannot start the desktop client. You can now specify the folder where desktop client modules
are installed.
Edit the StruxureWare Data Center Operation.ini file in the installation directory, for example, C:\Program Files\StruxureWare Data
Center Operation 8.2.7\application\. Add one of the following lines, then save the file:

Page 20
 To use the installation directory as the folder for downloading modules: -DdropinsUseInstanceLocation=true
To use a custom folder for downloading modules: -DcustomDropinsLocation=custom_folder_path
Examples:
-DcustomDropinsLocation=C:\DCO_Modules
-DcustomDropinsLocation="C:\DCO Modules"

If no option is defined in the .ini file, or if both options are defined, -DdropinsUseInstanceLocation=true will be used, and modules will
be downloaded to the installation directory.
Clustered environment is no longer available
Clustered Environments will no longer be available as an installation option in Data Center Operation starting with version 8.2.7.
Performance, uptime, and stability, especially in scalable situations, has proven to be significantly better at one node than with several in
a cluster.

There are two alternatives to achieve the same results as a cluster:

Use EcoStruxure IT Advisor

Disaster recovery in StruxureWare Data Center Operation

Note: Your clustered setup will not be saved when you upgrade to version 8.2.7. You must switch to one of these two alternatives.

Existing disaster recovery node setups must be reattached after updating to version 8.2.7.

More...
Other features
The ETL password is now encrypted.
Active Directory integration improvements including support for mutual trust between the child and parent domain controller.
Vizor is no longer supported and is no longer available in the app stores.
The 8.2.7 release allows your organization to fulfill GDPR requirements.

What is new in StruxureWare Data Center Operation 8.2.2

The 8.2.2 release includes critical security updates for Meltdown and Spectre. Red Hat users should also update packages.

Note: This is not a mandatory release, as it only includes security package updates. You can update your OS manually using standard
OS update functionality. However, we recommend you always run the latest version.

What is new in StruxureWare Data Center Operation 8.2.1

Reverse U position
The rack U position numbering can now be configured to start from the top instead of the bottom of the rack. The rack can also start
counting U positions from zero instead of one. More information is available here.

ETL manufacturer nameplate in export database

The value for the Manufacturer's Nameplate is now included in the ETL export database. More information can be found here.

ETL Amp measurements in export database

The Manufacturer's Nameplate Amp value is now included in the ETL export database. More information can be found here.

KPI improvement
Performance improvements on the KPI jobs.

What is new in StruxureWare Data Center Operation 8.2

The 8.2 release improves workflow planning, and includes additional fixes and improvements.
Improved work flow planning
The 8.2 release improves the workflow process.

In the desktop client:

New work flow processes replace templates

Set up strict work orders with processes that must be followed

New work order recording task

Add start and end nodes in the work flow view

New work order process permissions

Page 21
 More...

Desktop client

New work flow permissions

There is a new user permission for administration of work flow processes under Global Permissions in Administration > Users or U
ser Groups in the web client.

More about user permissions...

Require work orders to follow a process

You can now require work orders to follow a selected process in Tools > Preferences.

Page 22
Enhanced Active Directory and LDAP support
You can now add details about your Active Directory or LDAP server in the Administration > Authentication Servers option in the
web client. This enables you to search the authentication server for users and groups, and to send email to individual users in work
orders (if the server has a valid email for that user).

When adding a group from the authentication server (AD or LDAP) all users in that group can login to Data Center Operation, it is no
longer necessary to create separate users in Data Center Operation.

Plan floor mounted equipment

The work order functionality has been extended, so you can record putting equipment on the floor. Coordinates are used to place it
and reserve the space.

Improved Rack ATS support

Rack ATS are now modeled much better. They can be part of the power path, and the power capacity calculations take them into
account. They are also shown as power assets in the Genome Library.

Updated Java package

The Java package has been updated to 1.8.0.152. This resolves a prior issue with a memory leak in version 1.8.0.144.

External systems supported in DCO 8.2

DCO 8.2 supports these external systems:

External system Latest version Version supported

VMware vSphere 6.5 vSphere 6, 6.5

Cisco UCS Cisco UCS 3.1(2b) Cisco UCS 3.02cPE1, Cisco UCS 3.1(2b)

ITO ITO Server version 7.5.2.0.119 ITO Server version 7.5.2.0.119

Remedy BMC Remedy 9.1 BMC Remedy 8.1

Note: Only Remedy versions prior to 9.1 are supported.

SCOM SCOM 2016 SCOM 2012 R2, SCOM 2016

StruxureWare Data Center Expert Data Center Expert 7.4.3 DCE 7.4.3, 7.4.1, 7.4

EcoStruxure Power Monitoring Expert PME DC 8.2 PME DC 8.1, PME DC 8.2

HP OneView 3.0 3.0

Cooling Optimize 6.6 Iceman 6.6 Iceman

What is new in StruxureWare Data Center Operation 8.1

Work flow planning

The 8.1 release improves workflow planning.

In the the desktop client:

Graphical workflow editor

Page 23
 New work flow templates

Assign templates to a group

More...

In the web client:

Execute tasks and change task status

Sort workorders by your tasks or your group's tasks

More...

Desktop client

Web client

New user groups

You can now configure authentication server groups for the following servers:
Active Directory
LDAP
Data Center Expert

Note: You must configure the authentication server first.

You can now create local user groups that contain DCO users.

Page 24
 Authentication server group

Local user group

Web client: Barcode scanning on smartphones

You can now scan a barcode to view a device or rack.

On Android, you tap the icon and scan the barcode to view.
On iOS, you tap the icon to take a photo of the barcode. DCO then finds the barcode in the photo. You can also use photos you
already have on your device.

Note: This feature is not supported on the Safari browser in iOS 11. Use Chrome with iOS 11 instead.

Web client: Capacity overview for locations

You can now toggle the inventory view to show either the inventory or capacity overview for the selected location.

Page 25
Web client: Branding has moved
The branding path has moved:

Old: /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/branding
New: /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding

Read more on branding here: Customizing web branding

Web client: Optimized to run on your smartphone

You can run the DCO Web client on your smartphone.

The layout scales smoothly to scale and show layout items as lists on smaller size screens rather than tiles, for example to show
rooms, floor and rack layouts as listed items rather than tiles, etc.

Web client inventory shown as tiles

Web client inventory shown as list on smartphone

Page 26
Platform: Information about software packages and services now available in
Webmin
In the DCO server management web interface (Webmin), you can see a list of installed software packages and services on the DCO
server, including version specific information.

Download new StruxureWare Portal 1.3.6 compatible with DCO 8.0.4

There's a new version of the StruxureWare Portal available for download here.

It is compatible with DCO 8.1 and includes a fix for adding markers to location maps.

Download links for Mobile, ITO and Server Access

Download links to StruxureWare Data Center Operation: Mobile and StruxureWare Data Center: IT Optimize and Server Access are
not available from the server's download page. They are available from the same location as the DCO .iso file. You can get these
through technical support.

DCO: Genome library version specification

The latest updates to the Genome Library at the time of the release are included with the release. However, the Genome Library is
continuously updated and you don't need to wait for the next release to get these updates. Regular updates to the Genome Library
are available for download independently of DCO releases.

It is now possible to see your current Genome Library version specified in Preferences and in Help>About.

Page 27
 It is shown as a timestamp, reflecting the time when the file was developed.

DCO: Rack layout with network routes has been improved

The graphical representation of network routes in the rack layout has been improved. When right-clicking a network cable to use the
Show route feature, you would see a complicated route across multiple racks. The order of the racks in the layout has been
improved.

DCO: Excel import of manual measurements

Support has been added for importing manual power measurements into DCO through ETL.

More...

DCO: Excel import, auto association of devices with UUID

The equipment's UUID is included in the Excel import file (hidden column). This functionality enables the system to identify the
equipment when importing and automatically associating it with the corresponding DCO model item. This means you can skip the
drag'n drop device association step in the DCO layout to associate the device with the modeled item.

The functionality also works for other ETL integrations. The UUID for equipment can be found in the ETL export database.

DCO for Colo: Customer details added for Excel import

A customer column has been added to the Excel import to store data about which customer a device with measurements is
assigned to.

Support for DCO installation on RedHat Linux

You can install DCO 8.1 on either RedHat 7.x or CentOS 7.x. See instructions for installing on RedHat.

Support for continuous Genome Library updates

You can request support for devices not yet in the DCO Genome Library through EcoStruxure IT Help Center DEVICE
SUPPORT.
Regular updates to the DCO Genome Library, including support for requested genomes, will be available for download in Ec
oStruxure IT Help Center DOWNLOADS, independently of DCO releases.

Genome Library in DCO

Support for AD user groups

In the DCO web client user group settings, you can have both DCO user groups or AD user groups.

Estimated load reduced on not connected 3p server

The estimated load has been reduced for a three-phase server that has not been connected for power the DCO model.

In previous versions, a three-phase 1000 W server that was not yet connected for power would have an estimated load of 3000 W
because the system would account for the phase uncertainty. In DCO 8.1, the estimated load value has been reduced to 1000 W (3
33 W on each phase) to reduce reservation of unneeded capacity and the remaining 2000 W (666 W on each phase) will be labeled
as Power Supply Unit uncertainty.

Page 28
 Estimated load in 8.1

Additional fixes and improvements

Security: SSH configuration was hardened
Capacity: If your solution included tags on capacity groups, upgrading DCO from a version prior to 8.0 could cause the
upgrade to fail
ETL: Improvements to performance when importing data through ETL
Tenant Portal: Cage navigation has been restored
External system integration: Support added for VMware 6.5

Known issues in StruxureWare Data Center Operation 8.1.x - 8.2.12

Using the web client to download a DCO backup larger than 2GB
When you use the web client to download a DCO backup, and the file is larger than 2 GB, the browser reports the download was
successful, but the file is corrupt. This issue does not occur when you download the file by other means, such as SCP.

If your DCO backup is larger 2 GB, and you use the web client to download it, contact support for help.

Deleting a room or location also deletes user groups

When you delete a room or location, all local user groups are also deleted. This issue will be fixed in next the release.

Webmin offline upgrade from 8.x.x to 8.2.2 unsuccessful

When you upgrade DCO from 8.x.x to 8.2.2 using the offline option in Webmin, the upgrade is unsuccessful.

If your setup requires the No third party RPMs and Do not download packages from the Internet options in Webmin, create a
post in the Help Center community to request help with the upgrade. Our team will get in touch with you.

Page 29
Known issues in StruxureWare Data Center Operation 8.1

External system integrations: Latest versions of Remedy and SCOM not supported
The external system integrations for DCO support the latest versions of the integration software, except Remedy and SCOM.

Supported versions:

BMC Remedy: Remedy 8.1

Microsoft System Center Operations Manager: SCOM 2012 R2

Broken download links for ITO

Download links to StruxureWare Data Center Operation: Mobile and StruxureWare Data Center: IT Optimize and Server Access are
not available from the server's download page. The links to ITO on the download page do not work. Contact technical support for
these.

Vizor: Issues in iOS 10.1.1

StruxureWare Data Center Operation: VIZOR doesn't work in iOS 10.2.1.

3D graphics issue
A 3D view graphics issue has been observed on Macintosh computers with Intel 4000 and Intel Iris graphics cards. Specifically, an
issue with black screen showing was observed on Macs running macOS Sierra with an Intel HD Graphics 5000 card and DCO 8.1.
Other versions may also affected.

Page 30
DCO 8.x may be affected by a critical memory leak in the latest Java package
The latest Java package contains a critical memory leak that can cause the DCO server to run out of memory and shut down, typically
within a few days. https://bugs.openjdk.java.net/browse/JDK-8164293

DCO 8.x installations or upgrades performed after June 26, 2017 (Java 1.8.0_144 release date) may be affected.

A DCO server can shut down within a few days as it runs out of memory if the Java package Java 1.8.0_144 is installed. If the server is
running fine, it is unlikely to have this Java package. Only the Java 1.8.0_144 version is affected.

This issue will be fixed when Java 1.8.0_152 is released as a CentOS package, expected in Oct 2017. For more information, see http://
openjdk.java.net/projects/jdk8u/releases/8u152.html

Workarounds

There are some workarounds for this issue:

For clean installs

Put the server in offline mode by turning interfaces off in Network & Host Name settings.

For upgrades

Select offline mode before upgrading.

For DCO servers already in this situation

If the DCO server is already in this situation, perform the following steps.

If the server is offline

Run this command to check the Java version:

Page 31
java -version

If the server is online

1. SSH login to the server.

Verify that it has the issue.
Run the command:

yum list installed java-1.8.0-openjdk*

Check that the versions start with: ‘1:1.8.0.144’, ex: ‘1:1.8.0.144-0.b01.el7_4’

If the server is offline, run this command to check the Java version:

java -version

2. Run the following single command:

yum downgrade java-1.8.0-openjdk java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el7_4.x86_64

java-1.8.0-openjdk-devel-1.8.0.141-2.b16.el7_4.x86_64

Verify that the package has successfully been downgraded.

3. Run the command:

yum list installed java-1.8.0-openjdk*

Check that the versions start with: ‘1:1.8.0.141’, ex: ‘1:1.8.0.141-2.b16.el7_4’

4. Reboot the server.

Page 32
Understanding the new Capacity implementation
In DCO 8.0 it is easier to set up and use the capacity management module as the implementation of system rules behind the
calculations has been simplified. This means there are a few new concepts to learn so here's an introduction and overview of how the
changes affect your existing system.

New implementation and concepts

Previously the capacity of the racks was defined by the capacity groups. In DCO 8.0 it is defined by the size of the breakers on the rack
PDUs and receptacles in the racks.

The new capacity is defined by:

1. Breaker size (derated capacity of the breakers in the power path)

2. UPS capacity (upstream limitation)
3. Design limits (on racks and rack PDUs)

Note

The new capacity calculations require a valid power path and only work if you have configured an upstream connection to one
of these power sources:

UPS
Input breaker on a PDU/Power Panel (switchgear>mains supply)

How do the changes affect my existing solution?

As the system automatically calculates your capacity based on the modeled data center:

You will see some changes in the way the capacity calculations appear, both the actual power values and what is shown in the
tooltips.
You no longer need to define capacity groups.
Some new capacity concepts have been introduced, and some concepts now have a changed meaning. Here's an overview:

Changed concepts

Concept Relevant if... Meaning in version 7.5 and previous versions Meaning from version 8.0

Estimated You have equipment connected Sum of server load x connections to account for uncertainty if multiple power Less pessimistic because the other new
load to multiple power sources. sources were used. concepts introduced handle some of
the uncertainty and explains the design
in a more clear way.

Remaining You are planning to add further How much power capacity remains in the rack without exceeding the allowed The concept is the same but it is no
capacity equipment to your design. This average load that you planned for the racks in the active capacity group. longer tied to capacity groups.
concept guides you in regards to
remaining capacity available. The remaining physical capacity is
limited by any upstream limitations,
such as the remaining capacity of the
UPS or on the input breaker of the
PDU.

For Rack PDUs, the Remaining

Capacity is limited by the design limits.

See here and here.

Failover You have a redundancy setup. In a redundancy setup the additional load on a power feed in case the other Same meaning but option for basing
load power feed is turned off. For example, if an A-Feed UPS was turned off, the this on measured data rather than
B-Feed UPS has to carry the full load, and so should the Rack PDU breakers, estimated load.
etc. This used to be calculated based on estimated load.

Adjusted You have a distribution The reserved capacity for distribution redundancy was illustrated with the N/A
average redundant setup and have capacity group's adjusted average.
servers connected to different This concept has been replaced by the
phases. new Reserved for Distribution
Redundancy concept.
(Enabled advanced tooltip on
rack in Power overlay)

Largest Just one value Split into two values, one for servers
Possible with redundancy (redundant) and one
Server for servers without redundancy (single).

New concepts

Page 33
Concept Relevant if... Meaning in version 7.5 and Meaning from version 8.0
previous versions

Reserved You have a setup with distribution N/A In a setup with distribution redundancy (redundancy at the PDU or rack
for redundancy (redundancy at PDU or rack PDU level) and load connected to a mix of phases, it is necessary to
Distribution PDU level) and have load connected to a reserve additional capacity in the shared part of the power path. This
Redundancy mix of phases. reservation is referred to as Reserved for Distribution Redundancy.

Power You have a complicated N setup with N/A Power Supply Unit (PSU) Uncertainty indicates a risk in the power supply
Supply Unit mixed power phase setups. It increases th path that the indicated load could be moved from one phase to another.
Uncertainty e estimated load. See more about PSU Uncertainty here.

Design You are planning capacity. It is a N/A You can set a design limit on rack and rack PDU level.
Limits theoretical planning concept replacing the
deprecated capacity group concept. For a rack PDU:

The specified limit is distributed on the connected phases. For example, a

design limit of 6 kW on a three phase rack PDU will give a design limit of 2
kW for each phase.

The limit is treated the same way as a physical breaker limit, so both
estimated load and failover load are taken into consideration when
calculating available capacity.

For a rack:

The specified limit is based on the total load in the rack. That means there
is no phase distribution and it could be possible to utilize the entire rack
design limit on one phase, for example L1.

The limit is based on solely on the total estimated load in the rack whereas
the failover load does not influence the rack design limit.

Predicted Instead of only looking at today's N/A Predicted power is a capacity strategy defining how estimated load is
Power measured data, you are predicting how calculated. The calculations run in the background and affect capacity
they are going to be in the near future. Re It was actually introduced in DC values all over the DCO interface, such as impact and failover load.
al measured data is used to create O 7.2.5 but was only running in
trending. special scenarios. In 8.0 you can It bases power calculations on measured peak data from DCE or other
select it as the main strategy. external system integrations. The default implementation of 30 days
trending and fixed min and max values can be customized.

It replaces previous implementations in which predictions were based on

estimations.

Remaining You're planning to add further equipment N/A The remaining capacity in a rack. It is shown in the rack tooltip as either R
Redundant to your design. This concept guides you in emaining Single Capacity or Remaining Redundant Capacity dependin
Capacity regards to remaining capacity available. g on what type/level of redundancy is detected for the rack.

Remaining You're planning to add further equipment N/A The remaining capacity in a rack. It is shown in the rack tooltip as either R
Single to your design. This concept guides you in emaining Single Capacity or Remaining Redundant Capacity dependin
Capacity regards to remaining capacity available. g on what is detected for the rack.

Deprecated concepts

Concept Relevant if... Meaning in version 7.5 and previous Meaning from
versions version 8.0

Capacity You were using capacity groups for capacity planning, reserving power source Reserving power on UPS N/A No longer
group capacity for a group of racks possible.

Page 34
Getting from previous versions to DCO 8.x
The latest version of DCO is available to customers with a valid Software Support contract.
To verify your contract and receive the latest download links, please fill out this form.
To upgrade to the latest version of 8.x, use one of these 2 methods:

Backing up a previous version and restoring it on a new clean 8.x installation

You can use this for upgrading from any DCO versions 8.x and 7.x.
Upgrading using the latest 8.x iso file
You can use this for upgrading if your current version of DCO is at least 8.0.

Logging in to the new version of DCO after upgrading

From Version Upgrade Path

8.x Upgrade or backup/restore

7.x Backup/restore

Older than 7.0.0 Backup/restore

Note: You'll need to restore your backup on a 7.x server first before you can restore it on 8.x.

Backing up a previous version and restoring it on a new clean 8.x installation

This upgrade method includes taking a backup of the data on your old DCO, making a clean installation of DCO 8.x, and then restoring
the data in the new DCO installation.

If your previous version is older than version 7.0.0, you'll need to restore your backup on a 7.x server first before you can
restore it on 8.x.

First, remember to back up your solution to be able to restore the backup after installing StruxureWare Data Center Operation on
the new server. The installation will wipe all current data. You will lose all data if you skip creating the backup.

A new installation of StruxureWare Data Center Operation 8.x is required, preferably on a new dedicated server. You can then
transfer all your data (data center model, user settings, historical data, and licenses) without loss using the backup and restore
procedure.

Recommendation

Install DCO 8.x on a new server and keep the old DCO version running concurrently on the old server until you have verified
that your new DCO 8.x server is up and running.

Installing StruxureWare Data Center Operation on the existing server is not recommended. If you choose this approach, be
sure to create an external backup file before beginning the new installation process (e.g. save to a share or download
the backup). See more here.

Page 35
Saving a backup from the existing Data Center Operation server

1. Open the Webmin web interface in a browser by typing the address of your Data Center Operation server in a Web
browser followed by :10000, https://<hostname>:10000 - e.g.: https://192.168.1.100:10000 .
2. Log into Webmin and in the left menu, select StruxureWare DC Operation.
3. In the submenu, select Backup, and optionally type a comment for the backup.
4. Click Backup now. You have now created a backup in a local backup directory (/data/backup) on the server.
5. Download the backup from the server by selecting StruxureWare DC Operation>Restore, selecting the backup you want to
download, and clicking Download selected backup. This file is the one you will later upload to your newly installed DCO 8.x
server.

Setting up a new server with a clean installation of StruxureWare Data Center Operation

See the entire installation process here.

Copying the backup file to the new server

1. Open the Webmin server configuration interface.

2. In the left menu, select System>Upload and Download.
3. Click the Upload to server tab.
4. In Files to upload, browse to the location of your saved backup file.
Make sure the file format is: <name><yyyy-mm-dd><hh.mm>.tar.gz
5. In File or directory to upload to, select the location on the Data Center Operation server in which to save the file: /data/bac
kup.

Restoring the backup file on the new server

1. Open Webmin for the new server on which you want to restore the backup.
If you are working with a cluster environment, type the virtual IP address of the cluster.
2. In the left menu, select StruxureWare DC Operation>Restore.
3. Select an uploaded backup file and click Restore selected backup.
If the backup you want to restore is not in the list, upload the file.

Upgrading using the latest 8.x iso file

Upgrading to StruxureWare Data Center Operation version 8.x takes at least 10 minutes (depending on the size of your solution).
Perform a backup of the data on the Data Center Operation server before initializing the upgrade.

Note

You can upgrade a Red Hat based DCO server from version 8.0 to the latest 8.x versions.

For versions older than 8.0, use the backup/restore method to get to the latest version.

If you are upgrading a cluster environment, you only need to perform the upgrade on the slave node, not the master node. The upgrade
takes up to about 20 minutes. You should not try to access or use StruxureWare Data Center Operation during the upgrade.

If you have a disaster recovery node, you will have to upgrade that as a stand-alone server after upgrading the cluster.

Prerequisites:

Ensure you back up the data on the existing Data Center Operation server to a remote location.
Uploading the .iso file through Webmin requires a browser supporting file upload sizes over 2GB, such as:
Chrome, version 8 or higher (Windows, Mac OS X, Linux)
Safari, version 5 or higher (Windows, Mac OS X)
Opera, version 11 or higher (Windows, Mac OS X, Linux)
1. Download the .iso file from a location provided by the support team and copy the SHA256 key from the same location.
To locate the telephone number for the support you need, visit Contact Us.
2.

Page 36
 2. Upgrade StruxureWare Data Center Operation.

Info

In a cluster environment this step is only required on the node where the upgrade is performed.

a. In the Webmin left menu, select StruxureWare DC Operation>Upgrade.

b. In Select upgrade file, browse to the location of the downloaded StruxureWare Data Center Operation .iso file.
If you upload the .iso file to the StruxureWare Data Center Operation server without using the Webmin interface, place
it in the /data folder.
c. Copy the SHA256 key and paste it into the SHA256 checksum from the download page field.
d. If your setup requires it, select the non-obligatory fields, No thirdparty RPMs* and Do not download packages from
the Internet.
- Selecting to not include 3rd party files may be relevant if you are running on Red Hat and your company policies force
you to install those packages separately. *Do not select this option as the upgrade will fail! Instead, if your setup
requires this option, create a post in the community requesting help with the upgrade and our team will get in
touch with you.
- Selecting not to download from the Internet may be relevant if you know you don't have an Internet connection during
the upgrade as it may be a bit quicker when the upgrade doesn't check for newer files online.
e. Click Upgrade.
3. When you have completed the upgrade, you can launch the web client and download the latest version of the StruxureWare
Data Center Operation desktop client.
a. On the computer on which to install the StruxureWare Data Center Operation client, open a Web browser and launch to
the IP address or hostname of the DCO server <serverIPaddress> to log in to the web client and get access to the
desktop client download.
(The DCO web client is automatically available with the server installation.)
b. If you're not an English speaker, select your preferred language from the profile menu Language option (profile image
in the upper right corner).
c. In Administration>Licenses add your license keys to enable download according to your purchased licenses.
d. In the profile menu select Download Desktop Clients.
e. On the download page click to download the StruxureWare Data Center Operation software according to your license
and follow the instructions in the installation wizard.
f. Repeat the above steps on all desktop client computers.

Webmin server management interface

Logging in to the new version of DCO after upgrading

Log in to the DCO web client interface with your usual credentials. From the web client, in your profile menu, you can select to
download desktop clients.

Licenses and local DCO users will be restored as part of the backup. AD users are handled in AD. All users with a password shorter
than 6 characters must change their passwords. For security reasons, it is recommended that you create a new DCO administration user
with a complete set of user rights, including user administration rights, and then delete the default apc/apc user, or at the very least that
you change the password of the apc user.

After making sure that the data was successfully restored, you can decommission the old server.

Page 37
How to transition from a clustered environment to disaster recovery
When transitioning from a clustered environment to disaster recovery, you need to:

1. Backup your solution.

2. Do a clean install of StruxureWare Data Center Operation.
3. Restore from your backup.

For information about backup/restore, see Getting from previous versions to DCO 8.x

For information about how to configure the disaster recovery node, see Disaster recovery.

Page 38
Clustered Environment no longer available in DCO 8.2.7
Clustered Environments will no longer be available as an installation option in Data Center Operation starting with version 8.2.7.
Performance, uptime, and stability, especially in scalable situations, has proven to be significantly better at one node than with several in
a cluster.

There are two alternatives to achieve the same results as a cluster:

Use EcoStruxure IT Advisor

Disaster recovery in StruxureWare Data Center Operation

Note: Your clustered setup will not be saved when you upgrade to version 8.2.7. You must switch to one of these two alternatives.

About EcoStruxure IT Advisor

IT Advisor is a cloud-based application for asset and capacity planning and risk management, visualizing physical infrastructure and IT
data across the enterprise.

Open platform, vendor neutral

Use one platform to analyze data from any vendor, with an enriched data model across all EcoStruxure platforms.

Access your data from anywhere, without VPN, using web browser clients and an app.

Contact sales for more information about EcoStruxure IT Advisor.

About disaster recovery in DCO

If you are currently running on Clustered Environment and want to minimize the risk of data loss, you can add an offsite disaster
recovery node to your standalone Data Center Operation (DCO) instance. This requires a DCO Cluster Node license (SFTWCLUSTER-
DIGI).

Supported DCO setups:

1 standalone node
1 standalone node + 1 disaster recovery node (requires 1 High Availability license)

When transitioning from a clustered environment to disaster recovery, you need to:

1. Backup your solution.

2. Do a clean install of two standalone DCO servers. One will be used as the operational server, and the other will be configured
as the disaster recovery node.
3. Restore your backup on the operational server.

Note: If there is a cluster node license included in your backup file, it is also valid for the new standalone + disaster recovery node setup.

For information about backup/restore, see Getting from previous versions to DCO 8.x

How to configure a disaster recovery node

In the following example, two stand alone servers have been created, Server1 and Server2. Server2 will be configured as the disaster
recovery node to Server1. This Standalone + Disaster Recovery setup requires a cluster node license. Managing licenses

If the Disaster Recovery node is monitored by Data Center Expert via SNMP, it is important to set the device scan timeout in DCE
high enough for the Disaster Recovery node to respond. Otherwise, it will return 'communication lost'. How you set the device scan
timeout depends on the network speed between the Disaster Recovery node and the DCO server.

Log in to the Server1 webmin interface, and select StruxureWare DC Operation > Disaster Recovery.
Select Allow another node to connect to this node.

In Allow the following IP as disaster recovery node, enter the IP address for Server2.

Click Attach.

Page 39
 Check Accept fingerprint

then click Allow.

Once the fingerprint is added successfully, follow the on-screen instruction and go to webmin for Server2 to continue the setup.

Go to Server2, webmin interface > StruxureWare DC Operation > Disaster Recovery.

Select Attach this node (xx.xx.xx.xx) as a disaster recovery node to another node/cluster.

Enter the IP address for Server1 in Attach this node to the following IP:

Click Attach.

Page 40
 Check Accept fingerprint.

Click Attach.

While the node is successfully being attaching, the notification is Attaching the node, please wait this could take several minutes......

The Server1 Status page displays information for both itself and Server2 as Disaster Recovery.

Page 41
The Server2 Status page displays information only about itself as Disaster Recovery.

Add a license

The standalone node + disaster recovery node setup requires a DCO Cluster Node license.
Log in to the standalone server (Server1) web client, and go to Administration > Licenses.

Enter the license key, and click Add license.

Page 42
StruxureWare Data Center Operation release summary
Version Date Release Content (Highlights)

8.3 April 2019 Rack PDUs with banks and outlets definition

Vertical U-Positions

New attribute are now included in the ETL export database

Energy Cost license removed and StruxureWare Insight removed.

8.2.14 February Includes security updates

2019
Update java to openJDK

Angular upgrade to version 7

Web Client now is separated from JBoss server

In Web Client power connection feature is simplified

8.2.12 November Change Request

2018
Change request templatet

Barcode lock feature

Improvements to reports

Server management options moved from Webmin to the web client

8.2.7 June 2018 Extended power capacity information for rack mount PDUs

Ability for colocators to send tenants messages in the web client

Discontinues the clustered environment

Allows GDPR compliance

8.2.2 February Critical security updates for Meltdown and Spectre.

2018
This is not a mandatory release, as it only includes security package updates.

8.2.1 December
2017
Reverse U position
ETL manufacturer nameplate in export database

ETL Amp measurements in export database

KPI improvement

8.2 November Improved work flow planning

2017
New work flow permissions

Require work orders to follow a process

Enhanced Active Directory and LDAP support

Plan floor mounted equipment

Improved Rack ATS support

8.1 April 2017 Improved work flow planning

8.0.4 February Server: Memory issue fixed

2017
Web client: Optimized to run on your smartphone

Web client: New capacity overview for locations

Web client: RackPDUs are now selectable items and you can edit properties

Platform: Information about software packages and services now available in Webmin

Download links for Mobile, ITO and Server Access

Additional fixes and improvements

Page 43
8.0.3 January Genome library version specification in Preferences
2017
Rack layout with network routes has been improved

Fix for Map View capacity overview issue if a power path spanned multiple rooms

Fix for manual measurements phase to phase breaker issue

Fix for issue preventing DR node setup

Fix for issue showing 3D layout

Fix for issues editing existing StruxureWare Lab solutions

Fix for Energy Efficiency scripted sensors duplication

8.0.2 November Support for import of manual power measurements

2016
Auto association of devices when importing manual power measurements

Ability to enter Colo customer information (device assigned to customer) when importing manual power
measurements

Vizor support reenabled (except iOS 10.1.1)

Fix for PME integration measured values not updating

Fix for Change: long work order texts preventing save

Cluster stability improvements

8.0.1 September Support for RHEL 7 (only RHEL 7.x)

2016
Support for AD Groups

Fix for potentially serious issue with log files growing in some setups, potentially taking up all disk space and
preventing DCO from running.

Minor fixes

8.0 July 2016 New Web Client

The new DCO web client provides easy access to features you need on a day-to-day basis, such as floor
view and rack inventory management. In addition some desktop client administration features moved to the
web.

New Tenant Portal

The Tenant Portal is a Colo edition of the DCO web client. In addition to all web client features, it includes a
customized feature set for colocation providers and allows for a sub set of these to be made available to
tenants.

Desktop Client
New features in the desktop client include: support for Direct Current and single phase equipment, power
paths without UPS as top level item, improved tooltips and colo overlay.

Server and platform updates

The installation and configuration happen as in previous versions but platform components have been
updated for improved security and performance, including RESTful API for faster, more rich third party
integrations, improved client/server communication, cluster simplification.

Miscellaneous updates
The genomes library has been extended, more 3rd party system integrations are supported, and updates are
available for Mobile, Portal, Vizor, and PRO Pack.

7.5 June 2015 Network Enhancements

New cable genomes, port types, and Network Cable Browser
Network cables are now available as genomes, and you can set properties on them.

Power Enhancement
A new Power Path Layout has been introduced, showing a graphical overview of the power connections from
UPS units to racks.

Change Work Order Improvements

For organizations having strict policies around their work order process, a new lock functionality has been
added to work orders and work order templates.

New Predefined Table Configuration

New predefined table configurations are available as well as the option to create your own predefined
configurations. This enables you to create and toggle between multiple configurations suited for different
purposes.

New Confirm Deletion Option

If enabled, a new confirmation message appears when deleting equipment.

Page 44
7.4.5 February Data Center Operation: Cooling Optimize
2015 Data Center Operation: Cooling Optimize is an add-on module to StruxureWare Data Center Operation that
provides continuously optimizes temperatures in the data center facility, delivering improved reliability and
availability.

HP OneView
The HP OneView connector enables communication between ITSM and DCIM platforms providing
simultaneous visibility to both IT and facilities managers.

Support for Red Hat 6.x

Starting from version 7.4.5 StruxureWare Data Center Operation is available using Red Hat Enterprise Linux
as OS on the server.

Work Order Updates

StruxureWare Data Center Operation v7.4.5 updates the Work order functionality in the StruxureWare Data
Center Operation: Change module.

Audit Trail Report

StruxureWare Data Center Operation v7.4.5 updates the audit trail functionality

7.4 January Visual Network Management

2015 StruxureWare Data Center Operation v7.4 greatly extends network management functionality.
- Graphical network connections
- Visual port mapping
- Cable route visualization
- Cable type visualization
- Network impact analysis
- Import and export of network data
- Network management tasks in audit trail

Visual breaker panels

- Manage capacity at breaker level
- Breakers available in Genome library
- Branch circuit monitoring
- Print breaker panel schedules

CAD improvements
Support for AutoCAD 2013 file format, ability to import many more shapes and export to CAD with separate
layers for each overlay.

Cooling calculator improvements

7.3.6 January Improved extended SNMP alarm statuses

2015 Improved extended SNMP error reporting is available in StruxureWare Data Center Expert if you are
monitoring StruxureWare Data Center Operation from StruxureWare Data Center Expert.

Windows 8 support
StruxureWare Data Center Operation is now supported on Windows 8.

Support for integration with StruxureWare Power Monitoring Expert 7.2 Data Center Edition
Integration with StruxureWare Power Monitoring Expert 7.2 Data Center Edition is now supported through
ETL. Configuration is done in StruxureWare Power Monitoring Expert 7.2 Data Center Edition.

External system integration: new full alarm synchronization setting

You can now configure how often StruxureWare Data Center Operation synchronizes alarms and alarm
statuses from StruxureWare Data Center Expert.

Improved ETL functionality

The ETL error handling has been improved

New receive timeout option in the logon dialog advanced settings

A new timeout option has been introduced in the logon dialog advanced settings, allowing you to specify how
many seconds the client should wait before timing out when trying to receive data from the server.

7.3.5 August Server Access and Power Cycling

2013 Data Center Operation: Server Access is an add-on module to StruxureWare Data Center Operation that
provides a software KVM solution. It allows you to control servers from multiple vendors remotely from
StruxureWare Data Center Operation, whether they are turned on or off, without the need for additional
hardware or cabling.

Improved ETL Export Functionality

Cage size data in the ETL export database.
Improved parent pointers in the ETL export database: The cage parent is now a cage if it is inside another
cage. In previous versions, the parent pointed at the room.
A user to access Operation web services in ETL transformations.

Page 45
7.3 June 2013 Copy/Paste
Copy/Paste context menu options on floor and rack equipment and shortcuts have been introduced
(Windows Ctrl+C, Ctrl+V / Mac Cmd+C, Cmd+V). A Clipboard panel containing the copies was introduced
next to the Navigation and Genomes panels. It gives possibility to copy/paste equipment on the floor, such
as racks, PDUs, UPS and cooling units as well as equipment in the racks, such as servers and patch panels.
You can copy/paste individual pieces of equipment or multiple items, such as a rack and its contents.

Genome Library Bundle Support for Process Optimization

In Genomes, you can add multiple pieces of equipment with bundles and copy/paste. Together with work
order templates, this is powerful for quickly adding bundles of pre-equipped rows or racks to support the
installation in large setups.

New Webmin server interface for the cluster setup

Customer no longer need to configure cluster environments through the command line interface and the
process has been simplified. In addition, the Webmin interface has been improved in general, collecting the
StruxureWare Data Center Operation settings

Disaster Recovery
A back-up node can be configured for resuming operation in the event of a disaster

Power Capping
New rack-level power capping functionality powered by Intel DCM for increasing power usage accuracy and
delay physical equipment investment. Intel DCM is now installed with the IT Optimize server for one common
IT monitoring server

Sensor Mapping
New overlays and live temperature mapping have been introduced and the 3D visual appearance has been
improved

Integration with data sources through a new ETL system

Two-way data exchange between StruxureWare Data Center Operation and a broad range of data storage
systems. Extract, transform and load data directly from the Data Center Operation server. Associate external
data with items in your data center model.

Improved custom property editing and new template functionality

A new menu item has been introduced for global configuration of custom properties, Tools>Configure
Custom Properties. You no longer have to configure properties for one component at a time. Creating
templates allows you to reuse standard properties.

StruxureWare Portal
Portal framework with additional portlets and connections to Schneider Electric and non-Schneider Electric
systems for transparency to StruxureWare key performance indicator data.

Mac Support
The client now runs on OS X.

Security enhancements
Multiple security enhancements have been implemented, working towards DIACAP certification.

7.2.5 January Import CAD drawing

2012 Import CAD drawing and build data center model based on it. Automatically recognize room shapes and
dimensions. Support for multiple layers is included.

Multi tenant management tool

Cages, equipment and racks can now all have owner assigned and managed. Customer information
obtained from CRM applications. Impact analysis includes customer information.

Floor space management

Floor area divided into cages and space automatically calculated and reported in easy to understand KPI.

Distributed redundant UPS

Support for new power redundancy models with distributed redundant UPS.

New reports
Reports for multi-tenant features: floor area usage, customer equipment report, power sold reports, impact
analysis report, contiguous rack report, and many others.

Page 46
7.2 June 2012 StruxureWare Data Center Operation: IT Optimize
New module that provides insight into the IT layer of the data center through integration with external IT
systems through SSH, SNMP, WMMI, or VMware. Compares server power draw and CPU utilization.

StruxureWare Data Center Operation: IT Power Control

New addon module to StruxureWare Data Center Operation: IT Optimize powered by Intel®DCM for power
data support through IPMI. Enables power capping for Intel chipsets.

Cisco USC Manager integration

Provides unified, embedded management of all software and hardware components in the Cisco UCS.
Controls multiple chassis and manages resources for thousands of virtual machines. Enables automatic
power capping.

Enhance User Interface

Consolidation of various overlays into simpler, richer overlays to support Power, Cooling, Network and
Physical space. Merging of room and rack layout editor into one split pane editor with introduction of new rear
rack view.

7.1 April 2012 Merged perspectives

IT Change perspective merged into the Data Center Planning perspective for improved usability.

Integration to BMC Remedy Change Management

Allowing tickets created in BMC Remedy Change Management to be seamlessly shared with StruxureWare
Data Center Operation: Change for ticket completion (twoway integration).

New Work Order editor

Improved usability when planning changes to IT equipment.

New Work Order Templates

Enabling user defined templates to be utilized when planning changes or facilitating maintenance check.
Templates can be defined as recurring.

New work order overview perspective

Provides a filterbased drilldown overview of work orders in the system based on location, project code,
assignee, and time. Allows managers to carry out resource planning and avoid scheduling conflicts.

New Master Product Catalog

Improved usability when working with the master catalog items and adding catalog items from the master
catalog to the user catalog.

Support for Branch Circuit Monitoring

Association of multiple device sensors from one component (branch circuit) to multiple data center items in
the layout using draganddrop.

Data import from Aperture Vista

Enabling seamless migration from Emerson Aperture Vista by importing all configuration data.

7.0 October New scalable StruxureWare Operations server platform

2011 Separation of StruxureWare Operations and StruxureWare Central into 2 separate servers, by removing the
StruxureWare Operations binaries from the StruxureWare Central Server. New StruxureWare Operations
server is based on J2EE technology using Red Hat JBoss

New Cluster Node license

A new license is available for cluster environments enabling increased availability through failover cluster
setup and better performance through load balancing.

StruxureWare Operations: Insight

New custom report design application enabling quick report design using drag and drop.

StruxureWare Operations: VIZOR

New smartphone application for iOS and Android, providing graphical presentation of power, cooling,
network, and space capacity utilization in real time.

Performance optimizations by introduction of partial load

Increased performance by only loading what is currently needed, for example, only the equipment in the
rooms currently opened, and only the recommendations for that equipment.

Support for integration with multiple external systems

Including access to multiple StruxureWare Central servers, VMware vCenter and Microsoft VMM.

User management, authentication, and finegrained user rights

Enhanced user rights settings allowing access restrictions to protect functions, locations and rooms that only
a subset of the operational team is allowed to see or edit.

Page 47
6.2 February Configuration import from InfraStruxure Designer
2011 Ability to import a configuration for a new Data Center created in InfraStruxure Designer.

Integration with VMware vCenter

Ensures that the VMware vCenter Server is aware of critical physical infrastructure alarms and events and
can execute corrective actions to move virtual machines to nonimpacted areas within the data center.

Cooling optimizations
Various enhancements to the cooling portion including optimized cooling calculations with more advanced
cooling configurations, cooling impact analysis and improved tooltips for cooling scenarios.

Capacity optimizations
Various enhancements to the capacity planning portion including improved phase balancing, more detailed
support for 2N redundant scenarios and new capacity report.

Network Management optimizations

Various enhancements to the network management portion including a new network report, notifications of
available copper and fiber ports and increased usability for handling network connections.

6.1 August New Network Management Implementation

2010 Network route documentation (active device to active device through passive device(s)) using autocomplete
functionality.

New InfraStruxure Operations PRO Pack for Microsoft Virtual Machine Manager
The Operations PRO Pack ensures that Virtual Machine Manager is aware of critical physical infrastructure
alarms and events and can execute corrective actions to move virtual machines to nonimpacted areas within
the data center.

Added configuration of supporting physical infrastructure, space and products outside rooms.
A new supporting infrastructure space has been added and is now available from the new menu. New
products have been added to the catalog, such as chillers, cooling towers, pumps and switches.

Improved support for blade solutions

Handling of configuration of blade enclosures, bays, and blade servers. Blade servers and enclosures from
multiple vendors have been added to the default product catalog.

6.0 April 2010 Operations

New module with Enterprise hierarchy in a tree structure with locationbased drilldown provides a structured
overview of data center locations, from a global to local view down to single assets: locations, rooms, rows,
floormounted equipment placed in the rows, such as racks, and rackmounted equipment placed in racks.

Cooling simulation
Possible for all rack layouts within perfect horizontal or vertical rows. Rack inlet temperature is calculated for
racks within perfect horizontal or vertical rows. Support for mixed cooling environments with under floor and
rowbased cooling.

IT impact simulation
Simulating potential effect of equipment failure (UPS, PDU, cooling)

Alarms from InfraStruxure Central

Alarms highlighted in the layout to help you locate where failing equipment is located and which servers
might be impacted by that failure.

Simulation of device failures

This feature enables data center operators to proactively identify how a device failure will impact business
critical applications.

Energy Efficiency
New module to provide current and historical Power Usage Effectiveness (PUE) values and with detailed
subsystem breakdown (measured or estimated).

Alarms in audit trail

Any alarm data polled from InfraStruxure Central on the selected equipment will be included in the Audit Trail
report

Page 48
5.1 May 2009 Energy Cost Management addon to Capacity Manager
Energy usage report providing visibility into the energy usage of a specified group of equipment in kWh for
racks, rows or rooms.

Rack USpace view and report

New report and view in floor layout perspective providing an overview of the space capacity in your racks.

Scalability improvements for client, server and Mobile Datacenter Assistant

Up to 400 racks and 10,000 servers/devices are now supported.

Floor weight capacity

Support for equipment weight constraints in raised floor data centers by calculating weight and by specifying
floor tile load limits.

Perimeter Cooling
Ability to model raised floor environments and to calculate/simulate airflow of various perimeter cooling
solutions including 3rd party products.

Network port usage management

Introduction of network port count to maintain and restrict placement based on port availability.

Power port usage management

Introduction of power port count to maintain and restrict placement based on availability of the required
power ports.

5.0 September 3phase Load Balancing

2008 Track single and 3phase applications, ensuring all 3 phases on the power system carries a balanced load.

Power Dependency Path

Map the power path and physical system relationships and dependencies.

Generic UPS Support

Allows for modeling data from any UPS vendor, providing support for brownfield environments.

Keyword Tagging
Highlight location constraints through keyword tagging of data center equipment.

Capacity Reporting
Shows planned and actual power data in one view, enabling detailed planning of future power needs.

Offline Mobile Change Manager

Offline access to work orders and asset management data.

Rack Audit
Perform instant inventory management through view of rack content and history.

User interface Localization

User interface localized in 10 languages (English, Japanese, German, Russian, Simplified Chinese, Korean,
French, Spanish, Italian, Portuguese).

4.2 June 2007 First public release

Various bug fixes based on close cooperation and testing by select strategic customers. Platform maturity
enhancements.

Live monitored data

All measured data points from InfraStruXure Central from APC devices related to power (UPS, PDU, rack
PDU, InRow CRACs, etc) are seamlessly available in the floor editor view.

4.1 September Initial version (narrow scope release to select customers only)
2006 First version of APC's DCIM solution consisting of two separate but integrated modules: Capacity Manager
(capacity management scope) and Change Manager (IT change request workflow scope).

Built on InfraStruXure Central platform

Binaries included on InfraStruXure Central platform, unlocked by specific license key(s).

Built on InfraStruXure Designer code base

Significant overlap with APC's internal, best practice design tool, used daily by thousands of APC and partner
engineers.

Page 49
StruxureWare Data Center Operation
The StruxureWare Data Center Operation base edition includes these elements:

Server
Desktop client
Web client

The base colo edition with additional features relevant for colocation companies includes these corresponding elements:

Server
Desktop client, colo edition
Web client, colo edition / Tenant Portal

DCO Server

Installing DCO server

DCO Desktop Client

Installing DCO desktop client

DCO Web Client

About DCO web client

Page 50
StruxureWare Data Center Operation for Colo

Desktop Client
StruxureWare Data Center Operation is available as an enterprise or a colocation base edition. This application is for the colocation
provider to help manage all aspects of the colocation facility. The application provides the owner of the colocation facility with real-time
status of current data center capacities in terms of data center power, cooling and space, and the ability to drill down further and identify
any constraints for expansion.

Features of the colocation edition include:

Integrated tenant billing

Reporting capabilities

Watch this video tutorial to learn how to model power in a colocation data center.
Web Client / Tenant Portal
As colocation provider with a StruxureWare Data Center Operation for Colo license, you have access to the DCO web client with
additional colo functionality, also referred to as the Tenant Portal.

Find more information about using the:

Web client
Custom colo features

See also

Page 51
StruxureWare Data Center Operation for Colo Desktop Client
The same functionality is available as in the enterprise base edition of the StruxureWare Data Center Operation Desktop Client. In
addition, the colo edition includes a feature set customized for colocation providers.

Tenant Billing

The open system integrates tenant billing information into the application for mapping tenant assets, providing detailed power draw, total
energy footprint and access to an instant impact analysis at the tenant level.

Assigning rooms, cages, or racks to customers

Prerequisite: Before you can assign a part of the infrastructure to customers, these customers must already exist in the system through
integration with a CRM application. For technical information about CRM integration, see Customer Web Service in the DCIM Developer
Documentation.

1. 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 Customer properties.
a. Search or choose a customer from the drop-down menu.
You cannot add new customers in the Properties dialog box as customer data is obtained through integration with a
CRM application.
b. In Contracted power specify the amount of power sold to the customer, or choose Reserved for a potential
customer to reserve equipment or space for a customer (you can add contracted power for potential customers as
well).

When a customer has been assigned to equipment, the equipment will change color in the floor layout Colo overlay to indicate if it is
reserved or closed. See more here.

Reporting Capabilities

Space report
Instant overview of current space capacities, identifying the sellable, occupied and reserved space, as well as space identified
as used internally.

Power report
Outlines the total capacity vs. the sold capacity and measured load per site for a complete overview of current power capacities.

Power receptacle report

Highlights the current status of plugs and sockets for one or more PDUs or tenants, including an indication of oversubscription.

Tenant inventory report

Shows all equipment associated with one tenant, for an instant tenant inventory.

More information on working with reports here.

Page 52
Cage Management
With cage space management the data center operator can import CAD drawings, apply grid-based naming for floor-mount equipment
and utilize cage drawing tools and cage power modeling.

Converting a closed shape into a cage

Any closed polyline shape in the CAD drawing can be converted into a cage. In the co-lo overlay, use the Detect walls tool to
select the shape and then double-click it to turn it into a cage. The cage is assigned a named based on its floor coordinates and the area
of the cage is automatically calculated.

Watch this video tutorial to learn how to manage a multi-tenant data center.

Drawing, splitting and deleting a cage

With the draw wall tool you can create walls and split cages. Press and hold Shift to draw consecutive wall segments.

Watch this video tutorial to learn how to work with cages in a multi-tenant data center.

Splitting cages with the Draw wall tool

Split a cage into two parts without deleting existing cage settings. The power connections are preserved when splitting a cage, and you
can move the receptacles between the cages in the split cage dialog box.

1. Draw the walls in the existing cage using the Draw wall tool.
2. In the Split cage dialog box choose which cage will inherit all settings and history of the original cage. The history will appear in
the audit trail for that cage.
3. Configure the properties and power connections of the cages.

Split cage dialog box

Page 53
Merging cages

If you have used the Draw Wall Tool to split a cage, you can delete the wall and merge the cages.

Delete the wall by right-clicking the wall and selecting Delete. In the Merge Cages dialog box you can merge cages or delete cages. If
you select Delete cages, all the settings and history of the cages will be deleted. If you choose to merge the cages, you must choose
which of the cages that should preserve the history and settings, and which of the cages will be deleted. Power connections for both
cages will be preserved.

Page 54
Room Colo overlay
The selected overlay defines what information is shown on top of the layout. You can switch to see the room layout in another overlay by
selecting another overlay tab at the bottom of the room layout pane. In Window > Show Overlays, you can define which overlay tabs to
enable.

The Colo overlay of the data center shows you information on space and rack count. The color highlights will give you an insight to
whether a rack or a floor space is open, reserved, closed or for internal use.

Racks:

Open: the rack is empty

Reserved: the rack is reserved for a customer, but the customer is not using it yet. To reserve a rack go to the Planning tab, right-click
the rack, select Customer and Reserved for potential customer

Closed: a customer is using the rack

Internal: the rack is booked for internal use. In the Planning tab, right-click the rack and select Properties > Customer. The customer
is an internal user.

Floor Space:

Open: the available amount of your sellable space

Reserved: the reserved amount of your sellable space

Closed: the used amount of your sellable space

Internal: the amount of your sellable space that is for internal use

Page 55
Room Area: the area of the room

Sellable Space: the sum of your open, reserved and closed space. Your internal space is not sellable and therefore not a part of the
calculation.

Space Efficiency: the ratio between your room area and your sellable space.

Page 56
StruxureWare Data Center Operation: Tenant Portal
The Tenant Portal is a StruxureWare Data Center Operation for Colo web application in which colocators can share customer specific
DCIM information with their customers, the tenants.

As colocator, you can configure the application to share just what is relevant to each of your customers. Nothing more, nothing less.

You can also keep the high-level overview of your data center and use the web client for online lightweight access to some of the
features in the DCO model without having to launch the desktop client.

As tenant, you will be granted access to the part of the colocator's data center infrastructure relevant to you. You'll be able to see your
inventory and, depending on your configuration, additional features such as edit your inventory, monitor space, power, and cooling
thresholds.

Tenant Portal Guide for Colo

A guide is available for colos here.

Tenant Portal Guide for Tenants

A guide is available for tenants here.

Page 57
Tenant Portal Guide for Colo
Use the Tenant Portal to share just what is relevant to each of your customers. Nothing more, nothing less.

As colocation provider with administration rights, you have access to more features and menu items than your customers. This adds to
the inventory, billing, and capacity management functionality in the desktop client, allowing you to easily set up the Tenant Portal for your
customers, and configure your branding towards your customers.

To onboard customers on the Tenant Portal first complete the initial configuration in the DCO desktop client to provide partial inventory
access rights, then configure customer administration in the Tenant Portal.

You can also keep the high-level overview of your data center for internal use, using the online lightweight access of the web client to
some of the features in the DCO model without having to launch the desktop client. See the web client user assistance for general
information about working with the web client inventory, dashboards, and administration options other than colo specific options, such as
managing licenses, users, and your profile, including language settings.

Tenant Portal customer administration

Web client base features

Working with the inventory

Editing rack inventory
Searching the inventory
Dashboards
Using the Energy Efficiency Dashboard
Using the PUE DCiE Dashboard
Changing the language
Managing your user account
Customizing web branding
Managing licenses
Managing DCO users and user rights
About users
Granting access to legacy SOAP web service API
Configuring authentication servers used for managing remote users
Setup an AD (Active Directory) Server
Working with SSL certificates

Colo specific features

Setting up a Tenant Portal for your customers

Onboarding a customer
Customizing branding towards your tenants

Customer administration

Managing customers and customer users

Page 58
Onboarding a customer

You configure customer inventory permissions and activate a portal for customers to provide users at the customer's site with access to
the Tenant Portal.

Customer properties in the desktop client combined with customer administration in the Tenant Portal (available in Administration>Cus
tomers) allow you to control customer user rights and the level of information you wish to share with your customers according to your
mutual agreement.

Configuring tenant inventory permissions

In the DCO desktop client customer properties, you configure permissions for your customers to their partial inventory (rooms, cages, or
racks).

Note

The web interface doesn't support granular customer rights down to server level. You can set up and use permissions at server
level in the desktop client but you will not be able to use it in the Tenant Portal.

1. Right-click any room, cage, or rack in a Navigation, or Layout pane and select Properties>Customer to edit the customer
properties.
2. Search or select a customer from the drop-down menu.
You cannot add new customers in the Properties dialog box as customer data is populated through integration with a CRM
system. For technical information about CRM integration, see Customer Web Service in the DCIM Developer Documentation.
3. In Contracted power specify the power sold to the customer.
4. Use Reserved for a potential customer if you want to reserve equipment or space for a customer.
You can add contracted power as well.
5. When a customer has been added and you saved the changes, the selected room, cage, or rack will change color in the Floor
Layout to indicate if it has been reserved or closed (in use). See more here.

Activating the Tenant Portal for a customer account

You activate the portal for a tenant/customer in Administration>Customers.

1. Click Activate customer.

2. Select the customer that you want to be able to access the portal.
Each customer account has contact information. This is for your primary contact person at the customer's site. The data is
read-only and typically automatically generated from your CRM system through the StruxureWare Data Center Operation deskt
op client. If the CRM data gets updated, the contact person will automatically change.
3. Set the information level, that is if the customer will be able to see power data (estimated and measured peak loads) and device
data, such as temperature and humidity sensor data.
4. Create the required amount of users for this customer and set the role to grant admin, edit, or view access.

View rights allow the user to see the partial inventory, including power and temperature data.
Edit rights allow the user to do the same as view rights. In addition, he can move, add, and delete equipment in the
partial inventory.
Administrator rights allow the user to do the same as edit rights. In addition, he can manage this customer's user
accounts, licenses, and authentication server configuration.

5. Confirm settings and review the email notification that will enable the users to log on with the specified credentials and start
using the portal.
Adjust the text as needed, and insert the customer's Tenant Portal URL.

There is an indicator next to every customer account, illustrating if the portal has been activated for this account. You can deactivate the
portal for a customer account at any time.

Page 59
Managing customers and customer users

Use customer administration (available in Administration>Customers) to control customer user rights and the level of information you
wish to share with your customers according to your mutual agreement.

Customer and user concepts

When referring to a user in the web client, we're normally referring to a DCO user. In the Tenant Portal for colocation providers however,
on some occasions when referring to a user, we may be referring to a user at a customer's site. This will be clearly differentiated in the
text.

Users ... are the DCO users in desktop/web client. Users are created in the system by system admin/user with permissions to
edit user rights in Administration>Users. User management settings are described here.

Customers ... are a colocation provider's customers (tenants) and these are automatically listed through integration to a CRM
system (configuration in DCO desktop client).

Customer's ... are the users at a customer's site. The settings available for this type of users are described here.
users

Customer administration

Use the customer administration (available in Administration>Customers ) to control customer user rights and the level of information
you wish to share with your customers according to your mutual agreement.

When you initially set up the Tenant Portal for a customer, as part of the onboarding process, you enter customer information, create
customer users, set information level and permissions, and activate the customer. The first time you open customer administration, there
are no active customers. Click ACTIVATE CUSTOMER to get started.

Contact

Each customer account has contact information. This is for your primary contact person at the customer's site. The data is read-only and
typically automatically generated from your CRM system through the StruxureWare Data Center Operation desktop client. If the CRM
data gets updated, the contact person will automatically change.

Permissions

You may have agreed with some customers to see estimated power values, and with others to see measured peak loads. You can also
toggle access to device data here, such as temperature and humidity sensor data.

Customer user level permissions

There may be several users at a customer's site with individual needs for viewing or editing in the Tenant Portal. The user roles settings
allows you to add customer users and define permissions.

View rights allow the user to see the partial inventory, including power and temperature data.
Edit rights allow the user to do the same as view rights. In addition, he can move, add, and delete equipment in the partial
inventory.
Administrator rights allow the user to do the same as edit rights. In addition, he can manage this customer's user accounts,
licenses, and authentication server configuration.

Active or inactive portal for customer

There is an indicator next to every customer account, illustrating if the portal has been activated for this account. You can deactivate the
portal for a customer account at any time.

Page 60
Customizing branding towards your tenants

You may want to change some default settings of the DCO web client, e.g. if you want to brand your site with your own logo, or color.

These settings are available in the branding folder on your DCO server and can be changed through the server management interface
(Webmin).

Replacing login background image, logo, and company logo

Changing website color theme

Changing help link

Configuring Tenant Portal link

Replacing login background image, icon, company name and logo

Replacing the icon will change the icon you see on login as well as the small icon in the top left corner of the web client.

Regardless of your image size, it will be automatically scaled to fit into the position of the default image. However, it's recommended to
use a photo in a square shape for the logo.png file.

1. Rename your custom file(s)

a. background image --> bg_login.jpg.
b. logo --> logo.png
c. company logo --> company_logo.png
2. Open the server management web interface (Webmin) by typing the address of your DCO server in a web browser folllowed by
:10000, https://<server IP address>:10000 .
3. Log on to Webmin using the user credentials created during the server installation.
4. In the left menu, select System>Upload and Download.
5. On the Upload to server tab:
a. Click Choose Files in Files to upload and navigate to your saved bg_login.jpg file. Same procedure for logo.png file
and company_logo.png file.
b. In File or directory to upload to navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/brandi
ng.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
c. In Owned by user and Owned by group, select dcojboss.
d. Click Upload.
6. Close and reopen your web browser and type the server address to access the login screen with your new custom images.

Changing website color theme

The color theme determines the color of borders in the web client (default green), e.g. borders of dialog boxes, borders in license icons,
borders in room icons in the inventory, etc.

1. Open and log in to Webmin as described above and navigate to System>Upload and Download in the left menu.
2. On the Download from server tab, navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/branding.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
and download the branding.css file.
3. Open the branding.css file, make your changes to the color codes, and save the file.
Tip: You can find an introduction to HEX color codes here: http://www.w3schools.com/cssref/css_colors.asp.
4. Reopen the Webmin interface and navigate to System>Upload and Download.
5. On the Upload to server tab:
a. Click Choose Files in Files to upload and navigate to your saved branding.css file.
b.

Page 61
5.

b. In File or directory to upload to navigate to the branding folder on your server:

8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/brandi
ng.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
c. In Owned by user and Owned by group, select dcojboss.
d. Click Upload.
e. Close and reopen your web browser and type the server address to log in to the web client with your custom color
theme.

Page 62
Changing help link

The default help link goes to our support and help site. To redirect to your custom help site, change the settings in the branding.json file.

1. Open and log in to Webmin as described above and navigate to System>Upload and Download in the left menu.
2. On the Download from server tab, navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/branding.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
and download the branding.json file.
3. Open the branding.json file, make your changes to the link, and save the file.
{
"subTitle": "StruxureWare",
"title": "Data Center Operation",
"helpUrl": " http://sxwhelpcenter.ecostruxureit.com ",
"tenantPortalUrl": ""
}
4. Reopen the Webmin interface and navigate to System>Upload and Download.
5. On the Upload to server tab:
a. Click Choose Files in Files to upload and navigate to your saved branding.json file.
b. In File or directory to upload to navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/brandi
ng.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
c. In Owned by user and Owned by group, select dcojboss.
d. Click Upload.
e. Close and reopen your web browser and type the server address to log in to the web client with your custom help link.

Page 63
Configuring Tentant Portal link

To redirect your tenants to access the Tenant Portal from an external URL, change the setting in the branding.json file. The URL you
specify here will be shown in the onboarding email sent to your tenants, welcoming them and instructing them how to access the Tenant
Portal.

Note

The DMZ setup protecting DCO against direct Internet access is entirely your own responsibility! See recommended setup in
the Web proxy server setup guide.

1. Open and log in to Webmin as described above and navigate to System>Upload and Download in the left menu.
2. On the Download from server tab, navigate to the branding folder on your server: /opt/jboss-as/standalone/deployme
nts/webclient.war/web/client/css/branding and download the branding.json file.
3. Open the branding.json file, make your changes to the link, and save the file.
{
"subTitle": "StruxureWare",
"title": "Data Center Operation",
"helpUrl": "http://sxwhelpcenter.ecostruxureit.com",
"tenantPortalUrl": ""
}
4. Reopen the Webmin interface and navigate to System>Upload and Download.
5. On the Upload to server tab:
a. Click Choose Files in Files to upload and navigate to your saved branding.json file.
b. In File or directory to upload to navigate to the branding folder on your server: /opt/jboss-as/standalone/dep
loyments/webclient.war/web/client/css/branding.
c. In Owned by user and Owned by group, select dcojboss.
d. Click Upload.
e. Close and reopen your web browser and type your new URL to log in to the Tenant Portal.

Page 64
Page 65
Tenant Portal Guide for Tenants
The Tenant Portal is made available to you by your colocation provider. As a tenant, you have access to the part of the colocation
provider's data center infrastructure relevant to you. You'll be able to see your inventory and, depending on your configuration, additional
features such as edit your inventory, monitor space, power, and cooling thresholds.

Rack level inventory management and audit trail

You can edit and track any changes to your rack inventory (add, move, edit, delete e.g. servers and rack PDUs) in the audit trail.

KPI insights

You can gain insight into power values (estimated and measured peak loads), environmental values (temperature and humidity sensors),
physical values (available U-space).

Power and space properties are shown on top of equipment in the floor layout. In addition, property tiles are shown to the right of the
layout for the selected room, cage, rack, or piece of equipment, e.g. power insight (estimated/measured power graphs).

You can also access KPI dashboards from the top menu, such as power history graphs.

Tenant level user management

Your colocation provider configures and makes the Tenant Portal available to you with the data relevant to you, according to your mutual
agreement.

Depending on your size and setup, you may have the need for a user with administrator rights and additional users with less rights for
editing or viewing only.

Rack inventory management

Working with inventory in the Tenant Portal

Editing asset inventory in the Tenant Portal
Searching the inventory in the Tenant Portal

KPI insights

Tenant Portal dashboards

User account and language settings

Managing your Tenant Portal user account

Changing the Tenant Portal language

Page 66
Working with inventory in the Tenant Portal

The web client rack inventory allows you to see any part of the DCO data center infrastructure model you have been granted access to
and drill down through locations and rooms to the rack inventory. You may have been granted with rights to view or edit all or parts of the
rack inventory.

Infrastructure overview and drill down

Locations and rooms from the DCO desktop client are represented in the web client in a non-hierarchical structure, making it easy to
click (or tap, if on a tablet) your way through locations, rooms, cages, and racks to a specific server or other asset in a rack.

Room

The room layout provides an overview of the floor-mounted equipment in the room. You can switch between overlays to reveal relevant
details on top of your equipment, such as power as graphs and numbers, and available u-space.

This information is also available as property tiles to the right of the layout. The information updates with relevant information for the
selected equipment.

The audit trail reflects any changes to the selected room or equipment.

Zoom and overview Use the zoom and full screen options to get a better view of specific details or an overview of the full solution.

Open rack Double-click a rack to open it in the rack layout.

Cage

If you are using StruxureWare Data Center Operation for Colo, you can see the cages you have been granted access to in the room
layout.

Glass Light blue

Mesh Dotted lines

Solid Black

Rack

The rack layout provides an overview of the rack-mounted equipment in the selected racks and enables you to edit your rack inventory.

Expand/collapse Use the expand/collapse icon to toggle viewing a rack from the front only or from the front and rear at the same
rack time, for example to see rear-mounted rack PDUs.

Open multiple Click the + icon to open multiple racks at the same time, allowing you to compare or drag equipment between
racks them.

If you open several racks, selecting zoom fit and full screen view will allow you to better see all racks at the
same time.

Show sensors in If you want to see temperature sensor data displayed directly in the rack layout at the sensor's position, select
rack to show sensors.

Editing rack inventory

In the web client changes to the rack inventory happens immediately. You don't have to click to save your changes as in the desktop
client. There's no undo either!

If you regret adding a piece of equipment, delete it; if you regret moving a piece of equipment, move it back, etc.

In case you accidentally make a quick move and didn't pay attention to where the equipment ended up, use the audit trail.

Adding equipment

1. In the rack layout open the rack in which you want to position the new equipment.
2. Click ADD EQUIPMENT to open the Equipment library.
3. Find the equipment to add by searching the library.
4. Drag it into the rack.

Moving equipment

1. In the rack layout open both the source and target racks.
a. Double-click to open the source rack.
b. Click COMPARE above this rack to open a list of other racks in the room.
c. Select the target rack from the list of racks.

2.

Page 67
 2. Drag the piece of equipment you want to move from the source rack into position in the target rack.

Deleting equipment

1. Select the equipment you want to delete.

2. Click Actions... in the information panel to the right of the layout, and select Delete.

Auditing rack inventory changes with the audit trail

The audit trail enables you to monitor rack inventory changes on-the-fly. It is available as a tile to the right of the rack layout. No need to
generate a report. It updates immediately as you add, move, or delete equipment, or disconnect cables, etc.

Page 68
Editing asset inventory in the Tenant Portal

Open the room with the racks you want to edit and double-click a rack to open it in the rack layout. To enable moving equipment
between racks, open multiple racks next to each other by clicking the plus icon and selecting more racks.

Warning

Any changes made to the rack inventory in the web client will update the model on the StruxureWare Data Center Operation se
rver and in the desktop client.

Adding, moving, or deleting rack equipment

To add equipment from the equipment library:

1. Click + ADD EQUIPMENT to open the equipment library.

2. In the text field, start typing some characters of the equipment you want to add, or the product category, for example 'blade
enclosures'.
As you type, all items that contain the typed characters are listed.
3. Select the item you want to add and drag it into position in the rack layout.
4. Close the equipment library (x) when you are done adding equipment to return to the full rack layout.

To move equipment in the layout:

Drag and drop equipment to other positions and/or racks.

To move equipment between racks, open the racks next to each other by clicking the plus icon, and selecting the racks, and
then drag equipment.

To delete equipment in the layout:

1. Select the piece of equipment to delete.

2. Scroll to the bottom of the equipment information panel to the right and select DELETE.

Configuring, editing, or deleting power connections

The application provides two ways of configuring power connections for rack equipment:

1. Configuring power connections from power consumers point of view,

2. Configuring power connections from rack PDU point of view, if rack PDU supports extended power information.

Configuring power connections from power consumers point of view

1. Select the power consumer for which you want to configure, edit, or delete power connections, such as a server.
2. In the equipment information panel to the right, click the Power tile and look for power consumer inlet with nothing connected to
it. Free inlet is marked with gray rectangle and label saying ”Not connected”.
3. Use dropdown to the right to see list of possible power sources.
4. Click on desired power source.
5. For power sources without power outlet information, select phase from list of available phase configurations,
6. For power sources with power outlet information, select available outlet.
7. To remove existing power connection, click on the selected phase or outlet again.

Configuring power connections from rack PDU point of view (extended power information only)

1. Select the power outlet for which you want to configure, edit, or delete power connection.
2. In the equipment information panel to the right, click the Power tile and check the Connected state.
3. Use dropdown to the right to see list of possible power consumers.
4. Click on desired power consumer to establish connection.
5. To remove existing power connection, click on the selected power consumer.

Editing equipment properties

1. Select the piece of equipment for which you want to edit properties, such as a server.
2. In the Properties tile in the equipment information panel to the right, edit any property.
Some properties may not be editable.

Any changes to the rack inventory will show in the Audit Trail.

Page 69
Searching the inventory in the Tenant Portal

Full inventory search

Use the search box in the welcome view (click Inventory in the top menu) to search for any piece of equipment in the entire inventory.
This allows you to quickly navigate to a specific piece of equipment. For example if you know the name of a server in a particular room,
you don't need to browse your way through locations, rooms, and racks.

If there's only one server matching your search, the system drills right down to it, opening the rack layout, highlighting the
server, and showing the property tiles on the right.
If more than one item fit your search, you can select from this limited list of items rather than browsing everything.

The DCO web client / Tenant Portal supports not simply exact string matches, but also character patterns using partial strings or
wildcards:

Full String
Begins-with partial string
When the search text entered is found in the beginning of the words (e.g. for equipment with name "Blade enclosure 23 1",
partial search works for searched entries: Bla, encl, 23, 1.
Wildcard characters (supported: *, #, %) (e.g for equipment with name "Blade enclosure 23 1", wildcard search works for *ade,
*clos*, *clos#, *closu%.
Minimum amount of characters to be entered for a search is 2 characters, except when there is a string or substring with a
single character in the name/property of the equipment. In this case single character search is possible.

Note

This is different from the behavior in the desktop client where search only returns results from the rooms you have opened on
your local machine.

Quickly search entire inventory

Quick search in open room

Use the quick search box appearing in the left corner when a room is open to search for any piece of floor-mounted equipment in this
room. This allows you to quickly navigate in a large room to locate a specific piece of floor-mounted equipment.

The quick search does not work in the same way as the full inventory search and does not support wildcards, etc. It is simply meant as a
quick way to find floor-mounted equipment in a large open room layout. Start typing the first characters of the equipment you want to
locate and the search immediately lists the matches in the room.

Search using:

Full string
Partial string
When the search text entered is found in a word, need not be at the beginning of the word (e.g. for equipment with name "Blade
enclosure 23 1", partial search works for searched entries: lad, ncl, losur.

Page 70
Quickly search open room (floor-mounted equipment)

Page 71
Tenant Portal dashboards

Use the web client's Dashboard menu to get an overview of your data center KPIs, such as the power history values (for the selection of
equipment to which you have access), or energy efficiency.
You will see one chart per top level item (room, cage, or rack).*

Tip

Bookmark the dashboard in your browser or keep it running on a separate screen.

Power History

Page 72
Changing the Tenant Portal language

Use the language option, available in the Profile>Language (your profile image in the upper right corner), to change the language
settings and view the web client in any of the supported languages.

The selected language will be used for texts on all pages, options, dialog boxes, status messages, etc. The language settings apply per
user and the default language is English.

Read about Desktop Client language settings here.

Tip

You can join our community of multilingual users of StruxureWare products and contribute translations for future versions of
the software.

See more here...

Page 73
Managing your Tenant Portal user account

Use your account settings, available in Profile>My Account (your profile icon in the upper right corner), to manage your user account
information.

Editing your account settings

Type your email address and full name.

This option is not available if you're a remote user since your account is handled by an authentication server. More...
The full name is the name displayed for your user account.

You cannot change your own username or delete your own user account.

Changing your password

Click CHANGE PASSWORD... and enter your old and new passwords.

If you forgot your password, your system administrator (a user with administrator rights) can reset your password for you and send you a
new password.

This option is not available if you're a remote user since your account is handled by an authentication server. More...

Setting system of measurement

In Preferred unit system, select to use metric or US customary settings.

This affects for example if the equipment dimensions are displayed in meters or feet.

Changing language settings

You can change your language settings (per user) in a separate menu item (Profile>Language). More...

Local user on the DCO server

Remote user on an authentication server

Page 74
StruxureWare Data Center Operation security
StruxureWare Data Center Operation is a client/server configuration. The server can be configured to run in cluster mode with multiple
nodes including data recovery node. The client runs on standard PC. You can find system requirements here.

Default user account for client

When setting up a server, a default apc user account is created for logging on to the client. The default credentials should be changed.
See Managing DCO users and user rights.

Firewall
It is recommended that the firewall is enabled. The firewall will reduce the number of open ports to the required minimum. It will also
protect internal services, such as the database, against external attacks. The firewall will allow all outgoing traffic and incoming traffic
according to these details.

Software vulnerability, scans and certifications

Read the Schneider Electric Vulnerability Management Policy here and see relevant security vulnerability information related to DCO
here.
3 different software scanning tools are run against StruxureWare Data Center Operation.

Antivirus
StruxureWare Data Center Operation does not include antivirus in the installation. From a functionality point of view, it is fine to install an
antivirus program on the server. We do have experience that antivirus will affect client performance and that performance loss
depending on configuration can potential lead to errors, e.g. in a cluster environment.

Logging
The DCO product has several log files capturing kernel, cron job, etc. based on standard Linux capabilities. Furthermore, DCO logs all
user account changes, logins and logouts to the Audit Trail log (available with change module license). The logs do not contain
confidential information but might include some of the data entered when building the model.

Server log files are stored on the server and are accessible to system administrators via the server configuration interface, Webmin
(StruxureWare DC Operation>Download Log Files).

Client log files are stored in the user folder, e.g. Windows 7: C:\Users\[Username]\.isxo\[Version]\Operations\application.log or Mac:
~/.isxo.

Asset Management Records: Asset additions, changes, moves, and removals are tracked and can be found in Audit Trail report in the
Reports section.

User Account Records: User additions, changes, and removals can be configured in User Rights and Authentication. These are tracked
and can be found in the Audit Trail report in the Analytics->Reports section.

Database architecture
Currently the database and server make up one unit and cannot be separated. The database and operating system are running on the
same partition on the server by default. The database technology is postgreSQL and cannot be exchanged with any other database type
or technology. The database is protected using RSA 2048 bits certificate password encryption.

Running in a cluster will also make the database run in a cluster. It is furthermore possible to have disaster recovery (DR) node in your
cluster environment. You can find more information here.

ETL is open to other database types and technologies. You can find more information about ETL here.

Page 75
Web proxy server setup guide
If you want to make the DCO web client or Tenant Portal available to your colleagues or customers directly from the Internet, ensure you
have a proxy configuration in the DMZ.

Note

The DMZ setup protecting DCO against direct Internet access is entirely your own responsibility!

However, here are some recommendations on what you should set up and how to do this.

This is not a complete newbie guide to setting up a proxy server. You should already have a working knowledge about scripting, web
proxy and DMZ configuration, or find it easy to acquire this knowledge.

About DMZ proxy and firewall port configuration

The DCO server should be on a protected network behind a firewall and not exposed directly on the Internet.

The only incoming traffic allowed through the firewall to the DCO server should be on ports 80/443.

Note

It is required that you set up a proxy server in the DMZ, only supporting incoming https on port 443 and proxying requests to
the DCO server on port 80/443 to the path: /web/ only.

You may want to use Nginx, Apache, AH Proxy, or some other proxy tools. Examples here will be referring to an Nginx setup.

You should only use secure https protocols, not e.g. SSL v2. For an Nginx setup, the default protocols: TLSv1, TLS1.1, TLSv1.2 are
supported.

Configuring a proxy for the DCO Tenant Portal

Proxy specific commands are explained in this section. For more information, refer to the complete Nginx configuration guide.

1. Ensure the Nginx server only handles https.

If an http request is made, it will be forwarded to https.

# Redirect browsers from http to https

server {
listen 80;
rewrite ^(.*) https://$host$1 permanent;
}

2. Set up the actual ssl connection pointing to the certificates.

# Set up the proxy to DCO

server {
listen 443 ssl;
server_name $NGINX_ADDRESS;
ssl_certificate $PATH_TO_CERTIFICATE_FILE;
ssl_certificate_key $PATH_TO_PRIVATE_KEY_FILE;
}

3.

Page 76
3. Proxy to the Tenant Portal

# First handle requests to the actual application path /web

location /web/ {
proxy_pass http://$DCO_ADDRESS;
}

4. Proxy root requests to the same location.

This is an additional option to proxy root requests to the same location, allowing the user to exclude /web in the URL when
accessing the Tenant Portal.
NOTE: The order matters! The location /web must be specified before location /.

# Handle root requests and forward to /web

location / {
proxy_pass http://$DCO_ADDRESS/web/;
}

Page 77
StruxureWare Data Center Operation Network Firewall Port Details

Network protocol and ports (incoming ports allowed by the firewall)

The firewall provides basic protection. If protection against sophisticated attacks is required, using a dedicated firewall product is
recommended.

Communication across a NAT firewall is not supported.

The following protocols and ports are used by StruxureWare Data Center Operation:

Protocol Transfer Port(s) Network Credentials/Access Encryption Comments

protocol

HTTP / TCP 80 / 443 Latency less than 200 ms, bandwidth minimum 1 Mbps. Bandwidth Manually created user Only using Communication
HTTPS usage between client and server heavily depends on size of solution, and password (default HTTPS between server
number of users and the type of operations done to the solution. apc/apc) and clients.
TLSv1.2 HTTP can be
Authentication server disabled or
integration support redirected to
HTTPS for
There is no option to improved
reset client user security.
password

Password policy is not

implemented in DCO
but can be enforced
using Authentication
servers. Password
can be ASCII format
and numbers

SNMP UDP 161 Basic system information and status of the Operation service will be SNMP community For added
exposed. More information can be found here string is default security from
The SNMP server can be disabled using the Server Configuration "public" v7.3.6,
interface disable
SNMPv1 and
configure
SNMPv3. Mo
re...

PostgreSQL TCP 5432 Depending on system integration the bandwidth requirements should As specified in Default MD5 ETL
be specified accordingly. external system ETL authentication communication
configuration between
Otherwise database and
depending on server
database
integration
created

Webmin TCP 10000 Very limited bandwidth requirements in normal operation. Manually created user Yes Server
Downloading/uploading backups will increase the bandwidth and password during configuration
requirements significantly. installation interface at
https://<server
User password reset i ip>:10000
nstructions

Ping ICMP Will reply to ping requests

External systems related protocols (outgoing, default (can be edited))

HTTP TCP 80 (443) Depending on system integration being used. As specified in Depending VMware,
(SSL/TLS) external system on system SCOM, Cisco
For StruxureWare Data Center Expert it is estimated that every alarm configuration integration UCS
will be around 2000 characters in size. Sensor data has approximately
the same size but is transferred more often (depending on the
integration configuration). The alarm and sensor data are bidirectional
communicated with the majority of data going to DCO. A catch-up job is
run on a hourly basis (configurable) this job will poll number of active
alarms * 2000 chars.

SMTP TCP 25 Email traffic from the DCO is limited and "user generated" via e.g. work As specified in Not communication
order execution, some system configuration etc. external system supported with e-mail
configuration server

DNS TCP/UDP 53 Very limited traffic and bandwidth requirement As specified in Not DNS server
external system supported communication
configuration

NFS TCP/UDP 111 Depending on system integration As specified in Not NFS mounted
external system supported by external drive
configuration protocol

NTP UDP 123 Very limited traffic and bandwidth requirement As specified in Depending NTP server
external system on system communication
configuration integration

SMB TCP/UDP 139 Depending on system integration As specified in Depending SMB

external system on system communication
configuration integration to NAS/SAN

CIFS TCP 445 Depending on system integration As specified in Depending CIFS

external system on system communication
configuration integration to NAS/SAN

Page 78
NFS TCP/UDP 2049 Depending on system integration As specified in Not NFS
external system supported by communication
configuration protocol to NAS/SAN

Disaster recovery node and cluster related protocols

SSH TCP 22 Very limited bandwidth requirements Handled by DCO Yes Internal cluster
server communication

HTTPS TCP 443 Very limited bandwidth requirements Handled by DCO Yes Internal cluster
server communication

PostgreSQL TCP 5432 Based on some data usage testing we found that the minimum Handled by DCO Yes Internal cluster
requirement for running a DR node on a 200 rack solution is 10 Mbit/s. server communication
This of course varies by usage, but unless the user performs multiple
changes to the entire solution in short succession, the DR node will
stay in sync within a few minutes on a 10 Mbit/s connection even with
larger changes (e.g. adding 50 racks). For most common tasks, the DR
will be sync'd within seconds. DCO also has a large buffer (8 GB), so
the DR node will be able to catch up even if there are many changes at
once, it will simply be a few saves behind the main node (however, still
in a consistent state). Nodes (except disaster recovery) must be on
same site in order to ensure network latency, failure rate, etc. is low
enough for cluster data traffic to get synchronized as needed and
thereby avoiding a "split brain" situation which is not supported.

See also

StruxureWare Data Center Operation security

StruxureWare Data Center Operation - System Requirements

StruxureWare Data Center Operation Software Vulnerability Scans

Page 79
StruxureWare Data Center Operation Software Vulnerability Fixes
This list shows fixes based on results from 3 different scanning tools Retina, Nessus and Acunetix run against StruxureWare Data
Center Operation as well as other relevant security vulnerability information related to the product. Some of these scans might also be
part of official certifications like e.g. DOD RMF IT (Former DIACAP) or FIPS140.

You can see relevant vulnerability information for previous versions of DCO here and read the Schneider Electric Vulnerability
Management Policy here.

Vulnerability Answer Affects Fixed Comments Scanning

DCO in tools
DCO

ZipSlip (CVE-2 Data Center Operation allows for the upload of a zip file from its user interface All 8.2.12
018-7806) to the server. A carefully crafted, malicious file could be mistakenly uploaded versions
by an authenticated user via this feature which could contain path traversal
file names. As such, it could allow for the arbitrary upload of files contained
with the zip onto the server file system outside of the intended directory. This
is leveraging the more commonly known ZipSlip vulnerability within Java
code.

CVSS score: 6.6. CVSS vector: AV:A/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

Meltdown (CVE Affects all versions of Linux (Centos, Red Hat, and Debian). Customers are All 8.2.2 Nessus
-2017-5754) advised to upgrade to the latest version of DCO. Red Hat users should versions
and Spectre (C upgrade packages. More information from Red Hat
VE-2017-5753,
CVE-2017-5715 An unprivileged attacker could use this flaw to:
)
Cross the syscall boundary and read privileged memory by conducting
targeted cache side-channel attacks.
Read privileged (kernel space) memory by conducting targeted cache
side-channel attacks.
Use guest/host boundaries and read privileged memory by conducting
targeted cache side-channel attacks.

Dirty COW (CV Affects all versions of Linux (Centos, Red Hat, and Debian). Customers are 7.5.0, 8.0.2 Red Hat Nessus
E-2016-5195) advised to upgrade to the latest version of DCO. Red Hat users should 8.0.0 CVE-2016-5195
upgrade packages and look for more information by following the Red Hat and
link. 8.0.1

An unprivileged local user could use this flaw to gain write access to
otherwise read-only memory mappings and increase their privileges on the
system.

BADLOCK (CV Affects both Debian and Red Hat versions of StruxureWare Data Center 7.5.0 8.0 Red Hat
E-2016-2118) Operation until and including version 7.5.0 when using Windows Networking CVE-2016-2118
Filesystem (smbfs), e.g., when using a Windows network share to store
backups.

Red Hat users should upgrade packages and look for more information by
following the Red Hat link.

We do not have a fix for Debian users so Debian users that use the Windows
Networking Filesystem (smbfs) functionality should consider their exposure to
this vulnerability and avoid using smbfs if necessary. The vulnerability will be
addressed in the next release of DCO.

DROWN (CVE- Affects both Debian and Red Hat versions of StruxureWare Data Center 7.4.5 7.5 Red Hat
2016-0800) Operation until and including version 7.4.5. Red Hat users should upgrade CVE-2016-0800
packages even though they are already running the fixed version of Struxure
Ware Data Center Operation.

The vulnerability is solved with the release of version 7.5 of StruxureWare

Data Center Operation .

glibc buffer Affects both Debian and Red Hat versions of StruxureWare Data Center 7.5 8.0 Upgrading glibc
overflow (CVE- Operation. on Debian
2015-7547)
Red Hat
CVE-2015-7547

Logjam (CVE-2 Affects disaster recovery nodes on Debian versions of StruxureWare Data 7.5 8.0 Updating
015-4000) Center Operation. Red Hat versions are not affected since they do not disaster
support disaster recovery nodes. recovery node
configuration

OpenSSL: Does not affects versions of StruxureWare Data Center Operation both Red Hat
alternative Debian and Red Hat. CVE-2015-1793
chains
certificate
forgery

Page 80
Leap Second The vulnerability affects versions of StruxureWare Data Center Operation until 7.4.5 7.5 Upgrading
2015 and including version 7.4.5. TZDATA 2015
to
The vulnerability is solved with the release of version 7.5 of StruxureWare accommodate
Data Center Operation . Leap second

NTP (CVE-201 The vulnerability affects versions of StruxureWare Data Center Operation until 7.4.5 7.5 Upgrading ntp
4-9295) and including version 7.4.5. on DCO Server
to Fix
The vulnerability is solved with the release of version 7.5 of StruxureWare CVE-2014-9295
Data Center Operation . Vulnerability

Ghost (CVE-20 The vulnerability affects versions of StruxureWare Data Center Operation until 7.4.5 7.5 Upgrading libc
15-0235) and including version 7.4.5 . on DCO Server
to Fix GHOST
The vulnerability is solved with the release of version 7.5 of StruxureWare Vulnerability
Data Center Operation .

Heartbleed StruxureWare Data Center Operation is not affected by the

(OpenSSL) Heartbleed vulnerability. In v7.4, the openSSL component has been updated
to present the latest version fixing all known vulnerabilities.

Shellshock (CV Shellshock does not seem remotely exploitable for unprivileged users on Stru 7.4 7.4.5 Upgrading
E-2014-6271 / xureWare Data Center Operation. We do however recommend following the BASH on DCO
CVE-2014-7169 guide on patching the vulnerability in the 7.4. Server to Fix
) Shellshock
In the 7.4.5 release of StruxureWare Data Center Operation, bash is updated Vulnerability
to include the fix.

Note about CVE-2014-7169: The original guide only covered

CVE-2014-6271. The guide has been updated at 2014-09-29 05:00 UTC to
cover both issues.

Poodle The vulnerability is solved with the release of version 7.4.5 of StruxureWare 7.4 7.4.5
Data Center Operation.

Page 81
Changing SSL certificate on the server
The DCO server is installed with self-signed security certificate. When connecting to the server from a web browser, you may receive
warnings about the security certificate. It is recommended, after the installation of DCO is complete, to purchase and install a security
certificate issued by a trusted certificate authority.

For you to be able to change to your SSL certificate on the DCO server, it needs to be an Apache 2.x/PEM format certificate consisting
of two files (*.key, *.crt).

It is best practice to disable access to the web clients before starting to update any certificates to ensure no client is connected with a
false certificate.

In a cluster setup, certificates can only be uploaded to the master but are automatically synchronized to the slave.

If your setup includes a disaster recovery node and you need a certificate on it, upload certificates to the DR server in the same way as
for a standalone server.

Preparing a certificate for upload

Password

A password protected key is not supported. Strip the password from the key before uploading it.

Intermediate or certificate bundle

If your certificate chain requires an intermediate certificate, append it to the .cert file. When appending, ensure you include everything,
including the lines: "-----BEGIN CERTIFICATE-----" & "-----END CERTIFICATE-----" as there may be several lines for this
intermediate certificate.

No users in the system during upload

The Apache HTTPD server will be reloaded during this process, so ensure no users are using the system during the upload.

Uploading a certificate

1. Open the Webmin web interface by selecting Administration>Webmin in the Data Center Operation web client.
Alternatively, type the address of your Data Center Operation server in a Web browser followed by :10000, <https://>:1000
0.
2. Log into Webmin using the user credentials created during the installation and in the left menu, select StruxureWare DC
Operation.
3. In the submenu, select Certificates.
4. Follow the instructions on the page.
5. Verify everything is working correctly by launching a web client and checking there's a green pad lock icon in the address line.

Page 82
Resetting user password on the DCO server
These instructions apply to the OS user on the DCO server, i.e. the user used during the DCO server installation process, and not the D
CO user on the desktop and web clients.

To reset the user password on the DCO server:

1. Insert the DCO installation media (USB key, DVD, or out-of-band management (OOM) interface) and reboot the server and ensure the
DCO installation media is booted up.

2. In the installation boot menu select Troubleshooting and then select Rescue a CentOS system.

3. In rescue mode you are presented with 4 options. Type 1 for 1) Continue and press <return>.

4. When you see Rescue Mount, press <return> and type chroot /mnt/sysimage.
5. To change the password type passwd <username> where <username> is the name of the user created during setup.
6. Type the new password.
Username is not allowed to be part of the password.
7. To exit chroot type: exit.

8. Reboot the server by typing reboot.

9. Remember to remove the DCO installation media.

Resetting password on DCO server

Page 83
System requirements
These system specifications are recommendations for your DCO system configuration in general. The performance and operation of the
system depends largely on the nature of the configuration, such as:

Number and population of racks

Number and nature of integrations to external systems
Number of devices and number of data points stored on these
Power path configuration (one big, several small, across rooms, etc.)
Concurrent and total users of the system and nature of their work cycle
Cluster configuration (recommended to run on hardware, not virtual setup for better ready time)

If StruxureWare Data Center Operation is running on lower specification servers than recommended, users may experience long
response times or timeout issues. In addition, the server may not be able to process scheduled jobs in a timely manner. This can lead to
an infinite job queue, where the amount of queued work on the StruxureWare Data Center Operation server is ever increasing to the
point where one or more StruxureWare Data Center Operation cluster servers are no longer responsive.

Recommended server hardware for StruxureWare Data Center Operation

The StruxureWare Data Center Operation Suite requires a dedicated server, either hardware or a virtual environment. The operating
system is included in the StruxureWare Data Center Operation installation. The below requirements are referring to the latest version Str
uxureWare Data Center Operation.

Recommended StruxureWare Data Center Operation server configuration

Server requirement guidelines (minimum)

CPU: 4 cores minimum. We recommend 8 cores

Memory: 16 GB RAM (absolute minimum requirement)
100 GB storage, speed minimum 170 MB/s
Cluster network: 1 Gbps connection between nodes
Disaster recovery network: 10 Mbps with low latency <100 ms

If your'e installing DCO on an existing server, note that DCO claims almost all memory (JVM about 8 GB and Postgres about 6 GB
alone). Therefore, you may experience issues if you have other applications running on the server, such as surveillance and monitoring
agents.

Server requirement guidelines for 10,000 racks across 200 rooms with 30 concurrent users

8 CPU cores
32 GB RAM
1 Gbps network connection between cluster nodes
100 GB storage, speed minimum 170 MB/s

Server requirement guidelines for 20,000 racks across 400 rooms with 30 concurrent users

16 CPU cores
64 GB RAM
1 Gbps network connection between cluster nodes
100 GB storage, speed minimum 170 MB/s

RAID systems

Recommended: Hardware RAID controllers (we have tested hardware controllers in the following server series, DELL x20 series, IBM
M4 series, HP G8 series) Be aware there might be hardware RAID controllers that we have not tested in special configuration of the
server series mentioned.

Not supported:

Generally all software RAID controllers

HP RAID Controller B-Series

DELL RAID Controller S-Series

Security configuration

For information about security configuration, see here.

Page 84
StruxureWare Data Center Operation Server Communication
For information on server communication, see here.

Recommended StruxureWare Data Center Operation Client Configuration

Processor: 2 GHz Intel Core 2 Duo (or equivalent)
Hard disk: 500 MB free hard disk space for installation
Memory: 4 GB RAM
Display: Absolute minimum 1024x768 screen resolution with 16 million colors, 1280x1024 is recommended. For 3D view to
work, 3D hardware including working drivers are needed
Operating System:
Windows
Windows 7, Windows 8.1, Windows 10
OS X
OS X (latest version)
Linux distributions (see Linux desktop client compatibility guide)
CentOS x86_64 (latest version)
Ubuntu x86_64 (latest LTS version)
The latest version of the Java Runtime Environment is needed for the desktop client
The web client is available on a computer, tablet, or mobile device with an internet browser: Browser: Internet Explorer 11, latest
version of Microsoft Edge, Chrome, Safari, or Firefox
Bandwidth requirement guidelines web client/Tenant Portal:
First time loading: 5 MB (this will be cached)
Loading a small room: 20 KB
Loading a room with 150 racks: 90 KB
Loading large room (1000 racks): 1.7 MB

These are the absolute minimum recommendations for running StruxureWare Data Center Operation but for larger setups, better
specifications are recommended.

You must have local administration rights on the client computer during installation, first login, and license upgrade.

Page 85
Linux desktop client compatibility guide

Use GTK2 instead of GTK3

StruxureWare Data Center Operation does not work well with GTK3. Issues with GTK3 include Asset Provisioning in Planning Mode not
working, report generation in Analytics not working, and user interface flickering. You can force the application to use GTK2 by ensuring
that the SWT_GTK3 environment variable is set to 0. While it is possible to perform this change system-wide (depending on how you set
up your system), it is also possible to perform the change per application, by running the application as shown below.

user@laptop ~/Desktop/StruxureWare Data Center Operation-8.0.0 $ SWT_GTK3=0 ./StruxureWare\ Data\

Center\ Operation

See also

System requirements

Page 86
Initial installation and system setup
Installing StruxureWare Data Center Operation
Installing DCO on Red Hat Enterprise Linux 7
List of Dependent Packages for Red Hat Enterprise Linux Installation
Installing the DCO server using out-of-band management interface
Installing StruxureWare Data Center Operation in a virtual environment
Installing DCO in a location without public Internet access
Creating a bootable media with the DCO ISO
Installing StruxureWare Data Center Operation in a clustered environment
Setting up a clustered environment
Setting up the system
Configuring external system integration
Configuring StruxureWare Data Center Expert integration
Configuring VMware vCenter integration
Configuring Remedy integration
Configuring Cisco UCS Manager integration
Configuring StruxureWare Power Monitoring Expert integration
HP OneView integration
External system integration through ETL
DCO SNMP status codes
RF Code CenterScape Connector
ServiceNow Asset Management Connector
ServiceNow Change Management Integration
Configuring email settings
Working with multiple languages
Starting StruxureWare Data Center Operation Client in a Different Language
Changing the location of the StruxureWare Data Center Operation client temporary files
Configuring disaster recovery

Page 87
Installing StruxureWare Data Center Operation
First, install the Data Center Operation server from a prepared installation media: DVD, USB key, or out-of-band management (OOM)
interface. Then, after installing the server, install the clients.

You do not need to preinstall an OS, as the Data Center Operation installer image includes all needed installation material, including
CentOS.

Separate instructions are available for installing DCO in a clustered environment and recommendations for installing DCO in a virtual
environment.

Prerequisites

You have prepared a bootable installation media with the StruxureWare Data Center Operation Installer Image file.
Ensure the media has sufficient space (4GB) and is clean before copying the ISO to it.
Download the ISO from a location provided by the support team. To locate the telephone number for your region, visit C
ontact Us.

Read about creating the bootable installation media here.

When you have a bootable installation media with the DCO installer, you can install the Data Center Operation server to any computer
according to your licenses.

If you have a previous version of Data Center Operation, first, remember to back up your solution in a remote location to be able to
restore the backup after installing StruxureWare Data Center Operation. The installation will destroy all data on the server. You will
lose all data if you skip creating the backup. More...

Installing the StruxureWare Data Center Operation server

It is recommended that you follow the on-screen instructions and select the default options unless you have specific requirements.

1. Insert the StruxureWare Data Center Operation installation media.

2. Connect a keyboard and display.
3. Ensure the BIOS settings enable the server to boot from the installation media and the server is connected to the network during
the entire installation process.

Complete installation process (animated)

4. In the StruxureWare Data Center Operation boot menu, select Install Standalone to install a stand-alone StruxureWare Data
Center Operation server with CentOS customization options described in step 5.

The menu also includes a cluster installation option. Separate instructions are available for installing DCO in a clustered
environment. In addition, a few more options not relevant to the initial installation are available:

Boot from local drive To skip the menu and continue booting from the local system disk.
Troubleshooting To troubleshoot installation problems.

But let's proceed with the installation...

Page 88
Boot menu

5. Follow the installation wizard and set the CentOS language, date and time, and keyboard options for your StruxureWare Data
Center Operation server.

a) When the CentOS language settings are displayed, select the language to be used for the installation process as well as
the default language of the installed system.

b) When the date and time options are displayed, select your country or the location matching your time zone.

Page 89
c) For setups without network time synchronization needs, set Network Time to OFF, and select time zone on the map.

For setups with network time synchronization needs, set Network Time to ON. Next to Network Time ON, click the settings
icon to open NTP options, add an NTP server, verify it is working, and select use.

Wait for the time (in the bottom left) to update, matching your current time. If NTP settings doesn't work, you can set the
time manually on the server (especially important in cluster setups).

Page 90
 d) Review the keyboard settings.

Advanced non-mandatory system settings

Note
You do not need to set up partitions as default LVM partitioning, allowing for easy disk space upgrades, is included in the
installation.

Custom partitioning is not recommended since it has no benefit on performance and will make troubleshooting and support
more difficult.

Note

Page 91
For networks without DHCP, you can assign a static IP to the ethernet interface:

1. Click NETWORK & HOST NAME, then Configure...

2. Click IPv4 Settings, and in Method select Manual.
3. Click Add, type your static IP and click Save.

Page 92
6. Click Begin Installation.

7. Select USER CREATION to create the first OS user on the StruxureWare Data Center Operation server with administration

Page 93
rights.

This is a Linux user used for server configuration operations through command line, SSH and Webmin. You do not need to set the
root password as it has been disabled for many functions in StruxureWare Data Center Operation.

Note

Do not use common usernames, such as apc or admin, and ensure the user is an administrator.

This step is important as, unless you create this administrator user (other than the root user) during installation, you'll not be
able to access the server through SSH later.

For clarification, read more about users here.

8. Take a break while waiting for the installation to complete, for the server to reboot, and the StruxureWare Data Center
Operation software to initialize.

It will be several minutes.

9. Remove the installation media.

The Data Center Operation server is now installed and is ready for use.

10. Log in to the StruxureWare Data Center Operation web client as default user (credentials: apc/apc) and, as the very first thing,
immediately change the password.

StruxureWare Data Center Operation uses a different set of users than the Linux OS users (used for the StruxureWare Data
Center Operation server installation itself).

For security reasons, it is recommended that you create a new StruxureWare Data Center Operation administration user with a
complete set of user rights, including user administration rights, and then delete the default apc/apc user, or at the very least that
you change the password of the apc user.

You can proceed with server configuration and client installations as required.

For information on security related settings, see StruxureWare Data Center Operation security.

Page 94
Installing StruxureWare Data Center Operation clients

DCO web client is automatically available

You don't need to install the DCO web client as it is automatically available with the server installation. When the server installation has
been completed, simply open a web browser and launch to the DCO server IP address to log in and start using the web client.

However, If you want to make the DCO web client or Tenant Portal available to your colleagues or customers directly from the Internet, y
ou need to set up web client access. See more about setting up web client access here.

Installing DCO desktop client

Prerequisites: The StruxureWare Data Center Operation server installation has been completed.
1. On the computer on which to install the StruxureWare Data Center Operation client, open a web browser and launch to the IP
address or hostname of the DCO server <serverIPaddress> to log in to the web client and get access to the desktop client
download.
(The DCO web client is automatically available with the server installation.)
2. If you're not an English speaker, select your preferred language from the profile menu Language option (profile image in the
upper right corner).
3. In Administration>Licenses add your license keys to enable download according to your purchased licenses.
4. In the profile menu select Download Desktop Clients.
5. On the download page click to download the StruxureWare Data Center Operation software according to your license and follow
the instructions in the installation wizard.
6. Repeat the above steps on all client computers.

Page 95
Installing DCO on Red Hat Enterprise Linux 7
*Content of this page will be reviewed*

We usually don't offer support on RHEL installations as most of our customers that are using RHEL have they own ways of installing and
configuring RHEL.

StruxureWare Data Center Operation 8.0.1 or later versions can be installed on a Red Hat Enterprise Linux 7 server.

On this page:

Installation requirements
Changes to the system
Installing the StruxureWare Data Center Operation server on Red Hat Enterprise Linux
Non-mandatory creation of users and groups
Installing StruxureWare Data Center Operation clients

Installation requirements

Prerequisite: Before starting the installation procedure, make sure that the general System Requirements are fulfilled in addition to
these:

A server running RHEL 7.x with at least minimum install selected.

Access to RHEL packages either by using an active RHEL subscription or inserting a Red Hat Enterprise Linux Server x86_64
DVD
Disk space:
/data is used for indexes and ETL configuration. Minimum size 5 GB.
/data/backup is used for backups. Minimum size 50 GB. Backups should always be mounted on a remote network
share.
/opt/jboss-as is used for the application server. Minimum size 10 GB.
/var/lib/pgsql is used for the postgres database. Minimum size 30 GB.
/var/log is used for log files. Minimum size 5 GB.
Total amount of space recommended for an installation is at least 100 GB in addition to the operating system.
Optional: Due to a bug in the Red Hat linux kernel, it is recommended to upgrade to 3.10.0-327.22.2.el7 or later. Some
audit log messages may not be logged if you have a kernel version earlier than 3.10.0-327.22.2.el7.

Note

If special configuration has been done, ensure the sudoers file /etc/sudoers includes the following lines before installing or
upgrading:

## Allow root to run any commands anywhere

root ALL=(ALL) ALL
## Read drop-in files from /etc/sudoers.d (the # here does not mean a comment)
#includedir /etc/sudoers.d

If, for security reasons, you do not want to enable one or both of the above lines, contact Technical Support for a list of
changes needed for the installation to proceed. For optimum support, supply your sudoers configuration in your support
request.

Changes to the system

The following system changes are applied during installation of the StruxureWare Data Center Operation software.

DCO will install the listed packages* if not already installed.

*You can get a list of dependent packages for Red Hat Enterprise Linux installation through your local Schneider Electric
contact.
Firewalld rules are set to DCO default locked down settings.
The SNMPd configuration is replaced with a DCO configuration to provide SNMP status for the DCO services.
The NTP configuration is changed to use default RHEL NTP servers. This can be changed afterwards through the server
management interface (Webmin).
The PostgreSQL configuration is replaced and certificates for the database get generated during install.
The Keepalived configuration is replaced.
SELinux is enabled.
CTRL+ALT+DELETE reboot is disabled.

Page 96
 Root login and UseDNS in SSH is disabled.
TCP Keepalive settings are modified.
Kernel shared memory, huge pages and network memory settings are modified.
The sudo configuration was changed, adding sudo permissions to operations-platform and dcojboss user, removing requiretty
parameter.
logrotate has been configured to handle DCO and PostgreSQL logs.
Loading kernel module ip_vs and ip_vs_rr.
The Apache configuration is modified.
The Webmin configuration is modified, disabling unused modules and changing security configuration.
Enabling PostgreSQL start at boot.
Maximum number of files has been increased to 100000 for JBoss (dcojboss) and root users.
Sudoers rules have been added for the dcojboss user to allow creation of ETL databases.

Installing the StruxureWare Data Center Operation server on Red Hat Enterprise Linux
1. Download the installation file (StruxureWareDataCenterOperation-<version no>.iso ) from a location provided by the support
team. To locate the telephone number for your region, visit Contact Us.

Note: The below commands should be run with root credentials.

2. Upload the installation file to: /tmp/

3. Create ISO mount point /tmp/iso
4. Mount the installer by running the command: mount -o loop /tmp/StruxureWareDataCenterOperation-<version
no>.iso /tmp/iso
(where you replace <version no> with the 8.x.x version number)
5. Execute the install script: bash /tmp/iso/dco-install/install.sh
However, if installing a cluster node, execute the install script: bash /tmp/iso/dco-install/install.sh
--clusternode
6. Un-mount ISO: umount /tmp/iso/

Non-mandatory creation of users and groups

Click here for details...
During the installation process the setup script will automatically create these user accounts: dcojboss, dcoplat, postgres, and
apache.

If required, these accounts may be manually added by executing these commands with root credentials prior to installation:

Add dcojboss user and group

groupadd --system dcojboss

useradd --system -g dcojboss --shell /bin/nologin --home-dir /opt/jboss-as -c
"StruxureWare Data Center Operation Application Server" --create-home dcojboss

Add dcoplat user and group

groupadd --system dcoplat

useradd --system -g dcoplat --shell /bin/sh --home-dir /home/dcoplat -c
"StruxureWare Data Center Operation Platform User" --create-home dcoplat

Add postgres user

groupadd -g 26 -o -r postgres
useradd -M -n -g postgres -o -r -d /var/lib/pgsql -s /bin/bash -c "PostgreSQL
Server" -u 26 postgres

The postgres package performs the above commands. Changing UID/GID is currently untested.

Add apache user

groupadd -g 48 -r apache
useradd -c "Apache" -u 48 -g 48 -s /sbin/nologin -r -d /usr/share/httpd apache

Page 97
 The httpd package performs the above commands. Changing UID/GID is currently untested.

Installing StruxureWare Data Center Operation clients

Prerequisite: The server installation has been completed.

1. On the computer on which to install the StruxureWare Data Center Operation client, open a web browser and launch to the IP
address or hostname of the DCO server <serverIPaddress> to log in to the web client and get access to the desktop client
download.
(The DCO web client is automatically available with the server installation.)
2. If you're not an English speaker, select your preferred language from the profile menu Language option (profile image in the
upper right corner).
3. In Administration>Licenses add your license keys to enable download according to your purchased licenses.
4. In the profile menu select Download Desktop Clients.
5. On the download page click to download the StruxureWare Data Center Operation software according to your license and follow
the instructions in the installation wizard.
6. Repeat the above steps on all client computers.

Page 98
List of Dependent Packages for Red Hat Enterprise Linux Installation

Repositories:

rhel-7-server-dvd-rpms = Red Hat Enterprise Linux Server x86_64 DVD

thirdparty-swdco-local-rpms = Packages included in the installer

Package name Repository

apr-util rhel-7-server-dvd-rpms

apr rhel-7-server-dvd-rpms

at rhel-7-server-dvd-rpms

autogen-libopts rhel-7-server-dvd-rpms

bash-completion rhel-7-server-dvd-rpms

bc rhel-7-server-dvd-rpms

cairo rhel-7-server-dvd-rpms

cifs-utils rhel-7-server-dvd-rpms

cups-client rhel-7-server-dvd-rpms

cups-libs rhel-7-server-dvd-rpms

dejavu-fonts-common rhel-7-server-dvd-rpms

dejavu-sans-mono-fonts rhel-7-server-dvd-rpms

ed rhel-7-server-dvd-rpms

fontconfig rhel-7-server-dvd-rpms

fontpackages-filesystem rhel-7-server-dvd-rpms

gdbm-devel rhel-7-server-dvd-rpms

giflib rhel-7-server-dvd-rpms

glibc-devel rhel-7-server-dvd-rpms

glibc-headers rhel-7-server-dvd-rpms

graphite rhel-7-server-dvd-rpms

harfbuzz rhel-7-server-dvd-rpms

hdparm rhel-7-server-dvd-rpms

httpd-tools rhel-7-server-dvd-rpms

httpd rhel-7-server-dvd-rpms

java-180-openjdk-devel rhel-7-server-dvd-rpms

java-180-openjdk-headless rhel-7-server-dvd-rpms

java-180-openjdk rhel-7-server-dvd-rpms

javapackages-tools rhel-7-server-dvd-rpms

keepalived rhel-7-server-dvd-rpms

kernel-headers rhel-7-server-dvd-rpms

keyutils rhel-7-server-dvd-rpms

libdb-devel rhel-7-server-dvd-rpms

libfontenc rhel-7-server-dvd-rpms

libICE rhel-7-server-dvd-rpms

libjpeg-turbo rhel-7-server-dvd-rpms

Page 99
libldb rhel-7-server-dvd-rpms

libpng rhel-7-server-dvd-rpms

libSM rhel-7-server-dvd-rpms

libtalloc rhel-7-server-dvd-rpms

libtdb rhel-7-server-dvd-rpms

libtevent rhel-7-server-dvd-rpms

libthai rhel-7-server-dvd-rpms

libwbclient rhel-7-server-dvd-rpms

libX11-common rhel-7-server-dvd-rpms

libX11 rhel-7-server-dvd-rpms

libXau rhel-7-server-dvd-rpms

libxcb rhel-7-server-dvd-rpms

libXdamage rhel-7-server-dvd-rpms

libXext rhel-7-server-dvd-rpms

libXfixes rhel-7-server-dvd-rpms

libXfont rhel-7-server-dvd-rpms

libXft rhel-7-server-dvd-rpms

libXi rhel-7-server-dvd-rpms

libXrender rhel-7-server-dvd-rpms

libxshmfence rhel-7-server-dvd-rpms

libXtst rhel-7-server-dvd-rpms

libXxf86vm rhel-7-server-dvd-rpms

lksctp-tools rhel-7-server-dvd-rpms

lm_sensors-libs rhel-7-server-dvd-rpms

m4 rhel-7-server-dvd-rpms

mailcap rhel-7-server-dvd-rpms

mailx rhel-7-server-dvd-rpms

mesa-libEGL rhel-7-server-dvd-rpms

mesa-libgbm rhel-7-server-dvd-rpms

mesa-libglapi rhel-7-server-dvd-rpms

mesa-libGL rhel-7-server-dvd-rpms

mod_ssl rhel-7-server-dvd-rpms

nano rhel-7-server-dvd-rpms

net-snmp-agent-libs rhel-7-server-dvd-rpms

net-snmp-libs rhel-7-server-dvd-rpms

net-snmp rhel-7-server-dvd-rpms

net-tools rhel-7-server-dvd-rpms

ntpdate rhel-7-server-dvd-rpms

ntp rhel-7-server-dvd-rpms

pango rhel-7-server-dvd-rpms

patch rhel-7-server-dvd-rpms

Page 100
perl-Archive-Extract rhel-7-server-dvd-rpms

perl-Archive-Zip rhel-7-server-dvd-rpms

perl-Authen-PAM thirdparty-swdco-local-rpms

perl-autodie rhel-7-server-dvd-rpms

perl-Business-ISBN-Data rhel-7-server-dvd-rpms

perl-Business-ISBN rhel-7-server-dvd-rpms

perl-Carp rhel-7-server-dvd-rpms

perl-CGI rhel-7-server-dvd-rpms

perl-Compress-Raw-Bzip rhel-7-server-dvd-rpms

perl-Compress-Raw-Zlib rhel-7-server-dvd-rpms

perl-Config-General thirdparty-swdco-local-rpms

perl-constant rhel-7-server-dvd-rpms

perl-Crypt-OpenSSL-X509 thirdparty-swdco-local-rpms

perl-Crypt-SSLeay rhel-7-server-dvd-rpms

perl-Data-Dumper rhel-7-server-dvd-rpms

perl-DBD-Pg rhel-7-server-dvd-rpms

perl-DBI rhel-7-server-dvd-rpms

perl-devel rhel-7-server-dvd-rpms

perl-Digest-MD5 rhel-7-server-dvd-rpms

perl-Digest rhel-7-server-dvd-rpms

perl-Encode-Locale rhel-7-server-dvd-rpms

perl-Encode rhel-7-server-dvd-rpms

perl-Exporter rhel-7-server-dvd-rpms

perl-ExtUtils-Install rhel-7-server-dvd-rpms

perl-ExtUtils-MakeMaker rhel-7-server-dvd-rpms

perl-ExtUtils-Manifest rhel-7-server-dvd-rpms

perl-ExtUtils-ParseXS rhel-7-server-dvd-rpms

perl-FCGI rhel-7-server-dvd-rpms

perl-File-Listing rhel-7-server-dvd-rpms

perl-File-Path rhel-7-server-dvd-rpms

perl-File-Temp rhel-7-server-dvd-rpms

perl-Filter rhel-7-server-dvd-rpms

perl-Getopt-Long rhel-7-server-dvd-rpms

perl-HTML-Parser rhel-7-server-dvd-rpms

perl-HTML-Tagset rhel-7-server-dvd-rpms

perl-HTTP-Cookies rhel-7-server-dvd-rpms

perl-HTTP-Daemon rhel-7-server-dvd-rpms

perl-HTTP-Date rhel-7-server-dvd-rpms

perl-HTTP-Message rhel-7-server-dvd-rpms

perl-HTTP-Negotiate rhel-7-server-dvd-rpms

perl-HTTP-Tiny rhel-7-server-dvd-rpms

Page 101
perl-IO-Compress rhel-7-server-dvd-rpms

perl-IO-HTML rhel-7-server-dvd-rpms

perl-IO-Interface thirdparty-swdco-local-rpms

perl-IO-Socket-IP rhel-7-server-dvd-rpms

perl-IO-Socket-SSL rhel-7-server-dvd-rpms

perl-IO-Tty thirdparty-swdco-local-rpms

perl-IPC-Cmd rhel-7-server-dvd-rpms

perl-IPC-Run thirdparty-swdco-local-rpms

perl-libs rhel-7-server-dvd-rpms

perl-libwww-perl rhel-7-server-dvd-rpms

perl-Locale-Maketext rhel-7-server-dvd-rpms

perl-Locale-Maketext-Simple rhel-7-server-dvd-rpms

perl-LWP-MediaTypes rhel-7-server-dvd-rpms

perl-LWP-Protocol-https rhel-7-server-dvd-rpms

perl-macros rhel-7-server-dvd-rpms

perl-Math-Round thirdparty-swdco-local-rpms

perl-Module-CoreList rhel-7-server-dvd-rpms

perl-Module-Load-Conditional rhel-7-server-dvd-rpms

perl-Module-Load rhel-7-server-dvd-rpms

perl-Module-Metadata rhel-7-server-dvd-rpms

perl-Mozilla-CA rhel-7-server-dvd-rpms

perl-Net-Daemon rhel-7-server-dvd-rpms

perl-Net-HTTP rhel-7-server-dvd-rpms

perl-Net-LibIDN rhel-7-server-dvd-rpms

perl-Net-SSLeay rhel-7-server-dvd-rpms

perl-Params-Check rhel-7-server-dvd-rpms

perl-parent rhel-7-server-dvd-rpms

perl-PathTools rhel-7-server-dvd-rpms

perl-PlRPC rhel-7-server-dvd-rpms

perl-Pod-Escapes rhel-7-server-dvd-rpms

perl-podlators rhel-7-server-dvd-rpms

perl-Pod-Perldoc rhel-7-server-dvd-rpms

perl-Pod-Simple rhel-7-server-dvd-rpms

perl-Pod-Usage rhel-7-server-dvd-rpms

perl-RRD-Simple thirdparty-swdco-local-rpms

perl-Scalar-List-Utils rhel-7-server-dvd-rpms

perl-Socket rhel-7-server-dvd-rpms

perl-Storable rhel-7-server-dvd-rpms

perl-Switch thirdparty-swdco-local-rpms

perl-Sys-Syslog rhel-7-server-dvd-rpms

perl-Test-Harness rhel-7-server-dvd-rpms

Page 102
perl-Text-ParseWords rhel-7-server-dvd-rpms

perl-threads-shared rhel-7-server-dvd-rpms

perl-threads rhel-7-server-dvd-rpms

perl-TimeDate rhel-7-server-dvd-rpms

perl-Time-HiRes rhel-7-server-dvd-rpms

perl-Time-Local rhel-7-server-dvd-rpms

perl-URI rhel-7-server-dvd-rpms

perl-version rhel-7-server-dvd-rpms

perl-WWW-RobotRules rhel-7-server-dvd-rpms

perl rhel-7-server-dvd-rpms

perl-XML-NamespaceSupport rhel-7-server-dvd-rpms

perl-XML-Parser rhel-7-server-dvd-rpms

perl-XML-SAX-Base rhel-7-server-dvd-rpms

perl-XML-SAX rhel-7-server-dvd-rpms

perl-XML-Simple rhel-7-server-dvd-rpms

perl-XML-XPath rhel-7-server-dvd-rpms

pixman rhel-7-server-dvd-rpms

postgresql95-contrib thirdparty-swdco-local-rpms

postgresql95-libs thirdparty-swdco-local-rpms

postgresql95-server thirdparty-swdco-local-rpms

postgresql95 thirdparty-swdco-local-rpms

psmisc rhel-7-server-dvd-rpms

pyparsing rhel-7-server-dvd-rpms

pytalloc rhel-7-server-dvd-rpms

python-javapackages rhel-7-server-dvd-rpms

redhat-lsb-core rhel-7-server-dvd-rpms

redhat-lsb-submod-security rhel-7-server-dvd-rpms

rhel-7-server-dvd-rpms

rrdtool-perl thirdparty-swdco-local-rpms

rrdtool rhel-7-server-dvd-rpms

rsync rhel-7-server-dvd-rpms

samba-client-libs rhel-7-server-dvd-rpms

samba-common-libs rhel-7-server-dvd-rpms

samba-common rhel-7-server-dvd-rpms

samba-common-tools rhel-7-server-dvd-rpms

samba-libs rhel-7-server-dvd-rpms

smartmontools rhel-7-server-dvd-rpms

spax rhel-7-server-dvd-rpms

systemtap-sdt-devel rhel-7-server-dvd-rpms

time rhel-7-server-dvd-rpms

ttmkfdir rhel-7-server-dvd-rpms

Page 103
tzdata-java rhel-7-server-dvd-rpms

unzip rhel-7-server-dvd-rpms

wbm-sysstats thirdparty-swdco-local-rpms

xorg-x11-fonts-Type1 rhel-7-server-dvd-rpms

xorg-x11-font-utils rhel-7-server-dvd-rpms

Page 104
Installing the DCO server using out-of-band management interface

Servers are often equipped with an out-of-band (OOB) management card. Depending on vendor, the technology has different names
(HP ILO, DELL iDRAC, IBM RSA). OOB management allows users to access the server remotely typically through an Ethernet
connection. This also gives access to the local media which makes it possible to install e.g. StruxureWare Data Center Operation server
from a remote location.

It is recommended that you follow the on-screen instructions and select the default options unless you have specific requirements.

1. Access and log into the server OOB management card.

2. Launch the remote console.
The server should be connected to the network during the entire installation process (preferably high bandwidth through cable
due to full ISO being transferred to the server).
3. Mount the ISO as a virtual CD/DVD drive.
4. Ensure the BIOS settings enable the server to boot from the CD/DVD (or use the boot menu. Often F11 must be pressed during
server startup).
5. In the StruxureWare Data Center Operation boot menu, select Install Standalone and follow the generic DCO installation steps
.

Page 105
Installing StruxureWare Data Center Operation in a virtual environment
The same installation instructions and system requirements apply to a virtual environment as to a stand-alone server. If your system
doesn't meet the system requirements, you may experience issues with the installation, for example if you don't assign enough vRAM.

Setting up the virtual machine is not included in these instructions. However, here are some recommendations to your environment:

When installing StruxureWare Data Center Operation in a virtual environment, it is best to select CentOS operating system
(version 4, 5, 6, or 7, 64 bit) as the guest operating system.
This will make the configuration of virtual hardware, especially drivers, easier as you can simply select the default options
suggested by the system during configuration. These default options are based on knowledge about the driver installation on
these OS versions.
If the CentOS guest operating system type is not available in the virtual environment, configure the virtual hardware to be
compatible with:
CPU architecture: 64 bit
SCSI Controller: LSI Logic Parallel
Network adaptor type: VMXNET 3
If you deploy as a virtual server on VMware, VMware tools to optimize performance significantly will be automatically installed.

Tip

If you want to manually configure the IP address for your StruxureWare Data Center Operation installation on VMware, you
may need to disable and reenable the network settings.

1. In the CentOS installation wizard, select NETWORK & HOST NAME.

2. Click Configure, then enter and save your network settings.
You may need to disable and reenable the NIC you just configured for the changes to take effect before finishing your
configuration by clicking Done.

Page 106
Installing DCO in a location without public Internet access
You should be able to install DCO in a location without public Internet access in the same way as when an Internet connection is
available by following the default installation instructions, ensuring you have prepared the installation media in advance. You may
experience a short delay (about a minute) as the installer gets ready.

You can force offline installation by selecting Troubleshooting in the boot menu when booting the ISO file.

Page 107
Creating a bootable media with the DCO ISO
Creating a bootable USB key

DCO can be installed using a bootable USB key containing the DCO installation.

On a Windows machine

Warning
We have experienced issues when creating the media using Windows 10, resulting in the media check failing before the
installation is supposed to begin. If you need to use Windows when creating the installation media, we recommend that you
use Windows 7.

On Windows one way of creating a bootable USB key is using the free tool, Rufus.

1. Download and install Rufus here: https://rufus.akeo.ie/

2. Insert your USB key and run Rufus.

3. In Device, select your USB key.

4. Click the disk icon (see screenshot), and select the ISO file, then click Start.

5. Select Write in DD Image mode, then click OK to replace all data on your USB key with the DCO installer files.

Page 108
6. Wait for the process to complete and click Close.

7. Eject the USB key from Windows before removing the key (e.g. in Windows Explorer right-click the USB key, and select Eject ).

On a Mac machine
Run the dd command as described below.

1. Insert your USB key and open Disk Utility on your Mac.
2. Select your USB key, and find the USB device name (see screenshot).
3. Open Terminal and navigate to the folder with the DCO ISO file (e.g. cd Downloads).
4. Type sudo dd if=StruxureWareDataCenterOperation-<version number>.iso of=/dev/<usb device name
from step 2>
5. Wait for dd to finish and remove the USB key.

Page 109
On a Linux machine
Run the dd command as described below.

1. Insert your USB key and open your favorite console program.
2. Type dmesg and find the USB device name, such as sdb (see screenshot).
3. Type sudo dd if=StruxureWareDataCenterOperation-<version number>.iso of=/dev/<usb device name
from step 2>
Ensure you select the device as destination (e.g. /dev/sdb) corresponding to the USB key and not a partition (such as
/dev/sdb1).
4. Wait for dd to finish and remove the USB key.

Output of dmesg, showing USB device name

Page 110
Installing StruxureWare Data Center Operation in a clustered environment

The clustered environment is no longer available in DCO 8.2.7. More...

First, install the Data Center Operation server on both machines from an installation media: DVD, USB key, or out-of-band management
(OOM) interface. Then, after installing the server on both machines, install the clients.

Prerequisites

You have prepared a bootable installation media with the StruxureWare Data Center Operation Installer Image file.

Ensure the media has sufficient space (4GB) and is clean before copying the ISO to it.
Download the ISO from a location provided by the support team. To locate the telephone number for your region, visit Contact
Us.
Cluster servers complying with the minimum requirements.

For information about installing from a media such as a USB key, refer to the CentOs documentation, for example: https://wiki.centos.org
/HowTos/InstallFromUSBkey.
You should be able to find the relevant scripts, for example dd if=CentOS-6.5-x86_64-bin-DVD1.iso of=/dev/sdb.

When you have a bootable installation media with the DCO installer, you can install the Data Center Operation server to any computer
according to your licenses.

If you have a previous version of Data Center Operation, first, remember to back up your solution in a remote location to be able to
restore the backup after installing StruxureWare Data Center Operation. The installation will destroy all data on the node. You will
lose all data if you skip creating the backup. More...

Installing the StruxureWare Data Center Operation server on both cluster machines
It is recommended that you follow the on-screen instructions and select the default options unless you have specific requirements. On
both machines:

1. Insert the StruxureWare Data Center Operation installation media.

2. Connect a keyboard and display.
3. Ensure the BIOS settings enable the server to boot from the installation media and the server is connected to the network during
the entire installation process.

Complete installation process (animated), select Install Cluster instead of Standalone

4. On both machines:
In the StruxureWare Data Center Operation boot menu, select Install Cluster to install StruxureWare Data Center Operation serv
ers with CentOS customization options described in step 5.

The menu also includes a standalone installation option. Separate instructions are available for installing DCO as a standalone
server. In addition, a few more options not relevant to the initial installation are available:

Boot from local drive To skip the menu and continue booting from the local system disk.
Troubleshooting To troubleshoot installation problems.

But let's proceed with the installation...

Page 111
Boot menu

5. Follow the installation wizard and set the CentOS language, date and time, and keyboard options for your StruxureWare Data
Center Operation server.

a) When the CentOS language settings are displayed, select the language to be used for the installation process as well as
the default language of the installed system.

Page 112
b) When the date and time options are displayed, select your country or the location matching your time zone.

c) Next to Network Time ON, click the settings icon to open NTP options, add an NTP server, verify it is working, and select
use.

Page 113
Wait for the time (in the bottom left) to update, matching your current time. If NTP settings doesn't work, you can set the
time manually on the server (the machines in a DCO cluster must have the same time, which means the use of NTP is
highly recommended).

d) Review the keyboard settings.

Page 114
Advanced non-mandatory system settings

Note
You do not need to set up partitions as this has already been done by the installer.

Note

For networks without DHCP, you can assign a static IP to the ethernet interface:

1. Click NETWORK & HOST NAME, then Configure...

2. Click IPv4 Settings, and in Method select Manual.
3. Click Add, type your static IP and click Save.

Page 115
6. Click Begin Installation.

Page 116
7. Select USER CREATION to create the first OS user on the StruxureWare Data Center Operation server with administration
rights.

This is a Linux user used for SSH and server configuration (Webmin) operations. You do not need to set the root password as it
has been disabled for many functions in StruxureWare Data Center Operation.

Note

Do not use common usernames, such as apc or admin, and ensure the user is an administrator.

Page 117
 8. Take a break while waiting for the installation to complete, for the server to reboot, and the StruxureWare Data Center
Operation software to initialize.

It will be several minutes.

9. Remove the installation media and proceed to setting up the cluster nodes.

For information on security related settings, see StruxureWare Data Center Operation security.

Installing StruxureWare Data Center Operation clients

Prerequisites:

The server installation has been completed.

Ensure the computer on which to install the DCO desktop client cannot be accessed from the Internet. It should only be
available on your intranet. See recommended setup here.

Page 118
1. On the computer on which to install the StruxureWare Data Center Operation client, open a web browser and launch to the IP
address or hostname of the DCO server <serverIPaddress> to log in to the web client and get access to the desktop client
download.
(The DCO web client is automatically available with the server installation.)
2. If you're not an English speaker, select your preferred language from the profile menu Language option (profile image in the
upper right corner).
3. In Administration>Licenses add your license keys to enable download according to your purchased licenses.
4. In the profile menu select Download Desktop Clients.
5. On the download page click to download the StruxureWare Data Center Operation base software according to your license and
follow the instructions in the installation wizard.
6. Repeat the above steps on all client computers.

Page 119
Setting up a clustered environment

The clustered environment is no longer available in DCO 8.2.7. More...

About DCO cluster environments

To achieve high availability, you can run DCO in a clustered environment with two servers. This means your system will still be available
if one server crashes since it will continue to run on the other server.

To minimize the risk of data loss, you can add an offsite disaster recovery node.

Supported DCO setups:

1 standalone node
1 standalone node + 1 DR node (requires 1 high availability license)
2 cluster nodes (requires 1 high availability license)
2 cluster nodes + 1 DR node (requires 2 high availability licenses)

When running DCO in a clustered environment, additional nodes in the cluster or a disaster recovery node (besides the initial DCO serve
r) requires a high availability license as illustrated above.

Note

For security reasons:

Ensure your DCO cluster nodes are protected from direct Internet access by a proxy server.
See how to configure a proxy in the DMZ between the Internet and DCO in the Web proxy server setup guide.
Ensure your DCO desktop client cannot be accessed from the Internet either. It should only be available on your
intranet.

Running StruxureWare Data Center Operation in a clustered environment requires low network latency. Therefore, the clustered servers
should be installed in the same data center site and on the same network subnet. All cluster nodes must have a static IP address. If your
setup includes a disaster recovery node, you can have a firewall between the cluster and the disaster recovery node. See here for
details about network ports.

Your network must support VRRP (Virtual Router Redundancy Protocol). If your network does not meet this requirement, use a disaster
recovery setup rather than using a clustered environment.

Setting up a DCO cluster

You configure cluster setup in the Webmin server configuration interface. When configured, the cluster appears as a single

server to the user. During configuration, you add each node individually and specify that the server is a participant in the cluster.

Follow the below steps or watch this video tutorial.

Prerequisites

Ensure you have an IP to use as cluster Virtual IP (VIP) on the same subnet as your DCO servers. E.g.:

Server 1: xxx.xxx.xxx.121 (netmask: 255.255.255.0)

Server 2: xxx.xxx.xxx.122 (netmask: 255.255.255.0)
VIP: xxx.xxx.xxx .123

Configuring the first (primary) node

1. Install StruxureWare Data Center Operation with cluster configuration. See how.
2. Open the Webmin web interface by selecting Administration>Webmin in the DCO web client.
Alternatively, type the address of your DCO server in a Web browser using https on port 10000: https://<hostname>:1000
0 e.g.: https://192.168.1.34:10000.
3. Accept self-signed certificate (in Your connection is not private, click to Proceed to the IP (unsafe)).
4. Log into Webmin using the credentials created during the installation (Linux OS admin user) and navigate to StruxureWare DC
Operation.
5. In Setup, select Setup new cluster and enter an IP address that is reserved on your network to be used as virtual 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.
6. Configure system time synchronization (NTP).
Note: Correct time settings are crucial for cluster nodes. Ensure you configure this during installation. Recommendation:
Synchronize the time on all nodes with the same NTP server(s).

Page 120
 6.

The default NTP servers are fine if there is an Internet connection. If the Data Center Operation servers are on a closed
network, you should add a local NTP server. You must configure time synchronization separately on each node.
7. For improved security, specify a range of IP addresses allowed to administrate the cluster (Webmin allowed IP addresses).
For more information about security related settings, see StruxureWare Data Center Operation security.
The default values for the other options should be fine, unless you have a special network setup.
8. Click Setup and wait for the Application to start up before continuing to the next node. You can verify that the application has
started up on the node in Webmin StruxureWare DC Operation>Status (Application Status should be Running).

TIP: Configuring the node takes time.

Configuring the additional node

Prerequisite: You have configured the first (primary) node.

1. On the first node's configuration interface, specify that the additional node is allowed to join the cluster.
a. Open the Webmin server interface on the first node and navigate to StruxureWare DC Operation.
b. In Cluster Participants, enter the IP address of the new additional node and specify that it is allowed to join the cluster.
c. Accept the fingerprint of the additional node.
2. On the additional node's configuration interface, specify which cluster to join.
a. Switch to the Webmin interface on the new node by clicking the Webmin link or typing the IP address in the browser
address line and navigate to StruxureWare DC Operation>Cluster Participants.
b. Specify the virtual IP address of the cluster the additional node should join and verify the cluster's fingerprint.
The node will copy all the settings from the first node.
3. Click Setup and wait for the Application to start up. You can verify that the application has started up on the node in Webmin Str
uxureWare DC Operation>Status (Application Status should be Running).
4. Set the NTP address(es) on the second node: StruxureWare DC Operation>Setup. Type in the same NTP Servers as you
used on the first server. Click the Update button just below the NTP settings.

Verifying the cluster setup

1. Open the Webmin server interface on one of the nodes.

2. In StruxureWare DC Operation>Cluster Participants, verify that the cluster setup includes the correct nodes.
3. In StruxureWare DC Operation>Status, verify that the nodes are running (especially that Application State is Running).

The cluster environment has now been set up. Clients will connect to the virtual IP address of the cluster, not the nodes. You can
continue to install the licenses.
To configure a stand-alone disaster recovery node for extra security, see here.

Configuring NTP servers for both nodes after setting up the cluster

If you are using a non-default NTP server, setup the same NTP server or servers for both nodes after setting up the cluster to ensure
they both use the same NTP server or servers.

1. Open Webmin on one of the servers as described above.

2. Select StruxureWare DC Operation>Setup.
3. In NTP Settings set the IP of the NTP server you want to use, and click Update.
If using multiple NTP servers, enter NTP servers on separate lines.
4. Wait for the setup to finish and verify that Webmin on both node servers show the same NTP server or servers.

Page 121
Page 122
Setting up the system
DCO system settings are available to you if you have the appropriate user rights.

Some settings are available in the desktop client System Setup menu, others can be found in the web client Administration menu.

Settings in the desktop client

External System Configuration allows you to set up integration to other systems and manage the server configurations.

E-mail Settings allow you to set up email notification functionality.

Migrate from StruxureWare Operation allows you to move data from previous versions to the Operation platform.

Migrate from Emerson Aperture allows you to migrate data from Emerson Aperture. This option is not available by default but a
software service is available to support this migration. For further information, contact your local sales representative.

Work Order Cleanup allows you to delete old work orders from the system.

Desktop options

Settings in the web client

Customers settings (colo feature) allow you as colocation provider to manage Tenant Portal access for your customers.
See how to manage customers and customer users.

Users, User Groups, Authentication settings allow you to manage user rights and authentication servers.

See how to manage users and user groups.

See how to configure authentication servers.

Certificates settings.

See how to work with certificates.

Licenses settings allow you to manage your DCO licenses.

See more about licenses and how to manage them.

Web options

Page 123
Configuring external system integration
In System Setup > External Systems Configuration, you can set up integration with an external system. Select the type of server, e.g.
StruxureWare Data Center Expert or VMware vCenter server, and enter the server communication data.

The latest version of the integration software is supported (unless any issues with the latest versions are specified in the known issues
section relevant for your DCO version).

Once the communication between the servers has been established, the Data Center Operation 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.

You must ensure time synchronization has been configured for the servers.

Supported product versions:

VMware vSphere 6 and 6.5

Cisco UCS 3.0, 3.0.1, and 3.0.2
BMC Remedy 8.1 (Not the latest version)
SCOM 2012 R2 (Not the latest version)
Data Center Expert 7.3.1 & 7.4.x
ITO Server Version 7.5.2.0.119
Power Monitoring Expert: PMEDC 8.1
HP OneView 3.0
Cooling Optimize 6.6

Page 124
Configuring StruxureWare Data Center Expert integration

Integrating with a StruxureWare Data Center Expert server

Configure the server connection to allow StruxureWare Data Center Operation to communicate with the StruxureWare Data Center
Expert server and receive device data and alarms.

It is possible to integrate with multiple StruxureWare Data Center Expert servers.

1. Select System Setup>External System Configuration.

2. Click Add server, and select StruxureWare Data Center Expert as the server type.
3. Type the StruxureWare Data Center Expert server identification, such as name, IP, port (80 or 443), and credentials.
4. To configure the data collection settings (see screenshot), set:
Time period for calculation of peak and average power values (Calculate power data based on the last).
Interval for asking StruxureWare Data Center Expert for updated device data (temperatures are collected).
Interval for asking StruxureWare Data Center Expert for updated power data. (This value does not include all kW
measurements. Power data from rack PDUs is collected, whereas power data from cooling units is not.)
Full alarm synchronization every (how often StruxureWare Data Center Operation synchronizes alarms and alarm
statuses from StruxureWare Data Center Expert).
Retrieve sensors: If you select this, data from sensors such as temperature sensors are included. If you do not want to
see the temperature sensor data in StruxureWare Data Center Operation, do not select this.
Callback information to the Data Center Operation server. This is used to tell StruxureWare Data Center Expert which
ip/hostname to push alarms once they occur.
To Use Encryption a certification must be added to StruxureWare Data Center Expert. More...
Timeout settings for connection and response.
Stop trying to connect after: In case StruxureWare Data Center Operation cannot connect to the StruxureWa
re Data Center Expert server, the user will get a warning after the specified amount of time, and data collection
will resume when the connection has been restored.
Stop waiting for data after: StruxureWare Data Center Operation will drop the connection after the specified
time to avoid having a hanging connection.
5. When you have finished the steps in the wizard and the server has been added to the list of external systems, click Test to test
the connection.

External system configuration

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 StruxureWare Data Center Expert and Data Center Operation servers.

1. Access the Data Center Operation server management interface to access the certificate.
a. Launch the Webmin web interface by typing the address of the Data Center Operation server in a Web browser and
click Server Configuration.
b. Log on to Webmin using the user credentials created during the installation.
c. In the Webmin interface menu, select System>Upload and Download.
d. Open the Download from server tab.
e.

Page 125
 e. Browse to the certificate: /etc/isx-operations/ssl/certificate.crt and click Download.
f. Open the .crt file with a text editor, such as Notepad.
g. Select all and copy the contents (Ctrl+A/Ctrl+C).

Alternatively, in a web browser:

a. Type the server IP address and click the pad lock icon to the left to open View Site Information.
b. Click Certificate Information.
c. In the Connection tab, click Export and save as .pem.
d. Open the file to copy the contents.
For Mac, there's an extra Keychain step before exporting, see animation.
2. Make the certificate available to StruxureWare Data Center Expert.
a. Launch StruxureWare Data Center Expert.
b. Select System>Server Administration Settings>Server SSL Certificates...
c. 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.

Access and copy contents from certificate (example using Chrome on Mac)

See also

Viewing External System Data

The Importance of System Time Synchronization for Accurate Power Values
DCO SNMP Status Codes
Enabling Data Center Operation monitoring through Data Center Expert

Page 126
Configuring VMware vCenter integration
Configure the server communication preferences between StruxureWare Data Center Operation and VMware vCenter Server. See
supported versions here.

The VMware vCenter user must have permission to these operations:

setCustomValue
logUserEvent
setTaskDescription
addCustomFieldDef
exitMaintenanceModeTask
destroyPropertyFilter
createFilter
waitForUpdatesEx
retrieveServiceContent
login
logout
waitForUpdates
retrieveProperties

1. Type the logon information of the vCenter server to connect to: host name / IP address, port number, and user credentials.
2. 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 VMware vCenter integration is event-based meaning the vCenter will report directly to StruxureWare Data Center Operation if
events/updates occur that the system must be notified about.

See also

VMware integration enabling migration of virtual machines impacted by alarms

Associating Live Data from an External System to the Layout

Page 127
Configuring Remedy integration

Set up server communication preferences to allow the Data Center Operation server to communicate with the Remedy server and
exchange ticket data.

When you have configured the integration, Remedy tickets will show in StruxureWare Data Center Operation and users can associate
them to work orders. When the user completes work orders in Data Center Operation, 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 Data Center Operation to
completed ticket in Remedy.

Tip

In StruxureWare Data Center Operation version 7.5, integration to Remedy version 8.1 is supported.

Configuring the server communication and user credentials

1. Select System Setup>External System Configuration.
2. Select type: BMC Remedy.
3. Type the logon information of the Remedy server to connect to:
Name
Host (IP address)
Remedy Server Name
Port
User credentials
4. 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.
5. Set the interval between which the system is to check for updates (Default: 300 secs).

Configuring a filter defining which Remedy tickets to show in Data Center Operation
The Remedy Tickets pane will show the not completed Remedy tickets assigned to your user group (defined in the Remedy system).
We will use Due date, Status, Priority, Summary and Assignee data from Remedy. All data is limited by the defined Remedy qualification
filter.

Reuse a specific filter from Remedy:

1. Copy the filter expression from the Remedy Advanced Qualification Builder
2. In Available Filters, select User Defined Qualification Filter
3. Paste the expression into Build Search Qualification.

Build a filter based on sample filters as template:

StruxureWare Data Center Operation provides sample filters you can use as a template to build your own user-defined filter.

1. In Available Filters, select the sample filter that comes the closest to the filter definition you want to create.
2. In Build Search Qualification, mark and copy the wanted filter expression.
3. In Available Filters, select User Defined Qualification Filter and paste the expression into Build Search Qualification.
4. Edit the expression as needed.
5. If you are creating a combined complex filter, repeat the steps to copy another sample filter snippet and edit your combined
custom filter.

Page 128
Testing the server configuration.

Click Test to test the connection before closing the dialog box.

Remedy documentation

For further information about Remedy, see the documentation provided by BMC Software.

See also

Integration with the Remedy change management system from BMC

Configuring external system integration

Page 129
Configuring Cisco UCS Manager integration
Configure the server communication preferences between StruxureWare Data Center Operation and the Cisco UCS Manager.

1. Configure data retrieval from Cisco UCS Manager to StruxureWare Data Center Operation.
a. Type the logon information of the Cisco UCS Manager to connect to: host name / IP address, port number, and user
credentials.
b. For a high-security logon session, select Use SSL and accept the certificate.
Ask the Cisco UCS Manager administrator for details if you are unsure whether to use SSL.
c. Click Test to test the connection.
2. Configure data exchange from StruxureWare Data Center Operation back to Cisco.
Select Use Automatic Power Management if you want to allow StruxureWare Data Center Operation to send back
power data to Cisco.
This will overwrite any existing power groups on the Cisco UCS Manager.

See also

Cisco UCS Manager integration requirements

Configuring external system integration
Viewing External System Data
The Importance of System Time Synchronization for Accurate Power Values

Page 130
Cisco UCS Manager integration requirements

Configuring integration between StruxureWare Data Center Operation and Cisco UCS Manager requires:

A user has been set up on the Cisco UCS Manager with rights to access the web services in the API.
Communication on the port used on the Cisco UCS Manager and, if SSL is wanted, it must be enabled.

Default ports:
http: 80
https: 443

The rest of the configuration happens on the Cisco UCS Manager.

For further information, see Cisco UCS Manager API information and power management.

See also

Configuring Cisco UCS Manager integration

System requirements

Page 131
Configuring StruxureWare Power Monitoring Expert integration

Configuring StruxureWare Power Monitoring Expert integration is a two sided integration.

Compatibility information: Power Monitoring Expert DC 7.2.2 is supported by DCO starting from version 7.4.5.

The below highlighted steps (4 and 5) cover the integration configuration in StruxureWare Data Center Operation. The other
steps are to be done on the StruxureWare Power Monitoring Expert side and are referenced in this document to provide an overview of
all the necessary steps for the integration.
For further information about the StruxureWare Power Monitoring Expert steps (1-3) please refer to the ETL for DCO documentation.

1. Install SQL Server 2014 on the StruxureWare Power Monitoring Expert server.
2. Install StruxureWare Power Monitoring Expert.
3. Install the ETL configuration tool.
4. Setup a dedicated ETL configuration for PME in DCO.
5. Discover devices in StruxureWare Power Monitoring Expert.
6. Set device hierarchy definitions for each device.
7. Define ETL configuration in StruxureWare Power Monitoring Expert.
8. Run ETL job (once or start service).

Setup a dedicated ETL configuration for PME in DCO

1. Log on to DCO 's web client.

2. Go to Administration -> Manage ETL Integrations.
3. Add an ETL configuration.
4. Fill in information for the staging database, and click Next.
5. Select the Power Monitoring Expert transformation "StruxureWare Power Monitoring Expert v1.0.0", and click Next.
6. Setup a schedule for how often to import data from PME, and click Submit.

Page 132
Adding devices to PME

The PME Management Console allows you to add peripherals to the PME server, such as:

Sites- The physical locations where devices are present.

Devices- The physical devices present on the sites along with their properties.
Dial out modems- More options for communication.
Connections Schedules: Scheduling temporary or timed connections to the selected devices.
System Event Logs: Allows seeing system logs which are filterable at sites, devices & alerts level.

Adding Sites & Devices

Devices are added to PME by telling which sites these devices are attached to. Sites can be seen as gateways for devices.

Add Sites:

1. Click on Sites.
2. Right-click the window and select New... > the needed site:
a. Direct Site: If the device is directly communicating with TCP/IP.
b. Modem Site: If the device is residing on a modem and information is being received through the modem.
c. Ethernet Gateway Site: If the devices are connected to Ethernet Gateways such as EGX100/300.
d. OPC: If the devices are communicating on OPC or connected to OPC gateway.
3. Fill in the details for the selected site.
a. Note: TCP/IP port is selected in a drop-down list, e.g. for Ethernet Gateway port number is 502.

Add Devices:

1. Click Devices.
2. Right-click the window select New... > the type of device to be added (Devices are connected via the sites already added).
3. Fill in the details for the device to be added.
a. Note: Unit ID should be same as the Slave number which is defined for the device while adding it to the Ethernet
Gateway.

PME management console

Page 133
Add Site

Device configuration

Defining the device hierarchy

The Hierarchy Manager wizard allows you to map added devices to logical data center entities like circuits, electrical equipment, etc. to
better define what the meter logically represents. Furthermore, logical devices are exportable through ETL which makes them available
to DCO, thus a step should be performed against any newly added devices in PME in order to make them available to DCO as well.

1. In the PME management console, select Tools>Hierarchy Manager.

2. Log on with an supervisor user.
3. For Branch Circuit Monitors, click the Circuits tab.
a. Click Add to add a definition for a circuit in the Circuits tab.
b. Define the Name, Breaker Rating and Rack info (if you have it).
c. Click Add above the Device box and choose the recently added device from the list.
4. For power meters click the Electrical Equipment tab.

a.

Page 134
 4.

a. Click Add to add a definition for a power meter.

b. Define the Name, Equipment Type and Location.
c. Click Add on the devices box, and select the appropriate added device from the list.

Hierarchy Manager

Hierarchy Manager - Login

Hierarchy Manager - Circuits & Electrical Equipment

Hierarchy Manager - Circuits

Hierarchy Manager - Electrical Equipment

Hierarchy Manager - Electrical Equipment Asset Name

Page 135
Defining ETL configuration in PME

1. Open the ETL Administration tool previously installed on the PME server.
2. Create an New ETL job.
3. Tasks that need to be added to the job:
a. Category: Extract Type: PowerMonitoringExpertDataCenterHierarchyExtractTask
i. Verify the Database Connection String settings are appropriate for your PME SQL-server installation.
b. Category: Transform Type: DcoTransformTask
c. Category: Load Type: DcoLoadTask
i. Verify the DCO staging database connection settings are configured to match the staging database
information created in the previous sections (DCO server name/IP, ETL import database name, ETL database
user, and ETL database password are required).
4. Mappings will make PME devices exposed in the ETL database for DCO discovery.
a. Select Use list of sources (allows aliasing).
b. Click Populate.
c. Click Recommend Pairs.
You may see a warning stating the existing mappings will be overwritten.
A list of devices which have logical definitions in the Hierarchal Manager should appear in the Sources list.
d. Verify Import has been selected for each entry (highlighted in screenshot).
5. Click OK to save any changes to the ETL job.

ETL Engine - SQL database connection verification

ETL Engine - DCO staging database connection verification

Recommend Pairs Warning

Page 136
Hierarchal Manager sources list import selected

Running ETL job

1. In the ETL configuration tool, click Control to view the service information.
2. Click the Run Once command to test the ETL job.
A popup should appear stating the job was either successful, or unsuccessful.
View the log information if the job was unsuccessful
3. If the job was successful, return to the DCO client, and view the ETL Integrations in the Unassociated Devices list.
4. In DCO, either wait for the next ETL import cycle to pass, or right-click the PME server entry in Unassociated Devices, and
select Synchronize external data to force the staging database to update DCO.
5. The new devices should appear below the PME server entry.

ETL configuration tool - run once

Device Association - Unassociated Devices list

Page 137
Device Association - new devices in list

Page 138
HP OneView integration
The HP OneView integration is available with the standard DCO license. This will enable you to get basic server and blade enclosure
information from the HP OneView system. Having theStruxureWare Data Center: IT Optimize license, you will also get CPU and power
data from the HP OneView system. TheStruxureWare Data Center: IT Power Control license will furthermore enable power control
features from HP OneView. To use Remote Console from the iLO Integrated Remote Console in the HP OneView system, you must
have the StruxureWare Data Center: Server Access license.

Assets and alarms are transferred instantly from HP to DCO using an event bus. CPU, Power and temperature data are polled from the
HP OneView system using its web service interface. The data shown when you hover over a tooltip is also loaded instantly from the HP
OneView server. DCO also presents historical trending (calculated average over the last 7 days). The interval for polling data for this
trending can be configured (System Setup > External System Configuration > HP OneView Configuration > Utilization update
interval in hours), but the default setting should be precise enough.

No data is transferred from DCO to the HP system.

The HP OneView integration is available for DCO version 7.4.5 or above and HP OneView version 1.10 or above.

Note: DCO 7.5 integration with HP OneView 2.00.x requires upgrading to DCO 7.5 SP3 or above.

123 Steps to...

Configuring data exchange between HP OneView and StruxureWare Data Center Operation

1. In System Setup > External System Configuration, click Add server and select HP OneView.
2. Set up the connection to HP OneView using the credentials of the HP OneView user (user must be HP Oneview administrator)
(Figure 1) and click Test to validate the server connection.
3. Edit update interval (Figure 2).
4. Open Planning>Device Association from the application bar.
5. Drag devices discovered by HP OneView from Unassociated Devices to equipment representing them in the floor or in the rack
layout to associate them.

Figure 1

Figure 2

Page 139
 See also

StruxureWare Data Center Operation: IT Optimize

StruxureWare Data Center Operation: Server Access

Configuring External System Integration

Associating Live Data from an External System to the Layout

Page 140
External system integration through ETL
One of the ways to integrate with external systems is using the Extract, Transform, Load (ETL) system. The ETL system creates
databases which can be accessed directly by 3rd party tools and solutions. It also allows scheduled execution of transformation scripts
on the Data Center Operation server. Together this gives the ability to extract and enter data on the Data Center Operation server.

Based on the ETL system, it is possible to develop custom solutions, integrating DCO with a broad range of data sources.

Watch this video tutorial to learn more about ETL.

For further information, see the developer documentation.

See also

Configuring external system integration

Page 141
Importing manual power measurements

You can import manual breaker panel measurements into DCO by importing the values from a preconfigured Excel workbook through an
ETL configuration. This makes it possible for you to include your manual power measurements on each of the circuits in a PDU in the
automatic power capacity calculations in DCO.

You'll need to

1. Create a staging database on the DCO server

2. Setup an ETL server configuration to read from the staging database
3. Select to create the Excel template in the DCO import wizard, enter your manual power measurements, and save the file
4. Import the saved file, including your measurements, into DCO

See detailed step-by-step instructions here, but first, let's learn about the excel file and entering measurements into the file.

About the Excel file

When importing data from an Excel file into DCO, you must use a fixed format for the Excel file to ensure the data is compatible and can
be processed by DCO. A button is available in the import wizard to automatically create a workbook template based on the latest
solution data from the server to ensure the data is compatible.

Note

It is important that you use the template from the DCO server, and generate the latest version of it in case of an update rather
than using an older version since the template includes information about the current fields in DCO, new equipment added, or
changes made to the breaker panel layout.

The Excel file contains information about the power equipment, customer information (equipment assigned to customer, DCO for Colo fe
ature), and allows you to enter current (Amp) and power (kW) measurements.

About entering measurements

The only data you should change in the Excel is this:

Date and Time (to specify when the measurements where taken)
Amps
Power
Power Factor (which is remembered separately for each PDU)
You can enter your power measurements as both Amps and kW.
Do not delete kW values, even if you use Amps for your measurements only, as DCO needs the kW values for the automatic
capacity calculations.
If you want to use the import functionality to update existing measurement values, provide the same timestamp.

Prerequisites
Access to the Webmin server management interface
Access to External System Configuration in DCO
If importing power measurements into multiple rooms in DCO, you you need access to the rooms for which you want to import
power measurements.

Step-by-step instructions

1. Create an ETL staging database (first time only).

a. Open the Webmin server management web interface by selecting Administration>Webmin in the DCO web client.
Alternatively, type the address of your DCO server in a Web browser folllowed by :10000, <https://>:10000 .
b. Log on to Webmin using the user credentials created during the DCO installation.
c. In the menu to the left, select StruxureWare DC Operation>ETL Integration Management.
d. In Management tasks, click Manage internal database and create a new internal import database, providing details
about the database, user, and secure communication.
The name you provide in Configuration Name will be used in the next step.
2. Configure the staging database created in step 1 (first time only).
a. Log in to the DCO desktop client (with a user that has rights to external system configuration).
b. In System Setup>External System Configuration, click Add server (+ icon) and follow the steps in the wizard:
i. Select system type StruxureWare Data Center Operation ETL Integration.
ii. Configure parameters for the ETL integration, pointing to the staging database created in step 1 (in ETL
Database, select your staging database recognizable with the configuration name you added in Webmin),
and selecting transformation type BreakerPanelMeasurements.
3. Get the Excel workbook template from the DCO server, enter and save your measurements in this file.
a. Open the DCO desktop client and, in the Planning>Data Center perspective, open the rooms to which you want to
import your manual power measurements.
This is a necessary first step as only the open rooms will be available for selection in a later step.
b. Select File>Import>Manual Power Measurements from Excel Workbook.
c. Follow the first steps in the Import manual measurements form Excel workbook wizard.
i. To export the template workbook for a set of rooms as it says in step 1, click Create template file... and
select the rooms to which you later want to import your manual power measurements.
ii.

Page 142
 c.

ii. Enter a file name for your power measurements template file, and make a note of the location in which you
save it.
iii. In your file system, open the template file, and enter your manual power measurements into it to ensure the
format is accepted by StruxureWare Data Center Operation, and save your changes.
4. Import the file with your measurements into DCO.
a. Reopen the import wizard in DCO (File>Import>Manual Power Measurements from Excel Workbook), and in Impor
t settings, browse to the location of your import file, select it, then click Next to review the import preview.
b. If the preview list shows data that will be excluded from the import because of issues encountered, click Save log file...
and review your Excel file again, fixing issues causing the errors before attempting a new import.
c. When you're sure that the import preview looks as it should, click Finish to complete the import.

Measurements that are less than 24 hours old might not be completely processed by DCO, and will not be used for the
Predicted Power calculations until they have been processed. Every 24 hours DCO looks at the measurements received
during the last day and aggregates the data. To ensure stable values in the predicted power calculations, data will not be used
before they have been aggregated.

Page 143
Lock the property field for ETL import

You can lock editing for the name, serial number, and barcode associated with a device from an ETL import in the External System
Configuration option of the desktop client. The web client and REST services will reflect the same locking.

Prerequisites

ETL Import Integration in External System Configuration

Association of external device to a DCO modeled device

You can use the standard release ETL import scripts if you don't have any other scripts:
/sources/modules/etl/server/com.apc.etl.server/resources/pentaho/internal/import/import release test suit

The device will have the locked properties value set by the ETL Import value in the Planning > System Setup > External System
Configuration option.

Use the edit function to configure the transformation, import job, file path, etc.

Configuration

During setup, choose to lock the property values for name, serial number, and barcode with a value from the external system.

You can choose all three properties, or just the ones you want.

Page 144
Verification

Verify that you cannot manipulate the value in the desktop client, the web client, or through the Asset REST webservice end-point.

In the desktop client, find the associated device look up the general properties to verify the property lock.

In the web client, the corresponding properties will also be locked for editing.

To verify the REST API, check that the properties: nameLocked, barcodeLocked, serialNumberLocked have been set according to
above configuration.

Page 145
DCO SNMP status codes

In StruxureWare Data Center Operation, the Data Center Operation server supports these SNMP OIDs and response values.

To implement the alarm statuses in StruxureWare Data Center Expert, update the Device Definition File, schneiderops.xml, in Struxure
Ware Data Center Expert. Download the file from the software download link provided by Schneider Electric and follow the instructions
about updating DDFs in the DCE user assistance.

Application server (OID .1.3.6.1.4.1.318.1.2.2.1.1.0)

Response Name Description

1 Unknown The status of the application server is unknown. Check Webmin and if the problem persists, contact Technical Support.

2 Stopped Restart the Data Center Operation server. If the server was part of a cluster, see the StruxureWare Data Center
Operation User Assistance about rejoining the cluster. If the problem persists, contact Technical Support.

3 Running No problem

4 Running but High availability is lost. The Data Center Operation Application server is running but one or more nodes are not
missing available. If the Data Center Operation server is part of a cluster, ensure all nodes are running and there is a network
nodes connection between the nodes. If the problem persists, contact Technical Support.

5 Initializing Wait for the Data Center Operation Application server to initialize. If the problem persists, contact Technical Support.

6 Starting or Wait for the Data Center Operation Application server to finish starting. If
non the problem persists, contact Technical Support.
responding

7 Disaster This node is running in DR mode.

Recovery

8 Running but The JBoss postoffice is currently inconsistent. This may be a temporary issue. If
postoffice is the problem persists for more than 10 minutes, contact Technical Support.
inconsistent

9 Running but The JBoss is missing jgroups. This may be a temporary issue. If the problem persists for more than 10 minutes, contact
missing Technical Support.
jgroups

Database server (OID .1.3.6.1.4.1.318.1.2.2.1.2.0)

Response Name Description

1 Unknown The status of the database is unknown. Check Webmin and if the problem persists, contact Technical Support.

2 Stopped Restart the Data Center Operation server. If the server was part of a cluster, see the StruxureWare Data Center Operation
User Assistance about rejoining the cluster. If the problem persists, contact Technical Support.

3 Running No problem

4 Detached High availability is lost. The database is detached from the cluster and does not receive updates. See the Data Center
Operation User Assistance about reattaching the database node to the StruxureWare Data Center Operation cluster. If the
problem persists, contact Technical Support.

5 Catching The database is catching up with the cluster. Wait for the StruxureWare Data Center Operation database to retrieve all
up updates from the master node. If the problem persists, contact Technical Support.

6 Attaching The database is attaching to the cluster. Wait for the StruxureWare Data Center Operation database to attach to the
cluster. If the problem persists, contact Technical Support.

7 Running The database is the master in a cluster.

as
Master

8 Running The database is the primary slave in the cluster. All changes on master are synchronously replicated to this node.
as
Primary
slave

9 Running The database is the secondary slave in the cluster. All changes on master are asynchronously replicated to this node.
as slave

10 Running The database does not replicate its changes to other nodes.
alone

Load balancer (OID .1.3.6.1.4.1.318.1.2.2.1.3.0)

Response Name Description

1 Unknown Load Balancer status is unknown. Check Webmin and if the problem persists, contact Technical Support.

2 Stopped Load Balancer stopped. Restart the Data Center Operation server. If the problem persists, contact Technical Support.

3 Running Normal status

Page 146
4 Running but High availability is lost. The StruxureWare Data Center Operation Load Balancer is running but one or more
missing nodes are not available. If the Data Center Operation server is part of a cluster, ensure all nodes are running and there
nodes is a network connection between the nodes. If the problem persists, contact Technical Support.

General and essential services (OID .1.3.6.1.4.1.318.1.2.2.1.4.0)

Response Name Description

1 Unknown Unknown status. Check Webmin and if the problem persists, contact Technical Support.

2 Stopped Essential services are not running on the Data Center Operation server. Reboot the node and monitor the status
page in Webmin. If the problem persists, contact Technical Support.

3 Running Normal status

4 Time is out of The time difference between the StruxureWare Data Center Operation slave and the master node is too big.
sync between Correct the time on the slave to match the time on the master. Consider using an NTP server. If the problem
cluster nodes persists, contact Technical Support.

5 Backup failed The last backup that was attempted on this server was not successful. Ensure the system can write to the location
specified as backup location. This is particularly relevant for network attached storage.

ETL (OID .1.3.6.1.4.1.318.1.2.2.1.5.0)

Response Name Description

1 Unknown Unknown status. Check Webmin and if the problem persists, contact Technical Support.

2 OK Normal status

3 Error ETL experienced an error while running the transformation. Monitor the status page in Webmin. The scheduler will try to
run the transformation again as scheduled.

4 Paused ETL is paused on the Data Center Operation server. Monitor the ETL status page in Webmin. Try to start the job if needed
using the management button.

5 Stopped For future use

See also

Configuring StruxureWare Data Center Expert integration

Page 147
RF Code CenterScape Connector

You can import asset and monitoring related data from CenterScape into StruxureWare Data Center Operation, giving you granular
visibility into data center resources and enabling you to monitor your data center floor. Integrating CenterScape and DCO also eliminates
duplicity of data and labor to enter the same data in two different systems.

RF Code CenterScape offers real-time asset management and environmental monitoring solution. CenterScape continuously tracks
physical asset locations and environmental conditions allowing users to locate and manage equipment, identify and troubleshoot power
and cooling inefficiencies and avoid downtime. The integration of the CenterScape into StruxureWare Data Center Operation simplifies
the management of complex data and reduces data manipulation, providing a single source of information.

Prerequisites
DCO with Change license
RF Code CenterScape version 1 and above
User access to CenterScape web services for integration
Open port and communication between DCO and CenterScape (CenterScape port number depends on the customer
installation)

Preparation

Field mapping

This CenterScape data will always be synchronized with DCO:

Asset Data Custom Properties Environmental Sensor Readings

Name Asset Tag Temperature reading

Serial Number Scope Daily peak temperature

Location Deletable Daily average temperature

Description Operational Status Relative Humidity

Model name

Manufacturer

Connector parameters

This information is to be provided by the customer.

rfcode_user RF Code user name with webservices access

rfcode_password RF Code user password

rfcode_host Url or IP address of your RF Code instance. Typically: http://myserver.rfcode.com/

rfcode_port RF Code port to query web services (e.g. port 6580)

Remove_deleted Possible choices: Yes / No. See Deletion of devices.

Change_ticket_due_days Number of days when a change ticket is due by. Example, 10. See Creation of Change Tickets

Deletion of devices

The user can choose whether the information coming from CenterScape and pushed to DCO should or should not be deleted in DCO wh
en an asset is removed from the CenterScape system.

This does not delete the actual device in the DCO model, only the RF Code information attached to this device.

See how to configure the deletion of devices here.

Creation of Change Tickets

When an asset change location and DCO discovers that Centerscape reports a different detected location than what it previously
reported, a change ticket will be created in DCO. These change tickets will appear in DCO and then can be associated with either a new
or existing work order.

No change tickets will be created on original asset location assignment

The change tickets will have predefined status as “RF Code generated” and priority “Medium”
Change_ticket_due_days variable decides the number of days from present day to be set for due date.
DCO Change module is required to use this functionality

Note: CenterScape considers Location type of Rack as a valid location. When devices are assigned to DataCenters or Rows, it is not
considered as valid locations and hence the change ticket would not be as required. Also when moving a device from DataCenter/Rows
to Racks, a change ticket will not be created as this is considered as initial allocation of location.

CI polling interval (job scheduling)

Page 148
Recommended settings

Up to 60 racks 60 minutes

From 61 to 150 racks 120 minutes

From 151 to 300 racks 180 minutes

From 301 to 500 racks 2400 minutes

Above 500 racks Please contact technical support

It is not recommended to configure a frequency lower than 60 minutes.

RF Code CenterScape data in DCO

Inventory shows up as unassociated devices. Automatic/manual association is needed.

Temperature and humidity sensors bring in values.

They can be dropped anywhere on the floor, in a rack, or on a device.

Page 149
Change tickets are created when an asset is moved from one location to another.

Configuring RF Code CenterScape Connector in DCO

1. Create a new import staging database (see ETL Database Configuration).

2. Download the .zip file from this page (available to verified Schneider Electric customers and personnel only): RF Code
CenterScape Connector

Note

If you cannot access the files, ensure you have a valid software support contract ready and contact technical support.

3. Upload the .zip file from the above step to the DCO server to the /data/pentaho/import/ folder.
4. From the server console (or ssh connection, e.g. using Putty), extract the files from the .zip, using this command:
sudo unzip /data/pentaho/import/RFCode_Connector_1.0.zip
5. From the DCO UI, create a new ETL external system and fill in the connector parameters.
6. Choose polling interval and save your configuration.
7. Restart your DCO client after completing the connector configuration.

Page 150
ServiceNow Asset Management Connector

You can import asset related data from ServiceNow into StruxureWare Data Center Operation (DCO). ServiceNow asset management
controls the inventory and asset life cycle from planning to disposal. The integration of asset management data from ServiceNow into D
CO simplifies management of the complex data and reduces data manipulation, providing a single source of information.

Process overview

Any updates to the Configuration Item table data are synchronized with the Configuration item table in DCO. Before the updates are
pushed to DCO, merging of data occurs in a staging database. Once merge is completed, the data is synchronized with DCO.

Process overview

Prerequisites

DCO version 7.5

ServiceNow version Eureka or above
ServiceNow user access to web services for integration
Open port and communication between DCO and ServiceNow (ServiceNow port number depends on the customer installation)

Preparation

Field mapping

These ServiceNow assets fields will always be synchronized with DCO:

Name in ServiceNow Name in DCO

Asset tag Name

Model category Model name

Manufacturer name Manufacturer

Sys_id (for logical use only) ci_id (for logical use only, not visible)

In addition, you can select extra ServiceNow fields to push to DCO:

Using the Excel spreadsheet provided with the connector (Fields_mapping.xls), you can define which ServiceNow asset related fields
you want to push to DCO.

It is recommended that you ask your local ServiceNow partner to retrieve the information needed for each field: table that contains the
field and field name.

One way to retrieve this information is to:

1. Navigate, in ServiceNow, to the dictionary and filter the view by searching the table cmdb_ci.
2. Search for the fields you want to push to DCO and note their corresponding table (cmdb_ci, cmdb_ci_server…, etc.), their
corresponding column name (=field name) and if the type is “Reference”.
3. Copy this information into the excel sheet provided as shown in the example. If the field type is “Reference”, mark the
corresponding column in the excel sheet as “Y”.

See example in the screenshot.

Page 151
 Warning

Do no edit or remove the fields “sys_id”, “name”, “manufacturer” and “model_id” from the excel sheet. Do not rename the excel
file and ensure the extension is .xls and not .xlsx.

Mapping fields between the systems

Connector parameters

This information is to be provided by the customer.

ServiceNow_username ServiceNow user name with webservices access

ServiceNow_password ServiceNow user password

ServiceNow_url Url or IP address of your HP UCMDB instance. Typically: http://myserver.service-now.com/

The port number can be added to the url: http://my_HP_ucmdb_server:port/

Ensure you end the url with a slash “/”

ci_types The device type to request to ServiceNow. Up to ten different types separated with a comma, without space, e.g.: cmdb_ci
_server,cmdb_ci_netgear,cmdb_ci_network_adapter

Do not add a comma after the last device type.

Remove_deleted Possible choices: Yes / No. See Deletion of devices.

log_file_path Extra variable

Desired location for the log file (default value can be used)

ServiceNow target table

DCO collects information about configuration items in the ServiceNow table called cmdb_ci.

Deletion of devices

The user can choose whether the information coming from ServiceNow and pushed to DCO should or should not be deleted in DCO wh
en an asset is removed from the ServiceNow catalog.

This does not delete the actual device in the DCO model, only the ServiceNow information attached to this device.

See how to configure the deletion of devices here.

CI polling interval (job scheduling)

Recommended settings

Page 152
Up to 80 racks 60 minutes

From 61 to 300 racks 120 minutes

From 301 to 1000 racks 180 minutes

Above 1000 racks Please contact technical support

It is not recommended to configure a frequency lower than 60 minutes.

Configuring ServiceNow Connector in DCO

1. Create a new import staging database (see ETL Database Configuration).

2. Download the .zip file from this page (available to verified Schneider Electric customers and personnel only): ServiceNow Asset
Management Connector

Note

If you cannot access the files, ensure you have a valid software support contract ready and contact technical support.

3. Upload the .zip file from the above step to the DCO server to the /data/pentaho/import/ folder.
4. From the server console (or ssh connection, e.g. using Putty), extract the files from the .zip, using this command:
sudo unzip /data/pentaho/import/Servicenow_Assets_Management_Connector_1.0.zip
5. From the DCO UI, create a new ETL external system and fill in the connector parameters.
6. Set polling interval and save your configuration.
7. Restart the DCO client after completing the connector configuration.

Page 153
ServiceNow Change Management Integration

You can import change records from ServiceNow into StruxureWare Data Center Operation (DCO). ServiceNow change management
controls changes to the IT environment. The integration of change management data from ServiceNow into DCO simplifies management
of the complex data and reduces data manipulation, providing a single source of information.

The ServiceNow Change Management integration is a customized integration that is offered as a service. Please contact your local
sales representative for further details.

How it works

data is synchronized with DCO. In DCO, the ServiceNow change

Change tickets are created in ServiceNow. The
tickets can be associated with work orders created in order to synchronize status.

Process overview

ServiceNow integration features:

Allows integration between ServiceNow change requests and DCO

Seamlessly connect approved ServiceNow change tickets with DCO work orders

Automatically track in real time DCO work order status in the ServiceNow change ticket
External system integration with built in revision control, support for secure communication and advanced logging capabilities

ServiceNow integration benefits:

Streamline work ow process

Improve documentation accuracy
Reduce time to install, move, add, change assets
Seamless implementation, with no required updates

Track and improve SLA’s

Streamline data center requests
Increase overall visibility of the data center
Allows for customization

Prerequisites

DCO version 7.5 or above

ServiceNow version Eureka or above
ServiceNow user access to web services for integration
Open port and communication between DCO and ServiceNow (ServiceNow port number depends on the customer installation)

Integration parameters

This information is to be provided by the customer.

ServiceNow_username ServiceNow user name with webservices access

ServiceNow_password ServiceNow user password

Page 154
 ServiceNow_url Url or IP address of your ServiceNow instance. Typically: http://myserver.service-now.com/

Depending on the integration there will be additional parameters to the above.

Page 155
Configuring email settings
In System Setup>Email Settings, you can configure email settings to enable the Data Center Operation server to send predefined
email notifications.

For the primary Simple Mail Transport Protocol (SMTP) server, then for the backup server (if required):

1. Type the email "from" address that will identify that the emails are sent by the Data Center Operation server.
2. Identify the SMTP server information needed by the Data Center Operation server for communication:
a. Port number at the SMTP server used for communication with the Data Center Operation server and secure connection
for the communication, if required.
b. Logon credentials for the SMTP server that the Data Center Operation server must use to logon to the SMTP server, if
required.

Note

Enable this option only when using an SMTP server that requires logon access.

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

Page 156
Working with multiple languages
The desktop client of StruxureWare Data Center Operation is localized into eleven languages and supports most left-to-right languages,
including double-byte languages. The single installer will place all language resources on your computer. Language, measurement units,
date, and number formats are selected based on your computer's regional settings. StruxureWare Data Center Operation clients, using
different regional settings, can work with the same server simultaneously. The server will take care of converting formats and
measurement units for you.

Watch this video tutorial to learn how to work with StruxureWare Data Center Operation in a multilingual environment.

Tip

You can join our community of multilingual users of StruxureWare products and contribute translations for future versions of
the software.

See more here...

Go to the operating system (OS) instructions for information on how to change the regional settings. It is possible to start the client in a
different language by overriding regional settings.

Tip

Make sure you understand the language settings, if you are working in a multinational company.

It is necessary to understand the difference between the application content and user generated content. Product names, user names,
work order names will remain exactly as they were created.

For example, an English user has created a work order with the default name "New Work Order". This name is stored and would not be
translated. If a Japanese user creates a work order, the default name would be given in Japanese.

The standard tasks and fields in a work order will be translated, while user comments will remain as entered.

Same work order viewed by English and Japanese user.

See also

Reconfiguring locale on the StruxureWare Data Center Operation server

Working with Localized Reports

Starting StruxureWare Data Center Operation Client in a Different Language

Page 157
Starting StruxureWare Data Center Operation Client in a Different Language
StruxureWare Data Center Operation client is available in eleven languages. By default, the
client will launch in the language of the operating system. It is possible to start the client in a Language Country Code
different language by overriding regional settings. This might be useful if you prefer your OS
in one language, but StruxureWare Data Center Operation client in another. However, it is English en
only recommended for bilingual users since some buttons and dialogs, supplied the by
operating system, will appear in the language of the operating system. Examples are French fr
calendar, color picker and standard buttons.
Italian it

Mac OS X German de

Right-click the StruxureWare Data Center Operation application icon and choose Show Spanish es
Package Contents. Locate and open Contents/MacOS/eclipse.ini with a text editor. Add
new line -Duser.language=[Country Code] anywhere below -vmargs line. Brazilian pt_BR
Portuguese

Tip Russian ru

You can create a copy of StruxureWare Data Center Operation application for Japanese ja
each language and edit eclipse.ini file in each copy.
Chinese zh
Simplified
Below is excerpt from modified eclipse.ini
Chinese zh_TW
Traditional
-application
Korean ko
com.apc.isxo.client.bootstrap.application
-clean
-vmargs
-Xms256M
-Xmx768M
-Dfile.encoding=utf-8
-Duser.language=ja

Linux

Locate StruxureWare Data Center Operation executable file. Next to it, there should be Str
uxureWare Data Center Operation.ini file. Open this file with a text editor and add a new
line -Duser.language=[Country Code] anywhere below -vmargs line.

Windows

Locate StruxureWare Data Center Operation.exe and create a shortcut to it. Open
shortcut properties and edit the Target line. Add -nl [Country Code] to the end of the
existing string there. Save shortcut.

Page 158
Opening this shortcut will force StruxureWare Data Center Operation client to launch in the
selected language.

Tip

You can create multiple shortcuts with different Target line for each language.

Page 159
Changing the location of the StruxureWare Data Center Operation client temporary
files
You may want to change the location of the temporary files for a number of reasons that the company policy leaves limited space in the
user profile folder.

Recommendation

Do not move the temporary files to a location on your network drive as you will experience decreased performance.

Windows 7, 8, 10

By default, the temporary Operations files are stored here: C:\users\<username>\.isxo

You can change this location in the .config ini file stored in the program files:

1. Browse to C:\Program Files\<StruxureWare Data Center Operation version>\application\configuratio

n
Program Files is the default location. If you are running 32bit, the location is Program Files (x86).
2. Open the config.ini file in a text editor, such as Notepad++.
3. Edit the path in these two lines from @user.home/ to a location of your choice, for example to the root c:/:
[email protected]/.isxo/<version number>/Operations
[email protected]/.isxo/<version number>/Operations

Page 160
Configuring disaster recovery

How to configure a disaster recovery node

In the following example, two stand alone servers have been created, Server1 and Server2. Server2 will be configured as the disaster
recovery node to Server1. This Standalone + Disaster Recovery setup requires a cluster node license. Managing licenses

If the Disaster Recovery node is monitored by Data Center Expert via SNMP, it is important to set the device scan timeout in DCE
high enough for the Disaster Recovery node to respond. Otherwise, it will return 'communication lost'. How you set the device scan
timeout depends on the network speed between the Disaster Recovery node and the DCO server.

Log in to the Server1 webmin interface, and select StruxureWare DC Operation > Disaster Recovery.
Select Allow another node to connect to this node.

In Allow the following IP as disaster recovery node, enter the IP address for Server2.

Click Attach.

Check Accept fingerprint

then click Allow.

Once the fingerprint is added successfully, follow the on-screen instruction and go to webmin for Server2 to continue the setup.

Page 161
Go to Server2, webmin interface > StruxureWare DC Operation > Disaster Recovery.
Select Attach this node (xx.xx.xx.xx) as a disaster recovery node to another node/cluster.

Enter the IP address for Server1 in Attach this node to the following IP:

Click Attach.

Check Accept fingerprint.

Click Attach.

Page 162
While the node is successfully being attaching, the notification is Attaching the node, please wait this could take several minutes......

The Server1 Status page displays information for both itself and Server2 as Disaster Recovery.

The Server2 Status page displays information only about itself as Disaster Recovery.

Add a license

The standalone node + disaster recovery node setup requires a DCO Cluster Node license.
Log in to the standalone server (Server1) web client, and go to Administration > Licenses.

Enter the license key, and click Add license.

Page 163
Upgrading a disaster recovery setup

Upgrade both the master node and the disaster recovery node to the new version of StruxureWare Data Center Operation.
If you have upgraded from a version before 8.2.7 to 8.2.7 or later you must reconfigure both the master node and disaster
recovery node as described at the top of this page, in section "How to configure a disaster recovery node".
Otherwise it is only necessary to attach the disaster recovery node after the upgrade.

Page 164
StruxureWare Data Center Operation Desktop Client
StruxureWare Data Center Operation 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.You can use the Application bar to navigate between the main parts of the
desktop client.

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, external system setup for device monitoring and alarm data. Some of these options are available in the web client, some
in the desktop client. More...

When the system setup is ready, you can using the desktop client and start building the initial data center infrastructure and add to the
inventory or import data to create a model in the application that represents the real-world physical infrastructure. More...

Getting started

The look and feel of the DCO desktop client

Inventory and asset management

Building the infrastructure and adding inventory

Working with Asset Provisioning

Desktop client configuration

Configuring power
Configuring cooling
Configuring network

Initial installation and system setup

Installing StruxureWare Data Center Operation

Setting up the system

Page 165
The look and feel of the DCO desktop client

Menu bar

The menu bar 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.

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 StruxureWare Data Center Operation: Change installed, you can access Pl
anning>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.

Perspectives

A perspective is a collection of panes and views in a window. The active perspective is indicated by the selected element in the
application bar. Available perspectives are for example: Operations>Data Center, Planning>Data Center, Analytics>Reports and,
depending on the installed add-on modules, possibly more, for example Analytics>Changes (StruxureWare Data Center Operation:
Change feature).

Status bar

The status bar at the bottom provides information about the communication with the server.

Alarm icons with a pop-up notification to inform of active alarms on devices monitored by the StruxureWare Data Center Expert
server or other external system server. Clicking the icon will open the Alarms pane with a list of the active alarms.
Discoveries icon to inform of active discoveries from one or more ITO servers. Clicking the icon will open the Server
Discoveries view, with a list of the active discoveries.
The user name with which you are currently logged on to the system.
The IP address of the server to which you are connecting.
Status icon indicating the state of the server/client connection: red (network problems), green (normal network connection).

Panes

Different screen parts are referred to in this help as panes, for example Navigation, Genomes.

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. You can use Boolean operators AND, OR and NOT to further scope
your search.

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 open a
selected layout in multiple panes, 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

Select Window>Restore Default Screen Layout to restore any screen parts to their default locations.

Page 166
Toolbar
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.

Saves changes made without exiting the display.

Undoes the last action that was performed, regardless of the active perspective. This function is identical to Edit > Undo.

Redoes the last action that was undone, regardless of the active perspective. This function is identical to > Edit > Redo.

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.

Pastes a selection of one or more items into this position. This function is identical to > Edit > Paste.

Opens the Configure Tags dialog box.

Opens the Genome Library from which to select products for the catalog.

Opens a new blank work order in the Work Order Editor in which to edit the work order.

Opens the list of discovered devices from external systems.

Opens the room layout for managing the floor and rack layouts (add, move, delete, or edit) for any room.

Opens the List View for managing any room (add, move, delete, or edit) in a table layout.

Opens the Power Path Layout for viewing a graphical overview of the power connections.

Opens the Map View for viewing a geographical representation of the data center infrastructure.

Opens the 3D View for viewing the data center temperature map in a 3D layout.

Toggles display of the control panel.

Opens a save dialog box to save a screenshot of the 3D layout.

See also

Room layout toolbar

The look and feel of the DCO desktop client

Page 167
Menus
The active menu bar items vary depending on what part of the application is active.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.

File New > Location: Creates a new folder in the physical infrastructure hierarchy with the
default name highlighted so you can type another name. (Right-click Global to invoke
this option.)
New > Floor Plan: Creates a new floor plan to which you can add a background
image, e.g. a .dwg file. (Right-click Global to invoke this option.)
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 > Genomes: Opens the dialog box from which to browse to a file with genomes
and import all or only genomes not currently in the system.
Import > Insight Report Design: Opens the dialog box in which to browse to a custom
report design created in StruxureWare Data Center Operation: Insight to add the
custom report. More...
Export > Temperature Map...: Opens the dialog box in which to export the
temperature map to CSV format.
Export > Floor Plenum Airflows...: Opens the dialog box in which to export the floor
plenum airflow configuration to CSV format.
Export > Ceiling Plenum Airflows...: Opens the dialog box in which to export the
ceiling 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 > Genomes: Opens the dialog box in which to export the genomes to .cat.
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 StruxureWare Data Center Operation to use it as a
template for a new custom report design in StruxureWare Data Center Operation:
Insight. More...
Open File: Opens a file dialog box to open a file from your computer or network drive.

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

Page 168
Tools Open Genome Library: Opens the Genome Library from which to add, edit or remove
available components in the system. More...
Show Discovered Devices: Opens the Discovered Devices view in which to view a
list of all devices from external systems.
Configure Network Cable Types: Opens a dialog box that allows you to change
description and color of cable types in the layout.
Configure Custom Properties: Opens the Configure Custom Properties dialog box
in which to manage and consolidate custom properties and configure templates.
Configure Tags: Opens the Configure Tags dialog box in which to set up tags to
categorize types of equipment in the layout (StruxureWare Data Center Operation:
Capacity feature). More...
Create new Work Order: Opens the Work Order Editor and enables the controlled
automated work order process. More...
Configure new Work Order Process: Opens the Work Order Process dialog box to
create processes and manage repetitive tasks. More...
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-do
wn list in the Work Order Editor.
Preferences: Opens the Preferences dialog box. More...

System External System Configuration: Opens the dialog box in which to set up integration to other systems and manage the
Setup server configurations. More...
E-mail Settings: Opens the dialog box in which to set up e-mail notification functionality. More...
Migrate from StruxureWare Operation: Opens the dialog box in which to move data from previous versions.
Work Order Cleanup: Opens the dialog box from which to delete old work orders. Use this operation with caution. Once
performed, there is no way of retrieving deleted work orders.

Window Show Overlays: Enables selection of available overlays in the room layout. When enabled, you can switch between the
overlays by selecting the tabs at the bottom of the layout.
Show View: Enables selection of available views in the selected perspective. If you accidentally close a view, you can
always retrieve it from here.
Dashboard>PUE/DCiE Dashboard and EE Dashboard: Opens the dashboards in a new browser tab.
Restore Default Screen Layout: Selects to restore any screen parts to their default locations if they have been moved to
new positions.

Help Online Help: Provides access to the online user assistance.

Download client log files: Opens a dialog box in which to define a location to download the system log files to. More...
Data Center Software Website: Opens the Data Center Software Website.
About StruxureWare Data Center Operation: Opens the dialog box with copyright and version information for the
application. More...

Page 169
Navigation
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.

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
use Boolean operators AND, OR and NOT to filter your search further).

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

You can move equipment between the different rooms (and locations) in the Navigation pane and Layout pane by dragging it or
copy/pasting. Opening rooms side by side makes dragging equipment between them easier. To arrange rooms side by side, drag the tab
of an open room off to the side of the main area.

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 Layout 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 Layout 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 Layout), cut, paste, rename, show properties.

You can delete equipment by right-clicking it and selecting Delete.

Tip

You can add, move or delete multiple items at the same time by using Ctrl-click or Shift-click.

See also

Exploring the infrastructure in Map, Floor and Rack Layouts

The look and feel of the DCO desktop client

Page 170
Monitoring operations in Map View
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).

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

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.

Alarms overview

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.

Capacity overview

If you have a valid StruxureWare Data Center Operation: Capacity 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.

Note

The amount of ports shown in the capacity overview here may not be the same as you see in the Network overlay of the room
layout.

Whereas the floor layout Network overlay shows the amount of ports for racks with network equipment including patch
panels, the global capacity overview shows network information represented as a percentage of the available network ports
utilized by networking equipment, not including patch panels, in the location or room.

The data is updated on a daily basis by default. If, for some reason, the data is not recorded, for example because the server was turned
off, you can re-enable recording in Tools>Preferences>Capacity History by clicking Record Now.

123 Steps to... See also

Page 171
Creating a geographical representation of the data center infrastructure Exploring the infrastructure in Map, Floor
and Rack Layouts
1. Create a representation of locations and rooms.
a. Select Planning>Data Center in the Application bar to be able to edit.
b. In Navigation, select the root location icon.
c. 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)
2. If you do not have the Map View open, double-click a location in Navigation to open it.
3. Drag the information boxes representing the locations and rooms from the upper left corner into the wanted position on
the map.
4. If you want another background image for the map view, customize it.
a. Right-click the map view and select Properties.
b. Click Select Image and browse to an image on the computer or network to import the image as background.
5. If you want to restore the default image, download the image used here and insert it in the same way as with another
image.

Page 172
Exploring the infrastructure in Map, Floor and Rack Layouts
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.

1. In Navigation, navigate to any location, room, or equipment that you want to see in the layout.
2. Double-click a location in Navigation to open it in the layout, showing the Map View.
3. Double-click a room in Navigation to open it in the layout, showing the floor layout.
4. 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 StruxureWare Data Center Operation: Capacity installed. You can display or hide specific views using the
display settings (accessed from the Window menu).
5. Show the rack layout by clicking a rack in the room or a rack in Navigation to see the rack front layout of the selection. To see
the rack rear layout, flip the rack by clicking the flip icon in the top left corner of the rack.
If you have StruxureWare Data Center Operation: Change installed, equipment may appear with + or x and arrow symbols,
indicating that changes were proposed to the design, but not yet implemented.
6. Switch to List View (available in the toolbar above the layout) to see the selection in a list.
7. 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

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.

Watch this video tutorial to learn how to use the split floor/rack view in the room layout.

See also

Monitoring operations in Map View

Working with the room layout
Working with the List View
Working with the 3D temperature map

Page 173
Showing or hiding room overlays
In Window>Show Overlays, you can enable/disable overlays in the room layout.

Note

This is a StruxureWare Data Center Operation: Capacity feature. You must have a valid license to use this feature.

You cannot delete all overlays at the same time, so the system will gray out the last view to be able to show something in the graphical
layout.

See also

Working with the room layout

Preferences: Showing or hiding tool tips sections
Preferences: Showing floor dimensions in meters or feet

Page 174
Reviewing system preferences

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.

1. Select Tools>Preferences to access the Preferences dialog box.

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

Setting system of measurement

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.

Linking to custom online 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.

Showing or hiding confirmation dialog boxes

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.

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 StruxureWare Data Center Operation.

Enabling the customer experience program

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.

Setting Energy Efficiency metric

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.

Showing or hiding tool tips

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

Disable any irrelevant information to avoid big tool tips blocking your view of equipment while working in the layout.

Page 175
 See also

Capacity history KPIs over time

Advanced power configuration

Page 176
Keyboard shortcuts
Selecting

Key Item Action

Primary click Single item Select a single item

Ctrl+click Multiple items Select multiple non-consecutive items

Shift+click Multiple items Select multiple consecutive items

Alternative: You can also draw a box around multiple items

Copying and Pasting

Key Item Action

Ctrl+C Selection Copy selected item(s)

If the selection includes multiple items, the coordinates will be preserved relative to each other.

Ctrl+V Selection Paste selected item(s) at cursor position

If the selection includes multiple items, the coordinates will be preserved relative to each other.

Ctrl+X Selection Cut

The selection is only marked for being cut, and not actually cut away from its position until you paste it in another
position.

Navigating

Key Item Action

Single-click Rack in floor layout Open the rack in rack layout

Double-click Rack in floor layout Open the rack in rack layout and open the Properties dialog box for the selected
rack

Double-click Item in the Navigation pane Highlight the selected item in the selected layout

Double-click Server in the Navigation pane Open the rack in the rack layout with the server highlighted

Double-click Item in the Power Dependency vi Highlight the selected item in the layout
ew

Double-click Room in the Navigation pane Open the room in the layout (same tab)

Ctrl+- Layout Zoom out

Ctrl++ Layout Zoom in

Ctrl+ Home Layout Zoom fit

Ctrl+K Selection Show selection in the Navigation pane

Ctrl+L Selection Show selection in the Layout

F7 Open the Genome Library

Alt+Enter Open Properties dialog box

Ctrl+N Open New Room dialog box

Editing

Key Item Action

Page 177
Arrow Keys Selection Move selection 1/16 of a floor tile in that direction

Hold to keep moving it.

Arrow Keys+Shift Selection Move selection by 1 mm

Hold to keep moving it. Coordinate guides will appear.

ESC Selection Interrupt move and return selected item to start position

Ctrl+Shift+E Execute Planned Change (StruxureWare Data Center Operation: Change feature)

Ctrl+Shift+C Cancel Planned Change (StruxureWare Data Center Operation: Change feature)

Ctrl+S Unsaved actions Save

Ctrl+Z Last action Undo

Ctrl+Y Last action Redo

Ctrl+R Selection Rotate selected item by 45°

Ctrl+I Selection Flip selected item 180°

Shift+Delete Selection Mark the selection for deletion

Delete Selection Delete the selection

Page 178
Building the infrastructure and adding inventory
When the initial system configuration is ready, you can start building the data center infrastructure and add to the inventory to create a
model in the application that represents the real-world physical data center infrastructure.

Watch this video tutorial and see CAD Import Supported Entities to learn how to start modeling based on CAD drawings.

Importing data from Excel is also supported. Contact Schneider Electric for further information and making the feature available to you.

123 Steps to...

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.

1. Select Planning>Data Center in the Application bar.

2. In Navigation, select the root location icon.
3. 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)
4. 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, for example adjusting the room design or adding equipment to the rooms.

See also

Creating the equipment catalog

Configuring equipment not available in the genome library
Adding equipment to the floor layout
Adding rack-mountable equipment to the room layout
Adding blade equipment to the rack layout
Setting up the system

Page 179
Configuring the room design
Use the room design toolbar to configure the room layout and ensure the layout in the data center model accurately represents the
real-world physical environment of the room. This includes physical attributes of the room such as size, shape, rows, walls, and cages
(co-lo).

You can toggle the room design mode by clicking this icon when you have selected Planning>Data Center, Plannning>Asset
Provisioning, or Planning>Device Association in the Application bar and have a room open in the layout.

Watch this video tutorial to learn about working with the floor layout or follow the below steps.

1. Modify the room shape.

For example to add an angle to an outer wall:
a. Select the corner tool in the toolbar.

The cursor icon now looks like this when you move it into the layout:

b. Click on a wall where you want to add the 2 new corners that will define where a new wall will begin and end.
c. Select the resize tool in the toolbar.

The cursor icon changes into a double-headed arrow when you move it over a wall in the layout.
d. Click the wall between the dots and drag the new wall into position.
2. Add inner walls or cages.
For example to add a new inner wall:
a. Select the draw wall tool in the toolbar.
The cursor icon now looks like a plus and coordinate guides appear.
b. Click and drag in the layout where you want the new wall to be.
A new wall of the default type now appears in the layout.
c. If you want to change the wall type, right-click the wall and select Set Wall Preferences, then select a predefined
standard wall type or select Properties, and set the width and type (mesh, solid, glass).
3. Add room fixtures, such as doors, windows, and walkways. More...
4. If the room has a row layout, select the Generate Rows icon in the toolbar

and follow the instructions in the wizard.

5. If the tile grid does not match the actual physical environment, select the pan tile tool in the toolbar

, and drag the tile grid around until the tiles are located properly in the floor layout.

See here for details about setting preferences relevant to the room design.

See also

Room layout toolbar

Working with the room layout
Building the infrastructure and adding inventory
Working with the genome library and genomes
Adding equipment to the floor layout
Adding rack-mountable equipment to the room layout
Adding blade equipment to the rack layout

Page 180
Configuring floor weight carrying capacity

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.

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.

1. Configure floor carrying capacity.

a. Right-click a room and select Properties>Room.
b. Define the Maximum Carrying Capacity measured in kg/m2 in the Floor page to match your physical environment.
2. Configure equipment weight.
a. Right-click the piece of equipment in the floor layout and select Properties.
b. 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
Working with the room layout

Page 181
Configuring room design preferences

System of measurement

To toggle the system of measurement used in the client, select Tools>Preferences>General and set Client Settings to display floor
dimensions in meters or feet.

All floor dimensions on the StruxureWare Data Center Operation client will display in meters or feet according to this setting
(metric/imperial).

If you want to see some rooms in metric and others in imperial, you can use different clients or toggle the setting before opening the
various rooms.

Default wall type

To predefine the wall type of any wall added to the room layouts, select Tools>Preferences>General and set Default Wall Settings to
enable a specific wall type, such as standard mesh.

Alternatively, in Genomes, right-click a wall type and select Set As Default to apply the properties of this wall type to any new walls
created.
A green check mark icon on the selected wall in Genomes illustrates the active default setting.

This setting applies to you. Other users in the system can have a different default wall type.

See also

Configuring the room design

Page 182
Adding room elements to the floor layout

Adding rows to a room

Click the Generate Rows icon in the room design toolbar and follow the instructions in the Generate Rows wizard to get a
quick standard row layout from which to start.
Or drag and drop individual rows from the Genomes pane into the layout and flip or resize as needed to get a customized row
layout.

Adding other elements to a room

Adding room fixtures such as gaps and block, inner walls, cages, doors and windows allows you to create a more accurate model of the
data center, making it easy to navigate the room.

1. Click the Genome Library icon and double-click Room Fixture to add the folder and elements to the Genomes pane.
2. Drag the element icons from the Genomes pane into position in the room layout.
3. Right-click an element in the layout and select Properties to edit e.g. name, size, or type properties, or use the icons in the
room design toolbar for editing.

Gaps and blocks

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

Walls and cages

Inner walls are represented as solid, mesh, or glass. You can copy properties from one wall to another or set a default wall type to be
applied to all new walls.

Doors

Doors are represented as slide or swing doors. Swing doors are color-coded in the layout based on security type.

Door Type Color

No lock Gray

Biometric Purple

Card Blue

Key Orange

See also

Configuring the room design

Page 183
Adding equipment to the floor layout
Prerequisite: 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).

1. Drag the component icon into the position in the floor layout that matches its position in the data center:
To add new equipment, drag it from the Genomes pane.
To add existing equipment from another position in the data center infrastructure, 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.
2. Right-click the component icon and select Properties, for example to define a custom name for it, or to use other menu options.
3. Repeat steps 1 and 2 to add all floor equipment to the floor layout.

Tip

You can move multiple items at the same time by using Ctrl-click or Shift-click.

You can switch to Planning>Device Association to associate the components added to the layout with devices monitored by
the StruxureWare Data Center Expert or other external system to get live data from the devices in operation.

See also

Working with the room layout

Page 184
Positioning components in the floor layout

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

1. 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.
2. 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.
a. Right-click the floor layout and select Properties > Floor, and then select Fine-grained Grid layout.
b. Right-click the component icon and select Snap to grid.
c. Drag the component icon to the position of your choice.

Tip

You can move multiple items at the same time by using Ctrl-click or Shift-click.

Aligning selected components in the floor layout

1. Select multiple pieces of equipment by using Ctrl+click or Shift+click.

2. Right-click and select Align Equipment.

This is useful, for example if you have imported a big data center layout with some misaligned equipment.

Adding selected components to a new row

1. Select multiple pieces of equipment by using Ctrl+click or Shift+click.

2. 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 room layout

Page 185
Adding rack-mountable equipment to the room layout
Adding equipment to racks

Prerequisite: Select Planning>Data Center or Planning>Asset Provisioning in the Application bar and select to view a room in Rack
Layout by toggling the Show/Hide Rack Layout icon and clicking a rack in the Floor Layout.

1. Drag the component icon into the position in the rack layout that matches its position in the data center or use the asset
provisioning functionality (in Planning>Asset Provisioning) to automatically add components in the rack layout according to
the selections you make in the Installation Requirements pane (StruxureWare Data Center Operation: Capacity functionality):
To add new equipment, drag it from the Genomes pane.
To add existing equipment from another position in the data center infrastructure, drag it from the Navigation pane.
To add new equipment by using the asset provisioning functionality of the Installation Requirements pane in
conjunction with the Provisioning Map layout overlay:
a. Select the Provisioning Map overlay (tab at the bottom of the floor layout pane) to activate the color-coded
view.
b. Select the component in the Genomes pane.
c. Review the Asset info section of the Installation Requirements pane, for example making sure that the Redu
ndancy setting is correct.
d. Add or review tags as required in Assign tags section of the Installation Requirements pane to categorize
the equipment.
e. In the Add Asset section of the Installation Requirements 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 (StruxureWare
Data Center Operation: Capacity functionality).
f. Click Add.
When you drag equipment into a selected rack, green highlights where it can be placed; red highlights where it
cannot be placed.
2. Repeat above steps to add all rack-mountable equipment to the rack layout.

Tip

You can move or delete multiple items at the same time by using Ctrl-click or Shift-click.

3. Right-click the component icon and select Properties, for example to define a custom name for it, or to use other menu options.

Watch this video tutorial to learn the entire process of how to install new servers.

Adding equipment to shelves in racks

All rack-mountable equipment can be shelf-mounted (Sh). Some servers will have Shelf as default mounting position, otherwise select
Properties>Mounting>Shelf in the right-click menu of the equipment you want to place on the shelf. You can do this in the Genomes p
ane or in the rack layout.

Prerequisite: Find the shelf in Genome Library>Other Rack Equipment and add it to local genomes.

1. Drag a shelf from the Genomes pane into the rack layout. The shelf will not occupy a U position.
2. Add equipment to the shelf by dragging it from the Genomes pane or the Navigation pane to the rack layout.

If there is no equipment on the shelf, place the equipment in the rack, right-click the equipment and select Mounting> Shelf and
the equipment will snap to the shelf. Once equipment is on the shelf, you can drag other equipment directly to the shelf.

Properties of the shelf

You can place equipment in the front and rear on the shelf. The depth of the shelf will determine how much equipment can be placed
there.

In Properties>Physical you can configure weight and depth of the shelf. The weight of the shelf will be included in the total weight of the
rack.

Page 186
Reverse rack U position number ordering

The rack U position numbering can be configured to be start from the top instead of the bottom of the rack. On a rack, select Properties
>Physical. In the property page, there is a check box option to change Ordering from bottom to top. Uncheck the check box to make
the U position count start from the top of the rack. This setting can be bulk updated using the equipment browser.

The rack can also start counting U positions from zero instead of one. Use the check box option Start from zero index.

Page 187
Rack vertical U positions
Each rack can be equipped with additional vertical U positions. Vertical U positions are grouped in multiple segments located within the
single vertical extension panel.

Each rack can be equipped with two vertical extension panels at most. One is located on the left side of the rack and the other on the
right. Left and right vertical extension can have different amount of U positions grouped in segments so as to allow on having asymmetric
configurations.

Image shows rack with two vertical extensions. Left extension consists of three segments with three u positions in each. Right one
consists of four segments with one u position in each.

Vertical U positions can be also configured in Rack Genomes.

To enable vertical extension right click on desired rack and go to Properties>Physical>Vertical u-positions.

There are some limitations to vertical U positions configurations:

Maximum four segments can be defined.

Maximum four U positions in segment can be defined.
It is not possible to edit vertical extension configuration for vertical extension with items mounted on it.

Vertical U positions can hold every rack mounted equipment that can be placed in horizontal U position, except:

Blade enclosures,
Switch enclosures,
Shelves.

Page 188
Page 189
Adding multiple pieces of equipment with bundles
In Genomes, you can create a bundle to add multiple pieces of equipment in one building block. This could be helpful, for example when
creating a large data center setup in StruxureWare Data Center Operation with a large amount of similar equipment.
Together with work order templates, this is powerful for quickly adding bundles of pre-equipped rows or racks and creating the workflow
to support the installation in large setups.

Creating a bundle

1. In Genomes, right-click a folder and select Add bundle.

2. Double-click the bundle icon to rename it.

Adding equipment to a bundle

1. Right-click the bundle icon and select Edit.

This opens the Bundle Layout.
2. Drag equipment from Genomes into the bundle in the Bundle Layout.

You can now use the new building block by dragging the bundle from Genomes into the layout.

Creating a new bundle based on an existing bundle

1. Right-click a bundle from which you want to reuse equipment and select Copy.
This creates a new bundle as a copy of the existing bundle.
2. Rename the new bundle (double-click).
3. Edit the bundle (right-click and drag or delete equipment).

You can now create a work order template with the tasks needed for deploying all the equipment in the bundle. This template can be
reused for assigning work orders to deploy all bundles.

See also

Working with the Genome Library and Genomes

Creating and applying work order processes

Page 190
Editing properties
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.

1. 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.
2. To edit properties for a component in the genome library, i.e. all pieces of this equipment added to the floor or rack layout
subsequently, open Genomes, select a component in the Floor Equipment or Rack-Mountable Equipment pane and perform
the edits in the Properties section.
3. 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.
4. 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

Custom properties

Page 191
Custom properties

Custom properties allow you to store information on items in the system relevant to your setup in addition to the standard properties
provided.
For example, you can use custom properties to store links to external information, such as links to files, web pages, and general URLs.

You configure which custom properties to include in your system through the Tools menu. Once this configuration is done, you can
apply the custom properties and add relevant values for individual items. Creating templates allows you to reuse standard properties.

When you have configured properties, you can add values to an individual piece of equipment in the Custom Properties section of the
Properties dialog box for the item.

Configuring custom properties

When configuring custom properties, you can define rules for how the users are allowed to enter data in the properties fields when using
custom properties.

Property type

Restricting data entry based on property types prevents users from typing data not complying to the type, e.g. in a phone number field,
the user must type numbers; in IP fields, the user must type a valid IP format.

List

The List and List Values fields enable you to create your own drop-down list with options any user can select from when applying
custom properties (Value field in Custom Properties) to equipment.

Mandatory

Although a property may be defined as mandatory, users are not prevented from leaving the field empty. The system will display a
recommendation to enter data.

Unique

Although a property may be defined as unique, users are not prevented from entering identical values. The system will display a
warning.

Configuring new custom properties

1. Open Tools>Configuring Custom Properties.

2. Select a Property Type to restrict user entries to this data type.
See below for information about the use of links and e-mails.
3. Enter a description of what the property will contain (optional).
4. Create a drop-down list of options to select from by selecting List and entering the options to include in the drop-down list
(optional).
5. Indicate if the property is mandatory or unique.

Modifying custom property configurations in use

If you modify a custom property name, the system updates any existing property values.
If you modify a custom property type, the system performs a conversion of any existing property values. If you have properties in the
system that are not compatible with the new type, the system keeps both versions and you must consolidate:

1. In the Configure Custom Properties dialog box, right-click the property with the conflict and select Consolidate.
2. Select the target property you want to keep.

Configuring custom property templates

1. Open Tools>Configuring Custom Properties and select the Templates tab.
2. Click the Add new template icon and name your template.
3. Click in the Custom Properties column to select the properties to include.

Page 192
Using custom properties
When custom properties have been configured, you can apply property values to items in the system.

1. Right-click an item in Navigation or Layout, such as a room, floor or rack-mounted equipment and select Properties>Custom
Properties.
2. Add custom properties to the list.

Linking through custom properties

If you start a property value with http:// or file://, you will create a clickable link in the list of custom properties and will also add C
ustom Links to the context menu for the equipment item. This allows you to store for example a photo of the equipment or any
equipment documentation, or create a link to product pages.
You can even launch a Remote Desktop Connection to a server through an RDP link.

Sending e-mails through custom properties

If a custom property has been configured for storing valid e-mail addresses, you will create a clickable e-mail link if you type a valid
e-mail address.
Clicking the link will open the default e-mail system on the computer, preparing to send an e-mail with the path of the equipment in the
subject line.

Using custom property templates

When templates have been created, a new context menu option appears on items, allowing you to apply the templates to items in the
system.

1. Right-click an item, for example in the layout and select Custom Property Templates>Your template name.
2. Click OK to apply the template.
You can add more custom properties to this item if you want in addition to the ones added with the template.

Page 193
Page 194
RDP linking through custom properties

You can create an RDP link through the Custom Properties. When you later select the custom property, the system will launch a Remote
Desktop Connection for that server.

1. Click here to download and save the remote.rdp file.

2. Open it in Notepad++ or similar text editor.
a. Replace <HOSTNAME> with the hostname or IP address of the RDP server and replace the port if is running on
another port.
b. Replace <USERNAME>
3. In StruxureWare Data Center Operation, create a new custom property and set the Value to: file://<PATH_TO_FOLDER>/r
emote.rdp
A link that can launch an RDP session has been generated.

Tip

NOTE: The .rdp file is stored on one client, so the link will not work from other clients. To enable the link on multiple clients,
store the .rdp file in a shared location, such as an FTP or Web server.

See also

Custom properties

Page 195
Working with the genome library and genomes
StruxureWare Data Center Operation includes a built-in Genome Library and a customizable list of genomes to use in your data center
infrastructure.

Genome Library

This is a read-only library of available products you can select from and add to the customizable list of genomes and use in your data
center infrastructure, provided you have the necessary user rights. (Genome Library pane to the right in the image). The Genome
Library database is extended with thousands of additional measured server power profiles, as well as storage and switch specifications.
This continuously growing asset library enables StruxureWare Data Center Operation to determine power consumption without the aid of
hardware sensors.

You can open the genome library and drag and drop equipment directly into your customizable list of genomes and rearrange products.

Genomes

This is an editable list of selected products you can use in your data center infrastructure. (Genomes pane to the left in the image).

You can right-click to add, rename, or delete categories and to copy or delete products. Multiple users can apply changes to the
genomes at the same time.

The Genomes pane 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 list shows all equipment that contains the typed
characters.

123 Steps to...

Page 196
 Creating the list of Genomes

Configure the list of genomes to contain the floor and rack-mountable equipment to add to the data center infrastructure.

Adding categories and products

1. Select Planning>Data Center in the Application bar.

2. Access the Genome Library through Tools>Open Genome Library or the Open Genome Library icon in the Toolbar.
3. Drag and drop a product or category from the library to the Genomes pane (or right-click and select Add to Genomes).
The products are placed in the same structure as in the library.
4. If you need a new sub category, right-click a category in Genomes and select Add category.

Editing categories and products

1. Right-click a category in Genomes to add, rename, or delete categories.

2. Right-click a product to copy or delete products.
3. Drag and drop products and categories if you want to restructure the list.

If a product does not exist in the Genome Library...

Customizing an existing product

You can use the generic components to configure a product that does not exist in the Genome Library.

For example, use the Generic Switch Enclosure and Generic Switch Module to configure a modular switch that does not exist in the
Genome library yet or a Generic Rack to configure a non-standard size rack, such as half size.

To add a half size rack:

1. Right-click a Generic rack type in Genomes.

2. Select Properties and modify the size, name, etc.

Requesting support for a not yet supported product

You can use the device support request option available in the main menu bar, ADD MY DEVICE, to request support for any products
in your data center that you cannot currently find in the Genome Library.

To send a device support request:

1. In the main menu bar, select ADD MY DEVICE.

2. Fill in the request form, adding details about the device, such as type, model, vendor.

To track progress on your pending requests:

Go to My device requests, available in the profile menu (your profile image in the top right corner).

See also

Building the infrastructure and adding inventory

Adding equipment to the floor layout
Adding rack-mountable equipment to the room layout
Configuring equipment not available in the genome library

Page 197
Genome icons

The most frequently used genome icons:

Type Icon

Block B

Bundle B

Gap G

Row R

Cage C

Server Room S

Electrical Room E

Rack R

UPS U

PDU P

Power Panel P

Remote Distribution Panel D

Battery B

Auxiliary X

CRAC C

RDU D

ATS A

Generator G

Generic Rack-mount Equipment, e.g. Server E

Environmental Equipment E

Environmental Power Consuming Equipment E

HACS H

CACS C

Camera C

Sensor S

Sensor Pod P

Rack-mount PDU P

Storage S

Generic Data Center Equipment G

Blade B

Blade Enclosure B

Person P

Switchgear S

Chiller CI

Air Chiller AC

Condenser CO

Network Gear, e.g. Patch Panel N

Door D

Window W

Breaker B

Breaker Module BM

Page 198
See also

Working with the genome library and genomes

Page 199
Configuring equipment not available in the genome library
When adding equipment to the floor and rack layouts, you may experience that the product you have in your physical data center and
want to add to your data center model does not exist as a standard component in the system's Genome Library yet.

The Genome Library is a public generic library containing thousands of measured server power profiles, as well as storage and switch
specifications and is continuously growing. However, it does not include all products in the market as soon as they are released so some
products may not be in the database yet. You may also need a genome that is slightly different from one in the library. In this case, you
must create a new genome with more precise information in your local genomes.

Creating new genomes based on generic components

You can use the generic components to configure a product that does not exist in the Genome Library.

For example, some network and compute units are not included in the Genomes yet.
Use the generic network and switch components as templates and customize the properties to match your product:

To add network products, use:

Generic Switch Enclosure

Generic Switch Module

To add blade products, use:

Generic Blade Enclosure

Generic Blade

To add other not yet supported equipment, use for example:

Gap (items over which cables and cooling lines can be routed (such as a walkway or ramp)
Block (solid items over which cables and cooling lines cannot be routed (such as a support column)

You can also use the generic components to configure custom equipment, such as half size racks and other custom solutions.

Configuring a NAS and fire suppression system based on generic components.

Importing genomes

It is possible to import genomes into your local genomes. You may find this useful when editing existing custom genomes.

1. Select Planning>Data Center in the Application bar.

2. Select File>Import>Genomes.
3. In the Open dialog box that appears, browse to, and select the file (*.cat format provided by Schneider Electric).

See also

Working with the genome library and genomes

Page 200
CAD Import Supported Entities
When importing from a CAD drawing (.dwg file), these entities are supported and recognized by StruxureWare Data Center Operation.

The DWG drawing must have measurement units (e.g. mm or inches) specified to allow import at the correct scale.

To detect a room or a cage, the lines must be closed, meaning shapes containing open doors or windows are not detected. The room
must be drawn using poly-lines to be able to use the detect wall tool.

Shapes

Arc

Circle

Line

MText

Polyline

Text

2dPolyline

Ellipse

Point

Solid

Hatch (only filled with a solid color)

MLine (partially)

RotatedDimension

AngularDimension

ArcDimension

DiametricDimension

RadialDimension

OrdinateDimension

AlignedDimension

Leader

MLeader

ArcAlignedText

(In version 7.3.6 or prior versions, support was limited to Arc, Circle, Line, MText, Polyline, and Text)

Page 201
Working with the room layout
The main graphical element of StruxureWare Data Center Operation is the room layout in the center of the screen by default. It shows
the floor layout of the room and, if enabled, the rack layout of the selected racks in the floor.

You can open multiple locations and rooms in the floor or rack layout at the same time, allowing you to compare or drag equipment
between them.

Use File>Export>Layout as image to export an image of the floor or rack layout with the selected layout.

Watch this video tutorial to learn about working with the floor layout.

Floor Layout

Use the floor layout to manage a room's floor equipment (view in different power, cooling, network, etc. overlays, and add, move, delete,
or edit equipment properties).

Use the room design toolbar zoom icons to control the zoom level or click the zoom icon in the top left corner of a rack:

If you select (highlight) a rack in the floor layout with the rack layout enabled, the rack will also be selected (highlighted) in the rack
layout. If you double-click, the same thing happens and the properties for the selected rack shows.

Clicking the pin icon in the floor layout "pins" the rack in the rack layout:

The icon appears in the top right corner when you move the cursor to a rack.
Pinning a rack means the rack is frozen in the rack layout and continues to show there even when you select other racks in the floor
layout. Clicking the pin icon again removes the "pin" and unfreezes the rack in the rack layout.

Rack Layout

Use the rack layout to manage the rack-mountable equipment of any room except store rooms (view, add, move, delete, or edit
equipment properties).

You can toggle the display of the rack layout using this icon in the room design toolbar:

You can view the racks from the front or rear. The flip icon toggles and flips the layout:

Overlays

The selected layout overlay defines what information is shown on top of equipment in the layout. You can switch to see the layout with
another overlay by selecting another tab at the bottom of the floor layout pane.
In Window>Show Overlays, you can predefine overlays between which to switch.

When you hover over equipment in the layout, tool tips display information relevant to the selected overlay.
In Tools>Preferences>General>Tool Tips, you can predefine some of the tool tip information to show.

Note

Disable any irrelevant information to avoid big tool tips blocking your view of equipment while working in the layout.

You must have a valid license for the add-on modules to see all overlays in your system.

Page 202
 See also

Configuring the room design

Room layout toolbar
Building the infrastructure and adding inventory
Configuring floor weight carrying capacity
Exporting layout as image
Positioning components in the floor layout
Room overlays
Showing or hiding room overlays
Preferences: Showing or hiding tool tips
What does the power tool tip tell me
What does the cooling tool tip tell me

Page 203
Room overlays
The selected overlay defines what information is shown on top of the layout. You can switch to see the room layout in another overlay by
selecting another overlay tab at the bottom of the room layout pane. In Window>Show Overlays, you can define which overlay tabs to
enable.

Association
Map Color highlights are used in the floor and rack layouts to indicate components most likely
representing the selected device in StruxureWare Data Center Operation (StruxureWare
Data Center Operation: Capacity feature).
This overlay is available when you are working with Planning>Device Association and
color highlights appear when you select a device in Unassociated Devices if there are
one or more potential matches for the device in StruxureWare Data Center Operation.
Dark Green: Perfect match.
The identifying properties of the unassociated device match those of the proposed
matching component in the layout. The software expects the match to be unique in
the sense that an external item should match with only one piece of equipment in Str
uxureWare Data Center Operation.

When highlighting perfect matches, the software compares these properties:

ITO asset and StruxureWare Data Center Expert device: IP to StruxureWare
Data Center Operation component: Port configuration or any custom property
ITO asset and StruxureWare Data Center Expert device: Serial number to Struxu
reWare Data Center Operation component: Any custom property
Any external system device: Name to StruxureWare Data Center Operation com
ponent: Label
Light Green: Highly likely match.
Some properties of the unassociated device match those of the proposed matching
component in the layout. The software detects multiple candidates and cannot tell
which is the best. However, you can use these highlights to narrow down the
components and their location before doing a manual association.

When highlighting highly likely matches, the software compares these properties:
ITO asset and StruxureWare Data Center Expert device: Model to StruxureWare
Data Center Operation component: Model
ITO asset: Genome to StruxureWare Data Center Operation component:
Genome
Yellow: Likely match.
The specified manufacturer of the unassociated ITO device (property) matches that
of the proposed matching component in the layout. The software detects multiple
candidates and cannot tell which is the best. However, even if there may be many
servers of a specific make, you can use these highlights to narrow down the
components and their location before doing a manual association.

When highlighting likely matches, the software compares these properties:

ITO asset: Manufacturer to StruxureWare Data Center Operation component:
Manufacturer
Cooling The Cooling overlay 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. Equipment is colored to describe cooling as green: sufficient; yellow: partial; red:
insufficient. The tooltip shows you important cooling indicators, such as a cooling unit's capacity (load in kW) and estimated return temperature.

Floor This overlay 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
Plenum pop-up box when the cursor is placed over a tile.

Floor This overlay of the data center floor layout shows a color-coded overview of the pressure distribution for the type of data center layout that includes a raised floor environment,
Plenum perforated tiles, and downflow CRACs.
Pressure

IT Optimize This overlay shows power utilization of the servers in a rack. Racks are colored to describe the utilization as: green: max amount of servers are utilized; yellow: max amount of
servers could be consolidated; red: max amount of servers could be retired. The tooltip includes a graphical overview of the server utilization in a selected rack. (StruxureWare
Data Center: IT Optimize feature)

Page 204
Network This overlay shows network capacity data for racks with network equipment, including total number of ports and remaining ports. Colors indicate the amount of ports in use: red:
all; yellow: almost all.

Note

The amount of ports shown in this overlay may not be the same as you see in the capacity overview shown in the global map overview.

Whereas the floor layout Network overlay shows the amount of ports for racks with network equipment including patch panels, the global capacity overview
shows network information represented as a percentage of the available network ports utilized by networking equipment, not including patch panels, in the
location or room.

Physical
The physical capacity of racks and their contents is shown, such as available U space.
The tooltip shows U and W bars on the racks to indicate the remaining U-space and
weight capacity. The weight capacity bar shows how much the equipment placed in the
rack layout weighs compared to the carrying capability of the floor or the rack depending
on which is the highest. The bar indicators are divided into 3 sections 0-55% green,
56-85% yellow, 86-100% red.

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.

If alarms occur on associated equipment, alarm icons help you identify precisely where
in the layout the alarms occur, for example on a specific UPS in the layout and what the
severity of the alarm is.
Power Power capacity data is provided on top of power consuming components that identifies in detail how much power the component is using. 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). The tooltip shows E and M bars on the UPS units to indicate the estimated and measured loads. The M bar only occurs when a
device from an external system has been associated with the component in StruxureWare Data Center Operation.

Provisioning
Map Color highlights are used in the racks to indicate what position is best suited for the
selected equipment (StruxureWare Data Center Operation: Capacity feature).
This overlay is available when you are working with Planning>Asset Provisioning and
the color highlights appear when you click Add to Best Rack.
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)
Co-lo The co-lo overlay shows information on space and rack count. See more here.

Cooling This overlay shows the thermal influence of an individual cooling unit over the facility, as well as its influence on individual sensors. Go to the Cooling Optimize tab and right
Optimize click a cooling unit in the layout. Select Show Influence to see the influence map.

You can adjust the Influence Scale to get a higher level of detail and a better view of the influence of the cooling units. Go to Tools > Preferences > Cooling Optimize.

The rack tool tip shows you the rack temperature on a scale of the high/low limit temperature set points.

The CRAC tool tip tells you if the unit is controlled manually or automatically and if the unit is on/off. The small icon
on the CRAC indicates that the CRAC is controlled automatically. If the icon is blue, it is on, and if it is black, it is off.

See also

Working with the room layout

Room Colo overlay

Page 205
Exporting layout as image
You can export the layout to a file.

1. Select File > Export > Layout as image to access the Export dialog or click this icon in the layout toolbar

.
2. Select which room or rooms to export and which layout overlay to export.
3. Select to omit cage, row, and customer specific data (suitable for co-lo environments).
4. 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 room layout

Page 206
Inventory report
You can generate an inventory report that lists the contents of the selected item or items in the application.
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).

See also

Working with Reports

Page 207
Room layout toolbar

Default Description
Tools

Zooms in (Ctrl+).

Zooms out (Ctrl-).

Zooms to show full layout (Ctrl+Home).

Toggles rack layout to show or hide the rack layout next to the floor layout.

Exports layout as image file.

Toggles room design mode to show or hide the room design icons.

Enables default pointer cursor.

Enables marquee select cursor to multi-select by dragging a box around a selection.

Enables ruler cursor to drag a line to show a distance, for example to other equipment or a wall.

Room Description
Design
Tools

Enables resize cursor to resize room elements, such as rows, blocks, gaps, containment systems and walls.

Enables the add corner cursor to add corner dots for creating new walls. To create a new wall, subsequently use the resize cursor
to drag the new piece of wall between the dots into position.

Enables the pan tile cursor to change the starting point of the tile layout.

Enables the draw wall tool to create walls and split cages. Press and hold Shift to draw consecutive wall segments.

Enables the draw rectangular shape tool. Double-click a shape to create a cage.

Generates a row layout with the settings selected in the wizard.

Resets to default layout in the Power Path Layout.

Paint items that are connected to equipment in other rooms as solid in the Power Path Layout.

Rack Design Description

Tools

Enables the show network tool to show network connections in the rack view.

Enables the hide network tool to hide network connections in the rack view.

Enables the connection tool to create network connections by clicking the source and then the destination of the network
connection.

See also

Working with the room layout

Configuring the room design

Page 208
What does the power tool tip tell me
Measured load

The measured peak power reported by the devices through an external system integration during a period of 30 days (configurable).
When using the power tool tip on servers, the measured data shown (if any) will be coming from the StruxureWare Data Center: IT
Optimize and is not part of the measured load shown at rack level. The measured data at that level will be coming from associated rack
PDUs discovered by StruxureWare Data Center Expert.

Estimated load

The load of all equipment in the rack even if the equipment has not been connected to a rack PDU (often the manufacturer's nameplate
value), unless the equipment has been marked as not being connected (Power properties setting, Exclude rack's load from power
calculations).

If a server is connected to 2 UPS units, the estimated load on each UPS is 1/2 the total estimated load, and the remaining 1/2 is shown
as failover load. In a typical scenario, it is expected that each server loads the 2 UPS units evenly, but in case one of them is turned off,
the other one will have to carry the full load and the load "fails over" to that UPS. See also potential failover Load.

Tip

TIP: If the load seems very high, check that the estimated load on each server is realistic. If the load still seems very high, you
can improve this by supplying more information, such as how the server is connected to the rack PDUs, or by supplying
measured (peak) power data for all rack PDUs in the rack.

If the load is red, it exceeds the supported load. See here for troubleshooting tips.

Potential failover load

The additional load in case the other power feed is turned off. For example, if the A-Feed UPS was turned off, then the B-Feed UPS has
to carry the full load, and so should the Rack PDU breakers, etc.

If the load is red, it exceeds the supported load. See here for troubleshooting tips.

Redundancy

The rack's redundancy level.

Definition: 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. For information about
configuring power connections, see here.

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

Largest possible server

The maximum load that a potential new server is allowed to add to the rack (without exceeding the allowed average power draw per
phase).

Page 209
 See also

Working with the room layout

Configuring power connections
Setting up a capacity plan

Page 210
Power tool tip troubleshooting

If there is an issue with your power configuration, the system warns you by highlighting the problems in the tool tip.
In this example, there is an issue with the potential failover load. There might be a problem even if there seems to still be power
available. Follow the below instructions to troubleshoot.

1. To troubleshoot, enable the advanced power tool tip and see details about the phases and feeds.
a. Select Tools>Preferences to access the Preferences dialog box.
b. Select Advanced Power.
2. Now, hover over the rack again and inspect the tool tip.

The tool tip reveals why the configuration does not provide enough power in case of a failover. This is a 3 phase configuration and phase
L1 on the A-Feed UPS would be overloaded in case of a failover. This causes an issue regardless of the available power on the other
phases.

If the estimated load would also be highlighted in red, there would be a similar issue with this value and the solution would be the same:
to reconfigure the phase configuration.

See also

What does the power tool tip tell me

Page 211
What does the cooling tool tip tell me

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.

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.

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.

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
Working with Capture Index

Page 212
Configuring power connections
Configuring power paths is a prerequisite for enabling some of the more advanced features, such as Add to Best rack in Planning >
Asset Provisioning.

Power dependencies can be configured on the device properties to identify the power connections, e.g. from UPS to PDU to rack PDU
to server.

The Power Dependency pane lists the configured power dependencies between the equipment in the data center model. The Power ov
erlay highlights the configured power connections in the layout.

You can enable/disable views in the floor and rack layouts by selecting Window > Show Overlays.

Watch this video tutorial to learn how to model distributed redundant UPS configurations.

123 Steps to...

Setting up a power path

You can set up the power connections between the equipment supplying and delivering power and the equipment requiring power.
Various items can be the top level item in a modelled power path, for example a UPS, rectifier (DC power path), or PDU. If a PDU is
the top level item, remember to set an input breaker value on the PDU as the system needs a value to calculate a valid power path.

Before configuring the power path, you must configure the data center layout and add equipment that will make up the power path to
the floor and rack layout, all the way from UPS to rack PDUs and servers.

1. In the Application bar, select Planning > Data Center.

2. 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.
3. In the Properties dialog box, go to Power > Power Dependency to select a power supply and enter connection details for the
connection between the UPS and PDU.
4. In Power > Breaker Panel, in the Power Consumer column select the rack PDU in the drop-down menu and select breaker
from the Breaker column to specify the connection between the PDU and rack PDU.
5. Select the Power Path tab at the bottom of the floor layout pane to highlight the configuration of power connections 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.

Page 213
Configuring DC power
In DCO you can configure a Direct Current (DC) power path by using DC genomes to model DC equipment, including a rectifier and
fuses for breakers to form the power path.

Generic DC equipment is available in the Genome Library. You can add these to your local genomes and adjust the properties to match
the DC equipment in your data center infrastructure, all the way from top level item such as UPS or rectifier in the floor layout all the way
to rack PDUs and servers in the rack layout.

Note

Various items can be the top level item in a modelled power path, for example a UPS, rectifier (DC power path), or
PDU. If a PDU is the top level item, remember to set an input breaker value on the PDU as the system needs a value
to calculate a valid power path.
A rectifier can be added as the top level item in a power path with DC voltages. If your setup includes a rectifier, you
may find power specified in amps/volt in addition to kW depending on the available vendor data. In case these are not
completely identical (due to rounding), DCO will use the lowest of these values to be on the safe side.
If you set input breaker ratings on the equipment, the available capacity may be restricted by these.
If your configured DC equipment is associated with DCE devices with measured data in amps, the DCO tooltip will
show amp values.
You can set a Default breaker derating for DC (Preferences>General).

How to model DC equipment

To set up a DC power path in DCO:

1. Set up your DC genomes.
a. Open the Genome Library and drag and drop items supporting DC voltages into your local list of genomes, e.g.
Generic items such as rectifiers, breakers and fuses, UPS, ATS, PDU, PP, RDP units, and rack PDUs.
b. Right-click and select Properties to rename items and adjust power properties as needed to match your modeled items
with your physical infrastructure, for example kW values on servers, input breaker ratings on PDUs, volt/amps ratings
on rectifiers.
Learn more here about working with genomes in DCO.
2. Add your DC equipment to the floor and rack layout and configure the power connections between them, all the way from top
level item such as UPS or rectifier to rack PDU and server.
a. Enable the layout edit mode (Application bar Planning> Data Center).
b. Open a room's Floor Layout, and drag the floor-mounted equipment from your list of genomes to the layout, such as
UPS, rectifier, power distribution units, and racks.
c. Open a room's Rack Layout, and drag the rack-mounted rack-mounted equipment from your list of genomes to the
layout, such as rack PDUs, and servers.
d. Open the power-related properties of the equipment one by one (right-click, Properties>Power/Power
Distribution/Power Dependency) and set up the power connections between the equipment in the power path,
including breakers and fuses.

The configured power paths are highlighted graphically in the Power Path layout and as lists in the Power Dependency tab below the
layout.

DC genomes

Page 214
Page 215
Working with Rack PDUs
Before connecting rack PDUs, you must add rack-mount equipment and rack PDUs to the layout by dragging these from the local
genomes to the rack.

1. In the Floor Layout, right-click the rack and select Properties > Power.
2. In the Properties dialog box, select a rack PDU and click Edit to enter the connection details.

Note: You can pair power consumers in the Properties dialog box. Use Shift+click to select two power consumers and click Pair. The
paired consumers will now appear in the Paired power consumers table. You can split a pair by selecting it and clicking Split. Paired
power consumers are primarily used in a co-location facility to provide power redundancy at the rack or cage level. Simulated impact will
show failover loads for each receptacle. See more here.

Positioning rack PDUs within the rack

In the rack layout the rack PDUs can be positioned using drag and drop. The new positions will be reflected in the navigation tree, but
the changes can only be made in the rack layout.

Rack PDUs with extended information

From 8.3 release in genome library there are rack PDUs with additional banks and outlets definition. Thanks to this extension user can
now connect end power consumer in rack to selected outlet. Power phase and output voltages are then found automatically by the
system, based on upstream connections. When connecting rack PDU to power supplier, based on the inlet type only relevant breakers
are shown for selection to avoid errors in power path configuration.

In order to check whether a rack PDU supports bank and outlet information, right-click the rack PDU and select Properties > Power.
There is an information about extended power information, Power Outlets and Voltage Outputs fields are not editable, and it is
possible to configure Internal breakers derating.

List of rack PDUs with extended power information can be found here: Rack PDUs with extended power information.

See also

Adding rack-mountable equipment to the room layout

Page 216
Configuring multiple power connections
You can configure multiple power connections to one rack PDU. The number of connections is limited by the number of power inlets on
the rack-mounted equipment.

1. Right-click the rack-mounted equipment, e.g. server, and select Properties>Power.

2. Type the number of power inlets.
3. In Power Cable Connection, select a rack PDU and connect to the relevant outlet if available* or choose phase from available
phases.
Make sure that the number of connections to each rack PDU is in compliance with your redundancy.

*Only for rack PDUs with outlets definition.

Page 217
Configuring distributed redundant UPS systems
A distributed redundant UPS configuration can be used as an inexpensive way to obtain complete redundancy as it is less expensive
than a 2N architecture. It is usually chosen for large multi-megawatt installations where concurrent maintenance is a requirement and
space is limited. It involves 3 or more UPS modules with independent input and output feeders. The critical load is connected through
multiple PDUs. In some cases, STS are also used.

For further information about UPS System Design Configurations, see White Paper 75.

StruxureWare Data Center Operation allows you to model all distributed redundant UPS design configurations mentioned in the white
paper.

Follow the below instructions or watch this video tutorial to learn how to model distributed redundant UPS configurations.

Distributed redundant "catcher" UPS configuration

This configuration includes 3 UPS modules in a distributed redundant design that could also be referred to as a "catcher system". In this
configuration, module 3 is connected to the secondary input on each STS, and would "catch" the load upon the failure of either primary
UPS module. It is only supported to have one "catcher" UPS per "catcher system" and it must be unloaded. Otherwise, you should set
up a distributed redundant UPS configuration as described below.
Configuration:

1. Add UPS modules, PDUs, STS, and racks to the floor layout as illustrated.
For the STS, add ATS from Genomes, right-click them and rename them STS.
2. Add servers and rack PDUs to the racks.
3. Configure the power paths.
a. Right-click the UPS modules one by one and select Properties>Power to set up redundancy feeds.
i. For UPS 1, select "With Catcher" (Distributed Redundant).
ii. For UPS 2, select "With Catcher" (Distributed Redundant).
iii. For UPS 3, select "Catcher" (Distributed Redundant).
b. Connect all equipment to the power paths (see tip below).

In normal operation, UPS 1 and 2 carry the full load.

In case of a failure of either UPS 1 or 2, UPS 3 catches the load of the failing UPS.

Distributed redundant UPS configuration (with STS)

This is a distributed redundant design with three STS and the load evenly distributed across the three modules in normal operation. The
failure on any one module would force the STS to transfer the load to the UPS module feeding its alternate source.
Configuration:

1. Add UPS modules, PDUs, STS, and racks to the floor layout as illustrated.
2. Add servers and rack PDUs to the racks.
a. Right-click the UPS modules one by one and select Properties>Power to set up redundancy feeds, all Distributed
Redundant.
b. Right-click the STS one by one and select Properties>Power Dependency to set up primary and secondary
connections.
i. Set the primary load so each UPS carries its own load.
ii. Set the secondary load so the UPS modules alternately catch the load for each other in case of a failover.
c. Connect all equipment to the power paths (see tip below).

In normal operation, the load is evenly distributed across all 3 UPS modules.
In case of a failure of any of the UPS modules (but only one at a time), the load gets transferred (failover) to the other UPS modules.

Page 218
Distributed redundant UPS configuration (no STS)

As the quantity of single-corded loads in data centers today are becoming fewer and fewer, it is becoming more practical and less costly
to apply multiple, small, point of use transfer switches close to the single-corded loads. In cases with 100% dual-corded loads, this
configuration could be designed without STS units. This design is typically known as a tri-redundant and uses no static transfer switches.
Configuration:

1. Add UPS modules, PDUs, and racks to the floor layout as illustrated.
2. Add servers and rack PDUs to the racks.
3. Right-click the UPS modules one by one and select Properties>Power to set up redundancy feeds, all Distributed Redundant
.
4. Connect all equipment to the power paths (see tip below).

In normal operation, the load is evenly distributed across all 3 UPS modules.
In case of a failure of any of the UPS modules (but only one at a time), the load gets transferred (failover) to the other UPS modules.

Tip

Use different colors for the power paths to visually distinguish between them. (Right-click on the UPS, select Properties>Pow
er>Power Path Color.)

The Power overlay tool tips displaying when you hover over equipment in racks provide a visual overview of the load distribution and red
undancy settings.

See also

Configuring power connections

What does the power tool tip tell me
Redundancy definitions

Page 219
Working with breaker panels
In the breaker panel you can add breakers with an exact definition of position and capacity available. This enables you to map out and
track power connections within the PDU and to reduce stranded capacity. When correctly configured, the breaker panel provides an
easy overview of available circuits, breakers, and phases. This overview can be printed and displayed inside the physical panel.

Working with breaker panels includes the following procedures:

Configuring Breakers
Configuring PDUs
Configuring Breaker Panels
Connecting breakers
Printing Breaker Panel Schedules

Watch this video tutorial on how to model various types of breaker panels.

When everything is set up, you can conduct impact analysis on connected breakers. See here.

Configuring breakers

Standard models of breakers are available in the Genome Library with detailed information about space and phase requirements. Add
standard breakers from the Genome Library to your local genomes. Right-click the breaker in genomes to view and configure properties.

Modular breaker

Breaker Rating: The amount of power the breaker module is rated to

Module size: The number of positions the breaker module occupies in the panel
Power phases: The amount of phases connected to the breaker
Single: a single phase module has three single phase breakers and can be connected to three individual power
consumers
Phase to phase (L1-L2, L2-L3, L3-L1): a phase to phase module has a two phase breaker and can have one power
consumer (phase to phase modules are typically used in North America)
Three phase (L1-L2-L3): a three phase module can have one power consumer

Modular breaker

Page 220
Generic breaker

Breaker Rating: The amount of power the breaker is rated to

Pole count: The amount of phases connected to the breaker
Breaker size: The number of positions the breaker occupies on the rail

Generic breaker

Page 221
Configuring PDUs

You can configure power properties for the PDU in your local genomes or directly in the room layout.

Right-click the PDU and select Properties > Power to edit voltage outputs and voltage inputs. Note that the parameter for the output
is phase to phase voltage. If you have an input breaker in front of the PDU, you can specify the value here. If you specify the input
breaker, remember to also specify voltage input.

Configuration of a PDU in the room layout will define properties for that individual PDU. Adjustments made in room layout will not affect
the PDU in genomes.

In genomes the configurations will apply to the PDU model in general. Adjustments can be made individually to a PDU in room layout,
but only within the margins of the configurations you made in genomes. Adjustments made in genomes will not affect the PDUs already
placed in the room layout.

PDU power properties

Page 222
You can also add breaker panels to the PDU in genomes. The panels will be part of the configuration of the PDU. In genomes, right-click
the PDU and select Properties > Power > Breaker Panel. You can add and delete panels and in a generic panel, you can edit the cir
cuit numbers to match your setup. You cannot connect breakers from this view. To connect breakers, drag the PDU to the room layout,
right-click PDU and select Properties > Power > Breaker Panel > select panel name. More on connecting breakers here.

Add breaker panel in genomes

Page 223
Configuring breaker panels

Custom breaker panel layouts can be specified individually within the PDU. The process will vary from generic to modular breaker
panels.

Modular breaker panel

123 Steps to...

Configuring a modular breaker panel

Add a modular panel in the room layout. Right-click a PDU and select Properties>Power>Breaker Panel>Add panel.
Modular panels require minimum configuration. In the Breaker panel configuration dialog box, define Panel name, Panel size an
d Type - in this case Modular
If you have an input breaker on the panel, select Panel breaker and add the value.

Breaker panel configuration (modular)

Page 224
Generic Breaker Panel

If you have upgraded from a previous version of StruxureWare Data Center Operation, you will have placeholder panels and need to
reorganize, see here. If you are setting up a generic panel, see below.

123 Steps to...

Configuring a generic breaker panel

Add a generic panel in the room layout. Right-click a PDU and select Properties > power > add panel.
Name the panel, set size and choose type.
If you have an input breaker on the panel, select Panel breaker and add the value.
In Layout in the Breaker panel configuration dialog box, you have different options:
Start value: If you have more than one breaker panel in a PDU, it can be useful to give them different start values. For
example one panel has circuit numbers 1-24 and the next panel starts at circuit number 25 that would be the start value for
that panel.
Phase grouping: If you have one circuit number covering three phases, choose phase grouping.
Distribute poles on two rails: Choose how to organize your breakers on the rails:
odd/even - odd numbers in the left rail and even numbers on the right
sequential - sequential numbering beginning in the left rail ending in the right rail

Breaker panel configuration (generic)

Page 225
Custom Breaker Panels

You can block out positions and edit circuit numbers to create a custom breaker panel.

123 Steps to...

Creating a custom breaker panel

In Genomes, right-click a PDU and select Properties > Power > Breaker Panel
Double-click the circuit number of generic panels to change it
If you delete a circuit number, that position will be blocked out

Creating a custom panel

Page 226
Connecting Breakers

Before connecting breakers to the breaker panel, you need to add breaker modules or breakers to your local genomes from the Genom
e Library.

123 Steps to...

Connect breakers

Right-click a PDU and select Properties > Power > Breaker Panel to open the Properties dialog box
Choose the desired panel by clicking the panel name
The Selected panel details are now visible
Click a cell in the Breaker column and choose a beaker module or breaker in the drop-down menu
Choose a Power Consumer to each breaker to map out breaker connections
Note: Breaker modules or breakers that take up multiple positions will automatically block the cell below it

Tip

Tip: You can take a picture of your breaker panel in your data center to help your memory when you map your connections.

Breaker panel

Page 227
A picture from your data center can help map connections

Page 228
Printing Breaker Panel Schedules

Manage occupied and free breaker positions on each breaker panel for an easy overview of available
breakers, circuit numbers and available phases that can be printed out to display inside the physical
breaker panel.
To print breaker panel schedules, right-click the PDU and select Reports >Panel Schedule >print.

For the Co-lo version, the tenant name will be added to the printed breaker panel schedule.

See also

Reorganizing breaker panels after upgrade

Page 229
Reorganizing breaker panels after upgrade
If you have upgraded your installation, you may need to reorganize the breaker panels. This applies specifically to generic PDUs
whereas modular PDUs, if correctly configured prior to the upgrade, require minimum configuration.

On this page:

Generic PDU
Reorganizing Breaker Panels
Modular PDU

Generic PDU

When you upgrade from a version prior to 7.4, the breakers will be placed randomly in a placeholder panel. The placeholder panel is a
temporary panel and it does not resemble the actual positions of the breakers. To get the benefits of the visual breaker panel, it is
important that you reorganize each breaker into the correct position in a new Breaker Panel. This can be done by right-clicking the PDU
and selecting Reorganizing Breaker Panel.

Watch this video tutorial on how to model various types of breaker panels in StruxureWare Data Center Operation 7.4 (Generic and
custom breaker panels are at 3:45).

Reorganizing Breaker Panels

1. Right-click a PDU and select Reorganizing Breaker Panels.

2. If you have already created a panel, you can find it in the drop-down menu in Destination Panel or create and name a new
panel.
3. Move breakers to the destination panel.
a. To place a breaker in the selected panel, click the desired cell in the panel and select a breaker. Only breakers with
matching phases will appear in the drop-down menu. You can toggle this display limitation by using the Strict phase
matching check box in the top left corner.

Reorganizing breaker panel

Modular PDU

If the PDU is correctly configured prior to the upgrade, the breaker modules should automatically be placed in the right positions, but it is
important that you verify.

Tip

Before you upgrade make sure that the modular PDU is correctly configured (model name and module numbers). Download
the PDU Webmin plugin to identify configuration issues with modular PDUs before the upgrade. Download and use of the
Webmin plugin is described here.

Modular breaker panel

Page 230
For more information on configuring modular and generic PDUs, see here.

See also

Working with breaker panels

Page 231
Power redundancy

Definition

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.

Distributed Redundant UPS systems is a redundancy setup with three or more UPS where one serves as backup for the others in
case one of them fails. There are 3 types of design and you can learn more here.

Distribution Redundancy is a type of redundancy setup in which the power distribution, not the power source, is redundant, using
multiple rack PDUs. Distribution redundancy does not provide as much security as the full redundancy setup at power source level
(Distributed Redundant UPS systems), 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 text below.

Redundancy types
You may come across these terms in connection with power redundancy in the system:

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.
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.
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. *In this
case, distribution redundancy is referring to rack PDU redundancy, not UPS level redundancy.
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).

See also

Cooling Redundancy

Configuring distributed redundant UPS systems

Page 232
Page 233
Power dependency description
The Power Dependency table shows details about power equipment in your data center infrastructure. You can right-click an item (row)
to identify it in the layout or navigation, or to open its Properties.

For a better and more graphical overview of your power dependencies, it is recommended to use the Power Path Layout.

Column Description

Item Power equipment items and where they fit in the power path (indention and expandable arrows).

Location Location of the power equipment items in the modeled data center infrastructure.

Phase Phase to which the selected equipment is connected.

Outlet Outlet to which the selected equipment is connected, shown only if rack PDU has power outlets definition.

Breaker module Breaker module number (can also be found in Properties>Power>Breaker Panel).
number

UPS used capacity Power used by equipment connected to this UPS for power.

UPS reserved Power reserved by equipment connected to this UPS for power.
capacity

Distribution Relevant for distribution units, such as PDUs, RDPs, and Power Panels. UPS power reserved by this
reserved capacity of distribution unit (in %).
UPS size

Distribution Relevant for distribution units, such as PDUs, RDPs, and Power Panels. UPS power reserved by this
reserved UPS distribution unit.
capacity

Distribution Relevant for distribution units, such as PDUs, RDPs, and Power Panels. Estimated load of equipment
estimated load connected to this distribution unit for power. In redundancy configurations, this value will include potential
failover load.

Distribution Relevant for distribution units, such as PDUs, RDPs, and Power Panels. Remaining power available on this
unreserved capacity distribution unit (total power available minus the load of connected equipment).

Rack remaining Relevant if you group racks with similar power requirements (capacity groups). Remaining power available in
power each rack connected to this distribution unit for power.

Rack maximum Relevant if you group racks with similar power requirements (capacity groups). The maximum load you can add
capacity to each rack connected to this distribution unit for power.

Page 234
Voltage supported in Data Center Operation
In Data Center Operation two types of voltage are specified:

Three phase voltage indicates the power supply to/from the equipment contains all three phases. The voltage specified is voltage
between two of the available phases. For example, a power distribution unit can supply all three power phases.

Single phase voltage are used by most power consumers, and for equipment that only supplies power on a single pair of lines/cables.
The voltage specified is the voltage between the two the lines. This can be a phase-to-neutral and a phase-to-phase pair. For example,
a server should be supplied with a single phase.

Voltage supported in Data Center Operation

AC

Three phase: 100V, 200V, 208V, 380V, 400V, 415V, 480V, 600V
Three phase (Scott transformed): 200V/100V, 208V/104V, 210V/105V, 220V/110V, 230V/115V
Single phase (both phase-to-neutral and phase-to-phase): 58V, 100V, 104V, 105V, 110V, 115V, 120V, 200V, 208V, 210V,
220V, 230V, 240V, 277V, 347V

DC

You can specify the voltage used in your data center.

Page 235
Configuring blade solutions
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.
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 genome library installed with the application contains the most commonly used blade products. You can configure any
additional blades and blade enclosures that you use, setting the number of bays and bay height and width (in any combination).

123 Steps to...

Adding blade equipment to the rack layoutThe 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.Before adding blade equipment to the layout, select Pl
anning > Data Center in the Application bar and select to view a room in Rack Layout, for example by double-clicking a rack in the F
loor Layout.

1. Drag the blade enclosure icon into the position in the rack layout that matches its position in the data center.
2. 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

Tip: You can move or delete multiple items at the same time by using Ctrl-click or Shift-click.

4. Right-click the component icon and select Properties to e.g. define a custom name for it, or to use other menu options.

See also

Valid blade configuration

Configuring equipment not available in the genome library

Page 236
Valid blade configuration
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.

Supported Any combination of full / half height with double / single width blades.
configurations

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

Product family 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.

Page 237
Configuring cooling
The graphical floor plan of the configured data center layout includes overlays showing capture index (CI), plenum pressure, plenum
velocities, and 3D rendering of the temperature map, including airflow, temperature thresholds, load. These overlays give 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.

Watch this video tutorial to learn how to configure different types of cooling.

Capture index

The Cooling overlay 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 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.

Plenum velocities

Subsequently, you can use the Floor Plenum overlay 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.

Plenum pressure

For data center layouts with raised floor environments, you can use the Floor Plenum Pressure overlay to drill down into looking at
specific pressure issues in the plenum.

3D temperature map

In the 3D view, you can see the room's airflow above the raised floor. Velocity vector and temperature results look like those from

Page 238
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 Calculate to show the updated view.
Subsequently, you can select File>Export and export to .xml or export directly to .pdml without using conversion tools.

See also

Working with Capture Index

Working with plenum velocities
Working with the 3D temperature map
Cooling Configuration Accuracy and Design Guidelines

Page 239
Row-based or room-based cooling
Row-based cooling

Cooling is distributed through InRow® cooling units placed in the rows close to the heat generating equipment in an equipment cluster.

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.

See also

Configuring cooling

Page 240
Working with Capture Index
The cooling simulation tool enables you to simulate the effect of potential changes to the cooling conditions.
You can view the data center temperature map in a 2D floor layout with various views.

In the Cooling overlay of the data center floor layout, you can see a color-coded overview the Capture Index (CI). You can use this view
to get an overview of the reasons 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.
Subsequently, you can use the plenum overlays to drill down into looking at specific pressure or velocity issues in the plenum.

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.

Select the Cooling tab in the floor layout.

1. Add CRACs, InRow® cooling units and perforated tiles as needed by dragging them from the Genomes pane into the layout.
2. Review or modify the cooling settings of the added equipment or the room as needed by right-clicking the item, and selecting Pr
operties, and using the settings in the Cooling page.
3. Simulate failure of one or more cooling units by selecting one or more cooling units in the floor layout, right-clicking, and
deselecting Activate.
4. 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

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.

*Value defined in the Rack's cooling properties page.

See also

Configuring cooling
Working with plenum velocities

Page 241
About the Capture Index (CI) colors
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").
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 20°C 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.

Capture Index (CI) color

See also

Configuring cooling
About Capture Index prediction models

Page 242
About Capture Index prediction models

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.

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.

See also

Configuring cooling
About the Capture Index (CI) colors

Page 243
Troubleshooting why Capture Index values do not display

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.

See also

Working with Capture Index

Page 244
Designs with perforated tiles on a raised floor
"Perforated tiles on a raised floor often deliver substantially more or less airflow than expected, resulting in inefficiencies and even
equipment failure due to inadequate cooling. In this paper, the impact of data center design parameters on perforated tile airflow is
quantified and methods of improving airflow uniformity are discussed."

Source: Airflow Uniformity through Perforated Tiles in a Raised-Floor Data Center (White Paper 121)

Read the full White Paper here.

See also

Configuring cooling
Working with plenum velocities
Working with plenum pressure

Page 245
Working with plenum velocities
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. The color coding
of tile(s) is done based on how airflow is divided between the tiles relative to each other. The tile(s) with the lowest airflow is blue. The
tile(s) with highest airflow is painted red. The tile(s) in the middle in terms of airflow is green.

You can relate the plenum velocities to the length or color of the arrows by changing the settings in Tools>Preferences>Plenum
Velocities.

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 Proper
ties>Floor.

You can add two types of perforated tiles (25% and 56% open area) to the layout from the Genomes pane.

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.

See also

Configuring cooling

Page 246
Working with plenum pressure
The Floor Plenum Pressure overlay of the data center floor layout shows a color-coded overview of the pressure distribution.

This is an advanced and specific view of the plenum for the type of data center layout that includes a raised floor environment,
perforated tiles, and downflow CRACs. Unlike the Cooling overlay, the plenum overlays only consider room-based cooling.

Note

Row-based cooling units, racks and other heat generating equipment are not taken into account in these calculations.

The color scale represents the various pressure differences between the air above and below the raised floor. The numbers in the
pressure scale automatically adjust to include the values in the data center layout.

You can use this overlay to get an overview of the positions in the floor layout that are eligible for positioning the perforated tiles based
on your insight into the plenum pressure. When you add tiles to the floor layout, you can use this insight to position perforated tiles
where the pressure is high and preferably not too close to a downflow CRAC.

See also

Designs with perforated tiles on a raised floor

Working with plenum velocities
Row-based or room-based cooling

Page 247
Working with the 3D temperature map
You can review the data center temperature map in 3D as a calculated or measured map.

The calculated map provides an estimate based on the maximum load servers would have (nameplate).

The measured map is more accurate because it has more detailed data available. It is based on real sensor readings retrieved through
discovered devices rather than estimates.

Tip

Room size limitation: The 3D temperature map currently does not support rooms bigger than 70x100 m.

Unsupported configurations: Deactivating a cooling unit does not affect the airflow in 3D as this is currently not supported. You
can omit the airflow of a cooling unit in 3D with these workarounds.

Follow the below steps or watch this video tutorial to see how to configure the temperature map.

Configuring temperature map based on real sensor readings

1. Retrieve live values from the sensors in the data center.

a. Configure external system integration with a system that provides real temperature measurements. See more here.
b. In Planning>Device Association, discover and associate devices. See more here.
2. Position the sensors in the correct locations in the model.
a. In the Association map overlay, map each temperature sensor to the correct physical location (devices, racks, or
rooms) using drag'n'drop.
For example, drag an InRow CRAC upper plenum exhaust temperature sensor to the upper position in the rear of the
CRAC.
b. Specify a precise location in a rack.
i. Right-click the rack that contains the sensor and select Properties>Device Sensor.
ii. Use the X, Y, Z % fields to define the location expressed as a percentage on the axes, starting with 0%, 0%,
0% in the lower left corner.
3. Calculate the 3D temperature map.
a. Open the 3D view to preview the sensors in the correct locations.
b. In Cooling plane type, select Measured plane and click Calculate.

Tip

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 Calculate to regenerate 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.

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.

Page 248
Measured cooling plane quality
A rack can get the inlet temperature by any of these methods:

Manual measured temperature (on rack properties)

Servers associated with external system integration

The outlet temperature on the rack (the derived temperature) can be calculated based on the load on the server/rack and the inlet
temperature.

If the Only measured setting is enabled, only actual measurements from other systems or manually entered measurements will be
included.

If the Measured and derived setting is enabled, the derived temperatures will also be included in the temperature map.

To enable or disable Measured and derived setting go to Preferences > Temperature Map > Measured cooling plane quality.

Enable or disable derived setting

See also

Configuring cooling
Customizing 3D Colors and Thresholds
Troubleshooting inaccurate 3D calculations

Page 249
Customizing 3D Colors and Thresholds
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

Tip: 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>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.

Page 250
Color:

Length:

See also

Working with the 3D temperature map

Page 251
Troubleshooting inaccurate 3D calculations

You may experience unexpected calculations in your 3D layout due to specific configurations not currently supported in 3D.

If your solution includes deactivated cooling units for failure simulation, the decrease in cooling capacity is not reflected in 3D as this is
currently not supported.

Workaround

You can omit the airflow of a cooling unit in 3D in one of these ways:

Change the airflow and cooling capacity of the cooling unit to 0 (by right-clicking and selecting Properties; remember to note
the value first to be able to restore it after the failure simulation)
Moving the cooling unit outside the room
Deleting the cooling unit (not recommended unless you are working with a test setup and perform a backup first)

See also

Working with the 3D temperature map

Troubleshooting

Page 252
Exporting Cooling Data to 3rd Party Applications
If you want to export cooling data from StruxureWare Data Center Operation and use it in other applications, you can use the export
options.

In File>Export, select the type of data to export and export it to your local or network drive.

Export types and formats

Temperature map in Comma Separated Values file format

Plenum airflows in Comma Separated Values file format
Computational Fluid Dynamics model in (APC by Schneider Electric, open) xml file format
Computational Fluid Dynamics model in (FloVENT) PDML file format

See also

Configuring cooling

Page 253
Cooling Redundancy
In StruxureWare Data Center Operation, 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

Page 254
Cooling Configuration Accuracy and Design Guidelines

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.

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

Note

If you flip a row to face front to back, it affects the cooling simulation for up to 3 rows.

Cooler airflow specifications

Cooler airflow in cubic feet per minute (CFM) is assumed to be:

Cooler type Minimum CFM Maximum CFM

InRow RC (300 mm) 1450 2900

InRow RC (600 mm) 2760 6900

InRow RP (600 mm Chilled Water) 2760 6900

InRow RP (600 mm Air Cooled) 1920 4800

InRow RD (600 mm Air Cooled) 2000 5000

InRow RD (300 mm Air Cooled) 916 2300

InRow RD (300 mm Fluid Cooled) 916 2300

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
Working with Capture Index

Page 255
About Capture Index prediction models
About the Capture Index (CI) colors

Page 256
Optimizing the Cooling Configuration Accuracy by Adjusting Power and Cooling Estimates
Since StruxureWare Data Center Operation 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.

Server load estimates

In StruxureWare Data Center Operation, every server in the data center has two power estimates.
By 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. StruxureWare Data Center Operation uses this
value as the reference value.
Estimated Load: Identifies the estimated load of the selected server. StruxureWare Data Center Operation 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.

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

Page 257
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
Cooling Configuration Accuracy and Design Guidelines

Page 258
Tips and tricks for configuring cooling
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.

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

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.

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 Floor Plenum view and in the 3D Velocity plane. The
different velocities will be represented as arrows of a certain length or color.

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.

Duct-to-ceiling

When using the duct-to-ceiling feature please make sure that you balance the airflow. The amount of airflow coming from the ducted
racks should be similar to the amount of airflow to the ducted cooling units. If there is a large unbalance the air will leak in or out from the
ceiling. This is handled by the cooling calculator, but the results can be difficult to interpret.

One indication that the calculations encounter an under-pressure in the ducted ceiling is that the Cooling Load on the cooling units is
very low.

See also

Configuring cooling

Page 259
Designs with CRAC Units Placed Outside the Room
Starting from version 7.4 StruxureWare Data Center Operation allows modeling of ceiling tiles, downflow CRAC units with air duct to
ceiling plenum and cooling units placed outside a room.
1. Add CRAC units by dragging them from the Genomes pane into the layout. Place them outside the room, but touching room
walls.
2. Enable Duct to ceiling by right-clicking the item, and selecting Properties, and using the settings in the Cooling page.
3. Configure room to use Drop ceiling.
4. Drag ceiling tiles from the Genomes pane into the layout. Add at least one ceiling tile for each CRAC unit. Place these tiles
touching the same wall as CRAC unit.

See also

Configuring cooling
Working with plenum velocities
Designs with perforated tiles on a raised floor

Page 260
Managing network configurations
The graphical overview of network connections offers easy management and identification of your cables through naming and
color-coding. Define color and usage for your cables in Configure Network Cable Types - see here.

The Network Management table lists the configured network connections and allows you to set up new network routes between the
configured equipment.

The Rack Layout provides a graphical overview of the configured network connections and allows you to set up new network routes by
clicking and dragging cables between equipment.

The network routes will be visible when you click a piece of equipment in the rack layout. Hover over the cables to see the path of the
connection or click the cable to see the route data in the table view.

Every network management change is recorded in audit trail report.

The Network Cable Browser lists cables for the loaded rooms. Cables in rooms that have not been opened will not be included or
displayed in gray.

You can multi-edit in this browser just as you can in the Equipment Browser, e.g. change cable type for all cables in a route by
multi-selecting the rows in the browser, right-clicking and selecting Edit Multiple Items.

Graphical network overview in rack and Network Management

Network Cable Browser

Page 261
Configuring network connections in rack view
The rack view offers a visual representation of the cable route from e.g. server to switch.

Select a piece of equipment with network properties in the floor layout and click

in the rack view toolbar to show connected and available ports. Connected ports are green and available ports are gray. Click a piece of
network equipment to show existing connections or to create new ones. If for example a patch panel has connections to equipment
outside the rack, the cables will be placed at the top of the rack. Right-click the cables and select Show Route to see all the connected
equipment in rack view. This only applies to equipment in the same room.

Use Ctrl-click to select, show and connect multiple items in rack view. Connections from room to room must be written in the table view.

Follow the instructions to configure network connections below.

123 Steps to...

Creating network connections

Make sure that the
1. Click show network cable type matches
. the connection
2. Use the connection tool
to click on the source then the destination of the network connection.
3. Connected ports are green and if there are no available ports of the correct type, a small stop sign will
appear next to the pointer. It is not possible to make connections between different port types (e.g. fiber to
RJ45).

Tip

Tip: To make a connection from for example front to rear, you can rotate the equipment in rack
view using the top left rotate icon
.

The New Network Connection dialog box opens automatically when you have chosen your destination.
4. Select one of the defined cable types. The cable types available in the dialog box are the ones defined by
you. See configuration of cable types here.
Note: Make sure that your cable type matches the configuration. The client will not recognize it if your
definition does not match the cables in the configuration.
5. Select port.
6. Select Multiple connections to make several connections at a time.

Tip

Tip: You can print the graphical network routes and bring them to your data center. Select the desired
piece of equipment in floor layout. Click Export Layout as Image in the floor layout toolbar and
select Rack layout > Current > Next > Image format > File > Finish.

Page 262
Configuring network connections in table view
The table view will be populated with network route data when you select a piece of equipment with configured network in the layout or N
avigation. 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 N
avigation.

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.

Follow the below instructions or watch this

video tutorial to learn how to configure network routes.

123 Steps to...

Configuring network routesYou 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.
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.

1. Select a piece of equipment with network configured in the layout, e.g. a server in the rack layout.
2. In the Network Management pane, click the row with the port that you want to configure in the list.
3. Place the cursor in the Route column and from the list, select a symbol, and press Enter.
4. From the list, select the equipment that you want to connect to, and press Enter.
Remember to enter the port number.
5. 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.

Recommendation

Configure the patch panel back connections prior to configuring the rest of the network route.

See also

Configuring Network Connections in Rack View

Managing network configurations

Page 263
Configuring network ports
You can configure network port properties for network equipment in Genomes.

1. Open the Genomes pane.

2. Select a piece of network equipment.
3. Click on the Network pane in the Properties section and perform the edits for the component in Genomes.
a. Click Add or Edit.
b. Select the type, port range (first port and the amount of ports in the range), and the network speed if relevant.
c. Repeat the above two steps for all port ranges needed. For example, a switch could be configured like this

Type Start (First port in range) Count (Amount of ports)

RJ45 1 16

RJ45 17 16

RJ45 33 16

Fiber Uplink 1 4

The configured properties will apply to all pieces of this equipment added to the layout subsequently.

Tip

Tip: To change the properties for one specific component only rather than the product type in Genomes, right-click the
component in the layout. The same options are available but they will only apply to the one component.

Page 264
Configuring network cable types
You can define color and usage (description) for your cables to easier trace and visualize the routes of your network connections. You
must have user rights to configure network cables (Genome Library and Network Cable Types in System Setup>User Rights and
Authentication).

If you have upgraded from a version prior to 7.4, all your existing connections will be gray and must be configured as well.

1. Go to Tools>Configure Network Cable Types.

2. Click Add and define a color and a description for your cable.
These do not depend on the physical cable type in hand but if you want your graphical overview to resemble what you see in
your data center, define your cables to resemble their physical appearance.

Note: You must configure each existing cable individually as there is no link between the cable and the Configure Network Cable
Types dialog box once the cable has been defined, saved and added to the room layout. So if you define color and usage for a fiber
cable, this configuration will not affect the color and description of any fiber cables already in the room layout.

Page 265
Network configuration example
Simplified example of a network setup with 3 network routes.These partial network routes were configured:

Server A <-> Switch A

Switch A <-> Switch B
Server B <-> Switch B

Selected equipment in layout Network route in Network Management pane Route color in example

Server B >Patch Panel 1:6->A/RackB/Patch Panel 2:6>Switch B:10 Blue

Server A >Switch A:13 Orange

Switch B >Patch Panel 2:1->A/RackC/Patch Panel 1:1>Server B Blue

Switch B >Patch Panel 3:1->A/RackA/PatchPanel 4:1>Switch A:12 Green

Switch A >Server A Orange

Switch A >Patch Panel 4:2->A/RackB/PatchPanel 3:4>Switch B:22 Green

Patch Panel 3 >Switch B:23 Green

Patch Panel 3 ->A/RackA/Patch Panel 4:5>Switch A:7 Green

Page 266
Route notation in network management
The system has built-in content assistance to guide you when setting up network routes.

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.

Notation Description

> Network gear in this rack

-> Racks in this room and/or all rooms

: Port specification

/ Location separator (room/row/rack)

Page 267
Network properties
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.

Network ports

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

Description Provides user-defined information.

Start Identifies the first port in the port range.

Count Identifies the amount of ports in the port range.

Speed Provides information about the network speed.

Connections (available if the dialog box is accessed by right-clicking a component in the rack layout that has routes defined)

Port Identifies the port number.

Type Identifies the port type.

Connected to Identifies the network route between the start and end items.

Description Provides user-defined information.

IP Address Identifies the IP Address.

Page 268
Network Summary report
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).

The Tag filter options are available if you have StruxureWare Data Center Operation: Capacity.

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

Page 269
Working with the List View
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.
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.

123 Steps to...

Filtering List View (Search)

You can set a filter on the List View to show only the equipment you want to see.

In the Search... field of a column, start typing some characters of the equipment you want to see.
As you type, the table shows all items that contain the typed characters.

See also

Editing multiple items in List View

Exporting List View table
Monitoring operations in Map View
Working with the room layout
Working with the 3D temperature map

Page 270
Editing multiple items in List View
You can edit multiple items at the same time in the List View by using the Edit Multiple Items dialog box.

1. In List View, select the items you want to edit

2. Click the Edit Multiple Items icon or right-click and select the context menu item

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

Page 271
Exporting List View table
You can export the list of equipment to a file.

1. Click the export icon to open the Export dialog box

.
2. 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.
a. 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

Page 272
Working with the Power Path Layout
The Power Path Layout shows a graphical overview of the power connections from UPS units to racks. Equipment with the same power
path will be displayed in a group.
Move equipment by dragging and dropping single pieces or groups of equipment or use the Marquee select tool to multi-select and
move equipment.

In solutions where e.g. a PDU is connected to a UPS in another room, the UPS will appear transparent in the layout. To make the UPS
appear solid click

You can configure equipment through the properties dialog box as in the floor layout. To access properties on grouped equipment click
the group in the layout and link view with selected equipment in the equipment browser. You can filter the content of the equipment
browser according to your preferences.

To reset layout to default layout click

. Note: this will reset changes to the graphical layout, not changes made in the properties dialog box.

See also

Working with the Equipment Browser

Configuring power connections

Page 273
Working with the Equipment Browser
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 and filter setup.

When working with future changes (StruxureWare Data Center Operation: Change feature), items marked with pending changes appear
in light gray.

123 Steps to...

Showing selected equipment in Equipment Browser

You can use the link functionality to filter the content of the Equipment Browser and only display selected equipment.

1. Click the Link view with selected equipment icon to enable this feature
.
2. Select equipment in Layout or Navigation pane that you want to see in the Equipment Browser.
3. Click the Link view with selected equipment icon again to disable this feature
.
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.

See also

Filtering and finding equipment in Equipment Browser

Exporting Equipment Browser table
Editing multiple items in the Equipment Browser
Configuring Equipment Browser layout
Working with the List View

Page 274
Editing multiple items in the Equipment Browser
You can edit multiple items at the same time in the Equipment Browser by using the Edit Multiple Items dialog box.

1. In Equipment Browser select the items you want to edit

2. Click the Edit Multiple Items icon or right-click and select the context menu item

3. In the Edit Multiple Items dialog box, select a column to edit, and identify the new value to apply to the selection.

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 Show in Layout.

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
Filtering and finding equipment in Equipment Browser
Exporting Equipment Browser table
Configuring Equipment Browser layout

Page 275
Filtering and finding equipment in Equipment Browser
You can set a filter on the Equipment Browser to show only the equipment you want to see.

In the Search box above the table, start typing some characters of the equipment you want to see.
As you type, the table shows all items that contain the typed characters in the entire table.

In the Search... field of any column, start typing some characters of the equipment you want to see.
As you type, the table shows all items that contain the typed characters in the selected column.

You can use Boolean operators AND, NOT and OR in the search field to further refine your search.

Examples:

AND, NOT, OR

'

Rack NOT Rack-

Page 276
 See also

Working with the Equipment Browser

Editing multiple items in the Equipment Browser
Showing selected equipment in Equipment Browser
Exporting Equipment Browser table
Configuring Equipment Browser layout

Page 277
Exporting Equipment Browser table
You can export the list of equipment to a file.

1. Click the export icon to open the Export dialog box

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

Info

CSV file exported in UTF-8 format with fields delimited by semicolon. Refer to Microsoft Office documentation for importing
options of CSV files.

See also

Working with the Equipment Browser

Editing multiple items in the Equipment Browser
Showing selected equipment in Equipment Browser
Filtering and finding equipment in Equipment Browser
Configuring Equipment Browser layout

Page 278
Configuring Equipment Browser layout
You can configure the layout of the Equipment Browser to show equipment according to your preferences.

Select which columns to show from the dialog box opened by clicking Configure columns

Edit the column width:

1. Drag the boundary of a column header to the required position
2. 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
Filtering and finding equipment in Equipment Browser
Exporting Equipment Browser table

Page 279
Creating predefined table configurations
The table layouts in Discovered Devices, List View, Network Browser, and Equipment Browser initially display the default table
configuration.

For the Equipment Browser, these built-in standard configurations are also available:

Power
Colo (Colo version)

You can create and save your own predefined table configurations and toggle between configurations suited for different purposes.

1. Click the arrow next to the Configure Columns icon above the table.
2. Select Add new configuration.
3. Name your configuration and select which columns to show.

Configurations are saved per DCO client.

Adjusting the table layout according to your preferences

Edit the column width:

1. Drag the boundary of a column header to the required position.
2. Double-click the boundary of a column header to make the column width fit to contents.
Drag and drop columns in the table to move columns.
Click a column header in the table to sort on this column.
Click a column header in the table to toggle sort order (ascending/descending).

See also

Working with the Equipment Browser

Working with the List View

Page 280
Editing IP address through the Equipment Browser
You can edit IP address for multiple servers directly through the Equipment Browser.

1. Add the IP Address column to the Equipment Browser:

Click the Configure columns icon

, and select IP Address.

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

Page 281
Properties description
This page describes the asset properties available in StruxureWare Data Center Operation.

When working with the equipment browser, you have the option to specify which columns are shown in the equipment browser (Configu
re columns

). The dialog box used for specifying columns displays a number of properties along with a description. This page adds to these
descriptions.

Property Description Can be found in... Optional/Auto License

entered

Account No Customer specific information Customer Properties Customer data Co-lo

integration

Area (m2) Area occupied by rack or cage Physical Properties Calculated by DCO Co-lo
(rack)

Available Power Outlets The amount of available power outlets on rack PDUs in the rack. The amount Power Properties Calculated by DCO Capacity
of power outlets is set in rack PDU Power Properties.

The system subtracts the amount of configured power connections.

Average CPU Utilization Average CPU utilization seen at device discovered by external system over IT Optimize tooltip ITO integration IT Optimize
(%) the last 30 days

Average Inlet Average inlet temperature seen at device discovered by external system - ITO integration IT Optimize
Temperature

Average Power Average power utilization seen at device discovered by external system over IT Optimize tooltip ITO integration IT Optimize
Utilization (W) the last 30 days

Barcode The asset's barcode. Must be unique General Properties Optional Operation

Bay count The amount of bays in a blade or modular switch enclosure Physical Properties Genome Library Operation
(Genomes)

Bay type The bay type (half or full) of a blade or modular switch component Physical Properties Genome Library Operation
(Genomes)

Cluster Cluster information provided by discovered VMware system External Systems VMware integration Capacity
Properties (read)

Company Customer specific information Customer Properties Customer data Co-lo

integration

Connection State Defines if the device is online, offline, or not responding. External Systems DCE integration / Operation /
Properties (read) ITO IT Optimize

Contact Customer specific information Customer Properties Customer data Co-lo

(read) integration

CPU Type The asset's CPU data External Systems ITO integration IT Optimize
Properties (read)

Description A description of the equipment General Properties Pre-entered Operation

Device description Description of device transferred from DCE server DCE server DCE integration Operation

Device IP Address IP address of device discovered by external system External Systems DCE integration / Operation /
Properties (read) ITO IT Optimize

Device Location Location of device transferred from DCE server DCE server DCE integration Operation

Device Manufacturer Manufacturer of the discovered device reported from the device. External Systems ITO integration IT Optimize
Properties (read)

Device Model Name Model of device discovered by external system External Systems DCE integration / Operation /
Properties (read) ITO IT Optimize

Device Name Name of device transferred from DCE server DCE server DCE integration Operation

Discovery Protocols The protocols used to discover the device - ITO integration IT Optimize

Discovery Time The first time the device was discovered External Systems ITO integration IT Optimize
Properties (read)

Estimated Load (W) or The actual maximum power consumption of the asset Power Properties Pre-entered Operation
Adjusted Nameplate

Floor Coordinates Coordinates on floor based on sequence or customization Floor Properties Optional Operation

Group Name of group in which device is located in DCE DCE server DCE integration Operation

Hostnames Hostname of device discovered by external system External Systems DCE integration / Operation /
Properties (read) ITO IT Optimize

Idle Power (W) Power draw of device when inactive - ITO integration IT Optimize

Installation Date Date where asset is installed General properties Auto entered when Operation
asset is added

IP Address IP address of device Network Optional Operation

properties/Network
Management

Last Poll Time When was the device discovered by external system poll last time - ITO integration IT Optimize

Page 282
Location Location of device General properties DCO Operation
(read)

Manufacturer Manufacturer of asset. General properties Genome library Operation

Manufacturer's The default nameplate value of a asset Power properties Genome library Operation
Nameplate (W)

Max Power (W) The maximum power usage of the device. Data coming from verified power Power properties (read) ITO integration IT Optimize
profile in Genome.

Max Power Ports Total number of power outlets in rack. A summation of power outlets on rack Power properties Calculated by DCO Operation
mount PDUs in a rack.

Model Name Model of device General properties Genome library Operation

Module Type The type (single or double) of a blade or switch module Physical Properties Genome Library Operation
(Genomes)

Name Name of device, could be used for more telling names than model name General properties Optional Operation

Operating Systems Operating system of device discovered by external system External Systems ITO integration IT Optimize
properties (read)

Parent System The type of external system from which StruxureWare Data Center Operation External Systems External system Operation
is retrieving device/asset data. properties (read)

Part Number Part number of device General properties Genome Library Operation

Peak CPU Utilization (%) Maximum CPU utilization seen at device discovered by external system over - ITO integration IT Optimize
the last 30 days

Peak Inlet Temperature Maximum inlet temperature seen at device discovered by external system - ITO integration IT Optimize

Peak Power Utilization Maximum power utilization seen at device discovered by external system over - ITO integration IT Optimize
(W) the last 30 days

Phone Number Customer specific information Customer properties Customer data Co-lo
(read) integration

Port Description The entered descriptions of the network equipment's port configurations Network Optional Operation
Properties/Network
Management

Power Profile Power profile being used External Systems ITO integration IT Optimize
properties (read)

Power Profile Enabled Once device is discovered by IT Optimize server the power estimated load is Power properties ITO integration IT Optimize
taken from the power profile

Power Sold (kW) Customer specific information Customer properties Optional Co-lo

Product Family The product family of a blade or modular switch component Physical Properties Genome Library Operation
(Genomes)

Rack The name of the rack, or the name of the rack in which the equipment is General properties Optional Operation
located.

Redundancy The redundancy option of the equipment Power properties Manuel entered Capacity

Room The room in which the equipment is located. General properties Manual entered Operation

Row The row in which the equipment is located. General properties Auto entered when Operation
row is added

Serial Number Serial number of device discovered by external system External Systems DCE integration / Operation /
properties (read) ITO IT Optimize

Server Access Enabled Server access enabled on device Server Access ITO integration Server
Properties Access

Stage Equipment is Existing by default. Planning stages, such as Pending Move will Work order Auto entered by Change
be seen if change module being used system

State State of device discovered by external system External Systems DCE integration / Operation /
properties (read) ITO IT Optimize

Supports Power Capping The device supports the power capping functionality Configure Power ITO integration IT Power
Capping menu on rack Control

Supports Remote Remote console supported by device Server Access ITO integration Server
Console Properties Access

Type Type of device discovered by external system External Systems DCE integration / Operation /
properties (read) ITO IT Optimize

U-Height The amount of U-positions occupied by the equipment Physical properties Genome Library Operation
(Genomes)

U-Position The U-Position where equipment is located General Properties Genome Library Operation
(read)

Virtual Machines and Specifying virtual machines and templates of discovered VMware system External Systems VMware integration Capacity
Templates properties (read)

Weight The equipment's physical weight Physical properties Genome Library Operation

Zero-based numbering Enclosure's bay numbering starts from 0 Physical properties Genome Library Operation

<Custom property> Customer specified property. Properties (Custom) Optional Operation

Tags Contains a list of names of tags Tags properties Optional Capacity

Tag <#> Shows a given tag <#> Tags properties Optional Capacity

Page 283
Internal breaker derating Rack PDUs internal breaker derating Power properties Manuel entered Capacity

U-Positions from bottom Rack U-Positions counted from bottom to top Physical properties Genome Library Operation

U-Positions from 0 Rack U-Positions counted from 0 Physical properties Genome Library Operation

Page 284
Working with Asset Provisioning
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.In the Planning>Asset Provisioning perspective, use the Installation Requirements p
ane together with the Provisioning Map view of the room and Provisioning Match view (available as tab 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 Genomes or move from Na
vigation or a layout position.

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, and power paths.

When you use the Add Asset 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, tag associations, rack PDU plug types*, load
balancing on the different phases, weight, and available network ports.

Color-coded messages in the Provisioning Match pane guide you in finding the optimum location for the selected equipment.

*For racks that contains rack PDUs with outlets information user can select power outlet type which should be used for power
connection. Outlet selection is not available when room contains only rack PDUs without outlets definition. When rack contains mixed
rack PDUs versions both can be advised even outlet is selected by user as missing outlet type on one of the rack PDU does not
eliminate it from use.

Page 285
Installation Requirements Pane
The Installation Requirements pane is used for guided addition/repositioning of equipment to the layout. It is available when Planning
>Asset Provisioning is selected in the Application bar.

New / Provides information about that component, e.g. how much power the equipment draws, how many power cords the equipment has,
Existing how much space the equipment takes up in a rack.
Asset info

Assign tags Lists available tags to select and assign to the equipment and rack in the new position in the layout.

Required Selects the level of redundancy for this piece of equipment in the new position in the layout.
Redundancy

Required Selects the amount of fiber or copper connections for this piece of equipment in the new position in the layout.
Network
Ports

Add / Move Adds one or more components to a Selected racks, Each rack in the server room, or Best rack.
Asset When you select Best rack, StruxureWare Data Center Operation: Capacity 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 Stru
xureWare Data Center Operation: Capacity installed).

Show Highlights the best location for the selected equipment in the layout.
location

See also

Finding the best location for a new server

Enabling provisioning match recommendations
Working with Asset Provisioning

Page 286
Optimizing the Design by Following the Recommendations
Recommendations are displayed in the Recommendation pane to guide you as you design the data center model.

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.

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

Cooling

General

License

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.

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

See also

General Recommendations
License recommendations
Power Recommendations
Cooling Recommendations
Showing Recommendations for Selected Equipment Only

Page 287
Showing Recommendations for Selected Equipment Only
How to filter the content of the Recommendation pane and display only the recommendations related to selected room or equipment.

1. Click the Link view with selected equipment icon to enable this feature.

2. Select equipment in Layout or Navigation pane that you want to see in the Recommendation pane.
3. Click the link icon again to disable this feature.

See also

Optimizing the Design by Following the Recommendations

Page 288
Cooling Recommendations
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.

See also

Optimizing the Design by Following the Recommendations

The Room has no Perforated Tiles for the CRAC Airflow

There is no Perforated Tile Airflow

Page 289
There is no Perforated Tile Airflow

Description
You have added one or more perforated tiles to the room but there are no CRACs to supply any airflow.

Recommended Action

Drag one or more CRACs into the layout.

See also

Optimizing the Design by Following the Recommendations

Page 290
The Room has no Perforated Tiles for the CRAC Airflow

Description
You have added one or more CRACs to the floor but there are no perforated tiles for the airflow.

Recommended Action

Drag one or more perforated tiles into the layout.

See also

Optimizing the Design by Following the Recommendations

Page 291
General Recommendations
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.

See also

Optimizing the Design by Following the Recommendations

The Tags Assigned to the Rack Equipment in the Rack do not Match
Rack Contains Overlapping Equipment at U Position
Max Load Weight of Rack has been Exceeded
Equipment Weight Exceeds the Weight Limit of the Floor

Page 292
Equipment Weight Exceeds the Weight Limit of the Floor

Description
The equipment is too heavy to be supported by the physical carrying properties of the floor layout.

Recommended Action

1. 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.
2. 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:
a. Right-click the floor layout and select Properties.
b. Redefine the Floor Carrying Capacity in the Floor page to match your physical environment.
To adjust the equipment weight:
a. Right-click the piece of equipment in the floor layout and select Properties.
b. 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

Page 293
Max Load Weight of Rack has been Exceeded

Description
The devices in this rack are too heavy to be supported by the rack.

Recommended Action

1. 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.
2. 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.
a. Right-click the rack and select Properties.
b. 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

Page 294
Rack Contains Overlapping Equipment at U Position

Description
More than one piece of equipment has been positioned in the same U position at a rack.

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

Page 295
The Tags Assigned to the Rack Equipment in the Rack do not Match

Description
The tags assigned to the equipment in the rack must match the tag or tags assigned to the rack.

Recommended Action

If the wrong tag was assigned to the rack or rack-mount equipment:

1. Right-click the recommendation message and select Show in Layout to identify the rack in the layout.
2. Right-click the rack or rack-mount equipment in the rack and select Properties to access the Properties dialog box for
the equipment.
3. 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:
1. Right-click the recommendation message and select Show in Layout to identify the rack in the layout.
2. Drag and drop the misplaced equipment into the correct rack.

See also

Optimizing the Design by Following the Recommendations

Page 296
License recommendations
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.

Page 297
You are Approaching the Amount of Racks Supported by your StruxureWare Data Center
Operation - Capacity License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 298
You are Approaching the Amount of Racks Supported by your StruxureWare Data Center
Operation - Change License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 299
You are Approaching the Amount of Racks Supported by your StruxureWare for Data Centers -
Operations Suite License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 300
You are Exceeding the Amount of Racks Supported by your StruxureWare Data Center
Operation - Capacity License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 301
You are Exceeding the Amount of Racks Supported by your StruxureWare Data Center
Operation - Change License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 302
You are Exceeding the Amount of Racks Supported by your StruxureWare for Data Centers -
Operations Suite License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 303
You have Reached the Amount of Racks Supported by your StruxureWare Data Center
Operation - Capacity License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 304
You have Reached the Amount of Racks Supported by your StruxureWare Data Center
Operation - Change License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 305
You have Reached the Amount of Racks Supported by your StruxureWare for Data Centers -
Operations License

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

Recommended Action

Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

See also

Optimizing the Design by Following the Recommendations

Page 306
Power Recommendations
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.

Page 307
Amount of Rack PDU Power Outlets has not been Configured

Description
The amount of power outlets has not been configured for this rack PDU.

Recommended Action

1. Right-click the rack PDU and select Properties.

2. In the Power page, fill in the appropriate amount of Power Outlets.

See also

Optimizing the Design by Following the Recommendations

Page 308
An Invalid Power Path has been Configured

Description
There is an invalid power connection in the power path.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.
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.
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.
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.

Recommended Action

1. Right-click the message in Recommendation and select Show in Editor to identify the components with the invalid power path
in the layout.
2. 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 Propert
ies, and remove the invalid power connection configured.

See also

Optimizing the Design by Following the Recommendations

Page 309
Associated Device Data has been Lost

Description

The component in the data center model is associated to a real-world device but the device data from the
Excerpt not found
The page: Branding was found, however the excerpt named: SWDCEaXTK was not found. Please check/update the excerpt name. is no
longer available.

Recommended Action

1. Right-click the message in the Recommendation pane and select Show in Navigation.
2. 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

Page 310
Breakers in Module must have Unique Power Phases

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

The numbers in brackets tell you which module number and phase combination causes the issue.

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.

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

Page 311
Connection has not been Configured between PDU and Power Supply

Description
A power connection is missing in the data center model from this PDU to the power supply from which it should receive power.

Recommended Action

1. Right-click the PDU and select Properties to open its Properties dialog box.
2. 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

Page 312
Connection has not been Configured between Power Panel and Power Supply

Description
A power connection is missing in the data center model from this Power Panel to the power supply from which it should receive power.

Recommended Action

1. Right-click the Power Panel and select Properties to open its Properties dialog box.
2. 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

Page 313
Connection has not been Configured between Remote Distribution Panel (RDP) and Power
Supply

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

Recommended Action

1. Right-click the RDP and select Properties to open its Properties dialog box.
2. 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

Page 314
Equipment Connected to this PDU Draws more Power than is Supported by the Power Supply
Breaker

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

Recommended Action

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:
1. Right-click the PDU in the Layout pane and select Properties to open its Properties dialog box.
2. 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

Page 315
Equipment Connected to this Power Panel Draws more Power than is Supported by the Power
Supply Breaker

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

Recommended Action

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:
1. Right-click the Power Panel in the Layout pane and select Properties to open its Properties dialog box.
2. 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

Page 316
Equipment Connected to this Remote Distribution Panel (RDP) Draws more Power than is
Supported by the Power Supply Breaker

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

Recommended Action

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:
1. Right-click the remote distribution panel (RDP) in the Layout pane and select Properties to open its Properties dialog
box.
2. 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

Page 317
Equipment in this Rack Receives Power from Multiple Power Supply Devices

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

Recommended Action

To configure a network power connection for the rack:

1. Remove the rack PDUs in the rack.

2. Right-click the rack in the layout and select Properties to open its Properties dialog box.
3. Ensure Exclude rack's load from power calculations has been selected.

To configure a rack PDU power connection:

1. Right-click the rack in the layout and select Properties to open its Properties dialog box.
2. Ensure Exclude rack's load from power calculations has been deselected.
3. Add rack PDUs to the rack and configure the power connection.

See also

Optimizing the Design by Following the Recommendations

Page 318
Equipment is Connected to a Rack PDU Outside this Rack

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

Optimize the connection by editing the power connection of the piece of equipment that is not connected to the intended rack PDU.

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

Page 319
PDU and Connected Rack PDU are Placed in Different Rooms

Description
This PDU is distributing power to one or more rack PDUs outside this room.

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

Page 320
PDU Output Voltage has not been Configured

Description
Output voltage has not been configured for this PDU.

Recommended Action

1. Right-click the PDU and select Properties to open its Properties dialog box.
2. In the Power Distribution page, select the appropriate Output voltage option.

See also

Optimizing the Design by Following the Recommendations

Page 321
Power Distribution Equipment must have Unique Breaker Module Numbers

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

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.

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

Page 322
Power Panel Output Voltage has not been Configured

Description
Output voltage has not been configured for this Power Panel.

Recommended Action

1. Right-click the Power Panel and select Properties to open its Properties dialog box.
2. In the Power Distribution page, select the appropriate Output voltage option.

See also

Optimizing the Design by Following the Recommendations

Page 323
Rack's Power Configuration does not Support Distribution Redundancy

Description
The rack does not have two or more compatible rack PDUs to comply with the group's distribution redundancy.

Recommended Action

Perform one of the following actions:

Remove the rack from the group and add it to another group:
1. Select the Floor Layout.
2. In the layout pane, right-click rack and select Remove from Capacity Group to remove it from the capacity group.
3. Repeat step 2, as needed.

Change the group's distribution redundancy settings:

1. Select the Floor Layout.
2. In the layout pane, right-click a rack in the capacity group and select Properties to open its Properties dialog box.
3. 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:
1. Select the Rack Layout.
2. In the layout pane, select a rack in the capacity group and add and connect rack PDUs to support distribution
redundancy.
3. Repeat step 2, as needed.

See also

Optimizing the Design by Following the Recommendations

Page 324
Rack is without Rack PDU or a Rack PDU is not Powered

Description
The rack is without rack PDUs or its rack PDUs are not connected to a PDU, remote distribution panel (RDP) or power panel.

Recommended Action

1. 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 Genomes p
ane into the rack in the Layout pane.

Tip: You can also select a rack PDU in the Genomes pane, and then use the Installation Requirements pane to
add multiple copies to the selected rack.

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 Genomes pane into the floor layout.
If there are rack PDUs in the rack and power supply in the solution, go directly to step 2.
2. Right-click the rack in the Layout pane and select Properties to open its Properties dialog box.
3. In the Power page, set up the power connection between a rack PDU and a PDU, Power Panel or remote distribution panel
(RDP).
4. Repeat step 3 until there are no more unconnected rack PDUs in the rack.

See also

Optimizing the Design by Following the Recommendations

Page 325
The Breaker Configuration does not Support Rack's Estimated Load

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

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

Page 326
The Breaker Configuration in the Power Distribution Properties does not Match the Measured
Power Data

Description

When the configuration is done and the system is running with device associations and retrieval of measured data from StruxureWare
Data Center Expert, the system notifies you if the module number and phase configuration in StruxureWare Data Center Operation do
not match the measurements.

The number in brackets tells you which module number causes the issue.

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.

Note

When you have reconfigured and resolved the issue, it may take some time before new data is retrieved from StruxureWare
Data Center Expert and this message disappears.

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 StruxureWare Data Center Operation reports an issue with it because no measurements are
available to the system.

Note

You cannot directly compare the power values you see here with the ones in StruxureWare Data Center Operation. The power
values displayed on the device in StruxureWare Data Center Expert are instant values whereas the values in StruxureWare
Data Center Operation are peak values.

To resolve the issue, you must remove the module number 12 from the breaker configuration in StruxureWare Data Center Operation.

See also

Optimizing the design by following the recommendations

Page 327
The Input Voltage Setting Required by the Equipment is not Available in Current Rack

Description
In the data center model, the server's input voltage requirement cannot be supplied by the rack PDU in the rack.

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
Genomes and select Properties to correct the value.

See also

Optimizing the Design by Following the Recommendations

Page 328
The Measured Load Exceeds the Estimated Load per Phase Designed for the Rack

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

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.

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

Page 329
The Measured Load Exceeds the Total Estimated Load Configured for the Rack

Description
Your physical infrastructure contains connected devices in the rack that use more power than the total estimated load in the rack reflects.

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

Page 330
The Measured Load of the Connected Rack PDU is 0, but an Estimated Load has been
Configured for the Rack

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

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

Page 331
The Measured Load of the UPS Exceeds the Total Estimated Load of the Connected Equipment

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

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.

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

Page 332
The Phase Configuration for the Connected Server is not Supported by the Rack PDU

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

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

Page 333
The Rack PDU Output Voltage Setting Does not Match the Output Voltage of the Connected
PDU or Power Panel

Description
The power connection is invalid because the voltage required by the rack PDU is not available from the power distribution component.

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 genome library 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

Page 334
The Server Should not be Supplied from Different Phases on 1 UPS

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

Recommended Action

1. Right-click the server and select Properties to open its Properties dialog box.
2. In the Power page, select the appropriate Connections options.

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.

See also

Optimizing the Design by Following the Recommendations

Page 335
The UPS in the Layout does not Supply Enough Power to Match the Configured Load of
Connected Equipment in the Layout

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

Recommended Action

Perform one of the following actions:

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

Page 336
This Equipment in Store Room is Connected to Equipment in a Room

Description
Equipment connected to other equipment in a room has been moved to a store room.

Recommended Action

1. Right-click the equipment in the store room and select Properties to open its Properties dialog box.
2. For a server, change the Power cable connection setting in the Power page.
3. For a rack PDU, PDU, Power Panel, or RDP, change the connection in the Power supply setting in the Power Dependency pa
ge.

See also

Optimizing the Design by Following the Recommendations

Page 337
UPS Internal Redundancy has not been Configured

Description
The internal redundancy has not been configured for this UPS.

Recommended Action

1. Right-click the UPS in the Layout pane and select Properties to open its Properties dialog box.
2. In the Power page, define the Internal Redundancy.

See also

Optimizing the Design by Following the Recommendations

Page 338
UPS Power Feed has not been Configured

Description
The power feed has not been configured for this UPS.

Recommended Action

1. Right-click the UPS in the Layout pane and select Properties to open its Properties dialog box.
2. In the Power page, define Redundancy as A Feed or B Feed.

See also

Optimizing the Design by Following the Recommendations

Page 339
Rack PDU internal breaker is overloaded

Description
The rack PDU internal breaker is overloaded.

Recommended Action

1. Perform one of the following actions:

Disconnect servers from overloaded bank to decrease load on internal breaker.
Check nameplate values for connected servers if all are correct.
Check if internal breaker derating value is set.

See also

Optimizing the Design by Following the Recommendations

Page 340
Viewing External System Data
StruxureWare Data Center Operation integrates with monitoring and virtualization systems.

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 StruxureWare Data Center Operation.
Monitored devices from external systems, for example StruxureWare Data Center Expert, StruxureWare Data Center: IT Power Control
or StruxureWare Data Center: IT Optimize, appear in Discovered Devices, available in Planning>Device Association.

On this page:

Viewing monitoring system data

Viewing virtualization management system data
Performing dynamic search
Locating an associated device in the layout
Launching to a device
Viewing properties

Viewing monitoring system data

Integration with monitoring systems, such as StruxureWare Data Center Expert 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). When it has been associated, it appears in Navigation (with the name from the external system in
parenthesis).

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). When it has been associated, it appears in Navi
gation (with the name from the external system in parenthesis).

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 Unassociated Devices p
ane.

Performing dynamic search

In the dynamic Search box above the Unassociated Devices 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.

Locating an associated device in the layout

Right-click the device in the Unassociated Devices pane and select Show in Layout to locate and select the device in its
physical location in the floor or rack layout.
Right-click the device in the Unassociated Devices pane and select Show in Navigation to locate and select the device in the
Navigation pane.

Launching to a device

Right-click the device in the Unassociated Devices pane and select Launch to Device for direct access to launch the device in
the external system.

Viewing properties

Right-click the monitored device or virtual machine host in the Unassociated Devices 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

Associating Live Data from an External System to the Layout

Configuring external system integration

Page 341
Launching to Device
Viewing Alarms From External Systems
The Importance of System Time Synchronization for Accurate Power Values

Page 342
About Peak and Average Power Data Retrieval from StruxureWare Data Center Expert
In StruxureWare Data Center Expert (DCE) devices, e.g. Rack PDUs, must provide measured values through power sensors in Watt. In
StruxureWare Data Center Operation(DCO), all power measurements are assumed to be in Watt.

DCO 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 opposed to apparent power VA, but the actual value is defined by the individual
device and how DCE retrieves the value. This could be done as a calculation in the DDF.

In System Setup>External systems configuration>Update power information every DCO retrieves the peak power values
from DCE at the specified power information retrieval interval. The default value is 300 seconds and average values once each day.
In System Setup>External systems configuration>Calculate power data based on the last, the peak and average power values are
calculated for the time period specified. The default value is 30 days. The peak power value is the highest value DCO receives
from DCE in the specified time period.

The collected data is summarized on a daily base. The summarization in done once a day at a time specified by when the server has
been booted. The summarization time can be seen in the server log file using the server configuration interface. Look for entries
like: Computing performance figures...

The retrieval of data between DCE and the device (rack PDU) is configured in DCE.

See also

Viewing External System Data

Configuring StruxureWare Data Center Expert integration

Page 343
Associating Live Data from an External System to the Layout
Monitored devices from external systems, for example StruxureWare Data Center Expert, StruxureWare Data Center: IT Power Control
or StruxureWare Data Center: IT Optimize, appear in Discovered Devices, available in Planning>Device Association. They also
appear in the Unassociated Devices pane.
When the monitored devices are associated with the corresponding items representing them in the application, the device data supports
the capacity planning process.

In the Unassociated Devices pane, a colored number indicates the number of matches found in the system for that item based on its
properties. The color corresponds to the likeliness the device matches one or more items in the layout. For example, if a StruxureWare
Data Center: IT Optimize asset matches the IP address of one server and the manufacturer of 100 servers, the number 1 will show in
green; if the IP address does not match but the manufacturer does, the number 100 will show in yellow.
Associating individual items (Figure 1)

1. To associate any of the items one by one with the item that represents it in the layout, drag-and-drop the item from the Unassoc
iated Devices pane into position over the corresponding items in the Navigation pane or Layout pane.
For example, drag a UPS on top of a UPS in the floor layout ( StruxureWare Data Center Expert), drag an IT asset on top of a
server in the rack layout (StruxureWare Data Center: IT Optimize), or drag a blade enclosure and its blades on top of a blade
enclosure and blades in the rack layout (Cisco integration).
2. 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 maximum kW power is
in use for each device or how much the CPU is utilized.
3. To remove the association between an item and the item representing it in the data center layout, right-click the device or IT
asset in the layout and select Unassociate from equipment.

Figure 1

Associating multiple items (Figure 2)

1. To associate multiple assets at the same time, select an external system in Unassociated Devices, for example a Cisco UCS
Manager or StruxureWare Data Center: IT Optimize server.
If there are perfect matches for items in that system, a Multi Associate icon will be enabled.
2. Click Multi Associate.
3. Select which associations to make and carry them out.

Multiple devices can be associated to one server in the layout, for example a server discovered through an ITO server, and a VMware
host.

Figure 2

Configuring association match interval (Figure 3)

Page 344
You can configure how often the system counts the association matches in Tools>Preferences>External Systems>Association
Suggestions.

Continuous counting whenever a change occurs, for example if properties change on items (default).
Only count on request. This is recommended for large setups.

If the system has been configured to only count association matches on request, an icon appears in the Association Details pane.

Click this icon to initiate another count.

Figure 3

Page 345
Launching to Device
You can access the device web interface directly from the Launch to Device right-click option.

1. Right-click a device, in the Unassociated Devices 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.
2. 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

Page 346
How Removing a Server Affects Power Values
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.To avoid this, the time period for measuring the data from the rack PDUs in the rack has been automatically
reduced:

When was the server removed from the rack? Measured data collected in time period:

Time From To

Less than 24 hours ago Present time - 24 hours Present time

Less than 30* days but more than 24 hours ago Deletion time Present time

More than 30* days ago Present time - 30* days Present time

*30 days is the default value set in the external system configuration settings; this value can also be 10, or 20 days.

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.

See also

Viewing External System Data

Configuring external system integration

Page 347
The Importance of System Time Synchronization for Accurate Power Values
When you have configured system integration correctly, StruxureWare Data Center Operation retrieves accurate and up-to-date power
measurements from the external system, such as StruxureWare Data Center Expert.
The StruxureWare Data Center Operation and StruxureWare Data Center Expert 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

StruxureWare Data Center Operation In the server's Webmin interface, StruxureWare DC Operation>Setup

StruxureWare Data Center Expert In System>Server Administration Settings, Time Settings option

Otherwise, the retrieved power measurements may be out of sync:

Server Time Consequence

StruxureWare Data Center Operation ahead of StruxureWare Data Center No measured peak data retrieved
Expert

StruxureWare Data Center Operation behind StruxureWare Data Center Expert Incorrect measured peak data retrieved (out of
sync)

For further instructions on how to configure system time synchronization for the StruxureWare Data Center Expert server, see the Struxu
reWare Data Center Expert help documentation.

Correct time settings are equally crucial in cluster environments.

See also

Setting up a clustered environment

Page 348
Power profiles and power value accuracy levels
StruxureWare Data Center Operation operates with these power values when calculating the most accurate values based on the data
retrieval from external systems and product specifications.

In the application, power values are highlighted based on the accuracy levels:

Green Advanced

Yellow Nameplate and Basic

Red No genome match

Advanced

Server Centric (Identical Match)

A power profile where the discovered server matches a server we have measured and the CPUs in the machine discovered matches the
CPUs of the machine we have measured. This gives a non-linear power curve.

CPU Centric (Component Based Model)

A power profile where the discovered server matches a server we have measured, but the CPUs in the machine discovered do not
match the CPUs of the machine we have measured.
However, the CPUs in the discovered machine do match a CPU we have measured. This gives a non-linear power curve.

Soft Profile (Identical non-measured Model)

A power profile where the discovered server matches a server for which we have vendor calculator information. This gives a non-linear
power curve.

Basic

CPU Centric Auto-Derated Nameplate (Component Based Model)

A power profile where the discovered server matches a server we have measured, but the CPUs in the machine discovered do not
match the CPUs of the machine we have measured.
However, unlike the CPU Centric case we have not measured the CPUs in the discovered server, but have a TDP nameplate value for
the CPUs in the discovered server. This gives a flat power line much better than a spec nameplate value for the server.

Nameplate

A power profile where the discovered server does not match a server we have measured. This gives a flat power line representing the
vendor provided spec value.

See also

Viewing External System Data

Page 349
Viewing Alarms From External Systems
When the system is configured to support integration with external systems, 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 Unassociated Devices 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

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.

See also

Associating Live Data from an External System to the Layout

Showing alarms for selected equipment only
Configuring external system integration

Page 350
Locating Alarms on Failing Equipment in the Layout
When configured, the system shows alarms from external system devices associated with modeled components in the layout, e.g. a
UPS or rack PDU.

In Operations (accessed in the Application bar Data Center>Operations):

1. View alarms in the layout by selecting the Room 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 Layout to identify and highlight the component
with the alarm in the Room Layout, or Navigation.

See also

Viewing Alarms From External Systems

Acknowledging Alarm Notifications from StruxureWare Data Center Expert

Page 351
Showing Alarms for Selected Equipment Only
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.

1. Click the Link view with selected equipment icon to enable this feature.

2. Select equipment in the Layout or Navigation pane that you want to see in the Alarms pane.
3. Click the link icon again to disable this feature.

See also

Viewing Alarms From External Systems

Locating Alarms on Failing Equipment in the Layout

Page 352
Acknowledging Alarm Notifications from StruxureWare Data Center Expert
In StruxureWare Data Center Operation, you can launch the StruxureWare Data Center Expert (DCE) web client to access alarm options
without installing the DCE client. For example, you can inform other users you are handling an alarm by acknowledging it directly in the
web client browser.

1. In Planning>Device Association, open the Unassociated Devices pane.

2. Right-click a monitored DCE device and select Launch to StruxureWare Data Center Expert .
3. In the browser showing the DCE web client, click the Monitoring tab.
4. In the list of alarms, click an alarm to select it, then use the acknowledgment check marks and comment option to let others
know you are handling the alarm.

For further information about using the DCE functionality, see the StruxureWare Data Center Expert help system.

Watch this video tutorial to learn how to detect an alarm, analyze impact, and acknowledge the alarm.

See also

Viewing Alarms From External Systems

Page 353
Configuring the PUE DCiE
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.
The PUE/DCiE Dashboard, available in the DCO web client Dashboard menu, 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 and read the Wh
ite Papers.

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.

123 Steps to...

Page 354
Configuring the energy system

1. 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.
a. Add device sensor measurements by clicking this icon

.
b. In the wizard, follow the steps to select one or more devices and sensors from the list.

Tip

Select multiple non-consecutive items by using Ctrl-click, or multiple consecutive items by using Shift-click.

c. 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.
d. Add custom values by clicking this icon

.
e. 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.
f. Delete any obsolete entries by clicking this icon

.
2. 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.
a. Add device sensor measurements by clicking this icon

.
b. In the wizard, follow the steps to select one or more devices and sensors from the list.

Tip

Select multiple non-consecutive items by using Ctrl-click, or multiple consecutive items by using Shift-click.

c. 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.
d. Add custom values by clicking this icon

.
e. 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.
f. Delete any obsolete entries by clicking this icon

.
3. See the results of the configuration expressed as a graph in the PUE/DCiE dial published to the PUE/DCiE Dashboard available
from the DCO web client Dashboard menu.

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.

Page 355
Working with Reports
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.

At any time, you can generate reports from the application. The amount of available reports depends on your system setup, as some
reports require specific module licenses.

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 StruxureWare Data Center Operation: Change installed).

123 Steps to...

Page 356
 Generating a reportYou can generate various reports based on standard or customized report designs.

1. From the Application bar, select Analytics>Reports.

2. In All Reports View pane, select a report type from Available Reports.
3. Use the Report Filter Options to define the filter for what data to include in the report, for example:
a. Select the time range that you want the report to cover.
b. Select the rooms that you want to include information about in the report.
c. 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.
4. 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).

Currently, csv and xls export is not supported for reports containing graphs.

Note

When generating reports on various Linux distributions, you might experience issues. See compatibility with Linux-based
operating systems for more information.

See also

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

Page 357
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.

Creating a report filter template

1. In Available Reports, select a report type.

2. In Report Filter Options, select the data that you want to include when you generate a report based on these settings.
3. 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.
4. 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.

Applying a previously saved report template

1. In Available Reports, click the + symbol next to the report type to expand the list and see the available report filter templates.
2. Select the report filter template to apply.
You can now see the filter settings of the selected template.
3. 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).

Page 358
Customizing Report Designs
In StruxureWare Data Center Operation, 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, StruxureWare Data Center Operation: Insight. This requires basic Birt development skills.

If you want custom reports but do not wish to develop these yourself, contact your local sales representative or visit the Data Center
Software website for information about purchasing custom reports.

Watch this video tutorial to see how to work in StruxureWare Data Center Operation: Insight to change the logo on a report.

Note

You must have a valid StruxureWare Data Center Operation: Insight license for the application to be available for download.

1. Export one of the built-in standard report designs from StruxureWare Data Center Operation to use it as a template for the new
custom report design.
a. In File>Export, select Report Design.
b. 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.
2. Open the Data Center Operation server's download page in the web browser by specifying the URL of the StruxureWare Data
Center Operation server.
3. Click StruxureWare Data Center Operation: Insight Download and follow the instructions to download and install StruxureWa
re Data Center Operation: Insight.
4. Launch StruxureWare Data Center Operation: Insight and follow the instructions in the New Report wizard to create a new
report design.
a. Type a name for the report with the extension .rptdesign.
b. Select a report type to use as template for your design.
These templates contain the same data as the default reports available in StruxureWare Data Center Operation. In
addition, there is a blank report template for creating a new report without starting from predefined data.
5. Create the custom report design, save and publish to the Data Center Operation server to make the report design available for
use in StruxureWare Data Center Operation.
For information about how to use StruxureWare Data Center Operation: Insight, refer to the built-in help system.
To make the report design available on the Data Center Operation server, select File>Publish to Data Center
Operation server.
6. In StruxureWare Data Center Operation, import the custom report design.
a. If it is not already open, select Analytics>Reports to switch to the report view.
b. Select File>Import>Report Design.
c. Select to save the custom report with a new name on the Data Center Operation server or overwrite an existing report,
and click OK.
The new report design has been saved to the Data Center Operation server and appears in the list of available reports
in StruxureWare Data Center Operation.

See also

StruxureWare Data Center Operation: Insight

Working with Reports
Working with Report Filter Templates

Page 359
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.

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 StruxureWare Data Center Operation: Insight.

Right-click the report name in the list of Available Reports, select Rename, and type the new name.

See also

Working with Reports

StruxureWare Data Center Operation: Insight
Reconfiguring locale on the StruxureWare Data Center Operation server

Page 360
Audit Trail Report
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.
The Audit Trail report is available if you have StruxureWare Data Center Operation: Change. In addition to being available from Analytic
s>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.

See also

Working with Reports

Page 361
Energy Cost Report
An Energy Cost report can be generated to calculate the costs for running specified equipment used for charge back and efficient
budgeting.
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.

1. 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 StruxureWare Data Center Expert server.
2. 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.
3. 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 and read the Wh
ite Papers.

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.

See also

Working with Reports

Page 362
Rack U-Space Report
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.
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 StruxureWare Data Center Operation: Change in
stalled, 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.

See also

Working with Reports

Page 363
Understanding what Happens when Multiple Users Work Simultaneously in DCO
You can work in StruxureWare Data Center Operation simultaneously with other users without any issues. However, some simultaneous
edits may cause conflicts. The system handles these situations according to these specifications.

General rule of thumb

When you are editing in mode, your system will not be updated with any changes made by other users while you are editing. These
changes will not be updated in your system until you save your changes or switch to Data Center Operations mode.

For example, you and another user are both editing in Data Center Planning mode, making changes in the same room. You both save
your changes. The user who saves his changes the first will not receive the changes made by the user who saves his changes the last.

Changes to the Navigation

Create Rooms
If you and another user simultaneously create rooms in the same folder, you will be prompted with a multi-user conflict warning in the Str
uxureWare Data Center Operation client. The user who saves his changes the last will lose his changes.

Modify Floor Plan

If you and another user simultaneously modify a Floor Plan, you will be prompted with a multi-user conflict warning in the StruxureWare
Data Center Operation client. The user who saves his changes the last will lose his changes.

Changes to the same room or rack

If you and another user simultaneously modify equipment in the same room or rack, your changes will be saved unless you modify the
same equipment (see below).

Changes to the same equipment

If you and another user simultaneously modify the same equipment, you will be prompted with a multi-user conflict warning in the Struxur
eWare Data Center Operation client. The user who saves his changes the last will lose his changes.

For example, you have made a lot of changes during the last 15 minutes (without saving yet). One of the changes made to a rack
conflicts with a change made by another user 10 minutes ago.
When you now save your changes, everything you changed in the last 15 minutes will be lost. You will be prompted with a multi-user
conflict warning, indicating that there is a conflict and your changes will be lost.

Tip

If you are working in StruxureWare Data Center Operation simultaneously with other users, save your changes frequently. This
will reduce the amount of changes lost in case of a multi-user conflict.

Page 364
StruxureWare Data Center Operation Web Client
About the DCO web client
The StruxureWare Data Center Operation web client is available on a computer, tablet, or mobile device with an internet browser, and
provides easy web access to a subset of the features available in the DCO suite:

Rack inventory management

Dashboards
Account settings
Administration functions, such as
License management
Desktop client download
User management
Authentication server configuration
Customer management (colo feature, available with the StruxureWare Data Center Operation for Colo license)

Web client interface

Supported browsers and OS

StruxureWare Data Center Operation web client minimum browser and OS requirements:

Internet Explorer 10
Chrome 52
Firefox 49
Safari 9.1.3
iOS 9.3.5
Android 5.1
Microsoft Edge 20.10240.16384.0

Access and language settings

To access the web client, use a browser to launch to the IP address or hostname of the DCO server <serverIPaddress> and log in.

If you're not an English speaker, you can select your preferred language in Profile>Language (your profile image in the upper right
corner).

Security

When connecting to the DCO server from a web browser, you may receive warnings about the security certificate needed for secure
communication. The DCO server is installed with a self-signed security certificate. It is recommended, after the installation of DCO is
complete, to replace this with a security certificate issued by a trusted certificate authority. For information about certificates and how to
replace the default self-signed certificate with one you purchase from a trusted certificate authority, see Working with SSL certificates an
d Changing SSL certificate on the server.

If you try logging in with wrong credentials 5 times, your account will be locked for 10 minutes.

Page 365
Rack inventory and dashboards
The web client rack inventory allows you to see any part of the DCO data center infrastructure model you have been granted access to
and drill down through locations and rooms to the rack inventory. You may have been granted with rights to view or edit all or parts of the
rack inventory. For example, depending on your user rights, you can:

View a graphical representation of locations, rooms including walls, doors, windows, cages, and floor-mounted equipment
View equipment in racks and their properties, such as servers, blade chassis, network equipment, and rack PDUs
Edit equipment in racks and their properties, such as servers, blade chassis, network equipment, and rack PDUs
Connect equipment in racks to rack PDUs for power or disconnect
View power and space usage for the selected room, cage, or equipment
View power history for the selected room, cage, or rack
View capacity overview for the entire solution or a selected location
View audit trail for the selected room, cage, or equipment, listing changes made to the infrastructure, such as connecting
servers to rack PDUs or changing equipment names

There's an upper limit to everything

The web client does not include all functionality included in the graphical editor in the DCO desktop client. For example, you cannot:

Add, change, or delete locations, rooms, or floor-mounted equipment (including racks)

Design or edit room layouts
Configure network connections
Use custom tags
Add, change, or delete work orders

Page 366
Working with the inventory
The web client rack inventory allows you to see any part of the DCO data center infrastructure model you have been granted access to
and drill down through locations and rooms to the rack inventory. You may have been granted with rights to view or edit all or parts of the
rack inventory.

Infrastructure overview and drill down

Locations and rooms from the DCO desktop client are represented in the web client in a non-hierarchical structure, making it easy to
click (or tap, if on a tablet) your way through locations, rooms, cages, and racks to a specific server or other asset in a rack.

Room

The room layout provides an overview of the floor-mounted equipment in the room. You can switch between overlays to reveal relevant
details on top of your equipment, such as power as graphs and numbers, and available u-space.

This information is also available as property tiles to the right of the layout. The information updates with relevant information for the
selected equipment.

The audit trail reflects any changes to the selected room or equipment.

Zoom and overview Use the zoom and full screen options to get a better view of specific details or an overview of the full solution.

Open rack Double-click a rack to open it in the rack layout.

Cage

If you are using StruxureWare Data Center Operation for Colo, you can see the cages you have been granted access to in the room
layout.

Glass Light blue

Mesh Dotted lines

Solid Black

Rack

The rack layout provides an overview of the rack-mounted equipment in the selected racks and enables you to edit your rack inventory.

Expand/collapse Use the expand/collapse icon to toggle viewing a rack from the front only or from the front and rear at the same time, for
rack example to see rear-mounted rack PDUs.

Open multiple Click the + icon to open multiple racks at the same time, allowing you to compare or drag equipment between them.
racks
If you open several racks, selecting zoom fit and full screen view will allow you to better see all racks at the same time.

Show sensors If you want to see temperature sensor data displayed directly in the rack layout at the sensor's position, select to show
in rack sensors.

Editing rack inventory

In the web client changes to the rack inventory happens immediately. You don't have to click to save your changes as in the desktop
client. There's no undo either!

If you regret adding a piece of equipment, delete it; if you regret moving a piece of equipment, move it back, etc.

In case you accidentally make a quick move and didn't pay attention to where the equipment ended up, use the audit trail.

Adding equipment

1. In the rack layout open the rack in which you want to position the new equipment.
2. Click ADD EQUIPMENT to open the Equipment library.
3. Find the equipment to add by searching the library.
4. Drag it into the rack.

Moving equipment

1. In the rack layout open both the source and target racks.
a.

Page 367
 1.
a. Double-click to open the source rack.
b. Click COMPARE above this rack to open a list of other racks in the room.
c. Select the target rack from the list of racks.
2. Drag the piece of equipment you want to move from the source rack into position in the target rack.

Deleting equipment

1. Select the equipment you want to delete.

2. Click Actions... in the information panel to the right of the layout, and select Delete.

Auditing rack inventory changes with the audit trail

The audit trail enables you to monitor rack inventory changes on-the-fly. It is available as a tile to the right of the rack layout. No need to
generate a report. It updates immediately as you add, move, or delete equipment, or disconnect cables, etc.

Page 368
Editing rack inventory
Open the room with the racks you want to edit and double-click a rack to open it in the rack layout. To enable moving equipment
between racks, open multiple racks next to each other by clicking the plus icon and selecting more racks.

Warning

Any changes made to the rack inventory in the web client will update the model on the StruxureWare Data Center Operation se
rver and in the desktop client.

Adding, moving, or deleting rack equipment

To add equipment from the equipment library:

1. Click + ADD EQUIPMENT to open the equipment library.

2. In the text field, start typing some characters of the equipment you want to add, or the product category, for example 'blade
enclosures'.
As you type, all items that contain the typed characters are listed.
3. Select the item you want to add and drag it into position in the rack layout.
4. Close the equipment library (x) when you are done adding equipment to return to the full rack layout.

To move equipment in the layout:

Drag and drop equipment to other positions and/or racks.

To move equipment between racks, open the racks next to each other by clicking the plus icon, and selecting the racks, and
then drag equipment.

To delete equipment in the layout:

1. Select the piece of equipment to delete.

2. Scroll to the bottom of the equipment information panel to the right and select DELETE.

Configuring, editing, or deleting power connections

The application provides two ways of configuring power connections for rack equipment:

1. Configuring power connections from power consumers point of view,

2. Configuring power connections from rack PDU point of view, if rack PDU supports extended power information.

Configuring power connections from power consumers point of view

1. Select the power consumer for which you want to configure, edit, or delete power connections, such as a server.
2. In the equipment information panel to the right, click the Power tile and look for power consumer inlet with nothing connected to
it. Free inlet is marked with gray rectangle and label saying ”Not connected”.
3. Use dropdown to the right to see list of possible power sources.
4. Click on desired power source.
5. For power sources without power outlet information, select phase from list of available phase configurations,
6. For power sources with power outlet information, select available outlet.
7. To remove existing power connection, click on the selected phase or outlet again.

Configuring power connections from rack PDU point of view (extended power information only)

1. Select the power outlet for which you want to configure, edit, or delete power connection.
2. In the equipment information panel to the right, click the Power tile and check the Connected state.
3. Use dropdown to the right to see list of possible power consumers.
4. Click on desired power consumer to establish connection.
5. To remove existing power connection, click on the selected power consumer.

Editing equipment properties

1. Select the piece of equipment for which you want to edit properties, such as a server.
2. In the Properties tile in the equipment information panel to the right, edit any property.
Some properties may not be editable.

Any changes to the rack inventory will show in the Audit Trail.

Page 369
Searching the inventory

Full inventory search

Use the search box in the welcome view (click Inventory in the top menu) to search for any piece of equipment in the entire inventory.
This allows you to quickly navigate to a specific piece of equipment. For example if you know the name of a server in a particular room,
you don't need to browse your way through locations, rooms, and racks.

If there's only one server matching your search, the system drills right down to it, opening the rack layout, highlighting the
server, and showing the property tiles on the right.
If more than one item fit your search, you can select from this limited list of items rather than browsing everything.

The DCO web client / Tenant Portal supports not simply exact string matches, but also character patterns using partial strings or
wildcards:

Full String
Begins-with partial string
When the search text entered is found in the beginning of the words (e.g. for equipment with name "Blade enclosure 23 1",
partial search works for searched entries: Bla, encl, 23, 1.
Wildcard characters (supported: *, #, %) (e.g for equipment with name "Blade enclosure 23 1", wildcard search works for *ade,
*clos*, *clos#, *closu%.
Minimum amount of characters to be entered for a search is 2 characters, except when there is a string or substring with a
single character in the name/property of the equipment. In this case single character search is possible.

Note

This is different from the behavior in the desktop client where search only returns results from the rooms you have opened on
your local machine.

Quickly search entire inventory

Quick search in open room

Use the quick search box appearing in the left corner when a room is open to search for any piece of floor-mounted equipment in this
room. This allows you to quickly navigate in a large room to locate a specific piece of floor-mounted equipment.

The quick search does not work in the same way as the full inventory search and does not support wildcards, etc. It is simply meant as a
quick way to find floor-mounted equipment in a large open room layout. Start typing the first characters of the equipment you want to
locate and the search immediately lists the matches in the room.

Search using:

Full string
Partial string
When the search text entered is found in a word, need not be at the beginning of the word (e.g. for equipment with name "Blade
enclosure 23 1", partial search works for searched entries: lad, ncl, losur.

Page 370
Quickly search open room (floor-mounted equipment)

Page 371
Dashboards
Use the web client's Dashboard menu to get an overview of your data center KPIs, such as the power history values (for the selection of
equipment to which you have access), or energy efficiency.
You will see one chart per top level item (room, cage, or rack).*

Tip

Bookmark the dashboard in your browser or keep it running on a separate screen.

Power History

Page 372
Using the Energy Efficiency Dashboard
The Energy Efficiency Dashboard, available from the DCO web client Dashboard menu, 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 StruxureWare Data Center Operation: Energy Efficiency.

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 and read the White Papers.

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 use the settings below the graphs on the dashboard to define the data (for example energy system and time period) displayed
in the graphs.

1. Open the Energy Efficiency Dashboard from the web client Dashboard menu.
2. 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.
3. 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.
4. 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

You can toggle the metric between PUE and DCiE in > Tools > Preferences > General.

Page 373
Using the PUE DCiE Dashboard
See the results of the PUE/DCiE configuration expressed as a graph in the PUE/DCiE dial published to the PUE/DCiE Dashboard
available from the DCO web client Dashboard menu.

The PUE/DCiE graph shows the calculated PUE/DCiE based on measured data collected on a daily basis according to the configuration
done in the DCO desktop client Planning > PUE/DCiE Configuration.

Follow the below instructions or watch this video tutorial to learn how to set up the PUE/DCiE dashboard.

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

You can toggle the metric between PUE and DCiE in Tools>Preferences>General.

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 and read the White Papers.

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

Page 374
Changing the language
Use the language option, available in the Profile>Language (your profile image in the upper right corner), to change the language
settings and view the web client in any of the supported languages.

The selected language will be used for texts on all pages, options, dialog boxes, status messages, etc. The language settings apply per
user and the default language is English.

Read about Desktop Client language settings here.

Tip

You can join our community of multilingual users of StruxureWare products and contribute translations for future versions of
the software.

See more here...

Page 375
Managing your user account
Use your account settings, available in Profile>My Account (your profile icon in the upper right corner), to manage your user account
information.

About users

User accounts are handled by the DCO server or authentication server and changes to your user settings are effective on both the DCO
web client (or Tenant Portal), and DCO desktop client. The same user may be able to access the desktop, and/or web client, or Tenant
Portal depending on his user permissions. These are handled by system administrators through the Administration>Users menu. More
...

In the DCO colo edition, there are also customers and users at a customer's site. More...

Editing your account settings

Type your email address and full name.

This option is not available if you're a remote user since your account is handled by an authentication server. More...
The full name is the name displayed for your user account.

You cannot change your own username or delete your own user account.

Changing your password

Click CHANGE PASSWORD... and enter your old and new passwords.

If you forgot your password, your system administrator (a user with administrator rights) can reset your password for you and send you a
new password.

This option is not available if you're a remote user since your account is handled by an authentication server. More...

Setting system of measurement

In Preferred unit system, select to use metric or US customary settings.

This affects for example if the equipment dimensions are displayed in meters or feet.

Changing language settings

You can change your language settings (per user) in a separate menu item (Profile>Language). More...

Local user on the DCO server

Page 376
Remote user on an authentication server

Page 377
Customizing web branding
You may want to change some default settings of the DCO web client, e.g. if you want to brand your site with your own logo, or color.

These settings are available in the branding folder on your DCO server and can be changed through the server management interface
(Webmin).

Replacing login background image, logo, and company logo

Changing website color theme

Changing help link

Replacing login background image, icon, company name and logo

Replacing the icon will change the icon you see on login as well as the small icon in the top left corner of the web client.

Regardless of your image size, it will be automatically scaled to fit into the position of the default image. However, it's recommended to
use a photo in a square shape for the logo.png file.

1. Rename your custom file(s)

a. background image --> bg_login.jpg.
b. logo --> logo.png
c. company logo --> company_logo.png
2. Open the server management web interface (Webmin) by typing the address of your DCO server in a web browser folllowed by
:10000, https://<server IP address>:10000 .
3. Log on to Webmin using the user credentials created during the server installation.
4. In the left menu, select System>Upload and Download.
5. On the Upload to server tab:
a. Click Choose Files in Files to upload and navigate to your saved bg_login.jpg file. Same procedure for logo.png file
and company_logo.png file.
b. In File or directory to upload to navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/brandi
ng.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
c. In Owned by user and Owned by group, select dcojboss.
d. Click Upload.
6. Close and reopen your web browser and type the server address to access the login screen with your new custom images.

Changing website color theme

The color theme determines the color of borders in the web client (default green), e.g. borders of dialog boxes, borders in license icons,
borders in room icons in the inventory, etc.

1. Open and log in to Webmin as described above and navigate to System>Upload and Download in the left menu.
2. On the Download from server tab, navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/branding.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
and download the branding.css file.
3. Open the branding.css file, make your changes to the color codes, and save the file.
Tip: You can find an introduction to HEX color codes here: http://www.w3schools.com/cssref/css_colors.asp.
4. Reopen the Webmin interface and navigate to System>Upload and Download.
5. On the Upload to server tab:
a. Click Choose Files in Files to upload and navigate to your saved branding.css file.
b. In File or directory to upload to navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/brandi

Page 378
5.

b.

ng.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
c. In Owned by user and Owned by group, select dcojboss.
d. Click Upload.
e. Close and reopen your web browser and type the server address to log in to the web client with your custom color
theme.

Page 379
Changing help link

The default help link goes to our support and help site. To redirect to your custom help site, change the settings in the branding.json file.

1. Open and log in to Webmin as described above and navigate to System>Upload and Download in the left menu.
2. On the Download from server tab, navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/branding.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
and download the branding.json file.
3. Open the branding.json file, make your changes to the link, and save the file.
{
"subTitle": "StruxureWare",
"title": "Data Center Operation",
"helpUrl": " http://sxwhelpcenter.ecostruxureit.com ",
"tenantPortalUrl": ""
}
4. Reopen the Webmin interface and navigate to System>Upload and Download.
5. On the Upload to server tab:
a. Click Choose Files in Files to upload and navigate to your saved branding.json file.
b. In File or directory to upload to navigate to the branding folder on your server:
8.0 - 8.0.3 - /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/brandi
ng.
8.0.4+ - /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding.
c. In Owned by user and Owned by group, select dcojboss.
d. Click Upload.
e. Close and reopen your web browser and type the server address to log in to the web client with your custom help link.

Page 380
Page 381
Managing licenses
Use the web client Administration>Licenses menu, to monitor, add, and delete licenses or update expiring evaluation licenses on the
DCO server through the DCO Web Client.

If you are running DCO for Colo Tenant Portal, this option is available to you only if you are logged in as colocator. License management
is not available to tenants.

About DCO licenses

DCO is available in a regular and a colo base version and is scalable with several license types 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 for high availability and
disaster recovery (clustered setup with multiple servers).

The base version includes a desktop and a web client; the colo base version also includes Tenant Portal with specific colocation
features.

Separate add-on module licenses are available for use with DCO. The base DCO license must be added before you can add the add-on
licenses.

Licenses are handled on the DCO server. This means that if you have DCO running on multiple clients, they will be updated
automatically, and you only need to restart the application to get the add-on features.

You can see all available products here. Contact your local sales representative or visit the Data Center Software website for information
about purchasing additional licenses.

Note

To get the full benefit of multiple modules, you need the same amount of licenses for all modules.

If you have a license type with a lower amount of supported racks than another, this may prevent you from adding to your
inventory.

For example, if you have a solution with 200 racks running in DCO, Capacity , and Change and you subsequently extend with
licenses for 100 additional racks in DCO, you should also add licenses for 100 additional racks in Capacity and Change.

However, some license types are excepted from this model. StruxureWare Data Center: Server Access and Data Center
Operation: Cooling Optimize licenses do not need to match the other license types. Instead limits are imposed on how many
devices you can manage when the license counts for these modules are lower than for DCO.

Monitoring license usage

You can see a graphical overview of the registered modules on your DCO server in Licensed Modules. You'll see relevant usage
information depending on the license type:

number of available nodes (e.g. racks)

number of used nodes
number of used nodes exceeding the number of licensed nodes
If you exceed your license limits, you should purchase additional licenses to continue working with the application.

The status bar at the top of the page also illustrates this usage status. If you have enterprise licenses, the status bar will not show.

If a license is limited by another license, a warning icon will appear.

Page 382
The License Keys table provides details about all license keys added to the server, including license type and size, installation and
expiration dates, and license key. Size indicates the node count/enterprise and, for Colo licenses, area. Expiration date shows for
evaluation licenses to remind you to update expiring licenses.

You can sort the table by column ascending/descending by clicking on a column header.

Adding licenses

1. In a browser, go to the DCIM Asset Management web site http://dcimassets.schneider-electric.com to redeem passcodes and
generate your license keys.
2. One by one, add the generated license keys to the text box.

To delete licenses, use the delete icon in the License Keys table.

Exporting license keys

You may find it useful to have an external list of purchased licenses in a number of situations, such as when doing a backup/restore or
upgrade of your system, for tracking expenses of your licenses, or in a support situation.
Use the Licenses display to copy/paste the license key information into a document or click EXPORT LICENSE KEYS to export to a .lic
file.

Page 383
Managing DCO users and user rights
In the web client Administration menu, if you are logged in as a DCO administrator with the needed permissions, you can set up and
edit DCO users, groups, permissions, and remote authentication servers.

Granting general (global) system rights and fine-grained permissions for individual parts of the application allows you to restrict access
and protect system functions and inventory that only you or a subset of your team is allowed to see or edit.

Warning

Setting up users and managing permissions can be a complex process. Take your time to understand how some settings
override others.

Be specifically cautious about granting permission to User Rights and Authentication Servers as it overrides all equipment
permissions and gives the user access to ALL locations and equipment on the DCO server, even if he was assigned No
access to a location, room, or equipment in Equipment Permissions.

About DCO users

First time login with default admin user

During the initial installation of DCO, a default DCO user with administration rights is created with the credentials apc/apc (password
must be changed on your first login). You will not be able to access the system without using this user account for the first login.

For security reasons, whether you're installing a fresh version of DCO or restoring an existing solution*, it is important to change the
default DCO user account as part of the initial setup.

You'll be prompted to change the password the first time you log in to the web client with this user. It is recommended that you create
new user with other credentials, avoiding apc, admin, system, and other frequently used names. You cannot change the apc username if
you are logged in as the apc user. You must create a new user with user administration rights and log in as this other user to delete the
apc user or change the username.

Because all DCO users will also be able to log in through the web client and Tenant Portal, it is particularly important that you avoid
insecure passwords and that you delete user accounts for all previous employees, etc.

*If you're restoring a backup of an existing solution, you should open Administration>Users and ensure you don't have a legacy apc
user in the system, or at least that the password is secure.

Local vs remote users

When you add a new user, you are setting up a local user on the DCO server by default. To set up a remote user, configure
authentication servers to have the information supplied by that server. See how to configure authentication servers for remote users here
.

About DCO permissions

The DCO user permission model is a complex model of general system permissions and granular equipment permissions for users and
groups. These permissions have an internal hierarchy in case of conflicts:

User and group permissions

If a user is in one or more groups, his total permissions are the sum of all these permissions.

If he has access to something his group doesn’t, he keeps his individual permissions.
If the group has access to more than the individual user or another group he is in, he gains the group’s permissions.

Equipment permissions

If there’s a conflict in user and user group permissions, equipment permissions take priority in this order: No access, view, and edit.

When setting up or changing equipment permissions, you may want to verify the equipment permissions for the user and all his groups
since the user interface may not update to reflect a change:

If No access is selected for the user or one of his groups, it overrides any view or edit permissions set the the user or another
one of his groups.
If View access is selected for the user or one of his groups, it overrides any edit permissions set for the user or another one of
his groups.

User Rights and Authentication Servers permissions

Page 384
This administration setting overrides any other settings and provides access to any location or equipment on the DCO server, regardless
of other settings, even No access.

Setting up users and permissions

When you are setting up a local user, user information is stored directly on the Data Center Operation server. This method provides the
ability to create Data Center Operation user accounts without the need to connect to any external systems or repositories.

Setting up a new user

In Administration>Users click ADD USER, and type the user information.

The user's email address is used by the system to send automatic notifications, e.g. initial welcome email with username and
password to new users, and notifications related to work order assignments (StruxureWare Data Center Operation: Change feat
ure).

Setting up permissions

1. Click the new user and open the user information view where you can select granular permissions.
2. Select the system functions to which the user needs access or administration rights and the inventory to which the user needs
view or edit rights.
a. Granting user administraiton rights
In Global Permissions, select User Rights and Authentication Servers to allow the user to set up users and
permissions like you.

Note

This user will get access to ALL locations and equipment on the DCO server, even if he was assigned No
access to a location, room, or equipment in Equipment Permissions.

b. Granting rights to use the system

In Global Permissions, deselect 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, alarms, planning data center and asset provisioning (to access these perspectives), or even access to the
desktop client.
c. Granting restricted rights to partial inventory
In Equipment Permissions, select which parts of the inventory the user is allowed to access, and if the access should
be restricted to only viewing or if editing rights should be applied. 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.

Setting up and editing user groups

User rights can be set at individual user or group level. If you're setting up many users with the same permissions, create a user group
with these permissions to automatically grant them the permissions set at group level.

1. In Administration>Users, add individual users one by one by clicking ADD and typing user information.
You do not need to set up permissions at this point.
2. In Administration>User Groups, click ADD to add a new user group and name it.
3. Set permissions to access and/or administrate various DCO features in the same way as for individual users, only these will
apply to all users in the group.
4. Select to add the users to the group.
Existing users can also be added to a group from the Users view (in User Groups, click SELECT... and choose between
existing user groups).

Auditing user access activities and resetting password

Auditing user access activities

You can track some user activities by generating an audit trail report in the desktop client.

Auto lock out is handled the same way for all users. No notification is sent. Failed login attempts login are logged to the server log file
only.

Page 385
Resetting a user's password

To reset a user's password, in Administration>Users, click the user to open the user information, then select RESET PASSWORD.

The Data Center Operation system users should not be confused with the OS user on the Data Center Operation server. Resetting the
password for the OS user is an entirely different story that you can read here.

Page 386
About users

DCO user

DCO users can log in to the DCO desktop and web client (known as Tenant Portal for Colo users) to use the parts of the application they
have been granted access to according to their user rights. They can manage their own user accounts but need to contact their
administrator for other configuration needs or in case of any issues.

DCO administrator

DCO administrators are administrators of the DCO application. DCO administrators can log in to the DCO web client and perform
administration tasks related to the DCO application, such as user management, license management, and web branding for the look and
feel of the web client.

This is not the same user as the server OS administrator described below.

DCO users and administrators can be local users (saved on the DCO server) or remote users authenticated by an AD or LDAP server,
see more Configuring authentication servers used for managing remote users. Ensure there's at least one local DCO administrator
account. This is needed for various reasons, for example in case there's a network related issue preventing connection to the
authentication server or in case changes were made on the authentication server preventing DCO from getting the user data.

Server administrator

The server administrator is administrator on a deeper level, managing the server as well as the applications running on the server. This
is the person doing server configuration and maintenance, such as configuring backup, secure connection, or file sharing.

This user may also be referred to as the Linux, OS (operating system) or Webmin user because:

Linux CentOS is the operating system that comes with the DCO server installation and, as part of the DCO installation process,
this first Linux server administrator must be created to subsequently be able to log in and perform server management tasks on
the server after installation is complete.
Webmin is the name of the web-based server management interface that the server OS administrators can use to perform
server management tasks on the DCO server after installation is complete.
Webmin is not the only way to manage the server. You can also run commands directly on the DCO server by connecting
through SSH without the need to open Webmin. SSH to the DCO server and log in with the server administrator credentials
created during initial installation of DCO.

Note

Since the DCO administrator and the server administrator are two different users, credentials are also separate and
independent of each other. DCO administrator credentials are stored in the the DCO application database while server
administrator credentials are stored by the server's operating system.

DCO administrator credentials are included in DCO backups. Restoring a DCO backup will reset DCO administrator
credentials to whatever was stored in the backup. Server administrator credentials are separate and are not affected by
restoring DCO backups.

Page 387
Granting access to legacy SOAP web service API
Users who have been granted the necessary user rights can integrate with third party systems using the legacy SOAP web service API.
These web services gradually being replaced by a new publicly available RESTFul API.

In Global Permissions, select Access to,Legacy SOAP web service APIs, save and close.

The user is now able to create a web service account and access the data exposed by the system.

Page 388
Configuring authentication servers used for managing remote users
Configuring authentication servers in the DCO web client provides access to DCO for remote users provided they have been
authenticated by the configured authentication server.

About remote users, certificates, and authentication methods

When a remote user attempts to log on to the DCO server, the credentials are sent to the authentication server associated with that
user. It is that server, and not the DCO server, that authenticates the logon attempt.

Note

If you use SSL, ensure there’s at least one local user on the DCO server so you’ll be able to log in and accept new SSL
certificates from authentication servers when the current ones expire.

This is necessary because when a certificate expires for an AD, LDAP, or DCE server used for authenticating remote users in
DCO, the DCO server will no longer be able to verify that the logon attempts come from a trusted server, and therefore will not
allow any of these users to log in.

Log in as a local user on the DCO server and trust the new certificate from the AD, LDAP, or DCE server to reenable
authentication.

See more about working with SSL certificates here.

Configuring remote user authentication

1. In Administration>Authentication Servers, click to add an authentication server.

2. Enter authentication server settings, starting with predefined authentication method from the drop-down list.
The name, email address, and password data is supplied by the authentication server.

When you are setting up a remote user, user information is stored on:

StruxureWare Data Center Expert server as a remote repository with user information. The Data Center Operation server
requires connection setup to the StruxureWare Data Center Expert server in order to obtain the user information.
LDAP or Active Directory server. The Data Center Operation server requires connection setup to the server and logon
information is required.

When a remote user attempts to log on to the Data Center Operation 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 Data Center Operation server, that authenticates the
logon attempt.

Indirect AD authentication (via DCE) is not recommended.

LDAP and Active Directory specifications

Support for LDAPv3, both ldaps:// and ldap://

DCO's Active Directory integration supports mutual trust between child and parent Domain Controllers (Active Directory servers)
mutual trust allows the user which authenticates an Active Directory server to authenticate against a parent or child
Domain controller of your Active Directory server.
The username of a user that has access to reading users and groups from the authentication server can, because of
mutual trust, be defined with the child domain name as part of the username. Example: username@child-domain
or [email protected]
How-to setup an Active Directory server: Set up AD server
The operations done are only read operations on the following fields: cn, uid, mail
You can import individual users or user groups from a remote authentication server.
Users in groups are automatically added to DCO and will appear in the user interface. Users are not automatically deleted,
however, permissions are removed if a user is removed from a group.
Tested and verified OS versions for Enterprise Active Directory:
Windows OS: Windows Server 2008 R2 SP1 and 2012 SP1
Forest function level: Windows Server 2008 and 2012
Domain functional level: Windows Server 2008 and 2012

LDAP and Active Directory Limitations

Active Directory has an LDAP query limit of 1000 objects, to prevent excessive load and Denial of Service attacks
The default method to get around this limitation, is to break up the query to return at most 1000 objects at a time. For
example, query only for objects starting with the letter a, then query for objects starting with the letter b and so forth.
The more efficient method for large environments is to enable paging. Paging automatically splits the results into
multiple result sets so the integration does not have to split up the query into multiple requests.
A more comprehensive list of limitations and work-arounds can be found here: LDAP policy in Active Directory

Page 389
Authentication server configuration in the Web client:

Administration > Authentication servers > Authentication server settings

Page 390
Setup an AD (Active Directory) Server
This is an example of setting up an AD Server.

Note: This setup requires a functional DCO web client.

To illustrate how an authentication server might look, Apache Directory Studio is used, to connect and show an authentication
server.

The following two illustrations show what the Authentication server settings look like (image 1) when you are connecting to an AD
Server, without groups (image 2).

(image 1)

Page 391
(Image 2)

Page 392
When configuring group info, you have two options based on your type of authentication server:

Your authentication server may support none (skip this step), one or both options.

1. Parse user attribute for list of groups.

a. Documentation: https://msdn.microsoft.com/en-us/library/ms677099.aspx
2. search for groups containing users.
a. Documentation: https://msdn.microsoft.com/en-us/library/ms677097.aspx

Configuration of option 1 - parse user attribute for list of groups:

Page 393
Configuration of option 2 - search for groups containing users:

Page 394
Finally.

Now that your server is setup, you can confirm your connection by checking if there are any groups available in
the User Groups Browser.

Page 395
Working with SSL certificates
When working with DCO in a secure environment, you need to verify and trust the authenticity of the DCO server and the servers it
connects to for integrations, such as VMWare, IT Optimize, AD or LDAP servers.

Verifying details of the installed DCO server certificate

To verify advanced details of a currently loaded SSL certificate for the DCO, such as key size, signature algorithm, etc., connect to the D
CO server through a web browser and view the SSL certificate there.

As an example, follow these steps with Chrome browser on Mac.

1. Connect via HTTPS in a web browser to your DCO server.

2. Click the pad lock icon in the browser's address bar to display a security related dialog box.
3. Click Details>View certificate, you will see important technical details, such as the signature algorithm, signature hash
algorithm, and key size.

Verifying details of the installed certificate for servers communicating with the DCO server

To verify advanced details of a currently loaded SSL certificate for servers communicating with the DCO server, such as AD or LDAP
servers:

1. In the DCO web client, open Administration>Certificates.

You will see a list of the currently loaded certificates.
2. Click SHOW... to see important technical details, such as the signature algorithm, signature hash algorithm, and key size.

Page 396
StruxureWare Data Center Operation Server
DCO server system requirements

System requirements
Linux desktop client compatibility guide

DCO server installation

Installing StruxureWare Data Center Operation

Security

StruxureWare Data Center Operation security

DCO server in a cluster environment

About DCO cluster environments

DCO server settings

Managing DCO server settings

Page 397
Managing DCO server settings
You can configure and monitor most DCO server management settings in the Webmin server management interface.

Some server settings are set during installation of DCO, such as language (DCO server locale). However, these settings and more can
be changed at a later time by using SSH to connect to the DCO server.

Note

Changing server settings no longer requires that you log in as root user (from DCO 8.0). You must now log in as the first OS
admin user on the DCO server. This user is the administrator created during initial installation.

Accessing Webmin

The server management interface, Webmin, provides a web-based interface for server configuration. The latest version of Webmin
available at the time of release is included with the Data Center Operation installation/upgrade.

1. Open the Webmin web interface by selecting Administration>Webmin in the Data Center Operation web client.
Alternatively, type the address of your Data Center Operation server in a Web browser folllowed by :10000, <https://>:1000
0.
2. Log on to Webmin using the user credentials created during the Data Center Operation installation.
3. Use the menu to the left to access server management features, such as
Backup configuration
System log configuration

Browser related issues

If you are experiencing issues accessing Webmin, check the privacy and advanced settings of your browser. For example, in Internet
Explorer 9:

Open Tools>Internet Options>Privacy and select to Accept All Cookies.

Open Tools>Internet Options>Advanced and make sure JavaScript is enabled.
If needed, contact your IT department for policies, etc. possibly preventing access.

Note
There are known issues with Internet Explorer 9 and the ETL Integration Management page. If you experience issues
creating staging databases, a possible workaround is to upgrade your browser.

For security reasons, it is recommended that you use the browser's settings such as deleting browser history on exit and that you don't
use the browser options to remember credentials.

Webmin access

Using SSH to connect to the DCO server

You can access the Data Center Operation server and change server settings used for e.g. server locale, archiving and rotating log files,
and IT discoveries (ITO, Server Access, IT Power Control).

To do this, you must log on to the server with an SSH client, such as PuTTY (download here), and use the credentials of the first OS
admin user on the Data Center Operation server created during initial installation of the Data Center Operation server.

If you skipped creating the first OS user as part of the installation process, you can use the root Webmin access to create the user at a

Page 398
later time:

1. Open the Webmin web interface.

2. In the left menu, select System>Users and Groups.
3. Click Create a new user.
4. In the Group Membership section, select wheel in the All groups column of Secondary groups and click the arrow to move it
into the In groups column.

User with credentials to connect to the server through SSH

See also

Page 399
File sharing between Data Center Operation and your network
Before you can configure remote backups of StruxureWare Data Center Operation on your network or migrate data to the Data Center
Operation server from previous versions, you need to enable file sharing between the Data Center Operation server (Linux) and your
network. CIFS and NFS protocols are mentioned below. Other file systems are also available.

When you configure a remote backup of StruxureWare Data Center Operation in the Webmin server management interface, specify the
mounted folder as your backup directory in StruxureWare DC Operation>Backup.

Watch this video tutorial to see how to configure a backup to a remote share.

Mounting a Windows share

Security
By default, when you mount a share using the Common Internet File System (CIFS) protocol, the password of the share will
be saved in clear text on the DCO server in a file that is readable by all local users on the DCO server. The password is also
logged to the Webmin log file in clear text. This log file is only readable by privileged users.

If this is not a concern for you, follow these instructions to mount a Windows share.

However, if the share requires a login/password and this security note is a concern for you, the recommended method is to
upload a specific file for this purpose to the DCO server and lock it for only root to read. Follow these instructions to save CIFS
share credentials in a separate file only accessible to root before mounting the share.

1. Open the Webmin web interface by selecting Administration>Webmin in the DCO web client.
Alternatively, type the address of your DCO server in a Web browser followed by :10000, <https://>:10000.
2. Log on to Webmin using the credentials created during the server installation.
3. In the left menu, select System>Disk and Network Filesystems.
4. In the Type drop-down list, select Common Internet Filesystem (cifs).
5. Click Add Mount.
6. In Mounted As, browse to the folder on the Data Center Operation server that you want to use for sharing the files.
It is recommended that you create a share folder at /data/share/.
7. Select Save and mount at boot and Mount.
8. In Server Name, type the hostname or IP address of the network server on which the folder resides.
9. In Share Name, type the name of the drive or folder on the network server that you want to share.
10. If needed for accessing the server, type the login credentials.
11. Click Create.

Mounting a Network File System

1. Follow steps 1-3 above.

2. In the Type drop-down list, select the network protocol that matches your system, such as Network Filesystem (nfs).
3. Click Add Mount.
4. In Mounted As, browse to the folder on the Data Center Operation server that you want to use for sharing the files.
5. Select Save and mount at boot and Mount.
6. In NFS Hostname, browse the list of NFS servers on your local network and select the IP address of the server that is exporting
the folder that you want to mount.
7. In NFS Directory, browse the list of exported folders.
8. Click Create.

If, at any point, you want to delete a mounted system:

1. Reopen the Webmin web interface.

2. In the left menu, System>Disk and Network Filesystems.
3. In the list of file systems, click the one that you want to delete.
4. Select Don't save and Unmount.

Save CIFS share credentials in a separate file only accessible to root

1. On your local machine, create a new empty text file named cifs-cred.txt.
2. Type the following in the file, exchanging USER and PASSWORD with the user and password required to access the CIFS
share:

username=USER
password=PASSWORD

3. Open the Webmin web interface by selecting Administration>Webmin in the DCO web client.
Alternatively, type the address of your DCO server in a Web browser followed by :10000, <https://>:10000.
4. Log on to Webmin using the credentials created during the server installation.
5. In the left menu, select System>Upload and Download.
6.

Page 400
 6. Click the Upload to Server tab and choose to upload the file you created in steps 1-2, uploading it to /root, and setting owner
and group to root.
7. In the left menu, navigate to System>Others>File Manager.
8. Find the root directory in the list and click it.
9. Click the small box next to your cifs-cred file to select it.
10. In the top menu, select the gear icon (Chmod selected).
11. In the permissions popup, ensure only the Owner has Read and Write permissions and click Change to apply the permission
restrictions.

The file should now only be accessible to root.

Webmin interface steps 5-11

Page 401
Backing up and restoring backup
Backing up the Data Center Operation server and restoring the backup is used for example when upgrading from certain versions of
DCO to the latest version.

Backups can only be restored to a Data Center Operation server of the same or newer product release.

The backup of the Data Center Operation server is a database backup. It does not include server and OS configuration settings, such as
configuration of server time, locale, remote backup settings. To ensure backup of any customized server configuration files, verify that
your enterprise backup system backs up these files. Otherwise, after restoring a backup, you must configure server and OS settings
again. Ensure you have a copy of all installed license keys and network settings prior to restore.

Running a backup

By default, the system backs up to a local backup directory on the same disk.

1. Open the web client and login with a user with the System Configuration permission.
2. Navigate to the Backup and Restore page, by clicking the.
3. Click 'Schedule Backup' to start a backup immediately. This will save a backup in the default location /data/backup* or see h
ere for information about scheduling regular backup jobs.

While the backup is being performed a log is shown that shows the status of the backup job. The log can be minimised without
interrupting the backup process.

Recommendation

It is highly recommended that you save backups to a remote location.

Configuring a remote backup

On the Backup and Restore page you can configure a remote backup location.
Prerequisite: To enable saving the backup on your network, mount the folder in which to save the backup.

1. Click Backup Settings to open the Backup Settings page.

2. Specify the Backup directory in the text field.
3. Select the Fail if not mounted remotely option if you want the Backup and Restore page to show an error message if the
remotely mounted directory is not mounted.

The last option is especially useful if it is important that the backups are stored away from the server.

Restoring a backup

1. Set up a new server with a clean installation of StruxureWare Data Center Operation.
2. Login to the web client for the new server on which you want to restore the backup, the user should have the System
Configuration permission.
3. Navigate to the Backup and Restore page.
4. Select an uploaded backup file and click Restore selected backup.
If the backup you want to restore is not in the list, upload the file as described below.

Note

A restore will wipe all current data.

Info

If you have upgraded to 7.4.X or above, note that when restoring a backup the ETL external system integration jobs
are not started automatically. You have to enable ETL again after the restore:

1. After the restore start the client, open the export configuration, and select the new export job (without psql in the
name).
2. Drop all tables in the export database.
3. Resume the job in Webmin.

Uploading a backup

Page 402
Open Webmin.
If you are working with a cluster environment, type the virtual IP address of the cluster server.

1. Login to the web client.

2. Navigate to the Backup and Restore page.
3. Click the Upload to backup.
4. In Files to upload, browse to the location of your saved backup.
Make sure the file format is: <name><yyyy-mm-dd><hh.mm>.tar.gz

Backing up a cluster environment

If you are running Data Center Operation in a cluster environment, only the slave nodes will run the backup.

Recommendation

Save backups to a remote location and schedule backup on all slave nodes. Configure each node to run the backup at
different times to avoid conflicts.

Restoring a backup in a cluster environment

The restore process may be started on any cluster node. However, restoring on the master node will be fastest.

Note

The Webmin Status page must be open during the entire process.

1. The cluster node to which you are restoring (preferably the master) stops running.
2. The other nodes all stops one by one, until all nodes in the cluster are stopped.
3. When the database restore has been completed, the nodes start up again one by one.
4. The solution has been restored and the cluster is functional again.

Testing backup

You should verify that the backup runs as expected. You can purchase an enterprise backup agent for PostgreSQL, or you can verify the
backup in Webmin.
The backup file size provides a good indication, and if you have scheduled daily backups, you can check that this is included in the file
name.

1. In Webclient, select Administration > Backup and Restore.

2. In the list of backup files, verify that the size of the backup seems reasonable, and that the file name includes the prefix Daily_
if you scheduled to run the backup every day.

Cleaning up old backups

In Webclient Administration > Backup and Restore > Backup Settings, you can configure cleanup frequency of old backups.

1. Specify whether to clean up and how often:

Disable: Never clean up
Days to keep backups: Delete files older than the specified amount of days
Click Save Settings.

Page 403
Restoring IT Optimize backup

The backup of the Data Center Operation server is a database backup. It does not include server and OS configuration settings, such as
configuration of server time, locale, remote backup settings, or cluster setup. To ensure backup of any customized server configuration
files, verify that your enterprise backup system backs up these files. Otherwise, after restoring a backup, you must configure server and
OS settings again.

Running a backup

The StruxureWare Data Center: IT Optimize server is automatically backed up in the StruxureWare Data Center Operation backup.

Restoring IT Optimize and Intel® Data Center Manager Server

ITO and DCM run autonomously, but they are linked to each other so if you have created discoveries using IPMI, you need to restore
both products.

Note

A restore will wipe all current data.

StruxureWare Data Center: IT Optimize servers must be running the same OS type (i.e. a backup of an StruxureWare
Data Center: IT Optimize server running on Microsoft Windows can only be restored to another StruxureWare Data
Center: IT Optimize server running Windows).
The ITO database backup must be from the same ITO release or older compared to the server on which it is being
restored.
The DCM database version must match the DCM to which it is being restored, meaning DCM 4.0.0 (included with ITO
7.5.2) can only be restored to another DCM 4.0.0 database.

For StruxureWare Data Center: IT Optimize, the easiest method to restore or move the installation:

1. Create the backup on the current server (or get your most recent backup).
2. On the target server, remove any existing ITO and DCM installations.
The restore procedure is the same on Windows and Linux.
3. Open a Windows command prompt, or a Linux command terminal.
a. Move to the directory/folder which contains the StruxureWare Data Center: IT Optimize installer.
b. Run the StruxureWare Data Center: IT Optimize installer, adding the ITO backup file as a command line argument.
Notice the --db_restore_zip command line argument which starts with a pair of "-" characters.

./StruxureWareItOptimize-setup.windows.x64.exe --db_restore_zip c:\DatabaseBackup.zip

This command will install IT Optimize, and restore the ITO backup file to the database so all polling data, assets, and discoveries will be
restored.

The installation will also install the Intel DCM software. It will be initialized. If you haven't been using IPMI based discoveries, the
procedure ends here.
If IPMI discoveries are being used, you also need to restore the DCM database. Here's how:
The DatabaseBackup.zip file created during the ITO backup should also contain the Intel DCM database backup.

1. Place the DatabaseBackup.zip file on the root of the C:\ drive and extract the contents of the zip file, so you'll have a DatabaseBackup
folder or the contents are extracted onto the C:\ drive.

The files listed in the image are contained in the DatabaseBackup.zip file. The DCM restore procedure requires access to the
"dcmDatabase" file. The other files are related to IT Optimize backups.

2. On the new ITO server, stop the Intel® Data Center Manager Server service using the Windows services control panel.

Files contained in the DatabaseBackup.zip file (step 1)

Windows services control panel (step 2)

Page 404
3. Open a Windows command prompt and navigate to: C:\Program Files\Intel\DataCenterManager\external\pgsql\bin

4. Run this command to remove the existing DCM database:

dropdb –p 6443 –U dcmdba dcm

5. Run this command to create a new clean DCM database:

createdb –p 6443 –U dcmdba dcm

6. Run this command to populate the newly created DCM database:

pg_restore –p 6443 –U dcmdba –d dcm <path>dcmDatabase

Example: If you have placed the dcmDatabase file in C:\DatabaseBackup, run:

pg_restore –p 6443 –U dcmdba –d dcm C:\DatabaseBackup\dcmDatabase

7. Restart the Intel® Data Center Manager Server service.

Page 405
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.

The regular backup files will consume some disk space and increase in size over time, so it is highly recommended to use a remote
location. See how to clean up old backups here.

1. Open the Webmin web interface by selecting Administration>Webmin in the DCO web client.
Alternatively, type the address of your DCO server in a Web browser followed by :10000, <https://>:10000 .
2. Log on to Webmin using the user credentials created during installation of StruxureWare Data Center Operation.
3. In the left menu, select System>Scheduled Cron Jobs.
4. To enable the default backup schedule:
a. Select one of the 3 backup options as needed:
Daily
Weekly
Monthly
b. Click Enable Selected Jobs to enable the job with the default settings. Note that per default the daily backup option is
enabled.

5. To customize the backup schedule:

a. Click one of the 3 backup Data Center Operation server options (click in the "Command" column) as needed:
Daily
Weekly
Monthly
b. Edit the time for the system to automatically execute the backup job as needed.
By default daily backup runs at 2:30 AM.
c. Select Active: Yes and save to enable the selected backup job.
The system will automatically run the job regularly with the specified interval.

Page 406
Disaster recovery
You can configure an up-to-date backup recovery server in a remote location for resuming operation in the event of a disaster.

The clustered environment is no longer available in DCO 8.2.7. More..

You can add a disaster recovery node to a stand-alone Data Center Operation (DCO) server. This requires a high availability license.

PostgresSQL streaming replication is used to move data to the disaster recovery node. Communication is necessary through ports 22,
80 and 5432. The disaster recovery node also needs to able to 'ping' the IP address that it gets attached to.

The connection between the DCO server and the disaster recovery node must be stable and quick enough to transfer a full backup.

Configuring disaster recovery

1. Allow the Disaster Recovery node to connect to the DCO server.
a. Selecting Administration > Webmin in the DCO web client to open the Webmin web interface on theDCO server.
Alternatively, type the address of your DCO server in a Web browser followed by :10000, <https://>:10000.
b. Log into Webmin and select StruxureWare DC Operation > Disaster Recovery.
c. Select the option Allow another node to connect to this node. Enter the IP to allow as disaster recovery node. Push
Attach. And then Accept the fingerprint and allow the Disaster Recovery node (.53 in the example) to connect to this
node (.52 in the example). Figure 1.
2. Configure the Disaster Recovery node.
a. Install DCO on a dedicated remote server with stand-alone Disaster Recovery configuration (.53 in the example). See h
ow.
b. Open the Webmin interface on the Disaster Recovery server.
i. Type the Disaster Recovery server's IP address in a Web browser.
ii. On the download page, click Server Configuration.
This opens the Webmin server configuration interface on the Disaster Recovery server.
iii. Log into Webmin using the user credentials created during installation (step 2a). Select StruxureWare DC
Operation > Disaster Recovery.
c. Select the option Attach this node as a disaster recovery node to another node. Enter the IP address of server to be
attached to. Attach. And then, Accept the fingerprint and attach this node as Disaster Recovery node. Figure 2.

You have now configured Disaster Recovery. In case of a disaster and shutdown of the DCO server, you can promote the Disaster
Recovery to a stand-alone DCO server.

Note

If the Disaster Recovery node is monitored, for example by DCE via SNMP, it is important to set the device scan timeout in
DCE high enough for the Disaster Recovery to respond. Otherwise, it will return 'communication lost'. How you set the device
scan timeout depends on the network speed between the Disaster Recovery and the DCO server.

Figure 1

Figure 2

Page 407
Promoting disaster recovery
1. Open the Webmin interface on the Disaster Recovery server (.53 in the example).
a. Type the Disaster Recovery server's IP address in a Web browser.
b. On the download page, click Server Configuration.
This opens the Webmin server configuration interface on the Disaster Recovery server.
c. Log into Webmin and select StruxureWare DC Operation > Disaster Recovery.
2. Verify the data shown is correct, and select Promote disaster recovery node. You have now restored a copy of your DCO serv
er.

Re-enabling after disaster recovery

Reconfigure your main server as it was before the disaster occurred, and then follow the steps below to re-enable the disaster recovery
node:

1. Create a backup of the disaster recovery server.

2. Restore the backup on your main DCO server(s).
3. Repeat the steps in Configuring disaster recovery to reconfigure your setup as it was before promoting disaster recovery.

Page 408
Managing StruxureWare Data Center Operation services
In the Webmin server management interface, you can see a list of all services installed on the Data Center Operation server (StruxureW
are DC Operation>About).

You can also monitor and manage the status of services running on the Data Center Operation server. All services must be OK for Strux
ureWare Data Center Operation to function properly.

Services

Web status of services ensuring the web server functions, used for example in configurations running secure connections and for load
balancing between nodes in a cluster environment.

Application status of services ensuring the StruxureWare Data Center Operation process functions.

Database status of services ensuring 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 is down, 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 other cluster nodes.

Backup status of services ensuring the backup configuration (default or custom setup) functions. The default backup location on the DC
O server is /data/backup.

Cluster status of services ensuring the cluster setup functions. If you are running StruxureWare Data Center Operation in a cluster
environment, you'll see the cluster status per node, showing you the role of the node in the cluster, such as master, backup, primary
node.

123 Steps to... See also

Monitoring and changing the status of a service Managing

DCO server
1. Open the Webmin web interface by selecting Administration>Webmin in the DCO web client. settings
Alternatively, type the address of your DCO server in a Web browser followed by :10000, <https://>:10000. Setting up a
2. Log on to Webmin using the user credentials created during the installation. clustered
3. In the left menu, select StruxureWare DC Operation>Status and verify that the status of all services are OK. environment
4. If the status of one or more components does not seem OK, click to reboot the Data Center Operation server and wait 5
minutes for the reboot to complete, search EcoStruxure IT Help Center questions or troubleshooting documentation or contact
technical support for assistance on how to resolve this.

Page 409
Changing the IP address of the StruxureWare Data Center Operation server through Webmin
1. Log on to Webmin using the user credentials created during the installation.
2. Change the IP address.
a. In the left menu, select System>Network Configuration.
b. Select Network Interfaces.
c. Click the Activated at Boot tab.
d. Click a line in the list of network interfaces to edit boot time interface parameters.
e. Set Activate to Yes.
f. Click the interface you want to change (for example eth0).
g. Select Static configuration (recommended for cluster setup), and type the IP address in IPv4 address and the Netma
sk, then save.
It is recommended that you do not use IPv6 (not supported).
3. Specify the Gateway.
a. In the left menu, select Network Configuration.
b. Select Routing and Gateways.
c. 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.
4. Specify the DNS server.
a. In the left menu, select Network Configuration.
b. Select Hostname and DNS Client.
c. In DNS servers, type the primary and secondary DNS servers, then save.
5. Restart the server.
a. In the left menu, select Boot and Shutdown.
b. Click Reboot System and wait for the system to finish rebooting.

Page 410
Reconfiguring locale on the StruxureWare Data Center Operation server
This page is under review as some of the commands are not available on CentOS 7.

The locale settings on the Data Center Operation server control the language of the alarm messages, etc. displayed in Data Center
Operation. The locale is configured during installation and you can subsequently reconfigure it as follows:
1. Log on to the server with an SSH client.
For example, use PuTTY. You can download it from here.
2. Type the command sudo dpkg-reconfigure locales and press Enter.

3. Select one of the locales supported in StruxureWare Data Center Operation, 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

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.

4. Select the locale that you want to use again, and select Ok.

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.

Page 411
5. Type reboot and wait for the server to restart.

6. Type exit to close the command prompt.

See also

Managing DCO server settings

Working with Localized Reports

Page 412
Configuring log rotation and archiving
You can configure daily log rotation and save an archive of log files for audit and troubleshooting.

On this page:

JBoss log files

Other log files
Client log files

JBoss log files

Enabling daily rotation of JBoss log files

1. Log on to the Data Center Operation server with an SSH client.

For example, use PuTTY. You can download it from here.
2. Type the command

sudo nano /opt/jboss-as/server/isxo/conf/jboss-log4j.xml

3. Find all occurrences of

org.jboss.logging.appender.RollingFileAppender

and replace them with

org.jboss.logging.appender.DailyRollingFileAppender

4. Find all occurrences of

<param name="MaxFileSize" value="100MB"/>

<param name="MaxBackupIndex" value="1"/>

and replace them with

<param name="DatePattern" value="'.'yyyy-MM-dd"/>

The server rolls the log files in /opt/jboss/server/isxo/log every day. You must now configure log archiving, otherwise the log
files will continue to grow and take up too much space on the server.

Configuring archiving of JBoss log files

1. On the Data Center Operation server, mount a folder in which to store the log files, for example /data/logarchive.
2. Open the Webmin web interface.
a. Type the address of your Data Center Operation server in a Web browser.
b. On the Data Center Operation server's download page, click Server Configuration.
3. Log on to Webmin using the user credentials created during the installation.
4. In the left menu, select System>Scheduled Cron Jobs.
5. Click Create a new scheduled cron job.
6. In Job Details
Type to execute job as root.
Type the command:

mv /opt/jboss-as/server/isxo/log/*.log.* /data/logarchive

Type a description.
If you want to save the log archive to a different folder than /data/logarchive, change the path in the command.
7. In When to execute, select Daily (at midnight).

Page 413
Other log files
You can configure log rotation for other server log files in the Webmin web interface.

1. Open the Webmin web interface.

a. Type the address of your Data Center Operation server in a Web browser.
b. On the Data Center Operation server's download page, click Server Configuration.
2. Log on to Webmin using the user credentials created during the installation.
3. In the left menu, select System>Log File Rotation.
4. Select the log files you want to rotate.
5. Click a log file line to open the Edit Log File page and change the default settings according to your wishes, such as location of
the files or rotation interval.

Client log files

In StruxureWare Data Center Operation, select Help>Download Log Files and save the server and client log files to a location of your
choice.

The client log file is rolled in this location when the .log file exceeds 1 MB. The latest 10 files will be stored.

See also

Managing DCO server settings

Page 414
Managing Webmin user accounts
The StruxureWare Data Center Operation server configuration is handled in the Webmin web interface and so are the Webmin user
accounts.

Creating a new user account (A)

1. Open the Webmin web interface
a. Type the address of your Data Center Operation server in a Web browser.
b. On the Data Center Operation server's download page, click Server Configuration.
2. Log on to Webmin using the user credentials created during the installation.
3. In the left menu, select System>Users and Groups.
4. Click the Local Users tab.
5. Click Create a new user.
6. In User Details, type username, real name, and Normal password.
7. Select Shell /bin/bash to ensure you can copy command examples in the user assistance or sent to you by technical support
as these have been written as bash scripts.
8. In Group Membership, select New group with same name as user as Primary group.
9. In Secondary groups, select sudo and click the arrow to move this group into the In groups box. This is needed for
performing administration tasks on the Data Center Operation server.
10. Click Create and test the new user account by logging out of Webmin and logging on using the credential created for this user.

Changing a user account (B)

1. Open the Webmin web interface
a. Type the address of your Data Center Operation server in a Web browser.
b. On the Data Center Operation server's download page, click Server Configuration.
2. Log on to Webmin using the user credentials created during the installation.
3. In the left menu, select System>Users and Groups.
4. Click the Local Users tab.
5. Open the Edit User page by clicking the Username of the user.
6. In User Details, change the password by selecting Normal password and typing the new password.
7. Click Save and test the password change by logging out of Webmin and logging on using the new credentials.

You can also change other password or group membership options. However, do not remove the sudo group membership as this is
needed for performing administration tasks on the Data Center Operation server.

Recommendation

Do not change the username of an existing user. Instead, create a new user with a new username and disable the old user
account by selecting the old user and clicking Disable Selected.

You can change the password for StruxureWare Data Center Operation in the StruxureWare Data Center Operation client.

Page 415
 See also

Managing DCO server settings

Page 416
Managing Webmin interface security

Webmin allowed IP addresses

As an extra security layer, we recommend that you limit access to Webmin to local IP addresses.

Enter IP addresses as a comma-separated list. IP subnets can be entered by typing address/mask. The mask can be either a network
mask or a plain number, specifying the number of 1's at the left side of the network mask. Thus, a mask of 24 is equivalent to
255.255.255.0.
You can use this Wolfram Alpha widget to calculate which net mask corresponds to which address range.

Disable Webmin session authentication

To avoid Webmin session cookies, go to Webmin Configuration > Authentication and disable session authentication.

See also

Managing Server Settings

Page 417
Enabling Data Center Operation monitoring through Data Center Expert
Monitoring StruxureWare Data Center Operation through StruxureWare Data Center Expert requires that you enable server
communication in Webmin and in StruxureWare Data Center Expert snmpExpert.

Webmin Configuration

StruxureWare Data Center Operation 8.x

1. Open the Webmin web interface.
a. Type the address of your Data Center Operation server in a Web browser.
b. On the Data Center Operation server's download page, click Server Configuration.
2. Log on to Webmin using the user credentials created during the installation.
3. In the left menu, select StruxureWare DC Operation>Setup.
4. Configure the server protocol settings, for example enable SNMPv1 and type community.
The SNMP server requires a specific SNMP community from the monitoring systems. If the SNMP community is not correct, it
will not reveal any information to the monitoring system. You can think of SNMP community as a password.

Tip

For added security, change the SNMP community to something other than "public" and make the monitoring system use this
(see below).

Tip

For added security, disable SNMPv1 and configure SNMPv3.

Version 8.x

StruxureWare Data Center Expert configuration

1. In the StruxureWare Data Center Expert Device Discovery wizard, select the corresponding SNMPv1 or SNMPv3 settings,
ensuring the community or username and password matches the one specified in the Webmin configuration (see above).
2. Set the Timeout to minimum 20 seconds to allow time for the server communication.

For further information about StruxureWare Data Center Expert configurations, see the StruxureWare Data Center Expert user
assistance User assistance for StruxureWare Data Center Expert (DCE) 7.x

SNMPv1 SNMPv3

See also

Configuring StruxureWare Data Center Expert integration

Page 418
Configuring external system integration
DCO SNMP Status Codes

Page 419
Disabling redirection of http requests to https
Some of the systems communicating with DCO do not support https communication.

Http communication must be enabled on DCO 8.0 for you to be able to use DCO with these systems, like StruxureWare Data Center
Operation: Mobile, StruxureWare Portal, and StruxureWare Data Center Operation: PRO Pack.
To handle this, a setting to disable redirecting http to https has been introduced in the server management interface (Webmin).

Warning

Use this option with caution and be aware of the reduction in security since your data will no longer be encrypted!

Unless you have enabled a secure connection in the DCO desktop and web clients, disabling the redirection will also mean
your communication between the server and clients may be at risk.

Server configuration (Webmin) settings

Page 420
Software packages and services
In the DCO server management web interface (Webmin), you can see a list of installed software packages and services on the DCO ser
ver, including version specific information.

All services must be running in order for DCO to function properly. To monitor and manage the status of services running on the Data
Center Operation server, go to the Webmin menu StruxureWare DC Operation>Status.

Page 421
StruxureWare Data Center Operation: Capacity
About capacity management
When talking about data center capacity, we talk about power, space or cooling capacity.

You may experience one or more of these typical power, space or cooling capacity issues in your data center (see screenshot).

When you have modelled the data center in StruxureWare Data Center Operation, use the add-on capacity management module to
design to solve these issues.

StruxureWare Data Center Operation: Capacity makes daily tasks significantly easier for you by applying advanced calculations on your
design. The asset provisioning functionality will guide you to obtain the optimum data center design, such as suggesting the best location
for your next equipment because of the right amount of free space, cooling, power, and redundancy available.

Note

Using the Capacity module requires a preconfigured and valid power path, including an upstream connection to one of these
power sources:

UPS
Input breaker on a PDU/Power Panel (assuming it is connected to the mains supply)

How does DCO know what the available capacity is?

The system calculates how much capacity is used to guide you on how much capacity is available. This happens automatically and you
don't need to set anything up for the system to provide you with guidance, other than modelling your power equipment in the system,
including correct breaker values, and a valid power path.

In addition to the power information available in each rack (physical breaker limits), the system relies on the enabled power capacity
strategy for calculating estimated load. Again, you don't need to set anything up, and in most cases, you can go with the default settings.
However, an option to change strategy is available if you want to explore other options.

Power information on equipment in the racks

The available capacity is defined by the physical breaker limits on the rack PDUs and receptacles in the racks, and upstream limitations
(UPS capacity), or you can choose to introduce additional design limit configurations if you like to plan capacity based on custom
predefined values on racks and rack PDUs.

1. Breaker size (derated capacity of the breakers in the power path)

2. UPS capacity (upstream limitation)
3. Design limits (on racks and rack PDUs)

Capacity strategies

See more about the strategies here.

Where are the calculations used?

The system calculates power consumption for estimated load and reserves capacity for advanced setups, including failover load, PSU
uncertainty, and distribution redundancy.
The tooltips provide an easy overview of power values relevant to your specific setup, showing the numbers and a graph (including
phase balancing bars).

Page 422
Examples of capacity calculations in various redundancy setups

These simple examples illustrate how the capacity is calculated in various redundancy setups.

Tooltip with capacity details

Capacity Management

Finding the best location for a new server

Understanding the new Capacity implementation

Tags

Creating tags
Assigning tags

Cooling

Working with Capture Index

Designs with perforated tiles on a raised floor
Working with the 3D temperature map

Reports

Capacity reports

Getting live data from external systems

Associating Live Data from an External System to the Layout

Impact Analysis on Virtual Machine Hosts

VMware integration enabling migration of virtual machines impacted by alarms

Locating virtual machines hosts with impact in the layout

IT Impact Simulation

Simulating impact
Configuring simulated impact layout
Filtering and finding equipment in simulated impact list
Exporting List View table

Page 423
Understanding estimated load and how it is calculated
The estimated load is a value used by the system to calculate how much capacity is used to be able to calculate and guide you on how
much capacity is available.

By default estimated load calculations are based on adjusted nameplate values. However, they can be different depending on the power
information available to the system in each rack and the power capacity strategy you have selected as the main strategy in Preferences
>Power Capacity.

The values and graphics in the Power overlay illustrate how close your estimated load is to the breaker capacity or design limit based on
your predefined thresholds.

See the introduction to the different strategies below to learn how they work and see the consequences of each strategy to the
calculation of your estimated load here.

Adjusted nameplate

You can reduce the manufacturer's nameplate value to the adjusted value when you know the actual power consumption of the product
and allow the system to perform more precise calculations. The adjusted nameplate value is more precise than the manufacturer's
nameplate as it is the actual known peak power draw of a server rather than the maximum load that the manufacturer guarantees the
server will not exceed. If the system doesn't have this value available, it will fall back on the manufacturer's nameplate.

Use the adjusted nameplate strategy when you know the adjusted nameplate values of your equipment and you want more precise
calculations than what the manufacturer's nameplate enables you to get (less pessimistic). The adjusted nameplate values must be
entered manually in the equipment's property settings.

If the system does not know about the phase connections, it will assume the server draws the load on all phases in a 3-phase setup and
triple the load to ensure the UPS/PDU can handle the load. To avoid this, configure how the servers are connected to the rack PDUs.

Predicted power

Power capacity calculations based on measured peak data from DCE or other external system integrations allow the system to predict
power based on already collected measurements. You can customize the default implementation of 30 days trending and fixed minimum
and maximum values (Preferences>External Systems>Measurement Trending).

Use the predicted power strategy if you have measured power values from your equipment and you want the capacity calculations to be
based on the measured values rather than nameplate values.

See more about predicted power here.

Contracted power (colo edition only)

The contracted power for the rack is distributed on the rack PDUs or receptacles and used as estimated load. The contracted power is
defined in the Colo overlay.

You cannot actively select this strategy in the system. It is used if you are a colocation provider running the DCO for Colo edition and
you haven't set up connected equipment with measured values from the contracted equipment.

Thresholds in Preferences>Power Capacity allow you to define the percentage of the contracted power to be used as estimated load.

Page 424
Adjusted nameplate or predicted power
The estimated load calculations always fall back on the best available information in the rack. Depending on the available information in
the rack, your calculations may switch strategy.

Adjusted nameplate

This illustration shows how, if the Adjusted Nameplate strategy is the main strategy (default), information available in the rack (left)
defines which strategy is enabled (right).

Predicted power

This illustration shows how, if the Predicted Power strategy is the main strategy, information available in the rack (left) defines which
strategy is enabled (right).

Page 425
Page 426
About predicted power

What is predicted power and how is it calculated?

Predicted power is a capacity strategy defining how estimated load is calculated. The calculations run in the background and affect
capacity values all over the DCO interface, such as impact and failover load.

Past trends in your equipment's measured peak power data from DCE or other external system integration are used to predict the future
power demand.

By default, the system bases the calculations on historic data from the last 90 days and predicts 30 days in to the future. You can adjust
these settings in Preferences>External Systems>Measurement Trending.

Note

The graphs here serve as examples only. They do not reflect any graphs available in DCO, in reports, orStruxureWare Portal.

The first graph illustrates the predicted power concept and the rest are examples of special scenarios to explain why your
calculations behave the way they do.

Predicted power (measured peak power consumption on rack PDU)

How is the prediction affected when adding the first server to an empty rack?

Due to the added load, the trend would become unrealistically steep over a period of 30 days. Therefore, a maximum factor of 1.5 (by
default) is used to keep the trend within a more appropriate range.

Note

When adding the new server, you may see some unexpected values while you're editing. This happens because the system
falls back on adjusted nameplate calculations until you save your changes or, if you have StruxureWare Data Center
Operation: Change, until you execute the pending change.

Page 427
Predicted power (when adding the first server to a rack)

How is the prediction affected when your measurements are stabile?

If the measurements have been stabile for the period of time the system has data for this rack, the system does not rely on this data to
be realistic until there's measured data for at least 90 days (default).

The trend line would become almost flat. Therefore, a minimum factor of 1.2 (by default) is used as a safety margin to keep the trend line
within a more appropriate range. A lower threshold of 1 also prevents the trend line from becoming negative.

However, if the measurements have been stabile for an even longer period of time (more than 90 days by default), the data is assumed
to be highly reliable and the safety margin is disregarded.

Predicted power (when measurements are stabile)

How is the prediction affected when removing a server from a rack?

Due to the reduction in load, the trend would drop unrealistically over a period of 30 days.

When you have removed a server from a rack and saved your changes, the trend line will no longer include values from the last 90 days
but only values since the server was removed to exclude values from removed equipment no longer relevant to you.

Page 428
About power supply unit uncertainty
Power Supply Unit (PSU) Uncertainty indicates an uncertainty in the power supply path as to which phase is carrying the load from a
server or chassis.

Many servers distribute the load evenly across multiple power supplies. However, some power supplies are most efficient when operated
at a higher load. This gives an incentive to turn off power supplies for servers or blade chassis with multiple power supplies, meaning the
real consumption may be higher on some power supplies than if the load was evenly distributed. Since DCO doesn't model power
supplies, it is unknown which power supplies may be turned off by the server or blade chassis. Furthermore, if the server or blade
chassis is connected to different phases, there's an uncertainty as to which phases are carrying the load.

To ensure you do not exceed your capacity, DCO reserves some of the capacity for PSU uncertainty which you can see expressed as
PSU uncertainty in the power tooltips.

Page 429
Redundancy examples
Depending on the the nature of the modeled equipment, redundancy settings, and power path setup in DCO, the capacity calculations
can get quite complex. If you have a similar setup as one of these simplified examples, they may help you understand where the
numbers in the tooltips come from.

Example 1: Multiple power supplies

The data center solution includes:

1 large server, 3000 W load

6 power supplies

Capacity values:

In previous versions of DCO, the Estimated Load would be very high. In the current version, it now works as follows:

Estimated Load: 500W on each connection (even load)

Estimated Load: 1000W on each connection (uneven load)

Power Supply Unit Uncertainty: 500W (uneven load)

If the server only uses half of the PSUs, the system must reserve up to: (3000W) / (6/2) = 1000W on each connection.
This implies a Power Supply Uncertainty of 500W (because 1000W - Estimated Load = 500W).

To minimize the impact of PSU Uncertainty on the PDU, the PSU Uncertainty be only be carried upstream to the PDU in case of phase
shifts.

Blade solutions:

If a blade enclosure includes bays powered by specific PSUs, the enclosure may only be using e.g. 2 out of 6 PSUs because
the other bays are empty. In this case, the PSU Uncertainty reservation done by the system might be too small!

Example 2: Classic 2N and multiple power supplies

The data center solution includes:

1 large server, 3000 W load

6 power supplies
3 connections to each of two separate rack PDUs

Capacity values:

Estimated load: 500 W on each connection

Failover load: 500 W on each connection

If the failover load can carry the full power supply uncertainty (as in this example), power supply uncertainty is not added to the
calculations.

Example 3: Reservation for Distribution Redundancy

The data center solution includes:

1 server, 1000 W load

2 connections to two different PDUs (L1 and L2)
Both PDUs are connected to the same parent PDU

Capacity values:

Load overview

Load type and phase PDU 1 PDU 2 Parent PDU

Estimated Load, L1 500 W 0W 500 W

Estimated Load, L2 0W 500 W 500 W

Failover Load, L1 500 W 0W -

Failover Load, L2 0W 500 W -

Reserved for Distribution Redundancy, L1 - - 500 W

Reserved for Distribution Redundancy, L2 - - 500 W

Page 430
On the parent PDU there is no failover load because additional load will not move to this PDU in case of a downstream failure. However,
a phase shift might happen in case of a downstream failure because of the mixed phases on the server. (If the server would have been
connected to only one single phase, there would be no need for reserving extra capacity.)

Example 4: Reservation for Distribution Redundancy with opposite effects

The data center solution includes:

1 server, 1000 W load

2 connections to two different PDUs (L1 and L2)

1 server, 600 W load

2 connections to two different PDUs (L2 and L1)

Capacity values:

Load overview

Load type and phase PDU 1 PDU 2 Parent PDU

Estimated Load, L1 500 W 300 W 800 W

Estimated Load, L2 300 W 500 W 800 W

Failover Load, L1 500 W 300 W -

Failover Load, L2 300 W 500 W -

Reserved for Distribution Redundancy, L1 - - 200 W

Reserved for Distribution Redundancy, L2 - - 200 W

The two servers partly cancel out the need to reserve extra capacity.

Page 431
Finding the best location for a new server
In Planning>Asset Provisioning, add or move servers and other equipment to the proposed best location in a rack and U-space by
using the options in the Installation Requirements pane and viewing the Provisioning Map and Provisioning Match.To provide the
system with the best foundation for the calculations, first add appropriate rack PDUs, UPS, and PDUs, and configure power paths.

1. Select a server in Genomes to add a new server or drag an existing server from the Navigation pane to move an existing
server into the layout.
2. Review the asset information in the Installation Requirements pane, assign tags, select the required redundancy and network
configuration, and select the amount to add as required.
3. Select Best Rack to have the system automatically calculate and select the rack and U-position that is best suited for the new
asset based on the capacity values (StruxureWare Data Center Operation: Capacity feature).
4. Click Show location to highlight the best location for the selected equipment in the layout.
5. Select Add Asset or Move Asset to allow the system to add or move the equipment to the best location in the layout.

The color-coded layout highlights rack positions 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 Provisioning Match pane and the tool tips in the
layout.

Page 432
Enabling provisioning match recommendations
Information about the selected rack is listed in the Provisioning Match pane to guide you on available space, power, and cooling as you
position equipment in the rack layout. For example, if you are using the Installation Requirements pane to look 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 Provisioning Match pane will help you investigate why it is not recommended.

Select the Provisioning Match 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 Genomes (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.

Page 433
Available copper-based network ports
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.

There is a sufficient amount of available copper ports to support the network requirements of the selected equipment.

There are available copper ports to support some of the network requirements of the selected equipment but the amount of available ports is
insufficient.

There are no available copper ports to support the network requirements of the selected equipment.

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.

Page 434
Available fiber-based network ports
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.

There is a sufficient amount of available fiber ports to support the network requirements of the selected equipment.

There are available fiber ports to support some of the network requirements of the selected equipment but the amount of available ports is
insufficient.

There are no available fiber ports to support the network requirements of the selected equipment.

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.

Page 435
Equipment fits into rack
This status message notifies you if there is sufficient space available in the selected rack.

There is sufficient space in the selected rack for the selected piece of equipment.

There is insufficient space in the selected rack for the selected piece of equipment.

Page 436
Floor supports weight of equipment
This status message notifies you if the floor's carrying capability supports the weight of the selected equipment.

The floor has sufficient carrying capability to support the weight of the selected piece of equipment.

The floor has insufficient carrying capability to support the selected piece of equipment.

Page 437
PDU supports rack PDUs voltage
This status message notifies you if the connected PDU is capable of supplying the voltage needed by the rack PDU.

The defined output voltage of the connected PDU and rack PDU is supported.

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.

Page 438
Rack airflow supports equipment
This status message notifies you if there is sufficient cooling available for the selected equipment in the rack.

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.

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.

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.

Page 439
Rack PDU supports equipment's load
This status message notifies you if the connected rack PDU is capable of supplying the power needed by the equipment.

The rack PDU supports the needed power supply to the selected equipment.

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.

Page 440
Rack PDU supports equipment's voltage
This status message notifies you if the connected rack PDU is capable of supplying if the voltage needed by the equipment.

The rack PDU supports the voltage needed by the selected equipment.

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.

Page 441
Rack supports equipment's redundancy
This status message notifies you if the redundancy of the selected equipment adheres to the redundancy of the selected rack.

The redundancy planned for the rack supports adding the selected equipment.

The rack 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.

The selected equipment requires better redundancy setup than is available according to the redundancy setup for the rack.

You may need to select a different piece of equipment requiring less redundancy and add to this rack.

Page 442
Rack supports equipment's Watts per U-height
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.

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.

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.

Page 443
Rack supports weight of equipment
This status message notifies you if the rack's carrying capability supports the weight of the selected equipment.

The selected rack has sufficient carrying capability to support the weight of the selected piece of equipment.

The selected rack has insufficient carrying capability to support the selected piece of equipment.

Page 444
Rack tags support equipment tags
This status message notifies you if there is a match between any tags assigned to the rack and tags assigned to the selected equipment.

Tags assigned to the selected rack and equipment are consistent.

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.

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.

Page 445
Rack supports equipment's plug type
This status message notifies you if the selected plug type is supported in rack. Strategy is available only when plug type is selected by
user.

The selected equipment's plug type is supported by rack pdus.

In case rack pdus are missing outlets type definition, equipment can be connected by selecting power phase.

The selected equipment's plug type is not supported by rack.

Page 446
Working with tags
Tags can be created and assigned to equipment in the floor or rack layout to categorize types of equipment.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 Installation Requirements pane.

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.

123 Steps to... See also

Assigning tags Creating tags

Tags can be assigned to equipment in the floor or rack layout to categorize types of equipment and plan the best Managing tags in the
place for new equipment automatically calculated based on the type of equipment. Equipment Browser or List
View
1. Right-click on a piece of equipment e.g. a server and select Properties. Tag properties
2. In the Properties dialog box, select the Tags section.
3. Select Add or Remove to assign a tag or annul an assignment.
4. 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.

Page 447
Creating tags
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.

1. In the Configure Tags dialog box, select Add to create new tags or categories.
2. Select if the tag is a strict requirement that must be met to be able to add a piece of equipment to a rack*.
3. Select a tag from the list and select Up or Down to move it and create a hierarchical structure according to your preferences.
4. If necessary, select a tag or category from the list and select Edit to modify it.
5. 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 provisioning match 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 provisioning match message will show with a yellow LED symbol next to it.

See also

Working with tags

Page 448
Managing tags in the Equipment Browser or List View
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.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.

1. 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.
2. 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.
3. 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.

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.

See also

Working with tags

Page 449
Tag properties
This section of the Properties dialog box lists tags associated with a component, e.g. a rack or server.

Name Defines the tag name.

Description Defines the value the tag provides.

Note

The listed information is defined by added tags in the Select Tags dialog box that are accessed by the Add button; Remove all
ows you to remove any listed tag.

Page 450
Simulating impact
The impact simulation provides an indication of issues or potential issues with the active power and cooling configuration in the event of
a failure.
You can use the simulate impact option to simulate a failure to determine whether the design is strong enough to fit the requirements of
the real-world infrastructure.

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.

123 Steps to...

Viewing the impact of a failing piece of equipment Figure

1
1. Select a piece of equipment in the rack view or in the floor layout that:
Supplies power to other equipment in the layout, for example a UPS, rack PDU or PDU
Supplies cooling to other equipment in the layout, for example a row-based cooling unit
2. Right-click it, and select Simulate Impact to simulate failure and see the impact (1)
In the Simulated Impact table (2), 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.

Note

If a piece of equipment has not been associated with a device, it will show as OK.

Viewing the impact of an active alarm

1. Select an alarm in the Alarms pane below the layout

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.

Simulated impact of cooling 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.

Simulated impact of power failure

Simulated impact of power failure on a selected PDU or UPS will give an indication of loss of redundancy, cooling (UPS) and power
supply.

On rack PDUs and paired receptacles the Impact description will show how the load of the simulated failed equipment distributes onto
the associated equipment if you have redundancy in your setup. This gives you an impression of any weak points in your design. In the
picture (2) you can see that the failure of one rack PDU will result in an increased load leading to a total of 109% on the associated rack
PDU.

In the Connected Breaker column you can se the which breaker is affected, the increased load and the exact location of the breaker.

Figure 2

Page 451
 See also

Filtering and finding equipment in simulated impact list

Exporting impact table

Configuring simulated impact layout

Configuring cooling impact preferences

StruxureWare Data Center Operation: Capacity

Page 452
Configuring cooling impact preferences
You can configure the thresholds for impact so the system reacts to impacts that are important to your physical infrastructure.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.

1. Select Tools > Preferences > Cooling Impact.

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

Note

If you select No limit, the system will not react to cooling impact.

See also

Simulating impact
Filtering and finding equipment in simulated impact list
Exporting impact table
Configuring simulated impact layout

Page 453
Configuring simulated impact layout
You can configure the layout of the Simulated Impact list to show equipment according to your preferences.

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.
Click on column header in the list to toggle sort order (ascending/descending).

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.

See also

Simulating impact
Filtering and finding equipment in simulated impact list
Exporting impact table
Configuring cooling impact preferences

Page 454
Exporting impact table
You can export the list of impacted equipment to a file.

1. Click Export.
2. 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.
a. 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.

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.

See also

Simulating impact
Filtering and finding equipment in simulated impact list
Configuring simulated impact layout
Configuring cooling impact preferences

Page 455
Filtering and finding equipment in simulated impact list
You can set a filter on the Simulated Impact list to show only the equipment that you want to see.In the Search... field of a column, start
typing some characters of the equipment you want to see. The table shows all items that contain the typed characters in the column that
is searched.

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.

See also

Simulating impact
Exporting impact table
Configuring simulated impact layout
Configuring cooling impact preferences

Page 456
Filtering network impact analysis
You can filter your network impact analysis to include only the key elements of your setup, for example your main servers and internet
access.

1. Right-click the equipment and select Properties > Properties (custom).

2. Type Network Marker in the Name column and define the equipment in the Text column, such as main server or internet
access.
3. Click OK.
4. Repeat for other key elements.

You will only get simulated network analysis on the equipment with the Network Marker custom property. Simulated impact analysis on
equipment other than the Network Markers will only include impact of power and/or cooling failure.

Note

To delete the Network Marker property, open Tools > Configure Custom Properties and right-click Network Marker in the
Custom Properties table to delete it. It will not suffice to delete it in the equipment's right-click menu.

Page 457
VMware integration enabling migration of virtual machines impacted by alarms
StruxureWare Data Center Operation 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 real-time
device alarm data from StruxureWare Data Center Expert or other monitoring system. This enables you to quickly analyze how an alarm
on one piece of equipment may impact other equipment located in the data center. Making this data available to a virtual machine
management system enables this system to automatically move the potentially impacted virtual machines to healthy hosts.

This feature requires a StruxureWare Data Center Operation: Capacity 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 StruxureWare Data Center
Operation: PRO Pack)
For further information about prerequisites for enabling this feature, select StruxureWare Data Center Operation: PRO Pack Stru
xureWare Data Center Operation: PRO Pack in the navigation menu.
VMware vCenter Server
You can configure the integration in StruxureWare Data Center Operation System Setup>External System Configuration.

If you connect to more than 5 vCenter servers, you may experience a performance decrease with the server communication.

Alarm and impact configuration in StruxureWare Data Center Operation

For each host for which you want to enable impact, you must set the properties to include it in the impact analysis in StruxureWare Data
Center Operation. 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 StruxureWare Data Center Operation, 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 StruxureWare Data Center Operation 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. However, it is possible to customize the critical alarm and threshold
configuration for migration of impacted servers.

See also

Associating Live Data from an External System to the Layout

Configuring VMware integration to automatically migrate virtual machines impacted by alarms
Locating virtual machines hosts with impact in the layout
Refreshing virtual machine host data
Disabling maintenance mode on a virtual machine host after the impact has been resolved
Virtual Machine Host Properties

Page 458
Configuring VMware integration to automatically migrate virtual machines impacted by alarms

Once this integration has been configured, physical location, alarm, and impact data is communicated from StruxureWare Data Center
Operation to the VMware vCenter server. Based on this data, the VMware environment is then able to move the relevant virtual
machines to healthy hosts.

To configure the integration between StruxureWare Data Center Operation and VMware vCenter Server:

1. Ensure you have the necessary user rights on the VMware vSphere Client. vMotion functionality is being utilized and must be
configured and enabled as well as user rights given.
2. In System Setup>External System Configuration, configure the server communication settings to allow StruxureWare Data
Center Operation to exchange data with the VMware environment.
a. 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.
b. 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.

Recommendation

If the Data Center Operation server is restarted, wait for several minutes before you make any changes to the vCenter
communication configuration.

Once you have set up this server communication, StruxureWare Data Center Operation displays virtual machine hosts in the Device
Association view. These discovered Virtual Machine hosts need to be associated with modeled servers in the DCO data center
model. Virtual Machine host data from the VMware vCenter Server is sent to StruxureWare Data Center Operation which, in return,
sends physical location, alarm and impact data of virtual machine hosts.

For each host for which you want to enable this feature, 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 and then enabling Ena
ble Power and cooling impact for this host.

Page 459
Locating virtual machines hosts with impact in the layout
When VMware integration and impact analysis has been configured, StruxureWare Data Center Operation shows virtual machine hosts
in the layout that have been associated with potentially failing equipment, e.g. a UPS, PDU, or rack PDU.

You can view impact on virtual machine hosts in the layout since associated hosts are highlighted on the modeled servers:

Red icon: Critically impacted virtual machine host. For example, if a critical alarm occurs on the power supply.

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.

Gray icon: Non-impacted virtual machine host.

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.

To locate a specific impacted virtual machine host in the layout:

1. Double-click the room in Navigation.

2. Right-click the virtual machine host in Navigation, and select Show in Layout to identify and highlight the server in the rack
layout with the associated host. Multiple devices can be associated to one server in the layout, for example a server discovered
through an ITO server, and a VMware host.

See also

Associating Live Data from an External System to the Layout

VMware integration enabling migration of virtual machines impacted by alarms
Configuring VMware integration to automatically migrate virtual machines impacted by alarms
Locating virtual machines hosts with impact in the layout
Refreshing virtual machine host data
Disabling maintenance mode on a virtual machine host after the impact has been resolved
Virtual Machine Host Properties

Page 460
Refreshing virtual machine host data
For integrations between StruxureWare Data Center Operation and VMware vCenter Server, the host data refreshes dynamically.

However, for integrations between StruxureWare Data Center Operation and Microsoft Virtual Machine Manager, the data is refreshed at
the configured frequency.

The StruxureWare Data Center Operation: PRO Pack Agent 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 StruxureWare Data Center Operation: PRO Pack. You will see an icon on the task bar when the agent is
running.

1. 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 Data Center Operation PRO Pack).
2. Define the interval of getting updated data from Virtual Machine Manager into StruxureWare Data Center Operation .

Updates include:

Virtual machine hosts: Addition/removal, switch between maintenance/normal mode

Virtual machines: Addition/move/deletion

Page 461
Disabling maintenance mode on a virtual machine host after the impact has been resolved
You can disable maintenance mode on a host when working in StruxureWare Data Center Operation as well as in the VMware
environment.

1. In StruxureWare Data Center Operation, identify the host in Navigation 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.
2. Right-click the virtual machine host in Navigation, and select Exit Maintenance Mode to disable the maintenance mode on the
host.

For information on how it is done in the VMware environment, refer to the VMware documentation.

Page 462
Virtual Machine Host Properties
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.

Page 463
Branch circuit monitoring
You must have a valid StruxureWare Data Center Operation: Capacity license to be able to configure Branch Circuit Monitoring.

Please note that Branch Circuit Monitoring only works for AC equipment.

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.

Branch circuit monitoring

Modular or non-modular power distribution

Modular power distribution

The Branch Circuit Monitoring configuration for modular PDUs is supported from StruxureWare Data Center Expert version 7.1.

When configuring Branch Circuit Monitoring, you configure the PDU breaker module number, which is necessary for the system's power
data configuration.

Measured Peak Power: When StruxureWare Data Center Expert integration has been configured, and the system starts retrieving
measurements, this field will automatically be populated with measurements.

Non-modular power distribution

Non-modular power distribution requires a bit more configuration. See Configuring branch circuit monitoring for more information.

Collecting multiple measurements for one component in the floor layout

In the non-physical representation in StruxureWare Data Center Expert, a physical PDU, RDP, or PP is represented as multiple
measurement points (devices).
In the physical representation in StruxureWare Data Center Operation, 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 Unass
ociated Devices to one PDU, RDP, or PP in the layout.

Modular breaker panel

Page 464
Page 465
Configuring branch circuit monitoring
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 StruxureWare Data Center Operation: Capacity 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).

1. Right-click a modular PDU in the layout, and select Properties.

2. Click Power and select output voltage.
3. In Power > Breaker Panel configure the connection between the breaker modules and the rack PDU.
4. Repeat the above step until all connections have been configured between the breaker modules and the rack PDUs.
5. Associate the corresponding PDU device to the PDU in the floor layout by dragging it from Unassociated Devices to the PDU
in the layout.

Figure 1 Modular Breaker Panel

Non-modular power distribution

If your data center configuration includes non-modular power distribution, you must associate devices and then configure the connection
between the expert sensors and the circuit numbers.

1. Choose Device Association in the Planning pane.

2. Associate a device to a PDU, RDP, or PP component in the floor layout by dragging it from Unassociated Devices to the
component in the layout.
3. Sensor Mapping will now appear in the right-click menu of the associated component.
4. Add sensors by clicking

. Use Ctrl-click to add multiple sensors at a time. You can also use the search bar.
5. The sensors can now be found in the Sensor Mapping table. Click Breaker panel and Position and choose the power values
from the drop down menu.
6. 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.

Notice how the circuit numbers in the breaker panel (Figure 2) match the circuit numbers in Sensor Mapping (Figure 3).

When you have saved your configuration, and the system has retrieved the first measurements from StruxureWare Data Center Expert,
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.

Page 466
Figure 2 Non-modular Breaker Panel

Figure 3 Sensor Mapping

Note

The measured values in Figure 3 are instant values from StruxureWare Data Center Expert whereas the measured values in

Page 467
 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 StruxureWare
Data Center Operation server gets data from StruxureWare Data Center Expert), 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.

See also

Branch circuit monitoring

Configuring power connections
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

Page 468
Working with branch circuit monitoring
When you have configured the Branch Circuit Monitoring, you can work with the StruxureWare Data Center Operation: Capacity 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 Unassociated Devices view and are not
included in the impact analysis.

Page 469
Advanced power configuration
Power cable connections between rack PDUs and servers are automatically calculated by default.

Turning off the automatic cable connections allows you to overrule the default settings to manually configure cable connections. This is
useful for example when configuring an already running data center with a power configuration that is not the most efficient. Once you
have modeled the data center in StruxureWare Data Center Operation, you can use the capacity features to identify and optimize the
design.

Configuration
Toggling cable connection settings is available in Tools>Preferences>Cable Connection if you have StruxureWare Data Center
Operation: Capacity installed.

1. Open Tools>Preferences>Cable Connection.

2. Define the default power connection setup for a server when it is added to the layout from Genomes.
In Cable Connection when moving a server, select Auto calculate cable connection or No cable connection.
3. Define the default power connection setup for a server when it is added to the layout from another position in the Rack Layout o
r Navigation.
In Cable Connection when moving a server, select Auto calculate cable connection or No cable connection.

Usage

When you configure manual cable connections, it is important that you remember that any server you add or move to a rack must be
manually connected to a rack PDU immediately. Otherwise, you will see too high load values because of the way the system works. If
the system does not know about the phase connections, it will assume the server draws the load on all phases in a 3-phase setup and
triple the load to ensure the UPS can handle the load.

Note

If you add equipment using the rack advisor functionality in the Installation Requirements pane, cable connections are
automatically calculated regardless of the selection of cable connection preferences.

Page 470
Capacity history KPIs over time
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 StruxureWare Data Center Operation: Capacity feature.

Once you have enabled the feature and configured when 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 or read about the DCO web service API here.

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.

123 Steps to...

Setting up the system to save KPI data

In Tools>Preferences>Capacity History, define the KPI data recordings.

1. In Record data, select the interval between the recordings, e.g. Daily.
2. 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 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

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.

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.

Page 471
Capacity history KPI description
Capacity history data captured in StruxureWare Data Center Operation on a daily base:

Capacity History Data Type (KPI) Area/license Description Data Equipment

Level

Available U-space (AVAILABLE_USPACE) Capacity The currently available rack u-space Location, Room,
Rack

Reserved U-space (RESERVED_USPACE) Capacity The rack u-space currently reserved by Location, Room,
planned changes Rack

Total used U-space (USED_USPACE) Capacity The currently used rack u-space Location, Room,
Rack

Available copper (AVAILABLE_COPPER_NETWORK) Capacity The number of available copper Location, Room,
network ports in layer 2 & 3 network Rack
equipment

Available fiber (AVAILABLE_FIBER_NETWORK) Capacity The number of available fiber network Location, Room,
ports in layer 2 & 3 network equipment Rack

Available network ports (AVAILABLE_NETWORK_PORTS) Capacity The number of available network ports Location, Room,
in layer 2 & 3 network equipment Rack

Used copper (USED_COPPER_NETWORK) Capacity The number of used copper network Location, Room,
ports in layer 2 & 3 network equipment Rack

Used fiber (USED_FIBER_NETWORK) Capacity The number of used fiber network ports Location, Room,
in layer 2 & 3 network equipment Rack

Used network ports (USED_NETWORK_PORTS) Capacity The number of used network ports in Location, Room,
layer 2 & 3 network equipment Rack

Ambient temperature ((AMBIENT_TEMPERATURE) Capacity The calculated ambient ("background") Room

temperature. This is the temperature in
the room when not in the immediate
vicinity of racks, coolers etc.

Cold aisle capture index (COLD_AISLE_CAPTURE_INDEX) Capacity The cold aisle capture index UPS, Rectifier,
Rack

Cooler capacity (COOLING_CAPACITY) Capacity The total capacity of coolers Location, Room

Cooler load (COOLING_LOAD) Capacity The calculated load of coolers Location, Room,
CRAC

Hot aisle capture index (HOT_AISLE_CAPTURE_INDEX) Capacity The hot aisle capture index UPS, Rectifier,
Rack

Inlet temperature (INLET_TEMPERATURE) Capacity The calculated inlet temperature UPS, Rectifier,
Rack

Auxiliary load connected (AUXILIARY_LOAD_CONNECTED) Capacity Get the estimated load for auxiliary Room
equipment. This is equipment that is
not in racks, such as coolers

Estimated Load (ESTIMATED_LOAD) Capacity Get the estimated load Location, Room, Ca
ge, UPS, Rectifier,
PDU, Rack, Rack
PDU, Internal
Breakers

Estimated failover load (ESTIMATED_TRANSFERRED_LOAD) Capacity Estimated failover load Location, Room,
UPS, Rectifier, PDU
, Rack PDU

Estimated PSU uncertainty (RESERVED_FOR_PSU_UNCERTAINT Capacity Estimated power reserved for PSU Location, Room,
Y) uncertainty UPS, Rectifier,
PDU, Rack, Rack
PDU

Estimated distribution redundancy (RESERVED_FOR_DISTRIBUTI Capacity Estimated power reserved for Location, Room,
ON_REDUNDANCY) distribution redundancy UPS, Rectifier,
PDU, Rack, Rack
PDU

Measured peak load (MEASURED_PEAK_LOAD) Capacity Get the measured peak power Location, Room,
UPS, Rectifier,
Rack, Cage, PDU,
Rack PDU, Internal
Breakers, Power
Outlets

Measured failover load (MEASURED_TRANSFERRED_LOAD) Capacity Measured failover load Location, UPS,
Rectifier, PDU

Page 472
Measured peak load per phase(MEASURED_PEAK_LOAD_PER_P Capacity Measured peak load per phase for UPS, Rectifier,
HASE) three phase equipment. PDU, Rack PDU

Power capacity (POWER_CAPACITY) Capacity Power capacity Location, Room,

UPS, Rectifier, PDU

Total estimated load (TOTAL_ESTIMATED_LOAD) Capacity Get the estimated load for equipment in Location, Room,
racks and cages Rack, Cage

Total load connected (TOTAL_LOAD_CONNECTED) Capacity Get the total nameplate load of all Location, Room,
equipment Rack

Estimated load per top redundancy item (ESTIMATED_LOAD_PER_ Capacity Estimated load for each top level Rack
TOP_LEVEL_ITEM) redundancy item of a rack

Estimated failover load per top redundancy item (FAILOVER_LOAD Capacity Estimated failoverload for each top Rack
_PER_TOP_LEVEL_ITEM) level redundancy item of a rack

Estimated PSU uncertainty per top redundancy item (RESERVED_F Capacity Estimated power reserved for PSU Rack
OR_PSU_UNCERTAINTY_PER_TOP_LEVEL_ITEM) uncertainty for each top level
redundancy item of a rack

Measured average load per top redundancy item (MEASURED_FOR Capacity Measured average load for each top Rack
_TOP_LEVEL_ITEM_AVERAGE) level redundancy item of a rack

Measured peak load per top redundancy item (MEASURED_FOR_T Capacity Measured peak load for each top level Rack
OP_LEVEL_ITEM_PEAK) redundancy item of a rack

Free outlets (FREE_POWER_OUTLET_CAPACITY) Capacity Number of free rack PDU power outlets Location, Room,
grouped by outlet type Rack, Rack PDU,
Internal Breakers

Used outlets (USED_POWER_OUTLET_CAPACITY) Capacity Number of used rack PDU power Location, Room,
outlets grouped by outlet type Rack, Rack PDU,
Internal Breakers

Total number of outlets Capacity Total rack PDU power outlets capacity Location, Room,
grouped by outlet type Rack, Rack PDU,
(TOTAL_POWER_OUTLET_CAPACITY) Internal Breakers

Cancelled work orders (CANCELLED_WORK_ORDERS) Change Total number of cancelled work orders Location, Room

Work orders not started (NOT_STARTED_WORK_ORDERS) Change Not started work orders, which are not Location, Room
overdue

Work orders in progress (IN_PROGRESS_WORK_ORDERS) Change In progress work orders Location, Room

Overdue work orders (OVERDUE_WORK_ORDERS) Change Overdue work orders Location, Room

Completed work orders (COMPLETED_WORK_ORDERS) Change Total number of completed work orders Location, Room

Total work orders (TOTAL_WORK_ORDERS) Change Total number of work orders Location, Room

Revenue space (ROOM_CAGES_AREA) Co-Lo Room cages area. Location, Room

Sold space (ROOM_CLOSED_AREA) Co-Lo Room area sold to customers Location, Room

Power contracted with customers Co-Lo Power already sold to customers for all Location, Room
(ROOM_CLOSED_POWER_SOLD) equipment in a room.

Closed racks (ROOM_CLOSED_RACKS) Co-Lo Racks in room sold to customers. Location, Room

Floor-mounted area (ROOM_FLOOR_MOUNTED_AREA) Co-Lo Room floor standing equipment total Location, Room
area

Internal space (ROOM_INTERNAL_AREA) Co-Lo Room internal area. Location, Room

Internal racks (ROOM_INTERNAL_RACKS) Co-Lo Racks in room for internal usage. Location, Room

Open space (ROOM_OPEN_AREA) Co-Lo Room area open for new customers. Location, Room

Open racks (ROOM_OPEN_RACKS) Co-Lo Racks in room open for new customers Location, Room

Racks utilization (ROOM_RACKS_UTILIZATION) Co-Lo Room racks utilization percentage. Location, Room
Racks utilization is sum of open, closed
and reserved racks divided by total
number of racks.

Reserved space (ROOM_RESERVED_AREA) Co-Lo Room area reserved for potential Location, Room
customers.

Power reserved for customers Co-Lo Power reserved for potential customers Location, Room
(ROOM_RESERVED_POWER_SOLD) for all equipment in a room

Reserved racks (ROOM_RESERVED_RACKS) Co-Lo Room area reserved for potential Location, Room
customers.

Sellable area (ROOM_SELLABLE_AREA) Co-Lo Sellable area: sum of Open, Closed Location, Room
and Reserved area.

Page 473
 Space utilization (ROOM_SPACE_UTILIZATION) Co-Lo Sellable area as a percentage of total Location, Room
room area.

Closed racks (standalone) Co-Lo Racks in room sold to customers. Only Location, Room
(ROOM_STANDALONE_CLOSED_RACKS) standalone (outside cages) racks are
counted.

Internal racks (standalone) Co-Lo Racks in room for internal usage. Only Location, Room
(ROOM_STANDALONE_INTERNAL_RACKS) standalone (outside cages) racks are
counted.

Open racks (standalone) (ROOM_STANDALONE_OPEN_RACKS) Co-Lo Racks in room open for new Location, Room
customers. Only standalone (outside
cages) racks are counted.

Total racks (standalone) (ROOM_STANDALONE_RACKS) Co-Lo Room total racks number. Location, Room

Racks utilization (standalone) Co-Lo Room racks utilization percentage. Location, Room
(ROOM_STANDALONE_RACKS_UTILIZATION) Racks utilization is sum of open, closed
and reserved racks divided by total
number of racks. Only standalone
(outside cages) racks are counted.

Reserved racks (standalone) Co-Lo Room area reserved for potential Location, Room
(ROOM_STANDALONE_RESERVED_RACKS) customers. Only standalone (outside
cages) racks are counted.

Room area (ROOM_TOTAL_AREA) Co-Lo Room total area. Location, Room

Total contracted power (ROOM_TOTAL_POWER_SOLD) Co-Lo Total power sold to customers for all Location, Room
equipment in a room.

Total racks (ROOM_TOTAL_RACKS) Co-Lo Total number of racks in a room Location, Room

Above temperature threshold Cooling Relative time that the temperature for a Rack
(ABOVE_TEMPERATURE_THRESHOLD) Optimize rack exceeds its threshold (with a
higher value)

Below temperature threshold Cooling Relative time that the temperature for a Rack
(BELOW_TEMPERATURE_THRESHOLD) Optimize rack exceeds its threshold (with a lower
value).

PUE Energy The PUE This is for energy systems Location

Efficiency only

Total network ports (TOTAL_NETWORK_PORTS) Operations The total number of network ports in Room, Rack
layer 2 & 3 network equipment

Total U-space (TOTAL_USPACE) Operations The total rack u-space Location, Room,
Rack

Total weight (TOTAL_WEIGHT) Operations The total weight of equipment Rack

Server quantity (SERVER_QUANTITY) Operations The number of servers mounted in Location, Room,
racks Rack

Total IT Assets (TOTAL_ITOASSETS) IT Optimize Total number of servers and blades in Location, Room
a room

Not associated IT Assets (UNPLACED_ITOASSETS) IT Optimize Number of not associated ITO assets Location, Room

IT Asset CPU utilization (UTILIZATION_CPU_AVG) IT Optimize Get the average CPU utilization Location, Room
(average of associated)

IT Asset Power utilization (UTILIZATION_POWER_AVG) IT Optimize Get the power utilization (sum of Location, Room
associated averages)

Consolidation Candidates (NUM_CONSOLIDATION_CANDIDATES) IT Optimize Number of retirement candidates Location, Room

(server utilization between 2% and
10%)

Retirement Candidates (NUM_RETIREMENT_CANDIDATES) IT Optimize Number of retirement candidates Location, Room

(server utilization below 2%)

Consolidation Candidates costs IT Optimize The power costs for consolidation Location, Room
(POWER_COSTS_CONSOLIDATION_CANDIDATE_PRICE) candidates

IT Asset costs (tag) (ENERGY_COST_PER_TAG) IT Optimize Power costs for all servers with a given Location, Room
tag, per room

IT Asset costs (POWER_COSTS_PRICE) IT Optimize The power cost setup for a room Location, Room

Retirement Candidates costs IT Optimize The Power Costs for retirement Location, Room
(POWER_COSTS_RETIREMENT_CANDIDATE_PRICE) candidates

Capacity history data discontinued in version 8.0:

Page 474
Capacity History Data Type (KPI) Area/license Description Data
Equipment
Level

Measured A-Feed average Capacity Get the measured average power on the A-feed UPS, Rack
(MEASURED_A_FEED_AVERAGE)

Measured A-Feed peak Capacity Get the measured peak power on the A-feed UPS, Rack
(MEASURED_A_FEED_PEAK)

Measured B-Feed average Capacity Get the measured average power on the B-feed UPS, Rack
(MEASURED_B_FEED_AVERAGE)

Measured B-Feed peak Capacity Get the measured peak power on the B-feed UPS, Rack
(MEASURED_B_FEED_PEAK)

Total reserved capacity Capacity Get the reserved capacity cf. capacity groups plus auxiliary Location, Room
(TOTAL_RESERVED_CAPACITY) equipment such as coolers

Page 475
Capacity reports
You can generate capacity reports showing an overview of the capacity and capacity over time.

Power Capacity report

You can generate a report with power data, i.e. available estimated load and planned estimated load.

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 StruxureWare Data Center Operation: Capacity license.

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.

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

Capacity Forecast report

You can generate a Power Capacity Forecast Report which is based on the power configuration from the modelled rooms and the
planned changes within the rooms. The report has a few parameters where Forecast Date will take work orders planned until and
including the date selected. Redundancy Selector will be used in calculating the capacity for both actual and forecast. The report will
show the results both at room, location and global level.

Rack PDU Power Overview report

For new rack PDUs with outlets and banks definition user can generate detail report with power capacity values on banks, outlets.
Report can also show measured peak value for each bank, outlet if 'Show measurements' checkbox is enabled. For better phase
recognition user can set individual color in the options section. Report can be generated directly for rack or rack PDU in the floor overlay
by selecting it from context menu.

See also

Working with Reports

Page 476
How power measurements are processed in Data Center Operation

Overview

Power measurements can come from two sources:

Data Center Expert

The ETL import database. This includes importing manual measurements by uploading an Excel sheet.

The measurements tracked in DCO are:

Peak power
Average power
Peak amps
Predicted power, calculated based on the historical peak power measurements

The most interesting value for managing the data center is the peak power measurement observed within the last 30 days
(configurable). This is the value typically shown in the user interface.

Predicted power is also actively used throughout DCO as estimated load. You can set this under Power Capacity; set Estimated Load
Strategy to Predicted Power. When this strategy is used, power measurements are prioritized in capacity planning calculations.

The flow of power measurements is designed around the integration with Data Center Expert. The ETL integration tries to mimic the
same behavior.

Polling for measurements

After DCO polls DCE for peak power measurements every 5 minutes (configurable), two things can happen:

If it has been less than 24 hours since a full update of the power measurements was done, only the peak measurements are
updated.
If it has been more than 24 hours since a full update of the power measurements was done, there is a full update (peak and
average for the last 24 hours).

Peak update of power measurements

DCO maintains values for the highest peak measurement observed over the last 30 days, configurable for the integration with DCE.

During a peak update, this value is updated if a larger peak measurement was found, that is, recent measurements affect the peak
value.

If a larger peak value was found, the predicted power values are recalculated.

Full update of power measurements

Measurements during the last 24 hours are polled, then peak and average measurements are stored as historical values in the
database.

If there are no measurements for devices, and there are already historical measurements, the historical value is copied and reused it as
the measurement for the last 24 hours.

The highest observed peak values for both amps and power are recalculated.

A job is started that recalculates the predicted power values.

Special cases

There is a special case when there have been no measurements for several days. This typically happens right after you set up DCO, or
when the server was stopped for multiple days. DCO performs a catch-up process to get measurements from as far back as 30 days
(not configurable).

Catch-up means that DCO looks at the latest measurement, up to 30 days back, and the time this measurement was taken. Then the
measurements for 24 hours immediately after that are polled. If no measurement is found, the existing measurement is duplicated with a
new timestamp. This process is repeated when there is less than 24 hours between the current time and the last measurement time.

Examples

There are no historical measurements because the DCO server was just installed and started: 30 day catch-up is performed

The server was shutdown for 10 days: 10 day catch-up is performed

When are measurements reset?

Page 477
The 30 days that the peak calculations look back is configurable for the DCE integration.

Sometimes, when making changes to the database, the historical peak values are no longer interesting. There are two cases where
DCO marks measurements older than some timestamp as invalid.

When equipment is removed from a rack

When you remove equipment from a rack, the historical measurements are no longer valid. DCO saves a timestamp for the
most recent time when equipment was deleted from a rack, and does not look further back than this timestamp for the
measurements it uses. Just after a delete, no measurement is available, so DCO shows the previous measurement until a
new one is available. When the measurements comes from an integration with DCE, this typically happens within a few
minutes.

If no measurement is available within the next 24 hours, the previous measurement will be used for that day, even if it was
taken before the timestamp, since no other measurement is available. This is important to note when importing manual
measurements through Excel, or when using the ETL database in a non-automated way.

When the assigned customer changes

The process described above happens for relevant equipment when you update the customer assigned to a rack or cage.

Another thing to note is when equipment is planned to be added using work orders (requires the Change module), DCO tries to include
the equipment in the capacity calculations. Since the equipment is not installed yet, it has not yet affected the measurement; when using
the predicted power capacity strategy, the adjusted nameplate of planned equipment is added to the estimated load.

What happens when the highest observed peak was 30 days ago?

Since the user interface shows the highest peak over the last 30 days, it is interesting to understand what happens when the highest
peak measurement becomes older that 30 days. In the typical setup with DCE, there are unique measurements for each day; when the
previously highest peak becomes 31 days old, the new highest peak from the last 30 days is shown.

How does this work with manual breaker panel measurements?

This is, in principle, the same thing that happens when you have manual breaker panel measurements uploaded in an Excel sheet.
However, with manual measurements, a new measurement is typically not made every day. This means the previous measurement is
duplicated for each day you do not have a measurement.

If you observe and import a measurement of 10 amps on day 1, and import an updated measurement of 5 amps on day 15, the
measurement from day 1 is duplicated for each day from 2 to 14. Only after 30 days, on day 45, will the 10 amps measurement leave the
history and the value in DCO change to 5 amps.

Page 478
StruxureWare Data Center Operation: Change
StruxureWare Data Center Operation: Change 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.

Plan (1)
The Data Center Planner manages new and existing work orders. New work orders are created using work order templates, recorded
adds, moves and changes, and custom tasks created by the user.

The planning feature supports advanced workflows with parallel and sequential workflows, and the option to assign the entire work order
or individual tasks to a group of users.

Execute (2)
You can execute work orders using the desktop client, or the web client running on a smart phone, following the process and workflow
defined by the work order planner.

The system automatically updates the data center model as work orders and tasks are executed.

Monitor (3)
You can monitor and plan the overall progress of projects in the Changes perspective, available in the Analytics > Changes option in
the Application bar. Drill down into areas of interest by a number of categories, such as work order assignee, project code, and location.
For example:
Allocate resources based on the number of work orders assigned to a resource.
Avoid scheduling conflicts.
Handle work order peaks.
Create reports about work order actions in the Analytics >Reports option in the Application bar.

IT Service Management System Integration (4)

Integration with the BMC Remedy Change Management system allows you to cover the entire change workflow from StruxureWare Data
Center Operation without running Remedy.

Figure 1

Figure 2

Page 479
Figure 3

Figure 4

Page 480
Change Management

Change management overview

Planning changes to rack equipment

Work Orders

Working with work orders

Identifying work order task and equipment relationship
Configuring work order administrative settings

Remedy Integration

Integration with the Remedy change management system from BMC

Reports

Work order reports

Page 481
Change management overview
The Changes perspective, available in the Application bar Analytics > Changes option, 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. Work orders without tasks in the system do not appear in this perspective.

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 (user or group), project code, time,
etc.
In the Tasks Overview, navigate and zoom in on the time line. 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.
You can also filter 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

Tip: Over time, the amount of tasks in the system will grow. You can select Hide completed projects to see only the active
tasks.

Editing

The Work Order Tasks Overview pane 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 the 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 assigned to a specific resource.

Page 482
Rack equipment planning
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).
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.

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.

Page 483
Planning changes to rack equipment
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.

1. In Planning>Data Center, open the Work Order Editor pane to plan changes to the rack-mountable equipment:
a. Add or move equipment by dragging it from the Genomes pane or another location in the Layout or Navigation panes
or by using the Installation Requirements pane.
b. Delete equipment by right-clicking it and selecting Delete.

Tip

You can move or delete multiple items at the same time by using Ctrl-click or Shift-click.

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.

1. Save and close the Work Order Editor pane.

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

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.

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.

Page 484
Equipment stages
When planning rack equipment, you can see equipment represented in various stages in the layout. The graphical representation varies
slightly at different zoom levels.

Layout

Equipment Description
Stage

Existing Equipment shown in its current location, with no action pending. It displays in dark gray, indicating that it occupies the position
shown.

Pending Move Equipment shown in its current location but has a move pending. It displays in blue with an arrow up, until you select to save,
(Source) 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.

Pending Move Equipment shown in its target location for a pending move. It displays in green with an arrow down, until you select to save,
(Destination) / indicating that the position is reserved, but that you can still edit it. After you have saved, the color will change to light gray,
Planned indicating that you can no longer edit it.

Pending Add 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.

Pending 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
Deletion 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.

Page 485
Working with work orders
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.

Each work order has its own unique workflow. To create or modify a workflow, click the Workflow icon on the work order header -->

to open the Work flow Editor.

You can view work orders in a list without opening the Work Order Editor in Planning > Data Center (and read-only in Operations >
Data Center) in the Work Orders pane if you have StruxureWare Data Center Operation: Change 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.

Edit or view a listed work order

1. In the Work Orders pane, double-click a listed work order.

2. Edit or view the selected work order in the Work Order Editor.
a. Edit the work order summary and details.
b. Add, edit, or delete task details.

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.

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.

Set up strict work orders

You can set up strict work orders that require work orders to follow a selected process. The option to select 'No process' when a work
order is created is not available when this setting is applied in the Tools > Preferences > General option.

Page 486
Creating a controlled automated work order
O pen the Work Order Editor in the Planning > Data Center perspective to create a controlled automated work order and make
changes to the layout. Any changes done to add, move, or delete equipment are recorded, and work order tasks for implementing these
changes in the data center are automatically generated.

Working with the controlled automated work order process

1. In Planning > Data Center, open the Work Order Editor.

2. Edit the work order details, such as summary, assignee (User or Group), needed by date, and priority.
3. Select a project code (not required).
Use the project code to identify the work order type. You can filter the work order list using this code. To add a new code, click
the plus icon and type the code.
4. Type a comment, (not required).
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 when it is completed.
5. Add, move, or delete equipment in the layout (drag and drop).
6. Edit the task details, if needed.
7. 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. 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 automatic work order recording when adding, moving, or deleting equipment in the layout, close the Work Order Editor.

Automated work order with network

Page 487
Creating a custom work order without recorded tasks
You can create, review, and edit custom work orders without recorded tasks.

1. In Planning > Data Center, click the create new work order icon to open the Work Order.

2. Select No process to add tasks to the work order. Selecting a process may restrict whether you can add tasks to the work order.
3. Edit the work order details, such as summary, assignee, needed by date, and priority.
4. Select a project code (not required).
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.
5. Type a comment (not required).
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 when it is completed.
6. Click Create new task if you want to add one or more tasks.

7. Edit the task details.

8. Add more tasks if needed.
9. Save and close the Work Order.

Page 488
Define a Work order workflow
How to build a work flow in the Work Order Work Flow Editor

1. Click the Open Workflow View icon in the header of the Work Order.

2. Tasks are run in parallel by default. Select a task, and drag and drop a connection from one to task to another to create a
sequential flow.
Note: Tasks in a sequential flow can not be completed until all previous tasks have been completed.
3. Add a placeholder for a predefined process, if desired.
4. Select icons on the work flow editor to add start and end nodes, if desired.
5. Save and Close the Work Order.

The system automatically creates the work order.

To exit the work order recording mode and execute planned changes, click Cancel in the Work Order.
When you execute a planned change, any associated work orders are automatically updated. 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.

Page 489
Identifying work order task and equipment relationship
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. 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.

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.

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 Layout icon next to the task for which you want to see the related equipment.

Page 490
Creating and applying work order processes
Working with change management in a data center often requires certain tasks to be repeated regularly. In StruxureWare Data Center
Operation, work order processes and the option to schedule recurring work orders help you manage repetitive tasks.

A work order process is a list of tasks in a defined flow that you can save and reuse for other similar work orders. As you add to it, your
processes library will grow into a valuable collection of best practices.

Creating a work order process is very similar to creating a work order. The only difference is the list of tasks and the flow you create in a
process can be saved and used again and again.
Creating a work order process

1. Click the Create new Work Order Process icon

in the menu bar.

2. Fill in the work order process properties, such as name, priority, project code, etc.
3. Add one or more tasks to the work order process.
4. Open the Work Flow Editor.
5. Define the workflow.
6. Click the Create work order recording task icon

to insert tasks that are work order specific, if needed.

For example, the process to install a server is always the same, but the rack, u-position, etc. is different every time.
Note: You can only add one work order recording to a process, however, you can add many tasks within that recording.

Work Order Process View

The saved work order process appears in the list of available processes when you create a new work order. and in the Work Order
Processes view.

Note: The Work Order Processes view is not displayed by default. Go to Window > Show View > Work Order Processes to open it.

Applying a work order process

1. Right-click one or more pieces of equipment or a room layout, and select Apply Work Order Process.
2. In the Work Order Editor, adjust the text for the work order if needed.

Tip

Ctrl-click or Shift-click to select multiple items at the same time.

Page 491
Work order reports
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.

Work Order List report

A summary list of work orders in the system.

Work Order Details report

A list of work orders, including details about status, description, and comments.

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 p
ane. 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.

Page 492
Deleting old work orders
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.

Note

Use this operation with caution. Once performed, there is no way of retrieving deleted work orders.

1. Select System Setup>Work Order Cleanup.

2. Type the minimum age of the old work orders to be deleted.
3. 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.

Page 493
Configuring work order administrative settings
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.

Page 494
Scheduling work order recurrence
Often, working with change management in a data center requires certain tasks to be repeated.

In StruxureWare Data Center Operation, work order processes 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.

Follow the below instructions or watch this video tutorial to learn how to configure recurring work orders.

Configuring a work order recurrence schedule

1. Open the work order for which you want to schedule recurrence.
2. Click the Administrative Settings icon and select Schedule recurrence.
3. 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.

Page 495
Setting up automatic email notification on work order completion
The system can automatically send an e-mail notification to relevant individuals when a work order status changes to Completed.

For this feature to be available, e-mail settings must have been configured as well as e-mail address for the users.

1. Open the work order for which you want to configure e-mail notification.
2. Click the Administrative Settings icon and select E-mail notification.
3. 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.
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 must have been set up but no further configuration is needed.

Page 496
Locking a work order
You can activate the lock on a work order or work order process, locking all work orders created based on that process. Locked work
orders cannot be edited.
Locking a work order

1. Create a new work order, or open the work order you want to lock.
2. Click the Administrative Settings icon and select Lock on save.
3. Edit the work order details if needed.

The lock will be applied when you save the work order. A lock icon will be display in the work order heading. Locked work orders cannot
not be unlocked and edited.

Creating a locked work order process

1. Create a new work order process in Tools > Create new Work Order Process, or open the work order process you want to
lock.
2. Fill in the work order process properties, such as name, priority, project code, etc.
3. Add one or more tasks to the work order process.
4. Click the Administrative Settings icon and select Lock on save.

The locked work order process now appears in the list of available processes when you right-click a piece of equipment or a room layout
and select Apply Work Order Process.

Page 497
User roles when working with work orders
There are three principal roles when working with work orders:

Work order process administrator, a specific user permission (under Global Permissions in Administration > Users or User
Groups in the web client)
Work order planner, a specific user permission
Users that perform the work order tasks. This can be any user.

The work order process administrators handle creating the general processes the work orders should follow.

The work order planners create and plan work orders. A work order planner can change or replan all work orders, and update the status
of tasks.

A user that has a task assigned to them can execute the task and update the status of that task.

An unassigned task is implicitly assigned to the user or group that the work order is assigned to.

When a task or work order is assigned to a user group, any user in that group can assign the work order to themselves. Afterwards, the
task can be updated as usual.
As a short cut, if a task is updated without assigning it first, the task is automatically assigned to the user who updated it. There is an
exception: when a Work Order planner updates a task in the desktop client, they can set the task status on behalf of another user.

Page 498
Executing work orders using the web client on mobile
You can execute work orders in the web client on your mobile device.

Work orders overview page

Work orders viewed in web client are grouped into 3 categories:

1-Assigned to me: Work orders that are assigned to you, or have tasks assigned to you.

2- Assigned to my group: Work orders that are assigned to the group you are in, or contain tasks assigned to a group you are in.

3- Others: Work orders that are not assigned to you or to any groups you are in.

Work orders can also be filtered by work order name or work order number.

Page 499
Work order details page

The work order details page contains the list of tasks in work order with detailed information. Tasks are grouped in 4 categories:

1- Tasks that are not overdue, and not started or in progress.

2- Overdue tasks

3- Completed tasks

4- Cancelled tasks

Task details page

Page 500
The task details page contains more detailed information about a specific task, with the option to navigate to the asset related to task,
assign the task to yourself, and change task status.
Inventory link

A task can be linked to an asset in rack. The link is shown in the task details page. The link will navigate to rack view with selection of
the related asset.

Assign to me/Unassign

You can assign a task to yourself if it is unassigned or assigned to a user group you are in. You can unassign yourself from the task if
needed.

Page 501
Page 502
Change status

You can execute the task by changing the task status.

Page 503
Page 504
Note

Note

Page 505
Work order task status
Work order tasks can have the following status:

Not started task

In progress task

Completed task

Cancelled task

Blocking task. Some other tasks are dependent on this task

Blocked task. Task cannot be executed before blocking tasks are executed

Page 506
Integration with the Remedy change management system from BMC
This system integration ensures relevant information is shared between StruxureWare Data Center Operation and the most commonly
used process management system in the market.

A valid StruxureWare Data Center Operation: Change license allows you to use this feature.

Integration version compatibility

DCO 8.1 integrates with BMC Remedy 8.1.

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 StruxureWare Data Center Operation 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 between the systems in External System Configuration in StruxureWare Data Center Operation.

You must also ensure the appropriate users get access to the feature.

Working with work orders and Remedy tickets

Once you have configured the system integration, you can start tracking tickets from Remedy in StruxureWare Data Center Operation an
d associating tickets with work orders.

Configuration of Remedy integration

Configuration of user rights for work orders

Page 507
Remedy tickets appear in StruxureWare Data Center Operation

Work order changed to In progress

Changes updated in Remedy

Page 508
Viewing tickets from Remedy
When the system has been configured to support integration with the Remedy Change Management system, 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 StruxureWare Data Center
Operation.

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

123 Steps to... See also

Filtering Remedy Tickets (Search) Associating Remedy tickets and

You can set a filter on the Remedy Tickets to show only the tickets you want to see. work orders
Configuring Remedy integration
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 StruxureWare Data Center Operation and is not to be
confused with the qualification filter.

Page 509
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 StruxureW
are Data Center Operation. You can associate one or more tickets to one work order.

Associate with a new work order

1. In the Remedy Change Tickets pane, right-click a Remedy ticket.

2. Select Associate with a new work order.
The Work Order Editor opens.
3. 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 Associat
ed Work Order/ID column in the Remedy Change Tickets and Work Orders panes.

Associate with an existing work order

If you have already started working on a work order in StruxureWare Data Center Operation, you can associate to an already existing
work order.

1. In the Remedy Change Tickets pane, right-click a Remedy ticket.

2. Select Associate with an existing work order.
The Work Orders pane opens.
3. 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.
4. 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 StruxureWare Data
Center Operation or Remedy, these changes are reflected in both systems.

Page 510
Remedy integration process overview

Page 511
StruxureWare Data Center Operation: Energy Efficiency
StruxureWare Data Center Operation: Energy Efficiency 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.

For information about the energy efficiency concepts, such as Power Usage Effectiveness (PUE) and Data Center Infrastructure
Efficiency (DCiE), go to the Green Grid and read the White Papers.

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

Note

You can toggle the efficiency metric between PUE and DCiE in Tools > Preferences > General.

Watch this video tutorial to learn how to measure the data center efficiency.

Energy Efficiency Metrics

Showing PUE or DCiE values

About PUE and DCiE

Energy Efficiency Dashboard

Using the Energy Efficiency Dashboard

Energy System Configuration

Configuring an energy system

Configuring power dependencies
Configuring infiltration
Configuring IT load
Configuring ventilation and lighting

Page 512
About PUE and DCiE
Power Usage Effectiveness (PUE) and Data Center Infrastructure Efficiency (DCiE) are commonly used metrics for determining if energy
efficiency improvements should be made.

PUE

PUE = Total Facility Power / IT Equipment Power

The range is from 1 to infinity (5 in StruxureWare Data Center Operation: Energy Efficiency). The lower the value is, the better the
efficiency is. 1 being 100% efficiency (all power used by IT equipment only).

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

Page 513
Power dependency configuration
In the Power Dependency Editor, you can draw a diagram of the entire physical infrastructure supporting the racks, including the power
connections.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.

123 Steps to... See also

StruxureWare Data Center

Configuring power dependencies Operation: Energy Efficiency
Configure the power dependencies between the equipment in the diagram to ensure the configuration accurately reflects the live physical infrastructure of your
energy systems.

1. In the Application bar, select Planning > EE Configuration to open the Power Dependency Editor.
2. 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

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.

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.
3. 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.
4. Select the connection icon
in the toolbar.
5. 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.
6. 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.
7. 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.

Page 514
Energy system configuration
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.

You can create a new system by selecting > File > New Energy System or by clicking the Systems pane New Energy System icon.

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 Pro
perties.

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.

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
Derate Capacity must be >0

123 Steps to... See also

Configuring an energy system StruxureWare Data Center

Configure the components of the energy system to ensure the configuration accurately reflects the live physical infrastructure of the Operation: Energy Efficiency
system.

1. Click the Systems pane New Energy System icon

and type a name and define the environmental settings.

2. Double-click an energy system in Systems to open it in the editor.
3. To include components in an energy system:
a. Right-click a grayed out component in the diagram and select Include in energy system.
b. 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.
c. If you regret including a component, right-click it and select Exclude from energy system.
4. 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.
5. At any time, right-click a component to see the properties.
6. In the Scripts pane, create scripts to include measurements in the energy system's PUE/DCiE calculation.
7. 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.

Page 515
Configuring infiltration
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.

1. Right-click the energy system and select > Properties > Infiltration.
2. Define the Dry bulb fixed loss to indicate the fraction of power that is lost per degree Celsius dry bulb.
3. 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.

Page 516
Configuring IT load
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.

1. Right-click the energy system and select > Properties > IT Load.
2. Define the general settings for the energy system's IT load.
a. Select if the IT load is on the critical or primary power path.
IT load must be included for the energy system.
b. IT load is measured (live).
3. Use the Script tab for writing scripts that retrieve measurements.

Page 517
Configuring ventilation and lighting
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.

1. Right-click the energy system and select > Properties > Ventilation.
2. Define the general settings for the energy system's ventilation.
a. 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.
b. Select if the ventilation data is measured (live) or computed (without power meters).
3. Define the configuration of the energy system's ventilation.
a. In Actual kW Nameplate, type the total nameplate value of the ventilation.
b. 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.
c. In Redundancy, type the redundancy of the subsystem.
d. In Redundancy +1 kW Increment, type the loss in kilowatt caused by internal redundancy. (Only needed if the
redundancy option includes +1)
e. In Derate Capacity fraction, type a number between 0 and 1, indicating the usable fraction of the ventilation
equipment nameplate value.
f. In Typical PU, type the power usage (PU) of the ventilation in power units relative to the total power usage.
4. Define the loss configuration of the energy system's ventilation.
a. In Fixed loss, type a number between 0 and 100, indicating the fraction of power that is the fixed loss of the ventilation.
b. 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.
c. 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.
d. In Dry bulb fixed loss, type a number between 0 and 100, indicating the fraction of power lost per degree Celsius dry
bulb.
5. Use the Script tab for writing scripts that retrieve measurements.
6. Click Lighting and repeat the above steps for configuring the energy system's lighting settings.

Page 518
Energy Efficiency properties
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.

Derate Capacity Identifies the usable fraction of the nameplate value that can be used for this component. For example, if you
fraction use a 20% safety margin, this value would be 0.8.

Redundancy Identifies the redundancy of this component. For example, if you have a redundant setup with two 80 kW
UPS, this value would be 2N.

Redundancy "+1" Identifies the loss in kilowatt caused by internal redundancy. (Only needed if redundancy option includes +1.)
kW Increment For example, if you have a 40 kW UPS with one spare 10 kW power module, this value would be 10 kW.

Typical PU Identifies the power usage (PU) of this component relative to the total power usage.

Usable fraction of Identifies the usable fraction of power that can be used without derating the value.
nameplate w/o
derating

Fixed loss Identifies the fraction of power that is the fixed loss of the component.

Proportional loss Identifies the fraction of power that is lost proportional to the load of the component.

Square Law loss Identifies the fraction of power that is lost proportional to the square of the load of the component.

Dry Bulb Fixed loss Identifies the fraction of power that is lost per degree Celsius dry bulb.

Page 519
Energy system properties
This section of the Properties dialog box, accessed by right-clicking an energy system, provides relevant information that identifies the
selected energy system.

Name A user-definable value used to identify the energy system.

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

Design IT Load Identifies the designed IT load.

Rating

Outdoor Dry Bulb Identifies the outdoor temperature.

Temperature

Calculation A user-definable value used to identify the interval for calculating the PUE / DCiE based on the data retrieved
Interval from the StruxureWare Data Center Expert server or other data provider.

Page 520
Infiltration properties
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.

Configuration

Dry bulb fixed loss Identifies the fraction of power that is lost per degree Celsius dry bulb.

Page 521
IT load properties
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.

Configuration

Power path Identifies whether the IT load is on the critical or primary power path. You cannot choose to exclude it in this
energy system.

Calculation Identifies that the IT load is measured (live).

source

Script Opens the script editor for editing scripts to retrieve IT load measurements.

Page 522
Lighting properties
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 used to light the data center.

Configuration

Power path Identifies if this subsystem is on the critical or primary power path, or if it is not included in this energy
system.

Calculation source Identifies if the load of the subsystem is measured (live) or computed (without power meters).

Actual kW Nameplate Sums up the total nameplate value of all equipment in this subsystem.

Usable fraction of Identifies the usable fraction of power that can be used within the devices in this subsystem without
nameplate w/o derating derating the value.

Redundancy Identifies the redundancy of this subsystem. For example, if you have a redundant setup with two 80
kW UPS, this value would be 2N.

Redundancy "+1" kW Identifies the loss in kilowatt caused by internal redundancy. (Only needed if redundancy option
Increment includes +1.)

Derate Capacity fraction 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.

Typical PU Identifies the power usage (PU) of this subsystem relative to the total power usage.

Fixed loss Identifies the fraction of power that is the fixed loss of the subsystem.

Proportional loss Identifies the fraction of power that is lost proportional to the load of the subsystem.

Square Law loss Identifies the fraction of power that is lost proportional to the square of the load of the subsystem.

Dry bulb fixed loss Identifies the fraction of power that is lost per degree Celsius dry bulb.

Script Opens the script editor for editing scripts for this subsystem.

Page 523
Ventilation properties
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.

Configuration

Power path Identifies if this subsystem is on the critical or primary power path, or if it is not included in this energy system.

Calculation source Identifies if the data of this subsystem is measured (live) or computed (without power meters).

Actual kW Sums up the total nameplate value of all equipment in this subsystem.
Nameplate

Usable fraction of Identifies the usable fraction of power that can be used within the devices in this subsystem without derating
nameplate w/o the value.
derating

Redundancy Identifies the redundancy of this subsystem. For example, if you have a redundant setup with two 80 kW
UPS, this value is 2N.

Redundancy "+1" Identifies the loss in kilowatt caused by internal redundancy. (Only needed if redundancy option includes +1.)
kW Increment For example, if you have a 40 kW UPS with one spare 10 kW power module, this value would be 10 kW.

Derate Capacity Identifies the usable fraction of the nameplate value that can be used in this subsystem. For example, if you
fraction use a 20% safety margin, this value would be 0.8.

Typical PU Identifies the power usage (PU) of this subsystem relative to the total power usage.

Fixed loss Identifies the fraction of power that is the fixed loss of the subsystem.

Proportional loss Identifies the fraction of power that is lost proportional to the load of the subsystem.

Square Law loss Identifies the fraction of power that is lost proportional to the square of the load of the subsystem.

Dry bulb fixed loss Identifies the fraction of power that is lost per degree Celsius dry bulb.

Script Opens the script editor for editing scripts for this subsystem.

Page 524
Database integration
You can integrate StruxureWare Data Center Operation: Energy Efficiency with any JDBC or ODBC compliant database. To do this, you
must configure a data provider in the startup script.

Page 525
Sample startup script for database integration
The configuration of the data provider, such as a database, is done in the startup script.You may need to add additional database drivers
to connect to the database, if the generic drivers shipped with StruxureWare Data Center Operation: Energy Efficiency 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.

Page 526
/*
* 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
");

Page 527
Sample simple database query script
An example of how to perform a simple database query from a StruxureWare Data Center Operation: Energy Efficiency script.

/*
* 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;

Page 528
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

Page 529
result.close();
statement.close();
connection.close();

Page 530
Sample database query script
An example of how to retrieve data from a database and calculate an average.

/*
* 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;

Page 531
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

Page 532
result.close();
statement.close();
connection.close();

Page 533
Web service integration
You can set up StruxureWare Data Center Operation: Energy Efficiency to retrieve values from web services.For further information, see
Energy Efficiency Web Service Integration in the DCIM Developer Documentation.

Page 534
StruxureWare Data Center Operation: Lab
StruxureWare Data Center Operation: Lab 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 StruxureWare Data Center Operation application.

The StruxureWare Data Center Operation: Lab client application is available from the Data Center Operation server's download page.
You need a valid StruxureWare Data Center Operation: Capacity license to log on to the application.

You can use the StruxureWare Data Center Operation: Lab 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 StruxureWare Data Center Operation, 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 StruxureWare Data Center Operation. However, as this
is a separate test environment only, you will not have all features available that you know from StruxureWare Data Center Operation:

No StruxureWare Data Center Operation: Change 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 StruxureWare Data Center Operation applicatio
n. However, any changes to available products in the genome library will subsequently be available in StruxureWare Data Center
Operation application.

To simulate changes to a product that you want to continue to use in its original version in StruxureWare Data Center Operation, make a
copy and use it as a template for a new product in the StruxureWare Data Center Operation: Lab.

You can delete any obsolete lab models in File > Manage Models.

123 Steps to... See also

Installing StruxureWare Data Center Operation: Lab Designing simulations in

The StruxureWare Data Center Operation: Lab client application is available from the Data Center Operation server's StruxureWare Data
download page. Center Operation: Lab

1. Open a Web browser and type the address of your Data Center Operation server: https://yourservername .
2. On the Data Center Operation server's download page, click LAB Download and follow the instructions to download
the StruxureWare Data Center Operation: Lab client. You can now proceed to logging on to the application with the
same credentials as for StruxureWare Data Center Operation.

Page 535
Designing simulations in StruxureWare Data Center Operation: Lab
Simulations designed and edited in the StruxureWare Data Center Operation: Lab exist only as separate simulation solutions and do not
affect the data center model of the live environment created in the StruxureWare Data Center Operation application.

When you launch the application, it will open a copy of the existing data center model of the live environment from StruxureWare Data
Center Operation. 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.

1. To simulate how planned changes would affect the existing StruxureWare Data Center Operation data center model without
affecting it:
a. In the Open Solution dialog box, select Current StruxureWare Data Center Operation 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 StruxureWare Data Center Operation data center model.)
b. Perform the desired edits, e.g. adding equipment.
c. Select File> Save as and type a file name.
2. To edit a previously saved test simulation:
a. In the Open Solution dialog box, select Existing StruxureWare Data Center Operation: Lab solution and click Open.
b. Perform the desired edits, e.g. adding equipment.
c. Select File> Save.

Page 536
Troubleshooting issues saving large solutions in Lab

Problem

You'll be able to save most lab solutions without any issues. However, when trying to save certain large solutions in StruxureWare Data
Center Operation: Lab, you get a generic Server Communication Lost error.

Why

There is a limit to the amount of data the DCO server is able to receive when communicating with the DCO clients. Certain large Struxur
eWare Data Center Operation: Lab solutions may exceed that limit.

How to verify

Open the DCO client log file and look for this:

Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response '502: Proxy Error' when communicating with https://swprod09
:443/isxo/core/model/DataCenterLabSolutionService

If you see this line in the log file, the steps below should fix the problem.

How to solve

1. Open /opt/jboss-as/standalone/configuration/standalone.xml
2. Locate <http-listener name="default" socket-binding="http" max-post-size="26214400"/>
3. Change 26214400 (25 mb in bytes) to e.g. 104857600 to increase the size limit to 100 mb.

Note
Be aware that some security attacks are sending large amounts of data towards the server. Therefore, it is not recommended
to set this limit extraordinarily high.

Page 537
StruxureWare Data Center Operation: Insight
StruxureWare Data Center Operation: Insight 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 StruxureWare Data Center Operation application.

The StruxureWare Data Center Operation: Insight client application is available from the Data Center Operation 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 Struxure
Ware Data Center Operation Suite. StruxureWare Data Center Operation: Insight includes the option to publish the configured report
designs to StruxureWare Data Center Operation.

StruxureWare Data Center Operation: Insight 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.

For further information on how to customize report designs, see the DCIM Developer Documentation: Customizing report designs. If you
have a need for custom report designs but don't want to create these yourself, they can also be created by our service department base
d on a quotation.

Note

Insight reports are not supported in Internet Explorer 11.

Page 538
StruxureWare Data Center Operation: Mobile
The Motorola device is no longer supported in DCO 8.1 and forward.
The StruxureWare Data Center Operation: Mobile application allows you to use a mobile device to work with the StruxureWare Data
Center Operation application, including add-on StruxureWare Data Center Operation: Capacity and StruxureWare Data Center
Operation: Change functionality.

Do not confuse StruxureWare Data Center Operation: Mobile with StruxureWare Data Center Operation: VIZOR.

StruxureWare Data Center Operation: Mobile allows you to work with StruxureWare Data Center Operation on-the-fly and synchronize
changes with the Data Center Operation server, whereas the StruxureWare Data Center Operation: VIZOR app allows you to monitor
data center operations through read-only KPI data using an iPhone.

Installation and logon

Installing StruxureWare Data Center Operation: Mobile on the mobile device

Logging on to StruxureWare Data Center Operation: Mobile
Troubleshooting logon problems
Troubleshooting operational problems

Local mode

Working in local mode

Synchronizing local changes
Troubleshooting connection and synchronization problems

Alarms

Viewing alarms on StruxureWare Data Center Operation - Mobile

Enabling or disabling pop-up alarm notifications
Closing active alarm notifications

Asset management

Adding equipment
Connecting equipment
Defining customized properties for a piece of equipment
Deleting equipment
Moving equipment
Canceling a pending change
Executing a pending change

Scanning

Scanning equipment bar codes into StruxureWare Data Center Operation: Mobile
Troubleshooting scan problems

Rack audit

Page 539
Performing a rack audit

Page 540
Required setting for Mobile 8.0
Using StruxureWare Data Center Operation: Mobile with StruxureWare Data Center Operation from version 8.0 requires disabling the
standard automatic redirect of http to https for secure communication.

Warning

Use this option with caution and be aware of the reduction in security since your data will no longer be encrypted!

You must enable secure connection in the DCO desktop and web clients to avoid bringing communication between the server
and clients at risk.

Disabling redirect to secure https connection

1. Open the server management web interface (Webmin) by typing the address of your DCO server in a web browser folllowed by
:10000, https://<server IP address>:10000.
2. Log in to Webmin using the user credentials created during the server installation.
3. In the left menu, select StruxureWare DC Operation>Setup.
4. Deselect Redirect HTTP to HTTPS and click Setup to save your changes.
5. Wait for the Struxureware DCOperation service to restart.
6. When the service is up and running, you can use StruxureWare Data Center Operation: Mobile.

DCO desktop and web clients can still use SSL to connect to the DCO server.

Page 541
Installing StruxureWare Data Center Operation: Mobile on the mobile device

System specifications

StruxureWare Data Center Operation: Mobile has been used on systems with these specifications:

OS version Windows mobile 6.5 Professional CE OS 5.2.23121 (Build 23121.5.3.6)

Windows mobile OS 5.1.478 (Build 15706.3.5.2)

Windows Mobile TM 2003 Second Edition Version 4.21.1088 (Build 14235.2.0.0)

Memory 64 MB
179 MB

Device storage capacity 657 MB

Device used Motorola MC55

Motorola MC70

Motorola MC75

Prerequisites

StruxureWare Data Center Operation: Mobile 8.0 requires the following to be installed in the specified order before you install the Struxur
eWare Data Center Operation: Mobile client. These files are available on the software download page together with the StruxureWare
Data Center Operation: Mobile file.

1. Microsoft .Net Compact Framework 3.5

2. Microsoft SQL Server Compact Edition 3.5

To find out which version of Windows Mobile you are running, go to the Start menu and select Settings>System tab, then select About.

Installing StruxureWare Data Center Operation: Mobile

1. Download the latest version of StruxureWare Data Center Operation: Mobile from the same location that you downloaded the D
CO ISO (provided by the support team. To locate the telephone number for your region, visit Contact Us).

Note

You must have a valid license for the module to be available for download.

2. 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 StruxureWare Data Center Operation: Mobile logon page.

Page 542
Logging on to StruxureWare Data Center Operation: Mobile
If you want to launch the StruxureWare Data Center Operation: Mobile in another language, select the desired language in Start >
Settings > System > Regional Settings.

1. On the opening screen of the mobile device, select > Start > Programs > StruxureWare Data Center Operation: Mobile.
This step is necessary except at installation, when the application starts automatically at the logon page.
2. On the StruxureWare Data Center Operation: Mobile logon screen:
a. Enter the server name or IP address of your StruxureWare Data Center Operation server.
b. Enter your user name and password, and select > Menu > Show Password if you want the password displayed as you
enter it.
c. If you want to use the high-security access that Secure Sockets Layer (SSL) provides, select Use SSL to enable SSL
access.
i. If there is no valid SSL certificate on the mobile device, StruxureWare Data Center Operation: Mobile prompts
you to accept the required certificate from the server.
ii. View the SSL certificates that are on your mobile device by selecting > Menu > SSL Certificates.
iii. Delete any certificate that is invalid or expired or that allows access to a server that you no longer use.
d. Select Local mode if you want to start the application in local mode.
e. Select OK.

See also

Troubleshooting logon problems

Page 543
Troubleshooting logon problems
Correcting problems that may occur during logon.

Symptom Explanation Solution

Either of these One of the fields of the StruxureWare Data Enter the missing data in the correct field.
Center Operation: Mobile logon screen was
error messages: blank.

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.

Either of these You must have a user account at the Data Try again to log on to ensure that you entered your
Center Operation server that includes your user password correctly. If the error message occurs again
error messages: name, your password, and permissions for the at your second attempt, contact your StruxureWare
user role of StruxureWare Data Center Data Center Operation server administrator.
The supplied Operation Admin.
user
name/password
is not valid.
The specified
user does not
have
permission to
log on to this
application.

Error message: DNS could not resolve the name of the host Contact your Data Center Operation server
computer. administrator.
Could not
resolve
specified
hostname.

Error message: You selected Use SSL but declined to accept Try again, and do one of the
the displayed certificate.
following as you log on:
You must
accept the SSL For a high-security
certificate in logon session, select Us
order to log on. e SSL and accept the
certificate.
For a logon session
protected only by an
unencrypted username
and password, deselect
Use SSL.

Page 544
Error message: The StruxureWare Data Center Operation client In the Web browser on
version has been updated to a later version,
and you should update the StruxureWare Data the mobile device,
The client and Center Operation: Mobile client. specify the URL of the S
server version truxureWare Data
do not match. It Center Operation server
is advised that .
you download In the Web browser on
the client from the mobile device,
the specified specify the URL of the S
server. truxureWare Data
Center Operation server
and add /frontpage to
the address.
On the Data Center
Operation server's
download page, click Do
wnload in the Mobile
box to download the
latest version to the
mobile device.
Follow the on-screen
instructions to install it.

Page 545
StruxureWare Data Center Operation: Mobile main screen
The main screen that opens when you have logged in to StruxureWare Data Center Operation: Mobile provides access to StruxureWare
Data Center Operation features as well as add-on StruxureWare Data Center Operation: Change and StruxureWare Data Center
Operation: Capacity features.

Alarms: Displays a list of alarms on devices in StruxureWare Data Center Operation that are monitored by StruxureWare Data
Center Expert.
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.

Note

This is an add-on feature and is available only if you have a valid StruxureWare Data Center Operation: Change licens
e.

Asset management: Enables you to view, move, edit, or delete equipment in the system.
Add Equipment: Provides access to the Add Equipment screen that enables you to add equipment to a rack.
Rack Audit: Provides access to the Audit screen that enables you to verify the system information.

Note

This is an add-on feature and is available only if you have a valid StruxureWare Data Center Operation: Change licens
e.

Synchronize: (Available in local mode) Synchronizes to update any changes made in StruxureWare Data Center Operation:
Mobile on the mobile device or in the StruxureWare Data Center Operation client installed on the host computer, while the
mobile device was in local mode.

Tip

In Menu, you can toggle server/local mode.

Page 546
Local and server mode
When using StruxureWare Data Center Operation: Mobile, you can work in either local or server mode.

Synchronizing updates StruxureWare Data Center Operation data center model with changes made in local mode through StruxureWare
Data Center Operation: Mobile and vice versa.

For connection and synchronization to occur when the mobile device is not on a wireless network that can access the Data Center
Operation 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.

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 Stru
xureWare Data Center Operation as well. Any changes made by other users will also be instantly reflected in StruxureWare Data Center
Operation: Mobile.

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 StruxureWare Data Center Operation until it is synchronized. StruxureWare Data Center Operation: Mobile will also only
receive changes made by other users when synchronized.

Page 547
Working in local mode
You can operate the StruxureWare Data Center Operation: Mobile application in local mode without accessing the network to connect to
the Data Center Operation server. The launch to device feature, however, requires network access.

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.

1. Work on a local copy of StruxureWare Data Center Operation: Mobile performing any changes that you want.
2. Synchronize any changes made to the data center model in either StruxureWare Data Center Operation or StruxureWare Data
Center Operation: Mobile local mode by selecting Synchronize in the StruxureWare Data Center Operation: Mobile main
screen.

See also

Local and server mode

Synchronizing local changes

Page 548
Synchronizing local changes
When you are using StruxureWare Data Center Operation: Mobile in local mode, it is recommended that you synchronize regularly with
the Data Center Operation server to ensure that you are always working on the updated data center model when in local mode.

1. Place the mobile device firmly in the cradle.

2. Open StruxureWare Data Center Operation: Mobile.
3. On the main screen, select Synchronize.
4. 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.
a. Select if you want to send any changes done while working in local mode on the mobile device to the server.
b. 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 StruxureWare Data Center
Operation: Mobile application.

Toggle Product Catalog to define if you want to have the products from the server's genomes 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 (StruxureWare Data Center Operation:
Change feature).

Page 549
Troubleshooting connection and synchronization problems
Correcting connection or synchronization problems that may occur when using the mobile device.

Symptom Explanation Solution

Error message: One or more of Contact your Data Center Operation server administrator.
the following
Could not conditions might
connect to exist:
server at
specified The specified
address. server is not
Ensure the responding
specified because it is
server is not running.
running. The specified
server refused
the connection
request
because it is
not a Data
Center
Operation ser
ver.

Error If the mobile device is on a wireless Ensure that the wireless

network, that network may be
Condition: network is enabled.
experiencing problems, or the server
may be off-line. Use the ping command from a
The mobile desktop computer or through
device the network connection software
application on the mobile device to
cannot determine whether the server is
connect to operating correctly.
or
synchronize
with the
server.

If the mobile device is in its cradle, Ensure that the cable from the cradle is securely attached
one or more physical connections and that the mobile device is firmly in the cradle.
may be loose.

Microsoft® ActiveSync® or Windows Ensure that ActiveSync or WMDC is available and running
Mobile Device Center (WMDC) for on the computer.
Windows Vista might be unavailable
or not running.

Page 550
Alarms on StruxureWare Data Center Operation: Mobile
The list of Alarms, available from the Alarms option on the main screen, displays a list of the alarms on devices in StruxureWare Data
Center Operation monitored by StruxureWare Data Center Expert and provides options to open individual alarms for viewing alarm
details. The system will notify you of new alarms occurring.

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

Warning

Error, Critical, and Failure

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 StruxureWare Data
Center Operation: Mobile, but only have them appear in the list the alarms.

123 Steps to... See also

Viewing Alarms Closing active alarm

The Alarms screen, accessed through the Alarms option on the main screen, allows you to view active alarm data from St notifications
ruxureWare Data Center Expert. Enabling or disabling
pop-up alarm
1. Tap Alarms on the main screen to open the Alarms screen. notifications
2. 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.
3. Select More in the bottom menu to see the recommended action on the next screen for how to resolve the alarm.
4. Select > Menu > Device... in the bottom of the screen to launch to the device data on the StruxureWare Data Center
Expert server.
5. Select > Menu > Equipment... in the bottom menu of the screen to browse directly to the associated equipment in A
sset Management if the alarm is happening on a device associated with a piece of equipment in the system.

Page 551
Closing active alarm notifications
Existing alarm notifications, informing you of active alarms while working in StruxureWare Data Center Operation: Mobile, can be closed
(no longer displayed).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.

1. To close all active alarm notifications

a. In the Main screen, select Alarms.
b. In the Alarms screen, select > Menu> Close All Notifications.
2. To close the active notification
a. Open the pop-up notification box by selecting the notification icon at the top of the screen.
b. Select Close to stop displaying the notification for this alarm.

Page 552
Enabling or disabling pop-up alarm notifications
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 StruxureWare Data Center Operation: Mobile.
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.

1. In the Main screen, select Alarms.

2. In the Alarms screen, clear Menu > Enable Notifications.
3. If, at any time, you want to enable the feature, select Menu > Enable Notifications to reintroduce it and toggle the feature on
again.

Page 553
Work Orders on StruxureWare Data Center Operation: 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 StruxureWare Data Center
Operation: Change 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

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 Filtering the work

From the Work Orders screen, you can select a work order and open it for viewing or editing. order list

1. Select a work order in the list and tap, hold, and select Open... to open it.
2. In the Work Orders screen, tap the Tasks tab to view the task information.
3. Tap and hold a task to track or change the status of the task.
a. Select Not Started

if no work has begun on the task.

b. Select In Progress

if the task is started but is incomplete.

c. Select Completed

if the task is finished.

d. Select Cancelled

if the task is no longer an active part of the work order, but remains on the list of tasks.
4. See the Summary for overview information about the selected work order.
5. 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.
6. Select More to open the Comment text field and view, add, or edit comments about the work order.
7. In the bottom menu bar, select Apply to save the changes

Page 554
Filtering the work order list
You can set up a filter in the Work Orders screen to display only work orders that match your selected criteria.

1. In the Work Orders screen, select Filter... in the bottom menu bar to access the Work Order Filter screen.
2. Select temporary filter options:
a. 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.
b. 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.
c. 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 StruxureWare Data Center Operation: Mobile.
3. Select persisted filter options:
a. Enter a number in the Max Count field to limit the amount of work orders shown in the filtered list.
b. 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.
c. 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.
d. 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.
4. Select OK to apply the filter settings and view the filtered list containing only work orders that match all the filtered criteria.

Page 555
Asset management
The Asset Management option on the main screen provides options to view, edit and audit equipment in the data center model.

123 Steps to...

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.

1. Select 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 (or by tapping, holding, and selecting Open...).
3. Select Filter in the bottom menu and select to show all floor-mounted items in the list (Show All), or only racks (Show Racks).
4. 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.
5. 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.
6. Select a rack to view the equipment in that rack by double-clicking (or by tapping, holding, and selecting Open....).
7. 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 StruxureWare Data Center Operation: Change, 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.
8. To view blade servers in a blade enclosure, continue to drill down by double-clicking the enclosure (or by tapping, holding, and
selecting Open...).
9. To view network routes for a piece of connected network equipment (read-only), select the equipment, then > Menu > Network.
10. 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.

Page 556
Scanning equipment bar codes into StruxureWare Data Center Operation: Mobile
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.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.

1. From a distance of approximately 6 inches (15 centimeters), point the scanner at the bar code.
2. 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.
3. Review or edit the equipment details of the scanned equipment, e.g. change the Name on the Edit screen.

Supported symbologies

StruxureWare Data Center Operation: Mobile (MC75 Handheld Mobile Computer) supports the following symbologies:
1D: All major ID bar codes.
2D: MaxiCode, PDF417, DataMatrix, QR Code, Aztec & Composite Codes
Postal Codes: US Postnet, US Planet, UK Postal, Australian Postal, Japan Postal.

Page 557
Troubleshooting scan problems
How to correct problems that may occur when scanning bar codes.

Symptom Explanation Solution

No response to pressing the button to The scanning function of StruxureWare Data Restart the mobile device and reattempt
activate the mobile device's scanner. Center Operation: Mobile may be in conflict with the scan or close the other application
the scanning function of another application. that is using the scanning function.

Barcode scanner not launching after The web based barcode scanning functionality is Using a different browser ie Chrome or
barcode icon has been pressed using a based on a web application that is not running in Firefox will launch the camera to scan a
laptop PC with Internet Explorer 11 IE11 barcode.

Page 558
Adding equipment
The Add Equipment screen allows you to add equipment to the data center model.

1. 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.
2. Select an item of equipment to add from the list of latest products or by using Search or Browse to find it in the genome library.
Select an item of equipment to add from the list of latest products.
The available selections are configured through the genome library in StruxureWare Data Center Operation.
3. 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.
a. Bar Code: Scan the item's bar code into this field (or enter the characters of the code manually).
b. 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.
4. Select Next... in the bottom menu bar, and display custom properties.
a. Tap and hold, and select to Add, Edit or Remove custom properties on the product that you are adding.
5. Select Next... in the bottom menu bar, and display the location: room, rack, and location for the item of equipment within the
rack.
a. 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.
b. 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.
6. Click OK to add the item of equipment.
7. 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.

Page 559
Connecting equipment
The Power screen, accessed from the Asset Management option on the main screen, allows you to access options to set up power
connections.

1. Tap Asset Management on the main screen to open the Browse screen.
2. Tap and hold a location's name to view the rooms in that location.
3. Tap and hold a room's name to view the racks in that room.
4. Tap and hold a rack's name to view the equipment in that rack.
5. Tap and hold a server or rack PDU to open the Edit screen for this piece of equipment
6. 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).
a. Tap and hold in the list to access add or remove connection options.
b. To remove a power connection select Remove.
c. To add a connection select Add... and in the Add Outlet Connection screen, select between available rack PDU and
phase options.

Page 560
Moving equipment
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.

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 (or by tapping, holding, and selecting Open...).
3. Select a rack to view the equipment in that rack by double-clicking (or by tapping, holding and selecting Open...).
4. Select a piece of equipment in a rack by double-clicking (or by tapping, holding and selecting Open...).
5. 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.
6. Select OK.
7. 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).
a. Tap and hold in the list to access add or remove connection options.
b. To remove a power connection select Remove.
c. To add a connection select Add... and in the Add Outlet Connection screen, select between available rack PDU and
phase options.

Page 561
Deleting equipment
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.

1. Select Asset Management on the main screen to open the View screen and navigate to the item that you want to delete.
a. Select a room to view the racks within that room by double-clicking (or by tapping, holding, and selecting Open...).
b. 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.
c. Select a rack to view the equipment in that rack by double-clicking (or by tapping, holding, and selecting Open....).
d. Select a piece of equipment in a rack by double-clicking a rack (or by tapping, holding, and selecting Open....) to
access equipment details.
2. Select Delete in the bottom menu.

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.

Although you cannot retrieve a deleted item, all actions including deletes performed through StruxureWare Data Center Operation:
Mobile are listed in the StruxureWare Data Center Operation application Audit Trail report. More...

Page 562
Working with Pending Changes on StruxureWare Data Center Operation: Mobile
You can execute a pending change configured through the StruxureWare Data Center Operation: Change module in StruxureWare Data
Center Operation: deletion, move, or addition of a new item for which space has been reserved in the data center.

The pending options are only available if there is equipment that was marked for deletion, moved or added in Planning IT Change mode
( StruxureWare Data Center Operation: Change feature in StruxureWare Data Center Operation).

A rack or item of equipment for which a move is pending is displayed in two locations in StruxureWare Data Center Operation: Mobile :

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 StruxureWare

You can execute a pending change configured through the StruxureWare Data Center Operation: Change module in Data Center
StruxureWare Data Center Operation: deletion, move, or addition of a new item for which space has been reserved Operation:
in the data center. Mobile

1. 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.
2. Select Execute Pending Change.
StruxureWare Data Center Operation: Mobile 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 Pendi
ng 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 StruxureWare Data Center Operation: Change modul
e in StruxureWare Data Center Operation.
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.

Page 563
Assigning tags on StruxureWare Data Center Operation: Mobile
You can assign tags to equipment in StruxureWare Data Center Operation: Mobile to categorize types of equipment (StruxureWare Data
Center Operation: Capacity 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

Page 564
Defining customized properties for a piece of equipment
The Properties tab of the Edit Equipment screen lists any customized properties defined for the piece of equipment.

1. Access the Edit Equipment screen:

a. Select Asset Management on the main screen.
b. Tap and hold a piece of equipment on the View Equipment screen and select Open....
2. 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.
3. If you regret and want to remove a property, tap the property to highlight it in the list, and tap Remove.

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

See also

Asset management

Page 565
Equipment stages on StruxureWare Data Center Operation: 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 (StruxureWare Data Center Operation: Change feature).

Icon Equipment Description Options

Stage Available

Existing Equipment shown in its current location, with no action pending. It displays in dark gray, indicating that it occupies the position View Rack
shown. Edit
Equipment
Delete
Equipment

Pending Equipment that is shown in its current location but has a move pending. It displays in dark gray, indicating that it occupies the View Rack
Move position shown. Edit
(Source) Equipment
Execute
Pending
Change
Cancel
Pending
Change

Pending Equipment shown in its target location for a pending move. It displays in gray (dimmed), indicating that the position shown, View Rack
Move although unoccupied, is reserved for the equipment. Edit
(Destination) Equipment
Execute
Pending
Change
Cancel
Pending
Change

Pending Add Equipment shown in its target location for a pending addition (configured through the desktop application with the item View Rack
selected from the genome library). It displays in gray (dimmed), indicating that the position shown, although unoccupied, is Edit
reserved for the equipment. Equipment
Delete
Equipment
Execute
Pending
Change
Cancel
Pending
Change

Pending Equipment shown in its current location, but with a pending deletion configured through the desktop application. It displays in View Rack
Deletion dark gray, indicating that it occupies the position shown. Edit
Equipment
Delete
Equipment
Execute
Pending
Change
Cancel
Pending
Change

See also

Asset management

Page 566
Performing a rack audit
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.

1. Tap Asset Management on the main screen to open the View screen.
2. Select the rack that you want to audit by tapping it in the list (or by scanning its bar code).
3. 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 (

icon).
4. Scan the equipment in the rack, one by one. The status icon listed next to the scanned equipment changes to Verified (

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 (

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 (

icon).
5. At any time during the audit, if you want to restart auditing the equipment in the rack, tap Restart in the bottom menu bar.
6. 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.

Page 567
Troubleshooting operational problems
How to correct problems that may occur when performing StruxureWare Data Center Operation: Mobile functions.

Symptom Explanation Solution

You experience frequent error You are working in server mode, and the Check your wireless network connection, or connect through the
messages, or your mobile network connection is unstable. StruxureWare cradle and switch to local mode to work in a mode that does not
device interface or the Struxu Data Center Operation: Mobile can run with a require network connection. (Remember to connect and
reWare Data Center variety of other applications, but if other synchronize regularly.) See your mobile device documentation for
Operation: Mobile application applications are too numerous or too large, instructions on checking memory usage. If memory is insufficient,
is frequently unresponsive. insufficient memory can cause errors. uninstall unnecessary applications.

See also

StruxureWare Data Center Operation: Mobile

Page 568
StruxureWare Data Center Operation: PRO Pack
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.

StruxureWare Data Center Operation 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 StruxureWare Data Center Operation with real-time device monitoring data
from the StruxureWare Data Center Expert 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 StruxureWare Data Center Operation 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. See supported versions here.

For example:

Rack 3A is powered by UPS A

Rack 3B is powered by UPS B
An alarm is triggered on UPS A
Virtual Machine Manager migrates the virtual machines from hosts in Rack 3A to hosts in Rack 3B that is powered by UPS B

Watch this video tutorial to learn how to configure Microsoft System Center - Virtual Machine Manager.

See also

Initial setup of StruxureWare Data Center Operation PRO Pack

Working with StruxureWare Data Center Operation PRO Pack

Page 569
Initial setup of StruxureWare Data Center Operation PRO Pack
You must perform the installation and configuration process of the StruxureWare Data Center Operation: PRO Pack 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.

Requirement for PRO pack installation

.NET Framework version 4.

Installation and data retrieval configuration

The StruxureWare Data Center Operation: PRO Pack installer is available from a location provided by the support team. To locate the
telephone number for the support you need, visit Contact Us. Once you have run the installer, you need to configure the server
communication between the StruxureWare Data Center Operation server and the Virtual Machine Manager server, and then import the
StruxureWare Data Center Operation: PRO Pack 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.

StruxureWare Data Center Operation: PRO Pack 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 R2, and Virtual Machine Manager 2012 and R2. These
versions of StruxureWare Data Center Operation: PRO Pack are available:

com.apcc.ISXO.PRO.2008R2.mp
com.apcc.ISXO.PRO.2012.mp

A complete configuration of StruxureWare Data Center Operation with StruxureWare Data Center Operation: Capacity license is
required (including association of monitored devices from StruxureWare Data Center Expert).

Data configuration in StruxureWare Data Center Operation

The StruxureWare Data Center Operation 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 StruxureWare Data Center Operation: PRO Pack through web services including a definition of the
polling interval. Read instructions on granting access to web service APIs here or read about the web service API here.

Note

If you are integrating with Virtual Machine Manager 2012 and R2, 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.

Page 570
Installing StruxureWare Data Center Operation PRO Pack
1. 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.
2. Download the StruxureWare Data Center Operation: PRO Pack .msi package to a location on your Microsoft System Center
Operations Manager server.
3. 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 StruxureW
are Data Center Operation: PRO Pack folder, and StruxureWare Data Center Operation PRO Pack configuration is available
from Start > StruxureWare Data Center Operation 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 StruxureWare Data Center Operation: PRO
Pack 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 StruxureWare Data Center Operation: PRO Pack at any time, remove it from Microsoft System Center
Operations Manager before you run the uninstaller. After uninstalling the StruxureWare Data Center Operation: PRO Pack, the computer
must be rebooted.

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.

See also

Initial setup of StruxureWare Data Center Operation PRO Pack

Configuring StruxureWare Data Center Operation PRO Pack
Configuring StruxureWare Data Center Operation PRO Pack Agent

Page 571
Configuring StruxureWare Data Center Operation PRO Pack
The setup includes configuring the server communication between the StruxureWare Data Center Operation and Virtual Machine
Manager servers.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 Data Center Operation PRO Pack > Configuration.

1. Type the description of the StruxureWare Data Center Operation server that you want to display in Microsoft System Center
Operations Manager.
2. Type the host name of the StruxureWare Data Center Operation server that will be sending location, power, cooling, and impact
data.
3. 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).
4. 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 Data Center Operation PRO Pack.mp file.
In > Administration > Run As Configuration, select Profiles. In the list, right-click StruxureWare Data Center
Operation and select Properties. Select Run As Accounts and click Add. In Run As account type, select Digest
Authentication, and type the account credentials that match a DCO user with access rights to Web services API.
Read instructions on granting access to web service APIs here.

The StruxureWare Data Center Operation: PRO Pack is now imported and configured in Microsoft System Center Operations Manager.
It appears in Monitoring > StruxureWare Data Center Operation PRO.

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 StruxureWare Data Center Operation.

You can customize what details to display in Microsoft System Center Operations Manager from StruxureWare Data Center Operation.
Select StruxureWare Data Center Operation or Impacted Virtual Machine Hosts in Monitoring > StruxureWare Data Center
Operation PRO, and select > Actions > Personalize view... and select the columns to display in the Detail View.

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.

Page 572
Configuring StruxureWare Data Center Operation PRO Pack Agent
The agent is installed with the StruxureWare Data Center Operation: PRO Pack. You will see an icon on the task bar when the agent is
running.The StruxureWare Data Center Operation: PRO Pack Agent ensures the data from the Virtual Machine Manager server is
updated in StruxureWare Data Center Operation at the configured frequency, e.g. every 10 minutes (minimum).

1. 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 Star
t > All Programs > Startup > StruxureWare Data Center Operation PRO Pack).
2. Define the interval of getting updated data from Virtual Machine Manager into StruxureWare Data Center Operation.

Updates include:

Virtual machine hosts: Addition/removal, switch between maintenance/normal modes

Virtual machines: Addition/move/deletion

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.

See also

Initial setup of StruxureWare Data Center Operation PRO Pack

Installing StruxureWare Data Center Operation PRO Pack
Configuring StruxureWare Data Center Operation PRO Pack

Page 573
Working with StruxureWare Data Center Operation PRO Pack
Overview of how to work with StruxureWare Data Center Operation: PRO Pack in the applications involved.Before you can begin using
StruxureWare Data Center Operation: PRO Pack, you must have finished the installation and configuration process by completing these
steps.

1. In Microsoft System Center Operations Manager, review the list of configured Virtual Machine Manager servers.

Note

The management pack runs discovery tasks at an interval of 4 hours, so it may take a while for the list to refresh.

2. In StruxureWare Data Center Operation, 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 StruxureWare Data Center Operation, 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

4. In System Center Operations Manager Virtual Machine Hosts view, review the impact data from StruxureWare Data Center Operation
to get an overview and monitor if the hosts are healthy.

5. In Virtual Machine Manager, monitor the hosts and implement the PRO tips.

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.

Page 574
 See also

StruxureWare Data Center Operation: PRO Pack

Page 575
Working with Impact Analysis in StruxureWare Data Center Operation
1. 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.
2. Associate the servers in the layout with your virtual hosts by dragging a server from the Unassociated Devices pane over the
server representing it in the layout.
3. 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.

See also

StruxureWare Data Center Operation: PRO Pack

Page 576
Working with StruxureWare Data Center Operation PRO Pack views in System
Center Operations Manager
When the StruxureWare Data Center Operation: PRO Pack has been imported and configured in System Center Operations Manager, a
StruxureWare Data Center Operation: PRO Pack folder with two views will be available.

1. In Monitoring, select StruxureWare Data Center Operation: PRO Pack and observe the two views listed.
2. Click StruxureWare Data Center Operation and observe the view open with a StruxureWare Data Center Operation list view and
a Detail View.
StruxureWare Data Center Operation servers that have been set up to communicate with the System Center Operations
Manager server appear in the list.

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 StruxureWare Data Center Operation server itself is not monitored by System Center
Operations Manager.

3. Click a list item and observe the details for the selected item.
4. 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 StruxureWare Data Center Operation servers appears in this view.
5. Click a list item and observe the details for the selected item.
6. Right-click Impacted Virtual Machine Hosts, and select Personalize view... Then select the StruxureWare Data Center
Operation data that you want to display in Virtual Machine Manager, such as Room Name, Rack Name, etc.

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.

See also

StruxureWare Data Center Operation: PRO Pack

Page 577
Working with StruxureWare Data Center Operation PRO Pack PRO Tips in Virtual
Machine Manager
The StruxureWare Data Center Operation: PRO Pack PRO tips are communicated to Virtual Machine Manager. You can manually
implement the PRO tips, or set up the system to automatically do so.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.

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 StruxureWare Data Center Operation: PRO Pack PRO tips as only impacts of severity level of critical are received.

1. 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.
2. Select the PRO tip, and review the details about the issue that caused the PRO tip and how to resolve the issue.
3. Click Implement to implement the recommended action to resolve the issue, or click Dismiss to remove the tip and close the P
RO 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.

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.

See also

StruxureWare Data Center Operation: PRO Pack

Page 578
Troubleshooting virtualization issues
You can troubleshoot any StruxureWare Data Center Operation: PRO Pack issues in the Event Viewer Application log.
Type of events that you might see:

Discovery
Monitoring
Recovery

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 StruxureWare Data Center Operation.
StruxureWare Data Center Operation: PRO Pack retrieves data from StruxureWare Data Center Operation 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

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.

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, StruxureWare Data Center Operation: PRO Pack 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.

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.

See also

StruxureWare Data Center Operation: PRO Pack

Page 579
StruxureWare Data Center Operation PRO Pack PRO tip implementation rules
List of recovery rules applied for virtual machine hosts in or outside clusters.

Hyper-V hosts If there are hosts in a cluster, impacted hosts are put in maintenance mode.
in a cluster
Virtual machines on those hosts are migrated within the cluster.

Hyper-V hosts If there are hosts outside a cluster, the recovery script finds potential hosts
outside a cluster
and virtual machines are migrated from the impacted host.
The status of the impacted host is changed from available to unavailable.

Stand-alone If there is one host in a cluster, the virtual machines on the host will be put in
Hyper-V host in
saved state and the host is still put in maintenance mode.
a cluster
Virtual machines on that host are not migrated from that host.

Stand-alone If there is a stand-alone host outside a cluster, an error message is displayed

Hyper-V host
in the PRO tip.
outside cluster
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.

Multiple If multiple hosts are being impacted at the same time, a PRO tip is created
Hyper-V hosts
for each impacted host. The PRO tips will be automatically implemented if
in maintenance
mode automatic implementation of PRO tips has been configured. Otherwise, you
should manually implement the PRO tips.

Virtual machine If there are Hyper-V hosts in a cluster that have been set to be excluded from
is excluded from
PRO host-level action, the hosts are put in maintenance mode. This means
PRO host-level
action 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.

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.

See also

StruxureWare Data Center Operation: PRO Pack

Page 580
StruxureWare Data Center Operation: PRO Pack supported alarm types
These standard alarm types are supported in StruxureWare Data Center Operation: PRO Pack.

Note

The alarms with the exact wording as listed are supported. Any alarms with a different wording will not be recognized by the Str
uxureWare Data Center Operation: PRO Pack.
However, it is possible to customize the critical alarm and threshold configuration for migration of impacted servers.

APC/MGE The battery power is too low to continue to support the load; the UPS will transfer
UPS
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.

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

APC InRow RC:

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

Page 581
 See also

StruxureWare Data Center Operation: PRO Pack

Page 582
StruxureWare Data Center Operation: IT Optimize
On this page:

Installation and upgrade

Configuration
Discovery of StruxureWare Data Center IT Optimize server subnets
Association of discovered IT assets
Monitoring power and CPU utilization
Configuration
Association of live IT assets with the data center model
Reports
System requirements

StruxureWare Data Center: IT Optimize (ITO) provides insight into the IT layer of the data center through integration with external IT
systems. The integration is handled by the StruxureWare Data Center IT Optimize server through either:

SSH (discoveries on Linux)

SNMP (discoveries on Linux)
WMI (discoveries on Windows)
VMware (discoveries on ESXi/VMware guest)

You can use StruxureWare Data Center: IT Optimize to identify any servers in the data center that are running but not really being used.
You will save unnecessary power by identifying and consolidating or retiring these servers. The system uses the actual power draw
rather than nameplate values to obtain much better accuracy.

For information about supported devices, see the Intel documentation here.

Watch this video tutorial to learn how to Install and configure the server, and discover devices in StruxureWare Data Center Operation.

Installation and upgrade

See how to install and upgrade here.

Configuration
You can configure the StruxureWare Data Center IT Optimize server communication to external systems Configuring StruxureWare Data
Center IT Optimize Server Integration such as Cisco UCS Manager, StruxureWare Data Center: IT Power Control powered by Intel, or
VMware vSphere® in System Setup>External System Configuration.

Discovery of StruxureWare Data Center IT Optimize server subnets

When the StruxureWare Data Center IT Optimize server communication has been configured, you can configure discovery of the assets
on various network subnets on the StruxureWare Data Center IT Optimize server. The discovery enables the system to agent less scan
the defined IP range and monitor changes in power and CPU utilization on the servers. To work with the values in the StruxureWare
Data Center Operation layout, the only remaining step is to associate the discovered IT assets with servers in the data center layout.

Association of discovered IT assets

You can associate a discovered asset with the server representing it in the data center layout by dragging it from the Unassociated
Devices pane on top of the corresponding server in the rack layout. You can also associate multiple assets in Associating live data from
an external system to the layout in one operation by using the multi-associate option.
When you have associated an asset, it disappears from the list of unassociated devices and you can see the power and or CPU
utilization data displayed in the layout.

Monitoring power and CPU utilization

When the system has been configured to retrieve data from the external systems and the devices have been discovered and associated
with assets in the data center layout, power and CPU utilization values from these systems show in the IT Optimize and Power overlays

Page 583
when you hover over a server in the layout and get a tooltip presenting Server CPU Utilization or Server Power Utilization.

For example, you'll see a graphical representation of the server CPU utilization in the IT Optimize overlay tooltip:

Color Description

Red Assets reporting less than 2% utilization

Yellow Assets reporting between 2% and 10% utilization

Green Assets reporting above 10% utilization

Configuration

Configuring StruxureWare Data Center IT Optimize Server Integration

Configuring IT Asset Discovery

Association of live IT assets with the data center model

Associating Live Data from an External System to the Layout

Reports

Underutilized Servers Report

Server Power Consumption Report
Server Utilization Report

System requirements

StruxureWare Data Center IT Optimize Server Requirements

StruxureWare Data Center IT Optimize client requirements
StruxureWare Data Center: IT Optimize security

Page 584
What's new in IT Optimize

ITO 7.5.6

Windows installer supports installation on Windows 2012, 2012 R2 and Windows 2016.
Java runtime environment updated from JRE 1.6 to 1.8
Intel DCM packages upgraded from DCM 4.0 to DCM 4.2
Intel vKVM packages upgraded from vKVM 1.3 to vKVM 1.4
IT Optimize web service updated to only accept TLSv1.2 connections

Issues fixed

Bug that prevented IT Optimize from being installed in an alternate directory has been fixed.
Bug that prevented backups of the DCM database from completing successfully has been fixed.

Page 585
Installing IT Optimize

Follow the below steps or watch this video tutorial.

Prerequisites

Download the installation file from a location provided by your local technical support team. To locate the telephone number for your
region, visit Contact Us.

1. Type the server's IP address in a Web browser.

2. Click to download IT Optimize for one of the supported operating systems.

Installing ITO on Windows

1. Browse to the location of the downloaded StruxureWareItOptimize-setup.zip file and extract the (3) files.
2. Double-click the StruxureWareItOptimize-setup.xxx file and follow the instructions in the wizard to install StruxureWare Data
Center IT Optimize server and Intel's DCM server.
The default installation directory is C:\Program Files\Schneider-Electric\ITOptimize.
The Web application port is the web services port used by StruxureWare Data Center Operation to communicate with
the StruxureWare Data Center IT Optimize server. This port number must match the one specified in the external
system configuration when configuring the system integration in StruxureWare Data Center Operation
The Windows user account will run the IT Optimize services on the StruxureWare Data Center IT Optimize server. It
must be a valid local or domain based Windows user with local administrator rights belonging to the "logon as a service"
role. See how to enable the user to "logon as a service": http://technet.microsoft.com/en-us/library/cc794944(v=ws.10).
aspx
The default TCP port used by IT Optimize to access the embedded MySQL database is 3306.
3. Verify the installation and connectivity.
a. Browse to the ITO-Lite client, https://localhost:8090, to verify the installation was completed successfully.
In some facilities, port 8090 may be blocked by firewall or other network policies. If the IT Optimize web services port
was changed during installation, substitute 8090 with the new port address.
4. Browse to the DCM server GUI to test connectivity to the Intel DCM server, http://localhost:8688/DataCenterManager/, to test
connectivity to the Intel DCM server.

You now have DCM and IT Optimize services running on the Windows host.

Installing ITO on Linux

1. Logon to the StruxureWare Data Center IT Optimize server as a root level user.
2. Use a browser to access the DCO server and download the StruxureWare Data Center: IT Optimize software.
3. If a browser is not available, download the StruxureWare Data Center: IT Optimize software to an alternate host and transfer the
Linux installer to the StruxureWare Data Center IT Optimize server.
4. Run the Linux installer from the Linux command line:

# ./StruxureWareItOptimize-setup.linux.x32.bin

Language Selection

Please select the installation language

[1] English - English

[2] French - Français

[3] Italian - Italiano

[4] German - Deutsch

[5] Spanish - Español

[6] Russian - Ð ÑÑÑкий

[7] Brazilian Portuguese - Português Brasileiro

[8] Korean - íêµ-ì́

[9] Japanese - æ¥æ¬èª

[10] Simplified Chinese - ç®ä½ä¸-æ

[11] Traditional Chinese - ç¹ä½ä¸-æ

Page 586
Please choose an option [1] : 1

----------------------------------------------------------------------------

Welcome to the Schneider Electric IT Optimize Setup Wizard.

----------------------------------------------------------------------------

ITOptimize Configuration

Please configure the following ITOptimize installation settings.

Please specify the directory where Schneider Electric IT Optimize will be

installed.

Installation Directory [/opt/SchneiderElectric/ITOptimize]: <ENTER>

The TCP port used by the ITOptimize web application.

ITOptimize Web Application Port Setting [8090]: <ENTER>

----------------------------------------------------------------------------

ITOptimize Database Configuration

Please configure the ITOptimize database settings.

The TCP port used by the ITOptimize database instance.

DataBase Port Setting [3306]: <ENTER>

----------------------------------------------------------------------------

Setup is now ready to begin installing Schneider Electric IT Optimize on your

computer.

Do you want to continue? [Y/n]: Y

----------------------------------------------------------------------------

Please wait while Setup installs Schneider Electric IT Optimize on your

computer.

Installing

0% ______________ 50% ______________ 100%

#########################################

----------------------------------------------------------------------------

Setup has finished installing Schneider Electric IT Optimize on your computer.

Launch Schneider Electric IT Optimize Services now? [Y/n]: Y

Page 587
Page 588
Upgrading IT Optimize
To upgrade to StruxureWare Data Center: IT Optimize, follow the regular installation procedure. The system will detect an existing
installation and ask if you want to upgrade.

Prerequisites:

Verify the StruxureWare Data Center IT Optimize server meets the minimum requirements.
Note that StruxureWare Data Center: IT Optimize also includes Intel's DCM server. Intel's DCM server must co-exist on the
same server as IT Optimize. Memory requirements for the server have increased to 4GB of memory. It cannot be accessed on a
remote server.
Create a backup of the existing StruxureWare Data Center: IT Optimize installation using the Webmin server configuration
interface to backup StruxureWare Data Center Operation Backing up and restoring backup, or using the ITO-lite client GUI, http
s://localhost:8090, to create a backup.
1. Download the installation file from a location provided by your local technical support team. To locate the telephone number for
your region, visit Contact Us.
a. Type the server's IP address in a Web browser.
b. Click to download IT Optimize for one of the supported operating systems.
The following instructions apply to Windows.
2. Browse to the location of the downloaded StruxureWareItOptimize-setup.zip file and extract the (3) files.
3. Double-click the StruxureWareItOptimize-setup.xxx file and follow the instructions in the wizard to install StruxureWare Data
Center IT Optimize server and Intel's DCM server.
4. Confirm that you want to upgrade.
5. Verify the installation and connectivity.
a. Browse to the ITO-Lite client, https://localhost:8090, to verify the installation was completed successfully.
In some facilities, port 8090 may be blocked by firewall or other network policies. If the IT Optimize web services port
was changed during installation, substitute 8090 with the new port address.
6. Browse to the DCM server GUI, http://localhost:8688/DataCenterManager/, to test connectivity to the Intel DCM server.

You have now upgraded DCM and StruxureWare Data Center: IT Optimize and have the services running on the Windows host.

See also

Installing IT Optimize
StruxureWare Data Center IT Optimize Server Requirements

Page 589
StruxureWare Data Center IT Optimize Server Requirements
The StruxureWare Data Center IT Optimize server requires a dedicated server to be deployed for its use. The system may be a physical
device or a virtual machine and it must have network connectivity to the targeted data center assets.

Windows: Windows 2012, 2012 R2, and 2016 (64-bit only)

Linux Environments: CentOS 6.x, 7.x, Redhat 6.x, 7.x (64-bit only)
CPU: Minimum 2 CPUs, 4 CPUs are recommended.
Memory: Recommended 4GB memory. Maximum 8GB.
Storage: Minimum 20GB disk space. Recommended 50GB.

If using server access, the hostname of the IT Optimize server must be resolvable in hosts or DNS from all Data Center Operation client
s.

IT Optimize licenses must be installed on the Data Center Operation server. Data Center Operation server must be running version 8.0
or newer.

Windows specific requirements:

IT Optimize must be installed by an Administrator level user.

The IT Optimize services must run as a user which has been granted the "Logon as a Service" privilege.

See also

System requirements

Installing IT Optimize

Restoring IT Optimize backup

StruxureWare Data Center Operation: IT Optimize

Page 590
StruxureWare Data Center IT Optimize client requirements
Access to the StruxureWare Data Center: IT Optimize user interface is provided through the use of standard web browsers. These web
browsers are supported:

Internet Explorer 7.x or 8.x (IE 9 will be supported in a future product release)
Firefox 3.x (Firefox 4.x and 5.x will be supported in a future product release)
Adobe's flash player 10.3.x or newer plug-in or add-on must also be installed and added to your browser to successfully access
the StruxureWare Data Center: IT Optimize web interface. The most recent version of the flash player for the appropriate
browser (recommended). See Adobe's web site for more information.

The display used to view the StruxureWare Data Center: IT Optimize graphical interface must be capable of 1024x768 or higher
resolution.
For StruxureWare Data Center IT Optimize server installations on Windows servers, the IT Optimize service must run as a user that has
been granted the Logon as Service privilege.

See also

StruxureWare Data Center IT Optimize Server Requirements

StruxureWare Data Center Operation: IT Optimize

Page 591
Configuring StruxureWare Data Center IT Optimize Server Integration
Configure user credentials to allow StruxureWare Data Center Operation to communicate with the StruxureWare Data Center IT
Optimize server and receive device data and alarms.

It is possible to integrate with multiple StruxureWare Data Center IT Optimize servers.

1. Set up the server connection in StruxureWare Data Center Operation.

a. Select System Setup>External System Configuration.
b. Click Add server, and select StruxureWare Data Center IT Optimize server as the server type.
c. Type the StruxureWare Data Center IT Optimize server information, host name and IP address.
2. Click Test to test the connection.

The Polling interval option is a setting relevant for data on the StruxureWare Data Center IT Optimize server only. It defines how often
the StruxureWare Data Center IT Optimize server requests CPU utilization data from the devices.

There is no setting defining how often StruxureWare Data Center Operation requests data from the StruxureWare Data Center IT
Optimize server. These are predefined (power and CPU utilization data: every 10 secs, new or changes to devices: every 60 secs).

See also

StruxureWare Data Center Operation: IT Optimize

Configuring external system integration
StruxureWare Data Center: IT Optimize security

Page 592
Workaround for ITO discovery of the StruxureWare Data Center Operation server

Warning

This operation will reduce security on the Data Center Operation server.

On the Data Center Operation server, to work around the security restrictions preventing ITO discovery:

1. Log on to the server with an SSH client.

For example, use PuTTY. You can download it from here.
2. Type the command sudo sed -i -e "s/^#%sudo/%sudo/g" /etc/sudoers.d/itodiscovery and press Enter.

If you are running a cluster, perform the above steps on all nodes.

If you reinstall or upgrade the server, you must perform the above procedure again.

See also

Configuring StruxureWare Data Center IT Optimize Server Integration

Page 593
StruxureWare Data Center: IT Optimize security
This page contains StruxureWare Data Center: IT Optimize security details.

StruxureWare Data Center: IT Optimize functionality

There are two conditions which cause StruxureWare Data Center: IT Optimize to reach out to a server. They are discovery and polling.

During discovery, for WMI, SSH, and VMware protocols, ITO performs a logon to the target server, and pulls a series of information
from the host including server make and model, IP, serial number, OS type, CPU details (make/model, cache, speed,...), Memory
details (make/model, size, type, ...). SNMP discovery is similar, except no physical logon to the host is required. After initial discovery, a
discovery of a Windows or Linux server only needs to occur if the physical hardware changes. Often running discoveries less than once
a month is enough but must be based on server changes done in the data center.

Polling occurs when ITOcontacts the target server to pull CPU utilization information. In this case, only previously discovered servers
are polled. By default, polls occur every five minutes. This value can be configured using the DCO GUI to occur as infrequently as every
30 minutes. So having 1000 discovered hosts, you can expect approximately 100k of polling data to be read from servers every 5
minutes. Overall load on the target servers is low. In our labs, we have a large set of ITOconfigurations discovering and poling a set of
live servers. They are all polling and discovering the same servers 24x365. The average CPU utilization of our idle lab servers (so only I
TOdiscover and polling is occurring on them) is approximately 3%.

Tip

If you want to check if the port 8090 is responding from DCO to ITO you can use the following command:

netstat -aln | awk '$6 == "LISTEN" && $4 ~ "8090$"'

Network protocol and ports

Protocol Transfer Port(s) Network Credentials/Access Encryption Commands

protocol

WMI TCP Request: Discovery queries WMI connections between hosts Credential information is WMI
135 between 3K and 10K of require valid user credentials on the always encrypted using Command
data (on average) per remote system. NTLM and/or Kerberos Details
Response: discovered asset. encryption.
1024-655 The credentials should be encrypted
35 Polling queries approx. on Linux (using j-Interop) as well as
60 bytes of data per Windows (using the native Windows
WMI asset per poll. Polling libraries).
Windows interval can be
Required configured in the StruxureWare Data Center: IT
Ports external system Optimize polls Windows server WMI
configuration. namespace. The specified user
account must have local administrator
access to query disk related details
from the namespace.

SNMP TCP/UDP 161, 162 Discovery queries StruxureWare Data Center: IT No encryption is used for SNMP
between 3K and 10K of Optimize uses a read-only community SNMP communication Command
data (on average) per string to pull values from a set of Details
discovered asset. server OIDs or Blade Chassis OIDs Both SNMP v1 and v2
are supported.
Polling queries approx.
60 bytes of data per
asset per poll. Polling
interval can be
configured in the
external system
configuration.

VMware TCP 80, 443 Discovery queries SSL connections to VMware web Encrypted connection VMware
vSphere between 3K and 10K of services api's to pull ESX server and (SSL) to the default https vSphere
Web data (on average) per guest utilization information port (443) key length is Web Service
Service discovered asset. determined by server command
Password authentication is used, no details
Polling queries approx. keys are stored on the ITOserver.
60 bytes of data per
asset per poll. Polling VMware protocol discoveries require a
interval can be local user account on each ESX host.
configured in the The account must belong to at least
external system the readonly role. It does NOT require
configuration. access to the ESX shell.

Connections are made

on port 443 by default

Page 594
 SSH TCP 22 Discovery queries Discovery commands require root level Server determine cipher SSH
between 3K and 10K of access. "sudo" may be used to type and key length. command
data (on average) per complete this task a guide can be details
discovered asset. found here. Polling of Linux and Unix SSH v2 is supported, v1
clients is completed using SNMP. is not supported.
Polling queries approx.
60 bytes of data per
asset per poll. Polling
interval can be
configured in the
external system
configuration.

TCP TCP 7 Echo functionality to - - -

ECHO make sure discovered
device is alive

ICMP IP N/A Ping/Echo functionality - - -

ECHO to make sure discovered
device is alive

IPMI UDP 623 Discovery queries IPMI connections between hosts Depending on
between 3K and 10K of require valid user credentials on the configuration and BMC
data (on average) per remote system. interface
discovered asset.

Polling queries approx.

60 bytes of data per
asset per poll. Polling
interval can be
configured in the
external system
configuration.

Postgres UDP 3306 Localhost only - internal Handled by ITO system Yes -
ITO database connection

HTTP TCP 8090 Management Console Handled by DCO/ITO integration - -

interface for ITO interface

HTTPs TCP 8643 Management Console Localhost only - -

interface for Intel DCM

HTTP UDP 8688 Management Console Localhost only - -

interface for Intel DCM

Postgres UDP 6443 Localhost only - internal Localhost only - -

Intel DCM database
connection

Server Access - related protocols

VNC RFB 5900 Bandwidth usage is very More info can be found here The encryption is -
(default) depended on screen depended on the OS and
activity and usage the installed VNC
application

SSH TCP 22 Since text only is More info can be found here Server determine cipher -
transferred the type and key length
bandwidth requirement is
very limited.

RDP TCP 3389 Bandwidth usage is very More info can be found here The encryption is -
(default) depended on screen depended on the OS and
activity and usage the installed application.
Default 128-bit
encryption, using the RC
4 encryption algorithm

A 1024-bit RSA key is generated and used for SSL communication. The key is self- signed and will generally require the user to trust the
signing authority. When connecting to an ITOserver, DCOpresents a dialog asking the user to trust the certificate. The keystore where
the RSA key is stored is password protected.

Packages being used in StruxureWare Data Center: IT Optimize server

Packages and their version numbers being used in StruxureWare Data Center: IT Optimize server can be found here.

Firewall configuration
StruxureWare Data Center: IT Optimize does not contain any firewall in the installation. The firewall must be allowing ports as needed
from the above table of ports and protocols.

Page 595
Software Vulnerability, Scan(s) and Certifications
Status in terms of general known vulnerabilities can be found here.
A software scanning tool is run against every release of the product. The results are investigated and needed action in terms of security
updates etc. taken. The scanning tool used is named Nessus.
Nessus is a network vulnerability scan utility. It scans the server as a network device and not just a webserver. Please contact us for
details.

Antivirus

Antivirus tools are not provided with the StruxureWare Data Center: IT Optimizeserver installation. Antivirus is allowed on the StruxureW
are Data Center: IT Optimizeserver and target client. It is recommended to exclude the data folders for the databases to maintain
performance and reduce problems when installing and upgrading ITO software.

Logging

Log files can be found in the .log folder in the installation directory of the StruxureWare Data Center: IT Optimize server

Database architecture

StruxureWare Data Center: IT Optimizedatabase technology is MariaDB version 5.2.14 and cannot be exchanged with any other
database type or technology.

See also

StruxureWare Data Center Operation: IT Optimize

Page 596
WMI Command Details
WMI protocol requires a local or domain based user account which has local administrator access on the target host. The user account
will logon and probe the following WMI namespace values on the target server.

Win32_ComputerSystemProduct.Caption

Win32_ComputerSystemProduct.Vendor

Win32_OperatingSystem.Caption

Win32_ComputerSystem.Name

Win32_ComputerSystem.Manufacturer

Win32_ComputerSystem.Model

Win32_ComputerSystemProduct.IdentifyingNumber

Win32_ComputerSystemProduct.UUID

Win32_OperatingSystem.Caption

Win32_OperatingSystem.Caption

Win32_PhysicalMemory.formFactor

Win32_PhysicalMemory.deviceLocator

Win32_PhysicalMemory.manufacturer

Win32_PhysicalMemory.model

Win32_PhysicalMemory.serialNumber

Win32_PhysicalMemory.capacity

Win32_PhysicalMemory.speed

Win32_PhysicalMemory.deviceLocator

Win32_PhysicalMemory.memoryType

Win32_DiskDrive.size

Win32_DiskDrive.caption

Win32_DiskDrive.interfaceType

Win32_DiskDrive.name

Win32_DiskDrive.manufacturer

Win32_DiskDrive.model

Win32_DiskDrive.deviceID

MSSMBIOS_RawSMBiosTables.DmiRevision

MSSMBIOS_RawSMBiosTables.SmbiosMajorVersion

MSSMBIOS_RawSMBiosTables.SmbiosMinorVersion

MSSMBIOS_RawSMBiosTables.Size

MSSMBIOS_RawSMBiosTables.SMBiosData

Win32_PerfFormattedData_PerfOS_System.SystemUpTime

Win32_PerfRawData_PerfOS_Processor.Name?where name = '_Total'

Win32_PerfRawData_PerfOS_Processor.PercentProcessorTime?where name = '_Total'

Win32_PerfRawData_PerfOS_Processor.PercentProcessorTime?where name = '_Total'

Win32_PerfRawData_PerfOS_Processor.Timestamp_Sys100NS?where name = '_Total'

Win32_ComputerSystemProduct.IdentifyingNumber

Win32_PerfRawData_PerfOS_System.Frequency_Object

Win32_PerfRawData_PerfOS_System.SystemUpTime

Win32_PerfRawData_PerfOS_System.Timestamp_Object

Win32_QuickFixEngineering.HotFixId?where HotFixId like '%KB932370%'

Win32_Processor.name

Page 597
Win32_Processor.Family

Win32_Processor.Architecture

Win32_Processor.Family

Win32_Processor.Family

Win32_Processor.CurrentClockSpeed

Win32_Processor.MaxClockSpeed

Win32_Processor.ExtClock

Win32_Processor.name

Win32_Processor.L2CacheSize

Win32_Processor.SocketDesignation

Win32_Processor.ProcessorId

Win32_Processor.ProcessorId

Win32_Processor.UpgradeMethod

Win32_Processor.Version

Win32_Processor.Level

Win32_Processor.Revision

Win32_Processor.name

Win32_Processor.name

Win32_Processor.name

HPSA_DiskDrive.driveInterface

HPSA_DiskPhysicalPackage.name

HPSA_DiskPhysicalPackage.manufacturer

HPSA_DiskPhysicalPackage.model

HPSA_DiskPhysicalPackage.serialNumber

Page 598
WMI Windows Required Ports
Discovering Windows hosts from a Windows based ITO server.

ITO relies on the Windows Management Interface (WMI), RPC, and DCOM to communicate from the ITO server to the target client so
the following windows based ports are required for WMI based discovery.

Application protocol Protocol Ports

RPC TCP 135

RPC over HTTPS TCP 593

NetBIOS Datagram Service UDP 138

NetBIOS Name Resolution UDP 137

NetBIOS Session Service TCP 139

SMB TCP 445

DCOM uses dynamic port ranges to respond to communication requests from a source server. The dynamic port ranges are:

Windows 2000, XP, and Server 2003: ports 1025 to 5000

Windows 2008, Vista and later : ports 49152 to 65535

Page 599
SNMP Command Details
Here is a list of the SNMP OID's used by AIX Polling IBMServerInfo
IT Optimize.
1.3.6.1.2.1.1.5 1.3.6.1.2.1.1.5

1.3.6.1.4.1.2.3.1.2.2.2.1.1.124 1.3.6.1.4.1.2.6.159.1.1.60.1.1.1-System
DeviceTypes
1.3.6.1.4.1.2.3.1.2.2.2.1.1.124 1.3.6.1.4.1.2.6.159.1.1.60.1.1.4
1.3.6.1.2.1.1.2
1.3.6.1.4.1.2.3.1.2.2.2.1.1.121 1.3.6.1.4.1.2.6.159.1.1.60.1.1.5.6
1.3.6.1.2.1.1.7
1.3.6.1.4.1.2.3.1.2.2.2.1.1.122 1.3.6.1.4.1.2.6.159.1.1.60.3.1.10
1.3.6.1.4.1.232.22.1.1
1.3.6.1.4.1.2.3.1.2.2.2.1.1.123 1.3.6.1.4.1.2.6.159.1.1.140.1.1.3
1.3.6.1.4.1.2.3.51.2.2.21.1.1.1
1.3.6.1.4.1.2.3.1.2.2.2.1.1.124 1.3.6.1.4.1.2.6.159.1.1.140.1.1.3
1.3.6.1.4.1.674.10892.2.1.1.1
1.3.6.1.4.1.2.6.159.1.1.140.1.1.3
1.3.6.1.2.1.4.20.1.1
PolledServerInfo 1.3.6.1.4.1.2.6.159.1.1.140.1.1.3

1.3.6.1.2.1.1.5 1.3.6.1.4.1.2.6.159.1.1.140.1.1.3
DeviceVendors
1.3.6.1.2.1.25.1.1 1.3.6.1.4.1.2.6.159.1.1.140.1.1.6
1.3.6.1.4.1.674.10892.1.1.1
1.3.6.1.4.1.2.6.159.1.1.140.1.1.7
1.3.6.1.4.1.232.1.1.1
DellServerInfo 1.3.6.1.4.1.2.6.159.1.1.140.1.1.12
1.3.6.1.4.1.2.6.159.1.1.60.1.1.4
1.3.6.1.4.1.674.10892.1.300.10.1.15 1.3.6.1.4.1.2.6.159.1.1.140.1.1.13
1.3.6.1.2.1.1.2
1.3.6.1.4.1.674.10892.1.300.10.1.8 1.3.6.1.4.1.2.6.159.1.1.140.1.1.13
1.3.6.1.4.1.232.22.1.1
1.3.6.1.4.1.674.10892.1.300.10.1.9 1.3.6.1.4.1.2.6.159.1.1.140.1.1.11
1.3.6.1.4.1.2.3.51.2.2.21.1.1.1
1.3.6.1.4.1.674.10892.1.300.10.1.11 1.3.6.1.4.1.2.6.159.1.1.140.1.1.13
1.3.6.1.4.1.674.10892.2.1.1.1
1.3.6.1.4.1.674.10892.1.1100.30.1.23 1.3.6.1.4.1.2.6.159.1.1.140.1.1.13

1.3.6.1.4.1.674.10892.1.1100.30.1.16 1.3.6.1.4.1.2.6.159.1.1.140.1.1.13
DeviceOSes
1.3.6.1.4.1.674.10892.1.1100.30.1.8 1.3.6.1.4.1.2.6.159.1.1.120.1.1.7
1.3.6.1.2.1.1.1
1.3.6.1.4.1.674.10892.1.1100.30.1.10 1.3.6.1.4.1.2.6.159.1.1.120.1.1.13
1.3.6.1.2.1.1.2
1.3.6.1.4.1.674.10892.1.1100.30.1.12 1.3.6.1.4.1.2.6.159.1.1.120.1.1.14
1.3.6.1.4.1.6876.1.1
1.3.6.1.4.1.674.10892.1.1100.30.1.11 1.3.6.1.4.1.2.6.159.1.1.120.1.1.15
1.3.6.1.4.1.6876.1.2
1.3.6.1.4.1.674.10892.1.1100.30.1.13 1.3.6.1.4.1.2.6.159.1.1.120.1.1.16

1.3.6.1.4.1.674.10892.1.1100.40.1.11-4 1.3.6.1.4.1.2.6.159.1.1.120.1.1.11
Linux Polling
1.3.6.1.4.1.674.10892.1.1100.40.1.13 1.3.6.1.4.1.2.6.159.1.1.120.1.1.10
1.3.6.1.4.1.2021.11/2
1.3.6.1.4.1.674.10892.1.1100.32.1.7 1.3.6.1.4.1.2.6.159.1.1.120.1.1.13
1.3.6.1.4.1.2021.11/53
1.3.6.1.4.1.674.10892.1.1100.30.1.15 1.3.6.1.4.1.2.6.159.1.1.120.1.1.8
1.3.6.1.4.1.2021.11/53
1.3.6.1.4.1.674.10892.1.1100.30.1.24
1.3.6.1.4.1.2021.11/50
1.3.6.1.4.1.674.10892.1.1100.30.1.25 HPBladeChassisInfo
1.3.6.1.4.1.2021.11/51
1.3.6.1.4.1.674.10892.1.1100.30.1.16 1.3.6.1.4.1.232.22.2.3.1.1.1/9
1.3.6.1.4.1.2021.11/52
1.3.6.1.4.1.674.10892.1.1100.50.1.12 1.3.6.1.4.1.232.22.2.3.1.1.1/3
1.3.6.1.4.1.2021.11/53
1.3.6.1.4.1.674.10892.1.1100.50.1.8 1.3.6.1.4.1.232.22.2.3.1.1.1/7
1.3.6.1.4.1.674.10892.1.300.10.1.11
1.3.6.1.4.1.674.10892.1.1100.50.1.21 1.3.6.1.4.1.232.22.2.3.1.1.1/8
1.3.6.1.4.1.2.6.159.1.1.60.3.1.10
1.3.6.1.4.1.674.10892.1.1100.50.1.22 1.3.6.1.4.1.232.22.2.3.1.1.1/8
1.3.6.1.4.1.232.2.2.2.1
1.3.6.1.4.1.674.10892.1.1100.50.1.23 1.3.6.1.4.1.232.22.2.4.1.1.1/3

1.3.6.1.4.1.674.10892.1.1100.50.1.14 1.3.6.1.4.1.232.22.2.4.1.1.1/4
Solaris Polling
1.3.6.1.4.1.674.10892.1.1100.50.1.15 1.3.6.1.4.1.232.22.2.4.1.1.1/4
1.3.6.1.4.1.2021.11/2
1.3.6.1.4.1.674.10892.1.1100.50.1.8 1.3.6.1.4.1.232.22.2.4.1.1.1/17
1.3.6.1.4.1.2021.11/53
1.3.6.1.4.1.674.10892.1.1100.50.1.7 1.3.6.1.4.1.232.22.2.4.1.1.1/6
1.3.6.1.4.1.2021.11/53
1.3.6.1.4.1.674.10893.1.20.130.4.1.11 1.3.6.1.4.1.232.22.2.4.1.1.1/16
1.3.6.1.4.1.2021.11/50
1.3.6.1.4.1.674.10893.1.20.130.4.1.2 1.3.6.1.4.1.232.22.2.4.1.1.1/18
1.3.6.1.4.1.2021.11/52

Page 600
1.3.6.1.4.1.2021.11/53 1.3.6.1.4.1.674.10893.1.20.130.4.1.3 1.3.6.1.4.1.232.22.2.4.1.1.1/8

1.3.6.1.4.1.674.10892.1.300.10.1.11 1.3.6.1.4.1.674.10893.1.20.130.4.1.6 1.3.6.1.4.1.232.22.2.5.1.1.1/5

1.3.6.1.4.1.2.6.159.1.1.60.3.1.10 1.3.6.1.4.1.674.10893.1.20.130.4.1.25 1.3.6.1.4.1.232.22.2.5.1.1.1/10

1.3.6.1.4.1.232.2.2.2.1 1.3.6.1.4.1.674.10893.1.20.130.4.1.7

IBMBladeChassisInfo

HPUX Polling HPServerInfo 1.3.6.1.4.1.2.3.51.2.2.21.1.1/1

1.3.6.1.2.1.1.5 1.3.6.1.2.1.1.5 1.3.6.1.4.1.2.3.51.2.2.21.1.1/2

1.3.6.1.4.1.11.2.3.1.1.15 1.3.6.1.4.1.232.2.2.4.2 1.3.6.1.4.1.2.3.51.2.2.21.1.1/3

1.3.6.1.4.1.11.2.3.1.1.15 1.3.6.1.4.1.232.2.2.2.1 1.3.6.1.4.1.2.3.51.2.2.21.3.1.1/3

1.3.6.1.4.1.11.2.3.1.1.13 1.3.6.1.4.1.232.1.2.2.1.1.3 1.3.6.1.4.1.2.3.51.2.2.21.3.1.1/3

1.3.6.1.4.1.11.2.3.1.1.14 1.3.6.1.4.1.232.1.2.2.1.1.8 1.3.6.1.4.1.2.3.51.2.2.21.4.1.1/1

1.3.6.1.4.1.11.2.3.1.1.16 1.3.6.1.4.1.232.1.2.2.1.1.4 1.3.6.1.4.1.2.3.51.2.2.21.4.1.1/6

1.3.6.1.4.1.11.2.3.1.1.15 1.3.6.1.4.1.232.1.2.2.1.1.21 1.3.6.1.4.1.2.3.51.2.2.21.4.1.1/6

1.3.6.1.4.1.232.1.2.2.1.1.7 1.3.6.1.4.1.2.3.51.2.2.21.4.1.1/7

PolledServerInfo 1.3.6.1.4.1.232.1.2.2.3.1.2-2 1.3.6.1.4.1.2.3.51.2.2.21.4.1.1/12

1.3.6.1.2.1.1.5 1.3.6.1.4.1.232.1.2.2.3.1.3 1.3.6.1.4.1.2.3.51.2.2.21.4.1.1/6

1.3.6.1.4.1.11.2.3.1.1.1 1.3.6.1.4.1.232.6.2.14.13.1.19-!2 1.3.6.1.4.1.2.3.51.2.2.21.4.1.1/8

1.3.6.1.4.1.232.6.2.14.13.1.7 1.3.6.1.4.1.2.3.51.2.2.21.4.1.1/2

1.3.6.1.4.1.232.6.2.14.13.1.19-!2 1.3.6.1.4.1.2.3.51.2.2.10.1.1.1/2

1.3.6.1.4.1.232.6.2.14.13.1.6 1.3.6.1.4.1.2.3.51.2.2.10.1.1.1/10

1.3.6.1.4.1.232.3.2.5.1.1.45

1.3.6.1.4.1.232.3.2.5.1.1.64 DellBladeChassisInfo

1.3.6.1.4.1.232.3.2.5.1.1.3 1.3.6.1.4.1.674.10892.2.1.1/10

1.3.6.1.4.1.232.3.2.5.1.1.3 1.3.6.1.4.1.674.10892.2.1.1/2

1.3.6.1.4.1.232.3.2.5.1.1.51 1.3.6.1.4.1.674.10892.2.1.1/6

1.3.6.1.4.1.674.10892.2.1.2/1

1.3.6.1.4.1.674.10892.2.1.2/1

1.3.6.1.4.1.674.10892.2.5.1.1/1

1.3.6.1.4.1.674.10892.2.5.1.1/4

1.3.6.1.4.1.674.10892.2.5.1.1/4

1.3.6.1.4.1.674.10892.2.5.1.1/3

1.3.6.1.4.1.674.10892.2.5.1.1/5

1.3.6.1.4.1.674.10892.2.4.1.1/1

1.3.6.1.4.1.674.10892.2.4.1.1/13

Page 601
VMware vSphere Web Service
Here is a list of command strings used by IT Optimize

com.viridity.dcos.omstubs.OMSmbiosData$SMBSystemInfo#manufacturerStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBBaseBoard#manufacturerStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBSystemInfo#productNameStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBBaseBoard#productNameStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBSystemInfo#serialNumberStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBBaseBoard#serialNumberStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBSystemInfo#uuidBytes

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorFamily

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorFamily

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorFamily

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorFamily

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorFamily

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#currentSpeed

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#maxSpeed

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#externalClock

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorVersionStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#l2Cache.installedCacheSize

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#socketDesignationStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorId

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorId

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorUpgrade

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorId

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorId

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorId

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorVersionStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorVersionStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBProcessor#processorVersionStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#deviceLocatorStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#formFactor

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#memoryType

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#manufacturerStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#partNumberStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#serialNumberStringIndex

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#size

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#speed

com.viridity.dcos.omstubs.OMSmbiosData$SMBMemoryDevice#deviceLocatorStringIndex

HostSystem:summary.hardware.vendor

HostSystem:config.product.name

HostSystem:config.product.version

HostSystem:name

HostSystem:summary.hardware.vendor

Page 602
HostSystem:summary.hardware.model

HostSystem:summary.hardware.uuid

HostSystem:summary.hardware.otherIdentifyingInfo\identifierValue

HostSystem:summary.hardware.uuid

HostSystem:hardware.cpuPkg/description

HostSystem:hardware.cpuPkg/vendor

HostSystem:hardware.cpuPkg/cpuFeature

HostSystem:hardware.cpuPkg/cpuFeature

HostSystem:hardware.cpuPkg/cpuFeature

HostSystem:hardware.cpuPkg/hz

HostSystem:hardware.cpuPkg/hz

HostSystem:hardware.cpuPkg/busHz

HostSystem:hardware.cpuPkg/description

HostSystem:hardware.cpuPkg/index

HostSystem:hardware.cpuPkg/cpuFeature

HostSystem:hardware.cpuPkg/cpuFeature

HostSystem:hardware.cpuPkg/cpuFeature

HostSystem:hardware.cpuPkg/cpuFeature

HostSystem:hardware.cpuPkg/description

HostSystem:hardware.cpuPkg/description

HostSystem:hardware.cpuPkg/description

HostSystem:config.storageDevice.scsiLun/lunType

HostSystem:config.storageDevice.scsiLun/capacity/block

HostSystem:config.storageDevice.scsiLun/capacity/blockSize

HostSystem:config.storageDevice.scsiLun/lunType

HostSystem:config.storageDevice.scsiLun/canonicalName

HostSystem:config.storageDevice.scsiLun/lunType

HostSystem:config.storageDevice.scsiLun/vendor

HostSystem:config.storageDevice.scsiLun/lunType

HostSystem:config.storageDevice.scsiLun/model

HostSystem:config.storageDevice.scsiLun/lunType

HostSystem:config.storageDevice.scsiLun/deviceName

HostSystem:config.product.fullName

HostSystem:config.product.name

HostSystem:config.product.version

HostSystem:name

HostSystem:?fullName=sys.uptime.latest/value/value[last()]

HostSystem:?fullName=cpu.idle.summation;fullName=cpu.used.summation#0

HostSystem:?fullName=cpu.idle.summation;fullName=cpu.used.summation#1

HostSystem:?fullName=cpu.idle.summation;fullName=cpu.used.summation#0

HostSystem:?fullName=cpu.idle.summation;fullName=cpu.used.summation#0

HostSystem:?fullName=cpu.idle.summation;fullName=cpu.used.summation#1

HostSystem:summary.hardware.uuid

HostSystem:summary.hardware.otherIdentifyingInfo\identifierValue

Page 603
HostSystem:?fullName=cpu.idle.summation,fullName=cpu.used.summation#0

HostSystem:name

HostSystem:summary.hardware.uuid

HostSystem:summary.hardware.otherIdentifyingInfo\identifierValue

HostSystem:summary.hardware.uuid

HostSystem:hardware.cpuInfo.numCpuCores

HostSystem:hardware.cpuInfo.hz

HostSystem:hardware.cpuInfo.numCpuPackages

HostSystem:hardware.cpuInfo.numCpuThreads

VirtualMachine:config.name

VirtualMachine:config.guestFullName

VirtualMachine:guest.ipAddress

VirtualMachine:config.memoryAllocation.limit

VirtualMachine:config.hardware.numCPU

VirtualMachine:config.uuid

VirtualMachine:config.instanceUuid

VirtualMachine:config.locationId

VirtualMachine:runtime.host/summary.hardware.uuid

VirtualMachine:config.name

VirtualMachine:config.uuid

VirtualMachine:?fullName=cpu.usage.average/value/value

VirtualMachine:?fullName=cpu.usage.average

VirtualMachine:config.hardware.numCPU

VirtualMachine:?fullName=sys.uptime.latest/value/value[last()]

VirtualMachine:summary.config.cpuReservation

ClusterComputeResource:name

ClusterComputeResource:configurationEx/rule

ClusterComputeResource:host/summary.hardware.uuid

ClusterComputeResource:configurationEx/drsConfig

ClusterComputeResource:configurationEx/dpmConfigInfo

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWSystemInfo#header.id

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWSystemInfo#vendor

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWSystemInfo#product

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWSystemInfo#serial

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWSystemInfo#uuid

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#vendor

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#processorSpeed

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#processorMaxSpeed

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#externalClockSpeed

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#product

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#l2Cache.size

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#socketDesignation

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#processorId

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#processorId

Page 604
com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#processorId

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#processorId

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#product

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWProcessor#product

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWMemoryDevice#slot

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWMemoryDevice#vendor

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWMemoryDevice#product

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWMemoryDevice#serial

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWMemoryDevice#size

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWMemoryDevice#slot

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWDiskDevice#logicalName

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWDiskDevice#size

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWDiskDevice#description

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWDiskDevice#vendor

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWDiskDevice#product

com.viridity.dcos.omstubs.OMHardwareListerData$LSHWDiskDevice#serial

Page 605
SSH Sudo Discovery Configuration
ITO needs root level access to do the SSH discovery of devices. The discovery process can also be done using "sudo".

You must enable the "sudo" interface on the ITO server:

1. Set (or add) the viridity.datacollection.ssh.usesudo=true flag in the <INSTALL-DIR>/conf/viridity.dcos.properties file.

2. Restart the "Schneider Electric EnergyCenter" service on the Windows ITO server host.
3. The /etc/sudoers entries should be the following (the format may need to be customized for specific Linux versions):

defaults:itouser !requiretty

defaults:itouser !authenticate

itouser ALL=(ALL) NOPASSWD: /usr/sbin/dmidecode

itouser ALL=(ALL) NOPASSWD: /usr/sbin/lshw

itouser ALL=(ALL) NOPASSWD: /bin/dd

Page 606
SSH Command Details
SSH protocol requires root level access for several commands. For customers who wish to use "sudo", see here.

SSH commands (command paths may be OS specific e.g. /bin/hostname or /usr/bin/hostname. $SUDO maps to the location of the sudo
command)

/bin/uname -s

/bin/uname -i

/bin/uname -m

/bin/uname -r

/usr/bin/test -x /usr/bin/vmware && /usr/bin/vmware -v

/bin/hostname

/usr/bin/test -x /usr/bin/lsb_release && /usr/bin/lsb_release -d

$SUDO /bin/dd if=/dev/mem bs=1 skip=$$entry_point_location@@ count=32

/usr/bin/test -x /usr/sbin/lshw && $SUDO /usr/sbin/lshw -version

/usr/bin/test -x /usr/sbin/lshw && $SUDO /usr/sbin/lshw -xml

/usr/bin/test -x /usr/sbin/dmidecode && $SUDO /usr/sbin/dmidecode -V

/usr/bin/test -x /usr/sbin/dmidecode && $SUDO /usr/sbin/dmidecode --dump-bin /tmp/dmidecodedata.dat > /dev/null && /bin/cat
/tmp/dmidecodedata.dat

/usr/bin/hostname

/usr/sbin/smbios -w /tmp/smbiosdata.dat > /dev/null & /usr/bin/cat /tmp/smbiosdata.dat

/usr/local/bin/viriditylisthw

Page 607
StruxureWare Data Center: IT Optimize Software Vulnerabilities

StruxureWare Data Center: IT Optimize relevant security vulnerabilities

Vulnerability Answer Affects Fixed Comments

DCO in
DCO

FREAK (CVE-2 The vulnerability affects versions of StruxureWare 7.4.5 7.5 Please let us know if you need a patch for your
015-0204) Data Center: IT Optimize until and including version system. The patch will be created based on your
7.4.5. system setup.

The vulnerability will be solved with the next release of Patch for version 7.3.6
StruxureWare Data Center Operation.

Page 608
Upgrading IT Optimize 7.3.6 to Fix FREAK Vulnerability

Note

This patch is ONLY meant for IT Optimize 7.3.6, it is not compatible with other IT Optimize releases.

Verify the IT Optimize server is running release 7.3.6.0.82.

1. Go to folder "C:\Program Files\SchneiderElectric\ITOptimize\conf" (Assuming IT Optimize is installed in the default installation
directory)
2. This folder will contain files called "install-<version>.log" where <version> represents the installed ITO release.
3. The newest version of the install log file should be called "install-7.3.6.0.82.log" (older install logs is fine as long as the
7.3.6.0.82 version is present. There should not be a newer file (i.e. a 7.4.5 version).
4. If you are not running IT Optimize 7.3.6, then stop. The patch is meant only for ITO 7.3.6.

The patch is a single file which needs to replace an existing file on your IT Optimize server. Then the ITO service needs to be restarted.

Install Instructions (assuming IT Optimize is installed in the default installation directory)

1. Logon to the ITO server as a server administrative user (using remote desktop or directly on the server)
2. Stop the IT Optimize server process (The IT Optimize database process does not need to be stopped)
a. The service can be stopped from the Windows Services control panel window
b. Open the services panel
c. Right click on the "Schneider Electric EnergyCenter" and choose stop
i. If an error occurs when trying to stop this process then terminate the "EnergyCenter" process, called
"Energy~1.exe" from the windows task manager view by right-clicking on the process and choosing "end
process"
d. Windows might try to restart the EnergyCenter service, so re-check the windows services control and verify the service
is stopped. If not then stop the service from the services control panel.
3. Change to the following folder on the IT Optimize server: "C:\Program Files\SchneiderElectric\ITOptimize\lib"
4. You should find an existing viridity-common.jar file in this folder. Make a copy of it for backup purposes
5. Download the patch file viridity-common.jar and copy it to the folder replacing the existing viridity-common.jar file.
6. Start/Restart the "Schneider Electric EnergyCenter" which had been previously stopped.
7. Wait 2 or 3 minutes for the IT Optimize services to initialize.

Page 609
Software Packages in StruxureWare Data Center IT Optimize
Software packages used in StruxureWare Data Center: IT Optimize

Java 6 Update 24 on Linux (32-bit and 64-bit)

Java 6 Update 31 on Windows (32-bit and 64-bit)

antlr-2.7.6.jar

aopalliance-1.0.jar

aspectjrt.jar

aspectjweaver.jar

commons-beanutils-1.8.3.jar

commons-digester-2.0.jar

commons-collections-3.1.jar

dom4j-1.6.1.jar

DynamicJasper-3.1.3.jar

ejb3-persistence.jar

ehcache-core-2.1.0.jar

jasperreports-3.7.4.jar

kryo-1.01.jar

asm-3.2.jar

dcm-3.7.jar

minlog-1.2.jar

mail.jar

poi-3.6-20091214.jar

reflectasm-0.8.jar

liquibase.jar

log4j-1.2.14.jar

trilead-ssh2-build213.jar

slf4j-api-1.5.8.jar

slf4j-log4j12.jar

jacob.jar

j-interop.jar

jcifs-1.2.19.jar

jcl-core-2.2.1.jar

j-interopdeps.jar

jta-1.1.jar

hibernate3.jar

hibernate-annotations.jar

hibernate-commons-annotations.jar

javassist-3.9.0.GA.jar

jasypt-1.5.jar

Page 610
commons-lang-2.1.jar

quartz-1.6.5.jar

commons-dbcp-1.2.2.jar

commons-pool-1.3.jar

org.springframework.aop-3.1.2.RELEASE.jar

org.springframework.asm-3.1.2.RELEASE.jar

org.springframework.beans-3.1.2.RELEASE.jar

org.springframework.context-3.1.2.RELEASE.jar

org.springframework.context.support-3.1.2.RELEASE.jar

org.springframework.core-3.1.2.RELEASE.jar

org.springframework.expression-3.1.2.RELEASE.jar

org.springframework.instrument-3.1.2.RELEASE.jar

org.springframework.jdbc-3.1.2.RELEASE.jar

org.springframework.orm-3.1.2.RELEASE.jar

org.springframework.transaction-3.1.2.RELEASE.jar

org.springframework.web-3.1.2.RELEASE.jar

snmp4j-1.11.1.jar

xpp3_min-1.1.4c.jar

xstream-1.3.1.jar

gson-1.7.1.jar

commons-httpclient-3.1.jar

commons-io-2.0.jar

commons-codec-1.3.jar

commons-logging-1.1.1.jar

hsqldb.jar

jscience.jar

WinRun4J.jar

mysql-connector-java-5.1.13-bin.jar

vijava2u120091204.jar

Page 611
Configuring IT Asset Discovery
Configure IT asset discovery to allow scanning of the external system's network subnets to continuously monitor changes in the power
and CPU utilization of the running servers. These values will be available in StruxureWare Data Center Operation.

1. In Planning>Device Association, right-click a StruxureWare Data Center IT Optimize server in the Unassociated Devices pa
ne and select Configure Discovery, or double-click a server in the ITO Discoveries view (in 7.3.5, Server Discoveries view).
2. Follow the steps in the wizard to configure the subnets one by one.
a. Specify the network range properties: Type a subnet name and the IP range.
b. Specify the protocols and credentials for accessing the data on the servers. Recommended protocols:
WMI for discovery of Windows systems
VMware for discovery of ESXi/VMware Guests
SNMP for discovery of blade chassis configurations, Linux and Unix systems
SSH for discovery of Linux
IPMI
c. Choose whether to run a discovery immediately or schedule a discovery either at a specified date and time or
repeatedly at a specified interval.

You can also access the discovery configuration by clicking Discoveries: 0 in the status bar. If accessed from here rather than
right-clicking a server, you must specify which server to configure the subnets as the first step.

You can use the reported power and CPU utilization values to find and manage underutilized servers.

Watch this video tutorial to learn how.

WMI Recommended protocol for discovery of Windows systems

Requires Windows account credentials with local administrator rights on all discovered windows servers. In multi-domain environments,
the account will also require the "Distributed COM Users" group. Specification of a domain-based user is optional but recommended to
simplify deployment.

SNMP Recommended protocol for discovery of Blade Chassis configurations. SNMP is also used to poll Linux and Unix systems.
SNMP V1 and V2 are supported. SNMP V3 is supported from version 7.3.6. Discovery requires a read-only SNMP community name,
typically public.

VMware Recommended protocol for discovery of VMware ESX servers and their guests
ESX/ESXi
Uses VMware's vSphere APIs to discover ESX hosts.
The user account can be configured on the ESX host using VMware's Infrastructure or vSphere client. The account must be local to
the ESX server and it must at least have the "read-only" permission. The account does not require shell access to the ESX server.
Discovery of VMware Servers through Virtual Center is currently not supported.
If "Discover Guests" is selected, any VMware guests on the ESX server will also be discovered and polled.

SSH Recommended protocol for discovery of Linux and Unix servers

Supports discovery of Linux and Unix systems using SSH V2 protocol. SSH V1 is not supported.
Discovery of Linux servers requires "root-like" access to several commands, so use of the "root" account or a non-root user with
"root-like" access is recommended. IT Optimize also supports the use of "sudo" to allow root-access to the specific commands.
Discovery of Solaris, HPUX, and AIX is also supported if you deploy a script called "viriditylisthw". Root access is not required on
Solaris and AIX to run the script, but it is required on HPUX. More...
Polling is completed on all Linux and Unix servers using SNMP with a read-only community string. This means the SNMP protocol
must be enabled for Linux/Unix client discoveries.

IPMI Required for discovery of servers to enable power capping. (Communication through UDP port 623. For further information, see the
Intel documentation).

See also

Page 612
 StruxureWare Data Center: IT Optimize security

StruxureWare Data Center Operation: IT Optimize

Configuring StruxureWare Data Center IT Optimize Server Integration

Page 613
Configuring discovery of HPUX Solaris and AIX
Discovery of HP-UX Solaris and AIX requires use of a script during discovery as the current implementation of the SSH interface is not
familiar with those operating systems out of box.

1. On the StruxureWare Data Center IT Optimize server, open the StruxureWare Data Center: IT Optimize installation folder.
Default location: c:\program files\SchneiderElectric\ITOptimize.
2. Open the bin/scripts sub-folder.
In the folder, you see a set of scripts, one for each Unix type (see screenshot).
3. Copy the viriditylisthw.HP-UX script to the /usr/local/bin folder on your target HP-UX client(s).
4. Rename the script once it has been placed in the /usr/local/bin folder to viriditylisthw, removing the .HP-UX
extension.
5. Change permissions on the script to allow execution on the Unix host, i.e. chmod 755 viriditylisthw.
6. Re-run the SSH discovery of the host(s).
The SSH discovery interface will look for that script in /usr/local/bin and will execute it if found.

Note

This script is ONLY used for discovery, not polling.

The viriditylisthw script is a shell script an nothing is hidden.

7. Run the script from the command line.
You should see server information written to the screen in an xml-like format.

The script looks for the HP-UX diagnostic utilities as well. If these tools are not present, some info may not be returned.

scripts folder

See also

Configuring IT Asset Discovery

Page 614
Server Power Consumption Report
A Server Power Consumption report can be generated to identify the servers with the highest average power usage. You can use this
list to evaluate likely server candidates for upgrades, load sharing, or retirement.
The report is available from Analytics>Reports if you have a valid StruxureWare Data Center: IT Optimize license.
A portlet is also available for the StruxureWare Data Center Operation: Dashboard and can be configured to show the server power
consumption data on the StruxureWare Data Center Operation: Dashboard.

Watch this video tutorial to learn how to monitor critical servers using reports.

The filter selections

Data range
The entered average power threshold
Room selection

See also

StruxureWare Data Center Operation: IT Optimize

Working with Reports
Server Utilization Report
Underutilized Servers Report

Page 615
Server Utilization Report
A Server Utilization report can be generated to identify performance indicators on power cost, server utilization and retirement
candidates.
The report is available from Analytics>Reports if you have a valid StruxureWare Data Center: IT Optimize license.
You can also right-click a rack in the layout and select to generate a daily, weekly, or monthly Server Utilization report.

A portlet is also available for the StruxureWare Data Center Operation: Dashboard and can be configured to show the server utilization
data on the StruxureWare Data Center Operation: Dashboard.

The report will include data based on

The filter selections

Date range
Asset selection

See also

StruxureWare Data Center Operation: IT Optimize

Working with Reports
Server Power Consumption Report
Underutilized Servers Report

Page 616
Underutilized Servers Report
An Underutilized Servers report can be generated to identify non-utilized and underutilized servers in the data center.
The report is available from Analytics>Reports if you have a valid StruxureWare Data Center: IT Optimize license.
A portlet is also available for the StruxureWare Data Center Operation: Dashboard and can be configured to show the server utilization
data on the StruxureWare Data Center Operation: Dashboard.

The report will include data based on

The filter selections

Time period
Peak and average utilization thresholds
Rooms
Tags

Watch this video tutorial to learn how to find and manage underutilized servers.

See also

StruxureWare Data Center Operation: IT Optimize

Working with Reports
Server Utilization Report
Underutilized Servers Report

Page 617
StruxureWare Data Center Operation: IT Power Control
StruxureWare Data Center: IT Power Control is powered by Intel(R) Data Center Management and provides insight into the IT layer of
the data center and allows you to manage power consumption through power capping.

The data retrieval is handled by the StruxureWare Data Center: IT Power Control module and supported through a variety of protocols,
such as IPMI or SSH. For further information about Intel(R) Data Center Management, see the documentation provided by Intel.

StruxureWare Data Center: IT Power Control is an add-on module to StruxureWare Data Center: IT Optimize and you must have a valid
StruxureWare Data Center: IT Optimize license to use it.

Configuration
You can configure the StruxureWare Data Center: IT Power Control server communication in System Setup>External System
Configuration.

Monitoring
When the server communication and device discovery has been configured, the device data, including power and temperature data
appears in the list of discovered devices in Planning>Device Association.
To open the Discovered Devices pane, select Window>Show View>Discovered Devices.
If the relevant columns do not show in the table for the discovered devices, click this icon above the pane and select to show the power
and temperature columns.

Servers appear in the list of Server Discoveries.

It is also possible to see Historical power data for devices discovered with the IT Power Control module. Those can be found in power
properties of the device that has been associated with a IT Power Control discovered device.

Power capping
Power capping allows you to limit how much power your IT equipment can use and helps you free UPS capacity.

The manufacturer's nameplate and adjusted nameplate values for servers are higher than the actual measured power consumption.
Power capping allows you to use some of this stranded capacity without tripping the breakers.

When you cap the power consumption of a server or a group of servers, you set a fixed limit that the server will not exceed, regardless of
its current workload. The cap has no effect until the server reaches its power consumption limit. At that point, a management processor
adjusts CPU performance states and clock throttling to limit the power consumption and prevent the breakers from tripping.

You can configure different levels of power capping depending on how much capacity you want to free and how critical the servers are to
the operation of your data center.
For example, you can set the power cap low for servers running non-time critical operations. You will free a lot of capacity but the
servers will run slower.

IT Power Control is installed with IT Optimize and you must have licenses for both to enable power capping in StruxureWare Data
Center Operation.

Page 618
Configuring power capping
It is not recommended to set the power capping value too low as it will affect performance and possibly prevent applications from
running on the capped servers.

Use the selected strategy preview, showing the effect and performance impact before you apply power capping.

Follow the below steps or watch this video tutorial.

Prerequisite: You have configured UPS, PDU, racks and IT equipment and set up power paths. You have configured ITO server
integration and discovered devices.

1. Right-click on a rack and select Configure Power Capping.

2. Choose between the power capping strategies or enter a custom cap value.

Tip

Tip: Click the info icons next to the options for information about the way the system calculates the cap values.
See the power capping effects and graphics to preview the selected cap level before applying it.

Typically, these options are sufficient. However, there is also an advanced configuration section in which you can select to enable or
disable capping on specific servers and set the criticality level.

You can disable capping on mission critical servers altogether to avoid performance impact (clear the Cap check box) and define which
servers will be affected first by the cap limit. Servers with low criticality will be affected first, critical servers last.

When you have configured power capping, a green P icon in the rack layout indicates that the rack or server is managed by a power
capping strategy.

Page 619
—

Configuration

Configuring IT Power Control

Configuring IT Asset Discovery
Configuring external system integration

Reports

Server Power Consumption Report

Server Utilization Report
Underutilized Servers Report

Page 620
Configuring IT Power Control
Configure user credentials to allow StruxureWare Data Center Operation to communicate with Intel® DCM and receive power and
temperature data.

For information about supported devices, see the Intel documentation here.

1. Set up the server connection in StruxureWare Data Center Operation.

a. Select System Setup>External System Configuration.
b. Click Add server, and select StruxureWare Data Center: IT Optimize as the server type.
c. Type the server identification, such as name, IP, port, and credentials and set up the polling interval.
2. Click Test to test the connection before closing the dialog box.
3. In Planning>Device Association, right-click the server or servers in ITO Discoveries (in 7.3.5, Server Discoveries).
a. Specify the server IP range monitored by Intel® DCM that will be scanned when StruxureWare Data Center Operation r
uns a discovery for devices.
b. Select the protocol used for the communication and credentials, if needed.

See also

StruxureWare Data Center Operation: IT Optimize

Configuring external system integration

Page 621
StruxureWare Data Center Operation: Server Access
StruxureWare Data Center: Server Access is an add-on module to StruxureWare Data Center Operation that provides a software KVM
solution. It allows you to control servers from multiple vendors remotely from StruxureWare Data Center Operation, whether they are
turned on or off, without the need for additional hardware or cabling. Both in-band (e.g. remote desktop or SSH) and out-of-band
management (e.g. through a BMC) is supported.

This module is available from version 7.3.5 and requires a valid StruxureWare Data Center: Server Access license. If you exceed the
license count, the server access functionality will be disabled altogether until your license covers all devices.
Contact your local sales representative or visit the Data Center Software website for information about purchasing additional licenses.

Follow the below instructions or watch this video tutorial to learn how to install and configure the server, discover devices in StruxureWar
e Data Center Operation, and access servers remotely, whether they are turned on or off.

1. Installing the StruxureWare Data Center Server Access Server

2. Configuring the Server Access Module
a. Configuring the server connection
b. Controlling user rights
3. Using the Server Access module
a. Associating discovered devices
b. Enabling server access and configuring properties
c. Accessing servers and power cycling
d. Toggling server access

See also

Server Access through Various Protocols

Configuring external system integration

Page 622
Configuring the Server Access Module
A system administrator must configure the StruxureWare Data Center Server Access server for discovering servers that can be
accessed remotely and grant users rights to use the server access functionality.

Note

StruxureWare Data Center Server Access server configuration is not needed to enable remote access to the server OS
through RDP, SSH, or VNC.

Configuring the server connection

In System Setup>External Systems Configuration, configure the server connection between StruxureWare Data Center Operation an
d the StruxureWare Data Center Server Access server used to discover servers that can be accessed remotely.

Managing user rights

Users who have been granted the necessary user rights can use the server access functionality.

To grant these rights:

1. Select System Setup>User Rights and Authentication.

2. In the Users tab, select the user you want to grant this right, select Server Access and Power Cycle and save and close.

The functionality is only available if the required license is installed on the server.
For generic information about managing user rights, see here.

Page 623
Installing the StruxureWare Data Center Server Access Server
Prerequisite: You must have a valid license to enable the module.

The StruxureWare Data Center Server Access server is available from the Data Center Operation server's download page. The server is
required for discovering servers that can be accessed remotely.

Note

The server download for StruxureWare Data Center: IT Optimize and StruxureWare Data Center: Server Access is identical. If
you already have one of the modules installed when you purchase the other, you do not need to download and install the
server for the other module. The licenses control the exposure of the StruxureWare Data Center: Server Access and/or Struxur
eWare Data Center: IT Optimize functionality in the StruxureWare Data Center Operation client. If you purchase both modules
together, the name of the external system is StruxureWare Data Center: IT Optimize and Server Access.

1. Open a Web browser and type the address of your Data Center Operation server: https://yourservername.
2. On the Data Center Operation server's download page, click Download in the Server Access box and follow the instructions to
download the StruxureWare Data Center Server Access server.

See also

StruxureWare Data Center Operation: Server Access

Configuring the Server Access Module
Using the Server Access module

Page 624
Server Access through Various Protocols

VNC

Linux and OS X

StruxureWare Data Center Operation uses the vnc:// URL to connect. The format is vnc://[<username>[:<password>]]@<network_addre
ss>[:<port>].

Windows

A .vnc file is generated and opened. The format is:

[connection]
host=<network_address>
port=<port>
password=<password>

SSH

Linux

It uses the terminal specified by the TERM environment variable. It executes the terminal with the options -hold and -e <ssh -p <port>
<username>@<>network_adress>.

OS X

StruxureWare Data Center Operation uses the ssh command in Terminal to connect. The format is ssh
<username>@<network_address.

Windows

PuTTY is embedded with the installer for SSH access on Windows.

RDP

Linux

StruxureWare Data Center Operation uses the rdp:// URL to connect. The format is rdp://[<username>]@<network_address>[:<port>].

Windows & OS X

An .rdp configuration file is generated that the system opens with the associated client.

Passwords stored in StruxureWare Data Center Operation do not function on OS X.

OS X users will be prompted for passwords even if a password is stored. This is due to an RDP functionality limitation on OS X.

See also

StruxureWare Data Center Operation: Server Access

Enabling server access and configuring properties

Page 625
Using the Server Access module

Associating discovered devices

1. When the server configuration is in place, open Planning>Device Association in the application bar.
2. Use Multi Associate or drag devices discovered by the StruxureWare Data Center Server Access server from Unassociated
Devices to servers in the rack layout to associate them.

You can find more detailed instructions about associating discovered devices here.

Enabling server access and configuring properties

When the discovered devices have been associated with the servers in the data center model, you can enable server access.

1. Right-click a server in the rack layout, Equipment Browser, Navigation, or Discovered Devices view and select Properties>
Server Access.
2. Select Enable Server Access and select to access through: Remote console, operating system, and whether to enable power
cycle functionality.
Configure the remote console settings to access the server remotely through the management card even if it is
powered off.
This is also known as virtual KVM and this option is available only if the server has a management card (BMC) installed.

See supported devices in the Intel documentation here.

Click Test to verify the connection works and a browser window opens a console.
If you experience issues viewing the page launching the console, this might be due to browser related issues.
Configure the OS settings to access the server OS through any of these protocols: Remote Desktop (RDP) for
Windows, SSH for Linux, or VNC.

Note

This option is available for all servers, even those without a management card, and you do not need an
external system configuration with a StruxureWare Data Center Server Access server and discovered devices
to enable the OS access option.
If you leave the logon credentials blank, the user will be prompted for credentials when connecting.

Select the power controls to enable power cycling the server.

This option is available only if the server has a management card (BMC) installed.

Page 626
Accessing servers and power cycling
When a device has been associated with a server and access has been enabled, a small icon appears on the server in the rack layout to
illustrate server access is available. If enabled, Server Access information will appear in the tool tip, informing you if access is enabled
and what the last status was, for example if the server was powered off and when.

1. Right-click a server in the rack layout, Equipment Browser, Navigation, or Discovered Devices view and select Server
Access.
2. Select one or more sub menu items.
Select Remote Console to access the server through a remote console.
This option is available only if the server has a management card (BMC) installed. It allows you to view, configure, and
control the server through this console regardless of vendor (HP, IBM, Dell, Fujitsu, Lenovo, Sun, etc.).
If you experience issues viewing the page launching the console, this might be due to browser related issues.
In the console window, press F2 before the server boots up to monitor and configure BIOS settings directly
from StruxureWare Data Center Operation to troubleshoot hardware problems preventing the server from
booting normally, for example disable a bad memory block or check the memory settings.
Select Remote Desktop, SSH, or VNC to access the server through another protocol, if configured.
You can access the server and install new applications, perform Windows updates, and other maintenance tasks. The
server does not need to be discovered for these options to be available.
Select the power controls to power cycle the server whether it is powered on or off.
This option is available only if the server has a management card (BMC) installed.
Select Off - Soft to send a normal shutdown message to the server OS.
Select Off - Hard to perform a hard shutdown, corresponding to physically pulling the plug.
Select On to reboot the server.

Tip

You can open a remote connection to the server next to StruxureWare Data Center Operation to monitor the power cycle
process live.

Page 627
Toggling server access
You can toggle server access to a server in the Equipment Browser, toggling the Server Access Enabled column to yes/no. This can
be useful, for example if you need to disable server access temporarily for maintenance purposes. The system remembers the settings
when you re-enable server access.

See also

Server Access through Various Protocols

StruxureWare Data Center Operation: Server Access
Installing the StruxureWare Data Center Server Access Server
Configuring the Server Access Module

Page 628
StruxureWare Data Center Operation: Cooling Optimize
Data Center Operation: Cooling Optimize continuously optimizes airflow in the data center facility, delivering improved reliability and
availability.

Cooling Optimize is a closed-loop system that reacts to real-time data from the temperature sensors. Data is wirelessly transmitted to
network gateways, aggregated, and sent to a purpose-built appliance where it is analyzed by control software. Control commands are
then delivered to the cooling equipment. As IT load changes, the built-in machine learning automatically adjusts cooling output to match
the dynamic data center environment.

You can use it to automatically identify and eliminate hot spots and to help diagnose potential facility risks. The system constantly adapts
cooling through the use of its artificial intelligence engine.

Watch this video tutorial to learn about overcooling and how to configure the Cooling Optimize integration.

Cooling Optimize Influence Map

Installation
Installing Data Center Operation: Cooling Optimize is part of a service deal. Please contact your local sales representative.

Configuration
You can configure the Data Center Operation: Cooling Optimize Integration in System Setup>External System Configuration.

Associate discovered assets

You can associate a discovered asset with the temperature sensor or CRAC unit representing it in the data center layout by dragging it
from the Unassociated Devices pane on top of the corresponding equipment in the rack layout. You can also associate multiple assets
by using the multi-associate option.

Configuration

Configuring Cooling Optimize Integration

Configuring the Cooling Optimize Web Client

Reports

Cooling Optimize Benchmark Report

Temperature Compliance Report

Page 629
Configuring Cooling Optimize Integration
Configure user credentials to allow Data Center Operation: Cooling Optimize to communicate with Vigilent and receive cooling and
temperature data.

1. Go to System Setup > External System Configuration.

a. Click Add

and select Data Center Operation: Cooling Optimize as system type.

b. Type the server identification, such as name, IP, port, and add the API Token.
The API Token is used to ensure secure communication with the Cooling Optimize server. The API Token can be
created in the Cooling Optimize CX tool by a user with administrator rights.
Info: If you are unable to launch Cooling Optimize verify that a dco user exists on the Cooling Optimize server.
2. Click Test to verify the connection.
3. Verify the polling interval.
Proxy should only be selected if the Cooling Optimize Server is on another network and the user must use the Data Center
Operationserver as proxy since there is no direct access to the Cooling Optimize server.
4. Associate the devices found in Planning > Device Association > Cooling Optimize to the servers and CRAC units
representing them in the floor layout.
5. Verify that the data has been associated to servers and CRAC units

Page 630
Page 631
 If you are unable to launch Cooling Optimize verify that a dco user exists on the Cooling Optimize server.

See also

Configuring the Cooling Optimize Web Client

Associating Live Data from an External System to the Layout
Room overlays

Page 632
Configuring the Cooling Optimize Web Client
In the Cooling Optimize web client you can edit the temperature set points used for cooling control and turn the cooling units on and off.
Because of this, you need user rights to be able to launch to the Cooling Optimize web client. Go to System Setup > User Rights and
Authentication > Launch to Cooling Optimize > Save and close .

To launch the web client go to the right-click menu of any Cooling Optimize item and select Launch to Cooling Optimize.

In the Set Points tab you can view and change the temperature set points of your racks.

The Equipment tab shows the state of the equipment, e.g.: cooling rate, power usage, and origin of on/off control. This is where you can
manually override units in the facility and where you can turn your cooling units on and off.

For more information go to the help icon

in the top right corner of the web client.

See also

Configuring Cooling Optimize Integration

Page 633
Cooling Optimize Benchmark Report
A benchmark report can be created to compare the energy usage for a before and after time period. The report can be generated for
each room and for the site total.

Power savings are quantified via power monitoring on the controlled cooling units.
Calculated chiller power is included in the savings values for chilled water units.
Greenhouse gas reductions are calculated based on the following default conversion rates: 1.32 lbs./kWh and 0.59 kG/kWh.

The report is available from Analytics > Reports if you have a valid Data Center Operation: Cooling Optimize license.

The filter selections:

Baseline time period

Verification time period
Cost per kWh
Currency
Chiller coefficient of performance (COP)

Tip

Create a report filter with your baseline measurements. That way they are easy to retrieve.

See also

Working with Reports

Temperature Compliance Report

Page 634
Temperature Compliance Report
A Temperature Compliance report can be generated to show the average temperature for a rack, room(s) or location for a specific date
range. It also identifies which racks are preforming outside of their threshold range. The report is available from Analytics>Reports if
you have a valid Data Center Operation: Cooling Optimize license.

Report filter options:

Data range
Temperature thresholds
Tag selection

Note: The temperature distribution tables on page two are based on the individual rack upper and lower threshold set in the Set Points
tab in the vx-tool.

Info

The report will also include middle sensors, if you have them in your setup.

See also

Working with Reports

Cooling Optimize Benchmark Report

Page 635
StruxureWare Data Center Operation Cooling Optimize system requirements

Version compatibility

Recommended minimum Vigilent version to configure integration with Data Center Operation: Cooling Optimize.

DCO Vigilent

7.5 Vigilent® System 6.5.1r06

7.4.5 Vigilent CX 6.5.0a06

Page 636
Troubleshooting
Troubleshooting incorrect power values
Resolving error collecting data
Troubleshooting inaccurate 3D calculations
Protocols and Modules used for IT related features
Correcting False Power Values Reported by StruxureWare Data Center Expert 7.2.6
Troubleshooting issues saving large solutions in Lab
Troubleshooting installation
Troubleshooting DCO client out-of-memory error
Power tool tip troubleshooting
Troubleshooting Performance Issues
Troubleshooting operational problems
Troubleshooting scan problems
Troubleshooting connection and synchronization problems
Troubleshooting logon problems
Troubleshooting why Capture Index values do not display

Page 637
Downloading log files for troubleshooting
If you get a critical error message, search for the error message in the documentation and community. If you do not find instructions for
solving this particular issue, you can ask a question in the community.

The log files can be helpful when troubleshooting why the error occurred. Collecting the files may take a few minutes.

Troubleshooting

1. Take a screenshot of the application and error message.

2. If the error occurred in the DCO desktop client, write down the installation details (version, build, and serial number). You can
access this information in the application Help>About StruxureWare Data Center Operation.
3. Write down (in steps) what you were doing before the message appeared.
4. Download the relevant log files as described below.
5. Post a question in the community or send this information to technical support, including:
a. Error description
b. Description of what you were doing when the message appeared
c. Pasting relevant lines from the log files (Caution: Do not share confidential information in the community!)
6. If the community does not help you solve your issue, contact technical support. However, ensure you include the full log archive
downloaded from Webmin for quicker, more efficient assistance.

Downloading server log files

You can collect server log files from the Webclient Download log Files Page (Administration > Download log Files).

Downloading desktop client log files

You can collect client log files from

The desktop client menu Help>Download client log files

The StruxureWare Data Center Operation installation folder, default location:
Windows: C:\Users\[Username]\.isxo\[Version]\Operations\application.log
OS X and Linux: ~/.isxo/[Version]/Operations/application.log

Downloading cluster log files

In a clustered environment, log on to one of the nodes and get the log files through Webmin as described here. You will get log files from
both servers.

Downloading Disaster Recovery log files

Note that if your setup includes a Disaster Recovery node, you must download the log files separately through the Webmin interface on
that server.

Downloading ITO log files

ITO log files are included with the DCO server log files. Alternatively, you can download them separately from the ITO:

1. In a browser, go to https://<ito-server-ip>:8090/.
2. Logon as the server user.
Don't remember the credentials?
3. Select System settings.
4. In the pop-up dialog box, Support tab, click Download...
5. Save the support.zip file containing the console log files.

Downloading StruxureWare Data Center Operation: Lab log files

Page 638
Resolving error collecting data
The Error collecting data message typically occurs if StruxureWare Data Center Operation is unable to receive data from StruxureWar
e Data Center Expert. There could be several reasons for the server response to be cut off. Start by ruling out the listed scenarios.

Why do I see this error? How do I resolve this?

Network infrastructure between the two servers. Ping the servers to ensure they are running and check your
Changes to DCE user credentials or update of the network path to rule out general network related issues.
SSL certificate. Test the DCO/DCE server connection (in DCO select System
Setup>External Systems Configuration. Perform the test for both
port 80 and 443 (use encryption).

Don't change the DCE server ID (IP/hostname) as part of the test

because this will result in all device associations being lost.

The DCE server may be under too much stress and Reboot the DCE server to re-initiate the jobs.
unable to run the necessary background jobs. If the server is stressed because it is monitoring too many devices,
The StruxureWare Data Center Expert server may be consider additional purchases.
unable to handle requests from the StruxureWare
Data Center Operation server.

If the connection was lost or interrupted, DCO will collect any data it missed when the connection has been restored.

See also

Troubleshooting
Troubleshooting Error Messages
Troubleshooting incorrect power values

Page 639
Correcting False Power Values Reported by StruxureWare Data Center Expert 7.2.6
Some rack-mount PDUs reporting power bank information to StruxureWare Data Center Expert7.2.6 report wrong power data to Struxur
eWare Data Center Operation.

Known affected devices: AP8970, AP8888, AP8886, AP8881, AP8870, AP8862, AP8860, AP8853, AP8841, AP8832J, AP8831, AP865
3, AP8632, AP8481, AP8441, AP7960, AP7853 ...

You will be able to see if your rack-mount PDUs are reporting incorrectly to DCO if you see a significant difference in a rack-mount
PDU's total peak and average values per phase in DCO compared with DCE. This can be done by running a power sensor report of the
device(s) in DCE for a time period of 30 days. This report will also show the average and peak values in the bottom table. These
numbers can then be compared with the power data seen in the device properties in DCO.

This patch fixing the issue applies to DCE 7.2.6+:

DCE version DCO version Fix includes

7.2.6 and later Prior to 7.5 Power (kW)

7.2.6 and later 7.5 and later Power (kW), Current (amps)

How do I know if my rack-mount PDUs might be reporting wrong power data to DCO?

1. Click View Device Sensors on your device (rack-mount PDU) in DCE (e.g. AP8841).
2. Look for Power - Bank 1 and Power - Bank 2.
3. If the device has more than one power bank, it could be reporting wrong power data to DCO.

How do I apply the patch in DCE?

1. Make sure to have a recent backup in place of your running systems before applying the patch.
2. On the DCE server, open this URL: http://<DCE server ip>/nbc/status/SensorContexts.
You must be logged in as an admin user.
a. If you already have a previous version of this patch installed (prior to March 2016), remove the existing file:
pduSensorUpdates.xml before proceeding.
3. Download this file and upload it to the DCE server.
The file has now been uploaded to the server and the patch is in place.

Tip

WARNING: Uploading a malformed or corrupted file can totally mess up the system.

The power values are now correctly transferred.

You can erase the false power data history and see the corrected values immediately* by deleting the external system (DCE) in DCO an
d adding it again. You will need to associate devices again in DCO.

*Once the data has been gathered from DCE. It might take up to 1 day depending of number of devices.

An alternative is waiting. Depending on the configuration in StruxureWare Data Center Operation (30 days by default), all the values will
be corrected after the configured time period (30 days by default). In general, power data is stored for a year for report purposes so for
reports, the data will take longer for the data to be fully corrected.

Page 640
Troubleshooting Performance Issues
On this page:

Slow server/client connection

Scaling client memory allocation for large solutions
3D showing only white surface
Advanced server debugging

Slow server/client connection

If the connection between the StruxureWare Data Center Operation server and client is slow, add an exception in the connection options
for the StruxureWare Data Center Operation IP address.

The StruxureWare Data Center Operation 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.

1. In Internet Explorer, select Tools>Internet Options.

2. Select the Connections tab.
3. Click LAN settings.
4. In Proxy server, select Use a proxy server for your LAN.
5. Click Advanced.
6. In Exceptions, add your exceptions separated by semi-colon.

Scaling client memory allocation for large solutions

Working with large solutions/rooms with many racks/assets, the client might run out of memory (java heap space error).
To increase the amount of assets that can be loaded at the same time in the client, you can modify the configuration ini file.

1. Browse to C:\Program Files (x86)\<Operation version, e.g. StruxureWare Data Center Operation
7.5>\application
2. Open the StruxureWare Data Center Operation.ini file in a text editor, such as Notepad++.
3. Edit the line
-Xmx768M corresponding to an average of 1200 racks to
-Xmx1500M which should double the memory (2400 racks)

There is an upper limit to how much memory could be allocated with the -Xmx parameter and in some cases, you will not be able to
launch the client. In that case, decrease the value again.

3D showing only white surface

If switching to 3D mode only shows a white surface and the client log file shows the following ERROR,

Page 641
 2014-12-11 10:06:32,190 ERROR
[com.apc.threedengine.eclipse.internal.lwjgl.LWJGLAWTCanvasEx] (AWT-EventQueue-0)
Unhandled exception occurred, skipping paint()
org.lwjgl.LWJGLException: Failed to find ARB pixel format 1 0

at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at
org.lwjgl.opengl.WindowsAWTGLCanvasPeerInfo.doLockAndInitHandle(WindowsAWTGLCanvasPeer
Info.java:61)
at org.lwjgl.opengl.PeerInfo.lockAndGetHandle(PeerInfo.java:85)
at org.lwjgl.opengl.AWTGLCanvas.paint(AWTGLCanvas.java:320)
at sun.awt.RepaintArea.paintComponent(Unknown Source)
at sun.awt.RepaintArea.paint(Unknown Source)
at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$400(Unknown Source)
at java.awt.EventQueue$2.run(Unknown Source)
at java.awt.EventQueue$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

you can adjust your Windows client PC settings as illustrated in the screenshot, using the control panel.

Advanced server debugging

If you experience serious performance issues on the Data Center Operation server, you may be asked to open the server debugging
page in Webmin.

Page 642
This page includes advanced information about the health of the server to help troubleshoot the issues.
When you use the StruxureWare DC Operation>Download Log Files option, the system includes the data from the Debug page in the
log. But first, you must open the Debug page.

1. Log on to Webmin using the user credentials created during the installation.
2. In the left menu, select StruxureWare DC Operation>Debug.
3. Click Show to generate memory graphs and debug data that can be used when troubleshooting together with our support team.

If you are running a cluster setup, you must generate the debug data on all nodes.

See also

System requirements

Page 643
Troubleshooting incorrect power values
If you are experiencing that power values in DCO don't match your expectations, the reasons can be many. Use this list of typical
scenarios to see if your issues can be resolved in a similar way.

Measured values in DCE and DCO don't match

Comparing measured data in DCE and DCO is like comparing apples and oranges. DCE is used for monitoring real-time values. DCO is
used for planning. DCO uses average values and KPI data collected over a period of time as real-time values are not as useful on its
own for planning.

Therefore, when looking at measured data in DCO, you are looking at the measured peak average over a specified period of time
(default latest 30 days) rather than the measured load as displayed in DCE.

DCO is not recommendable for real-time monitoring. For this, you should use DCE.

Specific rack PDUs don't report correct power measurements

In previous versions, some rack PDUs reporting power bank information to DCE report wrong power data to DCO. A patch fixes this.

See more here: Correcting False Power Values Reported by StruxureWare Data Center Expert 7.2.6

Deleted equipment continues to affect the average value

Removing equipment from a rack may result in less accurate values for a while. It can take several days for the capacity calculations to
stabilize.

See more here: How Removing a Server Affects Power Values

Measurements from unsupported devices are not included

If your DCO doesn't show the expected measurements from all your devices, it could because getting the measurements from some of
the devices is not supported. Contact [email protected] for requesting new device support (customized or new DDF files).

The capacity overview isn't updating

The data is updated on a daily basis by default. If, for some reason, the data isn't recorded, for example because the server was turned
off, you can re-enable recording in Tools>Preferences>Capacity History by clicking Record Now.

See also

Resolving error collecting data

Monitoring operations in Map View

Correcting False Power Values Reported by StruxureWare Data Center Expert 7.2.6

Page 644
Protocols and Modules used for IT related features
This page will show a brief overview of the features found in the DCO client and which IT related modules will provide data using which
protocols for these features. A number of the modules and integrations require license. Licenses are not covered in this page, see here.

The data provided by the protocols might vary a bit depending on system providing data. The protocols are not all needed in order to get
data for the specific features but can be used together or individually.

Server CPU Utilization

Feature Discovery Protocol External System / Integration Tooltip information

- CPU Utilization (graph) WMI IT Optimize

SNMP - SSH
VMware Discovery
HP OneView
HP OneView

- Average Power (bar-graph) Cisco UCS Cisco UCS Manager

I PMI
WMI IT Optimize
SNMP - SSH
VMware Discovery HP OneView
HP OneView
ETL ETL

Server Power Utilization

Feature Discovery Protocol External System / Integration Tooltip information

- Historical Power (graph) HP OneView HP OneView

IPMI
WMI IT Optimize
SNMP - SSH
VMware Discovery

- Average Power (bar-graph) Cisco UCS Cisco UCS Manager

IPMI
WMI IT Optimize
SNMP - SSH
VMware Discovery HP OneView
HP OneView
ETL ETL

Server Temperature
Feature Discovery Protocol External System / Integration Tooltip information

- Inlet Temperature (graph) IPMI (only 3D temperature sensors) IT Optimize

HP OneView
ETL (only 3D temperature sensors) HP OneView

ETL

Server Access
Feature Discovery Protocol External System / Integration Tooltip information

Remote Console IPMI discovery (vendor specific BMC access) IT Server Access
HP OneView
HP OneView

Operating System Remote Desktop IT Server Access

VNC
SSH HP OneView
HP OneView

Power On/Off IPMI discovery (vendor specific BMC controls) IT Server Access
HP OneView
HP Oneview

Page 645
Troubleshooting installation
You install the DCO server from a preconfigured installation media (DVD, USB key), or out-of-band management (OOM) interface. After
following the steps in the installation wizard for the server installation, you can log in to the web client and from your profile menu, you
can select to download and install one or more desktop clients.

Having issues configuring the installation media?

Consult the instructions here or search the documentation and community.

Having issues during the server installation?

The DCO 8.0 disk image comes bundled with CentOS 7.0. During the DCO server installation process, you're looking at the graphical
interface provided by CentOS. Press F4 to switch to text terminal to follow the progress of the installation in detail, or track any errors
during the installation.

Page 646
Troubleshooting DCO client out-of-memory error
If you run into an out-of-memory error in the DCO desktop client running on 32 bit Windows, you can try to resolve the issue by adjusting
memory parameters in the StruxureWare Data Center Operation.ini file in the installation folder.

java.lang.OutOfMemoryError: Java heap space

If this is the wording of the error, raise the -Xmx value.

java.lang.OutOfMemoryError: unable to create new native thread

If this is the wording of the error, lower the -Xmx value (e.g. 700M). This will give more room for creating new threads.

You can also try to lower the -Xss value (to e.g. 160k) since that will make each thread use less memory.

Note

Don't specify an -Xms value unless there is a really good reason for it. If it is not specified, the JVM will allocate heap space in
steps instead of all in one go which helps the JVM adjust memory use between heap and thread memory.

There is a third type of memory used by the Java code (PerGen). You should not change the PerGen setting.

Page 647
Advanced use
The DCIM Developer Documentation provides more advanced StruxureWare documentation for developers and advanced users with
highly technical skills.

Warning

Using the advanced documentation requires that you have fundamental or advanced experience in certain areas, such as
command line interface, database configuration, certain tools, etc.

No technical support is provided for this content through EcoStruxure IT Help Center, Engineering, or Technical Support.

Web services
StruxureWare Data Center Operation REST Web Service API

Transition from SOAP to RESTful web service API

Advanced server configuration

About advanced Server Configuration

ETL

About ETL - Extract Transform Load

Setting Up an ETL Configuration
ETL Database Configuration

StruxureWare Data Center Operation Insight

About StruxureWare Data Center Operation Insight

Customizing report designs

Page 648
DCO web service API
The StruxureWare Data Center Operation Web Service API is a set of web services that provide access to various parts of StruxureWa
re Data Center Operation .

The RESTful web service documentation is available:

On your StruxureWare Data Center Operation server: https://<server-IP>/api/current.

Use the system administration credentials you use when logging into StruxureWare Data Center Operation.
Accessing the API documentation on your StruxureWare Data Center Operation allows you to easily test the endpoints.

On the web: http://sxwhelpcenter.ecostruxureit.com/DCOAPIdoc/.

You can access the same documentation on help.se-dmaas.com using this link without the need to log in to your StruxureWare
Data Center Operation server, however, without the possibility of easily testing the endpoints as when you access /api/current
on your server.

Introduction to RESTful API

The SOAP web services (deprecated) are documented here.

Page 649
About migration
Migration is used for moving existing data to and from the Data Center Operation server. Situations in which migration could be used
include:

Moving existing data from Emerson Aperture

Moving existing data from different solutions into one (merging)
It is important to note that solutions must be from different setups, eg. solutions must not be originated from the same
instance/installation.
When you migrate more rooms from different solutions into one using the backup process in Webmin together with the Migrate
option in DCO, you do not risk overwriting rooms with other rooms as they will be appended. Do not use the backup/restore
process in Webmin for moving data into an existing solution as this will wipe all data.

Page 650
Recommended reading
Read the white papers in the Schneider Electric white paper library produced by Schneider Electric's Data Center Science Center.

Click the titles to open the papers directly in pdf format.

Estimating a Data Center's Electrical Carbon Footprint (WP-66)

Data center total carbon profile
The impact of power generation
How data center energy use relates to carbon emissions
Tools for estimation of electrical carbon footprint

Comparing UPS System Design Configurations (WP-75)

Scale, availability, and cost
Capacity or "N" system
Isolated redundant
Parallel redundant or "N+1"
Distributed redundant
System plus system redundant
Choosing the right configuration

How Data Center Infrastructure Management Software Improves Planning and Cuts Operational
Costs (WP-107)
Planning: Effect/Impact
Operations: Completing more tasks in less time
Analysis: Identifying operational strengths and weaknesses

Virtualization and Cloud Computing: Optimized Power, Cooling, and Management Maximizes
Benefits (WP-118)
The rise of high density
Reduced IT load can affect PUE
Dynamic IT loads
Lowered redundancy requirements

Guidelines for Specification of Data Center Power Density (WP-120)

The various density specification methods
Deployment strategies
The model

Power and Cooling Capacity Management for Data Centers (WP-150)

Capacity supply and demand
System-level capacities
Managing capacity
Monitoring power and cooling for IT devices

Allocating Data Center Energy Costs and Carbon to IT Users (WP-161)

Measuring vs. modeling
How many points do we need to measure
Allocating energy to IT users
Translating energy into carbon
Providing guidance to IT users

Avoiding Common Pitfalls of Evaluating and Implementing DCIM Solutions (WP 170)
Pitfall 1: Choosing an inappropriate solution
Pitfall 2: Relying on inadequate or mismatched processes
Pitfall 3: Lack of commitment, ownership, and knowledge

Page 651
Considerations for Owning versus Outsourcing Data Center Physical Infrastructure (WP 171)
Approaches to supporting new IT capacity
Cost analysis
Cash flow
Strategic Factors

Power and Cooling Guidelines for Deploying IT in Colocation Data Centers (WP 173)
Causes of stranded capacity in colocation data centers
Best practices promoted by an effective acceptable use policy
Other recommended best practices
Attributes of an effective acceptable use policy (AUP)

Page 652
Support

EcoStruxure IT Help Center site

Use the EcoStruxure IT Help Center site to find the information you need to make the most of your software applications and share
information with the Community.

Community: Meet other users and share issues and ideas.

Documentation: Access the latest user assistance on our applications, and read release news and other product information.
Contact: Contact support for help on finding a solution to your particular problem or concern.

For additional assistance or if the above resources do not answer your questions, please feel free to contact us. The Customer Care
Center will work with you to find a tailored solution to your particular problem or concern. To locate the telephone number for the support
you need, visit Contact Us.

Tip

Before contacting support, search the documentation and community to see if you can find the answer to your question.

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 Data Center Operation

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

Page 653
Glossary
Here’s a high-level overview of terminology and key concepts used when referring to DCIM and StruxureWare Data Center Operation.

Block
A block in the room layout represents a section over which cables and cooling lines cannot be routed (such as a support column).

Breaker Panel
In the breaker panel you can add breakers with an exact definition of position and capacity available. This enables you to map out and
track power connections within the PDU and to reduce stranded capacity. When correctly configured the breaker panel provides an easy
overview of available circuits, breakers, and phases.

Capture Index (CI)

Unit of measure for 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.

Cluster
When used in connection with cluster environment, cluster is used as follows:

A computer cluster is a group of linked computers, 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. 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.

Source: Wikipedia. Wikimedia Foundation, Inc. 5 May 2011

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.

Cubic Feet per Minute (CFM)

Unit of measurement used to measure the airflow of a cooling unit.

Data Set
This term is used in StruxureWare Data Center Operation: Insight. 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 StruxureWare Data Center Operation are
available in StruxureWare Data Center Operation: Insight.

Data Source
This term is used in StruxureWare Data Center Operation: Insight. A data source is used for connecting to the database to get the
requested data.

Design Limit for racks and rack PDUs

You can set a design limit on a rack or rack PDU. This concept replaces the capacity group concept in previous versions (7.5 and
earlier).

For a rack PDU, the specified limit is distributed on the connected phases. For example, a design limit of 6 kW on a three phase rack
PDU will give a design limit of 2 kW for each phase.
For a rack, the specified limit is based on the total load in the rack. That means there is no phase distribution and it could be possible to
utilize the entire rack design limit on one phase, for example L1.

Distribution Redundancy

Page 654
A type of redundancy setup in which the power distribution, not the power source, is redundant, using multiple 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.

Estimated Downstream Load

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.

Failover Load
In a redundancy setup the additional load on a power feed in case the other power feed is turned off. For example, if an A-Feed UPS
was turned off, the B-Feed UPS has to carry the full load, and so should the Rack PDU breakers, etc. This is calculated based on
measured values.

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

Genome
The Genome Library is a database extended with thousands of additional measured server power profiles, storage and switch
specifications. This continuously growing asset library enables StruxureWare Data Center Operation to determine power consumption
without hardware sensors.
This is a read-only library of available products you can select from and add to the customizable list of Genomes to use in your data
center infrastructure.

High Availability
High Availability enables you to run in a clustered environment with multiple servers for improved performance. You must have a Cluster
node for high availability and disaster recovery license for each node in a cluster setup. The Cluster node for high availability and
disaster recovery license is also needed for disaster recovery configurations.

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.

Local Mode
When using the StruxureWare Data Center Operation: Mobile, 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 StruxureW
are Data Center Operation client application until it is synchronized. The StruxureWare Data Center Operation: Mobile will also receive
changes made by other users when synchronized.

Measured Average Load

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.

Nameplate
The nameplate value is used by the system in case no power measurements are available. It is the specified worst case power draw.
When you can get the actual power draw, use this data instead of the much higher nameplate value.

Manufacturer's nameplate
The guaranteed value the manufacturer specifies that the product will never exceed.
This value is used by the system if more precise values or measurements are not available.

Adjusted nameplate
Adjusted nameplate < Manufacturer's nameplate

You can reduce the manufacturer's nameplate value to the adjusted value when you know the actual power consumption of the product
and to allow the system to perform more precise calculations.

If the system does not have access to power measurements through system integration but you have measured values in some other

Page 655
way, you can select Use manually entered measurements in the equipment's Power Distribution properties and type the value. This
will override the nameplate value and provide even more precise calculations.

Network Communication Endpoint

Equipment that is not network gear as such, rather equipment that is connected to a network, such as a server or PDU.

Network Gear, Layer 1, 2, 3

Network equipment such as 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.

Network Redistribution Point

Network gear, such as routers and switches.

Node
When used in connection with licenses, such as the StruxureWare Data Center Operation: Capacity 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.

Partial loading
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.

Phase Balancing
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.

Physical Power Limit or Total Capacity

The total capacity is based on the breaker or the capacity of the connected UPS.

Plenum
A pocket of space used for air distribution below a raised floor or above a suspended ceiling.

Power Capping
Power capping is a method to get the most out of the available capacity in your data center. When you cap the power consumption of a
server or a group of servers, you set a fixed limit that the server will not exceed, regardless of its current workload. The cap has no effect
until the server reaches its power consumption limit. At that point, a management processor adjusts CPU performance states and clock
throttling to limit the power consumption and prevent the breakers from tripping.

Power Feed
This term is used in connection with a redundant configuration where one UPS is referred to A feed and the other as B feed.

Power Supply Unit Uncertainty

Power Supply Unit (PSU) Uncertainty indicates a risk in the power supply path that the indicated load could be moved from one phase to
another.

Predicted Power
Predicted power is a capacity strategy defining how estimated load is calculated. The calculations run in the background and affect

Page 656
capacity values all over the DCO interface, such as impact and failover load.

It shows power calculations based on measured peak data from DCE or other external system integration. The default implementation of
30 days trending and fixed min and max values can be customized.

This concept was introduced in DCO 8.0 and replaces previous implementations in which predictions were based on estimations.

Redundancy
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.
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.
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).
Distributed Redundant UPS systems: Three or more UPS where one serves as backup for the others in case one of them fails.
There are 3 types of design and you can learn more here.

*In this case, distribution redundancy is referring to rack PDU redundancy, not UPS level redundancy.

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

Reserved for Distribution Redundancy

In a setup with distribution redundancy (redundancy at the PDU or rack PDU level) and load connected to a mix of phases, it is
necessary to reserve additional capacity in the shared part of the power path. This reservation is referred to as Reserved for Distribution
Redundancy.

Remaining Physical Capacity

The Remaining Physical Capacity value is limited by any upstream limitations, such as the remaining capacity of the UPS or on the
input breaker of the PDU.

For Rack PDUs, the Remaining Capacity is limited by the design limits.

Remaining Redundant Capacity

The remaining capacity in a rack. It is shown in the rack tooltip as either Remaining Single Capacity or Remaining Redundant
Capacity depending on what is detected for the rack.

Remaining Single Capacity

The remaining capacity in a rack. It is shown in the rack tooltip as either Remaining Single Capacity or Remaining Redundant
Capacity depending on what is detected for the rack.

Server Mode
When using the StruxureWare Data Center Operation: Mobile, 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 StruxureWare Data Center

Page 657
Operation client application as well. Any changes made by other users will also be instantly reflected in the StruxureWare Data Center
Operation: Mobile.

Stranded Capacity
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.

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.

Temperature Map
A color map showing the temperature in different parts of a room. The temperature map is 3-dimensional with movable planes.

Temperature Plane
The temperature plane is a movable plane (vertically and horizontally) that shows a color-coded cross section of the temperature in the
room.

Tenant
A customer of a colocation center. See Tenant Portal.

Tenant Portal
A StruxureWare Data Center Operation for Colo web application in which colocators can share customer specific DCIM information with
their customers, the tenants.

Total Capacity or Physical Power Limit

The total capacity is based on the breaker or the capacity of the connected UPS.

Velocity Plane
The velocity plane is a movable plane (vertically and horizontally) that shows a color-coded cross section of the airflow vectors in the
room.

Wizard
A wizard leads you through dialog steps.

Work Order
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.

Page 658