Sun StorEdge Enterprise Storage Manager 1.2 Topology Reporter Release Notes Table of ContentsPrevious ChapterNoNextNoIndex


Release Notes

These release notes describe the following topics:

Features In This Release

The Sun StorEdgetrademark Enterprise Storage Manager 1.2 Topology Reporter software enables you to view and manage your storage area network (SAN) or direct-attached storage (DAS) environment. Using a Web-browser user interface (UI) or the command-line interface (CLI), you can:

The software includes agent, management, and database software installed on host machines in your environment. The agent software continuously collects information from devices in your environment and stores the information in a database. This database contains the information needed to build a data model of your environment. The agent software updates the data model depending on discovered changes in device status.

You can view and manage this information at any time by using a Web browser or CLI. For example, you can view a graphic representing your environment and click parts of the graphic to see details about that host machine or device.

Product Changes

The version 1.2 software includes, but is not limited to, the following changes or improvements from versions 1.0 and 1.1:

System Requirements

The software packages require that you have the latest network, switch, and host bus adapter software packages and updates. These packages and updates are available from:

http://www.sun.com/storage/san

TABLE 1 shows the required software operating environment and SAN software for the topology reporter, configuration services, and diagnostic expert software.

TABLE 1 Required Operating Environment and SAN Software

Required SAN Software

The Sun StorEdge Enterprise Storage Manager 1.2 software requires that you have installed the Sun SAN Foundation Kit software, version 4.2. The SUNWsan software, related software, and updates are available from:

http://www.sun.com/storage/san

Patches are available from:

http://sunsolve.sun.com/

Required Operating Environment

Solaristrademark 8 10/01 (also known as Update 6) with the latest patch cluster, including patches for the Javatrademark 2 SDK v1.4.0, available at:

http://java.sun.com/j2se/1.4/install-solaris-patches.html

 

Solaris 9

Patches

Patch number 114616-xx (xx indicates the latest patch revision level)

See also Recommended Patch If Your SAN Includes the Sun StorEdge 6320 Storage System.

Patches are available from:

http://sunsolve.sun.com/

Required Web Browser (minimum version)

Netscape Navigator version 4.79

Microsoft Internet Explorer version 5.0


Table describes the minimum required revision levels of the SAN, operating system, and Web browser software

TABLE 2 shows supported and required hardware.

 

TABLE 2 Supported and Required Hardware

CD-ROM Requirement

A CD-ROM drive connected to the host machine where the software is to be installed.

Host Machines, Supported

The software is supported on host machines using the Solaris operating environment. Hosts include but are not limited to:

  • Sun Enterprisetrademark server models 220R, 250, 420R, 450
  • Sun Enterprise server models 3500, 4500, 5500, 6500
  • Sun Firetrademark server models 280R, 3800, 4800, 4810, and 6800

 

Management stations include the above list and the following workstations:

  • Sun Ultra workstation models 5, 10, 60, and 80

Supported and Discoverable Attached Storage

Sun StorEdge T3 arrays, minimum firmware release 1.171

Sun StorEdge T3+ arrays, minimum firmware release 2.01

Sun StorEdge 3510 FC array

Sun StorEdge 3900 and 6900 Series storage subsystems

Sun StorEdge 6120 Series arrays1

Sun StorEdge 6320 Series systems1

Sun StorEdge 9900 Series systems
(includes the Sun StorEdge 9910 and Sun StorEdge 9960 system arrays)

1. The configuration service software supports these storage arrays or subsystems

 

Switches, Supported

Sun StorEdge Network FC Switch8 and Switch-16

Brocade Communications Systems SAN switches

McDATA Corp. 2 Gbyte per second 16, 32, and 64 port SAN switches

Disk and Memory Space Requirements, Total

 

1 Gbyte total disk space in the /opt directory for all packages

512 Mbytes system memory minimum

Disk and Memory Space Requirements, Topology Reporter

 

Management station installation and operation:

  • 640 Mbytes of disk space
  • 512 Mbytes system memory

 

Agent station installation and operation:

  • 71 Mbytes of disk space
  • 512 Mbytes system memory


If the management and agent station is a single machine:

  • 711 Mbytes of disk space
  • 256 Mbytes system memory (512 Mbytes preferred)

Disk and Memory Space Requirements, Configuration Service

 

200 Mbytes of disk space

Disk and Memory Space Requirements, Diagnostic Expert

 

60 Mbytes of disk space in the /opt directory (default installation directory)

30 Mbytes of disk space in the /var/opt directory (default installation directory)

128 Mbytes system memory


