WAAS - Multicast Deployment

Has anyone deployed WAAS using multicast for the WCCP registration? We're using the multicast address of 239.0.0.1 ip pim dense-mode and multicast routing being enabled. Does anyone know if you can use ip pim sparse-dense-mode instead of ip pim dense-mode? The documentation shows only an example for ip pim dense-mode. I've gotten it working in the LAB, I was just wondering what the recomendation is and if it's alight to use 239.0.0.1 instead of the 224.10.10.1 multicast address shown in the documentation.Is the 224.10.10.1 reserved for WAAS? If so then I would want to use that instead of 239.0.0.1.

Either multicast mode will work. In addition, WAAS/WCCP don't care which multicast group is used (they'll use what is configured).
Regards,
Zach

Similar Messages

Multicast deployment with WDS 2012R2

Hi,
Testing WDS multicast deployment using Server 2012 R2. DHCP is also on the same box.
Unicast deployment work fine. Tested multicast scenarios but didn't helped.
Following the URL:
http://social.technet.microsoft.com/forums/windowsserver/en-US/bba1f5d1-41ff-4351-8d6c-3070b2052a59/wds-and-multicasting-session-is-starting-too-soon
But it didn't helped either, nothing found in logs we well, even there were no log generated for multicast transmission.
Note: I don't have configured anything on Switch right now.
Any suggestions?
N.A.Malik

Hi,
I think this article will be helpful, please refer to subtitle “Prerequisites
for creating a multicast transmission”
Performing Multicast Deployments
http://technet.microsoft.com/en-us/library/dd637994(v=ws.10).aspx
Hope this helps.

WAAS inline deployment

Hello All,
I'm deploying a couple of WAE-512's in "inline" mode for a customer. I have the configuration and seems pretty straight forward, looks like I just need to have the inlinegroup created and allow all VLAN's. I will also have a crossover connection from the gateway router to the WAE and straight through from the WAE to the core LAN infrastructure. Is there any other things I should look out for?, gotcha's,etc?. Just looking to see what other people experiences have been with this type of deployment. Thanks for your help!

Beware of duplex issues that can pop-up from time to time on FE connections, hard coding can help avoid that. I would also suggest portfast where applicable ie switchports.

WAAS inline deployment options

Hi,
Can someone answer this basic question? I cant seem to find that much documentation on the inline modules.
Can you confirm whether or not devices can see each other on layer 2 across the two groups of an inline WAAS Ethernet module? i.e., if I have a router connected to the WAN of group 1 and another connected to the WAN of group 2, and the two routers are running HSRP (or even an ASA cluster), will they see each other correctly?
Thanks

Thanks for that. So if I had
Group1 = router1 - WAAS inline group1 - LAN switch
Group 2 = router2 - WAAS inline group2 - LAN switch
The routers would see each other through the WAAS and then the LAN switches (as if they were just connected to the switches), but wouldn't see each other directly across the WAAS module? Or you mean they don't see each other at all?
Cheers

Temporary wim-files for multicast transmissions still needed for WDS installation in Server 2012 R2?

Acording to
https://technet.microsoft.com/en-us/library/dn281955.aspx one of the new features for WDS in Server 2012 R2 for multicast is:
Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
However, this doesn't seem to be activated by default and I still get the following error when installing one or more machines using multicast:
"Windows Setup cannot locate a valid hard drive to store temporary installation files." However, once I remove Multicast from this install image, it installs without any problems at all.
I have also noticed that while multicasting, the installation will use the "Copying Windows files" phase, while downloading and copying the install.wim (or whatever name it is) locally on the hard drive first, so this will require lots of space.
So the question is, how do you enable this new feature that should be a part of WDS in Server 2012 R2???

Full version:
Following steps could help enable the feature:
1. Mount the boot image using dism.
e.g.
>dism /mount-wim /wimfile:c:\remoteinstall\boot\x64\images\boot.wim /index:2 /mountdir:c:\mount
2. Create a metadata file if no existing one. The metadata file should be in mountdir from the first step under mountdir\sources. And the file name should be: WdsClientMetadata.txt
3. Add entry to the metadata file: WDS.Client.Multicast.WIM.Streaming.Enabled=true
4. Save changes and unmount the boot image
e.g.
>dism /unmounts-wim /mountdir:c:\mount /commit
Sorry for the late reply, but I had to test this thoroughly since I didn't get it working right away. I tried both the regedit you first mentioned, and later also creating a textfile in the "/index:2 boot.wim", both without any success. I noticed
that creating the sources\WdsClientMetadata.txt with the data "WDS.Client.Multicast.WIM.Streaming.Enabled=true" gives me an error upon booting into WDS as follows (EUFI/IPv6-boot):
Same happens if I boot using IPv4 (an non-UEFI boot), except that there would be a plain IPv4-address instead in the error msg. Just for troubleshooting I tried writing WDS.Client.Multicast.WIM.Streaming.Enabled=false in the file instead, and WDS would throw
me the exact same error message. Once I delete the file sources\WdsClientMetadata.txt from the WDS/Boot image, the client boots ok, both for IPv4/IPv6. Disabling the firewall on the WDS didn't help, so something in the configuration is still missing? I'm getting
to a dead end here, and I suppose you're all out of advice on this one?
Thank you Shaon Shan for your great effort so far.

