Motorola 49901 Software Release Notes - Page 59

Known Software Limitations Part No. T0001-42, Rev C October, 2002 Page 59 of 103 Vanguard 6435/6455 T1E1 ATM Port Configuration If you are running T1 ATM on a Vanguard 6400 Series product, the AAM port may not function after upgrading to release 6.0.R00A or greater (when certain parameters are not at default). You must have local CTP access to the node if this is the case. Do not upgrade to release 6.0.R00A if you have no other way to access the CTP than through ATM. The ATM connection could be down after booting in Release 6.0.R00A (DRFaa19362) Workaround: At present, there is no workaround. You must have local CTP access if the following parameters are not configured as follows (prior to the upgrade): Parameter *Port Type: *Maximum VPI Range: *Maximum VCI Range: F5 Link Assurance Timer: F5 Link Assurance Count: CC Activate/Deactivate Timer: CC Activate/Deactivate Count: Default AAM 3 127 3 3 5 3 If these parameters are not set at default, you must reconfigure all AAM ports after release 6.0.R00A has been booted on-line and then reboot the node again. All AAM station configurations are correctly transferred in the upgrade and will function once the AAM port is reconfigured properly. BGP Global TCP Segment Size and Peer TCP Segment Size All Vanguards The Global TCP segment size is overriding peer TCP segment size if any one peer is configured for zero. (DRFaa19391) Workaround: Ensure that all peer segment sizes are equal. Vanguard 7300 Series BGP Initial Configuration The initial configuration of BGP requires a warm boot. (DRFaa19411) Workaround: Set global TCP segment size at a high value and configure remote BGP peer to control over TCP segment size. Vanguard 6400 Default Configuration The Vanguard 6400 Series default configuration is different from the Vanguard Application Ware Frame Relay Interface Documentation. (DRFaa18862)