Recommended Patch If Your SAN Includes the Sun StorEdge 6320 Storage System

Please install patch number 114616-xx if you wish to use the Sun StorEdge Enterprise Storage Manager 1.2 software to manage a Sun StorEdge 6320 storage system. (xx indicates the latest patch revision level.)

Patches are available at
http://sunsolve.sun.com/

Table describes the supported and required hardware for the Sun StorEdge Enterprise Storage Manager software.

Known Issues and Bugs

The following paragraphs describe known issues and software bugs.

Known Issues

This section includes the following known issues:

Zoning By World Wide Name

The topology reporter software supports port-based zoning. If wish to implement World Wide Name (WWN) zoning, you must install patch 114616-01.

Use the esminstall Script to Install the Sun StorEdge Enterprise Storage Manager Software

The documentation available for each Sun StorEdge Enterprise Storage Manager software component (topology reporter, configuration service, and diagnostic expert) might include references to installation scripts named install or procedures to install software using the pkgadd(1M) command.

Do not use these procedures to install the software. Use the esminstall script located on the Sun StorEdge Enterprise Storage Manager 1.2 product CD, as described in the Sun StorEdge Enterprise Storage Manager 1.2 Installation Guide.

Ensure that the Agent Stations in Your SLP Scope Use the Same Locale

The management station and agent stations are considered to be in the same SLP scope when each machine has the same scope setting and locale. The Sun StorEdge Enterprise Storage Manager 1.2 Installation Guide describes how to configure the SLP scope settings and rules for the topology reporter software.

Using JNI Host Bus Adapters

If your storage network configuration includes a JNI host bus adapter card, ensure that you have the latest version of your card's JNIsnia package for the Solaris operating environment. This package is available at the following URL:

http://www.jni.com

Also ensure that your JNI HBA card drivers are current. The latest package and drivers are required if you are using the topology reporter software.

Networks with Multicasting Features Disabled

If your management station and agent hosts reside on separate network segments and multicast network traffic cannot pass between these segments (that is, multicasting is disabled on your network), the Sun StorEdge Enterprise Storage Manager software might be prevented from discovering agents deployed to hosts located within a configured network segment.

Updating or Changing an HTTPS Site Certificate

The topology reporter software includes a sample secure web server (HTTPS) .keystore site certificate in the /etc/var/SUNWnsm/etc/ directory. This file provides authentication when you use a secure HTTP (HTTPS) connection to the topology reporter web browser user interface. The default URL for this connection is https://hostname:8543/.


Note - A certificate is a digitally signed statement vouching for the identity and public key of an entity (person, company, and so on). Certificates can be self-signed or issued by a Certification Authority (CA). Certification Authorities are entities that are trusted to issue valid certificates for other entities. Well-known CAs include VeriSign, Entrust, and GTE CyberTrust.


You can update the certificate or use an existing certificate on the topology reporter management station. Perform the following procedures at the machine you designate as a management station.


procedure icon  To Update the .keystore File

1. Log in to the management station as superuser.

2. Type the following command on a single line to update the .keystore file:

  

# keytool -keystore -genkey -alias ESM_TR -keypass changeit -storepass changeit -keyalg RSA -validity valDays

where valDays is the length of time in days that the certificate remains valid. The certificate will expire after the number of days specified.

The program displays the following prompts: 

What is your first and last name?

  [Unknown]:

What is the name of your organizational unit?

  [Unknown]:

What is the name of your organization?

  [Unknown]:

What is the name of your City or Locality?

  [Unknown]:

What is the name of your State or Province?

  [Unknown]:

What is the two-letter country code for this unit?

  [Unknown]:

Is CN=<first and lastname>, OU=<unit>, O=<organization>, L=<city>, ST=<state>, C=<country> correct?

  [no]:  yes

3. Respond to each prompt.

4. Ensure that the topology reporter software is running: 

# /opt/SUNWnsm/bin/sstr_ctl --status

The following messages are displayed: 

Status of Sun StorEdge(TM) Topology Reporter Components

 

Core Components:

 

PostgreSQL for SSTR............running.

The CRE for SSTR...............running.

Tomcat for SSTR................running.

 

Supporting Applications:

 

SLP............................running.

iPlanet iMQ....................running.

  • If the status messages show that any component is ...not running, try the following: 

    • # /etc/init.d/sstrd stop

    # /etc/init.d/sstrd start

    # /opt/SUNWnsm/bin/sstr_ctl --status

5. Test the certificate by entering the following URL in a web browser such as Netscape Navigatortrademark: 

https://hostname:8543/

6. Click View in the certificate acceptance pop-up window to display the certificate information.

7. Click Accept if the certificate information is correct.


procedure icon  To Use an Existing Certificate

1. Log in to the management station as superuser.

2. Stop the topology reporter software: 

# /opt/SUNWnsm/bin/sstr_ctl stop


Note - Also stop the software on each agent station.


3. Edit the /opt/SUNWnsm/util/tomcat/conf/server.xml.default file using a text editor such as vi(1M).

4. Search for the word keystoreFile.

The bold text indicates the lines to edit: 

keystoreFile="/etc/opt/SUNWnsm/etc/.keystore"

keystorePass="changeit"

5. Change the keystore= directory path to the path of your .keystore file.

6. Change the keystorePass= password to your .keystore file's password

7. Save and exit the file.

8. Configure the topology reporter software: 

# /opt/SUNWnsm/bin/sstr_ctl -c

9. Respond to the prompts with a yes (y) answer, including the prompt to restart the software.

The topology reporter web server is now reconfigured and restarted using the new information.

Security


Note - This security issue results from the use of the Remote Method Invocation (RMI) registry and is not particular to the Sun StorEdge Enterprise Storage Manager 1.2 software.


The RMI Registry used in the Sun StorEdge Enterprise Storage Manager 1.2 software to register look up middle-tier services is unprotected. This situation implies that a malicious user can carry out attacks against the software by using the RMI Registry as the initial point of attack. Possible attacks include, but are not limited to, the following:

  • Denial of service - implemented by removing service proxies from the RMI registry; the attack can be launched from the machine hosting the management station software

  • Capture of information - implemented by replacing service proxies in the RMI registry; the attack can be launched from the machine hosting the management station software

  • Unauthorized access of services - implemented by retrieving service proxies from the RMI registry; the attack can be launched from a remote host

If Sun StorEdge Component Manager Software is Installed on Your Host

If the Sun StorEdge Component Manager software is already installed on the host you have chosen as the management station (including configurations where the management station and agent station are the same host), you might have to select a different web server port number for the topology reporter software.

The default Component Manager non-secure web server port is 8180. The 8180 port is also the default for the topology reporter non-secure (non-SSL) server. Make sure that the topology reporter software non-secure Tomcat web server port is different from the Component Manager web server port.

If the already-installed Component Manager non-secure web server port is 8180, respond to the /opt/SUNWstm/bin/esmconfig configuration script prompts for the topology reporter software as follows. User responses are in bold text in this example showing the port choice as 8280: 

Run Tomcat non-SSL server on port 8180 [y,n,?] n

 

Please enter the Tomcat non-SSL server port: 8280

 

Run Tomcat SSL server on port 8543 [y,n,?] y

 

Do you want to use the SLP scope nsmscope [y,n,?] y

 

Configuration successful.

End: TR configuration.

See also Possible Port Conflicts and TABLE 3.

The Sun StorEdge Enterprise Storage Manager 1.2 Software Installation Guide describes the installation and configuration procedures in detail.

Possible Port Conflicts

Generally, you can use the default values for web server, telnet, and other ports when prompted by the /opt/SUNWstm/bin/esmconfig configuration script. Ensure that the default port numbers do not conflict with any other software you might have installed.

TABLE 3 lists the default ports for the topology reporter, configuration services, and diagnostic expert software located on the Sun StorEdge Enterprise Storage Manager 1.2 product CD.

 

TABLE 3 Default Ports, Sun StorEdge ESM 1.2 Software

Sun StorEdge ESM 1.2 Software

Non-Secure Socket Layer Port

SSL Port

Apache HTTP Server Port

Postgres SQL Port

Additional Default Ports

Topology reporter

8180

8543

1024

5437

Not applicable

Configuration service

8080

9443

1024

Not applicable

CLI telnet port - 8023

ssh proxy - 8514

Sun StorEdge 9900 Series software - 2001

Solaris CIM/WBEM port - 8181

Diagnostic Expert

8088

8443

Not applicable

Not applicable

Not applicable


Web Browser Requires the Correct Java Plug-in Application for Switch Software

To launch the Brocade Communications Systems WebTools switch software in a web browser from the topology reporter software, ensure that you have the correct Javatrademark web browser plug-in software installed. For example, the Netscape Communicator web browser might display a blank browser page or issue an error message such as: 

This page contains information of a type (application/x-java-applet; version=1.2.2) that can only be viewed with the appropriate Plug-in.

Click OK to download Plugin.

See the documentation for your Brocade Communications System switch and web browser for more information about web browser configuration requirements.

Moving Connectors on Switch Ports

If your environment includes a QLogic switch and you have moved a connector to a different switch port, the connector type information is not reflected in the topology reporter database. That is, the connector type information is not updated on the topology reporter web browser interface or in the command-line output and does not show the move to a different port.

single-step bulletTo show the correct information, reboot the switch after moving connectors.

Use the Assets page or the sstr command-line interface to see switch port information.

Documentation Errata

  • Sun StorEdge Enterprise Storage Manager 1.2 Topology Reporter Administration and Operations Guide

1. In Chapter 4, "Specifying the Sun StorEdge T3 Array Application" and "Specifying the Sun StorEdge 6000 Family Application", the Sun StorEdge Configuration Service software selection app-name is referred to as SCCS.

The correct app-name is SSCS.

2. In Chapter 3, "To Launch the Software from the Sun Management Center Main Console", the text and referenced figures indicate that you view the topology reporter management and agent station status from the Remote Systems link in the Sun Management Center main console Browser tab.

In most installations, you view the topology reporter management and agent station status under the Local Applications folder in the Sun Management Center Browser tab.

  • Sun StorEdge Enterprise Storage Manager 1.2 Installation Guide

1. In Chapter 2, "The esminstall and esmuninstall Script Options", the second bulleted paragraph states that the esmuninstall script is located in the /var/opt/SUNWstem/ directory.

The esmuninstall script is located in the /opt/SUNWstm/bin/ directory after you install the software.

2. In Chapter 2, "Sun Management Center Integration" and "Before You Can Launch the Topology Reporter Software", a paragraph states the following:

Ensure that the Sun Management Center SUNWesagt package is installed and started on each agent station.
The corrected paragraph is as follows:
Ensure that the Sun Management Center agent software (including the SUNWesagt package) is installed and started on each agent station.

3. In Chapter 2, "To Launch the Software from the Sun Management Center Main Console", the text and referenced figures indicate that you view the topology reporter management and agent station status from the Remote Systems link in the Sun Management Center main console Browser tab.

In most installations, you view the topology reporter management and agent station status under the Local Applications folder in the Sun Management Center Browser tab.
  • Sun StorEdge Diagnostic Expert 1.2 User's Guide

This guide describes how to install the Sun StorEdge Diagnostic Expert 1.2 software by using the pkgadd(1M) command. Do not use this command.
Use the esminstall script located on the Sun StorEdge Enterprise Storage Manager 1.2 product CD, as described in the Sun StorEdge Enterprise Storage Manager 1.2 Installation Guide.
See the Sun StorEdge Enterprise Manager 1.2 Installation Guide for complete information about installing and configuring the software.

Known Bugs

This section describes the following known bugs and workarounds, if applicable:

Bug 4642875 (P3/S2) Topology Reporter Software Fails if One or More Supporting Software Components Fail

If any of the supporting topology reporter software components (such as the database or Apache software) fails or crashes, the topology reporter software stops functioning with no alarms generated or notifications sent to the user. Error messages are written to the /var/sadm/install/logs/SUNWnsm.log log file.

Workaround

1. Check the log files if a component is not running.

2. Stop the software on the management and agent stations:


Note - sstrd start also starts the SLP service (slpd). However, sstrd stop does not stop the SLP service. To stop the SLP service, type:
/etc/init.d/slpd stop 


# /etc/init.d/sstrd stop

# /opt/SUNWnsm/bin/sstr_ctl --status

3. Fix any errors shown in the log files.

4. Start the software and check its status: 

# /etc/init.d/sstrd start

# /opt/SUNWnsm/bin/sstr_ctl --status

Bug 4796475 (P2/S2) Device Information Might Not Appear Correctly for Sun StorEdge T3 Arrays That Include Partner Pairs with Multiple Device Paths

When Sun StorEdge T3 storage arrays are configured as partner pairs with multiple device paths ("multipath"), the software might periodically fail to display the device paths in the web browser user interface.

Workaround

Use the format(1M) command without options to view device path information for these arrays.

Bug 4816105 (P3/S4) "Device not connected to SAN" Message Might Be Displayed for Switches Connected to a Sun StorEdge 6910 System

The Show SAN Connectivity feature in the web browser user interface might report a status of Device not connected to SAN for host-side switches connected to a Sun StorEdge 6910 storage system.

Workaround

None.

Bug 4816295 (P3/S4) The Management Station Does Not Find Agents on When the Agent Stations are Multi-homed

