Connecting a WLC 4400 to a 2960 POE Catalyst

                   I need some help connecting my WLC 4400 to my 2960 catalyst switch. The gigabit port
on the Catalyst switch I am using is connected to port 1 on WLC 4400. I have the port set to trunking
mode but I cannot ping the management interface IP. I also noticed the activity lights on the two interfaces
are not lit. 
interface GigabitEthernet0/2
switchport mode trunk
Is there something else I need to attribute to this port?
Thanks

Sorry to get back to you so late. Here is what I got.
Wireless#sh ip int brief gi0/2
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/2 unassigned YES unset down down
Wireless#sh ip int gi0/2
GigabitEthernet0/2 is down, line protocol is down
Inbound access list is not set
It is plugged in.

Similar Messages

  • Troubleshoot Cisco Airlap 1242 with WLC 4400 Series LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response

    I have a Problem with my new AIRLAP 1242 to connect with WLC 4400
    after debug in my airlap it shows :
    Reset done!
    ethernet link up, 100 mbps, full-duplex
    Ethernet port 0 initialized: link is up
    Loading "flash:/c1240-k9w8-mx.123-7.JX8/c1240-k9w8-mx.123-7.JX8"...######################################################################################################################################################################################################################################
    File "flash:/c1240-k9w8-mx.123-7.JX8/c1240-k9w8-mx.123-7.JX8" uncompressed and installed, entry point: 0x3000
    executing...
                  Restricted Rights Legend
    Use, duplication, or disclosure by the Government is
    subject to restrictions as set forth in subparagraph
    (c) of the Commercial Computer Software - Restricted
    Rights clause at FAR sec. 52.227-19 and subparagraph
    (c) (1) (ii) of the Rights in Technical Data and Computer
    Software clause at DFARS sec. 252.227-7013.
               cisco Systems, Inc.
               170 West Tasman Drive
               San Jose, California 95134-1706
    Cisco IOS Software, C1240 Software (C1240-K9W8-M), Version 12.3(7)JX8, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2007 by Cisco Systems, Inc.
    Compiled Mon 19-Mar-07 01:42 by hqluong
    Image text-base: 0x00003000, data-base: 0x004051E0
    Initializing flashfs...
    flashfs[1]: 9 files, 3 directories
    flashfs[1]: 0 orphaned files, 0 orphaned directories
    flashfs[1]: Total bytes: 15998976
    flashfs[1]: Bytes used: 5062144
    flashfs[1]: Bytes available: 10936832
    flashfs[1]: flashfs fsck took 4 seconds.
    flashfs[1]: Initialization complete....done Initializing flashfs.
    cisco AIR-LAP1242AG-E-K9   (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.
    Processor board ID FCW1411U0FZ
    PowerPCElvis CPU at 266Mhz, revision number 0x0950
    Last reset from power-on
    1 FastEthernet interface
    2 802.11 Radio(s)
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 68:EF:BD:5F:9A:18
    Part Number                          : 73-10256-07
    PCA Assembly Number                  : 800-26918-06
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC14093XU3
    Top Assembly Part Number             : 800-29152-03
    Top Assembly Serial Number           : FCW1411U0FZ
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-LAP1242AG-E-K9
    Press RETURN to get started!
    *Mar  1 00:00:05.608: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
    *Mar  1 00:00:06.858: %DOT11-2-VERSION_INVALID: Interface Dot11Radio0, unable to find required radio version 581.18
    *Mar  1 00:00:06.858: Interface Dot11Radio0, Accepting as a test version of radio firmware
    *Mar  1 00:00:06.878: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
    *Mar  1 00:00:07.234: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
    *Mar  1 00:00:08.212: %DOT11-2-VERSION_INVALID: Interface Dot11Radio1, unable to find required radio version 581.18
    *Mar  1 00:00:08.212: Interface Dot11Radio1, Accepting as a test version of radio firmware
    *Mar  1 00:00:08.232: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
    *Mar  1 00:00:09.278: %SYS-6-LOGGERSTART: Logger process started
    *Mar  1 00:00:09.326: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C1240 Software (C1240-K9W8-M), Version 12.3(7)JX8, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2007 by Cisco Systems, Inc.
    Compiled Mon 19-Mar-07 01:42 by hqluong
    *Mar  1 00:00:09.332: %CDP_PD-4-POWER_OK: Full power - AC_ADAPTOR inline power source
    *Mar  1 00:00:09.388: %DOT11-6-FREQ_SCAN: Interface Dot11Radio0, Scanning frequencies for 32 seconds
    *Mar  1 00:00:10.271: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
    *Mar  1 00:00:10.332: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
    *Mar  1 00:00:10.332: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar  1 00:00:11.271: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
    *Mar  1 00:00:28.331: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    *Mar  1 00:00:28.361: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2462 selected
    *Mar  1 00:00:28.362: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar  1 00:00:28.363: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar  1 00:00:28.369: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5260 selected
    *Mar  1 00:00:28.372: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
    *Mar  1 00:00:28.398: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar  1 00:00:28.399: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
    *Mar  1 00:00:28.465: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
    *Mar  1 00:00:29.398: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar  1 00:00:29.465: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
    Translating "CISCO-LWAPP-CONTROLLER.ekahospital.com"...domain server (202.134.0.155)
    *Mar  1 00:00:38.351: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 172.31.xxx.xxx, mask 255.255.255.0, hostname AP68ef.bd5f.9a18
    *Mar  1 00:00:38.820: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2417 selected
    *Mar  1 00:00:38.827: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5200 selected (203.130.196.5)
    *Mar  1 00:00:49.835: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2422 selected
    *Mar  1 00:00:49.842: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5220 selected
    *Mar  1 00:00:49.851: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
    *Mar  1 00:00:49.852: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Mar  1 00:00:49.852: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
    *Mar  1 00:00:50.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar  1 00:00:50.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
    *Sep 18 07:02:25.504: %LWAPP-5-CHANGED: LWAPP changed state to CFG
    *Sep 18 07:02:29.288: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.MYDOMAIN.com
    *Sep 18 07:02:30.504: LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response
    *Sep 18 07:02:30.551: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET CONFIG RESPONSE.
    *Sep 18 07:02:30.551: %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file system is available.
    flashfs[0]: 9 files, 3 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 15998976
    flashfs[0]: Bytes used: 5062144
    flashfs[0]: Bytes available: 10936832
    flashfs[0]: flashfs fsck took 26 seconds.
    Base ethernet MAC Address: 68:ef:bd:5f:9a:18
    Initializing ethernet port 0...
    Reset ethernet port 0...
    Reset done!
    and after that i check in my WLC that shows
    AP with Base Radio MAC xx:xx:xx:xx:xx:xx (APxxxx.xxxx.xxxx) is unable to associate.
    The reulatory domain configured on it '-e' does not match the controller's country
    code: USA
    i found that the problem about the region.
    question :
    1. is it possible to change the region in AIRLAP 1242 or in WLC?
    2. if possible how to change it?
    INFO :
    my first AIRLAP Product/Model Number : AIR-LAP1242AG-A-K9 and my new AIRLAP Product/Model Number : AIR-LAP1242AG-E-K9

    WLC GUI >> Wireless >> Country >> Select the country.
    Regards
    Surendra

  • WLC 4400 (SW ver: 7.0.235.3) and 1242 AP connectivity issue

    Hi ALL..,
    I got the problem with WLC and APs, APs cannot get IP and can't connect to WLC, it show folloing error,
    *Oct 24 14:45:27.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.2.11 peer_port: 5246
    *Oct 24 14:45:28.000: %CAPWAP-5-CHANGED: CAPWAP changed state to 
    *Oct 24 14:45:29.419: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.11 peer_port: 5246
    *Oct 24 14:45:29.420: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.11
    *Oct 24 14:45:29.420: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
    *Oct 24 14:45:29.595: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
    *Oct 24 14:45:29.602: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.2.11
    *Oct 24 14:45:29.602: %DTLS-5-PEER_DISCONNECT: Peer 192.168.2.11 has closed connection.
    *Oct 24 14:45:29.602: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.2.11:5246
    *Oct 24 14:45:29.661: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Oct 24 14:45:29.661: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Oct 24 14:45:29.756:  status of voice_diag_test from WLC is false
    My Management Int IP : 192.168.2.50
    AP Mangement interface :192.168.2.11
    DHCP server Pri : 192.168.2.12 Sec 192.168.2.13
    There are reachability betweent SW and WLC. Do you have any idea about my issue?
    Thanks and Regards
    CSCO11872447

    It seems your LAP AP is not getting the iP of the management subnet and LAP is in different subnet than your management IP.
    Please try keeping the static IP on the LAP and then try joining it to the controller first and later on keep it on the DHCP.
    when AP is plugged into a switch, the switch port needs to be access with the right VLAN allowed

  • 2960 POE acting as a dhcp server

                       I have a 2960 POE 24 switch acting as a DHCP server
    for a WLC 4402 and six Aironet APs. I cant get the APs to aquire
    an address. At least when I check the switch by doing a sh dhcp
    lease it shows nothing. Here is the commands I used to set it up
    on the switch.
    ip dhcp excluded-address 192.168.50.1 255.255.255.0
    ip dhcp pool wireless
       network 192.168.50.0 255.255.255.0
       domain-name newtonma.gov
       default-router 192.168.50.1
       lease 4
    Here is an example of one of the interfaces
    interface FastEthernet0/1
    switchport trunk native vlan 10
    switchport mode trunk
    The Vlan for wireless
    interface Vlan10
    ip address 192.168.50.1 255.255.255.0
    ip helper-address 192.168.50.1
    no ip route-cache
    Any help would be appreciated

    Hi
    You can remove the helper address as the DHCP server is on the switch itself. A helper address is only needed when the DHCP server is another device than the one the default gateway sits on.
    The interface example you gave above, is that the interface to one of the Access Points or to the WLC?
    Assuming the Access Points are not in Flex Connect mode, they only need to be access ports (i.e not trunks) as the traffic is tunneled back to the WLC.
    The config for each AP would be:
    #interface fa0/1
    #switchport mode access
    #switchport access vlan 10
    The config for the WLC would be:
    #interface fa0/10
    #switchport mode trunk
    I would leave the Native Vlan as 1 (i.e remove the command) or at least change it to something other than Vlan10.
    The DHCP excluded address could be causing an issue as there is no need for a subnet mask if you simply want to exclude a single address.
    #ip dhcp excluded-address 192.168.50.1

  • Wired guest access on WLC 4400 with SW 7.0.240.0

    Hello,
    after we upgrade our Wlan-controller 4400 from software 7.0.116.0 to 7.0.240.0
    wired guest access don't work anymore.
    All other things works fine, incl. WLAN guest access!
    When we try wired guest access, we get the web-authentication page and can log in.
    On the controller we can see that the Policy Manager State changes from WEBAUTH_REQD
    to RUN.
    But then there is no access to the internet.
    We tried also SW 7.0.250.0, same problem!
    Log Analysis on the WCS:
    Time :03/12/2014 14:21:23 MEZ Severity :INFO Controller IP :10.101.200.11 Message :The WLAN to which client is connecting does not require 802 1x authentication.
    Time :03/12/2014 14:21:23 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Client does not have an IP address yet.
    Time :03/12/2014 14:21:23 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Client L3 authentication is required
    Time :03/12/2014 14:21:23 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Client Moved to DHCP Required State.
    Time :03/12/2014 14:21:26 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Mobility role update request. from Unassociated to Local Peer = 0.0.0.0, Old Anchor = 0.0.0.0, New Anchor = 10.101.200.11
    Time :03/12/2014 14:21:26 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Mobility role changed. State Update from Mobility-Incomplete to Mobility-Complete, mobility role=Local, client state=APF_MS_STATE_ASSOCIATED
    Time :03/12/2014 14:21:26 MEZ Severity :INFO Controller IP :10.101.200.11 Message :DHCP successful.
    Time :03/12/2014 14:21:26 MEZ Severity :ERROR Controller IP :10.101.200.11 Message :Client got an IP address successfully and the WLAN requires Web Auth or Web Auth pass through.
    Time :03/12/2014 14:21:26 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Client IP address is assigned.
    Time :03/12/2014 14:22:01 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Webauth user logged in to the network. manni
    Time :03/12/2014 14:22:01 MEZ Severity :INFO Controller IP :10.101.200.11 Message :AAA response message sent.
    Time :03/12/2014 14:22:01 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Client has completed Web Auth successfully.
    Time :03/12/2014 14:22:01 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Client has completed Web Auth successfully.
    Trying http://www.google.de .... doesnt work. No Log Entries. Next entries while logging out.
    Time :03/12/2014 14:36:20 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Web auth is being triggered again.
    Time :03/12/2014 14:36:20 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Client L2 authentication has been completed successfully.
    Time :03/12/2014 14:36:20 MEZ Severity :INFO Controller IP :10.101.200.11 Message :Client Moved to DHCP Required State.
    Time :03/12/2014 14:36:20 MEZ Severity :INFO Controller IP :10.101.200.11 Message :WebAuth user Logged out from network.
    Has someone a idea how to solve this problem?
    Regards
    Manfred

    Hi
    Yes got it resolved. It turns out that the connection from the wired guest access port to the WLC must be L2. That is the switch that the wired guest acces sport is connected and WLC are connected to must be L2 only. We were using a single switch to do the testing and it was also doing the routing for the test LAN. Even though there was no L3 VLAN interface configured for the VLAN that the guest access port was on for some reason this breaks it. Absolu Didnt have chance to work out the exact limitations of this as we simply made the switch L2 only and configured an 802.1Q trunk to the Internet router and made subinterfaces on the router for the wired and wireless egress ports and it worked then. No config change was needed on the WLC at all.
    The only thing I can think of is that it's something about the way the WLC joins the wired guest access ingress VLAn and egress VLAN. The WLC isn't a reall router it says so in the documentation. I think the packet coming from the wired access port is being bridged to the egress VLAn not routed and this is what screws it up (remeber with a router the source and destination MAC addresses would be changed with a bridge they aren't). Got to be something along those lines. If you have a bigger newtork with a guest anchor WLC handling this function you dont run into this as the traffic is coming over an EOIP tunnle from the remote WLC so the switch with the guest anchor WLC doesnt see the MAC address of the wired guest PC.

  • WLC 4400 : some of the clients are stuck in 802.1x REQD ( Auth - no but status is Associated ) in PEM process

    Hi ,
    I have wlc 4400 with 1010 AP's wireless set-up.
    Everything is working fine but unfortunately , I am coming across with one issue that, clients are not getting authenticated.
    If I see the status of respective client  in WLC :
    status : Associated
    Auth : No
    Policy manager : 802.1X REQD
    I read about PEM ( Policy enforcement Module ) , as it is going through same procedure but policy manager should in " RUN " condition , Unfortunately it is not.
    how do i resolve this issue ?

    Hi Vinod,
    The 802.1X_REQD state would suggest that the client cannot complete L2 authentication.
    If possible, it would be helpful to collect the following debugs from the WLC while trying to connect the client:
    debug client
    debug aaa event enable
    Also, please attach the full text output of the command "show run-config" and let us know the WLAN through which the client should be connecting.
    Regards,
    Fede
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • WLC 4400 to WLC 5508

    Hi All
    I want to migrate from WLC 4400 to WLC 5508. currently on WLC 4400 we got 10 AP are connected with 5 SSID having different authentication method. On WLC 5508 If I create the same SSID with same key, will I need to reconfigure anything on end user PC and smart devices
    any tool to migrate wlc 4400 config to wlc 5508
    cheers
    Vishal 

    Thanks Scott, some more inquiry
    how to reboot the AP from the controller. ( I see 'Reset AP' -  this option to reboot or something else)
    how to disconnect all users connected to specific SSID from controller
    Can AP model 3702 work with WLC  5508, do we need specific software version
    cheers
    Vishal

  • Catalyst 2960 POE Consumption

    Hi,
    I've been advised by a third party vendor to put my catalyst 2960 poe switch into consumption mode. Is that possible with this model?
    Thanks,

    This is what you can do:
    Supported Protocols and Standards
    The switch uses these protocols and standards to support PoE:
    •CDP with power consumption—The powered device notifies the switch of the amount of power it is consuming. The switch does not reply to the power-consumption messages. The switch can only supply power to or remove power from the PoE port.
    •Cisco intelligent power management—The powered device and the switch negotiate through power-negotiation CDP messages for an agreed power-consumption level. The negotiation allows a high-power Cisco powered device, which consumes more than 7 W, to operate at its highest power mode. The powered device first boots up in low-power mode, consumes less than 7 W, and negotiates to obtain enough power to operate in high-power mode. The device changes to high-power mode only when it receives confirmation from the switch.
    High-power devices can operate in low-power mode on switches that do not support power-negotiation CDP.
    Cisco intelligent power management is backward-compatible with CDP with power consumption; the switch responds according to the CDP message that it receives. CDP is not supported on third-party powered devices; therefore, the switch uses the IEEE classification to determine the power usage of the device.
    •IEEE 802.3af—The major features of this standard are powered-device discovery, power administration, disconnect detection, and optional powered-device power classification. For more information, see the standard.
    •IEEE 802.3at (Catalyst 2960-S only)—This PoE+ standard supports all the features of 802.1af and increases the maximum power available on each PoE port from 15.4 W to 30 W.
    Powered-Device Detection and Initial Power Allocation
    The switch detects a Cisco pre-standard or an IEEE-compliant powered device when the PoE-capable port is in the no-shutdown state, PoE is enabled (the default), and the connected device is not being powered by an AC adaptor.
    After device detection, the switch determines the device power requirements based on its type:
    •A Cisco pre-standard powered device does not provide its power requirement when the switch detects it, so a Catalyst 2960 switch allocates 15.4 W as the initial allocation for power budgeting; a Catalyst 2960-S switch allocates 30 W (PoE+).
    The initial power allocation is the maximum amount of power that a powered device requires. The switch initially allocates this amount of power when it detects and powers the powered device. As the switch receives CDP messages from the powered device and as the powered device negotiates power levels with the switch through CDP power-negotiation messages, the initial power allocation might be adjusted.
    •The switch classifies the detected IEEE device within a power consumption class. Based on the available power in the power budget, the switch determines if a port can be powered. Table 12-1 lists these levels.
    Table 12-1 IEEE Power Classifications 
    Class
    Maximum Power Level Required from the Switch
    0 (class status unknown)
    15.4 W
    1
    4 W
    2
    7 W
    3
    15.4 W
    4
    30 W (Catalyst 2960-S only)

  • Agregar Aironet 1552e a k9 a una WLC 4400?

    Como puedo agregar 2 access points Aironet 1552e a k9 a una WLC 4400.
    Estan ya instalados y conectados a un switch PoE que va a la WLC 4400 y no los reconocé.

    Es necesario agregar la dirección MAC a la lista de seguridad del controlador.

  • 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.

  • CiscoWorks LMS3.0 doesn't know the 2960 PoE type

    I have several PoE Catalyst 2960 WS-C2960-24PC-L
    When I added them to CiscoWokrs I found out that it doesn't know WS-C2960-24PC-L type.
    As a result they are unknown.
    The list of installed applications:
    1. LMS Portal 1.0.0
    2. CiscoWorks Assistant 1.0.0
    3. CiscoView 6.1.6
    4. CiscoWorks Common Services 3.1.0
    5. Integration Utility 1.7.0
    6. Resource Manager Essentials 4.1.0
    7. Campus Manager 5.0.0
    8. Device Fault Manager 3.0.0
    9. Internetwork Performance Monitor 4.0.0
    How to add WS-C2960-24PC-L to the LMS?
    As I understand I have to update Resource Manager Essentials. Which version should I install ?

    RME 4.1.1, Campus Manager 5.0.3
    Check the doc:
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html
    I understand that is for device :
    Cisco Catalyst 2960-24PC-L Switch
    (WS-C2960-24PC-L)
    with sysobject ID :1.3.6.1.4.1.9.1.950

  • WLC 4400 and multiple authentication servers e.g. RADIUS, ACS

    WLC 4400 and multiple authentication servers e.g. RADIUS, ACS
    Can the WCL 4400 be set up to use multiple RADIUS servers? The user accounts for accessing wireless would use a RADIUS server. The administrative accounts for the WLC would reside on an ACS server.

    Yes, that is correct. You can set acs to use both radius and tacacs.
    For this you need to add WLC twice in acs-->network configuration. But you need to keep host name different.
    eg 1) Host name WLC --->IP x.x.x.x -->Auth using -->radius
    2) Host name WLC1--->IP x.x.x.x --->Auth using -->Tacacs.
    You need to set up tacacs commands on WLC along with radius commands.
    Regards,
    ~JG
    Please rate helpful posts

  • ISE WLC 4400 configuration

    Up until now, my experience has been with 5500 controllers and ISE.
    My customer is using 4400 controller, on 7.0.240 code.
    I cannot locate any documents referencing 4400 controller configuration for webauth, named ACLs, posturing, etc...
    Does anyone know of any documents, or have experience that can assist with this configuration?

    Michael,
    Depending on the version of ISE software you are running, you may be in luck.  The information below is for 1.1.x.  If you are using v 1.2, you may have to tweak a bit.
    In this first document, you can see the WLC 4400 is supported and Local Web Auth is supported, with the following caveat:  “Wireless (An ISE Inline Posture node is required if the WLC does not support CoA as discussed in Footnote #4. WLCs with the code specified in this table do support CoA without an ISE Inline Posture node)”
    http://www.cisco.com/en/US/docs/security/ise/1.1/compatibility/ise_sdt.html#wp55038
    Of course, with an IPN, your posturing  (and CoA) is handled here.
    DACLs are also supported on the WLC 4400.
    Per User ACLs are covered in the following document:
    http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a00808b041e.shtml
    I think you will find that if you substitute the ACS pages with the corresponding ISE interface pages, this can be done.
    Please feel free to ask any additional or follow-up questions.
    Also, please let me know if this fixes your issue.  If it does, please rate this answer and mark your question as Answered.
    Charles Moreton

  • WLC 4400 and IDS attacks

    Hi,
    I have a WLC 4400 and a WCS 5.2. I'm receiving alarm about flood atacks and desauthentication attacks from a client. These alarms are detected by the IDS system. I'd like to know if there are any way to block this client.
    Thanks a lot.

    Thanks Sschmidt,
    I saw this solution. The problem it's that i must create an entry by any client. If there are any client that capture the wpa key and after chage his mac i couldn't block them. Is that correct? I don't know how easily it's capture authenticantion packets with a WLC.
    Thanks

  • WLC 4400 and WLC 5500

    We have a site with a WLC 4400 and we would like to setup a Controller failover. The WLC 4400 is EOS/EOL and the replacement available is WLC 5508. Can someone advice me on how to configure these units in Primary /Secondary mode so that if any of the Controllers fail, the other one can take over?
    Thanks,

    Hi Akil,
    You are most welcome
    Yes, you can configure 4400's and 5500's in a redundant configuration, but both should be runningthe
    same code version. I believe the latest version that is compatible for both is 7.0.220.0. 
    this is the last version that supports the 4400 series.
    Here's a note that reflects the support;
    Note
    Controllers  do not have to be of the same model to be a member of a mobility group.  Mobility groups can be comprised of any combination of controller  platforms.
    http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mobil.html
    Cheers!
    Rob
    "Show a little faith, there's magic in the night" - Springsteen

Maybe you are looking for