EMC Smarts Network Configuration Manager Version · PDF fileEMC Smarts Network Configuration...

README

P/N 302-002-221REV 01

This document contains supplemental information about EMC Smarts Network Configuration Manager Version 9.4.0 Patch 5. Topics include:

◆ Revision history ........................................................................................................ 2◆ Patch description ...................................................................................................... 2◆ New features and changes ........................................................................................ 3◆ Fixed problems ......................................................................................................... 4◆ Environment and system requirements ..................................................................... 7◆ Known problems and limitations............................................................................... 7◆ Technical notes ....................................................................................................... 13◆ Documentation errata ............................................................................................. 14◆ Installing NCM 9.4.0 Patch 5 ................................................................................... 15◆ Uninstalling NCM 9.4.0 Patch 5 ............................................................................... 18◆ Troubleshooting and getting help............................................................................ 21

EMC® Smarts®

Network Configuration ManagerVersion 9.4.0 Patch 5

Readme

August, 2015

Revision history

Revision history

The following table presents the revision history of this document:

Revision Date Description

Product versioning and naming

◆ The EMC Smarts Network Configuration Manager Version 9.4.0 Patch 5 is the fifth patch release

after Version 9.4.0. The Network Configuration Manager patch numbering is consistent with

entire Smarts portfolio.

◆ The Network Configuration Manager is part of Smarts product portfolio that also contains IP,

SAM, MPLS, VoIP, ESM and NPM products, and has a separate patch readme document.

Patch description

A patch provides one or more fixes to an EMC Smarts product. A patch can only be applied to the specific major or minor release and Service Pack of the particular product for which it is intended; this is called the product’s baseline.

01 August, 2015 First release of EMC Smarts Network Configuration Manager Version 9.4.0 Patch 5

2 EMC Smarts Network Configuration Manager Version 9.4.0 Patch 5 Readme

New features and changes

New features and changes

This release includes important new features and changes to the existing features.

◆ “New features and changes in Patch 5” on page 3



New features and changes in Patch 5

The Patch 5 release contains no new features and changes.


The Patch 2 contains the following enhancements and changes:

◆ “Integration with EMC M&R” on page 3

Integration with EMC M&R

Integration with EMC M&R has changed and there is a different procedure for enabling "Certificate monitoring" feature in NCM Solution pack.

Follow the instructions provided in the SolutionPack for EMC Network Configuration Manager 2.0.3 Summary Sheet for Configuring Certificate Monitoring reports with NCM server running 9.4.0.2.


The Patch 1 release contains no new features and changes.

EMC Smarts Network Configuration Manager Version 9.4.0 Patch 5 Readme 3

Fixed problems

Fixed problems

This section describes the fixed problems addressed by the patch.

Table 1 Fixed problems

Issue number Symptom Fix description Version fixed

IS-383971813922

While changing the passwords using password-change.pl utility, Current passwords are not being asked and also the utility accepts simple passwords as well.

password-change.pl utility has been modified to ask the Current Password and validate the same before asking for the New Password. Also it will not accept simple passwords and entered password should have one 8 characters in length, upper and lower case letters, numbers and special characters. Help is also added for the utility password-change.pl –h or password-change.pl –help

For Internal users system, controlDaemon and int_mod_user passwords will be auto-generated.

Patch 5

IS-393872045486

Discovery of a large number of devices causes device server restart and SNMP to crash

Issue is resolved by making SNMP threads re-entrant.

Patch 5

IS-3701 P&S: Performance degraded observed in 9.4 Patch 2 while login to NCM UI initial screen.

Code has been modified to improve the performance

Patch 2

IS-2867 P&S: Performance degrade is observed in 9.4 J2EE APIs when compared to 9.3


Patch 2

IS-2866 P&S: Performance degrade is observed in 9.4 WS APIs when compared to 9.3


Patch 2

IS-267168378800

Push Job Fails, using Prompt on Manual Execute When credentials are passed from the UI made sure that e_salt key is added for encrypting the credentials, if it’s not there.

Patch 2

IS-374771111378

Discovery of a large number of devices causes device server restart.

