File Path: C:\IOC\dcexpert\StruxureWare Data Center Expert 7.8.0\dcexpert

Description: StruxureWare is used to monitor main power and other major production equipment within the Datacenters

Monitoring Instructions:

Data Center Enterprise and Storage should be notified of any red alarms that appear in StruxureWare by phone call. Yellow alarms should be monitored for changes, but do not need to be reported (with the exception of door alarms - they should be reported as below, "Routine alarm", and Temperature Alarms (See High Temperature Alarms (red or yellow) ~~or Outage~~; except 2550 netbotz alarms - see "2550 Netbotz 750 Alarms" below). FIRE alarms warrants an immediate call.

If you need to reach the DCM on-call, please use 765-607-6324, and select option 8. Be sure to send a follow-up email.

For routine alarms, you need only call the on-call once, whether contact is made or not. Be sure to leave a message if possible, and send follow-up email.

For emergencies (fire, water, rapid temperature rises, etc), if on-call does not answer, immediately call the following until contact is made: Todd Turner 765-496-8214, Joe Wenzel 765-532-3624, Greg 765-496-2456

Escalation: If the on-calls do not answer, call Taylor Donald 317-340-9937. If Taylor doesn't answer, call Keith Duvall 219-448-8281. If you have still not made contact with anyone, call the IOC on-call (765-49-64272).

• Routine alarm: Call/Send email once.

As of 12/17/23, please note that individual cooling failures that are not causing an overheat condition in the room need only be reported by email message. These are non-critical and will be resolved during business hours.
Ex: crac unit failed (compressor, low or high pressure).

Door alarm: MATH/HAAS - Send email then walk over and close the door. LAMB - call/send email.

High temps or Power Outage: ~~For a single crac unit with high temp or any alarm. Also a~~ Metasys module would be the same. Call and then send email immediately so anyone reading email can reply. If no reply after 20-30 minutes then call the next person and send email on who you called.

If another crac unit or room temp sensor triggers on high temp. Call again and if no answer start calling others. This process is for when a room gets hot, power outage, cooling or etc. (So keep calling)

In case of high temperature alarms, click here: High Temperature Alarms (red or yellow)

StruxureWare Alarms that do not require a call (and what to do instead)
Firmware/Software update pop ups	Always ignore these pop-ups. Do not click yes, only close it out or click no.
Communication lost, Connection, or Timeout errors	This alarm means that the server tried to talk to the device and didn’t get a response. Since all of the monitoring is done via the internet there will be times when a communication signal is lost. Please wait for 10 minutes for it to try again. If it still is alarming, contact DCM 496-8214 / ITIDataCenterManagement@groups.purdue.edu. If ALL devices in a room are down, call right away. Other reasons for a communication loss alarm: the building or room lost power, device lost power, network PIC or cable failure or network switch it is connected to is down. For netbotz modules, a phone call is not necessary unless the actual unit has lost connection (see 2550 Netbotz 750 Alarms below). Only send an email, even on critical alarms.
Humidity Alarms	Whether they are low or high humidity, these alarms in StruxureWare should be reported by email only ITIDataCenterManagement@groups.purdue.edu. Do not call for these alarms.
Dew Point Alarms	These alarms should be reported by email only ITIDataCenterManagement@groups.purdue.edu.
Battery Alarms for UPS devices.	Battery alarms in StruxureWare for UPS devices (devices with "apc" or "trp" in the hostname) should be reported by email only ITIDataCenterManagement@groups.purdue.edu. UNLESS!!! The battery alarm is temperature related. Then call. Ex: " internal battery temperature exceeds the critical threshold "
Surveillance Camera Errors/Test Patterns/Failures	Send email to ITIDataCenterManagement@groups.purdue.edu
Failed Login Attempts	No action needed
Maintenance Mode	If a device is in maintenance mode, all alarms currently showing in StruxureWare for it can be ignored. While new alarms may show up after a device is put in maintenance mode, they will often not trigger audio notifications and will still be ignored.
Low Coolant	These alarms should be reported by email only ITIDataCenterManagement@groups.purdue.edu.
Output Current High	These alarms should be reported only if they persist for at least 20 minutes. These alarms can still be reported by phone call.

2550 Netbotz 750 Alarms

For 2550-1370a-netbotz-01 alarms, email on warnings (even temperature alarms) and call on critical alarms. For critical Lost Communication alarms – only call if it is for the actual Netbotz 750 device (if link status is offline as described below). For Lost Communication for peripherals such as cameras, sensors, etc., only send email. Examples of common sensor alarms include L-7 front-bottom rack, H row ladder, K-20 sub-floor, and RSSI devices.

To verify the controller is still online, go to the monitoring tab, select 2550 under the Surveillance folder. Then right click on the Netbotz 750 and select "View Device Sensors".

Then scroll down to "Link Status" and it should show "Online". If it shows, "Offline", then call Data Center Management.

If you scroll down a couple more lines, you will see the word, "RSSI". These are the wireless devices. In the picture below, C-01 is showing "Unplugged". It is a little confusing (showing a wireless device as being unplugged) but that is how they report it.

Physical Facilities will call to report PMs on the CRAC & generator units listed below. Send email to ITI Data Center Management at ITIDataCenterManagement@groups.purdue.edu when they start and stop.
This protocol also pertains to when they come in on the weekends for a key. Ask what they are working on and send email to ITI Data Center Management.

Include the building, room, device name, and Physical Facilities technician name in the e-mail.
This is only for the equipment listed below. In all other cases dealing with Physical Facilities requests for permission to do work call Todd Turner at 496-8214.

Generator Test TEL Nodes

ERHT
LAMB
LYNN
TEL

Crac units Data Centers

FREH G2 CRAC #1,2,3,4
FREH G57 CRAC 1
FREH G60 CRAC 1, ACG-2
HAAS CRAC 1,2,3
MATH B60 CRAC 1,2,3
MATH G72 Chiller
MATH G109 CRAC 5,6,13
MATH G190 CRAC 1,12,32

TEL Nodes

ERHT 5 CRAC 1,2
LAMB 20 ACG-20,21
LYNN G168 ACG-40, 41
TEL 210 CRAC 1,2,3

Application Setup:

Launching the Application
Via Shortcut	Click on the StruxureWare shortcut on the desktop.
Manually	Click start, Type StruxureWare, Click on StruxureWare Data Center Expert 7.6.0
The log-on information should be saved/auto-populated (The splash screen may have a slightly different appearance):
Hostname/IP Address = 128.210.251.117 Port = 443 Use SSL to Connect Connection Timeout (seconds) = 30 Username & Password (Please see Passwords page) After successfully logging on, the main screen will look like the Screenshot below.

128.210.251.117

Pay attention to the ‘Monitoring’ and ‘Surveillance’ buttons at the top left of the screen, they will be used at the console monitors. Also note the Device Groups and Active Alarms tabs. These will alert the user to equipment problems.

Monitoring View

Please make sure the Monitoring view is selected (as it is by default).
Select All Devices
Double check to make sure all Data Centers are accounted for.
Make sure the audio alarm is enabled by completing the following steps:

Go to File > Client Preferences > Audio Settings
Click on "Play Sound when an Alarm Occurs"
Click on the radio button for "Select Provided Audio File"
Select "Tower Clock" from the drop-down list.
Click "Apply"
Click "OK"

Active Alarms will be displayed under the “Active Alarms” tab, and the normal-status green checkmarks next to the devices will change to yellow or red, depending on the nature of the alarm(s).

The most important screens within the software to be monitored are the “Device Groups” and “Active Alarms” windows. We are looking for any color other than green , but specifically yellow and/or red in one or both of those windows. Yellow alarms should be monitored for changes, but do not need to be reported (except High Temperature alarms, which should be treated as red alarms).

Red alarms are to be reported to Data Center Management immediately. These alarms should also have an audible ‘clock tower’ alarm to get your attention. If there is an alarm that presents and you are at all unsure of what to do, please call Todd Turner, as he would much rather be woken up for a questionable alarm rather than be left alone to sleep through a catastrophic meltdown.

**All events should be logged on the ITaP Operations Log following standard procedures.**

Surveillance Tab

In the Surveillance tab, you will have access to viewing 6 rooms with 56 cameras total. The ‘Thumbnails’ view will show all 56 feeds on one page. The 6 Datacenters are: DAT2; HAAS 234; INOK; ITAR STEW B001K; LAMB 20; MATH B60, G109, G190; TEL 201, 210, Building.

If you click on a specific Room Camera in the Device Group window, you will see only views for that Room.

Please monitor the cameras from time to time to make sure nothing suspicious is going on. Check the Shift Log, Change and Release Management Calendar and your email for scheduled work. If it appears that the occupants do not belong in the room or are removing things during the night,

notify PUPD (48221) to investigate. You will also need to call Todd Turner if you do call PUPD, or if you feel unsure.

HAAS is considered a lights-out facility with several groups who have card access. The building fire panel is located in the datacenter. The Fire & Safety group works Midnight to 8am doing panel tests across campus, and you will see them or the PUFD in the room from time-to-time.

Browser not supported