Step 4 |
Enter the following parameters to configure the new notification:
-
Name: Enter a name for the new notification name.
-
Type: From the Type drop-down list, choose the notification type.
For a description of the available notification types, see the table below. When specifying the details, note that:
-
If a location hierarchy is selected, the hierarchy will be the specific area filter for that notification.
-
If a MAC address is entered, the MAC address will be a filter for that notification.
Table 2. Notification Types
Notification Type
|
Used for
|
Absence
|
Generating a notification when a client is undetected for more than 15 minutes.
|
Area Change
|
Generating a notification when a device changes its location between campuses, buildings, or floors.
|
Association
|
Generating a notification when a client is associated or unassociated.
|
Battery Life
|
As part of RFID telemetry, Cisco CMX receives battery information which are of type Low, Medium, and Normal. Depending on the condition(s) set in the notification rule, notifications are generated for tags reporting similar battery
status.
Note
|
This notification is applicable for RFID tag only.
|
|
Chokepoint
|
As part of RFID telemetry, Cisco CMX receives chokepoint details when a tag encounters it. A notification is generated when
Cisco CMX detects an encountered mac that matches the chokepoint mac from notification rule.
Note
|
This notification is applicable for RFID tag only.
|
|
Emergency
|
As part of RFID telemetry, Cisco CMX receives event information which are of type Any, Unknown, Panic Button, Detached, and Tampering. Depending on the condition(s) set in the notification rule, notifications are generated for tags reporting similar events.
Note
|
This notification is applicable for RFID tag only.
|
|
In/Out
|
Generating a notification when a device is detected as moving into or moving out of a specific area in the location hierarchy.
|
Location Update
|
Generating a notification when a device's location is being recalculated.
The Location Update notification is based on the RSSI from the different APs that detect the device.
|
Movement
|
Generating a notification when a device moves more than a specified distance.
|
Network Design Changed
|
Generating a notification when maps are changed.
|
-
Conditions: Depending on the notification type selected, the Conditions parameters are displayed. Enter the required conditions for the new notification.
Note
|
-
For some notifications types such as Association, Absence, and so on, you must provide Device Type as a condition parameter. The Device Type field on the Create New Notification window provides these options: All, RFID Tag, Client, BLE Tag, and Interferer. For notification types Area Change, In/Out, Location Update, and Movement, the Device Type condition has the following additional options: Rogue Client and Rogue AP.
-
For the In/Out notification type, if the In option is selected in the Condition field, this warning message is displayed: Please make sure to add 'Out' condition with same Hierarchy. Conversely, if the Out option is selected in the Condition field, this warning message is displayed: Please make sure to add 'In' condition with same Hierarchy.
-
For the Location Update, In/Out, and Movement notification type, choose the device status from the Status drop-down list. The association status for the client device are All, Probing Only, and Associated. This condition helps to filter the clients by their association status and sends notifications only for the filtered subset
of client devices.
-
For the Location Update notification, Cisco CMX provides a new Status option for the Client device type. Use this option to filter notifications to either associated or probing devices. If the Status option is not selected, the default option (All) is considered, and then notifications are sent for both associated and probing clients.
-
For the Location Update notification with device type as BLE tag, Cisco CMX will receive details such as UUID, Major, Minor fields in the payload.
-
To view In/Out notification details for all locations, we recommend that you configure seperate In/Out notifictions for each
hierarchy created in the Activity Map window.
-
For the notification type Battery Life, the conditions All and Any indicates the same battery life status. You can either select All or Any to incule all available battery life statues conditions to create the notification.
-
For the notification type Emergency, the conditions All and Any indicates the same emergency status condition. You can either select All or Any to incule all condition types to create the notification.
|
-
MacAddress: Enter the MAC address. The defaul is all.
-
Receiver: From the Receiver drop-down list, choose the receiver type as HTTP, HTTPS, or Email. For HTTP and HTTPS receiver, you must provide the host address, port number, and url.
Note
|
When FIPS mode is enabled in Cisco CMX and the receiver is selected as HTTPS, you must import a CA certificate corresponding to that receiver. Use the Browse field to import CA certificate which is signed with northbound notification receiver's server certificate. For more information,
see Configuring Notification Listener in FIPS Mode.
The imported CA certificate is used to validate receiver's certificate when Cisco CMX tries to establish TLS connection to
the receiver to send notifications to it.
If northbound notification receivers were added prior to enabling FIPS mode in Cisco CMX, you must edit individual northbound
notification receiver and then import CA certificate or remove and add the northbound notification receiver again.
|
-
HTTP Headers: Enter the HTTP header inputs for Key and Value. Click the plus icon to add more custom HTTP headers to the notification. You can add a maximum of three custom HTTP headers.
Note
|
HTTP headers are manadatory for northbound notifications to connect to third party services.
|
-
MAC Hashing: Click to disable the MAC hashing. By default, MAC hashing is enabled.
-
Message Format: From the Message Format drop-down list, choose the format as JASON or XML.
-
Salt: Enter a secret hash key.
|