lightweight

[dkblee]

hi! I'm trying to configure some of the aut

onomous command into ligthweight ap, but not too sure how.

In autonomous setup, i've these commands

1) server x.x.x.x aut-port 1645 acct-port 1646

2) service timestamps debug datetime msec localtime show time-zone

3) service password-encryption

4) password enable secret

5) snmp-server community aaaaa RW

6) EAP authentication x.x.x.x

7) encryption mode aes ccmp_tkip

banner

9)how do i enable http access in lightweigh AP

how do i configure these in the lightweight AP?

Thanks.

[Leo Laohoo]

how do i configure these in the lightweight AP?

You DON'T.  That's what the WLC is for.

[dkblee]

but it seems that not every option i listed above is configurable in wlc or wcs. Can these settings be configured in a template and push down to the access points? where can i do that....i did not see the options there. Thks

[Peter Nugent]

1) server x.x.x.x aut-port 1645 acct-port 1646 Under security tab

2) service timestamps debug datetime msec localtime show time-zone - should be ok if your time is correct on the wlc as the ap pulls its cofig from the controller and sends messages back to the controller

3) service password-encryption - not required you can however set passwords on the access points if you wanted to

4) password enable secret - I dont think so

5) snmp-server community aaaaa RW - Yes this again is from the WLC as all messages will be from the wlc

6) EAP authentication x.x.x.x - WLC

7) encryption mode aes ccmp_tkip - WLC  WLANS tab

8) banner - No

9)how do i enable http access in lightweigh AP - there is no http access to the access points only the controller.

The whole point of a centralised solution is that all of your management and pretty much all of your troubleshooting is done from the controller, this is where you will set your WLAN security and RADIUS servers etc

[Vinay Sharma]

Hi,

Please mark the Question as Answered if the provided information is correct and issue is fixed.

thanks,
Vinay

[Carlos Leiton]

Lightweight access points are meant to be zero-touch deployment. The operating system of the lightweight is that, lightweight, though it does not has any of the regular commands that you use to configure an autonomous.

This means that you do all the configuration from the Wireless LAN Controller.

There is no reason why you want to access the CLI because there is nothing that you can configure there. Banner is not required because nobody should be accesing the Access Point through Telnet or SSH, also HHTP access is not enabled at all.