Shutdown Second WISM controller in 6509

We have the task to shutdown our secondary WISM controllers and bring up new 5508 controllers. I'd like to shut down WISM controller 2 and re-use the IP on the new WLC. Is there a way to shut down or disable the second WISM so i can reuse that IP? When i attempt to disable the interface i get the following:
(WiSM-slot6-2) >config interface ap-manager management disable
Error - This command is only applicable to dynamic interfaces.
(WiSM-slot6-2) >show interface summary
Interface Name                   Port Vlan Id IP Address      Type    Ap Mgr Guest
ap-manager                       LAG untagged 132.189.242.236 Static Yes    No
guest                            LAG 500      192.168.124.33 Dynamic No     No
management                       LAG untagged 132.189.242.232 Static No     No
service-port                     N/A N/A      192.168.254.4   Static No     No
virtual                          N/A N/A      1.1.1.1         Static No     No
wireless-users                   LAG 10       10.96.128.13    Dynamic No     No
(WiSM-slot6-2) >
We currently have active wireless clients on WISM Controller 1 in the same chassis.
Thanks,
Jay

Why not just use a different ip initially and move all the access points to the 5508 and then change the management ip to the old WiSM IP address. You can even change the management of the WiSM first and then bring up the new 5508 on the old WiSM IP address also. You can do what Leo mentioned or even power down the module.
-Scott

Similar Messages

WiSM Controller 1 is Down

Dear all,
I have WiSM WLAN Service Module installed on 6509 core switch, everything was working fine, suddenly the first controller became unavailable and showing the following output
CoreSwitch# <strong>show wism mod 4 controller 1 status</strong>
WiSM Controller 1 in Slot 4
Operational Status of the Controller : Service Port Up
Service VLAN : 144
Service Port : 9
Service Port Mac Address : 0000.0000.0000
Service IP Address : 0.0.0.0
Management IP Address : 0.0.0.0
Software Version :
Port Channel Number : 289
Allowed vlan list : empty
Native VLAN ID : default
WCP Keep Alive Missed : 0
Second controller is working fine and showing the following:
CoreSwitch# show wism mod 4 controller 2 status
WiSM Controller 2 in Slot 4
Operational Status of the Controller : Oper-Up
Service VLAN : 144
Service Port : 10
Service Port Mac Address : 001a.6c22.8f62
Service IP Address : 192.168.100.3
Management IP Address : 10.41.1.21
Software Version : 4.2.176.0
Port Channel Number : 290
Allowed vlan list : empty
Native VLAN ID : default
WCP Keep Alive Missed : 0
<strong>Anybody can help??</strong>

yup ... i had that on a install a few months back ... had to do a RMA....
I would call TAC and get this replaced. Dont waste your time on this one ...

Configure WISM controller Vlan Management

Anyone can clarify me if is correct or not to confifure the WISM controller on a 6509 management in VLAN1 or is a must to put ( as Cisco Described : http://www.cisco.com/en/US/docs/wireless/technology/wism/technical/reference/appnote.html#wp40841 ) in VLAN 40 or any aother VLAN different by Vlan 1 ?
This question because now we found a broadcast storm passing through VLAN 1 and through the wirelles network
Thanks !

you an use whatever VLAN you wish. If all of your network is managed via VLAN 1, than that is fine. I know that some people recommend not using VLAN 1, but that is a personal call.

Pass Data Into Second View Controller

*My Setup:*
I have a tab-bar program; I'm currently focusing on one tab, which has a nav controller
The root controller works as expected. In one of the table view selection methods (didSelectAccessoryButtonAtIndex, or something similar), I initialize one of my classes, which is a subclass of UIViewController with an alloc and custom init. Then I use the pushViewController to push an instance of that class onto the view stack.
*My Issue:*
I can't figure out how to pass the data from my first level controller to the second. I'm using a custom init method, which is an instance method because I have to pass an instance of a view controller to the pushViewController method. The data isn't getting to the second level controller, as verified by some NSLogs.
*Pseudo code:*
FirstViewController.m:
-(void)accessoryButtonPressedAtSomeIndex {
SecondViewController *svc = [[SecondViewController alloc] initWithString:@"Some string"];
pushViewController: svc
SecondViewController.m:
@synthesize string;
-(id)initWithString:(NSString *)someString {
self.string = someString;
NSLog (@"string = %@", someString);
return self;
The NSLog returns NULL.
Obviously some of the code isn't valid, but I don't remember the exact methods. I can post the real code if necessary, but there are a lot of "dependencies" between files. Everything else (pertaining to this problem, although there are some other bugs in my app that I'd appreciate help on too) works. Any suggestions?

Hello musicwind95
Two suggestions :
1) Didn't you forget to do
if (self = [super init] )
return self;
in an init method ?
Otherwise there is nothing to handle your string
2) Put a breakpoint and trace ..

Regulatory domain on WiSM Controller

Can we change the regulatory domain of the WISM controller. The region I am working in, the max EIRP allowed in on 14 dBm. Is it a right step if I change the regulatpry domain of the WISM controller so that the EIRP of 1524 can be increased?

The EIRP is observed on AP. The Radio elements ( including Antennae ) are present in AP not controllers. So if AP has been regulated to emit maxm @14dBm , you cannot observe more power beyond that even if you configure it via controllers.

Wism controller does not show url redirection spalash page

Hi
Wism controller does not show url redirection/splash page .
client takes the ip from the dhcp server. when browsing its not going to the authentication page as usual
Thank you

Can you elaborate on your issue... really hard to follow. To me, it seems like you want to use a guest splash page. The client associates to the open guest ssid and get's an ip address. Now the user has to open a browser to get the portal page correct? This has nothing to do with the WLC, but the OS on the device. Some devices can detect if no internet is present after authentication and obtaining an address. This means the device will automatically open a browser to present the user with the splash page. Other devices will require the user to open a browser to get the login screen.
Scott

Adding second domain controller in Windows server 2012 R2

Hello, our primary domain controller is currently on a machine that has Windows Server 2008 R2 Standard. We are planning to setup a second domain controller as a failover to our primary domain controller. My question is, can we have a secondary domain
controller on a Windows Server 2012 R2 even if our primary domain controller is on a machine that has Windows Server 2008 R2?

I think I found the answer to my question.
http://technet.microsoft.com/en-us/library/dd464018(v=ws.10).aspx
"In Windows Server 2012, Adprep.exe is integrated into the AD DS installation process and runs automatically as needed. For example, when you install the first domain controller that runs Windows Server 2012 into an existing domain and forest, then adprep
/forestprep and adprep /domainprep automatically run and report the results of the operations.
Some organizations may prefer to run Adprep.exe separately in advance of an AD DS installation. For this reason, Adprep.exe is also included in the \Support\Adprep folder of the operating system disk.
In Windows Server 2012, there is only one 64-bit version of Adprep.exe. It can be run remotely from any server that runs a 64-bit version of Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012. The computer where you run it can be either
domain-joined or in a workgroup.
The version of Adprep.exe in Windows Server 2012 includes new syntax and parameter options in order to run it remotely. For more information, see
Adprep."
For more information about the objects and containers that are created when the schema is extended to support Windows Server 2012, see
Windows Server 2012: Changes to Adprep.exe.

Potential Downtime or Damage to Exchange if I remove a second domain controller??

We have a single instance of Exchange 2010 with all roles (minus lync, communications, etc..) on a Server 2008 Standard server.
We also have a primary domain controller and a second domain controller that offers DNS and would be used in case of disaster to the primary controller.
I've noticed in the past that if the secondary domain controller is down for maintenance that the Exchange server starts having problems. A major example of this would be last year the virtual instance of the second domain controller failed and when we rebooted
the exchange server, it lost its association with the domain even though the primary domain controller was readily accessible.
We are in a spot now that we no longer need the secondary domain controller and want to decommission it. I obviously want that to go as smoothly as possible. Is there anything I should do to prevent any unwanted damages to the exchange environment?
Jonathan Strader

It doesn't seem that anyone has responded to this. The short answer is turning off the secondary server will NOT have an effect on the exchange server. HOWEVER, that is the short answer.
It WILL have an effect if:
1) the secondary server is the ONLY DNS server and the exchange server is using the secondary server for DNS queries.
2) The FSMO Roles are on the secondary server
3) The Secondary server is the only global catalog.
I know this is a lot to take in.. but it really isn't that hard. FSMO Roles and global catalog are just a piece of active directory that keeps track of users, rights, settings, that sort of thing. You need to make sure that you seize the FSMO
roles on the first domain controller.
One command you can do on the first server to check fsmo roles is:
netdom query fsmo
On a side note. This is what you can do as well to see if the secondary server has any effect on exchange. Ready? Turn off the secondary server and see if anything bad happens (People don't get their emails..) if something stops working
after you turn off the second server then turn it back again. Everything should be back to normal.
Jerry Suner

Second IDE controller not seen, Blade 150

On our Blade 150, on the first IDE bus I have a hard drive and a DVD recorder. On the second IDE bus I have another hard drive. The second bus is not seen at all. If I do a stop-a, probe-scsi-all the drive on the second controller is not seen. If I swap the two hard drives I get the same results; drives on the first bus are seen, drives on the second bus are not seen. I have also tried a new cable. Do I need to enable the second IDE controller somehow? Am I overlooking something? My goal is to make this a multi-boot machine and use an alias to choose which drive to boot from.

Thank you for the tip, I gave this a shot. I took all the defaults up to the point where it asked if I wanted to rebuild the path_to_inst file, where I answered yes. Then it asked for the physical name of the root device, I took the default which looked correct. Then it gave me the same error as before, "/dev/dsk/c0t2d0s6 or /usr, no such file or directory" and the boot failed. I then rebooted again and it cannot find the path_to_inst file so aparently it did not get far enough to save the new file.
Just to clarify what I believe the problem is, here is my layout:
c0t0d0sX --> Solaris 9 install, boots and runs great, c0t2d0sX listed under both /dev/dsk and /dev/rdsk, c0t2d0sX will mount just fine when running Solaris 9 so the disk looks OK
c0t2d0sX --> Solaris 8 install, OS was installed when disk was in c0t0d0 location then the disk was moved to c0t2d0 (first disk, second IDE bus), now has problems booting, c0t2d0sX not listed under /dev/dsk or /dev/rdsk on this disk and I think this is the problem.

Second WiSM Design Guide

Hi All,
I have been running a WiSM successfully for months now, but our wireless network has grown quite a bit so we have purchased a second WiSM.
Are there any best practises for implementing another one, or are there any design guides?
Thanks,
Michael

Hello Michael,
Your setup is basically going to be the same. However, you do want to make sure the virtual IP address on both WLCs on the 2nd WISM you purchased are configured the same as the other WISM if you intend to allow mobility between APs and clients. Additionally, you will also have to add your two mobility members to your existing controllers and configure them correctly on your new ones.
If you intended to configure manual load balancing you can use the primary/secondary/tert configuration on the access points.
All of the above is mentioned in the 4.0 configuration guide and it does cover multiple WLC implementation as well:
http://cco/en/US/products/ps6366/products_configuration_guide_book09186a00806b0077.html
I hope this helps!
-Mark

WISM Controller and 6500 Switch power cycled

Has anyone come across this issue where if the 6500 switch is reloaded or power cycled that 8 out of 10 interfaces on the WISM become administratively down this does not happen if you reload just the wism or power cycle the controller.
the softwear loaded on the switch is as follows.
Supervisor Engine 720 10GE with f/w 8.5(2) and s/w 12.2(33)SXH
WiSM WLAN Service Module with f/w 12.2(14r)S5 and s/w 12.2(33)SXH
any suggestions as to how to sort this so it loads all the interfaces as up from the power cycle or reload of the switch would be welcome have already made sure the config is saved but still happens.
Jeremy

1. I believe a 6509 can handle 5 WiSMs, though I've found 4 more realistic when considering the need for uplinks and service modules.
2. Based on 5 WiSMs, you can have 1500 per chassis. Again, I tend to stick with 4, or 1200 APs per chassis.
3. There is no hard limit that I am aware of. WCS on a VERY high-end server can handle ~2500 APs when running Linux WCS. As with the above, this works well with 1 WCS per 2 chassis if each has 4 WiSMs.

Wism Controller 2 doesn't get service port IP but Controller 1 does

I followed the documentation for setting up the WiSM. Controller 1 is up and fine. I see in dhcp bindings, that Controller 2 is getting a DHCP address and when I "session slot 9 pro 2" it tries to connect to that dhcp address, but on a "show wism status" the service-port of controller 2 is 0.0.0.0
Has anyone encountered this problem?
Thanks

Hi..
What about the connectivity?? do we still have the access to the WLC 2?? either from telnet or the GUI?? or will the session to the WLC work?
Regards
Surendra

Adding HASH keys from one WISM controller to all other controllers

I have 4 controllers(2 WISMS) on one controller we have ~30 MAC/SSC/KEY HASH
the other 3 have ~half. How can I copy all the MAC/SSC/KEY HASH to the rest of the controllers. I don't have access to the station that converted the AP's. I would prefernot to have to add each individually.

Hi, if you have an WCS you can use the AP Authorization Template, you can find it under Configure > Templates > Security > AP Authorization. Use the csv File generated by the Conversion Tool and import it to WCS. Then push the Template to the Controllers. Otherwise you can do it directly on the Controller, under Security > AP Authorization. Insert the AP MAC, Certififcate Type SSC and the RSA Key Hash. Regards, Michael

Can't join AP with WiSM controller

We have a (brand new) WiSM blade installed in a 6509. The configuration looks ok, but when we try to register (join?) an AP with the controler the process fails. The controler shows the AP in the status display but the AP reboots, claiming that no join-response was received.
The controler claims that it sent the join-response, however imediatly after that it generates the error "Slot ID 0 is not valid for AP".
Here is a more complete log:
Tue Aug 22 16:08:47 2006: sshpmGetOpensslPrivateKeyFromCID: match in row 2
Tue Aug 22 16:08:47 2006: sshpmPrivateKeyEncrypt: calling RSA_private_encrypt with 236 bytes
Tue Aug 22 16:08:47 2006: sshpmPrivateKeyEncrypt: RSA_private_encrypt returned 256
Tue Aug 22 16:08:47 2006: sshpmPrivateKeyEncrypt: calling RSA_private_encrypt with 24 bytes
Tue Aug 22 16:08:47 2006: sshpmPrivateKeyEncrypt: RSA_private_encrypt returned 256
Tue Aug 22 16:08:47 2006: sshpmPrivateKeyEncrypt: encrypted bytes: 512
Tue Aug 22 16:08:47 2006: 00:18:b9:xx:xx:xx Successfully transmission of LWAPP Join-Reply to AP 00:18:b9:xx:xx:xx
Tue Aug 22 16:08:48 2006: 00:18:b9:xx:xx:xx Slot ID 0 is not valid for AP 00:18:B9:xx:xx:xx
Tue Aug 22 16:08:48 2006: 00:18:b9:82:29:2a Slot ID 0 is not valid for AP 00:18:B9:xx:xx:xx
Any thoughts, hints etc. We do have another controler that is working.
thanks
Phil

Turns out the SlotID 0 issue was a red herring. There was a bug in the network topology that prevented the join-reply from reaching the AP.

WISM controller stays "Started KeepAlive"

After an upgrade of both controllers on a WiSM module from 4.1.171.0 to 5.0.148.0 the first stays in
"Operational Status of the Controller : Started KeepAlive"
Even after setting to factory defaults or repowering the module.
Any idea what's problem

the service port is configured to get an IP from the dedicated management vlan where a local dhcp service is provided.
...and in the meantime after several controller and module resets it works without config changes....
So I'm wondering whether this is usable in an productive environement.

Shutdown Second WISM controller in 6509

Similar Messages

Maybe you are looking for