Journey

Journey

Translate

Wednesday, June 18, 2014

Introduction to Wireless

Introduction to Wireless!

This probably should have been my 2nd post after the "Intro" post but its never too late to create a post on introduction to wireless.

Quick overview of what you will learn:


*         What is Wireless?
*         WPAN/WLAN/WMAN/WWAN
*         Standalone AP and Controller based AP
*         802.11a/b/g/n and 802.11a/c
*         2.4 GHz
*         5.0 GHz
*         Interference
*         Why Wireless Skills Matter
*         Different Types of Cisco Access Points

Lets define wireless:

       Wireless is: Not using wires to send and receive electronic signals: sending and receiving electronic signals by using radio waves.

Lets define Radio Waves:

Radio Waves are: An electromagnetic wave that is used for sending signals through the air without using wires.

4 Common Types of Wireless Networks you will hear about:


*        WPAN – Wireless Personal Area Network
      Works in a very small area (5 to 10 meters)
      Mice, keyboards, headsets that connect to your computer
      Think of Bluetooth
*        WLAN (Wireless Local Area Network)
      Works typically around an area of under 100 meters
      Think of the wireless network you have at your house or office
*        WMAN -Wireless Metro Area Network
      Low budget, bridging network.

      Alternative to T1 or 3 point to point leased lines. 
*        WWAN (Wireless Wide Area Network)
      Cellular service providers – Example: AT&T nationwide GSM cellular Network.

2 types of access point modes you will hear about:


v  Access Point in:
       Standalone Mode – No WLC
      Router (layer 3)
      Switch (layer 2)
      Wireless Access Point standalone
      End Devices (Wireless phone, ipad, laptop, etc)

      Access Point – Lightweight Access Points –
(LWAPP/CAPWAP – Controller Mode)
      Router (layer 3)
      Switch (layer 2)
      Wireless Access Point (LAP)
      Wireless LAN Controller

      End Devices (Wireless phone, ipad, laptop, etc)
We still need the wireless NIC on the client side for everything to complete the list of component
for a wireless network.

Be familiar with the following terms:


v  IBSS (Independent Basic Service Set) – Ad Hoc
      Wireless NICs and other devices can communicate directly without the need for an AP.
      Peer to Peer
v  BSS (Basic Service Set) – The area/cell defined by the wireless signal served by the AP.
      It might be referred to as BSA.
      Single AP
v  ESS (Extended Service Set) –
      Most common in a corporate environment
      All access points to the same SSID
      Roaming ability takes place

v  SSID (Service Set Identifier ) – Unique 32-character identifier







Now lets go over 802.11a/b/g/n:



*         Narrow band and spread spectrum are the two main ways of sending a signal
*         802.11a operate at:
*         5.0GHz band
*         Uses OFDM with modulation formats that are available: BPSK, QPSK, 16-QAM, 64-QAM
*         802.11b operate at:
*         2.4GHz band
*         Uses DSS (Direct-sequence spread spectrum) with CCK or PBCC modulation formats.
*         802.11g operate at:
*         2.4GHz band
*         Uses either OFDM or DSS and the modulation formats are set according to the data rate.
*         802.11n operate at:
*         Can operate at both 2.4GHz and 5.0GHz band
*         Uses DSSS but prefers OFDM (Orthogonal frequency division multiplexing)
*         MIMO + OFDM
*         802.11a/c operate at:              
*         5.0GHz band with support for backwards compatibility with other 802.11n technologies operating in the same band. MIMO + OFDM
*         802.11ac AP Support up to 8 data streams (Each stream at 433Mbps)
*         Max speed 1.3Gbps

*         Samsung Galaxy S4 chipset only supports 1 single stream (up to 433Mbps in speed)        

Its always a good idea to understand the basics above. Don't worry too much about the modulation 
techniques just yet!



Now lets take a look at 5.0Ghz









2 terms that you should understand are:


v  RSSI – Received signal strength indicator
       The measure of signal strength that arrives at the receiving device.
       The lower the number to 0dBm would indicate a stronger signal
       Grade value from 0 to 255 with each grade value is an equivalent dBm (decibels to a milliwatt) value.
       The scale will be different from one card vendor to another.
       Anything above SNR of -72dBm would mean the client is far away or signal is weaker
v  SNR – Signal to Noise Ratio
       Comparison of the amount of signal as compared to the surrounding noise.

       The higher the SNR the better. (Anything between 25dB to 40dB SNR is very good signal)


Now lets talk about types of interference's that can weaken or disrupt your wireless signal:

*         Types of signal interference:
       Physical interference – Easier to see.
       A cordless phone sitting next to an AP.
       Plants and Trees
       Microwave ovens
       Hidden physical interference – difficult to mitigate. Think about: What is inside those walls?
       An Exterior wall that consists of brick and thick insulation can cause interference and its not easy to see.
       Lead paint
       Bulletproof glass (you might think nothing of it but the degree of attenuation is high )
       Channel interference – Other wireless devices on an overlapping channel.

       Neighbor APs using channels that is interfering with the AP channel that ones own is on. 

