Re: Using ultrasound

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Inline

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

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.

"trmatthe" <trmatthe@xxxxxxxxx> wrote in message
news:1170071032.761372.55230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi. I'm using the latest ultrasound to monitor FRS and have a couple
of basic questions.

In the main ultrasound view I have a DC (DC1) with a green tick at the
base of a tree view. Underneath as a node I have another DC (DC2)
which has a red cross. I take this to mean that DC2 is a replica
partner with DC1.

excuse my ascii art but,

-DC1 (tick)
|
\---> DC2 (cross)

When I open the alert for DC2 (by clicking on it) I am told that I
have old backlogged files. I open Advanced to get more details. In the
alert data I have:

Connection: DC1 <--> DC2.
InboundServerDNS: DC1.
OutboundServerDNS: DC2.
ReplicaSet:sysvol
Inbound: Green Tick
Outbound: Red Tick.

The simple problem I have is "from which perspective is this data
produced"? An inbound partner provides data. An outbound partner is
one to which you feed data.

Am I right in saying that for the alert mentioned above:

Similar to an airport you have inbound and outbound aircraft. In
replication you have inbound and outbound data.

Outbound should be understood as files departing the DC
Inbound should be understood as files arriving to the DC


The data is from the perspective of DC1. DC1 is ok. However, its
outbound connection to DC2 is in fault with a queue of backlogged
files? In the alert details, the Inbound green tick refers to DC1 and
the outbound red tick refers to DC2.

DC2 is having problems exporting its replication. Open the help from
Ultrasound and try and determine why.


I think this is correct, but I would then expect to find DC2 as root
node in the tree view with a node underneath showing DC1 and stating
that the Inbound was in failure. In other words, the opposite of the
first entry.

Secondly, is there any current tool which will map a topology for me?
Ideally I would like to be able to select a server and find its
partners. Not necessarily graphically, but enough so that I can build
a chain, as I would do with Sites&Services and connection objects. I'm
working through ntfrsutl so if its in there, could you point me to the
command line?

There are probably third party tools but AD Sites and Services is a
definition of your current topology. You can try replmon.exe but I haven't
found it real useful, I have never gotten the topology view to work correct,
but I haven't put that much effort in to it.

http://technet2.microsoft.com/WindowsServer/en/library/078506cf-1221-42de-a221-b1a0d1151fd61033.mspx?mfr=true


I hope I've explained this clearly enough and thanks for any help you
can offer. I know it's a basic question but I want to be 100% sure.

trm



.



Relevant Pages

  • Using ultrasound
    ... In the main ultrasound view I have a DC (DC1) with a green tick at the ... Underneath as a node I have another DC (DC2) ... An inbound partner provides data. ...
    (microsoft.public.win2000.active_directory)
  • Re: Active Directory Replication
    ... You may want to verify that you have the direction on the firewall rule to ... The rule may be set to inbound and not outbound. ... > we add a user to DC2 the change shows up on DC1. ...
    (microsoft.public.win2000.active_directory)
  • how to turn firewall down
    ... Enable 3 Allow outbound destination unreachable ... Enable 9 Allow inbound router request ... 23 TCP Enable Telnet Server ...
    (comp.os.linux.networking)
  • Re: Message deferrals from EHS
    ... this is for inbound messages. ... on the sending server, if we did not use EHS. ... And outbound messages bound for EHS are working fine? ...
    (microsoft.public.exchange.connectivity)
  • HEADS UP: struct thread changed (Fwd: svn commit: r194012)
    ... Introduce a mechanism for detecting calls from outbound path of the ... where outbound path of the network stack calls into netgraph, ... netgraph nodes which can potentially reenter the network ... stack in the inbound path have to mark their inbound hooks using ...
    (freebsd-current)