Redundent cotrllers multicasting

hello friends,
if we have 2 cisco 2504 series wlcs and use multicast fetures in both and both are primary and secondry for LAPs
what about of we use multicast ip address let's say 255.239.1.60 can we use the same ip address for the secondry contrller too or we should use any other ip ?
thanks

If Primary got 230.0.0.1 then use 230.0.0.2 for secondary WLC.
http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70ccfg.html#wp1089006
Guidelines for Using Multicast Mode
Follow these guidelines when you enable multicast mode on your network:
•The Cisco Unified Wireless Network solution uses some IP address ranges for specific purposes, and you should keep these ranges in mind when configuring a multicast group:
–224.0.0.0 through 224.0.0.255—Reserved link local addresses
–224.0.1.0 through 238.255.255.255—Globally scoped addresses
–239.0.0.0 through 239.255.x.y /16—Limited scope addresses
•The CAPWAP multicast group configured on the controllers should be different for different controllers.

Similar Messages

Redundant MOH Server and multicast addressing

Per SRND:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guide_chapter09186a00806e8c28.html#wp1043768
I want to use the 2nd method:
"Configure separate media resource groups (MRGs) for the same MoH server, with one MRG configured to use multicast for audio streams and the second MRG configured to use unicast. "
as well as use redundancy. My questions is:
Can I use the same multicast address (ie 239.1.1.1) for primary and backup moh server or do I need to put in a 2nd multicast address (ie 239.1.1.2) on the backup MOH server.
Thanks

Maybe for second Multicast MOH server, start at 239.1.10.1 or like 239.1.1.50.
Sankar is right, but if you add multiple audio source files and have like 4 multicast audio sources then it may start higher up for the audio source you are using.
In my time working on fixing systems I've seen people don't maintain/delete old audio sources so starting second MOH server at 239.1.1.11 could cause problems/conflicts potentially.
It would also be nice if they displayed the mcast address used for each audio source in CCMadmin so admins could see it easily without having to figure it out. Or for people who aren't aware of how the addresses increment per codec/audio source.

Redundant Multicast switching

All, I have a customer with a L2 network with multiple VLANS and consisting of multiple access switches with two L2/L3 core switches. Both core switches have a SVI for each vlan using HSRP to provde redundant Default Gateways.
The main core switch is a Cisco 6500 (running 12.2(33)SXJ6) and the backup core switch is a Cisco 4500.
One of the applications on this network is Multicast which needs the protection of the redundant core switches (this is for a critical public infrastruction and so requires the protection, if one switch fails the other must continue to support the service).
I initially tried configuing "IP PIM DENSE-MODE" on the VLAN interfaces (one of the solutions as per Cisco doc #68131 which discribes a problem and solutions for configuring multicast on a L2 network) to make the switch act as a "mrouter". When I configure pim on the applicatable vlan's on one (the main core) switch the multicast application/s work properly but when I then configure pim on the applicatable vlan's on the other (backup) switch igmp-snooping seems to fail and all interfaces on the vlan get the multicast traffic whether they have joined the group or not (effectively causing a DOS attack on the interfaces that haven't joined the group).
Another solution from document #66131 is to enable the igmp querier feature on the L2 switches (and I assume, remove the IP PIM configuration). This should make the switch act as a mrouter "proxy".
I have also read the chapter (chaper 38) in the IOS configuraiton guide on "Configuring IGMP Snooping" which has a section on configuring redundant igmp snooping queriers. I am thinking of trying the configuration this section is suggesting where I would remove the IP PIM and, instead, configure "ip igmp snooping querier" on the appropriate vlan interfaces on both switches. Unfortunately I do not have a lab to test this out on and so am currently limited to trying this out on the actual network (scary!).
So, my questions. First, and in general, does anyone have any words of wisdom for me? Two, if my network only has mrouter "proxies" only but no actual mrouter (as I believe will be the case if I am only using the "querier" configurations) will that cause any problems with the multicast applications?
I am under some immediate pressure to solve this redundancy issue so any help would be greatly appreciated.

Steve
Can I have both IP PIM and the igmp querier configurations on the same (routed) VLAN interface?
You don't need to. The IGMP querier function is only used when you don't have PIM enabled on the vlan interface. When you enable PIM on a L3 interface it then sends out IGMP queries and the switch listens to the responses with IGMP snooping so it can record the multicast mac address to the correct ports. If you don't have PIM enabled, something still needs to make those IGMP queries otherwise the switch has nothing to listen for. So that is what the IGMP snooping querier does. So its one or the other. With PIM enabled you do not need the querier.
To be honest i didnt understand a lot of what you said about your physical connectivity other than each switch sees the other switches via trunk links.
So when you enable PIM on the 6500 only multicast works for all clients on all switches properly. When you enable it on both switches multicast is then flooded to all interfaces on both switches ?
Cna you just clarify what you mean by all interfaces ie. do you mean all end devices on all the switches start seeing multicast traffic ?
When you enabled PIM on the 4500 did you enable it on all L3 interfaces at the same time ?
I am just trying to get a picture of which switches were affected and how they connect back to the core switches. Like i say i did not really follow your setup because i have no experience of that. Is each access switch in effect connected to both core switches or do they only connect to one or the other ?
Jon

How to protect a PIM-SM network from unauthorized pim routers and multicast sources?

Hi,
we're using pim sparse mode in a customer network with catalyst 2/3/4/6K switches, all multicast routers are redundant with pim dr running for access subnets. RPs are configured with anycast rp.
A) Is there any possiblity to prevent rogue pim routers/igmp queriers connected to host ports from getting connected to the legal pim routers and from getting involved in the local igmp traffic?
Maybe like DHCP Snooping used with DHCP. I read that in the latest Sup2T ios (http://www.cisco.com/c/dam/en/us/td/docs/switches/lan/catalyst6500/ios/15-2SY/config_guide/sup2T/15_2_sy_swcg_2T.pdf) there is a feature called 'ipv4 router guard' which does exactly what we're looking for:
'When configured, the Router Guard feature makes the specified port a host port only. The port is prevented from becoming a router port, even if a multicast router control packets are received. In addition, any control packets normally received from multicast routers, such as IGMP queries and PIM joins, will also be discarded by this filter.'
Afaik, PIM authentication isn't supported in current catalyst ios versions.
Using a normal port ACL is not an option in our case because of a management decision.
B) Is there any possibility to prevent (on a per-subnet basis) rogue sources from sending multicast streams to legal multicast-groups?
Maybe, can I configure a svi of a host subnet or a host port to drop any incoming multicast stream while still accepting IGMP and sending out legal multicast streams?
Using 'ip pim accept-register' command on the rp is not an option because we've tons of legal sources which would end in an very huge error-prone acl
Unfortunately, a normal ACL is not an option here, too.
Best Regards
Thorsten

