CLEANACCESS Archives

April 2007

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"King, Michael" <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Thu, 5 Apr 2007 16:50:44 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (75 lines)
Pssst.....

You can also create the DNS name of
CISCO-LWAPP-CONTROLLER.your.domain.edu pointing to your AP manager.

And the AP's will find the controller.  

I think the order is
L2 broadcast
Then for L3

Broadcast
Over the Air (OTAP)
Previously Configured (remembered)
DHCP response
DNS response


Mike
 

> -----Original Message-----
> From: Cisco Clean Access Users and Administrators 
> [mailto:[log in to unmask]] On Behalf Of Cal Frye
> Sent: Thursday, April 05, 2007 3:47 PM
> To: [log in to unmask]
> Subject: DHCP options
> 
> I'm [still] running version 3.5.11.
> We're trying to insert DHCP options for our Airespace 
> wireless controllers and Novell's SLP settings. So far, I 
> can't even get to first base.
> 
> To tell the wireless access points where to find the 
> controller, Cisco's documentation tells us to set DHCP option 
> 43 for the address, like this:
> 
> option 43 hex f104ac10fc55
> 
> for a single controller at address 172.16.252.85, for 
> example. (f1 is an option code, 04 tells us we're sending 4 
> octets, i.e. a single address, and the remainder is the IP 
> address in hex)
> 
> I've gone into one of our CCA servers, DHCP Global Options 
> tab, and tried several things with no success. What am I doing wrong?
> 
> 1) entered it as a Root Global Option, using the text above. 
> The DHCP daemon failed to restart, didn't like the syntax of 
> the option.
> 2) entered it as a Root Global Option, minus the keyword 
> "option." That didn't work, either. I don't find the error 
> messages particularly illuminating.
> 
> 3) entered it as a Scoped Global Option, and while it shows 
> up on the subnet definition page as an additional option, it 
> doesn't actually appear in the generated dhcpd.conf file and 
> I don't see where the option is actually being issued to clients.
> 
> It doesn't surprise me that this feature was completely 
> redone in version 4.x...
> 
> Anyone have some light to shed on this particular?
> --
> Regards,
> -- Cal Frye, Network Administrator, Oberlin College
> 
>    www.calfrye.com,  www.pitalabs.com
> 
> "This is the moment freedom begins, the moment you realize 
> someone else has been writing your story, and it's time you 
> took the pen from his hand and started writing it yourself." 
> -- Bill Moyers.
> 

ATOM RSS1 RSS2