Multicasting with an SGE2010P

Hi,
I have just purchased a SGE2010p switch. I am hoping to multicast with windows deployment services WDS
and also hoping someone might be able to give a basic explanation (configuration would be brilliant!) on the process.
On the switch webpage, we ticked the box for IGMP snooping. WDS configured with multicasting and that part of
it works. Getting transfer rates of 16,000KBps (according to WDS console). Would have thought gigabyte should be
better than that, but still better than the 250KBps without IGMP snooping.
The problem is that all traffic is still being sent to all other ports on the switch. There is only the switch
and no routers involved. Some documents indicate IGMP querier is required, but there seems no option for that that
I can find. I believe we later enabled autolearn (but not certain - dont have access to the switch at the moment)
and then WDS broke <again>.
So I am hoping someone can please educate me!
What needs to be done to prevent the switch from forwarding data to all ports
Is AutoLearn the same as an IGMP querier?
What is bridge multicast forwarding? Sounds like passing multicasts across routers?.
Do we need to create a multicast group on the switch? I would think no, that WDS does all that.
Does this switch support MLD snooping?
Any help appreciated
thank you!

That's not going to work; manually defining groups means static multicasting (ie not dynamic nor scalable). That sort of defeats the purpose of IGMP snooping.
The problem is Microsoft's default multicast range is incompatible with IGMP and switches.
When a multicast layer 3 address is mapped to layer 2 (for the switch multicast layer 2 address), only the last 23 bits of the IPv4 address come across. The other bits are lost as we need specify the ethernet OUID owned by iana.  (01-00-5e).
So the default range by microsoft 239.0.0.1-239.0.0.255 maps out at the ethernet layer:  01-00-5e-00-00-01 to 01-00-5e-00-00-ff
The problem is, the 224.x.x.x mulicast control messages also map out like that, e.g. 224.0.0.1 maps to 01-00-5e-00-00-01.
So 224.0.0.1 and 239.0.0.1 map to the same ethernet (layer 2) mac address. Therefore the switch has no alternative but to broadcast as 224.0.0.1 = all nodes.
So try changing the default WDS address to something that wont get confused by the switch, e.g. 239.67.54.3 to 239.67.54.255.
Have tested this in a lab only but should fix the problem.
bye
Oh, bridge multicast forwarding is for when the traffic needs to be forwarded (ie to another switch or router). Filtering is only to be touched to block all multicast traffic - perhaps for permanent groups that need to be manually configured. You dont need to touch that.

