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 : How do I adjust the console timeout period for NCM 9.4 thru NCM 9.5? (517723)

Last Updated: 5/29/2020Categories: How toTotal Views: 2927Language:
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. The following section of this solution article explains how to configure the timing for the NCM console timeout.

To configure the Smarts NCM console timeout period, do the following:
This can be completed in three separate locations - JMX Console, an XML file and the Database.
Note - Editing these default settings while having NCM to authenticate with TACACS's. RADIUS, or RSA token systems may cause NCM authentication to fail.

First location:

Edit the JMX console as will modify the "value" setting in the database and it will take precedence over the "default_value" in the database. This is should not be edited and normally there is no "value" setting in the database by default. See the screen shot below: (To view the settings in the database, refer to KB https://support.emc.com/kb/517776.)

Follow the directions below to make the change using the JMX console:

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

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(java.lang.String,java.lang.String,java.lang.String) you should see the following below:

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
java.lang.String p3 = 3600 (or Any value, currently 1800)

Click on Execute to set the values

Select the saveAll() operation from the list.

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.

Second location:

Editing the $VOYENCE_HOME/ncmcore/webapps/ncm-webapp/WEB-INF/classes/system-config.xml file will edit the "default_value" in the database. Refer screen shot below:

Follow the directions below to make the change by editing the system-config.xml file.

Log into the Application Server user root privileges.

Set the environmental variable by running the command: source /etc/voyence.conf

Navigate to $VOYENCE_HOME/ncmcore/webapps/ncm-webapp/WEB-INF/classes/ directory.

Open system-config.xml file

Locate or search for the line:

<name>com.powerup.configmgr.server.security.login.authentication_cache_timeout</name>
<editable>true</editable>
<defaultValue>1800</defaultValue>

Edit the 1800 between the brackets to your desired value.

Save the and exit the file.

Run the following command to restart services for the new settings to take in effect: service vcmaster restart

Third Location

1. Login to Database Server as root and execute below command:

su - pgdba -c 'psql voyencedb voyence'

Enter Database Password.

2. To view the settings the Database, run the following query below:
Note - The "value" setting will take precedence over any value in the "default_value" field.

SELECT name, value, default_value from cm_config_item WHERE NAME='com.powerup.configmgr.server.security.login.authentication_cache_timeout';

3. To edit the default_value run the following command:

UPDATE cm_config_item set default_value=1800 WHERE NAME='com.powerup.configmgr.server.security.login.authentication_cache_timeout';

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/306580 - Smarts NCM: How do I adjust/configure the console timeout period for 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