FCC Safety Compliance Statement Modifying the equipment without Cisco’s authorization may result in the equipment no longer complying with FCC requirements for Class A digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense. This equipment has been tested and found to comply with the limits for a Class A 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 commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.

Operation of this equipment in a residential area is likely to cause harmful interference in which case users will be required to correct the interference at their own expense. Try to correct the interference by one or more of the following measures: • Verify that the ambient temperature remains between 32 to 104° F (0 to 40° C), taking into account the elevated temperatures when installed in a rack or enclosed space. • When multiple Cisco 5508 Wireless Controllers are mounted in an equipment rack, be sure that the power source is sufficiently rated to safely run all the equipment in the rack. • Verify the integrity of the electrical ground before installing the controller. Controller Overview The Cisco 5508 Wireless Controller, designed for 802.11n performance and maximum scalability, supports up to 500 lightweight access points and 7000 clients, making it ideal for large-sized enterprises and high-density applications.

A core component of the Cisco unified wireless solution, these controllers deliver wireless security, intrusion detection, radio management, quality of service (QoS), and mobility across an entire enterprise. The controllers work in conjunction with other controllers, Cisco Wireless Control System (WCS), and access points to provide network managers with a robust wireless LAN solution. The Cisco 5508 Wireless Controller supports the OfficeExtend access point, which provides secure communications from a controller to an access point at a remote location, seamlessly extending the corporate WLAN over the Internet to an employee’s residence. In order to best use this guide, you should have already designed the wireless topology of your network. Because the radio resource management (RRM) feature automatically detects and configures access points as they appear on the network, it is not necessary to have any access points on the network in order to install and configure a controller.

Shows the front panel of the Cisco 5508 Wireless Controller. Figure 1 Front Panel.

Console Port Connections The controller has both EIA/TIA-232 asynchronous (RJ-45) and USB 5-pin mini Type B, 2.0 compliant serial console ports. The default parameters for the console ports are 9600 baud, 8 data bits, 1 stop bit, and no parity. The console ports do not support hardware flow control. EIA/TIA-232 Depending on the cable and the adapter used, this port appears as a DTE or DCE device at the end of the cable. Only one port can be used at a time. USB Console The USB console port connects directly to the USB connector of a PC using a USB Type A to 5-pin mini Type B cable. For operation with Microsoft Windows, the Cisco Windows USB Console Driver must be installed on any PC connected to the console port.

If it is not installed, prompts guide you through a simple installation process. Description RP/SP port Off: Not present. Green: Indicates RP/SP port is active and link is established.

Amber: Present with failure. USB0/USB1 port Off: Not present.

Green: Present and enabled. Amber: Present with failure. Console port (RJ-45) Green: Indicates active console port. When this LED is on, the USB console port LED is off. Console port (mini-USB Type B) Green: Indicates active aux port. When this LED is on, the RJ-45 console port LED is off. Distribution ports 1-8 Off: Not present.

Get expert recommendations for deploying a high density wireless LAN network in this Cisco design guide. Get support for the NETGEAR WNA3100 (N300) wireless USB adapter including documentation and software version downloads.

Green: Indicates SFP port is active and link is established. Amber: Present with failure. Power supplies (PS1 and PS2) Continuous green: Indicates that the power supply is operational. Blinks green: Indicates that a power supply is installed but does not have AC power.

Note Verify that the power cord in installed correctly and that the power switch is on. Blinks amber: Indicates that the standby power supply fan is not spinning or that the power supply is over temperature. Continuous amber: Indicates that the power supply is in failure condition. Note When the PS1 or PS2 LED is amber, the power supply shuts down. System (SYS) During system power-up: • SYS blinks amber. • ALM is continuous amber.

During system boot: • SYS blinks green. • ALM is continuous amber. After bootup: • SYS is continuous green.

• ALM is off. During controller image upgrade: • SYS is continuous green. • ALM blinks green. System crash: • SYS is continuous amber.

