Topic 'Re: Wireless LAN Controller or WLSE?' in forum 'Cisco' - dslreports.com

Re: Wireless LAN Controller or WLSE?

Thu, 03 Jan 2013 04:27:27 EDT

markysharkey posted : Unfortunately a non disclosure order prevents me from giving a fuller explanation of where these will be deployed. Suffice to say the area to be covered is considerably less than 5000 sq feet per floor. I have 8 access points spread over 3 floors plus one outside. The area has some challenges to overcome with regards to signal propogation so we routinely spec what would be considered to be far too many AP's for the size of the area in order to compensate for those challenges.

Now I know how to get it going I can erase start the lot and configure it with the actual deployment config.

Once again, I would like to thank you guys for your contributions which have all been really helpful.

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 23:44:43 EDT

HELLFIRE posted : DHCP options here, IIRC 66 and 150 are the key ones, along with basic connectivity to the TFTP server, but sounds like you got it figured out.
Congrats and let us know what the PM's reaction is.

Regards

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 19:56:12 EDT

phantasm11b posted : Glad to hear it's working. I've got about 20 of those wireless phones on my enterprise WLAN. They're a bit of pain up front but after you get them running they're good to go. Make sure you have the AP density to allow for seamless roaming. General rule of thumb is each AP overs 5000 sq ft. Subtract 1/3 from that for voice and another 1/3 if you want to run location tracking. So, if you have a 10,000 sq ft building you would need 2 AP's for data. If your running voice you'd be better running 3 AP's for that amount of space. These are of course just quick guidelines, but something to keep in mind.

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 19:24:54 EDT

markysharkey posted : Ok, thanks for that. It is currently working with import all but I'll remove it and I'll ditch the Google DNS too.
Also Option 66 is currently configured, pointing at 50.1 but I'll try Option 150 again to see what happens and so I can properly document the process and config required.

The install isn't that big. 12 wireless phones, about 12 wired but only 2 of them are "feature phones" (7940G's). The rest are 6901's. There are 8 1142 LAP's and a couple of 2960S's to complete the LAN.
Now I know I can get the wireless phones going the next job is the tedium of adding them to the CME and creating DN's. Once that's out the way I'll move on to getting the features working. Expect more threads in the not too distant future!

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 18:55:38 EDT

cramer posted : The Voice pool DNS server should be the CME host only (50.1?) so it can find CiscoCM1 (the call manager.) There's no reason for them to resolve public internet hosts; and the router can do it if they do. [Note: that's actually 'CiscoCM1.' -- NO DOMAIN component. That makes it hard to add to most DNS servers.]

You can get around this by static programming *everything* on the phone. (that's the way I make remote 12sp+'s run. Yes, I still have one.) I'm sure your installation is too large for that. Option 150 (ip addresses) or 66 (hostname or address) points to CME to get their configuration file(s). DNS is how they'll find the callmanager.

[edit]
That would be...


ip dhcp-pool Voice
  network 192.168.50.0 255.255.255.0
  option 150 ip 192.168.50.1
  import all !! NO
  dns 192.168.50.1
  defualt router 192.168.50.2

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 18:11:07 EDT

markysharkey posted : Cracked it! Not quite sure which config got it working but I suspect it was adding the TFTP server (the CME) IP address to the handsets under the network config setting. I added the native VLAN ip address of the CME as a secondary TFTP Server address and both phones popped up on the CME really quickly. One DN and one ephone mac-address later and I had wireless calls between the two handsets. I will brick one of the handsets tomorrow to pin down exactly what was needed to get it working.

Now I can at least show the project manager that we can route calls. Imagine how pleased he will be when I tell him I have a phone system on which telephone calls can be placed and received...

I'd than to thank you guys for replying to my plea for help. It really is very much appreciated. I will no doubt be back with more questions as I get deeper in to the whole CME / wireless phone set up. But now it's time for a celebratory cup of tea!

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 11:16:44 EDT

phantasm11b posted : I should've elaborated. We use option 66 to allow the phone to pull the config file from cme via tftp. I am not sure where you get the file... I would have to check with our voice guy but I'm not in the office.
--
"There are two American flags flying on the property I reside on. Anyone who tries to take them down will be rendered inoperative." -Lindy

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 10:17:05 EDT

markysharkey posted : OK, voice is back on Port 1... just re-booting everything just in case!

Edit...
Still nothing

Second edit...
Both phones now have matching system messages, so I guess that's progress of sorts. I just don't know where that progress is taking me!

Third edit...
The DHCP phone is now showing an xml.default.cnf.xml: TFTP error message.
Schoolboy error alert! Am I supposed to be offering the .cnf file out from TFTP on the CME?
If so, I don't have it. Can I download it from Cisco.com?

Fourt edit...

The .cnf files are present for the statically configured phone.
sho telephony-service tftp-binding shows what's there, so I don't think it's a TFTP issue unless it's related to a DHCP option or an IP address issue.

Router_2901#sho telephony-service tftp-bindings
tftp-server system:/its/united_kingdom/7960-tones.xml alias United_Kingdom/7960-tones.xml
tftp-server system:/its/united_states/7960-tones.xml alias United_States/7960-tones.xml
tftp-server system:/its/united_states/7960-font.xml alias English_United_States/7960-font.xml
tftp-server system:/its/united_states/7960-font.xml alias English_United_States/7920-font.xml
tftp-server system:/its/united_states/7960-dictionary.xml alias English_United_States/7960-dictionary.xml
tftp-server system:/its/united_states/7960-kate.xml alias English_United_States/7960-kate.xml
tftp-server system:/its/united_states/7960-kate.xml alias English_United_States/7920-kate.xml
tftp-server system:/its/united_states/SCCP-dictionary.xml alias English_United_States/SCCP-dictionary.xml
tftp-server system:/its/vrf1/XMLDefault7945.cnf.xml alias SEP10BD18001015.cnf.xml
tftp-server system:/its/vrf1/XMLDefault7945.cnf.xml alias SEP10BD1801C09C.cnf.xml
tftp-server system:/its/vrf1/XMLDefault6901.cnf.xml alias SEP203A0722B1CA.cnf.xml
tftp-server system:/its/vrf1/XMLDefault6901.cnf.xml alias SEP203A0722B215.cnf.xml
tftp-server system:/its/vrf1/XMLDefault6901.cnf.xml alias SEP203A0722B372.cnf.xml
tftp-server system:/its/vrf1/XMLDefault6901.cnf.xml alias SEP203A0722B248.cnf.xml
tftp-server system:/its/vrf1/XMLDefault6901.cnf.xml alias SEP203A0722B258.cnf.xml
tftp-server system:/its/vrf1/XMLDefault6901.cnf.xml alias SEP203A0722B11C.cnf.xml
tftp-server system:/its/vrf1/XMLDefault7925.cnf.xml alias SEP442B0355XXXX.cnf.xml
tftp-server system:/its/SEPDEFAULT.cnf alias SEPDefault.cnf
tftp-server system:/its/vrf1/XMLDefault.cnf.xml alias XMLDefault.cnf.xml
tftp-server system:/its/vrf1/ATADefault.cnf.xml alias ATADefault.cnf.xml

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 10:05:38 EDT

markysharkey posted : Option 66 produced no results. I removed Option 150 before adding Option 66 and I pointed it at the CME.
On the phone wiith static configs I see these system messages in this order from phone boot:
IP Initialized
TFTP Timeout
Installed MIDP Module Successfully
CiscoCM1
DNS Unknown Host

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

Delco, even with the no ap option the output is still huge. Care to narrow it down a bit so I can show the relevant sections?
What I think is relevant is below:

====================================

(Cisco Controller) >show run-config no-ap

Press Enter to continue...

System Inventory
NAME: "Chassis" , DESCR: "Cisco 2500 Series Wireless LAN Controller"
PID: AIR-CT2504-K9, VID: V01, SN: PSJ163000E5

Burned-in MAC Address............................ 64:D8:14:xx:xx:xx
Maximum number of APs supported.................. 15
Press Enter to continue or to abort

System Information
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.2.103.0
Bootloader Version............................... 1.0.16
Field Recovery Image Version..................... 1.0.0
Firmware Version................................. PIC 16.0

Build Type....................................... DATA + WPS

System Name...................................... xxxxxxxxxxxx
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 192.168.0.5
Last Reset....................................... Power on reset
System Up Time................................... 0 days 0 hrs 18 mins 20 secs
System Timezone Location.........................

Configured Country............................... GB - United Kingdom
Operating Environment............................ Commercial (0 to 40 C)

--More or (q)uit current module or to abort
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +26 C
External Temperature............................. +30 C
Fan Status....................................... 3900 rpm

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 4
Number of Active Clients......................... 2

Burned-in MAC Address............................ 64:D8:14:xx:xx:xx
Maximum number of APs supported.................. 15
Press Enter to continue or to abort

Switch Configuration
802.3x Flow Control Mode......................... Disable
FIPS prerequisite features....................... Disabled
secret obfuscation............................... Enabled
Strong Password Check Features:

case-check ...........Disabled
consecutive-check ....Disabled
default-check .......Enabled
username-check ......Disabled

Network Information
RF-Network Name............................. xxxxxxxxxxx
Web Mode.................................... Enable
Secure Web Mode............................. Enable
Secure Web Mode Cipher-Option High.......... Disable
Secure Web Mode Cipher-Option SSLv2......... Enable
OCSP........................................ Disabled
OCSP responder URL..........................
Secure Shell (ssh).......................... Enable
Telnet...................................... Enable
Ethernet Multicast Forwarding............... Disable
Ethernet Broadcast Forwarding............... Disable
AP Multicast/Broadcast Mode................. Multicast Address : 0.0.0.0
IGMP snooping............................... Disabled
IGMP timeout................................ 60 seconds
IGMP Query Interval......................... 20 seconds
MLD snooping................................ Disabled
MLD timeout................................. 60 seconds
MLD query interval.......................... 20 seconds
User Idle Timeout........................... 300 seconds
ARP Idle Timeout............................ 300 seconds
Cisco AP Default Master..................... Disable

--More or (q)uit current module or to abort
AP Join Priority............................ Disable
Mgmt Via Wireless Interface................. Enable
Mgmt Via Dynamic Interface.................. Disable
Bridge MAC filter Config.................... Enable
Bridge Security Mode........................ EAP
Mesh Full Sector DFS........................ Enable
AP Fallback ................................ Enable
Web Auth Redirect Ports .................... 80
Web Auth Proxy Redirect ................... Disable
Web Auth Captive-Bypass .................. Disable
Web Auth Secure Web ....................... Enable
Fast SSID Change ........................... Disabled
AP Discovery - NAT IP Only ................. Enabled
IP/MAC Addr Binding Check .................. Enabled
CCX-lite status ............................ Disable
oeap-600 dual-rlan-ports ................... Disable
oeap-600 local-network ..................... Enable
Press Enter to continue or to abort

Port Summary
STP Admin Physical Physical Link Link
Pr Type Stat Mode Mode Status Status Trap POE
-- ------- ---- ------- ---------- ---------- ------ ------- -------
1 Normal Forw Enable Auto 1000 Full Up Enable N/A
2 Normal Disa Enable Auto Auto Down Enable N/A
3 Normal Disa Enable Auto Auto Down Enable Enable (Power Off)
4 Normal Disa Enable Auto Auto Down Enable Enable (Power Off)
Press Enter to continue or to abort

AP Summary
Number of APs.................................... 2

Global AP User Name.............................. Not Configured
Global AP Dot1x User Name........................ Not Configured

AP Name Slots AP Model Ethernet MAC Location Port Country Priority
------------------ ----- -------------------- ----------------- ---------------- ---- ------- ------
APf0f7.5519.xxxx 2 AIR-LAP1142N-E-K9 f0:f7:55:xx:xx:xx default location 1 GB 1
APf0f7.5560.xxxx 2 AIR-LAP1142N-E-K9 f0:f7:55:xx:xx:xx default location 1 GB 1

AP Tcp-Mss-Adjust Info
AP Name TCP State MSS Size
------------------ -------- -------
APf0f7.5519.xxxx disabled -
APf0f7.5560.xxxx disabled -

802.11a Configuration
802.11a Network.................................. Enabled
11nSupport....................................... Enabled
802.11a Low Band........................... Enabled
802.11a Mid Band........................... Enabled
802.11a High Band.......................... Enabled
802.11a Operational Rates
802.11a 6M Rate.............................. Disabled
802.11a 9M Rate.............................. Disabled
802.11a 12M Rate............................. Mandatory
802.11a 18M Rate............................. Supported
802.11a 24M Rate............................. Supported
802.11a 36M Rate............................. Supported
802.11a 48M Rate............................. Supported
802.11a 54M Rate............................. Supported
802.11n MCS Settings:
MCS 0........................................ Supported
MCS 1........................................ Supported
MCS 2........................................ Supported
MCS 3........................................ Supported
MCS 4........................................ Supported
MCS 5........................................ Supported
MCS 6........................................ Supported