Imposible to deploy Ipv6 on lan with catalyst 2950t ?

Is it imposible to deploy Ipv6 on Lan enviroment with catalyst 2950T access switch?
Thanks

[similar question was asked in "ask the expert" so posting the same answer here as well]
- snip -
Hello,
This is a common question which comes quite often – What should I do with my old Layer2 switches (e.g. Catalyst 2900, 3900, 5000, etc.)? The simple answer is; IPv6 is transparent on L2 switches so no need to worry about it. However; there are couple cases where you would need to take a closer look.
Rightly asked; one is MLD snooping. Yes, if you are planning to have real IPv6 Multicast deployment then you would need to have products which support MLD snooping at Layer2. If you are not deploying IPv6 Multicast then I would not worry about it much.
Another one is when you have intelligent services on WLAN; may be it’s not Catalyst switch but it’s a AP where you are running intelligent services such as QoS, or ingress ACLs on AP or maybe actual controller based environment where you have thin APs and fat controllers in the back-end, but you have a distributed policy at the edge, if you are doing this and using IPv4 based protocols then you have to make sure that those products supports equivalent configurations for IPv6 capabilities or you would have serious road blocks.
Simple “2 rules of thumb” which I always tell customers:
There is no way you put 10lbs of sugar in a 5lb bag.
Always have plan/testing/validation/pilot before introducing any new protocol/technology in your production network.
Please take a look at http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6553/at_a_glance_c45-625859.pdf and lot of good information regarding Enterprise dual-stack case studies and recommendations at www.cisco.com/go/ipv6. I would recommend you to also work with your Cisco Account and Services teams for smooth Dual-Stack deployment.
Regards,
Salman

Multicast and wirerless

I have a 4404 controller running 6.0.202 code and more more people have Mac running bonjour and wanting to use Airplay. I see how to turn on Multicasting and even provide a Multicast address for IGMP snooping but does anyone have a good feel as to the overall load Multicast adds to the wireless network?
Thanks,
Gary

It depends on the type of deployment you have.
If the network infrastructure supports multicast, you should enable Multicast - Multicast as the controller multicast mode and choose a multicast address in the 239.X.X.X range.
If your network is not capable of supporting multicast, you would want to select Multicast - Unicast mode. This mode puts a load on the controller and on the wireless network as the Multicast is then sent as a unicast to each access point instead.
These support articles should help you.
Bonjour Deployment Guide
http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_tech_note09186a0080bb1d7c.shtml
Multicast Deployment Guide
https://supportforums.cisco.com/docs/DOC-14713

Distribution Point Multicast and Unicast at same time

Hi,
Scenario: SCCM 2012 R2. All in one server.
The server is distribution point (PXE and Multicast enabled).
The questions are:
If any Multicast dependency fails (i.e firewall blocks ports for multicast traffic),
Does the OS image will be deployed using unicast?
Is mandatory the multicast deployment method?
Thanks!

Hi,
No, when the multicast fail the TS would failed.
If you select the checkbox “Transfer this package only via multicast” in Configuration Manager Client Package Properties, which is mandatory.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WAAS No Peer - Insufficient option Space?

Hi,
I have a WAAS trial deployment running with a pair of 612s in the data centre and a coupe for remote 674s.
One site appears to be running fine (has optimised connections, both sides see each other in topology) but my new site cant discover the peer. From what I have read this commonly seems to be asymmetric routing but I only have one path in and out so it cant be that.
Checking show stat auto-discovery and debug auto-discover conn I see that my 'Insufficient Option-Space' count is increasing. Does anyone know what this means or how to resolve the undiscovered peer? I see the conns from the remote site in the head-end WAAS, so I believe that means WCCP is at least sending the traffic to the head-end device.
FYI the difference between the working and non-working sites is that one is using GRE/IPSec (working) and the other is plain IPSec (not working). Again, I don't believe its MSS or MTU as the default 1380 is large enough to pass unfragmented.
Thanks for your help,
Des

