There's certainly room for improvement. When the ISP goes down, you'll get an alert for the firewall and every managed switch and AP on the network.
But it does let you know there's a problem before the clerks complain on Sunday.
Network alerts
-
russellhltn
- Community Administrator
- Posts: 35576
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Network alerts
In case you didn't notice, Church Network Manager (CNM) has the ability to email alerts when things happen. Like when the system goes off-line, or comes back on-line.
There's certainly room for improvement. When the ISP goes down, you'll get an alert for the firewall and every managed switch and AP on the network.
But it does let you know there's a problem before the clerks complain on Sunday.
There's certainly room for improvement. When the ISP goes down, you'll get an alert for the firewall and every managed switch and AP on the network.
But it does let you know there's a problem before the clerks complain on Sunday.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
-
brucew
- New Member
- Posts: 3
- Joined: Tue Jan 14, 2025 12:08 pm
Re: Network alerts
That is great. Some of us STS proactively monitor for network issues and we don't have as many diagnostic features with CNM as with the older system.
One thing to know though, you will get 2 categories of false alerts regularly that you'll just have to ignore (some filtering of these might be useful):
* "Rogue AP detected", these are detected every time Miracast/Screen Sharing is used on a smart TV. They use WIFI-Direct which is not actually going over the church network but are reported as an AP. You'll know them by the ssid beginning with "DIRECT-". If it uses some other SSID then you may actually have a rogue AP.
* "Client IP conflict detected", coming from the Cisco gear (MX64 switch in our case) just for a moment when the system has been reboot. Some of the gear seems to momentarily come up with a fixed IP before getting the correct one assigned. Of course, if they come from other equipment or happen at other times then there is a problem with someone likely incorrectly using a static IP.
One thing to know though, you will get 2 categories of false alerts regularly that you'll just have to ignore (some filtering of these might be useful):
* "Rogue AP detected", these are detected every time Miracast/Screen Sharing is used on a smart TV. They use WIFI-Direct which is not actually going over the church network but are reported as an AP. You'll know them by the ssid beginning with "DIRECT-". If it uses some other SSID then you may actually have a rogue AP.
* "Client IP conflict detected", coming from the Cisco gear (MX64 switch in our case) just for a moment when the system has been reboot. Some of the gear seems to momentarily come up with a fixed IP before getting the correct one assigned. Of course, if they come from other equipment or happen at other times then there is a problem with someone likely incorrectly using a static IP.