EMC Ionix IP Management Suite - Dell EMC Japan These notes contain information about the EMC Ionix IP Management Suite Version 7.0 Service Pack 4, Patch 3 (IP 7.0.4.3). Topics include:

1

These notes contain information about the EMC Ionix IP Management Suite Version 7.0 Service Pack 4, Patch 3 (IP 7.0.4.3).

Topics include:

◆ Revision history ......................................................................................................... 2◆ Patch description ....................................................................................................... 2◆ Enhancements and changes ..................................................................................... 4◆ Known problems and limitations ........................................................................... 7◆ Number of fixed defects and certified devices...................................................... 7◆ Fixed defects............................................................................................................... 8◆ Certified devices ...................................................................................................... 10◆ Environment and system requirements ............................................................... 28◆ Installation ................................................................................................................ 29◆ Log files..................................................................................................................... 33◆ Reconcile user-modifiable files.............................................................................. 33◆ Uninstallation........................................................................................................... 36◆ Troubleshooting and getting help ......................................................................... 39

EMC® Ionix™

IP Management SuiteVersion 7.0.4 Patch 3

Read MeP/N 300-013-145

Rev A01

September 13, 2011

2 EMC Ionix IP Management Suite Version 7.0.4.3 Patch Read Me

Revision history

Revision historyThe following table presents the revision history of this document.

Patch descriptionA patch provides one or more fixes to an EMC Ionix 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.

Installation directory

In this document, the term BASEDIR represents the location where EMC Ionix software is installed.

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

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

The <productsuite> represents the EMC Ionix product suite to which the product belongs.

The EMC Ionix ITOps System Administration Guide provides additional information about the directory structure of EMC Ionix software.

Installation overview

A patch installs files to the BASEDIR/smarts/local directory of the product. The InstallShield 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, then the results can be copied to another computer.

Revision Date Description

A01 September, 2011 First release

3

Patch description

EMC Ionix IP Management Suite Version 7.0.4.3 Patch Read Me

JRE requirement for InstallShield softwareThe patch InstallShield software requires the Java Runtime Environment (JRE) version 1.5. If the InstallShield 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 Ionix software on one line. For example:

./setup-IP-solaris-7_0_4_3-20110912.bin -is:javahome /opt/InCharge/IP/_jvm

Install a new patch over an older patch

Patches are cumulative; each successive patch includes all of the fixes from any previous patches. As a result, a newer patch can be installed on top of an older patch. The patch number, which increments 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 InstallShield 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

When you upgrade an EMC Ionix product with a new major, minor, or Service Pack release, the upgraded version becomes the new baseline for the product. The upgrade incorporates all changes from any previous patches.

You must uninstall any patches before upgrading your EMC Ionix product with a new major, minor, or Service Pack release. “Uninstallation” on page 36 provides instructions for uninstalling a patch.

Patch files, which are installed at 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, 7.0.4.3

Patch installation files

Install the patch on each host where the IP Management Suite is running. Choose the appropriate InstallShield software based on the operating system of the host.

◆ setup-IP-hpux-7_0_4_3-20110912.bin

◆ setup-IP-linux-7_0_4_3-20110912.bin

◆ setup-IP-solaris-7_0_4_3-20110912.bin

◆ setup-IP-win-7_0_4_3-20110912.exe


Enhancements and changes

Enhancements and changesIP Management Suite 7.0.4 Patch 1 includes the following enhancements:

◆ “InstallShield software merges the current configuration into new patch configuration files” on page 4

◆ “New environment variable SM_USE_PING_PAYLOAD_ADDR added” on page 4

◆ “Certification for Cisco 2821 Integrated Services Router” on page 5

◆ “Behavior changes in IP Management Suite 7.0.4 Patch 1 for creation of Temperature Sensors for Cisco Nexus devices” on page 6

◆ “False and unwanted alarms were being notified” on page 5

◆ “Log enhancements” on page 6

InstallShield software merges the current configuration into new patch configuration filesThe patch InstallShield software was enhanced to automate the process of moving changes from user-modifiable configuration files to new versions of the configuration files that are part of the patch.

In earlier versions, the InstallShield software compared files in the patch with configuration files from the local directories. Files in the local directories contain changes from the base release, introduced either by user modifications or by earlier patches. The patch installed the new files while maintaining a copy of the earlier versions. These actions were listed in a reconciliation report. Using the report, you had to review each set of files, the new patch file and the previously changed file, and then manually merge desired changes into the active configuration file.

The enhanced InstallShield software reduces and simplifies the effort required to merge existing configuration changes into new files included in the patch. Most changes from user-modifiable configuration files can be automatically merged into the new files.

If the InstallShield software cannot merge the files due to conflicting changes, it creates a merged file that clearly identifies the conflicting user modification, the patch change, and the original code. While merging the files, the program saves copies of the both the user-modified file and the patch file before any changes.

New environment variable SM_USE_PING_PAYLOAD_ADDR addedCQ 532168/CQ 502950 (Patch 1)

Earlier releases of the IP Management Suite did not handle ICMP responses coming from an IP address other than the address to which the ICMP ping was originally sent. For example, assume that a device has two IP addresses, IP1 and IP2. An ICMP ping is sent to IP1, but the corresponding response is received from IP2. In such cases the device will get added to the pending list in case it is discovered with access mode as ICMP/ICMPSNMP.

5



In this release, a new environment variable SM_USE_PING_PAYLOAD_ADDR is introduced to allow ICMP to recognize replies coming from an IP address other than the IP address to which the ping request was originally sent.

To enable this functionality:

1. Add the environment variable SM_USE_PING_PAYLOAD_ADDR in the <BASEDIR>/smarts/local/runcmd_env.sh file

2. Set this environment variable to 1. By default, it is disabled.

3. Restart the domain manager to load the variable.

The implementation of ICMP protocol now places a copy of the destination address in the payload of ping requests. If this option is enabled, ICMP uses this address in the reflected payload, rather than the source IP address of the reply. The device, therefore, will be added to the topology instead of being put on the pending list.

Certification for Cisco 2821 Integrated Services Router

CQ 572578/CQ 570755/SR35237512

The existing certification for Cisco 2821 Integrated Services Router with systemObjectID .1.3.6.1.4.1.9.1.577 (IOS 15.1.1(T)) was found to be appropriate except for the following issue:

The existing certification uses the OldCiscoChassis MIB for card creation and monitoring. However, since this MIB is deprecated, Entity-MIB and cefcModuleOperStatus should be used. But cefcModuleOperStatus does not provide the status for all cards found on the device, where as OldCiscoChassis MIB does. Also, the data reflected by using the OldCiscoChassis MIB matched with the cards on the device as opposed to cefcModuleOperStatus.

Thus the existing certification for this device continues to use the OldCiscoChassis MIB.

False and unwanted alarms were being notifiedCQ 573299/CQ 494444/SR 34974038/SR 35440820

False and unwanted alarms were being notified and cleared due to insufficient correlation time.

Performance improvements have been made in the model in order to reduce the correlation time.

This issue has been addressed in the IP Management Suite Version 7.0 Service Pack 4.



Behavior changes in IP Management Suite 7.0.4 Patch 1 for creation of Temperature Sensors for Cisco Nexus devices

CQ 536815/CQ 571506

In IP Management Suite 7.0.4 and earlier releases, Temperature Sensors that were not present on the device were created. In IP Management Suite 7.0.4 Patch 1, Temperature Sensors that are not present on the device are now not created. This change in behavior is applicable only to the following Nexus devices:

◆ Nexus-7018 with systemObjectID .1.3.6.1.4.1.9.12.3.1.3.777




entSensorStatus with OID 1.3.6.1.4.1.9.9.91.1.1.1.1.5 can have 3 values:

◆ Ok (1)

◆ Unavailable (2)

◆ Non-operational (3)

The value Unavailable (2) indicates that Temperature Sensors are not present on the device.

Log enhancementsIn this patch release, enhancements are made to the log to include diagnostic information.

Example [04-Jan-2011 17:34:36 EST]The following lines are routine diagnostic output; this is not a crash.===============================================================Start of process debug and runtime information:===============================================================Solaris 20800:IP_NETWORK_SUITE: V7.0.4.1(103357), 17-Dec-2010 01:04:34 Copyright 1995-2010, EMC Corporation - Build 13sm_server -n xxxx-7041-ip -c icf --output --bootstrap=bootstrap-am-pm.conf --daemon --subscribe=default --ignore-restore-errorsFoundation: V7.0.2.1(103346), 16-Dec-2010 14:19:32 Copyright 1995-2010, EMC Corporation - Build 135libsm_clsapi.so (101877) 16-Oct-2010 09:54:19

libsm_servif.so (98871) 13-Jun-2010 03:58:58

sm_server (101375) 25-Sep-2010 11:48:26

7

Known problems and limitations


Known problems and limitationsThe following problems and limitations are known for IP Management Suite 7.0.4.3:

Devices are not deleted from the Map Console

CQ 573336

IssueWhen a device is deleted from the domain manager, the device does not get deleted from the map console.

ResolutionRediscovering any single device from the domain manager refreshes the map console.

Warning messages are seen in the install and uninstall log filesCQ 479612

IssueThe following warning message is seen in the installation and uninstallation log files:

*(Dec 15, 2009 10:36:18 AM), Install, com.installshield.wizard.Wizard, wrn, could not open resource for manifest_en.md5*.

ResolutionThere is currently no resolution.

Number of fixed defects and certified devicesThis section lists the number of defects fixed and devices certified for every patch.

Table 1 Number of defects fixed and certified devices

Original Patch Release Fixed defects Certified devices

3 1 0

2 0 167

1 3 25


Fixed defects

Fixed defectsThis section describes the fixed problems addressed by the patches.

Table 2 Fixed defects for IP Management Suite 7.0.4.3 (1 of 2)

CQ or SRTicket Number Symptom Description of Fix

Modified Files (all files inBASEDIR/smarts/local/)

Original Patch Release

CQ 574325CQ 503456CQ 503547

EMC Ionix IP Management Suite version 7.0.4.3 buffer overflow vulnerability (CVE-2011-2738). Please see ESA-2011-029 for more details. The EMC Security Advisory (ESA) is available on Powerlink.

3

CQ 495297SR37503840

Devices are not removed from the pending list even after a pending list discovery.

The presence of the parameter REFRESH_SHORT in the function call addPending makes the device persist in the pending list. The problem is fixed by removing this parameter.

File modified:rules/discovery/devstat/oi/ic-oi-trap.asl

1

CQ 502855SR37417660

Cisco Discovery Protocol (CDP) post processing takes more time if the Remote Peer IP address found in the CDP address table is a duplicate IP address.Earlier, in a duplicate IP scenario, if the Remote Peer IP address found in the CDP table is a duplicate IP address, the existing code logic used the Remote Device ID to find the neighboring device using the findComputerSystem call. If the Remote Device ID was not available in the topology, the corresponding IP address was obtained from the DNS entry. If the DNS entry was corrupted, then the findComputerSystem call took more time than expected.

To avoid the delay in post processing, a fix is now provided where the Remote Device ID is matched with the system names of the Duplicate IP Parent Systems. The matched system is considered as the peer device and the connections are established.As a result of this fix, the extra CDP connections are created specifically while encountering such types of Duplicate IP instances.

File modified:rules/discovery/ic-cisco-post-processor.asl

1

9

Fixed defects


CQ 527913SR35708022

When an IP object is in the DOWN state, the IP Manager will poll only once to check the responsiveness of the address.In cases where an IP is reachable using a communication medium that is not always active, the first communication request may timeout while the connection protocol is being established. If a successive communication request is not attempted, the communication medium becomes inactive again resulting in no response from the object and leaving the object in perpetual DOWN state.

Note: This tends to happen on specific media types. The type reported was a wireless dial-on-demand interface with an idle threshold less than the polling interval. Because they are charged based on time of activation as well as data transmitted, the idle thresholds are quite short. Essentially, it will look like the following:- time 0: ping request sent- time 0 + ~240ms : ping request timed out- time n (typically 3-5 seconds): connection is established(since all IPs are unresponsive, no SNMP packets are sent)- time n+idle threshold: connection is terminated- time x: ping request sent.In this state, the polling of the IP will not recover.

A feature is added to use the default retries when an IP object is DOWN.Set the flag PingControl to ENABLED in the Connectivity properties. This will activate the settings and allow you to adjust the new parameter UseICMPRetriesWhenDown. Setting the parameter UseICMPRetriesWhenDown to TRUE will retry ICMP communication request when an IP object is DOWN based on the value of the attribute PingRetries.

Note: This is manipulated through the Polling and Thresholds Console and is a part of the Connectivity Polling settings. Further, it is configured on a per-class basis.

File modified:rules/discovery/devstat/settings/sys-setting.asl

1

Table 2 Fixed defects for IP Management Suite 7.0.4.3 (2 of 2)





Certified devices

Certified devicesThe following certifications which were marked as TEMPLATE in the IP 7.0.4.1 release are now marked as CERTIFIED in IP 7.0.4.2:

◆ Cisco Nexus 7018 switch, with systemObjectID .1.3.6.1.4.1.9.12.3.1.3.777

◆ Avaya G450 Media Gateway host, with systemObjectID .1.3.6.1.4.1.6889.1.45.103.8

◆ Zyxel VES1616FE switch, with systemObjectID .1.3.6.1.4.1.890.1.5.12.37

◆ Ciena CN4200RS switch, with systemObjectID .1.3.6.1.4.1.7737.5.2.2.8

◆ Juniper EX2500 switch, with systemObjectID .1.3.6.1.4.1.1411.102

◆ Alcatel OmniSwitch 6600 switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.12

◆ Alcatel OmniSwitch 6850-48X switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.4

◆ Alcatel OmniSwitch 6850-P48L switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.6

◆ Alcatel OmniSwitch 6200 switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.2.4.1.7

◆ Alcatel Omniswitch 6850-48 switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.2

◆ Alcatel OmniSwitch 6850-48X switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.4

This section describes the devices certified by the patch.

Table 3 Certified devices for IP Management Suite 7.0.4.3 (1 of 18)




CQ 573174SR37252732

IBM IBM3584 host, with systemObjectID .1.3.6.1.4.1.2.6.182.1.0.408.1, was required to be certified.

The device is certified. File modified:conf/local/oid2type_Misc.conf

2

CQ 572888 HP MSA2212fc host, with systemObjectID .1.3.6.1.4.1.11.2.51, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Hp.conf

2

CQ 571686SR35697302

Foundry WXR10201 loadbalancer, with systemObjectID .1.3.6.1.4.1.1991.1.3.47.9.2, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Foundry.conf

2

CQ 573045 Huawei S2309TP switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.88, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Huawei.conf

2

11

Certified devices


CQ 571745SR34551860

Foundry FESX448 PREM switch, with systemObjectID .1.3.6.1.4.1.1991.1.3.34.2.1.2.2, was required to be certified.


2

CQ 571750SR34547514

Cisco NMEX24ES1 switch, with systemObjectID .1.3.6.1.4.1.9.1.703, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Cisco.conf

2

CQ 571775SR33337708

VisualNetworks M411 CSU probe, with systemObjectID .1.3.6.1.4.1.1246.1.212, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Misc.conf

2

CQ 572842SR32998222

Foundry NetIron CES router, with systemObjectID .1.3.6.1.4.1.1991.1.3.49.3, was required to be certified.


2

CQ 573163SR36608196

Lineage CPL host, with systemObjectID .1.3.6.1.4.1.10520.2.1.1, was required to be certified.


2

CQ 571792 Nortel CS1K 60 host, with systemObjectID .1.3.6.1.4.1.562.3.14, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Nortel.conf

2

CQ 571795SR33122966

Alcatel OmniSwitch 6400 switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.10.1.1, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Alcatel.conf

2

CQ 573252 Cisco 7204 router, with systemObjectID .1.3.6.1.4.1.9.1.125, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type.conf

2

CQ 573481SR34273068

Cisco MeetingPlace bridge, with systemObjectID .1.3.6.1.4.1.7185, was required to be certified.


2

CQ 571794SR33076684

HP J8165A ProCurve switch 2650-PWR, with systemObjectID .1.3.6.1.4.1.11.2.3.7.11.35, was required to be certified.


2

CQ 571755SR34296716

VisualNetworks Visual M411 CSU probe, with systemObjectID .1.3.6.1.4.1.1246.1.411, was required to be certified.


2






Certified devices

CQ 571780 BlueCoat SG9000 host, with systemObjectID .1.3.6.1.4.1.3417.1.1.29, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Bluecoat.conf

2

CQ 573017SR35913392

Cisco 3750-24TS switch, with systemObjectID .1.3.6.1.4.1.9.1.1023, was required to be certified.


2

CQ 572892SR34832046

HP ProCurve j9020a switch 2510-48, with systemObjectID .1.3.6.1.4.1.11.2.3.7.11.62, was required to be certified.


2

CQ 573202SR33482976

Brocade FCX648 switch, with systemObjectID .1.3.6.1.4.1.1991.1.3.54.2.1.1.1, was required to be certified.


2

CQ 572841SR32998104

Foundry NetIron-CES router, with systemObjectID .1.3.6.1.4.1.1991.1.3.49.4, was required to be certified.


2

CQ 572843SR32893834

Foundry FastIron SX1600 switch, with systemObjectID .1.3.6.1.4.1.1991.1.3.36.6.1, was required to be certified.


2

CQ 572890SR34846484

HP ProCurve J9021A switch 2810-24G, with systemObjectID .1.3.6.1.4.1.11.2.3.7.11.63, was required to be certified.


2

CQ 573253 Cisco 4948GL3 switch, with systemObjectID .1.3.6.1.4.1.9.1.626, was required to be certified.


2

CQ 573204SR36973502

Brocade fibre channel switch, with systemObjectID .1.3.6.1.4.1.1588.2.1.1.42, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Brocade.conf

2

CQ 571746SR34336152

Foundry FastIron Edge 400 switch, with systemObjectID .1.3.6.1.4.1.1991.1.3.22.2, was required to be certified.


2

CQ 571702 Cisco C2960SM-LANBASEK9-M router, with systemObjectID .1.3.6.1.4.1.9.1.1051, was required to be certified.


2





13

Certified devices


CQ 571772SR33423516

Huawei QuidWay S5648P switch, with systemObjectID .1.3.6.1.4.1.2011.10.1.45, was required to be certified.


2

CQ 572846SR36364060

Foundry FastIron FESX624PREM switch, with systemObjectID .1.3.6.1.4.1.1991.1.3.34.6.1.2.3, was required to be certified.


2

CQ 573486SR36957914

Cisco ACE module loadbalancer, with systemObjectID .1.3.6.1.4.1.9.1.1291, was required to be certified.


2

CQ 573019SR35913174



2

CQ 573158SR31746312

NEC NEAX 2400 IPX host, with systemObjectID .1.3.6.1.4.1.119.1.76.2, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Nec.conf

2

CQ 573454SR33059304

Cisco WS-SVC-SSL router, with systemObjectID .1.3.6.1.4.1.9.1.610, was required to be certified.


2

CQ 572964 APC AP9617 host, with systemObjectID .1.3.6.1.4.1.318.1.3.4.4, was required to be certified.


2

CQ 573063 Huawei S5324TP SI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.98, was required to be certified.


2

CQ 572946SR33692070

Juniper SA-6000 firewall, with systemObjectID .1.3.6.1.4.1.12532.252.6.1, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Juniper.conf

2

CQ 572473SR37387000

Cisco CDE-205 host, with systemObjectID .1.3.6.1.4.1.9.1.1167, was required to be certified.


