Header Only - DO NOT REMOVE - Extreme Networks

SLB EXOS


Userlevel 2
How its possible create a SLB (ldap) with EXOS(X8) like LSNAT on Enterasys ??

13 replies

Userlevel 6
Hi Luis, currently this feature is only supported on EOS for specific HW.

I don't see any roadmap for that in EXOS.
Userlevel 2
Henrique wrote:

Hi Luis, currently this feature is only supported on EOS for specific HW.

I don't see any roadmap for that in EXOS.

have other ways, like script for this?
Userlevel 6
Henrique wrote:

Hi Luis, currently this feature is only supported on EOS for specific HW.

I don't see any roadmap for that in EXOS.

Could you please describe what would you like to accomplish?
Userlevel 2
Henrique wrote:

Hi Luis, currently this feature is only supported on EOS for specific HW.

I don't see any roadmap for that in EXOS.

The service is ldap..tcp/389 . the customer have many servers with this service...
Userlevel 6
If you could change the SLB config on the servers to an NLB (Network Load Balancing) if using microsoft we could use an NLB kind of solution.
Userlevel 7
Depending on your topology, you can have a look at the Health Check Link Aggregation feature (p.271 of 16.1 User Guide). I never really used it, but that might help you.

Another approach could be via ACL. You can create a "sort of" SLB if the servers' IP can be masked correctly. Here's an example of such ACL (you would have several rules like that):

entry r11 {
if {
source-address 0.0.0.0 mask 0.0.0.7;
} then {
redirect-port-list 1:1;
}
}

entry r12 {
if {
source-address 0.0.0.1 mask 0.0.0.7;
} then {
redirect-port-list 1:2;
}
}[/code]
Userlevel 2
Grosjean, Stephane wrote:

Depending on your topology, you can have a look at the Health Check Link Aggregation feature (p.271 of 16.1 User Guide). I never really used it, but that might help you.

Another approach could be via ACL. You can create a "sort of" SLB if the servers' IP can be masked correctly. Here's an example of such ACL (you would have several rules like that):

entry r11 {
if {
source-address 0.0.0.0 mask 0.0.0.7;
} then {
redirect-port-list 1:1;
}
}

entry r12 {
if {
source-address 0.0.0.1 mask 0.0.0.7;
} then {
redirect-port-list 1:2;
}
}[/code]

On this acl the problem is if the server down...
Userlevel 7
Grosjean, Stephane wrote:

Depending on your topology, you can have a look at the Health Check Link Aggregation feature (p.271 of 16.1 User Guide). I never really used it, but that might help you.

Another approach could be via ACL. You can create a "sort of" SLB if the servers' IP can be masked correctly. Here's an example of such ACL (you would have several rules like that):

entry r11 {
if {
source-address 0.0.0.0 mask 0.0.0.7;
} then {
redirect-port-list 1:1;
}
}

entry r12 {
if {
source-address 0.0.0.1 mask 0.0.0.7;
} then {
redirect-port-list 1:2;
}
}[/code]

yes, that needs to be handled.
Another way to do it is to use a script/app with UPM that would check the availability of the servers on a regular basis and apply dynamic ACLs accordingly.
Grosjean, Stephane wrote:

Depending on your topology, you can have a look at the Health Check Link Aggregation feature (p.271 of 16.1 User Guide). I never really used it, but that might help you.

Another approach could be via ACL. You can create a "sort of" SLB if the servers' IP can be masked correctly. Here's an example of such ACL (you would have several rules like that):

entry r11 {
if {
source-address 0.0.0.0 mask 0.0.0.7;
} then {
redirect-port-list 1:1;
}
}

entry r12 {
if {
source-address 0.0.0.1 mask 0.0.0.7;
} then {
redirect-port-list 1:2;
}
}[/code]

Example?
Grosjean, Stephane wrote:

Depending on your topology, you can have a look at the Health Check Link Aggregation feature (p.271 of 16.1 User Guide). I never really used it, but that might help you.

Another approach could be via ACL. You can create a "sort of" SLB if the servers' IP can be masked correctly. Here's an example of such ACL (you would have several rules like that):

entry r11 {
if {
source-address 0.0.0.0 mask 0.0.0.7;
} then {
redirect-port-list 1:1;
}
}

entry r12 {
if {
source-address 0.0.0.1 mask 0.0.0.7;
} then {
redirect-port-list 1:2;
}
}[/code]

Or a write up would be great. The more gtac knowledge articles the better! 
Userlevel 2
Grosjean, Stephane wrote:

Depending on your topology, you can have a look at the Health Check Link Aggregation feature (p.271 of 16.1 User Guide). I never really used it, but that might help you.

Another approach could be via ACL. You can create a "sort of" SLB if the servers' IP can be masked correctly. Here's an example of such ACL (you would have several rules like that):

entry r11 {
if {
source-address 0.0.0.0 mask 0.0.0.7;
} then {
redirect-port-list 1:1;
}
}

entry r12 {
if {
source-address 0.0.0.1 mask 0.0.0.7;
} then {
redirect-port-list 1:2;
}
}[/code]

But with LSNAT i need only 1 IP, and all devices have the ip with authenticator, then the switch redirectly to devices according with algorithm chosen...
Userlevel 2
Grosjean, Stephane wrote:

Depending on your topology, you can have a look at the Health Check Link Aggregation feature (p.271 of 16.1 User Guide). I never really used it, but that might help you.

Another approach could be via ACL. You can create a "sort of" SLB if the servers' IP can be masked correctly. Here's an example of such ACL (you would have several rules like that):

entry r11 {
if {
source-address 0.0.0.0 mask 0.0.0.7;
} then {
redirect-port-list 1:1;
}
}

entry r12 {
if {
source-address 0.0.0.1 mask 0.0.0.7;
} then {
redirect-port-list 1:2;
}
}[/code]

there any example???
Userlevel 6
Grosjean, Stephane wrote:

Depending on your topology, you can have a look at the Health Check Link Aggregation feature (p.271 of 16.1 User Guide). I never really used it, but that might help you.

Another approach could be via ACL. You can create a "sort of" SLB if the servers' IP can be masked correctly. Here's an example of such ACL (you would have several rules like that):

entry r11 {
if {
source-address 0.0.0.0 mask 0.0.0.7;
} then {
redirect-port-list 1:1;
}
}

entry r12 {
if {
source-address 0.0.0.1 mask 0.0.0.7;
} then {
redirect-port-list 1:2;
}
}[/code]

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-Extreme-switches-to-handl...

Reply