The topology reporter management station cannot receive information from an agent station machine if the agent station machine has more than one network interface (that is, it is a multihomed machine). This situation occurs if the default network defined on the agent station is not the same default network defined on the management station.

Workaround

None.

Bug 4827348 (P1/S1) Topology Reporter Uses Default RMI Registration Port 1099

The topology reporter software starts and registers to its own rmid process using the default Remote Method Invocation (RMI) Registry port 1099.

However, port conflicts can occur if a user is running other software on the management station that is already running an rmid process using the default RMI Registry port of 1099. Other RMI-dependent applications might fail to run as intended if the topology reporter is using the default RMI Registry port 1099.

Specifically, if the McDATA Enterprise Fabric Connectivity (EFC) Manager and Bridge Agent software are installed and running (the Bridge Agent runs on an agent station), the topology reporter might not be able to complete or perform device discovery.

To use the McDATA software and topology reporter software, perform the steps in the workaround that follows.

Workaround for McData Software

1. Stop the topology reporter software on each station. 

# /etc/init.d/sstrd stop

2. Stop the McDATA software on each station.

3. Install patch number 114616-xx on each management and agent station.

xx indicates the latest patch revision level.

4. Edit the /opt/SUNWnsm/util/cre/population/transient.xml file, using an ASCII text editor such as vi(1M).

Search for the following text and note the port number in bold text:

CODE EXAMPLE 1 transient.xml File 
<!-- RMI Registry Facility -->

 <instance>

 <component package="com.sun.netstorage.mgmt.facility.nsm.registry" version="1.0"/>

        <id>7069d597dd444de590ecb1c6a900f7e7</id>

        	<factory>pinned</factory>

<class>com.sun.netstorage.mgmt.facility.nsm.registry.RMIRegistryFacility</class>

        <properties>

        <keyvalue key="registryPort" value="1099"/>

        </properties>

     </instance>

5. Change the value= port number to a port number that is not in use.

See If Sun StorEdge Component Manager Software is Installed on Your Host and Possible Port Conflicts.

6. Save and exit the file.

7. Install and start the McData Bridge agent on each agent station in your environment, if you wish to use the EFC switch management application.

8. Restart the topology reporter software. 

# /etc/init.d/sstrd start

9. Make sure the McDATA Bridge agent software is started on each agent station.

Bug 4831937 (P4/S4) SLPFindSrvs Call Fails to Find Agents

The Service Locator Protocol (SLP) fails to find registered services in a unique SLP scope. In this case, the topology reporter software then cannot find devices in the SAN when it is configured in the same scope.

Workaround

This behavior usually occurs if the management or agent station machine running the Solaris operating environment has a host name that also contains the host's domain (for example, hostname.domain.superdomain). Change the full host and domain name(s) to just the host name in files where the host name is indicated, such as:

/etc/hosts

/etc/hostname.hme0

/etc/nodename

/etc/net/ticlts/hosts

/etc/net/ticots/hosts

/etc/net/ticotsord/hosts

Release Documentation

Application

Title

Part Number

Man pages

sstr

ssde

sscs

Not applicable

Release and product information

Sun StorEdge Configuration Service 1.2 Release Notes

817-0998

 

Sun StorEdge Diagnostic Expert 1.2 Release Notes

817-0197

 

Sun StorEdge Enterprise Storage Manager 1.2 Roadmap

817-1039

 

Sun StorEdge SAN Foundation Release Notes

817-0071

 

Sun StorEdge Traffic Manager Software Release Notes

817-0385

Installation

Sun StorEdge SAN Foundation Kit Installation Guide

817-1244

 

Sun StorEdge Enterprise Storage Manager 1.2
Installation Guide

817-1037

 

Sun StorEdge SAN Foundation Kit Configuration Guide

817-1245

 

Sun StorEdge Traffic Manager Software Installation and Configuration Guide

816-1420

System administration

Sun StorEdge Enterprise Storage Manager 1.2
Topology Reporter Administration and Operations Guide

817-1112

 

Sun StorEdge Configuration Service 1.2 Administrator's Guide

817-0997

 

Service Location Protocol Administration Guide

806-1412

User and diagnostic

Sun StorEdge Diagnostic Expert 1.2 User's Guide

817-0195


Service Contact Information

If you need help installing or using this product, call 1-800-USA-4SUN, or go to the following web site:

http://www.sun.com/service/contacting/index.html



  Sun StorEdge Enterprise Storage Manager 1.2 Topology Reporter Release Notes 817-1111-11 Table of ContentsPrevious ChapterNoNextNoIndex


Copyright © 2003, Sun Microsystems, Inc. All rights reserved.