2

CQ 571778SR33344356

VisualNetworks M134 probe, with systemObjectID .1.3.6.1.4.1.1246.1.1.134, was required to be certified.


2






Certified devices

CQ 573018SR35913302



2

CQ 572943SR34545468

Allied Telesyn AT 8288XL SC switch, with systemObjectID .1.3.6.1.4.1.207.1.4.43, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Alliedtel.conf

2

CQ 572845SR36364120

Foundry FastIron FCX624S POE PREM switch, with systemObjectID .1.3.6.1.4.1.1991.1.3.54.1.2.1.4, was required to be certified.


2

CQ 571707 Cisco C2960SM router, with systemObjectID .1.3.6.1.4.1.9.1.1052, was required to be certified.


2

CQ 571779SR33344426

VisualNetworks M205 probe, with systemObjectID .1.3.6.1.4.1.1246.1.1.205, was required to be certified.


2

CQ 573147SR35198004

Cyclades AlterPath host, with systemObjectID .1.3.6.1.4.1.2925.5, was required to be certified.


2

CQ 573156SR32965770

Dragonwire HC30 router, with systemObjectID .1.3.6.1.4.1.7262.2.2, was required to be certified.


2

CQ 573159SR36726356

Cybertec 2000 router, with systemObjectID .1.3.6.1.4.1.15428.1.5, was required to be certified.


2

CQ 573025SR35742878

Cisco C3560IPBASE switch, with systemObjectID .1.3.6.1.4.1.9.1.1024, was required to be certified.


2

CQ 572886SR35426086

HP PC Blade switch, with systemObjectID .1.3.6.1.4.1.11.2.3.7.14.14.1.1.3, was required to be certified.


2

CQ 573012SR35913468

Cisco 3750-48PS switch, with systemObjectID .1.3.6.1.4.1.9.1.1027, was required to be certified.


2





15

Certified devices


CQ 573382 Cisco FSP150CCGE201SE host, with systemObjectID .1.3.6.1.4.1.2544.1.12.1.1.5, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Adva.conf

2

CQ 572882SR35965406

Sonus Management Agent host, with systemObjectID .1.3.6.1.4.1.2879.1.5.3, was required to be certified.

The device is certified. File modified:conf/discovery/import/oid2type_Misc.conf

2

CQ 573171SR33084380

Quintum Tenor DX host, with systemObjectID .1.3.6.1.4.1.6618.1.1.10, was required to be certified.


2

CQ 573144SR31427100

IBM UltraScaleable 7420 host, with systemObjectID .1.3.6.1.4.1.2.6.182.1, was required to be certified.


2

CQ 573161SR33060158

EMC CX4-110 host, with systemObjectID .1.3.6.1.4.1.1981.1.1, was required to be certified.


2

CQ 571781SR33350456

3COM 8807 switch, with systemObjectID .1.3.6.1.4.1.43.1.16.4.3.4, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_3Com.conf

2

CQ 571756SR34172598

Cisco TelePresence 162 host, with systemObjectID .1.3.6.1.4.1.9.1.800, was required to be certified.


2

CQ 570757SR35068428

Nokia IPSO firewall, with systemObjectID .1.3.6.1.4.1.94.1.21.2.1.139, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Nokia.conf

2

CQ 572910SR34028790

Tavve ZoneRanger host, with systemObjectID .1.3.6.1.4.1.2668.1.1.16, was required to be certified.


2

CQ 572439 Huawei S3352PEI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.79, was required to be certified.


2

CQ 571754SR34399782

Cisco Catalyst C3560E switch, with systemObjectID .1.3.6.1.4.1.9.1.1020, was required to be certified.


2

CQ 571734SR34820990

Nokia IPFirewallGA039 firewall, with systemObjectID .1.3.6.1.4.1.94.1.21.2.1.148, was required to be certified.


2






Certified devices

CQ 573054 Huawei S3352P EI 48S bridge, with systemObjectID .1.3.6.1.4.1.2011.2.23.85, was required to be certified.


2

CQ 573150SR35700870

Microsemi PowerDsine 9024G switch, with systemObjectID .1.3.6.1.4.1.7428.1.1.1.22, was required to be certified.


2

CQ 573177SR37883370

Cisco C3560E router, with systemObjectID .1.3.6.1.4.1.9.1.1049, was required to be certified.


2

CQ 573151SR35402728

Ellacoya e100 switch, with systemObjectID .1.3.6.1.4.1.3813.2.9, was required to be certified.


2

CQ 571793SR33076730

HP J8164A ProCurve switch 2626-PWR, with systemObjectID .1.3.6.1.4.1.11.2.3.7.11.36, was required to be certified.


2

CQ 571747SR34336152

Foundry FastIron Edge S2402 switch, with systemObjectID .1.3.6.1.4.1.1991.1.3.25.2, was required to be certified.


2

CQ 572847SR36364170

Foundry FastIron SuperX switch, with systemObjectID .1.3.6.1.4.1.1991.1.3.36.8.2, was required to be certified.


2

CQ 571807SR32077058

Cisco ISM router, with systemObjectID .1.3.6.1.4.1.9.1.1149, was required to be certified.


2

CQ 565854SR35744726

Cisco C3560v2 switch, with systemObjectID .1.3.6.1.4.1.9.1.1019,


2

CQ 570783SR33417872

Huawei CX600 8 switch, with systemObjectID .1.3.6.1.4.1.2011.2.87.7,


2

CQ 570785SR33666206

Huawei Quidway S9312 switch, with systemObjectID .1.3.6.1.4.1.2011.2.170.3, was required to be certified.


2

CQ 570798SR33423238

Huawei 3Com Quidway S5624P switch, with systemObjectID .1.3.6.1.4.1.2011.10.1.43, was required to be certified.


2





17

Certified devices


CQ 571680SR36467442

Juniper EX2200 switch, with systemObjectID .1.3.6.1.4.1.2636.1.1.1.2.43, was required to be certified.


2

CQ 571688SR35795184

Cisco C3270 router, with systemObjectID .1.3.6.1.4.1.9.1.689, was required to be certified.


2

CQ 571690SR35430474

Cisco VG202 router, with systemObjectID .1.3.6.1.4.1.9.1.964, was required to be certified.


2

CQ 571692SR34937758

Cisco 881 Integrated Services router, with systemObjectID .1.3.6.1.4.1.9.1.837, was required to be certified.


2

CQ 571693SR34937758

Cisco 887 Integrated Services router, with systemObjectID .1.3.6.1.4.1.9.1.847, was required to be certified.


2

CQ 571695SR35251974

F5 Big IP 6900 bridge, with systemObjectID .1.3.6.1.4.1.3375.2.1.3.4.22, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_F5.conf

