NetBotz® Appliance User’s Guide NBRK0570 NBRK0550 NBRK0450 NBWL0455 NBWL0456 NBWL0355 NBWL0356
This manual is available in English on the enclosed CD.
Contents Preface ............................................................................. 1 U.S. Government Restricted Rights . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Misuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Improper Use of Audio/Video Recording Capabilities. . . . . . . . . . . . 1 Availability of Open Source Technologies . . . . . . . . . . . . . . . . . . . . . 1 Introduction ...........................................
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Installing software on a Windows system . . . . . . . . . . . . . . . . . . . . 11 Installing software on a Linux system . . . . . . . . . . . . . . . . . . . . . . . 11 Adding Appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Removing Appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Accessing an Appliance Using Advanced View. . .
Viewing Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Resolving alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Saving picture sequences to your system . . . . . . . . . . . . . . . . . . . 26 Viewing Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Creating and editing maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Viewing Graphs . . . . . . .
IPMI Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Adding, editing, and removing IPMI devices . . . . . . . . . . . . . . . . . . 50 Sensor settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Modbus Slave System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Assigning a slave ID to a pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Removing a slave ID from a pod . . .
Advanced View: Configuring Appliances.................... 74 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Clock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Custom Audio Clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Adding custom audio clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Deleting custom audio clips . . . . . . . . .
Pod, Pelco Camera, and Rack Access PX-HID Sharing . . . . . . . . . 93 Setting up a Pelco shared IP camera pod . . . . . . . . . . . . . . . . . . . . 95 Setting up shared IP camera pods . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Rack Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advanced View: Creating Alert Actions .................... 112 Creating an activate button output alert action . . . . . . . . . . . . . . 113 Creating a call web services alert receiver alert action . . . . . . . . 113 Creating a play audio alert action . . . . . . . . . . . . . . . . . . . . . . . . . 113 Creating a play custom audio alert action . . . . . . . . . . . . . . . . . . . 114 Creating a send custom HTTP GET alert action . . . . . . . . . . . . . .
NetBotz Appliance User’s Guide viii
Preface U.S. Government Restricted Rights Restricted rights legend. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of the Commercial Computer SoftwareRestricted Rights clause at CFR 52.227-19, as applicable. Misuse Use your appliance ONLY in the manner specified.
Introduction The Schneider Electric NetBotz® Web Client and Advanced View each provide a software interface for monitoring and controlling your NetBotz security and environmental monitoring system with the following NetBotz appliances: NetBotz Rack Monitor 450, NetBotz Rack Monitor 550, NetBotz Rack Monitor 570, NetBotz Room Monitor 455, and NetBotz Room Monitor 355. You use the Web Client interface primarily to monitor the environment.
SSL Support By default, Secure Sockets Layer (SSL) is enabled on your NetBotz appliance. All browser/appliance interaction can be carried out using SSL by connecting to the appliance using a URL beginning with https (for example, https://IP_address). Your appliance can also use SSL when posting alert notification and sensor data to Web servers, and Advanced View can be configured to use SSL when communicating with your appliance.
Web Client: Getting Started The NetBotz Web Client provides a real-time overview of alerts and device details for a NetBotz appliance running at least version 4.2. It does not require the Advanced View application and Java Runtime Environment.
Choosing a Language Configure your browser or operating system to view the Web Client in any of the following supported languages. Note: The appliance you are accessing will have a subset of the following languages loaded. If the Web Client is not displayed in the chosen language, it may need to be loaded. See “Region” on page 98 for instructions on loading language files onto the appliance.
Interface Navigation The Web Client interface is divided into five tabs: Status, Alerts, Cameras, Pods, and Sensor History: Status: Provides information at a glance about alerting sensors, security sensors, and cameras. Alerts: Displays alerts from the device types and severities you select, All by default. Cameras: Displays live video captured by the appliance, the cameras connected to the appliance, or IP cameras on your network that are shared through the appliance.
Web Client: Monitoring Your Environment The Web Client provides a real-time overview of alerts and device details, including sensor readings and images captured by camera pods, for a NetBotz appliance running at least version 4.2. It does not require the Advanced View application and Java Runtime Environment. By default, Secure Sockets Layer (SSL) is enabled on the NetBotz appliance. The SSL certificate is generated by the appliance (self-signed) and requires no user interaction.
Alerts tab The Alerts tab allows you to view the alerts reported by the sensor or camera pod you select, and the severity you select, All by default. • Pod: Allows you to select the alerts you want to view by pod type and severity, and choose whether to include resolved alerts. The severity values, from most severe to least severe, are Failure, Critical, Error, Warning, and Information. Resolved alerts are stored on the appliance for up to 24 hours.
Depending on the pod type selected, one or more of the following options are available: • Settings: Allows you to change the pod label. • External Sensor Ports: Allows you to select the sensor type, and change the port label. • Pod Details: Displays details for the selected pod, including the name, model, manufacturer, revision, bootstrap verison, and application version. You can select a sensor to change its label or sensor value history, or choose whether to report unplugged errors, when applicable.
Advanced View: Getting Started Advanced View is a stand-alone Java application you can use to monitor and configure your appliance and any camera pods, sensor pods, CCTV adapter pods, output relay pods, 4-20 mA sensor pods, external sensors, or supported serial-based sensors connected to the appliance. Note: Your monitor must be set to at least 1024x768 for Advanced View to display properly.
Software Installation Follow the procedures in this section to install the following applications from the NetBotz Appliance Utility CD onto the personal computer that you will use to configure and manage your NetBotz security and environmental monitoring system: • Advanced View: A Java-based user interface for monitoring and managing your NetBotz security and environmental monitoring system.
Adding Appliances Before using Advanced View to manage an appliance, you must first add the appliance IP address or hostname to the Appliance list. To add an appliance to the Appliance list: 1. Click Add Appliance. The Add Host Device window opens. 2. In the IP Address or Hostname field, type the IP address or hostname of the appliance. 3. In the Port field, type the TCP port through which you will communicate with this appliance. The default value is 80. 4.
Accessing an Appliance Using Advanced View Select an appliance from the Appliance list. • If the appliance Guest account is configured with a Sensor (No Camera), Sensor, Application, or Administrator privilege set, you are automatically granted access to the appliance and can view Advanced View panes permitted by the privilege set.
Interface Navigation The Advanced View interface is divided into the Navigation pane, the Sensor Data pane, and the Action/ Information pane.
To create or modify a folder: 1. Right-click on the background of the Navigation pane, not on a device, and select Add Folder. To modify a folder, right-click on the folder and select Modify Folder. 2. Type a folder name in the Folder Name field. 3. To add devices, select one or more devices from Available Enclosures and click the right arrow (>) button to add the selected devices to the Selected Enclosures list. 4.
Sensor Data Pane Located in the lower-left hand corner of the interface, the Sensor Data pane displays the readings and alert status of sensors associated with the selected device in the Navigation pane. If the selected device is an output relay device, the state of the relay is displayed. If the selected device features a large number of sensors, the sensors may be divided into sensor sets. Use the Set drop-down list to select either a specific sensor set or All Sensors.
Advanced View Menus Advanced View features the following menu bar: • File: Use this menu to add appliances to or remove appliances from the Appliance selection drop-down list and to exit the Advanced View application. • Edit: Use this menu to cut, copy, paste, and delete text, and to configure Preferences. See “Editing Preferences” on page 18. • Tools: Use this menu to complete the following tasks: – View Messages (information generated by Advanced View for logging and debugging purposes).
Using Advanced View POST-only Mode If you use StruxureWare Data Center Expert to monitor and manage a NetBotz appliance that is located behind a firewall, StruxureWare Data Center Expert may not be able to communicate directly with the appliance. Placing the appliance in Advanced View POST-Only Mode causes the appliance to post all monitoring data to a specified StruxureWare Data Center Expert appliance at a user-specified interval. SSL encryption can be used for secure data posting.
Advanced View: Monitoring Your Environment Use Advanced View to view sensor readings, view camera images, graph collected sensor data, and view active and resolved alert conditions. You can also create, view, and delete maps for use in the Map view. Viewing Sensor Readings and Status To view sensor readings, select a device that includes sensors from the Navigation pane. The Sensor Data pane automatically updates with sensor information for the device you selected.
To enable or disable a card reader in Advanced View: 1. From the Navigation pane, select a Rack Access Pod. 2. Right-click the Reader sensor in the Sensor Data pane. 3. Select Reader (n): Set to “Disabled” next to the desired card reader. The reading will change to Disabled and the button label will read Reader (n): Set to “Enabled”. Note: A physical key can always be used to access the rack regardless of whether the card reader is enabled or disabled.
Viewing Live Video Click the Camera View button in the Action/Information pane to view live video captured by the appliance, cameras connected to the appliance, or shared IP cameras on your network. Controls are applied to the top-most camera image. Click an image to change its position to the top. To view all camera images side by side, click the Tiled check box. For information on shared IP cameras, see “Pod, Pelco Camera, and Rack Access PX-HID Sharing” on page 93.
Pelco PTZ camera controls The Update button provides access to the Add/Update Presets display, used to specify or modify a name for preset camera positions, and configure a tour using those camera positions, for the selected Pelco PTZ camera. To associate a camera position with a preset, select a preset from the list, use the arrow and zoom controls to position the camera, and click the Set button. To view the live video for a preset, select a preset from the list, and click the Go button.
Control Name Description View a part of the image in more detail. Click this button, and then on the Resize Camera image, click and drag a box around the area of interest. When you release the View mouse button, the camera automatically zooms to the box you created. Center Click this button and then click a point on the image to center the image on that point.
Pelco PTZ Camera Presets The Pelco camera preset controls allow you to associate a name with a camera position, and save it. You can modify the camera position of a preset, or rename it. Adding a Pelco PTZ Camera Preset To create, modify, or remove presets for the selected Pelco camera: 1. Click the Update button from the Action/Information pane. 2. On the Presets tab, in the Add/Update Preset field, specify the name of a new preset, and click Add, then click OK. 3.
Recording Camera Images Use Advanced View to record camera images and save them to a user-specified directory. By default, recorded camera images are saved to a subdirectory with the same name as the camera pod, located within a directory named camera in your Home directory. For example, a user account named NetBotz on a Windows XP system recording images from a camera pod labeled My Camera would store recorded images in the directory C:\Documents and Settings\NetBotz\camera\My Camera.
If additional alert-specific data such as graphs, maps, or captured images is available, it appears on the Alert Details view as entries in additional tabs. Double-click entries on tabs to view additional data. Note: When viewing video that was captured for an alert for a camera motion sensor, the IP Address displayed is that of the appliance selected from the Appliance field, even if the camera pictures are from a shared IP camera.
Creating and editing maps To create a new map for use in the Map View or to edit a map: 1. Click the Maps View button in the Action/Information pane. 2. To create a new map, click Add. To edit a map, select the map from the Maps drop-down list and click Edit. The Map Configuration window opens. Note: There is a limited amount of space available for creating maps and using custom audio clips.
Viewing Historical Data The History View lets you view and export historical data from one or more sensors. You can specify which pods and sensors to include, as well as the range of time for which data will be retrieved. The data can then be exported to a text file in a tab-delimited, comma-delimited, or semi-colon-delimited format. The History View button is available on the Action/Information pane. Running a historical data report To define the parameters for the report: 1.
Event Log The event log records System and Rack Access System events in order to provide an audit trail for security-related events. The Event Log can hold ten pages of data (with each page limited to 64K of data). For each event, the date and time of the event is recorded, along with the category of the event, the severity of the event, and a text description of the event. To refresh the contents of the Event Log, click Refresh. Any new events will be appended to the bottom of the current page.
Advanced View: Pod/Sensor Settings Use the icons in the Pod/Sensors Settings area of the Configuration view to configure the pods and sensors connected to your appliance and configure the alert actions and policies that are used when alerts are reported by sensors. Note: The icons that appear in the Pod/Sensor Settings area depend on how your system is configured. It is possible that not all icons discussed in this chapter will appear in your Pod/ Sensor Settings area.
• Send HTTP Post: Sends an HTTP post to a specified HTTP server with information about the alert. The alert notification post can include images captured by a camera pod, a graph, and a map of the sensor-specific data associated with the alert. Note: The appliance posts all data according to the HTTP Post/FTP Data Delivery parameters. You must configure the target HTTP server appropriately to receive the posted data. More information can be found on the APC Web site.
Creating or editing alert actions To create a new Alert Action or edit an existing Alert Action: 1. Double-click the Alert Actions icon. 2. Click Add... If you are editing an existing alert action, select it from Alert Action, click Edit, and proceed to step 4 . 3. Select the alert notification method for this action from the Add Alert Action window, and click OK. 4. Specify the notification information for this alert action.
Default alert profile Your appliance comes pre-configured with a default alert profile. The default policy features the following four pre-configured Alert Sequences which are active 24 hours a day, 7 days a week: • Alert Level 1: Begins immediately after an alert condition occurs (Start Value of 0) and repeats two times at 5 minute intervals. It initiates the Primary E-Mail Notification, and Short Message E-Mail alert actions.
Creating an alert sequence To create a new alert sequence or modify an existing alert sequence: 1. Double-click the Alert Profile icon. 2. Select the alert profile to which you would like to add a new alert sequence and click Edit. 3. Click Add.... If you are modifying an existing alert sequence, select the alert sequence from the Sequence table and click Edit.... 4. Type a name for the alert sequence in the Label field. 5.
Suppressing alert notifications You can temporarily suppress all alert notifications associated with a selected alert profile globally. Note: Disabling alert notifications prevents your appliance from automatically notifying you of conditions that may be hazardous to your critical assets and spaces. Use this feature only for scheduled maintenance or downtime. When alert notifications are disabled, sensors in the Sensor Readings pane continue to turn red to indicate that a threshold has been violated.
Camera Pods To configure a camera: Note: From the Navigation pane, you can right-click a Pelco camera and select Connect to... to launch the Pelco Web interface for the camera. This will allow access to additional required configuration settings. 1. For integrated cameras or cameras connected to the appliance, double-click the Camera Pods icon. The Camera Pod Configuration window appears with a list of cameras. 2.
Field Description Speaker Label An additional label for the speaker on this pod (camera pods and CCTV adapter pods only). Unplugged Alert Severity The severity of alerts generated if this device is unplugged. Unplugged Alert Profile The actions taken if the camera pod is unplugged. By default, the default alert profile is used for all thresholds. If you create additional alert profiles, you can specify an alert profile other than default.
Associating relays, switches, or outlets with integrated cameras and camera pods. Relays, switches, and outlets can be associated with cameras to simplify manually changing relay states from the Camera View. Once a relay, switch, or outlet is associated with a camera, you can associate an action with it, and manually generate that action from the camera image in the Camera View. You right-click the camera image, and select the action from the menu.
Field Description Flicker filter Minimize image brightness flickering that can occur in the dark areas of the image. Note: Enabling the flicker filter can impact the number of frames per second at which images are captured and displayed, typically noticeable only at image capture rates more than 5 per second. Note: This option is available only when configuring Capture settings for NetBotz Camera Pod 120s, Revision A0, Submodel 120-0000 or earlier.
Field Post-Alert Capture Time Description The total number of seconds after the alert generating event that images are included in alert notifications. NOTE: For Pelco cameras, once an alert is generated a new alert will not be generated until 30 seconds has elapsed. To ensure that you capture all motion, set this field to 30 seconds. The number of post-alert images captured is equal to the Post-Alert Capture Time multiplied by the Maximum Rate.
Mask settings Select a camera from the Camera Pods window and click Masking. Masking is available only on the NetBotz Rack Monitor 570, 550 or on appliances for which the Advanced Software Pack has been purchased. For more information, contact your NetBotz authorized reseller or the NetBotz support team. Camera-based motion sensing compares concurrent image captures and determines whether any detected changes are significant enough to generate an alert.
Click OK to save your changes. Click Cancel to close the Camera Motion Configuration window without saving any changes. Block out mask tab. The following controls are available: • Enable Block Out Mask: Check to enable the Block Out Mask function. • Block Out Mask: Specify regions of the image that are not visible in the camera image. Use the Block Out Mask to configure your camera so specified areas of the image cannot be seen. To mask a portion of the image: 1.
Sensor configuration Select a camera from the Camera Pods or Shared Cameras window and click Sensors. The Sensor Configuration window displays a Sensors list and a Thresholds list. Select a sensor from the Sensors list to display thresholds defined for the sensor in the Thresholds list. To modify a sensor: 1. Select the sensor to modify from the Sensors list and click Modify. 2. Enter a label in the Label field.
Scanned Devices Note: The Scanned Devices icon is only available with the purchase of the 5-node Scanner/ IPMI Pack. For more information, contact your NetBotz authorized reseller or the NetBotz support team. Scanned devices are SNMP targets that are monitored by the NetBotz appliance. You can monitor status information for up to five remote SNMP targets such as servers, routers, and switches as well as APC devices such as APC UPSs and APC Rack Power Distribution Units (PDUs).
Scanners gather the following information about the network interfaces of all configured SNMP targets in individual sensor sets: • Admin Status: State sensor that reports the admin status of the interface. • IF Description: Displays the interface description value (does not support threshold configuration). • IF MAC Address: Displays the interface MAC address (does not support threshold configuration). • IF Type: State sensor that reports the interface type value.
Adding, editing, and removing SNMP targets 1. Double-click the Scanned Devices icon. The SNMP Target window appears. 2. To remove SNMP targets from the SNMP Targets list, select SNMP target entries and click Remove. 3. To add a new SNMP target, click Add. To edit a target, select the target from the SNMP Targets list and click Edit. 4. The Add SNMP Device window or Edit SNMP Device window appears. Configure the SNMP target using the item descriptions for both windows shown below. When finished, click OK.
Additional SNMPv3 fields. If you select “v3” as the SNMP version, the dialog asks for the following information: Item Description User The user name for the SNMP device. Authentication Protocol The authentication protocol used to access the SNMP device. Available choices are “None”, “MD-5”, and “SHA-1” Password/Verify The password for the user. Re-enter the password in the Verify field. The password must be a minimum of 15 characters.
Adding or updating Device Definition Files Device Definition Files (DDFs) allow the appliance to determine what type of device is connected and what sensors it can monitor. The Device Definition File view on the Scanned Device Configuration window lists which DDFs are installed and the option to add new DDFs or update to the latest version. To add and update your DDFs: 1. On the Device Definition Files view, click Add/Update Definitions.... 2.
Sensor settings Select an SNMP target from the SNMP Targets view and click Sensors to open the Sensor Configuration window. Monitored values available from the SNMP target are listed in the Sensors list. Select a sensor from the Sensors list to display thresholds defined for that sensor in the Thresholds selection list. Note: If the selected sensor does not support threshold configuration, a message advising you of this appears in the Thresholds area of the interface. To modify a sensor: 1.
IPMI Devices Note: The IPMI Devices icon is only available with the purchase of the 5-node Scanner/ IPMI Pack. For more information, contact your NetBotz authorized reseller or the NetBotz support team. The IPMI standard defines a hardware and software management interface and implementation that provide different hardware platforms with compatible server management and control functions.
Sensor settings Select an IPMI-enabled device from the IPMI Devices view and click Sensors to open the Sensor Configuration window. Once you select a sensor from the Sensors list, thresholds defined for the selected sensor appear in the Thresholds selection list. Note: If the selected sensor does not support threshold configuration, a message advising you of this appears in the Thresholds area of the interface. To modify a sensor: 1. Select a sensor from the Sensors list. 2.
Modbus Slave System Note: The Modbus Slave System icon is available only on the NetBotz Rack Monitor 570, 550 or on appliances for which the Advanced Software Pack has been purchased. For more information, contact your NetBotz authorized reseller or the NetBotz support team To configure your pod to communicate with a Modbus Master, double-click the Modbus Slave System icon. The Modbus Slave System Settings window is displayed and a list of pods connected to your appliance appears.
Exporting the Modbus map To export the Modbus map to a space-delimited text file: 1. Click View Modbus Map to display the map. 2. Click Save to file... in the upper right corner. A save dialog window opens. 3. Select the location and a file name for the saved data and click Save. Assigning a register address to a sensor To assign a Modbus register address to a sensor: 1. Select the pod from the list that hosts the sensor and click Modify Pod Settings.... 2.
Output control external port settings Select a device from the Output Control Configuration window and click External Ports. To modify devices connected to your output control devices: 1. Select the output control action to assign to the corresponding port from Relay Output Type. Note: Output control actions do not apply for devices wired between the NO and NC terminals. These devices have an always open state.
The following output control actions are available when the output control device is wired between the NC (Normally Closed) and COM terminals on the appliance: Action Description None No output action is associated with this port. One-Second Button (NC) When activated, a normally closed (NC) relay is switched to a closed state for 1 second, and then switched back to open.
Field Description Default relay output label The label used, by default, for any new output types added using this custom output definition. To modify a label, see “Output control sensor settings” on page 57. Unpressed value The text describing the relay in its unpressed state. Pressed value The text describing the relay in its pressed state. Active time (seconds) The time in seconds that the relay remains in a pressed state before reverting to the unpressed state.
Output control sensor settings After you select an output control device from the Output Control Configuration window and click Sensors, the Sensor Configuration window opens. Select a relay from the Sensors list to display thresholds defined for the selected sensor in the Thresholds list. Sensor settings. To modify a sensor: 1. Select a relay to modify from the Sensors list. Click Modify. 2. Type a label in the Label field.
Periodic Reports Configure your appliance to generate sensor reading reports and deliver them on a user-specified schedule. These reports contain readings for all sensors connected to your appliance. Double-click the Periodic Reports icon to open the Periodic Reports Configuration window.
Field Description Graph available history The maximum time period for which data is graphed. E-mail addresses The addresses to which periodic e-mail reports are delivered. 3. Type the appropriate values in the fields. 4. By default, all Periodic Reports are generated according to the Interval you specify. You can specify that a Periodic Report be active only during specific time ranges. To configure Advanced Scheduling: a. Click Advanced Scheduling.... b.
Field Description Graph priority Limit the amount of sensor data included with the periodic report. Select one of the following settings: High: Only sensor data associated with physical sensors that are integrated with or connected to the appliance are included in the report. Sensor data associated with shared pods is not included in the report. Medium: Sensor data associated with physical sensors and shared pods is included in the report. Data associated with scanned devices is not included.
This window features Primary and Backup tabs, each of which has the same fields available. The settings on the Primary tab are used by default for any periodic FTP reports. The settings on the Backup tab are used if communication with the Primary server fails. 3. Type the appropriate values in the fields. 4. By default, all Periodic Reports are generated according to the Interval you specify. You can specify that a Periodic Report is active only during specific time ranges.
This window features Primary and Backup tabs, each of which has the same fields available. The settings on the Primary tab are used by default for any periodic HTTP reports. The settings on the Backup tab are used if communication with the Primary server fails. 1. Type the appropriate values in the fields. 2. By default, all Periodic Reports are generated according to the Interval you specify. You can specify that a Periodic Report is active only during specific time ranges.
Unplugged alert severity. Select the severity to be applied to the reported alert from the list. This alert severity will be used if the Rack Access Pod is unplugged or no longer responding. Unplugged alert profile. Select the alert profile to use when the Rack Access Pod is unplugged or no longer responding. Configuring the Rack Access Pod sensors The Rack Access Pod 170 can have two sets of sensors attached to the appliance.
Rack Access System Note: The Rack Access System icon only appears when a Rack Access Pod 170 has been connected to the appliance. The Rack Access System dialog allows administrators to control access to resources secured by Rack Access hardware. Proximity cards, traditional key access, and remote access through Advanced View and the Web Client can be used to control access to hardware contained in racks utilizing the Rack Access System.
Authorization card swipes. There are two levels of authorization for cards in the Rack Access System. A Level One card does not require authorization from another card to access assigned doors. A Level Two card has the “Requires authorization card swipe” checkbox selected. When a Level Two card is swiped, it must be followed by a swipe from a Level One card before the Auto-Lock timer expires in order to access the door. Both cards must have valid access to the door in order for access to be granted.
To assign a door to a card. 1. Select the card from the list of registered cards. 2. Select a door (or doors) in the list of available doors in the All Available Doors pane. You can select all doors on an appliance by right-clicking the appliance and selecting Select all doors from the menu. You can also select all Door (1) doors or Door (2) doors 3. Drag and drop the door into the Assigned Doors pane.
Adding an appliance You can have multiple appliances (with associated Rack Access Pods) listed in the All Available Doors pane. A maximum of five appliances can be listed in the pane. When an appliance is added to the list, all of the registered cards on that appliance are added to the Registered Cards list. Cards can be assigned to doors across all appliances in the list. Note: All listed appliances must use the same HID Card Format.
Sensor Pods Use the information in this section to configure integrated sensor pods, NetBotz sensor pods, Rack Access PX-HID, and any other non-camera device associated with the appliance. The maximum number of attached pods an appliance can manage depends on the appliance: Appliance Attached Pod Capability NetBotz 550 and 570 Can host up to twelve external sensor pods, or up to thirteen Rack Access Pods. Up to four of the attached pods can be camera pods.
Settings Note: Fields displayed may vary depending on the features of the selected device. Select a device from the Sensor Pods window and click Settings. 1. Type a label for this device in the Label field. 2. Select options for Unplugged alert severity and Unplugged alert profile. 3. To enable alarm sounds on a sensor pod, select an alert Severity from the Alarm Sounds list. Select an Alarm Sound type from the Alert Sound drop-down list. 4. Click OK.
Thresholds. All sensors have a default threshold that is generated automatically by Advanced View. This threshold provides the typical threshold for the specific sensor type. Thresholds can be customized. Sensor thresholds are explained in detail in “Advanced View: Defining Thresholds” on page 107. To enable or modify a sensor threshold: 1. Select a sensor from the Sensor list. 2. Select the threshold to enable or modify from the Thresholds list. 3. Click Edit.... 4. The Edit Threshold window appears.
To add a custom sensor: 1. Click Add custom.... 2. Select the type of sensor you want to define and click OK. – Define the custom analog sensor a. Select Analog (0-3.3V) or Analog (0-5.0V), click OK to open the Add Analog Sensor window. This window features the following fields and controls: Field Description Sensor type The name of the custom sensor definition. Once defined, the Sensor type label appears only in the Sensor Type Installed drop-down list when specifying Sensor Pod external port settings.
– Define the custom dry contact sensor a. Select Dry Contact and click OK to display the Add Dry Contact Sensor window. This window features the following fields and controls: Field Description Sensor type label The name of the custom sensor definition. Once defined, the Sensor type label appears only in the Sensor Type Installed drop-down list when specifying Sensor Pod external port settings.
– Define the custom 4-20mA sensor a. Select 4-20mA sensor and click OK to open the Add Custom 4-20mA Sensor window. This window features the following fields and controls: Field Description Sensor type label The name of the custom sensor definition. Once defined, the Sensor Type Label appears only in the Sensor Type Installed drop-down list when specifying Sensor Pod external port settings. Default sensor label The label used, by default, for any new sensors added using this custom sensor definition.
Advanced View: Configuring Appliances The icons in the Appliance Settings area of the Configuration view enable you to configure your appliance. Backup Use the Backup icon to save your appliance configuration to a password-protected, encrypted file. This backup file includes all of the configuration settings for your appliance, including user account settings, pod configurations, alert actions, and profiles.
Custom Audio Clips Use the Custom Audio Clips icon to upload custom audio clips (in WAV or OGG format) to your appliance or to delete clips from the appliance. For more information about the Play Custom Audio alert action, see “Creating a play custom audio alert action” on page 114. Adding custom audio clips To upload a custom audio clip to your appliance: 1. Double-click the Custom Audio Clips icon. 2. Click Add custom audio clip. 3. Select a sound file.
DNS Use the Domain Name Server (DNS) icon to view or change the domain name server settings and to enable and configure Dynamic DNS functionality. Double-click the DNS icon to open the DNS Settings window. This window consists of the DNS pane and the Dynamic DNS pane. Configuring DNS settings To change the DNS settings, configure the following fields in the DNS pane: Field Description DNS Domain The DNS domain name to which this appliance belongs.
E-mail Server Double-click the E-mail Server icon to open the E-Mail Server Configuration window. Configure the following fields and click OK. Click Test E-mail Server to test your e-mail server settings. All settings except From address to appear in appliance e-mails are available for both a primary e-mail server and a secondary backup e-mail server. Field Description From address to appear in appliance e-mails The e-mail address that appears in the From field of e-mail generated by the appliance.
Using an external storage system Note: You cannot select the USB Drive option if no USB drive is connected to your appliance. To configure your appliance to use an External Storage System: 1. Click the External Storage icon to open the External Storage window. 2. Click Add... to open the External Storage Configuration window. 3. Select USB Drive and click Next. 4.
To configure your appliance to use a Windows Share: 1. Click the External Storage icon to open the External Storage window. 2. Click Add... to open the External Storage Configuration window. 3. Select Windows Share and click Next. 4. Enter information in the following fields: Field Description Remote hostname/IP The hostname or IP address of the NAS. Remote share name The name of the Windows share on the NAS. Subdirectory (optional) The subdirectory in the Windows share that stores data.
Using an NFS mount To configure your appliance to use network-attached storage for extended storage purposes: 1. Use the Backup icon to back up your appliance configuration before using External Storage to configure the appliance to use a network file system (NFS) mount. 2. Click the External Storage icon to open the External Storage window. 3. Click Add... to open the External Storage Configuration window. 4. Select NFS Mount and click Next. 5.
Reclaiming external storage data External Storage data is stored in a top-level directory on the remote server. The data is stored in a directory that is named using the MAC address of the appliance. For example, if your External Storage target NAS is \\Server1\storage, you specify a subdirectory of Headquarters, and if the appliance MAC address is 00:02:D3:02:9F:50, the data is stored at \\Server1\storage\Headquarters\00_02_D3_02_9F_50.
IP Filter Overview Use the IP Filter icon to limit access to your appliance to users connecting from specified IP addresses or IP address ranges. By default, users from any IP address can attempt to access your appliance. While access to the appliance is granted only when valid user account names and passwords are provided, IP Filtering provides additional security. The IP Filter allows you to specify the following behavior: • Which IP addresses can (or cannot) access the NetBotz appliance.
Filter fields Filter Action The Filter Action field can be set to Accept or Reject. This is the action that will be applied to network packets that meet the criteria specified in the filter. IP Address Specify either Include or Exclude. Include means the value as entered, while Exclude means all values EXCEPT the one entered. Enter an IP address in the field in the format xxx.xxx.xxx.xxx. The wildcard "*" can be used in the last two segments of the IP address to specify "all", such as "192.168.*.
posted to a monitoring StruxureWare Data Center Expert server. Configuring IP filters The IP filter has four behaviors when dealing with incoming network packets: • If there are no filter entries, all packets are accepted by the appliance. • If there are filter entries, those filter entries are evaluated in order from first to last as they appear in the entry list. • If a filter matches the corresponding packet data, the network packet is either accepted or rejected by the appliance based on that rule.
Example configurations Example 1: Allow default SNMP traffic from only 192.168.20.21, and reject all other activity. Filter 1: To accept UDP protocol network packets from IP address 192.168.20.21 on port 161. [Filter Action] Accept [IP Address] Include 192.168.20.21 [Protocol] Include UDP [Port] Include Filter 2: To reject all addresses that are exactly (over the full 32 bits of the address) "not 0.0.0.0". This effectively says "reject all". [Filter Action] Reject [IP Address] Exclude 0.0.0.
License Keys Use the License Keys icon to manage license key-enabled applications available on this appliance. A list of available applications appears in the License Keys window, indicating whether the application is enabled or not. If a license key is applied to an available function, the license key is displayed also. To enable a license key-based application: 1. Select the application from the License Keys list and click Edit. 2.
You can configure the appliance to post log data to a remote Syslog server. When the Syslog functionality is enabled, all events stored in the Audit Trail are also forwarded to a remote Syslog host for logging to a user-specified Syslog facility. To enable logging of events to a remote Syslog host: 1. In the Hostname field, enter the IP Address or Hostname of the remote Syslog server. 2.
The following controls and fields are displayed in the Edit Network Interface window: Field Enable Interface Description Select to enable this network interface. Configure automatically via DHCP Configure the network interface to use a DHCP server on the network to obtain its IP address, subnet mask, and gateway address. Configure using these settings Manually specify the IP address, subnet mask, and gateway address for the network interface.
PPP/Modem Note: The PPP/Modem icon appears only when a supported modem has been connected to the appliance and configured using the Serial Devices icon. For more information on configuring serial devices, see “Serial Devices” on page 99. For more information about supported modems and how they connect to the appliance, see the installation and quick configuration manual included with your appliance.
Field Description Dial-out response to alerts/reports Select the PPP dial-up action taken by the appliance when alerts or periodic reports are generated. Select from the following list: • Disabled—No dial-up action is taken when alerts or reports are generated. • Enabled—Use PPP to connect to the network whenever an alert or report is generated. Note: If the alert does not require a PPP connection, no connection will be made.
Managing your appliance using a dial-In PPP connection When dial-in support is enabled, the appliance places the external modem in auto-answer mode. This allows you to initiate a dial-in connection to the appliance through the external modem. To authenticate a PPP connection, you must provide a user ID and password for a user account with Administrator access. Once the PPP connection is established, you can access the appliance using the IP address 192.168.254.1.
Data to FTP Server notification method. If too many notifications are delayed, some will not be sent. • Sensor Data Fails to Load: If the appliance is transmitting a large amount of data, attempts to load sensor data may fail. Once the load on the appliance is reduced, the sensor data re-appears. Using SIM security If your SIM requires a PIN and you enter the PIN incorrectly, the SIM can become blocked. If your SIM is blocked, you will require a Pin Unblocking Key (PUK) from your service provider.
Pod, Pelco Camera, and Rack Access PX-HID Sharing Pod, Pelco Camera, and Rack Access PX-HID Sharing lets you select a single appliance to monitor remote devices distributed throughout your network. With pod sharing, the appliance connects with and receives data—including sensor data and camera images—directly from remote devices.
The maximum number of shared pods that an appliance can manage depends on the appliance. Appliance Shared Pod Capability NetBotz 570 and 550 Can host up to 16 shared pods. The total shared pods can be physically connected to or integrated with up to eight NetBotz appliances. Up to four of the shared pods can be camera pods. Can host the Rack Access PX-HID. NetBotz 455 Can host up to eight shared pods. Up to two of the shared pods can be camera pods. Can host the Rack Access PX-HID.
5. Select the remote device that you just added from the Remote Devices list. A list of pods available for sharing appears in the Available Pods list. 6. For each pod that you want to centrally manage, select the pod from the Available Pods list (ignore any instances of Base Enclosure in the list) and then click Share Remote Pod.
Field Password / Verify password Description Type the password to be used to access the remote device. 5. Click the camera from the Remote Devices list. The list in the Available Pods area updates. 6. Select Click OK to close the Pod, Pelco Camera, & Rack Access PX-HID Sharing Configuration window. 7. The camera will now appear in the Navigation pane.the camera from the list of available pods, then click Share Remote Pod.
Proxy Use the Proxy icon to allow the appliance to use an HTTP, Socks V4, or V5 Proxy Server. When configured, the appliance uses the proxy server for all e-mail and HTTP Post communications, allowing these communications to cross the firewall. These settings apply only to communications from the appliance. To use an HTTP, Socks V4, or V5 Proxy Server, double-click the Proxy icon to open the Proxy Settings window.
Region Use the Region icon to specify the region in which the appliance is used, configure the appliance clock to report time using a 12- or 24-hour clock, and control which languages are available for viewing in the Web Client. Note: Region settings affect only the date and time stamp displayed in image captures and the format of sensor readings and dates or times specified in alert notifications.
Restore Use the Restore icon to restore your appliance configuration using a configuration file created using the Backup icon. For more information, see “Backup” on page 74. To restore your appliance configuration: 1. Double-click the Restore icon. 2. In the Backup file field, enter the name and fully qualified path to the backup file or click Browse to navigate to the drive and directory in which the backup file is stored. Select the file then click OK. 3.
SMS Use the SMS (Short Messaging Service) icon to view or change the SMS settings used by your appliance. For more information, see “Creating a send short message e-mail alert action” on page 123. Note: This icon is available only if a modem that supports SMS messaging is installed in and configured for use with your appliance. The SMS Configuration window consists of Basic, Advanced, and Status tabs. The Status tab displays the level and quality of the SMS signal.
The following controls and data appear in the Advanced tab: Field Send debug messages to syslog Description When checked, debug messages are forwarded to the syslog host specified in the Configure Log Settings window. For more information see “Log” on page 86. Use default SMS settings Check to use the default SMS values for your SMS-capable modem. To use custom settings, uncheck this checkbox, check Use protocol descriptor unit, and enter Character set and Initialization commands.
The Version 3 pane contains the following fields: Field Description Available Users/Authorized Users Use the arrow buttons to authorize or de-authorize specific users. controls Authentication protocol Select the SNMP Version 3 authentication protocol used for SNMP Version 3 communications. Encryption algorithm Select the encryption method used for SNMP Version 3 communications.
Upgrade Use the Upgrade icon to check or upgrade Advanced View and BotzWare version installed on your appliance. Double-click the Upgrade icon to open the Appliance Upgrade window. The Current Version of BotzWare is displayed. Click Check APC Website to check for an updated version of Advanced View or BotzWare. The BotzWare and User Interface versions are displayed, as well as the most current versions available from the Web site. Check the components you want to upgrade and click OK.
Privilege Set Description Sensor Gives user access to only the Navigation, Sensor Data and selected portions of the Information/Action panes. User accounts configured with the Sensor Privilege Set can view the Cameras, Graphs, and About panes. This Privilege Set does not permit access to the Alerts pane, Configuration pane, or to the Appliance Log, Change Root Password, and Reboot Appliance Tool menu selections.
To delete a configured account, select the account from the Users pane and click Remove. Lost password recovery To recover from a lost password: 1. Locate the reset switch on the appliance. 2. Using a thin wire such as a paperclip, press and hold down the reset switch for ten seconds. This will cause the system to reboot. 3. Once the system reboots, you have two minutes to log in using the following default login values: a. For Advanced View • User ID: apc • Password: apc b.
Web Server Use the Web Server icon to view or change the HTTP and HTTPS IP ports through which the appliance Web server communicates. Double-click the Web Server icon to open the Web Server Configuration window. Basic Tab The Basic tab controls the IP ports used with HTTP and HTTPS connections to the NetBotz appliance. On the Basic tab: 1. Enter the IP port used for HTTP communications in HTTP port. 2. Enter the IP port used for HTTPS communications in HTTPS port. 3.
Advanced View: Defining Thresholds The appliance uses analog sensors and state sensors. Analog sensors report sensor readings as a value within a range of potential values defined by a minimum and maximum value, such as temperature or humidity readings. If the value reported by a sensor exceeds the specified threshold, an alert condition is reported. State sensors report sensor readings as one of two mutually exclusive states, such as a door being open or closed.
8. Check Enabled to enable the threshold. If this checkbox is not checked, the alert threshold is saved but is not active. 9. In Threshold-Specific Addresses, click Add... to enter the e-mail addresses of personnel to whom e-mail alert notifications should be sent if this threshold generates an alert condition. Click OK.
Defining State Thresholds To define a threshold: 1. Double-click the Camera Pods, Sensor Pods, or Scanned Devices icon. 2. Click Sensors... to open the Sensor Configuration window. 3. To define a threshold, select a sensor from the Sensors list. Defined thresholds for the sensor, if any, appear in the Thresholds list. 4. Click Add... to open the Select Threshold Type window. 5. Select the threshold to define and click OK. The Add Threshold window opens. 6. Type a name for the threshold in Threshold name. 7.
f. Unscheduled Remote Access Threshold - This is only available for Lock sensors and is not enabled by default. If a lock is opened with a remote command issued from Advanced View or the Web Client, an alert is generated. In order to allow remote access without generating an alert, you will need to modify the threshold schedule, disable the threshold for the desired timeframe, and disable the default “Unscheduled Access Threshold”. An unlock event will still be generated in the event log. 9.
Advanced Threshold Settings All Advanced threshold settings are optional. From the Advanced tab in the Add Threshold window: 1. In Return To Normal Delay, specify the number of seconds that must pass after this threshold returns to normal before the threshold state is considered normal. The default value is 0 indicating that the state is considered normal immediately after the measured value is no longer violating the threshold. 2. Set an Advanced Schedule for this threshold (optional).
Advanced View: Creating Alert Actions The information that must be provided for an Alert Action depends on which alert notification method you have selected.
Creating an activate button output alert action To create an Activate Button Output alert notification method: 1. Double-click the Alert Actions icon. 2. Click Add... to open the Add Alert Action window. 3. Select Activate Button Output and click OK. 4. Enter a name for this alert action in Alert action name. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
6. Check the alert Severities that apply to buttons to be activated. 7. Select an Output Device to play the audio alerts. Any camera pods connected to your appliance can be selected. 8. Select an Output Volume for the audio alert. By default, audio alerts are played at 75% of the output device maximum volume. 9. Click OK to save this Alert Action. Creating a play custom audio alert action To create an Alert Action to use Play Custom Audio alert notification: 1. Double-click the Alert Actions icon. 2.
Creating a send custom HTTP GET alert action To create an Alert Action to use Send Custom HTTP GET alert notification: 1. Double-click the Alert Actions icon. 2. Click Add... to open the Add Alert Action window. 3. Select Send Custom HTTP GET and click OK. 4. Enter a name for this alert action in the Alert action name field. 5. Select the language and territory using the Locales drop-down list. 6. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
Example target URLs. When creating a Send Custom HTTP GET alert action, a data handling application such as CGI script, ASP script, or servlet, for example, must be invoked on the Web host invoked in the Target URL, and data must be passed to the application in the proper format. The content of the Target URL field depends on the configuration of the target server which processes the HTTP GET. The following examples demonstrate two possible ways in which this alert action could be configured. Example #1.
Creating a send custom text file to FTP server alert action To create an Alert Action to use Send Custom Text File to FTP Server alert notification method: 1. Double-click the Alert Actions icon. 2. Click Add... to open the Add Alert Action window. 3. Select Send Custom Text File to FTP Server and click OK. 4. Enter a name for this alert action in the Alert action name field. 5. Select the language and territory using the Locales drop-down list. 6. Specify Advanced Scheduling (optional).
Creating a send data to FTP server alert action To create an Alert Action to use the Send Data to FTP Server alert notification: 1. Double-click the Alert Actions icon. 2. Click Add... to open the Add Alert Action window. 3. Select Send Data to FTP Server and click OK. 4. Enter a name for this alert action in the Alert action name field. 5. Select the language and territory using the Locales drop-down list. 6.
– Type the Base Filename for storing the data on the FTP server. The alert data is stored in a file with this name, followed by the .nbalert.xml file extension. Pictures from alerts are stored in files with this name, followed by the .n.jpg file extension, where n is the picture number (for example: 1, 2, 3). The Target Directory and Base Filename fields accept BotzWare macros. For more information on macros supported by BotzWare see “BotzWare Macros” on page 133. 13.
Creating a send e-mail alert action To create an Alert Action to use Send E-Mail alert notification: 1. Double-click the Alert Actions icon. 2. Click Add... to open the Add Alert Action window. 3. Select Send E-mail and click OK. 4. Enter a name for this alert action in the Alert action name field. 5. In Maximum Camera Pictures, enter the maximum number of available images included with the generated data.
14.If you do not want e-mail notifications sent when sensor readings return to a normal state, select the Advanced tab and check Do Not Send Return-To-Normal Messages. 15.To include only the header information necessary to ensure delivery of the e-mail message, select the Advanced tab and check Minimize Header Usage. 16.To specify the format in which captured images are sent, select the Advanced tab and select the format from Picture Export Format.
Creating a send HTTP post alert action To create an Alert Action to use Send HTTP Post alert notification: 1. Double-click the Alert Actions icon. 2. Click Add... to open the Add Alert Action window. 3. Select Send HTTP Post and click OK. 4. Enter a name for this alert action in the Alert action name field. 5. Select the language and territory using the Locales drop-down list. 6. In Maximum Camera Pictures, enter the maximum number of available images included with the generated data.
Creating a send short message e-mail alert action To create an Alert Action to use Send Short Message E-Mail alert notification: 1. Double-click the Alert Actions icon. 2. Click Add... to open the Add Alert Action window. 3. Select Send Short Message E-Mail and click OK. 4. Enter a name for this alert action in the Alert action name field. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
8. In the Advanced tab: a. If you do not want e-mail notifications sent when sensor readings return to a normal state, check Do Not Send Return-To-Normal Messages. b. To include only the header information necessary to ensure delivery of the e-mail message, check Minimize Header Usage. c. Specify a Message Size Limit (bytes) for e-mail messages generated by this alert action. d. Click to Send Both HTML and Plain Text Message. 9. Click OK to save this Alert Action.
Creating a send SNMP v3 inform alert action To create an Alert Action to use Send SNMP v3 Inform alert notification: 1. Double-click the Alert Actions icon. 2. Click Add... to open the Add Alert Action window. 3. Select Send SNMP v3 Inform and click OK. 4. Enter a name for this alert action in Alert action name. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
6. Check the alert Severities that apply to buttons to be activated. 7. In the Basic tab: a. Click Add..., enter an E-mail or SMS address to which the alert notification will be sent, select the language and territory using the Locales drop-down list, then click OK. b. Check Include Addresses from Thresholds to include threshold-specific e-mail recipients. Note: If the E-mail Addresses field is blank and you uncheck Include Addresses from Thresholds, no e-mail notifications are sent.
Creating a set beacon output state alert action To create an Alert Action to use Set Beacon Output State alert notification: 1. Double-click the Alert Actions icon to open the Alert Action window. 2. Click Add to open the Select Notification Method window. 3. Select Set Beacon Output State and click OK. 4. Enter a name for this alert action in Alert action name. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
Creating a set output switch 1 or output switch 2 alert action To create an Alert Action to use Set Output Switch 1 or Set Output Switch 2 alert notification: 1. Double-click the Alert Actions icon to open the Alert Action window. 2. Click Add to open the Select Notification Method window. 3. Select Set Output Switch 1 and click OK. 4. Enter a name for this alert action in Alert action name. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
Creating a set switch output state alert action To create an Alert Action to use the Set Switch Output State alert notification: 1. Double-click the Alert Actions icon to open the Alert Action window. 2. Click Add to open the Select Notification Method window. 3. Select Set Switch Output State and click OK. 4. Enter a name for this alert action in Alert action name. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
Creating a set outlet state alert action To create an Alert Action to use the Set Outlet State alert notification: 1. Double-click the Alert Actions icon to open the Alert Action window. 2. Click Add to open the Select Notification Method window. 3. Select Set Outlet State and click OK. 4. Enter a name for this alert action in Alert action name. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
Creating a set lock output state alert action To create an Alert Action to use the Set Lock Output State alert notification: 1. Double-click the Alert Actions icon to open the Alert Action window. 2. Click Add to open the Select Notification Method window. 3. Select Set Lock Output State and click OK. 4. Enter a name for this alert action in Alert action name. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
Creating a set reader output state alert action To create an Alert Action to use the Set Reader Output State alert notification: 1. Double-click the Alert Actions icon to open the Alert Action window. 2. Click Add to open the Select Notification Method window. 3. Select Set Reader Output State and click OK. 4. Enter a name for this alert action in Alert action name. 5. Specify Advanced Scheduling (optional). By default, all Alert Actions are active 24 hours a day, 7 days a week.
BotzWare Macros This appendix defines the macros supported by BotzWare. Note: Macros are case-sensitive and must be entered exactly as shown. Appliance Macros The following macros are supported for attributes that support Appliance macros: Macro Definition Example ${SERIAL} The serial number of the appliance. 5A0806V0014 ${IP} The dotted-decimal IP address of the appliance. 192.168.2.23 ${HOSTNAME} The hostname of the appliance. testbot.netbotz.com ${MODEL} The model of the appliance.
Macro Definition Example ${ROOM} The room (specified in the Location settings) for the appliance. C-100 ${ROOMROW} The row within the room (specified in the Location settings) for the appliance. AA ${ROOMCOL} The column within the room (specified in the Location settings) for the appliance. 25 ${HEIGHT} The height above the floor (specified in the Location settings) for the appliance. 60 ${BLDG} The building (specified in the Location settings) for the appliance.
Alert Macros Alert macros access attributes particular to the alert being processed at the time the macros are resolved. The following macros are supported for attributes that support Alert macros: Macro Definition Example ${SENSORLUID} The locally unique ID of the sensor generating the alert. TEMP1 ${SENSORGUID} The globally unique ID of the sensor generating the alert. B000113_TEMP1 ${ALERTTYPE} The type of alert. HIGHERR ${SENSORTYPE} The type of sensor generating the alert.
Macro Definition Example ${ALERT_LEVEL} The name of the specific alert sequence that caused the alert to be generated. Corresponds with the Label value of the alert sequence. First Alert Level, Second Alert Level ${CURRENT_ALERT_NUM} The number of times the alert sequence repeated, from 0 up to the Repeats value for the alert sequence. 0, 1, 2 ${ISACTIVE?yes?no} Specifies custom active vs. return to normal text. The strings yes and no can be replaced with user-specified strings.
Overloaded Appliances: Symptoms and Solutions Symptoms Some symptoms of an overloaded or busy appliance include: • HTTP time-out errors that occur while submitting configuration updates in Advanced View. • A significant delay between the time at which the alert condition occurred and the time at which the alert notification was delivered, based on the time of the alert noted in the notification. • Audio clips and/or camera clips associated with an alert notification are missing.
Solutions If your appliance has become overloaded, the following configuration adjustments will help alleviate the load on the appliance: • If you are using the Scanned Devices functionality, increase the scan interval. For information on the Scanned Devices functionality, see “Scanned Devices” on page 44. For details on increasing the scan interval, see “Adding, editing, and removing SNMP targets” on page 46. • If you are using Scanners, disable MIB2 scanning on devices.
• Wireless mode or SSL mode consumes more processing power and causes image captures or interactive viewing of camera images to have an even greater affect on performance. Verify that the appliance is configured to generate alert states and send alert notifications as efficiently as possible. • When viewing alerts in Advanced View, setting the refresh interval to None or to a high refresh interval allows a heavily-alerting appliance to load its list of alerts more efficiently.
Verifying Signed M-JPEG AVI Files Schneider Electric has included a simple command line utility that lets you verify that digitally signed M-JPEG files have not been tampered with since they were generated by your NetBotz appliance. This command line utility, AVIVRFY.BAT, is automatically installed along with the Advanced View and can be accessed from the Advanced View installation directory. In Windows installations, AVIVRFY.BAT appears as avivrfy.bat and in Linux installations, as avi-vrfy.
Radio Frequency Interference Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate this equipment. USA—FCC 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 when the equipment is operated in a commercial environment.
APC Worldwide Customer Support Customer support for this or any other APC product is available in any of the following ways: • Visit the APC Web site to access documents in the APC Knowledge Base and to submit customer support requests. – www.apc.com (Corporate Headquarters) Connect to localized APC Web sites for specific countries, each of which provides customer support information. – www.apc.com/support/ Global support searching APC Knowledge Base and using e-support.