3Com 3CR15600 - Enterprise Management Suite User manual

http://www.3com.com/
Part Number 10015165 Rev.2
Published September 2007
ENTERPRISE MANAGEMENT SUITE
GETTING STARTED GUIDE
Enterprise Management Suite
Release 2.41

3Com Corporation
350 Campus Drive
Marlborough, MA
01752-3064
Copyright © 2001 - 2007, 3Com Corporation. All rights reserved. No part of this
documentation may be reproduced in any form or by any means or used to make any
derivative work (such as translation, transformation, or adaptation) without written
permission from 3Com Corporation.
3Com Corporation reserves the right to revise this documentation and to make
changes in content from time to time without obligation on the part of 3Com
Corporation to provide notification of such revision or change.
3Com Corporation provides this documentation without warranty, term, or condition
of any kind, either implied or expressed, including, but not limited to, the implied
warranties, terms, or conditions of merchantability, satisfactory quality, and fitness
for a particular purpose. 3Com may make improvements or changes in the product(s)
and/or the program(s) described in this documentation at any time.
If there is any software on removable media described in this documentation, it is
furnished under a license agreement included with the product as a separate
document, in the hardcopy documentation, or on the removable media in a directory
file named LICENSE.TXT or !LICENSE.TXT. If you are unable to locate a copy, please
contact 3Com and a copy will be provided to you.
UNITED STATES GOVERNMENT LEGENDS:
If you are a United States government agency, then this documentation and the
software described herein are provided to you subject to the following:
United States Government Legend: All technical data and computer software is
commercial in nature and developed solely at private expense. Software is delivered
as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995)
or as a commercial item as defined in FAR 2.101(a) and as such is provided with only
such rights as are provided in 3Com’s standard commercial license for the Software.
Technical data is provided with limited rights only as provided in DFAR 252.227-7015
(Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to
remove or deface any portion of any legend provided on any licensed program or
documentation contained in, or delivered to you in conjunction with guide.
Unless otherwise indicated, 3Com registered trademarks are registered in the United
States and may or may not be registered in other countries.
3Com and the 3Com logo are registered trademarks of 3Com Corporation. VCX is a
trademark of 3Com Corporation.
Other brand and product names may be registered trademarks or trademarks of their
respective holders.

CONTENTS
ENTERPRISE MANAGEMENT SUITE GETTING STARTED GUIDE
ABOUT THIS GUIDE
Conventions 13
Related Documentation 14
Your Comments 15
1PRODUCT OVERVIEW
Introduction 17
Object Containers 17
Equipment Folders 18
Logical Views 18
Object Usage 19
Configuration Templates 19
Scheduled Operations 19
EMS Device Classes 20
All Configuration Template Classes 20
All Events 20
All Operation Steps 20
All Stated Managed Objects 20
All Stateless Folders 20
All Static Classes 20
Serial and Parallel Processing 20
Features 21
Benefits 22
EMS Software Components 23
Supported Devices 24
Supported 3Com Data Products 24
Supported 3Com Router Products 26
Supported 3Com Wireless Products 27

4
Supported VCX Products 29
Graphical User Interface Basics 30
Menu Bar 30
Toolbar 31
Left-hand Pane Views 31
Explorer View (default view) 31
List View 32
Logical Views 32
Right-hand Pane Views 32
Properties View (default view) 32
Related View 32
Root Folders 33
Pop-up Menus 34
SNMP Devices 34
Help Options 35
Help Menu 35
Tool Tips 35
Advisor Window 36
Online Help 36
Printing Options 36
EMS Event Processing 37
Event Flow 37
2PRE-INSTALLATION
EMS Software Licenses 41
Network Management Platform Software (Optional) 42
System Requirements 42
Hardware Requirements 42
IBM-Compatible Hardware Requirements 42
Sun Workstation Hardware Requirements 42
IBM i5/OS Hardware Requirements 43
Network Interface Card Requirements 43
Platform and Operating System Requirements 43
Supported Databases 45
Supported Network Management Platforms 46
Platform Related Installation Information 46
Solaris 46

5
File Permissions and EMS 46
Running the EMS Server from Root Accounts 47
Setting User Read-Write Permissions 47
Using Static IP Addresses 47
Using the EMS GUI Client Without a Monitor 47
Windows 48
Using Windows Filenames 48
Linux 48
Resolving Remote Client Login Problems 48
IBM iSeries 48
Running EMS as QSECOFR User 48
Ports Used by EMS 48
TFTP Server Installation and Initial Configuration 49
TFTP for Windows 49
Installing the 3Com TFTP Server for Windows Software 50
Initially Configuring the 3Com TFTP Server for Windows
Software 50
Initially Configuring EMS for the 3Com TFTP Server Software for
Windows 51
TFTP for UNIX and Linux 51
TFTP for IBM i5/OS 52
Server Failover Requirements 52
Hardware Requirements 52
Supported Platforms 53
3INSTALLATION AND INITIAL SETUP
Installing EMS Software Components 56
Installing the EMS Server using the Silent Option 59
Installing the EMS Server using the Console Option 59
Navigating the Enterprise Management Suite Directories 59
Database Configuration 61
Embedded Database 62
Features and Benefits 62
Configuring Database Compaction 63
Limitations 64
Configuring Embedded Databases 64
Maintenance Options 64
External Database 64

6
Features and Benefits 65
Deploying on an EMS Server 66
Deploying on a Dedicated Server 66
Configuring Oracle External Databases 67
Configuring MySQL External Databases 69
Configuring i5 DB2 External Databases 71
Running Multiple External Databases on a Single Database
Server 73
Multiple User Access for External Databases 74
External Database Tools and Options 74
Configuring for Multi-homed Server Support 74
Configuring EMS Servers with a Static IP Address 75
EMS Licensing System 75
Evaluation Mode 75
Extended Evaluation Mode 75
Activating EMS 76
Obtaining an Activation Key 76
Activate Server Command 76
Activation Key Verification 77
EMS Client: Evaluation Mode Visual Indicator 77
Initially Starting the EMS Server 79
Using Windows Shortcut Options 79
Using a Command Prompt 80
Initially Starting the EMS GUI Client 81
Using Windows Shortcut Options 81
Using a Command Prompt 83
Initially Starting the EMS CLI Client 84
4SERVER FAILOVER CONFIGURATION
Introduction to Server Failover 87
How Server Failover Works 87
Server Failover Concepts 88
Remote Server 88
Server Run Modes 89
Active 89
Dormant 89
EMS_FILEHOME 89

7
local_server. properties file 90
Setting Up Server Failover 91
Initial Setup 91
Editing the Properties Files 91
Other local_server.
properties Configurations 93
SNMP Trap Forwarding 93
TFTP Server Directory 93
EMS_FILEHOME 94
Troubleshooting 94
Running in Server Failover Mode 94
Server Startup Messages 94
Active Server Behaviors 96
Client Logins 96
Scheduled Operations 96
Data Collectors 96
Logged-in Users 96
Shutting down the Active Server 96
Losing the Connection to the Active Server 97
Dormant Server Behaviors 97
Connecting to the Dormant server when the Active server is still
running 97
Preventing Clients from Attaching to the Dormant Server 97
How the Failover System Works 98
Server Failover Mechanism 98
Passing Control Back to the Peferred Server 99
5SNMP DEVICE CONFIGURATION
Creating Device Folders 101
Creating Equipment Bays and Racks 102
Discovering Multiple SNMP Devices 103
Discovering Single SNMP Devices 108
Listing Devices by IP Address instead of Hostname 111
Deleting SNMP Devices and Folders 112
Rediscovering an SNMP Device 112
Viewing SNMP Device Identification 113
Configuring the SNMP Version 114
Configuring Read and Write Community Strings 114

8
Common SNMP Device Configuration 115
Exporting and Importing SNMP Devices 115
Importing SNMP Devices from HP OpenView 115
Create Device File 115
Import New Devices 116
Remove Old Devices 116
Reserving and Unreserving Elements 116
Reserving an Element 116
Unreserving an Element 117
Renaming Elements 117
Configuring Equipment Folder Parameters 118
Understanding the Discovery Interface 118
To Discover a Range of SNMP Devices using the Discovery Tab 120
Schedulable GUI Based Device Discovery 120
Transferring Values to/from the Discovery Tab 120
Copy Values from the Discovery Tab 120
Save Values to the Discovery Tab 121
6GUI CLIENT CONFIGURATION
Configuring Environment Settings 125
Configuring the Printer Page Setup 129
Configuring the Display of Non-supported MIB Objects in the EMS
GUI 131
7USER CONFIGURATION
Creating User Folders 133
Creating New Users 134
Deleting a User 135
Assigning a Root View to a User 135
Assigning User Access Rights 136
Removing an Assigned Root View 137
Exporting and Importing Users 137
Exporting Users 137
Importing EMS Users 138
User Passwords 138
Resetting User Passwords 138
Changing User Passwords 139

9
Setting a Login Expiration Date and Time 140
Forcing a Logout 140
From the EMS GUI 140
From the Command Line 140
Broadcasting Messages to Users 141
Sending a Message to One User 141
Sending a Message to Multiple Users 141
Applying RADIUS Authentication to a User 142
Changing a User’s RADIUS Shared Secret 143
Configuring User Access to Device Folders 143
Telnet Script Access Levels 145
Setting Telnet Scripting Access Levels 145
8LOGICAL VIEW CONFIGURATION
Creating a Logical View 147
Deleting a Logical View 148
9NETWORK MANAGEMENT PLATFORM INTEGRATION
CONFIGURATION
About 3Com Integration Kit 149
Installation 150
Launching EMS from a Network Management Platform 152
Setting Up the EMS Launcher 152
Launching EMS from a Network Management Platform 153
Icons 154
Traps 154
MIBs 155
Network Node Manager Integration Architecture 156
General File Location 156
Menu Integration and Application Registration Files 156
Fields File 157
Configuration Files for SysObjectID Recognition 158
Symbol Integration File 159
Icon Files 159
Trap File 160
MIB Files 160
Trap Support 161

10
Forwarding Traps to a Network Management Platform 161
Uncommenting the SNMP.trap.Threads Line 162
Trap Forwarding Based on IP addr Range Setting 162
Event Type Tab 162
IP Address Ranges Tab 163
10 OPERATIONS
Verifying the EMS Serial Number 168
Viewing Software Version and Copyright Information 168
Toggling between the Explorer View and List View 170
Using the List View 170
Toggling between the Properties and Related View 173
Expanding and Collapsing Elements 175
Using the Tree Menu Option 175
Using the Toolbar 175
Using Standard Double-clicking 175
Executing Commands for Multiple Elements 176
Organizing Elements 176
Monitoring the Status of GUI Elements 177
Viewing the Status 177
Using the State Tab 177
Using the State Icon 178
Using the Monitor State Utility 179
Refreshing the Status 180
Using the MIB Browser 181
Starting the MIB Browser 181
Getting and Setting MIB Values 181
Viewing Numeric Values in Alternative Formats 182
Monitoring Numeric Properties 183
Setting the Poll Rate 183
Using EMS to Edit Network Device Properties 184
Editing Simple Properties 185
Editing Tabular Properties 186
Copying and Pasting Values between Elements 188
Locating Information Using the Find Command 190
Creating Inventory Reports 192
Locating Information in MIB Tables Using the Find Button 193

11
Accessing the Web Browser Interface 194
Printing the EMS GUI Explorer Tree 195
Starting and Stopping EMS Software Components 195
Starting the EMS Server 195
Starting the EMS Server as a Daemon 195
Starting the Server as a UNIX Background Process 196
Starting the Server as a Windows Background Process 197
Stopping the EMS Server 198
Starting the EMS GUI Client 198
Stopping the EMS GUI Client 198
Starting the EMS CLI Client 199
Stopping the EMS CLI Client 199
Using the Server Monitor to Monitor EMS Server Performance 199
Monitoring EMS Server Memory 201
Monitoring EMS GUI Memory 202
Displaying Server Console Commands 203
Displaying EMS CLI Client Console Commands 204
Configuring Table Data Loading 204
ACOMMAND LINE INTERFACE REFERENCE
EMS Server Console 207
Using Daemon-specific Server Console Commands 208
EMS CLI Client 209
Dormant Server CLI Commands 210
info Command 211
runMode Command 211
INDEX

12

ABOUT THIS GUIDE
This chapter contains an overview of this guide, lists guide
conventions, related documentation, product compatibility, and
describes how to send us your comments on the user documentation.
This guide describes how to install, start, and initially configure the
Enterprise Management Suite (EMS) to run your system components.
This guide is intended for network administrators with some training
or experience working in a data center using 3Com equipment.
The README file is bundled with the EMS software and provides release
notes and basic installation instructions. If the information in the
README file differs from the information in this guide, follow the
instructions in the README file.
Conventions Table 1 and Tab l e 2 list conventions that are used throughout this guide.
Tab l e 1 Notice Icons
Icon Notice Type Description
Information note Information that describes important features or
instructions
Caution Information that alerts you to potential loss of data or
potential damage to an application, system, or device
Warning Information that alerts you to potential personal injury

14 ABOUT THIS GUIDE
Related
Documentation
These 3Com documents contain additional information about the
Enterprise Management Suite.
The following documents are a part of the Enterprise Management Suite:
■Enterprise Management Suite User Guide
■Enterprise Management Suite Getting Started Guide
Tab l e 2 Text Conventions
Convention Description
Screen displays This typeface represents information as it appears on the
screen.
Syntax The word “syntax” means that you must evaluate the syntax
provided and then supply the appropriate values for the
placeholders that appear in angle brackets. Example:
To enable RIPIP, use the following syntax:
SETDefault !<port> -RIPIP CONTrol =
Listen
In this example, you must supply a port number for <port>.
Commands The word “command” means that you must enter the
command exactly as shown and then press Return or Enter.
Commands appear in bold. Example:
To remove the IP address, enter the following command:
SETDefault !0 -IP NETaddr = 0.0.0.0
The words “enter”
and “type”
When you see the word “enter” in this guide, you must type
something, and then press Return or Enter. Do not press
Return or Enter when an instruction simply says “type.”
Keyboard key names If you must press two or more keys simultaneously, the key
names are linked with a plus sign (+). Example:
Press Ctrl+Alt+Del
Words in italics Italics are used to:
■Emphasize a point.
■Denote a new term at the place where it is defined in the
text.
■Identify menu names, menu commands, and software
button names. Examples:
From the Help menu, select Contents.
Click OK.

Your Comments 15
Your Comments Your suggestions are important to us because we want to make our
documentation more useful to you.
Please send e-mail comments about this guide or any of the 3Com Voice
Products documentation and Help systems to:
[e-mail]
Please include the following information with your comments:
■Document title
■Document part number (found on the front page)
■Page number
■Your name and organization (optional)
Example:
Enterprise Management Suite Getting Started Guide
Part Number 900-0282-01 Rev AA
Page 25
Please address all questions regarding the 3Com software to your
authorized 3Com representative.

16 ABOUT THIS GUIDE

1PRODUCT OVERVIEW
The Enterprise Management Suite (EMS) provides a flexible
management solution with comprehensive integration abilities and
advanced value-added features to provide industry-leading
management capabilities.
This chapter contains the following topics:
■Introduction
■Features
■Benefits
■EMS Software Components
■Supported Devices
■Graphical User Interface Basics
■Help Options
■Printing Options
■EMS Event Processing
Introduction The 3Com Enterprise Management Suite addresses the complexity of
network management by presenting a truly object-oriented view of all
aspects of its system. In EMS everything is considered an object, which
includes devices, folders, logical views, users, scheduled operations, and
configuration templates. This object-based approach is fundamental to
giving you the flexibility to customize EMS to your specific needs.
Object Containers Objects are stored in different types of containers (or folders) in EMS.
Folders are used for objects such as users, scheduled events, and
configuration templates. Equipment and logical view folders are also a
type of container, but they have a recommended purpose, which is
described in detail in the next paragraph.

18 CHAPTER 1: PRODUCT OVERVIEW
Equipment Folders
Equipment folders provide a basic container for your devices. They let you
store your devices in logical, physical groupings according to your choice
of physical property. For example, you could create folders for subnets,
sites, machine rooms, equipment bays, or even racks. Equipment folders
can hold any type of EMS object, however 3Com recommends you limit
equipment folders to only contain devices.
Logical Views
You can create as many logical views as you need to group your EMS
objects in a way that makes sense for you. The important fact to bear in
mind is that the logical views can contain any object. For example, you
could create a logical view that groups a common set of devices together
with their relevant configuration templates and scheduled operations.
Logical views can contain objects that are links to objects elsewhere in
the EMS Explorer Tree. For example, when you discover or add a new
device to an equipment folder, EMS creates a corresponding
system-defined logical view that groups the new devices according to
device type. The devices inside the device type folders are actually links
to the original object in the equipment folder. If you reserve the object
in the equipment folder, the link is reserved at the same time.
Logical views can be used in conjunction with the Root View for a
user. A user can be limited to only seeing the contents of the logical
view assigned as their root view. Combining this with the other
capabilities mentioned in this section, the EMS administrator can
create logical views for each user that contain not only the devices,
but also any pre-configured scheduled operations, data collections,
configuration templates or any other EMS objects (or entire folders)
the user may need.
As a further level of control, the EMS data product device support
includes folders for Administration, Security, Configuration,
Performance, and Fault. Using logical views, you can limit users such
that they can only access the Performance folders (but not the
Administration folder) for example.

Introduction 19
Object Usage Objects can be used in many different ways (as described in the rest of
this guide), but there are two general-purpose object usage tools that put
a number of powerful features at your disposal.
Configuration Templates
When we refer to the attributes of an object, we are specifically referring
to the contents of the right-hand pane in the EMS window. Attributes
can be edited manually or configured in bulk using configuration
templates.
Initially, you might think of configuration templates as only acting on
device objects, but in fact, any object's attributes can be modified. For
example, you can set up a configuration template to change user settings
such as Expiration Date for the user's login or to update a department
setting.
Once created, a configuration template is itself an object, and while
you cannot change any attributes for a configuration template you
can use the template like any object. For example, you can move it to
a more appropriate container or add a link (using a Logical View) to it
instead, if other users need to access the same template.
Scheduled Operations
The operations of an object are specifically the right-click menus available
for that object. The scheduler lets you run any object's operations at a
defined time or over a repeated interval you specify.
One example is to run device-based operations at a preset time by
configuring a scheduled operation to run automatically. For example, you
can apply a configuration template as part of a scheduled operation or
log off certain EMS users at a pre-determined time.
Once created, a scheduled operation is an object and can be moved
around the EMS system — placing it in a logical view for example.

20 CHAPTER 1: PRODUCT OVERVIEW
EMS Device Classes This section defines EMS device classes, which you need to understand in
order to configure scheduled operations, data collectors, and the Target
Filter Selection dialog.
All Configuration Template Classes
This consists of classes that define the configuration template managed
object itself, the class that the managed object configures, and a class
that defines the attribute data being configured.
All Events
This defines classes for all Events within the system. This includes events
used when operations are executed, SNMP traps, and user-based access
to the system.
All Operation Steps
These classes are used to specify the operations steps that may be
performed in a scheduled operation.
All Stated Managed Objects
Stated Managed Objects are Managed Objects that have an operational
state. The state is represented by a colored square in the tree. The
following colors represent the possible states: Green (enabled), Yellow
(degraded), Red (disabled), and Magenta if EMS cannot accurately
determine the state. Stated Managed Objects includes Equipment, SNMP
Managed devices, and users.
All Stateless Folders
Stateless folders are Managed Objects that act as containers for other
Managed Objects. Stateless folders do not have an operational state
associated with them.
All Static Classes
Static classes have no instances in EMS. These are typically used to define
common functions across Managed Objects.
Serial and Parallel
Processing
EMS lets you specify whether to operate on objects in serial (one at a
time) or in parallel (all at once). You can have one type of processing
thread per selection. For instance, when you single select a folder of
objects, the folder contents are processed in a series. With serial
processing, EMS allocates one processing thread and works on the
objects one at a time. When you multi-select the folder contents, the