2 5508 a mobility-group autonomous migration

Similar Questions

• Copy configuration WLC wlc next in the same mobility group

  Hello

  We have a 4400 WLAN operational controller. We intend to deploy a new controller in the same mobility group.

  How do we configure the second WLC? From scratch, or we could for example use backup configuration of the first WLC (just to change the address-ip/hostname etc.)?

  ARO

  Mikko

  Or the other works, but remember that reproduction should be the new controller to be off the grid to avoid intellectual property conflicts. I like to build from scratch, and then to ensure that the same configuration settings, use WCS to push models. Local on controllers do is ok, if you only have a few, but if you have more that 5-10 you will find keeping all the controllers of the same becomes a management nightmare.

• Mobility Group - without layer 3 roaming

  Hi all

  With a N + 1 WLC deployment, is it possible to disable the layer 3 roaming while allowing the Group feature of mobility on the backup controller?

  based on the configuration of the network, layer 3 mobility is not necessary. However, we need two controllers to exchange all the parameters so that excluded customer info etc. will be synchronized during a failover security scenario.

  I don't want to use ACL as such.

  Thoughts appreciated.

  see you soon,

  Andrée

  Andrée,

  Looks like there's nothing for you to do. Let me clarify my thoughts, so can you tell me if I saw correctly your concern:

  -If the buildings are separated, the case where a laptop can move from the field of application of 1 to cover other WLC WLC will never happen right? And if this does not occur, layer 3 roaming never happen either.

  -If no layer 3 roaming happens, no additional charge affects the WLC.

  Nicolas

  ===

  Remember responses of the rate that you find useful

• 'group tabs' migration to a new computer

  My HARD drive is a failure I'm trying to back up EVERYTHING. Is it possible to save my "tab groups" so they can be restored on a new HARD drive? I use win 7 Home Premium 64-bit system.

  Yes, I printed the referenced article. Because nothing will be available on the new HARD drive. I copied the backup profile and when the HARD drive gets here, I'll follow the signs to replace the new default profile.

  Thanks for such a quick reply and these good guidelines.

• Mobile groups within other groups

  Seems really basic, but keep problems to move a group within another group (tested CC 2014 and 2015). So the following code results in an error of the argument not comply .move line (I also tried other variants like. PLACEATBEGINNING and. INSIDE):

  var doc = app.documents.add (256, 256, 72, "foo")

  var group1 = doc.layerSets.add)

  var group2 = doc.layerSets.add)

  Group1.move (Group2, ElementPlacement.PLACEATEND)

  doc. Close (SaveOptions.DONOTSAVECHANGES)

  But this way works OK

  var doc = app.documents.add (256, 256, 72, "foo")

  var group1 = doc.layerSets.add)

  var group2 = doc.layerSets.add)

  Layer1 var = group1.artLayers.add)

  Layer2 var = group2.artLayers.add)

  Group1.move (layer2 , ElementPlacement.PLACEAFTER)

  doc. Close (SaveOptions.DONOTSAVECHANGES)

  No cracking what limits are at stake here? You can do the latter, but then you might need to create and remove the layers of the tmp to use as target.

  Yes, it has been a problem, but you can use AM.

  var doc = app.documents.add( 256, 256, 72, "foo");
  doc.layerSets.add();
  var group1 = getLayerID();
  doc.layerSets.add();
  var group2 = getLayerID();
  
  moveLayerToLayerSet( group2, group1);
  
  function moveLayerToLayerSet( fromID, toID ){
  var desc5 = new ActionDescriptor();
  var ref4 = new ActionReference();
  ref4.putIdentifier( charIDToTypeID('Lyr '), Number(fromID) );
  desc5.putReference( charIDToTypeID('null'), ref4 );
  var ref5 = new ActionReference();
  ref5.putIndex( charIDToTypeID('Lyr '), getLayerIndexByID(toID) );
  desc5.putReference( charIDToTypeID('T   '), ref5 );
  desc5.putBoolean( charIDToTypeID('Adjs'), false );
  desc5.putInteger( charIDToTypeID('Vrsn'), 5 );
  try{
  executeAction( charIDToTypeID('move'), desc5, DialogModes.NO );
  }catch(e){alert(e);}
  };
  function getLayerID(){
  var ref = new ActionReference();
  ref.putEnumerated( charIDToTypeID('Lyr '),charIDToTypeID('Ordn'),charIDToTypeID('Trgt') );
  var desc = executeActionGet(ref);
  return desc.getInteger(stringIDToTypeID( 'layerID' ));
  };
  function getLayerIndexByID(ID){
  var ref = new ActionReference();
  ref.putIdentifier( charIDToTypeID('Lyr '), ID );
  try{
  activeDocument.backgroundLayer;
  return executeActionGet(ref).getInteger(charIDToTypeID( "ItmI" ))-1;
  }catch(e){
  return executeActionGet(ref).getInteger(charIDToTypeID( "ItmI" ));
  }
  };
  