We use two pim routers in each host subnet for redundancy, they elect the PIM DR.
Does pim passive mode work here?
(Config Guide: If the ip pim passive command is configured on an interface enabled for IP multicast, the router will operate this interface in PIM passive mode, which means that the router will not send PIM messages on the interface nor will it accept PIM messages from other routers across this interface. The router will instead consider that it is the only PIM router on the network and thus act as the DR and also as the DF for all bidir-PIM group ranges. IGMP operations are unaffected by this command. ... The redundant PIM stub router topology is not supported. The redundant topology exists when there is more than one PIM router forwarding multicast traffic to a single access domain. PIM messages are blocked, and the PIM asset and designated router election mechanisms are not supported on the PIM passive interfaces.)
ip pim neighbor-filter maybe would work to prevent rogue pim routers to connect to the legal pim routers but wouldn't rogue pim routers still be able to manipulate the layer2 switch to send all igmp traffic to them and not to the legal pim routers?

Configuring ssm multicast

hi,
we are getting ready to implement the nexus 7000 with otv are two sites. since multicast is required to support this configuration i am currently testing how to implement ssm multicast on our core network. i am having problems joining the ssm group. here is the output from the 6509 i am using:
hw-dc-vss-cs6509-1(config-if)#ip igmp join-group 232.1.1.1
Ignoring request to join group 232.1.1.1, SSM group without source specified
hw-dc-vss-cs6509-1(config-if)#ip igmp join-group 232.1.1.1 ?
<cr>
hw-dc-vss-cs6509-1(config-if)#ip igmp join-group 232.1.1.1
as you can see the source option is not available and i can't figure out why.
here is a copy of my running configure and show multicast show commands
sh runn
Building configuration...
Current configuration : 6830 bytes
! Last configuration change at 18:37:28 UTC Thu Dec 16 2010
upgrade fpd auto
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
service counters max age 5
hostname hw-dc-vss-cs6509-1
boot-start-marker
boot system flash sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXI3.bin
boot-end-marker
security passwords min-length 1
no logging console
enable secret 5 $1$dZ1J$6KkcatZ2tXk055vswN1Kb1
no aaa new-model
--More--                           ip subnet-zero
ip multicast-routing
mls netflow interface
mls cef error action reset
spanning-tree mode rapid-pvst
spanning-tree portfast edge default
spanning-tree portfast edge bpduguard default
spanning-tree extend system-id
spanning-tree pathcost method long
spanning-tree vlan 1,5,245,501-502 priority 16384
--More--                           spanning-tree vlan 1,5,245,501-502 forward-time 9
spanning-tree vlan 1,5,245,501-502 max-age 12
diagnostic bootup level minimal
redundancy
main-cpu
auto-sync running-config
mode sso
ip access-list standard ssm-groups
permit 232.0.0.0 0.255.255.255
permit 239.232.0.0 0.0.255.255
vlan internal allocation policy ascending
vlan access-log ratelimit 2000
interface Loopback1
ip address 10.255.255.1 255.255.255.255
interface GigabitEthernet3/1
description adcore-4503 2/1
--More--                            mtu 9216
ip address 159.233.253.106 255.255.255.252
ip pim sparse-mode
ip igmp version 3
interface GigabitEthernet3/2
description pwcore-6509 3/2
mtu 9216
ip address 159.233.253.110 255.255.255.252
ip pim sparse-mode
ip igmp version 3
interface GigabitEthernet3/3
description p101-4503 1/1
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,5,245,501,502
switchport mode trunk
mtu 9216
spanning-tree guard root
interface GigabitEthernet3/4
no ip address
--More--                           !
interface GigabitEthernet3/5
no ip address
interface GigabitEthernet3/6
no ip address
interface GigabitEthernet3/7
no ip address
interface GigabitEthernet3/8
no ip address
interface GigabitEthernet3/9
no ip address
interface GigabitEthernet3/10
no ip address
interface GigabitEthernet3/11
no ip address
interface GigabitEthernet3/12
--More--                            no ip address
interface GigabitEthernet3/13
no ip address
interface GigabitEthernet3/14
no ip address
interface GigabitEthernet3/15
no ip address
interface GigabitEthernet3/16
no ip address
interface GigabitEthernet3/17
no ip address
interface GigabitEthernet3/18
no ip address
interface GigabitEthernet3/19
no ip address
--More--                           interface GigabitEthernet3/20
no ip address
interface GigabitEthernet3/21
no ip address
interface GigabitEthernet3/22
no ip address
interface GigabitEthernet3/23
no ip address
interface GigabitEthernet3/24
no ip address
interface GigabitEthernet5/1
no ip address
shutdown
interface GigabitEthernet5/2
no ip address
shutdown
--More--                           interface GigabitEthernet8/1
switchport
switchport access vlan 5
switchport mode access
interface GigabitEthernet8/2
switchport
switchport access vlan 245
switchport mode access
interface GigabitEthernet8/3
no ip address
shutdown
interface GigabitEthernet8/4
no ip address
shutdown
interface GigabitEthernet8/5
no ip address
shutdown
interface GigabitEthernet8/6
--More--                            no ip address
shutdown
interface GigabitEthernet8/7
no ip address
shutdown
interface GigabitEthernet8/8
no ip address
shutdown
interface GigabitEthernet8/9
no ip address
shutdown
interface GigabitEthernet8/10
no ip address
shutdown
interface GigabitEthernet8/11
no ip address
shutdown
--More--                           interface GigabitEthernet8/12
no ip address
shutdown
interface GigabitEthernet8/13
no ip address
shutdown
interface GigabitEthernet8/14
no ip address
shutdown
interface GigabitEthernet8/15
no ip address
shutdown
interface GigabitEthernet8/16
no ip address
shutdown
interface GigabitEthernet8/17
no ip address
shutdown
--More--                           !
interface GigabitEthernet8/18
no ip address
shutdown
interface GigabitEthernet8/19
no ip address
shutdown
interface GigabitEthernet8/20
no ip address
shutdown
interface GigabitEthernet8/21
no ip address
shutdown
interface GigabitEthernet8/22
no ip address
shutdown
interface GigabitEthernet8/23
no ip address
--More--                            shutdown
interface GigabitEthernet8/24
no ip address
shutdown
interface GigabitEthernet8/25
no ip address
shutdown
interface GigabitEthernet8/26
no ip address
shutdown
interface GigabitEthernet8/27
no ip address
shutdown
interface GigabitEthernet8/28
no ip address
shutdown
interface GigabitEthernet8/29
--More--                            no ip address
shutdown
interface GigabitEthernet8/30
no ip address
shutdown
interface GigabitEthernet8/31
no ip address
shutdown
interface GigabitEthernet8/32
no ip address
shutdown
interface GigabitEthernet8/33
no ip address
shutdown
interface GigabitEthernet8/34
no ip address
shutdown
--More--                           interface GigabitEthernet8/35
no ip address
shutdown
interface GigabitEthernet8/36
no ip address
shutdown
interface GigabitEthernet8/37
no ip address
shutdown
interface GigabitEthernet8/38
no ip address
shutdown
interface GigabitEthernet8/39
no ip address
shutdown
interface GigabitEthernet8/40
no ip address
shutdown
--More--                           !
interface GigabitEthernet8/41
no ip address
shutdown
interface GigabitEthernet8/42
no ip address
shutdown
interface GigabitEthernet8/43
no ip address
shutdown
interface GigabitEthernet8/44
no ip address
shutdown
interface GigabitEthernet8/45
no ip address
shutdown
interface GigabitEthernet8/46
no ip address
--More--                            shutdown
interface GigabitEthernet8/47
no ip address
shutdown
interface GigabitEthernet8/48
no ip address
shutdown
interface Vlan1
no ip address
shutdown
interface Vlan5
mtu 9216
ip address 159.233.5.1 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
ip pim sparse-mode
ip igmp join-group 239.1.1.1
--More--                            ip igmp version 3
arp timeout 200
interface Vlan245
mtu 9216
ip address 159.233.245.1 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
ip pim sparse-mode
ip igmp join-group 239.1.1.1
ip igmp version 3
arp timeout 200
interface Vlan501
mtu 9216
ip address 159.233.62.1 255.255.255.224
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
arp timeout 200
--More--                           !
interface Vlan502
mtu 9216
ip address 159.233.1.1 255.255.255.240
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
arp timeout 200
router eigrp 241
network 159.233.0.0
no auto-summary
redistribute static
ip classless
no ip http server
no ip http secure-server
ip pim rp-address 10.255.255.1
ip pim ssm default
--More--                           !
control-plane
dial-peer cor custom
line con 0
line vty 0 4
password f1v3c3nt2
login
line vty 5 15
password f1v3c3nt2
login
end
hw-dc-vss-cs6509-1#
sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.1.1.1), 00:20:20/00:02:55, RP 10.255.255.1, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
    Vlan5, Forward/Sparse, 00:19:14/00:02:55