2

CQ 571697SR35305564

Huawei Quidway S3328TP EI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.81, was required to be certified.


2

CQ 571704 Cisco C2960SM router, with systemObjectID .1.3.6.1.4.1.9.1.1055, was required to be certified.


2

CQ 571706SR34927338

Adtran NetVanta 3120 router, with systemObjectID .1.3.6.1.4.1.664.1.880, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Adtran.conf

2

CQ 571732SR35126624

Brocade ds5000b switch, with systemObjectID .1.3.6.1.4.1.1588.2.1.1.58, was required to be certified.


2

CQ 571749SR34520840

Cisco Catalyst 2960 switch, with systemObjectID .1.3.6.1.4.1.9.1.1016, was required to be certified.


2

CQ 571761SR33908518

Cisco Universal router, with systemObjectID .1.3.6.1.4.1.9.1.1050, was required to be certified.


2






Certified devices

CQ 571770SR33555686

Acme Packet Net-Net 3800 switch, with systemObjectID .1.3.6.1.4.1.9148.1.3.1, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_AcmePacket .conf

2

CQ 571789SR33155384

Cisco C3560 router, with systemObjectID .1.3.6.1.4.1.9.1.1015, was required to be certified.


2

CQ 571790SR33060084

Cisco WS-C2975GS-48PS-L switch, with systemObjectID .1.3.6.1.4.1.9.1.1068, was required to be certified.


2

CQ 571805SR32645004

Juniper SA2000 host, with systemObjectID .1.3.6.1.4.1.12532.252.2.1, was required to be certified.


2



2



2



2

CQ 572438 Huawei S3328TPEI24S switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.82, was required to be certified.


2

CQ 572440 Huawei S5328CEI24S switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.96, was required to be certified.


2

CQ 572441 Huawei AR1831E router, with systemObjectID .1.3.6.1.4.1.2011.10.1.74, was required to be certified.


2

CQ 572443 Huawei AR19 router, with systemObjectID .1.3.6.1.4.1.2011.10.1.225, was required to be certified.


2

CQ 572445 Huawei AR19 bridge, with systemObjectID .1.3.6.1.4.1.2011.10.1.138, was required to be certified.


2





19

Certified devices




2

CQ 572588SR37794134

Cisco 2960-8TC-S switch, with systemObjectID .1.3.6.1.4.1.9.1.1006, was required to be certified.


2

CQ 572881SR36022976

Nortel 4548GT switch, with systemObjectID .1.3.6.1.4.1.45.3.71.1, was required to be certified.


2

CQ 572885 HP Proliant BL host, with systemObjectID .1.3.6.1.4.1.232.22.3.1, was required to be certified.


2

CQ 572891SR34846528

HP ProCurve J9085A switch 2610-24, with systemObjectID .1.3.6.1.4.1.11.2.3.7.11.76, was required to be certified.


2

CQ 572894SR34797484

HP ProCurve J4904A switch 2848, with systemObjectID .1.3.6.1.4.1.11.2.3.7.11.32, was required to be certified.


2

CQ 572895SR33994786

HP ProCurve J9050A switch, with systemObjectID .1.3.6.1.4.1.11.2.3.7.11.68, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Hp. conf

2

CQ 572904SR32961582

Nortel 8610 switch, with systemObjectID .1.3.6.1.4.1.2272.32, was required to be certified.


2

CQ 572911SR33975992

RiverStone 3200 switch, with systemObjectID .1.3.6.1.4.1.5567.1.1.12, was required to be certified.


2

CQ 572914SR32626752

Symmetricom TimeServer host, with systemObjectID .1.3.6.1.4.1.1896.0, was required to be certified.


2

CQ 572915 HP Modular Cooling System host, with systemObjectID .1.3.6.1.4.1.232.167, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Hp. conf

2

CQ 572917SR37142110

Nortel BNT 10GB switch, with systemObjectID .1.3.6.1.4.1.26543.1.18.11, was required to be certified.


2






Certified devices

CQ 572918SR37034916

Nortel 10GB Switch Module switch, with systemObjectID .1.3.6.1.4.1.26543.1.18.5, was required to be certified.


2

CQ 572919 Avaya G860 Media Gateway host, with systemObjectID .1.3.6.1.4.1.5003.8.2.1.2, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Avaya.conf

2

CQ 572921SR37621684

Nortel Ethernet Routing switch, with systemObjectID .1.3.6.1.4.1.45.3.71.6, was required to be certified.


2

CQ 572933SR35726404

3Com 4500G 24 Port switch, with systemObjectID .1.3.6.1.4.1.43.1.16.4.3.30, was required to be certified.


2

CQ 572934SR35328728

3Com 4500 switch, with systemObjectID .1.3.6.1.4.1.43.1.16.4.3.21, was required to be certified.


2

CQ 572935SR33407062CQ 573384SR37173412



2

CQ 572938SR36795744

3com 2952-SFP switch, with systemObjectID .1.3.6.1.4.1.43.1.8.73, was required to be certified.


2

CQ 572939SR37291668



2

CQ 572940SR37291336

3Com 4500 50-Port switch, with systemObjectID .1.3.6.1.4.1.43.1.16.4.3.22, was required to be certified.


2

CQ 572947SR33570942

F5 Networks BIG-IP 8800 loadbalancer, with systemObjectID .1.3.6.1.4.1.3375.2.1.3.4.13, was required to be certified.


2

CQ 572948SR33552908

F5 Networks BIG-IP loadbalancer, with systemObjectID .1.3.6.1.4.1.3375.2.1.3.4.2, was required to be certified.


2





21

Certified devices


CQ 572949SR33552908



2

CQ 572959SR36409650

VMWare ESX 4.0.0 host, with systemObjectID .1.3.6.1.4.1.6876.4.1, was required to be certified.


2

CQ 572970SR33277314

Voltaire SMAgent host, with systemObjectID .1.3.6.1.4.1.5206.1.18, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Voltaire.conf

2

CQ 572973SR37036958



2

CQ 573024SR35806730

Cisco WS-C3560X-24 switch, with systemObjectID .1.3.6.1.4.1.9.1.1226, was required to be certified.


2

CQ 573026SR35841214

Cisco Catalyst C1900 switch, with systemObjectID .1.3.6.1.4.1.9.1.1191, was required to be certified.


2

CQ 573039SR35754158

Cisco Catalyst C3560E switch, with systemObjectID .1.3.6.1.4.1.9.1.1057, was required to be certified.


2



2

CQ 573046 Huawei S2309TP PWR EI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.108, was required to be certified.


2



2



2






Certified devices

