||On the Conditions tab, add one or more conditions. For each condition you add, specify the rules for triggering event notifications. |
||For example, to keep track of heart monitors in a hospital, you might add rules to generate notifications when the following occur: (1) the heart monitor is missing for one hour, (2) the heart monitor moves off its assigned floor, or (3) the heart monitor enters a specific coverage area within a floor. In this example, add three separate rules to address these occurrences.|
To add a condition, follow these steps:
- Click Add to add a condition that triggers a notification.
- In the Add/Edit Condition dialog box, follow these steps:
- Choose a condition type from the Condition Type drop-down list.
- If you chose Missing from the Condition Type drop-down list, enter the number of minutes after which a missing asset generates a notification. For example, if you enter 10 in this text box, the mobility services engine generates a missing asset notification if the mobility services engine has not located the asset for more than 10 minutes after the device has become inactive or is no longer in the system. This condition occurs when the controller detects its absence and informs the mobility services engine about it, or if the mobility services engine does not hear anything about this device from the controller for 60 minutes by default. This value is configurable from the MSE command-line interface (accessible using cmdshell on the console) using the config mobile-node-inactive-in-minutes command for clients and config tag-inactive-time-in-minutes command for tags. Proceed to Step e.
- If you choose In/Out from the Condition Type drop-down list, choose Inside of or Outside of, then click Select Area. Entry and exit of assets from the selected area is then monitored. In the Select dialog box, choose the area to monitor, then click Select. The area to monitor can be an entire campus, building within a campus, a floor in a building, or a coverage area (you can define a coverage area using the map editor). For example, to monitor part of a floor in a building, choose a campus from the Campus drop-down list, choose a building from the Building drop-down list, and choose the area to monitor from the Floor Area drop-down list. Then click Select. Proceed to Step e.
- If you chose Distance from the Condition Type drop-down list, enter the distance in feet from a designated marker beyond which an asset triggers an event notification. Click Select Marker. In the Select dialog box, choose the campus, building, floor, and marker from the corresponding drop-down lists, and click Select. For example, if you add a marker to a floor plan and set the distance in the Trigger If text box to 60 feet, an event notification is generated if the monitored asset moves farther than 60 feet away from the marker. Proceed to Step e.
You can create markers and coverage areas using the Map Editor. When you create marker names, make sure they are unique across the entire system.
- If you chose Battery Level from the Condition Type drop-down list, select the check box next to the appropriate battery level (low, medium, normal) that triggers a notification. Proceed to Step e.
- If you chose Location Change from the Condition Type drop-down list, proceed to Step e.
- If you chose Emergency from the Condition Type drop-down list, click the button next to the appropriate emergency (any, panic button, tampered, detached) that triggers a notification. Proceed to Step e.
- If you chose Chokepoint from the Condition Type drop-down list, proceed to Step c. There is only one trigger condition and it is displayed by default. No configuration required.
- In the Trigger If text box, specify the time in minutes to trigger the notification. The default is 60 minutes.
- Select either Recurring or Non-recurring from the Notification Frequency radio button. If the frequency is non-recurring, the MSE sends absence notification only once. For recurring frequency, the MSE sends an absence notification periodically until the device becomes present again. Here period refers to the configured value in the absence definition.
- From the Apply To drop-down list, choose the type of asset (Any, Clients, Tags, Rogue APs, Rogue Clients, or Interferers) for which a notification is generated if the trigger condition is met.
If you choose Any from the Apply to drop-down list, the battery condition is applied to all tags, clients, rogue access points, and rogue clients.
Emergency and chokepoint notifications apply only to Cisco-compatible extension (CX) tags Version 1 or later.
- The Match By drop-down list contains the following choices, from left to right:
- Choose the matching criteria (MAC Address, Asset Name, Asset Group, or Asset Category) from the first drop-down list.
- Choose the operator (Equals or Like) from the second drop-down list.
- Enter the relevant text into the text box based on the Match By criteria you chose.
The following examples describe the asset matching criteria that you can specify:
- If you choose MAC Address from the first drop-down list, choose Equals from the second drop-down list, and enter a MAC address (for example 12:12:12:12:12:12) in the text box, the event condition applies to the element whose MAC address is 12:12:12:12:12:12 (exact match).
- If you choose MAC Address from the first drop-down list, choose Like from the second drop-down list, and enter 12:12 in the text box, the event condition applies to elements whose MAC address starts with 12:12.
If the MAC address is a partial MAC address, then it might cause a performance issue in the Prime Infrastructure.
- Click Add to add the condition you have just defined.
If you are defining a chokepoint, you must select the chokepoint after you add the condition.