Hi
We use the static ARP/mac address trick for our NLB load sharing:
arp 172.25.14.30 03bf.ac19.0e1e ARPA
arp 172.25.14.35 03bf.ac19.0e23 ARPA
arp 172.25.14.69 03bf.ac19.0e45 ARPA
mac address-table static 03bf.ac19.0e1e vlan 846 interface TenGigabitEthernet2/3
mac address-table static
Hi,
On Sun, Dec 16, 2012 at 02:32:27PM -0800, Randy wrote:
It also may be worthwhile for your $Employer to consider some form of
*service-contract* with Cisco. CCO has a wealth of information (for your own
edification). You will need a valid-contract to have access to said info!
Google-Foo
On 12/16/2012 04:49 PM, Robert Williams wrote:
Hi,
I'm sensing a lot of frustration / anger / hatred for NLB, having
never really used it myself I'll just back away from that quietly :)
Hehe...
Unfortunately the test is valid because the situation actually arose
when a Windows NLB cluster
Hi,
Thanks for that, just to clarify a couple of details regarding the 'flow' of
traffic in this instance, as I think my attempt to simplify for the purpose of
identifying the issue has had the opposite effect :)
So, the connectivity is as follows:
[--- Internet --]
\/
On 17/12/2012 8:57 PM, Gert Doering wrote:
Hi,
On Sun, Dec 16, 2012 at 02:32:27PM -0800, Randy wrote:
It also may be worthwhile for your $Employer to consider some form of
*service-contract* with Cisco. CCO has a wealth of information (for your own
edification). You will need a
Hi,
On Mon, Dec 17, 2012 at 10:58:12AM +, Robert Williams wrote:
(PS. For the NLB fans, you'll be pleased to know the cluster is now going for
good I'm told)
I know I'm going to get stoned for that, but hey, it's Monday anyway...
I actually *like* NLB. It's a brilliant way to twist
On 17/12/12 11:38, Gert Doering wrote:
Hi,
On Mon, Dec 17, 2012 at 10:58:12AM +, Robert Williams wrote:
(PS. For the NLB fans, you'll be pleased to know the cluster is now going for
good I'm told)
I know I'm going to get stoned for that, but hey, it's Monday anyway...
I actually *like*
Hi,
On Mon, Dec 17, 2012 at 01:16:30PM +, Phil Mayers wrote:
I have a suspicion that re-using the IPv4/IPv6 multicast MAC OUI was
part of the problem - that is special-cased in a lot of kit,
That's actually the brilliant thing about it :-) - and yes, kit that
does not handle MAC-level
On 17/12/12 13:32, Gert Doering wrote:
Hi,
On Mon, Dec 17, 2012 at 01:16:30PM +, Phil Mayers wrote:
I have a suspicion that re-using the IPv4/IPv6 multicast MAC OUI was
part of the problem - that is special-cased in a lot of kit,
That's actually the brilliant thing about it :-) - and
Hi,
On Mon, Dec 17, 2012 at 01:34:21PM +, Phil Mayers wrote:
Wait for IPv6 ND flood attacks... (and then nobody will be able to point
a finger to MS to tell them hey, all your fault!)
No need to wait. We've had several (accidental, but nevertheless).
Suffice to say it had a...
On 17/12/12 13:48, Gert Doering wrote:
Hi,
On Mon, Dec 17, 2012 at 01:34:21PM +, Phil Mayers wrote:
Wait for IPv6 ND flood attacks... (and then nobody will be able to point
a finger to MS to tell them hey, all your fault!)
No need to wait. We've had several (accidental, but
On Dec 17, 2012, at 5:58 PM, Robert Williams wrote:
The 'attack' traffic entered via the Non-Cisco router, from the internet. Was
delivered to the LAN switch while the NLB was unreachable. Thus the switch
flooded to all ports, which included the 6500.
NLB is a bag of hurt, IMHO.
What DDoS
I built up a PIM connection to a new multicast
provider and I see this provider is sending the same mcast flow with some
different sources:
--
xx#sh ip mroute 224.0.1.114 count
IP Multicast Statistics
858 routes using 542426 bytes of
memory
705 groups, 0.21 average sources
On a 6500 we use for lab/testing/dev if we create a new vlan with an IP address
that is the same as another VLAN on the device the box will admin shut the new
VLAN.
I understand it doing this if the existing VLAN is UP and maybe in certain
circumstances if the existing VLAN is down but is
But as you see it seems that the application is the same (same group and same
number of pkts received)...
At least for three sources...
Tks
sent with android
David Prall d...@dcptech.com ha scritto:
This is why it is called Any Source Multicast (ASM). A number of
applications use the same
On Mon, 2012-12-17 at 12:34 -0500, Drew Weaver wrote:
On a 6500 we use for lab/testing/dev if we create a new vlan with an
IP address that is the same as another VLAN on the device the box will
admin shut the new VLAN.
Our 6500s have alway put newly created SVIs in the shutdown state. We
need
On 17/12/12 17:52, Riccardo S wrote:
But as you see it seems that the application is the same (same group and same
number of pkts received)...
At least for three sources...
I don't understand what your question is.
Multicast lets 1 host send to the same group (even source-specific
multicast
This is why it is called Any Source Multicast (ASM). A number of
applications use the same group for discussions. Cisco's old IP/TV
distributed over one group, then had a second group for feedback. So as you
typed in a question it was sent to everyone.
David
--
http://dcp.dcptech.com
Could the other 3 be keepalives. Don't know what the application is. Is your
receiver sending to the group as well? Could be the primary address is
advertising everything via an election process. The others are sending
keepalives, if the primary goes away, then the next is elected based on some
Ugh. Sent this directly to Tim and not the list.
My only updates are that I have a 3550 prepped to go out there when we can deal
with the downtime and that the packet loss continues during the PPS peaks. I'm
still confused as to why I see the discards on the 7206 side and not the 3560
side
20 matches
Mail list logo
