Cisco 4400 - 100 WLC ap manager IP address

I am going to implement a Cisco 4400-100 WLC. I need it to manage 100 Cisco LWAPP AP's
Can this be done with one AP Manager IP address?
Is it recommended to have the AP manager and manager address on the same subnet?
How many of the 4 fibre connectors need to be used to manage 100 AP's?
Mark Cronin

ok, you have 2 options one is work with AP MANAGER interfaces and the other is to work with LAG, whe LAG is enable you just need one AP MANAGER interface becouse the LAG makes the redundancy and load balancing function.
checkout this link:
http://cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html
In this section:
Using Link Aggregation (LAG)

Similar Messages

2 x Cisco 4400 series WLC to provide redundancy

Hi all,
can any one point me in the direction of some resources so that I can get a better understanding of configuring 2 4400's in a redundancy group?
I've got experience with the HP wireless module kits in a redundancy group, any one know whether the cisco stuff works in the same sort of way??
Mario

Here are a few docs that should help.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml
http://www.cisco.com/en/US/docs/wireless/controller/6.0/configuration/guide/c60mobil.html

Wanted to Know more about cisco 4400 WLC

is cisco 4400 WLC support third party access points or not
i have coral-maksat.

Hi Tahseen,
Not at this point in time. But this type of 3rd party support will be added in the future;
In controller software release 5.2 or later, Cisco lightweight access points use the IETF standard Control and Provisioning of Wireless Access Points protocol (CAPWAP) in order to communicate between the controller and other lightweight access points on the network. Controller software releases prior to 5.2 use the Lightweight Access Point Protocol (LWAPP) for these communications.
CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a controller to manage a collection of wireless access points. CAPWAP is being implemented in controller software release 5.2 for these reasons:
To provide an upgrade path from Cisco products that use LWAPP to next-generation Cisco products that use CAPWAP
To manage RFID readers and similar devices
***To enable controllers to interoperate with third-party access points in the future
LWAPP-enabled access points can discover and join a CAPWAP controller, and conversion to a CAPWAP controller is seamless. For example, the controller discovery process and the firmware downloading process when you use CAPWAP are the same as when you use LWAPP. The one exception is for Layer 2 deployments, which are not supported by CAPWAP.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008064a991.shtml
Hope this helps!
Rob

WLAN Clients not browsing on Cisco Wireless Controller WLC NME-AIR-WLC12-K9

