Radio Channel and Bandwidth

4900-4990 MHz frequency support for US and canada with license enforcement

From UIW Release 17.16.1, the Cisco Catalyst IW9167E, IW9165D, and IW9165E APs introduces additional support 4.9 GHz frequency band in URWB mode for Canada (-A) and -B (United States) domains.

When operating in the 4.9 GHz frequency bands for -A and -B domains, devices use 10 MHz and 20 MHz channel bandwidths with 5 MHz channel spacing.

The 4.9 GHz frequency bands are available on both the radio slot 1 and slot 2 and is disabled by default.


Note

The -A and -B domains do not support IEEE 802.11ax rates when operating in 4.9 GHz.
Table 1. 4.9 GHz frequency bands supported for the 10 MHz and 20 MHz channel bandwidth

Channel

Channel bandwidth (10 MHz)

Channel bandwidth (20 MHz)

11

4945

NA

19

4985

NA

20

4950

4950

21

4955

4955

22

4960

4960

23

4965

4965

24

4970

4970

25

4975

4975

26

4980

4980

Enable 4900-4990 MHz frequency bands

Use this task to enable the 4.9 GHz frequency bands on the AP.

The IW Service sends the 4.9 GHz frequency band enablement configuration to the AP.

Procedure

Step 1

Configure the 4.9 GHz frequency band enablement using IW Service Cloud-Managed or offline deployment mode.

For more information on how to configure the 4.9 GHz band enablement from IW Service, see the Introduction to Industrial Wireless.

Step 2

Use the configure dot11Radio interface 4.9G high-throughput enable command to enable 802.11an/ac rates. When enabled, the radios are allowed to operate at higher rates, limiting the power profile. 

Device# configure dot11Radio 1 4.9G high-throughput enable

Note

 

You can use the configure dot11Radio interface 4.9G high-throughput disable command to disable high-throughput. When disabled, the radio interface operates only at 802.11a rates, unlocking high-power profile.

5855-5935 MHz frequency support

The Intelligent Transport Systems (ITS) frequency band is a radio spectrum allocation that

  • spans 5875–5935 MHz and is subdivided for specific applications

  • designates 5875–5915 MHz for Road ITS applications

  • allocates 5915–5935 MHz for Urban Rail Systems, such as automatic train control systems Communications-Based Train Control (CBTC), and

  • requires license approval from the relevant national regulatory authority.

Channel allocation and power table specifications

From UIW Release 17.18.1, the Cisco Catalyst IW9167E, IW9165D, and IW9165E APs support the ITS frequency band within the European regulatory domain (-E PID).

A new power table is introduced for the -E domain. This allows for various frequencies from 5860 MHz to 5930 MHz at 10 MHz intervals.

Table 2. 10 MHz channel allocation in the 5.9 GHz band

Channel width

Frequency (MHz)

Channel number

10 MHz

5860

172

10 MHz

5870

174

10 MHz

5880

176

10 MHz

5890

178

10 MHz

5900

180

10 MHz

5910

182

10 MHz

5920

184

10 MHz

5930

186

Restrictions for wireless frequency configuration

Here are some unsupported scenarios:

  • The 5 MHz channel width option is not supported.

  • Using frequencies from 5860 MHz to 5930 MHz is allowed only for customers who have obtained local regulatory approval.

  • 5930 MHz is not supported in the IW9165E AP in 17.18.1 release.

Enabling 5855-5935 MHz frequency bands

Summary

The key components involved in enabling 5855-5935 MHz frequency bands are:

  • IW Service: Sends the 5.9 GHz frequency band enablement configuration to the access point and manages the deployment mode selection

  • Access Point (AP): Receives the configuration and initiates the frequency band activation process

  • Deployment Modes: Cloud-Managed Mode and Offline Deployment Mode provide different configuration approaches

Workflow

These stages describe the process to configure the 5.9 GHz frequency band using the IW service.

  1. Choose one of the two available deployment modes for the IW Service
    • Cloud-Managed Mode
    • Offline Deployment Mode
  2. Use the IW Service to enable the 5.9 GHz frequency band based on your selected deployment mode
  3. The IW Service transmits the 5.9 GHz enablement configuration to the target AP.

Configure operating channel and bandwidth using CLI

This task configures the operating channel and bandwidth settings for a dot11Radio interface to optimize wireless network performance.

Use this procedure when you need to set specific channel and bandwidth parameters for wireless radio interfaces in your network configuration.

Procedure

Step 1

Use the configure dot11Radio interface channel channel-id command to set the operating channel.

Example:

Device# configure dot11Radio 1 channel 172

Valid channel-id range is from 1 to 256.

Step 2

Use the configure dot11Radio interface band-width bandwidth command to set the bandwidth.

Example:

Device# configure dot11Radio 1 band-width 10

Valid bandwidth is 10 MHz.

Step 3

Use the end command to return to privileged EXEC mode.

Example:

Device# end

Validate operating channel and bandwidth using CLI

To validate radio channel and bandwidth, use the show command to display configuration parameters and verify operational status. 

Device# show dot11Radio 1 config

Interface:              enabled

Mode:                   fixed infrastructure

Frequency:              5860 MHz
Channel:                172
Channel width:          10 MHz
Antenna number:         2
TX power level:         8
TX power:               2 dBm
Antenna gain:           unselected
Maximum tx mcs:         9
High-efficiency:        disabled
Maximum tx nss:         2
RTS protection:         disabled
guard-interval:         800 ns
ampdu max length:       255
distance:               3000 m

The ampdu Tx
priority 0:             enabled
priority 1:             enabled
priority 2:             enabled
priority 3:             enabled
priority 4:             enabled
priority 5:             enabled
priority 6:             disabled
priority 7:             disabled

Enhanced Distributed Channel Access (EDCA) configuration
vo: aifs=1 cw_min=2 cw_max=3 txop=15
vi: aifs=1 cw_min=3 cw_max=4 txop=31
be: aifs=3 cw_min=4 cw_max=6 txop=31
bk: aifs=7 cw_min=3 cw_max=4 txop=0

Passphrase:             33322f268bd38d6307fb52ffec9f515fe15303ac62ed375b397716bd810d511c
AES encryption:         disabled
AES key-control:        disabled
Key rotation:           disabled
Key rotation timeout:   0(second)

DFS region:             E
DFS radar role:         auto
Radar detected:         0
Indoor deployment:      disable
Rx-SOP Threshold:       0 dBm(AUTO)
Max packet retries:     32

Configure operating channel and bandwidth using GUI

This task allows you to set the frequency range and channel width for wireless radio operations to ensure optimal network performance.

Use this procedure when you need to configure wireless radio SETTINGS for your network device. This configuration affects the radio's operating parameters and bandwidth allocation.

Procedure

Step 1

Choose GENERAL SETTINGS > wireless radio and go to Radio 1 Settings:

Step 2

From the Role drop-down list, select Fixed or Fluidity.

Step 3

From the Frequency (MHz) drop-down list, select the frequency range. See Table 1 for a list of valid frequencies.

Step 4

From the Channel Width (MHz) drop-down list, select 10 MHz.

Step 5

Click Save.

Step 6

(Optional) Choose MANAGEMENT SETTINGS > status. This page displays the status of radio channel, bandwidth configuration, and specific information of each wireless interface.

UNII-3 band with DFS support

Dynamic Frequency Selection (DFS) is a wireless communication feature that scans for radar signals in real-time, automatically adjusts the frequency on a DFS-enabled radio to avoid interference with radar systems, and ensures coexistence with radar systems, especially in the 5 GHz frequency band. DFS is a regulatory requirement for devices operating in the 5 GHz band to prevent interference with critical radar systems, such as weather or military radars.

The Unlicensed National Information Infrastructure (UNII-3) frequency band is part of the radio frequency spectrum ranging from 5725 MHz to 5825 MHz, as defined by the US Federal Communications Commission (FCC).

UNII-3 frequency band support in Great Britain

From Cisco UIW Release 17.18.1, the Cisco Catalyst IW9165D and IW9167EH APs support the UNII-3 band with DFS channels. These channels range from channel 149 (5745 MHz) to channel 165 (5825 MHz) under the country code GB in the Rest of the World (ROW) regulatory domain (-ROW PID).

Table 3. UNII-3 band support on Cisco Catalyst IW9165 and 9167 APs (Great Britain)

Cisco UIW Release

Access Points

Regulatory Domain

Country Code

Frequency Range

17.18.1

IW9165D

IW9167EH

-ROW

GB

5745 to 5825 MHz
Table 4. Supported UNII-3 band channels (Great Britain)

Channel Number

Center Frequency (MHz)

149

5745

153

5765

157

5785

161

5805

165

5825

UNII-3 frequency band support in Egypt

From Cisco UIW Release 26.1.1, the Cisco Catalyst IW9165E and IW9167E APs support the UNII-3 band in Egypt. The supported frequencies range from 5745 MHz to 5825 MHz under the ROW regulatory domain.

The available channel widths are 20, 40, and 80 MHz, except for frequency 5825 MHz, which supports only 20 MHz.


Note

To unlock Egypt's extended frequencies, you should enable the configuration file from IW Service.

For information on how to activate the license, see the Enablement of licensed frequencies section in Industrial Wireless documentation.

Table 5. UNII-3 band support on Cisco Catalyst IW9165 and 9167 APs (egypt)

Cisco UIW Release

Access Points

Regulatory Domain

Country Code

Frequency Range

26.1.1

IW9165E

IW9167E

-ROW

EG

5745 to 5825 MHz
Table 6. Supported UNII-3 band channels (Egypt)

Channel Number

20 MHz Center Frequency (MHz)

149

5745

153

5765

157

5785

161

5805

165

5825 1
1 Supports only 20 MHz.

Caution

The frequencies in the table are available only if you have an explicit authorization from the local regulatory authority to operate with higher transmit (TX) power.

UNII-3 frequency band support in Saudi Arabia

From Cisco UIW Release 26.1.1, the Cisco Catalyst IW9165E and IW9167E APs support the UNII-3 band in Saudi Arabia. The supported frequencies range from 5745 MHz to 5825 MHz under the ROW regulatory domain. The frequencies are available to all customers and do not require a license.

The available channel widths are 20, 40, and 80 MHz, except for frequency 5825 MHz, which supports only 20 MHz.

Table 7. UNII-3 band support on Cisco Catalyst IW9165 and 9167 APs (Saudi Arabia)

Cisco UIW Release

Access Points

Regulatory Domain

Country Code

Frequency Range

26.1.1

IW9165E

IW9167E

-ROW

SA

5745 to 5825 MHz
Table 8. Supported UNII-3 band channels (Saudi Arabia)

Channel Number

20 MHz Center Frequency (MHz)

149

5745

153

5765

157

5785

161

5805

165

5825 2
2 Supports only 20 MHz.

Caution

The frequencies in the table are available only if you have an explicit authorization from the local regulatory authority to operate with higher transmit (TX) power.

How DFS works

Workflow

These stages describe how the DFS process works:

  1. Radar signal scanning: DFS-enabled radios continuously monitor the operating frequency band for radar signals to ensure compliance with regulatory requirements.
  2. Radar signal detection: If a radar signal is detected, the device identifies the specific frequency being used by the radar.
  3. Frequency avoidance: The radio dynamically selects and prepares to switch to a new frequency within the allowed spectrum to avoid interference with the radar.
  4. Channel availability check: Before switching, the device performs a channel availability check to confirm that the new frequency is clear of radar signals or other interference.
  5. Seamless communication: Once the new frequency is validated, the device switches to it and resumes normal communication without disrupting network operations.

Benefits

APs operating in the UNII-3 band provide enhanced wireless connectivity and performance advantages in radar environments.

APs operating in the UNII-3 band

  • operates within the 5.8 GHz frequency range of 5745 MHz to 5825 MHz

  • helps to avoid radar interference by switching frequencies, and

  • improves wireless connectivity and performance in radar environments.

Restrictions for UNII-3 band with DFS support

These are the restriction for the UNII-3 band with DFS support.

  • Supports 10 MHz and 160 MHz channel width only.

  • Use of 5.8 GHz frequencies from 5745 MHz to 5825 MHz is permitted only for customers with local regulatory approval.

Configure DFS channel

Configure the DFS (Dynamic Frequency Selection) channel to enable wireless operation on specific regulatory frequencies.

Use this procedure to configure the DFS channel. DFS channels allow wireless devices to operate on specific frequencies while avoiding interference with radar systems.

Before you begin

Ensure that the device's regulatory domain is ROW.

Follow these steps to configure DFS channel:

Procedure

SUMMARY STEPS

  1. Use the configure countrycode country-code command to set the country code.
  2. (Optional) Use the show controllers dot11Radio radio frequency command to verify the UNII-3 band with DFS support channels.

DETAILED STEPS

