46NETBUILDER SOFTWARE VERSION 11.1 RELEASE NOTES
parameter settings. The practical limit may be lower and depends on the traffic load, CPU, and memory usage by other services.
Table 14 DLSw Circuit Maximums with CONNectionUsage Parameter Settings
| Maximum Number of DLSw Circuits | ||
System | Low | Medium | High |
|
|
|
|
OfficeConnect and SuperStack II | 190 | 390 | 790 |
NETBuilder bridge/routers |
|
|
|
Boundary router peripheral node* | n/a | n/a | 790† |
NETBuilder II bridge/router |
|
|
|
DPE modules | 390 | 790 | 7990 |
|
|
|
|
*The CONNectionUsage parameter is set to High by the Boundary Router Peripheral node software; it cannot be changes.
†The IBM Boundary Router peripheral node uses two LLC2 circuits to support one LLC2 end system. Therefore, the maximum number of LLC2 end systems supported by an IBM Boundary Router peripheral node is 395.
Number of TCP Connections
3Com LLC2 tunneling uses one TCP connection for each LLC2 session. DLSw scales to large networks better than LLC2 tunneling because it multiplexes all LLC2 sessions over one TCP connection per tunnel. Each Telnet session also uses one TCP connection. Table 15 shows the maximum number of TCP connections possible with the different CONNectionUsage parameter settings. The practical limit may be lower and depends on the traffic load, CPU, and memory usage by other services.
Table 15 TCP Circuit Maximums with CONNectionUsage Parameter Settings
| Maximum Number of TCP Circuits | ||
System | Low | Medium | High |
|
|
|
|
OfficeConnect and SuperStack II | 32 | 256 | 512 |
NETBuilder bridge/routers |
|
|
|
Boundary router peripheral node* | n/a | n/a | 790 |
NETBuilder II bridge/router |
|
|
|
DPE module | 32 | 512 | 2048 |
*The CONNectionUsage parameter is set to High by the Boundary Router peripheral node software; it cannot be changed.
| The maximum number of FradMap entries that may be defined for each Frame |
Processor/Frame Relay | Relay port is 50. |
Access for LLC2 Traffic |
|
History Compression Not | A port using Async PPP (AT dial) cannot be configured for history compression. The |
Allowed With Async PPP | user interface will not prevent you from configuring the port for history com- |
| pression, however, if history compression is selected the path will not come up. |
HPR and ISR | High Performance Routing (HPR) is enabled by default. Therefore, if you are |
Configurations | configuring APPN Intermediate Session Routing (ISR), you must disable HPR on |
| both the PortDef and the AdjLinkSta parameters by setting HPR = No. |
IBM Boundary Routing | In an IBM Boundary Routing topology that uses disaster recovery through PPP |
Topology Disaster | (when two paths are mapped to one port), a disruption to existing SNA and |
Recovery |
|