HiI have a question and i need a solution and expert help.I have done a deployment which involves Security (ASA5540), Routing/voice gateway/wlc NME-AIR-WLC12-k9) and Switching (Cisco3845-ccme/k9)Below is the list of equipment used:1. Cisco ASA 5540 - which is connected at the edge to the ISP router
2. Core Switch WS-C4948E as core and DHCP Server for all VLANs
3. Access/Distribution Switches WS-C3560G-48PS-S connected as trunk to the core switch
4. Router/Voice Gateway/WLC Cisco3845-CCME/K9 - This is the voice gateway and also the WLC
5. Wireless APs AIR-LAP1242AG-E-K9 (12 qty)Here is the deployment scenario:1. G0/0 of the ASA is connected to a 7200 router from the ISP (Public IP Add)
2. G0/1 of the ASA is connected to gig 1/3 on the Core Switch on VLAN 2 which is the management VLAN (Local IP 10.1.1.2)
3. Port 3 of the Core switch is on vlan 2 connected to ASA - Management IP of Core Switch is 10.1.1.1. Core Switch is the DHCP Server for all VLANS on the network.
4. All the Access/Distribution switches are configured with IP Addresses on VLAN 2
5. Telephony Services is configured on the router and DHCP Pool for Access Points and Wireless Clients is running on the router.
6. Two DHCP pools were created on the router for APs and Wireless Clients.
7. G0/0 of the router is configured on the same network that issues dhcp ip to the AP and is connected to gig 1/1 on the core switch
8 G0/1 of the router is configured as the voice port for the IP Telephony Services and is connected to G 1/2 on the core switch1. Clients receiving DHCP IP on the Core Switch can communicate with all vlans and can browse to the Internet.
2. IP Telephony Services is running well.
3. Client on wireless can get IP from the DHCP on the router but cannot browse.I have pings from the router to the core switch and firewall, but clients connected to the wireless
cannot ping other vlans on the core switch and vice versa.The port connecting the router to the core switch is an Access Port, i have changed to to trunk but still no changes.My biggest problem now is how to make the clients on the wireless communicate with other clients on the network and be able to browse to the Internet.Below is the configs on the router and core switch.Router ConfigNimc_Voice_Router#sh run
Building configuration...
Current configuration : 10513 bytes
! Last configuration change at 13:03:55 Nigeria Mon Nov 29 2010 by admin
! NVRAM config last updated at 13:03:56 Nigeria Mon Nov 29 2010 by admin
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Nimc_Voice_Router
boot-start-marker
boot-end-marker
! card type command needed for slot/vwic-slot 0/2
logging message-counter syslog
enable secret
aaa new-model
! aaa authentication login default local
aaa session-id common
clock timezone Nigeria 1
dot11 syslog
ip source-route
ip dhcp excluded-address 10.1.12.1 10.1.12.10
ip dhcp excluded-address 192.168.1.1 192.168.1.10
ip dhcp pool LWAAP-AP
network 10.1.12.0 255.255.255.0
default-router 10.1.12.1
option 43 hex f104.c0a8.0002
dns-server 83.229.88.30 4.2.2.2 193.238.28.249
option 60 ascii "Cisco AP c1240"
ip dhcp pool Wireless
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
ip cef
no ip domain lookup
ip domain name nimc.gov.ng
ip name-server 83.229.88.30
ip name-server 193.238.28.249
ip name-server 4.2.2.2
no ipv6 cef
multilink bundle-name authenticated
voice-card 0
archive
log config
hidekeys
interface GigabitEthernet0/0
description Connection to AP
ip address 10.1.12.1 255.255.255.0
ip helper-address 192.168.0.2
load-interval 30
duplex auto
speed auto
media-type rj45
interface Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/1
ip address 10.1.2.2 255.255.255.0
duplex auto
speed auto
media-type rj45
interface FastEthernet0/0/0
no ip address
shutdown
duplex auto
speed auto
interface Serial0/1/0
no ip address
shutdown
no fair-queue
clock rate 2000000
interface Serial0/1/1
no ip address
shutdown
clock rate 2000000
interface Integrated-Service-Engine1/0
ip address 192.168.0.1 255.255.255.0
no keepalive
interface Integrated-Service-Engine1/0.15
encapsulation dot1Q 15
ip address 192.168.1.1 255.255.255.0
interface Integrated-Service-Engine1/0.100
encapsulation dot1Q 100
ip forward-protocol nd
ip forward-protocol udp 12223
ip route 10.1.0.0 255.255.255.0 10.1.1.1
ip route 10.1.1.0 255.255.255.0 10.1.1.1
ip route 10.1.2.0 255.255.255.0 10.1.1.1
ip route 10.1.3.0 255.255.255.0 10.1.1.1
ip route 10.1.4.0 255.255.255.0 10.1.1.1
ip route 10.1.5.0 255.255.255.0 10.1.1.1
ip route 10.1.6.0 255.255.255.0 10.1.1.1
ip route 10.1.7.0 255.255.255.0 10.1.1.1
ip route 10.1.8.0 255.255.255.0 10.1.1.1
ip route 10.1.9.0 255.255.255.0 10.1.1.1
ip route 10.1.10.0 255.255.255.0 10.1.1.1
ip route 10.1.11.0 255.255.255.0 10.1.1.1
ip route 10.1.12.0 255.255.255.0 10.1.1.1
ip route 192.168.0.0 255.255.255.0 10.1.1.1
ip route 192.168.1.0 255.255.255.0 10.1.1.1
no ip http server
ip http secure-server
!Core Switch Configsh run
Building configuration...Current configuration : 10622 bytes
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
service compress-config
hostname Nimc_Core
boot-start-marker
boot-end-marker!
aaa new-model
aaa authentication login default local
aaa session-id common
storm-control broadcast include multicast
ip subnet-zero
no ip domain-lookup
ip domain-name nimc.gov.ng
ip dhcp excluded-address 10.1.2.1 10.1.2.10
ip dhcp excluded-address 10.1.4.1 10.1.4.10
ip dhcp excluded-address 10.1.5.1 10.1.5.10
ip dhcp excluded-address 10.1.6.1 10.1.6.10
ip dhcp excluded-address 10.1.7.1 10.1.7.10
ip dhcp excluded-address 10.1.8.1 10.1.8.10
ip dhcp excluded-address 10.1.9.1 10.1.9.10
ip dhcp excluded-address 10.1.10.1 10.1.10.10
ip dhcp excluded-address 10.1.3.1 10.1.3.10
ip dhcp pool Voice
network 10.1.2.0 255.255.255.0
next-server 10.1.2.1
option 150 ip 10.1.2.2
default-router 10.1.2.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
ip dhcp pool SF_DGs_Office
network 10.1.3.0 255.255.255.0
domain-name nimc.gov.ng
default-router 10.1.3.1
dns-server 81.199.3.7
lease 10
ip dhcp pool Admin_Process_Fac_Mgt
network 10.1.4.0 255.255.255.0
domain-name nimc.gov.ng
default-router 10.1.4.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
lease 10
ip dhcp pool SF_IDD
network 10.1.5.0 255.255.255.0
domain-name nimc.gov.ng
default-router 10.1.5.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
lease 10
ip dhcp pool Finance_Fin_Inv
network 10.1.6.0 255.255.255.0
domain-name nimc.gov.ng
default-router 10.1.6.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
lease 10
ip dhcp pool Finance_CS
network 10.1.7.0 255.255.255.0
domain-name nimc.gov.ng
default-router 10.1.7.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
lease 10
ip dhcp pool FF_Human_Capital_Mgt
network 10.1.8.0 255.255.255.0
domain-name nimc.gov.ng
default-router 10.1.8.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
lease 10
ip dhcp pool FF_Legal_Services
network 10.1.9.0 255.255.255.0
domain-name nimc.gov.ng
default-router 10.1.9.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
lease 10
ip dhcp pool SF_Procurement_Serv
network 10.1.10.0 255.255.255.0
domain-name nimc.gov.ng
default-router 10.1.10.1
dns-server 83.229.88.30 193.238.28.249 4.2.2.2
lease 10
ip vrf mgmtVrf
errdisable recovery cause bpduguard
errdisable recovery interval 180
power redundancy-mode redundant
spanning-tree mode mst
spanning-tree portfast bpduguard default
spanning-tree extend system-id
spanning-tree mst configuration
name xxxx
revision 1
instance 1 vlan 1-20
spanning-tree mst 1 priority 0
spanning-tree vlan 1-20 priority 0
vlan internal allocation policy ascending
interface FastEthernet1
ip vrf forwarding mgmtVrf
no ip address
speed auto
duplex auto
interface GigabitEthernet1/1
switchport trunk encapsulation dot1q
switchport mode trunk
interface GigabitEthernet1/2
switchport access vlan 4
switchport mode access
spanning-tree portfast
interface GigabitEthernet1/3
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/4
switchport mode access
spanning-tree portfast
interface GigabitEthernet1/5
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/6
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/7
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/8
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast!
interface GigabitEthernet1/9
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/10
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/11
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/12
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/13
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/14
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/15
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/16
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/17
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/18
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/19
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/20
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/21
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/22
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/23
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/24
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/25
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/26
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/27
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/28
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/29
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/30
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/31
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfastinterface GigabitEthernet1/32
switchport access vlan 2
switchport voice vlan 4
interface GigabitEthernet1/33
switchport mode access
interface GigabitEthernet1/34
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/35
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/36
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/37
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/38
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/39
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/40
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/41
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/42
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/43
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/44
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/45
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/46
switchport access vlan 2
switchport mode access
switchport voice vlan 4
spanning-tree portfast
interface GigabitEthernet1/47
switchport trunk encapsulation dot1q
switchport mode trunk
interface GigabitEthernet1/48
switchport trunk encapsulation dot1q
switchport mode trunk
interface Vlan1
no ip address
shutdown
interface Vlan2
description Management
ip address 10.1.1.1 255.255.255.0
interface Vlan3
description Enterprise
ip address 10.1.0.1 255.255.255.0
interface Vlan4
description Voice
ip address 10.1.2.1 255.255.255.0
interface Vlan5
description SS_DGs_Office
ip address 10.1.3.1 255.255.255.0
interface Vlan6
description Admin_Process_Fac_Management
ip address 10.1.4.1 255.255.255.0
interface Vlan7
description SF_National_Identity_Database
ip address 10.1.5.1 255.255.255.0
interface Vlan8
description Fin_Finance_Investment
ip address 10.1.6.1 255.255.255.0
interface Vlan9
description Fin_Corporate_Services
ip address 10.1.7.1 255.255.255.0
interface Vlan10
description FF_Human_Capital_Management
ip address 10.1.8.1 255.255.255.0
interface Vlan11
description FF_Legal_services
ip address 10.1.9.1 255.255.255.0
interface Vlan12
description SF_Procurement_Services
ip address 10.1.10.1 255.255.255.0
ip default-gateway 10.1.1.2
ip route 0.0.0.0 0.0.0.0 10.1.1.2
ip route 10.1.1.0 255.255.255.0 10.1.1.2
ip route 10.1.2.0 255.255.255.0 10.1.1.2
ip route 10.1.3.0 255.255.255.0 10.1.1.2
ip route 10.1.4.0 255.255.255.0 10.1.1.2
ip route 10.1.5.0 255.255.255.0 10.1.1.2
ip route 10.1.6.0 255.255.255.0 10.1.1.2
ip route 10.1.7.0 255.255.255.0 10.1.1.2
ip route 10.1.8.0 255.255.255.0 10.1.1.2
ip route 10.1.9.0 255.255.255.0 10.1.1.2
ip route 10.1.10.0 255.255.255.0 10.1.1.2
ip route 10.1.11.0 255.255.255.0 10.1.1.2
ip http server
--More--
control-plane
line con 0
stopbits 1
line vty 0 4
end
Please i need somebody to help me