--More or (q)uit current module or to abort
MCS 7........................................ Supported
MCS 8........................................ Supported
MCS 9........................................ Supported
MCS 10....................................... Supported
MCS 11....................................... Supported
MCS 12....................................... Supported
MCS 13....................................... Supported
MCS 14....................................... Supported
MCS 15....................................... Supported
MCS 16....................................... Supported
MCS 17....................................... Supported
MCS 18....................................... Supported
MCS 19....................................... Supported
MCS 20....................................... Supported
MCS 21....................................... Supported
MCS 22....................................... Supported
MCS 23....................................... Supported
802.11n Status:
A-MPDU Tx:
Priority 0............................... Enabled
Priority 1............................... Disabled
Priority 2............................... Disabled
Priority 3............................... Disabled

--More or (q)uit current module or to abort
Priority 4............................... Enabled
Priority 5............................... Enabled
Priority 6............................... Disabled
Priority 7............................... Disabled
Aggregation scheduler.................... Enabled
Realtime Timeout..................... 10
A-MSDU 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
Rifs Rx ..................................... Enabled
Guard Interval .............................. Any
Beacon Interval.................................. 100
CF Pollable mandatory............................ Disabled
CF Poll Request mandatory........................ Disabled
CFP Period....................................... 4
CFP Maximum Duration............................. 60
Default Channel.................................. 36

--More or (q)uit current module or to abort
Default Tx Power Level........................... 0
DTPC Status..................................... Enabled
Fragmentation Threshold.......................... 2346
TI Threshold..................................... -50
Legacy Tx Beamforming setting.................... Disabled
Traffic Stream Metrics Status.................... Enabled
Expedited BW Request Status...................... Enabled
World Mode....................................... Enabled
EDCA profile type................................ default-wmm
Voice MAC optimization status.................... Disabled
Call Admission Control (CAC) configuration
Voice AC:
Voice AC - Admission control (ACM)............ Enabled
Voice Stream-Size............................. 84000
Voice Max-Streams............................. 2
Voice max RF bandwidth........................ 75
Voice reserved roaming bandwidth.............. 6
Voice CAC Method ............................. Load-Based
Voice tspec inactivity timeout................ Disabled
CAC SIP-Voice configuration
SIP based CAC ................................ Disabled
SIP Codec Type ............................... CODEC_TYPE_G711
SIP call bandwidth ........................... 64

--More or (q)uit current module or to abort
SIP call bandwith sample-size ................ 20
Video AC:
Video AC - Admission control (ACM)............ Enabled
Video max RF bandwidth........................ 5
Video reserved roaming bandwidth.............. 0
Best-effort AC - Admission control (ACM)...... Disabled
Background AC - Admission control (ACM)....... Disabled
Maximum Number of Clients per AP Radio........... 200
Press Enter to continue or to abort

802.11a Advanced Configuration
Member RRM Information
AP Name MAC Address Admin State Operation State Channel TxPower
-------------------------------- ------------------ ------------ --------------- ---------- --------
APf0f7.5519.xxxx a4:56:30:xx:xx:xx ENABLED UP 44* Level 1*
APf0f7.5560.xxxx a4:56:30:xx:xx:xx ENABLED UP 36* Level 1*

Interface Name................................... management
MAC Address...................................... 64:d8:14:xx:xx:xx
IP Address....................................... 192.168.0.5
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.0.2
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. untagged
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 192.168.0.2
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Disabled

Interface Name................................... virtual
MAC Address...................................... 64:d8:14:xx:xx:xx
IP Address....................................... 1.1.1.1
DHCP Option 82................................... Disabled
Virtual DNS Host Name............................ Disabled
AP Manager....................................... No
Guest Interface.................................. No

Interface Name................................... voice545
MAC Address...................................... 64:d8:14:xx:xx:xx
IP Address....................................... 192.168.50.5
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.50.2
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 50
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 192.168.50.2
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Enabled

================================================

I included the native VLAN and the Voice VLAN. Phones are on 802.11a, native VLAN is 802.11n.

EDIT.
Just noticed the active physcal port for Voice is port 2. No idea how that happened! I've plugged port two into the switch but no joy.
Going to see if I can put voice back on port 1.

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 09:31:55 EDT

Delco24 posted : Can you post the WLC config? show run-config no-ap

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 07:50:41 EDT

markysharkey posted : I'll give option 66 a go when I get back to my lab this evening, and I'll report back.

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 07:15:40 EDT

phantasm11b posted : I checked my dhcp server and I'm handing out option 66 to my wireless phones which points to our call manager. Not sure if that'll help. The switch config looks fine to me.
--
"There are two American flags flying on the property I reside on. Anyone who tries to take them down will be rendered inoperative." -Lindy

Re: Wireless LAN Controller or WLSE?

Wed, 02 Jan 2013 04:16:54 EDT

markysharkey posted : @ Phantasm
Yes I have done all that acording to what you say, as far as I can tell. I will put up screenshots later.

Hellfire, I will put up the config but as it's a pre deploymant lab there isn't much:

=========================================

vlan 50

ip dhcp-pool Voice
network 192.168.50.0 255.255.255.0
option 150
import all
dns 192.168.0.1 8.8.8.8 8.8.4.4
defualt router 192.168.50.2

ip dhcp excluded-address 192.168.50.1 192.168.50.99

Int vlan 50
ip address 192.168.50.2 255.255.255.0

Int Gig 1/0/47
description Link to WLC
swi mo trunk

Int Gig 1/048
description Link to CME
swi mo trunk

==========================================

The CME is a 2901. There are 4 or 5 sub-ifs on Gig 0/0 which relate to the VLAN's on the switch and all SVI's and sub-ifs are pingable from everywhere.

int gig 0/0.50
ip address 192.168.50.1 255.255.255.0

The router is brand new so it's running CME 8.5 (I think) so it's pretty much the latest version.

CME will see and discover every wired phone I throw at it and I am OK with adding DN's and assigning buttons etc.
I put my laptop wirelessly on to the Voice network to test. It received a DHCP address and could ping throgh to the CME and the WLC.
I cannot ping from the WLC CLI to any subnet other than the native vlan which is VLAN 1, 192.168.0.0/24

Re: Wireless LAN Controller or WLSE?

Tue, 01 Jan 2013 23:23:08 EDT

HELLFIRE posted :

said by markysharkey:

DHCP scopes are on a 2960S switch and all other hosts tested on the Voice VLAN receive DHCP responses as expected. That's 1...

Got the 2960S config (minus passwords and other sensitive info) for review?

