UCCE for CCM failover with DNS SRV.

we are testing UCCE for CCM failover with Local DNS SRV. We have enabled the "Use DNS SRV type query:YES"&"Resolve SRV records locally:1" on CVP Call server configuration SIP tab.
The srv.xml file updated with CCM  IP addrs in this path \Cisco\CVP\conf\srv.xml
On testing, the agent state moved to reserved state, but call is not delivered. Static Route is added for Phone Extension as "500>,proxy.ipcc.com".
What will be the issue? Kindly let me know what needs to be done.
Thanks & Regards
JP.

So, as Markus already figured out, you need to make sure that your CUCM actually understands that it is the intended recipient for these SIP INVITEs. I.e. if you define the static route to point to cucm.cisco.com you have to specificy the specify the Custer FQDN to be cucm.cisco.com under the 'Cluster Wide Domain Settings' in the CUCM Enterprise Parameters.
A second thing to watch out for the CUCM Group assigned to your SIP Trunks. Each SIP Trunk, like any CUCM device, has a Device Pool, the device pool has a UCM Group defining on which UCM nodes that device 'exists'. For phones that typically means : which UCM nodes can I register to ?
But for SIP trunks this means : which UCM nodes have a SIP deamon process for this Trunk and so which of the UCM nodes will actually accept INVITEs for this trunk. The most common cause for 503 Service Unavailable is probably this, (not all) the CUCM nodes in your DNS / srv.xml round robin are in the UCM Group assigned to the Device Pool configured on the SIP trunk for this Call Server.
Cheers,
Kris