Changes has been made to remove the corrupted session handlers from the ssh session cache. This will ensure that there are no further interactions with the device using the corrupted session.Note: DSR 20 HF3 or above must be installed after upgrading to NCM 9.4.0 Patch 2 for the complete fix.

Patch 2

IS-339170707036

Report Advisor not allowing filtering by views Changes have been made to get all the views under a particular network in the RA settings window, so that user can filter the views in a network.

Patch 2

IS-359870530476

Device Server Restart Issue Issue is resolved by making SNMP threads re-entrant.

Patch 2

IS-361671182872

Transformer user not created as UID 514 already in use

Ensured that the transformer user is allocated a random UID by the Linux rather than a static UID i.e 514.

Patch 2

IS-362771105464

NCM client has a caching issue, where it sometimes happens that a new policy will show the area selection of the previous open policy

Made the buffered listener to non-buffered so that it always shows the new policy selection.

Patch 2

IS-359971106246

The output of cmstatus is partly broken. Irrelevant data from the the cmstatus output has been removed and only relevant data (Summary and Details) are processed and displayed.

Patch 2


Fixed problems

IS -252368803138

NCM UI will not launch if it’s installed on the server not having the internet connectivity

Bundled the required dtd file for NCM Core to work.

Patch 1

IS-2569 68880558

NCM and RA UI will not launch if NCM and RA servers are installed in the dark site.

Bundled the required dtd file for NCM Core to work. For RA changed the applicationContext.xml to use the same versions of XSD files which are bundled within the binaries.

Patch 1

IS-274069394990

NCM 9.4 RA fresh install fails to launch Changed the applicationContext.xml to use the existing version of the XSDs which are bundled with the binaries.

Patch 1

IS-307369913748

NCM Smarts adapter is not able to authenticate and throws error "ERROR Public API Connection is DOWN" in the log file.

NCM adapter installed in dark site setup, the spring xsd schema files are now referred from the classpath instead of referring it from the internet.

Patch 1

IS-210567340504

Cfwrite.cgi binary can be invoked through an URL which causes infraDb database to be reset thus leading to a severe security issue.

Cfwrite.cgi now ignores the request if invoked through the URL thus ensuring no update to the infraDb database.

Patch 1

IS-253468806502

Healthcheck functionality broken due to cmstatus binary not having enough permissions on DS instances.

Cmstatus file has been given enough permissions such that the DS would invoke it to send the results to AS so that the healthcheck page shows the results.

Patch 1

IS-263269172140

WS enforcePoliciesOnDevices(String jobName) API call was broken in 9.4

Included the code in the server side to make WS Api enforcePolicies(String jobName) to work.

Patch 1

IS-2633 69172508

WS APIs will take more time for giving the results

Enabled the lazy loading made other code changes

Patch 1

IS-265469230242

Copy the Automation Library Item folder from one network to another does not happen.

Modified the code to copy the folder correctly. Patch 1

IS-287369236222

9.4 NCM javadoc had getReadOnly and getReadWrite APIs which were not documented

The APIs getReadOnly and getReadWrite are documented as internal APIs in javadoc.

Patch 1

IS-253868902606

When invoked via Browser Axis Happiness Page shows system usernames and passwords

Removed the happyaxis.jsp page from the NCM deployment as this is not required for NCM.

Patch 1

IS-2661 Set a filter in regex test and do complaince audit. Remove the filter in the regex test and made it to default while auditing throws an error.

Modified the code to avoid the error when the filter sets to default in regex test

Patch 1

IS-241568363202

Two regex tests are looped by one test referring the another test variable. The test variable is resolved to a value. If this resolved value is present in the config file multiple times, while doing compliance audit, then this results in OutOfMemory error because of looping multiple times.

Resolved the code to look for the value correct number of times and avoid the looping. Now the compliance audit will not throw OutOfMemory error when the resolved value present in the config file multiple times.

Patch 1

IS-232167858850

A user was not able to generate custom self signed certificate since NCM ships with its own self signed certificate.

New tool has been provided to generate a custom self signed certificate Tool: $VOYENCE_HOME/tools/ssl/ssl-utility-self-signed.pl

Patch 1




Fixed problems

Note: The Patch 1 contains additional 52 problems fixed and Patch 2 contains additional 31 problems fixed.

IS-2623 Following DISA Goals requires changes in the rule definition

