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 NCM: Why does Smarts NCM not issue a logout/disconnect command on disconnecting from devices? (329700)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 6734Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This article explains why Smarts NCM does not use explicit session disconnects when disconnecting from devices.

Smarts NCM does not issue a logout or specific disconnect command when disconnecting from a device.

Resolution

When Smarts NCM was designed with the current architecture, a number of factors were taken into account for the scalability and performance of the system. One such consideration was around the NCM <-> Device connection, and the decision was made and subsequently implemented that Smarts NCM would not issue explicit disconnect commands to devices after logging into the device to perform various tasks.

Implementing session disconnects would have required additional overhead to handle the operations, and would have manifested itself in performance related issues. The use of an explicit logout / exit / quit command from the device has never been present in NCM and / or the driver code base. A protocol disconnection only was used explicitly by the driver in product versions earlier than 4.x. There is also no provision for a driver routine to issue class-specific actions at the point a connection is torn down.

Efficiencies within NCM have been evaluated and implemented with NCM 4.x, session caching was introduced with the aim to reduce the overhead of connection setup and tear-down, which keeps a connection up for a configurable period so that subsequent communications may proceed (in effect) immediately. The best example of the efficiencies of session caching comes in when there is a device pull for multiple configuration units, where each type has a public entry point in the associated driver code. Without session caching, additional delay would be imposed for the disconnect / reconnect activities. A driver has no knowledge beforehand of how many operations will be required of it in fulfilling a job task; this is consistent with the reduction of business logic on the network-facing side.

Device capabilities ultimately define the communication process / methodology as there are a few device classes that permit only a single session at a time; in general they are written to use the original approach of explicit setup and teardown, the mechanics of which are handled in C++ code. Nonetheless they do not issue logout commands either.

Explicit disconnects are often done prior to a device reboot or after rolling account credentials, but again, that is driver-specific in its use.

Implementing explicit session disconnects would have far reaching consequences within the NCM architecture and as such, is not something that is under consideration for implementation.

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 - NCM

Take Our Survey

Support Assistant