Motorola 49901 Software Release Notes - Page 48

Caution, Input Data Rate for SoTCP Sessions

Page 48 highlights

Known Software Limitations Part No. T0001-42, Rev C October, 2002 Page 48 of 103 X.25 Host X.25 Access Port with maximum access port speed SoTCP WAN or Ethernet Link SoTCP Figure 12. Input Data Rate for SoTCP Sessions The maximum access port speed that can be supported by SOTCP varies with the number of SoTCP sessions in place. These tables show the recommended maximum limit on access port speed for a given number of SoTCP sessions: With intermediate WAN link at 2 Mbps Access Port Speed 1024 Kpbs 768 Kpbs 128 Kpbs 128 Kpbs Maximum number of 500 250 100 50 SoTCP sessions 80 Kpbs 10 57.6 Kpbs 1 With intermediate Ethernet link Access Port Speed 1024 Kpbs 512 Kpbs 384 Kpbs Maximum number of 500 250 100 SoTCP sessions 256 Kpbs 50 128 Kpbs 10 128 Kpbs 1 Caution Exceeding these data transfer rates may cause SoTCP sessions to disconnect. Based on X.25 access port data packet size set to 128 bytes; window sizes set to K=7 and W=15. When TCP (SOTCP) is heavily loaded, the TCP session will be dropped. This is due to congestion issues when running traffic over Ethernet. TCP is flooding the Ethernet with bidirectional traffic and the CPU usage hits 100%. This delays the consumption of received frames and causes the number of collisions to rise. Basic Rate Interface (BRI) Boot - Vanguard 6400 Series, Vanguard 320 A BRI interface does not recover with the first BRI interface boot following a node boot. A second BRI interface boot clears and recovers the interface. (DRFaa18340) Workaround: Boot the interface twice. Using IP Multicast on a Vanguard 6560 On a Vanguard 6560, multicast traffic running on more than two Ethernet ports, generates Cyclic Redundancy Check (CRC) -errored frames on the Ethernet port configured with the highest interface number, excluding port 4. For example, if port 4 is interface 3, port 7 is interface 2, and port 13 is interface 1, the errored frames are generated by port 7. (DRFaa14892) Workaround: Try to limit multicast traffic to a maximum of two Ethernet ports.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103

Part No. T0001-42, Rev C
October, 2002
Known Software Limitations
Page 48 of 103
Figure 12. Input Data Rate for SoTCP Sessions
The maximum access port speed that can be supported by SOTCP varies with the
number of SoTCP sessions in place. These tables show the recommended maximum
limit on access port speed for a given number of SoTCP sessions:
Caution
Exceeding these data transfer rates may cause SoTCP sessions to disconnect. Based
on X.25 access port data packet size set to 128 bytes; window sizes set to K=7 and
W=15.
When TCP (SOTCP) is heavily loaded, the TCP session will be dropped. This is due
to congestion issues when running traffic over Ethernet. TCP is flooding the Ethernet
with bidirectional traffic and the CPU usage hits 100%. This delays the consumption
of received frames and causes the number of collisions to rise.
Basic Rate Interface (BRI) Boot - Vanguard 6400 Series, Vanguard 320
A BRI interface does not recover with the first BRI interface boot following a node
boot. A second BRI interface boot clears and recovers the interface. (DRFaa18340)
Workaround:
Boot the interface twice.
Using IP Multicast on a Vanguard 6560
On a Vanguard 6560, multicast traffic running on more than two Ethernet ports,
generates Cyclic Redundancy Check (CRC) -errored frames on the Ethernet port
configured with the highest interface number, excluding port 4. For example, if port
4 is interface 3, port 7 is interface 2, and port 13 is interface 1, the errored frames are
generated by port 7. (DRFaa14892)
Workaround:
Try to limit multicast traffic to a maximum of two Ethernet ports.
X.25 Host
X.25 Access Port
with maximum
access port speed
SoTCP
SoTCP
WAN
or Ethernet
Link
With intermediate WAN link at 2 Mbps
Access Port Speed
1024 Kpbs
768 Kpbs
128 Kpbs
128 Kpbs
80 Kpbs
57.6 Kpbs
Maximum number of
SoTCP sessions
500
250
100
50
10
1
With intermediate Ethernet link
Access Port Speed
1024 Kpbs
512 Kpbs
384 Kpbs
256 Kpbs
128 Kpbs
128 Kpbs
Maximum number of
SoTCP sessions
500
250
100
50
10
1