Motorola 49901 Software Release Notes - Page 47

Node cold boot or Node Warm Boot Logs a Fatal Error Reporting

Get Motorola 49901 - Vanguard 340 Router PDF manuals and user guides
UPC - 786523499018
View all Motorola 49901 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 47 highlights

Known Software Limitations Part No. T0001-42, Rev C October, 2002 Page 47 of 103 Node crashes when Bridge is configured on VPN over LAN When you have TB Bridge traffic over the LAN Tunnel (Tunnel over LAN Link), the traffic from TB-1 is transported to TB-2 and from TB-2 to TB-1 over Tunnel. Refer to Figure 11 below: (TB-1) (TB-2) PC Node----ETH-------- BN -L-A--N--T-u-n-n-e-l -(E--T-H---1-) BN ETH -----------PC Node (BL-2) 100 (BL-1) (BL-1) 200 (BL-2) Figure 11. TB Bridge Traffic over A LAN Tunnel The tunnel carrier ETH-1 does not have Bridge enabled. If the user (by mistake) enables the Bridge Link (BL-1) corresponding to ETH-1 which is the tunnel physical link, the node starts to repeatedly crash until the Bridge Link (BL-1) is disabled. (INDaa01627) Workaround: In the practical scenario, you do not have to enable the Bridge link corresponding to the ETH physical link of Tunnel. To avoid the node crashing, disable the Bridge Link (BL-1) corresponding to the ETH-1 (which is the Tunnel carrier). This workaround does not impact the other functionality's. All the functionality (including Bridge Traffic over LAN Tunnel) will work as usual. Node cold boot or Node Warm Boot Logs a Fatal Error Reporting Software Failure Logged - Vanguard 320 The BRI voice card can cause the node to crash if the voice port used for BRI is previously configured as another voice port type. (DRCaa22044) Workaround: Null the port before installing the BRI voice card. AS/400 Communications Server Alarm ID Error - Vanguard 64xx, 65xx If you configure an incorrect LU ID into the 5494 Conversion Station, the AS/400 software accepts the ID value, autocreates a workstation with the incorrect LU ID, and the AS/400 Communications Server Alarm reports: "WORKSTATION UP, LU ID: x", although the intended workstation might not be active. However, the 5494 Conversion Station statistics correctly report that the workstation is in the "INITIALIZING" state. (DRCaa20861) Workaround: Be sure to configure the correct LU ID into the 5494 Conversion Station. Input Data Rate for SoTCP Sessions - Vanguard 6560 If the input data rate exceeds a certain limit, SoTCP sessions can disconnect because of loss of IP datagrams in the underlying network and excessive TCP retransmissions. The report "SOTCP-n -TCP session timed out with x.y.z.w" is generated under such conditions. (INDaa01195) The input data rate is controlled by the port speed setting on the X.25 access port as shown in the figure:

  • 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 47 of 103
Node crashes when Bridge is configured on VPN over LAN
When you have TB Bridge traffic over the LAN Tunnel (Tunnel over LAN Link), the
traffic from TB-1 is transported to TB-2 and from TB-2 to TB-1 over Tunnel. Refer
to Figure 11 below:
Figure 11. TB Bridge Traffic over A LAN Tunnel
The tunnel carrier ETH-1 does not have Bridge enabled. If the user (by mistake)
enables the Bridge Link (BL-1) corresponding to ETH-1 which is the tunnel physical
link, the node starts to repeatedly crash until the Bridge Link (BL-1) is disabled.
(INDaa01627)
Workaround:
In the practical scenario, you do not have to enable the Bridge link
corresponding to the ETH physical link of Tunnel. To avoid the node crashing,
disable the Bridge Link (BL-1) corresponding to the ETH-1 (which is the Tunnel
carrier). This workaround does not impact the other functionality's. All the
functionality (including Bridge Traffic over LAN Tunnel) will work as usual.
Node cold boot or Node Warm Boot Logs a Fatal Error Reporting
Software Failure Logged - Vanguard 320
The BRI voice card can cause the node to crash if the voice port used for BRI is
previously configured as another voice port type. (DRCaa22044)
Workaround:
Null the port before installing the BRI voice card.
AS/400 Communications Server Alarm ID Error - Vanguard 64xx, 65xx
If you configure an incorrect LU ID into the 5494 Conversion Station, the AS/400
software accepts the ID value, autocreates a workstation with the incorrect LU ID,
and the AS/400 Communications Server Alarm reports: “WORKSTATION UP, LU
ID: x”, although the intended workstation might not be active. However, the 5494
Conversion Station statistics correctly report that the workstation is in the
“INITIALIZING” state. (DRCaa20861)
Workaround:
Be sure to configure the correct LU ID into the 5494 Conversion
Station.
Input Data Rate for SoTCP Sessions - Vanguard 6560
If the input data rate exceeds a certain limit, SoTCP sessions can disconnect because
of loss of IP datagrams in the underlying network and excessive TCP
retransmissions. The report “SOTCP-n -TCP session timed out with x.y.z.w” is
generated under such conditions. (INDaa01195)
The input data rate is controlled by the port speed setting on the X.25 access port as
shown in the figure:
PC Node----ETH-------- BN ------------------ BN ----------- ETH -----------PC Node
(TB-1)
(TB-2)
(BL-2)
(BL-1)
(BL-1)
(BL-2)
100
200
LAN Tunnel (ETH-1)