WLC 5508 APs showing Line Protocol Down

I have a WLC 5508 (software version 7.5.102.0) and it has 175 APS (mixture of 1131, 1142, 1602, 2602).  Recently I've noticed that
about 40 of those APs don't work on the 2.4G Dot11Radio0.  sh int dot11 0 shows me:
Dot11Radio0 is up, line protocol is down
  Hardware is 802.11N 2.4GHz Radio, address is 1833.9d0c.2180 (bia 1833.9d0c.2180)
  MTU 1500 bytes, BW 54000 Kbit/sec, DLY 1000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/9355/42086/0 (size/max/drops/flushes); Total output drops: 3769399
  Queueing strategy: fifo
  Output queue: 0/30 (size/max)
  5 minute input rate 11000 bits/sec, 13 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     150800958 packets input, 597188558 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     217132697 packets output, 1132963042 bytes, 0 underruns
     55238 output errors, 0 collisions, 8 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
I've tried restarting the interface,to no avail, but rebooting the whole AP does bring it back up, but I expect that's a solution to the symptom, not the problem.

Hi Sean,
There are certain related bugs of this version. You may need to check whether you are hitting one these. I would suggest staying in 7.4.121.0 code would be a good idea unless you require new features available in 7.5 or 7.6.
CSCui66891:Marvell-based radio goes down due to stuck multicast packets in driverSymptom:AP's radio interface goes down and does not recover on its own without an AP reboot.Conditions:With releases 7.2.103.0 - 7.2.115.2, 7.3.101.0 - 7.3.112.0, and 7.4.100.0 - 7.4.110.0, this bug applies to all Marvell-based 802.11n Cisco Aironet access points *except* the 1140, 1040, and certain mesh APs.With releases 7.5.90.0 - 7.5.102.0, this bug applies to *all* Marvell-based 802.11n Cisco Aironet access points.Workaround:None. Reboot the AP.
Known Affected Releases(6)7.6(1.52)7.6(1.50)7.5(102.0)7.6(1.226)7.6(1.95)15.2(4)JA
Known Fixed Releases(10)10.1(0.74)7.6(1.55)7.5(102.8)10.1(100.0)15.2(4)JN7.6(1.103)10.1(11.5)7.4(111.7)15.2(4)JB7.4(121.0)
CSCum14069: AP1600/2600 radio down with 7.5.102.0 release  Symptom:[AIR-CAP1602I-Q-K9 (AC power supply) ]---------[Catalyst switch]------------[AIR-CT5508-K9 (7.5.102.0)][AIR-CAP1602I-Q-K9 (PoE) ]----[AIR-PWRINJ5=]-----[ Catalyst switch]------------[AIR-CT5508-K9 (7.5.102.0)][AIR-CAP1602I-Q-K9 (AC power supply) ]---------[non-Cisco non-PoE switch]------------[AIR-CT5508-K9 (7.5.102.0)]AP1600/2600 radios never go UP on above topology if the Catalyst switch was running older IOS such as c3750-ipservices-mz.122-25.SEB4
Conditions:WLC release 7.5.102.0 specific issue.AP1600/2600 specific issue.Older Catalyst IOS software (e.g. 12.2(25)SEB4)non-Cisco 3rd party switch
Workaround:Enable "Pre-standard 802.3af switches" option on AP from WLC GUI;WIRELESS => Access Points => All APs => target AP name => Advanced tab => Power Over Ethernet SettingsThis option is required to workaround this problem even if you don't have Pre-standard 802.3af switch nor you're using AC adapter/Power Injector.
Known Affected Releases:(1)7.5(102.0)Known Fixed Releases:(1)7.5(102.18)
HTH
Rasika
**** Pls rate all useful responses *****

