Content
Introduction
This page describes how to configure site-wide vs. local settings in a M500 dual-cell configuration.Â
Site-wide vs. Local settings
Site-wide settings are applicable to all base stations in a dual-cell configuration. When you update a site-wide setting via provisioning, the setting will be automatically updated for all base stations in the system.Â
Local settings are applicable to a specific base station in a dual-cell configuration. When you update a local setting via provisioning, the setting will only be updated for the specified base station.Â
WebUI
On the primary base station, the WebUI displays both site-wide settings and local settings:
- Changes to the site-wide settings will be automatically applied to all base stations.
- Changes to the local settings will only be applied to the primary base station.
On the secondary base station, the WebUI displays local settings only:
- Changes to the local settings will be only be applied to the secondary base station.
Below are some examples of WebUI pages that display local settings:
System → Base Preferences
Network → Advanced
Servicing → Provisioning
The following local settings are not available on the WebUI, and must be configured via provisioning:
- multicell.multicast_address
- multicell.multicast_ipv6_address
- multicell.site_id
- network.dhcpv6_vendor_class_id
- network.ip.pppoe.service_name
- provisioning.pnp_response_timeout
- provisioning.remote_check_sync_enable
Provisioning
The file fetching rules for provisioning.server_address stay the same, but the way that imported settings are applied depends on the base type:
| Base Type | Import Behavior |
|---|---|
| Single | All settings will be self applied. |
| Primary |
|
| Secondary |
Note: Before it joins a site, a secondary base will self apply all settings. |
Suggested practice for dual-cell operation
Have one MAC-specific file (e.g. snomM500-000413A11FA7.htm) for each individual base.
- Include local settings for each base to its associated MAC file for both primary and secondary base.
- Include site-wide settings to the MAC file of the primary base. Alternatively, site-wide settings can be included to a separate generic file (e.g. snomM500.htm) if separating local and site-wide settings in two files is the preferred approach.
Exporting settings
The way that settings are exported depends on the base type:
| Base Type | Export Behavior |
|---|---|
| Single | All settings will be exported. |
| Primary | Both site-wide settings and local settings will be exported. |
| Secondary | Only local settings will be exported. Note: Before it joins a site, a secondary base will export all settings. |
Further Information
Related articles
Overview
Content Tools
Tasks