(*, 239.255.255.250), 00:26:33/00:02:35, RP 10.255.255.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null
(159.233.245.100, 232.1.1.1), 00:06:48/00:02:55, flags: sPT
Incoming interface: Vlan245, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list: Null
(*, 224.0.1.40), 02:25:53/00:02:33, RP 10.255.255.1, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
    GigabitEthernet3/1, Forward/Sparse, 02:25:53/00:02:30
hw-dc-vss-cs6509-1#sj   h ip igmp gr
hw-dc-vss-cs6509-1#sh ip igmp groups
IGMP Connected Group Membership
Group Address    Interface                Uptime    Expires   Last Reporter   Group Accounted
239.1.1.1        Vlan5                    00:19:22 00:02:48 159.233.5.1
239.1.1.1        Vlan245                  00:20:14 00:02:25 159.233.245.1
239.255.255.250 Vlan245                  00:26:41 00:02:28 159.233.245.100
224.0.1.40       Vlan245                  01:30:34 00:02:25 159.233.245.105
224.0.1.40       GigabitEthernet3/1       1w1d      00:02:22 159.233.253.105
hw-dc-vss-cs6509-1#
any help would be greatly appreciated. thank you
i did some more digging and found the answer to my question, have to use the following command instead of the join-group command
Ip igmp static-group

