The slave will not set the M-bit to zero until it's database has been
sent. The master will keep sending a DD packet with a new sequence number
and the M-bit to zero, and the slave will keep sending a DD packet in reply
with the same sequence number and with LSA headers from it's database
inc
I am confused with following:
In ospf link state database synchronization process,When the master =
sends last DD packet,the slave sends an acknowledging DD packet that =
also has its M-bit set to zero.But if the slave has largger link state =
database than master,slave's rest database will be ign
I am confused with following:
In ospf link state database synchronization process,When the master =
sends last DD packet,the slave sends an acknowledging DD packet that =
also has its M-bit set to zero.But if the slave has largger link state =
database than master,slave's rest database will be ign
hi,all
I have a question about ospf link state database synchronization
process.
I think,two routes will be
1.exstart in which determine master/slave
2.exstart in which exchange database description packets(DDs).DDs
contrain enough information(LSA headers) to find more recent LSAs than
in its
4 matches
Mail list logo
