EMC Smarts Version 9.4.2 Patch 15 Readme ... - VMware Docs

EMC® Smarts® Version 9.4.2 Cumulative Patch

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

Readme 302-004-364

Rev 02

EMC Smarts Version 9.4.2 Patch 15 Readme

Copyright © 1996 - 2017 Dell Inc. or its subsidiaries. All rights reserved. Published in the USA.

Published November 2017

Dell 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. Dell 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 Dell software described in this publication requires an applicable software license.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA.

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


https://support.emc.com/


3

Contents

The document contains information about the EMC® Smarts® Version 9.4.2 Patch 15 release (EMC Smarts 9.4.2.15).

Revision history ..................................................................................................... 5 Scope .................................................................................................................... 5 Patch description ................................................................................................... 5 Enhancements and changes .................................................................................. 8 Known problems and limitations .......................................................................... 10 Number of fixed defects and certified devices ...................................................... 12 Fixed Defects ....................................................................................................... 13 Certified devices .................................................................................................. 32 Third party software/library vulnerability .............................................................. 48 Environment and system requirements ................................................................ 49 Installation........................................................................................................... 54 Log files ............................................................................................................... 59 Reconcile user-modifiable files ............................................................................ 60 Uninstallation ...................................................................................................... 62 Troubleshooting and getting help ......................................................................... 65

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


5

Revision history This section presents the revision history of this document.

Table 1. Revision history

Revision Release Date Description

01 April 2017 Release of EMC Smarts Version 9.4.2 Patch 9 Readme.

02 July 2017 Release of EMC Smarts Version 9.4.2 Patch 11 Readme.

03 August 2017 Release of EMC Smarts Version 9.4.2 Patch 12 Readme.

04 October 2017 Release of EMC Smarts Version 9.4.2 Patch 15 Readme.

05 November 2017

Release of EMC Smarts Version 9.4.2 Patch 15 Readme (second revision).

Scope

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.2 Patch 15

November 2017 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 product’s baseline.

Note: All EMC Smarts 9.4.2.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 1 and Patch 2 is only for SAM and IP, the next patch number irrespective of which product is released will be Patch 3. In addition, Network Configuration Manager (NCM) is also part of EMC Smarts 9.4 release and impacts the patch numbering for the release. Details for this product are kept in a separate Patch Readme.

Installation directory In this document, the term BASEDIR represents the location where EMC Smarts software is installed.

Patch description


6

• 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.

• 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_2_15-20171026-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.

Patch description


7

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.2.15

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_2_15-20171026-64BIT.bin

• setup-IP-win-9_4_2_15-20171026-64BIT.exe

SAM:

• setup-SAM-linux-9_4_2_15-20171020-64BIT.bin

• setup-SAM-win-9_4_2_15-20171020-64BIT.exe

CONSOLE:

• setup-CONSOLE-linux-9_4_2_15-20171020.bin

• setup-CONSOLE-win-9_4_2_15-20171020.exe

ESM:

• setup-ESM-linux-9_4_2_15-20171012-64BIT.bin

• setup-ESM-win-9_4_2_15-20171012-64BIT.exe

MPLS:

• setup-MPLS-linux-9_4_2_15-20171019-64BIT.bin

• setup-MPLS-win-9_4_2_15-20171019-64BIT.exe

NPM:

• setup-NPM-linux-9_4_2_15-20171019-64BIT.bin

• setup-NPM-win-9_4_2_15-20171019-64BIT.exe

Enhancements and changes


8

VoIP:

• setup-VOIP-linux-9_4_2_15-20171017-64BIT.bin

• setup-VOIP-win-9_4_2_15-20171017-64BIT.exe

OTM:

• setup-OTM-linux-9_4_2_15-20171019-64BIT.bin

• setup-OTM-win-9_4_2_15-20171019-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 Enhancements and changes in IP Enhancement to automate manual IP tagging via script

This patch release contains enhancement to automate manual IP tagging via script.

A new utility (via asl script) has been introduced, file name : ic-autoIPTagging.asl present under rules/utils directory that runs through all the duplicateIP present in the topology, and creates appropriate tag groups based on the device name that it is duplicatedBy.

Note: This is mainly useful for tagging purpose where RD (route distinguisher) is not populated.

The following are the modified files (all files in BASEDIR/smarts/local/):

local/rules/utils/ic-autoIPTagging.asl

To run the utility, execute the following command:

./sm_adapter -s <server_name> -b <broker_port> ic-autoIPTagging.asl

Note: Before running the utility, please take a backup of the RPS file (in case if tagging needs to be redone).

Enhancements and changes


9

Also, the tool is a framework for automating the manual IP tagging, and hence this tool can be customized as per user requirement.

Enhancement of an IP domain to Usedot34Addresses and dot34ExclusionPattern This patch release contains enhancement for the IP domain to Usedot34Addresses and dot34ExclusionPattern. This is to support the exclusion of IpAddressIfIndex {“.1.3.6.1.2.1.4.34.1.3”} during device discovery. This feature is mainly introduced to handle the agent bug while probing the IpAddressTable.

The following are the modified files (all files in BASEDIR/smarts/local/):

local/auto-discovery/manager/ic-ns-data.asl

local/auto-discovery/manager/ic-ns-probe.asl

local/discovery/ic-mib2-hyper-data.asl

local/conf/discovery/tpmgr-param.conf

Enhancements and changes in SAM This patch release does not contain any enhancement and changes.

Enhancements and changes in VoIP This patch release does not contain any enhancement and changes.

Enhancements and changes in MPLS This patch release does not contain any enhancement and changes.

Enhancements and changes in NPM This patch release does not contain any enhancement and changes.

Enhancements and changes in ESM This patch release does not contain any enhancement and changes.

Enhancements and changes in OTM This patch release does not contain any enhancement and changes.

New configuration flags This patch release does not contain any new configuration flags.

Known problems and limitations


10


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 problem and limitation in OTM

General Known problems and limitations Known problems and limitations in IP

This patch release does not include any known issues.

Known problems and limitations in SAM Perl configuration error blocks Failover. Failover fails to show the correct status of the domains due to perl config failure in an upgraded environment. Messages appear in Failover logs, such as follows:

May 30, 2017 3:01:10 PM GMT+00:00 +953ms 6133 331314944 ALWAYS Monitor-Driver ASL_MSG-ASLP failover/failover-monitor.asl: Output: 'Must be invoked from sm_perl! at /opt/InCharge/SAM/smarts/actions/determine_version.pl line 31. BEGIN failed--compilation aborted at /opt/InCharge/SAM/smarts/actions/determine_version.pl line 34.

Workaround:

In the failover installation, do the following:

1. Navigate to the file mentioned in the logs (in this case /opt/InCharge/SAM/smarts/actions/determine_version.pl at line number 31)

2. Replace the if condition mentioned as follows:

