The system’s behaviour (TM&TC) generally remains consistent with previous versions, but the system is more rigorous in checking the loaded contents, especially where duplicates appear after merging several MIB’s.You are not obliged to clean up duplicates immediately, but you will see warnings. These warnings are correct, and you should clean up as soon as it is convenient.All table resolution (searching for cross-references) is now done after loading all tables; therefore, e.g. cross-references are now allowed from MIB databases loaded first to databases loaded last.
The whole MIB loading process is faster, because it performs fewer repeated sorts and searches during loading.
The correct user action when a duplicate is reported is to clean up duplicates from all except a single MIB. Note that cross-references are allowed from one MIB to another, even to MIB’s that are loaded later, but there is a potential ambiguity when the target object is duplicated. The ambiguity should be removed, to make sure that it is clear which TC or which TM object is actually to be used.
Recognising that it may not be convenient to clean up all duplicates immediately, a consistent approach is taken when a duplicate exists:
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.