So what happens when there is interference? Well, the wireless signal range is degraded, 
data throughput decreases and you may end up having complete signal drops or intermittent signal 
drops.





Why do wireless skills matter?

Wireless as grown tremendously over the years. Not many people know how to properly design, 
configure and manage a wireless infrastructure. It is an advantage to be not only good but great
with managing a wireless network. As more and more wireless devices come into a network, it
will be up to you as a wireless engineer to train, maintain, support your staff with ease if you
take the time to learn and understand the art of wireless!

I highly recommend going with Cisco because when it comes to wireless deployments because
Cisco gets the job done! Feel free to correct any mistakes I've made or ask me any questions. 
Please check out my twitter and instagram! Most images are courtesy of Cisco, Apple, Wiki,
Ciscolive. I strongly encourage you to visit and register for free at www.ciscolive.com if you 
want to learn more. The site offers free resources from industry experts like myself. 

Thank you for visiting!!!


Cisco 3700 Access Points (802.11ac)

Cisco 3600 Access points (support for 802.11AC with module)

Cisco 2700 Access points (3x4, 802.11ac)

Cisco 1600 Acces points (entry-level)

















































Thursday, May 1, 2014

Wireless LAN Controller (WLC) Software Upgrade 5508/2504/vWLC

This post is for those of you that are not sure how to upgrade the wireless code using the GUI (I will do another post on how to do it via CLI). Reading this post will give you almost a step-by-step process on how to upgrade a WLC code on a 5508 (its very similar if you have a Cisco Wireless 2504 or virtual WLC (vWLC) controller as well)

The following questions will be answered after reading this post:

1. When its a brand new controller without any configuration, how do I update the code?

2. Where is the service port on a 5508 WLC and how do I use it?

3. How do I upgrade primary or secondary wireless code using GUI and a TFTP server?

4. How do I switch between primary image and backup image?


Step 1.

When you first boot up a Cisco 5508 while being consoled in, you will notice the controller go through its boot up process and you will most likely notice on the screen that reads "Press <ESC> now to access the Boot Menu..."

Now, if you have not configured the new WLC yet, you might be tempted to check out what the menu is all about.

It will look something like this:

============================================================
 Boot Loader Menu
============================================================

 1. Run primary image (7.0.241.7) - Active
 2. Run backup image (7.0.241.7)
 3. Change active boot image
 4. Clear configuration
 5. Format FLASH Drive
 6. Manually update images

------------------------------------------------------------


Here you will notice you can change the boot up to run primary or backup image. Clear the configuration, format FLASH drive or manually update images.

You might think, "hey I can manually update the image". Think again...

If you go through option 6, this is what it would look like:

Enter selection: 6
Launching...
init started: BusyBox v1.6.0 (2010-05-13 17:50:10 EDT) multi-call binary
starting pid 683, tty '': '/etc/init.d/rcS'
Use DHCP for ip configuration (Y/n)? n
Enter switch IP address: 192.168.1.3
Enter switch netmask: 255.255.255.0
Enter switch gateway: 192.168.1.1
Enter TFTP server IP address: 192.168.1.2

You have entered:
     IP Address     : 192.168.1.3
     Netmask        : 255.255.255.0
     Gateway        : 192.168.1.1
     Server Ip Addr : 192.168.1.2

Is this correct(y/N)? y

!!! WARNING updating using .aes or unapproved files will disable this unit !!!

Do you want to update RTOS (y/N)? y

Do you want to update Primary Or Secondary Image (P/s)? P

Enter filename for RTOS update: AIR-CT5500-K9-7-4-110-0.aes
Error updating RTOS, Invalid image type!
Do you want to update an AP image (y/N)? n
AP Images Not Updated
Done.  Restarting...
Restarting system.



You should NEVER try to update RTOS using .aes file.

This menu does not seem to give you the ability to upgrade the WLC code itself. It does give you the ability to update RTOS and AP image.

SO what do you do at this point?

Go through the WLC AUTO-INSTALL wizard and configure the controller.

When you get to this step:
Service Interface IP Address Configuration [static][DHCP]: static
Service Interface IP Address: 192.168.1.3
Service Interface Netmask: 255.255.255.0


....
Management Interface IP Address: 192.168.2.3
Management Interface Netmask: 255.255.255.0
Management Interface Default Router: 192.168.2.1
Management Interface VLAN Identifier (0 = untagged):
Management Interface Port Num [1 to 8]: 1
Management Interface DHCP Server IP Address: 192.168.2.1



Configure a service port IP. This is useful if you need to upgrade the code before you actually put the WLC on your network. Some people need the ability to upgrade the code without having to rack and stack, connect it to the network by using just your laptop and the service port on the WLC.

Note: This IP has to be on a different network then your management IP address that you will configure.

Once your done with the wizard, hit Save.


Configuration saved!
Resetting system with new configuration...
Restarting system.


Step 2:

Once the WLC boots up, connect an ethernet cable from your laptop directly to the service port.


On your laptop/pc, make sure you go into your IPv4 settings and put your laptop on the same network as your service port.

Example:
Laptop/PC 
IP address: 192.168.1.2
Subnet mask:255.255.255.0
default gateway:192.168.1.1 

Step 3:
Once you are connected, just open a web browser and browse to the management IP that you had configured earlier in the AUTO-INSTALL in  Step. 1


Step 4:

You will notice the software version currently on it at 7.0.241.7.

We will use the GUI to upgrade it to 7.4.110.0 and then to 7.4.121 (I am aware you can upgrade straight to 7.4.121 from the code this has which is 7.0.241.7 but I wanted to show how to have two different codes on primary and secondary boot)






Step 5:

Click on COMMANDS
Click on Download File
Choose "code" from drop down
Choose TFTP
Launch your TFTP server ( I used tftpd64)












You will notice that RTOS to flash disk is being written. I believe this is the best way to upgrade the WLC code as well as RTOS as the .aes file contains the file to update RTOS.




Step 6:
Once the file has been uploaded to the WLC and the WLC update is complete, you will get this prompt below. (Be patient because sometimes this process can take a while so don't navigate to other pages in the GUI)

Click where it says "Click Here" to get redirected.



Step 7:
Click Save and Reboot



Step 8:
Once the WLC reboots, you will see the code has been upgraded to 7.4.110.0 and you will see the backup image as 7.0.241.7 (Click on COMMANDS and then Click on "Config Boot" to see the backup image.)

In this page, you can have the WLC boot on either primary code or secondary by simply changing the 'config boot image' drop down to either Primary or Secondary and hitting save and reboot.

If you were to upload 7.4.121.0 code, it will back the primary image as backup image and the newly uploaded image as primary image.



Note: Be aware that when you upgrade the WLC code, your APs will go down and will start upgrading to the newer code. This tutorial is meant for a brand new setup of a WLC that is not on the network yet. I will perhaps post a tutorial on how to pre-stage APs in Cisco Prime at a later post.

Step 9:
Upgrade to code 7.4.121.0 the same way I upgraded to 7.4.121.0.

Step 10:

If you ever want to blow out your configuration since you had used the AUTO INSTALL wizard just to get things up and running to upgrade the WLC code, you can simply clear out all the configs except for the code by doing the following:

After you are done upgrading the code that you want on the WLC and after it restarts, console in and issue the following command:

Recover-Config

And you are done! Now you have the stable code of 7.4.121.0 and its ready to be configured correctly with the correct IP, etc and put on the network.





Thats all folks'! Now you know how to upgrade a WLC 5508 to a newer code, how to boot to either primary or secondary code, what the Boot Loader Menu is all about, and how to use the service port on a 5508 wireless controller.

Feel free to comment me with any errors or positive feedback!


Monday, April 21, 2014

Intro

Ladies & Gentleman,


Allow me to welcome you to my blog! I've been active on online forums reading, commenting, attending excellent Cisco user groups such as the Southern California Cisco User Group (If you live in SoCal, I highly recommend checking it out, its FREE & informative) where CCIE engineers like Jason Bomar and Robert Yee tend to enlighten most of us with their expertise in Cisco Products and best practices. My background in computers goes back to when I was a kid at the age of 9 with the opportunity to use an Apple computer at school. While learning about computers as a hobby, I pursued my college degree in Business Management from CSUN and Automotive Technology from Pierce College. Eventually I made one of my dreams happen, which was to work for Mercedes Benz where I became an Automotive Technician, Emissions Specialist and a Team Leader. My strengths included on-board computer diagnostics, emission testing and troubleshooting.
Few years later, I attended Cisco Academy and took my first CCNA class as I grew more interest in the field of networking after realizing the different networks a Mercedes Benz vehicle had and that eventually got me to where I am today as a Network Engineer with a focus on Wireless Technology and Data Center. It is amazing to see how far wireless have grown over the years. This made an impact on me because I realized that wireless communication gives us the ability to keep our communication between our friends and family no matter where we are in the world (almost anywhere in the world as long as there is a signal).


In all honesty, I created this blog to share what I learn throughout my career on the job with Cisco Wireless deployments, help others to resolve wireless issues and to help others grow as engineers working on Cisco technology and lastly to make a positive impact in lives of others.


If you enjoy WiFi, Networking or Data Center then feel free to follow my blog. I am currently a CCNP Wireless and look forward to becoming a CCIE in Wireless and Eventually in Data Center.


Feel free to share your thoughts and follow me on:
twitter: http://www.twitter.com/LPerera3



"I am a member of the Cisco Champions Program. Cisco Champions are passionate about Cisco and enjoy sharing our knowledge, expertise, and thoughts across the social web and with Cisco. I am not a representative of Cisco. My views as a Cisco Champion are my own."