• ALM is off. Firmware Error: • SYS is continuous amber. • ALM is continuous amber. Note Power cycle the controller to clear the firmware error. Internal Voltage Error: • SYS blinks amber. • ALM is continuous amber. Temperature Error: • SYS is off.

• ALM blinks amber. Note Check for blocked air vents and fans on the controller, and make sure that ambient room temperature is below 104° F (40° C). Required Tools and Information You will need the following equipment in order to install the controller: • Wireless LAN controller hardware – Controller with factory-supplied power cord and mounting hardware – Network, operating system service network, and access point cables as required • Command-line interface (CLI) console – VT-100 terminal emulator on CLI console (PC, laptop, or palmtop) – Null modem serial cable to connect CLI console and controller • Local TFTP server (required for downloading operating system software updates).

Cisco uses an integral TFTP server. This means that third-party TFTP servers cannot run on the same workstation as the Cisco WCS because Cisco WCS and third-party TFTP servers use the same communication port. • A management interface netmask address. • A management interface default router IP address.

• A VLAN identifier if the management interface is assigned to a VLAN, or 0 for an untagged VLAN. • Distribution system physical port number—1 through 8 for front panel Gigabit Ethernet ports. • IP address of the default DHCP server that will supply IP addresses to clients. • The Control And Provisioning of Wireless Access Points Protocol (CAPWAP) transport mode (Layer 3). • A virtual gateway IP address (a fictitious, unassigned IP address, such as 1.1.1.1, used by all Cisco wireless LAN controller Layer 3 security and mobility managers). • A Cisco wireless LAN controller mobility group name, if required.

• An 802.11 network name (SSID) for WLAN 1. This is the default SSID that the access points use when they join with the controller. • Whether or not to allow static IP addresses from clients. – Yes is more convenient, but has lower security (session can be hijacked). – No is less convenient, but has higher security and works well for Windows XP devices. • RADIUS server IP address, communications port, and secret (if you are configuring a RADIUS server).

• The country code for this installation. Refer to the Cisco Wireless LAN Controller Configuration Guide for country code information. This guide is available at cisco.com. • Status of the 802.11a, 802.11b, 802.11g, and 802.11n networks (enabled or disabled).

• Status of radio resource management (RRM) (enabled or disabled). • Make sure you can reach the controller and all cables attached to it. • Make sure that water or excessive moisture cannot get into the controller. • Make sure that the controller is within 328 ft. (100 m) of equipment connected to a 1000BASE-T port. • Make sure that the controller is within one of the following distances of equipment connected to the optional 1000BASE-SX or -LX port: – 722 ft (220 m) when using 160 MHz-km rated 62.5/125 um multimode fiber. – 902 ft (275 m) when using 200 MHz-km rated 62.5/125 um multimode fiber.

– 1312 ft (400 m) when using 400 MHz-km rated 50/125 um multimode fiber. – 1641 ft (500 m) when using 500 MHz-km rated 50/125 um multimode fiber. Installing the Chassis The controller ships with rack mounting brackets and the desktop or shelf mounting rubber feet in a separate bag. An adjustable rack-mount kit is included for mounting the controller in a standard 19-inch (48.3 cm) equipment rack. A standard equipment rack has two unobstructed outer posts, a minimum depth between the front and rear mounting posts of 13 inches (33 cm), and a maximum depth of 32 inches (81.3 cm). You can also install the controller in a 2-post equipment rack.

This kit is not suitable for racks with obstructions (such as a power strip) that could impair access to system components. Shows the contents of the mounting kit. Figure 3 Mounting Kit.

To attach the grounding lug and cable to the chassis, follow these steps: Step 1 Use a wire-stripping tool to remove approximately 0.75 inch (19 mm) of the covering from the end of the grounding cable. Step 2 Insert the stripped end of grounding cable into the open end of the grounding lug. Step 3 Use the crimping tool to secure the grounding cable in the grounding lug. Step 4 Remove the adhesive label from either the right or left grounding pad on the chassis.

