Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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: How do I adjust the timing of the console timeout "warning" message in NCM 9.4 thru NCM 9.5? (520280)

Last Updated: 5/29/2020Categories: How toTotal Views: 2452Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

The Smarts NCM console will timeout after a certain period of user inactivity, at which point the user session will end and the user will need to login to the Smarts NCM console again. A console timeout "warning" message can be configured to appear before the console timeout occurs to alert users that the Smarts NCM console is about to timeout.
The following sections of this solution article explain how Smarts NCM calculates the timing of this console timeout warning message, and how to configure the timing for when the warning message will display.

How NCM calculates console timeout warning message?
The timing when the Smarts NCM console timeout "warning" message will appear is calculated by Smarts NCM based on the timeout period configured for the console. For example, if the Smarts NCM console timeout is set to 28800 seconds (8 hours) and the timeout warning value is set to 6000 seconds (1 hour and 40 minutes), the warning message would be displayed 1 hour and 40 minutes before the 8 hour timeout occurs (after 6 hours and 20 minutes of user inactivity). So, if you wanted the console timeout "warning" message to appear 30 minutes before the console timeout ended the user session, you would need to configure the timeout warning message to a value <Configured console timeout value> - 1800 (seconds).

IMPORTANT! The value configured for the console timeout warning MUST NOT be set to a value greater than the console timeout value or to a negative value.

Configuring the timing of the Smarts NCM console timeout warning message
Configure the timing of the Smarts NCM console timeout warning message can be managed from two separate locations, the database and JMX console:

Database:
1. Login to Database Server as root and execute below command:
su - pgdba -c 'psql voyencedb voyence'
Enter Database Password.

2. To view the current value, run the following query:

SELECT name, value, default_value from cm_config_item where name='com.powerup.configmgr.server.security.login.authentication_cache_timeout_warning';

3. To set changes, run the following command in the database.

update cm_config_item set value=<required_value> where name='com.powerup.configmgr.server.security.login.authentication_cache_timeout';

Ex: If the new value to be set is 1800, the query would be:

update cm_config_item set value=1800 where name='com.powerup.configmgr.server.security.login.authentication_cache_timeout';

Note that the 'value' will over write the 'default_value'.

JMX Console:
To adjust the warning timeout in the JMX console, follow the directions below to make the changes:

1. Login to jmx console by accessing following URL:
https://<NCM IP address>:8880/ncm-webapp/
Enter your NCM Application Server IP in the above link. Default username/password is jmx-user/sysadmin

2. In the navigation tree, drill into :

servers > 0 > domains > com.powerup.configmgr.server.config.jmx > mbeans > name=VoyenceControlConfig,type=JMXSystemConfig

Scroll down under operations and select setConfigItem you should see the following below:

4. Set the parameters as it follows:
java.lang.String p1 = config.server
java.lang.String p2 = com.powerup.configmgr.server.security.login.authentication_cache_timeout_warning
java.lang.String p3 = 3600 (or Any value, currently 1800)

5. Click on "execute" to set the values
6. Select the saveAll() operation from the list.

7. Click on  to save the changes and it will show "Config items are saved" indicating that it was successful.

Log out and back in again for the new settings to take effect

Note that editing these default settings while having NCM to authenticate with TACACS's, RADIUS, or RSA token systems may cause NCM authentication to fail.

Related Information

The steps in this article apply for NCM 9.4 thru NCM 9.5, it does not apply for NCM 9.1 thru NCM 9.3.
For NCM versions 9.1 thru 9.3, refer below KB:
https://support.emc.com/kb/317590 - How do I adjust/configure the timing of the console timeout "warning" message in NCM 9.1 thru NCM 9.3?

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