CQ 573049 Huawei S3328TP EI MC switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.112, was required to be certified.


2



2

CQ 573051 Huawei S3328TP PWR EI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.110, was required to be certified.


2

CQ 573052 Huawei S3352P SI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.78, was required to be certified.


2

CQ 573053 Huawei S3352P EI 24S bridge, with systemObjectID .1.3.6.1.4.1.2011.2.23.84, was required to be certified.


2

CQ 573055 Huawei S2352P EI bridge, with systemObjectID .1.3.6.1.4.1.2011.2.23.94, was required to be certified.


2



2

CQ 573059 Huawei S5352C PWR SI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.105, was required to be certified.


2

CQ 573060 Huawei S5352C SI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.103, was required to be certified.


2

CQ 573061 Huawei S5328C PWR SI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.104, was required to be certified.


2

CQ 573062 Huawei S5328C SI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.102, was required to be certified.


2

CQ 573065 Huawei S5352C PWR EI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.107, was required to be certified.


2





23

Certified devices


CQ 573066 Huawei S5328C PWR EI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.106, was required to be certified.


2

CQ 573067 Huawei S5348TP PWR SI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.101, was required to be certified.


2



2

CQ 573069 Huawei S5328C EI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.95, was required to be certified.


2

CQ 573070 Huawei S3352P PWR EI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.111, was required to be certified.


2

CQ 573071 Huawei S5324TP PWR SI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.100, was required to be certified.


2

CQ 573092SR33617276

Cisco C2960 switch, with systemObjectID .1.3.6.1.4.1.9.1.1005, was required to be certified.


2

CQ 573096 Cisco 2960S switch, with systemObjectID .1.3.6.1.4.1.9.1.1208, was required to be certified.


2

CQ 573103SR35743428

Cisco WS-C3560-24PS-S switch, with systemObjectID .1.3.6.1.4.1.9.1.1021, was required to be certified.


2

CQ 573107 Cisco C2960SM LANBASEK9-M router, with systemObjectID .1.3.6.1.4.1.9.1.1048, was required to be certified.


2

CQ 573111SR34027648

Cisco 3560E switch, with systemObjectID .1.3.6.1.4.1.9.1.1054, was required to be certified.


2






Certified devices

CQ 573112SR33906288

Cisco 7606 router, with systemObjectID .1.3.6.1.4.1.9.1.863, was required to be certified.


2

CQ 573132SR35331016

Infoblox IB-Infoblox host, with systemObjectID .1.3.6.1.4.1.7779.2.2, was required to be certified.


2

CQ 573142SR32883844

IBM BladeCenter switch, with systemObjectID .1.3.6.1.4.1.1663.1.1.1.1.34, was required to be certified.


2

CQ 573145SR34948434

Gigamon Gigavue420 switch, with systemObjectID .1.3.6.1.4.1.26866.1.1, was required to be certified.


2

CQ 573162SR31592740

Nokia ESA24 switch, with systemObjectID .1.3.6.1.4.1.738.1.5.100.1.1.555, was required to be certified.


2

CQ 573200SR34627392

Brocade SilkWorm switch, with systemObjectID .1.3.6.1.4.1.1588.2.1.1.43, was required to be certified.


2

CQ 573218SR36791214

Cisco PGW 2200 softswitch switch, with systemObjectID .1.3.6.1.4.1.99.1.1.3.34, was required to be certified.


2

CQ 573380SR34088370

Cisco ASR1002F router, with systemObjectID .1.3.6.1.4.1.9.1.1116, was required to be certified.


2



2

CQ 573441SR37293434

Cisco MCS7816I host, with systemObjectID .1.3.6.1.4.1.9.1.898, was required to be certified.


2

CQ 573444SR37622382

Cisco IE30008TC switch, with systemObjectID .1.3.6.1.4.1.9.1.959, was required to be certified.


2



2





25

Certified devices


CQ 573485SR36957840

Cisco VG204 switch, with systemObjectID .1.3.6.1.4.1.9.1.963, was required to be certified.


2

CQ 573490 Huawei S5352CEI switch, with systemObjectID .1.3.6.1.4.1.2011.2.23.97, was required to be certified.


2

CQ 508273SR32560296

Juniper EX8216 switch, with systemObjectID .1.3.6.1.4.1.2636.1.1.1.2.33, was required to be certified.


1

CQ 511331SR32564704

Cisco CDS router, with systemObjectID .1.3.6.1.4.1.9.1.1114, was required to be certified.


1

CQ 511943SR32010284

Juniper EX2500 switch, with systemObjectID .1.3.6.1.4.1.1411.102, was required to be certified.


1

CQ 563172SR31802994

Force10 C300 switch, with systemObjectID .1.3.6.1.4.1.6027.1.2.1, was required to be certified.

The device is certified. Files modified:• rules/discovery/

ic-force10-cseries-chassis.asl• rules/discovery/

ic-force10-cseries-health.asl

1

CQ 563585SR31376572

Ciena CN4200RS switch, with systemObjectID .1.3.6.1.4.1.7737.5.2.2.8, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_Ciena.conf

1

CQ 570761SR34493184



1

CQ 570771SR34490356CQ 570802

Alcatel OmniSwitch 6850-48X switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.4, was required to be certified.

The device is certified. File modified:conf//discovery/oid2type_Alcatel.conf

1

CQ 570772SR34493484 CQ 570805

Alcatel OmniSwitch 6850-P48L switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.6, was required to be certified.

The device is certified. File modified:conf//discovery/oid2type_Alcatel.conf

1






Certified devices

CQ 570774SR34493836



1

CQ 570787SR33552246

NetScreen 208 firewall, with systemObjectID .1.3.6.1.4.1.3224.1.10, was required to be certified.

The device is certified. File modified:conf/discovery/oid2type_NetScreen.conf

1

CQ 570788SR33553230



1

CQ 570790SR33553066

NetScreen SSG 550 firewall, with systemObjectID .1.3.6.1.4.1.3224.1.51, was required to be certified.

The device is certified. Files modified:• conf/discovery/oid2type_NetScreen.conf• conf/discover/

DISCOVERY_NETSCREEN.import• rules/discover/ic-netscreen-ssg-health.asl

1

CQ 570791SR33552888



1

CQ 570792SR33552840


The device is re-certified. File modified:conf/discovery/oid2type_NetScreen.conf

1

CQ 570794SR33552722

NetScreen ISG 1000 firewall, with systemObjectID .1.3.6.1.4.1.3224.1.28, was required to be certified.

The device is certified. Files modified:• conf/discovery/oid2type_NetScreen.conf• rules/discovery/

ic-netscreen-ssg-health.asl

1

CQ 570795SR33552508

