NLSR

On the testbed it was observed that ChronoSync was trying to send large size data packets.
This is because whenever NLSR restarts it starts publishing on a new user prefix (Name and Coordinate LSA prefixes) since ChronoSync appends a new session name. Other NLSR (ChronoSync) still keeps track of the old NLSR and the State increases leading to the crashes as we saw on testbed.
When NSync was used NLSR fixed the session name. When switch to ChronoSync was made, this was over looked.