Step 1

Use the configure countrycode country-code command to set the country code.

Example:

Device# configure countrycode GB

Step 2

(Optional) Use the show controllers dot11Radio radio frequency command to verify the UNII-3 band with DFS support channels.

Example:

Device# show controllers dot11Radio 1 frequency 
wifi1     Link encap:Ethernet  HWaddr 8C:84:42:92:EA:C0  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:2699 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Configured Frequency: 5745Mhz Channel: 149 20MHz (DFS enabled)
Serving Frequency: 5745Mhz Channel: 149 20MHz
Allowed Frequency: * Dynamic Frequency Selection (DFS) only
	 *5500MHz(100) *5520MHz(104) *5540MHz(108) *5560MHz(112) *5580MHz(116) *5600MHz(120) *5620MHz(124) *5640MHz(128)
	 *5660MHz(132) *5680MHz(136) *5700MHz(140) *5745MHz(149) *5765MHz(153) *5785MHz(157) *5805MHz(161) *5825MHz(165)

Configure operating channel using CLI

Configure the operating channel for wireless devices to operate in the 4.9 GHz frequency band with URWB mode support.

From UIW Release 17.15.1, the Cisco Catalyst IW9167E, IW9165D, and IW9165E AP supports 4.9 GHz frequency band in URWB mode for -Q domain (Japan). When operating at 4.9 GHz frequency band, the device supports only 20 MHz channel bandwidth.

The -Q domain supports 802.11ax rates when operating in 4.9 GHz.

Table 9. Supported channels and frequencies for the 4.9 GHz band

Channel number

Frequency (MHz)

184

4920

188

4940

192

4960

196

4980

Procedure

Step 1

Use the configure dot11Radio interface command to configure the wireless device with radio interface number.

Example:

Device# configure dot11Radio 1

The valid values are 1 and 2.

Step 2

Use the configure dot11Radio interface channel channel-id command to set the operating channel id.

Example:

Device# configure dot11Radio 1 channel 192

The valid range for the channel is 1 to 256.

Step 3

Use the end command to return to privileged EXEC mode.

Example:

Device# end

Configure channel bandwidth from CLI

This task configures the channel bandwidth for radio interfaces to optimize wireless network performance and manage spectrum usage.

Channel bandwidth configuration is performed on radio interfaces to set the appropriate bandwidth for wireless communication. Different radio interfaces support different bandwidth options depending on their capabilities.

Procedure

Step 1

Use the configure dot11Radio interface command to configure the radio interface number.

Example:

Device# configure dot11Radio 1

The valid values are 1 and 2.

Step 2

Use the configure dot11Radio interface band-width bandwidth command to set channel bandwidth.

Example:

Device# configure dot11Radio 1 band-width 20

  • Radio 1 supports 20, 40, and 80 MHz bandwidths.

  • Radio 2 supports 20, 40, 80, and 160 MHz bandwidths.

Step 3

Use the end command to return to privileged EXEC mode.

Example:

Device# end

Validate operating channel and bandwidth from CLI

To validate radio channel and bandwidth, use the show command shown in the example:

Device# show dot11Radio 1 config
Interface : enabled
Mode : fluidmax secondary
Frequency : 5180 MHz
Channel : 36
Channel width : 40 MHz
Device# show dot11Radio 2 config
Interface : enabled
Mode : fluidity
Frequency : 5785 MHz
Channel : 157
Channel width : 40 MHz

Configure radio channel and bandwidth from GUI

Configure Radio channel and bandwidth to set the operating channel ID, Radio mode as Fluidity or fixed infrastructure and set the Radio frequency range and bandwidth.

Use this configuration to optimize wireless network performance by properly setting radio parameters for your environment.

Procedure

Step 1

Configure Radio channel and bandwidth to set the operating channel ID, Radio mode as Fluidity or fixed infrastructure and set the Radio frequency range and bandwidth.

The following image shows the configuration of Radio channel and bandwidth:

The configuration interface displays the settings for radio channel and bandwidth, including the status and specific information for each wireless interface.

Step 2

Following image shows the status of Radio channel and bandwidth configuration and specific information of each wireless interface.

The image displays the status of the radio channel and bandwidth configuration, along with specific information for each wireless interface.

Configure VLAN SETTINGS

Configure VLAN SETTINGS to enable the access point to connect to VLANs within the local wireless network using specific management and native VLAN identifiers.

Default VLAN configuration parameters for the access point are:

Parameter

Default value

Management VLAN ID (MVID)

1

Native VLAN ID (NVID)

1

Procedure

Step 1

In the ADVANCED SETTINGS, click VLAN SETTINGS.

The VLAN SETTINGS window appears.

The VLAN SETTINGS window displays the configuration options for setting the Native VLAN ID and managing packet settings.

Step 2

Check the Enable VLANs checkbox to connect the access point to a VLAN that is part of the local wireless network.

Step 3

Enter the management identification number of the VLAN in the Management VLAN ID field.

For detailed info about VLAN SETTINGS and packet management, see Rules for Packet Management.

Note

 

The same Management VLAN ID must be used on all the access points that are part of the same mesh network.

Step 4

Enter the native identification number of the VLAN in the Native VLAN ID field.

Step 5

Click Save.

Rules for packet management

This topic provides the rules for packet management in traffic management scenarios, including classification parameters for incoming and outgoing data packets.

Traffic management

The incoming data packets are classified based on these parameter values:

Table 10. Access port rules management for incoming packets with an access point in smart mode

Untagged packet

If native VLAN is ON, then the packet is allowed (tagged with NVID) If native VLAN is OFF, then the packet is dropped

Tagged packet (any VID without any check)

Packet allowed with original tag
Table 11. Access port rules management for outgoing packets with an access point in smart mode

Packets from the access points (for example: IW Service interface)

Packet tagged with MVID

Signaling traffic

Packet tagged with MVID

Tagged with valid VID (1–4094), but not with NVID

Packet allowed (tagged)

Tagged with null VID (0) or NVID

Packet allowed (untagged)

Note

The packets transmitted through the Cisco VIC SFP+ interface is always tagged with a VLAN header. The interface transmits outgoing packets are classified as untagged with an IEEE 802.1p header with a VLAN ID tag of 0.

Configure Fluidity using GUI

Procedure

Step 1

In the GENERAL SETTINGS , click wireless radio .

The WIRELESS RADIO window appears.

Step 2

Choose Fluidity from the Role drop-down list.

Step 3

In the ADVACED SETTINGS , click Fluidity .

The FLUIDITY window appears.

Step 4

In the Fluidity Settings , choose a Unit Role from the drop-down list:

  • Infrastructure

  • Infrastructure (wireless relay)

  • Vehicle

Note

 

  • Vehicle ID must be unique among all the mobile devices installed on the same vehicle.

  • Devices installed on different vehicles must use different Vehicle IDs.

Step 5

Check the Automatic Vehicle ID check box to automatically set the Vehicle ID for mobile units.

The Fluidity configuration is applied. The following images illustrate the wireless interface configured in infrastructure mode and the requirement that both radios must be configured as Fluidity when the role is set to Vehicle.

The following image shows, both radios must be configured as Fluidity for role Vehicle. if one wireless interface is configured in fixed mode and the other one is configured in Fluidity mode then unit role Vehicle cannot be selected.

Configure fluidity using CLI

Configure Fluidity mode on radio interfaces to enable enhanced wireless connectivity and performance for vehicle communications.

Fluidity mode is configured on radio interfaces to support specific communication roles.

Before you begin

Follow these steps to configure fluidity using CLI:

Procedure

Step 1

Use the configure dot11Radio interface mode fluidity command to configure Fluidity mode on the desired radio interface:

Example:

configure dot11Radio 1 mode fluidity

Note

 

At least one radio interface should be in Fluidity mode.

Step 2

For Vehicle role, configure both radios in Fluidity mode:

Example:

configure dot11Radio 1 mode fluidity
configure dot11Radio 2 mode fluidity

If the desired Fluidity role is Vehicle both radios should be in Fluidity mode.

Configure fluidity role using CLI

Configure the Fluidity role to establish whether the device operates in infrastructure mode, vehicle mode, or as a wireless relay.

The Fluidity role determines how the device functions within the network topology. Infrastructure mode provides fixed network services, while vehicle modes support mobile connectivity with automatic or manual ID selection.

Procedure

Step 1

Use the configure fluidity id command to configure the Fluidity role (infrastructure or mobile).

Example:

Device# configure fluidity id

Step 2

Use the configure fluidity id [vehicle-auto | infrastructure| vehicle-id| wireless-relay] command to configure Fluidity id mode.

