• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 640
  • Last Modified:

getting two Cisco 1131 AP's to give out different ranges from Wireless Lan controller...

I have a Cisco 4507R with a wireless LAN controller plugged into it (4402). I also have an access point plugged into the switch so I can test it. Everything is working but I'd like to put one last change in.

The access point has two wireless SSID's that it's broadcasting (wlan1 and wlan2). Right now they're both getting the DHCP server on our network from the controller and giving out addresses in the regular range. 10.0.0.1-250. What I would like to do is have one SSID give out one range and then the other to give out another range like 192.168.1.1-250.

Can anyone tell me how I can do this in this setup? I have different ranges defined in my dhcpd.conf file that point to different VLAN, so how can I make the AP's give out ranges from these?

0
wlandymore
Asked:
wlandymore
  • 12
  • 9
1 Solution
 
jjmartineziiiCommented:
Yes its very possible.

Who is your DHCP server right now?
0
 
wlandymoreAuthor Commented:
the DHCP server is a Linux box plugged into the 4507 switch
0
 
jjmartineziiiCommented:
what you need to do is create a trunk between the switch and controller.

then create new interfaces on the vlan you want to assign. in the interface properties, point the DHCP to your linux box. Then, assign the SSID that interface.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
wlandymoreAuthor Commented:
Any chance you could explain those steps a little. :)

I'm really new to Cisco stuff so it can take a while to muddle through things.
0
 
wlandymoreAuthor Commented:
If I create the trunk between the two should I make only the two VLAN's accessible to that? I see where to create the interfaces on the controller and then assign them a VLAN id and DHCP server so I think I have part figured out....
0
 
jjmartineziiiCommented:
Ok, well you need to create a new DHCP scope. So create that on your linux box.

Personally, I have it running on the switch so here is my config:

ip dhcp pool GuestSSID
   network 10.66.66.0 255.255.255.0
   netbios-node-type h-node
   dns-server 192.168.9.2 192.168.9.3
   default-router 10.66.66.1
!


So now we have the DHCP covered. Now I need to make the VLAN:

interface Vlan11
 description ** Guest SSID **
 ip address 10.66.66.1 255.255.255.0
!


So now my switch can be accessed using the new ip address of 10.66.66.1. If i were to assign any port vlan11, it would now get a 10.66.66.X address.

Now I need to create a new interface on the controller. Login in and hit controller  and Interfaces on the left.

Click New.. at the top right to create a new interface.  Give it a Name such as "Guest SSID" and assign it the VLAN you are using on your switch, in my case, its 11. Now at the edit page, give it the intformation it wants. Give it an IP, in my case 10.66.66.2 subnet and gateway. Assign a port number and for the DHCP, put the address of the DHCP server. In my case, its 10.66.66.1.  Apply the changes.


Now you have to tell your SSID to use that interface. Go to WLANs and edit the SSID you want to have that address range. Change the Interface to whatever you named the interface in the previous step.

You must make the ports connecting to the WLC trunking so it can access multiple ports.

0
 
jjmartineziiiCommented:
I mean multiple vlans*.

Here is the example of the port:

interface GigabitEthernet3/0/1
 description ***CISCO WLC***
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 9
 switchport mode trunk

The native vlan is 9 which lets me access the controller using a 192.168.9.X address (my management interface).
0
 
wlandymoreAuthor Commented:
It accepted the IP, mask and gateway, but it doesn't like the fact that the DHCP server is on a different network from the IP of the VLAN. How can I get it to accept that different subnet as the one where it should be getting the DHCP information?
0
 
wlandymoreAuthor Commented:
okay, my bad. It was the port configuration it didn't like. Once I switched that it accepted it.
0
 
jjmartineziiiCommented:
Hmmm, i've never tried that but I created a test interface and had no problem adding a DHCP on a different subnet.

Im running 4.1.185.0
0
 
wlandymoreAuthor Commented:
I just missed putting in a port number so it had 0 and 0 and it wanted two different ports. Once I put that in it was fine.

Just going to work out the rest and I'll let you know.

Thanks so far though....very good instructions
0
 
jjmartineziiiCommented:
oh ok good. yeah good luck!
0
 
wlandymoreAuthor Commented:
I thought if you wanted to set trunking on a port on the WLC it was under Controller > ports > edit but I don't see it there.
0
 
jjmartineziiiCommented:
Setting the trucking on the switch side. WLC will automatically truck. Set the native vlan on the switch to the vlan that uses the management IP
0
 
wlandymoreAuthor Commented:
Yeah, I have that done.

I can see the access point and it tries to connect but the DHCP isn't getting there because it doesn't assign an address.
0
 
jjmartineziiiCommented:
what i would do to test is to try using the built in dhcp server of the WLC and pointing clients to itself as a DHCP server
0
 
wlandymoreAuthor Commented:
yeah, that's probably a good idea. I'll give that a shot.
0
 
wlandymoreAuthor Commented:
put on the DHCP range on the WLC but I still can't get it to acquire an address. It just sits there looking until it gives it an APIPA one.
0
 
wlandymoreAuthor Commented:
Okay, I got it. I hadn't specified the management interface (properly) as the DHCP server of the VLAN interface that was created in the WLC. Once I did that it came up 'Excellent' right away.

Thanks for all your help...that was great.
0
 
jjmartineziiiCommented:
Thats great! I remember when I was configuring mine, it was very difficult and had to read the configuration guide 3 times before I understood it. I recommend you read it as well! There are alot of great features.
0
 
wlandymoreAuthor Commented:
yeah, will do.

I started with the quick config guide and then I got as far as creating the two networks but I was kinda stuck there. :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

  • 12
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now