Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts IP / TSM : What is the purpose of the IsIPNetworkFirstEnabled, IsIgnoreLargeIPNetworkEnabled, and IsNonRelayDeviceFirstEnabled options in tsm.conf? (304695)

Last Updated: 12/17/2018Categories: How toTotal Views: 2201Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

What is the purpose of the IsIPNetworkFirstEnabled, IsIgnoreLargeIPNetworkEnabled, and IsNonRelayDeviceFirstEnabled options in tsm.conf?

1) IsIPNetworkFirstEnabled is not used much by the topology split algorithm in release 9.1 and later. There is code left over that starts the weight threshold for each domain at a different value if IsIPNetworkFirstEnabled is TRUE, but there is no real reason to change IsIPNetworkFirstEnabled from its default value of FALSE.

The above also applies if using the scripts shipped with Smarts IP Manager 7.0.4 through 9.0, but prior to release 9.1, Topology Split Manager installations almost always involved Professional services, and tended to have more customized scripts. Some customized scripts were based on a different code branch, which still used IsIPNetworkFirstEnabled. On any installation prior to 9.1 we should check the scripts in local/rules/discovery/topo-split and rules/discovery/topo-split to be sure if this property is used.

2) IsIgnoreLargeIPNetworkEnabled:

Traditionally, this was meant to overcome configuration mistakes in environments that would cause very strange splits. For example, the 10.0.0.0 IP Network could be matched with a variety of subnet masks and is officially a class B network. Previously the software could have issues where a single misconfigured device would associate two separate (but numerically overlapping) IP Networks into one really big network. This incorrect joining of networks could create a significant number of proxy devices in the split AM domains.

It is extremely rare to see anything larger than a class C network being used in Smarts IP Manager environments. Large, flat IP networks are simply not the norm. So, the software assumes that anything larger than class C is probably a misconfiguration rather than a "real" network.

The flag was so that if someone had a subnetted class B network (not the full class B) that was actually part of their network design, TSM could be made to work. Unless someone has a specific problem, there is no reason they should ever change the value of that flag.

3) IsNonRelayDeviceFirstEnabled:

The assumption here is that most non-relay devices historically have had a single IP address and a single physical connection to the network. Generally they would be poor candidates for being an edge of the split. The idea is to quickly assign them and concentrate on the more interesting devices. Internal testing with IsNonRelayDeviceFirstEnabled=TRUE since that time, however, has not uncovered any problems.  This option in current versions is unlikely to create much difference in the topology split.

The flag applies to devices which are not an instance of RelayDevice. Classes which inherit from RelayDevice in Smarts IP Manager are Router, Bridge, Switch, and Hub.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant