---

Cisco Catalyst Series 9105AXW and 9105AXWT Wireless Access Point Features

The C9105AXW and C9105AXWT wireless APs are wireless controller-based products and support the following features:

■Two dual-band internal antennas and one single-band internal IoT–BLE antenna in both the C9105AXW and C9105AXWT-x AP models

---

Note The ‘x’ in the model numbers represents the regulatory domain. For information on supported regulatory domains, see the AP Model Numbers and Regulatory Domains.

■Integrated antennas that are directional in azimuth, for both 2.4 GHz (peak gain 3dBi) and 5 GHz (peak gain 5dBi) bands.

■The following hardware external interfaces:

–1x100/1000/2500 Multigigabit Ethernet (RJ-45)

–3x10/100/1000 BASE-T Ethernet (RJ-45)

One of these Ethernet ports serves as a PoE-Out port. However, this PoE-Out port does not provide any power output when the AP is powered by 802.3af power.

–RS-232 console interface through RJ-45

---

Note The AP may face issues while booting if you use an unterminated console cable (not plugged into any device or terminal) or a console cable that is more than one meter in length.

–Pass-through port (RJ-45)

The C9105AXWT does not have pass-through functionality as it is connected to the WAN port on the back of the AP using the jumper cable available in the teleworker kit. For more information, see the Mounting the Kit C9105AXWT_COVER= to the AP section.

–Passive pass-through port (RJ-45)

–Mode button (enables partial or full system configuration recovery)

–USB 2.0 Port

■One multi-color LED Status indicator. see the Checking the Access Point LEDs for information on the colors of the LED status indicator.

■Simultaneous 2x2 Multiple-Input Multiple-Output (MIMO) with 2 spatial streams for both 2.4 GHz and 5 GHz bands.

■Multiuser (MU) MIMO technology with 2 spatial streams for downlink.

■MIMO equalization capabilities, which optimize uplink performance and reliability by reducing the impact of signal fade.

■Orthogonal Frequency Division Multiple Access (OFDMA)-based scheduling for both uplink and downlink.

■Spatial Reuse (also known as Basic Service Set (BSS) coloring) which allows APs and their clients to differentiate between BSSs, thus permitting more simultaneous transmissions.

■New power savings mode called Target Wake Time (TWT) which allows the client to stay asleep and wake up only at pre-scheduled (target) times to exchange data with the AP. This provides significant energy savings for battery-operated devices.

■Cisco Catalyst Center support enables Cisco Spaces, Apple FastLane and Cisco Identity Services Engine.

■Cross-AP Noise Reduction, a Cisco innovation that enables APs to intelligently collaborate in real time about RF conditions so that users connect with optimized signal quality and performance.

■Optimized AP Roaming for ensuring that client devices associate with the AP in their coverage range that offers the fastest data rate available.

■Cisco CleanAir delivers proactive, high-speed spectrum intelligence across 20-, 40-, and 80-MHz-wide channels to combat performance problems arising from wireless interference.

This AP supports both lightweight deployments (using Cisco Wireless Controllers) and Cisco Embedded Wireless Controller deployments. The AP can operate in the following modes:

■Local: This is the default mode for the Cisco AP. In this mode, the AP serves clients.
In local mode, the AP creates two CAPWAP tunnels to the Cisco WLC, one for management and the other for data traffic. This is known as central switching because the data traffic is switched (bridged) from the AP to the controller where it is then routed.

■FlexConnect: In FlexConnect mode (previously known as HREAP), the data traffic is switched locally and is not sent to the controller. In this mode, the Cisco AP behaves like an autonomous AP, but is managed by the Cisco WLC. Here, the AP continues to function even if connection to the controller is lost.

■Monitor: In the monitor mode, specified Cisco APs can exclude themselves from handling data traffic between clients and the infrastructure. These APs act as dedicated sensors for location based services (LBS), rogue AP detection, and intrusion detection (IDS).
When APs are in monitor mode, they actively monitor the airwaves and typically do not serve clients.

■Sniffer: In the wireless sniffer mode, the AP starts sniffing the air on a given channel. It captures and forwards all the packets from the clients on that channel to a remote machine that runs Airopeek or Wireshark (packet analyzers for IEEE 802.11 wireless LANs). This includes information on the time stamp, signal strength, packet size, etc.

---

Note In the sniffer mode, the server to which the data is sent should be on the same VLAN as the wireless controller management VLAN otherwise an error will be displayed.

■OEAP: This is the office extend mode for the Cisco AP.

AP Model Numbers and Regulatory Domains

Difference between the models

You need to verify whether the AP model you have is approved for use in your country. The x in the model number is a placeholder for the regulatory domain. To verify approval and to identify the regulatory domain that corresponds to a particular country, visit http://www.cisco.com/go/aironet/compliance. Not all regulatory domains have been approved. As and when they are approved, this compliance list will be updated.

Antennas and Radios

The C9105AXW and C9105AXWT AP models have two internal dual-band antennas with a dedicated 2.4 GHz radio and a 5 GHz radio, and one internal single-band antenna with a dedicated 2.4 GHz IOT radio that supports a BLE device.

The AP can be vertically mounted on a wall or on a standard junction box. Physical security is offered with the included Torx screw and the option to add a Kensington lock.

Access Point Antenna Radiation Patterns

---

Unpack and remove the access point and the accessory kit from the shipping box.

1. Return any packing material to the shipping container and save it for future use.
2. Verify that you have received the items listed below. If any item is missing or damaged, contact your Cisco representative or reseller for instructions.

– The access point

– Torx security screw and mylar label to cover the screw.

---

 

The following accessories can be ordered separately from Cisco:

■Mid-span power injector (AIR-PWRINJ6=) when PoE is not available

■For the C9105AXWT-x, the teleworker cradle kit (C9105AXWT-COVER=) which includes one back cover (with four rubber feet), one Ethernet cable, and one RJ-45 jumper cable

Face of the 9105AXW and C9105AXWT Models

1.For more information on the status LED, see Checking the Access Point LEDs.

Ports and Connectors on the 9105AXW and C9105AXWT Models

2.For more information on how to use the Mode button, see Using the Mode Button. 3.The pass-through port on the C9105AXWT functions like an mGig uplink port. This behavior is observed since the passive pass-through port is connected to the uplink port on the back of the AP through the RJ-45 jumper cable available in the teleworker kit. For more information on this behavior change in the C9105AXWT, see the Mounting the Kit C9105AXWT_COVER= to the AP section. 4.See The pass-through port on the C9105AXWT functions like an mGig uplink port. This behavior is observed since the passive pass-through port is connected to the uplink port on the back of the AP through the RJ-45 jumper cable available in the teleworker kit. For more information on this behavior change in the C9105AXWT, see the Mounting the Kit C9105AXWT_COVER= to the AP section.. 5.See The pass-through port on the C9105AXWT functions like an mGig uplink port. This behavior is observed since the passive pass-through port is connected to the uplink port on the back of the AP through the RJ-45 jumper cable available in the teleworker kit. For more information on this behavior change in the C9105AXWT, see the Mounting the Kit C9105AXWT_COVER= to the AP section.. When the AP is in RLAN mode, it supports up to four wired clients on the LAN ports.

---

---

 

■Operating temperature: 32°—122°F (0°—50°C)

---

Note When installing the AP in an environment where the ambient temperature is in the range of 104°—122°F (>40°—50°C), the access point configuration will change from 8x8 to 4x4 on the 5 GHz radios and the uplink Ethernet will downgrade to 1GbE. However, the USB port will remain enabled.

Cisco recommends that you make a site map showing access point locations so that you can record the device MAC addresses from each location and return them to the person who is planning or managing your wireless network.

---

 

---

Pre-Installation Configuration Setup

 

For pre-installation configuration, perform the following steps:

---


Make sure that the Cisco Wireless Controller DS port is connected to the network. Use the procedure for CLI or web-browser interface as described in the appropriate Cisco Wireless Controller guide.