if ( ! defined($ENV{"SM_PERL_BASE"}) || $Config{prefix} !~ /$ENV{"SM_PERL_BASE"}/ ) {

With the following if condition:

if ( ! defined($ENV{"SM_PERL_BASE"})) {

3. Restart failover server.



11

Known problems and limitations in VoIP This patch release does not include any known issues.

Known problems and limitations in MPLS This patch release does not include any known issues.

Known problems and limitations in NPM This patch release does not include any known issues.

Known problems and limitations in ESM This patch release does not include any known issues.

Known problems and limitations in OTM This patch release does not include any known issues.

Number of fixed defects and certified devices


12

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. Number of fixed defects and certified devices

Product Number of fixed defects

Number of new certifications

Number of updated certifications

Patch release

DMT 1 0 0 9.4.2.15

IP 9 109 7 9.4.2.15

SAM 1 0 0 9.4.2.15

NPM 0 0 0 9.4.2.15

ESM 1 0 0 9.4.2.15

MPLS 0 0 0 9.4.2.15

VoIP 0 0 0 9.4.2.15

OTM 0 0 0 9.4.2.15

Fixed Defects


13

Fixed Defects This section describes the defect fixes in this patch:

• Fixed Foundation defects applicable for all products

• 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

Fixed Foundation defects Table 4. Fixed Foundation defects applicable for all products

CQ/JIRA or SR Ticket Number

Symptom Description of Fix Modified Files (all files in BASEDIR/smarts/local/)

Patch Release

IS-9477/ SR 08311986

ESM server goes down immediately after starting the service.

The crash was caused while parsing the encrypted Auth/Priv password having new lines. Code has been modified to properly parse the encrypted Auth/Priv passwords having new lines.

lib//libsm_repos.so lib/libsm_adsnmp.so

9.4.2.15

IS-8704/ SR 7230121

Service started with --noregister causes an attached service to unattach.

The code has been modified so that in case of --noregister, server never tries to connect with broker.

local/bin/system/sm_server 9.4.2.12

IS- 8327/ SR 71319566

PCI Scan makes SAM server unresponsive and also there is an issue where server crashes when decoding URLs.

Decoding of URL used to cause a heap corruption which has been fixed. For the server unresponsiveness, a delay of 25 milliseconds is introduced while accepting any new connections and the HTTP worker threads are increased from 2 to 4, to allow processing of requests for closure.

libsm_sockserv.so and libsm_httpd.so

9.4.2.9

Fixed Defects


14

Fixed IP specific defects

Table 5. Fixed IP specific defects



Original Patch Release

The Fixed Foundation Defects table lists issues fixed in the patch.

IS-9773/ SR 08719844

The user gets many HSRP alerts.

Many HSRP alerts are generated as an IsUnknownEndPointExist Event is being called, on the basis of the default UNKNOWN_HSRP state of HSRPEndpoints. The Default state is modified to INITIAL_UNKNOWN, and the code for IsUnknownEndPointExist is also modified to encapsulate all the possible test cases.

ip/icim/ICIM_Network.mdl ip/devstat/cisco/Cisco.mdl

9.4.2.15

IS-9584/ SR 88104354

The VoltageSensor threshold is false.

Code has been modified so that the voltageSetting class have the UseMIBThreshold attribute populated.

local/lib/libsm_health_settings.so

9.4.2.15

IS-6196/ SR 111111

The ASNMP issue occurs. The selective probing of indices is performed to fix the ASNMP issue based on sysObjectID flag.

local/rules/discovery/ic-mib2-hyper-data.asl local/conf/discovery/tpmgr-param.conf

9.4.2.15

IS-9470/ SR 08215158

The GDC-SCM-Cont-Driver logic for discovery cards need to be changed to check during discovery for scmNodeOperStatus of Cards.

The user gets false alarms on Card status for the cards that are not installed. The fix has been provided by creating Cards with valid indexes of scmNodeOperStatus.

DISCOVERY_GDC.import ic-gdc-scm-cont.asl

9.4.2.15

IS-9323/ SR 08139909

Descriptions are not being appended/added to object display names in 9.4.1.

Description was not appearing properly because the wrong driver was being called that has been corrected.

ic-cisco-end-device-CPUProc.asl

9.4.2.15

IS-9314/ SR 8780872

The AggregateInterface/AggregatePort logic for disabling LayeredOver/Underlying relationship needs to be changed.

Code has been modified to allow to create LayeredOver relationship for AggregatePort or AggregateInterface along with composedOf relationship if data exists for both.

ic-clear-interface-layering.asl

9.4.2.15

IS-8594/ SR 07134823

Hypervisor with sysOid 1.3.6.1.4.1.6876.4.1 does not show any memory component.

As part of the fix, memory components are created from hrDeviceVolatileMemory (oid - 1.3.6.1.2.1.25.2.1.20) for the

local/rules/discovery/ic-hostresources-mib2-other.asl

9.4.2.15

Fixed Defects


15




Hypervisor (1.3.6.1.4.1.6876.4.1).

IS-9181/ SR 87068124

Non-existing AggregateLink is created.

The AggregateLinks, which are created as part of logical connections and does not have any physical connections, are removed.

discovery/adapter/ic-post-cleanup.asl

9.4.2.15

IS-9546/ SR 08025664

Need to have ways to disable Impact Propagation for devices on the same IP Subnetwork.

As part of the feature enhancement, the following setting has been introduced in the Polling and Threshold window: Group: IPNetwork IPNetwork Impact Propagation Group Setting: IPNetwork_ImpactPropagation_Setting Note: To get the preceding group populated, execute the following command: <BaseDir>/IP/smarts/bin>sm_adapter -s <server> -b <broker> -f BASEDIR/IP/smarts/local/conf/discovery/settings.conf icf/init-settings.asl The user can add the IPNetwork under this newly created group and choose to either enable/disable impact propagation through the attribute: “ImpactPropagation”. Once this value is set (either enable/disable), a reconfigure is essential for the respective attribute: “isImpactPropOverIPNetworkEnabled” to reflect the same Boolean value (TRUE/FALSE). Then, the newly generated event or the existing event will have the refined list of impacts as per the settings applied.

local/rules/discovery/ipNetwork-impact-prop-setting.asl local/conf/discovery/settings.conf local/lib/libsm_icim.so local/lib/libsm_health.so local/lib/libsm_discovery.so

9.4.2.15

Fixed Defects


16




IS-8378/ SR 85638724

ASL error occurs in IP, during discovery in ic-protocol-discovery.asl. When lite synchronization is enabled in BGP domain.

Code has been enhanced to handle the IP and Interface objects properly.

local/rules/discovery/ic-protocol-discovery.asl

9.4.2.11

IS-5417/ SR 76021426

Smarts IP Juniper port is removed after rediscovery.

The history table is handled to retain the ports that are created as part of different source (like: BRIDGE, LAG, LLDP, STACK).

local/rules/discovery/ic-juniper-mib-port.asl

9.4.2.11

IS-9021/ SR 84969162

Polling delayed for devices with TRUNK connection.

The polling_interval which was used as a global variable. It only holds the latest value that corresponds to the last network adapter processed in the loop. As part of the fix, the right polling interval was passed when setting the instrumentation object to the accessor.

local/rules/health/adapter-setting.asl

9.4.2.11

IS-7521 SR 06385178

Physical device and its virtual router share IP. After rediscovery, IP is randomly seen as duplicate and removed from agent address list.

The discovery logic for virtual routers has been modified to exclude the IPs being classified as duplicate IP between the physical routers to the virtual ones.

local/rules/discovery/ic-name-resolver.asl

9.4.2.11

IS-7447 SR 81998476

Unable to manage Spanning Tree and Bridge Probe layer-2 protocols

The STP instrumentation logic has been refined to fetch the right STP key so the monitoring sub-system is able to poll the status of STPNodes through specific STPKey key.

local/rules/devstat/sys-setting.asl

9.4.2.11

IS-8865 SR 86096344

Memory counters are not interpreted correctly for notification generation, it uses 32bits Gauge instead of 64bits.

Device sysoid (.1.3.6.1.4.1.9.1.1658 - Cisco CRS-8SB) health driver has been changed to look up for 64 bit counters cempMemPoolHCUsedOID { ".1.3.6.1.4.1.9.9.221.1.1.1.1.18" } ) as 1st priority and then fall back to look up 32 bit counters (cempMemPoolUsedOID { ".1.3.6.1.4.1.9.9.221.1.1.1.1.7" } ) for creating memory instances associated with this device.

local/conf/oid2type_Cisco.conf

9.4.2.11

Fixed Defects


17




IS-8837 SR 86455718

Validation of IP log message during a discovery.

HostResrcs-MIB2-Checkpoint-Processor-Driver has been revamped to not delete the CPU instances as part of multiple CPU creation driver and streamlined the health driver and HostResource driver to only create the respective components than getting mixed up between these two driver.

local/rules/ic-health-ilo.asl local/rules/ic-hostresources-Compaq-proc.asl local/rules/ic-hostresources-mib2-checkpoint-proc.asl local/conf/discovery/DISCOVERY_COMPAQ.import local/conf/discovery/DISCOVERY_GENERIC.import

9.4.2.11

IS-7072 SR 80573488

Receiving duplicate tickets on the clarify queue from SMARTS.

Set HasSingleEndPoint flag on hosts by default to FALSE to avoid duplicate alerts.

lib/libsm_icim.so 9.4.2.11

IS-8479 AggregateInterface Support for ISIS.

Added support for AggregateInterface class in ISIS domain.

lib/libsm_msi.so rules/isis/ic-isis-ipv6.asl

9.4.2.11

IS-7236 SR 81760610

Juniper MX series temperature Sensor discovery logic needs to be changed, due to issue in DISCOVERY_JUNIPER.import file.

Added code to create temperature sensor when the temperature value is not zero.

Conf/discovery/DISCOVERY_JUNIPER.import Rules/discovery/ic-juniper-MXseries-health.asl

9.4.2.11

IS-8551 SR 7163952

Two out of five IPv6 addresses are not discovered.

Added check to avoid tagging on IPv6 addresses.

Rules/discovery/ic-juniper-ip-tag.asl

9.4.2.11

IS-8282/ SR 06644431

The router DOWN alarm is not getting generated.

Code has been modified to generate router DOWN alarm by avoiding the conflicting and exclusive symptoms to be listed together for the same problem. And, take away peer system MightBeDown from the symptom list for the interface Down problem.

local/lib/libsm_icim.so 9.4.2.9

IS-8284/ SR 06340724

When the Smarts IP card is down, the interface belonging to the sub card on this parent card is not suppressing the DOWN notification.

The certainty has been increased for the NetworkAdapter Down symptom that is realized by the card while computing the Card DOWN problem. This avoids the unnecessary interfae DOWN problem when the reaslizedBy card is DOWN.

local/lib/libsm_icim.so 9.4.2.9

IS-8239/ SR 06661874

The Alcatel-Timex-7750SR12-driver definition in the

The containment driver definition for Containment-Alcatel-Timex-7750SR12-Driver was having a bug. As

local/conf/discovery/DISCOVERY_ALCATEL.import

9.4.2.9

Fixed Defects


18




DISCOVERY_ALCATEL.import is incorrect.

part of the fix, the drivers are rearranged and priority is altered.

IS-8046/ SR 82160000

The FileSystem calculations are not correct for some devices which use NetSNMP agent sysOID .1.3.6.1.4.1.8072.3.2.10.

For sysOid "1.3.6.1.4.1.8072.3.2.10", code has been written to select the type of instrumentation class based on the host type (which is a normal host, firewall). For this, the value of sysOid ".1.3.6.1.4.1.2620.1.1.21" (fwProdName) has been pulled first and checked if its value is "firewall". If it’s a firewall, the instrumentation class is overridden with "FileSystem_Performance_HostResources".

ic-hostresources-checkpoint-other.asl DISCOVERY_GENERIC.import

9.4.2.9

IS-8043/ SR 84371510

The ic-cisco-loadbalancer-ace.asl script logic needs to be changed because during the devices rediscovery, Smarts concatenates the card serial number in the location attribute which is multiplying it.

Code has been modified to populate the card serial number which was getting appended indefinitely during multiple discoveries.

local/rules/discovery/c-cisco-loadbalancer-ace.asl

9.4.2.9

IS-7977/ SR 82822850

IP and interface are not discovered for the IXIA device.

There are multiple rules that match against various formats that follow the ifIndex in the IP table. All these matching rules are a slightly variant of the other. The common flaw in all these rules are how the IP address is parsed. The IP address matched as a word. This does not strictly enforce the a.b.c.d format for the IP address. Even an "a.b.c" matches for an IP address. Because of the flaw, the entries are matched against different unintended rule. This results in certain IP/interfaces not being created. As a fix, the a.b.c.d format is strictly checked in the parsing rules.

local/rules/atuo-discovery/ic-ns-data.asl

9.4.2.9

IS-7914/ SR 05809041

The system VLAN tag groups are not supported

The VLAN tagging logic has been implemented to those

local/rules/discovery/ic-cisco-cvi-vlan.asl

9.4.2.9

Fixed Defects


19




for /Router/.1.3.6.1.4.1.9.1.1935.

devices that have been certified to create Vlans using "Cisco-CVI-Vlan" driver.

IS-7869/ SR 79879638

Many false positive notifications are generated during rediscovery.

It was found that some of the IPs in the AgentAddressList were virtual IPs. Ideally, the virtual IPs need not be the part of AgentAddresList. Also, only these virutal IPs were causing the AgentAddressList to be different across discoveries. The ic-end-virtualip.asl file that prunes virutal IP and the device relationship uses the agentObj LayeredOver relationship and check if any of these IPs is virtual. If so, it removes the virtual IP and device association and remove it from the agentAddressList. The problem in using the LayeredOver relation is that it doesn't have all the Virtual IPs that are associated to the device (the size of LayerdOver IPs is limited by maxNumberOfAgentAddress flag). So, some of the virtual IPs still end up being part of the agentAddressList.

The ic-end-virtualip.asl has been fixed to use the UCS HostsAccessPoint relationship so that all the virtual IPs are removed from the agentAddressList.

local/rules/discovery/ic-end-virtualip.asl

9.4.2.9

IS-7842/ SR 82959280

Smarts IP shows wrong FS details in the containment view of the device.

The containment view in SAM now does not match to the IP domain's FileSystem description attribute rather than the root attribute.

local/conf/maps/MAP-CONTAINMENT.import

9.4.2.9

IS-7722/ SR 05674826

Physical device and its virtual router share IP. After rediscovery, IP is randomly seen as duplicate and removed from agent address list.

The discovery logic for virtual routers has been modified to exclude the IPs being classified as duplicate IP between the physical routers to the virtual ones.

local/rules/discovery/ic-name-resolver.asl

9.4.2.9

IS-7714/ SR 05499710

Existing notifications are cleared and notified

When "Interface Management Policy" is applied to an

local/rules/discovery/if-provision-setting.asl

9.4.2.9

Fixed Defects


20




again as an instrumentation is deleted during domain reconfigure.

interface group and when the Unmanaged setting is applied to that group, the EXPLICITLY_MANAGED interfaces are getting set to Unmanaged. As part of the fix, additional condition check has been made in file "if-provision-setting.asl" for the explicitly_managed interfaces.

IS-7691/ SR 82566722

Recertification is needed for the discovery of all CISCO devices currently certified for IPv6.

Modified logic has been added in the file ic-cisco-ipv6.asl where we selectively ignore creating IPv6 objects created using CISCO-IETF-IP-MIB as claimed by CISCO. And, we only retain the IPv6 objects created through the generic Mibs.

local/rules/discovery/ic-cisco-ipv6.asl

9.4.2.9

IS-7671/ SR 79280834

The aggregation ports are not created for CISCO UCS when CLI credential are supplied.

As the aggregation ports are for Nexus 6K, devices are created via CLI probing. And, the same nexus 6K device (which is .1.3.6.1.4.1.9.12.3.1.3.1063) is excluded from the EtherChannel probe.

local/conf/discovery/DISCOVERY_GENERIC.import

9.4.2.9

IS-7670/ SR 81493316

The AggregateInterface class notification is missing.

When a WAN link is established at the LACP identified interfaces, the WAN link created between the same indexes is removed to avoid duplicate connection representation of the same WAN link.

local/rules/ic-post-lag.asl 9.4.2.9

IS-7283/ SR 04695661

The IP tagging and shadowing affect the device discovery.

Altered the internal logic while performing findIP to avoid duplicate key insertion into the MR_AnyVal structure.

local/lib/sm_autodiscovery.so

9.4.2.9

IS-7629/ SR 0502205

Verizon reports false DOWN alerts on multiple devices that last only one polling cycle.

The solution is for XDIP domain. And, from the IP domain perspective, there is an additional attribute introduced for the partition class "lastPartitionCreatedAt" that reflects the timestamp of the partition created which is utilized by the XDIP domain.

local/lib/libsm_discovery.so local/lib/libsm_icim.so

9.4.2.9

IS-7577/ SR 9090

The polling and the threshold matching

The polling and the threshold matching criteria for proxy

local/conf/icim/settings.conf

9.4.2.9

Fixed Defects


21




criteria for proxy devices are incorrect.

devices have been changed from Isproxy to Domain.

IS-7401/ SR 82292716

An Instrumentation for the EXPLICITLY_MANAGED vPorts for CISCO Nexus1KV is deleted by ic-post-port-manager.asl.

Added further logic to check for managedState for Nexus1K devices in ic-post-port-manager.asl.

local/rules/discovery/ic-post-port-manager.asl

9.4.2.9

IS-6295/ SR 78602150

The temperature alerts occur on the Nexus devices.

Exposed UseMIBThresholds attribute under generic TemperatureSensor settings in P&T tab.

local/lib/sm_health.so 9.4.2.9

IS-6514/ SR 77748956

After upgrading to CISCO NX-OS switch to revision m9100-s3ek9-mz, version 6.2(13a) receives incorrect card down alerts.

While creating card using "Performance-Entity-Driver" using oid: entPhysicalClass (.1.3.6.1.2.1.47.1.1.1.1.5), SMARTS checks the Card status using cefcModuleOperStatus {".1.3.6.1.4.1.9.9.117.1.2.1.1.2"}. And, for only indexes that has the status populated, the respective cards are created.

local/rules/ic-entity-health.asl local/conf/DISCOVERY_GENERIC.import

9.4.2.9

Fixed SAM specific defects

Table 6. Fixed SAM specific defects



Patch Release


IS-9691/

SR 08645777

The HostedBy relationship of IP address instances is null in OI.

When there are multiple book keeping from the same source for the relationship, it must avoid the null, invalid value.

/local/lib/libsm_sam_common.so

9.4.2.15

IS-9345/

SR 08194171

Unable to launch web Console.

There were issues with Jar signing, which has been addressed.

Note: It is recommended to upgrade the SAM Console from 9.4.2.x to 9.4.2 patch 12.

JAR files (.jar file) 9.4.2.12

IS-8489/

SR 07021932

SAM services do not respond.

After every topology sync, the additional escaping added to

Ics/ics-adapters.ics-topology-sync.asl

9.4.2.12

Fixed Defects


22



Patch Release

the topology buffer is removed.

IS-8972/

SR 07729176

After the upgrade to 9.4.2 patch 9, the edaaClientConnect.conf file is not present in the <BASE-DIR>/smarts/conf, and is not being passed to tomcat.

Code has been modified to build the sub-system, by disabling the deletion of edaaClientConnect.conf file.

ROLLING_PATCH.uip 9.4.2.12

IS-8346/

SR 06477937

NOTIF issue occurs without delaying notifications.

Code has been added to change the behavior, where Auto-Acknowledge was calling changed function on the notification even if the notification is in the Active state.

ics-event-processing.asl

ICS_Notification_Impl.c

9.4.2.12

IS-9036/

SR 07496357

Acknowledge state is different between SAM services.

The notification property updation is done after the notify method is invoked on a notification, which prevents the acknowledged-active notification received from aggregate-sam to be set active-unacknowledged notification in presentation-sam.

ics-nl-processing.asl 9.4.2.12

IS-7120/

SR 81325424

Alerts are not in synchronization between the SAM layers.

The problems being addressed are: • Mismatch of alerts

due to notifications from Trap and syslog adapter in OI Server.

• Mismatch of alerts due to InMaint and SchedMaint notifications.

• In case of Manual failover and Automatic failover, in the new standby OI Server, the alerts existing from Trap adapter and syslog adapter will be cleared.

• When the schedMaint and InMaint notifications are cleared, those notifications gets acked by MBIM server, along with the ack operation, the changed operation is also invoked on the notification which allows the ack message to be propagated to standby servers. This allows the cleared InMaint and SchedMaint alerts to be archived.

• smarts/failover/rules/failover-monitor.asl

Smarts/failover/rules/clearStaleAlerts.asl

• smarts/mbim/rules/ics-maint.asl

9.4.2.12

Fixed Defects


23



Patch Release

IS-8106/ SR 84438338

The dynamic model error message appears when the user tries to bring over the ‘Type’ properties from interface class in the IP domain into the SAM domain.

The 'Type' attribute has been removed from the ‘TransportConnector’ model class which eliminates the dynamic model error message.

libsm_sockserv.so 9.4.2.9

IS-7973/ SR 84382184

(Smarts 9.4.2) (MnR6.7.1) (EMC SP for Smarts 2.2.1: Version 2.2.1) - The Failover manager version is not compatible with the latest version of Smarts Solution pack.

Failover manager had specific checks for 2.0 and 2.1 versions. This was added since the ways to update EDAA in MnR were different between both the versions. We now have removed the explicit checks and made it generalized since post 2.1, the mechanism to update EDAA remains the same.

failover/java/com/emc/util/MNRServer.java

9.4.2.9

IS-8058/ SR 83809604

The additional source-notify messages are seen in SAM when there is no notify message seen in the underlying domains.

The ics-nl-processing.asl file has been modified to prevent invoking ICS_Notificaiton::notify, when the notification from the same source exists as active notification in the SAM/oi server.

ics-nl-processing.asl 9.4.2.9

IS-8333 a) The action scheduler thread gets into a forever loop when the expiration time for a notification provided is a huge value which overflows signed integer value.

b) Race condition issue exists in HyperNotif driver which prevents events being cleared, when a domain is disabled and reconfigured.

a) The fix is to avoid scheduling of expiration of notifications when the expiration interval is invalid.

b) The race condition for the Hyper Notif driver stopping process has been fixed, which allows all the notifications to be cleared while disabling and reconfiguring the domain.

a) ics/xml-config-handlers/DomainHandler_Impl.c Modified library : libsm_ics_xml_conf.so

b) ics/ems/ICS_ActionScheduler_Impl.c

Modified library : libsm_ics_ems.so

9.4.2.9

Fixed Defects


24

Fixed VoIP specific defects Table 7. Fixed VoIP specific defects



Patch Release


IS-8836/ SR 07459316

Smarts VoIP 9.4.2.9 fails to monitor CUCM 10.5 phones' status. The status is displayed as Unknown.

The instrumentation soap.xml code has been modified to pick up the correct AXL port number from settings.

classes/voip_cisco_axl.jar classesvoip_cisco_axl-javadoc.jar

9.4.2.12

IS-8244/ SR 85240044

Production VOIP service crashes.

Cleanup code has been added when socket bind fails.

lib/libsm_clsapi.so 9.4.2.12

IS-8193/ SR 84304972

IPPhones status changes from REGISTERED to UNKNOWN.

Sometimes, Cisco CUCM does not recognize IP address as NodeName in Soap queries that results into monitoring of IPPhone failure. To resolve this, NodeName parameter is populated with AgentSysName, rather than IP address. This has been achieved by setting CallAgentDiscovered with the AgentSysName when there is a change in phone registration.

voip-cisco-controller.asl 9.4.2.12

Fixed MPLS specific defects

Table 8. Fixed MPLS specific defects



Patch Release


Fixed NPM specific defects Table 9. Fixed NPM specific defects





Fixed Defects


25




IS-8376/ SR 85478892

FALSE MTUMisMatch alert appears because the IOS device do not add Layer 2 header in MTU.

The dxa, model files, and ASL files have been modified to add correct Layer 2 header size to the MTU on IOS devices before comparing.

rules/ospf/ic-ospfv3-interfaces.asl rules/ospf/ic-ospf-interfaces.asl conf/ospf/dxa-am-v4v6.conf conf/ospf/dxa-am.conf lib/libsm_msi.so lib/libsm_rpsm_ospf.so

9.4.2.12

IS-8226/ SR 6628250

Parsing issue occurs when the SNMP agent returns empty VRF name.

The asl file has been modified to handle and ignore the empty VRF name.

rules/ospf/is-ospf-vrf.asl rules/bgp/is-bgp-vrf.asl

9.4.2.12

IS-8336/ SR 82414920

The OSPF interface events are not generated at endpoint.

Changes has been done to handle SNMP error conditions properly. Like in this case, snmp oid poll throws errors when the interfaces is disabled and NPM generates unnecessary alarm based on this error condition. Same has been handled with this fix.

rpm-ospf /model/OSPF_Instrumentation.mdl rpm-ospf /model/OSPF.mdl

9.4.2.9

IS-8483 AggregateInterface Support for ISIS.

Added support for AggregateInterface class in ISIS domain.

lib/libsm_msi.so rules/isis/ic-isis-ipv6.asl

9.4.2.9

ER 505/ SR 81639594, 83457748

VRF BGP/OSPF sessions are not discovered and monitored.

In order to enable this feature, set the VRFEnabled flag to TRUE (by default it is FALSE) for BGP and OSPF in the respective files given below:

BGP : <smarts>/conf/bgp/bgp.conf

OSPF : <smarts>/conf/ospf/ospf.conf

Also, In GUI VRFEnabled attribute is introduced in MSI_AdapterManager class.

rules/isis/ic-bgp-cisco-ipv6-peers.asl rules/isis/ic-bgp-default-probe.asl rules/isis/ic-bgp-juniper-ipv6-peers.asl rules/isis/ic-bgp-peers.asl rules/isis/ic-bgp-post.asl rules/isis/ic-bgp-vrf.asl lib/libsm_msi.so

lib/libsm_rpsm_bgp.so

lib/libsm_rpsm_ospf.so

conf/bg/bgp.conf

conf/bgp/BGP.import

conf/ospf/ospf.conf

conf/ospf/OSPF.import

9.4.2.9

Fixed Defects


26




Note: You must install IP 9.4.2 Patch 4 before using this feature.

rules/ospf/ic-ospf-default-probe.asl

rules/ospf/ic-ospf-interfaces.asl

rules/ospf/ic-ospf-post.asl

rules/ospf/ic-ospf-virtual-interfaces.asl

rules/ospf/ic-ospf-vrf.asl

rules/ospf/ic-ospfv3-interfaces.asl

rules/ospf/ic-ospfv3-virtual-interfaces.asl

IS-6828/ SR 80425716

BGP is shutting down abruptly (with core dump) due to FD growth.

Changes has been made to handle exception when a device with SNMP V3 does not have a username.

lib/libsm_snmpwalk.so 9.4.2.9

IS-7314/ SR 04845027

BGP Peer sessions with Peer ID 0.0.0.0 were not being discovered.

Made a configurable feature to enable users to set flag DiscoverBGPSessionWithoutPeerID to True in <smarts>/bgp/bgp.conf file.

rules/bgp/ic-bgp-cisco-ipv6-peers.asl rules/bgp/ic-bgp-juniper-ipv6-peers.asl rules/bgp/ic-bgp-peers.asl

lib/libsm_msi.so

conf/bg/bgp.conf

9.4.2.9

IS-7272/ SR 81991444

BGP Session Flapping event was not being generated when trap received.

Code added to handle trap count for each trap received.

rules/bgp/bgp-traps.asl rules/bgp/ic-bgp-post.asl

9.4.2.9

Fixed ESM specific defects Table 10. Fixed ESM specific defects



Patch Release


IS-9796/ SR 88896838

The F5 Loadbalancer Pool events is not generated post ESM 9.4.2 patch 12 implementation.

There is no need to update OS version again by HostResources MIB-2 data, as the OS version for F5 specific device is getting

ic-hostresources-f5-other.asl

9.4.2.15

Fixed Defects


27



Patch Release

updated in the containment driver itself.

IS-9074/ SR 07880320

There is a lack of CPU FileSystem memory (and other features) for managed hosts on ESM Topology.

The user can create WMI credential using hostname or FQDN or IP address in host field, and perform the discovery.

esm/model/cluster/GA_WMIFE.mdl esm/model/cluster/GA_WMIFE_Impl.c esm/rules/wmi/wmi-tpmgr-discovery.asl esm/model/cluster/WMI_Discovery.mdl esm/model/cluster/WMI_Discovery_Impl.c

9.4.2.12

IS-9097/ SR 07864248

The PrimaryOwnerContact attribute is not populated with data.

The PrimaryOwnerContact attribute has been populated in ESM on host entities.

esm/conf/init/dxa-am.conf 9.4.2.12

IS-7476/ SR 5162222

ESM and IP are reporting some virtual machines on the vCenter: some virtual machines on the vCenter are properly reported as virtual, and whereas some are reported as physical servers.

Cluster names are reused across different data centers which have been fixed now.

local/classes/logger-0.0.1.jar

9.4.2.12

IS-8183/ SR 06228280

Event correlation does not work for VirtualMachine class.

Code has been modified as follows:

1. If the host (HostType = VIRTUAL and member of Partition) in IP becomes unresponsive, the VM in ESM which virtualizes the host would generate “Virtual Machine Down” event.

2. If the host (HostType = VIRTUAL and member of Partition) in IP becomes unresponsive and the partition to which it belongs is Down, then the VM in ESM which virtualizes the host

IP:

ICIM_Network.mdl

ESM:

MSI.mdl

vm.mdl

9.4.2.9

Fixed Defects


28



Patch Release

would clear the “Virtual Machine Down” event.

3. If the switch is down, the ESX host and VM hosts become unresponsive in IP. Howevre, the VM down is not generated from ESM. The impact of Switch Down would not display that VM has been impacted. This is as per the existing design.

IS-8303/ SR 84196536, 6546943

ESM shows applications against ICMPONLY hosts with no SNMP or WMI access.

Model has been modified to create processData based on thread ID and the host name unlike the earlier way of creating it using just the thread-id. With the earlier approach, it was possible that the same thread ID in future process an ICMP host and hence it may create same processes for the ICMP host which belong to SNMP host. Now with this fix, process Data is created with UcsName along with the threadId.

esm\rules\serviceProcess\app-template-discovery.asl msi-esm\MSI_Impl.c

9.4.2.9

IS-8207/ SR 5703542

The Smarts Server Manager displays IncompleteNetworkConfiguration alarm for sfda18-dc1-bcs and sfda18-dac1-bcs.

Code has been added to provide support for vNIC type E1000e and create relationship with vSwitch.

esm_vcenter.jar 9.4.2.9

IS-8007/ SR 83051280

Receiving notifications of high utilization on processor groups that cannot be matched by scripts to the parent host objects. This disrupts the process where tickets are automatically opened and

The fix is to clean up the ESM topology that has orphan processor/memory groups. Also, the processor/memory group that is already being exported from IP domain is to be deleted if the same are getting created in ESM

local/rules/esm/esm-init.asl

9.4.2.9

Fixed Defects


29



Patch Release

emails are sent to the user.

domain by setting the EnableCPUFilesystemMemoryDiscovery to TRUE.

IS-8267/ 06728433

Following problems were observed when the user upgraded ESM from 9.4.1 to 9.4.2.2 version.

This can be true in case if user upgrades from any other version to 9.4.2.2.

1. Applications were getting created on ICMPONLY hosts.

2. After loading the application data (APP-<hostname>.txt) files, the existing applications were removed on discoverAll/discovery/sync.

3. After upgrade, the template names and the relationship to associated templates were not retained on the applications which were created on the hosts via the application templates.

4. Unwanted processes part of SNMP host were getting recreated on the ICMPONLY host which resulted in to many application missing events on the topology.

1. In order to remove the application from the ICMPONLY host, the CleanRougeApplications flag is introduced in the esm-param.conf file. You can find the esm-param.conf file under $SM_HOME/local/conf/esm folder.

If the CleanRougeApplications flag has a value FALSE, ESM removes all rouge applications only on the ICMPONLY hosts.

If the CleanRougeApplications flag has a value TRUE, ESM removes all the rouge applications from all the host with accesstype as ICMPONLY, SNMPONLY and ICMPSNMP, however ESM server recreates the legitimate applications belonging to applied template on the host if the host has the application still running.

Note: Once all the rouge applications are removed from ESM server and the discovery is completed on ESM server, it is advised to set the CleanRougeApplications to FALSE in order

Config file : esm/conf/init/esm-param.conf

ASL files :

esm/rules/init/esm-post.asl

esm/rules/serviceProcess/app-template-discovery.asl

esm/rules/serviceProcess/autoconfig-setting.asl

esm/rules/serviceProcess/create_config_from_file.asl

esm/rules/serviceProcess/process_host_monitor_config_file.asl

Model files : msi-esm/MSI.mdl

msi-esm/MSI_Impl.c

9.4.2.9

Fixed Defects


30



Patch Release

to avoid the removal of application from the non ICMP host in case.

To check the value of CleanRougeApplications, execute the following command:

./dmctl -b localhost:5000 -s ESM invoke ESM_Params::ESM-Params findParameter CleanRougeApplications | tee

To set the value of CleanRougeApplications to TRUE:

./dmctl -b localhost:5000 -s ESM invoke ESM_Params::ESM-Params insertParameter CleanRougeApplications TRUE | tee

To set the value of CleanRougeApplications to FALSE:

./dmctl -b localhost:5000 -s ESM invoke ESM_Params::ESM-Params insertParameter CleanRougeApplications FALSE | tee

2. The version 9.4.1 did not have the templateRow present in the process data files (txt). And, on upgrade, the templateRow value changes to 0 which

Fixed Defects


31



Patch Release

was causing the applications to be removed from the host on loading of process data files.

3. The templateName was getting overwritten to empty in case if user loads the process data files from while upgrading. So in order to retain the process templateName, the templateName is being read while processing the host monitor config file.

4. The Application::remove() code is added to clean the ESM_ProcessMonitoring_Setting of the host in case if the application is removed and the same does not get reused during discovery or monitoring.

Fixed OTM specific defects

Table 11. Fixed OTM specific defects



Patch Release



32

Certified devices

This section describes the devices certified and the certification impact in this patch:

Simple certifications Simple certification involves only in configure file changes and the qualification of new OID in the currently existing driver. This section describes the devices certified in this patch.

Table 12. Simple devices certified in the patch

SR /TASC Number

Vendor Name Description Patch Release

304029 Cisco CISCO SYSTEMS cBR-8 .1.3.6.1.4.1.9.1.2141 9.4.2.15

304037 Cisco CISCO SYSTEMS NCS-5501 .1.3.6.1.4.1.9.1.2432 9.4.2.15

303212 Cisco CISCO SYSTEMS ASA5515-X .1.3.6.1.4.1.9.12.3.1.3.1420

9.4.2.15

303218 Juniper Juniper SRX5400 .1.3.6.1.4.1.2636.1.1.1.2.105 9.4.2.15

303227 Cisco CISCO SYSTEMS AIR-CT8540-K9 .1.3.6.1.4.1.9.1.2171

9.4.2.15

303261 Cisco Cisco 887 .1.3.6.1.4.1.9.1.848 9.4.2.15

303263 Juniper Juniper Networks SRX320-1 .1.3.6.1.4.1.2636.1.1.1.2.134

9.4.2.15

303264 Cisco CISCO SYSTEMS C819-GNCF .1.3.6.1.4.1.9.1.2309 9.4.2.15

303280 Aruba Aruba7010-US .1.3.6.1.4.1.14823.1.1.40 9.4.2.15

303291 Avaya Avaya DEWIL1MAS107 .1.3.6.1.4.1.6889.2.42.1.1.0

9.4.2.15

303293 Cisco Cisco C2960 .1.3.6.1.4.1.9.1.1750 9.4.2.15

303298 Cisco CISCO SYSTEMS SBI-MUM-N93120-CL3-C2-RB .1.3.6.1.4.1.9.12.3.1.3.1675

9.4.2.15

303299 Huawei Huawei S5710-28C-EI .1.3.6.1.4.1.2011.2.23.167 9.4.2.15

303300 HP HP-A6602 .1.3.6.1.4.1.25506.11.2.55 9.4.2.15

303301 H3C H3C MSR920 .1.3.6.1.4.1.25506.1.524 9.4.2.15

303316 Cisco CISCO SYSTEMS C880 .1.3.6.1.4.1.9.1.1856 9.4.2.15

303323 H3C H3C MSR900 .1.3.6.1.4.1.25506.1.523 9.4.2.15

Certified devices


33

SR /TASC Number


303332 CheckPoint CheckPoint x3550M3 .1.3.6.1.4.1.2620.1.6.123.1.49

9.4.2.15

303335 Cisco Cisco ASR920 .1.3.6.1.4.1.9.1.2155 9.4.2.15

303336 Cisco Cisco ASR920 .1.3.6.1.4.1.9.1.2159 9.4.2.15

303337 Cisco Cisco ASR920-24SZM .1.3.6.1.4.1.9.1.2102 9.4.2.15

303338 Cisco Cisco ASR920 .1.3.6.1.4.1.9.1.2158 9.4.2.15

303339 CheckPoint CheckPoint 15600 .1.3.6.1.4.1.2620.1.6.123.1.64 9.4.2.15

303365 HP HP 5930-2Slot+2QSFP+ .1.3.6.1.4.1.25506.11.1.229

9.4.2.15

303466 Juniper Juniper Networks vSRX .1.3.6.1.4.1.2636.1.1.1.2.129

9.4.2.15

303471 HP HP 5920AF-24XG .1.3.6.1.4.1.25506.11.1.78 9.4.2.15

303504 BlueCoat BlueCoat SSLV2800 .1.3.6.1.4.1.3417.1.5.3 9.4.2.15

303549 Cisco CISCO SYSTEMS ciscoASASm1 .1.3.6.1.4.1.9.1.1277

9.4.2.15

303559 CheckPoint CheckPoint Smart-1-3050 .1.3.6.1.4.1.2620.1.6.123.1.53

9.4.2.15

303591 CheckPoint CheckPoint-Secure .1.3.6.1.4.1.2620.1.6.123.1.37

9.4.2.15

303594 Huawei Huawei Eudemon8000E-X .1.3.6.1.4.1.2011.6.122.8.11.2

9.4.2.15

303595 CheckPoint CheckPoint Appliance 23800 .1.3.6.1.4.1.2620.1.6.123.1.62

9.4.2.15

303597 BlueCoat Bluecoat SSLV 1800-C .1.3.6.1.4.1.3417.1.5.2 9.4.2.15

303600 Cisco CISCO SYSTEMS UCS6324 .1.3.6.1.4.1.9.12.3.1.3.1454

9.4.2.15

303601 Cisco Cisco ASR9904 .1.3.6.1.4.1.9.1.1762 9.4.2.15

303606 Arista Arista DCS-7050SX-72Q .1.3.6.1.4.1.30065.1.3011.7050.3741.72.2512

9.4.2.15

303619 Arista Arista DCS-7504N .1.3.6.1.4.1.30065.1.3011.7504.1359

9.4.2.15

Certified devices


34

SR /TASC Number


303620 Arista Arista DCS-7050TX-72Q .1.3.6.1.4.1.30065.1.3011.7050.1958.72.2512

9.4.2.15

303621 Arista Arista DCS-7280SR-48C6 .1.3.6.1.4.1.30065.1.3011.7280.3735.48.2878.6

9.4.2.15

303628 Dell Dell S6100 .1.3.6.1.4.1.6027.1.3.28 9.4.2.15

303635 HP HP 5700-24G-40XG-2QSFP+ .1.3.6.1.4.1.25506.11.1.172

9.4.2.15

303638 Opengear Opengear IM-7216-2-DAC .1.3.6.1.4.1.25049.1.61 9.4.2.15

303644 ACME ACME Net-Net-4600-ECZ7 .1.3.6.1.4.1.9148.1.1.3 9.4.2.15

303646 Brocade Brocade 6910 .1.3.6.1.4.1.1991.1.16.1 9.4.2.15

303652 F5 F5 bigip10255 .1.3.6.1.4.1.3375.2.1.3.4.99 9.4.2.15

303658 Cisco CISCO SYSTEMS ASA 5515 .1.3.6.1.4.1.9.1.1420 9.4.2.15

303660 Geist Geist PDU .1.3.6.1.4.1.21239.5.2 9.4.2.15

303674 Cisco CISCO SYSTEMS 831 .1.3.6.1.4.1.49736 9.4.2.15

303675 Arista Arista DCS-7280SR2A-48YC6 .1.3.6.1.4.1.30065.1.3011.7280.3735.2.3648.48.1654.6

9.4.2.15

303681 Polycom Polycom VD .1.3.6.1.4.1.2684 9.4.2.15

303689 Dell Dell PowerConnect-N4032 .1.3.6.1.4.1.674.10895.3042

9.4.2.15

303705 Cisco CISCO SYSTEMS Nexus-3172TQ .1.3.6.1.4.1.9.12.3.1.3.1389

9.4.2.15

303709 Cisco Cisco Controller .1.3.6.1.4.1.9.1.2170 9.4.2.15

303736 Cisco Cisco 3560CX-12PC-S .1.3.6.1.4.1.9.1.2134 9.4.2.15

303769 Cisco CISCO SYSTEMS ASR1009X .1.3.6.1.4.1.9.1.2144 9.4.2.15

303770 Viptela Viptela vEdge-100m-VZ .1.3.6.1.4.1.41916.3.2.10 9.4.2.15

303783 HP HP-ProCurve-J9449A .1.3.6.1.4.1.11.2.3.7.11.103 9.4.2.15

303785 Cisco CISCO SYSTEMS IE1000 managed Industrial switch .1.3.6.1.4.1.9.1.2331

9.4.2.15

Certified devices


35

SR /TASC Number


303788 Cisco CISCO SYSTEMS N5K-C5696Q .1.3.6.1.4.1.9.12.3.1.3.1539

9.4.2.15

303795 McAfee McAfee ACE-VM32 .1.3.6.1.4.1.23128.1000.11.1 9.4.2.15

303796 McAfee McAfee ETM-VM12 .1.3.6.1.4.1.23128.1000.1.1 9.4.2.15

303797 McAfee McAfee ELM-VM12 .1.3.6.1.4.1.23128.1000.7.1 9.4.2.15

303798 McAfee McAfee ERC-VM12 .1.3.6.1.4.1.23128.1000.3.1 9.4.2.15

303799 Cisco CISCO SYSTEMS N9K-C93180LC-EX .1.3.6.1.4.1.9.12.3.1.3.1843

9.4.2.15

303801 HP HP5940 .1.3.6.1.4.1.25506.11.1.270 9.4.2.15

303802 HP HP-ProCurve-J9147A .1.3.6.1.4.1.11.2.3.7.11.87 9.4.2.15

303803 HP HP-ProCurve-J9450A .1.3.6.1.4.1.11.2.3.7.11.104 9.4.2.15

303808 CheckPoint CheckPoint-CPX .1.3.6.1.4.1.2620.1.6.123.1.61 9.4.2.15

303816 CheckPoint Checkpoint 13800 .1.3.6.1.4.1.2620.1.6.123.1.55 9.4.2.15

303818 Juniper Juniper MX480 .1.3.6.1.4.1.2636.1.1.1.2.25 9.4.2.15

303821 Cisco Cisco ASA5506-X .1.3.6.1.4.1.9.1.2114 9.4.2.15

303822 Cisco Cisco WS-C3650-48TD-E .1.3.6.1.4.1.9.1.1828 9.4.2.15

303824 Cisco CISCO SYSTEMS NEXUS 3132Q-XL .1.3.6.1.4.1.9.12.3.1.3.1726

9.4.2.15

303825 Sonus Sonus UX1000 .1.3.6.1.4.1.177.15.1.1.2 9.4.2.15

303826 Viptela Viptela vEdge-100b .1.3.6.1.4.1.41916.3.2.11 9.4.2.15

303827 Alcatel Alcatel 7302 ISAM DSLAM .1.3.6.1.4.1.637.61.1 9.4.2.15

303830 Pulse Secure Pulse Secure PSA-3000 .1.3.6.1.4.1.12532.256.2.1

9.4.2.15

303848 PALO-ALTO-NETWORKS PALO-ALTO-NETWORKS PA-5220-series .1.3.6.1.4.1.25461.2.3.24

9.4.2.15

303849 PALO-ALTO-NETWORKS PALO-ALTO-NETWORKS PA-5250 series .1.3.6.1.4.1.25461.2.3.23

9.4.2.15

303850 PALO-ALTO-NETWORKS PALO-ALTO-NETWORKS PAN-WF-500 .1.3.6.1.4.1.25461.2.3.33

9.4.2.15

Certified devices


36

SR /TASC Number


303851 APC APC SmartUPS2200 .1.3.6.1.4.1.318.1.3.14.11 9.4.2.15

303852 PALO-ALTO-NETWORKS PALO-ALTO-NETWORKS PA-850 .1.3.6.1.4.1.25461.2.3.37

9.4.2.15

303865 Fortinet Fortinet FortiSandbox 3000E .1.3.6.1.4.1.12356.118.1.30006

9.4.2.15

303878 Dell Dell PowerEdge R330 .1.3.6.1.4.1.21343.3.2.17 9.4.2.15

303893 Cisco Cisco NCS5501 .1.3.6.1.4.1.9.1.2429 9.4.2.15

303956 Alcatel Alcatel-7750-SR-c12 .1.3.6.1.4.1.6527.1.3.6 9.4.2.15

303961 REBASOFT Radware RA1000 .1.3.6.1.4.1.168.1.100 9.4.2.15

304020 Cisco CISCO SYSTEMS IOS-XRv 9000 .1.3.6.1.4.1.9.1.2264

9.4.2.15

Complex certifications Complex certifications involve recertification, new device certifications, and involve new driver creations or multiple file changes. This section describes the devices certified in this patch.

Table 13. Description of complex devices certified in the patch

SR /TASC Number


303711 F5 Certified the following components for the F5-4200V device (System OID: .1.3.6.1.4.1.3375.2.1.3.4.82): AggregatePort, Disk, Fan, FileSystem, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, VoltageSensor, and VLAN.

9.4.2.15

303997 F5 Certified the following components for the BigIP-LTM device (System OID: .1.3.6.1.4.1.3375.2.1.3.4.25): AggregatePort, Disk, Fan, FileSystem, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, and VLAN.

9.4.2.15

302833 Ciena Certified the following components for the Ciena-5142 device (System OID: .1.3.6.1.4.1.6141.1.96): Card, Fan, Interface, Memory, Port, PowerSupply, Processor, and TemperatureSensor.

9.4.2.15

Certified devices


37

SR /TASC Number


303391 Fujitsu Certified the following components for the Fujitsu Flashwave 7120 device (System OID: .1.3.6.1.4.1.18070.2.2): Card and Port.

9.4.2.15

303445 Linux Re-certified the following components for the Net-SNMP-Agent-5.1 device (System OID: .1.3.6.1.4.1.8072.3.2.10): Card, Fan, Interface, and PowerSupply.

9.4.2.15

303739 Dell Certified the following components for the Z9100 device (System OID: .1.3.6.1.4.1.6027.1.5.2): Card, Interface, Fan, Memory, Processor, Port, Temperature Sensor, and PowerSupply.

9.4.2.15

303740 Dell Certified the following components for the S4048T device (System OID: .1.3.6.1.4.1.6027.1.3.30): Card, Fan, Interface, Port, Memory, PowerSupply, Processor, and TemperatureSensor.

9.4.2.15

303741 Dell Certified the following components for the S6010 device (System OID: .1.3.6.1.4.1.6027.1.3.29): Card, FAN, Interface, Memory, Port, PowerSupply, Processor, and TemperatureSensor.

9.4.2.15

303754 Cisco Certified the following component for the N9K-C92160YC-X device (System OID: .1.3.6.1.4.1.9.12.3.1.3.1744): AggregatePort, Card, Fan, Memory, Port, PowerSupply, Processor, TemperatureSensor, VoltageSensor, and VLAN.

9.4.2.15

303800 Aruba Certified the following components for the 3810M 24G PoE+ 1-slot (JL073A) device (System OID: .1.3.6.1.4.1.11.2.3.7.11.174.3): Fan, Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, and VLAN.

9.4.2.15

303804 HP Certified the following components for the HP-ProCurve-J4122A-2400M device (System OID: .1.3.6.1.4.1.11.2.3.7.11.10): Fan, Memory, Port, Processor, and PowerSupply.

9.4.2.15

303805 HP Certified the following components for the HP-ProCurve-J4850A-5304XL device (System OID: .1.3.6.1.4.1.11.2.3.7.11.20): Aggregate-Port, Fan, Interface, Memory, PowerSupply, Processor, and VLAN.

