dctrack implementation & integration...

Copyright © 2013 Raritan, Inc.

dcTrack-Implementation-Integration-0A-v3.0.0-E

February 2013

255-80-0023-00

dcTrack Implementation & Integration Guide

Implementation & Integration Guide 3.0.0

This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated into another language without express prior written consent of Raritan, Inc.

© Copyright 2013 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.

FCC Information

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a commercial installation. This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential environment may cause harmful interference.

VCCI Information (Japan)

Raritan is not responsible for damage to this product resulting from accident, disaster, misuse, abuse, non-Raritan modification of the product, or other events outside of Raritan's reasonable control or not arising under normal operating conditions.

If a power cable is included with this product, it must be used exclusively for this product.

iii

Contents

Chapter 1 Introduction 1

Intended Audience ......................................................................................................................... 1 About this Guide ............................................................................................................................ 2 Professional Services, Customer Support and Training ................................................................ 3 Related Documentation ................................................................................................................. 3

Chapter 2 First Time Installation of dcTrack 4

Overview ........................................................................................................................................ 5 Planning and Assessment ............................................................................................................. 6

Spreadsheet Templates ...................................................................................................... 6 Drawing File Templates ....................................................................................................... 8 Implementation Planning Considerations ............................................................................ 9 Determining the Data Collection Scope............................................................................. 11

Install dcTrack & Build the Data Center Model ............................................................................ 12 Preparing to Install dcTrack ............................................................................................... 12 Virtual Machine Recommendations ................................................................................... 13 Client Requirements and Supported Software .................................................................. 13 Installation Steps ............................................................................................................... 15 Build Your Data Center Model in dcTrack ......................................................................... 25

Begin Using dcTrack .................................................................................................................... 61

Chapter 3 Integrating dcTrack 62

Overview ...................................................................................................................................... 62 Integrating an Existing dcTrack Installation with a New Power IQ Installation ............................ 63

dcTrack 2.2 Users.............................................................................................................. 63 dcTrack 2.4 Users.............................................................................................................. 63 dcTrack 2.5 (and Later) Users ........................................................................................... 73

Integrating an Existing Power IQ Installation with a New dcTrack Installation ............................ 80 Checklist - Existing Power IQ Installation with a New dcTrack Installation ....................... 81 Change the Web Session Timeout for Power IQ .............................................................. 82 Back Up Your Power IQ Database .................................................................................... 82 Upgrade to the Current Version of Power IQ .................................................................... 82 Import Power IQ Data into dcTrack ................................................................................... 83 Install dcTrack .................................................................................................................... 87

Integrating an Existing dcTrack Installation with an Existing Power IQ Installation..................... 87 Checklist - Existing dcTrack Installation with an Existing Power IQ Installation................ 88 Change the Web Session Timeouts in Power IQ and dcTrack ......................................... 89 Back Up Your Power IQ and dcTrack Databases ............................................................. 89 Upgrade to the Current Versions of Power IQ and dcTrack .............................................. 90 Import Power IQ Data into dcTrack ................................................................................... 91

Contents

iv

Add Remaining dcTrack Items to Power IQ ...................................................................... 95 Integrating dcTrack with AMS via EMX or PX2 ........................................................................... 97

Overview ............................................................................................................................ 97 EMX Asset Sensor Management ...................................................................................... 99 PX2 Asset Sensor Management ..................................................................................... 112

Appendix A dcTrack Architecture and Data Model 121

dcTrack Architecture .................................................................................................................. 122 dcTrack Data Model ................................................................................................................... 123

Appendix B Interfaces and Terminology 124

dcTrack Interfaces ..................................................................................................................... 124 dcTrack Terms ........................................................................................................................... 124

Location ........................................................................................................................... 124 Items ................................................................................................................................ 124 Ports ................................................................................................................................ 128 Circuits ............................................................................................................................. 129

Appendix C Drawing File Preparation and Best Practices 130

Overview .................................................................................................................................... 130 Optional Drawing Feature Requirements .................................................................................. 131

Drawing Cable Routes Option ......................................................................................... 131 Drawing Raised Floor Grid Labeling Option .................................................................... 135 Drawing Perforated Tiles (PT) ......................................................................................... 136

Contents

v

Drawing File Good Practices ..................................................................................................... 138 Visio-to-AutoCAD Export Rules ................................................................................................. 139

Appendix D Spreadsheet Import Requirements and Recommendations 142

Overview .................................................................................................................................... 142 Best Practices when Using Import Wizard................................................................................. 142 General Spreadsheet Requirements ......................................................................................... 143 Cabinet Import Requirements .................................................................................................... 144 Item Import Requirements ......................................................................................................... 145 Power Circuit Import Requirements ........................................................................................... 146 Data Circuit Import Requirements ............................................................................................. 147 Custom Field Import Requirements ........................................................................................... 148 Blade Chassis and Blade Import Requirements ........................................................................ 149 Virtual Machine Import Requirements ....................................................................................... 150

Appendix E Adding Data Using the Import Wizard or Manually 151

Overview .................................................................................................................................... 151 Import Data Center Items Process Flow .................................................................................... 152 Importing Items Using the Import Wizard .................................................................................. 153

Using the Import Wizard .................................................................................................. 153 Manually Adding Items in dcTrack ............................................................................................. 170 Important Maintaining Data Once dcTrack and Power IQ are Synched .................................... 170

Index 171

1

In This Chapter

Intended Audience ..................................................................................... 1 About this Guide ........................................................................................ 2 Professional Services, Customer Support and Training ........................... 3 Related Documentation ............................................................................. 3

Intended Audience

This guide is intended for use by Raritan customers and Raritan Solution/Implementation Partners who are deploying, installing or integrating dcTrack™.

Chapter 1 Introduction

Chapter 1: Introduction

2

About this Guide

This guide outlines the following:

The steps that must be taken before you install the application

Performing a first time, clean install of dcTrack

Information on building your data center model in dcTrack after a clean install

An overview of next steps following a successful dcTrack implementation

Steps to upgrade dcTrack, as well as integrate dcTrack and Power IQ (if applicable)

High-level information on the dcTrack™ application architecture and data model

Review First Time Installation of dcTrack (on page 4) if you are performing a 'clean install' of dcTrack, meaning you are not currently using dcTrack, or integrating dcTrack and Power IQ.

Review Integrating dcTrack (on page 62) if you are:

Integrating an Existing dcTrack Installation with a New Power IQ Installation (on page 63)

Integrating an Existing Power IQ Installation with a New dcTrack Installation (on page 80)

Integrating an Existing dcTrack Installation with an Existing Power IQ Installation (on page 87)

Integrating dcTrack with AMS via EMX or PX2 (on page 97)

Integration steps vary from one integration scenario to another, so follow the steps that are specific to your integration needs. If you are unsure of the steps to follow, contact Raritan Technical Support.

Important: Raritan strongly suggests you read through the steps that apply to your dcTrack integration needs before you begin an integration.

Chapter 1: Introduction

3

Professional Services, Customer Support and Training

Raritan offers a Quick Start service that includes help deploying dcTrack™, as well as a full day of training at your location. Contact Raritan for more information about purchasing this service.

Raritan Customer Support provides support information on installing dcTrack, as well as addressing technical support issues you may encounter. Additionally, Customer Support provides you with the license you need to use dcTrack. If you have not already received a license, contact Raritan Customer Support.

Raritan strongly suggests you take our dcTrack training prior to implementing dcTrack and prior to using it. The dcTrack video training course is accessed from www.raritantraining.com http://www.raritantraining.com. You need a Raritan provided username and password to access training, which are acquired through our training website. Once you are verified, Raritan gives you access to the courses.

Related Documentation

In addition to this guide, Raritan provides PDF versions of dcTrack Quick Setup Guides (for application installation and hardware installation), as well as dcTrack Help that is in both online help and PDF format. The is Help is referenced in this guide and should be referred to as indicated. The Quick Setup Guide and Help are available on the Raritan website to licensed customers.

Note: To access the Raritan dcTrack website, you need a valid dcTrack license, and a username and password. Contact Raritan Customer Support for more information.

http://www.raritantraining.com/

4

In This Chapter

Overview .................................................................................................... 5 Planning and Assessment ......................................................................... 6 Install dcTrack & Build the Data Center Model........................................ 12 Begin Using dcTrack ............................................................................... 61

Chapter 2 First Time Installation of dcTrack

Chapter 2: First Time Installation of dcTrack

5

Overview

This section walks you through installing dcTrack™ and then building your data center model in the application. In other words, this is a clean install and you are not currently using another version of dcTrack that need to upgrade, and you are not integrating dcTrack and Power IQ.

There are three stages to a dcTrack initial installation and installation:

Stage 1: Planning and Assessment - The implementation is planned, and the data collection and scope of the implementation are defined

Stage 2: Installation and Implementation - The dcTrack application and database server are installed and the initial data is collected, organized and imported into dcTrack

Stage 3: Begin Using dcTrack - dcTrack is launched as an operational system for data center infrastructure management


6

Planning and Assessment

Spreadsheet Templates

Raritan provides Microsoft Excel® spreadsheet templates that are used to capture data center information. With the exception of the Structured Cable Plant and Power Panel spreadsheets, they can then be imported into dcTrack in order to populate your data center model in the application.

Note: dcTrack does not support .XLSX file formats for Microsoft Excel

2010®.

Complete a template for each item class as part of the data gathering process before you begin to build your data center model dcTrack.

Raritan provides the following spreadsheet templates that can be used to capture data, then import the data into dcTrack using the Import Wizard:

Document Description

01_Items_-_Cabinets_Only_for_3.0.xls

Use to capture cabinet data, then import the spreadsheet data into dcTrack using the Import Wizard

02_Items_-_All_Other_Classes_for_3.0.xls

Use to capture IT, power and environmental items, then import the spreadsheet data into dcTrack using the Import Wizard

04 Power Panels.xls Use to capture power panel information, then import the spreadsheet data into dcTrack using the Import Wizard

05_Connections_-_Communications_for_3.0.xls

Use to capture data connections, then import the spreadsheet data into dcTrack using the Import Wizard

06_Connections_-_Power_for_3.0.xls

Use to power connections, then import the spreadsheet data into dcTrack using the Import Wizard

Raritan also provides the following worksheet is used to capture data, but not to import data:

Document Description

03 Structured Cable Plant.xls Use as a data gathering worksheet to collect structure cabling information


7

Spreadsheet templates and worksheets are downloaded from the Raritan dcTrack Support website. See Downloading Raritan dcTrack Spreadsheet Templates (on page 7).

Note: To access the Raritan dcTrack website, you need a valid dcTrack license, and a username and password. Contact Raritan Customer

Support for more information.

Using Raritan Spreadsheets vs. Your Own Spreadsheets

Raritan recommends using the import spreadsheet templates we provide in order to reduce the amount of manual mapping involved during the import process using the dcTrack™ Import Wizard.

Note: dcTrack does not support .XLSX file formats for Microsoft Excel 2010®.

Alternatively, if you already have a spreadsheet of your own you are using to track the items, you can use your spreadsheet. Make sure your spreadsheet headings match those of Raritan's spreadsheet headings in order to avoid manually mapping spreadsheet column names during the import process. For example, if you use the heading Mdl for the models column in your spreadsheet, the heading must be changed to Models so it matches the Raritan spreadsheet. See General Spreadsheet Requirements (on page 143) for more spreadsheet requirement information.

Whether you use Raritan spreadsheets or your own, review the spreadsheet requirements for formatting requirements. See Spreadsheet Import Requirements and Recommendations (on page 142).

See Downloading Raritan dcTrack Spreadsheet Templates (on page 7) for more information on accessing the Raritan spreadsheets.

Downloading Raritan dcTrack Spreadsheet Templates

To download data collection worksheets:

1. Access Raritan's Support Website link (http://www.raritan.com/support/dctrack/). The Raritan website opens in a browser window.