I'm assuming you mean WebLogic SSM. If you set it up using organizational structure, you should see a new org in /entitlementsadministration with a number of applications bound to the SSM you declared.

DLSw+ Eth. Redundancy

Can you give me an example of a 'Multicast MAC Address' other than 9999.9999.9999?
I'm not exactly sure how to determine Multicast
MAC Addresses.
Thank You.

A layer 2 multicast MAC address in Ethernet 802.3 format means that bit 0 (the least significant bit) of the first octet is set on to indicate a multicast frame. A layer 2 multicast MAC address in Token Ring 802.5 format means that the most significant bit of the first octet is on. So long as you use a layer 2 multicast MAC address for the dlsw transparent redundancy-enable configuration command DLSw+ ER will work fine. MAC address 9999.9999.9999 is normally used since the MAC address would be same in both cannonical and non-connonical format (ie., bitswapped).

What is Multicasting?

Grid Version: 11.2
OS : AIX 6.1
I come across articles on RAC on AIX where the term Multicasting is frequently referenced. (For eg: thread like below)
NICs for Private Interconnect redundancy
When I googled it , i found articles like below which hasn't got anything to do with RAC networking at all
http://en.wikipedia.org/wiki/Multicast
Any idea what Multicasting is and how it is related to RAC?

Hi,
IP multicast is a technique for one-to-many communication over an IP infrastructure in a network. It scales to a larger receiver population by not requiring prior knowledge of who or how many receivers there are. Multicast uses network infrastructure efficiently by requiring the source to send a packet only once, even if it needs to be delivered to a large number of receivers. The nodes in the network take care of replicating the packet to reach multiple receivers only when necessary.
The most common transport layer protocol to use multicast addressing is User Datagram Protocol (UDP). By its nature, UDP is not reliable—messages may be lost or delivered out of order. Reliable multicast protocols such as Pragmatic General Multicast (PGM) have been developed to add loss detection and retransmission on top of IP multicast.
The multicast addresses are in the range 224.0.0.0 through 239.255.255.255. The range of addresses between 224.0.0.0 and 224.0.0.255, inclusive, is reserved for the use of routing protocols and other low-level topology discovery or maintenance protocols, such as gateway discovery and group membership reporting. Multicast routers should not forward
any multicast datagram with destination addresses in this range, regardless of its TTL.
http://www.iana.org/assignments/multicast-addresses/multicast-addresses.xml
Oracle Grid Infrastructure 11.2.0.2 introduces a new feature called "Redundant Interconnect Usage", which provides an Oracle internal mechanism to make use of physically redundant network interfaces for the Oracle (private) interconnect.
As part of this new feature, multicast based communication on the private interconnect is utilized to establish communication with peers in the cluster on each startup of the stack on a node.
Once the connection with the peers in the cluster has been established, the communication is switched back to unicast. Per default, the 230.0.1.0 address (port 42424) on the private interconnect network is used for multicasting. Another IP can be enabled using the patch mentioned below, if it is determined that using the 230.0.1.0 IP causes the multicast communication to fail. Multicasting on either of these IPs and the respective port must, however, be enabled and functioning across the network and on each node meant to be part of the cluster. If multicasting is not enabled as required, nodes will fail to join the cluster with the symptoms discussed.
Regards,
Levi Pereira
Edited by: Levi Pereira on May 31, 2012 2:20 PM

