Sun Network Switch
 

PLA-Support>Sun Systems>SAND>Network>SN-SND: Sun Network Ethernet Switches
 

HTTP retries

HTTP retries by the N1000/2000 to the server should hide the problem from clients in the case of GET transfers and small PUT transfers. The problem remains for large PUT transfers.

Action
Set the ServiceGroup retryCount to 2 (default=1).

Syntax

vSwitch-name loadBalance serviceGroup name text retryCount integer

Arguments

retryCount integer

Optional: The number of tries the system should make to connect to a different real service (server) within the same service group before failover to the sorry server.

Valid values are from 0 to 2; the default setting is "1".

Links

Modify service group

PooledConnections

For a "pooled" service, which N1000/2000 calls "TCP multiplexing", there is a software feature to discard idle connections that are getting stale. However, that mechanism is probably governed by longRxTimer.

Some customers don't use "TCP multiplexing" anyway because they want to propagate the client IP addresses to the servers.

Action

Check if you can enable "usePooledConnections"?

Syntax

vSwitch-name loadBalance requestPolicy name text usePooledConnections enumeration

Arguments

usePooledConnections enumeration

Optional: When enabled, a pool of connections to Real Services will be maintained so that a new TCP session will not need to be established for each incoming client connection.

The default setting is "disabled".

Valid values: enabled, disabled

Links

Modify a request policy

RxTimers

The general "solution" is to set the Virtual (VS) and Real Services (RS) shortRxTimer and longRxTimer no larger than the application (e.g. Apache/Tomcat) time-out for idle connections.

Action

Tune the Virtual Services and Real Services shortRxTimers and longRxTimer to a few seconds less then the equivalent setting on the application side. For example this would be the "KeepAliveTimeout" (default=15 seconds) setting in Apache. Use the same shortRxTimer and longRxTimer values for related Real and Virtual Services.

Syntax

vSwitch-name loadBalance realService advanced name text shortRxTimer enumeration longRxTimer enumeration
vSwitch-name loadBalance virtualService advanced name text shortRxTimer enumeration longRxTimer enumeration

Arguments

shortRxTimer enumeration

Optional: The receive timer short timeout value, which defines how long you are willing to wait to receive the first data packet from a real service after a session has been established. If the timer expires, the switch terminates the session.

The default setting for a RS is "16_seconds", for a VS it is "32_seconds".

Valid values:

   * disable : Timers are disabled.
* 125_msec : 125 milliseconds.
* 250_msec : 250 milliseconds.
* 500_msec : 500 milliseconds.
* 1_second : 1 second.
* 2_seconds : 2 seconds.
* 4_seconds : 4 seconds.
* 8_seconds : 8 seconds.
* 16_seconds : 16 seconds.
* 32_seconds : 32 seconds.
* 64_seconds : 64 seconds.
* 128_seconds : 128 seconds.
* 256_seconds : 256 seconds.
* 512_seconds : 512 seconds.
* 1024_seconds : 1024 seconds.
* 2048_seconds : 2048 seconds.

longRxTimer enumeration

Optional: The receive timer long timeout value, which defines how long you are willing to wait to receive subsequent data from the real service (RS) or client (VS) after the initial packet. If the timer expires, the switch terminates the session.

The default setting for RS+VS is "64_seconds".

Valid values:

   * disable : Timers are disabled.
* 125_msec : 125 milliseconds.
* 250_msec : 250 milliseconds.
* 500_msec : 500 milliseconds.
* 1_second : 1 second.
* 2_seconds : 2 seconds.
* 4_seconds : 4 seconds.
* 8_seconds : 8 seconds.
* 16_seconds : 16 seconds.
* 32_seconds : 32 seconds.
* 64_seconds : 64 seconds.
* 128_seconds : 128 seconds.
* 256_seconds : 256 seconds.
* 512_seconds : 512 seconds.
* 1024_seconds : 1024 seconds.
* 2048_seconds : 2048 seconds.

Links

Modify a real service advanced configuration
Modify virtual service advanced configuration

This solution has no attachment