File Path: C:\IOC\dcexpert\StruxureWare Data Center Expert 7.8.0\dcexpert
...
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. Exceptions to when to call are listed below:
Business Hours 8 to 5pm: Greg 765-496-2456, Joe Wenzel 765-532-3624
After Business Hours: 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, Todd Turner Greg 765-496-82142456
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.
...
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.
...
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).
...