Docu58687 - Smarts SAM, IP, NPM, MPLS, ESM, OTM and VoIP Version 9.4.0.1 Cumulative Patch Readme Installation Instructions PDF

EMC Smarts
Version 9.4.0 Cumulative Patch

Readme
For IP, SAM, ESM, NPM, VoIP, MPLS, OTM
Readme
302-001-893
Rev 01
Copyright 1996 - 2015 EMC Corporation. All rights reserved. Published in the USA.
Published March 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).
EMC Smarts Version 9.4.0 Patch 1 Readme
Contents
The document contains information about the EMC Smarts Version 9.4.0 Patch 1
release (EMC Smarts 9.4.0.1).
Revision history ..................................................................................................... 5
Scope .................................................................................................................... 5
Patch description ................................................................................................... 5
Enhancements and changes .................................................................................. 8
Known problems and limitations .......................................................................... 15
Number of fixed defects and certified devices ...................................................... 16
Fixed Defects ....................................................................................................... 17
Certified devices .................................................................................................. 26
Environment and system requirements ................................................................ 29
Installation........................................................................................................... 32
Log files ............................................................................................................... 38
Reconcile user-modifiable files ............................................................................ 39
Uninstallation ...................................................................................................... 42
Troubleshooting and getting help ......................................................................... 44
Note: Patch Readme documents for a specific release are now consolidated into a
single document. Patch Readme documents as well as product
documentation for all releases are available as a download from EMC Online
Support (https://support.emc.com).
Contents
4 EMC Smarts Version 9.4.0 Patch 1 Readme
Revision history
This section presents the revision history of this document.

Table 1.
Scope
Revision history
Revision
Release Date
Description
01
Mar 2015
First release of EMC Smarts Version 9.4.0 Patch 1 Readme.
This section presents the product scope for this patch release.
Table 2.
Products released in this patch
Patch Release
Release date
Product (s) released in this patch
EMC Smarts Version

9.4.0 Patch 1
Mar 2015
IP, SAM, ESM, NPM, VoIP, MPLS, OTM
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 products baseline.
Note: Not all EMC Smarts 9.4.0 products are released when a patch becomes
available as it may apply only to a subset of products. For example, a patch
release may only apply to SAM and IP and not the rest of the products that
comprise Smarts.
Installation directory
In this document, the term BASEDIR represents the location where EMC Smarts
software is installed.
For UNIX, the default location is: /opt/InCharge/<productsuite>.
For Windows, the default location is: C:\InCharge\<productsuite>.
The <productsuite> represents the EMC Smarts product suite to which the product
belongs.
Optionally, you can specify the root of BASEDIR to be something other than
/opt/InCharge (on UNIX) or C:\InCharge (on Windows), but you cannot change the
name of the <productsuite> that is part of the BASEDIR.
The System Administration Guide provides additional information about the directory
structure of EMC Smarts software.
Installation overview
A patch installs files to the BASEDIR/smarts/local directory of the product. The
Installation software performs the following actions:
Backs up all files that are being replaced or merged.
Patch description
Merges changes from your current, user-modifiable configuration files into the
new versions of the files from the patch.
Displays a list of files that were merged and files that could not be merged due
to conflicts.
Displays the location of a log file that lists the results of merging the files.
Leaves user-modifiable files that are not updated by the patch untouched.
Note: If the original product was installed on one computer and then was copied to
another computer, the patch cannot be applied to the copied installation. You
must apply the patch to the computer with the original installation, and then
the results can be copied to another computer.
JRE requirement for Installation software
If the patch Installation software cannot find the correct version of the JRE, it displays
the message: A suitable JVM could not be found.
If this occurs, use the is:javahome option to specify the absolute path of the JRE
installed with the EMC Smarts software on one line. For example:
./setup-IP-linux-9_4_0_1-20150325-64BIT.bin -is:javahome BASEDIR/IP/_jvm
Or, if software is being installed in Wizard mode and an error message is thrown
saying Cannot find a compatible JVM. Select the java.exe file of the JVM from the
<BASEDIR>/_jvm/bin directory.
Note: The term BASEDIR represents the location where EMC Smarts software is
installed; for example, C:/InCharge/<productsuite>.
Install a new patch over an older patch
Patches are cumulative; each successive patch includes all of the fixes from any
previous patches. As a result, a newer patch can be installed on top of an older patch.
The patch number, which increments itself for each successive patch, indicates the
version. A patch with higher version number can be installed over a patch with a
lower version number.
The Installation software checks the version of the installed product and the version
to be installed at the beginning of its process. It will not allow an older version to be
installed on top of a newer version.
Upgrade after applying a patch

During an upgrade, the Installation software automatically uninstalls any applied
patches. Patch files, which are installed to BASEDIR/smarts/local, are removed if the
files are not modified by the user. The files that are modified are not removed and are
copied to <BASEDIR>/smarts/.local.bkp.<patch version> directory for manual
reconciliation.
Note: <patch version> is the complete version number for the patch, for example,
9.4.0.1
Patch description
Patch installation files
Install the patch on each host where the EMC Smarts product is running. Choose the
appropriate Installation software based on the operating system of the host.
IP:
setup-IP-linux-9_4_0_1-20150325-64BIT.bin
setup-IP-win-9_4_0_1-20150325-64BIT.exe
SAM:
setup-SAM-linux-9_4_0_1-20150324-64BIT.bin
setup-SAM-win-9_4_0_1-20150325-64BIT.exe
CONSOLE:
setup-CONSOLE-linux-9_4_0_1-20150324.bin
setup-CONSOLE-win-9_4_0_1-20150325.exe
ESM:
setup-ESM-linux-9_4_0_1-20150324-64BIT.bin
setup-ESM-win-9_4_0_1-20150325-64BIT.exe
MPLS:
setup-MPLS-linux-9_4_0_1-20150324-64BIT.bin
setup-MPLS-win-9_4_0_1-20150325-64BIT.exe
NPM:
setup-NPM-linux-9_4_0_1-20150324-64BIT.bin
setup-NPM-win-9_4_0_1-20150325-64BIT.exe
VoIP:
setup-VOIP-linux-9_4_0_1-20150324-64BIT.bin
setup-VOIP-win-9_4_0_1-20150325-64BIT.exe
OTM:
setup-OTM-linux-9_4_0_1-20150324-64BIT.bin
setup-OTM-win-9_4_0_1-20150325-64BIT.exe
Enhancements and changes
This patch release contains the following enhancements and changes:
General enhancements and changes
Enhancements and changes in IP
Enhancements and changes in SAM
Enhancements and changes in VoIP
Enhancements and changes in MPLS
Enhancements and changes in NPM
Enhancements and changes in ESM
Enhancements and changes in OTM
General enhancements and changes
This patch release does not contain any enhancement and changes.
Enhancements and changes in IP
Enhancements and changes in SAM

Enhancements and changes in VoIP

Enhancements and changes in MPLS

Enhancements and changes in NPM

Enhancements and changes in ESM

Discover and monitor storage devices grouped under Customer Groups
Management in EMC M&R
EMC M&R provides "Groups Management" feature where a service provider can group
storage devices base on customer names or site names and collect the data in to the
Database. It also provides group tagging information to retrieve collected data via
web service to the user. The customer specific groups can be configured under
"Customers" tab by visiting EMC M&R installation link as given below
http://<EMC_M&R_Host_IP_address>:58080/centralized-management/#/grouping
For more information on Groups management you can refer to EMC M&R user guides
or help document.
ESM 9.3 release onwards Server Manager provides EMC M&R specific filters and
properties in the XML configuration files for Brocade, Cisco, VNX and VMAX
SolutionPacks where it can fetch data from EMC M&R through web service API in
order to discover and monitor only those Storage devices that belong to a specific
customer defined in M&R instead of importing the entire M&R storage topology.
In order to configure ESM Manager to import devices assigned to a specific customer
in M&R, users need to specify the customer group name in <name>-sp-config.xml file
under $SM_HOME\conf\w4n\sp-xml-conf directory where Server Manager is
installed. The directory contains a configuration file for each SolutionPack: brocadesp-config.xml, vnx-sp-config.xml, vmax-sp-config.xml, cisco-sp-config.xml
For example: If there is a customer group name Pepsi under Groups Management
in EMC M&R, then entityFilter XML tags value inside <name>-sp-config.xml files
should be post-appended with & customer = '%Pepsi% string. Make
modifications to brocade-sp-config.xml, vnx-sp-config.xml, vmax-sp-config.xml,
cisco-sp-config.xml based on these devices being present in your environment.
Before:
<entityFilter>devtype =='FabricSwitch' & name=='OperStatus' & vendor ==
'Brocade' & isps = 'yes ' & (!vstatus | vstatus=='active')</entityFilter>
After:
<entityFilter>devtype =='FabricSwitch' & name=='OperStatus' & vendor ==
'Brocade' & isps = 'yes ' & (!vstatus | vstatus=='active') & customer =
'%Pepsi%</entityFilter>.
Note: Loading of these files from <BASEDIR>/local is not supported. Editing these files
via sm_edit is discouraged. These files are only present under
<SMARTS_BASE_DIR>\conf\w4n\sp-xml-conf. Make a manual copy of the files before
making any modifications.
Note: ESM Server needs to be restarted in order to load changes to these xml files.
Changing polling frequency for Brocade, Cisco, VNX and VMAX SolutionPacks
in EMC M&R 6.5u2
Server Manager (ESM) queries/polls device data from EMC M&R installation through
webservices for both discovery and monitoring. There are scenarios where user
wants to poll device data frequently i.e. less than the default polling interval that is
configured on EMC M&R SolutionPack. In such scenarios user need to modify the
required configuration files as given below.
Steps for frequent polling in VNX SolutionPack
Pre-requisite: VNX SolutionPack should be installed.
Procedure
1. Log in to the EMC M&R platform with your user name and password.
2. Select Administration.
3. Select Centralized Management.
4. Select Logical Overview> Collecting
5. Select Text-Collector::<VNX SolutionPack instance>
6. Edit the conf/textoutputcollector-vnxblock-frequentpoll.xml file under the
Configuration Files + Schemas section.
7. Look for the polling-interval tag:
<simultaneous-collecting>1</simultaneous-collecting>
<polling-interval>300</polling-interval>
<refresh>3600</refresh>
<collecting-group >group</collecting-group>
<source>VNXBlock-Collector</source>
Default value for polling-interval is 300 seconds. Change it to required polling
interval.
8. For each collecting-configuration in same file you will have to set timeout with
polling interval value which was set in previous step.
For example:
<collecting-configuration name="VNXBLOCK-FREQUENTPOLL-DISKS"
timeout="120">
Set the timeout=120 if you had chosen the polling interval as 120.
9. Click on Save.
10. Under Logical Overview> Collecting, Select Collector-Manager::< VNX
SolutionPack instance>.
11. Edit the conf/collecting.xml, as below
Go to line
<collector enabled="false" name="VNXBlock-FrequentPoll" next="VNXCRFSERIALNB" config="Text-Collector/emc-vnx/conf/textoutputcollectorvnxblock-frequentpoll.xml" />
Set enabled='true'.
12. Click on Save.
13. Restart the collector, by clicking on Restart button.
Steps for frequent polling in VMAX SolutionPack
Pre-requisite: VMAX SolutionPack should be installed.
Procedure
5. Select XML-Collector:: <VMAX SolutionPack instance>
6. Edit the conf/xmlcollector-vmax-topo-fp.xml file under the Configuration

Files + Schemas section.
7. Change the polling interval and all the timeouts to the frequent polling period
(set polling interval to below tags).
For timeout="300" in <collecting-configuration tag.
For <parameter name="data-timeout"> (set frequent polling interval in
<value>300</value>).
For <parameter name="connection-timeout"> (set frequent polling interval
in <value>300</value>).
Do the same for all collecting-configuration.
8. Uncomment the last collection-configuration. i.e. <collecting-configuration
id="VMAX-SE-TOPO-POOLS-CAPACITY" variable="source device parttype part
name" timeout="300" xmljob="com.watch4net.apg.v2.collector.plugins.xmlcollector.engine.NuxXmlJob
" max-threads="10">
9. Click on Save.
10. Under Logical Overview> Collecting, Select Stream-Collector:: <VMAX
SolutionPack instance>.
11. Edit the conf/streamcollector-vmax-topo-smi.xml file,
Uncomment the section:
<values context-key="FreeCapacity" type="counter">
<name>FrequentPollingFreeCapacity</name>
<unit>GB</unit>
</values>
12. Click on Save.
13. Edit the conf/parsers/smi/topology/parser-disks-fp.xml file, Change the
retrieving period to the frequent polling period
14. Click on Save.
15. Edit the conf/parsers/smi/topology/parser-ports.xml file, Change the
retrieving period to the frequent polling period.
16. Click on Save.
17. Edit the conf/parsers/smi/topology/parser-storage-pools-fp.xml file,Change
the retrieving period to the frequent polling period.
18. Click on Save.
After changing the files, restart the collector manager.
Note: Those changes will be lost if the SolutionPack is reconfigured or if a device is
added. We recommend a minimum frequent polling period of 5 minutes for an
average size array.
Steps for frequent polling in Cisco MDS SolutionPack
Pre-requisite: Cisco MDS SolutionPack should be installed.
11
1. Connect to Front-end host via ssh.

2. cd /opt/APG/Custom/WebApps-Resources/Default/device-discovery/snmpcapability-discovery-actions
3. Edit CISCO-MDS-NEXUS-PORTS-STATUS-discovery-actions.xml file
4. Insert default-polling-period="120" as shown below.
<tns:snmp-capability-discovery-actions-config capability-name="CISCO-MDSNEXUS-PORTS-STATUS" default-polling-period="120" load-factor="10"
xmlns:tns="http://www.watch4net.com/capability-discovery-action"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.watch4net.com/capability-discoveryaction ../snmp-capability-discovery-actions.xsd ">
5. Save and exit.
10. Select Collector-Manager::<brocade SolutionPack intance> and restart the
collector by click the Restart button.
11. Navigate to Administration in the EMC M&R platform.
12. Click Modules > SNMP Device Discovery.
A Dashboard appears where you add new SNMP collectors and devices as
well as add
devices to existing SNMP collectors. You can use a seed file to import a list of
device
definitions or manually add and configure devices.
13. To add an SNMP collector, click Collectors > New Collector.
Specify the required information for the SNMP collector.
Click Save.
14. To manually add Cisco MDS switch, click Devices > New Device.
On the New Device window, click each tab and type the required
information for the device.
Click Save on each tab.
15. Select the device that you just added and click the Approve action, which is
the checkmark.
16. On the Dashboard, do the following:
Click Import devices from all enabled device sources.
Click Discover capabilities from all approved devices.
Click Distribute all approved devices with capabilities on all enabled
collectors.
Click Send the generated configurations on all available collectors.
Green indicators appear on the Dashboard after successful executions of the
above functions.
Steps for frequent polling in Brocade FC Switch SolutionPack
Pre-requisite: Brocade FC Switch SolutionPack should be installed.

1. Connect to Front-end host via ssh.
2. cd /opt/APG/Custom/WebApps-Resources/Default/device-discovery/snmpcapability-discovery-actions
3. Edit BROCADE_FCSWITCH_PORT_STATUS-discovery-actions.xml file
4. Insert default-polling-period="120" as shown below.
<tns:snmp-capability-discovery-actions-config capabilityname="BROCADE_FCSWITCH_PORT_STATUS" default-pollingperiod="120" load-factor="20"
xmlns:tns="http://www.watch4net.com/capability-discovery-action"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.watch4net.com/capability-discoveryaction ../snmp-capability-discovery-actions.xsd ">
5. Save and exit.
10. Select Collector-Manager::<brocade SolutionPack intance> and restart the
collector by click the Restart button.
11. Navigate to Administration in the EMC M&R platform.
12. Click Modules > SNMP Device Discovery.
A Dashboard appears where you add new SNMP collectors and devices as
well as add
devices to existing SNMP collectors. You can use a seed file to import a list of
device
definitions or manually add and configure devices.
13. To add an SNMP collector, click Collectors > New Collector.
Specify the required information for the SNMP collector.
Click Save.
14. To manually add Brocade FC switch, click Devices > New Device.
On the New Device window, click each tab and type the required
information for the device.
Click Save on each tab.
15. Select the device that you just added and click the Approve action, which is
the checkmark.
16. On the Dashboard, do the following:
Click Import devices from all enabled device sources.
Click Discover capabilities from all approved devices.
Click Distribute all approved devices with capabilities on all enabled
collectors.
Click Send the generated configurations on all available collectors.
Green indicators appear on the Dashboard after successful executions of
the above functions.
13
Enhancements and changes in OTM
New configuration flags

This patch release does not contain any new configuration flags.
Known problems and limitations
Known problems and limitations

This patch release contains the following known problems and limitations:
General Known problems and limitations
Known problems and limitations in IP
Known problems and limitations in SAM
Known problems and limitations in VoIP
Known problems and limitations in MPLS
Known problems and limitations in NPM
Known problems and limitations in ESM
Known problems and limitations in OTM
General Known problems and limitations
Patch installer throws two error message boxes if Install Shield cannot find a suitable JVM.
Known problems and limitations in IP
This patch release does not include any known issues.
Known problems and limitations in SAM
Known problems and limitations in VoIP
Known problems and limitations in MPLS
Known problems and limitations in NPM
Known problems and limitations in ESM
Known problems and limitations in OTM
15
Number of fixed defects and certified devices
This section lists the number of defects fixed and devices certified (new and
updated) for this patch:
Table 3.
Product
Number of
fixed defects
Number of new
certifications
Number of updated
certifications
Patch release
DMT/Foundation
9.4.0.1
IP
15
73
9.4.0.1
SAM
9.4.0.1
NPM
9.4.0.1
ESM
9.4.0.1
MPLS
9.4.0.1
VoIP
9.4.0.1
OTM
9.4.0.1
Fixed Defects
Fixed Defects
This section describes the defect fixes in this patch:
Fixed Foundation defects applicable for all products in 9.4.0.1
Fixed IP specific defects
Fixed SAM specific defects
Fixed VoIP specific defects
Fixed MPLS specific defects
Fixed NPM specific defects
Fixed ESM specific defects
Fixed OTM specific defects

Table 4.
CQ/JIRA or SR
Ticket Number
IS-1819
66607340
Symptom
Security vulnerability
reported for FlexNet
License Manager
v11.9.0.0.
Description of Fix
Modified Files (all files in

BASEDIR/smarts/local/)
Upgraded FlexNet License

Server & client libraries to
version 11.10.1.0, which is
safe.
CVE-2011-1389 and
bin/system/lmgrd (.exe)
Patch
Release
9.4.0.1
bin/system/lmutil (.exe)
bin/system/sm_lmgrd92
(.exe)
lib/libsm_license.so Linux
CVE-2011-4135.
lib/libsm_dmtlic.so - Linux
lib\sm_license.dll Windows
lib\sm_dmtlic.dll -Windows
IS-144
64470330
False alerts are generated

when device attributes
are added using dynamic
modeling
When new properties are

added to a class using
dynamic modeling, the
attributes and relationships
indexes are shifted in that
class and all the child
classes. The attributes which
are referred in a computation
expression using the "->"
operator are grouped in a list
as indirect references.
Property indices for these
indirect references were not
getting updated after class
refinement. Hence the
monitoring tree would show
invalid/unrelated attributes,
lib/libsm_repos.so - Linux
9.4.0.1
lib/sm_repos.dll Windows
17
Fixed Defects
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix

Patch
Release
and the monitoring

computations would fail.
Fixed this, so that the
attribute indices are updated
after class refinement.

Table 5.
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix

9.4.0.1
The Fixed Foundation Defects

table lists issues fixed in the
patch.
IS-2223
66126622
NetworkConnection is
not built between
AggregatePorts
A new class
AggregateInterface was
introduced that is derived
from Interface. ITwill retain
the underlying IP relationship
which will be used for
creating a
NetworkConnection.
Patch
Release
rules/devstat/settings/thrsetting.asl
9.4.0.1
rules/discovery/ic-clearinterface-layering.asl
rules/Discovery/adapter/icetherChannel-perfInst.asl
rules/discovery/adapter/iclag-dot3ad.asl
rules/discovery/ic-post-stptrunk.asl
rules/Discovery/cisco/iclag-cisco-pagp.asl
conf/discovery/discovery/c
isco/DISCOVERY_CISCO.im
port
conf/health/settings.conf
lib/ sm_health.dll
Windows
lib/ libsm_health.so
Linux
lib/sm_icim.dll -- Windows
lib/libsm_icim.so Linux
IS-2572
68914338
Managing Cisco Nexus

with VRF and SNMPv3
IS-2698
IS-2177
Even though an IP
domain was started in
Enhance to walk the MIB :

1.3.6.1.4.1.9.9.468 (CISCOCONTEXT-MAPPING-MIB) to
fetch the context data
present in the cisco device.
conf/discovery/DISCOVERY
_CISCO.import
An new condition check was

introduced into discovery
_CISCO.import
9.4.0.1
rules/discovery/ic-ciscofind-context.asl
9.4.0.1
Fixed Defects
CQ/JIRA or SR
Ticket Number
67289066

Patch
Release
Symptom
Description of Fix
Availability Mode
(AMONLY),it generated
discovery errors related
to performance
discovery.
code to ensure that

performance related OIDs are
not probed if a domain is
started in AMONLY mode.
rules/discovery/ic-ciscoend-device-CPUProc.asl
IP domain is alerting on
unused Power Supplies
The Discovery code has been

changed to ignore Power
Supplies that are marked as
disabled in
hh3cEntityExtOperStatus
MIB.
rules/discovery/ic-huaweiH3C-health.asl
9.4.0.1
Voltage sensors on Cisco

Nexus 3K devices are
discovered as
temperature sensors
Check the entSensorType and

figure out the value
representation and create the
appropriate health
components (i.e the value
type is Celsius, then create
teperatureSensor and if the
value type is volt, then create
VoltageSensor.
_CISCO.import
9.4.0.1
Example error:
SWFE-E-EGETNEXT-While
getting next of OID
.1.3.6.1.4.1.9.9.109.1.1.
1.1.2, SNMPERESPONSE-No response
from 167.84.168.18,
port 161 SNMPETIMEOUT-Timed out; in
file
"/work/tancurrent/DMT9.3.0.0/116/smarts/snm
p/lib/SNMP_RequestsSe
nder.c" at line 1337
IS-2807
69545606
IS-2744
69368428
rules/discovery/ic-nexushealth.asl
Create health components

based on the unit value in
the entSensorType MIB,
components (i.e the value
type is Celsius, then create
teperatureSensor and if the
value type is volt, then create
VoltageSensor).
IS-2840
WiFi elements were not

discovered if IP Manager
was started in the AM
only mode.
The fix is to start the wifi

prober when the domain
manager is started in AM only
mode. This driver will create
and monitor WIFI
rules/discovery/discoveryinit.asl
9.4.0.1
19
Fixed Defects
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix

Patch
Release
9.4.0.1
components such
WirelessController,
WirelessAccessPoints,
AuthenticationServer and
WirelessClients.
IS-2843
69214978
IS-2540
68892656
The TemperatureSensor
is showing as
"UNKNOWN" for status
for a Ciena Switches
Modified the model code to

map the polled attribute to
the Status attribute for
TemperatureSensor.
lib/sm_health_ciena.dll -Windows
StateNotNormal alarm is
not generated for a
Juniper device when a
Power Supply is out of
chassis.
PowerSupply_Fault_JuniperE
nvMon instrumentation
class has been changed to
map NOSUCHINSTANCE to
CRITICAL status resulting in
StateNotNormal alarm. The
fix applies to all Juniper
devices using
PowerSupply_Fault_JuniperE
nvMon instrumentation
lib/libsm_health_juniper.so
Linux
lib/libsm_health_ciena.so
-- Linux
9.4.0.1
lib/ sm_health_juniper.dll - Windows
IS-2433
68025616
Port Channels that have IP

address on second VRF are
not being managed and
connections using these
port channels are not being
created.
Used the deviceID to form the

CDP connection if we fail to
identify the neighbor device
through VRF IPs.
rules/discovery/ic-cisco-postprocessor.asl
9.4.0.1
IS-1870
65823972
IPSEC Alerts showing wrong

status
The issue is because of the

missing short containment
driver definition missing for
many containment drivers that
discovers Ipsec tunnel
interfaces. The fix is to add
appropriate short containment
driver for those needed devices.
conf/discovery/DISCOVERY_CI
SCO.import
conf/discovery/oid2Type_Cisc
o.conf
9.4.0.1
IS-2474
68548850
Smarts IP Configuration
Manager will not push the
ProcessorUtilizationAlertMo
de setting to IP domain
The necessary attributes

including
ProcessorUtilizationAlertMode,
SmoothingForMemoryGroupUtili
zation,
MemoryGroupUtilizationThresh
old,
ProcessorGroupUtilizationThres
hold,
SmoothingForProcessorUtilizati
on,
SmoothingForProcessorGroupUt
ilization
and SmoothingForInsufficientM
conf/icf-c/push.conf
9.4.0.1
Fixed Defects
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix

Patch
Release
lib/sm_auto_discovery.dll
Windows
9.4.0.1
emory are being pushed to the

underlying domain managers
from the CM maanger under
Processor_Performance_Setting
class.
IS-2507
68694738
Following error message

appears in the server log
during discovery :
MR2MR_TRANS_BAD_PROPProp: PendingList; in file
"n:/DMT9.3.0.0/116/smarts/repos/
mr/transactions.c" at line
3560
MR2MR_TRANS_BAD_OBJECTObject: AD-Pending; in file
"n:/DMT9.3.0.0/116/smarts/repos/
mr/transactions.c" at line
3557 MRKEY_VALUE_NOT_FOUNDSpecified key value not
found in table; in file
"AD_Pending.c" at line
1393
A race condition may occur

where one discovery thread is
deleting a pending entry while
another thread is trying to
access it. The fix here is to
check if the entry persists
before accessing/deleting it.
lib/libsm_auto_discovery.so
Linux
IS-2708
CQ654354
62996904
Unable to discover SNMPv3

devices added to the
pendng list using dmctl
Added additional error handling

for condition described in IS2463.
lib/libsm_auto_discovery.so - Linux
lib/sm_auto_discovery.dll -Windows
9.4.0.1
IS-2657
68568216
Smarts IP domain is not

monitoring some interfaces
for performance during
discovery.
DuplexMode and Duplex Source

interface attributes were cleared
during discovery if they have
been discovered using
NEIGHBOR_MIB. The values are
set back during post
processing. In long discovery
cases the values may not be set
for hours. IP domain will not
monitor interfaces for
performance until the Duplex
value is set. The code was
changed to avoid resetting the
Interface
DuplexMode/DuplexSource in
pre-processing and
incorporated in the discovery
code itself.
rules/discovery/ic-ciscocdp.asl
rules/discovery/ic-cisco-postprocessor.asl
rules/discovery/ic-preprocessor.asl
9.4.0.1
21
Fixed Defects
CQ/JIRA or SR
Ticket Number
IS-2856
69578978
Symptom
Description of Fix
Warning messages in
discovery logs
Example:
[February 27, 2015 7:40:37
AM CST +920ms]
t@102284 Discovery #3
ASL_MSG-*-ASLPdiscovery/ic-teamedifhostvendorinfo.asl: ***
WARNING *** *** DEFAULT
*** line:
.1.3.6.1.4.1.232.11.2.2.12.
0|4956522D53384D502D4
34647505032|
Warning messages has been

added to be logged in the
debug mode.

Patch
Release
local/rules/discovery/icteamedif-hostvendorinfo.asl
9.4.0.1

Table 6.
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix

9.4.0.1

patch.
IS-953
62373896
IS-2107
67325824
IS-2720
69106668
Patch
Release
Failover -- When running

the failover actions
script to activate SAM A
from SAM B the console
did not follow the active
SAM
A deadlock situation during

failover was creating this
issue which has been fixed.
masterpiece.jar
9.4.0.1
Incoming NOTIFY traps

are cleared when they
should not have
The trap manager was not

considering the timestamp of
incoming traps and in some
cases could use previously
received CLEAR traps to clear
newly received NOTIFY traps.
The code has been changed
to consider the timestamp of
a trap.
icoi-trapd/
trap_mgr_parse.asl
9.4.0.1
Interface alerts active in

ESM are not being
passed through to SAM
This could happen in

situations when a
notification is notified by
multiple domain managers.
If one of the domain
managers disconnected the
notification in SAM would
change to WAS_ACTIVE
status and further updates
lib/libsm_ics_ems.so Linux
9.4.0.1
lib\sm_ics_ems.dll Windows
Fixed Defects
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix

Patch
Release
lib/libsm_storage_ext.so
Linux
9.4.0.1
from other domains would

not update the Source.
Notification processing logic
has been changed no to
mark notifications as
WAS_ACTIVE if there is
another source domain
listing in as ACTIVE
IS-2586
69082894
SAM 9.4 crashes when

MR_ManagedObject
refined through DM
Redefinition of the classes

already declared is removed
which was resulting in crash
while loading dynamically.
lib\sm_storage_ext.dll
Windows
lib/libsm_otm_sam.so Linux
lib\libsm_otm_sam.dll Windows

Table 7.
CQ/JIRA or SR
Ticket Number
Symptom

Description of Fix
patch.
Patch
Release
9.4.0.1

Table 8.
CQ/JIRA or SR
Ticket Number
Symptom

Description of Fix
Patch
Release
9.4.0.1

patch.

Table 9.
CQ/JIRA or SR
Ticket Number
Symptom

Description of Fix
patch.
Patch
Release
9.4.0.1
23
Fixed Defects
Fixed ESM specific defects

Table 10. Fixed ESM specific defects
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix

Patch
Release
Section Enhancements and

changes in ESM list the
enhancements in ESM.
9.4.0.1

patch.
IS-2366
IS-2592
67940014
69043310
ESM Topology Not Cleaned

Up After ESX Removal
The cleanup of ESX host is

handled properly. However the
ScsiLuns will stay in the
topology as it can still be there
in case if they are discovered
through Array.
local/rules/esm/esm-post.asl
9.4.0.1
IS-2882
Following Java NULL

pointer exceptions are
thrown while discovering
VMAX, VNX, Brocade and
Cisco MDS switch data.
This fix here is to handle

exceptions when W4N sends
any invalid data.
classes/esm_vcenter.jar
9.4.0.1
[March 4, 2015 6:22:01

AM EST +544ms] t@4388
platform
MAIN_MSG-*-STDFD_ERRstderr:
java.lang.NullPointerExcep
tion
[March 4, 2015 6:22:01
AM EST +544ms] t@4388
platform
MAIN_MSG-*-STDFD_ERRstderr:
at
com.smarts.w4n.w4nData
Source.w4nXMLManagem
ent.XMLDataMgrImplemen
t.getAllElementsName(XM
LDataMgrImplement.java:
49)
at
com.smarts.w4n.discovery
.storage.StorageDiscovery.
startDiscovery(StorageDisc
overy.java:70)
at
.common.W4NDiscoveryM
anager.startSolutionPackD
Fixed Defects
CQ/JIRA or SR
Ticket Number
Symptom

Description of Fix
Patch
Release
iscovery(W4NDiscoveryMa
nager.java:117)
at
.common.W4NDiscoveryM
anager.initiateDiscovery(W
4NDiscoveryManager.java:
96)
at
.common.W4NDiscoveryPr
obe.invoke(W4NDiscovery
Probe.java:134)
at
com.smarts.java_probe.Pr
obeRunner.invoke(ProbeR
unner.java:69)
SND-1990
For Brocade Fabric some of

the relationships
mentioned below are not
created in ESM integration
with M&R 6.5 and vCenter
discovered
Addressed the logic issue and

now the relationship is created.
classes/esm_vcenter.jar
9.4.0.1
IP address that is type IPv4z

were not parsed according to
new standards and that lead to
the missing of pool-members
being created. Have enhanced
the logic to parse those types IP
address and create the Pool
members.
IPv4z type IP addresses were
not parsed according to new
standards. As a result, some of
the pool members were not
created. The code has been
enhanced to parse IPv4z IP
address and create the pool
rules/f5/ic-f5_esm-pools.asl
conf/esm/DISCOVERY_f5_ES
M.import
9.4.0.1
MemberPort
MemberPortLink
TraversedBy
In case of ESM and M&R
integration the following
relationships may not be
discovered for Brocade
Fabric: MemberPort,
MemberPortLink,
TraversedBy
IS-2838
69573044
F5 Pools are not

discovered and monitored
properly
25
Certified devices
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix

Patch
Release

Patch
Release
members.

Table 1.
CQ/JIRA or SR
Ticket Number
Symptom
Description of Fix
9.4.0.1

patch.
IS-2763
69424730
The TopologicalLink
Down problem does not
have the PTP LosEvent
as its impact.
Certified devices
Code changed to include the

LosEvent in the impact
lib/libsm_wdm_ng.so
Linux
9.4.0.1
lib\sm_wdm_ng.so
Windows
This section describes the devices certified and the certification impact in this patch:
Table 2.
Description of devices certified in the patch
CQ/JIRA or SR
Ticket
Number
Product
Symptom
Description of Fix

Patch
Release
N/A
N/A
N/A
N/A
N/A
N/A
Certification impact
This section lists the impacted drivers and SysOIDs as a result of certification
changes.
Table 3.
Certification impact
CQ/JIRA or SR
Ticket Number
Product
Impacted drivers
Impacted SysOIDs
Patch
Release
IS-2540
IP
Environment =
JuniperEnvMon:DeviceID
.1.3.6.1.4.1.2636.1.1.1.2.5
9.4.0.1
.1.3.6.1.4.1.2636.1.1.1.2.4
.1.3.6.1.4.1.2636.1.1.1.2.2
.1.3.6.1.4.1.2636.1.1.1.2.1
.1.3.6.1.4.1.2636.1.1.1.2.3
.1.3.6.1.4.1.2636.1.1.1.2.8
.1.3.6.1.4.1.2636.1.1.1.2.6
Certified devices
CQ/JIRA or SR
Ticket Number
Product
Impacted drivers
Impacted SysOIDs
Patch
Release
.1.3.6.1.4.1.2636.1.1.1.2.7
.1.3.6.1.4.1.2636.1.1.1.2.11
.1.3.6.1.4.1.2636.1.1.1.2.9
.1.3.6.1.4.1.2636.1.1.1.2.10
.1.3.6.1.4.1.2636.1.1.1.2.14
.1.3.6.1.4.1.2636.1.1.1.2.15
.1.3.6.1.4.1.2636.1.1.1.2.13
.1.3.6.1.4.1.2636.1.1.1.2.17
.1.3.6.1.4.1.2636.1.1.1.2.17.1
.1.3.6.1.4.1.2636.1.1.1.2.17.2
.1.3.6.1.4.1.2636.1.1.1.2.17.3
.1.3.6.1.4.1.2636.1.1.1.2.17.4
.1.3.6.1.4.1.2636.1.1.1.2.20
.1.3.6.1.4.1.2636.1.1.1.2.19
.1.3.6.1.4.1.2636.1.1.1.2.18
.1.3.6.1.4.1.2636.1.1.1.2.23
.1.3.6.1.4.1.2636.1.1.1.2.27
.1.3.6.1.4.1.2636.1.1.1.2.24
.1.3.6.1.4.1.2636.1.1.1.2.25
.1.3.6.1.4.1.2636.1.1.1.2.21
.1.3.6.1.4.1.2636.1.1.1.2.29
.1.3.6.1.4.1.2636.1.1.1.2.30
.1.3.6.1.4.1.2636.1.1.1.2.31
.1.3.6.1.4.1.2636.1.1.1.2.26
.1.3.6.1.4.1.2636.1.1.1.2.28
.1.3.6.1.4.1.2636.1.1.1.2.32
.1.3.6.1.4.1.2636.1.1.1.2.36
.1.3.6.1.4.1.2636.1.1.1.2.35
.1.3.6.1.4.1.2636.1.1.1.2.34
.1.3.6.1.4.1.2636.1.1.1.2.40
.1.3.6.1.4.1.2636.1.1.1.2.39
.1.3.6.1.4.1.2636.1.1.1.2.41
.1.3.6.1.4.1.2636.1.1.1.2.43
.1.3.6.1.4.1.2636.1.1.1.2.33
.1.3.6.1.4.1.2636.1.1.1.2.44
.1.3.6.1.4.1.2636.1.1.1.2.49
.1.3.6.1.4.1.2636.1.1.1.2.57
.1.3.6.1.4.1.2636.1.1.1.2.73
.1.3.6.1.4.1.2636.1.1.1.4.82.1
27
Certified devices
CQ/JIRA or SR
Ticket Number
Product
Impacted drivers
Impacted SysOIDs
Patch
Release
.1.3.6.1.4.1.2636.1.1.1.2.84
.1.3.6.1.4.1.2636.1.1.1.2.67
.1.3.6.1.4.1.2636.1.1.1.2.59
.1.3.6.1.4.1.2636.1.1.1.2.69
.1.3.6.1.4.1.2636.1.1.1.4.84.1
.1.3.6.1.4.1.2636.1.1.1.4.84.2
.1.3.6.1.4.1.2636.1.1.1.2.90
.1.3.6.1.4.1.2636.1.1.1.2.64
.1.3.6.1.4.1.2636.1.1.1.2.76
.1.3.6.1.4.1.2636.1.1.1.2.58
.1.3.6.1.4.1.2636.1.1.1.4.82.2
.1.3.6.1.4.1.2636.1.1.1.2.92
.1.3.6.1.4.1.2636.1.1.1.2.89
.1.3.6.1.4.1.2636.1.1.1.2.88
.1.3.6.1.4.1.2636.1.1.1.2.93
.1.3.6.1.4.1.2636.1.1.1.2.86
.1.3.6.1.4.1.2636.1.1.1.2.102
.1.3.6.1.4.1.2636.1.1.1.2.104
.1.3.6.1.4.1.2636.1.1.1.2.98
.1.3.6.1.4.1.2636.1.1.1.2.63
.1.3.6.1.4.1.2636.1.1.1.4.82.5
IS-2744
IP
HEALTH = Nexus-Entity
.1.3.6.1.4.1.9.12.3.1.3.377
9.4.0.1
.1.3.6.1.4.1.9.12.3.1.3.1060
IS-2843
IP
Environment
=
CienaLEOSChassis:Device
ID
.1.3.6.1.4.1.6141.1.78
.1.3.6.1.4.1.6141.1.79
.1.3.6.1.4.1.6141.1.77
.1.3.6.1.4.1.6141.1.80
9.4.0.1
Environment and system requirements
This section lists the supported operating systems and describes how to verify the
version number.
Supported operating systems and version number details

Table 4.
Product
VOIP
Supported operating systems and version number details
Supported operating systems
Red Hat Enterprise Linux 5.9 or later

64 bit, Red Hat Enterprise Linux
6.4 or later 64 bit, Red Hat
Enterprise Linux 7.0 or later 64 bit
linux_rhAS50-x86-64/206320000
Microsoft Windows Vista 32 /64
VOIP_SUITE: V9.4.0.1(140756), 24-Mar-2015

09:19:57 Copyright 1995-2015, EMC
Corporation - Build 3
CentOS 6.4 or later 64 bit, CentOS

7.0 or later 64 bit

From <BASEDIR>/smarts/bin/, type the following command:

./sm_server --version (Linux)
The following output is displayed
sm_server:
Additionally, for SAM Console:
linux_rhAS50-x86-64/206320000
IP_NETWORK_SUITE: V9.4.0.1(140773), 25-Mar2015 02:01:02 Copyright 1995-2015, EMC


7.0 or later 64 bit

Microsoft Windows Server 2012
R2 64 bit
bit, Microsoft Windows 7 32/64
bit
Foundation V9.4.0.1(140746), 23-Mar-2015

23:14:40 Copyright 1995-2015, EMC

R2 64 bit
The following output is displayed:

bit
SAM
sm_server:

R2 64 bit

bit
IP
Version number details
Foundation V9.4.0.1(140746), 23-Mar-2015

23:14:40 Copyright 1995-2015, EMC
sm_server:
linux_rhAS50-x86-64/206320000
SAM_SUITE: V9.4.0.1(140758), 24-Mar-2015
10:59:02 Copyright 1995-2015, EMC
Foundation V9.4.0.1(140746), 23-Mar-2015
23:14:40 Copyright 1995-2015, EMC
29

Product
MPLS
7.0 or later 64 bit
Console
sm_server:
linux_rhAS50-x86-32/206180000
SAM_CONSOLE_SUITE: V9.4.0.1(140754), 24-Mar2015 07:21:47 Copyright 1995-2015, EMC
Foundation V9.4.0.1(140746), 23-Mar-2015
23:14:20 Copyright 1995-2015, EMC


R2 64 bit
bit
NPM

7.0 or later 64 bit


R2 64 bit
bit
ESM

7.0 or later 64 bit


R2 64 bit
bit

sm_server:
linux_rhAS50-x86-64/206320000
MPLS_SUITE: V9.4.0.1(140755), 24-Mar-2015
07:45:28 Copyright 1995-2015, EMC
Foundation V9.4.0.1(140746), 23-Mar-2015
23:14:40 Copyright 1995-2015, EMC
sm_server:
linux_rhAS50-x86-64/206320000
NPM_SUITE: V9.4.0.1(140754), 24-Mar-2015
06:59:11 Copyright 1995-2015, EMC
Foundation V9.4.0.1(140746), 23-Mar-2015
23:14:40 Copyright 1995-2015, EMC

sm_server:
linux_rhAS50-x86-64/206320000
ESM_SUITE: V9.4.0.1(140758), 24-Mar-2015
11:16:13 Copyright 1995-2015, EMC
Product
OTM

7.0 or later 64 bit


R2 64 bit
bit

7.0 or later 64 bit
Foundation V9.4.0.1(140746), 23-Mar-2015

23:14:40 Copyright 1995-2015, EMC

sm_server:
linux_rhAS50-x86-64/206320000
OTM_SUITE: V9.4.0.1(140757), 24-Mar-2015
09:56:47 Copyright 1995-2015, EMC
Foundation V9.4.0.1(140746), 23-Mar-2015
23:14:40 Copyright 1995-2015, EMC
31
Installation
Installation
Install the patch using one of the following methods:
Apply patch using Wizard mode
Apply patch using CLI mode
Apply patch using Unattended (Silent) mode
Note: Administrative privileges are required to install a patch.
Apply patch using Wizard mode
Wizard mode provides a graphical interface to the patch Installation software.

Wizard mode requirements for UNIX systems
On UNIX systems, Wizard mode uses the X Window System to display the installation
wizard. The host on which you install the EMC Smarts software and the host where
you log on must be configured to run the X Window System. Before starting the
Installation software using the Wizard mode, verify that the X Window System is
running.
Run Wizard mode

1.
Run the appropriate setup command listed in Table 5. Replace xx with the
relevant product name, for example, IP, SAM, ESM, VOIP, MPLS, and NPM.
For exact name, check the Patch Installation Files section.
Table 5.
Setup command syntax for Wizard mode
Operating
system
Wizard setup command

syntax
Wizard setup command

syntax for the SAM Console
Linux
./setup-XX-linux9_4_0_1-2015032464BIT.bin
./setup-CONSOLE-linux9_4_0_1-20150324.bin
Windows
setup-XX-win-9_4_0_120150325-64BIT.exe
setup-CONSOLE-win9_4_0_1-20150325.exe
The Installation Wizard dialog box appears and closes. The Shutdown EMC
Smarts Programs dialog box and the Welcome screen appear.
You may need to point the Patch installer to the java location. (Click here for
more details).
2.
Click Next in the Welcome screen.

If you do not have administrative privileges, Next is disabled and a message
appears. Exit and restart the installation with administrative privileges.
3.
Read the license agreement, select I accept the terms of the license
agreement, and click Next. If you do not accept the terms, you cannot
complete the installation and must exit.
The Installation software detects all existing installations of the particular
product and displays them in the upgrade screen.
Installation
4.
Select the product to patch and click Next.

If there is only a single installation of the product, it is selected. The Installed
EMC Smarts services screen appears.
5.
If the Installation software detects services running from the install area, a
list of services that the Installation software has detected is displayed. Stop
each running service by pressing any key. Then click Next.
The Installation software then checks for any changes made to usermodifiable files. This check is performed only on files that will be updated
with new versions in the patch and the results are displayed in the Merge
Files screen. If there are no changes to user-modifiable files, this screen is not
displayed.
The Installation software will attempt to merge changes from the existing
user-modifiable files into the new versions of the files that are in the patch.
The Merge Files screen lists the files that were changed so that you are aware
of the scope of the merge:
A red x-mark indicates that a file was modified after the previous patch was
installed.
An orange exclamation point indicates that a file was modified before the
previous patch was installed.
6.
Choose whether to use merged files or the new files from the patch:
Select Merge and use the files to merge changes from existing versions of
the user-modifiable files into the new versions from the patch. These
merged files will be used when the products are restarted.
Unchanged versions of the new patch files are also installed, but they are
named with an extension that corresponds to the patch number. This
prevents the files from being used when the products are restarted.
The existing files are backed up into a directory that is named using the
version number of the previous patch release that was installed
(<BASEDIR>/smarts/.local.bkp.<previous_version_number>).
Select Merge but do not use the files to merge changes from existing
versions of the user-modifiable files into the new versions from the patch.
These merged files will be named with the extension .automerge and will
not be used when the products are restarted.
New, unmerged versions of the user-modifiable files from patch are also
installed and are named so that they will be used by the products when
they are restarted.
The existing files are backed up into a directory that is named using the
version number of the previous patch release that was installed
(<BASEDIR>/smarts/.local.bkp.<previous_version_number>).
Click Next.
7.
Verify the target installation directory and click Next.

The list of products to be installed will contain only the patch. At the bottom
of this screen, the total amount of disk space required for the patch is
provided so that you can verify that adequate disk space is available.
33
Installation
8.
Upon completion, the Installation Summary displays informational

messages including the confirmation of a successful installation and the
location of the log file for the automatic reconciliation and file merge. The
names of all merged files that contain conflicts are also displayed. Click
Finish to exit the installation.
9.
Reconcile the files with conflicts and review successfully merged files as
described in Reconcile user-modifiable files.
Apply patch using CLI mode
CLI mode provides a text-based method for invoking the Installation software. This
mode is intended for UNIX platforms with non-graphic (text-only) consoles. The CLI
mode installation follows the same process as the wizard mode but displays text on
the terminal screen and requires user responses on the keyboard.
Run CLI mode

1.
Change directory to the directory where you typically store patches, for
example, <BASEDIR> for your product suite.
2.
Type the setup command listed in Table 6 and then press Enter. Replace
xx with the relevant product name, for example, IP, SAM, ESM, VOIP,
MPLS and NPM. For exact name, check the Patch Installation Files section.
Table 6.
Operating
system
Setup command syntax for CLI mode

CLI setup command syntax
Wizard setup command syntax

for the Console
Linux
./setup-XX-linux-9_4_0_120150324-64BIT.bin -console
./setup-CONSOLE-linux9_4_0_1-20150324.bin console
Windows
setup-XX-win-9_4_0_120150325-64BIT.exe -console
setup-CONSOLE-win-9_4_0_120150325.exe -console
A welcome message with information about the installation appears.

You may need to point the Patch installer to the java location. (Click here for
more details)
User selections and navigation in CLI mode
During the patch installation process, at the end of each screen of text, you are
prompted with a set of options. For example:
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay
[1]
Select a choice by typing its number and pressing Enter.
Accept the default choice, indicated in brackets ([1] in the above example), by
pressing Enter.
To navigate between the steps, type a number key as listed in Table 7 and then press
Enter.
Installation
Table 7.
CLI mode navigation keys
Key
Operation
Next, continue to the next step
Previous, go back to the previous step
Cancel, terminates the install program
Redisplay, repeats the step
Accept the marked ([X]) menu choice
Other screens have different choices. For example when the license agreement is
displayed, the following prompt appears:
Press ENTER to read the text [Type q to quit]
Press Enter after reading each page. At the end of the license agreement, the
installation process displays the first of several menus.
Please choose from the following options:
[ ] 1 - I accept the terms of the license agreement.
[X] 2 - I do not accept the terms of the license agreement.
To select an item enter its number, or 0 when you are finished:
[0]
Each choice is numbered and has a pair of brackets. The default menu choice (2 in
this example) has an X in the brackets. Type the number of the desired selection and
press Enter. In the case of the license agreement, you must accept the agreement by
typing 1 and pressing Enter.
The screen is redisplayed with an X in the brackets next to the selected item. When
you are satisfied with the indicated selection, type 0 (zero) and press Enter.
The rest of the installation follows the same steps as the Wizard Mode but uses the
above method for selecting choices and navigating through the installation steps.
When the patch installation is complete, reconcile the configuration files as
Apply patch using Unattended (Silent) mode
Unattended mode installs the patch without user input or a response file. When
invoking the install program, specify the location of the product suite to be patched.
In order to invoke an unattended installation of the patch, type the appropriate setup
command from Table 8 or Table 9 for SAM Console and then press Enter. Replace xx
with the relevant product name, for example, IP, SAM, ESM, VOIP, MPLS and NPM. For
exact name, check the Patch Installation Files section.
35
Installation
Table 8.
Setup command syntax for unattended mode
Operating
system
Unattended setup command syntax

./setup-XX-linux-9_4_0_1-20150324-64BIT.bin -silent
-G replaceNewerResponse="Yes to All"
Linux
-P rpProduct.installLocation=<BASEDIR>
-W mergeSummaryPanel.choiceMergeResult={auto|manual}
setup-XX-win-9_4_0_1-20150325-64BIT.exe -silent
Windows
<BASEDIR> is the location where the EMC Smarts software is installed.

{auto|manual} specifies the merge operation. You must choose either:
auto will merge existing versions of the user-modifiable files with new versions that
are included in the patch. These merged files will be used when the products are
restarted. This is equivalent to Select Merge and use the files in Wizard mode.
manual will install and use the new versions of the user-modifiable files included in
the patch. Merged versions of the files will also be created and saved for review. This
is equivalent to Select Merge but do not use the files in Wizard mode.

You may need to point the Patch installer to the java location. (Click here for more
details).
Table 9.
Operating
system
Linux
Setup command syntax for unattended mode for SAM Console

./setup-CONSOLE-linux-9_4_0_1-20150324.bin -silent
Windows
setup-CONSOLE-win-9_4_0_1-20150325.exe -silent
<BASEDIR> is the location where the EMC Smarts software is installed.

{auto|manual} specifies the merge operation. You must choose either:
auto will merge existing versions of the user-modifiable files with new versions that are
included in the patch. These merged files will be used when the products are restarted.
This is equivalent to Select Merge and use the files in Wizard mode.
Installation
Operating
system
manual will install and use the new versions of the user-modifiable files included in the
patch. Merged versions of the files will also be created and saved for review. This is
equivalent to Select Merge but do not use the files in Wizard mode.

37
Log files
Log files
Table 10 lists the files that the Installation software creates during the install process.
Table 10. Patch report and log file locations
Name
Install log
Merged files log
Path
File Name
<BASEDIR>/smarts/setup/logs
Install.<patch
version>.log
C:\tmp (if install fails)

BASEDIR/smarts/setup/logs
install.merge.<patch
version>.log
Where <patch version> is the complete version number for the patch, for example,
9.4.0.1
Install log
The installer creates an Install log file listing all actions performed by the installation.
You need not read this file unless you suspect an installation failure.
If the installation process fails, the log files are located in a temporary directory, for
example /tmp or C:\temp. A non-zero status indicates a failure.
Merged files Log

This log lists the files in the BASEDIR/smarts/local directory structure that were
merged. For each merged file, the log lists the location and name of the file. If any file
cannot be merged due to conflicts, this is also noted. In addition, the log lists the
name and location for unmerged versions of all user-modifiable files that are
included in the patch.
Reconcile user-modifiable files
The Installation software is designed to preserve your changes to user-modifiable

files when installing new versions of these files. The Installation software does this by
analyzing the user modifiable-files to answer these questions:
For each new user-modifiable file in a patch, has the current version of the file
been changed?
If the current version was changed, do the changes conflict with changes in the
new version in the patch?
Existing changes to user-modifiable files are always automatically merged into new
files, but you control whether or not the files are used by making one of these
selections during installation:
Merge and use the files: If there are no conflicts between the changes in the
new file and the changes in the current version, the Installation software
combines the changes in to merged version of the user-modifiable file. The
merged version is named and placed in the location where the Manager can
load and use it.
If there are conflicts between changes in the new file and the changes in the
current version, then a conflict file (.<filename>.<patch version>.conflict)is
created that clearly indicates the issues so that you can evaluate them. In
addition, an unchanged version of the file from the patch is placed in the
location where the Manager can load and use it. Resolve issues in conflict files
section provides a procedure to resolve the conflicts.
Merge but do not use the files: All the new user-modifiable files included in the
patch are placed in the location where the Manager can load and use them.
These files do not include any changes from your current files.
The Installation software does combine changes from the current files with the
new files, but the changes are saved into merged versions that are named
using an extension (.automerge) so that the Manager will not use the merged
files. You can then review these automerge files and decide when to make
merged changes operational. See Rename and use Automerge files for this
procedure.
If there are conflicts between changes in the new file and the changes in the
current file, then a conflict file is created that clearly indicates the issues so
that you can evaluate them. See Resolve issues in conflict files for a procedure
to resolve the conflicts and use the files.
The Installation software also creates a backup of all the versions of the usermodifiable files to ensure that you will not lose any configuration data. See Backup
versions of user-modifiable files for a description of the backup files.
Note: In UNIX, the conflict and automerge versions of the user-modifiable files are
hidden files.
39
Backup versions of user-modifiable files
The Installation software always creates backup versions of user-modifiable files

included in the patch and all current versions of the files. Table 11 lists the purpose
and location of all user-modifiable files that the Installation software creates during
the install process and their locations.
Table 11. Purpose and location of backup files
Purpose of back up file
Path (from BASEDIR/smarts)
Example (from BASEDIR/smarts)
Preserve settings of the new

user-modifiable file in patch
/local/<directory>/.<filename>.<
patch version>
/local/conf/.discovery.conf.9.4.0.1
Preserve your changes in the

current user-modifiable file, if a
new version of the same file is in
the patch
/.local.bkp.<patch
version>/<directory>/<filename>
/.local.bkp.9.4.0.1/conf/discovery.c
onf
Where:
<directory> is the standard location for the file
<filename> is the standard name of the file
<patch version> is the complete version number for the patch, for example, 9.4.0.1
Review the results of the reconciliation process

The results of the reconciliation analysis performed during the installation and all
actions taken are included in the merged files log located in
<BASEDIR>/smarts/setup/logs. The name of the log file is
install.merge.<patch version>.log
Determine which files require action by reviewing the merged files log generated by
the install process:
1.
Using any editor, open and review the log:
BASEDIR/smarts/setup/log/Install.Merge.9.4.0.1.log.
2.
Review the log:
Resolve conflicts in files manually. See Resolve issues in conflict files.
If you chose the Merge and do not use option during the installation, note
the entries that indicate file merges without conflicts that resulted in
automerge files. The automerge file can be reviewed and then manually
renamed for use. See Rename and use Automerge files.
Resolve issues in conflict files
If a conflict occurs, the Installation software creates conflict files that indicate which
portions of the file are an issue.
Review the conflict files and resolve issues using the following procedure:
1.
Open the user-modifiable file where the conflict occurs using sm_edit.
Conflict files are named using the following convention:.

.<filename>.<patch version>.conflict
For example, the conflict file for discovery.conf is named

.discovery.conf.9.4.0.1.conflict. In UNIX, conflict files are hidden files.
2.
Save the file using the same file name, but without the .conflict extension.
This will overwrite the unmerged version of the file included with the patch.
(Note that a backup version of the unmerged file is at .<standard
filename>.9.4.0.1.)
3.
Review and resolve the conflict. The file shows each conflict with applicable
sections from the various versions of the file: a section from the userconfigurable file in the patch (hotfix.txt), another section from the base
release (original.txt), and one from the modified version of the file
(local.txt). The following is an example of a conflict:


# ServerName = "INCHARGE-<Product>"

serverName = "INCHARGE-<Product>"

serverName = "TESTINCHARGE-<Product>"

Delete the incorrect sections from the conflict and ensure that the correct
section is uncommented.
4.
Save and close the file.
Rename and use Automerge files
Automerge files are only created if you choose the Merge but do not use the files
option during installation, and no conflicts had occurred during the merge process.
1.
Open and review merged files using sm_edit. Merged files are named as
.<filename>.automerge. For example, the merged version of discovery.conf
will be named .discovery.conf.automerge. In UNIX, automerge files are
hidden files.
2.
If necessary, make changes in the file to reflect your desired configuration.
3.
To use the automerge file, rename the file from .<filename>.automerge to

<filename> and save the file. For example, change the name of the merged
file from .discovery.conf.automerge to discovery.conf and save the file.
4.
Save and close the file.
Note: A backup version of the unmerged user-modifiable file from the patch is at
.<standard filename>.9.4.0.1.
41
Uninstallation
Uninstallation
Uninstalling a patch removes all previously applied patches and returns the EMC
Smarts software to the baseline product version.
Note: Administrative privileges are required to uninstall a patch.
Note: Use either the uninstaller program or, for Windows, Add/Remove Programs to
uninstall a patch. Failure to use one of these methods can result in an
unstable system and/or inconsistent product directories.
Roll back to a previous patch
If you want to revert to a previous patch, you must:
Uninstall the currently installed patch to return to the baseline version.
Reinstall the previous patch.
For example, to revert from Patch 20 to Patch 19, uninstall Patch 20, and then
reinstall Patch 19.
Uninstall patch using the Control Panel (Windows only)

Note: If you installed a patch to two different installations of the product on the
same system, use the uninstaller program to remove the patch. Do not use
the Add/Remove Programs because it does not support multiple instances of
the same software.
Use the Windows Control Panel to uninstall a patch:
1.
For Windows Server 2012, Right-click at the screens bottom-left corner and
from the pop-up menu choose Control Panel
2.
Open the list of programs.
For Windows Server 2012, double-click Programs and Features.
3.
From the programs window, select <Product>.
4.
For Windows Server 2012, Click Uninstall/Change
The uninstaller program proceeds as described in Uninstall steps.
Uninstall patch using the uninstaller program

Use the uninstaller program to uninstall a patch:
Note: Do not to use the uninstaller program in the _uninst directory because it will
remove the entire product.
1.
Change the directory or use the file navigator to find the _rpuninst directory.
For example:
/opt/InCharge/<Product>/_rpuninst on UNIX systems
C:\InCharge\<Product>\_rpuninst on Windows systems
2.
Invoke the uninstaller program. For example:
./uninstaller.bin on UNIX systems
Uninstallation
C:\uninstaller.exe on Windows
Note: To run the uninstaller program in CLI mode, specify the console option after
the uninstall command.
The uninstall proceeds as described in Uninstall steps.
Uninstall steps
1.
The Welcome screen appears. Click Next.

The patch to be uninstalled is displayed with its location.
2.
Review the patch number and the directory path.
3.
Click Next and the Uninstallation Progress screen appears. After you click
Next, you cannot cancel the uninstallation process.
Upon completion, the Uninstallation Summary displays informational
messages such as successful completions, error messages, and warnings.
4.
Click Next and, if necessary, restart your system. Otherwise, click Finish to
exit the uninstaller program.
The uninstaller program creates a log file with the naming convention
Uninstall.RP.<maj>.<min>.<sp>.log.
<maj> is the major release version number.
<min> is the minor release version number.
<sp> is the service pack release number.
<patch> is the patch number.
The log file is located in the <BASEDIR>/smarts/setup/logs directory.
43
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 for
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. 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

Docu58687 - Smarts SAM, IP, NPM, MPLS, ESM, OTM and VoIP Version 9.4.0.1 Cumulative Patch Readme Installation Instructions PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Docu58687 - Smarts SAM, IP, NPM, MPLS, ESM, OTM and VoIP Version 9.4.0.1 Cumulative Patch Readme Installation Instructions PDF

Uploaded by

Copyright:

Available Formats

EMC Smarts

Version 9.4.0 Cumulative Patch

EMC Smarts Version 9.4.0 Patch 1 Readme

EMC Smarts Version 9.4.0 Patch 1 Readme

4 EMC Smarts Version 9.4.0 Patch 1 Readme

This section presents the revision history of this document.

First release of EMC Smarts Version 9.4.0 Patch 1 Readme.

Products released in this patch

Product (s) released in this patch

EMC Smarts Version

IP, SAM, ESM, NPM, VoIP, MPLS, OTM

For UNIX, the default location is: /opt/InCharge/<productsuite>.

For Windows, the default location is: C:\InCharge\<productsuite>.

Backs up all files that are being replaced or merged.

EMC Smarts Version 9.4.0 Patch 1 Readme

JRE requirement for Installation software

./setup-IP-linux-9_4_0_1-20150325-64BIT.bin -is:javahome BASEDIR/IP/_jvm

Install a new patch over an older patch

Upgrade after applying a patch

6 EMC Smarts Version 9.4.0 Patch 1 Readme

Patch installation files

EMC Smarts Version 9.4.0 Patch 1 Readme

Enhancements and changes

Enhancements and changes

This patch release contains the following enhancements and changes:

General enhancements and changes

Enhancements and changes in IP

Enhancements and changes in SAM

Enhancements and changes in VoIP

Enhancements and changes in MPLS

Enhancements and changes in NPM

Enhancements and changes in ESM

Enhancements and changes in OTM

General enhancements and changes

Enhancements and changes in IP

Enhancements and changes in SAM

Enhancements and changes in VoIP

Enhancements and changes in MPLS

Enhancements and changes in NPM

Enhancements and changes in ESM

8 EMC Smarts Version 9.4.0 Patch 1 Readme

Enhancements and changes

EMC Smarts Version 9.4.0 Patch 1 Readme

Enhancements and changes

10 EMC Smarts Version 9.4.0 Patch 1 Readme

Enhancements and changes

6. Edit the conf/xmlcollector-vmax-topo-fp.xml file under the Configuration

EMC Smarts Version 9.4.0 Patch 1 Readme

Enhancements and changes

1. Connect to Front-end host via ssh.

12 EMC Smarts Version 9.4.0 Patch 1 Readme

Enhancements and changes

Pre-requisite: Brocade FC Switch SolutionPack should be installed.

EMC Smarts Version 9.4.0 Patch 1 Readme

Enhancements and changes

Enhancements and changes in OTM

New configuration flags

14 EMC Smarts Version 9.4.0 Patch 1 Readme

Known problems and limitations

Known problems and limitations

General Known problems and limitations

Known problems and limitations in IP

Known problems and limitations in SAM