NetScreen ISG 2000 firewall, with systemObjectID .1.3.6.1.4.1.3224.1.16, was required to be certified.


1

CQ 570801 Alcatel Omniswitch 6850-48 switch, with systemObjectID .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.2, was required to be certified.


1

CQ 570803 Avaya G450 Media Gateway host, with systemObjectID .1.3.6.1.4.1.6889.1.45.103.8, was required to be certified.

The device is certified. Files modified:• conf/discovery/oid2type_Avaya.conf• rules/discovery/

adapter/ic-interface-displayname.asl

1

CQ 570806 Zyxel VES1616FE switch, with systemObjectID .1.3.6.1.4.1.890.1.5.12.37, was required to be certified.

The device is certified. Files modified:• conf/discovery/import/oid2type_Misc.conf• conf/discovery/import/tpmgr-param.conf

1





27

Certified devices


CQ 571506SR35744176

Cisco Nexus 7018 switch, with systemObjectID .1.3.6.1.4.1.9.12.3.1.3.777, was required to be certified.

The device is certified. Files modified:• conf/discovery/oid2type_Cisco.conf• conf/discovery/

DISCOVERY_CISCO.import• rules/discovery/

ic-cisco-nexus-health.asl

1

CQ 571508SR36392482

Fortigate 80CM firewall, with systemObjectID .1.3.6.1.4.1.12356.101.1.810, was required to be certified.

The device is certified. Files modified:• conf/discovery/oid2type_Fortinet.conf• conf/discovery/

DISCOVERY_FORTINET.import• rules/discovery/ ic-fortigate-health.aslLibrary file modified:lib\sm_health_fortinet.dll (Windows)lib/libsm_health_fortinet.* (UNIX)

1

CQ 571684SR35814122

Cisco cat4500e-LANBASEK9-M switch, with systemObjectID .1.3.6.1.4.1.9.1.1178, was required to be certified.


1

CQ 533432SR36851664

Cisco Catalyst 6500 series firewall services module, with systemObjectID .1.3.6.1.4.1.9.1.522, is discovered as Class Router.

The device type of Cisco Catalyst 6500 series firewall services module, with systemObjectID .1.3.6.1.4.1.9.1.522 was certified as Router. The device type is now re-certified as Firewall.

File modified:conf/discovery/oid2type_Cisco.conf

1






Environment and system requirements

Environment and system requirementsThis section describes supported operating systems and how to verify the version number of EMC Ionix software.

Supported platforms

IP Management Suite 7.0.4.3 is supported on the following operating systems:

◆ Solaris 8, 9, and 10

◆ HP-UX 11i

◆ Red Hat Enterprise Linux AS 3 and AS 4

◆ Red Hat Enterprise Linux Server 5

◆ Microsoft Windows Server 2003 Enterprise Edition, SP1, SP2, and R2

◆ Microsoft Windows Server 2008 Enterprise Edition, SP1, SP2, and R2

Checking the version numberFrom BASEDIR/smarts/bin/, enter the following command:

sm_server --version

sm_server:IP_NETWORK_SUITE: V7.0.4.3(109823), 12-Sep-2011 11:54:01 Copyright 1995-2011, EMC Corporation - Build 25Foundation V7.0.2.135(109746), 09-Sep-2011 07:07:41 Copyright 1995-2011, EMC Corporation - Build 1

The output of the version option to sm_server indicates that this is version 7.0 Service Pack 4, Patch 3 of the IP Management Suite.

29

Installation


InstallationInstall the patch using one of the following methods:

• “Apply patch using Wizard mode” on page 29.

• “Apply patch using CLI mode” on page 31.

• “Apply patch using Unattended (Silent) mode” on page 32.

Note: Administrative privileges are required to install a patch.

Apply patch using Wizard modeWizard mode provides a graphical interface to the patch InstallShield software.

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

Run Wizard mode1. Run the appropriate setup command listed in Table 4 on page 29:

The InstallShield Wizard dialog box appears and closes. The Shutdown EMC Ionix Programs dialog box and the Welcome screen appear.

2. Click Next in the Welcome screen.

If you do not have administrative privileges, Next is disabled and a message appears. Exit and restart the installation with administrative privileges.

3. Read the license agreement, select I accept the terms of the license agreement, and click Next. If you do not accept the terms, you cannot complete the installation and must exit.

The InstallShield software detects all existing installations of the particular product suite and displays them in the suite upgrade screen.

4. Select the product suite to patch and click Next.

If there is only a single installation of the suite, it is selected. The Installed EMC Ionix services screen appears.

Table 4 Setup command syntax for Wizard mode

Operating system Wizard setup command syntax

HP-UX ./setup-IP-hpux-7_0_4_3-20110912.bin

Linux ./setup-IP-linux-7_0_4_3-20110912.bin

Solaris ./setup-IP-solaris-7_0_4_3-20110912.bin

Windows setup-IP-win-7_0_4_3-20110912.exe


Installation

5. If the InstallShield software detects services running from the install area, a list of service that the InstallShield software has detected is displayed. Stop each running services by pressing any key. Then click Next.

The InstallShield software then checks for any changes made to user-modifiable files. This check is only performed 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 InstallShield 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 and so that you are aware of the scope of the merge:

• A red x-mark indicates that a file was modified after the previous patch was installed.

• An orange exclamation point indicates that a file was modified before the previous patch was installed.

6. Choose whether to use merged files or the new files from the patch:

• Select Merge and use the files to merge changes from existing versions of the user-modifiable files into the new versions from the patch. These merged files will be used when the products are restarted. Unchanged versions of the new patch files are also installed, but they are named with an extension that corresponds to the patch number. This prevents the files from being used when the products are restarted. The existing files are backed up into a directory that is named using the version number of the previous patch release that was installed (BASEDIR/smarts/.local.bkp.<previous_version_number>).

• Select Merge but do not use the files to merge changes from existing versions of the user-modifiable files into the new versions from the patch. These merged files will be named with the extension .automerge and will not be used when the products are restarted. New, unmerged versions of the user-modifiable files from patch are also installed and are named so that they will be used by the products when they are restarted.The existing files are backed up into a directory that is named using the version number of the previous patch release that was installed (BASEDIR/smarts/.local.bkp.<previous_version_number>).

Click Next.

7. Verify the target installation directory and click Next.

The list of EMC Ionix 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” on page 33.

31

Installation


Apply patch using CLI modeCLI mode provides a text-based method for invoking the InstallShield 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 mode1. Change directory to the directory where you typically store patches, for

example the BASEDIR for your product suite.

2. Type the setup command listed in Table 5 on page 31 and press Enter.

A welcome message with information about the installation appears.

