RE: [enterasys] AW: Still with NLB

[POVEDA SANCHEZ, WENCESLAO]

Hi Erick,

That's the config I made. I put an static ARP entry pointing to the virtual IP.

I agree with Hugo, about the publication of documents. Perhaps, the end 
costumer doesn't have all the knowledge about Enterasys devices (as a partner), 
but costumer knows the infrastructure of the enterprise and the global 
interaction between services better than anybody and usually, problems are not 
treated globally. That's why this info could be very usefull on first stage of 
an incident before scaling it.

Thanks.


Servicio de Informática   
Wenceslao Poveda Sánchez.
I. Técnico de Sistemas.
Unidad de SSII - Servicio de Informática.
Excma.Diputación Provincial de Alicante 
  wpov...@dip-alicante.es 
  965.98.89.00  Ext. 8416 


La información contenida en este correo electrónico es confidencial, incluyendo 
sus adjuntos, y va dirigida únicamente al receptor/es que aparece como 
destinatario. Si ha recibido este mensaje por error, por favor, notifíquenoslo 
inmediatamente y bórrelo de su sistema. 
Queda terminantemente prohibida a cualquier otra persona su revelación, copia, 
distribución o cualquier tipo de tratamiento.

The information contained in this email is confidential, including attachments, 
and is directed only to the receiver listed as the recipient. If you have 
received this message by mistake, please notify us immediately and delete it 
from your system.
It is strictly forbidden to any other person the disclosure, copying, 
distribution or any kind of treatment.


Antes de imprimir este mensaje, por favor, compruebe que es verdaderamente 
necesario. 
El Medio Ambiente es cosa de todos.

Before printing this message, please check that it is absolutely necessary.
The environment is everyone's business.


