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****
[email protected]****
** **
[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:* [email protected] [mailto:[email protected]] *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<[email protected]>****
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****
[email protected]****
****
[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:[email protected]]
*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]<[email protected]>
[email protected]<[email protected]>
[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:[email protected]]
*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****
[email protected]****
****
[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:[email protected]]
*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 [email protected] with
the body: unsubscribe enterasys [email protected] ****
- --To unsubscribe from enterasys, send email to [email protected] with
the body: unsubscribe enterasys [email protected] ****
- --To unsubscribe from enterasys, send email to [email protected] with
the body: unsubscribe enterasys [email protected] ****
- --To unsubscribe from enterasys, send email to [email protected] with
the body: unsubscribe enterasys [email protected] ****
** **
- --To unsubscribe from enterasys, send email to [email protected] with
the body: unsubscribe enterasys [email protected] ****
- --To unsubscribe from enterasys, send email to [email protected] with
the body: unsubscribe enterasys [email protected]