2. From the Raritan website, login by entering your username and password in the fields provided under the Customer Login section of the page. If you do not have a username and password to access the website, contact Raritan Customer Support (http://www.raritan.com/support/contact-support/).

3. Click Log In. The dcTrack support page opens.


8

4. On the left side of the page under Firmware, Software, and Product Documentation dcTrack, click on the version of dcTrack you are using. The version page opens.

5. Click Import Wizard and Floor Plan Templates to the templates page, then select and download the zip files containing the templates. Save the zip files to the local or network location of your choosing, then unzip and extract the files.

Drawing File Templates

Raritan offers drawing file templates you can download and use to create drawing file renderings of you data center. These files can then be added to dcTrack™ when you create a data center site in the application. See Downloading Raritan dcTrack Drawing File Templates (on page 8) for steps on downloading drawing file templates from the dcTrack Support page.

Both AutoCAD® and Microsoft Visio® templates are available for download. Note that dcTrack requires you to save the drawing files as .DWG files in order to add the application.

For information on drawing file requirements, see:

Step 4: Prepare Drawing Files (on page 38)

Mandatory Drawing File Requirements (on page 39)

Drawing File Preparation and Best Practices (on page 130)

For information on adding drawing files to dcTrack, see Step 6: Create Locations/Link Drawings and Images to the Location (on page 41).

Downloading Raritan dcTrack Drawing File Templates

To download data collection worksheets:

1. Access Raritan's Support Website link (http://www.raritan.com/support/dctrack/). The Raritan website opens in a browser window.



4. On the left side of the page under Firmware, Software, and Product Documentation dcTrack, click on the version of dcTrack you are using. The version page opens.


9

5. Click Import Wizard and Floor Plan Templates to the templates page, then select and download the zip files containing the drawing file templates. Save the zip files to the local or network location of your choosing, then unzip and extract the files.

Implementation Planning Considerations

Implementation planning is critical to a successful implementation and long term use of dcTrack™. Before you start your implementation, you must make a series of decisions about how you will use dcTrack.

Following is a list of things to consider when implementing dcTrack. While complete answers are not required to each question, carefully thinking through each question helps ensure a successful implementation.

Implementation planning considerations

What are your goals with dcTrack?

What problem(s) do you want to solve?

What improvements do you want to make?

How do you define success in using dcTrack?

What Data Center Infrastructure Management functions do you want to address?

What overall functions will dcTrack support?

For example, dcTrack supports functions such asset management, network connectivity, structured cabling connectivity, power chain connectivity, IP address management, and so on. Which of these do you plan to use?

You will need to populate the dcTrack database with the appropriate information for each function.

What is the scope of the data you will manage in dcTrack?

How many data centers will be modeled in dcTrack?

What areas, assets, infrastructure and connectivity of your data center(s) do you plan to model in dcTrack?

Will you start with a subset and expand?


10

Implementation planning considerations

What data will need to be collected and where is that data?

Where is the existing information about your data center assets?

Do you have AutoCAD® and/or Microsoft Visio® floor plan drawings?

Do you have information on your data center assets in spreadsheets, databases or other software systems?

Do you need to survey the data center for missing information?

Who are you dcTrack users?

Who will use dcTrack?

What will their roles be?

Who is the primary administrator(s)?

What are your current processes and do you need to change them when you begin using dcTrack?

What is your process to use dcTrack?

How does it relate to your current processes?

Are any process changes required to use dcTrack?

Who will implement dcTrack?

Are the individuals who will implement the application trained on dcTrack?

Will you require assistance from Raritan or one of our Solution/Implementation Partners to implement dcTrack?

Do you need assistance from other internal organizations to implement dcTrack?

What is your implementation and release schedule?

What is your schedule to implement dcTrack?

When do you plan to commence operations?

Do you have a project plan?

What training will you need?

How will your end users be trained?

Do you require formal training classes?


11

Determining the Data Collection Scope

The scope of your project depends on the amount of data that needs to be collected, and how easily that data can be gathered based on where it is currently stored. Understanding this determines the overall scope of the project and the related effort required to populate dcTrack™.

To do this, you must first understand the dcTrack data model. See dcTrack Data Model (on page 123). You then need to determine what your target data are and what your data sources are.

Target Data

Target data includes:

The number and size of data centers to be managed in dcTrack™

The item classes to be modeled and managed in dcTrack

Note: Item class is the dcTrack term for asset type.

The extent of attributes (database fields) to be managed for every item class in dcTrack

The extent of power connectivity to be managed in dcTrack. For example, connecting a power supply to a rack PDU socket, connecting a rack PDU to an electrical outlet, connecting an outlet to a breaker, the number of panels in floor PDUs/RPP and PDU to UPS, and so on

The structured cabling connectivity to be managed in dcTrack

The network connectivity for the network and the SAN environments to be managed in dcTrack

The IP subnet management and assignment of IP addresses to network interfaces that are managed in dcTrack

Data Sources

Once you identify the target data to be managed in dcTrack™, you need to identify the data sources. Data sources are the places the target data is currently stored. This includes, but is not limited to:

Existing AutoCAD® or Microsoft Visio® drawings of data center floor plans

Note: These drawing files must be saved as .dwg files.


12

Existing spreadsheets

Existing databases or systems from which data can be extracted or exported

Existing documentation such as power chain single line diagrams and other drawings

Data that currently does not exist in any of these formats and must be manually entered into spreadsheets that are imported into dcTrack

Install dcTrack & Build the Data Center Model

Installing dcTrack™ means you are installing the application for the first time. In other words, this is a clean install and you are not currently using another version of dcTrack that need to upgrade, and you are not integrating dcTrack and Power IQ.

Once the application is installed, build your data center in dcTrack.

With the exception building the data center, the steps in this section of the guide can also be found in the dcTrack Quick Setup Guide should you need a more concise reference document that does not include the additional information contained in this guide such as planning and assessment and so on.

Preparing to Install dcTrack

Before you begin an installation:

Review the Virtual Machine Recommendations (on page 13), and Client Requirements and Supported Software (on page 13)

Verify you have the dcTrack™ DVD containing the dcTrack ISO file or download the ISO file from the Raritan website

Contact Raritan Customer Support for a license file if you have not already done so, and save the license file locally so you can retrieve when you add the license

Verify the datastore has 160GB free for a new virtual machine and 3GB free for the installation ISO file. Upload the ISO file to the datastore

Note: The instructions in this guide refer to the vSphere client, which is compatible with ESX/ESXi 4.0 and higher.


13

Virtual Machine Recommendations

Important:

Your dcTrack virtual machine must be given priority

Configure ESXi so that all required resources are available on the dcTrack virtual machine at all times.

Manipulating ESXi settings or changing the priority of other virtual machines running on the same ESXi host may impact the ESXi scheduling policy. If this happens, resources may be diverted from the dcTrack virtual machine resulting in poor performance or dcTrack malfunctioning.

Raritan's minimum recommendations for the dcTrack VMware host configuration:

# of cabinets

# of CPUs

RAM (GB)

Datastore (GB)

CPU (GHz)

VMWare

1- 100 1 3 160* 2.8 ESX/ESXi 4.0, 4.1 or 5.0

101 or more

1 4 160* 2.8 ESX/ESXi 4.0, 4.1 or 5.0

*Note: An additional 3GB of space may be needed to upload the ISO so it can be installed. Alternatively, the ISO can be installed directly from the

DVD.

The following TCP ports must be open when building your virtual machine:

22 - SSH

80 - HTTP

443 - HTTPS

5432 - Postgres DB

Client Requirements and Supported Software

Item Description

Workstation Dual core processor with 2 GHz, 2GB of RAM and 2GB of free disk space

Supported operating systems

Windows 7® operating system or Windows XP® operating system


14

Item Description

Supported browsers

Internet Explorer® 7, 8 or 9

Firefox® 17 and higher for Web Client, or Firefox 3.6.1 to launch Classic View

Note: To use Firefox 1.2.1 or later with dcTrack, Microsoft .NET® Framework Assistant must be installed. The dcTrack prerequisites installer can deploy the add-on as well.

Note: If you are using Firefox running on a Windows 7 operating system, the Windows 7 User Account Control must be set to Never Notify during the installation and can

then be set back.

Adobe® Flash® Player

Version 11.1.102 and later

Microsoft® .NET Framework

Version 3.5

Note: .NET versions are not inclusive of past .NET versions. So, for example, if you are installing .NET 4.0

you must install .NET 3.5 SP1.

Microsoft Paint In order to view model images correctly in Classic View, Microsoft Paint must be set as your default image viewer.

When you launch dcTrack from the dcTrack Web Client, the following software is installed automatically if it does not already exist on your machine. This software can also be re-installed, for example in order to repair issues, by clicking the Prerequisites button in the dcTrack Web Client start page.

Add-ons and database drivers

Microsoft Access® 2003 Runtime

Microsoft Access 2003 Runtime is installed when dcTrack is installed. Microsoft Access Macro Security is set to Low during the installation process. See your Microsoft Access documentation on how to set Macro Security if you wish to change the setting from Low to another level.

Note: Microsoft Access 2007 is not supported.

PostgreSQL ODBC drivers and PostgreSQL ADO drivers

PostgreSQL ODBC drivers and PostgreSQL ADO drivers are required to run dcTrack. If these drivers are not already installed on your machine, they are installed automatically when you launch dcTrack.


15

Add-ons and database drivers

Microsoft Office® file converter pack

If this is not already installed on your machine, it is installed automatically when you launch dcTrack.

dcTrack Classic View supports the following software but are not required in order to use dcTrack.

Supported software

AutoCAD® 2009 or earlier

AutoCAD .dwg files, which can be linked to an existing drawing of a data center floor plan (top view), are supported.

Note: AutoCAD 2010 and 2011 are not supported by dcTrack.

Microsoft Visio® Microsoft Visio is also supported.

Visio drawings must be saved in AutoCAD .dwg file format in order to import them into dcTrack.

Installation Steps

Following is a high-level overview of the dcTrack™ clean install steps:

Step Description

Download the dcTrack application

dcTrack is downloaded from the Raritan website. Note that you must have a login username and password to access the dcTrack page on the website. Contact Raritan Customer Support if you do not have access to the dcTrack page.

Setup the dcTrack virtual machine

Create a vSphere ESX\ESXi 4.x virtual machine.

Configure the dcTrack server

Setup network access to the dcTrack server using the vSphere client’s virtual machine console


16

Step Description

Log in for the first time, install dcTrack licenses and change the Administrator password

Log in to dcTrack for the first time, install the license file in the network installation folder, then change the Administrator password to ensure security

Configure dcTrack user workstations

Install and setup the client workstation via web a browser

Create the dcTrack Virtual Machine

Note: The following virtual machine installation steps are an example of a virtual machine installation. Follow your installation preferences if they

differ from these.

Refer to Virtual Machine Recommendations (on page 13) as needed for information on the number of virtual processors, and the amount of memory allocated for the virtual machine.

To create the virtual machine:

1. Connect to the VMware server using vSphere client. Log in as a user that has permission to create, start, and stop virtual machines.

2. In the Summary tab, click New Virtual Machine in the Command box.

3. Choose Custom. Click Next.

4. Enter a name for the virtual machine. Click Next.

5. Choose a datastore with at least 160GB of free space available for the VM. Click Next.

6. You may need to select the Virtual Machine Version, depending on your host. Select the version. Click Next.

7. Select Linux for the Guest Operating System, then select CentOS 32-bit, if available, from the Version drop-down. If CentOS 32-bit is not available, select Other Linux (32-bit). Click Next.

8. Set the number of virtual processors based on the size of your configuration. Click Next.

9. Adjust the amount of memory allocated for the virtual machine to at least the minimum required. Click Next.

10. Select LSI Logic Parallel for the SCSI Controller. Click Next.


17

11. Select "Create a new virtual disk." Click Next.

12. Set the Disk Capacity 160GB (based on your datastore selection early) and select "Store with the virtual machine". Click Next.

13. Leave all advanced options at default. Click Next.

14. Select the "Edit virtual machine settings before completion" checkbox, then click Continue. The New Virtual Machine - Virtual Machine Properties dialog appears. Select New CD/DVD in the Hardware/Summary panel.

15. In the Device Type section, select the Data Store ISO radio button, then browse and select the datastore containing the ISO file. Click Finish to save drive and return to the main dialog.

16. Click Finish to create the virtual machine.

Load dcTrack onto the Virtual Machine

To load dcTrack™ onto the virtual machine:

1. Select VM and right click Edit Settings.

2. Select Options > Advanced > Boot Options and select Force BIOS Setup.

3. Click "Power on" to power up the virtual machine.

4. Click on "disk" at the top of the console window and select "Connect to ISO image on datastore".

5. Select the datastore

6. Select the dcTrack ISO.

7. Click on the Console tab.

8. Click inside console window,

9. Use the Esc key to get to main BIOS page.

10. Exit the BIOS by selecting Exit Discarding Changes and using the Enter key. The dcTrack Kickstart page opens.

11. Type 2 for a VMware installation and press Enter to begin installation.

12. When the installation completes, disconnect the ISO disk and press Enter to reboot the dcTrack virtual machine. The virtual machine reboots and displays a console prompt.


18

Run the Prerequisite Program (Optional)

When you launch dcTrack™, the application checks the client to make sure it meets the minimum system requirements. If this is the first time you are using dcTrack, you must install the prerequisites program. The prerequisites program installs all of the software required to use dcTrack on your local machine. This includes:



dcTrack shared components

PostgreSQL ODBC drivers

PostgreSQL ADO drivers

To run the prerequisites program:

1. Connect to dcTrack using a web browser on any machine on the network.

2. In the browser's address bar, enter the IP address assigned to dcTrack. For example: http://192.168.1.10

3. Answer yes to any security alerts and accept all certificates.

4. Select Install Prerequisites for Classic View from the Administration menu to download the dcTrackPrereqs.exe file and save it to your machine.

5. Once the program is downloaded, run the dcTrackPrereqs.exe by double-clicking on it.

6. Click Install on the first dialog of the install wizard.

7. Optionally, select the 'Set MC Access security mode to low' on the 'Setting MS Access 2003 security mode' dialog. Click Next.

Note: If you do not set the Microsoft Access security mode to low, dcTrack still works but security warnings are displayed each time you launch dcTrack. You must then answer all questions about blocking unsafe expressions with "No". If you set the security mode to low but want to change to a higher level later, see your Microsoft Access

documentation on how to set Macro Security.

8. If you are using Firefox® as your browser, you must install the Firefox .NET Framework add-on. Check the 'Install Mozilla Firefox .NET Framework assistant add-on' checkbox and click Next.

If you are not using Firefox and are not planning on using it in the future, you do not need to install this add-on.

9. Click Finish on the last dialog. All of the components required to run dcTrack are installed.


19

Initial Configuration of dcTrack

After installing dcTrack™, you must configure the system for access over the network.

To configure the system for access over the network:

1. Access the local port from the Console tab of the VMware Infrastructure Client.

2. When prompted to log in, use the username config and the password raritan. The dcTrack configuration page opens.

3. Select Networking Setup, then select Setup LAN 1 to configure the primary Ethernet port.

4. Press the Space bar to select Enable this LAN Port.

5. To manually assign the network settings to dcTrack, deselect Use DHCP. Type the IP address, network masks, and gateway into the appropriate fields. If using DHCP, note the address. There must be a DHCP server available on the LAN.

6. Select Accept to reset the network interface with the new values.

7. If you are using a second network interface, select Setup LAN 2 from the Network Configuration menu and configure the secondary Ethernet port in the same manner as the first. Optional

8. Select Ping Network Test to ensure that dcTrack can communicate over the network. Optional

9. Setup the Name Servers under Network Configuration. If you do not setup the Name Server, DNS names cannot be resolved. Optional

10. In order to increase the secure access to dcTrack, it is advisable to disable SSH remote access to dcTrack. To disable SSH remote access to dcTrack, select System Services. Deselect Enable SSH. By default, the config account has access to dcTrack. SSH is re-enabled if a support connection is created. Optional

11. Select Exit from the main menu. You can now access dcTrack from any client on the network.


20

Log In to dcTrack for the First Time

dcTrack™ supports the Windows 7® and Windows XP® operating systems, as well as the Internet Explorer® and Firefox® browsers.

If you are using Firefox running on the Windows 7 operating system, additional steps must be taken the first time you log in.

The first time you log in to dcTrack, you download dcTrack licenses. The steps outlined in this section walk you through the license installation. If you do not have a license, go to http://www.raritan.com/licensing. You need a username and password to access the Software License Key Management page. Contact Raritan Customer support if you do not have this information.

This information covers logging in to dcTrack for the first time. Once all licenses and necessary add-ons are installed, the majority of steps do not need to be repeated.

Default Login Information

Use the following default login information the first time you login to dcTrack™.

Login information Default

Username admin

Password raritan

IP address As defined by you

Internet Explorer Users

To log in using Internet Explorer:

1. In the browser's address bar, enter the IP address or name assigned to dcTrack™.


3. The first time you access dcTrack, the Licensing page opens. Log in to the page.

a. Click Add, then select your dcTrack license file. Licenses are .LIC files. Repeat this step to add incremental licenses if needed.


21

Note: Your license file can be retrieved from the Raritan website after you have activated your registration. To activate your registration, click the link in the "Thank you for registering" email from Raritan and create your user account. Once you create your account, look for a "Your Raritan software license key is available" email containing a link to your license file download page.

b. Click Continue. If you see error messages and the Continue button is disabled, contact Raritan Technical Support. There may be a problem with your license file.

c. Select 'I agree' for the End User License Agreement and click Submit.

4. Log in to dcTrack with the default username admin and password raritan. The dcTrack Web Client Dashboard opens.

Note: For security reasons, be sure to change the admin password. See Change the Administrator Password (on page 23).

5. Click the Classic View link in the dcTrack Web Client to open Classic View. You must have local administrator rights on the client machine in order to run and properly install the Classic View prerequisites.

6. To install prerequisites, do one of the following:

If you have .NET 3.5 components installed, clicking the Classic View link launches dcTrack Classic View and no other steps are needed. Begin using the application. If the components are not found, dcTrack walks you through the install (see steps below).

Note: The .NET 3.5 component is built into the Windows 7® operating system, so dcTrack launches without needing to install any

components.

If .NET 3.5 components are not installed, a message letting you know once you click the Classic View link.

Install the .NET components by following the wizard that is launched when you click Classic View or by clicking Administration > Install Classic View Prerequisites.

a. Click Install on the first dialog of the install wizard.

b. Optionally, select the "Set MS Access security mode to low" on the "Setting MS Access 2003 security mode" dialog. Click Next.

Note: If you do not set the Microsoft Access® security mode to low, dcTrack still works but you see security warnings each time you launch dcTrack. You must then answer 'No' to all questions about blocking unsafe expressions. If you set the security mode to low but want to change to a higher level later, see your Microsoft Access


c. Click Finish. All components required to run dcTrack are installed.


22

Firefox Users

To log in using Firefox as your browser:

1. If you are using Firefox® and the Windows 7® operating system, if Firefox .NET Assistant® has not already been installed, set the Windows 7 User Account Control to Never Notify and restart Windows 7. See your Windows Help for information on changing this setting.

2. In the browser's address bar, enter the IP address or name assigned to dcTrack™.


4. The first time you access dcTrack, the Licensing page opens. Log in to the page.

a. Click Add, then select your dcTrack license file. Licenses are .LIC files. Repeat this step to add incremental licenses if needed.

Note: Your license file can be retrieved from the Raritan website after you have activated your registration. To activate your registration, click the link in the "Thank you for registering" email from Raritan and create your user account. Once you create your account, look for a "Your Raritan software license key is available" email containing a

link to your license file download page.

b. Click Continue. If you see error messages and the Continue button is disabled, contact Raritan Technical Support. There may be a problem with your license file.

c. Select 'I agree' for the End User License Agreement and click Submit.

5. Firefox users running the Windows 7 operating system - restart Firefox, then reconnect to dcTrack via its IP address.

6. Log in to dcTrack with the default username admin and password raritan. The dcTrack Web Client Dashboard opens.

Note: For security reasons, be sure to change the admin password.

See Change the Administrator Password (on page 23).

7. Click the Classic View link in the dcTrack Web Client to open Classic View. You must have local administrator rights on the client machine in order to run and properly install the Classic View prerequisites.

8. To install prerequisites, do one of the following:

If you have .NET 3.5 components installed, clicking the Classic View link launches dcTrack Classic View and no other steps are needed. Begin using the application. If the components are not found, dcTrack walks you through the install (see steps below).


23

Note: The .NET 3.5 component is built into the Windows 7® operating system, so dcTrack launches without needing to install any

components.

If .NET 3.5 components are not installed, a message letting you know once you click the Classic View link.

Install the .NET components by following the wizard that is launched when you click Classic View or by clicking Administration > Install Classic View Prerequisites.

a. Click Install on the first dialog of the install wizard.

b. Optionally, select the "Set MS Access security mode to low" on the "Setting MS Access 2003 security mode" dialog. Click Next.

Note: If you do not set the Microsoft Access® security mode to low, dcTrack still works but you see security warnings each time you launch dcTrack. You must then answer 'No' to all questions about blocking unsafe expressions. If you set the security mode to low but want to change to a higher level later, see your Microsoft Access


c. Click Finish. All components required to run dcTrack are installed.

9. To complete the installation, do one of the following:

Firefox on a Windows XP client - close and then reopen the browser to complete the installation. Log back in and launch dcTrack.

Firefox running on Windows® client - reset the User Account Control to its previous setting and reboot. Log back in and launch dcTrack.

Change the Administrator Password

The administrator password can only be changed by the administrator. Change the default administrator password as soon as possible to prevent unauthorized administrator-level access to dcTrack.

To change the administrator password:

1. In the Web Client, select Administration > Settings. The Settings window opens in a secondary browser.

2. Click User Accounts in the Authorization and Authentication section. The Users page opens.

3. Click on the admin user.

4. Click Change Password in the "User Information for ADMIN" section.


24

5. Type a new password for the admin account in the Password field, then type it again in the Confirm Password field. The password must be at least 8 characters, including one numerical character, one uppercase character, one lowercase character, and one of the following special characters: ~!@#$%^&*()_+{}|:"<>?/.,';][=-`").

6. Click Save.

Configure the System Clock

dcTrack™ uses the system clock to time-stamp events. Set the system clock as soon as possible to keep an accurate record of events. Using an NTP server is recommended to keep the system clock synchronized.

To configure the system clock manually:

1. In the Web Client, click Administration > Settings. The Settings page opens in a secondary browser window.

2. Click Application Settings in the Application Administration section.

3. In the Time Settings box, select the Time Zone dcTrack resides in from the Time Zone drop-down list.

4. Select the date and time using the tools in the "Set time manually" fields. Select the date from the pop-up calendar. Select the 24-hour time from the drop-down list.

5. Click Save.

See Configure NTP Server Settings (on page 24) for additional time setting information.

Configure NTP Server Settings

The NTP server settings are configured in the Management Client. The Configure Time Servers table lists the NTP servers dcTrack™ contacts to get date and time information. NTP must be enabled first.

dcTrack attempts to retrieve the date and time from the first server on the list. If this attempt fails, it proceeds down the list and attempts to contact the second server, then the third, and so on.

Note: The dcTrack Web Client and not the dcTrack Classic View uses NTP.

To enable NTP and configure NTP servers:


2. Click Application Settings in the Application Administration section.


25

3. In the Time Settings box, check the NTP Settings checkbox to enable it.

4. Click Add.

5. Type the time server's IP address or DNS name in the Time Server field. If you are using the DNS name, it must be configured via the console.

6. Click Save Time Settings.

Build Your Data Center Model in dcTrack

Once you have determined the scope of the data you plan to model in dcTrack™, captured data center information in a spreadsheet template, and installed the application, it is time to build your data center model in the dcTrack database.


26

Checklist - Build Your Data Center Model

Following are the steps to build your data center model in dcTrack. Columns are included for you to use to mark off each step as it is completed:

Step

Step 1: Update the Models Library (on page 28)

Verify Item Models are in Raritan's Models Library (on page 34)

Step 2: Customize dcTrack Lists and MIBs (on page 34)

Customize Drop-Down Lists (on page 34)

Add and Configure SNMP MIBs (on page 35)

Step 3: Create Teams and Users (Optional) (on page 36)

Adding Teams (on page 36)

Adding Users (on page 36)

Step 4: Prepare Drawing Files (on page 38)

Step 5: Collect Your Data to Populate dcTrack (on page 40)

Step 6: Create Locations/Link Drawings and Images to the Location (on page 41)

Creating Locations (Sites) for the First Time (on page 43)

Link AutoCAD Objects with dcTrack Items (on page 45)


27

Step

Step 7: Synch AutoCAD Objects (on page 47)

Importing AutoCAD Items into dcTrack (on page 48)

Step 8: Import Cabinets

Step 9: Add Data Center Infrastructure Items (on page 51)

Add Structured Cable Items (on page 51)

Add Power Items (on page 52)

Add Environmental Items (on page 54)

Add IP Subnets (on page 55)

Step 10: Add Items, Data Connections and Power Connections (on page 57)

Run SNMP Auto-Discovery (Optional) (on page 57)

Import Items and Ports, Data Connections and Power Connections (on page 58)

Step 11: Add and Assign Applications (Optional) (on page 59)

Step 12: Test and Verify (on page 60)


28

Step 1: Update the Models Library

The dcTrack™ Models library is updated regularly by Raritan. The library contains device models, including the ports for each model (where applicable).

Even if this is an initial installation of dcTrack, Raritan recommends you run the Library Update Wizard in Classic View to import the latest Models library available from Raritan. This ensures you are using the most current library available. Obtain the latest library from the Raritan website by logging on and accessing the dcTrack Firmware and Documentation page.

Note: It is recommended you update the library before you customize your dcTrack lists since you cannot configure your MIBs before your

library is updated.

Customers currently on dcTrack 2.6.1 (or earlier) are advised to update to the latest available 2.x library before upgrading to dcTrack 3.0.

Supported Models Library Upgrades by dcTrack Version

Each Raritan Models library is given a version number. The library version you can upgrade to depends on your current version of dcTrack:

dcTrack version Supported Models library version

dcTrack 2.x Any 2.x version of the dcTrack Models library

To use a 3.x version of the dcTrack Models library, you must upgrade to dcTrack 3.0

dcTrack 3.x Any 3.x version of the dcTrack Models library

2.x versions of the dcTrack Models library, are not supported for dcTrack 3.0


29

Notes on Mapping Library Items

Use Ctrl+click or Shift+click to select multiple items at once

If you map an item in your library to an item in the Raritan library but the items are not an exact match, all models that are currently using the Raritan library model are updated to reflect the new library model you apply

If there are no items to map, a message is displayed on the page indicating no items are available for mapping

If items exist in your library but there are no Raritan items to map them to, your items are imported without being mapped

To import the Raritan Master library:

1. In Classic View, select Administration > Libraries > Lib Updates. The Library Update Wizard page opens. Next, download the latest Raritan Models library so you can import it.

2. Click on the Raritan's Support Website link (http://www.raritan.com/support/dctrack/). The Raritan website opens in a browser window.



5. Click the Model Library link in the Firmware, Software, and Product Documentation section of the page on the right.

6. On the Model Library page, select the link for the library version you want to download.

7. Download the Library file and save it to a location of your choosing.

8. In Classic View on the Library Update Wizard page, click Browse to locate the library you saved locally, then click Open to begin the update.


30

9. Click Go to begin the import. dcTrack then walks you through each step of the import process that needs your input. For example, if a manufacturer or model does not exist in your library but does in exist in dcTrack's library, you map the items or skip them.

10. First, map the any manufacturers that are in your library but not in the dcTrack library. Click your library item in the left text box, then click on the Raritan item you want to map it to in the right text box.

11. Click Map to map the items. If the item does not have a match, skip the mapping by clicking Next. Your items are imported into the library once the library update process is complete.

12. Map any data connectors that are in your library but not in the Raritan library. If your connector has an image associated with it, when you click on it the image is displayed in the 'Image of selected connector' box. If you want your image to replace Raritan's connector image, select the 'Copy image when mapping' checkbox. Click Next to move to the next mapping page.


31

13. Map any power connectors that are in your library but not in the Raritan library. If your connector has an image associated with it, when you click on it the image is displayed in the 'Image of selected connector' box. If you want your image to replace Raritan's connector image, select the 'Copy image when mapping' checkbox. Click Next to move to the next mapping page.

14. Map any protocol information, such as Ethernet/IP address, HSSI information and so on, that is in your library but not in the Raritan library. Click Next to move to the next mapping page.


32

15. Map any data rates that are in your library but not in the Raritan library. For example, a network item in your library may have a data rate of 2GB. If the item does not exist in the Raritan library, add it now so it is associated with the network item when the library update is complete. Click Next to move to the next mapping page.

16. Map any circuit breakers and fuses that are in your library but not in the Raritan library. Click Next to move to the next mapping page.

17. For models, dcTrack compares the models in the Raritan library with those in your library. Click Begin Compare to start the model comparison between the two libraries. As the process is underway, monitor the progress through the progress bars displayed at the top of the page.

If an exact match to your library model is found in the Raritan library, dcTrack updates your library with the latest model information and image (if any).

If no exact match is found, dcTrack looks for the best match for the model. If a match is not found, dcTrack prompts you to find a match or add it to the library.

Make changes to the model information, such as form factor and so on, as needed.


33

Selecting the 'Don't Overwrite from Master Library' checkbox when you are mapping models prevents images from your library from overwriting the model image in the Raritan library. Clicking on Images opens an image of the model in a new window.

18. Once the library update finishes, the new information is available in dcTrack.


34

Verify Item Models are in Raritan's Models Library

After you have updated the library, it is good practice to ensure models that you are using in your data center are included in the library. This is an optional step when building your data center model.

The easiest way to verify this is to import the latest models library from Raritan, then designate models you use in your data center as your standard models. While you go through this process, if you find models you use are missing from the library, note them and then submit a request to Raritan Customer Support.

Alternatively, import the spreadsheet that contains your latest inventory of data center assets including, at a minimum, their make and model. You can them map items using the Import Wizard, thereby identifying items not the Raritan library.

See Designating Standard Models and Identifying Models Missing from the Library in the dcTrack Help for details, respectively.

Step 2: Customize dcTrack Lists and MIBs

Note: It is recommended you update the library before you customize your dcTrack lists since you cannot configure your MIBs before your

library is updated.

Customize Drop-Down Lists

Customizable drop-down lists (administrative lists) are specific to your data center needs and are used in dcTrack™ as field values. For example, departments, color coding, item functions, and so on.

Lists are maintained by administrators and work in conjunction with libraries as a tool to manage the information collected in and maintained by dcTrack. Items can be added to lists and edited as needed to fulfill your specific requirements.

To add an item to a list:

1. In Classic View, click Administration > Lists to open the Lists page.

2. In the Lists section of the page, click on the list you want to add the item to.

3. Click Add.

4. In the Add/Edit List Item section of the page, enter a name for the item. Required

5. Enter a description of the item.

6. Enter any additional information as needed and where applicable. The information that can be entered varies depending on the list you are adding it to.


35

7. Click Save.

For more details on lists, see the Lists topic dcTrack Help.

Add and Configure SNMP MIBs

If dcTrack™ is to request SNMP data from SNMP-enabled facility equipment in the data center, MIBs and OIDs for this equipment need to be configured in dcTrack. All equipment for a particular manufacturer that uses the same MIB can share the same dcTrack MIB definition.

Configure MIBs and OIDs in dcTrack™ for your SNMP enabled equipment if you are going to use SNMP requests to get data.

To create an SNMP MIB definition from the SNMP library:

1. In Classic View, select Administration > Libraries > SNMP.

2. Add a MIB definition in the MIB Library section of the page.

3. Load a MIB file that is provided by the item manufacturer.

4. Once the MIB is loaded, you can browse in the MIB Browser and Object Details section of the page.

5. Identify the MIB OID that contains the data you want and select it in the browser. The details of this OID branch are shown in the lower right section of the page.

6. From the Link OID to dcTrack drop-down, select the dcTrack field that corresponds to the OID value.

Note: If you want to select a custom field, type the name of the custom field into the drop-down. If the custom field already exists, it is added. If the field is not found, you are prompted by the application

to create it. Create the field if needed.

7. Select a value in the Index Start drop-down. The index is a value that is added to the end of the OID to create the full OID used to query the item. For example, if querying amps for all receptacles of a rack PDU, then the Index Start would be the last digit in the OID for the first receptacle. dcTrack then increments the index for each receptacle that exists for that particular rack PDU.

8. Select a multiplication factor to correct the unit. For example, the amps value in MIB is stored in milliamps and must be multiplied by 0.001 to store the value as amps in dcTrack.

9. Once all fields are mapped, link the MIB definition with all the models that use it by selecting the MIB in the MIB Library section and then selecting all the models you want to link to the MIB (use Ctrl and Shift keys for multiple selections). Click Link. Repeat the process for other MIBs.

10. From an item page such as a Rack PDU page:

a. Add a Comm Port.


36

b. Provide the IP address and SNMP Community Name.

11. Click Get Readings to get a new SNMP reading.

Step 3: Create Teams and Users (Optional)

If needed, create users and teams, and assign users to teams in dcTrack™. This is an optional step at this point, but a good practice.

The level of access each user has to dcTrack functions is based on the access level they are assigned when they are created. Access levels are default "roles" that cannot be edited.

User accounts are added, edited and deleted in the dcTrack™ Web Client. Teams, which users are assigned to, are managed in the Classic View.

Note: It is recommended that teams be created before user accounts but this is not required in order to create user accounts.

As an alternative to using local user account management, configure dcTrack™ to use an LDAP server or an Active Directory (AD) server for centralized authentication. See Configuring dcTrack to Use LDAP User Authentication in dcTrack Help for information.

Adding Teams

To add a team:

1. In Classic View, select Administration > Users to open Users page.

2. In the Teams section, enter a name for the team in the first field and description of the team in the second field. Required

3. Click Update. The team is added to the list and is available in the Team drop-down in the User Details section of the page.

Adding Users

To add a user:

1. In the Web Client, click Administration > Settings in the dcTrack Web Client. The Settings page opens in a secondary browser window.

2. Click User Accounts in the Authorization and Authentication section. The User Configuration page opens displaying a list of all user accounts created for the system.

3. Click Add. A blank user information page opens.

4. Enter the Common User Information.

a. Enter a username. User names must be at least 3 characters, but not more than 40 characters. For email notification to function in the dcTrack Classic View, the user name must match the user's email account user name. Required


37

b. Enter the user's first name.

c. Enter the user's last name. Required

d. Enter an email address. Required

e. Password and Confirm Password: Enter a password for this user. The password must be at least 8 characters, including one numerical character, one uppercase character, one lowercase character, and one of the following special characters: ~!@#$%^&*()_+{}|:"<>?/.,';][=-`"). Required

f. In the Description field, enter comments about the user.

5. Complete the Additional Fields.

a. Enter the user's mail server. For example, mail.company.com.

b. Enter the mail server's SMTP port. Default is 25.

Note: If the mail server field is left blank, the user cannot receive

email notifications.

c. If a password is not required to access the SMTP, select the No Password checkbox.

d. Select the team this user is on. Teams must be created in dcTrack before you can assign them to users.

e. Select the user's access level from the Access Level drop-down. If the user is a Gatekeeper who should receive request notifications, select the Request Emails checkbox.

6. Click Add.


38

Step 4: Prepare Drawing Files

Locate any AutoCAD® or Microsoft Visio® data center floor plan drawings you have. If floor plan drawings do not exist for your data center, create drawings in either AutoCAD or Microsoft Visio according to the requirements described in Mandatory Drawing File Requirements (on page 39).

Raritan offers drawing file templates you can download and use to create drawing file renderings of you data center. See Drawing File Templates (on page 8).

Note: Raritan or its authorized Solution/Implementation Partners can

provide services to assist you in this step.

All drawings must be saved as .dwg files in order to be used with dcTrack™. Drawing files are linked to data center locations in dcTrack - the files are not imported into dcTrack. Linking to the file allows you to make changes to the file as needed so it is always current.

As a best practice, Raritan recommends a single working copy of your data center drawing be used throughout your organization. This drawing file can be saved on a file share that is visible as a read-only file to all dcTrack users.

See Drawing File Preparation and Best Practices (on page 130) for additional best practices regarding drawing files. If you are exporting files from AutoCAD to Visio, see Visio-to-AutoCAD Export Rules (on page 139).


39

Mandatory Drawing File Requirements

Before you import your drawings into dcTrack™, make sure they meet the following mandatory drawing requirements:

A Solid Hatch object must be drawn inside each rack, cabinet, PDU and CRAC unit

A text label (Standard Text or Multiline Text) must be created and placed inside every rack, cabinet, PDU and CRAC unit represented in the drawing. This label must contain the name or ID of the object that will be used in dcTrack

All drawing objects must be located in the drawing's Model Space (for AutoCAD drawings)

Do not begin the name of any layer with the word "dcTrack" unless you are directed to do so

Also, review the drawings to ensure:

All floor objects such as cabinets, floor PDUs, and CRAC units, and other floor-standing units are included in the drawing.

All floor objects have unique text IDs and that they match any other documentation to be imported into dcTrack.

See Drawing File Preparation and Best Practices (on page 130) for additional best practices regarding drawing files. If you are exporting files from AutoCAD to Visio, see Visio-to-AutoCAD Export Rules (on page 139).


40

Step 5: Collect Your Data to Populate dcTrack

To speed up the dcTrack™ implementation process, Raritan recommends you collect as much information as possible from your existing systems and documents. The data you gather is then added to dcTrack to populate the database. For example, locate any spreadsheets containing data center items.

The data must be in Microsoft Excel® spreadsheets or CSV files, and match the format of the dcTrack import and documentation templates as closely as possible.

Following are the most common data collection sources for most of our clients:

Data source Description

Existing spreadsheets

If you have data center infrastructure data already documented in Microsoft Excel spreadsheets, most of this information can be imported into dcTrack when it's time to populate your data base. Imports are done using the Import Wizard.

The review and audit the spreadsheets for accuracy to ensure they accurately represent the as-built conditions of your data center.

Export from existing databases

Data in databases that track infrastructure data, which are typically exported as Microsoft Excel files or CSV files. The databases and spreadsheets that are exported from must be reviewed and audited to ensure an accurate representation of as-built conditions of the data center.

Single line diagrams and other documents

Single line diagrams and other documents that represent how the power and data infrastructure are installed and configured in the data center are used to gather data for input into dcTrack.

Surveys documented in spreadsheets

The scope of work associated with this step may vary greatly depending on the number of data centers, their sizes, the breadth and depth of the target data to be managed in dcTrack, and the degree of completeness and accuracy of the existing documentation.


41

Data source Description

Cloning items Although not a data collection method per se, use the dcTrack Clone feature to create copies of device and network items rather than add them one-by-one. This feature speeds up the data creation process.

For example, rather than adding all of your UPS to dcTrack one at a time when it comes time to add them, add one and use the Clone feature to clone as many UPS as needed.

The Clone feature is available in Classic View. Information on using this feature is provided in this guide (where applicable).

Step 6: Create Locations/Link Drawings and Images to the Location

Your data center location (site) is the root of your data center model in dcTrack™. At least one location and one cabinet must exist in dcTrack to build your data center model.

Adding the location requires you to enter a minimum amount of information in order to save it (see Creating Locations (Sites) for the First Time (on page 43) for details).

Raritan offers drawing file templates you can download and use to create drawing file renderings of you data center. See Downloading Raritan dcTrack Drawing File Templates (on page 8) for steps on downloading drawing file templates from the dcTrack Support page.

Note that when you add a drawing file of the location to dcTrack, the cabinets in the file are added. However, you must add or import all of the items that are contained in the cabinet such as servers and so on, as well as add or import free-standing data center items such UPS, CRAC units and so on. Information on performing these steps is included in this guide.


42

Item Object Description

Data center information

Location information such as the name of the location, square footage, and so on.

Data center image

An image of your data center location (if needed) can also be added when the location is created. This is an image file, such as a .JPG, that depicts the data center itself.

.DWG drawing file of the data center

When you add your location, you also link the data center's drawing file to it. The drawing file is a .DWG file created in AutoCAD® or Microsoft Visio®. The elements of the drawing file, such as the floor plan, floor tiles, cabinets and so on, are added to dcTrack once the file is linked to the location.

Review the information preparing drawing files before you add them. See Step 4: Prepare Drawing Files (on page 38)


43

Creating Locations (Sites) for the First Time

This topic covers creating a data center location for the first time in dcTrack™ when you are building your data center model after dcTrack has been installed.

Note: The term site is used in Classic View and location is used in the Web Client.

At least one location must exist in dcTrack before you can begin building your entire data center, including creating cabinets, items, connections and so on, in dcTrack.

Once you have created the location, you are ready to import AutoCAD® drawing files containing your data center items, and then synch those AutoCAD objects.

To create a location in dcTrack:

1. In Classic View, click Sites to open the Sites page.

2. Click Add on the bottom of the Sites page.

3. Complete the Site Information section:


44

a. Enter a Site Code and the Site Name for the site. The site code and site name appear in the Available Sites list once the site is added. Required

b. Select a type for the site, either main, regional, local or disaster recovery.

c. Enter the square footage of the site. Required

d. Enter the outer room dimensions, if needed. When you put your cursor in the Outer Room Dimensions field, example diagrams of rooms measured in length and width is displayed.

Tip: You can change the measurement units to either US or SI (metric) by clicking on the Units drop-down at the bottom of the left

frame.

e. Enter the data center heights, if needed. When you put your cursor in any one of the Data Center Heights fields, example diagrams of room heights is displayed.

4. Complete the Site Address section:

a. Select the country the site is located in. Required

b. Enter the floor, street, city, state and postal code for the site, if needed.

5. Complete the Floor Map Drawing Options section:

a. Select the appropriate Drawing North arrow that best reflects your floor map orientation. For example, select the down arrow if North is located in that direction.

b. If a raised floor grid labeling system such as A1, A2 and so on is used in the data center, make the appropriate selection from the Grid Labeling drop-down.

6. Complete the Cabinet Row Orientation on Drawing section:

a. Make the appropriate selections to indicate the direction in which the cabinet position numbers increase.

The labels shown inside the depiction of the cabinets are cabinet IDs, they are not position numbers. The position number for each cabinet is entered on the IT Items Cabinet page. Position numbers are used to create a convention that allows dcTrack to track the relative position of a cabinet within a row.

7. Upload a of the site in the Site Picture section of the page:

a. Click Browse and select the picture. JPG, BMP, WMF and GIF formats are supported. Once added, the picture is displayed in the box under the Site Picture field.

8. Upload a drawing of the site in the Site Drawing section of the page:


45

a. Click Browse and select the AutoCAD® .dwg drawing file of the data center. See Drawing File Preparation and Best Practices (on page 130) for more detail about setting up the AutoCAD drawing.

Note: AutoCAD 2010 and 2011 file formats are not supported by dcTrack.

9. Click Save.

Note: Once the site is created, in order to see it in the Web Client, you must log out and then log back in to Web Client.

Once you have created the location, you are ready to import AutoCAD® drawing files containing your data center items, and then synch those AutoCAD objects.

Link AutoCAD Objects with dcTrack Items

To link/synchronize AutoCAD® objects with dcTrack™ items:

1. In Classic View, select Visualize > Floor Map to open the Floor Map page.

2. Click the AutoCAD Synch button.


46

The Synch dcTrack with AutoCAD Drawing dialog opens.

A blank space appears in the "In dcTrack" column of the "Objects found in AutoCAD Drawing" list if the objects are found in the AutoCAD drawing but are either not found in dcTrack or are in dcTrack with a matching label that is not linked to AutoCAD.

Note: Not every floor-standing item has to have a link. For example, UPS units may not be located within the data center raised floor room, so the UPS exists in dcTrack but does not have a link to the

AutoCAD drawing.

If the items already exists in dcTrack but have not been linked to the AutoCAD drawing, No is displayed under the Linked column of the "Items found in dcTrack" list. If the item is already linked, Yes is displayed.

3. Link the items to objects in the AutoCAD drawing in one of the following ways:

a. Link one object to one AutoCAD object:

Select the item from the "Items found in dcTrack" list.

Select an object from the "Objects found in AutoCAD Drawing" list.

Click "Link dcTrack Item with AutoCAD Object".

Note: Using this method of linking also allows you to link AutoCAD objects to objects in dcTrack that do not have matching object labels.

4. Link those objects found in the AutoCAD drawing with dcTrack items.


47

a. Link multiple objects to the AutoCAD drawing:

Select objects of the same item class from the "Objects found in AutoCAD Drawing" list. Use Ctrl + click or Shift + click to select multiple items.

Select the corresponding item class from the "Import selected AutoCAD objects as Item Class" drop-down and click Import Items.

All new items that have been imported are now visible in dcTrack in the floor map items list and on the corresponding Item Class page.

5. Double-click on each item or click Detail 1 to complete all relevant fields for each item. From the Actions drop-down, select Install Item Request for Approval.

Step 7: Synch AutoCAD Objects

Synchronize the floor plan drawing with dcTrack™ using the AutoCAD Sync function on the Visualize > Floor Map page in Classic View. Synching imports items such as cabinets, floor PDUs, CRAC units, and other floor-standing units into dcTrack.


48

Importing AutoCAD Items into dcTrack

Once an object has been imported into dcTrack™, you can edit its detail information from its corresponding Items List page. For example, you can import a cabinet represented on an AutoCAD drawing, select IT Items > Cabinets to locate it, and then edit the cabinet information.

To import an AutoCAD object into dcTrack:

1. In Classic View, select Visualize > Floor Map to open the Floor Map page.

2. Click the AutoCAD Synch button.

The Synch dcTrack with AutoCAD Drawing dialog opens.

3.

A blank space appears in the "In dcTrack" column of the "Objects found in AutoCAD Drawing" list if the objects are found in the AutoCAD drawing but are either not found in dcTrack or are in dcTrack with a matching label that is not linked to AutoCAD.


49

Note: Not every floor-standing item has to have a link. For example, UPS units may not be located within the data center raised floor room, so the UPS exists in dcTrack but does not have a link to the

AutoCAD drawing.

4. If the items already exists in dcTrack but have not been linked to the AutoCAD drawing, No is displayed under the Linked column of the "Items found in dcTrack" list. If the item is already linked, Yes is displayed.

5. Select objects of the same item class from the "Objects found in AutoCAD Drawing" list. Use Ctrl + click or Shift + click to select multiple items.

6. Click Import Items. The items are added to the "Items found in dcTrack" list. Close the Synch dcTrack with AutoCAD Drawing dialog.

7. Edit the item(s) as needed.


50

Step 8: Import Cabinets

Raritan strongly recommends you review the following topics before using the Import Wizard:

Best Practices when Using Import Wizard (on page 142)

Using Raritan Spreadsheets vs. Your Own Spreadsheets (on page 7)

General Spreadsheet Requirements (on page 143)

Cabinets themselves are added to dcTrack™ by synching a linked AutoCAD® drawing in dcTrack. See Link AutoCAD Objects with dcTrack Items (on page 45).

However, synching only creates the cabinet item and populates its Item Name field. All other information must be populated using the Import Wizard or it must be entered manually.

Raritan recommends using the Import Wizard when you have many items to add at once since it may be time consuming to add items manually one at a time. However, items can be added manually if you prefer.

See:

Importing Cabinets and Additional Items Using the Import Wizard (on page 154) for details on adding cabinets using the Import Wizard

Manually Adding Items in dcTrack (on page 170) for details on adding cabinets manually one at a time

Cabinet Import Requirements (on page 144) before beginning an import.

Use the Raritan 01_Items_-_Cabinets_Only_for_3.0.xls spreadsheet template for importing cabinets, or use your own spreadsheet.

Template spreadsheets are available on the Raritan dcTrack Support Website. See Downloading Raritan dcTrack Spreadsheet Templates (on page 7).

Whether you use a Raritan spreadsheet or your own, review:




51

Step 9: Add Data Center Infrastructure Items

This step includes adding data center infrastructure items such as structured cabling items, power items and environmental items to your data center model in dcTrack™.

Infrastructure items also include the IP subnets being used in your data center. Without these IP subnets, automated data population using SNMP discovery cannot be performed.


Use a Raritan spreadsheet template to capture the information and then import it. Templates are available on the Raritan dcTrack Support Website.

See Downloading Raritan dcTrack Spreadsheet Templates (on page 7).

Alternatively, if you already have a spreadsheet of your own you are using to track the items, you can use your spreadsheet. Make sure your spreadsheet headings match those of Raritan's spreadsheet headings in order to avoid manually mapping spreadsheet column names during the import process. For example, if you use the heading Mdl for the models column in your spreadsheet, the heading must be changed to Models so it matches the Raritan spreadsheet. See General Spreadsheet Requirements (on page 143) for more spreadsheet requirement information.

Add Structured Cable Items

In this step, the Structured Cable Items are created. This step applies to anyone using Structured Cable Items. If you are not using Structured Cable Items, this step is optional.

Use the 03 Structured Cable Plant.xls spreadsheet as a resource to capture structured cabling information, if needed. This template is available on the Raritan dcTrack Support Website.

See Downloading Raritan dcTrack Spreadsheet Templates (on page 7).

Once you have gathered all your information, manually create the items in dcTrack™.

See Manually Adding Items in dcTrack (on page 170) for details on adding Structured Cable Items manually.


52

Add Power Items

Add UPS, outlet, floor PDU, and rack PDU power items to dcTrack™.






See:

Importing Cabinets and Additional Items Using the Import Wizard (on page 154) for details on adding power items using the Import Wizard

Manually Adding Items in dcTrack (on page 170) for details on adding power items manually one at a time

Notes on Adding UPS Items

Use the 02_Items_-_All_Other_Classes_for_3.0.xls spreadsheet template to capture the information and then import it. This template is available on the Raritan dcTrack Support Website. See Downloading Raritan dcTrack Spreadsheet Templates (on page 7).

Create UPS units and assign them to UPS banks.

If UPS units are included in your floor plan drawing and you have synched with your drawing already, go to the Power Items > UPS page to edit and/or update them. If UPS units are not included in your floor plan drawing, add them to dcTrack.

You must enter the UPS capacity in kVA and kW as well as the voltage values.

You must assign the UPS to a UPS bank even if you have only one UPS unit.

UPS banks are created in the Available UPS Banks section of the UPS page.


53

Notes on Adding Floor PDUs

Use the 04 Power Panels.xls spreadsheet template to capture the information and then import it. This template is available on the Raritan dcTrack Support Website. See Downloading Raritan dcTrack Spreadsheet Templates (on page 7).

Create a floor PDU, assign it to a UPS bank, enter the floor PDU capacity in kVA, and enter its input breaker amperage and voltage, which should match your UPS voltage.

If floor PDU units are included in your floor plan drawing and you have synched them with your drawing already, go to the Power Items > PDU page in Edit mode to edit and update the PDU items.

If floor PDU units are not included in your floor plan drawing, add the floor PDU items on the PDU page.

Create power panels, remote power panels, or busways for each floor PDU.

If using remote power panels (RPP), create RPP for each floor PDU. Next, go back to the floor map and sync each RPP with its matching floor object in the AutoCAD® drawing.

Add breakers to each power breaker panel.

If using busways, breakers are added when creating the outlet plug-in modules in the power outlets step.

Notes on Adding Rack PDUs

Use the 02_Items_-_All_Other_Classes_for_3.0.xls spreadsheet template to capture the information and then import it. This template is available on the Raritan dcTrack Support Website. See Downloading Raritan dcTrack Spreadsheet Templates (on page 7). Verify this is the spreadsheet to use

Create one rack PDU with ports, such as electrical sockets or receptacles, for each rack PDU model in the data center

Clone each rack PDU model as needed to cover all rack PDUs installed

Rename the cloned rack PDUs. There is no need to assign cabinet location

By using this import process you create a data ports for each intelligent rack PDU


54

Notes on Adding Power Outlets


Create power outlet items, assign them to breakers and create outlet ports, such as electrical sockets or receptacles, on the Power Items > Outlet page.

On the floor plan drawings, add power cable lines between cabinets and floor PDUs or RPPs. A cable line must be a continuous line and each end must penetrate inside the cabinet and PDU/RPP rectangles. Optional

If using busways, rather than selecting a breaker, enter the total number of poles within the outlet plug-in module. Then, for each of the poles, select the appropriate breaker. Once this is complete, create the outlet ports (such as electrical sockets or receptacles).

Add Environmental Items

Environmental items include CRAC units and probes.






See:

Importing Cabinets and Additional Items Using the Import Wizard (on page 154) for details on adding s using the Import Wizard

Manually Adding Items in dcTrack (on page 170) for details on adding s manually one at a time


55

Notes on Adding CRAC Units


Create CRAC units and assign to CRAC groups. If CRAC units were included when you synched with your drawing, select Environ. Items > CRAC Explorer menu to edit and/or update the CRAC items.

If CRAC units were not included when you synched with your drawing, use this page to add the CRAC items.

You must enter the CRAC capacity in tons, which is automatically converted to kW, as well as the Input Voltage values.

You must assign the CRAC to a CRAC group even if you have only one CRAC unit.

CRAC groups are created in the Available CRAC Groups section of the page.

Notes on Adding Probes - verify/review/questions


Probes are equipment that various sensors can be connected to

Add IP Subnets

When subnets are defined, assigning IP addresses to items is quicker and allows dcTrack™ to provide you with a list of unused IP addresses so as not to duplicate addresses.

Important: You must create your IP subnets prior to performing an SNMP auto-discovery. Otherwise, the discovered IP address is not added to the systems and ports that you are adding.

IP addresses that do not belong to subnets can be assigned to an item, it is highly recommended that you do not do this since address duplication cannot be tracked and prevented in this situation.

To add a subnet:

1. In Classic View, select IP Space > Subnets. The Subnets page opens.

2. Select Edit from the Page Mode drop-down.


56

3. Make the appropriate selection for the new subnet from the Mask drop-down.

4. Enter the network prefix in the Net Prefix field.

5. From the Subnets drop-down, select the quantity of subnets you want to create. The number of subnets is limited to the maximum possible number of subnets based on the mask selection.

6. The Hosts/Subnet field provides the total number of hosts (or IP addresses) that can be created for each subnet.

7. The first Subnet drop-down provides the address of the first subnet to be created. You can edit the first octet after the network prefix. The fourth octet must always be 0. For example, if the network prefix is two octets, then you can type over the third octet if that address is not in the list.

8. The entry in the Default Gateway field is created automatically but you can edit it as needed.

9. The DNS Suffix entry can remain blank. If a selection is made from the drop-down, the value is appended to the name of the server that is assigned an IP address from this subnet. If this drop-down is empty, ask the Gatekeeper to provide selections and then select the DNS Suffix List.

10. Making a selection form the Logical Name drop-down is optional but highly recommended since it is a way to identify the subnet's purpose or function. If this drop-down is empty, ask the Gatekeeper to provide selections and then select the Subnets/VLANs.

11. The Location Type drop-down can only be completed after a selection is made from the Logical Name drop-down. This list is used in conjunction with the Location drop-down and it limits the item locations that can be assigned IP addresses from the subnet. If Group is selected and the Location drop-down is empty, ask the Gatekeeper to provide selections and then select the Cabinet Groupings. If Row is selected and the Location drop-down is empty, then you have not specified the row label entry for any of the cabinets on the IT Items Cabinet page.

12. Each subnet can be associated with up to four colors for identification purposes.


57

13. When all fields have been completed, click Create. If a duplication or overlap in the entries is detected, no subnets are created. You must make the necessary adjustments to remove the duplication.

Step 10: Add Items, Data Connections and Power Connections

Add the remaining items from your data center using either SNMP auto-discovery (optional), or using the Import Wizard.

Run SNMP Auto-Discovery (Optional)

dcTrack uses SNMP auto-discovery to locate existing data center items and their associated ports, and then create them in dcTrack. Items must be SNMP enabled in order for dcTrack to locate them, and their MAC and IP addresses must be provided.

Important: Run SNMP auto-discovery before you import item spreadsheets. If you do not, the discovered MAC and IP addresses are not added to ports created during the import process.

Important: You must create your IP subnets prior to performing an SNMP auto-discovery. Otherwise, the discovered IP address is not added to the systems and ports that you are adding.


58

SNMP auto-discovery collects the following types of data using RFC 1213 MIB (.1.3.6.1.2.1) and Host Resources MIB (.1.3.6.1.2.1.25):

System name, description, services, uptime

System network interfaces (ports) including MAC and IP addresses

System RAM and virtual memory

Disk storage capacity and percent used

Brand, number and load of system processors

Installed software and installation date

Port names located through SNMP auto-discovery use the prefix "eth." Make sure to use this prefix when using the Import Wizard so as not to duplicate ports.

To access SNMP auto-discovery:

1. In Classic View, select the IP Space > Discovery to run the SNMP auto-discovery.

2. Add one or more of the discovered systems by choosing the appropriate site and item class.

Visit each discovered item and complete the missing port attributes, such as the connector and media. This info cannot be derived from the discovery process. This step can be performed on the item pages. However, it is easier to do from the Administration > Item & Ports page by selecting Ports from the upper left drop-down list.

Import Items and Ports, Data Connections and Power Connections

Items that are not discovered during an SNMP auto-discovery are imported using the Import Wizard or entered manually. Items that are already in dcTrack via SNMP auto-discovery are updated by the import process thus adding information not available from discovery such as the model, cabinet and RU position, serial number, and so on.






59

Notes on Adding Items

The 02_Items_-_All_Other_Classes_for_3.0.xls template should be used for documenting items to be imported. The following items are imported via the Wizard:

Device Items

Network Items

Comm\Data Panel Items

Floor PDU and Rack PDU Items

Probes Items

Note: Data and power ports are created as part of the import item process.

Notes on Data Connections

Use the 05_Connections_-_Communications_for_3.0.xls template to document all communications connections and import them into dcTrack™. Manually update any remaining data not included in the template.

Notes on Adding Power Connections

Use the 06_Connections_-_Power_for_3.0.xls template to document all power connections to be imported into dcTrack™. Manually update any remaining data not included in the template.

Step 11: Add and Assign Applications (Optional)

If applications associated with items were not discovered during SNMP auto-discovery, manually add any additional applications to items.

To add an application:

1. In Classic View, select IT Items > Device.

2. Select the device you want to add the application to.

3. Select Edit from the page mode drop-down.

4. Add the application manually or through SNMP.

Manually:

a. From the Application Name drop-down, select the application to be tracked.

b. If the application name does not exist in the list, select Add New Application Name from the Actions drop-down. The Manage Lists dialog appears. Add the application name and click Save.

Auto-Discovery


60

a. Click the Discovered Applications button. The Apps from SNMP dialog appears. All applications that were auto-discovered via SNMP and are installed on the device item are displayed. If no applications are displayed or the specific application you are looking for is not displayed, run the SNMP process again.

b. Select applications to be added.

5. Click Update and then click Close.

Step 12: Test and Verify

Once you have completed all necessary data center build steps, test the application and verify the data for completeness and accuracy by using dcTrack™ on a trial basis and incorporating dcTrack into your standard data center management processes.


61

Begin Using dcTrack

At this stage, you have installed dcTrack™ and built your data center model, so you are ready to begin using the application to manage your data center.

Raritan strongly suggests you take our dcTrack training prior to implementing dcTrack and prior to using it. The dcTrack video training course is accessed from www.raritantraining.com http://www.raritantraining.com. You need a Raritan provided username and password to access training, which are acquired through our training website. Once you are verified, Raritan gives you access to the courses.

The key to the success of any infrastructure management system is to introduce a clearly defined change management process. We suggest that you identify a single point of contact (a single person or department) to manage and administer all of the communications systems infrastructure and their subsystems and resources.

All future change requests must be funneled through this single point of contact. In turn, this person/department initiates work orders to execute and document changes.

Raritan highly recommends that a single person is assigned to audit the physical changes implemented within the data center space as a result of work orders issued in dcTrack. This person should not be the same person who implements the work orders.

See dcTrack Help for information on using dcTrack features to manage

your data center.

http://www.raritantraining.com/

62

In This Chapter

Overview .................................................................................................. 62 Integrating an Existing dcTrack Installation with a New Power IQ Installation................................................................................................ 63 Integrating an Existing Power IQ Installation with a New dcTrack Installation................................................................................................ 80 Integrating an Existing dcTrack Installation with an Existing Power IQ Installation................................................................................................ 87 Integrating dcTrack with AMS via EMX or PX2 ....................................... 97

Overview

Review this section of this guide if you are:

Integrating an Existing dcTrack Installation with a New Power IQ Installation (on page 63)

Integrating an Existing Power IQ Installation with a New dcTrack Installation (on page 80)

Integrating an Existing dcTrack Installation with an Existing Power IQ Installation (on page 87)

Integrating dcTrack with AMS via EMX or PX2 (on page 97)

Integration steps vary from one integration scenario to another, so follow the steps that are specific to your integration needs. If you are unsure of the steps to follow, contact Raritan Technical Support.

Important: Raritan strongly suggests you read through the steps that apply to your dcTrack integration needs before you begin an integration.

Chapter 3 Integrating dcTrack

Chapter 3: Integrating dcTrack

63

Integrating an Existing dcTrack Installation with a New Power IQ Installation

Follow the steps provided here if you have already installed dcTrack™ and are using the application, and you are now adding a new installation of Power IQ for the first time.

Important: The steps you must perform to add Power IQ to your dcTrack installation vary based on the version of dcTrack you are currently using. Refer to the dcTrack version-specific instructions provided here.

dcTrack 2.2 Users

dcTrack™ 2.2 does not support Power IQ. Call Raritan Technical Support in order to schedule a database upgrade.

dcTrack 2.4 Users

dcTrack™ 2.4 does not support an upgrade to dcTrack 2.6. Follow these steps to move to dcTrack 2.6 and integrate it with a new Power IQ installation.

Change the Web Session Timeout for dcTrack (on page 64) Optional

Back Up Your dcTrack Database (on page 66)

Recreate the dcTrack Virtual Machine (see "Recreate the dcTrack Virtual Machine - verify/review/questions" on page 67)

Load dcTrack onto the Virtual Machine (on page 17)

Restore Your Database (on page 68)

Run the Prerequisite Program (Optional) (on page 18)

Initial Configuration of dcTrack (on page 19)

Update Power IQ with dcTrack Items (on page 71)

For a checklist you can print and use to check off steps as you completed them, see Checklist - dcTrack 2.4 Users Integrating with a New Power IQ Installation (on page 64)


64

Checklist - dcTrack 2.4 Users Integrating with a New Power IQ Installation

Use the checklist to track your progress.

Step Status

Change the Web Session Timeout for dcTrack Optional

Back Up Your dcTrack Database

Recreate the dcTrack Virtual Machine


Restore Your Database

Run the Prerequisite Program Optional


Update Power IQ with dcTrack Items

If you have notes on the process, capture them here.

Notes:


65

Change the Web Session Timeout for dcTrack

Because the processes described in this section may take some time to complete, change the session timeout to Never to ensure the application does not timeout before the process completes. Once done, change the session timeout as needed.

To change web session timeout for dcTrack:


2. In the Security and Encryption section, click Other Security Settings.

3. In the User Session Timeout box, select Never from the "Log users out" drop-down.

4. Click Save Timeout. A "User sessions will not time out" confirmation appears at the top of the page.


66


The size of your database may impact the time it takes to complete this process. The larger the database, the more time it may take.

If your database is large, consider changing the application timeout to Never in order to avoid the system timing out. Change this setting back to your desired timeout period once the process is completed.

Best Practice:

When performing a backup, Raritan suggests you do the following in order to minimize the risk of data loss and system downtime:

If you are running dcTrack from a virtual machine:

Check with your virtual machine group to make sure your virtual instance is backed up

If the virtual machine is backed up, ask for the backup frequency and retention duration

If you are running dcTrack on a hardware appliance or you do not want to rely on your virtual machine instance backup, Raritan recommends:

Setting up your nightly back-ups so they are automatically moved to an ftp server, or manually move them to a local computer each day

Restoring the back-ups to a recovery system on Monday, Wednesday and Friday each week (see Restoring a Database in the dcTrack Help)

Spot checking your standby system

Note: Your dcTrack license permits you to have a recovery system at no extra charge.

To back up your dcTrack database:


2. Click Data Backups in the Data Management section.

3. In the Backup Archives section, click Create. The file is created and added at the top of the list.


67

Recreate the dcTrack Virtual Machine - verify/review/questions

After you have upgraded to the current version of dcTrack™ and backed up your database, recreate your dcTrack virtual machine. See Virtual Machine Recommendations (on page 13) for recommended minimum requirements.

Note: The following virtual machine installation steps are an example of a virtual machine installation. Follow your installation preferences if they

differ from these.

Refer to Virtual Machine Recommendations (on page 13) as needed for information on the number of virtual processors, and the amount of memory allocated for the virtual machine.

To create the virtual machine:

1. Connect to the VMware server using vSphere client. Log in as a user that has permission to create, start, and stop virtual machines.

2. In the Summary tab, click New Virtual Machine in the Command box.

3. Choose Custom. Click Next.

4. Enter a name for the virtual machine. Click Next.

5. You may need to select the Virtual Machine Version, depending on your host. Select the version. Click Next.

6. Select Linux for the Guest Operating System, then select CentOS 32-bit, if available, from the Version drop-down. If CentOS 32-bit is not available, select Other Linux (32-bit). Click Next.

7. Set the number of virtual processors based on the size of your configuration. Click Next.

8. Adjust the amount of memory allocated for the virtual machine to at least the minimum required. Click Next.

9. Select LSI Logic Parallel for the SCSI Controller. Click Next.

10. Select "Create a new virtual disk." Click Next.

11. Set the Disk Capacity 160GB (based on your datastore selection early) and select "Store with the virtual machine". Click Next.

12. Leave all advanced options at default. Click Next.

13. Select the "Edit virtual machine settings before completion" checkbox, then click Continue. The New Virtual Machine - Virtual Machine Properties dialog appears. Select New CD/DVD in the Hardware/Summary panel.

14. In the Device Type section, select the Data Store ISO radio button, then browse and select the datastore containing the ISO file. Click Finish to save drive and return to the main dialog.


68

15. Click Finish to create the virtual machine.


To load dcTrack™ onto the virtual machine:

1. Select VM and right click Edit Settings.

2. Select Options > Advanced > Boot Options and select Force BIOS Setup.

3. Click "Power on" to power up the virtual machine.

4. Click on "disk" at the top of the console window and select "Connect to ISO image on datastore".

5. Select the datastore

6. Select the dcTrack ISO.

7. Click on the Console tab.

8. Click inside console window,

9. Use the Esc key to get to main BIOS page.

10. Exit the BIOS by selecting Exit Discarding Changes and using the Enter key. The dcTrack Kickstart page opens.

11. Type 2 for a VMware installation and press Enter to begin installation.

12. When the installation completes, disconnect the ISO disk and press Enter to reboot the dcTrack virtual machine. The virtual machine reboots and displays a console prompt.

Restore Your Database



Once you have recreated your virtual machine, restore your database.

Note: Raritan recommends that dcTrack™ users with database backup files that exceed 2G should use either Internet Explorer® 9 or Chrome® to

restore a database.

To restore your database:



69

2. Click Data Backups in the Data Management section. The Data Backups page opens.

3. In the Restore a Backup Archive section, click Browse, then select a backup file.

4. Click Upload. The dcTrack data and configuration settings are restored to the backup's configuration settings, and the server is rebooted.

Run the Prerequisite Program (Optional)

When you launch dcTrack™, the application checks the client to make sure it meets the minimum system requirements. If this is the first time you are using dcTrack, you must install the prerequisites program. The prerequisites program installs all of the software required to use dcTrack on your local machine. This includes:



dcTrack shared components

PostgreSQL ODBC drivers

PostgreSQL ADO drivers

To run the prerequisites program:

1. Connect to dcTrack using a web browser on any machine on the network.

2. In the browser's address bar, enter the IP address assigned to dcTrack. For example: http://192.168.1.10


4. Select Install Prerequisites for Classic View from the Administration menu to download the dcTrackPrereqs.exe file and save it to your machine.

5. Once the program is downloaded, run the dcTrackPrereqs.exe by double-clicking on it.

6. Click Install on the first dialog of the install wizard.

7. Optionally, select the 'Set MC Access security mode to low' on the 'Setting MS Access 2003 security mode' dialog. Click Next.

Note: If you do not set the Microsoft Access security mode to low, dcTrack still works but security warnings are displayed each time you launch dcTrack. You must then answer all questions about blocking unsafe expressions with "No". If you set the security mode to low but want to change to a higher level later, see your Microsoft Access



70

8. If you are using Firefox® as your browser, you must install the Firefox .NET Framework add-on. Check the 'Install Mozilla Firefox .NET Framework assistant add-on' checkbox and click Next.

If you are not using Firefox and are not planning on using it in the future, you do not need to install this add-on.

9. Click Finish on the last dialog. All of the components required to run dcTrack are installed.


After installing dcTrack™, you must configure the system for access over the network.

To configure the system for access over the network:

1. Access the local port from the Console tab of the VMware Infrastructure Client.

2. When prompted to log in, use the username config and the password raritan. The dcTrack configuration page opens.

3. Select Networking Setup, then select Setup LAN 1 to configure the primary Ethernet port.

4. Press the Space bar to select Enable this LAN Port.

5. To manually assign the network settings to dcTrack, deselect Use DHCP. Type the IP address, network masks, and gateway into the appropriate fields. If using DHCP, note the address. There must be a DHCP server available on the LAN.

6. Select Accept to reset the network interface with the new values.

7. If you are using a second network interface, select Setup LAN 2 from the Network Configuration menu and configure the secondary Ethernet port in the same manner as the first. Optional

8. Select Ping Network Test to ensure that dcTrack can communicate over the network. Optional

9. Setup the Name Servers under Network Configuration. If you do not setup the Name Server, DNS names cannot be resolved. Optional

10. In order to increase the secure access to dcTrack, it is advisable to disable SSH remote access to dcTrack. To disable SSH remote access to dcTrack, select System Services. Deselect Enable SSH. By default, the config account has access to dcTrack. SSH is re-enabled if a support connection is created. Optional

11. Select Exit from the main menu. You can now access dcTrack from any client on the network.


71

Prerequisites and Important Notes - Updating Power IQ with dcTrack Items

In order to import floor PDUs, each PDU must have a comm port with an assigned IP address

The synch process may take some time to complete depending on the amount of data being synched, your bandwidth, the number of floor PDUs being imported, and so on

Synching floor PDUs can take up to 30 seconds for each floor PDU because Power IQ must first poll each PDU, then send data back to dcTrack

The synch continues even if you leave the Power IQ Integration page, but the screen locks and you cannot stop the synch once the page is locked. This prevents other users who may access the application from disrupting the synch process

If you have configured dcTrack to automatically time out and log off, keep your session active during the synch or change the User Session Timeout period on the Other Security Administration Settings page to Never for the duration of the synch process

If a session does time out and you are logged off, you must restart the synch process. The data that was imported before the session timeout exists in Power IQ, so the process does not need to import that data again once it is restarted


Follow the steps provided here if have already installed dcTrack™ and are using the application, and you are now adding a new installation of Power IQ for the first time.

This process exports dcTrack data to Power IQ, thereby synching the data in the two applications.

Important: In order to maintain data integrity, once Power IQ and dcTrack data have been synched, all items must be added and updated in dcTrack. Do not add or update items in Power IQ once they are synched with dcTrack.

Power IQ does not track the make and model of racks. Since dcTrack does track this information, you must manually map the make and model of each item during the import.

If you have a large number of devices to import into Power IQ, mapping each item's make and model may be time consuming. Raritan recommends the following steps to reduce the amount of mapping required:

1. Create a spreadsheet of your Power IQ items using a dcTrack Import Wizard template.

2. Map the makes and models of your Power IQ items in the spreadsheet.


72

3. Use the Import Wizard to import the mapped items into dcTrack .

4. Click Update Power IQ in the Power IQ Wizard to import your dcTrack items into Power IQ.

See Adding Data Using the Import Wizard or Manually (on page 151).

Before you begin:

At a minimum, racks must exist in Power IQ to map data between Power IQ and dcTrack.

To update Power IQ with dcTrack items:

1. Log in to dcTrack.

2. From the Web Client, click Administration > dcTrack Settings. The Power IQ Integration Settings page opens.

3. Check the Enable Power IQ Integration checkbox to enable the synch function.

4. In the Power IQ Appliance Address field, enter the IP address or hostname of your Power IQ appliance.

5. Enter your Power IQ username and password in the Web Services Username field and Web Services Password field, respectively.

Note: You must belong to the admin group or be the configured web_api user.

6. Test your connection from dcTrack to the Power IQ appliance by clicking Test Connection. Optional

7. Click Save.

8. Once you are ready to begin the synch process, click Update Power IQ.

A progress bar is displayed throughout the process. The process may take some time to complete depending on the amount of data being imported.

Click Cancel at any time to stop the synch process. All of the data up to the point you canceled the synch process is now in Power IQ. The remaining data can be synched at a later time, as needed. A message is displayed at the bottom of the page once the process is complete.

9. Click Events to check the Events tab so you can locate any issues that may have arisen, such as missed items, items that were not mapped, and so on.


73

dcTrack 2.5 (and Later) Users

Follow the steps outlined here if you are a dcTrack™ 2.5 (and later) user who is adding Power IQ. See Important Notes on Importing Data Using the Power IQ Import Wizard (on page 83), VM and Client Requirements and Preparing to Install dcTrack before you begin.

Important: Before you begin an upgrade from dcTrack 2.5 to 3.0, you must disable Data Backup Encryption feature in the Security and Encryption section of the Settings page if you have enabled it. See Important - Disable Data Backup Encryption in dcTrack 2.5 (on page 75).

This use case includes the following steps:

Upgrade to the Current Version of dcTrack (on page 75)

Back Up Your dcTrack Database (on page 66)

Update Power IQ with dcTrack Items (on page 71)

For a checklist you can print and use to check off steps as you completed them, see Checklist - dcTrack 2.5 (and Later) Users Integrating with a New Power IQ Installation (on page 73).


74

Checklist - dcTrack 2.5 (and Later) Users Integrating with a New Power IQ Installation


Step Status

Important - Disable Data Backup Encryption in dcTrack 2.5

Change the Web Session Timeout for dcTrack Optional

Upgrade to the Current Version of dcTrack




Notes:


75

Important - Disable Data Backup Encryption in dcTrack 2.5

Data backup and encryption is not supported in dcTrack 3.0, so the Data Backup Encryption feature is disabled. If you are using the Data Backup Encryption feature in 2.5, disable it before you upgrade to 3.0.

If you leave this feature enabled when upgrading to dcTrack 3.0 and then back up the 3.0 database, the 3.0 backups are also encrypted. This may cause serious data corruption.

To disable the Data Backup Encryption feature in dcTrack 2.5:

1. On the Settings page, click Data Backup Encryption in the Security and Encryption section. The Backup Security Configuration page opens.

2. Select the No radio button for "Encrypt Backup?".

3. Click Save.

Change the Web Session Timeout for dcTrack


To change web session timeout for dcTrack:





Upgrade to the Current Version of dcTrack

dcTrack™ upgrades can take two hours or more to complete. As such, Raritan strongly recommends setting your session timeout to Never before beginning the upgrade process. See Change the Web Session Timeout for dcTrack (on page 64).

Customers currently on dcTrack 2.6.1 (or earlier) are advised to update to the latest available 2.x library before upgrading to dcTrack 3.0. See Step 1: Update the Models Library (on page 28).

Important: Before you begin an upgrade from dcTrack 2.5 to 3.0, you must disable Data Backup Encryption feature in the Security and Encryption section of the Settings page if you have enabled it.


76

Important: Do not reboot your dcTrack server before the upgrade is complete. Doing so causes your database to be corrupted.

To upgrade dcTrack:

1. First, if the Data Backup Encryption feature is enabled in dcTrack 2.5, disable it.

a. In the Web Client, click Administration > Settings. The Settings page opens in a secondary browser window.

b. On the Settings page in the Application Administration section, click Server Settings.

c. In the Authentication and Encryption Settings section, select the None radio button for "Encrypt method".

d. Click Save. Return to the Settings page.

2. In the Appliance Administration section, click Software Upgrades.

3. Click Browse, select the firmware file (usually a *.bin file).

4. Click Upload. The new firmware uploads to the application.


77




Best Practice:















78

Prerequisites and Important Notes - Updating Power IQ with dcTrack Items

In order to import floor PDUs, each PDU must have a comm port with an assigned IP address

The synch process may take some time to complete depending on the amount of data being synched, your bandwidth, the number of floor PDUs being imported, and so on

Synching floor PDUs can take up to 30 seconds for each floor PDU because Power IQ must first poll each PDU, then send data back to dcTrack

The synch continues even if you leave the Power IQ Integration page, but the screen locks and you cannot stop the synch once the page is locked. This prevents other users who may access the application from disrupting the synch process

If you have configured dcTrack to automatically time out and log off, keep your session active during the synch or change the User Session Timeout period on the Other Security Administration Settings page to Never for the duration of the synch process

If a session does time out and you are logged off, you must restart the synch process. The data that was imported before the session timeout exists in Power IQ, so the process does not need to import that data again once it is restarted


Follow the steps provided here if have already installed dcTrack™ and are using the application, and you are now adding a new installation of Power IQ for the first time.

This process exports dcTrack data to Power IQ, thereby synching the data in the two applications.


Power IQ does not track the make and model of racks. Since dcTrack does track this information, you must manually map the make and model of each item during the import.

If you have a large number of devices to import into Power IQ, mapping each item's make and model may be time consuming. Raritan recommends the following steps to reduce the amount of mapping required:

1. Create a spreadsheet of your Power IQ items using a dcTrack Import Wizard template.


79

2. Map the makes and models of your Power IQ items in the spreadsheet.

3. Use the Import Wizard to import the mapped items into dcTrack .

4. Click Update Power IQ in the Power IQ Wizard to import your dcTrack items into Power IQ.

See Adding Data Using the Import Wizard or Manually (on page 151).

Before you begin:

At a minimum, racks must exist in Power IQ to map data between Power IQ and dcTrack.

To update Power IQ with dcTrack items:

1. Log in to dcTrack.







7. Click Save.






80

Integrating an Existing Power IQ Installation with a New dcTrack Installation

Follow these steps if you already have Power IQ installed and are using the application, and you are now adding dcTrack™ for the first time.

This use case includes the following steps:

Upgrade to the Current Version of Power IQ (on page 82)

Install dcTrack (on page 87)

Add Remaining dcTrack Items to Power IQ (on page 95)

Before you begin, we recommend you review Important Notes on Importing Data Using the Power IQ Import Wizard (on page 83).

For a checklist you can print and use to check off steps as you completed them, see Checklist - Existing Power IQ Installation with a New dcTrack Installation (on page 80).


81

Checklist - Existing Power IQ Installation with a New dcTrack Installation


Step Status

Change the Web Session Timeout for Power IQ

Back Up Your Power IQ Database

Upgrade to the Current Version of Power IQ

Import Power IQ Data in dcTrack

Install dcTrack


Notes:


82

Change the Web Session Timeout for Power IQ


To change the web session timeout in Power IQ:

1. In Power IQ, click on the Settings tab.




Back Up Your Power IQ Database


If your database is large, consider changing the application timeout to Never in order to avoid the system timing out. Change this setting back to your desired timeout period once the process is completed. See Change the Web Session Timeout for Power IQ (on page 81).

To back up your Power IQ database:

1. Log in to Power IQ.

2. In the Settings tab, click Data Backups in the Data Management section.


Upgrade to the Current Version of Power IQ

Before you integrate dcTrack™ and Power IQ, upgrade to the current version of Power IQ.

Upgrades can take a significant amount of time to complete. As such, Raritan strongly recommends setting your session timeout to Never before beginning the upgrade process. See Change the Web Session Timeout for Power IQ (on page 81).

Important: Do not reboot your Power IQ server before the upgrade is complete. Doing so causes your database to be corrupted.


83

To upgrade Power IQ:


2. In the Settings tab, click Software Upgrades in the Appliance Administration section. The Upgrade page opens.



Import Power IQ Data into dcTrack

Because the processes described in this section may take some time to complete, be sure your application session timeout is set to Never. Once the import is complete, change the session timeout as needed. See Change the Web Session Timeouts in Power IQ and dcTrack (on page 89).

Important Notes on Importing Data Using the Power IQ Import Wizard

Following are notes on synching dcTrack and Power IQ using the Power IQ Import Wizard in Classic View.

Important: Once you begin the import process, data is immediately written to the dcTrack database and the process cannot be stopped once it has begun.

Before You Begin

Raritan recommends you do the following before you begin the process:

Make a backup of your database

Review the data to be imported, and make sure it is accurate and current

Create a rack under the data center in Power IQ. Without this, Power IQ will not be available in the Import Wizard

General Information

The best practice is to do as stated so that the action can be reversed by deleting the session. Sessions are only created if 2 or more items are added at a time. You can import one item at a time but you cannot delete through the wizard only via normal means of deleting unapproved item from item screen

As a best practice:

First add all racks at the rack level, then import all IT items at the device level. By doing this, you can delete the session if needed

Make sure the import job contains two or more items at the same level


84

Make sure two or more racks are imported as part of the import job

dcTrack does not rename Power IQ data centers when they are imported into dcTrack

dcTrack renames racks and items that are added to dcTrack from Power IQ

dcTrack uses ALL CAPS for item names

Data center names, floors and room names that exceed 20 characters are truncated. For example, Data Center - Headquarters - Somerset, NJ becomes Data Center - Headqu

If two items have the same name and exceed 20 characters, the second item is made up of the first 17 characters followed by a number in parenthesis. For example, Cisco MDS 9222i Multiservice Modular Switch becomes CISCO MDS 9222I M(1)

All items that are imported are in a Planned state. Move the items to an Installed by selecting an import session and clicking Approve

If a make and model are not applied to a rack, those racks remain in a Planned state and cannot be move to Installed until makes and models are mapped to the racks

Power IQ PDU outlets are not imported using the Power IQ Import Wizard. You must add them manually once you have imported all your racks and items

PDU IP addresses are imported using the Power IQ Import Wizard, but IT device IP address and community strings are not imported using the wizard

If a Power IQ PDU or IT device is mapped to a dcTrack rack PDU, device, network or probe, the Power IQ item name is used

Timestamp and site are used to indicate individual import jobs

Each import is tracked by timestamp, so it is important to remember what you have done sequentially

dcTrack does not display specific changes that occurred for each import

dcTrack asks if you want to delete items/racks from both Power IQ and dcTrack, or only from dcTrack

Import multiple items in one import vs. importing items one at a time. Adding items one at a time is not recommended since if a mistake is made during the process, nothing is imported


85

Integrate Power IQ Data with dcTrack Using the Power IQ Wizard

Use the Power IQ wizard in dcTrack™ Classic View to import Power IQ data into dcTrack in order to integrate the two applications.

Note that you must be using Power IQ 3.1 or later, and dcTrack 3.0 or later.



To integrate dcTrack and Power IQ data:

1. Configure the necessary Power IQ settings:

a. Log in to Power IQ.

b. On the Settings tab in the Data Management section, click ODBC Access. The Configure ODBC Database Access page opens.

c. Click Add, then double-click the 0.0.0.0/0 addresses to enter edit mode and type the ODBC network address with the mask in CIDR format.

CIDR format example: 192.168.43.0/24 instead of 192.168.43.0 and 255.255.255.0.

Use the network mask value to specify a single address or a range of addresses.

Use the default value 0.0.0.0/0 to allow access from all IP addresses.

d. Repeat to add new addresses as needed. Select an address and click Remove to remove authorization from the address.

e. Click Save when all authorized addresses have been added. The Power IQ database restarts.

After the restart, ODBC compliant applications are allowed to access the database from the authorized IP addresses.

2. Log in to the dcTrack Web Client.

a. From the Web Client, click Administration > dcTrack Settings. The Power IQ Integration Settings page opens.

b. Check the Enable Power IQ Integration checkbox to enable the synch function.


86

c. In the Power IQ Appliance Address field, enter the IP address or hostname of your Power IQ appliance.

d. Enter your Power IQ username and password in the Web Services Username field and Web Services Password field, respectively.


e. Test your connection from dcTrack to the Power IQ appliance by clicking Test Connection. Optional

f. Click Save.

3. Open Classic View.

a. In Classic View, click Administration > Wizards > Power IQ.

b. Review the information for each step.

c. Click Begin.

d. Proceed through each step of the wizard, adding and mapping Power IQ and dcTrack items. Mapping may require you to add makes and models, and/or map similar but not identical information. For example, Power IQ may use the term 'Cisco' and dcTrack uses 'Cisco Systems'. These two terms need to be mapped manually.

e. Once the import is completed, select an import session from the Select a Session drop-down, and map any items that are not mapped.

f. Once all data is mapped, click Approve to approve the imported items and add them to dcTrack.

g. Delete the import by selecting it from the Select a Session drop-down and clicking Delete.


87

Install dcTrack

At this point, you are installing dcTrack™ in order to integrate with your Power IQ installation. Details on the installation can be found in the Installation Steps (on page 15) section of the guide. Installation includes:

Create the dcTrack Virtual Machine (on page 16)

Load dcTrack onto the Virtual Machine (on page 17)

Run the Prerequisite Program (Optional) (on page 18)

Initial Configuration of dcTrack (on page 19)

Log In to dcTrack for the First Time (on page 20)

Change the Administrator Password (on page 23)

Configure the System Clock (on page 24)

Configure NTP Server Settings (on page 24)

Integrating an Existing dcTrack Installation with an Existing Power IQ Installation

Follow the steps provided here if you are currently using dcTrack™ 2.6 and Power IQ 3.1 or higher as separate applications, and are now integrating the two.

Integrate the two applications using the Power IQ Import wizard accessed in Classic View. This ensures each level of the Power IQ data model is mapped to the dcTrack model. See dcTrack Architecture and Data Model (on page 121) for more information on each data model.

For a checklist you can print and use to check off steps as you completed them, see Checklist - Existing dcTrack Installation with an Existing Power IQ Installation (on page 87).


88

Checklist - Existing dcTrack Installation with an Existing Power IQ Installation


Step Status

Change the Web Session Timeouts in Power IQ and dcTrack

Back Up Your Power IQ and dcTrack Databases

Upgrade to the Current Versions of Power IQ and dcTrack


Add Remaining dcTrack Items to Power IQ


Notes:


89

Change the Web Session Timeouts in Power IQ and dcTrack


You need to change the session timeouts for both Power IQ and dcTrack.

To change the web session timeout in Power IQ:

1. In Power IQ, click on the Settings tab.




To change web session timeout in dcTrack:





Back Up Your Power IQ and dcTrack Databases

Back up both your Power IQ and dcTrack™ databases before you begin the integration.

To back up your Power IQ database:


2. In the Settings tab, click Data Backups in the Data Management section.

3. In the Backup Archives section, click Create. The file is created and added at the top of the list. Data Backups in the Data Management section.



90


Best Practice:













Upgrade to the Current Versions of Power IQ and dcTrack

Before you integrate dcTrack™ and Power IQ, upgrade to the current versions of both applications.

Upgrades can take a significant amount of time to complete. As such, Raritan strongly recommends setting your session timeout to Never before beginning the upgrade process.

Important: Do not reboot your Power IQ or dcTrack server(s) before the upgrades are complete. Doing so causes your database to be corrupted.


91

Power IQ Upgrade

To upgrade Power IQ:


2. In the Settings tab, click Software Upgrades in the Appliance Administration section. The Upgrade page opens.



dcTrack Upgrade

Customers currently on dcTrack 2.6.1 (or earlier) are advised to update to the latest available 2.x library before upgrading to dcTrack 3.0.

Important: Before you begin an upgrade from dcTrack 2.5 to 3.0, you must disable Data Backup Encryption feature in the Security and Encryption section of the Settings page if you have enabled it.

To do this:

a. In the Web Client, click Administration > Settings. The Settings page opens in a secondary browser window.

b. On the Settings page, click Server Settings in the Application Administration section. The Backup Security Configuration page opens.

c. In the Encryption & Authentication Settings section, select the None radio button for "Encrypt method".

d. Click Save. Return to the Settings page.

To upgrade dcTrack:


2. In the Appliance Administration section, click Software Upgrades.




Because the processes described in this section may take some time to complete, be sure your application session timeout is set to Never. Once the import is complete, change the session timeout as needed. See Change the Web Session Timeouts in Power IQ and dcTrack (on page 89).


92

Important Notes on Importing Data Using the Power IQ Import Wizard

Following are notes on synching dcTrack and Power IQ using the Power IQ Import Wizard in Classic View.


Before You Begin

Raritan recommends you do the following before you begin the process:

Make a backup of your database

Review the data to be imported, and make sure it is accurate and current

Create a rack under the data center in Power IQ. Without this, Power IQ will not be available in the Import Wizard

General Information

The best practice is to do as stated so that the action can be reversed by deleting the session. Sessions are only created if 2 or more items are added at a time. You can import one item at a time but you cannot delete through the wizard only via normal means of deleting unapproved item from item screen

As a best practice:

First add all racks at the rack level, then import all IT items at the device level. By doing this, you can delete the session if needed

Make sure the import job contains two or more items at the same level

Make sure two or more racks are imported as part of the import job


93

dcTrack does not rename Power IQ data centers when they are imported into dcTrack

dcTrack renames racks and items that are added to dcTrack from Power IQ

dcTrack uses ALL CAPS for item names

Data center names, floors and room names that exceed 20 characters are truncated. For example, Data Center - Headquarters - Somerset, NJ becomes Data Center - Headqu

If two items have the same name and exceed 20 characters, the second item is made up of the first 17 characters followed by a number in parenthesis. For example, Cisco MDS 9222i Multiservice Modular Switch becomes CISCO MDS 9222I M(1)

All items that are imported are in a Planned state. Move the items to an Installed by selecting an import session and clicking Approve

If a make and model are not applied to a rack, those racks remain in a Planned state and cannot be move to Installed until makes and models are mapped to the racks

Power IQ PDU outlets are not imported using the Power IQ Import Wizard. You must add them manually once you have imported all your racks and items

PDU IP addresses are imported using the Power IQ Import Wizard, but IT device IP address and community strings are not imported using the wizard

If a Power IQ PDU or IT device is mapped to a dcTrack rack PDU, device, network or probe, the Power IQ item name is used

Timestamp and site are used to indicate individual import jobs

Each import is tracked by timestamp, so it is important to remember what you have done sequentially

dcTrack does not display specific changes that occurred for each import

dcTrack asks if you want to delete items/racks from both Power IQ and dcTrack, or only from dcTrack

Import multiple items in one import vs. importing items one at a time. Adding items one at a time is not recommended since if a mistake is made during the process, nothing is imported

Integrate Power IQ Data with dcTrack Using the Power IQ Wizard

Use the Power IQ wizard in dcTrack™ Classic View to import Power IQ data into dcTrack in order to integrate the two applications.

Note that you must be using Power IQ 3.1 or later, and dcTrack 3.0 or later.

Important: Once you begin the import process, data is immediately written to the dcTrack database and the process cannot be stopped


94

once it has begun.


To integrate dcTrack and Power IQ data:

1. Configure the necessary Power IQ settings:

a. Log in to Power IQ.

b. On the Settings tab in the Data Management section, click ODBC Access. The Configure ODBC Database Access page opens.

c. Click Add, then double-click the 0.0.0.0/0 addresses to enter edit mode and type the ODBC network address with the mask in CIDR format.

CIDR format example: 192.168.43.0/24 instead of 192.168.43.0 and 255.255.255.0.

Use the network mask value to specify a single address or a range of addresses.

Use the default value 0.0.0.0/0 to allow access from all IP addresses.

d. Repeat to add new addresses as needed. Select an address and click Remove to remove authorization from the address.

e. Click Save when all authorized addresses have been added. The Power IQ database restarts.

After the restart, ODBC compliant applications are allowed to access the database from the authorized IP addresses.

2. Log in to the dcTrack Web Client.

a. From the Web Client, click Administration > dcTrack Settings. The Power IQ Integration Settings page opens.

b. Check the Enable Power IQ Integration checkbox to enable the synch function.

c. In the Power IQ Appliance Address field, enter the IP address or hostname of your Power IQ appliance.

d. Enter your Power IQ username and password in the Web Services Username field and Web Services Password field, respectively.



95

e. Test your connection from dcTrack to the Power IQ appliance by clicking Test Connection. Optional

f. Click Save.

3. Open Classic View.

a. In Classic View, click Administration > Wizards > Power IQ.

b. Review the information for each step.

c. Click Begin.

d. Proceed through each step of the wizard, adding and mapping Power IQ and dcTrack items. Mapping may require you to add makes and models, and/or map similar but not identical information. For example, Power IQ may use the term 'Cisco' and dcTrack uses 'Cisco Systems'. These two terms need to be mapped manually.

e. Once the import is completed, select an import session from the Select a Session drop-down, and map any items that are not mapped.

f. Once all data is mapped, click Approve to approve the imported items and add them to dcTrack.

g. Delete the import by selecting it from the Select a Session drop-down and clicking Delete.

Add Remaining dcTrack Items to Power IQ

When you integrate an existing Power IQ application with an existing dcTrack™ application, if you were maintaining more items in dcTrack than you were maintaining in Power IQ before you integrated, the remaining dcTrack items must be added to Power IQ.

For example, if you only maintained PDUs in Power IQ for Site A, but maintained servers and so on for Site A in dcTrack, those additional dcTrack items must be added to Power IQ.

Raritan recommends you perform this step as a best practice to better ensure data integrity.

To do this, synch dcTrack and Power IQ from the Power IQ Integration Settings page in the Web Client, or add the items manually to dcTrack (once added to dcTrack, the items are automatically added to Power IQ).

To add remaining dcTrack items to Power IQ:





96




6. Click Save.






97

Integrating dcTrack with AMS via EMX or PX2

Overview

dcTrack™ allows you to track the location of data center items at the rack level. This is accomplished using Raritan asset management tags (AMT) that are adhered to the data center item at one end, and plugged into a Raritan asset management sensor (AMS) from the other end. Each AMT has a unique ID that is used to identify the data center item the AMT is adhered to. These asset sensors are connected to either a Raritan PX2 or Raritan EMX, and the Raritan asset sensor device is added to dcTrack.

Asset management tags (AMTs) are electronic IDs that are adhered to data center items so you can remotely track the item's location. AMTs are plugged in to an asset management sensor (AMS), and the AMS is then configured in either Raritan's PX2 or EMX.

The PX2 or EMX that is managing the asset sensor is added to dcTrack as a rack PDU item for PX2 devices, or as a probe item for EMX devices. Power IQ then receives location data via the IP connection to the PX2 or EMX. dcTrack polls Power IQ every few minutes to pull in new data and display it.

dcTrack recognizes the PX2 as a rack PDU, and an EMX as a probe. When you add these devices to dcTrack, it is important you assign them to the correct item type in order for them to be recognized and information retrieved.


98

Diagram key

Asset management tag (AMT)

One end of the AMT is affixed to the item and the other end is plugged into the AMS

Asset management sensor (AMS)

The AMS RJ-45 connector is connected to the PX using a Cat 5e/6 cable

PX or EMX

The PX is added to dcTrack as a rack PDU, then connects to dcTrack via an IP connection

The EMX is added to dcTrack as a probe, then connects to dcTrack via an IP connection

dcTrack/Power IQ

The items the asset tags are adhered to must be tracked as part of the dcTrack asset management workflow, just as with any other device in the data center. This allows dcTrack to manage and monitor the status of the items the tags are adhered to.

When tags are adhered to an item and plugged in to the asset sensor, the tag ID of the asset management sensor is automatically updated in dcTrack.

Note: There may be a short delay between when the asset tag is plugged in to the asset sensor and when that information becomes available in dcTrack.


99

EMX Asset Sensor Management

Before asset sensors can be managed in dcTrack™, they must be configured in EMX, the EMX needs to be added to dcTrack as a probe item, and the data center item the asset management tag is adhered to must exist in dcTrack.

dcTrack supports the EMX2-111 and EMX2-888 models.

Note: dcTrack does not support asset management blade extension strips.

If you have a large number of EMXs to add, consider using the Import Wizard. See Import Wizard.

For a checklist you can print and use to check off steps as you completed them, see Checklist - Integrating EMX Asset Sensors (on page 99).


100

Checklist - Integrating EMX Asset Sensors


Step Status

Connecting Asset Sensors to the EMX

Configuring Asset Sensors in EMX

Setting dcTrack Asset Sensor LED Colors (Optional)

Adding an EMX to dcTrack

Adding AMT Tracked Items to dcTrack


Notes:


101

Connecting Asset Sensors to the EMX

You need both asset sensors and asset tags for tracking devices. Asset tags, which are adhered to devices, provide an ID number for each device, while the asset sensors transmit ID numbers and positioning information to the connected EMX device.

The following diagram illustrates an asset tag.

Letter Item

Barcode (ID number), which is available on either end of the asset tag

Tag connector

Adhesive area with the tape

Note: The barcode of each asset tag is unique and is displayed in the

EMX web interface so it can easily be identified.


102

Connecting an Asset Sensor to the EMX-111

The EMX-111 does not natively support the 12 volts of power needed to connect to asset management sensors via a Category 5e/6 cable. Distances greater than 1 to 10 meters require the use of a Raritan 12V Feature Port X-Cable along with a Category 5e/6 cable to connect to asset management strips.

Diagram key

Asset management tags

Asset management strip


103

Diagram key

EMX-111

Category 5e/6 cable (Cat5e/6 cable)

12V Feature Port X-Cable (X-cable)

To connect asset sensors to the EMX-111 device:

1. Affix the adhesive end of an asset tag to each IT device through the tag's tape.

2. Plug the connector on the other end of each asset tag into the corresponding tag port on the asset sensor.

3. Connect one end of a Cat5e/6 cable to the RJ-45 connector on the MASTER asset sensor. The EMX-111 supports a maximum of 10-meters of cable connecting each asset sensor assembly.

4. Connect the other end of the Cat5e/6 cable into the in-line Cat5e/6 connector on the X-cable.

5. Connect the ethernet end of the X-cable into the FEATURE port on the EMX-111 device.

6. Plug the sensor cable of the X-cable into the SENSOR port on the EMX-111. This supplies power to the asset sensor assembly from the SENSOR port via the Cat5e/6 cable.

Note: If sensors need to be connected to the EMX via the SENSOR port, plug them into the SENSOR connector on the X-cable. If no

sensors are connected, this connector can remain empty.

7. Configure the asset sensor. See Configuring Asset Sensors in EMX (on page 105).

All LEDs on the asset sensor assembly may cycle through different colors during the power-on process if the asset sensor's firmware is being upgraded by the EMX device. After the power-on or firmware upgrade process completes, the LEDs show solid colors. Note that the LED color of the tag ports with asset tags connected will be different from the LED color of the tag ports without asset tags connected.


104

Connecting an Asset Sensor to the EMX-888

The EMX-888 can connect to an asset management sensor via a Category 5e/6 cable up to a distance of 10 meters.

Note: The EMX-888 does not require the use of a Raritan 12V Feature Port X-Cable like the EMX-111.

Diagram key

Asset management tags

Asset management strip

EMX-888

Category 5e/6 cable (Cat5e/6 cable)


105

To connect asset sensors to the EMX-888 device:



3. Connect one end of a Cat5e/6 cable to the RJ-45 connector on the MASTER asset sensor, and then connect the other end of the cable into a FEATURE port on the EMX-888.

4. If needed, repeat the above steps to connect additional asset sensors to the rest of FEATURE ports.

5. Configure the asset sensor. See Configuring the Asset Sensor.

Configuring Asset Sensors in EMX

The EMX cannot detect how many rack units (tag ports) a connected asset management sensor supports, so you must provide this information manually.

When you add an asset management sensor, you name it. The customized name is followed by the label in parentheses.

Note: A label refers to the port number where the asset sensor is connected. See Connecting Asset Sensors to the EMX (on page 100)

for information on connecting asset sensors.

To configure asset sensors:

1. If you have not already done so, log in to the EMX.

2. Connect the asset sensor to the EMX if it is not already.

3. Click on the Feature Ports folder in the navigation tree to expand it.

4. Click the desired asset sensor. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports).

Note: You can also access this dialog by double-clicking the asset sensor shown on the Dashboard page.

5. Click Setup in the Settings section. The Setup of Asset Strip dialog appears.

6. Enter a name for the asset sensor.

7. In the "Number of Rack Units" field, type the total number of rack units supported by the AMS. Default is 48.

8. Here, rack units are the number of asset management tag ports on the asset management strip. For example, if the AMS has 48 asset management tag ports, it supports up to 48 rack units on a cabinet.


106

9. Determine how to number all rack units on the asset sensor by selecting an option in the Numbering Mode.

Top-Down: The rack units are numbered in the ascending order from the highest to the lowest rack unit.

Bottom-Up: The rack units are numbered in the descending order from the highest to the lowest rack unit.

Raritan strongly suggests you select Bottom-Up as the numbering for the rack units because dcTrack numbers rack units from the bottom-up, where rack units are numbered in the descending order from the highest to the lowest rack unit. For example, the top rack unit may be 48 and the bottom rack unit is 1.

10. In the Numbering Offset field, select the starting number. For example, if you select 3, the first rack unit is numbered 3, the second is numbered 4, the third is numbered 5, and so on until the final number.

11. Indicate how the asset sensor is mounted on the rack in the Orientation field. The rack unit that is most close to the RJ-45 connector of the asset sensor will be marked with the index number 1 in the web interface.

For the latest version of asset sensors with a built-in tilt sensor, it is NOT necessary to configure the orientation setting manually. The EMX device can detect the orientation of the asset sensors and automatically configure it.

Top Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located on the top.

Bottom Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom.

12. To change the LED color denoting the absence of a connected tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color without connected Tag" field.

13. Click OK to save the changes.

See the EMX Help for additional information on using the EMX device.

Setting EMX Asset Sensor LED Colors (Optional)

In the EMX web interface, a rack unit refers to a tag port on the asset sensor. You can name a specific rack unit, or change its LED color settings so that this LED behaves differently from others on the same asset sensor.

Note: This step is optional.

To change an LED's settings:



107





5. Select the rack unit whose LED settings you want to change.

6. Click Configure Rack Unit or double-click the selected rack unit. The setup dialog for the selected rack unit appears.

7. In the Name field, type a name for identifying this rack unit.

8. Select either Auto or Manual Override as this rack unit's LED mode.

Auto (based on Tag): This is the default setting. With this option selected, the LED follows the global LED color settings.

Manual Override: This option differentiates this LED's behavior. After selecting this option, you must select an LED mode and/or an LED color for the selected rack unit.

LED Mode: Select On to have the LED stay lit, Off to have it stay off, "Slow blinking" to have it blink slowly, or "Fast blinking" to have it blink quickly.

LED Color: If you select On, "Slow blinking" or "Fast blinking" in the LED Mode field, select an LED color by either clicking a color in the color palette or typing the hexadecimal RGB value of a color in the accompanying text box.


Adding an EMX to dcTrack

Once the asset management sensor has been connected to and configured in EMX, add the EMX to dcTrack™ as a probe. Items are manually added to dcTrack in the Web Client, or using the Import Wizard in Classic View.

Following are the steps for adding a single EMX to dcTrack along with its asset management sensors in. If you have a large number of EMXs and asset management sensors to add to dcTrack, consider using the Import wizard to import multiple devices at once. See Using the Import Wizard (on page 153).

Important: dcTrack recognizes EMX devices as probes, so it is important to add them as such.


108

The EMX goes through the asset management workflow just like any other item that is added to dcTrack. However, asset sensor readings are available immediately in dcTrack once they are attached to the EMX.

To add the EMX to dcTrack as a probe:

1. If you are using SNMP to pull data from the EMX, PowerIQ Integration must be enabled in the Web Client. Click Administration > dcTrack Settings, then select Enable Power IQ Integration. If you are not using SNMP, PIQ Integration does not need to be enabled and you can proceed with adding the EMX.

Alternatively, enable PowerIQ Integration to pull information from the EMX via Power IQ. See Power IQ Integration Settings (Synching dcTrack and Power IQ) (on page 110) for instructions on enabling and configuring PowerIQ integration.

2. In the Web Client, select Asset Management > New Item or click the

Create New Item icon on the Items List page.

3. Select the Raritan as the make. Required

4. Select the EMX model. Required

5. Enter the EMX (probe) name. Required

6. Select the location the item is installed. Required

7. Select the cabinet and rail position of the probe. Required

8. Click Save. The item is now in a Planned state.

9. Submit an Install Item request by clicking on Actions > Install Item Request, then click OK on the install confirmation message.

Check the status of the request at any time from Classic View by clicking Change Control > Requests.

After the Gatekeeper has reviewed and approved the request, a work order to actually perform the task is issued by the Gatekeeper. Once the work order is marked as Complete in dcTrack, the action is considered complete. The Gatekeeper must then mark the request as Complete.

10. If login credentials are required to access the EMX or you are using SNMP on the EMX, add them to the EMX in Classic View.

11. Launch Classic View.

12. Select Environ. Items > Probes.

13. Double-click on the EMX in the list to open its Details 1 page.

14. Select Edit from the Page Mode drop-down.

15. On the Details 1 page, click the EMX Credentials and SNMP v3 Settings button to open the EMX Credentials and SNMP v3 Settings dialog.


109

Note: For SNMP v2, enter the SNMP v2 community string in the DataPort field for that probe when you create a data port.

a. Enter the username, password and password confirmation information for the login credentials (if applicable).

b. Enable or disable the use of the device's SNMPv3 settings.

16. Click Create Ports. The Create Ports dialog opens.

a. Select Asset Strip from the Port Type drop-down.

b. Enter a name for the port. Required

c. Select the cabinet and position of the port. Required

d. Enter comments as needed.

e. Click Create Port. A confirmation that the port was created is at the top of the dialog. Click Close.

17. Create a comm port for the EMX and assign it the IP address used to locate the device on the network. Click Create Ports in the Comm Ports section of the page. The Create Ports dialog appears.

Do one of the following:

Create the port manually or by selecting it from the port library.

a. Manually select or enter the port name in the Port Name drop-down, then select the connector, media, protocol and speed. Required

Or

If the port is available in the Port Library, it is displayed in the "Create from the Model's Port Definition in the Library" list at the bottom of the dialog. Select the appropriate port and click Use Selected.

a. Assign an IP address to the port. Required

To assign an IP address, select a subnet. This automatically assigns the first available address from the selected subnet. You can change the address by manually typing another address in the subnet, or using the drop-down to view all the available addresses in that subnet.

b. If needed, enter comments pertinent to the port.

c. Enter the community name used for SNMPv2 with this device.

d. Click Create Port.

18. Click Detail 2 to open the Detail 2 page for the EMX, then enter any additional information that is needed. Optional

19. Click Save. The saved item is tagged with a status of Planned.


110

Once the EMX exists in dcTrack, the asset management tag number is populated in dcTrack when it is plugged into the asset management sensor port that corresponds to the item's rack unit position in the cabinet. If the EMX exists and has an electronic asset tag number assigned to it, when the asset tag is plugged into the asset management sensor, dcTrack validates that the asset tag numbers match.

Note: The item's Detail page in dcTrack contains the Electronic Asset Tag field.

The asset management sensors that are detected by dcTrack are listed in the Temp/Humidity section of the Probes list page in Classic View.

After adding a Humidity/Temperature sensor to an EMX make sure that the Order column in the Sensor Ports table of the item's Detail page in Classic View is set exactly to the same order appearing in the EMX.

Power IQ Integration Settings (Synching dcTrack and Power IQ)

This feature eliminates the need to enter dcTrack™ data into Power IQ.

This is done by synching dcTrack and Power IQ so that data center items, such as, racks, PDUs, power associations and so on, are shared between the two applications.

After synching, all dcTrack items are added to Power IQ. Any items added to dcTrack after the synch are automatically added to Power IQ, and can be viewed in Power IQ by refreshing the page.


Synching applies to Power IQ users who are adding dcTrack. If you are an existing dcTrack user who is adding Power IQ, follow the steps outlined in Use Case 2: Integrating Power IQ with an Existing dcTrack Installation. Users who are current dcTrack and Power IQ users who now integrating the two applications follow the steps outlined in Use Case 4: Integrating an Existing dcTrack Installation with an Existing Power IQ Installation.

Before you begin the synch process, see Prerequisites and Important Notes - Updating Power IQ with dcTrack Items (on page 71).

To synch Power IQ and dcTrack:




111





6. Click Save.






112

Adding AMT Tracked Items to EMX

The data center item an asset management tag is adhered to must be added to dcTrack. Items are manually added to dcTrack in the Web Client, or using the Import Wizard in Classic View.

If the EMX already exist in dcTrack, the asset management tag number is populated when it is attached to the asset management strip at the item's rack unit position.

If the EMX exists and has an electronic asset tag number assigned to it, when the asset tag is attached, dcTrack validates that the asset tag numbers match.

The item's Details 2 page contains the Electronic Asset Tag field.

PX2 Asset Sensor Management

Before asset sensors can be managed in dcTrack™, they must be configured in PX2, the PX2 needs to be added to dcTrack as a rack PDU item, and the data center item the asset management tag is adhered to must exist in dcTrack.

If you have a large number of PX2s to add, consider using the Import Wizard. See Import Wizard.

For a checklist you can print and use to check off steps as you completed them, see Checklist - Integrating PX2 Asset Sensors (on page 112).


113

Checklist - Integrating PX2 Asset Sensors


Step Status

Connecting Asset Sensors to the PX2

Configuring Asset Sensors in PX2

Setting dcTrack Asset Sensor LED Colors Optional

Adding a PX2 to dcTrack

Adding AMT Tracked Items to dcTrack


Notes:


114

Connecting Asset Sensors to the PX

You need both asset sensors and asset tags for tracking devices. Asset tags, which are adhered to devices, provide an ID number for each device, while the asset sensors transmit ID numbers and positioning information to the connected PX device.

The following diagram illustrates an asset tag.

Letter Item

Barcode (ID number), which is available on either end of the asset tag

Tag connector

Adhesive area with the tape

Note: The barcode of each asset tag is unique and is displayed in the PX

web interface so it can easily be identified.

To connect asset sensors to the PX device:



3. Connect the asset sensor assembly on the rack to the PX device.

a. Connect one end of the Category 5e/6 cable to the RJ-45 connector on the MASTER asset sensor.

b. Connect the other end of the cable to the FEATURE port on the PX device.


115

The PX device supplies power to the asset sensor assembly through the Category 5e/6 cable. All LEDs on the asset sensor assembly may cycle through different colors during the power-on process if the asset sensor's firmware is being upgraded by the PX device. After the power-on or firmware upgrade process completes, the LEDs show solid colors. Note that the LED color of the tag ports with asset tags connected will be different from the LED color of the tag ports without asset tags connected.

Letter Item

The PX device

Asset sensors

Asset tags

IT devices, such as servers

Note: The PX cannot detect how many rack units the connected asset sensor(s) has. You must provide the information to it manually. See

Configuring the Asset Sensor in PX2 (on page 116).


116

Configuring the Asset Sensor in PX2

The PX2 cannot detect how many rack units (tag ports) a connected asset management sensor supports, so you must provide this information manually.

See Connecting Asset Sensors to the PX2 (see "Connecting Asset Sensors to the PX" on page 113) for information on connecting asset sensors.

To configure asset sensors:

1. If you have not already done so, log in to the PX2.

2. If the Feature Port folder is not expanded, expand it to show the device under the Feature Port folder.

3. Click the asset sensor in the left pane. The asset sensor's page opens in the right pane.

Note: The asset sensor is named "Asset Strip 1" by default. The name changes after being customized.

Tip: The same asset sensor's page can be also opened by clicking Feature Port in the left pane, and then double-clicking the asset

sensor in the right pane.

4. Click Setup. The setup dialog for the asset sensor appears.

Tip: You can also trigger the same dialog by clicking Asset Management in the left pane, and then clicking Asset Strip Setup or

double-clicking the asset sensor in the right pane.

5. To rename the asset sensor, type a new name in the Name field.

6. In the "Number of Rack Units" field, type the total number of rack units supported by the AMS. Default is 48.

7. Here, rack units are the number of asset management tag ports on the asset management strip. For example, if the AMS has 48 asset management tag ports, it supports up to 48 rack units on a cabinet.

8. In the Numbering Offset field, select the starting number. For example, if you select 3, the first rack unit is numbered 3, the second is numbered 4, the third is numbered 5, and so on until the final number.

9. Indicate how the asset sensor is mounted on the rack in the Orientation field. The rack unit that is most close to the RJ-45 connector of the asset sensor will be marked with the index number 1 in the web interface.


117

For the latest version of asset sensors with a built-in tilt sensor, it is NOT necessary to configure the orientation setting manually. The PX2 device can detect the orientation of the asset sensors and automatically configure it.

Top Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located on the top.

Bottom Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom.

10. Determine how to number all rack units on the asset sensor by selecting an option in the Numbering Mode.

Raritan strongly suggests you select Bottom-Up as the numbering for the rack units because dcTrack numbers rack units from the bottom-up, where rack units are numbered in the descending order from the highest to the lowest rack unit. For example, the top rack unit may be 48 and the bottom rack unit is 1.

11. Click OK.

See the PX2 Help for additional information on using the EMX device.

Setting EMX Asset Sensor LED Colors

Each LED on the asset sensor indicates the presence and absence of a connected asset tag by changing its color. You can configure or change the color settings for all LEDs on the connected asset sensor(s) by following the procedure below.

This feature is accessible only by users with Administrative Privileges.

To configure all LED colors:






5. Click Setup on the asset sensor page. The setup dialog for that asset sensor appears.

6. To change the LED color denoting the absence of a connected tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color without connected Tag" field.



118

Tip: To make a specific LED's color settings different from other LEDs, see Configuring a Specific Rack Unit.

Adding a PX2 to dcTrack

Once the asset management sensor has been connected to and configured in the PX2, add the PX2 to dcTrack™ as a rack PDU. Once the PX2 is added to dcTrack, attach the asset tag(s) to the device and plug them in to the asset sensor.

Following are the steps for creating a single PX2. If you have a large number of PX2s, consider using the Import wizard to import multiple devices at once. See Using the Import Wizard (on page 153) for details.

The PX2 goes through the change management workflow just like any other item that is added to dcTrack. However, asset sensor readings are available immediately in dcTrack once they are attached to the PX2.

Important: dcTrack recognizes PX2s as rack PDUs, so it is important to add them as such.

To add the PX2 to dcTrack as a rack PDU:

1. If you are using SNMP to pull data from the PX2, PowerIQ Integration must be enabled in the Web Client. Click Administration > dcTrack Settings, then select Enable Power IQ Integration. If you are not using SNMP, PIQ Integration does not need to be enabled and you can proceed with adding the PX2.

Alternatively, enable PowerIQ Integration to pull information from the PX2 via Power IQ. See Power IQ Integration Settings (Synching dcTrack and Power IQ) (on page 110) for instructions on enabling and configuring PowerIQ integration.



3. Select the Raritan as the make. Required

4. Select the PX2 model. Required

5. Enter the PX2 (rack PDU) name. Required


7. Select the cabinet and rail position of the probe. Required

Note: Twelve vertically mounted rack PDUs are supported per cabinet. Horizontally mounted/rack mounted rack PDUs do not apply

to this step since there is no side to select.

8. Click Save.


119

9. If login credentials are required to access the EMX or you are using SNMP on the EMX, add them to the EMX in Classic View.

10. Launch Classic View.

11. Select Power Items > Rack PDU.

12. Double-click on the PX2 in the list to open its Details 1 page.

13. Select Edit from the Page Mode drop-down in the toolbar.

14. If login credentials are required to access the PX2 or you are using SNMP on the PX2, click the EMX Credentials and SNMP v3 Settings button to open the PX2 Credentials and SNMP v3 Settings dialog.

a. Enter the username, password and password confirmation information for the login credentials (if applicable).

b. Enable or disable the use of the device's SNMP settings.

15. Click Create Ports. The Create Ports dialog opens.

a. Select Asset Strip from the Port Type drop-down.

b. Enter a name for the port. Required

c. Select the cabinet and position of the port. Required

d. Enter comments as needed.

e. Click Create Port. A confirmation that the port was created is at the top of the dialog. Click Close.

16. Create a comm port for the PX2 and assign it the IP address used to locate the device on the network. Click Create Ports in the Comm Ports section of the page. The Create Ports dialog appears.

a. Create the port manually or by selecting it from the port library:

Manually, select or enter the port name in the Port Name drop-down, then select the connector, media, protocol and speed. Required

Or

If the port is available in the Port Library, it is displayed in the "Create from the Model's Port Definition in the Library" list at the bottom of the dialog. Select the appropriate port and click Use Selected.

a. Assign an IP address to the port. Required

To assign an IP address, select a subnet. This automatically assigns the first available address from the selected subnet. You can change the address by manually typing another address in the subnet, or using the drop-down to view all the available addresses in that subnet.

b. If needed, enter comments pertinent to the port.

c. Enter the community name used for SNMPv2 with this device.

d. Click Create Port.


120

17. Click Save. The saved item is tagged with a status of Planned. The item appears in red on the cabinet elevation, which indicates that the item is new.

Adding Items to PX2

The data center item an asset management tag is adhered to must be added to dcTrack. Items are manually added to dcTrack in the Web Client, or using the Import Wizard in Classic View.

If the PX2 already exist in dcTrack, the asset management tag number is populated when it is attached to the asset management strip at the item's rack unit position.

If the PX2 exists and has an electronic asset tag number assigned to it, when the asset tag is attached, dcTrack validates that the asset tag numbers match.

The item's Details 2 page contains the Electronic Asset Tag field.

121

In This Chapter

dcTrack Architecture .............................................................................. 122 dcTrack Data Model .............................................................................. 123

Appendix A dcTrack Architecture and Data Model

Appendix A: dcTrack Architecture and Data Model

122

dcTrack Architecture

dcTrack™ uses a client-server architecture consisting of a back-end database and front-end application. The diagram shown here depicts the dcTrack client-server architecture with respect to the installation process.

Appendix A: dcTrack Architecture and Data Model

123

dcTrack Data Model

The dcTrack™ data model consists of:

Floor Plan Drawings - An AutoCAD® or Microsoft Visio® drawing in .dwg file format

Sites - A data center room. Multiple sites are supported by dcTrack.

Items - Assets within your data center. Items include cabinets, devices, networks, data and comm panels, UPS, floor PDUs, power outlets, rack PDUs, CRAC units and environmental probes

Ports - Data/communication and power ports. This includes data panel ports, power ports, breaker panel poles and environmental probe ports

Connections - Data/communication and power connections are made in dcTrack between data/comm panel ports and power ports, respectively

Note: The terms data port and comm port are used interchangeably in dcTrack. The Web Client uses data port and Classic View uses comm

port.

124

In This Chapter

dcTrack Interfaces ................................................................................. 124 dcTrack Terms ....................................................................................... 124

dcTrack Interfaces

dcTrack™ is made up of two user interfaces - the Web Client, which is completely web-based, and Classic View, which is a Windows-based component.

Each of these interfaces are used when installing or integrating dcTrack. As such, the steps provided in this guide include information on which interface to use when performing a task.

For more information on these two dcTrack interfaces, see dcTrack Help.

dcTrack Terms

Location

In dcTrack™, a data center room is referred to as a location or site. Locations have their own AutoCAD® .dwg drawing file.

Note: The term site is used in Classic View and location is used in the Web Client.

Note: Once the site is created, in order to see it in the Web Client, you must log out and then log back in to Web Client.

Items

Any asset being managed in the data center is called an item. Items are broken into three groups: IT items, power items, and environmental items, then each group is broken further into the item class. Each item can have one or more power port and/or data ports. See Ports (on page 128).

IT Item Classes

Items are grouped into six classes called item classes in dcTrack™:

Item Description

Cabinet A cabinet item is the structure that contains other items such as devices, network equipment, data panels and/or rack PDUs.

Appendix B Interfaces and Terminology

Appendix B: Interfaces and Terminology

125

Item Description

A cabinet can be an enclosed cabinet or an open bay rack. Cabinets and racks have mounting screw holes that are spaced apart according to an EIA industry standard. This spacing is known as a rack unit (RU), which represents a mounting height of 1.75.”

Note: dcTrack uses the terms rail position and U position interchangeably.

Device A device item is any computer system and its peripherals that are placed into a cabinet in the data center. There are several device types such as servers, appliances, disks, storage, tape drives, KVMs, etc.

Network A network item is any network equipment that provides network connectivity to devices. Network equipment typically has many more ports than devices. Multiple network items can be grouped into a network stack and given a logical name.

Data panel A data panel (communication panel) is used to terminate both ends of a grouping of a certain number of fixed structured data cables installed in the data center.

Typically, one end of the grouping of data cables resides in or near a device cabinet while the other end resides in or near a network cabinet.

Data panels can take a variety of types and form factors such as Category 5e/6/6A RJ45 patch panels, 110-type punch down blocks, fiber patch panels, etc. Collectively, the comm panels, data cables, and patch cords are referred to as the structured cable plant.

Note: The terms data panel, comm panel and patch panel are used interchangeably in dcTrack. Data panel is used in the Web Client and comm panel is

used in Classic View.

Passive Items that may or may not be placed inside a cabinet, but still need to be tracked as part of the data center.

Shelves Shelves within a cabinet


126

Power Items

Item Description

UPS An UPS (Uninterruptable Power Supply) item is an electrical system that provides continuous and uninterrupted power by switching very quickly to a local power source in the event the electrical utility feed is interrupted.

The local power source is composed of battery cells that are charged by the electrical utility feed during normal conditions.

The size and quantity of batteries determine the duration of the local power source. Typically, a UPS feeds PDUs downstream in the power chain.

Floor PDU A floor PDU (floor Power Distribution Unit) item is an electrical system unit that typically houses a step down transformer and circuit breaker panel boards. In some cases, the electrical panel boards are housed outside the floor PDU in remote power panel (RPP) cabinets distributed throughout the data center raised floor. A panel board contains circuit breaker positions called poles.

An alternate method of electrical distribution is an electrical busway system whereby the floor PDU main circuit breakers feed the busway instead of the internal panel boards or RPPs. In this system, the circuit breakers reside on the busway modules that house the power outlets. Typically a floor PDU is fed by one or more UPS systems.

Note: Do not confuse a rack PDU item with a PDU item. Rack PDU items are essentially a power strip and PDU items are an electrical system unit that typically houses a step down transformer and circuit breaker panel boards.

Rack PDU A rack PDU item is a specialized power strip that is used to provide additional electrical receptacles for a particular electrical outlet.

The rack PDU can be mounted horizontally or vertically in the cabinet. Some rack PDUs may be “metered” whereby they include an internal electronic measurement unit to measure the current draw at the receptacle or aggregate level of the rack PDU, and report this reading on an LED display internal to the rack PDU. Other rack PDUs may be “intelligent”


127

Item Description

whereby they can report the current draw and other electrical measurements at the receptacle level or at the aggregate level of the rack PDU via SNMP to an IP network device. Additionally, some of the “intelligent” rack PDUs can have temperature and humidity probes.

PX2 devices that are managing asset sensors are added to dcTrack as a Rack PDU.

Power outlet A power outlet item is the housing unit that contains one or more electrical receptacles of varying types. The electrical receptacles are in this case ports. Each power outlet is fed from a circuit breaker.

Environmental Items

Item Description

CRAC A CRAC (Computer Room Air Conditioning) item is usually a floor-standing air conditioning unit that provides cold and, usually, pressurized air under the raised floor to cool the heat dissipative data center equipment.

Probe A probe item is equipment that accepts one or more signals from a temperature and/or humidity sensor. The probe reports the temperature and humidity values via SNMP to dcTrack™.

EMX devices that are managing asset sensors are added to dcTrack as a probes.

Asset management tag and sensors

Asset management tags (AMTs) are electronic IDs that are adhered to data center items so you can remotely track the item's location. AMTs are plugged in to an asset management sensor (AMS), and the AMS is then configured in either Raritan's PX2 or EMX.


128

Ports

With the exception of cabinets, all items can be configured with ports.

Ports represent all the connectors on an item that may be connected to other ports. Ports can be added or deleted by any user who has edit access to that item. Ports that are already connected may not be deleted until they are disconnected.

Note: The terms data port and comm port are used interchangeably in dcTrack. The Web Client uses data port and Classic View uses comm

port.

Item Description

Data port Any port on an item used for voice or data communications is a data/comm port.

A port is defined with a name, connector, communications protocol, transmission speed, address and comments.

Virtual port Any data/comm port on a virtual machine.

Logical port A port using the internal communications paths on the blade chassis housing the blades on which the ports reside. For example, device blade logical port to network blade logical port within the same chassis, or device blade logical port to its blade chassis pass through ports.

Power port Any port on an item used to provide power to the item.

Each power supply in a device or in a network equipment item is represented in dcTrack as a power port. Each receptacle in a power outlet, and input cord or outlet in a rack PDU is represented as a power port.

Breaker panel pole

A PDU, RPP or electrical busway module contains panel boards. The maximum number of poles a panel can have is 96 for sites with the address in the United States. Sites defined in all other countries can have a maximum of 96 poles. Poles are either numbered sequentially in an odd/even layout, or using numbers and letters.

A panel is laid out such that odd poles are on the left and even poles are on the right.

There are 3 types of circuit breakers: 1-, 2-, or 3-pole breakers. As the name implies, a 2-pole breaker requires two pole positions and a 3-pole breaker requires three positions.


129

Item Description

Sensor port Sensor ports for temperature sensors, humidity sensors and asset management sensors that are part of an "intelligent" rack PDU, floor PDU, UPS, CRAC or probe item.

Circuits

Data and power circuits can be built in dcTrack™ as needed. Circuits refer to connections that are built between data center items (data circuits), and data center items and power sources (power circuits). Circuits include virtual connections from virtual machines to hosts, logical connections within a blade chassis, and physical connections between devices.

Circuits are composed of nodes and connections. Each node represents a point in the circuit, and connections connect each node in the circuit. For example, a server connects to a rack PDU and the rack PDU's power cord connects to a power source and so on.

For more information on building circuits in dcTrack™, see Building New Circuits in dcTrack Help. For more details on the types of circuits as they relate to dcTrack, see Circuits in the dcTrack Help.

130

In This Chapter

Overview ................................................................................................ 130 Optional Drawing Feature Requirements .............................................. 131 Drawing File Good Practices ................................................................. 138 Visio-to-AutoCAD Export Rules ............................................................. 139

Overview

This section of Help provides best practices and drawing file requirements regarding AutoCAD® and Microsoft Visio® location files that are imported into dcTrack™ when building a data center in the application. See Build the Data Center in dcTrack for information on performing this function.

Raritan offers drawing file templates you can download and use to create drawing file renderings of you data center. See Downloading Raritan dcTrack Drawing File Templates (on page 8) for information on downloading drawing files from Raritan's dcTrack Support Website.

Note: Regarding instructions on using Microsoft Visio™ drawings when building a data center in dcTrack™, the term "shapes" refers to the Visio drawing element that is used to represent an item in a data center. For

example, a server may be represented by a rectangle.

Appendix C Drawing File Preparation and Best Practices

Appendix C: Drawing File Preparation and Best Practices

131

Optional Drawing Feature Requirements

Drawing Cable Routes Option

Draw UTP cabling on a Layer called dcTrackCablingCopper.

Draw fiber cabling on a Layer called dcTrackCablingFiber.

Draw coax cabling on a Layer called dcTrackCablingCoax.

Draw power cabling on a Layer called dcTrackCablingPower.

Draw lines representing the cable routes using the Pline (Polyline) command. The Pline between two cabinets must be a continuous Pline object.

Each end of the Pline must cross inside the cabinet Solid Hatch.

Turn the above Layers off after creating the Layers and drawing the cable routes. Do not Freeze them.

Raised Floor Grid Labeling Option

1. Draw a marker on a Layer called dcTrackGridMarker.


132

The figure shown here is an example of a grid marker starting at a location where the A1 tile doesn't exist. Note that the blue lines were temporarily drawn to represent the location of the A1 tile exactly. Note the corner and direction of the line inside.

2. Draw the marker using the Rectangle command matching the origin coordinate (A1) tile exactly. If the A1 tile doesn't exist because of the geometry of the room walls, use the temporary lines to extend the raised floor grid to where the A1 tile would have been and draw the square marker there. Delete the temporary lines.