User selections and navigation in CLI modeDuring 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 6 on page 31 and then press Enter.

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.

Table 5 Setup command syntax for CLI mode

Operating system CLI setup command syntax

HP-UX ./setup-IP-hpux-7_0_4_3-20110912.bin -console

Linux ./setup-IP-linux-7_0_4_3-20110912.bin -console

Solaris ./setup-IP-solaris-7_0_4_3-20110912.bin -console

Table 6 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


Installation

Please choose from the following options:[ ] 1 - I accept the terms of the license agreement.[X] 2 - I do not accept the terms of the license agreement.

To select an item enter its number, or 0 when you are finished:[0]

Each choice is numbered and has a pair of brackets. The default menu choice (‘2’ in this example) has an X in the brackets. Type the number of the desired selection and press Enter. In the case of the license agreement, you must accept the agreement by typing 1 and pressing Enter.

The screen is redisplayed with an X in the brackets next to the selected item. When you are satisfied with the indicated selection, type 0 (zero) and press Enter.

The rest of the installation follows the same steps as the Wizard Mode but uses the above method for selecting choices and navigating through the installation steps.

When the patch installation is complete, reconcile the configuration files as described in “Reconcile user-modifiable files” on page 33.

Apply patch using Unattended (Silent) mode Unattended mode installs the patch without user input or a response file. When invoking the install program, you must specify the location of the product suite to be patched.

To invoke an unattended installation of the patch, type the appropriate setup command from Table 7 on page 32 and then press Enter.

Table 7 Setup command syntax for Unattended mode

Operating system Unattended setup command syntax

HP-UX ./setup-IP-hpux-7_0_4_3-20110912.bin -silent-G replaceNewerResponse="Yes to All" -P rpProduct.installLocation=<BASEDIR>-W mergeSummaryPanel.choiceMergeResult={auto|manual}>

Linux ./setup-IP-linux-7_0_4_3-20110912.bin -silent-G replaceNewerResponse="Yes to All" -P rpProduct.installLocation=<BASEDIR>-W mergeSummaryPanel.choiceMergeResult={auto|manual}

Solaris ./setup-IP-solaris-7_0_4_3-20110912.bin -silent-G replaceNewerResponse="Yes to All" -P rpProduct.installLocation=<BASEDIR>-W mergeSummaryPanel.choiceMergeResult={auto|manual}

Windows C:\setup-IP-win-7_0_4_3-20110912.exe -silent-G replaceNewerResponse="Yes to All" -P rpProduct.installLocation=<BASEDIR>-W mergeSummaryPanel.choiceMergeResult={auto|manual}

<BASEDIR> is the location where the EMC Ionix 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.

33

Log files


When the patch installation is complete, reconcile the configuration files as described in “Reconcile user-modifiable files” on page 33.

Log filesTable 8 on page 33 lists the files that the InstallShield software creates during the install process.

Install logThe installer creates an Install log file listing all actions performed by the installation. You should not need to 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 LogThis log lists the files in the BASEDIR/smarts/local directory structure that were merged. For each merged file, the log lists the location and name of the file. If any file cannot be merged due to conflicts, this is also noted. In addition, the log lists the name and location for unmerged versions of all user-modifiable files that are included in the patch.

Reconcile user-modifiable filesThe InstallShield software is designed to preserve your changes to user-modifiable files when installing new versions of these files. The InstallShield 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:

Table 8 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, 7.0.4.3.


Reconcile user-modifiable files

◆ 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 InstallShield 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. See “Resolve issues in conflict files” on page 35 for 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 InstallShield 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” on page 36 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” on page 35 for a procedure to resolve the conflicts and use the files.

The InstallShield software also create 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” on page 34 for a description of the backup files.

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

Backup versions of user-modifiable files

The InstallShield software always creates backup versions of user-modifiable files included in the patch and all current versions of the files. Table 9 on page 35 lists the purpose and location of all user-modifiable files that the InstallShield software creates during the install process and their locations.

35

Reconcile user-modifiable files


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.7.0.4.3.log.

2. Review the log:

• Resolve conflicts in files manually. See “Resolve issues in conflict files” on page 35.

• 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” on page 36.

Resolve issues in conflict files

If a conflict occurs, the InstallShield software creates conflict files that indicate which portions of the file are an issue.

Review the conflict files and resolve issues using the following procedure:

1. Open the user-modifiable file where the conflict occurs using sm_edit. Conflict files are named using the following convention:.

.<filename>.<patch version>.conflict

For example, the conflict file for discovery.conf is named .discovery.conf.7.0.4.3.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>.7.0.4.3.)

Table 9 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.7.0.4.3

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.7.0.4.3/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, 7.0.4.3


Uninstallation

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-SA"

 serverName = "INCHARGE-SA"

 serverName = "TESTINCHARGE-SA"



Delete the incorrect sections from the conflict and ensure the correct section is uncommented.

4. Save and close the file.

Rename and use Automerge filesAutomerge files are only created if you choose the Merge but do not use the files option during installation, and no conflicts occurred during the merge process.

1. Open and review merged files using sm_edit. Merged files are named .<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-modifable file from the patch is at .<standard filename>.7.0.4.3.

UninstallationUninstalling a patch removes all previously applied patches and returns the EMC Ionix software to the baseline product version.

Note: Administrative privileges are required to uninstall a patch.

WARNING

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.

37

Uninstallation


Roll back to a previous patchIf 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 200 to Patch 198, you must uninstall Patch 200, then reinstall Patch 198.

Uninstall patch using the Control Panel (Windows only)

WARNING

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 Control Panel 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 2003, double-click Add/Remove Programs.

3. From the programs window, select EMC Ionix IP Management Suite 7.0.4.3.

4. Click Change/Remove

The uninstaller program proceeds as described in “Uninstall steps” on page 38.

Uninstall patch using the uninstaller programUse the uninstaller program to uninstall a patch:

WARNING

Do not to use the uninstaller program in the _uninst directory because it will remove the entire product.

1. Change directory or use the file navigator to find the _rpuninst directory. For example:

• /opt/InCharge/IP/_rpuninst on UNIX systems

• C:\InCharge\IP\_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

The uninstall proceeds as described in “Uninstall steps” on page 38.

Uninstall steps1. 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.

39

Troubleshooting and getting help


Troubleshooting and getting helpEMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

http://powerlink.emc.com


Troubleshooting and getting help

Copyright © 2011 EMC Corporation. All rights reserved.

Published September 13, 2011

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Documents

EMC Ionix IP Management Suite - Dell EMC Japan These notes contain information about the EMC Ionix IP Management Suite Version 7.0 Service Pack 4, Patch 3 (IP 7.0.4.3). Topics include: