Installation manual
Part No. T0249-01, Rev A
April, 2002
Software Improvements Page 20 of 55
Vanguard 6520, Vanguard 7300 Series Aggregation Table
An Aggregation Table entry overrides the RIP route when the table entry matches the
Static route or the RIP route for the IP address and the mask. (INDaa01153)
This is fixed.
Internal IP Addresses are Deleted in the Routing Table - All Products
If there is an un-numbered Grouped LCON with a single member and if the LCON is
disabled and then enabled again, the routing table entry for the Internal IP address of
the node is removed. (INDaa01189)
This is fixed.
H.323 Call Not Cleared after Node Boot - All Products
When an H.323 call is established directly between two nodes and the originating
node is booted, the H.323 call is not cleared. This does not occur if a gatekeeper is
used. (DRCaa19949)
This is fixed.
Expiry of H.323 Time to Live Timer Causes Vanguard Gateway
Unregistration - All Products
At Release 5.4, the Vanguard gateway currently supports H.323 standard Version
one, which does not provide a time to live update message. The Netspeak
Gatekeeper expects a time to live update messages from gateways connected in its
zone. Because the Vanguard gateway does not send time to live update messages, the
Netspeak Gatekeeper unregisters the Vanguard gateway each time the gatekeeper’s
time to live timer expires. The Vanguard gateway attempts to re-register with the
gatekeepers. (DRCaa20703)
This is fixed.
Large SDLC-to-LLC2 (SLAC) Calling Addresses - All Products
For incoming X.25 calls over Frame Relay SVC, Vanguard network services updates
the X.25 table with calling address and the station. It always interprets the calling
address as XX...X**. That is, the last two digits are assumed to be sub-address and
the rest as node address. For calls which use large subaddresses, such as those made
by SDLC SLAC stations, this interpretation would lead to a wrong node address. For
example, a calling address of 2000822, where 0822 is the subaddress, is interpreted
as 20008**.
Therefore, to dynamically route outbound calls over existing FR SVC stations only
calls to 20008 node address is allowed. In such cases, network services would look
for a new FR SVC station to connect to the remote. (DRCaa20328)
This is fixed.
Route Selection Table - Syntax Error Message - All Products
After configuring and saving the Route Selection Table’s Destination parameter with
this entry, FRI-n (where n is the port number), this warning message appears:
The following Destination(s) have a SYNTAX ERROR or they do not match a
known PORT TYPE or NODE RESOURCE. (DRFaa11989) (DRCaa20268)
The configured Destination parameter, however, is saved to CMEM.
This is fixed.