• Mobile groups of logic between applications

  Hello Experts, we run two applications of FDM - one test and a live. When a company has completed stable, we charge all mappings to live but have to manually re-create the accounts/groups of logic in the live application. Is it possible to move the accounts or groups of logic between applications because it is extremely laborious having to recreate them manually?
  
  Thank you
  
  Nick

  Hi Nick,

  You can go on Workbench, select export and then check the box for groups of logic. Go in the other application, and then import this XML file.

  If necessary, you can go to the XML file and delete all rows that belong to groups, you do not want to import.

  KR. JDeM.

  Published by: JDeM on 6-APR-2011 04:43

• Mobility groups, failover on different subnets

  I have read up on 5.1 and wonder how and if real failover on subnets is an option.

  I understand controllers mg even customers roaming on different subnets.

  How it works if your main "anchor" isn't alive to replicate the DB entry on the controller off-subnet? Say if die of my local WISN and the backup is in the next State, how the HA will maintain connectivity?

  Thank you!

  Yes, but tha ap will be the new configuration of the WLC. Also, users will get tunnelees to the wlc and be thrown out of this subnet. Then make sure you understand the ssid and ip clients will get when they associate to of different wlc. That should do it.

• Groups of mobility between...

  Hi experts,

  I am managing WLC 3:

  1 WLC 2112 - code version 7.0.235.0

  2 WLC 2112 - code version 7.0.235.0

  3 - WLC 5508 - version code 7.6.130.0 (new purchase)

  Is possible to group the WLCs 3 in a group of mobility

  No, it is the recommendation of Cisco, but still 7.0 can work with 7.6 in the same mobility group. So you should get these worms upward in the same group of mobility, although this isn't the recommended best practice (but keep a migration strategy to move away of series 21xx).

  Note that you must put all your AP to the same mobility group THAN if the user moves between these APs & you don't want to drop their roaming sessions.

  So if you have APs in various buildings, you have no coverage wireless between the buildings, I worry not put them all in the same mobility group.

  Identify the geographical area where AP are close & customers wander in, put them on a group of mobility.

  Hope this clarify your query.

  HTH

  Rasika

  * Pls note the answers useful. *

