APC AP95100 Power supplier AP95100 User Manual
Product codes
AP95100
Mass Configuration: Sensor and Alert Settings
114
InfraStruXure Central 4.1 User’s Reference
Whenever you start a Mass Configuration task, the first window that is displayed shows a table of devices
on which the selected task can be performed. This table features a Status column, in which the current
status of each device is displayed. If a device is currently in an offline state the Status field for the device
will read “Offline,” but you will still be able to enact Mass Configuration tasks on the device, just as if the
device were online. When a Mass Configuration task is enacted against an offline device, the Status field
will show that the task did not complete and is being retired automatically, and a small image of a clock is
displayed to indicate that the configuration request against this device is currently in a pending state.
on which the selected task can be performed. This table features a Status column, in which the current
status of each device is displayed. If a device is currently in an offline state the Status field for the device
will read “Offline,” but you will still be able to enact Mass Configuration tasks on the device, just as if the
device were online. When a Mass Configuration task is enacted against an offline device, the Status field
will show that the task did not complete and is being retired automatically, and a small image of a clock is
displayed to indicate that the configuration request against this device is currently in a pending state.
If InfraStruXure Central is unable to carry out a mass configuration task because a device is in an Offline
state, it adds the task to the Pending Requests list (“Management Device Job Control” on page 89).
state, it adds the task to the Pending Requests list (“Management Device Job Control” on page 89).
Managing BotzWare Version 1.x Devices
The Pod Sharing task enables you to use NetBotz 500 devices to receive data from legacy NetBotz
devices running BotzWare 1.x (including RackBotz and WallBotz 300, 303, 310, 400, and 410 devices).
Once a NetBotz 500 is configured to access these legacy models they are treated exactly like other shared
pods or devices, providing alert and sensor data exactly as if they were directly connected to the NetBotz
500. For more information on Pod Sharing, see “Pod Sharing” on page 206.
devices running BotzWare 1.x (including RackBotz and WallBotz 300, 303, 310, 400, and 410 devices).
Once a NetBotz 500 is configured to access these legacy models they are treated exactly like other shared
pods or devices, providing alert and sensor data exactly as if they were directly connected to the NetBotz
500. For more information on Pod Sharing, see “Pod Sharing” on page 206.
About Sensor and Alert Settings Tasks
The majority of tasks that are available from the Sensor & Alert Settings pane enable you to configure the
sensors that are built into or connected to your NetBotz devices. Each sensor threshold configuration task
is named for the type of sensor with which the sensor will be used (temperature, air flow, humidity, and so
forth).
sensors that are built into or connected to your NetBotz devices. Each sensor threshold configuration task
is named for the type of sensor with which the sensor will be used (temperature, air flow, humidity, and so
forth).
The sensors used by your devices fall into two categories: Numeric sensors and state sensors. Numeric
sensors report sensor readings as a current value within a broad range of potential values defined by a
minimum and maximum value, such as temperature or humidity readings. State sensors, on the other
hand, report sensor readings as one of two mutually exclusive states, such as a door being “open” or
“closed” or motion being “detected” or “not detected.” Due to the differences in the kind of data reported
by these two sensor types, the thresholds that can be applied to each sensor type differ greatly.
sensors report sensor readings as a current value within a broad range of potential values defined by a
minimum and maximum value, such as temperature or humidity readings. State sensors, on the other
hand, report sensor readings as one of two mutually exclusive states, such as a door being “open” or
“closed” or motion being “detected” or “not detected.” Due to the differences in the kind of data reported
by these two sensor types, the thresholds that can be applied to each sensor type differ greatly.
Each sensor threshold configuration task is named either a) for the type of sensor with which the sensor
will be used (temperature, air flow, humidity, and so forth) or b) with a general name that describes the
sort of sensor that is configured using the task. The sensor configuration tasks are:
will be used (temperature, air flow, humidity, and so forth) or b) with a general name that describes the
sort of sensor that is configured using the task. The sensor configuration tasks are:
• Air Flow Settings (to configure air flow sensors integrated with your devices)
• Amp Detector Settings (to configure amp detector sensors connected your devices)
• Audio Settings (to configure audio sensors integrated with your devices)
• Dew Point Settings (to configure dew point sensors integrated with your devices)
• Door Settings (to configure door switch sensors connected to your devices)
• Dry Contact Settings (to configure dry contact sensors connected to your devices)
• Humidity Settings (to configure humidity sensors integrated with or connected to your devices)
• Motion Sensor Settings (to configure the camera motion sensors integrated with your devices)
• Power (VA) Settings: Use the Power (VA) Settings to configure thresholds for your device volt
amperage sensors.
• Power (Volts) Settings: Use the Power (Volts) Settings to configure thresholds for your device
voltage sensors.