The SDC-CF10G module has two connectors
for 2.4 GHz antennas.
The SDC-CF10AG module has two connectors for 5 GHz antennas (left) and two connectors for 2.4 GHz antennas (right).
1.0 Introduction
1.1 Product Overview
1.2 Security Capabilities
2.0 Getting Started
2.1 Install or Upgrade Summit Software
2.2 Install the Radio
2.3 Configure the Manner of Obtaining an IP Address
2.4 Connect to Your WLAN
2.2.1 Preferred Method: Use SCU
2.4.2 Alternative: Use Windows Zero Config
2.5 Interact with the Radio
3.0 Using the Summit Client Utility
3.1 Initializing SCU
3.2 Main Window
3.3 Profile Window
3.3.1 Using Scan To Create a Profile
3.3.2 EAP Credentials
3.3.3
Encryption
3.3.4 ThirdPartyConfig
3.3.5 EAP-FAST
3.4 Status Window
3.5 Diags Window
3.6 Global Window
3.6.1 PMK Caching
4.0 Using the Summit System Tray Icon
5.0 Regulatory Domains and Channels
Appendix: FCC Information
Thank you for choosing one of the following wireless LAN (WLAN) radio modules or cards from Summit Data Communications, Inc.:
Note: SDIO radios must use V2.01.xxSD. They cannot currently use V2.02.xx.
Your Summit WLAN radio, or WLAN client adapter, enables a computing device to
communicate to a computing network using all of the IEEE 802.11 protocols listed
above for that radio.
The hardware components for all Summit radios are the
same. A 20G or 22G version is a 10G version with integrated antennas. (In fact, if you
look at the back of a CF20G, you'll see a label for the CF10G.) A PCMCIA version
is a CF version in a specially designed CF-to-PCMCIA carrier. The miniature CF version
is essentially the CF version with a different layout and a different (Molex)
connector.
This manual is a user's guide for a Summit radio that is installed on a computing device that is running one of the following operating systems:
The software that Summit provides for its radios on these operating systems includes:
For an overview of Summit WLAN radios, click the Products link on the Summit home page.
Your Summit radio is Wi-Fi CERTIFIED and certified for Version 4 of Cisco Compatible Extensions (CCX):
Summit radios typically are used in business-critical mobile devices that transmit sensitive information, such as inventory data and patient information, over the air that separates the mobile devices from the network. To protect transmitted data as well as the mobile devices and network infrastructure that transmit and receive the data, an organization's IT department often imposes on mobile devices the same strict security standards imposed on other client devices. Summit's integrated approach to security simplifies the task of enforcing a consistent security policy on all devices.
A foundational element of the IEEE 802.11i WLAN security standard is IEEE 802.1X, and a critical application on a mobile device is an 802.1X supplicant. Such a supplicant provides an interface between the radio and the operating system and supports the authentication and encryption elements required for 802.11i, also known as WPA2, as well as predecessors such as WPA and WEP. Summit software includes an integrated supplicant that supports a broad range of security capabilities, including:
The following EAP types are supported by the Summit software integrated supplicant and can be configured in SCU:
PEAP, EAP-TTLS, and EAP-TLS require the use of Windows facilities for the configuration of digital certificates.
With each of the EAP types supported by SCU, if authentication credentials are not stored in the active configuration profile, then the user is prompted to enter those credentials the first time the radio tries to associate to an AP that supports 802.1X (EAP).
Before you can use a Summit radio, you or your device manufacturer must install Summit software and the radio in your computing device. If you are doing the software and hardware installation, then you will need the following:
It is recommended that you install the software before you install the hardware. If you insert the card in your device before you install the software, then the "Found New Hardware Wizard" screen will appear, and you must select Cancel to cancel the Hardware Wizard.
Summit software for Windows Embedded CE or Windows Mobile is in a .cab file, which is the software equivalent of a "file cabinet". A Summit .cab file contains all software components, including the device driver and the Summit Client Utility (SCU). To install or upgrade Summit software, perform these tasks:
Profiles are sets of radio and security settings that are created on the SCU Profile window. Every profile has a unique name. Global settings include radio and security settings that apply to all profiles and settings that apply to SCU itself. Profiles and global settings are stored in the registry.
When you install Summit software, no profile settings or global settings are loaded in the registry. Profile settings and global settings are placed in the registry only when you use SCU, use the Summit software developer's kit (SDK), or edit the registry directly. If nothing is specified for a profile setting or a global setting, then Summit software will use a default value.
When you install or upgrade Summit software over an existing installation, you should perform a cold boot of the device to ensure that the device uses the newly installed software. The act of upgrading Summit software does not overwrite or remove profile settings and global settings in the registry, but a cold boot may clear those settings unless the registry is in non-volatile memory. The first time the driver or SCU is loaded after an upgrade, all existing profiles and global settings are validated, and invalid values are reset.
Once you have installed the Summit software, you must install the Summit radio in a CF or PCMCIA slot. Instructions on installing a Summit radio module in an internal slot (within a device) are available only to device manufacturers.
To install a 20G or 22G Series radio card, you simply insert the card in an external card slot. To install a 10G Series or 10AG Series radio module in an external slot, you must complete two types of connections:
The standard approach is to insert the module in the external slot first and then connect the antenna(s). If the antenna connectors on the radio module are not visible when the module is inserted, however, then you will need to connect the antenna(s) before inserting the module in the external slot.
To connect the antennas, take each antenna and its cable, which is fitted with a Hirose U.FL connector, and attach the antenna cable to the radio module by mating the U.FL connector on the antenna cable with a U.FL connector on the radio module. Follow the instructions below for your module:
| 10G module - There are two antenna connectors. If you have a single antenna, then connect it to the main antenna connector, which is located to the right of the auxiliary connector, and set the Rx Diversity and Tx Diversity global settings to Main Only (see Section 3.6). If you have two antennas for diversity, then connect the primary antenna to the main antenna connector and the secondary antenna to the auxiliary antenna connector, which is located to the left of the main connector. |
The SDC-CF10G module has two connectors for 2.4 GHz antennas. |
| 10AG module - There are four antenna connectors, two for the 5 GHz (802.11a) band and two for the 2.4 GHz (802.11b and 802.11g) band, with the 2.4 GHz connectors located to the right of the 5 GHz connectors. If you have a single antenna for each band, then connect it to the main antenna connector for each band, which is located to the right of the auxiliary connector, and set the Rx Diversity and Tx Diversity global settings to Main Only (see Section 3.6). If you have two antennas for each band for diversity, then in each band connect the primary antenna to the main antenna connector and the secondary antenna to the auxiliary antenna connector. |
The SDC-CF10AG module has two connectors for 5 GHz antennas (left) and two connectors for 2.4 GHz antennas (right). |
Here are the steps required to use facilities on Windows Embedded CE or Windows Mobile to configure the manner of obtaining an IP address:
You can configure DNS servers statically, but if you use DHCP for IP address assignment then DNS usually is supplied by the same server that assigns IP addresses.
Two methods exist for configuring the radio for operation on a wireless network. The first and preferred method is to use SCU, which is described in detail in the next section of this guide. The other method is to use WZC, which is the Microsoft program for configuring any WLAN card.
To use SCU to connect to your wireless network, first initialize SCU (see Section 3.1) and go to the Profile window by tapping the Profile tab. The Default configuration profile, if not modified, does not specify an SSID, an EAP type, or a method of data encryption. As a result, if the Default profile is the active profile, then the radio will associate only to an AP that broadcasts its SSID and requires no EAP type and no encryption. If no profile has been created for the WLAN to which you want to connect, then use the following steps to create and select a profile for your WLAN:
To assist with troubleshooting of any connectivity issues, the Status window reflects the current state of the device and the Diag window allows for DHCP renewal and ICMP Echo Requests, also known as Pings, to be sent by the device. You can learn more about using these SCU windows in Section 3.
Another method of configuring the radio is through the operating systems WZC feature. If the radio is inserted and the SCU is not configured, then WZC will attempt to use the card to attach to an available WLAN. A pop-up box will appear that indicates which networks (SSIDs) have been located and asks the user which network the device should use. Selecting an SSID that requires security will prompt the user for security keys or credentials. If the correct credentials are entered, then the WZC process will attempt to associate, authenticate, and run the appropriate encryption required to connect the user to the network.
You can configure radio and security settings, monitor performance and activity, and troubleshoot issues with the radio using any of the following:
The rest of this guide assumes that you are using SCU for all interactions with the radio.
The Summit Client Utility (SCU) is an application designed for end users and administrators of mobile devices that use a Summit radio. Using SCU, an end user can:
After completing an administrator login to the utility, a user can perform these additional tasks:
The SCU provides a graphical user interface (GUI) for access to all of its functions. Access to these functions also is available through an application programming interface (API) that is defined in a software developer's kit (SDK). Through the API, an application such as Wavelink Avalanche can manage Summit radios.
To initialize SCU on Windows Embedded CE or Windows Mobile, do the following:
SCU has five windows: Main, Profile, Status, Diags (or Troubleshooting), and Global. SCU displays one tab for each window. To view a window, tap its tab. Each window is described in more detail in this section.
Figure 1 below shows two examples of a Main window:
Figure 1: Main window, with and without automatic profile selection active
Here are the highlights of the Main window, beginning at the top of the window:
Admin Login/Logout button - To log in as an administrator, tap Admin Login and enter the administrator password in the dialog box. The default password is SUMMIT (case sensitive). Tap Admin Logout to log out as an administrator, leaving access to end-user functions only.
Note: The administrator password can be changed through the Admin Password function on the Global window.
Enable/Disable Radio button - When the radio is enabled, select Disable Radio to disable it; when the radio is disabled, select Enable Radio to enable it.
Active Profile - Displays the name of the active profile. Use the drop-down menu to select a different profile. If ThirdPartyConfig is selected (and after the device goes through a power cycle), WZC (Windows Zero Configuration) or another application is used to configure the SSID, Auth Type, EAP Type, and Encryption settings. See "ThirdPartyConfig" for more information.
Status - Indicates the current status of the Summit radio. Potential values include:
Down - The radio is not recognized by Summit software, possibly because the radio is not installed properly.
Disabled - The radio has been disabled because you tapped Disable Radio on the SCU Main window. To enable the radio, tap Enable Radio on the SCU Main window.
Not Associated - The radio is not associated to an AP, possibly because no AP for the active profile is in range.
Associated - The radio is associated to an AP. If the radio is not sending data to or receiving data from the AP, then:
If WEP is being used, then one of the WEP keys in the active profile is invalid.
If WPA-PSK or WPA2-PSK is being used, then the PSK or password is invalid.
If WPA-Enterprise or WPA2-Enterprise is being used, then the radio did not complete EAP authentication successfully.
<EAP type> Authenticated - The radio is associated to an AP and has completed EAP authentication successfully.
Radio Type - Indicates the device's radio type including:
Reg. Domain - Indicates the regulatory domain(s) for which the radio is configured. The domain(s) cannot be configured by an administrator or user. For more information on regulatory domains, see Section 5.0.
Auto Profile - Enables the user to activate or deactivate an automatic profile selection facility. Tap List and use the dialog box to select a created profile. When the facility is active and the Summit radio makes its first attempt to associate to an AP (after a device startup or resume), SCU tries each profile, in order, until the radio associates to an AP. That profile becomes the active profile and remains the active profile until one of the following occurs:
The device is suspended and resumed, power-cycled, or restarted, which causes the automatic profile selection facility to restart the selection process.
The user turns off the automatic profile selection facility and manually selects a different profile on the SCU Main window.
Note: The profile list should not include any profiles with an Ad Hoc Radio Mode setting.
Note: Auto Profile is not available for the MSD30AG and SSD30AG modules.
Driver - Indicates the current version of the device driver.
SCU - Indicates the SCU version currently running on the device. Displays only if space permits.
Import/Export
- Displays only if the radio is programmed to allow import/export functions
and if you are logged in as an administrator.
Tap Import/Export and use the dialog
box to do one of the following:
Note: When importing information, select Add to existing to merge new information with current registry information. Select Replace to overwrite the current registry information with the newly-imported information.
About SCU - Tap About SCU to view SCU information including driver and the SCU version.
Profile settings are radio and security settings that are stored in the registry as part of a configuration profile. When a profile is selected as the active profile on the Main window, the settings for that profile become active.
Notes: When the ThirdPartyConfig profile is selected, a power cycle must be performed. See "ThirdPartyConfig" for more information.
If the Default profile is not modified, it does not specify an SSID, an EAP type, or a data encryption method. As a result, if the Default is the active profile, then the radio associates only to an AP that broadcasts its SSID and requires no EAP type and no encryption.
From the Profile window, an administrator can:
Profile changes are not saved to the profile until you tap Commit.
Figure 2 below is an example of a Profile window:
Figure 2: Profile window
The Profile window displays the following properties and options:
Note: The device manufacturer should use the Summit Manufacturing Utility (SMU) to ensure that the transmit power value reported by SCU is EIRP, or the total effective transmit power of the radio (including gains that the antenna provides and losses from the antenna cable.
Note: If you select a specific bit rate, then the radio connects to an AP only if that AP has the specified SSID configured with the selected bit rate as the only required rate.
Note: This feature is not supported when using the SDC-MSD30AG and SDC-SSD30AG wireless LAN modules. When using the SDC-MSD30AG or SDC-SSD30AG modules, the Bit Rate option is unavailable. It defaults to Auto.
When SCU operates with a Summit 802.11g radio, an administrator can select from among the following Radio Mode values:
When SCU operates with a Summit 802.11a/g radio, an administrator can select from among the following Radio Mode values:
Note: See http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801bd035.shtml for a Cisco explanation of 802.11 authentication using Open and Network-EAP. The Summit Client Utility refers to Network-EAP as LEAP.
When the Radio Mode value is ABG rates full or BGA rates full, one band (5 GHz for ABG or 2.4 GHz for BGA) is preferred over the other. When trying to associate to an AP, the radio considers APs in the preferred band. If the radio is able to associate to one of these APs, then the radio will not try to associate to an AP in the other band. The only time that the radio attempts to associate to an AP in the non-preferred band is when the radio is not associated and cannot associate in the preferred band. When roaming, the radio considers only APs in the current band (the band in which the radio is currently associated). When an administrator tries to create or edit a profile, SCU determines which radio is operating in the device and populates the available radio mode values according to the radio type. Suppose a profile created for an 802.11a/g card is loaded on a device with an 802.11g card. If a radio mode value of A rates only, ABG rates full, or BGA rates full was set in the profile, then SCU displays a value of BG rates full. If the administrator does not save any changes to the profile, then SCU leaves the profile, including the radio mode, unchanged. If the administrator saves any changes to the profile, then SCU saves the radio mode value as BG rates full.
If the administrator selects Ad Hoc for radio mode, then the Summit radio uses ad hoc mode instead of infrastructure mode. In infrastructure mode, the radio associates to an AP. In ad hoc mode, the radio associates to another client radio that is in ad hoc mode and has the same SSID and, if configured, static WEP key.
Note: For ABGN radios, CKIP and CKIP EAP are unavailable. WEP and WEP EAP are the defaults.
When you tap Scan on the Profile window, SCU displays a list of APs that are broadcasting their SSIDs. Figure 3a below is an example of a Scan window:
Figure 3a: Scan window
Each row shows an AP's SSID, its received signal strength indication (RSSI), and whether or not data encryption is in use (true or false). You can sort the list by tapping on the column headers. If the scan finds more than one AP with the same SSID, the list displays the AP with the strongest RSSI and the least security. Every five seconds, the Scan window updates the RSSI value for each of the APs in the list. To scan for new APs and view an updated list, tap the Refresh button.
If you are authorized as an administrator in SCU, you can create a profile for any SSID in the list. To do so, double-tap the row for the SSID or tap the row and tap Configure. SCU will display a dialog box such as the one shown in Figure 3b below:
Figure 3b: Create a profile?
If you tap the Yes button on the dialog box, then SCU will create a profile for that SSID, with the profile name being the same as the SSID (or the SSID with a suffix such as "_1" if a profile with the SSID as its name exists already). If the AP is using WEP, then SCU will open a dialog box in which you can specify WEP keys. If the AP is using EAP, then SCU will open a dialog box in which you can specify login credentials for the EAP type (which SCU assumes is LEAP). After you enter information on a dialog box, you will return to the SCU Profile window, where you can view and edit profile settings. If you make any changes, then you must tap the Commit button to save them.
The 802.1X authentication types PEAP, EAP-TTLS, and EAP-TLS rely upon information in digital certificates that are created by a certificate authority, or CA. To enable a client device to validate (or authenticate) the server used for PEAP, EAP-TTLS, or EAP-TLS authentication, you must provision a root CA certificate and distribute it to that client. You can store the CA certificate in a device's Microsoft certificate store or in a directory with a path that you specify as the value for Certs Path on the SCU Global window. If you don't specify a Certs Path value, then SCU uses for the Certs Path value the path to the certs directory that is off the SCU folder. For EAP-TLS you also must generate a user certificate for each client; that user certificate must be stored in the Microsoft certificate store on the client.
Instead of using digital certificates, EAP-FAST relies upon strong shared-secret keys that are unique to users. These secrets are called protected access credentials (PACs) and can be created automatically or manually. With automatic or in-band provisioning, the PAC is created and distributed to the client device in one operation. With manual or out-of-band provisioning, the PAC is created in one step and then must be distributed to the client device separately. SCU supports PACs created automatically or manually. When you create a PAC manually, you must load it to the directory identified by the Certs Path global setting. Be sure that the PAC file does not have read-only permissions set, or SCU will not be able to use the PAC.
Here are the credentials for each EAP type:
There are no default values for credentials. If the credentials are not specified in the profile then, when the radio tries to associate using that profile, Summit software will display a dialog box that prompts the user to enter the credentials. Summit software will populate the dialog box with the username and password supplied for the previous EAP authentication. Figure 4 below shows a sample PEAP credentials dialog box:
Figure 4: PEAP credentials dialog box
Here are some other important notes on entering credentials for EAP authentication:
Alternatively, the user can select another profile as the active profile and then switch back to the profile for which EAP authentication was canceled.
If the active profile has an Encryption setting of CKIP or CKIP EAP, then the Summit radio will associate or roam successfully to an AP is configured with:
Summit radios support two special AP settings: WPA Migration Mode and WPA2 Mixed Mode. WPA Migration Mode is a setting on Cisco APs that enables both WPA and non-WPA clients to associate to an AP using the same SSID, provided that the AP is configured for Migration Mode (WPA optional with TKIP+WEP128 or TKIP+WEP40 cipher). In other words, WPA Migration Mode means WPA key management with TKIP for the pairwise cipher and TKIP, 128-bit WEP, or 40-bit WEP for the group cipher. When WPA Migration Mode in use, you can select WPA TKIP or WEP EAP for your Summit radio encryption type.
WPA2 Mixed Mode operation enables both WPA and WPA2 clients to associate to an AP using the same SSID. WPA2 Mixed Mode is defined by the Wi-Fi Alliance, and support for the feature is a part of Wi-Fi certification testing. When WPA2 Mixed Mode is configured, the AP advertises the encryption ciphers (TKIP, CCMP, other) that are available for use, and the client selects the encryption cipher it wants to use. In other words, WPA Mixed Mode means WPA key management with AES for the pairwise cipher and AES or TKIP for the group cipher. When WPA2 Mixed Mode in use, you can select WPA2 AES or WPA TKIP for your Summit radio encryption type.
If the profile named ThirdPartyConfig is selected as the active profile, then SCU works in tandem with WZC or another third-party application for configuration of all radio and security settings for the radio. The third-party application must be used to define the SSID, Auth Type, EAP Type, and Encryption settings. SCU can be used to define the Client Name, Power Save, Tx Power, Bit Rate, and Radio Mode settings. Those SCU profile settings, all SCU global settings, and the third-party application settings are applied to the radio when ThirdPartyConfig is selected as the active profile and a power cycle is performed.
On some devices that run Pocket PC or Windows Mobile, the radio will not associate if WPA with pre-shared keys, or WPA-PSK, is used with WZC. If that is the case for your device, then to use WPA-PSK you must use an SCU profile other than ThirdPartyConfig.
The 802.1X authentication types PEAP and EAP-FAST use a client-server security architecture that encrypts EAP transactions within a TLS tunnel. PEAP relies on the provisioning and distribution of a digital certificate for the authentication server. With EAP-FAST, tunnel establishment is based upon strong shared-secret keys that are unique to users. These secrets are called protected access credentials (PACs) and can be created automatically or manually. With automatic or in-band provisioning, the PAC is created and distributed to the client device in one operation. With manual or out-of-band provisioning, the PAC is created in one step and then must be distributed to the client device separately.
SCU supports PACs created automatically or manually. When you create a PAC manually, you must load it to the certs directory on the device that runs SCU. Be sure that the PAC file does not have read-only permissions set, or SCU will not be able to use the PAC.
Note: If you enter a PAC filename in the SCU field, manual provisioning is used. If you omit the PAC filename, automatic provisioning is used.
The Status window provides status information on the radio. A sample Status window is shown in Figure 5 below:
Figure 5: Status windows, infrastructure and ad hoc modes
Here is the information on the Status window:
Note: This value will be lower with a ThirdPartyConfig profile (under Windows Zero Config) than with a standard profile.
Radio association state is shown on both the Status window and the Main window. The following status items display on the Main window but not on the Status window:
When a ping initiated on the Diags window is active, the Status window displays a ping indicator consisting of two "lights" that alternative in "flashing" green (for a successful ping) or red (for an unsuccessful ping).
A sample Diags, or troubleshooting, window is shown in Figure 6 below:
Figure 6: Diags window
Here are the functions available on the Diags window:
Global settings include radio and security settings that apply to all profiles and settings that apply to SCU itself. An administrator can define and change most global settings on the Global window in SCU. A sample Global window is shown in Figure 7 below:
Figure 7: Global window
The following radio global settings, which apply to all configuration profiles, can be changed in SCU:
Note: For 30AG (MSD30AG and SSD30AG) radio modules, this parameter is disabled. The default is Optimized.
Note: For ABGN radio modules, this parameter is disabled.
Note: When switching from Standard to OPMK, you must initiate a suspend resume of the device. Only tapping Commit does not cause the change to take effect.
Note: For 30AG (MSD30AG and SSD30AG) radio modules, this parameter is disabled.
Note: For 30AG (MSD30AG and SSD30AG) radio modules, this parameter is disabled.
Note: Summit does not support the AUX antenna as a single-antenna solution.
Note: For ABGN and 30AG (MSD30AG and SSD30AG) radio modules, this parameter is disabled.
Note: Summit does not support the AUX antenna as a single-antenna solution.
Note: For 30AG (MSD30AG and SSD30AG) radio modules, this parameter is disabled.
If SCU displays a value of "Custom" for a global setting, then the operating system registry has been edited to include a value that is not available for selection on the Global window. Selecting Custom has no real effect. If SCU displays a value other than Custom and you select the value of Custom and tap Commit, then SCU reverts to the value that it displayed before you selected Custom.
The following SCU global settings, which apply to SCU and other Summit applications, can be changed in SCU:
When you change global settings and tap Commit, the changes take effect immediately. The only exception is the WMM setting; if you change it, you must do a power cycle or suspend/resume on the device to cause the change to take effect. (SCU provides you with a warning about the required power cycle.) To cause global settings changes to take effect without a power cycle, Summit software may have to reset and re-establish the WLAN connection between the Summit radio and the AP.
If you make changes without tapping Commit and attempt to move to a different SCU window, SCU will display a warning message and give you the option of saving your changes before you leave the Global window.
A few global settings can be defined or set only through a separate utility such as the Summit Manufacturing Utility, which Summit makes available only to device manufacturers and not to their customers.
PMK caching is an alternative to CCKM supported with WPA2. The goal of PMK caching is to speed up roaming between APs by accomplishing 802.1X reauthentications without communicating with the authentication server. When a client does an initial authentication to the WLAN infrastructure, both sides derive the information needed for reauthentications.
If there are no controllers, then standard PMK caching is used, and reauthentication information is cached only on the initial AP. When the client tries to reauthenticate to that AP, the client and the AP use the cached information to do the four-way handshake to exchange keys. If there are controllers, then opportunistic PMK caching is used, and reauthentication information is cached on the controllers. When the client tries to reauthenticate, the client and the controller behind the AP use the cached information to do the four-way handshake to exchange keys.
Use the PMK Caching global setting to configure the type of PMK caching supported by your infrastructure. If the Summit radio is configured for one type of PMK caching and the infrastructure supports the other type, then PMK caching will not work, and every roam will require a full 802.1X authentication that requires interaction with an authentication server.
If the active profile has an Encryption setting of WPA2 CCKM, then the Summit radio ignores the PMK Caching global setting and attempts to use CCKM.
On Windows CE or Windows Mobile, Summit software includes a service that displays an icon in the Windows System Tray. That icon provides a visual status for the Summit radio in the device and enables the user to launch SCU by tapping the icon.
The software for the service is installed with other Summit software in a .cab file. The service is active and displays an icon in the System Tray only when all of the following are true:
Once the service is active, if you remove the radio, turn off the device, make WZC active, or set the Tray Icon global setting to Off (and power cycle the device), then the service is stopped and the tray icon removed.
When the service is active, it queries the driver every three seconds for the status of the connection for the active profile, as selected in the SCU Main window. Based on the driver's response to the query, the service displays one of the following icons:
The radio is not associated/authenticated to an AP
The signal strength (RSSI) for the current AP
(to which the radio is associated) is -90 dBm or weaker, which means that a
Summit 802.11b/g radio will operate at 802.11b data rates only
The RSSI for the current AP is stronger than
-90 dBm but not stronger than -70 dBm, which means that a Summit radio will
operate at 802.11g or 802.11a data rates that are less than 54 Mbps
The RSSI for the current AP is stronger than
-70 dBm but not stronger than -50 dBm, which means that a Summit radio
should operate consistently at 54 Mbps
The RSSI for the current AP is stronger than
-50 dBmWhen you tap the icon, the SCU application is launched. On most CE devices, the System Tray icon is not visible while SCU is running, but the service remains active. If SCU usually runs on the device, or if you want to maximize performance, then you should disable the System Tray icon service by setting the Tray Icon global setting to Off and power cycling the device.
Summit radios are certified for operation in four regulatory domains:
A Summit radio can be programmed for any one of these four domains. Alternatively, a Summit radio can be programmed for a Worldwide domain, which enables the radio to be used in any domain.
A Summit radio's regulatory domain determines the radio's maximum transmit power and the frequency channels available to the radio. An 802.11g radio, which supports both 802.11b and 802.11g, operates in the 2.4 GHz frequency spectrum, where up to 14 channels, numbered 1 to 14, are defined. Adjacent channels overlap. In fact, there must be five channels of separation to avoid overlap and co-channel interference. As an example, channels 1, 6, and 11 are non-overlapping.
An 802.11a/g radio operates in both the 2.4 GHz spectrum for 802.11b and 802.11g and the 5 GHz spectrum for 802.11a. The 5 GHz frequency spectrum is grouped into sets of channels, or bands:
None of the channels in these bands overlap. Note that, for FCC countries, UNII-1 operation is allowed only indoors. The table below shows the channels that are available in each regulatory domain:
|
|
UNII-1 |
UNII-2 |
Intermediate |
UNII-3 |
|||||||||||||||||||
|
5150-5250 |
5250-5350 |
5450-5725 |
5725-5825 |
||||||||||||||||||||
|
36 |
40 |
44 |
48 |
52 |
56 |
60 |
64 |
100 |
104 |
108 |
112 |
116 |
120 |
124 |
128 |
132 |
136 |
140 |
149 |
153 |
157 |
161 |
|
|
FCC |
O |
O |
O |
O |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
O |
O |
O |
O |
|
ETSI |
O |
O |
O |
O |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
P |
- |
- |
- |
- |
|
TELEC |
O |
O |
O |
O |
P |
P |
P |
P |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
KCC |
O |
O |
O |
O |
P |
P |
P |
P |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
P |
P |
P |
P |
|
WorldWide |
O |
O |
O |
O |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
- |
P |
P |
P |
P |
P
– DFS is required.
O
– DFS is not required.
A radio programmed for the WorldWide domain may not be limited to the channels listed in the table above. The radio can use IEEE 802.11d support or a special Summit-defined mechanism to adapt itself to the channels that are available on the APs in the vicinity.
802.11d is the ratified IEEE standard for the operation of a wireless LAN client radio in multiple regulatory domains. Summit software supports a performance-optimized version of IEEE 802.11d. When a Summit radio programmed for the WorldWide domain associates to an AP that is configured for 802.11d, the radio adapt its channels and maximum transmit power to those for the country specified by the AP.
To take advantage of 802.11d support in Summit software and ensure optimal performance, make sure that every AP on your WLAN:
In addition, make sure that every Summit radio is programmed for the Worldwide regulatory domain. A radio that is programmed for a regulatory domain of FCC, ETSI, or TELEC ignores the AP's country information elements.
A Summit radio uses 802.11d only when it tries to associate on an SSID for the first time or after a disconnect. During the initial association process, if the AP provides a Country information element, then the radio configures its channel set and maximum transmit power for that country. The radio assumes that all APs with the same SSID have the same 802.11d country code; as a result, the radio effectively ignores the country code when roaming from one AP to another.
A 10-Series, 20-Series, or 22-Series Summit radio programmed for the WorldWide domain supports not only 802.11d but also a "world mode" capability. When the radio is within range of APs that are not configured for 802.11d, the radio identifies the channels that the APs support and automatically adapts its channel set to the channels supported by the APs. The world mode feature applies to all 14 channels at 2.4 GHz but only to the UNII-1 channels at 5 GHz.
FCC information is provided to device manufacturers in the appendix to the users guide for the Summit Manufacturing Utility, which is made available only to device manufacturers.
------------------------------------------------------------------------
[1] The device manufacturer should use the Summit
Manufacturing Utility (SMU) to
ensure that the Tx Power value reported by SCU is EIRP, or the total effective
transmit power of the radio, including gains that the antenna provides and
losses from the antenna cable.
[2] See http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801bd035.shtml
for a Cisco explanation of 802.11 authentication using Open and Network-EAP.
The Summit Client Utility refers to Network-EAP as LEAP.