And if I read this right, you confirmed the pool itself is functional and is handing out DHCP addresses
as expected right? I've never worked with wireless phones but I'm halfway wondering if there's certain
DHCP options that are(n't) being set.

Regards

Re: Wireless LAN Controller or WLSE?

Tue, 01 Jan 2013 20:04:59 EDT

phantasm11b posted : So... ok. First you create the interfaces which is where you associate the IP address to a vlan. When you create the WLAN your associate the WLAN to an interface. So when you create the WLAN make sure you select the appropriate interface (ap management interface is default). So when you create your voice WLAN, select your voice interface from the drop down menu. Have you tried this or am I misunderstanding the problem?
--
"There are two American flags flying on the property I reside on. Anyone who tries to take them down will be rendered inoperative." -Lindy

Re: Wireless LAN Controller or WLSE?

Tue, 01 Jan 2013 20:00:51 EDT

Paulg posted : The 2504 can support LAG if you upgrade to 7.4 (released last week).

Re: Wireless LAN Controller or WLSE?

Tue, 01 Jan 2013 19:33:53 EDT

markysharkey posted : That may be where I'm going wrong.
The WLC has 4 VLANS each with it's own appropriate interface. The un-tagged VLAN is the management VLAN and is in the native VLAN subnet hanging off port 1 which is a trunk to the switch. All VLAN's are permitted on the switch trunk port. The 2504 does not seem to support LAG.
Each WLAN seems to have to be "mapped" to it's own interface which the WLC creates and names the same as the WLAN. If I put the Voice WLAN into the Management Interface the native VLAN seems to be bumped off as if I had changed the native VLAN. Very confused...

Re: Wireless LAN Controller or WLSE?

Tue, 01 Jan 2013 19:11:10 EDT

phantasm11b posted : Have you permitted your phone vlan on the trunk to the 2504? All vlan's used by the wlc need to be on the trunk port (or LAG) going to the wlc. Once that's done you need to create interfaces on the wlc for the appropriate vlans (same spot as you define the ap manager interface).
--
"There are two American flags flying on the property I reside on. Anyone who tries to take them down will be rendered inoperative." -Lindy

Re: Wireless LAN Controller or WLSE?

Tue, 01 Jan 2013 17:49:15 EDT

markysharkey posted : DHCP proxy is currently disabled but I have tried it enabled as well.
I have two 7925 wireless phones. One is set up for DHCP, one is set up with a static IP and DNS, DHCP Server and TFTP server.
The CME router is set for auto-reg-ephone and I have manually added the phone that I manually configured which seemed to make sense. But neither phone will join the CME. Wired phones are found no problem.
I have noticed that I can't ping the DHCP SVI IP address from the WLC.
WLC Management ip is 192.168.0.5/24 and is VLAN 1
Phone VLAN is 192.168.50.0/24, SVI is 192.168.50.2, CME sub-if is 192.168.50.1. The 2960S is the DHCP server.
I can ping anything on VLAN 1 from the WLC but nothing else.
Appropriate DHCP scopes are set and include Option 150, Import all and DNS server IP's as appropriate.

Re: Wireless LAN Controller or WLSE?

Tue, 01 Jan 2013 15:35:26 EDT

ladino posted : Try Disabling DHCP proxy...under Controller > Advanced
Does the phone have any IP address?

Re: Wireless LAN Controller or WLSE?

Tue, 01 Jan 2013 14:01:32 EDT

markysharkey posted :

quote:
What problems are you having with the 2504?

It's my first one, so lots!
Right now the wireless phones can connect to the AP's but they aren't getting a DHCP response.
DHCP scopes are on a 2960S switch and all other hosts tested on the Voice VLAN receive DHCP responses as expected. That's 1...
Trunks are set up, mls qos and CoS / DSCP trust points are set but CoS to DSCP mappings are not BUT this is a pre-deployment lab. I'll get to those shortly.

2. I have set the CME router (a 2901) to auto-reg-ephone so I am assuming that once the phones get an IP address, CME will see them. I am perfectly OK setting ip wired phones, DN's etc etc, it's the wireless that's kickin' my *** right now.

Re: Wireless LAN Controller or WLSE?

Mon, 31 Dec 2012 23:23:30 EDT

HELLFIRE posted :

said by markysharkey:

Is there one, or is it simply Cisco creating demand out of thin air?

2nd Paulg and Delco24 : it's a question better answered if you have multiple APs to push out for deployment and mangement.

Regards

Re: Wireless LAN Controller or WLSE?

Mon, 31 Dec 2012 17:03:57 EDT

Delco24 posted : Pretty much what Paulg said. But, if you only have a handful of APs with one or two SSIDs and no wireless voice, then you're right, there's really not a huge benefit.

What problems are you having with the 2504?

Re: Wireless LAN Controller or WLSE?

Mon, 31 Dec 2012 14:56:18 EDT

Paulg posted : Simplified management, automatic channel selection, automatic tx power management, rogue AP detection/suppression, seamless roaming (huge for voice deployments)

Re: Wireless LAN Controller or WLSE?

Sun, 30 Dec 2012 20:25:38 EDT

markysharkey posted : Scratch that. I see the WLSE is EoL with no replacement offered. Back to the 2504 I go...

Wireless LAN Controller or WLSE?

Sun, 30 Dec 2012 20:03:03 EDT

markysharkey posted : As I'm struggling with a 2504 WLC right now, and have successfully deployed and maintain SME networks with up to a dozen or so autonomous AP's I have to ask, what does the WLC bring to the table when the max number of AP's is, lets say less than 30? I want to ignore batch configuration for now. I have plenty of copy 'n' paste templates so configging a dozen or so AP's doesn't take long and I still have to set up the WLC which also takes time so initially time saved is not going to be much when using a WLC. So what am I missing? Where's the big advantage of a WLC? Is there one, or is it simply Cisco creating demand out of thin air?