Configuring SAP to CAP

Mostly we convert light weight access point to standalone access point but if we have to configure a SAP to CAP process is following,

1. Keep the CAP image in the Tftp server path and start the server. (You can download CAP image from Cisco website directly without license registration but you need register to login with your ID).

2. In the privilege mode type the following command,

ap# archive download-sw /overwirte /force-reload tftp:///

3. After the file loads completely it will automatically reload with the CAP image.

CAP to SAP Conversion Easy WAY!

This Solutions is for converting a CAP access point from CLI to SAP..

After logging into the AP....,

1. Enter into Privilege mode

2. Clear already existing configuration.  

ap# clear lwapp private-configuration.

3. Assign Ip address, default gateway to the AP,

ap# capwap ap ip address
ap# capwap ap ip default-gateway

4. Now to upload the IOS give the debug command to access the ‘configuration terminal’,

ap# debug capwap console cli

5. Turn ON the "SolarWinds tftp server" on you PC and in the path of the server keep the IOS image to load for the access point.

6. keep the PC and access point in the same Subnet so that they will be able to communicate... for this we use a dhcp server to avoid disconnections of the Access point. 

we will use "Tftpd32" as a dhcp server 

******click here for Tftpd download ******

To configure Dhcp in Tftpd32,

- Click on "DHCP server" in the tab's when you open tftpd32.



- Select the "settings" button at the bottom.



- You can give the details as mentioned below.



* Only 2 IP's are given for PC and access point.


- Select your LAN network adapter which is connected to the power injector or the switch where the access point is connected.




- Keep you PC and Access point in DHCP mode.
- In a minute you would be able to see the IP's assigned from the server.

- Once the IP's are assigned go back to the AP for further configurations..

7. Enter into the configuration terminal  and type the following command,

ap(config)# archive /download-sw /force-reload /overwrite tftp://.tar

8. After loading the file loads keep the AP will automatically restart.

*Note to keep the PC firewall turned OFF.

 *IF the access point reloads before the complete extraction use tftpd.exe application and configure dhcp server to avoid reload.(cause of reload, the access point will try find the dhcp server automatically).

Rommon Mode conversion in Cisco AP from CAP to SAP.

This solution is for loading IOS in to AP in case of resetting device or converting CAP to SAP in Rommon Mode:



1. Start the Access Point by First pressing the mode button beside the console port and then plugging in the power… 

(OR)

- Open the CLI using a Telnet session or a connection to the access point console port.

- Reboot the access point by removing power and reapplying power.

- Let the access point boot until it begins to inflate the image. When you see these lines on the CLI, press Esc:

Loading "flash:/c1140-k9w7-tar.124-21a.JY.tar" 
...########################################################################### 
################################################################################ 
################################################################################ 
####################

2. When the ap: command prompt appears, enter the set command to assign   an IP address, subnet mask, and default gateway to the access point.

- Clear the flash inatially, to do that..

ap: format flash:

Note - You must use upper-case characters when you enter the IP-ADDR, NETMASK, and DEFAULT_ROUTER options with the set command.

Your entries might look like this example:

ap: set IP_ADDR 192.168.100.100

ap: set NETMASK 255.255.255.0

ap: set DEFAULT_ROUTER 192.168.100.1

3. Enter the tftp_init command to prepare the access point for TFTP.

ap: tftp_init

ap: ether_init

ap: flash_init

4. Enter the tar command to load and inflate the new image from your TFTP server. The command must include this information:

•the -xtract option, which inflates the image when it is loaded

•the IP address of your TFTP server

•the directory on the TFTP server that contains the image

•the name of the image

•the destination for the image (the access point Flash)

Your entry might look like this example:

ap: tar -xtract tftp://192.168.100.101/images/c1140-k9w7-tar.124-21a.JY.tar flash:

5. Enter the set BOOT command to designate the new image as the image   that the access point uses when it reboots. The access point creates a   directory for the image that has the same name as the image, and you   must include the directory in the command. Your entry might look like this 

Example:

ap: set BOOT flash:/c1140-k9w7-tar.124-21a.JY.tar

OR

ap: set BOOT flash:/ c1140-k9w7-tar.124-21a.JY

6. Enter the set command to check your bootloader entries.

ap: set

BOOT=flash:/c1140-k9w7-tar.124-21a.JY

DEFAULT_ROUTER=192.168.100.1

IP_ADDR=192.168.100.100

NETMASK=255.255.255.0

7. Enter the boot command to reboot the access point. When the access point reboots, it loads the new image.

ap: boot

CONFIGURE NTP SERVER FOR WLC

Switch#sh clock

*05:08:16.326 UTC Mon Mar 1 1993