3. Inside this square, draw a Line (don't use Pline) from the exact corner of the square to the approximate center. Choose the corner that represents the 0,0 coordinate. In other words, this line starts at the corner and points to the direction of increasing numbers and letters.

4. Do not draw any other objects on this Layer.

5. The Layer should be turned Off, however, do not Freeze it.

The figure below shows an example of a grid marker at the A1 tile which is not a full tile, but the marker must have the dimensions of a full tile. Note the corner and direction of the line inside.


133

Perforated Tiles (PT) Option

1. Draw the Perforated Tiles (PT) on a Layer called dcTrackPerfTiles.

2. The PT is represented by drawing a Solid Hatch that is the size of one floor tile. You can make the PT look more realistic by showing the perforations in the Solid Hatch object. To do this:

a. Before drawing the Solid Hatch, draw a grid of small Circles inside the square of the tile.

b. Next, draw the Solid Hatch. This keeps the Solid Hatch out of the interior of the Circles. Delete all the Circles.


134

3. Use the PT Solid Hatch and copy it to every tile in the data center where a PT can be possibly installed. Use the Array command to accomplish the copying. Start with the PT Solid Hatch in the lower left most tile. Then provide the Array command with the number of rows and columns of PTs to be created. For correct array propagation, use the mouse with 'intersection snap' turned on so as to pick the offset points. The Layer should be turned Off but do not Freeze it.

4. Draw a grid of 7 x 7 circles using the Array command.

5. Draw two Lines from opposite corners in order to find the center point of the tile.

6. Move all circles so that the center of the center circle is at the intersection of the two Lines. Delete the two Lines.

7. Draw a Solid Hatch bound by the tile and the outside of all Circles. Delete all the Circles.


135

8. Use the Array command to copy the hatch object to all tiles in your data center.

9. Delete all extra PT hatch objects where a PT may never be installed such as under and to the sides of the floor PDU and CRAC units.

Drawing Raised Floor Grid Labeling Option

To draw a raised floor grid:

1. Draw a marker on a Layer called dcTrackGridMarker.

The figure shown here is an example of a grid marker starting at a location where the A1 tile doesn't exist. Note that the blue lines were temporarily drawn to represent the location of the A1 tile exactly. Note the corner and direction of the line inside.


136

2. Draw the marker using the Rectangle command matching the origin coordinate (A1) tile exactly. If the A1 tile doesn't exist because of the geometry of the room walls, use the temporary lines to extend the raised floor grid to where the A1 tile would have been and draw the square marker there. Delete the temporary lines.

3. Inside this square, draw a Line (don't use Pline) from the exact corner of the square to the approximate center. Choose the corner that represents the 0,0 coordinate. In other words, this line starts at the corner and points to the direction of increasing numbers and letters.

4. Do not draw any other objects on this Layer.

5. The Layer should be turned Off, however, do not Freeze it.

The figure below shows an example of a grid marker at the A1 tile which is not a full tile, but the marker must have the dimensions of a full tile. Note the corner and direction of the line inside.

Drawing Perforated Tiles (PT)

To draw perforated tiles:

1. Draw the Perforated Tiles (PT) on a Layer called dcTrackPerfTiles.

2. The PT is represented by drawing a Solid Hatch that is the size of one floor tile. You can make the PT look more realistic by showing the perforations in the Solid Hatch object. To do this:

a. Before drawing the Solid Hatch, draw a grid of small Circles inside the square of the tile.


137

b. Next, draw the Solid Hatch. This keeps the Solid Hatch out of the interior of the Circles. Delete all the Circles.

3. Use the PT Solid Hatch and copy it to every tile in the data center where a PT can be possibly installed. Use the Array command to accomplish the copying. Start with the PT Solid Hatch in the lower left most tile. Then provide the Array command with the number of rows and columns of PTs to be created. For correct array propagation, use the mouse with 'intersection snap' turned on so as to pick the offset points. The Layer should be turned Off but do not Freeze it.

4. Draw a grid of 7 x 7 circles using the Array command.

5. Draw two Lines from opposite corners in order to find the center point of the tile.


138

6. Move all circles so that the center of the center circle is at the intersection of the two Lines. Delete the two Lines.

7. Draw a Solid Hatch bound by the tile and the outside of all Circles. Delete all the Circles.

8. Use the Array command to copy the hatch object to all tiles in your data center.

9. Delete all extra PT hatch objects where a PT may never be installed such as under and to the sides of the floor PDU and CRAC units.

Drawing File Good Practices

The cabinet outline should be a single object. Use the Pline or the Rectangle commands to draw the cabinet outline.

If a cabinet has a curved front that you want to show, use a single Pline to draw the cabinet starting at the center of the rear. Then, for the curved front, draw several shorter straight lines while varying the angle each time to achieve the curved look.

Make the Pline width of the cabinet outline equal to 0.75” or 1”.

Draw cabinet outlines, cabinet solid hatches and cabinet labels on separate Layers. This makes it much easier to make modifications and global changes in the future.

A text label (Standard Text or Multiline Text) should be created to identify each row. The same label should be used in the Row Label field on the Cabinet page.

Colors:

Use Color 81 for the cabinet Solid Hatch.

Use Color 254 for PDU and CRAC Solid Hatches.


139

Use Color 151 for PT Solid Hatches.

Use text style Arial Bold and a text height of 9 inches. This text height assumes that the AutoCAD® drawing is drawn in a scale of 1:1.

Use the Fillet command with a radius of 3 inches to round the edges of all the Plines representing the cable routes. This provides a cleaner look. This radius size assumes that the AutoCAD drawing is drawing in a scale of 1:1.

If there is a title block in the AutoCAD drawing, place it in the Paper Space and create a Viewport to the Model Space. When you use the Advanced Print feature in dcTrack™, dcTrack switches to the first Paper Space layout (if it exists) and print it, thus printing your floor map with a title block.

Visio-to-AutoCAD Export Rules

Due to the behavior of the Microsoft Visio®-to-AutoCAD® export, you must follow these rules when creating the drawing in Visio in order to provide proper visualization once the drawing is imported into dcTrack™.

Each floor plan object must use a solid fill color other then 01:White.

To add a fill color to a shape in Visio:

1. Right-click the object and choose Format > Fill.

2. Select a color and set the pattern to 01:Solid.

The specific color is not important since it is not be used in dcTrack.

Visio shapes on a layer cannot use a black border.

In Visio, an object border is drawn in black and is then filled in with another color. For example, a rectangle with a black outline may be filled in with blue. When the drawing is converted to DWG and opened in dcTrack, the object is filled in with black since the color of the rectangle border is used for the fill color and not the fill color itself.

To change the boarder and fill color for shapes on a Visio layer:

1. In Visio, go to View > Layer Properties. The Layer Properties dialog appears.

2. Create a new layer for the objects by selecting the New... button, naming the layer in the New Layer dialog and clicking OK.

Important: Do not begin the name of any layer with the word

"dcTrack" unless you are directed to do so.


140

3. Using the Layer Color drop-down on the Layer Properties dialog, select a color. To change the color to the same color that dcTrack uses for cabinets (AutoCAD's color 81), click on More Colors… from the color drop-down in Visio and select the Custom tab.

a. Enter the RGB colors as follows:

Red = 159

Green = 255

Blue = 127

4. Click OK to apply the changes to the layer.

5. Next, make sure all objects are assigned only to the layer you just created. To do this, turn on the Format Shape toolbar and select an object. The layer name is displayed in the toolbar for all objects selected.

Note: When you do this, the rectangle of the object takes on the color of the layer and no longer appears to be filled even though it is.

Objects do not have a black border to define them from each other after you complete these steps and save the Visio drawing as an AutoCAD® file. Instead, the object border and its fill use the color of the layer. If you want the Visio objects to use a boarder that is a different color than the fill, do the following as a workaround.

To create a boarder for the objects:

1. Draw an additional rectangle that has no fill (Pattern = None) around each object that is not assigned to a layer (Layer = {No Layer}). This is similar to the way it would be done in AutoCAD, where the rectangle and the hatch are two separate objects.

2. To easily distinguish classes of objects, create separate layers and colors for each type of floor-standing object in the data center such as a cabinet, floor PDU, CRAC or UPS.

3. Text labels should be modified if the text wraps to multiple lines. Text wrapping causes AutoCAD to insert a dash at the end of each line.

The workaround to this issue is to size the text box of the label to be wide enough so that the text does not wrap. Reducing the font size also helps prevent wrapping.

Each floor plan object must have a unique text ID.

To add a text ID to a Visio object:

1. Double-click on the object to put it in edit mode and type the text ID or use the Text Tool to add a text box.

2. Make sure the text box is inside the floor plan object.

3. Create duplicate objects with no fill and no text ID.


141

Duplicate objects cannot be on a layer.

Place them on top of the original object to provide borders for the objects. This is important to clearly distinguish multiple objects arranged side-by-side in a row.

The Visio Measurement Units setting must be set to inches, not feet and inches.

If you are using US units in the Visio drawing, the Measurement Units setting must be set to inches rather than feet and inches.

To change the measurement setting in Visio:

1. Select File > Page Setup.

2. Select the Page Properties tab.

3. Select Inches from the "Measurement units" drop-down.

142

In This Chapter

Overview ................................................................................................ 142 Best Practices when Using Import Wizard ............................................ 142 General Spreadsheet Requirements ..................................................... 143 Cabinet Import Requirements................................................................ 144 Item Import Requirements ..................................................................... 145 Power Circuit Import Requirements ...................................................... 146 Data Circuit Import Requirements ......................................................... 147 Custom Field Import Requirements ....................................................... 148 Blade Chassis and Blade Import Requirements.................................... 149 Virtual Machine Import Requirements ................................................... 150

Overview

This section contains information on general and specific spreadsheet template requirements. These requirements apply to both Raritan spreadsheet templates, and your own spreadsheet templates if you are using any.

Best Practices when Using Import Wizard

Raritan recommends following these best practices for all imports using the Import Wizard. Following these practices helps ensure the import runs as smoothly as possible.

Use Raritan spreadsheet template to import data

While you can use your own spreadsheet templates, Raritan's spreadsheet templates are designed to follow the import process and import rules specifically.

If you do you use your own spreadsheets, they must be formatted according to Raritan's spreadsheet template requirements.

See Using Raritan Spreadsheets vs. Your Own Spreadsheets (on page 7)

Appendix D Spreadsheet Import Requirements and Recommendations

Appendix D: Spreadsheet Import Requirements and Recommendations

143

Review the requirements for importing each item class before you start an import. See Spreadsheet Import Requirements and Recommendations (on page 142)

Do not have blank columns in between populated columns

Before you begin an import session, validate all required columns are included and data populated in the spreadsheet

See Spreadsheet Import Requirements and Recommendations (on page 142) for information on spreadsheet requirements

Perform an import for each item class rather than import multiple classes at the same time

For example, if you are planning on bulk importing rack PDUs and servers, create individual spreadsheets for the rack PDUs and the servers, then import them in separate import sessions.

General Spreadsheet Requirements

The following rules apply to all spreadsheets.

The first row must contain the column heading names that are mapped to dcTrack™ fields during the import process. For example, row 1 in the spreadsheet may contain Class, Item Name, Cabinet and so on.

The first row cannot be empty. If the first row is empty, dcTrack generates generic column heading names such as Heading 1, Heading 2 and so on. These headings then have to be mapped manually to corresponding dcTrack fields.

Each spreadsheet can contain up to 50 columns. If the spreadsheet has more than 50 columns, split the additional columns into another file.

Delete all unused columns in the spreadsheet. Blank columns may cause import errors.

To quickly delete all unused columns in an Microsoft Excel ® spreadsheet:

a. Select the first blank column in the spreadsheet in order to highlight it.

b. Press Ctrl+Shift+Right Arrow Key on your keyboard to select all the columns to the end of the file.


144

c. Right click on the highlighted columns and select Delete from the right-click menu. All columns are deleted even though they still may appear in the file.

d. Save the file.

Cabinet Import Requirements

Cabinets themselves are added to dcTrack™ by synching a linked AutoCAD® drawing in dcTrack. See Link AutoCAD Objects with dcTrack Items (on page 45).

However, synching only creates the cabinet item and populates its Item Name field. All other information must be populated using the Import Wizard or it must be entered manually.

It is recommended that you first import only the cabinet information so you have a structure in place in which to populate the items that are contained in each cabinet. If you do not have the cabinets imported first, you must manually add them.

Use the Raritan 01_Items_-_Cabinets_Only_for_3.0.xls spreadsheet template for importing cabinets, or use your own spreadsheet.






145

Before you begin an import, see General Spreadsheet Requirements (on page 143) for more details on general requirements.

For cabinets, use the Items with Ports as Quantities import type. This option is presented to you as you move through the steps of the Wizard.

See the Legend worksheet included in the Raritan template for required spreadsheet column information, and descriptions of the type of information captured in the spreadsheet for the item.

Item Import Requirements

After importing cabinets, import all additional items. 'All additional items' includes all data center items, such as servers, floor PDUs and so on, with the exception of custom fields, blades and chassis, virtual machines, data connections, and power connections - all of which have their own specific import instructions.

You can import all additional items at once using the same spreadsheet, or use individual spreadsheets to import each item type separately. For example, enter all of your servers, floor PDUs and so on into one spreadsheet and import them, or create separate spreadsheets for each item and import each individually.

Use the Raritan spreadsheet template for importing additional items, or use your own spreadsheet.






146


For devices such as servers, rack PDUs, CRAC units and so on, use the Items with Ports as Quantities import type. This option is presented to you as you move through the steps of the Wizard.


Power Circuit Import Requirements

Use the Raritan 06_Connections_-_Power_for_3.0.xls spreadsheet template for importing power circuit, or use your own spreadsheet.






147


For power connections, use the Power Circuits import type. This option is presented to you as you move through the steps of the Wizard.


For power circuit spreadsheets, each row after the first row must correlate to a dcTrack™ power circuit consisting of only two endpoints. Endpoints are the power supply on the item, and the existing power outlet or rack PDU. It is important to designate the power supply as the starting item/port, and the power outlet or rack PDU as the ending item/port.

The wizard imports power connections between the item's power supply port (starting item) and what it connects to, either a rack PDU or a power outlet (ending item). The remainder of the electrical circuit, for example the rack PDU to power outlet to breaker, must already be defined in dcTrack.

The data must include columns for the item name and port for each of the two endpoints. Optionally, you can include the connection type and label for the connection between the two endpoints. The Item and Port Name columns should contain the name of the items and ports that match the existing item and port names in dcTrack.

Data Circuit Import Requirements

Use the Raritan 05_Connections_-_Communications_for_3.0.xls spreadsheet template for importing data circuit, or use your own spreadsheet.






148


For data (comm) connections, use the Comm Circuits import type. This option is presented to you as you move through the steps of the Wizard.


For data circuits, each row after the first row in a spreadsheet must correlate to a dcTrack™ data circuit consisting of up to 8 endpoints: 2 endpoints – one at the beginning of the connection and one at the end, plus 3 hops of 2 endpoints each.

The data must include columns for the item name and port name for each endpoint. Optionally, you can include the connection type and label for the connection between endpoint pairs. The item and port name columns should contain the name of items and ports that match existing item and port names in dcTrack.

When you are creating a hop for data circuits, you only need to define the near end since the circuit's port defines what it is connected to. For example, DataPanelA in CabinetA terminates at DataPanelB in CabinetB. When you are defining this hop in Import Wizard, you only need to define DataPanelA and the port. DataPanelB is implicit.

Note: You cannot use a single file that includes a variety of hop quantities for each circuit. Make one file for all circuits that use no cabling hops, one file for those that have only one hop, one file for those with 2

hops and one file for those with 3 hops.

Custom Field Import Requirements

Use the Raritan 02_Items_-_All_Other_Classes_for_3.0.xls spreadsheet template for importing custom fields, or use your own spreadsheet.






149



Blade Chassis and Blade Import Requirements

It is recommended you first import blade chassis, then import the blades to be installed in those chassis.

Use the Raritan 02_Items_-_All_Other_Classes_for_3.0.xls spreadsheet template for importing blade chassis and blades, or use your own spreadsheet.








150

Virtual Machine Import Requirements

Use the Raritan 02_Items_-_All_Other_Classes_for_3.0.xls spreadsheet template for importing virtual machines, or use your own spreadsheet.







151

In This Chapter

Overview ................................................................................................ 151 Import Data Center Items Process Flow ............................................... 152 Importing Items Using the Import Wizard .............................................. 153 Manually Adding Items in dcTrack ........................................................ 170 Important Maintaining Data Once dcTrack and Power IQ are Synched170

Overview

Raritan recommends using the Import Wizard when you have a large number of items to add to dcTrack™ at once since it may be time consuming to add items individually. However, items can be added individually. Following are details on using both the Import Wizard and manually adding items.

Appendix E Adding Data Using the Import Wizard or Manually

Appendix E: Adding Data Using the Import Wizard or Manually

152

Import Data Center Items Process Flow

Following is a high-level overview of the process flow involved when importing items into dcTrack™ as you build your data center model in dcTrack.


153

Importing Items Using the Import Wizard

Because the processes described in this section may take some time to complete, be sure your application session timeout is set to Never. Once the import is complete, change the session timeout as needed. See Change the Web Session Timeout (see "Change the Web Session Timeout for dcTrack" on page 64).

The steps involved when using the Import Wizard, which is accessed in Classic View, vary slightly depending on the type of item you are importing, so an individual topic for each item type import is included here. See:

Importing Cabinets and Additional Items Using the Import Wizard (on page 154)

Importing Power Connections Using the Import Wizard (on page 160)

Importing Data (Comm) Connections Using the Import Wizard (on page 165)

Using the Import Wizard

When adding items using the Import Wizard, you are walked through essentially the same steps when importing cabinets and all additional items such as servers, rack PDUs, CRAC units and so on.

The steps vary slightly when importing power connections and data (comm) connections.


154

Importing Cabinets and Additional Items Using the Import Wizard

The steps in this process apply to importing cabinets and all additional items such as servers, rack PDUs, CRAC units and so on. Note that the screenshots used here are meant as example only and reflect importing cabinets.

The location and the cabinet the item is being added to must exist in dcTrack™ before the item can be added. See Creating Locations (Sites) for the First Time (on page 43) information on adding a location.

After importing cabinets, import all additional items. 'All additional items' includes all data center items, such as servers, floor PDUs and so on, with the exception of custom fields, blades and chassis, virtual machines, data connections, and power connections - all of which have their own specific import instructions.

You can import all additional items at once using the same spreadsheet, or use individual spreadsheets to import each item type separately. For example, enter all of your servers, floor PDUs and so on into one spreadsheet and import them, or create separate spreadsheets for each item and import each individually.

If you are using Raritan spreadsheets for your import, use the 01_Items_-_Cabinets_Only_for_3.0.xls for cabinets and 02_Items_-_All_Other_Classes_for_3.0.xls for all additional items.

To import cabinets and items using the Import Wizard:

1. In Classic View, select Administration > Wizards > Import.

2. In the "Select a file to import from" section of the page, click Browse. Locate the source file and click Open in the "Select a file to import" dialog. The import information from the file is then displayed at the top of the page.


155

3. In the "Select a file to import from" section of the page, click Next. An Import Wizards section is displayed on the page.

4. In the Import Wizards section, select the type of import:

Items with Ports as Quantities - select when importing cabinets (using the Raritan 01_Items_-_Cabinets_Only_for_3.0.xls spreadsheet or your own spreadsheet) and device items (using the 02_Items_-_All_Other_Classes_for_3.0.xls spreadsheet or your own spreadsheet)


156

5. From the Import all Items to this Site drop-down, select the site you are importing the data for. Click Next.

6. Next, begin mapping the data.

The data from the spreadsheet is displayed in the data table at the top of the page and each column, along with the dcTrack field it is mapped to, is displayed in the field match panel at the bottom left of the page.

If dcTrack has successfully mapped each of the spreadsheet column headings to a field in dcTrack, the "You've successfully mapped this field! Click Next." message is displayed at the bottom of the page. Additionally, all of the field values are listed in the "Available values in dcTrack for field" box in the import panel on the bottom left of the page. Click Next.

If dcTrack could not map a spreadsheet column heading to a dcTrack field, you must do one of the following:


157

a. Skip the field by selecting the "Skip column" checkbox.

OR

b. Manually select and map the fields to a dcTrack field listed in the "Map to dcTrack field" drop-down. Use the Add function to add the field or Map to map the field. dcTrack prompts you to enter related information for each field. Required information is indicated by a red asterisk (*). You are able select multiple items (with the exception of Models) using Ctrl and/or Shift.

7. After the last field is matched or mapped, click Next to open the data validation page. Click Validate to begin the process.

Note: Large imports and/or use of hardware with specifications below the minimally recommended specifications can result in a processing

time of up to several minutes.

During validation, the format and integrity of the data is verified. Any rows (records) that do not meet the import criteria are displayed in the import panel of the page along with the specific reason for the validation failure.

You can make corrections to data directly in the data table at the top of the page. To do this, first move back one column from the column you want to make changes to and then make changes. Once the changes are made, click Next to move forward until you reach the Validation page again. You can move back using the Back button, or you can click on the column name in the list of columns to the left.


158

If the number of conflicts in need of correction is long, click the "Pop up Problems List" button to open a new window containing the list of conflicts in order to keep the information visible while you move back to the columns that require corrections.

8. Once data validation is complete and no more conflicts are displayed click Next.

9. Before you begin the final import, it is recommended that you export the validated data to a new or existing spreadsheet so you have a copy of the most current version of the data. To do this, click the Save As button at the top of the page, then save the file locally. Optional

10. Click on the Import button to begin the import process. The progress of the import as it happens is displayed on the page.

You can stop the import at any time by pressing the Cancel button. Records imported up to the point before you canceled the process are retained in the database.

At the end of the import process, a status message is displayed. For all records that are imported successfully, the time, date and other parameters of the import are saved as a separate import session in the Completed Import Session drop-down for future reference and additional functions.


159

Once the import is complete, a Planned status is applied to each item that was imported.

11. You are advised to go to the item detail page for each imported item in order to review and, if necessarily, revise or adjust imported items.

12. Verify the items were imported by looking them up on the Items List page for the item type in Classic View, or on the Items List page in the Web Client. Optional

After reviewing imported data and determining it is correct, you can change the status of each imported item at once to Installed by approving the import session. This is done on the Import page, which you can access from anywhere in Classic View by clicking on Import in the Explorer Menu, or clicking Back to Start at the end of the import process if you have not navigated away from the Import page.

13. On the Import page, select the session from the Select an Import Session drop-down on the Import page.

Note: In order for an import session to appear in the Select an Import Session drop-down, more than one record must be imported as part

of the import session.

14. Click Approve, then click Yes on the confirmation message to mark all the items as Installed.

Note: If the import was done in multiple sessions, for example if you needed to make multiple corrections to the data and then begin the import again, you must go to each session and select Approve.


160

Note: Once a session is approved, that session no longer appears in the Select a Session drop-down, at which point those items cannot

be returned to Planned status and they cannot be deleted.



15. Verify the items are now in an Installed state by looking them up on the Items List page for the item type in Classic View, or on the Items List page in the Web Client. Optional

Once the s are in an Installed state, items can be added to them.

Importing Power Connections Using the Import Wizard

To import power connections:





Power Circuits - select when importing power circuits (using the 06_Connections_-_Power_for_3.0.xls spreadsheet or your own spreadsheet)


161



162






OR


163










10. If needed, apply one or both of the following options to apply to power items:

'Allow connections between items in different cabinets' - when selected, power connections between different cabinets are permitted


164

'Allow mismatched Color Codes' - when selected, colors applied to connections cables can be mismatched






13. Verify the power connections were imported by looking them up on the Circuits List page for the item type in Classic View, or on the Circuits List page in the Web Client. Optional


165

You can change the status of each imported connection at one time to Installed by approving the import session. This is done on the Import page, which you can access from anywhere in Classic View by clicking on Import in the Explorer Menu, or clicking Back to Start at the end of the import process if you have not navigated away from the Import page.






Note: Once a session is approved, that session no longer appears in the Select a Session drop-down, at which point those items cannot be returned to Planned status and they cannot be deleted.



16. Verify the power connections are now in an Installed state by looking them up on the Circuits List page for the item type in Classic View, or on the Circuits List page in the Web Client. Optional


Importing Data (Comm) Connections Using the Import Wizard

To import data connections:



166




Comm Circuits - select when importing power circuits (using the 05_Connections_-_Communications_for_3.0.xls spreadsheet or your own spreadsheet)





167




OR










10. If needed, apply one or both of the following options to apply to power items:


168

'Allow connections between items in different cabinets' - when selected, power connections between different cabinets are permitted

'Allow mismatched Color Codes' - when selected, colors applied to connections cables can be mismatched

'Allow mismatched VLAN or Groups' - when selected, mismatched VLANs and groups do not have to match





169



13. Verify the data connections were imported by looking them up on the Circuits List page for the item type in Classic View, or on the Circuits List page in the Web Client. Optional

You can change the status of each imported connection at one time to Installed by approving the import session. This is done on the Import page, which you can access from anywhere in Classic View by clicking on Import in the Explorer Menu, or clicking Back to Start at the end of the import process if you have not navigated away from the Import page.


Note: In order for an import session to appear in the Select an Import Session drop-down, more than one record must be imported as part of the import session.



Note: Once a session is approved, that session no longer appears in the Select a Session drop-down, at which point those items cannot

be returned to Planned status and they cannot be deleted.

16. Verify the data connections are now in an Installed state by looking them up on the Circuits List page for the item type in Classic View, or on the Circuits List page in the Web Client. Optional



170

Manually Adding Items in dcTrack

When you build your data center model in dcTrack™, some items must be added manually or you may choose to enter them manually rather than use the Import Wizard.

To manually add an item to dcTrack via the Web Client:



2. Select the item's make. Required

3. Select the item's model. Required

4. Enter a name for the item in the Item Name field. The item name must be unique within the location. Required


6. Complete any additional required fields.

7. Click Save. The item is now in a Planned state.

8. Submit an Install Item request by clicking on Actions > Install Item Request, then click OK on the install confirmation message. Alternatively, submit one or more Install Item requests at once using Ctrl+click to select them on the Item's List page, then clicking Actions > Install Item Request. Note that the request can be issued now or at a later time.

Check the status of the request at any time from Classic View by clicking Change Control > Requests.

After the Gatekeeper has reviewed and approved the request, a work order to actually perform the task is issued by the Gatekeeper. Once the work order is marked as Complete in dcTrack, the action is considered complete. The Gatekeeper must then mark the request as Complete.

Important Maintaining Data Once dcTrack and Power IQ are Synched

In order to maintain data integrity, once Power IQ and dcTrack™ data are synched, all items must be added and updated in dcTrack.

Important: Do not add or update items in Power IQ once they are synched with dcTrack.

171

A

About this Guide • 2 Add and Configure SNMP MIBs • 26, 35 Add Environmental Items • 27, 54 Add IP Subnets • 27, 55 Add Power Items • 27, 52 Add Remaining dcTrack Items to Power IQ •

80, 95 Add Structured Cable Items • 27, 51 Adding a PX2 to dcTrack • 118 Adding AMT Tracked Items to EMX • 112 Adding an EMX to dcTrack • 107 Adding Data Using the Import Wizard or

Manually • 72, 79, 151 Adding Items to PX2 • 120 Adding Teams • 26, 36 Adding Users • 26, 36

B

Back Up Your dcTrack Database • 63, 66, 73, 77

Back Up Your Power IQ and dcTrack Databases • 89

Back Up Your Power IQ Database • 82 Begin Using dcTrack • 61 Best Practices when Using Import Wizard • 50,

52, 54, 58, 142 Blade Chassis and Blade Import

Requirements • 149 Build Your Data Center Model in dcTrack • 25

C

Cabinet Import Requirements • 50, 144 Change the Administrator Password • 21, 22,

23, 87 Change the Web Session Timeout for dcTrack

• 63, 65, 75, 153 Change the Web Session Timeout for Power

IQ • 82 Change the Web Session Timeouts in Power

IQ and dcTrack • 83, 89, 91 Checklist - Build Your Data Center Model • 26 Checklist - dcTrack 2.4 Users Integrating with

a New Power IQ Installation • 63, 64 Checklist - dcTrack 2.5 (and Later) Users

Integrating with a New Power IQ Installation • 73, 74

Checklist - Existing dcTrack Installation with an Existing Power IQ Installation • 87, 88

Checklist - Existing Power IQ Installation with a New dcTrack Installation • 80, 81

Checklist - Integrating EMX Asset Sensors • 99, 100

Checklist - Integrating PX2 Asset Sensors • 112, 113

Circuits • 129 Client Requirements and Supported Software

• 12, 13 Configure NTP Server Settings • 24, 87 Configure the System Clock • 24, 87 Configuring Asset Sensors in EMX • 103, 105 Configuring the Asset Sensor in PX2 • 115,

116 Connecting an Asset Sensor to the EMX-111 •

102 Connecting an Asset Sensor to the EMX-888 •

104 Connecting Asset Sensors to the EMX • 101,

105 Connecting Asset Sensors to the PX • 114,

116 Create the dcTrack Virtual Machine • 16, 87 Creating Locations (Sites) for the First Time •

26, 41, 43, 154 Custom Field Import Requirements • 148 Customize Drop-Down Lists • 26, 34

D

Data Circuit Import Requirements • 147 Data Sources • 11 dcTrack 2.2 Users • 63 dcTrack 2.4 Users • 63 dcTrack 2.5 (and Later) Users • 73 dcTrack Architecture • 122 dcTrack Architecture and Data Model • 87,

121 dcTrack Data Model • 11, 123 dcTrack Interfaces • 124 dcTrack Terms • 124 Default Login Information • 20 Determining the Data Collection Scope • 11 Downloading Raritan dcTrack Drawing File

Templates • 8, 41, 130

Index

Index

172

Downloading Raritan dcTrack Spreadsheet Templates • 7, 50, 51, 52, 53, 54, 55, 144, 145, 146, 147, 148, 149, 150

Drawing Cable Routes Option • 131 Drawing File Good Practices • 138 Drawing File Preparation and Best Practices •

8, 38, 39, 45, 130 Drawing File Templates • 8, 38 Drawing Perforated Tiles (PT) • 136 Drawing Raised Floor Grid Labeling Option •

135

E

EMX Asset Sensor Management • 99 Environmental Items • 127

F

Firefox Users • 22 First Time Installation of dcTrack • 2, 4

G

General Spreadsheet Requirements • 7, 50, 51, 52, 54, 58, 143, 144, 145, 146, 147, 148, 149, 150

I

Implementation Planning Considerations • 9 Import Data Center Items Process Flow • 152 Import Items and Ports, Data Connections and

Power Connections • 27, 58 Import Power IQ Data into dcTrack • 83, 91 Important - Disable Data Backup Encryption in

dcTrack 2.5 • 73, 75 Important Maintaining Data Once dcTrack and

Power IQ are Synched • 170 Important Notes on Importing Data Using the

Power IQ Import Wizard • 73, 80, 83, 92 Importing AutoCAD Items into dcTrack • 27,

48 Importing Cabinets and Additional Items Using

the Import Wizard • 50, 52, 54, 153, 154 Importing Data (Comm) Connections Using

the Import Wizard • 153, 165 Importing Items Using the Import Wizard • 153 Importing Power Connections Using the

Import Wizard • 153, 160 Initial Configuration of dcTrack • 19, 63, 70, 87 Install dcTrack • 80, 87 Install dcTrack & Build the Data Center Model

• 12

Installation Steps • 15, 87 Integrate Power IQ Data with dcTrack Using

the Power IQ Wizard • 85, 93 Integrating an Existing dcTrack Installation

with a New Power IQ Installation • 2, 62, 63 Integrating an Existing dcTrack Installation

with an Existing Power IQ Installation • 2, 62, 87

Integrating an Existing Power IQ Installation with a New dcTrack Installation • 2, 62, 80

Integrating dcTrack • 2, 62 Integrating dcTrack with AMS via EMX or PX2

• 2, 62, 97 Intended Audience • 1 Interfaces and Terminology • 124 Internet Explorer Users • 20 Introduction • 1 IT Item Classes • 124 Item Import Requirements • 145 Items • 124

L

Link AutoCAD Objects with dcTrack Items • 26, 45, 50, 144

Load dcTrack onto the Virtual Machine • 17, 63, 68, 87

Location • 124 Log In to dcTrack for the First Time • 20, 87

M

Mandatory Drawing File Requirements • 8, 38, 39

Manually Adding Items in dcTrack • 50, 51, 52, 54, 170

N

Notes on Adding CRAC Units • 55 Notes on Adding Floor PDUs • 53 Notes on Adding Items • 59 Notes on Adding Power Connections • 59 Notes on Adding Power Outlets • 54 Notes on Adding Probes -

verify/review/questions • 55 Notes on Adding Rack PDUs • 53 Notes on Adding UPS Items • 52 Notes on Data Connections • 59

O

Optional Drawing Feature Requirements • 131 Overview • 5, 62, 97, 130, 142, 151

Index

173

P

Planning and Assessment • 6 Ports • 124, 128 Power Circuit Import Requirements • 146 Power IQ Integration Settings (Synching

dcTrack and Power IQ) • 108, 110, 118 Power Items • 126 Preparing to Install dcTrack • 12 Prerequisites and Important Notes - Updating

Power IQ with dcTrack Items • 71, 78, 110 Professional Services, Customer Support and

Training • 3 PX2 Asset Sensor Management • 112

R

Recreate the dcTrack Virtual Machine - verify/review/questions • 63, 67

Related Documentation • 3 Restore Your Database • 63, 68 Run SNMP Auto-Discovery (Optional) • 27, 57 Run the Prerequisite Program (Optional) • 18,

63, 69, 87

S

Setting EMX Asset Sensor LED Colors • 117 Setting EMX Asset Sensor LED Colors

(Optional) • 106 Spreadsheet Import Requirements and

Recommendations • 7, 142, 143 Spreadsheet Templates • 6 Step 1

Update the Models Library • 26, 28, 75 Step 10

Add Items, Data Connections and Power Connections • 27, 57

Step 11 Add and Assign Applications (Optional) •

27, 59 Step 12

Test and Verify • 27, 60 Step 2

Customize dcTrack Lists and MIBs • 26, 34 Step 3

Create Teams and Users (Optional) • 26, 36

Step 4 Prepare Drawing Files • 8, 26, 38, 42

Step 5

Collect Your Data to Populate dcTrack • 26, 40

Step 6 Create Locations/Link Drawings and

Images to the Location • 8, 26, 41 Step 7

Synch AutoCAD Objects • 27, 47 Step 8

Import Cabinets • 50 Step 9

Add Data Center Infrastructure Items • 27, 51

T

Target Data • 11

U

Update Power IQ with dcTrack Items • 63, 71, 73, 78

Upgrade to the Current Version of dcTrack • 73, 75

Upgrade to the Current Version of Power IQ • 80, 82

Upgrade to the Current Versions of Power IQ and dcTrack • 90

Using Raritan Spreadsheets vs. Your Own Spreadsheets • 7, 50, 52, 54, 58, 142, 144, 145, 146, 147, 148, 149, 150

Using the Import Wizard • 107, 118, 153

V

Verify Item Models are in Raritan's Models Library • 26, 34

Virtual Machine Import Requirements • 150 Virtual Machine Recommendations • 12, 13,

16, 67 Visio-to-AutoCAD Export Rules • 38, 39, 139

U.S./Canada/Latin America Monday - Friday 8 a.m. - 6 p.m. ET Phone: 800-724-8090 or 732-764-8886 For CommandCenter NOC: Press 6, then Press 1 For CommandCenter Secure Gateway: Press 6, then Press 2 Fax: 732-764-8887 Email for CommandCenter NOC: [email protected] Email for all other products: [email protected]

China

Beijing Monday - Friday 9 a.m. - 6 p.m. local time Phone: +86-10-88091890

Shanghai Monday - Friday 9 a.m. - 6 p.m. local time Phone: +86-21-5425-2499

GuangZhou Monday - Friday 9 a.m. - 6 p.m. local time Phone: +86-20-8755-5561

India Monday - Friday 9 a.m. - 6 p.m. local time Phone: +91-124-410-7881

Japan Monday - Friday 9:30 a.m. - 5:30 p.m. local time Phone: +81-3-3523-5991 Email: [email protected]

Europe

Europe Monday - Friday 8:30 a.m. - 5 p.m. GMT+1 CET Phone: +31-10-2844040 Email: [email protected]

United Kingdom Monday - Friday 8:30 a.m. to 5 p.m. GMT Phone +44(0)20-7090-1390

France Monday - Friday 8:30 a.m. - 5 p.m. GMT+1 CET Phone: +33-1-47-56-20-39

Germany Monday - Friday 8:30 a.m. - 5:30 p.m. GMT+1 CET Phone: +49-20-17-47-98-0 Email: [email protected]

Melbourne, Australia Monday - Friday 9:00 a.m. - 6 p.m. local time Phone: +61-3-9866-6887

Taiwan Monday - Friday 9 a.m. - 6 p.m. GMT -5 Standard -4 Daylight Phone: +886-2-8919-1333 Email: [email protected]

dctrack implementation & integration...

Documents