Routing Groups were logical groupings of Exchange
servers determined by the administrator. In Exchange Server 2007, because the transport core functionality
has changed as noted in Chapter 7 , message routing has also been changed. Rather than
using the Routing Engine found in Exchange 2000/2003, the Categorizer (see ??? The Transport
Server Architecture ??? in Chapter 7 ) now has a routing stage that determines the ultimate destination
for a message, selects a route to that destination, and selects and resolves the next hop for that
destination to a server(s) and IP addresses.
Link state was one of the components of routing in Exchange 2000/2003 many Exchange
administrators were happy to see go away. Although link state had some benefits, managing it in
some cases required a significant overhead. In some large Exchange Server environments, the
orgInfo packet, which holds the routing information for the organization, became quite large
and caused significant network bandwidth utilization during data transfer among servers.
Also, transient network and Active Directory replication problems caused connector oscillations.
Rather than use a logical groups of servers, Exchange Server 2007 takes advantage of Active
Directory site topology in routing messages within and outside an Exchange organization.
Pages:
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429