The next step is to setup the AP in Meraki. (The configurations for remotely managed Access Points can be found at the end of the Configure AP process).:
- Log into Meraki
- Select the organization at which the device will be located from the next page. Note: This page will not show up if you belong to a single organization. Instead you will be redirected to that organization. This Organization will be 'Managed Services' unless otherwise instructed. See image below:
Meraki Organization: What organization will this location be added to in Meraki?
- Select Organization > Inventory.
- The Inventory page shows all devices that are both used and unused for the network. Check to see if the device already exists in the list by selecting the "Both" button located above the inventory table and inserting the serial number () in the "search inventory bar. (see image below)
- If the device is found in the list skip to the next step.
- If the device is not found locate and click on the Claim button above the tables top right corner. Enter the serial number (Serial Number (First AP or if there's only One AP)) that is found on the Meraki Access point and click the "Claim" button. (see image below) The device will now show up under the "Unused" section of the inventory
- Make sure that the "Unused' button is selected (located above the table next to the "Search inventory" box. Locate the device that was just added and check the box next to the MAC Address column.
- (see image below) Now that the device is selected, a new button is available to use. The "Add to ..." button is located above the top left corner of the inventory table. Select this button.
- In the drop down, select the "New network" option. Enter the name of the network: Location (Name of Location as seen in Automation, see name of location in signed agreement if uncertain)
- Select the "Configuration" drop down. The options will be "Use defaults" or "clone". Below "clone" will be listed all the networks that belong to this organization. Select the first network below the "clone" option. We will clone the existing network to reduce the amount of configuration that is needed
Be sure to select the new Network you created by selecting the Location (Name of Location as seen in Automation, see name of location in signed agreement if uncertain) Network from the Network drop down menu in Meraki.
A Cloned network copies all the settings from another network. This means all setting are identical including the SSID's, which is not desirable. We will need to confirm the following settings are configured correctly before moving forward.
First, go to Network-wide > General
- You must revise the Local time zone to reflect what's recorded for the Network being configured.
- Time Zone of Location (Must use Time Zone as identified in Meraki, see CSM for more on how to find this if uncertain).
- Next, underneath 'Location and scanning, configure to the following:
- Analytics: Enabled
- Scanning API: Enabled
- Post URLs: Must be added if not already registering within the cloned network. If cloning a network with 'Managed Services' Organization within Meraki, please use the following Post URLs
- Click Validate for all three Post URLs above and click Save.
- If NOT a Network within Managed Services, the Customer Success team member will need to navigate to a different Network within the applicable Organization the new network is being configured within. Copy & paste the post-URL and password information for validation in a similar manner as above.
- Post-URLs are created by the development team. Should a network configuration be necessary for a network not managed by Bloom Intelligence (i.e. a remote network configuration) please jump to the process listed at the end of the Configure AP list).
- Save Changes
From there, Network-Wide configurations are complete. Next are Wireless configurations.
Go to Wireless > Access Points
- Select any Access Point within the drop down. As this is a new network, it should be the actual MAC address of the Access Point(s) themselves that are listed.
- Rename the device by clicking the pencil icon adjacent to the MAC address listed name.
- Rename the device to the location's name OR if multiple APs, list as the location name AP 1, 2, 3 etc.
- Add the address within the Address field by selecting the pencil icon.
- Location Address
- Make sure, after pasting the address, that the Move Marker icon is selected.
- Click save.
- If more than one AP, select the arrow icon to navigate to the next AP. Rinse and repeat until all APs are updated.
The SSID's are typically the name of the network and since we cloned another network, this new network will have the cloned network's SSID.
- In the menu on the left select Wireless > SSIDs
- Networks typically have one or two SSID's. The first is the guest network where visitors to the location can connect and will go through the Bloom Intelligence Captive Portal. The second network is a private network that the business uses to allow its employees to connect. The second network does not use the Captive Portal. To rename the first network select the "rename" link and fill in the new name: @Location (Name of Location as seen in Automation, see name of location in signed agreement if uncertain) Guest Wifi. Do the same for the private network but the convention for name is the business name followed by Private. In this case: @Location (Name of Location as seen in Automation, see name of location in signed agreement if uncertain) Private
- Click on the "Save changes" button to update the SSID settings before continuing
Select Wireless > Access control and confirm the guest SSID is configured correctly (leave all other settings alone unless listed below).
- Make sure the SSID is set to the Guest signal.
- Network Access must have the Association requirements set to Open
- Splash page must be set to Click-through
- Captive portal strength must be set to Block all access until sign-on is complete
- Walled garden must be set to Walled garden is enabled
- Walled garden ranges MUST include the below ranges:
- Controller disconnection behavior must be set to Restricted
- Addressing and traffic must have the Client IP assignment set to NAT mode and Content filtering set to Block adult content
- Wireless options should be set to Dual band operation (2.4 GHz and 5 GHz) and Minimum bitrate (Mbps) to the lowest density along the slider.
- Save changes.
- Make sure SSID is set to the Private signal within Access Control.
- On the Access Control page locate the "Association requirements" under the "Network Access" section. Ensure that "Pre-shared key with WPA2" is selected under "Association requirements" and that the password is set. The convention is to use the Business name followed by the street address number. i.e. for the Crepevine locations at 1304 N Monroe St, the password would be "Crepevine1304". The business may choose to have a different password if they so desire (see below for picture)
- The address for this location is: Location Address
- Next we want to make sure that the private network is not using a captive portal. Locate the "Splash Page" settings under the "Network Access" section and check to make sure that the private network settings is set to "None (direct access)".
- Next we want to make sure that under the "Addressing and Traffic" section, the "Client IP assignment" is set to "Bridge mode: Make clients part of the LAN".
- Next under the "Wireless Options" section, the "Band selection" should be set to "Dual band operation with Band Steering".
- When you have updated all the settings click the "Save Changes" button at the bottom of the page.
Finally, go to Wireless > Splash page
- Make sure SSID is set to the guest signal.
- Custom splash URL must be set to include the following URL: http://bloomwifi.com/page/authenticate
- The Splash behavior Splash frequency must be set to Every week unless otherwise specified by the customer.