DISA STIG NET0240DISA STIG NET0440DISA STIG NET0470DISA STIG NET0600DISA STIG NET0812DISA STIG NET0820DISA STIG NET0890DISA STIG NET1639DISA STIG NET1665DISA STIG NET1660DISA STIG NET-NAC-012

The required changes are made in the rules. Patch 1

IS-267369346376

Scheduled Autodiscovery job failed on NCM 9.4 installation

When the prompt user option is enabled, there were 2 different hibernate sessions involved to save the job details. Fixed the issue to use the same hibernate session.

Patch 1

IS-275669366566

Email Notifications will not be sent to users when the job Status changes

Modified the code to make it work Patch 1




Environment and system requirements

Environment and system requirements

EMC Smarts Network Configuration Manager Installation Guide provides information on environment and system requirements.

Prerequisites for installing the patch on Windows platform

1. Install the following Microsoft Visual Studio libraries on Windows platform:

• Microsoft Visual C++ 2005 SP1 Redistributable Package MFC Security Update

• Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)

2. Install the patch software.

Both, Network Configuration Manager and Report Advisor must be running and accessible when the patch is being installed.

Known problems and limitations

The following problems and limitations are known for the Network Configuration Manager Version 9.4.0 Patch 5 release:

◆ “Core file observed during NCM patch installation” on page 8

◆ “SMTP server settings gets reset to default values” on page 8

◆ “NCM UI on Chrome will not launch with Java 1.8 update 45” on page 8

◆ “Version Number is not shown properly when latest DSR is installed before the NCM 9.4.0 Patch 2” on page 9

◆ “Unable to launch NCM after uninstalling a NCM patch” on page 9

◆ “Unable to launch NCM after uninstalling a NCM patch” on page 9

◆ “Credentials are not prompted on Manual Execute for 'Submit and then Approve' sequence” on page 9

◆ “Deleting attribute query under attribute test is failing” on page 10

◆ “Unable to launch sysadmin console in secure mode on Windows” on page 10

◆ “Contextual Launch: Enabling autoLogin” on page 10

◆ “API getAllUnmanagedOpsDevices return value” on page 10

◆ “Email notifications not sent” on page 10

◆ “Telnet proxy not working in windows” on page 11

◆ “Wrong message shown in UI while accessing deleted WorkSpace” on page 11

◆ “Unable to save standard” on page 11

◆ “MSA User Password change does not accept a set of special characters” on page 11

◆ “ssl-utility-self-signed.pl file refers to JBoss paths instead of Spring” on page 11



◆ “String ‘if’after text box under flat file module” on page 12

Core file observed during NCM patch installation

IS-4429

Issue: While installing NCM patch on device server if jobs are in running state, sometimes commmgr process creates the core dump. This is due to the NCM service restart during the patch installation.

Resoultion: There is no resolution. This issue is inconsistent and there is no functionality impact.

SMTP server settings gets reset to default values

IS-3434

Issue: SMTP server settings gets reset to default values after upgrading to NCM 9.4.0 Patch 2.

Resoultion: User will have to configure the SMTP server settings again.

NCM UI on Chrome will not launch with Java 1.8 update 45

IS-3411

Issue: NCM UI not launching on Chrome if you have Java 1.8 update 45 on client

Resoultion: This is a known issue in Google Chrome as the deprecation of NPAPI support in Chrome.

References

https://code.google.com/p/chromium/issues/detail?id=477112

http://blog.chromium.org/2014/05/update-on-npapi-deprecation.html

https://www.chromium.org/developers/npapi-deprecation

Workaround:

Type chrome://flags in the browser's address bar and hit enter.

Search for chrome://flags/#enable-npapi on the page. Or, load it directly.

Enable it with a click on the link.

Restart the browser.

You may re-enable using the chrome://flags switch as described but support is scheduled to be removed in September with Chrome 45.



Version Number is not shown properly when latest DSR is installed before the NCM 9.4.0 Patch 2

IS-3863

Issue: Version Number will not be shown properly when latest DSR is installed before the NCM 9.4.0 Patch 2

Resolution: Install the NCM Patch first and then the DSR HF.

Unable to delete workspace even if user has delete permissions

IS-3505