Similar Messages

  • QOS problem (multicast) with 3750

    Hi,
    I need help to solve following problem.
    I have setup qos in our 3750, see below.
    Unicast traffic is handle correct, However with multicast streams the router set the dscp to 0
    Has somebody any idea what is missing?
    Too old sw?   Cisco IOS Software, C3750 Software (C3750-ADVIPSERVICESK9-M), Version 12.2(35)SE,
    Regards Niklas
    ip multicast-routing distributed
    ip multicast multipath
    mls qos srr-queue input priority-queue 1 bandwidth 10
    mls qos srr-queue input dscp-map queue 1 threshold 1  46
    mls qos srr-queue input dscp-map queue 2 threshold 1  11 24 30 48
    mls qos srr-queue output dscp-map queue 1 threshold 1  48
    mls qos srr-queue output dscp-map queue 2 threshold 1  46
    mls qos srr-queue output dscp-map queue 3 threshold 1  40
    mls qos srr-queue output dscp-map queue 4 threshold 1  11 24 30
    mls qos
    interface GigabitEthernet1/0/22
    switchport access vlan 41
    switchport mode access
    load-interval 30
    srr-queue bandwidth share 25 25 25 20
    priority-queue out
    mls qos trust dscp
    interface GigabitEthernet1/0/23
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 40
    switchport mode trunk
    load-interval 30
    srr-queue bandwidth share 25 25 25 20
    priority-queue out
    mls qos trust dscp

    Hi,
    Here comes the printouts:
    with mls qos enabled:
    cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/22 statistics
    GigabitEthernet1/0/22
      dscp: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            0            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      dscp: outgoing
      0 -  4 :     8881981            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0          307            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      cos: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :     8881981            0            0            0            0 
      5 -  7 :           0          307            0 
    Policer: Inprofile:            0 OutofProfile:            0
    cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/23 statistics
    GigabitEthernet1/0/23
      dscp: incoming 
      0 -  4 :     8931330            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0          202            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      dscp: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0         1206            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      cos: incoming 
      0 -  4 :    11357772            0            0            0            0 
      5 -  7 :           0            2            0 
      cos: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  7 :           0         1206            2 
    Policer: Inprofile:            0 OutofProfile:            0
    cisco-Mcast#
    mls qos disabled:
    cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/22 statistics
    GigabitEthernet1/0/22
      dscp: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            0            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      dscp: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0         7371            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            0            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      cos: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :        7371            0            0            0            0 
      5 -  7 :           0            0            0 
    Policer: Inprofile:            0 OutofProfile:            0
    cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/23 statistics
    GigabitEthernet1/0/23
      dscp: incoming 
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0        23281            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            0            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      dscp: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           0            0            0            0            0 
    45 - 49 :           0            0            0            2            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0            0            0            0            0 
    60 - 64 :           0            0            0            0 
      cos: incoming 
      0 -  4 :       29272            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :           0            0            0            0            0 
      5 -  7 :           0            2            0 
    Policer: Inprofile:            0 OutofProfile:            0
    cisco-Mcast#
    BR Niklas

  • Multicasting with a guest anchor configuration.

    Hi All
    First time posting. :-)
    I have a guest anchor controller in our DMZ servicing Apple devices. We are looking at options for using Apple TV to display/stream presentations from executive iPads and such. Since it uses bonjour (multicast) would I be able to utilize the new features available in 7.0.116.0 to implement this solution? I have 4 WiSM 1s servicing the headquarters building and one 4402 guest anchor. I believe this is possible based on the note in the document: VLAN Select and Multicast Optimization Features Deployment Guide; specifically the section:
    Note: In a Guest Tunneling scenario, roaming between export foreign and export foreign is supported. However, roaming between export foreign and export anchor is not supported with VLAN Select.
    In case of Auto Anchor:
    Clients joining a foreign WLC, which is exported to an anchor WLC and mapped to a interface group, will receive an IP address in round robin method inside the interface group.
    Clients joining a foreign WLC, which is exported to an anchor WLC and mapped to a interface only, will receive an IP address from that interface only.
    Clients roaming between two or more foreign controllers mapped to a single anchor WLC with an interface group configured will be able to maintain its IP address.
    Since I only have one guest anchor, I would assume based on this that I would fall under the export foreign - export foreign option and implementing this would be possible.
    Could someone advise?
    Thank you in advance!!

    Thank you for information, I have the same problem. So I made a search on EoIP tunnel and Multicast.
    http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a00808b4c61.shtml
    Q I have a guest tunneling, Ethernet over IP (EoIP) tunnel, configured between my 4400 Wireless LAN Controller (WLC), which acts as the anchor WLC, and several remote WLCs. Can this anchor WLC forward subnet broadcasts through the EoIP tunnel from the wired network to wireless clients associated with the remote controllers?
    A. No, the WLC 4400 does not forward IP subnet broadcasts from the wired side to the wireless clients across the EoIP tunnel. This is not a supported feature. Cisco does not support tunneling of subnet broadcast or multicast in guest access topology. Since the guest WLAN forces the client point of presence to a very specific location in the network, mostly outside the firewall, tunneling of subnet broadcast can be a security problem.
    unofortunately it seems that multicast over EoIP does not work.

  • Can receive multicast with 2 different IP Subnet

    I Have Sun Server installed with Solaris 10, and because the application requirement I had 2 interface with different subnet for example 10.160.x.x and 10.19.x.x right now only interface 10.160.x.x can receive multicast packets while multicast packet from 10.19.x.x subnet can not be receive by the 10.19.x.x interface.
    Is there any configuration need so the 10.19.x.x can receive the multicast packets.
    Sorry if my english is not good.
    Regards,
    Abi

    MrHoffman wrote:
    Where? There are various spots to [learn about Mac OS X Server|http://www.apple.com/server/macosx/resources/documentation.html]. For this case, in [the web administration manual|http://images.apple.com/server/macosx/docs/WebTech_Adminv10.6.pdf], certainly. Or the "Managing Multiple Sites on One Server" in the Web section of the Server Admin help file. Via Google, of course. Or [something here|http://labs.hoffmanlabs.com/node/1329]? The underpinnings of this environment are Apache, and you can learn about the pieces underneath Server Admin (and what Apple calls "sites") at the [Apache web site|http://www.apache.org], and in various Apache books.
    I found the Apple's web administration manual you referenced contains numerous inaccuracies that it makes it difficult to use. For example, on page 35 is says:
    +To create a website:+
    +1. Open Server Admin and connect to the server.+
    +2. Click the triangle at the left of the server.+
    +3. The list of services appears.+
    +4. From the expanded Servers list, select Web.+
    +5. Click Sites, then click the Add (plus) button to add a site.+
    The problem is there is you cannot ad a site from Server Admin, and it actually should be Server Preferences. Server 10.6 has a tab called Custom Sites, and there is no reference to it in the web administration manual. When I add a custom site, which I think is a second website in addition to the one that the server hosts, it asks about IP address and port (80 as a default). the IP address has an option "Any" and "10.0.1.5". I tried both and none of them works.
    I will try to research more, but if you have any suggestion on how to setup a second website (domain name) correctly, please respond.

  • Breaking 100Mbps on Multicast with WDS

    I'm building WDS (with MDT) servers that will be replacing legacy Symantec Ghost imaging environments.
    I really like the "Auto-cast" concept of a revolving multicast. That could really be game-changing.
    However, all my servers refuse to go past the 100Mbps seemingly artificial limit. This has been seen on various HP, Dell, and VMWare servers running Windows Server 2008 R2, 2012, and 2012 R2.
    For the most part, the transmission stays pegged at 99.9-100Mbps, occasionally suffering a drop to lower speeds, and then jumping back up. 
    A Ghostcast on the other hand will jump from 30Mb to 300Mb wildly.
    The network is full Gig, all gig ports, and all switches with IGMP(v3) support and snooping set up.
    What can I do to unlock full Gig multicast speeds? Even a jump from 100Mb to 500Mb will be a huge jump.
    I am multicasting to SSD devices and modern machines- I do not believe that disk I/O on the target device is a problem. Server I/O is on a RAID 5 or greater.
    Thanks for any help...!

    Hi,
    Notice: Content referred modifying registry, please backup before any operation.
    The setting is also available via registry setting. In order to make sure the settings are applied, we ca have atry.
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC
    Change the value of "DefaultProfile" to the desired setting (10Mbps, 100Mbps, 1Gbps, or Custom).
    If using Custom, make sure to make the necessary customizations under the registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Profiles\Custom
    Do not make any customizations to any of the built in profiles (10Mbps, 100Mbps, 1Gbps). Use the Custom profile if any customizations
    are desired.
    Hope this helps.

  • Multicast Mroute behavior for local VLAN multicast (with overlap)

    We have a multicast address that exists at various locations but we want to isolate them at each location to a single VLAN.  We run PIM Sparse with anycast RP throughout our Enterprise.  Our original thought was to just turn off PIM on the SVI/VLAN at a campus and isolate that multicast to the VLAN it is in.
    We are still learning the Multicast address via PIM from the other sites we have not turned PIM off yet (since it is an overlapping address).  The question came up that if you disable PIM for that VLAN/SVI would the multicast stay local if the default gateway for that VLAN still has a multicast route it learned via PIM from another site?  Or would that VLAN without PIM still use the mroute table to connect to the Multicast address?

    Paul
    Sorry, i didn't realise this was addressed to me.
    To be honest i have never used this command but reading up on it it would seem you certainly could block the flow of multicast packets between the interface for the group(s) you wanted to so it would be a way of isolating traffic between vlans.
    In terms of the RP announcement messages there is a keyword you can add to the command "filter-autorp" which filters discovery and announcement messages as well. But i wouldn't like to say for sure exactly how it would or wouldn't work without testing ie. do you need to filter the RP announcements before they reach the SVI or would it work applied to the SVI.
    I could see a use for this if you had a number of SVIs that needed to route the multicast stream between themselves but not to other L3 subnets. But the topology would be a little difficult on a L3 switch ie. if half the SVIs need to route the multicast stream but the other half didn't where do you apply the command. It would have to be on each SVI you didn't want to receive the stream.
    It would work better if, for example, you had a L3 switch connected to a router with L3 routed ports and all the SVIs should route the multicast stream but it should stay local to the L3 switch so it is blocked on the L3 uplink (and other potential streams from the router to the L3 switch blocked as well).
    Hope that made some sense. It's sometimes difficult to explain things without a diagram
    Jon

  • MultiCasting with applets ??

    Hi
    I would like to ask about how can i avoid the problem of using the multicast socket with the applet as i want to build an applet and i knew that multicasting is not applicable with applets
    but also i wanna use multicast socket for the multicasting of data stream in conferencing project
    so any suggestions related to this problem is appreciated
    thanks alot in advance

    That's not going to work; manually defining groups means static multicasting (ie not dynamic nor scalable). That sort of defeats the purpose of IGMP snooping.
    The problem is Microsoft's default multicast range is incompatible with IGMP and switches.
    When a multicast layer 3 address is mapped to layer 2 (for the switch multicast layer 2 address), only the last 23 bits of the IPv4 address come across. The other bits are lost as we need specify the ethernet OUID owned by iana.  (01-00-5e).
    So the default range by microsoft 239.0.0.1-239.0.0.255 maps out at the ethernet layer:  01-00-5e-00-00-01 to 01-00-5e-00-00-ff
    The problem is, the 224.x.x.x mulicast control messages also map out like that, e.g. 224.0.0.1 maps to 01-00-5e-00-00-01.
    So 224.0.0.1 and 239.0.0.1 map to the same ethernet (layer 2) mac address. Therefore the switch has no alternative but to broadcast as 224.0.0.1 = all nodes.
    So try changing the default WDS address to something that wont get confused by the switch, e.g. 239.67.54.3 to 239.67.54.255.
    Have tested this in a lab only but should fix the problem.
    bye
    Oh, bridge multicast forwarding is for when the traffic needs to be forwarded (ie to another switch or router). Filtering is only to be touched to block all multicast traffic - perhaps for permanent groups that need to be manually configured. You dont need to touch that.

  • Multicast with Air

    Hello,
    From:
    http://forums.adobe.com/message/2423240#2423240
    It was said:
    remember you'll need FP10.1 beta *and* the accompanying playerglobal.swc to compile these with the Flex SDK.
    -mike
    I've got multicast working with FP 10.1 per instructions.
    My question is;  what is required for AIR to compile multicast?
    Flex 4?
    AIR 2?
    Stratus special airglobal.swc ?
    Cheers,
    Arnie

    i believe you should just need the AIR 2 SDK.  that should give you access to all the new APIs.
    -mike

  • WCCP Multicast with 6500

    I have two 6500s (6509-1 and 6509-2)and two WAE-674 devices. I am trying to configure these devices in a redundant way. However the WAEs form wccp relation only with the 6509-2.
    6509-2#sh ip wccp 61 detail
    WCCP Cache-Engine information:
    Web Cache ID: 172.27.249.65
    Protocol Version: 2.0
    State: Usable
    Redirection: GRE
    Packet Return: GRE
    Assignment: HASH
    Initial Hash Info: 00000000000000000000000000000000
    00000000000000000000000000000000
    Assigned Hash Info: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    00000000000000000000000000000000
    Hash Allotment: 128 (50.00%)
    Packets Redirected: 0
    Connect Time: 00:36:19
    Web Cache ID: 172.27.249.66
    Protocol Version: 2.0
    State: Usable
    Redirection: GRE
    Packet Return: GRE
    Assignment: HASH
    Initial Hash Info: 00000000000000000000000000000000
    00000000000000000000000000000000
    Assigned Hash Info: 00000000000000000000000000000000
    FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    Hash Allotment: 128 (50.00%)
    Packets Redirected: 0
    Connect Time: 00:36:18
    however on the 6509-1
    6509-1#sh ip wccp 61 detail
    WCCP Cache-Engine information:
    Web Cache ID: 172.27.249.66
    Protocol Version: 2.0
    State: NOT Usable
    Redirection: L2
    Packet Return: L2
    Packets Redirected: 0
    Connect Time: 01:17:18
    Assignment: MASK
    Web Cache ID: 172.27.249.65
    Protocol Version: 2.0
    State: NOT Usable
    Redirection: L2
    Packet Return: L2
    Packets Redirected: 0
    Connect Time: 00:00:15
    Assignment: MASK
    Redirection (L2 on 6509-1 and GRE on the 6509-2) methods are shown differently on the 6500 switches.
    However the configurations on the WAE side is same:
    HOAE1674#sh run
    <outputs omitted>
    primary-interface Standby 1
    interface Standby 1
    ip address 172.27.249.65 255.255.255.240
    exit
    interface GigabitEthernet 1/0
    standby 1 priority 250
    exit
    interface GigabitEthernet 2/0
    standby 1
    exit
    ip default-gateway 172.27.249.78
    <outputs omitted>
    wccp router-list 1 224.10.10.10
    wccp tcp-promiscuous router-list-num 1
    wccp version 2
    And the 6500 configurations:
    6509-2#sh run int vlan 311
    interface Vlan311
    description WAAS-Normal
    ip address 172.27.249.77 255.255.255.240
    ip wccp 61 group-listen
    ip wccp 62 group-listen
    ip pim dense-mode
    standby 211 ip 172.27.249.78
    6509-2#sh run | i redire
    ip wccp 61 group-address 224.10.10.10 redirect-list 101
    ip wccp 62 group-address 224.10.10.10 redirect-list 102
    I know that L2-redirection and masking advised on the 6500s, however when I configure, 6500 sh ip wccp output shows that GRE masking is used.
    The WAE devices are connected directly to the 6509-2, I suspected a multicast issue, to test I shutdown the 6509-2 vlan interface but no help
    The version on the 6500s are same (12.2SXF8), as I know that 12.2SXF14 is suggested. However a software upgrade requires a lot of change management procedures. I want to be sure that I did not make a configuration mistake.

    Thanks Dan, Matthew
    After I remove l2-return, wccp seems to be ok:
    HOAE1674#sh run | i wccp
    wccp router-list 1 224.10.10.10
    wccp tcp-promiscuous router-list-num 1 l2-redirect mask-assign
    wccp version 2
    6509-1#sh ip wccp 61
    Global WCCP information:
    Router information:
    Router Identifier: 192.168.2.253
    Protocol Version: 2.0
    Service Identifier: 61
    Number of Cache Engines: 2
    Number of routers: 2
    Total Packets Redirected: 0
    Redirect access-list: 101
    Total Packets Denied Redirect: 13843
    Total Packets Unassigned: 0
    Group access-list: -none-
    Total Messages Denied to Group: 0
    Total Authentication failures: 0
    6509-1#sh ip wccp 61 de
    WCCP Cache-Engine information:
    Web Cache ID: 172.27.249.66
    Protocol Version: 2.0
    State: Usable
    Redirection: L2
    Packet Return: GRE
    Packets Redirected: 0
    Connect Time: 01:32:23
    Assignment: MASK
    Mask SrcAddr DstAddr SrcPort DstPort
    0000: 0x00001741 0x00000000 0x0000 0x0000
    Value SrcAddr DstAddr SrcPort DstPort CE-IP
    0032: 0x00001000 0x00000000 0x0000 0x0000 0xAC1BF942 (172.27.249.66)
    0033: 0x00001001 0x00000000 0x0000 0x0000 0xAC1BF942 (172.27.249.66)
    0034: 0x00001040 0x00000000 0x0000 0x0000 0xAC1BF942 (172.27.249.66)
    0035: 0x00001041 0x00000000 0x0000 0x0000 0xAC1BF942 (172.27.249.66)
    0036: 0x00001100 0x00000000 0x0000 0x0000 0xAC1BF942 (172.27.249.66)
    0037: 0x00001101 0x00000000 0x0000 0x0000 0xAC1BF942 (172.27.249.66)
    0038: 0x00001140 0x00000000 0x0000 0x0000 0xAC1BF942 (172.27.249.66)
    Now I am trying to redirect packets over the these appliances.
    However TCP connections could not be established between redireced subnets. I can sniff that packet is forwarded to the WAAS but it did not send a respond. I saw that bad bucket error are incrementing when I try new connections.
    HOAE1674#sh wccp gre | i buckets
    Packets dropped due to bad buckets: 516
    regards,
    Bulent

  • SG 300 10 - Multicast with multiple switches in LAN

    Hi there,
    I have short question concerning Multicast in my LAN. My internet router acts as an IGMP Proxy for the LAN and distributes IPTV there. The router is connected to one of my three SG 300 10 Cisco switches (connected to one another via uplink port). Now I want all switches to send multicast traffic to only the recipients of such traffic (PCs with VLC and Network Media Players) connected to either one of them. How do I have to configure the switches to do so and not flood the LAN with multicast traffic, is it enough to enable IGMP Snooping on each switch?
    Thanks in advance and best regards
    Christoph

    Hi Christopher, by the default the switch will treat multicast traffic like a broadcast until you enable the Bridge Multicast Filter and IGMP snooping.
    Navigate to; Multicast -> Properties and enable the Bridge Multicast Filtering
    Navigate IGMP snooping -> Enable
    Multicast -> Multicast Router Port
    Then make sure to specify the mrouter port (which must be a member of a static vlan, not a dynamic vlan)

  • Stacking SGE2010P with another SGE2010P

    Hi,
    I would like to ask on how to stack 2 SGE2010P switches which particular port on the ethernet is to be use for the stacking. Because for SGE2000P we can use 12 and 24 to do stacking.
    Kindly help me on this issue
    Best Regards,
    Gilbert Gimeno

    Gilbert,
    SGE2010 - Default stacking ports: 24/GBIC 3, 48/GBIC 4.
    To configure stacking, see the "Administration Guide" - Chapter 2.
    http://www.cisco.com/en/US/docs/switches/lan/csbms/sfe2000/administration/guide/SFE-SGE2xxx_Admin_Guide.pdf
    Thank you,
    Darren

  • Multicast with NIO

    Hello,
    I searched the web for some time now, and got the impression that multicast support for NIO is not possible.
    I was woner if it's possible to implement a SelectorProvider, and provide the openSelector, openDatagramChannel etc', and then implement the inheritedChannel() method. for that I need an implementation for SelectorImpl, DatagramChannelImpl, SocketChannelImpl etc'.
    Did anybody ever done a thing like that? Or has a code for that purpose?
    thanks
    Udi

    Wait for 1.7. It's coming.

  • WDS & MDT 2012 Integration Questions: Do I need an install image on WDS if I'm multicasting from MDT

    I'm running WDS & MDT 2012 on Server 2012 for my deployment solution.  I have a few questions about what happens when you integrate WDS & MDT.
    Perhaps this is a simple question, but if WDS multicasts the installation image from MDT, do I need to have an image in the installation folder of WDS?  I have the "Enable multicasting" box checked whenever I update my deployment share
    Also, my server is running X64 architecture, so I have the x64 WAIK installed.  but I'm having issues editing the unattend.xml on my server because my images are all X86.  Keeping in mind that I already have the X64 WAIK installed, can i install
    the X86 WAIK tools on my server?

    Sorry, that's two questions you only get one... Just kidding...
    FOr MDT, you don't import the images into the WDS console, you just need to add a Multicast namespace.
    http://keithga.wordpress.com/2014/04/23/multicasting-with-mdt/
    AS for the unattend.xml edit issue, that is known:
    http://blogs.technet.com/b/deploymentguys/archive/2009/08/27/windows-7-waik-and-custom-images.aspx
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Multicast stops after about 2 minutes

    Hi,
    We are testing IP Multicast, with Flahs media player 4.0.
    We set up the encoder and generated the manifest file.
    Multicast start, but we see lot of bufferring and video running fast.
    After about 2 minutes, the encode stops publishing to the server.
    We are using digital rapids as the encoder.
    Any idea this might be causing ?

    A few things to try:
    1. If you're using the 'multicast' application that ships with FMS4, it logs state transitions and event info to the app log as the server-side multicast relay (a server-side NetConnection/NetGroup/NetStream) start up and redirect the ingest stream from FMLE into the Flash Group. I'd recommend reading through that and verifying that the server-side objects handling the relay into the Group are happy (i.e. not disconnecting or being closed down).
    2. The multicastplayer client SWF app has some flashvars defined in the HTML shim file that loads it. One of these is a debug flag. If you set that to true, you'll get some debug info surfaced up to your UI. This will include the various events the client is processing on its NetConnection/NetGroup/NetStream that's being used to play the multicast stream out of the target Flash Group. Feel free to post those details back to this thread.
    3. If you're doing IP multicast, that won't work over the public internet. In that case you'll want to be using P2P multicast.
    Best,
    Seth

  • Clustering on multi cpu box without multicast

              Just wonder whether weblogic cluster can be configured to not use IP multicast
              if the clustered servers are running on the same multi cpu box as I would have
              thought that in memory communication would be a faster option in this case.
              This is again as we were told that Weblogic doesnt scale well for more than 2
              cpus per box.
              If we are using a 4-6 cpu box then in this case it makes more sense to have 2/3
              instances
              per server communicating via mem and not multicast
              

    Just wonder whether weblogic cluster can be configured to not use IP          multicast
              > if the clustered servers are running on the same multi cpu box as I would
              have
              > thought that in memory communication would be a faster option in this
              case.
              Multicast with a TTL of zero is basically implemented by the OS as a shared
              memory approach, so there is usually very little difference in performance.
              > This is again as we were told that Weblogic doesnt scale well for more
              than 2
              > cpus per box.
              > If we are using a 4-6 cpu box then in this case it makes more sense to
              have 2/3
              > instances
              > per server communicating via mem and not multicast
              The scalability on various numbers of CPUs differs greatly. It is vastly
              improved on more recent versions of WebLogic with more recent versions of
              the JVM. Back on JVM 1.2 with WL 5.x and earlier, you would have to run
              multiple instances in order to "soak" a box. The best way to determine if
              this is still the case is to use a load test that (with everything else
              equal) will soak the box with multiple JVMs but not with a single one.
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "r g" <[email protected]> wrote in message
              news:3f181388$[email protected]..
              >
              

Maybe you are looking for