Expand Configuration and Management Manual (H06.21+, J06.10+)

Configuring Expand-Over-X.25 Lines
Expand Configuration and Management Manual — 529522-013
10 - 13
Profile Modifiers
Profile Modifiers
This subsection lists the recommended modifiers for Expand-over-X.25 line-handler
processes and describes the modifiers provided for configuring special features. It also
describes default values and value ranges for all the modifiers contained in the
PEXQSNAM profile.
Recommended Modifiers
Recommended modifiers are modifiers that should be used to obtain optimum
performance and efficiency. This modifier is recommended for Expand-over-X.25 line-
handler processes:
L4TIMEOUTn
Default: 2000 (20 seconds)
Units: 0.01 seconds
Range: 500 through 32,767 (5.00 seconds through 5.27.67 minutes)
This modifier specifies the time interval, in one-hundredth of a second increments, that
the Expand-over-X.25 line-handler process will wait for a response to an end-to-end
(Layer 4) request before retrying. L4TIMEOUT should be the same for every Expand
line-handler process in the network.
If a message is not acknowledged within the L4TIMEOUT period, an enquiry (ENQ) will
be initiated. Because retransmissions of an X.25 network can degrade response time,
cause network link congestion, or cause excessive packet charges, you should set
L4TIMEOUT to a value in excess of the maximum anticipated response time on a
loaded link.
Modifiers for Special Features
These modifiers are provided in the PEXQSNAM profile to enable you to configure
special features:
•
PATHBLOCKBYTES modifier for the multipacket frame feature
•
PATHPACKETBYTES modifier for the variable packet size feature
•
L4CONGCTRL_ON modifier for the congestion control feature
•
SUPERPATH_ON modifier for the Expand multi-CPU feature
•
L4CWNDCLAMP modifier for the configuration of the congestion control transmit
window feature
Note. A different profile is provided for Expand-over-X.25 lines that are part of a multi-line
path; this profile is described in Section
13, Configuring Multi-Line Paths.
Note. The Expand End-to-End protocol is explained in
Path Function of the Expand
Subsystem on page 17-13.