1. Make sure that access points have Layer 3 connectivity to the Cisco Wireless Controller Management and AP-Manager Interface.
2. Configure the switch to which your access point is to attach. See the Cisco Wireless Controller Configuration Guide for the release you are using, for additional information.
3. Set the Cisco Wireless Controller as the primary so that new access points always join with it.
4. Make sure DHCP is enabled on the network. The access point must receive its IP address through DHCP.

---

Note An 802.11ax Cisco AP will be assigned an IP address from the DHCP server only if a default router (gateway) is configured on the DHCP server (enabling the AP to receive its gateway IP address) and the gateway ARP is resolved.

1. CAPWAP UDP ports must not be blocked in the network.
2. The access point must be able to find the IP address of the controller. This can be accomplished using DHCP, DNS, or IP subnet broadcast. This guide describes the DHCP method to convey the controller IP address. For other methods, refer to the product documentation. See also the Configuring DHCP Option 43 for more information.

---

Note The access point requires a gigabit Ethernet (GbE) link to prevent the Ethernet port from becoming a bottleneck for traffic because wireless traffic speeds exceed transmit speeds of a 10/100 Ethernet port.

1. Apply power to the access point. See Powering the Access Point.
2. As the access point attempts to connect to the controller, the status LED alternates between red and green. This can take up to 5 minutes.

---

Note If the access point remains in this mode for more than five minutes, it indicates that the access point is unable to find the primary Cisco Wireless Controller. Check the connection between the access point and the Cisco Wireless Controller and be sure that they are on the same subnet.

1. If the access point shuts down, check the power source.
2. After the access point finds the Cisco Wireless Controller, it attempts to download the new operating system code if the access point code version differs from the Cisco Wireless Controller code version. While this is happening, the Status LED blinks blue.
3. If the operating system download is successful, the access point reboots.
4. Configure the access point if required. Use the controller CLI, controller GUI, or Cisco Prime Infrastructure to customize the access-point-specific 802.11ax network settings.
5. If the pre-installation configuration is successful, the Status LED is green indicating normal operation. Disconnect the access point and mount it at the location at which you intend to deploy it on the wireless network.
6. If your AP does not indicate normal operation, turn it off and repeat the pre-installation configuration.

When you are installing a Layer 3 access point on a different subnet than the Cisco Wireless Controller, be sure that a DHCP server is reachable from the subnet on which you will be installing the access point, and that the subnet has a route back to the Cisco Wireless Controller. Also be sure that the route back to the Cisco Wireless Controller has destination UDP ports 5246 and 5247 open for CAPWAP communications. Ensure that the route back to the primary, secondary, and tertiary controller allows IP packet fragments. Finally, be sure that if address translation is used, that the access point and the Cisco Wireless Controller have a static 1-to-1 NAT to an outside address. (Port Address Translation is not supported.)

---

 

Type of Mounting	Mounting Bracket and Kit
Mounting the AP directly on a Wall	AIR-AP-BRACKET-W46 7
Mounting the AP on an Electrical Junction Box
Mounting the AP on a Wall using the Spacer	AIR-AP-BRACKET-W4 6 C9105AXW-KIT spacer kit.
Mounting the AP on an Electrical Junction Box using the Spacer

Mounting the AP directly on a Wall

To mount the AP on a wall, follow these steps:

---


Fasten the wall-mount bracket (AIR-AP-BRACKET-W4) to the wall, using two M3.5X32mm screws. Ensure that the side having the Mount Arrows Up label is facing outwards, and the bracket is oriented vertically as indicated by the arrows.

1. Connect the power and network cables to the AP.

If you are unable to connect a PoE cable to the port on the back of the AP, then:

1. On the back of the AP, use an RJ45 jumper cable to connect the PoE port to the Pass-Through port. This jumper cable is available as part of the spacer kit (C9105AXW-KIT=).
2. Connect the PoE supply cable to the Pass-Through port on the base of the AP.

This connection sends power internally from the Pass-Through port on the base, to the Pass-Through port on the back, and then though the jumper cable into the PoE port on the back.

1. Mount the AP onto the wall-mount bracket. For this, align the AP with the bracket and then offset the AP around ¼ inch above the bracket.
2. Fasten the AP to the bracket using the M2 x 5.5mm Torx security screw. Cover it with the mylar label.

Mounting the AP on an Electrical Junction Box

To mount the AP on an electrical junction box, follow these steps:

---


Fasten the wall-mount bracket (AIR-AP-BRACKET-W4), using two #6-32 x 0.81 inch machine screws, to the electrical junction box. Ensure that the side having the Mount Arrows Up label is facing outwards, and the bracket is oriented vertically as indicated by the arrows.

1. Connect the power and network cables to the AP.

If you are unable to connect a PoE cable to the port on the back of the AP, then:

1. On the back of the AP, use an RJ45 jumper cable to connect the PoE port to the Pass-Through port. This jumper cable is available as part of the spacer kit (C9105AXW-KIT=).
2. Connect the PoE supply cable to the Pass-Through port on the base of the AP.

This connection sends power internally from the Pass-Through port on the base, to the Pass-Through port on the back, and then though the jumper cable into the PoE port on the back.

1. Mount the AP onto the wall-mount bracket. For this, align the AP with the bracket and then offset the AP around ¼ inch above the bracket.
2. Fasten the AP to the bracket using the M2 x 5.5mm Torx security screw. Cover it with the mylar label.

Mounting the AP on a Wall using the Spacer

Mounting the AP on an Electrical Junction Box using the Spacer

The spacer kit helps mount the AP on an electrical junction box. This spacer avoids exposing Ethernet cable to the elements. The the pass-through Ethernet port is used to connect the Ethernet cable to the AP.

Mounting the Kit C9105AXWT_COVER= to the AP

---

The Controller Discovery Process

The controller must be running release 8.10.105.0 or IOS-XE 17.3.x to support C9105AXW models. For more information, visit the access point data sheet available on Cisco.com at https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9100ax-access-points/datasheet-c78-744062.html.

• You cannot edit or query any access point using the controller CLI if the name of the access point contains a space.
• Make sure that the controller is set to the current time. If the controller is set to a time that has already occurred, the access point might not join the controller because its certificate may not be valid for that time.

Deploying the Access Point on the Wireless Network

After you have mounted the access point, follow these steps to deploy it on the wireless network:

---


Connect and power up the access point.

1. Observe the access point LED (for LED descriptions, see Checking the Access Point LEDs).
2. When you power up the access point, it begins a power-up sequence that you can verify by observing the access point LED. If the power-up sequence is successful, the discovery and join process begins. During this process, the LED blinks sequentially green, red, and off. When the access point has joined a controller, the LED is green if no clients are associated or blue if one or more clients are associated.
3. If the LED is not on, the access point is most likely not receiving power.
4. If the LED blinks sequentially for more than 5 minutes, the access point is unable to find its primary, secondary, and tertiary Cisco Wireless Controller. Check the connection between the access point and the Cisco Wireless Controller, and be sure the access point and the Cisco Wireless Controller are either on the same subnet or that the access point has a route back to its primary, secondary, and tertiary Cisco Wireless Controller. Also, if the access point is not on the same subnet as the Cisco Wireless Controller, be sure that there is a properly configured DHCP server on the same subnet as the access point. See the Configuring DHCP Option 43 for additional information.
5. Reconfigure the Cisco Wireless Controller so that it is not the primary controller.

A primary Cisco Wireless Controller should be used only for configuring access points and not in a working network.

---

LED Status Indications

Message Type	LED State	Message Meaning
Association status	Green	Normal operating condition, but no wireless client associated
	Blue	Normal operating condition, at least one wireless client association
Boot loader status	Green	Executing boot loader
Boot loader error	Blinking Green	Boot loader signing verification failure
Operating status	Blinking Blue	Software upgrade in progress
	Alternating between Green and Red	Discovery/join process in progress