I wouldn't configure an ip address on the service engine subinterface.
Try setting up a vlan interface on the router with that ip address and the subinterface will be linked to the vlan interface through the encapsulation command. A vlan interface will better work as a gateway for the wireless clients
Nicolas

Cisco 4400 summary page doesn't display proper # of active AP's

4400 series WLC with 100 supported AP's.
present capacity is 62 active AP's but summary only shows 48 active...Why???????

I'm sure this has been figured out by now, but just in case it hasn't, or the solution was unclear, you probably only have one of the controller's gigabit interfaces plugged in, or you don't have enough ap-managers configured. For more than 48 APs, you need more than one link connected. If you are using LAG, you should be all set with one ap-manager. If you are not using LAG, you need to connect at least two ports for 62 APs, and you will need a second ap-manager IP address configured.
Regards,
Scott

No more AP manager IP address remain

I have a few AP's that were working fine, had some power issues and they went offline. Now they will not reassociate with the controllers. I keep getting this error message.
*Mar 1 00:00:38.955: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLL
ER
*Mar 1 00:00:48.959: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar 1 00:00:48.959: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 1 00:00:48.960: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Mar 1 00:00:55.959: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join respon
se
*Mar 1 00:00:55.959: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
*Mar 1 00:01:00.963: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join respon
se
*Mar 1 00:01:00.963: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
*Mar 1 00:01:01.025: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JO
IN RESPONSE.
*Mar 1 00:01:01.025: %LWAPP-5-CHANGED: LWAPP changed state to DOWN
Any suggestions or ideas would be appreciated.

