Download  Print this page

3Com 3CR15600 - Enterprise Management Suite Getting Started Manual

Getting started guide.
Hide thumbs

Advertisement

E
NTERPRISE
G
ETTING
Enterprise Management Suite
Release 2.41
Part Number 10015165 Rev.2
Published September 2007
http://www.3com.com/
M
ANAGEMENT
S
TARTED
S
G
UIDE
UITE

Advertisement

   Related Manuals for 3Com 3CR15600 - Enterprise Management Suite

   Summary of Contents for 3Com 3CR15600 - Enterprise Management Suite

  • Page 1 NTERPRISE ANAGEMENT UITE ETTING TARTED UIDE Enterprise Management Suite Release 2.41 Part Number 10015165 Rev.2 Published September 2007 http://www.3com.com/...
  • Page 2 3Com Corporation Copyright © 2001 - 2007, 3Com Corporation. All rights reserved. No part of this 350 Campus Drive 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 Marlborough, MA permission from 3Com Corporation.
  • Page 3: Table Of Contents

    All Configuration Template Classes All Events All Operation Steps All Stated Managed Objects All Stateless Folders All Static Classes Serial and Parallel Processing Features Benefits EMS Software Components Supported Devices Supported 3Com Data Products Supported 3Com Router Products Supported 3Com Wireless Products...
  • Page 4 Supported VCX Products Graphical User Interface Basics Menu Bar Toolbar Left-hand Pane Views Explorer View (default view) List View Logical Views Right-hand Pane Views Properties View (default view) Related View Root Folders Pop-up Menus SNMP Devices Help Options Help Menu Tool Tips Advisor Window Online Help...
  • Page 5 TFTP for Windows Installing the 3Com TFTP Server for Windows Software Initially Configuring the 3Com TFTP Server for Windows Software Initially Configuring EMS for the 3Com TFTP Server Software for Windows TFTP for UNIX and Linux TFTP for IBM i5/OS...
  • Page 6 Features and Benefits Deploying on an EMS Server Deploying on a Dedicated Server Configuring Oracle External Databases Configuring MySQL External Databases Configuring i5 DB2 External Databases Running Multiple External Databases on a Single Database Server Multiple User Access for External Databases External Database Tools and Options Configuring for Multi-homed Server Support Configuring EMS Servers with a Static IP Address...
  • Page 7 local_server. properties file Setting Up Server Failover Initial Setup Editing the Properties Files Other local_server. properties Configurations SNMP Trap Forwarding TFTP Server Directory EMS_FILEHOME Troubleshooting Running in Server Failover Mode Server Startup Messages Active Server Behaviors Client Logins Scheduled Operations Data Collectors Logged-in Users Shutting down the Active Server...
  • Page 8 Common SNMP Device Configuration Exporting and Importing SNMP Devices Importing SNMP Devices from HP OpenView Create Device File Import New Devices Remove Old Devices Reserving and Unreserving Elements Reserving an Element Unreserving an Element Renaming Elements Configuring Equipment Folder Parameters Understanding the Discovery Interface To Discover a Range of SNMP Devices using the Discovery Tab Schedulable GUI Based Device Discovery...
  • Page 9 Creating a Logical View Deleting a Logical View ETWORK ANAGEMENT LATFORM NTEGRATION ONFIGURATION About 3Com Integration Kit Installation Launching EMS from a Network Management Platform Setting Up the EMS Launcher Launching EMS from a Network Management Platform Icons Traps MIBs...
  • Page 10 Forwarding Traps to a Network Management Platform Uncommenting the SNMP.trap.Threads Line Trap Forwarding Based on IP addr Range Setting Event Type Tab IP Address Ranges Tab PERATIONS Verifying the EMS Serial Number Viewing Software Version and Copyright Information Toggling between the Explorer View and List View Using the List View Toggling between the Properties and Related View Expanding and Collapsing Elements...
  • Page 11 Accessing the Web Browser Interface Printing the EMS GUI Explorer Tree Starting and Stopping EMS Software Components Starting the EMS Server Starting the EMS Server as a Daemon Starting the Server as a UNIX Background Process Starting the Server as a Windows Background Process Stopping the EMS Server Starting the EMS GUI Client Stopping the EMS GUI Client...
  • Page 13: Conventions

    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.
  • Page 14: Related Documentation

    Examples: From the Help menu, select Contents. Click OK. Related These 3Com documents contain additional information about the Documentation Enterprise Management Suite. The following documents are a part of the Enterprise Management Suite: Enterprise Management Suite User Guide ■...
  • Page 15: Your Comments

    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: voice_techcomm_comments@3com.com Please include the following information with your comments: Document title ■...
  • Page 16 BOUT UIDE...
  • Page 17: Product Overview

    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.
  • Page 18: Equipment Folders

    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.
  • Page 19: Object Usage

    Introduction 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.
  • Page 20: Ems Device Classes

    1: P HAPTER RODUCT VERVIEW 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.
  • Page 21: Features

    ■ (GUI) and command line interface (CLI) clients with remote browser access to key functions Java-based platform independent architecture ■ Consistent, common interfaces across 3Com applications and ■ components Open solutions environment ■ Hierarchical organization of discovered devices into several different ■...
  • Page 22: Benefits

    ■ scripting APIs, which provides a wide variety of options for developing custom device management extensions and clients. If you need more information about scripting, please contact your 3Com customer representative. Flexible Client/Server Architecture — Client (both GUI and CLI) ■...
  • Page 23: Ems Software Components

    EMS Software Components EMS Software EMS is a client-server management solution that provides a Java-based Components GUI for managing individual SNMP devices. EMS comes bundled with three main software applications for you to use: Server ■ Runs as a Java application ■...
  • Page 24: Supported Devices

    EMS does not provide any explicit XRN support. Any XRN devices are shown with the text “(XRN)” next to the device name. For example. Switch 4050 (XRN). Supported 3Com This section lists all of the 3Com Data devices supported by EMS. Data Products Table 3 Supported 3Com Data Products Device Family...
  • Page 25 Supported Devices Table 3 Supported 3Com Data Products (continued) Device Family Individual Device SuperStack 3 Switch 38xx SuperStack 3 Switch 3812 SuperStack 3 Switch 3824 SuperStack 3 Switch 3870 SuperStack 3 Switch 3848 SuperStack 3 Switch 40x0 SuperStack 3 Switch 4050...
  • Page 26: Supported 3com Router Products

    Managed Switch 9 Managed Switch 9 Managed Switch 9 FX Switch 2xxx Switch 2226-Plus Switch 2250-Plus Switch 2426-PWR-Plus 3Com OfficeConnect Managed Gigabit PoE Switch Supported 3Com This section lists all of the 3Com Router devices supported by EMS. Router Products...
  • Page 27: Supported 3com Wireless Products

    Router 5680 Router 5682 Router 6000 Router 6040 Router 6080 Supported 3Com This section lists of all the 3Com Wireless LAN and Bridge devices Wireless Products supported by EMS. EMS does not support any of the 3Com OfficeConnect Wireless Access Points.
  • Page 28 Table 6 Supported 3Com Bridge Products Device Family Individual Device Wireless LAN Building-to-Building Bridge 11 a/b/g Wireless LAN Bridge Outdoor Building to Building Bridge Table 7 Supported 3Com Wireless Switch Products Device Family Individual Device Wireless Switch WX1200 Wireless Switch WX2200 Wireless Switch WX4400...
  • Page 29: Supported Vcx Products

    Supported Devices Supported VCX This section lists all of the VCX devices supported by EMS. Products Table 9 Supported VCX Products Product Family System Release Individual Components VCX IP Telephony Solution Accounting Server Authentication Server Directory Server SIP Phone Downloader Call Processor Accounting Server Authentication Server...
  • Page 30: Graphical User Interface Basics

    1: P HAPTER RODUCT VERVIEW Graphical User The EMS GUI provides a simple and intuitive device management Interface Basics environment. As shown in Figure 1, all managed devices, event logs, and users are organized in an explorer tree (Explorer view) in the left-hand pane of the EMS GUI main window.
  • Page 31: Toolbar

    Graphical User Interface Basics Figure 2 Menu Bar Commands View Help Tree Menu Menu Menu Tools Configuration File Menu Menu Menu Toolbar The toolbar provides quick access to specific commands and features available for the EMS GUI. See Figure 3 Figure 3 Toolbar Commands paste SNMP...
  • Page 32: List View

    1: P HAPTER RODUCT VERVIEW List View The List view provides an alternative way to view and manage SNMP devices. For more information, see Toggling between the Explorer View and List View page 170. The List view allows you to: Manage properties ■...
  • Page 33: Root Folders

    Graphical User Interface Basics Root Folders The EMS GUI main window contains a number of default root folders, these are sub-elements of the root node (the first node in the explorer tree; typically, it is the hostname of the workstation where your EMS server resides).
  • Page 34: Pop-up Menus

    101. EMS labels each SNMP device in the left-hand pane of the EMS GUI main window with the IP address of the device. If the discovered device is a 3Com product, a 3Com icon appears in front of the IP address.
  • Page 35: Help Options

    Help Options Help Options EMS has four help options available for you to use: the Help menu, Tool Tips, the Advisor window, and Online help. Help Menu The Help menu on the EMS Toolbar allows access to the following information: About —...
  • Page 36: Advisor Window

    RODUCT VERVIEW Advisor Window When you start the EMS GUI, the 3Com EMS Advisor window opens. The Advisor window displays status information on a selected device, as well as MIB definitions on a selected property. To open the EMS Advisor window, use one of the following methods:...
  • Page 37: Ems Event Processing

    EMS Event Processing EMS Event Generally, an event is an action or occurrence detected by a software Processing program. Specifically, EMS events are messages that report internal activity and communication between the EMS server and each client and managed SNMP device. For example, when a user launches the EMS GUI, an event is logged and saved on the EMS server in the security log and in the daily audit log.
  • Page 38 1: P HAPTER RODUCT VERVIEW Figure 6 Event Flow SNMP SNMP Trap SNMP Trap device Other syslog syslog message SNMP Trap Management device Plaftorms(s) EMS Event SNMP Trap EMS Server Process EMS Event Daily Event Manager Audit Event Action Script Event Table Any SNMP device managed by EMS (A) can send SNMP traps to EMS.
  • Page 39 EMS Event Processing The Event Manager (C) uses the Log Filter (F) to determine if the specific event should be written to the daily audit log (G) and stored in the Event Table (H) for the database. The Event Manager (C) independently launches the Event Action Script (I) if one has been supplied.
  • Page 40 1: P HAPTER RODUCT VERVIEW...
  • Page 41: Pre -installation

    TFTP Server Installation and Initial Configuration ■ Server Failover Requirements ■ EMS Software 3Com provides four types of EMS licenses to meet your network’s needs. Licenses The following EMS Software CDs are available from 3Com: Table 10 EMS License Types 3C Number 3Com EMS Version Maximum No.
  • Page 42: Network Management Platform Software (optional)

    2: P HAPTER NSTALLATION Network 3Com provides an integration kit for HP OpenView Network Node Management Manager. This kit installs MIB files, icons, SNMP trap decodes and Platform Software database customizations to allow you to manage your devices effectively (Optional) from the network management platform.
  • Page 43: Ibm I5/os Hardware Requirements

    Ultra 10 with CD-ROM Ultra 60 or better with CD-ROM 1024MB 1GB or more Free Disk Space 300MB 3Com recommends 500MB of space to store back-up images, agent images, templates, and for the chosen database. Network Type TCP/IP TCP/IP IBM i5/OS Hardware Requirements...
  • Page 44 Windows 2003 Server ■ Windows 2000 Professional SP4 ■ Windows XP Professional SP1a and SP2 ■ 3Com supports the following Windows operating systems for the EMS client: Windows 2000 Server ■ Windows 2000 Professional SP4 ■ Windows XP Professional SP1a ■...
  • Page 45: Supported Databases

    3Com recommends that you use one of the databases listed in Table 15 for moderate to large scale deployments. You must install the correct JDBC drivers to attach to the chosen database because 3Com does not provide them. Table 15 Supported Databases...
  • Page 46: Supported Network Management Platforms

    Solaris 9. Tivoli NetView NetView version 7.1.3 ■ Supported on Solaris 8, and Solaris 9. For information on the 3Com Network Management Platform Integration Kits, see Network Management Platform Software (Optional) page 42 Platform Related This section provides installation information related to these specific...
  • Page 47: Running The Ems Server From Root Accounts

    Platform Related Installation Information This is because the other users do not have access to the EMS database or log directories. Workaround: The recommended practice is to install and run the EMS server using the root user. If this is not possible, you can install EMS as a non root user but, you will have to recursively change the group permissions to the EMS directory and its sub dirs to grant write access to the files and directories.
  • Page 48: Windows

    This section provides additional information and issues related to Linux environments that you will need to review before installing and using the EMS server and clients in your network. Linux is not a 3Com supported operating system. Resolving Remote Client Login Problems...
  • Page 49: Tftp Server Installation And Initial Configuration

    Update, or Golden Configuration operation using the EMS Server. Configuration 3Com recommends that the TFTP Server software be installed on the same server running the EMS Server because EMS points to the TFTP Server upload and download folders. The Windows 3Com TFTP server is included on the EMS CD.
  • Page 50: Installing The 3com Tftp Server For Windows Software

    Initially Configuring the 3Com TFTP Server for Windows Software To initially configure the TFTP Server software: 1 Start the 3Com TFTP Server software. The default location is Start | All Programs | 3Com TFTP Server | 3Com TFTP Server. The 3Com TFTP Server application appears.
  • Page 51: Initially Configuring Ems For The 3com Tftp Server Software For Windows

    3 Locate the tftp SERVER heading. 4 From the tftpServer.tftpbootDirectory= entry, type the same path that was entered in the Upload / download directory field for the 3Com TFTP Server. In Windows, you must use double backslashes as shown below.
  • Page 52: Tftp For Ibm I5/os

    You therefore need to download and install the IBM patch: PTF #SI27230. This PTF allows EMS to support all 3Com data products. For more information about configuring a TFTP server for IBM i5/OS please refer to the URL below: http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rza...
  • Page 53: Supported Platforms

    Server Failover Requirements Physical clustering of machines may be required for a clustered ■ database installation. Supported Platforms Both EMS servers must be running the same operating system. The operating system version should also be the same on both machines. This section lists the supported platforms for EMS version 2.3 and therefore those required by Server Failover.
  • Page 54 2: P HAPTER NSTALLATION...
  • Page 55: Installation And Initial Setup

    NSTALLATION AND NITIAL ETUP This chapter explains how to install and run the EMS server software and client software. EMS is distributed as an executable Java Archive (JAR) file that can be installed on any platform. This chapter provides information necessary for the first-time setup of an EMS server and EMS GUI and CLI clients using a single server.
  • Page 56: Installing Ems Software Components

    EMS Software Licenses page 41 for the available EMS software. The CD contains the following files: 3ts01_04.exe is the 3Com TFTP Server for Windows installation file. ■ EMS_gs.pdf is a PDF version of the EMS Getting Started Guide. It ■...
  • Page 57 If installing on a Windows platform and if no previous version has been installed, the default directory chosen is <System Drive>\Program Files\3Com\EMS. If installing on either a UNIX or Linux platform, the default directory chosen is /opt/3Com/EMS. If you choose a different installation directory...
  • Page 58 3: I HAPTER NSTALLATION AND NITIAL ETUP from the default, symbolic links are automatically created from the default directory to the chosen directory. 9 Once you have selected the desired directory, click Next. Three installation options appear. See Figure 10 Table Figure 10 Installation Options for Enterprise Management Suite Table 19 Enterprise Management Suite Installation Options...
  • Page 59: Installing The Ems Server Using The Silent Option

    -jar EMSSetup.jar -console The following screen displays: ------------------------------------------------------------------ 3Com Enterprise Management Suite v2.40 This will install 3Com Enterprise Management Suite v2.40 on your computer. To continue, choose Next. 3Com Enterprise Management Suite v2.40 Copyright (c) 2002-2006 www.3com.com Press 1 for Next, 3 to Cancel or 4 to Redisplay [1] Navigate the text based wizard via the numeric keys.
  • Page 60 Files and directories not listed in Table 20 are for internal use only and must not be modified or deleted unless directed to do so by a 3Com customer service representative. In HA Mode these directories are re-created by the EMS server on its first run, according to the EMSFILEHOME setting in the local_server.properties...
  • Page 61: Database Configuration

    Files not listed in Table 21 are for internal use only and must not be modified or deleted unless directed to do so by a 3Com customer service representative. The root folder may contain Release Notes, Readme files, or other forms of documentation that contain last-minute information that could not be included in this documentation.
  • Page 62: Embedded Database

    3: I HAPTER NSTALLATION AND NITIAL ETUP Embedded Database By default, EMS comes bundled with an internal, embedded database. EMS uses the open source InstantDB, created by Enhydra, as the default embedded database. Features and Benefits Using the internal, embedded database provides the following features and benefits: The embedded database is pre-configured and has very little ■...
  • Page 63: Configuring Database Compaction

    Java Virtual Machine (JVM Figure 11 Embedded Databases Configuring Database Compaction When using InstantDB 3Com recommends enabling the compactOnStartup feature within the server.properties file. This compresses free space on the DB and reduces its size on the disk. To configure DB Compression: 1 Using a standard text editor, open the server.properties file.
  • Page 64: Limitations

    EMS server command prompt. Use these commands to compact existing databases and to export and import databases. For more information about these commands, see “Command Line Interface Reference” page 207. External Database For larger networks, 3Com allows you to use an external database from an approved vendor.
  • Page 65: Features And Benefits

    Database Configuration EMS supports the following external databases: Oracle ■ MySQL ■ IBM DB2 database ■ All other external databases listed in the server.properties file (MS/Access and SQL Server) are not supported for this release. When using Server Failover, consider setting up your Oracle or MySQL server in a resilient configuration to provide high resilience for your overall network management system.
  • Page 66: Deploying On An Ems Server

    3: I HAPTER NSTALLATION AND NITIAL ETUP Figure 13 shows the location of an external database in relationship to ™ the Java Virtual Machine (JVM Figure 13 External Databases Deploying on an EMS Server If you deploy an external database on the EMS server itself, use the following minimum hardware requirements, which differ from the original requirements found in Table...
  • Page 67: Configuring Oracle External Databases

    Database Configuration If you deploy an external database on a dedicated database server, increased latency in the fulfillment of database requests may occur as a result of network overhead. Configuring Oracle External Databases EMS uses JDBC database connection and interface drivers to communicate with external databases.
  • Page 68 3: I HAPTER NSTALLATION AND NITIAL ETUP ##### Instant DB ###### #DBDriver=org.enhydra.instantdb.jdbc.idbDriver #DBURL=jdbc:idb:db/fdserver.prp #DBLong=LONG #DBBLOB=BINARY #DBEmbeddedQuote=\\' #DBEmbeddedBackslash=\\\\ #DBFile=db 6 To enable the external database, from the Oracle Server section of the server.properties file, uncomment each line by removing the pound signs (#) for each variable and configure according to your customized needs: #### Oracle Server ##### DBDriver=oracle.jdbc.driver.OracleDriver...
  • Page 69: Configuring Mysql External Databases

    Database Configuration Table 22 Oracle Server Section of the server.properties File (continued) Field Description DBEmbeddedQuote The escape sequence for an embedded single quote character. NOTE: \\ results in a single backslash character. DBFile The specific location of the EMS database file/directory that contains all data.
  • Page 70 3: I HAPTER NSTALLATION AND NITIAL ETUP Do not configure the external database tables and schemas. When EMS detects a blank database, EMS will automatically create all of the necessary tables and configure them according to your customized needs. 5 Create user privileges for the new user account. If a database user has not been created, MySQL creates a new user for you when entering the command in the following example: GRANT ALL PRIVILEGES ON <database_name>.* to...
  • Page 71: Configuring I5 Db2 External Databases

    Database Configuration Table 23 MySQL DB Section of the server.properties File (continued) Field Description DBEmbeddedQuote The escape sequence for an embedded single quote character. NOTE: \\ results in a single backslash character. DBFile The specific location of the EMS database file/directory that contains all data.
  • Page 72 3: I HAPTER NSTALLATION AND NITIAL ETUP 4 As the default database used is Instant DB, you need to first comment each line of the Instant DB section by adding a pound sign (#) before each variable of the server.properties file. For example: ##### Instant DB ###### #DBDriver=org.enhydra.instantdb.jdbc.idbDriver...
  • Page 73: Running Multiple External Databases On A Single Database Server

    Database Configuration Table 24 IBM DB2 DB Section of the server.properties File (continued) Field Description DBFile The specific location of the EMS database file/directory that contains all data. This is used to compute the database size. NOTE: If you deploy the database on a separate server, you cannot use this option.
  • Page 74: Multiple User Access For External Databases

    External Database Tools and Options If you are using external databases, 3Com does not recommend using the maintenance tools and options bundled with EMS. These options are limited and may not prove to be useful. Instead, use the database tools and options bundled with your external database.
  • Page 75: Configuring Ems Servers With A Static Ip Address

    Configuring EMS Servers with a Static IP Address Configuring EMS It is important that you run the EMS server on a workstation with a static Servers with a IP address. Remote EMS clients might be unable to connect consistently Static IP Address to an EMS server running on a system configured to use the Dynamic Host Configuration Protocol (DHCP).
  • Page 76: Activating Ems

    -activate <activation key> Activating EMS Obtaining an Activation Key The activation key is obtained from the 3Com website http://esupport.3com.com. You will need the EMS serial number (from EMS server), and the license key (from the CD) to obtain the activation key.
  • Page 77: Activation Key Verification

    (E) The activation key entered is invalid. Please contact 3Com software vendor and obtain the correct activation key. Following the failed activation key verification the EMS server will revert back to evaluation mode. If the 60-day trial period has expired...
  • Page 78 3: I HAPTER NSTALLATION AND NITIAL ETUP Figure 14 Evaluation Mode Visual Indicator Once the evaluation period has expired the EMS client will be logged out and the following screen as shown in is displayed. Figure 15 Figure 15 Evaluation Period Expired Visual Indicator Once you click OK the EMS Client GUI is dismissed.
  • Page 79: Initially Starting The Ems Server

    Initially Starting the EMS Server Initially Starting the EMS uses a client-server deployment model. You must start the EMS EMS Server server before starting the EMS GUI or CLI clients. If you are setting up a Server Failover EMS system, you should now refer Chapter 4“Server Failover Configuration”...
  • Page 80: Using A Command Prompt

    <name>). -compact Compact database on start-up. -activate Provides EMS with an activation key obtained from the 3Com web site. -Dcache.python=no Do not cache python scripts (compile each time invoked). -Dcache.java=no Do not cache Java methods (reload each time invoked).
  • Page 81: Initially Starting The Ems Gui Client

    Initially Starting the EMS GUI Client To access the server console commands available, see “Displaying Server Console Commands” in the “Enterprise Management Server Administration Guide” and “Command Line Interface Reference” page 207. Initially Starting the The EMS GUI client is independent of the EMS server. Therefore, the EMS GUI Client procedures in this section assume that the EMS server is running.
  • Page 82 3: I HAPTER NSTALLATION AND NITIAL ETUP Figure 18 Login Dialog Box 2 Minimize the EMS GUI command prompt window. 3 In the Login dialog box, type a valid User ID, Password, and Server IP address/host name. If this is the first time running an EMS GUI client, type the User ID Administrator.
  • Page 83: Using A Command Prompt

    Initially Starting the EMS GUI Client Figure 19 EMS GUI Main Window 5 If this is the first time you have started the EMS GUI client, see “SNMP Device Configuration” page 101 for information on creating folders and discovering devices. For additional information on users, see “User Configuration”...
  • Page 84: Initially Starting The Ems Cli Client

    3: I HAPTER NSTALLATION AND NITIAL ETUP Table 26 GUI Login Optional Parameters (continued) Parameter Description Default -P<password> where <password> is the valid Blank password for this user ID. -S<servername> where <servername> is the localhost hostname/ipaddress of the EMS server. Enter localhost if you are running the EMS GUI client on the same workstation as the EMS server.
  • Page 85 Initially Starting the EMS CLI Client 3 From the folder containing the runCLIClient executable file, enter the following command and optional parameters (See Table 27): runCLIClient [parameters] Table 27 CLI Client Startup Optional Parameters Parameter Usage Default @<scriptname.py> where <scriptname.py> is the A python script is not name of the python script to executed.
  • Page 86 3: I HAPTER NSTALLATION AND NITIAL ETUP For more information on using the CLI client to create customized scripts, contact your 3Com customer service representative.
  • Page 87: Server Failover Configuration

    ERVER AILOVER ONFIGURATION This chapter explains how Server Failover works and how to set up and configure two EMS servers to operate in Server Failover mode. Before you begin configuring your two servers to operate in Server Failover mode you need to refer to the instructions in “Installation and Initial Setup”...
  • Page 88: Server Failover Concepts

    4: S HAPTER ERVER AILOVER ONFIGURATION directory” using which the EMS server locates its files and EMS_FILEHOME directories. shows how Server Failover works using the server-to-server Figure 20 connection and the shared file system and database. Figure 20 How Server Failover Works Server-server notification Active Dormant...
  • Page 89: Server Run Modes

    ###### EMS Files Location ####### ##Specify a base directory from which the EMS server should locate its files #EMS_FILESHOME=\\\\149.112.120.120\\Program Files\\3Com\\EMS # Specifying a local directory on a windows machine: #EMS_FILEHOME=G:\\ems_file_home\\ property is used by the EMS server when locating...
  • Page 90: Local_server. Properties File

    4: S HAPTER ERVER AILOVER ONFIGURATION local_server. file contains the settings for the EMS local_server.properties properties file Server Failover, as shown below. ############## Remote Server For Server Failover ############# # This server identifies the remote server which forms part of the Server Failover system.
  • Page 91: Setting Up Server Failover

    For example, suppose the file is server.properties shared between two servers and contains the following setting for the tftpboot directory: tftpServer.tftpbootDirectory=c:\\Program Files\\3Com\\TFTP Server\\tftpboot However, if one of the EMS server’s TFTP directory is c:\tftpboot, you can add the following line to the file to local_server.properties...
  • Page 92 4: S HAPTER ERVER AILOVER ONFIGURATION Active entry: local_server.properties Remote_Server=149.112.120.121 Dormant entry: local_server.properties Remote_Server=149.112.120.122 2 Setting Preferred_Server Properties Edit the property of the Preferred_Server local_server.properties on each server to specify which server in the Server Failover system you would prefer to be the Active server on startup. It does this by listening for the remote server connection early in its startup sequence, thereby forcing a remote server (started at approximately the same time) into Dormant mode.
  • Page 93: Other Local_server

    Setting Up Server Failover Where is the current retry and is the total number or retries. <x> <y> The default value for the retry and timeout settings if they are not configured by the user are shown below. ############# Retry Count for Server Failover ################ # This specifies the number of attempts made to connect to the remote server # once the count reaches the Remote_Server_Retries value it...
  • Page 94: Ems_filehome

    4: S HAPTER ERVER AILOVER ONFIGURATION EMS_FILEHOME should be treated as a server-specific setting only. Given EMS_FILEHOME the different ways that two computers can attach to a shared disk (using different UNIX mount points or mapping different drive letters in Windows), it is not desirable to share this setting.
  • Page 95 Running in Server Failover Mode Start the EMS server on the second machine. Assuming it can open a connection to your Active server this EMS server assumes it is the Dormant server and displays the message: ------------- DORMANT SERVER MODE --------------- --- EMS Clients cannot connect to this server --- ------------------------------------------------ These messages indicate Server Failover is running correctly.
  • Page 96: Active Server Behaviors

    4: S HAPTER ERVER AILOVER ONFIGURATION status maintains the EMS state and network connection state for each EMS server. Table 28 explains the Server Failover table fields. Table 28 Server Failover table fields Attribute Description ServerName IP Address of EMS Server part of Server Failover setup EMSState EMS Server states: Active / Dormant/ Unknown NetworkState...
  • Page 97: Losing The Connection To The Active Server

    Running in Server Failover Mode Administrator (Administrator) at 02/24/2006 11:06:20 IP=152.67.109.201 Port=4757 The forced quit (quit /f) command can still be used if required. Losing the Connection to the Active Server When you lose connection with the server the GUI client gives you the option of switching over to a different server.
  • Page 98: How The Failover System Works

    4: S HAPTER ERVER AILOVER ONFIGURATION if it is trying to re-establish a connection to the Active Server, it will ■ short-out the failover retry and timeout mechanism, make itself the Active Server and let the client connect. if it still has a connection to the Active Server, it refuses to let the client ■...
  • Page 99: Passing Control Back To The Peferred Server

    Running in Server Failover Mode Passing Control Back command is used to pass control back to the preferred runMode to the Peferred server. Server 1 Enter at the Server CLI prompt. The server checks for runMode dormant logged on users and running jobs. A server cannot enter Dormant mode if there are logged in users or running jobs.
  • Page 100 4: S HAPTER ERVER AILOVER ONFIGURATION...
  • Page 101: Snmp Device Configuration

    SNMP D EVICE ONFIGURATION Use EMS to create SNMP device folders and discover SNMP devices in your existing network. This section does not discuss how to configure SNMP devices currently discovered in your network (for example, configuring VLANs or media processing). To configure SNMP devices according to your customized needs, see the related documentation for that specific device type.
  • Page 102: Creating Equipment Bays And Racks

    5: SNMP D HAPTER EVICE ONFIGURATION 3 From the pop-up menu, select New and then select Equipment Folder. The New dialog box appears. 4 Type a label and click OK. The device folder you just created appears as a sub-folder under the Equipment root folder.
  • Page 103: Discovering Multiple Snmp Devices

    Discovering Multiple SNMP Devices 3 Right-click the sub-folder. A pop-up menu appears. 4 From the pop-up menu, select New and then select either Equipment Bay or Equipment Rack. The New dialog box appears. 5 Type a label and click OK. The bay or rack appears under the equipment sub-folder you created earlier.
  • Page 104 This parameter is used only during IP range discovery. If you select this parameter (recommended), EMS will automatically skip over network and broadcast addresses based on the subnet mask. NOTE: 3Com recommends making sure this option is selected. Subnet Mask The subnet mask for this SNMP device.
  • Page 105 Discovering Multiple SNMP Devices Table 29 Discovery Parameters (continued) Parameter Description Read Community The SNMP Read Community string for access to the devices. This should match the Read Community string of the devices to be discovered. Write Community The SNMP Write Community string. This should match the Write Community string of the devices to be discovered.
  • Page 106 5: SNMP D HAPTER EVICE ONFIGURATION 5 In the Discovery dialog box, enter the appropriate SNMPv3 parameters. Table Table 30 Additional Discovery Parameters for SNMPv3 with No Authentication Parameters Description Context Name For SNMPv3, leave this field blank. Contact Engine ID For SNMPv3, enter #.
  • Page 107 Table 31 Additional Parameters for SNMPv3, Authentication and No Encryption Parameters Description User Name Enter the user name. The default is manager for most 3Com SNMP devices. Password Enter the password. The default is manager for most 3Com SNMP devices. Privacy/Encryption From the drop-down list, select none.
  • Page 108: Discovering Single Snmp Devices

    5: SNMP D HAPTER EVICE ONFIGURATION Discovering Single The discovery feature also lets you add devices one at a time. SNMP Devices To discover multiple SNMP devices, see Discovering Multiple SNMP Devices page 103. To discover a single SNMP device: 1 In the explorer tree, right-click an equipment sub-folder, bay, or rack under the Equipment root folder.
  • Page 109 Discovering Single SNMP Devices 3 In the New Device dialog box, enter the appropriate discovery parameters. See Table Table 32 Discovery Parameters Parameter Description Hostname/IP Address The IP address of the SNMP device to be discovered. Timeout (sec) The SNMP time out, in seconds. The default is 1. Retrys The number of times EMS will retry connecting to an SNMP device.
  • Page 110 5: SNMP D HAPTER EVICE ONFIGURATION 5 In the New Device dialog box, enter the appropriate SNMPv3 parameters. Table 33 Table 33 Additional Discovery Parameters for SNMPv3 with No Authentication Parameter Description Context Name For SNMPv3, leave this field blank. Contact Engine ID For SNMPv3, enter #.
  • Page 111: Listing Devices By Ip Address Instead Of Hostname

    Table 34 Additional Parameters for SNMPv3, Authentication, and No Encryption Parameter Description User Name Enter the user name. The default is manager for most 3Com SNMP devices. Password Enter the password. The default is manager for most 3Com SNMP devices.
  • Page 112: Deleting Snmp Devices And Folders

    5: SNMP D HAPTER EVICE ONFIGURATION Deleting SNMP The EMS GUI lets you delete SNMP devices, device folders, bays, and Devices and Folders racks from the explorer tree. Not all elements in the explorer tree can be deleted. The menu option may not be available for some sub-elements.
  • Page 113: Viewing Snmp Device Identification

    Viewing SNMP Device Identification Viewing SNMP To view basic identification information for an SNMP device: Device Identification 1 From the explorer tree, select the SNMP device. 2 In the right pane of the main window, select the Identification tab. The Properties view changes to show the Identification tab. 3 Use the Identification tab for your customized needs.
  • Page 114: Configuring The Snmp Version

    5: SNMP D HAPTER EVICE ONFIGURATION Configuring the EMS acts as an SNMP manager communicating with various SNMP SNMP Version devices, or agents. Select the SNMP version that communicates with each SNMP device. To select the SNMP version for the SNMP manager: 1 From the explorer tree, select the SNMP device.
  • Page 115: Common Snmp Device Configuration

    Device standard MIBs (for example, RFC MIBs). These configurables and statistics Configuration are considered common across all SNMP devices, not just 3Com-specific devices. For more information on these configurables and statistics, see “SNMP Device Common Configuration Tabs” in the Enterprise Management Suite Administration Guide.
  • Page 116: Import New Devices

    5: SNMP D HAPTER EVICE ONFIGURATION Import New Devices This option will import all devices that are not currently present in EMS. The import will create an Equipment folder for each subnet present in the HP OpenView database. All the devices in each subnet will then be imported into the appropriate Equipment folder.
  • Page 117: Unreserving An Element

    Renaming Elements Figure 29 shows the explorer tree when an element is locked. Figure 29 Reserving Elements Unreserving an To unreserve an element in the explorer tree: Element 1 From the explorer tree, right-click the reserved element. 2 From the pop-up menu, select Operator Un-reserve. Renaming Elements To change the name of a selected element, use the Rename command.
  • Page 118: Configuring Equipment Folder Parameters

    5: SNMP D HAPTER EVICE ONFIGURATION 3 Type the new name for the selected element. 4 Click OK. Configuring Every equipment folder created in EMS has a Discovery tab available to Equipment Folder view and configure parameters that pertain to that specific folder. You Parameters can edit and re-run the discovery parameters from the equipment folder’s right-click menu to update the parameters that you want to associate...
  • Page 119 If you select this parameter (recommended), EMS will automatically skip over network and broadcast addresses based on the subnet mask. NOTE: 3Com recommends this option is set to Yes. Community String (Read) The SNMP Read Community string for access to the devices.
  • Page 120: To Discover A Range Of Snmp Devices Using The Discovery Tab

    5: SNMP D HAPTER EVICE ONFIGURATION To Discover a Range To discover a range of SNMP Devices within an equipment folder using of SNMP Devices the Discovery tab: using the Discovery 1 From the explorer tree, select an equipment folder at the level you want. 2 From the Discovery tab, configure the parameters according to the descriptions in Table...
  • Page 121: Save Values To The Discovery Tab

    Schedulable GUI Based Device Discovery Table 37 Copy Values from Discovery Tab dialog Button Behavior Button Action All applicable attributes are copied from the Discovery tab to the dialog being launched Launches the relevant Discovery dialog with the dialog fields containing the same values as the last time. Cancel Closes the message box with no further action being taken.
  • Page 122 5: SNMP D HAPTER EVICE ONFIGURATION Table 38 Save Values to Discovery Tab Dialog Button Behavior Button Action Do not ask me again Marking this checkbox will record the user answer to this dialog (either Yes or No, the Cancel response is not recorded).
  • Page 123 Schedulable GUI Based Device Discovery Figure 32 Session Preferences Discovery Tab Boxes...
  • Page 124 5: SNMP D HAPTER EVICE ONFIGURATION Table 39 lists the behavior of the available options for the copy values on the Discovery tab box: Table 39 Session Preferences Discovery Tab Copy Values Button Action All applicable attributes are copied from the Discovery tab to the dialog being launched.
  • Page 125: Gui Client

    GUI C LIENT ONFIGURATION Configuring Use the User Options option from the Tools menu to customize the look Environment and feel of the GUI client and the state icons that appear next to each Settings node in the explorer tree. To customize the GUI client environment: 1 From the main menu of the EMS main window, select Tools.
  • Page 126 6: GUI C HAPTER LIENT ONFIGURATION Figure 33 Session Preferences Tab a In the Adviser Pane Preferences section, select the Always show Advisor on startup checkbox if you want the Advisor window to appear each time you launch the GUI Client. The Advisor window appears on GUI client startup by default.
  • Page 127 Configuring Environment Settings Figure 34 State ICONs tab a Select the State ICON to show in tree view drop-down list to view the available state type icons. See Figure 35 Figure 35 State ICON to Show in Tree View b Select a state type according to the options shown in Table...
  • Page 128 6: GUI C HAPTER LIENT ONFIGURATION Table 41 lists the choices for the State Icon to show in tree view drop-down list. Table 41 Monitor State Types State Type Description operationalState enabled disabled degraded usageState idle active busy administrativeState locked unlocked shutting down If a device is disabled all properties and attributes related to MIB objects...
  • Page 129: Configuring The Printer Page Setup

    Configuring the Printer Page Setup Figure 37 State Color Palette Click Reset to return to the default color. d Use the Swatches, HSB, and RGB tabs to choose the specific color you want. e Select a new color and click OK to save your changes. Configuring the Before printing, configure the printer page setup.
  • Page 130 6: GUI C HAPTER LIENT ONFIGURATION To configure the printer page setup: 1 On the main menu, select the File menu and then select Page Setup. See Figure 38 Figure 38 Page Setup Dialog Box 2 In the Paper section, select the Size and Source from the drop-down lists. The default for Size is Letter and the default for Source is Automatically Select.
  • Page 131: Configuring The Display Of Non-supported Mib Objects In The Ems Gui

    Configuring the Display of Non-supported MIB Objects in the EMS GUI Configuring the All MIB objects generated by an SNMP device that are not supported by Display of EMS are automatically hidden in the GUI client. However, if you prefer to Non-supported MIB see non-supported MIB objects in the GUI as Not Supported, use this Objects in the EMS...
  • Page 132 6: GUI C HAPTER LIENT ONFIGURATION...
  • Page 133: User Configuration

    ONFIGURATION EMS gives you the ability to add new EMS GUI and CLI client users. You can also assign a root view to a user preventing them from accessing SNMP devices not assigned to them. Also, use EMS to customize the password and access rights for each user.
  • Page 134: Creating New Users

    7: U HAPTER ONFIGURATION Creating New Users To create a new user: 1 In the explorer tree, right-click the Users folder. A pop-up menu appears. Figure 2 From the pop-up menu, select New and then select User. See Figure 40 New User in Users Dialog Box 3 In the New user in Users dialog box, enter the information as described in Table 42 Table 42 New User Information...
  • Page 135: Deleting A User

    Deleting a User Table 42 New User Information (continued) Attribute Description Department Type the department for this user. This department name appears on the Identification tab when you select a user in the explorer tree. This is an optional parameter. 4 If desired, click the Optional view root button, which allows you to assign the root view for a particular user.
  • Page 136: Assigning User Access Rights

    7: U HAPTER ONFIGURATION 4 From the pop-up menu, select Root view and then select Assign. The contents of the explorer tree appear in a dialog box. 5 Navigate through the equipment folders and select the root view for this particular user.
  • Page 137: Removing An Assigned Root View

    Removing an Assigned Root View 3 On the Identification tab, double-click the Rights property and select either browser or operator from the drop-down list. CAUTION: If the only EMS GUI user is the Administrator, and you set the user rights to “browser”, when you login again as the Administrator, you cannot change the rights back to operator.
  • Page 138: Importing Ems Users

    7: U HAPTER ONFIGURATION For example: c:\EMS 3 When finished, click Close. 4 If you are going to use this list of users for another EMS server, copy and paste the text file from this workstation into the directory on the other EMS server where the EMS software files are located.
  • Page 139: Changing User Passwords

    User Passwords Figure 42 Operation Complete Dialog Box 3 Click OK. The next time the user starts the EMS GUI client, the password will be blank. Changing User In order to change a user password, the current password must be Passwords known.
  • Page 140: Setting A Login Expiration Date And Time

    7: U HAPTER ONFIGURATION Setting a Login For each user in the explorer tree, you can set a login expiration date. If Expiration Date and you set the login expiration date for a particular user, a user will not be Time able to log into the EMS server after the set date and time.
  • Page 141: Broadcasting Messages To Users

    Broadcasting Messages to Users A display like the following shows current users: User1 (User) at 04/08/2002 10:43:37 IP=10.1.1.1 Port=2089 2 Enter a logout command to log out each user, as shown here: logout User1 A confirmation message displays, as shown here: User1 has been logged out.
  • Page 142: Applying Radius Authentication To A User

    7: U HAPTER ONFIGURATION 2 Right-click the Users folder and select Send Message to all. The Send Message dialog box appears. 3 When finished typing the message, click OK. EMS broadcasts the message in an EMS Chat window to all users in the Users root folder.
  • Page 143: Changing A User's Radius Shared Secret

    Configuring User Access to Device Folders Table 43 RADIUS Tab Description Field Description Authentication Type From the drop-down menu, choose either PAP or CHAP depending on the type of authentication you want to use. Primary RADIUS server This is the IP address of the user’s preferred RADIUS server.
  • Page 144 7: U HAPTER ONFIGURATION To configure user device folder access permissions: 1 Log into the EMS client as administrator. 2 In the explorer tree, select a user under the Users root folder that you want to establish permissions for. 3 From the right-hand side of the EMS window, click the Permissions tab. 4 For any folder you want to edit the permissions for, double-click the field next to the attribute and choose either Yes or No.
  • Page 145: Telnet Script Access Levels

    Telnet Script Access Levels Telnet Script Access EMS provides different access levels to the telnet script facility. This is Levels in the form of user permissions where the administrator can determine the access level they wish to assign to a particular user. A user is assigned an access level between 1 and 5 (inclusive) that determines the telnet scripts a user can run.
  • Page 146 7: U HAPTER ONFIGURATION Figure 46 Telnet Scripting Access Level attribute 5 Click Yes or No at the drop-down menu list on Telnet Scripting Write Access attribute as shown in Figure 47 to control whether that user can edit telnet scripts or not. Figure 47 Telnet Scripting Write Access Attribute When this attribute is set to No, the user cannot launch the Telnet Scripts Manage Scripts right-click menu, which prevents access to the...
  • Page 147: Logical View Configuration

    OGICAL ONFIGURATION Logical views are a mechanism for grouping tree elements (for example, devices, configuration templates, and scheduled tasks) in a group of your choosing. Create logical views to include any managed SNMP device from any of the root folders. For example, you can create a logical view under the main Equipment folder in the explorer tree to quickly access and view a specific group of devices organized by device type, geographical region, and so forth.
  • Page 148: Deleting A Logical View

    8: L HAPTER OGICAL ONFIGURATION The folder you just created displays as a sub-folder under the Logical Views root folder. 5 Right-click the newly-labeled folder, and select Add from the pop-up menu. 6 In the root Equipment folder, navigate to the specific device folder (or bay or rack) you want to use in your new logical view folder.
  • Page 149: Network Management Platform Integration Configuration

    The network management platforms include support for the products listed in Supported Devices page About 3Com The 3Com Integration Kit customizes a Tivoli NetView or HP OpenView Integration Kit Network Node Manager installation to provide: Iconic representation (NNM only) ■...
  • Page 150: Installation

    NTEGRATION ONFIGURATION Installation This section describes how to install Version 2.0 of the 3Com Software Integration Kit, which is distributed on a CD-ROM. Before installing the 3Com Integration Kit, you must install Sun Microsystems Java 2 Runtime Environment version 1.4.2 or later.
  • Page 151 This section summarizes the installation and lists any errors that occurred during installation. 9 Click Finish to complete the installation. If you need to install launch points for your 3Com Network Management software, see Menu Integration and Application Registration Files page 156.
  • Page 152: Launching Ems From A Network Management Platform

    The .arf file, as shipped on the CD, references the default installation location for EMS. 5 To change the default location, edit the following section of the .arf file (marked in bold): DisplayString "Launch 3Com EMS Client"; Command "C:\\Program Files\\3Com\\EMS\\runGUIClient.bat";...
  • Page 153: Launching Ems From A Network Management Platform

    Launching EMS from To launch EMS from a network management platform: a Network Management Platform 1 From the Tools menu, click 3Com EMS Client. See Figure 51, which shows an example using HP OpenView. Figure 51 HP OpenView EMS Launch Point...
  • Page 154: Icons

    ■ MIBs ■ OIDs (see Configuration Files for SysObjectID Recognition - ■ oid_to_sym, oid_to_type) Symbol types (see Symbol Integration File - 3Com.srf) ■ Icons In the Network Node Manager kit, icons are provided for each device type. See Figure Figure 52 Network Node Manger Icon The NetView kit installs generic icons, based on the function of the device.
  • Page 155: Mibs

    Integration Kit General Features Figure 53 Trap Translation EMS provides an updated trapd.conf file that decodes all 3Com device traps. EMS also sends its own traps for backup, restore, and agent update actions. EMS’ SNMP library does not share the trap port. Therefore, EMS receives all traps and forwards them on to OpenView or NetView as appropriate.
  • Page 156: Network Node Manager Integration Architecture

    Application menu display and the action taken when the user clicks on the menu. The Registration Files 3Com Integration Kit CD contains three application registration files to provide the following menus for a selection of 3Com network management applications: 3Com_dv.arf ■...
  • Page 157: Fields File

    The fields file (3Com.fld) specifies the 3Com database fields used to customize the OpenView Network Node Manager or NetView database. These fields are used to identify the capabilities of 3Com devices, and you can use these fields in conjunction with your own customizations.
  • Page 158: Configuration Files For Sysobjectid Recognition

    9: N HAPTER ETWORK ANAGEMENT LATFORM NTEGRATION ONFIGURATION Configuration Files The oid_to_sym file associates a sys object ID to a symbol type (for for SysObjectID example, a Connector). A typical entry is: Recognition 1.3.6.1.4.1.43.10.27.4.1.2.4:Connector:SuperStack 3 Switch 4400 The oid_to_type file associates a sysobject ID with the type of device. The following list the device types: B = bridge ■...
  • Page 159: Symbol Integration File

    ■ Windows– C:\Program Files\HP Openview\NNM\symbols\C ■ The 3Com.srf lists the symbols used for 3Com products. The file is similar to a database schema, in that it contains values for specific device fields. A typical entry is: SymbolType "Connector" : "3Com SuperStack 3 Switch 3300"...
  • Page 160: Trap File

    FROM A3Com-products-MIB DisplayString FROM RFC1213-MIB OBJECT-TYPE FROM RFC-1212 This means that 3FC-1212, RFC1213, and 3com-45 (which contains the definition for A3Com-products-MIB) must be loaded before 3FC-043. The file $3Com/common/ov/mibs/miborder.txt contains the list of MIBs loaded in the correct order.
  • Page 161: Trap Support

    Trap Support Trap Support EMS provides an updated trapd.conf file that decodes all 3Com device traps. EMS also sends its own traps for backup, restore, and agent update actions. EMS’ SNMP library does not share the trap port. Therefore, EMS receives all traps and forward them on to OpenView or NetView as appropriate.
  • Page 162: Uncommenting The Snmp.trap.threads Line

    9: N HAPTER ETWORK ANAGEMENT LATFORM NTEGRATION ONFIGURATION Figure 55 Uncommenting the SNMP.trap.QueueSize Line remove the pound sign SNMP.trap.QueueSize=2000 8 Edit the queue size to suit your needs. The default is 2000. 9 Set the number of processing threads. 10 Uncomment the SNMP.trap.Threads line. See . Uncommenting the SNMP.trap.Threads remove the pound sign...
  • Page 163: Ip Address Ranges Tab

    Trap Support Figure 56 Trap Forwarding Dialog — Event Type Tab Contents 2 Select the event types and forwarding options you want from those displayed. 3 Click Save to save the changes or click Cancel to close the dialog without saving.
  • Page 164 9: N HAPTER ETWORK ANAGEMENT LATFORM NTEGRATION ONFIGURATION Figure 57 Trap Forwarding Dialog — IP Address Ranges Tab 1 Select the Forward traps from all IP addresses button if this is your preferred option. 2 Click Save to save the changes or click Cancel to close the dialog without saving.
  • Page 165 Trap Support The fields in the IP Address Ranges tab behave as described in Table 44 Table 44 IP Address Ranges Tab Field Behavior Dialog Field Behaviour Forward traps from all When selected, EMS forwards all traps received (subject to IP addresses the event type filtering) Only forward traps...
  • Page 166 9: N HAPTER ETWORK ANAGEMENT LATFORM NTEGRATION ONFIGURATION...
  • Page 167: Operations

    PERATIONS This chapter provides information that will help you monitor devices, individual properties, and servers, create inventory reports for groups of devices, and use various utility features such as the MIB browser, server monitor, and memory monitor. This chapter contains the following topics: Verifying the EMS Serial Number ■...
  • Page 168: Verifying The Ems Serial Number

    10: O HAPTER PERATIONS Using the Server Monitor to Monitor EMS Server Performance ■ Monitoring EMS Server Memory ■ Monitoring EMS GUI Memory ■ Displaying Server Console Commands ■ Displaying EMS CLI Client Console Commands ■ Configuring Table Data Loading ■...
  • Page 169 Viewing Software Version and Copyright Information To view EMS software version and copyright information: 1 From the menu bar, select Help and then select About. See Figure 58 Figure 58 Viewing the EMS Software Version The About window opens. From the EMS Version heading the EMS version is listed and from the Installed Packages heading the package version is listed.
  • Page 170: Toggling Between The Explorer View And List View

    10: O HAPTER PERATIONS Figure 59 Viewing Copyright Information The Copyright window opens and displays copyright information for EMS and other related proprietary products. 4 When finished, click Close. Toggling between When the EMS GUI client starts, the Explorer view is the default view for the Explorer View the left-hand pane of the EMS GUI main window, which lists the system and List View...
  • Page 171 Toggling between the Explorer View and List View To use the List view instead of the Explorer view: 1 In the left-hand pane of the EMS GUI main window, select the List tab. Figure 60 Figure 60 List Tab 2 At the bottom of the List tab, click Filter. See Figure 61...
  • Page 172 10: O HAPTER PERATIONS Figure 61 Target Filter Selection Window Use this filter engine to search for specific devices, event records, managed objects, and configuration groups. For example, if you want to search all managed objects in the explorer tree, select the All Managed Objects root element.
  • Page 173: Toggling Between The Properties And Related View

    Toggling between the Properties and Related View Figure 62 Selecting an Element in the List View select an element Using the List view, you can perform operations on the elements and manage the element properties using most of the same procedures described in this guide.
  • Page 174 10: O HAPTER PERATIONS To use the Related view instead of the Properties view: 1 In the right-hand pane of the EMS GUI main window, select the Related tab. See Figure 63 Figure 63 Related Tab 2 Use the Related view to verify the relationship of related objects in the explorer tree.
  • Page 175: Expanding And Collapsing Elements

    Expanding and Collapsing Elements Expanding and The EMS GUI client gives you three ways to expand and collapse any Collapsing element containing sub-elements in the explorer tree. Elements Expand and collapse elements in the explorer tree using one of the following options: Tree menu option ■...
  • Page 176: Executing Commands For Multiple Elements

    10: O HAPTER PERATIONS Executing Some of the options and commands available from the toolbar and in the Commands for pop-up menus can be performed on more than one element at the same Multiple Elements time. If you do this, EMS creates separate a job for each element you select from the explorer tree.
  • Page 177: Monitoring The Status Of Gui Elements

    Monitoring the Status of GUI Elements Monitoring the When using the EMS GUI client, each element within EMS is given an Status of GUI administrative, operational, and usage state which is determined by the Elements usage of each element and all associated sub-elements, including devices and users.
  • Page 178: Using The State Icon

    10: O HAPTER PERATIONS For a detailed definition of each state type, see Table Using the State Icon To view the administrative, operational, and usage states using state icons in the explorer tree: 1 In the explorer tree, select an element. 2 View the Operational State icon next to each element in the explorer tree.
  • Page 179: Using The Monitor State Utility

    Monitoring the Status of GUI Elements Using the Monitor State Utility To view the administrative, operational, and usage states using the Monitor State utility: 1 In the explorer tree, select an element. 2 Right-click the element, and select Monitor State from the pop-up menu. Figure 64 shows the Monitor State utility.
  • Page 180: Refreshing The Status

    10: O HAPTER PERATIONS Figure 65 shows the Class selection filter window. Figure 65 Class Selection Filter Window Use this filter engine to search for specific devices, event records, managed objects, and configuration groups. For example, if you want to search all managed objects in the explorer tree, select the All Stated Managed Objects root element.
  • Page 181: Using The Mib Browser

    Browser Managed Information Base (MIB) values of compiled MIBs that are either distributed with EMS or integrated by 3Com Customer Services. Some MIB values available in the browser may either be unsupported or simply not available through the GUI client.
  • Page 182: Viewing Numeric Values In Alternative Formats

    10: O HAPTER PERATIONS Viewing Numeric You can display and edit numeric property values in various data formats, Values in including: Alternative Formats Octet String ■ ASCII characters ■ Integer ■ IP Address ■ Octal ■ Binary ■ To view numeric values in alternative formats: 1 In the explorer tree, select an element that contains a numeric value.
  • Page 183: Monitoring Numeric Properties

    Monitoring Numeric Properties Monitoring You can view a dynamic line graph to monitor any numeric property in Numeric Properties EMS. Each graph scrolls continuously according to the poll rate, which has a default of five seconds. You can view graphs for as many properties as you want at the same time.
  • Page 184: Using Ems To Edit Network Device Properties

    10: O HAPTER PERATIONS Using EMS to Edit The EMS GUI client lets you configure an individual device or an entire Network Device group of devices. To configure an individual device, select a device in the Properties left-hand pane, select a specific tab in the right-hand pane, and then edit the specific property directly.
  • Page 185: Editing Simple Properties

    Using EMS to Edit Network Device Properties Editing Simple Most of the time, properties are organized in a simple list on the Properties right-hand pane of the EMS GUI. You can edit any simple MIB object property that has a white background.
  • Page 186: Editing Tabular Properties

    10: O HAPTER PERATIONS Figure 69 shows how to select simple properties. Figure 69 Selecting Simple Properties double-click the property field 4 Click Save all. Editing Tabular Sometimes simple properties are organized in a database (MIB) table on Properties the right-hand pane of the EMS GUI main window. Simple properties are organized in tabular columns and rows to provide greater functionality and database integrity.
  • Page 187 Using EMS to Edit Network Device Properties shows how to edit tabular properties. Figure 70 Figure 70 Tabular Properties informational property editable property table index add a table row delete a table row To edit a tabular property: 1 In the explorer tree, select an element that contains a tabular property. 2 In the right-hand pane, select a tab that contains a MIB table.
  • Page 188: Copying And Pasting Values Between Elements

    10: O HAPTER PERATIONS 4 Fill in the appropriate information the dialog box. 5 When finished, click OK. A new row is added to the MIB table. You can change any of the editable (simple) properties after adding the row, as described in Editing Simple Properties page...
  • Page 189 Copying and Pasting Values between Elements The following dialog box opens, showing a list of potential values to change. Figure 71 shows the SNMP Values to Change dialog box. Figure 71 SNMP Values to Change Dialog Box 5 To remove a value from the list, select the value and click Remove. 6 When you are satisfied with the list of values you want to change, click Set.
  • Page 190: Locating Information Using The Find Command

    10: O HAPTER PERATIONS Locating The Find command lets you search for a string of text that may be part of Information Using a EMS Tree Label, Property (field label), or MIB OID. Searches can either the Find Command include or exclude sub-elements. Instead of using the Find command from an explorer tree node, you can use the Find toolbar option to find specific information.
  • Page 191 Locating Information Using the Find Command Figure 73 Explorer Tree Window 6 When finished, click OK. 7 If you would like to search in all sub-elements of the selected tree node, select the Include All Subtrees checkbox. 8 After entering your search criteria, click Find now. If any matches are found, the results appear in the Find window.
  • Page 192: Creating Inventory Reports

    10: O HAPTER PERATIONS Figure 74 Sample Search Using the Find Command 9 Review the list of results and double-click the result that best matches your search criteria. The explorer tree changes and takes you directly to the tree node where that property or MIB object is located.
  • Page 193: Locating Information In Mib Tables Using The Find Button

    Locating Information in MIB Tables Using the Find Button Figure 75 Inventory Report To save the inventory as an .html file for historical purposes, click “Save” at the bottom of the inventory report window. You can also access inventory reports on the web browser interface. To use the web browser interface, see Accessing the Web Browser Interface.
  • Page 194: Accessing The Web Browser Interface

    10: O HAPTER PERATIONS The editable fields for the Find row in table dialog box changes, depending on the index values found in the associated MIB tables. You can only search on index values. 3 In the Find row in table dialog box, type the desired search information in the editable fields or select the desired search information from drop-down lists, and click OK.
  • Page 195: Printing The Ems Gui Explorer Tree

    Printing the EMS GUI Explorer Tree AuditLog-yyyymmdd.log — These log files are created if the ■ AuditLog field is set to yes in the server.properties file. ftplog/ — The log files in this folder contain a detailed list of all FTP ■...
  • Page 196: Starting The Server As A Unix Background Process

    When launched as a background process or daemon, the EMS server will still issue its normal startup messages to the console. 3Com recommends that you only run the EMS server as a daemon when there is no expected interaction required with the EMS server command prompt.
  • Page 197: Starting The Server As A Windows Background Process

    3Com does not recommend this option because if you accidentally close the command window, Windows will force the server to stop. 3Com recommends that you create a Scheduled Task that will run the ■ server in daemon mode when Windows boots. The scheduled task should have the following properties: Run —...
  • Page 198: Stopping The Ems Server

    10: O HAPTER PERATIONS is no guarantee that it will be allowed to. In the daily console log, you will see entries similar to the following: 11/27/2004 14:53:38 (E) ** SERVER PANIC - Attempting to close logs and database connections ** 11/27/2004 14:53:38 (I) FDServerLog:log\AuditLog-20021127.log shutting down...
  • Page 199: Starting The Ems Cli Client

    Make sure the EMS server is running before using this procedure. 2 Navigate to the directory containing the installed EMS software files, the default through Windows is C:\Program Files\3Com\EMS. 3 From the command prompt, enter the following command and optional...
  • Page 200 10: O HAPTER PERATIONS Table 47 lists optional parameters for the runServerMonitor command. Table 47 Optional Parameters for the Server Monitor Parameter Usage -Sservername Where servername is the hostname or IP address of the EMS server. The default is localhost. -Llogfile Where logfile is the name of the log file to capture all data in Comma Separated Version (CSV) format.
  • Page 201: Monitoring Ems Server Memory

    Monitoring EMS Server Memory 4 Select the Statistics tab and select any of the EMS server statistics you would like to monitor and graph performance data for. 5 At the bottom of the Server Monitor window, click Poll Rate to set the refresh rate for the server monitor.
  • Page 202: Monitoring Ems Gui Memory

    10: O HAPTER PERATIONS Figure 78 Memory Tab on the EMS Server Monitor At the left-hand side of the Memory tab, you can monitor the amount of memory available and the amount of memory currently being used. 4 When finished, click Close. Monitoring EMS To monitor the amount of memory the EMS GUI client is using: GUI Memory...
  • Page 203: Displaying Server Console Commands

    Displaying Server Console Commands Figure 79 GUIClient Memory Monitor At the left-hand side of the GUIClient Memory Monitor window, you can monitor the amount of memory allocated and the amount of memory currently being used. 3 When finished, click Close. Displaying Server Although it is not normally necessary to use any of the server commands Console Commands...
  • Page 204: Displaying Ems Cli Client Console Commands

    10: O HAPTER PERATIONS Figure 80 shows the list of available EMS server console commands. Figure 80 EMS Server Console Commands For a comprehensive list of all EMS server console commands and their functions, see EMS Server Console page 207. Displaying EMS CLI To display the list of available EMS server console commands: Client Console...
  • Page 205 Configuring Table Data Loading To change the table data loading from one mode to the other, do one of the following steps: 1 If the Table loading indicator is green: EMS is set to load table data continuously. Click Table loading. The Table loading indicator changes to red, and EMS changes to loading the table data line by line as you scroll down in a full on-screen table display.
  • Page 206 10: O HAPTER PERATIONS...
  • Page 207: Ems Server Console

    OMMAND NTERFACE EFERENCE This appendix contains a comprehensive list of all commands used on the Enterprise Management Suite (EMS) server command line interface (CLI) and the EMS CLI client CLI. EMS Server Console Table 48 lists the available commands for the EMS server CLI. Table 48 Server Console Commands Command Function...
  • Page 208: Using Daemon-specific Server Console Commands

    A: C PPENDIX OMMAND NTERFACE EFERENCE Table 48 Server Console Commands (continued) Command Function resdiscoverAll rediscovers all equipment restart [/f] restarts the server rmov_integration remove HP OpenView integration set name=value set server property value stats show instrumentation statistics stop [/f] stops the server uninstall packageName uninstall a package with packageName...
  • Page 209: Ems Cli Client

    EMS CLI Client For example: user123>server stop /f Signaled server to stop user123>Server signal: The server shutdown. You will have to login again later. This is considered normal operation, indicating that you have successfully stopped the EMS server. You can also use the CLI client to issue one line commands without bringing up an interactive session.
  • Page 210: Dormant Server Cli Commands

    A: C PPENDIX OMMAND NTERFACE EFERENCE Table 50 EMS CLI Client Commands (continued) Command Function quit exit the CLI rediscoverAll rediscovers all equipment stats show instrumentation statistics stop exit the CLI users displays a list of users currently logged in Dormant Server CLI Table 51 defines how each server CLI command behaves when the server...
  • Page 211: Info Command

    Dormant Server CLI Commands Command not available – this server is running in Dormant Mode info Command command on the server CLI displays the server status — either info Active or Dormant, in addition to other information. runMode Command command accepts one of two values: runMode active ■...
  • Page 212 A: C PPENDIX OMMAND NTERFACE EFERENCE...
  • Page 213 NDEX poll rate 183 Numbers server console 207 3Com.fld 157 state 180 3Com.srf 159 comments 15 common SNMP device configuration 115 components, software 23 configuration files, for SysObjectID recognition 158 activation key 76 configuring add command 148 color palette 128...
  • Page 214 NDEX EMS_FILEHOME 89 environment settings 125 data equipment folder 101 displaying and editing in various formats 182 event flow 37 database compaction, configuring 63 event processing 37 database, configuration 61 executing commands for multiple elements 176 databases expanding and collapsing elements 175 embedded 62 explorer view 170 external 64...
  • Page 215 NDEX installing network node manager console option 59 fields file 157 EMS 56 general file location 156 network node manager 150 icon files 159 silent option 59 icons 154, 159 Instant DB, limitations 64 installation 150 integration kit 149 integration architecture 156 inventory command 192 menu integration and application registration inventory reports, creating 192...
  • Page 216 45 remote_server properties 91 network management platform 46 server behaviors 96 supported products server run modes 3Com data products 24 active, dormant 89 3Com router products 26 server startup messages 94 3Com wireless products 27 timeout and retry 92...
  • Page 217 NDEX system requirements 42 TFTP IBM iSeries 52 initial configuration 49 UNIX and Linux 51 Windows 49 TFTP server configuring EMS 51 installation 49 tool tips 35 toolbar 31 toolbar, using 175 training 13 trap support, network node manager 161 traps, forwarding to network management platform 161 tree menu option, using 175...
  • Page 218 NDEX...

This manual also for:

Enterprise management suite 2.41

Comments to this Manuals

Symbols: 0
Latest comments: