HooperJM: Added a sub-heading for the events that will trigger a network alert

2024-08-30T23:01:55Z

Added a sub-heading for the events that will trigger a network alert

← Older revision		Revision as of 23:01, 30 August 2024
Line 58:		Line 58:
	*When a trigger event occurs, an email message will be sent to all addresses that have been validated and opted-in.		*When a trigger event occurs, an email message will be sent to all addresses that have been validated and opted-in.

	*The following events will trigger an alert:		=== The following events will trigger a network alert: ===

	*A Rogue Access Point is detected		*A Rogue Access Point is detected

HooperJM: Added image of alert settings dialogue

2024-08-30T22:51:33Z

Added image of alert settings dialogue

← Older revision		Revision as of 22:51, 30 August 2024
Line 29:		Line 29:

	*On the Unit Information page, click on the blue header in the card that represents the property		*On the Unit Information page, click on the blue header in the card that represents the property

	===Configure Alert Settings===		===Configure Alert Settings===
	*From the dropdown '''Menu''' (normally on the right-hand side of the screen), select '''Alert Settings'''

			* From the '''Menu''' dropdown, select '''Alert Settings'''
			* On the Network Alert Settings screen:

	[~~image]~~		[[File:Screenshot 2024-07-02 at 2.50.06 PM.png\|alt=Configure Alert Settings Dialogue. The email address has a yellow caution sign because the user has not yet accepted the opt-in email.\|thumb\|Configure Alert Settings Dialog]]
	*On the ~~Network~~ Alert Settings ~~screen:~~

	*Enter an email address for the first recipient.		*Enter an email address for the first recipient.

Line 56:		Line 56:
	*To remove an email recipient, click the circle slash icon next to the language identifier.		*To remove an email recipient, click the circle slash icon next to the language identifier.


	~~[image]~~
	*When a trigger event occurs, an email message will be sent to all addresses that have been validated and opted-in.		*When a trigger event occurs, an email message will be sent to all addresses that have been validated and opted-in.

HooperJM: Updated Introduction to be a heading not a page title

2024-08-30T17:25:38Z

Updated Introduction to be a heading not a page title

← Older revision		Revision as of 17:25, 30 August 2024
Line 1:		Line 1:
	=Introduction=		== Introduction ==
	Church Network Manager (CNM) can be configured to send email messages to a list of recipients based on events configured for a network. Alerts can be sent to any valid email address, and are not dependent on CNM access. They are specific to a single network. If a user is responsible for multiple networks, alerts will need to be configured for each network.		Church Network Manager (CNM) can be configured to send email messages to a list of recipients based on events configured for a network. Alerts can be sent to any valid email address, and are not dependent on CNM access. They are specific to a single network. If a user is responsible for multiple networks, alerts will need to be configured for each network.

HooperJM: Created the article.

2024-08-30T17:24:58Z

Created the article.

New page

=Introduction=
Church Network Manager (CNM) can be configured to send email messages to a list of recipients based on events configured for a network. Alerts can be sent to any valid email address, and are not dependent on CNM access. They are specific to a single network. If a user is responsible for multiple networks, alerts will need to be configured for each network.

There are two kinds of alerts in Church Network Manager-
#'''Network alerts'''- Triggered based on a predefined set of events available in the Meraki API. Not all supported events were selected, but the CNM team has chosen those most relevant to most users. These events will be enumerated later in this document.

#'''Sensor alerts'''- Triggered by events detected by one of the optional Meraki sensors.

We’ll explain network alerts first. Scroll down if you want to skip to instructions for sensor alerts.
==Configuring Network Alerts-==
===Navigate to your network in CNM===
*Go to: <nowiki>https://cnm.churchofjesuschrist.org</nowiki>

*Click on '''Search'''

*Search for your network using one of the following options:
**Firewall Serial Number
**Device Serial Number
**Property Number
**Unit Name
**Unit Number
**ReceiverUA
**CNM Network ID
**IP Address

*Click on the name of the unit in the search results.

*On the Unit Information page, click on the blue header in the card that represents the property
===Configure Alert Settings===
*From the dropdown '''Menu''' (normally on the right-hand side of the screen), select '''Alert Settings'''

[image]
*On the Network Alert Settings screen:

*Enter an email address for the first recipient.

*Select a language in which the emails will be sent.

*Click '''Verify'''.

*If desired, you can enter additional email addresses, with a corresponding language selection for each recipient.

*Click '''Save'''.

*Click '''Enable Network Alerts''', to ensure the setting is turned on.

*A validation and opt-in email will be sent to the email address entered. If the user doesn’t see a message, they might check their spam or junk folder, or try adding cnm-noreply@mail.churchofjesuschrist.org to their address book.

*Alerts will only be sent after the email recipient has opted-in by responding to the validation email.

*You are now ready to receive network alerts.

*To remove an email recipient, click the circle slash icon next to the language identifier.

[image]
*When a trigger event occurs, an email message will be sent to all addresses that have been validated and opted-in.

*The following events will trigger an alert:

*A Rogue Access Point is detected

*A gateway (AP) goes offline for more than 30 minutes

*A gateway becoming a repeater

*A WAN appliance goes offline for more than 30 minutes

*The DHCP lease pool is exhausted

*An IP Conflict is detected

*A rogue DHCP server is detected

*A switch goes offline for more than 30 minutes

*A new DHCP server is detected

*Power supply goes down for a managed switch

*Critical temperature alert for switches (only certain models supported)

For a detailed description of each alert, you can reference the Cisco Meraki documentation: <nowiki>https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alerts_and_Notifications</nowiki>
==Configuring Sensor Alerts==
===Navigate to your network in CNM===
*Go to: <nowiki>https://cnm.churchofjesuschrist.org</nowiki>

*Click on '''Search'''

*Search for your network using one of the following options:
**Firewall Serial Number
**Device Serial Number
**Property Number
**Unit Name
**Unit Number
**ReceiverUA
**CNM Network ID
**IP Address

*Click on the name of the unit in the search results.

*On the Unit Information page, click on the blue header in the card that represents the property
===Add Sensors to the Network===
If you haven’t already, add your sensors to the network.
*From the '''Menu''', select '''Add Devices'''.

*Enter the '''Serial Number'''

*Optionally give your device a '''Label'''

*Click '''Add Device'''

[image]

[image]
===Configure Alert Profiles===
*On the Network page, select the '''Sensors''' tab.

*Click '''Alert Profiles''' button the right of the screen.

*Enable, disable, or modify the sensor alerts in the default profile as desired. The default profile applies to all sensors on the network.

*Click the '''Add''' button.

*Give your new profile a name (Required field)

*In the next section, sensor alert settings are available in an accordion menu. Select the sensor type to expand the configuration options.

*Configure sensor alerts as desired.

*The bottom section is where you will select the specific sensors you want this profile to apply to.

*Click '''Save''' and notice the new profile name listed in the left pane.

*Close the dialog box.
===Configure Alert Settings===
*Back on the Network Page, select '''Menu''' (normally on the right-hand side of the screen), then select '''Alert Settings.'''

[image[
*On the Alert Settings Dialog, select the '''Sensor Alert Settings''' tab.

*Enter an email address for the first recipient.

*Select a language in which the emails will be sent.

*The email address will perform a validation step after you select a language.

*If desired, you can enter additional email addresses, with a corresponding language selection for each recipient.

*Click '''Save'''.

*Click '''Enable Sensor Alerts''', to ensure the setting is turned on.

*A validation and opt-in email will be sent to the email address entered. If the user doesn’t see a message, they might check their spam or junk folder, or try adding cnm-noreply@mail.churchofjesuschrist.org to their address book.

*Alerts will only be sent after the email recipient has opted-in by responding to the validation email.

*You are now ready to receive sensor alerts.

[image]
*When a trigger event occurs based on the alert profiles you configured or a default profile, an email message will be sent to all addresses that have been validated and opted-in.

*The following Meraki sensors are supported in CNM:

*Temperature and Humidity (MT10)

*Probe Sensor (MT11)

*Water Detection (MT12)

*Indoor Air Quality (MT14)

*Open/Close Detection (MT20)

*Smart Power Controller (MT40)
*(Note: Meraki also sells the MT15 and MT30, but CNM does not support them at this time.)
==Additional Resources==
*Meraki documentation for the MT series sensors: <nowiki>https://documentation.meraki.com/MT</nowiki>

*For a detailed description of each alert, you can reference the Cisco Meraki documentation: <nowiki>https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alerts_and_Notifications</nowiki>

Configuring Network and Sensor Alerts - Revision history

HooperJM: Added a sub-heading for the events that will trigger a network alert

HooperJM: Added image of alert settings dialogue

HooperJM: Updated Introduction to be a heading not a page title

HooperJM: Created the article.