KCC does not generate all connections

Answered KCC does not generate all connections

  • Wednesday, May 09, 2012 10:11 AM
     
     

    Hi all,

    I've two hub sites and several spoke sites. Each spoke site is connected with the two hub sites. No direct connection exists between spoke sites. I've noticed that KCC generates connections within my spoke sites:

    sometimes it generates two connection (correct) one for each hub site

    sometimes it generated only one connection (non correct) only to a hub site (always the same)

    what have I to check?

All Replies

  • Wednesday, May 09, 2012 10:16 AM
     
     

    Hello,

    as long as you don't specify the replication yourself the KCC does the job itself and this shouldn't be changed if no specific reason exists. This is done automatically so don't care about as long as all DCs replicate with at least one other server.

    http://blogs.technet.com/b/markmoro/archive/2011/08/05/you-are-not-smarter-than-the-kcc.aspx


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

  • Wednesday, May 09, 2012 11:16 AM
    Moderator
     
     

    You need to check sites/subnets/sitelinks/Costings are configured properly. KCC evaluates the topology and accordingly generates the connection objects. Is there been network routing with all the sites and also is Bridge All Site Ling option is disabled(by default it is enabled). By default KCC runs after every 15 min to generate the CO's.

    Active Directory Sites and Services  http://technet.microsoft.com/en-us/library/cc730868.aspx

    Designing the Site Topology for Windows Server 2008 AD DS  http://technet.microsoft.com/en-us/library/cc772013(v=ws.10).aspx

    Resources for Active Directory Sites and Services  http://technet.microsoft.com/en-us/library/cc755294.aspx

    Managing Sites http://technet.microsoft.com/en-us/library/bb727051.aspx

    Just delete the manual created connection object and run repadmin /kcc * and see if it can generate the topology based on the AD sites and services configuration.


    Awinish Vishwakarma - MVP - Directory Services

    My Blog: awinish.wordpress.com

    Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

  • Wednesday, May 09, 2012 11:53 AM
    Moderator
     
     

    Actually the KCC doesn't generate the intersite connections, it does the intrasite generation.  Intersite is done by the Bridgehead DC for that partition within the site, it is called the Intersite Topology Generator (ISTG).

    What are you expecting?  As Meinolf already pointed out as long as replication is occuring as expected there is no issue.  Each Partition within Active Directory (AD) has a seperate bridgehead and replication responsibility. 

    Partitions:
    Schema
    Configuration
    Domain
    Application (DNS uses this now)

    So I believe this is why you will see two DC's sometimes, but to be honest I am not 100% positive on this.  The following article does a good job of detailing for you.
    http://technet.microsoft.com/en-us/library/cc755994(v=WS.10).aspx

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://blogs.dirteam.com/blogs/paulbergson  Twitter @pbbergs
    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

  • Wednesday, May 09, 2012 12:41 PM
     
     

    I've defined a IP site link for each spoke site. In this site link I've added the spoke site itself and the two hub sites. All site link I've defined has the same cost because they all have the same physical network connection.

    I'v the option "bridge all site" checked

    I exepct to have two automatically generated connection for each spoke sites.

  • Wednesday, May 09, 2012 1:38 PM
    Moderator
     
     

    ISTG is part of the KCC process and if everything is in place, then there is no reason CO is not generated. A good reference on the Intrasite and Intersite Topologies.

    http://etutorials.org/Server+Administration/Active+directory/Part+II+Designing+an+Active+Directory+Infrastructure/Chapter+9.+Creating+a+Site+Topology/9.1+Intrasite+and+Intersite+Topologies/

    Just delete all the connection object on one of the DC and run repadmin /kcc* and see if it can generate the topology.

    Also, verify the connectivity between all the DC are upto the mark along with DNS name resolution.


    Awinish Vishwakarma - MVP - Directory Services

    My Blog: awinish.wordpress.com

    Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

  • Wednesday, May 09, 2012 2:23 PM
     
     

    Hi,

    for one of the spoke site for which KCC fails to generate two connections I've done the following:

    1) delete connection object, deleted IP site like, create IP site link with the spoke site and the two hub site, forced KCC to create the connection -> I get only a connection

    2) edited the IP site link, removed the hub site with the existing connection, forced KCC to create the connections -> I get the prevously missing connection, but deleted the previous existing, result again only one connection

    3) ri-edited the IP site link, added the previously removed hub site, forced KCC to create the connections -> KCC deletes the connection created at 2) and left me with the same situation at 1)

  • Wednesday, May 09, 2012 3:34 PM
    Moderator
     
     

    Actually the KCC doesn't generate the intersite connections, it does the intrasite generation.  Intersite is done by the Bridgehead DC for that partition within the site, it is called the Intersite Topology Generator (ISTG).

    What are you expecting?  As Meinolf already pointed out as long as replication is occuring as expected there is no issue.  Each Partition within Active Directory (AD) has a seperate bridgehead and replication responsibility. 

    Partitions:
    Schema
    Configuration
    Domain
    Application (DNS uses this now)

    So I believe this is why you will see two DC's sometimes, but to be honest I am not 100% positive on this.  The following article does a good job of detailing for you.
    http://technet.microsoft.com/en-us/library/cc755994(v=WS.10).aspx

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://blogs.dirteam.com/blogs/paulbergson  Twitter @pbbergs
    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

    I did some further research and as long as the partitions are all the same and/or a single DC the topology will reuse itself, so each partition won't generate a second connection with respect to the partitions themselves.

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://blogs.dirteam.com/blogs/paulbergson  Twitter @pbbergs
    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

  • Wednesday, May 09, 2012 3:36 PM
    Moderator
     
     Proposed Answer

    I think you are confused, you don't have a problem.  The system is replicating as expected.  I will contact some folks to provide additional details as to why, but you are fine.

    Is Bridge All Site Links enabled (BASL)?

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://blogs.dirteam.com/blogs/paulbergson  Twitter @pbbergs
    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

  • Wednesday, May 09, 2012 6:13 PM
    Moderator
     
     Answered

    Since I haven't heard back from you, I am making the assumption that BASL is disabled.  This would be why your spokes are only connecting with your hubs. 

    Since BASL is disabled, your network must not be fully routed, so first thing I would check is to ensure that the spoke site that is only getting one connection has a route to this second hub.

    Second since there is no guarantee what interconnections exist and all sites are connected, there is no problem.

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://blogs.dirteam.com/blogs/paulbergson  Twitter @pbbergs
    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

  • Thursday, May 10, 2012 4:32 AM
     
     Answered

    You should not woory too much about the same as long as there is no replication issue between the DC.KCC will generate required topology for replication as per requirement.It seems that the connection is not required for the moment hence kcc is not generating the same for the server,it could generate the other hub site connection if the hub site(whose connection is visible) is down since BASL is enabled transitive connection will be created in the event of failure.

    Hope this helps


    Best Regards,

    Sandesh Dubey.

    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.