WiSM redundancy/failover

Cisco documents mentions only up to tertiary WLC. The thing is each WiSM has 2 WLC 4404 cards. We have 2 WiSM modules. How do we configure the WiSM modules for redundancy/failover? -Thanks

If you have two WiSM's in one chassis then I would set it up like this... no need for a tertiary:
WiSM 1 WLC 1 A
WiSM 1 WLC 2 B
WiSM 2 WLC 1 A
WiSM 2 WLC 2 B
Just break up the sections via floor, building or sections.
ex.
A = floors 1-3
B = floors 4-6

Similar Messages

Redundant Failover link on ASA5500 Series?

Cisco recommends connecting failover link over L2 switch in thier document.
But if L2 switch fails, both ASA's failover I/F will down.
I wonder if there is any way to get redundancy for failover link, like etherchannel.
Or should I prepare two L2 switches to avoid both ASA's I/F down?
Any hints appriciated.

Even if both of the failover interfaces go down it wont affect the traffic flow. Also if the switch is being monitored this will get detected and can be solved easily. If you still want redundant failover links, using seperate switches will be good idea.

ASA redundant failover links

Hi,
We are setting up a new ASA which is in multi context mode. I was wondering if it is possible to setup redundant failover and state links? I know that it is possible to run failover on one link and state on another, or both over the same link, but is it possible to have both failover and state running on 2 links? For example, failover and state on ten1/0 as well as failover and state on ten1/1.
Hope I have explained my question well enough. If not I will try to explain better.
thanks

I would suggest to make a redundant logical link and attach two physical links to it. Than during failover link configuration specify your redundant link as a failover link. Not sure if it works but dont see any obstacles for this solution to fail..

WiSM redundancy, mobility groups and RF groups

Hi there
we would like to implement the following:
- Support for about 2000 LAP's
- 1 x Catalyst 6509
- 1 x Sup 720
- 7 x WiSM's
What I'm interesting is are the following points:
1. I thought that we would build the switch completly redudant, so we have to wlan switches (switch A and B) with 7 WiSM's eatch. So I can garanty a N+N redundancy --> each LAP's has a primary controller on switch A and it's secondary controller on switch B. The LAP's can be splitted on the two switches, but for your understanding there is a 1:1 redundancy. What do you think of this design, is the too much or is this appropriate?
2. As I know you can build up a mobility group of a maximum of 24 controllers or 12 WiSM's. I would put only these controllers in a mobility group, where Layer 2 roaming can occure.
3. But what is about the RF groups - there is a maximum of 1000 LAP's, so I can put only 3 WiSM's in one group. But this would not work form me, then I would have 2 WiSM's on switch A and only 1 WiSM on switch B in a RF group (not a 1:1 redundancy). First is it possible to put WiSM-A and WiSM-B into different RF groups, I think so because they are logically splitted, aren't they?
And what RF group design would be best (just as a reference)? I thought that it would make sense to form a RF group for each of the seven pairs (1 WiSM on switch A and 1 WiSM on switch B) for redundancy? What do you think of that approach?
4. So I would have 1 mobility group and 7 RF groups. Or do you recommend to form the mobility groups like the RF groups? But what happens with Layer 2 roaming in that case?
I'm sorry for the long and messy text, but I hope you can see my design questions?
Thanks a lot in advance.
Dominic

It sounds like you already have some good replies. Personally I like N+1 redundancy, but that is a designers choice. One thing I should point out is that the 6500 can only support 5 WiSM cards each. In this case a 4 WiSM x 3 chassis option would give your more spare capacity with only 12 total cards. The lower WiSM cost (12 vs 14) would help offset the cost of the extra chassis. You could also support 2400 APs with 8 WiSM cards even if one switch is down.
Not too long ago Cisco added the ability to set the priority of APs so your critical ones would join a controller and the less critical ones would go down if a controller failed and there were no redundancy. That is something to keep in mind when designing wireless. You may not need redundancy for all APs and that could affect your design and costs.
Randy

