Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Readme
P/N 302-001-129
Rev 02
Copyright 1996 - 2014 EMC Corporation. All rights reserved. Published in the USA.
Published August, 2014
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 8.1.4 Patch 10 Readme
Contents
The document contains information about the EMC Smarts Version 8.1.4 Patch 10
release (EMC Smarts 8.1.4.10).
Revision history ..................................................................................................... 5
Scope .................................................................................................................... 5
Patch description ................................................................................................... 5
Enhancements and changes .................................................................................. 9
Known problems and limitations .......................................................................... 11
Number of fixed defects and certified devices ...................................................... 16
Fixed Defects ....................................................................................................... 17
Certified devices .................................................................................................. 30
Environment and system requirements ................................................................ 37
Installation........................................................................................................... 38
Log files ............................................................................................................... 44
Reconcile user-modifiable files ............................................................................ 45
Uninstallation ...................................................................................................... 48
Troubleshooting and getting help ......................................................................... 50
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
Revision history
Revision history
Scope
Revision history
Revision
Release Date
Description
01
July, 2014
02
August, 2014
This section presents the product scope for this patch release.
Table 2.
Patch Release
Release date
July, 2014
Dec, 2013
July, 2013
IP and SAM
May, 2013
April, 2013
March, 2013
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: All EMC Smarts 8.1.x products will not be released for every patch release. A
patch may apply only to a subset of products, for example, the next patch
release may be only for SAM and IP. Also, if the latest patch version for all
products is 4 and patch 5 is only for SAM and IP, the next patch number
irrespective of which product is released will be patch 6.
Patch description
Installation directory
In this document, the term BASEDIR represents the location where EMC Smarts
software is installed.
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 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:
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.
Patch description
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>.
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.
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-8_1_4_10-20140626-64BIT.bin
setup-IP-linux-rhAS50-8_1_4_10-20140626-64BIT.bin
setup-IP-solaris-8_1_4_10-20140626-64BIT.bin
setup-IP-win-8_1_4_10-20140626-64BIT.exe
Multicast
setup-MCAST-linux-8_1_4_10-20140623-64BIT.bin
setup-MCAST-linux-rhAS50-8_1_4_10-20140623-64BIT.bin
Patch description
setup-MCAST-linux-rhAS60-8_1_4_10-20140806-64BIT.bin
setup-MCAST-solaris-8_1_4_10-20140623-64BIT.bin
setup-MCAST-win-8_1_4_10-20140623-64BIT.exe
SAM Adapter:
setup-SAMADP-linux-8_1_4_10-20140626.bin
setup-SAMADP-linux-rhAS50-8_1_4_10-20140626.bin
setup-SAMADP-solaris-8_1_4_10-20140626.bin
setup-SAMADP-win-8_1_4_10-20140626.exe
Card redundancy Group was not created for Juniper ERX 1440
CQ 654585
Issue
Card redundancy Group was not created for Juniper ERX 1440
.1.3.6.1.4.1.4874.1.1.1.1.3
Resolution
Modified the driver to identify the cards participating in the redundancy group based
on redundancy slot information and create the card redundancy group.
Modified Files
local/conf/discovery/DISCOVERY_UNISPHERE.import
local/rules/discovery/ic-unisphere-erx-cont.asl
local/lib/libsm_devstat_unisphere.so
SAM Adapter OpsManager provides option to connect to different AD user and Password
SAM Adapter OpsManager has been enhanced to connect to a remote OpsManager
using different AD user and password. This can be achieved by configuring the
remote OpsManager in the adapter.conf.
By default this functionality is disabled by setting the below flag to false. If needed, a
user can enable CONNECT_OPS_MGR_FROM_EXT_DOMAIN = true flag in
adapter.conf.
Apart from enabling the flag a user also need to provide the AD username, domain
name, and password as below in the adapter.conf.
OPS_MGR_HOST_USERNAME = "username";
OPS_MGR_HOST_DOMAIN_NAME = "localhost";
OPS_MGR_HOST_PASSWORD = "changeme";
This patch release does not contain any enhancement and changes.
This patch release does not contain any enhancement and changes.
This patch release does not contain any enhancement and changes.
This patch release does not contain any enhancement and changes.
This patch release contains the following known problems and limitations:
11
Resolution
This log in the 8.1.4.10 domain manager logs can be ignored. This text is seen only in
the logging and has no impact on any of the functionality of the product. However,
the sm_server version will show the proper version of the patch.
Domain Manager crashes due to interchange of environment variables when started as a service
CQ 567780
Issue
Environment variables set in one installation, if propagated to another installation
through sm_serviced, can cause the Domain Manager service to crash.
Resolution
Domain manager can crash when multiple versions of EMC Smarts products are
installed on the same machine and are started as a service. This happens as the
environment variables set in one installation get propagated to another installation.
To avoid this, maintain a common base, that is, the version of the application same,
for example, SAM 8.1.4. The installed IP version should also be then IP 8.1.4. This
way we can avoid using other products environment variable getting populated to
another installation.
Another option is to use the environment variable SM_AUTHORITY="<STD>" which will
force the application not to read the environment variables from other installations.
Patch installer displays two error messages if InstallShield cannot find a suitable JVM
CQ 638701
Issue
If InstallShield cannot find a suitable JVM version when the Patch installer is run, two
error messages are displayed instead of one.
Resolution
The two messages are just redundant error messages and can be ignored. Click OK on
both the messages and proceed as indicated in the JRE requirement for InstallShield
software.
Resolution
There is no impact on the functionality and can be ignored. This issue has been fixed
in SAM 9.2. CQ 577224 provides more information.
The following problems and limitations are known for Service Assurance Manager
8.1.4.10:
High value set for Audit Trail Size Limit could cause performance degradation
CQ 639620 / SR 48928556
Issue
Increasing the audit trail size limit more than the default value may result in longer
archival durations which could result in degradation of server performance.
Resolution
Retain a default value of 100.
ASL errors during topology synchronization in the SAM log
CQ 636309
Issue
13
The following ASL errors are observed in the SAM domain log during topology
synchronization with the IP server.
Error description:
[March 6, 2012 1:10:27 AM PST +750ms] t@6292 IP9001_Topo-Driver
ASL-W-ERROR_RULE_SOURCE-While executing rule set
'C:\InCharge\SAM\smarts\rules\ics\ics-topology-sync.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: IgnoreThisType, Line: 2803
ASL-CALL_STACK_RULE- RuleName: PROCESS_ATTRIBUTES_FOR_NEXT_INSTANCE, Line: 2167
ASL-CALL_STACK_RULE- RuleName: PROCESS_ATTRIBUTES_FOR_NEXT_CLASS,
ASL-CALL_STACK_RULE- RuleName: ProcessOneClass, Line: 1979
ASL-CALL_STACK_RULE- RuleName: FastEOF, Line: 2961
ASL-CALL_STACK_RULE- RuleName: EOF, Line: 796
ASL-ERROR_GET-While attempting to get property 'Type' of object
'MR_Object::CHASSIS-APM000648055820006'
MR-PROPERTY_NOT_FOUND-Specified property 'Type' not found in class; in file
These errors appear because of the subscription entry for attribute "Type" of
NASChassis in the dxa-conn-perf.conf file. However, this attribute does not exist in IP.
Resolution
Remove line attr Type for class NASChassis from the /conf/ics/dxa-conn-perf.conf
file which corresponds to this subscription, that is, remove the following entry using
the sm_edit utility:
attr Type
--line 46
15
The version also has support for SCOM2012, but the files, Server, Logs, and Folder
names in OpsManager adapter installation still has 2007 suffix.
Resolution
This issue will be fixed by renaming the folder to OpsMgr instead of OpsMgr2007 in a
future release.
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
IP
16
10
8.1.4.10
VoIP
8.1.4.5
SAM
Not Applicable
Not Applicable
8.1.4.6
SAM Adapters
Not Applicable
Not Applicable
8.1.4.10
Foundation
Not Applicable
Not Applicable
8.1.4.5
MPLS
8.1.4.5
NPM
8.1.4.5
MCAST
8.1.4.10
Fixed Defects
Fixed Defects
Fixed Foundation defects applicable for all products in 8.1.4.10 and earlier
patches
Fixed Foundation defects applicable for all products in 8.1.4.10 and earlier patches
Table 4.
CQ or SR Ticket
Number
Patch
Release
Symptom
Description of Fix
CQ 644612
libsm_sms.dll
NA
NA
NA
NA
8.1.4.7
NA
NA
NA
NA
8.1.4.6
CQ 577011
Cross-site scripting
(XSS) vulnerability
detected on the domain
manager/broker
HTTP port. This can lead
to javascript execution
or cookie injection
attacks on
the user browser.
sm_httpd
8.1.4.5
NA
NA
NA
NA
8.1.4.4
CQ 567460
sm_serviced was
observed to be doing
unexpected state
transitions such as
STARTING -> NOT
sm_serviced
8.1.4.3
SR 48965488
8.1.4.10
17
Fixed Defects
CQ or SR Ticket
Number
CQ 642186
CQ 640746
SR 50939472
SR 50401868
Patch
Release
Windows:
8.1.4.3
Windows:
Description of Fix
CQ 576691
Symptom
Incorrect notifications
for dynamic-model
computed attributes
depending on
built-in functions
errnum, errstr, and no
response.
A "timestamp" is
attached to every event,
which is used to
determine if the event is
stale and discard it.
sm_repos.dll
Unix:
libsm_repos.so
8.1.4.2
lib\sm_repos.dll
Unix:
lib\libsm_repos.so
Symptom
Description of Fix
Original
Patch
Release
Fixed Defects
CQ or SR Ticket
Number
Original
Patch
Release
Symptom
Description of Fix
CQ 609628
Autodiscovery process
will hang indefinitely
since the closure
counter
increment/decrement
methods are not thread
safe.
local/lib/sm_auto_discove
ry.so
8.1.4.10
CQ 651462
IFTypePattern set in
tpmgr-param.conf was
not taking effect
ic-mib2-hyper-data.asl
8.1.4.10
CQ 614448
ic-cisco-vlan-br-stp.asl
runs in a loop during
bridge probing due to a
agent bug.
local/rules/discovery/iccisco-vlan-br-stp.asl
8.1.4.10
CQ 654354
libsm_auto_discovery.so
8.1.4.10
NA
NA
NA
NA
8.1.4.7
CQ 602076
rules/discovery/ic-ns-contact.asl
8.1.4.6
rules/discovery/icunisphere-vr-data.asl
sm_snmpwalk was
walking vlans that did
not exist.
Sm_snmpwalk.exe
(windows)
rules/discovery/ic-ciscomodule-pre-card.asl
CQ 602647
CQ 601929
CQ 602390
libsm_auto_discovery.dll
rules/discovery/ic-nsdata.asl
8.1.4.5
conf/discovery/DISCOVERY
_UNISPHERE.import
8.1.4.5
Sm_snmpwalk
(linux/solaris).
8.1.4.5
19
Fixed Defects
CQ or SR Ticket
Number
Original
Patch
Release
Symptom
Description of Fix
CQ641530
rules/discovery/ic-vlancisco-membership.asl
8.1.4.4
CQ 576914
NetworkAdapter
OperStatus/AdminStatu
s initial value was
Unknown even though
the initial value was set
as UP in Polling and
Threshold settings. This
happened only when
Connectivity Polling was
set as External Poller.
Windows:
8.1.4.3
rules/discovery/ic-ciscopost-processor.asl
8.1.4.3
rules/health/adaptersettings.asl
8.1.4.3
SR 50738604
CQ 567685
SR 49923046
CQ 596595
lib\sm_repos.dll
Unix:
lib\libsm_repos.so
rules/discovery/ic-foreasx1000.asl
conf/discovery/DISCOVERY
_FORE.import
conf/discovery/oid2Type_
Misc.conf
conf/icf/
HEALTH_FORE.import
Windows:
lib/sm_health_fore.dll
Unix:
Fixed Defects
CQ or SR Ticket
Number
Symptom
Description of Fix
Original
Patch
Release
lib/libsm_health_fore.so
CQ 599629
CQ 599463
CQ 641086
SR 52831400
CQ 640503
SR 50196456
CQ 576854
CQ 576969
SR 50940772
SR 51604840-1
Windows:
Windows:
Interface (without
underlying IP in the
topology) did not get
deleted from the
topology after
rediscovery, when
deleted from the device.
rules/discovery/ic-createinterface.asl
8.1.4.2
rules/discovery/ic-ciscovlan-br-stp.asl
8.1.4.2
ic-cisco-vlan-br-stp.asl:
ASL-ERROR_GET-While
attempting to get
property 'PortNumber'
of object '::'
8.1.4.3
lib/sm_health_marconi.dll
Unix:
lib/libsm_health_marconi.
so
8.1.4.3
sm_health_cisco.dll
Unix:
sm_health_cisco.so
rules/discovery/ic-ciscocrs-entity.asl
rules/devstat/syssettings.asl
ic-cisco-crs-entity.asl:
ASLERROR_UNDEFINED_VA
RIABLE_ACCESSVariable 'entPhycardId'
has not been assigned a
value
sys-settings.asl:
ASL-ERROR_PUT-While
21
Fixed Defects
CQ or SR Ticket
Number
Symptom
Original
Patch
Release
Description of Fix
attempting to set
property
'DataProvidedBy' of
object '::'
CQ or SR Ticket
Number
Symptom
Description of Fix
NA
NA
NA
NA
8.1.4.10
NA
NA
NA
NA
8.1.4.7
CQ 643518
When relationships
change (swap) between
devices in IP Topology,
SAM does not sync
topology properly
resulting in discrepancy
between IP and SAM
topology.
Additional condition
added to handle the
scenario where the
relationship instances
get exchanged between
devices.
Windows:
lib/sm_sam_common.dll
8.1.4.6
Windows:
CQ 642034
Patch
Release
Unix:
lib/libsm_sam_common.so
8.1.4.5
libsm_map_base.dll
Unix
libsm_map_base.so
CQ 642471
Class path in
NotifGui.bat is now
updated to pick up the
new jar with latest
version information.
CONSOLE\smarts\notif\e
ditor\NotifGui.bat
8.1.4.5
CQ 577625
Getexplains is called
only for the problem
events which resolved
the issue.
rules/ics/ics-eventprocessing.asl
8.1.4.5
PROCESS_DISCONNECT
rule was processing for
rules/ics/ics-eventprocessing.asl
8.1.4.4
Fixed Defects
CQ or SR Ticket
Number
CQ 567853
SR 53037290
CQ 567776
SR 52749378
CQ 641038
SR 51612984
Patch
Release
rules/ics/ics-nlprocessing.asl
8.1.4.4
Connections disappear
on the map in SAM
domain during topology
synchronization with
underlying domains
attached.
Classes
VirtualSwitchSystem
and VSSChassis were
not defined which are
now defined in the dxa
files
conf/ics/dxa-oi.conf
8.1.4.4
Windows:
Symptom
Description of Fix
all values of
DISCONNECT_SMOOTHI
NG_INTERVAL. Added a
condition to continue
only if
Events in MSSCOM
which have been
cleared, still shows as
active in the attached OI
and SAM.
DISCONNECT_SMOOTHI
NG_INTERVAL is greater
than zero.
conf/icoi/dxa-oi-fromam-pm.conf
conf/icoi/bootstrap.conf
8.1.4.3
lib\ libsm_ics_ems.dll
Unix:
lib\ libsm_ics_ems.so
8.1.4.2
23
Fixed Defects
CQ 654965
CQ 615560
CQ 616615
CQ 653359
CQ 654680
Patch
Release
bin/sm_OpsMgrOAO.exe
8.1.4.10
SAM Adapter
OpsManager provides
option to connect to
different AD user and
Password
bin/sm_OpsMgrOAO.exe
rules/niqam/importEvent.
asl (main.asl)
8.1.4.10
UpdateTopology
function stops when it
hit an error condition,
internally it is stopping
processing of other
entries from SAM to SDI
adapter
Fix is provided to
handle error condition
in the asl file
rules/sdi/sdi.asl
8.1.4.10
Symptom
Description of Fix
SAM Adapter
OpsManager is not
fetching all needed
attributes from SCOM
Server
conf/OpsMgr2007/adapt
er.conf
rules/OpsMgr2007/adapt
erConfImport.asl
8.1.4.10
conf/OpsMgr2007/adapt
er.conf
rules/OpsMgr2007/adapt
erConfImport.asl
Fixed Defects
CQ or SR Ticket
Number
Patch
Release
sdi-archival/sdiarchive.cmd
8.1.4.10
BMC Session
Disconnect Notification
disappears after
Acknowledge and
reappear as
Unacknowledge.
bmc-events-parse.asl
8.1.4.10
NA
NA
8.1.4.7
NA
NA
NA
NA
8.1.4.6
CQ 642702
/conf/opsmgr2007/adapt
er.conf
8.1.4.5
/rules/opsmgr2007/event
Mgr.asl
CQ 651629
CQ 615876
CQ 615948
CQ 616634
SR 54189790
Symptom
Description of Fix
/rules/opsmgr2007/adap
terConfImport.asl
25
Fixed Defects
CQ or SR Ticket
Number
Symptom
Description of Fix
Patch
Release
eHealth Adapter
support on Linux.
Note: This is an
enhancement.
CQ 586445
CQ 640983
SR 51597922
CQ 577034
CQ 503271
8.1.4.5
rules/OpsManager2007/r
estartableThreadMgr.asl
bin/system/sm_arclient7
64
Windows :
8.1.4.4
8.1.4.3
bin/system/sm_arclient7
01
bin/system/sm_arclient6
30
bin/system/sm_arclient
local/lib/sm_sdi_core.dll
local/lib/sm_sdi_core.lib
local/lib/sm_sdi.dll
local/lib/sm_sdi.lib
8.1.4.2
Fixed Defects
CQ or SR Ticket
Number
Symptom
Description of Fix
Patch
Release
local/lib/sm_sdi.po
local/bin/system/sm_sdi.
exe
Linux/Solaris :
local/lib/libsm_sdi_core.
so
local/lib/libsm_sdi.so
local/bin/system/sm_sdi
CQ or SR Ticket
Number
Symptom
Description of Fix
Patch
Release
NA
NA
NA
NA
8.1.4.10
NA
NA
NA
NA
8.1.4.7
NA
NA
NA
NA
8.1.4.6
CQ 577638
Introduced configurable
ReadTimeout for
protocol handler used
by
java.net.URLConnection
underlying SOAP client.
This timeout will be
effective reading from
input stream, hence
avoiding the chance on
pooling thread hand in
case connected SOAP
service on CUCM fails to
respond to SOAP
requests by VoIP-AM.
voip_cisco_axl.jar
8.1.4.5
NA
NA
rules/voip/cisco/iccisco-detector.asl
rules/voip/cisco/voipcisco-settings.asl
conf/voip/voip.conf
lib/sm_voip (dll/so)
The Description of
devices certified in the
patch table contains
description of changes
in this patch.
8.1.4.4
8.1.4.3
NA
NA
8.1.4.2
27
Fixed Defects
CQ or SR Ticket
Number
Symptom
Description of Fix
Patch
Release
NA
NA
NA
NA
8.1.4.10
NA
NA
NA
NA
8.1.4.7
NA
NA
NA
NA
8.1.4.6
NA
NA
8.1.4.5
NA
NA
NA
8.1.4.4
8.1.4.3
NA
8.1.4.2
Symptom
Description of Fix
CQ 651311
NA
Patch
Release
8.1.4.10
8.1.4.7
Fixed Defects
CQ or SR Ticket
Number
Symptom
Description of Fix
Patch
Release
NA
8.1.4.6
NA
NA
8.1.4.5
NA
NA
NA
8.1.4.4
CQ 576931
Multicast Manager
experienced rapid
memory consumption
due to growth of
SubscriberFE queue.
mcast.mdl
8.1.4.3
SR 50887122
Windows:
libsm_mcast.dll
Linux/Solaris:
libsm_mcast.so
NA
NA
NA
NA
8.1.4.2
Symptom
Description of Fix
Original
Patch
Release
NA
NA
NA
NA
8.1.4.10
NA
NA
NA
NA
8.1.4.7
NA
NA
NA
NA
8.1.4.6
8.1.4.5
NA
NA
NA
8.1.4.4
CQ 567687
BGPSession disconnect
events raised
incorrectly.
Windows:
8.1.4.3
SR 51346218
libsm_rpsm_bgp.dll
Unix:
libsm_rpsm_bgp.so
29
Certified devices
CQ or SR Ticket
Number
Symptom
Description of Fix
Original
Patch
Release
instrumentation never
occurred.
NA
NA
Certified devices
NA
NA
8.1.4.2
This section describes the devices certified and the certification impact in this patch:
Table 12.
CQ or SR
Ticket
Number
Product
Symptom
Description of
Fix
Patch
Release
CQ 616116
IP
Certification for
Juniper PTX3000
.1.3.6.1.4.1.2636.1.
1.1.2.98
This device is
certifed in IP
local/conf/discovery/oid2type_J
uniper.conf
8.1.4.10
local/conf/discovery/JuniperPow
erType.conf
local/rules/discovery/ic-juniperchassis-ptx.asl
local/rules/discovery/ic-juniperhealth-ptx.asl
CQ 654585
CQ 604508
IP
IP
Card redundancy
Group was not
created for Juniper
ERX 1440
.1.3.6.1.4.1.4874.1.
1.1.1.3
Modified the
driver to identify
the cards
participating in
the redundancy
group based on
redundacy slot
information and
create the card
redundancy
group.
local/conf/discovery/DISCOVER
Y_UNISPHERE.import
For Sonus
GSX9000HD
.1.3.6.1.4.1.2879.1.
1.2Layering
relationship is not
formed between
DSX1 and DSX3
Interfaces.
Modified the
code to create
layered over
relationship
between DSX1
and DSX3
interfaces.
rules/discovery/ic-sonus-createinterface.asl
8.1.4.10
local/rules/discovery/icunisphere-erx-cont.asl
local/lib/libsm_devstat_unisphe
re.so
8.1.4.6
Certified devices
CQ or SR
Ticket
Number
Product
Symptom
Description of
Fix
Patch
Release
CQ 602647
IP
IPV6 is not
discovering
Unisphere Virtual
routers
IPV6 support
provided for
Virtual Router
device Juniper
Unisphere E320
rules/discovery/ic-unisphere-vrdata.asl
8.1.4.5
conf/discovery/DISCOVERY_UNI
SPHERE.import
CQ 602390
IP
Card redundancy
group created based
on unitID and
peerUnitID from
Cisco-RF MIB did not
reflect the set of
cards in entPhysical
MIB
Based on the
logic given by
the vendor, the
modules from
entPhysicalMIB
with description
as RP0 and RP1
has been
mapped to
having standby
status from
unitID .32 and
.33 in the CiscoRF MIB
ic-cisco-module-pre-card.asl
8.1.4.5
CQ 642178
IP
Memory instances of
Cisco GSR Router do
not show location
information. SYS OID
of the device is
.1.3.6.1.4.1.9.1.385
Enhancement to
additionally
display Memory
location
information in
display name
for Memory for
Cisco GSR
Router
(.1.3.6.1.4.1.9.
1.385)
conf/discovery/DISCOVERY_Cisc
o.import
8.1.4.4
Memory instances of
Cisco CRS MCC
Router do not show
location information
Enhancement to
additionally
display Memory
location
information in
display name
for Memory
instances for
Cisco CRS
Router
(.1.3.6.1.4.1.9.
1.613).
conf/discovery/DISCOVERY_Cisc
o.import
CQ 600619
IP
rules/discovery/ic-cisco-createiosxr-health.asl
8.1.4.4
rules/discovery/ic-cisco-createcrsiosxr-health.asl
31
Certified devices
CQ or SR
Ticket
Number
Product
Symptom
Description of
Fix
Patch
Release
CQ 642182
IP
Cards discovered
from OLD-CiscoChassis MIB were
showing
NOTPRESENT state
as it was polling
cefcModuleOperStat
us OID from EntityFRU MIB to get the
status instead of
using
OldCiscoChassis MIB
for instrumentation.
SYS OID of the
device is Cisco1941
.1.3.6.1.4.1.9.1.104
7
Modified
discovery code
to instrument
cards from
OldCiscoChassi
s MIB when
data from
Entity-FRU MIB
is unavailable.
rules/ic-cisco-router-card.asl
8.1.4.4
Modified the
instrumentation
class of DSX1
and DSX2
interfaces to
use OIDs
sonusDsx1Stat
OperStatus and
sonusDsx3Stat
OperStatus for
OperStatus
lib/ libsm_devstat_sonus.so
8.1.4.4
New
Containment
and
Performance
Drivers.
Discovered
Ports(.1.3.6.1.4.
1.23022.2.8.1.
1.6),
PowerSupply(.1
.3.6.1.4.1.2302
2.2.8.1.1.12.1.
2),
CPU(.1.3.6.1.4.
1.23022.2.8.1.
1.21.1.5)
rules/discovery/ic-netopticsport.asl
8.1.4.4
CQ 600620
IP
and
sonusDsx2AdmnMod
e
This is for SONUS
GSX 9000HD
(.1.3.6.1.4.1.2879.1.
1.2)
CQ 642184
IP
rules/discovery/ic-netopticshealth.asl
conf/discovery/DISCOVERY_NET
OPTICS.import
conf/discovery/oid2type_Netopt
ics.conf
lib/libsm_devstat_netoptics.so
lib/libsm_health_netoptics.so
Certified devices
CQ or SR
Ticket
Number
Product
Symptom
Description of
Fix
Patch
Release
CQ 642248
IP
Modified driver
to create IPV6
addresses. IPV6
created using
oid
inetCidrRouteIfI
ndex
(.1.3.6.1.2.1.4.
24.7.1.7.2)
conf/discovery/DISCOVERY_UNI
SPHERE.import
8.1.4.4
Added a
certification
code for AES.
Added AES trap
definitions in
trap manager
configuration
file for
Avaya. VoIP AM
will generate
notifications if
AES
server/processe
s goes down
conf/voip/discovery/certavaya.conf
Implemented
code to
discover and
monitor all
missing
components
and
relationships.
conf/discovery/DISCOVERY_ALC
ATEL.import
CQ577654
CQ 597811
VoIP
IP
rules/discovery/ic-unispheredata.asl
8.14.4
conf/voip/icoi/avaya_trap_mgr.
conf
conf/voip/avaya/avayatrapd.conf
rules/voip/icoi/avaya/avayaaes-trap-rules.asl
8.1.4.2
conf/discovery/oid2type_Alcatel
.conf
rules/discovery/ic-alcatel-timexcont.asl
rules/discovery/ic-alcatel-timexhealth.asl
33
Certified devices
CQ or SR
Ticket
Number
Product
Description of
Fix
Symptom
were missing.
Certification impact
This section lists the impacted drivers and SysOIDs as a result of certification
changes.
Table 13.
CQ or SR
Ticket Number
Product
CQ 616116
IP
CQ 654585
IP
Certification impact
Impacted drivers
Performance-JuniperPTX-Driver
Containment-JuniperPTX-Driver
ContainmentUnisphere-ERXDriver
Impacted SysOIDs
.1.3.6.1.4.1.2636.1.1.1.2.98
.1.3.6.1.4.1.2636.1.1.1.2.69
.1.3.6.1.4.1.4874.1.1.1.1.1
Patch Release
8.1.4.10
8.1.4.10
.1.3.6.1.4.1.4874.1.1.1.1.2
.1.3.6.1.4.1.4874.1.1.1.1.3
.1.3.6.1.4.1.4874.1.1.1.1.4
.1.3.6.1.4.1.4874.1.1.1.6.1
.1.3.6.1.4.1.4874.1.1.1.1.5
CQ 604508
IP
Containment-SonusGSX-Driver
.1.3.6.1.4.1.2879.1.1.2
8.1.4.6
CQ 602647
IP
Containment-ERXVRF-Data-Driver
.1.3.6.1.4.1.4874.1.1.1.1.1
.1.3.6.1.4.1.4874.1.1.1.1.2
.1.3.6.1.4.1.4874.1.1.1.1.3
.1.3.6.1.4.1.4874.1.1.1.1.4
.1.3.6.1.4.1.4874.1.1.1.1.5
.1.3.6.1.4.1.4874.1.1.1.6.1
.1.3.6.1.4.1.4874.1.1.1.1.5.1
.1.3.6.1.4.1.4874.1.1.1.6.1.1
8.1.4.5
CQ 602390
IP
Cisco-Entity-FRU-RF
.1.3.6.1.4.1.9.1.643
8.1.4.5
Patch
Release
Certified devices
CQ or SR
Ticket Number
Product
CQ 642178
IP
HEALTH = CiscoIOSXR
.1.3.6.1.4.1.9.1.385
8.1.4.4
CQ 600619
IP
HEALTH = CiscoCRSIOSXREntSensor
.1.3.6.1.4.1.9.1.613
8.1.4.4
Impacted drivers
Impacted SysOIDs
Patch Release
.1.3.6.1.4.1.9.1.643
.1.3.6.1.4.1.9.1.394
.1.3.6.1.4.1.9.1.388
.1.3.6.1.4.1.9.1.1331
CQ 642182
IP
CONT = CiscoRouter-Entity
.1.3.6.1.4.1.9.1.223
8.1.4.4
.1.3.6.1.4.1.9.1.648
.1.3.6.1.4.1.9.1.1215
.1.3.6.1.4.1.9.1.1172
.1.3.6.1.4.1.9.1.1166
.1.3.6.1.4.1.9.1.1191
.1.3.6.1.4.1.9.1.1174
.1.3.6.1.4.1.9.12.3.1.9.2.180
.1.3.6.1.4.1.9.1.743
.1.3.6.1.4.1.9.1.1044
.1.3.6.1.4.1.9.1.1042
.1.3.6.1.4.1.9.1.1041
.1.3.6.1.4.1.9.1.1047
.1.3.6.1.4.1.9.1.1046
.1.3.6.1.4.1.9.1.1045
.1.3.6.1.4.1.9.1.388
.1.3.6.1.4.1.9.1.1096
.1.3.6.1.4.1.9.1.1095
.1.3.6.1.4.1.9.1.1355
.1.3.6.1.4.1.9.1.1389
.1.3.6.1.4.1.9.1.1386
.1.3.6.1.4.1.9.1.1383
.1.3.6.1.4.1.9.1.1392
.1.3.6.1.4.1.9.1.1376
.1.3.6.1.4.1.9.1.1380
.1.3.6.1.4.1.9.1.830
.1.3.6.1.4.1.9.1.598
.1.3.6.1.4.1.9.1.577
.1.3.6.1.4.1.9.1.1341
.1.3.6.1.4.1.9.1.1249
.1.3.6.1.4.1.9.1.945
35
Certified devices
CQ or SR
Ticket Number
Product
CQ 600620
IP
Impacted drivers
Interface_Fault_Son
usInterface_Dsx1
Impacted SysOIDs
Patch Release
.1.3.6.1.4.1.2879.1.1.2
8.1.4.4
.1.3.6.1.4.1.4874.1.1.1.1.1
8.1.4.4
Interface_Fault_Son
usInterface_Dsx3
CQ 642248
IP
ADNR = UnisphereAccess
.1.3.6.1.4.1.4874.1.1.1.1.2
.1.3.6.1.4.1.4874.1.1.1.1.3
.1.3.6.1.4.1.4874.1.1.1.1.4
.1.3.6.1.4.1.4874.1.1.1.1.5
.1.3.6.1.4.1.4874.1.1.1.6.1
.1.3.6.1.4.1.4874.1.1.1.1.5.1
.1.3.6.1.4.1.4874.1.1.1.6.1.1
This section lists the supported operating systems and describes how to verify the
version number.
IP
Multicast
37
Product
SAM
Adapter
Solaris 9 and 10
Windows 2003 R2
WIndows 2008 R2
Installation
Installation
Run the appropriate setup command listed in Table 15. Replace xx with the
relevant product name, for example, IP, SAM, SAMADP, VOIP, MPLS, MCAST,
and NPM. For exact name, check the Patch Installation Files section.
Table 15.
Operating
system
Linux
./setup-xx-linux-8_1_4_10-2014062664BIT.bin
Linux AS 5
&6
Solaris
Windows
./setup-xx-solaris-8_1_4_10-2014062664BIT.bin
setup-xx-win-8_1_4_10-2014062664BIT.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.
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.
4.
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.
39
Installation
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.
8.
9.
Reconcile the files with conflicts and review successfully merged files as
described in Reconcile user-modifiable files.
Installation
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 16 and then press Enter. Replace
xx with the relevant product name, for example, IP, SAM, SAMADP, VOIP,
MPLS, MCAST, and NPM. For exact name, check the Patch Installation Files
section.
Table 16.
Operating
system
Linux
./setup-xx-linux-8_1_4_10-20140626-64BIT.bin
-console
Linux AS 5
&6
Solaris
./setup-xx-solaris-8_1_4_10-2014062664BIT.bin -console
Windows
setup-xx-win-8_1_4_10-20140626-64BIT.exe console
41
Installation
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 17 and then
press Enter.
Table 17.
Key
Operation
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
described in Reconcile user-modifiable files.
Installation
xx with the relevant product name, for example, IP, SAM, SAMADP, VOIP, MPLS,
MCAST, and NPM. For exact name, check the Patch Installation Files section.
Table 18.
Operating
system
Linux
./setup-xx-linux-8_1_4_10-20140626-64BIT.bin silent
-G replaceNewerResponse="Yes to All"
-P rpProduct.installLocation=<BASEDIR>
-W mergeSummaryPanel.choiceMergeResult={auto|manual}
Linux AS 5
&6
Solaris
./setup-xx-solaris-8_1_4_10-20140626-64BIT.bin
silent
-G replaceNewerResponse="Yes to All"
-P rpProduct.installLocation=<BASEDIR>
-W mergeSummaryPanel.choiceMergeResult={auto|manual}
Windows
setup-xx-win-8_1_4_10-20140626-64BIT.exe silent
-G replaceNewerResponse="Yes to All"
-P rpProduct.installLocation=<BASEDIR>
-W mergeSummaryPanel.choiceMergeResult={auto|manual}
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
43
Log files
Operating
system
is equivalent to Select Merge but do not use the files in Wizard mode.
Operating
system
NA
NA
Log files
Table 20 lists the files that the Installation software creates during the install
process.
Table 20.
Name
Install log
Path
File Name
<BASEDIR>/smarts/setup/logs
Install.<patch
version>.log
install.merge.<patch
version>.log
Where <patch version> is the complete version number for the patch, for example,
8.1.4.10
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.
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.
45
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.
/local/<directory>/.<filename>.<
patch version>
/local/conf/.discovery.conf.8.1.4.10
/.local.bkp.<patch
version>/<directory>/<filename>
/.local.bkp.8.1.4.0/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, 8.1.4.10
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.
BASEDIR/smarts/setup/log/Install.Merge.8.1.4.10.log.
2.
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.
Open the user-modifiable file where the conflict occurs using sm_edit.
Conflict files are named using the following convention:.
.<filename>.<patch version>.conflict
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>.8.1.4.10.)
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:
Delete the incorrect sections from the conflict and ensure that the correct
section is uncommented.
4.
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.
3.
4.
Note: A backup version of the unmerged user-modifiable file from the patch is at
.<standard filename>.8.1.4.10.
47
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.
For example, to revert from Patch 20 to Patch 19, uninstall Patch 20, and then
reinstall Patch 19.
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.
2.
3.
4.
Click Change/Remove.
Change the directory or use the file navigator to find the _rpuninst directory.
For example:
2.
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.
2.
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.
49