In fact, I think the devices still aren't auto-discovering after all; although they show in the topology table in the GUI, doing show stat tfo peer on either of the head end devices or the remote device shows no peer.
Looking at tcpdump, I definitely seem to see the MAC addresses entered into option21 / 33 at either end:
Remote end:
14:41:36.225065 IP (tos 0x0, ttl 58, id 50033, offset 0, flags [DF], length: 64) TERM_SERVER_IP.51979 > DEST_SERVER_IP.ssh: S [tcp sum ok] 1505981933:1505981933(0) win 49640
14:41:38.267296 IP (tos 0x0, ttl 250, id 0, offset 0, flags [none], length: 56) DEST_SERVER_IP.ssh > TERM_SERVER_IP.51979: S [tcp sum ok] 227079900:227079900(0) ack 1505981934 win 4128
Head-end:
14:41:34.505685 IP (tos 0x0, ttl 55, id 50033, offset 0, flags [DF], length: 64) TERM_SERVER_IP.51979 > DEST_SERVER_IP.ssh: S [tcp sum ok] 1505981933:1505981933(0) win 49640
14:41:34.508646 IP (tos 0x0, ttl 253, id 0, offset 0, flags [none], length: 56) DEST_SERVER_IP.ssh > TERM_SERVER_IP.51979: S [tcp sum ok] 3768269639:3768269639(0) ack 1505981934 win 4128
Those MACs are the correct addresses for the NIC on the WAEs. Shouldn't show stat tfo peer be showing the head and remote end devices (as with my other boxes)? I know ssh wont be optimised, but I just want to see the devices recognise each other as peers.
Thanks for your help.

WAAS on 1700

Hi Team
I just want to confirm if the 1700 support wccpv2 if so which image and can waas be deployed with this routers.
Thanks and Regards
Tau Maiula

ISR 1800 and above.
The following platforms are recommended for use with Cisco WAAS and the WCCP tcp-promiscuous services:
â¢ Cisco Integrated Services Routers (1800, 2800, 3800)
â¢ Cisco 3700, 7200 (NPE-400, NPE-G1, and NPE-G2 only), 7600, and ASR 1000 Series Routers
â¢ Cisco Catalyst 3560 and 3750 Series Switches
â¢ Cisco Catalyst 4500 and 4948 Series Switches
â¢ Cisco Catalyst 6500 Series Switches

WAAS hardware upgrade

We currently have a WAAS 7341 deployed at our central location and are in the process of upgrading that hardware to a 7371. Can I simply build the new server with the same OS version and then copy the configuration from the 7341 to the 7371, or is there a specific procedure I need to follow to upgrade the hardware?

We'd need a bit more information before saying for sure. What version of WAAS? If 4.1, are you running in CIFS native mode or legacy? If 4.1, are you using SSL Acceleration?
If 4.1 using native CIFS (not legacy) and no SSL acceleration, what you're proposing should work.
Thanks, Steve

Multicast: duplicated packets on nexus 7k with vpc and HSRP

Hi guys,
I'm testing multicast deployment on the lab shown below. The sender and the receiver are connected to the 6500 in two different vlans. The sender is in vlan 23 and the reciever in vlan 500. They are connected to the 6500 with a trunk link. There is VPc between the two nexus 7k and the 6500.
Furthermore, there is HSRP running on the two vlan interface 23 and 500 on both nexus.
I have configured the minimum to use PIM-SM with static RP. The RP is the 3750 above the nexus. (*,G) and (S,G) states are created correctly.
IGMP snopping is enabled on 6500, and the two nexus.
I'm using iperf to generate my flow, and netflow and snmp to monitor what happens.
All works correctly, my receiver receive the flow and it takes the good route. My problem is that I have four times more multicast traffic on the vlan interface 500 on both nexus but this traffic is only sent one time to the receiver (which is the good comportment) and the rest of the traffic is not shown on any other physical interface in outbound.
Indeed, I'm sending one flow, the two nexus receive it (one from peer link and the other from the 6500) in the vlan 23 (for example 25 packets inbound).
But when the flow is routed in the vlan 500, there is 100 packets on each interface vlan 500 on each nexus in outbound.
And when monitoring all physical interfaces, I only see 25 packets outbound on the interface linked with the receiver and the overflow isn't outgone.
I have joined the graphs I obtain on one of the nexus for the vlan 23 and the vlan 500. Netflow says the same things in bits/s.
Had someone already seen that? Any idea about the duplication of the packets?
Thanks for any comment,
Regards,
Configuration:
Nexus 1: n7000-s1-dk9.5.2.7.bin, 2 SUP1, 1 N7K-M132XP-12, 1 N7K-M148GS-11
Nexus 2: n7000-s1-dk9.5.2.7.bin, 2 SUP1, 1 N7K-M132XP-12, 1 N7K-M148GS-11
6500: s72033-adventerprisek9_wan-mz.122-33.SXI5.bin (12.2(33)SXI5)
3750: c3750-ipservicesk9-mz.122-50.SE5.bin (12.2(50)SE5)

Hi Kuldeep,
If you intend to put those routers on a non-vpc vlan, you may create a new inter-switch trunk between the N7K and allow that non-vpc vlan . However if those will be on a VPC vlan, best to create two links to the N7K pair and create a VPC, otherwise configure those ports as orphan ports which will leverage the VPC peer link .
HTH
Jay Ocampo

Task Sequence Failed 0x80091007. SCCM 2012 R2 OSD

Hi,
I have multicast deployment issue with Configuration Manager 2012 R2.
Unicast is working fine, Multicast throwing error 0x80091007.
Wait time starts and after 40 to 50 seconds pops up with error 0x80091007
I have already tried Redistributing and recreating image, trying with different systems, Direct access from DP settings, validating share access and all.
There is no SMSTS.LOG available on client systems.

Hi,
How about MCSISAPI.log?
Here is a blog talks about this error, you could have a look.
"Update 19-6-2013: Nick send me a possible solution in comments. What you have to do is make sure you don't have a custom Multicast range set - use the setting "Use IPv4 addresses within any range"
in the SCCM 2012 multicast tab under Distribution Point properties.
The default is 239.0.0.1 to 239.0.0.254 - if you have a custom range set - it IGNORES it and uses a random address in 239 range anyways. He has tried to statically set a 239 range on both SCCM multicast and WDS multicast settings - ignores them still uses a
random address in the 239 range regardless.
On your Cisco core - if your using that - make sure your ACL's and Rendezvous Point ACL for PIM permits the 239 range. As soon as this was done it's all working. > Will try that myself next month! "
http://henkhoogendoorn.blogspot.com/2013/02/multicast-error-0x80091007-during.html
(Note: Microsoft provides third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WAE IRQ Routing Issue

Hi,
Has anyone come across the issue with the IRQ for routing on the WAE?
My edge box in our customer demo lab stopped routing traffic and only starts once you er-apply the gateway statments back in. Then network connectivity is restored and the WAE thinks its passing traffic to be acceleration process but in fact the traffic is worse than native across the WAN. This is on a 512 with an inline module running either 4.0.15b6 and or 4.0.17b14
Cheers
Rob

Rob,
Which "gateway statements" are you referring to? Obviously performance shouldn't be worse than native when WAAS is deployed. Can you please verify what speed/duplex the inline ports are configured/running as?
Thanks,
Zach

OTV site vlan with multiple overlay interface

Hi,
I have an OTV multihoming sites. 2 sites. 2 otv edge device each site.
and with multiple overlay interface sharing 1 joint interface
otv edge device connected to multiple VDC.
each internal / downlink will forward different vlan for each vdc.
================================
example
int overlay 1
otv extends-vlan 10
int overlay 2
otv extends vlan 20
int eth 2/1
description trunk to VDC1
switchport trunk allowed vlan 10,100
int eth 2/2
description trunk to VDC2
switchport trunk allowed vlan 20,100
otv site-vlan 100
================================
i understand that i can only use 1 site vlan.
so in order for the failover to happen, both eth 2/1 and eth2/2 must fail?
what if only int eth2/1 fail? will the int overlay 1 failover to secondary otv device?
thanks,
ivan

"So when querying the adjacency server the ED then knows which other ED is within the same site?"
Yes for the first part of the question, using the site Vlan unique to each site.
Why do you need a routed link between ED's at local site? You dont need to connect those back-back over L3. Moreover if you want to use it for L3 ADJ over peer-link, you need to make sure that VLAN that you are using is not allowed on the VPC member ports, just on the peer-link, else VPC loop alrorithm will break your traffic.
Are you planning to use multicast or a Unicast deployment? I remember I tried testing the topology in a POC for one of my customer, things did not work as expected in multicast deployment mode and worked fine in Unicast Adjacency server mode. I need to go back and check my notes on this.
I would rather have the join-interface go back to a routed core at site rather than back-back connecivity as it opens up the tested Multicast deployment mode.
Cheers,
-amit singh

WAAS - Multicast Deployment

Similar Messages

Maybe you are looking for