WiSM Redundancy in Campus Network L3 Access

Hi guys,
I'm designing a Campus network L3 Access in a Building with 30 floors and aproximately 250 APs,8 APs in each floor.
For each floor I will use two /24 subnet (one for data and one for voice). I have 2 WiSM...
I don't wanna to use another two /24 subnet for each floor only for redundancy, so I want to know
if i can use the following idea (Please take a look in the PPT File)
I will create a AP Group in each controller to include the APs for each 2 floors (for example floor 1 and 2).
The only diference between those AP Group in each controller is the network subnet associated with the Dynamic
Interface. The AP Group in controller WiSM1-A will be associated with the 192.168.1.0 network and the AP Group
in controller WiSM2-A will be associated with the 192.168.2.0 network.
The APs in the first floor I will configure to use the controller WiSM1-A as primary and I expect to see the hosts with the 192.168.1.0/24 network.
The APs in the second floor I will configure to use the controller WiSM2-A as primary and I expect to see he hosts with the 192.168.2.0/24 network.
If one of those controllers fail (for example WiSM1-A), I think all the APs will use the another controller and I expect to see the hosts with the 192.168.2.0. In this case I know that network 192.168.2.0 is used for both the two floors, not more just one floor. I accept that half the users can use the wireless network during the fail..
Is this works and if yes, can I use this idea with Mobility Group, Roaming L3, etc ????
Thanks in Advanced,
Andre Lomonaco

Hi gamccall,
First thanks for your reply...
I like you idea but initially I can't use it cause I put each wism in a ospf tottaly stub area and I use area summarization to have less networks in the core routers....
In my designing, the wism1 is in the
range 10.0.0.0 -> 10.0.95.0 and the
wism2 is in the range 10.0.96.0 ->
10.0.191.0
My Best Regards,
Andre Lomonaco

Redundancy/failover testing

My company is a relatively small enterprise (about 800 people scattered across 45-50 branches) and we are planning on setting up a periodic failover/redundancy testing schedule for our routers. Basically, we want to test the secondary WAN links at our branch offices and test our redundancy in our data centers.
I'm sure there is plenty of documentation out there in regards to best practices, but what I find has more to do with a full DR test of a enterprise's systems, as opposed to a simple failover test of an office's WAN link.
Does anyone have good suggestions for how often you should run these tests? My original thinking is to do this every quarter, but this would involve some travel for us and our resources are slim. The branch offices can be done remotely without any issue, but our DR site (which is actually used for some production traffic) would probably require one of our staff to be on site during a redundancy test.
Thanks!

Yep, that's what I did now.
But keep in mind this is not really explained, even if crossing all the documentations.
There is no document explaining what behaviour to expect in Jabber in case of redundancy of all the UC components.
For the CUCM, it's not clear, and nothing is mentionned in case of MRA.
IM&P is documented, but nothing for MRA.
Expressays states about redundancy, but the behaviour to expect is not. Same for XMPP federation, no idea.
UnityConnection as well, nothing is explained.

WiSM 2 failover for WiSM 1

I have a client who has all APs on a WiSM 1, and wants to set the WiSM 2 as the secondary controller. Are there any issues with this setup if both controllers are running the same version of code?
Thanks for the input in advance.

I have the same setup. Works well.
As what Steve has stated, make sure your code and configs are the same. PLUS make sure that the amount of WAPs failing over to the WiSM-1 doesn't exceed 150 WAPs per controller. Remember the WiSM-1 has TWO controllers and each of the controller can support up to 150 WAPs.

NAC OOB & Desktops with redundant/failover NICs

Can anyone tell me if NAC is capable of handling desktops that have multiple NICs configured for failover or even just set up as a team (i.e. a single ip address). Can it handle placing all of the correct switch ports in to the right vlan once the user is authenticated or are we just asking a little too much of the NAC devices?
Thanks for any help.

NAc will not be able to handle desktop with multiple NIC's.
Change VLAN according to global device filter list (device must be in list). When set, the VLAN of the port will be assigned by global device filter settings (ALLOW=Default Access VLAN, DENY=Auth VLAN, ROLE/CHECK=User Role VLAN, IGNORE=ignore SNMP traps from managed switches (IP Phones)).
If above option is enabled, thenl look at the filter table to decide what role user is and then move user to the vlan assigned for
that User Role:

Unity Express redundancy & failover

Hello Team,
Is there any option to configure redundancy for CUE ,we have two module and two 2921 gateways,
Thanks in Advance
Renji

Hi Renji,
Just thought I'd add this new reference to the good tips from Peter (+5 "P")
From April 2013;
Messaging Redundancy
Messaging redundancy is discussed in this section as it refers to Cisco Unity Connection. Cisco Unity Express does not support messaging redundancy.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/9x/vmessage.html#wp1090276
Cheers!
Rob
"A smile relieves a heart that grieves"
- Stones

Redundant / Failover VPN tunnel

Hi All,
We have several remote sites using PIX 501's back to cvpn 3015--works great. We would like to implemement a backup peer device in HQ on isp B (testing with just a PIX 501)...PIXs are default gateway for remote sites, and 3015 is in parallel with our firewall in HQ. We use static routes on an internal layer 3 switch to route through 3015 to remote sites. How would we be able to route internally to backup PIX (or concentrator if we get another)? I have an old 2500 I could use internally, if necessary, since the switch is non cisco and RIP / static routing is buggy on it.
Thanks much in advance!

This looks fantastic and was exactly the concept I was looking for. I was scratching my head wondering why something like this didn't exist to do simple tests on whether an ip was up or down...looks relatively new(?) Too bad my 2500 won't run that level IOS with the memory it has, but I can always find something around here that will ;)
Thanks to all who replied!!!!

Jabber for Windows 10.5 and global redundancy

Hi All,
I implement J4W 10.5 in a full redundant environment, that contains:
- 3 x CUCM 10.5
- 2 x Unity Connection 10.5
- 2 x IM&P 10.5
- 2 x Expressway-C 8.2.2
- 2 x Expressway-E 8.2.2
After testing, I notice that the redundancy/failover does not act the same way depending the product, sometime no.
As it is not clearly stated in the documentation, what is clearly supported as automatic failover, and what's not, when using Jabber for Windows 10.5?
In my first test, I saw that Jabber does not support failover with UnityConnection: if the primary peer is down, no more voicemail on Jabber.
If jabber run in Mobile and Remote Access, and the Expressway where it's conencted goes down, it doesn't switch to the other peer.
It will be good to have a document that relate all the redundancy and failover support with Jabber, what can we expect during the failover process.
It will help a lot of people.
Thanks
Gabriel

Yep, that's what I did now.
But keep in mind this is not really explained, even if crossing all the documentations.
There is no document explaining what behaviour to expect in Jabber in case of redundancy of all the UC components.
For the CUCM, it's not clear, and nothing is mentionned in case of MRA.
IM&P is documented, but nothing for MRA.
Expressays states about redundancy, but the behaviour to expect is not. Same for XMPP federation, no idea.
UnityConnection as well, nothing is explained.

WiSM Design Question

I have 2 WiSM's which I plan on placing in 2 geographically dispersed datacenters. I have 2 questions
1) Do I setup the 2 WLC's inside the WiSM to be in the same Mobility group to provide redundancy? Is that the best solution?
2) What is the best way to provide WiSM redundancy with this scenario? I will be supporting voice and data.

