What is the correct call-home configuration on

VNX?
Article Number:000016259 Version:1
Key Information
Original Create Date: Fri Nov 16
05:52:33 GMT 2012
First Published: Fri May 31
Channels: Customer , Internal App
05:06:00 GMT 2013
Originally Created By: Amy
Last Modified: Fri May 31
Wang
05:06:00 GMT 2013
Summary:
Audience: Level 30 = Customers

Article Type: How To

Validation Status: Final Approved
Last Published: Fri May 31
05:06:00 GMT 2013

Article Content
Goal: What is the correct call-home configuration on VNX?
Environment: Product: VNX Series
EMC SW: EMC Secure Remote Support (ESRS) Gateway
Feature: VNX Email Home
Resolution: If it is a VNX Unified/File system, control station will function as the component to generate
call home messages. Do not configure e-mail home from SPs on this type of system as it will
cause duplicate call-home alerts.
To verify if call-home has been configured properly:
1. Open a secure shell (SSH) to the primary Control Station.
2. List all the call-home templates used by SP A directly: /nas/sbin/navicli -h SPA
eventmonitor -monitor -listmapping -system "A-IMAGE" (A-IMAGE should be
replaced by the network name of SP A.)
3. Remove all the call-home templates used by SP A: /nas/sbin/navicli -h SPA
eventmonitor -monitor -stoptemplate -system "A-IMAGE"
4. Repeat Step 2 and Step 3 on SP B to remove all call-home templates used by SP B.
5. Verify if connect_home has been configured correctly on the Control Station:
/nas/sbin/nas_connecthome -info
A correct call-home configuration should look like the following:
$ /nas/sbin/nas_connecthome -info
Email :
Priority
= Enabled
Sender Address
= connectemc@emc.com >> An email address within the customer
domain
Recipient Address(es) = emailalert@emc.com

Subject
= CallHome Alert
Primary :
Email Server
= xx.xx.xx.xx >> IP address of the SMTP server
Email IP Protocol
= IPv4
Secondary :
Email Server
=
Email IP Protocol
= IPv4
6. Verify if the system can connect home successfully: /nas/sbin/nas_connecthome -test
-email_1
If it is a VNX Block-only system, an ESRS IP Client should be deployed as the centralized
monitor to send call-home alerts. Emailing home directly from any SP is not a supported
configuration anymore. The ESRS IP Client uses ConnectEMC to send back call-home alerts.
The installation will be different depending on whether the customer has deployed ESRS GW
Client:
To install the ESRS IP Client, the customer must prepare the following:
1. A Physical Windows Host or Virtual Machine (Monitor Station) with a CPU speed of 1
GHZ or greater, a total physical memory size of 2 GB or greater, 1 GB hardware space,
installed .NET framework 2.0 and the latest JRE version 1.6.x.
2. A fixed/static IP address must be reserved for the Monitor Station.
3. The following TCP ports must be open on the Monitor Station: 80(inbound/outbound) /
443(inbound/outbound) / 25(outbound) / 6389(outbound) / 5414(outbound) /
9519(outbound)/
4. An existing Powerlink account.
5. IP address of a portal VNX system.
If the customer has already deployed ESRS GW Client, the ESRS IP Client must be installed on
a different server from which ESRS GW Client. During the installation at the step Call Home
Configuration, select DO NOT Install and use EMC Secure Remote Support. Manually
configure call-home later using ConnectEMC after the installation:
1. Click the Connect Console icon on the desktop.
2. On the left panel, expand Connection directory and highlight General icon. Go to Menu
> Connection > Add Connection > Email Connection
3. A connection record pane opens and then enter the following data in the connection pane:
4.
1. Recipients: emailalert@emc.com
2. Mail Server: IP address of the ESRS GW server
3. Sender: connect@emc.com (Must be an email address in emc.com domain)
4. Description: Enter an email connection description of your choice
5. Alert Type: Select Use this connection first ( Primary ) from the drop down menu
6. Timeout: 300
7. Retries: 3
8. Include Data: Yes
9. Email Type: Select HTML
5. Click the Save button to save the configuration.
6. Clickthe Test button to send an test event.
After the ESRS IP Client is installed, the monitor station should be configured as centralized
monitor of the VNX automatically. If not, configure it manually following these steps:
1.

1. Launch Unisphere Client and login the portal VNX system with Administrative
credentials.
2. Go to Monitoring and Alerts > Notifications > Distributed Monitors .
3. Click SP A to display templates in use. Right click the template > Click Stop Using.
4. Repeat the same steps on SPB to remove call-home templates for SP B.
5. Switch to Centralized Monitors tab. If there is a centralized monitor, go to Step 8.
6. Click Configure > Right-click Portals > Click Add Portals > Go to Subnet to Add >
Enter the first three octets of the IP for the Monitor Station (for example, if the Monitor
Station uses 10.32.125.100, enter 10.32.125) -> Click Scan > The monitor station will
appear in the discovered system > Click the Monitor Station > Move it to Selected
System > Click OK.
7. Right-click the Portal> Select Add Centralized Event Monitor > Enter the IP address of
the Monitor Station > Click OK.
8. Select the centralized monitor and click the Monitor System.
9. Select the VNX system to be monitored by this centralized monitor from the drop-down
menu.
10. Right-click the Centralized Monitor > Click Select Global Template > Select the
template from drop-down menu.
Notes: Frequently Asked Questions (FAQs) :
1. What is the correct version of Java required to install ESRS IP Client?
Answer: If Java 7 is installed already, you must uninstall it and re-install Java 6. Otherwise,
rules check will not pass. Java 6 update 32 can be found at ftp://ftp.emc.com/pub/rcm/app/vnx/.
2. What is the minimum space required to install ESRS IP Client?
Answer: It is recommended that the customer should have at least 1 GB to facilitate the
installation.
3. Does ESRS IP Client install the ConnectEMC as well?
Answer: Yes, ConnectEMC is part of the ESRS IP Client installation.
4. If the workstation on which customer wants to install the ESRS IP Client already has
ConnectEMC installed does it need to be uninstalled?
Answer: No need to do it manually. ConnectEMC will be re-installed during ESRS IP Client
installation.
5. If customer has already configured ESRS GW Server, can I install the ESRS IP Client on the
same workstation?
Answer: No, ESRS IP Client must be installed on another server. During the installation, select
do not use ESRS as the primary method for call home feature and manually configure
call-home later with ConnectEMC.
6. Do I still need to remove distributed template from SP if customer chooses to install the ESRS
IP Client?
Answer: Yes, ESRS IP Client aims to swap call home configuration from distributed
monitoring to centralize monitoring. The server where ESRS IP Client is installed will function

as the centralized monitor.

7. Can I install the ESRS IP Client on the same server where Unisphere Server has been installed?
Answer: No, ESRS IP Client must be installed on another server.
Please refer to the latest VPG for more details on this procedure. The documents can be found under
ESRS, UDoctor and Email-Home Procedures > Remote Support Installations.
Article Metadata
Product: VNX Series, ConnectEMC, Secure Remote Support Single Product Configuration
Primus/Webtop solution ID: emc309065
RCA Status: Not Started
Shared: Yes
Requested Publish Date: 5/25/2013 12:59 PM
Originally Created By: Amy Wang
External Source: Primus