Similar Messages

  • What trigger Line Protocol Down?

    Hi,
    Recently I encountered a problem on "line protocol down" as I'd posted on 4th April.
    Could anyone direct me to any webpage or sites where there's a detail explaination of how & what would trigger a line protocol down. Or these kinda data-link failure. Thanks!
    With regards

    Hi Friend,
    There could be few reasons majorly physical layer issue when the line protocol goes down.
    Can you please update which interface was showing line protocol down. Logical interface (SVI) on layer 3 switch, physical port on layer 2/3 switch or any physical interface on router?
    If it is a physical interface on layer 2 switch it is majorly a physical layer issue or may be that particular vlan asscosiated to that port got deleted.
    If it is a layer 3 logical interface showing line protocol down may be there is no vlan associated to that vlan configured on layer 2 switch port or no trunk carrying that vlan on that switch.
    HTH, if yes please rate the post.
    Ankur

  • Line protocol down

    what are all possibilities for having line protocol down status.pls discuss in detail.

    please see below link to get detailed information.
    http://www.cisco.com/univercd/cc/td/doc/cisintwk/itg_v1/tr1915.htm

  • Multiple DHCP scopes on WLC 5508 (not showing leases?)

    I have 2 DHCP scopes set up on a wlc 5508, one for the AP's and another for a wlan, the leases for the AP's scope show up, but the one that the clients on the WLAN are on do not show up in the "show leases" is that a bug? normal? 

    Customers using Cisco Unified Wireless solutions have been reporting issues with the DHCP support provided on the Wireless LAN Controller (WLC). Some of these issues are software bugs or debugability problems. Others are due to lack of proper understanding on the DHCP implementation.
    This document describes the different DHCP operations on the wireless controller, which provides consistent and accurate information to customers in an effort to reduce the related customer issues and TAC cases.
    Please refer to the following link: http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html

  • Line protocol question

    Okay, this might seem like a really stupid question but it's got me stumped.
    What the hell does "line protocol down" mean and how the hell do I fix it? I'm using a Cisco 2500 series router, and it's occuring on serial port 0 on BOTH routers. I've checked, double checked, re double checked, and triple checked (quadruple checked?) the wiring and the physical wiring is fine...
    Can anyone provide any insights to this at all for me? I'd greatly appreciate it.
    TIA

    The line protocol state (up or down) reflects the layer 2 status of the interface. If your serial interface is saying that its state is up/down it means that it knows that it is plugged into something on the interface but that there is a layer 2 connectivity problem.
    The nature of how the router determines the layer 2 status depends somewhat on the type of interface. On Serial interfaces the determination is based on the keepalives. So basically what the router is saying is that keepalives are not working on the router. There are a couple of things that can prevent keepalives on the serial interface, such as different protocols being configured (one end may be Cisco HDLC and the other end is PPP). If it was Frame Relay a mismatch of LMI type may cause it. Given your comment about using 2500 and that both sides are showing protocol down I am going to guesss that you have the routers configured back to back. And I am going to guess that you have not configured clock rate on whichever router has the DCE serial cable connected. When routers are back to back and do not connect to provider equipment, you need one of them to generate clocking (and it needs to be the one with the DCE cable). So check your cables, find which one is DCE, and configure clock rate on that router.
    HTH
    Rick

  • AIR-LAP1252AG Line protocol Error

    What are the reason for my Access Point to display interface up and line protocol down?
    I have tried to shut and unshut the interface and it still remain the same?
    AP# sh ip int br
    Interface IP-Address OK? Method Status Protocol
    BVI1 xx.xx.xx.xx YES NVRAM up up
    Dot11Radio0 unassigned YES NVRAM up up
    Dot11Radio0.aa unassigned YES unset up up
    Dot11Radio0.bb unassigned YES unset up up
    Dot11Radio0.cc unassigned YES unset up up
    Dot11Radio1 unassigned YES NVRAM up down
    Dot11Radio1.aa unassigned YES unset up down
    Dot11Radio1.bb unassigned YES unset up down
    Dot11Radio1.cc unassigned YES unset up down
    GigabitEthernet0 unassigned YES NVRAM up up
    GigabitEthernet0.bb unassigned YES unset up up
    GigabitEthernet0.cc unassigned YES unset up up

    dot11 ssid SSID
    vlan 12
    authentication open
    power inline negotiation prestandard source
    username uuuuuu password ppppp
    bridge irb
    interface Dot11Radio0
    no ip address
    no ip route-cache
    ssid SSID
    speed basic-5.5 11.0 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
    channel 2437
    station-role root
    rts threshold 2312
    interface Dot11Radio0.12
    encapsulation dot1Q 12
    no ip route-cache
    bridge-group 255
    bridge-group 255 subscriber-loop-control
    bridge-group 255 block-unknown-source
    no bridge-group 255 source-learning
    no bridge-group 255 unicast-flooding
    bridge-group 255 spanning-disabled
    interface Dot11Radio0.13
    encapsulation dot1Q 13 native
    no ip route-cache
    no cdp enable
    bridge-group 1
    bridge-group 1 subscriber-loop-control
    bridge-group 1 block-unknown-source
    no bridge-group 1 source-learning
    no bridge-group 1 unicast-flooding
    bridge-group 1 spanning-disabled
    interface Dot11Radio1
    no ip address
    no ip route-cache
    ssid SSID
    dfs band 3 block
    speed basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
    channel dfs
    station-role root
    rts threshold 2312
    interface Dot11Radio1.12
    encapsulation dot1Q 12
    no ip route-cache
    bridge-group 255
    bridge-group 255 subscriber-loop-control
    bridge-group 255 block-unknown-source
    no bridge-group 255 source-learning
    no bridge-group 255 unicast-flooding
    bridge-group 255 spanning-disabled
    interface Dot11Radio1.13
    encapsulation dot1Q 13 native
    no ip route-cache
    no cdp enable
    bridge-group 1
    bridge-group 1 subscriber-loop-control
    bridge-group 1 block-unknown-source
    no bridge-group 1 source-learning
    no bridge-group 1 unicast-flooding
    bridge-group 1 spanning-disabled
    interface GigabitEthernet0
    no ip address
    no ip route-cache
    duplex auto
    speed auto
    bridge-group 1
    no bridge-group 1 source-learning
    bridge-group 1 spanning-disabled
    interface GigabitEthernet0.12
    encapsulation dot1Q 12
    no ip route-cache
    bridge-group 255
    no bridge-group 255 source-learning
    bridge-group 255 spanning-disabled
    interface BVI1
    ip address xx.xx.xxx.xx 255.255.255.0
    no ip route-cache
    ip default-gateway xx.xx.xx.1
    no ip http server
    ip http authentication aaa
    no ip http secure-server
    ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
    ip radius source-interface BVI1

  • WLC 5508 rebooted but still showing high uptime

    Hi all,
    I had to reboot our production WLC 5508 last night to apply a new adder license, which increased our AP count by 25.
    We run a DMZ mobility controller alongside the primary controller, which handles our mobile/guest WLANs using a Mobility Anchor. Normally we would reboot both of these due to issues with the anchor after the primary is rebooted.
    So last night I rebooted the primary after installing the new adder license. Once it came back up, I checked the license count and it had increased as per the new license. After that I rebooted the mobility controller, and waited to ensure that this came back up.
    Almost straight away, all the AP's had re-associated with the primary (all 96 of them), and clients were starting to show up. I checked the same on the mobility controller (although this does not manage any AP's) and I could see mobility clients associating with this also.
    The problem came this morning, when none of the mobility clients that were connected to the mobiltiy WLANs were able to get to the Internet, or any kind of outside connection. This is the typical issue we see when our core switch gets rebooted, or the primary on its own, without rebooting the secondary.
    So to troubleshoot this morning the first thing I suddenly noticed was the uptime on the primary controller. It showed 298 days!!
    Anyone seen this behaviour before? The WLC DID reboot - I watched it go down and POST again. Why would the uptime counter not reset?
    We're on firmware 7.2.111.3 - which I realise is pretty old, but due to CIsco screwing us over with a limited upgrade path, we are not able to upgrade it yet (AP hardware not supported on any of the newer code above this version).
    Any help appreciated!

    In response to Sandeep, here's the sh sysinfo output:
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 7.2.111.3
    Bootloader Version............................... 1.0.1
    Field Recovery Image Version..................... 6.0.182.0
    Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
    Build Type....................................... DATA + WPS
    System Name...................................... UK***********
    System Location.................................. Slough CoLo
    System Contact................................... Greg Dent
    System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
    IP Address....................................... 172.17.1.40
    Last Reset....................................... Software reset
    System Up Time................................... 0 days 3 hrs 42 mins 23 secs
    System Timezone Location.........................
    Configured Country............................... Multiple Countries:GB,RU,US
    Operating Environment............................ Commercial (0 to 40 C)
    Internal Temp Alarm Limits....................... 0 to 65 C
    Internal Temperature............................. +44 C
    External Temperature............................. +26 C
    --More-- or (q)uit
    Fan Status....................................... OK
    State of 802.11b Network......................... Enabled
    State of 802.11a Network......................... Enabled
    Number of WLANs.................................. 7
    Number of Active Clients......................... 794
    Burned-in MAC Address............................ **************
    Power Supply 1................................... Present, OK
    Power Supply 2................................... Present, OK
    Maximum number of APs supported.................. 125
    As you may notice, the uptime has now reset, but thats because I had to reboot it again this morning. I didnt grab the output before the second reboot. It seems whatever issue caused the uptime counter not to reset didnt occur this time.
    Very odd.    

  • Why WLC 5508 shows message " Operator changed to 11g mode" & AP is rebooted

    Dear Sir,
    I have faced some problem with Cisco 1520 Series APs.
    Since few days, We got the log in wlc 5508 like this
    "AP 'MAPNSY#WMI3', MAC: ac:a0:16:5c:45:00 disassociated previously due to AP  Reset. Uptime: 0 days, 00 h 22 m 52 s . Last reset reason: operator changed 11g  mode."
    & then AP is rebooted.
    Here, I attached the screenshot of WLC 5508 Log.
    Plz, help us.

    Not the IP addr of the management interface.. I am telling about the Dynamic AP manager interface that you have configured which is for the AP to register..
    Please post in the output..
    show interface summary (mentioning the interface used for APs to join)
    Regards
    Surendra

  • 5508 pair show "Down" as data sources for Netflow

    I've setup my 5508s to monitor and export netflow to Cisco Prime Infrastructure but no data populates in the expected tabs.  When I check Admin-> Data Sources they show up as "down", while other netflow exporters (ASA1000s I used to test) show as "up".  I verified in the WLC CLI that they are exporting flows.  Thoughts?
    WLC show flow exporter stat:
    Exporter-name: CiscoPrime
      Total Flows Sent: 69536
      Total Pkts Sent: 4021
      Total Pkts Dropped: 0
      Last Sent Time: Thu Aug 15 15:24:29 2013

    Hi Marcin,
    You are most welcome my friend I think the great NetPros in this thread
    offer some excellent tips and strategies for this plan as well as the restrictions
    you will encounter moving forward. You will likely want to make the 5508 the
    primary controller with an eye on moving away from the 4400 at some point
    due to it's EoL and inability to run the latest code versions.
    Cheers!
    Rob
    "Show a little faith, there's magic in the night" - Springsteen

  • IPsec over GRE tunnel's line protocol is down but able to ping the tunnel destination

    >>both routers are located in different countries and connected with ISP
    >>IPsec over GRE tunnel is configured on both the routers 
    >>tunnel's line protocol is down for both the ends but able to reach the tunnel destination with tunnel source
    >>Packet is not receiving on the router_1 and but could see packets are getting encrypting on the Router_2
    >>ISP is not finding any issue with their end 
    >>Please guide me how i can fix this issue and what need to be check on this ????
    ========================
    Router_1#sh run int Tunnel20
    Building configuration...
    Current configuration : 272 bytes
    interface Tunnel20
     bandwidth 2048
     ip address 3.85.129.141 255.255.255.252
     ip mtu 1412
     ip flow ingress
     delay 1
     cdp enable
     tunnel source GigabitEthernet0/0/3
     tunnel destination 109.224.62.26
    end
    ===================
    Router_1#sh int Tunnel20
    Tunnel20 is up, line protocol is up>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Keepalive is not set
      Hardware is Tunnel
      Description: *To CRPrgEIQbaghd01 - 2Mb GRE over Shared ISP Gateway*
      Internet address is 3.85.129.141/30
      MTU 17916 bytes, BW 2048 Kbit/sec, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation TUNNEL, loopback not set
      Keepalive not set
      Tunnel source 195.27.20.14 (GigabitEthernet0/0/3), destination 109.224.62.26
       Tunnel Subblocks:
          src-track:
             Tunnel20 source tracking subblock associated with GigabitEthernet0/0/3
              Set of tunnels with source GigabitEthernet0/0/3, 32 members (includes iterators), on interface <OK>
      Tunnel protocol/transport GRE/IP
        Key disabled, sequencing disabled
        Checksumming of packets disabled
      Tunnel TTL 255, Fast tunneling enabled
      Tunnel transport MTU 1476 bytes
      Tunnel transmit bandwidth 8000 (kbps)
      Tunnel receive bandwidth 8000 (kbps)
      Last input 1w6d, output 14w4d, output hang never
      Last clearing of "show interface" counters 2y5w
      Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/0 (size/max)
      5 minute input rate 0 bits/sec, 0 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         1565172427 packets input, 363833090294 bytes, 0 no buffer
         Received 0 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         1778491917 packets output, 1555959948508 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 unknown protocol drops
         0 output buffer failures, 0 output buffers swapped out
    =============================
    Router_1#ping 109.224.62.26 re 100 sou 195.27.20.14
    Type escape sequence to abort.
    Sending 100, 100-byte ICMP Echos to 109.224.62.26, timeout is 2 seconds:
    Packet sent with a source address of 195.27.20.14
    Success rate is 92 percent (92/100), round-trip min/avg/max = 139/142/162 ms
    Router_1#
    ============================================
    Router_1#sh cry ip sa pe 109.224.62.26 | in caps
        #pkts encaps: 831987306, #pkts encrypt: 831987306, #pkts digest: 831987306
        #pkts decaps: 736012611, #pkts decrypt: 736012611, #pkts verify: 736012611
    Router_1#sh clock
    15:09:45.421 UTC Thu Dec 25 2014
    Router_1#
    ===================
    Router_1#sh cry ip sa pe 109.224.62.26 | in caps
        #pkts encaps: 831987339, #pkts encrypt: 831987339, #pkts digest: 831987339
        #pkts decaps: 736012611, #pkts decrypt: 736012611, #pkts verify: 736012611>>>>>>>>>>>>>>>>>>>>Traffic is not receiving from Router 2 
    Router_1#sh clock
    15:11:36.476 UTC Thu Dec 25 2014
    Router_1#
    ===================
    Router_2#sh run int Tu1
    Building configuration...
    Current configuration : 269 bytes
    interface Tunnel1
     bandwidth 2000
     ip address 3.85.129.142 255.255.255.252
     ip mtu 1412
     ip flow ingress
     load-interval 30
     keepalive 10 3
     cdp enable
     tunnel source GigabitEthernet0/0
     tunnel destination 195.27.20.14
    end
    Router_2#
    =======================
    Router_2#sh run | sec cry
    crypto isakmp policy 10
     authentication pre-share
    crypto isakmp key Router_2 address 195.27.20.14
    crypto isakmp key Router_2 address 194.9.241.8
    crypto ipsec transform-set ge3vpn esp-3des esp-sha-hmac
     mode transport
    crypto map <Deleted> 10 ipsec-isakmp
     set peer 195.27.20.14
     set transform-set ge3vpn
     match address Router_2
    crypto map <Deleted> 20 ipsec-isakmp
     set peer 194.9.241.8
     set transform-set ge3vpn
     match address Router_1
     crypto map <Deleted>
    Router_2#
    ====================================
    Router_2#sh cry ip sa pe 195.27.20.14 | in caps
        #pkts encaps: 737092521, #pkts encrypt: 737092521, #pkts digest: 737092521
        #pkts decaps: 828154572, #pkts decrypt: 828154572, #pkts verify: 828154572>>>>>>>>>>>>Traffic is getting encrypting from router 2 
    Router_2#sh clock
    .15:10:33.296 UTC Thu Dec 25 2014
    Router_2#
    ========================
    Router_2#sh int Tu1
    Tunnel1 is up, line protocol is down>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Down
      Hardware is Tunnel
      Internet address is 3.85.129.142/30
      MTU 17916 bytes, BW 2000 Kbit/sec, DLY 50000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation TUNNEL, loopback not set
      Keepalive set (10 sec), retries 3
      Tunnel source 109.224.62.26 (GigabitEthernet0/0), destination 195.27.20.14
       Tunnel Subblocks:
          src-track:
             Tunnel1 source tracking subblock associated with GigabitEthernet0/0
              Set of tunnels with source GigabitEthernet0/0, 2 members (includes iterators), on interface <OK>
      Tunnel protocol/transport GRE/IP
        Key disabled, sequencing disabled
        Checksumming of packets disabled
      Tunnel TTL 255, Fast tunneling enabled
      Tunnel transport MTU 1476 bytes
      Tunnel transmit bandwidth 8000 (kbps)
      Tunnel receive bandwidth 8000 (kbps)
      Last input 1w6d, output 00:00:02, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 14843
      Queueing strategy: fifo
      Output queue: 0/0 (size/max)
      30 second input rate 0 bits/sec, 0 packets/sec
      30 second output rate 0 bits/sec, 0 packets/sec
         1881547260 packets input, 956465296 bytes, 0 no buffer
         Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         1705198723 packets output, 2654132592 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 unknown protocol drops
         0 output buffer failures, 0 output buffers swapped out
    =============================
    Router_2#ping 195.27.20.14 re 100 sou 109.224.62.26
    Type escape sequence to abort.
    Sending 100, 100-byte ICMP Echos to 195.27.20.14, timeout is 2 seconds:
    Packet sent with a source address of 109.224.62.26
    Success rate is 94 percent (94/100), round-trip min/avg/max = 136/143/164 ms
    Router_2#
    =========================

    Hello.
    First of all, try to reset IPSec (clear crypto isakmp sa ..., clear crypto session ...).
    Configure inbound ACL on the router to match esp protocol and check if the packets arrive.
    Please provide full output "show crypto ipsec sa"
     from both sides.

  • GigabitEthernet1/1 is up, line protocol is down (notconnect)

    Hi All,
    I am really curious to investigate a possible reason behind this error message.
    During the configuration of a port channel bundled with 2 links I have the error in the subject but only for one side of the connection and only for one link part of the port channel.
    On the other side the corrispondent interface was up/up and the other link part of the port channel was able to go up with no issue (for all the configuration is the same).
    Background info:
    - The link in discussion was connecting the two Multilayer swicthes before the configuration of the port channel with no issue
    - The port channel is a L2 etherchannel
    - What was done was simply to shutdown the interface on both swicthes, add the command channel group xx mode on  on both side of the connection and then bring up the connection with the result above showed: one side up/down (not connect) and the other side up/up
    I am excluding problem with the configuration. The reason is simple: i just reply the configuration to the all links (total 2) part of the port channel with no issue.
    Can be a cabling problem (SFP)? Again keep in mind that before the change, this link was active with no issue for 4 years.
    Thanks all.

    Hi Peter,
    Find below the requested output.
    I forgot to mention something:
    The etherchannel is a L2
    The mode employed to create the port channel was on
    In any case what I did in the meanwhile was:
    - To check the cable -> It is ok
    - I did not check the SFP but I configured the involved interfaces as L3 and I bringed up both with no issue. They are connected so I am assuming that the SFP is ok. Do you agree?
    At this point due to the fact that:
    Configuration is working properly for the second link part of the same portchannel
    The cable and sfp is ok
    The only problem that I can see here is the Etherchannel Modes adopted: I heard that on modes is not the best practice. The best is use the LACP
    Here the requested output:
    show int gi1/1 capa
    Dot1x:                 yes
      Model:                 WS-X6748-SFP
      Type:                  1000BaseSX
      Speed:                 1000
      Duplex:                full
      Trunk encap. type:     802.1Q,ISL
      Trunk mode:            on,off,desirable,nonegotiate
      Channel:               yes
      Broadcast suppression: percentage(0-100)
      Flowcontrol:           rx-(off,on,desired),tx-(off,on,desired)
      Membership:            static
      Fast Start:            yes
      QOS scheduling:        rx-(1q8t), tx-(1p3q8t)
      CoS rewrite:           yes
      ToS rewrite:           yes
      Inline power:          no
      SPAN:                  source/destination
      UDLD                   yes
      Link Debounce:         yes
      Link Debounce Time:    yes
      Ports on ASIC:         25,27,29,31,33,35,37,39,41,43,45,47
      Port-Security:         yes
    GigabitEthernet1/1 is up, line protocol is down (notconnect)
      Hardware is C6k 1000Mb 802.3, address is 0019.aa70.0000 (bia 0019.aa70.0006)
      Description:
      MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 1000Mb/s, media type is SX
      input flow-control is off, output flow-control is off
      Clock mode is auto
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:58, output 02:08:13, output hang never
      Last clearing of "show interface" counters 4y10w
      Input queue: 0/2000/66318/0 (size/max/drops/flushes); Total output drops: 1731225685
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 17000 bits/sec, 25 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         1705750435550 packets input, 2106584160022948 bytes, 1 no buffer
         Received 245618852 broadcasts (148781910 multicasts)
         0 runts, 48 giants, 1 throttles
         0 input errors, 0 CRC, 0 frame, 66317 overrun, 0 ignored
         0 watchdog, 0 multicast, 0 pause input
         0 input packets with dribble condition detected
         3762458417011 packets output, 3133012553118384 bytes, 0 underruns
         0 output errors, 0 collisions, 4 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier, 0 PAUSE output
         0 output buffer failures, 0 output buffers swapped out
    show interfaces status err-disabled
    empty
    show etherchannel summary
    120    Po120(SU)        -        Gi1/2(P) Gi1/1(D)

  • WLC 5508 LOAD BALANCING APs to HA-SSO

    Do somebody knows what´s going to happen about configuration when you migrate 2-WLC 5508 giving wireless services correctly, using load balancing with the APs to HA-SSO mode???
    At this time we have some AP groups in WLC1 and in WLC2 we don´t have the AP groups, what´s going to happen with the configuration of both WLCs, both configuration are going to be merged??
    REGARDS

    When you covert the pair into SSO, all the APs will go to the ACTIVE unit.  No unit will "live" in the standby unit because this unit will "share" the AP-support license between the two.
    This is the first step you need to get sorted.  Send an email to [email protected] and give them the exact details of what you want to do (i. e.  AP SSO) and then provide the serial number of your nominated active WLC and the serial number of your nominated standby WLC.

  • I have a blue veritcal line going down the middle of my screen turned my iMac and it showed up. What can that mean?

    I have a blue veritcal line going down the middle of my screen turned my iMac and it showed up. What can that mean?

    Hard to help without knowing which variant of iMac you have. They've been in continuous production since 1998 in four major families, and what works for one familiy of iMac may not work to diagnose one from another family.
    Doing "About ths Mac" will show the processor info. Post what it says about your processor (and Mac OS version while you are there) and that will narrow what family of iMac you have.
    This forum section is for the three iMac families made before 2006.

  • WLC 5508 : session disconnected when one lag-port is down.

    Hello,
    I have a WLC 5508 ( version 6.0.182).
    When the port1 and port2 are connected ( The switch is configured with a etherchannel in forced mode) everything works fine: There is traffic on the 2 ports.
    When I disconnect one of the 2 ports, I can still ping outside with my PC client, but all my tcp sesssions goes down and I even cannot restart my session. The only way I found  is to do a "Disconnect / Reconnect"  on my  PC  wireless connection.
    Do you know this probleme ?
    Is it a way to avoid it ?
    Michel Misonne

    CSCth12513 LAG fail-over does not work on CT5508
    This bug is fixed in the special release available through TAC : 6.0.199.157 and 7.0.xxxx
    Hope this helps.
    Nicolas
    ===
    Dont' forget to rate answers that you find useful

  • Cisco WLC 5508 assigning different SSID to few APs

    Hello Everyone,
    I have a WLC 5508 runing 8.0
    Presently one SSID is assigned to all th APs registered with my WLC.
    I want a different SSID to 2 of APs. Can anyone tell me how to do this?

    Depend on WLAN ID number as well.
    1. if WLAN ID number is greater than 16, then those SSID not visible in "default ap-group" & only in the APs in particular AP Group.
    2. if WLAN ID number is lower than 16 then, by default it will advertise in APs in "default ap-grop". So if you add that WLAN to particular AP Group, then that WLAN advertised by APs in both AP groups (default & specific AP group)
    HTH
    Rasika
    **** Pls rate all useful responses ****

Maybe you are looking for