> -----Mensaje original-----
> De: Erik Auerswald [mailto:auersw...@fg-networking.de]
> Enviado el: lunes, 30 de abril de 2012 15:32
> Para: Enterasys Customer Mailing List
> Asunto: Re: [enterasys] AW: Still with NLB
> 
> Hi,
> 
> there are a couple of Knowledge Base articles regarding NLB, perhaps there
> you can find what info you need:
> 
> https://cp-enterasys.kb.net/display/4n/search.aspx?tab=search
> 
> KB Article 5708 looks like a good starting point:
> 
> https://cp-enterasys.kb.net/article.aspx?article=5708&p=1
> 
> I have once configured L3 access to an NLB cluster where the router interface
> was located on an N-Series. There a static ARP entry linking the virtual 
> cluster
> address to the multicast MAC was needed. I've never configured a B-Series (or
> equivalent) for this, thus I don't know if this works on a B5 as well.
> 
> Regards,
> Erik
> --
> Dipl.-Inform. Erik Auerswald           http://www.fg-networking.de/
> E:auersw...@fg-networking.de P:+49-631-4149988-0 M:+49-176-64228513
> 
> Gesellschaft für Fundamental Generic Networking mbH
> Geschäftsführung: Volker Bauer, Jörg Mayer
> Gerichtsstand: Amtsgericht Kaiserslautern - HRB: 3630
> 
> 
> On 04/30/2012 12:58 PM, Hugo Veiga wrote:
> > Hi Adam,
> >
> > That might be the truth if: the end costumer doesn't have the same
> > formation and technical experience (or even more) than the partner.
> >
> > Regards,
> > Hugo Veiga
> >
> >
> >
> >
> >
> >
> > 2012/4/30 Adam Rainer<rainer.a...@imtech.at>
> >
> >>   This document I have, did not solve an issue directly, it describes
> >> possible solutions depending on your infrastructure and
> >> requirements.****
> >>
> >> ** **
> >>
> >> Such documents are not very usefull for end customers this should be
> >> the part for your Enterasys Partner, you should report him your
> >> problems and he have to find a possible solution that may fit to your
> >> infrastructure and requirements not Enterasys. It's just like a
> >> workshop manual for a car. It does'nt help you to fix your issue in
> >> all possible cases, thats the same like this document. ****
> >>
> >> ** **
> >>
> >> It would NOT fix your problem. I only want to give you a hint that
> >> there exists a fix exist for a different infrastructure and you have
> >> to open a case at Enterasys' GTAC to solve your issue or to contact
> >> your Enterasys
> >> Partner.****
> >>
> >> ** **
> >>
> >> The Partners are there to have an overview whats on the market and
> >> whats are the possible issues with your infrastructure and your
> >> requirements.***
> >> *
> >>
> >> ** **
> >>
> >> ** **
> >>
> >> ** **
> >>
> >> Mit freundlichen Grüßen / Best regards****
> >>
> >> * *
> >>
> >> *Rainer ADAM*****
> >>
> >> *System Engineer*
> >>
> >> * *
> >>
> >> ** **
> >>
> >> Imtech ICT Austria GmbH****
> >>
> >> Guglgasse 15****
> >>
> >> Bauteil 3, 4. Stock****
> >>
> >> A-1110 Wien****
> >>
> >> ** **
> >>
> >> T: +43 51715 4830****
> >>
> >> F: +43 51715 99 4830****
> >>
> >> M: +43 664 851 4830****
> >>
> >> rainer.a...@imtech.at****
> >>
> >> ** **
> >>
> >> [image: Beschreibung: https://webmail.imtech.at/logos/imtech.jpg]
> >>
> >> *Imtech ICT Austria GmbH
> >> **Infrastructure Services*****
> >>
> >> ** **
> >>
> >> *www.imtech-ict.at*<http://www.imtech-ict.at/>* *****
> >>
> >> ** **
> >>
> >> *Von:* hve...@fcsaude.ubi.pt [mailto:hve...@fcsaude.ubi.pt] *Im
> >> Auftrag von *Hugo Veiga
> >> *Gesendet:* Montag, 30. April 2012 10:54
> >> *An:* Enterasys Customer Mailing List
> >> *Betreff:* Re: [enterasys] AW: Still with NLB****
> >>
> >> ** **
> >>
> >> @Enterasys:****
> >>
> >> ** **
> >>
> >> Can someone from Enterasys please explain why there are documents
> >> that aren't widely distributed to the people that really buy and use
> >> your
> >> equipments!!?****
> >>
> >> ** **
> >>
> >> Regards,****
> >>
> >> Hugo Veiga****
> >>
> >> ** **
> >>
> >> ** **
> >>
> >> 2012/4/27 Adam Rainer<rainer.a...@imtech.at>****
> >>
> >> Hi ****
> >>
> >>   ****
> >>
> >>   ****
> >>
> >> I am sorry, I have a document, yes, but I don't have the permission
> >> to distribute it AND this document is to fix "Microsoft NLB on
> >> N-Series".****
> >>
> >>   ****
> >>
> >> Please open a case at Enterasys and ask for a solution.****
> >>
> >>   ****
> >>
> >> ****
> >>
> >>   ****
> >>
> >>   ****
> >>
> >> Mit freundlichen Grüßen / Best regards****
> >>
> >> * *****
> >>
> >> *Rainer ADAM*****
> >>
> >> *System Engineer*****
> >>
> >> * *****
> >>
> >>   ****
> >>
> >> Imtech ICT Austria GmbH****
> >>
> >> Guglgasse 15****
> >>
> >> Bauteil 3, 4. Stock****
> >>
> >> A-1110 Wien****
> >>
> >>   ****
> >>
> >> T: +43 51715 4830****
> >>
> >> F: +43 51715 99 4830****
> >>
> >> M: +43 664 851 4830****
> >>
> >> rainer.a...@imtech.at****
> >>
> >>   ****
> >>
> >> [image: Beschreibung: https://webmail.imtech.at/logos/imtech.jpg]
> >>
> >> *Imtech ICT Austria GmbH
> >> **Infrastructure Services*****
> >>
> >>   ****
> >>
> >> *www.imtech-ict.at*<http://www.imtech-ict.at/>* *****
> >>
> >>   ****
> >>
> >> *Von:* POVEDA SANCHEZ, WENCESLAO [mailto:wpov...@dip-alicante.es]
> >> *Gesendet:* Freitag, 27. April 2012 11:33
> >> *An:* Enterasys Customer Mailing List
> >> *Betreff:* RE:[enterasys] Still with NLB****
> >>
> >>   ****
> >>
> >> Hi Adam,****
> >>
> >>   ****
> >>
> >> For the Microsoft NLB: The cluster NEVER talks with his virtual MAC
> >> address. *You should put in the cluster members in a seperate vlan
> >> and assign the virtual MAC address to this vlan*, but I am not sure
> >> if the B5 supports this. Our customers core switches are N-Serie's
> >> there you can configure this.****
> >>
> >>   ****
> >>
> >> Please could you explain this point, I mean, is there any article or
> >> document about it?****
> >>
> >>   ****
> >>
> >> Thanks****
> >>
> >>   ****
> >>
> >> [image: Descripción:
> >> http://www.ladipu.com/images/Imagenes_email/LogoDipu.png]****
> >>
> >> Servicio de Informática   ****
> >>
> >>   ****
> >>
> >> Wenceslao Poveda Sánchez.
> >> I. Técnico de Sistemas.
> >> Unidad de SSII - Servicio de Informática.
> >> Excma.Diputación Provincial de Alicante ****
> >>
> >> [image: Descripción:
> >> http://www.ladipu.com/images/Imagenes_email/icono-mail.jpg]<freus@dip
> >> -alicante.es> wpov...@dip-alicante.es<wpov...@dip-alicante.es>
> >> [image: Descripción:
> >> http://www.ladipu.com/images/Imagenes_email/icono-telefono.jpg]
> 965.98.89.00  Ext.
> >> 8416 ****
> >>
> >> [image: Descripción:
> >> http://www.ladipu.com/images/Imagenes_email/ISO_9001.jpg]****
> >>
> >> La información contenida en este correo electrónico es confidencial,
> >> incluyendo sus adjuntos, y va dirigida únicamente al receptor/es que
> >> aparece como destinatario. Si ha recibido este mensaje por error, por
> >> favor, notifíquenoslo inmediatamente y bórrelo de su sistema.
> >> Queda terminantemente prohibida a cualquier otra persona su
> >> revelación, copia, distribución o cualquier tipo de tratamiento.
> >>
> >> *The information contained in this email is confidential, including
> >> attachments, and is directed only to the receiver listed as the recipient.
> >> If you have received this message by mistake, please notify us
> >> immediately and delete it from your system.
> >> It is strictly forbidden to any other person the disclosure, copying,
> >> distribution or any kind of treatment.*****
> >>
> >>   ****
> >>
> >>   ****
> >>
> >> Antes de imprimir este mensaje, por favor, compruebe que es
> >> verdaderamente necesario.
> >> El Medio Ambiente es cosa de todos.
> >>
> >> *Before printing this message, please check that it is absolutely
> >> necessary.
> >> The environment is everyone's business.*****
> >>
> >>   ****
> >>
> >>   ****
> >>
> >> *De:* Adam Rainer [mailto:rainer.a...@imtech.at] *Enviado el:*
> >> viernes, 27 de abril de 2012 11:04
> >> *Para:* Enterasys Customer Mailing List
> >> *Asunto:* [enterasys] AW: Still with NLB****
> >>
> >>   ****
> >>
> >> Hi****
> >>
> >>   ****
> >>
> >> We had the same problem with one of our customers with his Microsoft
> NLB.
> >> ****
> >>
> >>   ****
> >>
> >> In which configuration does your NLB Cluster work? Unicast?
> >> Multicast?****
> >>
> >>   ****
> >>
> >> For the Microsoft NLB: The cluster NEVER talks with his virtual MAC
> >> address. You should put in the cluster members in a seperate vlan and
> >> assign the virtual MAC address to this vlan, but I am not sure if the
> >> B5 supports this. Our customers core switches are N-Serie's there you
> >> can configure this.****
> >>
> >>   ****
> >>
> >>   ****
> >>
> >>   ****
> >>
> >>   ****
> >>
> >> Mit freundlichen Grüßen / Best regards****
> >>
> >> * *****
> >>
> >> *Rainer ADAM*****
> >>
> >> *System Engineer*****
> >>
> >> * *****
> >>
> >>   ****
> >>
> >> Imtech ICT Austria GmbH****
> >>
> >> Guglgasse 15****
> >>
> >> Bauteil 3, 4. Stock****
> >>
> >> A-1110 Wien****
> >>
> >>   ****
> >>
> >> T: +43 51715 4830****
> >>
> >> F: +43 51715 99 4830****
> >>
> >> M: +43 664 851 4830****
> >>
> >> rainer.a...@imtech.at****
> >>
> >>   ****
> >>
> >> [image: Beschreibung: https://webmail.imtech.at/logos/imtech.jpg]
> >>
> >> *Imtech ICT Austria GmbH
> >> **Infrastructure Services*****
> >>
> >>   ****
> >>
> >> *www.imtech-ict.at*<http://www.imtech-ict.at/>* *****
> >>
> >>   ****
> >>
> >> *Von:* POVEDA SANCHEZ, WENCESLAO [mailto:wpov...@dip-alicante.es]
> >> *Gesendet:* Freitag, 27. April 2012 10:46
> >> *An:* Enterasys Customer Mailing List
> >> *Betreff:* [enterasys] Still with NLB****
> >>
> >>   ****
> >>
> >> Hi all,****
> >>
> >>   ****
> >>
> >> Sometime ago I made some questions about configuring a B5G stack to
> >> work against a NLB cluster from TMG, only switching (Thanks Sylvain,
> >> Markus and everyone who helps me).****
> >>
> >> Now I have to enable routing on that B5G so, of course, I have
> >> another
> >> problem.****
> >>
> >> I'm configuring static routes. If I put as gateway to a network the
> >> virtual ip (VIP) of the NLB latency grows incredibly, so performance
> >> is quite poor.****
> >>
> >> I'm forced to config as gateway the dedicated IP of one of the NLB
> >> nodes, disabling NLB on the other machine.****
> >>
> >> This is the routing config:****
> >>
> >>   ****
> >>
> >> !****
> >>
> >> ip route 10.1.0.0 255.255.0.0 192.168.7.3****
> >>
> >> !****
> >>
> >> interface vlan 20****
> >>
> >> ip address 192.168.7.10 255.255.255.0****
> >>
> >> no shutdown****
> >>
> >> interface vlan 200****
> >>
> >> ip address 192.168.249.254 255.255.255.0****
> >>
> >> no shutdown****
> >>
> >> !****
> >>
> >> arp 192.168.7.1 03BF.C0A8.0701****
> >>
> >> !****
> >>
> >>   ****
> >>
> >> On the switching side I have "set mac multicast" config pointing to
> >> ports where TMG servers are connected.****
> >>
> >>   ****
> >>
> >> Thanks****
> >>
> >>   ****
> >>
> >>   ****
> >>
> >>     - --To unsubscribe from enterasys, send email to lists...@unc.edu with
> >>     the body: unsubscribe enterasys rainer.a...@imtech.at ****
> >>
> >>
> >>     - --To unsubscribe from enterasys, send email to lists...@unc.edu with
> >>     the body: unsubscribe enterasys wpov...@dip-alicante.es ****
> >>
> >>
> >>     - --To unsubscribe from enterasys, send email to lists...@unc.edu with
> >>     the body: unsubscribe enterasys rainer.a...@imtech.at ****
> >>
> >>
> >>     - --To unsubscribe from enterasys, send email to lists...@unc.edu with
> >>     the body: unsubscribe enterasys hve...@ubi.pt ****
> >>
> >>   ** **
> >>
> >>     - --To unsubscribe from enterasys, send email to lists...@unc.edu with
> >>     the body: unsubscribe enterasys rainer.a...@imtech.at ****
> >>
> >>
> >>     - --To unsubscribe from enterasys, send email to lists...@unc.edu with
> >>     the body: unsubscribe enterasys hve...@ubi.pt
> 
> ---
> To unsubscribe from enterasys, send email to lists...@unc.edu with the body:
> unsubscribe enterasys wpov...@dip-alicante.es

---
To unsubscribe from enterasys, send email to lists...@unc.edu with the body: 
unsubscribe enterasys arch...@mail-archive.com