Temple Technology

2023-09-08T18:52:44Z

NormanKR:

__NOTOC__
[[Category:Temple Technology]]

<div style="margin: 10px 0px 0px 0px;">[[File:OahuLaieMormonTemple-stock.jpg|left|thumb]]
This content is provided by product managers, moderators, and technology specialists and is subject to change. For overviews of different technology, or information on your calling as a technology specialist, go to [https://www.churchofjesuschrist.org/help/support/meetinghouse-technology/?lang=eng&_r=1&cid=vb-mhtech MHTech]. Training modules (for Technology Specialist) and videos on how to use the TechWiki can be found [[Videos for Tech Specialists|here]].

<div class="mw-category">
*
*
*
*
*
*
*
*
*
</div>

<br>

Temple Technology

2023-08-17T22:07:07Z

NormanKR:

Network Menu Options

2023-08-15T17:14:00Z

NormanKR:

> [[Temple Technology]]

Each network has the following Menu Options:
[[File:Menu Options Local Manager.png|thumb|800x800px|alt=|left]]
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>

# '''Add Devices''' - add Switches and Access Points to this network
# '''IP Assignment''' - [[Assigning a Static IP Address|assign static IP addresses to devices that need a static IP address]]
# '''Group Policy''' - [[CNM Group Policies|Group Policies bypass the terms of use page or add IoT devices to a network]]
# '''Change log''' - Records all changes to this network for the last 3 months.
# '''Blink Firewall''' - Blinks the little light on the front panel of the firewall to locate the Firewall and determine communication.
# '''Reboot Firewall''' - Power Cycles the firewall but does not delete any configurations.
<br>
<br>

[[Troubleshooting Firewalls|<br>Firewall Troubleshooting tips]]<br> <br>

2023-08-10T17:06:03Z

NormanKR:

__NOTOC__
[[Category:Temple Technology]]

<div style="margin: 10px 0px 0px 0px;">[[File:OahuLaieMormonTemple-stock.jpg|left|thumb]]

The content of this wiki does not always reflect official Church information. This content is provided by product managers, moderators, and technology specialists and is subject to change. For overviews of different technology, or information on your calling as a technology specialist, go to [https://www.churchofjesuschrist.org/help/support/meetinghouse-technology/?lang=eng&_r=1&cid=vb-mhtech MHTech]. Training modules (for Technology Specialist) and videos on how to use the TechWiki can be found [[Videos for Tech Specialists|here]].

<div class="mw-category">
*
*
*
*
*
*
*
*
*
</div>

===[[Meetinghouse Networking|Temple Networking]]===

* [[Network Training]]
* [[Temple Network Configuration|Temple Network Overview]]
*
* [[Temple Firewall, Switch and Access point Activation in CNM]]
* [[Temple Switch Configuration]]
* [[Temple Wireless Configuration]]
*
*
* [[Temple Network Zones]]

* [[Temple Network Failover Process]]
* [[Improving Internet Access]]
* [[Assigning a Static IP]]
* [[Creating a Group Policy]]

=== TroubleShooting Network Devices ===
* [[Troubleshooting Firewalls|Troubleshooting Meraki firewalls]]
* [[Troubleshooting Meraki switches]]
* [[Troubleshooting Meraki Wireless Access Points]]

</div>

Troubleshooting Wireless Access Points

2023-08-10T17:01:11Z

NormanKR:

=== Only Cisco or Meraki APs added through the CNM portal are supported by the GSD, Network Operation, and Network Engineering. ===

== '''Access Points are offline, wireless is unavailable, or wireless users are unable to access the internet''' ==

# Verify that the Meraki Firewall is powered up and indicates that it is online.
## Check the Firewall status indicator light and verify that it is solid white or blinking white.
## If the Meraki firewall is not online, follow the process outlined in the [[Troubleshooting Firewalls|Meraki firewall troubleshooting guide]].
# Verify that the Meraki Switch(es) is(are) powered up and indicate that they are online.
## Check the status indicator light and verify that it is solid white or blinking white.
## If the Meraki switch is not on-line, please follow the process outlined in the [[Switches Troubleshooting|Meraki switch troubleshooting guide]].
# Verify that Meraki APs are connected directly to a Meraki PoE switch (Meraki MR3x APs are the only supported wireless solutions for meetinghouses).

=='''Check the AP status light (follow this process for each Meraki AP in question):''' ==

# '''ORANGE''' indicates that the device is booting. The orange light comes on as soon as the AP is powered up and may remain orange for a few minutes while it is booting.
## Normal condition immediately after booting.
## From orange the next state is normally the Rainbow.
# '''RAINBOW''' (in this state the light will transition through several colors) indicates that the device is initializing its configuration and pulling information from Meraki’s cloud controllers.
## Under normal operation, once the AP has initialized and downloaded its configuration the next state is solid Green.
# '''BLINKING BLUE''' indicates that the device is updating it's firmware.
## This is not a normal circumstance but does indicate that the AP is able to communicate with the internet and the Meraki cloud.
## Once the update is complete the AP will reboot and return to normal operation.
# '''SOLID GREEN''' indicates that the AP is operational, but no devices are connected to it.
# '''SOLID BLUE''' indicates that the AP is operational and has devices connected to it.

== '''Status lights indicating error or problems with the AP:''' ==

# '''ORANGE''' - An indicator light that is permanently orange indicates that the device is not booting properly.
## Power cycle the device by disconnecting the power from the Meraki switch and reconnect it.
### If the error persists, contact the GSD
# '''ORANGE and RAINBOW''' - An indicator light that is continuously cycling between orange and rainbow indicates a problem with internet connectivity.
## Verify that the device is connected directly to the Meraki switch. APs must be directly to the Meraki switch for proper functionality.
## Make sure that the port on the Meraki switch is properly configured for as an AP port in the CNM switch management tool.
## If the AP is connected to a properly configured port on a Meraki switch and still cycling between Orange and Rainbow status lights, perform a factory reset on the AP.
### If the error persists, contact the GSD.

== '''Status lights on the AP indicate normal operation (Solid Blue), but users are not able to reach the splash page or access the internet:''' ==

# Verify that users are joined to “Liahona” and not another SSID. Liahona is the only supported SSID for public access using Meraki APs.
# Verify that the user’s IP address is properly configured:
## All devices connecting to meetinghouse networks should be set up for dynamic (DHCP) addressing.
### When connected to “Liahona” user ip addresses should be in the range 192.168.108.2-255, 192.168.109.0-255, 192.168.110.0-255, or 192.168.111.0-254.
### The default gateway on user devices should be 192.168.108.1.
### The subnet mask should be 255.255.252.0.
### DNS Servers must be set to 8.34.34.91, 8.34.34.92, 8.34.34.93, 8.35.35.91, 8.35.35.92, or 8.35.35.93.
### Other DNS servers are not permitted.
## Use the IP Address Reservation Tool in CNM any time that a static reservation is needed.
## If the IP address is static and the above IP address requirements are not true for the client device(s), there is likely a rogue DHCP server on your network.
## Only one DHCP server can serve a network at any given time. You will need to find any devices acting as DHCP servers and remove or disable them.
# Incorrect IP addresses may also indicate that the meetinghouse network is being “spoofed”. This occurs when someone else creates a wireless network nearby using the same SSID and password hoping to get users to join unknowingly so that their experience can be impacted, or personal data compromised.
# Power off all APs in the meetinghouse and see if the SSID is still present.
# Verify that the AP is connected to the Meraki switch, and that the switch port is set to “AP” in the CNM switch management tool.
## Power injectors and in line switches are not permitted. Meraki APs must connect to Meraki switches to function properly.
# APs connected to switch ports configured for “Public”, “Special”, “Facility”, or “Workforce” may have normal status lights, but client traffic will not pass properly through the switch.

== '''Users connect to the network and are unable to communicate on the network:''' ==

# Verify that all Meraki hardware is online (white indicator lights on firewalls and switches, green or blue indicator lights on wireless access points)
# Check the IP address settings on the devices that are unable to access the internet.
## For devices connected to the Public zone:
### IP Address – 192.168.X.Y
#### X is some number ranging from 108 to 111
#### Y is some number between 1 and 255.
#### If X is equal to 108, Y cannot be equal to 1
#### If X is equal to 111, Y cannot be equal to 255
### Subnet Mask – 255.255.252.0
### Default Gateway – 192.168.108.1
### DNS Servers – Vary depending
# If devices are unable to reach a DHCP server they will usually show an IP address beginning with 169
## Verify that Meraki APs are connected only to the Meraki switch(es), most switches found in meetinghouses cannot support the type of connection required for the Meraki APs in our current meetinghouse network design
## Verify that the ports on the Meraki switch used for wireless access points are configured for “AP” in CNM
# For devices connected to Facility zones and Workforce zones:
## IP addresses will vary from site to site, refer to CNM to determine what IP address range your devices should use.
# Rogue DHCP servers are the most common cause of invalid IP addresses:
## Most wireless routers and access points purchased from retail providers have a built in DHCP server built in which is enabled by default
## It is only permissible to have one DHCP server running on a given network
## Locate any other potential DHCP servers (i.e. wireless extender/repeater, 3<sup>rd</sup> party router installed downstream from firewall)
# If Public zone users are getting IP addresses in the ranges that are indicated for Workforce or Facility zone, you have a wireless access point connected to the wrong zone
## Remove all wireless access points that are not managed by CNM (i.e. wireless extender/repeater, 3<sup>rd</sup> party router installed downstream from firewall) from the network
## Meraki APs should not have this problem
## Contact the Global Service Desk once you have verified that there are no wireless access points other than those indicated in CNM
# The pool of IP addresses is much smaller in these zones than in the public zone, allowing wireless users to connect to any of these may cause the pools to become exhausted and prevent wireless users from accessing the network