Since this is for redundancy, all WLC will have to be on the same mobility group. Only if you you have different buildings would you might not want to have then on the same mobility group. For example... if WiSM 1 WLC 1 is primary for building 1 and WiSM 1 WLC 2 is primary for building 2 ,WiSM 2 WLC 1 is secondary for building 1 and WiSM 2 WLC 2 is secondary for building 2. Mobility group for WLC 1 would be building1 and WLC 2 would be building 2. If both WiSM's will be primary or secondary to any of the access points, will the mobility group name have to be the same.
The best redundancy, depends on your setup.

Two wism module in vss

i have two core 6509E with version 12.2(33)SXI connected by VSS
i install two wism module , one in each core .
i need best two wism design and configuration in this case.
please advice me .

Hi Mohammad,
First, VSS redundancy it's completly independent for WiSM redundancy.
What you can do it's configure both WiSM at same mobility group, so you have a cluster with two controllers. With all APs registered on it, you can share half of your APs at WiSM-A and the other half at WiSM-B, because Primary, Secondary and Terciary controller settings are AP independent, So you have redundancy for you LWAPP wireless network.
Now, for VSS, you have your L2 and L3 unified at 6500 series switch. This config it's independent of anything, and you'll have to know how you wanna have the L3 of your network, making the virtual interfaces across VSS system.
You can take a look at this document, just to understand it: http://www.cisco.com/en/US/partner/products/hw/modules/ps2706/products_tech_note09186a0080a6c202.shtml
Best regards,
Please rate helpful replies.
Alexsandro.

Event Hub failover implementation

EventProcessorHost provides a persistent checkpoint storage in blob for failover. But this is only a convenience for failover not failover itself.
Event Hub does not have similar concept as Message Queue paired namespaces for queue redundancy (failover). How would one implement Event Hub redundancy easily?

hi - thanks for your suggestion, but adding "UserProperties" JSON array to the content of the message does not seem to work. When the message is received through IEventProcessor.ProcessEventsAsync()
the Properties dictionary on the EventData instance is still empty.
Please let me clarify what I am trying to achieve here.
I have a plain HTTP client (C++ client) sending messages to the Event Hub via HTTPS. I am trying to achieve similar to
this as I would in a C# client with the service bus client library for event hub:
SomeEventBody body = new SomeEventBody { SomeData = 100 };
EventData data = new EventData(body, serializer) //Object and serializer
// *** I WANT TO SET PROPERTIES ON THE EVENTDATA LIKE THIS ***
data.Properties.Add("Type", "Telemetry_" + DateTime.Now.ToLongTimeString());
await client.SendAsync(data); // Send single message async
When this message is received at the event hub processor, I am able to access EventData.Properties and use the "Type" property in the dictionary.
I want to be able to set the same "Type" property when I send this message from a plain HTTP client, and when the message is received by the event processor I want to be able to read the value out of the dictionary in the same way. I can't though
- because EventData.Properties is always just an empty collection

VIP failover time

I have configured a critical service(ap-kal-pinglist) for the VIP redundant failover, default freq,maxfail and retry freq is 5,3,5, so I think the failover time is 5+5*3*2=35s.But the virtual-router's state changed from "master" to "backup" in around 5 secs after connection lost.
Anyone help me to understand it?

Service sw1-up-down connect to e2 interface,going down in 15sec
Service sw2-up-down connect to e3 interface,going down in 4sec?
JAN 14 02:38:41 5/1 3857 NETMAN-2: Generic:LINK DOWN for e2
JAN 14 02:39:57 5/1 3858 NETMAN-2: Generic:LINK DOWN for e3
JAN 14 02:39:57 5/1 3859 VRRP-0: VrrpTx: Failed on Ipv4FindInterface
JAN 14 02:40:11 5/1 3860 NETMAN-2: Enterprise:Service Transition:sw2-up-down -> down
JAN 14 02:40:11 5/1 3861 NETMAN-2: Enterprise:Service Transition:sw1-up-down -> down

WiSM redundancy/failover

Similar Messages

Maybe you are looking for