Setting Up 1041N and 702i Wireless Access Points

Last Updated: 16 October 2017 at 15:23

The FM group is responsible for purchasing and installing wireless access points; however, they may choose to delegate installation to an experienced technology specialist. The following steps can be used to set up Cisco 1041N or 702i wireless access points in a meetinghouse.

Note: The 1041N and 702i wireless access points will only work properly when connected to a meetinghouse firewall, or a switch connected to the firewall.

Instructions

  1. The power injector should be plugged in to a power outlet convenient to the firewall or a switch connected to the firewall.
  2. A network cable should be run from the power injector port labeled “TO SWITCH” to the firewall or to a switch connected to the firewall.
  3. A separate network cable should be run from the power injector port labeled “TO AP” to the 1041N or 702i wireless access point port labeled “ETHERNET.”
  4. The 1041N or 702i should be positioned horizontally with the rounded side facing down. If vandalism is not a concern, it is preferable to mount the 1041N or 702i to the underside of a ceiling. If you are placing the 1041N or 702i in an attic, it should be mounted to the underside of a shelf situated at least one foot above the attic floor. The 1041N and 702i should not be placed in locations where metal will obstruct the wireless signal.
  5. Be certain that you comply with all regulations in your country for wireless communications.

Once connected properly, the 1041N or 702i should configure itself automatically. A steady LED light in a color other than amber or red indicates a successful connection to the access point. The Getting Started Guide: Cisco Aironet 1040 Series Access Points describes LED behavior for the 1041N. The Getting Started Guide: Cisco Aironet 700 Series Access Points describes LED behavior for the 702i. The Cisco documents referenced above should be studied for detailed instructions on installing and configuring the relevant access point. Configuration often completes in less than 15 minutes but could take two hours or more.

You may want to configure the access point in a convenient place and later move it to its location in the meetinghouse (be sure to test it after mounting). A link speed of around 54 Mb/s or more is considered good. Although 100 or more clients can theoretically be accommodated on a wireless access point, for good user experience you may want to plan for 25 or fewer simultaneous connections. Every connection to the access point will have some network overhead; when several people stream video or update apps at the same time, they will use much of the available bandwidth, which can seriously degrade network performance for other users. You may want to remind people that, in church, they probably don't need to use a computer, tablet, and Wi-Fi cell phone simultaneously.

Wireless signal strength can be viewed graphically using the free Wifi Analyzer application for Android devices, which can be downloaded from Google Play. The "Channel graph" view shows graphically the name (SSID) and signal strength of each Wi-Fi frequency channel. The "AP list" view shows the Wi-Fi signal strength and channel number of every available access point. Tap the check mark at the top of the display to show the IP address, link speed, and other information about the access point currently connected to your Android device, including information about the DHCP lease duration. For Church DHCP networks, the lease duration is set to 30 minutes (1800 seconds). Be aware that DHCP clients will renew their lease after half the lease duration, which is 15 minutes (900 seconds).

Troubleshooting

If, after being plugged in correctly for 24 hours, a 1041N or 702i is still not working properly, troubleshooting options include the following:

  1. Connecting the power injector directly to the meetinghouse firewall (from the “TO SWITCH” port on the power injector to one of the public zone LAN ports on the firewall, typically LAN port 0 or 1). You may use a PoE port on the firewall, if activated.
  2. Power cycling the power injector (unplugging the power cable for a few seconds and then plugging it back in). For PoE connections, unplug and replug the ethernet cable.
  3. Checking with the internet service provider to make sure they are not blocking UDP ports 5246 and 5247.
  4. Contacting the Global Service Center (GSC) if other options don’t work.