Introduction Saravanan Lakshmanan is a customer support engineer at the Cisco Technical Assistance Center, specialising in wireless technologies and solving high-severity and critical wireless issues for Cisco customers and partners. In this document, Saravanan explained about Understanding 3850 uplink ports/NM Module. 3850 - 48 switch Ports show interface status, status, capabilities, spanning-tree, mtu might not show all available Gig/Ten-Gig uplink physical interfaces because it is based on the uplink NM type installed on 3850. How to find what type of NM module is installed/available on the 3850 switch ----------------- show inventory ------------------ NAME: "c3xxx Stack", DESCR: "c3xxx Stack" PID: WS-C3850-48T , VID: L0 , SN: FOC1747Y5UD NAME: "Switch 1", DESCR: "WS-C3850-48T" PID: WS-C3850-48T , VID: L0 , SN: FOC1747Y5UD NAME: "Switch 1 - Power Supply A", DESCR: "Switch 1 - Power Supply A" PID: PWR-C1-350WAC , VID: V01 , SN: AZS1726015W NAME: "Switch 1 - Power Supply B", DESCR: "Switch 1 - Power Supply B" PID: PWR-C1-350WAC , VID: V01 , SN: AZS17260160 NAME: "Switch 1 FRU Uplink Module 0", DESCR: "2x1G 2x10G Uplink Module" =========> uplink modules. Below are the available uplink ports. PID: C3850-NM-2-10G , VID: V01 , SN: FOC17448T4Y NAME: "GigabitEthernet1/1/1", DESCR: "1000BaseSX SFP" PID: GLC-SX-MMD , VID: V01 , SN: AGA1743RP4A NAME: "GigabitEthernet1/1/2", DESCR: "1000BaseSX SFP" PID: GLC-SX-MMD , VID: V01 , SN: AGA1743RS1C NAME: "TenGigabitEthernet1/1/3", DESCR: "1000BaseSX SFP" PID: GLC-SX-MMD , VID: V01 , SN: AGA1743RPA5 NAME: "TenGigabitEthernet1/1/4", DESCR: "1000BaseSX SFP" PID: GLC-SX-MMD , VID: V01 , SN: AGA1743RPAN   Not showing interfaces Gi1/1/3, Gi1/1/4, Te1/1/1 and Te1/1/2, which is expected.   Show interface status ------------------ show interfaces status ------------------ Port Name Status Vlan Duplex Speed Type Gi1/0/1 connected 352 a-full a-1000 10/100/1000BaseTX . . . Gi1/0/47 notconnect 1 auto auto 10/100/1000BaseTX Gi1/0/48 notconnect 1 auto auto 10/100/1000BaseTX Gi1/1/1 connected 1 full 1000 1000BaseSX SFP Gi1/1/2 connected 1 full 1000 1000BaseSX SFP Te1/1/3 connected 1 full 1000 1000BaseSX SFP Te1/1/4 connected 1 full 1000 1000BaseSX SFP   ------------------ show spanning-tree ------------------ . . Interface Role Sts Cost Prio.Nbr Type ------------------- ---- --- --------- -------- -------------------------------- Gi1/1/1 Desg FWD 4 128.49 P2p Gi1/1/2 Desg FWD 4 128.50 P2p Te1/1/3 Back BLK 4 128.55 P2p Te1/1/4 Back BLK 4 128.56 P2p It is an expected behaviour based on the available Uplink module on the 3850 switch. More Information Configuring a Network Module 3850: Understanding interface configuration on NM modules ... View more

  Introduction WLC update from 7.6.120.0 to 8.0.110.0 - speed and ms drops alot. Core Issue User had to update their Wism2's and 5508's to 7.6.120.0 for 3702 support. One of the Wism2's started to hand/restart a few times per week after the update. Other than that the wireless was working good. TAC found some bugs that suited what they could read from the logs and told me to update to 8. So user upgrade, and *smack* the wireless dropped to speeds around 5-10 Mbits with 80+ ms. Yielding that exchange, fileservers and alot if not all programs did not function/lost connection. Solution After the upgrade the upgrade. The upgrade itself had enabled interim update under the AAA accounting with a value of 0. I tried on our lab controller to turn on interim with the same value but the system wouldn't let me since its not an accepted value. So I turned the function off on one of the live controllers (that just had a few AP's heh) and immediately the Wireless were back delivering good speeds and answering times again. Another user did confirmed that 8.x upgrade automatically enabled interim update with 0 value and disabled them manually after seeing this. Similar Issue This bug might be connected to the problem https://supportforums.cisco.com/discussion/11894006/ise-12-wlc-5508-nas-sends-radius-accounting-update-messages-too-frequently More Information Description - WLC sends acct-update twice in the same millisecond - CSCug14713 Symptom: Radius Accounting update seen twice from the WLC when initial authentication occurs for Radius NAC enabled WLAN.  Conditions: When Radius NAC is enabled.  Workaround: No Workaround. Known Affected Releases: 7.5(1.7)   Known Fixed Releases:   7.3(113.108) 7.4(122.4) 7.4(130.0) 7.6(1.39) 7.6(100.0) 7.6(4.2) 8.0(100.0) 8.0(72.15) 8.0(72.2) 8.0(72.3)   Source Download software for  Cisco Wireless LAN Controller Software WLC update from 7.6.120.0 to 8.0.110.0 - speed and ms drops alot ... View more

  Introduction Prime fails to add a WLC or unable to add Controller in WCS Scenario 1 WLC 5508 8.0.115 fails when  add to prime 2.2: Unable to collect details neighbor device using Cisco Discovery Protocol. Posible cause :  SNMP request timed out. Verify device credentials and SNMP response speed from device. The SNMP credentials are corrects.  Capturing packets we see that the WLC responds snmp requests but  prime does not know how interpret the responses and re-order them. Solution  User resolved it by changing  " Maximum VarBinds per Get PDU " from 30 to 15  in  Administration > Settings > System Settings > SNMP Settings. Scenario 2 I use WCS v6.0.132.0 to manage my 4402 and 2106 controller both running version 6.0.182.0 When I try to add another 2106 over DM-VPN it fails with the following errors: ”No response from device, check SNMP communities, version or network for issues” If I move the new 2106 controller to LAN with same config there is no problem. I found this note in the in “Cisco Wireless Control System Configuration Guide, Release 6.0” “Note If you are adding a controller into WCS across a GRE link using IPsec or a lower MTU link with multiple fragments, you may need to adjust the MaxVar Binds PerPDU. If it is set too high, the controller may fail to be added into WCS. To adjust the MaxVarBindsPerPDU setting, do the following:  1) Stop WCS.  2) Go to the location of the Open SnmpParameters.properties file on the server that is running WCS.  3) Edit MaxVarBindsPerPDU to 50 or lower.  4) Restart WCS.” On my system I have the “SnmpParameters.properties” file is located //WCS6.0.132.0\webnms\classes\com\cisco\server\resources But I don’t have “MaxVarBindsPerPDU” settings in the file.  Beside some # explanations text, the only settings I have in the “SnmpParameters.properties” file is: DebugEnabled false SerializeRequests true MaxRepetitions 10 MaxRetryTimeout 60 WlanTimeoutMsecsPerAP 50 I have tried to add “MaxVarBindsPerPDU” settings, but it have no effect. Solution User resolved the issue by changing the “Maximum VarBinds per Get PDU” from 30 to 20 and “Maximum VarBinds per Set PDU” from 50 to 20. More Information If you are adding a controller into Prime Infrastructure across a GRE link using IPsec or a lower MTU link with multiple fragments, you might need to adjust the Maximum VarBinds per Get PDU and Maximum VarBinds per Set PDU. If it is set too high, the controller might fail to be added into Prime Infrastructure. To adjust the Maximum VarBinds per Get PDU or Maximum VarBinds per Set PDU, do the following: Stop Prime Infrastructure, choose Administration > Settings > SNMP Settings, and edit the Maximum VarBinds per Get PDU and Maximum VarBinds per Set PDU values to 50 or lower. If you reduce the Maximum VarBinds per Get PDU or Maximum VarBinds per Set PDU value, applying the configurations to the device might fail. Source Prime fails to add a WLC Can’t add Controller over VPN in WCS v6.0.132.0 Cisco Prime Infrastructure Classic View Configuration Guide for Wireless Devices - Configuring Devices ... View more

  Introduction User is trying to configure an autonomous AP with EAP authentication. The AP is a 1600 with software Version 15.2(2)JB2 and the RADIUS NPS is a Windows 2008R2. When the client tries to authenticate, I get the following error on the AP: Error Jun 12 11:39:13.945: RADIUS:  AAA Unsupported Attr: ssid              [347] 2    Jun 12 11:39:13.945: RADIUS:  AAA Unsupported Attr: service-type      [345] 4   1 Jun 12 11:39:13.945: RADIUS:  AAA Unsupported Attr: interface         [222] 3   Debugs Jun 12 11:39:13.945: RADIUS/ENCODE(00000062):Orig. component type = DOT11 Jun 12 11:39:13.945: RADIUS:  AAA Unsupported Attr: ssid              [347] 2    Jun 12 11:39:13.945: RADIUS:  AAA Unsupported Attr: service-type      [345] 4   1 Jun 12 11:39:13.945: RADIUS:  AAA Unsupported Attr: interface         [222] 3    Jun 12 11:39:13.945: RADIUS:   32                 [ 2] Jun 12 11:39:13.945: RADIUS(00000062): Config NAS IP: 172.16.254.116 Jun 12 11:39:13.945: RADIUS(00000062): Config NAS IPv6: Jun 12 11:39:13.945: RADIUS/ENCODE(00000062): acct_session_id: 87 Jun 12 11:39:13.945: RADIUS(00000062): Config NAS IP: 172.16.254.116 Jun 12 11:39:13.945: RADIUS(00000062): sending Jun 12 11:39:13.945: RADIUS(00000062): Send Access-Request to 172.16.0.32:1812 id 1645/16, len 176 Jun 12 11:39:13.945: RADIUS:  authenticator 22 42 80 A5 A5 A3 1B 9C - 3C 79 68 45 58 6E BF 0D Jun 12 11:39:13.945: RADIUS:  User-Name           [1]   28  "host/WM-WSUS-998.empresa.local" Jun 12 11:39:13.945: RADIUS:  Framed-MTU          [12]  6   1400                       Jun 12 11:39:13.945: RADIUS:  Called-Station-Id   [30]  22  "2C-3E-CF-0B-BF-60:1A" Jun 12 11:39:13.945: RADIUS:  Calling-Station-Id  [31]  16  "001e.58a2.ba4b" Jun 12 11:39:13.945: RADIUS:  Service-Type        [6]   6   Login                     [1] Jun 12 11:39:13.945: RADIUS:  Message-Authenticato[80]  18   Jun 12 11:39:13.945: RADIUS:   FF FB F9 0F BB 98 02 E3 19 71 EC DF 94 D6 13 A6                 [ q] Jun 12 11:39:13.945: RADIUS:  EAP-Message         [79]  33   Jun 12 11:39:13.945: RADIUS:   02 02 00 1F 01 68 6F 73 74 2F 57 4D 2D 57 53 55 53 2D 39 39 38  [host/WM-WSUS-998] Jun 12 11:39:13.945: RADIUS:   2E 63 62 61 2E 6C 6F 63 61 6C        [ .empresa.local] Jun 12 11:39:13.945: RADIUS:  NAS-Port-Type       [61]  6   802.11 wireless           [19] Jun 12 11:39:13.945: RADIUS:  NAS-Port            [5]   6   277                        Jun 12 11:39:13.945: RADIUS:  NAS-Port-Id         [87]  5   "277" Jun 12 11:39:13.945: RADIUS:  NAS-IP-Address      [4]   6   172.16.254.116             Jun 12 11:39:13.945: RADIUS:  Nas-Identifier      [32]  4   "ap" Jun 12 11:39:13.945: RADIUS(00000062): Sending a IPv4 Radius Packet Jun 12 11:39:13.945: RADIUS(00000062): Started 5 sec timeout Jun 12 11:39:13.949: RADIUS: Received from id 1645/16 172.16.0.32:1812, Access-Reject, len 44 Jun 12 11:39:13.949: RADIUS:  authenticator 7E 87 33 D9 2C 29 15 87 - 54 75 9A A2 A2 3E 63 08 Jun 12 11:39:13.949: RADIUS:  EAP-Message         [79]  6    Jun 12 11:39:13.949: RADIUS:   04 02 00 04 Jun 12 11:39:13.949: RADIUS:  Message-Authenticato[80]  18   Jun 12 11:39:13.949: RADIUS:   89 B3 79 93 B1 C5 2B 9D 43 A2 65 AE 9C 04 91 A4              [ y+Ce] Jun 12 11:39:13.953: RADIUS(00000062): Received from id 1645/16 Jun 12 11:39:13.953: RADIUS/DECODE: EAP-Message fragments, 4, total 4 bytes Jun 12 11:39:13.953: %DOT11-7-AUTH_FAILED: Station 001e.58a2.ba4b Authentication failed Jun 12 11:39:14.973: RADIUS/ENCODE(00000063):Orig. component type = DOT11 J un 12 11:39:14.973: RADIUS:  AAA Unsupported Attr: ssid              [347] 2    Jun 12 11:39:14.973: RADIUS:  AAA Unsupported Attr: service-type      [345] 4   1 Jun 12 11:39:14.973: RADIUS:  AAA Unsupported Attr: interface         [222] 3    Jun 12 11:39:14.973: RADIUS:   32                 [ 2] Jun 12 11:39:14.973: RADIUS(00000063): Config NAS IP: 172.16.254.116 Jun 12 11:39:14.973: RADIUS(00000063): Config NAS IPv6: Jun 12 11:39:14.973: RADIUS/ENCODE(00000063): acct_session_id: 88 Jun 12 11:39:14.973: RADIUS(00000063): Config NAS IP: 172.16.254.116 Jun 12 11:39:14.973: RADIUS(00000063): sending Jun 12 11:39:14.973: RADIUS(00000063): Send Access-Request to 172.16.0.32:1812 id 1645/17, len 158 Jun 12 11:39:14.973: RADIUS:  authenticator 1D BA 6B A3 29 E2 0C AE - AA AA EC FD 14 2F CD 24 Jun 12 11:39:14.973: RADIUS:  User-Name           [1]   19  "Empresa\User" Jun 12 11:39:14.973: RADIUS:  Framed-MTU          [12]  6   1400                       Jun 12 11:39:14.973: RADIUS:  Called-Station-Id   [30]  22  "2C-3E-CF-0B-BF-60:1A" Jun 12 11:39:14.973: RADIUS:  Calling-Station-Id  [31]  16  "001e.58a2.ba4b" Jun 12 11:39:14.973: RADIUS:  Service-Type        [6]   6   Login                     [1] Jun 12 11:39:14.973: RADIUS:  Message-Authenticato[80]  18   Jun 12 11:39:14.973: RADIUS:   27 0E 57 4F 94 F1 A4 C2 A2 D7 CE 18 7C 2A B9 AF             [ 'WO|*] Jun 12 11:39:14.973: RADIUS:  EAP-Message         [79]  24   Jun 12 11:39:14.973: RADIUS:   02 02 00 16 01 43 42 41 5C 50 65 64 72 6F 2E 41 6C 6D 65 69 64  [Empresa\User] Jun 12 11:39:14.973: RADIUS:   61                 [ a] Jun 12 11:39:14.973: RADIUS:  NAS-Port-Type       [61]  6   802.11 wireless           [19] Jun 12 11:39:14.973: RADIUS:  NAS-Port            [5]   6   278                        Jun 12 11:39:14.973: RADIUS:  NAS-Port-Id         [87]  5   "278" Jun 12 11:39:14.973: RADIUS:  NAS-IP-Address      [4]   6   172.16.254.116             Jun 12 11:39:14.973: RADIUS:  Nas-Identifier      [32]  4   "ap" Jun 12 11:39:14.973: RADIUS(00000063): Sending a IPv4 Radius Packet Jun 12 11:39:14.973: RADIUS(00000063): Started 5 sec timeout Jun 12 11:39:14.977: RADIUS: Received from id 1645/17 172.16.0.32:1812, Access-Challenge, len 90 Jun 12 11:39:14.977: RADIUS:  authenticator B0 3A 94 27 69 48 8A 39 - 71 DB 7C A3 6F B1 47 19 Jun 12 11:39:14.977: RADIUS:  Session-Timeout     [27]  6   30                         Jun 12 11:39:14.977: RADIUS:  EAP-Message         [79]  8    Jun 12 11:39:14.977: RADIUS:   01 03 00 06 19 20                 [  ] Jun 12 11:39:14.977: RADIUS:  State               [24]  38   Jun 12 11:39:14.977: RADIUS:   21 0E 03 C7 00 00 01 37 00 01 02 00 AC 10 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 7B 20 F6 EE            [ !7 0{ ] Jun 12 11:39:14.977: RADIUS:  Message-Authenticato[80]  18   Jun 12 11:39:14.977: RADIUS:   C3 8B 89 69 C7 7B 57 72 67 A5 8F B2 2C 84 44 7C          [ i{Wrg,D|] Jun 12 11:39:14.977: RADIUS(00000063): Received from id 1645/17 Jun 12 11:39:14.977: RADIUS/DECODE: EAP-Message fragments, 6, total 6 bytes Jun 12 11:39:14.985: RADIUS/ENCODE(00000063):Orig. component type = DOT11 Jun 12 11:39:14.985: RADIUS:  AAA Unsupported Attr: ssid              [347] 2    Jun 12 11:39:14.985: RADIUS:  AAA Unsupported Attr: service-type      [345] 4   1 Jun 12 11:39:14.985: RADIUS:  AAA Unsupported Attr: interface         [222] 3    Jun 12 11:39:14.985: RADIUS:   32                 [ 2] Jun 12 11:39:14.985: RADIUS(00000063): Config NAS IP: 172.16.254.116 Jun 12 11:39:14.985: RADIUS(00000063): Config NAS IPv6: Jun 12 11:39:14.985: RADIUS/ENCODE(00000063): acct_session_id: 88 Jun 12 11:39:14.985: RADIUS(00000063): Config NAS IP: 172.16.254.116 Jun 12 11:39:14.985: RADIUS(00000063): sending Jun 12 11:39:14.985: RADIUS(00000063): Send Access-Request to 172.16.0.32:1812 id 1645/18, len 279 Jun 12 11:39:14.985: RADIUS:  authenticator BE 87 70 F0 26 CF FC 41 - 02 10 8D 7C CD 40 D1 12 Jun 12 11:39:14.985: RADIUS:  User-Name           [1]   19  "Empresa\User" Jun 12 11:39:14.985: RADIUS:  Framed-MTU          [12]  6   1400                       Jun 12 11:39:14.985: RADIUS:  Called-Station-Id   [30]  22  "2C-3E-CF-0B-BF-60:1A" Jun 12 11:39:14.985: RADIUS:  Calling-Station-Id  [31]  16  "001e.58a2.ba4b" Jun 12 11:39:14.985: RADIUS:  Service-Type        [6]   6   Login                     [1] Jun 12 11:39:14.985: RADIUS:  Message-Authenticato[80]  18   Jun 12 11:39:14.985: RADIUS:   63 30 E2 67 34 27 2D 93 C2 BD 0E F8 B0 E2 2D EF           [ c0g4'--] Jun 12 11:39:14.985: RADIUS:  EAP-Message         [79]  107 Jun 12 11:39:14.985: RADIUS:   02 03 00 69 19 80 00 00 00 5F 16 03 01 00 5A 01 00 00 56 03 01 53 99 BB 5F 6E 1D 89 61 75 51 D9 7C C3 55 88 C7 E8 DF 37 E9 EB 1D 8C 21 09 0D 8C C5 59 47  [i_ZVS_nauQ|U7!YG] Jun 12 11:39:14.985: RADIUS:   AD B1 00 00 18 00 2F 00 35 00 05 00 0A C0 13 C0 14 C0 09 C0 0A 00 32 00 38 00 13 00 04 01 00 00 15 FF 01 00 01 00 00 0A 00 06 00 04 00 17 00 18 00 0B 00 02 01 00              [ /528] Jun 12 11:39:14.985: RADIUS:  NAS-Port-Type       [61]  6   802.11 wireless           [19] Jun 12 11:39:14.985: RADIUS:  NAS-Port            [5]   6   278                        Jun 12 11:39:14.985: RADIUS:  NAS-Port-Id         [87]  5   "278" Jun 12 11:39:14.985: RADIUS:  State               [24]  38   Jun 12 11:39:14.985: RADIUS:   21 0E 03 C7 00 00 01 37 00 01 02 00 AC 10 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 7B 20 F6 EE            [ !7 0{ ] Jun 12 11:39:14.985: RADIUS:  NAS-IP-Address      [4]   6   172.16.254.116             Jun 12 11:39:14.989: RADIUS:  Nas-Identifier      [32]  4   "ap" Jun 12 11:39:14.989: RADIUS(00000063): Sending a IPv4 Radius Packet Jun 12 11:39:14.989: RADIUS(00000063): Started 5 sec timeout Jun 12 11:39:19.597: RADIUS(00000063): Request timed out Jun 12 11:39:19.597: RADIUS: Retransmit to (172.16.0.32:1812,1813) for id 1645/18 Jun 12 11:39:19.597: RADIUS(00000063): Started 5 sec timeout Jun 12 11:39:23.981: RADIUS(00000063): Request timed out Jun 12 11:39:23.981: RADIUS: Retransmit to (172.16.0.32:1812,1813) for id 1645/18 Jun 12 11:39:23.981: RADIUS(00000063): Started 5 sec timeout Jun 12 11:39:28.365: RADIUS(00000063): Request timed out Jun 12 11:39:28.365: RADIUS: Retransmit to (172.16.0.32:1812,1813) for id 1645/18 Jun 12 11:39:28.365: RADIUS(00000063): Started 5 sec timeout Jun 12 11:39:33.005: RADIUS(00000063): Request timed out Jun 12 11:39:33.005: RADIUS: Retransmit to (172.16.0.32:1812,1813) for id 1645/18 Jun 12 11:39:33.005: RADIUS(00000063): Started 5 sec timeout Jun 12 11:39:37.389: RADIUS(00000063): Request timed out Jun 12 11:39:37.389: RADIUS: Fail-over denied to  (172.16.0.32:1812,1813) for id 1645/18 Jun 12 11:39:37.389: RADIUS: No response from (172.16.0.32:1812,1813) for id 1645/18 Jun 12 11:39:37.389: RADIUS/DECODE: No response from radius-server; parse response; FAIL Jun 12 11:39:37.389: RADIUS/DECODE: Case error(no response/ bad packet/ op decode);parse response; FAIL NPS - Event Viewer    Network Policy Server denied access to a user. Contact the Network Policy Server administrator for more information. User:     Security ID:            Empresa\WM-WSUS-998$     Account Name:            host/WM-WSUS-998.empresa.local     Account Domain:            EMPRESA     Fully Qualified Account Name:    EMPRESA\WM-WSUS-998$ Client Machine:     Security ID:            NULL SID     Account Name:            -     Fully Qualified Account Name:    -     OS-Version:            -     Called Station Identifier:        2C-3E-CF-0B-BF-60:1A     Calling Station Identifier:        001e.58a2.ba4b NAS:     NAS IPv4 Address:        172.16.254.116     NAS IPv6 Address:        -     NAS Identifier:            Aironet     NAS Port-Type:            Wireless - IEEE 802.11     NAS Port:            342 RADIUS Client:     Client Friendly Name:        Cisco Aironet - 1A     Client IP Address:            172.16.254.116 Authentication Details:     Connection Request Policy Name:    Empresa - Wireless     Network Policy Name:        -     Authentication Provider:        Windows     Authentication Server:        dc02.empresa.local     Authentication Type:        EAP     EAP Type:            -        Account Session Identifier:        -     Logging Results:            Accounting information was written to the local log file.     Reason Code:            48     Reason:                The connection request did not match any configured network policy.     Reason:                The client could not be authenticated  because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server. Solution configured one more option in Connection Request Policies - My Policy: Settings                                                                             Value Authentication Provider                                                   Local Computer Extensible Authentication Protocol Method                     Microsoft: Protected EAP (PEAP) Override Authentication                                                   Disabled Extensible Authentication Protocol Configuration    Configure @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ In Network Policies - My Policy Settings                                                                                           Value Authentication Method                                                    EAP Access Permission                                                         Grand Access Update Noncompliant Client                                           True NAP Enforcement                                                            Allow full network access Extensible Authentication Protocol Method                     Microsoft: Protected EAP (PEAP) Extensible Authentication Protocol Configuration    Configure Extended State                                                                 <Blank> BAP Percentage of Capacity                                            ReduceMultink if server reaches 50% for 2 minutes Encryption                                                                        Basic encryption (MPPE 40-bit), Strong encryption (MPPE 56-bit), Strongest encryption (MPPE 128-bit) Encryption Policy                                                             Enabled NAS Port Type                                                                 Wireless - IEEE 802.11 Source RRAS Authentication and Aironet 1600 Autonomous AP with EAP and NPS Windows 2008R2   ... View more

  Introduction  User complained that ncs server is restart, but the NCS can not start  DB and Can't use WEB interface access. the status: PCQ-NCS-01/admin# ncs status Health Monitor is running, with an error. initHealthMonitor(): can not start DB Reporting Server is Stopped Ftp Server is Stopped Database server is stopped Tftp Server is Stopped Matlab Server is Stopped NMS Server is stopped. PCQ-NCS-01/admin# ncs start Starting Network Control System... This may take a few minutes... Health Monitor is already running. Failure during Network Control System startup. Check launchout.log for details. the show-tech file   Another User shared that  he has the same problem too. PI version is 1.3. PI have not been working after rebooting hardware appliance. I have been receiving same message like hailin huang when I use command ncs status. Solution Did an SSH session happen to time out while you were in the process of upgrading or performing other actions? Hopefully you have the NCS backed up. To get it back up and running do the following from the CLI. 1. Stop the NCS 2. Run 'ncs db reinitdb' 3. Start the NCS ***WARNING*** You may lose database information but with this you should be able to get the NCS back up and running. More Information PI 1.x Health Monitor is running, with an error/NMS Server is stopped CSCuf25963 Description Symptom: PI cannot start completely after the re-setup with different hostname/IP address from that in the original setup. ------ NCS-APL-01-new/admin# ncs status Health Monitor is running, with an error. failed to start NCS on startup Health Monitor Reporting Server is running Ftp Server is running Database server is running Tftp Server is running Matlab Server is running NMS Server is stopped. SAM Daemon is running ... DA Daemon is running ... Syslog Daemon is running ... ------- Conditions: 1.2.1.12 Not happen in 1.1.X or earlier Workaround: from the root shell, update the file /opt/CSCOlumos/conf/messaging.properties with the correct ipaddress. Source https://tools.cisco.com/bugsearch/bug/CSCuf25963/?referring_site=bugquickviewredir Download software for  Network Level Service NCS Can't start DB, Can't use WEB interface access ... View more

  Introduction Cisco Prime Infrastructure - Need to use both the ports of PRIME-NCS-APL-K9. Scenario 1 The ETHERNET 2 Port in the CISCO PRIME INFRASTRUCTURE  APPLIANCE. Is it in use? Can user connect network in this port? what is the purpose of ETHERNET 2 port?     Solution Another user is using it for out of band to be able to GUI and transfer files. The only catch was that he had to set the interface ip on a different subnet than the management. Other than that, most of all the PI appliances we have used we only connect and set one interface.  More Information Q. Did you mean that this port is using like a service port in a WLC? Do you recommend the implementation of this appliance with one port ethernet? A. It isn't like a service port.... my peer needed a work around because they had to backup the server and didn't have access to the network, so they used the second port to connect directly to a laptop.  I do recommend only using one port.  "When both NICs are used, one will be for reaching the GUI for access and the other for sending SNMP traffic over to the managed devices, but most folks use just one" Adding to Rasika and Scott's correct replies, realize that the appliances are based on general purpose server platforms - the old one was IBM OEM and the new appliances are Cisco UCS-based. Those servers have a set of hardware components that are designed for general purpose requirements. When Cisco builds the Linux and ADE-OS that runs on this general purpose hardware, they don't necessarily maximize the potential use of every bit of that underlying hardware. Scenario 2 I am having NCS prime appliance. In that i have two Ethernet ports. I want to use both the ports for connectivity . Can anyone please confirm that is it possible to bond these to ports and assign a single ip to these ports. I wants to have redundancy in case of failure of links. Solution This isn't possible today.  Whether a physical or virtual NCS/Prime Infrastructure appliance, the two NICs are separate and cannot be ether channeled, NIC Teamed or combined in any other way with one IP address covering both of them. When both NICs are used, one will be for reaching the GUI for access and the other for sending SNMP traffic over to the managed devices, but most folks use just one.   If you need this functionality, please contact your Cisco SE, Cisco account team or Cisco authorised wireless reseller, and discuss it with them.  The sales side of Cisco has procedures in place to accumulate customer inputs like this across all the customers they serve, and to get that input forwarded to the various business units within Cisco for possible inclusion in future releases of Cisco's products. Q. Is it possible to assign two different IP addresses to both the ports? can any one of the IP address be reached in case of one link failure ? A. No, it's not possible for interface GigabitEthernet 0 to have an address like 10.10.10.1 and 20.20.20.1 at the same time, nor can interface GigabitEthernet 0 and interface GigabitEthernet 1 both have 10.10.10.1 at the same time.  Further, in the GUI under Administration > Appliance > Appliance Interfaces, there are drop downs to select the Management interface (the one the GUI responds on) and the Peer Server interface (the one that talks to the devices that will be managed).  Each type of interface can only have one selection at a time. Again, that's how it works today.  All sorts of things are possible with Product Enhancement Requests. Source https://supportforums.cisco.com/discussion/11856911/need-use-both-ports-prime-ncs-apl-k9  https://supportforums.cisco.com/discussion/12523586/cisco-prime-infrastructure-appliance ... View more

  Introduction This document is the home page for documents/blogs written by "Viten Patel", is working as Technical Marketing Engineer (Converged Access) at Cisco. He was working as Wireless Escalation Engineer - Cisco TAC and holds many wireless certification like CCIE Wireless, CCNP Wireless, CCNA Wireless, CWNA, CWSP, CWAP, CWNE#146. Blogs Converged Access MC managing MA Deployment Guide Converged Access Small Branch (Single switch) Best Practices / Golden Configuration Cheats  Multi-Gigabit AP Backhaul - Yes why not? 802.11ac data traffic over-the-air capture using 802.11ac and 802.11n devices Easy way to replay 802.11 frames BlockAck Mechanism and AP debugging for BlockAck exchange Wireshark 802.11 Display Filter Field Reference Prime Infrastructure WorkFlows for Converged Access -Single Switch Branch Network WorkFlow 802.11ac Transmit Beamforming and VHT NDP sounding procedure 256 QAM - 802.11ac Debugging client related issues on Cisco AireOS Documents Converged Access Workflow Lifecycle Cisco Converged Access Deployment What debugs to collect for 5760/3850 CWA issue with ISE Converting Mesh AP to Local mode and vice-versa using AP CLI 802.11ac Transmit Beamforming and VHT NDP sounding procedure  802.11ac MCS rates 802.11 Management, Control and Data frames 256 QAM - 802.11ac Low Density Parity Check (LDPC) Codes Best Practices and Golden Configs - Converged Access Branch Deployment 802.11n MAC Header vs 802.11ac MAC Header Processing AAA Error 'Out of Memory' IOS-XE controllers System Health Check for Debugging Issues SUP8E 4500 Wireless Installation Cisco PI WorkFlows for Converged Access (CA) -Single Switch Branch Network WorkFlow Video Prime Infrastructure WorkFlows for Converged Access -Single Switch Branch Network WorkFlow Additional Information Video Series- NGWC-Converged Access 5760 WLC - 3850, Converged Access mobility Video - 802.11r PSK configuration and Roaming Video - 11r-dot1x configuration and Roam Video - 11r-psk and dot1x GUI configuration ... View more

  Introduction Launch KVM Console: "Application Error - Unable to launch the application". Problem Description I have a UCS C220 M3S with CIMC 1.5(4d). When I try to launch the KVM Console, I get a popup with "Unable to launch the application". Windows 7 Firefox 33.1 Java Version 8 Update 25 Exception com.sun.deploy.net.FailedDownloadException: Unable to load resource: https://10.85.162.187:443/software/avctNuova.jar at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source) at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Wrapped Exception javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure at sun.security.ssl.Alerts.getSSLException(Unknown Source) at sun.security.ssl.Alerts.getSSLException(Unknown Source) at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source) at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.access$200(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessController.doPrivileged(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source) at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source) at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source) at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source) at com.sun.deploy.net.BasicHttpRequest.doGetRequest(Unknown Source) at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source) at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Error   Solution Downgrade to Java 7 u21 (remove the other Java versions installed) and let us know. http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html More Information KVM Console Failure Problem The KVM console fails to launch and the JRE displays the following message:  Unable to launch the application. Possible Cause This problem can be caused if several KVM consoles are launched simultaneously. Recommended Action To launch the KVM console, follow these steps: Procedure Step 1 If possible, close one or more of any open KVM consoles. Step 2 Close all open KVM consoles and relaunch the KVM console. Source Troubleshooting Issues with Cisco UCS KVM Does Not Launch After Upgrade of UCS C220 M3 Servers to 1.5(1b)  Launch KVM Console: Unable to launch the application ... View more

  Introduction Cisco Unified Computing System Manager - Fatal Error - Event Sequencing is Skewed, would you like and login again, or exit? Problem Description User is have issue with with Cisco UCS manager, after logging in UCS Manager i get an error.  User tested it with windows 2003 server and 2008 virtual machines, which does not enter sleep mode and the problem persists in order to eliminate CSCta94641 (mentioned below).  Related Bugs Fatal Error: Event Sequencing is skewed msg when coming back from sleep - CSCta94641 Problem Description: When waking up from sleep, UCSM GUI will detect an event sequencing error and display the error: "Event Sequencing is skewed", as the JRE doesn't have a sleep detection mechanism. Workaround: Always shutdown UCSM GUI before putting your computer to sleep. Known Affected Releases: 1.0(1.56) More Information Q. What UCSM version? A. Cisco UCS Manager - 2.0(1s). Q. Can you reproduce at will? If yes, what steps do you take to make this happen? A. Yes, Open the UCS manager. Q. Do you really get logged out? what happens if you just try to close the pop-up window? are you kicked out? A. I always off, close the window and closes all. Q. Any recent change in the firmware or Java version? A. 1.6 Q. Does this happen when connecting through a PC? A. Yes. really all host including laptop, pc, vm. Solution Definitely looks like a bug cause UCSM is not doing what it is supposed to and the only bug that really fits (based on the version you are running) is internal Bug CSCum95854: Defect ID Description First Bundle Affected Resolved in Release CSCum95854 Cisco UCS Manager no longer frequently closes with an "event sequencing is skewed" error. 2.2(2c)A 3.0(2c)A Known Affected Releases: 2.2(1.117)A 2.2(1.123)A Known Fixed Releases: 2.2(2c) 2.2(3a) 2.5(1a) 3.0(2c) The problem is resolved with a update to version 2.2(3g).  Relevant Information Troubleshooting Cisco UCS Manager Issues Event Sequencing Fatal Error   Problem—After coming back from sleep mode, the Cisco UCS Manager GUI displays the following message: Fatal error: event sequencing is skewed. Possible Cause—This problem can be caused if the Cisco UCS Manager GUI was running when the computer went to sleep. Since the JRE does not have a sleep detection mechanism, the system is unable to retrack all of the messages received before it went into sleep mode. After multiple retries, this event sequencing error is logged. Note Always shut down Cisco UCS Manager GUI before putting your computer to sleep. Procedure In Cisco UCS Manager GUI, if a Connection Error dialog box is displayed, click one of the following: Click Re-login to log back in to the Cisco UCS Manager GUI. Click Exit to exit the Cisco UCS Manager GUI. Source Fatal Error: Event Sequencing is skewed msg when coming back from sleep CSCta94641 Release Notes for Cisco UCS Manager, Release 3.0, for Cisco UCS Mini Cisco UCS Manager B-Series Troubleshooting Guide Troubleshooting Cisco UCS Manager Issues UCS Manager Issue ... View more

  Introduction AppleTV and Airplay does not work unless P2P is allowed. Problem Description User have WLC 5508's and 1142 and 2602 AP's.  AppleTV and Airplay will not work unless P2P is enabled on the WLAN.  BYOD is allowed and people are using P2P inappropriately. How they can get AppleTV and Airplay to work but also disable P2P?   More Information AppleTV and clients are on the same WLAN and managed by a single WLC.  The only way we been able to get the clients and AppleTV to work is to select the SSID from the WLC then go to --> advanced and change P2P Blocking Action from enabled to forward-UpStream. Solution P2P blocking can't be enabled if you want bonjour to work as it is peer to peer. I believe this has been documented in the WLC bonjour guide also. I don't think there is a way to get bonjour to work if you do want P2P blocking enabled. Details Ensure Peer-to-Peer Blocking Is Disabled Peer-to-peer blocking is configured on a per-WLAN basis and prevents clients on the wireless network from communicating with one another. By default, it is disabled for new WLANs, but if enabled, it can cause issues for services like AirPlay when the AppleTV is on the wireless network. Any Bonjour service that relies on communication between wireless clients can be broken by peer-to-peer blocking. Under the WLANs tab > Advanced section of the WLAN configuration, make sure P2P Blocking Action is set to Disabled.   Source AppleTV and Airplay not working unless I allow P2P Wireless LAN Apple Bonjour Deployment Guide ... View more

  Introduction Aironet 1142 - %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an IP ! Problem Description User wanted to configure 2 AP's for a new host name and IP address.  User tried via Serial connection and using PuTTY.  When initially connected, it went into enable mode and when tried typing in config t and it says invalid input.  User went in and reset to factory. When tried into enable mode, error message keeps popping up: Error Message %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an IP !! More Information Now, these are my commands available: Exec commands: cd Change current directory clear Reset functions clock Manage the system clock crypto Encryption related commands. debug Debugging functions (see also 'undebug') delete Delete a file dir List files on a filesystem disable Turn off privileged commands enable Turn on privileged commands exit Exit from the EXEC fsck Fsck a filesystem help Description of the interactive help system led LED functions lock Lock the terminal login Log in as a particular user logout Exit from the EXEC lwapp lwapp exec commands mkdir Create new directory monitor Monitoring different system events more Display the contents of a file name-connection Name an existing network connection no Disable debugging functions ping Send echo messages pwd Display current working directory release Release a resource reload Halt and perform a cold restart rename Rename a file renew Renew a resource rmdir Remove existing directory send Send a message to other tty lines set Set system parameter (not config) show Show running system information systat Display information about terminal lines terminal Set terminal line parameters test Test subsystems, memory, and interfaces traceroute Trace route to destination undebug Disable debugging functions (see also 'debug') upgrade Upgrade software verify Verify a file where List active connections Not sure what the next step is, and how to get rid of that message.  I do not want to connect to my WLC just yet, I just want to program via Serial since this will be on a different subnet IP than what is here, locally. Solution This is a CAPWAP AP and it can only be managed when you have Wireless LAN controller. If you want to change host name and IP via serial interface then do these: 1. Run this command "debug capwap console cli" 2. Then start using config t and run your normal command to change both. Details Before converting LWAP to Autonomous need to understand the type of OS image running on these platforms: k9w7 – autonomous IOS k9w8 – full lightweight IOS (this is what is bundled in the WLC .aes image, and is factory installed on “mesh” APs) rcvk9w8 – lightweight recovery image – this is factory installed on lightweight APs, unless a “mesh” image is specified; it lacks radio firmware. AP#sh ip int brief Interface IP-Address OK? Method Status Protocol Dot11Radio0 unassigned NO unset up up Dot11Radio1 unassigned NO unset up up GigabitEthernet0 unassigned YES DHCP up up AP#debug capwap console cli <- This command is required, otherwise LWAP will not accept the conf t AP#conf t AP(config)#ip default-gateway 10.10.10.1 AP(config)#int g0 AP(config-if)#ip address 10.10.10.1x 255.255.255.0 AP(config-if)#no sh Source AP not getting IP address from DHCP Server LWAPP to Autonomous Conversion and Vice versa on Access Points Video - LWAPP (Lightweight Mode) to Autonomous Conversion and Vice Versa  Access Point ROMMON Recovery AP: prompt Recovery Example  Discussion - Converting a lightweight AP to an autonomous AP ... View more

  Introduction This Document is written by "Viten Patel", is working as Technical Marketing Engineer (Converged Access) at Cisco. He was working as Wireless Escalation Engineer - Cisco TAC and holds many wireless certification like CCIE Wireless, CCNP Wireless, CCNA Wireless, CWNA, CWSP, CWAP, CWNE#146.  This document explains things we need to take care before getting the 4500 SUP8E up and running for Wireless. The Cisco Catalyst® 4500E Supervisor Engine 8-E is the next generation of enterprise-class switching engine that provides full convergence between wired and wireless networks on a single platform. This new Cisco® Unified Access Data Plane (UADP) application-specific integrated circuit (ASIC) powers the wireless convergence and helps enable uniform wired-wireless policy enforcement, application visibility, flexibility, and application optimization.       Requirements To get Wireless up and running on this box we have to make sure the below requirements are satisfied Check Rommon version Image should be K9 - Crypto VSS not supported Switch should run Install mode License should be Entservices or IP base In Bundle Mode Daughter card will not come up (only in install mode) Max supported APs -50 / Max supported Clients – 2000 AP should terminate on the same chassis / SUP Once you get the above up, rest of the config is similar to any 3850 / 5760 ROMMON version Lets looks at each one of them on how it looks on the output 1. Check the ROMMON version, it should be 15.1(Xr)SG4 [X - Number starting from 1] or higher BGL.I.15-4500-2#sh version ROM: 15.1(1r)SG4 BGL.I.15-4500-2 uptime is 6 minutes System returned to ROM by power-on Running default software Jawa Revision 3, RadTrooper Revision 0x0.0x41, Conan Revision 0x1449 Last reload reason: power-on Check the Image 2. Check the Image - It should be running 3.7 and should be a K9 Crypto image and nothing else will work CRYPTO image looks like this - 4500-2#sh version Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500es8-UNIVERSALK9-M), Version 03.07.00E RELEASE SOFTWARE (fc4) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2014 by Cisco Systems, Inc. Compiled Sun 07-Dec-14 17:59 by prod_rel_team NON CRYPTO image looks like this - Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500es8-UNIVERSAL-M), Version 03.03.00.XO RELEASE SOFTWARE (fc2) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2013 by Cisco Systems, Inc. Compiled Wed 14-Aug-13 09:51 by prod_rel_team VSS Status 3. Make Sure VSS is not enabled (If VSS enabled wireless commands will not be preset and the vise versa if Wireless is enabled VSS commands are not present) 4500-2#sh switch virtual Switch Mode : Standalone Not in Virtual Switch mode due to: Domain ID is not configured Install Mode and not in Bundle Mode 4. Make Sure the Switch is running in Install Mode and not in Bundle Mode Bundle Mode - bootsystem pointing to .bin image (no wireless commands) Install Mode - Bootsystem pointing to package.conf instead of Bin BGL.I.15-4500-2#dir bootflash: In Bundle Mode Directory of bootflash:/ 81602 -rw- 181583336 Oct 7 2014 09:18:45 +00:00 cat4500es8-universal.SPA.03.03.00.XO.151-1.XO.bin 81603 -rw- 181601128 Nov 18 2014 18:28:43 +00:00 cat4500es8-universal.SPA.03.03.02.XO.151-1.XO2.bin 81604 -rw- 483862876 Dec 31 2014 20:21:43 +00:00 cat4500es8-universalk9.SPA.03.07.00.E.152-3.E.bin 1708220416 bytes total (857677824 bytes free) This is how the boot looks like 4500-2#sh boot --------------------------- Switch 1 --------------------------- Current Boot Variables: BOOT variable = flash:cat4500es8-universal.SPA.03.07.00.E.152-3.E.bin; Boot Variables on next reload: BOOT variable = flash:cat4500es8-universal.SPA.03.07.00.E.152-3.E.bin; Allow Dev Key = yes Manual Boot = no Enable Break = no In Install Mode BGL.I.20-4500-1#dir bootflash: Directory of bootflash:/ 81602 -rwx 199051336 Oct 7 2014 02:00:02 +00:00 cat4500es8-universalk9.SPA.03.06.00.E.152-2.E.bin 81603 -rw- 215049252 Dec 29 2014 07:07:31 +00:00 cat4500es8-universal.SPA.03.07.00.E.152-3.E.bin 16 drwx 4096 Dec 29 2014 07:14:26 +00:00 virtual-instance 18 drwx 4096 Dec 29 2014 07:14:26 +00:00 virtual-instance-stby-sync 81606 drwx 4096 Dec 30 2014 01:52:34 +00:00 wnweb_store 21 -rw- 126880776 Dec 30 2014 01:34:38 +00:00 cat4500es8-base.SPA.03.07.00E.pkg 57125 -rw- 82245776 Dec 30 2014 01:34:45 +00:00 cat4500es8-dc-base.SPA.03.07.00E.pkg 57126 -rw- 7019480 Dec 30 2014 01:34:47 +00:00 cat4500es8-dc-drivers.SPA.03.07.00E.pkg 57127 -rw- 35161204 Dec 30 2014 01:34:46 +00:00 cat4500es8-dc-infra.SPA.03.07.00E.pkg 81604 -rw- 483862876 Dec 30 2014 01:24:49 +00:00 cat4500es8-universalk9.SPA.03.07.00.E.152-3.E.bin 57128 -rw- 26876920 Dec 30 2014 01:34:47 +00:00 cat4500es8-dc-platform.SPA.03.07.00E.pkg 57129 -rw- 4225328 Dec 30 2014 01:34:39 +00:00 cat4500es8-firmware.SPA.03.07.00E.pkg 57130 -rw- 54192 Dec 30 2014 01:34:39 +00:00 cat4500es8-infra.SPA.03.07.00E.pkg 57131 -rw- 1987552 Dec 30 2014 01:34:47 +00:00 cat4500es8-platform.SPA.03.07.00E.pkg 57132 -rw- 88661144 Dec 30 2014 01:34:42 +00:00 cat4500es8-universalk9.SPA.152-3.E.pkg 57133 -rw- 110742524 Dec 30 2014 01:34:51 +00:00 cat4500es8-wcm.SPA.10.3.100.0.pkg 20 -rw- 1724 Dec 30 2014 01:35:59 +00:00 packages.conf 81605 ---- 11679 Dec 31 2014 23:15:15 +00:00 dc_console_log-20141230-014159-UTC 1708220416 bytes total (321839104 bytes free) BGL.I.20-4500-1# 4500-2#sh run | i boot boot-start-marker boot system bootflash:packages.conf boot-end-marker BGL.I.15-4500-2#sh boot BOOT variable = bootflash:packages.conf,12; CONFIG_FILE variable does not exist BOOTLDR variable does not exist Configuration register is 0x2102 Converting Bundle 5. How to convert Bundle to Install Converting from the Bundle Running Mode to the Installed Running Mode License  6. License should be either Entservices or IP base (once we enable Entservices and reboot we wil then see AP-count in the RTU BGL.I.15-4500-2#sh license right-to-use License Store: Primary License Storage License Store: Dynamic License Storage StoreIndex: 1 Feature: entservices Version: 1.0 License Type: PermanentRightToUse License State: Inactive License Count: Non-Counted StoreIndex: 3 Feature: ipbase Version: 1.0 License Type: PermanentRightToUse License State: Inactive License Count: Non-Counted StoreIndex: 4 Feature: lanbase Version: 1.0 License Type: PermanentRightToUse License State: Active, Not in Use, EULA not accepted License Count: Non-Counted StoreIndex: 6 Feature: apcount Version: 1.0 License Type: PermanentRightToUse License State: Inactive License Count: 0/0 4500-2#license right-to-use activate entservices acceptEula (Requires Reboot) BGL.I.15-4500-2#sh license right-to-use License Store: Primary License Storage License Store: Dynamic License Storage StoreIndex: 1 Feature: entservices Version: 1.0 License Type: PermanentRightToUse License State: Active, In Use License Count: Non-Counted StoreIndex: 3 Feature: ipbase Version: 1.0 License Type: PermanentRightToUse License State: Inactive License Count: Non-Counted StoreIndex: 4 Feature: lanbase Version: 1.0 License Type: PermanentRightToUse License State: Active, Not in Use, EULA not accepted License Count: Non-Counted StoreIndex: 6 Feature: apcount Version: 1.0 License Type: PermanentRightToUse License State: Inactive License Count: 0/0 Device running in Bundle Mode 7. If the Device is running in Bundle Mode the Daughter Card which is required for Wireless will not come up.. this can be verified using show module command. daughter card failures are considered as SUP failures and may require an RMA While the device is booting we will see Cisco IOS-XE software, Copyright (c) 2005-2014 by cisco Systems, Inc. All rights reserved. Certain components of Cisco IOS-XE software are licensed under the GNU General Public License ("GPL") Version 2.0. The software code licensed under GPL Version 2.0 is free software that comes with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such GPL code under the terms of GPL Version 2.0. (http://www.gnu.org/licenses/gpl-2.0.html) For more details, see the documentation or "License Notice" file accompanying the IOS-XE software, or the applicable URL provided on the flyer accompanying the IOS-XE software. Daughter Card is booting.. Please stand by .............................................. Daughter Card is ready, continuing in wireless mode.. BGL.I.20-4500-1#sh module Chassis Type : WS-C4510R+E Power consumed by backplane : 40 Watts Mod Ports Card Type Model Serial No. ---+-----+--------------------------------------+------------------+----------- 2 2 1000BaseX (GBIC) WS-X4302-GB JAE10307QDW 3 48 10/100/1000BaseT POE E Series WS-X4648-RJ45V-E JAE1211B9K2 4 6 1000BaseX (GBIC) WS-X4306 JAE053700PA 5 12 Sup 8-E 10GE (SFP+), 1000BaseX (SFP) WS-X45-SUP8-E CAT1814L3A7 M MAC addresses Hw Fw Sw Status --+--------------------------------+---+------------+----------------+--------- 2 0015.62e6.e2b8 to 0015.62e6.e2b9 3.2 Ok 3 001e.7af2.95f0 to 001e.7af2.961f 1.0 Ok 4 0004.4dfb.87c4 to 0004.4dfb.87c9 2.0 Ok 5 70ca.9b5e.6600 to 70ca.9b5e.660b 1.1 15.1(1r)SG4 03.07.00E Ok Mod Redundancy role Operating mode Redundancy status ----+-------------------+-------------------+---------------------------------- 5 Active Supervisor RPR Active Mod Submodule Model Serial No. Hw Status ----+-----------------------+-----------------+------------+----+--------- 5 Daughter Card WS-UA-SUP8E CAT1814L5H1 1.0 Ok 3850 GUI 8. Once above things are taken care of, the rest of the things are similar to getting 3850 up and running Here is the GUI     More Information Cisco Catalyst 4500E Supervisor Engine 8-E: Wired and Wireless Convergence Data Sheet Cisco Catalyst 4500 Supervisor Engine 8-E Wireless Mode Quick-Start Guide Installation and Configuration Note for the Cisco Catalyst 4500 E-Series Supervisor Engine 8-E ... View more

This Blog is written by "Viten Patel", is working as Technical Marketing Engineer (Converged Access) at Cisco. He was working as Wireless Escalation Engineer - Cisco TAC and holds many wireless certification like CCIE Wireless, CCNP Wireless, CCNA Wireless, CWNA, CWSP, CWAP, CWNE#146.   ... View more

  Video - "FastLocate (Packet RSSI Location)" by Jerome Henry and James Noxon, Technical Marketing Engineer, Enterprise Networking Market Strategy, Cisco Systems Inc. ... View more

        Video - Presence Analytics by James Noxon, Technical Marketing Engineer, Enterprise Networking Market Strategy, Cisco Systems Inc. ... View more