Professional Documents
Culture Documents
Uaswo71 191216 1310 59355
Uaswo71 191216 1310 59355
7
7
7
7
7
7
7
7
8
8
8
8
8
9
9
10
10
10
11
11
11
11
12
12
12
12
13
13
13
13
13
14
14
14
15
15
15
15
16
16
16
16
16
16
17
17
17
17
17
18
18
18
18
19
19
19
20
20
21
21
21
21
22
22
22
22
23
23
23
23
23
23
24
24
24
24
24
24
24
24
24
25
25
25
25
26
26
26
26
27
27
27
27
28
28
28
29
29
29
29
30
30
30
30
31
31
31
31
31
31
31
32
32
32
32
32
33
33
33
33
33
34
34
34
34
34
34
34
35
35
35
35
35
36
36
36
36
37
37
37
37
37
38
38
48
48
48
48
49
49
49
49
49
49
50
50
50
50
50
51
51
51
51
51
51
51
52
52
52
52
52
52
52
52
53
53
53
53
53
54
54
54
54
54
55
55
55
55
56
56
56
56
57
57
57
57
58
58
58
58
59
59
59
59
59
59
60
60
60
60
60
60
61
61
61
61
62
62
62
62
62
63
63
63
63
63
63
63
64
64
64
64
65
65
65
65
65
66
66
66
66
67
67
67
67
67
68
68
68
68
69
69
69
69
69
70
70
70
70
70
71
71
71
71
72
72
72
72
72
73
73
73
73
73
74
74
74
75
75
75
75
75
76
76
76
77
77
77
10.38.1.1 Installing the StruxureWare Operations Dashboard on the StruxureWare Operations server . . . . . . . . . . . . . . . . .
10.38.2 Configuring the initial setup of the StruxureWare Operations - Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.3 Configuring StruxureWare Operations KPI tabs and portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.4 Configuring a tab slide show on the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.5 Configuring the dashboard theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.6 Hiding the cursor on the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.7 Hiding the tool icons on the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.8 Hiding the welcome page on the dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.9 Changing the dashboard administration credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.10 Displaying the configured dashboard on a screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.11 Accessing the StruxureWare Operations - Dashboard from any computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.12 Invoking the sign in page, even if the page was deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.38.13 Troubleshooting StruxureWare Operations - Dashboard issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39 StruxureWare Operations Web Service API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.1 Inventory Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.1.1 Inventory web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.1.2 Inventory By Filter Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.1.2.1 Inventory by filter web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.2 Power Path Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.2.1 Power path web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.3 Custom Properties Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.3.1 Custom properties web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.4 Impact Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.4.1 Impact web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.5 Capacity History Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.5.1 Capacity history web service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.39.6 Tutorial - Accessing web service Java API using CXF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.40 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.40.1 Troubleshooting error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.40.2 Troubleshooting performance issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.41 Video Tutorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.42 White Papers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.43 Write to us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.44 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.45 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
78
78
79
79
79
79
79
79
79
79
80
80
80
80
80
81
81
82
82
82
82
83
83
83
83
84
84
84
84
84
84
85
85
85
87
Attachment Library
This is the library of attachments in this space to keep them in one place and allow for reuse by linking to this page from multiple pages. Any
changes to an attachment used in multiple pages only need to be done here.
Branding
The following are registered trademarks of Schneider Electric, Inc., in the United States and other countries. {multi-excerpt:name=ISXC}
StruxureWare Central {multi-excerpt} {multi-excerpt:name=ISXCb} StruxureWare Central {multi-excerpt} {multi-excerpt:name=ISX} InfraStruxure
{multi-excerpt} {multi-excerpt:name=ISXb} InfraStruxure {multi-excerpt} {multi-excerpt:name=ISXCOLD} InfraStruxure Central {multi-excerpt}
{multi-excerpt:name=ISXOOLD} InfraStruxure Operations {multi-excerpt} {multi-excerpt:name=ISXCHMOLD} InfraStruxure Change {multi-excerpt}
{multi-excerpt:name=ISXMOLD} InfraStruxure Mobile {multi-excerpt} {multi-excerpt:name=ISXCPMOLD} InfraStruxure Capacity {multi-excerpt}
{multi-excerpt:name=ISXEEOLD} InfraStruxure Energy Efficiency {multi-excerpt} {multi-excerpt:name=ISXTLOLD} InfraStruxure Data Center Lab
{multi-excerpt} {multi-excerpt:name=ISXEEOLD} InfraStruxure Energy Efficiency {multi-excerpt} {multi-excerpt:name=ISXOPROOLD}
InfraStruxure Operations PRO Pack {multi-excerpt} {multi-excerpt:name=ISXO} StruxureWare Operations {multi-excerpt}
{multi-excerpt:name=ISXOb} StruxureWare Operations {multi-excerpt} {multi-excerpt:name=ISXCPM} StruxureWare Operations: Capacity
{multi-excerpt} {multi-excerpt:name=ISXCPMb} StruxureWare Operations: Capacity {multi-excerpt} {multi-excerpt:name=ISXCHM} StruxureWare
Operations: Change {multi-excerpt} {multi-excerpt:name=ISXCHMb} StruxureWare Operations: Change {multi-excerpt}
{multi-excerpt:name=ISXM} StruxureWare Operations: Mobile {multi-excerpt} {multi-excerpt:name=ISXMb} StruxureWare Operations: Mobile
{multi-excerpt} {multi-excerpt:name=ISXEE} StruxureWare Operations: Energy Efficiency {multi-excerpt} {multi-excerpt:name=ISXEEb}
StruxureWare Operations: Energy Efficiency {multi-excerpt} {multi-excerpt:name=ISXEC} StruxureWare Operations: Energy Cost {multi-excerpt}
{multi-excerpt:name=ISXECb} StruxureWare Operations: Energy Cost {multi-excerpt} {multi-excerpt:name=ISXD} InfraStruxure Designer
{multi-excerpt} {multi-excerpt:name=ISXDb} InfraStruxure Designer {multi-excerpt} {multi-excerpt:name=nonISX} non-InfraStruxure {multi-excerpt}
{multi-excerpt:name=nonISXb} non-InfraStruxure {multi-excerpt} {multi-excerpt:name=ISXCp} (StruxureWare Central) {multi-excerpt}
{multi-excerpt:name=ISXTL} StruxureWare Operations: Lab {multi-excerpt} {multi-excerpt:name=ISXOPRO} StruxureWare Operations: PRO Pack
{multi-excerpt} {multi-excerpt:name=ISXOPROb} StruxureWare Operations: PRO Pack {multi-excerpt} {multi-excerpt:name=ISXOPROAgent}
StruxureWare Operations: PRO Pack Agent {multi-excerpt} {multi-excerpt:name=ISXOPROAgentb} StruxureWare Operations: PRO Pack Agent
{multi-excerpt} {multi-excerpt:name=DCI} StruxureWare Operations: Insight {multi-excerpt} {multi-excerpt:name=StrW} StruxureWare
{multi-excerpt} {multi-excerpt:name=ISXOserver} StruxureWare Operations {multi-excerpt} {multi-excerpt:name=Vizor} StruxureWare Operations:
VIZOR {multi-excerpt} {multi-excerpt:name=Dashboard} StruxureWare Operations: Dashboard {multi-excerpt}
Download the PDF version of the User Assistance for StruxureWare Operations 7.1 here.
Installation Guide
{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Download the PDF version of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 7.1 Installation Guide [here|^StruxureWare Operations 7.1 Installation
Guide.pdf]. {panel} {section} {panel} Click the individual pages in the list to view them online.
{contentbylabel:label=installation|space=@self|showSpace=false|showLabels=false|maxResults=10000|sort=title}{panel} {section}
User's Guide
{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Sorry, the pdf version is currently not available. {panel} {section} {panel} Click the
individual pages in the list to view them online. {contentbylabel:labels=usage
quickstart|showLabels=false|showSpace=false|max=10000|spaces=@self|sort=title}{panel} {section}
Troubleshooting Guide
{panel:title=Download|borderStyle=solid|borderColor=#009530|titleBGColor=#009530|bgColor=#ffffff} !PDF version of the User Assistance for
StruxureWare Operations 7.1^PDF_icon.gif!{anchor:pdf} Download the PDF version of the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} 7.1 Troubleshooting Guide [here|^StruxureWare Operations 7.1
Troubleshooting Guide.pdf]. {panel} {section} {panel} Click the individual pages in the list to view them
online.{contentbylabel:label=troubleshooting|space=@self|showSpace=false|showLabels=false|maxResults=10000|sort=title}{panel} {section}
available}New Work Order List and Project Code portlets are available for the
{multi-excerpt-include:pageTitle=Branding|name=Dashboard|nopanel=true}. In the generic Data Center KPI portlet, you can add and combine
work order data: total, completed, overdue, not started, in progress. !portlet_WOList.png|thumbnail!!portlet_ProjectCode.png|thumbnail!
{expand_plain} h2. {expand_plain:Change Management: Work order cleanup}Over time, the amount of old work orders in the system will grow.
You can now perform a cleanup and delete work orders older than 400 days, that is work orders with a Needed by date of minimum 400 days
prior to today's date. Use this operation with caution. Once performed, there is no way of retrieving deleted work orders. [More...|Deleting old work
orders] !Deleting old work orders^wo_cleanup.png|thumbnail! {expand_plain} h2. {expand_plain:New master product catalog introduces a new
flow to adding equipment} You can open the master catalog and drag and drop equipment directly into your custom catalog and rearrange
products without the need to open a separate dialog box. You can right-click the custom catalog to add, rename, or delete categories and to copy
or delete products. Multiple users can apply changes to the catalog at the same time. The new master catalog includes new products, such as
windows, doors, and grilles. [More...|Working with the Catalog] !master_catalog.png|thumbnail! {expand_plain} h2. {expand_plain:Support for
windows and doors}Windows and doors are now available in the catalog and allow you to create a more precise model of the data center, making
it easier to navigate the room. !doors_windows.png|thumbnail! {expand_plain} h2. {expand_plain:Cooling: Support for grilles}Grilles are now
available in the catalog and allow you to configure ventilation through grilles. !verticalgrille.png|thumbnail! {expand_plain} h2.
{expand_plain:Branch Circuit Monitoring, mapping of multiple device sensors}Now you can associate multiple device sensors to one component
in the layout using drag-and-drop. [More...|Branch Circuit Monitoring] !Branch Circuit Monitoring^props_powerdistr_highlighted.png|thumbnail!
{expand_plain} h2. {expand_plain:Aperture Import}A new software service is available to support migration from Emerson Aperture. If enabled,
migration from Aperture can be executed through a configuration wizard in *System Setup>External System Configuration*.
!ApertureMigration.png|thumbnail! {expand_plain}
System requirements
The following requirements are based on preliminary test results. They are subject to change. h2. Minimum Server Requirements
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} Suite requires an additional server. It can be installed on dedicated
hardware or in a virtual environment. No operating system installation is required as it is included in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} installation. * Memory: 16 GB RAM * CPU: Multicore is preferred. More
CPU is only beneficial if multiple (5+) clients are accessing the server constantly. * Storage: 40 GB storage The setup has been tested
successfully on the following makes and models: ** HP DL380 ** Dell PowerEdge R710 ** Dell Blade PowerEdge M610 h2. Minimum Client
Requirements * Processor: 2 GHz Intel Core 2 Duo (or equivalent) * Hard disk: 500 MB free hard disk space for installation * Memory: 4 GB RAM
* Display: 1024x768 screen resolution with 16 million colors * Operating System: MS Windows XP Service Pack 2, MS Windows Vista, Windows
7, 32-bit recommended, Linux (mainly tested on Ubuntu) * Browser: Internet Explorer (v7 and up), Chrome, and Firefox You must have local
administration rights on the client computer. h2. Proxy settings for {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} The
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client uses the proxy settings from the operating system. If you are running
on Windows, you can configure the settings through the Internet Explorer connection options. h2. Server communication *Client/server
communication across a firewall requires specific port configuration:* If it is required that the client and server communicate across a firewall, you
must ensure the firewall allows for communication on the following ports: * Port 80: (TCP) - HTTP * Port 443: (TCP) - HTTP using SSL * Port
4457: (TCP) - JMS binding port * Port 4459: (TCP) - JMS binding port using SSL * Port 4460: (TCP) - JMS control port * Port 4462: (TCP) - JMS
control port using SSL Communication across a NAT firewall is not supported. *External communication between
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and external systems:* Here are some default port configurations for
external communication (outgoing). You can use different ports if required. * Ports 443 and 80: (TCP) - VMWare, SCOM, and
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} integration * Port 25: (TCP) - SMTP communication to e-mail server * Port
53: (TCP/UDP) - DNS communication to DNS server * Port 111: (TCP) - NFS mount * Port 123: (UDP) - NTP communication to NTP server * Port
139: (TCP/UDP)- SMB communication to NAS/SAN * Port 445: (TCP) - CIFS communication to NAS/SAN * Port 2049: (UDP) - NFS
communication to NAS/SAN *Communication in a cluster environment:* If you configured a
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} cluster environment, remember to open the port configured in the cluster
setup. *Communication between {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and Webmin:* Port configuration for
communication with the browser-based server administration module. * Port 10000 (TCP) || See also || [Installing StruxureWare Operations]
[Troubleshooting performance issues]
the virtual router ID. In order to create the common entry point to the cluster, a router is emulated through VRRP (Virtual Router Redundancy
Protocol) with that IP. This virtual router has an ID at it must be unique within the space of virtual routers configured on the network. # Wait for
JBoss to start up before continuing to the next node. The installation has finished when the word Started appears. You can monitor the web page
by typing the IP address of the node in a Web browser. Once the web page displays, the server has finished starting up. If you do not have Web
access, you can also monitor the node in this way: Type: service operations open-server-log and press Shift+F, and then Ctrl+C followed by Q to
stop executing the service operations command. Remember to configure [system time synchronization|Configuring system time synchronization
(NTP)]. h2. Configuring the additional nodes: Prerequisite: You have followed the above steps. # When the cursor reaches the login prompt, enter
{{root/apc}}. To change the password, see [here|Enhancing security on the StruxureWare Operations server#changeroot]. # In the Cluster
preconfiguration menu, select 3. # Enter the virtual IP address of the first node that was set up in the cluster. # Enter the root credentials for the
primary node. # Enter a unique ID of this node. (See explanation above.) # Wait for JBoss to start up on one node before continuing to the next
node. The installation has finished when the word Started appears. You can monitor the web page of the individual node by typing the IP address
of the node in a Web browser followed by :8080. Once the web page displays, the server has finished starting up. If you do not have Web access,
you can also monitor the nodes in this way: Type: service operations open-server-log and press Shift+F, and then Ctrl+C followed by Q to stop
executing the service operations command. When a following node is started, its database could be corrupt or "dirty". This means that it is
detached from the cluster, and that write operations will not be committed to this database. To remedy this, attach the database to the cluster.
You must do this on a node in OK state. To attach a database to a cluster: # Type the command {{service operations attach-db-node}}. The
command will display a list of the databases in the cluster and their state. The new database might be in a detached state. # Select the detached
database and press Enter. This will synchronize the new database with the database(s) already in the cluster. To attach the database through the
Webmin interface: In *System>StruxureWare Operations* *Status* tab, select the detached PostgreSQL Database and click *Attach DB*. Read
more [here|Managing StruxureWare Operations services]. {tip:icon=false}*Note*: This operation will block the cluster while synchronizing, which
may result in some warnings in the server log (about connections being destroyed). This is expected and should not cause any concern.{tip} If all
nodes are in OK state, click Ctrl+C to stop execution of the attach command. The cluster environment has now been set up and you can continue
to install the licenses. You can start running the application immediately for a trial period of 30 days after which you need to activate the real
licenses. Remember to configure [system time synchronization|Configuring system time synchronization (NTP)]. || See also || [Managing system
licenses] [Running StruxureWare Operations in a cluster environment|Running StruxureWare Operations in a cluster environment] [Configuring
system time synchronization (NTP)|Configuring system time synchronization (NTP)] [Migrating data to a StruxureWare Operations cluster
environment]
# Update the package cache: Type {{aptitude update}} and press *Enter*. # Install development packages: Type {{aptitude install build-essential
linux-headers-`uname -r`}}.\\ \\ {tip:icon=false}*Tip*: Use back quote ` not ' (Alt+96).{tip} # If prompted to continue, press Y. # Insert a virtual CD in
the virtual machine's drive: Select *Inventory > Virtual Machine > Guest > Install/Upgrade VMware Tools* (in the vSphere Client). The option may
be located in another menu in other VMware products, such as Player or Workstation. # Click *OK* to the *Install VMware Tools* message. #
Mount the CD in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: Type: {{mount /dev/cdrom /mnt/}} and press *Enter*. The
*mount: block device...* message is expected. The VMware Tools on the CD is now available on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. # Extract the VMware Tools from the CD to the server: Type
{{tar xvf /mnt/VMwareTools-\*.tar.gz -C /tmp/}} and press *Enter*. # Run the installer: Type {{/tmp/vmware-tools-distrib/vmware-install.pl}} and
press *Enter*. You will be prompted with questions and instructions. # Press *Enter* to all of these. VMware Tools are now installed on the server.
# Comment all lines in /etc/apt/sources.list again: ## Type {{nano /etc/apt/sources.list}} to open the file and press *Enter*. ## Place the cursor in
front of each line and type #. Press *Ctrl+X* to save and exit. ## Type {{Y}} to the save buffer question and press *Enter*. # Open the *Summary*
tab and verify the line VMware Tools: OK (in the vSphere Client). The option may be available in another place in other VMware products, such as
Player or Workstation.
the *Users* section of the *Users* tab. # To fill out the user information, select *Remote* and the predefined authentication method from the
drop-down list. The name, e-mail address, and password data is supplied by the authentication server. When you are setting up a remote user,
user information is stored on * {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server as a remote repository with user
information. The {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server requires connection setup to the
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} server in order to obtain the user information. * LDAP or Active Directory
server. The {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server requires connection setup to the server and logon
information is required. When a remote user attempts to log on to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true}
server, the user credentials (user name and password) are sent to the authentication server associated with that user. It is that server, and not the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, that authenticates the log on attempt. User groups are not
supported in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and you cannot import user groups from a remote
authentication server. ||See also|| [Setting up the system] [Managing user rights]
{tip:icon=false}*Note*: Enable this option only when using an SMTP server that requires logon access.{tip} When you have configured these
settings, you can set up the system to send automatic notifications on work order changes. || See also || [Setting up automatic e-mail notification
on work order changes|Setting up automatic e-mail notification on work order completion]
You can upload data to the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server in the Webmin server
management interface. # Open the new {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server's Webmin web
interface by typing the address of the {multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server followed by :10000 in a
Web browser, https://yourservername:10000. # Log on to Webmin using the root credentials (default root / apc). To change the password, see
[here|Enhancing security on the StruxureWare Operations server]. # In the left menu, select *System>Upload and Download*. # Select *Upload to
server* and browse to the location of data file (.tar file), and then specify the new location on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server, and select *Upload*. ||See also|| [Upgrading to StruxureWare
Operations 7.1] [Mounting a Windows share]
*Status* tab, monitor if the services are all running. # Select a service and use the buttons to start or stop it. \\ \\ When you have started a service,
wait 5 minutes for the operation to complete. | [Managing server settings] [Installing StruxureWare Operations in a cluster environment] [Migrating
data to a StruxureWare Operations cluster environment] |
layout or by double-clicking a rack in the room or a rack in *Navigation* to see the rack front layout of the selection. If you have
{multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} installed, equipment may appear with *+* or *x* and arrow symbols,
indicating that changes were proposed to the design, but not yet implemented. # Switch to *List View* (available in the toolbar above the layout) to
see the selection in a list. # Switch between the panes in the bottom of the application to see relevant information. For example, browse to see
any equipment listed in the *Equipment Browser*, get an overview of power connection configurations in *Power Dependency*, or any alarms on
associated devices in *Alarms*. \\ \\ {tip:icon=false}*Tip*:To identify which component in the layout is causing an alarm in the *Alarms* pane,
right-click the alarm in the *Alarms* pane and select *Show in Layout* to highlight the component representing the device in the floor or rack
layout.{tip} ||See also|| [Monitoring data center operations in Map View] [Working with the Floor Layout] [Working with the Rack Layout] [Working
with the List View]
Toolbar
{excerpt:hidden=false}The toolbar options depend on what part of the application is active and what add-on modules you have installed. When
you are configuring the room layout in an editor, layout-specific icons are available such as move and add corners
icons.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} !toolbariconsave.gif|align=center!\\ {table-cell} {table-cell:}Saves changes made
without exiting the display. {table-cell} {table-row} {table-row} {table-cell:} !toolbariconundo.gif|align=center!\\ {table-cell} {table-cell:}Undoes the
last action that was performed, regardless of the active perspective. This function is identical to *Edit* *> Undo*.{table-cell} {table-row} {table-row}
{table-cell:} !toolbariconredo.gif|align=center!\\ {table-cell} {table-cell:}Redoes the last action that was undone, regardless of the active perspective.
This function is identical to *> Edit* *> Redo*.{table-cell} {table-row} {table-row} {table-cell:} !icon_cut.png|align=center!\\ {table-cell}
{table-cell:}Cuts the selected item or items. The selection is only marked for being cut and not actually cut away from its position until you paste it
in another position. This function is identical to *> Edit* *> Cut*. {table-cell} {table-row} {table-row} {table-cell:} !icon_paste.png|align=center!\\
{table-cell} {table-cell:}Pastes a selection of one or more items into this position. This function is identical to *> Edit* *> Paste*. {table-cell}
{table-row} {table-row} {table-cell:} !toolbariconeditcatalog.gif|align=center!\\ {table-cell} {table-cell:}Opens the *Master Catalog* from which to
select products for the catalog. {table-cell} {table-row} {table-row} {table-cell:} !tool-generate-row.png|align=center!\\ {table-cell} {table-cell:}Opens
dialog box with options to configure a row layout. {table-cell} {table-row} {table-row} {table-cell:} !tool-select.png|align=center!\\ {table-cell}
{table-cell:}Selects to use the standard cursor while deactivating the corner or floor tile tools. {table-cell} {table-row} {table-row} {table-cell:}
!add-corner.png|align=center!\\ {table-cell} {table-cell:}Allows you to add a corner to a room's outline. {table-cell} {table-row} {table-row} {table-cell:}
!move-corner.png|align=center!\\ {table-cell} {table-cell:}Allows you to move corners and walls to a room's outline. {table-cell} {table-row}
{table-row} {table-cell:} !pan-grid.png|align=center!\\ {table-cell} {table-cell:}Allows you to move the tile grid to match the floor tiles in the layout with
the tile offset that exists at the data center. {table-cell} {table-row} {table-row} {table-cell:} !tool-zoom-in.png|align=center!\\ {table-cell}
{table-cell:}Zooms in on the layout. {table-cell} {table-row} {table-row} {table-cell:} !tool-zoom-out.png|align=center!\\ {table-cell} {table-cell:}Zooms
out on the layout. {table-cell} {table-row} {table-row} {table-cell:} !tool-zoom-fit.png|align=center!\\ {table-cell} {table-cell:}Sets the zoom level to a
size that allows you to see the entire room in the layout. {table-cell} {table-row} {table-row} {table-cell:} !physical-layout.png|align=center!\\
{table-cell} {table-cell:}Opens the *Floor Layout* for managing the floor layout (add, move, delete, or edit) for any room. {table-cell} {table-row}
{table-row} {table-cell:} !icon_manageoverlays.png|align=center!\\ {table-cell} {table-cell:}Selects to enable/disable views in the floor and rack
layouts. {table-cell} {table-row} {table-row} {table-cell:} !rack-layout.png|align=center!\\ {table-cell} {table-cell:}Opens the *Rack Layout* for
managing rack-mountable equipment (add, move, delete, or edit) for any room. {table-cell} {table-row} {table-row} {table-cell:}
!list-view.png|align=center!\\ {table-cell} {table-cell:}Opens the *List View* for managing any room (add, move, delete, or edit) in a table layout.
{table-cell} {table-row} {table-row} {table-cell:} !icon_worldmap.png|align=center!\\ {table-cell} {table-cell:}Opens the *Map View* for viewing a
geographical representation of the data center infrastructure. {table-cell} {table-row} {table-row} {table-cell:} !icon_worldmapup.png|align=center!\\
{table-cell} {table-cell:}Changes the view of the data center infrastructure *Map View* to the location one level up in the location hierarchy.
{table-cell} {table-row} {table-row} {table-cell:} !icon_3D.png|align=center!\\ {table-cell} {table-cell:}Opens the *3D View* for viewing the data center
temperature map in a 3D layout. {table-cell} {table-row} {table-row} {table-cell:} !icon_3Dmanagecontrolpanel.png|align=center!\\ {table-cell}
{table-cell:}Toggles display of the control panel. {table-cell} {table-row} {table-row} {table-cell:} !icon_3Dsavescreenshot.png|align=center!\\
{table-cell} {table-cell:}Opens a save dialog box to save a screenshot of the 3D layout. {table-cell} {table-row} {table} ||See also|| [The look and feel
of the application]
Menus
{excerpt:hidden=false}The active menu bar items vary depending on what part of the application is active. {excerpt} Some menu options are only
available when specific features are enabled. For descriptions of these specific menu options, refer to the topics about those features in the help.
{table:border=1|frame=box|} {table-row} {table-cell} *File* {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF|
bgColor=#FFFFFF} *New > Location*: Creates a new folder in the physical infrastructure hierarchy with the default name highlighted so you can
type another name. *New > Server Room*: Opens the wizard for creating a new server room. *New > Electrical Room*: Opens the wizard for
creating a new electrical room. *New > Store Room*: Opens the wizard for creating a new store room. *New > Supporting Infrastructure Space*:
Opens the wizard for creating a new space for supporting infrastructure elements (for example for chillers on the roof). *Save*: Saves your
changes. *Import > InfraStruxure Designer*: Opens the dialog box in which to browse to an InfraStruxure Designer configuration. Importing an
existing InfraStruxure Designer solution saves you from doing the basic configuration in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. *Import > Insight Report Design*: Opens the dialog box in which to browse
to a custom report design created in {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true} to add the custom report.
[More...|Customizing report designs] *Export > Temperature Map...*: Opens the dialog box in which to export the temperature map to CSV format.
*Export > Plenum Airflows...*: Opens the dialog box in which to export the plenum airflow configuration to CSV format. *Export > CFD PDML
Export...*: Opens the dialog box in which to export the cooling configuration directly to .pdml without the need to use conversion tools. *Export >
CFD XML Export...*: Opens the dialog box in which to export the cooling configuration to .xml. *Export > Layout as Image*: Opens the *Export*
dialog box used to save a bmp or jpg copy of one or more of the server rooms. *Export > Insight Report Design*: Opens the dialog box in which to
select a built-in standard report design from {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} to use it as a template for a
new custom report design in {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. [More...|Customizing report designs] *Restart*:
Restarts the client and the server. For example, you can use this option if you are migrating from multiple
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} servers to restart after each migration. *Exit*: Closes the application.{panel}
{table-cell} {table-row} {table-row} {table-cell} *Edit* {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}
*Undo*: Selects to undo the last action that was performed, regardless of the perspective selected. *Redo*: Selects to redo the last action that
was performed, regardless of the perspective selected. *Cut*: Cuts the selected item or items. The selection is only marked for being cut and not
actually cut away from its position until you paste it in another position. *Paste*: Pastes a selection of one or more items into this position.{panel}
{table-cell} {table-row} {table-row} {table-cell} *Tools* {table-cell} {table-cell}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}
*Open Master Catalog*: Opens the master catalog from which to add, edit or remove available components in the system. [More...|Working with
the Catalog] *Configure Tags*: Opens the Configure Tags dialog box in which to set up tags to categorize types of equipment in the layout
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature). [More...|Creating tags] *Generate Capacity Groups*: Opens
the Generate Capacity Groups dialog box in which to set up capacity planning.
({multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} feature) [More...|Working with capacity groups] *Create new Work
Order*: Opens the *Work Order Editor* and enables the controlled automated work order process. [More...|Working with work orders] *Configure
Work Order Templates*: Opens the *Configure Work Order Templates* dialog box to create templates and manage repetitive tasks.
[More...|Creating and applying work order templates] *Create Work Order Project Codes*: Opens the *Create Project Codes* dialog box to create
work order project codes. These codes will appear in the *Project Code* drop-down list in the *Work Order Editor*. *Preferences*: Opens the
Preferences dialog box.{panel} [More...|Reviewing system preferences] {table-cell} {table-row} {table-row} {table-cell} *System Setup* {table-cell}
{table-cell}*User Rights and Authentication*: Opens the dialog box in which to manage user rights and authentication servers. [More...|Managing
users in the system] *External System Configuration*: Opens the dialog box in which to set up integration to other systems and manage the
server configurations. [More...|Configuring external system integration] *E-mail Settings*: Opens the dialog box in which to set up e-mail
notification functionality. [More...|Configuring e-mail settings] *Migrate from StruxureWare Central*: Opens the dialog box in which to move data
from previous versions to the new stand-alone StruxureWare Operations server. [More...|Migrating data from StruxureWare Central] *System
Licenses*: Opens the dialog box in which to manage licenses. [More...|Managing system licenses] {table-cell} {table-row} {table-row} {table-cell}
*Window* {table-cell} {table-cell} *Restore Default Screen Layout*: Selects to restore any screen parts to their default locations if they have been
moved to new positions. {table-cell} {table-row} {table-row} {table-cell} *Help* {table-cell} {table-cell} *Online Help*: Provides access to the [online
user assistance|User Assistance for StruxureWare Operations 7.1]. *Download Log Files*: Opens a dialog box in which to define a location to
download the system log files to. [More...|Troubleshooting error messages] *Data Center Software Website*: Opens the [Data Center Software
Website|http://www.apc.com/site/software/index.cfm]. *About StruxureWare for Data Centers: Operations Suite*: Opens the dialog box with
copyright and version information for the application. [More...|Troubleshooting error messages] {table-cell} {table-row}{table}
Help menu
{excerpt:hidden=false}Help menu options provide access to the wiki-based user assistance, the [Data Center Software
website|http://www.apc.com/site/software], and copyright and version information for the application. They can be accessed at any
time.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell} *Online Help* {table-cell} {table-cell}Opens the wiki-based user assistance. You
can view the user assistance, and if you register as a user on the wiki, you can use the feedback options to comment on pages or send an e-mail
to the documentation team.{table-cell}{table-row} {table-cell} *Data Center Software Website* {table-cell} {table-cell} Opens the Data Center
Software website where you can read more about the applications and services and get contact information. {table-cell} {table-row} {table-row}
{table-cell} *About {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}* {table-cell} {table-cell}Opens the About dialog box,
which provides copyright and version information for the application. {table-cell} {table-row}{table} ||See also|| [User Assistance for StruxureWare
Operations 7.1]
Navigation
{excerpt:hidden=false}The *Navigation* pane lists the hierarchy of the data center model in a tree structure: Locations, rooms, rows,
floor-mounted equipment placed in the rows, such as racks, and rack-mounted equipment placed in racks. {excerpt} The pane provides a
hierarchical overview of the contents in the data center model placed in locations. It has dynamic search functionality: As you start typing in the
*Search* box, the tree structure shows all equipment that contains the typed characters. You can edit when you have selected *> Planning* *>
Data Center* in the Application bar and build the data center model to reflect the real-world infrastructure by adding new locations (such as
regions, countries, cities) and room items to the hierarchy. * Locations and rooms of different types can be added from *> File* *> New*. * New
rows, floor and rack-mountable components can be added from the *Catalog*. You can move equipment between the different rooms (and
locations) in the *Navigation* pane and *Layout* pane by dragging it. * Rack-mountable equipment can be dragged from any rack in the
*Navigation* pane to a store room, any rack in a selected rack layout, or any rack in the *Navigation* pane. * Floor equipment can be dragged
from any room in the *Navigation* pane to a store room, electrical room or any room shown in the floor layout, or any rack in the *Navigation*
pane. * Rack or floor equipment can be dragged from any room in the *Navigation* pane to any selected store room shown in the *Layout* pane.
You can highlight any listed equipment by right-clicking it and selecting *Show in Editor* to highlight the selected *Navigation* pane device in the
*Layout* pane. Double-clicking a room opens the selected room in the floor layout editor view. If a room is already open in the layout editor,
right-click and select *Open New Editor* to open the selected room in the layout in a separate pane. You can use the right-click menu to access
the most relevant options. For example: * Right-clicking a location allows you to create, rename, and delete locations and rooms. * Right-clicking a
room allows you to open the selected room in a new floor layout editor, copy, paste, rename, and show properties. * Right-clicking an item allows
you to highlight it in the layout (*Show in Editor*), cut, paste, rename, show properties. You can delete equipment by right-clicking it and selecting
*Delete*. {tip:icon=false}*Tip*: You can add, move or delete multiple items at the same time by using Ctrl-click or Shift-click.{tip} ||See also||
[Exploring the infrastructure in map, floor and rack layouts] [The look and feel of the application]
away from its position until you paste it in another position.) {table-cell} {table-row} {table-row} {table-cell:}Ctrl+Z {table-cell} {table-cell:}Undo
{table-cell} {table-row} {table-row} {table-cell:}Ctrl+- {table-cell} {table-cell:}Zoom out {table-cell} {table-row} {table-row} {table-cell:}Ctrl++
{table-cell} {table-cell:}Zoom in {table-cell} {table-row} {table-row} {table-cell:}Shift+Delete {table-cell} {table-cell:}Delete the selection In
*Planning>IT Change*, mark the selection for deletion {table-cell} {table-row} {table-row} {table-cell:}F7 {table-cell} {table-cell:}Open the *Master
Catalog* {table-cell} {table-row}{table}
Support
Software Support Wiki
Access the Software Support Wiki to find the information you need to make the most of your software applications and share information with the
software team and the rest of the support community.
On the support wiki home page, you can access the following:
User Forum: Meet other users and ask questions.
Help Documentation: Access the latest user assistance on our applications, and read release notes and other product information.
Feature Request: Request new features or report a bug.
FAQ: Search the Knowledge Base.
Tip: Make a note of the installation details (version, build, and serial number) and have this information ready when contacting support. You
can access this information in the application Help>About StruxureWare Operations.
If a critical error message occurred, follow these instructions or watch this short video tutorial (2:26) before contacting support.
Inventory report
{section}{column:width=50%}{excerpt:hidden=false}You can generate an Inventory report that lists the contents of the selected item or items in
the application.{excerpt} In addition to being available from *Analytics>Reports*, it can be generated for individual components and racks in
*Operations>Data Center* by right-clicking a component or rack in the layout, and selecting *Asset Inventory*. The generated report displays in
the *Report View*. You can now use the *Report View* toolbar to navigate the report pages on the screen (arrow icons), or to print or export the
report to a file in any of the available formats (Export icon, down arrow for selection of format). {column} {column:width=50%}
!report_inventory.png|thumbnail! {column} {section} ||See also|| [Working with reports]
Editing Properties
{excerpt:hidden=false}Right-click any room, floor equipment (including racks), or rack-mountable equipment in a *Navigation* pane, or *Layout*
pane and select *Properties* to access and edit the properties. {excerpt} # To edit properties for a selected component, right-click it in the
floor/rack *Layout* or *Navigation* pane and select *Properties* and perform the edits in the Properties dialog box. # To edit properties for a
component in the catalog, i.e. all pieces of this equipment added to the floor or rack layout subsequently, open the catalog, select a component in
the *Floor Equipment* or *Rack-Mountable Equipment* pane and perform the edits in the *Properties* section. # To add custom properties,
perform one of the above steps, and in the *Properties (Custom)* section, select *Add*, then in the Add Custom Properties dialog box, type the
name and value for the new property. # To add power connection properties, perform one of the above steps, and in the New Power Connection
dialog box, accessed in the *Power Dependency* (CRAC) or *Power Distribution* (PDU or remote distribution panel (RDP)) section, select *New*
to add a new power connection or *Edit* to edit an existing connection. ||See also|| [Viewing external system data] [Room Properties] [Cooling
Properties] [Custom Properties] [General Properties] [Device Properties] [Mounting Properties] [Network Properties] [New Custom Properties]
[New Power Connection Properties] [Physical Properties] [Power Dependency Properties] [Power Distribution Properties] [Power Properties
(rack)] [Power Properties (rack PDU)] [Power Properties (server, blade server, blade enclosure)] [Power Properties (UPS)] [Pump Properties]
Custom Properties
{excerpt:hidden=false}This section of a Properties dialog box lists custom properties for the selected
component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Name* {table-cell} {table-cell:}Defines the property's name. {table-cell}
{table-row} {table-row} {table-cell:} *Value* {table-cell} {table-cell:}Defines the value the property provides. {table-cell} {table-row} {table}
{tip:icon=false}*Note*: The listed information is defined by add and edit versions of a Custom Properties dialog box that are accessed by the
*Add* and *Edit* buttons; *Delete* allows you to remove any listed custom property.{tip} ||See also|| [Editing Properties]
General Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component, provides relevant information that
identifies the selected component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Name* {table-cell} {table-cell:colspan=2|}A
user-definable value used to identify the component. {table-cell} {table-row} {table-row} {table-cell:} *Location* {table-cell}
{table-cell:colspan=2|}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Identifies the component by type and location. For
example: * *R/A-3/Z2* identifies a rack that is the third from the left in row A, and is included in the power zone identified as Z2. * *E2/Wall*
identifies the second of at least two emergency power off (EPO) buttons located against a wall.{panel} {table-cell} {table-row} {table-row}
{table-cell:} *Barcode* {table-cell} {table-cell:colspan=2|}A user-definable alphanumeric value that identifies the barcode assigned to the
component, if any. {table-cell} {table-row} {table-row} {table-cell:} *Product Information* {table-cell} {table-cell:colspan=2|}Identifies the
*Manufacturer*, *Model name* and *Part Number*, and provides a *Description* of the component. You can edit *Product Information* for a
generic component. {table-cell} {table-row}{table} ||See also|| [Editing Properties]
Device Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an associated device or component with an associated
device, identifies the general and measured data of the device. {excerpt}{table:border=1|frame=box|} {table-row} {table-cell} *Properties*
{table-cell} {table-cell}Identifies device details. {table-cell} {table-row} {table-row} {table-cell} *Power* {table-cell} {table-cell}Reports the measured
load values for the device. {table-cell} {table-row}{table} ||See also|| [Editing Properties]
Mounting Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component, identifies the mounting options of the
component in the rack.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Available mounting Positions* {table-cell}
{table-cell:}Identifies the position of the component in *Front*, *Rear*, *Left Rear*, *Right Rear*, *Not Mounted*, and *Top*. {table-cell}
{table-row}{table} ||See also|| [Editing Properties]
Physical Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component, identifies physical attributes associated
with the component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Position* {table-cell} {table-cell:}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF}Provides information that varies based on the component type: * Floor: Identifies the location of the
component within the Layout pane: *X* identifies its distance from the left side of the pane; *Y* its distance from the top of the pane. *
Rack-mountable: Identifies the rack unit (U) position within its rack. {panel} {table-cell} {table-row} {table-row} {table-cell:} *Weight* {table-cell}
{table-cell:}Identifies how much the component weighs. For racks: *Weight* identifies how much the rack weighs when empty; *Maximum weight*
identifies the maximum weight that is allowed to be added to the rack; *Current weight* is the sum of the rack's weight and the weight of the
equipment added to the rack.{table-cell} {table-row} {table-row} {table-cell:} *Boundary* {table-cell} {table-cell:}Identifies the component's
dimensions (*Width*, *Depth*, and *Height*), and the *Orientation* that component has in relation to the server room's physical layout. {table-cell}
{table-row} {table-row} {table-cell:} *Frame* {table-cell} {table-cell:}Provides information about how many rack units (U) a rack provides
(*U-positions*), how many are still available (*Free U-positions*). {table-cell} {table-row}{table} ||See also|| [Editing Properties]
Pump Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a pump, identifies the selected pump by pump package
type. Pump packages are specified based on desired flow rate and piping losses.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:}
*Chilled Water* {table-cell} {table-cell:colspan=2|}Identifies if the cooling method used is chilled water. The pump is circulating chilled water in a
chilled water cooling system. {table-cell} {table-row} {table-row} {table-cell:} *Heat Rejection* {table-cell} {table-cell:colspan=2|}Identifies if the
cooling method used is heat rejection. The pump is circulating glycol solutions and condenser water to the cooling tower or dry cooler. {table-cell}
{table-row}{table} ||See also|| [Editing Properties]
Room Properties
{excerpt:hidden=false}Relevant properties are displayed for the selected room. They vary based on the type of room.{excerpt} h2.
{expand_plain:Cooling Properties (room)} These properties identify cooling attributes associated with the room as a
whole.{table:border=1|frame=box|} {table-row} {table-cell:} *Raised floor leakage* {table-cell} {table-cell:}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF}Sets the percentage of air leaking through the raised floor. The leakage in a typical data center is
10-50%+. You can adjust the default value (30%) by moving the slider. This value is used by the system to calculate the airflow per perforated tile.
* 0%: Perfectly Sealed * 15%: Tight * 30%: Typical * 45%: Leaky * 60%: Very Leaky {panel} {table-cell} {table-row} {table-row} {table-cell:}
*Temperature* {table-cell} {table-cell:}Indicates the *Supply* temperature for all InRow cooling units in the room. The higher the supply
temperature, the higher Capture Index (CI) values you should design for. Ambient and max inlet temperatures are set to default values.
{table-cell} {table-row}{table} {expand_plain} h2. {expand_plain:Custom Room Properties} This section of the Properties dialog box, accessed by
right-clicking a room in the *Navigation* pane, lists custom properties for the selected room.{table:border=1|frame=box|} {table-row} {table-cell:}
*Name* {table-cell} {table-cell:}Defines the property's name. {table-cell} {table-row} {table-row} {table-cell:} *Value* {table-cell} {table-cell:}Defines
the value the property provides. {table-cell} {table-row} {table} {tip:icon=false}*Note*: The listed information is defined by add and edit versions of
a Custom Properties dialog box that are accessed by the *Add* and *Edit* buttons; *Delete* allows you to remove any listed custom property.{tip}
{expand_plain} h2. {expand_plain:General Room Properties} This section of the Properties dialog box, accessed by right-clicking a room in the
*Navigation* pane, provides relevant information that identifies the selected room.{table:border=1|frame=box|} {table-row} {table-cell:} *Name*
{table-cell} {table-cell:}A user-definable value used to identify the room. {table-cell} {table-row}{table} {expand_plain} h2. {expand_plain:Physical
Room Properties - Ceiling} This section of the Properties dialog box, accessed by right-clicking a room in the *Navigation* pane, identifies
physical attributes associated with the ceiling of the room.{table:border=1|frame=box|} {table-row} {table-cell:} *Ceiling height* {table-cell}
{table-cell:}Defines how much space exists between the floor and ceiling. {table-cell} {table-row} {table-row} {table-cell:} *Drop ceiling* {table-cell}
{table-cell:}Selects to identify that a dropped ceiling exists. {table-cell} {table-row} {table-row} {table-cell:} *Tile size* {table-cell}
{table-cell:}Matches the tile overlay in the *Floor Layout* pane to the tiles at the data center. \\ \\ The default setting may not match the data center
tiles. For example, if you selected to use metric measurements for a server room that uses US standard tiles, change the setting from *600 mm*
to *2 feet*. {table-cell} {table-row} {table-row} {table-cell:} *Drop ceiling height* {table-cell} {table-cell:}Defines how much space exists above the
dropped ceiling, when *Drop ceiling* is selected. {table-cell} {table-row} {table-row} {table-cell:} *The space above the drop ceiling extends beyond
the boundaries of the room* {table-cell} {table-cell:}Selects to identify that the space above the dropped ceiling extends beyond the room's walls,
when *Drop ceiling* is selected. {table-cell} {table-row}{table} {expand_plain} h2. {expand_plain:Physical Room Properties - Floor} This section of
the Properties dialog box, accessed by right-clicking a room in the *Navigation* pane, identifies physical attributes associated with the floor of the
room.{table:border=1|frame=box|} {table-row} {table-cell:} *Raised floor* {table-cell} {table-cell:}Selects to identify that the room has a raised floor.
{table-cell} {table-row} {table-row} {table-cell:} *Floor height* {table-cell} {table-cell:}Defines how much space exists below a raised floor, when
*Raised floor* is selected. {table-cell} {table-row} {table-row} {table-cell:} *Tile size* / *Tiles* (Electrical Room only) {table-cell} {table-cell:}Matches
the tile overlay in the *Floor Layout* pane to the tiles in the room. Electrical rooms have no tiles per default, but this can be selected here. \\ \\ The
default setting may not match the room tiles. For example, if you selected to use metric measurements for a server room that uses US standard
tiles, change the setting from *600 mm* to *2 feet*.{table-cell} {table-row} {table-row} {table-cell:} *Grid layout* {table-cell} {table-cell:}Defines the
distance between the grid lines in the layout. You can select between a fine-grained and coarse-grained layout. The grid lines help you align
equipment in the layout and show the distance between them. You will find it useful to select a fine-grained layout, if you want to align equipment
closer together in the layout using the *Snap to grid* right-click option on equipment, leaving no room for unintended space. {table-cell} {table-row}
{table-row} {table-cell:} *Maximum carrying capacity* {anchor:floorcarryprops} {table-cell} {table-cell:}Defines how much equipment weight the floor
supports, measured in kg/m2. {table-cell} {table-row} {table-row} {table-cell:} *Row Layout* (Electrical Room only) {table-cell} {table-cell:} *None*/
*Automatic*: Allows for adding row layout to the electrical room (default value is *None*). {table-cell} {table-row} {table-row} {table-cell:} *Aisle*
{table-cell} {table-cell:}Defines the width (space between rows) for the hot (*Hot aisle width*) and cold (*Cold aisle width*) aisles, as well as
whether the first (top) row is hot (*First aisle hot* selected) or cold. {table-cell} {table-row}{table} {expand_plain} ||See also|| [Editing Properties]
with raised floor environments in the Plenum view] [Floor Layout Views] [Showing or hiding floor and rack views] [Preferences: Showing or hiding
tool tips|Reviewing system preferences#pref_tooltip] [Preferences: Showing floor dimensions in meters or feet|Reviewing system
preferences#pref_meas] |
space in the rack has been used. * Red: 86-100 % of available space in the rack has been used. At zoom level 90% and above: A color bar is
used to identify how many U-positions are available in the each rack. The amount of Total, Used, and Free U-positions are displayed next to the
bar. At zoom level 89% and below: The racks are colored, and numbers indicate the amount of free U-positions. {panel} {table-cell}
{table-row}{table} ||See also|| [Working with the Floor Layout]
Configuring cooling
{section}{column:width=50%}{excerpt:hidden=false}The application gives you a fail/pass indication of the effectiveness of the active cooling
configuration. As the design takes place, you get a qualified estimation of the effect of changes in supply temperature, airflow, and number of
cooling units and room-based cooling parameters.{excerpt} h2. Cooling The *Cooling* view of the data center floor layout shows a color-coded
overview of the Capture Index. You can use this view to get an overview of the reasons why the tile airflow may not be the same across the room.
Each rack in a well-formed hot aisle / cold aisle layout shows a color-coded capture index (CI) percentage. The CI value identifies inlet air which is
supplied by what fraction of the equipment's exhaust airflow is captured by the InRow cooling units included in that row pair or by the CRAC or
CRACs in the room through the perforated tiles. {column} {column:width=50%} !coolingview.png|thumbnail! {column} {section}
{section}{column:width=50%} h2. 2D Plenum airflow Subsequently, you can use the *Plenum* view to drill down into looking at specific velocity
issues in the plenum and estimate perforated tile airflow rates. When you drag in a new cooling unit or move a perforated tile, the flow vectors and
perforated tile flow rates update instantly. {column} {column:width=50%} !plenum_view.jpg|thumbnail! {column} {section}
{section}{column:width=50%} h2. Airflow in 3D In the *3D* view, you can see the room's airflow above the raised floor. Velocity vector and
temperature results look like those from traditional CFD applications and provide the same ability to quickly locate problem spots and understand
the underlying causes. You can have multiple rooms open in the 3D view at a time. When you have opened a room in 3D view or applied changes
to the configuration, click *Start* to regenerate the calculations and show the updated view. Subsequently, you can select *File>Export* and
export to .xml or export directly to .pdml without using conversion tools. {column} {column:width=50%} !3D.png|thumbnail! {column} {section} ||See
also|| [Performing cooling simulation in the Cooling view] [Working with raised floor environments in the Plenum view] [Working with the
temperature map in the 3D view] [Cooling configuration accuracy and design guidelines]
{table-cell}*Cooler type* {table-cell} {table-cell}*Minimum CFM* {table-cell} {table-cell}*Maximum CFM* {table-cell} {table-row} {table-row}
{table-cell}InRow RC (300 mm) {table-cell} {table-cell}1450 {table-cell} {table-cell}2900 {table-cell} {table-row} {table-row} {table-cell}InRow RC
(600 mm) {table-cell} {table-cell}2760 {table-cell} {table-cell}6900 {table-cell} {table-row} {table-row} {table-cell}InRow RP (600 mm Chilled Water)
{table-cell} {table-cell}2760 {table-cell} {table-cell}6900 {table-cell} {table-row} {table-row} {table-cell}InRow RP (600 mm Air Cooled) {table-cell}
{table-cell}1920 {table-cell} {table-cell}4800 {table-cell} {table-row} {table-row} {table-cell}InRow RD (600 mm Air Cooled) {table-cell}
{table-cell}2000 {table-cell} {table-cell}5000 {table-cell} {table-row} {table-row} {table-cell}InRow RD (300 mm Air Cooled) {table-cell}
{table-cell}916 {table-cell} {table-cell}2300 {table-cell} {table-row} {table-row} {table-cell}InRow RD (300 mm Fluid Cooled) {table-cell} {table-cell}
916 {table-cell} {table-cell}2300 {table-cell} {table-row}{table} * Rack airflow is by default assumed to be 160 CFM/kW based on the total rack
power. This value can be changed by right-clicking a rack and selecting *Properties*, to change to, for example, 105 CFM/kW for blade server
racks. * CRAC airflow is, by default, assumed to be 6000 CFM. This can be changed by right-clicking a CRAC and selecting *Properties*. * UPS
airflow is automatically calculated by the system based on the UPS size and the number of power modules (assumed to be 10kW each). * Airflow
through each tile is calculated as the tiles are positioned in the layout. * Airflow for generic powered equipment is not included in the cooling
calculations by default. This can be changed by right-clicking a piece of generic powered equipment and selecting *Properties*. ||See also||
[Configuring cooling] [Performing cooling simulation in the Cooling view] [About Capture Index prediction models] [About the Capture Index (CI)
colors]
Optimizing the cooling configuration accuracy by adjusting power and cooling estimates
Since {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} uses estimates to calculate the temperatures in the 3D view, you
cannot expect the simulation to be completely accurate. However, you can improve the accuracy of these estimates to fit your particular setup by
providing the system with as much information about the power and cooling in your data center as possible. h2. Server load estimates In
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, every server in the data center has two power estimates. Per default, the
two values are the same. They define the maximum power consumption for a particular server in its maximum configuration. * Manufacturer's
Nameplate: Identifies the nameplate value of the selected server. {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} uses this
value as the reference value. * Estimated Load: Identifies the estimated load of the selected server.
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} uses this value for the calculations. You can lower the Estimated Load for
all servers in the data center if they do not consume all the power specified by the nameplate value. The option is available if you right-click the
server and select *Properties>Power*. h2. Cooling unit airflow estimates The accuracy of the cooling unit airflow is about 85-90% in typical
configurations. However, you can adjust the airflow properties for the cooling units if the default values in the system do not match your specific
setup. The option is available if you right-click the cooling unit and select *Properties>Cooling*. In this way, you can provide the system with the
specific power and cooling values for your data center and improve the accuracy of the configuration. ||See also|| [Cooling configuration accuracy
and design guidelines] [Configuring cooling]
Cooling Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking a component, identifies cooling attributes associated
with the component.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Airflow* {table-cell} {table-cell:}Identifies the maximum cooler
airflow in cubic feet per minute (CFM). {table-cell} {table-row} {table-row} {table-cell:} *Discharge Pattern* {table-cell} {table-cell:}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Identifies the room air distribution system. * Downflow: Warm exhaust air is drawn
in through the top of the unit, cooled, and then cool air is distributed back into the room through a raised floor plenum. These systems are ideal for
areas with raised floors greater than 305 mm (12 in) high. * Upflow: Warm exhaust air is drawn in through the front of the unit. The warm exhaust
air is then cooled and discharged back into the room through a plenum or ductwork. These systems are ideal for areas without a raised floor, but
can also be used in a raised floor environment. {panel} {table-cell} {table-row} {table-row} {table-cell:} *Include in cooling calculation* {table-cell}
{table-cell:}Defines if the airflow from this equipment is to be included in the cooling calculations. You can set this for generic powered equipment.
{table-cell} {table-row}{table} ||See also|| [Editing Properties]
layout pane) to highlight the best position in the rack layout for a selected piece of equipment you want to add from the *Catalog* or move from
*Navigation* or *Layout*. To effectively identify the best location for the selected equipment using this feature, ensure the system is set up
correctly, including the appropriate rack PDUs, UPS and PDUs, power paths, and capacity groups. When you use the *Add Equipment* to *Best
rack* option, the system recommends the best position based on your setup: available space, cooling and power. This could be information about
supported voltage, redundancy, capacity group and tag associations, remaining power outlets, load balancing on the different phases, weight and
available network ports. In addition, color-coded messages in the *Placement Status* pane guide you in finding the optimum location for the
selected equipment.{column}{column:width=50%}!Enabling placement recommendations^placementadvisor.jpg|thumbnail!{column}{section} ||See
also|| [Enabling placement recommendations] [Finding the best location for a new server] [Setting up a capacity plan] [Capacity Planning Example] [Best Rack Advisor - Redundancy configuration]
options to ensure that the network is connected logically.{table:border=1|frame=box|} {table-row:align=center} {table-cell:}*Notation* {table-cell}
{table-cell:colspan=2|}*Description* {table-cell} {table-row} {table-row} {table-cell:} > {table-cell} {table-cell:colspan=2|}{panel: borderStyle=none|
borderColor=#FFFFFF| bgColor=#FFFFFF} * Network gear in this rack{panel} {table-cell} {table-row} {table-row} {table-cell:} -> {table-cell}
{table-cell:colspan=2|}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} * Racks in this room and/or all rooms {panel}
{table-cell} {table-row} {table-row} {table-cell:} : {table-cell} {table-cell:colspan=2|}{panel: borderStyle=none| borderColor=#FFFFFF|
bgColor=#FFFFFF} * Port specification{panel} {table-cell} {table-row} {table-row} {table-cell:} / {table-cell} {table-cell:colspan=2|}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF} * Location separator (room/row/rack){panel} {table-cell} {table-row}{table} ||See
also|| [Configuring network routes|Managing network configurations]
Network Properties
{excerpt:hidden=false}This section of the *Properties* dialog box, accessed by right-clicking a piece of network equipment, identifies network
attributes associated with it. The information may vary based on the type of equipment.{excerpt}{table:border=1|frame=box|} {table-row}
{table-cell:colspan=3|} *Network ports* {table-cell} {table-row} {table-row} {table-cell:} *Type* {table-cell} {table-cell:colspan=2|}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Provides information about the type of network port. The available options include
pairs of a regular port and an uplink port. * The regular port is selected for the piece of equipment that makes network available to other pieces of
equipment, such as a switch. * The uplink port is selected for the piece of equipment that requires network access. {panel} {table-cell} {table-row}
{table-row} {table-cell:} *Description* {table-cell} {table-cell:colspan=2|}Provides user-defined information. {table-cell} {table-row} {table-row}
{table-cell:} *Start* {table-cell} {table-cell:colspan=2|}Identifies the first port in the port range. {table-cell} {table-row} {table-row} {table-cell:} *Count*
{table-cell} {table-cell:colspan=2|}Identifies the amount of ports in the port range. {table-cell} {table-row} {table-row} {table-cell:} *Speed*
{table-cell} {table-cell:colspan=2|}Provides information about the network speed. {table-cell} {table-row} {table-row} {table-cell:colspan=3|}
*Connections* (available if the dialog box is accessed by right-clicking a component in the rack layout that has routes defined) {table-cell}
{table-row} {table-row} {table-cell:} *Port* {table-cell} {table-cell:colspan=2|}Identifies the port number. {table-cell} {table-row} {table-row}
{table-cell:} *Type* {table-cell} {table-cell:colspan=2|}Identifies the port type. {table-cell} {table-row} {table-row} {table-cell:} *Connected to*
{table-cell} {table-cell:colspan=2|}Identifies the network route between the start and end items. {table-cell} {table-row} {table-row} {table-cell:}
*Description* {table-cell} {table-cell:colspan=2|}Provides user-defined information. {table-cell} {table-row} {table-row} {table-cell:} *IP Address*
{table-cell} {table-cell:colspan=2|}Identifies the IP Address. {table-cell} {table-row} {table} ||See also|| [Editing Properties] [Managing network
configurations]
About peak and average power data retrieval from StruxureWare Central
Devices (for example Rack PDUs) in {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} must provide measured values
through power sensors in Watt. In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, all power measurements are assumed to
be in Watt. {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} includes measured power values from any device, supporting
real power measurements in Watt, regardless of make and model (including 3rd party devices). The power sensor value is assumed to be real
power (as apposed to apparent power VA), but the actual value is defined by the individual device and how
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} retrieves the value (could be done as a calculation in the DDF).\\
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} retrieves the peak power values from
Launching to device
{excerpt:hidden=false}You can access the device web interface directly from the *Launch to Device* right-click option.{excerpt} # Right-click a
device, in the *External Systems* pane, for example, and select *Launch to Device*. An error will occur if the HTTP/HTTPS protocol or port
definitions defined for this device at the external system server do not match the protocol and port definitions required by that device. # If an error
occurs, refer to the external system's documentation for instructions on how to check or set the HTTP/HTTPS settings. ||See also|| [Viewing
external system data] [Configuring external system integration]
identify the exact location of the alarms in the data center model, for example on a specific UPS in the floor layout, and help you identify the
severity of the alarm. Alarm types ||Info||Warning||Error, Critical, and Failure|| | !ImgAlarmInfo.png! | !ImgAlarmWarning.png! |
!ImgAlarmCritical.png! | If enabled in *Tools>Preferences*, the tool tips include information about active alarms in *Rack Layout* (on
rack-mountable equipment) and *Floor Layout* (on equipment in the floor, e.g. UPS). You can view the device with the alarm on the external
system by right-clicking and selecting *Launch to Device*. {column} {column:width=50%} !externalsystem_alarms.png|thumbnail! {column}
{section} ||See also|| [Associating live data from an external system to the layout] [Showing alarms for selected equipment only] [Configuring
external system integration]
Cooling Recommendations
{excerpt:hidden=false}Messages about the cooling configuration may occur in the *Recommendation* pane to guide you as you design the data
center model. Refer to the topics about the individual messages for information about how to optimize the design.{excerpt} ||See also|| [Optimizing
the design by following the recommendations] {contentbylabel:label=recommendation_cooling|space=@self|showSpace=false|showLabels=false}
General Recommendations
{excerpt:hidden=false}Messages about the general configuration may occur in the *Recommendation* pane to guide you as you design the data
center model. Refer to the topics about the individual messages for information about how to optimize the design.{excerpt} ||See also|| [Optimizing
the design by following the recommendations] {contentbylabel:label=recommendation_general|space=@self|showSpace=false|showLabels=false}
The tags assigned to the rack equipment in the rack do not match
{set-metadata:_UImapping_}KeywordMismatchConstraint{set-metadata} h2. Description {excerpt:hidden=false}The tags assigned to the
equipment in the rack must match the tag or tags assigned to the rack.{excerpt} h2. Recommended Action * If the wrong tag was assigned to the
rack or rack-mount equipment: *# Right-click the recommendation message and select *Show in Editor* to identify the rack in the layout. *#
Right-click the rack or rack-mount equipment in the rack and select Properties to access the Properties dialog box for the equipment. *# In the
*tags* section select the tag in question and select *Remove* to remove the tag assignment to this equipment. * If the tag information is correct
but the rack-mount equipment was accidentally placed in the wrong rack with a different tag assignment: *# Right-click the recommendation
message and select *Show in Editor* to identify the rack in the layout. *# Drag and drop the misplaced equipment into the correct rack. ||See
also|| [Optimizing the design by following the recommendations]
License Recommendations
{section}{column:width=50%}{excerpt:hidden=false}Messages about the installed licenses may occur in the *Recommendation* pane to guide you
as you design the data center model. Refer to the topics about the individual messages for information about how to optimize the design.{excerpt}
{column}{column:width=50%} !Optimizing the design by following the recommendations^recommendation.png|thumbnail! {column}{section} ||See
also|| [Managing system licenses] [You are approaching the amount of racks supported by your StruxureWare for Data Centers - Operations Suite
license] [You are approaching the amount of racks supported by your StruxureWare Operations - Capacity license] [You are approaching the
amount of racks supported by your StruxureWare Operations - Change license] [You are exceeding the amount of racks supported by your
StruxureWare for Data Centers - Operations Suite license] [You are exceeding the amount of racks supported by your StruxureWare Operations Capacity license] [You are exceeding the amount of racks supported by your StruxureWare Operations - Change license] [You have reached the
amount of racks supported by your StruxureWare for Data Centers - Operations license] [You have reached the amount of racks supported by
your StruxureWare Operations - Capacity license] [You have reached the amount of racks supported by your StruxureWare Operations - Change
license]
You are approaching the amount of racks supported by your StruxureWare for Data Centers Operations Suite license
{set-metadata:_UImapping_}operationsLicenseWarningCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are
approaching the amount of equipment supported by your license. If you continue adding equipment after you have reached the limit, you will not
be able to save your data center model.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center
Software website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also||
[Optimizing the design by following the recommendations]
You are approaching the amount of racks supported by your StruxureWare Operations - Capacity
license
{set-metadata:_UImapping_}capacityLicenseWarningCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are approaching
the amount of equipment supported by your license. If you continue adding equipment after you have reached the limit, you will not be able to
save your data center model. {excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]
You are approaching the amount of racks supported by your StruxureWare Operations - Change
license
{set-metadata:_UImapping_}changeLicenseWarningCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are approaching
the amount of equipment supported by your license. If you continue adding equipment after you have reached the limit, you will not be able to
save your data center model.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]
You are exceeding the amount of racks supported by your StruxureWare for Data Centers - Operations
Suite license
{set-metadata:_UImapping_}operationsLicenseErrorCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are exceeding the
amount of equipment supported by your license. If you continue adding equipment after you have reached the limit, you will not be able to save
your data center model.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]
You are exceeding the amount of racks supported by your StruxureWare Operations - Capacity license
{set-metadata:_UImapping_}capacityLicenseErrorCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are exceeding the
amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]
You are exceeding the amount of racks supported by your StruxureWare Operations - Change license
{set-metadata:_UImapping_}changeLicenseErrorCountConstraint{set-metadata} h2. Description {excerpt:hidden=false}You are exceeding the
amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]
You have reached the amount of racks supported by your StruxureWare for Data Centers - Operations
license
{set-metadata:_UImapping_}operationsLicenseLimitReachedConstraint{set-metadata} h2. Description {excerpt:hidden=false}You have reached
the amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]
You have reached the amount of racks supported by your StruxureWare Operations - Capacity license
{set-metadata:_UImapping_}capacityLicenseLimitReachedConstraint{set-metadata} h2. Description {excerpt:hidden=false}You have reached the
amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]
You have reached the amount of racks supported by your StruxureWare Operations - Change license
{set-metadata:_UImapping_}changeLicenseLimitReachedConstraint{set-metadata} h2. Description {excerpt:hidden=false}You have reached the
amount of equipment supported by your license. Any equipment added to your data center model after you have exceeded the limit will not be
saved.{excerpt} h2. Recommended Action Contact your local sales representative or visit [the Data Center Software
website|http://www.apc.com/site/software/index.cfm/Contact/] for information about purchasing additional licenses. ||See also|| [Optimizing the
design by following the recommendations]
Power Recommendations
{excerpt:hidden=false}Messages about the power configuration may occur in the *Recommendation* pane to guide you as you design the data
center model. Refer to the topics about the individual messages for information about how to optimize the design.{excerpt} ||See also|| [Amount of
rack PDU power outlets has not been configured] [An invalid power path has been configured] [Associated device data has been lost] [Capacity
group equipment is placed in multiple rooms] [Connection has not been configured between PDU and power supply] [Connection has not been
configured between Power Panel and power supply] [Connection has not been configured between remote distribution panel (RDP) and power
supply] [Equipment connected to this PDU draws more power than is supported by the power supply breaker] [Equipment connected to this
Power Panel draws more power than is supported by the power supply breaker] [Equipment connected to this remote distribution panel (RDP)
draws more power than is supported by the power supply breaker] [Equipment in this rack receives power from multiple power supply devices]
[Equipment is connected to a rack PDU outside this rack] [Internal redundancy setup for UPS and group must match] [PDU and connected rack
PDU are placed in different rooms] [PDU output voltage has not been configured] [Power connection configuration is invalid for equipment in one
or more racks in the group] [Power feed connection for UPS and group must match] [Power Panel output voltage has not been configured]
[Rack's estimated load exceeds group's peak load settings] [Rack does not support the group's peak load settings] [Rack is not included in a
capacity group] [Rack is without rack PDU or a rack PDU is not powered] [Rack's power configuration does not support distribution redundancy]
[The average estimated load of the racks in the group exceeds the group's average load settings] [The breaker configuration does not support
rack's estimated load] [The capacity group supports a higher redundancy than this server requires] [The input voltage setting required by the
equipment is not available in current rack] [The measured load exceeds the estimated load per phase designed for the rack] [The measured load
exceeds the total estimated load configured for the rack] [The measured load of the connected rack PDU is 0, but an estimated load has been
configured for the rack] [The measured load of the UPS exceeds the total estimated load of the connected equipment] [The phase configuration
for the connected server is not supported by the rack PDU] [The Rack PDU output voltage setting does not match the output voltage of the
connected PDU or Power Panel] [The server should not be supplied from different phases on 1 UPS] [The UPS in the layout does not supply
enough power to match the configured load of connected equipment in the layout] [This equipment in store room is connected to equipment in a
room] [This server requires a higher redundancy than is available in the capacity group] [UPS internal redundancy has not been configured] [UPS
power feed has not been configured]
Connection has not been configured between PDU and power supply
{set-metadata:_UImapping_}pduNotConnectedToSupplierConstraint{set-metadata} h2. Description {excerpt:hidden=false}A power connection is
missing in the data center model from this PDU to the power supply from which it should receive power.{excerpt} h2. Recommended Action #
Right-click the PDU and select *Properties* to open its Properties dialog box. # In *Power Dependency* page, select the appropriate *Power
supply*option to connect the PDU to the PDU or UPS from which it should receive power. ||See also|| [Optimizing the design by following the
recommendations]
Connection has not been configured between Power Panel and power supply
{set-metadata:_UImapping_}powerPanelNotConnectedToSupplierConstraint{set-metadata} h2. Description {excerpt:hidden=false}A power
connection is missing in the data center model from this Power Panel to the power supply from which it should receive power.{excerpt} h2.
Recommended Action # Right-click the Power Panel and select *Properties* to open its Properties dialog box. # In *Power Dependency* page,
select the appropriate *Power supply* option to connect the Power Panel to the Power Panel or UPS from which it should receive power. ||See
also|| [Optimizing the design by following the recommendations]
Connection has not been configured between remote distribution panel (RDP) and power supply
{set-metadata:_UImapping_}rdpNotConnectedToSupplierConstraint{set-metadata} h2. Description {excerpt:hidden=false}A power connection is
missing in the data center model from this Remote Distribution Panel (RDP) to the power supply from which it should receive power.{excerpt} h2.
Recommended Action # Right-click the RDP and select *Properties* to open its Properties dialog box. # In the *Power Dependency* page, select
the appropriate *Power supply* option to connect the RDP to the PDU from which it should receive power. ||See also|| [Optimizing the design by
following the recommendations]
Equipment connected to this PDU draws more power than is supported by the power supply breaker
{set-metadata:_UImapping_}pduMaxPowerDrawExceededConstraint{set-metadata} h2. Description {excerpt:hidden=false}The breaker does not
provide sufficient power to cover the power requirements of the equipment connected to this PDU. If you are working with 3 phase equipment, this
will trigger a recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action * If the equipment
drawing power from this PDU is part of a capacity group, reduce the average estimated load for the group: *# In the *Layout* pane, right-click a
rack in a capacity group and select *Properties* to open its Properties dialog box. *# In the *Capacity* page, reduce the *Average estimated load*
for all racks in the capacity group. *# Repeat steps 1 and 2 for any other capacity groups that get power from the PDU. * Lower the estimated load
by disconnecting as much of the equipment that receives power from the PDU as necessary to keep the estimated load on the PDU within the
values supported by the breaker: *# Right-click the PDU in the *Layout* pane and select *Properties* to open its Properties dialog box. *# Select
*Power Distribution* and edit or delete any surplus power connections * In the *Rack Layout*, select equipment in the racks that connect to the
PDU to drag that equipment to racks that are not connected to it. ||See also|| [Optimizing the design by following the recommendations]
Equipment connected to this Power Panel draws more power than is supported by the power supply
breaker
{set-metadata:_UImapping_}powerPanelMaxPowerDrawExceededConstraint{set-metadata} h2. Description {excerpt:hidden=false}The breaker
does not provide sufficient power to cover the power requirements of the equipment connected to this power panel. If you are working with 3
phase equipment, this will trigger a recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action *
If the equipment drawing power from this Power Panel is part of a capacity group, reduce the average estimated load for the group: *# In the
*Layout* pane, right-click a rack in a capacity group and select *Properties* to open its Properties dialog box. *# In the *Capacity* page, reduce
the *Average estimated load* for all racks in the capacity group. *# Repeat steps 1 and 2 for any other capacity groups which get power from the
Power Panel. * Lower the estimated load by disconnecting as much of the equipment that receives power from the Power Panel as necessary to
keep the estimated load on the Power Panel within the values supported by the breaker: *# Right-click the Power Panel in the *Layout* pane and
select *Properties* to open its Properties dialog box. *# Select *Power Distribution* and edit or delete any surplus power connections * In the
*Rack Layout*, select equipment in the racks that connect to the Power Panel to drag that equipment to racks that are not connected to it. ||See
also|| [Optimizing the design by following the recommendations]
Equipment connected to this remote distribution panel (RDP) draws more power than is supported by
the power supply breaker
{set-metadata:_UImapping_}rdpMaxPowerDrawExceededConstraint{set-metadata} h2. Description {excerpt:hidden=false}The breaker does not
provide sufficient power to cover the power requirements of the equipment connected to this RDP. If you are working with 3 phase equipment, this
will trigger a recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action * If the equipment
drawing power from this RDP is part of a capacity group, reduce the average estimated load for the group: *# In the *Layout* pane, right-click a
rack in a capacity group and select *Properties* to open its Properties dialog box. *# In the *Capacity* page, reduce the *Average estimated load*
for all racks in the capacity group. *# Repeat steps 1 and 2 for any other capacity groups that get power from the remote distribution panel (RDP).
* Lower the estimated load by disconnecting as much of the equipment that receives power from the remote distribution panel (RDP) as
necessary to keep the estimated load on the remote distribution panel (RDP) within the values supported by the breaker: *# Right-click the remote
distribution panel (RDP) in the *Layout* pane and select *Properties* to open its Properties dialog box. *# Select *Power Distribution* and edit or
delete any surplus power connections. * In the *Rack Layout*, select equipment in the racks that connect to the remote distribution panel (RDP) to
drag that equipment to racks that are not connected to it. ||See also|| [Optimizing the design by following the recommendations]
Equipment in this rack receives power from multiple power supply devices
{set-metadata:_UImapping_}PowerPathSetupForNetworkingRackConstraint{set-metadata} h2. Description {excerpt:hidden=false}Multiple power
connections have been set up for equipment in this rack. It can be supplied either through rack PDUs or, if it is a rack with network equipment,
Ethernet. Network equipment not using power from the UPS must be excluded from the power calculations. {excerpt} h2. Recommended Action
To configure a network power connection for the rack: # Remove the rack PDUs in the rack. # Right-click the rack in the layout and select
*Properties* to open its Properties dialog box. # Ensure *Exclude rack's load from power calculations* has been selected. To configure a rack
PDU power connection: # Right-click the rack in the layout and select *Properties* to open its Properties dialog box. # Ensure *Exclude rack's load
from power calculations* has been deselected. # Add rack PDUs to the rack and configure the power connection. ||See also|| [Optimizing the
design by following the recommendations]
Power connection configuration is invalid for equipment in one or more racks in the group
{set-metadata:_UImapping_}rackInGroupMustConnectToSameUPSConstraint{set-metadata} h2. Description {excerpt:hidden=false}A rack PDU in
this capacity group is connected to a power supply that does not match the connection set up for the other rack PDUs, e.g. all rack PDUs in a rack
are connected to a specific UPS except for one that is connected to another UPS.{excerpt} h2. Recommended Action To make the connections
match, edit the power connection of the rack PDU that is not connected to the intended power supply as described below, or remove the rack
from the group by right-clicking it and selecting *Remove from Capacity Group*. # In the *Floor Layout*, select the *Power Path* tab at the bottom
of the layout pane. # Identify the rack in the group with the unwanted power connection setup (the color-coded connections help identify the
connections). # In the *Layout* pane, right-click the rack identified in step 2 and select *Properties* to open its *Properties* dialog box. # In the
*Power* page, set its power supply connection to match the other rack PDUs in the capacity group. Alternatively, you can right-click the PDU or
Power Panel and select *Properties*, then select the *Power Dependency* pane to access the *Power Distribution* properties to select a rack
PDU. Click *Edit* and edit the power connection to match the other connections for equipment in the same rack. ||See also|| [Optimizing the
design by following the recommendations]
Reduce the capacity group's peak load setting: ** Right-click the rack and select *Properties* to open its *Properties* dialog box ** In the
*Capacity* page, reduce the *Peak Load (per rack)* value. * Remove the rack from this capacity group by right-clicking the rack, and selecting
*Remove from Capacity Group*. ||See also|| [Optimizing the design by following the recommendations]
The average estimated load of the racks in the group exceeds the group's average load settings
{set-metadata:_UImapping_}RackTotalPowerDrawExceedsGroupPlannedAvg{set-metadata} h2. Description {excerpt:hidden=false}The estimated
load of the racks in the group is higher on average than what you are planning for the group. If you are working with 3 phase equipment, this will
trigger a recommendation message even if the value is exceeded for only one of the phases. {excerpt} h2. Recommended Action Perform one of
the following actions, making sure that the data center model still reflects the actual physical infrastructure: * Right-click racks in the capacity
group and select *Properties* to reduce the *Average Load (per rack)*, a *Capacity* option in the Properties dialog box for these racks until the
racks no longer exceed the group's average estimated load setting. * Remove equipment from one or more of the racks until the connected racks
no longer exceed the group's average estimated load setting. * Change the phase settings: *# If a server's load on only 1 phase is causing the
warning and there is still capacity left on the other phases, right-click the server and select *Properties* to open its Properties dialog box. *# In
*Power* page, edit to connect to another phase in *Connections* section. \\ \\ {tip:icon=false}*Tip*: Select the *Power Details* view tab available at
the bottom of the *Rack Layout* pane to see a color-coded bar below the racks illustrating the load distribution on the phases.{tip} * Remove one
or more of the racks from the group until the remaining connected racks no longer exceed the group's average load setting. ||See also||
[Optimizing the design by following the recommendations]
The breaker configuration in the Power Distribution properties does not match the measured power
data
{set-metadata:_UImapping_}measuredPowerDrawMatchesBreakerModuleSetupConstraint{set-metadata} h2. Description
{excerpt:hidden=false}When the configuration is done and the system is running with device associations and retrieval of measured data from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true}, the system notifies you if the module number and phase configuration in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} do not match the measurements. The number in brackets tells you which
module number causes the issue. h2. Recommended Action * Reconfigure the breaker configuration to match the actual physical environment. *
If you have configured sensor mappings, reconfigure the sensor mapping configuration to match the actual physical environment. {tip:icon=false}
*Note*: When you have reconfigured and resolved the issue, it may take some time before new data is retrieved from
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} and this message disappears.{tip} h2. Example The system will notify you
when there is a mismatch between the configuration and the measured data for a module. For example, you will get this notification if you have
configured Rack PDU connections for breaker module 10, 11, 12, and 13 on a modular PDU but measured data only exists for module 10, 11,
and 13. In this case, you can right-click the PDU and select *Launch to Device* to see the measured data and module numbers to see what the
issue is with module 12. It is occupied and {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} reports an issue with it because
no measurements are available to the system. {tip:icon=false}{*}Note*: You cannot directly compare the power values you see here with the ones
in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. The power values displayed on the device in
{multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} are instant values whereas the values in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} are peak values. {tip} To resolve the issue, you must remove the module
number 12 from the breaker configuration in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}.
!launchtodevice_seemoduleno.png|thumbnail! || See also || [Optimizing the design by following the recommendations]
The capacity group supports a higher redundancy than this server requires
{set-metadata:_UImapping_}rackPowerConsumerRedundcyShouldMatchCapacityGroupConstraint{set-metadata} h2. Description
{excerpt:hidden=false}The redundancy set up for the selected equipment in a rack does not match the internal redundancy planned for the
capacity group. The group supports a higher redundancy than the server requires.{excerpt} h2. Recommended Action * To avoid stranded
capacity, replace the rack-mounted equipment with equipment that has redundancy settings matching the group settings. Remove it and add a
better match, either by using drag-and-drop or *Add to Best rack* (if you have the add-on product installed that enables this feature). * If the
equipment's redundancy settings are incorrect: *# In the *Rack Layout*, right-click the equipment and select *Properties*. *# In the *Power* page,
select the appropriate *Redundancy*. ||See also|| [Optimizing the design by following the recommendations]
The input voltage setting required by the equipment is not available in current rack
{set-metadata:_UImapping_}EquipmentInputVoltageIsNotSupportedByRackConstraint{set-metadata} h2. Description {excerpt:hidden=false}In the
data center model, the server's input voltage requirement cannot be supplied by the rack PDU in the rack. {excerpt} h2. Recommended Action
Make sure the voltage of the server matches the voltage of the rack PDU to which you want to connect: * Replace the rack PDU with one that
supports the required voltage. * Replace the server with one that has the correct input voltage supported by the rack PDU. * If the voltage
properties of either the server, rack PDU, PDU or Power Panel are incorrect, right-click that piece of equipment in the catalog and select
*Properties* to correct the value. ||See also|| [Optimizing the design by following the recommendations]
The measured load exceeds the estimated load per phase designed for the rack
{set-metadata:_UImapping_}MeasuredRackPeakExceedsRmPduAndPhaseMappedNameplatePowerDrawConstraint{set-metadata} h2.
Description {excerpt:hidden=false}Your physical infrastructure contains connected devices in the rack that use more power than the estimated
load per phase in the rack reflected in the data center model.{excerpt} {tip:icon=false}*Note*: This message only appears when all servers in a
rack have a power phase configuration. If you disconnect a phase connection for a server in a rack, this message will disappear, but it does not
necessarily mean there is no longer an issue with the configuration.{tip} h2. Recommended Action Update the solution to accurately reflect the
equipment in the physical infrastructure by adjusting the estimated load values for the equipment in the rack. * If you have added the appropriate
servers to the rack: ** Modify the estimated load: *** Right-click the servers in the rack and select *Properties*. *** Select the *Power* section to
access the power properties. *** Increase the *estimated load* value. ** Verify that the servers are connected to the correct phases in the system
to reflect your physical infrastructure: *** Right-click the servers in the rack and select *Properties*. *** Select the *Power* section to access the
power properties. *** Modify the phase connection in the *Power Cable Connection* table. * If you are in the process of designing your data center
and have not yet added the sufficient amount of servers to the rack: ** Drag the missing servers into the rack as required and configure phase
connection for each server. ||See also|| [Optimizing the design by following the recommendations]
The measured load exceeds the total estimated load configured for the rack
{set-metadata:_UImapping_}MeasuredRackPeakExceedsNameplatePowerDrawConstraint{set-metadata} h2. Description
{excerpt:hidden=false}Your physical infrastructure contains connected devices in the rack that use more power than the total estimated load in the
rack reflects.{excerpt} h2. Recommended Action Update the solution to accurately reflect the equipment in the physical infrastructure by adjusting
the estimated load values for the equipment in the rack. * If you have added the appropriate servers to the rack: ** Modify the estimated load: ***
Right-click the servers in the rack and select *Properties*. *** Select the *Power* section to access the power properties. *** Increase the
*Estimated load* value. * If you are in the process of designing your data center and have not yet added the sufficient amount of servers to the
rack: ** Drag the missing servers into the rack as required. ||See also|| [Optimizing the design by following the recommendations]
The measured load of the connected rack PDU is 0, but an estimated load has been configured for the
rack
{set-metadata:_UImapping_}MeasuredPowerDrawZeroConstraint{set-metadata} h2. Description {excerpt:hidden=false}The rack PDU in the layout
associated with an external system device reports no load, but in the data center model, an estimated load has been configured for the connected
servers in the layout.{excerpt} h2. Recommended Action Troubleshoot why the physical device is not reporting any measured data. It may be
turned off or not yet physically connected. ||See also|| [Optimizing the design by following the recommendations]
The measured load of the UPS exceeds the total estimated load of the connected equipment
{set-metadata:_UImapping_}MeasuredUpsPeakExceedsNameplatePowerDrawConstraint{set-metadata} h2. Description
{excerpt:hidden=false}Your physical infrastructure contains devices connected to the UPS that use more power than your design reflects or they
have not been assigned to the correct UPS in the data center model layout to correctly represent the physical infrastructure. If you are working
with 3 phase equipment, this will trigger a recommendation message even if the measured value is only too high for one of the phases.{excerpt}
{tip:icon=false}*Note*: This message will typically occur until the initial system setup has been completed. It can also occur if equipment has
recently been removed from the rack. The measured average value will change over time to reflect the change.{tip} h2. Recommended Action
Update the data center model to accurately reflect the equipment in the infrastructure by assigning devices to the correct location in the
*Navigation* pane. * If the device has been assigned to the wrong UPS in the *Layout* pane, drag it from that location in *Navigation* pane, or
floor layout, to the correct location. * If the value is wrong in the *Manufacturer's Nameplate* / *Estimated load* field for the connected equipment,
right-click the equipment and select *Properties* to correct the value. ||See also|| [Optimizing the design by following the recommendations]
The phase configuration for the connected server is not supported by the rack PDU
{set-metadata:_UImapping_}EquipmentIsConnectedToWrongPowerPhaseConstraint{set-metadata} h2. Description {excerpt:hidden=false}The
phase connection configured for this server is not valid. This message will typically occur if you have configured a power connection to this server
but subsequently make changes to the phase configuration.{excerpt} h2. Recommended Action * Modify the server's phase properties: **
Right-click the server in the rack and select *Properties*. ** Select the *Power* section to access the power properties. ** Modify the phase
connection by selecting a valid power phase connection in the *Power Cable Connection* table. ** If there is no available phase to choose, the
rack PDU output voltage might not match the server's voltage requirements. * Modify the rack PDU's phase properties: ** Right-click the rack PDU
in the rack and select *Properties*. ** Select the *Power Dependency* section to access the power properties. ** Modify the phase connection by
selecting a valid power phase connection in the *Power phase* drop-down. ||See also|| [Optimizing the design by following the recommendations]
The Rack PDU output voltage setting does not match the output voltage of the connected PDU or
Power Panel
The UPS in the layout does not supply enough power to match the configured load of connected
equipment in the layout
{set-metadata:_UImapping_}UpsCapacityExceedPlannedCapacityConstraint{set-metadata} h2. Description {excerpt:hidden=false}The load of the
equipment connected to the UPS is higher than the load that the UPS can supply. If you are working with 3 phase equipment, this will trigger a
recommendation message even if only one of the phases is overloaded.{excerpt} h2. Recommended Action Perform one of the following actions:
* For racks in a capacity group, right-click racks in the group and select *Properties* to reduce the *Average Load (per rack)*, a *Capacity* option
in the *Properties* dialog box for these racks until the racks no longer exceed the capacity of the UPS. * For racks not in a capacity group, remove
equipment from one or more of the racks until the total power consumption of the connected racks no longer exceeds the capacity of the UPS.
Total power consumption is the sum of the *Estimated load*, a *Power* value in the Properties dialog box of the racks connected to the UPS. *
For other equipment connected to the UPS, for example a CRAC, review the estimated load value or disconnect its power connection to the UPS.
* Right-click the UPS and select *Properties* to increase its *Capacity*, a *Power* option in the Properties dialog box. * Replace the UPS with one
that can distribute more power. ||See also|| [Optimizing the design by following the recommendations]
This server requires a higher redundancy than is available in the capacity group
{set-metadata:_UImapping_}RackPowerConsumerRedundancyMustMatchCapacityGroup{set-metadata} h2. Description
{excerpt:hidden=false}The redundancy set up for the selected equipment in a rack does not match the internal redundancy planned for the
capacity group. The server requires a higher redundancy than is available in the group.{excerpt} h2. Recommended Action * Replace the
rack-mounted equipment with equipment that has redundancy settings matching the group settings or * If the equipment's redundancy settings
are incorrect: *# In the *Rack Layout*, right-click the equipment and select *Properties*. *# In the *Power* page, select the appropriate
*Redundancy*. ||See also|| [Optimizing the design by following the recommendations]
!icon_instantPUE_adddevices.png!. ## In the wizard, follow the steps to select one or more devices and sensors from the list. \\ \\
{tip:icon=false}*Tip*: Select multiple non-consecutive items by using Ctrl-click, or multiple consecutive items by using Shift-click.{tip} ## You can
filter the list and search for one or more devices or sensors to add to the PUE/DCiE calculation by starting to type the name or model in the
*Search* field. As you type in the Search box, the list shows all equipment that contains the typed characters in the selected column. ## Add
custom values by clicking this icon !icon_instantPUE_addcustom.png!. ## In the dialog box, type *Name*, *Value*, *Unit*, and *Factor*. *Unit* and
*Factor* can be used to make adjustments to the value, e.g. if the unit of one item does not match the others, such as kW and W or kVA, or if
there is a factor that needs to be left out of the calculation, for example if the value is a total and some of it is used for other data centers as well.
## Delete any obsolete entries by clicking this icon !icon_instantPUE_deleteentry.png!. # Use the icons in *IT Load* section of the *Configuration*
tab to set up the system with information about how much power is needed by the IT load in the data center. ## Add device sensor measurements
by clicking this icon !icon_instantPUE_adddevices.png!. ## In the wizard, follow the steps to select one or more devices and sensors from the list.
\\ \\ {tip:icon=false}*Tip*: Select multiple non-consecutive items by using Ctrl-click, or multiple consecutive items by using Shift-click.{tip} ## You
can filter the list and search for one or more devices or sensors to add to the PUE/DCiE calculation by starting to type the name or model in the
*Search* field.\\ In the *Search* box, start typing some characters of the equipment you want to see. As you type, the pane shows all items that
contain the typed characters in the column that is selected. ## Add custom values by clicking this icon !icon_instantPUE_addcustom.png!. ## In
the dialog box, type *Name*, *Value*, *Unit*, and *Factor*. \\ *Unit* and *Factor* can be used to make adjustments to the value, e.g. if the unit of
one item does not match the others, such as kW and W or kVA, or if there is a factor that needs to be left out of the calculation, for example if the
value is a total and some of it is used for other data centers as well. \\ ## Delete any obsolete entries by clicking this icon
!icon_instantPUE_deleteentry.png!. # See the results of the configuration expressed as a graph in the PUE/DCiE dial published to the PUE/DCiE
Dashboard available from *> Analytics* *> PUE/DCiE Dashboard*. It can also be accessed at any time on the
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server for viewing without having the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application running. \\ \\ {tip:icon=false}*Note*: The PUE/DCiE graph shows
the calculated PUE/DCiE based on measured data collected on a daily basis (midnight to midnight). This data collection method is also referred to
as measurement sampling level 2, intermediate according to the Green Grid definitions. \\ When you add a sensor to the calculations, the data
collected from this sensor the previous day, if any, is included in the calculations immediately. When you add a newly-installed sensor, its value
will be included in the calculations once the data collection has run for 24 hours or at least since before the previous midnight.{tip}| [About PUE
and DCiE] [Preferences: Showing PUE or DCiE values|Reviewing system preferences#pref_EEmetric] [Using the PUE DCiE Dashboard]|
you want to include when you generate a report based on these settings. # Click *Save Filter As...* in the top right corner of the options section.
Some data is required for certain report types. If you try to save without this data, you will be prompted to select the required options. # In the
Save dialog box, type a name for the report filter template. The saved report filter template now appears in the list of available reports as a sub
type to the selected report type. h2. Applying a previously saved report template # In *Available Reports*, click the + symbol next to the report
type to expand the list and see the available report filter templates. # Select the report filter template to apply. You can now see the filter settings
of the selected template. # Select *Generate Report*. The generated report displays in the *Report View*. You can now use the *Report View*
toolbar to navigate the report pages on the screen (arrow icons), or to print or export the report to a file in any of the available formats (Export
icon, down arrow for selection of format). ||See also|| [Working with reports] [Saving KPIs over time] [Customizing report designs]
information about the energy efficiency concepts, such as Power Usage Effectiveness (PUE), go to: [the Green Grid|http://www.thegreengrid.org/]
and read the [White Papers|http://www.apc.com/go/promo/whitepapers/index.cfm]. * WP-157: Selecting an Industry-Standard Metric for Data
Center Efficiency * WP-154: Electrical Efficiency Measurement for Data Centers * WP-114: Implementing Energy Efficient Data Centers *
WP-113: Electrical Efficiency Modeling for Data Centers *Tags included in this report are tags on racks. If you include a piece of tagged
rack-mounted equipment and select to include this tag in the report, it will not be included in the report calculation. Only if the rack that the piece
of equipment is positioned in is tagged and selected for the report, it will be included. {column}{column:width=50%}
!report_energycost.png|thumbnail!{column}{section} ||See also|| [Working with reports]
{table-row} {table-row} {table-cell} !icon_led_red.gif|align=center!\\ {table-cell} {table-cell}The defined output voltage of the connected PDU and
rack PDU is not supported. You may need to select another PDU or rack PDU for this power connection, or change the properties of either
component if these are incorrect. {table-cell} {table-row}{table} ||See also|| [Enabling placement recommendations]
Creating tags
{excerpt:hidden=false}Tags can be created in the Configure Tags dialog box accessed from *Tools* *> Configure Tags*. When tags have been
created, they are subsequently available in the application to be assigned to equipment in the floor and rack layout.{excerpt} # In the Configure
Tags dialog box, select *Add* to create new tags or categories. # Select if the tag is a strict requirement that must be met to be able to add a
piece of equipment to a rack*. # Select a tag from the list and select *Up* or *Down* to move it and create a hierarchical structure according to
your preferences. # If necessary, select a tag or category from the list and select *Edit* to modify it. # If necessary, select a tag or category from
the list and select *Remove* to delete it from the list. *This setting controls the behavior of the Add to best rack feature. If you select that a
matching tag is a strict requirement, the tag assigned to a piece of equipment must match the tag assigned to the rack to which you are adding it.
The placement status message: Rack tags support equipment tags will show with a red LED symbol next to it. If you select that a matching tag is
not a strict requirement, the tag assigned to a piece of equipment does not have to match the tag assigned to the rack, but it is recommended that
it does. The placement status message will show with a yellow LED symbol next to it. ||See also|| [Working with tags]
Tag Properties
{excerpt:hidden=false}This section of the Properties dialog box lists tags associated with a component, e.g. a rack or server.
{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:} *Name* {table-cell} {table-cell:}Defines the tag name. {table-cell} {table-row}
{table-row} {table-cell:} *Description* {table-cell} {table-cell:}Defines the value the tag provides. {table-cell} {table-row} {table}
{tip:icon=false}*Note*: The listed information is defined by added tags in the Select Tags dialog box that are accessed by the *Add* button;
*Remove* allows you to remove any listed tag.{tip} ||See also|| [Working with Tags]
Simulating IT Impact
{section}{column:width=50%}{excerpt:hidden=false}The IT Impact simulation provides an indication of issues or potential issues with the active
power and cooling configuration in the event of a failure. {excerpt} The IT Impact simulation can be accessed by right-clicking a piece of
equipment in the Floor Layout (1). You can use the IT Impact option to simulate a failure to determine whether the design is strong enough to fit
the requirements of the real-world infrastructure, for example: * If a selected UPS was to fail, what connected equipment would be impacted and
lose the power supply or redundancy due to the failure (2). * If a selected cooling unit was to fail, what surrounding equipment would be impacted
and overheating or losing redundancy due to the failure. Simulated impact of cooling failure is based on calculated inlet temperature for individual
racks compared to the maximum target inlet temperature for the room. If the first value exceeds the latter, the impact will show as overheating all
equipment in the rack. The calculated inlet temperature for an individual rack can be seen by selecting the *Cooling* tab in the Floor Layout, and
hovering over the rack to see the tool tip. The inlet temperature is calculated as the high-level average inlet temperature for the rack. The
calculations are not detailed enough to specify the temperature more precisely, such as floor, middle, or top of the rack. In addition, the generic
cooling prerequisites, assumptions, and design guidelines apply. {tip:icon=false}*Note*: The simulation is only as accurate as the source
information (the data provided in the data center model). A simulation, although a helpful and informative tool, may not be accurate and only
shows eventual real effects.{tip} {column}{column:width=50%} !simulateimpact.png|thumbnail! !UPSfailtable.png|thumbnail! {column}{section} ||
123 Steps to... || See also || | *Viewing the IT impact of a failing piece of equipment* \\ # Select a piece of equipment in the *Floor Layout* that: #*
Supplies power to other equipment in the layout, for example a UPS or PDU. #* Supplies cooling to other equipment in the layout, for example a
row-based cooling unit. # Right-click it, and select *Simulate Impact* to simulate failure and see the impact. \\ In the *Simulated Impact* table, the
equipment that would be impacted is listed. The *Status (Live)* field is used for equipment that is associated with live devices and indicates the
device status: OK, Failure, Critical, Error, Warning, Informational. \\ \\ {tip:icon=false}*Note*: If a piece of equipment has not been associated with
a device, it will show as OK.{tip} \\ *Viewing the IT impact of an active alarm* \\ 1. Select an alarm in the *Alarms* pane below the layout (available
when *Operations* is selected in the Application bar). 2. Right-click it, and select *Simulate Impact* to see the impact if the live device that is
reporting the alarm would fail. \\ A list of equipment in the data center model that would be affected by the simulated failure pops up, including a
description about what type of impact the failure would have, such as power loss, or power redundancy loss. \\ | [Filtering Simulated Impact List
(Search)|Filtering Simulated Impact List (Search)] \\ [Exporting Impact Table] \\ [Configuring Simulated Impact Layout] \\ [Configuring Cooling
Impact Preferences] \\ [StruxureWare Operations - Capacity|StruxureWare Operations - Capacity] \\ |
*Data Center Planning* and as read-only information in *Data Center Operations*. You configure the position of your host servers in the data
center layout and associate the servers with your virtual servers. In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, a
number of alarms are considered crucial to the continuous operation of the virtual machines. If you have associated a host to a server in the
layout that is affected by one of the following scenarios, the system will notify the virtual machine management system of an impact on the host
that should be migrated: * A power supply with an alarm that could lead to imminent power loss, e.g. a UPS is failing or running low on battery * A
cooling unit with an alarm that could lead to a server overheating, e.g. a cooling unit's compressor or power supply is failing The associated host
will be marked as critically impacted (red icon). * In Microsoft Virtual Machine Manager, the location and impact data from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} will be available via the generated PRO tip, allowing the Virtual Machine
Manager administrator to configure automatic migration to a healthy location of the virtual machine servers marked as impacted. * In VMware
vCenter Server, the impacted hosts will be put into maintenance mode. For further information, refer to the VMware documentation. However, an
alarm that occurs on one of the power supplies in a redundant power supply setup is considered a non-critical impact and the associated host will
be marked as non-critically impacted (yellow icon). * No PRO tip will be generated from this type of impact in Virtual Machine Manager and no
servers will be migrated. * No data will be communicated from this type of impact to the vCenter Server and no servers will be migrated. By
default, the system supports [the standard critical alarm types|StruxureWare Operations - PRO Pack Supported Alarm Types]. However, it is
possible to customize the critical alarm and threshold configuration for migration of impacted servers. ||See also|| [Enabling Impact Analysis with a
VMware vCenter Server setup] [Locating virtual machines hosts with impact in the layout] [Refreshing Virtual Machine Host data] [Removing the
maintenance mode on a host with a VMware vCenter Server setup] [Virtual Machine Host Properties] [Working with virtualization]
Removing the maintenance mode on a host with a VMware vCenter Server setup
{excerpt:hidden=false}You can remove the maintenance mode on a host that was critically impacted by an alarm in
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} after the impact has been resolved. {excerpt}This can be done when
working in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} as well as in the VMware environment. To remove the
maintenance mode on a host in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}: # In the *External Systems* pane, identify
the host that used to be critically impacted but is now safe. It is marked as in maintenance mode and is highlighted on the modeled servers in the
layout with a yellow or gray V icon (used to be red), and it is marked as in maintenance mode. # Right-click the virtual machine host in the
*External Systems* pane, and select *Exit Maintenance Mode* to remove the maintenance mode on the host. For information on how it is done in
the VMware environment, refer to the VMware documentation. ||See also|| [Performing an impact analysis on virtual machine hosts] [Working with
virtualization] [Enabling Impact Analysis with a VMware vCenter Server setup] [Locating virtual machines hosts with impact in the layout]
[Refreshing Virtual Machine Host data] [Virtual Machine Host Properties]
Capacity reports
{section}{column:width=50%}{excerpt:hidden=false}You can generate capacity reports showing an overview of the capacity and capacity over
time.{excerpt} h2. Power Capacity report You can generate a report with power data, i.e. available estimated load and planned estimated load. h2.
Capacity History report You can generate a report with a graph showing capacity data from a specified time period, e.g. the total load of all
connected equipment (calculated by the system) or the measured peak load on the UPS devices (actual measured data form associated UPS
devices). The Capacity History report is available if you have a valid {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true}
license. {tip:icon=false}*Note*: The report is based on data collected over the last 24 hours, so the server must have been running for at least 24
hours.{tip} When you select the report filter options, select what is appropriate according to the data types. For example, when you are generating
a report of available U-space, select a rack (not a UPS), and for a report of measured peak load, select a UPS (not a rack). The generated report
displays in the *Report View*. You can now use the *Report View* toolbar to navigate the report pages on the screen (arrow icons), or to print or
export the report to a file in any of the available formats (*Export* icon, down arrow for selection of format). {column}{column:width=50%}
!report_capacityhistory.png|thumbnail! {column}{section} ||See also|| [Working with reports]
PP is represented in the layout as one component and, normally, one device from an external system is associated with one component in the
layout. However, if the physical and non-physical representations do not match, you can drag and drop sensors from multiple devices in *External
Systems* to one PDU, RDP, or PP in the layout. ||See also|| [Configuring Branch Circuit Monitoring] [Working with Branch Circuit Monitoring]
not appear in this perspective. !Configuring the room layout^video24x20.jpg! Watch this [video tutorial|Video Tutorials#changesviewvideo] to see
how to monitor the structured change management process. h2. Monitoring You can use the charts and views for insight (read-only). They update
dynamically as you drill down left to right and top to bottom. * Click on a specific location to see all the related tasks or continue drilling down on
assignee, project code, time, etc. * In the *Tasks Overview*, navigate and zoom in on the time line, and hover over the colored bars to see tool tip
details. * Quickly identify overdue tasks in the *Summary* view: Click the word *Overdue*, and the *Work Order Tasks Overview* will show only
these overdue tasks. The same kind of filtering happens when you click on *Not Started*, *In Progress*, etc. * In the *Project Overview*, filter on
tasks with a specific project code. The charts and views update accordingly. {tip:icon=false}*Tip*: Over time, the amount of tasks in the system will
grow, and you can select *Hide completed projects* to only see the active tasks.{tip} h2. Editing The *Work Order Tasks Overview* pane,
however, provides an option to edit tasks across work orders. * Double-click a task in the list to open the work order with this task in the *Work
Order Editor* and apply changes. For example, if a resource is out sick or will be on vacation next week, select all tasks not started or in progress
for this assignee and reassign them to another resource or change the due date to postpone the tasks until he returns. * At any time, right-click
and print a list of tasks, for example assigned to a specific resource and hand it out. {column} {column:width=50%} !StruxureWare Operations Change^change_overview.png|thumbnail! {column} {section} ||See also|| [StruxureWare Operations - Change] [Working with work orders]
Equipment Stages
{excerpt:hidden=false}When planning rack equipment, you can see equipment represented in various stages in the layout. The graphical
representation varies slightly at different zoom levels. {excerpt} {table:border=1|frame=box|} {table-row:align=center} {table-cell}*Layout*
{table-cell} {table-cell}*Equipment Stage* {table-cell} {table-cell}*Description* {table-cell} {table-row} {table-row} {table-cell:rowspan=5|}
!rackplanning.png|align=center!\\ {table-cell} {table-cell}Existing {table-cell} {table-cell}Equipment shown in its current location, with no action
pending. It displays in dark gray, indicating that it occupies the position shown. {table-cell} {table-row} {table-row} {table-cell}Pending Move
(Source) {table-cell} {table-cell}Equipment shown in its current location but has a move pending. It displays in blue with an arrow up, until you
select to save, indicating that it occupies the position shown but that you can still edit it. After you have saved, the color will change to light gray,
indicating that you can no longer edit it. {table-cell} {table-row} {table-row} {table-cell}Pending Move (Destination) / Planned {table-cell}
{table-cell}Equipment shown in its target location for a pending move. It displays in green with an arrow down, until you select to save, indicating
that the position is reserved, but that you can still edit it. After you have saved, the color will change to light gray, indicating that you can no longer
edit it. {table-cell} {table-row} {table-row} {table-cell}Pending Add {table-cell} {table-cell}Equipment shown in its target location for a pending
addition. It displays in green with a +, until you select to save, indicating that the position is reserved, but that you can still edit it. After you have
saved, the color will change to light gray, indicating that you can no longer edit it. {table-cell} {table-row} {table-row} {table-cell}Pending Deletion
{table-cell} {table-cell}Equipment shown in its current location, but with a pending deletion. It displays in green with an x in a circle, until you select
to save, indicating that it occupies the position shown but that you can still edit it. After you have saved, the color will change to light gray,
indicating that you can no longer edit it. {table-cell} {table-row} {table} ||See also|| [Rack equipment planning] [Planning changes to rack
equipment] [Working with work orders]
and export options for the work order list, multi-select work orders (Ctrl+click or Shift+click) and select *Print Work Order List*. The report view
opens and you can click the *Print* icon and then *Export* icon to export it as a PDF, HTML, or XLS document. * To view or print an audit report,
listing the tasks in a selected work order, right-click a work order and select *Audit Work Order*. The report view opens and you can click the
*Print* icon and then *Export* icon to export it as a PDF, HTML, or XLS document. {column} {column:width=50%} !StruxureWare Operations Change^rackplanning_WO_Editor.png|thumbnail! {column} {section} ||See also|| [Creating a controlled automated work order] [Creating a custom
work order without recorded tasks] [Identifying work order task and equipment relationship] [Creating and applying work order templates]
[Configuring work order administrative settings] [Work Order reports]
Planning* *> Data Center*. # At any time, right-click a component to see the properties. The components now have a power path setup, and the
load is included in the power capacity calculations. They also appear in the *Equipment Browser*, *Power Dependency pane*, *Inventory Report*,
and *Audit Trail Report*. | [StruxureWare Operations - Energy Efficiency] |
Configuring Infiltration
{excerpt:hidden=false}You can access and edit the data on the property tabs defining the configuration for infiltration by right-clicking an energy
system and selecting *Properties* or by clicking the icons at the bottom of the Energy System pane. The configuration options vary based on the
type of subsystem.{excerpt} # Right-click the energy system and select *> Properties* *> Infiltration*. # Define the *Dry bulb fixed loss* to indicate
the fraction of power that is lost per degree Celsius dry bulb. # Define the loss configuration in *Dry bulb fixed loss*: type a number between 0 and
100, indicating the fraction of power lost per degree Celsius dry bulb. ||See also|| [Energy System Configuration]
Configuring IT load
{excerpt:hidden=false}You can access and edit the data on the property tabs defining the configuration for IT load by right-clicking an energy
system and selecting *Properties* or by clicking the icons at the bottom of the Energy System pane.{excerpt} # Right-click the energy system and
select *> Properties* *> IT Load*. # Define the general settings for the energy system's IT load. ## Select if the IT load is on the critical or primary
power path. IT load must be included for the energy system. ## IT load is measured (live). # Use the *Script* tab for writing scripts that retrieve
measurements. ||See also|| [Energy System Configuration]
Creating scripts
{excerpt:hidden=false}Create scripts to extract any data, sensor measurements and estimations to be associated with the energy system's
components and included in the PUE/DCiE calculations.{excerpt} You must have created an energy system and included the components
representing your physical infrastructure. # In *Scripts* pane, click the *Add folder* icon, and type a name for the folder. # Select the created
folder, and click the *Add Script* icon to open the script editor. # Type the JavaScript to extract any data, sensor measurements and estimations.
# If you want to extract data from {multi-excerpt-include:pageTitle=Branding|name=ISXC|nopanel=true} devices, click *Devices* to access the
{multi-excerpt-include:pageTitle=Branding|name=ISXCb|nopanel=true} *Devices* dialog box. ## In the *Devices* section, select from the list of
devices to expand the list of device sensors below. ## In the *Device sensors* section, select from the list of device sensors. ## Double-click to
add the sensor ID to the script at cursor position.\\ \\ You can multi-select device sensors, and right-click to access functions to extract: #*
Minimum #* Maximum #* Sum #* Average \\ \\ The function will be inserted at the bottom of the script with a default name. If you insert more than
one function of the same type, e.g. to add two sets of average values, you must rename one of the average functions to avoid name conflicts. \\ \\
To use the result of the function as a measurement, assign it to the returnValue variable, e.g. {{returnValue=sum();}}. It is necessary to convert the
values you use to kW to avoid having some input values in W, and others in kW, and to ensure consistent data on the dashboard. \\ \\ # Click
*Evaluate* to validate, execute and display the result of the script. # Subsequently, if you want to edit the script, right-click it in the *Scripts* pane,
and select *Edit*. If the script has been associated with a component in an energy system, right-click the component and select *Edit Script*. # If
you regret creating a script, right-click the script in the *Scripts* pane, and select *Delete*. When the scripts have been created, you can associate
them with the components in an energy system to indicate which scripted values to include for which components. You can see the PUE/DCiE,
CO2 emission and cost results of the configuration expressed as graphs published to the Energy Efficiency Dashboard available when typing the
server's IP address into a Web browser. ||See also|| [Energy System Configuration] [Associating scripts] [Script Editor]
Associating scripts
{excerpt:hidden=false}Configure the association between the scripts and the components of the energy system to ensure the correct scripted data
is included in the configuration.{excerpt} You must have configured an energy system with included components and have created scripts before
you can start associating the scripts. # Double-click an energy system in the *Systems* pane to open it. # In the diagram, right-click a component
that has been included in the energy system, and select *> Associate Scripts* *> Folder name* *> Script name*. A green s icon appears on the
component in the diagram and on the script in the *Scripts* pane to illustrate the association. # If you regret associating a script with a component,
right-click the component and select *Unassociate Script*. # Subsequently, if you want to edit the associated script, right-click the component and
select *Edit Script*. ||See also|| [Creating scripts] [Script Editor]
Script Editor
{excerpt:hidden=false}The Script Editor allows for writing scripts, e.g. to extract measured data from devices using JavaScript.{excerpt} It is
accessed by clicking the *Add Script* icon in the *Scripts* pane, or by right-clicking an existing script or component in an energy system with an
associated script. Double-clicking a device sensor will add the sensor ID to the script window. Selecting multiple device sensors and right-clicking
will access functions to extract minimum, maximum, sum, and average values. Use the Energy Efficiency specific language construct returnValue
to return the value of the script. {tip:icon=false}*Note*: If you do not specify a returnValue, the script will return null.{tip} The script editor has
built-in content assistance, including: * Auto-complete on JavaScript language constructs and device sensor IDs (Ctrl-Space). * Text highlighting
of strings (blue), JavaScript language constructs (purple), comments (green), and reserved words, such as returnValue and importPackage
(orange). Clicking *Evaluate* will validate, execute and display the result of the script. ||See also|| [Creating scripts] [Associating scripts] [Energy
System Configuration]
Sample Scripts
{excerpt:hidden=false}Sample scripts are provided as a guideline for creating the scripts needed to configure the energy systems. You can copy
and paste snippets or whole scripts into the script editor, and modify according to your needs.{excerpt} ||See also|| [Creating scripts] [Script Editor]
[Database Integration] [Sample Startup Script for Database Integration] [Sample Simple Database Query Script] [Sample Database Query Script]
[Web Service Integration] [Sample Startup Script for Web Service Integration] [Sample Data Retrieval Script for Web Service Integration]
Startup Script
{excerpt:hidden=false}The startup script is used for setting up data providers needed for retrieving measurements from sensors and third party
systems. The startup script is run when the {multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} server starts.{excerpt} The
script is a JavaScript file named startup.js located at /data/e2m on the server. To edit the file, you must log on to the server using SSH with
sufficient user rights. ||See also|| [Creating scripts] [Script Editor]
Infiltration Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system or by clicking the relevant icon at the
bottom of the energy system, provides relevant information that identifies this subsystem. The information may vary based on the subsystem
type.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell:colspan=3|} *Configuration* {table-cell} {table-row} {table-row} {table-cell:} *Dry
bulb fixed loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost per degree Celsius dry bulb. {table-cell}
{table-row}{table} ||See also|| [Energy System Configuration]
IT Load Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system or by clicking the relevant icon at the
bottom of the energy system, provides relevant information that identifies this subsystem. The information may vary based on the subsystem type.
The IT load is a very dynamic value since it can change with the power consumption of each server in the data center. It will also change as
servers are added or removed from the date center.{excerpt}{table:border=1|frame=box|} {table-row} {table-cell:colspan=3|} *Configuration*
{table-cell} {table-row} {table-row} {table-cell:} *Power path* {table-cell} {table-cell:colspan=2|}Identifies whether the IT load is on the critical or
primary power path. You cannot choose to exclude it in this energy system. {table-cell} {table-row} {table-row} {table-cell:} *Calculation source*
{table-cell} {table-cell:colspan=2|}Identifies that the IT load is measured (live). {table-cell} {table-row} {table-row} {table-cell:} *Script* {table-cell}
{table-cell:colspan=2|}Opens the script editor for editing scripts to retrieve IT load measurements. {table-cell} {table-row}{table} ||See also||
[Energy System Configuration]
Lighting Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system or by clicking the relevant icon at the
bottom of the energy system, provides relevant information that identifies this subsystem. The information may vary based on the subsystem type.
Lighting covers the lighting is used to light the datacenter.{excerpt} {table:border=1|frame=box|} {table-row} {table-cell:colspan=3|} *Configuration*
{table-cell} {table-row} {table-row} {table-cell:} *Power path* {table-cell} {table-cell:colspan=2|}Identifies if this subsystem is on the critical or
primary power path, or if it is not included in this energy system. {table-cell} {table-row} {table-row} {table-cell:} *Calculation source* {table-cell}
{table-cell:colspan=2|}Identifies if the load of the subsystem is measured (live) or computed (without power meters). {table-cell} {table-row}
{table-row} {table-cell:} *Actual kW Nameplate* {table-cell} {table-cell:colspan=2|}Sums up the total nameplate value of all equipment in this
subsystem. {table-cell} {table-row} {table-row} {table-cell:} *Usable fraction of nameplate w/o derating* {table-cell} {table-cell:colspan=2|}Identifies
the usable fraction of power that can be used within the devices in this subsystem without derating the value. {table-cell} {table-row} {table-row}
{table-cell:} *Redundancy* {table-cell} {table-cell:colspan=2|}Identifies the redundancy of this subsystem. For example, if you have a redundant
setup with two 80 kW UPS, this value would be 2N. {table-cell} {table-row} {table-row} {table-cell:} *Redundancy "+1" kW Increment* {table-cell}
{table-cell:colspan=2|}Identifies the loss in kilowatt caused by internal redundancy. (Only needed if redundancy option includes +1.) {table-cell}
{table-row} {table-row} {table-cell:} *Derate Capacity fraction* {table-cell} {table-cell:colspan=2|}Identifies the usable fraction of the nameplate
value that can be used in this subsystem. For example, if you use a 20% safety margin, this value would be 0.8. {table-cell} {table-row} {table-row}
{table-cell:} *Typical PU* {table-cell} {table-cell:colspan=2|}Identifies the power usage (PU) of this subsystem relative to the total power usage.
{table-cell} {table-row} {table-row} {table-cell:} *Fixed loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is the fixed loss of
the subsystem. {table-cell} {table-row} {table-row} {table-cell:} *Proportional loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power
that is lost proportional to the load of the subsystem. {table-cell} {table-row} {table-row} {table-cell:} *Square Law loss* {table-cell}
{table-cell:colspan=2|}Identifies the fraction of power that is lost proportional to the square of the load of the subsystem. {table-cell} {table-row}
{table-row} {table-cell:} *Dry bulb fixed loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost per degree Celsius dry
bulb. {table-cell} {table-row} {table-row} {table-cell:} *Script* {table-cell} {table-cell:colspan=2|}Opens the script editor for editing scripts for this
subsystem. {table-cell} {table-row}{table} ||See also|| [Energy System Configuration]
Ventilation Properties
{excerpt:hidden=false}This section of the Properties dialog box, accessed by right-clicking an energy system or by clicking the relevant icon at the
bottom of the energy system, provides relevant information that identifies this subsystem. Equipment that supplies fresh air to the data center.
Ventilation includes fans, and, if present, any heaters, humidifiers and dehumidifiers associated with the fresh air ventilation system.{excerpt}
{table:border=1|frame=box|} {table-row} {table-cell:colspan=3|} *Configuration* {table-cell} {table-row} {table-row} {table-cell:} *Power path*
{table-cell} {table-cell:colspan=2|}Identifies if this subsystem is on the critical or primary power path, or if it is not included in this energy system.
{table-cell} {table-row} {table-row} {table-cell:} *Calculation source* {table-cell} {table-cell:colspan=2|}Identifies if the data of this subsystem is
measured (live) or computed (without power meters). {table-cell} {table-row} {table-row} {table-cell:} *Actual kW Nameplate* {table-cell}
{table-cell:colspan=2|}Sums up the total nameplate value of all equipment in this subsystem. {table-cell} {table-row} {table-row} {table-cell:}
*Usable fraction of nameplate w/o derating* {table-cell} {table-cell:colspan=2|}Identifies the usable fraction of power that can be used within the
devices in this subsystem without derating the value. {table-cell} {table-row} {table-row} {table-cell:} *Redundancy* {table-cell}
{table-cell:colspan=2|}Identifies the redundancy of this subsystem. For example, if you have a redundant setup with two 80 kW UPS, this value is
2N. {table-cell} {table-row} {table-row} {table-cell:} *Redundancy "+1" kW Increment* {table-cell} {table-cell:colspan=2|}Identifies the loss in kilowatt
caused by internal redundancy. (Only needed if redundancy option includes +1.) For example, if you have a 40 kW UPS with one spare 10 kW
power module, this value would be 10 kW. {table-cell} {table-row} {table-row} {table-cell:} *Derate Capacity fraction* {table-cell}
{table-cell:colspan=2|}Identifies the usable fraction of the nameplate value that can be used in this subsystem. For example, if you use a 20%
safety margin, this value would be 0.8. {table-cell} {table-row} {table-row} {table-cell:} *Typical PU* {table-cell} {table-cell:colspan=2|}Identifies the
power usage (PU) of this subsystem relative to the total power usage. {table-cell} {table-row} {table-row} {table-cell:} *Fixed loss* {table-cell}
{table-cell:colspan=2|}Identifies the fraction of power that is the fixed loss of the subsystem. {table-cell} {table-row} {table-row} {table-cell:}
*Proportional loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost proportional to the load of the subsystem.
{table-cell} {table-row} {table-row} {table-cell:} *Square Law loss* {table-cell} {table-cell:colspan=2|}Identifies the fraction of power that is lost
proportional to the square of the load of the subsystem. {table-cell} {table-row} {table-row} {table-cell:} *Dry bulb fixed loss* {table-cell}
{table-cell:colspan=2|}Identifies the fraction of power that is lost per degree Celsius dry bulb. {table-cell} {table-row} {table-row} {table-cell:}
*Script* {table-cell} {table-cell:colspan=2|}Opens the script editor for editing scripts for this subsystem. {table-cell} {table-row}{table} ||See also||
[Energy System Configuration]
Database Integration
{excerpt:hidden=false}You can integrate {multi-excerpt-include:pageTitle=Branding|name=ISXEE|nopanel=true} with any JDBC or ODBC
compliant database. To do this, you must configure a data provider in the startup script.{excerpt} ||See also|| [StruxureWare Operations - Energy
Efficiency] [Sample Startup Script for Database Integration] [Sample Simple Database Query Script] [Sample Database Query Script]
relating to the * sample code. Schneider Electric disclaims all warranties, express or implied, and in particular, * disclaims all warranties of
merchantability, fitness for a particular purpose, and warranties related * to the code, or any service or software related thereto. * * Schneider
Electric shall not be liable for any direct, indirect or consequential damages or costs * of any type arising out of any action taken by you or others
related to the sample code. */ /* * This script shows how to make a simple connection to an MS SQL database * and read measurements using
SQL * * The database drivers (JDBC drivers) should be loaded in the startup script. An example of this is available * in the file databasedriver.js in
the startup folder. * * This script assumes that the MS SQL database driver has been loaded. */ // Make Java SQL classes available to the script
importPackage(java.sql); // Define connection properties // The properties needed to connect to the database and the format of the connection
URL differ // between different database. Please consult the documentation of the JDBC driver for the database used // for specific information on
this matter username = "user1"; password = "password1"; server = "159.215.173.127"; port = 1134; databaseName = "sample"; connectionUrl =
"jdbc:sqlserver://" + server + ":" + port + ";databaseName=" + databaseName + ";user=" + username + ";password=" + password + ";" // Create a
connection to the database connection = DriverManager.getConnection(connectionUrl); // Create a statement to execute SQL // The sample
database contains the Measurements table with two columns: measurement_id and measurement_value // We want to extract the value of the
measurement with id 11111111 sql = "SELECT measurement_value FROM measurements WHERE measurement_id = '11111111'"; // Create
and execute statement statement = connection.createStatement(); result = statement.executeQuery(sql); // Move cursor to first result and retrieve
the value of measurement_value result.next(); value = result.getDouble("measurement_value"); // Return measurement returnValue = value;
//Release resources result.close(); statement.close(); connection.close();{noformat}
PUE and DCiE in *> Tools* *> Preferences* *> General*.{tip} | [Exporting dashboard graphs to an external web site] [Customization of exported
dashboard graphs] [StruxureWare Operations - Energy Efficiency]|
reports but this is not supported. For generic information about how to use the 3rd party features, refer to the built-in help system. You should
already have a working knowledge about scripting or find it easy to acquire this knowledge. {column}
{column:width=50%}!Insight.jpg|thumbnail!{column}{section} ||See also|| [Customizing report designs] [Working with reports]
{excerpt:hidden=false}Correcting connection or synchronization problems that may occur when using the mobile
device.{table:border=1|frame=box|} {table-row:align=center} {table-cell:}*Symptom* {table-cell} {table-cell:}*Explanation* {table-cell}
{table-cell:}*Solution* {table-cell} {table-row} {table-row} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Error
message: * Could not connect to server at specified address. Ensure the specified server is running. {panel} {table-cell} {table-cell:}{panel:
borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}One or more of the following conditions might exist: * The specified server is not
responding because it is not running. * The specified server refused the connection request because it is not a
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server. {panel} {table-cell} {table-cell:}Contact your
{multi-excerpt-include:pageTitle=Branding|name=ISXOserver|nopanel=true} server administrator. {table-cell} {table-row} {table-row}
{table-cell:rowspan=3|}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}Error Condition: * The mobile device application
cannot connect to or synchronize with the server. {panel} {table-cell} {table-cell:}If the mobile device is on a wireless network, that network may be
experiencing problems, or the server may be off-line. {table-cell} {table-cell:}{panel: borderStyle=none| borderColor=#FFFFFF| bgColor=#FFFFFF}
* Ensure that the wireless network is enabled. * Use the ping command from a desktop computer or through the network connection software on
the mobile device to determine whether the server is operating correctly. {panel} {table-cell} {table-row} {table-row} {table-cell:}If the mobile device
is in its cradle, one or more physical connections may be loose. {table-cell} {table-cell:}Ensure that the cable from the cradle is securely attached
and that the mobile device is firmly in the cradle. {table-cell} {table-row} {table-row} {table-cell:}Microsoft ActiveSync or Windows Mobile Device
Center (WMDC) for Windows Vista might be unavailable or not running. {table-cell} {table-cell:}Ensure that ActiveSync or WMDC is available and
running on the computer. {table-cell} {table-row}{table}{excerpt} ||See also|| [Local and server mode]
Asset Management
{excerpt:hidden=false}The *Asset Management* option on the main screen provides options to view, edit and audit equipment in the data center
model. {excerpt} || 123 Steps to... || See also || | *Viewing Equipment* \\ The Browse screen, accessed from the *Asset Management* option on
the main screen, allows you to view equipment in the data center model and access edit options.{excerpt} # Select *Asset Management* on the
main screen to open the Browse screen. # Select a room to view the racks within that room by double-clicking (or by tapping, holding, and
selecting *Open...*). # Select *Filter* in the bottom menu and select to show all floor-mounted items in the list (*Show All*), or only racks (*Show
Racks*). # Select a row in the *Select Row* list at the top of the Browse screen if the racks in the selected room are placed in multiple rows. #
Select a floor-mounted item such as UPS, PDU, or cooling unit to access details by double-clicking (or by tapping, holding, and selecting
*Open...*) to access details. # Select a rack to view the equipment in that rack by double-clicking (or by tapping, holding, and selecting *Open...*.).
# Select a piece of equipment in a rack by double-clicking a rack (or by tapping, holding, and selecting *Open...*.) to access equipment details,
e.g. for a server or blade enclosure. If you have {multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true}, the stage of a piece of
equipment determines which menu options are available for that item on the Browse screen. For an overview of the icons that identify equipment
stages, see [Equipment Stages]. # To view blade servers in a blade enclosure, continue to drill down by double-clicking the enclosure (or by
tapping, holding, and selecting *Open...*). # To view network routes for a piece of connected network equipment (read-only), select the
equipment, then *> Menu* *> Network*. # To navigate to a specific piece of equipment in the system based on the barcode, scan it with a barcode
scanner, or select *> Menu* *> Search Barcode*, and type the barcode manually. In the bottom menu, you can enable editing capabilities, for
example selecting *Add...* will open the Add Equipment screen. | [Adding Equipment] [Connecting Equipment] [Moving Equipment] [Deleting
Equipment] [Scanning equipment bar codes into StruxureWare Operations - Mobile] |
Adding Equipment
{excerpt:hidden=false}The Add Equipment screen allows you to add equipment to the data center model.{excerpt} # Select by double-clicking, or
tapping and holding a rack name on the Browse screen accessed through *Asset Management* on the main screen, and selecting *Add...*. The
Add Equipment screen opens. # Select an item of equipment to add from the list of latest products or by using *Search* or *Browse* to find it in
the product catalog. #* Select an item of equipment to add from the list of latest products. The available selections are configured through the
product catalog in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. # Select the piece of equipment by double-clicking or
tapping and holding, and display fields for a bar code and name. Specifying values for these fields is optional. ## *Bar Code*: Scan the item's bar
code into this field (or enter the characters of the code manually). ## *Name*: Enter a name to identify the item within your data center
configuration (Rack PDU 1, for example). If you omit this name, the model name of the item is used in screen displays. # Select *Next...* in the
bottom menu bar, and display custom properties. ## Tap and hold, and select to *Add*, *Edit* or *Remove* custom properties on the product that
you are adding. # Select *Next...* in the bottom menu bar, and display the location: room, rack, and location for the item of equipment within the
rack. ## Rack Mount Position: On the drop-down list, select one from the following: ##* *Front* for equipment that uses one or more U-positions
inside the front of the rack. ##* *Right Rear*, *Left Rear*, or *Rear* for equipment that is installed inside the back of the rack. ##* *Top* for
equipment that is on top of the rack. ##* *Not Mounted* for equipment that does not use any U-positions, such as a Rack PDU installed vertically.
## *Bottom U-Position*: For an item being added to the front view only, select the lowest-numbered U-position that the item will occupy. For
equipment that needs multiple U-positions, a U-position is available for selection only if it has enough U-positions above it to fit the equipment. #
Click *OK* to add the item of equipment. # Define if you want to configure a power connection to the equipment. #* If you select *Yes*, the Power
screen opens, in which you can configure how the equipment is connected for power. #* If you select *No*, the equipment will be added to the
specified position in the data center model. ||See also|| [Asset Management]
Connecting Equipment
{excerpt:hidden=false}The Power screen, accessed from the *Asset Management* option on the main screen, allows you to access options to set
up power connections.{excerpt} # Tap *Asset Management* on the main screen to open the Browse screen. # Tap and hold a location's name to
view the rooms in that location. # Tap and hold a room's name to view the racks in that room. # Tap and hold a rack's name to view the equipment
in that rack. # Tap and hold a server or rack PDU to open the Edit screen for this piece of equipment # Select *Power* in the menu, and review
the power connection setup as you may need to change the connection and phase settings. For example, if a server has been moved to a
different rack, verify that it is connected to the correct rack PDU (you might want to either move the connected rack PDU to the same rack or
reconnect the server to a rack PDU in the same rack). ## Tap and hold in the list to access add or remove connection options. ## To remove a
power connection select *Remove*. ## To add a connection select *Add...* and in the *Add Outlet Connection* screen, select between available
rack PDU and phase options. ||See also|| [Asset Management]
Moving Equipment
{excerpt:hidden=false}The Browse screen, accessed from the *Asset Management* option on the main screen, allows you to view equipment in
the data center and access edit options to move equipment.{excerpt} # Tap *Asset Management* on the main screen to open the Browse screen.
# Select a room to view the racks within that room by double-clicking (or by tapping, holding, and selecting *Open...*). # Select a rack to view the
equipment in that rack by double-clicking (or by tapping, holding and selecting *Open...*). # Select a piece of equipment in a rack by
double-clicking (or by tapping, holding and selecting *Open...*). # Select *Move...* in the bottom menu bar. #* To change the room or rack in
which the item is to be located, tap the button labeled with an ellipsis (...) to the right of the location fields and browse to a new location or, if the
field has focus, you can scan the barcode of a rack to select this rack as new location. #* Use the drop-down lists to select a position for the
moved equipment in the selected rack (*Top*, *Right Rear*, *Left Rear*, *Not Mounted*, *Front*, or *Rear*) and, for the front view, the bottom
U-position that the moved equipment will occupy. # Select *OK*. # Select *Power...* in the bottom menu bar to review the power connection setup
as you may need to change the rack PDU and Phase settings. For example, if a server has been moved to a different rack, verify that it is
connected to the correct rack PDU (you might want to either move the connected rack PDU to the same rack or reconnect the server to a rack
PDU in the same rack). ## Tap and hold in the list to access add or remove connection options. ## To remove a power connection select
*Remove*. ## To add a connection select *Add...* and in the *Add Outlet Connection* screen, select between available rack PDU and phase
options. ||See also|| [Asset Management]
Deleting Equipment
{excerpt:hidden=false}The View screen, accessed from the *Asset Management* option on the main screen, allows you to view equipment in the
data center and access edit options to delete equipment.{excerpt} # Select *Asset Management* on the main screen to open the View screen and
navigate to the item that you want to delete. ## Select a room to view the racks within that room by double-clicking (or by tapping, holding, and
selecting *Open...*). ## Select a floor-mounted item such as UPS, PDU, or cooling unit to access details by double-clicking (or by tapping,
holding, and selecting *Open...*) to access details. ## Select a rack to view the equipment in that rack by double-clicking (or by tapping, holding,
and selecting *Open...*.). ## Select a piece of equipment in a rack by double-clicking a rack (or by tapping, holding, and selecting *Open...*.) to
access equipment details. # Select *Delete* in the bottom menu. {tip:icon=false}*Note*: You are always asked to confirm that you want to perform
the deletion. Deleting a piece of equipment removes it completely from the system. You cannot retrieve a deleted item.{tip} Although you cannot
retrieve a deleted item, all actions including deletes performed through {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} are
listed in the {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} application *Audit Trail* report. [More...|Audit Trail report] ||See
also|| [Asset Management]
*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]
A * Rack 2 is powered by UPS B * An alarm is triggered on UPS A * Virtual Machine Manager migrates the virtual machines from hosts in Rack 1
to hosts in Rack 2 that is powered by UPS B {column}{column:width=50%} !systemoverview.png|thumbnail! {column}{section} || See also|| [Initial
Setup of StruxureWare Operations PRO Pack] [Working with StruxureWare Operations PRO Pack]
Working with StruxureWare Operations PRO Pack views in System Center Operations
Manager
{excerpt:hidden=false}When the {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} has been imported and configured in
System Center Operations Manager, a {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} folder with two views will be
available.{excerpt} # In *Monitoring*, select {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} and observe the two views
listed. # Click {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} and observe the view open with a
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} list view and a *Detail View*.
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} servers that have been set up to communicate with the System Center
Operations Manager server appear in the list.\\ \\ {tip:icon=false}*Note*: These servers appear as Not monitored in this view. However, this does
not mean that the virtual machine hosts are not monitored. It means that the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} server itself is not monitored by System Center Operations Manager.{tip} #
Click a list item and observe the details for the selected item. # Click *Impacted Virtual Machine Hosts* and observe the view open with an
*Impacted Virtual Machine Hosts* view and a *Detail View*. Impact analysis data from the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} servers appears in this view. # Click a list item and observe the details for
the selected item. # Right-click *Impacted Virtual Machine Hosts*, and select *Personalize view...* Then select the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} data that you want to display in Virtual Machine Manager, such as *Room
Name*, *Rack Name*, etc. {tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup may look a little different
from the instructions and images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.{tip}
||See also|| [StruxureWare Operations - PRO Pack]
Working with StruxureWare Operations PRO Pack PRO Tips in Virtual Machine Manager
{excerpt:hidden=false}The {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} PRO tips are communicated to Virtual
Machine Manager. You can manually implement the PRO tips, or set up the system to automatically do so. {excerpt} Before you can work with the
PRO tips, you must configure how they should be enabled in the Virtual Machine Manager Administrator Console. In *Administration*, click
*General*, and then click *PRO Settings*, and select *Automatically implement PRO tips* if you want the system to automatically implement the
critical PRO tips. Or if you want the PRO settings to apply to a host group or cluster, in *Hosts* or *Virtual Machines*, right-click the group or
cluster and select *Properties* *> PRO*.\\ {tip:icon=false}*Note*: The option for the system to receive PRO tips of severity level *Critical Only* or
*Warning and Critical* does not have any effect on {multi-excerpt-include:pageTitle=Branding|name=ISXOPRO|nopanel=true} PRO tips as only
impacts of severity level of critical are received.{tip} # Click *PRO Tips* in the toolbar to open the *PRO Tips* window to view active PRO tips for
the host groups that you are administering. # Select the PRO tip, and review the details about the issue that caused the PRO tip and how to
resolve the issue. # Click *Implement* to implement the recommended action to resolve the issue, or click *Dismiss* to remove the tip and close
the *PRO Tips* window. If you have configured the PRO tips to be automatically implemented, the issues are automatically resolved and the PRO
tips are removed. You can troubleshoot any issues with discovery, monitoring or recovery in the Event Viewer Application log.
{tip:icon=false}*Note*: If you are integrating with Virtual Machine Manager 2012, your setup may look a little different from the instructions and
images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.{tip} ||See also||
[StruxureWare Operations - PRO Pack]
return to the Welcome page. You now have the initial setup and are ready to start configuring the data to be shown on the dashboard and the look
and feel. ||See also|| [Configuring StruxureWare Operations KPI tabs and portlets] [Configuring the dashboard theme] [Configuring a tab slide
show on the dashboard]
version. It could be the Liferay server or another computer. # Open Mozilla Firefox on this computer. # Type the Liferay dashboard address
(http://dashboard_server_ip:8080} into the browser address bar. # Press F11 to allow the browser to take up the full screen. At any time, press
F11 again to toggle full screen on/off. # Set the display options: \\ [Configuring a tab slide show on the dashboard] [Hiding the welcome page on
the dashboard] [Hiding the tool icons on the dashboard] [Hiding the cursor on the dashboard] ||See also|| [Configuring the initial setup of the
StruxureWare Operations - Dashboard]
suited for browsing the data center in a top-down manner: * Get all rooms * Get all racks and other floor-mounted equipment in a particular room *
Get the equipment in a rack along with some basic properties (label, barcode, u-height,...) A typical use case could be a mobile application that
will list the rooms, allow the user to drill down to one of the rooms, further drill down to a rack in the room, etc. Each web service call provides
keys for the equipment returned that can then be supplied to the next call in either the inventory web service or in some of the more specialized
web services, such as custom properties, simulate impact, or performance history. The inventory web service is the most obvious entry point into
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. See a complete list of inventory web service call snippets [here|Inventory
web service calls] or follow the links in the below text to look up a specific web service call. {composition-setup} h2. {toggle-cloak:id=WSRooms}
Rooms {cloak:id=WSRooms} In {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}, you operate with different types of rooms: *
server rooms * electrical rooms * store rooms You typically want to access data from the server rooms. To get this data, use
[{{getAllServerRooms}}|Inventory web service calls#F2.1] with no arguments. It returns all server rooms. Similar methods exist to get the other
kinds of rooms: * {{getAllElectricalRooms}} returns all electrical rooms * {{getAllStorages}} returns all storages * {{getAllRooms}} returns all three
kinds of rooms {cloak} h2. {toggle-cloak:id=WSRows} Rows {cloak:id=WSRows} A row is an optional level between rooms and racks. If you are
working with a big room, you can group by rows to get an overview. {{getRowsInRoom}} takes the key of a room and returns the rows in the room.
Read more [here|Inventory web service calls#F2.3] and [here|Inventory web service calls#F2.4]. {cloak} h2. {toggle-cloak:id=WSRacks} Racks
{cloak:id=WSRacks} {{getRacksInRoom}} takes the key of a room and returns all racks in the room. Read more [here|Inventory web service
calls#F2.5] and [here|Inventory web service calls#F2.6]. Similarly, {{getRacksInRow}} takes the key of a row and returns all racks in the row.
{cloak} h2. {toggle-cloak:id=WSFlooreq} Other floor-mounted equipment {cloak:id=WSFlooreq} You can use these methods to get typical kinds of
floor-mounted equipment: * UPS: {{getUpsInRoom}} * PDUs: {{getPdusInRoom}} * Power Panels: {{getPowerPanelsInRoom}} * Remote
Distribution Panels (RDPs): {{getRemoteDistributionPanelsInRoom}} * InRow and downflow coolers: {{getCoolersInRoom}} {cloak} h2.
{toggle-cloak:id=WSEqinracks} Equipment in racks {cloak:id=WSEqinracks} You can use these methods to get typical kinds of equipment in
racks: * Servers: {{getServersInRack}} or {{getServersInRoom}} * Blade enclosures: {{getBladeEnclosuresInRack}} * Rack PDUs:
{{getRackMountPdusInRack}} For example, to get the servers in a particular rack, use {{getServersInRack}}. Read more [here|Inventory web
service calls#F2.7] and [here|Inventory web service calls#F2.8]. NOTE: Blades are not considered servers in this regard. Instead, you must
retrieve the blade enclosures and then get the blades from them. Read more [here|Inventory web service calls#F2.6]. {cloak} h2.
{toggle-cloak:id=WSBlades} Blades {cloak:id=WSBlades} You can use these methods to get blades: * Get all blades in a room:
{{getBladesInRoom}} * Get all blades in a blade enclosure {{getBladesInEnclosure}} Read more about how to get blade enclosures
[here|Inventory web service calls#F2.4]. For example, to get the blades in a particular blade enclosure, call {{getBladesInEnclosure}}. Read more
[here|Inventory web service calls#F2.9] and [here|Inventory web service calls#F2.10]. {cloak} h2. {toggle-cloak:id=WSGeneraldcitems} General
data center items {cloak:id=WSGeneraldcitems} In some cases, you might want to get a particular item without knowing exactly what type it is or
where to look for it. {{getDataCenterItems}} takes one or more keys for items that may be of different types. Read more [here|Inventory web
service calls#F2.11]. It returns the items in the order corresponding to the keys. Read more [here|Inventory web service calls#F2.12]. {cloak} ||See
also|| [Inventory web service calls] [Inventory By Filter Web Service] [StruxureWare Operations Web Service API]
{cloak} h2. {toggle-cloak:id=WSCombi} Combinations {cloak:id=WSCombi} You can combine filters into new filters with negations, conjunctions
and disjunctions. You can combine these, in turn, into new filters, and so forth. Arbitrary nesting is supported as illustrated as shown
[here|Inventory by filter web service calls#F3.13]. *Negation* A negation gives all equipment that does *not* match a certain filter. To get e.g. all
equipment without a particular tag, make a call as shown [here|Inventory by filter web service calls#F3.10]. The {{not}} tag can contain the same
things as the filter tag. A negation in itself might not be useful since it may yield a large amount of (irrelevant) equipment. It typically makes more
sense to put it in a conjunction to further limit the result. *Conjunctions* A conjunction gives all equipment that matches all of one or more filters.
See how to get all PowerEdge 2600 servers tagged "foo" [here|Inventory by filter web service calls#F3.13]. *Disjunction* A disjunction gives all
equipment that matches any of one or more filters. See how to get all equipment that is either a PowerEdge 2600 or has the tag "foo" or both
[here|Inventory by filter web service calls#F3.12]. {cloak} ||See also|| [Inventory by filter web service calls] [Inventory Web Service] [StruxureWare
Operations Web Service API]
service|http://dcimsupport.apc.com/ws-javadoc/index.html?com/apc/webservice/customproperty/v2/CustomPropertiesWebService.html] is a
separate web service for performance reasons and to avoid expanding the inventory web service. The starting point for accessing custom
properties is the key of the equipment. To get the key, use the [Inventory web service|Inventory Web Service] and [Inventory by filter web
service|Inventory By Filter Web Service]. {composition-setup} h2. {toggle-cloak:id=WSReading} Reading {cloak:id=WSReading} You can use the
{{getCustomProperties}} method to get the custom properties for a particular data center item. If you need the custom properties for several items,
it might be faster to batch them into one call. The method {{getCustomPropertiesForMultiple}} accepts the keys of multiple items and returns their
custom properties in the order corresponding to the order of the keys. The method {{getCustomPropertiesIn}} takes the key of a room and returns
all custom properties for all equipment in this room. The method {{getAllCustomProperties}} returns all custom properties for all equipment
altogether. Only call this method for small solutions or when custom properties are used sparingly. {cloak} h2. {toggle-cloak:id=WSModifying}
Modifying {cloak:id=WSModifying} Custom properties can also be modified through web services. This is useful for example for batch jobs that
import data from a third party system into custom properties in {multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true}. See
[here|Custom properties web service calls#F5.3] for an example to add or overwrite two custom properties. If you do not use the value element,
you remove the custom property. Read more [here|Custom properties web service calls#F5.4]. As with reading, there is a variant
{{setCustomPropertiesForMultiple}} to add, modify or remove custom properties for multiple items at a time. {cloak} ||See also|| [Custom
properties web service calls] [StruxureWare Operations Web Service API]
1319018544145 42.0
Troubleshooting
{excerpt-include:Troubleshooting error messages} {excerpt-include:Troubleshooting performance issues} {excerpt-include:Troubleshooting
virtualization issues} {excerpt-include:Troubleshooting scan problems} {excerpt-include:Troubleshooting operational problems}
{excerpt-include:Troubleshooting logon problems} {excerpt-include:Troubleshooting connection and synchronization problems}
{excerpt-include:Troubleshooting why Capture Index values do not display} ||See also||
{contentbylabel:labels=troubleshooting|showLabels=false|space=@self|showSpace=false|spaces=@self}
Video Tutorials
{panel:borderWidth=0|bgColor=9FAOA4}h2. Getting Started Take a quick tour of the application and get started with the basics and more
advanced features by watching these short video tutorials. {panel} {section}{column:width=50%} TIP: For optimum quality, select to watch the
video full screen and ensure the highest quality has been selected in the bottom right corner of the video (YouTube setting). {column}
{column:width=50%} !youtube_changequality_icon.png|thumbnail! {column} {section} {composition-setup} h1. {toggle-cloak:id=CPM} *Working
White Papers
Error: The XML content could not be parsed. There is a problem at line 2, column 143. Parser message: Unexpected character '=' (code 61);
expected a semi-colon after the reference for entity 'Query_Type' at [row,col {unknown-source}]: [2,143]
Write to us
h5. Contact the documentation team directly and provide us with your feedback by filling out this form. Your feedback is highly appreciated in our
attempt to improve the help that we provide. Use the form when you want to contact the documentation team directly or write to
!feedbackmail.png!. You are also welcome to comment, make a request, or ask questions directly on a page by clicking Add Comment at the
bottom of the page. Use this option when you want to share your comment with everybody as it will be visible to everybody viewing the page.
{mail-form:id=documentationFeedback} {mail-input:type=hidden|name=subject|vtlValue=Documentation feedback #if($user) from
$!user.fullName#end} {mail-input:type=hidden|name=confUser|vtlValue=$!user.name}
{mail-input:type=hidden|name=URL|vtlValue=$req.requestURL#if($req.queryString)?$req.queryString#end} || Contact Name |
{mail-input:type=text|name=contactName|cssStyle=width: 170px|vtlValue=$!user.fullName|required=true} | || Contact Email |
{mail-input:type=text|name=contactEmail|cssStyle=width: 100%|validation=email|vtlValue=$!user.email|required=true} | || Contact Address |
{mail-textarea:name=contactAddress|cssStyle=width: 300px; height: 120px}{mail-textarea} | || Your Schneider contact |
{mail-input:type=text|name=schneiderContact|cssStyle=width: 170px;}| || Your question/comment | {mail-textarea:name=desc|cssStyle=width:
600px; height: 320px|required=true}{mail-textarea} | {mail-submit:Submit} {mail-success:render=wiki} {tip:title=Feedback submitted}Thank you for
taking the time to write to us.{tip} {mail-success} {mail-form}
Glossary
{excerpt:hidden=false}This overview lists data center related glossary terms.{excerpt} h2. Block {anchor:block} A block in the room layout
represents a section over which cables and cooling lines cannot be routed (such as a support column). h2. Capacity Group {anchor:capgroup}
Capacity groups allow you to group your equipment, placing it in groups of racks with similar power capacity requirements. Grouping your racks in
capacity groups with similar racks will help you plan and manage the capacity and prevent failure. h2. Capture Index (CI) {anchor:ci} Unit of
measurement used to measure how much exhaust airflow of a rack is captured by the cooling units included in that rack's equipment cluster.
*Cold Aisle Capture Index (CACI)*: The cold aisle capture index is defined as the fraction of air ingested by the rack that originates from local
cooling resources (e.g. perforated floor tiles or local coolers). *Hot Aisle Capture Index (HACI)*: The hot aisle capture index is defined as the
fraction of air exhausted by a rack that is captured by local extracts (e.g. local coolers or return vents). Based on these airflow patterns, the
system calculates the following cooling values: Inlet temperature, Exhaust temperature, Estimated heat loss. The cooling values can be seen by
selecting the Cooling tab in the Floor Layout, and hovering over a rack to see the tool tip. h2. Cluster {anchor:cluster} When used in connection
with cluster environment, cluster is used as follows: {quote} A *computer cluster* is a group of linked
[computers|http://en.wikipedia.org/wiki/Computer], working together closely thus in many respects forming a single computer. The components of
a cluster are commonly, but not always, connected to each other through fast [local area
networks|http://en.wikipedia.org/wiki/Local_area_network]. Clusters are usually deployed to improve performance and availability over that of a
single computer, while typically being much more cost-effective than single computers of comparable speed or availability. {quote} Source:
[Wikipedia. Wikimedia Foundation, Inc. 5 May 2011|http://en.wikipedia.org/wiki/Computer_cluster] When used in connection with cooling, cluster
is used as follows: An equipment cluster is two nearly-equal-length rows of equipment separated by a hot or cold aisle. A row of equipment can be
a member of one or two clusters. h2. Cubic Feet per Minute (CFM) {anchor:cfm} Unit of measurement used to measure the airflow of a cooling
unit. h2. Data Set {anchor:dataset} This term is used in {multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. A data set is a
collection of data. You can combine data from various data sets to make your custom report design. The data sets that have been exposed from
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} are available in
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. h2. Data Source {anchor:datasource} This term is used in
{multi-excerpt-include:pageTitle=Branding|name=DCI|nopanel=true}. A data source is used for connecting to the database to get the requested
data. h2. Distribution Redundancy {anchor:distrredundancy} A type of redundancy setup in which the power source is not redundant, only the
power distribution in the form of redundant rack PDUs. Distribution redundancy does not provide as much security as the full redundancy setup at
power source level (redundant UPS), because even if a server is connected to different Rack PDUs, the UPS remains the single point of failure. In
the system, you can come across these variations: DN and DN+1, see these explained in the Redundancy section. h2. Estimated Downstream
Load {anchor:estdownstream} The *Estimated Downstream Load* value identifies how much capacity the selected piece of equipment (UPS,
PDU, RDP, Power Panel) needs from its power supply to distribute the power you plan to the connected equipment. This value is the sum of the
estimated load of the connected equipment, i.e. the sum of what has been set per piece of equipment in *Properties > Power > estimated load*
value. h2. Gap {anchor:gap} A gap icon in a room layout represents a section over which cables and cooling lines can be routed (such as a
walkway or ramp). h2. Group's Planned Average Load {anchor:plannedavg} The planned average load per rack in a capacity group. This setting
can be accessed by right-clicking a rack and selecting *> Properties > Capacity > Average estimated load (per rack)*. It identifies the estimated
load allowed on average for racks that are included in the capacity group. Some racks are allowed to draw up to peak value, but this will cause
other racks to be allowed to draw less than the average value. It is displayed in the *Capacity Summary* above the racks in the layout, when
\*Rack Layout* is selected with the \*Power Details* view active. h2. Group's Planned Peak Load {anchor:plannedpeak} The planned peak load
value identifies the maximum load that is allowed for any rack included in the capacity group. It is displayed in the Capacity Summary above the
racks in the layout, when Rack Layout is selected with the Power Details view active. A well-balanced planned peak and planned average power
draw ratio will help you plan an even load in all racks and avoid stranded capacity. h2. High Availability {anchor:highavail} High Availability
enables you to run the application in a clustered environment with multiple servers for improved performance. You must have a Cluster Node
license for each node in a cluster setup. h2. Key Performance Indicator (KPI) KPI is a business term used for critical data collected to measure
the success of a business. When you use software supporting KPI trending, it enables you to identify areas of improvement to most efficiently
spend resources where they are needed the most. h2. Local Mode {anchor:localmode} When using the
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}, you can work in either local or server mode. Local mode means that you
are working in a local copy. It does not require that you have network connection and your changes will not be updated in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client application until it is synchronized. The
{multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true} will also only receive changes made by other users when synchronized. h2.
Measured Average Load {anchor:measavg} The measured average load per rack. The measured average value is measured over a specified
period of time, and will be affected by any changes to the load in that period, e.g. due to equipment being switched off for maintenance. h2.
Network Communication Endpoint {anchor:netwendpoint} Equipment that is not network gear as such, rather equipment that is connected to a
network, such as a server or PDU. h2. Network Gear, Layer 1, 2, 3 {anchor:netwgear} Equipment dedicated to dealing with network, e.g.
switches, routers, patch panels, etc. * Layer 1: Non-powered non-intelligent network equipment, e.g. a patch panel. * Layer 2: Powered
non-intelligent network equipment, e.g. a hub. * Layer 3: Powered intelligent network equipment, e.g. a switch or router. h2. Network
Redistribution Point {anchor:netwredistr} Network gear, such as routers and switches. h2. Node {anchor:node} When used in connection with
licenses, such as the {multi-excerpt-include:pageTitle=Branding|name=ISXCPM|nopanel=true} license, a node is a rack supported by the license.
You must buy a license covering as many racks as you want supported (10, 100, etc.). When used in connection with cluster setup, a node is a
single server that is part of a distributed installation with multiple servers. You must buy a license per additional node added to the cluster setup.
h2. Partial loading {anchor:partload} Partial loading means that the system only loads active parts of the application (rooms, etc. on demand).
Because the system does not need to load the entire data center model all the time, performance is increased significantly. h2. Perspective
{anchor:persp} A perspective is a collection of views in a window. The active perspective is indicated by the selected element in the toolbar.
Available perspectives are Operations, Analytics Reports and, depending on the installed add-on modules, possibly more, e.g. Planning Work
Orders ({multi-excerpt-include:pageTitle=Branding|name=ISXCHM|nopanel=true} feature). h2. Phase Balancing {anchor:phasebalance} Phases
are also referred to as L1, L2, L3. If the load of equipment is distributed on more than one phase, make sure the load is distributed evenly on all
phases in a Capacity Group to obtain an optimum solution. The configuration of phases is done in the Properties. h2. Plenum {anchor:plenum} A
pocket of space used for air distribution below a raised floor or above a suspended ceiling. h2. Power Buffer {anchor:pwbuffer} When doing
capacity planning, some racks are allowed to draw up to peak value, but this will cause other racks to be allowed to draw less than the average
value. This means that the maximum additional load that can be added to a rack equals the *Remaining Power* and *Power Buffer*. In line with
the group's *Reserved Power* being utilized, the *Power Buffer* will decrease. h2. Power Feed {anchor:pwfeed} This term is used in connection
with a redundant configuration where one UPS is referred to A feed and the other as B feed. h2. Redundancy {anchor:redund} The provision of
multiple interchangeable components to perform a single function in order to cope with failures and errors, e.g. the setup of more power supplies
to reduce the risk of failure of the entire system in case one of them fails. You may come across these terms in connection with redundancy in the
system: Power redundancy: * N: No redundancy. * N+1: One UPS with one redundant power module (also referred to as internal redundancy in
the UPS Power properties page). If the UPS fails, there is no redundant UPS serving as backup, but if one of the power modules inside the UPS
fails, the redundant module ensures that the UPS still has full capacity. In other words, the spare power is at least equal to the capacity of one
system module. * N+2: One UPS with two redundant power modules (also referred to as internal redundancy in the UPS Power properties page).
If the UPS fails, there is no redundant UPS serving as backup, but if one or two of the power modules inside the UPS fail, the redundant modules
ensure that the UPS still has full capacity. In other words, the spare power is at least equal to two system modules. * 2N: Two UPS where one
serves as backup for the other in case one of them fails. One UPS is referred to as A feed and the other as B feed. * 2N+1: This is a combination
of N+1 and 2N for combined external and internal redundancy, both one redundant UPS and one redundant power module inside both UPS. *
2N+2: This is a combination of N+2 and 2N for combined external and internal redundancy, both one redundant UPS and two redundant power
modules inside both UPS. * DN: This is a combination of D (distribution redundancy) and N (above). For this type of redundancy, the power
distribution is redundant but there is no redundancy on the UPS level. Therefore, you are still vulnerable to failure on the power supply. * DN+1:
This is a combination of D (distribution redundancy) and N+1 (above). For this type of redundancy, the power distribution is redundant and there is
internal redundancy on the UPS level (one UPS with one redundant power module). Cooling redundancy: * N: There are no redundant cooling
units for the rack. There are one or more coolers in the data center. If ONE cooler fails anywhere in the data center, it would result in inadequate
cooling (yellow or red CI). * N+1: There is one redundant cooling unit for the rack. ONE cooler (CRAC, row-based, or OA unit) can fail anywhere in
the data center and cooling will still be adequate (green CI). * N+2: There are two redundant cooling units for the rack. TWO coolers (CRACs,
row-based, or OA units) can fail anywhere in the data center and cooling will still be adequate (green CI). * N+x: There are x redundant cooling
units for the rack. X coolers (CRACs, row-based, or OA units) can fail anywhere in the data center and cooling will still be adequate (green CI).
h2. Remaining Power {anchor:remainpw} The *Remaining Power* value identifies how much power capacity remains in the rack without
exceeding the allowed average load that you planned for the racks in the active capacity group. It is displayed in the *Capacity Summary* above
the racks in the layout, when *Rack Layout* is selected with the *Power Details* view active. h2. Reserved Capacity {anchor:reserved} The
*Reserved Capacity* value identifies how much capacity the selected piece of equipment (UPS, PDU, RDP, Power Panel) needs from its power
supply to distribute the power you plan to the connected equipment. This value is the sum of the estimated load of the connected equipment, i.e.
the sum of what has been set per rack in a capacity group in *Properties > Capacity > estimated load*. h2. Server Mode {anchor:servermode}
When using the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}, you can work in either local or server mode. Server mode
means that you are working in the database on the server, and any saved changes will immediately be updated in the
{multi-excerpt-include:pageTitle=Branding|name=ISXO|nopanel=true} client application as well. Any changes made by other users will also be
instantly reflected in the {multi-excerpt-include:pageTitle=Branding|name=ISXM|nopanel=true}. h2. Stranded Capacity {anchor:stranded} Capacity
that cannot be utilized by IT loads due to the design or configuration of the system. The presence of stranded capacity indicates an imbalance
between two or more of the following capacities: Floor and rack space, Power, Power distribution, Cooling, Cooling distribution. h2. Tags
{anchor:tags} Tags are category labels that can be created and assigned to equipment in the floor or rack layout to group equipment. Tags can be
used to help plan the best place for new equipment automatically. h2. Temperature Map {anchor:tempmap} A color map showing the temperature
in different parts of a room. The temperature map is 3-dimensional with movable planes. h2. Temperature Plane {anchor: tempplane} The
temperature plane is a movable plane (vertically and horizontally) that shows a color-coded cross section of the temperature in the room. h2.
Unreserved Capacity {anchor:unreserv} The unreserved capacity value identifies how much remaining power there is for the selected PDU, RDP,
or Power Panel. That means that this value does for instance not take into account that other power distribution units may reduce the actual
value. h2. Velocity Plane {anchor:velplane} The velocity plane is a movable plane (vertically and horizontally) that shows a color-coded cross
section of the airflow vectors in the room. h2. Wizard {anchor:wizard} A wizard leads you through dialog steps. h2. Work Order {anchor:worder} A
work order contains tasks. A list of work orders can be created in the system, listing what actions need to be executed in the data center, e.g.
installing new servers in specific positions.
Index
{index}