Switch#ping in.pool.ntp.org

Translating "in.pool.ntp.org"...domain server (255.255.255.255) % Name lookup aborted

% Unrecognized host or address, or protocol not running.

CONFIGURE LOOKUP

Switch#

Switch#conf t

Switch(config)#ip domain-lookup

Switch(config)#ip name 8.8.8.8

TESTING

Switch#ping in.pool.ntp.org

Translating "in.pool.ntp.org"...domain server (8.8.8.8) [OK]

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 125.62.193.121, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 34/40/42 ms

Switch#ping 125.62.193.121

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 125.62.193.121, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 42/42/42 ms

CONFIGURING NTP SERVER.

Switch(config)#ntp server in.pool.ntp.org

SETTING TIMEZONE

Switch(config)#clock timezone UTC +5 30

CREATING AUTHENTICATING KEY

Switch(config)#ntp authenticate

Switch(config)#ntp authentication-key 1 md5 123456

Switch(config)#ntp trusted-key 1

Switch(config)#ntp allow mode private

Controller Configuration

1.      Choose Controller > NTP > Servers to open the NTP Servers page. Click New to add an NTP server.

The NTP Servers > New page appears.

2.      Choose a server priority from the Server Index (Priority) drop-down list.

3.      Enter the NTP server IP Address in the Server IPAddress text box.

4.      Enable NTP server authentication by selecting the NTP Server Authentication check box.

5.      Click Apply.

6.      Choose Controller > NTP > Keys.

7.      Click New to create a key.

8.      Enter the key index in the Key Index text box.

9.      Choose the key format from the Key Format drop-down list.

10.  Enter the Key in the Key text box.

Verify

You can use these commands from the WLC CLI to verify the configuration:

(Cisco Controller) >show time

Time............................................. Wed Nov 23 15:31:27 2011

Timezone delta................................... 0:0

Timezone location................................ (GMT -6:00) Central Time (US and Canada)

NTP Servers

    NTP Polling Interval.........................     86400

     Index     NTP Key Index     NTP Server      NTP Msg Auth Status

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

       1              1        10.78.177.30       AUTH SUCCESS

Troubleshoot

You can use the debug ntp detail enable command to view the sequence of events that occur once the NTP server configuration is done on the WLC.

*sntpReceiveTask: Nov 23 15:08:24.360: Started=3531049704.360568 2011 Nov 23 15:08:24.360

*sntpReceiveTask: Nov 23 15:08:24.360: Looking for the socket addresses

*sntpReceiveTask: Nov 23 15:08:24.360: NTP Polling cycle: accepts=0, count=5, attempts=1, retriesPerHost=6.

 Outgoing packet on NTP Server on socket 0:

*sntpReceiveTask: Nov 23 15:08:24.360: sta=0 ver=3 mod=3 str=15 pol=8 dis=0.000000 ref=0.000000

*sntpReceiveTask: Nov 23 15:08:24.361: ori=0.000000 rec=0.000000

*sntpReceiveTask: Nov 23 15:08:24.361: tra=3531049704.360889 cur=3531049704.360889

*sntpReceiveTask: Nov 23 15:08:24.361: Host Supports NTP authentication with Key Id = 1

*sntpReceiveTask: Nov 23 15:08:24.361: NTP Auth Key Id = 1 Key Length = 5

*sntpReceiveTask: Nov 23 15:08:24.361: MD5 Hash and Key Id added in NTP Tx packet

*sntpReceiveTask: Nov 23 15:08:24.361: Flushing outstanding packets

*sntpReceiveTask: Nov 23 15:08:24.361: Flushed 0 packets totalling 0 bytes

*sntpReceiveTask: Nov 23 15:08:24.361: Packet of length 68 sent to 10.78.177.30 UDPport=123

*sntpReceiveTask: Nov 23 15:08:24.363: Packet of length 68 received from 10.78.177.30 UDPport=123

*sntpReceiveTask: Nov 23 15:08:24.363: KeyId In Recieved NTP Packet 1

*sntpReceiveTask: Nov 23 15:08:24.363: KeyId 1 found in recieved NTP packet exists as part of the trusted Key/s

*sntpReceiveTask: Nov 23 15:08:24.363: The NTP trusted Key Id  1 length = 5

*sntpReceiveTask: Nov 23 15:08:24.363: NTP Message Authentication - SUCCESS

*sntpReceiveTask: Nov 23 15:08:24.363: sta=0 ver=3 mod=4 str=8 pol=8 dis=3.875031 ref=3531071269.384065

*sntpReceiveTask: Nov 23 15:08:24.363: ori=3531049704.360889 rec=3531071270.103183