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: What is a Smarts partition? (319427)

Last Updated: 3/22/2024Categories: How toTotal Views: 1774Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

What is a Smarts partition?

Overview:

Availability Manager only creates partitions with two or more elements.  More often than not, network devices managed by InCharge are not connected continuously due to various reasons. For example:

- devices are not in the seed file;
- devices are not managed by other management platforms where the initial seeds for discovery are taken from.
- network managements do not have access to manage the backbone

switches and routers that interconnect managed devices.

As a result, the managed domain is broken into network partitions. In some scenarios, a failure in the network can break connectivity between the management station and all the devices in a partition.  Support for Partition in the InCharge Application adds the diagnosis of Partition Down failure. A Partition Down failure occurs when the management station loses connection to ALL the devices in a partition.

Specifications:

A partition is defined as a group of managed computer systems in the InCharge topology that are interconnected to each other, that is, a managed computer system can reach any other managed computer system in the same partition by traversing layer 2 and/or layer 3 connectivity relationships.

Class name:  Partition

Root cause: Partition Down

ConsistsOf/MemberOf relationships between Partition and
ICIM_UnitaryComputerSystem (Switch, Router, Host, etc.)

relationshipset ConnectedSystems in IPNetwork
- show computer systems in a network, similar to ConnectedSystems in a VLAN.

Configuration:

- Enable/disable partitioning through sm_tpmgr and discovery.conf
- Set partition DisplayName through partition.conf file

It is very important to notice that InCharge does not report failures on ANY unmanaged entity. It is thus important to notice the effect of that on partitions. If two managed devices are connected via two unmanaged interfaces, if the interfaces go down, InCharge will not send any notifications. Users could be mislead to think that because the devices are connected via unmanaged interfaces, that the partition program was going to create two separate partitions. However, only unmanaged devices cause partition connectivity to break. Unmanaged
interfaces do not cause that.

For more information about partitions, see the InCharge IP Discovery Guide.

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