NICs for Private Interconnect redundancy

DB/Grid version : 11.2.0.2
Platform : AIX 6.1
We are going to install a 2-node RAC on AIX (that thing which is almost good as Solaris )
Our primary private interconnect is
### Primary Private Interconnect
169.21.204.1      scnuprd186-privt1.mvtrs.net scnuprd186-privt1
169.21.204.4      scnuprd187-privt1.mvtrs.net scnuprd187-privt1For Cluster inteconnect's redundancy , Unix team has attached an extra NIC for each node with an extra Gigabit-ethernet switch for these NICs.
###Redundant Private Interconnect attached to the server
169.21.204.2      scnuprd186-privt2.mvtrs.net scnuprd186-privt2 # Node1's newly attached redundant NIC
169.21.204.5      scnuprd187-privt2.mvtrs.net scnuprd187-privt2 # Node2's newly attached redundant NICExample borrowed from citizen2's post
Apparently I have 2 ways to implement cluster inteconnect's redundancy
Option1. NIC bonding at OS level
Option2. Let grid software do it
Question1. Which is better : Option 1 or 2 ?
Question2.
Regarding Option2.
From googling and OTN , i gather that , during grid installation you just provide 169.21.204.0 for cluster inteconnect and grid will identify the redundant NIC and switch. And if something goes wrong with the Primary Interconnect setup (shown above) , grid will automatically re-route interconnect traffic using the redundant NIC setup. Is this correct ?
Question 3.
My colleague tells me , for the redundant Switch (Gigabit) Unless I configure some Multicasting (AIX specific), I could get errors during installation. He doesn't clearly what it was ? Anyone faced Multicasting related issue on this ?

Hi,
My recommendation is to you use the AIX EtherChannel.
The EtherCannel of AIX is much more powerfull and stable compared with HAIP.
See how setup AIX EtherChannel on 10 Gigabit Ethernet interfaces
http://levipereira.wordpress.com/2011/01/26/setting-up-ibm-power-systems-10-gigabit-ethernet-ports-and-aix-6-1-etherchannel-for-oracle-rac-private-interconnectivity/
If you choose use HAIP I recommend you read this note, and find all notes about bugs of HAIP on AIX.
11gR2 Grid Infrastructure Redundant Interconnect and ora.cluster_interconnect.haip [ID 1210883.1]
ASM Crashes as HAIP Does not Failover When Two or More Private Network Fails [ID 1323995.1]
About Multicasting read it:
Grid Infrastructure 11.2.0.2 Installation or Upgrade may fail due to Multicasting Requirement [ID 1212703.1]
Regards,
Levi Pereira

Use of Bind , Connect with IP Multicasting

i'm trying to get a clear picture of the semantics of using bind, connect with IP multicasting.
ipv4 & ipv6 both are relavent.
it is my understanding -- you must multicast join on each interface you want to receive on.
in my view of the world, ideal semantics would provide :
bind-ing a socket to a specific local IP address, port - that has joined multiple IP multicast addresses
on multiple interfaces would allow multicasts to still be received - but would limit them to
interfaces which matched the bound IP address, and further if more than 1 interface supported
the same IP address, would allow receipt for all the joined interfaces that match the bound
IP address.
this does not appear to be the case; it appears that binding to a local IP address causes
multicast receipt to terminate. binding to 1 of the joined multicast address limits receipt
to the bound multicast address. the semantics seem confusing.
regarding connect :,
imagine multiple sources of a specific IP multicast address; your socket is doing receiving only,
no transmiting. it seems that ideally connect would allow you to limit the receipt of IP multicast
to the source that you connect to; i imagine connecting to the foreign IP address,
not the IP multicast address being transmitted. if semantically i could connect to the IP multicast address
i would still be receiving from all the sources - so no filtering benefit.
my understanding is you can connect to a IP multicast address; but this seems redundant to bind with
the only advandage that you can use send instead of sendto. and further if multiple sources are
transmitting the same IP multicast address you dont get filtering
when i tried using multiple sources transmitting 2048 different IP multicast address, with a receiver
who had multicast joined the same 2048 IP multicast address -- as soon as connect to 1 of the
sources ( foreign IP address) of the IP multicasts i stop receving packets all together. i had hoped
to limit the receipt of the multicasts to just that single source.

Generally, you would use bind variables by changing statements that are written like this
select * from emp where empno=6678 and ename='Jones'
so that they're written like
select * from emp where empno=? and ename=?
How you then bind these question marks to the particular values you want depends on the API you're using (ADO? OLE DB directly?, etc). If you have a support contract, there are plenty of examples for any API on metalink.oracle.com
Justin

Support Redundant NIC cards in a HP server

Hi
I would like to connect a HP server with two NIC cards (for redundancy) to two CISCO 2970 switches.
From the HP site they configured Channel Bonding
[root@sm36s_donald root]# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:14:38:EE:6C:6F
inet addr:172.23.160.36 Bcast:172.23.160.63 Mask:255.255.255.192
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:563837 errors:0 dropped:0 overruns:0 frame:0
TX packets:110645 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:49833329 (47.5 Mb) TX bytes:17943723 (17.1 Mb)
eth0 Link encap:Ethernet HWaddr 00:14:38:EE:6C:6F
inet addr:172.23.160.36 Bcast:172.23.160.63 Mask:255.255.255.192
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:563837 errors:0 dropped:0 overruns:0 frame:0
TX packets:110645 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:49833329 (47.5 Mb) TX bytes:17943723 (17.1 Mb)
Interrupt:25
eth1 Link encap:Ethernet HWaddr 00:14:38:EE:6C:6F
inet addr:172.23.160.36 Bcast:172.23.160.63 Mask:255.255.255.192
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:26
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8239071 errors:0 dropped:0 overruns:0 frame:0
TX packets:8239071 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:670754425 (639.6 Mb) TX bytes:670754425 (639.6 Mb)
What I have to configure from the Cisco switches site in order to avoid ARP problems?
Thank you for your support
Stelios

Stelios,
We have had issues when trying to load balance between the NICs. when in active/active, the virtual MAC reflects in both the connected switch ports, and the packets tend to loop between the ports. There will be a lot of Spanning Tree TCNs generated, which can shoot up the CPU. We had a 4507R with SUP IV, which got loaded to 70% when doing load balancing. when we made it active/standby on the NIC, the CPU came down to 1 %...
so just be careful on this. best way of doing it is active/standby
hope this helps.. all the best.. rate replies if found useful..
Raj

Multicast and processing

Hi all;
I have two 6500 running as When I issue "sh ip Vl15 200.155.16.10 Null Vl27 200.155.16.98 Null Vl95 200.155.16.85 Null Vl169 200.155.16.66 Null Vl120 200.155.16.226 Null Vl131 200.155.16.242 Null Vl75 200.155.16.178 Null Vl58 200.155.18.130 Null Vl17 200.155.18.242 Null Vl160 200.150.150.203 Null Vl8 200.155.18.2 Null Vl26 200.155.18.66 Null Vl86 200.155.18.82 Null Vl116 200.155.29.109 Null Vl122 200.155.29.114 Null Vl98 200.155.29.74 Null Vl115 200.155.29.194 Null Vl124 200.155.29.162 Null Vl49 200.155.29.130 Null Vl135 200.150.146.119 Null Vl16 200.155.30.130 Null Vl79 200.155.31.82 Null Vl164 200.155.31.122 Null Vl135 200.150.146.40 Null Vl91 200.155.31.2 Null Vl94 200.155.30.226 Null Vl29 200.155.31.18 Null Vl20 200.155.31.66 Null Vl110 200.155.25.82 Null I have the even and odds Thanks redundancy. They run HSRP and there are several vlans. I upgraded them with SUP2 recently and everything seems to be normal, but some things are a little bit weird.
cache flow" on both, I see a lot of multicast traffic from HSRP. Is it normal ??
224.0.0.2 11 07C1 07C1 55
224.0.0.2 11 07C1 07C1 60
224.0.0.2 11 07C1 07C1 42
224.0.0.2 11 07C1 07C1 53
224.0.0.2 11 07C1 07C1 58
224.0.0.2 11 07C1 07C1 60
224.0.0.2 11 07C1 07C1 56
224.0.0.2 11 07C1 07C1 54
224.0.0.2 11 07C1 07C1 59
10.254.224.132 11 9BFA 00A1 5
224.0.0.2 11 07C1 07C1 59
224.0.0.2 11 07C1 07C1 54
224.0.0.2 11 07C1 07C1 57
224.0.0.2 11 07C1 07C1 54
224.0.0.2 11 07C1 07C1 54
224.0.0.2 11 07C1 07C1 55
224.0.0.2 11 07C1 07C1 60
224.0.0.2 11 07C1 07C1 61
224.0.0.2 11 07C1 07C1 60
200.150.146.127 11 0089 0089 3
224.0.0.2 11 07C1 07C1 53
224.0.0.2 11 07C1 07C1 52
224.0.0.2 11 07C1 07C1 60
200.150.146.127 11 008A 008A 4
224.0.0.2 11 07C1 07C1 52
224.0.0.2 11 07C1 07C1 575
224.0.0.2 11 07C1 07C1 61
224.0.0.2 11 07C1 07C1 63
224.0.0.2 11 07C1 07C1 60
vlans balanced between the two cat's, but the process cpu from one is about 40%, while the other is about 10%. Can anyone help me to troubleshoot this ??

The traffic observed is not hsrp but cgmp.
http://www.cisco.com/en/US/tech/tk828/technologies_white_paper09186a00800a3e2b.shtml
Regards,
Leo

IPSec for Redundant DMVPN with VRF

Hi.
I have been labbing up a solution using DMVPN and VRF, similar to that described in the blog post here. It works very well, however when I try to extend the concept to a redundant hub, it breaks with IPSec. If I remove the tunnel protection, it works fine.
Does anyone have any ideas about providing IPSec protection to multiple DMVPN tunnels for VRFs to a redundant Hub?
Thanks.
Client config (no IPSec):
interface Tunnel10
ip vrf forwarding Staff
ip address 10.254.254.23 255.255.255.0
no ip redirects
ip mtu 1416
ip nhrp authentication MFS
ip nhrp map multicast 172.16.1.1
ip nhrp map 10.254.254.1 172.16.1.1
ip nhrp map 10.254.254.3 172.16.1.3
ip nhrp map multicast 172.16.1.3
ip nhrp network-id 10
ip nhrp holdtime 600
ip nhrp nhs 10.254.254.1
ip nhrp nhs 10.254.254.3
ip tcp adjust-mss 1360
tunnel source FastEthernet0/0
tunnel mode gre multipoint
tunnel key 10
interface Tunnel20
ip vrf forwarding Clients
ip address 10.254.253.23 255.255.255.0
no ip redirects
ip mtu 1416
ip nhrp authentication MFSC
ip nhrp map 10.254.253.1 172.16.1.1
ip nhrp map multicast 172.16.1.1
ip nhrp map multicast 172.16.1.3
ip nhrp map 10.254.253.3 172.16.1.3
ip nhrp network-id 20
ip nhrp holdtime 600
ip nhrp nhs 10.254.253.1
ip nhrp nhs 10.254.253.3
ip tcp adjust-mss 1360
tunnel source FastEthernet0/0
tunnel mode gre multipoint
tunnel key 20
Hub 1:
interface Tunnel10
ip vrf forwarding Staff
ip address 10.254.254.1 255.255.255.0
no ip redirects
ip mtu 1416
ip nhrp authentication MFS
ip nhrp map multicast dynamic
ip nhrp network-id 10
ip nhrp holdtime 360
ip tcp adjust-mss 1360
tunnel source FastEthernet0/0
tunnel mode gre multipoint
tunnel key 10
interface Tunnel20
ip vrf forwarding Clients
ip address 10.254.253.1 255.255.255.0
no ip redirects
ip mtu 1416
ip nhrp authentication MFSC
ip nhrp map multicast dynamic
ip nhrp network-id 20
ip nhrp holdtime 360
ip tcp adjust-mss 1360
tunnel source FastEthernet0/0
tunnel mode gre multipoint
tunnel key 20
Hub 2:
interface Tunnel10
ip vrf forwarding Staff
ip address 10.254.254.3 255.255.255.0
no ip redirects
ip mtu 1416
ip nhrp authentication MFS
ip nhrp map multicast dynamic
ip nhrp network-id 10
ip nhrp holdtime 360
ip nhrp server-only
ip tcp adjust-mss 1360
tunnel source FastEthernet0/0
tunnel mode gre multipoint
tunnel key 10
interface Tunnel20
ip vrf forwarding Clients
ip address 10.254.253.3 255.255.255.0
no ip redirects
ip mtu 1416
ip nhrp authentication MFSC
ip nhrp map multicast dynamic
ip nhrp network-id 20
ip nhrp holdtime 360
ip tcp adjust-mss 1360
tunnel source FastEthernet0/0 tunnel mode gre multipoint
tunnel key 20

Under the Hub you have to add
HUB1
interface Tunnel10
ip nhrp map 10.254.254.1
ip nhrp map multicast < ip add of FastEthernet0/0 for HUB2>
HUB2
interface Tunnel10
ip nhrp map 10.254.254.3
ip nhrp map multicast < ip add of FastEthernet0/0 for HUB1>
The same thing for the other tunnel interfaces

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

I am using Windows 8.1 i have an External Hard Disk and one drive is now inaccessible due to sudden power failure few days ago. Now it shows "Data error (Cyclic redundancy check)". I want all my important files and Pics. How ?

Hi,
I am using Windows 8.1
I have an External Hard Disk i have partitioned it to 4 parts.
One drive is now inaccessible due to sudden power failure while listening Music from that drive few days ago.
Now it shows "Data error (Cyclic redundancy check)".
I tried all the procedures provided here like
chkdsk /f, diskpart, rescan etc
but no result :( (i mean all processes failed. They could not detect the drive).
Please help me to get those data, pictures and project files.
thank you

Then why aren't you posting this in the Windows 8 forums found @
http://social.technet.microsoft.com/Forums/windows/en-US/home?category=w8itpro
This is a Windows 7 forum for discussion about Windows 7.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Data error (cyclic redundancy check) when installing windows xp..

hi guys.. i'm new here.. just switched to macdom a few days ago but unfortunately, i have been having problems trying to install windows xp with sp 2 on my system using boot camp. everytime i install it, i get to the setup screen ("39 minutes till setup rah rah rah", "windows xp is awesome because it has this cool interface etc... rah rah rah") and then the error of doom comes out -_-
the error given is;
an eror has been encountered that prevents setup from continuing
one of the components that windows needs to continue setup could not be installed
data error (cyclic redundancy check)
if you are installing from a cd, there might be a problem with the disc; try cleaning the disc or using another disc
if you are installing from the network, it is possible that not all of the files were copied correctly to your disk drive. run the disk checking utility on your installation drive from the recovery console and start setup again
press ok to view the setup log file
i have tried numerous times without fail and it is getting to my head.. gah.. if someone could help me out, it would be massive and i would sell my soul to you! (kidding).. thanks for reading!
p/s: my setup is;
Macbook
2.1ghz
1gb ram
120gb hard disk
dvd/cd-rw combo drive
the basic setup pretty much.. again.. any help would be greatly appreciated. thank you so much guys!

I guess there is a problem with your XP CD, probably scratched or did not burn successfully. Have you tried it with another installation cd?

Redundent cotrllers multicasting

Similar Messages

Maybe you are looking for