cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3159
Views
10
Helpful
7
Replies

CAP can't enter static IP address: WLC 2504 ver_8.5.135 to CAP3602I ver_15.3(3)JF8

I've tried everything but I can get the CAP to keep a static ip address.  I've entered it the WLC GUI from the panel shown below, bottom right, from the WLC CLI [(Cisco Controller) >config ap static-IP enable AP1 192.168.170.100 255.255.255.0 192.168.170.1], and from the CAP CLI [# capwap ap ip address 192.168.170.100 255.255.255.0 etc for GW and Prim_Controller].  After reload, it always defaults to 169.254.1.1 but keeps the Fallback Ipv4 192.168.170.100.  But it will not connect to the WLC, after a reboot, until I enter at the CAP "# capwap ap ip address 192.168.170.100 255.255.255.0"

Also the WLC will not work on management vlan 111, it has to be set to vlan 0?

Wireless_CAP_issue.png

1 Accepted Solution

Accepted Solutions

Hi clyde.a.huffman.ctr@mail.mil 

From the AP set the ip to BVI interface.

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

View solution in original post

7 Replies 7

This is what happens when I restart either the WLC or the CAP to force the CAP to connect - note that the WLC GUI will show 169.154.1.1 GW 169.254.1.254.

AP1#sh capwap ip config

LWAPP Static IP Configuration
IP Address 192.168.170.101
IP netmask 255.255.255.0
Default Gateway 192.168.170.1
Primary Controller 192.168.170.1

AP1#capwap ap ip address 192.168.170.101 255.255.255.0
You should configure Domain and Name Server from controller CLI/GUI.
AP1#
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
AP1#

*Aug 29 13:48:13.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.170.70 peer_port: 5246
*Aug 29 13:48:13.391: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.170.70 peer_port: 5246
*Aug 29 13:48:13.391: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.170.70
*Aug 29 13:48:13.495: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to channel change from 11 to 11
*Aug 29 13:48:13.499: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug 29 13:48:13.507: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 29 13:48:14.123: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to channel change from 36 to 36
*Aug 29 13:48:14.123: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to interface reset
*Aug 29 13:48:14.131: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WLC2504
*Aug 29 13:48:14.183: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 29 13:48:14.291: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
*Aug 29 13:48:14.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug 29 13:48:14.535: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Aug 29 13:48:14.539: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to completion of off channel transmission
*Aug 29 13:48:14.543: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug 29 13:48:14.551: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 29 13:48:15.183: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Aug 29 13:48:15.571: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 29 13:48:15.579: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Aug 29 13:48:16.571: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Aug 29 13:48:16.607: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Aug 29 13:48:17.607: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Aug 29 13:48:34.627: %CLEANAIR-6-STATE: Slot 0 disabled
*Aug 29 13:48:34.627: %CLEANAIR-6-STATE: Slot 1 disabled

AP1#sh capwap ip config

LWAPP Static IP Configuration
IP Address 192.168.170.101
IP netmask 255.255.255.0
Default Gateway 192.168.170.1
Primary Controller 192.168.170.1

AP1#

Hi clyde.a.huffman.ctr@mail.mil 

From the AP set the ip to BVI interface.

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

Hi Daniel, thanks for answering.  I was looking for a way to enter a BVI ip configuration.  There are so many types of Cisco access points with different commands.... II found "show ip interface bvi1".... Do you know how to configure BVI with CLI commands?

 

This worked!! # capwap ap easy-config done

 

I need to learn more about BVI bridge interface because I'd like to move management to vlan 200 and keep the WiFi on vlan 111.

 

Hi clyde.a.huffman.ctr@mail.mil 

 

Glad to heard it works. btw I love your topology.

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

Thanks Daniel, Thanks for your positive feedback.  I'm learning and finally comfortable with the 2504 WLC setup that I have, but there is another thing that I'd like to learn.  How to put the management port on a different vlan (office network) and the guest network vlan on another 2504 port.  The idea is to disable guest network access to the http GUI.  SSH to the WLC would still work from the guest network, but for some strange reason, I trust SSH more than the http GUI?????

 

I'm sure that it has to do with setting up bridge interfaces.... But I don't understand them very well yet. 

Most common way of configuring it as "trunk port" on switch end (where WLC connects) & allow wireless vlans across that trunk. . Typically connect both ports of 2504 and act as channel group (mode on as WLC does not support LACP/PAgP )

 

You should disable "Management Via Wireless" under Management tab (This should be disabled by default). In that way you cannot access WLC GUI/CLI from wireless subnets.

 

HTH

Rasika

 

Thanks Rasika, just disabled wireless http access :-)  I appreciate your help.  Allan

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: