Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Im field testing MWTM in my lab and I see confusing results when discovering new network configurations. Whats going on?

0
Posted

Im field testing MWTM in my lab and I see confusing results when discovering new network configurations. Whats going on?

0

The MWTM keeps information about older objects in its database even after they have been deleted. This is considered a logically deleted state. MWTM retains this information to try and maintain any user customized data associated with an object (for instance, a customized name) in case the object is rediscovered at some point in the future. Logically deleted data is physically deleted after seven days if it is not reused by then. You can use the mwtm purgedb command to immediately remove this logically deleted data from the MWTM database. Unfortunately, this benefit may have a side effect. In certain cases, rediscovery of a deleted object may cause the MWTM to use obsolete information in the database, rather than the new information. Ultimately, some configuration changes are not detected, and the viewable data from the client application is incorrect. There are 2 alternatives to address this behavior in a lab environment: 1. Change the default setting of 7 days to 0 in the Server.prop

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123