Planning WISM to WISM2
Hello,
I hope my english is comprehensible. I have an environment with 2 WISM (4 logical controller) and about 450 APs. Both WISMs have the same configuration. Now I want to migrate the whole thing on 2 WISM-2. I've designed the following scheme and I would like to have confirmed whether this can work this way. The migration should take place during operations, but single APs can fail at short times.
-First, move all the APs on 3 logic controllers, so that one controller is empty
-then update the firmware of the empty controller from version 7.0.116.0 to 7.0.230.0 (bring the WISM-2 on the same version 7.0.230.0, too)
-export the configuration of the empty WISM and import it on the WISM-2
-updating the firmware version of the WISM-2 to the current version (7.2.x.x)
-then change the APs with older version 7.0.116.0 bit by bit from the 3 WISMs to the new WISM-2 with version 7.2.x.x (if it works)
Is that possible, and to recommend, or is there a better alternative for the migration?
Because upgrading the WiSM-2 FUS takes about 20 minutes, I'd be leaving the WAPs with the WiSM-1 and upgrading the WiSM-2 FUS and the firmware to 7.2.110.0.
Once the WiSM-2 upgrades are complete, swing the WAPs across.
Now I know that by doing it this way, the WAPs will go offline because of the software upgrades from the WiSM-2 but I believe it's better this way because it's the same anyway. Whether you use the orignal method or not, the WAPs will still reboot.
This changes if, say, you the WiSM-2 in the same code level as the WiSM-1.
Similar Messages
-
Hi, next week I am going to a customer and upgrade his wireless installation. From a WISM / WCS system to a WISM2 / Cisco Prime Infrastructure system. Does anyone have any best practice advice in such scenarios? Exchange the WISM with the WISM2 first or upgrade the WCS to Cisco Prime Infrastructure first? Or just start over from scratch :-)
Hans JørgenWhat I would do, is migrate the WiSM to WiSM2 first. Put the WiSM2 on the same code version as WiSM, and move the AP's. Run in parallel for a bit just to make sure everything is stable.
Join the WiSM2 to WCS, hopefully the code supports it. Once you have that done, then use the export command to pull the data out of WCS. Load up your VM, medium or large no point doing a small, and import the data from WCS.
What I've found is that 1.2 does not have the import availability, so it would be two staged to get from WCS to Prime. WCS to NCS 1.1, then upgrade 1.1 to 1.2.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered -
Unable to access WEB UI of WiSM2
Bear with me as this is my first install of a 6500 and WiSM module.
The backgroud is that we are small, but management used to be in networking and basically forced the the purchase of a 6509E. Most of my experience is with 3560X and 2950 switches.
I have followed the basic deployment guide here:http://www.cisco.com/c/en/us/support/docs/interfaces-modules/catalyst-6500-series-7600-series-wireless-services-module-wism/112968-wism2-deploy-guide-00.html. My problem is that I have a flat network (see why I didn't want a 6500) so the management network and the production network is on VLAN 1. Yes I know how bad this is, but apparently wireless is more important than adhering to good security practices.
My problem is I am unable to access the Web UI of the controller. I am however able to ping the address for the management IP. I will give as much output as I can think would be helpful right now (and more if needed), but any assistance I can get would be appreciated.
#show module
Mod Ports Card Type Model Serial No.
2 4 WiSM 2 WLAN Service Module WS-SVC-WISM2-K9 SAL172579DM
6 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL1706YCQJ
Mod MAC addresses Hw Fw Sw Status
2 30f7.0d0b.9820 to 30f7.0d0b.982f 1.1 12.2(18r)S1 15.1(1)SY1 Ok
6 ccef.4838.97d5 to ccef.4838.97dc 1.4 12.2(50r)SYS 15.1(1)SY1 Ok
Mod Sub-Module Model Serial Hw Status
6 Policy Feature Card 4 VS-F6K-PFC4 SAL17299W2L 2.1 Ok
6 CPU Daughterboard VS-F6K-MSFC5 SAL1706YBTQ 1.5 Ok
Mod Online Diag Status
2 Pass
6 Pass
#sh wism module 2 controller 1 st
WiSM Controller 1 in Slot 2 configured with auto-lag
Operational Status of the Controller : Oper-Up
Service VLAN : 50
Service Port : 3
Service Port Mac Address : 6c20.562c.2c61
Service IP Address : 192.168.2.51
Management IP Address : 40.96.0.2
Software Version : 7.0.116.0
Port Channel Number : 403
Allowed-vlan list : 1
Native VLAN ID : 1
WCP Keep Alive Missed : 0
#do sh wism st
Service Vlan : 50, Service IP Subnet : 192.168.2.1/255.255.254.0
WLAN
Slot Controller Service IP Management IP SW Version Controller Type Status
----+-----------+----------------+----------------+------------+------------------+---------------
2 1 192.168.2.51 40.96.0.2 7.0.116.0 WS-SVC-WISM-2-K9 Oper-Up
HQR1#sh ip int brief
Interface IP-Address OK? Method Status Protocol
TenGigabitEthernet2/1 unassigned YES unset up up
TenGigabitEthernet2/2 unassigned YES unset down down
GigabitEthernet2/3 unassigned YES unset up up
GigabitEthernet2/4 unassigned YES unset administratively down down
GigabitEthernet6/1 unassigned YES unset up up
GigabitEthernet6/2 unassigned YES unset down down
GigabitEthernet6/3 unassigned YES unset down down
TenGigabitEthernet6/4 unassigned YES NVRAM administratively down down
TenGigabitEthernet6/5 unassigned YES NVRAM administratively down down
Port-channel403 unassigned YES unset up up
Vlan1 40.96.0.1 YES NVRAM up up
Vlan50 192.168.2.1 YES NVRAM up upWell I feel stupid, apparrently, either by default or by my commands "Web mode" and Secure Web Mode" was disabled. after enabling, it works.
-
If you drilll down in the POODLE security advisory ( Advisory ID: cisco-sa-20141015-poodle) into the Affected products and then to the vulnerable produst and almost at the end you find
Cisco Wireless LAN Controller (WLC) [CSCur27551]
If you open up this bug report it ONLY identifies and lists the 5508. So... does this mean that none of the other controllers such as the 4400.2500, WiSM and WiSM2 are effected? Kind of difficult to beleive since they are are interrelated (at least the 5508 and WiSM2).
Anyone know?
Thanks!Hmmm, two answers for which WLC's are vulnerable, both marked correct and contradicting each other. I have to wonder why Cisco only listed the 5508 in the bug report and only listed 2 versions of RTOS. I hate to make assumptions even if they seem to make sense so hopefully Cisco will update and revise the advisory...
Thanks! -
Hi all,
I plan to replace 2 x WISM1 (WLC 6.0.182) by 2 x WISM2 (WLC 7.2.115.1). One WISM in each Catalyst 6500. I am sorry it is a little long but I have no lab and I need your advice.
Summarized migration plan is the following :
Upgrade of the 4 WLC (WISM1) from 6.0.182 to 7.0.240
AP pre-download from the 4 WLC (WISM1)
Transfert WLC 7.0.240 image to the 4 WLC (last compatible version)
Transfert WLC 7.0.240 image from the 4 WLC to AP and swap AP primary and secondary image
So, AP primary image is 7.0.240, AP secondary image is 6.0.182
Scheduled reboot of the 4 WLC
So, 4 WLC (WISM1) and AP are running WLC 7.0.240
Move AP from the 2 WLC of the1st WISM1 to the 2 WLC of 2sd WISM1 Swap AP primary and secondary controller with NCS
Backup the configuration file
of one WLC of the 1st WISM1
of one WLC of the 2st WISM1
Replace the 1st WISM1 by one WISM2
WISM2 upgrade from the current WLC version to 7.0.240
Import the saved configuration file (WISM1) to WISM2 (7.0.240)
Check the configuration via HTTPS
Move AP from the 2 WLC of the 2sd WISM1 to the 1st WISM2 Swap AP primary and secondary controller with NCS
Replace the 2sd WISM1 by one WISM2
WISM2 upgrade from the current WLC version to 7.0.240
Import the saved configuration file (WISM1) to WISM2 (7.0.240)
Check the configuration via HTTPS
Upgrade WISM2 from 7.0.240 to 7.2.115.1
AP pre-download etc.
etc.
Please, what do you think about this migration plan ?
Do you have a better/simplier solution ?
ThanksAlso you would enable Authorize MIC APs against auth-list to avoid AP's fallback to the WiSM1. So, if I understand you, it would be enable on WISM1. This way AP's trying to fallback to the WISM1 will be refused and reconnect to the WISM2 that's right ?
Yes... this will prevent access point from joining the WiSM1... AP's that are already on WiSM1 will stay, it just prevents any AP's that has already been migrated to WiSM2 to fail to WiSM1.
How can I get the configuration from WiSM1 to the WiSM2 ?
Well you would backup your config and open it up in a text editor... then you would edit the file, by changing the hostname and ip address, etc. Make sure you have a trailing space at the end of each command that you change. This is important or else the config will not take. Also you will have to edit the password for the management since it is encrypted in the backup config. replace it with:
config mgmtuser password
Save the config and do a restore on the WiSM2 and verify that the setting are okay prior to moving all the ap's over. I would move one to test your wlans and make sure its fine before moving more.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered" -
IPv6 for management and control plane on WLCs and LWAPs
Good morning, everybody!
I am trying to find answer to a question that has been previously asked by people but never successfully answered
The question is about IPv6 support on Cisco Wireless LAN Controllers and access points... Does Cisco have a roadmap to include support for IPv6 used in CAPWAP, control plane and management? There are couple of posts on this topic that do not unfortunately provide any answer to this point.
https://supportforums.cisco.com/message/3018843
https://supportforums.cisco.com/docs/DOC-15667
Infamous "Cisco IPv6 Solution" at http://www.cisco.com/en/US/partner/technologies/collateral/tk648/tk872/tk373/technologies_white_paper_09186a00802219bc_ps6553_Products_White_Paper.html briefly states "Wireless Solutions... In future, IPv6 control plane features may get added to those components."
Has anyone heard of any more specific roadmap for IPv6 support for CAPWAP, control plane and management on WLCs and LWAPs?Full ipv6 support will never be available on the Wism and 440x controllers because they have a NPU to forward traffic and it was not designed with ipv6 in mind.
The 5508 and Wism2 and all new controllers all have CPU based forwarding and ipv6 is coming in next releases.
WLC 8.0 is only for december 2011/2012 and I have to say I don't know if it will support native ipv6.
my 2 cents -
Hi experts,
We are in middle of deploying WiSM2s on our network, from a design point of view i am confused on where to position the WiSM2s. We have 2 DCs and from best practice architecture view WLCs should not be placed on the Data Centre segment, but it seems that is the only option i have.
DCs host 6509s, i am planning to host 1 WiSM in each DC, all clients will be on seperate subnet. Do you foresee any issues with this deployment or any security issues?
authentications are followed as per cisco recommendation, clients authenticated against AD through ACS so it is fairly secure. Will appreciate any advice.
Cheers
APAmar,
Since you are going to install the WISM2 you will be limited to where your chassis is physically installed. If we are operating under the assumption that all, or at least most, of the traffic sent to the WISM2 will eventually hit the data center I do not se a reason to move them. On the other hand if you have a lot of peer to peer wireless traffic such as voice calls and pages you may want to consider some HREAP configuration. Placement of the WISM2 will not have any affect on the authentication/encryption that you will use. Ideally when planning a new WLC/WISM(2) deployment I like to use all local mode APs with a WLC/WISM(2) at each site as well as a WLC in the DMZ to use as a mobility anchor. If you provide more specific details such as client type, traffic path, and number of clients per location I can help you with something more specific to your design.
Thanks, -
Hi,
I'm seeing the following error on our clients WiSM (WS-SVC-WISM2-K9) installed in a 6500 chassis:
*dtlDataLowTask: Mar 10 08:50:21.088: %SYSTEM-3-MBUFF_ALL_USED: sysapi_if_net.c:223 No free Mbufs available.Shared memory allocation failed. Internal system error. *dtlArpTask: Mar 10 08:50:19.084: %SYSTEM-3-MBUF_ALLOC_FAIL: sysapi_if_net.c:602 Cannot allocate new Mbuf.Internal system error.
I've taken a look through cisco.com and there are known issues but no fixes but only on WLC's rather than WiSM. Has anyone ever seen this issue before on WiSM?
Regards
NeilMay be you are hitting a bug.
Must contatc TAC and provides the log.
Regards -
Hi everyone
I cannot login the wism2 with browser.
But I can use command to login the wism.
like this:
VSS-6509#session switch 2 slot 9 processor 1
The default escape character is Ctrl-^, then x.
You can also type 'exit' at the remote prompt to end the session
Trying 172.16.31.2 ... Open
User:admin
Password:*********
(WiSM-slot41-1) >
notice:Sometimes I can login via the web.The interface and ip address configuration were correct.
WISM2 log:
*emWeb: Mar 08 05:20:38.189: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 05:04:38.105: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 04:48:38.032: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 04:32:37.951: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 04:16:37.861: #CLI-3-LOGIN_FAILED: cliutil.c:653 Login failed. User:nouser, Service type:-8. excessive failed login attempts.
*emWeb: Mar 08 04:16:37.861: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 04:00:37.780: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 03:44:37.708: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 03:28:37.623: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 03:12:37.550: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 02:56:37.482: #CLI-3-LOGIN_FAILED: cliutil.c:653 Login failed. User:nouser, Service type:-8. excessive failed login attempts.
*emWeb: Mar 08 02:56:37.482: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 02:40:37.396: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 02:24:37.308: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 02:08:37.191: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 01:52:37.103: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 01:36:37.022: #CLI-3-LOGIN_FAILED: cliutil.c:653 Login failed. User:nouser, Service type:-8. excessive failed login attempts.
*emWeb: Mar 08 01:36:37.022: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 01:20:36.951: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 01:04:36.853: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 characters.
*emWeb: Mar 08 00:48:35.253: #CLI-3-LOGIN_FAILED: cliutil.c:576 Login failed. User:nouser, Service type:-8. Username/Password length must be between 3 and 24 charYou have radius setup for managment? If you have radius setup, make sure you don't have the managmeent check box enabled unless you are using TACACS or Radius for management users. Seem's like radius if sending a reject back to the WLC.
-
Cisco AP 2702 can't join WiSM2 7.6.130.0
i got these msg log from AP. AP got ip address but can't discover WiSM2. other model 3502/2602 it's ok.
IOS Bootloader - Starting system.
flash is writable
Antigua Board
40MB format
Tide XL MB - 40MB of flash
Xmodem file system is available.
flashfs[0]: 13 files, 2 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 41158656
flashfs[0]: Bytes used: 6153216
flashfs[0]: Bytes available: 35005440
flashfs[0]: flashfs fsck took 9 seconds.
Base Ethernet MAC address: d4:6d:50:f9:eb:00
Ethernet speed is 100 Mb - FULL Duplex
Loading "flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-mx"...#########################
File "flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-mx" uncompressed and installed, entry point: 0x2003000
executing...
Secondary Bootloader - Starting system.
Antigua Board Pre-Pilot
40MB format
Tide XL MB - 40MB of flash
Xmodem file system is available.
flashfs[0]: 13 files, 2 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 41158656
flashfs[0]: Bytes used: 6153216
flashfs[0]: Bytes available: 35005440
flashfs[0]: flashfs fsck took 10 seconds.
flashfs[1]: 0 files, 1 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 12257280
flashfs[1]: Bytes used: 1024
flashfs[1]: Bytes available: 12256256
flashfs[1]: flashfs fsck took 0 seconds.
Base Ethernet MAC address: d4:6d:50:f9:eb:00
Boot CMD: 'boot flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-xx;flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-xx'
Loading "flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-xx"...########################
File "flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-xx" uncompressed and installed, entry point: 0x1003000
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, C2700 Software (AP3G2-RCVK9W8-M), Version 15.3(3)JA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 15-Aug-14 12:27 by prod_rel_team
Antigua Board Pre-Pilot
40MB format
Tide XL MB - 40MB of flash
Initializing flashfs...
flashfs[2]: 13 files, 2 directories
flashfs[2]: 0 orphaned files, 0 orphaned directories
flashfs[2]: Total bytes: 40900608
flashfs[2]: Bytes used: 6153216
flashfs[2]: Bytes available: 34747392
flashfs[2]: flashfs fsck took 11 seconds.
flashfs[2]: Initialization complete.
flashfs[3]: 0 files, 1 directories
flashfs[3]: 0 orphaned files, 0 orphaned directories
flashfs[3]: Total bytes: 11999232
flashfs[3]: Bytes used: 1024
flashfs[3]: Bytes available: 11998208
flashfs[3]: flashfs fsck took 0 seconds.
flashfs[3]: Initialization complete....done Initializing flashfs.
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-CAP2702E-C-K9 (PowerPC) processor (revision A0) with 376810K/134656K bytes of memory.
Processor board ID FGL1849XBEM
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 8.0.72.236
1 Gigabit Ethernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: D4:6D:50:F9:EB:00
Part Number : 73-15823-03
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC18474C56
Top Assembly Part Number : 800-41175-02
Top Assembly Serial Number : FGL1849XBEM
Top Revision Number : A0
Product/Model Number : AIR-CAP2702E-C-K9
% Please define a domain-name first.
ipv6 enable
^
% Invalid input detected at '^' marker.
ipv6 address autoconfig
^
% Invalid input detected at '^' marker.
ipv6 address dhcp
^
% Invalid input detected at '^' marker.
Press RETURN to get started!
*Mar 1 00:00:13.071: APAVC: Initial WLAN Buffers Given to System is 2500
*Mar 1 00:00:13.119: APAVC: WlanPAKs 42878 RadioPaks 42270
*Mar 1 00:00:13.119: Starting Ethernet promiscuous mode
*Mar 1 00:00:13.127: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
*Mar 1 00:00:15.119: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:15.119: %LINK-6-UPDOWN: Interface GigabitEthernet1, changed state to up
*Mar 1 00:00:15.259: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C2700 Software (AP3G2-RCVK9W8-M), Version 15.3(3)JA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 15-Aug-14 12:27 by prod_rel_team
*Mar 1 00:00:15.295: %CDP_PD-4-POWER_OK: Full power - HIGH_POWER inline power source
*Mar 1 00:00:15.303: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
lwapp_crypto_init: MIC Present and Parsed Successfully
*Mar 1 00:00:15.443: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:16.287: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:20.083: DPAA Initialization Complete
*Mar 1 00:00:20.083: %SYS-3-HARIKARI: Process DPAA INIT top-level routine exited
*Mar 1 00:00:21.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:23.083: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Mar 1 00:00:24.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
*Mar 1 00:00:27.291: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Mar 1 00:00:28.291: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:29.259: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.201.1.184, mask 255.255.255.0, hostname APd46d.50f9.eb00
bridge-group 1 source-learning
^
% Invalid input detected at '^' marker.
%Default route without gateway, if not a point-to-point interface, may impact performance
*Mar 1 00:00:34.123: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
%Error opening flash:/capwap-saved-config (No such file or directory)
APd46d.50f9.eb00#sh version
Cisco IOS Software, C2700 Software (AP3G2-RCVK9W8-M), Version 15.3(3)JA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 15-Aug-14 12:27 by prod_rel_team
ROM: Bootstrap program is C2700 boot loader
BOOTLDR: C2700 Boot Loader (AP3G2-BOOT-M) LoaderVersion 15.2(4)JB5m, RELEASE SOFTWARE (fc2)
APd46d.50f9.eb00 uptime is 4 minutes
System returned to ROM by power-on
System image file is "flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-xx"
cisco AIR-CAP2702E-C-K9 (PowerPC) processor (revision A0) with 376810K/134656K bytes of memory.
Processor board ID FGL1849XBEM
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 8.0.72.236
1 Gigabit Ethernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: D4:6D:50:F9:EB:00
Part Number : 73-15823-03
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC18474C56
Top Assembly Part Number : 800-41175-02
Top Assembly Serial Number : FGL1849XBEM
Top Revision Number : A0
Product/Model Number : AIR-CAP2702E-C-K9
Configuration register is 0xF
================
APd46d.50f9.eb00#show ip interface brief
Interface IP-Address OK? Method Status Protocol
BVI1 10.201.1.184 YES DHCP up up
GigabitEthernet0 unassigned NO unset up up
GigabitEthernet1 unassigned NO unset up down
===============
(WiSM-slot4-1) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.130.0
Bootloader Version............................... 1.0.16
Field Recovery Image Version..................... 7.0.43.32
Firmware Version................................. FPGA 1.6, Env 0.0, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... WISM2
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1293
Redundancy Mode.................................. Disabled
IP Address....................................... 10.201.255.250
Last Reset....................................... Software reset
System Up Time................................... 1 days 16 hrs 59 mins 28 secs
System Timezone Location......................... (GMT +8:00) HongKong, Bejing, Chongquing
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... MY - Malaysia
still got log:
Not in Bound state.
*Mar 1 02:59:49.139: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 02:59:52.211: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.201.1.184, mask 255.255.255.0, hostname APd46d.50f9.eb00
Not in Bound state.
*Mar 1 03:00:45.639: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 03:00:48.711: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.201.1.184, mask 255.255.255.0, hostname APd46d.50f9.eb00Hello
we had this problem too. I've figured out that the AP's which came factory preloaded with the
LWAPP image version
PRE { font-family: "Liberation Serif",serif; }P { margin-bottom: 0.08in; }
8.0.72.236 and 15.3(3) JA (without 1)
Version 15.3(3)JA
LWAPP image version 8.0.72.236
remained stuck on
*Mar 1 00:09:24.639: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 00:09:28.735: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.0.60, mask 255.255.255.0, hostname AP881d.fcaf.a71c
Not in Bound state.
*Mar 1 00:10:21.139: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.######### ######### ip IP information
In our case we wanted to use the DNS Entry CISCO-CAPWAP-CONTROLLER.domain.name to discover the controller. As older APs (1240) were able to connect I tried with the recovery image (downloaded on Support)
15.3(3)JA1 containing
PRE { font-family: "Liberation Serif",serif; }P { margin-bottom: 0.08in; }
Version Suffix: k9w8-.153-3.JA1 8.0.110.0
Image Name: ap3g2-k9w8-mx.153-3.JA1
Version Directory: ap3g2-k9w8-mx.153-3.JA1
Ios Image Size: 11407872
Total Image Size: 13496832
Image Feature: WIRELESS LAN|LWAPP
Image Family: AP3G2
Wireless Switch Management Version: 8.0.110.0
with this image the AP could join the Controller via DNS.
So If you have an AP preloaded with Image 15.3.JA (without 1) try this:
ping CISCO-CAPWAP-CONTROLLER.localdomain as stated by mykhuzaimi above
OR
capwap ap controller ip address <IP-address> as stated by mykhuzaim above
set option 43
Load image ap3g2-rcvk9w8-tar.153-3.JA1.tar
Unfortunately all workaround require manual interventions......
Saluti Mauro -
Hello,
I have next issue:
When i was trying to configure redundancy, i lost access to wism2 module. When i ping service port, it reply me, but i unable to get access via "session slot proc".
some brief information:
cisco WS-C6509-E
SN-1#sh module
Mod Ports Card Type Model Serial No.
2 4 WiSM 2 WLAN Service Module WS-SVC-WISM2-K9 SAL1739DEGF
5 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL1739D9EL
SN-1#sh run | i wism
wism service-vlan 222
wism module 2 controller 1 allowed-vlan 1-1001,1006-4094
SN-1#sh wism module 2 controller 1 status
WiSM Controller 1 in Slot 2 configured with auto-lag
Operational Status of the Controller : Oper-Up
Service VLAN : 222
Service Port : 3
Service Port Mac Address : 6c20.562c.5a61
Service IP Address : 192.168.1.101
Management IP Address : 10.32.252.21
Software Version : 7.5.102.0
Port Channel Number : 547
Allowed-vlan list : 1-1001,1006-4094
Native VLAN ID : 1
WCP Keep Alive Missed : 0
any idea?Also, a have found a difference between second wism2 module
SN-1(config)#do sh wism module 2 cont 1 sta
WiSM Controller 1 in Slot 2 configured with auto-lag
Operational Status of the Controller : Oper-Up
Service VLAN : 999
Service Port : 3
Service Port Mac Address : 6c20.562c.5a61
Service IP Address : 192.168.1.101
Management IP Address : 10.32.252.21
Software Version : 7.5.102.0
Port Channel Number : 547
Allowed-vlan list : 1-1001,1006-4094
Native VLAN ID : 1
WCP Keep Alive Missed : 0
SN-2#sh wism module 2 controller 1 status
WiSM Controller 1 in Slot 2 configured with auto-lag
Operational Status of the Controller : Oper-Up
Service VLAN : 999
Service Port : 3
Service Port Mac Address : 6c20.562c.4b61
Service IP Address : 192.168.1.102
Management IP Address : 10.32.252.12
Software Version : 7.5.102.0
Port Channel Number : 547
Allowed-vlan list : 1-1000,1006-4094
WCP Keep Alive Missed : 0
As you can see there is no native vlan on working wism and i cant turn off it on unavailable wism. -
Wism2 in High Availability - FUS Upgrade
Hello all,
what is the procedure to be followed when upgrading the FUS on a WISM-2 in HA cluster?
Is it the same procedure that applies when upgrading the wism's code in HA?
Thank you
Edited:
The procedure is exactly the same as upgrading. First upgrade the image and then FUS.make sure that you are connected using console connection and definitely perform this within a maintenance window of at least 1 hour.Hi,
Thanks for sharing this info.
Snipped from this guide also explains how its done:
https://supportforums.cisco.com/discussion/12190806/wism2-high-availability-fus-upgrade
The FUS image can be upgraded while the controllers have HA enabled. The secondary controller will
get upgraded just like it does when upgrading the regular code. However, when you initiate the reboot
on the primary controller both controllers will be unreachable until the FUS upgrade completes on both
the active and the standby in the HA pair. This process will take around 30 to 40 minutes to complete
just like in a non-HA FUS upgrade. -
Why is the WiSM2 not recomended in the Sup slots?
I have a situation where a customer doesn't have the required power units installed in theior 6500 for me to provision a WiSM2.
They use a VSS paiur with a single Sup720 in each. They have no intention of adding a second Sup to each chassis.
I need to justify why they can't use slot 6 (which has power reserverd) if I am to get them to upgrade the PSU's. The documentation I've found says it is supported but not recomended. Does anyone know of any cast iron reason why this is not recomended.
Cheers in advance
RhodriWiSM2 Power Requirements
http://www.cisco.com/en/US/docs/wireless/module/wism2/installation/note/WiSM_2.html#wp73014
WiSM2, Initial System Configuration with Sup 720
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_tech_note09186a0080bb2500.shtml#init-syst
Configuring Sup720 or 2T and WiSM-2 communication in a VSS mode
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_tech_note09186a0080bb2500.shtml#t6 -
WiSM Switch - Questions about Client Connections
Hello!
i?m planning a worst case scenario for a customer site. They got a couple of 6500?s with WiSM Modules installed. Now I?m sitting over a instruction of what to do when a WiSM breaks down and I got a few questions regarding the clients.
In the case a Controller stops responding, the AP?s are automatically switched to the secondary Controllers. What happens when the Primary Controller returns - they automatically switch back, right? Is this automatic switch combined with a loss of wireless connectivity? (LWAPP tunnel gets torn down, and a new LWAPP connection must be established - that is basically the same if I restarted the AP, isn?t it? ) If so, how long does it take for the connectivity to return? Is it possible to manually do the switch to a later time (late in the evening..) to minimize the effects for the clients? The Goal is to keep the clients up and running, without termination of the wireless connection - if this is possible.Also, after checking my WLC's Controller->General config screen, you will find a parameter called "AP Fallback".
It can be either "Enabled" or "disabled" and determines whether or not an access point that lost a primary controller connection automatically returns to service when the primary controller becomes functional again.
I suppose that if you set this parameter to "Disabled" in the secondary controller, before activating the repaired/replaced primary controller that this would also accomplish what you want.
It is not clear if the same setting would also need to be applied to the primary controller. You may need to test this aspect first to be sure.
Presumably, you could then re-enable "AP fallback" when you are ready to force the LWAPs back to the primary.
I hope this helps,
- John -
Transfer WISM Access Point license to another type of controller
Guys,
Is it possible to transfer Access Point license from existing wism to another type of controller ?
For example my client have existing wism with support for 300 access point and the plan will be migrated to Cisco WLC 5508, can the access point license transfer from existing wism to new Cisco WLC 5508, so i just buy Cisco WLC 5508 with minimum access point (12 license) and get license transfer from existing wism (300 license) so the total 312 license.
Is it possible to do that ? If not what the best scenario (for value) for hardware choice for controller if my customer want to migrate to new hardware ?Refer to " Re hosting a License " from
http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_011.pdf
It has both a> GUI b>. CLI mode steps
Maybe you are looking for
-
RoboHelp 9 Will Not Compile Web Help
Windows 7 Professional 640-bit Microsoft Office 2010 RH 9.0.2.271 I have several projects for which I compile Web help. Compiling the projects has been no problem in the past. I have made no known changes to the computer or user rights. Now, RH stops
-
Alright, so I'm supposed to write an inheritance class called MusicStore, which is inherited from the Store ( already written), and then the MusicStore method tests out the MusicStore. The MusicStore has the additional attributes of the number of tit
-
My computer is dying and I purchased a Toshiba 500GB external drive so I can back up my files. I'm noticing that several files types are NOT backing-up / transferring to the Toshiba external drive. Specifically Photoshop files (.psd)...they are not
-
Just had my Mcafee updated. Before this update, everything worked fine. Also, had to have wireless printer reconnected. New issue is that when I open a downloaded pdf, I get a pop up that says I need to acitvate a related product like photoshop to us
-
Vertical Swiping through Article hanging
Hi, there was something happening with vertical swiping through articles in the custom viewer (v22). When Swiping from one page down to the next page, I have to drag my finger over the complete screen or it is not changing the page at all (just crapp