A normal LWAPP discovery/join exchange between a WLC and AP looks like this:
1. AP sends LWAPP Discovery Request to WLC
2. WLC sends LWAPP Discovery Response to AP
3. AP sends LWAPP Join Request to WLC
4. WLC sends LWAPP Join Response to AP
If you follow the log messages, you can see the AP never got the LWAPP Join Response from the WLC. The log message "No more AP manager IP addresses remain" indicates the AP has exhausted it's candidate controller list and received no LWAPP Join Responses.
So, now you have to figure out why. You might take a swag and check the date/time on your controller is current. If it's defaulted, your AP certificates will be out of the valid date/time range and so the WLC won't validate them.
I'd start by running the following debug on your AP:
debug lwapp client event
That'll tell you that the AP is sending out the LWAPP Join Request to the right controller. If it's not, then you have to investigate what's going with the discovery phase.
Next, check that the LWAPP Join Request is arriving at your controller. At your controller console:
debug lwapp events enable
You should see a message that indicates the LWAPP Join Request has arrived from your AP. It'll also tell you if it sends an LWAPP Join Response.
The point is just walk through the LWAPP state machine and find the point where it's failing.
HTH...

Ap-manager ip address is not reachable

Hi,
we have Cisco 4402 Wireless LAN standalone controller, we recently upgraded the firmware from 4.0.155.0 to 4.0.179.11.
with new image we are unable to ping manager ip address but unable to ping ap-manager ip address. however both manager an d ap-manager interfaces are in same subnet.
Please help me any one face this type of problem.
Thanking you,
Regards,
Ranga Kishore
9959344436