Similar Messages

  • SPA 5xx and 9xx phones registering to all proxies with DNS SRV records

    A weird situation -- I use DNS SRV records to prioritize the two Asterisk servers to register to (east coast vs west coast).  However it seems that phones are often registering to BOTH servers and show as live on both at the same time.  There seems to be little rhyme or reason as to when it occurs, but it's weird.  Fortunately the phone does seem to be preferring the higher priority SRV record but I can't figure out why it is registering to both.
    This happens with SPA-942s (6.1.5a) and SPA504Gs (7.4.9c). 
    Any ideas what makes this happen?  On the surface it seems like a good thing, but functionally the phones are registering the same port numbers and only the priority server can get through firewalls with traffic for the phones.  This screws up my "presence" indicators within the system.
    DNS SRV RECORDS:
    _sip._udp.west.server.net  (for west coast customers)
    Priority 10:  west coast machine
    Priority 20:  east coast machine
    _sip._udp.east.server.net (for east coast customers)
    Priority 10:  east coast machine
    Priority 20:  west coast machine

    We determined this was not actually happening.  There was a syncing taking place in the background that was giving the impression this was happening but it really was not.

  • Architectural question for CCM failover WAN best practices

    I have a client that has a large CCM cluster in Texas. Approx 2000 phones register here over the wan from branch offices, HQ, etc. In Milwaukee, there is a call center that is going to go in for about 200 agents 24/7 operations. We are looking at the architecture of this design and are wondering if it would be wise to setup another cluster in Milwaukee just for the Call Center, then use Intercluster trunking between the two clusters.
    Or, could we just place a (2)subscribers at the Milwaukee location for a DR between the two sites? (Texas and Milwaukee).
    The WAN backbone is MPLS, so we could configure multiple T's back to the data center, etc. The problem we see is if what the Texax CCM cluster falls down... what happens then? Will the CallCenter be able to function?
    Any good advice, simple is better.
    Thanks much!

    What type of callcenter is it? IPCC Enterprise or Express?

  • Different SBA DNS SRV entry for the same dns zone?

    Hello,
    I got here a testlab with one enterprise pool and one sba deployed. The Branch Site got also an DNS Server installed. Both are using the same dns zone "test.com".
    Of course now i got different server for the same SRV Record _sipinternaltls._tcp.test.com - one for autodiscovery in the enterprise pool and one for the sba. Also I want to add the second one as failover srv + the DNS Server in the Enterprise Pool should
    be used as a Forwarder.
    Now I got some issues how to deploy several entries on two different dns server for the same zone.
    1.) If I add manually the same zone + DNS SRV entries on the SBA the dns is somehow not resolving/forwarding the entries on the other dns server in ee to other servers which are not on my SBA dns.
    2.) If I only pinpoint the SRV entries for _sipinternaltls._tcp.test.com (one for sba and failover for ee site) the dns won't resolve the second a record to the enterprise pool.
    What is the Best Practise for DNS SBA? Always point to the enterprise pool and, therefore, no other configuration is needed?
    Regards DrWho

    I played a little bit around. Problem was that I can not add the pinpoint dns srv entries via gui. Aditionally the tutorials did not work as my DNS server for SBA is not on a domain controller. In the end I did this:
    sbafe -> fqdn of my sba
    eefe -> fqdn of my frontend of enterprise pool
    dnscmd . /zoneadd _sipinternaltls._tcp.test.com. /primary /file _sipinternaltls._tcp.test.com.dns
    dnscmd . /recordadd _sipinternaltls._tcp.test.com. @ SRV 0 0 5061 sbafe.test.com.
    dnscmd . /recordadd _sipinternaltls._tcp.test.com. @ SRV 10 0 5061 eefe.test.com.
    dnscmd . /zoneadd sbafe.test.com. /primary /file sbafe.test.com.dns
    dnscmd . /recordadd sip.sbafe.test.com. @ A 192.168.10.220
    dnscmd . /zoneadd eefe.test.com. /primary /file eefe.test.com.dns
    dnscmd . /recordadd sip.eefe.test.com. @ A 192.168.0.40
    Question is if that is a good best proctise or should the dns server within a zone contain the same records (Primary/Backup). The Client will then always hit the FE of the EE Pool first.
    Also its quite a lot of work to setup.

  • ISSUE: "This domain controller must register a DNS SRV resource record, which is required for replication to function correctly"

    so we currently have three domain controllers set up, two of them on 2012r2 and one of them on 2008r2. prior to any of these domain controllers being added to the domain there was only one, running on 2003r2. the 2003r2 server was up and running when the
    first 2012r2 was added and that's when running 'dcdiag /e /c /v' would yield an issue with "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local" in the DNS portion of the diagnostics, specifically:
    TEST: Records registration (RReg)
    Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
    Error:
    Missing SRV record at DNS server 192.168.22.4:
    _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
    after adding the second 2012r2 to the domain, this issue is still there... adding the 2008r2 server to the domain and running BPA it gives the following:
    Title:
    This domain controller must register a DNS SRV resource record, which is required for replication to function correctly
    Severity:
    Error
    Date:
    7/3/2014 11:24:48 AM
    Category:
    Configuration
    Issue:
    The "DcByGuid" DNS service (SRV) resource record that advertises this server as an available domain controller in the domain and ensures correct replication is not registered. All domain controllers (but not RODCs) in the domain must register this record.
    Impact:
    Other member computers and domain controllers in the domain or forest will not be able to locate this domain controller. This domain controller will not be able to provide a full suite of services.
    Resolution:
    Ensure that "DcByGuid" is not configured in the "DnsAvoidRegisteredRecords" list, either through Group Policy or through the registry. Restart the Netlogon service. Verify that the DNS service (SRV) resource record "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local", pointing to the local domain controller "CM-DC4-NY01.cmedia.local", is registered in DNS.
    More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=126968
    I've tried scanning and then re-scanning every single entry in DNS Manager and do not see any reference to this specific GUID mentioned, nor do I see any other domain controllers referenced that should not be in there. The two 2012r2 and the 2008r2 domain
    controllers are the only ones listed in DNS Manager... the 2003r2 mentioned earlier failed and was removed.

    Just to chime in, I noticed that you said you have one 2008 R2 DC, and two 2012 DCs.
    I also noticed in the ipconfig /all that all DCs are pointint to themselves for DNS. We usually like to see them point to a partner, then itslelf as the second entry, w hether loopback or by its own IP.
    Based on that, what I suggest to level the playing field by choosing the WIndows 2008 R2 DC as the first DNS on all DCs and only administer DNS using that DC. The reason I chose that is because of the least common denominator is what we rather use so we
    don't invoke any new features in the newer 2012 DNS console that 2008 R2 may not understand.  After that's done, on each DC run (and you can use a PowerShell window to run this):
    Rename the system32\config\netlogon.dns and netlogon.dnb files by suffixing ".old" to the file.
    ipconfig /registerdns
    net stop netlogon
    net start netlogon
    Then re-run the dcdiag /e /c /v.
    Post your results, please.
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    I thought the DNS entries were supposed to be the other way around? point to themselves first and a partner as secondary? regardless, as requested, I've changed it to what you've prescribed where they point to the 2008r2 server as the primary with themselves
    as the secondary. I've also followed the steps to what seems like refreshing the DNS? on each of the DCs. Here's the output from dcdiag /e /c /v
    Directory Server Diagnosis
    Performing initial setup:
    Trying to find home server...
    * Verifying that the local machine CM-DC1-NY01, is a Directory Server.
    Home Server = CM-DC1-NY01
    * Connecting to directory service on server CM-DC1-NY01.
    * Identified AD Forest.
    Collecting AD specific global data
    * Collecting site info.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory
    =ntDSSiteSettings),.......
    The previous call succeeded
    Iterating through the sites
    Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia
    ,DC=local
    Getting ISTG and options for the site
    * Identifying all servers.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=nt
    DSDsa),.......
    The previous call succeeded....
    The previous call succeeded
    Iterating through the list of servers
    Getting information for the server CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    * Identifying all NC cross-refs.
    * Found 3 DC(s). Testing 3 of them.
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC1-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC3-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC4-NY01 passed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Advertising
    The DC CM-DC1-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC1-NY01 is advertising as an LDAP server
    The DC CM-DC1-NY01 is advertising as having a writeable directory
    The DC CM-DC1-NY01 is advertising as a Key Distribution Center
    The DC CM-DC1-NY01 is advertising as a time server
    The DS CM-DC1-NY01 is advertising as a GC.
    ......................... CM-DC1-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    [CM-DC1-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC1-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC1-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC1-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC1-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC1-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    ......................... CM-DC1-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC1-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC1-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC1-NY01\netlogon
    Verified share \\CM-DC1-NY01\sysvol
    ......................... CM-DC1-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC1-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC1-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC1-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC1-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 4609 to 5108
    * rIDPreviousAllocationPool is 4609 to 5108
    * rIDNextRID: 4629
    ......................... CM-DC1-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC1-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    A warning event occurred. EventID: 0x0000002F
    Time Generated: 07/08/2014 13:19:14
    Event String:
    Time Provider NtpClient: No valid response has been received from manually configured peer 0.ca.pool.ntp.org
    after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a n
    ew peer with this DNS name. The error was: The peer is unreachable.
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC1-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC1-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC1-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC1-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Advertising
    The DC CM-DC3-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC3-NY01 is advertising as an LDAP server
    The DC CM-DC3-NY01 is advertising as having a writeable directory
    The DC CM-DC3-NY01 is advertising as a Key Distribution Center
    The DC CM-DC3-NY01 is advertising as a time server
    The DS CM-DC3-NY01 is advertising as a GC.
    ......................... CM-DC3-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC3-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC3-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC3-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC3-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC3-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC3-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC3-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    ......................... CM-DC3-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC3-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC3-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC3-NY01\netlogon
    Verified share \\CM-DC3-NY01\sysvol
    ......................... CM-DC3-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC3-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC3-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC3-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC3-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15109 to 15608
    * rIDPreviousAllocationPool is 15109 to 15608
    * rIDNextRID: 15110
    ......................... CM-DC3-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC3-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC3-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC3-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC3-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC3-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Advertising
    The DC CM-DC4-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC4-NY01 is advertising as an LDAP server
    The DC CM-DC4-NY01 is advertising as having a writeable directory
    The DC CM-DC4-NY01 is advertising as a Key Distribution Center
    The DC CM-DC4-NY01 is advertising as a time server
    The DS CM-DC4-NY01 is advertising as a GC.
    ......................... CM-DC4-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC4-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC4-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC4-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC4-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC4-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC4-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC4-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    ......................... CM-DC4-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC4-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC4-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC4-NY01\netlogon
    Verified share \\CM-DC4-NY01\sysvol
    ......................... CM-DC4-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC4-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC4-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC4-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC4-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15609 to 16108
    * rIDPreviousAllocationPool is 15609 to 16108
    * rIDNextRID: 15609
    ......................... CM-DC4-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC4-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC4-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC4-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC4-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC4-NY01 passed test VerifyReplicas

  • Gateway Failover with CCM 4 1 3b

    Hi
    I am having issues with gateway redundancy on CCM 4-1-3b. Basically when the Primary route group gateway fails, the backup gateway does not work. You can not make external calls out of this gateway unless you change the priority of the gateways in the route group manually. The only other time it failsover is if ip connectivity fails between the primary gateway and the CCM. Has anyone had any issues like this or is there a bug with this version of CCM? Failover with RG/RL should be a basic feature with CCM?

    Hi Derek,
    CCM regards H323 gateways as a black hole. CCM does not have the ability see the busy/fail status of the H323 ports. As you said, the only way CCM would switch to the second gateway, in the Route List, would be if IP connectivity was lost.
    I would recommend that you additionally configuring outbound VOIP dial-peers (with a higher preference value) to forward the call from your first gateway to your second gateway when the first gateway is up and, for whatever reason, the outward ports are busy or down.
    Regards
    Chris

  • Impact of wrong DNS in DHCP scope for CCM

    We recently deployed some phones at a new site  which were displaying  error messages on the screen
    The initial issue was that Option 150 as not set up - resolved-
    Phone now seemed to register to CCM (8.6) - IP address located to phone but CCM was showing rejected  on the phone page 
    Phone displayed error  messages "Db config." and "Security"  
    Db Config looked like it was that no phone was configured/MAC address, phone type etc  - incorrect double checked all ok
    Other could be replication between Cluster but again all ok
    Security error - Led me to look at the security trust list and delete it and as normally this solves the problem
    The actual issue/resolution  was incorrect DNS name in the Option 15 of the scope - e.g xxxx.net instead of xxx.com 
    Why would this lead to the above issues, I thought the main requirement was the 150 for the TFTP 
    Any thoughts, answers
    Many thanks

    The issue was that there was an incorrect DNS option 15 given out e.g mycompany.com  instead of the correct one of mycompany.com, Option 150 was an IP as normal 
    I think the issue was as follows
    Our CCM`s have host names such XXX-CMSUB1, XXX-CMSUB2 etc instead of IP address- before I joined. If my thinking is correct the phone received its TFTP as normal and was provided with the CM Group but in our case the group contained Host names instead of IP address. The Host names were then added to the Option 15 DNS    and so the phones tried to look for CCM`s at XXX-CMSUB1.mycompnaya.net and XXX-CMSUB2.mycompanya.net which failed since DNS has the CCM`s as XXX-CMSUB1.mycompnaya.com and XXX-CMSUB2.mycompanya.com
    Does this make sense , if so why the Security and db config issue unless these are standard error messages?

  • Creating a DNS Record for a Host with Two or More IP???

    Can we create DNS A Record for a Host with Two or More IP ... ( we like to use my website  "mysite.com" pointing to two Ips )
    Please help...

    Sure, no worries.
    In a production environment DNS will query always the first record it will stores in cache, you need to find a dynamic or NLB way to achieve the automatic fail over else when you will have an outage with the first IP, then you need to ask your clients to
    clear the cache and register to DNS again, this i will not suggest in a production environment, lots of manual efforts and doesnt sound like a solution in a production environment, i would suggest you to explore windows NLB, it's easy to set and use the OS
    license.
    Thanks
    Inderjit

  • Re: Failover for SO's with context

    Right, delivery of events is not guaranteed by Forte, even though
    it is reasonable to rely on it in the case of two Forte servers on a LAN.
    I would not go towards a solution for securing events delivery by
    an acknowledgement mechanism (ack event or shared object notifier),
    because of increased complexity and performance overhead.
    On the other hand, a second simple security level can be provided by
    enabling
    your mirror/backup SO to be refreshed at will, by letting it get a
    snapshot
    of the current transient data to be mirrored, so you can :
    - Start your partitions in any order (The mirror partition will first
    task a
    snapshot of the transient data, then will register for mirror events)
    - Start and stop the mirror partition at will, without disrupting the
    application
    Then, if you do not trust events delivery, you can reinitialize your
    mirror
    periodically (say every 12 hours) to minimize the risks of losing
    transient
    data events.
    Again, this solution is suited to low volumes of transient data.
    I guess what Chad means by journaling is writing to a log file any
    event (in a large sense) happening on data from its initial value. Then
    if
    you need to restore state, you re-play the events from the initial value.
    This is a common solution in the banking area where you need to backup
    values but also events on the values. I do not know how this can be
    applied
    to a generic mechanism with Forte, but it may be a good way to explore,
    although probably more complex to implement with Forte than the
    Backup SO/ Events pattern.
    Hope this helps,
    Vincent Figari
    On Fri, 13 Feb 1998 10:39:03 -0600 Chad Stansbury
    <[email protected]> writes:
    Actually, since events (let alone distributed events) are not
    'guaranteed delivery' in Forte, I would hesitate to use events
    as a mechanism of mirroring your data - unless, of course, you
    really don't require an industrial strength failover strategy.
    This would also apply to asynchronous messaging (unless you
    are careful to register for exception events (which again, aren't
    guaranteed delivery) and have a mechanism to handle said
    asynchronous exception events. I also know that Forte will retry
    certain tasks when the service object it is sent to fails com-
    pletely (like a NIL object exception), but don't know enough
    about the internal workings of Forte to know under which conditions
    this will occur.
    I think that the most common method of a truly industrial-
    strength, guaranteed-delivery mechanisms is via journaling...
    which I know very little about, but is something that you should
    be able to look up and study if that's what you require.
    Again, if you don't care about the (admittedly small) chance
    of an asynchronous call failing, then the suggestions that
    Vincent has already made are good ones.
    From: [email protected]
    To: [email protected]
    Cc: [email protected]
    Sent: 2/13/98 9:13:17 AM
    Subject: Re: Failover for SO's with context
    Steven,
    The pattern choice between external resource vs SO is dependent on the
    type
    of transient data you want to backup. Probably the external resource
    is
    better
    suited to high volumes of data. We have implemented the 'Backup SO'
    pattern because our transient data volumes are rather low (which I
    guess
    must
    be the most common case for global, transient data).
    Whatever the choice you do :
    - Be sure to enforce encapsulation for updating the transient data, in
    order to
    guarantee that any modification to your transient data is duplicated
    on
    the backup
    SO or the external resource
    - About performances, the CPU cost is fairly low for your 'regular'
    application if you
    take care to :
    * use asynchronous tasks to update the external resource
    or
    * use events to notify the backup SO
    Now it is true that you will have a network overhead when using
    events,
    as your
    backup SO shall be isolated in a remote partition on a remote
    server.
    That is one good argument to select the Backup SO pattern for low
    volumes of
    transient data.
    If you choose the 'Backup SO' pattern, you will also have to be
    careful
    not sending
    any distributed reference to your Backup SO but only clones.
    Anyway, the backup SO pattern works fairly well for low volumes of
    data,
    but requires lots of testings and a good understanding of events and
    communication
    across partitions.
    Hope this helps,
    Vincent Figari
    On Fri, 13 Feb 1998 09:24:57 +0100 Steven Arijs <[email protected]>
    writes:
    We're going to implement a failover scenario for our application.
    Unfortunately, we also have to replicate the state of our failed
    service
    objects.
    I've browsed the Forte site and found a TechNote concerning this
    (TechNote 11074).
    In this TechNote they talk about a service object that is responsible
    for updating all backup service objects when needed.
    It seems to me that when I implement that way, I will be creating a
    lot
    of overhead, i.e. I will be doing a lot of stuff several times.
    What will be the effects on my performance ?
    The way with the least performance loss would be to use an external
    resource that is updated. But what if this external resource also
    fails
    Is there any one who has already implemented a failover scenario for a
    service objects with state ?
    Any help would be appreciated.
    Steven Arijs
    ([email protected])
    You don't need to buy Internet access to use free Internet e-mail.
    Get completely free e-mail from Juno at http://www.juno.com
    Or call Juno at (800) 654-JUNO [654-5866]
    You don't need to buy Internet access to use free Internet e-mail.
    Get completely free e-mail from Juno at http://www.juno.com
    Or call Juno at (800) 654-JUNO [654-5866]

    Right, delivery of events is not guaranteed by Forte, even though
    it is reasonable to rely on it in the case of two Forte servers on a LAN.
    I would not go towards a solution for securing events delivery by
    an acknowledgement mechanism (ack event or shared object notifier),
    because of increased complexity and performance overhead.
    On the other hand, a second simple security level can be provided by
    enabling
    your mirror/backup SO to be refreshed at will, by letting it get a
    snapshot
    of the current transient data to be mirrored, so you can :
    - Start your partitions in any order (The mirror partition will first
    task a
    snapshot of the transient data, then will register for mirror events)
    - Start and stop the mirror partition at will, without disrupting the
    application
    Then, if you do not trust events delivery, you can reinitialize your
    mirror
    periodically (say every 12 hours) to minimize the risks of losing
    transient
    data events.
    Again, this solution is suited to low volumes of transient data.
    I guess what Chad means by journaling is writing to a log file any
    event (in a large sense) happening on data from its initial value. Then
    if
    you need to restore state, you re-play the events from the initial value.
    This is a common solution in the banking area where you need to backup
    values but also events on the values. I do not know how this can be
    applied
    to a generic mechanism with Forte, but it may be a good way to explore,
    although probably more complex to implement with Forte than the
    Backup SO/ Events pattern.
    Hope this helps,
    Vincent Figari
    On Fri, 13 Feb 1998 10:39:03 -0600 Chad Stansbury
    <[email protected]> writes:
    Actually, since events (let alone distributed events) are not
    'guaranteed delivery' in Forte, I would hesitate to use events
    as a mechanism of mirroring your data - unless, of course, you
    really don't require an industrial strength failover strategy.
    This would also apply to asynchronous messaging (unless you
    are careful to register for exception events (which again, aren't
    guaranteed delivery) and have a mechanism to handle said
    asynchronous exception events. I also know that Forte will retry
    certain tasks when the service object it is sent to fails com-
    pletely (like a NIL object exception), but don't know enough
    about the internal workings of Forte to know under which conditions
    this will occur.
    I think that the most common method of a truly industrial-
    strength, guaranteed-delivery mechanisms is via journaling...
    which I know very little about, but is something that you should
    be able to look up and study if that's what you require.
    Again, if you don't care about the (admittedly small) chance
    of an asynchronous call failing, then the suggestions that
    Vincent has already made are good ones.
    From: [email protected]
    To: [email protected]
    Cc: [email protected]
    Sent: 2/13/98 9:13:17 AM
    Subject: Re: Failover for SO's with context
    Steven,
    The pattern choice between external resource vs SO is dependent on the
    type
    of transient data you want to backup. Probably the external resource
    is
    better
    suited to high volumes of data. We have implemented the 'Backup SO'
    pattern because our transient data volumes are rather low (which I
    guess
    must
    be the most common case for global, transient data).
    Whatever the choice you do :
    - Be sure to enforce encapsulation for updating the transient data, in
    order to
    guarantee that any modification to your transient data is duplicated
    on
    the backup
    SO or the external resource
    - About performances, the CPU cost is fairly low for your 'regular'
    application if you
    take care to :
    * use asynchronous tasks to update the external resource
    or
    * use events to notify the backup SO
    Now it is true that you will have a network overhead when using
    events,
    as your
    backup SO shall be isolated in a remote partition on a remote
    server.
    That is one good argument to select the Backup SO pattern for low
    volumes of
    transient data.
    If you choose the 'Backup SO' pattern, you will also have to be
    careful
    not sending
    any distributed reference to your Backup SO but only clones.
    Anyway, the backup SO pattern works fairly well for low volumes of
    data,
    but requires lots of testings and a good understanding of events and
    communication
    across partitions.
    Hope this helps,
    Vincent Figari
    On Fri, 13 Feb 1998 09:24:57 +0100 Steven Arijs <[email protected]>
    writes:
    We're going to implement a failover scenario for our application.
    Unfortunately, we also have to replicate the state of our failed
    service
    objects.
    I've browsed the Forte site and found a TechNote concerning this
    (TechNote 11074).
    In this TechNote they talk about a service object that is responsible
    for updating all backup service objects when needed.
    It seems to me that when I implement that way, I will be creating a
    lot
    of overhead, i.e. I will be doing a lot of stuff several times.
    What will be the effects on my performance ?
    The way with the least performance loss would be to use an external
    resource that is updated. But what if this external resource also
    fails
    Is there any one who has already implemented a failover scenario for a
    service objects with state ?
    Any help would be appreciated.
    Steven Arijs
    ([email protected])
    You don't need to buy Internet access to use free Internet e-mail.
    Get completely free e-mail from Juno at http://www.juno.com
    Or call Juno at (800) 654-JUNO [654-5866]
    You don't need to buy Internet access to use free Internet e-mail.
    Get completely free e-mail from Juno at http://www.juno.com
    Or call Juno at (800) 654-JUNO [654-5866]

  • Oracle 11gR2 RAC installation with DNS

    Dear Guru's,
    I want to configure RAC on two node cluster with DNS(For SCAN) in my testing server.
    O.S: RHEL5.4(64 bit)
    Oracle Version: 11gR2(11.2.0.2)
    Note: Am creating nodes in VMware ESXi server.
    Just I want to know whether DNS should be configure in any one of those NODES or in separate machine.
    Bala :)

    Hi Bala,
    I want to configure my Database with & without DNS. (Will try both installation in different servers)I think, you have already received a link on very good article about Oracle RAC installation without DNS and DHCP (I mean Jeffrey Hunter's article).
    There is one more about Oracle RAC installation with DNS and DHCP (http://gjilevski.com/2011/10/05/build-two-node-oracle-rac-11gr2-11-2-0-3-with-gns-dns-dhcp-and-haip/).
    And want to know how it forwards the client connection if a node fails.. Can anyone update the URL for this..There are a lot of information about it:
    - http://www.oracle.com/technetwork/database/features/oci/taf-10-133239.pdf
    - http://docs.oracle.com/cd/E14072_01/java.112/e10589/apxracfan.htm
    - http://www.oracle.com/technetwork/database/app-failover-oracle-database-11g-173323.pdf
    Very good videos:
    - http://www.dsvolk.ru/oracle/racdd4d/demos/video/taf/session/session_viewlet_swf.html
    - http://www.dsvolk.ru/oracle/racdd4d/demos/video/taf/select/select_viewlet_swf.html
    - http://www.dsvolk.ru/oracle/racdd4d/demos/video/taf/callback/callback_viewlet_swf.html
    - http://www.dsvolk.ru/oracle/racdd4d/demos/video/fan/fan_viewlet_swf.html
    Hope it helps,
    Best regards,
    Gena

  • CUCM IM and P Design - DNS SRV -

    Hey guys.
    I would like to design a CUCM IM and P infrastructure for my customer. High availability is mandatory for my customer and here is what I found from the documentation:
    Configure SIP Trunk for IM and Presence Service
    If high availability is configured for the IM and Presence cluster, multiple entries should be entered in the Dotted IP Address or FQDN to identify the various nodes in the cluster. DNS SRV cannot be used for an IM and Presence cluster if high availability is configured.
    So SRV record can't be used for an IM and P cluster.
    Now if I want to configure a presence gateway on the CUCM IM and P, the configuration guide says that we must configure a CUCM as a presence gateway to enable SIP connection:
    The problem is that I cannot configure 2 or more CUCM Presence gateways ... and for that I have to use a DNS SRV.
    But I can't use an DNS SRV because I am using high availability ... This is a chicken and egg problem to me :)
    Does someone has a recommendation please ? 
    Thanks guys :)

    Actually, the config guide allows DNS SRV on the Presence Gateway config of the IM&P servers:
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/10_5_1/CUP0_BK_CE43108E_00_config-admin-guide-imp-105/CUP0_BK_CE43108E_00_config-admin-guide-imp-105_chapter_0111.html#d54883e741a1635
    It appears they are only disallowing SRV in the CCM to IM&P SIP Proxy, not the other way around.

  • Finding proxy through DNS SRV

    Can Cisco SPA phones use DNS SRV record to find and select outbound proxy even if there are 3 or 4 answered from the DNS query?
    Is there a way to over-ride the cost and weight with custom selection method?

    If implemented according RFC2782 the device should contact proxy1.doman.com, then proxy2.doman.com then either proxy3.doman.com or proxy4.doman.com with probability 50:50.
    So what's your question ? Are you asking if particular device's resolver follow the RFC2782 correctly ? You didn't specified device nor exact firmware version so it's not possible to answer.  And implementation may vary between product's model and firmware version.
    Just try it on your particular hardware and firmware - it's simple test. It should work if implemented correctly ...
    Sorry if it's not the answer you wished for ...

  • Problem with DNS - ping/Safari cannot resolve, but host/dig work OK

    Hi All,
    Have a weird problem with DNS which is a bit similar to the following ones:
    http://discussions.info.apple.com/thread.jspa?threadID=2190208
    http://forums.macrumors.com/showthread.php?t=337942
    I connect with remote internal network via OpenVPN and from time to time (yes, intermittent problem :)) internal DNS names cannot be resolved.
    When it happens I can still resolve names using host or dig utilities, but applications (like Safari) and ping cannot resolve them.
    resolv.conf has proper DNS server set:
    *$ cat /etc/resolv.conf*
    *# Mac OS X Notice*
    *# This file is not used by the host name and address resolution*
    *# or the DNS query routing mechanisms used by most processes on*
    *# this Mac OS X system.*
    *# This file is automatically generated.*
    *domain openvpn*
    *search openvpn*
    *nameserver 10.0.0.1*
    More than that - it can resolve those internal names when queried directly, for example using host:
    *$ host YYY.XXX.ru 10.0.0.1*
    *Using domain server:*
    *Name: 10.0.0.1*
    *Address: 10.0.0.1#53*
    Aliases:
    *YYY.XXX.ru has address 192.168.x.y*
    but at the same time ping reports "*Unknown host*":
    *$ ping YYY.XXX.ru*
    *ping: cannot resolve YYY.XXX.ru: Unknown host*
    I tried "*dscacheutil -flushcache*" and it did not help. Also tried to comment out domain and search directives in resolv.conf and it did not help as well (and actually it should not matter).
    Any ideas why this can happen and what else can I check when it happens again?
    Thanks!

    I have the same issue. It cropped up after I installed updates to MS Office 2008 and Firefox in which I also saw issues with the icons disappearing in the dock of the applications that were open when I started the Office update. I rebooted to try to get them back, but ended up deleting them and restoring from the Applications folder. I don't know if that's a red herring or not, but I generally try to figure out what has recently changed that may cause something to suddenly start failing.
    I'd been working successfully all morning before it started acting up. Switching from wifi to cat5 had no effect.
    @realaaa, were you able to resolve without a major undertaking, like reinstalling your OS?
    pnmbp:~ pn$ dig goo.gl
    ; <<>> DiG 9.6.0-APPLE-P2 <<>> goo.gl
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40996
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
    ;; QUESTION SECTION:
    ;goo.gl. IN A
    ;; ANSWER SECTION:
    goo.gl. 140 IN A 74.125.45.139
    goo.gl. 140 IN A 74.125.45.102
    goo.gl. 140 IN A 74.125.45.113
    goo.gl. 140 IN A 74.125.45.138
    goo.gl. 140 IN A 74.125.45.101
    goo.gl. 140 IN A 74.125.45.100
    ;; Query time: 27 msec
    ;; SERVER: 192.168.2.1#53(192.168.2.1)
    ;; WHEN: Mon Dec 13 16:59:34 2010
    ;; MSG SIZE rcvd: 120
    pnmbp:~ pn$ ping goo.gl
    ping: cannot resolve goo.gl: Unknown host
    pnmbp:~ pn$ curl <a class="jive-link-external-small" href="http://">http://goo.gl
    curl: (6) Couldn't resolve host 'goo.gl'
    pnmbp:~ pn$ host goo.gl
    goo.gl has address 74.125.45.100
    goo.gl has address 74.125.45.101
    goo.gl has address 74.125.45.138
    goo.gl has address 74.125.45.113
    goo.gl has address 74.125.45.102
    goo.gl has address 74.125.45.139
    pnmbp:~ pn$

  • TCP connection for DHCP failover frequently are broken in Solaris 10

    Hi
    We have two dhcp servers which are installed in Solaris 10 and set to a failover pair. Currently, we can find that tcp connection for dhcp failover protocol are frequently broken. It looks like that primary dhcp server initiatively send FIN message to secondary one but in general, this tcp connection should always keep alive. On the other hand, the tcp connection can not completely be closed right now which FIN_WAIT_2 status in Primary one and CLOSE_WAIT status in secondary would last for a long time.
    Will Solaris 10 cause this fault? Is it a known bug in OS?
    OS info:
    -bash-3.00$ cat /etc/release
    Solaris 10 5/08 s10s_u5wos_10 SPARC
    Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
    Use is subject to license terms.
    Assembled 24 March 2008
    -bash-3.00$
    -bash-3.00$
    -bash-3.00$ uname -a
    SunOS edns1 5.10 Generic_142900-03 sun4v sparc SUNW,Netra-T5220
    TCP connection info:
    Primary DHCP Server:
    2012 08 29 03:41:43
    PING 172.25.6.137: 56 data bytes 64 bytes from edns2 (172.25.6.137): icmp_seq=0. time=0.678 ms
    remote refid st t when poll reach delay offset disp
    ==============================================================================
    *idns1           195.26.151.151   3 u   45 1024  377     0.75   -0.071    0.05
    +idns2           195.26.151.151   3 u  162 1024  377     0.93    0.169    0.08
    clusternode1-pr 0.0.0.0 16 - - 1024 0 0.00 0.000 16000.0
    +clusternode2-pr idns1            4 u  406 1024  376     0.49   -0.154   15.12
    172.25.6.133.647 172.25.6.137.58107 49640 0 49640 0 ESTABLISHED
    172.25.6.133.647 *.* 0 0 49152 0 LISTEN
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    2012 08 29 03:41:47
    PING 172.25.6.137: 56 data bytes 64 bytes from edns2 (172.25.6.137): icmp_seq=0. time=0.535 ms
    remote refid st t when poll reach delay offset disp
    ==============================================================================
    *idns1           195.26.151.151   3 u   49 1024  377     0.75   -0.071    0.05
    +idns2           195.26.151.151   3 u  166 1024  377     0.93    0.169    0.08
    clusternode1-pr 0.0.0.0 16 - - 1024 0 0.00 0.000 16000.0
    +clusternode2-pr idns1            4 u  410 1024  376     0.49   -0.154   15.12
    172.25.6.133.647 172.25.6.137.58107 49640 0 49640 0 FIN_WAIT_2
    172.25.6.133.647 *.* 0 0 49152 0 LISTEN
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Secondary DHCP Server:
    2012 08 29 03:41:41
    PING 172.25.6.133: 56 data bytes 64 bytes from edns1 (172.25.6.133): icmp_seq=0. time=1.26 ms
    remote refid st t when poll reach delay offset disp
    ==============================================================================
    *idns1           195.26.151.151   3 u  450 1024  377     0.92   -0.067    0.06
    +idns2           195.26.151.151   3 u  552 1024  377     0.96    0.237    0.08
    +clusternode1-pr idns1            4 u  360 1024  377     1.85   -0.528    1.51
    clusternode2-pr 0.0.0.0 16 - - 1024 0 0.00 0.000 16000.0
    172.25.6.137.647 *.* 0 0 49152 0 LISTEN
    172.25.6.137.58107 172.25.6.133.647 49640 0 49640 0 ESTABLISHED
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    2012 08 29 03:41:45
    PING 172.25.6.133: 56 data bytes 64 bytes from edns1 (172.25.6.133): icmp_seq=0. time=1.36 ms
    remote refid st t when poll reach delay offset disp
    ==============================================================================
    *idns1           195.26.151.151   3 u  454 1024  377     0.92   -0.067    0.06
    +idns2           195.26.151.151   3 u  556 1024  377     0.96    0.237    0.08
    +clusternode1-pr idns1            4 u  364 1024  377     1.85   -0.528    1.51
    clusternode2-pr 0.0.0.0 16 - - 1024 0 0.00 0.000 16000.0
    172.25.6.137.647 *.* 0 0 49152 0 LISTEN
    172.25.6.137.58107 172.25.6.133.647 49640 0 49640 0 CLOSE_WAIT
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Thanks!

    Thanks, but had found a previous discussion with this hint and applied it.
    svccfg -s sendmail listprop shows config /local_only = false
    Yes, I would really love to fix the fault, but what I would really like is some hints as to how to debug ports under svc control.

  • 2008 R2 failover cluster dns

    Hello,
    Wondering if there is any best practices when it comes to setting up DNS. Options are either dynamic DNS or add static A records for nodes and cluster name. Also I understand that there will be no DNS servers specified in TCP properties of the heartbeat
    NIC.
    Thanks

    Hi,
    please check "Network infrastructure and domain account requirements for a failover Cluster"
    http://technet.microsoft.com/en-us/library/ff182359(v=ws.10).aspx#BKMK_Account_Infrastructure
    The cluster should automatic register DNS records for ech cluster node and for the cluster name.
    And yes, you do not need to specify DNS servers for heartbeat, livemigration or CSV NIC.
    Hope that helps
    Regards
    Sebastian

Maybe you are looking for

  • Installed- and fixed- iTunes 7.6 and now can't load 100 items onto iPod

    Hi, I just got done fixing my compatability issue with iTunes 7.6 (error -2096) and when I tried to update my iPod it says that 100 items were not copied to my iPod because it (or my computer, I'm not exactly sure) are not authorized to play them. Ca

  • Link between Material Document and Notification Number

    Hi In table QMEL we find the material document that is generated in correspond to Inspection Lot not for Notification((Goods Movement - Material Document). Our problem is that we didn't find the material document(Goods Movement) generated after notif

  • Has anyone successfully put varnish in front of web service?

    I've got server app 3.2.1 on a mac mini server.  love the machine, but want to put varnish in front of the web service.  so far it's been a hassle.  I can't even get the 0000_any_80_site.example.com.conf file to listen on 127.0.0.1:80... I start varn

  • Battery life is minimal - should I have it looked at?

    16GB iPod touch, bought back in February, exact same day as the 32GB came out I've had no end of little annoying things wrong with it: stuck pixel right in the center of the screen, safari randomly quits, volume control acts really oddly when I touch

  • Zen micro firmware upgr

    I have a zen micro with a firmware of ..0 i need to upgrade to the 2.20.05 for a music subscription service. I have unchecked the detector box and have tried everything possible the upgrade the firmware.when i do it says "An application is interferri