Communication Server for AIX Tuning and Performance Tips

About this document
牋牋Related documentation
Communications buffers (mbufs)
Setting maxmbuf
SNA DLC link parameters
LAN-based DLC characteristics
Memory
Paging space
File transfer applications

About this document

This document contains tips for network tuning in an SNA environment. It applies to AIX Versions 4.x.

Communications buffers (mbufs)

The mbuf pool is a shared resource that must be managed at the system level. Communications Server for AIX uses mbufs to send and receive data across the network, but it is just one of the subsystems that uses mbufs. Communications Server for AIX mbuf resource utilization can affect the performance of other subsystems such as TCP/IP, NFS, and AFS.

There are two ways to determine how much memory should be be made available as communications memory buffers (mbufs). This amount of memory is defined using the maximum number, or maxmbuf.

"4096 X number of Comm Adapters"
This method counts the total number of communications adapters in the system (whether being used for SNA or not), and then multiplies this number by 4096. The result is used as the setting for maxmbuf.
For example, if there are two token ring adapters that are being used for SNA and two Ethernet adapters that are being used for TCP/IP, the calculation would be 4 adapters multiplied by 4096, or 16384. 16384 would be the number used for maxmbuf.
"25% of RAM"
SNA generally requires more memory for buffers than other applications. With the larger memory sizes that have become available, SNA will usually operate efficiently if the maxmbuf parameter is set to a number equal to 25% of real memory. In most circumstances, any number larger than 64MB (65536) will not yield any appreciable benefit.
For example, if there is 128Mb of real memory on the machine, set the maxmbuf parameter to 32Mb (32768). If there is 512Mb of memory, set maxmbuf to the recommended maximum of 64Mb (65536).
If SNA_SRF errors are being logged in the system error log, this parameter should be checked.

Setting maxmbuf

To check the current setting of this parameter, enter the following:

           lsattr -El sys0 |grep maxmbuf

To change this parameter, enter the following:

           chdev -l sys0 -a maxmbuf=new_value

For example, to set maxmbuf to its maximum value of 64MB, enter the following:

           chdev -l sys0 -a maxmbuf=65536

NOTE: On AIX 4.2 and AIX 4.3, the default for maxmbuf is 0. This value is known to cause problems with SNA. Please set maxmbuf to any value other than 0.

SNA DLC link parameters

Certain SNA DLC profile parameters significantly impact throughput of file transfer applications. For token ring and Ethernet, use the following guidelines.

The Transmit_Window_Count parameter on any node A should always be greater than the Receive_Window_Count on any node B for any two nodes that are connected to each other. This is true even if a node is not an IBM eServer pSeries or RS/6000.
Using large values for Transmit_Window_Count and Receive_Window_Count does not enhance throughput. Setting the Transmit_Window_Count to 16 and Receive_Window_Count to a lesser value should be sufficient for peak throughput.

For an SDLC connection, the Receive_Window_Count does not exist. With SDLC, the primary_repoll_time_out parm setting must allow enough time for the largest frame to travel to and from the secondary station. Otherwise, unnecessary polls will flood the link, eventually bringing it down.

If the link speed is X bits per second and the largest frame is Y bits, then the primary_repoll_time-out should be larger than 2(Y/X).

LAN-based DLC characteristics

The Token Ring, Ethernet, and FDDI Data Link Controls contain a parameter called the Depth of receive queue. This queue is logically between the device handler and the data link control and holds asynchronous event notifications such as the receipt of data packets. This queue defaults to a depth of 32 entries and can be changed by the operator if log entries indicate that the device handler is overrunning the DLC due to heavy system activity. This attribute should be changed in small increments because it directly affects system storage availability.

To change this value, use the following fastpath command.

           smit devices

Then follow these steps:

Select Communication.
Select the type of communication from the list displayed (for example, TOKEN RING ADAPTER).
Select Services.
Select Data Link Control.
Select Change/Show Data Link Control.
Change the parameter value.

Memory

A rough estimate of the amount of memory required to run a certain number of sessions is that one additional megabyte of memory will support about seven additional sessions. The exact number will depend on traffic.

Paging space

A paging space is a dedicated area of fixed disk storage used to temporarily store information from real memory. When activity increases and the amount of available free memory decreases, "pages" of programs or data that have not been referenced recently are moved to fixed disk to allow real memory to be used for immediate requirements.

For systems with less than 512Mb of real memory, the value recommended for paging space is TWO TIMES the amount of real memory. For systems with 512Mb of real memory or greater, the recommended value for paging space is an amount at least EQUAL to the amount of real memory.

To display the amount of memory, enter

           lsattr -El sys0 | grep realmem

To display total paging space and the approximate amount used, enter

           lsps -s

It is advisable to keep the paging space used below 75% to ensure that SNA resources will be available. If these resources must be "paged" out of real memory, it is important that enough space is available to prevent SNA from experiencing errors that could result in total failure of SNA communications. If the percent used is over 75%, additional paging space should be added.

File transfer applications

When using file transfer applications, the SNA LU 6.2 Mode Profile can be configured to maximize throughput. Use the following guidelines.

Larger request/response unit (RU) sizes generally correspond to higher throughput. The following formula for RU sizes will provide optimum throughput in most cases.

RU = (I-Field size) - (9 bytes)
It is also very important to try to match the RU sizes on both sides of communicating nodes, regardless of the platform. An RU size larger than one calculated from the formula will result in segmentation of the data and cause a slowdown in data transfer.
NOTE: To find the I-field size, use the following command while the link station is active.
```
             sna -d l -o long |grep -p linkstation_name
```
Look for the field labeled Max frame data (BTU) size. This I-field size is controlled from within the SNA DLC profile in the SNA configuration. The I-field size should be system defined or matched exactly with the other node configuration.
Generally, increased throughput is also related to larger SEND and RECEIVE session pacing window sizes. Try setting the SEND pacing and RECEIVE pacing window sizes to the maximum value of 63.
When writing file transfer applications, use large buffers in the TP code. A 16K buffer size will speed up the transfer.

[ Doc Ref: 9064778089346 Publish Date: Jan. 03, 2001 4FAX Ref: 9777 ]