That is normal behavior.

Management ip address on a different vlan/bridge

We have several standalone AP's. On our switches we have a data and a guest vlan. Perviously on Aironet AP I configured the ethernet interface with 802.1q trunking and I configure a subinterface with its management ip address. This all worked perfectly.
No we bought some new one's (SAP2602) which has ios v15.2 (the old ones still have 14.3) and I applied the same config (changed the ip address and hostname of course), but the ip management of the AP does not work (Wireless clients works good, so no problem with 802.1q)
COnfig (so both on old and new):
bridge irb
Interface GigabitEthernet0
no ip address
no ip route-cache
duplex full
speed 100
no keepalive
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface GigabitEthernet0.90
encapsulation dot1Q 90
no ip route-cache
bridge-group 90
no bridge-group 90 source-learning
bridge-group 90 spanning-disabled
interface GigabitEthernet0.104
encapsulation dot1Q 104
ip address 10.104.70.1 255.255.0.0
no ip route-cache
bridge-group 104
no bridge-group 104 source-learning
bridge-group 104 spanning-disabled
interface BVI1
ip address dhcp client-id GigabitEthernet0
no ip route-cache
ip default-gateway 10.104.1.1
Any ideas what's changed between new and old IOS or AP? (I only noticed that in the new AP the command "no ip route-cache") is not enabled anymore.

I'd suggest to define vlan114 as native vlan and change the bridge group to 1
interface GigabitEthernet0.104
encapsulation dot1Q 104 native
bridge-group1
Remember to configure the trunk port the ap is connected as native vlan 104.
Normally the ip address is configured under bvi interface,if still no change you can try it.
That should work.
Regards

DMP 4400G RS 232 connection with Cisco LCD 100 PRO 40N

Hi everyone,
I know that this question was kinda asked before, but I still have trouble setting the DMM to control the Cisco LCD 100 PRO 40N (Samsung) through the DMP RS 232 connection!
I have searched and read every post on this forum, tried everything ("Samsung_MDC_RS232_Protocol_Ver-21.pdf" & rs232.tx_hex= ) but with no avail.
We have DMS VmWare Demo (Signs&Cast 5.2, Show and Share 5.2) and 4400G with 5.2 firmware.
Also, I've connected the Serial RS232 9-Pin Female to Female that came with the TV onto the DMP 4400G and into the TV RS232 IN port, configured the DMP Display Control in the Advance Task tab as you can see from the attach picture, and set the TV type to Cisco 40N and Power ON and another task for Display OFF. What am I doing wrong here!?
Any input will be greatly appriciated!

