Installation manual

Part No. T0249-01, Rev A
April, 2002
Known Software Limitations Page 29 of 55
Descriptions 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 8 below:
Figure 8. 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.
Encrypted (SAM) Tunnel
Encrypted (SAM) Tunnel over WAN/LAN with (RTP+UDP/UDP)+IP Header
compression is not working for certain size UPD-IP packets where IP packet length
is greater than 46 (Version 5.5 and 5.6). Compression works for IP packets where the
IP packet length is less than 46. (INDaa01629)
Workaround: At present, there is no workaround.
IPX WAN Node Boot - All Products
When you add an interface with IPX WAN enabled, you must boot the node.
(INDaa00790)
Workaround: At present, there is no workaround.
DTR Connection Type and BSC3270 Port - All Products
DTR connection type does not work as configured in the BSC3270 port record.
(DRFaa07855)
Workaround: At present, there is no workaround.
Backup Link and Alternate Destination - All Products
If the backup link is configured as an alternative destination in the Route Selection
Table as well as configured in the Switched Service Table, the backup link is
activated under CALL/EITHER activation mode, when a call arrives for this
destination, even if the monitor port is active. In FAIL/FAIL_ALL modes, the
backup link is not activated if the Monitored Port is active. (INDaa01138)
Workaround: The backup link should not be configured in the route selection entry.
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)