XCON: Recalculating Routing does not Remove Previously Deleted RoutesID: Q176518
|
When you recalculate routing using the Microsoft Exchange Administrator program, the routing table may not reflect changes made to the routing in other Microsoft Exchange Sites.
In large topologies, these routes are not being removed quickly enough. Therefore, modifications have been made to the routing calculation to strip these routes more quickly.
Within a Site, one Microsoft Exchange Server is responsible for recalculating the routing information for that Site. This Exchange Server can be determined by clicking the General tab of the Site Addressing object you opened above and checking the Routing Calculation Server value. This Exchange Server must be running version 4.0.996.42 of the Microsoft Exchange Message Transfer Agent (MTA) or above.
Microsoft has confirmed this to be a problem in Microsoft Exchange Server,
version 4.0. This problem has been corrected in the latest U.S. Service
Pack for Microsoft Exchange Server version 4.0. For information on
obtaining the Service Pack, query on the following word in the Microsoft
Knowledge Base (without the spaces):
S E R V P A C K
For example, an address space is deleted on a connector in Site 1 but
the routing table in Site 2 still shows the deleted route. This deleted
route still shows in the routing table even after a number of successful
directory replication cycle have been completed amongst all Sites, even
though the route no longer shows in Site 2's replica of Site 1.
The current routing table can be examined following these steps:
Additional query words: GWART EMS_RID SP5
Keywords : kbbug4.00 XADM
Version : 4.0
Platform : winnt
Issue type : kbbug
Last Reviewed: March 14, 1999