Example:

Device# configure fluidity id wireless-relay

Mode is one of the following values vehicle-auto - vehicle mode with automatic vehicle ID selection vehicle ID - (alphanumeric) vehicle mode with manual ID. infrastructure - infrastructure mode wireless-relay - wireless infrastructure with no ethernet connection to the backhaul

Step 3

Use the end command to return to privileged EXEC mode.

Example:

Device# end

Step 4

Use the write command to save the configuration.

Example:

Device# write

Configure fluidity coloring

Fluidity coloring enables wayside or outside devices (Fluidity infrastructure devices) to be given specific color codes to enhance or drive the handoff process. With the standard configuration handoff decision is made based on received signal strength indication (RSSI).

Typical use case: When a train is travelling on one side of the track in one direction (metro line with single tunnel for both track directions) and does not need to connect to the access point located on the opposite side of the tunnel, so mark the access point on each side with a different color to prevent occasional handovers to infrastructure devices on the opposite track.

Fluidity Coloring is introduced from UIW Release 17.12.1. The painter is a key role for wayside or outside device (Fluidity infrastructure device).

This image explains the Fluidity coloring logic and painter is a key role for wayside or outside device (Fluidity infrastructure device):

Figure 1. Fluidity coloring

The process of Fluidity coloring as follows:

  • Based on the color code, painter notifies the Fluidity vehicle device which Fluidity infrastructure devices are suitable for the handoff.

  • The Fluidity vehicle device ignores the color settings and continues to use the standard handoff mechanism (based on RSSI level) until it detects a painter.

  • Once the Fluidity vehicle device completes the handoff on a Fluidity infrastructure device with the painter configuration, it starts considering only Fluidity infrastructure devices with the same color code or other painters Fluidity infrastructure devices.

  • Multiple Fluidity infrastructure devices acting as painters are allowed.

The following table explains the Fluidity color role and its corresponding options:

Table 12. Fluidity coloring role

Fluidity Coloring Role

Options

Wayside painter (Fluidity infrastructure device)

Only one color code can be assigned to a Fluidity infrastructure device configured as a painter

Wayside standard (Fluidity infrastructure device)

A non-painter Fluidity infrastructure device can be configured with multiple color codes

Fluidity vehicle

Only one color can be assigned to Fluidity vehicle device

Procedure

Step 1

Use the configure fluidity color mode {disabled | enabled} command to configure the Fluidity color mode.

Example:


Device# configure fluidity color mode enabled

Step 2

Use the configure fluidity color value command to configure the Fluidity color value.

Example:

Device# configure fluidity color 
WORD quoted list of colors from 1 to 7 or "p X" for painter (for example: "1 2 6","4", "p 1"). "clear" to reset

Example (painter):


Device# configure fluidity color mode enabled
Device# configure fluidity color value "p 1"
Device# write
Device# reload

Example (non-painter):


Device# configure fluidity color mode enabled
Device# configure fluidity color value "3 4 5"
Device# write
Devie# reload

Example (clear):

Device# configure fluidity color value clear

Step 3

Use the show fluidity config command to verify the Fluidity color configuration.

Example (painter):


Device# show fluidity config
.
.
.
Color: enabled, current: p 1

Example (non-painter):


Device# show fluidity config
.
.
.
Color: enabled, current: 3 4 5

Example (clear):


Device# show fluidity config
.
.
.
Color: enabled, current: 0

Step 4

Use the configure fluidity color rssi-threshold threshold command to configure fluidity coloring RSSI threshold.

Example:


Device# configure fluidity color rssi-threshold
<0-96> COLOR_RSSI_THRESHOLD
Device# configure fluidity color rssi-threshold 55

The Fluidity vehicle device temporarily ignore the Fluidity coloring settings if there is a coverage hole and the current RSSI is less than the configured RSSI threshold. In this case, the Fluidity vehicle device retain it's Fluidity coloring settings and ignores them until it receives a handoff from a Fluidity infrastructure device that has the current color code. The Fluidity vehicle device resets its Fluidity coloring settings to the default value (no color) after four consecutive handoffs on a Fluidity infrastructure device with color codes differs from the present value.

Step 5

Use the show fluidity config command to verify the fluidity coloring RSSI threshold configuration.

Example:


Device# show fluidity config
.
.
.           
Color: enabled, current: 0
Color min RSSI threshold: 55