Access point operating system errors	Cycling through Red-Off-Green-Off-Blue-Off	General warning; insufficient inline power

Using the Mode Button

Using the Mode button (see Ports and Connectors on the 9105AXW and C9105AXWT Models) you can:

■Reset the AP to the default factory-shipped configuration.

■Clear the AP internal storage, including all configuration files.

To use the mode button, press, and keep pressed, the mode button on the access point during the AP boot cycle. Wait until the AP console shows a seconds counter. Once the counter indicates the number of seconds the mode button is pressed, the AP status LED changes to blinking red. Then:

■To reset the AP to the default factory-shipped configuration, keep the mode button pressed for less than 20 seconds. The AP configuration files are cleared.

This resets all configuration settings to factory defaults, including passwords, the IP address, and the SSID.

■To clear the AP internal storage, including all configuration files, keep the mode button pressed for more than 20 seconds, but less than 60 seconds.

---

Note If the mode button is pressed for more than 30 seconds but less than 60 seconds, the FIPS mode flag is also cleared during the full factory reset of the AP. The FIPS flag when set disables console access.

The AP status LED changes from Blue to Red, and all the files in the AP storage directory are cleared.

If you keep the mode button pressed for more than 60 seconds, the mode button is assumed faulty and no changes are made.

Troubleshooting the Access Point to Cisco Controller Join Process

---

Note As specified in the Cisco Wireless Solutions Software Compatibility Matrix, ensure that your controller is running controller software release 8.10.105.0 or IOS-XE 17.3.x or later to support C9105AXW.

Access points can fail to join a controller for many reasons: a RADIUS authorization is pending; self-signed certificates are not enabled on the controller; the access point and the controller regulatory domains don’t match, and so on.

Controller software enables you to configure the access points to send all CAPWAP-related errors to a syslog server. You do not need to enable any debug commands on the controller because all of the CAPWAP error messages can be viewed from the syslog server itself.

The state of the access point is not maintained on the controller until it receives a CAPWAP join request from the access point. Therefore, it can be difficult to determine why the CAPWAP discovery request from a certain access point was rejected. In order to troubleshoot such joining problems without enabling CAPWAP debug commands on the controller, the controller collects information for all access points that send a discovery message to it and maintains information for any access points that have successfully joined it.

The controller collects all join-related information for each access point that sends a CAPWAP discovery request to the controller. Collection begins with the first discovery message received from the access point and ends with the last configuration payload sent from the controller to the access point.

When the controller is maintaining join-related information for the maximum number of access points, it does not collect information for any more access points.

An access point sends all syslog messages to IP address 255.255.255.255 by default.

You can also configure a DHCP server to return a syslog server IP address to the access point using option 7 on the server. The access point then starts sending all syslog messages to this IP address.

When the access point joins a controller for the first time, the controller sends the global syslog server IP address (the default is 255.255.255.255) to the access point. After that, the access point sends all syslog messages to this IP address until it is overridden by one of the following scenarios:

■The access point is still connected to the same controller, and the global syslog server IP address configuration on the controller has been changed using the config ap syslog host global syslog_server_IP_address command. In this case, the controller sends the new global syslog server IP address to the access point.

■The access point is still connected to the same controller, and a specific syslog server IP address has been configured for the access point on the controller using the config ap syslog host specific Cisco_AP syslog_server_IP_address command. In this case, the controller sends the new specific syslog server IP address to the access point.

■The access point is disconnected from the controller and joins another controller. In this case, the new controller sends its global syslog server IP address to the access point.

■Whenever a new syslog server IP address overrides the existing syslog server IP address, the old address is erased from persistent storage, and the new address is stored in its place. The access point also starts sending all syslog messages to the new IP address provided the access point can reach the syslog server IP address.

You can configure the syslog server for access points and view the access point join information from the controller CLI.

Important Information for Controller-based Deployments

Keep these guidelines in mind when you use C9105AXW series access point:

■The access point can only communicate with Cisco wireless controllers.

■The access point does not support Wireless Domain Services (WDS) and cannot communicate with WDS devices. However, the controller provides functionality equivalent to WDS when the access point joins it.

■CAPWAP does not support Layer 2. The access point must get an IP address and discover the controller using Layer 3, DHCP, DNS, or IP subnet broadcast.

■The access point console port is enabled for monitoring and debug purposes. All configuration commands are disabled when the access point is connected to a controller.

Configuring DHCP Option 43

You can use DHCP Option 43 to provide a list of controller IP addresses to the access points, enabling them to find and join a controller.

The following is a DHCP Option 43 configuration example on a Windows 2003 Enterprise DHCP server for use with Cisco Catalyst lightweight access points. For other DHCP server implementations, consult product documentation for configuring DHCP Option 43. In Option 43, you should use the IP address of the controller management interface.

---

Note DHCP Option 43 is limited to one access point type per DHCP pool. You must configure a separate DHCP pool for each access point type.

The C9105AXW series access point uses the type-length-value (TLV) format for DHCP Option 43. DHCP servers must be programmed to return the option based on the access point DHCP Vendor Class Identifier (VCI) string (DHCP Option 43). The VCI string for the C9105AXW series access point is:

Cisco AP C9105AXW

The format of the TLV block is listed below:

■Type—0xf1 (decimal 241)

■Length—Number of controller IP addresses * 4

■Value—IP addresses of the WLC management interfaces listed sequentially in hex

To configure DHCP Option 43 in the embedded Cisco IOS DHCP server, follow these steps:

---


Enter configuration mode at the Cisco IOS CLI.

1. Create the DHCP pool, including the necessary parameters such as default router and name server. A DHCP scope example is as follows:

ip dhcp pool <pool name>

network <IP Network> <Netmask>

default-router <Default router>

dns-server <DNS Server>

Where:

<pool name> is the name of the DHCP pool, such as AP9105AXW

<IP Network> is the network IP address where the controller resides, such as 10.0.15.1

<Netmask> is the subnet mask, such as 255.255.255.0

<Default router> is the IP address of the default router, such as 10.0.0.1

<DNS Server> is the IP address of the DNS server, such as 10.0.10.2

1. Add the option 43 line using the following syntax:

option 43 hex <hex string>

The hex string is assembled by concatenating the TLV values shown below:

Type + Length + Value

For example, suppose that there are two controllers with management interface IP addresses, 10.126.126.2 and 10.127.127.2. The type is f1(hex). The length is 2 * 4 = 8 = 08 (hex). The IP addresses translate to 0a7e7e02 and 0a7f7f02. Assembling the string then yields f1080a7e7e020a7f7f02. The resulting Cisco IOS command added to the DHCP scope is option 43 hex f1080a7e7e020a7f7f02.

What is 802.11ax?

The IEEE 802.11ax standard, also known as the High-Efficiency Wireless (HEW) or Wi-Fi 6, builds off of the 802.11ac and delivers a better experience in typical environments, and a more predictable performance for advanced applications such as 4K or 8K video, high-density high-definition collaboration applications, all-wireless offices and Internet-of-Things (IoT). 802.11ax is designed to use both 2.4Ghz and the 5GHz bands, unlike prior standards.

 

What is Cisco Multigigabit Ethernet?

Cisco Multigigabit Ethernet (mGig) is a unique Cisco innovation also available in the Cisco Catalyst 9105AXW series access point. With the increasing popularity of 802.11ax and new wireless applications, wireless devices now require more network bandwidth. Hence, there is a need for a technology that supports speeds higher than 1 Gbps on all cabling infrastructure. Cisco Multigigabit technology allows you to achieve bandwidth speeds from 1 to 10 Gbps over traditional Cat 5e cabling or newer. The C9105AXW AP supports up to 2.5 Gbps using mGig.

For more information see the following Cisco Multigigabit FAQ document:
http://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise-networks/catalyst-multigigabit-switching/multigigabit-ethernet-technology.pdf

Manufacturers Federal Communication Commission Declaration of Conformity Statement

 

 

Manufacturer:

Cisco Systems, Inc.
125 West Tasman Drive
San Jose, CA 95134-1706
USA

This device complies with Part 15 rules. Operation is subject to the following two conditions:

1. This device may not cause harmful interference, and

2. This device must accept any interference received, including interference that may cause undesired operation.

This equipment has been tested and found to comply with the limits of a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a residential environment. This equipment generates, uses, and radiates radio frequency energy, and if not installed and used in accordance with the instructions, may cause harmful interference. However, there is no guarantee that interference will not occur. If this equipment does cause interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to correct the interference by one of the following measures:

■Reorient or relocate the receiving antenna.

■Increase separation between the equipment and receiver.

■Connect the equipment to an outlet on a circuit different from which the receiver is connected.

■Consult the dealer or an experienced radio/TV technician.

The Part 15 radio device operates on a non-interference basis with other devices operating at this frequency when using the integrated antennas. Any changes or modification to the product not expressly approved by Cisco could void the user’s authority to operate this device.

VCCI Statement for Japan

 

	This is a Class B product based on the standard of the Voluntary Control Council for Interference from Information Technology Equipment (VCCI). If this is used near a radio or television receiver in a domestic environment, it may cause radio interference. Install and use the equipment according to the instruction manual.

Guidelines for Operating Cisco Catalyst Access Points in Japan

This section provides guidelines for avoiding interference when operating Cisco Catalyst access points in Japan. These guidelines are provided in both Japanese and English.

Statement 371—Power Cable and AC Adapter

 

 

Industry Canada

Canadian Compliance Statement

This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.

Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication.
Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas l'intensité nécessaire à l'établissement d'une communication satisfaisante.

This radio transmitter has been approved by Industry Canada to operate with the antenna types listed below with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device.
Le présent émetteur radio a été approuvé par Industrie Canada pour fonctionner avec les types d'antenne énumérés ci-dessous et ayant un gain admissible maximal et l'impédance requise pour chaque type d'antenne. Les types d'antenne non inclus dans cette liste, ou dont le gain est supérieur au gain maximal indiqué, sont strictement interdits pour l'exploitation de l'émetteur.

 

Operation in the band 5150-5250 MHz is only for indoor use to reduce the potential for harmful interference to co-channel mobile satellite systems.
La bande 5 150-5 250 MHz est réservés uniquement pour une utilisation à l'intérieur afin de réduire les risques de brouillage préjudiciable aux systèmes de satellites mobiles utilisant les mêmes canaux.

Users are advised that high-power radars are allocated as primary users (i.e. priority users) of the bands 5250-5350 MHz and 5650-5850 MHz and that these radars could cause interference and/or damage to LE-LAN devices.
Les utilisateurs êtes avisés que les utilisateurs de radars de haute puissance sont désignés utilisateurs principaux (c.-à-d., qu'ils ont la priorité) pour les bandes 5 250-5 350 MHz et 5 650-5 850 MHz et que ces radars pourraient causer du brouillage et/ou des dommages aux dispositifs LAN-EL.

European Community, Switzerland, Norway, Iceland, and Liechtenstein

Access Point Models:

C9105AXW-E
C9105AXW-EWC-E
C9105AXWT-E

---

Note This equipment is intended to be used in all EU and EFTA countries. Outdoor use may be restricted to certain frequencies and/or may require a license for operation. For more details, contact Cisco Corporate Compliance.

The product carries the CE Mark:

 

 

Declaration of Conformity for RF Exposure

This section contains information on compliance with guidelines related to RF exposure.

Administrative Rules for Cisco Catalyst Access Points in Taiwan

This section provides administrative rules for operating Cisco Catalyst access points in Taiwan. The rules for all access points are provided in both Chinese and English.

Operation of Cisco Catalyst Access Points in Brazil

This section contains special information for operation of Cisco Catalyst access points in Brazil.

 

Declaration of Conformity Statements

All the Declaration of Conformity statements related to this product can be found at the following location: http://www.ciscofax.com