Installation manual

Part No. T0001-43, Rev B
February, 2003
Known Software Limitations Page 43 of 99
Descriptions 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.
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.
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.
Alarms when Doing Warm or Cold Boot of Release 5.5 - Vanguard 6455
The alarm message "DBG-Error-Module:L3 Function:L3_Go Error:L3_Get_NLCB
failed" may display when you boot the node during the handling of the T314_timer
expiry. These alarms do not impact the node's functionality. (DRCaa22131)
Workaround: At present, there is no workaround.
T1 N. American ISDN B-Channels appear IDLE - Vanguard 6400 Series
When you look at the detailed PRI statistics with the D-channel connected, all of the
associated B-channels are shown to be in an IDLE state, even if some of the channels
are not configured in the ISDN interface. (DRCaa22080)
Workaround: At present, there is no workaround.
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)