Step 5 Place the grounding lug against the grounding pad so that there is solid metal-to-metal contact, and insert the two M4 screws with washers through the holes in the grounding lug and into the grounding pad. Step 6 Ensure that the lug and cable do not interfere with other equipment. Step 7 Prepare the other end of the grounding cable and connect it to an appropriate grounding point in your site to ensure adequate earth ground. Follow these steps to connect the PC to the controller’s console port: Step 1 If you use the RJ-45 console port, plug the RJ-45 connector on a null-modem serial cable into the controller’s RJ-45 console port and the other end of the cable into the PC’s serial port. If you use the USB console port, plug the 5-pin mini Type B connector into the controller’s USB console port and the other end of the cable into the PC’s USB Type A port. Step 2 Start the PC’s terminal emulation program.

Step 3 Configure the terminal emulation program for the following parameters: • 9600 baud • 8 data bits • No flow control • 1 stop bit • No parity. Running the Bootup Script and Power-On Self Test When you plug the controller into an AC power source, the bootup script initializes the system, verifies the hardware configuration, loads its microcode into memory, verifies its operating system software load, and initializes itself with its stored configurations. Before performing this test, you should connect your PC to the controller’s CLI console as described in the. Free Download Race 2 Mashup Song Mp3 here. Follow these steps to run the bootup script and conduct the power-on self test (POST).

Step 1 Plug an AC power cord into the back of the controller and connect the other end to a grounded 100 to 240 VAC, 50/60 Hz electrical outlet. Step 2 Turn on the power supply. Step 3 Observe the bootup on the CLI screen.

The bootup script displays operating system software initialization (code download and POST verification) and basic configuration as shown in the following sample bootup display. Step 2 Enter the system name, which is the name you want to assign to the controller. You can enter up to 32 ASCII characters. Step 3 Enter the administrative username and password to be assigned to this controller. You can enter up to 24 ASCII characters for each.

The default administrative username and password are admin and admin, respectively. Step 4 If you want the controller’s service-port interface to obtain an IP address from a DHCP server, enter DHCP. If you do not want to use the service port or if you want to assign a static IP address to the service-port interface, enter none.

The service port works with auto-negotiation and in full duplex mode only. The other device such as switch and access point that communicates with the controller must be set to full duplex and auto-negotiation mode. You can use the command show interface detailed service-port to check all the service port interface parameters on the controller. Step 5 If you entered none in, enter the IP address and netmask for the service-port interface on the next two lines. Step 6 Enable or disable link aggregation (LAG) by choosing yes or no. Step 7 Enter the IP address, netmask, default router IP address, and optional VLAN identifier (a valid VLAN identifier or 0 for an untagged VLAN) for the management interface. Step 11 Enter the network name, or service set identifier (SSID).

The initial SSID enables basic functionality of the controller and allows access points that have joined the controller to enable their radios. Step 12 Enter yes to allow clients to assign their own IP address or no to make clients request an IP address from a DHCP server. Step 13 To configure a RADIUS server now, enter yes and then enter the IP address, communication port, and secret key of the RADIUS server. Otherwise, enter no.

Step 14 Enter the code for the country in which the controller will be used. Step 17 If you want the controller to receive its time setting from an external Network Time Protocol (NTP) server when it powers up, enter yes to configure an NTP server.

Otherwise, enter no. Step 18 If you entered no in the previous step and want to manually configure the system time on your controller now, enter yes.

If you do not want to configure the sy stem time now, enter no. Step 19 If you entered yes in the previous step, enter the current date in MM/DD/YY format and the current time in HH:MM:SS format.

Step 20 When prompted to verify that the configuration is correct, enter yes or no. The controller saves your configuration, reboots, and prompts you to log in.

Connecting the Network (Distribution System) Up to eight of the following SFP modules can be installed in any combination: • GLC-SX-MM (1000BASE-SX) SFP modules that provide a 1000 Mb/s wired connection to a network through an 850nM (SX) fiber-optic link using an LC physical connector. • GLC-LH-SM (1000BASE-LX) SFP modules that provide a 1000 Mb/s wired connection to a network through a 1300nM (LX/LH) fiber-optic link using an LC physical connector. • GLC-T (1000BASE-T) SFP modules that provide a 1000 Mb/s wired connection to a network through a copper link using an RJ-45 physical connector. Depending on the distribution system physical port to be assigned, use Ethernet Category 5 or higher cables or SX/LX/LH compatible fiber-optic cables to connect the network equipment to the controller. Connecting the Switch’s Service Port (Optional) The service port is controlled by the service-port interface and is reserved for out-of-band management of the controller and system recovery and maintenance in the event of a network failure.

The service-port interface enables the controller to be managed on an interface different from the one used for your network traffic. Use of the service port is optional.

You can perform out-of-band controller management from a PC running a terminal emulation program or a PC running Cisco WCS, a network management tool that enables you to configure and monitor a network of controllers, or the controller GUI. However, you must first connect the PC to the switch’s service port in one of two ways: • Use an Ethernet cross-over cable to connect the PC directly to the switch’s service port. • For a remote connection (using Telnet or SSH) through a dedicated management network, use a Category 5, Category 5e, Category 6, or Category 7 Ethernet cable to connect the management network to the switch’s service port and the appropriate cable to connect the PC to the management network. Connecting Access Points After you have configured the controller, use Category-5, Category-5e, Category-6, or Category-7 Ethernet cables to connect Cisco lightweight access points to the network. As soon as the controller is operational, it starts to scan for access points. When it detects an access point, it records the access-point MAC address in its database. The controller radio resource management (RRM) feature then automatically configures the access point to start sending and allowing clients to associate.

Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation: Subscribe to the What’s New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0. Cisco 90-Day Limited Hardware Warranty Terms There are special terms applicable to your hardware warranty and various services that you can use during the warranty period. Your formal Warranty Statement, including the warranties and license agreements applicable to Cisco software, is available on Cisco.com. Follow these steps to access and download the Cisco Information Packet and your warranty and license agreements from Cisco.com. Launch your browser, and go to this URL: The Warranties and License Agreements page appears.

To read the Cisco Information Packet, follow these steps: a. Click the Information Packet Number field, and make sure that the part number 78-5235-03B0 is highlighted.

Select the language in which you would like to read the document. The Cisco Limited Warranty and Software License page from the Information Packet appears. Read the document online, or click the PDF icon to download and print the document in Adobe Portable Document Format (PDF). To read translated and localized warranty information about your product, follow these steps: a. Enter this part number in the Warranty Document Number field: 78-5236-01C0 b. Select the language in which you would like to read the document.

The Cisco warranty page appears. Review the document online, or click the PDF icon to download and print the document in Adobe Portable Document Format (PDF). Click this link to browse to the Cisco Support and Documentation page: Duration of Hardware Warranty Ninety (90) days. Replacement, Repair, or Refund Policy for Hardware Cisco or its service center will use commercially reasonable efforts to ship a replacement part within ten (10) working days after receipt of a Return Materials Authorization (RMA) request. Actual delivery times can vary, depending on the customer location. Cisco reserves the right to refund the purchase price as its exclusive warranty remedy.

To Receive a Return Materials Authorization (RMA) Number Contact the company from whom you purchased the product. If you purchased the product directly from Cisco, contact your Cisco Sales and Service Representative. Complete the information below, and keep it for reference.

The WUSB54GC is a compact wireless-G USB adapter that connects your computer to a wireless network. This adapter also lets you connect to any public wireless hotspots in places such as coffee shops, airports, hotels, and convention centers. This article will show you the features of a Wireless-G USB Compact USB Network Adapter (WUSB54GC).