With DMS 5.2, this pretty straight forward as your JPEG attachment shows.
Take a look at the documentation...
There may have been some steps you missed...
For 5.1 & 5.2....
http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_1/dmm/user/guide/dsm+etv.html#wp1718477
* Connect RS-232 cable to the DMP and the LCD.
I believe either RS-232 port should work for the LCD. I thought the FRONT port (closet to front of TV)
was an IN\OUT port. And the BACK port was just an IN port. I used the BACK port for my testing.
* next, you NEED to ENABLE ON RS-232 controls on the DMP first. From the DMM, issue the
"Advanced Task--> System Task --> RS-232: Control Supported, non-DMTech displays" for the DMP(s)
in question. By default, RS-232 controls are disabled.
* Create 2 new System Tasks in the Advanced Tasks Tab.
Turn ON - Cisco LCD = rs232.tx_hex=aa11fe010111
Turn OFF - Cisco LCD = rs232.tx_hex=aa11fe010010
* Once RS-232 Control is Enabled & the New System Tasks are created, You can now issue the LCD Turn On & Off
tasks from the DMM-DSM DMP Manager.
Note: You can combine RS-232 commands using the "Control TV" tool on the DMP Manager List Zone. The "Control TV"
is designated by the TV with Antenna Icons in the DMP List Tool bar.
If this answers your question, Please take time to mark thisdiscussion answered & rate the response.
Thank You!
T.

Block IPs from accessing WLC web management

Hi all,
I have tried using access control list to block certain IPs from accessing WLC web management. I apply the ACL to interface management, but it seems like no effect at all.
How can I block or permit some IPs so only certain IPs can access WLC web management ?
Thanks in advance.

I need deal with this matter also... So here's what I found:
- you must use CPU acls - interface acls won't do what you want;
- it appears that once you use an acl, you must explicitly define each type of traffic you want to allow, since an implicit deny all action occurs.
I'm working on trying to restrict admin access to controllers in order address policy compliance matters. I'm disappointed at the lack of better documentation and practical examples on acls...
If anyone can shed some light on this topic I think two of us would appreciate it...

Migrate WLC 4400 to WLC 5500

Hi experts,
I want to Migrate WLC 4400 with WLC 5500, But i don't know how to do this.
Should i create new configuration or use my WLC 4400 config ?
I want to know about IOS for WLC 5500, should I upgrade my Access Point to connect with new WLC ?
I need a good method to migrate this WLC. So my WLC 5500 can run properly.
Thankyou for your help.

I have no idea how Ravi's answer is considered "correct" when he didn't address the most important aspect of your thread.
As far as I'm aware, you need to ensure both controllers are running the same firmware or 7.0.250.X.
Take a copy or export the config of the 4400 configuration to your TFTP server. Edit the file and change the necessary settings. Go to the 5500 and download this configuration file. Upgrade the firmware and the bootstrap if necessary.

Cisco 3750G Integrated WLC upgrade failure

I am trying to upgrade our Cisco 3750G Integrated WLC from version 5 to version 7, at 92% I receive an error
Code file transfer failed - Error while writing output file
There is enough space on WLC,
Total System Memory............: 529088512 bytes
Used System Memory.............: 121180160 bytes
Free System Memory.............: 407908352 bytes
I have tried 2 different TFTP servers..
Any thoughts?

Hi,
1. Is it OK to upgrade to SWLC3750K9-5-2-193-0.aes ? or do I need to go through 4.2 first ?
ANS - Yes you have to upgrade to 4.2 first and then to 5.2, here is the doc..
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn52xgmr1.html#wp233853
2. Will that code upgrade the bootloader at the same time?
ANS - Yes, after upgrading the WLC code upgrade the boot loader.. the boot loader is 5.2.157 (BOOT)
3. How can I make sure there is enough flash space on the WLC?
ANS - Dont worry.. we have enough flash!!
4. Are there any special considerations to plan/prepare for?
ANS - Yes, please upgrade the WLC in a planned , scheduled maitenance window.
The DHCP issue is failure of associated clients to get an IP address with this message found in WLC debugging:
Wed Jul 20 17:16:37 2011: 00:19:db:5b:38:73 dhcpProxy: Dropping packet (no mscb) from STA 00:19:db:5b:38:73, giaddr:0.0.0.0, udpSrcPort:68, op:1
ANS - Issue the command ans see if that helps!!
WLC CLI access...
config dhcp proxy disable
Lemme know if this answered ur question and please dont forget to rate the usefull posts!!
Regards
Surendra

Cisco's AnyConnect Network Access Manager (NAM)

Hi dears,
I configurate EAP_FAST in Cisco ISE and want wired users authenticate from ISE. I install Network Access Manager Profile Editor and Cisco Anyconnect Security Mobility Client on PC. I configure Network Access Manager when i want to save as that I did not see the . \newConfigFiles folder. Then I did that: Organize’, ‘Folder and Search Options’, ‘Show hidden files, folders, and drives. but in this case i did see the network access manager folder.
I need a to install Cisco’s AnyConnect Network Access Manager (NAM) on PC. HOW I get this soft? I have a smartnet for ISE.
Which email address(to cisco) i must be write to get this soft?
Thanks.

You can download the Network Access Manager module from CCO. This link should work if you have a CCO account.
http://software.cisco.com/download/release.html?mdfid=283000185&softwareid=282364313&release=3.1.05160&relind=AVAILABLE&rellifecycle=&reltype=latest&i=rs
The file name will be similar to anyconnect-win-3.1.05160-pre-deploy-k9.iso. Just unzip the ISO with 7zip or Winrar and you will see the NAM msi file anyconnect-nam-win-3.1.05149-k9.msi.

Hide AP Management IP Address

I'm looking for a command that will hide the management IP address from clients. Currently with my Intel PROSet/Wireless I'm able to get the access point name and IP address that I'm connected to. I would like to turn that off if possible.

That put me in the right direction, thanks. We don't use the web interface so for the CLI, we had to pick the interface and do a 'no dot11 extension aironet'
Thanks.

Assign management ip address with SCVMM 2012 R2 for hyper-v converged network?

Hi,
I am setting up a converged network for our Hyper-V clusters using vNICs for the different network traffic including management, live migration, cluster-csv, hyper-v etc.
Problem is, how do I assign the hyper-v hosts a management IP address? They need a network connection on the management network for scvmm to manage them in the first place. How do I take the existing management IP address that is directly assigned to the
host and transfer it directly to the new vNIC so scvmm has management of it? Kind of in a chicken and egg situation here. I thought about assigning a temp ip address to the host initially but am worried that assigning the address will cause problems as then
the host would then have 2 default gateways configured. How have others managed this scenario?
Thanks
Microsoft Partner

Rule of thumb: Use one connected network for your Fabric networks (read the whitepaper), and use VLAN based networks for your tenant VMs when you want to associate VM Networks with each VLAN.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )
We don't have tenants as such due to this being an environment on a private company LAN for sole use of the company virtual machines.
What I have so far:
I created "one connected network" for Hyper-V-Virtual-Machine traffic.
Unchecked "Allow new VM networks created on this logical switch to use network virtualization"
Checked "Create a VM network with the same name to allow vms to access this logical network directly"
This logical network has one site called UK.
Within this site I have defined all of the different VLANS for this site.
Created IP pools for each VLAN subnet range.
I hope I understand this correctly. Started reading the whitepaper from cover to cover now.
Microsoft Partner

Cisco 4400 - 100 WLC ap manager IP address

Similar Messages

Maybe you are looking for