9.4.2.15

303806 HP Certified the following components for the HP-ProCurve-J4905A device (System OID: .1.3.6.1.4.1.11.2.3.7.11.42): AggregatePort, Fan,

9.4.2.15

Certified devices


38

SR /TASC Number


Interface, Memory, Port, PowerSupply, Processor, TemperatureSensor, and VLAN.

303810 HP Certified the following components for the HP-ProCurve-J9776A-2530-24G device (System OID: .1.3.6.1.4.1.11.2.3.7.11.140): Fan, Interface, Memory, Port, PowerSupply, and Processor.

9.4.2.15

303829 Isilon Certified the following components for the Isilon-OneFS-X410 device (System OID: .1.3.6.1.4.1.12325.1.1.2.1.1): Disk, Fan, FileSystem, Interface, Memory, MemoryGroup, Processor, ProcessorGroup, TemperatureSensor, VoltageSensor.

9.4.2.15

303869 Juniper Re-certified the following components for the ERX1440 device (System OID: .1.3.6.1.4.1.4874.1.1.1.1.3): Interface, Card, Memory, TS, Processor, Fan, PS, and Virtual Router.

9.4.2.15

303895 Cisco Certified the following components for the UCS-C240-M4SNEBS device (System OID: .1.3.6.1.4.1.9.1.2179): Card, Fan, Disk, Interface, PowerSupply, TemperatureSensor, and VoltageSensor.

9.4.2.15

303902 Fortigate Certified the following components for the Fortinet FGT5101C device (System OID: .1.3.6.1.4.1.12356.101.1.51010): Interface/IPSec, CPU, and Memory.

9.4.2.15

303905 Fortigate Certified the following components for the Fortinet FGT5001B device (System OID: .1.3.6.1.4.1.12356.101.1.50013): Interface/IPSec, CPU, and Memory.

9.4.2.15

303906 Adtran Certified the following component for the Adtran NV838 device (System OID: .1.3.6.1.4.1.664.1.1005): Port.

9.4.2.15

303907 Adtran Certified the following component for the Adtran TA1248 device (System OID: .1.3.6.1.4.1.664.1.688): Interface.

9.4.2.15

303908 Adtran Certified the following component for the Adtran TA5006 device (System OID: .1.3.6.1.4.1.664.1.986): Interface.

9.4.2.15

Certified devices


39

SR /TASC Number


303909 Adtran Certified the following components for the Adtran TA1248V-4thGen-GigE-VDSL2 device (System OID: .1.3.6.1.4.1.664.1.1284): Interface and Port.

9.4.2.15

303910 Adtran Certified the following components for the Adtran TA1248A device (System OID: .1.3.6.1.4.1.664.1.1123): Interface and Port.

9.4.2.15

303911 Adtran Certified the following components for the Adtran TA1148V-VDSL2 device (System OID: .1.3.6.1.4.1.664.1.1268): interface/Port.

9.4.2.15

303913 CheckPoint Certified the following components for the CheckPoint Linux fwccorl01 device (System OID: .1.3.6.1.4.1.2620.1.1): FileSystem, Interface, Memory, and Processor.

9.4.2.15

303930 Alcatel Certified the following components for the Alcatel ISAM 7302 device (System OID: .1.3.6.1.4.1.6527): Card, Interface, Port, TempSensor, and PowerSupply.

9.4.2.15

303931 Alcatel Certified the following components for the Alcatel 7302 ISAM DSLAM device (System OID: .1.3.6.1.4.1.2076): Interface, Port, and VLAN.

9.4.2.15

Certified devices


40

Certification impact This section lists the impacted drivers and SysOIDs as a result of certification changes.

Table 14. Certification impact

SR /TASC Number

Impacted drivers Impacted SysOIDs Patch Release

303212 HEALTH = Cisco-ASA5k-EntSensor .1.3.6.1.4.1.9.12.3.1.3.1420 .1.3.6.1.4.1.9.1.2114

9.4.2.15

303711 CONT = F5-BIGIP-Select

CONT = F5-Viprion

Port-Fault = MIB2:PortKey

Port-Performance = MIB2:PortKey

.1.3.6.1.4.1.3375.2.1.3.4.11

.1.3.6.1.4.1.3375.2.1.3.4.10

.1.3.6.1.4.1.3375.2.1.3.4.4

.1.3.6.1.4.1.3375.2.1.3.4.6

.1.3.6.1.4.1.3375.2.1.3.4.5

.1.3.6.1.4.1.3375.2.1.3.4.8

.1.3.6.1.4.1.3375.2.1.3.4.12

.1.3.6.1.4.1.3375.2.1.3.4.21

.1.3.6.1.4.1.3375.2.1.3.4.20

.1.3.6.1.4.1.3375.2.1.3.4.1000

.1.3.6.1.4.1.3375.2.1.3.4.23

.1.3.6.1.4.1.3375.2.1.3.4.22

.1.3.6.1.4.1.3375.2.1.3.4.13

.1.3.6.1.4.1.3375.2.1.3.4.24

.1.3.6.1.4.1.3375.2.1.3.4.25

.1.3.6.1.4.1.3375.2.1.3.4.19

.1.3.6.1.4.1.3375.2.1.3.4.43

.1.3.6.1.4.1.3375.2.1.3.4.57

.1.3.6.1.4.1.3375.2.1.3.4.53

.1.3.6.1.4.1.3375.2.1.3.4.26

.1.3.6.1.4.1.3375.2.1.3.4.48

.1.3.6.1.4.1.3375.2.1.3.4.61

.1.3.6.1.4.1.3375.2.1.3.4.87

.1.3.6.1.4.1.3375.2.1.3.4.81

.1.3.6.1.4.1.3375.2.1.3.4.59

.1.3.6.1.4.1.3375.2.1.3.4.82

.1.3.6.1.4.1.3375.2.1.3.4.47

.1.3.6.1.4.1.3375.2.1.3.4.60

.1.3.6.1.4.1.3375.2.1.3.4.71

.1.3.6.1.4.1.3375.2.1.3.4.63

.1.3.6.1.4.1.3375.2.1.3.4.80

.1.3.6.1.4.1.3375.2.1.3.4.84

9.4.2.15

Certified devices


41

SR /TASC Number


.1.3.6.1.4.1.3375.2.1.3.4.94

.1.3.6.1.4.1.3375.2.1.3.4.72

.1.3.6.1.4.1.3375.2.1.3.4.70

.1.3.6.1.4.1.3375.2.1.3.4.97

.1.3.6.1.4.1.3375.2.1.3.4.89

.1.3.6.1.4.1.3375.2.1.3.4.83

.1.3.6.1.4.1.3375.2.1.3.4.95

.1.3.6.1.4.1.3375.2.1.3.4.99

303997 HOSTRESRCS = F5-MIB2

HostResrcs-F5-MIB2-Processor-Driver

.1.3.6.1.4.1.3375.2.1.3.4.11

.1.3.6.1.4.1.3375.2.1.3.4.10

.1.3.6.1.4.1.3375.2.1.3.4.4

.1.3.6.1.4.1.3375.2.1.3.4.6

.1.3.6.1.4.1.3375.2.1.3.4.5

.1.3.6.1.4.1.3375.2.1.3.4.8

.1.3.6.1.4.1.3375.2

.1.3.6.1.4.1.3375.2.1.3.4.12

.1.3.6.1.4.1.3375.2.1.3.4.21

.1.3.6.1.4.1.3375.2.1.3.4.20

.1.3.6.1.4.1.3375.2.1.3.4.1000

.1.3.6.1.4.1.3375.2.1.3.4.23

.1.3.6.1.4.1.3375.2.1.3.4.22

.1.3.6.1.4.1.3375.2.1.3.4.13

.1.3.6.1.4.1.3375.2.1.3.4.2

.1.3.6.1.4.1.3375.2.1.3.4.1

.1.3.6.1.4.1.3375.2.1.3.4.24

.1.3.6.1.4.1.3375.2.1.3.4.25

.1.3.6.1.4.1.3375.2.1.3.4.19

.1.3.6.1.4.1.3375.2.1.3.4.43

.1.3.6.1.4.1.3375.2.1.3.4.57

.1.3.6.1.4.1.3375.2.1.3.4.53

.1.3.6.1.4.1.3375.2.1.3.4.26

.1.3.6.1.4.1.3375.2.1.3.4.48

.1.3.6.1.4.1.3375.2.1.3.4.61

.1.3.6.1.4.1.3375.2.1.3.4.87

.1.3.6.1.4.1.3375.2.1.3.4.81

.1.3.6.1.4.1.3375.2.1.3.4.59

.1.3.6.1.4.1.3375.2.1.3.4.82

.1.3.6.1.4.1.3375.2.1.3.4.47

9.4.2.15

Certified devices


42

SR /TASC Number


.1.3.6.1.4.1.3375.2.1.3.4.60

.1.3.6.1.4.1.3375.2.1.3.4.71

.1.3.6.1.4.1.3375.2.1.3.4.63

.1.3.6.1.4.1.3375.2.1.3.4.80

.1.3.6.1.4.1.3375.2.1.3.4.84

.1.3.6.1.4.1.3375.2.1.3.4.94

.1.3.6.1.4.1.3375.2.1.3.4.72

.1.3.6.1.4.1.3375.2.1.3.4.70

.1.3.6.1.4.1.3375.2.1.3.4.97

.1.3.6.1.4.1.3375.2.1.3.4.89

.1.3.6.1.4.1.3375.2.1.3.4.83

.1.3.6.1.4.1.3375.2.1.3.4.95

.1.3.6.1.4.1.3375.2.1.3.4.99

303814 CONT = Mcafee-Generic-MIB2-selector

Containment-Mcafee-Generic-MIB2-selector-Driver

Containment-Mcafee-Entity-Driver

Containment-Create-Mcafee-Interface-Driver

.1.3.6.1.4.1.8072.3.2.10 9.4.2.15

303913 HOSTRESRCS = MIB2-Checkpoint-Other

CPU/Memory = Checkpoint:DeviceID

HostResrcs-MIB2-Checkpoint-Other-Driver

.1.3.6.1.4.1.2620.1.6.123.1.45

.1.3.6.1.4.1.2620.1.6.123.1.47

.1.3.6.1.4.1.2620.1.6.123.1.24

.1.3.6.1.4.1.2620.1.6.123.1.41

.1.3.6.1.4.1.2620.1.6.123.1.42

.1.3.6.1.4.1.2620.1.6.123.1.38

.1.3.6.1.4.1.2620.1.6.123.1.44

.1.3.6.1.4.1.2620.1.6.123.1.13

.1.3.6.1.4.1.2620.1.6.123.1.36

.1.3.6.1.4.1.2620.1.6.123.1.23

.1.3.6.1.4.1.2620.1.6.123.1.20

.1.3.6.1.4.1.2620.1.6.123.1.54

.1.3.6.1.4.1.2620.1.6.123.1.16

.1.3.6.1.4.1.2620.1.6.123.1.48

.1.3.6.1.4.1.2620.1.6.123.1.15

.1.3.6.1.4.1.2620.1.6.123.1.63

.1.3.6.1.4.1.2620.1.6.123.1.61

.1.3.6.1.4.1.2620.1.6.123.1.62

.1.3.6.1.4.1.2620.1.6.123.1.37

9.4.2.15

Certified devices


43

SR /TASC Number


.1.3.6.1.4.1.2620.1.6.123.1.64

.1.3.6.1.4.1.2620.1.6.123.1.49

.1.3.6.1.4.1.2620.1.6.123.1.55

.1.3.6.1.4.1.2620.1.1

303895 CONT = Cisco-UCS-C-Series

Containment-Cisco-UCS-C-Series-Driver

Containment-CiscoUCS-CSeries-Driver

.1.3.6.1.4.1.9.1.1682

.1.3.6.1.4.1.9.1.1683

.1.3.6.1.4.1.9.1.2179

9.4.2.15

303829 HOSTRESRCS = Isilon

HostResrcs-Isilon-Driver

HostResrcs-Isilon-MIB2-Processor-Driver

.1.3.6.1.4.1.12325.1.1.2.1.1

.1.3.6.1.4.1.12124.1

9.4.2.15

303810 HEALTH = HPProCurveJ4Series

Performance-HPProCurveJ4Series-Driver

.1.3.6.1.4.1.11.2.3.7.11.34

.1.3.6.1.4.1.11.2.3.7.11.23

.1.3.6.1.4.1.11.2.3.7.11.7

.1.3.6.1.4.1.11.2.3.7.11.8

.1.3.6.1.4.1.11.2.3.7.11.45

.1.3.6.1.4.1.11.2.3.7.11.29

.1.3.6.1.4.1.11.2.3.7.11.89

.1.3.6.1.4.1.11.2.3.7.11.60

.1.3.6.1.4.1.11.2.3.7.11.51

.1.3.6.1.4.1.11.2.3.7.11.50

.1.3.6.1.4.1.11.2.3.7.11.58

.1.3.6.1.4.1.11.2.3.7.11.14

.1.3.6.1.4.1.11.2.3.7.11.64

.1.3.6.1.4.1.11.2.3.7.8.1

.1.3.6.1.4.1.11.2.3.7.11.36

.1.3.6.1.4.1.11.2.3.7.11.35

.1.3.6.1.4.1.11.2.3.7.11.63

.1.3.6.1.4.1.11.2.3.7.11.76

.1.3.6.1.4.1.11.2.3.7.11.62

.1.3.6.1.4.1.11.2.3.7.11.32

.1.3.6.1.4.1.11.2.3.7.11.68

.1.3.6.1.4.1.11.2.3.7.11.80

.1.3.6.1.4.1.11.2.3.7.11.61

.1.3.6.1.4.1.11.2.3.7.11.90

.1.3.6.1.4.1.11.2.3.7.11.88

.1.3.6.1.4.1.11.2.3.7.11.107

.1.3.6.1.4.1.11.2.3.7.11.31

9.4.2.15

Certified devices


44

SR /TASC Number


.1.3.6.1.4.1.11.2.3.7.11.52

.1.3.6.1.4.1.11.2.3.7.11.105

.1.3.6.1.4.1.11.2.3.7.11.95

.1.3.6.1.4.1.11.2.3.7.11.129

.1.3.6.1.4.1.11.2.3.7.11.108

.1.3.6.1.4.1.11.2.3.7.11.153

.1.3.6.1.4.1.11.2.3.7.11.138

.1.3.6.1.4.1.11.2.3.7.11.132

.1.3.6.1.4.1.11.2.3.7.11.140

.1.3.6.1.4.1.11.2.3.7.11.10

.1.3.6.1.4.1.11.2.3.7.11.20

.1.3.6.1.4.1.11.2.3.7.11.42

.1.3.6.1.4.1.11.2.3.7.11.87

303800 HEALTH = HP-Aruba-Switch

Performance-HP-Aruba-Switch-Driver

.1.3.6.1.4.1.11.2.3.7.11.174.3 9.4.2.15

303754 HEALTH = Nexus-Entity-EntSensor

Performance-Nexus-Entity-EntSensor-Driver

Performance-Nexus-Entity-Driver

.1.3.6.1.4.1.9.12.3.1.3.612

.1.3.6.1.4.1.9.12.3.1.3.840

.1.3.6.1.4.1.9.12.3.1.3.719

.1.3.6.1.4.1.9.12.3.1.3.777

.1.3.6.1.4.1.9.12.3.1.3.798

.1.3.6.1.4.1.9.12.3.1.3.1008

.1.3.6.1.4.1.9.12.3.1.3.1038

.1.3.6.1.4.1.9.12.3.1.3.1084

.1.3.6.1.4.1.9.12.3.1.3.1106

.1.3.6.1.4.1.9.12.3.1.3.1107

.1.3.6.1.4.1.9.12.3.1.3.1105

.1.3.6.1.4.1.9.12.3.1.3.932

.1.3.6.1.4.1.9.12.3.1.3.1163

.1.3.6.1.4.1.9.12.3.1.3.1238

.1.3.6.1.4.1.9.12.3.1.3.1308

.1.3.6.1.4.1.9.12.3.1.3.1147

.1.3.6.1.4.1.9.12.3.1.3.1237

.1.3.6.1.4.1.9.12.3.1.3.1467

.1.3.6.1.4.1.9.12.3.1.3.1352

.1.3.6.1.4.1.9.12.3.1.3.1354

.1.3.6.1.4.1.9.12.3.1.3.1508

.1.3.6.1.4.1.9.12.3.1.3.1390

.1.3.6.1.4.1.9.12.3.1.3.1507

9.4.2.15

Certified devices


45

SR /TASC Number


.1.3.6.1.4.1.9.12.3.1.3.1410

.1.3.6.1.4.1.9.12.3.1.3.1388

.1.3.6.1.4.1.9.12.3.1.3.1627

.1.3.6.1.4.1.9.12.3.1.3.1625

.1.3.6.1.4.1.9.12.3.1.3.1409

.1.3.6.1.4.1.9.12.3.1.3.1489

.1.3.6.1.4.1.9.12.3.1.3.1626

.1.3.6.1.4.1.9.12.3.1.3.1619

.1.3.6.1.4.1.9.12.3.1.3.1491

.1.3.6.1.4.1.9.12.3.1.3.1824

.1.3.6.1.4.1.9.12.3.1.3.1712

.1.3.6.1.4.1.9.12.3.1.3.1660

.1.3.6.1.4.1.9.12.3.1.3.1239

.1.3.6.1.4.1.9.12.3.1.3.1666

.1.3.6.1.4.1.9.12.3.1.3.1570

.1.3.6.1.4.1.9.12.3.1.3.1539

.1.3.6.1.4.1.9.12.3.1.3.1175

.1.3.6.1.4.1.9.12.3.1.3.1812

.1.3.6.1.4.1.9.12.3.1.3.1697

.1.3.6.1.4.1.9.12.3.1.3.1743

.1.3.6.1.4.1.9.12.3.1.3.1758

.1.3.6.1.4.1.9.12.3.1.3.1759

.1.3.6.1.4.1.9.12.3.1.3.1839

.1.3.6.1.4.1.9.12.3.1.3.1726

.1.3.6.1.4.1.9.12.3.1.3.1843

.1.3.6.1.4.1.9.12.3.1.3.1389

.1.3.6.1.4.1.9.12.3.1.3.1744

.1.3.6.1.4.1.9.12.3.1.3.1454

.1.3.6.1.4.1.9.12.3.1.3.1675

303445 HEALTH = Checkpoint-Firewall

Performance-Checkpoint-Firewall-Driver

Performance-Checkpoint-Driver

.1.3.6.1.4.1.2620.1.6.123.1.45

.1.3.6.1.4.1.2620.1.6.123.1.47

.1.3.6.1.4.1.2620.1.6.123.1.24

.1.3.6.1.4.1.2620.1.6.123.1.41

.1.3.6.1.4.1.2620.1.6.123.1.42

.1.3.6.1.4.1.2620.1.6.123.1.38

.1.3.6.1.4.1.2620.1.6.123.1.44

.1.3.6.1.4.1.2620.1.6.123.1.13

.1.3.6.1.4.1.2620.1.6.123.1.36

9.4.2.15

Certified devices


46

SR /TASC Number


.1.3.6.1.4.1.2620.1.6.123.1.23

.1.3.6.1.4.1.2620.1.6.123.1.20

.1.3.6.1.4.1.2620.1.6.123.1.54

.1.3.6.1.4.1.2620.1.6.123.1.16

.1.3.6.1.4.1.2620.1.6.123.1.48

.1.3.6.1.4.1.2620.1.6.123.1.15

.1.3.6.1.4.1.2620.1.6.123.1.63

.1.3.6.1.4.1.2620.1.6.123.1.61

.1.3.6.1.4.1.2620.1.6.123.1.62

.1.3.6.1.4.1.2620.1.6.123.1.37

.1.3.6.1.4.1.2620.1.6.123.1.64

.1.3.6.1.4.1.2620.1.6.123.1.49

.1.3.6.1.4.1.2620.1.6.123.1.55

.1.3.6.1.4.1.2620.1.1

.1.3.6.1.4.1.2620.1.6.123.1.53

303742 CONT = Force10-Dell-Cont-Select

HEALTH = Force10-Dell-Health-Select

.1.3.6.1.4.1.6027.1.3.28

.1.3.6.1.4.1.6027.1.3.7

.1.3.6.1.4.1.6027.1.3.3

.1.3.6.1.4.1.6027.1.3.9

.1.3.6.1.4.1.6027.1.3.14

.1.3.6.1.4.1.6027.1.3.12

.1.3.6.1.4.1.6027.1.3.16

.1.3.6.1.4.1.6027.1.3.20

.1.3.6.1.4.1.6027.1.3.23

.1.3.6.1.4.1.6027.1.4.1

.1.3.6.1.4.1.6027.1.3.22

9.4.2.15



.1.3.6.1.4.1.6027.1.3.29 9.4.2.15



.1.3.6.1.4.1.6027.1.3.30 9.4.2.15



Environment = Dell_Networking_Force10:DeviceID

CPU/Memory = Dell_Networking_Force10:DeviceID

.1.3.6.1.4.1.6027.1.5.2 9.4.2.15

Certified devices


47

SR /TASC Number


Card-Fault = Dell_Networking_Force10:DeviceID

301683 CONT = AI-296 .1.3.6.1.4.1.539.2.15

.1.3.6.1.4.1.539.2.7

.1.3.6.1.4.1.539.2.18

9.4.2.15

303827 CONT = Alcatel-ISAM

HEALTH = Alcatel-ISAM

Card-Fault = ISAM:DeviceID

Environment = ISAM:DeviceID

.1.3.6.1.4.1.637.61.1 9.4.2.15





.1.3.6.1.4.1.6527 9.4.2.15





.1.3.6.1.4.1.2076 9.4.2.15

303902 HEALTH = Fortigate-Health

CPU/Memory = Fortigate:DeviceID

.1.3.6.1.4.1.12356.101.1.51010 9.4.2.15

303905 HEALTH = Fortigate-Health

CPU/Memory = Fortigate:DeviceID

.1.3.6.1.4.1.12356.101.1.50013 9.4.2.15

303391 CONT = Fujitsu-Flashwave

Card-Fault = Fujitsu_Flashwave_Slot:DeviceID

.1.3.6.1.4.1.18070.2.2 9.4.2.15

Third party software/library vulnerability


48

Third party software/library vulnerability This section lists the third party software/library vulnerabilities.

