At 11:08 AM 1/17/01, ahmad wrote:
>Hi ,
>
>I agree with priscilla , but doesnt this master/slave relationship change
>after the slave had sent its dd packets to the master then the master
>becomes slave and sents the dd packets?
It's bidirectional communication. They both send and acknowledge DD
The master/slave relationship exists ONLY during the interface states from
EXSTART (where this relationship is negotiated) until a FULL adjacency is
achieved. The master/slave relationship is then terminated for the two
routers involved.
The DR may indeed become the slave. Master is the rout
Hi ,
I agree with priscilla , but doesnt this master/slave relationship change
after the slave had sent its dd packets to the master then the master
becomes slave and sents the dd packets?
can you send me the report of ur sniffer priscilla cause i havent yet been
able to see this besides books
P
I don't think the master/slave business is related to DR and BDR. It has to
do with neighbor adjacency and establishing the protocol for exchanging the
link state database.
After initializing, two neighbors establish bidirectional communication and
then enter the ExStart state. In this state,
The BDR will become the DR if the DR goes down. It
will stay the DR even_if_ the original DR comes back
online. Point to point links down have the option of
DR/BDR.
--- Gopinath Pulyankote <[EMAIL PROTECTED]> wrote:
> Hello all,
> Could someone explain what is master/slave
> relationship during
Hello all,
Could someone explain what is master/slave relationship during DBD
exchange. My understanding is that since DR is the Router with the highest
priority value, it will always be the master. So why have this definition ?
Or is it only used on Point-to-Point links, which don't elect DR & B
6 matches
Mail list logo