Issue: With only Delete check box selected, unable to delete the workspace.

Resolution: Select Edit and View check box along with Delete check box to delete workspace which is associated with devices.

Unable to launch NCM after uninstalling a NCM patch

IS-3865

Issue: User is unable to launch NCM and observes the exception "java.io.IOException: Keystore was tampered with, or password was incorrect" in catalina.out.

This can occur if a user had changed the voyence-ssl.keystore password after installing a patch. Then if the user uninstalls the patch the keystore password will reset to default. Customer will need to change the password again.

Resolution: Follow below steps to change the voyence-ssl.keystore password

1. Open $VOYENCE_HOME/ncmcore/conf/server.xml

2. Search for the below line and change the password to the one which was used to create the voyence-ssl.keystore

keystorePass="change management"

3. Save it and ‘service ncm-as restart’ to restart NCM ser vice.

Credentials are not prompted on Manual Execute for 'Submit and then Approve' sequence

IS-3491

Issue: Crendetials are not prompted on Manual Execute for 'Submit and then Approve' sequence. It's inconsistent.

Resolution: Before clicking on Manual Execute refresh the screen or wait for few seconds.



Deleting attribute query under attribute test is failing

SND-2143

Issue: Deleting attribute query under attribute test is failing.

Create a attribute test and under it, create a attribute query. Now delete attribute query only under attribute test. The Deletion fails.

Resolution: Delete the entire attribute test to delete attribute query.

Unable to launch sysadmin console in secure mode on Windows

IS-3675

Issue: Unable to launch sysadmin console in secure mode on Windows.

Contextual Launch: Enabling autoLogin

IS-3160

Issue: Enabling autoLogin in the powerup.jnlp of the server does not reflect on the client side.

1. From the server side of the NCM application open powerup.jnlp from file /opt/smarts-ncm/ui/html

2. Modify from 'false' to 'true' the autoLogin feature <property name="jnlp.feature.autoLogin.enabled" value="true"/>

3. Launch the NCM application from client side.

4. Open the powerup.jnlp from notepad and view the value of the modified attribute.

5. The value remains "false"

Resolution: Use /opt/smarts-ncm/ncmcore/webapps/voyence/powerup.jnlp file instead of /opt/smarts-ncm/ui/html/powerup.jnlp

API getAllUnmanagedOpsDevices return value

IS-2899

Issue: API getAllUnmanagedOpsDevices returns discovered device name instead of display name.

Email notifications not sent

IS-3004

Issue: API registerForNotification fails to send email notification for the user after releasing the lock.



Telnet proxy not working in windows

IS-3218

Issue: Telnet proxy not working in windows

Resolution: Change line number 40 in the file $VOYENCE_HOME\tools\telnetproxy\runTelnet.pl

from

$CLASSPATH = "$VOYENCE_HOME\\tools\\telnetproxy\\".$SEP."$UI_CLIENT_JARS"."$VOYENCE_HOME\\tools\\telnetproxy\\TelnetProxyUtil.jar".$SEP."$VOYENCE_HOME\\tools\\telnetproxy\\resources".$SEP."$CONTROLDAEMON_JARS".$SEP."$APPSERVER_JARS";

to

$CLASSPATH = "$VOYENCE_HOME\\tools\\telnetproxy\\".$SEP."$UI_CLIENT_JARS"."$VOYENCE_HOME\\tools\\telnetproxy\\TelnetProxyUtil.jar".$SEP."$VOYENCE_HOME\\tools\\telnetproxy\\resources".$SEP."$CONTROLDAEMON_JARS".$SEP."$APPSERVER_JARS".";$VOYENCE_HOME\\ui\\html\\lib\\zebedee-9.0.0.0.jar";

Wrong message shown in UI while accessing deleted WorkSpace

IS-3213

Issue: Wrong message shown in UI of an NCM session when trying to access deleted WorkSpace deleted from another NCM session.

Resolution: Refresh the UI of an NCM session before accessing the WorkSpace.

Unable to save standard

IS-2863

Issue: If you link the tests first and then select device classes, you are not able save standard.

Resolution: Select device classes first and then link the tests.

MSA User Password change does not accept a set of special characters

IS-3082

Issue: MSA User Password change does not work when a set of special characters are involved.

ssl-utility-self-signed.pl file refers to JBoss paths instead of Spring

IS-3208

Issue: ssl-utility-self-signed.pl script has all the paths w.r.t JBoss instead of Spring.



Resolution: Please follow the below instructions for ssl-utility-self-signed.pl to create a custom self-signed certificates.

1. Open $VOYENCE_HOME/tools/ssl /ssl-utility-self-signed.pl file.

2. Search for the below line and comment it

$JBOSS_HOME=getJBossHome();

#$JBOSS_HOME=getJBossHome();

3. Replace the string "$JBOSS_HOME/server/vc-server/deploy/1vc.sar/voyence-ssl.keystore" to "$VOYENCE_HOME/conf/voyence-ssl.keystore" where ever it refers.

Example: @files = ("$VOYENCE_HOME/conf/server.crt", "$VOYENCE_HOME/conf/server.key", "$VOYENCE_HOME/conf/voyence-ssl.keystore", "$TOMCAT_HOME/conf/.keystore", "$VOYENCE_HOME/slm/conf/.keystore");

4. Replace the string "$JBOSS_HOME/server/vc-server/deploy/jbossweb.sar/server.xml" to "$VOYENCE_HOME/ncmcore/conf/server.xml" where ever it refers.

Example: chown($uid, $gid, "$VOYENCE_HOME/ncmcore/conf/server.xml");

5. save the file $VOYENCE_HOME/tools/ssl /ssl-utility-self-signed.pl.

String ‘if’after text box under flat file module

IS-3083

Issue: Under the flat file module, try to give input for the operations involving user input. the java.lang.String input has 'if' string mentioned on the screen after the text box.


Technical notes

Technical notes◆ “Technical notes for Patch 5” on page 13

Technical notes for Patch 5

◆ “Configuring WS API client for NCM 9.4.0.2” on page 13

◆ “NCM API changes deployment changes” on page 14

Configuring WS API client for NCM 9.4.0.2

Follow below steps to configure WS API client for NCM 9.4.0.2.

1. Log in to the NCM host and copy "$VOYENCE_HOME/conf/bundle.p12" to the destination machine where the WS API client is configured (for example, /opt)

2. On the destination machine, type the following command as one line and press Enter:

$JAVA_HOME/bin>keytool -changealias -keystore "/opt/bundle.p12" -alias 1 -destalias newalias –storetype pkcs12

3. Enter keystore password. (This is the PassPhrase entered during the NCM server installation.)

4. On the destination machine, type the following command as one line and press Enter:

$JAVA_HOME/bin>keytool -importkeystore -srckeystore "/opt/bundle.p12" -destkeystore "$JAVA_HOME/jre/lib/security/cacerts" -srcstoretype pkcs12

5. Enter the destination keystore password : changeit

6. Enter the source keystore password. (This is the PassPhrase entered during the NCM server installation.)

7. These results should display:

Entry for alias newalias successfully imported. Import command completed: 1 entries successfully imported, 0 entries failed or cancelled.

Note: If customer has 3rd party certificate installed instead of selfsigned certificate,Steps 1, 3, and 6 will be different as follows:

1. Log in to the NCM host and copy "$VOYENCE_HOME/tools/ssl/server.p12" to the destination machine where the WS API client is configured (for example, /opt)(server.p12 will be generated while installing 3rd party certificate using ssl utility for NCM 9.4.0.2)

3. Enter keystore password. (In case of 3rd party certificate, the same password has to be entered which was given during certificate installation)

6. Enter the source keystore password. (In case of 3rd party certificate, the same password has to be entered which was given during certificate installation.)


Documentation errata

NCM API changes deployment changes

1. The <VOYENCE_HOME>/ncmcore/webapps/Api is removed and the contents are merged with <VOYENCE_HOME>/ncmcore/webapps/ncm-webapp

2. The Api samples folder is located at: <VOYENCE_HOME>/ncmcore/webapps/ncm-webapp/samples

3. The JAVADOC folder is located at: <VOYENCE_HOME>/ncmcore/webapps/ncm-webapp/javadoc

4. For better API performance use the following WSDL URL:

WSDL URL: https://<serverip>:8880/ncm-webapp/services/ApiService?wsdl

Note: If the user doesn’t want to change the WSDL URL in all the WS client code, then follow the below steps to make the WS client work. There will be a performance degradataion with this option.

a. Open <VOYENCE_HOME>/ncmcore/webapps/ROOT/WEB-INF/urlrewrite.xml

b. Modify the below line:

from:

< to type="permanent-redirect" last="true">/ncm-webapp/services/ApiService?wsdl</to>

to:

< to type="redirect" last="true">/ncm-webapp/services/ApiService?wsdl</to>

c. ‘service ncm-as restart’ to restart NCM service.

5. The cc.remoting.servlet.base URL in J2EE samples folder is changed from https (secure) to http by default. This is to bring performance improvement for J2EE API calls.

To make the J2EE API calls secure, please follow below steps

1. Open <VOYENCE_HOME>/ncmcore/webapps/ncm-webapp/samples/J2EE/conf/config.properties file

2. Modify the below line

from

cc.remoting.servlet.base=http://localhost:8881/ncm-webapp/remoting/

to

cc.remoting.servlet.base=https://<NCM Server IP>:8880/ncm-webapp/remoting/

Documentation errata

The Patch 5 release contains no documentation errata.


Installing NCM 9.4.0 Patch 5


Installation instructions included in this section are for the Linux and Windows Server 2012 R2 operating environments.

This patch must be installed on all distributed Network Configuration Manager servers.

In the examples in both the Install and Uninstall instructions, [Product Directory] is used; however you must substitute [Product Directory] with your actual installation directory path.

◆ For Linux, you can determine your product installation directory by examining /etc/voyence.conf, and look for the text VOYENCE_HOME.

◆ For Windows, you can determine your product installation directory by accessing the Registry key at: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Voyence\Control\Configuration\VOYENCE_HOME.

Installation instructions for a cluster environment

Use the following steps to install this patch for a cluster environment on an application or device server.

On an application server (Linux)

Follow these steps:

Table 2 Steps for installing on an application server–Linux

Step Action Command

• bash NETWORK_CONFIGURATION_MANAGER_9_4_0_5_XX_Linux.bin

• Follow the prompts to install.

1 Stop the cluster. clusvcadm -d vc_cluster

2 Mount the disk. mount /dev/sdc1 [Product Directory]/dev/sdc1 is an example

3 Source /etc/voyence.conf . /etc/voyence.conf

4 Run the NCM 9.4.0 Patch 5 installer.

Notice: Where XX represents the build number.

5 Stop the vcmaster service. service vcmaster stop

6 Unmount the disk. umount [Product Directory](Isof [Product Directory] and kill processes if the drive is busy.)

7 Start the cluster. clusvcadm -e vc_cluster



On a device server (Linux)

Follow these steps:

Table 3 Steps for installing on a device server–Linux

Step Action Command

• service sysadmin stop• service voyence stop


• Follow the prompts to install.• Unlock the lockbox:

Installation instructions for a non-clustered environment

Use the following steps to install this patch for a non-clustered environment on Linux and Windows.

On an application, device, database, or combination server (Linux)

Follow these steps:

Table 4 Steps for installing on an application, device, or combination server–Linux

Step Action Command



1 Stop services Stop:

2 Source /etc/voyence.conf. ./etc/voyence.conf

3 Run the NCM 9.4.0 Patch 5 installer.

$VOYENCE_HOME/bin/cstdriver -lockbox $VOYENCE_HOME/data/lockb.clb -passphrase <passphrase>


1 Run the NCM 9.4.0 Patch 5 Installer for Linux.

For Linux:




On an application, device, or combination server (Windows)

Follow these steps:

Table 5 Steps for installing on an application, device or combination server–Windows

Step Action Command

On a remote or stand alone Report Advisor (Linux)

Follow these steps:

Table 6 Steps for installing on a remote or stand alone Report Advisor–Linux

Step Action Command



On a remote or stand alone Report Advisor (Windows)

Follow these steps:

Table 7 Steps for installing on a remote or stand alone Report Advisor–Windows

Step Action Command

1 Start the .exe file. Double-click the NETWORK_CONFIGURATION_MANAGER_9_4_0_5_XX_Windows.exe file.


2 The installer will load. Follow the prompts by clicking Next.

3 The installation is complete. Click Done when the install completes.

1 Run the NCM 9.4.0 Patch 5 Installer for Linux.

For Linux:

Unlock the lockbox (Linux):. /etc/voyence.conf$VOYENCE_HOME/cstbin/cstdriver -lockbox $VOYENCE_HOME/data/lockb.clb -passphrase <passphrase>


1 Start the .exe file. Double-click the NETWORK_CONFIGURATION_MANAGER_9_4_0_5_XX_Windows.exe file.


2 The installer will load. Follow the prompts by clicking Next.

3 The installation is complete. Click Done when the install completes.

4 Unlock the lockbox. perl unlockLockbox.pl


Uninstalling NCM 9.4.0 Patch 5

Verifying the installation

To verify the Network Configuration Manager 9.4.0 Patch 5 installation, follow these steps.

Table 8 Steps for verifying the installation

Step Action Command


The following sections provide details regarding uninstalling the patch from different environments.

◆ “Uninstallation instructions for a cluster environment–Linux only” on page 18

◆ “Uninstallation instructions for a non-clustered environment–Linux” on page 19

◆ “Uninstallation instructions for a non-clustered environment–Windows” on page 19

◆ “Verifying the uninstallation” on page 20

Uninstallation instructions for a cluster environment–Linux only

On an application server

Follow these steps:

1 Open the Help menu. Click the Help option on the Network Configuration Manager menu bar.

2 Open the About window. Select About. The About Network Configuration Manager window opens.

3 Verify the version of this release.

In Linux and Windows 2012 R2 platforms:The version of this release is 9.4.0 [Platform] Patch 5.

Table 9 Steps for uninstalling on an application server

Step Action Command

1 Stop the cluster. clusvcadm -d vc_cluster

2 Mount the disk. mount /dev/sdc1 [Product Directory]For example: /dev/sdc1

3 Navigate to the patch directory.

cd [Product Directory]/Hotfix/NETWORK_CONFIGURATION_ MANAGER_9_4_0_5/

4 Run the patch rollback script. perl rollbackHotfix.pl

5 Stop the vcmaster service. service vcmaster stop



On a device server

Follow these steps:

Table 10 Steps for uninstalling on a device server

Step Action Command

Uninstallation instructions for a non-clustered environment–Linux

On an application, device, or combination server

Follow these steps:

Table 11 Steps for uninstalling on an application, device, or combination server –Linux

Step Action Command

Uninstallation instructions for a non-clustered environment–Windows

On an application, device, or combination server

Follow these steps:

Table 12 Steps for uninstalling on an application, device, or combination server–Windows

Step Action Command

6 Navigate from the patch directory.

cd /

7 Unmount the disk. umount [Product Directory] (lsof [Product Directory] and kill processes if the drive is busy.)

8 Start the cluster. clusvcadm -e vc_cluster

Table 9 Steps for uninstalling on an application server

Step Action Command






2 Run the patch uninstall script.

perl rollbackHotfix.pl


Open a command prompt.Enter: cd [Product Directory]\Hotfix\NETWORK_CONFIGURATION_ MANAGER_9_4_0_5\




Verifying the uninstallation

To verify that Network Configuration Manager 9.4.0 Patch 5 is uninstalled, do the following:.

Table 13 Steps for verifying the uninstall

Step Action Command

1 Open the Help menu. Click the Help option on the Network Configuration Manager menu bar.

2 Open the About window. Select About. The About Network Configuration Manager window opens.

3 Verify the version of the previous release.

In Linux and Windows 2012 R2 platforms, the version of the previous release is 9.4.0 [Platform] [patch release number if previously installed].


Troubleshooting and getting help

Troubleshooting and getting help

EMC support, product, and licensing information can be obtained as follows:

Product information — For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at:

https://support.emc.com

Technical support — Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Copyright © 2009 - 2015 EMC Corporation. All rights reserved. Published in the USA.

Published August, 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).


http://support.emc.com

http://support.emc.com

EMC Smarts Network Configuration Manager Version · PDF fileEMC Smarts Network Configuration...

Documents

Transcript of EMC Smarts Network Configuration Manager Version · PDF fileEMC Smarts Network Configuration...