IS-9728/ SR 88763558

The zero day vulnerability has been found for Tomcat 7.0.0 and above, on all operating systems.

Root-cause analysis has been identified which suggests that Smarts is not affected with the zero day vulnerability. From the version of Tomcat shipped along with Smarts 9.4.2.0 (which is Tomcat 8.0.23) does retain the default configuration. Hence with that configuration, the Tomcat version deployed along with Smarts is no longer vulnerable.

However, if the user changes the configuration, the vulnerability occurs. The updated version of Tomcat is picked up by the next SP release of Smarts.

The vulnerability only affects the following configurations of Tomcat:

Default Servlet

• Default Servlet configured with readonly="false"

• Untrusted users are permitted to perform HTTP PUT requests

WebDAV Servlet

• WebDAV Servlet configured with readonly="false"

• Untrusted users are permitted to perform HTTP PUT requests

• The documented advice to not to map the WebDAV servlet as the Default servlet has been ignored

Note:

• The WebDAV servlet is disabled by default

• The default value for the readonly parameter is true for both the Default servlet and the WebDAV servlet

Therefore, a default Tomcat installation is not affected by this potential vulnerability.

The potential vulnerability may be mitigated by any of the following:

• Setting readonly to “true” for the Default servlet and WebDAV servlet

• Blocking HTTP methods that permit resource modification for untrusted users

Environment and system requirements


49

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 15. Supported operating systems and version number details

Product Supported operating systems Version number details

VOIP • Red Hat® Enterprise Linux® AS 5 and AS6,CentOS (64-bit operating system version only; for AMD64/EM64T chipsets)

• Microsoft Windows Server® 2008 Enterprise Edition SP1, SP2, and R2, (x64), Microsoft Windows Server 2012

• VMware® ESX Version 4.x,5 and vSphere 4 installed directly on physical server running the following operating systems for virtual machines:

o Windows Server 2008 Enterprise Edition, SP1, SP2, and R2, (x64), Microsoft Windows Server 2012

• Red Hat Enterprise Linux AS 5 and AS6, 64-bit

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

./sm_server --version (Linux)

The following output is displayed:

sm_server:

linux_rhAS50-x86-64/206320000

VOIP_SUITE: V9.4.2.15(163267), 17-Oct-2017 08:11:43 Copyright 1995-2017, EMC Corporation - Build 6

Foundation V9.4.2.1(162354), 09-Sep-2017 07:04:10 Copyright 1995-2017, EMC Corporation - Build 8

sm_server.exe --version (Windows)


sm_server.exe:

winnt-x86-64/206200

VOIP_SUITE: V9.4.2.15(163267), 17-Oct-2017 08:13:23 Copyright 1995-2017, EMC Corporation - Build 6


IP • Red Hat® Enterprise Linux® AS 5 and AS6,CentOS (64-bit operating system version only; for AMD64/EM64T chipsets)


• VMware® ESX Version 4.x,5 and vSphere 4 installed directly on physical server running the




sm_server:

linux_rhAS50-x86-64/301022900

IP_NETWORK_SUITE: V9.4.2.15(163461), 25-Oct-2017 10:12:16 Copyright 1995-2017, EMC Corporation - Build 52



50


following operating systems for virtual machines:






sm_server.exe:

winnt-x86-64/206110

IP_NETWORK_SUITE: V9.4.2.15(163463), 25-Oct-2017 11:51:15 Copyright 1995-2017, EMC Corporation - Build 52


SAM • Red Hat® Enterprise Linux® AS 5 and AS6,CentOS (64-bit operating system version only; for AMD64/EM64T chipsets)




Red Hat Enterprise Linux AS 5 and AS6, 64-bit




sm_server:

linux_rhAS50-x86-64/206320000

SAM_SUITE: V9.4.2.15(163274), 17-Oct-2017 15:00:44 Copyright 1995-2017, EMC Corporation - Build 14




sm_server.exe:

winnt-x86-64/206200

SAM_SUITE: V9.4.2.15(163274), 17-Oct-2017 15:00:44 Copyright 1995-2017, EMC Corporation - Build 14




51


Console sm_server: linux_rhAS50-x86-32/301032700 SAM_CONSOLE_SUITE: V9.4.2.15(163274), 17-Oct-2017 14:58:56 Copyright 1995-2017, EMC Corporation - Build 14 Foundation V9.4.2.1(162355), 09-Sep-2017 08:07:12 Copyright 1995-2017, EMC Corporation - Build 8 sm_server.exe: winnt-x86-32/206200 SAM_CONSOLE_SUITE: V9.4.2.15(163305), 18-Oct-2017 22:05:30 Copyright 1995-2017, EMC Corporation - Build 14 Foundation V9.4.2.1(162354), 09-Sep-2017 07:18:54 Copyright 1995-2017, EMC Corporation - Build 8

MPLS • Red Hat® Enterprise Linux® AS 5 and AS6,CentOS (64-bit operating system version only; for AMD64/EM64T chipsets)








sm_server:

linux_rhAS50-x86-64/206320000

MPLS_SUITE: V9.4.2.15(163313), 19-Oct-2017 06:03:04 Copyright 1995-2017, EMC Corporation - Build 5




sm_server.exe:

winnt-x86-64/206200

MPLS_SUITE: V9.4.2.15(163313), 19-Oct-2017 05:58:23 Copyright 1995-2017, EMC Corporation - Build 5


NPM • Red Hat® Enterprise Linux® AS 5 and AS6,CentOS (64-bit operating




52


system version only; for AMD64/EM64T chipsets)







sm_server:

linux_rhAS50-x86-64/206320000

NPM_SUITE: V9.4.2.15(163309), 19-Oct-2017 02:18:32 Copyright 1995-2017, EMC Corporation - Build 14




sm_server.exe:

winnt-x86-64/206200

NPM_SUITE: V9.4.2.15(163311), 19-Oct-2017 04:32:47 Copyright 1995-2017, EMC Corporation - Build 14


ESM • Red Hat® Enterprise Linux® AS 5 and AS6,CentOS (64-bit operating system version only; for AMD64/EM64T chipsets)








sm_server:

linux_rhAS50-x86-64/206320000

ESM_SUITE: V9.4.2.15(163147), 12-Oct-2017 07:49:53 Copyright 1995-2017, EMC Corporation - Build 19




sm_server.exe:

winnt-x86-64/206200


53


ESM_SUITE: V9.4.2.15(163147), 12-Oct-2017 07:51:35 Copyright 1995-2017, EMC Corporation - Build 19


OTM • Red Hat® Enterprise Linux® AS 5 and AS6,CentOS (64-bit operating system version only; for AMD64/EM64T chipsets)








sm_server:

linux_rhAS50-x86-64/206320000

OTM_SUITE: V9.4.2.15(163312), 19-Oct-2017 04:47:45 Copyright 1995-2017, EMC Corporation - Build 6




sm_server.exe:

winnt-x86-64/206200

OTM_SUITE: V9.4.2.15(163312), 19-Oct-2017 05:04:24 Copyright 1995-2017, EMC Corporation - Build 6


Installation


54

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 16. Replace “xx” with

the relevant product name, for example, IP, SAM, ESM, VOIP, MPLS, OTM, and NPM. For exact name, check the Patch Installation Files section.

Table 16. Setup command syntax for Wizard mode

Operating system

Wizard setup command syntax

Wizard setup command syntax for the SAM Console

Linux ./setup-XX-linux-9_4_2_15-20171026-64BIT.bin

Note: Where XX represents the product name.

./setup-CONSOLE-linux-9_4_2_15-20171020.bin

Windows setup-XX-win-9_4_2_15-20171026-64BIT.exe


setup-CONSOLE-win-9_4_2_15-20171020.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.

Installation


55

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.

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 user-modifiable 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

Installation


56

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.

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 17 and then press Enter. Replace “xx” with the relevant product name, for example, IP, SAM, ESM, VOIP, MPLS, OTM, and NPM. For exact name, check the Patch Installation Files section.

Table 17. Setup command syntax for CLI mode

Operating system

CLI setup command syntax Wizard setup command syntax for the Console

Linux ./setup-XX-linux-9_4_2_15-20171026-64BIT.bin -console

./setup-CONSOLE-linux-9_4_2_15-20171020.bin -console

Windows setup-XX-win-9_4_2_15-20171026-64BIT.exe -console

setup-CONSOLE-win-9_4_2_15-20171020.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)

Installation


57

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 18 and then press Enter.

Table 18. CLI mode navigation keys

Key Operation

1 Next, continue to the next step

2 Previous, go back to the previous step

3 Cancel, terminates the install program

5 Redisplay, repeats the step

0 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.

Installation


58

When the patch installation is complete, reconcile the configuration files as described in Reconcile user-modifiable files.

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 19 or Table 20 for SAM Console and then press Enter. Replace “xx” with the relevant product name, for example, IP, SAM, ESM, VOIP, MPLS, OTM and NPM. For exact name, check the Patch Installation Files section.

Table 19. Setup command syntax for unattended mode

Operating system

Unattended setup command syntax

Linux

./setup-XX-linux-9_4_2_15-20171026-64BIT.bin -silent

-G replaceNewerResponse="Yes to All"

-P rpProduct.installLocation=<BASEDIR>

-W mergeSummaryPanel.choiceMergeResult={auto|manual}


Windows

setup-SAM-win-9_4_2_15-20171020-64BIT.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.

• 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 20. Setup command syntax for unattended mode for SAM Console

Operating system


Linux ./ setup-CONSOLE-linux-9_4_2_15-20171020.bin -silent


Log files


59

Operating system




Windows

setup-CONSOLE-win-9_4_2_15-20171020.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.

• 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.


Log files Table 21 lists the files that the Installation software creates during the install process.

Table 21. Patch report and log file locations

Name Path File Name

Install log <BASEDIR>/smarts/setup/logs

C:\tmp (if install fails) Install.<patch version>.log

Merged files log BASEDIR/smarts/setup/logs install.merge.<patch version>.log

Where <patch version> is the complete version number for the patch, for example, 9.4.2.15

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

Reconcile user-modifiable files


60

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 user-modifiable 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.

Reconcile user-modifiable files


61

Note: In UNIX, the conflict and automerge versions of the user-modifiable files are hidden files.

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 22 lists the purpose and location of all user-modifiable files that the Installation software creates during the install process and their locations.

Table 22. 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.2.15

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.2.15/conf/discovery.conf

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.2.15

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.2.15.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:

Uninstallation


62

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.2.15.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.2.15.)

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 user-configurable 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.2.15.

Uninstallation Uninstalling a patch removes all previously applied patches and returns the EMC Smarts software to the baseline product version.

Uninstallation


63

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. Click Start > Settings > Control Panel.

2. Open the list of programs.

For Windows Server 2008, double-click Programs and Features.

For Windows Server 2012, double-click Programs and Features.

3. From the programs window, select <Product>.

4. Click Change/Remove.

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

C:\uninstaller.exe on Windows

Note: To run the uninstaller program in CLI mode, specify the console option after the uninstall command.

Uninstallation


64

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.

Troubleshooting and getting help


65

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


EMC Smarts Version 9.4.2 Patch 15 Readme ... - VMware Docs

Documents

Transcript of EMC Smarts Version 9.4.2 Patch 15 Readme ... - VMware Docs