WifiNigel

This probably falls into that category: " stuff that everyone else already knows, but I don't ", but I thought it was worth jotting down a few notes about. I recently saw someone tweet about the command: " netsh show wlan <various options> ", which I had never heard of before. After having had a look through the command help screens, it seems an incredibly useful command if you want to quickly find out about the wireless networks and the wireless capabilities of a Windows 7 machine you're working on. Much of the information can be found by poking around in various GUI pages, but this command line utility is much quicker to use and gives a greater depth of information. I'll just run through a few useful examples and then leave you to poke about in the help pages yourself if you want to know more. A great way to get a summary of the wireless networks that a Win 7 client can hear is to open a command window (...or a DOS box as I like to call i...

Just a quick note for anyone who may come across a similar issue when trying to deploy server images on to their VMWare environment. I've been lucky enough to get a new server recently to test various virtual WLCs and management packages that are being put out by various wireless vendors. But after installing ESXi and deploying a couple of server images, when I tried to start the virtual servers up, I kept getting the following messages popping up in vShere: (For search engine benefit: This virtual machine is configured for 64-bit operating systems. However, 64-bit operation is not possible. Longmode is not possible. Longmode is disabled for this virtual machine ) Also, in the console of the server (Cisco MSE & NCS), I was getting the following reported: " Your CPU does not support long mode. use a 32 bit distribution " I was concerned that maybe there was an issue with my server CPU, in terms of support for virtualization.  I rebooted the server ...

The whole area around the free DTLS license that can be obtained for Cisco WLCs has always been a bit of a head-scratcher for me. I'm never sure whether I need the additional license or I already have it to be honest. Anyhow, today on my home lab I tried to have a look at some features which required DTLS between the AP & WLC, only to find that my 2504 did not support the option (the option was grayed out). After some digging around on the Cisco forums, I found that the following licensing link can be used to obtain the DTLS entitlement license with very little fuss at all: https://tools.cisco.com/SWIFT/LicensingUI/loadDemoLicensee?FormId=4090 The information to be entered can be found on the WLC inventory page. Only the model number & serial number are required. Within seconds, I had the license (which can be downloaded directly or sent by email) and applied it to my 2504 (Management > Software Activation > Commands > Install License)