Installation manual

Part No. T0001-43, Rev B
February, 2003
Software Improvements Page 36 of 99
SNABSC HPAD and TPAD Entries - Vanguard 6455, 7300 Series
The Destination Control Unit Address and Destination Device Address parameters in
the SNABSC entry in HPAD must match one of the following set of parameters of
BSC3270 TPAD device table, for the device it is connecting to: (DRCaa22909)
1) BSC Control Unit Address and BSC Device Address.
2) Destination Control Unit Address and Destination Device Address.
When placing the call from HPAD, the Destination Control Unit Address and
Destination Device Address must match the BSC3270 device table parameters: BSC
Control Unit Address and BSC Device Address. When placing the call from TPAD,
the Destination Control Unit Address and Destination Device Address must also
match the BSC3270 device table parameters: Destination Control Unit Address and
Destination Device Address.
This is fixed.
Single DLCI Multiplexing SNA/IP/IPX Causes Node Crash - All Products
RFC1490 Single DLCI Multiplexing and De-Multiplexing SNA/IP/IPX will cause
the node to crash. If you configure the string FRISNA-xSy as either a source or
destination in the PVC Setup Table and then boot the node, the node will not come
up. The node will repeatedly crash. Multiplexing IP and IPX in the same DLCI
works fine. (DRFaa16306)
This is fixed.
Vanguard 7300 Series BGP Initial Configuration
The initial configuration of BGP requires a warm boot. (DRFaa19411)
This is fixed.
Vanguard 7300, 6455 ISDN D-Channel Statistics Reports
Statistics are incorrect for a Vanguard 7300 or 6455 node configured for ISDN PRI
(5ESS, Network). When you connect the T1 PBX cable to the Interface, and the
RED Alarm clears, the D-channel will go ACTIVE and all virtual ports report IDLE.
If you do not place a call within one minute the D-Channel reports that it is DOWN
and the voice ports report OUT OF SERVICE. If you place a call it will go through
This is fixed.
Vanguard 320, SoTCP Calls not Connecting
SoTCP calls (data or voice) are not connecting if the SoTCP "TCP Keep Alive
Timer" is disabled. If enabled, a SoTCP boot does not initialize the timer. A warm
boot is required. (DRFaa19651)
This is fixed.