• migration of APs to the 5508 controller 4402

  Hello all,.

  We have two controllers (4402 and 5508) to one of the site.

  Customers of services at present.

  Both controllers have the same set of SSID but uses only a single group of AP.

  What would be the best means to move APs on 4402 to 5508?

  4402 services series years 1230 and 1240 AP. And looking at the note accompanying the WLC 7.6 code located on 5508,

  years 1240 only are supported. So, we will need to get the replacement of the years 1230.

  Someone suggested to go into every single years 1240 and change high availability for point to 5508 as primary and secondary 4402

  (just in case the AP don't is not the controller) 5508 Once this is done, I can add the AP in the access point default of the group to broadcase the same SSID.

  Is it enough for the task of migration?

  Also, what is the requirement of default design for the number of necessary uplinks?

  We have about 150 APs currently on 5508 that uses Group LAG of 1 4 uplinks.

  Regarding the 4402, it is service 60 APs with 1 2 uplinks.

  Thus with the APs on 4408 joining the 5508, 5508 serves about 210APs. 4 1 enough uplink is?

  What is the best practice recommended requirement of uplink AP?  APs on 5508 are 3602 s and 3702 s.

  Thank you in advance.

  P.S. BTW two controllers are part of the same mobility group

   Someone suggested going into every single 1240s and change the high availability to point to 5508 as primary and 4402 as secondary.(just in case the AP does not join the 5508 controller.) Once that is done, I can add the AP into the default AP group to broadcase the same SSIDs.Is that enough for migration task?

  Yes, it is sufficient. Unless 5508 have the same available on 4402 AP group name, all years 1240 migration goes into default-group & you may need to add to the good group of AP. It is advisable to have same AP group created between the controllers where AP configured for failover.

  Don't forget 1240 last took in charge in 8.0.x code. In order to better plan as well before moving on to 8.1 replacement code (expect less than 1-2 months of time). See below for more details compatibility matrix

  http://www.Cisco.com/c/en/us/TD/docs/wireless/compatibility/matrix/compatibility-matrix.html

   Also what is the default design requirement for the number of uplinks needed? We have about 150 APs currently on 5508 which uses LAG group of 4 1G uplinks.Thus with APs on 4408 joining the 5508, 5508 will roughly serve 210APs. is 4 1G uplink sufficient? 

  4G LAG is more that sufficient for 250 AP, I'm sure that together the traffic will be much less of 4G if monitor you the traffic volume of the art on this trunk links.

   What is the best practice recommended AP to uplink requirement? APs on 5508 are 3602s and 3702s.

  I guess that all of these AP connected to 1 Gbps switch compatible PoE ports +. If your binding rising intercommutation is 1 Gbit/s, which would be the bottleneck, WLC to SW LAG before becoming a bottleneck.

  HTH

  Rasika

  Pls note all useful responses *.

• Creating groups of mobility with 4402

  I am looking to place three 4402 controllers of production in the same mobility group.  Currently, there is no mobility group.  My question is, will this affect somehow customers when I add the controllers to the same group?  I'm sure not, but I wanted to just make sure.

  Yes, you're right, it will not adversely affect the customer.

  #Mobility Group is useful for roaming, anchor and AP aid smoothly. WLC restart is not required to add/configure mobility.

  #If you have similar wlan configured on all these customers and 3 WLCs tried to roaming, it probably makes roaming with delays dhcp failover. Given that it is already harming those clients, feel free to set up mobility.

  #If APs on these 4402 s sharing RF so don't forget to set up similar groups of RF to avoid each idetifying APs themselves as thieves.

• Requirements of the mobility for the comments of anchor WLC group

  Hello-

  I always assumed that you cannot create a tunnel between a local WLC and an anchor WLC comments that are in different groups of mobility.   However, I was told recently (no more details) that it is possible.  So I put to test this.

  I'm trying one of my local WLCs SSID comments point to an anchor of WLC comments in a different group of mobility.   I have a forthcoming maintenance window and I'm looking to anchor clients on a campus at anchor WLC on the campus on the other for the customer service does not lower.   Each campus is that it's mobility group.   Trying to set up I went to the "mobility anchors" screen for the SSID guest on one of the local WLCs and I cannot add anchor WLC on campus on the other because it is not in the drop-down list.  This is because it is not in the same mobility group.   So my question is how do customers of anchor across a local WLC in a group of mobility to a WLC anchor in another group of mobility?

  To me it seems not possible without major configuration changes.   I don't want to reconfigure / rebuild mobility groups.

  Thank you

  Chuck

  Not only is it possible, that I recommend. However, you can be confusing to some concepts.

  The mobility group is different from that of the field of mobility.  Generally, I am referring to group mobility as these WLCs with the name of the default mobility group and the field of mobility than the entire list of mobility (where you can set up to 72 controllers belonging to various groups of mobility).

  The point is that GroupA and WLCs of to WLCs 1-10 11-20 are GroupB, anchor to work, you at least need to add anchor to the mobility list wlc abroad and vice versa.

  If you notice, when you add an entry of mobility to the list, it should ask you for mobility group. If you leave this field empty, it must default to that of the WLC, but on controllers GroupA, you could define GroupB controllers (and specific group b) and then you should now have the mobility between your controllers and configuration of the anchor will be your anchor in the menu...

  Who is?

• Mobile accounts in Snow Leopard 10.5.8

  I run a small network with 6 minis. Two are old models of mini1.1 and run only Snow Leopard 10.5.8.

  However, I would like to link to my server, built later and use the Mobile accounts to connect.

  I understood how to do this with newer hardware. You create accounts on the server and select 'Accounts Mobile' on client machines and who push with a profile for managed clients.

  But Snow Leopard does not allow that to happen. It's the former.

  HOW can I activate accounts Mobile on Snow Leopard?

  YoursPierre

  I thought about it.

  In the Profile Manager make a GROUP with specific accounts MOBILE set to "create Mobile account.

  On the Snow Leopard Client, connect to one of the accounts, in the preferences panes accounts, choose 'create mobile account', now, is only active once you have joined this accounts on the server to the MOBILE group.

  That's all.

• Mobility to new comments controller, do not discount

  Hi all

  I hit my head against the wall for the last day watching a strange problem with my wireless controllers.  My current setup has been a cluster (8.0.140) foreign controller and a N + 1 alien Controller (8.01.121).  I then had two Controllers (7.6.130) of anchor individual comments in a DMZ with 3 SSID being mounted on the guest.

  I have installed a new controller of Anchor Guest (7.6.130) in a new demilitarized zone, built the tunnel of mobility between new comments and foreign controllers. Removed the existing anchorages among the SSID and added new comments to test connectivity.  My client cannot obtain a DHCP address.  If I statically assign an ip address, then I am connected but disconnects 10 seconds later.

  So I install a new SSID, exactly the same as I was testing on foreigners and the new controller of the anchor.  Create the mobility group the same way and test my client, works without problem.  So I know that my DHCP setup is ok, my new controller of anchor is ok.

  I tried to remove my old SSID and add once again, get the same results, the client cannot connect.

  When I do a debug of the customer on the controller from abroad, I get the error message following which seems to be the where it is a failure:

  Retry mobility anchor Packet XX.xx.xx.xx.xx.XX: Peer IP: , anchor IP: 0.0.0.0

  Once I change the anchor to old controllers on the foreign controller SSID, my client connects immediately again.  I tried my new guest anchor controller on 8.0.121 and 8.0.140, but I get the same results.

  The fact that a new SSID works first time with the same settings (just a different SSID) baffles me.  Even if I change the old SSID to no authentication, it still does not connect.  I tried with 3 different customers comes to exclude one of the problems.

  I have also repeated the above test on N + 1 foreign controller (running 8.01.121) and get the same results

  Anybody have suggestions for something else to test.  My apologies for all levels of different code, but also through an upgrade code for the moment.

  So, when you set up a new SSID that is mapped to the same vlan everything works. When return you your old controller who maps also the SSID to the same vlan it also works very well. However when you have the new anchor with the current SSID added new controller, it does not work?  So when you auth enjoying a nice SSID don't see you the customer also on the controller of the anchor?  To have a static and drop all 10 seconds or seems weird and you can create a new SSID on foreigners and the anchor without problem?  What I would do is create a new WLAN using the same SSID, the name of different profile on the two foreigners and anchor. It should work since you mentioned a new SSID works very well. If your WLAN id is 1-16, and then create the new with id WLAN 17 or more, otherwise you will need to disable the old SSID before activating the new.

  -Scott

  Evaluate the useful ticket *.

• DHCP and groups AP assignments

  I'm having a problem where I have AP groups works perfectly fine, but when a customer moves from one building to the other assignment DHCP from the 'first' AP group is preserved when the user accesses AP assigned to another group of AP.

  For example, Laptop1 has an 10.2.1.110 address in AP Group1. When the user moves to an AP in Group 2, the Laptop1 retains the 10.2.1.110 rather than get a new address of Group2.

  Traffic still works perfectly, but I need them to inherit the regimes of intellectual property of the AP group they moved (conditions of the application).

  Our configuration is very similar to this document: http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008073c723.shtml#configs

  We have a controller 4402 with 37 1131 AP all AP is assigned to a group AP in their respective buildings and DHCP VLAN and traffic works perfectly well in each.

  DHCP is offered by a Windows 2003 server as clients wired and wireless must be in the same subnet for the purposes of the application.

  The controller and the AP is in native VLAN 10.

  I'd appreciate any help to determine why the controller or the DHCP server is not recognize the change of the client subnet.

  It is a normal behavior as long as the customer can place an AP on Group1 AP to ap on AP Group2. If you want the device to re-associate one building to another, you need to place the ap on a different WLC with a different mobility group name. If all of the ap is on the same mobility group, then you will have the seamless roaming like what you see.

• Standard switch DV Switch migration

  Hello the heroes of VMware.

  I intend to convert networking virtual switch to standard dv switch in my company in the context of ESX 4.1 to 5.5 upgrade infrastructure. We have about 160 guests and virtual 2000 computers in this project. From now on, we have rebuilt most of the hosts to 5.5 (dint want to upgrade, coz of the limitations of space on the startup of the Bank directory). Currently, we have created standard switches with the same configurations hosts 4.1.

  The standard configuration is like this, vswitches 2. 1 for management and vmotion with 2 physical links.

  2nd is for virtual machines with 4 X 1 gig nics. We are not view our uplinks, as we do not have virtual connect for our hp blades.

  We did an analysis, and most of VLANS match through consolidation.  So we need 2 dv switches to 160 guests, one for the IPC and the other is for production.

  Now us created these dv switches and added guests, but haven't removed rising standard switch, since the use of the network is quite high. Also, we cannot accommodate VMs downtime, but we can afford downtime of host (per host at a time).

  As the migration of port groups will migrate all virtual machines on this group of ports from one switch to another, if we do that, we have the same number of uplinks on vds as with vss to carry the load.

  Having said all that, can anyone give us some valuable tips on how to solve this problem and move to vds.

  Thank you.

  Thor.

  To add more worries, vMotion will not VSS for VDS support (correct me if I'm wrong), which excludes the issue of putting a host into maintenance mode, remove all top links from VSS and link them to the VDS and replace the virtual machines on the host.

  vMotion traffic itself does not care, but the workflow of migration requires the machine network virtual source is available on the destination host. It seems that you are due for 10 GbE cards to help face the apparent flood of network traffic.

  To be fair, moving around the virtual machine networks is a rather low-risk. If you plan not to move the vmkernel interfaces, which said you are on a completely different vSwitch, it's really just a matter of ensuring that your VDS is configured with the appropriate uplink slots and groups of ports. You can start a workflow of migration to move physical uplink (vmnic) and the virtual machines at the same time. To test this, you can migrate virtual machines on a host, run a few test VMs and try it.